Beam quality enhancement techniques in discontinuous reception (DRX) mode

Abstract

Certain aspects of the present disclosure provide a method for wireless communication by a user equipment (UE). The UE receives a beam monitoring configuration indicating at least one condition to be satisfied for transmission of a beam condition report. The UE monitors at least one beam fault detection (BFD) reference signal (RS) during an on duration of a discontinuous reception (DRX) cycle. When the at least one condition is satisfied during the on-duration of the DRX cycle, the UE transmits the beam condition report at the end of the on-duration of the DRX cycle.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. patent application No. 17 / 804,275, filed on May 26, 2022, which is assigned to the assignee of the present application and is hereby expressly incorporated by reference in its entirety, as if fully set forth below and for all applicable purposes. Background Art Technical Field

[0003] Various aspects of the present disclosure relate to wireless communications, and more particularly to beam management techniques for use in a discontinuous reception (DRX) mode.

[0004] Related technologies

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available wireless communication system resources with those users.

[0006] Although wireless communication systems have made tremendous technical progress over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Therefore, there is a continuous desire to improve the technical performance of wireless communication systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of using shared communication media, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Therefore, there is a need to further improve wireless communication systems to overcome the above-mentioned technical challenges and other challenges. Summary of the invention

[0007] One aspect provides a method for wireless communication by a user equipment (UE), the method comprising: receiving a beam monitoring configuration indicating at least one condition to be satisfied for sending a beam condition report; monitoring at least one beam failure detection (BFD) reference signal (RS) during an on duration of a discontinuous reception (DRX) cycle; and when the at least one condition is satisfied during the on duration of the DRX cycle, sending the beam condition report at the end of the on duration of the DRX cycle.

[0008] On the other hand, a method for wireless communication by a network entity is provided, the method comprising: configuring a UE with a beam monitoring configuration, the beam monitoring configuration indicating at least one condition to be met in monitoring of a BFD-RS for sending a beam condition report during an on-duration of a DRX cycle; and receiving a beam condition report at the end of the on-duration of the DRX cycle when the at least one condition is met during the on-duration of the DRX cycle.

[0009] Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform the aforementioned method and those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the aforementioned method and those described elsewhere herein; a computer program product embodied on a computer-readable storage medium, the computer program product comprising code for performing the aforementioned method and those described elsewhere herein; and an apparatus comprising components for performing the aforementioned method and those described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating through one or more networks.

[0010] For purposes of illustration, the following description and drawings set forth certain features. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings depict certain features of the aspects described herein and should not be considered to limit the scope of the disclosure.

[0012] Figure 1 An example wireless communication network is depicted.

[0013] Figure 2 An example decomposed base station (BS) architecture is depicted.

[0014] Figure 3 Aspects of an example BS and example user equipment (UE) are depicted.

[0015] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures for a wireless communication network are described.

[0016] Figure 5 An example timeline for a discontinuous reception (DRX) cycle is illustrated.

[0017] Figure 6 An example timeline for connected mode DRX (C-DRX) operation is illustrated.

[0018] Figure 7 Example beam monitoring by a UE is illustrated.

[0019] Figure 8 An example beam failure instance (BFI) indicator at each opportunity of a beam failure detection (BFD) reference signal (RS) is illustrated.

[0020] Fig. 9 Example beam monitoring during the on duration of a DRX cycle is illustrated.

[0021] Fig.10 A call flow diagram depicts example communications between a UE and a network entity.

[0022] Fig.11 Depicted is an example transmission of a beam condition report at the end of the on duration of a DRX cycle.

[0023] Fig.12 Depicted is an example monitoring of a response to a beam condition report from a network entity during a second predetermined time period following a first predetermined time period.

[0024] Fig.13 Methods for wireless communications by a UE are described.

[0025] Fig.14 Methods for wireless communications by a network entity are described.

[0026] Fig.15 Aspects of an example communications device are depicted.

[0027] Fig.16 Aspects of an example communications device are depicted. DETAILED DESCRIPTION

[0028] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for beam management in a discontinuous reception (DRX) mode.

[0029] Advanced wireless systems, such as 5G New Radio (NR), utilize higher frequencies (e.g., mmWave) and a larger number of antennas to perform beamforming. Beamforming refers to a signal processing technique that allows a device (e.g., a network entity) to transmit using a directional beam targeted at an intended recipient (e.g., a user equipment (UE)). Beamforming can help to efficiently use frequency resources by controlling the direction of transmission to reduce interference.

[0030] Unfortunately, one potential hazard associated with beamforming is blocking. Blocking refers to a scenario where a device (e.g., a blocking entity) is present in the beam path, which can abruptly interrupt communications and cause beam failure. To detect beam failure, the UE typically measures a beam failure detection (BFD) reference signal (BFD-RS) and determines whether a beam failure trigger condition is met (e.g., based on defined criteria). If a beam failure is detected, a beam failure recovery (BFR) procedure may be performed in which the UE transmits a beam failure recovery request (BFRQ) to a network entity.

[0031] There are various potential problems with the existing BFD process. One potential problem is that the existing BFD process may not work in DRX mode. This is because the BFD process requires the UE to constantly monitor the physical (PHY) layer to calculate beam quality and determine beam failure. However, in DRX mode, the UE can only monitor the PHY layer during the on duration of the DRX cycle because the UE goes to sleep during the off duration of the DRX cycle. As a result, since the UE does not monitor the PHY layer during the off duration of the DRX cycle, the UE cannot calculate the beam quality during the off duration of the DRX cycle.

[0032] For various applications, it may be necessary for the UE to maintain good beam quality throughout the DRX cycle to ensure that the UE can immediately send data to the network entity when needed. This can help the UE meet the Quality of Service (QoS) requirements associated with the application. However, in some cases, when the beam may be of low quality and the UE cannot declare a beam failure and initiate BFR during the on duration of the DRX cycle, this may cause the communication link between the UE and the network entity to be suddenly interrupted at some later time, and the UE may not be able to send data during the interruption.

[0033] The techniques proposed in this article can help manage the beam quality of data services throughout the DRX cycle. For example, when the UE determines that there are some problems with the beam during the on duration of the DRX cycle (for example, the channel strength drops), but cannot confirm the beam failure at the end of the on duration of the DRX cycle, the UE generates a beam condition report associated with the current beam at the end of the on duration of the DRX cycle and sends it to the network entity. The beam condition report may indicate a potential beam failure and / or a request to switch beams. The network entity may switch beams based on the beam condition report to ensure that the communication link between the UE and the network entity is not interrupted throughout the DRX cycle.

[0034] The techniques proposed herein may help achieve maintaining beam quality throughout the DRX cycle, which may result in reduced latency (eg, due to no data transmission interruption) and improved quality of service (QoS).

[0035] Introduction to wireless communication networks

[0036] The techniques and methods described herein can be used in various wireless communication networks. Although various aspects may be described herein using terms commonly associated with 3G, 4G and / or 5G wireless technologies, various aspects of the present disclosure may also be applicable to other communication systems and standards not explicitly mentioned herein.

[0037] Figure 1 An example of a wireless communication network 100 is depicted in which various aspects described herein may be implemented.

[0038] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is typically a communication device and / or a communication function performed by a communication device (e.g., user equipment (UE), base station (BS), component of a BS, server, etc.). For example, various functions of a network and various devices associated with and interacting with the network may be considered network entities. In addition, the wireless communication network 100 includes ground aspects, such as ground-based network entities (e.g., BS 102), and non-ground aspects, such as satellites 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) that can communicate with other network elements (e.g., ground BSs) and UEs.

[0039] In the depicted example, the wireless communication network 100 includes a BS 102, a UE 104, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190) that interoperate to provide communication services over various communication links (including wired and wireless links).

[0040] Figure 1 Various example UEs 104 are depicted, which may more generally include: a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an Always-On (AON) device, an edge processing device, or other similar devices. UE 104 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.

[0041] BS 102 wirelessly communicates with (e.g., transmits signals to or receives signals from) UE 104 via communication link 120. Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also referred to as a reverse link) transmissions from UE 104 to BS 102 and / or downlink (DL) (also referred to as a forward link) transmissions from BS 102 to UE 104. In various aspects, communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.

[0042] BS 102 may generally include: NodeB, enhanced NodeB (eNB), next generation enhanced NodeB (ng-eNB), next generation NodeB (gNB or gNodeB), access point, transceiver base station, radio BS, radio transceiver, transceiver function, transmission and reception point, and / or other. Each of BS 102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell, and may overlap in some cases (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, a BS may provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (relatively small geographic area (e.g., a home)), and / or other types of cells.

[0043] Although BS102 is depicted as a single communication device in various aspects, BS102 can be implemented in various configurations. For example, one or more components of BS102 may be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, to name a few examples. In another example, various aspects of BS102 may be virtualized. More generally, a BS (e.g., BS102) may include components located at a single physical location or components located at various physical locations. In an example in which BS102 includes components located at various physical locations, each component may perform each function so that each component together achieves functionality similar to that of a BS 102 located at a single physical location. In some aspects, a BS102 including components located at various physical locations may be referred to as a decomposed radio access network (RAN) architecture, such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture. Figure 2 An example decomposed BS architecture is depicted and described.

[0044] Different BSs 102 within the wireless communication network 100 may also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) over a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0045] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 600 MHz-6 GHz, which is often (interchangeably) referred to as "below 6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 26 GHz–41 GHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A BS (e.g., a mmWave BS such as BS 180) configured to communicate using mmWave / near mmWave radio bands may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and distance.

[0046] The communication link 120 between the BS 102 and, for example, the UE 104 may be through one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and / or other MHz) and may be aggregated in various aspects. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL).

[0047] Communications using higher frequency bands may have higher path loss and shorter range than communications at lower frequencies. Therefore, some BSs (e.g. Figure 1180) may utilize beamforming 182 with UE 104 to improve path loss and distance. For example, BS 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels and / or antenna arrays) to facilitate beamforming. In some cases, BS 180 may send beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from BS 180 in one or more receive directions 182". UE 104 may also send beamformed signals to BS 180 in one or more transmit directions 182". BS 180 may also receive beamformed signals from UE 104 in one or more receive directions 182'. BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. It is noteworthy that the transmit direction and receive direction of BS 180 may be the same or different. Similarly, the transmit direction and receive direction of UE 104 may be the same or different.

[0048] Wireless communication network 100 also includes Wi-Fi AP 150 that communicates with Wi-Fi station (STA) 152 via communication link 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0049] Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0050] The EPC 160 may include various functional components, including: a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and / or a packet data network (PDN) gateway 172, such as in the depicted example. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management.

[0051] Typically, user Internet Protocol (IP) packets are delivered through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming media service, and / or other IP services.

[0052] The BM-SC 170 may provide functionality for MBMS user service configuration and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or may be used to schedule MBMS delivery. The MBMS Gateway 168 may be used to distribute MBMS services to BSs 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a specific service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

[0053] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 192, other AMFs 193, session management function (SMF) 194, and user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196.

[0054] AMF 192 is a control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides, for example, Quality of Service (QoS) flow and session management.

[0055] Internet Protocol (IP) packets are delivered through UPF 195, which connects to IP Services 197 and provides IP address allocation for UEs and other functions for 5GC 190. IP Services 197 may include, for example, the Internet, Intranet, IMS, PS streaming services, and / or other IP services.

[0056] The wireless communication network 100 also includes a beamforming component 198, which can be configured to perform Fig.13 The wireless communication network 100 also includes a beamforming component 199, which may be configured to perform Fig.14 Operation 1400.

[0057] In various aspects, a network entity or network node may be implemented as a converged BS, a decomposed BS, a component of a BS, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.

[0058] Figure 2 An example decomposed BS 200 architecture is depicted. The decomposed BS 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed BS units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. The RU 240 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 240.

[0059] Each of the units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally or alternatively, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0060] In some aspects, CU 210 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 210. CU210 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 210 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 210 may be implemented to communicate with DU 230 for network control and signaling.

[0061] The DU 230 may correspond to a logical unit that includes one or more BS functions for controlling the operation of one or more RUs 240. In some aspects, the DU 230 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.) based at least in part on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 230 or with control functions hosted by the CU 210.

[0062] The lower layer functionality may be implemented by one or more RUs 240. In some deployments, a RU 240 controlled by a DU 230 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 a functional split (such as a lower layer functional split). In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the implementation of the DU 230 and the CU 210 in a cloud-based RAN architecture (such as a vRAN architecture).

[0063] The SMO framework 205 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 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 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) 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 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, the SMO framework 205 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 211) via the O1 interface. Additionally, in some specific implementations, the SMO framework 205 may communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

[0064] The non-RT RIC 215 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 225. The non-RT RIC 215 may be coupled to or in communication with the near-RT RIC 225 (such as via an A1 interface). The near-RT RIC 225 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 210, one or more DUs 230, or both, and the O-eNB with the near-RT RIC 225.

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

[0066] Figure 3 Aspects of an example BS 102 and UE 104 are depicted.

[0067] In general, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively 334), transceivers 332a-332t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement various functions described herein related to wireless communication.

[0068] BS 102 includes a controller / processor 340 that can be configured to perform various functions related to wireless communication. In the depicted example, controller / processor 340 includes a beamforming component 341, which can represent Figure 1 The beam component 199. It is worth noting that, although depicted as an aspect of the controller / processor 340, in other specific implementations, the beam component 341 may additionally or alternatively be implemented in various other aspects of the BS 102.

[0069] In general, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively 352), transceivers 354a-354r (collectively 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 362) and wireless reception of data (e.g., provided to a data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communications.

[0070] UE 104 includes a controller / processor 380 that can be configured to perform various functions related to wireless communication. In the depicted example, the controller / processor 380 includes a beamforming component 381, which can represent Figure 1 Beamforming component 198. Note that while depicted as one aspect of controller / processor 380, in other implementations, beamforming component 381 may additionally or alternatively be implemented in various other aspects of UE 104.

[0071] Regarding example downlink transmissions, BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or others. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0072] The transmit processor 320 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols, such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS).

[0073] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to a modulator (MOD) in transceivers 332a to 332t. Each modulator in transceivers 332a-332t may process a corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 332a-332t may be transmitted via antennas 334a-334t, respectively.

[0074] To receive downlink transmissions, UE 104 includes antennas 352a-352r that can receive downlink signals from BS 102 and can provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0075] A MIMO detector 356 may obtain received symbols from all demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0076] With respect to example uplink transmissions, the UE 104 also includes a transmit processor 364 that may receive and process data from a data source 362 (e.g., for a PUSCH) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 364 may also generate reference symbols for reference signals (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 364 may be pre-decoded by a TX MIMO processor 366, if applicable, further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM), and transmitted to the BS 102.

[0077] At BS 102, uplink signals from UE 104 may be received by antennas 334 a-334 t, processed by demodulators in transceivers 332 a-332 t, detected by MIMO detector 336 if applicable, and further processed by receive processor 338 to obtain decoded data and control information transmitted by UE 104. Receive processor 338 may provide decoded data to data sink 339 and decoded control information to controller / processor 340.

[0078] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0079] Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0080] In various aspects, BS 102 may be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 312, a scheduler 344, a memory 342, a transmit processor 320, a controller / processor 340, a TX MIMO processor 330, a transceiver 332a-332t, an antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 334a-334t, a transceiver 332a-332t, a RX MIMO detector 336, a controller / processor 340, a receive processor 338, a scheduler 344, a memory 342, and / or other aspects described herein.

[0081] In various aspects, the UE 104 may also be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 362, a memory 382, ​​a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-354t, an antenna 352a-352t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 352a-352t, a transceiver 354a-354t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, ​​and / or other aspects described herein.

[0082] In some aspects, the processor may be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.

[0083] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes a method for use in a wireless communication network such as Figure 1 Various aspects of the data structure of the wireless communication network 100).

[0084] Specifically, Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4DFIG480 is a diagram illustrating an example of UL channels within a 5G subframe.

[0085] Wireless communication systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems may also support half-duplex operation using time division duplex (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) can be used to maximize the system bandwidth (e.g., Figure 4B and Figure 4D ) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0086] The wireless communication frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to both DL and UL.

[0087] exist Figure 4A and Figure 4C In the wireless communication frame structure, TDD is used, where D is DL, U is UL, and X can be used flexibly between DL / UL. The UE can be configured with a time slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received time slot format indicator (SFI). In the depicted example, the 10ms frame is divided into 10 equally sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. The subframe may also include a micro-time slot, which typically has fewer symbols than a whole time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0088] In certain aspects, the number of time slots within a subframe is based on the time slot configuration and the parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 time slots per subframe, respectively. Thus, for time slot configuration 0 and parameter set μ, there are 14 symbols / time slot and 2μ time slots / subframe. The subcarrier spacing and symbol length / duration are a function of the parameter set. The subcarrier spacing may be equal to 2 μ × 15kHz, where μ is parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A, Figure 4B , Figure 4C and Figure 4D An example is provided for slot configuration 0 with 14 symbols per slot and a parameter set with μ = 2, 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0089] like Figure 4A , Figure 4B , Figure 4C and Figure 4D As depicted in , a resource grid can be used to represent a frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) extending, for example, 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.

[0090] like Figure 4A As illustrated, some of the REs carry data for UEs (eg, Figure 1 and Figure 3 The RS may include a demodulation RS (DMRS) and / or 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 / or a phase tracking RS (PT-RS).

[0091] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated.The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE Groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0092] The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is transmitted by a UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identification.

[0093] The Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0094] Based on the physical layer identifier and the physical layer cell identifier group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. 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. 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 (such as system information blocks (SIBs)) that is not sent via the PBCH, and / or paging messages.

[0095] like Figure 4C As illustrated, some of the REs carry DMRS for channel estimation at the BS (indicated as R for one particular configuration, but other DMRS configurations are possible). The UE may send a DMRS for the PUCCH and a DMRS for the PUSCH. The PUSCH DMRS may be sent, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used. The UE 104 may send a sounding reference signal (SRS). The SRS may be sent, for example, 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 combs. The SRS may be used by the BS for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0096] Figure 4D 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 HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0097] Example Discontinuous Reception (DRX) Cycle

[0098] Connected mode discontinuous reception (CDRX) improves UE battery power consumption by allowing the user equipment (UE) to periodically enter a sleep state (e.g., an off duration) during which it does not need to monitor the physical downlink control channel (PDCCH). In order to monitor the PDCCH for possible downlink / uplink data, the UE is allowed to wake up periodically and stay awake (e.g., an on duration) for a certain amount of time before going to sleep again.

[0099] The network entity configures the UE with a set of CDRX parameters. The CDRX parameters can be selected based on the application type so as to maximize power and resource savings. When CDRX is implemented, UE power consumption is reduced.

[0100] like Figure 5 and Figure 6 As illustrated, during periods of traffic inactivity, the UE switches to CDRX operation for power saving. The UE is configured for CDRX operation according to various configuration parameters, such as an inactivity timer, a short DRX (discontinuous reception) timer, a short DRX cycle, and a long DRX cycle.

[0101] A long DRX cycle may be characterized by an active state and a sleep state. A long DRX cycle may not be suitable for certain services that require a period of data transmission followed by a period of inactivity. In such cases, the network entity has the flexibility to configure the long DRX cycle together with an additional DRX cycle that is shorter than the long DRX cycle. The additional DRC cycle is a short DRX cycle.

[0102] When the network entity has configured a short DRX cycle, this means that both a long DRX cycle and a short DRX cycle are configured. In some cases, configuring a short DRX cycle is optional, and if not configured, the UE follows the long DRX cycle as usual. Whenever the network entity configures a short DRX cycle, the network entity ensures that the long DRX cycle duration is an integer multiple of the short DRX cycle duration. This means that the short DRX cycle duration is shorter than the long DRX cycle duration.

[0103] Based on the configured CDRX cycle, the UE occasionally wakes up for the on duration and monitors the PDCCH transmission. In addition to the on duration, for the rest of the CDRX cycle, the UE may remain in a low power (sleep) state called the off duration. During the off duration, the UE does not expect to send and receive any signal.

[0104] In CDRX mode, the UE wakes up after a CDRX cycle (during the CDRX on period) and sends and / or receives (TX / RX) data packets. In some cases, if the UE detects PDCCH scheduled data during the on duration, the UE remains on to send and receive data. Otherwise, the UE returns to sleep at the end of the on duration. This type of CDRX mode has been used for many years and is still the default behavior for some new radio (NR) networks and UEs.

[0105] In some cases, with a periodic CDRX cycle, the UE may wake up frequently, even when the UE has no data to send and / or to monitor for data (e.g., indicated by paging), which wastes UE power. Although expanding the CDRX cycle may cause the UE to wake up less frequently, this may also result in increased data service latency (e.g., if the UE has data packets to send well before the next CDRX on duration). This is because there may be an extended delay in receiving data because the UE may be in a dormant state when the data arrives. The latency increases with the CDRX cycle length, i.e., the longer the CDRX cycle length, the higher the latency. Therefore, the CDRX parameters are selected so that packet delay is minimized and power savings are maximized.

[0106] Example Beam Monitoring Process

[0107] In some systems, narrow beam transmission and reception are useful for improving link budgets at millimeter wave (mmW) frequencies, but may be susceptible to beam failures. In mmW, directional beamforming is used between user equipment (UE) and a network entity (e.g., a base station (BS)), and the UE and network entity communicate via a beam pair link (BPL). This may allow the network entity to transmit an aimed beam to the UE, reduce interference, and efficiently use the spectrum with improved spectral efficiency.

[0108] Beam failure refers to a scenario where the beam quality drops below a threshold, which may result in a radio link failure (RLF). In response to RLF, the UE may perform a cell reselection procedure, in which the UE may use neighbor BS information obtained from a decoded neighbor advertisement message, or may schedule a scanning / sleeping interval to scan neighbor BSs for handover to a potential target BS.

[0109] like Figure 7 As illustrated, the UE is configured to monitor a set of beam failure detection (BFD) reference signals (RS) (e.g., synchronization signal block (SSB) / channel state information (CSI)-RS beams) for measuring beam quality. The UE may monitor BFD-RS from a primary cell (Pcell), a primary secondary cell (PScell), and / or a secondary cell (Scell) (e.g., a coverage area of ​​a BS).

[0110] The UE detects a beam failure when a beam failure trigger condition is met (e.g., based on a measurement parameter associated with the BFD-RS). In one example, BFD is triggered when the estimated block error rate (BLER) of the BFD-RS associated with the configured control resource set (CORESET) is above a threshold (e.g., 10%). In another example, the UE detects a beam failure when the reference signal received power (RSRP) or other signal quality measurement associated with the BFD-RS fails to meet (e.g., is below) a threshold. Once a beam failure is detected, the UE initiates a beam failure recovery (BFR) procedure.

[0111] In some cases, BFD is a combined Layer 1 (L1) / Layer 2 (L2) process in which the L1 may provide a Medium Access Control (MAC) layer indication of a beam failure instance (BFI). The UE may determine the BFI indicator at each opportunity of the BFD-RS. The MAC layer counts the indications of the BFI and declares a beam failure when the configured maximum number of BFI indications is reached.

[0112] For example, Figure 8 As illustrated, when the physical (PHY) layer detects that the RSRP of the BFD-RS of the serving beam is below a threshold, the PHY layer triggers a first BFI and transmits an indication of the first BFI to the MAC layer. Upon receiving the indication of the first BFI, the MAC layer starts a BFD timer. For each new BFI indicator, the MAC layer increases the BFI count by 1. In some cases, when a specific threshold of BFI is reached before the BFD timer expires (e.g., when the BFI counter is greater than or equal to the maximum count of BFI (e.g., 4)), the MAC layer declares a beam failure and initiates BFR. In some cases, when a specific threshold of BFI is not reached before the BFD timer expires (e.g., when the BFI counter is less than the maximum count of BFI), the MAC layer does not declare a beam failure. In such cases, the BFD timer and the BFI counter are reset (e.g., reset to 0).

[0113] Example beam monitoring in discontinuous reception (DRX) mode

[0114] Conventional beam failure detection (BFD) procedures may not work in discontinuous reception (DRX) mode. For example, conventional BFD procedures require user equipment (UE) to continuously monitor the physical (PHY) layer to calculate beam quality and determine beam failure based on estimated BFD reference signal (RS) measurements. However, in DRX mode, the UE can only monitor the PHY layer during the on duration of the DRX cycle because the UE goes to sleep during the off duration of the DRX cycle. As a result, since the UE does not monitor the PHY layer during the off duration of the DRX cycle, the UE cannot calculate beam quality during the off duration of the DRX cycle.

[0115] Depending on the quality of service (QoS) requirements of the service business, the UE may have to maintain good beam quality throughout the DRX cycle to ensure that the UE can send data to the network entity immediately when needed. For example, in an extended reality (XR) application, a UE executing an XR application must send gesture data (e.g., user eye or hand movements in a video game) to the network entity before a deadline, otherwise the gesture data (transmitted after the deadline) will be discarded and may negatively affect the user's experience of playing the video game on the UE.

[0116] In some DRX mode situations, such as Fig. 9 As illustrated, the UE may start performing a BFD process during the on duration of the DRX cycle and detect potential problems with the current BFD-RS beam. However, due to the limited time of the on duration of the DRX cycle, the UE may not be able to confirm the beam quality of the current BFD-RS beam at the end of the on duration of the DRX cycle. The UE may suspend the BFD process at the end of the on duration of the DRX cycle, and then continue the BFD process again during the next on duration of the DRX cycle. However, as described above, some application / service data services may require consistent beam quality maintenance. For example, in XR applications, the UE may need to consistently maintain good beam quality to facilitate timely sending of data (e.g., attitude data) whenever there is a gesture data update. In such cases, since the current BFD-RS beam may be of low quality (but the UE cannot declare a beam failure and initiate BFR during the on duration of the DRX cycle), this may cause the communication link between the UE and the network entity to be suddenly interrupted at a later time, and the UE may not be able to send data (e.g., attitude data) during the interruption. Therefore, enhanced techniques are needed to ensure that the beam quality of data services is maintained throughout the DRX cycle.

[0117] Aspects related to beam quality enhancement techniques in DRX mode

[0118] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for beam management in a discontinuous reception (DRX) mode.

[0119] For example, when a user equipment (UE) determines that there are some problems (e.g., channel strength drops) with a current beam during the on duration of a DRX cycle, but cannot confirm beam failure at the end of the on duration of the DRX cycle, the UE generates a beam condition report associated with the current beam and sends it to a network entity. The beam condition report may indicate a potential beam failure and / or a request to switch beams. The network entity may switch beams based on the beam condition report.

[0120] The techniques proposed in this article ensure that the beam quality of data traffic is maintained throughout the DRX cycle. This can result in reduced latency (e.g., due to no data transmission interruptions), as well as improved quality of service (QoS) and beam conditions. Figures 10 to 14 Understand the techniques presented in this article.

[0121] like Fig.10 As illustrated, at 1002, a network entity (eg, Figure 1 gNodeB (gNB) or BS 102 in the wireless communication network 100 to a UE (e.g., Figure 1 In one example, the beam monitoring configuration indicates at least one condition to be satisfied for the transmission of a beam condition report. In another example, the beam monitoring configuration indicates a beam monitoring set. The beam monitoring set may indicate a set of different beams (e.g., beams that must be monitored).

[0122] In certain aspects, the network entity may send the beam monitoring configuration to the UE using Layer 3 (L3) signaling or a radio resource control (RRC) configuration message.

[0123] In certain aspects, a network entity may use Layer 1 (L1) / Layer 2 (L2) signaling, such as a medium access control (MAC) control element (CE) or downlink control information (DCI), to switch the beam monitoring configuration (e.g., replace at least one condition with a new condition).

[0124] At 1004, the network entity transmits one or more beam failure detection (BFD) reference signals (RS). In one example, the BFD-RS is a synchronization signal block (SSB). In another example, the BFD-RS is a channel state information (CSI)-RS.

[0125] At 1006, the UE may operate in DRX mode and monitor the BFD-RS (eg, during an ON duration of a DRX cycle). The UE determines that the at least one condition is satisfied during BFD-RS monitoring in the ON duration of the DRX cycle.

[0126] In certain aspects, the at least one condition is satisfied based on a decrease in estimated channel strength during an on duration of the DRX cycle. For example, the UE determines that the at least one condition is satisfied when a value of a signal to interference and noise ratio (SINR) of the BFD-RS during an on duration of the DRX cycle decreases by a predetermined value (e.g., X dB) compared to a previous SINR value.

[0127] In certain aspects, when the UE determines a new beam that is not included in the beam monitoring set during the on duration of the DRX cycle (i.e., a new candidate beam that is not in the configured beam monitoring set is found), the UE determines that at least one condition is satisfied.

[0128] In certain aspects, the at least one condition is satisfied when the UE predicts a beam failure during an on duration of a DRX cycle based on one or more signal measurements associated with the BFD-RS. The one or more signal measurements may include a block error rate (BLER) and / or a reference signal received power (RSRP) associated with the BFD-RS.

[0129] At 1008, when the at least one condition is met, the UE generates a beam condition report and sends the beam condition report to the network entity (e.g., at the end of the on duration of the DRX cycle, such as Fig.11 exemplified).

[0130] In certain aspects, the beam condition report indicates information that identifies one or more factors for sending a beam condition report (i.e., a reason for transmitting the beam condition report). The information indicates a potential beam failure and / or a channel strength drop exceeding a threshold (e.g., a predetermined value) within a predetermined time period based on one or more signal measurements associated with the BFD-RS.

[0131] In certain aspects, the beam condition report indicates a status of the BFD. The status of the BFD is based on an indication of a beam failure instance (BFI) at each opportunity of the BFD-RS during BFD-RS monitoring in the on duration of the DRX cycle. The status indicates a current number of total BFI counts and / or a BFI record history (e.g., a previous number of total BFI counts during monitoring of a previous BFD-RS).

[0132] In certain aspects, the beam condition report indicates a channel measurement report associated with a channel between the UE and the network entity. The channel measurement report indicates SINR, signal-to-noise ratio (SNR), RSRP, and / or path loss.

[0133] In certain aspects, the beam condition report indicates a preferred response from the network entity. The preferred response indicates a first request for a beam switch (e.g., switching from a current beam to another beam), a second request for additional new BFD-RS resources to monitor a new beam for BFD, and / or a third request to change a subset of beams within a beam monitoring set.

[0134] In certain aspects, a network entity may configure a user equipment (UE) (e.g., using RRC) with a beam condition reporting configuration indicating one or more types of beam condition reports (e.g., a first type of beam condition report that conveys a beam failure detection status, a second type of beam condition report that indicates a preferred network response). The beam condition reporting configuration may depend on how comprehensive the network entity wants the beam condition report to be and / or how many physical uplink shared channel (PUSCH) resources are available. In certain aspects, the network entity may reconfigure the UE (e.g., using MAC-CE or DCI) with a new beam condition reporting configuration indicating one or more new types of beam condition reports (e.g., a third type of beam condition report that conveys a channel measurement report).

[0135] In certain aspects, the UE may use different transmission options and / or techniques to transmit the beam condition report. These different techniques may be selected based on the size of the beam condition report (e.g., according to the beam condition report configuration).

[0136] In one example, when the size of the beam condition report is smaller than a predetermined size (i.e., the beam condition report has a small size), the UE uses uplink control information (UCI) to send the beam condition report. In another example, when the size of the beam condition report is larger than a predetermined size (i.e., the beam condition report has a large size), the UE uses MAC-CE to send the beam condition report.

[0137] like Fig.12 As illustrated, after sending the beam condition report, the UE monitors a response to the beam condition report from the network entity during a second predetermined time period (e.g., a second timer duration) after the first predetermined time period (e.g., a first timer duration). When no response is received during the second predetermined time period, the UE initiates a retransmission of the beam condition report using a retransmission resource. The network entity may preconfigure the UE with the retransmission resource.

[0138] In one example, the UE is configured to retransmit the beam condition report up to a predetermined number of times (e.g., N times), and each retransmission of the beam condition report is separated by a third predetermined time period (e.g., retransmission after every X milliseconds (ms)).

[0139] In another example, the UE is configured to retransmit the beam condition report in a specific mode, and each retransmission of the beam condition report is separated by a different time period (for example, the beam condition report is retransmitted for the first time within X ms, the beam condition report is retransmitted for the second time within X+Y ms, the beam condition report is retransmitted for the third time within X+Y+Z ms, etc.).

[0140] In certain aspects, a network entity may configure a UE (e.g., using RRC) with a beam condition report retransmission configuration indicating a retransmission procedure and / or retransmission parameters (e.g., retransmission resources) for a beam condition report. The retransmission procedure for the beam condition report is based on QoS requirements of a service traffic, a delay estimate, and / or a path loss estimate.

[0141] Example Operation of User Equipment (UE)

[0142] Fig.13 Example operations 1300 for wireless communication are illustrated. For example, operations 1300 may be performed by a user equipment (UE) (e.g., Figure 1 Operation 1300 may be implemented as a processor (e.g., Figure 3 In addition, the signal transmission and reception performed by the UE in operation 1300 may be performed by one or more antennas (e.g., Figure 3 In some aspects, the signal transmission and / or reception by the UE may be implemented by obtaining and / or outputting signals via a bus interface of one or more processors (eg, controller / processor 380).

[0143] Operations 1300 begin at 1302 by receiving a beam monitoring configuration that indicates at least one condition to be satisfied for transmission of a beam condition report. For example, the UE may use Figure 1 or Figure 3 The antenna and / or transceiver components and / or Fig.15 The antenna and / or transceiver assembly of the apparatus is shown to receive a beam monitoring configuration.

[0144] At 1304, the UE monitors at least one beam failure detection (BFD) reference signal (RS) during an on duration of a discontinuous reception (DRX) cycle. For example, the UE may use Figure 1 or Figure 3 The processor and / or Fig.15 The processor of the apparatus is configured to monitor at least a BFD-RS.

[0145] At 1306, when the at least one condition is satisfied during the on duration of the DRX cycle, the UE sends a beam condition report at the end of the on duration of the DRX cycle. For example, the UE may use Figure 1 or Figure 3 The processor and / or Fig.15 The processor of the device is used to send a beam condition report.

[0146] It should be noted that Fig.13 This is merely one example of a method, and other methods including fewer, additional, or alternative steps may also be consistent with the present disclosure.

[0147] Example Operations of Network Entities

[0148] Fig.14 Example operations 1400 for wireless communication are illustrated. For example, operations 1400 may be performed by a network entity (e.g., Figure 1 Operation 1400 may be implemented as a processor (e.g., Figure 3 In addition, the signal transmission and reception performed by the network entity in operation 1400 may be performed by one or more antennas (e.g., Figure 3 In some aspects, the transmission and / or reception of signals by the network entity may be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (eg, controller / processor 340).

[0149] Operations 1400 begin at 1402 by configuring a user equipment (UE) with a beam monitoring configuration that indicates at least one condition to be satisfied for transmission of a beam condition report in monitoring of a beam failure detection (BFD) reference signal (RS) during an on duration of a discontinuous reception (DRX) cycle. For example, a network entity may use Figure 1 or Figure 3 The antenna and / or transmitter / transceiver components of the BS 102 shown, and / or Fig.16 The antenna and / or transmitter / transceiver components of the apparatus are shown configured to configure a user equipment (UE) using a beam monitoring configuration.

[0150] At 1404, when the at least one condition is satisfied during the on-duration of the DRX cycle, the network entity receives a beam condition report at the end of the on-duration of the DRX cycle. For example, the network entity may use Figure 1 or Figure 3 The antenna and / or receiver / transceiver components of BS 102 and / or Fig.16An antenna and / or a receiver / transceiver component of the apparatus is shown to receive beam condition reports.

[0151] It should be noted that Fig.14 This is merely one example of a method, and other methods including fewer, additional, or alternative steps may also be consistent with the present disclosure.

[0152] Example Communication Device

[0153] Fig.15 Depicted are aspects of an example communications device 1500. In some examples, the communications device 1500 is a UE, such as described above with respect to Figure 1 and Figure 3 UE 104 is described.

[0154] The communication device 1500 includes a processing system 1502 coupled to a transceiver 1508 (e.g., a transmitter and / or a receiver). The transceiver 1508 is configured to transmit and receive signals for the communication device 1500, such as the various signals described herein, via an antenna 1510. The processing system 1502 may be configured to perform processing functions for the communication device 1500, including processing signals received by the communication device 1500 and / or signals to be transmitted by the communication device.

[0155] The processing system 1502 includes one or more processors 1520. In various aspects, the one or more processors 1520 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380, as shown in FIG. Figure 3 The one or more processors 1520 are coupled to the computer readable medium / memory 1530 via the bus 1506. In some aspects, the computer readable medium / memory 1530 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 1520, cause the one or more processors 1520 to perform operations related to Fig.13 The described operations 1300 or any aspects related thereto. It should be noted that reference to a processor performing a function of the communication device 1500 may include one or more processors performing that function of the communication device 1500.

[0156] In the depicted example, the computer-readable medium / memory 1530 stores the following codes (e.g., executable instructions): code 1531 for receiving, including code for receiving a beam monitoring configuration, the beam monitoring configuration indicating at least one condition to be satisfied for the transmission of a beam condition report; code 1532 for monitoring, including code for monitoring at least one BFD-RS during the on duration of the DRX cycle; and code 1533 for transmitting, including code for transmitting the beam condition report at the end of the on duration of the DRX cycle when the at least one condition is satisfied during the on duration of the DRX cycle. Processing of codes 1531-1535 may cause the communication device 1500 to perform operations relative to Fig.13 Operation 1300 or any aspect related thereto may be described.

[0157] The one or more processors 1520 include circuits configured to implement (e.g., execute) code stored in a computer-readable medium / memory 1530, the circuits including: a circuit 1521 for receiving, including a circuit for receiving a beam monitoring configuration, the beam monitoring configuration indicating at least one condition to be satisfied for the transmission of a beam condition report; a circuit 1522 for monitoring, including a circuit for monitoring at least one BFD-RS during the on-duration of the DRX cycle; and a circuit 1523 for transmitting, including a circuit for transmitting the beam condition report at the end of the on-duration of the DRX cycle when the at least one condition is satisfied during the on-duration of the DRX cycle. Processing using circuits 1521-1523 may cause the communication device 1500 to perform operations relative to Fig.13 The described operations 1300 or any aspect related thereto.

[0158] The various components of the communication device 1500 may be provided for performing Fig.13 The described means for operation 1300 or any aspect related thereto. For example, means for sending, transmitting, or outputting for sending may include Figure 3 The transceiver 354 and / or antenna 352 of the UE 104 illustrated in FIG. 1 , and / or Fig.15 The transceiver 1508 and antenna 1510 of the communication device 1500 in FIG. 1 may include Figure 3 The transceiver 354 and / or antenna 352 of the UE 104 illustrated in FIG. 1 , and / or Fig.15 The transceiver 1508 and antenna 1510 of the communication device 1500 in FIG.

[0159] Fig.16 Depicted are aspects of an example communications device 1600. In some aspects, the communications device 1600 is a network entity, such as described above with respect to Figure 1 and Figure 3BS102 as described.

[0160] The communication device 1600 includes a processing system 1602 coupled to a transceiver 1608 (e.g., a transmitter and / or a receiver) and / or a network interface. The transceiver 1608 is configured to transmit and receive signals for the communication device 1600, such as the various signals described herein, via an antenna 1610. The network interface 1612 is configured to communicate with the communication device 1600 via a communication link (such as described herein). Figure 2 The processing system 1602 may be configured to obtain and transmit signals for the communication device 1600 using the backhaul link, midhaul link, and / or fronthaul link described herein. The processing system 1602 may be configured to perform processing functions of the communication device 1600, including processing signals received by the communication device 1600 and / or signals to be sent by the communication device.

[0161] The processing system 1602 includes one or more processors 1620. In various aspects, the one or more processors 1620 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340, as described with respect to FIG. Figure 3 The one or more processors 1620 are coupled to the computer readable medium / memory 1630 via the bus 1606. In some aspects, the computer readable medium / memory 1630 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 1620, cause the one or more processors 1620 to perform operations related to Fig.14 The described operations 1400 or any aspects related thereto. It should be noted that reference to a processor of the communication device 1600 performing a function may include one or more processors of the communication device 1600 performing the function.

[0162] In the depicted example, the computer-readable medium / memory 1630 stores the following codes (e.g., executable instructions): code 1631 for configuring, including code for configuring the UE with a beam monitoring configuration, the beam monitoring configuration indicating at least one condition to be satisfied in monitoring of the BFD-RS for transmission of a beam condition report during an on duration of a DRX cycle; and code 1632 for receiving, including code for receiving the beam condition report at the end of the on duration of the DRX cycle when the at least one condition is satisfied during the on duration of the DRX cycle. Processing of the codes 1631-1632 may cause the communication device 1600 to perform operations relative to Fig.14 The described operations 1400 or any aspects related thereto.

[0163] One or more processors 1620 include circuits configured to implement (e.g., execute) code stored in a computer-readable medium / memory 1630, the circuits comprising: circuitry 1621 for configuring, comprising circuitry for configuring the UE with a beam monitoring configuration, the beam monitoring configuration indicating at least one condition to be satisfied in monitoring of the BFD-RS for sending a beam condition report during an on-duration of a DRX cycle; and circuitry 1622 for receiving, comprising circuitry for receiving a beam condition report at the end of the on-duration of the DRX cycle when the at least one condition is satisfied during the on-duration of the DRX cycle.

[0164] Processing by circuits 1621-1622 may enable communications device 1600 to perform operations relative to Fig.14 The described operations 1400 or any aspects related thereto.

[0165] The various components of the communication device 1600 may be provided for performing Fig.14 The described means for operation 1400 or any aspect related thereto. The means for sending, transmitting, or outputting for sending may include Figure 3 The transceiver 332 and / or antenna 334 of the BS 102 illustrated in FIG. Fig.16 The transceiver 1608 and antenna 1610 of the communication device 1600 in FIG. 1 may include Figure 3 The transceiver 332 and / or antenna 334 of the BS 102 illustrated in FIG. Fig.16 The transceiver 1608 and antenna 1610 of the communication device 1600 in FIG.

[0166] Sample Clauses

[0167] Specific implementation examples are described in the following numbered clauses:

[0168] Clause 1: A method for wireless communication by a user equipment (UE), the method comprising: receiving a beam monitoring configuration, the beam monitoring configuration indicating at least one condition to be satisfied for sending a beam condition report; monitoring at least one beam failure detection (BFD) reference signal (RS) during an on duration of a discontinuous reception (DRX) cycle; and when the at least one condition is satisfied during the on duration of the DRX cycle, sending the beam condition report at the end of the on duration of the DRX cycle.

[0169] Clause 2: The method, alone or in combination with the first clause, wherein the at least one condition is satisfied when the value of the signal to interference and noise ratio (SINR) of the at least one BFD-RS during the on duration of the DRX cycle decreases by a predetermined value compared to a previous SINR value.

[0170] Clause 3: The method, alone or in combination with the first clause, wherein: the beam monitoring configuration also indicates a beam monitoring set; the beam monitoring set indicates a group of different beams; and at least one of the conditions is met when the UE determines a new beam that is not included in the beam monitoring set during the on-time of the DRX cycle.

[0171] Clause 4: The method, alone or in combination with the first clause, wherein the at least one condition is met when the UE predicts a beam failure during the on duration of the DRX cycle based on one or more signal measurements associated with the at least one BFD-RS.

[0172] Clause 5: The method, alone or in combination with the first clause, wherein: the beam condition report indicates information, the information identifying one or more factors used for the transmission of the beam condition report, and the information indicates at least one of the following: a predicted beam failure based on one or more signal measurements associated with the at least one BFD-RS, or a drop in channel strength exceeding a threshold during a predetermined time period.

[0173] Clause 6: The method, alone or in combination with the first clause, wherein: the beam condition report indicates the status of the BFD based on determining an indication of a beam failure instance (BFI) at each opportunity of the at least one BFD-RS during the monitoring of the at least one BFD-RS in the on duration of the DRX cycle, and the status indicates at least one of the following: the current number of total BFI counts or the BFI record history.

[0174] Clause 7: The method, alone or in combination with the first clause, wherein: the beam condition report indicates a channel measurement report associated with a channel between the UE and a network entity, and the channel measurement report indicates at least one of the following: signal to interference and noise ratio (SINR), signal to noise ratio (SNR), reference signal received power (RSRP) or path loss.

[0175] Clause 8: The method, alone or in combination with the first clause, wherein: the beam condition report indicates a preferred response from a network entity, and the preferred response indicates at least one of: a first request to switch from one beam to another beam, a second request for additional BFD-RS resources to monitor the new beam for BFD, or a third request to change a subset of beams within a beam monitoring set indicating a different set of beams.

[0176] Clause 9: The method, alone or in combination with the first clause, wherein the sending further comprises: sending the beam condition report using different techniques selected based on a size of the beam condition report.

[0177] Clause 10: The method alone or in combination with Clause 9, wherein the sending further comprises: when the size of the beam condition report is smaller than a predetermined size, using uplink control information (UCI) to send the beam condition report, or when the size of the beam condition report is larger than the predetermined size, using a medium access control (MAC) control element (CE) to send the beam condition report.

[0178] Clause 11: The method, alone or in combination with the first clause, further comprising: monitoring a response to the beam condition report from a network entity during a second predetermined time period after the first predetermined time period.

[0179] Clause 12: The method, alone or in combination with clause 11, further comprising: initiating a retransmission of the beam condition report when no response is received during the second predetermined time period.

[0180] Clause 13: The method as claimed in claim 12, alone or in combination with claim 12, wherein: the initiating comprises initiating retransmission of the beam condition report to a maximum of a predetermined number of times, and each retransmission of the beam condition report is separated by a third predetermined time period.

[0181] Clause 14: The method as claimed in claim 12, alone or in combination with claim 12, wherein: the initiating comprises initiating retransmission of the beam condition report to a maximum of a predetermined number of times, and each retransmission of the beam condition report is separated by a different time period.

[0182] Clause 15: A method for wireless communications by a network entity, the method comprising: configuring a user equipment (UE) with a beam monitoring configuration, the beam monitoring configuration indicating at least one condition to be satisfied in monitoring a beam failure detection (BFD) reference signal (RS) for sending a beam condition report during an on duration of a discontinuous reception (DRX) cycle; and receiving the beam condition report at the end of the on duration of the DRX cycle when the at least one condition is satisfied during the on duration of the DRX cycle.

[0183] Clause 16: The method, alone or in combination with clause 15, further comprising: configuring the UE with a new beam monitoring configuration, the new beam monitoring configuration indicating at least one new condition to be satisfied for the sending of the beam condition report.

[0184] Clause 17: The method, alone or in combination with clause 15, further comprising: configuring the UE with a beam condition reporting configuration indicating one or more types of beam condition reporting.

[0185] Clause 18: The method, alone or in combination with clause 17, further comprising: configuring the UE with a new beam condition reporting configuration indicating one or more new types of beam condition reports.

[0186] Clause 19: The method, alone or in combination with clause 15, further comprising: configuring the UE to send the beam condition report using different transmission options.

[0187] Clause 20: The method as claimed in clause 19, alone or in combination with clause 19, wherein the different transmission options are associated with different sizes of the beam condition reports.

[0188] Clause 21: The method, alone or in combination with clause 15, further comprising: configuring the UE with a beam condition report retransmission configuration indicating a retransmission process of the beam condition report.

[0189] Clause 22: The method, alone or in combination with clause 21, wherein the retransmission process of the beam condition report is based on at least one of: Quality of Service (QoS) requirements of the service traffic, delay estimation, or path loss estimation.

[0190] Clause 23: An apparatus, the apparatus comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the method according to any one of clauses 1 to 22.

[0191] Clause 24: An apparatus comprising means for performing the method according to any one of clauses 1 to 22.

[0192] Clause 25: A non-transitory computer readable medium comprising executable instructions which, when executed by a processor of an apparatus, cause the apparatus to perform the method of any one of clauses 1 to 22.

[0193] Clause 26: A computer program product embodied on a computer readable storage medium, the computer program product comprising code for performing the method according to any one of clauses 1 to 22.

[0194] Additional considerations

[0195] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Each example may ignore, replace or add various procedures or components as appropriate. For example, the described method may be performed in a different order than the described order, and various actions may be added, omitted or combined. In addition, the features described for some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functions, or structures and functions that are supplementary or alternative to the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0196] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0197] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items (including single members). As an example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0198] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Additionally, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0199] The method disclosed herein includes one or more actions for implementing the method. The method actions can be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions can be modified without departing from the scope of the claims. In addition, the various operations of the method described above can be performed by any appropriate component that can perform the corresponding function. The component may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors.

[0200] The following claims are not intended to be limited to the various aspects shown herein, but should be granted the full scope consistent with the language of the claims. Within the claims, unless otherwise specified, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. Any claim element is not interpreted according to the provisions of 35 U.S.C. § 112 (f) unless the element is explicitly stated using the phrase "member for...". All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, regardless of whether such disclosure is explicitly stated in the claims, anything disclosed herein is not intended to be disclosed to the public.

Claims

1. A user equipment (UE) configured for wireless communication, the user equipment (UE) comprising: a memory including computer executable instructions; and a processor configured to execute the computer executable instructions and cause the UE to: receiving a beam monitoring configuration indicating at least one condition to be satisfied for transmission of a beam condition report; monitoring at least one beam failure detection (BFD) reference signal (RS) during an on duration of a discontinuous reception (DRX) cycle; as well as When the at least one condition is met during the on-duration of the DRX cycle, the beam condition report is sent at the end of the on-duration of the DRX cycle.

2. The UE of claim 1, wherein the at least one condition is satisfied when a value of a signal to interference and noise ratio (SINR) of the at least one BFD-RS during the on duration of the DRX cycle decreases by a predetermined value compared to a previous SINR value.

3. The UE according to claim 1, wherein: The beam monitoring configuration further indicates a beam monitoring set; The beam monitoring set indicates a group of different beams; and The at least one condition is met when the UE determines a new beam that is not included in the beam monitoring set during the on duration of the DRX cycle.

4. The UE of claim 1 , wherein the at least one condition is met when the UE predicts a beam failure during the on-duration of the DRX cycle based on one or more signal measurements associated with the at least one BFD-RS.

5. The UE according to claim 1, wherein: the beam condition report indicating information identifying one or more factors for the sending of the beam condition report, and The information indicates at least one of: a predicted beam failure based on one or more signal measurements associated with the at least one BFD-RS, or a drop in channel strength exceeding a threshold during a predetermined time period.

6. The UE according to claim 1, wherein: The beam condition report indicates a status of the BFD based on determining an indication of a beam failure instance (BFI) at each opportunity of the at least one BFD-RS during the monitoring of the at least one BFD-RS in the on duration of the DRX cycle, and the status indicates at least one of: a current number of total BFI counts or a BFI record history.

7. The UE according to claim 1, wherein: The beam condition report indicates a channel measurement report associated with a channel between the UE and a network entity, and The channel measurement report indicates at least one of: a signal to interference and noise ratio (SINR), a signal to noise ratio (SNR), a reference signal received power (RSRP), or a path loss.

8. The UE according to claim 1, wherein: The beam condition report indicates a preferred response from a network entity, and The preferred response indicates at least one of: a first request to switch from one beam to another, a second request for additional BFD-RS resources to monitor the new beam for BFD, or a third request to change a subset of beams within a beam monitoring set indicating a different set of beams.

9. The UE according to claim 1, wherein the sending further comprises: The beam condition report is sent using different techniques selected based on a size of the beam condition report.

10. The UE according to claim 9, wherein the sending further comprises: When the size of the beam condition report is smaller than a predetermined size, uplink control information (UCI) is used to send the beam condition report, or when the size of the beam condition report is larger than the predetermined size, a medium access control (MAC) control element (CE) is used to send the beam condition report.

11. The UE of claim 1 , wherein the processor is further configured to execute the computer executable instructions and cause the UE to: monitor a response to the beam condition report from a network entity during a second predetermined time period after the first predetermined time period.

12. The UE of claim 11, wherein the processor is further configured to execute the computer executable instructions and cause the UE to: initiate a retransmission of the beam condition report when no response is received during the second predetermined time period.

13. The UE according to claim 12, wherein: The initiating comprises initiating the retransmission of the beam condition report to a maximum of a predetermined number of times, and Each retransmission of the beam condition report is separated by a third predetermined time period.

14. The UE according to claim 12, wherein: The initiating comprises initiating the retransmission of the beam condition report to a maximum of a predetermined number of times, and Each retransmission of the beam condition report is separated by a different time period.

15. A network entity configured for wireless communication, the network entity comprising: a memory including computer executable instructions; and a processor configured to execute the computer executable instructions and cause the network entity to: configuring a user equipment (UE) with a beam monitoring configuration indicating at least one condition to be satisfied for transmission of a beam condition report in monitoring of a beam failure detection (BFD) reference signal (RS) during an on duration of a discontinuous reception (DRX) cycle; as well as When the at least one condition is met during the on-duration of the DRX cycle, the beam condition report is received at the end of the on-duration of the DRX cycle.

16. A network entity according to claim 15, wherein the processor is further configured to execute the computer-executable instructions and cause the network entity to: configure the UE with a new beam monitoring configuration, wherein the new beam monitoring configuration indicates at least one new condition to be met for the sending of the beam condition report.

17. The network entity of claim 15, wherein the processor is further configured to execute the computer-executable instructions and cause the network entity to: configure the UE with a beam condition reporting configuration indicating one or more types of the beam condition report.

18. The network entity of claim 17, wherein the processor is further configured to execute the computer executable instructions and cause the network entity to: configure the UE with a new beam condition reporting configuration indicating one or more new types of the beam condition reporting.

19. The network entity of claim 17, wherein the processor is further configured to execute the computer executable instructions and cause the network entity to: configure the UE to send the beam condition report using different transmission options.

20. The network entity of claim 19, wherein the different transmission options are associated with different sizes of the beam condition reports.

21. The network entity of claim 15, wherein the processor is further configured to execute the computer executable instructions and cause the network entity to: configure the UE with a beam condition report retransmission configuration indicating a retransmission process of the beam condition report.

22. The network entity of claim 21, wherein the retransmission process of the beam condition report is based on at least one of: a quality of service (QoS) requirement of a serving traffic, a delay estimation, or a path loss estimation.

23. A method for wireless communication by a user equipment (UE), the method comprising: receiving a beam monitoring configuration indicating at least one condition to be satisfied for transmission of a beam condition report; monitoring at least one beam failure detection (BFD) reference signal (RS) during an on duration of a discontinuous reception (DRX) cycle; as well as When the at least one condition is met during the on-duration of the DRX cycle, the beam condition report is sent at the end of the on-duration of the DRX cycle.

24. The method of claim 23, wherein the at least one condition is satisfied when a value of a signal to interference and noise ratio (SINR) of the at least one BFD-RS during the on duration of the DRX cycle decreases by a predetermined value compared to a previous SINR value.

25. The method of claim 23, wherein the at least one condition is met when the UE predicts a beam failure during the on-duration of the DRX cycle based on one or more signal measurements associated with the at least one BFD-RS.

26. The method of claim 23, wherein: The beam monitoring configuration further indicates a beam monitoring set; The beam monitoring set indicates a group of different beams; and The at least one condition is met when the UE determines a new beam that is not included in the beam monitoring set during the on duration of the DRX cycle.

27. A method for wireless communication by a network entity, the method comprising: configuring a user equipment (UE) with a beam monitoring configuration indicating at least one condition to be satisfied for transmission of a beam condition report in monitoring of a beam failure detection (BFD) reference signal (RS) during an on duration of a discontinuous reception (DRX) cycle; as well as When the at least one condition is met during the on-duration of the DRX cycle, the beam condition report is received at the end of the on-duration of the DRX cycle.

28. The method according to claim 27, further comprising: The UE is configured with a new beam monitoring configuration indicating at least one new condition to be satisfied for the sending of the beam condition report.

29. The method according to claim 28, further comprising: The UE is configured with a beam condition reporting configuration indicating one or more types of the beam condition reporting.

30. The method of claim 27, further comprising: The UE is configured to send the beam condition report using different transmission options.

Images