Patent Application
20240244478
The present disclosure relates generally to communication systems, and more particularly, to Buffer Status Reporting (BSR) trigger enhancements for wireless communication.
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. 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.
These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with 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 exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical 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 is presented later.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a user equipment (UE). The apparatus may include memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to transmit, to a network entity, a buffer status reporting (BSR) in response to a BSR triggering condition from multiple BSR triggering conditions being met, wherein each of the multiple BSR triggering conditions is associated with a Protocol Data Unit (PDU) set including a group of PDUs; and communicate, based on the BSR, with the network entity.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a network entity. The apparatus may include memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to receive, from a UE, a BSR, wherein the BSR is received in response to one BSR triggering condition of multiple BSR triggering conditions being met, wherein each of the multiple BSR triggering conditions is associated with a PDU set including a group of PDUs; and communicate, based on the BSR, with the UE.
To the accomplishment of the foregoing and related ends, the one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.
In wireless communication systems, such as Long-Term Evolution (LTE) and 5G systems, a buffer status report (BSR) provides the network with information about the data waiting to be transmitted from a user equipment (UE). The UE transmits a BSR that indicates the buffer status of the UE, which may facilitate the network to more efficiently allocate resources for wireless communication with the UE. The BSR transmission may be triggered based on an occurrence of one or more BSR trigger conditions (or BSR triggers), such as the expiration of a timer. The BSR triggers may further be associated with the type of BSR, e.g., whether a BSR is a short, long, or truncated BSR. Aspects provided herein further provide for BSR trigger conditions associated with the reason for which the BSR was triggered. In the current BSR mechanisms, one set of BSR trigger conditions may correspond to one medium access control (MAC) entity, and the single set of conditions may be applied to each of the logical channel groups (LCGs), radio bearer (DRB), protocol data unit (PDU) sessions, and application flows of the MAC entity. Example aspects presented herein provide the capability to enable various triggers associated with a PDU set (e.g., a group of PDUs associated with an application frame (e.g., a video frame)) level, rather than the PDU level.
Various aspects relate generally to wireless communication and more particularly to BSR triggering enhancements. Some aspects more specifically relate to the configurations of multiple BSR triggering conditions. In some examples, a UE may transmit, to a network entity, a buffer status reporting (BSR) in response to a BSR triggering condition from multiple BSR triggering conditions being met. Each of the multiple BSR triggering conditions may be associated with a PDU set including a group of PDUs. The UE may further communicate with the network entity based on the BSR.
Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by enabling a UE to use multiple BSR triggering conditions associated with the data transmission, the described techniques can be used to make the BSR information more readily available to the network and to enable a more efficient resource allocation. Thus, it improves the efficiency of wireless communication.
The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. When multiple processors are implemented, the multiple processors may perform the functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
Accordingly, in one or more example aspects, implementations, and/or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can include a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
While aspects, implementations, and/or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and/or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and/or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.). Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.
Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (CNB), NR BS, 5G NB, access point (AP), a transmission reception point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.
An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among 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 throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.
Each of the units, i.e., the CUS 110, the DUs 130, the RUs 140, as well as the Near-RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.
In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.
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 high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, or the like) depending, at least in part, on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.
Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a DU 130, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 140 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU(s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 111, via an O1 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an O1 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.
The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI)/machine learning (ML) (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 125. The Non-RT RIC 115 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.
In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. In some examples, the Non-RT RIC 115 or the Near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies).
At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify 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 a UE 104. The base station 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and/or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base station 102/UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. 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). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).
Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi™ (Wi-Fi is a trademark of the Wi-Fi Alliance) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs)) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHZ) and FR2 (24.25 GHz-52.6 GHZ). Although a portion of FR1 is greater than 6 GHZ, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHZ-24.25 GHZ). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHZ-71 GHZ), FR4 (71 GHz-114.25 GHZ), and FR5 (114.25 GHZ-300 GHz). Each of these higher frequency bands falls within the EHF band.
With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHZ, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.
The base station 102 and the UE 104 may each include a plurality of 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 best receive and transmit directions for each of the base station 102/UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.
The base station 102 may include and/or be referred to as a gNB, Node B, 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, network node, network entity, network equipment, or some other suitable terminology. The base station 102 can be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and/or an RU. The set of base stations, which may include disaggregated base stations and/or aggregated base stations, may be referred to as next generation (NG) RAN (NG-RAN).
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 the control node that processes the signaling between the UEs 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 identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, 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, the LMF 166, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients/applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and/or the base station 102 serving the UE 104. The signals measured may be based on one or more of a satellite positioning system (SPS) (e.g., one or more of a Global Navigation Satellite System (GNSS), global position system (GPS) 170, non-terrestrial network (NTN), or other satellite position/location system), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT), DL angle-of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle-of-arrival (UL-AoA) positioning), and/or other systems/signals/sensors.
Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.
Referring again to
For normal CP (14 symbols/slot), different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2μ slots/subframe. The subcarrier spacing may be equal to 2μ*15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing.
A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 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.
As illustrated in
As illustrated in
The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., 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 produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.
At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may 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 may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
The controller/processor 359 can 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, deciphering, header decompression, and control signal processing to recover IP packets. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality 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.
Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.
The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function 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 a RX processor 370.
The controller/processor 375 can 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, deciphering, header decompression, control signal processing to recover IP packets. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with the BSR triggering component 198 of
At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with the BSR triggering component 199 of
A UE may have uplink data to transmit to a network. The UE may transmit a BSR, e.g., in a MAC-CE from the UE to the network, with information regarding the amount of data in the UE's buffer waiting to be sent, e.g., transmitted, to the network. By sending a BSR to a network, the UE requests, or informs, the network to provide a UL grant (e.g., allocating or granting a transmission resource to the UE), through which the UE may transmit the data to the network. Upon receiving a BSR from the UE, the network may allocate a corresponding amount of resources in a UL grant (e.g., scheduling a transmission resource) for the UE to use for a UL transmission, the amount of resources being based on the amount of data that the BSR indicated.
A BSR may have different data structures and transmission timing. For example, a BSR may be a long BSR or a short BSR, depending on its data structure. A short BSR may indicate the amount of data in the UE's buffer for a single LCG, while a long BSR may indicate the amount of data in the UE's buffer for multiple LCGs.
A BSR may be an aperiodic BSR or a periodic BSR based on the timing at which the BSR is sent to the network. A UE may transmit an aperiodic BSR, which may be referred to as a regular BSR in some aspects, in response to the arrival of new data in the UE's buffer, and based on the new data having a higher priority than the data already waiting in the UE's buffer. A UE may use regular BSR to inform the network about the change in its buffer status, allowing the network to update its resource allocation and scheduling decisions accordingly. On the other hand, the UE may also transmit a periodic BSR according to a preset periodicity, e.g., a periodicity that may be configured by the network for BSR transmission. Since a periodic BSR is sent regardless of the change in the buffer status, it may not necessarily indicate a change in the buffer status (e.g., the arrival of new data), as is the case with regular BSRs.
A wireless communication system may support various types of traffic. Among other types of traffic, a wireless communication system may support XR traffic. XR traffic may refer to wireless communications for technologies such as virtual reality (VR), mixed reality (MR), and/or augmented reality (AR). VR may refer to technologies in which a user is immersed in a simulated experience that is similar or different from the real world. A user may interact with a VR system through a VR headset or a multi-projected environment that generates realistic images, sounds, and other sensations that simulate a user's physical presence in a virtual environment. MR may refer to technologies in which aspects of a virtual environment and a real environment are mixed. AR may refer to technologies in which objects residing in the real world are enhanced via computer-generated perceptual information, sometimes across multiple sensory modalities, such as visual, auditory, haptic, somatosensory, and/or olfactory. An AR system may incorporate a combination of real and virtual worlds, real-time interaction, and accurate three-dimensional registration of virtual objects and real objects. In an example, an AR system may overlay sensory information (e.g., images) onto a natural environment and/or mask real objects from the natural environment. XR traffic may include video data and/or audio data. XR traffic may be transmitted by a base station and received by a UE or the XR traffic may be transmitted by a UE and received by a base station.
XR traffic may arrive in periodic traffic bursts (“XR traffic bursts”). An XR traffic burst may vary in a number of packets per burst and/or the size of each packet in the burst. The diagram 700 in
XR traffic bursts may arrive at non-integer periods (i.e., in a non-integer cycle). The periods may be different than an integer number of symbols, slots, etc. In an example, for 60 frames per second (FPS) video data, XR traffic bursts may arrive in 1/60=16.67 ms periods. In another example, for 120 FPS video data, XR traffic bursts may arrive in 1/120=8.33 ms periods.
Arrival times of XR traffic may vary. For example, XR traffic bursts may arrive and be available for transmission at a time that is earlier or later than the time at which a UE (or a base station) expects the XR traffic bursts. The variability of the packet arrival relative to the period (e.g., 16.76 ms period, 8.33 ms period, etc.) may be referred to as “jitter.” In an example, jitter for XR traffic may range from −4 ms (earlier than expected arrival) to +4 ms (later than expected arrival). For instance, referring to the first XR flow 702, a UE may expect a first packet of the first XR traffic burst 704 to arrive at time t0, but the first packet of the first XR traffic burst 704 arrives at time t1.
XR traffic may include multiple flows that arrive at a UE (or a base station) concurrently with one another (or within a threshold period of time). For instance, the diagram 700 includes a second XR flow 708. The second XR flow 708 may have different characteristics than the first XR flow 702. For instance, the second XR flow 708 may have XR traffic bursts with different numbers of packets, different sizes of packets, etc. In an example, the first XR flow 702 may include video data and the second XR flow 708 may include audio data for the video data. In another example, the first XR flow 702 may include intra-coded picture frames (I-frames) that include complete images and the second XR flow 708 may include predicted picture frames (P-frames) that include changes from a previous image.
In a BSR configuration, a single set of BSR triggering conditions may correspond to one MAC entity. The set of BSR triggering conditions may be used for each of the LCGs, DRBs, PDU sessions, and various application flows. The set of BSR triggering conditions may correspond to the BSR being a short, long, or truncated BSR, but does not correspond to the reason that a BSR is triggered (e.g., whether a BSR is triggered due to new data arrival, the significant change of the data amount to be transmitted, or as a periodic BSR transmission). Some timing mechanisms may use a timer to monitor the transmission process of the data associated with an application, and a device may react accordingly (e.g., discard the transmission or request a retransmission) if the transmission delay is too long and extends longer than a threshold amount of time. For example, a “timer discard” may correspond to discarding a transmission based on a timer running at the PDCP layer. If a PDU waits at the PDCP layer for longer than Timer Discard, it will be discarded.
Aspects presented herein provide the capability to enable various triggers at a PDU set level (rather than the PDU level). In this disclosure, a “PDU set” may refer to a group of PDUs associated with an application frame (e.g., a video frame). The set of BSR triggering conditions does not cover the physical layer (PHY) aspects, for example. In BSR triggering mechanisms based on the timer discard mechanism, even with a complete Hybrid Automatic Repeat Request (HARQ) Block Error Rate (BLER), when the BSR is already encoded in a MAC TB, the retransmit (ReTx) BSR timer logic may stop further BSR transmission (e.g., a retransmission of a BSR) to the network for a period of time, which may prevent the BSR information from being transmitted to the network in a timely manner. When a PDU set is transmitted, if the HARQ fails or experiences delays due to the retransmission (which may result in the PDU Set Delay Budget (PSDB) requirement being missed), the BSR may be stopped or held due to the retransmission BSR. Hence, even though some grants (e.g., transmission resources) may come in association with an earlier BSR, when the PSDB requirement is missed due to physical (PHY) layer issues, there may be no additional BSR trigger to the network. For example, when a timer discard happens (e.g., due to the transmission delay) and some PDU sets are discarded, which may impact the QoS requirements, the BSR will not be triggered. Under the current BSR triggering mechanisms, the BSR trigger happens when higher-priority DRB data arrives, but not for the data on the same DRB, and there is no distinction of higher or lower priority flow within the DRB that is considered. Additionally, after the BSR information is sent to the network at the instance a BSR triggering condition is met, the BSR may be changed by the time the grant (e.g., transmission resources) starts coming. In that case, a UE may not send an updated BSR until a condition is met (e.g., one of the “Regular or Padding BSR” conditions is met) and the retransmission BSR (ReTxBSR) timer is not running.
The present disclosure provides for signaling enhancements for BSR triggering conditions. In some aspects, the signaling enhancements may include additional BSR triggering conditions to enable the timely availability of buffer status information for the base station. In some example aspects, these additional BSR triggering conditions may be introduced for XR-specific applications.
In some aspects, the BSR triggering conditions may be PDU set specific. In XR applications, the communication of PDUs in a PDU set may have certain requirements, such as the PDU Set Delay Budget (PSDB) requirement and the PDU Set Error Rate (PSER) requirement. For example, an example PSDB may be 100 milliseconds and an example PSER may be 1%, meaning that the entire PDU set is to be transmitted within 100 milliseconds with an error rate not more than 1%.
In some aspects, the BSR triggering conditions may be related to the latency condition of a PDU set transmission. In one example, the triggering conditions may be related to an elapsed time from the beginning of a PDU set transmission. For example, if an elapsed time since the beginning of a PDU set transmission is greater than a first elapsed threshold and no grant (e.g., transmission resources) has been received yet, a BSR transmission may be triggered. In another example, the triggering conditions may be related to an elapsed time from the reception of the last grant (e.g., the last transmission that provides transmission resources). For example, if an elapsed time since the reception of the last grant (e.g., the last transmission that provides transmission resources) is greater than a second elapsed threshold, and no new grant (e.g., transmission resources) has been received yet, a BSR transmission may be triggered. In another example, the triggering conditions may be related to the experienced latency of the PDU set transmission. For example, if the experienced latency of a PDU set transmission is longer than a third threshold (or the ratio of the experienced latency to the PSDB is larger than a ratio threshold), a BSR transmission may be triggered. In these examples, when the transmission of a PDU set is experiencing a delay more than a specific threshold from the beginning of the PDU set's arrival into a modem or from the reception of the last grant, a BSR may be triggered to request a further grant (e.g., additional transmission resource) from the network, which may help to get the grant (e.g., transmission resource) within the PSDB to ensure the PDU set is delivered successfully within the PSDB from the flow perspective.
In some examples, grants (e.g., transmission resources) may be received periodically and the time interval between adjacent grants (e.g., adjacent transmissions that provide transmission resources) may be less than the second elapsed threshold. In those cases, the BSR triggering conditions based on the elapsed time since the beginning of a PDU set transmission and the elapsed time since the reception of the last grant (e.g., the last transmission that provides transmission resources) are not met, and no BSR may be triggered based on these triggering conditions. However, in those cases, the overall latency may exceed the PSDB. Hence, sending the BSR based on the experienced latency may help the network increase the grant (e.g., transmission resources) to, for example, meet the PSDB requirement.
In some aspects, new BSR types may be provided, and a BSR may include additional bits or fields indicating the corresponding BSR types. The BSR types may indicate the reason the BSR is triggered. For example, the reason may be that the elapsed time from the beginning of a PDU set transmission or the elapsed time since the reception of the last grant is longer than the corresponding threshold. The additional bits or fields in the BSR may be helpful for the network to react to the scheduling perspective (e.g., changing the grant pattern). For example, if the BSR type indicates that the BSR is triggered because the elapsed time since the reception of the last grant is longer than the corresponding threshold, the network may increase the frequency of transmitting the grant. A new BSR type, for example, a “latency” type, may be provided as an additional type. The BSR triggered by the latency condition of a PDU set transmission may have an indication of the “type of latency” as additional bits/reasons. This information may help the network to react to the scheduling perspective accordingly.
In some aspects, the BSR triggering conditions may be related to the number of HARQ failures or the overall HARQ conclusion delay. For example, when the number of the experienced previous HARQ failures, or the experienced overall HARQ conclusion delay is greater than a corresponding threshold, a BSR may be triggered. In one example, a BSR may be triggered if the number of HARQ failures is greater than two, or the overall HARQ conclusion delay is greater than 100 milliseconds.
In some aspects, the BSR triggering conditions may be related to the timer discard (e.g., discard of one or more PDUs based on the expiration of a timer) for any PDU in the PDU set. When the timer discard happens, and some PDUs are discarded, the QoS requirements or the PSER may be affected. Hence, having additional BSR triggering mechanisms to indicate the relevant information to the network may help the network to better manage the PDU set transmission (for example, by increasing the grant to address the PSDB or conserving the MCS to improve the PSER). A new BSR type, for example, a “PHY” type, may be provided as an additional type. The BSR triggered by the PHY issues related to a PDU set transmission (e.g., the number of the experienced previous HARQ failures) may have an indication of, for example, a “type of drop” as additional bits/reasons that indicate a reason that the PDU(s) were dropped. This information may help the network to react to the received information with more effective scheduling for the UE.
In some aspects, the BSR triggering conditions may have a flow level distinction. For example, the BSR triggering conditions may be related to new PDU sets (on the same priority or higher priority flow, on the same flow or different flow) arriving on the same DRB of the current PDU set. The BSR triggering conditions may also be related to new PDU sets arrived on different DRBs of the same priority, which may belong to the same PDU session or different PDU sessions of the current PDU set.
As multiple flows of different priorities and QoS requirements may be multiplexed on the same DRB, when high priority flow data (compared to previous BSR instances) arrives, additional BSR may be sent to the network to help the network better arrange the resource from the PSDB and PSER perspectives.
For example, on a given flow, the arrival of a higher priority PDU set (compared to previous PDU sets) or the arrival of the same priority flow on the bearer may indicate that the PDU set associated with the previous frame may be late. Hence, a trigger for the BSR may be sent.
Even if the data came on different DRBs of the same priority, if the PDU session type is different (e.g., IPv4, IPv6, IPv4v6, Ethernet (ETH), Unspecified) or the PDU session slice type is different (e.g., eMBB, URLLC, mMTC, etc.), a BSR may be triggered to indicate the presence of data as some of the PDU sessions may be more sensitive to PSDB (e.g., ETH, URLLC) than others.
As all the above scenarios may impact the PSDB, PSER, additional BSR triggers related to these scenarios may be provided to indicate relevant information to the network for the network to better manage the PUD set transmission. For example, the network may increase the grant to address PSDB or conserve MCS to improve the PSER. A New BSR type, for example, a type based on “flow” may be provided as an additional type. The BSR triggered by the flow level issues related to a PDU set transmission (e.g., the arrival of new PDU sets on the DRB) may have an indication of, for example, “type of flow” as additional bits/reasons. This information may help the network to react to the scheduling perspective accordingly.
In some aspects, the BSR triggering conditions may be related to a change of BSR. When the BSR has changed between the BSR report time and the time of receiving the first grant, a new BSR may be triggered, even with the current data not being fully drained. In one example, the first BSR may report a requested data amount of 10K, and the grant may come after 20 ms. Meanwhile, after the first BSR was sent, 4K of data may be discarded due to, for example, a timer discard on the same DRB. In that case, without additional BSR, the network may assume 10K is the requested data amount and schedule the grant accordingly (for example, the network may schedule 5K of grant at t=0 and another 5K of grant at t=10 ms). However, the actual data amount before the first grant is 6K, and 4K of grant may be wasted if the network is not notified of the updated data amount. Hence, if the BSR has changed before the first grant is received, a new BSR may be reported in the first MAC TB (or every MAC TB in which this change happened) to inform the network of the updated BSR. For example, with the new BSR report, the network may schedule 1K (instead of 5K) of data at t=10 ms to avoid wasting transmission resources.
In some aspects, the network may schedule in a way that the total amount of data indicated by the BSR may be spread over time. Hence, having the updated BSR at the time of the first grant or periodically may help the network to adjust the scheduling mechanisms, for example, by increasing or decreasing the grant, to meet the PSDB. For example, the network may increase the grant if the BSR increases or decrease the grant if BSR is reduced due to, for example, a timer discard.
As the BSR update may impact the PSDB, PSER, having additional BSR trigger mechanisms to indicate the BSR update information to the network may help the network to better manage the PDU set transmission, for example, by increasing the grant to address the PSDB or conserving the MCS to improve the PSER.
A new BSR type, for example, an “updated” type, may be provided as an additional type. The BSR triggered by the change of BSR may have an indication of the “type of update” as additional bits/reasons. This information may help the network to react to the scheduling perspective accordingly.
As shown in
At 808, the base station 804 may, in response to the first BSR, allocate the corresponding UL grant to the UE 802.
At 810, when the UE 802 receives the UL grant from the base station 804, the UE 802 may start transmitting the data to the base station 804 with the UL grant. In some examples, the data may be a PDU set.
At 812, based on the transmission condition of the data, the UE 802 may evaluate whether a BSR triggering condition from multiple BSR triggering conditions is met. The multiple BSR triggering conditions may be based on one or more of: a latency condition of the PDU set; a condition relating to dropped packets (or PDUs) in the PDU set; a flow condition of the PDU set; or an update condition of the PDU set. For example, the UE 802 may evaluate whether there is a delay on receiving the UL grant from the base station 804, or whether there are any HARQ failures associated with the data transmission, or whether there is another PDU set arriving on the same DRB.
At 814, if one BSR triggering condition is met, the UE 802 may send a second BSR to the base station 804. For example, if the UE 802 determines that the elapsed time since the last transmission resource received from the base station 804 is longer than a corresponding threshold, the UE 802 may send, at 814, a second BSR. The second BSR may include the information for the reason the second BSR is triggered.
At 816, based on the received second BSR, the base station 804 may adjust the transmission scheme to the UE 802. For example, the base station may adjust (e.g., increase or decrease) the transmission resource for the UE or modify the MCS for the transmission. For example, if the second BSR indicates that the reason for the BSR is the elapsed time since the last transmission resource received from the base station 804 is longer than a corresponding threshold, the base station 804 may reduce the interval between the grant allocations to the UE 802.
At 818, the UE 802 may continue communicating with the base station 804 based on the BSR. For example, if the base station 804 has adjusted the transmission scheme (e.g., adjusted the transmission resource or modified the MCS) at 816 based on the second BSR received at 814, the UE 802 and the base station 804 may continue the communication based on the adjusted transmission scheme.
As shown in
At 904, the UE may communicate, based on the BSR, with the network entity. For example, referring to
As shown in
At 1004, the UE may communicate, based on the BSR, with the network entity. For example, referring to
In some aspects, as shown in
In some aspects, at 1006, the BSR may include a field indicating the BSR triggering condition. For example, referring to
In some aspects, the BSR triggering condition may be based on a latency condition of the PDU set (1012). The latency condition may be based on one or more of: a first elapsed time since the beginning of the PDU set; a second elapsed time since the last transmission resource received from the network entity associated with the PDU set; or a ratio of the first elapsed time to a PSDB. For example, referring to
In some aspects, the BSR triggering condition may be based on a condition relating to dropped packets (or PDUs) in the PDU set (1014). The condition relating to dropped packets (or PDUs) in the PDU set may be based on one or more of: a number of Hybrid Automatic Repeat Request (HARQ) failures associated with the PDU set; an overall HARQ conclusion delay; or a number of timers discarded for the PDUs in the PDU set. For example, referring to
In some aspects, the PDU set may be a first PDU set, and the BSR triggering condition is based on a flow condition of the first PDU set (1016). The flow condition may be based on at least one of: a second PDU set arrived on the same DRB of the first PDU set; or a third PDU set arrived on a second DRB different from the DRB of the first PDU set. For example, referring to
In some aspects, the first PDU set and the second PDU set may be associated with the same flow or different flows. For example, referring to
In some aspects, the first PDU set and the second PDU set may have the same priority or different priorities. For example, referring to
In some aspects, the first PDU set and the third PDU set may be associated with the same PDU session or different PDU sessions. For example, referring to
In some aspects, the first PDU set and the third PDU set may have the same priority or different priorities. For example, referring to
In some aspects, the BSR triggering condition may be based on an update condition of the PDU set (1018). The update condition may be based on: an increase or a decrease of data associated with the BSR from a BSR report time of the BSR to a receiving time for receiving a first grant associated with the BSR. For example, referring to
In some aspects, the multiple BSR triggering conditions may be based on traffic types of one or more PDU sessions associated with an application (1022). The traffic types may include one or more of: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4 & IPv6 (IPv4v6), ETH traffic, or unstructured traffic. For example, referring to
In some aspects, the multiple BSR triggering conditions may be based on slice characteristics associated with an application (1024). The slice characteristics may include one or more of: a slice type, a slice ID, or UE route selection policy (URSP) rules. For example, referring to
In some aspects, the multiple BSR triggering conditions may be based on link characteristics associated with an application (1026). The link characteristics may include: a TN connection or an NTN connection. For example, referring to
In some aspects, the multiple BSR triggering conditions may be based on one or more of: SCS characteristics associated with an application or the frequency band associated with the application (1028). The frequency band may include one of: the FR1 frequency band, the FR2 frequency band, or the FR4 frequency band. For example, referring to
As shown in
At 1104, the network entity may communicate, based on the BSR, with the UE. For example, referring to
As shown in
At 1204, the network entity may communicate, based on the BSR, with the UE. For example, referring to
In some aspects, as shown in
In some aspects, at 1206, the BSR may include a field indicating the BSR triggering condition. For example, referring to
In some aspects, the BSR triggering condition may be based on a latency condition of the PDU set (1212). The latency condition may be based on one or more of: a first elapsed time since the beginning of the PDU set; a second elapsed time since the last transmission resource received from the network entity associated with the PDU set; or a ratio of the first elapsed time to a PSDB. For example, referring to
In some aspects, the BSR triggering condition may be based on a condition relating to dropped packets (or PDUs) in the PDU set (1214). The condition relating to dropped packets (or PDUs) in the PDU set may be based on one or more of: the number of HARQ failures associated with the PDU set; the overall HARQ conclusion delay; or the number of timers discarded for the PDUs in the PDU set. For example, referring to
In some aspects, the PDU set may be a first PDU set, and the BSR triggering condition may be based on a flow condition of the first PDU set (1216). The flow condition may be based on at least one of: a second PDU set arrived on the same DRB of the first PDU set; or a third PDU set arrived on a second DRB different from the DRB of the first PDU set. For example, referring to
In some aspects, the first PDU set and the second PDU set may be associated with the same flow or different flows. For example, referring to
In some aspects, the first PDU set and the second PDU set may have the same priority or different priorities. For example, referring to
In some aspects, the first PDU set and the third PDU set may be associated with the same PDU session or different PDU sessions. For example, referring to
In some aspects, the first PDU set and the third PDU set may have the same priority or different priorities. For example, referring to
In some aspects, the BSR triggering condition may be based on an update condition of the PDU set (1218). The update condition of the PDU set is based on: an increase or a decrease of data associated with the BSR from a BSR report time of the BSR to a receiving time for receiving a first grant associated with the BSR. For example, referring to
In some aspects, to communicate, based on the BSR, with the UE, the network entity may be configured to, at 1208, increase transmission resources to the UE based on a PSDB of the PDU set and the BSR or, at 1210, modify an MCS associated with the PDU set based on the BSR to improve a PSER of the PDU set. For example, referring to
In some aspects, the multiple BSR triggering conditions may be based on one or more of: traffic types of one or more PDU sessions associated with an application (1222), where the traffic types include one or more of: IPv4, IPv6, IPv4v6, ETH traffic, or unstructured traffic; slice characteristics associated with an application (1224), where the slice characteristics comprise one or more of: a slice type, a slice ID, or URSP rules; link characteristics associated with an application (1226), where the link characteristics include a TN connection or an NTN connection; SCS characteristics associated with the application or the frequency band associated with the application (1228), where the frequency band includes one of: the FR1 frequency band, the FR2 frequency band, or the FR4 frequency band. For example, referring to
As discussed supra, the component 198 may be configured to transmit, to a network entity, a BSR in response to a BSR triggering condition from multiple BSR triggering conditions being met, where each of the multiple BSR triggering conditions is associated with a PDU set including a group of PDUs associated with a frame of an application; and communicate, based on the BSR, with the network entity. The component 198 may be further configured to perform any of the aspects described in connection with the flowcharts in
As discussed supra, the component 199 may be configured to receive, from a UE, a BSR, where the BSR is received in response to one BSR triggering condition of multiple BSR triggering conditions being met, wherein each of the multiple BSR triggering conditions is associated with a PDU set including a group of PDUs; and communicate, based on the BSR, with the UE. The component 199 may be further configured to perform any of the aspects described in connection with the flowcharts in
This disclosure provides a method for wireless communication at a UE. The method may include transmitting, to a network entity, a BSR in response to a BSR triggering condition from multiple BSR triggering conditions being met, wherein each of the multiple BSR triggering conditions is associated with a PDU set including a group of PDUs; and communicating, based on the BSR, with the network entity.
The method provides multiple BSR triggering conditions based on various scenarios in data transmission. The method allows the BSR information to be more readily available to the network and enables a more efficient resource allocation. Thus, it improves the efficiency of wireless communication.
It is understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.
The previous 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 readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint 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 to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, 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, B, and C,” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor, individually or in any combination, is configured to perform the set of functions. Accordingly, each processor of the at least one processor may be configured to perform a particular 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 may be referred to as processor circuitry. A memory/memory module may be referred to as memory circuitry. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received/transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. A device configured to “output” data or “provide” data, such as a transmission, signal, or message, may transmit the data, for example with a transceiver, or may send the data to a device that transmits the data. A device configured to “obtain” data, such as a transmission, signal, or message, may receive, for example with a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and/or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”
As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.
The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.
Aspect 1 is a method of wireless communication at a UE. The method may include transmitting, to a network entity, a BSR in response to a BSR triggering condition from multiple BSR triggering conditions being met, where each of the multiple BSR triggering conditions is associated with a PDU set including a group of PDUs; and communicating, based on the BSR, with the network entity.
Aspect 2 is the method of aspect 1, where the multiple BSR triggering conditions may include one or more of: a latency condition of the PDU set; a condition relating to dropped PDUs in the PDU set; a flow condition of the PDU set; or an update condition of the PDU set.
Aspect 3 is the method of any of aspects 1 to 2, where the BSR may include a field indicating the BSR triggering condition.
Aspect 4 is the method of any of aspects 2 to 3, where the BSR triggering condition may be based on the latency condition of the PDU set, which is based on one or more of: a first elapsed time since the beginning of the PDU set; a second elapsed time since the last transmission resource received from the network entity associated with the PDU set; or a ratio of the first elapsed time to a PDU set delivery budget (PSDB).
Aspect 5 is the method of any of aspects 2 to 3, where the BSR triggering condition may be based on the condition relating to dropped PDUs in the PDU set, which is based on one or more of: a number of HARQ failures associated with the PDU set; an overall HARQ conclusion delay; or a number of timers discarded for the PDUs in the PDU set.
Aspect 6 is the method of any of aspects 2 to 3, where the PDU set may be a first PDU set, and the BSR triggering condition may be based on the flow condition of the first PDU set, which is based on at least one of: a second PDU set arrived on the same Radio Bearer (DRB) of the first PDU set; or a third PDU set arrived on a second DRB different from the DRB of the first PDU set.
Aspect 7 is the method of aspect 6, where the first PDU set and the second PDU set may be associated with the same flow or different flows.
Aspect 8 is the method of aspect 6, where the first PDU set and the second PDU set may have the same priority or different priorities.
Aspect 9 is the method of aspect 6, where the first PDU set and the third PDU set may be associated with the same PDU session or different PDU sessions.
Aspect 10 is the method of aspect 6, where the first PDU set and the third PDU set may have the same priority or different priorities.
Aspect 11 is the method of any of aspects 2 to 3, where the update condition of the PDU set may be based on: an increase or a decrease of data associated with the BSR from a BSR report time of the BSR to a receiving time for receiving a first grant associated with the BSR.
Aspect 12 is the method of any of aspects 1-11, where the multiple BSR triggering conditions may be based on traffic types of one or more PDU sessions associated with an application, and the traffic types may include one or more of: IPv4, IPv6, IPv4v6, ETH traffic, or unstructured traffic.
Aspect 13 is the method of any of aspects 1-11, where the multiple BSR triggering conditions may be based on slice characteristics associated with an application, and the slice characteristics may include one or more of: a slice type, a slice ID, or URSP rules.
Aspect 14 is the method of any of aspects 1-11, where the multiple BSR triggering conditions may be based on link characteristics associated with an application, and the link characteristics may include: the TN connection or the NTN connection.
Aspect 15 is the method of any of aspects 1-11, where the multiple BSR triggering conditions may be based on one or more of: SCS characteristics associated with an application, or a frequency band associated with the application. The frequency band may include one of the FR1 frequency band, the FR2 frequency band, or the FR4 frequency band.
Aspect 16 is an apparatus for wireless communication at a UE, comprising: a processing system that includes processor circuitry and memory circuitry that stores code and is coupled with the processor circuitry, the processing system configured to cause the UE to perform the method of one or more of aspects 1-15.
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, where the at least one processor, individually or in any combination, is configured to perform the method of any of aspects 1-15.
Aspect 18 is the apparatus for wireless communication at a UE, comprising means for transmitting, to a network entity, a BSR in response to a BSR triggering condition from multiple BSR triggering conditions being met, wherein each of the multiple BSR triggering conditions is associated with a PDU set including a group of PDUs, and means for communicating, based on the BSR, with the network entity.
Aspect 19 is the apparatus of aspect 18, further comprising means for performing each step in the method of any of aspects 2-15.
Aspect 20 is an apparatus of any of aspects 16-19, further comprising a transceiver configured to receive or to transmit in association with the method of any of aspects 1-15.
Aspect 21 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code at a UE, the code when executed by at least one processor causes the at least one processor to, individually or in any combination, perform the method of any of aspects 1-15.
Aspect 22 is a method of wireless communication at a network entity. The method may include receiving, from a UE, a BSR, where the BSR is received in response to one BSR triggering condition of multiple BSR triggering conditions being met, and each of the multiple BSR triggering conditions is associated with a PDU set including a group of PDUs; and communicating, based on the BSR, with the UE.
Aspect 23 is the method of aspect 22, where the multiple BSR triggering conditions may include one or more of: a latency condition of the PDU set; a condition related to dropped PDUs in the PDU set; a flow condition of the PDU set; or an update condition of the PDU set.
Aspect 24 is the method of any of aspects 22 to 23, where the BSR may include a field indicating the BSR triggering condition.
Aspect 25 is the method of any of aspects 23 to 24, where the BSR triggering condition may be based on the latency condition of the PDU set, which is based on one or more of: a first elapsed time since the beginning of the PDU set; a second elapsed time since the last transmission resource received from the network entity associated with the PDU set; or a ratio of the first elapsed time to a PDU set delivery budget (PSDB).
Aspect 26 is the method of any of aspects 23 to 24, where the BSR triggering condition may be based on the condition relating to dropped PDUs in the PDU set, which is based on one or more of: the number of HARQ failures associated with the PDU set; the overall HARQ conclusion delay; or the number of timers discarded for the PDUs in the PDU set.
Aspect 27 is the method of any of aspects 23 to 24, wherein the PDU set is a first PDU set, and the BSR triggering condition may be based on the flow condition of the first PDU set, which is based on at least one of: a second PDU set arrived on the same DRB of the first PDU set; or a third PDU set arrived on a second DRB different from the DRB of the first PDU set.
Aspect 28 is the method of aspect 27, where the first PDU set and the second PDU set may be associated with the same flow or different flows.
Aspect 29 is the method of aspect 27, where the first PDU set and the second PDU set may have the same priority or different priorities.
Aspect 30 is the method of aspect 27, where the first PDU set and the third PDU set may be associated with the same PDU session or different PDU sessions.
Aspect 31 is the method of aspect 27, where the first PDU set and the third PDU set may have the same priority or different priorities.
Aspect 32 is the method of any of aspects 23 to 24, where the update condition of the PDU set may be based on an increase or a decrease of data associated with the BSR from a BSR report time of the BSR to a receiving time for receiving a first grant associated with the BSR.
Aspect 33 is the method of any of aspects 22 to 32, where, to communicate, based on the BSR, with the UE, the network entity may be configured to: increase transmission resources to the UE based on a PSDB of the PDU set and the BSR; or modify an MCS associated with the PDU set based on the BSR to improve the PSER of the PDU set.
Aspect 34 is the method of any of aspects 22 to 32, where the multiple BSR triggering conditions may be based on one or more of: traffic types of one or more PDU sessions associated with an application, where the traffic types include one or more of: IPv4, IPv6, IPv4v6, ETH traffic, or unstructured traffic; slice characteristics associated with the application, where the slice characteristics include one or more of: a slice type, a slice ID, or URSP rules; link characteristics associated with the application, where the link characteristics include the TN connection or the NTN connection; SCS characteristics associated with the application; or the frequency band associated with the application, where the frequency band includes one of: the FR1 frequency band, the FR2 frequency band, or the FR4 frequency band.
Aspect 35 is an apparatus for wireless communication at a network entity, comprising: a processing system that includes processor circuitry and memory circuitry that stores code and is coupled with the processor circuitry, the processing system configured to cause the network entity to perform the method of one or more of aspects 22-34.
Aspect 36 is an apparatus for wireless communication at a network entity, comprising: at least one memory; and at least one processor coupled to the at least one memory and, where the at least one processor, individually or in any combination, is configured to perform the method of any of aspects 22-34.
Aspect 37 is the apparatus for wireless communication at a network entity, comprising means for receiving, from a UE, a BSR, wherein the BSR is received in response to one BSR triggering condition of multiple BSR triggering conditions being met, wherein each of the multiple BSR triggering conditions is associated with a PDU set including a group of PDUs, and means for communicating, based on the BSR, with the UE.
Aspect 38 is the apparatus of aspect 37, further comprising means for performing each step in the method of any of aspects 23-34.
Aspect 39 is an apparatus of any of aspects 35-38, further comprising a transceiver configured to receive or to transmit in association with the method of any of aspects 22-34.
Aspect 40 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code at a network entity, the code when executed by at least one processor causes the at least one processor to, individually or in any combination, perform the method of any of aspects 22-34.
This application claims the benefit of and priority to U.S. Provisional Application Ser. No. 63/479,964, entitled “BSR TRIGGER ENHANCEMENTS” and filed on Jan. 13, 2023, which is expressly incorporated by reference herein in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 63479964 | Jan 2023 | US |
