Dynamically distributed augmented reality computing

By deploying processors in user equipment, XR equipment and application servers of wireless communication systems, dynamically determining the computing location of XR data, the problem of poor XR data computing location management in existing systems is solved, and higher rendering quality and lower latency and power consumption are achieved.

CN120077621APending Publication Date: 2025-05-30QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380074296.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-03-01
Filing Date
2023-09-21
Publication Date
2025-05-30

AI Technical Summary

Technical Problem

When existing wireless communication systems provide dynamic distributed extended real-world computing services, it is difficult to effectively manage the computing location of XR data, resulting in unstable rendering quality, excessive delay and excessive power consumption.

Method used

By deploying processors in user equipment (UE), XR devices, and application servers, the computational location of associated XR data is dynamically determined and a computational location indication is selectively sent to the network nodes to optimize the distribution of XR computing resources.

Benefits of technology

It realizes dynamic adjustment of XR calculation position based on radio conditions, power consumption and prediction parameters, thereby improving rendering quality, reducing latency and optimizing power usage.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120077621A_ABST
    Figure CN120077621A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may determine an augmented reality (XR) calculation location of XR data associated with an XR device associated with the UE based at least in part on one or more parameters, where the XR calculation location corresponds to the UE, the XR device, or an application server associated with the XR data. The UE may selectively send an indication of the XR computed location to a network node. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross - reference to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 381,076, entitled "DYNAMIC DISTRIBUTED EXTENDED REALITY COMPUTE", filed on October 26, 2022, and U.S. Non - Provisional Patent Application No. 18 / 176,685, entitled "DYNAMIC DISTRIBUTED EXTENDED REALITY COMPUTE", filed on March 1, 2023, which are hereby incorporated by reference in their entirety. Technical Field

[0003] Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatus for dynamic distributed extended reality computing. 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 standard 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. The UE may communicate with the 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 improve spectral efficiency, reduce costs, enhance services, utilize new spectrums, and better integrate with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (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 supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technology, and carrier aggregation, so as to better support mobile broadband Internet access. With the continuous increase in the demand for mobile broadband access, further improvements to LTE, NR, and other radio access technologies are still useful. SUMMARY OF THE INVENTION

[0007] Some aspects described herein relate to a User Equipment (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: determine an XR computing location of XR data associated with an Extended Reality (XR) device associated with the UE, at least in part based on one or more parameters, wherein the XR computing location corresponds to the UE, the XR device, or an application server associated with the XR data. The one or more processors may be configured to: selectively send an indication of the XR computing location to a network node.

[0008] Some aspects described herein relate to an XR device for wireless communication. The XR device may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: determine an XR computing location of XR data associated with the XR device, at least in part based on one or more parameters, wherein the XR computing location corresponds to the XR device, a UE associated with the XR device, or an application server associated with the XR data. The one or more processors may be configured to: selectively send an indication of the XR computing location to a network node.

[0009] Some aspects described herein relate to an application server for wireless communication. The application server may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: determine an XR computing location of XR data associated with an XR device at least in part based on one or more parameters, where the XR computing location corresponds to the XR device, a UE associated with the XR device, or an application server associated with the XR data. The one or more processors may be configured to: selectively switch the XR computing location at least in part based on determining the XR computing location.

[0010] 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: determine an XR computing location of XR data associated with an XR device associated with the UE at least in part based on one or more parameters, where the XR computing location corresponds to the UE, the XR device, or an application server associated with the XR data. The set of instructions, when executed by one or more processors of the UE, may cause the UE to: selectively send an indication of the XR computing location to a network node.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication. The set of instructions, when executed by one or more processors of the XR device, may cause the XR device to: determine an XR computing location of XR data associated with the XR device at least in part based on one or more parameters, where the XR computing location corresponds to the XR device, a UE associated with the XR device, or an application server associated with the XR data. The set of instructions, when executed by one or more processors of the XR device, may cause the XR device to: selectively send an indication of the XR computing location to a network node.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions, when executed by one or more processors of the application server, may cause the application server to: determine an XR computing location of XR data associated with an XR device at least in part based on one or more parameters, where the XR computing location corresponds to the XR device, a UE associated with the XR device, or an application server associated with the XR data. The set of instructions, when executed by one or more processors of the application server, may cause the application server to: selectively switch the XR computing location at least in part based on determining the XR computing location.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for determining an XR computational location of XR data associated with an XR device associated with the apparatus, at least in part based on one or more parameters, where the XR computational location corresponds to the apparatus, the XR device, or an application server associated with the XR data. The apparatus may include components for selectively sending an indication of the XR computational location to a network node.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for determining an XR computational location of XR data associated with the apparatus, at least in part based on one or more parameters, where the XR computational location corresponds to the apparatus, a UE associated with the apparatus, or an application server associated with the XR data. The apparatus may include components for selectively sending an indication of the XR computational location to a network node.

[0015] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for determining an XR computational location of XR data associated with an XR device, at least in part based on one or more parameters, where the XR computational location corresponds to the XR device, a UE associated with the XR device, or an associated apparatus. The apparatus may include components for selectively switching the XR computational location, at least in part based on determining the XR computational location.

[0016] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include: determining an XR computational location of XR data associated with an XR device associated with the UE, at least in part based on one or more parameters, where the XR computational location corresponds to the UE, the XR device, or an application server associated with the XR data. The method may include: selectively sending an indication of the XR computational location to a network node.

[0017] Some aspects described herein relate to a method of wireless communication performed by an XR device. The method may include: determining an XR computational location of XR data associated with the XR device, at least in part based on one or more parameters, where the XR computational location corresponds to the XR device, a UE associated with the XR device, or an application server associated with the XR data. The method may include: selectively sending an indication of the XR computational location to a network node.

[0018] Some aspects described herein relate to a method of wireless communication performed by an application server. The method may include: determining an XR computational location of XR data associated with an XR device based at least in part on one or more parameters, where the XR computational location corresponds to the XR device, a UE associated with the XR device, or an application server associated with the XR data. The method may include: selectively switching the XR computational location based at least in part on determining the XR computational location.

[0019] Aspects generally include methods, apparatus, 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 as 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 hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out 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, as well as the 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 in the accompanying drawings is provided for purposes of illustration and description and is not 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 may be implemented in many different arrangements and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects may 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 may 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 may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may 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 wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of various 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 invention content briefly outlined above can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings only illustrate certain 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 may 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 a device designed for XR service applications according to the present disclosure.

[0027] Figures 5A to 5D is a diagram of an example of distributed XR computing according to the present disclosure.

[0028] Figure 6 is a diagram of an example of dynamic distributed XR computing according to the present disclosure.

[0029] Figure 7 is a diagram of an example of dynamic distributed XR computing according to the present disclosure.

[0030] Figure 8 is a diagram of an example of dynamic distributed XR computing according to the present disclosure.

[0031] Figure 9 is a diagram of an example of dynamic distributed XR computing according to the present disclosure.

[0032] Figure 10 is a diagram of an example of dynamic distributed XR computing according to the present disclosure.

[0033] Figure 11 is a diagram illustrating an example of a process, such as one performed by a UE, according to the present disclosure.

[0034] Figure 12 is a diagram illustrating an example of a process, such as one performed by an XR device, according to the present disclosure.

[0035] Figure 13FIG. is an illustration of an example process performed, for example, by an application server in accordance with the present disclosure.

[0036] Figure 14 FIG. is an illustration of an example apparatus for wireless communication in accordance with the present disclosure.

[0037] Figure 15 FIG. is an illustration of an example apparatus for wireless communication in accordance with the present disclosure.

[0038] Figure 16 FIG. is an illustration of an example apparatus for wireless communication in accordance with the present disclosure. DETAILED DESCRIPTION

[0039] 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 will understand that the scope of the present disclosure is intended to cover any aspect of the present 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 an apparatus or method practiced using other structures, functionality, or a combination of structures and functionality in addition to or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0040] 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 blocks, 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 upon the particular application and design constraints imposed on the overall system.

[0041] Although terms that are generally associated with 5G or new radio (NR) radio access technology (RAT) may be used herein to describe aspects, aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

[0042] Figure 1FIG. is an illustration of an example of a wireless network 100 in accordance with 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, etc. The wireless network 100 may include one or more network nodes 110 (shown as network nodes 110a, network nodes 110b, network nodes 110c, and network nodes 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UEs 120a, UEs 120b, UEs 120c, UEs 120d, and UEs 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).

[0043] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes 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. In some examples, the 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. The 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 transmit receive point (TRP), a DU, an 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, the network nodes 110 may be interconnected with each other or interconnected to one or more other network nodes 110 in the 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.

[0044] 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 macro cells, picocells, femtocells, and / or another type of cell. A macro cell may cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unrestricted access by UEs 120 with a service subscription. A picocell may cover a relatively small geographical area and may allow unrestricted access by UEs 120 with a service subscription. A femtocell may cover a relatively small geographical area (e.g., a home) and may allow restricted access by UEs 120 associated with the femtocell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). The network node 110 for a macro cell 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. In Figure 1 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 picocell 102b, and network node 110c may be a femto network node for femtocell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell 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).

[0045] In some aspects, the term "base station" or "network node" may refer to a centralized base station, a distributed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. 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 multiple different devices (which may be located in 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.

[0046] Wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions from an upstream node (e.g., network node 110 or UE 120) and forward the transmissions 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 UE120d 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 relay, etc.

[0047] Wireless network 100 may 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 may have different transmit power levels, different coverage areas, and / or different impacts on interference in wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watt to 2 watts).

[0048] 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 fronthaul communication link or a midhaul communication link. The network nodes 110 can also communicate directly with each other or indirectly via a wireless fronthaul communication link or a wired fronthaul 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.

[0049] UEs 120 can be distributed throughout the wireless network 100 and each UE 120 can be stationary or mobile. The UE 120 can include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. 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, a smart wristband, 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, the UE functionality of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

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

[0051] In some examples, the wireless network 100 may include an extended reality (XR) device 160. For example, the XR device 160 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 160 may be an example of the UE 120. In other words, some UEs 120 may be XR devices 160. XR functionality may include augmented reality (AR), virtual reality (VR), or mixed reality (MR), etc. For example, when providing XR services, the XR device 160 may provide rendered data via a display (such as a screen, a set of VR goggles, a heads-up display, or another type of display). The XR device 160 may be an augmented reality (AR) glasses device, a virtual reality (VR) glasses device, or other gaming devices.

[0052] 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. Each frequency in a given geographical area 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.

[0053] 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 the network node 110 as an intermediate device). For example, the 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) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or a mesh network to communicate. In such examples, the UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the network node 110.

[0054] Devices of the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, channels, etc. according to frequency or wavelength. For example, devices of the wireless network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been identified as Frequency Range Designation FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). It should be understood that although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is usually (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.

[0055] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified operating frequency bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can 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 frequency bands have been identified as Frequency Range Designation 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.

[0056] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" etc. is used in this article, this term can generally represent frequencies that can be below 6 GHz, can be within FR1, or can include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" etc. is used in this article, this term can generally represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can be within the EHF band. Considering that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described in this article apply to those modified frequency ranges.

[0057] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may determine an XR computing location of XR data associated with the XR device 160 associated with the UE 120 based at least in part on one or more parameters; and selectively send an indication of the XR computing location to the network node 110. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0058] 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 an indication of an XR computing location associated with the XR device 160; and may provide the indication of the XR computing location to the application server 180. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0059] In some aspects, the XR device 160 may include a communication manager 170. As described in more detail elsewhere herein, the communication manager 170 may determine an XR computing location of XR data associated with the XR device 160 based at least in part on one or more parameters; and selectively send an indication of the XR computing location to the network node 110. Additionally or alternatively, the communication manager 170 may perform one or more other operations described herein.

[0060] As Figure 1 Further shown, the application server 180 may be coupled to or communicate with one or more network controllers 130. The application server 180 may host applications such as game applications, video streaming applications, XR, VR, or AR applications and / or another type of application that provides a communication stream of streaming data between the UE 120 and the application server 180, between the XR device 160 and the application server 180, and / or between the application server 180 and another device in the wireless network 100. The application server 180 may be included in an edge server, a cloud environment, and / or another type of server environment. The UE 120 and / or the XR device 160 may execute an application client associated with the application hosted by the application server, such as a game application client, a video streaming application client, an XR, VR, or AR application client, and / or another type of application client.

[0061] In some aspects, the application server 180 may include a communication manager 190. As described in more detail elsewhere herein, the communication manager 190 may determine an XR computing location of XR data associated with the XR device 160 based at least in part on one or more parameters; and selectively switch the XR computing location based at least in part on the determined XR computing location. Additionally or alternatively, the communication manager 190 may perform one or more other operations described herein.

[0062] As indicated above, Figure 1 is provided as an example. Other examples may differ from the example Figure 1 described.

[0063] Figure 2 FIG. 200 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 or an XR device 160 in a wireless network 100 according to the present disclosure. The network node 110 may also communicate with a network controller 130 and may communicate with the application server 180 via the network controller 130. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 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, the XR device 160, 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 160, such as one or more CUs or one or more DUs.

[0064] At network node 110, transmit processor 220 may receive data destined for UE 120 or XR device 160 (or a set of UEs 120 or a set of XR devices 160) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 or XR device 160 at least in part based on one or more channel quality indicators (CQIs) received from the UE 120 or XR device 160. Network node 110 may process (e.g., encode and modulate) data for the UE 120 or XR device 160 at least in part based on the MCS selected for the UE 120 or XR device 160, and may provide data symbols for the UE 120 or XR device 160. 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 through 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 corresponding modulator component to obtain an output sample stream. Each modem 232 may also process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) using the corresponding modulator component to obtain a downlink signal. Modems 232a through 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 through 234t).

[0065] At the UE 120 or XR device 160, a set of antennas 252 (shown as antennas 252a through 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 through 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 where 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 for the UE 120 or XR device 160 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 160 may be included in the housing 284.

[0066] The network controller 130 may include a communication unit 290, a controller / processor 286, and a memory 288. 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 and / or the application server 180 via the communication unit 290.

[0067] The application server 180 may include a communication unit 296, a controller / processor 292, and a memory 294. In some aspects, the application server 180 includes a communication manager 190. The application server 180 may communicate with the network controller 130 via the communication unit 296.

[0068] One or more antennas (e.g., antennas 234a through 234t and / or antennas 252a through 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

[0069] On the uplink, at the UE 120 or XR device 160, 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. Symbols from the transmit processor 264 may be pre-coded by the TX MIMO processor 266 when applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 or XR device 160 may include a modulator and a demodulator. In some examples, the UE 120 or XR device 160 includes a transceiver. The transceiver may include any combination of the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and / or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller / processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figures 5A to 16 ).

[0070] At network node 110, an uplink signal from UE 120 or XR device 160 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., the demodulator component of modem 232, shown as DEMOD), detected (where applicable) by MIMO detector 236, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120 or XR device 160. Receive processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, modem 232 of network node 110 may include a modulator and a demodulator. In some examples, 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 aspects of any of the methods described herein (e.g., with reference to Figures 5A to 16 ).

[0071] Controller / processor 240 of network node 110, controller / processor 280 of UE 120 or XR device 160, and / or Figure 2 any other components may perform one or more techniques associated with dynamic distributed XR computing, as described in more detail elsewhere herein. For example, controller / processor 240 of network node 110, controller / processor 280 of UE 120 or XR device 160, and / or Figure 2 any other components may execute or direct, for example, Figure 11 process 1100, Figure 12 process 1200, Figure 13The operations of process 1300 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120 or XR device 160, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when executed by one or more processors of network node 110 and / or UE 120 or XR device 160 (e.g., directly executed, or after compilation, conversion, and / or interpretation), the one or more instructions may cause the one or more processors, UE 120 or XR device 160, and / or network node 110 to perform or direct, for example Figure 11 process 1100, Figure 12 process 1200, Figure 13 the operations of process 1300 and / or other processes as described herein. In some examples, executing the instructions may include running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, etc.

[0072] In some aspects, UE 120 includes components for determining an XR computing location of XR data associated with XR device 160 associated with UE 120, at least in part based on one or more parameters, where the XR computing location corresponds to UE 120, XR device 160, or application server 180 associated with the XR data; and / or components for selectively sending an indication of the XR computing location to network node 110. The components for UE 120 to perform the operations described herein may include, for example, one or more of 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.

[0073] In some aspects, XR device 160 includes components for determining an XR computing location of XR data associated with XR device 160, at least in part based on one or more parameters, where the XR computing location corresponds to XR device 160, UE 120 associated with XR device 160, or application server associated with the XR data; and / or components for selectively sending an indication of the XR computing location to network node 110. In some aspects, the components for XR device 160 to perform the operations described herein may include, for example, one or more of communication manager 170, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0074] In some aspects, the application server 180 includes components for determining an XR computing location of XR data associated with the XR device 160 based at least in part on one or more parameters, where the XR computing location corresponds to the XR device 160, the UE 120 associated with the XR device 160, or the application server 180 associated with the XR data; and / or components for selectively switching the XR computing location based at least in part on the determined XR computing location. In some aspects, the components for the application server 180 to perform the operations described herein may include, for example, one or more of a communication manager 190, a controller / processor 292, a memory 294, and a communication unit 296.

[0075] While Figure 2 the blocks in are illustrated as separate components, the functions described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functions described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

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

[0077] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. 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 an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station (BS), a 5G NB, an access point (AP), a TRP, or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as a stand-alone base station or a monolithic base station) or a disaggregated base station. A "network entity" or "network node" may refer to a disaggregated base station or one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0078] ​A centralized base station (e.g., a centralized network node) may 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 split base station (e.g., a split network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more CUs, one or more DUs, or one or more RUs. In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually spread across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may 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.

[0079] Base station type operations or network designs may consider the aggregation characteristics of base station functionality. For example, a split base station may be utilized in an IAB network, an open radio access network (O-RAN, such as a network configuration advocated 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 separately. A split base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may achieve flexibility in network design. Each unit of a split base station may be configured for wired or wireless communication with at least one other unit of the split base station.

[0080] Figure 3 FIG. is an illustration of an example split base station architecture 300 in accordance with the present disclosure. The split 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 split 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 330 among the DUs 330 may communicate with one or more RUs 340 via a respective fronthaul link. Each RU 340 among the RUs 340 may communicate with one or more UEs 120 or XR devices 160 via a respective radio frequency (RF) access link. In some implementations, a UE 120 or an XR device 160 may be served simultaneously by multiple RUs 340.

[0081] Each unit in the unit (including 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, and the one or more interfaces are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit in the unit or the associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more units in other units via the transmission medium. In some examples, each unit in the unit may include a wired interface and a wireless interface. The wired interface is configured to receive signals or transmit signals to one or more units in other units via a wired transmission medium. The wireless interface may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), and the wireless interface is configured to receive signals or transmit signals to one or more units in other units via a wireless transmission medium or perform both.

[0082] In some aspects, 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, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to convey signals to other control functions hosted by CU 310. 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 specific implementations, CU 310 may be logically divided 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 bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0083] 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 high physical (PHY) layers at least partially according to a functional split (such as the functional split defined by 3GPP). In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, which may be 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, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

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

[0085] The SMO framework 305 can be configured to support the RAN deployment and orchestration of 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 operation and maintenance interfaces (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 aspect 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 directly communicate 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.

[0086] The non-RT RIC 315 can be configured to include logical functions that can enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and update, or policy-based guidance for 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 logical functions that enable near-real-time control and optimization of RAN elements and resources through an interface (such as via the E2 interface) via 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.

[0087] In some specific implementations, to generate the AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may 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 may be configured to tune the RAN behavior or performance. For example, the non-RT RIC 315 may monitor the long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

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

[0089] Figure 4 is a diagram illustrating an example 400 of a device designed for XR service applications according to the present disclosure. As Figure 4 shown, the XR device 160 may communicate with the application server 180.

[0090] In some aspects, the XR device 160 communicates with the application server 180 via the UE 120 that communicates with a network node 110 in the wireless network 100. Here, the UE 120 may be communicatively connected to the XR device 160 via a wired (e.g., Universal Serial Bus (USB), Serial ATA (SATA)) and / or wireless (e.g., Bluetooth, Wi-Fi, 5G) connection.

[0091] In some aspects, the XR device 160 communicates with the application server 180 without using an intermediate UE 120. Here, the XR device 160 communicates wirelessly with a network node 110 in the wireless network 100 to communicate with the application server 180.

[0092] As indicated above, the application server 180 may host applications (e.g., XR applications or applications with XR support). The UE 120 or the XR device 160 may execute an application client that communicates with the applications hosted by the application server 180. Applications for the XR device 160 (or for another type of gaming device such as the UE 120) may include video games (e.g., where multimedia traffic is delivered to and from the application server 180 at a specific frame rate to support audio and / or video rendering) and / or VR environments (e.g., where multimedia traffic is delivered to and from the application server 180 at a specific polling rate to support sensor input (e.g., 6 degrees of freedom (6DOF) sensor input and feedback)), and so on. Some applications (including applications for XR, VR, AR, and / or gaming) may require low-latency traffic to and from an edge server or a cloud environment. The traffic to and from the edge server or the cloud environment may be periodic to support a specific frame rate (e.g., 120 frames per second (FPS), 90 FPS, 60 FPS), a specific refresh rate (e.g., 500 Hertz (Hz), 120 Hz), and / or a specific data transfer rate (e.g., 8 megabits per second (Mbps), 30 Mbps, 45 Mbps) for XR traffic applications.

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

[0094] The application may be executed by an application processor of an associated UE and / or by the XR device. In some aspects, the XR device may have limited battery life and / or limited processing power. In these aspects (and / or in other aspects), the UE may perform operations for the XR device so that the XR device may conserve processing and / or battery resources. These operations may include rendering XR data (e.g., rendering XR video, rendering XR audio), head tracking, hand tracking, and / or pose tracking, and so on. Additionally or alternatively, rendering of XR data for the XR device may be performed at the application server so that the rendered XR data is provided to the XR device (directly or via the UE). In addition to conserving the processing and / or battery resources of the XR device, this may also conserve the processing and / or battery resources of the UE and may improve the rendering quality. Furthermore, this may enable more resource-intensive operations, such as rendering, to be performed remotely while less resource-intensive and latency-sensitive operations, such as hand / head tracking, are performed locally at the UE and / or the XR device.

[0095] However, due to the propagation delay between the application server and the application client executed by the XR device or UE, offloading resource-intensive operations to the application server may result in an increase in latency when delivering XR data to the XR device or UE. In addition, poor radio conditions on the wireless communication link between the network node and the XR device or UE can also increase the latency when delivering XR data and / or may result in the dropping or non-receipt of XR data, thereby degrading the quality of the video and / or audio rendered for the application client.

[0096] Some aspects described herein provide dynamic distributed XR computing. In some aspects described herein, resource-intensive XR operation tasks, such as XR rendering, can be dynamically distributed based at least in part on one or more parameters associated with the XR device 160 and / or the UE 120. In some aspects, other XR operation tasks, such as head tracking, hand tracking, and / or pose tracking, etc., can be dynamically distributed. In some aspects, the UE 120 or the XR device 160 can determine the location where XR data associated with the XR device 160 is to be rendered based at least in part on the radio conditions between the UE 120 or the XR device 160 and the network node 110, at least in part on the power consumption of the XR device 160, the UE 120, and / or the application server 180, at least in part on a radio condition prediction associated with the XR device 160 and / or the UE 120, and / or at least in part on another parameter.

[0097] As described herein, determining the XR computing location of XR data refers to determining or selecting the device on which to perform the XR computing of the XR data. Thus, if the XR computing location is determined to be the UE 120, the UE 120 will perform the XR computing of the XR data. Alternatively, if the XR computing location is determined to be the application server 180, the application server 180 will perform the XR computing of the XR data.

[0098] In this way, the techniques described herein enable the location where XR operations are to be performed for the XR device 160 to be dynamically changed based at least in part on various conditions that can affect the rendering quality, latency, power consumption, and / or data rate of XR data delivery of the XR device 160 and / or the UE 120. Thus, the techniques described herein can provide improved rendering quality for the application client of the XR device 160, can provide an improved user experience for the XR device 160, and / or can increase or extend the battery life of the XR device 160 and / or the UE 120, etc.

[0099] Figures 5A to 5D is a diagram of an example of distributed XR computing according to the present disclosure. As Figures 5A to 5DAs shown, examples of distributed XR computing may include XR device 160, UE 120, network node 110, and / or application server 180, etc.

[0100] Figure 5A Example 500 of distributed XR computing is illustrated. As Figure 5A shown, XR device 160 may communicate with UE 120. UE 120 may communicate with network node 110. Network node 110 may communicate with application server 180. Thus, XR device 160 may communicate with application server 180 via UE 120 and network node 110, and UE 120 may communicate with application server 180 via network node 110.

[0101] As Figure 5A further shown, XR computing of XR data (e.g., associated with an application hosted by application server 180 and associated with an application client on XR device 160 and / or on UE 120) may be performed by application server 180. The XR data may include raw video data (e.g., data to be used for generating a video stream), etc. Thus, in example 500, the XR computing location is application server 180. Application server 180 performs XR computing of the XR data and provides XR rendering data (e.g., a rendered video stream, a rendered audio stream) to XR device 160 via network node 110 and via UE 120. UE 120 acts as a pathway because UE 120 forwards or relays the XR rendering data to XR device 160, which is tethered to UE 120. The connection between XR device 160 and UE 120 does not need to be merely tethered; other types of connections, such as Wi-Fi, may also be used.

[0102] In addition to XR rendering data, other types of communications may be sent and received by network node 110, UE 120, XR device 160, and / or application server 180. For example, application server 180 may provide aggregated application information to UE 120 and / or another type of application information that supports XR computing of XR data at UE 120. Also, for example, downlink communications and / or uplink communications may be exchanged by network node 110, UE 120, XR device 160, and / or application server 180.

[0103] Figure 5B Another example 505 of distributed XR computing is illustrated. XR device 160 may communicate with UE 120. UE 120 may communicate with network node 110. Network node 110 may communicate with application server 180. Thus, XR device 160 may communicate with application server 180 via UE 120 and network node 110, and UE 120 may communicate with application server 180 via network node 110.

[0104] As Figure 5B As further shown, the XR calculations of XR data can be performed by the UE 120 associated with the XR device 160. Thus, in Example 505, the XR calculation location is the UE 120. In some specific implementations, the application server 180 provides an indication to the UE 120 via the network node 110 to perform XR calculations for the XR device 160. The UE 120 receives the indication and performs the XR calculations of the XR data. The UE 120 provides the XR rendering data to the XR device 160.

[0105] When providing XR rendering data from the UE 120 to the XR device 160, other types of communication can be exchanged between the network node 110, the UE 120, the XR device 160, and / or the application server 180. For example, the application server 180 can provide aggregated application information and / or another type of application information that supports the XR calculations of XR data at the UE 120. Also, for example, downlink communication and / or uplink communication can be exchanged between the network node 110, the UE 120, the XR device 160, and / or the application server 180.

[0106] Figure 5C Figure 5C Another example 510 of distributed XR calculations is illustrated. As Figure 5C shown, the XR device 160 can communicate with the application server 180 via the network node 110. The XR device 160 can communicate directly with the network node 110 (e.g., without communicating through the associated UE 120).

[0107] As Figure 5C As further shown, the XR calculations of XR data can be performed by the application server 180. Thus, in Example 510, the XR calculation location is the application server 180. The application server 180 performs the XR calculations of the XR data and provides the XR rendering data to the XR device 160 via the network node 110.

[0108] In addition to the XR rendering data, other types of communication can be sent and received by the network node 110, the XR device 160, and / or the application server 180. For example, the application server 180 can provide aggregated application information and / or another type of application information that supports the XR calculations of XR data at the XR device 160. Also, for example, downlink communication and / or uplink communication can be exchanged between the network node 110, the XR device 160, and / or the application server 180.

[0109] Figure 5DIllustrates another example 515 of distributed XR computing. The XR device 160 can communicate with the application server 180 via the network node 110. The XR device 160 can communicate directly with the network node 110 (e.g., without communicating via the associated UE 120).

[0110] As Figure 5D Further shown, the XR computing of XR data can be performed by the XR device 160. Thus, in example 515, the XR computing location is the XR device 160. The application server 180 provides an indication to the XR device 160 via the network node 110 to perform XR computing for the XR device 160. The XR device 160 receives the indication from the application server 180 via the network node 110.

[0111] When XR rendering data is generated at the XR device 160, other types of communication can be exchanged between the network node 110, the XR device 160, and / or the application server 180. For example, the application server 180 can provide aggregated application information and / or another type of application information that supports the XR computing of XR data at the XR device 160. Also, downlink communication and / or uplink communication can be exchanged by the network node 110, the XR device 160, and / or the application server 180.

[0112] As indicated above, Figures 5A to 5D is provided as an example. Other examples may be different from the examples described with respect to Figures 5A to 5D what is described.

[0113] Figure 6 is a diagram of an example 600 of dynamic distributed XR computing according to the present disclosure. As Figure 6 shown, the example 600 of dynamic distributed XR computing can include the XR device 160, the UE 120, the network node 110, and / or the application server 180, etc.

[0114] As described above, resource-intensive XR operation tasks, such as XR rendering, can be dynamically distributed based at least in part on one or more parameters associated with the XR device 160 and / or the UE 120, etc.

[0115] At 605, the UE 120 can determine the XR computing location for rendering the XR data associated with the XR device 160. As described above, determining the XR computing location of XR data means determining or selecting the device to perform the XR computing of the XR data. Thus, if the UE 120 determines that the XR computing location will be the UE 120, the UE 120 determines that the UE 120 will perform XR rendering (and other XR computing tasks) of the XR data for the XR device 160. This is referred to as "local rendering" or "local computing", and at Figure 5BIllustrated in Example 505 of

[0116] Alternatively, if the UE 120 determines the XR computing location as the application server 180, the UE 120 determines that the application server 180 will perform XR computing of XR data for the XR device 160. This is referred to as "remote rendering" or "remote computing", and is illustrated in Figure 5A Example 500 of

[0117] The UE 120 may determine the XR computing location at least in part based on the radio conditions between the UE 120 and the network node 110 and / or between the XR device 160 and the network node 110, at least in part based on the power consumption of the XR device 160 and / or the UE 120, at least in part based on the radio condition prediction associated with the XR device 160 and / or the UE 120, and / or at least in part based on another parameter.

[0118] The radio condition between the UE 120 and the network node 110 may correspond to (or may be indicated by) one or more radio device parameters associated with the radio device link (e.g., uplink and / or downlink) between the UE 120 and the network node 110. The one or more radio device parameters may include RSRP on the uplink and / or downlink, RSSI on the uplink and / or downlink, RSRQ on the uplink and / or downlink, and / or CQI on the uplink and / or downlink, and / or enhanced link capacity estimate (eLCE), etc. The radio device parameters may be at least in part based on the input from the modem 254 of the UE 120 and / or at least in part based on another component of the UE 120.

[0119] The UE 120 may determine the XR computing location at least in part based on whether the radio device parameters meet a threshold. For example, if the RSRP meets (e.g., exceeds, equals) the RSRP threshold, the UE 120 may determine the XR computing location as the application server 180. Another example is that if the RSRP does not meet (e.g., is less than, equals) the RSRP threshold, the UE 120 may determine the XR computing location as the UE 120.

[0120] For another example, if the eLCE meets (e.g., exceeds, equals) the eLCE threshold, the UE 120 may determine the XR computing location as the application server 180. For another example, if the eLCE does not meet (e.g., is less than, equals) the eLCE threshold, the UE 120 may determine the XR computing location as the UE 120. The eLCE may refer to the estimated available capacity on the radio device link between the UE 120 and the network node 110. The eLCE threshold may be at least partially based on the application hosted by the application server 180 and the bit rate required by the associated application client on the XR device 160 and / or the UE 120. For example, the UE 120 may determine the eLCE threshold to be at least partially based on a bit rate of approximately 8 Mbps for a cloud gaming application. For another example, the UE 120 may determine the eLCE threshold to be at least partially based on a bit rate of approximately 30 Mbps for an AR application. For another example, the UE 120 may determine the eLCE threshold to be at least partially based on a bit rate of approximately 45 Mbps for a VR application.

[0121] The radio condition prediction associated with the XR device 160 and / or the UE 120 may include one or more sensor-based perceptions of the XR device 160 and / or the UE 120, may include one or more RF-based measurement perceptions of the XR device 160 and / or the UE 120, and / or other perceptions of the XR device 160 and / or the UE 120. The radio condition prediction enables the fusion of RF measurements, camera, and sensor perceptions, such that the modem 254 of the UE 120 can detect early sudden radio changes that may occur at least partially based on radio device link blockage, changes in the RF environment of the UE 120, and / or at least partially based on another radio condition change that may not be perceivable based on radio device measurements.

[0122] The power consumption of the UE 120 and / or the XR device 160 may include the estimated power consumption of the UE 120 and / or the XR device 160 for different XR computing locations. As an example, if the XR computing location is the UE 120 (e.g., if the UE 120 is to perform XR calculations for the XR device 160), the UE 120 may determine a first estimated power consumption (P_local) of the UE 120, and if the XR computing location is the application server 180 (e.g., if the application server 180 is to perform XR calculations for the XR device 160), the UE may determine a second estimated power consumption (P_remote) of the UE 120. If the second estimated power consumption is greater than the first estimated power consumption (e.g., if P_remote > P_local), the UE 120 may determine the XR computing location as the UE 120. Alternatively, if the first estimated power consumption is greater than the second estimated power consumption (e.g., if P_remote < P_local), the UE 120 may determine the XR computing location as the application server 180.

[0123] The estimated power consumption may include a combination of the estimated radio device power consumption (P_radio) of the UE 120 and the estimated XR computing power consumption (P_compute) of the UE 120. The estimated radio device power consumption may be the peak radio device power consumption, the average radio device power consumption, or a combination thereof. The UE 120 may determine the estimated radio device power consumption at least in part based on information provided by the modem 254 of the UE 120, which may include data rate, transmit power, device latency period, and / or channel utilization, as well as other parameters.

[0124] The estimated XR computing power consumption may be the peak XR computing power consumption, the average XR computing power consumption, or a combination thereof. The UE 120 may determine the estimated XR computing power consumption at least in part based on the type of computing tasks to be performed for the XR calculations and / or historical measurements of the power consumption of the computing tasks of the controller / processor 280 of the UE 120 (e.g., the central processing unit (CPU) of the UE 120, the graphics processing unit (GPU) of the UE 120).

[0125] The UE 120 may determine an estimated power consumption (e.g., P_local, P_remote) at least in part based on an estimated radio device power consumption and an estimated XR computing power consumption (e.g., P_radio+P_compute). Specifically, the UE 120 may determine a first estimated power consumption as P_local = P_radio_local+P_compute_local, and may determine a second estimated power consumption as P_remote = P_radio_remote+P_compute_remote.

[0126] In some aspects, the UE 120 may determine the XR computing location at least in part based on other parameters such as the packet loss rate between the application client at the XR device 160 and the network node 110, the round-trip time (RTT) between the application client at the XR device 160 and the network node 110, the server load associated with the application server 180, and / or the network load associated with the network node 110, etc.

[0127] For example, if the packet loss rate meets (e.g., exceeds, equals) the packet loss rate threshold, the UE 120 may determine the XR computing location as the UE 120. Also, if the packet loss rate does not meet (e.g., is less than, equals) the packet loss rate threshold, the UE 120 may determine the XR computing location as the application server 180.

[0128] Also, if the RTT meets (e.g., exceeds, equals) the RTT threshold, the UE 120 may determine the XR computing location as the UE 120. Also, if the RTT does not meet (e.g., is less than, equals) the RTT threshold, the UE 120 may determine the XR computing location as the application server 180.

[0129] Also, if the server load meets (e.g., exceeds, equals) the server load threshold, the UE 120 may determine the XR computing location as the UE 120. Also, if the server load does not meet (e.g., is less than, equals) the server load threshold, the UE 120 may determine the XR computing location as the application server 180. Generally speaking, the greater the server load, the fewer resources available for allocation to the UE 120, which may lead to an increase in latency even if the radio conditions on the radio device link between the UE 120 and the network node 110 are satisfactory.

[0130] As another example, if the network load meets (e.g., exceeds, equals) the network load threshold, the UE 120 may determine the XR computing location as the UE 120. As another example, if the network load does not meet (e.g., is less than, equals) the network load threshold, the UE 120 may determine the XR computing location as the application server 180. Generally speaking, the greater the network load, the fewer resources available for allocation to the UE 120, which may lead to increased latency even if the radio conditions on the radio device link between the UE 120 and the network node 110 are satisfactory.

[0131] In some aspects, the UE 120 may determine the XR computing location at least in part based on a combination of the above parameters (and / or other parameters). For example, the UE 120 may assign appropriate weights to one or more of these parameters and may determine the XR computing location at least in part based on the weighted parameters. As an example, even if the radio conditions on the radio device link between the UE 120s at the network node 110 degrade, if the power consumption at the UE 120 in the case where the UE 120 performs XR computing is greater than the power consumption at the UE 120 in the case where the application server 180 performs XR computing (e.g., if (P_remote < P_local)), the UE 120 may still maintain the XR computing location as the application server 180.

[0132] As Figure 6 As further shown, at 610, the UE 120 may selectively send an indication of the XR computing location to one or more devices (such as the application server 180 and / or the XR device 160). The UE 120 may selectively send an indication of the XR computing location to the application server 180 via the network node 110. The UE 120 may selectively send an indication of the XR computing location to the application server 180 because in some aspects, if the XR computing location determined by the UE 120 is different from the current XR computing location, the UE 120 sends an indication of the XR computing location. Otherwise, if the XR computing location determined by the UE 120 is the same as the current XR computing location (e.g., if the XR computing location has not changed), the UE 120 may avoid sending an indication of the XR computing location.

[0133] For example, if the current XR computing location is UE 120 and UE 120 determines that the XR computing location will be the application server 180, UE 120 may send an indication of the XR computing location to the application server 180. This enables the application server 180 to switch the XR computing location from UE 120 to the application server 180. As another example, if the current XR computing location is the application server 180 and UE 120 determines that the XR computing location will be UE 120, UE 120 may send an indication of the XR computing location to the application server 180. This enables the application server 180 to switch the XR computing location from the application server 180 to UE 120.

[0134] As another example, if the current XR computing location is UE 120 and UE 120 determines that the XR computing location will be UE 120, UE 120 may avoid sending an indication of the XR computing location to the application server 180 because the application server 180 does not need to change the XR computing location. This reduces the consumption of processing and memory resources of UE 120 and the network node 110, and reduces the consumption of radio device link resources between UE 120 and the network node 110. As another example, if the current XR computing location is the application server 180 and UE 120 determines that the XR computing location will be the application server 180, UE 120 may avoid sending an indication of the XR computing location to the application server 180.

[0135] Alternatively, even if the XR computing location determined by UE 120 is the same as the current XR computing location, UE 120 may send an indication of the XR computing location to the application server 180.

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

[0137] Figure 7 is a diagram of an example 700 of dynamic distributed XR computing according to the present disclosure. As Figure 7 shown, the example 700 of dynamic distributed XR computing may include an XR device 160, UE 120, a network node 110, and / or an application server 180, etc. In some aspects, UE 120 may be omitted, and the XR device 160 may communicate directly with the network node 110 to communicate with the application server 180.

[0138] As described above, resource-intensive XR computing tasks, such as XR rendering, may be dynamically distributed based at least in part on one or more parameters associated with the XR device 160 and / or UE 120, etc.

[0139] At 705, the XR device 160 may determine an XR computing location at which XR data associated with the XR device 160 is to be rendered. The XR device 160 may use similar techniques as described above in connection with Figure 6 to determine the XR computing location. If the XR device 160 determines that the XR computing location will be the UE 120, the XR device 160 determines that the UE 120 will perform XR computing of the XR data for the XR device 160. This is referred to as "local rendering" or "local computing", and is illustrated in Figure 5B Example 505.

[0140] Alternatively, if the XR device 160 determines the XR computing location to be the XR device 160, the XR device 160 determines that the XR device 160 will perform XR computing of the XR data for the XR device 160. This may also be referred to as "local rendering" or "local computing", and is illustrated in Figure 5D Example 505.

[0141] Alternatively, if the XR device 160 determines the XR computing location to be the application server 180, the XR device 160 determines that the application server 180 will perform XR computing of the XR data for the XR device 160. This is referred to as "remote rendering" or "remote computing", and is illustrated in Figure 5A Example 500 and in Figure 5C Example 510.

[0142] As Figure 7 further shown, at 710, the XR device 160 may selectively send an indication of the XR computing location to the application server 180. In some aspects, the XR device 160 may selectively send an indication of the XR computing location to the application server 180 via the network node 110 (e.g., without sending an indication of the XR computing location via the UE 120). In some aspects, the XR device 160 may selectively send an indication of the XR computing location to the application server 180 via the UE 120 and the network node 110.

[0143] The XR device 160 may selectively send an indication of the XR computing location to the application server 180 because in some aspects, if the XR computing location determined by the XR device 160 is different from the current XR computing location, the XR device 160 sends an indication of the XR computing location. Otherwise, if the XR computing location determined by the XR device 160 is the same as the current XR computing location (e.g., if the XR computing location has not changed), the XR device 160 may avoid sending an indication of the XR computing location.

[0144] For example, if the current XR computing location is the XR device 160, and the XR device 160 determines that the XR computing location will be the application server 180, the XR device 160 may send an indication of the XR computing location to the application server 180. This enables the application server 180 to switch the XR computing location from the UE 120 to the application server 180. As another example, if the current XR computing location is the application server 180, and the XR device 160 determines that the XR computing location will be the UE 120, the XR device 160 may send an indication of the XR computing location to the application server 180. This enables the application server 180 to switch the XR computing location from the application server 180 to the UE 120.

[0145] As another example, if the current XR computing location is the UE 120, and the XR device 160 determines that the XR computing location will be the UE 120, the XR device 160 may avoid sending an indication of the XR computing location to the application server 180 because the application server 180 does not need to change the XR computing location. This reduces the consumption of processing and memory resources of the XR device 160, the UE 120, and / or the network node 110, and reduces the consumption of radio device link resources between the UE 120 and the network node 110. As another example, if the current XR computing location is the application server 180, and the XR device 160 determines that the XR computing location will be the application server 180, the XR device 160 may avoid sending an indication of the XR computing location to the application server 180.

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

[0147] Figure 8 is a diagram of an example 800 of dynamic distributed XR computing according to the present disclosure. The operations described in connection with example 800 may be performed by the UE 120 and / or the XR device 160.

[0148] As Figure 8 shown, a decision loop may be implemented to determine whether XR data is to be processed locally (e.g., on the XR device 160 or the UE 120) or remotely (e.g., on the application server 180). At 805, the XR computing location may be switched from local computing to remote computing at least in part based on a parameter meeting a first threshold. At 810, the XR computing location may be switched from remote computing to local computing at least in part based on the parameter not meeting a second threshold. In some aspects, the XR computing location may be maintained if the parameter does not meet the first threshold and / or if the parameter does not meet the second threshold.

[0149] In some aspects, the parameter is RSRP. Here, the first threshold may include a combination of an RSRP threshold and a first sensitivity parameter, while the second threshold may include a combination of an RSRP threshold and a second sensitivity parameter. Thus, if X>T+δ 1 , then at 805, the XR calculation location may be switched from local calculation to remote calculation, where X corresponds to the RSRP measurement, T corresponds to the RSRP threshold, and δ 1 corresponds to the first sensitivity parameter. If X<T+δ 2 , then at 810, the XR calculation location may be switched from remote calculation to local calculation, where X corresponds to the RSRP measurement, T corresponds to the RSRP threshold, and δ 2 corresponds to the second sensitivity parameter. If T+δ 2 <X<T+δ 1 , then the XR calculation location may be maintained.

[0150] The first sensitivity parameter and the second sensitivity parameter may be selected to provide hysteresis to prevent frequent switching of the XR calculation location and to provide robustness to channel changes. To do so, the first sensitivity parameter may be selected as a larger value relative to the value selected for the second sensitivity parameter (e.g., such that δ 1 >δ 2 >0).

[0151] In some aspects, the parameter is eLCE. Here, the first threshold may include a combination of the required bit rate (T) for XR data operations and a first sensitivity parameter (δ 1 ), while the second threshold may include a combination of the required bit rate threshold and a second sensitivity parameter (δ 2 ).

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

[0153] Figure 9 is a diagram of example 900 of dynamic distributed XR calculation according to the present disclosure. The configurations and / or operations described in connection with example 800 may be included in and / or performed by UE 120 and / or XR device 160.

[0154] As Figure 9As shown, the configuration may include an application client 905 (e.g., an XR-based application client), one or more sensors 910 (e.g., gyroscopes, 6DOF sensors, accelerometers, cameras), and an application programming interface (API) 915 that enables communication between the application client 905, the modem 254, and the sensors 910. Information provided by the modem 254 (e.g., link information, beam measurements) and the perception of the environment of the UE 120 and / or the XR device 160 provided by the sensors 910 can be used to generate a radio condition prediction at 920. The radio condition prediction may include a blockage prediction (e.g., the time and / or duration of a wireless blockage), an RF environment map (e.g., a map location of the RSRP mapping, a map location of the link rate mapping), and / or another type of radio condition prediction. At 925, radio device parameters such as RSRP and / or eLCE, etc., can be determined.

[0155] The radio condition prediction and the radio device parameters can be provided to the application client 905 via the API 915 such that an XR calculation location determination can be performed at 930. At 935, an indication of the XR calculation location can be provided from the application client 905 to the modem 254, which can send the indication of the XR calculation location to the network node 110 for sending to the application server 180 associated with the application client 905.

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

[0157] Figure 10 is a diagram of an example 1000 of dynamic distributed XR calculation according to the present disclosure. As Figure 10 shown, the example 1000 of dynamic distributed XR calculation may include an XR device 160, a UE 120, a network node 110, and / or an application server 180, etc.

[0158] At 1005, the application server 180 can determine the XR calculation location of the XR data associated with the XR device 160. At 1010, the application server 180 can selectively send an indication to switch the XR calculation location to the UE 120 via the network node 110. Additionally, the application server 180 can selectively send an indication to switch the XR calculation location to the XR device 160 (either via the UE 120 and the network node 110 or via the network node 110 without relaying the indication through the UE 120). The application server 180 can selectively switch the XR calculation location at least partially based on the determination.

[0159] The application server 180 may determine the XR computing location based at least in part on one or more parameters. The one or more parameters may include one or more downlink parameters associated with the downlink between the network node 110 and the UE 120 (or between the network node 110 and the XR device 160). The one or more downlink parameters may include downlink RSRP, downlink RSSI, downlink RSRQ, downlink CQI, downlink throughput, and / or another downlink parameter.

[0160] For example, if the application server 180 determines that the downlink parameters do not meet a threshold (e.g., the downlink RSRP is less than the RSRP threshold, equal to the RSRP threshold), the application server 180 may determine the XR computing location as the UE 120 (or XR device 160) so that local computing can be performed due to degraded radio conditions on the downlink.

[0161] As another example, if the application server 180 determines that the downlink parameters do meet the threshold (e.g., the downlink throughput is greater than the throughput threshold, equal to the throughput threshold), the application server 180 may determine the XR computing location as the application server 180 so that remote computing can be performed to save the processing and memory resources of the UE 120 and / or the XR device 160.

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

[0163] Figure 11 FIG. 11 is a diagram illustrating an example process 1100 that may be performed by a UE, for example, in accordance with the present disclosure. The example process 1100 is an example in which a UE (e.g., UE 120) performs operations associated with dynamic distributed XR computing.

[0164] As Figure 11 shown, in some aspects, process 1100 may include: determining an XR computing location for XR data associated with an XR device associated with the UE based at least in part on one or more parameters, where the XR computing location corresponds to the UE, the XR device, or an application server associated with the XR data (block 1110). For example, the UE (e.g., using the communication manager 140 and / or the determination component 1408 depicted in Figure 14 FIG. 14) may determine an XR computing location for XR data associated with an XR device associated with the UE based at least in part on one or more parameters, as described above. In some aspects, the XR computing location corresponds to the UE, the XR device, or an application server associated with the XR data.

[0165] As Figure 11As further shown, in some aspects, process 1100 may include: selectively sending an indication of the XR computing location to a network node (block 1120). For example, a UE (e.g., using Figure 14 the communication manager 140 and / or the sending component 1404 depicted in

[0166] Process 1100 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.

[0167] In a first aspect, one or more parameters include at least one of the following: one or more radio device parameters, one or more power consumption parameters, or one or more radio device condition predictions.

[0168] In a second aspect, either alone or in combination with the first aspect, a corresponding weight is assigned to each radio device parameter of the one or more radio device parameters, each power consumption parameter of the one or more power consumption parameters, or each radio device condition prediction of the one or more radio device condition predictions.

[0169] In a third aspect, either alone or in combination with one or more of the first and second aspects, the one or more parameters further include at least one of the following: a packet loss rate associated with the UE; an RTT associated with the UE; an estimated network load associated with the network node; or an estimated load associated with an application server associated with XR data.

[0170] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the one or more parameters include one or more radio device parameters, and the one or more radio device parameters include at least one of the following: RSRP or eLCE.

[0171] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the one or more parameters include radio device parameters, and determining the XR computing location includes: determining the XR computing location at least in part based on whether the radio device parameters meet a threshold.

[0172] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the threshold includes a combination of a threshold parameter and a sensitivity parameter.

[0173] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, determining the XR calculation location includes: determining that the radio device parameter meets the threshold; and determining the XR calculation location as the application server associated with the XR data at least in part based on determining that the radio device parameter meets the threshold.

[0174] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the threshold includes a first threshold, and determining the XR calculation location includes: determining that the radio device parameter does not meet a second threshold; and determining the XR calculation location as the UE at least in part based on determining that the radio device parameter does not meet the second threshold.

[0175] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the first threshold includes a combination of a threshold parameter and a first sensitivity parameter, where the second threshold includes a combination of the threshold parameter and a second sensitivity parameter, and where the first sensitivity parameter is greater than the second sensitivity parameter.

[0176] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the threshold includes a first threshold, and determining the XR calculation location includes: determining that the radio device parameter does not meet the first threshold; determining that the radio device parameter meets a second threshold; and determining the XR calculation location for maintaining the XR data at least in part based on determining that the radio device parameter does not meet the first threshold and determining that the radio device parameter meets the second threshold.

[0177] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the one or more parameters include one or more radio device condition predictions, and the one or more radio device condition predictions include at least one of the following: a radio device blockage prediction associated with the UE, or an RF environment map of the area where the UE is located.

[0178] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the one or more parameters include a plurality of power consumption parameters, and the plurality of power consumption parameters include: a first estimated power consumption for the UE in the case where the XR calculation location is the UE, and a second estimated power consumption for the UE in the case where the XR calculation location is the application server associated with the XR data.

[0179] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, each of the first estimated power consumption and the second estimated power consumption includes a combination of an estimated radio device power consumption of the UE and an estimated XR computing power consumption of the UE.

[0180] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, determining the XR computing location includes: determining that the second estimated power consumption is greater than the first estimated power consumption; and determining the XR computing location as the UE at least in part based on determining that the second estimated power consumption is greater than the first estimated power consumption.

[0181] In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, determining the XR computing location includes: determining that the first estimated power consumption is greater than the second estimated power consumption; and determining the XR computing location as the application server at least in part based on determining that the first estimated power consumption is greater than the second estimated power consumption.

[0182] In a sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, selectively sending the indication of the XR computing location to the network node includes: avoiding sending the indication of the XR computing location at least in part based on determining to maintain the XR computing location.

[0183] Although Figure 11 illustrates example blocks of process 1100, in some aspects, process 1100 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner compared to those depicted in Figure 11 . Additionally or alternatively, two or more blocks of process 1100 may be executed in parallel.

[0184] Figure 12 is a diagram illustrating an example process 1200, for example, performed by an XR device in accordance with the present disclosure. Example process 1200 is an example in which an XR device (e.g., XR device 160) performs operations associated with dynamic distributed XR computing.

[0185] As Figure 12 shown, in some aspects, process 1200 may include: determining an XR computing location associated with XR data of the XR device at least in part based on one or more parameters, where the XR computing location corresponds to the XR device, a UE associated with the XR device, or an application server associated with the XR data (block 1210). For example, the XR device (e.g., using Figure 15The communication manager 170 and / or the determination component 1508 depicted in [above] may determine the XR computing location of XR data associated with the XR device based at least in part on one or more parameters, as described above. In some aspects, the XR computing location corresponds to the XR device, the UE associated with the XR device, or the application server associated with the XR data.

[0186] As Figure 12 Further shown, in some aspects, process 1200 may include: selectively sending an indication of the XR computing location to a network node (block 1220). For example, the XR device (e.g., using Figure 15 the communication manager 170 and / or the sending component 1504 depicted in [above]) may selectively send an indication of the XR computing location to a network node, as described above.

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

[0188] In a first aspect, the one or more parameters include at least one of the following: one or more radio device parameters, one or more power consumption parameters, or one or more radio device condition predictions.

[0189] In a second aspect, either alone or in combination with the first aspect, a respective weight is assigned to each radio device parameter of the one or more radio device parameters, each power consumption parameter of the one or more power consumption parameters, and each radio device condition prediction of the one or more radio device condition predictions.

[0190] In a third aspect, either alone or in combination with one or more of the first and second aspects, the one or more parameters further include at least one of the following: packet loss rate; RTT; estimated network load associated with a network node; or estimated load associated with an application server associated with XR data.

[0191] In a fourth aspect, either alone or in combination with one or more of the first through third aspects, the one or more parameters include one or more radio device parameters, and the one or more radio device parameters include at least one of the following: RSRP or eLCE.

[0192] In a fifth aspect, either alone or in combination with one or more of the first through fourth aspects, the one or more parameters include radio device parameters, and determining the XR computing location includes: determining the XR computing location based at least in part on whether the radio device parameters meet a threshold.

[0193] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the threshold includes a combination of a threshold parameter and a sensitivity parameter.

[0194] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, determining the XR calculation location includes: determining that the radio device parameters meet the threshold; and determining the XR calculation location as the network node at least in part based on determining that the radio device parameters meet the threshold.

[0195] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the threshold includes a first threshold, and determining the XR calculation location includes: determining that the radio device parameters do not meet a second threshold; and determining the XR calculation location as the XR device at least in part based on determining that the radio device parameters do not meet the second threshold.

[0196] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the threshold includes a first threshold, and determining the XR calculation location includes: determining that the radio device parameters do not meet a second threshold; and determining the XR calculation location as the UE associated with the XR device at least in part based on determining that the radio device parameters do not meet the second threshold.

[0197] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the first threshold includes a combination of a threshold parameter and a first sensitivity parameter, where the second threshold includes a combination of the threshold parameter and a second sensitivity parameter, and where the first sensitivity parameter is larger than the second sensitivity parameter.

[0198] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the threshold includes a first threshold, and determining the XR calculation location includes: determining that the radio device parameters do not meet the first threshold; determining that the radio device parameters meet a second threshold; and determining the XR calculation location for maintaining the XR data at least in part based on determining that the radio device parameters do not meet the first threshold and determining that the radio device parameters meet the second threshold.

[0199] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the one or more parameters include one or more radio device condition predictions, and the one or more radio device condition predictions include at least one of the following: a radio device blockage prediction associated with the XR device, or a radio frequency (RF) environment map of the area where the XR device is located.

[0200] In a thirteenth aspect, either alone or in combination with one or more of the first aspect to the twelfth aspect, the one or more parameters include one or more radio device condition predictions, and the one or more radio device condition predictions include at least one of the following: a radio device blockage prediction associated with the UE associated with the XR device, or an RF environment map of the area where the UE is located.

[0201] In a fourteenth aspect, either alone or in combination with one or more of the first aspect to the thirteenth aspect, the one or more parameters include a plurality of power consumption parameters, and the plurality of power consumption parameters include: a first estimated power consumption for the XR device in the case where the XR calculation location is the XR device, and a second estimated power consumption for the XR device in the case where the XR calculation location is the application server associated with the XR data.

[0202] In a fifteenth aspect, either alone or in combination with one or more of the first aspect to the fourteenth aspect, each of the first estimated power consumption and the second estimated power consumption includes a combination of an estimated radio device power consumption of the XR device and an estimated XR calculation power consumption of the XR device.

[0203] In a sixteenth aspect, either alone or in combination with one or more of the first aspect to the fifteenth aspect, determining the XR calculation location includes: determining that the second estimated power consumption is greater than the first estimated power consumption; and determining the XR calculation location as the XR device at least in part based on determining that the second estimated power consumption is greater than the first estimated power consumption.

[0204] In a seventeenth aspect, either alone or in combination with one or more of the first aspect to the sixteenth aspect, determining the XR calculation location includes: determining that the first estimated power consumption is greater than the second estimated power consumption; and determining the XR calculation location as the application server at least in part based on determining that the first estimated power consumption is greater than the second estimated power consumption.

[0205] In an eighteenth aspect, either alone or in combination with one or more of the first aspect to the seventeenth aspect, the one or more parameters include a plurality of power consumption parameters, and the plurality of power consumption parameters include: a first estimated power consumption for the UE associated with the XR device in the case where the XR calculation location is the UE, and a second estimated power consumption for the UE in the case where the XR calculation location is the application server associated with the XR data.

[0206] In a nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, each of the first estimated power consumption and the second estimated power consumption includes a combination of an estimated radio device power consumption of the UE and an estimated XR computing power consumption of the UE.

[0207] In a twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, determining the XR computing location includes: determining that the second estimated power consumption is greater than the first estimated power consumption; and determining the XR computing location as the UE at least in part based on determining that the second estimated power consumption is greater than the first estimated power consumption.

[0208] In a twenty - first aspect, either alone or in combination with one or more of the first to twentieth aspects, determining the XR computing location includes: determining that the first estimated power consumption is greater than the second estimated power consumption; and determining the XR computing location as the application server at least in part based on determining that the first estimated power consumption is greater than the second estimated power consumption.

[0209] In a twenty - second aspect, either alone or in combination with one or more of the first to twenty - first aspects, selectively sending the indication of the XR computing location to the network node includes: sending the indication of the XR computing location to the UE for sending to the network node.

[0210] In a twenty - third aspect, either alone or in combination with one or more of the first to twenty - second aspects, selectively sending the indication of the XR computing location to the network node includes: directly sending the indication of the XR computing location to the network node on a radio device link between the XR device and the network node.

[0211] In a twenty - fourth aspect, either alone or in combination with one or more of the first to twenty - third aspects, selectively sending the indication of the XR computing location to the network node includes: avoiding sending the indication of the XR computing location at least in part based on determining to maintain the XR computing location.

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

[0213] Figure 13FIG. is an illustration of an example process 1300, such as may be performed by an application server, in accordance with the present disclosure. The example process 1300 is an example in which an application server (e.g., application server 180) performs operations associated with dynamic distributed XR computing.

[0214] As Figure 13 shown, in some aspects, process 1300 may include: determining an XR computing location for XR data associated with an XR device, at least in part based on one or more parameters, where the XR computing location corresponds to the XR device, a UE associated with the XR device, or an application server associated with the XR data (block 1310). For example, an application server (e.g., using Figure 16 the communication manager 190 and / or the determination component 1608 depicted in ) may determine an XR computing location for XR data associated with an XR device, at least in part based on one or more parameters, where the XR computing location corresponds to the XR device, a UE associated with the XR device, or an application server associated with the XR data, as described above. In some aspects, the XR computing location corresponds to the XR device, a UE associated with the XR device, or an application server associated with the XR data.

[0215] As Figure 13 further shown, in some aspects, process 1300 may include: selectively switching the XR computing location, at least in part based on determining the XR computing location (block 1320). For example, an application server (e.g., using Figure 16 the communication manager 190 and / or the switching component 1610 depicted in ) may selectively switch the XR computing location, at least in part based on determining the XR computing location, as described above.

[0216] Process 1300 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.

[0217] In a first aspect, the one or more parameters include one or more downlink parameters associated with a downlink between network nodes at the XR device.

[0218] In a second aspect, either alone or in combination with the first aspect, the one or more downlink parameters include at least one of the following: downlink RSRP or downlink throughput.

[0219] Although Figure 13 example blocks of process 1300 are shown, in some aspects, process 1300 may include Figure 13fewer boxes, different boxes, or boxes arranged in a different manner than those depicted in the figures. Additionally or alternatively, two or more of the boxes of process 1300 may be performed in parallel.

[0220] Figure 14 is a diagram of an example apparatus 1400 for wireless communication in accordance with the present disclosure. Apparatus 1400 may be a UE 120, or UE 120 may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402 and a transmitting component 1404 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1400 may use receiving component 1402 and transmitting component 1404 to communicate with another apparatus 1406 (such as another UE 120, XR device 160, application server 180, network node 110, and / or another wireless communication device). As further shown, apparatus 1400 may include a communication manager 140. Communication manager 140 may include a determination component 1408, and so on.

[0221] In some aspects, apparatus 1400 may be configured to perform one or more operations described herein in connection with Figures 5A to 10 Additional or alternative, apparatus 1400 may be configured to perform one or more processes described herein, such as Figure 11 process 1100. In some aspects, Figure 14 apparatus 1400 and / or one or more components shown may include one or more components of UE 120 described in connection with Figure 2 Additional or alternative, Figure 14 one or more components shown may be implemented within one or more components described in connection with Figure 2 Additional or alternative, one or more components in a 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.

[0222] Receiving component 1402 may receive communications from apparatus 1406, such as reference signals, control information, data communications, or combinations thereof. Receiving component 1402 may provide the received communications to one or more other components of apparatus 1400. In some aspects, receiving component 1402 may perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of apparatus 1400. In some aspects, receiving component 1402 may include those described in connection with Figure 2One or more antennas, modems, demodulators, MIMO detectors, receive processors, controller / processors, memories, or combinations thereof of the described UE 120.

[0223] The transmit component 1404 may send communications to the device 1406, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 1400 may generate the communications and may provide the generated communications to the transmit component 1404 for sending to the device 1406. In some aspects, the transmit component 1404 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 send the processed signals to the device 1406. In some aspects, the transmit component 1404 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controller / processors, memories, or combinations thereof of the described UE 120. In some aspects, the transmit component 1404 may be co-located with the receive component 1402 in a transceiver. Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controller / processors, memories, or combinations thereof of the described UE 120. In some aspects, the transmit component 1404 may be co-located with the receive component 1402 in a transceiver.

[0224] The determination component 1408 may determine an XR calculation location of XR data associated with the XR device associated with the device 1400 at least in part based on one or more parameters. The XR calculation location corresponds to the device 1400, the XR device, or an application server associated with the XR data. The transmit component 1404 may selectively send an indication of the XR calculation location to the device 1406.

[0225] Figure 14 The number and arrangement of the illustrated components 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 those illustrated. Additionally, Figure 14 Compared to those illustrated. Additionally, Figure 14 Two or more of the illustrated components may be implemented in a single component, or Figure 14 The single illustrated component may be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The illustrated set(s) of components may perform one or more functions described as being performed by Figure 14 Another illustrated set of components.

[0226] Figure 15FIG. is a diagram of an example apparatus 1500 for wireless communication in accordance with the present disclosure. The apparatus 1500 may be an XR device 160, or the XR device 160 may include the apparatus 1500. In some aspects, the apparatus 1500 includes a receiving component 1502 and a transmitting component 1504 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1500 may use the receiving component 1502 and the transmitting component 1504 to communicate with another apparatus 1506 (such as a UE 120, a network node 110, an application server 180, and / or another wireless communication device). As further shown, the apparatus 1500 may include a communication manager 170. The communication manager 170 may include a determination component 1508 and so on.

[0227] In some aspects, the apparatus 1500 may be configured to perform one or more operations described herein in connection with Figures 5A to 10 Additional or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Figure 12 process 1200. In some aspects, Figure 15 The apparatus 1500 and / or one or more components shown may include one or more components of the XR device 160 described in connection with Figure 2 Additional or alternatively, Figure 15 One or more of the components shown may be implemented within one or more components described in connection with Figure 2 Additional or alternatively, one or more components in a 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 capable of being executed by a controller or a processor to perform the functions or operations of the component.

[0228] The receiving component 1502 may receive communications from the apparatus 1506, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1502 may provide the received communications to one or more other components of the apparatus 1500. In some aspects, the receiving component 1502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 1500. In some aspects, the receiving component 1502 may include a controller / processor, a memory, a communication unit, or a combination thereof of the XR device 160 described in connection with Figure 2 Additional or alternatively, one or more components in a 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 capable of being executed by a controller or a processor to perform the functions or operations of the component.

[0229] The transmitting component 1504 can send communications to the device 1506, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 1500 can generate communications and can provide the generated communications to the transmitting component 1504 for transmission to the device 1506. In some aspects, the transmitting component 1504 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can send the processed signals to the device 1506. In some aspects, the transmitting component 1504 can include the controller / processor, memory, communication unit of the XR device 160 described in conjunction with Figure 2 or combinations thereof. In some aspects, the transmitting component 1504 can be co-located with the receiving component 1502 in a transceiver.

[0230] The determining component 1508 can determine an XR calculation location of XR data associated with the device 1500 based at least in part on one or more parameters. The XR calculation location corresponds to the device 1500, the UE associated with the device 1500, or the application server associated with the XR data. The transmitting component 1504 can selectively send an indication of the XR calculation location to the device 1506.

[0231] Figure 15 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 15 those shown. Additionally, Figure 15 two or more of the components shown can be implemented within a single component, or Figure 15 a single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 15 a set of components (one or more components) shown can perform one or more functions described as being performed by Figure 15 another set of components shown.

[0232] Figure 16FIG. is a diagram of an example apparatus 1600 for wireless communication in accordance with the present disclosure. The apparatus 1600 may be an application server 180, or the application server 180 may include the apparatus 1600. In some aspects, the apparatus 1600 includes a receiving component 1602 and a transmitting component 1604 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1600 may communicate with another apparatus 1606 (such as a UE 120, a network node 110, an XR device 160, and / or another wireless communication device) using the receiving component 1602 and the transmitting component 1604. As further shown, the apparatus 1600 may include a communication manager 190. The communication manager 190 may include one or more of a determination component 1608 and / or a switching component 1610, among others.

[0233] In some aspects, the apparatus 1600 may be configured to perform one or more operations described herein in connection with Figures 5A to 10 Additional or alternatively, the apparatus 1600 may be configured to perform one or more processes described herein, such as Figure 13 process 1300. In some aspects, Figure 16 the apparatus 1600 and / or one or more components shown may include one or more components of the application server 180 described in connection with Figure 2 Additional or alternatively, Figure 16 one or more components shown may be implemented within one or more components described in connection with Figure 2 Additional or alternatively, one or more components of a 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.

[0234] The receiving component 1602 may receive communications from the apparatus 1606, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1602 may provide the received communications to one or more other components of the apparatus 1600. In some aspects, the receiving component 1602 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 apparatus 1600. In some aspects, the receiving component 1602 may include a controller / processor, a memory, a communication unit, or combinations thereof of the application server 180 described in connection with Figure 2 Additional or alternatively, one or more components shown may be implemented within one or more components described in connection with

[0235] The transmitting component 1604 can send communications to the device 1606, such as reference signals, control information, data communications, or a combination thereof. In some aspects, one or more other components of the device 1600 can generate communications and can provide the generated communications to the transmitting component 1604 for sending to the device 1606. In some aspects, the transmitting component 1604 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can send the processed signals to the device 1606. In some aspects, the transmitting component 1604 can include a controller / processor, a memory, a communication unit, or a combination thereof of the application server 180 described in conjunction with Figure 2 In some aspects, the transmitting component 1604 can be co-located with the receiving component 1602 in a transceiver.

[0236] The determining component 1608 can determine an XR computing location of XR data associated with the XR device at least in part based on one or more parameters, where the XR computing location corresponds to the XR device, a UE associated with the XR device, or an application server associated with the XR data. The switching component 1610 can selectively switch the XR computing location at least in part based on the determining component 1608 determining the XR computing location.

[0237] Figure 16 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 the components shown. Additionally, Figure 16 two or more of the components shown can be implemented within a single component, or Figure 16 a single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 16 a set of components (one or more components) shown can perform one or more functions described as being performed by another set of components shown. Figure 16 Figure 16 Figure 16 Figure 16

[0238] An overview of some aspects of the present disclosure is provided below:

[0239] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: determining an XR computing location of XR data associated with an extended reality (XR) device associated with the UE at least in part based on one or more parameters, where the XR computing location corresponds to the UE, the XR device, or an application server associated with the XR data; and selectively sending an indication of the XR computing location to a network node.

[0240] Aspect 2: The method according to aspect 1, wherein the one or more parameters include at least one of the following: one or more radio device parameters, one or more power consumption parameters, or one or more radio device condition predictions. One or more radio device parameters, one or more power consumption parameters, or one or more radio device condition predictions.

[0241] Aspect 3: The method according to aspect 2, wherein a respective weight is assigned to each radio device parameter of the one or more radio device parameters, each power consumption parameter of the one or more power consumption parameters, or each radio device condition prediction of the one or more radio device condition predictions.

[0242] Aspect 4: The method according to aspect 2, wherein the one or more parameters further include at least one of the following: packet loss rate associated with the UE; round-trip time (RTT) associated with the UE; estimated network load associated with the network node; or estimated load associated with the application server associated with the XR data. Packet loss rate associated with the UE; round-trip time (RTT) associated with the UE; estimated network load associated with the network node; or estimated load associated with the application server associated with the XR data.

[0243] Aspect 5: The method according to any one of aspects 1 to 4, wherein the one or more parameters include one or more radio device parameters; and wherein the one or more radio device parameters include at least one of the following: reference signal received power (RSRP); or enhanced link capacity estimate (eLCE).

[0244] Aspect 6: The method according to any one of aspects 1 to 5, wherein the one or more parameters include radio device parameters; and wherein determining the XR calculation location includes: determining the XR calculation location at least in part based on whether the radio device parameters meet a threshold, wherein determining the XR calculation location includes: determining the XR calculation location at least in part based on whether the radio device parameters meet a threshold.

[0245] Aspect 7: The method according to aspect 6, wherein the threshold includes a combination of a threshold parameter and a sensitivity parameter.

[0246] Aspect 8: The method according to aspect 6, wherein determining the XR calculation location includes: determining that the radio device parameters meet the threshold; and determining the XR calculation location as the application server associated with the XR data at least in part based on determining that the radio device parameters meet the threshold. Determining that the radio device parameters meet the threshold; and determining the XR calculation location as the application server associated with the XR data at least in part based on determining that the radio device parameters meet the threshold.

[0247] Aspect 9: The method according to aspect 6, wherein the threshold includes a first threshold; and wherein determining the XR calculation location includes: determining that the radio device parameters do not meet a second threshold; and determining the XR calculation location as the UE at least in part based on determining that the radio device parameters do not meet the second threshold, wherein determining the XR calculation location includes: determining that the radio device parameters do not meet a second threshold; and determining the XR calculation location as the UE at least in part based on determining that the radio device parameters do not meet the second threshold.

[0248] Aspect 10: The method according to aspect 9, wherein the first threshold includes a combination of a threshold parameter and a first sensitivity parameter; wherein the second threshold includes a combination of the threshold parameter and a second sensitivity parameter; and wherein the first sensitivity parameter is larger than the second sensitivity parameter, wherein the second threshold includes a combination of the threshold parameter and a second sensitivity parameter; and wherein the first sensitivity parameter is larger than the second sensitivity parameter.

[0249] Aspect 11: The method according to aspect 6, wherein the threshold includes a first threshold; and wherein determining the XR calculation location includes: determining that the radio device parameters do not meet the first threshold; determining that the radio device parameters meet a second threshold; and determining the XR calculation location for maintaining the XR data at least in part based on determining that the radio device parameters do not meet the first threshold and determining that the radio device parameters meet the second threshold, wherein determining the XR calculation location includes: determining that the radio device parameters do not meet the first threshold; determining that the radio device parameters meet a second threshold; and determining the XR calculation location for maintaining the XR data at least in part based on determining that the radio device parameters do not meet the first threshold and determining that the radio device parameters meet the second threshold.

[0250] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the one or more parameters include one or more radio device condition predictions; and wherein the one or more radio device condition predictions include at least one of the following: a radio device blockage prediction associated with the UE, or a radio frequency (RF) environment map of the area where the UE is located, wherein the one or more radio device condition predictions include at least one of the following: a radio device blockage prediction associated with the UE, or a radio frequency (RF) environment map of the area where the UE is located.

[0251] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the one or more parameters include a plurality of power consumption parameters; and wherein the plurality of power consumption parameters include: a first estimated power consumption for the UE in the case where the XR calculation location is the UE, and a second estimated power consumption for the UE in the case where the XR calculation location is the application server associated with the XR data, wherein the plurality of power consumption parameters include: a first estimated power consumption for the UE in the case where the XR calculation location is the UE, and a second estimated power consumption for the UE in the case where the XR calculation location is the application server associated with the XR data.

[0252] Aspect 14: The method according to Aspect 13, wherein each of the first estimated power consumption and the second estimated power consumption includes a combination of an estimated radio device power consumption of the UE and an estimated XR calculation power consumption of the UE.

[0253] Aspect 15: The method according to Aspect 13, wherein determining the XR calculation location includes: determining that the second estimated power consumption is greater than the first estimated power consumption; and determining the XR calculation location as the UE at least in part based on determining that the second estimated power consumption is greater than the first estimated power consumption. Determining that the second estimated power consumption is greater than the first estimated power consumption; and determining the XR calculation location as the UE at least in part based on determining that the second estimated power consumption is greater than the first estimated power consumption.

[0254] Aspect 16: The method according to aspect 13, wherein determining the XR computing location includes: determining that the first estimated power consumption is relatively large compared to the second estimated power consumption; and determining the XR computing location as the application server at least in part based on determining that the first estimated power consumption is relatively large compared to the second estimated power consumption. Determining that the first estimated power consumption is relatively large compared to the second estimated power consumption; and determining the XR computing location as the application server at least in part based on determining that the first estimated power consumption is relatively large compared to the second estimated power consumption.

[0255] Aspect 17: The method according to any one of aspects 1 to 16, wherein selectively sending the indication of the XR computing location to the network node includes: avoiding sending the indication of the XR computing location at least in part based on determining to maintain the XR computing location. Avoiding sending the indication of the XR computing location at least in part based on determining to maintain the XR computing location.

[0256] Aspect 18: A method for wireless communication performed by an extended reality (XR) device, the method including: determining an XR computing location associated with XR data of the XR device at least in part based on one or more parameters, wherein the XR computing location corresponds to the XR device, a user equipment (UE) associated with the XR device, or an application server associated with the XR data; and selectively sending an indication of the XR computing location to a network node.

[0257] Aspect 19: The method according to aspect 18, wherein the one or more parameters include at least one of the following: one or more radio device parameters, one or more power consumption parameters, or one or more radio device condition predictions. One or more radio device parameters, one or more power consumption parameters, or one or more radio device condition predictions.

[0258] Aspect 20: The method according to aspect 19, wherein a respective weight is assigned to each radio device parameter among the one or more radio device parameters, each power consumption parameter among the one or more power consumption parameters, and each radio device condition prediction among the one or more radio device condition predictions.

[0259] Aspect 21: The method according to aspect 19, wherein the one or more parameters further include at least one of the following: packet loss rate; round-trip time (RTT); estimated network load associated with the network node; or estimated load associated with the application server associated with the XR data. Packet loss rate; round-trip time (RTT); estimated network load associated with the network node; or estimated load associated with the application server associated with the XR data.

[0260] Aspect 22: The method according to any one of aspects 18 to 21, wherein the one or more parameters include one or more radio device parameters; and wherein the one or more radio device parameters include at least one of the following: reference signal received power (RSRP); or enhanced link capacity estimate (eLCE).

[0261] Aspect 23: The method according to any one of aspects 18 to 22, wherein the one or more parameters include radio device parameters; and wherein determining the XR calculation location includes: determining the XR calculation location at least in part based on whether the radio device parameters meet a threshold, wherein determining the XR calculation location includes: determining the XR calculation location at least in part based on whether the radio device parameters meet a threshold.

[0262] Aspect 24: The method according to aspect 23, wherein the threshold includes a combination of a threshold parameter and a sensitivity parameter.

[0263] Aspect 25: The method according to aspect 23, wherein determining the XR calculation location includes: determining that the radio device parameters meet the threshold; and determining the XR calculation location as the network node at least in part based on determining that the radio device parameters meet the threshold. Determining that the radio device parameters meet the threshold; and determining the XR calculation location as the network node at least in part based on determining that the radio device parameters meet the threshold.

[0264] Aspect 26: The method according to aspect 23, wherein the threshold includes a first threshold; and wherein determining the XR calculation location includes: determining that the radio device parameters do not meet a second threshold; and determining the XR calculation location as the XR device at least in part based on determining that the radio device parameters do not meet the second threshold, wherein determining the XR calculation location includes: determining that the radio device parameters do not meet a second threshold; and determining the XR calculation location as the XR device at least in part based on determining that the radio device parameters do not meet the second threshold.

[0265] Aspect 27: The method according to aspect 23, wherein the threshold includes a first threshold; and wherein determining the XR calculation location includes: determining that the radio device parameter does not meet a second threshold; and determining the XR calculation location as the UE associated with the XR device at least in part based on determining that the radio device parameter does not meet the second threshold, wherein determining the XR calculation location includes: determining that the radio device parameter does not meet a second threshold; and determining the XR calculation location as the UE associated with the XR device at least in part based on determining that the radio device parameter does not meet the second threshold.

[0266] Aspect 28: The method according to aspect 27, wherein the first threshold includes a combination of a threshold parameter and a first sensitivity parameter; wherein the second threshold includes a combination of the threshold parameter and a second sensitivity parameter; and wherein the first sensitivity parameter is larger than the second sensitivity parameter, wherein the second threshold includes a combination of the threshold parameter and a second sensitivity parameter; and wherein the first sensitivity parameter is larger than the second sensitivity parameter.

[0267] Aspect 29: The method according to aspect 23, wherein the threshold includes a first threshold; and wherein determining the XR calculation location includes: determining that the radio device parameter does not meet the first threshold; determining that the radio device parameter meets a second threshold; and determining the XR calculation location for maintaining the XR data at least in part based on determining that the radio device parameter does not meet the first threshold and determining that the radio device parameter meets the second threshold, wherein determining the XR calculation location includes: determining that the radio device parameter does not meet the first threshold; determining that the radio device parameter meets a second threshold; and determining the XR calculation location for maintaining the XR data at least in part based on determining that the radio device parameter does not meet the first threshold and determining that the radio device parameter meets the second threshold.

[0268] Aspect 30: The method according to any one of aspects 18 to 29, wherein the one or more parameters include one or more radio device condition predictions; and wherein the one or more radio device condition predictions include at least one of the following: a radio device blockage prediction associated with the XR device, or a radio frequency (RF) environment map of the area where the XR device is located, wherein the one or more radio device condition predictions include at least one of the following: a radio device blockage prediction associated with the XR device, or a radio frequency (RF) environment map of the area where the XR device is located.

[0269] Aspect 31: The method according to any one of aspects 18 to 30, wherein the one or more parameters include one or more radio device condition predictions; and wherein the one or more radio device condition predictions include at least one of the following: a radio device blockage prediction associated with the UE associated with the XR device, or a radio frequency (RF) environment map of the area where the UE is located, wherein the one or more radio device condition predictions include at least one of the following: a radio device blockage prediction associated with the UE associated with the XR device, or a radio frequency (RF) environment map of the area where the UE is located.

[0270] Aspect 32: The method according to any one of aspects 18 to 31, wherein the one or more parameters include a plurality of power consumption parameters; and wherein the plurality of power consumption parameters include: a first estimated power consumption for the XR device in the case where the XR calculation location is the XR device, and a second estimated power consumption for the XR device in the case where the XR calculation location is the application server associated with the XR data, wherein the plurality of power consumption parameters include: a first estimated power consumption for the XR device in the case where the XR calculation location is the XR device, and a second estimated power consumption for the XR device in the case where the XR calculation location is the application server associated with the XR data.

[0271] Aspect 33: The method according to aspect 32, wherein each of the first estimated power consumption and the second estimated power consumption includes a combination of an estimated radio device power consumption of the XR device and an estimated XR calculation power consumption of the XR device.

[0272] Aspect 34: The method according to aspect 32, wherein determining the XR calculation location includes: determining that the second estimated power consumption is greater than the first estimated power consumption; and determining the XR calculation location as the XR device at least in part based on determining that the second estimated power consumption is greater than the first estimated power consumption. Determining that the second estimated power consumption is greater than the first estimated power consumption; and determining the XR calculation location as the XR device at least in part based on determining that the second estimated power consumption is greater than the first estimated power consumption.

[0273] Aspect 35: The method according to aspect 32, wherein determining the XR calculation location includes: determining that the first estimated power consumption is relatively large compared to the second estimated power consumption; and determining the XR calculation location as the application server at least in part based on determining that the first estimated power consumption is relatively large compared to the second estimated power consumption. Determining that the first estimated power consumption is relatively large compared to the second estimated power consumption; and determining the XR calculation location as the application server at least in part based on determining that the first estimated power consumption is relatively large compared to the second estimated power consumption.

[0274] Aspect 36: The method according to any one of aspects 18 to 35, wherein the one or more parameters include a plurality of power consumption parameters; and wherein the plurality of power consumption parameters include: a first estimated power consumption of the UE associated with the XR device in the case where the XR calculation location is the UE, and a second estimated power consumption of the UE in the case where the XR calculation location is the application server associated with the XR data, wherein the plurality of power consumption parameters include: a first estimated power consumption of the UE associated with the XR device in the case where the XR calculation location is the UE, and a second estimated power consumption of the UE in the case where the XR calculation location is the application server associated with the XR data.

[0275] Aspect 37: The method according to aspect 36, wherein each of the first estimated power consumption and the second estimated power consumption includes a combination of an estimated radio device power consumption of the UE and an estimated XR calculation power consumption of the UE.

[0276] Aspect 38: The method according to aspect 36, wherein determining the XR calculation location includes: determining that the second estimated power consumption is relatively large compared to the first estimated power consumption; and determining the XR calculation location as the UE at least in part based on determining that the second estimated power consumption is relatively large compared to the first estimated power consumption. Determining that the second estimated power consumption is relatively large compared to the first estimated power consumption; and determining the XR calculation location as the UE at least in part based on determining that the second estimated power consumption is relatively large compared to the first estimated power consumption.

[0277] Aspect 39: The method according to aspect 36, wherein determining the XR calculation location includes: determining that the first estimated power consumption is relatively large compared to the second estimated power consumption; and determining the XR calculation location as the application server at least in part based on determining that the first estimated power consumption is relatively large compared to the second estimated power consumption. Determining that the first estimated power consumption is relatively large compared to the second estimated power consumption; and determining the XR calculation location as the application server at least in part based on determining that the first estimated power consumption is relatively large compared to the second estimated power consumption.

[0278] Aspect 40: The method according to any one of aspects 18 to 39, wherein selectively sending the indication of the XR calculation location to the network node includes: sending the indication of the XR calculation location to the UE for sending to the network node. Sending the indication of the XR calculation location to the UE for sending to the network node.

[0279] Aspect 41: The method according to any one of aspects 18 to 40, wherein selectively sending the indication of the XR calculation location to the network node includes: directly sending the indication of the XR calculation location to the network node on a radio device link between the XR device and the network node. Directly sending the indication of the XR calculation location to the network node on a radio device link between the XR device and the network node.

[0280] Aspect 42: The method according to any one of aspects 18 to 41, wherein selectively sending the indication of the XR calculation location to the network node includes: avoiding sending the indication of the XR calculation location at least in part based on determining to maintain the XR calculation location. Avoiding sending the indication of the XR calculation location at least in part based on determining to maintain the XR calculation location.

[0281] Aspect 43: A method of wireless communication performed by an application server, the method comprising: determining an XR calculation location of XR data associated with an extended reality (XR) device at least in part based on one or more parameters, wherein the XR calculation location corresponds to the XR device, a user equipment (UE) associated with the XR device, or an application server associated with the XR data; and selectively switching the XR calculation location at least in part based on determining the XR calculation location.

[0282] Aspect 44: The method according to aspect 43, wherein the one or more parameters include one or more downlink parameters associated with a downlink between the network node at the XR device.

[0283] Aspect 45: The method according to aspect 44, wherein the one or more downlink parameters include at least one of the following: downlink reference signal received power (RSRP) or downlink throughput. Downlink reference signal received power (RSRP) or downlink throughput.

[0284] Aspect 46: 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 45.

[0285] Aspect 47: 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 45.

[0286] Aspect 48: 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 45.

[0287] Aspect 49: 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 45.

[0288] Aspect 50: 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 1 to 45.

[0289] 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.

[0290] 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 various aspects. Accordingly, 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.

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

[0292] 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 various 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 set of claims. 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). By way of 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 of multiple identical elements (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).

[0293] No element, act, or instruction used herein shall be construed as critical or essential unless expressly so stated. Further, as used herein, the article "a" is intended to include one or more items and may be used interchangeably 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 used interchangeably with "one or more." Further, as used herein, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more." If only one item is intended, the phrase "only one" or similar language will be used. Further, as used herein, the terms "has," "owns," "possesses," etc. are intended to be open-ended terms that do not limit the elements they modify (e.g., an element that "has" A may also have B). Further, the phrase "based on" is intended to mean "at least partially based on" unless otherwise expressly stated. Further, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless otherwise expressly stated (e.g., if used in conjunction with "either" or "only one").

Claims

1. 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: determine an XR computing location of XR data associated with an extended reality (XR) device associated with the UE, at least in part based on one or more parameters, wherein the XR computing location corresponds to the UE, the XR device, or an application server associated with the XR data; and selectively send an indication of the XR computing location to a network node.

2. The UE according to claim 1, wherein the one or more parameters include at least one of the following: one or more radio device parameters, one or more power consumption parameters, or one or more radio device condition predictions.

3. The UE according to claim 2, wherein the one or more parameters further include at least one of the following: a packet loss rate associated with the UE, a round-trip time (RTT) associated with the UE, an estimated network load associated with the network node, or an estimated load associated with the application server associated with the XR data.

4. The UE according to claim 1, wherein the one or more parameters include one or more radio device parameters; and wherein the one or more radio device parameters include at least one of the following: a reference signal received power (RSRP), or an enhanced link capacity estimate (eLCE).

5. The UE according to claim 1, wherein the one or more parameters include radio device parameters; and wherein, to determine the XR computing location, the one or more processors are configured to: determine the XR computing location, at least in part based on whether the radio device parameters meet a threshold.

6. The UE according to claim 5, wherein the threshold includes a first threshold; and wherein, to determine the XR computing location, the one or more processors are configured to: determine that the radio device parameters do not meet a second threshold; and determine the XR computing location as the UE, at least in part based on determining that the radio device parameters do not meet the second threshold.

7. The UE according to claim 6, wherein the first threshold includes a combination of a threshold parameter and a first sensitivity parameter; wherein the second threshold includes a combination of the threshold parameter and a second sensitivity parameter; and wherein the first sensitivity parameter is larger than the second sensitivity parameter.

8. The UE according to claim 1, wherein the one or more parameters include one or more radio device condition predictions; and wherein the one or more radio device condition predictions include at least one of the following: a radio device blockage prediction associated with the UE, or a radio frequency (RF) environment map of the area where the UE is located.

9. The UE according to claim 1, wherein the one or more parameters include multiple power consumption parameters; and wherein the plurality of power consumption parameters include: a first estimated power consumption for the UE in the case where the XR calculation location is the UE, and a second estimated power consumption for the UE in the case where the XR calculation location is the application server associated with the XR data.

10. The UE according to claim 9, wherein each of the first estimated power consumption and the second estimated power consumption includes a combination of an estimated radio device power consumption of the UE and an estimated XR calculation power consumption of the UE.

11. An extended reality (XR) device for wireless communication, the extended reality (XR) device comprises: a memory; and one or more processors coupled to the memory, the one or more processors being configured to: determine an XR calculation location of XR data associated with the XR device based at least in part on one or more parameters, wherein the XR calculation location corresponds to the XR device, a user equipment (UE) associated with the XR device, or an application server associated with the XR data; and selectively send an indication of the XR calculation location to a network node.

12. The XR device according to claim 11, wherein the one or more parameters include at least one of the following: one or more radio device parameters, one or more power consumption parameters, or one or more radio device condition predictions.

13. The XR device according to claim 12, wherein the one or more parameters further include at least one of the following: packet loss rate, round-trip time (RTT), an estimated network load associated with the network node, or an estimated load associated with the application server associated with the XR data.

14. The XR device according to claim 11, wherein the one or more parameters include one or more radio device parameters; and wherein the one or more radio device parameters include at least one of the following: reference signal received power (RSRP), or enhanced link capacity estimate (eLCE).

15. The XR device according to claim 11, wherein the one or more parameters include radio device parameters; and wherein, to determine the XR calculation location, the one or more processors are configured to: determine the XR calculation location based at least in part on whether the radio device parameters meet a threshold.

16. The XR device according to claim 15, wherein the threshold includes a combination of a threshold parameter and a sensitivity parameter.

17. The XR device according to claim 15, wherein, to determine the XR calculation location, the one or more processors are configured to: determine that the radio device parameters meet the threshold; and determine the XR calculation location as the network node based at least in part on determining that the radio device parameters meet the threshold.

18. The XR device according to claim 15, wherein the threshold includes a first threshold; and Wherein, to determine the XR calculation location, the one or more processors are configured to: Determine that the radio device parameters do not meet a second threshold; and Determine the XR calculation location as the XR device based at least in part on determining that the radio device parameters do not meet the second threshold.

19. The XR device according to claim 15, wherein the threshold includes a first threshold; and Wherein, to determine the XR calculation location, the one or more processors are configured to: Determine that the radio device parameters do not meet a second threshold; and Determine the XR calculation location as the UE associated with the XR device based at least in part on determining that the radio device parameters do not meet the second threshold.

20. The XR device according to claim 19, wherein the first threshold includes a combination of a threshold parameter and a first sensitivity parameter; Wherein the second threshold includes a combination of the threshold parameter and a second sensitivity parameter; and Wherein the first sensitivity parameter is larger than the second sensitivity parameter.

21. The XR device according to claim 15, wherein the threshold includes a first threshold; and Wherein, to determine the XR calculation location, the one or more processors are configured to: Determine that the radio device parameters do not meet the first threshold; Determine that the radio device parameters meet a second threshold; And Determine the XR calculation location for maintaining the XR data based at least in part on determining that the radio device parameters do not meet the first threshold and determining that the radio device parameters meet the second threshold.

22. The XR device according to claim 11, wherein the one or more parameters include one or more radio device condition predictions; and Wherein the one or more radio device condition predictions include at least one of the following: A radio device blockage prediction associated with the radio device associated with the XR device, or A radio frequency (RF) environment map of the area where the XR device is located.

23. The XR device according to claim 11, wherein the one or more parameters include one or more radio device condition predictions; and Wherein the one or more radio device condition predictions include at least one of the following: A radio device blockage prediction associated with the UE associated with the XR device, or A radio frequency (RF) environment map of the area where the UE is located.

24. The XR device according to claim 11, wherein the one or more parameters include a plurality of power consumption parameters; and Wherein the plurality of power consumption parameters Include: A first estimated power consumption for the XR device in the case where the XR calculation location is the XR device, and A second estimated power consumption for the XR device in the case where the XR calculation location is the application server associated with the XR data.

25. The XR device according to claim 24, wherein the first estimated power consumption and the second estimated power consumption each comprise a combination of an estimated radio device power consumption of the XR device and an estimated XR computing power consumption of the XR device.

26. The XR device according to claim 11, wherein the one or more parameters comprise a plurality of power consumption parameters; and wherein the plurality of power consumption parameters comprise: a first estimated power consumption of the UE associated with the XR device in a case where the XR computing location is the UE, and a second estimated power consumption of the UE in a case where the XR computing location is the application server associated with the XR data.

27. The XR device according to claim 26, wherein the first estimated power consumption and the second estimated power consumption each comprise a combination of an estimated radio device power consumption of the UE and an estimated XR computing power consumption of the UE.

28. An application server for wireless communication, the application server comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to: determine an XR computing location of XR data associated with an extended reality (XR) device at least in part based on one or more parameters, wherein the XR computing location corresponds to the XR device, a user equipment (UE) associated with the XR device, or an application server associated with the XR data; and selectively switch the XR computing location at least in part based on determining the XR computing location.

29. The application server according to claim 28, wherein the one or more parameters comprise one or more downlink parameters associated with a downlink between a network node and the XR device or the UE.

30. The application server according to claim 29, wherein the one or more downlink parameters comprise at least one of the following: downlink reference signal received power (RSRP), or downlink throughput.