Delay Status Report

Abstract

A user equipment (UE) may buffer data associated with a service. The deferral status of the data may include the amount of time remaining until a timer expires (e.g., failure of a particular latency requirement) or identification of data for which a timer has already expired (e.g., data for which a particular latency requirement has not been met). Some aspects described herein enable deferral status reporting. For example, a UE may generate and transmit a deferral status report to a network node that identifies the deferral status of the data.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS)

[0001] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 481,379, filed January 24, 2023, entitled "DELAY STATUS REPORTING," and U.S. Non-Provisional Patent Application No. 18 / 396,252, filed December 26, 2023, entitled "DELAY STATUS REPORTING," both of which are expressly incorporated herein by reference.

[0002] Aspects of the present disclosure generally relate to wireless communications and to techniques and apparatus for delayed status reporting. [Background technology]

[0003]

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. 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, etc.). 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 extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[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 and uplink communications. The "downlink" (or "DL") refers to the communication link from the network node to the UE, and the "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communications via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, among other examples).

[0005]

[0005] The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that allows various UEs to communicate at a city, country, region, and / or global level. 5G, sometimes referred to as New Radio (NR), is a set of extensions to the LTE mobile standard promulgated by 3GPP. 5G is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink and 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 to better integrate with other open standards, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As demand for mobile broadband access continues to increase, further improvements in 4G, 5G, and other radio access technologies remain useful. Summary of the Invention

[0006] A user equipment (UE) may buffer data associated with a service. For example, a UE may have a buffer associated with data for an extended reality (XR) service provided by the UE or by one or more XR devices communicating with the UE. The data may be associated with different entities, such as a data radio bearer, a logical channel, or a set of logical channels (e.g., a logical channel group). Some data may be associated with a timing reference. For example, some data may have latency requirements as part of the service provided. In this case, an XR service may be associated with a specific latency requirement, and data associated with an XR service may be subject to the specific latency requirement. In some embodiments, the delay status of data may include the amount of time remaining until a timer expires (e.g., failure of a specific latency requirement), or identification of data for which a timer has already expired (e.g., data for which a specific latency requirement has not been met). A network node may schedule communication resources to ensure that the data is not delayed. However, the network node may lack information about the data and / or communication delays associated with the data.

[0007] Some aspects described herein enable delayed status reporting. For example, a UE may receive information identifying a set of criteria for generating a delayed status report, and may generate and transmit the delayed status report to a network node when the set of criteria is met. In this case, the network node may use the delayed status report to configure communications on the network, such as by scheduling resources, balancing load, or modifying quality of service parameters, among other examples. In this manner, the UE and network node may improve the service being provided on the network, such as by scheduling additional resources to improve XR service latency when XR data is delayed.

[0008] Certain aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving information identifying a set of criteria for a deferred status report. The method may include transmitting, based at least in part on the set of criteria being satisfied, a deferred status report including an indicator of an amount of data and a deferred status associated with the amount of data.

[0009] Certain aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting information identifying a set of criteria for a deferred status report. The method may include receiving, based at least in part on the set of criteria being met, a deferred status report including an indicator of a data amount and a deferred status associated with the data amount.

[0010] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive information identifying a set of criteria for a deferred status report. The one or more processors may be configured to transmit a deferred status report including an indicator of an amount of data and a deferred status associated with the amount of data based at least in part on the set of criteria being satisfied.

[0011] Some aspects described herein relate to a network node for wireless communications. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit information identifying a set of criteria for a deferred status report. The one or more processors may be configured to receive, based at least in part on the set of criteria being met, a deferred status report including an indicator of a data amount and a deferred status associated with the data amount.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive information identifying a set of criteria for a deferred status report. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to transmit a deferred status report including an indicator of an amount of data and a deferred status associated with the amount of data based at least in part on the set of criteria being met.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit information identifying a set of criteria for a deferral status report. The set of instructions, when executed by the one or more processors of the network node, may cause the network node to receive a deferral status report including an indicator of a data volume and a deferral status associated with the data volume based at least in part on the set of criteria being met.

[0014] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving information identifying a set of criteria for a deferred status report. The apparatus may include means for transmitting, based at least in part on the set of criteria being met, a deferred status report including an indicator of a data amount and a deferred status associated with the data amount.

[0015] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting information identifying a set of criteria for a deferred status report. The apparatus may include means for receiving, based at least in part on the set of criteria being met, a deferred status report including an indicator of a data amount and a deferred status associated with the data amount.

[0016]

[0016] The foregoing has outlined rather broadly the features and technical advantages of embodiments of the present disclosure in order that the following Detailed Description may be better understood. Additional features and advantages will be described hereinafter. The concepts 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 structures do not depart from the scope of the appended claims. The properties 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 conjunction with the accompanying figures. Each of the figures is provided for purposes of illustration and description, and not as a definition of the limits of the claims. [Brief explanation of the drawings]

[0017] [Figure 1]

[0017] FIG. 1 illustrates an example of a wireless network according to the present disclosure. [Figure 2]

[0018] FIG. 1 illustrates an example of a network node in communication with a user equipment (UE) in a wireless network according to the present disclosure. [Figure 3]

[0019] FIG. 1 illustrates an exemplary disaggregated base station architecture in accordance with the present disclosure. [Figure 4]

[0020] FIG. 10 illustrates an example of timing for delayed status reporting in accordance with the present disclosure. [Figure 5A]

[0021] FIG. 1 illustrates an example associated with delayed status reporting according to the present disclosure. [Figure 5B] FIG. 1 illustrates an example associated with delayed status reporting according to the present disclosure. [Figure 6]

[0022] 1 is a flowchart of an exemplary method of wireless communication according to the present disclosure. [Figure 7]

[0023] 1 is a flowchart of an exemplary method of wireless communication according to the present disclosure. [Figure 8]

[0024] FIG. 1 is a diagram of an exemplary apparatus for wireless communication according to the present disclosure. [Figure 9]

[0025] FIG. 1 illustrates an example of a hardware implementation for an apparatus employing a processing system according to the present disclosure. [Figure 10]

[0026] FIG. 1 is a diagram of an exemplary apparatus for wireless communication according to the present disclosure. [Figure 11]

[0027] FIG. 1 illustrates an example of a hardware implementation for an apparatus employing a processing system according to the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0018]

[0028] The detailed description set forth below in connection with the accompanying drawings is intended as a description of various configurations and is not intended to represent configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0019]

[0029] A user equipment (UE) may buffer data associated with a service. For example, a UE may have a buffer associated with data for an extended reality (XR) service provided by the UE or by one or more XR devices in communication with the UE. The delay status of the data may include the amount of time remaining until a timer expires (e.g., failure of a particular latency requirement) or identification of data for which a timer has already expired (e.g., data for which a particular latency requirement has not been met). A network node may schedule communication resources to ensure that the data is not delayed. However, the network node may lack information about the data and / or communication delays associated with the data.

[0020]

[0030] Various aspects relate generally to deferred status reporting. Some aspects relate, more specifically, to generating deferred status reports and transmitting deferred status reports. In some aspects, a UE may receive information identifying a set of criteria for generating a deferred status report. In some aspects, the UE may determine that the set of criteria are met and generate a deferred status report related to determining that the set of criteria are met. In some aspects, the UE may transmit the deferred status report to a network node. The network node may use the deferred status report to configure communications on the network, such as by scheduling resources, balancing load, or modifying quality of service parameters, among other examples.

[0021]

[0031] Certain aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages: In some embodiments, by having a UE generate and transmit a delay status report in connection with a configured set of criteria being met, the UE and network nodes can improve the service being provided over the network. For example, the described techniques can enable scheduling of additional resources to improve XR service latency, for example, in cases where XR data is delayed.

[0022]

[0032] Certain aspects of telecommunications systems are presented herein with reference to various apparatus and methods. These apparatus and methods are described in the following Detailed Description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0023]

[0033] As an example, an element or any portion of an element or any combination of elements may be implemented in a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functionality described throughout this disclosure. One or more processors in a processing system may execute 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, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0024]

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

[0025]

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

[0026]

[0036] 1 is a diagram illustrating an example of a wireless network 100. The wireless network 100 may be or include, among other examples, an element of a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network. The wireless network 100 may include one or more network nodes 110 (illustrated as network node 110a, network node 110b, network node 110c, and network node 110d), a UE 120 or multiple UEs 120 (illustrated as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other entities. The network node 110 is an example of a network node that communicates with the UE 120. As shown, the network node 110 may include one or more network nodes. For example, 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 RAN node (e.g., within a single device or unit). As another example, network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (e.g., one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0027]

[0037] In some embodiments, the network node 110 is or includes a network node, such as a RU, that communicates with the UE 120 over a radio access link. In some embodiments, the network node 110 is or includes a network node, such as a DU, that communicates with other network nodes 110 over a fronthaul link or a midhaul link. In some embodiments, the network node 110 is or includes a network node, such as a CU, that communicates with other network nodes 110 over a midhaul link or with a core network over a backhaul link. In some embodiments, the network node 110 (e.g., an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network nodes 110 may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points or transmission reception points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some embodiments, the network nodes 110 may be interconnected to each other or to one or more other network nodes 110 within the wireless network 100 through various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0028]

[0038] In some embodiments, 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 the coverage area of ​​a network node 110 or a network node subsystem serving that coverage area, depending on the context in which the term is used. A network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 that have an association with the femtocell (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 a home network node. In the example shown in FIG. 1 , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or multiple (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move according to the location of a mobile network node 110 (e.g., a mobile network node).

[0029]

[0039] In some aspects, the term “base station” or “network node” may refer to an aggregated base station, a non-aggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a “base station” or “network node” may refer to a CU, DU, RU, a Near-Real Time (RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof. In some aspects, the term “base station” or “network node” may refer to one device configured to perform one or more functions, such as the functions described herein in connection with network node 110. In some aspects, the term “base station” or “network node” may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, multiple different devices (which may be located in the same geographic location or different geographic locations) may each be configured to perform at least a portion of the functions or to replicate the performance of at least a portion of the functions, and the term "base station" or "network node" may refer to any one or more of those different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions and not another base station function. In this manner, a single device may include two or more base stations.

[0030]

[0040] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a data transmission from an upstream node (e.g., the network node 110 or the UE 120) and forward the data transmission to a downstream node (e.g., the UE 120 or the network node 110). A relay station may also be a UE 120 that can relay a transmission for another UE 120. In the embodiment shown in FIG. 1, network node 110d (e.g., a relay network node) may communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communications between network node 110a (e.g., a macro network node) and 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, or a repeater, among other examples.

[0031]

[0041] The wireless network 100 may be a heterogeneous network including different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different susceptibility to interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5-40 watts), while a pico network node, femto network node, and relay network node may have a lower transmit power level (e.g., 0.1-2 watts).

[0032]

[0042] A network controller 130 may be coupled to or in communication 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 backhaul or midhaul communication links. The network nodes 110 may communicate with each other directly or indirectly via wireless or wired backhaul communication links. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0033]

[0043] The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be fixed or mobile. The UEs 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. The UEs 120 may be a cellular phone (e.g., a smartphone), 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, smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device configured to communicate over a wireless or wired medium.

[0034]

[0044] Some UEs 120 may be considered machine-type communication (MTC) UEs or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, 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 Internet-of-Things (IoT) devices or implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UEs 120 may be included within a housing that houses components of the UE 120, such as a processor component or a memory component. In some embodiments, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0035]

[0045] In general, any number of wireless networks 100 may be deployed within 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 or air interface. A frequency may be referred to as a carrier or frequency channel. To avoid interference between wireless networks of different RATs, each frequency may support a single RAT within a given geographic area. In some cases, NR or 5G RAT networks may be deployed.

[0036]

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

[0037]

[0047] Devices of wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, or channels. For example, devices of wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified, designated frequency ranges FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although portions of FR1 are above 6 GHz, FR1 is often referred to (interchangeably) as the “sub-6 GHz” band in various documents and papers. Similar nomenclature issues may arise with respect to FR2, which is often referred to (interchangeably) as the “millimeter wave” band in documents and papers, despite being different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunications Union (ITU) as the “millimeter wave” band.

[0038]

[0048] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as a frequency range designated FR3 (7.125 GHz to 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 or FR2 characteristics, thus effectively extending the features of FR1 or FR2 to mid-band frequencies. However, 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 ranges designated FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0039]

[0049] With these examples in mind, unless otherwise specified, the term "sub-6 GHz," as used herein, may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise specified, the term "millimeter wave," as used herein, may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a, or FR4-1, or FR5, or may be within the EHF band. Frequencies included within these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and it is contemplated that the techniques described herein are applicable to those modified frequency ranges.

[0040]

[0050] In some aspects, UE 120 may include communications manager 140. As described in more detail elsewhere herein, communications manager 140 may receive information identifying a set of criteria for a deferred status report and, based at least in part on the set of criteria being met, transmit a deferred status report including an indicator of the amount of data and a deferred status associated with the amount of data. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0041]

[0051] In some aspects, network node 110 may include a communications manager 150. As described in more detail elsewhere herein, communications manager 150 may transmit information identifying a set of criteria for a deferral status report and receive a deferral status report including an indicator of data volume and a deferral status associated with the data volume based at least in part on the set of criteria being met. Additionally or alternatively, communications manager 150 may perform one or more other operations described herein.

[0042]

[0052] As noted above, Figure 1 is provided as an example. Other implementations may differ from those described with respect to Figure 1.

[0043]

[0053] 2 illustrates an example network node 110 200 in communication with a UE 120 in a wireless network 100. The network node 110 may be equipped with a set of antennas 234a-234t, such as T antennas (T≧1). The UE 120 may be equipped with a set of antennas 252a-252r, such as R antennas (R≧1). The network node 110 of the example 200 includes one or more radio frequency components, such as the antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0044]

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

[0045]

[0055] At the UE 120, the set of antennas 252 (depicted as antennas 252a through 252r) may receive downlink signals from the network node 110 or another network node 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), depicted as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (depicted as DEMOD) of the modem 254. Each modem 254 may condition (e.g., filter, amplify, downconvert, or digitize) the received signal using its respective demodulator component to obtain input samples. Each modem 254 may further process the input samples (e.g., for OFDM) using the demodulator component to obtain received symbols. A MIMO detector 256 may obtain the received symbols from the modems 254, perform MIMO detection on the received symbols if applicable, and provide the detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control and system information to the controller / processor 280. The term “controller / processor” may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, or a CQI parameter, among other examples. In some embodiments, one or more components of the UE 120 may be included within a housing 284.

[0046]

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

[0047]

[0057] One or more antennas (e.g., antennas 234a-t or antennas 252a-r) may include or be contained within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled to one or more transmitting or receiving components, such as one or more components of FIG. 2.

[0048]

[0058] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some embodiments, the modem 254 of the UE 120 may include a modulator and demodulator. In some embodiments, 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, or the TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the processes described herein.

[0049]

[0059] In the network node 110, uplink signals from the UE 120 or other UEs may be received by an antenna 234, processed by a modem 232 (e.g., a demodulator component, denoted 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 the decoded control information to a 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 for scheduling one or more UEs 120 for downlink or uplink communications. In some embodiments, the modem 232 of the network node 110 may include a modulator and a demodulator. In some embodiments, the network node 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, modem(s) 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform any aspect of the processes described herein.

[0050]

[0060] As described in more detail elsewhere herein, 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 deferred status reporting. 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 the operations of, for example, method 600 of FIG. 6, method 700 of FIG. 7, and / or other processes as described herein. The memory 242 and the memory 282 may store data and program code for the network node 110 and the UE 120, respectively. In some embodiments, 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 by one or more processors of the network node 110 and / or the UE 120 (e.g., directly or after being compiled, translated, and / or interpreted), may cause the one or more processors, the UE 120, and / or the network node 110 to perform or direct operations of, for example, method 600 of FIG. 6, method 700 of FIG. 7, and / or other processes as described herein. In some embodiments, executing instructions may include running the instructions, translating the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.

[0051]

[0061] In some aspects, the UE 120 includes means for receiving information identifying a set of criteria for a deferred status report and / or means for transmitting a deferred status report including an indicator of the amount of data and a deferred status associated with the amount of data based at least in part on the set of criteria being met. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0052]

[0062] In some aspects, the network node 110 includes means for transmitting information identifying a set of criteria for a deferred status report and / or means for receiving a deferred status report including an indicator of the amount of data and a deferred status associated with the amount of data based at least in part on the set of criteria being met. Means for the network node 110 to perform the operations described herein may include, for example, one or more of the communications manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antennas 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0053]

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

[0054]

[0064] As noted above, Figure 2 is provided as an example. Other implementations may differ from those described with respect to Figure 2.

[0055]

[0065] The deployment of a communication system, such as a 5G NR system, can be configured in multiple ways with various components or parts. In a 5G NR system or network, a network node, network entity, network mobility element, RAN node, core network node, network element, base station, or network equipment may be implemented in a centralized or disaggregated architecture. For example, a base station (e.g., a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, among other examples), or one or more units (or one or more components) performing base station functionality, may be implemented as a centralized base station (also known as a standalone base station or monolithic base station) or a disaggregated base station. A "network entity" or a "network node" may refer to a disaggregated base station or may refer to one or more units (e.g., one or more CUs, one or more DUs, one or more RUs, or a combination thereof) of a disaggregated base station.

[0056]

[0066] 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 (e.g., one or more CUs, one or more DUs, or one or more RUs). In some embodiments, a CU may be implemented within a network node, and one or more DUs may be collocated with the CU or, alternatively, geographically or virtually distributed throughout one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

[0057]

[0067] The operation or network design of a base station type may take into account the 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 a network configuration supported 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 the communication system by separating base station functionality into one or more units that can be deployed independently. A disaggregated base station may include functionality implemented across two or more units in various physical locations as well as functionality implemented virtually in at least one unit, which may allow flexibility in network design. Various units of a disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0058]

[0068] 3 illustrates an example disaggregated base station architecture 300 according to 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 (quasi-RT RIC 325 via an E2 link, or non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, for example, through an F1 interface. 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 served by multiple RUs 340 simultaneously.

[0059]

[0069] Each of the units, including the CU 310, DU 330, RU 340, and quasi-RT RIC 325, non-RT RIC 315, and SMO framework 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the respective unit's one or more communication interfaces, may be configured to communicate with one or more of the other units over a transmission medium. In some embodiments, each of the units may include a wired interface configured to receive or transmit signals to or from one or more of the other units over a wired transmission medium, and a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver), configured to receive, transmit, or transmit and receive signals to or from one or more of the other units over a wireless transmission medium.

[0060]

[0070] In some aspects, the CU 310 may host one or more higher-layer control functions. Such control functions may include, among other examples, a radio resource control (RRC) function, a packet data convergence protocol (PDCP) function, or a service data adaptation protocol (SDAP) function. Each control function may implement 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 (e.g., Central Unit-User Plane (CU-UP) functionality), control plane functionality (e.g., Central Unit-Control Plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may bidirectionally communicate with the CU-CP unit via an interface, such as an E1 interface. The CU 310 may be implemented to communicate with the DU 330 as needed for network control and signaling.

[0061]

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

[0062]

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

[0063]

[0073] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support deployment of dedicated physical resources related to RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (e.g., an open cloud (O-Cloud) platform 390) to perform lifecycle management of the network element (e.g., to instantiate virtualized network elements) via a cloud computing platform interface (e.g., an O2 interface). Such virtualized network elements may include, but are not limited to, the CU 310, the DU 330, the RU 340, the non-RT RIC 315, and the quasi-RT RIC 325. In some implementations, the SMO framework 305 may communicate with hardware aspects of a 4G RAN, such as the open eNB (O-eNB) 311, via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via their respective O1 interfaces. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0064]

[0074] The non-RT RIC 315 may be configured to include logic functions that enable 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 / functions in the quasi-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the quasi-RT RIC 325 (e.g., via an A1 interface). The quasi-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and action via interfaces (e.g., via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, and the O-eNB to the quasi-RT RIC 325.

[0065]

[0075] In some implementations, the non-RT RIC 315 may receive parameters or external enrichment information from an external server to generate AI / ML models to be deployed in the quasi-RT RIC 325. Such information may be utilized by the quasi-RT RIC 325 and may be received at the SMO framework 305 or non-RT RIC 315 from non-network data sources or from network functions. In some embodiments, the non-RT RIC 315 or quasi-RT RIC 325 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns in performance, employ AI / ML models, and take corrective action through the SMO framework 305 (e.g., reconfiguration via the O1 interface) or through the creation of RAN management policies (e.g., A1 interface policies).

[0066]

[0076] As noted above, Figure 3 is provided as an example. Other implementations may differ from those described with respect to Figure 3.

[0067]

[0077] FIG. 4 is a diagram illustrating an example timing 400 for delayed status reporting in accordance with the present disclosure.

[0068]

[0078] As shown in FIG. 4, the reporting entity may be configurable with a timeline for delay status reporting (DSR), which may also be referred to as "delay information reporting (DIR)." The reporting entity may be an entity to which UE 120 reports delay information in a DSR message. For example, the reporting entity may be a data radio bearer (DRB), a logical channel (LCH), or a set of logical channels (e.g., a logical channel group (LCG)). In some embodiments, a DRB may include multiple LCHs corresponding to multiple protocol data unit (PDU) sets, each including one or more PDUs with common parameters (e.g., importance level parameters). UE 120 may be configured with multiple reporting entities in some embodiments.

[0069]

[0079] As further shown in FIG. 4, the timeline for delay status reporting may be based at least in part on arrival time 410. Arrival time 410 may include the time when the first PDU of the PDU set is received by UE 120. In some embodiments, the first received PDU may differ from the first indexed PDU (e.g., as a result of out-of-order delivery of the PDUs). The amount of remaining time for the PDU may be associated with a PDU set delay budget (PSDB) or a packet delay budget (PDB). For example, UE 120 (or its reporting entity) may be configured with a PSDB timer that represents the amount of time after arrival time 410 during which the PDU set may be delivered from UE 120 to a destination device (e.g., a network node (not shown)). Similarly, the UE 120 may be configured with a PDB timer, which represents the amount of time after the arrival time 410 during which a PDU (e.g., not associated with a PDU set) may be delivered from the UE 120 to the destination device (e.g., before a failure occurs).

[0070]

[0080] The UE 120 determines the time threshold 420 (T DIR,m ) The time threshold 420 may be configured as an absolute time or a percentage of time between the arrival time 410 and the end of the PSDB or PDB. However, the network node 110 and the UE 120 may lack signaling to exchange or synchronize configurations related to the reporting timeline of the reporting entity. For example, the UE 120 may not be configured with information indicating a trigger threshold that would allow the UE 120 to determine whether the trigger threshold is met at the time threshold 420. Thus, the UE 120 and the network node 110 may not be synchronized on the current time 430 and may not evaluate whether the deadline 440 has occurred.

[0071]

[0081] As mentioned above, Figure 4 is provided as an example. Other implementations may differ from those described with respect to Figure 4.

[0072]

[0082] Some aspects described herein enable deferred status reporting. For example, a UE may receive information identifying a set of criteria for generating a deferred status report and may generate and transmit a deferred status report to a network node when the set of criteria is met. In this case, the network node may use the deferred status report to configure communications over the network, such as by scheduling resources, balancing load, or modifying quality of service parameters, among other examples. In this manner, the UE and network node may improve services being provided over the network, such as by scheduling additional resources to improve XR service latency when XR data is delayed. In some aspects, by enabling configuration of the reporting entity (e.g., UE 120), the network node and UE remain synchronized, which may enable efficient allocation of resources for transmitting data associated with one or more services.

[0073]

[0083] 5A and 5B illustrate an example 500 associated with deferred status reporting in accordance with the present disclosure. As shown in FIG. 5A and 5B, the example 500 includes communication between a network node 110 and a UE 120.

[0074]

[0084] As further indicated by reference numeral 510 in FIG. 5A , the UE 120 may receive information identifying a deferred status reporting configuration. For example, the UE 120 may receive information from the network node 110 identifying a set of criteria for deferred status reporting. The set of criteria for deferred status reporting may include one or more parameter values, such as one or more values ​​for a delay deadline, a data volume threshold, an amount of time for a prohibit timer, a reporting threshold, or another configurable parameter, as described herein. In some aspects, the UE 120 may receive information identifying a parameter for determining whether a delay deadline has been met. For example, the UE 120 may receive information identifying a PSDB. In this case, the UE 120 may determine the amount of time remaining for transmitting a deferred status report based at least in part on the delay deadline (e.g., which is a function of the PSDB) and a current time (e.g., at which the UE 120 evaluates whether to transmit a deferred status report). Additionally or alternatively, the UE 120 may receive information identifying a PDB for determining a delay deadline for PDUs not included in the PDU set. In some aspects, the PDB may be configured based on a quality of service (QoS) flow-specific basis. For example, the UE 120 may receive information indicating a PDB for a particular QoS flow (and its PDUs). A QoS flow may refer to one or more data packets associated with a particular PDU and / or data radio bearer (DRB) and associated with one or more QoS parameters such as a priority level, a data rate, or latency, among other examples. Thus, the UE 120 may have multiple QoS flows for receiving traffic from a network (e.g., the network node 110) and may have a PDB (e.g., a different PDB or the same PDB) for each QoS flow. The PDB may be a QoS characteristic that specifies an upper bound on the amount of time a packet may be delayed between the UE 120 and a network source associated with the network node 110.For example, a particular QoS flow may be configured with a PDB of 2 milliseconds (ms), indicating that packets may be delayed by up to 2 ms when transported, for example, from a user plane function (UPF) to a UE 120 (e.g., via a network node 110).

[0075]

[0085] In some aspects, UE 120 may receive information identifying a time threshold. For example, UE 120 may receive information identifying a time threshold T associated with reporting entity m of UE 120. DIR,m In this case, UE 120 may evaluate whether a time threshold is met to determine whether to generate and transmit a delayed status report for reporting entity m, as described herein. Additionally or alternatively, UE 120 may receive information indicating a data volume threshold V , which represents the amount of data accumulated in a buffer before a delayed status report is triggered. prohibit In this case, V prohibit The value of V can be configured to control when UE 120 triggers a delayed status report (e.g., V prohibit A higher value of reduces the frequency of delay status reports, thereby reducing network resource utilization, and V prohibit (A lower value of increases the frequency of delay status reports, thereby reducing delay.) The amount of data may include, for example, the amount of data stored in the buffer (e.g., a number of packets, a number of bits, or another data metric).

[0076]

[0086] Additionally or alternatively, UE 120 may determine a time threshold T 1 , which represents a period of time during which UE 120 will not trigger a deferred status report. prohibit In this case, T prohibit The value of T can be configured to control when UE 120 triggers a delayed status report (e.g., T prohibit A higher value of reduces the frequency of delay status reports, thereby reducing network resource utilization, and T prohibitLower values ​​of increase the frequency of delay status reports, thereby reducing delay).

[0077]

[0087] 5A by reference numerals 520 and 530, UE 120 may evaluate whether to send a deferred status report and may generate a deferred status report. For example, UE 120 may determine whether a set of criteria for a deferred status report is met and, if the set of criteria is met, may generate a deferred status report identifying the status of the buffer.

[0078]

[0088] In some aspects, UE 120 may determine whether a delay deadline has been met. For example, UE 120 may determine whether a delay deadline has been met for one or more PDUs. In some aspects, the PDU may be included in a PDU set. If the PDU is included in the PDU set, UE 120 may determine the delay deadline based at least in part on the time at which a first PDU of the PDU set is received by the UE. For example, UE 120 may receive a first PDU of the PDU set (e.g., which may or may not be the first index PDU of the PDU set) at time T1, and the delay deadline T deadline =T1+T2, where T2 represents the PSDB of the QoS flow that includes the first PDU received. Thus, the UE 120 may determine that the remaining time for transmitting the delay status report is T remaining =T deadline -T current where T current represents the time during which UE 120 is evaluating whether to send a delay status report. Alternatively, if the received PDU is not included in the PDU set, UE 120 may determine the delay deadline based at least in part on the PDB. For example, UE 120 may receive a PDU and determine T deadline =T1+T2, where T1 represents the time the PDU is received and T2 represents the PDB for the QoS flow that contains the PDU.

[0079]

[0089] In some aspects, UE 120 may determine whether a time threshold for reporting the deferral status is met. For example, a reporting entity m of UE 120 (e.g., UE 120 may include multiple reporting entities corresponding to multiple applications or QoS flows) may determine whether a time threshold T DIR,m which, when met, may trigger UE 120 to send a deferred status report.

[0080]

[0090] In some aspects, UE 120 may determine whether a data volume threshold is met to determine whether to generate and transmit a deferred status report. For example, UE 120 may determine whether the amount of data in a buffer associated with the reporting entity is greater than or equal to a threshold V prohibit In some aspects, the UE 120 may determine whether a delayed status report is to be triggered for a slot. For example, the UE 120 may determine whether T DIR represents the amount of data with remaining time less than S urgent (T DIR Additionally or alternatively, UE 120 may DIR ×PSDB or T DIR × S as the amount of data with remaining time less than PDB urgent (T DIR Additionally or alternatively, UE 120 may determine the amount of data S reported in a previously triggered delayed status report. ref (e.g., if a previous delayed status report occurred, otherwise S ref may be set to a default value such as 0). urgent -S ref >V prohibit In other words, UE 120 determines whether the difference between the current amount of data having a remaining time less than the time threshold and the previously reported amount of data having a remaining time less than the time threshold is greater than a threshold amount.

[0081]

[0091] Similarly, the UE 120 starts the inhibit timer T prohibit The UE 120 may determine whether to generate and transmit a deferred status report based at least in part on whether a prohibit timer is active. For example, if a prohibit timer is not active (e.g., the UE 120 is not inhibited from triggering a deferred status report), the UE 120 may trigger a deferred status report. In this case, the UE 120 may start the prohibit timer when the deferred status report is triggered and may refrain from triggering a further deferred status report until after the prohibit timer has elapsed or after a deferred status report MAC control element (CE) (MAC CE) has been transmitted over a physical uplink shared channel (PUSCH).

[0082]

[0092] In some aspects, the UE 120 may determine whether to generate and transmit a delayed status report based at least in part on a configured periodicity. For example, the network node 110 may configure periodic reporting of the delayed status of the UE 120. In this case, the network node 110 may configure the delayed status reporting to occur at each period t, which may be a configurable parameter (e.g., configured via network node 110 radio resource control (RRC) signaling, such as a configuration information element (IE)) or a static parameter (e.g., in a specification, such as specifying the periodicity of the delayed status reporting to occur (or occur in some cases) at each slot). In some aspects, the network node 110 may enable or disable periodic reporting, for example, on a per reporting entity basis. For example, the network node 110 may configure the periodic delayed status reporting using static signaling and may select one or more reporting entities of the UE 120 for which the UE 120 will perform the periodic delayed status reporting by transmitting a MAC CE. In some aspects, UE 120 may determine whether to generate and transmit a deferred status report based at least in part on the occurrence of a mobility event. For example, a mobility event may occur when UE 120 changes its primary cell (PCell) (e.g., as a result of a handover) or its primary secondary cell (PSCell) (e.g., as a result of a secondary cell group (SCG) change). Based on these events, UE 120 may trigger a deferred status report to indicate the deferred status of one or more reporting entities of UE 120 to the new cell (e.g., network node 110).

[0083]

[0093] In some aspects, UE 120 may evaluate one or more reporting thresholds for one or more reporting entities m when generating a deferred status report. For example, UE 120 may evaluate one or more reporting thresholds V m,1 ,...,V m,n where n represents the number of intervals for reporting. In other words, UE 120 may evaluate the buffered data as V m,i and V m,i+1 , n), the UE 120 may determine to report at the remaining time between i=1,...n. For example, the UE 120 may generate a MAC CE, as shown in FIG. 5B, that conveys information associated with the set of reporting thresholds. In this case, the set of reporting entities and the set of values ​​that the UE 120 reports in the MAC CE may be based at least in part on the configuration information, for example.

[0084]

[0094] As further shown in FIG. 5B, the MAC CE may store a bitmap L that indicates whether reporting entity m is reported in the MAC CE. m In this case, the bitmap L m has a size of 2×B (e.g., if the reporting entity of UE 120 is a DRB or LCH), or 1×B, where B represents the number m of reporting entities. m which indicates which buffer status reporting table of a set of possible buffer status reporting tables is being used to report the amount of data. In this case, if UE 120 is configured with multiple classes of BSR tables, such as extended 3GPP Release 18-specific BSR tables and pre-Release 18 BSR tables, UE 120 may further include parameter B m For each reporting entity being reported, UE 120 may include V m,i and V m,j+1 a parameter S representing the amount of buffered data for reporting entity m, with the remaining time between m,i In some aspects, the UE 120 may include the mParameter S using the specified BSR table, as shown in m,j may be encoded as:

[0085]

[0095] In some aspects, the UE 120 may determine a parameter T that indicates the duration between a sampling instance (e.g., when the UE 120 determines the deferral status) and the transmission time of the PUSCH that includes the deferral status report. m For example, the UE 120 may indicate a number of slots indicating the duration between identifying the deferred status and reporting the deferred status. In some aspects, the sampling instance may represent a slot at which the deferred status report is triggered. In some aspects, the sampling instance may represent a slot at which a MAC PDU including the deferred status report is generated. In this case, the UE 120 may select a reporting entity and / or a reporting value of the reporting entity based at least in part on which sampling instance is used.

[0086]

[0096] As further indicated by reference numeral 540 in FIG. 5A , the UE 120 may transmit a deferred status report. For example, the UE 120 may transmit the deferred status report to the network node 110. In this case, the UE 120 may transmit the MAC CE using a PUSCH resource for transmitting the MAC CE, as described herein. In some aspects, the UE 120 may transmit the deferred status report with a particular priority. For example, the deferred status reporting MAC CE may be associated with a higher logical channel prioritization (LCP) priority value than that assigned to the buffer status report. In other words, the deferred status reporting MAC CE may have a first priority that is higher than the second priority of the buffer status report message, such that the deferred status reporting MAC CE may be prioritized to receive uplink resources for transmission.

[0087]

[0097] In some aspects, if there are available PUSCH resources and the UE 120 has a delayed status report pending for transmission, the UE 120 may multiplex the delayed status report onto the PUSCH for transmission. For example, the UE 120 may piggyback the delayed status report onto one or more other communications to be carried over the PUSCH resources. Additionally or alternatively, to carry the delayed status report on the PUSCH resources, the UE 120 may puncture the PUSCH resources and overwrite the one or more other communications to be carried over the PUSCH resources. Alternatively, the UE 120 may request PUSCH resources from the network node 110 via a scheduling request (SR). In this case, the network node 110 may configure dedicated physical uplink control channel (PUCCH) resources for transmitting the SR, e.g., to request resources for transmission of the delayed status report.

[0088]

[0098] In some aspects, UE 120 may start or stop an inhibit timer in connection with transmitting a MAC CE. For example, UE 120 may start or stop an inhibit timer T prohibit UE 120 may stop transmitting the deferred status report to allow for generation of a new, updated deferred status report. Additionally or alternatively, UE 120 may cancel one or more other pending deferred status reports. In some aspects, UE 120 may receive an allocation of resources. For example, based at least in part on transmitting the deferred status report, UE 120 may receive information from network node 110 identifying an allocation of resources for transmitting data reported in the deferred status report.

[0089]

[0099] As mentioned above, Figures 5A and 5B are provided as an example, and other embodiments may differ from those described with respect to Figures 5A and 5B.

[0090]

[0100] 6 is a flowchart of an example method of wireless communication 600. Method 600 may be performed, for example, by a UE (e.g., UE 120).

[0091]

[0101] At 610, the UE may receive information identifying a set of criteria for deferred status reporting. For example, the UE may receive (e.g., using the communications manager 140 and / or the receiving component 802 shown in FIG. 8 ) the information identifying the set of criteria for deferred status reporting as described above. In some aspects, the UE is configured to receive signaling associated with configuring one or more parameters for deferred status reporting. In some aspects, the one or more parameters include at least one of a data volume threshold parameter, a timer parameter, or one or more reporting thresholds.

[0092]

[0102] At 620, in some aspects, the UE may determine that a set of criteria for a deferred status report is met. For example, the UE may determine (e.g., using the communications manager 140 and / or the determining component 808 shown in FIG. 8) that the set of criteria for a deferred status report is met, as described above. In some aspects, the UE may determine that the set of criteria for a deferred status report is met based at least in part on determining that a timer has expired or that the amount of data in the buffer meets a threshold.

[0093]

[0103] At 630, in some aspects, the UE may generate a deferred status report. For example, the UE (e.g., using communications manager 140 and / or report generation component 810 shown in FIG. 8) may generate the deferred status report based at least in part on determining that a set of criteria for a deferred status report is met, as described above. In some aspects, the deferred status report is associated with a first priority that is higher than a second priority of the buffer status report. In some aspects, the deferred status report is multiplexed onto physical uplink shared channel resources. In some aspects, the deferred status report is included in the physical uplink shared channel resources requested via the scheduling request.

[0094]

[0104] At 640, the UE may transmit a deferral status report including an indicator of the amount of data and a deferral status associated with the amount of data based at least in part on the set of criteria being met. For example, the UE may transmit (e.g., using communications manager 140 and / or transmitting component 804 shown in FIG. 8 ) a deferral status report including an indicator of the amount of data and a deferral status associated with the amount of data based at least in part on the set of criteria being met, as described above.

[0095]

[0105] In some aspects, the deferred status report is associated with at least one of a data radio bearer, a logical channel, or a logical channel group. In some aspects, the deferred status is based at least in part on a delay deadline of a protocol data unit associated with an amount of data or a packet delay budget associated with a quality of service flow, where the quality of service flow includes the protocol data unit. In some aspects, the deferred status is based at least in part on a time threshold for triggering generation of the deferred status report or for reporting the deferred status report. In some aspects, the deferred status report is based at least in part on whether a threshold amount of data is associated with a remaining time, where the remaining time is less than the time threshold.

[0096]

[0106] In some aspects, the delayed status report is based at least in part on the amount of data reported in a previous delayed status report. In some aspects, the delayed status report is based at least in part on the status of a timer. In some aspects, alone or in combination with one or more of the first through ninth aspects, a timer is stopped at least in part based on the transmission of the delayed status report.

[0097]

[0107] In some aspects, the deferred status report is based at least in part on a configured periodicity. In some aspects, the configured periodicity is associated with a reporting entity. In some aspects, the deferred status report is based at least in part on the occurrence of a mobility event. In some aspects, the deferred status report is included in a MAC CE. In some aspects, the MAC CE includes at least one of a reporting entity bitmap of deferred status reports, a buffer status report table bitmap, an indicator of data having a remaining time within a configured range, an indicator of data having a remaining time below a threshold, an indicator that the MAC CE is for the reporting entity, an indicator of a buffer status report table, a sampling instance duration indicator, or a transmission time indicator.

[0098]

[0108] 6 illustrates example blocks of method 600, in some aspects method 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently than shown in FIG 6. Additionally or alternatively, two or more of the blocks of method 600 may be performed in parallel.

[0099]

[0109] 7 is a flowchart of an example method of wireless communication 700. Method 700 may be performed, for example, by a network node (e.g., network node 110).

[0100]

[0110] At 710, the network node may transmit information identifying a set of criteria for deferred status reporting. For example, the network node may transmit (e.g., using the communications manager 150 and / or the transmitting component 1004 shown in FIG. 10 ) the information identifying the set of criteria for deferred status reporting as described above. In some aspects, the deferred status reporting is associated with at least one of a data radio bearer, a logical channel, or a logical channel group. In some aspects, the network node may transmit signaling associated with configuring one or more parameters of the deferred status reporting. In some aspects, the one or more parameters include at least one of a data volume threshold parameter, a timer parameter, or one or more reporting thresholds.

[0101]

[0111] At 720, the network node may receive a deferral status report. For example, the network node (e.g., using the communications manager 150 and / or the receiving component 1002 shown in FIG. 10 ) may receive a deferral status report including an indicator of a data amount and a deferral status associated with the data amount based at least in part on a set of criteria being met, as described above. In some aspects, the deferral status is based at least in part on a delay deadline of a protocol data unit associated with the data amount or a packet delay budget associated with a quality of service flow, the quality of service flow including the protocol data unit. In some aspects, the deferral status is based at least in part on a time threshold for triggering generation of the deferral status report or for reporting the deferral status report. In some aspects, the deferral status report is based at least in part on whether a threshold data amount is associated with a remaining time, the remaining time being less than the time threshold.

[0102]

[0112] In some aspects, the delayed status report is based at least in part on the amount of data reported in a previous delayed status report. In some aspects, the delayed status report is based at least in part on the status of a timer. In some aspects, the timer is stopped at least in part based on the transmission of the delayed status report. In some aspects, the delayed status report is based at least in part on a configured periodicity.

[0103]

[0113] In some aspects, the configured periodicity is associated with a reporting entity. In some aspects, the delayed status report is based at least in part on the occurrence of a mobility event. In some aspects, the delayed status report is included in a MAC CE. In some aspects, the MAC CE includes at least one of a reporting entity bitmap of the delayed status report, a buffer status report table bitmap, an indicator of data having a remaining time within a configured range, an indicator of data having a remaining time below a threshold, an indicator that the MAC CE is for the reporting entity, an indicator of a buffer status report table, a sampling instance duration indicator, or a transmission time indicator. In some aspects, the delayed status report is associated with a first priority that is higher than a second priority of the buffer status report. In some aspects, the delayed status report is multiplexed onto physical uplink shared channel resources. In some aspects, the delayed status report is included in physical uplink shared channel resources requested via a scheduling request.

[0104]

[0114] At 730, in some aspects, a network node may communicate with the UE according to the content of the deferred status report. For example, the network node (e.g., using the communications manager 150, receiving component 1002, and / or transmitting component 1004 shown in FIG. 10) may communicate with the UE according to the content of the deferred status report. In some aspects, the network node may schedule resources for the UE and / or its associated XR device based at least in part on the content of the deferred status report.

[0105]

[0115] 7 illustrates example blocks of method 700, in some aspects method 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently than those shown in FIGURE 7. Additionally or alternatively, two or more of the blocks of method 700 may be performed in parallel.

[0106]

[0116] 8 is a diagram of an example apparatus 800 for wireless communication in accordance with the present disclosure. The apparatus 800 may be a UE, or a UE may include the apparatus 800. In some aspects, the apparatus 800 includes a receiving component 802 and a transmitting component 804, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 800 may communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using the receiving component 802 and the transmitting component 804. As further shown, the apparatus 800 may include a communications manager 140. The communications manager 140 may include one or more of a determining component 808 or a report generating component 810, among other examples.

[0107]

[0117] In some aspects, the apparatus 800 may be configured to perform one or more operations described herein, such as one or more operations described with respect to FIG. 5A and FIG. 5B. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as the method 600 of FIG. 6. In some aspects, the apparatus 800 and / or one or more components illustrated in FIG. 8 may include one or more components of a UE described with respect to FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 8 may be implemented within one or more components described with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be realized at least in part as software stored in memory. For example, a component (or a portion of a component) may be realized as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0108]

[0118] The receiving component 802 may receive communications from the device 806, such as reference signals, control information, data communications, or a combination thereof. The receiving component 802 may provide the received communications to one or more other components of the device 800. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and provide the processed signals to one or more other components of the device 800. In some aspects, the receiving component 802 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 a UE as described in connection with FIG.

[0109]

[0119] The transmitting component 804 may transmit a communication, such as a reference signal, control information, a data communication, or a combination thereof, to the device 806. In some aspects, one or more other components of the device 800 may generate a communication and provide the generated communication to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and transmit the processed signal to the device 806. In some aspects, the transmitting component 804 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 a UE described in connection with FIG. 2. In some aspects, the transmitting component 804 may be collocated with the receiving component 802 within a transceiver.

[0110]

[0120] The receiving component 802 may receive information identifying a set of criteria for a deferred status report. The transmitting component 804 may transmit a deferred status report including an indicator of the amount of data and a deferred status associated with the amount of data based at least in part on the set of criteria being met.

[0111]

[0121] The determining component 808 may determine that a set of criteria for a deferred status report is met. The report generating component 810 may generate a deferred status report based at least in part on determining that the set of criteria for a deferred status report is met. The receiving component 802 may receive signaling associated with configuring one or more parameters of a deferred status report.

[0112]

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

[0113]

[0123] 9 illustrates an example hardware implementation 900 for an apparatus 905 employing a processing system 910 in accordance with the present disclosure. The apparatus 905 may be a UE.

[0114]

[0124] Processing system 910 may be implemented with a bus architecture, represented generally by bus 915. Bus 915 may include any number of interconnected buses and bridges, depending on the particular application and overall design constraints of processing system 910. Bus 915 links together various circuits, including processor 920, the illustrated components, and one or more processors and / or hardware components, represented by computer-readable medium / memory 925. Bus 915 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0115]

[0125] The processing system 910 may be coupled to a transceiver 930. The transceiver 930 is coupled to one or more antennas 935. The transceiver 930 provides a means for communicating with various other devices over a transmission medium. The transceiver 930 receives signals from the one or more antennas 935, extracts information from the received signals, and provides the extracted information to the processing system 910, specifically the receiving component 802. In addition, the transceiver 930 receives information from the processing system 910, specifically the transmitting component 804, and generates signals to be applied to the one or more antennas 935 based at least in part on the received information.

[0116]

[0126] The processing system 910 includes a processor 920 coupled to a computer-readable medium / memory 925. The processor 920 is responsible for overall processing, including the execution of software stored on the computer-readable medium / memory 925. The software, when executed by the processor 920, causes the processing system 910 to perform various functions described herein for any particular apparatus. The computer-readable medium / memory 925 may also be used to store data that is manipulated by the processor 920 when executing the software. The processing system further includes at least one of the illustrated components. A component may be a software module running on the processor 920 and residing / stored on the computer-readable medium / memory 925, one or more hardware modules coupled to the processor 920, or some combination thereof.

[0117]

[0127] In some aspects, processing system 910 may be a component of UE 120 and may include memory 282 and / or at least one of TX MIMO processor 266, receive (RX) processor 258, and / or controller / processor 280. In some aspects, apparatus 905 for wireless communication includes means for receiving information identifying a set of criteria for a deferred status report and / or means for transmitting a deferred status report including an indicator of the amount of data and a deferred status associated with the amount of data based at least in part on the set of criteria being met. The aforementioned means may be one or more of the aforementioned components of apparatus 800 and / or processing system 910 of apparatus 905 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, processing system 910 may include TX MIMO processor 266, RX processor 258, and / or controller / processor 280. In one configuration, the aforementioned means may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations recited herein.

[0118]

[0128] Figure 9 is provided as an example. Other implementations may differ from those described in connection with Figure 9.

[0119]

[0129] 10 is a diagram of an example apparatus 1000 for wireless communication in accordance with the present disclosure. The apparatus 1000 may be a network node, or a network node may include the apparatus 1000. In some aspects, the apparatus 1000 includes a receiving component 1002 and a transmitting component 1004, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using the receiving component 1002 and the transmitting component 1004. As further shown, the apparatus 1000 may include a communications manager 150. The communications manager 150 may include, among other examples, a determining component 1008.

[0120]

[0130] In some aspects, apparatus 1000 may be configured to perform one or more operations described herein, such as one or more operations described with respect to FIG. 5A and FIG. 5B. Additionally or alternatively, apparatus 1000 may be configured to perform one or more processes described herein, such as method 700 of FIG. 7. In some aspects, apparatus 1000 and / or one or more components illustrated in FIG. 10 may include one or more components of a network node described with respect to FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 10 may be implemented within one or more components described with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be realized at least in part as software stored in memory. For example, a component (or a portion of a component) may be realized as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0121]

[0131] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of a network node described in connection with FIG.

[0122]

[0132] The transmitting component 1004 may transmit a communication, such as a reference signal, control information, a data communication, or a combination thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate a communication and provide the generated communication to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and transmit the processed signal to the device 1006. In some aspects, the transmitting component 1004 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 network node described in connection with FIG. 2 . In some aspects, the transmitting component 1004 may be collocated with the receiving component 1002 within a transceiver.

[0123]

[0133] The transmitting component 1004 may transmit information identifying a set of criteria for a deferred status report. The receiving component 1002 may receive a deferred status report including an indicator of the amount of data and a deferred status associated with the amount of data based at least in part on the set of criteria being met. The transmitting component 1004 may transmit signaling associated with configuring one or more parameters of the deferred status report. The determining component 1008 may determine the set of criteria for a deferred status report.

[0124]

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

[0125]

[0135] 11 illustrates an example hardware implementation 1100 for an apparatus 1105 employing a processing system 1110 in accordance with the present disclosure. The apparatus 1105 may be a network node.

[0126]

[0136] Processing system 1110 may be implemented with a bus architecture, represented generally by bus 1115. Bus 1115 may include any number of interconnected buses and bridges, depending on the particular application and overall design constraints of processing system 1110. Bus 1115 links together various circuits, including processor 1120, the illustrated components, and one or more processors and / or hardware components, represented by computer-readable medium / memory 1125. Bus 1115 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0127]

[0137] The processing system 1110 may be coupled to a transceiver 1130. The transceiver 1130 is coupled to one or more antennas 1135. The transceiver 1130 provides a means for communicating with various other devices over a transmission medium. The transceiver 1130 receives signals from the one or more antennas 1135, extracts information from the received signals, and provides the extracted information to the processing system 1110, specifically the receiving component 1002. Additionally, the transceiver 1130 receives information from the processing system 1110, specifically the transmitting component 1004, and generates signals to be applied to the one or more antennas 1135 based at least in part on the received information.

[0128]

[0138] The processing system 1110 includes a processor 1120 coupled to a computer-readable medium / memory 1125. The processor 1120 is responsible for overall processing, including the execution of software stored on the computer-readable medium / memory 1125. The software, when executed by the processor 1120, causes the processing system 1110 to perform various functions described herein for any particular apparatus. The computer-readable medium / memory 1125 may also be used to store data that is manipulated by the processor 1120 when executing the software. The processing system further includes at least one of the illustrated components. A component may be a software module running on the processor 1120 and residing / stored on the computer-readable medium / memory 1125, one or more hardware modules coupled to the processor 1120, or some combination thereof.

[0129]

[0139] In some aspects, the processing system 1110 may be a component of the network node 110 and may include the memory 242 and / or at least one of the TX MIMO processor 230, the RX processor 238, and / or the controller / processor 240. In some aspects, the apparatus 1105 for wireless communication includes means for transmitting information identifying a set of criteria for a deferred status report, and / or means for receiving a deferred status report including an indicator of the amount of data and a deferred status associated with the amount of data based at least in part on the set of criteria being met. The aforementioned means may be one or more of the aforementioned components of the apparatus 1000 and / or the processing system 1110 of the apparatus 1105 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1110 may include the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240. In one configuration, the aforementioned means may be a TX MIMO processor 230, a receive processor 238, and / or a controller / processor 240 configured to perform the functions and / or operations recited herein.

[0130]

[0140] Figure 11 is provided as an example. Other embodiments may differ from those described in connection with Figure 11.

[0131]

[0141] The following provides a summary of several aspects of the disclosure.

[0132]

[0142] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method including: receiving information identifying a set of criteria for a deferred status report; and transmitting a deferred status report including an indicator of a data amount and a deferred status associated with the data amount based at least in part on the set of criteria being met.

[0133]

[0143] Aspect 2: The method of aspect 1, further comprising: determining that a set of criteria for a delayed status report is met; and generating a delayed status report based at least in part on determining that the set of criteria for a delayed status report is met.

[0134]

[0144] Aspect 3: The method of any one of aspects 1 to 2, wherein the deferred status report is associated with at least one of a data radio bearer, a logical channel, or a logical channel group.

[0135]

[0145] Aspect 4: A method according to any one of aspects 1 to 3, wherein the delay status is based at least in part on a delay deadline of a protocol data unit associated with a data amount or a packet delay budget associated with a quality of service flow, and the quality of service flow includes the protocol data unit.

[0136]

[0146] Aspect 5: The method of any of aspects 1-4, wherein the deferred status is based at least in part on a time threshold for triggering generation of or reporting the deferred status report.

[0137]

[0147] Aspect 6: The method of any of aspects 1 to 5, further comprising receiving signaling associated with configuring one or more parameters of a deferred status report.

[0138]

[0148] Aspect 7: The method of aspect 6, wherein the one or more parameters include at least one of a data volume threshold parameter, a timer parameter, or one or more reporting thresholds.

[0139]

[0149] Aspect 8: The method of any of aspects 1 to 7, wherein the delayed status reporting is based at least in part on whether a threshold amount of data is associated with a remaining time, and the remaining time is less than the time threshold.

[0140]

[0150] Aspect 9: The method of any of aspects 1-8, wherein the delayed status report is based at least in part on the amount of data reported in a previous delayed status report.

[0141]

[0151] Aspect 10: The method of any of aspects 1 to 9, wherein the delayed status reporting is based at least in part on the status of a timer.

[0142]

[0152] Aspect 11: The method of aspect 10, wherein the timer is stopped based at least in part on transmitting the delayed status report.

[0143]

[0153] Aspect 12: The method of any of aspects 1-11, wherein the delayed status reporting is based at least in part on a configured periodicity.

[0144]

[0154] Aspect 13: The method of aspect 12, wherein the configured periodicity is associated with a reporting entity.

[0145]

[0155] Aspect 14: The method of any of aspects 1-13, wherein the deferred status reporting is based at least in part on the occurrence of a mobility event.

[0146]

[0156] Aspect 15: The method of any one of aspects 1 to 14, wherein the deferred status report is included in a medium access control (MAC) control element (CE).

[0147]

[0157] Aspect 16: The method of aspect 15, wherein the MAC CE includes at least one of a reporting entity bitmap for delayed status reports, a buffer status report table bitmap, an indicator of data having remaining time within a configured range, an indicator of data having remaining time below a threshold, an indicator that the MAC CE is for a reporting entity, an indicator of a buffer status report table, a sampling instance duration indicator, or a transmission time indicator.

[0148]

[0158] Aspect 17: The method of any of aspects 1 to 16, wherein the delayed status report is associated with a first priority that is higher than the second priority of the buffer status report.

[0149]

[0159] Example 18: The method of any one of Examples 1 to 17, wherein the delayed status report is multiplexed onto physical uplink shared channel resources.

[0150]

[0160] Example 19: The method of any one of examples 1 to 18, wherein the delayed status report is included in the physical uplink shared channel resources requested via the scheduling request.

[0151]

[0161] Aspect 20: A method of wireless communications performed by a network node, the method including: transmitting information identifying a set of criteria for a deferred status report; and receiving a deferred status report including an indicator of a data volume and a deferred status associated with the data volume based at least in part on the set of criteria being met.

[0152]

[0162] Aspect 21: The method of aspect 20, wherein the deferred status report is associated with at least one of a data radio bearer, a logical channel, or a logical channel group.

[0153]

[0163] Aspect 22: The method of any of aspects 20 to 21, wherein the delay status is based at least in part on a delay deadline of a protocol data unit associated with a data amount or a packet delay budget associated with a quality of service flow, and the quality of service flow includes the protocol data unit.

[0154]

[0164] Aspect 23: The method of any of aspects 20-22, wherein the deferred status is based at least in part on a time threshold for triggering generation of or reporting the deferred status report.

[0155]

[0165] Aspect 24: The method of any of aspects 20 to 23, further comprising transmitting signaling associated with configuring one or more parameters of the deferred status report.

[0156]

[0166] Aspect 25: The method of aspect 24, wherein the one or more parameters include at least one of a data volume threshold parameter, a timer parameter, or one or more reporting thresholds.

[0157]

[0167] Aspect 26: The method of any of aspects 20 to 25, wherein the delayed status reporting is based at least in part on whether a threshold amount of data is associated with a remaining time, and the remaining time is less than the time threshold.

[0158]

[0168] Aspect 27: The method of any of aspects 20 to 26, wherein the delayed status report is based at least in part on the amount of data reported in a previous delayed status report.

[0159]

[0169] Aspect 28: The method of any of aspects 20 to 27, wherein the delayed status reporting is based at least in part on the status of a timer.

[0160]

[0170] Aspect 29: The method of aspect 28, wherein the timer is stopped based at least in part on transmitting the delayed status report.

[0161]

[0171] Aspect 30: The method of any of aspects 20 to 29, wherein the delayed status reporting is based at least in part on a configured periodicity.

[0162]

[0172] Aspect 31: The method of aspect 30, wherein the configured periodicity is associated with a reporting entity.

[0163]

[0173] Aspect 32: The method of any of aspects 20 to 31, wherein the deferred status reporting is based at least in part on the occurrence of a mobility event.

[0164]

[0174] Aspect 33: The method of any one of aspects 20 to 32, wherein the deferred status report is included in a medium access control (MAC) control element (CE).

[0165]

[0175] Aspect 34: The method of aspect 33, wherein the MAC CE includes at least one of a reporting entity bitmap for delayed status reports, a buffer status report table bitmap, an indicator of data having remaining time within a configured range, an indicator of data having remaining time below a threshold, an indicator that the MAC CE is for a reporting entity, an indicator of a buffer status report table, a sampling instance duration indicator, or a transmission time indicator.

[0166]

[0176] Aspect 35: The method of any of aspects 20 to 34, wherein the delayed status report is associated with a first priority that is higher than the second priority of the buffer status report.

[0167]

[0177] Example 36: The method of any of Examples 20 to 35, wherein the delayed status report is multiplexed onto physical uplink shared channel resources.

[0168]

[0178]

[0071] Aspect 37: The method of any one of aspects 20 to 36, wherein the delayed status report is included in the physical uplink shared channel resources requested via the scheduling request.

[0169]

[0179] Aspect 38: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, wherein the instructions executable by the processor cause the apparatus to perform one or more of the methods of aspects 1 to 37.

[0170]

[0180] Aspect 39: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the one or more processors are configured to perform one or more of the methods of aspects 1 to 37.

[0171]

[0181] Aspect 40: An apparatus for wireless communication, comprising at least one means for performing one or more of the methods of aspects 1-37.

[0172]

[0182] Aspect 41: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform one or more of the methods of aspects 1 to 37.

[0173]

[0183] Aspect 42: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more methods of aspects 1 to 37.

[0174]

[0184] The above disclosure provides illustration and description, but is not intended to be exhaustive or to limit the embodiments to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the embodiments.

[0175]

[0185] As used herein, the term "component" is intended to be broadly construed as hardware and / or combinations of hardware and software. "Software" should be broadly construed to mean, among other examples, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, 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 the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, with the understanding that those skilled in the art will be able to design software and hardware to implement the systems and / or methods based at least in part on the description herein.

[0176]

[0186] As used herein, "meeting a threshold" can 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, etc., depending on the context.

[0177]

[0187] Although particular combinations of features are recited in the claims and / or disclosed herein, those 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 herein. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, phrases referring to "at least one of" a list of items refer to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other permutation of a, b, and c).

[0178]

[0188] No element, act, or instruction used herein should be construed as essential or required unless expressly 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." Furthermore, as used herein, the article "the" is intended to include one or more items referred to in connection with the article "the" and may be used interchangeably with "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, terms such as "has," "have," and "having" are intended to be open-ended terms that do not limit the elements they modify (e.g., an element that "has" A may also have B). Furthermore, the phrase "based on" is intended to mean "based at least in part on," unless expressly stated otherwise. As used herein, the term "or" is also intended to be inclusive when used in a series, and may be used interchangeably with "and / or," except where expressly stated otherwise (e.g., when used in combination with "either" or "only one of").

Claims

1. 1. A user equipment (UE) for wireless communications, comprising: one or more memories; one or more processors coupled to the one or more memories, wherein the one or more processors: receiving information identifying a set of criteria for delay status reporting; The UE is configured to transmit, based at least in part on the set of criteria being met, a deferral status report including an indicator of an amount of data and a deferral status associated with the amount of data.

2. the one or more processors: determining that the set of criteria for a delayed status report is met; The UE of claim 1 , further configured to generate the deferred status report based at least in part on determining that the set of criteria for a deferred status report is met.

3. The delayed status report: Data radio bearer, logical channel, or The UE of claim 1 , associated with at least one of the logical channel groups.

4. 2. The UE of claim 1, wherein the delay status is based at least in part on a delay deadline of a protocol data unit associated with the amount of data or a packet delay budget associated with a quality of service flow, the quality of service flow including the protocol data unit.

5. The UE of claim 1 , wherein the deferred status is based at least in part on a time threshold for triggering generation of the deferred status report or for reporting the deferred status report.

6. the one or more processors: The UE of claim 1 , further configured to receive signaling associated with configuring one or more parameters of the deferred status report.

7. The one or more parameters are: A data volume threshold parameter, timer parameters, or The UE of claim 6 , comprising at least one of one or more reporting thresholds.

8. 10. The UE of claim 1, wherein the deferred status report is based at least in part on whether a threshold amount of data is associated with a remaining time, the remaining time being less than a time threshold.

9. The UE of claim 1 , wherein the delayed status report is based at least in part on an amount of data reported in a previous delayed status report.

10. The UE of claim 1 , wherein the delayed status report is based at least in part on the status of a timer.

11. The UE of claim 10 , wherein the timer is stopped based at least in part on transmitting the delayed status report.

12. The UE of claim 1 , wherein the delayed status reporting is based at least in part on a configured periodicity.

13. The UE of claim 12 , wherein the configured periodicity is associated with a reporting entity.

14. The UE of claim 1 , wherein the deferred status reporting is based at least in part on the occurrence of a mobility event.

15. The UE of claim 1 , wherein the deferred status report is included in a medium access control (MAC) control element (CE).

16. The MAC CE is reporting entity bitmap for delayed status reporting; Buffer Status Reporting Table Bitmap, an indicator of data having remaining time within a configured range; an indicator of data having time remaining below a threshold; an indicator that the MAC CE is for a reporting entity; Buffer status reporting table indicators, a sampling instance duration indicator, or 16. The UE of claim 15, comprising at least one of a transmission time indicator.

17. The UE of claim 1 , wherein the delayed status report is associated with a first priority that is higher than a second priority of a buffer status report.

18. The UE of claim 1 , wherein the delayed status report is multiplexed onto physical uplink shared channel resources.

19. The UE of claim 1 , wherein the delayed status report is included in physical uplink shared channel resources requested via a scheduling request.

20. A network node for wireless communication, comprising: one or more memories; one or more processors coupled to the one or more memories, wherein the one or more processors: transmitting information identifying a set of criteria for delay status reporting; The network node is configured to receive, based at least in part on the set of criteria being met, a deferral status report including an indicator of a data amount and a deferral status associated with the data amount.

21. The delayed status report: Data radio bearer, logical channel, or 21. A network node according to claim 20, associated with at least one of the logical channel groups.

22. 21. The network node of claim 20, wherein the delay status is based at least in part on a delay deadline of a protocol data unit associated with the amount of data or a packet delay budget associated with a quality of service flow, the quality of service flow including the protocol data unit.

23. 21. The network node of claim 20, wherein the deferred status is based at least in part on a time threshold for triggering generation of the deferred status report or for reporting the deferred status report.

24. the one or more processors:

21. The network node of claim 20, further configured to transmit signaling associated with configuring one or more parameters of the deferred status report.

25. The one or more parameters are: A data volume threshold parameter, timer parameters, or 25. The network node of claim 24, comprising at least one of one or more reporting thresholds.

26. 21. The network node of claim 20, wherein the deferred status reporting is based at least in part on whether a threshold amount of data is associated with a remaining time, the remaining time being less than a time threshold.

27. 21. The network node of claim 20, wherein the delayed status report is based at least in part on an amount of data reported in a previous delayed status report.

28. 21. The network node of claim 20, wherein the delayed status reporting is based at least in part on the status of a timer.

29. 1. A method of wireless communication performed by a user equipment (UE), comprising: receiving information identifying a set of criteria for delay status reporting; and transmitting a deferral status report, based at least in part on the set of criteria being met, the deferral status report including an indicator of an amount of data and a deferral status associated with the amount of data.

30. 1. A method of wireless communication performed by a network node, comprising: transmitting information identifying a set of criteria for delay status reporting; receiving a deferral status report, based at least in part on the set of criteria being met, the deferral status report including an indicator of an amount of data and a deferral status associated with the amount of data.

Images