A method for CSI reporting with type II codebook for high speeds.

Abstract

A system and method for channel state information (CSI) reporting with a Type II codebook for high speeds are provided. In some embodiments, the method includes determining when to apply Doppler-domain compression and when to avoid Doppler-domain compression when feeding back CSI reporting, determining a signaled number of CSI instances for which a network node requests a UE to calculate CSI, and determining whether to apply CSI compression in the Doppler domain based on the number of CSI instances. Some proposed solutions enable the network and UE to support cases with and without Doppler-domain compression under a single CSI reporting framework. Based on signaling received from the network, the solutions enable the UE to determine when to feed back a selected Doppler-domain base and when to avoid Doppler-domain base selection in Type II CSI reporting.

Description

[Technical Field]

[0001] Related Applications This application claims the benefit of Provisional Patent Application No. 63 / 409,394, filed September 23, 2022, the entire disclosure of which is incorporated herein by reference.

[0002] TECHNICAL FIELD This disclosure relates generally to reporting channel state information (CSI). [Background technology]

[0003] Multi-antenna techniques can significantly increase the data rates and reliability of wireless communication systems. Performance is particularly improved when both the transmitter and receiver are equipped with multiple antennas, resulting in a multiple-input multiple-output (MIMO) communication channel. Such systems and / or related techniques are commonly referred to as MIMO.

[0004] The New Radio (NR) standard is currently evolving with enhanced MIMO support. Core components in NR are MIMO antenna deployment and support for MIMO-related techniques, such as spatial multiplexing. Spatial multiplexing mode aims for high data rates in favorable channel conditions. An illustration of spatial multiplexing operation is provided in FIG. 1.

[0005] As can be seen, the information-carrying symbol vector s is multiplied by an NT×r precoder matrix W, which serves to distribute the transmission energy among subspaces of the NT-dimensional vector space (corresponding to the NT antenna ports). The precoder matrix is ​​typically selected from a codebook of possible precoder matrices and is typically indicated by a precoder matrix indicator (PMI), which specifies a unique precoder matrix in the codebook for a given number of symbol streams. Each of the r symbols in s corresponds to a layer, and r is called the transmission rank. In this way, spatial multiplexing is achieved, since multiple symbols can be transmitted simultaneously on the same time / frequency resource element (TFRE). The number of symbols r is typically adapted to suit the current channel properties.

[0006] NR uses OFDM in the downlink (and DFT-precoded OFDM in the uplink for rank-1 transmission), so the received NR×1 vector yn for a TFRE on subcarrier n (or alternatively, number n of data TFREs) is therefore yn=HnWsn+en It is modeled by where en is the noise / interference vector obtained as a realization of a random process. The precoder W may be a wideband precoder, which is either constant over frequency or frequency selective.

[0007] The precoder matrix W is often chosen to match the characteristics of the NR×NT MIMO channel matrix Hn, resulting in so-called channel-dependent precoding, which is also commonly referred to as closed-loop precoding, and essentially strives to concentrate the transmitted energy in a subspace that is strong in the sense that it transfers most of the transmitted energy to the UE.

[0008] In closed-loop precoding for the NR downlink, the UE sends a recommendation to the gNB of a preferred precoder to use based on channel measurements in the downlink. The gNB may configure the UE to provide feedback according to CSI-ReportConfig, transmit CSI-RS, and configure the UE to use the CSI-RS measurements to feed back a recommended precoding matrix that the UE selects from a codebook. A single precoder that is considered to cover a large bandwidth (wideband precoding) may be fed back. It may also be beneficial to feed back a frequency-selective precoding report, e.g., several precoders, one per subband, that match the frequency variations of the channel. This is an example of a more general case of channel state information (CSI) feedback, which also encompasses feeding back other information besides the recommended precoder to assist the gNodeB in subsequent transmissions to the UE. Such other information may include a channel quality indicator (CQI) as well as a transmission rank indicator (RI). In NR, CSI feedback can be either wideband, where one CSI is reported for the entire channel bandwidth, or frequency-selective, where one CSI is reported for each subband, which is defined as the number of adjacent resource blocks spanning between 4 PRBs and 32 PRBs, depending on the size of the bandwidth part (BWP).

[0009] Given CSI feedback from the UE, the gNB determines the transmission parameters it wants to use to transmit to the UE, including the precoding matrix, transmission rank, and modulation and coding scheme (MCS). These transmission parameters may differ from the recommendation made by the UE. The transmission rank, and therefore the number of spatially multiplexed layers, is reflected in the number of columns of the precoder W. For efficient performance, it is important that a transmission rank that matches the channel properties is selected.

[0010] In the case of multi-user MIMO (MU-MIMO), two or more users in the same cell are co-scheduled on the same time-frequency resource(s). That is, two or more independent data streams are transmitted simultaneously to different UEs, and the spatial domain can generally be used to separate each stream. By transmitting several streams simultaneously, the system capacity can be increased. However, this comes at the expense of reducing the SINR per stream, since power must be shared between the streams, causing the streams to interfere with each other.

[0011] Channel State Information Reference Signal (CSI-RS)

[0012] For CSI measurement and feedback, a CSI-RS is defined. The CSI-RS is transmitted on each antenna port and used by the UE to measure the downlink channel between each transmit antenna port and each receive antenna port. A transmit antenna port is also referred to as a CSI-RS port. The supported number of antenna ports in NR is {1, 2, 4, 8, 12, 16, 24, 32}. By measuring the received CSI-RS, the UE can estimate the channel traversed by the CSI-RS, including the radio propagation channel and antenna gain. The CSI-RS for the above purpose is also referred to as a non-zero power (NZP) CSI-RS.

[0013] CSI-RS may be configured to be transmitted in some REs in a slot and in some slots. Figure 2 shows an example of CSI-RS REs for 12 antenna ports, where one RE per RB per port is shown.

[0014] Additionally, an interference measurement resource (IMR) for a UE to measure interference is also specified in NR. The IMR resource contains four REs, either four adjacent REs in frequency in the same OFDM symbol, or 2 × 2 adjacent REs in both time and frequency in a slot. By measuring both the channel based on the NZP CSI-RS and the interference based on the IMR, the UE can estimate the effective channel and noise-plus-interference to determine the CSI, i.e., rank, precoding matrix, and channel quality.

[0015] Additionally, a UE in NR may be configured to measure interference based on one or more NZP CSI-RS resources.

[0016] CSI Framework in NR

[0017] In NR, a UE may be configured with multiple CSI reporting settings and multiple CSI-RS resource settings. Each resource setting may include multiple resource sets, and each resource set may include up to eight CSI-RS resources. For each CSI reporting setting, the UE feeds back a CSI report.

[0018] Each CSI reporting setting includes at least the following information: CSI-RS resource set for channel measurements Optionally, a CSI-RS resource set for interference measurement Time domain behavior, i.e. periodic, semi-persistent, or aperiodic reporting Frequency granularity, i.e., wideband or subband CSI parameters to be reported, such as RI, PMI, CQI, and CSI-RS Resource Indicator (CRI), in case of multiple CSI-RS resources in a resource set Codebook type, i.e., Type I or II, and codebook subset restrictions Measurement Limits Subband size. One of two possible subband sizes is indicated, the value range depends on the bandwidth of the BWP. One CQI / PMI is fed back per subband (if configured for subband reporting).

[0019] When a CSI-RS resource set in a CSI reporting setting includes multiple CSI-RS resources, one of the CSI-RS resources is selected by the UE, and a CSI-RS resource indicator (CRI) is reported by the UE to instruct the gNB regarding the selected CSI-RS resource in the resource set, along with the RI, PMI, and CQI associated with the selected CSI-RS resource.

[0020] In aperiodic CSI reporting in NR, two or more CSI reporting settings, each with a different CSI-RS resource set for channel measurement and / or a different resource set for interference measurement, can be configured and triggered simultaneously, where multiple CSI reports are aggregated and sent from the UE to the gNB in ​​a single PUSCH.

[0021] Type I and Type II Codebooks in NR

[0022] Type I codebooks (CBs) are generally used by UEs to report CSI for single-user MIMO (SU-MIMO) scheduling in NR, while Type II CBs are generally for more accurate CSI feedback for multi-user MIMO (MU-MIMO) scheduling.

[0023] In both Type-I and Type-II CB, for each rank, the precoding matrix W is W=W1W2 It is specified in the form of where: TIFF2025533521000002.tif131702W is an N×2L matrix containing information on the L selected DFT beams {d i , i = 1,...,L}, where di is an N×1 DFT vector and N is the number of CSI-RS ports per polarization. W2 is a 2L×v matrix containing cophasing coefficients between the selected beams and between antenna ports with two different polarizations, where v is the number of layers or ranks. W1 is the same for the entire CSI bandwidth, and W2 can be for the entire bandwidth or per subband.

[0024] In Type-I CB, the precoding vector for each MIMO layer is associated with a single DFT beam, whereas in Type-II CB, the precoding vector for each layer is a linear combination of multiple DFT beams.

[0025] Extended Type II Codebook in NR

[0026] In NR Rel-16, the Type II codebook is extended by applying frequency-domain (FD) compression across all subbands to reduce CSI feedback overhead and / or improve CSI accuracy. Instead of reporting W for each subband, a linear combination of DFT basis vectors is used to jointly represent W across the entire CSI bandwidth. For each layer, the precoding matrix W across all subbands has the following form: It is TIFF2025533521000003.tif9170, where Wf = [f1,...,fM] is a matrix containing the M selected DFT basis vectors {f1,...,fM}; TIFF2025533521000004.tif8170 is a 2L×M matrix containing the coefficients for each selected DFT beam and each selected FD basis vector.

[0027] To save on reporting overhead, and TIFF2025533521000005.tif9170 Because some coefficients are typically weak, only a subset of KNZ,i ≤ K0 < 2LMi non-zero coefficients (NZC) is reported for each layer i. The 2LMi-KNZ,i unreported coefficients are assumed to be zero. The maximum number of non-zero coefficients per layer is For TIFF2025533521000006.tif10170RI={2,3,4}, the total maximum number of NZCs across all layers is ≦2K0. TIFF2025533521000007.tif9170 To know which coefficients have been selected, a bitmap of size 2LMi for each layer i is used to indicate in the NZC for that layer.

[0028] Extended Type II Codebook for High / Medium UE Speeds

[0029] In measurements in real-world deployments, it has been observed that downlink MU-MIMO precoding performance degrades when one or more of the co-scheduled UEs start moving faster than a few km / h relative to the base station. One of the main reasons is that the channel information used to compute the MIMO precoding at the base station becomes outdated fairly quickly when this occurs, causing the precoder to lose its effectiveness in protecting the co-scheduled users from interference when transmitting to their intended users. Therefore, downlink MU-MIMO precoding needs to be made robust to higher UE speeds.

[0030] One solution to alleviate this problem and address such fast channel variations is to configure faster CSI reporting (i.e., more frequent CSI reporting and measurement). The problem with this approach is that it incurs large signaling and reporting overhead. Furthermore, even if the CSI-RS periodicity is increased, there is still a CSI reporting and scheduling delay that can cause the reported CSI to be out of date. Therefore, with the current CSI framework in NR, it is difficult to obtain accurate CSI for medium- to high-speed UEs with a reasonable amount of overhead.

[0031] In the 3GPP Rel-18 work item on MIMO evolution for downlink and uplink (see 3GPP RP-213598), it was agreed to specify CSI reporting enhancements for high / medium UE speeds by exploiting time-domain correlation / Doppler-domain information to support DL precoding. In particular, Rel-16 / 17 Type II codebook refinements without modifications to the spatial and frequency-domain basis should be investigated.

[0032] The following agreement on a new Type II codebook structure for high / medium UE speeds was reached at RAN1#110 (see, e.g., RAN1 Chair's Notes, 3GPP TSG RAN WG1#110, Toulouse, France, August 22-26, 2022):

[0033] For Rel-18 Type II codebook refinement for high / medium rates, down-select one of the following codebook structures: Alt2A: The commonly selected Doppler domain base for all SD / FD bases, e.g. TIFF2025533521000008.tif9170 ○ Note that Wd can be a special case of identity. Alt2B: Doppler domain basis independently selected for different SD / FD bases Note that Wd can be a special case of identity. Alt3. We reuse TIFF2025533521000009.tif9170 and the Rel-16 / 17(F)e Type-II codebook with single W1 and Wf reports.

[0034] Currently, there is one or more issues. The agreement made in RAN1#110 is that Alt3 corresponds to the case without Doppler domain compression, so TIFF2025533521000010.tif8170If included in the CSI report, it may result in large CSI overhead.On the other hand, two variants of Alt2 (i.e., Alt2A and Alt2B) offer the possibility of Doppler domain compression by introducing a matrix Wd.To achieve compression in the Doppler domain, the matrix Wd may contain one or more selected Doppler domain basis vectors (note that the Doppler domain basis vectors were agreed upon to be DFT basis vectors in RAN1).

[0035] In the agreement made in RAN1#110, the above two versions of Alt2 allow the possibility of setting the matrix Wd to the identity matrix, in which case there will be no compression in the Doppler domain. Therefore, the above two versions of Alt2 also allow Alt3 to be supported as a special case by setting Wd to the identity matrix.

[0036] Improved systems and methods for reporting CSI are needed. Summary of the Invention

[0037] Systems and methods for channel state information (CSI) reporting with a Type II codebook for high speeds are provided. In some embodiments, the method includes determining when to apply Doppler-domain compression and when to avoid Doppler-domain compression when feeding back channel state information (CSI) reports (e.g., Type II CSI), determining a signaled number of CSI instances for which a network node requests a UE to calculate CSI, and determining whether to apply CSI compression in the Doppler domain based on the number of CSI instances. Some embodiments may provide one or more of the following technical advantages. The solutions proposed in this disclosure enable the network and UE to support cases with and without Doppler-domain compression under a single Type II CSI reporting framework. Based on signaling received from the network, the solutions enable the UE to determine when to feed back a selected Doppler-domain base (i.e., if Doppler-domain compression is assumed) and when to avoid Doppler-domain base selection in Type II CSI reporting.

[0038] Some embodiments of the present disclosure provide a solution that defines criteria used by a UE to determine when to apply Doppler domain compression and when to avoid Doppler domain compression when feeding back Type II CSI reports. The present disclosure also defines associated signaling and UE behavior related to such Type II CSI reports.

[0039] Some embodiments of the present disclosure use the signaled number of CSI instances for which the gNB requests the UE to calculate CSI to determine whether the UE needs to apply CSI compression in the Doppler domain. If CSI compression needs to be applied, the UE needs to feed back selected Doppler domain basis vectors (indicated via indexes) as part of Type II CSI feedback. If CSI compression is not applied, the UE does not select Doppler domain basis vectors and does not need to feed back Doppler domain basis vectors (i.e., does not need to feed back indices representing the Doppler domain basis vectors).

[0040] The present disclosure also covers various signaling alternatives for the number of CSI instances for which the gNB requests the UE to calculate CSI, and mechanisms for defining the threshold used to determine whether to apply CSI compression in the Doppler domain.

[0041] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several aspects of the present disclosure and, together with the description, serve to explain the principles of the disclosure. [Brief explanation of the drawings]

[0042] [Figure 1] FIG. 1 illustrates an example of spatial multiplexing operation. [Figure 2] FIG. 1 illustrates an example of channel state information reference signal (CSI-RS) resource elements (REs) for 12 antenna ports, where one RE per resource block (RB) per port is shown. [Figure 3] 1A-1C illustrate four different examples with different numbers of CSI instances in which a gNB requests a user equipment (UE) to feed back CSI, in accordance with some embodiments of the present disclosure. [Figure 4] FIG. 1 illustrates a method performed by a UE in accordance with some embodiments of the present disclosure. [Figure 5] FIG. 1 illustrates a method performed by a network node according to some embodiments of the present disclosure. [Figure 6] FIG. 1 illustrates an example of a communication system, according to some embodiments. [Figure 7] FIG. 1 illustrates a UE, according to some embodiments. [Figure 8] FIG. 1 illustrates a network node, according to some embodiments. [Figure 9] 7 is a block diagram of a host, which may be an embodiment of the host of FIG. 6 in accordance with various aspects described herein. [Figure 10] FIG. 1 is a block diagram illustrating a virtualized environment in which functionality implemented by some embodiments may be virtualized. [Figure 11] FIG. 1 is a communication diagram of a host communicating with a UE via a network node over a partial wireless connection, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0043] The embodiments described below represent information to enable those skilled in the art to practice the embodiments and illustrate the best modes of practicing the embodiments. Upon reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will recognize applications of these concepts not specifically addressed herein. It is understood that these concepts and applications fall within the scope of the present disclosure.

[0044] It remains an open question what criteria should be used to determine whether the Wd matrix should be set to the identity matrix or whether it should contain selected Doppler domain base vectors. The associated signaling and UE behavior are also open issues that need to be resolved.

[0045] Systems and methods for channel state information (CSI) reporting with a Type II codebook for high speeds are provided. In some embodiments, the methods include determining when to apply Doppler-domain compression and when to avoid Doppler-domain compression when feeding back a CSI report (e.g., Type II CSI), determining a signaled number of CSI instances for which a network node requests a UE to calculate CSI, and determining whether to apply CSI compression in the Doppler domain based on the number of CSI instances. Some embodiments may provide one or more of the following technical advantages. The solutions proposed in this disclosure enable the network and UE to support cases with and without Doppler-domain compression under a single Type II CSI reporting framework. Based on signaling received from the network, the solutions enable the UE to determine when to feed back a selected Doppler-domain base (i.e., if Doppler-domain compression is assumed) and when to avoid Doppler-domain base selection in a Type II CSI report.

[0046] Some aspects of the present disclosure and their embodiments may provide solutions to these and other problems. Some embodiments of the present disclosure provide solutions that specify criteria used by a UE to determine when to apply Doppler domain compression and when to avoid Doppler domain compression when feeding back Type II CSI reports. The present disclosure also specifies associated signaling and UE behavior related to such Type II CSI reports.

[0047] Some embodiments of the present disclosure use the signaled number of CSI instances for which the gNB requests the UE to calculate CSI to determine whether the UE needs to apply CSI compression in the Doppler domain. If CSI compression needs to be applied, the UE needs to feed back selected Doppler domain basis vectors (indicated via indexes) as part of Type II CSI feedback. If CSI compression is not applied, the UE does not select Doppler domain basis vectors and does not need to feed back Doppler domain basis vectors (i.e., does not need to feed back indices representing the Doppler domain basis vectors).

[0048] The present disclosure also covers various signaling alternatives for the number of CSI instances for which the gNB requests the UE to calculate CSI, and mechanisms for defining the threshold used to determine whether to apply CSI compression in the Doppler domain.

[0049] General embodiment

[0050] In one embodiment, the gNB signals to the UE the number of CSI instances (denoted as NCSI) for which the gNB requests the UE to feed back CSI. In FIG. 3 , four different examples are shown with different numbers of CSI instances for which the gNB requests the UE to feed back CSI. The boxes labeled n, n+1, ..., n+9 in these examples may be any one of a slot, a subslot (where a subslot consists of a subset of symbols within a slot), or a time unit. In some embodiments, a value for the time unit (e.g., the duration of each box shown in the example of FIG. 3 ) may be configured by the gNB to the UE. In some embodiments, a time unit may be defined as the minimum time gap between any two NZP CSI-RS samples (or resources) in the set of NZP CSI-RS samples used to calculate the CSI corresponding to the NCSI CSI instances. In the remainder of this description, each box in the example of FIG. 3 is referred to as a time unit. However, it should be understood that each such box may instead represent a slot or a subslot.

[0051] In example A of Figure 3, the UE is requested to calculate CSI corresponding to time units n+2, n+4, n+6, and n+8. Therefore, the number of CSI instances for which the UE is requested to calculate CSI is NCSI = 4.

[0052] In example B of Figure 3, the UE is requested to calculate CSI corresponding to time units n, n+4, and n+8. Therefore, the number of CSI instances for which the UE is requested to calculate CSI is NCSI = 3.

[0053] In example C of Figure 3, the UE is requested to calculate CSI corresponding to time units n and n+5. Therefore, the number of CSI instances for which the UE is requested to calculate CSI is NCSI = 2.

[0054] In example D of Figure 3, the UE is requested to calculate CSI corresponding to time units n, n+1, n+2, n+3, n+4, n+5, n+6, n+7, and n+8. Thus, the number of CSI instances for which the UE is requested to calculate CSI is NCSI = 10.

[0055] Although the example in Figure 3 shows evenly spaced CSI instances, embodiments of the present disclosure are equally applicable to cases where the CSI instances are not evenly spaced. In some embodiments, the CSI instances may be unevenly spaced across time units. This may correspond to some TDD deployments where some slots may be DL slots for which CSI may be required, but CSI may not be needed for UL slots. An example may be that for a case with NCSI = 4, CSI may be required for time units n+2, n+3, n+7, and n+8 (instead of what is shown in example a in Figure 3).

[0056] Note that in this disclosure, CSI corresponding to N CSI CSI instances are reported in a single slot. For example, when a UE is able to predict CSI in future slots, CSI corresponding to N CSI CSI instances may be reported in slot n shown in FIG. 3.

[0057] In one alternative embodiment, the number of time instances N CSI at which the gNB requests the UE to feed back CSI may be explicitly signaled via an explicit parameter. In another alternative embodiment, the number of time instances N CSI at which the gNB requests the UE to feed back CSI may be implicitly signaled via a combination of one or more other parameters.

[0058] In one embodiment, the threshold Nth can be either signaled by the gNB to the UE or pre-specified in the 3GPP specifications. This threshold is used to define UE behavior regarding when to select the Doppler region basis vectors as part of Wd or when to set the Wd matrix to the identity matrix. In some embodiments, when the threshold Nth is signaled as a parameter, the threshold can be set either as part of the CSI-ReportConfig IE defined in 3GPP TS38.331 V17.1.0 or as part of the CodebookConfig IE defined in 38.331 V17.1.0.

[0059] If the number of time instances NCSI for which the gNB requests the UE to feedback CSI is less than the threshold Nth (i.e., NCSI < Nth), the UE assumes no compression in the Doppler region and sets the matrix Wd to the identity matrix. Since Wd is set to the identity matrix, the UE does not feedback the selected Doppler region base vectors as part of the CSI report when the criterion NCSI < Nth is met. Alternatively, in this embodiment, the criterion NCSI ≤ Nth can be used instead of NCSI < Nth (i.e., if the number of time instances NCSI for which the gNB requests the UE to feedback CSI is less than or equal to the threshold Nth, the UE assumes no compression in the Doppler region and sets the matrix Wd to the identity matrix).

[0060] If the number of time instances NCSI at which the gNB requests the UE to feed back CSI is greater than a threshold Nth (i.e., NCSI > Nth), the UE assumes compression in the Doppler domain and selects one or more Doppler domain basis vectors to be columns of the Wd matrix. In this case, the UE feeds back the selected Doppler domain basis vector for each layer in the form of index i1,9,l, where i1,9,l represents the selected Doppler domain basis vector corresponding to the lth layer. Alternatively, the UE feeds back the selected Doppler domain basis vector for each SD / FD pair for each layer in the form of index i1,9,sdfd,l, where i1,9,sdfd,l represents the selected Doppler domain basis vector corresponding to the lth layer and the sdfdth SD / FD basis pair. The number of Doppler domain basis vectors to be selected can be signaled to the UE by the gNB either as a standalone upper layer parameter or as a parameter indicating a combination of parameters.

[0061] In one embodiment, whether the UE assumes no compression in the Doppler domain or compression in the Doppler domain is determined by a parameter (or parameter combination) that indicates the number of Doppler domain basis vectors to be selected. If the number of Doppler domain basis vectors to be selected is indicated as 0, the UE assumes no compression in the Doppler domain. In this case, the UE sets the matrix Wd to an identity matrix, and the UE does not feedback indices representing the selected Doppler domain basis vectors. If the number of Doppler domain basis vectors to be selected is indicated as a non-zero value, the UE assumes compression in the Doppler domain. In this case, the UE feeds back the selected Doppler domain basis vectors, represented by one or more indices, as part of Type II CSI feedback, similar to what is described above.

[0062] In one alternative, the CSI for N CSI time instances is reported as a single PMI value corresponding to codebook indices i1 and i2, where The file is TIFF2025533521000011.tif31170.

[0063] The elements of i1 are the selected beam, the FD basis, the DD basis, the index of the strongest coefficient, and for each layer TIFF2025533521000012.tif9170 represents a bitmap indicating which coefficients are reported. The i2 component consists of an index pointing to the quantized amplitude and phase of the coefficients being reported.

[0064] i1,1, i1,2 indicate the selected L spatial beams.

[0065] i1,5 indicates the set of FD bases from which the reported basis is selected when the number of PMIs to be reported N3>19.

[0066] i1,6,l is a combination index indicating the selected FD base for layer l.

[0067] i1,7,l is for layer l This shows a bitmap whose non-zero bits identify which pixels are reported in TIFF2025533521000013.tif8170i2,4,l and i2,5,l.

[0068] i1,8,l is for layer l, when v=1, TIFF2025533521000014.tif8170 indicates the index of the strongest non-zero coefficient reported, and if v≧2 indicates the index of the strongest spatial beam.

[0069] In one embodiment, i1,9,l indicates the selected Doppler region base for layer l, and i1,9,l TIFF2025533521000015.tif14170 where N4 is the Doppler domain basis vector length and MDD,l is the number of Doppler domain basis vectors to be selected.

[0070] In another embodiment, i1,9,l indicates the selected Doppler domain basis for layer l, when a Doppler basis of 0 is always selected. TIFF2025533521000016.tif13170 where N4 is the Doppler domain basis vector length and MDD,l is the number of Doppler domain basis vectors to be selected.

[0071] Embodiments for Signaling NCSI

[0072] In one embodiment, the number of time instances (NCSI) at which the gNB requests the UE to feed back CSI is signaled as part of the CSI-ReportConfig information element (IE). The CSI-ReportConfig IE is specified in 3GPP TS38.331 V17.1.0. A first example of signaling NCSI as part of the CSI-ReportConfig IE is shown below. In this first example, the NCSI is configured via the RRC-configured parameter numCsiInstances-r18. Note that since Type-II CSI is mainly carried on the PUSCH, the parameter numCsiInstances-r18 can be configured when the CSI-ReportConfig has a reporting configuration type (i.e., reportConfigType) set to either aperiodic (i.e., aperiodically triggered CSI reporting on PUSCH) or semiPersistentOnPUSCH (i.e., semi-persistently activated CSI reporting on PUSCH).

[0073] In the following example, the parameter firstTimeUnitCSI-r18 may also be RRC configured as part of the CSI-ReportConfig IE. The parameter firstTimeUnitCSI-r18 indicates the time unit (or alternatively, slot or subslot) corresponding to the first CSI instance among N CSI CSI instances. In the example of FIG. 3, firstTimeUnitCSI-r18 corresponds to: In example A of Figure 3, firstTimeUnitCSI-r18 corresponds to time unit n+2 In examples B, C, and D of Figure 3, firstTimeUnitCSI-r18 corresponds to time unit n

[0074] In some embodiments, firstTimeUnitCSI-r18 may be defined relative to the slot in which the CSI should be reported (i.e., if CSI is to be reported in slot n, the time unit corresponding to the first CSI instance is given by n+firstTimeUnitCSI-r18). Alternatively, when the time unit is smaller than an uplink slot, the time unit corresponding to the first CSI instance may be given by n+X*firstTimeUnitCSI-r18, where X is a predefined value specified in the 3GPP specifications.

[0075] In some other embodiments, firstTimeUnitCSI-r18 may be defined for the slot containing the CSI reference resource (i.e., if CSI is to be reported in slot nCSI-ref, the time unit corresponding to the first CSI instance is given by nCSI-ref+firstTimeUnitCSI-r18). Alternatively, when the time unit is smaller than an uplink slot, the time unit corresponding to the first CSI instance may be given by nCSI-ref+X*firstTimeUnitCSI-r18, where X is a predefined value specified in the 3GPP specifications. Note that the CSI reference resource here is the one specified in clause 5.2.2.5 of 3GPP TS38.214.

[0076] In the following example IE, the parameter timeUnitStepSize-r18 may also be RRC configured as part of the CSI-ReportConfig IE. The parameter timeUnitStepSize-r18 indicates the gap between adjacent CSI instances in terms of time units (or alternatively, slots or subslots). In the example of Figure 3, timeUnitStepSize-r18 corresponds to: In example A in Figure 3, timeUnitStepSize-r18 has the value 2 In example B of Figure 3, timeUnitStepSize-r18 has the value 4 In example C of Figure 3, timeUnitStepSize-r18 has the value 5 In example D of Figure 3, timeUnitStepSize-r18 has the value 1

[0077] Alternatively, the parameter timeUnitOffsetList-r18 may be RRC configured as part of the CSI-ReportConfig IE to indicate timeUnitStepSize-r18. The parameter timeUnitOffsetList-r18 indicates the CSI instance in terms of time unit offsets (or alternatively, slots or subslots). In the example of Figure 3, timeUnitOffsetList-r18 corresponds to: In example A in Figure 3, timeUnitOffsetList-r18 has the values ​​[2,4,6,8] In example B of Figure 3, timeUnitOffsetList-r18 has the values ​​[0,4,8] In example C of Figure 3, timeUnitOffsetList-r18 has the value [0,5] In example D of Figure 3, timeUnitOffsetList-r18 has values ​​[0,1,2,3,4,5,6,7,8,9] CSI-ReportConfig Information Element TIFF2025533521000017.tif200170TIFF2025533521000018.tif136170

[0078] In an alternative embodiment, the UE may be signaled with timeUnitStepSize and an indication of the total number of time units, in which case the number of instances NCSI may be determined as floor(total number of time units / timeUnitStepSize), where the floor() operator rounds the result of total number of time units / timeUnitStepSize to the largest integer less than total number of time units / timeUnitStepSize.

[0079] In another alternative, instead of signaling the parameters in the CSI-ReportConfig as shown in the above IE, those parameters can alternatively be signaled as part of the CodebookConfig information element as specified in 38.331 v17.1.0.

[0080] In another alternative embodiment, one or more of firstTimeUnitCSI, timeUnitStepSize, and numCsiInstances are signaled via codepoints in the DCI field of the DCI. For example, different codepoints in the DCI field in the DCI may indicate different combinations of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize values, as shown in Table 1. TIFF2025533521000019.tif51170

[0081] Although the examples in Table 1 show each codepoint of the DCI field indicating a combination of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize values, in some alternative embodiments, each codepoint could indicate a subset of the following: Each code point indicates only a value for firstTimeUnitCSI Each code point indicates only a value for numCsiInstances Each code point indicates only a value for timeUnitStepSize Each codepoint indicates only the value for firstTimeUnitCSI and the value numCsiInstances Each codepoint indicates only a value for firstTimeUnitCSI and a value for timeUnitStepSize. Each code point indicates only a value for numCsiInstances and a value for timeUnitStepSize.

[0082] In the above alternative embodiment, any one of the values ​​of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize that is not indicated to the UE by the DCI is indicated to the UE by the network via higher layer configuration (e.g., via RRC).

[0083] In some further alternative embodiments, the values ​​of one or more of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize are indicated by MAC CE signaling.

[0084] FIG. 4 shows a method performed by the UE, including one or more of determining when to apply Doppler domain compression and when to avoid Doppler domain compression when feeding back a CSI report (e.g., Type II CSI) (step 400), determining a signaled number of CSI instances for which the gNB requests the UE to calculate CSI (step 402), and determining whether to apply CSI compression in the Doppler domain based on the number of CSI instances (step 404).

[0085] FIG. 5 shows a method implemented by a network node that includes one or more of indicating the number of CSI instances for which the network node requests the UE to calculate CSI (step 500) and receiving CSI with or without CSI compression in the Doppler domain based on the number of CSI instances (step 502).

[0086] FIG. 6 illustrates an example of a communication system 600, according to some embodiments.

[0087] In this example, the communications system 600 includes a communications network 602 including an access network 604, such as a radio access network (RAN), and a core network 606 including one or more core network nodes 608. The access network 604 includes one or more access network nodes (one or more of which may be generally referred to as network nodes 610), such as network nodes 610A and 610B, or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP access points (APs). The network nodes 610 facilitate direct or indirect connectivity of user equipment (UE), such as by connecting UEs 612A, 612B, 612C, and 612D (one or more of which may be generally referred to as UEs 612), to the core network 606 over one or more wireless connections.

[0088] Exemplary wireless communication over a wireless connection includes sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, communication system 600 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. Communication system 600 may include and / or interface with any type of communication, telecommunication, data, cellular, wireless network, and / or other similar type systems.

[0089] The UE 612 may be any of a wide variety of communication devices, including a wireless device configured, configured, and / or operable to communicate wirelessly with the network node 610 and other communication devices. Similarly, the network node 610 is configured, capable, configured, and / or operable to communicate, directly or indirectly, with the UE 612 and / or with other network nodes or equipment in the communication network 602 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration, in the communication network 602.

[0090] In the illustrated example, the core network 606 connects the network node 610 to one or more hosts, such as the host 616. These connections may be direct or indirect via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 606 includes one or more core network nodes (e.g., the core network node 608) structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, and therefore, those descriptions are generally applicable to the corresponding components of the core network node 608. Exemplary core network nodes include one or more of a Mobile Switching Center (MSC), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Subscription Identifier De-Concealing Function (SIDF), a Unified Data Management (UDM), a Security Edge Protection Proxy (SEPP), a Network Publishing Function (NEF), and / or a User Plane Function (UPF).

[0091] The host 616 may be owned or under the control of, and operated by or on behalf of, a service provider other than the operator or provider of the access network 604 and / or the communication network 602. The host 616 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data about various ambient conditions detected by multiple UEs, analytics functions, social media, functions for controlling or possibly interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0092] Overall, the communication system 600 of FIG. 6 enables connectivity between UEs, network nodes, and hosts. In that sense, the communication system 600 may be configured to operate according to predefined rules or procedures, such as a particular standard, including, but not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable second, third, fourth, or fifth generation (2G, 3G, 4G, or 5G) standard, or any applicable future generation standard (e.g., sixth generation (6G)), a wireless local area network (WLAN) standard such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi), and / or any low power wide area network (LPWAN) standard such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, near field communications (NFC) ZigBee, LiFi, and / or LoRa and Sigfox.

[0093] In some examples, the communication network 602 is a cellular network that implements 3GPP standardized features. Thus, the communication network 602 may support network slicing to provide different logical networks to different devices connected to the communication network 602. For example, the communication network 602 may provide Ultra-Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs and / or providing Massive Machine-Based Communication (mMTC) / Massive Internet of Things (IoT) services to still further UEs.

[0094] In some examples, the UE 612 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to the access network 604 on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the access network 604. Furthermore, the UE may be configured to operate in a single or multi-radio access technology (RAT) or multi-standard mode. For example, the UE may operate with any one or a combination of Wi-Fi, New Radio (NR), and LTE, i.e., Multi-Radio Dual Connectivity (MR-DC), such as Enhanced UMTS Terrestrial RAN (E-UTRAN) NR-Dual Connectivity (EN-DC).

[0095] In this example, a hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UEs 612C and / or 612D) and a network node (e.g., network node 610B). In some examples, the hub 614 may be a controller, a router, a content source, a content analyzer, or any of the other communication devices described herein with respect to UEs. For example, the hub 614 may be a broadband router that enables access to the core network 606 for the UE. As another example, the hub 614 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 610, or may be due to executable code, scripts, processes, or other instructions in the hub 614. As another example, the hub 614 may be a data collector that serves as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 614 may be a content source. For example, for a UE that is a virtual reality (VR) headset, display, loudspeaker, or other media distribution device, the hub 614 may retrieve, via a network node, VR assets, video, audio, or other media or data related to sensory information, which the hub 614 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In yet another example, the hub 614 acts as a proxy server or orchestrator for the UEs, particularly in the case where one or more of the UEs are low-energy IoT devices.

[0096] The hub 614 may have a constant / permanent or intermittent connection to the network node 610B. The hub 614 may also enable different communication schemes and / or schedules between the hub 614 and the UEs (e.g., UEs 612C and / or 612D) and between the hub 614 and the core network 606. In other examples, the hub 614 is connected to the core network 606 and / or one or more UEs via a wired connection. Moreover, the hub 614 may be configured to connect to a machine-to-machine (M2M) service provider over the access network 604 and / or to another UE over a direct connection. In some scenarios, a UE may establish a wireless connection with the network node 610 while still connected via a wired or wireless connection through the hub 614. In some embodiments, the hub 614 may be a dedicated hub, i.e., a hub whose primary function is to route communications from / to the UE to / from the network node 610B. In other embodiments, the hub 614 may be a non-dedicated hub, i.e., a device that is capable of operating to route communications between the UE and the network node 610B, but that is further capable of operating as a communication initiation and / or termination point for some data channels.

[0097] 7 illustrates a UE 700, according to some embodiments. As used herein, a UE refers to a device capable of, set up, configured, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, a mobile phone, a cell phone, a Voice over Internet Protocol (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless camera, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop computer, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a smart device, a wireless customer premises equipment (CPE), a vehicle-mounted or vehicle-embedded / integrated wireless device, etc. Other examples include any UE identified by 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0098] A UE may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE does not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but may not be associated with or initially associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but may be associated with or operated for the user's benefit.

[0099] The UE 700 includes a processing circuit 702 operably coupled to an input / output interface 706, a power source 708, a memory 710, a communication interface 712, and / or any other components, or any combination thereof, via a bus 704. Some UEs may utilize all or a subset of the components shown in FIG. 7. The level of integration between components may vary from UE to UE. Additionally, some UEs may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0100] The processing circuit 702 is configured to process instructions and data and may be configured to implement any sequential state machine operable to execute instructions stored in memory 710 as a machine-readable computer program. The processing circuit 702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.), programmable logic together with appropriate firmware, one or more stored computer programs such as a microprocessor or digital signal processor (DSP) together with appropriate software, a general-purpose processor, or any combination of the above. For example, the processing circuit 702 may include multiple central processing units (CPUs).

[0101] In this example, the input / output interface 706 may be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 700. Examples of input devices include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. A presence-sensitive display may include a capacitive or resistive touch sensor for detecting input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as the input device. For example, a universal serial bus (USB) port may be used to accommodate input and output devices.

[0102] In some embodiments, the power source 708 is structured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The power source 708 may further include power circuitry for delivering power to various portions of the UE 700 from the power source 708 itself and / or from an external power source via an interface such as an input circuit or a power cable. Delivering power may be for charging the power source 708, for example. The power circuitry may perform any formatting, conversion, or other modification on the power from the power source 708 to make it suitable for the respective component of the UE 700 being powered.

[0103] The memory 710 may be or be configured to include memory, such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrical EPROM (EEPROM), magnetic disk, optical disk, hard disk, removable cartridge, flash drive, etc. In one example, the memory 710 includes one or more application programs 714, such as an operating system, a web browser application, a widget, a gadget engine, or other applications, and corresponding data 716. The memory 710 may store any of a variety of different operating systems or combinations of operating systems for use by the UE 700.

[0104] The memory 710 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD) optical disc drive, an internal hard disk drive, a Blu-ray optical disc drive, a holographic digital data storage (HDDS) optical disc drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory, such as a tamper-resistant module in the form of a universal integrated circuit card (UICC) containing one or more SIMs, such as a universal subscriber identity module (SIM) (USIM) and / or an Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC, commonly known as a "SIM card." The memory 710 may enable the UE 700 to access, offload, or upload data, instructions, application programs, etc. stored on a temporary or non-transitory memory medium. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied as or in the memory 710, which may be or comprise a device-readable storage medium.

[0105] The processing circuit 702 may be configured to communicate with an access network or other networks using a communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or network node in the access network). Each transceiver may include a transmitter 718 and / or a receiver 720 suitable for providing network communication (e.g., optical, electrical, frequency allocation, etc.). Moreover, the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software, or firmware, or may alternatively be implemented separately.

[0106] In the illustrated embodiment, the communication capabilities of communication interface 712 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, NFC, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication capability, or any combination thereof. Communications may be implemented in accordance with one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), etc.

[0107] Regardless of the type of sensor, the UE may provide an output of data captured by the UE's sensors to a network node through the UE's communications interface 712 or via a wireless connection. Data captured by the UE's sensors may be communicated to a network node via another UE through a wireless connection. The output may be periodic (e.g., once every 15 minutes when reporting sensed temperature), in response to a triggering event (e.g., an alert is sent when humidity is detected), in response to a request (e.g., a user-initiated request), random (e.g., to even out the load from reporting from several sensors), or a continuous stream (e.g., a live video feed of a patient).

[0108] As another example, the UE may include an actuator, motor, or switch associated with a communications interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch may change. For example, the UE may include a motor that adjusts a control surface or rotor of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input.

[0109] When in the form of an IoT device, the UE may be a device for use in one or more application areas, including, but not limited to, urban wearable technology, augmented industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices that are or are embedded in a connected refrigerator or freezer, a television, a connected lighting device, an energy meter, a robotic vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a water / humidity sensor, an electronic door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for augmented reality (AR) or VR, a wearable for haptic augmentation or sensory augmentation, a water sprinkler, an animal or product tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any type of medical device such as a heart rate monitor or a remote-controlled surgical robot. A UE in the form of an IoT device comprises, in addition to the other components described with respect to the UE 700 shown in FIG. 7, circuitry and / or software depending on the intended application of the IoT device.

[0110] As yet another particular example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another UE and / or network node. The UE may in this case be an M2M device, which may be referred to as an MTC device in a 3GPP context. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, bus, truck, ship, airplane, or other equipment capable of monitoring and / or reporting on its operating status or other functionality related to its operation.

[0111] In practice, any number of UEs may be used together for a single use case. For example, a first UE may be a drone or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE that is a remote controller that operates the drone. When a user makes changes from the remote controller, the first UE may adjust a throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE may also include two or more of the functions described above. For example, a UE may include a sensor and an actuator and handle communication of data for both the speed sensor and the actuator.

[0112] 8 illustrates a network node 800 according to some embodiments. As used herein, a network node refers to a device capable of, set up, configured, and / or operable to communicate, directly or indirectly, with UEs and / or other network nodes or devices in a communication network. Examples of network nodes include, but are not limited to, APs (e.g., wireless APs), base stations (BSs) (e.g., wireless BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0113] BSs may be categorized based on the amount of coverage they provide (or, stated another way, their transmit power level) and may therefore be referred to as femto BSs, pico BSs, micro BSs, or macro BSs depending on the amount of coverage provided. A BS may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed wireless BS, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such RRUs may or may not be integrated with an antenna, such as an antenna-integrated radio. Portions of a distributed wireless BS may also be referred to as nodes in a distributed antenna system (DAS).

[0114] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, MSR equipment such as a multi-standard radio (MSR) BS, a network controller such as a radio network controller (RNC) or a BS controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile location center (E-SMLC)), and / or a minimization drive test (MDT).

[0115] The network node 800 includes processing circuitry 802, memory 804, a communications interface 806, and a power source 808. The network node 800 may be assembled from multiple physically separate components (e.g., Node B and RNC components, or BTS and BSC components, etc.), each of which may have their own respective components. In some scenarios in which the network node 800 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such scenarios, each unique Node B and RNC pair may, in some instances, be considered a single separate network node. In some embodiments, the network node 800 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs) and some components may be reused (e.g., antenna 810 may be shared by different RATs). Network node 800 may also include multiple sets of the various shown components for different wireless technologies, e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies, integrated into network node 800. These wireless technologies may be integrated into the same or different chips or sets of chips and other components within network node 800.

[0116] The processing circuitry 802 may comprise one or more combinations of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable to provide the network node 800 functionality, either alone or in conjunction with other network node 800 components such as memory 804.

[0117] In some embodiments, the processing circuit 802 comprises a system on a chip (SOC). In some embodiments, the processing circuit 802 includes one or more of a radio frequency (RF) transceiver circuit 812 and a baseband processing circuit 814. In some embodiments, the RF transceiver circuit 812 and the baseband processing circuit 814 may be on separate chips (or sets of chips), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit 812 and the baseband processing circuit 814 may be on the same chip or set of chips, board, or unit.

[0118] The memory 804 may comprise any form of volatile or non-volatile computer-readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD), or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable, and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 802. The memory 804 may store any suitable instructions, data, or information, including applications including one or more of computer programs, software, logic, rules, code, tables, and / or other instructions that can be executed by the processing circuit 802 and utilized by the network node 800. The memory 804 may be used to store computations performed by the processing circuit 802 and / or data received via the communications interface 806. In some embodiments, the processing circuit 802 and the memory 804 are integrated.

[0119] The communication interface 806 is used in wired or wireless communication of signaling and / or data between network nodes, access networks, and / or the UE. As shown, the communication interface 806 comprises port(s) / terminal(s) 816 for sending and receiving data to and from a network, e.g., over a wired connection. The communication interface 806 also includes radio front-end circuitry 818, which is coupled to an antenna 810 or, in some embodiments, may be part of the antenna 810. The radio front-end circuitry 818 comprises a filter 820 and an amplifier 822. The radio front-end circuitry 818 may be connected to the antenna 810 and the processing circuit 802. The radio front-end circuitry 818 may be configured to condition signals communicated between the antenna 810 and the processing circuit 802. The radio front-end circuitry 818 may receive digital data to be sent to another network node or the UE via a wireless connection. The radio front-end circuitry 818 may convert the digital data into radio signals having appropriate channel and bandwidth parameters using a combination of filters 820 and / or amplifiers 822. The radio signals may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect the radio signals, which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuit 802. In other embodiments, the communication interface 806 may comprise different components and / or different combinations of components.

[0120] In some alternative embodiments, network node 800 does not include a separate radio front-end circuit 818; instead, processing circuit 802 includes the radio front-end circuitry and is connected to antenna 810. Similarly, in some embodiments, all or a portion of RF transceiver circuitry 812 is part of communication interface 806. In still other embodiments, communication interface 806 includes one or more ports or terminals 816, radio front-end circuitry 818, and RF transceiver circuitry 812 as part of a radio unit (not shown), and communication interface 806 communicates with baseband processing circuitry 814 that is part of a digital unit (not shown).

[0121] Antenna 810 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 810 may be coupled to radio front-end circuitry 818 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 810 is separate from network node 800 and connectable to network node 800 through an interface or port.

[0122] The antenna 810, the communication interface 806, and / or the processing circuit 802 may be configured to perform any receiving operation and / or some obtaining operations described herein as being performed by the network node 800. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 810, the communication interface 806, and / or the processing circuit 802 may be configured to perform any transmitting operation described herein as being performed by the network node 800. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0123] The power supply 808 provides power to the various components of the network node 800 in a form suitable for each component (e.g., at the voltage and current levels required for each respective component). The power supply 808 may further comprise, or be coupled to, power management circuitry for supplying power to the components of the network node 800 for performing the functions described herein. For example, the network node 800 may be connectable to an external power source (e.g., a power grid or an electrical outlet) via an input circuit or interface, such as an electrical cable, whereby the external power source supplies power to the power circuitry of the power supply 808. As a further example, the power supply 808 may comprise a power source in the form of a battery or battery pack connected to or integrated in the power circuitry. The battery may provide backup power in the event that the external power source fails.

[0124] Embodiments of network node 800 may include additional components other than those shown in Figure 8 to provide certain aspects of the network node's functionality, including any of the functionality described herein and / or functionality necessary to support the subject matter described herein. For example, network node 800 may include user interface devices to enable input of information into network node 800 and output of information from network node 800. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 800.

[0125] 9 is a block diagram of a host 900, which may be an embodiment of the host 616 of FIG. 6 in accordance with various aspects described herein. As used herein, the host 900 may be or comprise various combinations of hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or processing resources in a server farm. The host 900 may provide one or more services to one or more UEs.

[0126] The host 900 includes a processing circuit 902 operably coupled to an input / output interface 906, a network interface 908, a power supply 910, and a memory 912 via a bus 904. In other embodiments, other components may be included. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as FIGS. 7 and 8, and therefore, those descriptions are generally applicable to the corresponding components of the host 900.

[0127] The memory 912 may include one or more computer programs, including one or more host application programs 914 and data 916, which may include user data, e.g., data generated by the UE for the host 900 or data generated by the host 900 for the UE. An embodiment of the host 900 may utilize only a subset or all of the shown components. The host application programs 914 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UE (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems). The host application program 914 may also provide user authentication and license checks, and may periodically report health, route, and content availability to a central node, such as a device in the core network or a device on the edge of the core network. Thus, the host 900 may select and / or direct different hosts for over-the-top (OTT) services for the UE. The host application program 914 may support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc.

[0128] FIG. 10 is a block diagram illustrating a virtualization environment 1000 in which functionality implemented by some embodiments may be virtualized. In this context, virtualizing means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage devices, and networking resources. Virtualization, as used herein, may apply to any device described herein, or components thereof, and relates to implementations in which at least a portion of functionality is implemented as one or more virtual components. Some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1000 hosted by one or more of the hardware nodes, such as a network node, a UE, a core network node, or a hardware computing device acting as a host. Furthermore, in embodiments in which the virtual node does not require wireless connectivity (e.g., to a core network node or host), the node may be fully virtualized.

[0129] An application 1002 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) is run in the virtualized environment 900 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0130] The hardware 1004 includes processing circuitry, memory that stores software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, etc. Software is executed by the processing circuitry to instantiate one or more virtualization layers 1006 (also referred to as a hypervisor or VM monitor (VMM)), provide VMs 1008A and 1008B (one or more of which may be referred to generically as VMs 1008), and / or implement any of the functions, features, and / or benefits described with respect to some embodiments described herein. The virtualization layer 1006 may present to the VMs 1008 a virtual operating platform that appears to be networking hardware.

[0131] The VMs 1008 may comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 1006. Different embodiments of the virtual appliance 1002 instance may be implemented on one or more of the VMs 1008, and the implementation may be done in different ways. Hardware virtualization is referred to in some contexts as network functions virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.

[0132] In the context of NFV, a VM 1008 may be a software implementation of a physical machine that runs programs as if those programs were running on a physical, non-virtualized machine. Each VM 1008 and the portion of the hardware 1004 on which it runs, whether hardware dedicated to that VM and / or hardware shared by that VM with other ones of the VMs 1008, form a separate virtual network element. Further, in the context of NFV, a virtual network function is responsible for handling a particular network function running in one or more VMs 1008 on the hardware 1004 and corresponds to the application 1002.

[0133] The hardware 1004 may be implemented in a standalone network node having general or specific components. The hardware 1004 may implement some functions via virtualization. Alternatively, the hardware 1004 may be part of a larger cluster of hardware (e.g., as in a data center or CPE) where many hardware nodes cooperate and are managed via a management and orchestration 1010 that, among other things, oversees the lifecycle management of the application 1002. In some embodiments, the hardware 1004 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with virtual components to provide a virtual node with wireless capabilities, such as a RAN or BS. In some embodiments, some signaling may be provided using a control system 1012, which may alternatively be used for communication between the hardware nodes and the radio units.

[0134] 11 shows a communication diagram of a host 1102 communicating with a UE 1106 via a network node 1104 over a partial wireless connection, according to some embodiments. Exemplary implementations according to various embodiments of a UE (such as UE 612A of FIG. 6 and / or UE 700 of FIG. 7), a network node (such as network node 610A of FIG. 6 and / or network node 800 of FIG. 8), and a host (such as host 616 of FIG. 6 and / or host 900 of FIG. 9) described in the previous paragraphs will now be described with reference to FIG. 11.

[0135] Similar to host 900, an embodiment of host 1102 includes hardware such as a communications interface, processing circuitry, and memory. Host 1102 also includes software stored on or accessible by host 1102 and executable by the processing circuitry. The software includes a host application that may be operable to provide services to a remote user, such as a UE 1106 connecting via an OTT connection 1150 extending between UE 1106 and host 1102. In providing services to a remote user, the host application may provide user data that is transmitted using the OTT connection 1150.

[0136] The network node 1104 includes hardware that enables the network node 1104 to communicate with the host 1102 and the UE 1106 over a connection 1160. The connection 1160 may be direct or may pass through one or more other intermediate networks, such as a core network (similar to the core network 606 of FIG. 6) and / or one or more public, private, or hosted networks. For example, the intermediate network may be a backbone network or the Internet.

[0137] The UE 1106 includes hardware and software stored on or accessible by the UE 1106 and executable by the UE's processing circuitry. The software includes a client application, such as a web browser or operator-specific "app," which, with the support of the host 1102, may be operable to provide services to a human or non-human user via the UE 1106. An executing host application on the host 1102 may communicate with an executing client application via an OTT connection 1150 that terminates at the UE 1106 and the host 1102. In providing services to the user, the UE's client application may receive request data from the host application and provide user data in response to the request data. The OTT connection 1150 may transfer both request data and user data. The UE's client application may interact with the user to generate user data that the UE's client application provides to the host application through the OTT connection 1150.

[0138] The OTT connection 1150 may extend via a connection 1160 between the host 1102 and the network node 1104 and via a wireless connection 1170 between the network node 1104 and the UE 1106 to provide connectivity between the host 1102 and the UE 1106. The connections 1160 and wireless connections 1170 over which the OTT connection 1150 may be provided are depicted abstractly to show communication between the host 1102 and the UE 1106 via the network node 1104, without explicit reference to intermediary devices and the precise routing of messages through these devices.

[0139] As an example of transmitting data over the OTT connection 1150, in step 1108, the host 1102 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1106. In other embodiments, the user data is associated with the UE 1106 sharing data with the host 1102 without explicit human interaction. In step 1110, the host 1102 initiates a transmission carrying user data toward the UE 1106. The host 1102 may initiate the transmission in response to a request sent by the UE 1106. The request may be caused by human interaction with the UE 1106 or by the operation of a client application executing on the UE 1106. The transmission may proceed via the network node 1104 in accordance with the teachings of the embodiments described throughout this disclosure. Thus, in step 1112, the network node 1104 transmits the user data carried in the transmission initiated by the host 1102 to the UE 1106, in accordance with the teachings of embodiments described throughout this disclosure. In step 1114, the UE 1106 receives the user data carried in the transmission, which may be performed by a client application running on the UE 1106 associated with the host application executed by the host 1102.

[0140] In some examples, the UE 1106 executes a client application that provides user data to the host 1102. The user data may be provided in reaction or response to data received from the host 1102. Thus, in step 1116, the UE 1106 may provide the user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from a user via an input / output interface of the UE 1106. Regardless of the particular manner in which the user data is provided, the UE 1106 initiates transmission of the user data towards the host 1102 via the network node 1104 in step 1118. In step 1120, the network node 1104 receives the user data from the UE 1106 and initiates transmission of the received user data towards the host 1102, in accordance with the teachings of embodiments described throughout this disclosure. In step 1122, the host 1102 receives the user data carried in the transmission initiated by the UE 1106.

[0141] One or more of the various embodiments improve the performance of the OTT service provided to the UE 1106 using the OTT connection 1150, of which the wireless connection 1170 forms the final segment. More precisely, the teachings of these embodiments may improve, for example, data rates, latency, power consumption, etc., thereby providing benefits such as, for example, reduced user latency, relaxed restrictions on file sizes, improved content resolution, better responsiveness, extended battery life, etc.

[0142] In an exemplary scenario, factory status information may be collected and analyzed by the host 1102. As another example, the host 1102 may process audio and video data that may have been retrieved from UEs for use in creating maps. As another example, the host 1102 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic signals). As another example, the host 1102 may store surveillance video uploaded by UEs. As another example, the host 1102 may store or control access to media content, such as video, audio, VR, or AR, that the host 1102 may broadcast, multicast, or unicast to UEs. As other examples, the host 1102 may be used for energy pricing, remote control of non-time-critical electrical loads to balance power generation needs, location services, presentation services (such as compiling diagrams, etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.

[0143] In some examples, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve. There may further be optional network functionality for reconfiguring the OTT connection 1150 between the host 1102 and the UE 1106 in response to fluctuations in the measurement results. The measurement procedures and / or the network functionality for reconfiguring the OTT connection 1150 may be implemented in software and hardware of the host 1102 and / or the UE 1106. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1150 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above or other physical quantities from which software can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1150 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not directly change the operation of the network node 1104. Such procedures and functionality may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation time, latency, etc. by the host 1102. The measurements may be implemented in software causing messages, particularly empty or "dummy" messages, to be sent using the OTT connection 1150 while monitoring propagation time, errors, etc.

[0144] While the computing devices (e.g., UEs, network nodes, hosts) described herein may include the depicted combinations of hardware components, other embodiments may comprise computing devices having different combinations of components. It should be understood that these computing devices may comprise any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, transforming the obtained information to other information, comparing the obtained or transformed information to information stored in a network node, and / or performing one or more operations based on the obtained or transformed information and as a result of the processing making a decision. Moreover, while a component is illustrated as a single box located within a larger box or nested within multiple boxes, in reality the computing device may comprise multiple different physical components that make up the single depicted component, and functionality may be partitioned among the separate components. For example, a communications interface may be configured to include any of the components described herein, and / or the functionality of those components may be partitioned between the processing circuitry and the communications interface. In another example, non-computationally intensive functionality of any of such components may be implemented in software or firmware, and computationally intensive functionality may be implemented in hardware.

[0145] In some embodiments, some or all of the functionality described herein may be provided by a processing circuit executing instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuit without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of these particular embodiments, the processing circuit may be configured to perform the described functionality, regardless of whether or not it executes instructions stored on a non-transitory computer-readable storage medium. Benefits provided by such functionality are not limited to the processing circuit alone or to other components of the computing device, but are enjoyed by the computing device as a whole and / or by end users and wireless networks generally.

[0146] Embodiment 1: A method implemented by a user equipment (UE), the method including: a. determining when to apply Doppler domain compression and when to avoid Doppler domain compression when feeding back channel state information (CSI) reports (e.g., Type II CSI) (400); b. determining a signaled number of CSI instances for which a gNB requests the UE to calculate CSI (402); and c. determining whether to apply CSI compression in the Doppler domain based on the number of CSI instances (404).

[0147] Embodiment 2: The method of embodiment 1, wherein the selected Doppler domain basis vectors are fed back when CSI compression needs to be applied.

[0148] Embodiment 3: The method of embodiment 1 or 2, wherein the selected Doppler domain basis vectors are part of Type II CSI feedback.

[0149] Embodiment 4: The method of any one of embodiments 1 to 3, wherein the selected Doppler domain basis vectors are indicated via an index.

[0150] Embodiment 5: The method according to any one of embodiments 1 to 4, wherein when CSI compression is not applied, the UE does not select Doppler domain basis vectors and does not need to feed back Doppler domain basis vectors.

[0151] Embodiment 6: The method according to any one of embodiments 1 to 5, wherein there is no need to feed back indices representing Doppler domain basis vectors.

[0152] Embodiment 7: The method of any one of embodiments 1 to 6, wherein determining the signaled number of CSI instances includes receiving a number of CSI instances (denoted as NCSI) for which the gNB requests the UE to feed back CSI.

[0153] Embodiment 8: The method of any one of embodiments 1 to 7, wherein the value for the time unit is configured in the UE by the gNB.

[0154] Embodiment 9: The method of any one of embodiments 1 to 8, wherein the time unit is a minimum time gap between any two non-zero power (NZP) CSI-RS samples (or resources) in a set of NZP CSI-RS samples used to calculate CSI corresponding to the NZS CSI instances.

[0155] Embodiment 10: The method according to any one of embodiments 1 to 9, wherein the number of time instances NCSI at which the gNB requests the UE to feed back CSI is explicitly signaled via an explicit parameter.

[0156] Embodiment 11: The method according to any one of Embodiments 1 to 10, wherein the number NCSI of time instances for which the gNB requests the UE to feedback CSI is implicitly signaled via a combination of one or more other parameters.

[0157] Embodiment 12: The method according to any one of Embodiments 1 to 11, wherein a threshold Nth is either signaled to the UE or pre-specified in the specification.

[0158] Embodiment 13: The method according to any one of Embodiments 1 to 12, wherein the threshold is used to define UE behavior regarding when to select the Doppler region basis vectors as part of Wd or when to set the Wd matrix to the identity matrix.

[0159] Embodiment 14: When the threshold Nth is signaled as a parameter, the threshold is set either as part of the CSI-ReportConfig IE or as part of the CodebookConfig IE, according to the method described in any one of Embodiments 1 to 13.

[0160] [[ID=!5]] Embodiment 15: If the number NCSI of time instances for which the gNB requests the UE to feedback CSI is less than the threshold Nth (i.e., NCSI < Nth), the UE assumes no compression in the Doppler region and / or sets the matrix Wd to the identity matrix, according to the method described in any one of Embodiments 1 to 14.

[0161] Embodiment 16: If the number NCSI of time instances for which the gNB requests the UE to feedback CSI is less than or equal to the threshold Nth (i.e., NCSI ≤ Nth), the UE assumes no compression in the Doppler region and / or sets the matrix Wd to the identity matrix, according to the method described in any one of Embodiments 1 to 15.

[0162] Embodiment 17: The method of any one of embodiments 1 to 16, wherein if the number NCSI of time instances at which the gNB requests the UE to feed back CSI is greater than a threshold Nth (i.e., NCSI>Nth), the UE assumes that there is compression in the Doppler domain and / or selects one or more Doppler domain basis vectors that are columns of the Wd matrix.

[0163] Embodiment 18: The method of any one of embodiments 1 to 17, further comprising feeding back the selected Doppler domain basis vector for each layer in the form of an index i1,9,l, where i1,9,l represents the selected Doppler domain basis vector corresponding to the lth layer.

[0164] Embodiment 19: The method of any one of embodiments 1 to 18, further comprising feeding back the selected Doppler domain basis vector for each SD / FD pair for each layer in the form of an index i1,9,sdfd,l, where i1,9,sdfd,l represents the selected Doppler domain basis vector corresponding to the lth layer and the sdfdth SD / FD basis pair.

[0165] Embodiment 20: The method of any one of embodiments 1 to 19, wherein the number of Doppler domain basis vectors to be selected is signaled by the gNB to the UE either as a standalone upper layer parameter or as a parameter indicating a combination of parameters.

[0166] Embodiment 21: The method of any one of embodiments 1 to 20, wherein whether the UE assumes no compression in the Doppler domain or compression in the Doppler domain is determined by a parameter (or combination of parameters) that indicates the number of Doppler domain basis vectors to be selected.

[0167] Embodiment 22: The method according to any one of embodiments 1 to 21, wherein if the number of Doppler domain basis vectors to be selected is indicated as 0, the UE assumes that there is no compression in the Doppler domain.

[0168] Embodiment 23: The method of any one of embodiments 1 to 22, wherein if the number of Doppler domain basis vectors to be selected is indicated as a non-zero value, the UE assumes that there is compression in the Doppler domain.

[0169] Embodiment 24: The method of any one of embodiments 1 to 23, wherein the CSI for N CSI time instances is reported as a single PMI value.

[0170]

[0071] Embodiment 25: The method according to any one of embodiments 1 to 24, wherein the number of time instances NCSI at which the gNB requests the UE to feed back CSI is signaled as part of the CSI-ReportConfig IE.

[0171]

[0082] Embodiment 26: The method according to any one of embodiments 1 to 25, wherein the NCSI is configured via an RRC configured parameter numCsiInstances-r18.

[0172] Embodiment 27: The method according to any one of embodiments 1 to 26, wherein a parameter firstTimeUnitCSI-r18 is RRC configured as part of the CSI-ReportConfig IE, which indicates the time unit (or alternatively, a slot or subslot) corresponding to the first CSI instance among the N CSI CSI instances.

[0173] Embodiment 28: The method according to any one of embodiments 1 to 27, wherein firstTimeUnitCSI-r18 is defined for the slot in which the CSI should be reported (i.e., if the CSI should be reported in slot n, the time unit corresponding to the first CSI instance is given by n+firstTimeUnitCSI-r18).

[0174] Embodiment 29: The method according to any one of embodiments 1 to 28, wherein firstTimeUnitCSI-r18 is defined for a slot containing a CSI reference resource (i.e., if CSI is to be reported in slot nCSI-ref, the time unit corresponding to the first CSI instance is given by nCSI-ref+firstTimeUnitCSI-r18).

[0175] Embodiment 30: The method of any one of embodiments 1 to 29, further comprising receiving a signal having a timeUnitStepSize and an indication of the total number of time units.

[0176] Embodiment 31: The method according to any one of embodiments 1 to 30, wherein the number of instances NCSI can be determined as floor(total number of time units / timeUnitStepSize).

[0177]

[0039] Embodiment 32: The method according to any one of embodiments 1 to 31, wherein any of the above parameters is signaled as part of a CodebookConfig IE.

[0178] Embodiment 33: The method according to any one of embodiments 1 to 32, wherein one or more of firstTimeUnitCSI, timeUnitStepSize, and numCsiInstances are signaled via a codepoint in a DCI field of the DCI.

[0179] Embodiment 34: The method according to any one of embodiments 1 to 33, wherein different code points of the DCI field in the DCI can indicate different combinations of the firstTimeUnitCSI value, the numCsiInstances value, and the timeUnitStepSize value.

[0180] Embodiment 35: The method according to any one of embodiments 1 to 34, wherein the value of any one of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize, which is not indicated to the UE by the DCI, is indicated to the UE by the network via higher layer configuration (e.g., via RRC).

[0181] Embodiment 36: The method according to any one of embodiments 1 to 35, wherein one or more values ​​of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize are indicated by MAC CE signaling.

[0182]

[0037] Embodiment 37: The method of any one of embodiments 1 to 36, further comprising providing user data and forwarding the user data to the host via transmission to the network node.

[0183] Group B Embodiments

[0184] Embodiment 38: A method implemented by a network node, the method including: a. indicating (500) a number of CSI instances for which the network node requests a user equipment (UE) to calculate channel state information (CSI); and b. receiving CSI with or without CSI compression in the Doppler domain based on the number of CSI instances (502).

[0185] Embodiment 39: The method of embodiment 38, including any of the features of the embodiments of Group A.

[0186] Embodiment 40: The method of embodiment 38 or 39, further comprising obtaining user data and forwarding the user data to a host or user equipment.

[0187] Group C Embodiments

[0188] Embodiment 41: A user equipment, comprising: a processing circuit configured to perform any of the steps recited in any one of the embodiments of group A; and a power supply circuit configured to supply power to the processing circuit. User equipment.

[0189] Embodiment 42: A network node, the network node comprising: a processing circuit configured to perform any of the steps recited in any one of the embodiments of Group B; and a power supply circuit configured to supply power to the processing circuit.

[0190] Embodiment 43: A user equipment (UE), comprising: an antenna configured to send and receive radio signals; a radio front-end circuit connected to the antenna and a processing circuit and configured to condition signals communicated between the antenna and the processing circuit, the processing circuit configured to perform any of the steps described in any one of the embodiments of Group A; an input interface connected to the processing circuit and configured to enable information input to the UE to be processed by the processing circuit; an output interface connected to the processing circuit and configured to output information from the UE that has been processed by the processing circuit; and a battery connected to the processing circuit and configured to provide power to the UE.

[0191] Embodiment 44: A host configured to operate in a communication system for providing over-the-top (OTT) services, the host comprising: a processing circuit configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), the UE comprising a communication interface and a processing circuit, the communication interface and processing circuit of the UE being configured to perform any of the steps described in any one of the embodiments of Group A to receive the user data from the host.

[0192] Embodiment 45: The host of embodiment 44, wherein the cellular network further includes a network node configured to communicate with the UE to transmit user data from the host to the UE.

[0193] Embodiment 46: A host as described in embodiment 44 or 45, wherein the processing circuitry of the host is configured to execute a host application to thereby provide user data, and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0194] Embodiment 47: A method implemented by a host operating in a communication system further including a network node and a user equipment (UE), the method including providing user data for the UE and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations described in any one of the embodiments of Group A to receive the user data from the host.

[0195]

[0082] Embodiment 48: The method of embodiment 47, further comprising: executing, at the host, a host application associated with the client application executing on the UE to receive user data from the UE.

[0083] Embodiment 49: The method of embodiment 48, further comprising: sending, at the host, input data to the client application executing on the UE, the input data being provided by executing the host application, and the user data being provided by the client application in response to the input data from the host application.

[0196] Embodiment 49: The method of embodiment 48, further comprising: in the host, sending input data to a client application executing on the UE, the input data being provided by executing the host application, and the user data being provided by the client application in response to the input data from the host application.

[0197] Embodiment 50: A host configured to operate in a communication system for providing over-the-top (OTT) services, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), the UE comprising a communications interface and processing circuitry, the communications interface and processing circuitry of the UE being configured to perform any of the steps described in any one of the embodiments of Group A to transmit the user data to the host.

[0198] Embodiment 51: The host of embodiment 50, wherein the cellular network further includes a network node configured to communicate with the UE to transmit user data from the UE to the host.

[0199] Embodiment 52: A host as described in embodiment 50 or 51, wherein the processing circuitry of the host is configured to execute a host application thereby to provide user data, the host application is configured to interact with a client application executing on the UE, and the client application is associated with the host application.

[0200] Embodiment 53: A method implemented by a host configured to operate in a communication system further including a network node and a user equipment (UE), the method including receiving, at the host, user data transmitted by the UE to the host via the network node, and the UE performing any of the steps described in any one of the embodiments of Group A to transmit the user data to the host.

[0201] Embodiment 54: The method of embodiment 53, further comprising: executing, at the host, a host application associated with the client application executing on the UE to receive user data from the UE.

[0202] Embodiment 55: The method of embodiment 54, further comprising: in the host, sending input data to a client application executing on the UE, the input data being provided by executing the host application, and the user data being provided by the client application in response to the input data from the host application.

[0203] Embodiment 56: A host configured to operate in a communication system for providing over-the-top (OTT) services, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communications interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations described in any one of the embodiments of Group B to transmit the user data from the host to the UE.

[0204] Embodiment 57: The host of embodiment 56, wherein processing circuitry of the host is configured to execute a host application that provides user data, and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive transmissions of user data from the host.

[0205] Embodiment 58: A method implemented in a host configured to operate in a communication system further including a network node and a user equipment (UE), the method including providing user data for the UE and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, the network node performing any of the operations described in any one of the embodiments of Group B to transmit the user data from the host to the UE.

[0206]

[0082] Embodiment 59: The method of embodiment 58, further comprising: transmitting, at the network node, user data provided by the host for the UE.

[0207] Embodiment 60: The method of embodiment 58 or 59, wherein the user data is provided in the host by executing a host application that interacts with a client application running on the UE, and the client application is associated with the host application.

[0208] Embodiment 61: A communications system configured to provide over-the-top services, the communications system comprising a host, the host comprising processing circuitry configured to provide user data for a user equipment (UE), the user data relating to the over-the-top services, and a network interface configured to initiate transmission of the user data to a cellular network node for transmission to the UE, the network node having a communications interface and processing circuitry, the network interface configured to perform any of the operations described in any one of the embodiments of Group B to transmit the user data from the host to the UE.

[0209] Embodiment 62: The communication system of embodiment 61, further comprising a network node and / or user equipment.

[0210] Embodiment 63: A host configured to operate in a communication system for providing over-the-top (OTT) services, the host comprising: a processing circuit configured to initiate reception of user data; and a network interface configured to receive user data from a network node in a cellular network, the network node having a communication interface and a processing circuit, the processing circuit of the network node configured to perform any of the operations described in any one of the embodiments of Group B to receive user data from a user equipment (UE) for the host.

[0211] Embodiment 64: A host as described in embodiment 63, wherein the processing circuitry of the host is configured to execute a host application thereby to provide user data, and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0212] Embodiment 65: The host of embodiment 63 or 64, wherein initiating the reception of user data includes requesting the user data.

[0213] Embodiment 66: A method implemented by a host configured to operate in a communication system further including a network node and a user equipment (UE), the method including initiating, at the host, reception of user data from the UE, the user data originating from a transmission received by the network node from the UE, and the network node performing any of the steps described in any one of the embodiments of Group B to receive the user data from the UE for the host.

[0214] Embodiment 67: The method of embodiment 66, further comprising, at the network node, transmitting the received user data to the host.

[0215] At least some of the following abbreviations may be used in this disclosure. In the event of inconsistencies between abbreviations, the abbreviation as used above should prevail. If listed multiple times below, the first listing should prevail over the subsequent listing(s). 3GPP 3rd Generation Partnership Project 5G (fifth generation) 5GC 5th generation core 5GS 5th generation system AF application features AMF access and mobility features AN Access Network AP access point ASIC Application Specific Integrated Circuit AUSF authentication server function CE control element CPU Central Processing Unit CSI (Channel State Information) CSI-RS Channel State Information Reference Signal DCI Downlink Control Information DN Data Network DSP Digital Signal Processor eNB Enhanced or Evolved Node B EPS Evolved Packet System E-UTRA Enhanced Universal Terrestrial Radio Access FPGA Field Programmable Gate Array · gNB New wireless base station gNB-DU New Radio Base Station Distributed Unit HSS Home Subscriber Server IE Information Elements IoT (Internet of Things) IP Internet Protocol LTE Long Term Evolution MAC Media Access Control MME Mobility Management Entity MTC Machine Type Communication NEF network publishing function NF network function · NR new radio NRF Network Function Repository Function NSSF network slice selection function · NZP non-zero power OTT (Over-the-Top) PC personal computer PCF policy control function P-GW Packet Data Network Gateway PMI precoder matrix indicator QoS Quality of Service RAM Random Access Memory RAN Radio Access Network ROM Read-Only Memory RRC Radio Resource Control RRH Remote Radio Head RTT Round Trip Time SCEF Service Capability Publishing Function SMF session management function UDM Integrated Data Management UE User Equipment UPF user plane function

[0216] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure, and all such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

1. 1. A method implemented by a user equipment (UE) for channel state information (CSI) reporting, comprising: determining 402 a signaled number of CSI instances for which a network node requests the UE to calculate CSI, each CSI instance corresponding to CSI for a duration of a time unit; determining whether to apply CSI compression in the Doppler domain based on the number of CSI instances (404); A method comprising:

2. The method of claim 1 , further comprising: feeding back selected Doppler domain basis vectors when CSI compression needs to be applied.

3. The method of claim 1 or 2, wherein the selected Doppler domain basis vectors are part of Type II CSI feedback.

4. The method of claim 1 , wherein the selected Doppler domain basis vectors are indicated via an index.

5. The method of claim 1 , wherein when CSI compression is not applied, the UE feeds back Type II CSI reports without feeding back Doppler domain basis vectors.

6. 6. The method of claim 1, wherein determining the signaled number of CSI instances comprises receiving the number of CSI instances (denoted as NCSI), for which the network node requests the UE to feed back CSI within a single CSI report.

7. The method of claim 1 , wherein the value for the time unit is configured in the UE by the network node.

8. 8. The method of claim 1, wherein the time unit is a minimum time gap between any two non-zero power (NZP) CSI-RS samples in a set of NZP CSI-RS samples used to calculate the CSI corresponding to N CSI CSI instances.

9. 9. The method of claim 1, wherein the number of time instances N CSI at which the network node requests the UE to feed back CSI is explicitly signaled via an explicit parameter.

10. 10. The method of claim 1, wherein the number of time instances N CSI at which the network node requests the UE to feed back CSI is implicitly signaled via a combination of one or more other parameters.

11. The method according to claim 1 , wherein the threshold value Nth is pre-specified in a specification.

12. 12. The method of claim 1, wherein a threshold is used to define UE behavior regarding when to select Doppler domain basis vectors as part of Type II CSI feedback or when to feedback Type II CSI reports without feeding back Doppler domain basis vectors.

13. A method according to any one of claims 1 to 12, further comprising receiving a combination index indicator of N4, where N4 is the Doppler domain basis vector length and MDD,l is the number of Doppler domain basis vectors to be selected.

14. 14. The method of claim 1, wherein if the number of time instances N CSI , at which the network node requests the UE to feedback CSI, is less than a threshold Nth, the UE assumes no compression in the Doppler domain and / or does not feed back Doppler domain basis vectors as part of a Type II CSI report.

15. 15. The method of claim 1, wherein if the number of time instances N CSI , at which the network node requests the UE to feedback CSI, is less than or equal to a threshold Nth, the UE assumes no compression in the Doppler domain and / or does not feed back Doppler domain basis vectors as part of a Type II CSI report.

16. 16. The method of claim 1, wherein if the number N CSI of time instances at which the network node requests the UE to feedback CSI is greater than a threshold Nth, the UE assumes that there is compression in the Doppler domain and / or selects one or more Doppler domain basis vectors to be part of Type II CSI feedback.

17. 17. The method of claim 1, further comprising: feeding back selected Doppler domain basis vectors for each layer in the form of an index i1,9,l, where i1,9,l represents the selected Doppler domain basis vector corresponding to the lth layer.

18. 18. The method of claim 1, wherein the number of Doppler-domain basis vectors to be selected is signaled to the UE by the network node either as a standalone higher layer parameter or as a parameter indicating a combination of parameters.

19. 19. The method of claim 1, wherein the CSI for N CSI time instances is reported as a single precoder matrix indicator (PMI) value.

20. 20. The method of any one of claims 1 to 19, wherein the number of time instances N CSI at which the network node requests the UE to feed back CSI is signaled as part of a CSI-ReportConfig IE.

21. 21. The method of any one of claims 1 to 20, wherein the NCSI is configured via a Radio Resource Control (RRC) configured parameter numCsiInstances-r18.

22. 22. The method according to claim 1, wherein a parameter firstTimeUnitCSI-r18 is RRC configured as part of a CSI-ReportConfig information element (IE), which indicates the time unit corresponding to a first CSI instance among N CSI CSI instances.

23. A method according to any one of claims 1 to 22, wherein firstTimeUnitCSI-r18 is defined for a slot for which CSI should be reported.

24. A method according to any one of claims 1 to 23, wherein firstTimeUnitCSI-r18 is defined for a slot containing a CSI reference resource.

25. 25. The method of any one of claims 1 to 24, further comprising receiving a signal having a timeUnitStepSize and an indication of the total number of time units.

26. 26. The method of claim 1, wherein the number of instances NCSI can be determined as floor(total number of time units / timeUnitStepSize).

27. 27. The method of any one of claims 1 to 26, wherein any of the above parameters are signaled as part of a CodebookConfig IE.

28. 27. The method of claim 1, wherein one or more of firstTimeUnitCSI, timeUnitStepSize, and numCsiInstances are signaled via codepoints in a Downlink Control Information (DCI) field of a DCI.

29. 29. The method of claim 1, wherein different codepoints of the DCI field in the DCI can indicate different combinations of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize values.

30. 30. The method according to claim 1, wherein the value of any one of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize, which is not indicated to the UE by DCI, is indicated to the UE by a network via higher layer configuration.

31. 30. The method of claim 1, wherein one or more values ​​of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize are indicated by medium access control (MAC) control element (CE) signaling.

32. 1. A method implemented by a network node, the method comprising: indicating (500) a number of channel state information (CSI) instances for which the network node requests a user equipment (UE) to calculate CSI, each CSI instance corresponding to CSI for a duration of a time unit; receiving CSI with or without CSI compression in the Doppler domain based on the number of CSI instances (502); A method comprising:

33. 33. The method of claim 32, receiving selected Doppler domain basis vectors when CSI compression needs to be applied.

34. 34. The method of claim 32 or 33, wherein the selected Doppler domain basis vectors are part of Type II CSI feedback.

35. 35. The method of any one of claims 32 to 34, wherein the selected Doppler domain basis vector is indicated via an index.

36. 36. The method of any one of claims 32 to 35, wherein when CSI compression is not applied, the UE feeds back Type II CSI reports without feeding back Doppler domain basis vectors.

37. 37. The method of claim 32, wherein determining a signaled number of CSI instances comprises transmitting the number of CSI instances (denoted as NCSI) for which the network node requests the UE to feed back CSI within a single CSI report.

38. 38. The method of any one of claims 32 to 37, wherein the value for the time unit is configured in the UE by the network node.

39. 39. The method of claim 32, wherein the time unit is a minimum time gap between any two non-zero power (NZP) CSI-RS samples in a set of NZP CSI-RS samples used to calculate the CSI corresponding to N CSI CSI instances.

40. 40. The method of any one of claims 32 to 39, wherein the number of time instances N CSI at which the network node requests the UE to feed back CSI is explicitly signaled via an explicit parameter.

41. 41. The method of any one of claims 32 to 40, wherein the number of time instances N CSI at which the network node requests the UE to feed back CSI is implicitly signaled via a combination of one or more other parameters.

42. 42. The method of any one of claims 32 to 41, wherein the threshold value Nth is pre-specified in a specification.

43. 43. The method of any one of claims 32 to 42, wherein a threshold is used to define UE behavior regarding when to select Doppler domain basis vectors as part of Type II CSI feedback or when to feedback Type II CSI reports without feeding back Doppler domain basis vectors.

44. The method of any one of claims 32 to 43, further comprising transmitting a combination index indicator, wherein N4 is the Doppler domain basis vector length and MDD,l is the number of Doppler domain basis vectors to be selected.

45. 45. The method of any one of claims 32 to 44, wherein if the number N CSI of time instances at which the network node requests the UE to feedback CSI is less than a threshold Nth, the UE assumes no compression in the Doppler domain and / or does not feed back Doppler domain basis vectors as part of a Type II CSI report.

46. 46. ​​The method of any one of claims 32 to 45, wherein if the number N CSI of time instances at which the network node requests the UE to feedback CSI is less than or equal to a threshold Nth, the UE assumes no compression in the Doppler domain and / or does not feed back Doppler domain basis vectors as part of a Type II CSI report.

47. 47. The method of any one of claims 32 to 46, wherein if the number N CSI of time instances at which the network node requests the UE to feedback CSI is greater than a threshold Nth, the UE assumes that there is compression in the Doppler domain and / or selects one or more Doppler domain basis vectors to be part of Type II CSI feedback.

48. 48. The method of claim 32, further comprising receiving a selected Doppler domain basis vector for each layer in the form of an index i1,9,l, where i1,9,l represents the selected Doppler domain basis vector corresponding to the lth layer.

49. 49. The method of any one of claims 32 to 48, wherein the number of Doppler-domain basis vectors to be selected is signaled to the UE by the network node either as a standalone upper layer parameter or as a parameter indicating a combination of parameters.

50. 50. The method of any one of claims 32 to 49, wherein the CSI for N CSI time instances is reported as a single PMI value.

51. 51. The method of any one of claims 32 to 50, wherein the number of time instances N CSI at which the network node requests the UE to feed back CSI is signaled as part of a CSI-ReportConfig IE.

52. A method according to any one of claims 32 to 51, wherein the NCSI is configured via an RRC configured parameter numCsiInstances-r18.

53. 53. The method of claim 32, wherein a parameter firstTimeUnitCSI-r18 is RRC configured as part of a CSI-ReportConfig IE, which indicates the time unit corresponding to a first CSI instance among N CSI CSI instances.

54. A method according to any one of claims 32 to 53, wherein firstTimeUnitCSI-r18 is defined for a slot for which CSI should be reported.

55. A method according to any one of claims 32 to 54, wherein firstTimeUnitCSI-r18 is defined for a slot containing a CSI reference resource.

56. 56. The method of any one of claims 32 to 55, further comprising receiving a signal having a timeUnitStepSize and an indication of the total number of time units.

57. 57. The method of any one of claims 32 to 56, wherein the number of instances NCSI can be determined as floor(total number of time units / timeUnitStepSize).

58. 58. The method of any one of claims 32 to 57, wherein any of the above parameters are signaled as part of a CodebookConfig IE.

59. 59. The method of any one of claims 32 to 58, wherein one or more of firstTimeUnitCSI, timeUnitStepSize, and numCsiInstances are signaled via codepoints in a DCI field of the DCI.

60. 60. The method of any one of claims 32 to 59, wherein different codepoints of the DCI field in the DCI can indicate different combinations of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize values.

61. 61. The method according to claim 32, wherein the value of any one of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize, which is not indicated to the UE by DCI, is indicated to the UE by a network via upper layer configuration.

62. 62. The method of any one of claims 32 to 61, wherein values ​​of one or more of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize are indicated by MAC CE signaling.

63. A user equipment (UE) (700) comprising processing circuitry (702) and memory (710), said memory (710) configured to: determining a signaled number of channel state information (CSI) instances for which a network node requests the UE to calculate CSI, each CSI instance corresponding to CSI for a duration of a time unit; determining whether to apply CSI compression in the Doppler domain based on the number of CSI instances; a user device (700) including instructions for causing the user device (700) to:

64. 64. The UE (700) of claim 63, further operable to implement the features of any one of claims 2 to 31.

65. A network node (800) comprising a processing circuit (802) and a memory (804), said memory (804) providing to said network node (800): indicating a number of channel state information (CSI) instances for which the network node requests a user equipment (UE) to calculate CSI, each CSI instance corresponding to CSI for a duration of a time unit; receiving CSI with or without CSI compression in the Doppler domain based on the number of CSI instances; A network node (800) comprising instructions for causing the network node to:

66. A network node (800) according to claim 65, further operable to implement the features according to any one of claims 33 to 62.

67. 32. A computer-readable medium comprising instructions that, when executed on at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 31.

68. 63. A computer readable medium comprising instructions that, when executed on at least one processor, cause the at least one processor to perform the method of any one of claims 32 to 62.

Images