Content migration in split xr systems

Abstract

This disclosure provides systems, devices, apparatus, and methods, including computer programs encoded on storage media, for content migration in split XR systems. A graphics processor may render, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associated with the wearable display device. The graphics processor may obtain an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device. The graphics processor may receive, from a companion device and based on the indication, second rendered content based on a second set of characteristics associated with the companion mode. The graphics processor may process the first rendered content and the second rendered content. The graphics processor may configure a combined display buffer based on the processed first rendered content and the processed second rendered content.

Description

CONTENT MIGRATION IN SPLIT XR SYSTEMSCROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of Indian Provisional Application No. 202321031173, entitled “CONTENT MIGRATION IN SPLIT XR SYSTEMS” and filed on May 2, 2023, which is expressly incorporated by reference herein in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates generally to processing systems, and more particularly, to one or more techniques for graphics processing.INTRODUCTION

[0003] Computing devices often perform graphics and / or display processing (e.g., utilizing a graphics processing unit (GPU), a central processing unit (CPU), a display processor, etc.) to render and display visual content. Such computing devices may include, for example, computer workstations, mobile phones such as smartphones, embedded systems, personal computers, tablet computers, and video game consoles. GPUs are configured to execute a graphics processing pipeline that includes one or more processing stages, which operate together to execute graphics processing commands and output a frame. A central processing unit (CPU) may control the operation of the GPU by issuing one or more graphics processing commands to the GPU. Modern day CPUs are typically capable of executing multiple applications concurrently, each of which may need to utilize the GPU during execution. A display processor may be configured to convert digital information received from a CPU to analog values and may issue commands to a display panel for displaying the visual content. A device that provides content for visual presentation on a display may utilize a CPU, a GPU, and / or a display processor.

[0004] Current techniques for transitioning between a standalone mode and a companion mode of an extended reality (XR) device may involve restarting an XR application on the XR device. There is a need for improved techniques pertaining to transitioning between a standalone mode and a companion mode of an XR device.BRIEF SUMMARY

[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus for graphics processing at a wearable display device are provided. The apparatus includes a memory; and a processor coupled to the memory and, based on information stored in the memory, the processor is configured to: render, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associated with the wearable display device; obtain an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device; receive, from a companion device and based on the indication, second rendered content based on a second set of characteristics associated with the companion mode; process the first rendered content and the second rendered content; and configure a combined display buffer based on the processed first rendered content and the processed second rendered content.

[0007] To the accomplishment of the foregoing and related ends, the one or more aspects include the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.BRIEF DESCRIPTION OF THE DRAWINGS

[0008] FIG. 1 is a block diagram that illustrates an example content generation system in accordance with one or more techniques of this disclosure.

[0009] FIG. 2 illustrates an example graphics processor (e.g., a graphics processing unit (GPU)) in accordance with one or more techniques of this disclosure.

[0010] FIG. 3 illustrates an example display framework including a display processor and a display in accordance with one or more techniques of this disclosure.

[0011] FIG. 4 is a diagram illustrating example aspects of augmented reality (AR) in accordance with one or more techniques of this disclosure.

[0012] FIG. 5 is a diagram illustrating example aspects of split extended reality (XR) head mounted displays (HMDs) in accordance with one or more techniques of this disclosure.

[0013] FIG. 6 is a diagram illustrating example aspects of a split XR system in accordance with one or more techniques of this disclosure.

[0014] FIG. 7 is a diagram illustrating example aspects of transitioning from a standalone mode to a companion mode in a split XR system in accordance with one or more techniques of this disclosure.

[0015] FIG. 8 is a diagram illustrating example aspects of data gathering in accordance with one or more techniques of this disclosure.

[0016] FIG. 9 is a communication flow diagram illustrating example communications between a wearable display device (WDD) and a companion device in accordance with one or more techniques of this disclosure.

[0017] FIG. 10 is a flowchart of an example method of graphics processing in accordance with one or more techniques of this disclosure.

[0018] FIG. 11 is a flowchart of an example method of graphics processing in accordance with one or more techniques of this disclosure.DETAILED DESCRIPTION

[0019] Various aspects of systems, apparatuses, computer program products, and methods are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein one skilled in the art should appreciate that the scope of this disclosure is intended to cover any aspect of the systems, apparatuses, computer program products, and methods disclosed herein, whether implemented independently of, or combined with, other aspects of the disclosure. For example, anapparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. Any aspect disclosed herein may be embodied by one or more elements of a claim.

[0020] Although various aspects are described herein, many variations and permutations of these aspects fall within the scope of this disclosure. Although some potential benefits and advantages of aspects of this disclosure are mentioned, the scope of this disclosure is not intended to be limited to particular benefits, uses, or objectives. Rather, aspects of this disclosure are intended to be broadly applicable to different wireless technologies, system configurations, processing systems, networks, and transmission protocols, some of which are illustrated by way of example in the figures and in the following description. The detailed description and drawings are merely illustrative of this disclosure rather than limiting, the scope of this disclosure being defined by the appended claims and equivalents thereof.

[0021] Several aspects are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, and the like (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0022] By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors (which may also be referred to as processing units). Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), general purpose GPUs (GPGPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems-on-chip (SOCs), baseband processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discretehardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software can be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0023] The term application may refer to software. As described herein, one or more techniques may refer to an application (e.g., software) being configured to perform one or more functions. In such examples, the application may be stored in a memory (e.g., on-chip memory of a processor, system memory, or any other memory). Hardware described herein, such as a processor may be configured to execute the application. For example, the application may be described as including code that, when executed by the hardware, causes the hardware to perform one or more techniques described herein. As an example, the hardware may access the code from a memory and execute the code accessed from the memory to perform one or more techniques described herein. In some examples, components are identified in this disclosure. In such examples, the components may be hardware, software, or a combination thereof. The components may be separate components or subcomponents of a single component.

[0024] In one or more examples described herein, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include a random access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0025] A user may wear a display device in order to experienced extended reality (XR) content. XR may refer to a technology that blends aspects of a digital experience and the real world. XR may include augmented reality (AR), mixed reality (MR), and / or virtual reality (VR). In AR, AR objects may be superimposed on a real -world environment as perceived through the display device. In an example, AR content may be experienced through AR glasses that include a transparent or semi-transparent surface. An AR object may be projected onto the transparent or semi-transparent surface of the glasses as a user views an environment through the glasses. In general, the AR object may not be present in the real world and the user may not interact with the AR object. In MR, MR objects may be superimposed on a real -world environment as perceived through the display device and the user may interact with the MR objects. In some aspects, MR objects may include “video see through” with virtual content added. In an example, the user may “touch” a MR object being displayed to the user (i.e., the user may place a hand at a location in the real world where the MR object appears to be located from the perspective of the user), and the MR object may “move” based on the MR object being touched (i.e., a location of the MR object on a display may change). In general, MR content may be experienced through MR glasses (similar to AR glasses) worn by the user or through a head mounted display (HMD) or headset worn by the user. The HMD may include a camera and one or more display panels. The HMD may capture an image of environment as perceived through the camera and display the image of the environment to the user with MR objects overlaid thereon. Unlike the transparent or semi-transparent surface of the AR / MR glasses, the one or more display panels of the HMD may not be transparent or semi-transparent. In VR, a user may experience a fully-immersive digital environment in which the real-world is blocked out. VR content may be experienced through an HMD or headset.

[0026] As used herein, instances of the term “content” may refer to “graphical content,” an “image,” etc., regardless of whether the terms are used as an adjective, noun, or other parts of speech. In some examples, the term “graphical content,” as used herein, may refer to content produced by one or more processes of a graphics processing pipeline. In further examples, the term “graphical content,” as used herein, may refer to content produced by a processing unit configured to perform graphics processing. In stillfurther examples, as used herein, the term “graphical content” may refer to content produced by a graphics processing unit.

[0027] A split XR system may include a companion device (e.g., a phone) and a wearable display device (e.g., a HMD), where the companion device and the wearable display device may exchange data in order to facilitate the display of content on the wearable display device. The companion device may have a greater amount of computational power in comparison to an amount of computational power of the wearable display device. In some split XR systems, the wearable display device may operate in standalone mode or in companion mode. In standalone mode, the wearable display device may operate independently of the companion device. For example, the wearable display device may render frames and display the frames without transmitting or receiving data to / from the companion device. In companion mode, the wearable display device may exchange data with the companion device in order to facilitate the display of content on the wearable display device. For example, the companion device may render frames and transmit the frames to the wearable display device. The wearable display device may receive the frames, process the frames, and present the processed frames for display. When the wearable display device transitions from companion mode to standalone mode (or vice versa), an application being executed by the wearable display device and / or the companion device may have to be restarted or shutdown. This may hinder user experience. Furthermore, restarting the application may be associated with computational overhead at the wearable display device and / or the companion device.

[0028] Various technologies pertaining to content migration in a split XR system are described herein. In an example, an apparatus (e.g., a wearable display device) renders, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associated with the wearable display device. The apparatus (e.g., a wearable display device) obtains an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device. The apparatus (e.g., a wearable display device) receives, from a companion device and based on the indication, second rendered content based on a second set of characteristics associated with the companion mode. The apparatus (e.g., a wearable display device) processes the first rendered content and the second rendered content. The apparatus (e.g., a wearable display device) configures acombined display buffer based on the processed first rendered content and the processed second rendered content. Vis-a-vis obtaining the indication, processing the first rendered content and the second rendered content, and configuring the combined display buffer, the wearable display device may seamlessly transition between standalone mode and companion mode, which may provide for an improved user experience. Furthermore, by obtaining the indication, processing the first rendered content and the second rendered content, and configuring the combined display buffer, the wearable display device may seamlessly transition between standalone mode and companion mode without restarting or shutting down an application, which may conserve computational resources at the wearable display device.

[0029] The examples describe herein may refer to a use and functionality of a graphics processing unit (GPU). As used herein, a GPU can be any type of graphics processor, and a graphics processor can be any type of processor that is designed or configured to process graphics content. For example, a graphics processor or GPU can be a specialized electronic circuit that is designed for processing graphics content. As an additional example, a graphics processor or GPU can be a general purpose processor that is configured to process graphics content.

[0030] FIG. 1 is a block diagram that illustrates an example content generation system 100 configured to implement one or more techniques of this disclosure. The content generation system 100 includes a device 104. The device 104 may include one or more components or circuits for performing various functions described herein. In some examples, one or more components of the device 104 may be components of a SOC. The device 104 may include one or more components configured to perform one or more techniques of this disclosure. In the example shown, the device 104 may include a processing unit 120, a content encoder / decoder 122, and a system memory 124. In some aspects, the device 104 may include a number of components (e.g., a communication interface 126, a transceiver 132, a receiver 128, a transmitter 130, a display processor 127, and one or more displays 131). Display(s) 131 may refer to one or more displays 131. For example, the display 131 may include a single display or multiple displays, which may include a first display and a second display. The first display may be a left-eye display and the second display may be a right-eye display. In some examples, the first display and the second display may receive different frames for presentment thereon. In other examples, the first and second display mayreceive the same frames for presentment thereon. In further examples, the results of the graphics processing may not be displayed on the device, e.g., the first display and the second display may not receive any frames for presentment thereon. Instead, the frames or graphics processing results may be transferred to another device. In some aspects, this may be referred to as split-rendering.

[0031] The processing unit 120 may include an internal memory 121. The processing unit 120 may be configured to perform graphics processing using a graphics processing pipeline 107. The content encoder / decoder 122 may include an internal memory 123. In some examples, the device 104 may include a processor, which may be configured to perform one or more display processing techniques on one or more frames generated by the processing unit 120 before the frames are displayed by the one or more displays 131. While the processor in the example content generation system 100 is configured as a display processor 127, it should be understood that the display processor 127 is one example of the processor and that other types of processors, controllers, etc., may be used as substitute for the display processor 127. The display processor 127 may be configured to perform display processing. For example, the display processor 127 may be configured to perform one or more display processing techniques on one or more frames generated by the processing unit 120. The one or more displays 131 may be configured to display or otherwise present frames processed by the display processor 127. In some examples, the one or more displays 131 may include one or more of a liquid crystal display (LCD), a plasma display, an organic light emitting diode (OLED) display, a projection display device, an augmented reality display device, a virtual reality display device, a head-mounted display, or any other type of display device.

[0032] Memory external to the processing unit 120 and the content encoder / decoder 122, such as system memory 124, may be accessible to the processing unit 120 and the content encoder / decoder 122. For example, the processing unit 120 and the content encoder / decoder 122 may be configured to read from and / or write to external memory, such as the system memory 124. The processing unit 120 may be communicatively coupled to the system memory 124 over a bus. In some examples, the processing unit 120 and the content encoder / decoder 122 may be communicatively coupled to the internal memory 121 over the bus or via a different connection.

[0033] The content encoder / decoder 122 may be configured to receive graphical content from any source, such as the system memory 124 and / or the communication interface 126. The system memory 124 may be configured to store received encoded or decoded graphical content. The content encoder / decoder 122 may be configured to receive encoded or decoded graphical content, e.g., from the system memory 124 and / or the communication interface 126, in the form of encoded pixel data. The content encoder / decoder 122 may be configured to encode or decode any graphical content.

[0034] The internal memory 121 or the system memory 124 may include one or more volatile or non-volatile memories or storage devices. In some examples, internal memory 121 or the system memory 124 may include RAM, static random access memory (SRAM), dynamic random access memory (DRAM), erasable programmable ROM (EPROM), EEPROM, flash memory, a magnetic data media or an optical storage media, or any other type of memory. The internal memory 121 or the system memory 124 may be a non-transitory storage medium according to some examples. The term “non- transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted to mean that internal memory 121 or the system memory 124 is non-movable or that its contents are static. As one example, the system memory 124 may be removed from the device 104 and moved to another device. As another example, the system memory 124 may not be removable from the device 104.

[0035] The processing unit 120 may be a CPU, a GPU, a GPGPU, or any other processing unit that may be configured to perform graphics processing. In some examples, the processing unit 120 may be integrated into a motherboard of the device 104. In further examples, the processing unit 120 may be present on a graphics card that is installed in a port of the motherboard of the device 104, or may be otherwise incorporated within a peripheral device configured to interoperate with the device 104. The processing unit 120 may include one or more processors, such as one or more microprocessors, GPUs, ASICs, FPGAs, arithmetic logic units (ALUs), DSPs, discrete logic, software, hardware, firmware, other equivalent integrated or discrete logic circuitry, or any combinations thereof. If the techniques are implemented partially in software, the processing unit 120 may store instructions for the software in a suitable, non-transitory computer-readable storage medium, e.g., internal memory 121, and may execute the instructions in hardware using one or more processors toperform the techniques of this disclosure. Any of the foregoing, including hardware, software, a combination of hardware and software, etc., may be considered to be one or more processors.

[0036] The content encoder / decoder 122 may be any processing unit configured to perform content decoding. In some examples, the content encoder / decoder 122 may be integrated into a motherboard of the device 104. The content encoder / decoder 122 may include one or more processors, such as one or more microprocessors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), arithmetic logic units (ALUs), digital signal processors (DSPs), video processors, discrete logic, software, hardware, firmware, other equivalent integrated or discrete logic circuitry, or any combinations thereof. If the techniques are implemented partially in software, the content encoder / decoder 122 may store instructions for the software in a suitable, non-transitory computer-readable storage medium, e.g., internal memory 123, and may execute the instructions in hardware using one or more processors to perform the techniques of this disclosure. Any of the foregoing, including hardware, software, a combination of hardware and software, etc., may be considered to be one or more processors.

[0037] In some aspects, the content generation system 100 may include a communication interface 126. The communication interface 126 may include a receiver 128 and a transmitter 130. The receiver 128 may be configured to perform any receiving function described herein with respect to the device 104. Additionally, the receiver 128 may be configured to receive information, e.g., eye or head position information, rendering commands, and / or location information, from another device. The transmitter 130 may be configured to perform any transmitting function described herein with respect to the device 104. For example, the transmitter 130 may be configured to transmit information to another device, which may include a request for content. The receiver 128 and the transmitter 130 may be combined into a transceiver 132. In such examples, the transceiver 132 may be configured to perform any receiving function and / or transmitting function described herein with respect to the device 104.

[0038] Referring again to FIG. 1, in certain aspects, the processing unit 120 may include a content migrator 198 configured to render, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associatedwith the wearable display device; obtain an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device; receive, from a companion device and based on the indication, second rendered content based on a second set of characteristics associated with the companion mode; process the first rendered content and the second rendered content; and configure a combined display buffer based on the processed first rendered content and the processed second rendered content. Although the following description may be focused on graphics processing, the concepts described herein may be applicable to other similar processing techniques, such as display processing. Furthermore, although the following description may be focused on wearable display devices in an XR context, the concepts described herein may also be applicable to non-wearable display devices in XR contexts.

[0039] A device, such as the device 104, may refer to any device, apparatus, or system configured to perform one or more techniques described herein. For example, a device may be a server, a base station, a user equipment, a client device, a station, an access point, a computer such as a personal computer, a desktop computer, a laptop computer, a tablet computer, a computer workstation, or a mainframe computer, an end product, an apparatus, a phone, a smart phone, a server, a video game platform or console, a handheld device such as a portable video game device or a personal digital assistant (PDA), a wearable computing device such as a smart watch, an augmented reality device, or a virtual reality device, a non-wearable device, a display or display device, a television, a television set-top box, an intermediate network device, a digital media player, a video streaming device, a content streaming device, an in-vehicle computer, any mobile device, any device configured to generate graphical content, or any device configured to perform one or more techniques described herein. Processes herein may be described as performed by a particular component (e.g., a GPU) but in other embodiments, may be performed using other components (e.g., a CPU) consistent with the disclosed embodiments.

[0040] GPUs can process multiple types of data or data packets in a GPU pipeline. For instance, in some aspects, a GPU can process two types of data or data packets, e.g., context register packets and draw call data. A context register packet can be a set of global state information, e.g., information regarding a global register, shading program, or constant data, which can regulate how a graphics context will beprocessed. For example, context register packets can include information regarding a color format. In some aspects of context register packets, there can be a bit or bits that indicate which workload belongs to a context register. Also, there can be multiple functions or programming running at the same time and / or in parallel. For example, functions or programming can describe a certain operation, e.g., the color mode or color format. Accordingly, a context register can define multiple states of a GPU.

[0041] Context states can be utilized to determine how an individual processing unit functions, e.g., a vertex fetcher (VFD), a vertex shader (VS), a shader processor, or a geometry processor, and / or in what mode the processing unit functions. In order to do so, GPUs can use context registers and programming data. In some aspects, a GPU can generate a workload, e.g., a vertex or pixel workload, in the pipeline based on the context register definition of a mode or state. Certain processing units, e.g., a VFD, can use these states to determine certain functions, e.g., how a vertex is assembled. As these modes or states can change, GPUs may need to change the corresponding context. Additionally, the workload that corresponds to the mode or state may follow the changing mode or state.

[0042] FIG. 2 illustrates an example GPU 200 in accordance with one or more techniques of this disclosure. As shown in FIG. 2, GPU 200 includes command processor (CP) 210, draw call packets 212, VFD 220, VS 222, vertex cache (VPC) 224, triangle setup engine (TSE) 226, rasterizer (RAS) 228, Z process engine (ZPE) 230, pixel interpolator (PI) 232, fragment shader (FS) 234, render backend (RB) 236, L2 cache (UCHE) 238, and system memory 240. Although FIG. 2 displays that GPU 200 includes processing units 220-238, GPU 200 can include a number of additional processing units. Additionally, processing units 220-238 are merely an example and any combination or order of processing units can be used by GPUs according to the present disclosure. GPU 200 also includes command buffer 250, context register packets 260, and context states 261.

[0043] As shown in FIG. 2, a GPU can utilize a CP, e.g., CP 210, or hardware accelerator to parse a command buffer into context register packets, e.g., context register packets 260, and / or draw call data packets, e.g., draw call packets 212. The CP 210 can then send the context register packets 260 or draw call packets 212 through separate paths to the processing units or blocks in the GPU. Further, the command buffer 250 can alternate different states of context registers and draw calls. For example, a commandbuffer can simultaneously store the following information: context register of context N, draw call(s) of context N, context register of context N+l, and draw call(s) of context N+l.

[0044] GPUs can render images in a variety of different ways. In some instances, GPUs can render an image using direct rendering and / or tiled rendering. In tiled rendering GPUs, an image can be divided or separated into different sections or tiles. After the division of the image, each section or tile can be rendered separately. Tiled rendering GPUs can divide computer graphics images into a grid format, such that each portion of the grid, i.e., a tile, is separately rendered. In some aspects of tiled rendering, during a binning pass, an image can be divided into different bins or tiles. In some aspects, during the binning pass, a visibility stream can be constructed where visible primitives or draw calls can be identified. A rendering pass may be performed after the binning pass. In contrast to tiled rendering, direct rendering does not divide the frame into smaller bins or tiles. Rather, in direct rendering, the entire frame is rendered at a single time (i.e., without a binning pass). Additionally, some types of GPUs can allow for both tiled rendering and direct rendering (e.g., flex rendering).

[0045] In some aspects, GPUs can apply the drawing or rendering process to different bins or tiles. For instance, a GPU can render to one bin, and perform all the draws for the primitives or pixels in the bin. During the process of rendering to a bin, the render targets can be located in GPU internal memory (GMEM). In some instances, after rendering to one bin, the content of the render targets can be moved to a system memory and the GMEM can be freed for rendering the next bin. Additionally, a GPU can render to another bin, and perform the draws for the primitives or pixels in that bin. Therefore, in some aspects, there might be a small number of bins, e.g., four bins, that cover all of the draws in one surface. Further, GPUs can cycle through all of the draws in one bin, but perform the draws for the draw calls that are visible, i.e., draw calls that include visible geometry. In some aspects, a visibility stream can be generated, e.g., in a binning pass, to determine the visibility information of each primitive in an image or scene. For instance, this visibility stream can identify whether a certain primitive is visible or not. In some aspects, this information can be used to remove primitives that are not visible so that the non-visible primitives are not rendered, e.g., in the rendering pass. Also, at least some of the primitives that are identified as visible can be rendered in the rendering pass.

[0046] In some aspects of tiled rendering, there can be multiple processing phases or passes. For instance, the rendering can be performed in two passes, e.g., a binning, a visibility or bin-visibility pass and a rendering or bin-rendering pass. During a visibility pass, a GPU can input a rendering workload, record the positions of the primitives or triangles, and then determine which primitives or triangles fall into which bin or area. In some aspects of a visibility pass, GPUs can also identify or mark the visibility of each primitive or triangle in a visibility stream. During a rendering pass, a GPU can input the visibility stream and process one bin or area at a time. In some aspects, the visibility stream can be analyzed to determine which primitives, or vertices of primitives, are visible or not visible. As such, the primitives, or vertices of primitives, that are visible may be processed. By doing so, GPUs can reduce the unnecessary workload of processing or rendering primitives or triangles that are not visible.

[0047] In some aspects, during a visibility pass, certain types of primitive geometry, e.g., position-only geometry, may be processed. Additionally, depending on the position or location of the primitives or triangles, the primitives may be sorted into different bins or areas. In some instances, sorting primitives or triangles into different bins may be performed by determining visibility information for these primitives or triangles. For example, GPUs may determine or write visibility information of each primitive in each bin or area, e.g., in a system memory. This visibility information can be used to determine or generate a visibility stream. In a rendering pass, the primitives in each bin can be rendered separately. In these instances, the visibility stream can be fetched from memory and used to remove primitives which are not visible for that bin.

[0048] Some aspects of GPUs or GPU architectures can provide a number of different options for rendering, e.g., software rendering and hardware rendering. In software rendering, a driver or CPU can replicate an entire frame geometry by processing each view one time. Additionally, some different states may be changed depending on the view. As such, in software rendering, the software can replicate the entire workload by changing some states that may be utilized to render for each viewpoint in an image. In certain aspects, as GPUs may be submitting the same workload multiple times for each viewpoint in an image, there may be an increased amount of overhead. In hardware rendering, the hardware or GPU may be responsible for replicating or processing the geometry for each viewpoint in an image. Accordingly, the hardwarecan manage the replication or processing of the primitives or triangles for each viewpoint in an image.

[0049] FIG. 3 is a block diagram 300 that illustrates an example display framework including the processing unit 120, the system memory 124, the display processor 127, and the display(s) 131, as may be identified in connection with the device 104.

[0050] A GPU may be included in devices that provide content for visual presentation on a display. For example, the processing unit 120 may include a GPU 310 configured to render graphical data for display on a computing device (e.g., the device 104), which may be a computer workstation, a mobile phone, a smartphone or other smart device, an embedded system, a personal computer, a tablet computer, a video game console, and the like. Operations of the GPU 310 may be controlled based on one or more graphics processing commands provided by a CPU 315. The CPU 315 may be configured to execute multiple applications concurrently. In some cases, each of the concurrently executed multiple applications may utilize the GPU 310 simultaneously. Processing techniques may be performed via the processing unit 120 output a frame over physical or wireless communication channels.

[0051] The system memory 124, which may be executed by the processing unit 120, may include a user space 320 and a kernel space 325. The user space 320 (sometimes referred to as an “application space”) may include software application(s) and / or application framework(s). For example, software application(s) may include operating systems, media applications, graphical applications, workspace applications, etc. Application framework(s) may include frameworks used by one or more software applications, such as libraries, services (e.g., display services, input services, etc.), application program interfaces (APIs), etc. The kernel space 325 may further include a display driver 330. The display driver 330 may be configured to control the display processor 127. For example, the display driver 330 may cause the display processor 127 to compose a frame and transmit the data for the frame to a display.

[0052] The display processor 127 includes a display control block 335 and a display interface 340. The display processor 127 may be configured to manipulate functions of the display(s) 131 (e.g., based on an input received from the display driver 330). The display control block 335 may be further configured to output image frames to the display(s) 131 via the display interface 340. In some examples, the display controlblock 335 may additionally or alternatively perform post-processing of image data provided based on execution of the system memory 124 by the processing unit 120.

[0053] The display interface 340 may be configured to cause the display(s) 131 to display image frames. The display interface 340 may output image data to the display(s) 131 according to an interface protocol, such as, for example, the MIPI DSI (Mobile Industry Processor Interface, Display Serial Interface). That is, the display(s) 131, may be configured in accordance with MIPI DSI standards. The MIPI DSI standard supports a video mode and a command mode. In examples where the display(s) 131 is / are operating in video mode, the display processor 127 may continuously refresh the graphical content of the display(s) 131. For example, the entire graphical content may be refreshed per refresh cycle (e.g., line-by-line). In examples where the display(s) 131 is / are operating in command mode, the display processor 127 may write the graphical content of a frame to a buffer 350.

[0054] In some such examples, the display processor 127 may not continuously refresh the graphical content of the display(s) 131. Instead, the display processor 127 may use a vertical synchronization (Vsync) pulse to coordinate rendering and consuming of graphical content at the buffer 350. For example, when a Vsync pulse is generated, the display processor 127 may output new graphical content to the buffer 350. Thus, generation of the Vsync pulse may indicate that current graphical content has been rendered at the buffer 350.

[0055] Frames are displayed at the display(s) 131 based on a display controller 345, a display client 355, and the buffer 350. The display controller 345 may receive image data from the display interface 340 and store the received image data in the buffer 350. In some examples, the display controller 345 may output the image data stored in the buffer 350 to the display client 355. Thus, the buffer 350 may represent a local memory to the display(s) 131. In some examples, the display controller 345 may output the image data received from the display interface 340 directly to the display client 355.

[0056] The display client 355 may be associated with a touch panel that senses interactions between a user and the display(s) 131. As the user interacts with the display(s) 131, one or more sensors in the touch panel may output signals to the display controller 345 that indicate which of the one or more sensors have sensor activity, a duration of the sensor activity, an applied pressure to the one or more sensor, etc. The displaycontroller 345 may use the sensor outputs to determine a manner in which the user has interacted with the display(s) 131. The display(s) 131 may be further associated with / include other devices, such as a camera, a microphone, and / or a speaker, that operate in connection with the display client 355.

[0057] Some processing techniques of the device 104 may be performed over three stages (e.g., stage 1 : a rendering stage; stage 2: a composition stage; and stage 3: a display / transfer stage). However, other processing techniques may combine the composition stage and the display / transfer stage into a single stage, such that the processing technique may be executed based on two total stages (e.g., stage 1 : the rendering stage; and stage 2: the composition / display / transfer stage). During the rendering stage, the GPU 310 may process a content buffer based on execution of an application that generates content on a pixel-by-pixel basis. During the composition and display stage(s), pixel elements may be assembled to form a frame that is transferred to a physical display panel / subsystem (e.g., the displays 131) that displays the frame.

[0058] Instructions executed by a CPU (e.g., software instructions) or a display processor may cause the CPU or the display processor to search for and / or generate a composition strategy for composing a frame based on a dynamic priority and runtime statistics associated with one or more composition strategy groups. A frame to be displayed by a physical display device, such as a display panel, may include a plurality of layers. Also, composition of the frame may be based on combining the plurality of layers into the frame (e.g., based on a frame buffer). After the plurality of layers are combined into the frame, the frame may be provided to the display panel for display thereon. The process of combining each of the plurality of layers into the frame may be referred to as composition, frame composition, a composition procedure, a composition process, or the like.

[0059] A frame composition procedure or composition strategy may correspond to a technique for composing different layers of the plurality of layers into a single frame. The plurality of layers may be stored in doubled data rate (DDR) memory. Each layer of the plurality of layers may further correspond to a separate buffer. A composer or hardware composer (HWC) associated with a block or function may determine an input of each layer / buffer and perform the frame composition procedure to generate an output indicative of a composed frame. That is, the input may be the layers andthe output may be a frame composition procedure for composing the frame to be displayed on the display panel.

[0060] Some aspects of display processing may utilize different types of mask layers, e.g., a shape mask layer. A mask layer is a layer that may represent a portion of a display or display panel. For instance, an area of a mask layer may correspond to an area of a display, but the entire mask layer may depict a portion of the content that is actually displayed at the display or panel. For example, a mask layer may include a top portion and a bottom portion of a display area, but the middle portion of the mask layer may be empty. In some examples, there may be multiple mask layers to represent different portions of a display area. Also, for certain portions of a display area, the content of different mask layers may overlap with one another. Accordingly, a mask layer may represent a portion of a display area that may or may not overlap with other mask layers.

[0061] FIG. 4 is a diagram 400 illustrating example aspects of augmented reality (AR) in accordance with one or more techniques of this disclosure. Augmented reality (AR) may refer to the augmentation of the real (physical) world with virtual content. AR may be utilized for applications such as room designing / virtual shopping, table top AR games, turn-by-turn navigation assistance, food and health monitoring, AR videos calls, and / or virtual meetings. AR may be performed via a wearable AR device that is capable of (1) mapping the physical world (i.e., the real world), (2) localizing the wearable AR device in the physical world, and (3) positioning / rendering virtual content on a near-eye display visible to the user. Some wearable AR devices may utilize hand / fingertip tracking to allow users to control interfaces in AR.

[0062] In an example, a user 402 may wear a HMD 404 on / over / around eyes of the user 402. In an example, the HMD 404 may be or include the device 104. The HMD 404 may be capable of presenting AR content to the user via display(s) 406. In an example, the display(s) 406 may be or include the display(s) 131. In an example, the display(s) 406 may include a left display corresponding to a left eye of the user 402 and a right display corresponding to a right eye of the user 402, where the left display displays first content to the left eye of the user 402 and the right display displays second content to the right of the user 402. The content may be any appropriate type of content, such as AR content, MR content, or XR content. The term “content” may refer to “graphical content,” an “image,” etc. In an example, the HMD 404 may be XRglasses, a wearable display device (WDD), or a headset. The HMD 404 may include camera(s) 408 that enable the HMD 404 to perceive an environment of the HMD 404, and hence an environment of the user 402. The HMD 404 may also include other sensors (e.g., an inertial measurement unit (IMU), etc.) that enable the HMD 404 to perceive the environment of the user 402.

[0063] In an example, the user 402 may perceive an environment 410 of the user 402 via the display(s) 406 of the HMD 404. In an example, the user 402 may perceive a real world object 412 via the display(s) 406. In one example, the HMD 404 may be XR glasses and the display(s) 406 may include transparent or semi-transparent display surface(s), and hence the user 402 may perceive the real world object 412 without processing performed by the HMD 404. In another example, the HMD 404 may be an HMD and the display(s) 406 may include opaque display surface(s). The HMD 404 may perceive the real world object 412 via the camera(s) 408 and the HMD 404 may present a visual representation (i.e., an image) of the real world object 412 on the display(s). This may be referred to as visual see through content. As the user 402 perceives the environment, the HMD 404 may also present a virtual object 414 to the user 402 via the display(s) 406, where the virtual object 414 may not actually be present in the environment 410.

[0064] FIG. 5 is a diagram 500 illustrating example aspects of split extended reality (XR) head mounted displays (HMDs) in accordance with one or more techniques of this disclosure. Due to a small form-factor utilized in XR HMDs (dictated by fashion, comfort, etc.), thermal constraints may be challenging. For instance, for user comfort, an XR HMD may be relatively lightweight and / or may have relatively small dimensions. The lightweight nature and / or small dimensions of the XR HMD affect an ability of the XR HMD to dissipate heat. Furthermore, the lightweight nature and / or the small dimensions of the XR HMD may cause the XR HMD to have a relatively limited battery life.

[0065] One approach to reduce power consumption in an XR HMD is to split processing between the HMD and a companion device (e.g., a puck or a cellphone). This may be referred to as a “split design.” There may be several important considerations in split designs. In some split design configurations, rendering (e.g., a high-power consumption workload) may be performed on the companion device; however, this may entail performing a late-stage reprojection (LSR) on the XR HMD (e.g., XRglasses). LSR may refer to reprojecting a previously-rendered frame based on a latest head pose of a user in order to reduce a motion-to-photon latency and avoid user nausea. Perception workloads (hand tracking, head tracking, body tracking, 3D reconstructions, etc.) may be performed either on the XR HMD or the companion device depending on latency / power characteristics.

[0066] In an example, an XR HMD 502 may be configured in a split rendering configuration with a companion device 504. In an example, the XR HMD 502 may be or include the device 104 or the HMD 404. In an example, the XR HMD 502 may be or include XR glasses. In an example, the companion device 504 may be or include the device 104. In an example, the companion device 504 may be or include a smartphone, a tablet, a puck, a video game console, a server, a cloud server, a desktop computing device, a laptop computing device, etc. The companion device 504 may include first processing capabilities and the XR HMD 502 may include second processing capabilities, where the first processing capabilities may be greater than the second processing capabilities. For instance, the companion device 504 may include faster processor(s), a greater amount of memory, etc., compared to processor(s), memory, etc. of the XR HMD 502. In an example, the companion device 504 may include a greater amount of battery life compared to a battery life of the XR HMD 502.

[0067] The XR HMD 502 may include a camera 506 and a display panel 508. In an example, the camera 506 may be or include the camera(s) 408 and the display panel 508 may be or include the display(s) 131 or the display(s) 406. The XR HMD 502 may also include an inertial measurement unit (IMU, not depicted in FIG. 5). The XR HMD 502 may perceive surrounding of the XR HMD 502 via the camera 506 and / or the IMU. The XR HMD 502 may present content (e.g., XR content) to a user via the display panel 508. The XR HMD 502 may include a display processing unit (DPU) (e.g., DPU 510). In an example, the DPU 510 may be or include the display processor 127. The XR HMD 502 may be configured to determine a six degrees-of-freedom (6DOF) pose 512 of a head of a user of the XR HMD 502 based on data generated by the IMU. The 6DOF pose 512 may include position information (surge, heave, sway) and orientation information (roll, pitch, yaw) of the head of the user as the user wears the XR HMD 502. The XR HMD 502 may also include client-side AR application(s) (not depicted in FIG. 5). In contrast, a three degrees-of-freedom (3DOF) pose mayinclude orientation information (roll, pitch, yaw) without including position information (surge, heave, sway).

[0068] The XR HMD 502 may be configured to perform a split perception encode 514 on the 6DOF pose 512 (or other data). The XR HMD 502 may transmit encoded information (e.g., the (encoded) 6DOF pose 512) to the companion device 504 via a link 516. In an example, the link 516 may be a wired link or a wireless link. In a specific example, the link 516 may be or include a wireless local area network (WLAN) link, such as an Institute of Electrical and Electronics Engineers (IEEE) 802.1 lax 6GHz link. In another example, the link 516 may be a 5G New Radio (5G NR) link.

[0069] The companion device 504 may receive the encoded information via the link 516 and the companion device 504 may perform a split perception decode 518 on the encoded information to decode the encoded information. In an example, the split perception decode 518 may reproduce the 6DOF pose 512 on the companion device 504. The companion device 504, at 520, may perform hand tracking (HaT), plane finding (PlaneF), and / or image tracking (IT) / object tracking (OT). Hand tracking may identify and localize a user’s hands for user interface (UI) purposes. Plane finding may identify and localize planes (e.g., desk, walls, etc.) in the environment such that virtual content can be positioned on the planes. Image tracking / object tracking may identify and localize images (e.g., quick response (QR) codes) or objects (e.g., game pieces, controllers, etc.) for interactivity with real -world objects.

[0070] The companion device 504 may include AR application(s) 522 and a software developer kit (SDK) 524. The SDK 524 may include a collection of software development tools in an installable package. The SDK 524 may facilitate the creation of application(s) (e.g., the AR application(s) 522) by including a compiler, a debugger, and / or a software framework. The SDK 524 may be specific to a hardware platform and / or an operating system of the companion device 504. The companion device 504 may perform a render 526 (e.g., render AR content) via the AR application(s) 522 and / or the SDK 524 based on the (decoded) 6DOF pose 512. The companion device 504 may perform an encode 528 on the rendered AR content. Then companion device 504 may transmit the (encoded) rendered AR content to the XR HMD 502 via the link 516.

[0071] The XR HMD 502 may receive the (encoded) rendered AR content from the companion device 504. The XR HMD 502 may perform a decode 530 on the(encoded) rendered AR content. The XR HMD 502 may perform a warp 532 on the (decoded) rendered AR content. The XR HMD 502 may present the (warped and decoded) rendered AR content on the display panel 508.

[0072] FIG. 6 is a diagram 600 illustrating example aspects of a split XR system in accordance with one or more techniques of this disclosure. In a split XR system, an HMD (e.g., the XR HMD 502) may operate in a standalone mode as well as with a companion device (e.g., a phone or a server). Table 1 below illustrates modes of interest.Table 1: Modes of Interest

[0073] Dynamically switching between modes of interest may presents problem for XR applications. In a first example 602, an XR device (e.g., the HMD 404, the XR HMD 502, smart glasses, etc.) may switch from a 3DOF mode 604 (i.e., 3DOF tracking) to a 6DOF mode 606 (i.e., 6DOF tracking). 3DOF may refer to a 3 rotational axis, which may allow turning left / right, looking up / down, and tilting the view. 6DOF may additionally include 3 translational degrees (in addition to 3DOF) that allow moving to the left / right, forwards / backwards, and upwards / downwards. In the first example 602, a user (e.g., the user 402) may be using a head-locked smart-glasses application (e.g., a navigation application) on the XR device in standalone mode when the user returns home. The standalone mode (e.g., a single XR viewer mode) may be associated with a head-locked rendering mode (i.e., a rendering mode where head movement is locked). The home of the user may include a companion device (e.g., the companion device 504). Ahead-locked smart-glasses application may connect to the companion device and switch to a companion mode (e.g., a split XR viewer mode). The companion mode may be associated with a world-locked rendering mode (i.e., a rendering mode where world movement is locked). However, in order to switch fromthe standalone mode to the companion mode, the head-locked smart-glasses application may restart, which may affect an experience of the user.

[0074] In a second example 608, an XR device (e.g., the HMD 404, the XR HMD 502, smart glasses, etc.) may switch from the 6DOF mode 606 (i.e., 6DOF tracking) to the 3DOF mode 604 (i.e., 3DOF tracking). In the second example 608, a user may be at home (where a WLAN companion device (e.g., the companion device 504) is located). The user may be using an AR viewer application on the XR device that is world-locked. For instance, the user may be watching television on a wall of the home via the XR device. The user may also decide to go for a run. The XR device may switch to a head-locked content mode in which content rendered on the XR device. However, in order to switch to the aforementioned mode, the AR viewer application may restart, which may affect an experience of the user.

[0075] FIG. 7 is a diagram 700 illustrating example aspects of transitioning from a standalone mode to a companion mode in a split XR system in accordance with one or more techniques of this disclosure. In one aspect, applications may be structured into two portions: a “simple application” which may be rendered from an HMD as one or more 2D planes and a “rich” application which may be rendered from a companion device in a fully 3D manner. The simple portion of the application may be rendered from the HMD and therefore may be able to smoothly transition between being rendered as a head-locked layer on the HMD and being warped and composited (on the HMD) into a prescribed plane as part of the rich application enabled by the companion. Aspects presented herein may relate to transitions between two modes that may be triggered manually or automatically (upon companion device pairing). When paired, some data may be passed between the simple application render and the rich application render to keep the applications synchronized with one another. When the HMD operates in a standalone mode, the HMD takes over the application rendering entirely.

[0076] In an example, an HMD 702 may be operating in a companion mode 704 with a companion device 706. In an example, the HMD 702 may be or include the device 104, the HMD 404, or the XR HMD 502. In an example, the companion device 706 may be or include the device 104 or the companion device 504.

[0077] The HMD 702 may include a first application 708 (i.e., a “simple application”) and the companion device 706 may include a second application 710 (i.e., a “richapplication”). The first application 708 and the second application 710 may exchange synchronization data 712 that enables the first application 708 and the second application 710 to synchronize with one another for rendering purposes. Synchronization data may refer to data that is used to keep local and remote applications in synchronization, such as user interactions (e.g., button presses) and currently-displayed screens (e.g., menus).

[0078] The first application 708 may perform a first render 714. In an example, the first render 714 may include rendering two-dimensional (2D) plane(s). In an example, the first render 714 may correspond to a head-locked rendering mode. The first application 708 may perform the first render 714 regardless of whether or not the first application 708 is operating in the companion mode 704. The second application 710 may perform a second render 716. In an example, the second render 716 may include rendering in a fully 3D manner. In an example, the second render 716 may correspond to a world-locked rendering mode. The second application 710 may transmit (e.g., via the link 516) a world-locked anchor point 718 in a prescribed plane to the HMD 702 based on the second render 716. The second application 710 may also transmit (e.g., via the link 516) content (i.e., second content) rendered by the second render 716 to the HMD 702. The HMD 702 may perform a warp 720 based on the first content rendered by the first render 714 and the world-locked anchor point 718. The warp 720 may generate warped content (e.g., a warped frame). Warping may transform (e.g., scale, rotate, project, etc.) content such that it appears to be locked to a particular anchor point.

[0079] The second application 710 may also generate content eye buffers 722 based on the second render 716. The second application 710 may transmit the content eye buffers 722 to the HMD 702. In an example, the content eye buffers 722 may include a left eye buffer for a left display of the HMD 702 and a right eye buffer for a right display of the HMD 702. The HMD 702 may perform a composition 724 based on (1) the warped content generated by the warp 720 and (2) the content eye buffers 722. The HMD 702 may perform an LSR 726 on the (composited) content eye buffers 722. The HMD 702 may then present the content eye buffers 722 on display(s), such as the display(s) 406. The composition process may refer to generating a composite image from multiple images by blending the two images with an explicit z-order.

[0080] In another example, an HMD 702 may be operating in a standalone mode 728. In the standalone mode 728, the first application 708 may perform the first render 714 as described above. In the standalone mode 728, the HMD 702 may display content without assistance from the companion device 706.

[0081] The HMD 702 may transition between the companion mode 704 and the standalone mode 728 either automatically (e.g., based on the companion device 706 being available to the HMD 702 or manually (e.g., via user input). In one aspect, the HMD 702 may transition between the companion mode 704 and the standalone mode 728 without exiting out of or restarting the first application 708.

[0082] FIG. 8 is a diagram 800 illustrating example aspects of data gathering in accordance with one or more techniques of this disclosure. When an XR device enters standalone mode, the XR device may continue to gather and buffer up perception data (even if the perception data is not processed or used by a “simple application” executing on the XR device) such that a “rich application” experience may be improved upon the XR device re-pairing with a companion device. In an example, the XR device may continue to gather and search for 6DOF keyframes and / or three-dimensional reconstruction (3DR) keyframes, even when the XR device is not actively running 6DOF algorithms and / or 3DR algorithms. When the XR device re-pairs with the companion device (e.g., a phone), the XR device may not have to wait for re-mapping or 3DR to catch up in a rendering process.

[0083] In an example, the HMD 702 may include sensor(s) 802 (e.g., camera(s)) that enable the HMD 702 to perceive an environment 804 of the HMD 702. The HMD 702 may enter the standalone mode 728. The HMD 702 may collect perception data 806 via the sensor(s) 802 when the HMD 702 is operating in the standalone mode 728, even when the first application 708 is not processing or otherwise utilize the perception data 806. In an example, the perception data 806 may include 6DOF keyframes, 3DR key frames, digests of IMU data, and / or head poses. The HMD 702 may store the perception data 806 in a buffer 810. When the HMD 702 enters the companion mode 704, the HMD 702 may utilize the perception data 806 in the buffer 810 to facilitate the display of content.

[0084] FIG. 9 is a communication flow diagram 900 illustrating example communications between a wearable display device (WDD) 902 and a companion device 904 in accordance with one or more techniques of this disclosure. In an example, the WDD902 may be or include the device 104, the HMD 404, the XR HMD 502, and / or the HMD 702. In an example, the companion device 904 may be or include the device 104, the companion device 504, and / or the companion device 706.

[0085] At 906, the WDD 902 may render, at a wearable display device (e.g., the WDD 902), first content based on a first set of characteristics associated with a standalone mode associated with the wearable display device. At 916, the WDD 902 may obtain an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device. At 920, the WDD 902 may receive, from a companion device (e.g., the companion device 904) and based on the indication, second rendered content based on a second set of characteristics associated with the companion mode. At 922, the WDD 902 may process the first rendered content and the second rendered content. At 924, the WDD 902 may configure a combined display buffer based on the processed first rendered content and the processed second rendered content. The display buffer may refer to a buffer that temporarily stores content that is ready for display.

[0086] At 918, the WDD 902 may transmit synchronization data for an application executed on the wearable display device, where receiving the second rendered content at 920 may include receiving the second rendered content further based on the synchronization data. At 912, the WDD 902 may pair the wearable display device with the companion device, where the indication that the wearable display device is to be switched to the companion mode may be obtained subsequent to the pairing. At 914, the WDD 902 may receive, at the wearable display device, user input, where the indication that the wearable display device is to be switched to the companion mode may be obtained based on the user input.

[0087] At 910, the WDD 902 may output, prior to the obtainment of the indication, the third content for display. At 926, the WDD 902 may output, subsequent to the obtainment of the indication, content for display, where the content may be based upon the second content and the fourth content.

[0088] At 928, the WDD 902 may obtain, subsequent to the processing, a second indication that the wearable display device is to be switched to the standalone mode. At 930, the WDD 902 may render, based on the second indication, third content based on the first set of characteristics associated with the standalone mode. At 908, the WDD 902 may collect, prior to the obtainment of the indication and as the wearable displaydevice operates in the standalone mode, data associated with the wearable display device, where processing the first rendered content and the second rendered content at 922 may be further based on the data.

[0089] FIG. 10 is a flowchart 1000 of an example method of graphics processing in accordance with one or more techniques of this disclosure. The method may be performed by an apparatus, such as an apparatus for graphics processing, a GPU, a CPU, a wearable display device (e.g., the HMD 404, the WDD 902), the XR HMD 502, the HMD 702, the device 104, a wireless communication device, and the like, as used in connection with the aspects of FIGs. 1-9. In an example, the method may be performed by the content migrator 198.

[0090] At 1002, the apparatus (e.g., a wearable display device) renders, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associated with the wearable display device. For example, FIG. 9 at 906 shows that the WDD 902 may render, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associated with the wearable display device. In an example, the wearable display device may be the device 104, the HMD 404, the WDD 902, the XR HMD 502, or the HMD 702. In an example, the standalone mode may be the standalone mode 728. In an example, rendering the first content may correspond to the first render 714. In an example, the first set of characteristics may be associated with the standalone smart glasses mode in Table 1 above. In an example, 1002 may be performed by the content migrator 198.

[0091] At 1004, the apparatus (e.g., a wearable display device) obtains an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device. For example, FIG. 9 at 916 shows that the WDD 902 may obtain an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device. In an example, the companion mode may be the companion mode 704. In an example, the switch may be associated with FIG. 6. In an example, 1004 may be performed by the content migrator 198.

[0092] At 1006, the apparatus (e.g., a wearable display device) receives, from a companion device and based on the indication, second rendered content based on a second set of characteristics associated with the companion mode. For example, FIG. 9 at 920 shows that the WDD 902 may receive, from a companion device and based on theindication, second rendered content based on a second set of characteristics associated with the companion mode. In an example, the companion device may be or include the device 104, the companion device 504, and / or the companion device 706. In an example, the second rendered content may correspond to the second render 716. In an example, the second set of characteristics may be associated with Split XR Viewer Mode in Table 1 above. In an example, 1006 may be performed by the content migrator 198.

[0093] At 1008, the apparatus (e.g., a wearable display device) processes the first rendered content and the second rendered content. For example, FIG. 9 at 922 shows that the WDD 902 may apparatus process the first rendered content and the second rendered content. In an example, processing first rendered content and the second rendered content may correspond to the warp 720, the composition 724, and / or the LSR 726. In an example, 1008 may be performed by the content migrator 198.

[0094] At 1010, the apparatus (e.g., awearable display device) configures a combined display buffer based on the processed first rendered content and the processed second rendered content. For example, FIG. 9 at 924 shows that the WDD 902 may configure a combined display buffer based on the processed first rendered content and the processed second rendered content. In an example, the combined display buffer may be associated with the content eye buffers 722. In an example, 1010 may be performed by the content migrator 198.

[0095] FIG. 11 is a flowchart 1100 of an example method of graphics processing in accordance with one or more techniques of this disclosure. The method may be performed by an apparatus, such as an apparatus for graphics processing, a GPU, a CPU, a wearable display device (e.g., the HMD 404, the WDD 902), the XR HMD 502, the HMD 702, the device 104, a wireless communication device, and the like, as used in connection with the aspects of FIGs. 1-9. In an example, the method (including the various aspects detailed below) may be performed by the content migrator 198.

[0096] At 1102, the apparatus (e.g., a wearable display device) renders, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associated with the wearable display device. For example, FIG. 9 at 906 shows that the WDD 902 may render, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associated with thewearable display device. In an example, the wearable display device may be the device 104, the HMD 404, the WDD 902, the XR HMD 502, or the HMD 702. In an example, the standalone mode may be the standalone mode 728. In an example, rendering the first content may correspond to the first render 714. In an example, the first set of characteristics may be associated with the Standalone Smart Glasses Mode in Table 1 above. In an example, 1102 may be performed by the content migrator 198.

[0097] At 1112, the apparatus (e.g., a wearable display device) obtains an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device. For example, FIG. 9 at 916 shows that the WDD 902 may obtain an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device. In an example, the companion mode may be the companion mode 704. In an example, the switch may be associated with FIG. 6. In an example, 1112 may be performed by the content migrator 198.

[0098] At 1116, the apparatus (e.g., a wearable display device) receives, from a companion device and based on the indication, second rendered content based on a second set of characteristics associated with the companion mode. For example, FIG. 9 at 920 shows that the WDD 902 may receive, from a companion device and based on the indication, second rendered content based on a second set of characteristics associated with the companion mode. In an example, the companion device may be or include the device 104, the companion device 504, and / or the companion device 706. In an example, the second rendered content may correspond to the second render 716. In an example, the second set of characteristics may be associated with Split XR Viewer Mode in Table 1 above. In an example, 1116 may be performed by the content migrator 198.

[0099] At 1118, the apparatus (e.g., a wearable display device) processes the first rendered content and the second rendered content. For example, FIG. 9 at 922 shows that the WDD 902 may apparatus process the first rendered content and the second rendered content. In an example, processing first rendered content and the second rendered content may correspond to the warp 720, the composition 724, and / or the LSR 726. In an example, 1118 may be performed by the content migrator 198.

[0100] At 1120, the apparatus (e.g., a wearable display device) configures a combined display buffer based on the processed first rendered content and the processed secondrendered content. For example, FIG. 9 at 924 shows that the WDD 902 may configure a combined display buffer based on the processed first rendered content and the processed second rendered content. In an example, the combined display buffer may be associated with the content eye buffers 722. In an example, 1120 may be performed by the content migrator 198.

[0101] In one aspect, the first set of characteristics may include three degrees of freedom (3DOF) tracking, and the second set of characteristics may include six degrees of freedom (6DOF) tracking. For example, the 3DOF tracking may correspond to the 3DOF mode 604 and the 6DOF tracking may correspond to the 6DOF mode 606.

[0102] In one aspect, the first set of characteristics may include a head-locked rendering mode, and the second set of characteristics may include a world-locked rendering mode. For example, the head-locked rendering may be the head-locked rendering in Table 1 above and the world-locked rendering mode may be the world-locked rendering mode in Table 1 above.

[0103] In one aspect, rendering the first content may include rendering at least one first two- dimensional (2D) plane, and the second rendered content may include at least one second 2D plane or a three-dimensional (3D) scene. For example, rendering the first content at 906 may include rendering at least one first two-dimensional (2D) plane, and the second rendered content (received at 920) may include at least one second 2D plane or a three-dimensional (3D) scene.

[0104] In one aspect, at 1114, the apparatus (e.g., a wearable display device) may transmit synchronization data for an application executed on the wearable display device, where receiving the second rendered content may include receiving the second rendered content further based on the synchronization data. For example, FIG. 9 at 918 shows that the WDD 902 may transmit synchronization data for an application executed on the wearable display device, where receiving the second rendered content at 920 may include receiving the second rendered content further based on the synchronization data. In an example, the synchronization data may be or include the synchronization data 712. In an example, the application may be or include the first application 708. In an example, 1114 may be performed by the content migrator 198.

[0105] In one aspect, at 1108, the apparatus (e.g., a wearable display device) may pair the wearable display device with the companion device, where the indication that the wearable display device is to be switched to the companion mode may be obtainedsubsequent to the pairing. For example, FIG. 9 at 912 shows that the WDD 902 may pair the wearable display device with the companion device, where the indication that the wearable display device is to be switched to the companion mode at 916 may be obtained subsequent to the pairing. In an example, 1108 may be performed by the content migrator 198.

[0106] In one aspect, at 1110, the apparatus (e.g., a wearable display device) may receive, at the wearable display device, user input, where the indication that the wearable display device is to be switched to the companion mode may be obtained based on the user input. For example, FIG. 9 at 914 shows that the WDD 902 may receive, at the wearable display device, user input, where the indication that the wearable display device is to be switched to the companion mode at 916 may be obtained based on the user input. In an example, 1110 may be performed by the content migrator 198.

[0107] In one aspect, processing the first rendered content and the second rendered content may include performing at least one of: a warping on the first rendered content and the second rendered content, a composition of the first rendered content and the second rendered content, or a late stage reprojection (LSR) on the first rendered content and the second rendered content. For example, processing the first rendered content and the second rendered content at 922 may include performing at least one of: a warping on the first rendered content and the second rendered content, a composition of the first rendered content and the second rendered content, or a late stage reprojection (LSR) on the first rendered content and the second rendered content. In an example, the warping may correspond to the warp 720, the composition may correspond to the composition 724, and the LSR may correspond to the LSR 726.

[0108] In one aspect, an application may be executed at the wearable display device, and where rendering the first content, obtaining the indication, receiving the second rendered content, processing the first rendered content and the second rendered content, and configuring the combined display buffer may occur without the application being restarted or shutdown. For example, the application may be the first application 708. In an example, rendering the first content at 906, obtaining the indication at 916, receiving the second rendered content at 920, processing the first rendered content and the second rendered content at 922, and configuring the combined display buffer at 924 may occur without the first application 708 being restarted or shutdown.

[0109] In one aspect, rendering the first content based on the first set of characteristics associated with the standalone mode may include: rendering, at a first time instance, third content; and rendering, at a second time instance, fourth content, where the first time instance occurs prior to the obtainment of the indication, and where the second time instance occurs subsequent to the obtainment of the indication. For example, rendering the first content based on the first set of characteristics associated with the standalone mode at 906 may include: rendering, at a first time instance, third content; and rendering, at a second time instance, fourth content, where the first time instance occurs prior to the obtainment of the indication at 916, and where the second time instance occurs subsequent to the obtainment of the indication.

[0110] In one aspect, at 1106, the apparatus (e.g., a wearable display device) may output, prior to the obtainment of the indication, the third content for display. For example, FIG. 9 at 910 shows that the WDD 902 may output, prior to the obtainment of the indication at 916, the third content for display. In an example, 1106 may be performed by the content migrator 198.[OHl] In one aspect, at 1122, the apparatus (e.g., a wearable display device) may output, subsequent to the obtainment of the indication, content for display, where the content may be based upon the second content and the fourth content. For example, FIG. 9 at 926 shows that the WDD 902 may output, subsequent to the obtainment of the indication at 916, content for display, where the content may be based upon the second content and the fourth content. In an example, 1122 may be performed by the content migrator 198.

[0112] In one aspect, at 1124, the apparatus (e.g., a wearable display device) may obtain, subsequent to the processing, a second indication that the wearable display device is to be switched to the standalone mode. For example, FIG. 9 at 928 shows that the WDD 902 may obtain, subsequent to the processing at 922, a second indication that the wearable display device is to be switched to the standalone mode. In an example, 1124 may be performed by the content migrator 198.

[0113] In one aspect, at 1126, the apparatus (e.g., a wearable display device) may render, based on the second indication, third content based on the first set of characteristics associated with the standalone mode. For example, FIG. 9 at 930 shows that the WDD 902 may render, based on the second indication, third content based on the first set ofcharacteristics associated with the standalone mode. In an example, 1126 may be performed by the content migrator 198.

[0114] In one aspect, the wearable display device may operate without exchanging data with the companion device when the wearable display device operates in the standalone mode, and the wearable display device may exchange the data with the companion device when the wearable display operates in the companion mode. For example, the WDD 902 may operate without exchanging data with the companion device 904 when the WDD 902 operates in the standalone mode 728, and the WDD 902 may exchange the data with the companion device 904 when the WDD 902 operates in the companion mode 704.

[0115] In one aspect, at 1104, the apparatus (e.g., a wearable display device) may collect, prior to the obtainment of the indication and as the wearable display device operates in the standalone mode, data associated with the wearable display device, where processing the first rendered content and the second rendered content may be further based on the data. For example, FIG. 9 at 908 shows that the WDD 902 may collect, prior to the obtainment of the indication at 916 and as the wearable display device operates in the standalone mode, data associated with the wearable display device, where processing the first rendered content and the second rendered content at 922 may be further based on the data. In an example, 1104 may be performed by the content migrator 198.

[0116] In one aspect, the data may include perception data. For example, the perception data may be or include the perception data 806.

[0117] In configurations, a method or an apparatus for graphics processing is provided. The apparatus may be a GPU, a CPU, or some other processor that may perform graphics processing. In aspects, the apparatus may be the processing unit 120 within the device 104, or may be some other hardware within the device 104 or another device. The apparatus (e.g., the processing unit 120) may include means for rendering, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associated with the wearable display device. The apparatus (e.g., the processing unit 120) may further include means for obtaining an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device. The apparatus (e.g., the processing unit 120) may include means for receiving, from a companion device and based on the indication,second rendered content based on a second set of characteristics associated with the companion mode. The apparatus (e.g., the processing unit 120) may include means for processing the first rendered content and the second rendered content. The apparatus (e.g., the processing unit 120) may include means for configuring a combined display buffer based on the processed first rendered content and the processed second rendered content. The apparatus (e.g., the processing unit 120) may include means for transmitting synchronization data for an application executed on the wearable display device, where receiving the second rendered content includes receiving the second rendered content further based on the synchronization data. The apparatus (e.g., the processing unit 120) may include means for pairing the wearable display device with the companion device, where the indication that the wearable display device is to be switched to the companion mode is obtained subsequent to the pairing. The apparatus (e.g., the processing unit 120) may include means for receiving, at the wearable display device, user input, where the indication that the wearable display device is to be switched to the companion mode is obtained based on the user input. The apparatus (e.g., the processing unit 120) may include means for outputting, prior to the obtainment of the indication, the third content for display. The apparatus (e.g., the processing unit 120) may include means for outputting, subsequent to the obtainment of the indication, content for display, where the content is based upon the second content and the fourth content. The apparatus (e.g., the processing unit 120) may include means for obtaining, subsequent to the processing, a second indication that the wearable display device is to be switched to the standalone mode. The apparatus (e.g., the processing unit 120) may include means for rendering, based on the second indication, third content based on the first set of characteristics associated with the standalone mode. The apparatus (e.g., the processing unit 120) may include means for collecting, prior to the obtainment of the indication and as the wearable display device operates in the standalone mode, data associated with the wearable display device, where processing the first rendered content and the second rendered content is further based on the data.

[0118] It is understood that the specific order or hierarchy of blocks / steps in the processes, flowcharts, and / or call flow diagrams disclosed herein is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of the blocks / steps in the processes, flowcharts, and / or call flow diagramsmay be rearranged. Further, some blocks / steps may be combined and / or omitted. Other blocks / steps may also be added. The accompanying method claims present elements of the various blocks / steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[0119] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, where reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0120] Unless specifically stated otherwise, the term “some” refers to one or more and the term “or” may be interpreted as “and / or” where context does not dictate otherwise. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”

[0121] In one or more examples, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. For example, although the term “processing unit” has been used throughout this disclosure, such processing units may be implemented in hardware, software, firmware, or any combination thereof. If any function, processing unit, technique described herein, or other module is implemented in software, the function, processing unit, technique described herein, or other module may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.

[0122] Computer-readable media may include computer data storage media or communication media including any medium that facilitates transfer of a computer program from one place to another. In this manner, computer-readable media generally may correspond to: (1) tangible computer-readable storage media, which is non-transitory; or (2) a communication medium such as a signal or carrier wave. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code, and / or data structures for implementation of the techniques described in this disclosure. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, compact disc-read only memory (CD-ROM), or other optical disk storage, magnetic disk storage, or other magnetic storage devices. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks usually reproduce data magnetically, while discs usually reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. A computer program product may include a computer-readable medium.

[0123] The techniques of this disclosure may be implemented in a wide variety of devices or apparatuses, including a wireless handset, an integrated circuit (IC) or a set of ICs, e.g., a chip set. Various components, modules or units are described in this disclosure to emphasize functional aspects of devices configured to perform the disclosed techniques, but do not necessarily need realization by different hardware units. Rather, as described above, various units may be combined in any hardware unit or provided by a collection of inter-operative hardware units, including one or more processors as described above, in conjunction with suitable software and / or firmware. Accordingly, the term “processor,” as used herein may refer to any of the foregoingstructure or any other structure suitable for implementation of the techniques described herein. Also, the techniques may be fully implemented in one or more circuits or logic elements.

[0124] Aspect 1 is a method of graphics processing, including: rendering, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associated with the wearable display device; obtaining an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device; receiving, from a companion device and based on the indication, second rendered content based on a second set of characteristics associated with the companion mode; processing the first rendered content and the second rendered content; and configuring a combined display buffer based on the processed first rendered content and the processed second rendered content.

[0125] Aspect 2 may be combined with aspect 1, wherein the first set of characteristics includes three degrees of freedom (3DOF) tracking, and wherein the second set of characteristics includes six degrees of freedom (6DOF) tracking.

[0126] Aspect 3 may be combined with any of aspects 1-2, wherein the first set of characteristics includes a head-locked rendering mode, and wherein the second set of characteristics includes a world-locked rendering mode.

[0127] Aspect 4 may be combined with any of aspects 1-3, wherein rendering the first content includes rendering at least one first two-dimensional (2D) plane, and wherein the second rendered content includes at least one second 2D plane or a three-dimensional (3D) scene.

[0128] Aspect 5 may be combined with any of aspects 1-4, further including: transmitting synchronization data for an application executed on the wearable display device, wherein receiving the second rendered content includes receiving the second rendered content further based on the synchronization data.

[0129] Aspect 6 may be combined with any of aspects 1-5, further including: pairing the wearable display device with the companion device, wherein the indication that the wearable display device is to be switched to the companion mode is obtained subsequent to the pairing.

[0130] Aspect 7 may be combined with any of aspects 1-6, further including: receiving, at the wearable display device, user input, wherein the indication that the wearabledisplay device is to be switched to the companion mode is obtained based on the user input.

[0131] Aspect 8 may be combined with any of aspects 1-7, wherein processing the first rendered content and the second rendered content includes performing at least one of: a warping on the first rendered content and the second rendered content, a composition of the first rendered content and the second rendered content, or a late stage reprojection (LSR) on the first rendered content and the second rendered content.

[0132] Aspect 9 may be combined with any of aspects 1-8, wherein an application is executed at the wearable display device, and wherein rendering the first content, obtaining the indication, receiving the second rendered content, processing the first rendered content and the second rendered content, and configuring the combined display buffer occur without the application being restarted or shutdown.

[0133] Aspect 10 may be combined with any of aspects 1-9, wherein rendering the first content based on the first set of characteristics associated with the standalone mode includes: rendering, at a first time instance, third content; and rendering, at a second time instance, fourth content, wherein the first time instance occurs prior to the obtainment of the indication, and wherein the second time instance occurs subsequent to the obtainment of the indication.

[0134] Aspect 11 may be combined with aspect 10, further including: outputting, prior to the obtainment of the indication, the third content for display; and outputting, subsequent to the obtainment of the indication, content for display, wherein the content is based upon the second content and the fourth content.

[0135] Aspect 12 may be combined with any of aspects 1-11, further including: obtaining, subsequent to the processing, a second indication that the wearable display device is to be switched to the standalone mode; and rendering, based on the second indication, third content based on the first set of characteristics associated with the standalone mode.

[0136] Aspect 13 may be combined with any of aspects 1-12, wherein the wearable display device operates without exchanging data with the companion device when the wearable display device operates in the standalone mode, and wherein the wearable display device exchanges data with the companion device when the wearable display device operates in the companion mode.

[0137] Aspect 14 may be combined with any of aspects 1-13, further including: collecting, prior to the obtainment of the indication and as the wearable display device operates in the standalone mode, data associated with the wearable display device, wherein processing the first rendered content and the second rendered content is further based on the data.

[0138] Aspect 15 may be combined with aspect 14, wherein the data includes perception data.

[0139] Aspect 16 is an apparatus for graphics processing including a processor coupled to a memory and, based on information stored in the memory, the processor is configured to implement a method as in any of aspects 1-15.

[0140] Aspect 17 may be combined with aspect 16 and includes that the apparatus is a wireless communication device comprising at least one of a transceiver or an antenna coupled to the processor, wherein to receive the second rendered content, the processor is configured to receive the second rendered content via at least one of the transceiver or the antenna.

[0141] Aspect 18 is an apparatus for graphics processing including means for implementing a method as in any of aspects 1-15.

[0142] Aspect 19 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, the computer executable code, when executed by a processor, causes the processor to implement a method as in any of aspects 1-15.

[0143] Various aspects have been described herein. These and other aspects are within the scope of the following claims.

Claims

CLAIMSWHAT IS CLAIMED IS:

1. An apparatus for graphics processing, comprising: a memory; and a processor coupled to the memory and, based on information stored in the memory, the processor is configured to: render, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associated with the wearable display device; obtain an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device; receive, from a companion device and based on the indication, second rendered content based on a second set of characteristics associated with the companion mode; process the first rendered content and the second rendered content; and configure a combined display buffer based on the processed first rendered content and the processed second rendered content.

2. The apparatus of claim 1, wherein the first set of characteristics includes three degrees of freedom (3DOF) tracking, and wherein the second set of characteristics includes six degrees of freedom (6DOF) tracking.

3. The apparatus of claim 1, wherein the first set of characteristics includes a head- locked rendering mode, and wherein the second set of characteristics includes a world- locked rendering mode.

4. The apparatus of claim 1, wherein to render the first content, the processor is configured to render at least one first two-dimensional (2D) plane, and wherein the second rendered content comprises at least one second 2D plane or a three-dimensional (3D) scene.

5. The apparatus of claim 1, wherein the processor is further configured to:transmit synchronization data for an application executed on the wearable display device, wherein to receive the second rendered content, the processor is configured to receive the second rendered content further based on the synchronization data.

6. The apparatus of claim 1, wherein the processor is further configured to: pair the wearable display device with the companion device, wherein the processor is configured to obtain the indication that the wearable display device is to be switched to the companion mode subsequent to the pairing.

7. The apparatus of claim 1, wherein the processor is further configured to: receive, at the wearable display device, user input, wherein to obtain the indication that the wearable display device is to be switched to the companion mode, the processor is configured to obtain the indication that the wearable display device is to be switched to the companion mode based on the user input.

8. The apparatus of claim 1, wherein to process the first rendered content and the second rendered content, the processor is configured to perform at least one of: a warping on the first rendered content and the second rendered content, a composition of the first rendered content and the second rendered content, or a late stage reprojection (LSR) on the first rendered content and the second rendered content.

9. The apparatus of claim 1, wherein an application is executed at the wearable display device, and wherein to render the first content, obtain the indication, receive the second rendered content, process the first rendered content and the second rendered content, and configure the combined display buffer, the processor is configured to render the first content, obtain the indication, receive the second rendered content, process the first rendered content and the second rendered content, and configure the combined display buffer without the application being restarted or shutdown.

10. The apparatus of claim 1, wherein to render the first content based on the first set of characteristics associated with the standalone mode, the processor is configured to: render, at a first time instance, third content; andrender, at a second time instance, fourth content, wherein the first time instance occurs prior to the obtainment of the indication, and wherein the second time instance occurs subsequent to the obtainment of the indication.

11. The apparatus of claim 10, wherein the processor is further configured to: output, prior to the obtainment of the indication, the third content for display; and output, subsequent to the obtainment of the indication, content for display, wherein the content is based upon the second content and the fourth content.

12. The apparatus of claim 1, wherein the processor is further configured to: obtain, subsequent to the processing, a second indication that the wearable display device is to be switched to the standalone mode; and render, based on the second indication, third content based on the first set of characteristics associated with the standalone mode.

13. The apparatus of claim 1, wherein the wearable display device operates without exchanging data with the companion device when the wearable display device operates in the standalone mode, and wherein the wearable display device exchanges the data with the companion device when the wearable display device operates in the companion mode.

14. The apparatus of claim 1, wherein the processor is further configured to: collect, prior to the obtainment of the indication and as the wearable display device operates in the standalone mode, data associated with the wearable display device, wherein to process the first rendered content and the second rendered content, the processor is further configured to process the first rendered content and the second rendered content further based on the data.

15. The apparatus of claim 14, wherein the data comprises perception data.

16. The apparatus of claim 1, wherein the apparatus is a wireless communication device further comprising at least one of a transceiver or an antenna coupled to the processor, and wherein to receive the second rendered content, the processor is configured to receive the second rendered content via at least one of the transceiver or the antenna.

17. A method of graphics processing, comprising: rendering, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associated with the wearable display device; obtaining an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device; receiving, from a companion device and based on the indication, second rendered content based on a second set of characteristics associated with the companion mode; processing the first rendered content and the second rendered content; and configuring a combined display buffer based on the processed first rendered content and the processed second rendered content.

18. The method of claim 17, wherein the first set of characteristics includes three degrees of freedom (3DOF) tracking, and wherein the second set of characteristics includes six degrees of freedom (6DOF) tracking.

19. The method of claim 17, wherein the first set of characteristics includes a head- locked rendering mode, and wherein the second set of characteristics includes a world- locked rendering mode.

20. A computer-readable medium storing computer executable code, the computer executable code, when executed by a processor, causes the processor to: render, at a wearable display device, first content based on a first set of characteristics associated with a standalone mode associated with the wearable display device; obtain an indication that the wearable display device is to be switched to a companion mode associated with the wearable display device; receive, from a companion device and based on the indication, second rendered content based on a second set of characteristics associated with the companion mode; process the first rendered content and the second rendered content; and configure a combined display buffer based on the processed first rendered content and the processed second rendered content.

Images