Smart window determination for beam scanning on physical downlink shared channel demodulation reference signals

By performing beam scanning on PDSCH DMRS and determining the beam management window using downlink service parameters, the UE can optimize the rank 2 performance, solving the problem of low beam management efficiency under high frequency bands in the prior art, and improving channel stability performance and performance.

CN118923056APending Publication Date: 2024-11-08QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380029398.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-31
Filing Date
2023-03-06
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

The existing wireless communication technology is difficult to optimize the rank 2 performance in the millimeter wave band with high frequency, especially the FR2 band, resulting in low beam management efficiency and inability to fully utilize the potential performance of multiple transmit and receive ports.

Method used

User equipment (UE) performs beam scanning on the physical downlink shared channel (PDSCH) demodulation reference signal (DMRS), uses downlink service parameters to determine beam management windows, selecting optimized beams to improve rank 2 performance.

Benefits of technology

Through beam scanning and service parameter optimization, the UE can select the best beam in an efficient beam management window, improve the channel estimation and reception performance of the downlink, optimize the rank 2 performance, avoid frequent beam switching, and enhance channel stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923056A_ABST
    Figure CN118923056A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may identify a beam management window based at least in part on one or more downlink traffic parameters satisfying a window opening condition. The UE may perform a beam scan on a set of beams associated with one or more physical downlink shared channel (PDSCH) demodulation reference signal (DMRS) transmissions received during the beam management window. The UE may select a beam for communication with the network node among the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each respective beam included in the set of beams. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 17 / 657,574, filed on March 31, 2022, entitled "SMART WINDOW DETERMINATION FOR BEAMSWEEP ON PHYSICAL DOWNLINK SHARED CHANNEL DEMODULATION REFERENCE SIGNAL," which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for smart window determination for beam scanning on a physical downlink shared channel (PDSCH) demodulation reference signal (DMRS). Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include: identifying a beam management window based at least in part on one or more downlink traffic parameters satisfying a window opening condition. The method may include: performing beam scanning on a set of beams associated with one or more physical downlink shared channel (PDSCH) demodulation reference signal (DMRS) transmissions received during the beam management window. The method may include: selecting a beam for communicating with a network node from the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each respective beam included in the set of beams.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to identify a beam management window based at least in part on one or more downlink service parameters satisfying a window opening condition. The one or more processors may be configured to perform beam scanning on a group of beams associated with one or more PDSCH DMRS transmissions received during the beam management window. The one or more processors may be configured to select a beam for communicating with a network node from the group of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each corresponding beam included in the group of beams.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication performed by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to: identify a beam management window based at least in part on one or more downlink service parameters satisfying a window opening condition. The instruction set, when executed by one or more processors of the UE, may cause the UE to: perform beam scanning on a set of beams associated with one or more PDSCH DMRS transmissions received during the beam management window. The instruction set, when executed by one or more processors of the UE, may cause the UE to: select a beam for communicating with a network node from the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each corresponding beam included in the set of beams.

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for identifying a beam management window based at least in part on one or more downlink traffic parameters satisfying a window opening condition. The apparatus may include a component for performing beam scanning on a set of beams associated with one or more PDSCH DMRS transmissions received during the beam management window. The apparatus may include a component for selecting a beam for communicating with a network node from the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each respective beam included in the set of beams.

[0011] Aspects of the present invention generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and descriptions and as illustrated in the accompanying drawings and descriptions.

[0012] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0013] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to fully understand the above features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same figure numbers in different drawings may identify the same or similar elements.

[0015] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0016] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment in a wireless network according to the present disclosure.

[0017] Figure 3 is a diagram illustrating an example of physical channels and reference signals in a wireless network according to the present disclosure.

[0018] Figure 4 is a diagram illustrating an example of a beam management procedure according to the present disclosure.

[0019] Figure 5 is a diagram illustrating an example associated with smart window determination for beam scanning on a physical downlink shared channel (PDSCH) demodulation reference signal (DMRS) according to the present disclosure.

[0020] Figure 6 is a diagram illustrating an example process associated with smart window determination for beam scanning on PDSCH DMRS according to the present disclosure.

[0021] Figure 7 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0022] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. 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 that are practiced using other structures, functions, or structures and functions other than the various aspects of the present disclosure set forth herein or different from 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.

[0023] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0024] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0025] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0026] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0027] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 can be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0028] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in FIG. 1 , BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, or the like.

[0029] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0030] A network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0031] UE 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0032] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as user premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0033] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0034] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using base station 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0035] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as a "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as a "millimeter wave" band in various documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as a "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0037] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0038] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: identify a beam management window based at least in part on one or more downlink traffic parameters satisfying a window open condition; perform beam scanning on a set of beams associated with one or more physical downlink shared channel (PDSCH) demodulation reference signal (DMRS) transmissions received during the beam management window; and select a beam for communicating with a network node from among the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each respective beam included in the set of beams. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0039] In some aspects, the term "base station" (e.g., base station 110), "network node" or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station", "network node" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station", "network node" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station", "network node" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographical location or in different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station", "network node" or "network entity" may refer to any one or more of these different devices. In some aspects, the terms "base station", "network node" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the terms "base station", "network node" or "network entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0040] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station (BS), a 5G NB, a gNodeB (gNB), an access point (AP), a TRP or a cell) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as a stand-alone base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

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

[0042] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN) (such as a network configuration initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0043] As indicated above, Figure 1 Other examples can be found in the Figure 1 Different than described.

[0044] Figure 2 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0045] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or DMRS) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0046] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0047] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0048] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0049] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 5 to 7 ) or any aspect of any of the methods described herein.

[0050] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 5 to 7 ) or any aspect of any of the methods described herein.

[0051] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component of the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or the like may perform one or more techniques associated with smart window determination for beam scanning on the PDSCH DMRS, as described in more detail elsewhere herein. Figure 2 Any other component of the Figure 6 600 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example, Figure 6 The process 600 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0052] In some aspects, the UE 120 includes: means for identifying a beam management window based at least in part on one or more downlink traffic parameters satisfying a window open condition; means for performing beam scanning on a set of beams associated with one or more PDSCH DMRS transmissions received during the beam management window; and / or means for selecting a beam for communicating with a network node from the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each respective beam included in the set of beams. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0053] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0054] As indicated above, Figure 2 Other examples can be found in the Figure 2 Different than described.

[0055] Figure 3 3 is a diagram illustrating an example 300 of physical channels and reference signals in a wireless network according to the present disclosure. Figure 3 As shown in , the downlink channel and the downlink reference signal may carry information from base station 110 to UE 120, and the uplink channel and the uplink reference signal may carry information from UE 120 to base station 110.

[0056] As shown, the downlink channel may include a physical downlink control channel (PDCCH) carrying downlink control information (DCI), a PDSCH carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, etc. In some aspects, PDSCH communication may be scheduled by PDCCH communication. As further shown, the uplink channel may include a physical uplink control channel (PUCCH) carrying uplink control information (UCI), a physical uplink shared channel (PUSCH) carrying uplink data, or a physical random access channel (PRACH) for initial network access, etc. In some aspects, UE 120 may send an acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH.

[0057] As further shown, the downlink reference signal may include a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a DMRS and / or a phase tracking reference signal (PTRS), among other examples. As also shown, the uplink reference signal may include a sounding reference signal (SRS), a DMRS, or a PTRS, among others.

[0058] The SSB may carry information used for initial network acquisition and synchronization, such as a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH, and a PBCH DMRS. The SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, the base station 110 may send multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection or beam management.

[0059] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, among other things. The base station 110 may configure a CSI-RS set for the UE 120, and the UE 120 may measure the configured CSI-RS set. Based at least in part on the measurements, the UE 120 may perform channel estimation and may report channel estimation parameters such as CQI, precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), layer indicator (LI), rank indicator (RI), or RSRP, among other things, to the base station 110 (e.g., in a CSI report). The base station 110 may use the CSI report to select transmission parameters for downlink communication to the UE 120, such as the number of transmission layers (e.g., rank), precoding matrix (e.g., precoder), MCS, or a refined downlink beam (e.g., using a beam refinement procedure or a beam management procedure), among other examples.

[0060] DMRS may carry information for estimating a radio channel to demodulate an associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of DMRS may be specific to the physical channel for which the DMRS is used for channel estimation. DMRS is UE-specific, may be beamformed, may be restricted to scheduled resources (e.g., rather than being sent over a wideband), and may be sent only when necessary. As shown, DMRS is used for both downlink and uplink communications.

[0061] PTRS can carry information for compensating for oscillator phase noise. Typically, phase noise increases with the increase of the oscillator carrier frequency. Therefore, PTRS can be used at high carrier frequencies (such as millimeter wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and to achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communications (e.g., on PDSCH) and uplink communications (e.g., on PUSCH).

[0062] The SRS may carry information for uplink channel estimation, which may be used for scheduling, link adaptation, pre-decoder selection, or beam management, etc. The base station 110 may configure one or more SRS resource sets for the UE 120, and the UE 120 may send the SRS on the configured SRS resource sets. The SRS resource sets may have configured usages, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. The base station 110 may measure the SRS, may perform channel estimation based at least in part on these measurements, and may use the SRS measurements to configure communications with the UE 120.

[0063] As indicated above, Figure 3 Other examples can be found in the Figure 3 Different than described.

[0064] Figure 4 4 is a diagram illustrating examples 400, 410, and 420 of a beam management procedure based on downlink reference signal transmission according to the present disclosure. Figure 4 As shown in , examples 400, 410, and 420 include UE 120 communicating with base station 110 in a wireless network (e.g., wireless network 100). However, Figure 4 The devices shown in are provided as examples, and the wireless network may support communication and beam management between other devices (e.g., between UE 120 and TRP, DU or RU, between mobile terminal nodes and control nodes, between IAB child nodes and IAB parent nodes, and / or between scheduled nodes and scheduling nodes). In some aspects, UE 120 and base station 110 may be in a connected state (e.g., a radio resource control (RRC) connected state) when performing beam management procedures.

[0065] like Figure 4 As shown in , example 400 may include base station 110 and UE 120 communicating to perform beam management using SSB or CSI-RS transmission. Example 400 depicts a first beam management procedure (e.g., P1 beam management). The first beam management procedure may be referred to as a beam selection procedure, an initial beam acquisition procedure, a beam scanning procedure, a cell search procedure, and / or a beam search procedure. Figure 4 As shown in example 400, during a first beam management procedure, SSBs and / or CSI-RSs may be configured to be sent from base station 110 to UE 120. For example, the SSBs sent by base station 110 are rank-1 periodic reference signals that are always sent by base station 110 to enable initial network acquisition and synchronization in addition to beam selection and beam management. For example, an identifier associated with an SSB may have a one-to-one mapping to a transmit beam used by base station 110, and the one-to-one mapping may not change over time (e.g., be static). CSI-RSs used for beam selection or beam management may be configured to be periodic (e.g., using RRC signaling), semi-persistent (e.g., using medium access control (MAC) control element (MAC-CE) signaling), and / or aperiodic (e.g., using DCI).

[0066] The first beam management procedure may include the base station 110 performing beam scanning on multiple transmit (Tx) beams. The base station 110 may use each transmit beam used for beam management to transmit an SSB or a CSI-RS. In order to enable the UE 120 to perform receive (Rx) beam scanning, the base station 110 may use the transmit beam to transmit each SSB or CSI-RS multiple times within the same reference signal resource set (e.g., using repetition) so that the UE 120 may perform beam scanning on multiple receive beams in multiple transmit instances. For example, if the base station 110 has a set of N transmit beams and the UE 120 has a set of M receive beams, the SSB or CSI-RS may be transmitted M times on each of the N transmit beams, so that the UE 120 may receive M instances of the SSB or CSI-RS per transmit beam. In other words, for each transmit beam of the base station 110, the UE 120 may perform beam scanning of the receive beams of the UE 120 one by one. Thus, the first beam management procedure may enable UE 120 to use different receive beams to measure SSB or CSI-RS on different transmit beams to support selection of one or more transmit / receive beam pairs (e.g., pairing between a transmit beam of base station 110 and a receive beam of UE 120). UE 120 may report the measurements to base station 110 to enable base station 110 to select one or more beam pairs for communication between base station 110 and UE 120.

[0067] like Figure 4 As shown in , example 410 may include base station 110 and UE 120 communicating to perform beam management using SSB or CSI-RS. Example 410 depicts a second beam management procedure (e.g., P2 beam management). The second beam management procedure may be referred to as a beam refinement procedure, a base station beam refinement procedure, a network node beam refinement procedure, and / or a transmit beam refinement procedure, among other examples. Figure 4As shown in example 410, SSBs and / or CSI-RSs may be configured to be sent from base station 110 to UE 120. SSBs may be periodic, and CSI-RSs may be configured to be non-periodic (e.g., using DCI). A second beam management procedure may include base station 110 performing beam scanning on one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with base station 110 (e.g., determined based at least in part on measurements reported by UE 120 in conjunction with the first beam management procedure). Base station 110 may transmit SSBs or CSI-RSs using each of the one or more transmit beams for beam management. UE 120 may measure each SSB or CSI-RS using a single (e.g., identical) receive beam (e.g., determined based at least in part on measurements performed in conjunction with the first beam management procedure). The second beam management procedure may enable base station 110 to select an optimal transmit beam based at least in part on measurements of SSB and / or CSI-RS reported by UE 120 (eg, measured by UE 120 using a single receive beam).

[0068] like Figure 4 As shown in , example 420 depicts a third beam management procedure (e.g., P3 beam management). The third beam management procedure may be referred to as a beam refinement procedure, a UE beam refinement procedure, a receive beam refinement procedure, and / or a UE beam management procedure, among other examples. Figure 4As shown in Example 420, one or more SSBs or CSI-RSs may be configured to be sent from base station 110 to UE 120. The SSBs may be configured to be periodic, and the CSI-RSs may be configured to be non-periodic (e.g., using DCI). The third beam management procedure may include base station 110 sending the one or more SSBs or CSI-RSs using a single transmit beam (e.g., determined at least in part based on measurements reported by UE 120 in conjunction with the first beam management procedure and / or the second beam management procedure). In order to enable UE 120 to perform receive beam scanning, the base station may use the transmit beam to send the SSB or CSI-RS multiple times in the same reference signal resource set (e.g., using repetition), so that UE 120 can scan one or more receive beams one by one in multiple transmission instances. The one or more receive beams may be a subset of all receive beams associated with UE 120 (e.g., determined at least in part based on measurements performed in conjunction with the first beam management procedure and / or the second beam management procedure). The third beam management procedure may enable UE 120 to select the best receive beam based at least in part on measurements of the SSB or CSI-RS, and / or may enable base station 110 to select the best receive beam for UE 120 based at least in part on reported measurements received from UE 120 (e.g., measurements of the SSB and / or CSI-RS using the one or more receive beams).

[0069] In general, wireless communication standards currently specify that UE beam management is performed based on SSB transmission or CSI-RS P3 transmission (e.g., in FR2 or millimeter wave bands). However, limiting UE beam management to SSB or CSI-RS P3 transmission may result in an inability to optimize rank 2 performance, where the rank value generally refers to the number of transmission streams observed at a receiver (e.g., UE 120). For example, in some cases, a transmitting antenna and / or a receiving antenna may have two ports, which may include a horizontally polarized (H) port and a vertically polarized (V) port. Therefore, when a transmitter (e.g., base station 110) independently uses both the H port and the V port to transmit a signal and / or uses a suitable precoder (e.g., a nonlinear precoder) to transmit a signal, the receiver (e.g., UE 120) may simultaneously observe two streams of the transmitted signal, which may be referred to as rank 2 communication. Alternatively, when the transmitter uses a linear precoder (e.g., an H+V precoder or an HV precoder) or uses only one port (e.g., only the H port or only the V port) to send a signal, the receiver may observe only one stream of the transmitted signal, which may be referred to as rank 1 communication.

[0070] Although rank 2 communications can provide improved downlink performance, current UE beam management techniques cannot fully optimize rank 2 performance. Specifically, as described above, current wireless communication standards specify that UE beam management in FR2 or millimeter wave bands is based on SSB transmission or CSI-RS P3 transmission, where SSB is a rank 1 periodic reference signal guaranteed to be transmitted in all 5G NR networks, and CSI-RS P3 is an optional downlink reference signal (e.g., for beam management) that can be configured in different ways across different 5G NR networks. However, to some extent, CSI-RS P3 can be configured as a rank 1 signal or a rank 2 signal, but there are currently no 5G NR networks deployed with CSI-RS P3, nor have any infrastructure providers or wireless network providers indicated any plans to deploy CSI-RS P3. Therefore, according to current wireless communication standards, UE beam management must be performed based on SSB transmission, which significantly limits the metrics that can be optimized when performing UE beam selection due to the rank 1 nature of SSB transmission (e.g., SSB cannot be mathematically used to optimize rank 2 performance because SSB is always a rank 1 signal).

[0071] Thus, in some aspects, UE 120 may perform beam scanning on the PDSCH DMRS to improve UE beam selection in a manner that may optimize rank 2 performance. For example, to optimize rank 2 performance, UE 120 may need to perform beam scanning on reference signals associated with rank 2 signaling (such that certain reference signals, such as SSBs or tracking reference signals (TRSs) that are always configured as rank 1 signals) . In addition, as described above, although CSI-RS P3 may be configured as a rank 1 signal or a rank 2 signal, CSI-RS P3 is not suitable for optimizing rank 2 performance because there is currently no infrastructure or plan to configure or otherwise deploy CSI-RS P3 in 5G NR networks. In addition, although the CSI-RS associated with the resources for obtaining channel state feedback (sometimes referred to as CSI-RS ACQ or CSI-RS CSF) may be configured as a rank 2 signal, the CSI-RS ACQ or CSI-RS CSF is typically configured aperiodically with the same time slot scheduling (e.g., where the k0 parameter defining the time slot offset between the PDCCH and the aperiodic CSI-RS ACQ or CSI-RS CSF scheduled by the PDCCH has a value of zero). Therefore, it may be difficult for the UE 120 to predict the time slot in which the CSI-RS ACQ or CSI-RS CSF is sent. Therefore, in some aspects described herein, the UE 120 may perform beam scanning on the PDSCH DMRS to optimize rank 2 performance, because the PDSCH DMRS may be configured as a rank 2 signal and is guaranteed to be sent with the PDSCH according to the wireless communication standard. Furthermore, although PDSCH DMRS may be associated with the same timeslot scheduling (eg, k0=0), the timeslot in which PDSCH DMRS will be sent may be easier to predict and capture in downlink heavy scenarios (eg, because PDSCH DMRS transmission is downlink traffic driven).

[0072] Therefore, some aspects described herein relate to techniques for determining when to open and when to close a beam management window in which a UE 120 performs beam scanning on a PDSCH DMRS. Figures 5 to 7 As further described in detail, UE 120 can identify a beam management window in which to perform beam scanning on the PDSCH DMRS based on one or more downlink traffic parameters satisfying a window opening condition (e.g., indicating an upcoming downlink heavy time period), and UE 120 can determine when to terminate beam scanning to avoid degrading PDSCH performance (e.g., by limiting the number of PDSCH time slots using weak or suboptimal PDSCH beams, which may affect downlink channel estimation and / or increase the downlink block error rate (BLER)).

[0073] As indicated above, Figure 4 As an example of a beam management procedure. Other examples of beam management procedures can be found in Figure 4 For example, UE 120 and base station 110 may perform the third beam management procedure before performing the second beam management procedure, and / or UE 120 and base station 110 may perform a similar beam management procedure to select a UE transmit beam.

[0074] Figure 5 is a diagram illustrating an example 500 associated with smart window determination for beam scanning on a PDSCH DMRS. Figure 5 As shown in , example 500 includes a UE communicating with a network node (e.g., a base station, a TRP, a DU, a RU, etc.) in a wireless network. In some aspects, the UE and the network node may communicate via a wireless access link using beamforming, which may include an uplink and a downlink.

[0075] As shown in the figure numeral 510, the UE and the network node may be in a connected state (e.g., an RRC connected state). For example, when in a connected state, the UE may receive downlink data from the network node in one or more PDSCH transmissions, and may send uplink data to the network node in one or more PUSCH transmissions. In some aspects, as described herein, the UE may be configured to optimize rank 2 performance (e.g., in the case of receiving downlink signals via two spatial streams) by performing beam scanning on a PDSCH DMRS, which may be configured as a rank 1 signal or a rank 2 signal that is always transmitted together with a PDSCH carrying one or more transport blocks (e.g., to achieve downlink channel estimation and thereby improve PDSCH reception performance). In some aspects, a signal may be sent to the UE to notify the mapping between the PDSCH DMRS and the transmit beam used by the network node, and the UE may generally expect the PDSCH DMRS beam to match the serving beam used by the network node. However, because the PDSCH DMRS transmission occurs together with the PDSCH to achieve downlink channel estimation, the PDSCH DMRS transmission is driven by downlink traffic. Thus, in some aspects, the UE may monitor one or more downlink traffic parameters while in a connected state to predict or otherwise determine a beam management window (e.g., a time period during which beam scanning is performed to select or refine a receive beam) that may have a large amount of downlink traffic.

[0076] For example, while in a connected state, the network node may send a downlink grant to the UE to schedule a PDSCH transmission, and may send an uplink grant to the UE to schedule a PUSCH transmission. Thus, in the case where the downlink grant includes a timing offset (e.g., a k0 parameter) having a value greater than or equal to one, the UE may accurately determine the exact time slot that will include the PDSCH DMRS transmission, where the timing offset refers to the number of time slots between the time slot in which the downlink grant is sent and the time slot in which the scheduled PDSCH transmission will occur. However, the network node may support same-slot scheduling (e.g., where k0=0, meaning that the PDSCH transmission occurs in the same time slot as the scheduled downlink grant), which may prevent the UE from accurately opening a beam management window to capture the PDSCH DMRS transmission with absolute certainty. In some aspects, the UE may therefore use downlink traffic parameters and / or other suitable information to determine when to open a beam management window in which beam scanning is performed for PDSCH DMRS transmissions.

[0077] As further shown in reference numeral 520, the UE may determine that the window opening condition is satisfied based on the downlink traffic parameters. For example, as described herein, the UE may identify a beam management window (e.g., a time period having a length in time slots) in which beam scanning of the PDSCH DMRS is performed when the window opening condition is satisfied, wherein the beam management window may be opened (e.g., started) in a time slot identified by the UE based on the monitored downlink traffic parameters. For example, in some aspects, the downlink traffic parameters may be based on the amount of downlink traffic served and / or downlink traffic requirements associated with one or more applications running on the UE. Therefore, the UE may identify (e.g., open) a beam management window in which beam scanning of PDSCH DMRS transmissions is performed based on the monitored downlink traffic parameters that satisfy the window opening condition, which may generally indicate an upcoming downlink heavy scenario that may include a sufficient number of PDSCH DMRS transmissions to enable beam scanning.

[0078] For example, in some aspects, the downlink traffic parameters monitored by the UE may include a downlink duty cycle, and the UE may determine that the window opening condition is satisfied based on the downlink duty cycle having a value that satisfies (e.g., is equal to or exceeds) a threshold. For example, the downlink duty cycle may be indicated by a network node in a time division duplex (TDD) parameter (e.g., a TDD-UL-DL-Pattern parameter), which indicates the number of uplink time slots, the number of uplink symbols, the number of downlink time slots, and the number of downlink symbols within a configurable period. In this case, the UE may determine that the window opening condition is satisfied based on the downlink duty cycle having a value that satisfies the threshold, or determine that the window opening condition is not satisfied based on the downlink duty cycle having a value that does not satisfy the threshold. In this way, by opening the beam management window only when the downlink duty cycle satisfies the threshold, the UE can avoid destroying a large proportion of PDSCH time slots by using non-PDSCH beams during beam scanning on the PDSCH DMRS.

[0079] In another example, the downlink traffic parameters monitored by the UE may include the number of downlink grants, wherein the UE may determine that the window open condition is satisfied based on the number of downlink grants received in a time period having a value that satisfies (e.g., equals or exceeds) a threshold. For example, in the case where a large number of downlink grants are received, the UE may expect more downlink grants in an upcoming time period. Therefore, in some aspects, the UE may determine that the window open condition is satisfied based on the number of downlink grants collected in a recent time period having a value that satisfies the threshold, or determine that the window open condition is not satisfied based on the number of recent downlink grants having a value that does not satisfy the threshold.

[0080] In another example, the downlink traffic parameters monitored by the UE may include resource block (RB) allocations, wherein if the number of RBs allocated to the UE is close to full RB allocation, the UE may expect more time slots to be allocated for downlink communications. Thus, in some aspects, the UE may determine that the window opening condition is satisfied based on the number of allocated RBs having a value that satisfies a threshold, or determine that the window opening condition is not satisfied based on the number of allocated RBs not satisfying the threshold.

[0081] In another example, the downlink traffic parameters monitored by the UE may include the padding size in each downlink grant. For example, when the downlink grant indicates that the scheduled PDSCH transmission includes padding in addition to data, the presence of padding means that the network node does not have additional downlink traffic to transmit to the UE. Therefore, in some aspects, the UE may determine that the window opening condition is met based on the data ratio (e.g., the amount of data divided by the sum of the amount of data and the amount of padding, or data / (data+padding)) having a value that meets a threshold, or determine that the window opening condition is not met based on the data ratio not meeting the threshold (e.g., when the data ratio meets the threshold, there may be a higher probability that additional downlink data is waiting to be sent to the UE).

[0082] In another example, the downlink traffic parameters monitored by the UE may include a throughput requirement of the UE. For example, when one or more applications running on the UE have high throughput requirements, the UE may expect a larger number or a larger proportion of downlink time slots. Therefore, in some aspects, the UE may determine that the window opening condition is satisfied based on the UE throughput requirement having a value that satisfies a threshold, or determine that the window opening condition is not satisfied based on the UE throughput requirement not satisfying the threshold.

[0083] In addition, when determining whether to open the beam management window, the UE may determine whether the time elapsed since the closing time of the most recent beam management window satisfies a threshold. For example, in order to avoid destroying a large number of downlink time slots, the UE may verify whether the time elapsed since the closing time of the most recent beam management window satisfies a threshold, and if the time difference between the current time and the time when the last beam management window was closed satisfies the threshold, the beam management window may be opened.

[0084] Therefore, in the event that the UE determines that one or more of the parameters described above (e.g., all or a subset) meet the applicable threshold, the UE may open a beam management window for performing beam scanning on PDSCH DMRS transmissions occurring during the beam management window. For example, when the downlink duty cycle, the number of downlink grants, the number of allocated RBs, the padding size in each downlink grant, the UE throughput requirement, and / or the time elapsed since the most recent beam management window meet the applicable threshold, the UE may identify the starting time slot of the beam management window (e.g., the time slot in which the downlink heavy traffic period is predicted to start). In addition, in some aspects, the UE may identify the starting time slot of the beam management window in a manner that does not include other reference signals that the UE needs to monitor. For example, in some aspects, the UE may configure the beam management window to not include any time slots containing periodic reference signals (e.g., SSB and / or TRS transmissions) and / or not include any time slots containing aperiodic reference signals (e.g., CSI-RS P2 or CSI-RS P3 transmissions, if configured) with a timing offset greater than one (1) (e.g., k0>1, meaning that there is more than one time slot between the PDCCH scheduling of the aperiodic reference signal and the transmission of the aperiodic reference signal). Further, in some aspects, the UE may determine a threshold number of PDSCH time slots to be covered by the beam management window.

[0085] As further shown in reference numeral 530, the UE may perform beam scanning on PDSCH DMRS transmissions occurring during a beam management window. For example, during the beam management window, the UE may scan various receive beams one by one and obtain one or more measurements or metrics for each PDSCH DMRS transmission. For example, the one or more measurements or metrics may include a rank 2 metric, such as an RSRP measurement, a signal-to-noise ratio (SNR) measurement, or a spectral efficiency measurement, among other examples. As further shown in reference numeral 540, the UE may terminate beam scanning based on determining that a window closing condition is met. For example, as described above, the UE may determine a threshold number of PDSCH slots to be covered by a beam management window in order to limit the number of PDSCH slots that are destroyed due to the use of a potentially weak or otherwise suboptimal beam (e.g., a non-PDSCH beam, which refers to a beam other than the current PDSCH receive beam). Thus, when performing beam scanning, the UE may count the number of PDSCH slots and may terminate beam scanning when the count of the number of PDSCH slots reaches a threshold.

[0086] As further shown by reference numeral 550, the UE may then select a beam for receiving subsequent PDSCH transmissions based on measurements or metrics associated with various receive beams scanned on PDSCH DMRS transmissions during the beam management window. For example, in some aspects, the UE may select a beam associated with the best rank 2 metric among the receive beams scanned on PDSCH DMRS transmissions during the beam management window in order to optimize rank 2 performance. Additionally or alternatively, in some aspects, beam selection may be subject to a hysteresis requirement (e.g., changing the current PDSCH beam may only occur if the new PDSCH beam provides a threshold beamforming gain (such as, a two decibel (dB) power improvement) relative to the current PDSCH beam). In this way, the UE can avoid frequency PDSCH beam switches, which may provide little performance improvement. Additionally or alternatively, as indicated by reference numeral 560, the UE may report measurements or metrics associated with beams scanned on PDSCH DMRS transmissions to a network node, and the network node may indicate to the UE the PDSCH beam to be used by the UE based on the reported measurements or metrics.

[0087] As indicated above, Figure 5 Other examples can be found in the Figure 5 Different than described.

[0088] Figure 6 is a diagram illustrating an example process 600, performed, for example, by a UE, according to the present disclosure. Example process 600 is an example of operations in which a UE (eg, UE 120) performs smart window determination for beam scanning on a PDSCH DMRS.

[0089] like Figure 6 As shown in , in some aspects, process 600 may include: identifying a beam management window based at least in part on one or more downlink traffic parameters satisfying a window opening condition (block 610). Figure 7 The communication manager 140 and / or beam management component 708 depicted in FIG. 1 may identify a beam management window based at least in part on one or more downlink traffic parameters satisfying a window opening condition, as described above.

[0090] like Figure 6As further shown in FIG. 6 , in some aspects, process 600 may include performing beam scanning on a set of beams associated with one or more PDSCH DMRS transmissions received during the beam management window (block 620). For example, the UE (e.g., using communication manager 140 and / or beam management component 708) may perform beam scanning on a set of beams associated with one or more PDSCH DMRS transmissions received during the beam management window, as described above.

[0091] like Figure 6 As further shown in , in some aspects, process 600 may include: selecting a beam for communicating with a network node from among the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each respective beam included in the set of beams (block 630). For example, the UE (e.g., using communication manager 140 and / or beam management component 708) may select a beam for communicating with a network node from among the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each respective beam included in the set of beams, as described above.

[0092] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0093] In a first aspect, the one or more downlink traffic parameters satisfy the window open condition based at least in part on a downlink duty cycle having a value satisfying a threshold.

[0094] In a second aspect, alone or in combination with the first aspect, the one or more downlink traffic parameters satisfy the window opening condition based at least in part on a number of downlink grants having a value satisfying a threshold.

[0095] In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more downlink traffic parameters satisfy the window opening condition based at least in part on a downlink RB allocation having a value satisfying a threshold.

[0096] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the one or more downlink traffic parameters satisfy the window opening condition at least in part based on a fill size in one or more downlink grants having a value satisfying a threshold.

[0097] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the one or more downlink traffic parameters satisfy the window opening condition at least partially based on a downlink throughput requirement having a value that satisfies a threshold.

[0098] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the window opening condition is satisfied based at least in part on a time elapsed since a closing time of a most recent beam management window having a value satisfying a threshold.

[0099] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 600 comprises terminating the beam scan based at least in part on a count of the one or more PDSCH DMRS transmissions received during the beam management window satisfying a threshold.

[0100] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the beam management window does not include any time slot containing a periodic reference signal.

[0101] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the beam management window does not include any time slot containing an aperiodic reference signal associated with a timing offset parameter having a value greater than one.

[0102] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the one or more metrics used to select a beam include one or more rank-2 metrics.

[0103] although Figure 6 An example block diagram of process 600 is shown, but in some aspects, process 600 may include Figure 6 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 600. Additionally or alternatively, two or more of the blocks in the process 600 may be performed in parallel.

[0104] Figure 7 700 is a diagram of an example apparatus 700 for wireless communication. Apparatus 700 may be a UE, or a UE may include apparatus 700. In some aspects, apparatus 700 includes a receiving component 702 and a transmitting component 704 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 700 may communicate with another apparatus 706 (such as a UE, a base station, or another wireless communication device) using receiving component 702 and transmitting component 704. As further shown, apparatus 700 may include a communication manager 140. Communication manager 140 may include a beam management component 708, as well as other examples.

[0105] In some aspects, the apparatus 700 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 700 may be configured to perform one or more processes described herein, such as Figure 6 In some aspects, the apparatus 700 and / or Figure 7 One or more of the components shown in the figure may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Figure 7 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0106] The receiving component 702 may receive communications from the device 706, such as reference signals, control information, data communications, or combinations thereof. The receiving component 702 may provide the received communications to one or more other components of the device 700. In some aspects, the receiving component 702 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and may provide the processed signals to one or more other components of the device 700. In some aspects, the receiving component 702 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the UE.

[0107] The transmitting component 704 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 706. In some aspects, one or more other components of the device 700 may generate communications and may provide the generated communications to the transmitting component 704 for transmission to the device 706. In some aspects, the transmitting component 704 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications and may transmit the processed signals to the device 706. In some aspects, the transmitting component 704 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE. In some aspects, the transmit component 704 can be co-located with the receive component 702 in a transceiver.

[0108] The beam management component 708 may identify a beam management window based at least in part on one or more downlink traffic parameters satisfying a window open condition. The beam management component 708 may perform beam scanning on a set of beams associated with one or more PDSCH DMRS transmissions received during the beam management window. The beam management component 708 may select a beam for communicating with a network node from among the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each respective beam included in the set of beams.

[0109] The beam management component 708 can terminate the beam scanning based at least in part on a count of the one or more PDSCH DMRS transmissions received during the beam management window satisfying a threshold.

[0110] Figure 7 The number and arrangement of components shown in are provided as examples. Figure 7 There may be additional components, fewer components, different components, or components arranged in a different manner than those components shown in FIG. Figure 7 Two or more components shown in may be implemented in a single component, or Figure 7 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Figure 7 A set (one or more) of components shown in the figure may be described as being executed by Figure 7 One or more functions performed by another set of components shown in FIG.

[0111] The following provides an overview of some aspects of the disclosure:

[0112] Aspect 1: A method of wireless communication performed by a UE, the method comprising: identifying a beam management window based at least in part on one or more downlink service parameters satisfying a window opening condition; performing beam scanning on a set of beams associated with one or more PDSCH DMRS transmissions received during the beam management window; and selecting a beam for communicating with a network node from the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each corresponding beam included in the set of beams.

[0113] Aspect 2: The method according to aspect 1, wherein the one or more downlink traffic parameters satisfy the window opening condition at least partially based on a downlink duty cycle having a value that satisfies a threshold.

[0114] Aspect 3: The method according to any one of aspects 1 to 2, wherein the one or more downlink traffic parameters satisfy the window opening condition at least partially based on the number of downlink grants having a value that satisfies a threshold.

[0115] Aspect 4: The method according to any one of aspects 1 to 3, wherein the one or more downlink traffic parameters satisfy the window opening condition at least partially based on a downlink resource block allocation having a value that satisfies a threshold.

[0116] Aspect 5: A method according to any one of aspects 1 to 4, wherein the one or more downlink traffic parameters satisfy the window opening condition at least in part based on a padding size in one or more downlink grants having a value that satisfies a threshold.

[0117] Aspect 6: The method according to any one of aspects 1 to 5, wherein the one or more downlink traffic parameters satisfy the window opening condition at least partially based on a downlink throughput requirement having a value that satisfies a threshold.

[0118] Aspect 7: The method according to any one of aspects 1 to 6, wherein the window opening condition is satisfied based at least in part on a time elapsed since a closing time of a most recent beam management window having a value satisfying a threshold.

[0119] Aspect 8: According to the method of any one of aspects 1 to 7, the method also includes: terminating the beam scanning at least in part based on a count of the one or more PDSCH DMRS transmissions received during the beam management window satisfying a threshold.

[0120] Aspect 9: The method according to any one of aspects 1 to 8, wherein the beam management window does not include any time slot containing a periodic reference signal.

[0121] Aspect 10: The method according to any one of aspects 1 to 9, wherein the beam management window does not include any time slot containing an aperiodic reference signal associated with a timing offset parameter having a value greater than one.

[0122] Aspect 11: The method according to any one of aspects 1 to 10, wherein the one or more metrics used to select the beam include one or more rank 2 metrics.

[0123] Aspect 12: An apparatus for performing wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 1 to 11.

[0124] Aspect 13: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to execute the method according to one or more of aspects 1 to 11.

[0125] Aspect 14: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 11.

[0126] Aspect 15: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 11.

[0127] Aspect 16: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform the method according to one or more aspects of aspects 1 to 11.

[0128] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0129] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures and / or functions and other examples. As used herein, "processor" is implemented by a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method at least in part based on the description herein.

[0130] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0131] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically listed in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0132] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated so. In addition, as used herein, the articles "one" and "an" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more items connected with the article "the", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and can be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: identifying a beam management window based at least in part on one or more downlink traffic parameters satisfying a window opening condition; performing beam scanning on a set of beams associated with one or more physical downlink shared channel (PDSCH) demodulation reference signal (DMRS) transmissions received during the beam management window; as well as A beam for communicating with a network node is selected from the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each respective beam included in the set of beams.

2. The method of claim 1, wherein the one or more downlink traffic parameters satisfy the window open condition based at least in part on a downlink duty cycle having a value that satisfies a threshold.

3. The method of claim 1, wherein the one or more downlink traffic parameters satisfy the window open condition based at least in part on a number of downlink grants having values ​​that satisfy a threshold.

4. The method of claim 1, wherein the one or more downlink traffic parameters satisfy the window open condition based at least in part on a downlink resource block allocation having a value that satisfies a threshold.

5. The method of claim 1, wherein the one or more downlink traffic parameters satisfy the window open condition based at least in part on a padding size in one or more downlink grants having a value that satisfies a threshold.

6. The method of claim 1, wherein the one or more downlink traffic parameters satisfy the window open condition based at least in part on a downlink throughput requirement having a value that satisfies a threshold.

7. The method of claim 1, wherein the window open condition is satisfied based at least in part on a time elapsed since a closing time of a most recent beam management window having a value satisfying a threshold.

8. The method according to claim 1, further comprising: The beam scanning is terminated based at least in part on a count of the one or more PDSCH DMRS transmissions received during the beam management window satisfying a threshold.

9. The method of claim 1, wherein the beam management window does not include any time slot containing a periodic reference signal.

10. The method of claim 1, wherein the beam management window does not include any time slot containing an aperiodic reference signal associated with a timing offset parameter having a value greater than one.

11. The method of claim 1, wherein the one or more metrics used to select the beam include one or more rank-2 metrics.

12. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to: identifying a beam management window based at least in part on one or more downlink traffic parameters satisfying a window opening condition; performing beam scanning on a set of beams associated with one or more physical downlink shared channel (PDSCH) demodulation reference signal (DMRS) transmissions received during the beam management window; as well as A beam for communicating with a network node is selected from the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each respective beam included in the set of beams.

13. The UE of claim 12, wherein the one or more downlink traffic parameters satisfy the window open condition based at least in part on a downlink duty cycle having a value that satisfies a threshold.

14. The UE of claim 12, wherein the one or more downlink traffic parameters satisfy the window open condition based at least in part on a number of downlink grants having values ​​that satisfy a threshold.

15. The UE of claim 12, wherein the one or more downlink traffic parameters satisfy the window open condition based at least in part on a downlink resource block allocation having a value that satisfies a threshold.

16. The UE of claim 12, wherein the one or more downlink traffic parameters satisfy the window open condition based at least in part on a padding size in one or more downlink grants having a value that satisfies a threshold.

17. The UE of claim 12, wherein the one or more downlink traffic parameters satisfy the window opening condition based at least in part on a downlink throughput requirement having a value satisfying a threshold.

18. The UE of claim 12, wherein the window opening condition is satisfied based at least in part on a time elapsed since a closing time of a most recent beam management window having a value satisfying a threshold.

19. The UE of claim 12, wherein the one or more processors are further configured to: The beam scanning is terminated based at least in part on a count of the one or more PDSCH DMRS transmissions received during the beam management window satisfying a threshold.

20. The UE of claim 12, wherein the beam management window does not include any time slot containing a periodic reference signal.

21. The UE of claim 12, wherein the beam management window does not include any time slot containing an aperiodic reference signal associated with a timing offset parameter having a value greater than one.

22. The UE of claim 12, wherein the one or more metrics used to select the beam comprise one or more rank-2 metrics.

23. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: identifying a beam management window based at least in part on one or more downlink traffic parameters satisfying a window opening condition; performing beam scanning on a set of beams associated with one or more physical downlink shared channel (PDSCH) demodulation reference signal (DMRS) transmissions received during the beam management window; as well as A beam for communicating with a network node is selected from the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each respective beam included in the set of beams.

24. A non-transitory computer-readable medium according to claim 23, wherein the one or more downlink traffic parameters satisfy the window opening condition based at least in part on: one or more of a downlink duty cycle, a number of downlink grants, a downlink resource block allocation, a padding size in one or more downlink grants, or a downlink throughput requirement having a value that satisfies a threshold.

25. The non-transitory computer readable medium of claim 23, wherein the window open condition is satisfied based at least in part on a time elapsed since a closing time of a most recent beam management window having a value satisfying a threshold.

26. The non-transitory computer readable medium of claim 23, wherein the one or more instructions further cause the UE to: The beam scanning is terminated based at least in part on a count of the one or more PDSCH DMRS transmissions received during the beam management window satisfying a threshold.

27. The non-transitory computer readable medium of claim 23, wherein the beam management window does not include any time slots containing a periodic reference signal.

28. The non-transitory computer readable medium of claim 23, wherein the beam management window does not include any time slot containing an aperiodic reference signal associated with a timing offset parameter having a value greater than one.

29. The non-transitory computer-readable medium of claim 23, wherein the one or more metrics used to select the beam include one or more rank-2 metrics.

30. An apparatus for wireless communication, the apparatus comprising: means for identifying a beam management window based at least in part on one or more downlink traffic parameters satisfying a window open condition; means for performing beam scanning on a set of beams associated with one or more physical downlink shared channel (PDSCH) demodulation reference signal (DMRS) transmissions received during the beam management window; and Means for selecting a beam for communicating with a network node among the set of beams associated with the one or more PDSCH DMRS transmissions received during the beam management window based at least in part on one or more metrics associated with each respective beam included in the set of beams.