Time domain channel attribute reporting

Abstract

The present disclosure provides systems, apparatuses, apparatuses, and methods, including computer programs encoded on a storage medium, for TDCP measurement and reporting techniques. The UE (102) receives (312) the TRS from the network entity (304) over a channel between the network entity (304) and the UE (102). The UE (102) measures a TDCP of a channel between the network entity (304) and the UE (102) based on the received (312) TRS. The measurement (314) of the TDCP of the channel is associated with at least one of: an amount of reporting for a configuration of the TDCP report, a CSI processing unit duration for the TDCP report, or a minimum processing delay for the TDCP report. The UE (102) transmits (316) a TDCP report to the network entity (304) based on the measurement (314).

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, and more particularly to time domain channel property (TDCP) measurement and reporting techniques. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) specifies a radio interface called 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 to other types of wireless communication systems, the 5G NR architecture may provide increased data rates, reduced latency, and / or increased capacity.

[0003] Wireless communication systems may generally be configured to provide various telecommunication services (e.g., telephone, video, data, messaging, broadcast, etc.) based on multiple access technologies (such as orthogonal frequency division multiple access (OFDMA) technologies) that support communication with multiple UEs. As mobile broadband technologies develop, improvements in mobile broadband help to continue the advancement of such technologies. For example, a user equipment (UE) moving relative to a base station may experience a phase shift in a channel path between the UE and the base station, which causes the quality of the channel path to degrade. Summary of the invention

[0004] The following presents a simplified overview of one or more aspects 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 the 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 a more detailed description presented later.

[0005] The phase shift in a channel path between a user equipment (UE) and a network entity (such as a base station) may be based on the speed of movement of the UE toward or away from the network entity, the carrier frequency, the angle of arrival (AoA) of the channel path, etc. Although each channel path of a multipath channel may be associated with the same speed of the UE and the same carrier frequency, the different AoAs of different channel paths of the multipath channel may create different phase shifts for each channel path.

[0006] The UE may receive a tracking reference signal (TRS) from a network entity to perform time and frequency offset tracking, such as Doppler shift estimation and / or Doppler spread estimation associated with downlink decoding. However, after the UE receives and measures the TRS from the network entity, the UE may not be configured to report a time domain channel property (TDCP) to the network entity based on the TRS. That is, the UE may utilize the measured TDCP (e.g., Doppler shift estimation and / or Doppler spread estimation) internally without indicating the measured TDCP to the network entity. At the same time, the network entity relies on the channel state information (CSI) measured and reported by the UE to perform processes such as downlink scheduling. For example, in a multiple-input multiple-output (MIMO) system, the network entity may indicate a digital precoder to the UE based on a CSI report received from the UE. However, if the UE is moving at an increased rate relative to the network entity (e.g., a large Doppler shift), the CSI report received from the UE may not be reliable enough for the network entity to efficiently schedule downlink transmission for the UE, which may result in reduced transmission efficiency between the network entity and the UE.

[0007] Aspects of the present disclosure address the above-mentioned and other deficiencies by configuring a UE to transmit a TDCP report to a network entity to assist the network entity in a downlink scheduling procedure for the UE.

[0008] According to some aspects, the UE receives a TRS from the network entity via a channel between the network entity and the UE. The UE measures the TDCP of the channel between the network entity and the UE based on the received TRS. The measurement of the TDCP of the channel is associated with at least one of: a configured reporting amount for TDCP reporting, a CSI processing unit duration for TDCP reporting, or a minimum processing delay for TDCP reporting. The UE transmits a TDCP report to the network entity based on measuring the TDCP of the channel based on the received TRS.

[0009] According to some aspects, the network entity transmits a TRS to the UE via a channel between the UE and the network entity. The network entity receives a TDCP report from the UE based on the transmitted TRS, the TDCP report indicating a measurement of the TDCP of the channel between the UE and the network entity. The measurement of the TDCP of the channel is associated with at least one of: a configured reporting amount for the TDCP report, a CSI processing unit duration for the TDCP report, or a minimum processing delay for the TDCP report.

[0010] To accomplish the aforementioned and related purposes, one or more aspects correspond to the features described below and specifically pointed out in the claims. One or more aspects can be implemented by any of an apparatus, a method, a means for performing the method, and / or a non-transitory computer-readable medium. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features indicate only a few of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 A diagram of a wireless communication system including multiple network entities communicating over multiple cells is shown.

[0012] Figure 2A A first timing diagram of a first channel state information (CSI) processing unit duration associated with periodic / semi-persistent CSI reporting is shown.

[0013] Figure 2B A second timing diagram illustrating a second CSI processing unit duration associated with aperiodic CSI reporting.

[0014] Figure 3 is a signaling diagram illustrating communications between a user equipment (UE) and network entities for a time domain channel property (TDCP) measurement and reporting procedure.

[0015] FIG. 4A to FIG. 4C A number of tables including example TDCP reporting information transmitted from a UE to a network entity are shown.

[0016] Figure 5 is a flow chart of a method for performing TDCP reporting at a UE.

[0017] Figure 6 is a flow chart of a method for performing TDCP reporting at a network entity.

[0018] Figure 7 is a diagram illustrating an example of a hardware implementation of an example UE equipment.

[0019] Figure 8 is a diagram illustrating an example of a hardware implementation of one or more example network entities. DETAILED DESCRIPTION

[0020] Figure 1A diagram 100 of a wireless communication system associated with a plurality of cells 190 is shown. The wireless communication system includes a user equipment (UE) 102 and base stations 104, some of which 104a include an aggregated base station architecture and other base stations 104b include a decomposed base station architecture. The aggregated base station architecture includes a radio unit (RU) 106, a distributed unit (DU) 108, and a centralized 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 decomposed 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 may be co-located with CU 110, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RUs 106. Each of the RU 106, DU 108, and CU 110 may be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU).

[0021] The operation and / or network design of the base station 104 can be based on the aggregation characteristics of the base station functions. For example, a decomposed base station architecture is utilized 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)). Decomposition can include distributing functions between two or more units located at various physical locations, and virtually distributing the functions of at least one unit, which can achieve flexibility in network design. Various units of the decomposed base station architecture or decomposed RAN architecture can be configured to communicate with at least one other unit by wire or wireless communication. For example, CU 110a communicates with DU108a-108b via corresponding mid-haul links based on F1 interfaces. DU 108a-108b can communicate with RU 106a and RU 106b-106c via corresponding front-haul links, respectively. RU 106a-106c can communicate with corresponding UE 102a-102c and 102s via one or more radio frequency (RF) access links based on Uu interface. In an example, multiple RU 106 and / or base station 104 can provide services for UE 102 at the same time, such as the access link of RU 106a of cell 190a and the UE 102a of cell 190e served by base station 104a of cell 190e at the same time.

[0022] One or more CUs 110, such as CU 110a or CU 110d, may communicate directly with the core network 120 via a backhaul link. For example, CU 110d communicates with the core network 120 via a backhaul link based on a next generation (NG) interface. One or more CUs 110 may also communicate indirectly with the core network 120 via 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 may 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 may further communicate with each other via a backhaul link based on an Xn interface. For example, the CU 110d of the base station 104a communicates with the CU 110a of the base station 104b via a backhaul link based on an Xn interface. Similarly, the base station 104a of the cell 190e can communicate with the CU 110a of the base station 104b via a backhaul link based on an Xn interface.

[0023] RU 106, DU 108 and CU 110 and 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 transmit or receive information / signals via a wired or wireless transmission medium. 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 executable instructions of the interface may be configured to provide communication between base stations 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 transmit or receive information / signals via a wired transmission medium (such as a fronthaul link between RU 106d and baseband unit (BBU) 112 of cell 190d, or more specifically, a fronthaul link between RU 106d and DU 108d). The BBU 112 includes the DU 108d and the CU 110d, which may also have a wired interface configured between the DU 108d and the CU 110d to transmit or receive information / signals between the DU 108d and the CU 110d based on a medium-range link. In a further example, a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) may be configured to transmit or receive information / signals via a wireless transmission medium, such as information transmitted between the RU 106a of the cell 190a and the base station 104a of the cell 190e via the cross-cell communication beam of the RU 106a and the base station 104a.

[0024] 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.) can be hosted at CU 110. Each control function can be associated with an interface for transmitting signals based on one or more other control functions hosted at CU 110. User plane functions (such as central unit-user plane (CU-UP) functions), control plane functions (such as central unit-control plane (CU-CP) functions), or a combination thereof can be implemented based on CU 110. For example, CU 110 may include 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 can be based on bidirectional communication with the CU-CP function via an interface (such as an E1 interface (not shown)).

[0025] The CU 110 may communicate with the DU 108 for network control and signal transmission. The DU 108 is a logical unit of the base station 104 that is configured to perform one or more base station functions. For example, the DU 108 may control the operation of one or more RUs 106. One or more of the following may be hosted at the DU 108: a radio link control (RLC) layer, a 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. The DU 108 may host such functions based on the functional division of the DU 108. The DU 108 may similarly host one or more lower PHY layers, where each lower layer or module may be implemented based on an interface for communicating with other layers and modules hosted at the DU 108, or based on a control function hosted at the CU 110.

[0026] The RU 106 may be configured to implement lower layer functions. For example, the RU 106 is controlled by the DU 108 and may 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 the RU 106 may be based on functional partitioning, such as lower layer functional partitioning.

[0027] The RU 106 may transmit or receive over-the-air (OTA) communications with one or more UEs 102. For example, the RU 106b of the cell 190b communicates with the UE 102b of the cell 190b via the first communication beam set 132 of the RU 106b and the second communication beam set 134 of the UE 102b, which may correspond to inter-cell communication beams or inter-cell communication beams. Both real-time and non-real-time features of the control plane and user plane communications of the RU 106 may be controlled by the associated DU 108. Thus, the DU 108 and the CU 110 may be used in a cloud-based RAN architecture (such as a vRAN architecture), and the SMO framework 116 may be used to support non-virtualized and virtualized RAN network elements. For non-virtualized network elements, the SMO framework 116 may support the deployment of dedicated physical resources for RAN coverage, where the dedicated physical resources may be managed through an operation and maintenance interface (such as an 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. The virtualized network elements may include, but are not limited to, RU 106, DU 108, CU 110, near real-time RIC 128, etc.

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

[0029] The non-real-time RIC 118 may 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 may 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 115 may 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 may also deploy the AI / ML model through 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.

[0030] Any combination of RU 106, DU 108, and CU 110, or any reference thereto individually, may correspond to base station 104. Thus, base station 104 may include at least one of RU 106, DU 108, or CU 110. Base station 104 provides UE 102 with access to core network 120. That is, base station 104 may relay communications between UE 102 and core network 120. Base station 104 may 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, cell 190e corresponds to a macro cell, and cells 190a-190d may correspond to a small cell. Small cells include femto cells, micro cells, micro cells, and the like. A cell structure including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network."

[0031] Transmissions from the UE 102 to the base station 104 / RU 106 are referred to as uplink (UL) transmissions, while transmissions from the base station 104 / RU 106 to the UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions, while downlink transmissions may also be referred to as forward link transmissions. For example, the RU 106 d utilizes the antenna of the base station 104 a of the cell 190 d to transmit downlink / forward link communications to the UE 102 d, or receive uplink / reverse link communications from the UE 102 d, based on a Uu interface associated with an access link between the UE 102 d and the base station 104 a / RU 106 d.

[0032] The communication link between UE 102 and 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. UE 102 and base station 104 / RU 106 can utilize Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) spectrum bandwidth allocated per carrier in up to a total of Yx MHz carrier aggregation, where x component carriers (CCs) are used for communication in each direction of the uplink direction and the downlink direction. The carriers may be adjacent to each other along the spectrum, or may not be adjacent to each other. In an example, uplink carriers and downlink carriers may be allocated in an asymmetric manner, and more or fewer carriers may be allocated for uplink or downlink. A component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be associated with a primary cell (PCell), and the secondary component carrier may be associated with a secondary cell (SCell).

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

[0034] The electromagnetic spectrum is typically subdivided into different categories, bands, channels, etc. based on different frequencies / wavelengths associated with the electromagnetic spectrum. The fifth generation (5G) NR is typically associated with two operating bands, referred to as frequency range 1 (FR1) and frequency range 2 (FR2). FR1 ranges from 410MHz–7.125GHz, and FR2 ranges from 24.25GHz–52.6GHz. Although a portion of FR1 is actually greater than 6GHz, FR1 is often referred to as the “below 6GHz” band. In contrast, FR2 is often referred to as the “millimeter wave” (mmW) band. FR2 is different from the “extremely high frequency” (EHF) band, but is an approximate subset of that band, the EHF band ranges from 30GHz–300GHz, and is sometimes also referred to as the “millimeter wave” band. The frequencies between FR1 and FR2 are often referred to as “mid-band” frequencies. The operating band of mid-band frequencies can be referred to as frequency range 3 (FR3), which ranges from 7.125GHz–24.25GHz. The frequency bands within FR3 may include the characteristics of FR1 and / or FR2. Therefore, the characteristics of FR1 and / or FR2 may be extended to mid-band frequencies. Higher operating bands have been identified as extending 5G NR communications to above 52.6 GHz associated with the upper limit of FR2. Three of these higher operating bands include FR2-2 (ranging from 52.6 GHz–71 GHz), FR4 (ranging from 71 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. Therefore, unless otherwise expressly stated herein, the term “below 6 GHz” may refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include mid-band frequencies. Further, unless otherwise expressly stated herein, the term “millimeter wave” or mmW refers to frequencies that may include mid-band frequencies, frequencies that may be within FR2, FR4, FR2-2, and / or FR5, or frequencies that may be within the EHF band.

[0035] UE 102 and base station 104 / RU 106 may each include multiple antennas. 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 transmit directions of RU 106b. UE 102b may receive a downlink beamformed signal from RU 106b based on a second beam set 134 in one or more receive 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 134 in one or more transmit directions of UE 102b. RU 106b may receive an uplink beamformed signal from UE 102b in one or more receive directions of RU 106b. UE 102b may perform beam training to determine the optimal receive and transmit directions of the beamformed signal. The transmit and receive directions of the UE 102 and the base station 104 / RU 106 may be the same, or may be different. In a further example, a beamformed signal may be transmitted between the first base station 104a and the second base station 104b. For example, the RU 106a of the cell 190a may transmit a beamformed signal to the base station 104a of the cell 190e based on the RU beam set 136 in one or more transmit directions of the RU 106a. The base station 104a of the cell 190e may receive a beamformed signal from the RU 106a based on the base station beam set 138 in one or more receive directions of the base station 104a. Similarly, the base station 104a of the cell 190e may transmit a beamformed signal to the RU 106a based on the base station beam set 138 in one or more transmit directions of the base station 104a. The RU 106a may receive a beamformed signal from the base station 104a of the cell 190e based on the RU beam set 136 in one or more receive directions of the RU 106a.

[0036] The base station 104 may include and / or be referred to as a next generation evolved Node B (ng-eNB), a next generation NB (gNB), an evolved NB (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network 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 side link node, a converged (monolithic) base station having a RU 106 and a BBU including a DU 108 and a CU 110, or as a decomposed base station 104b including one or more of the RU 106, the DU 108, and / or the CU 110. The set of converged or decomposed base stations 104a-104b may be referred to as a next generation radio access network (NG-RAN).

[0037] The 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. The 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, the one or more location servers include one or more location / positioning servers, and in addition to one or more of a positioning determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), etc., the one or more location / positioning servers may also include GMLC 125 and LMF 126.

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

[0039] The transmitted signal may also be based on one or more of the satellite positioning systems (SPS) 114, such as signals measured for positioning. In an example, the SPS 114 of the cell 190c may communicate with one or more UEs 102 (such as UE 102c) and one or more base stations 104 / RU 106 (such as RU 106c). The SPS 114 may correspond to one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / position systems. The SPS 114 may be associated with LTE signals, NR signals (e.g., based on round trip time (RTT) and / or multiple RTT), wireless local area network (WLAN) signals, ground beacon systems (TBS), sensor-based information, NR enhanced cell ID (NR E-CID) technology, downlink departure angle (DL-AoD), downlink arrival time difference (DL-TDOA), uplink arrival time difference (UL-TDOA), uplink arrival angle (UL-AoA), and / or other systems, signals, or sensors.

[0040] UE 102 may be configured as a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, a GPS, a multimedia device, a video device, a digital audio player (e.g., a Moving Picture Experts Group (MPEG) Audio Layer 3 (MP3) player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, a utility meter, a gas pump, a home appliance, a healthcare device, a sensor / actuator, a display, or any other device with similar functionality. Some of UE 102 may be referred to as Internet of Things (IoT) devices, such as parking meters, gas pumps, home appliances, vehicles, healthcare equipment, etc. UE 102 may also be referred to as a station (STA), a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handheld device, a mobile client, a 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.

[0041] Still refer to Figure 1In certain aspects, the UE 102 may include a time domain channel property (TDCP) reporting component 140 configured to receive a tracking reference signal (TRS) from a network entity via a channel between the network entity and the UE 102. The TDCP reporting component 140 is further configured to measure the TDCP of the channel between the network entity and the UE 102 based on the received TRS. The measurement of the TDCP of the channel is associated with at least one of: a configured reporting amount for the TDCP report, a channel state information (CSI) processing unit duration for the TDCP report, or a minimum processing delay for the TDCP report. The TDCP reporting component 140 is further configured to transmit a TDCP report to the network entity based on the measured TDCP of the channel.

[0042] In certain aspects, the base station 104 or the network entity of the base station 104 may include a TDCP report processing component 150 configured to transmit a TRS to the UE via a channel between the UE and the network entity. The TDCP report processing component 150 is further configured to receive a TDCP report indicating the measurement of the TDCP of the channel between the UE and the network entity from the UE based on the transmitted TRS. The measurement of the TDCP of the channel is associated with at least one of the following: a configured reporting amount for the TDCP report, a CSI processing unit duration for the TDCP report, or a minimum processing delay for the TDCP report. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies.

[0043] Figure 2A A first timing diagram 200 is shown of a first CSI processing unit duration 211 associated with periodic / semi-persistent CSI reporting. Figure 2B A second timing diagram 250 of a second CSI processing unit duration 213 associated with an aperiodic CSI report is shown. A UE 102 moving toward or away from a base station 104 or a network entity of the base station 104 may experience a phase shift (e.g., Doppler shift) in a channel path between the UE 102 and the base station 104 based on a Doppler effect associated with the movement of the UE 102. The phase shift / Doppler shift may be based on a speed of the UE 102 relative to the base station 104, a carrier frequency, an angle of arrival (AoA) of the channel path, etc. Although each channel path of a multipath channel may be associated with the same speed and the same carrier frequency of the UE 102, different AoAs of different channel paths of the multipath channel may result in different Doppler shifts for each channel path.

[0044] The phase shift of channel path k is calculated based on:

[0045]

[0046]

[0047]

[0048] Where λ indicates the waveform length based on the carrier frequency, t indicates time, and θ k indicates the zenith angle of arrival (ZAoA) of channel path k, indicates the azimuth angle of arrival (AAoA) of channel path k, v0 indicates the moving speed of UE 102, and θ v indicating a first moving direction (eg, a vertical direction), and Indicates a second direction of movement (e.g., horizontal direction). Base station 104 may transmit a channel state information-reference signal (CSI-RS) to UE 102 to track the movement of UE 102 in time and frequency offset. Time and frequency offset tracking may be associated with Doppler shift estimation and / or Doppler spread estimation. CSI-RS for time and frequency offset tracking may be referred to as TRS.

[0049] The TRS may correspond to a CSI-RS resource set indicated in an RRC message parameter (such as trs-Info). The base station 104 may configure a periodic TRS using a high-level parameter (such as trs-Info) based on RRC messaging (e.g., non-zero power (NZP)-CSI-RS-ResourceSet). In a further example, the base station 104 may transmit an aperiodic TRS indicated to the UE via downlink control information (DCI) signaling. The base station 104 may transmit the TRS in 2 symbols of a time slot or in 4 symbols allocated to two consecutive time slots, where 2 CSI-RS resources or 4 CSI-RS resources are configured using a high-level parameter (such as trs-Info) (e.g., in NZP-CSI-RS-ResourceSet). The UE 102 may use the received TRS to estimate the Doppler shift and / or Doppler spread for downlink decoding.

[0050] The non-periodic TRS may be quasi-colocated (QCL) with the periodic TRS, and the base station 104 may provide a QCL indication via the DCI. Further, the base station 104 may configure the QCL type and / or the source reference signal for the QCL signaling. The QCL type of the source reference signal may be configured based on high-level parameters (for example, the QCL type may correspond to the qcl-Type in the QCL-Info parameter). The first QCL type typeA includes values ​​for Doppler shift, Doppler spread, average delay, and delay spread. The second QCL type typeB includes values ​​for Doppler shift and / or Doppler spread. The third QCL type typeC includes values ​​for Doppler shift and / or average delay. The fourth QCL type typed includes values ​​for spatial reception (Rx) parameters.

[0051] The communication link between the UE 102 and the base station 104 may be based on multiple-input multiple-output (MIMO) antenna technology. The base station 104 may select a digital precoder for the UE 102 based on the CSI report received from the UE 102. The base station 104 may configure the CSI report using an information element (IE) (e.g., CSI-reportConfig) of the RRC message so that the UE 102 can use a channel measurement resource (CMR) 203 to measure the downlink channel of the CSI-RS transmitted between the base station 104 and the UE 102. Further, the base station 104 may configure an interference measurement resource (IMR) 205 for the UE 102 to measure interference. The UE may then indicate the measured interference on the IMR to the base station 104 in the CSI report (e.g., based on the CSI-reportConfig parameter). The CMR 203 and the IMR 205 enable the UE 102 to measure the CSI-RS and then report the CSI to the base station 104. The CSI report may include a rank indicator (RI), a precoder matrix indicator (PMI), a channel quality indicator (CQI), and / or a layer indicator (LI). The base station 104 may use the RI and PMI to select a digital precoder for transmission to the UE 102. The CQI indicates the signal to interference plus noise ratio (SINR) used to determine the modulation and coding scheme (MCS). The LI indicates the strongest layer, which may be used for multi-user (MU)-MIMO pairing with low rank transmission and precoder selection for phase tracking reference signal (PT-RS).

[0052] The base station 104 may configure the time domain CSI reporting technique to the UE 102. For example, the base station 104 may configure the UE 102 for periodic / semi-persistent CSI reporting 207 or aperiodic CSI reporting 209 (e.g., using a CSI-reportConfig parameter). The base station 104 activates or deactivates periodic / semi-persistent CSI reporting 207 using a medium access control control element (MAC-CE) indication to the UE 102. In a further example, the base station 104 may trigger aperiodic CSI reporting 209 by transmitting a physical downlink control channel (PDCCH) 201 instruction to the UE 102. The UE 102 may report periodic CSI on a physical uplink control channel (PUCCH) resource (e.g., configured based on the CSI-reportConfig parameter). The UE 102 may report semi-persistent CSI on a PUCCH resource or on a physical uplink shared channel (PUSCH) resource configured based on a DCI received from the base station 104. UE 102 may also report aperiodic CSI on PUSCH resources configured based on DCI received from base station 104 .

[0053] UE 102 may be configured with multiple CSI-reportConfig IEs for multiple CSI measurements and reports. Thus, multiple CSI processing units may be used to process the received CSI-RS in parallel to create multiple CSI measurements and reports. UE 102 may transmit UE capability information to base station 104 indicating the number of CSI processing units supported by UE 102. If the CSI report requested by base station 104 requires more parallel CSI processing at UE 102 than the number of CSI processing units available at the UE (i.e., indicated in the UE capability information), UE 102 may report non-current information for low priority CSI reports. In some examples, UE 102 may determine the priority of a particular CSI report based on a predefined protocol. For example, the CSI processing unit occupancy rules for periodic / semi-persistent CSI reports 207 and aperiodic CSI reports 209 may be based on a predefined protocol.

[0054] The first CSI processing unit duration 211 of the periodic / semi-persistent CSI report 207 corresponds to the CSI processing unit occupied starting from the first symbol of the earliest resource of the CMR 203 or IMR 205 used for measurement by the UE 102. For example, the UE 102 may perform one or more measurements of CSI-RS, CSI interference measurement (CSI-IM), synchronization signal block (SSB), etc. The first CSI processing unit duration 211 of the periodic / semi-persistent CSI report 207 continues through the last resource of the CMR 203 and IMR 205 used for measurement by the UE 102, and ends at the last symbol of the PUSCH / PUCCH used by the UE 102 to transmit the periodic / semi-persistent CSI report 207 to the base station 104.

[0055] The second CSI processing unit duration 213 of the aperiodic CSI report 209 corresponds to the CSI processing unit occupied starting at the first symbol after the PDCCH 201 triggering the aperiodic CSI report 209 is received. The second CSI processing unit duration 213 of the aperiodic CSI report 209 continues through the last resource of the CMR 203 and IMR 205 measured by the UE 102, and ends at the last symbol of the PUSCH used by the UE 102 to transmit the aperiodic CSI report 209 to the base station 104. If the PDCCH 201 triggering the aperiodic CSI report 209 corresponds to two PDCCH candidates in two corresponding search space sets, the PDCCH candidate that ends later in time is used to determine the second CSI processing unit duration 213 of the aperiodic CSI report 209.

[0056] If the PDCCH 201 triggers an initial semi-persistent CSI report on the PUSCH, the CSI processing unit duration of the initial semi-persistent CSI report should not be the same as the first CSI processing unit duration 211 of the periodic / semi-persistent CSI report 207. Instead, the CSI processing unit duration of the initial semi-persistent CSI report may correspond to the second CSI processing unit duration 213 of the aperiodic CSI report 209. That is, after the PDCCH 201, the CSI processing unit duration of the initial semi-persistent CSI report transmitted on the PUSCH starts at the first symbol after the PDCCH 201 and ends at the last symbol of the PUSCH carrying the initial semi-persistent CSI report. If the PDCCH 201 that triggers the initial semi-persistent CSI report corresponds to two PDCCH candidates in two corresponding search space sets, the PDCCH candidate that ends later in time is used to determine the CSI processing unit duration of the initial semi-persistent CSI report.

[0057] CSI reporting by UE 102 may be based on a minimum processing delay time. For example, scheduling of periodic / semi-persistent CSI reporting 207 or aperiodic CSI reporting 209 may include minimum processing delays Z and Z'. The values ​​of Z and Z' for different types of CSI reports may be based on one or more predefined protocols. If the scheduling offset does not indicate a minimum processing delay Z and Z', the UE 102 may report the minimum processing delay associated with non-current CSI, or ignore the triggering DCI if no other signals (e.g., data or hybrid automatic repeat request (HARQ)-acknowledgement (ACK) (HARQ-ACK)) are to be transmitted on the PUSCH triggered by the DCI (e.g., PDCCH 201). If the CSI request field of the DCI is used to trigger one or more CSI reports from UE 102 on the PUSCH, the first uplink symbol associated with the one or more CSI reports is used as no earlier than symbol Z. ref UE 102 may transmit one or more CSI reports to base station 104 if the timing of the start of the nth CSI report is advanced by 0.1% or more. For example, if the first uplink symbol associated with the nth CSI report is not earlier than symbol Z′ ref (n) starts, UE 102 may transmit the nth triggered CSI report to base station 104.

[0058] Some CSI feedback techniques may not include UE reporting of one or more TDCPs to the base station 104. Instead, the UE 102 may internally utilize one or more TDCPs (such as Doppler shift and / or Doppler spread measured from the TRS) for the CSI reporting process, but does not report the one or more TDCPs to the base station 104. The lack of information about the TDCP measured at the UE 102 may cause the base station 104 to rely on the CSI measured and reported to the base station 104 to perform further scheduling. If the UE 102 is moving at an increased rate relative to the base station 104, an increased Doppler shift may occur, which may cause the CSI report received from the UE 102 to be inaccurate. Therefore, the base station 104 may not be able to select an appropriate precoder for the downlink transmission, which may reduce the transmission efficiency.

[0059] Therefore, the transmission of the TDCP report to the base station 104 by the UE 102 assists the base station 104 in scheduling downlink transmissions for the UE 102. The base station 104 can determine whether the channel is undergoing significant changes based on the TDCP report, so that the base station 104 can further determine whether to request additional CSI feedback or a sounding reference signal (SRS) for antenna beam control. If the TDCP report indicates a significant change in channel conditions, the base station 104 can trigger SRS for antenna switching to measure the downlink precoder based on uplink and downlink channel reciprocity. However, the SRS-based resources are dedicated resources for the UE 102, and the SRS technology may increase system overhead. If the TDCP report does not indicate a significant channel change, the base station 104 can trigger a CSI report based on the PDCCH 201. However, by Figure 2B and Figure 2A As shown in the comparison, the PDCCH triggering technique may be associated with increased latency.

[0060] The base station 104 may generate a channel prediction or a channel eigenvector prediction based on the reported TDCP received from the UE 102, so that the base station 104 may further generate a second prediction for the precoder based on the past precoder matrix and the reported TDCP. The base station 104 transmits a trigger indication to the UE 102 so that the UE 102 transmits a TDCP report to the base station 104. The UE 102 may determine the CSI processing unit occupancy rule and the minimum processing delay for the TDCP report after receiving the trigger indication. If the base station 104 configures multiple TRSs for the TDCP measurement at the UE 102, the UE 102 may select / determine the TDCP to be included in the TDCP report. FIG. 2A to FIG. 2B The CSI report does not include TDCP information. Figure 3 As discussed, UE 102 may transmit a TDCP report including TDCP information to the network so that the network may make scheduling determinations for channels associated with changing channel conditions.

[0061] Figure 3300 is a signaling diagram illustrating communication between a UE 102 and a network entity 304 for a TDCP measurement and reporting procedure. The network entity 304 may correspond to a base station 104 or an entity at the base station 104 such as a RU 106, a DU 108, a CU 110, etc. The UE 102 may report 306 UE capabilities to the network entity 304 for TDCP measurement and reporting. For example, the UE capabilities may correspond to a first UE capability for TDCP measurement and a second UE capability for TDCP reporting. The UE 102 may transmit 306 in the UE capability information an indication of the following: a first maximum number of TRSs that may be received 312 per CSI-reportConfig for TDCP reporting, a second maximum number of TRSs that may be received 312 across CSI-reportConfigs for TDCP reporting, and / or a third maximum number of CSI-reportConfigs that may be received 312 for TDCP reporting. The maximum number may be counted per component carrier (CC), per frequency band, per frequency band combination, and / or per UE. The UE 102 may also transmit 306 an indication of parameters supported by the UE 102 for TDCP measurements (eg, number of CSI-RS resources per TRS, minimum bandwidth of a TRS, etc.).

[0062] The network entity 304 transmits 308 a CSI configuration for TDCP reporting to the UE 102 based on the UE capability information received 306 from the UE 102. For example, the CSI configuration transmitted 308 to the UE 102 may include a CMR configuration for TDCP measurement. The network entity 304 may configure N TRSs based on RRC parameters (not shown; occurring after 308 or in association with 308). In an example, the RRC parameters may also be associated with an RRC reconfiguration message or a system information block (SIB) from the network entity 304 to the UE 102. The SIB may correspond to an existing type of SIB (e.g., SIB1) or a different type of SIB (e.g., SIBJ, where J is an integer greater than 21) transmitted by the network entity 304. In a further example, N TRSs may be configured for TDCP measurement in CSI-reportConfig. Therefore, N NZP-CSI-RS-ResourceSets may be configured for resourcesForChannelMeasurement.

[0063] In some examples, network entity 304 configures N TRSs for TDCP measurement based on an RRC message, but instructs the UE to select M TRSs to perform TDCP measurement via a MAC-CE or DCI, where 0 < M ≤ N. Network entity 304 may configure N TRSs for TDCP measurement based on CSI-reportConfig. Accordingly, N NZP-CSI-RS-ResourceSets can be configured for resourcesForChannel Measurement such that network entity 304 can use a MAC-CE to indicate the M TRSs to be measured at UE 102 for 314.

[0064] The MAC-CE may indicate a serving cell index, which may correspond to the serving cell index of the CSI-reportConfig used for TDCP measurement. In a further example, the MAC-CE may indicate a bandwidth part (BWP) index, which may correspond to the BWP index of the CSI-reportConfig used for TDCP measurement. In yet a further example, the MAC-CE may indicate a CSI-reportConfigId, which may correspond to the identifier (ID) of the corresponding CSI-reportConfig used for TDCP measurement. In yet another example, the MAC-CE may indicate a bitmap of the TRSs to be measured at UE 102 for 314, which may correspond to the activation / deactivation status of the TDCP measurement for each TRS configured via the CSI-reportConfig used for TDCP measurement. When using a triggering DCI, network entity 304 transmits 310 to UE 102 a trigger for TDCP reporting. Network entity 304 may indicate different values in the CSI request field to indicate different TRSs that will be transmitted 312 to UE 102 for TDCP measurement. For example, network entity 304 may configure different TRSs for TDCP measurement for different CSI-AssociatedReportConfigInfo.

[0065] The network entity 304 determines a TRS to transmit 312 to the UE 102 for TDCP measurement based on a transmission configuration indicator (TCI) state of the PDCCH / PDSCH associated with the TRS. The network entity 304 may indicate the TRS for QCL indication in the TCI state. The UE 102 measures 314 TDCP based on receiving 312 the TRS from the network entity 304. For example, the TRS transmitted 312 to the UE 102 may reflect channel distortion and multipath between the UE 102 and the network entity 304, so that the UE 102 may determine various channel properties based on the distortion. The UE 102 may measure 314 TDCP and transmit 316 a TDCP report using a TRS for a QCL type other than typeD (associated with spatial Rx parameters).

[0066] When the TCI state of the PDCCH / PDSCH changes dynamically, the UE 102 may use the TRS indicated for QCL typeD to perform TDCP measurements and reports. If multiple TCI states are indicated for the PDCCH / PDSCH, the UE 102 may use a TRS in one of the TCI states for TDCP measurements, such as a TRS in a TCI state with a lowest TCI state ID value. In other examples, the UE 102 may use all TRSs in TCI states for TDCP measurements. If the UE 102 measures more than one TRS to generate a TDCP report, the UE 102 may measure 314 more than one TDCP.

[0067] If the number of TRSs received 312 by UE 102 for TDCP measurement (e.g., determined based on the TCI state of PDCCH / PDSCH) is greater than the reported number of TRSs transmitted 306 in the UE capability information, the UE 102 may select one or more TRSs for TDCP measurement and reporting based on the periodicity of the TRSs, the TCI state ID value, the control resource set (CORESET) ID, or the search space ID.

[0068] The TRS transmitted 312 to the UE 102 for TDCP measurement may correspond to a configuration of a first TRS associated with 2 CSI-RS resources and / or a second TRS associated with 4 CSI-RS resources. The network entity 304 may configure the TRS associated with 2 CSI-RS resources as a CMR for TDCP reporting based on periodic TRS and configure the TRS associated with 4 CSI-RS resources as a CMR for TDCP reporting based on aperiodic TRS. The network entity 304 may avoid transmitting an IMR configuration for TDCP measurement. For example, the network entity 304 may avoid configuring the UE 102 based on csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference in the CSI-reportConfig transmitted 308 to the UE 102.

[0069] The network entity 304 may configure the TDCP reporting quantity for TDCP reporting via an RRC parameter (eg, based on reportQuantity). The multipath channel between the network entity 304 and the UE 102 may correspond to:

[0070]

[0071] where α k Corresponding to the time-independent parameter, f k corresponds to the Doppler shift, and K corresponds to the maximum number of paths for the multipath channel. A multipath channel may be indicated based on:

[0072]

[0073] f min =min{f1, f2, ... f k}

[0074] For CSI reports, (f k -f min ) may correspond to the CSI variation due to the Doppler effect.

[0075] The network entity 304 may configure the UE 102 via an RRC message information element (e.g., reportQuantity) to report the Doppler shift of the strongest path of the multipath channel based on a channel impulse response (CIR) estimated using a TRS transmitted 312 to the UE 102. In a further example, the network entity may configure the UE 102 via an RRC message parameter (e.g., reportQuantity) to report the maximum Doppler shift of the X strongest paths of the multipath channel based on the CIR estimated using the TRS transmitted 312 to the UE 102, where the value of X may be predefined, configured based on an RRC message, or indicated via a MAC-CE or DCI. Alternatively, the UE 102 may determine the value of X based on the received power associated with each path of the multipath channel and a threshold power difference from the strongest path. Paths including a received power higher than the received power of the strongest path minus the threshold power difference may be included in the X strongest paths. The power may be quantified in units of decibel milliwatts (dBm), and the threshold may be quantified in units of decibels (dB). The threshold may be predefined (eg, 3 dB) or configured based on RRC messaging via CSI-reportConfig.

[0076] In a further example, the network entity 304 may configure the UE 102 via RRC messaging (e.g., reportQuantity) to report the Doppler spread of the X strongest paths based on the CIR estimated using the TRS transmitted 312 to the UE 102. The delay spread may correspond to the maximum Doppler shift of the X strongest paths minus the minimum Doppler shift. In a further example, the network entity 304 may configure the UE 102 via RRC messaging (e.g., reportQuantity) to report the relative Doppler shift of the strongest path based on the CIR estimated using the TRS transmitted 312 to the UE 102. The relative Doppler shift may correspond to the Doppler shift minus the minimum Doppler shift of all paths of the multipath channel. In a further example, the network entity 304 can configure the UE 102 via RRC messaging (e.g., reportQuantity) to report a maximum relative Doppler shift for the X strongest paths based on the CIR estimated using the TRS transmitted 312 to the UE 102. The maximum relative Doppler shift can correspond to the Doppler shift minus the minimum Doppler shift for all paths of the multipath channel or the X strongest paths of the multipath channel.

[0077] The network entity 304 may configure the UE 102 to report both Doppler shift and Doppler spread. The network entity 304 may also configure the UE 102 via RRC messaging (e.g., reportQuantity) to report the Doppler shift or relative Doppler shift of the X strongest paths based on the CIR estimated using the TRS transmitted 312 to the UE 102. The network entity 304 may also configure the UE 102 via RRC messaging (e.g., reportQuantity) to report, in addition to the Doppler shift and / or Doppler spread, the layer 1 (L1) reference signal received power (RSRP) (L1-RSRP) or L1-SINR measured 314 by the UE 102 based on the TRS transmitted 312 to the UE 102.

[0078] When the UE 102 is configured (e.g., based on CSI-reportConfig) to measure 314 M TDCPs associated with M TRSs transmitted 312 to the UE 102, the network entity 304 and the UE 102 may determine that M CSI processing units are occupied. The duration of the CSI processing unit may be different for different TRSs received 312 from the network entity 304. For example, the CSI processing unit duration for periodic / semi-persistent TDCP reporting may start at the first symbol of the TRS and end at the first symbol of the PUCCH / PUSCH including the TRS report or at the next symbol after the last symbol of the PUCCH / PUSCH including the TRS report. The CSI processing unit duration for non-periodic TDCP reporting may start at the first symbol of the DCI that triggers the 310 TDCP report or at the next symbol after the last symbol of the DCI that triggers the 310 TDCP report, and end at the first symbol of the PUCCH / PUSCH including the TRS report or at the next symbol after the last symbol of the PUCCH / PUSCH including the TRS report.

[0079] In some examples, the CSI processing unit may include a common duration for all M TRSs. The CSI processing unit duration for periodic / semi-persistent TDCP reporting may start at the first symbol of each of the M TRSs and end at the next symbol after the last symbol of the PUCCH / PUSCH including the TRS report. The CSI processing unit duration for aperiodic TDCP reporting may start at the first symbol of the DCI that triggers 310 TDCP reporting or at the next symbol after the last symbol of the DCI that triggers 310 TDCP reporting, and end at the first symbol of the PUCCH / PUSCH including the TDCP report or at the next symbol after the last symbol of the PUCCH / PUSCH including the TDCP report. In a further example, when the UE 102 (e.g., based on CSI-reportConfig) is configured to measure 314 M TDCPs associated with the M TRSs transmitted 312 to the UE 102, the network entity 304 and the UE 102 may determine that 1 CSI processing unit is occupied. For both periodic / semi-persistent TDCP reporting and aperiodic TDCP reporting, the start and end symbols of 1 CSI processing unit duration may correspond to the same symbols used by the CSI processing unit duration associated with M TRSs.

[0080] When the UE 102 (e.g., based on CSI-reportConfig) is configured to measure 314 M TDCPs associated with M TRSs transmitted 312 to the UE 102, the network entity 304 and the UE 102 may determine that X CSI processing units are occupied, where the value of X corresponds to the number of strongest paths in the multipath channel. The UE 102 may determine the value of X based on the number of TRSs that overlap in the time domain. The TRSs may overlap in the time domain if two TRSs are transmitted 312 at overlapping symbols or overlapping time slots. Alternatively, the TRSs may overlap in the time domain if the two TRSs have overlapping time domain durations. The duration of the TRS may start at the first symbol of the TRS and end at Y symbols after the last symbol of the TRS, where the UE measures the TDCP within Y symbols and Y is an integer higher than 0, which may be predefined or reported by the UE.

[0081] The network entity 304 may also determine the value of X and the value of M based on UE capability information received 306 from the UE 102. The UE 102 may indicate in the UE capability information the UE capability for a maximum number of TRSs per CSI processing unit (which may be represented as T), such that the network entity 304 may determine the value of X based on X=ceil(M / T), where “ceil” refers to a function for rounding to the next highest integer.

[0082] If the network entity 304 triggers 310 multiple CSI-reportConfigs associated with more CSI processing units than the maximum number of CSI processing units indicated in the UE capability information, the UE 102 may report non-current CSI or non-current TDCP with a low priority CSI report. The priority of the TDCP report transmitted 316 to the network entity 304 may be different from the priority of other types of CSI reports. The network entity 304 and the UE 102 may determine the priority of a CSI report (such as a TDCP report) based on the time domain characteristics of the CSI report (such as whether the CSI report is periodic, semi-persistent, or aperiodic). The priority of the CSI report may also be based on the CSI-reportConfigId, the serving cell ID, and / or the reporting amount (e.g., Doppler shift, Doppler spread, etc.).

[0083] In an example, the priority of the TDCP report transmitted 316 to the network entity 304 may be based on the Pri iCSI (y, k, c, s) = 2·N 小区 ·M s y+N 小区 ·M s ·k+M s ·c+s, where if the priority value is lower, the actual priority of the TDCP report is higher (for example, priority 0 corresponds to a higher priority than priority 1). A value of k=0 may indicate a CSI report including L1-RSRP or L1-SINR information, a value of k=1 may indicate a CSI report not including L1-RSRP, L1-SINR or TDCP information, and a value of k=2 may indicate a CSI report including TDCP information. Further, y=0 indicates an aperiodic CSI report transmitted on PUSCH, y=1 indicates a semi-persistent CSI report transmitted on PUSCH, y=2 indicates a semi-persistent CSI report transmitted on PUCCH, and y=3 indicates a periodic CSI report transmitted on PUCCH. c corresponds to a serving cell index, and N 小区 Corresponds to the value of the higher layer parameter maxNrofServingCells. s corresponds to reportConfigID, and M s Corresponds to the value of the higher layer parameter maxNrofCSI-ReportConfigurations.

[0084] In an alternative example, k=0 may indicate a CSI report including TDCP information, k=1 may indicate a CSI report including L1-RSRP or L1-SINR information, and k=2 may indicate a CSI report not including L1-RSRP, L1-SINR, or TDCP information. In yet another alternative example, k=0 may indicate a CSI report including L1-RSRP or L1-SINR information, k=1 may indicate a CSI report including TDCP information, and k=2 may indicate a CSI report not including L1-RSRP, L1-SINR, or TDCP information. In yet another alternative example, k=0 may indicate a CSI report including L1-RSRP, L1-SINR, or TDCP information, and k=1 may indicate a CSI report not including L1-RSRP, L1-SINR, or TDCP information.

[0085] The minimum processing delay for TDCP reporting may be predefined for UE 102. For example, the minimum processing delay for TDCP reporting may be the same as the delay (e.g., Z3, Z3') used for L1-RSRP reporting. Alternatively, the minimum processing delay for TDCP reporting may be the same as the delay (e.g., Z1, Z1') used for CSI reporting based on Type1 codebook. The values ​​of Z1 and Z3 may be based on a predefined table, where Z1 and Z1' indicate a first delay for low complexity CSI reporting, and Z3 and Z3' indicate a second delay for L1-RSRP reporting. In a further example, the minimum processing delay may be based on the minimum processing delay for L1-RSRP reporting and the number of configured M TRSs and the number of CSI processing units of the CSI-reportConfig for TDCP measurement C. The minimum processing delay may be calculated based on ceil(M / C)*Z3, ceil(M / C)*Z3'. In a further example, the minimum processing delay for TDCP reporting corresponds to the minimum processing delay for CSI reporting based on Type1 codebook and the number of configured M TRSs and the number of CSI processing units of CSI-reportConfig for TDCP measurement C. Therefore, the minimum processing delay can be calculated based on ceil(M / C)*Z1, ceil(M / C)*Z1'.

[0086] The UE 102 may report the UE capability of the minimum processing delay (Z, Z′) for TDCP reporting in the UE capability information transmitted 306 to the network entity 304. The minimum processing delay of the CSI-reportConfig with M TRSs for TDCP measurement corresponds to (M*Z, M*Z′). In another example, the minimum processing delay of the CSI-reportConfig with M TRSs and C CSI processing units for TDCP measurement C corresponds to ceil(M / C)*Z, ceil(M / C)*Z′. In a further example associated with the maximum number of configured TRSs, the minimum processing delay of the CSI-reportConfig with M TRSs for TDCP measurement corresponds to (Z, Z′).

[0087] UE 102 may measure 314 TDCP based on wideband operation. For example, UE 102 may measure 314 TDCP based on the entire bandwidth of the corresponding TRS. TDCP (such as Doppler shift and / or Doppler spread) can be quantized as a phase shift associated with a certain duration. In an example, UE 102 can report multiple bits to indicate Doppler shift and / or Doppler spread. The quantization of multiple bits defines what the multiple bits indicate. For example, Doppler shift and / or Doppler spread may be quantized based on a phase shift in the range of (0, 360) degrees. Therefore, 2 bits may be used to quantize the phase shift, where based on '00': 0-90 degrees; '01': 90-180 degrees; '10': 180-270 degrees; '11': 270-360 degrees, the step size may be 90 degrees. The duration may be predefined or configured based on RRC messaging from network entity 304. The predefined duration may correspond to the duration of a time slot for an active uplink / downlink BWP or subframe based on a subcarrier spacing (SCS). The UE 102 may also determine the duration based on a symbol spacing between two symbols of the TRS received 312 for the TDCP measurement. Alternatively, the TDCP may be quantized based on an absolute value of the Doppler shift and / or Doppler spread, which may be indicated in Hertz (Hz) or kilohertz (kHz). The Doppler shift can be calculated based on Calculate Doppler spread. TDCP can be quantized as 2πf based on the coefficients of Doppler shift and Doppler spread calculation. k and 2π(f k -f min ), or quantized as f k and (f k -f min ). FIG. 4A to FIG. 4C It shows that it can be based on Figure 3An example TDCP report generated by the TDCP measurement and reporting process shown.

[0088] FIG. 4A to FIG. 4C Table 410 - 430 shows an example TDCP report message including TDCP report information transmitted 316 from UE 102 to network entity 304. If UE 102 is configured to transmit 316 TDCP reports based on M TRS transmissions for TDCP measurement (e.g., including Doppler shift and / or Doppler spread), then UE 102 may report V TDCPs in the TDCP report transmitted 316 to network entity 304, where 0 < V ≤ M. If V is less than M, then UE 102 may report V CSI - RS resource set indices and report V quantized TDCPs in the TDCP report transmitted 316 to network entity 304. The CSI - RS resource set index indicates the resource sets from the lowest NZP - CSI - RS - ResourceSetId to the highest NZP - CSI - RS - ResourceSetId configured for TDCP measurement. The TDCP report may be transmitted 316 to network entity 304 based on an absolute reporting technique associated with the maximum TDCP value or the minimum TDCP value, or the TDCP report may be transmitted 316 to network entity 304 based on a differential reporting technique using the first TDCP as a reference point.

[0089] The first table 410 includes example information of the TDCP report, which indicates at least one TDCP report quantity (e.g., Doppler shift, Doppler spread, etc.) for the TRS. Specifically, when reporting the CSI - RS resource set index in the TDCP report transmitted 316 to network entity 304, the first table 410 indicates the CSI - RS resource set indices 1 - V. When reporting the CSI - RS resource set index in the TDCP report transmitted 316 to network entity 304, the first table 410 also indicates the TDCPs for the CSI - RS resource set indices 1 - V. Since the TDCP report associated with the first table 410 corresponds to at least one TDCP report quantity, at least the TDCP for the CSI - RS resource set index 1 is reported in the TDCP report transmitted 316 to network entity 304.

[0090] The second table 420 includes example information of a TDCP report indicating more than one TDCP reporting amount (e.g., Doppler shift and Doppler spread) for a single TRS. Specifically, when the CSI-RS resource set index is reported in the TDCP report transmitted 316 to the network entity 304, the second table 420 indicates the CSI-RS resource set index 1-V. When the CSI-RS resource set index is reported in the TDCP report transmitted 316 to the network entity 304, the second table 420 also indicates the first TDCP (e.g., Doppler shift) and the second TDCP (e.g., Doppler spread) for the CSI-RS resource set index 1-V. Since the TDCP report associated with the second table 420 corresponds to more than one TDCP reporting amount, at least the first TDCP and the second TDCP for the CSI-RS resource set index 1 are recorded in the TDCP report transmitted 316 to the network entity 304.

[0091] The third table 430 includes example information of a TDCP report indicating a joint TDCP and beam report (e.g., L1-RSRP). Specifically, when the CSI-RS resource set index is reported in the TDCP report transmitted 316 to the network entity 304, the third table 430 indicates the CSI-RS resource set index 1-V. When the CSI-RS resource set index is reported in the TDCP report transmitted 316 to the network entity 304, the third table 430 also indicates TDCP and L1-RSRP information for the CSI-RS resource set index 1-V. The L1-RSRP for the CSI-RS resource set index 2-V may correspond to a differential L1-RSRP value relative to the L1-RSRP value of the CSI-RS resource set index 1. Because the TDCP report associated with the third table 430 corresponds to a joint TDCP and beam report (e.g., L1-RSRP), at least TDCP and L1-RSRP for CSI-RS resource set index 1 are reported in the TDCP report transmitted 316 to the network entity 304. Some TDCP reports may also indicate L1-SINR information.

[0092] In the event that the value of V is the same as the value of M, the UE 102 may not transmit the CSI-RS resource set index to the network entity 304. The value of V may be configured to the UE 102 based on RRC messaging from the network entity 304 (such as, via an RRC parameter in CSI-reportConfig). The UE 102 may determine the value of V based on the number of TCI states associated with the PDCCH / PDSCH. The UE 102 may indicate the value of V in the TDCP report after selecting a TRS for which to report beam quality (e.g., L1-RSRP / L1-SINR). The UE 102 measures 314 the selected TRS and transmits 316 a TDCP report of the TRS associated with the L1-RSRP / L1-SINR above a threshold. The threshold may be predefined or configured based on RRC messaging from the network entity 304. In a further example, the UE 102 may determine the threshold as the L1-RSRP of the strongest TRS minus an offset, where the offset may be predefined or configured based on RRC messaging from the network entity 304 .

[0093] When the UE 102 transmits 316 a TDCP report on the PUCCH / PUSCH, the value of V may be reported in CSI Part 1 and other information (such as the information included in Tables 410-430) may be reported in CSI Part 2. If the TDCP report is transmitted 316 with another CSI report, the TDCP may be reported in CSI Part 1 or CSI Part 2 in different implementations. CSI Part 1 may include a fixed payload size and may be used to identify the number of information bits in CSI Part 2. The entire contents of CSI Part 1 are transmitted to the network entity 304 before CSI Part 2 is transmitted to the network entity 304. Figure 3 4 to 4 illustrate the TDCP measurement and reporting process and an example TDCP report. Figures 5 and 6 A method for implementing one or more aspects of the TDCP measurement and reporting process is shown. Specifically, Figure 5 UE 102 is shown Figure 3 To an implementation of one or more aspects of FIG. 4 . Figure 6 The network entity 304 is shown Figure 3 To an implementation of one or more aspects of FIG. 4 .

[0094] Figure 5 A flowchart 500 of a method of wireless communication at a UE is shown. Figure 1 and Figure 7The method may be performed by UE 102, UE equipment 702, etc., which may include a memory 724' and may correspond to the entire UE 102 or UE equipment 702, or components of the UE 102 or UE equipment 702 such as a wireless baseband processor 724 and / or an application processor 706.

[0095] UE 102 transmits 506 UE capability information to the network entity, the information indicating at least one of: a first UE capability for measuring TDCP of a channel between the network entity and the UE or a second UE capability for transmitting a TDCP report to the network entity. Figure 3 , the UE 102 transmits 306 UE capabilities for TDCP measurement and reporting to the network entity 304. The TDCP reporting component 140 of the UE 102 or the UE equipment 702 may perform the transmission 506.

[0096] The UE 102 receives 508 a TDCP configuration based on the UE capability information—the TDCP configuration indicating a TDCP reporting structure of at least one of: a configured reporting amount for TDCP reporting, a CSI processing unit duration for TDCP reporting, or a minimum processing delay for TDCP reporting. Figure 3 , the UE 102 receives 308 a CSI configuration for TDCP reporting based on transmitting 306 the UE capabilities for TDCP measurement and reporting to the network entity 304. The receiving 508 may be performed by the TDCP reporting component 140 of the UE 102 or the UE equipment 702.

[0097] UE 102 receives 510 a trigger indication for TDCP reporting from a network entity. Figure 3 , the UE 102 receives 310 a TDCP reporting trigger from the network entity 304. The receiving 510 may be performed by the TDCP reporting component 140 of the UE 102 or the UE equipment 702.

[0098] UE 102 receives 512 TRS from a network entity via a channel between the network entity and the UE. Figure 3 , the UE 102 receives 312 a TRS from the network entity 304. The receiving 512 may be performed by the TDCP reporting component 140 of the UE 102 or the UE equipment 702.

[0099] The UE 102 measures 514 a TDCP of a channel between the network entity and the UE based on the received TRS—the measurement of the TDCP of the channel being associated with at least one of: a configured reporting amount for TDCP reporting, a CSI processing unit duration for TDCP reporting, or a minimum processing delay for TDCP reporting. Figure 3 Based on receiving 312 the TRS from the network entity 304, the UE 102 measures 314 the TDCP of the channel between the network entity 304 and the UE 102 based on the configured TDCP reporting amount, CSI processing unit occupancy duration, and / or minimum processing delay for the TDCP reporting. The TDCP reporting component 140 of the UE 102 or UE equipment 702 may perform the measurement 514.

[0100] The UE 102 transmits 516 a TDCP report to the network entity based on the TDCP measurement of the channel. Figure 3 , the UE 102 transmits 316 a TDCP report to the network entity 304 based on the TDCP measurement of the configured TDCP reporting amount, CSI processing unit occupancy duration and / or minimum processing delay for the TDCP report. The TDCP reporting component 140 of the UE 102 or UE equipment 702 may perform the transmission 516.

[0101] UE 102 transmits 530 to the network entity at least one of an L1-RSRP report or an L1-SINR report for measuring the TRS of the TDCP of the channel. Figure 3 and Figure 4C The TDCP report transmitted 316 to the network entity 304 may correspond to the third table 430 including the L1-RSRP information. The TDCP reporting component 140 of the UE 102 or UE equipment 702 may perform the transmission 530. Figure 5 A method from the UE side of a wireless communication link is described, while Figure 6 A method from the network side of a wireless communication link is described.

[0102] Figure 6 600 is a flow chart of a method of wireless communication at a network entity. Figure 1 and Figure 8 The method may be performed by the base station 104 or one or more network entities 804 at the base station 104, which may correspond to the RU 106, the DU 108, the CU 110, the RU processor 842, the DU processor 832, the CU processor 812, etc. The base station 104 or one or more network entities 804 at the base station 104 may include a memory 812' / 832' / 842', which may correspond to the entirety of one or more network entities 804 or base station 104, or a component of one or more network entities 804 or base station 104 such as the RU processor 842, the DU processor 832, or the CU processor 812.

[0103] The base station 104 or one or more network entities at the base station 104 receives 606 UE capability information indicating at least one of: a first UE capability for measuring TDCP of a channel between the UE and the network entity or a second UE capability for TDCP reporting to the network entity. Figure 3 , the base station 104 or one or more network entities at the base station 104 receives 306 UE capabilities for TDCP measurement and reporting from the UE 102. The TDCP report processing component 150 of the base station 104 or one or more network entities at the base station 104 (such as the RU 106, DU 108 and / or CU 110) can perform the receiving 606.

[0104] The base station 104 or one or more network entities at the base station 104 transmits 608 a TDCP configuration based on the UE capability information—the TDCP configuration indicating a TDCP reporting structure of at least one of: a configured reporting amount for TDCP reporting, a CSI processing unit duration for TDCP reporting, or a minimum processing delay for TDCP reporting. For example, referring to Figure 3 , the base station 104 or one or more network entities at the base station 104 transmits 308 a CSI configuration for TDCP reporting based on the UE capabilities for TDCP measurement and reporting received 306 from the UE 102. The TDCP report processing component 150 of the base station 104 or one or more network entities at the base station 104 (such as the RU 106, DU 108 and / or CU 110) can perform the transmission 608.

[0105] The base station 104 or one or more network entities at the base station 104 transmits 610 a trigger indication for TDCP reporting to the UE. Figure 3 , the network entity 304 transmits 310 a TDCP report trigger to the UE 102. The transmission 610 may be performed by the TDCP report processing component 150 of the base station 104 or one or more network entities at the base station 104, such as the RU 106, DU 108, and / or CU 110.

[0106] The base station 104 or one or more network entities at the base station 104 transmits 612 the TRS to the UE via a channel between the UE and the network entity. Figure 3 , the base station 104 or one or more network entities at the base station 104 transmits 312 the TRS to the UE 102. The TDCP report processing component 150 of the base station 104 or one or more network entities at the base station 104 (such as the RU 106, DU 108 and / or CU 110) may perform the transmission 612.

[0107] The base station 104 or one or more network entities at the base station 104 receives 616 a TDCP report from the UE based on the transmitted TRS, the TDCP report indicating a measurement of the TDCP of a channel between the UE and the network entity—the measurement of the TDCP of the channel being associated with at least one of: a configured reporting amount for the TDCP report, a CSI processing unit duration for the TDCP report, or a minimum processing delay for the TDCP report. For example, referring to Figure 3 , the base station 104 or one or more network entities at the base station 104, after transmitting 312 the TRS to the UE 102, receives 316 from the UE 102 a TDCP report associated with a configured TDCP reporting amount, a CSI processing unit occupancy duration, and / or a measurement 314 of a minimum processing delay for the TDCP report. The TDCP report processing component 150 of the base station 104 or one or more network entities at the base station 104 (such as the RU 106, the DU 108, and / or the CU 110) may perform the receiving 616.

[0108] The base station 104 or one or more network entities at the base station 104 receives 630 from the UE at least one of an L1-RSRP report or an L1-SINR report for measuring the TRS of the TDCP of the channel. Figure 3 and Figure 4C , the TDCP report received 316 from the UE 102 may correspond to a third table 430 including L1-RSRP information. Figure 7 The UE equipment 702 described in the flowchart 500 may perform the method of the flowchart 500. The base station 104 or one or more network entities 804 ( Figure 8 The method of flowchart 600 may be executed as described in the accompanying drawings.

[0109] Figure 7 700 is a diagram illustrating an example of a hardware implementation of a UE equipment 702. The equipment 702 may be a UE 102, a component of a UE 102, or may implement UE functionality. In some aspects, the equipment 702 may include a wireless baseband processor 724 (also referred to as a modem) coupled to one or more transceivers 722 (e.g., a wireless RF transceiver). The wireless baseband processor 724 may include on-chip memory 724'. In some aspects, the equipment 702 may further include one or more subscriber identity module (SIM) cards 720 and an application processor 706 coupled to a secure digital (SD) card 708 and a screen 710. The application processor 706 may include on-chip memory 706'.

[0110] Equipment 702 may further include a Bluetooth module 712, a WLAN module 714, an SPS module 716 (e.g., a GNSS module), and a cellular module 717 located within one or more transceivers 722. The Bluetooth module 712, the WLAN module 714, the SPS module 716, and the cellular module 717 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 712, the WLAN module 714, the SPS module 716, and the cellular module 717 may include their own dedicated antennas and / or communicate using antenna 780. Equipment 702 may further include one or more sensor modules 718 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional module for memory 726, a power supply 730, and / or a camera 732.

[0111] The wireless baseband processor 724 communicates with another UE 102 and / or with a RU associated with the base station 104 via one or more antennas 780 through the transceiver 722. The wireless baseband processor 724 and the application processor 706 can each include a computer-readable medium / memory 724', 706', respectively. The additional modules of the memory 726 can also be regarded as computer-readable media / memory. Each computer-readable medium / memory 724', 706', 726 can be non-temporary. The wireless baseband processor 724 and the application processor 706 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. When the software is executed by the wireless baseband processor 724 / application processor 706, it causes the wireless baseband processor 724 / application processor 706 to perform the various functions described. The computer-readable medium / memory can also be used to store data manipulated by the wireless baseband processor 724 / application processor 706 when executing the software. The wireless baseband processor 724 / application processor 706 can be a component of the UE 102. The equipment 702 may be a processor chip (modem and / or applications) and include only the wireless baseband processor 724 and / or the application processor 706 , and in another configuration, the equipment 702 may be the entire UE 102 and include additional modules of the equipment 702 .

[0112] As discussed, the TDCP reporting component 140 is configured to receive TRS from the network entity through a channel between the network entity and the UE 102. The TDCP reporting component 140 is further configured to measure the TDCP of the channel between the network entity and the UE 102 based on the received TRS. The measurement of the TDCP of the channel is associated with at least one of the following: the configured reporting amount for the TDCP report, the CSI processing unit duration for the TDCP report, or the minimum processing delay for the TDCP report. The TDCP reporting component 140 is further configured to transmit the TDCP report to the network entity based on the TDCP of the measured channel. The TDCP reporting component 140 may be located in the wireless baseband processor 724, the application processor 706, or in both the wireless baseband processor 724 and the application processor 706. The TDCP reporting component 140 may be one or more hardware components explicitly configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof.

[0113] As shown, the equipment 702 may include various components configured for various functions. In one configuration, the equipment 702 and specifically the wireless baseband processor 724 and / or the application processor 706 include: a component for receiving a TRS from a network entity through a channel between the network entity and the UE; a component for measuring the TDCP of the channel between the network entity and the UE based on the received TRS, the measurement of the TDCP of the channel being associated with at least one of: a configured reporting amount for a TDCP report, a CSI processing unit duration for a TDCP report, or a minimum processing delay for a TDCP report; and a component for transmitting a TDCP report to the network entity based on the measurement. The equipment 702 further includes a component for transmitting UE capability information to the network entity, the UE capability information indicating at least one of: a first UE capability for measuring the TDCP of the channel or a second UE capability for transmitting a TDCP report to the network entity. The equipment 702 further includes a component for receiving a TDCP configuration based on the UE capability information, the TDCP configuration indicating a TDCP reporting structure of at least one of the following: a configured reporting amount for the TDCP report, a CSI processing unit duration for the TDCP report, or a minimum processing delay for the TDCP report. The equipment 702 further includes a component for transmitting at least one of an L1-RSRP report or an L1-SINR report of a TRS for the TDCP of the measurement channel to the network entity. The component for transmitting the TDCP report to the network entity is further configured to: receive a trigger indication for the TDCP report from the network entity. The component can be a TDCP reporting component 140 of the equipment 702 configured to perform the functions described by the component.

[0114] Figure 8 800 is a diagram illustrating an example of a hardware implementation of one or more network entities 804. The one or more network entities 804 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 804 may include at least one of a CU 110, a DU 108, or a RU 106. For example, depending on the layer functionality handled by the TDCP report processing component 150, the one or more network entities 804 may include a CU 110; both a CU 110 and a DU 108; each of a CU 110, a DU 108, and a RU 106; a DU 108; both a DU 108 and a RU 106; or a RU 106.

[0115] The CU 110 may include a CU processor 812. The CU processor 812 may include an on-chip memory 812'. In some aspects, the CU 110 may further include an additional memory module 814 and a communication interface 818. The CU 110 communicates with the DU 108 via a mid-range link (such as an F1 interface). The DU 108 may include a DU processor 832. The DU processor 832 may include an on-chip memory 832'. In some aspects, the DU 108 may further include an additional memory module 834 and a communication interface 838. The DU 108 communicates with the RU 106 via a front-end link. The RU 106 may include a RU processor 842. The RU processor 842 may include an on-chip memory 842'. In some aspects, the RU 106 may further include an additional memory module 844, one or more transceivers 846, an antenna 880, and a communication interface 848. The RU 106 communicates wirelessly with the UE 102.

[0116] On-chip memory 812 ', 832 ', 842 ' and additional memory modules 814, 834, 844 can each be considered a computer readable medium / memory. Each computer readable medium / memory can be non-transitory. Each of the processors 812, 832, 842 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various described functions. The computer readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0117] As discussed, the TDCP report processing component 150 is configured to transmit a TRS to the UE via a channel between the UE and the network entity. The TDCP report processing component 150 is further configured to receive a TDCP report indicating the measurement of the TDCP of the channel between the UE and the network entity from the UE based on the transmitted TRS. The measurement of the TDCP of the channel is associated with at least one of the following: the configured report amount for the TDCP report, the CSI processing unit duration for the TDCP report, or the minimum processing delay for the TDCP report. The TDCP report processing component 150 may be located in one or more processors of one or more of the CU 110, DU 108, and RU 106. The TDCP report processing component 150 may be one or more hardware components explicitly configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof.

[0118] One or more network entities 804 may include various components configured for various functions. In one configuration, one or more network entities 804 include: a component for transmitting a TRS to a UE through a channel between the UE and the network entity; and a component for receiving a TDCP report from the UE based on the transmitted TRS, the TDCP report indicating the measurement of the TDCP of the channel between the UE and the network entity, and the measurement of the TDCP of the channel is associated with at least one of the following: a configured report amount for the TDCP report, a CSI processing unit duration for the TDCP report, or a minimum processing delay for the TDCP report. One or more network entities 804 further include a component for receiving UE capability information, the UE capability information indicating at least one of the following: a first UE capability for measuring the TDCP of the channel or a second UE capability for the TDCP report for TDCP reporting to the network entity. One or more network entities 804 further include a component for transmitting a TDCP configuration based on the UE capability information, the TDCP configuration indicating a TDCP reporting structure of at least one of the following: a configured report amount for the TDCP report, a CSI processing unit duration for the TDCP report, or a minimum processing delay for the TDCP report. The one or more network entities 804 further include a component for receiving at least one of an L1-RSRP report or an L1-SINR report of a TRS for TDCP of a measurement channel from a UE. The component for receiving a TDCP report from a UE is further configured to transmit a trigger indication for a TDCP report to the UE. The component may be a TDCP report processing component 150 of the one or more network entities 804 configured to perform the functions described by the component.

[0119] The specific order or hierarchy of the boxes in the process and flow chart disclosed herein is an illustration of an example means. Therefore, the specific order or hierarchy of the boxes in the process and flow chart can be rearranged. Some boxes can also be merged or deleted. The optional boxes of the process and flow chart can be indicated with dotted lines. The attached method claims present elements of each box in an example order and are not limited to the specific order or hierarchy presented in the claims, process and flow chart.

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

[0121] Various aspects of wireless communication systems (such as telecommunication systems) are presented with reference to various equipment and methods. These equipment and methods are described in the detailed description that follows and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

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

[0123] If the functions described herein are implemented in software, the functions may be stored on a computer-readable medium (such as a non-transitory computer-readable storage medium) or encoded as one or more instructions or codes on the computer-readable medium. Computer-readable media include computer storage media and may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage devices, magnetic disk storage devices, 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 medium can be any available medium that is accessible to a computer.

[0124] The aspects, implementations, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases may 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 / procurement devices, medical devices, artificial intelligence (AI)-enabled devices, machine learning (ML)-enabled devices, and the like. The aspects, implementations, and / or use cases may 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 techniques described herein.

[0125] Devices incorporating the various aspects and features described herein may also include additional components and features for implementing and practicing the various aspects and features claimed and described. For example, the transmission and reception of wireless signals necessarily include 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 may 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.

[0126] The description herein is provided to enable those 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 may be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be interpreted in view of the full scope of the disclosure consistent with the language of the claims.

[0127] Unless explicitly stated, references to singular elements do not mean "one and only one", but rather "one or more". Terms such as "if", "when ..." and "at ..." do not imply an immediate temporal relationship or reaction. That is, these phrases (such as "when ...") do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply mean that if a certain condition is met, an action will occur, but no specific or immediate time constraints are required for the occurrence of the action. Unless explicitly stated otherwise, the term "some" refers to 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, multiple B, and / or multiple C, or may include only A, only B, or only C. A set should be interpreted as a set of elements in which the number of elements is one or more.

[0128] The structural equivalents and functional equivalents of the elements of various aspects described in the entire disclosure known or later learned by those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. The words "module", "mechanism", "element", "device", etc. may not be substitutes for the word "component". Therefore, unless the phrase "component for ..." is used to clearly state the claim element, any claim element shall not be interpreted as a means plus function. As used herein, the phrase "based on" should not be interpreted as a reference to a closed information set, one or more conditions, one or more factors, etc. In other words, unless clearly stated differently, the phrase "based on A" (where "A" can be information, conditions, factors, etc.) should be interpreted as "at least based on A".

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

[0130] Example 1 is a method of wireless communication at a UE, comprising: receiving a TRS from a network entity via a channel between the network entity and the UE; measuring a TDCP of the channel between the network entity and the UE based on the received TRS, the measurement of the TDCP of the channel being associated with at least one of: a configured reporting amount for a TDCP report, a CSI processing unit duration for a TDCP report, or a minimum processing delay for a TDCP report; and transmitting a TDCP report to the network entity based on the measurement of the TDCP of the channel.

[0131] Example 2 may be combined with Example 1, and further include transmitting UE capability information to the network entity, the UE capability information indicating at least one of: a first UE capability for measuring TDCP of a channel or a second UE capability for transmitting a TDCP report to the network entity.

[0132] Example 3 can be combined with any one of Examples 1-2, and further includes receiving a TDCP configuration based on UE capability information, the TDCP configuration indicating a TDCP reporting structure of at least one of: a configured reporting amount for TDCP reporting, a CSI processing unit duration for TDCP reporting, or a minimum processing delay for TDCP reporting.

[0133] Example 4 can be combined with Example 3 and includes that the TDCP configuration is received as part of an RRC message and corresponds to an available TRS set for the TDCP of the measurement channel, and the example includes selecting at least a TRS subset of the available TRS set for the TDCP of the measurement channel based on at least one of MAC-CE or DCI.

[0134] Example 5 can be combined with any of Examples 1-4 and includes a report amount for the configuration of the TDCP report corresponding to at least one of: a first maximum number of TRSs per TDCP configuration, a second maximum number of TRSs across multiple TDCP configurations, or a third maximum number of TDCP configurations for the TDCP report.

[0135] Example 6 may be combined with any of Examples 1-5 and include the TRS being configured to be in a TCI state of at least one of a PDCCH or a PDSCH associated with the TRS.

[0136] Example 7 can be combined with any of Examples 1-6 and include a TDCP report indicating at least one of: a Doppler shift of one or more strongest paths, a maximum Doppler shift of a strongest path among one or more strongest paths, a relative Doppler shift of one or more strongest paths, a maximum relative Doppler shift of the strongest path among one or more strongest paths, or a Doppler spread of one or more strongest paths.

[0137] Example 8 may be combined with any of Examples 1-7 and include that the one or more strongest paths are based on a CIR associated with the TRS.

[0138] Example 9 can be combined with Example 7 and include that the number of one or more strongest paths is at least one of the following: configured based on an RRC message, configured based on MAC-CE, indicated based on DCI, based on a predefined protocol, based on RSRP associated with multiple paths including the one or more strongest paths, or based on a threshold power difference with the strongest path among the one or more strongest paths.

[0139] Example 10 may be combined with any one of Examples 1-9, and further comprises transmitting at least one of an L1-RSRP report or an L1-SINR report for measuring a TRS of a TDCP of a channel to a network entity.

[0140] Example 11 may be combined with any of Examples 1-10 and include a first number of CSI processing units occupied by the UE during a CSI processing unit duration being based on a second number of TDCPs of the channel measured by the UE for a corresponding number of TRSs.

[0141] Example 12 may be combined with any of Examples 1-11, and include transmitting the TDCP report to the network entity further comprising: receiving a trigger indication for the TDCP report from the network entity.

[0142] Example 13 may be combined with any of Examples 1-12 and include prioritizing the TDCP report relative to at least one of: the L1-RSRP report, the L1-SINR report, or the CSI report excluding the L1-RSRP report, the L1-SINR report, and the TDCP report.

[0143] Example 14 may be combined with any of Examples 1-13 and include a minimum processing delay for a TDCP report being based on a processing time of at least one of a CSI report, an L1-RSRP report, a first number of CSI processing units, or a corresponding number of TRSs.

[0144] Example 15 may be combined with any of Examples 4-13, and include the TDCP report indicating a first total number of TDCPs for the channel that is less than or equal to a second total number of at least a subset of TRSs in the available TRS set selected for measuring the TDCP for the channel.

[0145] Example 16 may be combined with Example 15 and include the TDCP report further indicating at least one of: a corresponding first total number of CSI-RS resource set indices, a beam report, or a CSI report.

[0146] Example 17 may be combined with any of Examples 1-16 and include the TDCP report being associated with at least one of: a phase shift over a duration, a first absolute value of a Doppler shift, a second absolute value of a Doppler spread, or a coefficient for calculating a phase shift over a duration.

[0147] Example 18 is a method of wireless communication at a network entity, comprising: transmitting a TRS to a UE via a channel between the UE and the network entity; and receiving a TDCP report from the UE based on the transmitted TRS, the TDCP report indicating a measurement of the TDCP of the channel between the UE and the network entity, the measurement of the TDCP of the channel being associated with at least one of: a configured reporting amount for the TDCP report, a CSI processing unit duration for the TDCP report, or a minimum processing delay for the TDCP report.

[0148] Example 19 may be combined with Example 18, and further include receiving UE capability information indicating at least one of: a first UE capability for TDCP measurement of a channel or a second UE capability for TDCP reporting to a network entity.

[0149] Example 20 can be combined with any one of Examples 18-19 and further includes transmitting a TDCP configuration based on UE capability information, wherein the TDCP configuration indicates a TDCP reporting structure of at least one of: a configured reporting amount for TDCP reporting, a CSI processing unit duration for TDCP reporting, or a minimum processing delay for TDCP reporting.

[0150] Example 21 can be combined with Example 20 and includes the TDCP configuration being transmitted as part of an RRC message and corresponding to an available TRS set for measurement of the TDCP of the channel, and the example includes selecting at least a subset of TRS in the available TRS set for measurement of the TDCP of the channel based on at least one of MAC-CE or DCI.

[0151] Example 22 can be combined with any of Examples 18-21 and includes a reporting amount for a TDCP report configuration corresponding to at least one of: a first maximum number of TRSs per TDCP configuration, a second maximum number of TRSs across multiple TDCP configurations, or a third maximum number of TDCP configurations for a TDCP report.

[0152] Example 23 may be combined with any of Examples 18-22 and include the TRS being configured to be in a TCI state of at least one of a PDCCH or a PDSCH associated with the TRS.

[0153] Example 24 can be combined with any of Examples 18-23 and include a TDCP report indicating at least one of: a Doppler shift of one or more strongest paths, a maximum Doppler shift of a strongest path among one or more strongest paths, a relative Doppler shift of one or more strongest paths, a maximum relative Doppler shift of the strongest path among one or more strongest paths, or a Doppler spread of one or more strongest paths.

[0154] Example 25 may be combined with any of Examples 18-24 and include the one or more strongest paths being based on a CIR associated with the TRS.

[0155] Example 26 can be combined with Example 24 and include that the number of the one or more strongest paths is at least one of: configured based on an RRC message, configured based on MAC-CE, indicated based on DCI, based on a predefined protocol, based on RSRP associated with multiple paths including the one or more strongest paths, or based on a threshold power difference with the strongest path among the one or more strongest paths.

[0156] Example 27 may be combined with any of Examples 18-26, and further include receiving at least one of an L1-RSRP report or an L1-SINR report of a measured TRS for a TDCP of a channel from a UE.

[0157] Example 28 may be combined with any of Examples 18-27 and include a first number of CSI processing units occupied during a CSI processing unit duration being based on a second number of TDCPs of channels measured for a corresponding number of TRSs.

[0158] Example 29 may be combined with any of Examples 18-28, and include receiving the TDCP report from the UE further comprising: transmitting a trigger indication for the TDCP report to the UE.

[0159] Example 30 may be combined with any of Examples 18-29 and include prioritizing the TDCP report relative to at least one of: the L1-RSRP report, the L1-SINR report, or the CSI report excluding the L1-RSRP report, the L1-SINR report, and the TDCP report.

[0160] Example 31 may be combined with any of Examples 18-30 and include a minimum processing delay for a TDCP report being based on a processing time of at least one of a CSI report, an L1-RSRP report, a first number of CSI processing units, or a corresponding number of TRSs.

[0161] Example 32 may be combined with any of Examples 18-31 and include the TDCP report indicating a first total number of TDCPs for the channel that is less than or equal to a second total number of at least a subset of TRSs in the available TRS set selected for measuring the TDCP for the channel.

[0162] Example 33 may be combined with Example 32, and include the TDCP report further indicating at least one of: a corresponding first total number of CSI-RS resource set indices, a beam report, or a CSI report.

[0163] Example 34 can be combined with any of Examples 18-33 and include the TDCP report being associated with at least one of: a phase shift over a duration, a first absolute value of a Doppler shift, a second absolute value of a Doppler spread, or a coefficient for calculating a phase shift over a duration.

[0164] Example 35 is an apparatus for wireless communication for implementing a method as described in any of Examples 1-34.

[0165] Example 36 is an apparatus for wireless communications that includes components for implementing a method as described in any of Examples 1-34.

[0166] Example 37 is a non-transitory computer readable medium storing computer executable code, which, when executed by at least one processor, causes the at least one processor to implement the method as described in any one of Examples 1-34.

Claims

1. A method of wireless communication at a user equipment (UE), comprising: receiving a tracking reference signal (TRS) from the network entity via a channel between the network entity and the UE; measuring a time domain channel property (TDCP) of the channel between the network entity and the UE based on the received TRS, the measurement of the TDCP of the channel being associated with at least one of: a configured reporting amount for a TDCP report, a channel state information (CSI) processing unit duration for the TDCP report, or a minimum processing delay for the TDCP report; as well as The TDCP report is transmitted to the network entity based on the measurement of the TDCP of the channel.

2. The method of claim 1, further comprising: UE capability information is transmitted to the network entity, the UE capability information indicating at least one of: a first UE capability for measuring the TDCP of the channel or a second UE capability for transmitting the TDCP report to the network entity.

3. The method according to any one of claims 1 to 2, further comprising: A TDCP configuration is received based on the UE capability information, the TDCP configuration indicating a TDCP reporting structure of at least one of: the configured reporting amount for the TDCP report, the CSI processing unit duration for the TDCP report, or the minimum processing delay for the TDCP report.

4. The method of claim 3, wherein the TDCP configuration is received as part of a radio resource control (RRC) message and corresponds to an available TRS set for measuring the TDCP of the channel, and wherein at least a subset of TRSs in the available TRS set is selected for measuring the TDCP of the channel based on at least one of a media access control-control element (MAC-CE) or downlink control information (DCI).

5. The method of any one of claims 1-4, wherein the configured reporting amount for the TDCP report corresponds to at least one of: a first maximum number of TRSs per TDCP configuration, a second maximum number of TRSs across multiple TDCP configurations, or a third maximum number of TDCP configurations for the TDCP report.

6. A method as described in any one of claims 1-5, wherein the TRS is configured to be in a transmission configuration indicator (TCI) state of at least one of a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH) associated with the TRS.

7. A method as described in any one of claims 1-6, wherein the TDCP report indicates at least one of the following: a Doppler shift of one or more strongest paths, a maximum Doppler shift of the strongest path among the one or more strongest paths, a relative Doppler shift of the one or more strongest paths, a maximum relative Doppler shift of the strongest path among the one or more strongest paths, or a Doppler spread of the one or more strongest paths.

8. The method of any of claims 1-7, wherein the one or more strongest paths are based on a channel impulse response (CIR) associated with the TRS.

9. The method of claim 7, wherein the number of the one or more strongest paths is at least one of: configured based on the RRC message, configured based on the MAC-CE, indicated based on the DCI, based on a predefined protocol, based on a reference signal received power (RSRP) associated with a plurality of paths including the one or more strongest paths, or based on a threshold power difference from the strongest path among the one or more strongest paths.

10. The method of any one of claims 1-9, further comprising transmitting to the network entity at least one of a Layer 1 (L1) RSRP (L1-RSRP) report or a L1 signal to interference plus noise ratio (SINR) (L1-SINR) report of the TRS of the TDCP for measuring the channel.

11. The method of any one of claims 1-10, wherein a first number of CSI processing units occupied by the UE during the CSI processing unit duration is based on a second number of TDCPs of the channel measured by the UE for a corresponding number of TRSs.

12. The method according to any one of claims 1 to 11, wherein transmitting the TDCP report to the network entity further comprises: A trigger indication for the TDCP report is received from the network entity.

13. The method of any one of claims 1-12, wherein the TDCP report is prioritized relative to at least one of: the L1-RSRP report, the L1-SINR report, or a CSI report excluding the L1-RSRP report, the L1-SINR report, and the TDCP report.

14. The method of any one of claims 1-13, wherein the minimum processing delay for the TDCP report is based on a processing time of at least one of the CSI report, the L1-RSRP report, the first number of CSI processing units, or the corresponding number of TRSs.

15. The method of any one of claims 4-13, wherein the TDCP report indicates a first total number of TDCPs for the channel, the first total number being less than or equal to a second total number of the at least the TRS subset in the available TRS set selected for measuring the TDCP for the channel.

16. The method of claim 15, wherein the TDCP report further indicates at least one of: a corresponding first total number of CSI reference signal (CSI-RS) resource set indices, a beam report, or the CSI report.

17. The method of any one of claims 1-16, wherein the TDCP report is associated with at least one of: a phase shift over a duration, a first absolute value of the Doppler shift, a second absolute value of the Doppler spread, or a coefficient used to calculate the phase shift over the duration.

18. A method of wireless communication at a network entity, comprising: transmitting a tracking reference signal (TRS) to a user equipment (UE) via a channel between the UE and the network entity; as well as A time domain channel property (TDCP) report is received from the UE based on the transmitted TRS, the TDCP report indicating a measurement of the TDCP of the channel between the UE and the network entity, the measurement of the TDCP of the channel being associated with at least one of: a configured reporting amount for the TDCP report, a channel state information (CSI) processing unit duration for the TDCP report, or a minimum processing delay for the TDCP report.

19. The method of claim 18, further comprising: UE capability information is received, the UE capability information indicating at least one of: a first UE capability for the measurement of the TDCP of the channel or a second UE capability for TDCP reporting for the TDCP report to the network entity.

20. The method of any one of claims 18-19, further comprising: A TDCP configuration is transmitted based on the UE capability information, the TDCP configuration indicating a TDCP reporting structure of at least one of: the configured reporting amount for the TDCP report, the CSI processing unit duration for the TDCP report, or the minimum processing delay for the TDCP report.

21. An apparatus for wireless communication, comprising a memory and at least one processor, the at least one processor being coupled to the memory and configured to implement the method of any one of claims 1-20.

Images