BSR Trigger ENHANCEMENT

Abstract

A method and related apparatus for wireless communication at a user equipment (UE) are provided. In the method, the UE transmits a buffer status report (BSR) to a network entity in response to a BSR trigger condition satisfying from a plurality of BSR trigger conditions. Each of the plurality of BSR trigger conditions is associated with a set of protocol data units (PDUs) that includes a set of PDUs. The UE also communicates with the network entity based on the BSR. The method provides a plurality of BSR trigger conditions based on various scenarios in the data transmission. This allows BSR information to be more easily available to the network and enables efficient resource allocation.

Description

[0001] This application claims the benefit of and priority to U.S. provisional application entitled “BSR TRIGGER ENHANCEMENTS” and serial number 63 / 479,964, filed on January 13, 2023, and U.S. non-provisional patent application serial number 18 / 405705, filed on January 5, 2024, entitled “BSR-TRIGGERENHANCEMENTS,” all of which are expressly incorporated herein by reference. Technical Field

[0002] The present disclosure relates generally to communication systems and, more particularly, to buffer status report (BSR) triggering enhancements for wireless communications. Background Art

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution released by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

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

[0006] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to: send a buffer status report (BSR) to a network entity in response to satisfying a BSR trigger condition from a plurality of BSR trigger conditions, wherein each of the plurality of BSR trigger conditions is associated with a set of protocol data units (PDUs); and communicate with the network entity based on the BSR.

[0007] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to: receive a BSR from a UE, wherein the BSR is received in response to satisfying one of a plurality of BSR triggering conditions, wherein each of the plurality of BSR triggering conditions is associated with a PDU set including a group of PDUs; and communicate with the UE based on the BSR.

[0008] To accomplish the foregoing and related objectives, one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of but some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is a schematic diagram illustrating an example of a wireless communication system and an access network.

[0010] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0011] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0012] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0013] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0014] Figure 3 is a schematic diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0015] Figure 4A and 4B is a diagram illustrating an example data structure of a buffer status report (BSR).

[0016] Figure 5 is a diagram illustrating an example mapping of Quality of Service (QoS) flows across bearers.

[0017] Figure 6 is a diagram illustrating example mappings between different flows, radio bearers (DRBs), service data adaptation protocols (SDAPs), and protocol data unit (PDU) sessions.

[0018] Figure 7 is a diagram illustrating an example of an extended reality (XR) business flow.

[0019] Figure 8 is a call flow diagram illustrating a method of wireless communication in accordance with various aspects of the present disclosure.

[0020] Figure 9 is a flow chart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure.

[0021] Figure 10 is a flow chart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure.

[0022] Figure 11 is a flow chart illustrating a method of wireless communication at a network entity according to various aspects of the present disclosure.

[0023] Figure 12 is a flow chart illustrating a method of wireless communication at a network entity according to various aspects of the present disclosure.

[0024] Figure 13 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus and / or UE.

[0025] Figure 14 is a schematic diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0026] In wireless communication systems (such as Long Term Evolution (LTE) and 5G systems), a buffer status report (BSR) provides the network with information about data waiting to be sent from a user equipment (UE). The UE sends a BSR indicating the UE's buffer status, which can facilitate the network to more efficiently allocate resources for wireless communication with the UE. BSR transmission can be triggered based on the occurrence of one or more BSR triggering conditions (or BSR triggers) (such as the expiration of a timer). The BSR trigger can be further associated with the type of BSR, for example, whether the BSR is a short, long, or truncated BSR. Various aspects provided herein further provide BSR triggering conditions associated with the cause of the BSR triggering. In current BSR mechanisms, a BSR triggering condition set can correspond to a medium access control (MAC) entity, and a single condition set can be applied to each of the logical channel group (LCG), radio bearer (DRB), protocol data unit (PDU) session, and application flow of the MAC entity. The example aspects presented herein provide the ability to enable various triggers associated with the PDU set level (e.g., a set of PDUs associated with an application frame (e.g., a video frame)) rather than the PDU level.

[0027] Various aspects relate generally to wireless communications and, more particularly, to BSR triggering enhancements. Some aspects relate more particularly to configuring multiple BSR triggering conditions. In some examples, a UE may send a buffer status report (BSR) to a network entity in response to satisfying a BSR triggering condition from multiple BSR triggering conditions. Each of the multiple BSR triggering conditions may be associated with a PDU set including a group of PDUs. The UE may further communicate with the network entity based on the BSR.

[0028] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by enabling a UE to use multiple BSR triggering conditions associated with data transmission, the described techniques can be used to make BSR information more readily available to the network and enable more efficient resource allocation. Thus, it improves the efficiency of wireless communications.

[0029] The detailed description set forth below in conjunction with the accompanying drawings describes various configurations and does not represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a comprehensive understanding of the various concepts. However, these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0030] Several aspects of telecommunications systems are presented with reference to various apparatuses and methods. These apparatuses and methods are described below in the detailed description and illustrated in the accompanying drawings by means of various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0031] For example, an element, or any part of an element, or any combination of elements, can be implemented as a "processing system" including one or more processors. When multiple processors are implemented, multiple processors can perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, or any combination thereof.

[0032] Thus, in one or more example aspects, implementations, and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or codes on a computer-readable medium or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. A storage medium may be any available medium that can be accessed by a computer. For example, such a computer-readable medium may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0033] Although various aspects, implementations and / or use cases are described in this application by illustrating some examples, additional or different aspects, implementations and / or use cases may occur in many different arrangements and scenarios. The various aspects, implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, various aspects, implementations and / or use cases can be implemented via integrated chip implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchase devices, medical devices, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, there may be a variety of applicable scopes for the examples described. Various aspects, implementations and / or use cases can vary in the range of chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems of one or more technologies incorporated herein. In some actual settings, the devices incorporated with the various aspects and features described may also include additional components and features for the implementation and enforcement of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / accumulators, etc.). The techniques described herein can be practiced in various devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0034] The deployment of a communication system (e.g., a 5G NR system) can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, a network node, a network entity, a mobile element of a network, a radio access network (RAN) node, a core network node, a network element, or a network device (such as a base station (BS) or one or more units (or one or more components) that perform base station functions) can be implemented in a converged or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP), or a cell) can be implemented as a converged base station (also called a standalone BS or a monolithic BS) or a decomposed base station.

[0035] A converged base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station can be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0036] Base station operation or network design can take into account the aggregated nature of base station functions. For example, a disaggregated base station can be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as the O-RAN Alliance initiative) or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation can include allocating functions across two or more units at various physical locations, as well as virtually allocating functions for at least one unit, which can achieve flexibility in network design. Each unit of the disaggregated base station or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0037] Figure 1 1 is a schematic diagram 100 illustrating an example of a wireless communication system and access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110, which may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station elements, such as a near real-time (near-RT) RAN intelligent controller (RIC) 125 via an E2 link, a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CUs 110 may communicate with one or more DUs 130 via corresponding mid-haul links, such as an F1 interface. The DUs 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RUs 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served by multiple RUs 140 simultaneously.

[0038] Each of the units (i.e., CU 110, DU 130, RU 140) and the near-RT RIC 125, non-RT RIC 115, and SMO framework 105 may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other units. In addition, these units may include a wireless interface (which may include a receiver, transmitter, or transceiver (such as an RF transceiver)) that is configured to receive signals on a wireless transmission medium or to send signals to one or more of the other units, or to perform both operations.

[0039] In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to transmit signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as the E1 interface when implemented in an O-RAN configuration). The CU 110 may be implemented to communicate with the DU 130 as needed for network control and signaling.

[0040] The DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, depending at least in part on a functional split (such as that defined by 3GPP), the DU 130 may host one or more of the following: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.). In some aspects, the DU 130 may also host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 130 or control functions hosted by the CU 110.

[0041] Lower layer functions may be implemented by one or more RUs 140. In some deployments, based at least in part on a functional split (such as a lower layer functional split), a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.), or both. In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0042] The SMO framework 105 can be configured to support RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 190) to perform network element lifecycle management (e.g., to instantiate virtualized network elements) via a cloud computing platform interface (e.g., the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, the SMO framework 105 can communicate with hardware aspects of the 4G RAN (e.g., Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, the SMO framework 105 can communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0043] The non-RT RIC 115 may be configured to include logic that implements non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows (including model training and updating), or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (e.g., via an A1 interface). The near-RT RIC 125 may be configured to include logic that implements near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface connecting one or more CUs 110, one or more DUs 130, or both, and an O-eNB with the near-RT RIC 125 (e.g., via an E2 interface).

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

[0045] At least one of the CU 110, DU 130, and RU 140 may be referred to as a base station 102. Thus, the base station 102 may include one or more of the CU 110, DU 130, and RU 140 (each component is indicated with a dashed line to indicate that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmissions from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmissions from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. Base station 102 / UE 104 may use spectrum of up to Y megahertz (MHz) (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier, allocated in carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0046] Certain UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be performed over various wireless D2D communication systems, such as, for example, Bluetooth (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi (Wi-Fi is a trademark of the Wi-Fi Alliance) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0047] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154 in, for example, a 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available before communicating.

[0048] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating frequency bands have been identified with the frequency range names FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. Similar naming issues sometimes arise with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz), which is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0050] In view of the above aspects, unless otherwise specifically stated, the term "sub-6 GHz" and the like (if used herein) may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, the term "millimeter wave" and the like (if used herein) may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0051] Base station 102 and UE 104 may each include multiple antennas (e.g., antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0052] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network entity, a network device, or some other suitable terminology. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a converged (monolithic) base station having a baseband unit (BBU) (including a CU and a DU) and a RU, or a disaggregated base station including one or more of a CU, a DU, and / or a RU. A collection of base stations that may include non-aggregated base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0053] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity processing, access authorization, and subscription management. The one or more location servers 168 are shown as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Positioning Center (MPC), etc. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Positioning the UE 104 may involve signal measurements, position estimation, and optional velocity calculation based on the measurements. Signal measurements may be performed by the UE 104 and / or the base station 102 serving the UE 104. The measured signals may be based on one or more of a satellite positioning system (SPS) (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS) 170, a non-terrestrial network (NTN), or other satellite positioning / location systems), an LTE signal, a wireless local area network (WLAN) signal, a Bluetooth signal, a terrestrial beacon system (TBS), sensor-based information (e.g., a pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, an NR signal (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0054] Examples of UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similar functional devices. Some UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access a network together and / or individually.

[0055] Reference again Figure 1 In certain aspects, the UE 104 may include a BSR triggering component 198. The BSR triggering component 198 may be configured to: send a BSR to a network entity in response to a BSR triggering condition from a plurality of BSR triggering conditions being satisfied, wherein each of the plurality of BSR triggering conditions is associated with a PDU set including a set of PDUs associated with a frame of an application; and communicate with the network entity based on the BSR. In certain aspects, the base station 102 may include a BSR triggering component 199. The BSR triggering component 199 may be configured to: receive a BSR from the UE in response to one of a plurality of BSR triggering conditions being satisfied, wherein each of the plurality of BSR triggering conditions is associated with a PDU set including a set of PDUs associated with a frame of an application; and communicate with the UE based on the BSR. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0056] Figure 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Figure 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. Figure 2Dis a diagram 280 showing an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), subframes within a subcarrier set are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), subframes within a subcarrier set are dedicated to both DL and UL). Figure 2A 、 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling) via the received slot format indicator (SFI). Note that the following description also applies to the 5G NR frame structure that is TDD.

[0057] Figures 2A-2D A frame structure is shown, and aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Depending on whether the cyclic prefix (CP) is normal or extended, each time slot may include 14 or 12 symbols. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbols (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe may be based on the CP and numerology. The digital scheme defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration may be proportional to 1 / SCS.

[0058]

[0059] Table 1: Digital scheme, SCS and CP

[0060] For normal CP (14 symbols / time slot), different digital schemes μ0 to 4 allow 1, 2, 4, 8 and 16 time slots per subframe respectively. For extended CP, digital scheme 2 allows 4 time slots per subframe. Therefore, for normal CP and digital scheme μ, there are 14 symbols / time slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is the digital scheme 0 to 4. Thus, digital scheme μ=0 has a subcarrier spacing of 15kHz, and digital scheme μ=4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example is provided for a normal CP with 14 symbols per slot and a digital scheme μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific numbering scheme and CP (normal or extended).

[0061] The resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)), which includes 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0062] As in Figure 2A As shown in , some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a specific configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0063] Figure 2BExamples of various DL channels within a subframe of a frame are shown. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 12 consecutive REs within one OFDM symbol of the RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH search spaces (e.g., common search space, UE-specific search space) during PDCCH monitoring opportunities on the CORESET for PDCCH candidates, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at larger and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the position of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as the system information block (SIB)), and paging messages.

[0064] like Figure 2C As shown in , some of the REs carry DM-RSs for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE may send DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of the subframe. The SRS may have a comb structure, and the UE may send the SRS in one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0065] Figure 2D An example of various UL channels within a subframe of a frame is shown. The PUCCH may be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI) such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0066] Figure 3 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with the following: broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with the following: header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with the following: transmission of upper layer packet data units, error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with the following: mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0067] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel state feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0068] At the UE 350, each receiver 354Rx receives a signal via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359 which implements layer 3 and layer 2 functionality.

[0069] The controller / processor 359 may be associated with at least one memory 360 that stores program codes and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0070] Similar to the functions described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides: RRC layer functions associated with: system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with: header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0071] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0072] The UL transmission is processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0073] The controller / processor 375 may be associated with at least one memory 376 that stores program codes and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0074] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Various aspects related to the BSR trigger component 198.

[0075] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 Various aspects related to the BSR trigger component 199.

[0076] A UE may have uplink data to send to a network. The UE may send a BSR from the UE to the network, for example, in a MAC-CE, with information regarding the amount of data in the UE's buffer waiting to be sent (e.g., transmitted) to the network. By sending the BSR to the network, the UE requests or notifies the network to provide an UL grant (e.g., allocate or grant transmission resources to the UE), via which the UE may send data to the network. Upon receiving the BSR from the UE, the network may allocate a corresponding amount of resources (e.g., scheduled transmission resources) in the UL grant for the UE to use for UL transmission, the amount of resources being based on the amount of data indicated by the BSR.

[0077] The BSR can have different data structures and transmission timings. For example, the BSR can be a long BSR or a short BSR, depending on its data structure. A short BSR can indicate the amount of data in the UE's buffer for a single LCG, while a long BSR can indicate the amount of data in the UE's buffer for multiple LCGs. Figure 4A FIG4 is a diagram 400 showing an example data structure of a short BSR. Figure 4A As shown in FIG, a short BSR may include an LCG ID 402 and a buffer size 404 for a single LCG. For example, the LCG ID 402 may be 2 bits and the buffer size 404 may include 6 bits. The buffer size 404 may indicate the amount of data for the LCG indicated by the LCG ID 402. Figure 4B FIG4 is a diagram 450 showing an example data structure of a long BSR. Figure 4B, a long BSR may include multiple buffer size fields, such as buffer size #1 452, buffer size #2 454, buffer size #3 456, and buffer size #4 458. For example, each of these buffer size fields may include 6 bits and indicate the amount of data for one LCG, and different buffer sizes may indicate the amount of data for different LCGs.

[0078] Based on the timing at which the BSR is sent to the network, the BSR may be an aperiodic BSR or a periodic BSR. The UE may send an aperiodic BSR, which may be referred to in some aspects as a regular BSR, in response to the arrival of new data in the UE's buffer and based on the new data having a higher priority than data already waiting in the UE's buffer. The UE may use a regular BSR to notify the network of changes in its buffer status, thereby allowing the network to update its resource allocation and scheduling decisions accordingly. On the other hand, the UE may also send a periodic BSR according to a preset period, for example, the period for BSR transmission may be configured by the network. Since the periodic BSR is sent regardless of a change in the buffer status, it may not necessarily indicate a change in the buffer status (e.g., the arrival of new data), as is the case with a regular BSR.

[0079] Figure 5 FIG. 5 is a diagram 500 illustrating an example mapping of QoS flows across bearers. Figure 5 As shown in , various QoS flows can be mapped based on different QoS requirements across radio bearers. For example, in the downlink (DL), incoming data packets 520 can be classified by the user plane function (UPF) 530 based on packet detection rules (PDR) 532, which is a set of criteria or algorithms for identifying the start and end of data packets (e.g., data packet 520) sent on the wireless network. The access network (AN) 540 can bind QoS flows (e.g., QoS flow 522) to AN resources (e.g., AN resources 542). The AN resources can include, for example, data radio bearers. Similarly, in the uplink (UL), the UE 502 can classify UL packets (e.g., packet 510) based on QoS rules 504 and bind QoS flows (e.g., QoS flows 512, 514) to AN resources (e.g., AN resources 542). In some examples, differentiating between bearers that are part of a single slice (e.g., a segment of a wireless network that operates independently to meet specific service or performance requirements) or different slices can facilitate support for end-to-end (E2E) resource management to meet service level agreements (SLAs).

[0080] Figure 6FIG6 is a diagram 600 showing an example mapping between different flows, DRBs, SDAPs, and PDU sessions. Figure 6 , different PDU sessions, such as an Internet PDU session 602, a streaming video PDU session 604, or an IP Multimedia Subsystem (IMS) PDU session 606, may have different QoS requirements. Each PDU session may have its own service data flow (SDF). For example, the Internet PDU session 602 may have four SDFs (e.g., SDFs 612, 614, 616, and 618). One or more SDFs may be mapped to the same QoS flow. For example, SDFs 614 and 616 may be mapped to QoS flow 2 622, and SDF 618 may be mapped to QoS flow 3 624. QoS flows may be mapped to data radio bearers (DRBs), and one or more QoS flows may be mapped to one DRB. For example, Figure 6 As shown in FIG, QoS flow 1 620 may be mapped to DRB 1 630, and QoS flow 2 622 and QoS flow 3 624 may be mapped to the same DRB (DRB 2 632). Figure 5 As shown in , QoS flows 512 and 514 may be mapped to AN resources 542 (which may be DRBs). Figure 6 As shown in , multiple DRBs (e.g., a default DRB and an optional dedicated DRB) can be mapped on the same PDU session. For example, DRB 1 630 and DRB 2 632 can be mapped to the Internet PDU session 602. One SDAP entity can correspond to one PDU session. For example, one SDAP entity (e.g., SDAP and Service Flow Template (SDAP+TFT) 652) can correspond to the Internet PDU session 602, another SDAP entity (e.g., SDAP+TFT654) can correspond to the streaming video PDU session 604, and a third SDAP entity (e.g., SDAP+TFT656) can correspond to the IMS PDU session 606. Due to the various mapping relationships between DRBs, QoS flows, SDAP entities, and PDU sessions, it is beneficial to have more refined control and management of data transmission (e.g., triggered by a BSR on a single DRB).

[0081] Wireless communication systems can support various types of services. In addition to other types of services, wireless communication systems can support XR services. XR traffic can refer to wireless communications used for technologies such as virtual reality (VR), mixed reality (MR), and / or augmented reality (AR). VR can refer to technologies that immerse users in simulated experiences similar to or different from the real world. Users can interact with VR systems through VR headsets or multi-projection environments that generate realistic images, sounds, and other sensations that simulate the user's physical presence in a virtual environment. MR can refer to technologies that blend aspects of virtual and real environments. AR can refer to technologies that augment objects residing in the real world via computer-generated sensory information, sometimes across multiple sensory modalities such as vision, hearing, touch, somatosensory, and / or smell. AR systems can include a combination of real and virtual worlds, real-time interaction, and precise three-dimensional registration of virtual and real objects. In one example, an AR system can overlay sensory information (e.g., images) onto a natural environment and / or mask real objects from the natural environment. XR services can include video data and / or audio data. The XR service may be sent by the base station and received by the UE, or the XR service may be sent by the UE and received by the base station.

[0082] XR traffic may arrive in the form of periodic traffic bursts ("XR traffic bursts"). XR traffic bursts may vary in the number of packets per burst and / or the size of each packet in the burst. Figure 7 Schematic diagram 700 in FIG. 7 shows a first XR stream 702 including a first XR traffic burst 704 and a second XR traffic burst 706. As shown in schematic diagram 700, the traffic bursts can include different numbers of packets. For example, the first XR traffic burst 704 is shown as having three packets (represented as rectangles in schematic diagram 700), and the second XR traffic burst 706 is shown as having two packets. Furthermore, as shown in schematic diagram 700, the three packets in the first XR traffic burst 704 and the two packets in the second XR traffic burst 706 can vary in size. That is, the packets within the first XR traffic burst 704 and the second XR traffic burst 706 can include different amounts of data.

[0083] XR traffic bursts may arrive with non-integer periods (i.e., with non-integer cycles). The period may be different from an integer number of symbols, time slots, etc. In one example, for 60 frames per second (FPS) video data, XR traffic bursts may arrive with a period of 1 / 60 = 16.67 ms. In another example, for 120 FPS video data, XR traffic bursts may arrive with a period of 1 / 120 = 8.33 ms.

[0084] The arrival time of XR traffic may vary. For example, an XR traffic burst may arrive and be available for transmission at a time that is earlier or later than the time when the UE (or base station) expects the XR traffic burst. The variability of packet arrival relative to a period (e.g., a 16.76ms period, an 8.33ms period, etc.) may be referred to as "jitter." In one example, the jitter of XR traffic may range from -4ms (arriving earlier than expected) to +4ms (arriving later than expected). For example, referring to the first XR stream 702, the UE may expect the first packet of the first XR traffic burst 704 to arrive at time t0, but the second packet of the first XR traffic burst 704 arrives at time t1.

[0085] XR traffic may include multiple streams that arrive at the UE (or base station) simultaneously with each other (or within a threshold time period). For example, the schematic diagram 700 includes a second XR stream 708. The second XR stream 708 may have different characteristics from the first XR stream 702. For example, the second XR stream 708 may have XR traffic bursts with a different number of packets, a different packet size, etc. In one example, the first XR stream 702 may include video data, and the second XR stream 708 may include audio data for the video data. In another example, the first XR stream 702 may include intra-coded picture frames (I frames) containing complete images, and the second XR stream 708 may include predicted picture frames (P frames) containing changes from previous images.

[0086] In a BSR configuration, a single BSR trigger condition set may correspond to one MAC entity. A set of BSR trigger conditions may be used for each of an LCG, a DRB, a PDU session, and various application flows. A BSR trigger condition set may correspond to whether the BSR is a short, long, or truncated BSR, but not to the reason why the BSR is triggered (e.g., whether the BSR is triggered due to the arrival of new data, a significant change in the amount of data to be transmitted, or as a periodic BSR transmission). Some timing mechanisms may use a timer to monitor the transmission process of data associated with an application, and if the transmission delay is too long and extends beyond a threshold amount of time, the device may react accordingly (e.g., discard the transmission or request a retransmission). For example, "TimerDiscard" may correspond to discarding a transmission based on a timer running at the PDCP layer. If a PDU waits at the PDCP layer for longer than the TimerDiscard, it will be discarded.

[0087] Various aspects presented herein provide the ability to enable various triggers at the PDU set level (rather than the PDU level). In the present disclosure, a "PDU set" may refer to a group of PDUs associated with an application frame (e.g., a video frame). For example, a BSR trigger condition set does not cover physical layer (PHY) aspects. In a BSR trigger mechanism based on a timer drop mechanism, even with a full hybrid automatic repeat request (HARQ) block error rate (BLER), when the BSR has been encoded in the MAC TB, the retransmission (ReTx) BSR timer logic may stop further BSR transmissions (e.g., retransmissions of the BSR) to the network for a period of time, which may prevent the BSR information from being sent to the network in a timely manner. When sending a PDU set, if HARQ fails or experiences delays due to retransmissions (which may result in missing the PDU set delay budget (PSDB) requirement), the BSR may be stopped or maintained due to the retransmission BSR. Therefore, even though some grants (e.g., transmission resources) may arrive in association with an earlier BSR, when the PSDB requirement is missed due to physical (PHY) layer issues, there may be no additional BSR triggering for the network. For example, when a timer drop occurs (e.g., due to transmission delays) and some PDU sets are dropped (which may affect QoS requirements), the BSR will not be triggered. Under the current BSR triggering mechanism, BSR triggering occurs when higher priority DRB data arrives, but not for data on the same DRB, and there is no distinction between higher or lower priority flows within the DRB under consideration. In addition, after the BSR information is sent to the network if the BSR triggering conditions are met, the BSR may change before the time when grants (e.g., transmission resources) start to arrive. In this case, the UE may not send an updated BSR until the conditions are met (e.g., one of the "regular or filler BSR" conditions is met) and the retransmission BSR (ReTxBSR) timer is not running.

[0088] The present disclosure provides signaling enhancements for BSR triggering conditions. In some aspects, the signaling enhancements may include additional BSR triggering conditions to enable the base station to obtain buffer status information in a timely manner. In some example aspects, these additional BSR triggering conditions may be introduced for XR-specific applications.

[0089] In some aspects, the BSR triggering conditions can be specific to a PDU set. In XR applications, there may be certain requirements for the transmission of the PDUs in a PDU set, such as a PDU set delay budget (PSDB) requirement and a PDU set error rate (PSER) requirement. For example, an example PSDB may be 100 milliseconds, and an example PSER may be 1%, meaning that the entire PDU set must be transmitted within 100 milliseconds with an error rate of no more than 1%.

[0090] In some aspects, the BSR triggering condition may be related to a latency condition for PDU aggregate transmission. In one example, the triggering condition may be related to the elapsed time since the start of the PDU aggregate transmission. For example, if the elapsed time since the start of the PDU aggregate transmission is greater than a first elapsed threshold and no grant (e.g., transmission resources) has been received, BSR transmission may be triggered. In another example, the triggering condition may be related to the elapsed time since the last grant (e.g., the last transmission providing transmission resources) was received. For example, if the elapsed time since the last grant (e.g., the last transmission providing transmission resources) was received is greater than a second elapsed threshold and no new grant (e.g., transmission resources) has been received, BSR transmission may be triggered. In another example, the triggering condition may be related to the experienced latency of the PDU aggregate transmission. For example, if the experienced latency of the PDU aggregate transmission is greater than a third threshold (or the ratio of the experienced latency to the PSDB is greater than a ratio threshold), BSR transmission may be triggered. In these examples, when the transmission of a PDU set experiences a delay greater than a certain threshold from the start of the PDU set arriving at the modem or from the receipt of the last grant, a BSR can be triggered to request further grant (e.g., additional transmission resources) from the network, which can help obtain the grant (e.g., transmission resources) within the PSDB to ensure that the PDU set is successfully transmitted in the PSDB from a flow perspective.

[0091] In some examples, grants (e.g., transmission resources) may be received periodically, and the time interval between adjacent grants (e.g., adjacent transmissions providing transmission resources) may be less than a second elapsed threshold. In these cases, the BSR triggering conditions based on the elapsed time since the start of the PDU set transmission and the elapsed time since the last grant received (e.g., the last transmission providing transmission resources) are not met, and a BSR may not be triggered based on these triggering conditions. However, in these cases, the total latency may exceed the PSDB. Therefore, sending a BSR based on the latency experienced can help the network increase grants (e.g., transmission resources) to, for example, meet PSDB requirements.

[0092] In some aspects, new BSR types may be provided, and the BSR may include an additional bit or field indicating the corresponding BSR type. The BSR type may indicate the reason why the BSR was triggered. For example, the reason may be that the elapsed time since the start of the PDU aggregate transmission or the elapsed time since the last grant was received is longer than a corresponding threshold. The additional bits or fields in the BSR may help the network react to the scheduling perspective (e.g., change the grant mode). For example, if the BSR type indicates that the BSR was triggered because the elapsed time since the last grant was received is longer than a corresponding threshold, the network may increase the frequency of sending grants. New BSR types may be provided, such as a "latency" type as an additional type. A BSR triggered by a latency condition for the PDU aggregate transmission may have an indication of the "latency type" as an additional bit / cause. This information may help the network react accordingly to the scheduling perspective.

[0093] In some aspects, a BSR triggering condition may be related to the number of HARQ failures or the overall HARQ conclusion delay. For example, a BSR may be triggered when the number of previous HARQ failures or the overall HARQ conclusion delay experienced exceeds a corresponding threshold. In one example, a BSR may be triggered if the number of HARQ failures is greater than two, or the overall HARQ conclusion delay is greater than 100 milliseconds.

[0094] In some aspects, a BSR triggering condition may be related to a timer drop for any PDU in a PDU set (e.g., one or more PDUs are dropped based on timer expiration). When a timer drop occurs and some PDUs are dropped, QoS requirements or PSER may be affected. Therefore, having an additional BSR triggering mechanism to indicate relevant information to the network may help the network better manage the PDU set transmission (e.g., by increasing grants to handle PSDB or preserving MCS to improve PSER). New BSR types may be provided, such as a "PHY" type as an additional type. A BSR triggered by a PHY problem related to the PDU set transmission (e.g., the number of previous HARQ failures experienced) may have an indication of, for example, a "drop type" as an additional bit / cause indicating the reason why the PDU was dropped. This information may help the network react to the received information with more efficient scheduling for the UE.

[0095] In some aspects, BSR triggering conditions may have flow-level differentiation. For example, a BSR triggering condition may be related to a new PDU set arriving on the same DRB as the current PDU set (on a flow of the same priority or higher priority, on the same flow or a different flow). A BSR triggering condition may also be related to a new PDU set arriving on a different DRB with the same priority, and these new PDU sets may belong to the same PDU session as the current PDU set or to a different PDU session.

[0096] Since multiple flows with different priorities and QoS requirements can be multiplexed on the same DRB, when high-priority flow data (compared to the previous BSR instance) arrives, additional BSRs can be sent to the network to help the network better arrange resources from the perspective of PSDB and PSER.

[0097] For example, on a given flow, the arrival of a higher priority PDU set (compared to a previous PDU set) or the arrival of a same priority flow on a bearer may indicate that the PDU set associated with the previous frame may be late. Therefore, a trigger for a BSR may be sent.

[0098] Even if data arrives on different DRBs of the same priority, a BSR may be triggered to indicate the presence of data if the PDU session types are different (e.g., IPv4, IPv6, IPv4v6, Ethernet (ETH), unspecified) or the PDU session slice types are different (e.g., eMBB, URLLC, mMTC, etc.), because some PDU sessions may be more sensitive to PSDB (e.g., ETH, URLLC) than other sessions.

[0099] Since all of the above scenarios may affect PSDB and PSER, additional BSR triggers related to these scenarios can be provided to indicate relevant information to the network so that the network can better manage PDU aggregate transmission. For example, the network can add grants to handle addressing PSDB or preserve MCS to improve PSER. New BSR types, such as "flow"-based types, can be provided as additional types. BSRs triggered by flow-level issues related to PDU aggregate transmission (e.g., a new PDU aggregate arriving on a DRB) can have an indication of the "flow type," for example, as an additional bit / cause. This information can help the network react accordingly from a scheduling perspective.

[0100] In some aspects, the BSR triggering condition may be related to a change in the BSR. When the BSR has changed between the time the BSR is reported and the time the first grant is received, a new BSR may be triggered even if the current data is not completely exhausted. In one example, the first BSR may report a requested data amount of 10K, and the grant may arrive 20ms later. At the same time, after the first BSR is sent, 4K of data may be discarded due to, for example, a timer drop on the same DRB. In this case, in the absence of an additional BSR, the network may assume that 10K is the requested data amount and schedule grants accordingly (for example, the network may schedule a grant of 5K at t=0 and another grant of 5K at t=10ms). However, the actual data amount before the first grant is 6K, and if the network is not notified of the updated data amount, a 4K grant may be wasted. Therefore, if the BSR has changed before the first grant is received, a new BSR may be reported in the first MAC TB (or each MAC TB where the change occurs) to notify the network of the updated BSR. For example, with the new BSR report, the network can schedule 1K (instead of 5K) of data at t=10ms to avoid wasting transmission resources.

[0101] In some aspects, the network can schedule in such a way that the total amount of data indicated by the BSR can be distributed over time. Thus, having an updated BSR at the time of the first grant or periodically can help the network adjust the scheduling mechanism, for example, by increasing or decreasing grants to meet the PSDB. For example, if the BSR increases, the network can increase the grant, or if the BSR decreases due to, for example, timer drops, the network can decrease the grant.

[0102] Since BSR updates may affect PSDB and PSER, having an additional BSR trigger mechanism to indicate BSR update information to the network can help the network better manage PDU aggregate transmission, for example, by increasing grants to handle PSDB or preserving MCS to improve PSER.

[0103] A new BSR type, such as an "updated" type, may be provided as an additional type. A BSR triggered by a BSR change may have an indication of the "updated type" as an additional bit / cause. This information may help the network react accordingly from a scheduling perspective.

[0104] Figure 8 8 is a call flow diagram 800 illustrating a method of wireless communication according to various aspects of the present disclosure. Although various aspects are described with respect to base station 804, these aspects can be performed by base stations in an aggregation and / or by one or more components of base station 804 (e.g., CU 110, DU 130, and / or RU 140).

[0105] like Figure 8 As shown in , at 806, UE 802 may send a first BSR to base station 804. The first BSR may request a UL grant from base station 804 for the UE to send UL data.

[0106] At 808, the base station 804 may allocate a corresponding UL grant to the UE 802 in response to the first BSR.

[0107] At 810, when UE 802 receives the UL grant from base station 804, UE 802 may begin transmitting data using the UL grant to base station 804. In some examples, the data may be a set of PDUs.

[0108] At 812, based on the transmission condition of the data, UE 802 may evaluate whether a BSR triggering condition from a plurality of BSR triggering conditions is satisfied. The plurality of BSR triggering conditions may be based on one or more of the following: a latency condition for the PDU set; a condition related to discarded packets (or PDUs) in the PDU set; a flow condition for the PDU set; or an update condition for the PDU set. For example, UE 802 may evaluate whether there is a delay in receiving an UL grant from base station 804, whether there are any HARQ failures associated with the data transmission, or whether another PDU set has arrived on the same DRB.

[0109] At 814, if one BSR triggering condition is met, UE 802 may send a second BSR to base station 804. For example, if UE 802 determines that the elapsed time since the last transmission resource received from base station 804 is longer than a corresponding threshold, UE 802 may send the second BSR at 814. The second BSR may include information regarding the reason why the second BSR was triggered.

[0110] At 816, based on the received second BSR, base station 804 may adjust the transmission scheme for UE 802. For example, the base station may adjust (e.g., increase or decrease) the transmission resources for the UE, or modify the MCS used for transmission. For example, if the second BSR indicates that the reason for the BSR is that the elapsed time since the last transmission resource received by base station 804 is longer than a corresponding threshold, base station 804 may reduce the interval between grant allocations to UE 802.

[0111] At 818, UE 802 may continue to communicate with base station 804 based on the BSR. For example, if base station 804 has adjusted the transmission scheme (e.g., adjusted the transmission resources or modified the MCS) at 816 based on the second BSR received at 814, UE 802 and base station 804 may continue to communicate based on the adjusted transmission scheme.

[0112] Figure 9 900 is a flow chart illustrating a wireless communication method at a UE according to various aspects of the present disclosure. The method may be performed by a UE. The UE may be UE 104, 350, 802, or Figure 13 The method provides multiple BSR triggering conditions based on various scenarios in data transmission. This method allows BSR information to be more easily available to the network and enables more efficient resource allocation. Therefore, it improves the efficiency of wireless communication.

[0113] like Figure 9 As shown in , at 902, the UE may send a BSR to a network entity in response to satisfying a BSR triggering condition from a plurality of BSR triggering conditions, wherein each of the plurality of BSR triggering conditions is associated with a PDU set including a group of PDUs. In some aspects, the PDU group may be associated with an application frame. The network entity may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; base station 804; or Figure 13 Network entity 1302 in a hardware implementation of FIG. Figure 8 Various aspects of the steps associated with flowchart 900 are shown. For example, referring to Figure 8 At 810, UE 802 may transmit a BSR to a network entity (base station 804) in response to a BSR triggering condition from a plurality of BSR triggering conditions being satisfied (at 812). Each of the plurality of BSR triggering conditions is associated with a PDU set comprising a group of PDUs that UE 802 begins transmitting at 810. In some examples, the PDU group may be associated with an application frame. In some aspects, 902 may be performed by BSR triggering component 198.

[0114] At 904, the UE may communicate with a network entity based on the BSR. Figure 8 At 818 , UE 802 can communicate with a network entity (base station 804 ) based on the BSR. In some aspects, 904 can be performed by BSR triggering component 198 .

[0115] Figure 10 1000 is a flow chart illustrating a wireless communication method at a UE according to various aspects of the present disclosure. The method may be performed by a UE. The UE may be UE 104, 350, 802, or Figure 13The method provides multiple BSR triggering conditions based on various scenarios in data transmission. This method allows BSR information to be more easily available to the network and enables more efficient resource allocation. Therefore, it improves the efficiency of wireless communication.

[0116] like Figure 10 As shown in , at 1002, the UE may send a BSR to a network entity in response to satisfying a BSR triggering condition from a plurality of BSR triggering conditions, wherein each of the plurality of BSR triggering conditions is associated with a PDU set including a group of PDUs. In some aspects, the PDU group may be associated with an application frame. The network entity may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; base station 804; or Figure 13 Network entity 1302 in a hardware implementation of FIG. Figure 8 Various aspects of the steps associated with flowchart 1000 are shown. For example, referring to Figure 8 At 810, UE 802 may transmit a BSR to a network entity (base station 804) in response to a BSR triggering condition from a plurality of BSR triggering conditions being satisfied (at 812). Each of the plurality of BSR triggering conditions is associated with a PDU set comprising a group of PDUs that UE 802 begins transmitting at 810. In some examples, the PDU group may be associated with an application frame. In some aspects, 1002 may be performed by BSR triggering component 198.

[0117] At 1004, the UE may communicate with a network entity based on the BSR. Figure 8 At 818 , UE 802 can communicate with a network entity (base station 804 ) based on the BSR. In some aspects, 1004 can be performed by BSR triggering component 198 .

[0118] In some aspects, such as Figure 10 As shown in , the multiple BSR triggering conditions may include one or more of the following: a delay condition (1012) of the PDU set; a condition related to the discarded packets (or PDUs) in the PDU set (1014); a flow condition (1016) of the PDU set; or an update condition (1018) of the PDU set. For example, referring to Figure 8 When the UE 802 evaluates at 812 whether a BSR from a plurality of BSR triggering conditions is satisfied, the plurality of BSR triggering conditions may include one or more of the following: a delay condition of a PDU set; a condition related to discarded packets (or PDUs) in a PDU set; a flow condition of a PDU set; or an update condition of a PDU set.

[0119] In some aspects, at 1006, the BSR may include a field indicating a BSR triggering condition. For example, referring to Figure 8 The BSR (eg, the second BSR at 814 ) may include a field indicating a BSR triggering condition (eg, the BSR triggering condition evaluated to be satisfied at 812 ).

[0120] In some aspects, the BSR triggering condition may be based on a latency condition (1012) of the PDU set. The latency condition may be based on one or more of: a first elapsed time since the beginning of the PDU set; a second elapsed time since the last transmission resource associated with the PDU set received by the network entity; or a ratio of the first elapsed time to the PSDB. For example, referring to Figure 8 , the latency condition can be based on one or more of: a first elapsed time since the start of transmission of the PDU set (at 810); a second elapsed time since the last transmission resource associated with the PDU set received by the network entity (base station 804) (at 808); or a ratio of the first elapsed time to the PSDB.

[0121] In some aspects, the BSR triggering condition may be based on a condition related to packets (or PDUs) discarded in the PDU set (1014). The condition related to packets (or PDUs) discarded in the PDU set may be based on one or more of: a number of hybrid automatic repeat request (HARQ) failures associated with the PDU set; an overall HARQ conclusion delay; or a number of timers dropped for PDUs in the PDU set. For example, referring to Figure 8 When the UE 802 evaluates whether a BSR triggering condition from a plurality of BSR triggering conditions is satisfied at 812, the BSR triggering condition may be based on a condition related to packets (or PDUs) discarded in the PDU set that the UE 802 begins sending at 810. The condition related to packets (or PDUs) discarded in the PDU set may be based on one or more of: a number of hybrid automatic repeat request (HARQ) failures associated with the PDU set; an overall HARQ conclusion delay; or a number of discarded timers for the PDUs in the PDU set.

[0122] In some aspects, the PDU set may be a first PDU set, and the BSR triggering condition is based on a flow condition (1016) of the first PDU set. The flow condition may be based on at least one of: a second PDU set arriving on the same DRB as the first PDU set; or a third PDU set arriving on a second DRB different from the DRB of the first PDU set. For example, referring to Figure 8When the UE 802 evaluates whether a BSR triggering condition from the plurality of BSR triggering conditions is satisfied at 812, the BSR triggering condition may be based on a flow condition of the first PDU set. The flow condition may be based on at least one of: a second PDU set arriving on the same DRB as the first PDU set; or a third PDU set arriving on a second DRB different from the DRB of the first PDU set.

[0123] In some aspects, the first PDU set and the second PDU set may be associated with the same flow or different flows. Figure 8 Different BSR triggering conditions may be specified (at 812) depending on whether the first PDU set and the second PDU set are associated with the same flow or different flows.

[0124] In some aspects, the first PDU set and the second PDU set may have the same priority or different priorities. Figure 8 Different BSR triggering conditions may be specified (at 812) depending on whether the first PDU set and the second PDU set may have the same priority or different priorities.

[0125] In some aspects, the first PDU set and the third PDU set may be associated with the same PDU session or different PDU sessions. Figure 8 Different BSR triggering conditions may be specified (at 812) depending on whether the first PDU set and the third PDU set are associated with the same PDU session or different PDU sessions.

[0126] In some aspects, the first PDU set and the third PDU set may have the same priority or different priorities. Figure 8 Different BSR triggering conditions may be specified (at 812) depending on whether the first PDU set and the third PDU set have the same priority or different priorities.

[0127] In some aspects, the BSR triggering condition may be based on an update condition (1018) of the PDU set. The update condition may be based on an increase or decrease in the data associated with the BSR from the BSR reporting time of the BSR to the reception time for receiving the first grant associated with the BSR. For example, referring to Figure 8When the UE 802 evaluates whether a BSR triggering condition from a plurality of BSR triggering conditions is satisfied at 812, the BSR triggering condition may be based on an update condition for the set of PDUs that the UE 802 begins sending at 810. The update condition may be based on an increase or decrease in data associated with the BSR from a BSR reporting time of the BSR (the time at which the first BSR was sent at 806) to a receive time for receiving (at 808) a first grant associated with the BSR.

[0128] In some aspects, multiple BSR triggering conditions can be based on the traffic type (1022) of one or more PDU sessions associated with the application. The traffic type can include one or more of the following: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4 and IPv6 (IPv4v6), ETH traffic, or unstructured traffic. For example, referring to Figure 8 When UE 802 evaluates whether a BSR trigger condition from a plurality of BSR trigger conditions is satisfied at 812, the plurality of BSR trigger conditions may be based on a traffic type of one or more PDU sessions associated with the application. The traffic type may include one or more of: IPv4, IPv6, IPv4v6, ETH traffic, or unstructured traffic.

[0129] In some aspects, multiple BSR triggering conditions may be based on slice characteristics (1024) associated with the application. The slice characteristics may include one or more of the following: slice type, slice ID, or UE routing selection policy (URSP) rules. For example, referring to Figure 8 When the UE 802 evaluates whether a BSR triggering condition from a plurality of BSR triggering conditions is satisfied at 812, the plurality of BSR triggering conditions may be based on slice characteristics associated with the application. The slice characteristics may include one or more of the following: a slice type, a slice ID, or a URSP rule.

[0130] In some aspects, multiple BSR triggering conditions can be based on link characteristics (1026) associated with the application. Link characteristics can include: TN connection or NTN connection. For example, referring to Figure 8 When UE 802 evaluates whether a BSR triggering condition from a plurality of BSR triggering conditions is satisfied at 812, the plurality of BSR triggering conditions may be based on link characteristics associated with the application. The link characteristics may include: a TN connection or an NTN connection.

[0131] In some aspects, the multiple BSR triggering conditions may be based on one or more of: an SCS characteristic associated with the application or a frequency band associated with the application (1028). The frequency band may include one of an FR1 band, an FR2 band, or an FR4 band. For example, referring to Figure 8 When the UE 802 evaluates whether a BSR triggering condition from a plurality of BSR triggering conditions is satisfied at 812, the plurality of BSR triggering conditions may be based on one or more of the following: an SCS characteristic associated with the application or a frequency band associated with the application. The frequency band may include one of an FR1 band, an FR2 band, or an FR4 band.

[0132] Figure 11 1 is a flow chart 1100 illustrating a method of wireless communication at a network entity according to various aspects of the present disclosure. The method may be performed by a network entity. The network entity may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310, 804; or Figure 13 The method provides multiple BSR triggering conditions based on various scenarios in data transmission. This method allows BSR information to be more readily available to the network and enables more efficient resource allocation. Therefore, it improves the efficiency of wireless communications.

[0133] like Figure 11 As shown in , at 1102, a network entity may receive a BSR from a UE, wherein the BSR is received in response to satisfying one of a plurality of BSR triggering conditions, and each of the plurality of BSR triggering conditions is associated with a PDU set including a group of PDUs. In some aspects, the PDU group may be associated with an application frame. The UE may be UE 104, 350, 802, or Figure 13 The device 1304 in a hardware implementation manner. Figure 8 Various aspects of the steps associated with flowchart 1100 are shown. For example, referring to Figure 8 At 814, the network entity (base station 804) may receive a BSR (e.g., a second BSR) from UE 802. The BSR is received (at 812) in response to one of a plurality of BSR triggering conditions being satisfied, and each of the plurality of BSR triggering conditions is associated with a PDU set comprising a group of PDUs (which UE 802 began transmitting at 810). In some examples, the PDU group may be associated with an application frame. In some aspects, 1102 may be performed by BSR triggering component 199.

[0134] At 1104, the network entity may communicate with the UE based on the BSR. Figure 8 At 818 , the network entity (base station 804 ) can communicate with UE 802 based on the BSR. In some aspects, 1104 can be performed by BSR triggering component 199 .

[0135] Figure 12 1 is a flow chart 1200 illustrating a method of wireless communication at a network entity according to various aspects of the present disclosure. The method may be performed by a network entity. The network entity may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310, 804; or Figure 13 The method provides multiple BSR triggering conditions based on various scenarios in data transmission. This method allows BSR information to be more readily available to the network and enables more efficient resource allocation. Therefore, it improves the efficiency of wireless communications.

[0136] like Figure 12 As shown, at 1202, a network entity may receive a BSR from a UE, wherein the BSR is received in response to one of a plurality of BSR triggering conditions being satisfied, and each of the plurality of BSR triggering conditions is associated with a PDU set including a group of PDUs. In some aspects, the PDU group may be associated with an application frame. The UE may be UE 104, 350, 802, or Figure 13 The device 1304 in a hardware implementation manner. Figure 8 Various aspects of the steps associated with flowchart 1200 are shown. For example, referring to Figure 8 At 814, the network entity (base station 804) may receive a BSR (e.g., a second BSR) from UE 802. The BSR is received (at 812) in response to one of a plurality of BSR triggering conditions being satisfied, and each of the plurality of BSR triggering conditions is associated with a PDU set comprising a group of PDUs (which UE 802 began transmitting at 810). In some examples, the PDU group may be associated with an application frame. In some aspects, 1202 may be performed by BSR triggering component 199.

[0137] At 1204, the network entity may communicate with the UE based on the BSR. Figure 8 At 818, the network entity (base station 804) may communicate with UE 802 based on the BSR. In some aspects, 1204 may be performed by BSR triggering component 199.

[0138] In some aspects, such as Figure 12 As shown in , the multiple BSR triggering conditions may include one or more of the following: a delay condition (1212) of the PDU set; a condition related to the discarded packets (or PDUs) in the PDU set (1214); a flow condition (1216) of the PDU set; or an update condition (1218) of the PDU set. For example, referring to Figure 8 When the UE 802 evaluates at 812 whether a BSR from a plurality of BSR triggering conditions is satisfied, the plurality of BSR triggering conditions may include one or more of the following: a delay condition of a PDU set; a condition related to discarded packets (or PDUs) in a PDU set; a flow condition of a PDU set; or an update condition of a PDU set.

[0139] In some aspects, at 1206, the BSR may include a field indicating a BSR triggering condition. For example, referring to Figure 8 The BSR (eg, the second BSR at 814 ) may include a field indicating a BSR triggering condition (eg, the BSR triggering condition evaluated to be satisfied at 812 ).

[0140] In some aspects, the BSR triggering condition may be based on a latency condition (1212) of the PDU set. The latency condition may be based on one or more of: a first elapsed time since the beginning of the PDU set; a second elapsed time since the last transmission resource associated with the PDU set received by the network entity; or a ratio of the first elapsed time to the PSDB. For example, referring to Figure 8 , the latency condition can be based on one or more of: a first elapsed time since the start of transmission of the PDU set (at 810); a second elapsed time since the last transmission resource associated with the PDU set received by the network entity (base station 804) (at 808); or a ratio of the first elapsed time to the PSDB.

[0141] In some aspects, the BSR triggering condition may be based on a condition related to packets (or PDUs) discarded in the PDU set (1214). The condition related to packets (or PDUs) discarded in the PDU set may be based on one or more of the following: a number of HARQ failures associated with the PDU set; an overall HARQ conclusion delay; or a number of timers discarded for PDUs in the PDU set. For example, referring to Figure 8When the UE 802 evaluates whether a BSR triggering condition from a plurality of BSR triggering conditions is satisfied at 812, the BSR triggering condition may be based on a condition related to packets (or PDUs) discarded in the PDU set that the UE 802 begins sending at 810. The condition related to packets (or PDUs) discarded in the PDU set may be based on one or more of: a number of hybrid automatic repeat request (HARQ) failures associated with the PDU set; an overall HARQ conclusion delay; or a number of discarded timers for the PDUs in the PDU set.

[0142] In some aspects, the PDU set may be a first PDU set, and the BSR triggering condition may be based on a flow condition (1216) of the first PDU set. The flow condition may be based on at least one of: a second PDU set arriving on the same DRB as the first PDU set; or a third PDU set arriving on a second DRB different from the DRB of the first PDU set. For example, referring to Figure 8 When the UE 802 evaluates whether a BSR triggering condition from the plurality of BSR triggering conditions is satisfied at 812, the BSR triggering condition may be based on a flow condition of the first PDU set. The flow condition may be based on at least one of: a second PDU set arriving on the same DRB as the first PDU set; or a third PDU set arriving on a second DRB different from the DRB of the first PDU set.

[0143] In some aspects, the first PDU set and the second PDU set may be associated with the same flow or different flows. Figure 8 Different BSR triggering conditions may be specified (at 812) depending on whether the first PDU set and the second PDU set are associated with the same flow or different flows.

[0144] In some aspects, the first PDU set and the second PDU set may have the same priority or different priorities. Figure 8 Different BSR triggering conditions may be specified (at 812) depending on whether the first PDU set and the second PDU set may have the same priority or different priorities.

[0145] In some aspects, the first PDU set and the third PDU set may be associated with the same PDU session or different PDU sessions. Figure 8 Different BSR triggering conditions may be specified (at 812) depending on whether the first PDU set and the third PDU set are associated with the same PDU session or different PDU sessions.

[0146] In some aspects, the first PDU set and the third PDU set may have the same priority or different priorities. Figure 8 Different BSR triggering conditions may be specified (at 812) depending on whether the first PDU set and the third PDU set have the same priority or different priorities.

[0147] In some aspects, the BSR triggering condition may be based on an update condition for a PDU set (1218). The update condition for the PDU set is based on an increase or decrease in the data associated with the BSR from the BSR reporting time of the BSR to the reception time for receiving the first grant associated with the BSR. For example, referring to Figure 8 When the UE 802 evaluates whether a BSR triggering condition from a plurality of BSR triggering conditions is satisfied at 812, the BSR triggering condition may be based on an update condition for the set of PDUs that the UE 802 begins sending at 810. The update condition may be based on an increase or decrease in data associated with the BSR from a BSR reporting time of the BSR (the time at which the first BSR was sent at 806) to a receive time for receiving (at 808) a first grant associated with the BSR.

[0148] In some aspects, to communicate with the UE based on the BSR, the network entity may be configured to, at 1208, increase transmission resources for the UE based on the PSDB and BSR of the PDU set, or, at 1210, modify the MCS associated with the PDU set based on the BSR to improve the PSER of the PDU set. For example, referring to Figure 8 , the network entity (base station 804) can be configured (at 816) to increase transmission resources for the UE based on the PSDB and BSR of the PDU set, or to modify the MCS associated with the PDU set based on the BSR to improve the PSER of the PDU set. In some aspects, 1208 and 1210 can be performed by BSR triggering component 199.

[0149] In some aspects, the multiple BSR triggering conditions may be based on one or more of the following: a service type (1222) of one or more PDU sessions associated with an application, wherein the service type comprises one or more of the following: IPv4, IPv6, IPv4v6, ETH service, or unstructured service; a slice characteristic (1224) associated with the application, wherein the slice characteristic comprises one or more of the following: a slice type, a slice ID, or a URSP rule; a link characteristic (1226) associated with the application, wherein the link characteristic comprises a TN connection or an NTN connection; an SCS characteristic associated with the application or a frequency band (1228) associated with the application, wherein the frequency band comprises one of an FR1 band, an FR2 band, or an FR4 band. For example, referring to Figure 8 , when UE 802 evaluates at 812 whether a BSR trigger condition from multiple BSR trigger conditions is met, the multiple BSR trigger conditions may be based on one or more of the following: a service type of one or more PDU sessions associated with the application, wherein the service type includes one or more of the following: IPv4, IPv6, IPv4v6, ETH service, or unstructured service; a slice characteristic associated with the application, wherein the slice characteristic includes one or more of the following: a slice type, a slice ID, or a URSP rule; a link characteristic associated with the application, wherein the link characteristic includes a TN connection or an NTN connection; an SCS characteristic associated with the application; or a frequency band associated with the application, wherein the frequency band includes one of an FR1 band, an FR2 band, or an FR4 band.

[0150] Figure 1313 is a diagram 1300 illustrating an example of a hardware implementation for an apparatus 1304. Apparatus 1304 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, apparatus 1304 may include at least one cellular baseband processor (or processing circuit) 1324 (also referred to as a modem) coupled to one or more transceivers 1322 (e.g., a cellular RF transceiver). Cellular baseband processor (or processing circuit) 1324 may include at least one on-chip memory (or memory circuit) 1324′. In some aspects, apparatus 1304 may further include one or more subscriber identity module (SIM) cards 1320 and at least one application processor (or processing circuit) 1306 coupled to a secure digital (SD) card 1308 and a screen 1310. Application processor (or processing circuit) 1306 may include on-chip memory (or memory circuit) 1306′. In some aspects, the device 1304 may further include a Bluetooth module 1312, a WLAN module 1314, an SPS module 1316 (e.g., a GNSS module), one or more sensor modules 1318 (e.g., a barometric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1326, a power supply 1330, and / or a camera 1332. The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include their own dedicated antennas and / or utilize antenna 1380 for communication. The cellular baseband processor (or processing circuit) 1324 communicates with the UE 104 and / or RUs associated with the network entity 1302 via one or more antennas 1380 via the transceiver 1322. The cellular baseband processor (or processing circuit) 1324 and the application processor (or processor circuit) 1306 can each include computer-readable media / memory (or memory circuit) 1324', 1306', respectively. The additional memory module 1326 can also be considered a computer-readable medium / memory (or memory circuit). Each computer-readable medium / memory (or memory circuit) 1324', 1306', 1326 can be non-transitory. The cellular baseband processor (or processing circuit) 1324 and the application processor (or processor circuit) 1306 are both responsible for general processing, including executing software stored on the computer-readable medium / memory (or memory circuit).When executed by the cellular baseband processor (or processing circuit) 1324 / application processor (or processor circuit) 1306, the software causes the cellular baseband processor (or processing circuit) 1324 / application processor (or processor circuit) 1306 to perform the various functions described above. The cellular baseband processor (or processing circuit) 1324 and the application processor (or processor circuit) 1306 are configured to perform the various functions described above based at least in part on information stored in the memory (or memory circuit). In other words, the cellular baseband processor (or processing circuit) 1324 and the application processor (or processor circuit) 1306 can be configured to perform a first subset of the various functions described above without the information stored in the memory, and can be configured to perform a second subset of the various functions described above based on the information stored in the memory. The computer-readable medium / memory (or memory circuit) can also be used to store data manipulated by the cellular baseband processor (or processing circuit) 1324 / application processor (or processor circuit) 1306 when executing the software. The cellular baseband processor (or processing circuit) 1324 / application processor (or processing circuit) 1306 may be a component of the UE 350 and may include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or at least one memory 360. In one configuration, the apparatus 1304 may be at least one processor chip (modem and / or applications) and include only the cellular baseband processor (or processing circuit) 1324 and / or the application processor (or processor circuit) 1306, and in another configuration, the apparatus 1304 may be the entire UE (e.g., see. Figure 3 UE 350) and includes additional modules of device 1304.

[0151] As discussed above, component 198 can be configured to send a BSR to a network entity in response to a BSR trigger condition from a plurality of BSR trigger conditions being satisfied, wherein each of the plurality of BSR trigger conditions is associated with a PDU set including a set of PDUs associated with a frame of an application; and communicate with the network entity based on the BSR. Component 198 can also be configured to perform a combined Figure 9 and Figure 10 The flowcharts described in and / or by Figure 81304. Component 198 may be within the cellular baseband processor (or processing circuit) 1324, the application processor (or processor circuit) 1306, or within both the cellular baseband processor (or processing circuit) 1324 and the application processor (or processing circuit) 1306. Component 198 may be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes / algorithms individually or in combination. As shown, apparatus 1304 may include various components configured for various functions. In one configuration, the apparatus 1304, in particular the cellular baseband processor (or processing circuit) 1324 and / or the application processor (or processing circuit) 1306, includes: means for sending a BSR to a network entity in response to a BSR triggering condition from a plurality of BSR triggering conditions being satisfied, wherein each of the plurality of BSR triggering conditions is associated with a PDU set including a set of PDUs associated with a frame of an application, and means for communicating with the network entity based on the BSR. The apparatus 1304 may also include means for performing a combined Figure 9 and Figure 10 Any aspects described in the flowcharts and / or by Figure 8 The UE 802 of FIG. 1304 may be a means for performing various aspects of the UE 802. A means may be a component 198 of the apparatus 1304 configured to perform the functions recited by the means. As described above, the apparatus 1304 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, a means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0152] Figure 1414 is a diagram illustrating an example of a hardware implementation for a network entity 1402. Network entity 1402 may be a base station (BS), a component of a BS, or may implement BS functionality. Network entity 1402 may include at least one of a CU 1410, a DU 1430, or a RU 1440. For example, depending on the layer functionality handled by component 199, network entity 1402 may include a CU 1410; both the CU 1410 and the DU 1430; each of the CU 1410, the DU 1430, and the RU 1440; the DU 1430; both the DU 1430 and the RU 1440; or the RU 1440. CU 1410 may include at least one CU processor (or processing circuitry) 1412. CU processor (or processing circuitry) 1412 may include on-chip memory (or memory circuitry) 1412′. In some aspects, CU 1410 may further include an additional memory module 1414 and a communication interface 1418. CU 1410 communicates with DU 1430 via a medium-range link (e.g., an F1 interface). DU 1430 may include at least one DU processor (or processing circuit) 1432. DU processor (or processing circuit) 1432 may include on-chip memory (or memory circuit) 1432′. In some aspects, DU 1430 may further include additional memory modules 1434 and a communication interface 1438. DU 1430 communicates with RU 1440 via a forward link. RU 1440 may include at least one RU processor (or processing circuit) 1442. RU processor (or processing circuit) 1442 may include on-chip memory (or memory circuit) 1442′. In some aspects, RU 1440 may further include additional memory modules 1444, one or more transceivers 1446, an antenna 1480, and a communication interface 1448. RU 1440 communicates with UE 104. On-chip memory (or memory circuit) 1412 ′, 1432 ′, 1442 ′ and additional memory modules 1414 , 1434 , 1444 can all be considered computer-readable media / memory (or storage circuit). Each computer-readable medium / memory (or storage circuit) can be non-transitory. Each of the processors (or processing circuits) 1412 , 1432 , 1442 is responsible for general processing, including executing software stored on the computer-readable medium / memory (or memory circuit). When executed by the corresponding processor (or processing circuit), the software causes the processor (or processor circuit) to perform the various functions described above. The computer-readable medium / memory (or memory circuit) can also be used to store data manipulated by the processor (or processing circuit) when executing the software.

[0153] As discussed above, component 199 may be configured to receive a BSR from a UE, wherein the BSR is received in response to satisfying one of a plurality of BSR triggering conditions, wherein each of the plurality of BSR triggering conditions is associated with a PDU set comprising a group of PDUs; and communicate with the UE based on the BSR. Component 199 may further be configured to perform a combined Figure 11 and Figure 12 The flowcharts described in and / or by Figure 8 1410, DU 1430, and RU 1440. Component 199 may be within one or more processors (or processing circuits) of one or more of the CU 1410, DU 1430, and RU 1440. Component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. The network entity 1402 may include various components configured for various functions. In one configuration, the network entity 1402 includes: a unit for receiving a BSR from a UE, wherein the BSR is received in response to satisfying one of a plurality of BSR trigger conditions, wherein each of the plurality of BSR trigger conditions is associated with a PDU set comprising a group of PDUs; and a unit for communicating with the UE based on the BSR. The network entity 1402 may also include a unit for performing a combined Figure 11 and Figure 12 Any aspects described in the flowcharts and / or by Figure 8 The present invention relates to a method for performing various aspects of the present invention in accordance with the present invention. The method may be a component 199 of the network entity 1402 configured to perform the functions recited by the means. As described above, the network entity 1402 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the method may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.

[0154] The present disclosure provides a method for wireless communication at a UE. The method may include: sending a BSR to a network entity in response to satisfying a BSR triggering condition from a plurality of BSR triggering conditions, wherein each of the plurality of BSR triggering conditions is associated with a PDU set including a group of PDUs; and communicating with the network entity based on the BSR.

[0155] This method provides multiple BSR triggering conditions based on various scenarios in data transmission. This method allows BSR information to be more easily available to the network and enables more efficient resource allocation. Therefore, it improves the efficiency of wireless communication.

[0156] It is to be understood that the specific order or hierarchy of blocks in the disclosed processes / flowcharts is illustrative of exemplary methods. It is to be understood that the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged based on design preferences. Furthermore, some blocks may be combined or omitted. The accompanying method claims present the elements of the various blocks in a sample order and are not limited to the specific order or hierarchy presented.

[0157] The foregoing description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may also be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but are to be given the full scope consistent with the language claims. Unless explicitly stated otherwise, reference to a singular element does not mean "one and only one," but rather "one or more." Terms such as "if," "when," and "while" do not imply a direct temporal relationship or reaction. That is, these phrases, such as "when," do not mean immediate action in response to an action or during the occurrence of an action, but simply mean that if the conditions are met, an action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be interpreted as being preferred or more advantageous than other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. For example, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A, B, and C, wherein any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements whose elements are numbered one or more. Thus, for a set of X, X will include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor is configured to perform the set of functions individually or in any combination. Thus, each processor in the at least one processor may be configured to perform a specific subset of a set of functions, where a subset is the full set, a proper subset of a set, or an empty subset of a set. A processor may be referred to as a processor circuit. A memory / memory module may be referred to as a memory circuit. If a first device receives data from a second device or sends data to a second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device via a set of devices. A device configured to "output" data or "provide" data (such as a transmission, signal, or message) may, for example, use a transceiver to send data, or may send data to a device that sends data.A device configured to "obtain" data (such as a transmission, signal or message) can, for example, be received using a transceiver, or can obtain data from a device that receives data. The information stored in the memory includes instructions and / or data. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or will later be known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, the content disclosed herein is not dedicated to the public, regardless of whether such disclosure is clearly recorded in the claims. The words "module", "mechanism", "element", "device" and the like may not be substitutes for the word "unit". Therefore, no claim element is to be interpreted as a functional module unless the element is clearly stated using the phrase "unit for..."

[0158] As used herein, the phrase "based on" should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless specifically stated differently, the phrase "based on A" (where "A" can be information, conditions, factors, etc.) should be interpreted as "based at least on A."

[0159] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein, but are not limited thereto.

[0160] Aspect 1 is a method of wireless communication at a UE. The method may include: sending a BSR to a network entity in response to a BSR triggering condition from a plurality of BSR triggering conditions being satisfied, wherein each of the plurality of BSR triggering conditions is associated with a PDU set including a group of PDUs; and communicating with the network entity based on the BSR.

[0161] Aspect 2 is a method according to Aspect 1, wherein the multiple BSR triggering conditions may include one or more of the following: a delay condition of the PDU set; a condition related to the PDU discarded in the PDU set; a flow condition of the PDU set; or an update condition of the PDU set.

[0162] Aspect 3 is a method according to any one of aspects 1 to 2, wherein the BSR may include a field indicating the BSR triggering condition.

[0163] Aspect 4 is a method according to any one of Aspects 2 to 3, wherein the BSR triggering condition may be based on the delay condition of the PDU set, and the delay condition is based on one or more of the following: a first elapsed time since the start of the PDU set; a second elapsed time since the last transmission resource associated with the PDU set received by the network entity; or a ratio of the first elapsed time to a PDU set delivery budget (PSDB).

[0164] Aspect 5 is a method according to any one of Aspects 2 to 3, wherein the BSR triggering condition may be based on the condition related to the PDU abandoned in the PDU set, and the condition related to the PDU abandoned in the PDU set is based on one or more of the following: the number of HARQ failures associated with the PDU set; the overall HARQ conclusion delay; or the number of timers discarded for the PDU in the PDU set.

[0165] Aspect 6 is a method according to any one of Aspects 2 to 3, wherein the PDU set may be a first PDU set, and the BSR trigger condition may be based on a flow condition of the first PDU set, the flow condition being based on at least one of: a second PDU set arriving on the same radio bearer (DRB) as the first PDU set; or a third PDU set arriving on a second DRB different from the DRB of the first PDU set.

[0166] Aspect 7 is a method according to aspect 6, wherein the first PDU set and the second PDU set may be associated with the same flow or different flows.

[0167] Aspect 8 is a method according to aspect 6, wherein the first PDU set and the second PDU set may have the same priority or different priorities.

[0168] Aspect 9 is the method according to aspect 6, wherein the first PDU set and the third PDU set may be associated with the same PDU session or different PDU sessions.

[0169] Aspect 10 is the method according to aspect 6, wherein the first PDU set and the third PDU set may have the same priority or different priorities.

[0170] Aspect 11 is a method according to any one of Aspects 2 to 3, wherein the update condition of the PDU set can be based on: an increase or decrease in the data associated with the BSR from the BSR reporting time of the BSR to the reception time for receiving the first grant associated with the BSR.

[0171] Aspect 12 is a method according to any one of Aspects 1-11, wherein the multiple BSR triggering conditions can be based on the service type of one or more PDU sessions associated with the application, wherein the service type includes one or more of the following: IPv4, IPv6, IPv4v6, ETH service or unstructured service.

[0172] Aspect 13 is a method according to any one of Aspects 1-11, wherein the multiple BSR triggering conditions may be based on slice characteristics associated with the application, and the slice characteristics may include one or more of a slice type, a slice ID, or a URSP rule.

[0173] Aspect 14 is a method according to any one of aspects 1-11, wherein the multiple BSR triggering conditions may be based on link characteristics associated with an application, and the link characteristics may include: the TN connection or the NTN connection.

[0174] Aspect 15 is a method according to any one of aspects 1-11, wherein the multiple BSR triggering conditions may be based on one or more of the following: an SCS characteristic associated with an application, or a frequency band associated with the application. The frequency band may include one of an FR1 band, an FR2 band, or an FR4 band.

[0175] Clause 16: An apparatus for wireless communication at a UE, comprising: a processing system including a processor circuit and a memory circuit storing code and coupled to the processor circuit, the processor system configured to cause the UE to perform the method according to one or more of aspects 1-15.

[0176] Aspect 17 is an apparatus for wireless communication at a UE, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured, alone or in any combination, to perform a method according to any one of aspects 1-15.

[0177] Aspect 18 is an apparatus for wireless communication at a UE, comprising: a unit for sending a BSR to a network entity in response to satisfying a BSR trigger condition from a plurality of BSR trigger conditions, wherein each of the plurality of BSR trigger conditions is associated with a PDU set comprising a group of PDUs; and a unit for communicating with the network entity based on the BSR.

[0178] Aspect 19 is the apparatus according to aspect 18, further comprising means for performing each step in the method according to any one of aspects 2-15.

[0179] Aspect 20 is an apparatus according to any one of aspects 16-19, further comprising a transceiver configured to receive or transmit in association with the method according to any one of aspects 1-15.

[0180] Aspect 21 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code at a UE, wherein the code, when executed by at least one processor, causes the at least one processor to perform a method according to any one of aspects 1-15, alone or in any combination.

[0181] Aspect 22 is a method of wireless communication at a network entity. The method may include: receiving a BSR from a UE, wherein the BSR is received in response to one of a plurality of BSR trigger conditions being satisfied, and each of the plurality of BSR trigger conditions is associated with a PDU set including a group of PDUs; and communicating with the UE based on the BSR.

[0182] Aspect 23 is an apparatus according to Aspect 22, wherein the multiple BSR triggering conditions may include one or more of the following: a delay condition of the PDU set; a condition related to the discarded PDUs in the PDU set; a flow condition of the PDU set; or an update condition of the PDU set.

[0183] Aspect 24 is a method according to any one of aspects 22 to 23, wherein the BSR may include a field indicating the BSR triggering condition.

[0184] Aspect 25 is a method according to any one of Aspects 23 to 24, wherein the BSR triggering condition may be based on the delay condition of the PDU set, and the delay condition is based on one or more of the following: a first elapsed time since the start of the PDU set; a second elapsed time since the last transmission resource associated with the PDU set received by the network entity; or a ratio of the first elapsed time to a PDU set delivery budget (PSDB).

[0185] Aspect 26 is a method according to any one of Aspects 23 to 24, wherein the BSR triggering condition may be based on the condition related to the PDU abandoned in the PDU set, and the condition related to the PDU abandoned in the PDU set is based on one or more of the following: the number of HARQ failures associated with the PDU set; the overall HARQ conclusion delay; or the number of timers discarded for the PDU in the PDU set.

[0186] Aspect 27 is a method according to any one of Aspects 23 to 24, wherein the PDU set is a first PDU set, and the BSR trigger condition can be based on the flow condition of the first PDU set, and the flow condition is based on at least one of the following: a second PDU set arriving on the same DRB as the first PDU set; or a third PDU set arriving on a second DRB different from the DRB of the first PDU set.

[0187] Aspect 28 is a method according to aspect 27, wherein the first PDU set and the second PDU set may be associated with the same flow or different flows.

[0188] Aspect 29 is a method according to aspect 27, wherein the first PDU set and the second PDU set may have the same priority or different priorities.

[0189] Aspect 30 is a method according to aspect 27, wherein the first PDU set and the third PDU set may be associated with the same PDU session or different PDU sessions.

[0190] Aspect 31 is a method according to aspect 27, wherein the first PDU set and the third PDU set may have the same priority or different priorities.

[0191] Aspect 32 is a method according to any one of aspects 23 to 24, wherein the update condition of the PDU set can be based on an increase or decrease in data associated with the BSR from a BSR reporting time of the BSR to a reception time for receiving a first grant associated with the BSR.

[0192] Aspect 33 is a method according to any one of Aspects 22 to 32, wherein, in order to communicate with the UE based on the BSR, the network device can be configured to: increase the transmission resources for the UE based on the PSDB of the PDU set and the BSR; or modify the MCS associated with the PDU set based on the BSR to improve the PSER of the PDU set.

[0193] Aspect 34 is a method according to any one of Aspects 22 to 32, wherein the multiple BSR triggering conditions may be based on one or more of the following: the service type of one or more PDU sessions associated with the application, wherein the service type includes one or more of the following: IPv4, IPv6, IPv4v6, ETH service or unstructured service; the slice characteristics associated with the application, wherein the slice characteristics include one or more of the following: slice type, slice ID or URSP rule; the link characteristics associated with the application, wherein the link characteristics include the TN connection or the NTN connection; the SCS characteristics related to the application; or the frequency band associated with the application, wherein the frequency band includes one of the FR1 band, the FR2 band or the FR4 band.

[0194] Clause 35 is an apparatus for wireless communication at a network entity, comprising: a processing system including a processor circuit and a memory circuit storing code and coupled to the processor circuit, the processor system being configured to cause the network entity to perform the method according to one or more of aspects 22-34.

[0195] Aspect 36 is an apparatus for wireless communication at a network entity, comprising: at least one memory; and at least one processor coupled to the at least one memory, and wherein the at least one processor is configured, alone or in any combination, to perform a method according to any one of aspects 22-34.

[0196] Aspect 37 is an apparatus for wireless communication at a network entity, comprising: a unit for receiving a BSR from a UE, wherein the BSR is received in response to satisfying one of a plurality of BSR trigger conditions, wherein each of the plurality of BSR trigger conditions is associated with a PDU set comprising a group of PDUs; and a unit for communicating with the UE based on the BSR.

[0197] Aspect 38 is the apparatus according to aspect 37, further comprising means for performing each step in the method according to any one of aspects 23-34.

[0198] Aspect 39 is an apparatus according to any one of aspects 35-38, further comprising a transceiver configured to receive or transmit in association with the method according to any one of aspects 22-34.

[0199] Aspect 40 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code at a network entity, which, when executed by at least one processor, causes the at least one processor to perform a method according to any one of aspects 22-34, alone or in any combination.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: at least one memory; as well as at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured, individually or in combination, to cause the UE to: In response to satisfying a buffer status report (BSR) triggering condition from a plurality of BSR triggering conditions, sending a BSR to a network entity, wherein each of the plurality of BSR triggering conditions is associated with a protocol data unit (PDU) set including a group of PDUs; as well as Communicate with the network entity based on the BSR.

2. The apparatus of claim 1 , further comprising a transceiver coupled to the at least one processor, wherein To send the BSR, the at least one processor is configured, individually or in combination, to send the BSR via the transceiver, and wherein the plurality of BSR triggering conditions include one or more of the following: The delay condition of the PDU set; conditions related to discarded PDUs in the PDU set; the flow condition of the PDU set; or The update condition of the PDU set.

3. The device according to claim 2, wherein The BSR includes a field indicating the BSR triggering condition.

4. The device according to claim 2, wherein The BSR triggering condition is based on the delay condition of the PDU set, and the delay condition is based on one or more of the following: a first elapsed time since the start of the PDU set; a second elapsed time since a last transmission resource associated with the set of PDUs received by the network entity; or A ratio of the first elapsed time to a PDU set delivery budget (PSDB).

5. The device according to claim 2, wherein The BSR triggering condition is based on the condition related to the discarded PDU in the PDU set, and the condition related to the discarded PDU in the PDU set is based on one or more of the following: a number of Hybrid Automatic Repeat Request (HARQ) failures associated with the PDU set; Overall HARQ conclusion delay; or The number of discard timers for the PDU in the PDU set.

6. The device according to claim 2, wherein The PDU set is a first PDU set, and wherein the BSR triggering condition is based on the flow condition of the first PDU set, the flow condition being based on at least one of the following: a second set of PDUs arriving on the same radio bearer (DRB) as the first set of PDUs; or A third set of PDUs arrives on a second DRB different from the DRB of the first set of PDUs.

7. The device according to claim 6, wherein The first PDU set and the second PDU set are associated with the same flow or different flows.

8. The device according to claim 6, wherein The first PDU set and the second PDU set have the same priority or different priorities.

9. The device according to claim 6, wherein The first PDU set and the third PDU set are associated with the same PDU session or different PDU sessions.

10. The device according to claim 6, wherein The first PDU set and the third PDU set have the same priority or different priorities.

11. The device according to claim 2, wherein The BSR triggering condition is based on the update condition of the PDU set, and the update condition is based on: The data associated with the BSR is increased or decreased from a BSR reporting time of the BSR to a reception time for receiving a first grant associated with the BSR.

12. The device according to claim 1, wherein The multiple BSR triggering conditions are based on a service type of one or more PDU sessions associated with the application, wherein the service type includes one or more of the following: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4&IPv6 (IPv4v6), Ethernet (ETH) services, or Unstructured business.

13. The device according to claim 1, wherein The multiple BSR triggering conditions are based on slice characteristics associated with the application, where the slice characteristics include one or more of the following: Slice type, Slice ID, or UE Routing Selection Policy (URSP) rules.

14. The device according to claim 1, wherein The multiple BSR triggering conditions are based on link characteristics associated with the application, wherein the link characteristics include: Terrestrial Network (TN) connection, or Non-terrestrial network (NTN) connection.

15. The device according to claim 1, wherein The multiple BSR triggering conditions are based on one or more of the following: The SCS characteristics associated with the application, or The frequency band associated with the application.

16. An apparatus for wireless communication at a network entity, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured, individually or in combination, to cause the network entity to: receiving a buffer status report (BSR) from a user equipment (UE), wherein the BSR is received in response to satisfying one of a plurality of BSR triggering conditions, wherein each of the plurality of BSR triggering conditions is associated with a protocol data unit (PDU) set including a group of PDUs; and Communicate with the UE based on the BSR.

17. The apparatus of claim 16, further comprising a transceiver coupled to the at least one processor, wherein To receive the BSR, the at least one processor is configured, individually or in combination, to receive the BSR via the transceiver, and wherein the plurality of BSR triggering conditions include one or more of the following: The delay condition of the PDU set; conditions related to discarded PDUs in the PDU set; the flow condition of the PDU set; or The update condition of the PDU set.

18. The device according to claim 17, wherein The BSR includes a field indicating the one BSR triggering condition.

19. The device according to claim 17, wherein The one BSR triggering condition is based on the delay condition of the PDU set, and the delay condition is based on one or more of the following: a first elapsed time since the start of the PDU set; a second elapsed time since a last transmission resource associated with the set of PDUs received by the network entity; or A ratio of the first elapsed time to a PDU set delivery budget (PSDB).

20. The apparatus according to claim 17, wherein The one BSR triggering condition is based on the condition related to the discarded PDU in the PDU set, and the condition related to the discarded PDU in the PDU set is based on one or more of the following: a number of Hybrid Automatic Repeat Request (HARQ) failures associated with the PDU set; Overall HARQ conclusion delay; or The number of discard timers for the PDU in the PDU set.

21. The apparatus according to claim 17, wherein The PDU set is a first PDU set, and wherein the one BSR triggering condition is based on the flow condition of the first PDU set, the flow condition being based on at least one of the following: a second set of PDUs arriving on the same radio bearer (DRB) as the first set of PDUs; or A third set of PDUs arrives on a second DRB different from the DRB of the first set of PDUs.

22. The device according to claim 21, wherein The first PDU set and the second PDU set are associated with the same flow or different flows.

23. The device according to claim 21, wherein The first PDU set and the second PDU set have the same priority or different priorities.

24. The apparatus according to claim 21, wherein The first PDU set and the third PDU set are associated with the same PDU session or different PDU sessions.

25. The apparatus according to claim 21, wherein The first PDU set and the third PDU set have the same priority or different priorities.

26. The apparatus according to claim 17, wherein The one BSR triggering condition is based on the update condition of the PDU set, and the update condition is based on: The data associated with the BSR is increased or decreased from a BSR reporting time of the BSR to a reception time for receiving a first grant associated with the BSR.

27. The apparatus according to claim 16, wherein In order to communicate with the UE based on the BSR, the at least one processor is configured, individually or in combination, to cause the network entity to perform the following operations: increasing transmission resources for the UE based on a PDU aggregate delivery budget (PSDB) of the PDU aggregate and the BSR; or A modulation and coding scheme (MCS) associated with the PDU set is modified based on the BSR to improve a PDU set error rate (PSER) of the PDU set.

28. The apparatus according to claim 16, wherein The multiple BSR triggering conditions are based on one or more of the following: a traffic type of one or more PDU sessions associated with the application, wherein the traffic type comprises one or more of: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4 and IPv6 (IPv4v6), Ethernet (ETH) traffic, or unstructured traffic; Slice characteristics associated with the application, wherein the slice characteristics include one or more of a slice type, a slice ID, or a UE Routing Selection Policy (URSP) rule; a link characteristic associated with the application, wherein the link characteristic comprises a terrestrial network (TN) connection or a non-terrestrial network (NTN) connection; SCS characteristics associated with the application; or The frequency band associated with the application.

29. A method of wireless communication at a user equipment (UE), comprising: In response to a buffer status report (BSR) triggering condition from a plurality of BSR triggering conditions being satisfied, sending a BSR to a network entity, wherein each of the plurality of BSR triggering conditions is associated with a protocol data unit (PDU) set including a group of PDUs; and Communicate with the network entity based on the BSR.

30. A method of wireless communication at a network entity, comprising: receiving a buffer status report (BSR) from a user equipment (UE), wherein the BSR is received in response to satisfying one of a plurality of BSR triggering conditions, wherein each of the plurality of BSR triggering conditions is associated with a protocol data unit (PDU) set including a group of PDUs; and Communicate with the UE based on the BSR.

Images