Enhanced UE behavior for BFD / BFR in DRX mode

Abstract

The UE identifies (914) that a first condition is satisfied during a first DRX on period immediately prior to an existing DRX off period. The UE sends (916) a request to a network node to extend the first DRX on period based on satisfying the first condition, and the network node may receive the request from the UE. The network node sends (918) an indication of approval of the request to extend the first DRX on period to the UE, and the UE may receive the indication from the network node. The UE and the network node delay (920) a start of the existing DRX off period for a first period of time based on the approval of the request to extend the first DRX on period.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 657,594, entitled “ENHANCED UE BEHAVIOR FOR BFD / BFR IN DRX MODE” and filed on March 31, 2022, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to a discontinuous reception (DRX) mode in a wireless communication system. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. 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.

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

[0006] A simplified overview of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary is neither intended to identify key or important elements of all aspects, nor to describe 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 a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE). The apparatus may identify that a first condition is satisfied during a first DRX on period immediately preceding an existing discontinuous reception (DRX) off period. The apparatus may send a request to a network node to extend the first DRX on period based on satisfying the first condition. The apparatus may receive an indication of approval of the request to extend the first DRX on period from the network node. The apparatus may, based on the approval of the request to extend the first DRX on period, delay the start of the existing DRX off period by a first time period.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a network node. The apparatus may receive from a UE a request to extend a first DRX on period immediately preceding an existing DRX off period based on satisfying a first condition. The apparatus may send to the UE an indication of approval of the request to extend the first DRX on period. The apparatus may, based on approval of the request to extend the first DRX on period, delay the start of the existing DRX off period by a first time period.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0016] Figure 4 is a diagram illustrating an example BFD process.

[0017] Figure 5 is a diagram illustrating an example timeline associated with a DRX mode.

[0018] Fig. 6A and Figure 6B is a diagram illustrating an example process for extending a current DRX On period.

[0019] Figure 7 is a diagram illustrating an example process for sending a beam failure warning report in association with a DRX mode.

[0020] Fig. 8A and Figure 8B is a diagram illustrating an example procedure for waking up during an existing DRX off period.

[0021] Fig. 9 The present invention is a diagram showing a communication flow of a wireless communication method.

[0022] Fig.10 is a flow chart of a method of wireless communication.

[0023] Fig.11 is a flow chart of a method of wireless communication.

[0024] Fig.12 is a flow chart of a method of wireless communication.

[0025] Fig.13 is a flow chart of a method of wireless communication.

[0026] Fig.14 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0027] Fig.15 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0028] Beamforming may be a common technique in wireless communications. With beamforming, the transmission energy may be concentrated in a certain direction between the UE and the base station / network node to compensate for potential large data losses in high frequencies. In addition, in order to maintain good quality of the communication beam, beam fault detection (BFD) and beam fault recovery (BFR) procedures may be utilized. When the UE is configured with a DRX mode, because the UE may not monitor the physical downlink control channel (PDCCH) during the DRX off period, the UE may not correctly perform the BFD / BFR procedure during the DRX off period because the BFD-RS used in the BFD procedure is transmitted via the PDCCH.

[0029] In one or more configurations, the UE may identify that a first condition is satisfied during a first DRX on period immediately preceding an existing DRX off period. The UE may send a request to a network node to extend the first DRX on period based on satisfying the first condition, and the network node may receive the request from the UE. The network node may send an indication of approval of the request to extend the first DRX on period to the UE, and the UE may receive the indication from the network node. The UE and the network node may delay the start of the existing DRX off period for a first time period based on approval of the request to extend the first DRX on period. Thus, the accuracy associated with the BFD / BFR process may be improved. In addition, during a portion of the initially scheduled DRX off period (DRX on extension period), there may be more time for the UE to perform BFD-RS monitoring to confirm beam failure.

[0030] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the detailed description includes specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0031] Several aspects of telecommunication systems are presented with reference to various apparatuses and methods. These apparatuses 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 these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

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

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

[0034] Although various aspects, specific implementations and / or use cases are described in this application by the illustrations of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some practical environments, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0035] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. 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) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

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

[0037] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

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

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

[0040] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by CU 110. CU110 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 specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0041] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, 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 and demodulation, etc.) depending at least in part on a functional split (such as a functional split defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0042] The lower layer functions may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the 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, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0043] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements 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, which may be managed via an operation 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 lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 111, via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

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

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

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

[0047] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

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

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

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

[0051] In view of the above, unless otherwise specified, if the term "below 6 GHz" or the like is used in this document, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" or the like is used in this document, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0052] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send 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 send 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 direction and the best transmit direction for each of the base station 102 / UE 104. The transmit direction and the receive direction of the base station 102 may be the same, or may be different. The transmit direction and the receive direction of the UE 104 may be the same, or may be different.

[0053] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may 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 a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0054] 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. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. 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, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a satellite system 170 (e.g., one or more of a global navigation satellite system (GNSS), a satellite positioning system (SPS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, 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 one or more of other systems / signals / sensors.

[0055] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terms. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0056] See again Figure 1 In certain aspects, the UE 104 may include a DRX component 198 that may be configured to identify that a first condition is satisfied during a first DRX on period that immediately precedes an existing DRX off period. The DRX component 198 may be configured to send a request to a network node to extend the first DRX on period based on satisfying the first condition. The DRX component 198 may be configured to receive an indication of approval of the request to extend the first DRX on period from the network node. The DRX component 198 may be configured to delay the start of the existing DRX off period for a first time period based on the approval of the request to extend the first DRX on period. In certain aspects, the base station 102 may include a DRX component 199 that may be configured to receive a request from the UE to extend the first DRX on period that immediately precedes the existing DRX off period based on satisfying the first condition. The DRX component 199 may be configured to send an indication of approval of the request to extend the first DRX on period to the UE. The DRX component 199 may be configured to delay the start of the existing DRX off period for a first time period based on the approval of the request to extend the first DRX on period. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

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

[0058] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various aspects of the present disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes (1ms) of the same size. Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0059]

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

[0061] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0063] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. A 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 a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also called SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as the system information block (SIB)), and paging messages.

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

[0065] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0066] Figure 3370 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery 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.

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

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

[0069] The controller / processor 359 may be associated with 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 channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0070] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer 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.

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

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

[0073] The controller / processor 375 may be associated with 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 channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

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

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

[0076] Beamforming may be a common technique in wireless communications. With beamforming, the transmission energy may be concentrated in a certain direction between the UE and the base station / network node to compensate for potential large data loss in high frequencies. In addition, in order to maintain good quality of the communication beam, BFD and BFR processes may be utilized.

[0077] Figure 4 400 is a diagram illustrating an example BFD process. The radio link between the UE and the base station may be susceptible to blockage and degradation of the RF signal, which may interrupt the communication link and cause beam failure. The UE may detect the beam failure in the BFD process and may attempt to recover from the beam failure with the help of the BFR process. The BFD process and the BFR process may be a joint effort of the UE PHY layer 402 and MAC layer 404 processes without involving higher layer signaling.

[0078] In particular, if the UE communicates with the base station using a beam pair (which may include one UE beam and one base station beam), the base station may periodically send a BFD-RS 406 to the UE using the corresponding base station beam (e.g., via the PDCCH). For example, the BFD-RS may be a CSI-RS or an SSB. At each BFD-RS opportunity (i.e., an opportunity when the base station sends the BFD-RS), the UE may measure the BFD-RS using the corresponding UE beam. Based on the measurement, if the estimated assumed PDCCH block error rate (BLER) is greater than a threshold (e.g., 10%) (which may indicate that the radio link quality associated with the UE beam is less than the corresponding threshold), the UE PHY layer 402 may report a beam failure instance (BFI) to the UE MAC layer 404.

[0079] The UE MAC layer 404 may count indications of BFI from the UE PHY layer 402 (i.e., BFI indications), and may initiate a BFR process when the BFI counter has reached or exceeded a configured BFI counter threshold (e.g., the value of the "maxCount" parameter). Specifically, each time the UE MAC layer 404 receives an indication of BFI from the UE PHY layer 402, the UE MAC layer 404 may start or restart a timer (e.g., a BFD timer) and may increment the BFI counter by 1. When the BFI counter reaches or exceeds the corresponding BFI counter threshold (e.g., in the illustrated example, the BFI counter threshold may be 3), the UE MAC layer 404 may declare a beam failure, and the UE MAC layer 404 may initiate a BFR process to attempt to recover from the beam failure. During the BFR process, the UE may perform a random access channel (RACH) process using a new candidate beam. If the UE MAC layer 404 does not receive an additional BFI indication before the timer (e.g., BFD timer) expires, the UE MAC layer 404 may reset the BFI counter (e.g., to "0"). In other words, if a certain period of time has passed since the last BFI indication without receiving an additional BFI indication from the UE PHY layer 402, the UE MAC layer 404 may assume that there is no beam failure.

[0080] Figure 5 500 is a diagram illustrating an example timeline associated with a DRX mode. In order to reduce power consumption, the UE may be configured with a DRX mode. In particular, based on the DRX mode, the UE may be configured with periodic and alternating DRX on periods 502 and DRX off periods 504. The UE may wake up and may remain active during each DRX on period in the DRX on period 502. The UE may monitor the PDCCH during the DRX on period 502 of the UE to find out whether there is an uplink or downlink data transmission scheduled for the UE. Herein, the DRX on period 502 may also be referred to as the DRX on duration. In contrast, the UE may enter a sleep state during each DRX off period in the DRX off period 504. The UE may not monitor the PDCCH during the DRX off period of the UE.

[0081] Therefore, since the UE may not monitor the PDCCH during the DRX off period 504, the UE may incorrectly perform the BFD / BFR procedure during the DRX off period 504 because the BFD-RS used in the BFD procedure is transmitted via the PDCCH.

[0082] Fig. 6A and Figure 6B600A and 600B are diagrams illustrating an example process for extending the current DRX on period. The UE may perform a BFD process based on the BFD-RS 606. In one or more configurations, when a condition (e.g., a trigger condition) is met, the UE may request an extension of the current DRX on period 602. In one or more configurations, when less than a pre-specified time period (e.g., y ms) remains until the end of the current DRX on period 602, it may be identified whether the condition is met. In one configuration, the condition may be met if the current BFI count is greater than a corresponding threshold. In one configuration, the condition may be met if more than a pre-specified number (e.g., N) of consecutive BFAs have been recorded during the current BFD session. In one configuration, the condition may be met if the UE identifies a (sudden) channel strength drop (decrease) greater than a corresponding threshold (e.g., x dB).

[0083] In one or more configurations, if the conditions are met, the UE may send a request 608 for an extension of the current DRX On period 602 to the network node (e.g., via a MAC-Control Element (CE) (MAC-CE) or a UCI message). After sending the request 608 for an extension of the current DRX On period 602, the UE may monitor a response from the network node. The UE may receive a response 610 to the request 608 for an extension of the current DRX On period 602 from the network node. For example, the response 610 may indicate an approval of the request 608 for an extension of the current DRX On period 602. In another example, the response 610 may indicate a rejection of the request 608 for an extension of the current DRX On period 602.

[0084] In one or more configurations in which the request 608 is approved, in addition to the approval of the request 608 for the extension of the current DRX on period 602, the response 610 may also indicate that a pre-specified DRX on extension period / value (corresponding to the length of the period in which the DRX on duration is extended) can be used for the approved extension. Therefore, the UE may be pre-configured with one or more pre-specified DRX on extension periods / values. In one or more configurations, the response 610 may also indicate a new DRX on extension period / value associated with the approval. For example, if the UE is not pre-configured with a DRX on extension period / value, or if the network node chooses to change a DRX on extension period / value pre-configured with the UE, a new DRX on extension period / value may be indicated. In one or more configurations, the UE may extend the current DRX on period 602 (e.g., the current DRX on period 602 may be extended to include a DRX on extension period 602a) based on the configured or pre-specified DRX on extension period / value.

[0085] In one or more configurations, the response 610 may indicate a rejection of the request 608 for an extension of the current DRX On period 602. Thus, if the response 610 indicates a rejection, the UE may enter an existing (e.g., pre-configured) DRX Off period 604 at the end of the current DRX On period 602 as originally configured, without extending the current DRX On period 602. Furthermore, the UE may wake up at the next DRX On period 602' at the end of the existing DRX Off period 604 as originally configured.

[0086] In one or more configurations, the network node may configure the UE with one or more DRX on period extension configurations (e.g., via RRC signaling). For example, in one or more configurations, the network node may configure the UE with a condition that may trigger the UE to send a request 608 for an extension of the current DRX on period (e.g., via RRC signaling). In one or more configurations, the network node may pre-configure the UE with one or more pre-specified DRX on extension periods / values ​​(e.g., the duration of the DRX on extension period 602a) (e.g., via RRC signaling). In one or more configurations, the network node may pre-configure the UE with multiple options for at least some of the above configuration parameters (e.g., via RRC signaling), and may use MAC-CE or DCI messages to switch between configuration options.

[0087] Thus, the accuracy associated with the BFD / BFR process can be improved. In addition, during a portion of the initially scheduled DRX off period (which may correspond to a DRX on extended period), there may be more time for the UE to perform BFD-RS monitoring in order to confirm a beam failure. Thus, a more timely or faster BFR may be performed where appropriate, while redundant BFR processes may be avoided. In addition, future beam quality may be improved. In particular, using UE-triggered reporting, the network may have a more comprehensive understanding of the UE's BFD status and may select a more suitable beam for the UE in the future. Additional advantages may include improved quality of service (QoS), enhanced beam connection consistency, reduced latency, and / or improved reliability.

[0088] Return to see Figure 5, if during the DRX off period 504, the UE wants to communicate with the network node about a specific situation before the next DRX on period 502, the UE may experience difficulties. For example, in virtual reality (VR) / augmented reality (VR) / extended reality (XR) applications, it may be appropriate or desirable to send attitude update information in a timely manner (e.g., with a cutoff time of 10ms). In such a case, the pre-configured DRX off period may be too long (e.g., the pre-configured DRX off period may be approximately 70ms long). In addition, in this case, it may be appropriate or desirable for the UE to maintain satisfactory beam conditions even during the DRX off period, so that fast attitude updates can be achieved when appropriate. It should be understood that during the DRX off period 504, the resources available to the UE may be limited. In addition, the network node may assume that the UE is asleep during the DRX off period 504 based on the DRX configuration, and therefore may not monitor signaling from the UE.

[0089] Return to see Fig. 6A and Figure 6B In one or more configurations, when a condition (e.g., a triggering condition) is met, the UE may request an extension of the current DRX On period 602. In one or more configurations, when less than a pre-specified time period (e.g., x ms) remains until the end of the current DRX On period 602, it may be identified whether the condition is met. In one configuration, the condition may be met if the UE has new uplink data to send to the network node (which transmission may not be completed within the current DRX On period 602 as initially configured) and chooses not to wait for the next DRX On period to complete the transmission (e.g., due to QoS specifications). In one configuration, the condition may be met if the UE is aware that the network node has more data to send to the UE (which transmission may not be completed within the current DRX On period 602 as initially configured) and chooses to receive the data during the current DRX On period 602. In one configuration, the condition may be met if the UE predicts a potential beam failure between the UE and the network node, which may occur during an existing DRX Off period 604 immediately following the current DRX On period 602.

[0090] In one or more configurations, similar to the configurations described above, if the conditions are met, the UE may send a request 608 to the network node for an extension of the current DRX On period 602 (e.g., via a MAC-CE or UCI message). After sending the request 608 for an extension of the current DRX On period 602, the UE may monitor a response from the network node. The UE may receive a response 610 to the request 608 for an extension of the current DRX On period 602 from the network node.

[0091] In one or more configurations, the network node may configure the UE with one or more DRX on period extension configurations (e.g., via RRC signaling). For example, in one or more configurations, the network node may configure the UE with one or more conditions that may trigger the UE to send a DRX on period extension request 608 to the network node (e.g., via RRC signaling). In one or more configurations, the network node may configure the UE with a format (content format) of the DRX on period extension request 608 (e.g., via RRC signaling). In particular, the content of the DRX on period extension request 608 may be different based on the condition that triggers the request 608. For example, different MAC-CEs may be used for different triggering conditions or causes. In one or more configurations, the network node may configure the UE with one or more pre-configured DRX on extension periods / values ​​(e.g., xms, a period / value pool including {a, b, c, ...} (ms), etc.) (e.g., via RRC signaling). In one or more configurations, the network node may configure the UE (e.g., via RRC signaling) with a signaling method (e.g., MAC-CE or UCI) for sending the request 608 to the network node. In one or more configurations, the network node may configure the UE (e.g., via RRC signaling) with resources that the UE may use to send the request 608. In one or more configurations, the network node may configure the UE (e.g., via RRC signaling) with resources that the UE may monitor for a response to the DRX on period extension request 608 from the network node. In one or more configurations, the network node may pre-configure the UE (e.g., via RRC signaling) with multiple options for at least some of the above configuration parameters, and may use MAC-CE or DCI messages to switch between configuration options.

[0092] In one or more configurations, the condition that may trigger the DRX on period extension request 608 may be an urgent new uplink or downlink data transmission, which may not wait until the next DRX on period. Therefore, in order to send a response 610 to the DRX on period extension request 608 triggered by the new data transmission, the network node may send an indication to the UE via the PDCCH before the end of the current DRX on period 602 to enable or authorize the extension of the current DRX on period 602. In addition to the approval of the DRX on period extension request 608, if the urgent new data transmission is in the uplink, the network node may also send an uplink grant for the new uplink data transmission from the UE to the UE. If the urgent new data transmission is in the downlink, the network node may also send an indication of the downlink data transmission to the UE.

[0093] In one or more configurations, the inactivity timer duration may be reused as the DRX On extension period / value. In one or more configurations, the network node may indicate a pre-specified DRX On extension period / value according to a pre-configuration, or may indicate a new DRX On extension period / value.

[0094] In one or more configurations, the condition that may trigger the DRX on period extension request 608 may be a predicted beam failure. Thus, the network node may indicate to the UE that the UE may monitor the BFD-RS during the DRX on extension period 602a. In some configurations, the network node may also indicate to the UE that the UE may not monitor other PDCCH indications that do not include the BFD-RS during the DRX on extension period 602a. Thus, the UE may save power because it may not monitor other PDCCH indications during the DRX on extension period 602a. In one or more configurations, the network node may indicate a pre-specified DRX on extension period / value according to a pre-configuration, or may indicate a new DRX on extension period / value.

[0095] In one or more configurations, the UE or the network node may activate or deactivate the process / mechanism of the UE-triggered DRX on period extension. In particular, the UE may send a request to the network node via a MAC-CE or UCI message to activate or deactivate the mechanism of the UE-triggered DRX on period extension. In addition, the network node may activate or deactivate the mechanism of the UE-triggered DRX on period extension via a MAC-CE or DCI message.

[0096] The activation or deactivation of the UE-triggered DRX on period extension mechanism may be based on one or more of the length of the DRX on period, the length of the DRX off period, the QoS specification of the service, the UE power constraint, the UE capability constraint or the overall network load.

[0097] Therefore, the QoS of the service can be improved. In addition, the beam quality between the UE and the network node can be improved. In addition, the communication delay can be reduced.

[0098] In order to accurately and quickly detect beam failure, in one or more configurations, the UE may perform BFD-related procedures in the DRX off period. The UE may perform the BFD procedure in the selected DRX off period when appropriate. In other words, the UE may not perform the BFD procedure in every DRX off period. In addition, even if the BFD procedure is performed during the DRX off period, the UE activity may be reduced or limited during the DRX off period in order to preserve the purpose and advantages of the DRX mode.

[0099] As UE technology advances, the UE can predict beam failures that may occur in the near future. For example, the UE can predict beam failures based on machine learning algorithms. In addition, the UE can predict beam failures with the assistance of cameras and / or other sensors that can help detect or predict beam blocking.

[0100] Figure 7 700 is a diagram illustrating an example process 700 for sending a beam failure warning report in association with a DRX mode. The UE may perform a BFD process based on a BFD-RS 710. In one or more configurations, when a beam failure is predicted to exist during an upcoming existing DRX off period 704 at 712 (i.e., before the end of the current DRX on period 702), the UE may send a beam failure warning report 714 to a network node (e.g., via a MAC-CE or UCI message). Then, after a timer-based delay, the UE may monitor a response 716 to the beam failure warning report 714 from the network node. In particular, after sending the beam failure warning report 714, the UE may start a timer 708 (e.g., a "drx-BFW-RTT-Timer" timer, where "BFW" may refer to beam failure warning and "RTT" may refer to round trip time). Upon or immediately after the expiration of timer 708, the UE may start a timer 706 (e.g., a "drx-BFWR-Timer" timer, where "BFWR" may refer to a beam failure warning response). During the duration of timer 706 (i.e., after the start of timer 706 and before the expiration of timer 706), the UE may monitor a response 716 to a beam failure warning report 714 from the network node. In particular, the response 716 from the network node (which may be sent via a MAC-CE or DCI message) may include an indication / command to switch downlink beams.

[0101] Therefore, because the UE may monitor the response 716 from the network node during the duration of the timer 706, the UE may not monitor the PDCCH for the response 716 from the network node during the entire DRX off period 704. Therefore, UE power consumption may be reduced, and the purpose and advantages of the DRX mode may be preserved. In one or more configurations, the beam failure warning report 714 may indicate that a beam failure is predicted to occur during an upcoming DRX off period 704. In addition, the beam failure warning report 714 may include at least one of a channel measurement report, one or more BFI counts, one or more BFI patterns, or a BFI history, and the like.

[0102] In one or more configurations, the network node may configure the UE (e.g., via RRC signaling) with one or more beam failure warning report configurations. For example, in one or more configurations, the network node may configure the UE (e.g., via RRC signaling) with one or more conditions that may trigger the UE to send a beam failure warning report 714. For example, the conditions may include one or more of a predicted beam failure in an upcoming DRX off period, a number of consecutive BFIs greater than a threshold (e.g., N), a total BFI count greater than a threshold (e.g., the threshold may be x% of a "maxCount" threshold), etc. In one or more configurations, the network node may configure the UE (e.g., via RRC signaling) with a format (content format) of the beam failure warning report 714. In one or more configurations, the network node may configure the UE (e.g., via RRC signaling) with the duration of the "drx-BFW-RTT-Timer" timer. In one or more configurations, the network node may configure the UE (e.g., via RRC signaling) with the duration of the "drx-BFWR-Timer" timer.

[0103] In one or more configurations, the network node may pre-configure the UE (eg, via RRC signaling) with multiple options for at least some of the above configuration parameters, and may use MAC-CE or DCI messages to switch between configuration options.

[0104] In one or more configurations, the UE or the network node may activate or deactivate the process / mechanism of UE beam failure warning reporting. In particular, the UE may send a request to the network node via a MAC-CE or UCI message for activating or deactivating the mechanism of UE beam failure warning reporting. In addition, the network node may activate or deactivate the mechanism of UE beam failure warning reporting via a MAC-CE or DCI message. In addition, the network node may send an indication of a configuration or a change in the configuration of a format (content format) of beam failure warning reporting to the UE via a MAC-CE or DCI message.

[0105] The activation or deactivation of the mechanism for UE beam failure warning reporting can be based on one or more of the UE autonomous capabilities, the QoS specifications of the service business, the UE DRX configuration (for example, the length of the DRX cycle, the length of the DRX on period, the length of the DRX off period, etc.), the UE power constraints or the UE capacity constraints, etc.

[0106] As described above, beam failure prediction can be an enhancement of the wireless communication system, which can also utilize machine learning / artificial intelligence techniques. Therefore, based on the mechanism of UE beam failure warning reporting, more accurate and faster BFD and / or BFR processes can be performed. The beam failure warning report can be used as an "advance warning" to the network node about potential beam failures. In addition, downlink beam switching initiated by the network node can be a faster beam recovery method compared to the RACH process. In addition, beam failure warning reporting and response monitoring during the DRX off period can enable rapid BFD and BFR processes. In addition, since beam switching can be associated with less power consumption compared to the RACH process, UE power consumption can be reduced. The UE can retain the purpose and advantages of the DRX mode and can transmit beam failure warning reports where appropriate (i.e., when it is not appropriate, the UE may not transmit beam failure warning reports). Additional advantages associated with beam failure warning reports may include one or more of improved QoS, enhanced beam connection consistency, reduced latency, or improved reliability.

[0107] Return to see Figure 5 In one or more configurations, if the UE performs a BFD procedure during the DRX On period 502, the short DRX On period 502 may not provide the UE with enough time to determine the beam quality. Furthermore, the long DRX Off period 504 may mean that the UE may wait for a considerable time before it can resume beam quality measurement after the last DRX On period 502. Therefore, beam quality degradation may occur as a result, especially when the QoS specification of the current service is strict.

[0108] Thus, in one or more configurations, the UE may, based on the configuration, wake up during the (long) DRX off period 504. During such supplemental wake-up periods, the UE may perform BFD and / or BFR procedures.

[0109] Fig. 8A and Figure 8B 800A and 800B illustrate example procedures for waking up during an existing DRX off period. The UE may perform a BFD procedure based on a BFD-RS 806. The UE may wake up during an existing DRX off period 804 if a (trigger) condition is met. In one or more configurations, the network node may pre-configure resources and / or parameters for signaling 810 associated with a supplemental wake-up of the UE. In one or more configurations, the condition may be met if the duration of the existing DRX off period 804 is greater than a pre-specified multiple (e.g., x times) of the duration of a DRX on period (e.g., DRX on period 802 / 802' or another suitable reference DRX on period).

[0110] In one or more configurations, the network node may configure the UE (e.g., via RRC signaling) with conditions that may trigger the UE to perform a supplemental wake-up. In one or more configurations, the network node may configure the UE (e.g., via RRC signaling) with a wake-up timing and / or a wake-up period / duration associated with a supplemental wake-up during a DRX off period (e.g., a wake-up timing and / or a wake-up period / duration of a supplemental DRX on period 802a). In one or more configurations, the network node may configure the UE (e.g., via RRC signaling) with resources that the UE may use for signaling 810 associated with a supplemental wake-up during a DRX off period. In one or more configurations, the network node may configure the UE (e.g., via RRC signaling) with resources that the UE may use to monitor a response from the network node after the UE sends signaling 810 associated with a supplemental wake-up.

[0111] exist Fig. 8A In the embodiment, the supplementary DRX on period 802a may be in the middle of the existing DRX off period 804 (ie, there may be a gap between the supplementary DRX on period 802a and the subsequent DRX on period 802'). Figure 8B In the embodiment, the supplementary DRX On period 802a may represent or correspond to an early start of the subsequent DRX On period 802' (ie, there may be no gap between the supplementary DRX On period 802a and the subsequent DRX On period 802').

[0112] In one or more configurations, the network node may pre-configure the UE (eg, via RRC signaling) with multiple options for at least some of the above configuration parameters, and may use MAC-CE or DCI messages to switch between configuration options.

[0113] In one or more configurations, the UE may send signaling 810 associated with the supplemental wake-up to the network node. The signaling 810 associated with the supplemental wake-up may indicate that the UE is active during a supplemental DRX on period 802a, wherein the supplemental DRX on period 802a may be within an existing DRX off period 804. In one or more configurations, the signaling 810 may indicate the supplemental wake-up based on one or more pre-configured parameters. In one or more configurations, the signaling 810 may indicate that the supplemental wake-up may represent or correspond to an early start of a subsequent DRX on period 802' (e.g., such as Figure 8B shown).

[0114] In one or more configurations, the UE or the network node may activate or deactivate the procedure / mechanism of supplementary wake-up during the existing DRX off period. In particular, the UE may send a request to the network node via a MAC-CE or UCI message to activate or deactivate the supplementary wake-up mechanism during the existing DRX off period. In addition, the network node may activate or deactivate the mechanism of supplementary wake-up during the existing DRX off period via a MAC-CE or DCI message.

[0115] The activation or deactivation of the supplementary wake-up mechanism during the existing DRX off period can be based on one or more of the length of the DRX on period, the length of the DRX off period, the QoS specification of the service traffic, the UE power constraint, the UE capability constraint or the overall network load.

[0116] Thus, based on the supplementary wake-up during the existing DRX off period, the UE may wake up during the (long) DRX off period to measure the beam quality in a timely manner. Thus, the latency of the UE or network node's response to potential beam problems may be reduced. Additional advantages associated with the supplementary wake-up during the existing DRX off period may include one or more of improved beam quality, reduced or avoided BFI, or improved QoS of service traffic.

[0117] Fig. 9 is a diagram of a communication flow 900 of a method of wireless communication. At 906, the network node 904 may send one or more DRX configuration sets to the UE 902 via RRC signaling, and the UE 902 may receive the one or more DRX configuration sets from the network node 904.

[0118] In one configuration, at least one of the one or more DRX configuration sets may include at least one of a DRX on period extension configuration, a beam failure warning configuration, or a supplemental DRX wake-up configuration.

[0119] At 908 , the network node 904 may send an indication of one of the one or more DRX configuration sets to the UE 902 via the second MAC-CE or the first DCI message, and the UE 902 may receive the indication from the network node 94 .

[0120] At 910 , via a third MAC-CE or a second UCI message, the UE 902 may send a request to the network node 904 to activate or deactivate one or more DRX-related mechanisms, and the network node 904 may receive the request from the UE 902 .

[0121] In one configuration, the one or more DRX-related mechanisms may include one or more of a DRX on-period extension mechanism, a beam failure warning mechanism, or a supplemental DRX wake-up mechanism.

[0122] At 912 , the network node 904 may send an indication of activation or deactivation of one or more DRX-related mechanisms to the UE 902 via a fourth MAC-CE or a second DCI message, and the UE 902 may receive the indication from the network node 904 .

[0123] At 914, the UE 902 may identify that a first condition is satisfied during a first DRX-on period immediately preceding an existing DRX-off period.

[0124] In one or more configurations, the first condition is met if a first number of BFI indicators is greater than a first threshold, a second number of consecutive BFI indicators is greater than a second threshold, the channel strength decreases by more than a third threshold, the UE has more data to send to the network node during the first DRX on period than would be possible without extending the first DRX on period, the network node has more data to send to the UE during the first DRX on period than would be possible without extending the first DRX on period, or the UE predicts a beam failure during an existing DRX off period.

[0125] At 916 , the UE 902 may send a request to the network node 904 to extend the first DRX On period based on satisfying the first condition, and the network node 904 may receive the request from the UE 902 .

[0126] In one configuration, the request 916 to extend the first DRX On period may be sent and received via a first MAC-CE or a first UCI message.

[0127] At 918 , the network node 904 may send an indication of approval of the request to extend the first DRX On period to the UE 902 , and the UE 902 may receive the indication from the network node 904 .

[0128] In one configuration, the approval of the request to extend the first DRX On period may include an indication of the first time period.In one configuration, the indication of the approval of the request to extend the first DRX On period may be sent and received via a PDCCH.

[0129] At 920, the UE 902 and the network node 904 may delay a start of an existing DRX Off period for the UE 902 by a first time period based on approval of the request to extend the first DRX On period.

[0130] At 922, the UE 902 may predict beam failure during an existing DRX off period during a first DRX on period.

[0131] At 924 , the UE 902 may send a beam failure warning report based on the prediction of the beam failure to the network node 904 , and the network node 904 may receive the beam failure warning report from the UE 902 .

[0132] In one configuration, the beam failure warning report may include at least one of a channel measurement report, a BFI count, a BFI pattern, or a BFI history.

[0133] At 926, the UE 902 may monitor for a response to the beam failure warning report from the network node 904 for a predetermined second time period during the existing DRX off period after expiration of the first timer. The first timer may be started at the beginning of the existing DRX off period.

[0134] At 928 , the network node 904 may send a response to the beam failure warning report 924 to the UE 902 during a predetermined second time period during the existing DRX off period after expiration of the first timer, and the UE 902 may receive the response from the network node 904 .

[0135] In one configuration, the response 928 to the beam failure warning report 924 may be sent and received via a fourth MAC-CE or a third DCI message. In one configuration, the response 928 to the beam failure warning report 924 may include an indication of beam switching.

[0136] At 930, the UE 902 may identify that the existing DRX OFF period is greater than a predetermined multiple of the second DRX ON period.

[0137] At 932, the UE 902 may wake up for a second time period during the existing DRX OFF period in response to identifying that the existing DRX OFF period is greater than a predetermined multiple of the second DRX ON period.

[0138] At 934, via a fifth MAC-CE or a third UCI message, the UE 902 may send an indication of waking up to the network node 904, and the network node 904 may receive the indication from the UE 902. The waking up of the UE may be based on the existing DRX off period being greater than a predetermined multiple of the second DRX on period. The indication of waking up may include an indication that the waking up is based on one or more preconfigured parameters, or an indication that the waking up corresponds to an early start of a third DRX on period immediately following the existing DRX off period.

[0139] At 936 , UE 902 may monitor for a response to the indication of wakeup from network node 904 .

[0140] At 938 , the network node 904 may send a response to the indication 934 of waking up to the UE 902 , and the UE 902 may receive the response from the network node 904 .

[0141] Fig.10 1000 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 / 350 / 902; device 1404). At 1002, the UE may identify that a first condition is satisfied during a first DRX on period immediately preceding an existing DRX off period. For example, 1002 may be performed by Fig.14 Component 198 in is used for execution. Fig. 9 At 914, the UE 902 may identify that the first condition is satisfied during a first DRX-on period immediately preceding an existing DRX-off period.

[0142] At 1004, the UE may send a request to the network node to extend the first DRX on period based on satisfying the first condition. For example, 1004 may be performed by Fig.14 Component 198 in is used for execution. Fig. 9 At 916, the UE 902 may send a request to the network node 904 to extend the first DRX on period based on satisfying the first condition.

[0143] At 1006, the UE may receive an indication of approval of the request to extend the first DRX on period from the network node. For example, 1006 may be Fig.14 Component 198 in is used for execution. Fig. 9 At 918, the UE 902 may receive an indication from the network node 904 of approval of the request to extend the first DRX on period.

[0144] At 1008, the UE may delay the start of the existing DRX off period for a first time period based on the approval of the request to extend the first DRX on period. For example, 1008 may be performed by Fig.14 Component 198 in is used for execution. Fig. 9 At 920, the UE 902 may delay the start of the existing DRX off period by a first time period based on the approval of the request to extend the first DRX on period.

[0145] Fig.111100 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 / 350 / 902; device 1404). At 1110, the UE may identify that a first condition is satisfied during a first DRX on period immediately preceding an existing DRX off period. For example, 1110 may be performed by Fig.14 198 in the implementation. Fig. 9 At 914, the UE 902 may identify that the first condition is satisfied during a first DRX-on period immediately preceding an existing DRX-off period.

[0146] At 1112, the UE may send a request to the network node to extend the first DRX on period based on satisfying the first condition. Fig.14 198 in the implementation. Fig. 9 At 916, the UE 902 may send a request to the network node 904 to extend the first DRX on period based on satisfying the first condition.

[0147] At 1114, the UE may receive an indication of approval of the request to extend the first DRX on period from the network node. For example, 1114 may be indicated by Fig.14 198 in the implementation. Fig. 9 At 918, the UE 902 may receive an indication from the network node 904 of approval of the request to extend the first DRX on period.

[0148] At 1116, the UE may delay the start of the existing DRX off period for a first time period based on the approval of the request to extend the first DRX on period. For example, 1116 may be performed by Fig.14 198 in the implementation. Fig. 9 At 920, the UE 902 may delay the start of the existing DRX off period by a first time period based on the approval of the request to extend the first DRX on period.

[0149] In one configuration, see Fig. 9 , a request 916 for extending the first DRX on period may be sent to the network node 904 via a first MAC-CE or a first UCI message.

[0150] In one configuration, the approval of the request to extend the first DRX On period may include an indication of the first time period.

[0151] In one configuration, see Fig. 9 , an indication 918 of approval of the request to extend the first DRX On period may be received from the network node 904 via the PDCCH.

[0152] In one configuration, see Fig. 9 The first condition may be met if a first number of BFI indicators is greater than a first threshold, a second number of consecutive BFI indicators is greater than a second threshold, the channel strength decreases by more than a third threshold, the UE 902 has more data to send to the network node 904 during the first DRX on period than would be possible without extending the first DRX on period, the network node 904 has more data to send to the UE 902 during the first DRX on period than would be possible without extending the first DRX on period, or the UE 902 predicts a beam failure during an existing DRX off period.

[0153] In one configuration, at 1102, the UE may receive one or more DRX configuration sets from a network node via RRC signaling. For example, 1102 may be Fig.14 198 in the implementation. Fig. 9 At 906, UE 902 may receive one or more DRX configuration sets from network node 904 via RRC signaling.

[0154] At 1104, the UE may receive an indication of one of the one or more DRX configuration sets from the network node via a second MAC-CE or a first DCI message. For example, 1104 may be Fig.14 198 in the implementation. Fig. 9 At 908, the UE 902 may receive an indication of one of the one or more DRX configuration sets from the network node 904 via a second MAC-CE or a first DCI message.

[0155] In one configuration, at least one of the one or more DRX configuration sets may include at least one of a DRX on period extension configuration, a beam failure warning configuration, or a supplemental DRX wake-up configuration.

[0156] In one configuration, at 1106, the UE may send a request to activate or deactivate one or more DRX-related mechanisms to the network node via a third MAC-CE or a second UCI message. For example, 1106 may be sent by Fig.14 198 in the implementation. Fig. 9 At 910, the UE 902 may send a request to activate or deactivate one or more DRX-related mechanisms to the network node 904 via a third MAC-CE or a second UCI message.

[0157] At 1108, the UE may receive an indication of activating or deactivating one or more DRX-related mechanisms from the network node via a fourth MAC-CE or a second DCI message. For example, 1108 may be Fig.14 198 in the implementation. Fig. 9 At 912, the UE 902 may receive an indication of activation or deactivation of one or more DRX-related mechanisms from the network node 904 via a fourth MAC-CE or a second DCI message.

[0158] In one configuration, the one or more DRX-related mechanisms may include one or more of a DRX on-period extension mechanism, a beam failure warning mechanism, or a supplemental DRX wake-up mechanism.

[0159] In one configuration, at 1118, the UE may predict beam failure during an existing DRX off period during a first DRX on period. For example, 1118 may be performed by Fig.14 198 in the implementation. Fig. 9 , at 922, UE 902 may predict beam failure during an existing DRX off period during a first DRX on period.

[0160] At 1120, the UE may send a beam failure warning report based on the prediction of beam failure to the network node. For example, 1120 may be performed by Fig.14 198 in the implementation. Fig. 9 At 924, UE 902 may send a beam failure warning report based on a prediction of beam failure to network node 904.

[0161] At 1122, the UE may monitor a response to a beam failure warning report from the network node within a predetermined second time period during the existing DRX off period after the first timer expires. The first timer may be started at the beginning of the existing DRX off period. For example, 1122 may be Fig.14 198 in the implementation. Fig. 9 , at 926, the UE 902 may monitor a response to the beam failure warning report from the network node 904 within a predetermined second time period during an existing DRX off period after expiration of the first timer.

[0162] At 1124, the UE may receive a response to the beam failure warning report from the network node during a predetermined second time period. For example, 1124 may be Fig.14 198 in the implementation. Fig. 9 At 928, the UE 902 may receive a response to the beam failure warning report 924 from the network node 904 during a predetermined second time period.

[0163] In one configuration, see Fig. 9 , a response 928 to the beam failure warning report 924 may be received from the network node 904 via a fourth MAC-CE or a third DCI message.

[0164] In one configuration, see Fig. 9 , the response 928 to the beam failure warning report 924 may include an indication of beam switching.

[0165] In one configuration, see Fig. 9 The beam failure warning report 924 may include at least one of a channel measurement report, a BFI count, a BFI pattern, or a BFI history.

[0166] In one configuration, at 1126, the UE may identify that the existing DRX off period is greater than a predetermined multiple of the second DRX on period. For example, 1126 may be Fig.14 198 in the implementation. Fig. 9 At 930, UE 902 may identify that the existing DRX-off period is greater than a predetermined multiple of the second DRX-on period.

[0167] At 1128, the UE may wake up for a second time period during the existing DRX OFF period in response to identifying that the existing DRX OFF period is greater than a predetermined multiple of the second DRX ON period. Fig.14 198 in the implementation. Fig. 9 At 932, the UE 902 may wake up for a second time period during the existing DRX OFF period in response to identifying that the existing DRX OFF period is greater than a predetermined multiple of the second DRX ON period.

[0168] At 1130, the UE may send an indication of waking up to the network node via a fifth MAC-CE or a third UCI message. The indication of waking up may include an indication that the waking up is based on one or more pre-configured parameters, or an indication that the waking up corresponds to an early start of a third DRX on period immediately following the existing DRX off period. For example, 1130 may be sent by Fig.14 198 in the implementation. Fig. 9 At 934, the UE 902 may send an indication of waking up to the network node 904 via a fifth MAC-CE or a third UCI message.

[0169] At 1132, the UE may monitor for a response to an indication of a wake-up from the network node. For example, 1132 may be performed by Fig.14 198 in the implementation. Fig. 9At 936 , UE 902 may monitor for a response to the indication of wake-up from network node 904 .

[0170] Fig.12 1200 is a flow chart of a method of wireless communication. The method may be performed by a base station / network node (e.g., base station / network node 102 / 310 / 904; network entity 1502). At 1202, the network node may receive from a UE a request to extend a first DRX on period immediately preceding an existing DRX off period based on satisfying a first condition. For example, 1202 may be performed by Fig.15 Component 199 in the implementation. Fig. 9 At 916, the network node 904 may receive from the UE 902 a request to extend a first DRX on period immediately preceding an existing DRX off period based on satisfying a first condition.

[0171] At 1204, the network node may send an indication to the UE of approval of the request to extend the first DRX on period. For example, 1204 may be sent by Fig.15 Component 199 in the implementation. Fig. 9 At 918, the network node 904 may send an indication to the UE 902 of approval of the request to extend the first DRX on period.

[0172] At 1206, the network node may delay the start of the existing DRX off period for a first time period based on the approval of the request to extend the first DRX on period. For example, 1206 may be performed by Fig.15 Component 199 in the implementation. Fig. 9 At 920, the network node 904 may delay the start of the existing DRX off period by a first time period based on the approval of the request to extend the first DRX on period.

[0173] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a base station / network node (e.g., base station / network node 102 / 310 / 904; network entity 1502). At 1310, the network node may receive from a UE a request to extend a first DRX on period immediately preceding an existing DRX off period based on satisfying a first condition. For example, 1310 may be performed by Fig.15 Component 199 in the implementation. Fig. 9 At 916, the network node 904 may receive from the UE 902 a request to extend a first DRX on period immediately preceding an existing DRX off period based on satisfying a first condition.

[0174] At 1312, the network node may send an indication to the UE of approval of the request to extend the first DRX on period. For example, 1312 may be sent by Fig.15 Component 199 in the implementation. Fig. 9 At 918, the network node 904 may send an indication to the UE 902 of approval of the request to extend the first DRX on period.

[0175] At 1314, the network node may delay the start of the existing DRX off period for a first time period based on the approval of the request to extend the first DRX on period. Fig.15 Component 199 in the implementation. Fig. 9 At 920, the network node 904 may delay the start of the existing DRX off period by a first time period based on the approval of the request to extend the first DRX on period.

[0176] In one configuration, see Fig. 9 , a request 916 to extend the first DRX on period may be received from the UE 902 via a first MAC-CE or a first UCI message.

[0177] In one configuration, the approval of the request to extend the first DRX On period may include an indication of the first time period.

[0178] In one configuration, see Fig. 9 , an indication 918 of approval of the request to extend the first DRX on period may be sent to the UE 902 via the PDCCH.

[0179] In one configuration, see Fig. 9 The first condition may be met if: a first number of BFI indicators is greater than a first threshold, a second number of consecutive BFI indicators is greater than a second threshold, the channel strength decreases by more than a third threshold, the UE 902 has more data to send to the network node 904 during the first DRX on period than would be possible without extending the first DRX on period, the network node 904 has more data to send to the UE 902 during the first DRX on period than would be possible without extending the first DRX on period, or the UE 902 predicts a beam failure during an existing DRX off period.

[0180] In one configuration, at 1302, the network node may send one or more DRX configuration sets to the UE via RRC signaling. For example, 1302 may be performed by Fig.15 Component 199 in the implementation. Fig. 9 At 906, the network node 904 may send one or more DRX configuration sets to the UE 902 via RRC signaling.

[0181] At 1304, the network node may send an indication of one of the one or more DRX configuration sets to the UE via a second MAC-CE or a first DCI message. For example, 1304 may be Fig.15 Component 199 in the implementation. Fig. 9 At 908, the network node 904 may send an indication of one of the one or more DRX configuration sets to the UE 902 via a second MAC-CE or a first DCI message.

[0182] In one configuration, see Fig. 9 At least one of the one or more DRX configuration sets 906 may include at least one of a DRX on-period extension configuration, a beam failure warning configuration, or a supplemental DRX wake-up configuration.

[0183] In one configuration, at 1306, the network node may receive a request to activate or deactivate one or more DRX-related mechanisms from the UE via a third MAC-CE or a second UCI message. For example, 1306 may be performed by Fig.15 Component 199 in the implementation. Fig. 9 At 910, the network node 904 may receive a request to activate or deactivate one or more DRX-related mechanisms from the UE 902 via a third MAC-CE or a second UCI message.

[0184] At 1308, the network node may send an indication of activating or deactivating one or more DRX-related mechanisms to the UE via a fourth MAC-CE or a second DCI message. For example, 1308 may be performed by Fig.15 Component 199 in the implementation. Fig. 9 At 912, the network node 904 may send an indication of activating or deactivating one or more DRX-related mechanisms to the UE 902 via a fourth MAC-CE or a second DCI message.

[0185] In one configuration, the one or more DRX-related mechanisms may include one or more of a DRX on-period extension mechanism, a beam failure warning mechanism, or a supplemental DRX wake-up mechanism.

[0186] In one configuration, at 1316, the network node may receive a beam failure warning report based on a predicted beam failure from the UE. For example, 1316 may be performed by Fig.15 Component 199 in the implementation. Fig. 9 At 924, the network node 904 may receive a beam failure warning report from the UE 902 based on the predicted beam failure.

[0187] At 1318, the network node may send a response to the beam failure warning report to the UE during a predetermined second time period during the existing DRX off period after the first timer expires. The first timer may be started at the beginning of the existing DRX off period. For example, 1318 may be initiated by Fig.15 Component 199 in the implementation. Fig. 9 , at 928, the network node 904 may send a response to the beam failure warning report 924 to the UE 902 during a predetermined second time period during the existing DRX off period after expiration of the first timer.

[0188] In one configuration, see Fig. 9 , a response 928 to the beam failure warning report 924 may be sent to the UE 902 via a fourth MAC-CE or a third DCI message.

[0189] In one configuration, see Fig. 9 , the response 928 to the beam failure warning report 924 may include an indication of beam switching.

[0190] In one configuration, see Fig. 9 The beam failure warning report 924 may include at least one of a channel measurement report, a BFI count, a BFI pattern, or a BFI history.

[0191] In one configuration, at 1320, the network node may receive, via a fifth MAC-CE or a third UCI message, from the UE an indication to wake up the UE for a second time period during an existing DRX off period. The waking up of the UE may be based on the existing DRX off period being greater than a predetermined multiple of the second DRX on period. The indication of the waking up may include an indication that the waking up is based on one or more preconfigured parameters, or an indication that the waking up corresponds to an early start of a third DRX on period immediately following the existing DRX off period. For example, 1320 may be received by Fig.15 Component 199 in the implementation. Fig. 9 At 934, the network node 904 may receive an indication from the UE 902 via a fifth MAC-CE or a third UCI message to wake up the UE 902 for a second time period during the existing DRX off period.

[0192] At 1322, the network node may send a response to the indication of the wake-up to the UE. For example, 1322 may be Fig.15 Component 199 in the implementation. Fig. 9 At 938, the network node 904 may send a response to the indication 934 of waking up to the UE 902.

[0193] Fig.141400 is a diagram illustrating an example of a hardware implementation for an apparatus 1404. The apparatus 1404 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1404 may include a cellular baseband processor 1424 (also referred to as a modem) coupled to one or more transceivers 1422 (e.g., a cellular RF transceiver). The cellular baseband processor 1424 may include on-chip memory 1424'. In some aspects, the apparatus 1404 may also include one or more subscriber identity module (SIM) cards 1420 and an application processor 1406 coupled to a secure digital (SD) card 1408 and a screen 1410. The application processor 1406 may include on-chip memory 1406'. In some aspects, the device 1404 may also include a Bluetooth module 1412, a WLAN module 1414, a satellite system module 1416 (e.g., a GNSS module), one or more sensor modules 1418 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1426, a power source 1430, and / or a camera 1432. The Bluetooth module 1412, the WLAN module 1414, and the satellite system module 1416 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 1424 communicates with the UE 104 and / or with a RU associated with the network entity 1402 through the transceiver 1422 via one or more antennas 1480. The cellular baseband processor 1424 and the application processor 1406 may each include a computer-readable medium / memory 1424', 1406', respectively. The additional memory module 1426 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1424', 1406', 1426 may be non-transitory. The cellular baseband processor 1424 and the application processor 1406 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1424 / application processor 1406, enables the cellular baseband processor 1424 / application processor 1406 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1424 / application processor 1406 when executing the software. The cellular baseband processor 1424 / application processor 1406 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 device 1404 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1424 and / or the application processor 1406, while in another configuration, the device 1404 may be an entire UE (eg, see. Figure 3 350) and includes additional modules of device 1404.

[0194] As discussed above, component 198 is configured to identify that a first condition is satisfied during a first DRX on period immediately preceding an existing DRX off period. Component 198 may be configured to send a request to a network node to extend the first DRX on period based on satisfying the first condition. Component 198 may be configured to receive an indication of approval of the request to extend the first DRX on period from the network node. Component 198 may be configured to delay the start of the existing DRX off period for a first time period based on approval of the request to extend the first DRX on period. Component 198 may be in the cellular baseband processor 1424, the application processor 1406, or in both the cellular baseband processor 1424 and the application processor 1406. Component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1404 may include a variety of components configured for various functions. In one configuration, the apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for identifying that a first condition is satisfied during a first DRX On period immediately preceding an existing DRX Off period. The apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for sending a request to a network node to extend the first DRX On period based on satisfying the first condition. The apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for receiving an indication of approval of the request to extend the first DRX On period from the network node. The apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for delaying the start of the existing DRX Off period by a first time period based on the approval of the request to extend the first DRX On period.

[0195] In one configuration, a request to extend the first DRX on period may be sent to the network node via a first MAC-CE or a first UCI message. In one configuration, the approval of the request to extend the first DRX on period may include an indication of the first time period. In one configuration, an indication of the approval of the request to extend the first DRX on period may be received from the network node via a PDCCH. In one configuration, the first condition may be met if a first number of BFI indicators is greater than a first threshold, a second number of consecutive BFI indicators is greater than a second threshold, a channel strength decreases by more than a third threshold, the UE has more data to send to the network node during the first DRX on period than is possible without extending the first DRX on period, the network node has more data to send to the UE during the first DRX on period than is possible without extending the first DRX on period, or the UE predicts a beam failure during an existing DRX off period. In one configuration, the device 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes a component for receiving one or more DRX configuration sets from the network node via RRC signaling. The apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for receiving an indication of one of the one or more DRX configuration sets from a network node via a second MAC-CE or a first DCI message. In one configuration, at least one of the one or more DRX configuration sets may include at least one of a DRX on period extension configuration, a beam failure warning configuration, or a supplemental DRX wake-up configuration. In one configuration, the apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for sending a request to activate or deactivate one or more DRX-related mechanisms to the network node via a third MAC-CE or a second UCI message. The apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for receiving an indication of activating or deactivating one or more DRX-related mechanisms from a network node via a fourth MAC-CE or a second DCI message. In one configuration, the one or more DRX-related mechanisms may include one or more of a DRX on period extension mechanism, a beam failure warning mechanism, or a supplemental DRX wake-up mechanism. In one configuration, the apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for predicting, during a first DRX on period, a beam failure during an existing DRX off period. The apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for sending a beam failure warning report based on the prediction of a beam failure to a network node.The device 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes a component for monitoring a response to a beam failure warning report from a network node during a predetermined second time period during an existing DRX off period after expiration of a first timer. The first timer may be started at the beginning of the existing DRX off period. The device 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes a component for receiving a response to the beam failure warning report from the network node during the predetermined second time period. In one configuration, the response to the beam failure warning report may be received from the network node via a fourth MAC-CE or a third DCI message. In one configuration, the response to the beam failure warning report may include an indication of beam switching. In one configuration, the beam failure warning report may include at least one of a channel measurement report, a BFI count, a BFI mode, or a BFI history. In one configuration, the apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for identifying that an existing DRX off period is greater than a predetermined multiple of a second DRX on period. The apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for waking up for a second time period during the existing DRX off period in response to identifying that the existing DRX off period is greater than a predetermined multiple of the second DRX on period. The apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for sending an indication of waking up to the network node via a fifth MAC-CE or a third UCI message. The indication of waking up may include an indication that the waking up is based on one or more preconfigured parameters, or an indication that the waking up corresponds to an early start of a third DRX on period immediately following the existing DRX off period. The apparatus 1404 (and in particular the cellular baseband processor 1424 and / or the application processor 1406) includes means for monitoring a response to an indication of wake-up from a network node.

[0196] The means may be a component 198 of the apparatus 1404 configured to perform the functions recited by the means. As described above, the apparatus 1404 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0197] Fig.151500 is a diagram illustrating an example of a hardware implementation for a network entity 1502. The network entity 1502 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1502 may include at least one of a CU 1510, a DU 1530, or a RU 1540. For example, depending on the layer functionality processed by the component 199, the network entity 1502 may include a CU 1510; both a CU 1510 and a DU 1530; each of the CU 1510, the DU 1530, and the RU 1540; the DU 1530; both a DU 1530 and a RU 1540; or the RU 1540. The CU 1510 may include a CU processor 1512. The CU processor 1512 may include an on-chip memory 1512'. In some aspects, the CU 1510 may also include an additional memory module 1514. The CU 1510 communicates with the DU 1530. DU 1530 may include DU processor 1532. DU processor 1532 may include on-chip memory 1532'. In some aspects, DU 1530 may also include additional memory module 1534. DU 1530 communicates with RU 1540. RU 1540 may include RU processor 1542. RU processor 1542 may include on-chip memory 1542'. In some aspects, RU 1540 may also include additional memory module 1544, one or more transceivers 1546 and antenna 1580. RU 1540 communicates with UE 104. On-chip memory 1512', 1532', 1542' and additional memory modules 1514, 1534, 1544 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of processors 1512, 1532, 1542 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0198] As discussed above, component 199 is configured to receive from a UE a request to extend a first DRX on period immediately preceding an existing DRX off period based on satisfying a first condition. Component 199 may be configured to send to the UE an indication of approval of the request to extend the first DRX on period. Component 199 may be configured to delay the start of the existing DRX off period for a first time period based on approval of the request to extend the first DRX on period. Component 199 may be within one or more processors of one or more of CU 1510, DU 1530, and RU 1540. Component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1502 may include a variety of components configured for various functions. In one configuration, the network entity 1502 includes means for receiving, from a UE, a request to extend a first DRX On period immediately preceding an existing DRX Off period based on satisfying a first condition. The network entity 1502 includes means for sending, to the UE, an indication of approval of the request to extend the first DRX On period. The network entity 1502 includes means for delaying a start of the existing DRX Off period by a first time period based on approval of the request to extend the first DRX On period.

[0199] In one configuration, a request to extend a first DRX on period may be received from a UE via a first MAC-CE or a first UCI message. In one configuration, approval of the request to extend the first DRX on period may include an indication of a first time period. In one configuration, an indication of approval of the request to extend the first DRX on period may be sent to the UE via a PDCCH. In one configuration, the first condition may be met if: a first number of BFI indicators is greater than a first threshold, a second number of consecutive BFI indicators is greater than a second threshold, a channel strength decreases by more than a third threshold, the UE has more data to send to a network node during the first DRX on period than would be possible without extending the first DRX on period, the network node has more data to send to the UE during the first DRX on period than would be possible without extending the first DRX on period, or the UE predicts a beam failure during an existing DRX off period. In one configuration, the network entity 1502 includes a component for sending one or more DRX configuration sets to the UE via RRC signaling. The network entity 1502 includes a component for sending an indication of one of the one or more DRX configuration sets to the UE via a second MAC-CE or a first DCI message. In one configuration, at least one of the one or more DRX configuration sets may include at least one of a DRX on period extension configuration, a beam failure warning configuration, or a supplementary DRX wake-up configuration. In one configuration, the network entity 1502 includes a component for receiving a request to activate or deactivate one or more DRX-related mechanisms from the UE via a third MAC-CE or a second UCI message. The network entity 1502 includes a component for sending an indication of activating or deactivating one or more DRX-related mechanisms to the UE via a fourth MAC-CE or a second DCI message. In one configuration, the one or more DRX-related mechanisms may include one or more of a DRX on period extension mechanism, a beam failure warning mechanism, or a supplementary DRX wake-up mechanism. In one configuration, the network entity 1502 includes a component for receiving a beam failure warning report based on a predicted beam failure from the UE. The network entity 1502 includes a component for sending a response to a beam failure warning report to the UE during a predetermined second time period during an existing DRX off period after expiration of a first timer. The first timer may be started at the beginning of the existing DRX off period. In one configuration, the response to the beam failure warning report may be sent to the UE via a fourth MAC-CE or a third DCI message. In one configuration, the response to the beam failure warning report may include an indication of beam switching. In one configuration, the beam failure warning report may include at least one of a channel measurement report, a BFI count, a BFI pattern, or a BFI history.In one configuration, the network entity 1502 includes means for receiving, from the UE via a fifth MAC-CE or a third UCI message, an indication to wake up the UE for a second time period during an existing DRX off period. The waking up of the UE may be based on the existing DRX off period being greater than a predetermined multiple of the second DRX on period. The indication of waking up may include an indication that the waking up is based on one or more preconfigured parameters, or an indication that the waking up corresponds to an early start of a third DRX on period immediately following the existing DRX off period. The network entity 1502 includes means for sending a response to the indication of waking up to the UE.

[0200] The means may be a component 199 of the network entity 1502 configured to perform the functions recited by the means. As described above, the network entity 1502 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.

[0201] Return to see Figures 4 to 15 , the UE may identify that the first condition is satisfied during a first DRX on period immediately preceding an existing DRX off period. The UE may send a request to a network node to extend the first DRX on period based on satisfying the first condition, and the network node may receive the request from the UE. The network node may send an indication of approval of the request to extend the first DRX on period to the UE, and the UE may receive the indication from the network node. The UE and the network node may delay the start of the existing DRX off period for a first time period based on approval of the request to extend the first DRX on period. Therefore, the accuracy associated with the BFD / BFR process may be improved. In addition, during a portion of the initially scheduled DRX off period (DRX on extension period), there may be more time for the UE to perform BFD-RS monitoring in order to confirm beam failure.

[0202] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. Further, some blocks can be combined or omitted. The attached method claims provide the elements of various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0203] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise expressly stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or data can be indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents that are known or will be known later to those of ordinary skill in the art throughout the elements of the various aspects described in this disclosure are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recorded in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a functional component unless the element is explicitly recorded using the phrase "component for...".

[0204] As used in this disclosure outside the claims, the phrase "based on" includes all interpretations and should not be limited to any single interpretation unless specifically recorded or indicated as such. For example, the phrase "based on A" (where "A" may be information, conditions, factors, etc.) may be interpreted as: "at least based on A", "partially based on A", "at least partially based on A", "only based on A" or "based on A alone". Therefore, as disclosed herein, in one aspect, "based on A" may mean "at least based on A". In another aspect, "based on A" may mean "partially based on A". In another aspect, "based on A" may mean "at least partially based on A". In another aspect, "based on A" may mean "only based on A". In another aspect, "based on A" may mean "based on A alone". In another aspect, "based on A" may mean any combination of alternative interpretations. As used in the claims, the phrase "based on A" should be interpreted as "at least based on A", unless otherwise specifically stated.

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

[0206] Aspect 1 is a method for performing wireless communications at a UE, comprising: identifying that a first condition is satisfied during a first DRX on period immediately preceding an existing DRX off period; sending a request to a network node to extend the first DRX on period based on satisfying the first condition; receiving an indication of approval of the request to extend the first DRX on period from the network node; and based on the approval of the request to extend the first DRX on period, delaying the start of the existing DRX off period by a first time period.

[0207] Aspect 2 is a method according to aspect 1, wherein the request for extending the first DRX on period is sent to the network node via a first MAC-CE or a first UCI message.

[0208] Aspect 3 is a method according to any one of aspects 1 and 2, wherein the approval of the request to extend the first DRX on period includes an indication of the first time period.

[0209] Aspect 4 is a method according to any one of aspects 1 to 3, wherein the indication of the approval of the request to extend the first DRX on period is received from the network node via a PDCCH.

[0210] Aspect 5 is a method according to any one of Aspects 1 to 4, wherein the first condition is met if a first number of BFI indicators is greater than a first threshold, a second number of consecutive BFI indicators is greater than a second threshold, the channel strength decreases by more than a third threshold, the UE has more data to send to the network node during the first DRX on period than is possible without extending the first DRX on period, the network node has more data to send to the UE during the first DRX on period than is possible without extending the first DRX on period, or the UE predicts a beam failure during the existing DRX off period.

[0211] Aspect 6 is a method according to any one of Aspects 1 to 5, further comprising: receiving one or more DRX configuration sets from the network node via RRC signaling; and receiving an indication of one of the one or more DRX configuration sets from the network node via a second MAC-CE or a first DCI message.

[0212] Aspect 7 is a method according to aspect 6, wherein at least one of the one or more DRX configuration sets includes at least one of a DRX on period extension configuration, a beam failure warning configuration, or a supplementary DRX wake-up configuration.

[0213] Aspect 8 is a method according to any one of Aspects 1 to 7, further comprising: sending a request to activate or deactivate one or more DRX-related mechanisms to the network node via a third MAC-CE or a second UCI message; and receiving an indication to activate or deactivate the one or more DRX-related mechanisms from the network node via a fourth MAC-CE or a second DCI message.

[0214] Aspect 9 is a method according to aspect 8, wherein the one or more DRX-related mechanisms include one or more of a DRX on-period extension mechanism, a beam failure warning mechanism, or a supplementary DRX wake-up mechanism.

[0215] Aspect 10 is a method according to any one of Aspects 1 to 9, further comprising: predicting a beam failure during the existing DRX off period during the first DRX on period; sending a beam failure warning report based on the prediction of the beam failure to the network node; monitoring a response to the beam failure warning report from the network node within a predetermined second time period during the existing DRX off period after expiration of a first timer, the first timer starting at the beginning of the existing DRX off period; and receiving the response to the beam failure warning report from the network node during the predetermined second time period.

[0216] Aspect 11 is a method according to aspect 10, wherein the response to the beam failure warning report is received from the network node via a fourth MAC-CE or a third DCI message.

[0217] Aspect 12 is a method according to any one of aspects 10 and 11, wherein the response to the beam failure warning report includes an indication of beam switching.

[0218] Aspect 13 is a method according to any one of aspects 10 to 12, wherein the beam failure warning report includes at least one of a channel measurement report, a BFI count, a BFI pattern, or a BFI history.

[0219] Aspect 14 is a method according to any one of Aspects 1 to 13, comprising: identifying that the existing DRX off period is greater than a predetermined multiple of a second DRX on period; waking up for a second time period during the existing DRX off period in response to identifying that the existing DRX off period is greater than the predetermined multiple of the second DRX on period; sending an indication of the wake-up to the network node via a fifth MAC-CE or a third UCI message, wherein the indication of the wake-up includes an indication that the wake-up is based on one or more pre-configured parameters, or an indication that the wake-up corresponds to an early start of a third DRX on period immediately after the existing DRX off period; and monitoring a response to the indication of the wake-up from the network node.

[0220] Aspect 15 is a method for performing wireless communications at a network node, comprising receiving a request from a UE to extend a first DRX on period immediately preceding an existing DRX off period based on satisfying a first condition; sending an indication to the UE of approval of the request to extend the first DRX on period; and based on the approval of the request to extend the first DRX on period, delaying the start of the existing DRX off period by a first time period.

[0221] Aspect 16 is a method according to aspect 15, wherein the request to extend the first DRX on period is received from the UE via a first MAC-CE or a first UCI message.

[0222] Aspect 17 is a method according to any one of aspects 15 and 16, wherein the approval of the request to extend the first DRX on period includes an indication of the first time period.

[0223] Aspect 18 is a method according to any one of aspects 15 to 17, wherein the indication of the approval of the request to extend the first DRX on period is sent to the UE via a PDCCH.

[0224] Aspect 19 is a method according to any one of Aspects 15 to 18, wherein the first condition is met if: a first number of BFI indicators is greater than a first threshold, a second number of consecutive BFI indicators is greater than a second threshold, the channel strength decreases by more than a third threshold, the UE has more data to send to the network node during the first DRX on period than is possible without extending the first DRX on period, the network node has more data to send to the UE during the first DRX on period than is possible without extending the first DRX on period, or the UE predicts a beam failure during the existing DRX off period.

[0225] Aspect 20 is a method according to any one of Aspects 15 to 19, further comprising: sending one or more DRX configuration sets to the UE via RRC signaling; and sending an indication of one of the one or more DRX configuration sets to the UE via a second MAC-CE or a first DCI message.

[0226] Aspect 21 is a method according to aspect 20, wherein at least one of the one or more DRX configuration sets includes at least one of a DRX on period extension configuration, a beam failure warning configuration, or a supplementary DRX wake-up configuration.

[0227] Aspect 22 is a method according to any one of Aspects 15 to 21, further comprising: receiving a request to activate or deactivate one or more DRX-related mechanisms from the UE via a third MAC-CE or a second UCI message; and sending an indication to activate or deactivate the one or more DRX-related mechanisms to the UE via a fourth MAC-CE or a second DCI message.

[0228] Aspect 23 is a method according to aspect 22, wherein the one or more DRX-related mechanisms include one or more of a DRX on-period extension mechanism, a beam failure warning mechanism, or a supplementary DRX wake-up mechanism.

[0229] Aspect 24 is a method according to any one of Aspects 15 to 23, further comprising: receiving a beam failure warning report based on a predicted beam failure from the UE; and sending a response to the beam failure warning report to the UE during a predetermined second time period during the existing DRX off period after expiration of a first timer, wherein the first timer is started at the beginning of the existing DRX off period.

[0230] Aspect 25 is a method according to aspect 24, wherein the response to the beam failure warning report is sent to the UE via a fourth MAC-CE or a third DCI message.

[0231] Aspect 26 is a method according to any one of aspects 24 and 25, wherein the response to the beam failure warning report includes an indication of beam switching.

[0232] Aspect 27 is a method according to any one of aspects 24 to 26, wherein the beam failure warning report includes at least one of a channel measurement report, a BFI count, a BFI pattern, or a BFI history.

[0233] Aspect 28 is a method according to any one of Aspects 15 to 27, further comprising: receiving an indication from the UE via a fifth MAC-CE or a third UCI message to wake up the UE for a second time period during the existing DRX off period, wherein the waking up of the UE is based on the existing DRX off period being greater than a predetermined multiple of the second DRX on period, and the indication of the wakeup includes an indication that the wakeup is based on one or more preconfigured parameters, or an indication that the wakeup corresponds to an early start of a third DRX on period immediately after the existing DRX off period; and sending a response to the indication of the wakeup to the UE.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: identifying that a first condition is satisfied during a first discontinuous reception (DRX) on period immediately preceding an existing DRX off period; sending a request to a network node to extend the first DRX on period based on satisfying the first condition; receiving an indication from the network node of approval of the request to extend the first DRX On period; and Based on the approval of the request to extend the first DRX On period, a start of the existing DRX Off period is delayed for a first time period.

2. The apparatus of claim 1 , wherein the request to extend the first DRX on period is sent to the network node via a first medium access control (MAC)-control element (CE) (MAC-CE) or a first uplink control information (UCI) message. 3 . The apparatus of claim 1 , wherein the approval of the request to extend the first DRX On period comprises an indication of the first time period.

4. The apparatus of claim 1, wherein the indication of the approval of the request to extend the first DRX On period is received from the network node via a physical downlink control channel (PDCCH).

5. The apparatus of claim 1, wherein if: a first number of beam failure instance (BFI) indicators is greater than a first threshold, a second number of consecutive BFI indicators is greater than a second threshold, The channel strength decreases beyond the third threshold, the UE has more data to send to the network node during the first DRX On period than would be possible without extending the first DRX On period, and the network node has more data to send to the UE during the first DRX On period than would be possible without extending the first DRX On period, or The first condition is met if the UE predicts beam failure during the existing DRX off period.

6. The apparatus of claim 1 , wherein the at least one processor is further configured to: receiving one or more DRX configuration sets from the network node via radio resource control (RRC) signaling; and An indication of one of the one or more DRX configuration sets is received from the network node via a second Medium Access Control (MAC)-Control Element (CE) (MAC-CE) or a first Downlink Control Information (DCI) message.

7. The apparatus of claim 6, wherein at least one of the one or more DRX configuration sets comprises at least one of a DRX on-period extension configuration, a beam failure warning configuration, or a supplemental DRX wake-up configuration.

8. The apparatus of claim 1, wherein the at least one processor is further configured to: sending a request to activate or deactivate one or more DRX-related mechanisms to the network node via a third medium access control (MAC)-control element (CE) (MAC-CE) or a second uplink control information (UCI) message; and An indication to activate or deactivate the one or more DRX-related mechanisms is received from the network node via a fourth MAC-CE or a second DCI message.

9. The apparatus of claim 8, wherein the one or more DRX-related mechanisms include one or more of a DRX on-period extension mechanism, a beam failure warning mechanism, or a supplemental DRX wake-up mechanism.

10. The apparatus of claim 1, wherein the at least one processor is further configured to: predicting, during the first DRX on period, a beam failure during the existing DRX off period; sending a beam failure warning report based on the prediction of the beam failure to the network node; monitoring a response to the beam failure warning report from the network node within a predetermined second time period during the existing DRX off period after expiration of a first timer, the first timer being started at the start of the existing DRX off period; and The response to the beam failure warning report is received from the network node during the predetermined second time period.

11. The apparatus of claim 10, wherein the response to the beam failure warning report is received from the network node via a fourth medium access control (MAC)-control element (CE) (MAC-CE) or a third downlink control information (DCI) message.

12. The apparatus of claim 10, wherein the response to the beam failure warning report comprises an indication of beam switching.

13. The apparatus of claim 10, wherein the beam failure warning report comprises at least one of a channel measurement report, a beam failure instance (BFI) count, a BFI pattern, or a BFI history.

14. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor, the at least one processor being further configured to: Identify that the existing DRX off period is greater than a predetermined multiple of the second DRX on period; waking up for a second time period during the existing DRX OFF period in response to identifying that the existing DRX OFF period is greater than the predetermined multiple of the second DRX ON period; sending an indication of the wakeup to the network node via a fifth medium access control (MAC)-control element (CE) (MAC-CE) or a third uplink control information (UCI) message, wherein the indication of the wakeup includes an indication that the wakeup is based on one or more preconfigured parameters, or an indication that the wakeup corresponds to an early start of a third DRX on period immediately following the existing DRX off period; and A response to the indication of the wakeup from the network node is monitored.

15. A method of wireless communication at a user equipment (UE), comprising: identifying that a first condition is satisfied during a first discontinuous reception (DRX) on period immediately preceding an existing DRX off period; sending a request to a network node for extending the first DRX on period; receiving an indication of approval of the request to extend the first DRX On period from the network node; as well as Based on the approval of the request to extend the first DRX On period, a start of the existing DRX Off period is delayed for a first time period.

16. An apparatus for wireless communication at a network node, comprising: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving, from a user equipment (UE), a request to extend a first discontinuous reception (DRX) on period immediately preceding an existing DRX off period based on satisfying a first condition; sending an indication to the UE of approval of the request to extend the first DRX on period; and Based on the approval of the request to extend the first DRX On period, a start of the existing DRX Off period is delayed for a first time period.

17. The apparatus of claim 16, wherein the first medium access control (MAC) - receiving the request to extend the first DRX on period from the UE via a control element (CE) (MAC-CE) or a first uplink control information (UCI) message.

18. The apparatus of claim 16, wherein the approval of the request to extend the first DRX On period comprises an indication of the first time period.

19. The apparatus of claim 16, wherein the indication of the approval of the request to extend the first DRX On period is sent to the UE via a physical downlink control channel (PDCCH).

20. The apparatus of claim 16, wherein if: a first number of beam failure instance (BFI) indicators is greater than a first threshold, a second number of consecutive BFI indicators is greater than a second threshold, The channel strength decreases beyond the third threshold, the UE has more data to send to the network node during the first DRX On period than would be possible without extending the first DRX On period, and the network node has more data to send to the UE during the first DRX On period than would be possible without extending the first DRX On period, or The first condition is met if the UE predicts beam failure during the existing DRX off period.

21. The apparatus of claim 16, wherein the at least one processor is further configured to: sending one or more DRX configuration sets to the UE via radio resource control (RRC) signaling; and An indication of one of the one or more DRX configuration sets is sent to the UE via a second medium access control (MAC)-control element (CE) (MAC-CE) or a first downlink control information (DCI) message.

22. The apparatus of claim 21, wherein at least one of the one or more DRX configuration sets comprises at least one of a DRX on-period extension configuration, a beam failure warning configuration, or a supplemental DRX wake-up configuration.

23. The apparatus of claim 16, wherein the at least one processor is further configured to: receiving a request to activate or deactivate one or more DRX-related mechanisms from the UE via a third medium access control (MAC)-control element (CE) (MAC-CE) or a second uplink control information (UCI) message; and An indication of activating or deactivating the one or more DRX-related mechanisms is sent to the UE via a fourth MAC-CE or a second DCI message.

24. The apparatus of claim 23, wherein the one or more DRX-related mechanisms include one or more of a DRX on-period extension mechanism, a beam failure warning mechanism, or a supplemental DRX wake-up mechanism.

25. The apparatus of claim 16, wherein the at least one processor is further configured to: receiving a beam failure warning report based on a predicted beam failure from the UE; and A response to the beam failure warning report is sent to the UE during a predetermined second time period during the existing DRX off period after expiration of a first timer, the first timer being started at the beginning of the existing DRX off period.

26. The apparatus of claim 25, wherein the response to the beam failure warning report is sent to the UE via a fourth medium access control (MAC)-control element (CE) (MAC-CE) or a third downlink control information (DCI) message.

27. The apparatus of claim 25, wherein the response to the beam failure warning report comprises an indication of beam switching.

28. The apparatus of claim 25, wherein the beam failure warning report comprises at least one of a channel measurement report, a beam failure instance (BFI) count, a BFI pattern, or a BFI history.

29. The apparatus of claim 16, further comprising a transceiver coupled to the at least one processor, the at least one processor further configured to: receiving, from the UE via a fifth medium access control (MAC)-control element (CE) (MAC-CE) or a third uplink control information (UCI) message, an indication to wake up the UE for a second time period during the existing DRX off period, wherein the waking up of the UE is based on the existing DRX off period being greater than a predetermined multiple of a second DRX on period, the indication of the waking up comprising an indication that the waking up is based on one or more preconfigured parameters, or an indication that the waking up corresponds to an early start of a third DRX on period immediately following the existing DRX off period; and and sending a response to the indication of the wakeup to the UE.

30. A method for wireless communication at a network node, comprising: receiving, from a user equipment (UE), a request to extend a first discontinuous reception (DRX) on period immediately preceding an existing DRX off period based on satisfying a first condition; sending an indication to the UE of approval of the request to extend the first DRX on period; as well as Based on the approval of the request to extend the first DRX On period, a start of the existing DRX Off period is delayed for a first time period.

Images