WO2021126789A1

WO2021126789A1 - Detecting system level instability or need for load balancing

Info

Publication number: WO2021126789A1
Application number: PCT/US2020/064940
Authority: WO
Inventors: Konstantinos Dimou; Arumugam Chendamarai Kannan; Tao Luo; Yan Zhou
Original assignee: Qualcomm Incorporated
Priority date: 2019-12-20
Filing date: 2020-12-14
Publication date: 2021-06-24
Also published as: TW202135560A

Abstract

A configuration to enable a UE to detect that a system may experience an increase in errors due to expiration of packets. The apparatus may determine a scheduling delay for each of a plurality of packets. The apparatus may determine that the scheduling delay for the plurality of packets meets a scheduling delay metric. The apparatus may send a notification to a base station based on the determination that the scheduling delay for the plurality of packets meets the scheduling delay metric.

Description

DETECTING SYSTEM LEVEL INSTABILITY OR NEED FOR LOAD BALANCING

CROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of Greek Patent Application No. 20190100571, entitled “Detecting System Level Instability of Need for Load Balancing” and filed on December 20, 2019, which is expressly incorporated by reference herein in its entirety.

BACKGROUND

Technical Field

[0002] The present disclosure relates generally to communication systems, and more particularly, to a configuration for detecting system level instability or need for load balancing in wireless communication networks.

Introduction

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate 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.

SUMMARY

[0005] 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, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a UE. The device may be a processor and/or a modem at a UE or the UE itself. The apparatus may determine a scheduling delay for each of a plurality of packets. The apparatus may determine that the scheduling delay for the plurality of packets meets a scheduling delay metric. The apparatus may send a notification to a base station based on the determination that the scheduling delay for the plurality of packets meets the scheduling delay metric.

[0007] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a base station. The device may be a processor and/or a modem at a base station or the base station itself. The apparatus may transmit or receive a plurality of packets with a user equipment (UE). The apparatus may receive a notification from the UE, wherein the notification is based on a scheduling delay for the plurality of packets meeting the scheduling delay metric. The apparatus may change a bandwidth part (BWP), a cell, a carrier, or a type of scheduler for the UE in response to receiving the notification.

[0008] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed 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, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

[0010] FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

[0011] FIG. 2B is a diagram illustrating an example of DL channels within a subframe, in accordance with various aspects of the present disclosure.

[0012] FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

[0013] FIG. 2D is a diagram illustrating an example of UL channels within a subframe, in accordance with various aspects of the present disclosure.

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

[0015] FIG. 4 is a diagram illustrating aUE in communication with one or more base stations.

[0016] FIG. 5 is a call flow diagram of signaling between a UE and abase station.

[0017] FIG. 6 is a flowchart of a method of wireless communication.

[0018] FIG. 7 is a diagram illustrating an example of a hardware implementation for an example apparatus.

[0019] FIG. 8 is a flowchart of a method of wireless communication.

[0020] FIG. 9 is a diagram illustrating an example of a hardware implementation for an example apparatus.

DETAILED DESCRIPTION

[0021] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to 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, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0022] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be 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.

[0023] 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. 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 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, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0024] Accordingly, in one or more example embodiments, 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, and not limitation, such computer-readable media can comprise 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 aforementioned 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.

[0025] FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC)). The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The macrocells include base stations. The small cells include femtocells, picocells, and microcells.

[0026] The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through first backhaul links 132 (e.g., SI interface). The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 through second backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface). The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless.

[0027] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102. 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 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from abase station 102 to aUE 104. The communication links 120 may use multiple- in put 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 stations 102 / UEs 104 may use spectrum up to 7MHz (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 respectto 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).

[0028] 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 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, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0029] The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the STAs 152 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available. [0030] The small cell 102' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP 150. The small cell 102', employing NRin an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

[0031] 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). The frequencies between FR1 and FR2 are often referredto as mid-band frequencies. 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.

[0032] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

[0033] Abase station 102, whether a small cell 102' or a large cell (e.g., macro base station), may include and/or be referredto as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the path loss and short range. The base station 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming. [0034] The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182'. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182". The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180 / UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

[0035] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

[0036] The core network 190 may include a Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and aUser Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UEIP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services.

[0037] The base station 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), atransmit reception point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. 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, amultimedia device, a video device, adigital 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 referredto 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.

[0038] Referring again to FIG. 1, in certain aspects, the UE 104 may be configured to detect that the system may experience an increase in errors due to expiration of packets. For example, the UE 104 of FIG. 1 may include a scheduling delay component 198 configured to determine that a scheduling delay for a plurality of packets meets a scheduling delay metric. The UE 104 may determine a scheduling delay for each of a plurality of packets. The UE 104 may determine that the scheduling delay for the plurality of packets meets a scheduling delay metric. The UE 104 may send a notification to a base station based on the determination that the scheduling delay for the plurality of packets meets the scheduling delay metric. [0039] Referring again to FIG. 1, in certain aspects, the base station 102/180 may be configured to change the conditions or resources configuration of a UE in response to an increase of scheduling delay. For example, the base station 102/180 of FIG. 1 may include a change component 199 configured to change the bandwidth part (BWP), a cell, a carrier, or a type of scheduler for the UE in response to a notification from the UE 104. The base station 102/180 may transmit or receive a plurality of packets with the UE. The base station 102/180 may receive a notification from the UE, where the notification is based on a scheduling delay for the plurality of packets meeting a scheduling delay metric. The base station 102/180 may change the BWP, the cell, the carrier, or the type of scheduler for the UE in response to receiving the notification.

[0040] Although the following description may be focused 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.

[0041] FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI), or semi- statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the description infra applies also to a 5G NR frame structure that is TDD. [0042] Other wireless communication technologies may have a different frame structure 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. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. The symbols on DL may be cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP -OFDM) symbols. The symbols on UL may be CP -OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission). The number of slots within a subframe is based on the slot configuration and the numerology. For slot configuration 0, different numerologies m 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology m, there are 14 symbols/slot and 2r slots/subframe. The subcarrier spacing and symbol length/duration are a function of the numerology. The subcarrier spacing may be equal to 2^m * 15 kHz, where m is the numerology 0 to 4. As such, the numerology m=0 has a subcarrier spacing of 15 kHz and the numerology m=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of slot configuration 0 with 14 symbols per slot and numerology m=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 ps. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology.

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

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

[0045] FIG. 2B illustrates an example of various DL channels within a subframe of a frame.

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 including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET). A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a 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 a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block (also referred to as SS block (SSB)). The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PD SCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages.

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

[0047] FIG. 2D illustrates an example of various UL channels within a subframe of a frame.

The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information (ACK/ negative ACK (NACK)) feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and/or UCI.

[0048] FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), 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 functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), 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 functionality 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. [0049] 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 (BP SK), 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 maybe 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 318 TX. Each transmitter 318 TXmay modulate an RF carrier with a respective spatial stream for transmission.

[0050] At the UE 350, each receiver 354 RX receives a signal through its respective antenna 352. Each receiver 354 RX 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 comprises 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.

[0051] The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The 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 from the EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

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

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

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

[0055] The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The 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 from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HAR.Q operations.

[0056] 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 198 of FIG. 1.

[0057] 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 199 of FIG. 1.

[0058] Some wireless communication systems may include data packet expiration. In such communication systems, packets may be intended for transmission within a period of time. If the period of time expires before the packet is transmitted, the packet may be discarded and not transmitted. Such a communication system may experience a number of communication errors as a result of the packets expiring. For example, the communication errors may be due to packets expiring prior to proper reception of the transmitted packets. In a communication system without data packet expiration, communication errors may be due to buffers experience overloading rather than packet expiration. The communication system with packet expiration may experience an increase in errors under diminished, or poor, channel quality conditions. The diminished channel quality conditions may cause the data packets to expire prior to being correctly received. However, in instances of good, or high, quality channel conditions, errors may not occur. The network may not be able to detect levels of overloading when there are good channel conditions.

[0059] Aspects presented herein provide a configuration for improving the manner of detecting when the system may experience an increase in errors due to packet expiration and provides a way to determine a level of overloading without relying on packet errors. [0060] In some aspects, a UE may be configured to detect when errors may begin to increase by monitoring a scheduling delay for packets exchanged with a base station. Thus, the UE may monitor a history of scheduling delay in order to identify a level of loading that may lead to packet errors. In some aspects, the UE may monitor the scheduling delay on a per packet basis. The UE, upon the detection of a scheduling delay event, may be configured to request a change to address the loading. For example, the UE may request a change to another BWP in response to detecting a scheduling delay event. The UE may request a change to another cell in response to detecting a scheduling delay event. The UE may request a change to another carrier in response to detecting a scheduling delay event. The UE may request another type of scheduler (e.g., deadline aware scheduler) in response to detecting a scheduling delay event. The scheduling delay may be measured in any time unit, such as but not limited to, seconds, milliseconds, microseconds, frames, subframes, slots, OFDM symbols, clock ticks, or the like. In some instances, the scheduling delay event may comprise the last N correctly received packets, for which the UE detects M occurrences of a scheduling delay increase. In another example, the scheduling delay event may include the K last correctly received packets experiencing a scheduling delay greater than a percentage of a total delay budget. In another example, the scheduling may be based on a combination thereof. When the UE detects that a scheduling delay has occurred, the UE may send a notification to the base station to request a change. In response to the notification from the UE, the base station may make a change for the UE in accordance with the request provided in the received notification.

[0061] FIG. 4 is a diagram 400 illustrating a UE 402 in communication with one or more base stations 404, 406. In some aspects, the UE 402 may be in communication with more than one transmission reception point (TRP). FIG. 4 illustrates the base station 404 and the base station 406. In some aspects, the base station (e.g., 404, 406) may transmit data 408/410 to the UE 402. Upon receipt of the data 408, the UE 402 may determine the scheduling delay for each of a plurality of packets within the data 408/410. The UE may detect a scheduling delay event by determining that the scheduling delay for the plurality of packets within the data 408/410 meets a scheduling delay metric. In some aspects, the scheduling delay metric may include monitoring for the occurrence of an event, such as but not limited to, M occurrences of scheduling delay increase of the last N corrected received packets, and/or K last received packets experience a scheduling delay greater than a percentage amount of the delay budget. In some instances, the delay budget may be predetermined or may be configurable. Upon the detection of such an occurrence, the UE 402 may send a notification 412/414 to the base station 404/406 requesting a change of the BWP, the carrier, the cell, or a scheduler algorithm change request. The base station 404/406 responds accordingly and changes the UE 402 in accordance with the request. In some aspects, the notification 412/414 sent by the UE 402 to the base station 404/406 may be based on the number of NACKs for the plurality of packets within the data transmission 408/410.

[0062] FIG. 5 is a call flow diagram 500 of signaling between a UE 502 and a base station 504. The base station 504 may be configured to provide at least one cell. The UE 502 may be configured to communicate with the base station 504. For example, in the context of FIG. 1, the base station 504 may correspond to base station 102/180 and, accordingly, the cell may include a geographic coverage area 110 in which communication coverage is provided and/or small cell 102’ having a coverage area 110’. Further, a UE 502 may correspond to at least UE 104. In another example, in the context of FIG. 3, the base station 504 may correspond to base station 310 and the UE 502 may correspond to UE 350. Optional aspects are illustrated with a dashed line.

[0063] As illustrated at 506, the base station 504 may transmit or receive a plurality of packets with the UE 502. In some aspects, the plurality of packets may include uplink packets. In some aspects, the plurality of packets may include downlink packets.

[0064] As illustrated at 508, the UE 502 may determine a scheduling delay for each of a plurality of packets. The scheduling delay may account for the time difference between a time instant to, a time instant of a new packet at a transmitter buffer, and a time instant fi, a time instant of a packet scheduled for transmission. The transmitter buffer may be a buffer storing Transport Blocks located at physical layer, or (storing) MAC PDUs located at MAC layer, or (storing) RLC PDUs located at RLC layer, or (storing) PDCP PDUs located at PDCP layer, or any other buffer that can be imagined in layers 1-3 or a radio communication system, in which stored packets are scheduled from a scheduler located anywhere in layers 1-3 of a radio communication system. The scheduler may decide which of the stored packets to schedule based on radio conditions and/or traffic conditions criteria. [0065] As illustrated at 510, the UE 502 may determine that the scheduling delay for the plurality of packets meets a scheduling delay metric. In some aspects, the scheduling delay metric may include a threshold number of scheduling delay increases in a set of correctly received packets. The scheduling delay may be measured in any time units, such as but not limited to, seconds, milliseconds, microseconds, frames, subframes, slots, OFDM symbols, clock ticks, or the like. The set of correctly received packets may comprise a set of N correctly received packets, where N > 0, and the scheduling delay for a packet (e.g., packetl) is greater than or equal than the scheduling delay of a previous packet (e.g., packetO), the scheduling delay for a second packet (e.g., packet2) is greater than or equal in duration than the scheduling delay for packetl, wherein the scheduling delay for the Nth packet (e.g., packetN) is greater than or equal than the scheduling delay of the preceding packet (e.g., packetN-1). In some aspects, the scheduling delay metric may include a number of correctly received packets that experienced a scheduling delay meeting a threshold. In aspects where the plurality of packets include uplink packets, the scheduling delay may be based on an indication of a scheduling delay received from the base station. In some aspects, the scheduling delay may be based on a schedule from the base station that is delayed. In some aspects, the UE may be provided with a basis or an indication to identify a scheduling delay, but may or may not be provided with a schedule. In some aspects, the UE may measure time between consecutive transmissions associated with the same data to determine the scheduling delay. In such instances, the UE may measure whether the time between consecutive packets is increasing or relatively constant. In aspects where the plurality of packets include downlink packets, the scheduling delay may be determined based on jitter for each of the plurality of packets.

[0066] As illustrated at 512, the UE 502 may send a notification to the base station 504 based on a determination that the scheduling delay for the plurality of packets meets the scheduling delay metric. The base station 504 may receive the notification from the UE 502. In some aspects, the notification may include a request to change a bandwidth part, a cell, a carrier, or a type of scheduler. The UE 502 may send the notification to request a handover, transition, or change to a less loaded BWP, a less loaded cell, or request to be grouped in a group of UEs which may be scheduled according to a different scheduling policy/metric. In some aspects, the notification may include a measurement report for the scheduling delay. In some aspects, the notification may indicate a scheduling delay event. The scheduling delay event may include a scheduling delay increasing within a set of N received packets, a scheduling delay of the last M correctly received packets meeting the delay threshold, or the scheduling delay increasing within a set of N received packets and the scheduling delay of the last M correctly received packets meeting the delay threshold. The notification sent to the base station 504 may be in the form of at least one of a RRC message, aMAC-CE, or DCI. In some aspects, the notification sent to the base station 504 may be further based on a number of negative acknowledgements (NACKs) for the plurality of packets.

[0067] As illustrated at 514, the base station 504 may change a bandwidth part (BWP), a cell, a carrier, or a type of scheduler for the UE 502. The base station 504 may change the bandwidth part, the cell, the carrier, or the type of scheduler for the UE 502 in response to receiving the notification. In some aspects, the base station 504 may change the UE 502 to a less loaded BWP, a less loaded cell, or may group the UE 502 within a group of UEs that may be scheduled according to a different scheduling policy/metric.

[0068] FIG. 6 is a flowchart 600 of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., the UE 104, 402, 502; the apparatus 702; the cellular baseband processor 704, which may include the memory 360 and which may be the entire UE 350 or a component of the UE 350, such as the TX processor 368, the RX processor 356, and/or the controller/processor 359). One or more of the illustrated operations may be omitted, transposed, or contemporaneous. Optional aspects are illustrated with a dashed line. The method may enable a UE to detect that the system may experience an increase in errors due to expiration of packets.

[0069] At 602, the UE may determine a scheduling delay for each of a plurality of packets.

For example, 602 may be performed by schedule component 740 of apparatus 702. The UE may receive or transmit packets with a base station, such as described in connection with FIG. 4 and/or FIG. 5. In some aspects, the plurality of packets may include uplink packets. In some aspects, the plurality of packets may include downlink packets. The scheduling delay may account for the time difference between a time instant to, a time instant of a new packet at a transmitter buffer, and a time instant fi, a time instant of a packet scheduled for transmission. The transmitter buffer may be a buffer storing Transport Blocks located at physical layer, or (storing) MAC PDUs located at MAC layer, or (storing) RLC PDUs located at RLC layer, or (storing) PDCP PDUs located at PDCP layer, or any other buffer that can be imagined in layers 1-3 or a radio communication system, in which stored packets are scheduled from a scheduler located anywhere in layers 1-3 of a radio communication system. The scheduler may decide which of the stored packets to schedule based on radio conditions and/or traffic conditions criteria.

[0070] At 604, the UE may determine that the scheduling delay for the plurality of packets meets a scheduling delay metric. For example, 604 may be performed by determination component 742 of apparatus 702. The determination may include aspects described in connection with 510 in FIG. 5, for example. In some aspects, the scheduling delay metric may include a threshold number of scheduling delay increases in a set of correctly received packets. The scheduling delay may be measured in any time units, such as but not limited to, seconds, milliseconds, microseconds, frames, subframes, slots, OFDM symbols, clock ticks, or the like. The set of correctly received packets may comprise a set of N correctly received packets, where N > 0, and the scheduling delay for a packet (e.g., packetl) is greater than or equal than the scheduling delay of a previous packet (e.g., packetO), the scheduling delay for a second packet (e.g., packet2) is greater than or equal in duration than the scheduling delay for packetl, wherein the scheduling delay for the Nth packet (e.g., packetN) is greater than or equal than the scheduling delay of the preceding packet (e.g., packetN-1). In some aspects, the scheduling delay metric may include a number of correctly received packets that experienced a scheduling delay meeting a threshold. In aspects where the plurality of packets include uplink packets, the scheduling delay may be based on an indication of a scheduling delay received from the base station. In some aspects, the scheduling delay may be based on a schedule from the base station that is delayed. In some aspects, the UE may be provided with a basis or an indication to identify a scheduling delay, but may or may not be provided with a schedule. In some aspects, the UE may measure time between consecutive transmissions associated with the same data to determine the scheduling delay. In such instances, the UE may measure whether the time between consecutive packets is increasing or relatively constant. In aspects where the plurality of packets include downlink packets, the scheduling delay may be determined based on jitter for each of the plurality of packets.

[0071] At 606, the UE may send a notification to a base station based on a determination that the scheduling delay for the plurality of packets meets the scheduling delay metric. For example, 606 may be performed by notification component 744 of apparatus 702. The notification may include aspects described in connection with any of 412, 414, and/or 512 in FIGs. 4 and 5. In some aspects, the notification may include a request to change a bandwidth part, a cell, a carrier, and/or a type of scheduler. The UE may send the notification to request a handover, transition, or change to a less loaded BWP or a less loaded cell. The UE may request to be grouped in a group of UEs which may be scheduled according to a different scheduling policy/metric. In some aspects, the notification may include a measurement report for the scheduling delay. In some aspects, the notification may indicate a scheduling delay event. The scheduling delay event may include a scheduling delay increasing within a set of N received packets, a scheduling delay of the last M correctly received packets meeting the delay threshold, or the scheduling delay increasing within a set of N received packets and the scheduling delay of the last M correctly received packets meeting the delay threshold. In some aspects, the notification may include a handover request, such as but not limited to a UE originated handover request. The UE originated handover request may be sent in an RRC message and may comprise fields indicating the reason and/or the event that triggered the UE originated handover request. The notification sent to the base station may be in the form of at least one of a RRC message, a MAC-CE, or DCI. In some aspects, the notification sent to the base station may be further based on a number of NACKs for the plurality of packets. Thus, in some aspects, the UE may determine whether to send a notification or request a change based on a determined scheduling delay in combination with NACK information [0072] FIG. 7 is a diagram 700 illustrating an example of a hardware implementation for an apparatus 702. The apparatus 702 is a UE and includes a cellular baseband processor 704 (also referred to as a modem) coupled to a cellular RF transceiver 722 and one or more subscriber identity modules (SIM) cards 720, an application processor 706 coupled to a secure digital (SD) card 708 and a screen 710, a Bluetooth module 712, a wireless local area network (WLAN) module 714, a Global Positioning System (GPS) module 716, and a power supply 718. The cellular baseband processor 704 communicates through the cellular RF transceiver 722 with the UE 104 and/or BS 102/180. The cellular baseband processor 704 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 704 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 704, causes the cellular baseband processor 704 to perform the various functions described supra. The computer-readable medium / memory may also be used for storing data that is manipulated by the cellular baseband processor 704 when executing software. The cellular baseband processor 704 further includes a reception component 730, a communication manager 732, and a transmission component 734. The communication manager 732 includes the one or more illustrated components. The components within the communication manager 732 may be stored in the computer- readable medium / memory and/or configured as hardware within the cellular baseband processor 704. The cellular baseband processor 704 may be a component of the UE 350 and may include the 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 702 may be a modem chip and include just the cellular baseband processor 704, and in another configuration, the apparatus 702 may be the entire UE (e.g., see 350 of FIG. 3) and include the aforediscussed additional modules of the apparatus 702.

[0073] The communication manager 732 includes a schedule component 740 that is configured to determine a scheduling delay for each of a plurality of packets, e.g., as described in connection with 602 of FIG. 6. The communication manager 732 further includes a determination component 742 that is configured to determine that the scheduling delay for the plurality of packets meets a scheduling delay metric, e.g., as described in connection with 604 of FIG. 6. The communication manager 732 further includes a notification component 744 that is configured to send a notification to a base station based on a determination that the scheduling delay for the plurality of packets meets the scheduling delay metric, e.g., as described in connection with 606 of FIG. 6.

[0074] The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowchart of FIG. 6. As such, each block in the aforementioned flowchart of FIG. 6 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof. [0075] In one configuration, the apparatus 702, and in particular the cellular baseband processor 704, includes means for determining a scheduling delay for each of a plurality of packets. The apparatus includes means for determining that the scheduling delay for the plurality of packets meets a scheduling delay metric. The apparatus includes means for sending a notification to a base station based on a determination that the scheduling delay for the plurality of packets meets the scheduling delay metric. The aforementioned means may be one or more of the aforementioned components of the apparatus 702 configured to perform the functions recited by the aforementioned means. As described supra , the apparatus 702 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

[0076] FIG. 8 is a flowchart 800 of a method of wireless communication. The method may be performed by a base station or a component of abase station (e.g., the base station 102/180, 404, 406, 504; the apparatus 902; the baseband unit 904, which may include the memory 376 and which may be the entire base station 310 or a component of the base station 310, such as the TX processor 316, the RX processor 370, and/or the controller/processor 375). One or more of the illustrated operations may be omitted, transposed, or contemporaneous. Optional aspects are illustrated with a dashed line. The method may allow a base station to change the conditions or resource configuration of a UE in response to an increase of scheduling delay.

[0077] At 802, the base station may transmit or receive a plurality of packets with a UE. For example, 802 may be performed by packet component 940 of apparatus 902. The base station may transmit or receive communication with the UE, such as described in connection with FIG. 4 and/or FIG. 5. In some aspects, the plurality of packets received by the base station may include uplink packets. In some aspects, the plurality of packets transmitted by the base station may include downlink packets.

[0078] At 804, the base station may receive a notification from the UE. For example, 804 may be performed by notification component 942 of apparatus 902. The notification may be based on a scheduling delay for the plurality of packets that meet a scheduling delay metric. The scheduling delay may account for the time difference between the time instant to, time instant of new packet at the transmitter buffer and the time instant ti, time instant of the packet being scheduled for transmission. In some aspects, the notification may include a request to change a bandwidth part, a cell, a carrier, or a type of scheduler. In some aspects, the notification may include a measurement report for the scheduling delay. The scheduling delay may be measured in a time unit such as any of seconds, milliseconds, microseconds, frames, subframes, slots, OFDM symbols, clock ticks, etc. In some aspects, the notification may indicate a scheduling delay event. In some aspects, the notification may include a handover request. The notification received from the UE may be in the form of at least one of a RRC message, a MAC-CE, or DCI. FIG. 4 illustrates 412 or 414, which may correspond to the notification in 804, and FIG. 5 illustrates an example notification 512 that is sent by the UE 502 to the base station 504.

[0079] At 806, the base station may change a bandwidth part, a cell, a carrier, or a type of scheduler for the UE. For example, 806 may be performed by change component 944 of apparatus 902. The base station may change the bandwidth part, the cell, the carrier, or the type of scheduler for the UE in response to receiving the notification. The base station may hand the UE over to a different cell in response to receiving the notification from the UE. The change may include aspects described in connection with 514 in FIG. 5, for example.

[0080] FIG. 9 is a diagram 900 illustrating an example of a hardware implementation for an apparatus 902. The apparatus 902 is a BS and includes a baseband unit 904. The baseband unit 904 may communicate through a cellular RF transceiver 922 with the UE 104. The baseband unit 904 may include a computer-readable medium / memory. The baseband unit 904 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the baseband unit 904, causes the baseband unit 904 to perform the various functions described supra. The computer-readable medium / memory may also be used for storing data that is manipulated by the baseband unit 904 when executing software. The baseband unit 904 further includes a reception component 930, a communication manager 932, and a transmission component 934. The communication manager 932 includes the one or more illustrated components. The components within the communication manager 932 may be stored in the computer- readable medium / memory and/or configured as hardware within the baseband unit 904. The baseband unit 904 may be a component of the BS 310 and may include the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375. [0081] The communication manager 932 includes a packet component 940 that may transmit or receive a plurality of packets with a UE, e.g., as described in connection with 802 of FIG. 8. The communication manager 932 further includes a notification component 942 that may receive a notification from the UE, e.g., as described in connection with 804 of FIG. 8. The communication manager 932 further includes a change component 944 that may change a bandwidth part, a cell, a carrier, or a type of scheduler for the UE, e.g., as described in connection with 806 of FIG. 8.

[0082] The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowchart of FIG. 8. As such, each block in the aforementioned flowchart of FIG. 8 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

[0083] In one configuration, the apparatus 902, and in particular the baseband unit 904, includes means for transmitting or receiving a plurality of packets with a UE. The apparatus includes means for receiving a notification from the UE. The notification may be based on a scheduling delay for the plurality of packets meets a scheduling delay metric. The apparatus includes means for changing a bandwidth part, a cell, a carrier, or a type of scheduler for the UE in response to receiving the notification. The aforementioned means may be one or more of the aforementioned components of the apparatus 902 configured to perform the functions recited by the aforementioned means. As described supra, the apparatus 902 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375. As such, in one configuration, the aforementioned means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the aforementioned means.

[0084] 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 meant to be limited to the specific order or hierarchy presented.

[0085] The following examples are illustrative only and may be combined with aspects of other embodiments or teachings described herein, without limitation.

[0086] Aspect 1 is a method of wireless communication at a UE comprising determining a scheduling delay for each of a plurality of packets; determining that the scheduling delay for the plurality of packets meets a scheduling delay metric; and sending a notification to a base station based on a determination that the scheduling delay for the plurality of packets meets the scheduling delay metric.

[0087] In Aspect 2, the method of Aspect 1 further includes that the scheduling delay metric includes a threshold number of scheduling delay increases in a set of correctly received packets.

[0088] In Aspect 3, the method of Aspect 1 or 2 further includes that the scheduling delay metric includes a number of correctly received packets that experienced a scheduling delay meeting a threshold.

[0089] In Aspect 4, the method of any of Aspects 1-3 further includes that the notification includes a request to change a bandwidth part, a cell, a carrier, or a type of scheduler.

[0090] In Aspect 5, the method of any of Aspects 1-4 further includes that the notification includes a measurement report for the scheduling delay.

[0091] In Aspect 6, the method of any of Aspects 1-5 further includes that the notification indicates a scheduling delay event.

[0092] In Aspect 7, the method of any of Aspects 1-6 further includes that the notification includes a handover request.

[0093] In Aspect 8, the method of any of Aspects 1-7 further includes that the notification is sent to the base station in at least one of an RRC message, a MAC-CE, or DCI.

[0094] In Aspect 9, the method of any of Aspects 1-8 further includes that the plurality of packets include uplink packets, and wherein the scheduling delay is based on indication of a scheduling delay that is received from the base station.

[0095] In Aspect 10, the method of any of Aspects 1-9 further includes that the plurality of packets include downlink packets, and wherein the scheduling delay is determined based on jitter for each of the plurality of packets.

[0096] In Aspect 11, the method of any of Aspects 1-10 further includes that the notification is sent to the base station further based on a number of NACKs for the plurality of packets. [0097] Aspect 12 is a device including one or more processors and one or more memories in electronic communication with the one or more processors storing instructions executable by the one or more processors to cause the system or apparatus to implement a method as in any of Aspects 1-11.

[0098] Aspect 13 is a system or apparatus including means for implementing a method or realizing an apparatus as in any of Aspects 1-11.

[0099] Aspect 14 is a non-transitory computer readable medium storing instructions executable by one or more processors to cause the one or more processors to implement a method as in any of Aspects 1-11.

[00100] Aspect 15 is a method of wireless communication at a base station comprising transmitting or receiving a plurality of packets with a UE; receiving a notification from the UE, wherein the notification is based on a scheduling delay for the plurality of packets meets a scheduling delay metric; and changing a bandwidth part, a cell, a carrier, or a type of scheduler for the UE in response to receiving the notification.

[00101] In Aspect 16, the method of Aspect 15 further includes that the notification includes a request to change a bandwidth part, a cell, a carrier, or a type of scheduler.

[00102] In Aspect 17, the method of Aspect 15 or 16 further includes that the notification includes a measurement report for the scheduling delay.

[00103] In Aspect 18, the method of any of Aspects 15-17 further includes that the notification indicates a scheduling delay event.

[00104] In Aspect 19, the method of any of Aspects 15-18 further includes that the notification includes a handover request.

[00105] In Aspect20, the method of any of Aspects 15-19 further includes that the notification is received from the UE in at least one of an RRC message, a MAC-CE, or DCI.

[00106] Aspect 21 is a device including one or more processors and one or more memories in electronic communication with the one or more processors storing instructions executable by the one or more processors to cause the system or apparatus to implement a method as in any of Aspects 15-20.

[00107] Aspect 22 is a system or apparatus including means for implementing a method or realizing an apparatus as in any of Aspects 15-20.

[00108] Aspect 23 is a non-transitory computer readable medium storing instructions executable by one or more processors to cause the one or more processors to implement a method as in any of Aspects 15-20. [00109] 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 intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” should be interpreted to mean “under the condition that” rather than 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. 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 intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be 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.”

Claims

CLAIMS WHAT IS CLAIMED IS:

1. A method of wireless communication at a user equipment (UE), comprising: determining a scheduling delay for each of a plurality of packets; determining that the scheduling delay for the plurality of packets meets a scheduling delay metric; and sending a notification to a base station based on a determination that the scheduling delay for the plurality of packets meets the scheduling delay metric.

2. The method of claim 1, wherein the scheduling delay metric includes a threshold number of scheduling delay increases in a set of correctly received packets.

3. The method of claim 1, wherein the scheduling delay metric includes a number of correctly received packets that experienced a scheduling delay meeting a threshold.

4. The method of claim 1, wherein the notification includes a request to change a bandwidth part, a cell, a carrier, or a type of scheduler.

5. The method of claim 1, wherein the notification includes a measurement report for the scheduling delay.

6. The method of claim 1, wherein the notification indicates a scheduling delay event.

7. The method of claim 1, wherein the notification includes a handover request.

8. The method of claim 1, wherein the notification is sent to the base station in at least one of: a radio resource control (RRC) message, a medium access control-control element (MAC-CE), or downlink control information (DCI).

9. The method of claim 1, wherein the plurality of packets include uplink packets, and wherein the scheduling delay is based on indication of a scheduling delay that is received from the base station.

10. The method of claim 1, wherein the plurality of packets include downlink packets, and wherein the scheduling delay is determined based on jitter for each of the plurality of packets.

11. The method of claim 1, wherein the notification is sent to the base station further based on a number of negative acknowledgements (NACKs) for the plurality of packets.

12. An apparatus for wireless communication at a user equipment (UE), comprising: a memory; and at least one processor coupled to the memory and configured to: determine a scheduling delay for each of a plurality of packets; determine that the scheduling delay for the plurality of packets meets a scheduling delay metric; and send a notification to a base station based on a determination that the scheduling delay for the plurality of packets meets the scheduling delay metric.

13. The apparatus of claim 12, wherein the scheduling delay metric includes a threshold number of scheduling delay increases in a set of correctly received packets.

14. The apparatus of claim 12, wherein the scheduling delay metric includes a number of correctly received packets that experienced a scheduling delay meeting a threshold.

15. The apparatus of claim 12, wherein the notification includes a request to change a bandwidth part, a cell, a carrier, or a type of scheduler.

16. The apparatus of claim 12, wherein the notification includes a measurement report for the scheduling delay.

17. The apparatus of claim 12, wherein the notification indicates a scheduling delay event.

18. The apparatus of claim 12, wherein the notification includes a handover request.

19. The apparatus of claim 12, wherein the notification is sent to the base station in at least one of: a radio resource control (RRC) message, a medium access control-control element (MAC-CE), or downlink control information (DCI).

20. The apparatus of claim 12, wherein the plurality of packets include uplink packets, and wherein the scheduling delay is based on indication of a scheduling delay that is received from the base station.

21. The apparatus of claim 12, wherein the plurality of packets include downlink packets, and wherein the scheduling delay is determined based on jitter for each of the plurality of packets.

22. The apparatus of claim 12, wherein the notification is sent to the base station further based on a number of negative acknowledgements (NACKs) for the plurality of packets.

23. A method of wireless communication at a base station, comprising: transmitting or receiving a plurality of packets with a user equipment (UE); receiving a notification from the UE, wherein the notification is based on a scheduling delay for the plurality of packets meets a scheduling delay metric; and changing a bandwidth part, a cell, a carrier, or a type of scheduler for the UE in response to receiving the notification.

24. The method of claim 23, wherein the notification includes a request to change a bandwidth part, a cell, a carrier, or a type of scheduler.

25. The method of claim 23, wherein the notification includes a measurement report for the scheduling delay.

26. The method of claim 23, wherein the notification indicates a scheduling delay event.

27. The method of claim 23, wherein the notification includes a handover request.

28. The method of claim 23, wherein the notification is received from the UE in at least one of: a radio resource control (RRC) message, a medium access control-control element (MAC-CE), or downlink control information (DCI).

29. An apparatus for wireless communication at a base station, comprising: a memory; and at least one processor coupled to the memory and configured to: transmit or receiving a plurality of packets with a user equipment (UE); receive a notification from the UE, wherein the notification is based on a scheduling delay for the plurality of packets meets a scheduling delay metric; and change a bandwidth part, a cell, a carrier, or a type of scheduler for the UE in response to receiving the notification.