Buffering application data based on latency information and / or power information

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may buffer, at a selected layer of the UE, a set of extended reality (XR) data associated with a plurality of XR applications instantiated on the UE based on at least one of latency information or power information in association with a buffering time period. The UE may transmit the set of XR data based on at least one of an expiration of the buffering time period or an indication associated with an XR application of the plurality of XR applications. Numerous other aspects are described.

Description

BUFFERING APPLICATION DATA BASED ON LATENCY INFORMATION AND / ORPOWER INFORMATIONCROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Application claims priority to Indian Patent Application No. 202341062867, filed on September 19, 2023, entitled “BUFFERING APPLICATION DATA BASED ON LATENCY INFORMATION AND / OR POWER INFORMATION,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application.FIELD OF THE DISCLOSURE

[0002] Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for buffering application data based on latency information and / or power information.BACKGROUND

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like). Examples of such multiple-access technologies 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 / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0004] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL”) refers to a communication link from the network node to the UE, and “uplink” (or “UL”) refers to a 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., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate on a municipal, national, regional, and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using 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, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful.SUMMARY

[0006] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to buffer, at a selected layer of the apparatus, a set of application data associated with a plurality of applications instantiated on the apparatus based on at least one of latency information or power information in association with a buffering time period. The one or more processors may be configured to transmit the set of application data based on at least one of an expiration of the buffering time period or an indication associated with an application of the plurality of applications. The application data may include extended reality (XR) data.

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include buffering, at a selected layer of the UE, a set of application data associated with a plurality of applications instantiated on the UE based on at least one of latency information or power information in association with a buffering time period. The method may include transmitting the set of application data based on at least one of an expiration of the buffering time period or an indication associated with an application of the plurality of applications.

[0008] Some aspects described herein relate to a non-transitory computer-readable medium that stores 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 buffer, at a selected layer of the UE, a set of application data associated with a plurality of applications instantiated on the UE based on at least one of latency information or power information in association with a buffering time period. The set of instructions, when executed by one or more processors ofthe UE, may cause the UE to transmit the set of application data based on at least one of an expiration of the buffering time period or an indication associated with an application of the plurality of applications.

[0009] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for buffering, at a selected layer of the UE, a set of application data associated with a plurality of applications instantiated on the UE based on at least one of latency information or power information in association with a buffering time period. The apparatus may include means for transmitting the set of application data based on at least one of an expiration of the buffering time period or an indication associated with an application of the plurality of applications.

[0010] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, wireless communication device, and / or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.

[0011] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed 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. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.

[0012] While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. 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 integrated chip embodiments or other non-modulecomponent based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, rctail / purchasing 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 described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components includingantennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of varying size, shape, and constitution.BRIEF DESCRIPTION OF THE DRAWINGS

[0013] So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

[0014] Fig. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0015] Fig. 2 is a diagram illustrating an example of a network node in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0016] Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

[0017] Fig. 4 illustrates a wireless communication system (also known as a wireless local area network (WLAN) or a Wi-Fi network) configured in accordance with the present disclosure.

[0018] Fig. 5 A is a diagram illustrating an example associated with buffering extended reality (XR) data based on latency information and / or power information, in accordance with the present disclosure.

[0019] Fig. 5B is a diagram illustrating an example associated with buffering application data based on latency information and / or power information in which the application data is flushed and transmitted based on a latency tolerance-based optimization, in accordance with the present disclosure.

[0020] Fig. 5C is a diagram illustrating an example associated with buffering application data based on latency information and / or power information in which the application data is flushed and transmitted based on receiving an application indication, in accordance with the present disclosure.

[0021] Fig. 6 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.

[0022] Fig. 7 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.DETAILED DESCRIPTION

[0023] Some devices, including devices for extended reality (XR), may require low-latency traffic to and from an edge server or a cloud environment. In some cases, XR software instantiated on a user equipment (UE) can have multiple threads (e.g., each thread associated with an application) and can generate data at periodic intervals. In some cases, the different sources of data (e.g., the different applications) can have different latency requirements (e.g., body pose data may be less latency -tolerant than statistics or hand tracking camera data). Due to the differences in timing, synchronizing the multiple threads to generate data at the same time may not be possible without generating fragments of data. Fragmented data transmission may result in unnecessarily numerous transmissions, thereby reducing potential power savings by preventing the wireless local area network (WLAN) component from entering low power mode as often as it may otherwise be configured to do.

[0024] Some aspects of the techniques described herein include dynamic buffering of XR data at one or more layers of the UE. For example, the UE may buffer, at a selected layer of the apparatus, a set of XR data associated with a plurality of XR applications instantiated on the UE. The UE may select the layer or layers based on at least one of latency information or power information. The UE may buffer the set of XR data in association with a buffering time period. The buffering time period may be configured, determined based on receipt of additional XR data, and / or based on receiving an indication from an application. In this way, some aspects may facilitate reducing unnecessary wake-up of the WLAN component of the UE, thereby reducing power consumption while mitigating latency.

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

[0026] Aspects and examples generally include a method, apparatus, network node, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and / or processing system as described or substantially described herein with reference to and as illustrated by the drawings and specification.

[0027] This disclosure 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. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, are better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.

[0028] While aspects are described in the present disclosure by illustration to some examples, such aspects may be implemented in many different arrangements and scenarios. 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 integrated chip embodiments or other non-module-component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing 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 described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, 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). Aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of varying size, shape, and constitution.

[0029] Several aspects of telecommunication systems 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 accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0030] While aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G).

[0031] Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as a network node 110a, a network node 110b, a network node 110c, and a network node 1 lOd), a user equipment (UE) 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e), and / or other entities. A network node 110 is a network node that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes. For example, a network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among 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)).

[0032] In some examples, a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, a 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, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU. In some examples, a 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. A network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmission reception point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and / or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.

[0033] In some examples, a network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a network node 110 and / or a network node subsystem serving this coverage area, depending on the context in which the term is used. A network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In the example shown in Fig. 1, the network node 110a may be a macro network node for a macro cell 102a, the network node 110b may be a pico network node for a pico cell 102b, and the network node 110c may be a femto network node for a femto cell 102c. A network node may support one or multiple (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network node 110 that is mobile (e.g., a mobile network node).

[0034] In some aspects, the terms “base station” or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, “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 terms “base station” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110. In some aspects, the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the terms “base station” or “network node” may refer to any one or more of those different devices. In some aspects, the terms “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 terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.

[0035] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. In the example shown in Fig. 1, the network node 1 lOd (e.g., a relay network node) may communicate with the network node 110a (e.g., a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, or the like.

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

[0037] A network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0038] The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. A UE 120 may 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, a camera, a gaming device, a netbook, a smartbook, an ultrabook, 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 vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device that is configured to communicate via a wireless or wired medium.

[0039] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE and / or an eMTC UE may include, for example, a robot, an unmanned aerial vehicle, a remote device, a sensor, a meter, a monitor, and / or a location tag, that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Intemet-of-Things (loT) devices, and / or may be implemented as NB-IoT (narrowband loT) devices. Some UEs 120 may be considered a Customer Premises Equipment. A UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0040] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, an air interface, or the like. A frequency may be referred to as a carrier, a frequency channel, or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0041] 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., without using a network node 110 as an intermediary to communicate with one another). For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device -to -device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to- vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and / or a mesh network. In such examples, a UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the network node 110.

[0042] Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being differentfrom the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

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

[0044] With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and techniques described herein are applicable to those modified frequency ranges.

[0045] In some aspects, a UE (e.g., the UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may buffer, at a selected layer of the UE, a set of XR data associated with a plurality of XR applications instantiated on the UE based on at least one of latency information or power information in association with a buffering time period; and transmit the set of XR data based on at least one of an expiration of the buffering time period or an indication associated with an XR application of the plurality of XR applications. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0046] As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

[0047] Fig. 2 is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. 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 antennas 234 and a modem 232. In some examples, anetwork node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.

[0048] At the network node 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS(s) selected for the UE 120 and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple -input multiple -output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the 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 a modulator component (shown as MOD) of a modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a downlink signal. The 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.

[0049] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive the 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 a modem 254. Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) a received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modems 254,may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller / processor 280. The term “controller / processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RS SI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other examples. In some examples, one or more components of the UE 120 may be included in a housing 284.

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

[0051] One or more antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) may include, 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, among other examples. An antenna panel, an antenna group, a set of antenna elements, and / or an antenna array 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 transmission and / or reception components, such as one or more components of Fig. 2.

[0052] Each of the antenna elements may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals. The antenna elements may include patch antennas, dipole antennas, or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. A spacing between antenna elements may be such that signals with a desired wavelength transmitted separately by the antenna elements may interact or interfere (e.g., to form a desired beam). For example, given an expected range of wavelengths or frequencies, the spacing may provide a quarter wavelength, half wavelength, or other fraction of a wavelength of spacing between neighboring antenna elements to allow for interaction or interference of signals transmitted by the separate antenna elements within that expected range.

[0053] Antenna elements and / or sub-elements may be used to generate beams. “Beam” may refer to a directional transmission such as a wireless signal that is transmitted in a direction of a receiving device. A beam may include a directional signal, a direction associated with a signal, a set of directional resources associated with a signal (e.g., angle of arrival, horizontal direction, vertical direction), and / or a set of parameters that indicate one or more aspects of a directionalsignal, a direction associated with a signal, and / or a set of directional resources associated with a signal.

[0054] As indicated above, antenna elements and / or sub-elements may be used to generate beams. For example, antenna elements may be individually selected or deselected for transmission of a signal (or signals) by controlling an amplitude of one or more corresponding amplifiers. Beamforming includes generation of a beam using multiple signals on different antenna elements, where one or more, or all, of the multiple signals are shifted in phase relative to each other. The formed beam may carry physical or higher layer reference signals or information. As each signal of the multiple signals is radiated from a respective antenna element, the radiated signals interact, interfere (constructive and destructive interference), and amplify each other to form a resulting beam. The shape (such as the amplitude, width, and / or presence of side lobes) and the direction (such as an angle of the beam relative to a surface of an antenna array) can be dynamically controlled by modifying the phase shifts or phase offsets of the multiple signals relative to each other.

[0055] Beamforming may be used for communications between a UE and a network node, such as for millimeter wave communications and / or the like. In such a case, the network node may provide the UE with a configuration of transmission configuration indicator (TCI) states that respectively indicate beams that may be used by the UE, such as for receiving a physical downlink shared channel (PDSCH). A TCI state indicates a spatial parameter for a communication. For example, a TCI state for a communication may identify a source signal (such as a synchronization signal block, a channel state information reference signal, or the like) and a spatial parameter to be derived from the source signal for the purpose of transmitting or receiving the communication. For example, the TCI state may indicate a quasi-co -location (QCL) type. A QCL type may indicate one or more spatial parameters to be derived from the source signal. The source signal may be referred to as a QCL source. The network node may indicate an activated TCI state to the UE, which the UE may use to select a beam for receiving the PDSCH.

[0056] A beam indication may be, or include, a TCI state information element, a beam identifier (ID), spatial relation information, a TCI state ID, a closed loop index, a panel ID, a TRP ID, and / or a sounding reference signal (SRS) set ID, among other examples. A TCI state information element (referred to as a TCI state herein) may indicate information associated with a beam such as a downlink beam. For example, the TCI state information element may indicate a TCI state identification (e.g., a tci-StatelD), a QCL type (e.g., a qcl-Typel, qcl-Type2, qcl- TypeA, qcl-TypeB, qcl-TypeC, qcl-TypeD, and / or the like), a cell identification (e.g., a ServCelllndex), a bandwidth part identification rwp-Id), a reference signal identification such as a CSI-RS (e.g., mNZP-CSI-RS-Resourceld, m SSB-Index, and / or the like), and / or the like. Spatial relation information may similarly indicate information associated with an uplink beam.

[0057] The beam indication may be a joint or separate downlink (DL) / uplink (UL) beam indication in a unified TCI framework. In some cases, the network may support layer 1 (L 1)- based beam indication using at least UE-specific (unicast) downlink control information (DCI) to indicate joint or separate DL / UL beam indications from active TCI states. In some cases, existing DCI formats 1 1 and / or 1 2 may be reused for beam indication. The network may include a support mechanism for a UE to acknowledge successful decoding of a beam indication. For example, the acknowledgment / negative acknowledgment (ACK / NACK) of the PDSCH scheduled by the DCI carrying the beam indication may be also used as an ACK for the DCI.

[0058] Beam indications may be provided for carrier aggregation (CA) scenarios. In a unified TCI framework, information the network may support common TCI state ID update and activation to provide common QCL and / or common UL transmission spatial filter or filters across a set of configured component carriers (CCs). This type of beam indication may apply to intra-band CA, as well as to joint DL / UL and separate DL / UL beam indications. The common TCI state ID may imply that one reference signal (RS) determined according to the TCI state(s) indicated by a common TCI state ID is used to provide QCL Type-D indication and to determine UL transmission spatial filters across the set of configured CCs.

[0059] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 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 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna(s) 252, the modem(s) 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 Figs. 5A-7).

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

[0061] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or any other component(s) of Fig. 2 may perform one or more techniques associated with buffering XR data based on latency information and / or power information, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or any other component(s) of Fig. 2 may perform or direct operations of, for example, process 500 of Fig. 5, and / or other processes as described herein. The memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively. In some examples, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and / or interpreting) by one or more processors of the network node 110 and / or the UE 120, may cause the one or more processors, the UE 120, and / or the network node 110 to perform or direct operations of, for example, process 500 of Fig. 5, and / or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instmctions, among other examples.

[0062] In some aspects, a UE (e.g., the UE 120) includes means for buffering, at a selected layer of the UE, a set of XR data associated with a plurality of XR applications instantiated on the UE based on at least one of latency information or power information in association with a buffering time period; and / or means for transmitting the set of XR data based on at least one of an expiration of the buffering time period or an indication associated with an XR application of the plurality of XR applications. The means for the UE to perform 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.

[0063] In some aspects, an individual processor may perform all of the functions described as being performed by the one or more processors. In some aspects, one or more processors may collectively perform a set of functions. For example, a first set of (one or more) processors of the one or more processors may perform a first function described as being performed by theone or more processors, and a second set of (one or more) processors of the one or more processors may perform a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to “one or more processors” should be understood to refer to any one or more of the processors described in connection with Fig.2. Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Fig.2. For example, functions described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.

[0064] While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to 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.

[0065] As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.

[0066] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may 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, a 5G NB, an access point (AP), a TRP, or a cell, among other examples), or one or more units (or one or more components) performing base station functionality, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. “Network entity” or “network node” may refer to a disaggregated base station, or to 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).

[0067] An aggregated base station (e.g., an aggregated 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 disaggregated base station (e.g., a disaggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU 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 distributed throughout one or multiple other network nodes. The DUs may be implemented tocommunicate with one or more RUs. Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

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

[0069] Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both). A CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through Fl interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be simultaneously served by multiple RUs 340.

[0070] Each of the units, including the CUs 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305, may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0071] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (for example, Central Unit - User Plane (CU-UP) functionality), control plane functionality (for example, Central Unit - Control Plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.

[0072] Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3 GPP. In some aspects, the 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, among other examples. In some aspects, the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT), an inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.

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

[0074] The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized networkelements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an 01 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective 01 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.

[0075] The Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy -based guidance of applications / features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (such as via an Al interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-realtime control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

[0076] In some implementations, to generate 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 external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an 01 interface) or via creation of RAN management policies (such as Al interface policies).

[0077] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.

[0078] Fig. 4 illustrates a wireless communication system 400 (also known as a wireless local area network (WLAN) or a Wi-Fi network) configured in accordance with the present disclosure. The wireless communication system 400 may include an access point (AP) 405 and multiple associated devices 415 (such as stations (STAs) or SAPs), which may represent devicessuch as mobile stations, personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, display devices (e.g., TVs, computer monitors, etc.), printers, etc. The AP 405 and the associated devices 415 (e.g., associated STAs) may represent a basic service set (BSS) or an extended service set (ESS). A BSS includes devices that communicate with each other, and an ESS may include multiple BSSs or one or more BSSs and associated wired networks. The various devices 415 in the network may be able to communicate with one another through the AP 405. Also shown is a coverage area 410 of the AP 405, which may represent a basic service area (BSA) of the wireless communication system 400. An extended network station (not shown) associated with the wireless communication system 400 may be connected to a wired or wireless distribution system that may allow multiple APs 405 to be connected in an ESS.

[0079] Although not shown in FIG. 4, a device 415 may be located in the intersection of more than one coverage area 410 and may associate with more than one AP 405. A single AP 405 and an associated set of devices 415 may be referred to as a BSS. An ESS is a set of connected BSSs. A distribution system (not shown) may be used to connect APs 405 in an ESS. In some cases, the coverage area 410 of an AP 405 may be divided into sectors (also not shown). The wireless communication system 400 may include APs 405 of different types (e.g., metropolitan area, home network, etc.), with varying and overlapping coverage areas 410. Two devices 415 may also communicate directly via a direct wireless communication link 425 regardless of whether both devices 415 are in the same coverage area 410. Examples of direct wireless communication links 420 may include Wi-Fi Direct connections, Wi-Fi Tunneled Direct Link Setup (TDLS) links, and other group connections.

[0080] In some cases, a device 415 (or an AP 405) may be detectable by a central AP 405, but not by other devices 415 in the coverage area 410 of the central AP 405. For example, one device 415 may be at one end of the coverage area 410 of the central AP 405 while another device 415 may be at the other end. Thus, both devices 415 may communicate with the AP 405, but may not receive the transmissions of the other. This may result in colliding transmissions for the two devices 415 in a contention-based environment (e.g., carrier sense multiple access with collision avoidance (CSMA / CA)) because the devices 415 may not refrain from transmitting on top of each other. A device 415 whose transmissions are not identifiable, but that is within the same coverage area 410 may be known as a hidden node. CSMA / CA may be supplemented by the exchange of a request-to-send (RTS) packet transmitted by a sending device 415 (or AP 405) and a clear-to-send (CTS) packet transmitted by the receiving device 415 (or AP 405). This may alert other devices within range of the sender and receiver not to transmit for the duration of the primary transmission. Thus, RTS and / or CTS may help mitigate a hidden node problem.

[0081] The wireless communication system 400 may include an AP 405, devices 415 (e.g., which may be referred to as source devices or central devices), and paired devices 415 (e.g., which may be referred to as sink devices or peripheral devices) implementing WLAN communications (e.g., Wi-Fi communications) and / or Bluetooth communications. For example, devices 415 may include cell phones, user equipment (UEs), STAs, mobile stations, PDAs, other handheld devices, netbooks, notebook computers, tablet computers, laptops, or some other suitable terminology. Paired devices 415 may include Bluetooth-enabled devices capable of pairing with other Bluetooth-enabled devices (e.g., such as devices 415), which may include wireless audio devices (e.g., headsets, earbuds, speakers, earpieces, headphones), display devices (e.g., TVs, computer monitors), microphones, meters, valves, etc. As one example, the paired devices 415 may include a wireless headset 430 as shown by Fig. 4, and the paired devices 415 may alternatively or additionally communicate with the AP 405. In some aspects, a paired device 415 may communicate with a device 415 using the AP 405.

[0082] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4.

[0083] In some cases, software instantiated on a UE can have multiple threads (e.g., each thread associated with an application) and can generate data at periodic intervals. In some cases, the different sources of data (e.g., the different applications) can have different latency requirements (e.g., pose data may be less latency -tolerant than statistics or hand tracking camera data). Due to the differences in timing, synchronizing the multiple threads to generate data at the same time may not be possible without generating fragments of data. Fragmented data transmission may result in unnecessarily numerous transmissions, thereby reducing potential power savings by preventing the WLAN component from entering low power mode as often as it may otherwise be configured to do.

[0084] Some aspects of the techniques described herein include dynamic buffering of application data at one or more layers of the UE. For example, the UE may buffer, at a selected layer of the apparatus, a set of application data associated with a plurality of applications instantiated on the UE. In some aspects, the application data may be XR data associated with one or more XR applications. The UE may select the layer or layers based on at least one of latency information or power information. The UE may buffer the set of application data in association with a buffering time period. The buffering time period may be configured, determined based on receipt of additional application data, and / or based on receiving an indication from an application. In this way, some aspects may facilitate reducing unnecessary wake-up of the WLAN component of the UE, thereby reducing power consumption while mitigating latency.

[0085] Some aspects may include a latency tolerance-based optimization in which the application data is buffered at the WLAN driver and / or firmware layers for up to a specified amount of time before the packets are transmitted. In some aspects, the selected layers may be based on latency tolerance associated with corresponding applications. Some aspects may include application indication-based optimization in which the WLAN driver or firmware layer buffer the packets of configured flows until a specific indication is provided by an application to flush the packet to the WLAN chipset. This indication may be provided via control information in the data packet or via an application programming interface (API) call. In some aspects, application indication-based optimization may be helpful in scenarios in which an application is generating periodic bursts of traffic and aware of final packets of the burst. In some aspects, a combination of latency tolerance and application indication-based approaches may be used to facilitate dynamic optimization.

[0086] Fig. 5 A is a diagram illustrating an example 500 associated with buffering application data based on latency information and / or power information, in accordance with the present disclosure. As shown in example 500, a UE 502 and a network node 504 may communicate with one another. The UE 502 may be, be similar to, include, or be included in, a device 415 depicted in Fig. 4 and / or the UE 120 depicted in Figs. 1-3. The network node 504 may be, be similar to, include, or be included in, a device 415 depicted in Fig. 4, the network node 110 depicted in Figs. 1 and 2, and / or one or more components of the disaggregated base station architecture 300 depicted in Fig. 3.

[0087] In some aspects, as shown, the UE 502 may include a wireless local area network (WLAN) component 506, a cellular communication component 508, and an application component 510. In some aspects, the UE 502 may include a communication manager 512. In some aspects, the communication manager 512 may be, be similar to, include, or be included in, the communication manager 140 depicted in Figs. 1, 2, and 4. In some aspects, the communication manager 512 may be configured to manage communication operations performed by and / or between the WLAN component 506, the cellular communication component 508, and / or the application component 510. In some aspects, one or more components of the WLAN component 506, the cellular communication component 508, and / or the application component 510 may be, be similar to, include, or be included in, the reception component 702, the transmission component 704, and / or the communication manager 706, depicted in Fig. 7. In some aspects, the WLAN component 506 may facilitate communications via a WLAN network (e.g., a WiFi network) and the cellular communication component 508 may facilitate communications via a cellular network. In some aspects, the application component 510 may include an application layer (e.g., a software layer) in which XR applications (e.g., APP1, APP2, APP3, and APP4) may be instantiated.

[0088] The UE 502 and the network node 504 may communicate application data via a communication link 514. The communication link 514 may be, be similar to, include, or be included in, the communication link 425 depicted in Fig. 4. The network node 504 may communicate, via a communication link 516, application data with an AP 518, which may be, be similar to, include, or be included in, the AP 405 depicted in Fig. 4. The communication link 516 may be, be similar to, include, or be included in, the communication link 420 depicted in Fig. 4. In some aspects, the application data may include XR data and the AP 405 may include one or more XR data servers, XR data relays, and / or other entities configured to support XR services provided to the UE 502. XR may include virtual reality (VR), augmented reality (AR), and / or mixed reality (MR), among other examples. In some aspects, for example, the AP 518 may provide XR data to the network node 504, which may provide the XR data to the UE 502, which may render the XR data via an output device of the UE 502 (e.g., a display device, an audio device and / or a haptic device, among other examples). The UE 502 also may transmit XR data to the AP 518. For example, the UE 502 may transmit XR data to the network node 504 and the network node 504 may transmit the XR data to the AP 518. In some aspects, the AP 518 may communicate with another WLAN and / or a cellular network to facilitate communication of application data outside of the WLAN.

[0089] As shown by reference number 520, the UE 502 (e.g., a WLAN component 506 of the UE 502) may obtain a set of application data. For example, the WLAN component 506 may obtain the set of application data from one or more applications (shown, e.g., as “APP1,” “APP2,” “APP3,” and “APP4”) instantiated on the UE 502. For example, the one or more applications may provide the set of application data to the WLAN component 506 for transmission to the network node 504 (which may then provide the set of application data to the AP 518). In some aspects, the WLAN component 506 may be, be similar to, include, or be included in, the communication manager 140 depicted in Figs. 1 and 2. In some aspects, the set of application data may include a first portion of application data associated with APP1, a second portion of application data associated with APP2, a third portion of application data associated with APP3, and / or a fourth portion of application data associated with APP4. In some cases, each portion of application data may be referred to as a flow (or as a part of a flow) associated with the corresponding application. In some aspects, the UE 502 may support any number of different applications and corresponding flows. A quantity of flows supportable by the UE 502 may, for example, be determined based on a UE capability.

[0090] As shown by reference number 522, the UE 502 (e.g., via a communication manager 512) may buffer the set of application data. In some aspects, the communication manager 512 may be, be similar to, include, or be included in, the communication manager 140 depicted in Figs. 1 and 2. For example, the UE 502 may use an adaptive buffering technique for buffering the set of application data at a selected layer of the UE 502. A layer of the UE 502 may refer toa layer of a protocol stack and / or a system architecture associated with the UE 502 and / or one or more components of the UE 502.

[0091] As shown, for example, the WLAN component 506 may include number of layers including a transmission control protocol (TCP) / user datagram protocol (UDP) component 524, an internet protocol (IP) component 526, a WLAN driver 528, and a WLAN chipset 530. A peripheral component interconnect express (PCIe) interface 532 may connect the WLAN driver 528 with the WLAN chipset 530. In some aspects, for example, the TCP / UDP component 524, the IP component 526, and the WLAN driver 528 may be software layers of a protocol stack used to facilitate WLAN communications. The WLAN chipset 530 may include a firmware and / or hardware layer of the system architecture of the UE 502 used to facilitate WLAN communications. For example, in some aspects, the WLAN chipset 530 may be, include, or be included in, a WLAN modem. In some aspects, the PCIe interface 532 may include firmware and / or hardware. In some aspects, each of the TCP / UDP component 524, the IP component 526, the WLAN driver 528, and the WLAN chipset 530 may be referred to as a “layer” of the UE 502. Similarly, software instantiated on the UE 502 may be referred to as being part of a “software layer,” firmware configured on the UE 502 may be referred to as being part of a “firmware layer,” and hardware included in the UE 502 may be referred to as being part of a “hardware layer.” In some aspects, the firmware layer includes the hardware layer. As shown, in some aspects, the WLAN driver 528 may include a protocol stack that includes a medium access control (MAC) layer management entity (MLME) 534. The WLAN chipset 530 may include a MAC layer 536 and a physical layer 538. In some aspects, the MAC layer 536 may be included in the physical layer 538. In some aspects, the MAC layer 536 and / or the physical layer 538 and / or the WLAN chipset 530 may be referred to as “lower layers.” In some aspects, the WLAN driver 528 and / or the MLME 534 may be referred to as “higher layers.”

[0092] To buffer the set of application data, the UE 502 (e.g., via the communication manager 512) may select one or more layers in which to buffer the set of application data. In some aspects, the communication manager 512 may be configured to select the one or more layers based on any number of different criteria and / or in association with any number of different formulas, configurations, and / or algorithms. For example, in some aspects, the communication manager 512 may be configured to implement one or more optimization operations in which the communication manager 512 selects the one or more layers based on satisfaction of an optimization condition that balances power savings with latency reduction. In some aspects, the optimization condition may be selected by the communication manager (e.g., in accordance with a configured rule or mles, a wireless communication standard, and / or a machine learning operation) and / or obtained by the communication manager (e.g., via an indication received from another network entity or an application instantiated on the UE 502). In some aspects, the communication manager may use one or more machine learning models,components, and / or algorithms to facilitate selection of the layer or layers in which the buffer the set of application data.

[0093] In some aspects, the UE 502 may buffer a portion 540 of the set of application data in a first layer 542 and another portion 544 of the set of XR data in a second layer 546. In some aspects, the set of application data may include only a portion of application data obtained from the application component 510 (e.g., in cases in which another set of XR data is transmitted without first being buffered). In some aspects, the layer or layers 542 and 546 to be to used for buffering the set of application data may be selected based on at least one of latency information or power information. In some aspects, the latency information and / or the power information may be associated with a buffering time period.

[0094] The latency information may include, for example, a latency requirement associated with an XR application. For example, the set of XR data may include XR packets associated with an XR application having a latency requirement that satisfies a latency condition (e.g., a high latency condition or a low latency condition). The latency condition may include a threshold and / or a range. The power information may be associated with a power requirement of the UE 502 while operating in association with an XR application. In some aspects, the power information may be associated with a power profile of at least one component of a system architecture of the UE 502.

[0095] In some aspects, for example, buffering at the WLAN driver 528 may provide the higher power savings than buffering at the PCIe interface 532 and / or the WLAN chipset 530 (as there is no PCIe / WLAN chipset wakeup for per packet queueing that occurs when buffering at the WLAN driver 528). However, buffering at the WLAN driver 528 may introduce more latency than buffering at the PCIe interface 532 and / or the WLAN chipset 530 (e.g., due to a delay in transferring data to the WLAN chipset 530 after a flush operation is triggered by buffering logic). In some aspects, buffering at the firmware layers (e.g., at the PCIe interface 532 and / or the WLAN chipset 530) may consume more power resources than buffering at the WLAN driver 528 (e.g., due to PCIe interface 532 and / or WLAN chipset 530 wakeup operations for per-packet queueing), but may result in lower latency as there is no delay in transferring data to the WLAN chipset 530 after flush is triggered by buffering logic.

[0096] In some aspects, for example, the selected layer may include at least one of the WLAN driver 528 or a lower layer (e.g., the MAC layer 536 and / or the physical layer 538 of the WLAN chipset 530). In some aspects, the selected layer may include the WLAN driver 528 based on the XR data including packets associated with a latency that satisfies a high latency condition. In some aspects, the selected layer may include the MAC layer 536 and may be based on the XR data including packets associated with a latency that satisfies a low latency condition.

[0097] In some aspects, the selection of the layer or layers at which to buffer the set of application data may be based on a dynamic determination associated with one or more latency requirements associated with the applications and / or packet arrival. For example, in some aspects, the communication manager 512 may buffer a higher latency tolerant packet at the WLAN driver 528 but may move that packet to the WLAN chipset 530 in association with obtaining a lower latency tolerant packet. For example, in some aspects, the communication manager 512 may obtain an additional set of application data and may move the set of application data from the selected layer to an additional selected layer based on obtaining the additional set of application data. In some aspects, the set of application data may include a first packet associated with a first latency value and the additional set of XR data may include a second packet associated with a second latency value, and the communication manager 512 may move the set of application data from the selected layer to the additional selected layer based on the second latency value being less than the first latency value.

[0098] As shown by reference number 548, the communication manager 512 may flush the set of application data. For example, the communication manager 512 may flush the set of application data from a memory (e.g., the buffer associated with the selected layer or layers) of the UE 502 based on an expiry of a timer associated with a first application of the plurality of applications. In some aspects, the communication manager 512 may flush the set of application data from a memory (e.g., the buffer associated with the selected layer or layers) of the UE 502 based on a latency tolerance value. In some aspects, the communication manager 512 may flush the set of application data from the memory (e.g., the buffer associated with the selected layer or layers) based on obtaining, from a corresponding application, an indication. In some aspects, the communication manager 512 may obtain the indication associated with the application based on obtaining a packet that includes the indication. In some aspects, the communication manager 512 may obtain the indication associated with the application based on an application programming interface (API).

[0099] As shown by reference number 550, the UE 502 may transmit the set of application data. In some aspects, the set of application data may include a first data packet associated with a first flow (e.g., a first application) and a second data packet associated with a second flow (e.g., a second application), and the UE 502 may transmit the set of application data based on transmitting, based on the first data packet being associated with the first flow, the first data packet based on a latency tolerance value associated with the buffering time period. The UE 502 may transmit, based on the second data packet being associated with the second flow, the second data packet based on the indication.

[0100] In some aspects, for example, the UE 502 may flush the set of application data and / or transmit the set of application data based on a latency tolerance-based optimization. Fig. 4B is a diagram illustrating an example 552 associated with buffering application data based on latencyinformation and / or power information in which the application data is flushed and transmitted based on a latency tolerance-based optimization, in accordance with the present disclosure. For example, in some aspects, a set of application data may be flushed based on an expiry of a latency timer associated with any one of the XR applications. In some aspects, for example, a first latency timer to expire may trigger the flush of the application data associated with all of the applications.

[0101] For example, as shown in example 552, a flow 554 may be associated with Appl, a flow 556 may be associated with App2, a flow 558 may be associated with App3, and a flow 560 may be associated with App4. As shown, a first latency timer 562 may be associated with App2 and a second latency timer 564 may be associated with App 3. As shown by reference number 566, in some aspects, the UE 502 may not buffer the application data associated with the flows 554, 556, 558, and 560, and may transmit the application data in the order received from the respective applications. As shown by reference number 568, in some aspects, the UE 502 may use aspects of the latency and power aware buffering techniques described herein to buffer the application data and may flush and transmit the application data based on a latency tolerance-aware optimization. For example, in example 552, the UE 502 may flush and transmit the application data based on an expiry of the first latency timer 562. In some aspects, a latency tolerance value specified via a user input may be used to trigger the flush of the set of application data.

[0102] In some other aspects, the UE 502 may flush the set of application data and / or transmit the set of application data based on receiving an application indication. Fig. 5C is a diagram illustrating an example 570 associated with buffering application data based on latency information and / or power information in which the application data is flushed and transmitted based on receiving an application indication, in accordance with the present disclosure. Example 570 illustrates the same flows 554, 556, 558, and 560 illustrated in Fig. 5B. As shown, App3 may provide an application indication 572. For example, App3 may provide the application indication 572 to the WLAN component 506 (and / or the communication manager 512) of the UE 502. As shown by reference number 574, in some aspects, the UE 502 may not buffer the application data associated with the flows 554, 556, 558, and 560, and may transmit the application data in the order received from the respective applications.

[0103] In some aspects, as shown by reference number 576, the UE 502 may flush the set of application data based on receiving the application indication 572 from App3. For example, in some aspects, application data associated with a first application may be flushed based on receiving an indication from the first application and application data associated with a second application may be flushed based on receiving an indication from the second application. In some aspects, the set of application data associated with more than one application may be flushed based on receiving an indication from one application of the more than one application.

[0104] In some aspects, the UE 502 may flush the set of application data and / or transmit the set of application data based on a combination of a latency tolerance-based optimization and receiving an application indication. For example, in some aspects, application data associated with one or more applications may be flushed based on a latency tolerance-based optimization and application data associated with one or more other applications may be flushed based on receiving one or more application indications from the one or more other applications. In some aspects, for example, the UE 502 may optimize application data flush efficiency based on the combination of the latency tolerance-based optimization and receiving application indications.

[0105] As indicated above, Figs. 5 A-5C are provided as examples. Other examples may differ from what is described with regard to Figs. 5A-5C.

[0106] Fig. 6 is a diagram illustrating an example process 600 performed, for example, by a UE, in accordance with the present disclosure. Example process 600 is an example where the UE (e.g., UE 502) performs operations associated with buffering application data based on latency information and / or power information.

[0107] As shown in Fig. 6, in some aspects, process 600 may include buffering, at a selected layer of the UE, a set of application data associated with a plurality of applications instantiated on the UE based on at least one of latency information or power information in association with a buffering time period (block 610). For example, the UE (e.g., using communication manager 706, depicted in Fig. 7) may buffer, at a selected layer of the UE, a set of application data associated with a plurality of applications instantiated on the UE based on at least one of latency information or power information in association with a buffering time period, e.g., in a manner similar to that described above in connection with reference number 522 of Fig. 5 A.

[0108] As further shown in Fig. 6, in some aspects, process 600 may include transmitting the set of application data based on at least one of an expiration of the buffering time period or an indication associated with an application of the plurality of applications (block 620). For example, the UE (e.g., using transmission component 704 and / or communication manager 706, depicted in Fig. 7) may transmit the set of application data based on at least one of an expiration of the buffering time period or an indication associated with an application of the plurality of applications, e.g., in a manner similar to that described above in connection with reference number 550 of Fig. 5 A.

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

[0110] In a first aspect, the selected layer is based on the at least one of the latency information or the power information. In a second aspect, alone or in combination with the first aspect, the selected layer comprises at least one of a WLAN driver or a lower layer. In a thirdaspect, alone or in combination with one or more of the first and second aspects, the selected layer comprises the WLAN driver based on the application data comprising packets associated with a latency that satisfies a high latency condition. In a fourth aspect, alone or in combination with the third aspect, the lower layer comprises a MAC layer. In a fifth aspect, alone or in combination with the fourth aspect, the selected layer comprises the MAC layer and is based on the application data comprising packets associated with a latency that satisfies a low latency condition.[oni] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process 600 includes obtaining an additional set of application data and moving the set of application data from the selected layer to an additional selected layer based on obtaining the additional set of application data. In a seventh aspect, alone or in combination with the sixth aspect, the set of application data comprises a first packet associated with a first latency value and the additional set of application data comprises a second packet associated with a second latency value, and moving the set of application data from the selected layer to the additional selected layer comprises moving the first packet based on the second latency value being less than the first latency value.

[0112] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the power information is associated with a power requirement of the UE while operating in association with an XR application. In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the power information is associated with a power profile of at least one component of a system architecture of the UE. In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process 600 includes flushing the set of application data from a memory of the UE based on an expiry of a timer associated with a first application of the plurality of applications. In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process 600 includes flushing the set of application data from a memory of the UE based on a latency tolerance value. In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, process 600 includes obtaining the indication associated with the application. In a thirteenth aspect, alone or in combination with the twelfth aspect, the set of application data comprises a packet that includes the indication. In a fourteenth aspect, alone or in combination with one or more of the twelfth or thirteenth aspects, obtaining the indication comprises obtaining the indication based on an application programming interface.

[0113] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the set of application data comprises a first data packet associated with a first flow and a second data packet associated with a second flow, and wherein transmitting the set of application data comprises transmitting, based on the first data packet being associated with the first flow, the first data packet based on a latency tolerance value associated with the bufferingtime period, and transmitting, based on the second data packet being associated with the second flow, the second data packet based on the indication. In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the set of application data comprises a set of XR data.

[0114] Although Fig. 6 shows example blocks of process 600, in some aspects, process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 6. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0115] Fig. 7 is a diagram of an example apparatus 700 for wireless communication, in accordance with the present disclosure. The apparatus 700 may be a UE, or a UE may include the apparatus 700. In some aspects, the apparatus 700 includes a reception component 702, a transmission component 704, and / or a communication manager 706, which may be in communication with one another (for example, via one or more buses and / or one or more other components). In some aspects, the communication manager 706 is the communication manager 140 described in connection with Fig. 1. As shown, the apparatus 700 may communicate with another apparatus 708, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 702 and the transmission component 704.

[0116] In some aspects, the apparatus 700 may be configured to perform one or more operations described herein in connection with Figs. 5A-5C. Additionally, or alternatively, the apparatus 700 may be configured to perform one or more processes described herein, such as process 600 of Fig. 6. In some aspects, the apparatus 700 and / or one or more components shown in Fig. 7 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 7 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer- readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0117] The reception component 702 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 708. The reception component 702 may provide received communications to one or more other components of the apparatus 700. In some aspects, the reception component 702 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 700. In someaspects, the reception component 702 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.

[0118] The transmission component 704 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 708. In some aspects, one or more other components of the apparatus 700 may generate communications and may provide the generated communications to the transmission component 704 for transmission to the apparatus 708. In some aspects, the transmission component 704 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 708. In some aspects, the transmission component 704 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 704 may be co-located with the reception component 702 in a transceiver.

[0119] The communication manager 706 may support operations of the reception component 702 and / or the transmission component 704. For example, the communication manager 706 may receive information associated with configuring reception of communications by the reception component 702 and / or transmission of communications by the transmission component 704. Additionally, or alternatively, the communication manager 706 may generate and / or provide control information to the reception component 702 and / or the transmission component 704 to control reception and / or transmission of communications.

[0120] The communication manager 706 may buffer, at a selected layer of the UE, a set of application data associated with a plurality of applications instantiated on the UE based on at least one of latency information or power information in association with a buffering time period. The transmission component 704 may transmit the set of application data based on at least one of an expiration of the buffering time period or an indication associated with an application of the plurality of applications. The reception component 702 may obtain an additional set of application data. The communication manager 706 may move the set of application data from the selected layer to an additional selected layer based on obtaining the additional set of application data. The communication manager 706 may flush the set of application data from a memory of the UE based on an expiry of a timer associated with a first application of the plurality of applications. The communication manager 706 may flush the set of application data from a memory of the UE based on a latency tolerance value. The reception component 702 may obtain the indication associated with the application.

[0121] The number and arrangement of components shown in Fig. 7 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 7. Furthermore, two or more components shown in Fig. 7 may be implemented within a single component, or a single component shown in Fig. 7 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 7 may perform one or more functions described as being performed by another set of components shown in Fig. 7.

[0122] The following provides an overview of some Aspects of the present disclosure:

[0123] Aspect 1 : A method of wireless communication performed by a user equipment (UE), comprising: buffering, at a selected layer of the UE, a set of application data associated with a plurality of applications instantiated on the UE based on at least one of latency information or power information in association with a buffering time period; and transmitting the set of application data based on at least one of an expiration of the buffering time period or an indication associated with an application of the plurality of applications.

[0124] Aspect 2: The method of Aspect 1, wherein the selected layer is based on the at least one of the latency information or the power information.

[0125] Aspect 3 : The method of Aspect 2, wherein the selected layer comprises at least one of a wireless local area network (WLAN) driver or a lower layer.

[0126] Aspect 4: The method of Aspect 3, wherein the selected layer comprises the WLAN driver based on the application data comprising packets associated with a latency that satisfies a high latency condition.

[0127] Aspect 5: The method of any of Aspects 2-4, wherein the lower layer comprises a medium access control (MAC) layer.

[0128] Aspect 6: The method of Aspect 5, wherein the selected layer comprises the MAC layer and is based on the application data comprising packets associated with a latency that satisfies a low latency condition.

[0129] Aspect 7: The method of any of Aspects 2-6, further comprising: obtaining an additional set of application data; and moving the set of application data from the selected layer to an additional selected layer based on obtaining the additional set of application data.

[0130] Aspect 8: The method of Aspect 7, wherein the set of application data comprises a first packet associated with a first latency value and the additional set of application data comprises a second packet associated with a second latency value, and wherein moving the set of application data from the selected layer to the additional selected layer comprises moving the first packet based on the second latency value being less than the first latency value.

[0131] Aspect 9: The method of any of Aspects 1-8, wherein the power information is associated with a power requirement of the UE while operating in association with an XR application.

[0132] Aspect 10: The method of any of Aspects 1-9, wherein the power information is associated with a power profile of at least one component of a system architecture of the UE.

[0133] Aspect 11 : The method of any of Aspects 1-10, further comprising flushing the set of application data from a memory of the UE based on an expiry of a timer associated with a first XR application of the plurality of applications.

[0134] Aspect 12: The method of any of Aspects 1-11, further comprising flushing the set of application data from a memory of the UE based on a latency tolerance value.

[0135] Aspect 13: The method of any of Aspects 1-12, further comprising obtaining the indication associated with the application.

[0136] Aspect 14: The method of Aspect 13, wherein the set of application data comprises a packet that includes the indication.

[0137] Aspect 15: The method of either of claims 13 or 14, wherein obtaining the indication comprises obtaining the indication based on an application programming interface.

[0138] Aspect 16: The method of any of Aspects 1-15, wherein the set of application data comprises a first data packet associated with a first flow and a second data packet associated with a second flow, and wherein transmitting the set of application data comprises: transmitting, based on the first data packet being associated with the first flow, the first data packet based on a latency tolerance value associated with the buffering time period; and transmitting, based on the second data packet being associated with the second flow, the second data packet based on the indication.

[0139] Aspect 17: The method of any of Aspects 1-16, wherein the set of application data comprises a set of extended reality data.

[0140] Aspect 18: An apparatus for wireless communication at a device, comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-17.

[0141] Aspect 19: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-17.

[0142] Aspect 20: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-17.

[0143] Aspect 21 : A non-transitory computer-readable medium storing code for wireless communication, the code comprising instmctions executable by a processor to perform the method of one or more of Aspects 1-17.

[0144] Aspect 22: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-17.

[0145] 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 acquired from practice of the aspects.

[0146] As used herein, the term “component” is intended to be broadly construed as hardware and / or a combination of hardware and software. “Software” shall be construed broadly 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, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein may be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and / or methods based, at least in part, on the description herein.

[0147] The hardware and data processing apparatus used to implement the various illustrative logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunctionwith a DSP core, or any other such configuration. In some aspects, particular processes and methods may be performed by circuitry that is specific to a given function.

[0148] As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

[0149] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0150] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are 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 referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, 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.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’).

Claims

WHAT IS CLAIMED IS:

1. An apparatus for wireless communication, comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the apparatus to: buffer, at a selected layer of the apparatus, a set of extended reality (XR) data associated with a plurality of XR applications instantiated on the apparatus based on at least one of latency information or power information in association with a buffering time period; and transmit the set of XR data based on at least one of an expiration of the buffering time period or an indication associated with an XR application of the plurality of XR applications.

2. The apparatus of claim 1, wherein the selected layer is based on the at least one of the latency information or the power information.

3. The apparatus of claim 2, wherein the selected layer comprises at least one of a wireless local area network (WLAN) driver or a lower layer.

4. The apparatus of claim 3, wherein the selected layer comprises the WLAN driver based on the XR data comprising packets associated with a latency that satisfies a high latency condition.

5. The apparatus of claim 2, wherein the lower layer comprises a medium access control (MAC) layer.

6. The apparatus of claim 5, wherein the selected layer comprises the MAC layer and is based on the XR data comprising packets associated with a latency that satisfies a low latency condition.

7. The apparatus of claim 2, wherein the one or more processors are further individually or collectively configured to cause the apparatus to: obtain an additional set of XR data; and move the set of XR data from the selected layer to an additional selected layer based on obtaining the additional set of XR data.

8. The apparatus of claim 7, wherein the set of XR data comprises a first packet associated with a first latency value and the additional set of XR data comprises a second packet associated with a second latency value, and the one or more processors, to cause the apparatus to move the set of XR data from the selected layer to the additional selected layer, are individually or collectively configured to move the first packet based on the second latency value being less than the first latency value.

9. The apparatus of claim 1, wherein the power information is associated with a power requirement of the apparatus while operating in association with an XR application.

10. The apparatus of claim 1, wherein the power information is associated with a power profile of at least one component of a system architecture of the apparatus.

11. The apparatus of claim 1, wherein the one or more processors are further individually or collectively configured to cause the apparatus to flush the set of XR data from a memory of the apparatus based on an expiry of a timer associated with a first XR application of the plurality of XR applications.

12. The apparatus of claim 1, wherein the one or more processors are further individually or collectively configured to cause the apparatus to flush the set of XR data from a memory of the apparatus based on a latency tolerance value.

13. The apparatus of claim 1, wherein the one or more processors are further individually or collectively configured to cause the apparatus to obtain the indication associated with the XR application.

14. The apparatus of claim 13, wherein the set of XR data comprises a packet that includes the indication.

15. The apparatus of claim 13, wherein the one or more processors, to cause the apparatus to obtain the indication, are individually or collectively configured to cause the apparatus to obtain the indication based on an application programming interface.

16. The apparatus of claim 1, wherein the set of XR data comprises a first data packet associated with a first flow and a second data packet associated with a second flow, and wherein the one or more processors, to cause the apparatus to transmit the set of XR data, are individually or collectively configured to cause the apparatus to:transmit, based on the first data packet being associated with the first flow, the first data packet based on a latency tolerance value associated with the buffering time period; and transmit, based on the second data packet being associated with the second flow, the second data packet based on the indication.

17. A method of wireless communication performed by a user equipment (UE), comprising: buffering, at a selected layer of the UE, a set of extended reality (XR) data associated with a plurality of XR applications instantiated on the UE based on at least one of latency information or power information in association with a buffering time period; and transmitting the set of XR data based on at least one of an expiration of the buffering time period or an indication associated with an XR application of the plurality of XR applications.

18. The method of claim 17, wherein the selected layer is based on the at least one of the latency information or the power information.

19. The method of claim 18, wherein the selected layer comprises at least one of a wireless local area network (WLAN) driver or a lower layer.

20. The method of claim 18, wherein the lower layer comprises a medium access control (MAC) layer.

21. The method of claim 18, further comprising: obtaining an additional set of XR data; and moving the set of XR data from the selected layer to an additional selected layer based on obtaining the additional set of XR data.

22. The method of claim 17, wherein the power information is associated with a power requirement of the UE while operating in association with an XR application.

23. The method of claim 17, wherein the power information is associated with a power profile of at least one component of a system architecture of the UE.

24. The method of claim 17, further comprising flushing the set of XR data from a memory of the UE based on an expiry of a timer associated with a first XR application of the plurality of XR applications.

25. The method of claim 17, further comprising flushing the set of XR data from a memory of the UE based on a latency tolerance value.

26. The method of claim 17, further comprising obtaining the indication associated with the XR application.

27. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: buffer, at a selected layer of the UE, a set of extended reality (XR) data associated with a plurality of XR applications instantiated on the UE based on at least one of latency information or power information in association with a buffering time period; and transmit the set of XR data based on at least one of an expiration of the buffering time period or an indication associated with an XR application of the plurality of XR applications.

28. The non-transitory computer-readable medium of claim 27, wherein the selected layer is based on the at least one of the latency information or the power information.

29. An apparatus for wireless communication, comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the apparatus to: buffer, at a selected layer of the apparatus, a set of application data associated with a plurality of applications instantiated on the apparatus based on at least one of latency information or power information in association with a buffering time period; and transmit the set of application data based on at least one of an expiration of the buffering time period or an indication associated with an application of the plurality of applications.

30. The apparatus of claim 29, wherein the set of application data comprises a set of extended reality data.

Images