Signaling for augmented reality (XR) rendering offloading

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, an augmented reality (XR) device may receive a user equipment (UE) capability indicator identifying a rendering offload capability of the UE. The XR device may send data for rendering at the UE to the UE based at least in part on receiving the UE capability indicator. The XR device may receive rendered data from the UE in response to sending the data for rendering at the UE. Numerous other aspects are described.

Description

[0001] Cross - Reference to Related Applications

[0002] This patent application claims priority to U.S. Non - Provisional Patent Application No. 18 / 047,911, filed on October 19, 2022, entitled "SIGNALING FOR EXTENDED REALITY (XR) RENDERING OFFLOADING" and assigned to the assignee of the present application. The disclosure of the prior application is considered part of this patent application and is incorporated herein by reference. Field of Technology

[0003] Aspects of the present disclosure generally relate to wireless communication and relate to techniques and apparatus for signaling for extended reality (XR) rendering offloading. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access techniques include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single - carrier frequency division multiple access (SC - FDMA) systems, time division - synchronous code division multiple access (TD - SCDMA) systems, and long - term evolution (LTE). LTE / Advanced LTE is an enhanced set of the universal mobile telecommunications system (UMTS) mobile standards promulgated by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communication and uplink communication. "Downlink" (or "DL") refers to the communication link from the network node to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device - to - device communication, such as via a local link (e.g., sidelink (SL), wireless local area network (WLAN) link, and / or wireless personal area network (WPAN) link, etc.).

[0006] The above multi-access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at the urban, national, regional, and / or global levels. New Radio (NR) (which may be referred to as 5G) is an enhanced set of the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectral efficiency; reducing costs; improving services; leveraging new spectrums; and using Orthogonal Frequency Division Multiplexing with Cyclic Prefix (CP-OFDM) on the downlink, CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink, and better integrating with other open standards; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technology, and carrier aggregation. With the continuous increase in the demand for mobile broadband access, further improvements in LTE, NR, and other radio access technologies are still useful. Summary of the Invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a device of a device. The method may include: receiving a UE capability indicator that identifies the rendering offloading capability of a User Equipment (UE). The method may include: sending data for rendering at the UE at least in part based on the received UE capability indicator. The method may include: receiving the rendered data from the UE in response to sending the data for rendering at the UE.

[0008] Some aspects described herein relate to a method of wireless communication performed by a device of a UE. The method may include: sending a UE capability indicator that identifies the rendering offloading capability. The method may include: receiving data for rendering at least in part based on sending the UE capability indicator. The method may include: sending the rendered data in response to receiving the data for rendering.

[0009] Some aspects described herein relate to a method of wireless communication performed by a device of a network node. The method may include: receiving data for rendering, wherein the data for rendering is at least in part based on a capability indicator. The method may include: sending the rendered data in response to receiving the data for rendering.

[0010] Some aspects described herein relate to a device for wireless communication. The device may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a UE capability indicator identifying a rendering offloading capability of the UE. The one or more processors may be configured to send data for rendering at the UE based at least in part on receiving the UE capability indicator. The one or more processors may be configured to receive the rendered data from the UE in response to sending the data for rendering at the UE.

[0011] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a UE capability indicator identifying a rendering offloading capability. The one or more processors may be configured to receive data for rendering based at least in part on sending the UE capability indicator. The one or more processors may be configured to send the rendered data in response to receiving the data for rendering.

[0012] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive data for rendering, where the data for rendering is based at least in part on a capability indicator. The one or more processors may be configured to send the rendered data in response to receiving the data for rendering.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a device. The set of instructions, when executed by one or more processors of the device, may cause the device to receive a UE capability indicator identifying a rendering offloading capability of the UE. The set of instructions, when executed by one or more processors of the device, may cause the device to send data for rendering at the UE based at least in part on receiving the UE capability indicator. The set of instructions, when executed by one or more processors of the device, may cause the device to receive the rendered data from the UE in response to sending the data for rendering at the UE.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to send a UE capability indicator identifying a rendering offloading capability. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive data for rendering based at least in part on sending the UE capability indicator. The set of instructions, when executed by one or more processors of the UE, may cause the UE to send the rendered data in response to receiving the data for rendering.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, can cause the network node to receive data for rendering, where the data for rendering is at least partially based on a capability indicator. The instruction set, when executed by one or more processors of the network node, can cause the network node to send the rendered data in response to receiving the data for rendering.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for receiving a UE capability indicator identifying a rendering offloading capability of a UE. The apparatus can include means for sending, at least partially based on the received UE capability indicator, data for rendering to the UE. The apparatus can include means for receiving, in response to sending the data for rendering to the UE, the rendered data from the UE.

[0017] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for sending a capability indicator identifying a rendering offloading capability. The apparatus can include means for receiving data for rendering, at least partially based on sending the capability indicator. The apparatus can include means for sending the rendered data in response to receiving the data for rendering.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for receiving data for rendering, where the data for rendering is at least partially based on a capability indicator. The apparatus can include means for sending the rendered data in response to receiving the data for rendering.

[0019] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to the figures and the specification and illustrated in the figures and the specification.

[0020] The features and technical advantages of examples in accordance with the present disclosure have been outlined rather broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both as to their organization and operation methods and associated advantages, will be better understood when considered in conjunction with the following description taken in connection with the accompanying figures. Each of the figures provided in the accompanying figures is for purposes of illustration and description and not as a definition of the limits of the claims.

[0021] Although aspects are described herein by way of illustration of some examples, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via an integrated chip implementation or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features can include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a variety of devices, components, systems, distributed arrangements, and / or end-user devices of different sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] To understand the above features of the present disclosure in detail, a more specific description of the above briefly summarized invention content can be obtained by referring to the aspects, some of which are illustrated in the drawings. However, it should be noted that the drawings only illustrate some typical aspects of the present disclosure and are therefore not considered to limit its scope, as the specification may admit other equally valid aspects. The same reference numerals in different drawings can identify the same or similar elements.

[0023] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0024] Figure 2 is a diagram illustrating an example of a network node communicating with a user equipment (UE) or an extended reality (XR) device in a wireless network according to the present disclosure.

[0025] Figure 3 is a diagram illustrating an example of a decomposed base station architecture according to the present disclosure.

[0026] Figure 4 is a diagram illustrating an example of sidelink communication according to the present disclosure.

[0027] Figure 5 is a diagram illustrating an example of sidelink communication and access link communication according to the present disclosure.

[0028] Figure 6Is a diagram illustrating an example associated with signaling for XR rendering offloading according to the present disclosure.

[0029] Figure 7 Is a diagram illustrating an example process, such as may be performed by a device such as an XR device, according to the present disclosure.

[0030] Figure 8 Is a diagram illustrating an example process, such as may be performed by a UE, according to the present disclosure.

[0031] Figure 9 Is a diagram illustrating an example process, such as may be performed by a network node, according to the present disclosure.

[0032] Figures 10 to 12 Is a diagram of an example apparatus for wireless communication according to the present disclosure. Detailed Description

[0033] Aspects of the present disclosure are described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may 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 the present disclosure to those skilled in the art. Those skilled in the art should understand that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, any number of the aspects set forth herein may be used to implement an apparatus or practice a method. In addition, the scope of the present disclosure is intended to cover such apparatus or methods implemented using other structures, functionality, or a combination of structures and functionality in addition to or different from the aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0034] Several aspects of a telecommunications system will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the drawings by various boxes, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0035] Although terms typically associated with 5G or New Radio (NR) radio access technology (RAT) may be used to describe aspects herein, aspects of the present disclosure may be applied to other RATs such as 3G RAT, 4G RAT, and / or post-5G RAT (e.g., 6G). In some examples, "LTE SL" may be used interchangeably with "V2X SL", and "5G" may be used interchangeably with "NR".

[0036] Figure 1 FIG. is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, and so on. The wireless network 100 may include one or more network nodes 110 (shown as network nodes 110a, 110b, 110c, and 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UEs 120a, 120b, 120c, 120d, and 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown, the network node 110 may include one or more network nodes. For example, the network node 110 may be an aggregated network node, which means that the aggregated network node is configured to utilize a radio protocol stack physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), which means that the network node 110 is configured to utilize a protocol stack physically or logically distributed between two or more nodes such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs).

[0037] In some examples, network node 110 is a network node that communicates with UE 120 via a radio access link, such as a RU, or includes a network node that communicates with a UE via a radio access link, such as a RU. In some examples, network node 110 is a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU, or includes a network node that communicates with other network nodes via a fronthaul link or a midhaul link, such as a DU. In some examples, network node 110 is a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU, or includes a network node that communicates with other network nodes via a midhaul link or communicates with a core network via a backhaul link, such as a CU. In some examples, network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmission and reception point (TRP), a DU, a RU, a CU, a mobility element of the network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected with each other or with one or more other network nodes 110 in wireless network 100 using any suitable transport network via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0038] In some examples, network node 110 may provide communication coverage for a specific geographical area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of network node 110 and / or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and / or another type of cell. A macrocell may cover a relatively larger geographical area (e.g., with a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively smaller geographical area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively smaller geographical area (e.g., a home) and may allow restricted access by UE 120 associated with the femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 for a macrocell may be referred to as a macro network node. The network node 110 for a picocell may be referred to as a pico network node. The network node 110 for a femtocell may be referred to as a femto network node or a home network node. InFigure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of a cell may move according to the location of a moving network node 110 (e.g., a mobile network node).

[0039] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more of their components. For example, in some aspects, the "base station" or "network node" may refer to a CU, a DU, an RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a single device configured to perform one or more functions (such as those described herein in connection with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located at the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeat at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function among base station functions, rather than another base station function. In this way, a single device may include more than one base station.

[0040] Wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., network node 110 or UE 120) and transmit the data to a downstream node (e.g., UE 120 or network node 110). A relay station may be a UE 120 capable of relaying transmissions for other UEs 120. In Figure 1 the example shown, network node 110d (e.g., a relay network node) may communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. A network node that relays communication may be referred to as a relay station, a relay base station, a relay network node, a relay node, a repeater, etc.

[0041] The wireless network 100 can be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 can have different transmission power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node can have a high transmission power level (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes can have lower transmission power levels (e.g., 0.1 watt to 2 watts).

[0042] The network controller 130 can be coupled to or communicate with a set of network nodes 110 and can provide coordination and control for these network nodes 110. The network controller 130 can communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 can be a CU or a core network device, or can include a CU or a core network device.

[0043] UEs 120 can be scattered throughout the wireless network 100, and each UE 120 can be stationary or mobile. The UEs 120 can include, for example, access terminals, terminals, mobile stations, and / or subscriber units. The UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, a superbook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, UE functionality of a network node, and / or any other suitable device configured to communicate via wireless or wired media.

[0044] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. The MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as narrowband IoT (NB-IoT) devices. Some UEs 120 may be considered customer premises equipment. The UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0045] In some examples, the wireless network 100 may include an extended reality (XR) device 170. For example, the XR device 170 may communicate with the network node 110 (e.g., via an access link) and / or the UE 120 (e.g., via a sidelink). In some examples, the XR device 170 may be an example of the UE 120. In other words, some UEs 120 may be the XR device 170. The XR functionality may include augmented reality (AR), virtual reality (VR), or mixed reality (MR), etc. For example, when providing an XR service, the XR device 170 may provide rendered data via a display such as a screen, a set of VR goggles, a head-up display, or another type of display.

[0046] Generally, any number of wireless networks 100 may be deployed in a given geographical area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. The RAT may be referred to as a radio technology, an air interface, etc. The frequency may be referred to as a carrier, a frequency channel, etc. In a given geographical area, each frequency may support a single RAT to avoid interference between wireless networks of different RATs. In some cases, an NR or 5G RAT network may be deployed.

[0047] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., communicate with each other without using network node 110 as an intermediate device). For example, UE 120 may use peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, or vehicle-to-pedestrian (V2P) protocol) and / or a mesh network to communicate. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0048] Devices of wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc. according to frequency or wavelength. For example, devices of wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, in various documents and articles, FR1 is typically (interchangeably) referred to as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is typically (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0049] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified operating bands for these mid-band frequencies as frequency range designations FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0050] In view of the above examples, unless otherwise specifically stated, it should be understood that if terms such as "below 6 GHz" are used herein, such terms can generally represent frequencies that can be below 6 GHz, can be within FR1, or can include intermediate band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if terms such as "millimeter wave" are used herein, such terms can generally represent frequencies that can include intermediate band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. In view of the fact that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0051] In some aspects, the XR device 170 may include a communication manager 172. As described in more detail elsewhere herein, the communication manager 172 may receive a UE capability indicator that identifies the rendering offloading capability of the UE; send data for rendering at the UE at least in part based on the received UE capability indicator; and receive the rendered data from the UE in response to sending the data for rendering at the UE. Additionally or alternatively, the communication manager 172 may perform one or more other operations described herein.

[0052] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may send a UE capability indicator that identifies the rendering offloading capability of the UE; receive data for rendering at least in part based on sending the UE capability indicator; and send the rendered data in response to receiving the data for rendering. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0053] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive data for rendering, where the data for rendering is at least in part based on a capability indicator; and send the rendered data in response to receiving the data for rendering. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0054] As indicated above, Figure 1 is provided as an example. Other examples may be different from the examples described with respect to Figure 1 those described.

[0055] Figure 2FIG. 200 is an illustration showing an example 200 of a network node 110 communicating with a UE 120 or an XR device 170 in a wireless network 100 according to the present disclosure. Although some aspects are described in terms of communication between the network node 110 and the UE 120 or the XR device 170, the aspects described herein may be applied to communication between the UE 120 and the XR device 170, communication between multiple UEs 120, or communication between multiple XR devices 170, and so on.

[0056] The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 or the XR device 170 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or the XR device 170 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120 or the XR device 170, such as one or more CUs or one or more DUs.

[0057] At network node 110, transmit processor 220 may receive data destined for UE 120 or XR device 170 (or a group of UEs 120 or a group of XR devices 170) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCSs) for UE 120 or XR device 170 based at least in part on one or more channel quality indicators (CQIs) received from UE 120 or XR device 170. Network node 110 may process (e.g., encode and modulate) data destined for UE 120 or XR device 170 based at least in part on the MCS selected for UE 120 or XR device 170, and may provide data symbols for UE 120 or XR device 170. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to the modulator component (shown as MOD) of modem 232. Each modem 232 may process the corresponding output symbol stream (e.g., for OFDM) using the respective modulator component to obtain a stream of output samples. Each modem 232 may further process the stream of output samples (e.g., convert to analog, amplify, filter, and / or up-convert) using the respective modulator component to obtain a downlink signal. Modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0058] At the UE 120 or XR device 170, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal using the corresponding demodulator component to obtain input samples. Each modem 254 may further process the input samples (e.g., for OFDM) using the demodulator component to obtain received symbols. The MIMO detector 256 may obtain the received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide the detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide the decoded data destined for the UE 120 or XR device 170 to the data sink 260, and may provide the decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and / or CQI parameters, etc. In some examples, one or more components of the UE 120 or XR device 170 may be included in the housing 284.

[0059] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0060] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, a set of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmit and / or receive components (such as Figure 2 one or more components) of.

[0061] On the uplink, at the UE 120 or XR device 170, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 or XR device 170 may include a modulator and a demodulator. In some examples, the UE 120 or XR device 170 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figure 6 ) any aspects of any of the methods described herein.

[0062] At the network node 110, uplink signals from the UE 120 or XR device 170 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120 or XR device 170. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figure 6 ) any aspects of any of the methods described herein.

[0063] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120 or the XR device 170, and / or Figure 2 any other component of may perform one or more techniques associated with signaling for XR rendering offloading, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120 or the XR device 170, and / or Figure 2 any other component of may execute or direct, for example, Figure 7 process 700 of, Figure 8 process 800 of, Figure 9 process 900 of, and / or the operation of other processes as described herein. The memories 242 and 282 may store data and program code for the network node 110 and the UE 120 or the XR device 170, respectively. In some examples, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions for wireless communication (e.g., code and / or program code). For example, when the one or more instructions are executed (e.g., directly executed, or after compilation, transformation, and / or interpretation) by one or more processors of the network node 110 and / or the UE 120 or the XR device 170, the one or more processors, the UE 120 or the XR device 170, and / or the network node 110 may be caused to execute or direct, for example, Figure 7 process 700 of, Figure 8 process 800 of, Figure 9 process 900 of, and / or the operation of other processes as described herein. In some examples, executing the instructions may include running the instructions, transforming the instructions, compiling the instructions, and / or interpreting the instructions, and so on.

[0064] In some aspects, the XR device 170 includes: components for receiving a UE capability indicator identifying the rendering offloading capabilities of a UE; components for sending data for rendering at the UE based at least in part on the received UE capability indicator; and / or components for receiving the rendered data from the UE in response to sending the data for rendering at the UE. In some aspects, the components for the XR device 170 to perform the operations described herein may include, for example, one or more of the communication manager 172, the antenna 252, the modem 254, the MIMO detector 256, the receiving processor 258, the sending processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0065] In some aspects, UE 120 includes: components for sending a UE capability indicator identifying a rendering offloading capability; components for receiving data for rendering at least in part based on sending the UE capability indicator; and / or components for sending rendered data in response to receiving the data for rendering. In some aspects, the components for UE 120 to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0066] In some aspects, a device includes: components for receiving data for rendering, where the data for rendering is at least in part based on a capability indicator; and / or components for sending rendered data in response to receiving the data for rendering. In some aspects, the components for the device to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0067] Although Figure 2 the boxes are illustrated as different components, the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by controller / processor 280 or under the control of the controller / processor.

[0068] As indicated above, Figure 2 is provided as an example. Other examples may be different from the examples described with respect to Figure 2 the examples described above.

[0069] The deployment of a communication system, such as a 5G NR system, can be arranged in various ways using various components or constituent parts. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in a centralized or decomposed architecture. For example, a base station (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as a centralized base station (also referred to as a stand-alone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0070] A centralized base station (e.g., a centralized network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually spread across one or more other network nodes. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), etc.

[0071] Base station type operations or network designs can consider the aggregation characteristics of base station functionality. For example, a decomposed base station can be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed independently. A decomposed base station can include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which can achieve flexibility in network design. The individual units of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0072] Figure 3FIG. is an illustration of an example disaggregated base station architecture 300 in accordance with the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link or indirectly with the core network 320 through one or more disaggregated control units (such as a near RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links (such as via an F1 interface). Each DU in the DUs 330 may communicate with one or more RUs 340 via a respective fronthaul link. Each RU in the RUs 340 may communicate with one or more UEs 120 or XR devices 170 via a respective radio frequency (RF) access link. In some specific implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0073] Each unit (including the CU 310, DU 330, RU 340) and the near RT RIC 325, non-RT RIC 315, and SMO framework 305 may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to one or more communication interfaces of a respective unit may be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of these units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and the wireless interface may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium or both.

[0074] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, service data adaptation protocol (SDAP) functions, and so on. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit - user plane (CU - UP) functionality), control plane functionality (e.g., central unit - control plane (CU - CP) functionality), or a combination thereof. In some embodiments, the CU 310 may be logically split into one or more CU - UP units and one or more CU - CP units. When implemented in an O - RAN configuration, the CU - UP units may communicate bi - directionally with the CU - CP units via an interface such as the E1 interface. As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0075] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of the radio link control (RLC) layer, the MAC layer, and one or more higher physical (PHY) layers, at least in part, according to a functional split such as that defined by 3GPP. In some aspects, one or more of the higher PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, and so on. In some aspects, the DU 330 may further host one or more lower PHY layers, such as those implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, and so on. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0076] Each RU 340 can implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 can correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc.) based on function splitting (such as the function splitting defined by 3GPP), such as lower layer function splitting. In such an architecture, each RU 340 can be operated to handle over-the-air (OTA) communication with one or more UEs 120 or XR devices 170. In some specific implementations, the real-time aspects and non-real-time aspects of the control plane communication and user plane communication with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0077] The SMO framework 305 can be configured to support the deployment and orchestration of RANs with non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources can be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 can communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 can communicate directly with each RU in one or more RUs 340 via the corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0078] The non-RT RIC 315 can be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325 (such as via the A1 interface). The near-RT RIC 325 can be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via an interface (such as via the E2 interface) through data collection and actions, and this interface connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB to the near-RT RIC 325.

[0079] In some specific implementations, to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions through the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0080] As indicated above, Figure 3 is provided as an example. Other examples may be different from the examples Figure 3 described.

[0081] Figure 4 is a diagram illustrating Example 400 of sidelink communication according to the present disclosure.

[0082] As Figure 4As shown, the first UE may communicate with a second UE (or more other UEs) via one or more sidelink channels. Although some aspects are described in the context of communication between a pair of UEs, the aspects described herein may apply to communication between a pair of XR devices or between a UE and an XR device. The UE may communicate using one or more sidelink channels for peer-to-peer communication, device-to-device communication, XR communication, vehicle-to-everything (V2X) communication (e.g., which may include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-network (V2N) communication, and / or vehicle-to-pedestrian (V2P) communication) and / or mesh networking. In some examples, the UE may correspond to one or more other UEs described elsewhere herein, such as UE 120. In some examples, one or more sidelink channels may use the PC5 interface and / or may operate in a high frequency band (e.g., 5.9 GHz band). Additionally or alternatively, the UE may use Global Navigation Satellite System (GNSS) timing to synchronize the timing of transmission time intervals (TTIs) (e.g., frames, sub-frames, time slots, or symbols).

[0083] As Figure 4 Further shown, one or more sidelink channels may include a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), and / or a Physical Sidelink Feedback Channel (PSFCH). The PSCCH may be used to convey control information, similar to the Physical Downlink Control Channel (PDCCH) and / or the Physical Uplink Control Channel (PUCCH) used for cellular communication with a network node 110 via an access link or access channel. The PSSCH may be used to convey data, similar to the Physical Downlink Shared Channel (PDSCH) and / or the Physical Uplink Shared Channel (PUSCH) used for cellular communication with a network node via an access link or access channel. For example, the PSCCH may carry sidelink control information (SCI), which may indicate various control information for sidelink communication, such as one or more resources (e.g., time resources, frequency resources, and / or spatial resources), where a transport block (TB) may be carried on the PSSCH. The TB may include data. The PSFCH may be used to convey sidelink feedback, such as Hybrid Automatic Repeat Request (HARQ) feedback (e.g., acknowledgement or negative acknowledgement (ACK / NACK) information), transmit power control (TPC), and / or scheduling request (SR).

[0084] Although shown on the PSCCH, in some aspects, the SCI may include multiple communications at different levels, such as a first-level SCI (SCI-1) and a second-level SCI (SCI-2). The SCI-1 may be transmitted on the PSCCH. The SCI-2 may be transmitted on the PSSCH. The SCI-1 may include, for example, an indication of one or more resources (e.g., time resources, frequency resources, and / or spatial resources) on the PSSCH, information for decoding sidelink communications on the PSSCH, a quality of service (QoS) priority value, a resource reservation period, a PSSCH demodulation reference signal (DMRS) pattern, an SCI format for the SCI-2, a β offset for the SCI-2, the number of PSSCH DMRS ports, and / or a modulation and coding scheme (MCS). The SCI-2 may include information associated with data transmission on the PSSCH, such as a hybrid automatic repeat request (HARQ) process ID, a new data indicator (NDI), a source identifier, a destination identifier, and / or a channel state information (CSI) report trigger.

[0085] In some aspects, one or more sidelink channels may use a resource pool. For example, a specific resource block (RB) spanning time may be used to transmit a scheduling assignment (e.g., included in the SCI) in a subchannel. In some aspects, data transmission associated with the scheduling assignment (e.g., on the PSSCH) may occupy adjacent RBs in the same subframe as the scheduling assignment (e.g., using frequency division multiplexing). In some aspects, the scheduling assignment and the associated data transmission are not transmitted on adjacent RBs.

[0086] In some aspects, the UE may operate using a sidelink transmission mode (e.g., mode 1), where resource selection and / or scheduling is performed by a network node (e.g., a base station, CU, or DU). For example, the UE may receive (e.g., directly or via one or more network nodes) a grant for sidelink channel access and / or scheduling from a network node (e.g., in downlink control information (DCI) or in a radio resource control (RRC) message, such as a configured grant). In some aspects, the UE may operate using a transmission mode (e.g., mode 2), where resource selection and / or scheduling is performed by the UE (e.g., instead of a network node). In some aspects, the UE may perform resource selection and / or scheduling by sensing the availability of channels for transmission. For example, the UE may measure received signal strength indicator (RSSI) parameters associated with various sidelink channels (e.g., sidelink RSSI (S-RSSI) parameters), may measure reference signal received power (RSRP) parameters associated with various sidelink channels (e.g., PSSCH-RSRP parameters), and / or may measure reference signal received quality (RSRQ) parameters associated with various sidelink channels (e.g., PSSCH-RSRQ parameters), and may select a channel for sidelink communication transmission based at least in part on the measurements.

[0087] Additionally or alternatively, the UE may use the SCI received in the PSCCH to perform resource selection and / or scheduling, and the SCI may indicate occupied resources and / or channel parameters. Additionally or alternatively, the UE may perform resource selection and / or scheduling by determining the channel busy ratio (CBR) associated with various sidelink channels, and the channel busy ratio (CBR) may be used for rate control (e.g., by indicating the maximum number of resource blocks available to the UE for a particular set of subframes).

[0088] In the transmission mode where the UE performs resource selection and / or scheduling, the UE may generate a sidelink grant and may transmit the grant in the SCI. The sidelink grant may indicate, for example, one or more parameters (e.g., transmission parameters) for an upcoming sidelink transmission, such as one or more resource blocks (e.g., for a TB) to be used for an upcoming sidelink transmission on the PSSCH, one or more subframes to be used for the upcoming sidelink transmission, and / or the modulation and coding scheme (MCS) to be used for the upcoming sidelink transmission. In some aspects, the UE may generate a sidelink grant indicating one or more parameters (such as the periodicity of sidelink transmissions) for semi-persistent scheduling (SPS). Additionally or alternatively, the UE may generate a sidelink grant for event-driven scheduling, such as for on-demand sidelink messages.

[0089] As indicated above, Figure 4 is provided as an example. Other examples may relate to Figure 4is different from the examples described above.

[0090] Figure 5 FIG. 500 is a diagram illustrating an example of sidelink communication and access link communication according to the present disclosure.

[0091] As Figure 5 shown, UE 505, UE 510, and XR device 515 may communicate with each other via the sidelink, as described above in connection with Figure 4 FIG. In some sidelink modes (e.g., NR sidelink mode 1 or LTE V2X sidelink mode 3), network node 110 may communicate with UE 505 (e.g., directly or via one or more network nodes) via, for example, a first access link. Additionally or alternatively, in some sidelink modes, network node 110 may communicate with UE 510 (e.g., directly or via one or more network nodes) via, for example, a first access link. Additionally or alternatively, in some sidelink modes (e.g., NR sidelink mode 1 or LTE V2X sidelink mode 3 or similar network-controlled sidelink modes), network node 110 may communicate with XR device 515 (e.g., directly or via one or more network nodes) via, for example, a first access link. Additionally or alternatively, in some sidelink modes (e.g., NR sidelink mode 2, LTE V2X sidelink mode 4, or similar autonomous sidelink modes), UE 505 and / or UE 510 may communicate with XR device 515 via the first and / or second sidelink (SL). UE 505 and / or UE 510 may correspond to one or more UEs described elsewhere herein, such as Figure 1 UE 120. XR device 515 may correspond to one or more XR devices described herein, such as Figure 1 XR device 170. Thus, a direct link between UEs 120 or between UE 120 and XR device 170 (e.g., via the PC5 interface, via the NR sidelink (NRSL) (such as NR SL1 or NR SL2), or NR sidelink unlicensed spectrum (NR SL-U) or LTE sidelink (LTE SL)) may be referred to as a sidelink, and a direct link between network node 110 and UE 120 or XR device 515 (e.g., via the Uu interface) may be referred to as an access link. Sidelink communication may be sent via the sidelink, and access link communication may be sent via the access link. Access link communication may be downlink communication (from network node 110 to UE 120 or XR device 170) or uplink communication (from UE 120 or XR device 170 to network node 110).

[0092] As indicated above, Figure 5 is provided as an example. Other examples may be related to Figure 5The described examples are different.

[0093] As described above, an XR device can provide rendered data (e.g., video data or XR data) via a display of the XR device. For example, the XR device can provide rendered VR video data for a user based on, for example, the user's location, the orientation of the user and / or the XR device, or the state of an application that generates VR video data, etc. Rendering data in real time for an XR service can cause the XR device to use a relatively large amount of processing resources and / or power resources. However, some XR devices may have limited processing resources and / or power resources, which may limit the amount of data that some XR devices can render in real time. This may cause the XR device to downselect to a lower quality video, or may cause gaps or artifacts to appear in the video provided by the XR device, among other issues.

[0094] Split rendering can be used to offload some rendering tasks from an XR device with limited resources. For example, the XR device can offload a rendering task to an edge device or a cloud device that has greater availability of computing resources and / or power resources relative to the XR device. In some cases, the XR device can split a rendering task such that a portion of the rendering task is performed remotely by another device and a portion of the rendering task is performed locally by the XR device. However, for some XR applications (e.g., XR applications with relatively low latency and / or relatively high reliability criteria), network rendering based on Uu (e.g., by a network edge device or a cloud computing device) may not be feasible. For example, for some XR applications, sending data to an edge device for rendering and receiving the rendered data in response may not meet service quality (QoS) parameters or quality of experience (QoE) parameters. Therefore, it may be desirable to offload rendering tasks with lower latency and / or higher reliability compared to what is achieved with network edge-based offloading.

[0095] Some aspects described herein provide signaling for XR rendering offloading to an adjacent device having underutilized computing resources. For example, an XR device may receive capability signaling indicating the ability of another device (e.g., a UE) to perform offloaded rendering on behalf of the XR device (e.g., and via a side link or a Wi-Fi connection to the XR device). In such a case, at least in part based on receiving the capability signaling, the XR device may offload rendering data to, e.g., the UE for rendering and may receive the rendered data in response. In this way, the XR device may use the computing resources of the UE to provide XR applications where rendering at the network edge does not meet its QoS parameters or QoE parameters. In some aspects, the XR device may dynamically offload rendering data to, e.g., the UE at least in part based on real-time information about the resource availability of the UE. For example, the XR device may receive a power and / or computing resource (PCR) message indicating the current power usage or computing resource usage of the UE and may offload rendering data to the UE when the UE has available power resources and computing resources. In some aspects, the XR device may offload rendering data at least in part based on receiving a semi-static indication of the ability of, e.g., the UE to perform offloaded rendering and at least in part based on dynamic PCR availability information, as described herein. In some aspects, the XR device may offload rendering data to multiple UEs or to a network node (e.g., via a Wi-Fi connection or an access link connection), as described herein.

[0096] Figure 6 is a diagram illustrating example 600 associated with signaling for XR rendering offloading according to the present disclosure. As Figure 6 shown, example 600 includes communication between an XR device 170, a UE 120, and another UE 120' or a network node 110.

[0097] As further shown in Figure 6 and by reference numeral 650, the XR device 170 may receive a capability indicator. For example, the XR device 170 may receive a UE capability indicator from the UE 120. Additionally or alternatively, the XR device 170 may receive a capability indicator from the UE 120' and / or the network node 110. In some aspects, the XR device 170 may receive the UE capability indicator via a particular type of link. For example, the XR device 170 may support communication via an NR side link (SL) (e.g., an NR licensed spectrum side link), an NR unlicensed spectrum side link (SL-U), an LTE side link, or an NR Uu interface (e.g., an access link). In such a case, the XR device 170 and the UE 120 may support communicating information identifying 5G SL capabilities (e.g., the UE120 is able to perform offloading using 5G SL) via, e.g., LTE SL, NR SL, or NR SL-U communication, etc.

[0098] In some aspects, the UE 120 may advertise its ability to perform offloaded rendering. For example, the UE 120 may send an advertisement message identifying the offloading ability and / or the maximum offloading capacity (e.g., the maximum rendering rate that the UE 120 can support). In such a case, the UE 120 may use, for example, 5G SL capability indication to send the advertisement message. In some aspects, the XR device 170 may request and receive UE capability indication. For example, the XR device 170 and the UE 120 may exchange UE 5G SL capability indication via PC5 radio resource control (RRC) messages. In such a case, the PC5-RRC message may include one or more new parameters or fields for conveying the 5G SL capability indication for XR rendering offloading. As an example of the one or more new parameters or fields, the XR device 170 may send a message with UECapabilityEnquirySidelink (UE capability enquiry sidelink) to request the 5G SL capability indication, and the UE 120 may send a message with UECapabilityInformationSidelink (UE capability information sidelink) to convey the 5G SL capability indication.

[0099] As shown in Figure 6 and further indicated by reference numeral 660, in some aspects, the XR device 170 may receive resource availability information. For example, the XR device 170 may request resource availability information from the UE 120 and receive a UE resource availability indicator in response. Additionally or alternatively, the XR device 170 may request resource availability information from the UE 120' or the network node 110 and receive the resource availability information from the UE or the network node.

[0100] In some aspects, the XR device 170 may receive resource availability information via sidelink control information (SCI). For example, the UE 120 may use a new SCI format (e.g., SCI format 2-D) having one or more fields associated with conveying UE-to-UE power and / or compute resource (PCR) information. In such a case, the UE 120 may send an SCI conveying PCR information at least in part based on receiving an SCI from the XR device 170 that conveys a request for PCR information (e.g., the SCI conveys a request for PCR information in one or more of its fields). For example, the XR device 170 may send a first SCI requesting the current PCR status of the UE 120 (e.g., in a first SCI format 2-D message where a 1-bit indicator is set to “1” to indicate that the XR device 170 is requesting the current PCR status). In such a case, in response, the UE 120 may send a second SCI conveying the current PCR status of the UE 120 (e.g., in a second SCI format 2-D message where a 1-bit indicator is set to “0” to indicate that the UE 120 is providing the current PCR status). Additionally or alternatively, the UE 120 may set another bit indicator in the second SCI to indicate that the UE 120 is capable of and / or is recommending the UE 120 for XR rendering offloading. In other words, the UE 120 may indicate the current PCR status (e.g., current power resource and / or compute processing resource utilization) and may recommend that the UE 120 has sufficient resources for XR offloading. In some aspects, preferred or non-preferred PCR resources for one or more rendering offloading tasks may be indicated via a MAC CE. In some aspects, preferred or non-preferred PCR resources for one or more rendering offloading tasks may be indicated via a combination of a MAC CE and SCI format 2-D.

[0101] Additionally or alternatively, the XR device 170 may use UE-to-UE coordination messages to obtain information about the PCR status of the UE 120. For example, a UE-to-UE coordination (IUC) scheme 1 having preferred resource information in SCI format 2-C may be used to convey the real-time or near-real-time status of the use of the power resources and / or compute resources of the UE 120. Additionally or alternatively, the UE 120 may include a bit indicator in a field of SCI format 2-C to indicate that the UE 120 has sufficient available resources (e.g., power resource utilization and compute processing resource utilization do not exceed respective thresholds) for providing XR rendering offloading. In some aspects, other fields may be included in SCI format 2-C to indicate the current compute resource usage of the UE, such as current offloading availability and offloading capacity. In some aspects, preferred or non-preferred resources may be indicated via an IUC MAC CE.

[0102] Additionally or alternatively, the UE 120 may send a PC5 Medium Access Control (MAC) Control Element (CE) to convey the PCR status (e.g., the level or percentage of PCR usage or PCR usage rate) and / or provide a recommendation for XR rendering offloading (e.g., preferred PCR usage or preferred rendering offloading). For another example, the UE 120 may use a MAC CE to activate or deactivate PCR usage among multiple PCR usages, which may be configured or preconfigured. Additionally or alternatively, the UE 120 may send a PC5 RRC message (e.g., UEAssistanceInformationSidelink) to convey the PCR status (e.g., the level or percentage of PCR usage or PCR usage rate) and / or provide a recommendation for XR rendering offloading (e.g., preferred PCR usage or preferred rendering offloading).

[0103] As shown in Figure 6 and further indicated by reference numeral 670, the XR device 170 may send data for rendering. For example, the XR device 170 may send data for rendering to the UE 120. Additionally or alternatively, the XR device 170 may send data to the UE120' or the network node 110 for rendering.

[0104] In some aspects, the XR device 170 may offload data for rendering at least in part based on receiving the UE 5G SL capabilities. For example, when the XR device 170 receives the UE 5G SL capabilities and will provide XR services, the XR device 170 may offload the rendering tasks for the XR services to one or more UEs 120 (e.g., UE 120 and UE 120', via 5G SL) that have provided UE 5G SL capabilities indication. In this way, the UE 120 can meet the low-latency XR use cases. Additionally or alternatively, for high-capacity XR rendering offloading, the XR device 170 may offload a first portion of the data for rendering at the UE 120 and a second portion of the data for rendering at the network node 110. In this case, the first portion of the data rendered at the UE 120 may support low latency, and the second portion of the data rendered at the network node 110 may achieve higher rendering capacity. In some aspects, the XR device 170 may offload data for rendering via multiple different links. For example, at least in part based on the capabilities of the XR device 170 and / or the capabilities of the destination for rendering (e.g., UE 120, UE 120' or network node 110), the XR device 170 may offload data for rendering via NR SL, NR SL-U, LTE SL, Uu link, or Wi-Fi link, etc. In some aspects, the XR device 170 may offload data to a single device via multiple links. For example, when the UE 120 supports both NR SL and NR SL-U, the XR device 170 may offload a first portion of the data to the UE 120 via NR SL and a second portion of the data to the UE 120 via NR SL-U, which can achieve greater capacity and / or reliability compared to using a single link. For another example, if multi-carrier operation is supported (e.g., NR SL CA or NR SL dual connectivity), the XR device 170 may offload a first portion and a second portion of the data to the UE 120 via multiple NR SLs. In another example, if multi-RAT operation is supported (e.g., NR / NR or NR / LTE SL dual connectivity), the XR device 170 may offload a first portion and a second portion of the data to the UE 120 via multiple SLs.

[0105] In some aspects, the XR device 170 may dynamically offload data for rendering. For example, at least in part based on the resource availability information received from the UE 120 (e.g., PCR information), the XR device 170 may dynamically offload data for rendering according to the resource availability. In other words, the XR device 170 may determine the amount and / or rate of the data to be offloaded for rendering at least in part based on the resource availability of the UE 120.

[0106] In some aspects, the XR device 170 may dynamically offload data for rendering at least in part based on the distance between the UE 120 and the XR device 170. For example, the XR device 170 may select a closer UE (e.g., UE120 or UE 120') that is closer to the XR device 170 for XR rendering offloading to reduce latency and / or increase reliability relative to selecting a more distant UE. In some aspects, the UE 120 may provide location information and / or mobility information (e.g., direction and speed) to the XR device 170 to enable the XR device 170 to select a closer UE (or a moving UE that will be closer in a particular future time period).

[0107] In some aspects, the XR device 170 may dynamically offload data for rendering at least in part based on the link connection status. For example, the XR device 170 may select a UE with a larger bandwidth rather than a UE with a smaller bandwidth to ensure a greater capacity. Additionally or alternatively, the XR device 170 may select a UE with a higher bit rate or throughput, such as a UE 120 that is at least in part based on having a Wi-Fi connection or an NR SL-U connection rather than another UE 120' having an NR SL connection (e.g., which may be configured to have a lower bit rate compared to the bit rate configured for Wi-Fi or NR SL-U). Additionally or alternatively, the XR device 170 may select a UE with better channel conditions relative to another UE. For example, the UE 120 may report the sidelink reference signal received power (RSRP), the sidelink reference signal received quality (RSRQ), or the channel busy ratio (CBR), the sidelink channel occupancy ratio (CR), etc., and at least in part based on this information, the XR device 170 may select the UE 120 to offload data for rendering. Additionally or alternatively, the UE 120 may report listen-before-talk (LBT) or other contention-based access (CBA) metrics, and at least in part based on this information, the XR device 170 may select the UE 120.

[0108] Additionally or alternatively, the XR device 170 may select the UE 120 for offloading data rendering at least in part based on the operating frequency range. For example, the XR device 170 may offload data to the UE 120 via NR SL on FR1 rather than via NR SL on FR2 at least in part because FR1 is associated with higher reliability compared to FR2 (e.g., when the XR device 170 supports multi-carrier operations such as NR SL carrier aggregation (CA) or NR SL dual connectivity). Similarly, the XR device 170 may determine to send the data for rendering to the UE 120 via LTE SL on FR1 rather than to the UE 120' in the case of NR SL on FR2 at least in part because FR1 is associated with higher reliability compared to FR2 (e.g., when the XR device 170 supports multi-RAT operations such as NR / NR operation or NR / LTE SL dual connectivity). Although FR1 is described as having higher reliability compared to FR2, some aspects described herein may apply to other frequency bands, and / or different reliability levels may be associated with different frequency bands, such as FR2 may be associated with a higher reliability level compared to FR1 (and be preferred).

[0109] In some aspects, the XR device 170 may select the UE 120 for offloading data rendering at least in part based on XR traffic characteristics. For example, the XR device 170 may select the UE 120, UE 120', and / or network node 110 at least in part based on data rate, packet delay budget (PDB), packet error rate (PER), round-trip time (RTT), traffic file size distribution or periodicity, QoS metric, QoE metric, 5G quality indicator (5QI) latency metric, or bitrate guarantee metric, etc.

[0110] In some aspects, the XR device 170 may offload data for rendering to another device (e.g., UE 120, UE 120', or network node 110) at least in part based on semi-static indications and dynamic indications. For example, the XR device 170 may receive a first signaling message indicating the 5G SL capabilities of the UE 120 (e.g., a PC5-RRC message directly from the UE 120 or an RRC message provided by the network node 110). Further for this example, the XR device 170 may receive a second signaling message via layer 1 signaling (e.g., SCI, such as SCI format 1-A or SCI format 2-X, where SCI format 2-X may be represented as SCI format 2-A, SCI format 2-B, SCI format 2-C, or SCI format 2-D), the second signaling message indicating the real-time or near-real-time resource availability of the UE 120 (e.g., current offloading availability and / or current offloading capacity, which may indicate the number of tasks that the UE 120 can complete for the XR device 170 within a set latency budget). In such a case, at least in part based on receiving the first signaling message and the second signaling message, the XR device 170 may determine to send data to the UE 120 for offloaded rendering.

[0111] In some aspects, the UE 120 may autonomously determine the offloading availability and signal this availability to the XR device 170. The UE 120 may prompt the XR device 170 to approve the rendering offloading. For example, the UE 120 may determine whether UE activity, UE battery level, or UE traffic meets one or more criteria for allowing the offloaded rendering to occur. In some aspects, the UE 120 may determine the offloading availability on a per-task basis and signal this availability. For example, the UE 120 may indicate the availability of offloaded rendering for a first task having a first data volume and / or first latency parameter, but not indicate the availability of offloaded rendering for a second task having a second data volume and / or second latency parameter. In such a case, the XR device 170 may determine to offload data for the first task, while not offloading data for the second task. Although some aspects are described herein with respect to a particular number of tasks and / or devices (e.g., offloading two tasks to two devices), other numbers of tasks or devices are contemplated, such as offloading data for rendering to 3 devices, 4 devices, or any other number of devices. Similarly, although some aspects are described herein with respect to offloading via 5G or NR connections, other types of connections are contemplated, such as LTE SL, V2XSL, Wi-Fi connections, Bluetooth connections, near field connections (NFC), or 6G or higher connections, etc.

[0112] As in Figure 6As further shown in A and by reference numeral 680, the XR device 170 may receive rendered data. For example, the XR device 170 may receive rendered data from the UE 120 at least in part based on sending data for rendering to the UE 120. Additionally or alternatively, the XR device 170 may receive rendered data from the UE 120' or the network node 110 at least in part based on sending data for rendering to the UE 120' or the network node 110. Additionally or alternatively, the XR device 170 may receive rendered data from multiple devices (such as two or more of the UE 120, UE 120', network node 110, or other devices). At least in part based on the received rendered data, the XR device 170 may output the rendered data. For example, the XR device 170 may output the rendered data as a video by a display. In some aspects, the XR device 170 may combine the rendered data (e.g., offloaded to one or more other devices) with additional rendered data (e.g., rendered by the XR device 170). In this way, the XR device 170 extends the capacity of the XR device 170 for rendering data (e.g., for XR services) by using offloading to other devices to supplement or replace rendering performed at the XR device 170.

[0113] As indicated above, Figure 6 is provided as an example. Other examples may be different from the examples described with respect to Figure 6 the examples described.

[0114] Figure 7 is a diagram illustrating an example process 700 performed by a device, such as according to the present disclosure. The example process 700 is an example where a device (e.g., the XR device 170) performs operations associated with signaling for XR rendering offloading.

[0115] As Figure 7 shown, in some aspects, the process 700 may include: receiving a UE capability indicator identifying the rendering offloading capability of the UE (block 710). For example, a device (e.g., using the communication manager 172 and / or the receiving component 1002 depicted) may receive a UE capability indicator identifying the rendering offloading capability of the UE, as described above. Figure 10 as described above.

[0116] As Figure 7 further shown, in some aspects, the process 700 may include: sending data for rendering at the UE to the UE at least in part based on receiving the UE capability indicator (block 720). For example, a device (e.g., using the communication manager 172 and / or the sending component 1004 depicted) may send data for rendering at the UE to the UE at least in part based on receiving the UE capability indicator, as described above. Figure 10 as described above.

[0117] As Figure 7 Further shown, in some aspects, process 700 may include: receiving rendered data from a UE in response to sending data for rendering at the UE (block 730). For example, a device (e.g., using Figure 10 the depicted communication manager 172 and / or receiving component 1002) may receive rendered data from the UE in response to sending data for rendering at the UE, as described above.

[0118] Process 700 may include additional aspects, such as any individual aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0119] In a first aspect, a UE capability indicator may include information identifying an offloading capability or a maximum offloading capacity.

[0120] In a second aspect, alone or in combination with the first aspect, a UE capability indicator may convey or trigger using at least one of: a UE 5G sidelink capability indicator, an LTE sidelink capability indicator, an NR sidelink capability indicator, an NR unlicensed spectrum sidelink capability indicator, a UECapabilityEnquirySidelink parameter, or a UECapabilityInformationSidelink parameter.

[0121] In a third aspect, alone or in combination with one or more of the first and second aspects, the data for rendering is a first portion of the rendered data and the rendered data is first rendered data, and process 700 includes: sending a second portion of the rendered data for rendering at a network node, and receiving second rendered data from the network node in response to sending the second portion of the rendered data for rendering at the network node.

[0122] In a fourth aspect, alone or in combination with one or more of the first to third aspects, sending the second portion of the rendered data includes: sending the second portion of the rendered data at least partially based on the amount of the rendered data for rendering.

[0123] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, sending data for rendering includes: sending data for rendering via at least one of a licensed sidelink or an unlicensed sidelink.

[0124] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 700 includes: receiving information identifying UE resource availability, and sending data for rendering includes: sending data for rendering at least partially based on UE resource availability.

[0125] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the UE capability indicator is received via semi-static signaling, and the information identifying the UE resource availability is received via at least one of dynamic layer 1 signaling, MAC CE signaling, or semi-static signaling.

[0126] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the UE resource availability includes information identifying at least one of power usage or computing resource usage.

[0127] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, procedure 700 includes: requesting the status of the UE via a first SCI message, and receiving the information identifying the UE resource availability includes: receiving the information identifying the UE resource availability via a second SCI message at least partially based on requesting the status of the UE.

[0128] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, at least one of the first SCI message or the second SCI message is associated with SCI format 2-D.

[0129] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the information identifying the UE resource availability is conveyed via at least one of: an inter-UE coordination message, a sidelink control information format 2-C message, one or more dedicated fields in a sidelink control information message, a PC5 MAC CE, a PC5 radio resource control message, or an activation message.

[0130] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the data for rendering is sent at least partially based on at least one of: the distance to the UE, the channel bandwidth, the resource availability, the type of communication link connection, the channel condition, the sidelink operating frequency range, the traffic characteristics, the quality of service metric, or the quality of experience metric.

[0131] Although Figure 7 example boxes of procedure 700 are shown, in some aspects, procedure 700 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to those depicted. Additionally or alternatively, two or more boxes of procedure 700 may be executed in parallel. Figure 7

[0132] Figure 8 ​FIG. 800 illustrates an example process, e.g., performed by a UE, in accordance with the present disclosure. Example process 800 is an example in which a UE (e.g., UE 120) performs operations associated with signaling for XR rendering offloading.

[0133] As Figure 8 shown, in some aspects, process 800 may include: sending a UE capability indicator identifying a rendering offloading capability (block 810). For example, a UE (e.g., using Figure 11 the depicted communication manager 140 and / or sending component 1104) may send a UE capability indicator identifying a rendering offloading capability, as described above.

[0134] As Figure 8 further shown, in some aspects, process 800 may include: receiving data for rendering, at least in part based on sending the UE capability indicator (block 820). For example, a UE (e.g., using Figure 11 the depicted communication manager 140 and / or receiving component 1102) may receive data for rendering, at least in part based on sending the UE capability indicator, as described above.

[0135] As Figure 8 further shown, in some aspects, process 800 may include: sending rendered data in response to receiving data for rendering (block 830). For example, a UE (e.g., using Figure 11 the depicted communication manager 140 and / or sending component 1104) may send rendered data in response to receiving data for rendering, as described above.

[0136] Process 800 may include additional aspects, such as any individual aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0137] In a first aspect, process 800 includes: rendering data to generate rendered data, and sending the rendered data includes: sending the rendered data, at least in part based on the rendered data.

[0138] In a second aspect, alone or in combination with the first aspect, the UE capability indicator may include information identifying an offloading capability or a maximum offloading capacity.

[0139] In a third aspect, either alone or in combination with one or more of the first and second aspects, the UE capability indicator can be conveyed or triggered using at least one of the following: a UE 5G sidelink capability indicator, an LTE sidelink capability indicator, an NR sidelink capability indicator, an NR unlicensed spectrum sidelink capability indicator, a UECapabilityEnquirySidelink parameter, or a UECapabilityInformationSidelink parameter.

[0140] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the data for rendering is a first part of the rendering data, where a second part of the rendering data is for rendering at another device.

[0141] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, receiving data for rendering includes: receiving data for rendering via at least one of a licensed sidelink or an unlicensed sidelink.

[0142] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 800 includes: sending information identifying resource availability, and receiving data for rendering includes: receiving data for rendering at least partially based on resource availability.

[0143] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the UE capability indicator is sent via semi-static signaling, and the information identifying resource availability is sent via at least one of dynamic layer 1 signaling, MAC CE signaling, or semi-static signaling.

[0144] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, resource availability includes information identifying at least one of power usage or computing resource usage.

[0145] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 800 includes: receiving a request for status information via a first sidelink control information (SCI) message, and sending information identifying resource availability includes: sending information identifying resource availability via a second SCI message at least partially based on the request for status information.

[0146] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, at least one of the first SCI message or the second SCI message is associated with SCI format 2-D.

[0147] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, information identifying resource availability is transmitted via at least one of: an inter-UE coordination message, a sidelink control information format 2-C message, one or more dedicated fields in a sidelink control information message, a PC5 MAC CE, a PC5 radio resource control message, or an activation message.

[0148] In a twelfth aspect, alone or in combination with one or more of aspects one to eleven, receiving data for rendering includes: receiving data for rendering based at least in part on at least one of: distance to a source of data for rendering, channel bandwidth, resource availability, type of communication link connection, channel conditions, side link operating frequency range, traffic characteristics, quality of service metrics, or quality of experience metrics.

[0149] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0150] Figure 9 9 is a diagram illustrating an example process 900 performed, for example, by a network node in accordance with the present disclosure. The example process 900 is an example in which a network node (eg, the network node 110) performs operations associated with signaling for XR rendering offload.

[0151] like Figure 9 As further shown, in some aspects, process 900 may include receiving data for rendering, wherein the data for rendering is based at least in part on a capability indicator (block 910). Figure 12 The depicted communications manager 150 and / or receiving component 1202) can receive data for rendering, wherein the data for rendering is based at least in part on the capability indicator, as described above.

[0152] like Figure 9 As further shown, in some aspects, process 900 may include sending rendered data in response to receiving data for rendering (block 920). Figure 12 The depicted communications manager 150 and / or sending component 1204) can send rendered data in response to receiving data for rendering, as described above.

[0153] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0154] In a first aspect, process 900 includes: rendering data to generate rendered data, and sending the rendered data includes: sending the rendered data at least in part based on the rendered data.

[0155] In a second aspect, alone or in combination with the first aspect, the capability indicator may include information identifying offloading capability or maximum offloading capacity.

[0156] In a third aspect, alone or in combination with one or more of the first and second aspects, the capability indicator may be conveyed or triggered using at least one of the following: UE 5G sidelink capability indicator, LTE sidelink capability indicator, NR sidelink capability indicator, NR unlicensed spectrum sidelink capability indicator, UECapabilityEnquirySidelink parameter, or UECapabilityInformationSidelink parameter.

[0157] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the data for rendering is a first part of the rendered data, where a second part of the rendered data is for rendering at another device associated with the capability indicator.

[0158] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, receiving data for rendering includes: receiving data for rendering via an access link.

[0159] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 900 includes: sending information identifying resource availability, and receiving data for rendering includes: receiving data for rendering at least in part based on resource availability.

[0160] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the capability indicator is conveyed via semi-static signaling, and the information identifying resource availability is sent via at least one of dynamic layer 1 signaling, MAC CE signaling, or semi-static signaling.

[0161] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, resource availability includes information identifying at least one of power usage or computing resource usage.

[0162] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, information indicating resource availability is conveyed via at least one of the following: inter-UE coordination messages, sidelink control information format 2-C messages, one or more dedicated fields in sidelink control information messages, PC5 MAC CE, PC5 radio resource control messages, or activation messages.

[0163] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, receiving data for rendering includes: receiving data for rendering based at least in part on at least one of the following: distance to the source of the data for rendering, channel bandwidth, resource availability, type of communication link connection, channel condition, sidelink operating frequency range, traffic characteristics, quality of service metric, or quality of experience metric.

[0164] Although Figure 9 example boxes of process 900 are shown, in some aspects, process 900 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to those depicted. Additionally or alternatively, two or more boxes of process 900 may be executed in parallel. Figure 9

[0165] Figure 10 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be an XR device, or an XR device may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may use receiving component 1002 and transmitting component 1004 to communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 1000 may include a communication manager 172. Communication manager 172 may include a rendering management component 1008, among others.

[0166] In some aspects, apparatus 1000 may be configured to perform one or more operations described herein in connection with Figure 6 Additional or alternative, apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 7 process 700. In some aspects, apparatus 1000 and / or Figure 10 one or more components shown may include one or more components of the XR device described in connection with Figure 2 Additional or alternative, Figure 10 one or more components shown may be in connection with Figure 2 ​implemented within one or more of the described components. Additionally or alternatively, one or more of the set of components may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the component.

[0167] The receiving component 1002 may receive communications from the device 1006, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing on the received communications (such as filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controller / processors, memories, or combinations thereof of the XR device described in conjunction with Figure 2 one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controller / processors, memories, or combinations thereof of the XR device described in conjunction with

[0168] The transmitting component 1004 may transmit communications to the device 1006, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 1000 may generate the communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing on the generated communications (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controller / processors, memories, or combinations thereof of the XR device described in conjunction with Figure 2 one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controller / processors, memories, or combinations thereof of the XR device described in conjunction with. In some aspects, the transmitting component 1004 may be co-located with the receiving component 1002 in a transceiver.

[0169] The receiving component 1002 may receive a UE capability indicator that identifies the rendering offloading capability of the UE. The transmitting component 1004 may transmit data for rendering at the UE at least partially based on the received UE capability indicator. The receiving component 1002 may receive the rendered data from the UE in response to transmitting the data for rendering at the UE.

[0170] The receiving component 1002 may receive information identifying UE resource availability. The transmitting component 1004 may request the status of the UE via a first SCI message. The rendering management component 1008 may partition data for offloaded rendering at one or more devices 1006 based at least in part on a UE capability indicator.

[0171] Figure 10 The number and arrangement of the components shown are provided as an example. In fact, there may be additional components, fewer components, different components, or components arranged in a different manner compared to Figure 10 those shown. Additionally, Figure 10 two or more of the components shown may be implemented within a single component, or Figure 10 a single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 10 a group (one or more) of the components shown may perform one or more functions described as being performed by Figure 10 another group of components shown.

[0172] Figure 11 is a diagram of an example apparatus 1100 for wireless communication in accordance with the present disclosure. The apparatus 1100 may be a UE, or the UE may include the apparatus 1100. In some aspects, the apparatus 1100 includes a receiving component 1102 and a transmitting component 1104 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1100 may use the receiving component 1102 and the transmitting component 1104 to communicate with another device 1106 (such as a UE, a base station, or another wireless communication device). As further shown, the apparatus 1100 may include a communication manager 140. The communication manager 140 may include a rendering component 1108 and so on.

[0173] In some aspects, the apparatus 1100 may be configured to perform one or more operations described herein in connection with Figure 6 the one or more processes described herein, such as Figure 8 process 800. In some aspects, the apparatus 1100 and / or Figure 11 one or more of the components shown may include one or more components of the UE described in connection with Figure 2 the one or more components shown may be implemented in connection with Figure 11 the one or more components shown may be implemented in connection with Figure 2implemented within the one or more components described. Additionally or alternatively, one or more of the set of components may be at least partially implemented as software stored in a memory. For example, a component (or a part of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0174] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controller / processors, memories, or combinations thereof of the UE described Figure 2 above.

[0175] The transmitting component 1104 may transmit communications to the device 1106, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 1100 may generate communications, and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding, etc.), and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controller / processors, memories, or combinations thereof of the UE described Figure 2 above. In some aspects, the transmitting component 1104 may be co-located with the receiving component 1102 in a transceiver.

[0176] The transmitting component 1104 may transmit a UE capability indicator indicating the rendering offloading capability. The receiving component 1102 may receive data for rendering at least partially based on the transmitted UE capability indicator. The transmitting component 1104 may transmit the rendered data in response to receiving the data for rendering.

[0177] The rendering component 1108 may render data to generate the rendered data. The transmitting component 1104 may transmit information indicating resource availability. The receiving component 1102 may receive a request for status information via a first SCI message.

[0178] Figure 11 The number and arrangement of the components shown are provided as an example. In fact, there may be additional components, fewer components, different components, or components arranged in a different manner compared to Figure 11 those shown. Additionally, Figure 11 two or more of the components shown may be implemented within a single component, or Figure 11 a single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 11 a set (one or more) of the components shown may perform one or more functions described as being performed by Figure 11 another set of components shown.

[0179] Figure 12 is a diagram of an example apparatus 1200 for wireless communication in accordance with the present disclosure. The apparatus 1200 may be a network node, or a network node may include the apparatus 1200. In some aspects, the apparatus 1200 includes a receiving component 1202 and a transmitting component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1200 may use the receiving component 1202 and the transmitting component 1204 to communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device). As further shown, the apparatus 1200 may include a communication manager 150. The communication manager 150 may include a rendering component 1208 and so on.

[0180] In some aspects, the apparatus 1200 may be configured to perform one or more operations described herein in connection with Figure 6 those described. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 9 process 900. In some aspects, the apparatus 1200 and / or Figure 12 one or more of the components shown may include one or more components of the network node described in connection with Figure 2 those described. Additionally or alternatively, Figure 12 one or more of the components shown may be implemented within one or more of the components described in connection with Figure 2 those described. Additionally or alternatively, one or more of the components in the set of components may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0181] The receiving component 1202 can receive communications from the device 1206, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1202 can provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and can provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 can include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the network node described in conjunction with Figure 2 one or more of the antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the network node described.

[0182] The transmitting component 1204 can send communications to the device 1206, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 1200 can generate the communications and can provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and can send the processed signals to the device 1206. In some aspects, the transmitting component 1204 can include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memories, or combinations thereof of the network node described in conjunction with Figure 2 one or more of the antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memories, or combinations thereof of the network node described. In some aspects, the transmitting component 1204 can be co-located with the receiving component 1202 in a transceiver.

[0183] The receiving component 1202 can receive data for rendering, where the data for rendering is at least partially based on a capability indicator. The transmitting component 1204 can send the rendered data in response to receiving the data for rendering. The rendering component 1208 can render the data to generate the rendered data. The transmitting component 1204 can send information identifying resource availability.

[0184] Figure 12 The number and arrangement of the components shown are provided as an example. In fact, there may be additional components, fewer components, different components, or components arranged in a different manner compared to Figure 12 those shown. Additionally, Figure 12 two or more of the components shown can be implemented within a single component, or Figure 12 a single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 a group (one or more) of the components shown can perform what is described as being performed by Figure 12One or more functions performed by another set of components shown.

[0185] Some aspects of the present disclosure are outlined below:

[0186] Aspect 1: A method of wireless communication performed by a device of a device, the method comprising: receiving a UE capability indicator identifying a rendering offloading capability of a user equipment (UE); sending data for rendering at the UE at least in part based on receiving the UE capability indicator; and receiving rendered data from the UE in response to sending the data for rendering at the UE.

[0187] Aspect 2: The method according to aspect 1, wherein the UE capability indicator can include information identifying an offloading capability or a maximum offloading capacity.

[0188] Aspect 3: The method according to any one of aspects 1 to 2, wherein the UE capability indicator can be conveyed or triggered using at least one of the following: a UE 5G sidelink capability indicator, a Long Term Evolution (LTE) sidelink capability indicator, a New Radio (NR) sidelink capability indicator, an NR unlicensed spectrum sidelink capability indicator, a UECapabilityEnquirySidelink parameter, or a UECapabilityInformationSidelink parameter.

[0189] Aspect 4: The method according to any one of aspects 1 to 3, wherein the data for rendering is a first part of the rendered data, and the rendered data is the first rendered data; and the method further comprises: sending a second part of the rendered data for rendering at a network node; and receiving second rendered data from the network node in response to sending the second part of the rendered data for rendering at the network node.

[0190] Aspect 5: The method according to any one of aspects 1 to 4, wherein sending the second part of the rendered data comprises: sending the second part of the rendered data at least in part based on an amount of the rendered data for rendering.

[0191] Aspect 6: The method according to any one of aspects 1 to 5, wherein sending the data for rendering comprises: sending the data for rendering via at least one of a licensed sidelink or an unlicensed sidelink.

[0192] Aspect 7: The method according to any one of aspects 1 to 6, the method further comprising: receiving information identifying UE resource availability; and wherein sending the data for rendering comprises: sending the data for rendering at least in part based on the UE resource availability.

[0193] Aspect 8: The method according to aspect 7, wherein the UE capability indicator is received via semi-static signaling, and the information identifying the UE resource availability is received via at least one of dynamic layer 1 signaling, medium access control (MAC) control element (CE) signaling, or semi-static signaling.

[0194] Aspect 9: The method according to aspect 7, wherein the UE resource availability includes information identifying at least one of power usage or computing resource usage.

[0195] Aspect 10: The method according to aspect 7, the method further comprising: requesting a state of the UE via a first sidelink control information (SCI) message; and wherein receiving the information identifying the UE resource availability includes: receiving the information identifying the UE resource availability via a second SCI message at least partially based on requesting the state of the UE.

[0196] Aspect 11: The method according to aspect 10, wherein at least one of the first SCI message or the second SCI message is associated with SCI format 2-D.

[0197] Aspect 12: The method according to aspect 7, wherein the information identifying the UE resource availability is conveyed via at least one of: an inter-UE coordination message, a sidelink control information format 2-C message, one or more dedicated fields in a sidelink control information message, a PC5 medium access control (MAC) control element, a PC5 radio resource control message, or an activation message.

[0198] Aspect 13: The method according to any one of aspects 1 to 12, wherein sending the data for rendering includes: sending the data for rendering at least partially based on at least one of: distance to the UE, channel bandwidth, resource availability, type of communication link connection, channel condition, sidelink operating frequency range, traffic characteristics, quality of service metric, or quality of experience metric.

[0199] Aspect 14: A method of wireless communication performed by a device of a user equipment (UE), the method comprising: sending a UE capability indicator identifying a rendering offloading capability; receiving data for rendering at least partially based on sending the UE capability indicator; and sending the rendered data in response to receiving the data for rendering.

[0200] Aspect 15: The method according to aspect 14, the method further comprising: rendering the data to generate the rendered data; and wherein transmitting the rendered data comprises: transmitting the rendered data at least in part based on rendering the data, wherein transmitting the rendered data comprises: sending the rendered data at least in part based on rendering the data.

[0201] Aspect 16: The method according to any one of aspects 14 to 15, wherein the UE capability indicator can include information identifying offloading capabilities or maximum offloading capacity.

[0202] Aspect 17: The method according to any one of aspects 14 to 16, wherein the UE capability indicator can be conveyed or triggered using at least one of the following: a UE 5G sidelink capability indicator, a Long Term Evolution (LTE) sidelink capability indicator, a New Radio (NR) sidelink capability indicator, an NR unlicensed spectrum sidelink capability indicator, a UECapabilityEnquirySidelink parameter, or a UECapabilityInformationSidelink parameter.

[0203] Aspect 18: The method according to any one of aspects 14 to 17, wherein the data for rendering is a first part of the rendering data, and a second part of the rendering data is for rendering at another device.

[0204] Aspect 19: The method according to any one of aspects 14 to 18, wherein receiving the data for rendering comprises: receiving the data for rendering via at least one of a licensed sidelink or an unlicensed sidelink.

[0205] Aspect 20: The method according to any one of aspects 14 to 19, the method further comprising: sending information identifying resource availability; and wherein receiving the data for rendering comprises: receiving the data for rendering at least in part based on the resource availability.

[0206] Aspect 21: The method according to aspect 20, wherein the UE capability indicator is sent via semi-static signaling, and the information identifying the resource availability is sent via at least one of dynamic layer 1 signaling, Medium Access Control (MAC) control element (CE) signaling, or semi-static signaling.

[0207] Aspect 22: The method according to aspect 20, wherein the resource availability includes information identifying at least one of power usage or computing resource usage.

[0208] Aspect 23: The method according to aspect 20, the method further comprising: receiving a request for status information via a first sidelink control information (SCI) message; and wherein transmitting the information identifying the resource availability comprises: transmitting the information identifying the resource availability via a second SCI message at least partially based on the request for the status information, wherein transmitting the information identifying the resource availability comprises: transmitting the information identifying the resource availability via a second SCI message at least partially based on the request for the status information.

[0209] Aspect 24: The method according to aspect 23, wherein at least one of the first SCI message or the second SCI message is associated with SCI format 2-D.

[0210] Aspect 25: The method according to aspect 20, wherein the information identifying the resource availability is conveyed via at least one of: an inter-UE coordination message, a sidelink control information format 2-C message, one or more dedicated fields in a sidelink control information message, a PC5 medium access control (MAC) control element, a PC5 radio resource control message, or an activation message.

[0211] Aspect 26: The method according to any one of aspects 14 to 25, wherein receiving the data for rendering comprises: receiving the data for rendering at least partially based on at least one of: the distance to the source of the data for rendering, the channel bandwidth, the resource availability, the type of communication link connection, the channel condition, the sidelink operating frequency range, the traffic characteristics, the quality of service metric, or the quality of experience metric.

[0212] Aspect 27: A method of wireless communication performed by an apparatus of a network node, the method comprising: receiving data for rendering, wherein the data for rendering is at least partially based on a capability indicator; and transmitting the rendered data in response to receiving the data for rendering.

[0213] Aspect 28: The method according to aspect 27, the method further comprising: rendering the data to generate the rendered data; and wherein transmitting the rendered data comprises: transmitting the rendered data at least partially based on rendering the data, wherein transmitting the rendered data comprises: transmitting the rendered data at least partially based on rendering the data.

[0214] Aspect 29: The method according to any one of aspects 27 to 28, wherein the capability indicator can include information identifying offloading capability or maximum offloading capacity.

[0215] Aspect 30: The method according to any one of aspects 27 to 29, wherein the capability indicator can be conveyed or triggered using at least one of the following: a UE 5G sidelink capability indicator, a Long-Term Evolution (LTE) sidelink capability indicator, a New Radio (NR) sidelink capability indicator, an NR unlicensed spectrum sidelink capability indicator, a UECapabilityEnquirySidelink parameter, or a UECapabilityInformationSidelink parameter.

[0216] Aspect 31: The method according to any one of aspects 27 to 30, wherein the data for rendering is a first part of the rendering data, and a second part of the rendering data is for rendering at another device associated with the capability indicator.

[0217] Aspect 32: The method according to any one of aspects 27 to 31, wherein receiving the data for rendering includes: receiving the data for rendering via an access link.

[0218] Aspect 33: The method according to any one of aspects 27 to 32, the method further includes: sending information identifying resource availability; and wherein receiving the data for rendering includes: receiving the data for rendering at least partially based on the resource availability.

[0219] Aspect 34: The method according to aspect 33, wherein the capability indicator is conveyed via semi-static signaling, and the information identifying the resource availability is sent via at least one of dynamic layer 1 signaling, Medium Access Control (MAC) control element (CE) signaling, or semi-static signaling.

[0220] Aspect 35: The method according to aspect 33, wherein the resource availability includes information identifying at least one of power usage or computing resource usage.

[0221] Aspect 36: The method according to aspect 33, wherein the information identifying the resource availability is conveyed via at least one of the following: an inter-UE coordination message, a sidelink control information format 2-C message, one or more dedicated fields in a sidelink control information message, a PC5 Medium Access Control (MAC) control element, a PC5 radio resource control message, or an activation message.

[0222] Aspect 37: The method according to any one of aspects 27 to 36, wherein receiving the data for rendering comprises: receiving the data for rendering at least in part based on at least one of the following: distance to the source of the data for rendering, channel bandwidth, resource availability, type of communication link connection, channel condition, sidelink operating frequency range, traffic characteristics, quality of service metric, or quality of experience metric.

[0223] Aspect 38: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1 to 13.

[0224] Aspect 39: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 13.

[0225] Aspect 40: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 13.

[0226] Aspect 41: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 13.

[0227] Aspect 42: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 13.

[0228] Aspect 43: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 14 to 26.

[0229] Aspect 44: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 14 to 26.

[0230] Aspect 45: An apparatus for wireless communication, the apparatus including at least one component for performing the method according to one or more of aspects 14 to 26.

[0231] Aspect 46: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to one or more of aspects 14 to 26.

[0232] Aspect 47: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set including one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 14 to 26.

[0233] Aspect 48: An apparatus for wireless communication at a device, the apparatus including: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 27 to 37.

[0234] Aspect 49: A device for wireless communication, the device including a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 27 to 37.

[0235] Aspect 50: An apparatus for wireless communication, the apparatus including at least one component for performing the method according to one or more of aspects 27 to 37.

[0236] Aspect 51: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to one or more of aspects 27 to 37.

[0237] Aspect 52: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set including one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 27 to 37.

[0238] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure, or may be obtained from practice of the aspects.

[0239] As used herein, the term "component" is intended to be broadly construed as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, "software" shall be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented by hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by different forms of hardware and / or combinations of hardware and software. The actual specific control hardware or software code used to implement these systems and / or methods does not limit the aspects. Thus, the operation and behavior of the systems and / or methods are not described herein with reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the description herein to implement the systems and / or methods.

[0240] As used herein, depending on the context, "meeting a threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0241] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the aspects. Many of these features can be combined in ways not specifically recited in the claims and / or not disclosed in the specification. The disclosure of each aspect includes each dependent claim in combination with every other claim in the claim set. As used herein, the phrase referring to "at least one of" a list of items refers to any combination of those items (which includes a single member). As an example, "at least one of a, b, or c" is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiple of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0242] None of the elements, acts, or instructions used herein should be construed as critical or essential unless explicitly described as such. Additionally, as used herein, the article "a" is intended to include one or more items and may be interchangeable with "one or more." Further, as used herein, the article "the" is intended to include one or more items mentioned in connection with the article "the" and may be interchangeable with "one or more." Additionally, as used herein, the terms "group" and "set" are intended to include one or more items and may be interchangeable with "one or more." If only one item is intended to be referred to, the phrase "only one" or similar language will be used. Additionally, as used herein, terms such as "having" are intended to be open-ended terms that do not limit the elements they modify (e.g., an element "having" A may also have B). Further, the phrase "based on" is intended to mean "at least partially based on" unless otherwise explicitly stated. Additionally, as used herein, the term "or" when used in a series is intended to be open-ended and may be interchangeable with "and / or" unless otherwise explicitly stated (e.g., if used in conjunction with "either" or "only one").

Claims

1. An extended reality (XR) device for wireless communication, the extended reality (XR) device comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to: receive a UE capability indicator identifying a rendering offloading capability of a user equipment (UE); send data for rendering at the UE to the UE at least in part based on receiving the UE capability indicator; and receive rendered data from the UE in response to sending the data for rendering at the UE.

2. The XR device according to claim 1, wherein the UE capability indicator can include information identifying an offloading capability or a maximum offloading capacity.

3. The XR device according to claim 1, wherein the UE capability indicator can be conveyed or triggered using at least one of the following: a UE 5G side link capability indicator, a Long Term Evolution (LTE) side link capability indicator, a New Radio (NR) side link capability indicator, an NR unlicensed spectrum side link capability indicator, a UECapabilityEnquirySidelink parameter, or a UECapabilityInformationSidelink parameter.

4. The XR device according to claim 1, wherein the data for rendering is a first part of the rendering data, and the rendered data is the first rendered data; and the XR device further comprises: send a second part of the rendered data for rendering at a network node to the network node; and receive second rendered data from the network node in response to sending the second part of the rendered data for rendering at the network node.

5. The XR device according to claim 4, wherein, in order to send the second part of the rendered data, the one or more processors are configured to: send the second part of the rendered data at least in part based on an amount of the rendering data for rendering.

6. The XR device according to claim 1, wherein, in order to send the data for rendering, the one or more processors are configured to: send the data for rendering via at least one of a licensed side link or an unlicensed side link.

7. The XR device according to claim 1, wherein the one or more processors are further configured to: receive information identifying UE resource availability; and wherein, in order to send the data for rendering, the one or more processors are configured to: send the data for rendering at least in part based on the UE resource availability.

8. The XR device according to claim 7, wherein the UE capability indicator is received via semi-static signaling, and the information identifying the UE resource availability is received via at least one of dynamic layer 1 signaling, Media Access Control (MAC) control element (CE) signaling, or semi-static signaling.

9. The XR device according to claim 7, wherein the UE resource availability includes information identifying at least one of power usage or computing resource usage.

10. The XR device according to claim 7, wherein the one or more processors are further configured to: request the status of the UE resources via a first sidelink control information (SCI) message; and wherein, in order to receive the information identifying the UE resource availability, the one or more processors are configured to: receive the information identifying the UE resource availability via a second SCI message based at least in part on requesting the status of the UE.

11. The XR device according to claim 10, wherein at least one of the first SCI message or the second SCI message is associated with SCI format 2-D.

12. The XR device according to claim 7, wherein the information identifying the UE resource availability is conveyed via at least one of the following: inter-UE coordination message, sidelink control information format 2-C message, one or more dedicated fields in the sidelink control information message, PC5 media access control (MAC) control element, PC5 radio resource control message, or activation message.

13. The XR device according to claim 1, wherein, in order to send the data for rendering, the one or more processors are configured to: send the data for rendering based at least in part on at least one of the following: distance to the UE, channel bandwidth, resource availability, type of communication link connection, channel condition, sidelink operating frequency range, traffic characteristic, quality of service metric, or quality of experience metric.

14. A user equipment (UE) for wireless communication, the user equipment (UE) comprises: a memory; and one or more processors coupled to the memory, the one or more processors being configured to: send a UE capability indicator identifying the rendering offloading capability; receive data for rendering based at least in part on sending the UE capability indicator; and send the rendered data in response to receiving the data for rendering.

15. The UE according to claim 14, wherein the one or more processors are further configured to: render the data to generate the rendered data; and wherein, in order to send the rendered data, the one or more processors are configured to: send the rendered data based at least in part on rendering the data.

16. The UE according to claim 14, wherein the UE capability indicator can include information identifying the offloading capability or the maximum offloading capacity.

17. The UE according to claim 14, wherein the UE capability indicator can be conveyed or triggered using at least one of the following: UE 5G sidelink capability indicator, Long Term Evolution (LTE) sidelink capability indicator, New Radio (NR) sidelink capability indicator, NR unlicensed spectrum sidelink capability indicator, UECapabilityEnquirySidelink parameter, or UECapabilityInformationSidelink parameter.

18. The UE according to claim 14, wherein the data for rendering is a first part of the rendering data, and a second part of the rendering data is for rendering at another device.

19. The UE according to claim 14, wherein in order to receive the data for rendering, the one or more processors are configured to: Receive the data for rendering via at least one of a licensed side link or an unlicensed side link.

20. The UE according to claim 14, wherein the one or more processors are further configured to: Send information identifying resource availability; and wherein in order to receive the data for rendering, the one or more processors are configured to: Receive the data for rendering at least in part based on the resource availability.

21. The UE according to claim 20, wherein the UE capability indicator is sent via semi-static signaling, and the information identifying the resource availability is sent via at least one of dynamic layer 1 signaling, media access control (MAC) control element (CE) signaling, or semi-static signaling.

22. The UE according to claim 20, wherein the resource availability includes information identifying at least one of power usage or computing resource usage.

23. The UE according to claim 20, wherein the one or more processors are further configured to: Receive a request for status information via a first side link control information (SCI) message; and wherein in order to send the information identifying the resource availability, the one or more processors are configured to: Send the information identifying the resource availability via a second SCI message at least in part based on the request for the status information.

24. The UE according to claim 23, wherein at least one of the first SCI message or the second SCI message is associated with SCI format 2-D.

25. The UE according to claim 20, wherein the information identifying the resource availability is conveyed via at least one of: Inter-UE coordination message, Side link control information format 2-C message, One or more dedicated fields in a side link control information message, PC5 media access control (MAC) control element, PC5 radio resource control message, or Activation message.

26. The UE according to claim 14, wherein in order to receive the data for rendering, the one or more processors are configured to: Receive the data for rendering at least in part based on at least one of: Distance to the source of the data for rendering, Channel bandwidth, Resource availability, Type of communication link connection, Channel condition, Side link operating frequency range, Traffic characteristics, Quality of service metric, or Quality of experience metric.

27. A network node for wireless communication, the network node comprising: A memory; and One or more processors coupled to the memory, the one or more processors being configured to: Receive data for rendering, wherein the data for rendering is at least partially based on a capability indicator; and Send rendered data as a response to the received data for rendering.

28. The network node according to claim 27, wherein the one or more processors are further configured to: Render the data to generate rendered data; and Wherein, for sending the rendered data, the one or more processors are configured to: Send the rendered data at least partially based on rendering the data.

29. The network node according to claim 27, wherein the capability indicator can include information identifying an offloading capability or a maximum offloading capacity.

30. A method of wireless communication performed by an apparatus of an extended reality (XR) device, the method comprises: Receive a UE capability indicator identifying a rendering offloading capability of a user equipment (UE); Send data for rendering at the UE to the UE at least partially based on receiving the UE capability indicator; and Receive rendered data from the UE as a response to sending the data for rendering at the UE.

Images