BSR configuration enhancements

Abstract

A method and related apparatus for wireless communication at a user equipment (UE) are provided. In the method, the UE obtains a plurality of buffer status report (BSR) tables and a plurality of sets of one or more timers. Each of the plurality of BSR tables corresponds to one of a plurality of logical channel groups (LCGs). The UE also communicates with a network entity based on a selected one BSR table from the plurality of BSR tables and a selected one set of timers from the plurality of sets of the one or more timers. According to the method, the UE can obtain a plurality of BSR tables and BSR timers, and the corresponding BSR tables and timers are selected according to the specific characteristics of the service.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 479,978, filed on January 13, 2023, entitled “BSR CONFIGURATION ENHANCEMENTS,” and U.S. Non-Provisional Patent Application No. 18 / 405,985, filed on January 5, 2024, entitled “BSR CONFIGURATION ENHANCEMENTS,” the entire contents of which are expressly incorporated herein by reference. Technical Field

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

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

[0005] 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 4G 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

[0006] The following is a simplified overview of one or more aspects to provide a basic understanding of these aspects. This overview is not an extensive overview of all contemplated aspects. This overview neither identifies key or important elements of all aspects nor delineates 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 provided later.

[0007] 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, wherein the at least one processor may be configured to perform certain actions based at least in part on information stored in the memory. The method, computer-readable medium, and apparatus obtain a plurality of BSR tables and a plurality of sets of one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to one of a plurality of logical channel groups (LCGs); and communicate with a network entity based on a BSR table selected from the plurality of BSR tables and a timer set selected from the plurality of sets of one or more timers.

[0008] 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, wherein the at least one processor may be configured to perform certain actions based at least in part on information stored in the memory. The method, computer-readable medium, and apparatus provide an indication to a UE for the UE to select a BSR table from a plurality of BSR tables and a set of one or more timers from a plurality of sets of one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to one of a plurality of LCGs; and communicate with the UE based on the one BSR table and the set of one or more timers indicated for the UE.

[0009] To accomplish the foregoing and related ends, 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 only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0016] Figure 4A and 4B is a diagram illustrating example data structures of a buffer status report (BSR) and a medium access control (MAC)-control element (MAC-CE).

[0017] Figure 4C An example of an extended reality (XR) traffic flow is shown.

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

[0019] Figure 6 is a diagram showing example mappings between different flows, radio bearers (RBs), service data adaptation protocols (SDAPs), and protocol data units (PDUs) sessions.

[0020] Figure 7 is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure.

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

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

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

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

[0025] Figure 12are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

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

[0027] 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 more efficient allocation of resources by the network for wireless communication with the UE. A BSR table refers to a defined set of values that maps the size of data in a buffer to a specific index, which can then be sent to the network in the BSR. For example, the defined set of values can be defined in a wireless standard and, in some examples, can be referred to as "predefined." A BSR table can reduce communication overhead because the UE can send an index to indicate the buffer size relative to the BSR table, rather than sending the exact buffer size. Current BSR configurations operate on a model with one BSR table for one medium access control (MAC) entity, and this BSR table is used to indicate various logical channel groups (LCGs), radio bearers (e.g., data radio bearers (DRBs) or signaling radio bearers (SRBs)), protocol data unit (PDU) sessions, and application flows. Example aspects presented herein provide a solution with an enhanced BSR configuration that is more suitable for various communication scenarios. Aspects presented herein can be used to provide improved BSR in various types of services, for example in the context of extended reality (XR). The proposed enhancements to BSR configuration allow multiple BSR tables to be configured corresponding to different link characteristics, PDU sessions, and logical channels, thereby improving the accuracy of BSR data and the responsiveness of wireless communications. In some aspects, switching between BSR tables can be indicated in signaling such as a medium access control-control element (MAC-CE). In some aspects, the indication can be based on activation / deactivation or enable / disable of a cell group (CG), component carrier, or based on throughput or admission mode. In some aspects, a UE can receive configuration of multiple BSR timers (e.g., periodic BSR timers or scheduling request (SR) delay timers) that are specific to an LCG or a quality of service (QoS) flow. In some aspects, a UE can indicate a BSR based on a BSR table that is specific to a specific protocol data unit (PDU) session, link, or subcarrier spacing (SCS).

[0028] Certain aspects of the inventive 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 obtain multiple BSR tables and one or more timers, the described techniques can be used to allow the UE to select a BSR table and timer based on the specific characteristics of the service. This approach enables uplink (UL) data transmission to be flexibly customized based on operational requirements. Consequently, 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. In order to provide a thorough understanding of the various concepts, the detailed description includes specific details. 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 such concepts.

[0030] Several aspects of telecommunication systems are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the detailed description below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the 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", which includes one or more processors. When multiple processors are implemented, multiple processors can perform functions individually or in combination. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic, a discrete hardware circuit, 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 referring to software, firmware, middleware, microcode, hardware description language or other, software should be broadly interpreted as an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable program, a thread of execution, a program, a function or any combination thereof.

[0032] Therefore, in one or more example aspects, implementations and / or use cases, the functions described can be implemented in hardware, software or any combination thereof. If implemented in software, the functions can be stored 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. The storage medium can be any available medium that can be accessed by a computer. By way of example, such computer-readable media can 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 the aforementioned computer-readable media types, or any other medium that can be used to store computer-executable code that can be accessed by a computer in the form of instructions or data structures.

[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 appear 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 generated 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 specifically point to use cases or applications, the applicability of various types of described examples may appear. Various aspects, implementations and / or use cases can be in the range of chip-level or modular components from one or more technologies incorporated herein to non-modular, non-chip-level implementations, and further to aggregated, distributed or original equipment manufacturer (OEM) devices or systems. In some actual settings, the device incorporating the described aspects and features may also include additional components and features for the implementation and practice 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, such as a 5G New Radio (NR) system, can be arranged in a variety of ways in various components or constituent 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 disaggregated 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 known as a standalone BS or a monolithic BS) or a disaggregated base station.

[0035] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may 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 may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may 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 that of 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 distributing functions across two or more units at various physical locations, as well as virtually distributing 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 11 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, or 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 or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interface of the unit, may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units on a wired transmission medium. Additionally, a unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit signals to one or more of the other units, or both, on a wireless transmission medium.

[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 (e.g., via an E1 interface when implemented in an O-RAN configuration). If necessary, the CU 110 may be implemented to communicate with the DU 130 for network control and signaling.

[0040] Thus, 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, the DU 130 may host one or more of 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.) at least in part according to a functional split (such as that defined by 3GPP). 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 of 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 (such as 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 (such as the Open eNB (O-eNB) 111) via the O1 interface. In addition, 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 that is 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 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 125 and can 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 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 can 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, the DU 130, and the 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, the DU 130, and the RU 140 (each component indicated by a dotted line indicates 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 including 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 BS 140 to UE 104. The communication link may utilize 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 utilize spectrum with up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) of 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 be adjacent to each other 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). The D2D communication may be performed via 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), LTE, or NR, based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard.

[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, e.g., in a 5 GHz unlicensed spectrum, etc. 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 prior to 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 generally 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.125GHz-24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the characteristics of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to above 52.6GHz. For example, three higher operating bands have been identified as the frequency range designations FR2-2 (52.6GHz–71GHz), FR4 (71GHz–114.25GHz), and FR5 (114.25GHz–300GHz). 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) can 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, if the term "millimeter wave" and the like are used herein, they can 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] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the optimal receive and transmit direction for each base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the 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 as 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 disaggregated base stations and / or converged 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 signal may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., air pressure sensor, motion sensor), NR enhanced cell ID (NRe-CID) methods, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of emission (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of incidence (UL-AoA) positioning) and / or other systems / signals / sensors.

[0054] Examples of UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, 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 UEs 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 companion devices 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 configuration component 198. The BSR configuration component 198 may be configured to obtain a plurality of BSR tables and a plurality of sets of one or more timers (e.g., several timers), wherein each BSR table in the plurality of BSR tables corresponds to one of the plurality of LCGs; and communicate with a network entity based on a BSR table selected from the plurality of BSR tables and a set of timers selected from the plurality of sets of one or more timers. In certain aspects, the base station 102 may include a BSR configuration component 199. The BSR configuration component 199 may be configured to provide an indication to the UE for the UE to select a BSR table from the plurality of BSR tables and a set of one or more timers from the plurality of sets of one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to one of the plurality of LCGs; and communicate with the UE based on the indicated BSR table and the set of one or more timers. 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 FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2CFIG250 is a diagram showing an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating 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), a subframe within a subcarrier set is dedicated to either DL or UL), or may be time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), a subframe within a subcarrier set is dedicated to both DL and UL). Figure 2A 、 Figure 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 subframe 3 and subframe 4 are shown as having slot format 1 and slot format 28, respectively, any particular subframe can be configured using any of the various available slot formats 0-61. Slot format 0 and slot format 1 are all DL and all UL, respectively. The other slot formats 2-slot format 61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format (dynamically through DL control information (DCI), or semi-statically / statically through radio resource control (RRC) signaling) through 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 microslots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. 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 is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled by 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μ time slots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is the digital scheme 0 to 4. As such, 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) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific number scheme and CP (normal or extended).

[0061] The frame structure can be represented using a resource grid. Each time slot includes a resource block (also known as a physical RB (PRB)), which extends over 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] like 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) (indicated as Rx for one specific configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. 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 in an OFDM symbol of a resource block. The PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during a PDCCH monitoring opportunity on the CORESET, 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 called SS block (SSB)). The MIB provides the number of resource blocks in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent through the PBCH (such as system information block (SIB)) and paging messages.

[0064] like Figure 2C As shown, some of the REs carry DM-RSs for channel estimation performed at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE can send DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the first one or two symbols of the PUSCH. The PUCCH DM-RS can 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 can send a sounding reference signal (SRS). The SRS can be sent in the last symbol of the subframe. The SRS can have a comb structure, and the UE can send the SRS in one of the combs. The SRS can be used by the base station for channel quality estimation to achieve frequency-related scheduling on the UL.

[0065] Figure 2D An example of various UL channels within one 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 the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with broadcasting 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 header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with 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 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 (which includes 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 onto 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 together 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 can be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimates can be derived from a reference signal and / or channel state feedback transmitted by the UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can 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 respective 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 functions 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 uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. 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 base station 310. The data and control signals are then provided to 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, as well as 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 respective 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 respective 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 configuration 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 configuration component 199.

[0076] The UE may have uplink data to send to the network. The UE may send a BSR, for example in a MAC-CE, from the UE to the network, which may include information about the amount of data in the UE 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) with 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, a 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. As used herein, a logical channel group or LCG can refer to a collection of logical channels categorized based on their function or purpose. Figure 4A FIG4 is a diagram 400 illustrating an example data structure of a Short BSR MAC-CE. Figure 4A As shown, the short BSR may include the LCGID 402 of a single LCG and the buffer size 404. For example, the LCGID 402 may be 2 bits and the buffer size 404 may include 6 bits. The buffer size 404 may indicate the amount of data of the LCG indicated by the LCGID 402. Figure 4B FIG450 is a diagram illustrating an example data structure of a Long BSR MAC-CE. Figure 4B As shown, the 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. As an 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] A BSR may be an aperiodic BSR or a periodic BSR, depending on the timing at which the BSR is sent to the network. The UE may send an aperiodic BSR, which in some aspects may be referred to as a regular BSR, in response to new data arriving in the UE buffer and based on the new data having a higher priority than data already waiting in the UE buffer. The UE may send a periodic BSR according to a preset period (e.g., a period that may be configured by the network for BSR transmission).

[0079] In a BSR configuration, a single BSR table may correspond to a MAC entity, and the BSR for the MAC entity may be based on a single BSR table. A single BSR table may be used for each of the LCGs, RBs (which may include DRBs or SRBs), PDU sessions, and various application flows for a MAC entity. For example, a BSR table may be associated with a given MAC entity regardless of a specific transmission scenario, such as the number of active CCs, the bandwidth (BW) of each CC. In some aspects, the BSR table may be indicated based on the BW or CC approach and how they are enabled / disabled through a MAC-CE mechanism or an RRC configuration-based mechanism. A single BSR table does not enable BSR reporting differentiation between one PDU session or multiple PDU sessions. The use of a single BSR table does not provide differentiation between PDU session bearers that are mapped to different services using UE Routing Policy (URSP) rules or advanced QoS requirements for network functions (e.g., slicing methods) or that carry different types of traffic. Additionally, a single BSR table may not be able to differentiate between BSR information between MAC entities operating on different frequency bands (e.g., FR1 or FR2), or for links based on different operating modes (e.g., terrestrial network (TN) or non-terrestrial network (NTN) operating modes), or when the NTN connection is on different mechanisms (e.g., high altitude platform station (HAPS), low earth orbit (LEO) / medium earth orbit (MEO) / geostationary orbit (GEO)). In some aspects, the UE may receive an RRC configuration for BSR that configures different timers related to the BSR at the MAC entity level. However, these timers may be applied to each logical channel or logical channel group. Various aspects presented herein provide BSR timers that may be logical channel (LC) specific, LCG specific, or flow specific, which allow BSR transmissions to be handled differently for different LCs, LCGs, or flows.

[0080] Figure 5 FIG5 is a diagram 500 illustrating an example mapping of QoS flows across bearers. Figure 5As shown, various QoS flows can be mapped based on different QoS requirements on 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 standards or algorithms for identifying the start and end of data packets (e.g., data packet 520) sent over 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). 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).

[0081] Figure 6 is a diagram 600 showing an example mapping between different flows, DRBs, SDAPs, and PDU sessions. Figure 6 In the example, different PDU sessions, such as an Internet PDU session 602, a streaming PDU session 604, or an IP Multimedia Subsystem (IMS) PDU session 606, may have different QoS requirements. Each PDU session may get 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, QoS flow 1620 may be mapped to DRB 1630, and QoS flow 2622 and QoS flow 3624 may be mapped to the same DRB (DRB 2632). Figure 6As shown, multiple DRBs (e.g., a default DRB and optional dedicated DRBs) can be mapped to the same PDU session. For example, DRB 1 630 and DRB 2 632 can be mapped to Internet PDU session 602. One SDAP entity can correspond to one PDU session. For example, SDAP entity 652 can correspond to Internet PDU session 602, SDAP entity 654 can correspond to streaming video PDU session 604, and SDAP entity 656 can correspond to IMS PDU session 606.

[0082] Wireless communication systems can support various types of services. Among other types of services, wireless communication systems can support XR services. XR traffic may refer to wireless communications used for technologies such as virtual reality (VR), mixed reality (MR), and / or augmented reality (AR). VR may 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 may refer to technologies that blend aspects of virtual and real environments. AR may refer to technologies in which objects residing in the real world are augmented via computer-generated sensory information, sometimes across multiple sensory modalities such as vision, hearing, touch, body sensation, and / or smell. AR systems can combine the real and virtual worlds, enable real-time interaction, and enable precise three-dimensional registration of virtual and real objects. In examples, AR systems can overlay sensory information (e.g., images) onto the natural environment and / or mask real objects from the natural environment. XR services may include video data and / or audio data. The XR service may be transmitted by the base station and received by the UE, or the XR service may be transmitted by the UE and received by the base station.

[0083] XR traffic may arrive in 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 4C Schematic diagram 475 in FIG. 4 shows a first XR stream 472 including a first XR traffic burst 474 and a second XR traffic burst 476. As shown in schematic diagram 475, the traffic bursts can include different numbers of packets. For example, the first XR traffic burst 474 is shown as having three packets (represented as rectangles in schematic diagram 475), while the second XR traffic burst 476 is shown as having two packets. Furthermore, as shown in schematic diagram 475, the three packets in the first XR traffic burst 474 and the two packets in the second XR traffic burst 476 can vary in size. That is, the packets within the first XR traffic burst 474 and the second XR traffic burst 476 can include varying amounts of data.

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

[0085] 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 at which the UE (or base station) expects the XR traffic burst. The variability of packet arrival relative to a time period (e.g., a 16.76ms time period, an 8.33ms time period, etc.) may be referred to as "jitter." In an example, the jitter range for XR traffic may be from -4ms (arriving earlier than expected) to +4ms (arriving later than expected). For example, referring to the first XR stream 472, the UE may expect the first packet of the first XR traffic burst 474 to arrive at time t0, but the second packet of the first XR traffic burst 474 arrives at time t1.

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

[0087] The present disclosure provides methods and apparatus for BSR configuration enhancement. In some aspects, multiple BSR tables can be provided to a UE, for example, by introducing one or more additional BSR tables. In some examples, additional BSR tables can be introduced for XR-specific applications. These BSR tables can be statically or dynamically configured based on, for example, RRC parameters signaled by the network. For example, multiple BSR tables can be defined in, for example, a wireless standard and known to the base station and the UE. In other examples, the base station can provide the UE with configurations of multiple BSR tables. For example, the base station can provide the UE with RRC configurations or multiple BSR tables with different characteristics. In one aspect, each BSR table can be associated with an LCG group. For example, a BSR table can be mapped to an LCG group according to the [LCGx, BSRTablex] model, where BSRTablex refers to the BSR table associated with LCGx. A default table (e.g., defined and / or configured) can be provided for a non-specific LCG (e.g., an LCG that does not have a mapping to a specific BSR table). In another example, each BSR table can be associated with a specific flow (e.g., a QoS flow). In some examples, different BSR tables can be provided for different DRBs, and the BSR for each LC in an LCG can use the same BSR table. The UE can then use a specific BSR table from the multiple BSR tables to report a BSR to the network based on the LCG group, flow, and / or DRB for which the BSR is to be reported.

[0088] In some aspects, a method for BSR configuration enhancement may include a MAC-CE based switching mechanism that provides an indication to the UE to select between different BSR tables (or a default BSR table). The indication may be based on whether a cell group (CG) or CC is enabled or disabled (or has an activation / deactivation state), which may dynamically change the UL RB mapping (e.g., secondary cell group (SCG) to primary cell group (MCG) or repeated disabling) and throughput / grant mode. In some aspects, the MCG may be referred to as a primary cell group. As an example, if the UE receives a MAC-CE activating a first CG, the UE may use a first BSR table. If the UE subsequently receives a MAC-CE activating a second CG and / or deactivating the first CG, the UE may use a second BSR table. Similarly, the UE may switch between BSR tables in response to a MAC-CE activating or deactivating a CC. The UE may then use the selected (or indicated) BSR table to provide a BSR to the network.

[0089] In some aspects, methods for BSR configuration enhancements may include additional retransmission (ReTx) BSR timers and other timer mechanisms, such as periodic BSR timers and SR delay timers that allow different BSR operations for different LCGs or flows. For example, a UE may receive configuration of BSR timers that are specific to an LCG. As an example, an LCG-specific BSR timer allows the UE to send BSR retransmissions for a higher priority LCG faster than BSR retransmissions for a lower priority LCG. As another example, the timer may be flow-specific such that the UE may send BSR retransmissions for higher priority flows (e.g., flows associated with video calls or other over-the-top (OTT) applications) faster than BSR retransmissions for lower priority flows.

[0090] In some aspects, the BSR table may be PDU session specific, link specific, or SCS specific. For example, different PDU sessions (e.g., Internet PDU sessions and on-demand PDU sessions) may have different URSP rules or support for BW slicing, different links (e.g., links associated with TN or NTN connections) may have different latencies and associated paths, and different SCSs (e.g., FR1 and FR2) may have different latencies and coverage / load issues. A corresponding BSR table for a specific PDU session, link, or SCS may allow the UE to provide more accurate information to the network than a single BSR table covering all PDU sessions, links, and SCSs. The UE may select a BSR table and / or timer from multiple BSR tables and / or timers based on the PDU session, link, and / or SCS. The UE may then use the selected BSR table to report the BSR to the network.

[0091] In some aspects, the UE may switch between BSR tables (or switch to a default BSR table) based on MAC-CE, as described above. For example, switching between BSR tables may be triggered based on a MAC-CE that enables / disables or activates / deactivates a CG or CC, which may dynamically change the UL RB mapping (e.g., SCG to MCG or repeated disablement) and throughput / grant mode. For example, the UE may receive a configuration for multiple cell groups, for example, in RRC signaling, and may activate or enable one or more of the configured cell groups for use by the UE via activation signaling in MAC-CE. Similarly, multiple CCs may be configured for the UE, and one or more of the configured CCs may be activated or enabled for the UE in MAC-CE. The UE may select a BSR table from a set of multiple BSR tables based on the status of one or more CGs and / or CCs.

[0092] Since SCG can be enabled or disabled for a UE via a MAC-CE sent by the network to the UE, the overall latency and link characteristics may change (for example, if the SCG is in FR2 and the MCG is in FR1, or if the SCG and MCG have different SCSs, etc.), and the BSR table configuration can be dynamically changed based on whether the data service goes through the MCG alone, the SCG alone, or is split across the SCG, for example, as used by the UE.

[0093] For example, when traffic passes through the MCG, the UE may use a different BSR table to report the BSR to the network (compared to the BSR table when the SCG is enabled). When the number of CCs enabled / disabled for the UE within a carrier group changes based on the MAC-CE method, the effective BW availability may change, and the UE may use a different BSR table configuration in response to (e.g., dynamically) the associated latency requirements. Additionally, MAC-CE-based duplication enablement / disablement may change the traffic pattern, and the UE may use a different BSR table based on the changed duplication enablement / disablement.

[0094] In some aspects of the present disclosure, the UE may use a BSR specific timer. The BSR specific timer may include any of a ReTxBSR timer, a periodic BSR timer, or a SR delay timer. In some aspects, the BSR specific timer may be LCG specific such that a higher priority LCG may result in faster BSR retransmissions compared to a lower priority LCG. For example, in two LCGs with different priorities (e.g., a first LCG has a higher priority than a second LCG), each of the two LCGs may have its own ReTx BSR timer, and the ReTx BSR timer for the higher priority LCG (e.g., the first LCG) may be shorter than the ReTx BSR timer for the lower priority LCG (e.g., the second LCG).

[0095] Since an LCG may include multiple LCs, and a UE may be associated with different LCGs based on priority logic, different timers expiring with lower or higher values may help enable differentiated behaviors based on service characteristics. For example, a first DRB (or LC, LCG) may have default Internet service (background (BG) service), while a second DRB (or LC, LCG) may have 5G New Radio Voice (VoNR) service. Since VoNR may be sensitive to latency, a smaller ReTx BSR timer associated with the second DRB (or LC, LCG) compared to the first DRB (or LC, LCG) may help send a BSR request for admission management of VoNR service that is faster than Internet service (BG service).

[0096] In some aspects, BSR-specific timers can be flow-specific, such that higher priority flows can result in faster BSR retransmissions compared to lower priority flows. For example, some applications (e.g., video calls or other OTT applications) can be assigned a higher priority than other applications, and the BSR timers corresponding to the higher priority applications can be shorter than the BSR timers used for other applications. When higher priority application (e.g., video calls / OTT) flows exist along with other Internet BG services mapped to the default DRB, the shorter BSR timers associated with these applications can help to quickly notify the network to ensure that the video call or OTT service receives better latency than the BG service.

[0097] Another aspect of the present disclosure provides a PDU session-specific BSR table, such as a BSR table associated with a specific PDU session. Different types of services may have different PDU sessions, such as a default PDU session and an on-demand PDU session. Each PDU session may be associated with a service type. The network may provide different PDU session options based on service type, such as Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4 and IPv6 (IPv4v6), Ethernet (ETH) service, or unstructured service. Using multiple BSR tables (e.g., a BSR table corresponding to one PDU session) for different service types can improve BSR reporting. For example, the default Internet service (IPV4) may pass through PDU session 1, while the ETH service may pass through PDU session 2. The two PDU sessions may have different service requirements in an application, and using a single BSR table to cover the two PDU sessions may not serve either of the two PDU sessions well. As proposed in this article, two BSR tables can be provided, one corresponding to PDU session 1 (for IPv4 services) and the other corresponding to PDU session 2 (for ETH services), which enables more targeted BSR reporting for the corresponding types of services.

[0098] In addition, different PDU sessions can have different URSP rules or slice BW support (e.g., slice types and slice instances for extended service level agreements (SLAs)). The network can provide enhanced mobile broadband (eMBB) / ultra-reliable low latency communication (URLLC) / massive machine type communication (mMTC) as options for different types of slice types, and also create various instances of slices with slice IDs (e.g., via the Single Network Slice Selection Assistance Information [S-NSSAI] mechanism). In addition, different slices can provide different QoS provisions to the core network at the E2E service level between applications, thereby reserving resources across entities. In these cases, multiple BSR tables can be provided, each corresponding to a PDU session. For example, different BSR tables can be provided based on the characteristics of the PDU session. These characteristics may include the service target of the PDU session, the QoS requirements of the PDU session, the business type characteristics of the PDU session, the slice requirements and URSP rules associated with the PDU session, and the slice instance and / or slice type associated with the PDU session.

[0099] Another aspect of the present disclosure relates to link-specific or SCS-specific BSR tables. Different types of links, such as TN connections and NTN connections, may have different latencies and different associated paths. For example, a TN network may have a shorter latency or round trip time (RTT) than an NTN network (although certain types of HAPS may have comparable latency). Timing advance (TA) logic and some other advanced mechanisms may be required to compensate for the NTN aspects. Due to the fine granularity and code point variations of different links, it may be helpful to have different BSR tables based on the characteristics of the link. For example, different BSR tables may be provided based on the characteristics of the link. These characteristics may include the connection type of the link, such as whether the link is for a TN connection or an NTN connection. As an example, an NTN connection may include a satellite or other airborne network equipment in the communication path. As an example, Figure 1 An example of an NTN 170 device is shown. In addition, if the connection type of the link is an NTN connection, the characteristics of the link may also include a delay associated with the NTN connection; a link capacity associated with the NTN connection; and additional NTN connection characteristics, which may include: a complete base station associated with the NTN connection, a reflector or repeater associated with the NTN connection, or a core network associated with the NTN connection.

[0100] In some aspects, the BSR table can be SCS specific. For example, different frequency bands (such as FR1 and FR2) can have different latency and coverage / load issues. For example, FR1 cells are generally designed for greater coverage and non-peak rate purposes, while FR2 cells are designed for greater capacity and peak rate purposes. In addition, FR2 cells can have higher BW and better SNR characteristics compared to their FR1 counterparts, but with limited coverage and reduced UE load. Therefore, having different BSR tables based on SCS aspects and associated functions can help differentiate service capabilities. For example, different BSR tables can be provided based on the SCS characteristics of the connection. These characteristics can include the frequency band used for the connection. The frequency band can be one of the FR1 band, the FR2 band, or the FR2+ band.

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

[0102] like Figure 7 As shown, at 706, UE 702 may receive a BSR configuration signal from base station 704. The BSR configuration signal may specify multiple BSR tables and multiple sets of one or more timers for the UE. Each of the multiple BSR tables may be specific to various characteristics of the communication between UE 702 and base station 704. For example, each of the multiple BSR tables may be specific to one or more of an LCG, a flow, a PDU session, a link, and an SCS. Each of the one or more timers may be specific to one or more of an LCG and a flow.

[0103] At 708, the UE 702 may obtain a plurality of BSR tables (e.g., as defined or received in a configuration, e.g., at 709) and a plurality of sets of one or more timers. Each of the plurality of BSR tables may correspond to one of the plurality of LCGs. For example, at 706, the UE 702 may obtain a plurality of BSR tables and a plurality of sets of one or more timers based on a BSR configuration signal received from the base station 704. In some examples, the plurality of BSR tables may be configured according to a plurality of PDU sessions. For example, referring to Figure 6 , the UE may receive configurations of three BSR tables corresponding to three PDU sessions (eg, Internet PDU, streaming video PDU, and IMS PDU), respectively.

[0104] At 709 , UE 702 may receive configurations for multiple BSR tables and multiple sets of one or more timers.

[0105] At 710, UE 702 may receive an indication for selecting a BSR table from base station 704. The indication may be received via MAC-CE or RRC information.

[0106] At 712, the UE 702 may select a BSR table from the plurality of BSR tables. For example, a BSR table may be selected based on characteristics of the communication between the UE 702 and the base station 704. For example, referring to Figure 6 , the UE may obtain three BSR tables corresponding to three PDU sessions (eg, Internet PDU, streaming video PDU, and IMS PDU), and the UE may select the BSR table corresponding to the Internet PDU session for data associated with the Internet PDU session.

[0107] At 714, the UE 702 may select a set of timers from a plurality of sets of one or more timers. For example, the set of timers may be selected based on characteristics of the communication between the UE 702 and the base station 704. For example, referring to Figure 6 , each of the one or more timers can be associated with a DRB in a plurality of DRBs.

[0108] At 716, UE 702 may communicate with base station 704 based on a BSR table and a set of timers configured for the UE. Figure 6 When the UE 702 and the base station 704 transmit data associated with a specific application (e.g., a video stream), the UE 702 may communicate with the base station 704 based on a corresponding BSR table (e.g., a BSR table corresponding to an Internet PDU session) and a corresponding timer (e.g., a timer corresponding to DRB 2). As an example, the UE may send a BSR to the network using the selected BSR table and / or timer.

[0109] Figure 8 800 is a flowchart 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 Figure 12 UE 104, 350, 702, or apparatus 1204 in a hardware implementation. This method enables the UE to obtain multiple BSR tables and BSR timers and select the appropriate BSR table and timer based on the specific characteristics of the service. This method enables UL data transmission to be flexibly customized based on operational requirements. Therefore, it improves the efficiency of wireless communications.

[0110] like Figure 8As shown, at 802, the UE may obtain multiple sets of multiple BSR tables and one or more timers. Each of the multiple BSR tables may correspond to one of the multiple LCGs. The BSR may be configured from Figure 1 access network or core network components (e.g., base stations 102, 310, 704; or Figure 12 A network entity (eg, a base station or a component of a base station) in a network entity 1202 in a hardware implementation of the invention receives. Figure 7 Various aspects of the steps associated with flowchart 800 are shown. For example, referring to Figure 7 , UE 702 can obtain multiple BSR tables and multiple sets of one or more timers at 708. Each BSR table in the multiple BSR tables can correspond to an LCG in the multiple LCGs. In some aspects, 802 can be performed by BSR configuration component 198.

[0111] At 804, the UE may communicate with a network entity based on a BSR table selected from a plurality of BSR tables and a set of timers selected from a plurality of sets of one or more timers. Figure 7 , UE 702 may select a BSR table from a plurality of BSR tables at 712 and select a set of timers from a plurality of sets of one or more timers at 714. UE 702 may communicate with a network entity based on the BSR table and the set of timers at 716. For example, the UE may send a BSR based on the selected BSR table and / or timer. In some aspects, 804 may be performed by BSR configuration component 198.

[0112] Figure 9 900 is a flowchart 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 Figure 12 UE 104, 350, 702, or apparatus 1204 in a hardware implementation. This method enables the UE to obtain multiple BSR tables and BSR timers and select the appropriate BSR table and timer based on the specific characteristics of the service. This method enables UL data transmission to be flexibly customized based on operational requirements. Therefore, it improves the efficiency of wireless communications.

[0113] like Figure 9 As shown, at 902, the UE may obtain multiple sets of multiple BSR tables and one or more timers. Each of the multiple BSR tables may correspond to one of the multiple LCGs. The BSR may be configured from Figure 1 access network or core network components (e.g., base stations 102, 310, 704; or Figure 12A network entity (eg, a base station or a component of a base station) in a network entity 1202 in a hardware implementation of the invention receives. Figure 7 Various aspects of the steps associated with flowchart 900 are shown. For example, referring to Figure 7 , UE 702 can obtain multiple BSR tables and multiple sets of one or more timers at 708. Each BSR table in the multiple BSR tables can correspond to an LCG in the multiple LCGs. In some aspects, 902 can be performed by BSR configuration component 198.

[0114] At 906, the UE may communicate with the network entity based on a BSR table selected from a plurality of BSR tables and a set of timers selected from a plurality of sets of one or more timers. Figure 7 , UE 702 may select a BSR table from a plurality of BSR tables at 712 and select a set of timers from a plurality of sets of one or more timers at 714. UE 702 may communicate with a network entity based on the BSR table and the set of timers at 716. For example, the UE may send a BSR based on the selected BSR table and / or timer. In some aspects, 906 may be performed by BSR configuration component 198.

[0115] In some aspects, the selection of a BSR table may be based on an indication received via MAC-CE or RRC information. For example, Figure 7 , UE 702 may receive an indication at 710 from base station 704. The indication may be received via MAC-CE or RRC information, and UE 702 may select a BSR table based on the indication at 712.

[0116] In some aspects, the selection of a BSR table may be based on one or more of the following: CG information (911); the number of CCs enabled or disabled on the CG (912); LCG service type (913); streaming service type (914); the presence of PDCP duplication (915); or enabled or disabled segmentation configuration (916). LCG service type (913) may refer to a service type within an LCG. For example, LCG service type (913) may include voice service, video service, data service, etc. Streaming service type (914) may refer to a service type based on the characteristics of a flow. For example, streaming service type (914) may include real-time service, streaming service, etc. For example, referring to Figure 7 When UE 702 selects a BSR table at 712, a BSR table may be selected based on one or more of: CG information; the number of CCs enabled or disabled on the CG; LCG service type; flow service type; the presence of PDCP duplication; or enabled or disabled split configuration.

[0117] In some aspects, the selection of a BSR table can be based on CG information (911), which includes one or more of the following: use of MCG, use of SCG, or use of dual connectivity (DC) mechanism. For example, referring to Figure 7 When the UE 702 selects a BSR table at 712, the BSR table may be selected based on CG information including one or more of the following: use of MCG, use of SCG, or use of DC mechanism.

[0118] In some aspects, the multiple sets of one or more timers may include one or more of the following: a periodic BSR timer (921), a retransmission BSR timer (922), or an SR delay timer (923). For example, referring to Figure 7 When the UE 702 obtains multiple sets of one or more timers at 708, the multiple sets of one or more timers may include one or more of the following: a periodic BSR timer, a retransmission BSR timer, or an SR delay timer.

[0119] In some aspects, at 904, the UE may receive configurations for multiple sets of multiple BSR tables and one or more timers. The configurations may be based on one or more of: LCG traffic type (931); stream traffic type (932); or DRBs associated with data (933). For example, referring to Figure 7 When UE 702 obtains multiple BSR tables and multiple sets of one or more timers at 708, UE 702 may receive configurations for multiple BSR tables and multiple sets of the one or more timers at 709. The configuration may be based on one or more of the following: LCG service type; streaming service type; or DRB associated with data. For example, referring to Figure 6 , the UE may obtain a timer for each DRB (eg, DRB 1, DRB 2, ..., DRB 5). In some aspects, 904 may be performed by BSR configuration component 198.

[0120] In some aspects, at 904, the UE may receive configurations for multiple sets of multiple BSR tables and one or more timers. The configurations may be based on characteristics of multiple PDU sessions (934). For example, referring to Figure 7 When the UE 702 obtains multiple BSR tables and multiple sets of one or more timers at 708, the UE 702 may receive configurations for multiple BSR tables and multiple sets of one or more timers based on characteristics of multiple PDU sessions. Figure 6, the UE can obtain a BSR table for each PDU session (e.g., Internet PDU, streaming video PDU, and IMS PDU).

[0121] In some aspects, the characteristics of the multiple PDU sessions on which the multiple sets of BSR tables and one or more timers are based may include at least one of the following: service targets for the multiple PDU sessions; QoS requirements for the multiple PDU sessions; traffic type characteristics for the multiple PDU sessions; slice requirements and URSP rules associated with the multiple PDU sessions; or at least one of slice instances or slice types associated with the multiple PDU sessions. For example, referring to Figure 6 The UE can obtain the BSR table based on the service objectives of multiple PDU sessions (for example, the Internet PDU or streaming video PDU described above). In addition, the UE can also obtain the BSR table based on the QoS requirements of multiple PDU sessions (for example, one BSR table for each QoS flow 1, QoS flow 2, ..., QoS flow 6) or the service type characteristics of multiple PDU sessions (for example, one BSR table for video applications and one BSR table for streaming video flows).

[0122] In some aspects, the multiple sets of BSR tables and one or more timers may be based on a service target for the multiple PDU sessions. The service targets for the multiple PDU sessions may include one or more of: an Internet PDU session or an on-demand PDU session. For example, referring to Figure 6 , multiple BSR tables and one or more timers can be based on service targets of multiple PDU sessions, which can include one or more Internet PDU sessions (e.g., PDU sessions for video applications) or on-demand PDU sessions (e.g., streaming video PDUs).

[0123] In some aspects, the multiple sets of BSR tables and one or more timers may be based on the traffic type characteristics of the multiple PDU sessions. The traffic type characteristics of the PDU sessions may include one or more of the following: IPv4, IPv6, IPv4v6, ETH traffic, or unstructured traffic. For example, referring to Figure 7 When the UE 702 obtains multiple BSR tables and multiple sets of one or more timers at 708, the multiple BSR tables and the multiple sets of one or more timers may be based on service type characteristics of the multiple PDU sessions, which may include one or more of the following: IPv4, IPv6, IPv4v6, ETH service, or unstructured service.

[0124] In some aspects, at 904, the UE may receive configurations for multiple sets of multiple BSR tables and one or more timers based on characteristics of a link between the UE and a network entity (935). For example, referring to Figure 7 When UE 702 obtains multiple BSR tables and multiple sets of one or more timers at 708, UE 702 can receive configurations for multiple BSR tables and multiple sets of the one or more timers based on characteristics of the link between UE 702 and the network entity (base station 704) at 709.

[0125] In some aspects, the multiple sets of BSR tables and one or more timers can be based on the characteristics of the link. The characteristics of the link can include: the connection type of the link. The connection type can be a TN connection or an NTN connection. For example, referring to Figure 7 When UE 702 obtains multiple BSR tables and multiple sets of one or more timers at 708, the multiple BSR tables and multiple sets of one or more timers may be based on characteristics of the link. The characteristics of the link may include a connection type of the link, which may be a TN connection or an NTN connection.

[0126] In some aspects, the connection type of the link can be an NTN connection, and the multiple sets of multiple BSR tables and one or more timers can be based on characteristics of the link. The characteristics of the link can also include one or more of the following: a latency associated with the NTN connection; a link capacity associated with the NTN connection; and NTN connection characteristics. The NTN connection characteristics can include: a complete base station associated with the NTN connection, a reflector or repeater associated with the NTN connection, or a complete network associated with the NTN connection. For example, referring to Figure 7 UE 702 may obtain multiple BSR tables and multiple sets of one or more timers based on characteristics of the link at 708. The link may be an NTN connection, and the characteristics of the link may include one or more of the following: latency associated with the NTN connection; link capacity associated with the NTN connection; and NTN connection characteristics. The NTN connection characteristics may include: a complete base station associated with the NTN connection, a reflector or repeater associated with the NTN connection, or a complete network associated with the NTN connection.

[0127] In some aspects, the connection type of the link may be a TN connection or an NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of one or more timers are based may also include SCS characteristics within the connection. Figure 7UE 702 may obtain multiple BSR tables and multiple sets of one or more timers based on the connection type of the link and the characteristics of the link at 708. The connection type of the link may be a TN connection or an NTN connection, and the characteristics of the link may include SCS characteristics within the connection.

[0128] In some aspects, the connection type of the link can be a TN connection or an NTN connection, and the characteristics of the link based on the multiple BSR tables and the multiple sets of one or more timers can also include: a frequency band used for the connection. The frequency band can include one of an FR1 frequency band, an FR2 frequency band, or an FR2+ frequency band. For example, referring to Figure 7 At 708, UE 702 may obtain multiple BSR tables and multiple sets of one or more timers based on the connection type and characteristics of the link. The connection type of the link may be a TN connection or an NTN connection. The characteristics of the link may include a frequency band used for the connection. The frequency band may include one of an FR1 band, an FR2 band, or an FR2+ band.

[0129] Figure 10 1 is a flow chart 1000 illustrating a wireless communication method 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 access network or core network components (e.g., base stations 102, 310, 704; or Figure 12 The method includes a base station or a base station component in a network entity 1202 in a hardware implementation. This method enables a UE to obtain multiple BSR tables and BSR timers and select the appropriate BSR table and timer based on the specific characteristics of the service. This method enables UL data transmission to be flexibly customized based on operational requirements. Therefore, it improves the efficiency of wireless communications.

[0130] like Figure 10 As shown, at 1002, the network entity may provide an indication to the UE for the UE to select a BSR table from a plurality of BSR tables and a set of one or more timers from a plurality of sets of one or more timers. Each BSR table in the plurality of BSR tables may correspond to an LCG in a plurality of LCGs. The UE may be Figure 12 UE 104 , 350 , 702 or device 1204 in a hardware implementation of . Figure 7 Various aspects of the steps associated with flowchart 1000 are shown. For example, referring to Figure 7, the network entity (base station 704) may send an indication (BSR configuration signal) to UE 702 at 706 to cause UE 702 to select (at 712) a BSR table from a plurality of BSR tables configured for UE 702 and to select (at 714) a set of one or more timers from a plurality of sets of one or more timers. Each BSR table in the plurality of BSR tables may correspond to one LCG in the plurality of LCGs. In some aspects, 1002 may be performed by BSR configuration component 199.

[0131] At 1004, the network entity may communicate with the UE based on a BSR table and a set of one or more timers indicated for the UE. Figure 7 The network entity (base station 704) can communicate with the UE 702 based on a set of a BSR table and timers at 716. In some aspects, 1004 can be performed by the BSR configuration component 199.

[0132] Figure 11 1 is a flow chart 1100 illustrating a wireless communication method 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 access network or core network components (e.g., base stations 102, 310, 704; or Figure 12 The method includes a base station or a base station component in a network entity 1202 in a hardware implementation. This method enables a UE to obtain multiple BSR tables and BSR timers and select the appropriate BSR table and timer based on the specific characteristics of the service. This method enables UL data transmission to be flexibly customized based on operational requirements. Therefore, it improves the efficiency of wireless communications.

[0133] like Figure 11 As shown, at 1102, the network entity may provide an indication to the UE for the UE to select a BSR table from a plurality of BSR tables and a set of one or more timers from a plurality of sets of one or more timers. Each BSR table in the plurality of BSR tables may correspond to an LCG in a plurality of LCGs. The UE may be Figure 12 UE 104 , 350 , 702 or device 1204 in a hardware implementation of . Figure 7 Various aspects of the steps associated with flowchart 1100 are shown. For example, referring to Figure 7, the network entity (base station 704) may send an indication (BSR configuration signal) to UE 702 at 706 to cause UE 702 to select (at 712) a BSR table from a plurality of BSR tables configured for UE 702 and to select (at 714) a set of one or more timers from a plurality of sets of one or more timers. Each BSR table in the plurality of BSR tables may correspond to one LCG in the plurality of LCGs. In some aspects, 1102 may be performed by BSR configuration component 199.

[0134] At 1106, the network entity may communicate with the UE based on a BSR table and a set of one or more timers indicated for the UE. Figure 7 The network entity (base station 704) can communicate with the UE 702 based on a set of a BSR table and timers at 716. In some aspects, 1106 can be performed by the BSR configuration component 199.

[0135] In some aspects, the indication may be included in a MAC-CE or RRC message. For example, see Figure 7 , the network entity may send an indication to the UE 702 at 710. The indication may be sent via MAC-CE or RRC information.

[0136] In some aspects, the selection of a BSR table can be based on one or more of: CG information (1111); number of CCs enabled or disabled on the CG (1112); LCG service type (1113); flow service type (1114); presence of PDCP duplication (1115); or enabled or disabled segmentation configuration (1116). For example, referring to Figure 7 When UE 702 selects a BSR table at 712, the BSR table may be selected based on one or more of the following: CG information; the number of CCs enabled or disabled on the CG; LCG service type; flow service type; the presence of PDCP duplication; or enabled or disabled split configuration.

[0137] In some aspects, the CG information may include one or more of the following: use of MCG, use of SCG, or use of DC mechanism. Figure 7 When the UE 702 selects a BSR table at 712, the BSR table may be selected based on CG information including one or more of the following: use of MCG, use of SCG, or use of DC mechanism.

[0138] In some aspects, the plurality of sets of one or more timers may include one or more of the following: a periodic BSR timer (1121), a retransmission BSR timer (1122), or an SR delay timer (1123). For example, referring to Figure 7 When the UE 702 obtains multiple sets of one or more timers at 708, the multiple sets of one or more timers may include one or more of the following: a periodic BSR timer, a retransmission BSR timer, or an SR delay timer.

[0139] In some aspects, at 1104, the network entity may send configurations for multiple sets of multiple BSR tables and one or more timers based on one or more of: LCG traffic type (1131); flow traffic type (1132); or RBs associated with data (1133). For example, referring to Figure 7 When the UE 702 obtains multiple BSR tables and multiple sets of one or more timers at 708, the network entity (base station 704) may send configurations for the multiple BSR tables and multiple sets of one or more timers at 709 based on one or more of the following: LCG service type; flow service type; or DRB associated with data. For example, referring to Figure 6 , the UE may obtain a timer for each DRB (eg, DRB 1, DRB 2, ..., DRB 5). In some aspects, 1104 may be performed by BSR configuration component 199.

[0140] In some aspects, at 1104, the network entity may send configurations for multiple sets of multiple BSR tables and one or more timers based on characteristics of the multiple PDU sessions (1134). For example, referring to Figure 7 When the UE 702 obtains multiple BSR tables and multiple sets of one or more timers at 708, the network entity (base station 704) may send configurations for multiple BSR tables and multiple sets of one or more timers based on the characteristics of multiple PDU sessions at 709. For example, referring to Figure 6 , the UE can obtain a BSR table for each PDU session (e.g., Internet PDU, streaming video PDU, and IMS PDU).

[0141] In some aspects, the characteristics of the multiple PDU sessions may include at least one of: a service target for the multiple PDU sessions; a QoS requirement for the multiple PDU sessions; a traffic type characteristic for the multiple PDU sessions; a slice requirement and URSP rule associated with the multiple PDU sessions; or at least one of a slice instance or a slice type associated with the multiple PDU sessions. For example, referring to Figure 6The UE can obtain the BSR table based on the service objectives of multiple PDU sessions (for example, Internet PDU or streaming video PDU); QoS requirements (for example, one BSR table for QoS flow 1, QoS flow 2, ..., QoS flow 6); and service type characteristics of multiple PDU sessions (for example, one BSR table for voice applications and one BSR table for streaming video streams).

[0142] In some aspects, the service targets of the plurality of PDU sessions include one or more of the following: an Internet PDU session or an on-demand PDU session. Figure 6 , multiple BSR tables and one or more timers can be based on service targets of multiple PDU sessions, which can include one or more Internet PDU sessions (e.g., PDU sessions for video applications) or on-demand PDU sessions (e.g., streaming video PDUs).

[0143] In some aspects, the traffic type characteristics of the multiple PDU sessions on which the multiple BSR tables and the multiple sets of one or more timers are based include one or more of the following: IPv4, IPv6, IPv4v6, ETH traffic, or unstructured traffic. For example, referring to Figure 7 When the UE 702 obtains multiple BSR tables and multiple sets of one or more timers at 708, the multiple BSR tables and the multiple sets of one or more timers may be based on service type characteristics of the multiple PDU sessions, which may include one or more of the following: IPv4, IPv6, IPv4v6, ETH service, or unstructured service.

[0144] In some aspects, at 1104, the network entity may send configurations for multiple BSR tables and one or more timers based on characteristics of the link between the UE and the network entity (1135). For example, referring to Figure 7 When UE 702 obtains multiple BSR tables and multiple sets of one or more timers at 708, the network entity (base station 704) may send configurations for multiple BSR tables and multiple sets of the one or more timers at 709 based on characteristics of a link between UE 702 and the network entity (base station 704).

[0145] In some aspects, the characteristics of the link on which the multiple BSR tables and the multiple sets of one or more timers are based may include a connection type of the link, which may be a TN connection or an NTN connection. Figure 7When UE 702 obtains multiple BSR tables and multiple sets of one or more timers at 708, the multiple BSR tables and multiple sets of one or more timers may be based on characteristics of the link. The characteristics of the link may include a connection type of the link, which may be a TN connection or an NTN connection.

[0146] In some aspects, the connection type of the link can be an NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of one or more timers are based further include one or more of the following: a delay associated with the NTN connection; a link capacity associated with the NTN connection; or an NTN connection characteristic, which may include: a complete base station associated with the NTN connection, a reflector or repeater associated with the NTN connection, or a complete network associated with the NTN connection. For example, referring to Figure 7 UE 702 may obtain multiple BSR tables and multiple sets of one or more timers based on characteristics of the link at 708. The link may be an NTN connection, and the characteristics of the link may include one or more of the following: latency associated with the NTN connection; link capacity associated with the NTN connection; and NTN connection characteristics. The NTN connection characteristics may include: a complete base station associated with the NTN connection, a reflector or repeater associated with the NTN connection, or a complete network associated with the NTN connection.

[0147] In some aspects, the connection type of the link may be a TN connection or an NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of one or more timers are based may also include SCS characteristics within the connection type. Figure 7 UE 702 may obtain multiple BSR tables and multiple sets of one or more timers based on the connection type of the link and the characteristics of the link at 708. The connection type of the link may be a TN connection or an NTN connection, and the characteristics of the link may include SCS characteristics within the connection.

[0148] In some aspects, the connection type of the link can be a TN connection or an NTN connection, and the characteristics of the link based on the multiple BSR tables and the multiple sets of one or more timers can also include: a frequency band used for the connection. The frequency band can include one of an FR1 frequency band, an FR2 frequency band, or an FR2+ frequency band. For example, referring to Figure 7 At 708, UE 702 may obtain multiple BSR tables and multiple sets of one or more timers based on the connection type and characteristics of the link. The connection type of the link may be a TN connection or an NTN connection. The characteristics of the link may include a frequency band used for the connection. The frequency band may include one of an FR1 band, an FR2 band, or an FR2+ band.

[0149] Figure 12FIG1200 is a diagram illustrating an example of a hardware implementation for an apparatus 1204. The apparatus 1204 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1204 may include at least one cellular baseband processor (or processing circuit) 1224 (also referred to as a modem) coupled to one or more transceivers 1222 (e.g., a cellular RF transceiver). The cellular baseband processor (or processing circuit) 1224 may include at least one on-chip memory (or memory circuit) 1224′. In some aspects, the apparatus 1204 may also include one or more subscriber identity module (SIM) cards 1220 and at least one application processor (or processing circuit) 1206 coupled to a secure digital (SD) card 1208 and a screen 1210. The application processor (or processing circuit) 1206 may include on-chip memory (or memory circuit) 1206′. In some aspects, the device 1204 may further include a Bluetooth module 1212, a WLAN module 1214, an SPS module 1216 (e.g., a GNSS module), one or more sensor modules 1218 (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 1226, a power supply 1230, and / or a camera 1232. The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include their own dedicated antennas and / or utilize antenna 1280 for communication. The cellular baseband processor (or processing circuit) 1224 communicates with the UE 104 and / or RUs associated with the network entity 1202 via one or more antennas 1280 via the transceiver 1222. The cellular baseband processor (or processing circuit) 1224 and the application processor (or processing circuit) 1206 may each include computer-readable media / memory (or memory circuit) 1224', 1206', respectively. The additional memory module 1226 may also be considered a computer-readable medium / memory (or memory circuit). Each computer-readable medium / memory (or memory circuit) 1224', 1206', 1226 may be non-transitory. The cellular baseband processor (or processing circuit) 1224 and the application processor (or processing circuit) 1206 are each responsible for general processing, including executing software stored on the computer-readable medium / memory (or memory circuit).The software, when executed by cellular baseband processor (or processing circuitry) 1224 / application processor (or processing circuitry) 1206, causes cellular baseband processor (or processing circuitry) 1224 / application processor (or processing circuitry) 1206 to perform the various functions described above. Cellular baseband processor (or processing circuitry) 1224 and application processor (or processing circuitry) 1206 are configured to perform the various functions described above based, at least in part, on information stored in memory (or memory circuitry). That is, cellular baseband processor(s) (or processing circuitry) 1224 and application processor(s) (or processing circuitry) 1206 can be configured to perform a first subset of the various functions described above without requiring information stored in memory, and can be configured to perform a second subset of the various functions described above based on information stored in memory. Computer-readable media / memory (or memory circuitry) can also be used to store data manipulated by cellular baseband processor (or processing circuitry) 1224 / application processor (or processing circuitry) 1206 when executing the software. The cellular baseband processor (or processing circuit) 1224 / application processor (or processing circuit) 1206 may be a component of the UE 350 and may include at least one memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1204 may be at least one processor chip (modem and / or applications) and include only the cellular baseband processor (or processing circuit) 1224 and / or the application processor (or processing circuit) 1206, and in another configuration, the apparatus 1204 may be the entire UE (e.g., see. Figure 3 UE 350) and includes additional modules of device 1204.

[0150] As described above, component 198 can be configured to obtain a plurality of BSR tables and one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to an LCG in the plurality of LCGs; select a BSR table from the plurality of BSR tables; select a timer set from the one or more timers; and communicate with a network entity based on a BSR table and a timer set. Component 198 can also be configured to perform a combination of Figure 8 and Figure 9 The flowchart described in and / or Figure 71204. Component 198 may be within the cellular baseband processor(s) (or processing circuits) 1224, the application processor(s) (or processing circuits) 1206, or both the cellular baseband processor(s) (or processing circuits) 1224 and the application processor(s) (or processing circuits) 1206. Component 198 may be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the 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 process / algorithm individually or in combination. As shown, apparatus 1204 may include various components configured for various functions. In one configuration, the apparatus 1204, and in particular the cellular baseband processor(s) (or processing circuits) 1224 and / or the application processor(s) (or processing circuits) 1206, includes: means for obtaining a plurality of BSR tables and one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to an LCG in a plurality of LCGs; means for selecting a BSR table from the plurality of BSR tables; means for selecting a timer set from the one or more timers; and means for communicating with a network entity based on the BSR table and the timer set. The apparatus 1204 may also include means for performing a BSR table in conjunction with Figure 8 and Figure 9 The aspects described in the flowcharts and / or by Figure 7 The means may be a component 198 of the apparatus 1204 configured to perform the functions recited by the means. As described above, the apparatus 1204 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the means.

[0151] Figure 13Figure 1300 illustrates an example of a hardware implementation for a network entity 1302. Network entity 1302 may be a base station (BS), a component of a BS, or may implement BS functionality. Network entity 1302 may include at least one of a CU 1310, a DU 1330, or a RU 1340. For example, depending on the layer functionality handled by component 199, network entity 1302 may include a CU 1310; both the CU 1310 and the DU 1330; each of the CU 1310, the DU 1330, and the RU 1340; the DU 1330; both the DU 1330 and the RU 1340; or the RU 1340. CU 1310 may include at least one CU processor (or processing circuitry) 1312. CU processor (or processing circuitry) 1312 may include on-chip memory (or memory circuitry) 1312′. In some aspects, CU 1310 may also include an additional memory module 1314 and a communication interface 1318. CU 1310 communicates with DU 1330 via an intermediate link, such as an F1 interface. DU 1330 may include at least one DU processor (or processing circuit) 1332′. DU processor (or processing circuit) 1332 may include on-chip memory (or memory circuit) 1332′. In some aspects, DU 1330 may further include an additional memory module 1334 and a communication interface 1338. DU 1330 communicates with RU 1340 via a fronthaul link. RU 1340 may include at least one RU processor (or processing circuit) 1342. RU processor (or processing circuit) 1342 may include on-chip memory (or memory circuit) 1342′. In some aspects, RU 1340 may also include an additional memory module 1344, one or more transceivers 1346, an antenna 1380, and a communication interface 1348. RU 1340 communicates with UE 104. On-chip memory (or memory circuit) 1312 ′, 1332 ′, 1342 ′ and additional memory modules 1314 , 1334 , 1344 can each be considered a computer-readable medium / memory (or memory circuit). Each computer-readable medium / memory (or memory circuit) can be non-transitory. Each of the processors (or processing circuits) 1312 , 1332 , 1342 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 enables the processor (or processing 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.

[0152] As described above, component 199 may be configured to send a BSR configuration signal to the UE so that the UE selects a BSR table from a plurality of BSR tables configured for the UE and selects a timer set from one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to an LCG in a plurality of LCGs; and communicate with the UE based on a BSR table and a timer set configured for the UE. Component 199 may also be configured to perform a BSR configuration signal in conjunction with Figure 10 and Figure 11 The flowcharts described in and / or by Figure 7 Any of the aspects performed by the base station 704 in . Component 199 may be within one or more processors (or processing circuits) of one or more of the CU 1310, DU 1330, and RU 1340. Component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the 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 process / algorithm individually or in combination. The network entity 1302 may include various components configured for various functions. In one configuration, the network entity 1302 includes: a unit for sending a BSR configuration signal to the UE so that the UE selects a BSR table from a plurality of BSR tables configured for the UE and a timer set from one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to an LCG in a plurality of LCGs; and a unit for communicating with the UE based on a BSR table and a timer set configured for the UE. The network entity 1302 may also include a unit for performing a BSR configuration signal in conjunction with Figure 10 and Figure 11 The aspects described in the flowcharts and / or by Figure 7 13. The present invention relates to a base station 704 in the network entity 1302. The means may be a component 199 of the network entity 1302 configured to perform the functions recited by the means. As described above, the network entity 1302 may include at least one of the TX processor 316, the RX processor 370, and / or the controller / processor 375. As such, in one configuration, the means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the means.

[0153] The present disclosure provides a method for wireless communication at a UE. The method may include: configuring multiple BSR tables and one or more timers, wherein each BSR table in the multiple BSR tables corresponds to one of multiple LCGs; selecting a BSR table from the multiple BSR tables; selecting a timer set from the one or more timers; and communicating with a network entity based on the BSR table and the timer set. The method enables the UE to obtain multiple BSR tables and BSR timers and select the corresponding BSR table and timer based on the specific characteristics of the service. The method enables flexible customization of uplink (UL) data transmission based on operational requirements. Therefore, it improves the efficiency of wireless communication.

[0154] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is illustrative by way of example. Based on design preferences, it should be understood that the specific order or hierarchy of blocks in the process / flowchart may be rearranged. Furthermore, some blocks may be combined or omitted. The accompanying method claims provide elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0155] The above description is provided to enable any person skilled in the art to practice 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 can be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but are to be given the full scope consistent with the claim formulation. Unless otherwise specifically stated, reference to an element in the singular is not intended to mean "one and only one", but rather "one or more". Terms such as "if", "when", and "at the time of" do not imply a direct temporal relationship or reaction. That is, these phrases, such as "when", do not imply a reaction to an action or immediate action 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 action to occur. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any aspect described herein as "exemplary" is not necessarily interpreted as being preferred over or advantageous over other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. 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 and B,” 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 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, either individually or in any combination. Thus, each of the at least one processor can be configured to perform a specific subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty subset of the set. A processor can be referred to as a processor circuit. A memory / memory module can be referred to as a memory circuit. If a first device receives data from or sends data to a second device, the data can 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 data, a transmission, a signal, or a message can, for example, use a transceiver to send data, or can send data to a device that sends data.A device configured to "obtain" data, such as a transmission, signal, or message, may receive it, for example, using a transceiver, or may obtain the data from a device that receives the 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 or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is dedicated to the public, regardless of whether such disclosure is expressly recited in the claims. Words such as "module," "mechanism," "element," and "device" are not substitutes for the word "unit." As such, no claim element is to be construed as a functional module unless the element is explicitly recited using the phrase "unit for..."

[0156] 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, the phrase "based on A" (where "A" can be information, conditions, factors, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0157] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0158] Aspect 1 is a method for wireless communication at a UE. The method includes obtaining a plurality of BSR tables and a plurality of sets of one or more timers, wherein each of the plurality of BSR tables corresponds to an LCG from a plurality of LCGs; and communicating with a network entity based on a BSR table selected from the plurality of BSR tables and a timer set selected from the plurality of sets of one or more timers.

[0159] Aspect 2 is a method according to aspect 1, wherein the selection of the one BSR table may be based on an indication received via MAC-CE or RRC information.

[0160] Aspect 3 is a method according to any one of Aspects 1 to 2, wherein the selection of the one BSR table may be based on one or more of the following: CG information; the number of CCs enabled or disabled on the CG; LCG service type; flow service type; presence of PDCP duplication; or enabled or disabled split configuration.

[0161] Aspect 4 is a method according to aspect 3, wherein the selection of the one BSR table may be based on the CG information, and the CG information may include one or more of the following: using MCG, using SCG, or using DC mechanism.

[0162] Aspect 5 is a method according to any one of aspects 1 to 4, wherein the multiple sets of one or more timers may include one or more of the following: a periodic BSR timer, a retransmission BSR timer, or an SR delay timer.

[0163] Aspect 6 is a method according to any one of Aspects 1 to 5, wherein the method may further include: receiving a configuration for the set of the multiple BSR tables and the multiple one or more timers based on one or more of the following: LCG service type; streaming service type; or a radio bearer (RB) associated with data.

[0164] Aspect 7 is a method according to any one of aspects 1 to 5, wherein the method may further include: receiving configurations for the multiple BSR tables and multiple sets of the one or more timers based on characteristics of multiple PDU sessions.

[0165] Aspect 8 is a method according to Aspect 7, wherein the characteristics of the multiple PDU sessions on which the multiple BSR tables and the multiple sets of one or more timers are based include at least one of the following: service targets of the multiple PDU sessions; quality of service (QOS) requirements of the multiple PDU sessions; business type characteristics of the multiple PDU sessions; slice requirements and UE routing policy (URSP) rules associated with the multiple PDU sessions; or at least one of slice instances or slice types associated with the multiple PDU sessions.

[0166] Aspect 9 is a method according to Aspect 8, wherein the multiple BSR tables and the multiple sets of the one or more timers are based on the service targets of the multiple PDU sessions, and the service targets of the multiple PDU sessions include one or more of the following: Internet PDU sessions or on-demand PDU sessions.

[0167] Aspect 10 is a method according to Aspect 8, wherein the multiple BSR tables and the multiple sets of the one or more timers are based on the service type characteristics of the multiple PDU sessions, and the service type characteristics of the multiple PDU sessions include one or more of the following: IPv4, IPv6, IPv4v6, ETH service or unstructured service.

[0168] Aspect 11 is a method according to any one of Aspects 1 to 5, wherein the method further includes: receiving configurations for the multiple BSR tables and multiple sets of the one or more timers based on characteristics of the link between the UE and the network entity.

[0169] Aspect 12 is a method according to aspect 11, wherein the multiple BSR tables and the multiple sets of the one or more timers may be based on characteristics of the link, which may include a connection type of the link. The connection type may be a TN connection or an NTN connection.

[0170] Aspect 13 is a method according to aspect 12, wherein the connection type of the link may be the NTN connection. The multiple BSR tables and the multiple sets of the one or more timers may be based on characteristics of the link, which may include one or more of the following: a delay associated with the NTN connection; a link capacity associated with the NTN connection; and an NTN connection characteristic, which may include a complete base station associated with the NTN connection, a reflector or repeater associated with the NTN connection, or a complete network associated with the NTN connection.

[0171] Aspect 14 is a method according to Aspect 12, wherein the connection type of the link can be the TN connection or the NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of one or more timers are based can also include SCS characteristics of the connection type.

[0172] Aspect 15 is a method according to Aspect 12, wherein the connection type of the link can be the TN connection or the NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of the one or more timers are based can also include: a frequency band used for the connection type.

[0173] Aspect 16 is 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 processing system being configured to cause the UE to perform one or more of the methods described in aspects 1-15.

[0174] 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, and wherein the at least one processor is configured, alone or in any combination, to perform the method of any one of aspects 1-15.

[0175] Aspect 18 is an apparatus for wireless communication at a UE, comprising: a unit for obtaining a plurality of buffer status report (BSR) tables and a plurality of sets of one or more timers, wherein each of the plurality of BSR tables corresponds to a logical channel group (LCG) among a plurality of LCGs; and a unit for communicating with a network entity based on a BSR table selected from the plurality of BSR tables and a timer set selected from the plurality of sets of the one or more timers.

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

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

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

[0179] Aspect 22 is a method of wireless communication at a network entity. The method may include: providing an indication to a UE for the UE to select a BSR table from a plurality of BSR tables and a set of one or more timers from a plurality of sets of one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to an LCG in a plurality of LCGs; and communicating with the UE based on the one BSR table and the set of one or more timers indicated for the UE.

[0180] Aspect 23 is a method according to aspect 22, wherein the indication may be included in MAC-CE or RRC information.

[0181] Aspect 24 is a method according to any one of Aspects 22 to 23, wherein the selection of the one BSR table may be based on one or more of: CG information; the number of CCs enabled or disabled on the CG; LCG service type; flow service type; the presence of PDCP repetition; or enabled or disabled split configuration.

[0182] Aspect 25 is a method according to aspect 24, wherein the CG information may include one or more of the following: using MCG, using SCG, or using DC mechanism.

[0183] Aspect 26 is a method according to any one of aspects 22 to 25, wherein the multiple sets of one or more timers include one or more of the following: a periodic BSR timer, a retransmission BSR timer, or an SR delay timer.

[0184] Aspect 27 is a method according to any one of Aspects 22 to 26, wherein the method further includes: sending configurations for the multiple BSR tables and multiple sets of the one or more timers based on one or more of the following: LCG service type; flow service type; or RB associated with data.

[0185] Aspect 28 is a method according to any one of aspects 22 to 26, wherein the method further comprises: sending configurations for the multiple BSR tables and multiple sets of the one or more timers based on characteristics of multiple PDU sessions.

[0186] Aspect 29 is a method according to Aspect 28, wherein the characteristics of the multiple PDU sessions on which the multiple sets of the multiple BSR tables and the one or more timers are based include at least one of the following: service objectives of the multiple PDU sessions; QoS requirements of the multiple PDU sessions; business type characteristics of the multiple PDU sessions; slice requirements and URSP rules associated with the multiple PDU sessions; or at least one of slice instances or slice types associated with the multiple PDU sessions.

[0187] Aspect 30 is a method according to aspect 29, wherein the service targets of the plurality of PDU sessions may include one or more of the following: an Internet PDU session or an on-demand PDU session.

[0188] Aspect 31 is a method according to Aspect 29, wherein the service type characteristics of the multiple PDU sessions on which the multiple BSR tables and the multiple sets of one or more timers are based may include one or more of the following: IPv4, IPv6, IPv4v6, ETH service or unstructured service.

[0189] Aspect 32 is a method according to any one of aspects 22 to 27, wherein the method further includes: sending configurations for the multiple BSR tables and multiple sets of the one or more timers based on characteristics of the link between the UE and the network entity.

[0190] Aspect 33 is a method according to aspect 32, wherein the characteristics of the link on which the multiple BSR tables and the multiple sets of one or more timers are based may include: the connection type of the link, wherein the connection type may be a TN connection or an NTN connection.

[0191] Aspect 34 is a method according to aspect 33, wherein the connection type of the link may be the NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of the one or more timers are based may also include one or more of the following: the delay associated with the NTN connection; the link capacity associated with the NTN connection; or NTN connection characteristics, which include: a complete base station associated with the NTN connection, a reflector or repeater associated with the NTN connection, or a complete network associated with the NTN connection.

[0192] Aspect 35 is a method according to Aspect 33, wherein the connection type of the link can be the TN connection or the NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of the one or more timers are based can also include SCS characteristics within the connection type.

[0193] Aspect 36 is a method according to Aspect 33, wherein the connection type of the link can be the TN connection or the NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of the one or more timers are based can also include: the frequency band used for the connection.

[0194] Aspect 37 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 processing system being configured to cause the network entity to perform one or more of the methods described in aspects 22-36.

[0195] Aspect 38 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 the method of any one of aspects 22-36.

[0196] Aspect 39 is an apparatus for wireless communication at a network entity, comprising: a unit for providing an indication to a user equipment (UE) for the UE to select a buffer status report (BSR) table from a plurality of BSR tables and a set of one or more timers from a plurality of sets of one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to one logical channel group (LCG) in a plurality of LCGs; and a unit for communicating with the UE based on the one BSR table and the set of one or more timers indicated for the UE.

[0197] Aspect 40 is the apparatus according to aspect 39, further comprising: a unit for performing each step of the method according to any one of aspects 23-36.

[0198] Aspect 41 is an apparatus according to any one of aspects 37-40, further comprising: a transceiver configured to receive or transmit in association with the method of any one of aspects 22-36.

[0199] Aspect 42 is a computer-readable medium (e.g., a non-transitory computer-readable medium) that stores computer-executable code at a network entity, which, when executed by at least one processor, causes the at least one processor to perform the method of any one of Aspects 22-36, 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 configured, individually or in combination, to cause the UE to: Obtaining a plurality of buffer status report (BSR) tables and a plurality of sets of one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to one of a plurality of logical channel groups (LCGs); as well as Communicating with a network entity is performed based on a BSR table selected from the plurality of BSR tables and a timer set selected from the plurality of sets of one or more timers.

2. The apparatus of claim 1 , further comprising a transceiver coupled to the at least one processor, wherein The at least one processor is configured, individually or in combination, to cause the UE to communicate with the network entity via the transceiver, and wherein selecting the one BSR table is based on an indication received via a Medium Access Control-Control Element (MAC-CE) or a Radio Resource Control (RRC) message.

3. The device according to claim 2, wherein The selecting of the one BSR table is based on one or more of the following: Cell Group (CG) information; The number of component carriers (CCs) enabled or disabled on the CG; LCG business type; Streaming service type; There is a Packet Data Convergence Protocol (PDCP) duplication; or Enable or disable split configuration.

4. The device according to claim 3, wherein The selecting of the one BSR table is based on the CG information including one or more of the following: Using Master Cell Group (MCG), Use a Secondary Cell Group (SCG), or Use the Dual Connection (DC) mechanism.

5. The device according to claim 1, wherein The plurality of sets of one or more timers include one or more of the following: Periodic BSR timer, Retransmit BSR timer, or Scheduling Request (SR) delay timer.

6. The device according to claim 1, wherein The at least one processor, alone or in combination, is further configured to cause the UE to: Receiving configurations for the plurality of BSR tables and the plurality of sets of the one or more timers based on one or more of: LCG business type; Streaming service type; or A radio bearer (RB) associated with data.

7. The device according to claim 1, wherein The at least one processor, alone or in combination, is further configured to cause the UE to: Configurations for the plurality of BSR tables and the plurality of sets of one or more timers are received based on characteristics of a plurality of protocol data unit (PDU) sessions.

8. The device according to claim 7, wherein The characteristics of the plurality of PDU sessions on which the plurality of BSR tables and the plurality of sets of the one or more timers are based include at least one of the following: service objectives of the multiple PDU sessions; Quality of Service (QoS) requirements for the plurality of PDU sessions; Service type characteristics of the multiple PDU sessions; Slicing requirements and UE Routing Selection Policy (URSP) rules associated with the multiple PDU sessions; or At least one of a slice instance or a slice type associated with the multiple PDU sessions.

9. The device according to claim 8, wherein The plurality of BSR tables and the plurality of sets of the one or more timers are based on the service targets of the plurality of PDU sessions, the service targets of the plurality of PDU sessions comprising one or more of the following: Internet PDU Session, or On-demand PDU sessions.

10. The device according to claim 8, wherein The multiple BSR tables and the multiple sets of the one or more timers are based on the traffic type characteristics of the multiple PDU sessions, the traffic type characteristics of the multiple PDU sessions comprising one or more of the following: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4 and IPv6 (IPv4v6), Ethernet (ETH) services, or Unstructured business.

11. The device according to claim 1, wherein The at least one processor, alone or in combination, is further configured to cause the UE to: Configurations for the plurality of BSR tables and the plurality of sets of one or more timers are received based on characteristics of a link between the UE and the network entity.

12. The device according to claim 11, wherein The characteristics of the link on which the multiple BSR tables and the multiple sets of one or more timers are based include: The connection type of the link, wherein the connection type is a terrestrial network (TN) connection or a non-terrestrial network (NTN) connection.

13. The device according to claim 12, wherein The connection type of the link is the NTN connection, and wherein the characteristics of the link on which the multiple BSR tables and the multiple sets of the one or more timers are based include one or more of the following: the delay associated with the NTN connection; a link capacity associated with the NTN connection; and NTN connectivity features include: a complete base station associated with said NTN connection, a reflector or repeater associated with the NTN connection, or The complete network associated with said NTN connection.

14. The device according to claim 12, wherein The connection type of the link is the TN connection or the NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of the one or more timers are based further include: The subcarrier spacing (SCS) characteristics of the connection type.

15. The device according to claim 12, wherein The connection type of the link is the TN connection or the NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of the one or more timers are based further include: The frequency band used for the connection type.

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 configured, individually or in combination, to cause the network entity to: providing an indication to a user equipment (UE) for the UE to select a buffer status report (BSR) table from a plurality of BSR tables and a set of one or more timers from a plurality of sets of one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to one of a plurality of logical channel groups (LCGs); as well as Communicating with the UE based on the one BSR table indicated for the UE and a set of the one or more timers.

17. The apparatus of claim 16, further comprising a transceiver coupled to the at least one processor, wherein To provide the indication, the at least one processor is configured, individually or in combination, to cause the network entity to send the indication via the transceiver, and wherein the indication is included in a Medium Access Control-Control Element (MAC-CE) or Radio Resource Control (RRC) information.

18. The device according to claim 17, wherein The selection of the one BSR table is based on one or more of the following: Cell Group (CG) information; The number of component carriers (CCs) enabled or disabled on the CG; LCG business type; Streaming service type; There is a Packet Data Convergence Protocol (PDCP) duplication; or Enable or disable split configuration.

19. The device according to claim 18, wherein The CG information includes one or more of the following: Using Master Cell Group (MCG), Use a Secondary Cell Group (SCG), or Use the Dual Connection (DC) mechanism.

20. The apparatus according to claim 16, wherein The plurality of sets of one or more timers include one or more of the following: Periodic BSR timer, Retransmit BSR timer, or Scheduling Request (SR) delay timer.

21. The apparatus according to claim 16, wherein The at least one processor, alone or in combination, is further configured to cause the network entity to: Sending configurations for the plurality of BSR tables and the plurality of sets of the one or more timers based on one or more of: LCG business type; Streaming service type; or A radio bearer (RB) associated with data.

22. The apparatus according to claim 16, wherein The at least one processor, alone or in combination, is further configured to cause the network entity to: Configurations for the plurality of BSR tables and the plurality of sets of one or more timers are sent based on characteristics of a plurality of protocol data unit (PDU) sessions.

23. The device according to claim 22, wherein The characteristics of the plurality of PDU sessions on which the plurality of BSR tables and the plurality of sets of the one or more timers are based include at least one of the following: service objectives of the multiple PDU sessions; Quality of Service (QoS) requirements for the plurality of PDU sessions; Service type characteristics of the multiple PDU sessions; Slicing requirements and UE Routing Selection Policy (URSP) rules associated with the multiple PDU sessions; or At least one of a slice instance or a slice type associated with the multiple PDU sessions.

24. The device according to claim 23, wherein The service objectives of the multiple PDU sessions include one or more of the following: Internet PDU Session, or On-demand PDU sessions.

25. The apparatus according to claim 23, wherein The traffic type characteristics of the plurality of PDU sessions on which the plurality of BSR tables and the plurality of sets of the one or more timers are based include one or more of the following: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4 and IPv6 (IPv4v6), Ethernet (ETH) services, or Unstructured business.

26. The apparatus according to claim 16, wherein The at least one processor, alone or in combination, is further configured to cause the network entity to: Configurations for the multiple BSR tables and the multiple sets of one or more timers are sent based on characteristics of a link between the UE and the network entity.

27. The device according to claim 26, wherein The characteristics of the link on which the multiple BSR tables and the multiple sets of one or more timers are based include: The connection type of the link, wherein the connection type is a terrestrial network (TN) connection or a non-terrestrial network (NTN) connection.

28. The apparatus according to claim 27, wherein The connection type of the link is the NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of the one or more timers are based further include one or more of the following: the delay associated with the NTN connection; the link capacity associated with the NTN connection; or NTN connectivity features include: a complete base station associated with said NTN connection, a reflector or repeater associated with the NTN connection, or The complete network associated with said NTN connection.

29. The apparatus according to claim 27, wherein The connection type of the link is the TN connection or the NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of the one or more timers are based further include: The subcarrier spacing (SCS) characteristics within the connection type.

30. The apparatus of claim 27, wherein: The connection type of the link is the TN connection or the NTN connection, and the characteristics of the link on which the multiple BSR tables and the multiple sets of the one or more timers are based further include: The frequency band used for the connection type.

31. A method of wireless communication at a user equipment (UE), comprising: Obtaining a plurality of buffer status report (BSR) tables and a plurality of sets of one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to one of a plurality of logical channel groups (LCGs); and Communicating with a network entity is performed based on a BSR table selected from the plurality of BSR tables and a timer set selected from the plurality of sets of one or more timers.

32. A method of wireless communication at a network entity, comprising: providing an indication to a user equipment (UE) for the UE to select a buffer status report (BSR) table from a plurality of BSR tables and a set of one or more timers from a plurality of sets of one or more timers, wherein each BSR table in the plurality of BSR tables corresponds to one of a plurality of logical channel groups (LCGs); and Communicating with the UE based on the one BSR table indicated for the UE and a set of the one or more timers.

Images