Method for high speed CSI reporting using type ii codebooks

Abstract

Systems and methods are provided for high speed channel state information (CSI) reporting using type II codebooks. In some embodiments, the method includes determining when Doppler domain compression is applied and when Doppler domain compression is avoided in feeding back CSI reports; determining a number of signaled CSI instances for which the network node requests the 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 allow the network and UE to support situations with and without Doppler domain compression under a single CSI reporting framework. Based on signaling received from the network, the solution allows the UE to determine when to feed back a selected Doppler domain base in the Type II CSI report and when to avoid Doppler domain base selection in the Type II CSI report.

Description

[0001] Related Applications

[0002] This application claims the benefit of provisional patent application serial number 63 / 409,394, filed on September 23, 2022, the disclosure of which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to reporting channel state information (CSI). Background Art

[0004] Multiple antenna technology can significantly improve the data rate and reliability of wireless communication systems. If both the transmitter and the receiver are equipped with multiple antennas, which leads to a multiple-input multiple-output (MIMO) communication channel, the performance is particularly improved. Such systems and / or related technologies are generally referred to as MIMO.

[0005] New Radio (NR) standards are currently evolving with enhanced MIMO support. A core component in NR is support for MIMO antenna deployment and MIMO related technologies such as spatial multiplexing. The spatial multiplexing mode aims at high data rates under favorable channel conditions. Figure 1 A description of spatial multiplexing operation is provided in .

[0006] As shown in the figure, the information carrying the symbol vector s is related to N T xr is multiplied by the precoder matrix W, which is used to distribute the transmit energy over N T (corresponding to N T 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.

[0007] NR uses OFDM in the downlink (and DFT-precoded OFDM in the uplink for rank 1 transmission), and therefore, for a certain TFRE (or alternatively, data FRE number n) on subcarrier n, the received N R x 1 vector y n It is therefore modeled by:

[0008] y n =H n W n +en

[0009] Among them, e n is the noise / interference vector obtained as a realization of a random process. The precoder W can be a wideband precoder, which is constant in frequency, or can be frequency selective.

[0010] The precoder matrix W is usually chosen to be consistent with N R xN T MIMO channel matrix H n This is also often referred to as closed-loop precoding and is essentially an effort to focus the transmission energy into a subspace that is strong in the sense that most of the transmission energy is delivered to the UE.

[0011] In closed-loop precoding for NR downlink, the UE sends a recommendation to the gNB of a suitable precoder to be used based on channel measurements in the downlink. The gNB configures the UE to provide feedback according to the CSI-ReportConfig, and may send a CSI-RS, and configures the UE to use measurements of the CSI-RS to feedback a recommended precoding matrix that the UE selected from the codebook. A single precoder that should cover a large bandwidth (wideband precoding) may be fed back. It may also be beneficial to match the frequency variation of the channel and instead feed back frequency selective precoding reports (e.g., several precoders, one per subband). This is an example of a more general case of channel state information (CSI) feedback, which also includes feeding back other information in addition to 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 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 a number of consecutive resource blocks between 4-32 PRBs depending on the bandwidth part (BWP) size.

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

[0013] With multi-user MIMO (MU-MIMO), two or more users in the same cell are co-scheduled on the same one or more time-frequency resources. That is, two or more independent data streams are transmitted to different UEs at the same time, and the corresponding streams can usually be separated using the spatial domain. By transmitting multiple streams simultaneously, the capacity of the system can be increased. However, this comes at the expense of reducing the SINR of each stream, because power must be shared between streams, and the streams will cause mutual interference.

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

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

[0016] The CSI-RS may be configured to be transmitted in certain REs in one slot and certain slots. Figure 2 An example of CSI-RS REs for 12 antenna ports is shown, where 1 RE per RB per port is shown.

[0017] In addition, interference measurement resources (IMR) are defined in NR for UE to measure interference. IMR resources contain 4 REs, which are 4 adjacent REs in frequency in the same OFDM symbol or 2×2 adjacent REs in time and frequency in a time slot. By measuring the NZP CSI-RS-based channel and IMR-based interference, the UE can estimate the effective channel and noise plus interference to determine CSI, i.e., rank, precoding matrix, and channel quality.

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

[0019] CSI framework in NR

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

[0021] Each CSI report setting contains at least the following information:

[0022] CSI-RS resource set for channel measurement

[0023] Optionally, a CSI-RS resource set for interference measurement

[0024] Time domain behavior, i.e. periodic, semi-persistent or aperiodic reporting

[0025] Frequency granularity, i.e. broadband or sub-band

[0026] In case there are multiple CSI-RS resources in a resource set, the CSI parameters to be reported, such as RI, PMI, CQI and CSI-RS Resource Indicator (CRI)

[0027] Codebook type, i.e., Type I or Type II, and codebook subset restrictions

[0028] Measurement limitations

[0029] Subband size. Indicates one of two possible subband sizes, with a value range that depends on the bandwidth of the BWP. One CQI / PMI is fed back per subband (if configured as subband reporting).

[0030] When a CSI-RS resource set in the CSI reporting setting contains multiple CSI-RS resources, the UE selects one of the CSI-RS resources, and the UE also reports a CSI-RS resource indicator (CRI) to indicate to the gNB the selected CSI-RS resource in the resource set, as well as the RI, PMI, and CQI associated with the selected CSI-RS resource.

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

[0032] Type I and Type II codebooks in NR

[0033] The UE typically uses Type-I codebook (CB) to report CSI for single-user MIMO (SU-MIMO) scheduling in NR, while Type-II CB is typically used for more accurate CSI feedback for multi-user MIMO (MU-MIMO) scheduling.

[0034] For Type I and Type II CB, for each rank, the precoding matrix W is defined in the following form:

[0035] W=W1W2

[0036] in, is a 2N x 2L matrix and contains the L selected DFT beams {d i ,i=1,…,L}, where d i is an Nx1 DFT vector, and N is the number of CSI-RS ports per polarization; while W2 is a 2L×v matrix and contains the co-phase coefficients between the selected beams and also the co-phase coefficients 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, while W2 can be the same for the entire bandwidth or for each subband.

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

[0038] Enhanced Type II Codebook in NR

[0039] In NR Rel-16, the Type II codebook is enhanced by applying frequency domain (FD) compression across all subbands to reduce CSI feedback overhead and / or improve CSI accuracy. Instead of reporting W2 for each subband, a linear combination of DFT basis vectors is used to jointly represent W2 across the entire CSI bandwidth. For each layer, the precoding matrix W across all subbands is of the following form:

[0040]

[0041] Among them, W f =[f1,…,f M ] is a matrix containing M selected DFT basis vectors {f1,…,f M}, is a 2L×M matrix containing coefficients for each selected DFT beam and each selected FD basis vector.

[0042] To save reporting overhead, and because Some coefficients in are usually weak, so for each layer i, only K NZ,i ≤K0<2LM i A subset of non-zero coefficients (NZC). 2LM i -K NZ,i Unreported coefficients are assumed to be zero. The maximum number of non-zero coefficients per layer is in, is RRC configured. For RI = {2,3,4}, the maximum total number of NZCs across all layers is ≤ 2K0. In order to let the gNB know Which coefficients have been chosen in the , size 2LM for each layer i i A bitmap is used to indicate the NZC for this layer.

[0043] Enhanced Type II codebook for high / medium UE speeds

[0044] It has been observed in measurements in real deployments that downlink MU-MIMO precoding performance degrades when one or more of the co-scheduled UEs starts moving faster than a few km / h relative to the base station. One of the main reasons is that when this happens, the information used to calculate the channel for the MIMO precoding at the base station quickly becomes outdated. As a result, the precoder loses its effectiveness in protecting the co-scheduled users from interference when transmitting to the target user. Therefore, downlink MU-MIMO precoding needs to be robust to higher UE speeds.

[0045] One solution to mitigate this problem and cope with such rapid channel changes is to configure faster CSI reporting (i.e. more frequent CSI reporting and measurements). The problem with using this approach is that this results in large signaling and reporting overhead. Furthermore, even with the increased CSI-RS periodicity, there are still CSI reporting and scheduling delays, which can cause the reported CSI to become outdated. Therefore, using the current CSI framework in NR, it is difficult to obtain accurate CSI for medium and high-speed UEs with a reasonable amount of overhead.

[0046] MIMO evolution for downlink and uplink has been agreed in 3GPP Rel-18 work items (e.g., see 3GPP RP-213598) to specify CSI reporting enhancements for high / medium UE speeds by leveraging time domain correlation / Doppler domain information to assist DL precoding. In particular, Rel-16 / 17 Type-II codebook refinements should be studied without modifying the spatial and frequency domain basis.

[0047] In RAN1#110 (see, e.g., Notes from RAN1 Chairman, 3GPP TSG RAN WG1#110, Toulouse, France, August 22-26, 2022), the following agreement was reached on a new Type II codebook structure for high / medium UE speeds:

[0048] For Rel-18 Type II codebook refinement for high / medium speed, select one of the following codebook structures:

[0049] Alt2A: Doppler domain basis chosen commonly for all SD / FD bases, e.g.

[0050] oPlease note that as a special case, W d Can be the identity matrix

[0051] Alt2B: Doppler domain basis selected independently for different SD / FD basis

[0052] oPlease note that as a special case, W d Can be the identity matrix

[0053] ●Alt3. Reuse Rel-16 / 17(F)eType-II codebook, which has multiple and single W1 and W f Report.

[0054] There are some challenges. According to the agreement reached in RAN1#110, if the CSI report contains a large number of Alt3 may lead to large CSI overhead because Alt3 corresponds to the case without Doppler domain compression. On the other hand, the two variants of Alt2 (i.e., Alt2A and Alt2B) introduce the matrix W d It provides the possibility of Doppler domain compression. In order to achieve compression in the Doppler domain, the matrix W d One or more selected Doppler domain basis vectors may be included (note that in RAN1, the Doppler domain basis vectors are agreed to be the DFT basis vectors).

[0055] In the agreement reached in RAN1#110, two versions of Alt2 allow the matrix W to be d The possibility of setting W to the identity matrix, in which case there will not be any compression in the Doppler domain. Therefore, both versions of Alt2 also allow d Set to the identity matrix to support Alt3 as a special case.

[0056] Improved systems and methods for CSI reporting are needed. Summary of the invention

[0057] Systems and methods for high-speed channel state information (CSI) reporting using a Type II codebook 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 a channel state information CSI report (e.g., Type II CSI); determining the number of CSI instances signaled 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. Certain embodiments may provide one or more of the following technical advantages. The solutions proposed in the present disclosure allow the network and UE to support the possibility of situations with and without Doppler domain compression under a single Type II CSI reporting framework. Based on signaling received from the network, these solutions allow the UE to determine when to feed back a selected Doppler domain basis in a Type II CSI report (i.e., assuming Doppler domain compression) and when to avoid Doppler domain basis selection in a Type II CSI report.

[0058] Some embodiments of the present disclosure provide solutions to define 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 signaling and UE behavior associated with such Type II CSI reports.

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

[0060] 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 a mechanism for defining a threshold for determining whether to apply CSI compression in the Doppler domain. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure and together with the description serve to explain the principles of the disclosure.

[0062] Figure 1 An example of spatial multiplexing operation is shown;

[0063] Figure 2An example of channel state information reference signal (CSI-RS) resource elements (REs) for 12 antenna ports is shown, where 1 RE per resource block (RB) per port is shown;

[0064] Figure 3 Four different examples with different numbers of CSI instances are shown according to some embodiments of the present disclosure, wherein the gNB requests a user equipment (UE) to feedback CSI for the different numbers of CSI instances;

[0065] Figure 4 A method performed by a UE according to some embodiments of the present disclosure is shown;

[0066] Figure 5 A method performed by a network node according to some embodiments of the present disclosure is shown;

[0067] FIG6 illustrates an example of a communication system according to some embodiments;

[0068] FIG7 illustrates a UE according to some embodiments;

[0069] FIG8 illustrates a network node according to some embodiments;

[0070] 9 is a block diagram of a host according to various aspects described herein, which may be an embodiment of the host of FIG. 6 ;

[0071] FIG. 10 is a block diagram illustrating a virtualized environment in which functions implemented by some embodiments may be virtualized; and

[0072] 11 illustrates a communication diagram of a host communicating with a UE over a partial wireless connection through a network node according to some embodiments. DETAILED DESCRIPTION

[0073] The embodiments set forth below represent information that enables those skilled in the art to practice the embodiments and illustrate the best way to practice the embodiments. After reading the following description in conjunction with the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will recognize the applications of these concepts not specifically described herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.

[0074] What criteria are used to determine whether W d The matrix is ​​set to the identity matrix or W d Whether the matrix should contain the selected Doppler domain basis vectors is still an open question. The related signaling and UE behavior are also open issues that need to be resolved.

[0075] A system and method for high-speed channel state information (CSI) reporting using a Type II codebook is provided. In some embodiments, the method includes 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 the number of CSI instances signaled 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. Certain embodiments may provide one or more of the following technical advantages. The solutions proposed in the present disclosure allow the network and UE to support the possibility of situations with and without Doppler domain compression under a single Type II CSI reporting framework. Based on signaling received from the network, these solutions allow the UE to determine when to feed back a selected Doppler domain basis in a Type II CSI report (i.e., assuming Doppler domain compression) and when to avoid Doppler domain basis selection in a Type II CSI report.

[0076] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. Some embodiments of the present disclosure provide solutions that define criteria used by a UE to determine when to apply Doppler domain compression and when to avoid Doppler domain compression when feeding back a Type II CSI report. The present disclosure also defines signaling and UE behavior associated with such Type II CSI reports.

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

[0078] The present disclosure also covers various signaling alternatives for the gNB to request the number of CSI instances for which the UE calculates CSI, as well as a mechanism for defining a threshold for determining whether to apply CSI compression in the Doppler domain.

[0079] General Examples

[0080] In one embodiment, the gNB sends a signal to the UE to inform the number of CSI instances (denoted as N) for which the gNB requests the UE to feedback CSI. CSI ).exist Figure 3, four different examples with different numbers of CSI instances for which the gNB requests the UE to feedback CSI. The boxes labeled n, n+1, ..., n+9 in this example may be any of: a slot, a subslot (where a subslot consists of a subset of symbols within a slot), or a time unit. In some embodiments, the value of the time unit (e.g., Figure 3 The duration of each frame shown in the example of ) may be configured by the gNB to the UE. In some embodiments, the time unit may be defined as the unit used to calculate the time interval corresponding to N CSI The minimum time interval between any two NZP CSI-RS samples (or resources) in a set of NZP CSI-RS samples for the CSI corresponding to a CSI instance. Figure 3 Each box in the example is referred to as a time unit. However, it should be understood that each such box may instead represent a time slot or sub-time slot.

[0081] exist Figure 3 In example A, 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 N. CSI =4.

[0082] exist Figure 3 In example B, 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 N. CSI =3.

[0083] exist Figure 3 In example C, the UE is requested to calculate the 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 N. CSI =2.

[0084] exist Figure 3 In example D, 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. Therefore, the number of CSI instances for which the UE is requested to calculate CSI is N. CSI =10.

[0085] Although Figure 3The examples in show CSI instances that are evenly spaced, but embodiments of the present disclosure are equally applicable to cases where CSI instances are unevenly spaced. In some embodiments, CSI instances may be unevenly spaced in time units. This may correspond to some TDD deployments where some time slots may be DL time slots for which CSI may be requested, while CSI for UL time slots may not be required. An example may be that for N CSI = 4, you can request CSI for time units n+2, n+3, n+7, and n+8 (instead of Figure 3 The situation shown in example a).

[0086] It should be noted in this disclosure that the CSI The CSI of a CSI instance is reported in a single time slot. For example, when the UE is able to predict the CSI in future time slots, Figure 3 The report in time slot n shown corresponds to N CSI The CSI of each CSI instance.

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

[0088] In one embodiment, the threshold N th This threshold is used to define the UE behavior regarding when to select the Doppler domain basis vectors as W d part of, or when W d The matrix is ​​set to the identity matrix. In some embodiments, when the threshold N th When signaled as a parameter, the threshold may be configured as part of the CSI-ReportConfig IE as defined in 3GPP TS 38.331 V17.1.0 or the CodebookConfig IE as defined in 38.331 V17.1.0.

[0089] If the gNB requests the UE to feedback CSI for the number of time instances N CSI Less than the threshold N th (That is, if N CSI <N th ), the UE assumes that there is no compression in the Doppler domain and transforms the matrix W d Set to the identity matrix. Since Wd is set to the identity matrix, so when the criterion N is satisfied CSI <N th , the UE will not feed back any of the selected Doppler domain basis vectors as part of the CSI report. Alternatively, in this embodiment, the criterion N may be used CSI ≤N th Instead of N CSI <N th (That is, if the number of time instances N CSI Less than or equal to threshold N th , where the gNB requests the UE to feedback the CSI for the time instance, then the UE assumes that there is no compression in the Doppler domain and transforms the matrix W d Set to the identity matrix).

[0090] If the gNB requests the UE to feedback CSI for the number of time instances N CSI Greater than the threshold N th (That is, if N CSI >N th ), the UE assumes that there is compression in the Doppler domain and selects one or more Doppler domain basis vectors, which will be W d In this case, the UE uses index i 1,9,l The Doppler domain basis vectors selected for each layer are fed back in the form of 1,9,l denotes the selected Doppler domain basis vector corresponding to layer l. Alternatively, the UE may use index i 1,9,sdfd,l The selected Doppler domain basis vectors according to the SD / FD pair for each layer are fed back in the form of 1,9,sdfd,l sdfd SD / FD basis pair. The number of Doppler domain basis vectors to be selected may be signaled by the gNB to the UE as a separate higher layer parameter or as a parameter indicating a combination of parameters.

[0091] In one embodiment, whether the UE assumes no compression in the Doppler domain or assumes compression in the Doppler domain is determined by a parameter (or combination of parameters) indicating the number of Doppler domain basis vectors to be selected. If the number of Doppler domain basis vectors to be selected is indicated to be zero, then the UE assumes no compression in the Doppler domain. For this case, the UE sets the matrix W d is set to the identity matrix, and the UE does not feed back any index representing the selected Doppler domain basis vector. 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. For this case, the UE feeds back the selected Doppler domain basis vector represented by one or more indices as part of Type II CSI feedback similar to that described above.

[0092] In an alternative approach, for N CSI The CSI for each time instance is reported as a single PMI value corresponding to the codebook index of i1 and i2, where:

[0093]

[0094] The components of i1 represent the selected beam, the FD basis, the DD basis, the index of the strongest coefficient, and for each layer, the report represents The components of i2 consist of indices pointing to the quantized magnitude and phase of the reported coefficients.

[0095] i 1,1 ,i 1,2 Indicates the selected L spatial beams.

[0096] i 1,5 Indicates the set of FD bases from which the reported basis is selected when the number of PMIs to be reported N3>19.

[0097] i 1,6,l is a combined index indicating the FD basis selected for layer l.

[0098] i 1,7,l Represents a bitmap whose non-zero bits are identified in i for layer l 2,4,l and i 2,5,l Reported in Which coefficients of .

[0099] i 1,8,l It means that for layer l, for υ = 1, The index of the strongest non-zero coefficient reported in , and for v ≥ 2, the index of the strongest spatial beam.

[0100] In an embodiment, i 1,9,l indicates the selected Doppler domain basis for layer l, and i 1,9,l Is the length bits of combination index indicator, where N4 is the length of the Doppler domain basis vector, and M DD,l is the number of Doppler domain basis vectors to be selected.

[0101] In another embodiment, when 0 Doppler basis is always selected, i 1,9,l represents the selected Doppler domain basis for layer l. 1,9,l Is the length A combination index indicator of 1 bit, where N4 is the length of the Doppler domain basis vector, and M DD,l is the number of Doppler domain basis vectors to be selected.

[0102] Used to signal N CSI Example

[0103] In one embodiment, the number of time instances N for which the gNB requests the UE to feedback CSI CSI The N is signaled as part of the CSI-ReportConfig information element (IE). The CSI-ReportConfig IE is specified in 3GPP TS 38.331 V17.1.0. The following shows the N signaled as part of the CSI-ReportConfig IE. CSI In this first example, N CSI It is configured via the parameter numCsiInstances-r18 configured by RRC. Note that since Type II CSI is mainly carried on PUSCH, the parameter numCsiInstances-r18 can be configured when CSI-ReportConfig has a report configuration type (i.e., reportConfigType) set to aperiodic (i.e., CSI reporting is triggered aperiodically on PUSCH) or semiPersistentOnPUSCH (i.e., CSI reporting is semi-persistently activated on PUSCH).

[0104] In the following example, the parameter firstTimeUnitCSI-r18 can also be configured by RRC as part of CSI-ReportConfigIE. The parameter firstTimeUnitCSI-r18 indicates the time interval between N CSI The time unit (or alternatively, time slot or sub-time slot) corresponding to the first CSI instance among the CSI instances. Figure 3 In the example, firstTimeUnitCSI-r18 corresponds to the following:

[0105] ·exist Figure 3 In example A, firstTimeUnitCSI-r18 corresponds to time unit n+2

[0106] ·exist Figure 3 In examples B, C, and D, firstTimeUnitCSI-r18 corresponds to time unit n

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

[0108] In some other embodiments, firstTimeUnitCSI-r18 may be defined relative to the time slot containing the CSI reference resource (i.e., if the CSI reference resource is to be included in time slot n CSI-ref The time unit corresponding to the first CSI instance is n CSI-ref +firstTimeUnitCSI-r18). Alternatively, when the time unit is smaller than the uplink time slot, the time unit corresponding to the first CSI instance can be given by n CSI-ref +X*firstTimeUnitCSI-r18, where X is a predefined value defined in the 3GPP specification. Note that the CSI reference resource here is as defined in clause 5.2.2.5 of 3GPP TS 38.214.

[0109] In the example IE below, the parameter timeUnitStepSize-r18 may also be RRC-configured as part of the CSI-ReportConfig IE. The parameter timeUnitStepSize-r18 indicates the interval between adjacent CSI instances in terms of time units (or alternatively, slots or subslots). Figure 3 In the example, timeUnitStepSize-r18 corresponds to the following:

[0110] ·exist Figure 3 In example A, the value of timeUnitStepSize-r18 is 2

[0111] ·exist Figure 3 In example B, the value of timeUnitStepSize-r18 is 4

[0112] ·exist Figure 3 In example C, the value of timeUnitStepSize-r18 is 5

[0113] ·exist Figure 3 In example D, the value of timeUnitStepSize-r18 is 1

[0114] Alternatively, to indicate timeUnitStepSize-r18, parameter timeUnitOffsetList-r18 may be RRC configured as part of CSI-ReportConfig IE. Parameter timeUnitOffsetList-r18 indicates CSI instances in terms of time unit offsets (or alternatively, slots or subslots). Figure 3 In the example, timeUnitOffsetList-r18 corresponds to the following:

[0115] ·exist Figure 3 In example A, timeUnitOffsetList-r18 has values ​​[2,4,6,8]

[0116] ·exist Figure 3 In example B, timeUnitOffsetList-r18 has values ​​[0,4,8]

[0117] ·exist Figure 3 In example C, timeUnitOffsetList-r18 has values ​​[0,5]

[0118] ·exist Figure 3 In example D, timeUnitOffsetList-r18 has values ​​[0,1,2,3,4,5,6,7,8,9]

[0119] CSI-ReportConfig Information Element

[0120]

[0121]

[0122] In an alternative embodiment, the timeUnitStepSize and the indication of the total number of time units may be signaled to the UE. The number of instances NCSI may then 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.

[0123] In another alternative, in addition to signaling the parameters in the CSI-ReportConfig as shown in the above IE, the parameters may also be signaled as part of the CodebookConfig information element defined in 38.331 v17.1.0.

[0124] In another alternative embodiment, one or more of firstTimeUnitCSI, timeUnitStepSize, and numCsiInstances are signaled via a code point in a DCI field of the DCI. For example, different code points of the DCI field in the DCI may indicate different combinations of firstTimeUnitCSI values, numCsiInstances values, and timeUnitStepSize values, as shown in Table 1.

[0125]

[0126] Table 1. Example showing indication of one or more of firstTimeUnitCSI, timeUnitStepSize, and numCsiInstances in DCI

[0127] Although the example in Table 1 shows that each code point of the DCI field indicates a combination of firstTimeUnitCSI, numCsiInstances, and timeUnitStepSize values, in some alternative embodiments it is possible for each code point to indicate the following subset:

[0128] Each code point indicates only the value of firstTimeUnitCSI

[0129] Each code point simply indicates the value of numCsiInstances

[0130] Each code point simply indicates the value of timeUnitStepSize

[0131] Each code point indicates only the value of firstTimeUnitCSI and the value of numCsiInstances

[0132] Each code point indicates only the value of firstTimeUnitCSI and the value of timeUnitStepSize

[0133] Each code point simply indicates the value of numCsiInstances and the value of timeUnitStepSize

[0134] In the above alternative embodiment, the value of any one of firstTimeUnitCSI, numCsiInstances and timeUnitStepSize that is not indicated to the UE through DCI is indicated to the UE by the network via higher layer configuration (eg, via RRC).

[0135] In some further alternative embodiments, the value of one or more of firstTimeUnitCSI, numCsiInstances and timeUnitStepSize is indicated by MAC CE signaling.

[0136] Figure 4 A method performed by a UE is shown, the method comprising one or more of: determining (step 400) 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 (step 402) the number of CSI instances sent using a signal, wherein the gNB requests the UE to calculate the CSI for the CSI instances; and determining (step 404) whether to apply CSI compression in the Doppler domain based on the number of CSI instances.

[0137] Figure 5 A method performed by a network node is shown, the method comprising one or more of: indicating (step 500) the number of CSI instances for which the network node requests the UE to calculate CSI; and receiving (step 502) CSI with or without CSI compression in the Doppler domain based on the number of CSI instances.

[0138] FIG. 6 shows an example of a communication system 600 according to some embodiments.

[0139] In this example, the communication system 600 includes a telecommunications network 602, which includes an access network 604 (e.g., a radio access network (RAN)) and a core network 606, which includes one or more core network nodes 608. The access network 604 includes one or more access network nodes, such as network nodes 610A and 610B (one or more of which may be generally referred to as network nodes 610), 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 connection of user equipment (UE), such as 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 via one or more wireless connections.

[0140] Example wireless communications over wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transferring information without the use of wires, cables, or other material conductors. In addition, in various embodiments, the 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 over a wired or wireless connection. The communication system 600 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.

[0141] UE 612 may be any of a variety of communication devices, including wireless devices that are arranged, configured and / or operable to communicate wirelessly with network node 610 and other communication devices. Similarly, network node 610 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 612 and / or with other network nodes or devices in telecommunication network 602 to enable and / or provide network access (e.g., wireless network access) and / or perform other functions (e.g., management in telecommunication network 602).

[0142] In the depicted example, the core network 606 connects the network node 610 to one or more hosts (e.g., host 616). These connections can be direct or indirect connections through one or more intermediate networks or devices. In other examples, the network node can be directly coupled to the host. The core network 606 includes one or more core network nodes (e.g., core network node 608), which are composed of hardware and software components. The features of these components can be substantially similar to those described for the UE, network node and / or host, so that their description is generally applicable to the corresponding components of the core network node 608. Example core network nodes include one or more of the following: 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-hiding function (SIDF), a unified data management (UDM), a security edge protection proxy (SEPP), a network open function (NEF) and / or a user plane function (UPF).

[0143] The host 616 may be owned or controlled by a service provider other than the operator or provider of the access network 604 and / or the telecommunications network 602, and may be operated by or on behalf of the service provider. 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 (e.g., retrieval and compilation of data of various environmental conditions detected by multiple UEs), analytical functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0144] In general, the communication system 600 of Figure 6 enables connections between UEs, network nodes, and hosts. In this sense, the communication system 600 can be configured to operate according to predefined rules or procedures, such as specific standards, 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) standards, or any applicable future generation standards (e.g., sixth generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other appropriate wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi and / or any Low Power Wide Area Network (LPWAN) standards, such as LoRa and Sigfox.

[0145] In some examples, telecommunication network 602 is a cellular network implementing 3GPP standardized features. Thus, telecommunication network 602 can support network slicing to provide different logical networks to different devices connected to telecommunication network 602. For example, telecommunication network 602 can provide ultra-reliable low-latency communication (URLLC) services to some UEs, while providing enhanced mobile broadband (eMBB) services to other UEs, and / or provide massive machine type communication (mMTC) / massive Internet of Things (IoT) services to more UEs.

[0146] In some examples, UE 612 is configured to send and / or receive information without direct human interaction. For example, the UE can be designed to transmit information to access network 604 according to a predetermined schedule, when triggered by an internal or external event, or in response to a request from access network 604. In addition, the UE can be configured to operate in a single or multiple radio access technology (RAT) or multi-standard mode. For example, the UE can operate using any one or a combination of WiFi, new radio (NR) and LTE, that is, configured for multi-radio dual connectivity (MR-DC), such as evolved UMTS terrestrial RAN (E-UTRAN) NR-dual connectivity (EN-DC).

[0147] In this example, the hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612C and / or 612D) and a network node (e.g., network node 610B). In some examples, the hub 614 can be a controller, a router, a content source and an analyzer, or any other communication device described herein with respect to the UE. For example, the hub 614 can be a broadband router that enables the UE to access the core network 606. As another example, the hub 614 can be a controller that sends commands or instructions to one or more actuators in the UE. The command or instruction can be received from the UE, the network node 610, or received by an executable code, a script, a process, or other instructions in the hub 614. As another example, the hub 614 can be a data collector that acts as a temporary storage of UE data, and in some embodiments, analysis or other processing of the data can be performed. As another example, the hub 614 can be a content source. For example, for a UE that is a virtual reality (VR) headset, display, speaker, or other media delivery device, the hub 614 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and then the hub 614 provides it to the UE directly, after performing local processing, and / or after adding additional local content. In another example, the hub 614 acts as a proxy server or coordinator for the UE, especially when one or more of the UEs are low-energy IoT devices.

[0148] Hub 614 can have constant / persistent or intermittent connection with network node 610B. Hub 614 can also allow different communication schemes and / or scheduling between hub 614 and UE (e.g., UE 612C and / or 612D) and between hub 614 and core network 606. In other examples, hub 614 is connected to core network 606 and / or one or more UEs via a wired connection. In addition, hub 614 can be configured to be connected to machine-to-machine (M2M) service providers and / or to another UE via a direct connection via access network 604. In some scenarios, UE can establish a wireless connection with network node 610, while still connected via hub 614 via a wired connection or a wireless connection. In some embodiments, hub 614 can be a dedicated hub, that is, a hub whose main function is to route communication from UE to network node 610B and / or from network node 610B to UE. In other embodiments, the hub 614 may be a non-dedicated hub, ie, a device operable to route communications between the UE and the network node 610B, but which is additionally operable as a communications origin and / or endpoint for certain data channels.

[0149] FIG7 shows a UE 700 according to some embodiments. As used herein, UE refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, voice over Internet protocol (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless client equipment (CPEs), vehicle-mounted or vehicle-mounted embedded / integrated wireless devices, etc. Other examples include any UE identified by 3GPP, including narrowband Internet of Things (NB-IoT) UEs, machine type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0150] 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 may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Rather, a UE may represent a device that is intended to be sold to or operated by a human user, but may not be associated with a particular human user, or may not initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but may be associated with or operated for the benefit of a user (e.g., a smart meter).

[0151] UE 700 includes processing circuit 702, which is operably coupled to input / output interface 706, power supply 708, memory 710, communication interface 712 and / or any other components, or any combination thereof, via bus 704. Some UEs may use all or part of the components shown in Figure 7. The degree of integration between components may vary from UE to UE. In addition, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0152] The processing circuit 702 is configured to process instructions and data, and may be configured to implement any sequential state machine that is operable to execute instructions stored in the 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, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) together with appropriate software; or any combination of the above. For example, the processing circuit 702 may include multiple central processing units (CPUs).

[0153] In this example, the input / output interface 706 can 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 speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device can allow a user to capture information into the UE 700. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, direction pads, trackpads, rollers, smart cards, etc. A presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biosensor, etc., or any combination thereof. An output device can use an interface port of the same type as an input device. For example, a universal serial bus (USB) port can be used to provide input devices and output devices.

[0154] In some embodiments, the power supply 708 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery. The power supply 708 may also include a power supply circuit for delivering power from the power supply 708 itself and / or an external power supply to the various components of the UE 700 via an input circuit or interface (e.g., a power cable). The delivered power may be used, for example, to charge the power supply 708. The power supply circuit may perform any formatting, conversion, or other modification on the power from the power supply 708 so that the power is suitable for the various components of the UE 700 being powered.

[0155] The memory 710 may be a memory or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable cartridge, a 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 application, and corresponding data 716. The memory 710 may store any of a variety of operating systems or combinations of operating systems for use by the UE 700.

[0156] The memory 710 may be configured to include a plurality of physical drive units, such as a redundant array of independent disks (RAID), a 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 disk (HD-DVD) optical drive, an internal hard disk drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external micro dual in-line memory module (DIMM), a synchronous dynamic RAM (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identity modules (SIMs), such as a universal SIM (USIM) and / or an Internet Protocol Multimedia Service Identity Module (ISIM)), other memories, or any combination thereof. The UICC may be an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card". The memory 710 may allow the UE 700 to access instructions, applications, etc. stored on a temporary or non-temporary memory medium to offload data or upload data. An article of manufacture (eg, an article of manufacture utilizing a communication system) may be tangibly embodied as or located in memory 710, which may be or include a device-readable storage medium.

[0157] The processing circuit 702 may be configured to communicate with an access network or other network using a communication interface 712. The communication interface 712 may include one or more communication subsystems and may include or may be communicatively coupled to an antenna 722. The communication interface 712 may include one or more transceivers for communication, 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 communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 718 and the 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.

[0158] In the illustrated embodiment, the communication functionality of the communication interface 712 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication (e.g., Bluetooth, NFC), location-based communication (e.g., using a global positioning system (GPS) to determine location), another similar communication functionality, or any combination thereof. Communication may be implemented according to 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 network (SONET), asynchronous transfer mode (ATM), fast user datagram protocol Internet connection (QUIC), hypertext transfer protocol (HTTP), etc.

[0159] Regardless of the sensor type, the UE may provide an output of the data captured by its sensor through its communication interface 712 or via a wireless connection to a network node. The data captured by the UE's sensor may be transmitted to the network node via another UE over a wireless connection. The output may be periodic (e.g., every 15 minutes if it reports a sensed temperature), random (e.g., to balance the load of reports from multiple sensors), in response to a trigger event (e.g., sending an alarm when moisture is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0160] As another example, the UE includes an actuator, motor, or switch associated with a communication interface that is 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 can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0161] When the UE is in the form of an IoT device, it can be a device for one or more application areas, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include or are embedded in the following devices: connected refrigerators or freezers, televisions, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems (such as heat pumps), self-driving cars, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smart watches, fitness trackers, head-mounted displays for augmented reality (AR) or VR, wearable devices for tactile enhancement or sensory enhancement, sprinklers, animal or item tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any type of medical equipment (such as heart rate monitors or teleoperated surgical robots). A UE in the form of an IoT device includes, in addition to other components described in relation to the UE 700 shown in FIG. 7 , circuits and / or software depending on the intended application of the IoT device.

[0162] As another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a 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 device capable of monitoring and / or reporting its operating status or other functions related to its operation.

[0163] 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 integrated into a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE, which is a remote controller that operates the drone. When a user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first UE and / or the second UE may also include more than one of the above functions. For example, the UE may include sensors and actuators, and handle communications for data from the speed sensors and actuators.

[0164] Figure 8 shows a network node 800 according to some embodiments. As used herein, a network node refers to a device capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), base stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0165] A BS may be classified according to the coverage it provides (or in other words, its transmit power level), and therefore, depending on the coverage provided, a BS may be referred to as a femto BS, a pico BS, a micro BS, or a macro BS. 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 radio BS, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such an RRU may or may not be integrated with an antenna as an antenna-integrated radio. The parts of a distributed radio BS may also be referred to as nodes in a distributed antenna system (DAS).

[0166] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment (e.g., MSRBS), network controllers (e.g., radio network controllers (RNC) or BS controllers (BSC)), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., evolved serving mobile positioning center (E-SMLC)) and / or minimization of drive tests (MDT).

[0167] The network node 800 includes a processing circuit 802, a memory 804, a communication interface 806, and a power supply 808. The network node 800 may be composed of multiple physically independent components (e.g., a node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own components. In certain scenarios where the network node 800 includes multiple independent components (e.g., BTS and BSC components), one or more of the independent components may be shared between multiple network nodes. For example, a single RNC may control multiple node Bs. In this case, each unique node B and RNC pair may be considered a single independent network node in some cases. In some embodiments, the network node 800 may be configured to support multiple RATs. In such embodiments, some components may be repeated (e.g., separate memories 804 for different RATs), and some components may be reused (e.g., antennas 810 may be shared by different RATs). The network node 800 may also include various illustrated components for multiple groups of different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies, integrated into the network node 800. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 800.

[0168] The processing circuit 802 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a CPU, a DSP, an ASIC, an FPGA, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic, which may be used alone or in combination with other network node 800 components (e.g., memory 804) to provide network node 800 functionality.

[0169] In some embodiments, processing circuitry 802 includes a system on a chip (SOC). In some embodiments, processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, RF transceiver circuitry 812 and baseband processing circuitry 814 may be located on separate chips (or chipsets), circuit boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, part or all of RF transceiver circuitry 812 and baseband processing circuitry 814 may be located on the same chip or a set of chips, boards, or units.

[0170] The memory 804 may include any form of volatile or non-volatile computer-readable memory, including but not limited to persistent memory, 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 disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device for storing information, data and / or instructions that can be used by the processing circuit 802. The memory 804 may store any suitable instructions, data or information, including computer programs, software, applications, including one or more of the following: logic, rules, codes, 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 any calculations performed by the processing circuit 802 and / or any data received via the communication interface 806. In some embodiments, the processing circuit 802 and the memory 804 are integrated.

[0171] The communication interface 806 is used for wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown, the communication interface 806 includes a port / terminal 816 for, for example, sending data to the network and receiving data from the network via a wired connection. The communication interface 806 also includes a radio front-end circuit 818, which may be coupled to an antenna 810, or may be coupled to a portion of the antenna 810 in certain embodiments. The radio front-end circuit 818 includes a filter 820 and an amplifier 822. The radio front-end circuit 818 may be connected to the antenna 810 and the processing circuit 802. The radio front-end circuit 818 may be configured to adjust the signal transmitted between the antenna 810 and the processing circuit 802. The radio front-end circuit 818 may receive digital data to be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 818 may use a combination of a filter 820 and / or an amplifier 822 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. Then, the radio signal may be transmitted via the antenna 810. Similarly, when receiving data, antenna 810 may collect radio signals, which may then be converted into digital data by radio front end circuit 818. The digital data may be passed to processing circuit 802. In other embodiments, communication interface 806 may include different components and / or different combinations of components.

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

[0173] 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 sending and receiving data and / or signals. In some embodiments, antenna 810 is separate from network node 800 and may be connected to network node 800 via an interface or port.

[0174] The antenna 810, the communication interface 806 and / or the processing circuit 802 may be configured to perform any receiving operation and / or certain acquisition operations performed by the network node 800 described herein. Any information, data and / or signal may be received from a UE, another network node and / or any other network device. Similarly, the antenna 810, the communication interface 806 and / or the processing circuit 802 may be configured to perform any sending operation performed by the network node 800 described herein. Any information, data and / or signal may be sent to a UE, another network node and / or any other network device.

[0175] The power supply 808 provides power to the various components of the network node 800 in a form suitable for the various components (e.g., at the voltage and current levels required by each of the various components). The power supply 808 may also include or be coupled to a power management circuit to provide power to the components of the network node 800 for performing the functions described herein. For example, the network node 800 may be connected to an external power source (e.g., a power grid or a power outlet) via an input circuit or an interface such as a cable, whereby the external power source supplies power to the power circuit of the power supply 808. As a further example, the power supply 808 may include a power source in the form of a battery or a battery pack, which is connected to the power circuit or integrated in the power circuit. If the external power source fails, the battery can provide backup power.

[0176] Embodiments of network node 800 may include additional components in addition to those shown in FIG8 to provide certain aspects of network node functionality, including any functionality described herein and / or any functionality required to support the subject matter described herein. For example, network node 800 may include a user interface device to allow information to be input into network node 800 and to allow information to be output from network node 800. This may allow a user to perform diagnostics, maintenance, repair, and other management functions on network node 800.

[0177] FIG9 is a block diagram of a host 900, which may be an embodiment of the host 616 of FIG6, according to various aspects described herein. As used herein, the host 900 may be or include a combination of various hardware and / or software, including processing resources in a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a server farm. The host 900 may provide one or more services to one or more UEs.

[0178] The host 900 includes a processing circuit 902, which is operably coupled to an input / output interface 906, a network interface 908, a power supply 910, and a memory 912 via a bus 904. Other components may be included in other embodiments. The features of these components may be substantially similar to the features described for the devices in the previous figures (e.g., Figures 7 and 8), so that the description thereof is generally applicable to the corresponding components of the host 900.

[0179] The memory 912 may store one or more computer programs (including one or more host applications 914) and data 916, which may include user data, such as data generated by a 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 components shown. The host application 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 a variety of different categories, types, or implementations of UE (e.g., mobile phones, desktop computers, wearable display systems, and heads-up display systems). The host application 914 may also provide user authentication and license checks, and may periodically report health status, routing, and content availability to a central node (e.g., a device in a core network or on the edge). Thus, the host 900 can select and / or indicate to the UE a different host for an Over-The-Top (OTT) service. The host application 914 can 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.

[0180] Figure 10 is a block diagram showing a virtualized environment 1000, wherein the functions implemented by certain embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage device, and network resources. As used herein, virtualization may be applied to any device or component thereof described herein, and relates to the implementation of at least a portion of functions being implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components performed by one or more virtual machines (VMs), which are implemented in one or more virtual environments 1000 hosted by one or more hardware nodes (e.g., hardware computing devices running as network nodes, UEs, core network nodes, or hosts). In addition, in embodiments where a virtual node does not require a radio connection (e.g., a core network node or host), the node may be fully virtualized.

[0181] Application 1002 (which may also be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment 1000 to implement some features, functions and / or advantages of some embodiments disclosed herein.

[0182] Hardware 1004 includes processing circuitry, memory storing 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. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 1006 (also referred to as virtual machine hypervisors or VM monitors (VMMs)), provide VMs 1008A and 1008B (one or more of which may be collectively referred to as VMs 1008), and / or perform any functions, features, and / or advantages associated with some embodiments described herein. Virtualization layer 1006 may present a virtual operating platform to VM 1008 that looks like networked hardware.

[0183] VM 1008 includes virtual processing, virtual memory, virtual network or interface and virtual storage device, and can be operated by corresponding virtualization layer 1006. Different embodiments of the instance of virtual device 1002 can be implemented on one or more VM 1008, and can be implemented in different ways. Virtualization of hardware is sometimes referred to as network function virtualization (NFV). NFV can be used to integrate many network device types onto industry-standard high-capacity server hardware, physical switches and physical storage, which can be located in data centers and client devices.

[0184] In the context of NFV, a VM 1008 may be a software implementation of a physical machine that runs programs as if they were running on a physical, non-virtualized machine. Each VM 1008 and the portion of the hardware 1004 on which the VM runs (whether dedicated to the VM or shared with other VMs 1008) form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function running in one or more VMs 1008 on top of the hardware 1004 and corresponds to an application 1002.

[0185] Hardware 1004 may be implemented in a standalone network node with general or specific components. Hardware 1004 may implement some functions via virtualization. Alternatively, hardware 1004 may be part of a larger hardware cluster (e.g., in a data center or CPE), where many hardware nodes work together and are managed via management and orchestration 1010, which, among other things, oversees the lifecycle management of application 1002. In some embodiments, hardware 1004 is coupled to one or more radio units, each of which includes 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 conjunction with virtual components to provide radio capabilities to virtual nodes (e.g., RAN or BS). In some embodiments, some signaling may be provided using a control system 1012, which may alternatively be used for communication between hardware nodes and radio units.

[0186] FIG11 shows a communication diagram of a host 1102 communicating with a UE 1106 over a partial wireless connection via a network node 1104 in accordance with some embodiments. According to various embodiments, an example implementation of a UE (e.g., UE 612A of FIG6 and / or UE 700 of FIG7 ), a network node (e.g., network node 610A of FIG6 and / or network node 800 of FIG8 ), and a host (e.g., host 616 of FIG6 and / or host 900 of FIG9 ) discussed in the preceding paragraphs will now be described with reference to FIG11 .

[0187] As with the host 900, embodiments of the host 1102 include hardware, such as a communication interface, a processing circuit, and a memory. The host 1102 also includes software that is stored in or accessible by the host 1102 and can be executed by the processing circuit. The software includes a host application that is operable to provide services to a remote user, such as a UE 1106 connected via an OTT connection 1150 extending between the UE 1106 and the host 1102. In providing services to the remote user, the host application can provide user data transmitted using the OTT connection 1150.

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

[0189] UE 1106 includes hardware and software, the software is stored in UE 1106 or accessible by UE 1106, and can be executed by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "application", which is operable to provide services to human users or non-human users via UE 1106 with the support of host 1102. In host 1102, the executing host application can communicate with the executing client application via an OTT connection 1150 terminated at UE 1106 and host 1102. When providing services to the user, the client application of the UE can receive request data from the host application of the host and provide user data in response to the request data. The OTT connection 1150 can transmit both request data and user data. The client application of the UE can interact with the user to generate user data, which is provided to the host application via the OTT connection 1150.

[0190] The OTT connection 1150 may extend via a connection 1660 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 connection 1660 and the wireless connection 1170 (via which the OTT connection 1150 may be provided) have been drawn abstractly to illustrate communications between the host 1102 and the UE 1106 via the network node 1104, without explicit reference to any intermediate devices and the precise routing of messages via those devices.

[0191] As an example of transmitting data via the OTT connection 1150, in step 1108, the host 1102 provides user data, which can be performed by running a host application. In some embodiments, the user data is associated with a specific human user interacting with the UE 1106. In other embodiments, the user data is associated with the UE 1106 that shares data with the host 1102 without explicit human interaction. In step 1110, the host 1102 initiates a transmission carrying the user data to 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 running on the UE 1106. According to the teachings of the embodiments described in the present disclosure, the transmission may be delivered via the network node 1104. Therefore, in step 1112, according to the teachings of the embodiments described throughout the present disclosure, the network node 1104 transmits the user data carried in the transmission initiated by the host 1102 to the UE 1106. In step 1114 , UE 1106 receives the user data carried in the transmission, which may be performed by a client application running on UE 1106 that is associated with a host application running on host 1102 .

[0192] In some examples, the UE 1106 runs a client application that provides user data to the host 1102. The user data may be provided as a 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 running the client application. In providing the user data, the client application may also take into account user input received from the user via the input / output interface of the UE 1106. Regardless of the specific manner in which the user data is provided, the UE 1106 initiates transmission of the user data to 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 to the host 1102 in accordance with the teachings of the embodiments described in the present disclosure. In step 1122, the host 1102 receives the user data carried in the transmission initiated by the UE 1106.

[0193] One or more of the various embodiments improve the performance of OTT services provided to UE 1106 using OTT connection 1150, where wireless connection 1170 forms the last leg. More specifically, the teachings of these embodiments can improve, for example, data rate, latency, power consumption, etc., thereby providing benefits such as reduced user waiting time, relaxed restrictions on file size, improved content resolution, better responsiveness, extended battery life, etc.

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

[0195] In some examples, a measurement process may be provided for monitoring data rates, delays, and other factors that one or more embodiments improve. There may also be an optional network function for reconfiguring the OTT connection 1150 between the host 1102 and the UE 1106 in response to changes in the measurement results. The measurement process and / or the network function for reconfiguring the OTT connection 1150 may be implemented in the software and hardware of the host 1102 and / or the UE 1106. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 1150 passes; the sensors may participate in the measurement process by providing the values ​​of the monitoring quantities exemplified above or by providing the values ​​of other physical quantities, and the software may calculate or estimate the monitoring quantities based on the values ​​of the other physical quantities. The reconfiguration of the OTT connection 1150 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not require direct changes to the operation of the network node 1104. Such processes and functions are known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which helps the host 1102 measure throughput, propagation time, delay, etc. Measurements may be accomplished by software causing a message (particularly a null or "dummy" message) to be transmitted using the OTT connection 1150 while monitoring propagation time, errors, etc.

[0196] Although the computing devices (e.g., UE, network node, host) described herein may include the hardware component combinations shown, other embodiments may include computing devices with different component combinations. It will be understood that these computing devices may include any suitable hardware and / or software combination required to perform the tasks, features, functions and methods disclosed herein. The determination, calculation, acquisition or similar operations described herein may be performed by a processing circuit, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination based on the result of the processing. In addition, although the components are depicted as being located within a larger box or nested within multiple boxes, in practice, a computing device may include multiple different physical components constituting a single illustrated component, and functions may be divided between separate components. For example, a communication interface may be configured to include any component described herein, and / or the functions of a component may be divided between a processing circuit and a communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0197] In some embodiments, some or all of the functionality described herein may be provided by a processing circuit that executes instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-temporary computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by a 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 specific embodiments, the processing circuit may be configured to perform the described functionality, regardless of whether instructions stored on a non-temporary computer-readable storage medium are executed. The benefits provided by such functionality are not limited to processing circuits alone or to other components of a computing device, but may generally be enjoyed by the entire computing device and / or end users and wireless networks.

[0198] Embodiment 1: A method performed by a user equipment UE, the method comprising one or more of the following: a. determining (400) 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); b. determining (402) the number of CSI instances signaled by the gNB requesting the UE to calculate CSI for it; and c. determining (404) whether to apply CSI compression in the Doppler domain based on the number of CSI instances.

[0199] Embodiment 2: The method of the previous embodiment, wherein: when CSI compression needs to be applied, the selected Doppler domain basis vector is fed back.

[0200] Embodiment 3: The method of any of the preceding embodiments, wherein: the selected Doppler domain basis vector is part of a Type II CSI feedback.

[0201] Embodiment 4: The method of any of the preceding embodiments, wherein: the selected Doppler domain basis vectors are indicated via indices.

[0202] Embodiment 5: The method of any of the preceding embodiments, wherein: when CSI compression is not applied, the UE does not select any Doppler domain basis vector and does not need to feed back any Doppler domain basis vector.

[0203] Embodiment 6: The method of any of the preceding embodiments, wherein: no index representing the Doppler domain basis vector needs to be fed back.

[0204] Embodiment 7: The method of any of the preceding embodiments, wherein: determining the number of CSI instances signaled by the gNB for which the UE is requested to feedback CSI comprises: receiving the number of CSI instances (denoted as N CSI ).

[0205] Embodiment 8: The method of any of the preceding embodiments, wherein: the value of the time unit is configured by the gNB to the UE.

[0206] Embodiment 9: The method of any of the above embodiments, wherein: the time unit is used to calculate the time unit corresponding to N CSI The minimum time interval between any two NZP CSI-RS samples (or resources) in a set of non-zero power NZP CSI-RS samples of the CSI corresponding to a CSI instance.

[0207] Embodiment 10: The method of any of the preceding embodiments, wherein: the gNB requests the UE to feedback the number of time instances of CSI for which N CSI is explicitly signaled via explicit parameters.

[0208] Embodiment 11: The method of any of the preceding embodiments, wherein: the gNB requests the UE to feedback the number of time instances of CSI for which N CSI is implicitly signaled via a combination of one or more other parameters.

[0209] Embodiment 12: The method of any of the above embodiments, wherein: the threshold value N th It is signaled to the UE or pre-specified in the specification.

[0210] Embodiment 13: The method of any of the preceding embodiments, wherein: the threshold is used to define when to select the Doppler domain basis vector as W with respect to the following UE behavior: d part of, or when W d The matrix is ​​set to the identity matrix.

[0211] Embodiment 14: The method of any of the above embodiments, wherein: when the threshold N th When signaled as a parameter, this threshold is configured as part of the CSI-ReportConfig IE or CodebookConfig IE.

[0212] Embodiment 15: The method of any of the preceding embodiments, wherein: if the gNB requests the UE to feedback the number of time instances of CSI for which N CSI Less than the threshold N th (That is, if N CSI <N th ), the UE assumes that there is no compression in the Doppler domain and / or converts the matrix W d Set to the identity matrix.

[0213] Embodiment 16: The method of any of the preceding embodiments, wherein: if the gNB requests the UE to feedback the number of time instances of CSI for which N CSI Less than or equal to threshold N th (That is, if N CSI ≤N th), the UE assumes that there is no compression in the Doppler domain and / or converts the matrix W d Set to the identity matrix.

[0214] Embodiment 17: The method of any of the preceding embodiments, wherein: if the gNB requests the UE to feedback the number of time instances of CSI for which N CSI Greater than the threshold N th (That is, if N CSI >N th ), the UE assumes that there is compression in the Doppler domain and / or selects W d The columns of the matrix are one or more Doppler domain basis vectors.

[0215] Embodiment 18: The method of any of the above embodiments further comprises: using index i 1,9,l The Doppler domain basis vectors selected for each layer are fed back in the form of 1,9,l represents the selected Doppler domain basis vector corresponding to the lth layer.

[0216] Embodiment 19: The method of any of the above embodiments further comprises: using index i 1,9,sdfd,l The selected Doppler domain basis vectors according to the SD / FD pair for each layer are fed back in the form of 1,9,sdfd,l represents the selected Doppler domain basis vector corresponding to the lth layer and the sdfdth SD / FD basis pair.

[0217] Embodiment 20: A method according to any of the preceding embodiments, wherein: the number of Doppler domain basis vectors to be selected is signaled by the gNB to the UE as an independent high-level parameter or as a parameter indicating a combination of parameters.

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

[0219] Embodiment 22: The method of any of the preceding embodiments, wherein: if the number of Doppler domain basis vectors to be selected is indicated to be zero, the UE assumes that there is no compression in the Doppler domain.

[0220] Embodiment 23: The method of any of the preceding embodiments, 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.

[0221] Embodiment 24: The method of any of the preceding embodiments, wherein: for N CSI The CSI for each time instance is reported as a single PMI value.

[0222] Embodiment 25: The method of any of the preceding embodiments, wherein: the gNB requests the UE to feedback the number of time instances N for which the UE feeds back CSI CSI It is signaled as part of the CSI-ReportConfig IE.

[0223] Embodiment 26: The method of any of the preceding embodiments, wherein: N CSI It is configured via the RRC configuration parameter numCsiInstances-r18.

[0224] Embodiment 27: The method of any of the preceding embodiments, wherein: the parameter firstTimeUnitCSI-r18 is configured by RRC as part of the CSI-ReportConfig IE, and the parameter firstTimeUnitCSI-r18 indicates the time interval between the N CSI The time unit (or alternatively, time slot or sub-time slot) corresponding to the first CSI instance among the CSI instances.

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

[0226] Embodiment 29: The method of any of the preceding embodiments, wherein: firstTimeUnitCSI-r18 is defined relative to the time slot containing the CSI reference resource (i.e., if the CSI reference resource is to be CSI-ref The time unit corresponding to the first CSI instance is n CSI-ref +firstTimeUnitCSI-r18).

[0227] Embodiment 30: The method of any of the preceding embodiments further includes: receiving a signal indicating a timeUnitStepSize and a total number of time units.

[0228] Embodiment 31: The method of any of the preceding embodiments, wherein: the number of instances N CSI Can be determined as floor(total number of time units / timeUnitStepSize).

[0229] Embodiment 32: The method of any of the preceding embodiments, wherein: any of the above parameters is signaled as part of the CodebookConfig IE.

[0230] Embodiment 33: The method of any of the preceding embodiments, wherein: one or more of firstTimeUnitCSI, timeUnitStepSize, and numCsiInstances are signaled via a code point in a DCI field of the DCI.

[0231] Embodiment 34: The method of any of the preceding embodiments, wherein: different code points of the DCI field in the DCI may indicate different combinations of firstTimeUnitCSI values, numCsiInstances values, and timeUnitStepSize values.

[0232] Embodiment 35: The method of any of the preceding embodiments, wherein: any one of the values ​​of firstTimeUnitCSI, numCsiInstances and timeUnitStepSize that is not indicated to the UE via DCI is indicated to the UE by the network via high-level configuration (e.g., via RRC).

[0233] Embodiment 36: The method of any of the preceding embodiments, wherein: the value of one or more of firstTimeUnitCSI, numCsiInstances and timeUnitStepSize is indicated through MAC CE signaling.

[0234] Embodiment 37: The method of any of the preceding embodiments further includes: providing user data; and forwarding the user data to the host via transmission to the network node.

[0235] Group B Embodiment

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

[0237] Embodiment 39: The method of the preceding embodiment includes any of the features of the embodiments in Group A.

[0238] Embodiment 40: The method of any of the foregoing embodiments further includes: obtaining user data; and forwarding the user data to a host or a user device.

[0239] Group C Example

[0240] Embodiment 41: A user device, comprising: a processing circuit configured to perform any step in Group A embodiments; and a power supply circuit configured to supply power to the processing circuit.

[0241] Embodiment 42: A network node, comprising: a processing circuit configured to perform any step in Group B embodiments; and a power supply circuit configured to supply power to the processing circuit.

[0242] Embodiment 43: A user equipment (UE), the UE comprising: an antenna configured to send and receive wireless signals; a radio front-end circuit connected to the antenna and a processing circuit and configured to adjust signals transmitted between the antenna and the processing circuit; a processing circuit configured to perform any step in Group A embodiments; an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing 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 supply power to the UE.

[0243] Embodiment 44: A host configured to operate in a communication system to provide an over-the-top (OTT) service, 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), wherein the UE comprises a communication interface and a processing circuit, and the communication interface and processing circuit of the UE are configured to perform any step in the embodiments of Group A to receive user data from the host.

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

[0245] Embodiment 46: The host of the first two embodiments, wherein the processing circuit of the host is configured to execute a host application to provide user data; and the host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0246] Embodiment 47: A method implemented by a host operating in a communication system that also includes a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission carrying the user data to the UE via a cellular network including the network node, wherein the UE performs any operation in the embodiments of Group A to receive the user data from the host.

[0247] Embodiment 48: The method of the previous embodiment further includes: at a host, running a host application associated with a client application running on the UE to receive user data from the UE.

[0248] Embodiment 49: The method according to the previous embodiment further includes: at the host, sending input data to the client application running on the UE, wherein the input data is provided by running the host application, wherein user data is provided by the client application in response to the input data from the host application.

[0249] Embodiment 49: The method of the previous embodiment further includes: at the host, sending input data to the client application running on the UE, wherein the input data is provided by running the host application, wherein user data is provided by the client application in response to the input data from the host application.

[0250] Embodiment 50: A host configured to operate in a communication system to provide 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), wherein the UE comprises a communication interface and a processing circuit, and the communication interface and processing circuit of the UE are configured to perform any steps of any Group A embodiments to transmit the user data to the host.

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

[0252] Embodiment 52: The host of the first two embodiments, wherein: the processing circuit of the host is configured to run a host application to provide user data; and the host application is configured to interact with a client application running on the UE, and the client application is associated with the host application.

[0253] Embodiment 53: A method implemented by a host, the host being configured to operate in a communication system that also includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted by the UE to the host via the network node, wherein the UE performs any step in the embodiments of Group A to transmit the user data to the host.

[0254] Embodiment 54: The method of the previous embodiment further includes: at a host, running a host application associated with a client application running on the UE to receive user data from the UE.

[0255] Embodiment 55: The method of the previous embodiment further includes: at the host, transmitting the input data to the client application running on the UE, providing the input data by running the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0256] Embodiment 56: A host is configured to operate in a communication system to provide 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 network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and a processing circuit, the processing circuit of the network node being configured to perform any operation of any Group B embodiment to transmit user data from the host to the UE.

[0257] Embodiment 57: The host of the preceding embodiment, wherein: the processing circuit of the host is configured to run a host application that provides user data; and the UE includes a processing circuit configured to run a client application associated with the host application to receive a transmission of user data from the host.

[0258] Embodiment 58: A method implemented in a host, the host being configured to operate in a communication system that also includes a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission carrying the user data to the UE via a cellular network including the network node, wherein the network node performs any operation of any Group B embodiment to transmit the user data from the host to the UE.

[0259] Embodiment 59: The method of the previous embodiment further includes sending, at the network node, user data provided by the host for the UE.

[0260] Embodiment 60: The method of any of the first two embodiments, wherein the user data is provided at the host by running a host application that interacts with a client application running on the UE, the client application being associated with the host application.

[0261] Embodiment 61: A communication system configured to provide an over-the-top service, the communication system comprising: a host, the host comprising: a processing circuit configured to provide user data to a user equipment (UE), the user data being associated with the over-the-top service; 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 communication interface and a processing circuit, the processing circuit of the network node being configured to perform any operation in the embodiments of Group B to transmit the user data from the host to the UE.

[0262] Embodiment 62: The communication system of the previous embodiment further includes: a network node; and / or a user equipment.

[0263] Embodiment 63: A host configured to operate in a communication system to provide an over-the-top (OTT) service, 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 being configured to perform any operation of the Group B embodiments to receive user data for the host from a user equipment (UE).

[0264] Embodiment 64: The host in the first two embodiments, wherein the processing circuit of the host is configured to run a host application to provide user data; and the host application is configured to interact with a client application running on the UE, and the client application is associated with the host application.

[0265] Embodiment 65: The host of any one of the first two embodiments, wherein initiating reception of user data includes requesting user data.

[0266] Embodiment 66: A method implemented by a host configured to operate in a communication system that also includes a network node and a user equipment (UE), the method comprising: at the host, initiating reception of user data from the UE, the user data originating from a transmission received by the network node from the UE, wherein the network node performs any steps of any Group B embodiments to receive user data for the host from the UE.

[0267] Embodiment 67: The method of the previous embodiment further includes: at the network node, transmitting the received user data to the host.

[0268] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between abbreviations, the above given method of using the abbreviation shall take precedence. If listed multiple times below, the first listed abbreviation shall take precedence over any subsequent listed abbreviations.

[0269] 3GPP Third Generation Partnership Project

[0270] 5G fifth generation

[0271] 5GC Fifth Generation Core

[0272] 5GS Fifth Generation System

[0273] AF application function

[0274] AMF access and mobility functions

[0275] AN Access Network

[0276] AP Access Point

[0277] ASIC Application-Specific Integrated Circuit

[0278] AUSF authentication server function

[0279] CE Control Elements

[0280] CPU Central Processing Unit

[0281] CSI Channel State Information

[0282] CSI-RS Channel State Information Reference Signal

[0283] DCI Downlink Control Information

[0284] DN Data Network

[0285] DSP Digital Signal Processor

[0286] eNB Enhanced or evolved Node B

[0287] EPS Evolved Packet System

[0288] E-UTRA Evolved Universal Terrestrial Radio Access FPGA Field Programmable Gate Array

[0289] gNB New Radio Base Station

[0290] gNB-DU New Radio Base Station Distributed Unit HSS Home Subscriber Server

[0291] IE Information Element

[0292] IoT

[0293] IP Internet Protocol

[0294] LTE Long Term Evolution

[0295] MAC Media Access Control

[0296] MME Mobility Management Entity

[0297] MTC Machine Type Communication

[0298] NEF network open function

[0299] NF Network Function

[0300] NR New Radio

[0301] NRF Network Function Repository Function

[0302] NSSF network slice selection function

[0303] NZP Non Zero Power

[0304] OTT (Over-the-Top)

[0305] PC Personal Computer

[0306] PCF policy control function

[0307] P-GW Packet Data Network Gateway

[0308] PMI Precoder Matrix Indicator

[0309] QoS Quality of Service

[0310] RAM Random Access Memory

[0311] RAN Radio Access Network

[0312] ROM Read Only Memory

[0313] RRC Radio Resource Control

[0314] RRH Remote Radio Head

[0315] RTT Round Trip Time

[0316] SCEF service capability exposure function

[0317] SMF session management function

[0318] UDM unified data management

[0319] UE User Equipment

[0320] UPF User Plane Function

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

Claims

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

2. The method according to claim 1, wherein: When CSI compression needs to be applied, the selected Doppler domain basis vectors are fed back.

3. The method according to any one of claims 1 to 2, wherein: The selected Doppler domain basis vectors are part of the Type II CSI feedback.

4. The method according to any one of claims 1 to 3, wherein: The selected Doppler domain basis vectors are indicated via indices.

5. The method according to any one of claims 1 to 4, wherein: When CSI compression is not applied, the UE feeds back a Type II CSI report without feeding back any Doppler domain basis vectors.

6. The method according to any one of claims 1 to 5, wherein: Determining the number of CSI instances to be signaled includes: receiving a number of CSI instances (denoted as N) for which the network node requests the UE to feedback CSI in a single CSI report. CSI ).

7. The method according to any one of claims 1 to 6, wherein: The value of the time unit is configured by the network node to the UE.

8. The method according to any one of claims 1 to 7, wherein: The time unit is used to calculate the CSI The minimum time interval between any two NZP CSI-RS samples in a set of non-zero power NZP CSI-RS samples of the CSI corresponding to a CSI instance.

9. The method according to any one of claims 1 to 8, wherein: The number N of time instances for which the network node requests the UE to feedback CSI CSI is explicitly signaled via explicit parameters.

10. The method according to any one of claims 1 to 9, wherein: The number N of time instances for which the network node requests the UE to feedback CSI CSI is implicitly signaled via a combination of one or more other parameters.

11. The method according to any one of claims 1 to 10, wherein: Threshold N th Pre-specified in the specification.

12. The method according to any one of claims 1 to 11, wherein: The threshold is used to define the UE behavior regarding when to select Doppler domain basis vectors as part of Type II CSI feedback or when to feed back Type II CSI reports without feeding back any Doppler domain basis vectors.

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

14. The method according to any one of claims 1 to 13, wherein: If the network node requests the UE to feedback CSI for a number of time instances N CSI Less than the threshold N th , the UE assumes that there is no compression in the Doppler domain and / or does not feed back any Doppler domain basis vectors as part of Type II CSI reporting.

15. The method according to any one of claims 1 to 14, wherein: If the network node requests the UE to feedback CSI for a number of time instances N CSI Less than or equal to threshold N th , the UE assumes that there is no compression in the Doppler domain and / or does not feed back any Doppler domain basis vectors as part of Type II CSI reporting.

16. The method according to any one of claims 1 to 15, wherein: If the network node requests the UE to feedback CSI for a number of time instances N CSI Greater than the threshold N th , 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. The method according to any one of claims 1 to 16, further comprising: Using index i 1,9,l The Doppler domain basis vectors selected for each layer are fed back in the form of 1,9,l represents the selected Doppler domain basis vector corresponding to the lth layer.

18. The method according to any one of claims 1 to 17, wherein: The number of selected Doppler domain basis vectors is signaled by the network node to the UE as an independent higher layer parameter or as a parameter indicating a combination of parameters.

19. The method according to any one of claims 1 to 18, wherein: For N CSI The CSI for each time instance is reported as a single precoder matrix indicator (PMI) value.

20. The method according to any one of claims 1 to 19, wherein: The number N of time instances for which the network node requests the UE to feedback CSI CSI It is signaled as part of the CSI-ReportConfig IE.

21. The method according to any one of claims 1 to 20, wherein: N CSI It is configured via the parameter numCsiInstances-r18 configured via the Radio Resource Control (RRC).

22. The method according to any one of claims 1 to 21, wherein: The parameter firstTimeUnitCSI-r18 is configured by RRC as part of the CSI-ReportConfig information element IE. The parameter firstTimeUnitCSI-r18 indicates the time corresponding to N CSI The time unit of the first CSI instance among the CSI instances.

23. The method according to any one of claims 1 to 22, wherein: firstTimeUnitCSI-r18 is defined relative to the time slot in which the CSI is to be reported.

24. The method according to any one of claims 1 to 23, wherein: firstTimeUnitCSI-r18 is defined relative to the time slot containing the CSI reference resource.

25. The method according to any one of claims 1 to 24, further comprising: A signal is received having an indication of the timeUnitStepSize and the total number of time units.

26. The method according to any one of claims 1 to 25, wherein: The number of instances N CSI Can be determined as floor(total number of time units / timeUnitStepSize).

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

28. The method according to any one of claims 1 to 26, wherein: One or more of firstTimeUnitCSI, timeUnitStepSize and numCsiInstances are signaled via a code point in a DCI field of the downlink control information DCI.

29. The method according to any one of claims 1 to 28, wherein: Different code points of the DCI field in the DCI can indicate different combinations of firstTimeUnitCSI value, numCsiInstances value, and timeUnitStepSize value.

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

31. The method according to any one of claims 1 to 29, wherein: The value of one or more of firstTimeUnitCSI, numCsiInstances and timeUnitStepSize is indicated through medium access control MAC control element CE signaling.

32. A method performed by a network node, the method comprising: indicating (500) the number of CSI instances for which the network node requests the user equipment UE to calculate channel state information CSI, wherein each CSI instance corresponds to the CSI for the duration of the time unit; and Based on the number of CSI instances, CSI is received (502) with or without CSI compression in the Doppler domain.

33. The method of claim 32, wherein: When CSI compression needs to be applied, the selected Doppler domain basis vectors are received.

34. The method according to any one of claims 32-33, wherein: The selected Doppler domain basis vectors are part of the Type II CSI feedback.

35. The method according to any one of claims 32 to 34, wherein: The selected Doppler domain basis vectors are indicated via indices.

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

37. The method according to any one of claims 32 to 36, wherein: Determining the number of CSI instances to be signaled includes: sending a number of CSI instances (denoted as N) for which the network node requests the UE to feedback CSI within a single CSI report. CSI ).

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

39. The method according to any one of claims 32 to 38, wherein: The time unit is used to calculate the CSI The minimum time interval between any two NZP CSI-RS samples in a set of non-zero power NZP CSI-RS samples of the CSI corresponding to a CSI instance.

40. The method according to any one of claims 32 to 39, wherein: The number N of time instances for which the network node requests the UE to feedback CSI CSI is explicitly signaled via explicit parameters.

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

42. The method according to any one of claims 32 to 41, wherein: Threshold N th Pre-specified in the specification.

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

44. The method according to any one of claims 32-43, further comprising: The length of the transmission is A combination index indicator of 1 bit, where N4 is the length of the Doppler domain basis vector, and M DD,l is the number of Doppler domain basis vectors to be selected.

45. The method according to any one of claims 32 to 44, wherein: If the network node requests the UE to feedback CSI for a number of time instances N CSI Less than the threshold N th , the UE assumes that there is no compression in the Doppler domain and / or does not feed back any Doppler domain basis vectors as part of Type II CSI reporting.

46. ​​The method of any one of claims 32-45, wherein: If the network node requests the UE to feedback CSI for a number of time instances N CSI Less than or equal to threshold N th , the UE assumes that there is no compression in the Doppler domain and / or does not feed back any Doppler domain basis vectors as part of Type II CSI reporting.

47. The method of any one of claims 32-46, wherein: If the network node requests the UE to feedback CSI for a number of time instances N CSI Greater than the threshold N th , 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. The method according to any one of claims 32-47, further comprising: Receive using index i 1,9,l The Doppler domain basis vectors selected for each layer are in the form of 1,9,l represents the selected Doppler domain basis vector corresponding to the lth layer.

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

50. The method of any one of claims 32-49, wherein: For N CSI The CSI for each time instance is reported as a single PMI value.

51. The method of any one of claims 32-50, wherein: The number N of time instances for which the network node requests the UE to feedback CSI CSI It is signaled as part of the CSI-ReportConfig IE.

52. The method of any one of claims 32-51, wherein: N CSI It is configured via the RRC configuration parameter numCsiInstances-r18.

53. The method of any one of claims 32-52, wherein: The parameter firstTimeUnitCSI-r18 is configured by RRC as part of the CSI-ReportConfig information element IE. The parameter firstTimeUnitCSI-r18 indicates the time corresponding to N CSI The time unit of the first CSI instance among the CSI instances.

54. The method of any one of claims 32-53, wherein: firstTimeUnitCSI-r18 is defined relative to the time slot in which the CSI is to be reported.

55. The method of any one of claims 32-54, wherein: firstTimeUnitCSI-r18 is defined relative to the time slot containing the CSI reference resource.

56. The method according to any one of claims 32-55, further comprising: A signal is received having an indication of the timeUnitStepSize and the total number of time units.

57. The method of any one of claims 32-56, wherein: The number of instances N CSI Can be determined as floor(total number of time units / timeUnitStepSize).

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

59. The method of any one of claims 32-58, wherein: One or more of firstTimeUnitCSI, timeUnitStepSize, and numCsiInstances are signaled via a code point in a DCI field of the DCI.

60. The method of any one of claims 32-59, wherein: Different code points of the DCI field in the DCI can indicate different combinations of firstTimeUnitCSI value, numCsiInstances value, and timeUnitStepSize value.

61. The method of any one of claims 32-60, wherein: Any value of firstTimeUnitCSI, numCsiInstances and timeUnitStepSize that is not indicated to the UE through DCI is indicated to the UE by the network via high-layer configuration.

62. The method of any one of claims 32-61, wherein: The value of one or more of firstTimeUnitCSI, numCsiInstances and timeUnitStepSize is indicated through MAC CE signaling.

63. A user equipment (700), comprising a processing circuit (702) and a memory (710), the memory (710) storing instructions, the instructions causing the UE (700) to: determining a number of signaled CSI instances for which the network node requests the UE to calculate channel state information CSI, wherein Each CSI instance corresponds to CSI for the duration of a time unit; as well as Based on the number of CSI instances, it is determined whether to apply CSI compression in the Doppler domain.

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

65. A network node (800) comprising a processing circuit (802) and a memory (804), the memory (804) storing instructions, the instructions causing the network node (800) to: Instructing the network node to request the user equipment UE to calculate the number of CSI instances for which the channel state information CSI is calculated, wherein: Each CSI instance corresponds to CSI for the duration of a time unit; as well as Based on the number of CSI instances, CSI is received with or without CSI compression in the Doppler domain.

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

67. A computer readable medium storing instructions which, 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. A computer readable medium storing instructions which, when executed on at least one processor, cause the at least one processor to perform the method of any one of claims 32-62.

Images