WO2024026815A1

WO2024026815A1 - Tracking reference signal based report with user equipment flexibility

Info

Publication number: WO2024026815A1
Application number: PCT/CN2022/110466
Authority: WO
Inventors: Jing Dai; Lei Xiao; Hao Xu
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2022-08-05
Filing date: 2022-08-05
Publication date: 2024-02-08
Anticipated expiration: 2025-02-05

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive, from a network node, an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold. The UE may transmit, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions. Numerous other aspects are described.

Description

TRACKING REFERENCE SIGNAL BASED REPORT WITH USER EQUIPMENT FLEXIBILITY

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for tracking reference signal (TRS) -based reporting with user equipment (UE) flexibility.

BACKGROUND

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like) . 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) .

A wireless network may include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL” ) refers to a communication link from the network node to the UE, and “uplink” (or “UL” ) refers to a communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL) , a wireless local area network (WLAN) link, and/or a wireless personal area network (WPAN) link, among other examples) .

The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate on a municipal, national, regional, 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 the 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a 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, 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

Some aspects described herein relate to a user equipment (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 receive, from a network node, an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold. The one or more processors may be configured to transmit, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.

Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit, to a UE, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold. The one or more processors may be configured to receive, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.

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 receive, from a network node, an indication for triggering a TDCP report associated with a TRS. The one or more processors may be configured to select whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS. The one or more processors may be configured to transmit, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.

Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit, to a UE, an indication for triggering a TDCP report associated with a TRS. The one or more processors may be configured to receive, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS.

Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving, from a network node, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold. The method may include transmitting, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.

Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting, to a UE, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold. The method may include receiving, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.

Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving, from a network node, an indication for triggering a TDCP report associated with a TRS. The method may include selecting whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS. The method may include transmitting, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.

Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting, to a UE, an indication for triggering a TDCP report associated with a TRS. The method may include receiving, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive, from a network node, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit, to a UE, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive, from a network node, an indication for triggering a TDCP report associated with a TRS. The set of instructions, when executed by one or more processors of the UE, may cause the UE to select whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit, to a UE, an indication for triggering a TDCP report associated with a TRS. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a network node, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold. The apparatus may include means for transmitting, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a UE, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold. The apparatus may include means for receiving, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a network node, an indication for triggering a TDCP report associated with a TRS. The apparatus may include means for selecting whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS. The apparatus may include means for transmitting, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a UE, an indication for triggering a TDCP report associated with a TRS. The apparatus may include means for receiving, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.

The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.

While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices) . Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components. Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers) . It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

Fig. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

Fig. 2 is a diagram illustrating an example of a network node in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

Fig. 4 is a diagram illustrating an example of physical channels and reference signals in a wireless network, in accordance with the present disclosure.

Fig. 5 is a diagram illustrating examples of tracking reference signal (TRS) configurations, in accordance with the present disclosure.

Figs. 6A-6C are diagrams illustrating an example associated with TRS-based reporting with UE flexibility, in accordance with the present disclosure.

Fig. 7 is a diagram illustrating an example associated with TRS-based reporting with UE flexibility, in accordance with the present disclosure.

Fig. 8 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.

Fig. 9 is a diagram illustrating an example process performed, for example, by a network node, in accordance with the present disclosure.

Fig. 10 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.

Fig. 11 is a diagram illustrating an example process performed, for example, by a network node, in accordance with the present disclosure.

Fig. 12 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

Fig. 13 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the 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 a claim.

Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses 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, or the like (collectively referred to as “elements” ) . These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

While aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT) , aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G) .

Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE) ) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as a network node 110a, a network node 110b, a network node 110c, and a network node 110d) , a user equipment (UE) 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e) , and/or other entities. A network node 110 is a network node that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes. For example, a network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit) . As another example, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station) , meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs) ) .

In some examples, a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU. In some examples, a network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and/or one or more DUs. A network node 110 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, a transmission reception point (TRP) , a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and/or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.

In some examples, a network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP) , the term “cell” can refer to a coverage area of a network node 110 and/or a network node subsystem serving this coverage area, depending on the context in which the term is used. A network node 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., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG) ) . A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In the example shown in Fig. 1, the network node 110a may be a macro network node for a macro cell 102a, the network node 110b may be a pico network node for a pico cell 102b, and the network node 110c may be a femto network node for a femto cell 102c. A network node may support one or multiple (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network node 110 that is mobile (e.g., a mobile network node) .

In some aspects, the terms “base station” or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, “base station” or “network node” may refer to a CU, a DU, an 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” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110. In some aspects, the term “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the term “base station” or “network node” may refer to any one or more of those different devices. In some aspects, the term “base station” or “network node” may refer to one or more virtual base stations 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 term “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.

The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110) . A relay station may be a UE 120 that can relay transmissions for other UEs 120. In the example shown in Fig. 1, the network node 110d (e.g., a relay network node) may communicate with the network node 110a (e.g., a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, or the like.

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

A network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit. A UE 120 may 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, 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 vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and/or any other suitable device that is configured to communicate via a wireless or wired medium.

Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a network node, another device (e.g., a remote device) , or some other entity. Some UEs 120 may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered a Customer Premises Equipment. A UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and/or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

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

In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using a network node 110 as an intermediary to communicate with one another) . For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol) , and/or a mesh network. In such examples, a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the network node 110.

Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, 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 range designations 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 referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz -300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz -24.25 GHz) . Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz -71 GHz) , FR4 (52.6 GHz -114.25 GHz) , and FR5 (114.25 GHz -300 GHz) . Each of these higher frequency bands falls within the EHF band.

With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, ifused herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, ifused herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may 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) may be modified, and techniques described herein are applicable to those modified frequency ranges.

In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive, from a network node, an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and transmit, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

In some aspects, as described in more detail elsewhere herein, the communication manager 140 may receive, from a network node, an indication for triggering a TDCP report associated with a TRS; select whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS; and transmit, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit, to a UE, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and receive, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

In some aspects, as described in more detail elsewhere herein, the communication manager 150 may transmit, to a UE, an indication for triggering a TDCP report associated with a TRS; and receive, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

Fig. 2 is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1) . The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1) . The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 254. In some examples, a network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.

At the network node 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120) . The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS (s) selected for the UE 120 and may 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., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS) ) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) ) . A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if 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 through 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal. The modems 232a through 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 through 234t.

At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive the downlink signals from the network node 110 and/or other network nodes 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 through 254r. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a 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 modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A 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 examples. In some examples, one or more components of the UE 120 may be included in a housing 284.

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 network node 110 via the communication unit 294.

One or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252r) may include, or may 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, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings) , a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of Fig. 2.

On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM) , and transmitted to the network node 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 the antenna (s) 252, the modem (s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 6A-6C and 7-13) .

At the network node 110, the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232) , detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller/processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 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 network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of the antenna (s) 234, the modem (s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 6A-6C and 7-13) .

The controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component (s) of Fig. 2 may perform one or more techniques associated with TRS-based reporting with UE flexibility, as described in more detail elsewhere herein. For example, the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component (s) of Fig. 2 may perform or direct operations of, for example, process 800 of Fig. 8, process 900 of Fig. 9, process 1000 of Fig. 10, process 1100 of Fig. 11, and/or other processes as described herein. The memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively. In some examples, the memory 242 and/or the 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 (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the network node 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the network node 110 to perform or direct operations of, for example, process 800 of Fig. 8, process 900 of Fig. 9, process 1000 of Fig. 10, process 1100 of Fig. 11, and/or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, a UE (e.g., the UE 120) includes means for receiving, from a network node, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and/or means for transmitting, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions. The means for the UE to perform operations described herein may include, for example, one or more of communication 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.

In some aspects, a UE (e.g., the UE 120) includes means for receiving, from a network node, an indication for triggering a TDCP report associated with a TRS; means for selecting whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS; and/or means for transmitting, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS. The means for the UE to perform operations described herein may include, for example, one or more of communication 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.

In some aspects, a network node (e.g., the network node 110) includes means for transmitting, to a UE, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and/or means for receiving, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions. In some aspects, the means for the network node to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

In some aspects, a network node (e.g., the network node 110) includes means for transmitting, to a UE, an indication for triggering a TDCP report associated with a TRS; and/or means for receiving, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS. In some aspects, the means for the network node to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions 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.

As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.

Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB) , an evolved NB (eNB) , an NR BS, a 5G NB, an access point (AP) , a TRP, or a cell, among other examples) , or one or more units (or one or more components) performing base station functionality, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. “Network entity” or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof) .

An aggregated base station (e.g., an aggregated network node) 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 disaggregated base station (e.g., a disaggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs) . In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other network nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) , among other examples.

Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both) . A CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through Fl interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be simultaneously served by multiple RUs 340.

Each of the units, including the CUs 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305, may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (for example, Central Unit -User Plane (CU-UP) functionality) , control plane functionality (for example, Central Unit -Control Plane (CU-CP) functionality) , or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the E 1 interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.

Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT) , an inverse FFT (iFFT) , digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.

Each RU 340 may implement lower-layer functionality. In some deployments, an RU 340, controlled by a DU 330, may correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 3GPP) , such as a lower layer functional split. In such an architecture, each RU 340 can be operated to handle over the air (OTA) communication with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an O 1 interface) . For virtualized network elements, the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface) . Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective O1 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.

The Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 325, the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies) .

As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.

Fig. 4 is a diagram illustrating an example 400 of physical channels and reference signals in a wireless network, in accordance with the present disclosure. As shown in Fig. 4, downlink channels and downlink reference signals may carry information from a network node 110 to a UE 120, and uplink channels and uplink reference signals may carry information from a UE 120 to a network node 110.

As shown, a downlink channel may include a physical downlink control channel (PDCCH) that carries downlink control information (DCI) , a physical downlink shared channel (PDSCH) that carries downlink data, or a physical broadcast channel (PBCH) that carries system information, among other examples. In some aspects, PDSCH communications may be scheduled by PDCCH communications. As further shown, an uplink channel may include a physical uplink control channel (PUCCH) that carries uplink control information (UCI) , a physical uplink shared channel (PUSCH) that carries uplink data, or a PRACH used for initial network access, among other examples. In some aspects, the UE 120 may transmit acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK/NACK feedback or ACK/NACK information) in UCI on the PUCCH and/or the PUSCH.

As further shown, a downlink reference signal may include a synchronization signal block (SSB) , a channel state information (CSI) reference signal (CSI-RS) , a DMRS, a positioning reference signal (PRS) , a phase tracking reference signal (PTRS) , or a TRS, among other examples. As also shown, an uplink reference signal may include a sounding reference signal (SRS) , a DMRS, or a PTRS, among other examples.

An SSB may carry information used for initial network acquisition and synchronization, such as a PSS, an SSS, a PBCH, and a PBCH DMRS. An SSB is sometimes referred to as a synchronization signal/PBCH (SS/PBCH) block. In some aspects, the network node 110 may transmit multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection.

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

A DMRS may carry information used to estimate a radio channel for demodulation of an associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH) . The design and mapping of a DMRS may be specific to a physical channel for which the DMRS is used for estimation. DMRSs are UE-specific, can be beamformed, can be confined in a scheduled resource (e.g., rather than transmitted on a wideband) , and can be transmitted only when necessary. As shown, DMRSs are used for both downlink communications and uplink communications.

A PTRS may carry information used to compensate for oscillator phase noise. Typically, the phase noise increases as the oscillator carrier frequency increases. Thus, PTRS can be utilized at high carrier frequencies, such as millimeter wave frequencies, to mitigate phase noise. The PTRS may be used to track the phase of the local oscillator and to enable suppression of phase noise and common phase error (CPE) . As shown, PTRSs are used for both downlink communications (e.g., on the PDSCH) and uplink communications (e.g., on the PUSCH) .

A PRS may carry information used to enable timing or ranging measurements of the UE 120 based on signals transmitted by the network node 110 to improve observed time difference of arrival (OTDOA) positioning performance. For example, a PRS may be a pseudo-random Quadrature Phase Shift Keying (QPSK) sequence mapped in diagonal patterns with shifts in frequency and time to avoid collision with cell-specific reference signals and control channels (e.g., a PDCCH) . In general, a PRS may be designed to improve detectability by the UE 120, which may need to detect downlink signals from multiple neighboring network nodes in order to perform OTDOA-based positioning. Accordingly, the UE 120 may receive a PRS from multiple cells (e.g., a reference cell and one or more neighbor cells) , and may report a reference signal time difference (RSTD) based on OTDOA measurements associated with the PRSs received from the multiple cells. In some aspects, the network node 110 may then calculate a position of the UE 120 based on the RSTD measurements reported by the UE 120.

A TRS is a downlink signal that may be used to perform time synchronization or frequency synchronization with an area, or to perform other tracking in order to receive communications in the area. The UE 120 may receive the TRS and may compare the resources on which the TRS is received to resources on which the TRS was expected to be received to perform time and frequency synchronization and tracking. For example, the UE 120 may use the TRS to update a tracking loop, which tracks changes to a frame timing of the network and an estimated time of arrival (TOA) of signals to be received by the UE 120. The TRS may be a type of CSI-RS configured for downlink tracking, referred to as a CSI-RS for tracking.

An SRS may carry information used for uplink channel estimation, which may be used for scheduling, link adaptation, precoder selection, or beam management, among other examples. The network node 110 may configure one or more SRS resource sets for the UE 120, and the UE 120 may transmit SRSs on the configured SRS resource sets. An SRS resource set may have a configured usage, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operations, uplink beam management, among other examples. The network node 110 may measure the SRSs, may perform channel estimation based at least in part on the measurements, and may use the SRS measurements to configure communications with the UE 120.

As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4.

Fig. 5 is a diagram illustrating examples 500 and 510 of TRS configurations, in accordance with the present disclosure. A TRS may be configured as a CSI-RS resource set (e.g., configured with a parameter trs-Info) . As shown in example 500, in some cases, a TRS may be configured as a CSI-RS resource set with two CSI-RS resources in one slot. As shown in example 510, in some cases, a TRS may be configured as a CSI-RS resource set with four CSI-RS resources in two consecutive slots (e.g., with two CSI-RS resources in each slot of the two consecutive slots) .

TRSs may be periodic or aperiodic. For a periodic TRS (P-TRS) , all of the CSI-RS resources (e.g., two or four CSI-RS resources) within the CSI-RS resource set are configured to occur with the same periodicity, bandwidth, and frequency location. In this case, each TRS occasion for a configured P-TRS includes two TRS transmissions in a slot or four TRS transmissions in two consecutive slots. For an aperiodic TRS (AP-TRS) , the AP-TRS may have a corresponding P-TRS with the same bandwidth and frequency location, and the corresponding P-TRS may be a quasi co-location (QCL) for the AP-TRS. For example, the AP-TRS may be quasi co-located with the corresponding P-TRS with QCL type A or QCL type D.

In some examples (e.g., in a current wireless communication standard) , TRSs may be used only for downlink tracking (e.g., loop processing) by UEs, and CSI reporting may not be configured for TRSs. For example, a UE may not expect to be configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to a value other than “none” for an aperiodic non-zero power (NZP) CSI-RS resource set configured with trs-Info, and a UE may not expect to be configured with a CSI-ReportConfig for a periodic NZP CSI-RS resource set configured with trs-Info.

As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.

In a current wireless communication standard (e.g., in Releases 15, 16, and 17 of the standard promulgated by the 3GPP) , TRSs are used for downlink tracking (e.g., loop processing) , and whether to receive a configured TRS (e.g., a P-TRS or an AP-TRS) or not depends on UE implementation. For example, a UE may determine whether to remain in a sleep state and not to receive a TRS (resulting in reduced power consumption for the UE) or wake up to receive the TRS and perform downlink tracking. In some cases, a UE may be permitted to rely on an SSB for downlink tracking instead of a TRS if a signal-to-noise ratio (SNR) of the TRS is below a threshold (e.g., due to a collision with a downlink transmission from a neighbor cell) .

In some aspects, a UE may be configured to report TDCPs measured via a TRS (e.g., a CSI-RS for tracking) to a network node. For example, such TRS-based TDCP reporting may be configured for medium and high speed UEs (e.g., for UEs with speeds of 10-120 km/h, as well as high speed train (HST) speeds) . The TRS-based TDCP reporting may exploit time-domain correlation and/or Doppler-domain information to assist the network node in downlink precoding. For example, the TRS-based TDCP reporting may assist the network node in determining a precoding scheme, using a CSI feedback based precoding scheme or an uplink SRS reciprocity based precoding scheme. Additionally, or alternatively, the TRS-based TDCP reporting may assist the network node in determining a CSI reporting configuration and/or CSI-RS resource configuration parameters, and/or the TRS-based TDCP reporting may aid the network node in performing CSI prediction. However, to perform TRS-based TDCP reporting, a UE may be forced to receive a TRS in some TRS occasions, which may adversely affect loop processing and/or power saving strategies of the UE.

Some techniques and apparatuses described herein enable a UE to receive, from a network node, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions. In some aspects, one or more measured TRS occasions may occur after the indication for triggering the TDCP report is received and decoded by the UE, and a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions may satisfy a gap threshold. The UE may transmit, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions. The gap threshold may provide flexibility for the UE to determine whether to receive or not receive TRS transmissions in TRS occasions for downlink tracking, while enabling the UE to receive the TRS transmissions in the one or more measured TRS occasions for TDCP reporting. For example, in a case in which the UE determines not to receive TRS transmissions in TRS occasions for downlink tracking, the gap threshold may provide sufficient time between the indication for triggering the TDCP report and the measured TRS occasions for the UE to prepare to receive the TRS transmissions in the measured TRS occasions. As a result, the UE may perform TDCP reporting based at least in part on the TRS transmissions in the one or more measured TRS occasions, while maintaining flexibility to determine whether or not to receive TRS transmissions in other TRS occasions, which may reduce the adverse effect of the TDCP reporting on the loop processing and/or power saving strategies of the UE.

Some techniques and apparatuses described herein enable a UE to have flexibility in determining whether to perform TDCP reporting based on a TRS or not based on the TRS. In some aspects, the UE may receive, from a network node, an indication for triggering a TDCP report associated with a TRS. The UE may select whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS. The UE may transmit, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS. For example, in a case in which the UE selects to report the one or more TDCP parameters not based on the TRS, the one or more TDCP parameters may be based at least in part on measurements of one or more sensors associated with the UE. As a result, the UE may have the flexibility to select not to receive TRS transmissions, even when the UE is triggered to perform TDCP reporting, which may reduce the adverse effect of the TDCP reporting on the loop processing and/or power saving strategies of the UE.

Figs. 6A-6C are diagrams illustrating an example 600 associated with TRS-based reporting with UE flexibility, in accordance with the present disclosure. As shown in Fig. 6A, example 600 includes communication between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

As shown in Fig. 6A, and by reference number 605, the UE 120 may transmit capability information to the network node 110. The network node 110 may receive the capability information from the UE 120. For example, the UE 120 may transmit the capability information to the network node 110 in an RRC message. In some aspects, the capability information may include capability information relating to receiving and decoding downlink (e.g., PDCCH) communications. For example, the capability information may indicate a processing capability of the UE 120 that identifies or relates to a processing time for the UE 120 to receive and decode a PDCCH communication. Additionally, or alternatively, the capability information may include capability information relating to performing TDCP measurements and/or TDCP reporting. For example, the capability information may indicate a capability of the UE 120 for TDCP reporting based on a half of a TRS occasion.

As further shown in Fig. 6A, and by reference number 610, the network node 110 may transmit, and the UE 120 may receive, a TRS configuration. In some aspects, the TRS configuration may indicate resources (e.g., CSI-RS resources) for a TRS. For example, the TRS configuration may indicate a CSI-RS resource set (configured with the parameter trs-Info) configured for the TRS. In some aspects, the TRS configuration may indicate a configuration of P-TRS that includes a CSI-RS resource set that is repeated, with a configured periodicity, in periodically reoccurring TRS occasions. In some aspects, the CSI-RS resource set configured for the TRS may include CSI-RS resources (for transmitting the TRS) in two symbols within one slot. In this case, each TRS occasion includes two symbols (in which the TRS is transmitted) within one slot. In some aspects, the CSI-RS resource set configured for the TRS may include CSI-RS resources (for transmitting the TRS) in four symbols in two consecutive slots (e.g., with CSI-RS resources in two symbols in each slot of the two consecutive slots) . In this case, each TRS occasion includes four symbols (in which the TRS is transmitted) in two consecutive slots.

In some aspects, the TRS configuration may include a configuration of a TDCP report associated with the TRS. For example, the configuration of the TDCP report may be a CSI report configuration. In some aspects, the configuration of the TDCP report may indicate uplink resources (e.g., PUSCH resources) for the UE 120 to use to transmit the TDCP report to the network node 110. In some aspects, the configuration of the TDCP report may indicate one or more TDCP parameters to be included in the TDCP report. For example, the one or more TDCP parameters may include a Doppler shift, a Doppler spread, a cross-correlation in time, a relative Doppler shift of a number of peaks in a channel impulse response (CIR) , relative Doppler shifts of different TRSs, CSI-RS resource configuration assistance information, and/or CSI reporting configuration assistance information. In some aspects, the configured TDCP report may be an aperiodic TDCP report that is triggered by an indication transmitted (e.g., in a PDCCH communication) from the network node 110 to the UE 120.

As further shown in Fig. 6A, and by reference number 615, the network node 110 may transmit, to the UE 120, an indication for triggering a TDCP report based at least in part on a TRS. The UE 120 may receive the indication for triggering the TDCP report. In some aspects, the indication for triggering the TDCP report may be included in a PDCCH communication that is transmitted to the UE 120 by the network node 110. For example, the indication may be a CSI request DCI included in a PDCCH communication. In some aspects, the indication may trigger the UE 120 to transmit a TDCP report in accordance with the configuration of the TDCP report included in the TRS configuration.

In some aspects, the indication may trigger a TDCP report based at least in part on one or more measured TRS occasions. The one or more measured TRS occasions are one or more TRS occasions in which the TRS transmissions (e.g., in the configured CSI-RS resources) are measured by the UE 120 to determine the one or more TDCP parameters included in the TDCP report.

As further shown in Fig. 6A, and by reference number 620, the UE 120 may measure TDCP measurements in the one or more measured TRS occasions. In some aspects, the UE 120, in connection with receiving the indication for triggering the TDCP report, may identify the one or more measured TRS occasions for the TDCP report. The UE 120 may perform TDCP measurements (e.g., measurements used to determine the one or more TDCP parameters to be indicated in the TDCP report) on one or more TRS transmissions in each measured TRS occasion. In some aspects, for the aperiodic TDCP report, the one or more measured TRS occasions for the TDCP report may occur after the triggering indication (e.g., the triggering PDCCH) is decoded. In some aspects, a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions may satisfy a gap threshold. For example, the gap threshold may be a PDCCH-to-TRS gap threshold. The one or more measured TRS occasions may include one or more TRS occasions for which the time gap between the indication (e.g., the triggering PDCCH) for triggering the TDCP report and the TRS occasion satisfies the gap threshold. For example, as shown by reference number 625, a gap between a last symbol of the triggering PDCCH and a first symbol of a measured TRS occasion (shown in Fig. 6A with four symbols for TRS transmissions in two consecutive slots) may satisfy (e.g., be greater than or equal to) the gap threshold.

In some aspects, the gap threshold may be based at least in part on a subcarrier spacing (SCS) . For example, the value of the gap threshold may increase as the SCS increases. Additionally, or alternatively, the gap threshold may be based at least in part on a capability of the UE 120 indicated in the capability information. In some aspects, the gap threshold value may be configured or determined similarly to a timeline for transmitting an ACK for a PDCCH communication that releases semi-persistent PDSCH resources. In some aspects, the gap threshold value may be N = 5 for μ = 0, N = 5.5 for μ = 1, and N = 11 for μ = 2 for a first configuration or a first UE capability, and the gap threshold value may be N = 10 for μ = 0, N = 12 for μ = 1, N = 22 for μ = 2, N = 25 for μ = 3, N = 100 for μ = 5, and N = 200 for μ = 6 for a second configuration or a second UE capability, where μ is numerology parameter that is based at least in part on the SCS, and N indicates a number of symbols for the gap threshold value. In this case, the first UE capability may correspond to the first processing time capability, and the second UE capability may correspond to a second processing time capability.

In some aspects, the TDCP report (e.g., the aperiodic TDCP report) may be based on a P-TRS. For example, the TDCP report may be based at least in part on one more measured TRS occasions, and the one or more measured TRS occasions may include one or more periodically occurring TRS occasions associated with a P-TRS. In some aspects, for a P-TRS, the one or more measured TRS occasions may include one or more TRS occasions that occur after the gap threshold from the indication for triggering the TDCP report (e.g., the gap between the triggering indication and the TRS occasion satisfies the gap threshold) and no later than a reference resource (e.g., a CSI reference resource) that is based at least in part on a slot in which the UE 120 is to transmit the TDCP report. For example, as shown in Fig. 6B, and by reference number 640,

TRS occasions

642 and 644 are periodic TRS occasions that occur with a configured periodicity. The TRS occasion 642 is a measured TRS occasion, and the TRS occasion 644 is not a measured TRS occasion. The measured TRS occasion 642 occurs after the gap threshold from a PDCCH communication 646 that triggers the TDCP report and no later than slot n _ref 648, which is a slot of the reference resource. The TRS occasion 644 occurs after the slot n _ref 648 (e.g., after the reference resource) , and is therefore not a measured TRS occasion.

The reference resource may be a CSI reference resource. The reference resource (in the time domain) may be a downlink slot n _ref = n -n _{CSI_ref}, where n is the uplink slot for reporting (e.g., the uplink slot in which the UE 120 is to transmit the TDCP report) , and n _{CSI_ref} is a value that differs for periodic, semi-persistent, or aperiodic reporting. For a periodic report, n _{CSI_ref} may be the smallest value that is ≥

(for a single-RS CSI repon) or≥

(for a multi-RS CSI report) , such that the slot n -n _{CSI_ref} corresponds to a valid downlink slot. For an aperiodic report (e.g., the aperiodic TDCP report) , the reference resource may be either the slot with the CSI request DCI (for a same-slot report) , or determined by a CSI processing time Z′ (for a report in a slot after the slot of the CSI request DCI) . For example, for an aperiodic report, n _{CSI_ref} may be the smallest value that is≥

slots, such that slot n -n _{CSI_ref} corresponds to a valid downlink slot.

In some aspects, in a case in which the TDCP report is based on a P-TRS, the network node 110 may be required to trigger the TDCP report such that there is at least one periodic TRS occasion that occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource. For example, the UE 120, when receiving the indication for triggering the TDCP report, may expect that at least one periodic TRS occasion occurs after the gap threshold from the indication and no later than the reference resource. In some aspects, the UE 120, in connection with receiving the indication for triggering the TDCP report, may determine whether at least one periodic TRS occasion occurs after the gap threshold from the indication and no later than the reference resource. In this case, in connection with a determination that at least one periodic TRS occasion occurs after the gap threshold from the indication and no later than the reference resource, the UE 120 may perform the TDCP measurements (e.g., measurements for determining the TDCP parameters to be included in the TDCP report) and transmit the TDCP report to the network node 110. In connection with a determination that there is not at least one periodic TRS occasion that occurs after the gap threshold from the indication and no later than the reference resource, the UE 120 may select not to transmit the TDCP report to the network node 110. For example, in a case in which there is no TRS occasion that occurs after the gap threshold from the indication and no later than the reference resource, the UE 120 may not be required to update the TDCP report, or the UE 120 may drop the TDCP report.

In some aspects, in a case in which a TRS occasion includes four symbols for transmitting the TRS in two consecutive slots, and only a half of a TRS occasion (ahalf-TRS occasion) occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource, the UE 120 may use the half-TRS occasion as a measured TRS occasion for the TDCP report. In this case, the one or more measured TRS occasions for the TDCP report may include only a half-TRS occasion. For example, the half-TRS occasion may include one slot with two TRS symbols.

Fig. 6C shows an example 650, in which only a first half of a TRS occasion is used as a measured TRS occasion for a TDCP report, and an example 660, in which only a second half of a TRS occasion is used as a measured TRS occasion for a TDCP report. As shown in example 650, a TRS occasion 652 may be a periodic TRS occasion that includes four TRS symbols in two consecutive slots. The TRS occasion may include a first half-TRS occasion 652a that includes the TRS symbols in the first slot, and a second half-TRS occasion 652b that includes the TRS symbols in the second slot. The first half-TRS occasion 652a may occur after the gap threshold from a PDCCH communication 654 for triggering the TDCP report, and the first half-TRS occasion 652a may occur no later than (e.g., in) the slot n _ref 656 (e.g., the slot of the reference resource) . The second half-TRS occasion 652b may occur after the slot n _ref 656. In some aspects, the UE 120 may use the only first half-TRS occasion 652a (and not the second half-TRS occasion 652b) as a measured TRS occasion based at least in part on the first half-TRS occasion 652a occurring no later than the slot n _ref 656 (e.g., the first half-TRS 652a occurs in the slot n _ref 656) and the second half-TRS occasion 652b occurring after the slot n _ref 656. As shown by reference number 658, the UE 120 may transmit, in a PUSCH resource configured for the TDCP report, the TDCP report that is based at least in part on the TRS transmissions (e.g., the TRS symbols) in the first half-TRS occasion 652a.

As shown in example 660, a TRS occasion 662 may be a periodic TRS occasion that includes four TRS symbols in two consecutive slots. The TRS occasion may include a first half-TRS occasion 662a that includes the TRS symbols in the first slot, and a second half-TRS occasion 662b that includes the TRS symbols in the second slot. The first half-TRS occasion 662a may not occur after the gap threshold from a PDCCH communication 664 for triggering the TDCP report. For example, a gap between the last symbol of the PDCCH communication 664 and a first TRS symbol in the first half-TRS occasion 662a may not satisfy the gap threshold. The second half-TRS occasion 662b may occur after the gap threshold from the PDCCH communication 664. For example, a gap between the last symbol of the PDCCH communication 664 and the first TRS symbol in the second half-TRS occasion 662b may satisfy the gap threshold. The second half-TRS occasion 662b may occur before the slot n _ref 666 (e.g., the slot of the reference resource) . In some aspects, the UE 120 may use only the second half-TRS occasion 662b (and not the first half-TRS occasion 662a) as a measured TRS occasion based at least in part on the gap between the PDCCH communication 664 and the second half-TRS occasion 662b satisfying the gap threshold, and the gap between the PDCCH communication 664 and the first half-TRS occasion 662a not satisfying the threshold. As shown by reference number 668, the UE 120 may transmit, in a PUSCH resource configured for the TDCP report, the TDCP report that is based at least in part on the TRS transmissions (e.g., the TRS symbols) in the second half-TRS occasion 662b.

In some aspects, the network node 110 may be required to trigger the TDCP report such that there is at least one half-TRS occasion (e.g., two TRS symbols in one slot of a TRS configuration with TRS symbols in two slots) that occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource. For example, the UE 120, when receiving the indication for triggering the TDCP report, may expect that there at least one half-TRS occasion that occurs after the gap threshold from the indication and no later than the reference resource. In some aspects, the UE 120, in connection with receiving the indication for triggering the TDCP report, may determine whether at least one half-TRS occasion occurs after the gap threshold from the indication and no later than the reference resource. In this case, in connection with a determination that at least one half-TRS occasion occurs after the gap threshold from the indication and no later than the reference resource, the UE 120 may perform the TDCP measurements (e.g., measurements for determining the TDCP parameters to be included in the TDCP report) and transmit the TDCP report to the network node 110. In connection with a determination that there is not at least one half-TRS occasion that occurs after the gap threshold from the indication and no later than the reference resource, the UE 120 may select not to transmit the TDCP report to the network node 110. For example, in a case in which there is no TRS occasion or half-TRS occasion that occurs after the gap threshold from the indication and no later than the reference resource, the UE 120 may not be required to update the TDCP report, or the UE 120 may drop the TDCP report.

In some aspects, the gap threshold may apply in a case in which the one or more measured TRS occasions for the TDCP report are periodic TRS occasions associated with a P-TRS, and the gap threshold may not apply in a case in which the one or more measured TRS occasions for the TDCP report are associated with one or more AP-TRSs.

In some aspects, the gap threshold may apply in a case in which the one or more measured TRS occasions for the TDCP report are associated with AP-TRSs, as well as in a case in which the one or more measured TRS occasions are associated with a P-TRS. In this case, the network node 110 may schedule a TRS occasion for an AP-TRS to be measured by the UE 120 for the TDCP report such that a time gap between the indication for triggering the TDCP report and the TRS occasion for the AP-TRS (e.g., the gap between a last symbol of the indication for triggering the TDCP report and a first TRS symbol in the TRS occasion) satisfies the gap threshold, and the TRS occasion for the AP-TRS occurs no later than the reference resource. In some aspects, the network node 110 may be required to schedule an aperiodic TRS occasion for the TDCP report to occur after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource. For example, the UE 120 may expect that an aperiodic TRS occasion for a TDCP report is scheduled to occur after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource. In some aspects, the UE 120 may ignore (e.g., refrain from receiving and/or measuring) an AP-TRS occasion for a TDCP report in a case in which the AP-TRS occasion does not occur after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.

In some aspects, the UE 120 may use a half-TRS occasion for an AP-TRS as a measured TRS occasion for the TDCP report, similar to as described above in connection with Fig. 6C. In some aspects, whether the TDCP report can be based on a half-TRS occasion (for P-TRS or AP-TRS) may be based at least in part on a UE capability indicated in the capability information.

Returning to Fig. 6A, as shown by reference number 630, the UE 120 may transmit the TDCP report to the network node 110. The network node 110 may receive the TDCP report from the UE 120. The TDCP report may be based at least in part on one or more TRS transmissions in the one or more measure TRS occasions. The UE 120 may transmit the TDCP report in uplink resources (e.g., a PUSCH resources) configured for the TDCP report.

In some aspects, the UE 120 may transmit the TDCP report to the network node 110 based at least in part on a determination that at least one TRS occasion occurs after the gap threshold from the indication for triggering the TDCP report and no later than a reference resource that is based at least in part on the slot in which the UE 120 is to transmit the TDCP report. In some aspects, the UE 120 may transmit the TDCP report to the network node 110 based at least in part on a determination that at least one TRS occasion or at least one half-TRS occasion that occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource, that is based at least in part on the slot in which the UE 120 is to transmit the TDCP report.

In some aspects, the TDCP report may include one or more TDCP parameters. For example, the one or more TDCP parameters may include a Doppler shift, a Doppler spread, a cross-correlation in time, a relative Doppler shift of a number of peaks in a CIR, relative Doppler shifts of different TRSs, CSI-RS resource configuration assistance information, and/or CSI reporting configuration assistance information. In some aspects, the network node 110 may perform downlink precoding based at least in part on the one or more TDCP parameters included in the TDCP report. For example, the network node 110 may determine a precoding scheme, using a CSI feedback based precoding scheme or an uplink SRS reciprocity based precoding scheme, based at least in part on the one or more TDCP parameters included in the TDCP report. In some aspects, the network node 110 may determine one or more CSI-RS resource configuration parameters and/or one or more CSI reporting configuration parameters based at least in part on the one or more TDCP parameters included in the TDCP report. For example, the network node 110 may determine the one or more CSI-RS resource configuration parameters and/or the one or more CSI reporting configuration parameters based at least in part on the CSI-RS resource configuration assistance information and/or the CSI reporting configuration assistance information included in the TDCP report. In some aspects, the network node 110 may perform CSI prediction based at least in part on the one or more TDCP parameters included in the TDCP report.

As indicated above, Figs. 6A-6C are provided as an example. Other examples may differ from what is described with respect to Figs. 6A-6C.

Fig. 7 is a diagram illustrating an example 700 associated with TRS-based reporting with UE flexibility, in accordance with the present disclosure. As shown in Fig. 7, example 700 includes communication between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

As shown in Fig. 7, and by reference number 705, the UE 120 may transmit capability information to the network node 110. The network node 110 may receive the capability information from the UE 120. For example, the UE 120 may transmit the capability information to the network node 110 in an RRC message. In some aspects, the capability information may indicate a capability of the UE 120 to support TDCP reporting that is not based on a TRS. For example, the capability information may indicate whether the UE 120 is capable of reporting one or more TDCP parameters that are not based on a TRS. In some aspects, the capability of the UE 120 to support TDCP reporting that is not based on a TRS may be based at least in part on a sensing capability of the UE 120 and/or one or more sensors associated with the UE 120. In some aspects, the capability information may also indicate other UE capabilities, such as the UE capabilities described above in connection with Fig. 6A.

As further shown in Fig. 7, and by reference number 710, the network node 110 may transmit, and the UE 120 may receive, a TRS configuration. In some aspects, the TRS configuration may indicate resources (e.g., CSI-RS resources) for a TRS (e.g., a P-TRS or an AP-TRS) . For example, the TRS configuration may indicate a CSI-RS resource set (configured with the parameter trs-Info) configured for the TRS. In some aspects, the CSI-RS resource set configured for the TRS may include CSI-RS resources (for transmitting the TRS) in two symbols within one slot. In some aspects, the CSI-RS resource set configured for the TRS may include CSI-RS resources (for transmitting the TRS) in four symbols in two consecutive slots (e.g., with CSI-RS resources in two symbols in each slot of the two consecutive slots) .

In some aspects, the TRS configuration may include a configuration of a TDCP report associated with the TRS. For example, the configuration of the TDCP report may be a CSI report configuration. In some aspects, the configuration of the TDCP report may indicate uplink resources (e.g., PUSCH resources) for the UE 120 to use to transmit the TDCP report to the network node 110. In some aspects, the configuration of the TDCP report may indicate one or more TDCP parameters to be included in the TDCP report. For example, the one or more TDCP parameters may include a Doppler shift, a Doppler spread, a cross-correlation in time, a relative Doppler shift of a number of peaks in a CIR, relative Doppler shifts of different TRSs, CSI-RS resource configuration assistance information, and/or CSI reporting configuration assistance information. In some aspects, the configured TDCP report may be an aperiodic TDCP report that is triggered by an indication transmitted (e.g., in a PDCCH communication) from the network node 110 to the UE 120.

As further shown in Fig. 7, and by reference number 715, the network node 110 may transmit, to the UE 120, an indication for triggering a TDCP report associated with a TRS. The UE 120 may receive the indication for triggering the TDCP report. In some aspects, the indication for triggering the TDCP report may be included in a PDCCH communication that is transmitted to the UE 120 by the network node 110. For example, the indication may be a CSI request DCI included in a PDCCH communication. In some aspects, the indication may trigger the UE 120 to transmit a TDCP report in accordance with the configuration of the TDCP report included in the TRS configuration.

As further shown in Fig. 7, and by reference number 720, the UE 120 may select whether to report, in the TDCP report, TDCP parameters based on the TRS or TDCP parameters not based on the TRS. For example, the UE 120 may select to report, in the TDCP report, one or more TDCP parameters based on the TRS associated with the TDCP report, or the UE 120 may select to report, in the TDCP report, one or more TDCP parameters not based on the TRS. In a case in which the UE 120 selects to report the TDCP parameters based on the TRS, the UE 120 may perform TDCP measurements on one or more transmissions of the TRS (e.g., in one or more measured TRS occasions) , and the UE 120 may determine the TDCP parameters based at least in part on the TDCP measurements performed on the TRS.

In some aspects, in a case in which the UE 120 selects to report TDCP parameters not based on the TRS, the UE 120 may determine the TDCP parameters (e.g., the one or more TDCP parameters not based on the TRS) based at least in part on measurements of one or more sensors associated with the UE 120. For example, the one or more sensors associated with the UE 120 may sense a velocity and/or movement of the UE 120, and the UE 120 may determine one or more TDCP parameters based at least in part on the velocity and/or movement measurements of the one or more sensors associated with the UE 120. The one or more sensors associated with the UE 120 may include one or more sensors integrated with the UE 120 and/or one or more sensors mounted on the UE 120, among other examples. In some aspects, the UE 120 may determine one or more TDCP parameters, including one or more of a Doppler shift, a Doppler spread, a cross-correlation in time, CSI-RS resource configuration assistance information, and/or CSI reporting configuration assistance information, based at least in part on velocity measurements sensed by the one or more sensors associated with the UE 120. For example, the CSI-RS resource configuration assistance information may include suggested periodicities for CSI-RS resources, and the CSI reporting configuration assistance information may include suggested update periodicities for CSI reports.

By using the velocity measurements of the one or more sensors associated with the UE 120 to determine TDCP parameters to be reported in the TDCP report, the UE 120 may have the flexibility to select to report TDCP parameters that are not based on the TRS, which may allow the UE 120 to not receive the TRS. In some aspects, the UE 120 may select whether to report, in the TDCP report, TDCP parameters based on the TRS or TDCP parameters not based on the TRS based at least in part on the capability of the UE 120 to support TDCP reporting that is not based on a TRS, the TDCP parameters configured to be reported in the TDCP report, the TRS associated with the TDCP report, and/or loop processing and/or power saving strategies of the UE 120, among other examples.

In some aspects, the UE 120 may select whether to report, in the TDCP report, TDCP parameters based on the TRS or TDCP parameters not based on the TRS based at least in part on a determination of whether there is at least one TRS occasion, for the TRS associated with the TDCP report, that occurs after a gap threshold from the indication for triggering the TDCP report and no later than a reference resource based on the slot in which the TDCP report is to be transmitted by the UE 120. In this case, the operations described above in connection with the Figs. 6A-6C may be performed in combination with the operations described in connection with Fig. 7. For example, the UE 120, in connection with receiving the indication for triggering the TDCP report, may determine whether there is at least one TRS occasion (or at least one half-TRS occasion) , for the TRS associated with the TDCP report, that occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource, as described above in connection with Figs. 6A-6B. In some aspects, the UE 120 may select to report the TDCP parameters not based on the TRS, based at least in part on a determination that there is no TRS occasion that occurs after the gap threshold from the indication that triggers the TDCP report and no later than the reference resource. In some aspects, the UE 120 may select to report the TDCP parameters not based on the TRS, based at least in part on a determination that there is no TRS occasion or half-TRS occasion that occurs after the gap threshold from the indication that triggers the TDCP report and no later than the reference resource.

As further shown in Fig. 7, and by reference number 725, the UE 120 may transmit the TDCP report to the network node 110. The network node 110 may receive the TDCP report from the UE 120. The UE 120 may transmit the TDCP report in uplink resources (e.g., PUSCH resources) configured for transmitting the TDCP report. In some aspects, the TDCP report may include one or more TDCP parameters based on the TRS, in connection with the UE 120 selecting to report the one or more TDCP parameters based on the TRS. In some aspects, the TDCP report may include one or more TDCP parameters not based on the TRS, in connection with the UE 120 selecting to report the one or more TDCP parameters not based on the TRS. In this case, the TDCP parameters not based on the TRS may be based at least in part on measurements (e.g., velocity and/or movement measurements) of one or more sensors associated with the UE 120. For example, the one or more TDCP parameters not based on the TRS may include at least one of a Doppler shift, a Doppler spread, a cross-correlation in time, CSI-RS resource configuration assistance information, or CSI reporting configuration assistance information.

The TDCP report may include one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS. In some aspects, the network node 110 may perform downlink precoding based at least in part on the one or more TDCP parameters included in the TDCP report. For example, the network node 110 may determine a precoding scheme, using a CSI feedback based precoding scheme or an uplink SRS reciprocity based precoding scheme, based at least in part on the one or more TDCP parameters included in the TDCP report. In some aspects, the network node 110 may determine one or more CSI-RS resource configuration parameters and/or one or more CSI reporting configuration parameters based at least in part on the one or more TDCP parameters included in the TDCP report. In some aspects, the network node 110 may perform CSI prediction based at least in part on the one or more TDCP parameters included in the TDCP report.

As indicated above, Fig. 7 is provided as an example. Other examples may differ from what is described with respect to Fig. 7.

Fig. 8 is a diagram illustrating an example process 800 performed, for example, by a UE, in accordance with the present disclosure. Example process 800 is an example where the UE (e.g., UE 120) performs operations associated with TRS-based reporting with UE flexibility.

As shown in Fig. 8, in some aspects, process 800 may include receiving, from a network node, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold (block 810) . For example, the UE (e.g., using communication manager 140 and/or reception component 1202, depicted in Fig. 12) may receive, from a network node, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold, as described above.

As further shown in Fig. 8, in some aspects, process 800 may include transmitting, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions (block 820) . For example, the UE (e.g., using communication manager 140 and/or transmission component 1204, depicted in Fig. 12) may transmit, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions, as described above.

Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the one or more measured TRS occasions include one or more periodic TRS occasions configured for the UE.

In a second aspect, alone or in combination with the first aspect, each measured TRS occasion, of the one or more measured TRS occasions, includes four TRS symbols in two consecutive slots, or each measured TRS occasion, of the one or more measured TRS occasions, includes two symbols in a slot.

In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more measured TRS occasions include one or more of the periodic TRS occasions that occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, transmitting the TDCP report includes transmitting the TDCP report based at least in part on a determination that there is at least one of the periodic TRS occasions that occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the gap threshold is based at least in part on a subcarrier spacing.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the gap threshold is based at least in part on the subcarrier spacing and based at least in part on a capability of the UE.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the one or more measured TRS occasions include a half of a TRS occasion based at least in part on a determination that the half of the TRS occasion occurs after the gap threshold from the indication for triggering the TDCP report and no later than a reference resource based on a slot in which the UE is to transmit the TDCP report.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the TRS occasion includes four TRS symbols in two consecutive slots, and the one or more measured TRS occasions include a first slot of the two consecutive slots based at least in part on the first slot occurring after the gap threshold from the indication for triggering the TDCP report.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the TRS occasion includes four TRS symbols in two consecutive slots, and the one or more measured TRS occasions include a second slot of the two consecutive slots based at least in part on the second slot occurring after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the one or more measured TRS occasions include one or more measured aperiodic TRS occasions, the time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies the gap threshold, and the one or more measured TRS occasions occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process 800 includes measuring one or more TDCP measurements based at least in part on the one or more transmissions of the TRS in the one or more measured TRS occasions.

Although Fig. 8 shows example blocks of process 800, in some aspects, process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 8. Additionally, or alternatively, two or more of the blocks of process 800 may be performed in parallel.

Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a network node, in accordance with the present disclosure. Example process 900 is an example where the network node (e.g., network node 110) performs operations associated with TRS-based reporting with UE flexibility.

As shown in Fig. 9, in some aspects, process 900 may include transmitting, to a UE, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold (block 910) . For example, the network node (e.g., using communication manager 150 and/or transmission component 1304, depicted in Fig. 13) may transmit, to a UE, an indication for triggering a TDCP report based at least in part on one or more TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold, as described above.

As further shown in Fig. 9, in some aspects, process 900 may include receiving, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions (block 920) . For example, the network node (e.g., using communication manager 150 and/or reception component 1302, depicted in Fig. 13) may receive, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions, as described above.

Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, receiving the TDCP report includes receiving the TDCP report based at least in part on a determination that there is at least one of the periodic TRS occasions that occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.

Although Fig. 9 shows example blocks of process 900, in some aspects, process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel.

Fig. 10 is a diagram illustrating an example process 1000 performed, for example, by a UE, in accordance with the present disclosure. Example process 1000 is an example where the UE (e.g., UE 120) performs operations associated with TRS-based reporting with UE flexibility.

As shown in Fig. 10, in some aspects, process 1000 may include receiving, from a network node, an indication for triggering a TDCP report associated with a TRS (block 1010) . For example, the UE (e.g., using communication manager 140 and/or reception component 1202, depicted in Fig. 12) may receive, from a network node, an indication for triggering a TDCP report associated with a TRS, as described above.

As further shown in Fig. 10, in some aspects, process 1000 may include selecting whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS (block 1020) . For example, the UE (e.g., using communication manager 140 and/or selection component 1210, depicted in Fig. 12) may select whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS, as described above.

As further shown in Fig. 10, in some aspects, process 1000 may include transmitting, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS (block 1030) . For example, the UE (e.g., using communication manager 140 and/or transmission component 1204, depicted in Fig. 12) may transmit, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS, as described above.

Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, process 1000 includes transmitting, to the network node, capability information indicating a capability of the UE for reporting the one or more TDCP parameters not based on the TRS.

In a second aspect, alone or in combination with the first aspect, the TDCP report includes an indication of whether the TDCP report includes the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.

In a third aspect, alone or in combination with one or more of the first and second aspects, transmitting the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS includes transmitting the TDCP report including the one or more TDCP parameters not based on the TRS.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the one or more TDCP parameters not based on the TRS are based at least in part on measurements of one or more sensors associated with the UE.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the one or more TDCP parameters not based on the TRS include at least one of a Doppler shift, a Doppler spread, a cross-correlation in time, CSI-RS resource configuration assistance information, or CSI reporting configuration assistance information.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, selecting whether to report, in the TDCP report, the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS includes selecting to report the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, selecting whether to report, in the TDCP report, the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS includes selecting to report the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion or half-TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.

Although Fig. 10 shows example blocks of process 1000, in some aspects, process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

Fig. 11 is a diagram illustrating an example process 1100 performed, for example, by a network node, in accordance with the present disclosure. Example process 1100 is an example where the network node (e.g., network node 110) performs operations associated with TRS-based reporting with UE flexibility.

As shown in Fig. 11, in some aspects, process 1100 may include transmitting, to a UE, an indication for triggering a TDCP report associated with a TRS (block 1110) . For example, the network node (e.g., using communication manager 150 and/or transmission component 1304, depicted in Fig. 13) may transmit, to a UE, an indication for triggering a TDCP report associated with a TRS, as described above.

As further shown in Fig. 11, in some aspects, process 1100 may include receiving, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS (block 1120) . For example, the network node (e.g., using communication manager 150 and/or reception component 1302, depicted in Fig. 13) may receive, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS, as described above.

Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, process 1100 includes receiving, from the UE, capability information indicating a capability of the UE for reporting the one or more TDCP parameters not based on the TRS.

In a third aspect, alone or in combination with one or more of the first and second aspects, receiving the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS includes receiving the TDCP report including the one or more TDCP parameters not based on the TRS.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, receiving the TDCP report including the one or more TDCP parameters not based on the TRS includes receiving the TDCP report including the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, receiving the TDCP report including the one or more TDCP parameters not based on the TRS includes receiving the TDCP report including the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion or half-TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.

Although Fig. 11 shows example blocks of process 1100, in some aspects, process 1100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 11. Additionally, or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

Fig. 12 is a diagram of an example apparatus 1200 for wireless communication, in accordance with the present disclosure. The apparatus 1200 may be a UE, or a UE may include the apparatus 1200. In some aspects, the apparatus 1200 includes a reception component 1202 and a transmission component 1204, which may be in communication with one another (for example, via one or more buses and/or one or more other components) . As shown, the apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using the reception component 1202 and the transmission component 1204. As further shown, the apparatus 1200 may include the communication manager 140. The communication manager 140 may include one or more of a measurement component 1208 and/or a selection component 1210, among other examples.

In some aspects, the apparatus 1200 may be configured to perform one or more operations described herein in connection with Figs. 6A-6C and 7. Additionally, or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as process 800 of Fig. 8, process 1000 of Fig. 10, or a combination thereof. In some aspects, the apparatus 1200 and/or one or more components shown in Fig. 12 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 12 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of 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 executable by a controller or a processor to perform the functions or operations of the component.

The reception component 1202 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1206. The reception component 1202 may provide received communications to one or more other components of the apparatus 1200. In some aspects, the reception component 1202 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 1200. In some aspects, the reception component 1202 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.

The transmission component 1204 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1206. In some aspects, one or more other components of the apparatus 1200 may generate communications and may provide the generated communications to the transmission component 1204 for transmission to the apparatus 1206. In some aspects, the transmission component 1204 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1206. In some aspects, the transmission component 1204 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 1204 may be co-located with the reception component 1202 in a transceiver.

The reception component 1202 may receive, from a network node, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold. The transmission component 1204 may transmit, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.

The measurement component 1208 may measure one or more TDCP measurements based at least in part on the one or more transmissions of the TRS in the one or more measured TRS occasions.

The reception component 1202 may receive, from a network node, an indication for triggering a TDCP report associated with a TRS. The selection component 1210 may select whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS. The transmission component 1204 may transmit, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.

The transmission component 1204 may transmit, to the network node, capability information indicating a capability of the UE for reporting the one or more TDCP parameters not based on the TRS.

The number and arrangement of components shown in Fig. 12 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 12. Furthermore, two or more components shown in Fig. 12 may be implemented within a single component, or a single component shown in Fig. 12 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 12 may perform one or more functions described as being performed by another set of components shown in Fig. 12.

Fig. 13 is a diagram of an example apparatus 1300 for wireless communication, in accordance with the present disclosure. The apparatus 1300 may be a network node, or a network node may include the apparatus 1300. In some aspects, the apparatus 1300 includes a reception component 1302 and a transmission component 1304, which may be in communication with one another (for example, via one or more buses and/or one or more other components) . As shown, the apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using the reception component 1302 and the transmission component 1304. As further shown, the apparatus 1300 may include the communication manager 150. The communication manager 150 may include a determination component 1308, among other examples.

In some aspects, the apparatus 1300 may be configured to perform one or more operations described herein in connection with Figs. 6A-6C and 7. Additionally, or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as process 900 of Fig. 9, process 1100 of Fig. 11, or a combination thereof. In some aspects, the apparatus 1300 and/or one or more components shown in Fig. 13 may include one or more components of the network node described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 13 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of 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 executable by a controller or a processor to perform the functions or operations of the component.

The reception component 1302 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1306. The reception component 1302 may provide received communications to one or more other components of the apparatus 1300. In some aspects, the reception component 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 1300. In some aspects, the reception component 1302 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the network node described in connection with Fig. 2.

The transmission component 1304 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1306. In some aspects, one or more other components of the apparatus 1300 may generate communications and may provide the generated communications to the transmission component 1304 for transmission to the apparatus 1306. In some aspects, the transmission component 1304 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1306. In some aspects, the transmission component 1304 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the network node described in connection with Fig. 2. In some aspects, the transmission component 1304 may be co-located with the reception component 1302 in a transceiver.

The transmission component 1304 may transmit, to a UE, an indication for triggering a TDCP report based at least in part on one or more measured TRS occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold. The reception component 1302 may receive, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.

The determination component 1308 may determine that there is at least one periodic TRS occasion that occurs after the gap threshold from the indication for triggering the TDCP report and no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.

The transmission component 1304 may transmit, to a UE, an indication for triggering a TDCP report associated with a TRS. The reception component 1302 may receive, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS.

The reception component 1302 may receive, from the UE, capability information indicating a capability of the UE for reporting the one or more TDCP parameters not based on the TRS.

The number and arrangement of components shown in Fig. 13 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 13. Furthermore, two or more components shown in Fig. 13 may be implemented within a single component, or a single component shown in Fig. 13 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 13 may perform one or more functions described as being performed by another set of components shown in Fig. 13.

The following provides an overview of some Aspects of the present disclosure:

Aspect 1: A method of wireless communication performed by a user equipment (UE) , comprising: receiving, from a network node, an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and transmitting, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.

Aspect 2: The method of Aspect 1, wherein the one or more measured TRS occasions include one or more periodic TRS occasions configured for the UE.

Aspect 3: The method of Aspect 2, wherein each measured TRS occasion, of the one or more measured TRS occasions, includes four TRS symbols in two consecutive slots, or wherein each measured TRS occasion, of the one or more measured TRS occasions, includes two symbols in a slot.

Aspect 4: The method of any of Aspects 2-3, wherein the one or more measured TRS occasions include one or more of the periodic TRS occasions that occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.

Aspect 5: The method of Aspect 4, wherein transmitting the TDCP report comprises: transmitting the TDCP report based at least in part on a determination that there is at least one of the periodic TRS occasions that occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.

Aspect 6: The method of any of Aspects 1-5, wherein the gap threshold is based at least in part on a subcarrier spacing.

Aspect 7: The method of Aspect 6, wherein the gap threshold is based at least in part on the subcarrier spacing and based at least in part on a capability of the UE.

Aspect 8: The method of any of Aspects 1-7, wherein the one or more measured TRS occasions include a half of a TRS occasion based at least in part on a determination that the half of the TRS occasion occurs after the gap threshold from the indication for triggering the TDCP report and no later than a reference resource based on a slot in which the UE is to transmit the TDCP report.

Aspect 9: The method of Aspect 8, wherein the TRS occasion includes four TRS symbols in two consecutive slots, and wherein the one or more measured TRS occasions include a first slot of the two consecutive slots based at least in part on the first slot occurring after the gap threshold from the indication for triggering the TDCP report.

Aspect 10: The method of Aspect 8, wherein the TRS occasion includes four TRS symbols in two consecutive slots, and wherein the one or more measured TRS occasions include a second slot of the two consecutive slots based at least in part on the second slot occurring after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.

Aspect 11: The method of any of Aspects 1 and 6-10, wherein the one or more measured TRS occasions include one or more measured aperiodic TRS occasions, wherein the time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies the gap threshold, and wherein the one or more measured TRS occasions occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.

Aspect 12: The method of any of Aspects 1-11, further comprising: measuring one or more TDCP measurements based at least in part on the one or more transmissions of the TRS in the one or more measured TRS occasions.

Aspect 13: A method of wireless communication performed by a network node, comprising: transmitting, to a user equipment (UE) , an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and receiving, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.

Aspect 14: The method of Aspect 13, wherein the one or more measured TRS occasions include one or more periodic TRS occasions configured for the UE.

Aspect 15: The method of Aspect 14, wherein each measured TRS occasion, of the one or more measured TRS occasions, includes four TRS symbols in two consecutive slots, or wherein each measured TRS occasion, of the one or more measured TRS occasions, includes two symbols in a slot.

Aspect 16: The method of any of Aspects 14-16, wherein the one or more measured TRS occasions include one or more of the periodic TRS occasions that occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.

Aspect 17: The method of Aspect 16, wherein receiving the TDCP report comprises: receiving the TDCP report based at least in part on a determination that there is at least one of the periodic TRS occasions that occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.

Aspect 18: The method of any of Aspects 13-17, wherein the gap threshold is based at least in part on a subcarrier spacing.

Aspect 19: The method of Aspect 18, wherein the gap threshold is based at least in part on the subcarrier spacing and based at least in part on a capability of the UE.

Aspect 20: The method of any of Aspects 13-19, wherein the one or more measured TRS occasions include a half of a TRS occasion based at least in part on a determination that the half of the TRS occasion occurs after the gap threshold from the indication for triggering the TDCP report and no later than a reference resource based on a slot in which the UE is to transmit the TDCP report.

Aspect 21: The method of Aspect 20, wherein the TRS occasion includes four TRS symbols in two consecutive slots, and wherein the one or more measured TRS occasions include a first slot of the two consecutive slots based at least in part on the first slot occurring after the gap threshold from the indication for triggering the TDCP report.

Aspect 22: The method of Aspect 20, wherein the TRS occasion includes four TRS symbols in two consecutive slots, and wherein the one or more measured TRS occasions include a second slot of the two consecutive slots based at least in part on the second slot occurring after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.

Aspect 23: The method of any of Aspects 13 and 18-22, wherein the one or more measured TRS occasions include one or more measured aperiodic TRS occasions, wherein the time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies the gap threshold, and wherein the one or more measured TRS occasions occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.

Aspect 24: A method of wireless communication performed by a user equipment (UE) , comprising: receiving, from a network node, an indication for triggering a time domain channel property (TDCP) report associated with a tracking reference signal (TRS) ; selecting whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS; and transmitting, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.

Aspect 25: The method of Aspect 24, further comprising: transmitting, to the network node, capability information indicating a capability of the UE for reporting the one or more TDCP parameters not based on the TRS.

Aspect 26: The method of any of Aspects 24-25, wherein the TDCP report includes an indication of whether the TDCP report includes the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.

Aspect 27: The method of any of Aspects 24-26, wherein transmitting the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS comprises: transmitting the TDCP report including the one or more TDCP parameters not based on the TRS.

Aspect 28: The method of Aspect 27, wherein the one or more TDCP parameters not based on the TRS are based at least in part on measurements of one or more sensors associated with the UE.

Aspect 29: The method of Aspect 28, wherein the one or more TDCP parameters not based on the TRS include at least one of a Doppler shift, a Doppler spread, a cross-correlation in time, channel state information (CSI) reference signal (CSI-RS) resource configuration assistance information, or CSI reporting configuration assistance information.

Aspect 30: The method of any of Aspects 27-29, wherein selecting whether to report, in the TDCP report, the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS comprises: selecting to report the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.

Aspect 31: The method of any of Aspects 27-30, wherein selecting whether to report, in the TDCP report, the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS comprises: selecting to report the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion or half-TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.

Aspect 32: A method of wireless communication performed by a network node, comprising: transmitting, to a user equipment (UE) , an indication for triggering a time domain channel property (TDCP) report associated with a tracking reference signal (TRS) ; and receiving, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS.

Aspect 33: The method of Aspect 32, further comprising: receiving, from the UE, capability information indicating a capability of the UE for reporting the one or more TDCP parameters not based on the TRS.

Aspect 34: The method of any of Aspects 32-33, wherein the TDCP report includes an indication of whether the TDCP report includes the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.

Aspect 35: The method of any of Aspects 32-34, wherein receiving the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS comprises: receiving the TDCP report including the one or more TDCP parameters not based on the TRS.

Aspect 36: The method of Aspect 35, wherein the one or more TDCP parameters not based on the TRS are based at least in part on measurements of one or more sensors associated with the UE.

Aspect 37: The method of Aspect 36, wherein the one or more TDCP parameters not based on the TRS include at least one of a Doppler shift, a Doppler spread, a cross-correlation in time, channel state information (CSI) reference signal (CSI-RS) resource configuration assistance information, or CSI reporting configuration assistance information.

Aspect 38: The method of any of Aspects 35-37, wherein receiving the TDCP report including the one or more TDCP parameters not based on the TRS comprises: receiving the TDCP report including the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.

Aspect 39: The method of any of Aspects 35-38, wherein receiving the TDCP report including the one or more TDCP parameters not based on the TRS comprises: receiving the TDCP report including the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion or half-TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.

Aspect 40: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-12.

Aspect 41: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-12.

Aspect 42: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-12.

Aspect 43: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-12.

Aspect 44: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-12.

Aspect 45: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 13-23.

Aspect 46: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 13-23.

Aspect 47: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 13-23.

Aspect 48: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 13-23.

Aspect 49: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 13-23.

Aspect 50: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 24-31.

Aspect 51: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 24-31.

Aspect 52: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 24-31.

Aspect 53: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 24-31.

Aspect 54: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 24-31.

Aspect 55: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 32-39.

Aspect 56: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 32-39.

Aspect 57: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 32-39.

Aspect 58: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 32-39.

Aspect 59: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 32-39.

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 the aspects.

As used herein, the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.

As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

Even though particular combinations of features are recited 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 may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (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, andc + c + c, or any other ordering of a, b, and c) .

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more. ” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more. ” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more. ” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has, ” “have, ” “having, ” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B) . Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or, ” unless explicitly stated otherwise (e.g., ifused in combination with “either” or “only one of” ) .

Claims

A user equipment (UE) for wireless communication, comprising:

a memory; and

one or more processors, coupled to the memory, configured to:

receive, from a network node, an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and

transmit, to the network node, the TDCP report based at least in part on one or more transmissions ofa TRS in the one or more measured TRS occasions.
The UE of claim 1, wherein the one or more measured TRS occasions include one or more periodic TRS occasions configured for the UE.
The UE of claim 2, wherein each measured TRS occasion, of the one or more measured TRS occasions, includes four TRS symbols in two consecutive slots, or wherein each measured TRS occasion, of the one or more measured TRS occasions, includes two symbols in a slot.
The UE of claim 2, wherein the one or more measured TRS occasions include one or more of the periodic TRS occasions that occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.
The UE of claim 4, wherein the one or more processors, to transmit the TDCP report, are configured to:

transmit the TDCP report based at least in part on a determination that there is at least one of the periodic TRS occasions that occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.
The UE of claim 1, wherein the gap threshold is based at least in part on a subcarrier spacing.
The UE of claim 6, wherein the gap threshold is based at least in part on the subcarrier spacing and based at least in part on a capability of the UE.
The UE of claim 1, wherein the one or more measured TRS occasions include a half of a TRS occasion based at least in part on a determination that the half of the TRS occasion occurs after the gap threshold from the indication for triggering the TDCP report and no later than a reference resource based on a slot in which the UE is to transmit the TDCP report.
The UE of claim 8, wherein the TRS occasion includes four TRS symbols in two consecutive slots, and wherein the one or more measured TRS occasions include a first slot of the two consecutive slots based at least in part on the first slot occurring after the gap threshold from the indication for triggering the TDCP report.
The UE of claim 8, wherein the TRS occasion includes four TRS symbols in two consecutive slots, and wherein the one or more measured TRS occasions include a second slot of the two consecutive slots based at least in part on the second slot occurring after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.
The UE of claim 1, wherein the one or more measured TRS occasions include one or more measured aperiodic TRS occasions, wherein the time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies the gap threshold, and wherein the one or more measured TRS occasions occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.
The UE of claim 1, wherein the one or more processors are further configured to:

measure one or more TDCP measurements based at least in part on the one or more transmissions of the TRS in the one or more measured TRS occasions.
A network node for wireless communication, comprising:

a memory; and

one or more processors, coupled to the memory, configured to:

transmit, to a user equipment (UE) , an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and

receive, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.
The network node of claim 13, wherein the one or more measured TRS occasions include one or more periodic TRS occasions configured for the UE.
The network node of claim 14, wherein each measured TRS occasion, of the one or more measured TRS occasions, includes four TRS symbols in two consecutive slots, or wherein each measured TRS occasion, of the one or more measured TRS occasions, includes two symbols in a slot.
The network node of claim 14, wherein the one or more measured TRS occasions include one or more of the periodic TRS occasions that occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.
The network node of claim 16, wherein the one or more processors, to receive the TDCP report, are configured to:

receive the TDCP report based at least in part on a determination that there is at least one of the periodic TRS occasions that occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.
The network node of claim 13, wherein the gap threshold is based at least in part on a subcarrier spacing.
The network node of claim 18, wherein the gap threshold is based at least in part on the subcarrier spacing and based at least in part on a capability of the UE.
The network node of claim 13, wherein the one or more measured TRS occasions include a half of a TRS occasion based at least in part on a determination that the half of the TRS occasion occurs after the gap threshold from the indication for triggering the TDCP report and no later than a reference resource based on a slot in which the UE is to transmit the TDCP report.
The network node of claim 20, wherein the TRS occasion includes four TRS symbols in two consecutive slots, and wherein the one or more measured TRS occasions include a first slot of the two consecutive slots based at least in part on the first slot occurring after the gap threshold from the indication for triggering the TDCP report.
The network node of claim 20, wherein the TRS occasion includes four TRS symbols in two consecutive slots, and wherein the one or more measured TRS occasions include a second slot of the two consecutive slots based at least in part on the second slot occurring after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.
The network node of claim 13, wherein the one or more measured TRS occasions include one or more measured aperiodic TRS occasions, wherein the time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies the gap threshold, and wherein the one or more measured TRS occasions occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.
A user equipment (UE) for wireless communication, comprising:

a memory; and

one or more processors, coupled to the memory, configured to:

receive, from a network node, an indication for triggering a time domain channel property (TDCP) report associated with a tracking reference signal (TRS) ;

select whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS; and

transmit, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.
The UE of claim 24, wherein the one or more processors are further configured to:

transmit, to the network node, capability information indicating a capability of the UE for reporting the one or more TDCP parameters not based on the TRS.
The UE of claim 24, wherein the TDCP report includes an indication of whether the TDCP report includes the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.
The UE of claim 24, wherein the one or more processors, to transmit the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS, are configured to:

transmit the TDCP report including the one or more TDCP parameters not based on the TRS.
The UE of claim 27, wherein the one or more TDCP parameters not based on the TRS are based at least in part on measurements of one or more sensors associated with the UE.
The UE of claim 28, wherein the one or more TDCP parameters not based on the TRS include at least one of a Doppler shift, a Doppler spread, a cross-correlation in time, channel state information (CSI) reference signal (CSI-RS) resource configuration assistance information, or CSI reporting configuration assistance information.
The UE of claim 27, wherein the one or more processors, to select whether to report, in the TDCP report, the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS, are configured to:

select to report the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.
The UE of claim 27, wherein the one or more processors, to select whether to report, in the TDCP report, the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS, are configured to:

select to report the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion or half-TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.
A network node for wireless communication, comprising:

a memory; and

one or more processors, coupled to the memory, configured to:

transmit, to a user equipment (UE) , an indication for triggering a time domain channel property (TDCP) report associated with a tracking reference signal (TRS) ; and

receive, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS.
The network node of claim 32, wherein the one or more processors are further configured to:

receive, from the UE, capability information indicating a capability of the UE for reporting the one or more TDCP parameters not based on the TRS.
The network node of claim 32, wherein the TDCP report includes an indication of whether the TDCP report includes the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.
The network node of claim 32, wherein the one or more processors, to receive the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS, are configured to:

receive the TDCP report including the one or more TDCP parameters not based on the TRS.
The network node of claim 35, wherein the one or more TDCP parameters not based on the TRS are based at least in part on measurements of one or more sensors associated with the UE.
The network node of claim 36, wherein the one or more TDCP parameters not based on the TRS include at least one of a Doppler shift, a Doppler spread, a cross-correlation in time, channel state information (CSI) reference signal (CSI-RS) resource configuration assistance information, or CSI reporting configuration assistance information.
The network node of claim 35, wherein the one or more processors, to receive the TDCP report including the one or more TDCP parameters not based on the TRS, are configured to:

receive the TDCP report including the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.
The network node of claim 35, wherein the one or more processors, to receive the TDCP report including the one or more TDCP parameters not based on the TRS, are configured to:

receive the TDCP report including the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion or half-TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.
A method of wireless communication performed by a user equipment (UE) , comprising:

receiving, from a network node, an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and

transmitting, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.
The method of claim 40, wherein the one or more measured TRS occasions include one or more periodic TRS occasions configured for the UE.
The method of claim 41, wherein each measured TRS occasion, of the one or more measured TRS occasions, includes four TRS symbols in two consecutive slots, or wherein each measured TRS occasion, of the one or more measured TRS occasions, includes two symbols in a slot.
The method of claim 41, wherein the one or more measured TRS occasions include one or more of the periodic TRS occasions that occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.
The method of claim 43, wherein transmitting the TDCP report comprises:

transmitting the TDCP report based at least in part on a determination that there is at least one of the periodic TRS occasions that occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.
The method of claim 40, wherein the gap threshold is based at least in part on a subcarrier spacing.
The method of claim 45, wherein the gap threshold is based at least in part on the subcarrier spacing and based at least in part on a capability of the UE.
The method of claim 40, wherein the one or more measured TRS occasions include a half of a TRS occasion based at least in part on a determination that the half of the TRS occasion occurs after the gap threshold from the indication for triggering the TDCP report and no later than a reference resource based on a slot in which the UE is to transmit the TDCP report.
The method of claim 47, wherein the TRS occasion includes four TRS symbols in two consecutive slots, and wherein the one or more measured TRS occasions include a first slot of the two consecutive slots based at least in part on the first slot occurring after the gap threshold from the indication for triggering the TDCP report.
The method of claim 47, wherein the TRS occasion includes four TRS symbols in two consecutive slots, and wherein the one or more measured TRS occasions include a second slot of the two consecutive slots based at least in part on the second slot occurring after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.
The method of claim 40, wherein the one or more measured TRS occasions include one or more measured aperiodic TRS occasions, wherein the time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies the gap threshold, and wherein the one or more measured TRS occasions occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.
The method of claim 40, further comprising:

measuring one or more TDCP measurements based at least in part on the one or more transmissions of the TRS in the one or more measured TRS occasions.
A method of wireless communication performed by a network node, comprising:

transmitting, to a user equipment (UE) , an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and

receiving, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.
The method of claim 52, wherein the one or more measured TRS occasions include one or more periodic TRS occasions configured for the UE.
The method of claim 53, wherein each measured TRS occasion, of the one or more measured TRS occasions, includes four TRS symbols in two consecutive slots, or wherein each measured TRS occasion, of the one or more measured TRS occasions, includes two symbols in a slot.
The method of claim 53, wherein the one or more measured TRS occasions include one or more of the periodic TRS occasions that occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.
The method of claim 55, wherein receiving the TDCP report comprises:

receiving the TDCP report based at least in part on a determination that there is at least one of the periodic TRS occasions that occurs after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.
The method of claim 52, wherein the gap threshold is based at least in part on a subcarrier spacing.
The method of claim 57, wherein the gap threshold is based at least in part on the subcarrier spacing and based at least in part on a capability of the UE.
The method of claim 52, wherein the one or more measured TRS occasions include a half of a TRS occasion based at least in part on a determination that the half of the TRS occasion occurs after the gap threshold from the indication for triggering the TDCP report and no later than a reference resource based on a slot in which the UE is to transmit the TDCP report.
The method of claim 59, wherein the TRS occasion includes four TRS symbols in two consecutive slots, and wherein the one or more measured TRS occasions include a first slot of the two consecutive slots based at least in part on the first slot occurring after the gap threshold from the indication for triggering the TDCP report.
The method of claim 59, wherein the TRS occasion includes four TRS symbols in two consecutive slots, and wherein the one or more measured TRS occasions include a second slot of the two consecutive slots based at least in part on the second slot occurring after the gap threshold from the indication for triggering the TDCP report and no later than the reference resource.
The method of claim 52, wherein the one or more measured TRS occasions include one or more measured aperiodic TRS occasions, wherein the time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies the gap threshold, and wherein the one or more measured TRS occasions occur no later than a reference resource based at least in part on a slot in which the UE is to transmit the TDCP report.
A method of wireless communication performed by a user equipment (UE) , comprising:

receiving, from a network node, an indication for triggering a time domain channel property (TDCP) report associated with a tracking reference signal (TRS) ;

selecting whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS; and

transmitting, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.
The method of claim 63, further comprising:

transmitting, to the network node, capability information indicating a capability of the UE for reporting the one or more TDCP parameters not based on the TRS.
The method of claim 63, wherein the TDCP report includes an indication of whether the TDCP report includes the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.
The method of claim 63, wherein transmitting the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS comprises:

transmitting the TDCP report including the one or more TDCP parameters not based on the TRS.
The method of claim 66, wherein the one or more TDCP parameters not based on the TRS are based at least in part on measurements of one or more sensors associated with the UE.
The method of claim 67, wherein the one or more TDCP parameters not based on the TRS include at least one of a Doppler shift, a Doppler spread, a cross-correlation in time, channel state information (CSI) reference signal (CSI-RS) resource configuration assistance information, or CSI reporting configuration assistance information.
The method of claim 66, wherein selecting whether to report, in the TDCP report, the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS comprises:

selecting to report the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.
The method of claim 66, wherein selecting whether to report, in the TDCP report, the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS comprises:

selecting to report the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion or half-TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.
A method of wireless communication performed by a network node, comprising:

transmitting, to a user equipment (UE) , an indication for triggering a time domain channel property (TDCP) report associated with a tracking reference signal (TRS) ; and

receiving, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS.
The method of claim 71, further comprising:

receiving, from the UE, capability information indicating a capability of the UE for reporting the one or more TDCP parameters not based on the TRS.
The method of claim 71, wherein the TDCP report includes an indication of whether the TDCP report includes the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.
The method of claim 71, wherein receiving the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS comprises:

receiving the TDCP report including the one or more TDCP parameters not based on the TRS.
The method of claim 74, wherein the one or more TDCP parameters not based on the TRS are based at least in part on measurements of one or more sensors associated with the UE.
The method of claim 75, wherein the one or more TDCP parameters not based on the TRS include at least one of a Doppler shift, a Doppler spread, a cross-correlation in time, channel state information (CSI) reference signal (CSI-RS) resource configuration assistance information, or CSI reporting configuration assistance information.
The method of claim 74, wherein receiving the TDCP report including the one or more TDCP parameters not based on the TRS comprises:

receiving the TDCP report including the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.
The method of claim 74, wherein receiving the TDCP report including the one or more TDCP parameters not based on the TRS comprises:

receiving the TDCP report including the one or more TDCP parameters not based on the TRS based at least in part on a determination that there is no TRS occasion or half-TRS occasion that occurs after a gap threshold from the indication that triggers the TDCP report and no later than a reference resource based on a slot in which the TDCP report is to be transmitted by the UE.
A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a user equipment (UE) , cause the UE to:

receive, from a network node, an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and

transmit, to the network node, the TDCP report based at least in part on one or more transmissions ofa TRS in the one or more measured TRS occasions.
A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a network node, cause the network node to:

transmit, to a user equipment (UE) , an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and

receive, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.
A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a user equipment (UE) , cause the UE to:

receive, from a network node, an indication for triggering a time domain channel property (TDCP) report associated with a tracking reference signal (TRS) ;

select whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS; and

transmit, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.
A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a network node, cause the network node to:

transmit, to a user equipment (UE) , an indication for triggering a time domain channel property (TDCP) report associated with a tracking reference signal (TRS) ; and

receive, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS.
An apparatus for wireless communication, comprising:

means for receiving, from a network node, an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and

means for transmitting, to the network node, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.
An apparatus for wireless communication, comprising:

means for transmitting, to a user equipment (UE) , an indication for triggering a time domain channel property (TDCP) report based at least in part on one or more measured tracking reference signal (TRS) occasions, wherein a time gap between the indication for triggering the TDCP report and the one or more measured TRS occasions satisfies a gap threshold; and

means for receiving, from the UE, the TDCP report based at least in part on one or more transmissions of a TRS in the one or more measured TRS occasions.
An apparatus for wireless communication, comprising:

means for receiving, from a network node, an indication for triggering a time domain channel property (TDCP) report associated with a tracking reference signal (TRS) ;

means for selecting whether to report, in the TDCP report, one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS; and

means for transmitting, to the network node, the TDCP report including the one or more TDCP parameters based on the TRS or the one or more TDCP parameters not based on the TRS.
An apparatus for wireless communication, comprising:

means for transmitting, to a user equipment (UE) , an indication for triggering a time domain channel property (TDCP) report associated with a tracking reference signal (TRS) ; and

means for receiving, from the UE, the TDCP report including one or more TDCP parameters based on the TRS or one or more TDCP parameters not based on the TRS.