Overhead reduction for channel correlation reporting

Abstract

The UE (102) receives (508) a configuration for the measurement report from the network entity (104). The measurement report corresponds to at least one of: a TDCC report using the configured quantization parameter, a Doppler spread report, or a Doppler frequency shift report, each report based on a measurement of one or more TRSs. The UE (102) receives (350) one or more TRSs from the network entity (104) and further receives (516) control signaling that triggers a configuration for the measurement report. The UE (102) sends (520) a measurement report to the network entity (104) in response to receiving (516, 350) the control signaling and the one or more TRSs. The measurement report is generated based on the configuration.

Description

Technical Field

[0001] The present disclosure generally relates to wireless communications and, more particularly, to reducing the overhead of time-domain channel correlation (TDCC) reporting and / or Doppler spread / frequency shift reporting. Background Art

[0002] The Third Generation Partnership Project (3GPP) has specified a radio interface called the fifth-generation (5G) new radio (NR) (5G NR). The architecture of a 5G NR wireless communication system may include a 5G core (5GC) network, a 5G radio access network (5G-RAN), user equipment (UE), etc. Compared with other types of wireless communication systems, the 5G NR architecture is designed to provide increased data rates, reduced latency, and / or increased capacity.

[0003] A wireless communication system is generally configured to provide various telecommunication services (such as, telephone, video, data, messaging, broadcasting, etc.) based on any one of multiple access technologies that support communication with multiple UEs (such as, orthogonal frequency division multiple access (OFDMA) technology). Improvements in mobile broadband have been useful for the continuous development of such wireless communication technologies. For example, the movement of a UE relative to a base station may cause the channel between the UE and the base station to change. However, reporting the channel correlation of a channel that may have an increased number of delays results in high reporting overhead. Summary of the Invention

[0004] A simplified overview of one or more aspects is presented below in order to provide a basic understanding of such aspects. This overview is not an extensive review of all contemplated aspects. This overview neither identifies key or important elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0005] Relative movement between communication entities (such as, a base station and a UE) causes the wireless channel used for communication to change. A UE may report information about the state of such a communication channel between the UE and the base station to the base station. For example, the UE sends a TDCC report to a network entity (such as, a base station or a radio unit (RU) of the base station) based on one or more tracking reference signals (TRS) received from the network entity. Thus, enabling the network entity to calculate the Doppler spread / frequency shift based on the channel change indicated in the TDCC report. In some examples, the UE performs an equivalent calculation and sends the value of the Doppler spread / frequency shift to the network entity. Since the channel correlation may be different at different delays, the channel correlation for multiple delays must be reported. The repeated reporting results in high reporting overhead.

[0006] The methods and apparatuses described below address the above and other deficiencies by using quantization techniques and / or compression techniques implemented at the UE for beam measurement and reporting procedures, which reduce the overhead associated with multiple reports of channel correlation due to different delays. A network entity may send downlink control signaling indicating a set of quantization parameters for TDCC reporting to the UE, or the UE may independently determine a set of quantization parameters for TDCC reporting. The TDCC report (e.g., a quantized TDCC report) is formatted to reduce reporting overhead, thereby improving the system performance of wireless communication between the network entity and the UE.

[0007] According to some aspects, the UE receives a configuration for a measurement report from a network entity. The measurement report corresponds to at least one of the following: a TDCC report using configured quantization parameters, a Doppler spread report, or a Doppler shift report, each report being based on measurements of one or more TRSs. The UE receives one or more TRSs from the network entity and further receives control signaling from the network entity that triggers the application of the configuration for the measurement report. The UE sends the measurement report to the network entity in response to receiving the control signaling and the one or more TRSs. The UE generates the measurement report according to the received configuration.

[0008] According to some aspects, the network entity sends the configuration for the measurement report to the UE as described above. After the network entity sends one or more TRSs and control signaling that triggers the application of the configuration for generating the measurement report to the UE, the network entity receives the measurement report from the UE according to the configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A diagram showing a wireless communication system including multiple UEs and a network entity communicating via one or more cells.

[0010] Figure 2 A diagram showing an example time slot structure of a tracking reference signal (TRS).

[0011] Figure 3 A signaling diagram showing a TDCC report based on each TRS.

[0012] Figure 4 A signaling diagram showing a cross-TRS TDCC reporting procedure for multiple TRSs.

[0013] Figure 5 A signaling diagram showing a reporting content selection procedure.

[0014] Figure 6 A flowchart of a method of wireless communication at the UE.

[0015] Figure 7Flowchart of a method of wireless communication at a network entity.

[0016] Figure 8 Diagram showing a hardware implementation of an example UE apparatus.

[0017] Figure 9 Diagram showing a hardware implementation of one or more example network entities. Detailed implementation

[0018] Figure 1 Diagram showing a wireless communication system 100 associated with a plurality of 190 cells 190a - e. The wireless communication system includes UEs 102a - d and base stations 104a - c, where some base stations (e.g., 104c) include an aggregated base station architecture, while other base stations (e.g., 104a - 104b) include a disaggregated base station architecture. The aggregated base station architecture includes a radio unit (RU) 106, a distributed unit (DU) 108, and a central unit (CU) 110, which are configured to utilize a radio protocol stack physically or logically integrated within a single radio access network (RAN) node. The disaggregated base station architecture utilizes a protocol stack physically or logically distributed between two or more units (e.g., RU 106, DU 108, CU 110). For example, CU 110 is implemented within a RAN node, and one or more DUs 108 can be collocated with CU 110, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. DU 108 can be implemented to communicate with one or more RUs 106. Each of RU 106, DU 108, and CU 110 can be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). The base station 104 and / or units of the base station 104 such as RU 106, DU 108, or CU 110 can be referred to as transmission and reception points (TRPs).

[0019] The operation and / or network design of base station 104 can be based on the aggregated characteristics of base station functions. For example, in an integrated access backhaul (IAB) network, an open radio access network (O-RAN) network, or a virtualized radio access network (vRAN) (which may also be referred to as a cloud radio access network (C-RAN)), a decomposed base station architecture is utilized. The decomposition can include distributing functions between two or more units located at various physical locations, as well as virtually distributing the functions of at least one unit, which can achieve flexibility in network design. The various units of the decomposed base station architecture or the decomposed RAN architecture can be configured to communicate with at least one other unit either wired or wirelessly. For example, CU 110a communicates with DUs 108a - 108b via respective midhaul links 162 based on the F1 interface. DUs 108a - 108b can communicate with RUs 106a and RUs 106b - 106c via respective fronthaul links 160, respectively. RUs 106a - 106c can communicate with respective UEs 102a - 102c and 102s via one or more radio frequency (RF) access links based on the Uu interface. In an example, multiple RUs 106 and / or base stations 104 can serve UEs 102 simultaneously. For example, the access link of RU 106a in cell 190a and base station 104c in cell 190e simultaneously serve UE 102a in cell 190a.

[0020] One or more CUs 110 (such as CU 110a or CU 110d) can communicate directly with core network 120 via backhaul link 164. For example, CU 110d communicates with core network 120 via backhaul link 164 based on the next generation (NG) interface. One or more CUs 110 can also communicate indirectly with core network 120 through one or more decomposed base station units, such as a near-real-time RAN intelligent controller (RIC) 128 via an E2 link and a service management and orchestration (SMO) framework 116 that can be associated with a non-real-time RIC 118. The near-real-time RIC 128 may communicate with the SMO framework 116 and / or the non-real-time RIC 118 via an A1 link. The SMO framework 116 and / or the non-real-time RIC 118 may also communicate with an open cloud (O-cloud) 130 via an O2 link. One or more CUs 110 can further communicate with each other via backhaul link 164 based on the Xn interface. For example, CU 110d of base station 104c communicates with CU 110a of base station 104b via backhaul link 164 based on the Xn interface. Similarly, base station 104c in cell 190e can communicate with CU 110a of base station 104b via backhaul link 164 based on the Xn interface.

[0021] RU 106, DU 108, and CU 110, as well as the near-real-time RIC 128, non-real-time RIC 118, and / or SMO framework 116 may include (or may be coupled to) one or more interfaces configured to send or receive information / signals via a wired or wireless transmission medium. The base station 104 or any one of the one or more decomposed base station units may be configured to communicate with one or more other base stations 104 or one or more other decomposed base station units via a wired or wireless transmission medium. In an example, a processor, memory, and / or controller associated with the executable instructions of the interface may be configured to provide communication between the base station 104 and / or one or more decomposed base station units via a wired or wireless transmission medium. For example, a wired interface may be configured to send or receive information / signals via a wired transmission medium, such as the fronthaul link 160 between the RU 106d for cell 190d and the baseband unit (BBU) 112, or more specifically, the fronthaul link 160 between the RU 106d and the DU 108d. The BBU 112 includes the DU 108d and CU 110d, which may also have a wired interface configured between the DU 108d and the CU 110d to send or receive information / signals between the DU 108d and the CU 110d based on the midhaul link 162. In a further example, a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) may be configured to send or receive information / signals via a wireless transmission medium, such as the information transmitted between the RU 106a in cell 190a and the base station 104c in cell 190e via the cross-cell communication beam of the RU 106a and the base station 104c.

[0022] One or more high-level control functions (such as functions related to radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc.) may be hosted at the CU 110. Each control function may be associated with an interface for transmitting signals based on one or more other control functions hosted at the CU 110. A user plane function (such as a central unit-user plane (CU-UP) function), a control plane function (such as a central unit-control plane (CU-CP) function), or a combination thereof may be implemented based on the CU 110. For example, the CU 110 may include a logical division between one or more CU-UP processes and / or one or more CU-CP processes. When implemented in an O-RAN configuration, the CU-UP function may be based on two-way communication with the CU-CP function via an interface (such as the E1 interface (not shown)).

[0023] CU 110 can communicate with DU 108 for network control and signal transmission. DU 108 is a logical unit of base station 104, which is configured to perform one or more base station functions. For example, DU 108 can control the operation of one or more RUs 106. One or more of the following can be hosted at DU 108: Radio Link Control (RLC) layer, Media Access Control (MAC) layer, or one or more higher Physical (PHY) layers, such as Forward Error Correction (FEC) modules for encoding / decoding, scrambling, modulation / demodulation, etc. DU 108 can host such functions based on the functional partitioning of DU 108. DU 108 can similarly host one or more lower PHY layers, where each lower layer or module can be implemented based on an interface for communicating with other layers and modules hosted at DU 108, or based on control functions hosted at CU 110.

[0024] RU 106 can be configured to implement lower layer functions. For example, RU 106 is controlled by DU 108 and can correspond to a logical node hosting RF processing functions or lower layer PHY functions, such as performing Fast Fourier Transform (FFT), inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc. The functions of RU 106 can be based on functional partitioning, such as the functional partitioning of the lower layer.

[0025] RU 106 can send or receive over-the-air (OTA) communications with one or more UEs 102. For example, RU 106b in cell 190b communicates with UE 102b in cell 190b via the first communication beam set 132 of RU 106b and the second communication beam set 134b of UE 102b, and these two communication beam sets can correspond to inter-cell communication beams or cross-cell communication beams. For example, UE 102b in cell 190b can communicate with RU 106a in cell 190a via the third communication beam set 134a of UE 102b and the RU beam set 136 of RU 106a. Both the real-time and non-real-time characteristics of the control plane and user plane communications of RU 106 can be controlled by the associated DU 108. Thus, DU 108 and CU 110 can be used in a cloud-based RAN architecture (such as a vRAN architecture), while the SMO framework 116 can be used to support non-virtualized and virtualized RAN network elements. For non-virtualized network elements, the SMO framework 116 can support the deployment of dedicated physical resources for RAN coverage, where the dedicated physical resources can be managed through an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 116 can interact with a cloud computing platform (such as O-Cloud 130) via an O2 link (e.g., a cloud computing platform interface) to manage the network elements. Virtualized network elements can include, but are not limited to, RU 106, DU 108, CU 110, near-real-time RIC 128, etc.

[0026] The SMO framework 116 can be configured to communicate directly with one or more RUs 106 using the O1 link. The non-real-time RIC 118 of the SMO framework 116 can also be configured to support the functions of the SMO framework 116. For example, the non-real-time RIC 118 implements logical functions that can control non-real-time RAN characteristics and resources, the characteristics / applications of the near-real-time RIC 128, and / or artificial intelligence / machine learning (AI / ML) processes. The non-real-time RIC 118 can communicate (or be coupled) with the near-real-time RIC 128, such as via the A1 interface. The near-real-time RIC 128 can implement logical functions that can control near-real-time RAN characteristics and resources based on data collection and interaction through an E2 interface (such as the E2 interface between the near-real-time RIC 128 and CU 110a and DU 108b).

[0027] The non-real-time RIC 118 can receive parameters or other information from an external server to generate an AI / ML model for deployment in the near-real-time RIC 128. For example, the non-real-time RIC 118 receives parameters or other information from the O-Cloud 130 via the O2 link to deploy the AI / ML model to the real-time RIC 128 via the A1 link. The near-real-time RIC 128 can utilize the parameters and / or other information received from the non-real-time RIC 118 or the SMO framework 116 via the A1 link to perform near-real-time functions. The near-real-time RIC 128 and the non-real-time RIC 118 can be configured to adjust the performance of the RAN. For example, the non-real-time RIC 116 monitors patterns and long-term trends to improve the performance of the RAN. The non-real-time RIC 116 can also deploy AI / ML models via the SMO framework 116 for implementing corrective actions, such as initiating reconfiguration of the O1 link or instructing the management process of the A1 link.

[0028] Any combination of the RU 106, DU 108, and CU 110 or a separate reference to each of them can correspond to the base station 104. Thus, the base station 104 can include at least one of the RU 106, DU 108, or CU 110. The base station 104 provides access to the core network 120 for the UE 102. That is, the base station 104 may relay the communication between the UE 102 and the core network 120. The base station 104 can be associated with a macro cell of a high-power cellular base station and / or a small cell of a low-power cellular base station. For example, the cell 190e corresponds to a macro cell, while the cells 190a - 190d can correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A cell structure including at least one macro cell and at least one small cell can be referred to as a "heterogeneous network".

[0029] The transmission from the UE 102 to the base station 104 / RU 106 is referred to as an uplink (UL) transmission, while the transmission from the base station 104 / RU 106 to the UE 102 is referred to as a downlink (DL) transmission. The uplink transmission can also be referred to as a reverse link transmission, and the downlink transmission can also be referred to as a forward link transmission. For example, the RU 106d uses the antennas of the base station 104c of the cell 190d to send downlink / forward link communication to the UE 102d or receive uplink / reverse link communication from the UE 102d based on the Uu interface associated with the access link between the UE 102d and the base station 104c / RU 106d.

[0030] The communication link between the UE 102 and the base station 104 / RU 106 can be based on multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be associated with one or more carriers. The UE 102 and the base station 104 / RU 106 can utilize a spectral bandwidth of Y MHz per carrier (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.) allocated in carrier aggregation of up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink direction and the downlink direction. The carriers can be adjacent to each other along the spectrum or can be non-adjacent to each other. In an example, the uplink carriers and the downlink carriers can be allocated in an asymmetric manner, and more or fewer carriers can be allocated for the uplink or the downlink. The component carriers can include a primary component carrier and one or more secondary component carriers. The primary component carrier can be associated with a primary cell (PCell), and the secondary component carriers can be associated with secondary cells (SCells).

[0031] Some UEs 102 (such as UEs 102a and 102s) can perform device-to-device (D2D) communication via a sidelink. For example, the sidelink communication / D2D link utilizes the spectrum of the wireless wide area network (WWAN) associated with the uplink communication and the downlink communication. The sidelink communication / D2D link can also use one or more sidelink channels, such as the physical sidelink broadcast channel (PSBCH), the physical sidelink discovery channel (PSDCH), the physical sidelink shared channel (PSSCH), and / or the physical sidelink control channel (PSCCH), to transmit information between the UEs 102a and 102s. Such sidelink / D2D communication can be performed via various wireless communication systems, such as a wireless fidelity (Wi-Fi) system, a Bluetooth system, a long term evolution (LTE) system, a new radio (NR) system, etc.

[0032] The electromagnetic spectrum is typically subdivided into different categories, frequency bands, channels, etc. based on the different frequencies / wavelengths associated with the electromagnetic spectrum. Fifth-generation (5G) NR is typically associated with two operating frequency ranges (FRs) called Frequency Range 1 (FR1) and Frequency Range 2 (FR2). The FR1 ranges from 410 MHz - 7.125 GHz, and the FR2 ranges from 24.25 GHz - 71.0 GHz, with the FR2 including FR2-1 (24.25 GHz - 52.6 GHz) and FR2-2 (52.6 GHz - 71.0 GHz). Although a part of FR1 is actually greater than 6 GHz, FR1 is typically referred to as the "sub-6 GHz" frequency band. In contrast, FR2 is typically referred to as the "millimeter wave" (mmW) frequency band. FR2 is different from the "extremely high frequency" (EHF) band, but is an approximate subset of this band, with the EHF band ranging from 30 GHz - 300 GHz and sometimes also being referred to as the "millimeter wave" band. The frequencies between FR1 and FR2 are typically referred to as "mid-band" frequencies. The operating frequency band of mid-band frequencies can be called Frequency Range 3 (FR3), which ranges from 7.125 GHz - 24.25 GHz. The frequency bands within FR3 can include characteristics of FR1 and / or FR2. Thus, the characteristics of FR1 and / or FR2 can extend to mid-band frequencies. Higher operating frequency bands have been identified to extend 5G NR communication beyond 52.6 GHz associated with the upper limit of FR2. Three of these higher operating frequency bands include FR2-2 ranging from 52.6 GHz - 71.0 GHz, FR4 ranging from 71.0 GHz - 114.25 GHz, and FR5 ranging from 114.25 GHz - 300 GHz. The upper limit of FR5 corresponds to the upper limit of the EHF band. Thus, unless otherwise explicitly stated herein, the term "sub-6 GHz" can refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that can include mid-band frequencies. Further, unless otherwise explicitly stated herein, the term "millimeter wave" or mmW refers to frequencies that can include mid-band frequencies, frequencies that can be within FR2-1, FR4, FR2-2, and / or FR5, or frequencies that can be within the EHF band.

[0033] UE 102 and base station 104 / RU 106 may each include multiple antennas. The multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that may facilitate beamforming operations. For example, RU 106b transmits a downlink beamformed signal to UE 102b based on a first beam set 132 in one or more transmission directions of RU 106b. UE 102b may receive the downlink beamformed signal from RU 106b based on a second beam set 134b in one or more reception directions of UE 102b. In a further example, UE 102b may also transmit an uplink beamformed signal to RU 106b based on a second beam set 134b in one or more transmission directions of UE 102b. RU 106b may receive the uplink beamformed signal from UE 102b in one or more reception directions of RU 106b. UE 102b may perform beam training to determine the optimal reception and transmission directions for the beamformed signals. The transmission and reception directions of UE 102 and base station 104 / RU 106 may be the same or may be different. In a further example, the beamformed signals may be transmitted between a first base station 104c and a second base station 104b. For example, RU 106a of cell 190a may transmit a beamformed signal to base station 104c of cell 190e based on an RU beam set 136 in one or more transmission directions of RU 106a. Base station 104c of cell 190e may receive the beamformed signal from RU 106a based on a base station beam set 138 in one or more reception directions of base station 104c. Similarly, base station 104c of cell 190e may transmit a beamformed signal to RU 106a based on a base station beam set 138 in one or more transmission directions of base station 104c. RU 106a may receive the beamformed signal from base station 104c of cell 190e based on an RU beam set 136 in one or more reception directions of RU 106a.

[0034] Base station 104 may include and / or be referred to as a network entity. That is, a "network entity" may refer to base station 104 or at least one unit of base station 104, such as RU 106, DU 108, and / or CU 110. Base station 104 may also include and / or be referred to as a next-generation evolved Node B (ng-eNB), a generation NB (gNB), an evolved NB (eNB), an access point, a base station transceiver, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network device, or other related terms. The base station 104 or an entity at the base station 104 may be implemented as an IAB node, a relay node, a sidelink node, an aggregated (monolithic) base station having an RU 106 and a BBU including a DU 108 and a CU 110, or may be implemented as a disaggregated base station 104b including one or more of RU 106, DU 108, and / or CU 110. A set of aggregated or disaggregated base stations 104a-104b may be referred to as a next-generation radio access network (NG-RAN). In some examples, UE 102b operates in dual connectivity (DC) with base station 104a and base station 104b. In this case, base station 104a may be the master node, while base station 104b may be the secondary node. In other examples, UE 102b operates in DC with DU 108a and DU 108b. In this case, DU 108a may be the master node, while DU 108b may be the secondary node.

[0035] Core network 120 may include an access and mobility management function (AMF) 121, a session management function (SMF) 122, a user plane function (UPF) 123, a unified data management (UDM) 124, a gateway mobile location center (GMLC) 125, and / or a location management function (LMF) 126. Core network 120 may also include one or more location servers (which may include GMLC 125 and LMF 126), as well as other functional entities. For example, one or more location servers include one or more location / locationing servers, and in addition to one or more of a positioning determination entity (PDE), a serving mobile location center (SMLC), a mobile location center (MPC), etc., one or more location / locationing servers may also include GMLC 125 and LMF 126.

[0036] The AMF 121 is a control node that processes signal transmission between the UE 102 and the core network 120. The AMF 121 supports registration management, connection management, mobility management, and other functions. The SMF 122 supports session management and other functions. The UPF 123 supports packet routing, packet forwarding, and other functions. The UDM 124 supports generating Authentication and Key Agreement (AKA) credentials, user identity handling, access authorization, and subscription management. The GMLC 125 provides an interface for clients / applications (such as emergency services) to access UE location information. The LMF 126 receives measurement and assistance information from the NG-RAN and the UE 102 via the AMF 121 to calculate the location of the UE 102. The NG-RAN can utilize one or more positioning methods to determine the location of the UE 102. Positioning the UE 102 can involve signal measurement, position estimation, and optional speed calculation based on the measurement. The signal measurement can be performed by the UE 102 and / or the serving base station 104 / RU 106.

[0037] The transmitted signals can also be based on one or more of the Satellite Positioning Systems (SPSs) 114, such as signals measured for positioning. In an example, the SPS 114 of cell 190c can communicate with one or more UEs 102 (such as UE 102c) and one or more base stations 104 / RUs 106 (such as RU 106c). The SPS 114 can correspond to one or more of the Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN), or other satellite positioning / location systems. The SPS 114 can be associated with LTE signals, NR signals (e.g., based on Round-Trip Time (RTT) and / or multi-RTT), Wireless Local Area Network (WLAN) signals, Terrestrial Beacon System (TBS), sensor-based information, NR Enhanced Cell ID (NR E-CID) technology, Downlink Angle of Departure (DL-AoD), Downlink Time Difference of Arrival (DL-TDOA), Uplink Time Difference of Arrival (UL-TDOA), Uplink Angle of Arrival (UL-AoA), and / or other systems, signals, or sensors.

[0038] The UE 102 may be configured as a cellular phone, smartphone, Session Initiation Protocol (SIP) phone, laptop computer, personal digital assistant (PDA), satellite radio, GPS, multimedia device, video device, digital audio player (e.g., Moving Picture Experts Group (MPEG) Audio Layer 3 (MP3) player), camera, game console, tablet computer, smart device, wearable device, vehicle, utility meter, gas pump, home appliance, healthcare device, sensor / actuator, display, or any other device with similar functionality. Some of the UEs 102 may be referred to as Internet of Things (IoT) devices, such as parking meters, gas pumps, home appliances, vehicles, healthcare equipment, etc. The UE 102 may also be referred to as a station (STA), mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, mobile client, client, or other similar terms. The term UE may also apply to a roadside unit (RSU), which may communicate with other RSU UEs, non-RSU UEs, the base station 104, and / or entities at the base station 104 (such as the RU 106).

[0039] Still referring to Figure 1 , in some aspects, the UE 102 may include a TDCC quantization component 140, which is configured to receive, from a network entity, a configuration for a measurement report that includes at least one of the following: a TDCC report using configured quantization parameters, a Doppler spread report, or a Doppler frequency shift report, each report being based on measurements of one or more TRSs; receive one or more TRSs from the network entity; receive control signaling from the network entity that triggers the configuration for the measurement report; and in response to receiving the control signaling and the one or more TRSs, send the measurement report to the network entity, the measurement report being based on the configuration.

[0040] In some aspects, the base station 104 or a network entity of the base station 104 may include a measurement report configuration component 150, which is configured to send, to the UE, a configuration for a measurement report that includes at least one of the following: a TDCC report using configured quantization parameters, a Doppler spread report, or a Doppler frequency shift report, each report being based on a TRS; send one or more TRSs to the UE; send control signaling to the UE that triggers the configuration for the measurement report sent to the UE; and in response to sending the control signaling and the one or more TRSs, receive the measurement report from the UE, the measurement report being based on the configuration.

[0041] Therefore, Figure 1A wireless communication system is described that can be implemented in combination with aspects of one or more other figures described herein (such as Figures 2 to 5 aspects shown). Further, although the following description may focus on 5G NR, the concepts described herein can be applied to other similar areas, such as 5G-Advanced and future releases, LTE, LTE-advanced (LTE-A), and other wireless technologies such as 6G.

[0042] Figure 2 FIG. 200 shows an example time slot structure of a TRS 250. A UE 102 and a network entity 104 (such as a base station or a unit of a base station) may perform multiple-input multiple-output (MIMO) communication, where the network entity 104 may use channel state information (CSI) to select a digital precoder for the UE 102. The network entity 104 may configure CSI reporting from the UE 102 via RRC signaling (e.g., CSI-reportConfig), where the UE 102 may use a channel state information reference signal (CSI-RS) as a channel measurement resource (CMR) for the UE 102 to measure a downlink channel. The TRS 250 corresponds to a special type of CSI-RS for tracking. The network entity 104 may also configure an interference measurement resource (IMR) for the UE 102 to measure interference to the downlink channel (e.g., via CSI-reportConfig). Thus, the UE 102 may estimate the channel between the UE 102 and the network entity 104 based on the CSI-RS (e.g., the TRS 250).

[0043] The network entity 104 may configure the time-domain behavior for the transmission of CSI reports to the network entity 104 (e.g., based on CSI-reportConfig), such as periodic, semi-persistent, or aperiodic reporting. In an example, the network entity 104 may activate or deactivate semi-persistent CSI reporting from the UE 102 using a MAC control element (MAC-CE). The network entity 104 may trigger aperiodic CSI reporting from the UE 102 based on the transmission of downlink control information (DCI) to the UE 102. The network entity 104 may receive periodic CSI reports from the UE 102 on a physical uplink control channel (PUCCH) resource (e.g., configured via CSI-reportConfig). CSI-reportConfig may also be used to configure the PUCCH resource for the transmission of semi-persistent CSI reports to the network entity 104. In other examples, the transmission of semi-persistent CSI reports to the network entity 104 may be on a physical uplink shared channel (PUSCH) resource triggered by DCI. The UE 102 may similarly send aperiodic CSI reports on a PUSCH resource triggered by DCI.

[0044] When reporting CSI on a PUSCH or PUCCH in long format (e.g., long PUCCH), the UE 102 may divide the CSI into two parts: CSI Part 1 and CSI Part 2. CSI Part 1 is based on a fixed payload size configured according to RRC, which may include a CSI-RS resource indicator (CRI), a rank indicator (RI), and / or a channel quality indicator (CQI) for the first codeword. The UE 102 may determine the payload size for CSI Part 2 based on the reported content of CSI Part 1. CSI Part 2 may include a precoder matrix indicator (PMI), a CQI for the second codeword, and / or a layer indicator (LI).

[0045] The UE 102 may measure a channel state information reference signal (CSI-RS) for tracking (e.g., TRS 250) to perform time and frequency offset tracking. Time and frequency offset tracking may include Doppler frequency shift estimation and Doppler spread estimation. The TRS 250 may correspond to a CSI-RS resource set associated with configured RRC parameters (e.g., trs-Info). The network entity 104 may send control signaling, such as RRC signaling, to configure the periodic TRS 250 (e.g., via a non-zero power (NZP)-CSI-RS-ResourceSet configured with a higher layer parameter trs-Info) or trigger an aperiodic TRS via downlink control information (DCI).

[0046] In the example, network entity 104 may configure a downlink reference signal (such as TRS 250) to be transmitted in two symbols of a time slot (e.g., symbol 3 of resource 213 and symbol 7 of resource 217 of the first time slot 260), or in four symbols distributed over two consecutive time slots (e.g., symbol 3 of resource 213 and symbol 7 of resource 217 of the first time slot 260, and symbol 3 of resource 233 and symbol 7 of resource 237 of the second time slot 270), where two CSI-RS resources or four CSI-RS resources may be associated with an NZP-CSI-RS-ResourceSet configured using a higher layer parameter trs-Info. FIG. 200 shows an example of a TRS structure based on 2 time slots (e.g., based on 4 resources) distributed over a resource block (RB) (e.g., 12 subcarriers). A TRS structure based on 1 time slot (e.g., based on 2 resources) may correspond to a subset of the 2-time-slot structure. For example, a TRS structure based on 1 time slot may correspond to the first time slot 260.

[0047] The aperiodic TRS may be quasi-co-located (QCL) with the periodic TRS 250, such that network entity 104 may provide a QCL indication to UE 102 via DCI. Network entity 104 may configure a QCL type and / or a source reference signal for QCL signaling. The QCL type of the downlink reference signal may be based on higher layer parameters, such as qcl-Type in the QCL-Info parameter. A first QCL type corresponding to type A may be associated with Doppler frequency shift, Doppler spread, average delay, and / or delay spread. A second QCL type corresponding to type B may be associated with Doppler frequency shift and / or Doppler spread. A third QCL type corresponding to type C may be associated with Doppler frequency shift and / or average delay. A fourth QCL type corresponding to type D may be associated with spatial receive (Rx) parameters.

[0048] The movement of UE 102 may cause a change in the radio channel between UE 102 and network entity 104. UE 102 may report information on the state of the channel between UE 102 and network entity 104 to network entity 104. For example, UE 102 may send a TDCC report to network entity 104 based on one or more TRS 250 received from network entity 104. Network entity 104 may calculate the Doppler spread of the time-domain channel under delay based on the channel correlation between symbol i and symbol j as follows:

[0049]

[0050] where is the time-domain duration of the symbol, is the zero - order Bessel function, is the normalized channel correlation matrix, which is determined based on the following formula:

[0051]

[0052] where indicates the time - domain channel of symbol i at delay below.

[0053] For the channel correlation matrix measured using periodic downlink reference signals (e.g., TRS 250), the channel correlation matrix can be averaged over multiple time slots based on the following formula:

[0054]

[0055] where indicates the time - domain channel of symbol i in time slot at delay below. The channel correlation can also be calculated to include interference and noise suppression based on the following:

[0056]

[0057] where indicates the interference and noise power within the estimated channel. The network entity 104 can calculate the Doppler spread / frequency shift based on the channel changes indicated in the TDCC report. In some examples, the UE 102 can perform an equivalent calculation and send the value of the Doppler spread / frequency shift to the network entity 104.

[0058] Since the channel correlation is likely to be different at different delays, it becomes necessary to report the channel correlations at several delays. This repeated reporting causes high reporting overhead. Therefore, quantization and / or compression techniques are implemented at the UE 102 for the beam measurement and reporting process to reduce the overhead associated with reporting the channel correlations at different delays. The network entity 104 can send downlink control signaling indicating a set of quantization parameters for the TDCC report to the UE 102, or the UE 102 can independently determine a set of quantization parameters for the TDCC report. The format of the TDCC report (e.g., the quantized TDCC report) reduces the reporting overhead, thereby improving the system performance of the wireless communication between the UE 102 and the network entity 104. Figures 3 to 5 Describes the report formatting techniques for reporting channel quality.

[0059] Figure 3FIG. 300 is a signaling diagram showing TDCC reports (e.g., transmission procedure 350 per TRS). The UE 102 may send 306 a UE capability report to the network entity 104, which UE capability report indicates one or more UE capabilities for TDCC reporting. For example, the UE 102 may indicate to the network entity 104 the UE 102's capability to report TDCC for each TRS (e.g., TDCC report per TRS). The one or more UE capabilities may indicate whether the UE 102 supports TDCC measurement, a first maximum number of serving cells for TDCC reporting, and / or a second maximum number of signal paths for TDCC reporting. That is, the UE 102 may indicate a first maximum number of taps for reporting TDCC reports and a second maximum number of TRSs in or across serving cells for TDCC reporting. TDCC corresponds to channel correlation at different delays. One tap indicates one delay. Different taps indicate TDCC calculated according to different delays. The second maximum number of TRSs may be counted per CC, per frequency band, per frequency band combination, or per UE. In other implementations, the network entity 104 may receive one or more UE capabilities from a core network entity (such as the AMF 121 shown in FIG. 100).

[0060] The network entity 104 sends 308 first control signaling to the UE 102, which first control signaling includes CSI report configuration for configuring the UE 102 to perform TDCC reporting. The first control signaling / configuration for TDCC reporting may correspond to RRC signaling (e.g., CSI-ReportConfig in RRCReconfiguration). The RRC signaling may indicate an RRC reconfiguration message from the network entity 104 to the UE 102, or a system information block (SIB), where the SIB may be a predefined SIB (e.g., SIB1) or a different SIB sent by the network entity 104 (e.g., SIB J, where J is an integer greater than 21). In an example, the CSI report configuration is based on one or more UE capabilities received 306 by the network entity 104 from the UE 102.

[0061] The first control signaling may optionally include a first set of quantization parameters. For example, the network entity 104 may send 308 quantization parameters in the first control signaling, such as the maximum number of measured taps (e.g., non-zero coefficients (NZC) of TDCC reports), the maximum number of reported taps (e.g., the maximum number of reported NZC of TDCC reports), the number of reported taps (e.g., the number of NZCs reported in the TDCC report), the time-domain duration of each tap , the number of bits of the quantized NZCs, one or more symbol offsets reported in the TDCC report, etc.

[0062] For a TDCC report of 2 time slots, as shown in FIG. 200, the candidate symbol offsets can be {4, 14, 18}. In other examples, the network entity 104 can configure the UE 102 to report in-slot TDCC (e.g., with 4 symbol offsets) or inter-slot TDCC (with 14 and / or 18 symbol offsets) or both. The content to be quantized (such as reporting only the amplitude or both the amplitude and the phase) can be associated with each NZC. If the network entity 104 does not configure a complete set of quantization parameters or any quantization parameters in the first control signaling, the network entity 104 can include the set of quantization parameters in the second control signaling sent 316 to the UE 102 that triggers the TDCC report. If the network entity 104 does include at least one quantization parameter in the first control signaling, the network entity 104 can not include any quantization parameters in the second control signaling sent 316 to the UE 102 that triggers the TDCC report.

[0063] The network entity 104 sends 310a, 312a periodic TRS to the UE 102. In response to receiving 310a, 312a periodic TRS from the network entity 104, the UE 102 can perform 314 TDCC measurements for the TDCC report. The network entity 104 sends 316 second control signaling to the UE 102 to trigger the TDCC report. The UE 102 determines the quantized TDCC and the reporting format of the quantized TDCC (e.g., based on the first / second set of quantization parameters). In the case where neither the first control signaling nor the second control signaling includes a set of quantization parameters, the UE 102 can optionally determine 318 a third set of quantization parameters for the TDCC report. The UE 102 can report the third set of quantization parameters to the network entity 104 in the quantized TDCC report sent 320 by the UE 102 to the network entity 104.

[0064] If the network entity 104 does not configure any quantization parameters for the UE 102, the network entity 104 and the UE 102 can apply the default values of the quantization parameters. The default values can correspond to the maximum number of measured taps based on the length of the cyclic prefix (CP) and the duration of each tap , for example , the maximum number of reported taps is the same as the maximum number of measured taps, the number of reported taps is the same as the maximum number of reported taps, and the time-domain duration of each tap is based on the symbol duration Number of resource elements in the TRS symbol for TDCC measurement 314 , for example , the number of bits of the quantized NZC is equal to 3, the symbol offsets reported by TDCC are equal to 4 and 14, or the quantized content of each NZC is based on the magnitude of the NZC. In some implementations, UE 102 may perform 314 TDCC measurement based on one receive antenna port. The receive antenna port may correspond to the highest or lowest layer 1 reference signal received power (L1-RSRP) or layer 1 signal-to-interference-plus-noise ratio (L1-SINR) measured among all receive antenna ports. In some other implementations, UE 102 may perform 314 TDCC measurement based on more than one receive antenna port, and UE 102 may quantize and report one TDCC based on the TDCC measured from the receive antenna ports. The one TDCC may be the average value, the minimum value, or the maximum value TDCC of the measured TDCCs. In some other implementations, UE 102 may perform 314 TDCC measurement based on more than one receive antenna port, and UE 102 may quantize and report based on the TDCC measured from the receive antenna ports.

[0065] After receiving the first / second control signaling 308, 316, UE 102 may quantize the TDCC measurement 314 based on the quantization parameter set. If UE 102 determines the third quantization parameter set, UE 102 may quantize the TDCC measurement 314 based on the first / second quantization parameter set received 308, 316 and / or the third quantization parameter set determined 318. UE 102 sends 320 the quantized TDCC report to the network entity 104 based on the determined 318 quantization and reporting format, where the reporting format indicates the information reported in CSI part 1 and CSI part 2. When the TDCC report is based on the third quantization parameter set, the TDCC report may indicate the third quantization parameter set to the network entity 104. The third quantization parameter set may be reported in CSI part 1 or CSI part 2.

[0066] UE 102 may measure 314 TDCC based on the following maximum number of measured taps as follows:

[0067] .

[0068] where corresponds to the channel correlation, i corresponds to symbol i, and j corresponds to symbol j. UE 102 may report the maximum number of measured taps in the TDCC report sent 320 to the network entity. In the example, UE 102 may report the first taps, where the reported taps are based on:

[0069] 。

[0070] UE 102 may report the coefficients in CSI Part 1 or CSI Part 2. For coefficient k, UE 102 may report the quantized magnitude. Alternatively, for coefficient k, UE 102 may report the quantized magnitude and phase. UE 102 may quantize the magnitude based on a predefined quantization process and the number of bits configured or predefined for quantization.

[0071] In the first example, the magnitude may be quantized based on a 3-bit quantization process, where the reported bits [000, 001, 010, 011, 100, 101, 110, 110] correspond to the magnitudes respectively. In the second example, the magnitude may be quantized based on another 3-bit quantization process, where the reported bits [000, 001, 010, 011, 100, 101, 110, 110] correspond to the magnitudes respectively. UE 102 may quantize the phase based on a predefined quantization process and the number of bits configured or predefined for quantization. For example, the phase may be quantized based on a 3-bit quantization process, where the reported bits [000, 001, 010, 011, 100, 101, 110, 110] correspond to the phases respectively.

[0072] If UE 102 reports TDCCs with more than 1 symbol offset, UE 102 may report the coefficients for each symbol offset. In the example, the UE reports the first taps for each symbol offset based on the following:

[0073] 。

[0074] UE 102 may report the coefficients in CSI Part 1 or CSI Part 2. UE 102 may also report the value of in CSI Part 1 or CSI Part 2. In the example, UE 102 may report the value of The reported value. If the UE 102 reports TDCCs with more than 1 symbol offset, the UE 102 may report the coefficients for each symbol offset and the value of. The UE 102 may report the coefficients for each symbol offset and the common value of for all symbol offsets.

[0075] For each symbol offset, the UE 102 may report the first taps after the most powerful tap based on the following:

[0076]

[0077] where is the index of the most powerful tap. Alternatively, the UE 102 may report the taps before the most powerful tap and the taps after the most powerful tap. In the example, the reported coefficients are based on:

[0078]

[0079] The UE 102 reports the coefficients and the value of in CSI Part 1 or CSI Part 2. In the example, the UE 102 may report the value of and the coefficients in the same CSI part. When the UE 102 reports TDCCs with more than 1 symbol offset, the UE 102 may report the coefficients for each symbol offset and the value of. The UE 102 may report the coefficients for each symbol offset and the common value of for all symbol offsets.

[0080] For each symbol offset, the UE 102 may report the first taps after the most powerful tap based on the following:

[0081]

[0082] where is the index of the most powerful tap. Alternatively, the UE 102 may report the taps before the most powerful tap and the taps after the most powerful tap. In the example, the reported coefficients are based on:

[0083]

[0084] The UE 102 reports in CSI Part 1 or CSI Part 2 coefficients, values, and values. In an example, the UE 102 reports values in CSI Part 1 and reports values and coefficients in CSI Part 2.

[0085] When the UE 102 reports a TDCC with more than 1 symbol offset, the UE 102 may report coefficients, values, and values for each symbol offset. The UE 102 may report coefficients, a common value of for each symbol offset, and a common value of coefficients and values for all symbol offsets. In a further example, the UE102 reports coefficients and values for each symbol offset and a common value of for all symbol offsets.

[0086] The UE 102 may report the strongest taps for each symbol offset. The UE 102 may report a first vector to indicate the indices of the taps reported within the taps, and report a second vector to indicate the coefficients of the taps reported. The first vector may be a bitmap with bits, where a value of 0 indicates an unreported tap and a value of 1 indicates a reported tap.

[0087] The UE 102 may report the first vector in CSI Part 1 or CSI Part 2. The UE 102 may similarly report the second vector in CSI Part 1 or CSI Part 2. In an example, the UE 102 reports the first vector in CSI Part 1 and the second vector in CSI Part 2. The payload size of the second vector is based on the number of "1" values in the reported first vector. When the UE 102 reports a TDCC with more than 1 symbol offset, the UE 102 may report the first vector and the second vector for each symbol offset. The UE 102 may report the second vector for each symbol offset and a common first vector for all symbol offsets. Figure 3Describes each TRS TDCC report, while Figure 4 Describes cross-TRS TDCC reports.

[0088] Figure 4 Is a signaling diagram 400 showing a cross-TRS TDCC reporting process (e.g., based on cross-TRS transmission processes 450a - 450b) for multiple TRSs. Element 306 has been described with respect to Figure 3 Has been described.

[0089] Network entity 104 sends 408 first control signaling including a CSI report configuration that configures UE 102 to measure 414 the TDCC of multiple TRSs for TDCC reporting. The first control signaling may include quantization parameters for UE 102 to report the TDCC of more than one TRS. UE 102 receives 410a - 412b multiple TRSs from network entity 104 for cross-TRS TDCC reporting. For example, UE 102 may receive 410a, 411, 412a periodic TRS1, periodic TRS 2 to periodic TRS M during a first cross-TRS transmission process 450a. UE 102 may receive 410b, 412b periodic TRS 1 to periodic TRS M again during a second cross-TRS transmission process 450b. UE 102 may select a subset of TRSs for TDCC reporting based on TDCC measurements 414 of multiple TRSs. When UE 102 reports the TDCC of more than one TRS, UE 102 may report the TDCC based on joint quantization of the TRSs.

[0090] The first set of quantization parameters indicated in the first control signaling may include: the maximum number of measured taps (e.g., NZC for TDCC reporting of each TRS, where network entity 104 may configure common parameters or separate parameters for each TRS), the maximum number of reported taps (e.g., the maximum number of reported NZC for TDCC reporting of each TRS, where the network entity may configure common parameters or separate parameters for each TRS), the maximum total number of reported taps (e.g., the maximum total number of reported NZC for cross-TRS TDCC reporting), the number of reported taps (e.g., the number of reported NZC for TDCC reporting of each TRS, where network entity 104 may configure common parameters or separate parameters for each TRS), the total number of reported taps (e.g., the number of reported NZC for cross-TRS TDCC reporting), the time-domain duration of each tap for each TRS (where the network entity 104 can configure a common parameter or a separate parameter for each TRS), the number of bits of the quantized NZC for each TRS (where the network entity 104 can configure a common parameter or a separate parameter for each TRS), one or more symbol offsets reported by the TDCC (which indicates the symbol offset of two symbols reported by the TDCC for each TRS, where the network entity 104 can configure a common parameter or a separate parameter for each TRS), the quantized content of each NZC (e.g., whether the TDCC report for each TRS reports only the amplitude or reports both the amplitude and the phase, where the network entity can configure a common parameter or a separate parameter for each TRS), and / or the number of reported TDCCs .

[0091] If the network entity 104 does not configure the complete quantization parameter set or any quantization parameter via the first control signaling, the network entity 104 may send 416 a second control signaling indicating a quantization parameter (e.g., a second quantization parameter set). In other examples, such as when the first control signaling indicates at least one quantization parameter in the first quantization parameter set, the second control signaling may not indicate any quantization parameter. The network sends 416 the second control signaling to trigger a TDCC report based on multiple TRSs.

[0092] In the case where the network entity 104 does not configure any quantization parameters in the first / second control signaling, the UE 102 may determine 418 a third quantization parameter set and report the third quantization parameter set to the network entity 104. For example, the UE 102 determines 418 a quantized TDCC report and a reporting format for a plurality of TRSs, and optionally determines 418 a third quantization parameter set so that the UE 102 may send 420 a quantized TDCC report for one or more of the plurality of TRSs (e.g., using the third quantization parameter set indicated in the TDCC report). The third quantization parameter set may include parameters for quantization of the cross-TRS TDCC. The third quantization parameter set may be a common parameter or a separate parameter for each reported TDCC.

[0093] In other implementations, if the network entity does not configure any quantization parameters in the first / second control signaling, the UE 102 and the network entity 104 may apply default values ​​for the quantization parameters. The default values ​​may include: the maximum number of measured taps reported by the TDCC for each TRS, which is based on the length of the CP and the duration of each tap ,For example ; the maximum number of reported taps in the TDCC report for each TRS, which is the same as the maximum number of measured taps; the total maximum number of reported taps across the TDCC reports of the TRS, which is the same as the maximum number of measured taps multiplied by the number of reported TDCCs; the number of reported taps in the TDCC report for each TRS, which is the same as the maximum number of reported taps in the TDCC report for each TRS; the number of reported taps in the TDCC report across the TRS, which is the same as the maximum number of reported taps in the TDCC report across the TRS; and / or the time domain duration of each tap in the TDCC report for each TRS, which is based on the symbol duration and the number of resource elements in the TRS symbol for TDCC measurement , for example . In some implementations, the network entity 104 can use the same bandwidth to send the TRS for TDCC reporting of 410a - 412b (e.g., the network entity 104 can avoid using different bandwidths to send the TRS for TDCC reporting of 410a - 412b). The default values can further include that the number of bits of the quantized NZC in the TDCC report for each TRS is equal to 3, the symbol offset in the TDCC report for each TRS is equal to 4 and 14, the quantized content of each NZC in the TDCC report for each TRS is based on the amplitude of the NZC, and / or the number of reported TDCCs is the same as the number of TRSs configured for TDCC reporting.

[0094] After receiving the first / second control signaling of 408, 416 from the network entity 104, the UE 102 quantizes the TDCC measurement 414 based on the quantization parameters. The UE 102 can determine a third set of quantization parameters 418 and quantize the measured TDCC based on the third set of quantization parameters, or the UE 102 can quantize the measured TDCC based on the first / second set of quantization parameters received in the first / second control signaling of 408, 416. The UE 102 sends a quantized TDCC report 420 for one or more of the multiple TRSs to the network entity 104. In some examples, the quantized TDCC report can include the third set of quantization parameters, which can be reported in CSI part 1 or CSI part 2.

[0095] To measure, quantize, and report the TDCC of multiple TRSs, the UE 102 can optionally select a subset of TRSs from the configured TRSs for TDCC measurement 414 and reporting 420. In some implementations, the UE 102 performs the selection based on the L1 - RSRP / L1 - SINR from the TRS measurement 414. The UE 102 selects the one with the highest L1 - RSRP / L1 - SINR TRS, and measure the TDCC of the 414 selected TRS. The UE 102 can jointly or separately quantify the TDCC reported for the TDCC. The UE 102 determines 418 the reporting format and content of the quantified coefficients and sends 420 the TDCC report to the network entity 104.

[0096] For each symbol offset of TRS x, the UE 102 reports the previous number of taps, where the reported taps are based on:

[0097]

[0098] The UE 102 reports the number of coefficients in CSI part 1 or CSI part 2. The UE 102 can report the value in CSI part 1 or CSI part 2. For X TRS, the value can be the same (e.g., ). The UE 102 reports the value 1 of X TDCCs and number of coefficients. In an example, the UE 102 reports the value in CSI part 1 and reports the number of coefficients in CSI part 2. The payload size of the TDCC report in CSI part 2 is based on the reported value in CSI part 1. The value for each TRS can be different. The UE 102 can report all the values of X TDCCs and number of coefficients. In an example, the UE 102 reports the value X in CSI part 1 and reports the number of coefficients in CSI part 2. The payload size of the TDCC report in CSI part 2 is based on the reported value in CSI part 1. The UE 102 can also report the selected TRS index in CSI part 1 or CSI part 2.

[0099] When the UE 102 reports the TDCC for more than 1 symbol offset, the UE 102 can report the number of coefficients for each symbol offset and the value or for each value. The UE 102 can report the number of coefficients for each symbol offset and the common value of the symbol offset and the common value of each .

[0100] For each symbol offset for TRS x, UE 102 may report the first taps after the tap with the strongest power based on the following:

[0101]

[0102] where is the index of the strongest tap for TRS x. Alternatively, UE 102 may report the taps before the strongest tap and the taps after the strongest tap. In the example, the reported coefficients are based on:

[0103]

[0104] UE 102 reports the coefficients in either CSI part 1 or CSI part 2 of the selected TRS. UE 102 reports the value in CSI part 1 or CSI part 2. UE 102 may report a common value of (e.g., ) for the selected TRS, where x0 indicates the TRS with the strongest L1-RSRP / L1-SINR. In other implementations, UE 102 may report a separate value of for each TRS. UE 102 may report the value or X values of and the coefficients in the same CSI part. UE 102 may also report the selected TRS index in CSI part 1 or CSI part 2. When UE 102 reports TDCCs for more than 1 symbol offset, UE 102 may report the coefficients and the value or X values of for each symbol offset. In other implementations, UE 102 may report the X common values of the

[0105] For each symbol offset for TRS x, UE 102 may report the first taps after the tap with the strongest power based on the following:

[0106]

[0107] where is the index of the strongest tap for TRS x. Alternatively, UE 102 may report the taps before the strongest tap and the taps after the strongest tap. In the example, the reported coefficients are based on:

[0108]

[0109] UE 102 reports coefficients of X selected TRSs in CSI Part 1 or CSI Part 2. UE 102 reports the value in CSI Part 1 or CSI Part 2. In some implementations, UE 102 reports the common value (e.g., ) for all selected TRSs, where x0 indicates the TRS with the strongest L1-RSRP / L1-SINR. In other implementations, UE 102 may report a separate value for each TRS. UE 102 may report the value in CSI Part 1 or CSI Part 2. The value may be the same for the X TRSs (e.g., ). UE 102 may report the value 1 and coefficients of X TDCCs. UE 102 may report the value in CSI Part 1 and report coefficients in CSI Part 2. The payload size of the TDCC report in CSI Part 2 is based on the reported value in CSI Part 1. For each TRS, the value may be different, such that UE 102 reports all the values of the X TDCC reports and coefficients. UE 102 may report X values of in CSI Part 1 and report

[0110] 110 When UE 102 reports TDCCs with more than 1 symbol offset, UE 102 may report coefficients, the value, or X values of the value, or X values for each symbol offset. UE102 may report coefficients, the common value, or X common values, and the symbol offset common value or X common values. In other implementations, UE 102 reports the number of coefficients and value and the symbol offset common value and X common values. UE 102 may also report the number of coefficients and value and the symbol offset common value and X common values.

[0111] For each symbol offset of TRS x, UE 102 may report the strongest number of taps. UE 102 reports a first vector to indicate the index of the number of taps reported within the number of taps for each TRS, and reports a second vector to indicate the coefficients of the number of taps reported for each TRS. The first vector may be a bitmap with bits, where the value "0" indicates that the tap is not reported, and the value "1" indicates that the tap is reported. value may be the same for all TRSs, or value may be different for some TRSs. UE 102 may also report the value.

[0112] UE 102 may report the first vector in CSI Part 1 or CSI Part 2. UE 102 may also report the second vector in CSI Part 1 or CSI Part 2. In an example, UE 102 reports the first vector in CSI Part 1 and reports the second vector in CSI Part 2. The payload size of the second vector is based on the number of "1" values in the reported first vector. UE 102 may additionally report a third vector in CSI Part 1 or CSI Part 2, indicating the value for each TRS. When UE 102 reports TDCCs for more than 1 symbol offset, UE 102 may report the first vector / second vector for each symbol offset. In other implementations, UE 102 reports the second vector for each symbol offset and a common first vector for all symbol offsets. The third vector may be common or separate for the symbol offsets. Figures 3 to 4 describes the TDCC report, while Figure 5 describes the Doppler spread / frequency shift report.

[0113] Figure 5It is a signaling diagram 500 showing a reporting content selection process (e.g., selection of TDCC reporting content or Doppler spread / frequency shift reporting content). Elements 310a, 312a, 314, and 350 have been described with respect to Figure 3 this.

[0114] UE 102 may be able to calculate Doppler spread / frequency shift based on TDCC measurements 314. In this case, UE 102 may directly send 520 the Doppler spread / frequency shift to network entity 104 to reduce overhead. However, calculating Doppler spread / frequency shift at UE 102 may have increased complexity and / or may consume an increased amount of time of UE 102 to determine 518 the Doppler spread / frequency shift based on one or more measurements 314 of TDCC.

[0115] In addition to the UE capabilities that may be sent 306 to network entity 104 for TDCC reporting, UE 102 may also send 506 to network entity 104 the UE capabilities for Doppler spread / frequency shift reporting. The UE capabilities report may indicate whether UE 102 supports both Doppler spread / frequency shift reporting and TDCC reporting, or whether UE 102 supports Doppler spread / frequency shift reporting in place of TDCC reporting.

[0116] Network entity 104 sends 508 first control signaling including CSI reporting configuration to configure UE 102 for channel reporting. The first control signaling may optionally indicate the reporting content (e.g., TDCC report or Doppler spread / frequency shift report) and / or a first set of quantization parameters. Network entity 104 sends 516 second control signaling that triggers channel reporting. The second control signaling may optionally indicate the reporting content (e.g., TDCC report or Doppler spread / frequency shift report) and / or a second set of quantization parameters.

[0117] UE 102 may determine 518 the reporting content (e.g., TDCC report or Doppler spread / frequency shift report) and the reporting format. In an example, UE 102 determines the reporting content based on the control signaling received 508, 516 from network entity 104. UE 102 sends 520 a quantized TDCC report or a quantized Doppler spread / frequency shift report to network entity 104 based on the reporting content indicated in the control signaling. In other examples, UE 102 may determine 518 the reporting content and the reporting format independently of the control signaling (e.g., based on UE capabilities for Doppler spread / frequency shift reporting and / or other parameters). When UE 102 determines 518 the reporting content independently of the control signaling, UE 102 sends 520 the quantized TDCC report or the quantized Doppler spread / frequency shift report together with an indicator of the reporting content to network entity 104.

[0118] If UE 102 determines 518 to send a TDCC report to network entity 104, UE 102 quantizes TDCC measurement 314 based on first / second control signaling received 508, 516 from network entity 104 indicating first / second quantization parameters. UE 102 may also select a third quantization parameter to determine 518 the TDCC report format for multiple TRSs. UE 102 sends 520 the TDCC report based on the quantized TDCC and the determined 518 TDCC report format. The TDCC report may include an indication that the report content corresponds to the TDCC report.

[0119] If UE 102 determines 518 to send a Doppler spread / frequency shift report to network entity 104, UE 102 may determine 518 the Doppler spread / frequency shift based on TDCC measurement 314. UE 102 may also determine the report format for the Doppler spread / frequency shift report. UE 102 sends 520 the Doppler spread / frequency shift report to network entity 104 based on the determined 518 Doppler spread / frequency shift and the report format. The Doppler spread / frequency shift report may also include an indication that the report content corresponds to the Doppler spread / frequency shift report. Figures 3 to 5 Techniques for reporting channel quality using one or more TRSs are described. Figures 6 to 7 Illustrates for implementing Figures 3 to 5 One or more aspects of. Specifically, Figure 6 Illustrates an implementation of one or more aspects of UE 102 for Figures 3 to 5 One or more aspects of. Figure 7 Illustrates an implementation of one or more aspects of network entity 104 for Figures 3 to 5 One or more aspects of.

[0120] Figure 6 Illustrates a flowchart 600 of a method for wireless communication at a UE. Referring to Figure 1 , Figures 3 to 5 and Figure 8 , this method may be performed by UE 102, UE equipment 802, etc., and UE 102, UE equipment 802, etc. may include memories 826’, 806’, 816 and may correspond to the entire UE 102 or the entire UE equipment 802, or components of UE 102 or UE equipment 802, such as wireless baseband processor 826 and / or application processor 806.

[0121] UE 102 sends 606 a UE capability report to the network entity, and the UE capability report indicates at least one of the following: the ability of the UE to send a measurement report to the network entity, the first maximum number of taps to be reported in the TDCC report, or the second maximum number of TRSs to be reported in the TDCC report. For example, referring to Figures 3 to 4, UE 102 sends 306 UE capabilities for TDCC reporting to network entity 104. Refer to Figure 5 , UE 102 may also send 506 Doppler spread / frequency shift reports to network entity 104.

[0122] UE 102 receives 608a from the network entity a configuration for a measurement report - the measurement report corresponding to at least one of the following: a TDCC report using configured quantization parameters, a Doppler spread report, or a Doppler frequency shift report, each report being based on measurements of one or more TRSs. For example, refer to Figures 3 to 4 , UE 102 receives 308, 408 from the network entity a first control signaling for CSI report configuration. Refer to Figure 5 , UE 102 receives 508 from network entity 104 a first control signaling for configuring a channel report, the channel report being able to include a Doppler spread / frequency shift report.

[0123] UE 102 receives 608b from the network entity a first indicator of report content options for sending a measurement report to the network entity - the report content options corresponding to at least one of a TDCC report, a Doppler spread report, or a Doppler frequency shift report. For example, refer to Figure 5 , UE 102 receives 508 from network entity 104 a first control signaling that may indicate the report content of a channel report, where the report content may correspond to a TDCC report or a Doppler spread / frequency shift report.

[0124] UE 102 receives 608c from the network entity at least one index of one or more TRSs associated with the configuration - the measurement report indicating the one or more TRSs based on the at least one index. For example, refer to Figures 3 to 5 , the first control signaling that UE 102 receives 308, 408, 508 from network entity 104 may indicate one or more indices of one or more TRSs.

[0125] UE 102 receives 650 the one or more TRSs from the network entity. For example, refer to Figure 3 and Figure 5 , UE 102 receives 350 from network entity 104 one or more periodic TRSs based on each TRS transmission process. Figure 4 , UE receives 450a, 450b from network entity 104 one or more periodic TRSs based on a cross-TRS transmission process.

[0126] UE 102 receives 616 from the network entity control signaling that triggers the configuration of a measurement report. For example, refer to Figures 3 to 4, UE 102 receives 316, 416 the second control signaling that triggers the TDCC report from the network entity 104. Refer to Figure 5 , UE 102 receives 516 the second control signaling from the network entity 104, and the second control signaling triggers a channel report, where the channel report may correspond to a TDCC report or a Doppler spread / frequency shift report.

[0127] In response to the receipt of the control signaling and one or more TRSs, UE 102 sends 620a a measurement report to the network entity - the measurement report is based on the configuration. For example, refer to Figures 3 to 4 , UE 102 sends 320, 420 a quantized TDCC report to the network entity 104 in response to the second control signaling and the periodic TRS. Refer to Figure 5 , UE 102 may also send 520 a Doppler spread / frequency shift report to the network entity 104 in response to the second control signaling and the periodic TRS.

[0128] UE 102 sends 620b a second indicator of the report content, and the report content is selected from the report content options for sending the measurement report to the network entity. For example, refer to Figure 5 , UE 102 sends 520 an indicator of the report content (e.g., TDCC report or Doppler spread / frequency shift report) to the network entity 104 together with the channel report. Figure 6 Describes a method from the UE side of a wireless communication link, while Figure 7 describes a method from the network side of a wireless communication link.

[0129] Figure 7 is a flowchart 700 of a method of wireless communication at a network entity. Refer to Figure 1 、 Figures 3 to 5 and Figure 9 , this method may be executed by one or more network entities 104, and the one or more network entities may correspond to a base station or a unit of a base station, such as RU 106, DU 108, CU 110, RU processor 906, DU processor 926, CU processor 946, etc. One or more network entities 104 may include a memory 906' / 926' / 946', and the memory may correspond to the whole of one or more network entities 104, or components of one or more network entities 104, such as RU processor 906, DU processor 926, or CU processor 946.

[0130] The network entity 104 receives 706 a UE capability report from the UE, and the UE capability report indicates at least one of the following: the UE's capability for measurement reporting, the first maximum number of taps included in the TDCC report, or the second maximum number of TRSs included in the TDCC report. For example, refer toFigures 3 to 4 , the network entity 102 receives 306 UE capabilities for TDCC reporting from the UE 102. Refer to Figure 5 , the network entity 104 may also receive 506 Doppler spread / frequency shift reports from the UE 102.

[0131] The network entity 104 sends 708a to the UE a configuration for a measurement report - the measurement report corresponds to at least one of the following: TDCC report using configured quantization parameters, Doppler spread report, or Doppler frequency shift report, each report being based on one or more TRSs. For example, refer to Figures 3 to 4 , the network entity 104 sends 308, 408 to the UE 102 the first control signaling for CSI report configuration. Refer to Figure 5 , the network entity 104 sends 508 to the UE 102 the first control signaling for configuring a channel report, which may include a Doppler spread / frequency shift report.

[0132] The network entity 104 sends 708b to the UE the first indicator of the report content option for the measurement report - the report content option corresponds to at least one of the TDCC report, Doppler spread report, or Doppler frequency shift report. For example, refer to Figure 5 , the network entity 104 sends 508 to the UE 102 the first control signaling, which may indicate the report content of the channel report, where the report content may correspond to the TDCC report or the Doppler spread / frequency shift report.

[0133] The network entity 104 sends 708c to the UE at least one index of one or more TRSs for the configuration - the measurement report indicates one or more TRSs based on the at least one index. For example, refer to Figures 3 to 5 , the first control signaling sent by the network entity 104 to the UE 102 in 308, 408, 508 may indicate one or more indexes of one or more TRSs.

[0134] The network entity 104 sends 750 one or more TRSs to the UE. For example, refer to Figure 3 and Figure 5 , the network entity 104 sends 350 to the UE102 one or more periodic TRSs based on each TRS transmission process. Refer to Figure 4 , the network entity 104 sends 450a, 450b to the UE102 one or more periodic TRSs based on the cross-TRS transmission process.

[0135] The network entity 104 sends 716 control signaling to the UE, which triggers the configuration for the measurement report sent to the UE. For example, refer to Figures 3 to 4, the network entity 104 sends the second control signaling 316, 416 to trigger the TDCC report to the UE 102. Refer to Figure 5 , the network entity 104 sends the second control signaling 516 to the UE 102, and the second control signaling triggers a channel report, where the channel report can correspond to a TDCC report or a Doppler spread / frequency shift report.

[0136] In response to the transmission of the control signaling and one or more TRSs, the network entity 104 receives 720a a measurement report from the UE - the measurement report is based on the configuration. For example, refer to Figures 3 to 4 , in response to the second control signaling and the periodic TRS, the network entity 104 receives 320, 420 the quantized TDCC report from the UE 102. Refer to Figure 5 , the network entity 104 may also receive 520 the Doppler spread / frequency shift report from the UE 102 in response to the second control signaling and the periodic TRS.

[0137] The network entity 104 receives a second indicator of the report content 720b from the UE, and the report content is selected from the report content options for the measurement report. For example, refer to Figure 5 , the network entity 104 receives an indicator of the report content (e.g., TDCC report or Doppler spread / frequency shift report) and a channel report 520 from the UE 102. As Figure 8 The UE device 802 described can perform the method of flowchart 600. As Figure 9 One or more network entities 104 described can perform the method of flowchart 700.

[0138] Figure 8 FIG. 800 is an example showing a hardware implementation of the UE device 802. The UE device 802 can be the UE 102, a component of the UE 102, or can implement UE functions. The UE device 802 may include an application processor 806, and the application processor may have on-chip memory 806'. In an example, the application processor 806 may be coupled to a Secure Digital (SD) card 808 and / or a display 810. The application processor 806 may also be coupled to a sensor module 812, a power supply 814, an additional memory module 816, a camera 818, and / or other related components. For example, the sensor module 812 may control a barometric pressure sensor / altimeter, a motion sensor (such as an Inertial Management Unit (IMU)), a gyroscope, an accelerometer, a Light Detection and Ranging (LIDAR) device, a Radio Assisted Detection and Ranging (RADAR) device, a Sound Navigation and Ranging (SONAR) device, a magnetometer, an audio device, and / or other technologies for positioning.

[0139] The UE device 802 may further include a wireless baseband processor 826, which may be referred to as a modem. The wireless baseband processor 826 may have on-chip memory 826'. Similar to and together with the application processor 806, the wireless baseband processor 826 may also be coupled to the sensor module 812, the power supply 814, the additional memory module 816, the camera 818, and / or other related components. The wireless baseband processor 826 may additionally be coupled to one or more subscriber identity module (SIM) cards 820 and / or one or more transceivers 830 (e.g., wireless RF transceivers).

[0140] Within one or more transceivers 830, the UE device 802 may include a Bluetooth module 832, a WLAN module 834, an SPS module 836 (e.g., GNSS module), and / or a cellular module 838. The Bluetooth module 832, the WLAN module 834, the SPS module 836, and the cellular module 838 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 832, the WLAN module 834, the SPS module 836, and the cellular module 838 may each include a dedicated antenna and / or communicate with one or more other nodes using the antenna 840. For example, the UE device 802 may communicate with another UE 102 (e.g., sidelink communication) and / or with a network entity 104 (e.g., uplink / downlink communication) via the transceiver 830 and the antenna 840, where the network entity 104 may correspond to a base station or a unit of a base station, such as an RU 106, a DU 108, or a CU 110.

[0141] The radio baseband processor 826 and the application processor 806 may each separately include a computer-readable medium / memory 826', 806'. Additional modules of the memory 816 may also be regarded as computer-readable media / memories. Each computer-readable medium / memory 826', 806', 816 may be non-transitory. The radio baseband processor 826 and the application processor 806 may each be responsible for general processing, including executing software stored on the computer-readable medium / memory 826', 806', 816. The software, when executed by the radio baseband processor 826 / application processor 806, causes the radio baseband processor 826 / application processor 806 to perform the various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by the radio baseband processor 826 / application processor 806 when executing the software. The radio baseband processor 826 / application processor 806 may be components of the UE 102. The UE device 802 may be a processor chip (e.g., a modem and / or an application) and include only the radio baseband processor 826 and / or the application processor 806. In other examples, the UE device 802 may be the entire UE 102 and include additional modules of the device 802.

[0142] As discussed, the TDCC quantization component 140 is configured to: receive, from a network entity, a configuration for a measurement report that includes at least one of the following: a TDCC report using configured quantization parameters, a Doppler spread report, or a Doppler frequency shift report, each report based on measurements of one or more TRSs; receive, from the network entity, one or more TRSs; receive, from the network entity, control signaling triggering the configuration for the measurement report; and in response to receiving the control signaling and the one or more TRSs, send a measurement report to the network entity, the measurement report being based on the configuration. The TDCC quantization component 140 may be located within the radio baseband processor 826, the application processor 806, or both the radio baseband processor 826 and the application processor 806. The TDCC quantization component 140 may be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or a combination thereof.

[0143] UE device 802 may include various components configured for various functions. In an example, UE device 802, and in particular wireless baseband processor 826 and / or application processor 806, includes: means for receiving, from a network entity, a configuration for a measurement report, the measurement report including at least one of: a TDCC report using configured quantization parameters, a Doppler spread report, or a Doppler shift report, each report based on measurements of one or more TRSs; means for receiving, from a network entity, one or more TRSs; means for receiving, from a network entity, control signaling triggering the configuration for the measurement report; and means for sending, in response to receiving the control signaling and the one or more TRSs, the measurement report to the network entity, the measurement report based on the configuration. UE device 802 further includes means for sending a UE capability report to the network entity, the UE capability report indicating at least one of: the UE's ability to send a measurement report to the network entity, a first maximum number of taps to be reported in the TDCC report, or a second maximum number of TRSs to be reported in the TDCC report, the second maximum number of TRSs being conveyed at least by one of: within a serving cell or across serving cells. UE device 802 further includes means for receiving, from a network entity, at least one index of one or more TRSs associated with the configuration, wherein the measurement report indicates the one or more TRSs based on the at least one index. UE device 802 further includes: means for receiving, from a network entity, a second indication of report content options for sending a measurement report to the network entity, the report content options corresponding to at least one of a TDCC report, a Doppler spread report, or a Doppler shift report; and means for sending, to the network entity, a third indication of report content selected from the report content options for sending a measurement report to the network entity. The means may be TDCC quantization component 140 of UE device 802 configured to perform the functions recited by the means.

[0144] Figure 9 FIG. 900 is an example showing a hardware implementation of one or more network entities 104. One or more network entities 104 may be a base station, a component of a base station, or may implement base station functions. One or more network entities 104 may include or may correspond to at least one of RU 106, DU 108, or CU 110. CU 110 may include CU processor 946, which may have on-chip memory 946'. In some aspects, CU 110 may further include additional memory module 956 and / or communication interface 948, both of which may be coupled to CU processor 946. CU 110 may communicate with DU 108 via an intermediate link 162 (such as the F1 interface between communication interface 948 of CU 110 and communication interface 928 of DU 108).

[0145] DU 108 may include a DU processor 926, which may have an on-chip memory 926'. In some aspects, DU 108 may further include an additional memory module 936 and / or a communication interface 928, both of which may be coupled to the DU processor 926. DU 108 may communicate with the RU 106 via a fronthaul link 160 between the communication interface 928 of the DU 108 and the communication interface 908 of the RU 106.

[0146] RU 106 may include an RU processor 906, which may have an on-chip memory 906'. In some aspects, RU 106 may further include an additional memory module 916, a communication interface 908, and one or more transceivers 930, all of which may be coupled to the RU processor 906. RU 106 may further include an antenna 940, which may be coupled to one or more transceivers 930 such that RU 106 may communicate with the UE 102 via the antenna 940 through one or more transceivers 930.

[0147] The on-chip memories 906', 926', 946' and the additional memory modules 916, 936, 956 may each be regarded as computer-readable media / memories. Each computer-readable media / memory may be non-transitory. Each of the processors 906, 926, 946 is responsible for general processing, including executing software stored on the computer-readable media / memories. The software, when executed by the corresponding processors 906, 926, 946, causes the processors 906, 926, 946 to perform the various functions described herein. The computer-readable media / memories may also be used to store data manipulated by the processors 906, 926, 946 when executing the software. In an example, the measurement report configuration component 150 may be located at one or more network entities 104, such as at the CU 110; at both the CU 110 and the DU 108; at each of the CU 110, the DU 108, and the RU 106; at the DU 108; at both the DU 108 and the RU 106; or at the RU 106.

[0148] As discussed, the measurement report configuration component 150 is configured to: send to the UE a configuration for a measurement report that includes at least one of the following: a TDCC report using configured quantization parameters, a Doppler spread report, or a Doppler shift report, each report being based on a TRS; send to the UE one or more TRSs; send to the UE control signaling that triggers the configuration for the measurement report sent to the UE; and in response to sending the control signaling and one or more TRSs, receive from the UE a measurement report that is based on the configuration. The measurement report configuration component 150 may be within one or more processors of one or more network entities 104, such as within the RU processor 906, the DU processor 926, and / or the CU processor 946. The measurement report configuration component 150 may be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors 906, 926, 946 configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors 906, 926, 946, or a combination thereof.

[0149] One or more network entities 104 may include various components configured for various functions. In an example, one or more network entities 104 include: means for sending to the UE a configuration for a measurement report, the measurement report including at least one of: a TDCC report using configured quantization parameters, a Doppler spread report, or a Doppler shift report, each report being based on one or more TRSs; means for sending to the UE one or more TRSs; means for sending to the UE control signaling that triggers the configuration for the measurement report sent to the UE; and means for receiving from the UE a measurement report in response to the sending of the control signaling and the one or more TRSs, the measurement report being based on the configuration. One or more network entities 104 further include means for receiving from the UE a UE capability report indicating at least one of: the UE's capability for measurement reporting, a first maximum number of taps included in the TDCC report, or a second maximum number of TRSs included in the TDCC report, the second maximum number of TRSs being communicated at least within or across serving cells. One or more network entities 104 further include means for sending to the UE at least one index of one or more TRSs for the configuration, wherein the measurement report indicates one or more TRSs based on the at least one index. One or more network entities 104 further include means for sending to the UE a second indication of report content options for the measurement report, the report content options corresponding to at least one of the TDCC report, the Doppler spread report, or the Doppler shift report; and means for receiving from the UE a third indication of report content selected from the report content options for the measurement report. The means may be a measurement report configuration component 150 of one or more network entities 104 configured to perform the functions recited by the means.

[0150] The specific order or hierarchy of the blocks in the processes and flowcharts disclosed herein are illustrative of example methods. Accordingly, the specific order or hierarchy of the blocks in the processes and flowcharts may be rearranged. Some blocks may also be combined or deleted. The dashed lines may indicate optional elements of the figures. The appended method claims present the elements of the blocks in an example order and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0151] The detailed description set forth herein in connection with the accompanying drawings describes various configurations, but does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for providing a thorough explanation of the various concepts. However, the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0152] Aspects of a wireless communication system, such as a telecommunications system, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0153] An "processing system" including one or more processors can implement an element, or any part of an element, or any combination of elements. Examples of processors include a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system can execute software, which can be referred to as software, firmware, middleware, microcode, hardware description language, or other. Software should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, processes, functions, or any combination thereof.

[0154] If the functions described herein are implemented in software, the functions can be stored on a computer-readable medium, such as a non-transitory computer-readable storage medium, or encoded as one or more instructions or code on the computer-readable medium. A computer-readable medium includes computer storage media and can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures. The storage media can be any available medium that is computer-accessible.

[0155] The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases can be generated via integrated chip implementations and other non-module-component-based devices such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, machine learning (ML)-enabled devices, etc. The scope of the aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular or non-chip-level implementations and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein.

[0156] Devices incorporating the aspects and features described herein may also include additional components and features for implementing and practicing the claimed and described aspects and features. For example, the transmission and reception of wireless signals necessarily involve many components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., in various configurations.

[0157] The description herein is provided to enable a person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but should be construed in view of the full scope of the present disclosure consistent with the language of the claims.

[0158] References to singular elements do not mean "one and only one" unless expressly stated, but rather "one or more." Terms such as "if," "when," and "while" do not imply an immediate temporal relationship or reaction. That is, phrases such as "when" do not mean an immediate action in response to or during the occurrence of an action, but rather mean that a certain action will occur if a certain condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. Unless expressly stated otherwise, the term "some" means one or more. Combinations such as "at least one of A, B, or C" or "one or more of A, B, or C" include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiple A's, multiple B's, and / or multiple C's, or may include only A, only B, or only C. A set should be interpreted as a set of elements where the number of elements is one or more.

[0159] Unless otherwise expressly indicated, ordinal terms such as "first" and "second" do not necessarily imply an order in time, sequence, numerical value, etc., but are used to distinguish different instances of the terms or phrases following each ordinal term.

[0160] Structural and functional equivalents of elements of the various aspects described throughout this disclosure that are known or later become known to those of ordinary skill in the art are hereby expressly incorporated by reference and are covered by the claims. The terms "module", "mechanism", "element", "device", etc. may not be substitutes for the term "means". Accordingly, no claim element shall be construed as means-plus-function unless the claim element is expressly recited using the phrase "means for". As used herein, the phrase "based on" shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless expressly stated otherwise, the phrase "based on A" (where "A" may be information, a condition, a factor, etc.) shall be construed as "at least based on A".

[0161] The following examples are illustrative only and may be combined with other examples or teachings described herein without limitation.

[0162] Example 1 is a method of wireless communication at a UE, comprising: receiving, from a network entity, a configuration for a measurement report that includes at least one of: a TDCC report using configured quantization parameters, a Doppler spread report, or a Doppler shift report, each report being based on measurements of one or more TRSs; receiving, from the network entity, the one or more TRSs; receiving, from the network entity, control signaling triggering the configuration for the measurement report; and, in response to receiving the control signaling and the one or more TRSs, sending the measurement report to the network entity, the measurement report being based on the configuration.

[0163] Example 2 may be combined with Example 1 and further includes sending a UE capability report to the network entity, the UE capability report indicating at least one of: the UE's ability to send the measurement report to the network entity, a first maximum number of taps to be reported in the TDCC report, or a second maximum number of TRSs to be reported in the TDCC report, the second maximum number corresponding to a first TRS associated with a serving cell or a second TRS associated with a cell different from the serving cell.

[0164] Example 3 may be combined with any one of Examples 1 to 2 and includes: the configuration corresponding to at least one of: a first set of TDCC quantization parameters indicated in the configuration, a second set of TDCC quantization parameters indicated in the control signaling, or a third set of TDCC quantization parameters determined at the UE and included in the measurement report.

[0165] Example 4 can be combined with any one of Examples 1 to 3 and includes: The configuration includes a first indication of at least one of the following: a first maximum number of taps to be reported in the TDCC report, a second maximum number of TRSs to be reported in the TDCC report, a third maximum number of taps to be measured for each of the one or more TRSs, a fourth maximum number of taps to be reported for each TRS in the TDCC report, a first number of taps to be reported in the TDCC report, a second number of taps to be reported for each TRS in the TDCC report, a time domain duration for each tap of each TRS, a third number of bits of the quantized NZC for each TRS, the quantized content for each NZC, a fourth number of TDCCs to be reported in the TDCC report, or a symbol offset for the TDCC report.

[0166] Example 5 can be combined with Example 4 and includes: The TDCC report indicates the applied parameters from the configuration.

[0167] Example 6 can be combined with any one of Examples 1 to 5 and includes: The TDCC report indicates at least one of the following: a first strongest tap set, a second strongest tap set after the first strongest tap set, a tap set adjacent to the first strongest tap set, or a tap set associated with at least one of the strongest L1-RSRP or the strongest L1-SINR.

[0168] Example 7 can be combined with Example 6 and includes: The TDCC report indicates taps based on a tap strength index.

[0169] Example 8 can be combined with any one of Examples 1 to 7 and includes: The TDCC report indicates at least one of the magnitude or phase of the TDCC coefficients of each tap reported in the TDCC report.

[0170] Example 9 can be combined with any one of Examples 1 to 2 and further includes receiving at least one index of the one or more TRSs associated with the configuration from the network entity, wherein the measurement report indicates the one or more TRSs based on the at least one index.

[0171] Example 10 can be combined with any one of Examples 1 to 9 and further includes receiving a second indication from the network entity of a reporting content option for reporting content to the network entity, the reporting content option corresponding to at least one of the TDCC report, the Doppler spread report, or the Doppler frequency shift report; and sending a third indication of the reporting content to the network entity, the reporting content being selected from the reporting content options for reporting content to the network entity.

[0172] Example 11 may be combined with any one of Examples 1 to 10 and further includes measuring the TDCC of the measurement report based on at least one of L1-RSRP or L1-SINR for at least one receive antenna port of the UE, where the TDCC of the measurement report corresponds to: a single TDCC associated with all TDCCs measured for the measurement report, or multiple TDCCs associated with each TDCC measured for the measurement report.

[0173] Example 12 is a method of wireless communication at a network entity, including: sending a configuration for a measurement report to a UE, the measurement report including at least one of: a TDCC report using configured quantization parameters, a Doppler spread report, or a Doppler shift report, each report being based on one or more TRSs; sending the one or more TRSs to the UE; sending control signaling to the UE, the control signaling triggering the sending of the configuration for the measurement report to the UE; and in response to sending the control signaling and the one or more TRSs, receiving the measurement report from the UE, the measurement report being based on the configuration.

[0174] Example 13 may be combined with Example 12 and further includes receiving a UE capability report from the UE, the UE capability report indicating at least one of: the UE's capability for the measurement report, a first maximum number of taps included in the TDCC report, or a second maximum number of TRSs included in the TDCC report, the second maximum number corresponding to a first TRS associated with a serving cell or a second TRS associated with a cell different from the serving cell.

[0175] Example 14 may be combined with any one of Examples 12 to 13 and includes: the configuration corresponds to at least one of: a first set of TDCC quantization parameters indicated in the configuration, a second set of TDCC quantization parameters indicated in the control signaling, or a third set of TDCC quantization parameters included in the measurement report.

[0176] Example 15 can be combined with any one of Examples 12 to 14 and includes: The configuration includes a first indication of at least one of the following: a first maximum number of taps included in the TDCC report, a second maximum number of TRSs included in the TDCC report, a third maximum number of taps for each TRS, a fourth maximum number of taps for each TRS in the TDCC report, a first number of taps included in the TDCC report, a second number of taps for each TRS in the TDCC report, a time domain duration of each tap for each TRS, a third number of bits of quantized NZC for each TRS, a quantized content for each NZC, a fourth number of TDCCs included in the TDCC report, or a symbol offset for the TDCC report.

[0177] Example 16 can be combined with Example 15 and includes: The TDCC report indicates at least one of the following: a first strongest tap set, a second strongest tap set after the first strongest tap set, a tap set adjacent to the first strongest tap set, or a tap set associated with at least one of the strongest L1-RSRP or the strongest L1-SINR.

[0178] Example 17 can be combined with any one of Examples 15 to 16 and includes: The TDCC report indicates at least one of the magnitude or phase of the TDCC coefficient of each tap included in the TDCC report.

[0179] Example 18 can be combined with any one of Examples 12 to 17 and further includes sending to the UE at least one index for the one or more TRSs of the configuration, wherein the measurement report indicates the one or more TRSs based on the at least one index.

[0180] Example 19 can be combined with any one of Examples 12 to 18 and further includes sending to the UE a second indication of report content options for the measurement report, the report content options corresponding to at least one of the TDCC report, the Doppler spread report, or the Doppler frequency shift report; and receiving from the UE a third indication of report content selected from the report content options for the measurement report.

[0181] Example 20 is an apparatus for wireless communication for implementing the method according to any one of Examples 1 to 19.

[0182] Example 21 is an apparatus for wireless communication, the apparatus including means for implementing the method according to any one of Examples 1 to 19.

[0183] Example 22 is a non-transitory computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to implement the method according to any one of Examples 1 to 19.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: receiving (508) from a network entity a configuration for a measurement report, the measurement report including at least one of the following: a time-domain channel correlation (TDCC) report using configured quantization parameters, a Doppler spread report, or a Doppler shift report, each report being based on measurements of one or more tracking reference signals (TRS); receiving (350, 450) the one or more TRS from the network entity; and in response to receiving the control signaling and the one or more TRS, sending (520) to the network entity the measurement report, the measurement report being based on the configuration.

2. The method according to claim 1, further comprising: receiving (516) from the network entity control signaling that triggers the configuration for the measurement report.

3. The method according to claim 1, further comprising: measuring the TDCC of the measurement report based on at least one of a layer 1 reference signal received power (L1-RSRP) or a layer 1 signal-to-interference-plus-noise ratio (L1-SINR) for at least one receive antenna port of the UE, wherein the TDCC of the measurement report corresponds to: a single TDCC associated with all TDCCs measured for the measurement report, or multiple TDCCs associated with each TDCC measured for the measurement report.

4. The method according to claim 1, further comprising: sending (506) to the network entity a UE capability report, the UE capability report indicating at least one of the following: the UE's ability to send the measurement report to the network entity, a first maximum number of taps to be reported in the TDCC report, or a second maximum number of TRS to be reported in the TDCC report, the second maximum number corresponding to a first TRS associated with a serving cell or a second TRS associated with a cell different from the serving cell.

5. The method according to any one of claims 1 to 4, wherein the configuration corresponds to at least one of the following: a first set of TDCC quantization parameters indicated in the configuration, a second set of TDCC quantization parameters indicated in the control signaling, or a third set of TDCC quantization parameters determined at the UE and included in the measurement report.

6. The method according to any one of claims 1 to 5, wherein the configuration includes a first indication of at least one of the following: a first maximum number of taps to be reported in the TDCC report, a second maximum number of TRS to be reported in the TDCC report, a third maximum number of taps to be measured for each TRS of the one or more TRS, a fourth maximum number of taps to be reported for each TRS in the TDCC report, a first number of taps to be reported in the TDCC report, a second number of taps to be reported for each TRS in the TDCC report, a time domain duration for each tap of each TRS, The third quantity of bits of the quantized non-zero coefficients (NZCs) for each TRS, The quantized content for each NZC, The fourth quantity of TDCCs to be reported in the TDCC report, or The symbol offset for the TDCC report.

7. The method according to claim 6, wherein the TDCC report indicates the applied parameters from the configuration.

8. The method according to any one of claims 1 to 7, wherein the TDCC report indicates at least one of the following: The first strongest tap set, The second strongest tap set after the first strongest tap set, The second tap set adjacent to the first strongest tap set, or The tap set associated with at least one of the strongest layer 1 reference signal received power (L1-RSRP) or the strongest layer 1 signal-to-interference-plus-noise ratio (L1-SINR).

9. The method according to claim 8, wherein the TDCC report indicates taps based on a tap strength index.

10. The method according to any one of claims 1 to 9, wherein the TDCC report indicates at least one of the magnitude or phase of the TDCC coefficients of each tap reported in the TDCC report.

11. The method according to any one of claims 1 to 10, further comprising: Receiving from the network entity at least one index of the one or more TRSs associated with the configuration, wherein the measurement report indicates the one or more TRSs based on the at least one index.

12. The method according to any one of claims 1 to 11, further comprising: Receiving from the network entity (508) a second indication of a reporting content option for sending the measurement report to the network entity, the reporting content option corresponding to at least one of the TDCC report, the Doppler spread report, or the Doppler shift report; and Sending to the network entity (520) a third indication of the reporting content, the reporting content being selected from the reporting content options for sending the measurement report to the network entity.

13. A method of wireless communication at a network entity, comprising: Sending (508) to a user equipment (UE) a configuration for a measurement report, the measurement report including at least one of the following: A time-domain channel correlation (TDCC) report using configured quantization parameters, A Doppler spread report, or A Doppler shift report, Each report being based on one or more tracking reference signals (TRSs); Sending (350, 450) the one or more TRSs to the UE; and Receiving from the UE (520) the measurement report in response to sending the control signaling and the one or more TRSs, the measurement report being based on the configuration.

14. The method according to claim 13, further comprising: Sending (516) control signaling to the UE, the control signaling triggering the configuration for the measurement report sent to the UE.

15. An apparatus for wireless communication, the apparatus including a transceiver, a memory, and at least one processor, the at least one processor being coupled to the memory and the transceiver, the apparatus being configured to implement the method according to any one of claims 1 to 14.

Images