Channel status information omitted for Type II channel status information.

Abstract

A method, network node, and wireless device for CSI omission for Type-II channel state information (CSI) are disclosed. According to one aspect, the method in the network node includes receiving an indication of CSI reporting capability from a wireless device (WD). The method includes configuring the WD to report frequency domain (FD) basis vector information in one of CSI report group 1 and CSI report group 0 based at least in part on the indicated CSI reporting capability.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more particularly to channel state information (CSI) omission for Type II CSI.

Background Art

[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) has developed and is developing standards for 4th generation (4G) (also known as Long Term Evolution (LTE)) and 5th generation (5G) (also known as New Radio (NR)) wireless communication systems. Such systems have functions such as broadband communication between network nodes such as base stations and mobile wireless devices (WDs), and communication between network nodes and between WDs, and 6th generation (6G) wireless communication systems are also under development.

[0003] A wireless communication system by 3GPP (registered trademark) may include one or more of the following channels: · Physical Downlink Control Channel (PDCCH) · Physical Uplink Control Channel (PUCCH) · Physical Downlink Shared Channel (PDSCH) · Physical Uplink Shared Channel (PUSCH) · Physical Broadcast Channel (PBCH) and · Physical Random Access Channel (PRACH). <0​​​​​​​​The NR standard is currently evolving with enhanced MIMO support. Core components in NR include support for MIMO antenna arrangements and MIMO-related technologies such as spatial multiplexing. The spatial multiplexing mode aims for high data rates in good channel conditions. An explanation of the spatial multiplexing operation is provided in the example of FIG. 1.

[0006] As shown in the figure, the symbol vector s is N T of xr Precoder multiplied by the matrix W, and this information functions to distribute the transmission energy to a subspace of the N T (corresponding to N antenna ports) dimensional vector space. The precoder matrix is typically selected from a codebook of possible precoder matrices and is typically indicated by a precoder matrix indicator (PMI) that specifies a unique precoder matrix within 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 because multiple symbols can be transmitted simultaneously through the same time / frequency resource element (TFRE). The number of symbols r is typically adapted to fit the current channel characteristics. NR uses orthogonal frequency division multiplexing (OFDM) in the downlink (and DFT-precoded OFDM in the uplink for rank-1 transmission). Thus, for a certain TFRE on subcarrier n (or alternatively the number of data TFREs n), the received N T x vector y R is modeled as follows: n Here, e TIFF0007848312000001.tif1055 is the noise / interference vector obtained as a realization of a random process. The precoder W can be a wideband precoder that is constant with respect to frequency or a precoder with frequency selectivity. The precoder matrix W is often the MIMO channel matrix H of N n xN R xN T and n the nThis is selected to match the characteristics of the channel, resulting in so-called channel-dependent precoding. This is also commonly called closed-loop precoding and essentially attempts to concentrate the transmitted energy in a strong subspace in the sense that the majority of the transmitted energy is transferred to the WD.

[0007] In closed-loop precoding for NR downlinks, the WD sends a recommendation to the gNB (Network Node) for the appropriate precoder to use, based on channel measurements in the downlink. The network node can configure the WD to provide feedback according to CSI-ReportConfig and transmit a Channel State Information Reference Signal (CSI-RS). The network node can also configure the WD to use the CSI-RS measurements to feed back the recommended precoder matrix that the WD selects from the codebook. A single precoder (wideband precoder) that is assumed to cover a wide bandwidth can be fed back. It may also be beneficial to match the channel frequency variation and instead feed back one frequency-selective precoder report per subband, e.g., several precoders. This is an example of a more common case of Channel State Information (CSI) feedback, which also includes feeding back information other than the recommended precoder to assist the network node in subsequent transmissions to the WD. Such other information may include Channel Quality Indicator (CQI) and Transmit Rank Indicator (RI). In NR, CSI feedback can be broadband, with one CSI reported for the entire channel bandwidth, or frequency-selective, with one CSI reported for each subband, defined as the number of consecutive resource blocks ranging from 4 to 32 PRBS depending on the bandwidth portion (BWP) size.

[0008] Upon receiving CSI feedback from the WD, the network node determines the transmit parameters it wishes to use for transmission to the WD, including the precoding matrix, transmit rank, and modulation and coding scheme (MCS). These transmit parameters may differ from the recommendations made by the WD. The transmit rank, and therefore the number of spatial multiplexing layers, is reflected in the number of columns in the precoder W. For efficient performance, it is important that a transmit rank matching the channel characteristics is selected.

[0009] 2D antenna array Some radios use a two-dimensional antenna array. Such an antenna array has a horizontal dimension of N h The number of rows of antennas corresponding to the vertical dimension N v The number of antenna rows corresponding to each, and different polarizations N p The total number of antennas can be described (partially) by the number of corresponding dimensions. Therefore, the total number of antennas is N=N h N v N p The concept of an antenna is non-restrictive in the sense that it can refer to any virtualization (e.g., linear mapping) of physical antenna elements. For example, a pair of physical sub-elements can be supplied with the same signal and therefore share the same virtualized antenna port.

[0010] Figure 2 shows an example of a 4x4 array with dual-polarization antenna elements.

[0011] Precoding can be interpreted as multiplying the signal before transmission using different beamforming weights for each antenna. A typical approach is to match the precoder to the antenna form factor, i.e., when designing the precoder codebook, N h ,N v and N p This should be taken into consideration.

[0012] Channel Status Information Reference Signal (CSI-RS) For CSI measurement and feedback, CSI-RS is defined. CSI-RS is transmitted on each antenna port and used by WD to measure the downlink channel between each transmitting antenna port and each receiving antenna port. The transmitting antenna ports are also called CSI-RS ports. The number of antenna ports supported by NR is {1, 2, 4, 8, 12, 16, 24, 32}. By measuring the received CSI-RS, WD can estimate the channel that the CSI-RS is traversing, including the radio propagation channel and antenna gain. CSI-RS for the above purposes is also called non-zero power (NZP) CSI-RS.

[0013] CSI-RS can be configured to be transmitted within slots and within specific resource elements (REs) within specific slots. Figure 3 shows an example of CSI-RS REs for 12 antenna ports, with one RE per resource block (RB) per port. Interference measurement resources (IMRs) are also defined for WDs in NRs to measure interference. An IMR resource consists of four REs, either four adjacent REs at frequency within the same OFDM symbol, or 2x2 adjacent REs at both time and frequency within a slot. By measuring both channel interference based on non-zero power (NZP) CSI-RS and interference based on IMRs, WDs can estimate effective channel and noise plus interference to determine the CSI, i.e., rank, precoding matrix, and channel quality.

[0014] Furthermore, WD in NR can be configured to measure interference based on one or more NZP CSI-RS resources.

[0015] CSI framework in NR In NR, the WD can be configured with multiple CSI report configurations and multiple CSI-RS resource configurations. Each resource configuration can contain multiple resource sets, and each resource set can contain up to eight CSI-RS resources. For each CSI report configuration, the WD provides CSI reports as feedback.

[0016] Each CSI report configuration may include at least the following information:

[0017] • CSI-RS resource set for channel measurement • IMR resource set for interferometry, Optionally, CSI-RS resource set for interference measurement. • Time-domain behavior, i.e., periodic, semi-permanent, or aperiodic reporting. • Frequency granularity, i.e., wideband or subband, • For multiple CSI-RS resources in a resource set, the CSI parameters to be reported include RI, Precoder Matrix Indicator (PMI), Channel Quality Indicator (CQI), and CSI-RS Resource Indicator (CRI). • Codebook type, i.e., Type I or II, and codebook subset restrictions. • Measurement limits, and / or • Subband size. One of two possible subband sizes is shown, and the range of values ​​depends on the bandwidth of the Bandwidth Portion (BWP). One CQI / PMI (if configured for subband reporting) is fed back per subband.

[0018] When a CSI-RS resource set in a CSI report configuration contains multiple CSI-RS resources, one of the CSI-RS resources is selected by the WD, and the CSI-RS Resource Indicator (CRI) is also reported by the WD to show the selected CSI-RS resource in the resource set to the network node, along with the RI, PMI, and CQI associated with the selected CSI-RS resource.

[0019] In the case of aperiodic CSI reporting in NR, there are two or more systems, each having a different CSI-RS resource set for channel measurement and / or a resource set for interference measurement. CSI Report The settings can be configured and triggered simultaneously. In this case, multiple CSI reports are aggregated and sent from the WD to the network node in a single PUSCH.

[0020] NR rel-15 Type II Codebook For the NR Type II codebook in 3GPP® Release 15 (3GPP® Rel-15), the precoding vectors for each layer and subband are expressed in 3GPP® Specification 38.214 as follows: TIFF0007848312000002.tif32151 The above formula can be more easily reconstructed and expressed, and thus, given layers l=0,1, polarization p=0,1, resource blocks k=0,...,N RB Precoder vector w for -1 l,p (k) can be given as follows: TIFF0007848312000003.tif2479 Here, regarding p=0 Regarding TIFF0007848312000004.tif1477 and p=1 The filename is TIFF0007848312000005.tif1789, where S is the subband size and N is the subband size. SB c is the number of subbands in the CSI report bandwidth. Therefore, the beam coefficient c over frequency. l,iThe change in (k) is 2N SB individual parameters TIFF0007848312000006.tif1369 and The determination is made based on TIFF0007848312000007.tif1066. Here, depending on the codebook configuration, the subband amplitude parameters TIFF0007848312000008.tif1313 is quantized using bits 0-1, and the subband phase parameter φ l,i This is quantized using 2-3 bits. NR 3GPP® Rel-16 Extended Type II Port Selection Codebook. The Extended Type II (eType II) Port Selection (PS) Codebook was introduced in 3GPP® Rel-16 and is intended for use for beamformed CSI-RS, where each CSI-RS port covers a small portion of the cell coverage area with a higher beamforming gain (compared to non-beamformed CSI-RS). Depending on the network node implementation, each CSI-RS port is typically assumed to transmit on a two-dimensional (2D) spatial beam with a main lobe having azimuthal and elevation pointing angles. The actual precoder matrix used for CSI-RS is transparent to the WD. Based on measurements, the WD selects the best CSI-RS port and recommends to the network node the rank, precoding matrix, and CQI conditioned on the rank and precoding matrix for use for downlink (DL) transmission. The precoding matrix comprises a linear combination of the selected CSI-RS ports. The eType II PS codebook can be used by the WD to feed back the selected CSI-RS ports and coupling coefficients.

[0021] Structure, organization, and reporting of the eType II PS codebook For a given transmitting layer l, where l∈{1,...,v} and v is indicated by a rank indicator (RI), the precoder matrix is ​​of size P CSI-RS ×N3 matrix W lGiven by, here, ·P CSI-RS This is the number of CSI-RS ports, N3=N SB ×R is the number of subbands for PMI. The value R={1,2} (PMI subband size indicator) is constructed using RRC, ○N3 is the number of CQI subbands, which are also composed of RRC. • The maximum RI value v is set according to the configured upper layer parameter typeII-RI-Restriction-r16. WD does not need to report v>4.

[0022] For each layer l, the precoding matrix W l is W l = It can be factorized as TIFF0007848312000009.tif1337 (see Figure 4), W l = TIFF0007848312000010.tif1260 is for l=1,...,v and t=0,1,...,N3-1 It is normalized to TIFF0007848312000011.tif1345. Here, the port selection matrix W1 is The decomposable size P is TIFF0007848312000012.tif1656. CSI-RS This is a port selection precoder matrix ×2L, TIFF0007848312000013.tif87 shows the Kronecker product, TIFF0007848312000014.tif1275 is size This is a port selection matrix of size TIFF0007848312000015.tif1420×L, with i=0,1,...,L-1. TIFF0007848312000016.tif1420×1 TIFF0007848312000017.tif1213 contains one element indicating the selected CSI-RS port, with all other elements being 0s. L is the number of CSI-RS ports selected from each polarization, with the same port selected for both polarizations. Supported L values ​​are shown in Table 1.

[0023] • The selected CSI-RS port is reported to the network node by WD. As shown by TIFF0007848312000018.tif1476, a)i 1,1 The value is determined by WD based on CSI-RS measurement. b) The value of d is set by the upper layer parameter portSelectionSamplingSize, where d∈{1,2,3,4} and d <min(P CSI-RS / 2,L) and W1 is common to all layers.

[0024] Dimension N3 × M v Frequency-domain (FD) compression matrix W having f,l is the FD compression matrix for layer l, where TIFF0007848312000019.tif1537 contains the rank indicator v and the RRC configuration parameter p. v The number of selected FD basis vectors, depending on p. v The supported values ​​for W are shown in Table 1. f,l = TIFF0007848312000020.tif1557, here TIFF0007848312000021.tif1731 contains N3 orthogonal discrete Fourier transform (DFT) basis vectors. M selected from TIFF0007848312000022.tif1227 v These are the FD basis vectors, where TIFF0007848312000023.tif1978, (.) T The symbol indicates transpose.

[0025] For N3 ≤ 19, one-step free selection is used.

[0026] c) For each layer, the FD basis selection is: TIFF0007848312000024.tif is represented by an 845-bit combination indicator. According to 3GPP® Technical Standard (TS) 38.214, the combination indicator is represented by index i 1,6,l The given value is l, where l corresponds to the layer index. This combined index is reported by the WD to the network node for each layer. N For 3>19, a two-step selection with a layer common intermediate subset (IntS) is used: i) In the first step, a window-based layer common IntS selection is used. This is M initial It is parameterized by the FD basis vector mod(M initial Includes +n,N3), where n=0,1,...,N3'-1 and N3'=2M v In 3GPP(registered trademark) TS 38.214, the selected IntS is reported per layer as part of the reported PMI by the WD, parameter i 1,5 It is reported to the network node via, ii) The second step subset selection is per layer This is indicated by a 1844-bit combination indicator in TIFF0007848312000025.tif. In TS 38.214, the combination indicator is index i 1,6,l The given value is provided by , where l corresponds to the layer index. This combined index is reported to the network node by WD for each layer. f,l This is layer-specific.

[0027] Linear coupling coefficient matrix W 2,l teeth: • Selected M v2LM for linearly combining FD basis vectors and selected 2L CSI-RS ports v Size 2L×M including the coefficient v It is a matrix of the form, Regarding Layer I, Only a subset of 0 coefficients in TIFF0007848312000026.tif1014 ≤ K are non-zero and reported. The remaining 2LM v - TIFF0007848312000027.tif1014 unreported coefficients are considered zero: ○ TIFF0007848312000028.tif1234 is the maximum number of non-zero coefficients per layer, where β is a Radio Resource Control (RRC) configuration parameter. Supported β values ​​are shown in Table 1. ○ For v ∈ {2, 3, 4}, the total number of non-zero coefficients summed across all layers. TIFF0007848312000029.tif1146 is, Satisfying TIFF0007848312000030.tif1132, ○The selected coefficient subset for each layer is size 2LM. v bitmap i 1,7,l In TIFF0007848312000031.tif1014 is represented by 1 and / or ○The selected CSI-RS port associated with the strongest layer l coefficient is i 1,8,l Identified by ∈{0,1,..,2L-1}, ·W 2,l The amplitude coefficient is i 2,3,l and i 2,4,l As shown by W 2,l The phase coefficient is i 2,5,l As shown by, and / or ·W 2,l This is layer-specific.

[0028] The PMI reported by TIFF0007848312000032.tif63131WD has codebook indices i1 and i2, where, The precoding matrix for TIFF0007848312000033.tif42164 is the PMI value according to Table 2.

[0029] TIFF0007848312000034.tif2521633GPP(registered trademark) For Rel-16 Extended Type II CSI feedback, the CSI report consists of two parts. Part 1 has a fixed payload size and is used to identify the number of information bits in Part 2. Part 1 includes indication of RI, CQI, and the total number of non-zero amplitude coefficients across layers, i.e. TIFF0007848312000035.tif1457. Part 2 includes PMI. Parts 1 and 2 are encoded separately.

[0030] FDD-based reciprocal operation and 3GPP® Rel-17 Type II port selection codebook In frequency-division duplex (FDD) operation, uplink (UL) and downlink (DL) transmissions are performed at different frequencies. Therefore, the propagation channels in UL and DL are not inverse of those in time-division duplex (TDD). Nevertheless, some physical channel parameters, such as delay and angle to different clusters, which depend on the spatial characteristics of the channel but not on the carrier frequency, are reciprocals between UL and DL. Such characteristics can be used to obtain FDD transmission based on partial reciprocity. The reciprocal part of the channel can be combined with the non-reciprocal part to obtain a complete channel. Estimates of the non-reciprocal part can be obtained by feedback from the WD. In 3GPP® RAN1, 3GPP® Rel-17, and 3GPP® Rel-16 Type II Port Selection Codebook are being considered to be enhanced to support the FDD-based reciprocal operation described above. In 3GPP® RAN1#104e, the 3GPP® Rel-17 Type II port selection codebook adopts the same codebook configuration as the 3GPP® Rel-16 Type II port selection codebook, that is, the codebooks are W1, W2 and W f It is believed to include the following. Further investigation of the codebook components, such as the dimensions of each matrix, is still ongoing.

[0031] Procedure for FDD-based reciprocal operation One exemplary procedure for a reciprocity-based FDD transmission scheme is shown in four steps in Figure 5, assuming the use of the NR 3GPP® Rel.16 Extended Type II Port Selection Codebook.

[0032] In step 1, the WD is configured with a sounding reference signal (SRS) by the network node, and the WD transmits the sounding reference signal (SRS) at the UL for the network node to estimate the angles and delays of different clusters associated with different propagation paths.

[0033] In step 2, the network node implementation algorithm selects a dominant cluster according to the estimated angular delay power spectral profile, and based on this, a set of spatial domain and frequency domain (SD-FD) basis pairs is computed by the network node for CSI-RS beamforming. Each SD-FD pair corresponds to a CSI-RS port with a predetermined delay pre-compensated. Each CSI-RS port resource can contain one or more SD-FD basis pairs by applying different delays to different resource elements of the resource. The network node precodes all CSI-RS ports in a configured CSI-RS resource or multiple CSI-RS resources into WDs, and each configured CSI-RS resource contains the same number of SD-FD basis pairs.

[0034] In step 3, the network node configures the WD to measure the CSI-RS, which measures the received CSI-RS ports and then determines the type II CSI, including the RI, PMI for each layer, and CQI. The precoding matrix indicated by the PMI includes the selected SD-FD basis pair / precoded CSI-RS ports and the corresponding best phase and amplitude for common-phase the selected pair / port. The phase and amplitude of each pair / port are quantized and fed back to the network node.

[0035] In step 4, the network node implementation algorithm calculates a layer-by-layer DL precoding matrix based on the selected beam and the corresponding amplitude and phase feedback, and then performs a PDSCH transmit. The transmit is based directly on the feedback (PMI) precoding matrix (e.g., single-user (SU)-MIMO transmit), or the transmit precoding matrix is ​​obtained from an algorithm that combines CSI feedback from multiple WDs (MU-MIMO transmit). In this case, a precoder (e.g., a zero-forcing (ZF) precoder or a normalized ZF precoder) is derived based on the precoding matrix (including CSI reports from concurrently scheduled WDs). The final precoder is generally scaled so that the transmit power per power amplifier is not overridden.

[0036] Such reciprocity-based transmission could potentially be utilized in codebook-based DL transmission for FDD to reduce feedback overhead in UL when NR Type II port selection codebooks are used. Another potential benefit is the reduction in the complexity of CSI calculations in WD. Note that Figure 5 is only a schematic example of the procedure for FDD-based reciprocity operation, where each CSI-RS port contains a single pair of SD-FD bases and WD performs broadband averaging of the channel to obtain the corresponding coefficients. Each CSI-RS port contains multiple pairs of SD-FD bases, and WD can compress the channel with more FD components in addition to the DC DFT components.

[0037] Type II Port Selection Codebook for FDD Operation Based on Angular and Delay Reciprocity When the 3GPP® Rel-16 Extended Type II Port Selection Codebook is used for FDD operation based on angular and / or delay reciprocity, the frequency domain (FD) basis W f This still needs to be determined by the WD. Therefore, the CSI report should provide feedback to indicate which FD basis vectors to select. Overhead The number of PMI subbands can increase, especially in the case of N3, where the number of PMI subbands is large. Furthermore, the computational complexity in WD for evaluating and selecting the best FD basis vectors also increases as N3 increases. Additionally, the channels observed in WD are frequency-selective, which requires several FD basis vectors to be compressed in the PMI report. Reporting the coefficients to these FD basis vectors also consumes a significant UL overhead.

[0038] As described above, based on the interrelationship of angle and delay, network nodes can determine the dominant set of clusters within a propagation channel by analyzing the angular delay power spectrum of the UL channel. The network nodes can then utilize this information so that each CSI-RS port is precoded toward the dominant cluster. In addition to SD beamforming, each CSI-RS port is also temporally pre-compensated so that all precoded CSI-RS ports are aligned in the delay domain. As a result, the frequency selectivity of the channel is eliminated, and the WD observes a frequency-flat channel requiring a very small number of FD basis vectors to compress. Ideally, if all beams could be perfectly aligned in time, the WD would only need to perform broadband filtering to obtain all channel information, on which it could calculate the 3GPP® Rel-17 Type II PMI. In practice, even if the delay cannot be fully pre-compensated at the network node, the frequencies selectively observed by the WD can still be significantly reduced, and therefore the WD can compress the channel with a much smaller number of frequency domain (FD) basis vectors, i.e., W f It only requires the number of basis vectors in the given structure.

[0039] The above procedure is further illustrated in the example in Figure 6. Based on UL measurements, the network node identifies eight dominant clusters present in the original channel, tagged as AGs, which are distributed in four directions, each containing one or more taps. In this example, eight CSI-RS ports are precoded at the network node. Each CSI-RS port is precoded toward the dominant direction with a pre-compensated delay for a given cluster. Delay compensation can be achieved in different ways, for example, by applying a linear phase gradient across the occupied subcarriers. As a result, in the beamformed channel seen in the WD, all dominant clusters are aligned with the same delay. Therefore, the WD only needs to apply a broadband filter, which is, for example, W f However, this can be achieved by applying the DC component of the DFT matrix, that is, by compressing the channels and including a single vector among all vectors of ones across the frequency domain channels in order to preserve all channel information. Based on the compressed channels, the WD calculates W1 (the selected CSI-RS ports) and W2 (complex coefficients for combining the selected ports), which are the remainder of the Type II port selection codebook. Figure 7 shows another example of precoding.

[0040] While the development of the 3GPP® Rel-17 Type II codebook is still ongoing, it has been confirmed that the 3GPP® Rel-16 Type II codebook structure will be reused for 3GPP® Rel-17, meaning that 3GPP® Rel-17 will use W1, W2 and W f This also includes. One potential difference between the 3GPP® Rel-17 codebook and the 3GPP® Rel-16 Type II codebook is W f This can be common to all layers. The structure of W1 and W2 is the same as that of 3GPP® Rel-16 Type II.

[0041] PUSCH Type II CSI Report If the WD successfully decodes downlink control information (DCI) format 0_1 ​​or DCI format 0_2 that triggers an aperiodic CSI trigger condition, it may use PUSCH to perform an aperiodic CSI report.

[0042] When DCI format 0_1 ​​schedules two PUSCH assignments, the aperiodic CSI report is carried on the second scheduled PUSCH. When DCI format 0_1 ​​schedules three or more PUSCH assignments, the aperiodic CSI report is carried on the second scheduled PUSCH. The second to last It will be executed by scheduled PUSCH.

[0043] If the WD successfully decodes DCI format 0_1 ​​or DCI format 0_2 to activate a semi-persistent CSI trigger state, it may perform a semi-persistent CSI report to the PUSCH. DCI format 0_1 ​​and DCI format 0_2 include a CSI request field indicating a semi-persistent CSI trigger state to activate or deactivate. The PUSCH resource and MCS may be semi-persistently allocated by the uplink DCI.

[0044] CSI reports on PUSCH can be multiplexed with uplink data on PUSCH. CSI reports on PUSCH can also be run without any multiplexing with uplink data from WD.

[0045] Type II CSI Report Part 1 and Part 2 For 3GPP® Rel-15 Type II and 3GPP® Rel-16 Type II (also known as Extended Type II or eType II) CSI feedback on PUSCH, the CSI report consists of two parts: Part 1 and Part 2. The main motivation for dividing the CSI report into Part 1 and Part 2 is to accommodate dynamically changing CSI payloads. For example, based on time-varying channels, a WD may report different ranks over the entire duration of the connection, which significantly impacts the actual required CSI payload size. Part 1, which has a fixed payload size and carries information for calculating the payload size in Part 2, is decoded first by the network node so that the network node can know the actual payload size.

[0046] For 3GPP® Rel-15 Type II CSI feedback, Part 1 includes rank information (RI) (if reported), channel quality indicator (CQI), and an indication of the number of non-zero wideband amplitude coefficients per layer for Type II CSI (see Section 5.2.2.2.3 of 3GPP® TS 38.214). The fields of Part 1—RI (if reported), CQI, and the indication of the number of non-zero wideband amplitude coefficients for each layer—are encoded separately. Part 2 includes the PMI for Type II CSI. Parts 1 and 2 are encoded separately.

[0047] For 3GPP® Rel-16 Type II CSI feedback, Part 1 includes indications for the RI, CQI, and the total number of non-zero amplitude factors across the layers for 3GPP® Rel-16 Type II CSI (see Section 5.2.2.2.5 of 3GPP® TS 38.214). Part 1—indications for the RI, CQI fields, and the total number of non-zero amplitude factors across the layers—are encoded separately. Part 2 includes PMI for Extended Type II CSI. Parts 1 and 2 are encoded separately.

[0048] UCI omission procedure for Type II CSI reports Because there can be significant discrepancies between PMI payloads due to different RI selections by WDs for Type II CSI reports, PUSCH resource allocations for carrying CSI reports may not fit the entire CSI content. For example, a Rank 2 PMI payload is almost twice as large as a Rank 1 PMI payload in the 3GPP® Rel-15 / 3GPP® Rel-16 Type II codebook. Also, because RIs are dynamically selected by WDs, network nodes cannot fully predict the PMI payload before scheduling CSI reports, and therefore resource allocations may be too small. That is, a network node might schedule appropriate resources for a Rank 1 PMI report (for example, because a WD has recently reported RI=1), but the WD reports a Rank 2 PMI, which does not fit the allocated PUSCH resources.

[0049] To address this issue, a CSI omission procedure is specified in 3GPP®, which allows for the omission of a portion of CSI Part 2 if the resulting Uplink Control Information (UCI) coding rate is too low (Part 1 cannot be omitted as it is required to correctly decode Part 2). This involves segmenting the CSI Part 2 payload into different priority levels and UCI sign This is achieved by dropping CSI segments starting from the lowest priority level until the rate falls below a threshold (therefore, the CSI payload "fits" for PUSCH allocation). The priority levels for 3GPP® Rel-15 and 3GPP® Rel-16 Type II are listed in Table 3 (Table 5.2.3-1 in 3GPP® TS 38.214 V16.0.0), where priority 0 has the highest priority and N_Rep is CSI Report This represents the number of items. The CSI omission procedure is explained in more detail below.

[0050] TIFF0007848312000036.tif254703GPP(Registered Trademark) Rel-15 Type II CSI (abbreviated): In the case of 3GPP® Rel-15 Type II, CSI Part 2 is divided into a wideband PMI part and a subband PMI part. The wideband part carries information such as rotation coefficients (in the case of normal Type II) or port indications (in the case of port-selected Type II), wideband amplitude coefficients per layer, and spatial domain (SD) basis indications including the strongest coefficient indicator (SCI) per layer. The subband part carries information such as subband amplitude and phase.

[0051] Subband PMIs are reported independently for each subband, making them the heaviest payload (while broadband PMIs are reported only once for the entire CSI reporting band). In the CSI omission procedure described, subband PMIs for odd and even subbands are grouped into different CSI segments with different priorities. This means that if the PUSCH resource allocation is too small to fit the CSI payload, subband PMIs for odd subbands can be dropped, and only subband PMIs for even subbands will be reported.

[0052] The motivation behind this design is that the remaining reported PMIs can still be used by network nodes. Since network nodes have knowledge of subband PMIs for every other subband, they can perform interpolation between subbands to estimate the PMI for the omitted subbands. Because subband PMIs are correlated in frequency, the performance loss may not be significant.

[0053] 3GPP(registered trademark) Rel-16 Type II CSI (abbreviated): For 3GPP® Rel-16 Type II, CSI Part 2 is divided into three groups: Group 0: Rotation coefficient (for 3GPP® Rel-16 Regular Type II) or port indication (for 3GPP® Rel-16 Port Select Type II), SD base indication including SCI for each layer, Group 1: Frequency domain (FD) basis indications for each layer, broadband (polarization) reference amplitude, portion of the bitmap, and amplitude and phase of the highest priority subband coefficients. Group 2: Bitmap of the subband coefficients with the lowest priority, and the remaining parts of amplitude and phase.

[0054] The bitmap, subband amplitude, and phase in groups 1 and 2 were reported respectively. element The priority level is determined by the values ​​of the following priority function, indexed by l,i,f: TIFF0007848312000037.tif10103 here The filename is TIFF0007848312000038.tif12113, where l=1,2,...,v is the layer index, v is the RI, i=0,1,...,2L-1 is the index of the selected port, and f=0,1,...,M v -1 is the index of the selected FD basis vector, and M v This is the number of FD basis vectors selected for each layer, TIFF0007848312000039.tif1263 is the index of the FD basis vectors that WD can select, and N3 is the number of PMI subbands. The element with the highest priority will have the lowest associated value Pri(l,i,f).

[0055] The motivation behind the way grouping is performed is that even if some low-priority groups are omitted, it should still be possible for network nodes to recover part of the CSI. For example, if groups 1 and 2 are omitted, the PMI feedback in group 0 is essentially a type I PMI, and network nodes can still schedule SU-MIMO based on its CSI report. In another example, if group 2 is omitted, the information for the selected SD and FD basis vectors is still complete, and only some of the coupling coefficients are omitted. However, since the coupling coefficients are reported and omitted in a predictable manner based on a predefined priority function, network nodes are still aware of the association between the reported coefficients and the SD and FD basis vectors. Thus, DL channels can still be partially obtained through an incomplete CSI report.

[0056] Because the payload of the 3GPP® Rel-17 Type II CSI is highly dependent on the reported rank, a robust CSI omission procedure is required for 3GPP® Rel-17 Type II to function even if parts of the CSI report are omitted. type Reusing the II CSI omission rule may not work when 3GPP® Rel-17 Type II is configured, including CSI grouping and priority processing. For example, if CSIs in groups 1 and 2 are omitted according to the 3GPP® Rel-16 Type II CSI omission rule, the network node cannot reconstruct the DL channel based solely on CSI group 0 because the selected FD-based essential information is lost. [Overview of the project]

[0057] Several embodiments provide advantageous methods, network nodes, and wireless devices for channel state information (CSI) omission for Type II CSI. Some embodiments provide a set of solutions for robust CSI omission procedures for 3GPP® Rel-17 Type II, including CSI content grouping and priority processing, including one or more of the following examples: • A method / configuration for determining the group position indicating the selected FD basis based on the CSI report configuration. • Methods / arrangements for priority processing in priority functions, • Part 2: Methods / Arrangements for Grouping CSIs.

[0058] According to one embodiment, a method in a network node configured to communicate with a wireless device, wherein a WD receives from the WD the ability to report for a codebook-based CSI, which includes indication of channel state information (CSI) and information of at least one frequency domain (FD) basis vector. The method also includes configuring the WD to report the codebook-based CSI in a plurality of CSI report groups having different priorities, wherein the FD basis vector information is associated with the CSI in the CSI report group having the highest priority among the plurality of CSI report groups.

[0059] According to this embodiment, in some embodiments, the codebook of a codebook-based CSI is a port selection codebook, and the CSI further comprises indices of a plurality of selected CSI reference signal (CSI-RS) ports. In some embodiments, the port selection codebook is an extended type II port selection codebook as defined in 3GPP® New Radio Technical Release 17, and the WD is configured to report FD basis vector information in CSI report group 0. In some embodiments, the FD basis vector information includes an index indicating a set of selected FD basis vectors. In some embodiments, the CSI further comprises information of a plurality of layers, and the FD basis vector information includes FD basis vector information for each of the plurality of layers. In some embodiments, the plurality of layers, a plurality of ports, and FD basis vectors are prioritized from highest to lowest in the order of FD basis vectors, ports, and then layers. In some embodiments, the CSI further comprises a set of non-zero subband coefficients and associated non-zero bitmaps for each layer, where at least one of the non-zero subband coefficients and the bits of the bitmap associated with the FD basis vector having the lowest index are assigned the highest priority. In some embodiments, each of the non-zero subband coefficients includes amplitude and phase. In some embodiments, at least one of the non-zero bitmaps and non-zero subband coefficients for all layers is reported in the same CSI reporting group. In some embodiments, sets of non-zero bitmaps and non-zero subband coefficients for each of multiple layers are reported in different CSI reporting groups. In some embodiments, sets of non-zero subband coefficients and non-zero bitmaps for sets of non-zero subband coefficients are reported in one of CSI reporting groups 1 and 0, at least partially based on priority.

[0060] In another embodiment, a network node configured to communicate with a wireless device (WD) includes a wireless interface configured to receive from the WD(22) the ability to report for a codebook-based CSI, which includes channel state information (CSI) indications and information for at least one frequency domain (FD) basis vector. The wireless interface is also configured to configure the WD to report the codebook-based CSI in a plurality of CSI report groups having different priorities, and the FD basis vector information is associated with the CSI in the CSI report group having the highest priority among the plurality of CSI report groups.

[0061] According to this embodiment, in some embodiments, the codebook of a codebook-based CSI is a port selection codebook, and the CSI further comprises an index of a plurality of selected CSI reference signal (CSI-RS) ports. In some embodiments, the port selection codebook is an extended type II port selection codebook as defined in 3GPP® New Radio Technical Release 17, and the WD is configured to report FD basis vector information in CSI report group 0. In some embodiments, the FD basis vector information includes an index indicating a set of selected FD basis vectors. In some embodiments, the CSI further comprises information for a plurality of layers, and the FD basis vector information includes FD basis vector information for each layer of the plurality of layers. In some embodiments, the layers, plurality of ports, and FD basis vectors are prioritized from highest to lowest in the order of FD basis vectors, ports, and then layers. In some embodiments, the CSI further comprises a set of non-zero subband coefficients and associated non-zero bitmaps for each layer, and at least one of the non-zero subband coefficients and the bit of the bitmap associated with the FD basis vector having the lowest index are assigned the highest priority. In some embodiments, each of the non-zero subband coefficients includes amplitude and phase. In some embodiments, at least one of the non-zero bitmaps and non-zero subband coefficient sets for all layers is reported in the same CSI report group. In some embodiments, the non-zero bitmaps and non-zero subband coefficients for each of multiple layers are reported in different CSI report groups. In some embodiments, the set of non-zero subband coefficients and the non-zero bitmaps for the set of non-zero subband coefficients are reported in one of CSI report groups 1 and 0, at least partially based on priority.

[0062] In yet another embodiment, a method in a wireless device (WD) configured to communicate with a network node includes receiving a configuration for reporting codebook-based channel status information (CSI) comprising frequency domain (FD) basis vector information, and reporting the codebook-based CSI in a plurality of CSI report groups having different priorities, wherein the FD basis vector information is included in the CSI report group having the highest priority among the plurality of report groups.

[0063] In this embodiment, in some embodiments, the method includes reporting FD basis vector information in CSI report group 1 for a Type II port selection codebook as defined in 3GPP® Technical Release 16 and reporting FD basis vector information in CSI report group 0 for a Type II port selection codebook as defined in 3GPP® Technical Release 17. In some embodiments, the FD basis vector information includes an index indicating a set of selected FD basis vectors. In some embodiments, the codebook CSI further includes information for multiple layers, and the FD basis vector information includes FD basis vector information for each layer of the multiple layers. In some embodiments, the layers, multiple ports, and FD basis vectors are prioritized from highest to lowest in the order of FD basis, port, and then layer. In some embodiments, at least one of the non-zero bitmaps and subband coefficients for all layers is reported in the same CSI report group. In some embodiments, at least one of the bitmaps and subband amplitudes and phases for each of the subsets of multiple layers is reported in different CSI report groups. In some embodiments, a set of non-zero subband coefficients and a non-zero bitmap for the set of non-zero subband coefficients are reported in one of CSI report groups 1 and 0, at least partially based on priority.

[0064] In another embodiment, a wireless device (WD) configured to communicate with a network node includes a wireless interface configured to receive a configuration for reporting codebook-based channel status information (CSI) comprising frequency domain (FD) basis vector information, and to report the codebook-based CSI in a plurality of CSI report groups having different priorities, wherein the FD basis vector information is included in the CSI report group having the highest priority among the plurality of report groups.

[0065] According to this embodiment, in some embodiments, reporting includes reporting FD basis vector information in CSI report group 1 for a Type II port selection codebook as defined in 3GPP® Technical Release 16 (3GPP® Release 16) and reporting FD basis vector information in CSI report group 0 for a Type II port selection codebook as defined in 3GPP® Technical Release 17 (3GPP® Release 17). In some embodiments, the FD basis vector information includes an index indicating a set of selected FD basis vectors. In some embodiments, the codebook CSI further includes information for multiple layers, and the FD basis vector information includes FD basis vector information for each layer of the multiple layers. In some embodiments, the layers, multiple ports, and FD basis vectors are prioritized from highest to lowest in the order of FD basis, port, and then layer. In some embodiments, at least one of the non-zero bitmaps and subband coefficients for all layers is reported in the same CSI report group. In some embodiments, at least one of the bitmaps and subband amplitudes and phases for each of the subsets of multiple layers is reported in different CSI report groups. In some embodiments, a set of non-zero subband coefficients and a non-zero bitmap for the set of non-zero subband coefficients are reported in one of CSI report groups 1 and 0, at least partially based on priority. [Brief explanation of the drawing]

[0066] A more complete understanding of this embodiment, as well as its associated advantages and features, will be more readily apparent by referring to the following detailed description in conjunction with the accompanying drawings. [Figure 1] Figure 1 shows the transmission structure for pre-coded spatial multiplexing. [Figure 2] Figure 2 is a diagram representing a two-dimensional array. [Figure 3] Figure 3 shows an example of resource element allocation. [Figure 4] Figure 4 shows the factorization of a Type II port selection precoder. [Figure 5] Figure 5 illustrates the procedure for sending a codebook-based message. [Figure 6] Figure 6 shows an example of CSI-RS precoding. [Figure 7] Figure 7 is a schematic diagram of an exemplary network architecture illustrating a communication system connected to a host computer via an intermediate network, based on the principles of this disclosure. [Figure 8] Figure 8 is a block diagram of a host computer communicating with a wireless device and a network node, at least partially via a wireless connection, according to some embodiments of the present disclosure. [Figure 9] Figure 9 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node, and a wireless device for running a client application on a wireless device, according to some embodiments of the present disclosure. [Figure 10] Figure 10 is a flowchart illustrating an exemplary method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data in a wireless device, according to some embodiments of the present disclosure. [Figure 11]Figure 11 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data from a wireless device in a host computer, according to some embodiments of the present disclosure. [Figure 12] Figure 12 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, network nodes, and wireless devices for receiving user data in a host computer, according to some embodiments of the present disclosure. [Figure 13] Figure 13 is a flowchart illustrating an exemplary process at a network node for omitting channel state information (CSI) for type II CSI. [Figure 14] Figure 14 is a flowchart illustrating an exemplary process in a wireless device for omitting channel state information (CSI) for Type II CSI. [Figure 15] Figure 15 is a flowchart of another exemplary process at a network node for omitting channel state information (CSI) for type II CSI. [Figure 16] Figure 16 is a flowchart of another exemplary process in a wireless device for omitting channel state information (CSI) for Type II CSI. [Figure 17] Figure 17 shows an example of CSI-RS precoding based on the principles described herein. [Modes for carrying out the invention]

[0067] Before describing exemplary embodiments in detail, it should be noted that embodiments primarily concern combinations of device components and processing steps related to the omission of channel state information (CSI) for Type II CSI. Therefore, components are represented, where appropriate, by conventional symbols in the drawings, and only specific details relevant to understanding the embodiments are shown, so as not to obscure this disclosure with details that would be readily apparent to those skilled in the art who benefit from the description herein. Similar numbers refer to similar elements throughout the description.

[0068] Where used herein, relational terms such as “first” and “second,” “upper” and “lower” may be used solely to distinguish one entity or element from another entity or element, and do not necessarily require or imply any physical or logical relationship or order between such entities or elements. The terms used herein are intended solely to describe specific embodiments and are not intended to limit the concepts described herein. Where used herein, the singular forms “a,” “an,” and “the” are intended to include the plural form unless the context clearly indicates otherwise. Where used herein, the terms “comprises,” “comprising,” “includes,” and / or “including” identify the presence of the described feature, integer, step, action, element, and / or component, but do not exclude the presence or addition of one or more other features, integers, steps, actions, elements, components, and / or groups thereof.

[0069] In the embodiments described herein, concordant terms such as “communicating with” may be used to indicate telecommunications or data communications, which may be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signals, infrared signals, or optical signals. Those skilled in the art will understand that multiple components can interact with each other and that modifications and variations are possible to achieve electrical and data communications.

[0070] In some embodiments described herein, terms such as “coupled” and “connected” may be used herein to indicate a connection, even if not directly related, and may include wired and / or wireless connections.

[0071] As used herein, the term “network node” may refer to any type of network node included in a radio network, further including base stations (BS), radio base stations, base transceiver stations (BTS), base station control units (BSC), radio network controllers (RNC), g-node B (gNB), advanced node B (eNB or eNodeB), node B, multi-standard radio (MSR) radio nodes such as MSR BS, multi-cell / multicast coordinating entities (MCE), integrated access and backhaul (IAB) nodes, relay nodes, donor nodes controlling relay, radio access points (AP), transmit points, transmit nodes, remote radio units (RRU), remote radio heads (RRH), core network nodes (e.g., mobile management entities (MME), self-organizing network (SON) nodes, coordinating nodes, positioning nodes, MDT nodes, etc.), external nodes (e.g., third-party nodes, nodes outside the current network), distributed antenna systems (DAS), spectrum access system (SAS) nodes, element management systems (EMS), and any other network node. Network nodes may also be equipped with test equipment. As used herein, the term “wireless node” may also be used to refer to a wireless device (WD) or a wireless network node, or any other wireless device (WD).

[0072] In some embodiments, the non-limiting terms "wireless device (WD)" and "user equipment (UE)" are used interchangeably. A WD as herein can be any type of wireless device capable of communicating with a network node or another WD via wireless signals, such as a wireless device (WD). A WD may also be a wireless communication device, a target device, a device-to-device (D2D) WD, a machine-type WD or WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet, a mobile terminal, a smartphone, an embedded laptop (LEE), a laptop-based equipment (LME), a USB dongle, customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device.

[0073] Furthermore, in some embodiments, the general term “wireless network node” is used. It can be any type of wireless network node, which may comprise any of the following: base station, wireless base station, base station transceiver, base station control unit, network controller, RNC, advanced node B (eNB), node B, gNB, multicell / multicast cooperative entity (MCE), IAB node, relay node, access point, wireless access point, remote radio unit (RRU), or remote radio head (RRH).

[0074] For example, while terms from a particular radio system, such as 3GPP® LTE and / or New Radio (NR), may be used in this disclosure, it should be noted that this should not be considered to limit the scope of this disclosure to the aforementioned systems only. However, other radio systems, including Wideband Code Division Multiple Access (WCDMA®), Worldwide Interoperability for Microwave Access (WiMAX), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM®), may also benefit from leveraging the ideas covered within this disclosure.

[0075] Furthermore, it should be noted that the functions described herein as being performed by wireless devices or network nodes may be distributed across multiple wireless devices and / or network nodes. In other words, the functions of network nodes and wireless devices described herein are not limited to the performance of a single physical device, but are intended to be distributed across several physical devices.

[0076] In some embodiments, a general descriptive element of the form "one of A and B" corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B or AB, or one or more of A and B. In some embodiments, at least one of A, B and C corresponds to one or more of A, B and C, and / or A, B, C, or any combination thereof.

[0077] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as those generally understood by those skilled in the art to which this disclosure belongs. Terms used herein should be construed to have meanings consistent with their meanings in the context of this specification and related art, and it will be further understood that they should not be construed in an idealized or overly formal sense unless expressly defined herein.

[0078] Some embodiments conform to 3GPP® Rel-17 (Release 17) Type II. CSI Report This provides a robust CSI omission procedure. It should also be noted that the 3GPP® standard does not require the use of the term Transmit / Receive Point (TRP). Instead, a TRP may be represented by a Transmit Configuration Indication (TCI) state, a Non-Zero Power (NZP) CSI-RS resource, or a subset of ports within an NZP CSI-RS resource.

[0079] Referring again to drawings where similar elements are referenced by similar reference numerals, Figure 7 shows a schematic diagram of a communication system 10 in an embodiment such as a 3GPP® type cellular network capable of supporting standards such as LTE and / or NR (5G), comprising an access network 12 such as a radio access network and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs, or other types of radio access points, each defining a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c is connectable to the core network 14 via a wired or wireless connection 20. A first radio device (WD) 22a located in coverage area 18a is configured to wirelessly connect to or be paged by a corresponding network node 16a. A second WD 22b within coverage area 18b can wirelessly connect to the corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where a single WD is within a coverage area or where a single WD is connected to the corresponding network node 16. For convenience, only two WDs 22 and three network nodes 16 are shown, but it should be noted that the communication system may include more WDs 22 and network nodes 16.

[0080] Furthermore, it is intended that the WD 22 can communicate simultaneously and / or be configured to communicate separately with two or more network nodes 16 and two or more types of network nodes 16. For example, the WD 22 may have dual connectivity with a network node 16 that supports LTE and the same or different network nodes 16 that support NR. As an example, the WD 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0081] The communication system 10 itself may be connected to a host computer 24, which may be embodied in the hardware and / or software of a standalone server, a cloud implementation server, a distributed server, or as a processing resource in a server farm. The host computer 24 may be owned or under the control of a service provider, or may be operated by or on behalf of a service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24, or may extend through an arbitrary intermediate network 30. The intermediate network 30 may be one or more combinations of a public network, a private network, or a hosted network. The intermediate network 30 may be a backbone network or the internet, if any. In some embodiments, the intermediate network 30 may comprise two or more subnets (not shown).

[0082] The communication system in Figure 7, as a whole, enables a connection between one of the connected WDs 22a, 22b and the host computer 24. The connectivity can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and / or signaling over the OTT connection using the access network 12, the core network 14, an optional intermediate network 30, and possible further infrastructure (not shown) as intermediaries. The OTT connection can be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of the routing of uplink and downlink communications. For example, network node 16 does not need to know, or is not required to know, the past routing of incoming downlink communications that have data originating from the host computer 24 to be forwarded (e.g., handed over) to the connected WD 22a. Similarly, network node 16 does not need to know the future routing of outgoing uplink communications from the WD 22a to the host computer 24.

[0083] Network node 16 is configured to include a configuration unit 32 configured to configure the WD to report codebook-based CSIs in multiple CSI report groups having different priorities, and FD basis vector information is associated with the CSI in the CSI report group having the highest priority among the multiple CSI report groups. Wireless device 22 is configured to include a priority unit 34 configured to report codebook-based CSIs in multiple CSI report groups having different priorities, and FD basis vector information is included in the CSI report group having the highest priority among the multiple report groups.

[0084] An exemplary embodiment described in the preceding paragraph, comprising WD 22, network node 16, and host computer 24, will be described with reference to Figure 8. The communication system 10 includes hardware (HW) 38, including a communication interface 40 configured on the host computer 24 to set up and maintain wired or wireless connections with the interfaces of different communication devices of the communication system 10. The host computer 24 further includes a processing circuit 42 which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and memory 46. In particular, in addition to a processor such as a central processing unit and memory, or instead, the processing circuit 42 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (field-programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) memory 46, which may have any type of volatile and / or nonvolatile memory, such as cache memory and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0085] The processing circuit 42 may be configured to control any of the methods and / or processes described herein and / or to cause a host computer 24, for example, to execute such methods and / or processes. The processor 44 corresponds to one or more processors 44 for performing the functions of the host computer 24 described herein. The host computer 24 includes memory 46 configured to store data, program software code, and / or other information described herein. In some embodiments, when the software 48 and / or host application 50 is executed by the processor 44 and / or processing circuit 42, it may include instructions that cause the processor 44 and / or processing circuit 42 to execute the processes described herein with respect to the host computer 24. The instructions may be software associated with the host computer 24.

[0086] Software 48 may be executable by processing circuit 42. Software 48 includes a host application 50. The host application 50 may be operable to provide services to remote users, such as a WD 22 connected via an OTT connection 52 terminating at the host computer 24. When providing services to remote users, the host application 50 may provide user data transmitted using the OTT connection 52. "User data" may be data and information described herein as implementing the described functions. In one embodiment, the host computer 24 may be configured to provide control and functionality to a service provider and may be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit, and / or receive network nodes 16 and / or wireless devices 22.

[0087] The communication system 10 further includes a network node 16, which is provided within the communication system 10 and includes hardware 58 that enables communication with the host computer 24 and the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining wired or wireless connections with the interfaces of different communication devices of the communication system 10, and a wireless interface 62 for setting up and maintaining at least a wireless connection 64 with the WD 22 located in a coverage area 18 serviced by the network node 16. The wireless interface 62 may be formed, or include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct, or it may pass through the core network 14 of the communication system 10, and / or it may pass through one or more intermediate networks 30 outside the communication system 10.

[0088] In the illustrated embodiment, the hardware 58 of the network node 16 further includes a processing circuit 68. The processing circuit 68 may include a processor 70 and memory 72. In particular, in addition to a processor such as a central processing unit and memory, or instead, the processing circuit 68 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (field-programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 70 may include any kind of volatile and / or non-volatile memory, such as cache memory and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory), and may be configured to access (e.g., write and / or read) memory 72.

[0089] Therefore, the network node 16 further has software 74 stored internally, for example, in memory 72, or stored in external memory (e.g., a database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by a processing circuit 68. The processing circuit 68 may be configured to control any of the methods and / or processes described herein, and / or to cause such methods and / or processes to be executed, for example, by the network node 16. The processor 70 corresponds to one or more processors 70 for performing the functions of the network node 16 described herein. Memory 72 is configured to store data, program software code, and / or other information described herein. In some embodiments, when the software 74 is executed by the processor 70 and / or the processing circuit 68, it may include instructions that cause the processor 70 and / or the processing circuit 68 to execute the processes described herein with respect to the network node 16. For example, the processing circuit 68 of the network node 16 may include a configuration unit 32 configured to configure the WD to report codebook-based CSIs in multiple CSI report groups having different priorities, and the FD basis vector information is associated with the CSI in the CSI report group having the highest priority among the multiple CSI report groups.

[0090] The communication system 10 further includes the WD 22 already mentioned. The WD 22 may have hardware 80 which may include a radio interface 82 configured to set up and maintain a radio connection 64 with a network node 16 serving the coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers, or may include them.

[0091] The WD 22 hardware 80 further includes a processing circuit 84. The processing circuit 84 may include a processor 86 and memory 88. In particular, in addition to a processor such as a central processing unit and memory, or instead, the processing circuit 84 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (field-programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may include any kind of volatile and / or non-volatile memory, such as cache memory and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0092] Therefore, the WD 22 may further include software 90, which may be stored in the WD 22's memory 88 or in external memory accessible by the WD 22 (e.g., a database, storage array, network storage device, etc.). The software 90 may be executable by the processing circuit 84. The software 90 may include a client application 92. The client application 92 may be able to operate to provide services to human or non-human users via the WD 22 with the support of the host computer 24. On the host computer 24, a running host application 50 can communicate with the running client application 92 via an OTT connection 52 that terminates at the WD 22 and the host computer 24. When providing services to a user, the client application 92 can receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 can transfer both the request data and the user data. The client application 92 can interact with the user and generate the user data it provides.

[0093] The processing circuit 84 may be configured to control any of the methods and / or processes described herein, and / or to cause such methods and / or processes to be performed, for example, by the WD 22. The processor 86 corresponds to one or more processors 86 for performing the WD 22 functions described herein. The WD 22 includes memory 88 configured to store data, program software code, and / or other information described herein. In some embodiments, when the software 90 and / or client application 92 is executed by the processor 86 and / or processing circuit 84, it may include instructions to cause the processor 86 and / or processing circuit 84 to perform the processes described herein with respect to the WD 22. For example, the processing circuit 84 of the wireless device 22 may include a priority unit 34 configured to report codebook-based CSIs in a plurality of CSI report groups with different priorities, and FD basis vector information is included in the CSI report group having the highest priority among the plurality of report groups. The processing circuit 84 may be further configured to report to the network node at least one of the following: a group position for indicating a set of frequency domain (FD) basis vectors; a priority for reporting elements of an index representing at least one of the bitmaps for subband amplitude, subband phase, and non-zero coefficients; and a group position for indicating at least one of the bitmaps for non-zero coefficients, subband amplitude, and phase coefficients.

[0094] In some embodiments, the internal operation of the network node 16, WD 22, and host computer 24 may be as shown in Figure 8, and independently, the surrounding network topology may be as shown in Figure 7.

[0095] In Figure 8, the OTT connection 52 is abstractly depicted to illustrate communication between the host computer 24 and the wireless device 22 via the network node 16, and no intermediate devices or precise routing of messages through these devices are explicitly referenced. The network infrastructure can determine the routing, and the routing can be configured to be hidden from the WD 22, or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure can further make decisions to dynamically change the routing (for example, based on load balancing considerations or network reconfiguration).

[0096] The wireless connection 64 between the WD 22 and the network node 16 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using an OTT connection 52 in which the wireless connection 64 may form the final segment. More precisely, some teachings of these embodiments may improve data rate, latency, and / or power consumption, thereby providing benefits such as reduced user latency, relaxed file size limitations, better responsiveness, and extended battery life.

[0097] In some embodiments, measurement procedures may be provided for the purpose of monitoring data rate, latency, and other factors that one or more embodiments improve. Furthermore, there may be optional network functions for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22 in response to variations in the measurement results. Measurement procedures and / or network functions for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24, or in the software 90 of the WD 22, or both. In some embodiments, sensors (not shown) may be deployed in or in connection with the communication equipment through which the OTT connection 52 passes, and the sensors may participate in the measurement procedures by supplying values ​​of the monitored quantities exemplified above, or by supplying values ​​of other physical quantities that the software 48, 90 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 52 may include message formatting, retransmission settings, preferred routing, etc., and the reconfiguration does not need to affect the network node 16 and may be unknown or imperceptible to the network node 16. Several such procedures and functions are known and can be practiced in the art. In certain embodiments, the measurements may include proprietary WD signaling that facilitates the measurement of the host computer 24's throughput, propagation time, delay time, etc. In some embodiments, the measurements may be carried out in such a way that the software 48, 90 has messages, particularly empty or "dummy" messages, sent using the OTT connection 52 while monitoring propagation time, errors, etc.

[0098] Accordingly, in some embodiments, the host computer 24 includes a processing circuit 42 configured to provide user data and a communication interface 40 configured to transfer the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 is configured to prepare / start / maintain / support / terminate transmissions to the WD 22 and / or to prepare / terminate / maintain / support / terminate transmissions from the WD 22 and / or to perform functions and / or methods described herein, and / or the processing circuit 68 of the network node 16 is configured to perform functions and / or methods described herein.

[0099] In some embodiments, the host computer 24 includes a processing circuit 42 and a communication interface 40 configured to receive user data originating from transmissions from the WD 22 to the network node 16. In some embodiments, the WD 22 is configured to perform functions and / or methods described herein for preparing / starting / maintaining / supporting / terminating transmissions to the network node 16 and / or preparing / terminating / maintaining / supporting / terminating transmissions from the network node 16, and / or includes a wireless interface 82 and / or processing circuit 84.

[0100] Figures 7 and 8 show various "units," such as the configuration unit 32 and the priority unit 34, as being within their respective processors, but these units are intended to be implemented such that parts of the units are stored in corresponding memories within the processing circuit. In other words, the units can be implemented in hardware within the processing circuit, or in a combination of hardware and software.

[0101] Figure 9 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figures 7 and 8, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be those described with reference to Figure 8. In a first step of the method, the host computer 24 provides user data (block S100). In an optional substep of the first step, the host computer 24 provides user data by running a host application, such as host application 50 (block S102). In a second step, the host computer 24 initiates a transmission to carry the user data to the WD 22 (block S104). In an optional third step, the network node 16 transmits the user data carried in the transmission initiated by the host computer 24 to the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (block S106). In an optional fourth step, the WD 22 executes a client application, such as a client application 92 related to a host application 50 executed by the host computer 24 (block S108).

[0102] Figure 10 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figure 7, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be described with reference to Figures 7 and 8. In a first step of the method, the host computer 24 provides user data (block S110). In an optional substep (not shown), the host computer 24 provides user data by running a host application, such as host application 50. In a second step, the host computer 24 initiates a transmission that carries the user data to the WD 22 (block S112). The transmission may pass through the network node 16 as taught in the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (block S114).

[0103] Figure 11 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figure 7, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be those described with reference to Figures 7 and 8. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (block S116). In an optional substep of the first step, the WD 22 runs a client application 92 that provides user data in response to the received input data provided by the host computer 24 (block S118). In an optional second step, the WD 22 provides user data (block S120). In an optional substep of the second step, the WD provides user data by running a client application, such as the client application 92 (block S122). When providing user data, the runnable client application 92 may further consider user input received from the user. Regardless of the specific method by which the user data is provided, the WD 22 may initiate transmission of the user data to the host computer 24 in any third substep (block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22 in accordance with the teachings of the embodiments described throughout this disclosure (block S126).

[0104] Figure 12 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system in Figure 7, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be described with reference to Figures 7 and 8. In an optional first step of the method, the network node 16 receives user data from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (block S132).

[0105] Figure 13 is a flowchart of an exemplary process at network node 16 for omitting channel status information (CSI) for type II CSI. One or more blocks described herein may be executed by one or more elements of network node 16, such as one or more of the processing circuit 68 (including configuration unit 32), processor 70, radio interface 62, and / or communication interface 60. Network node 16, via the processing circuit 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, etc., is configured to receive channel status information CSI reports from WD (block S134). The process also includes, CSI Report This includes determining the priority of ports, layers, and frequency domain (FD) bases based at least in part on the configuration (block S136).

[0106] Figure 14 is a flowchart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as one or more of the processing circuit 84 (including priority unit 34), processor 86, wireless interface 82, and / or communication interface 60. The wireless device 22 is configured to receive channel state information (CSI) configuration from a network node (block S138). The process also includes reporting to the network node a priority for reporting group positions indicating a set of frequency domain (FD) basis vectors and elements of an index representing at least one of the bitmaps for subband amplitude, subband phase, and non-zero coefficients and group positions indicating at least one of the bitmaps for non-zero coefficients, subband amplitude, and phase coefficients (block S140).

[0107] Figure 15 is a flowchart of an exemplary process at network node 16 for omitting channel state information (CSI) for type II CSI. One or more blocks described herein may be executed by one or more elements of network node 16, such as one or more of the processing circuit 68 (including configuration unit 32), processor 70, radio interface 62, and / or communication interface 60. Network node 16 is configured to receive instructions for channel state information (CSI) reporting capability from WD 22 (block S142). The process also includes configuring WD 22 to report frequency domain (FD) basis vector information in one of CSI report group 1 and CSI report group 0, at least in part, based on the indicated CSI reporting capability (block S144).

[0108] In some embodiments, the codebook of a codebook-based CSI is a port selection codebook, and the CSI further comprises an index of multiple selected CSI reference signal (CSI-RS) ports. In some embodiments, the port selection codebook is an extended type II port selection codebook as defined in 3GPP® New Radio Technical Release 17, and WD 22 is configured to report FD basis vector information in CSI report group 0. In some embodiments, the FD basis vector information includes an index indicating a set of selected FD basis vectors. In some embodiments, the CSI further includes information for multiple layers, and the FD basis vector information includes FD basis vector information for each layer of the multiple layers. In some embodiments, the multiple layers, multiple ports, and FD basis vectors are prioritized from highest to lowest in the order of FD basis vectors, ports, and then layers.

[0109] In some embodiments, the CSI further comprises a set of non-zero subband coefficients and an associated non-zero bitmap for each layer, where at least one of the non-zero subband coefficients and a bit of the bitmap associated with the FD basis vector having the minimum index are assigned the highest priority. In some embodiments, each of the non-zero subband coefficients includes amplitude and phase. In some embodiments, the non-zero bitmaps and at least one of the non-zero subband coefficients for all layers are reported in the same CSI report group. In some embodiments, the sets of non-zero bitmaps and non-zero subband coefficients for each of multiple layers are reported in different CSI report groups. In some embodiments, the sets of non-zero subband coefficients and the non-zero bitmaps for the sets of non-zero subband coefficients are reported in one of CSI report groups 1 and 0, at least partially based on priority.

[0110] Figure 16 is a flowchart of an exemplary process in a wireless device 22 according to several embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as one or more of the processing circuit 84 (including priority unit 34), processor 86, wireless interface 82, and / or communication interface 60. The wireless device 22 is configured to receive indications of a codebook-based CSI reporting capability from a WD 22, comprising channel state information (CSI) and information of at least one frequency domain (FD) basis vector (block S146). The process also includes configuring the WD 22 to report the codebook-based CSI in a plurality of CSI report groups having different priorities, where the FD basis vector information is associated with the CSI in the CSI report group having the highest priority among the plurality of CSI report groups (block S148).

[0111] In some embodiments, the method includes reporting FD basis vector information in CSI report group 1 for a Type II port selection codebook as defined in 3GPP® Technical Release 16 (3GPP® Rel-16) and reporting FD basis vector information in CSI report group 0 for a Type II port selection codebook as defined in 3GPP® Technical Release 17 (3GPP® Rel-17). In some embodiments, the FD basis vector information includes an index indicating a selected set of FD basis vectors. In some embodiments, the codebook CSI further includes information for multiple layers, and the FD basis vector information includes FD basis vector information for each layer of the multiple layers. In some embodiments, the layers, multiple ports, and FD basis vectors are prioritized from highest to lowest in the order of FD basis, port, and then layer. In some embodiments, at least one of the non-zero bitmaps and subband coefficients for all layers is reported in the same CSI report group. In some embodiments, at least one of the bitmaps and subband amplitudes and phases for each of the subsets of multiple layers is reported in different CSI report groups. In some embodiments, a set of non-zero subband coefficients and a non-zero bitmap for the set of non-zero subband coefficients are reported in one of CSI report groups 1 and 0, at least partially based on priority.

[0112] While the general process flow of the arrangements of this disclosure has been described and examples of hardware and software arrangements for implementing the processes and functions of this disclosure have been provided, the following sections provide details and examples of arrangements for omitting channel state information (CSI) for type II CSI.

[0113] Report of selected FD basis vectors in Group 0 A problem with the 3GPP® Rel-16 CSI omission rule is that network node 16 may be unable to reconstruct the channel based on incomplete PMI feedback. According to the 3GPP® Rel-16 CSI report grouping and omission rules, the FD basis vectors selected by WD 22 are reported in group 1. In some cases, only group 0, which has the highest priority, is reported (i.e., groups 1 and 2 are omitted), in which case network node 16 will not have information (or incomplete information) about which FD basis vectors are selected by WD 22, which may be essential information for 3GPP® Rel-17 Type II.

[0114] To further illustrate the above, consider the example shown in Figure 17, where four CSI-RS ports are all configured to be WD 22, which should be selected. The four ports are used to cover seven dominant clusters in the propagation channel, indicated as AG. Furthermore, WD 22 is configured to select M=2 FD basis vectors (i.e., delay taps) from an FD window of size N=4 (i.e., four taps enclosed by dashed lines).

[0115] The first two taps (i.e., FD basis vectors 0 and 1) are used by WD 22 to calculate the PMI. If the selected FD basis vectors are unknown to network node 16 because group 1 is omitted, network node 16 cannot calculate the correct DL channel based only on the selected ports in group 0. For example, in the worst case, if network node 16 assumes that FD basis vectors 2 and 3 are used, the DL precoder will completely mismatch the true DL channel, and therefore the signal transmitted using this precoder may be canceled out at WD 22.

[0116] Even if we consider a solution that rotates the selected FD basis vector so that FD basis vector 0 and DC FD components are always selected, as 3GPP(registered trademark) does, it should be noted that network node 16 still cannot grasp the remaining taps if M>1.

[0117] In light of the above, knowledge of the selected FD basis vectors is used by network node 16 to reconstruct the DL channel, even if CSI omission occurs.

[0118] In some embodiments, depending on the report configuration, the group position for indicating the selected FD basis vectors is determined. When a 3GPP® Rel-16 Type II or Type II port selection report is configured, the FD basis vector information is carried on group 1. When a 3GPP® Rel-17 Type II report is configured, the FD basis information is carried on group 0.

[0119] Therefore, WD 22 can report, as a capability, support for 3GPP® Rel-17 and / or 3GPP® Rel-16 Type II reporting. The network configures a preferred Type II reporting mode / release, and based on this information, the network and WD 22 have the same knowledge as to whether the FD basis is in group 1 or group 0.

[0120] In one embodiment, an index for reporting selected FD basis vectors for 3GPP® Rel-17 Type II (e.g., i_1,6 if layer-common FD basis vectors are selected, or i_(1,6,l) for layer l if layer-specific FD basis vectors are selected) is reported in CSI report group 0.

[0121] In another variation of the above embodiment for a 3GPP® Rel-17 Type II report, the index for reporting the selected FD basis vectors (e.g., i_1,6 if a layer common FD basis vector is selected, or i_(1,6,l) for layer l if a layer-specific FD basis vector is selected) is encoded in PMI field X_1 as defined in 3GPP® TS 38.212 V 16.0.0 and reported in CSI report group 0.

[0122] Reporting the selected FD basis vectors in group 0 is possible when the selected FD basis vectors are common to the layers and the overhead is N=4 and M=2, at most Note that TIFF0007848312000040.tif can be 1046 bits, so it imposes only a slight increase in overhead for group 0.

[0123] Priority function reordering The existing 3GPP® Rel-16 Type II priority function for CSI omission does not have proper ordering with respect to port, FD basis vector, and layer priorities, as will be further explained below.

[0124] For a 3GPP® Rel-16 Type II report, a given CSI report is indexed by l,i,f. 2,4,l (Subband amplitude), i 2,5,l (Subband phase), and i 1,7,l Each reported element (in the bitmap) is such that ν is the layer index, ν is the RI, i=0,1,...,2L-1 is the index of the selected port, and f=0,1,...,M ν -1 is the index of the selected FD basis vector, and M ν This is the number of indices of the FD basis vectors selected for each layer, TIFF0007848312000041.tif1163 is where WD 22 is the index of the selectable FD basis vectors, N3 is the number of PMI subbands, and l = 1, 2, ... ν. Function of TIFF0007848312000042.tif13113 This is associated with the priority value given by TIFF0007848312000043.tif10101. The element with the highest priority has the lowest associated value Pri(l,i,f). Given the possible parameter configurations in Table 1 for Type II of 3GPP® Rel-16, it can be observed that priority is given from layer to port to FD base, as high-to-low priority is not appropriate considering the importance of the selected FD base.

[0125] Based on the above discussion, the indices of the selected FD basis vectors should be associated with higher priorities in the 3GPP® Rel-17 Type II priority function.

[0126] Some embodiments provide configurations for priority processing in a priority function when a Type II of 3GPP® Rel-17 is configured.

[0127] In one embodiment, the highest-to-lowest prioritization in 3GPP® Rel-17 Type II may be from FD base to port-to-layer.

[0128] In another embodiment, the highest-to-lowest prioritization in 3GPP® Rel-17 Type II may be FD base-to-layer-to-port.

[0129] Some embodiments are based on the report configuration PriorityThis is determined by configuring a 3GPP® Rel. 16 Type II or 3GPP® Rel 16 Type II port selection CSI report, and then determining the highest-to-lowest priority order in layer, port, and FD-based order. If a 3GPP® Rel-17 Type II report is configured, the highest-to-lowest priority order is determined according to one of the following: • Priority determined by the order of FD base, port, and layer. The priority order is determined as follows: port, FD base, and layer.

[0130] Therefore, WD 22 can report its capability to support Type II reports for 3GPP® Rel-17 and / or 3GPP® Rel-16. The network configures a preferred Type II report mode / release, and based on this information, the network and WD 22 have the same knowledge of the priority for CSI omission.

[0131] Another issue with the Type II priority function in 3GPP® Rel-16 is that FD basis vectors close to the zeroth FD basis vector have higher priority in a cyclical manner inferred from the value of π(f). This is no longer true for Type II in 3GPP® Rel-17 as it imposes greater complexity on WD 22 implementations.

[0132] Some embodiments provide solutions for handling the prioritization of selected FD basis vectors.

[0133] In one embodiment, subband coefficients or bitmaps associated with FD basis vectors having smaller indices have higher priority; for example, a bitmap or subband coefficient for FD basis vector 0 has higher priority than a bitmap or subband coefficient for FD basis vector 1.

[0134] In the modified embodiment described above, the FD basis vector shift is applied first so that the strongest coefficient indicator (SCI) is associated with the 0th FD basis vector. Therefore, subband coefficients or bitmaps associated with FD basis vectors with smaller indices have higher priority; for example, the bitmap or subband coefficient for FD basis vector 0 has higher priority than the bitmap or subband coefficient for FD basis vector 1.

[0135] Grouping of amplitude and phase of bitmaps and subbands In 3GPP® Rel-16 Type II, even with FD compression employed, subband PMI reports can still be heavy on payload. One reason for this is that the number of FD basis vectors used to compress the FD channels is proportional to the number of PMI subbands, which potentially increases the total number of coefficients reported for large bandwidths.

[0136] Therefore, in 3GPP® Rel-16, the information PMI field X2 is encoded, for example, as defined in 3GPP® TS 38.212 V16.0.0, and the non-zero coefficient (NZC) i 1,7,l , subband coefficient amplitude i 2,4,l and phase i 2,5,l The subband PMI, including the bitmaps used to indicate the subband amplitude and phase, is segmented into two groups, namely Group 1 and Group 2. The higher-priority portions of the bitmaps and subband amplitude and phase, calculated based on the 3GPP® Rel-16 Type II priority function, are reported in Group 1, while the remaining portions of the bitmaps and subband amplitude and phase are reported in Group 2.

[0137] Since the UCI payload can be significantly reduced compared to the payload of 3GPP® Rel-16 Type II, the above grouping may not be necessary in 3GPP® Rel-17 Type II. For example, the number of reported subband coefficients is no longer proportional to the bandwidth. Therefore, it is reasonable to have a unified subband report to reduce the complexity of encoding / decoding the CSI report. When 3GPP® Rel-17 Type II is configured, several solutions are provided for grouping the bitmap and the amplitude and phase of the subband amplitudes. In one embodiment, the complete bitmap is reported in the same CSI group, e.g., Group 1.

[0138] In another embodiment, both the amplitude and phase of the complete bitmap and subbands are reported in the same CSI group, for example, group 1.

[0139] Grouping by layer index Since layers may have the lowest priority in 3GPP® Rel-17 Type II, the grouping of CSI reports can also be reprocessed based on the layer index. This makes sense because network node 16 should still be able to recover parts of the CSI based on PMI reports for subsets of layers. Several embodiments provide solutions for grouping NZC bitmaps and subband amplitudes and phases in Part 2 CSI when 3GPP® Rel-17 Type II is configured.

[0140] In one embodiment, part 2 of the CSI report is segmented into v groups, where v is the rank indicator (RI). The NZC bitmap and subband amplitude and phase of each layer are reported in a distinct group (for example, the amplitude and phase of layer v are reported in CSI group v).

[0141] In another embodiment, Part 2 of the CSI report is segmented into two groups, each group containing the amplitude and phase of NZC bitmaps and subbands for a predefined subset of layers (e.g., specified by 3GPP®). For example, Group 1 contains those for layers 1 and 2, and Group 2 contains those for layer 3.

[0142] In some embodiments, depending on the report configuration, group positions are determined for displaying bitmaps of non-zero coefficients, subband amplitudes, and phase coefficients. When a 3GPP® Rel.16 Type II or Type II port selection report is configured, the bitmaps of non-zero coefficients, subband amplitudes, and phase coefficients are segmented into two groups, with the portions of the bitmaps of non-zero coefficients, subband amplitudes, and phases that have a higher priority calculated based on the 3GPP® Rel-16 Type II priority function being reported in Group 1, and the remaining portions of the bitmaps of subband amplitudes and phases being reported in Group 2.

[0143] When a Type II report of 3GPP® Rel-17 is constructed, the group position for showing bitmaps for non-zero coefficients, subband amplitudes, and / or phase coefficients may be determined according to one of the following non-limiting examples: Bitmaps with non-zero coefficients are reported as a single group. • Bitmaps of non-zero coefficients, subband amplitudes, and phase coefficients are reported within the same CSI group, and / or The bitmaps of non-zero coefficients, subband amplitudes, and phase coefficients for a given layer are reported within the same CSI group, and each CSI group contains bitmaps of non-zero coefficients, subband amplitudes, and phase coefficients for one or more layers.

[0144] Therefore, WD can report as capable of supporting Type II reporting for 3GPP® Rel-17 and / or 3GPP® Rel.16. The network constitutes a preferred Type II reporting mode / release, and based on this information, the network and WD 22 have the same knowledge of bitmap grouping information for non-zero coefficients, subband amplitude and phase coefficients.

[0145] Some embodiments include some or all of the following:

[0146] Embodiment 1. A method for CSI reporting, Step 1: WD22 receives the configuration for Type II CSI reporting in the CSI reporting configuration.

[0147] Step 2: WD22 calculates the CSI based on the received configuration of the Type II CSI report.

[0148] Step 3: WD22 determines the type of Type II CSI based on its configuration, reporting at least one of the following: Group positions in Part 2 of the CSI to indicate the selected FD basis vectors; Priority for reporting the subband amplitude, subband phase, and index elements representing the bitmap for non-zero coefficients; Group positions for showing bitmaps of non-zero coefficients, subband amplitudes and / or phase coefficients, and / or Step 4: WD22 reports the CSI based on the determination in Step 3.

[0149] Embodiment 2. The method of Embodiment 1, wherein the type of Type II CSI reporting is configured to be 3GPP® Rel-16 Type II (i.e., Extended Type II Codebook) or 3GPP® Rel-16 Type II Port Selection (i.e., Extended Type II Port Selection Codebook), the FD basis vector information is carried within a second group (i.e., Group 1) in Part 2 of the CSI. Here, when the type of Type II CSI report is configured as Type II of 3GPP® Rel-17, the FD basis vector information is transported in the first group (i.e., group 0) in Part 2 of the CSI, by method.

[0150] Embodiment 3. The method of Embodiment 1, in which the type of Type II CSI reporting constitutes 3GPP® Rel-16 Type II (i.e., Extended Type II Codebook) or 3GPP® Rel-16 Type II Port Selection (i.e., Extended Type II Port Selection Codebook), the highest to lowest priority is determined in the order of layer, port, and FD base. Here, when the type of a Type II CSI report is configured as Type II in 3GPP® Rel-17, the priority order from highest to lowest is: Priority determined by the order of FD base, port, and layer, or Priority determined in the order of port, FD base, layer. A method determined according to one of the following.

[0151] Embodiment 4. The method of Embodiment 1, wherein when the type of Type II CSI report is configured as 3GPP® Rel-16 Type II (i.e., Extended Type II Codebook) or 3GPP® Rel-16 Type II Port Selection (i.e., Extended Type II Port Selection Codebook), the bitmaps of non-zero coefficients, subband amplitudes and phase coefficients are divided into two groups, with a portion of the bitmaps of non-zero coefficients, subband amplitudes and phases being reported in a second group (i.e., Group 1) in Part 2 of the CSI, while the remaining portion of the bitmaps and subband amplitudes and phases is reported in a third group (i.e., Group 2) in Part 2 of the CSI; and when the type of Type II CSI report is configured as 3GPP® Rel-17 Type II, the group positions for showing the bitmaps of non-zero coefficients, subband amplitudes and / or phase coefficients are, Bitmaps for non-zero coefficients are reported in a single group in Part 2 of the CSI. Bitmaps of non-zero coefficients, subband amplitudes, and phase coefficients are reported in the same group in Part 2 of the CSI, and / or Bitmaps of non-zero coefficients, subband amplitudes, and phase coefficients for a given layer are reported within the same CSI group, and each CSI group contains bitmaps of non-zero coefficients, subband amplitudes, and phase coefficients for one or more layers. A method determined according to one of the following.

[0152] In one embodiment, the network node 16 is configured to communicate with a wireless device 22 (WD 22). The network node 16 includes a wireless interface 62 and / or processing circuit 68 configured to receive a channel status information (CSI) report from the WD 22 and to determine port, layer, and frequency domain (FD) basis priorities based at least in part on the configuration of the CSI report.

[0153] According to this embodiment, in some embodiments, the priority order is FD base, port, then layer. In some embodiments, the priority order is port, FD base, then layer. In some embodiments, the priority order is layer, port, then FD base. In some embodiments, In another embodiment, a method implemented at the network node 16 includes receiving a channel status information (CSI) report from the WD 22 and determining port, layer, and frequency domain (FD) basis priorities based at least in part on the configuration of the CSI report.

[0154] According to this embodiment, in some embodiments, the priority order is FD base, port, then layer. In some embodiments, the priority order is port, FD base, then layer. In some embodiments, the priority order is layer, port, then FD base.

[0155] In yet another embodiment, the wireless device (WD) 22 is configured to communicate with a network node 16. The WD 22 includes a wireless interface 82 and / or processing circuit 84 configured to receive channel state information (CSI) configuration from the network node 16 and report to the network node 16 at least one of the following: a group position for indicating a set of frequency domain (FD) basis vectors; a priority for reporting elements of an index representing at least one of a bitmap for subband amplitude, subband phase, and non-zero coefficients; and a group position for indicating at least one of a bitmap for non-zero coefficients, subband amplitude, and phase coefficients.

[0156] In this embodiment, when a Type II CSI report is comprised of one of an Extended Type II Codebook and an Extended Type II Port Selection Codebook, FD basis vector information is carried in a second group within Part 2 of the CSI. In some embodiments, FD basis vector information is carried in a first group within Part 2 of the CSI. In some embodiments, a Type II CSI report includes FD basis vectors, priority in the order of ports, then layers, and at least one of ports, FD basis vectors, then layer priority.

[0157] In another embodiment, a method implemented in a wireless device (WD 22) includes receiving a channel state information (CSI) configuration from a network node 16 and reporting to the network node 16 at least one of the following: a group position for indicating a set of frequency domain (FD) basis vectors; a priority for reporting elements of an index representing at least one of a bitmap for subband amplitude, subband phase, and non-zero coefficients; and a group position for indicating at least one of a bitmap for non-zero coefficients, subband amplitude, and phase coefficients.

[0158] In this embodiment, in some embodiments, when the Type II CSI report is comprised of one of the Extended Type II Codebook and the Extended Type II Port Selection Codebook, the FD basis vector information is carried in a second group of Part 2 of the CSI. In some embodiments, the FD basis vector information is carried in a first group of Part 2 of the CSI. In some embodiments, the Type II CSI report includes FD basis vectors, priority in the order of ports and then layers, and at least one of ports, FD basis vectors and then priority in the order of layers. Some examples Example A1. A network node 16 configured to communicate with a wireless device 22 (WD 22), Received a Channel Status Information (CSI) report from WD 22. Prioritize ports, layers, and frequency domain (FD) bases based at least partially on the structure of the CSI report. A network node 16 having a wireless interface 62 configured as such, and / or a processing circuit 68 configured as such.

[0159] Example A2. The priority order is FD base, port, then layer, as in network node 16 of Example A1.

[0160] Example A3. The priority order is port, FD base, then layer, as in network node 16 of Example A1.

[0161] Example A4. The priority order is layer, port, then FD base, as in network node 16 of Example A1.

[0162] Example B1. A method implemented within network node 16, Receiving Channel Status Information (CSI) reports from WD 22, Based at least partially on the configuration of the CSI report, the prioritization of ports, layers, and frequency domain (FD) basis is determined, Methods that include...

[0163] Example B2. The priority order is FD base, port, then layer, as in Example B1.

[0164] Example B3. The priority order is port, FD base, then layer, as in Example B1.

[0165] Example B4. The priority order is layer, port, then FD base, as in Example B1.

[0166] Example C1. A wireless device 22 (WD 22) configured to communicate with a network node 16, Receive channel status information CSI configuration from network node 16. To network node 16, Group positions to indicate the set of frequency-domain (FD) basis vectors, Priority for reporting the elements of an index representing at least one of the subband amplitude, subband phase, and bitmap for non-zero coefficients, A group position to show at least one of the bitmaps for non-zero coefficients, subband amplitude, and phase coefficients, Report at least one of the following: The WD 22 is configured such as and / or includes a configured wireless interface 82 and / or a configured processing circuit 84.

[0167] Example C2. In the case of WD 22 of Example C1, where the type of the Type II CSI report is configured to be one of the Extended Type II Codebook and the Extended Type II Port Selection Codebook, the FD basis vector information is carried in the second group in Part 2 of the CSI, WD 22.

[0168] Example C3. WD 22 of Example C2, where the FD basis vector information is carried in the first group in Part 2 of the CSI, WD 22.

[0169] Example C4. WD 22 of Examples C1-C3, wherein the type of Type II CSI report includes FD basis vectors, ports, then layer order priority, and at least one of ports, FD basis vectors, then layer order priority.

[0170] Example D1. A method implemented in wireless device 22 (WD 22), Receiving channel status information (CSI) configuration from network node 16, To network node 16, Group positions to indicate the set of frequency-domain (FD) basis vectors, Priority for reporting the elements of an index representing at least one of the subband amplitude, subband phase, and bitmap for non-zero coefficients, A group position to show at least one of the bitmaps for non-zero coefficients, subband amplitude, and phase coefficients, Report at least one of the following, Methods that include...

[0171] Example D2. The method of Example D1, wherein the type of the Type II CSI report consists of one of the Extended Type II Codebook and the Extended Type II Port Selection Codebook, and the FD basis vector information is carried in the second group in Part 2 of the CSI.

[0172] Example D3. A method of Example D2, wherein the FD basis vector information is carried in the first group in Part 2 of the CSI.

[0173] Example D4. A method of the methods of Examples D1-D3, wherein the type of Type II CSI report includes at least one of FD basis vectors, ports, then priority in the order of layers, and ports, FD basis vectors, then priority in the order of layers.

[0174] As will be understood by those skilled in the art, the concepts described herein can be embodied as methods for storing executable computer programs, data processing systems, computer program products, and / or computer storage media. Thus, the concepts described herein can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects, all of which are generally referred to herein as “circuits” or “modules,” and any process, step, action, and / or function described herein may be executed and / or associated therewith by a corresponding module which may be implemented in software and / or firmware and / or hardware. Furthermore, this disclosure can take the form of computer program products on tangible computer-readable storage media having computer program code embodied in a medium executable by a computer. Any suitable tangible computer-readable medium may be utilized, including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0175] Several embodiments are described herein with reference to flowcharts and / or block diagrams of methods, systems, and computer program products. It will be understood that each block in a flowchart and / or block diagram, as well as any combination of blocks in a flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer processor (thus creating a dedicated computer), a dedicated computer, or other programmable data processing device, so that instructions executed via the processor of the computer or other programmable data processing device can create means to perform functions / operations specified in the flowchart and / or block diagram blocks or blocks.

[0176] These computer program instructions may also be stored in computer-readable memory or storage medium that can instruct a computer or other programmable data processing device to function in a particular way, resulting in a product that includes instruction means for implementing specified functions / operations in flowcharts and / or block diagram blocks or blocks.

[0177] Computer program instructions can also be loaded onto a computer or other programmable data processing device to generate a computer implementation process by causing the computer or other programmable data processing device to execute a series of operational steps so that the instructions executed on the computer or other programmable device provide steps for performing a function / operation specified in a block or block of a flowchart and / or block diagram.

[0178] Please understand that the functions / actions described in a block may occur outside the order shown in the operation diagram. For example, two blocks shown consecutively may actually be executed substantially simultaneously, or they may be executed in reverse order depending on the function / action the blocks are involved in. Some diagrams include arrows on the communication path to indicate the main direction of communication, but please understand that communication may occur in the opposite direction to the depicted arrow.

[0179] Computer program code for performing the operations of the concepts described herein may be written in an object-oriented programming language such as Python, Java®, or C++. However, computer program code for performing the operations of the disclosure may also be written in a conventional procedural programming language such as the C programming language. The program code can run entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer, partially on a remote computer, or entirely on a remote computer. In the latter scenario, the remote computer may be connected to the user's computer via a local area network (LAN) or wide area network (WAN), or it may be connected to an external computer (for example, via the Internet using an Internet service provider).

[0180] This specification has disclosed many different embodiments in connection with the above description and drawings. It will be understood that a literal description and illustration of all combinations and subcombinations of these embodiments would be excessively repetitive and obfuscated. Therefore, all embodiments can be combined in any way and / or combination, and this specification, including the drawings, shall be construed as constituting a description by specification of all combinations and subcombinations of the embodiments described herein, as well as methods and processes for making and using them, and shall support the claims for any such combination or subcombination.

[0181] Those skilled in the art will understand that the embodiments described herein are not limited to those specifically shown and described above. In addition, it should be noted that, unless otherwise stated above, all accompanying drawings are not to a constant scale. Various modifications and variations are possible in light of the above teachings without departing from the following claims.

Claims

1. A method in a network node (16) configured to communicate with a wireless device (WD(22)), Transmitting a configuration to the WD(22) for reporting codebook-based channel state information (CSI) including information on at least one frequency domain (FD) basis vector, Multiple CSI report groups receive the codebook-based CSI from the WD(22), In relation to the Type II port selection codebook defined in the Third Generation Partnership Project Technical Release 16 (3GPP® Release 16), the CSI report group 1 receives the FD basis vector information, In relation to the Type II port selection codebook defined in 3GPP® Technical Release 17 (3GPP® Release 17), the CSI report group 0 receives the FD basis vector information, Includes, A method for determining which CSI report groups contain information indicating selected FD basis vectors, based on the CSI report configuration.

2. A method according to claim 1, wherein the FD basis vector information includes an index indicating a selected set of FD basis vectors.

3. A method according to Claim 1, wherein the CSI further comprises a set of non-zero subband coefficients for each layer and an associated non-zero bitmap, wherein at least one of the non-zero subband coefficients and the bits of the bitmap associated with the FD basis vector having the smallest index is assigned the highest priority.

4. A method according to claim 3, wherein each of the non-zero subband coefficients comprises amplitude and phase.

5. A method according to claim 1, wherein the CSI further includes information for a plurality of layers, and the FD basis vector information includes FD basis vector information for each of the plurality of layers.

6. A network node (16) configured to communicate with a wireless device (WD(22)), A network node (16) comprising a wireless interface (62) and / or processing circuit (68) configured to perform all steps of the method according to any one of claims 1 to 5.

7. A method in which a wireless device (WD(22)) is configured to communicate with a network node (16), Receiving a configuration for reporting codebook-based channel state information (CSI) that includes frequency domain (FD) basis vector information (S146), Based on the CSI report configuration, determine the CSI report group that contains information indicating the selected FD basis vectors, Reporting the codebook-based CSI in multiple CSI report groups (S148), In the Third Generation Partnership Project Technical Release 16 (3GPP® Release 16), the CSI report group 1 reports the aforementioned FD basis vector information for the Type II port selection codebook, In relation to the Type II port selection codebook defined in 3GPP® Technical Release 17 (3GPP® Release 17), the FD basis vector information is reported in CSI report group 0, Methods that include...

8. The method according to claim 7, wherein the FD basis vector information includes an index indicating a selected set of FD basis vectors.

9. The method according to claim 7, wherein the codebook-based CSI further includes information for a plurality of layers, and the FD basis vector information includes FD basis vector information for each of the plurality of layers.

10. A method according to claim 7, wherein the CSI further comprises a set of non-zero subband coefficients for each layer and an associated non-zero bitmap, wherein at least one of the non-zero subband coefficients and the bits of the bitmap associated with the FD basis vector having the smallest index is assigned the highest priority.

11. A method according to claim 10, wherein each of the non-zero subband coefficients comprises amplitude and phase.

12. A wireless device (WD(22)) configured to communicate with a network node (16), A WD (22) comprising a wireless interface (82) and / or processing circuit (84) configured to perform all steps of the method according to any one of claims 7 to 11.

Images