CSI compression

Abstract

Various aspects of the disclosure relate to user equipment, base stations, processors, and methods for CSI compression. In one aspect, a user equipment (UE) sends a base station capability information on channel state information (CSI) compression using a bilateral model. The UE receives from the base station at least one configuration corresponding to at least one CSI compression model for obtaining a compressed CSI report accordingly. The UE receives from the base station an indication corresponding to a first CSI compression model of the at least one CSI compression model, the first CSI compression model being associated with a CSI report configuration.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically to user equipment (UE), base stations, processors, and methods for channel state information (CSI) compression. Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as base stations, which may also be referred to as eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UEs), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, the wireless communication system may also support wireless communication across various radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies after 5G (e.g., sixth-generation (6G)).

[0003] CSI reporting based on CSI compression using bilateral models (such as artificial intelligence (AI) / machine learning (ML) models) has been introduced. CSI reporting based on CSI compression using bilateral models can provide performance gains in most use cases. However, some unresolved issues related to CSI compression based on bilateral models remain and require further investigation. Summary of the Invention

[0004] This disclosure relates to methods, apparatus, and systems that support CSI compression.

[0005] In a first aspect of this solution, a user equipment (UE) may include: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: transmit via the transceiver to a base station capability information regarding channel state information (CSI) compression using a bilateral model; receive via the transceiver from the base station at least one configuration corresponding to at least one CSI compression model for obtaining compressed CSI reports; and receive via the transceiver from the base station an indication corresponding to a first CSI compression model among the at least one CSI compression model, the first CSI compression model being associated with a CSI report configuration.

[0006] In some implementations of the methods and apparatus described herein, at least one CSI compression model can be determined by the base station based on capability information.

[0007] In some implementations of the methods and apparatus described herein, the capability information may be determined by the UE by UE, by frequency band, or by a combination of frequency bands.

[0008] In some implementations of the methods and apparatus described herein, capability information may include: first information regarding whether CSI compression using a bilateral model is supported by the UE.

[0009] In some implementations of the methods and apparatus described herein, when CSI compression using a bilateral model is supported by the UE, the capability information may further include: the number of CSI compression models supported by the UE; second information regarding whether at least one of the rank-based CSI reports and layer-based CSI reports is supported by the UE; the maximum rank supported by the CSI compression report for each CSI compression function or for each CSI compression model, wherein the CSI compression function is associated with one or more CSI compression models; and third information regarding the number of uplink control information (UCI) bits used for the compressed CSI report.

[0010] In some implementations of the methods and apparatus described herein, when rank-based CSI reporting is supported by the UE, the third information may include: for each CSI compression function or for each CSI compression model, the number of UCI bits for the compressed CSI report corresponding to each rank; and when layer-based CSI reporting is supported by the UE, the third information may include: for each CSI compression function or for each CSI compression model, the number of UCI bits for the compressed CSI report corresponding to each transport layer.

[0011] In some implementations of the methods and apparatus described herein, where the rank-based CSI reporting is supported by the UE, the third information may include one or more candidate values ​​regarding the number of UCI bits for each rank.

[0012] In some implementations of the methods and apparatus described herein, the configuration in the at least one configuration may include: an identifier (ID) corresponding to the CSI compression model; the maximum rank supported by the compressed CSI report for the CSI compression model; the number of uplink control information (UCI) bits for the compressed CSI report corresponding to each rank when rank-based CSI reporting is configured; and the number of UCI bits for the compressed CSI report corresponding to each transport layer when layer-based CSI reporting is configured.

[0013] In some implementations of the methods and apparatus described herein, the indication may include a CSI compression model identifier (ID) of a first CSI compression model, and the first CSI compression model is activated.

[0014] In some implementations of the methods and apparatus described herein, when the CSI report configuration corresponds to periodic CSI reports, the indication can be specified in the CSI report configuration via Radio Resource Control (RRC) signaling; when the CSI report configuration corresponds to semi-persistent (SP) CSI reports on the Physical Uplink Control Channel (PUCCH), the indication can be specified in the CSI report configuration via RRC signaling, or in the first Media Access Control (MAC) control element (CE) used to activate SP CSI reports on the PUCCH; when the CSI report configuration corresponds to SP CSI reports on the Physical Uplink Shared Channel (PUSCH), the indication can be specified in the CSI report configuration via RRC signaling, or in the downlink control information (DCI) field included in the DCI used to activate SP CSI reports on the PUSCH; or when the CSI report configuration corresponds to non-periodic CSI reports, the indication can be specified in the CSI report configuration via RRC signaling, or in the second MAC... It is specified in CE, or may be specified in the DCI field included in the DCI used to trigger non-periodic CSI reporting.

[0015] In some implementations of the methods and apparatus described herein, the processor may also be configured to: update the first CSI compression model using a second CSI compression model when a third Media Access Control (MAC) control element (CE) is received from the base station, wherein the third MAC CE includes an ID of a CSI report configuration and an ID of a second CSI compression model associated with the CSI report configuration, and the second CSI compression model is activated by the base station.

[0016] In some implementations of the methods and apparatus described herein, the processor may also be configured to: determine a CSI report corresponding to the CSI report configuration.

[0017] In some implementations of the methods and apparatus described herein, when the CSI report is a rank-based CSI report, the CSI report may include at least: a rank indicator (RI) field and a single field for a compressed CSI corresponding to the RI indicated in the RI field; and when the CSI report is a layer-based CSI report, the CSI report may include at least: an RI field and multiple fields, wherein each of the multiple fields indicates a compressed CSI corresponding to each layer in the layer indicated by the RI field.

[0018] In some implementations of the methods and apparatus described herein, when the CSI report is a rank-based CSI report, the CSI report may include at least: a CSI Reference Signal (RS) Resource Indicator (CRI) field, an RI field, and a Precoding Matrix Indicator (PMI) portion, the PMI portion including compressed CSI or back-back CSI corresponding to the RI indicated in the RI field; and when the CSI report is a layer-based CSI report, the CSI report may include at least: a CRI field, an RI field, a Layer Indicator (LI) field, and a PMI portion, the PMI portion including compressed CSI or back-back CSI corresponding to each layer of the RI indicated in the RI field.

[0019] In some implementations of the methods and apparatus described herein, the fallback CSI can be acquired based on predetermined reporting information included in the CSI reporting configuration and on the same resources configured for the CSI reporting configuration used for channel and / or interference measurements.

[0020] In some implementations of the methods and apparatus described herein, the CSI report may also include a rollback indicator that indicates whether compressed or rolled-back CSI is included in the CSI report.

[0021] In some implementations of the methods and apparatus described herein, the size of the PMI portion can be determined by the maximum number of UCI bits used for compressed CSI reports corresponding to the CSI report configuration and the number of UCI bits used for rollback of CSI reports.

[0022] In some implementations of the methods and apparatus described herein, in the absence of resources available for the first CSI compression model, the processor may also be configured to: discard the CSI report; or discard the PMI portion of the CSI report and send a CSI report without the PMI portion to the base station.

[0023] In some implementations of the methods and apparatus described herein, in the absence of resources available for the first CSI compression model, a fallback indicator may indicate that the fallback CSI is included in the CSI report.

[0024] In a second aspect of this solution, the base station may include: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver, capability information regarding channel state information (CSI) compression using a bilateral model from a user equipment (UE); transmit via the transceiver at least one configuration corresponding to at least one CSI compression model for obtaining compressed CSI reports to the UE; and transmit via the transceiver to the UE an indication corresponding to a first CSI compression model among the at least one CSI compression model, the first CSI compression model being associated with a CSI report configuration.

[0025] In some implementations of the methods and apparatus described herein, at least one CSI compression model can be determined by the base station based on capability information.

[0026] In some implementations of the methods and apparatus described herein, the capability information may be determined by the UE by UE, by frequency band, or by a combination of frequency bands.

[0027] In some implementations of the methods and apparatus described herein, the capability information may include: first information regarding whether CSI compression using a bilateral model is supported by the UE.

[0028] In some implementations of the methods and apparatus described herein, when CSI compression using a bilateral model is supported by the UE, the capability information may further include: the number of CSI compression models supported by the UE; second information regarding whether at least one of the rank-based CSI reports and layer-based CSI reports is supported by the UE; the maximum rank supported by the CSI compression report for each CSI compression function or for each CSI compression model, wherein the CSI compression function is associated with one or more CSI compression models; and third information regarding the number of uplink control information (UCI) bits used for the compressed CSI report.

[0029] In some implementations of the methods and apparatus described herein, when rank-based CSI reporting is supported by the UE, the third information may include: for each CSI compression function or for each CSI compression model, the number of UCI bits for the compressed CSI report corresponding to each rank; and when layer-based CSI reporting is supported by the UE, the third information may include: for each CSI compression function or for each CSI compression model, the number of UCI bits for the compressed CSI report corresponding to each transport layer.

[0030] In some implementations of the methods and apparatus described herein, where the rank-based CSI reporting is supported by the UE, for each rank, the third information may include one or more candidate values ​​regarding the number of UCI bits for each rank.

[0031] In some implementations of the methods and apparatus described herein, the configuration in the at least one configuration may include: an identifier (ID) corresponding to the CSI compression model; the maximum rank supported by the compressed CSI report for the CSI compression model; the number of uplink control information (UCI) bits for the compressed CSI report corresponding to each rank when rank-based CSI reporting is configured; and the number of UCI bits for the compressed CSI report corresponding to each transport layer when layer-based CSI reporting is configured.

[0032] In some implementations of the methods and apparatus described herein, the indication may include a CSI compression model identifier (ID) of a first CSI compression model, and the first CSI compression model is activated.

[0033] In some implementations of the methods and apparatus described herein, when the CSI report configuration corresponds to periodic CSI reports, the indication can be specified in the CSI report configuration via Radio Resource Control (RRC) signaling; when the CSI report configuration corresponds to semi-persistent (SP) CSI reports on the Physical Uplink Control Channel (PUCCH), the indication can be specified in the CSI report configuration via RRC signaling, or in the first Media Access Control (MAC) control element (CE) used to activate SP CSI reports on the PUCCH; when the CSI report configuration corresponds to SP CSI reports on the Physical Uplink Shared Channel (PUSCH), the indication can be specified in the CSI report configuration via RRC signaling, or in the downlink control information (DCI) field included in the DCI used to activate SP CSI reports on the PUSCH; or when the CSI report configuration corresponds to non-periodic CSI reports, the indication can be specified in the CSI report configuration via RRC signaling, or in the second MAC... It is specified in CE, or may be specified in the DCI field included in the DCI used to trigger non-periodic CSI reporting.

[0034] In some implementations of the methods and apparatus described herein, the processor may also be configured to: send a third Media Access Control (MAC) control element (CE) to the UE via a transceiver to update the first CSI compression model using a second CSI compression model, wherein the third MAC CE includes an ID of a CSI report configuration and an ID of a second CSI compression model associated with the CSI report configuration, and the second CSI compression model is activated by a base station.

[0035] In some implementations of the methods and apparatus described herein, the processor may also be configured to receive a CSI report corresponding to a CSI report configuration.

[0036] In some implementations of the methods and apparatus described herein, when the CSI report is a rank-based CSI report, the CSI report may include at least: a rank indicator (RI) field and a single field for a compressed CSI corresponding to the RI indicated in the RI field; and when the CSI report is a layer-based CSI report, the CSI report may include at least: an RI field and multiple fields, wherein each of the multiple fields indicates a compressed CSI corresponding to each layer in the layer indicated by the RI field.

[0037] In some implementations of the methods and apparatus described herein, when the CSI report is a rank-based CSI report, the CSI report may include at least: a CSI Reference Signal (RS) Resource Indicator (CRI) field, an RI field, and a Precoding Matrix Indicator (PMI) portion, the PMI portion including compressed CSI or back-back CSI corresponding to the RI indicated in the RI field; and when the CSI report is a layer-based CSI report, the CSI report may include at least: a CRI field, an RI field, a Layer Indicator (LI) field, and a PMI portion, the PMI portion including compressed CSI or back-back CSI for each layer corresponding to the RI indicated in the RI field.

[0038] In some implementations of the methods and apparatus described herein, the fallback CSI can be acquired based on predetermined reporting information included in the CSI reporting configuration and on the same resources configured for the CSI reporting configuration used for channel and / or interference measurements.

[0039] In some implementations of the methods and apparatus described herein, the CSI report may also include a rollback indicator that indicates whether compressed or rolled-back CSI is included in the CSI report.

[0040] In some implementations of the methods and apparatus described herein, the size of the PMI portion may be determined by the maximum number of UCI bits used for the compressed CSI report corresponding to the CSI report configuration and the number of UCI bits used for rolling back the CSI report.

[0041] In some implementations of the methods and apparatus described herein, in the absence of resources available for the first CSI compression model, the processor may also be configured to: discard the CSI report; or discard the PMI portion of the CSI report and send a CSI report without the PMI portion to the base station.

[0042] In some implementations of the methods and apparatus described herein, in the absence of resources available for the first CSI compression model, a fallback indicator may indicate that the fallback CSI is included in the CSI report.

[0043] In a third aspect of this solution, a processor for wireless communication may include: at least one memory; and a controller coupled to the at least one memory and configured such that the processor: transmits to a base station via a transceiver capability information regarding channel state information (CSI) compression using a bilateral model; receives from the base station via the transceiver at least one configuration corresponding to at least one CSI compression model for obtaining compressed CSI reports; and receives from the base station via the transceiver an indication of a first CSI compression model among the at least one CSI compression model, the first CSI compression model being associated with a CSI report configuration.

[0044] In a fourth aspect of this solution, a method performed by a user equipment (UE) may include: transmitting capability information regarding channel state information (CSI) compression using a bilateral model to a base station via a transceiver; receiving, via the transceiver, from the base station at least one configuration corresponding to at least one CSI compression model for obtaining compressed CSI reports; and receiving, via the transceiver, from the base station an indication corresponding to a first CSI compression model among the at least one CSI compression model, the first CSI compression model being associated with a CSI report configuration.

[0045] In a fifth aspect of this solution, the processor for wireless communication may include: at least one memory; and a controller coupled to the at least one memory and configured such that the processor: receives from a user equipment (UE) via a transceiver capability information regarding channel state information (CSI) compression using a bilateral model; transmits to the UE via the transceiver at least one configuration corresponding to at least one CSI compression model for obtaining compressed CSI reports; and transmits to the UE via the transceiver an indication corresponding to a first CSI compression model among the at least one CSI compression model, the first CSI compression model being associated with a CSI report configuration.

[0046] In a sixth aspect of this solution, a method performed by a base station may include: receiving, via a transceiver, capability information regarding channel state information (CSI) compression using a bilateral model from a user equipment (UE); correspondingly transmitting via the transceiver to the UE at least one configuration corresponding to at least one CSI compression model for obtaining compressed CSI reports; and transmitting via the transceiver and to the UE an indication corresponding to a first CSI compression model among the at least one CSI compression model, the first CSI compression model being associated with the CSI report configuration.

[0047] It should be understood that the summary section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become apparent from the following description. Attached Figure Description

[0048] Figure 1 An example of a wireless communication system supporting CSI compression according to aspects of this disclosure is shown.

[0049] Figure 2 An example of a signaling procedure for CSI compression according to aspects of this disclosure is shown.

[0050] Figure 3 An example of MAC CE for CSI compression model association on PUCCH in accordance with aspects of this disclosure is shown.

[0051] Figure 4 An example of MAC CE for updating the CSI compression model configured for CSI reports, according to aspects of this disclosure, is shown.

[0052] Figure 5 and Figure 6 An example of a device that supports CSI compression according to aspects of this disclosure is shown.

[0053] Figure 7 and Figure 8 An example of a processor that supports CSI compression according to aspects of this disclosure is shown.

[0054] Figure 9 and Figure 10 A flowchart of a method supporting CSI compression according to aspects of this disclosure is shown. Detailed Implementation

[0055] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0056] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0057] In this disclosure, references to "an embodiment," "an example embodiment," "an embodiment," "some embodiments," etc., indicate that the described embodiments may include specific features, structures, or characteristics, but not every embodiment necessarily includes that specific feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will recognize that, whether explicitly described or not, incorporating other embodiments to affect such a feature, structure, or characteristic is within their knowledge.

[0058] It should be understood that although the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0059] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising,” “including,” “having,” “having,” “including,” and / or “containing” are used herein, the presence of the stated features, elements, and / or components is specified, but the presence or addition of one or more other features, elements, components, and / or combinations thereof is not excluded.

[0060] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as 5G New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols and / or any other protocols currently known or to be developed in the future. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems that this disclosure can utilize. This should not be construed as limiting the scope of this disclosure to the systems described above.

[0061] As used herein, the term "network device" generally refers to a node in a communication network through which terminal devices can access the network and receive services. Depending on the terminology and technology used, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Head (RH), infrastructure equipment for V2X (Vehicle-to-Everything) communication, a Transmit and Receive Point (TRP), a Receive Point (RP), a Remote Radio Head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, and a low-power node (such as a femtoBS, a picoBS, etc.).

[0062] As used herein, the term "terminal device" generally refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), end user equipment, subscriber station (SS), unmanned aerial vehicle (UAV), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, VoIP phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), USB dongles, smart devices, wireless client devices (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0063] CSI reporting based on CSI compression using bilateral models (such as artificial intelligence (AI) / machine learning (ML) models) has been introduced in NR Release 19. In this process, the eigenvectors of the downlink (DL) channel matrix are first compressed by the UE via a UE-side CSI generation model to obtain compressed CSI. This compressed CSI is then reported to the NW by the CSI reporting process. The NW reconstructs the eigenvectors of the DL channel matrix by inputting the received compressed CSI into its NW-side CSI reconstruction model. CSI reporting based on CSI compression using bilateral models can provide performance gains in most use cases. However, some open questions regarding CSI compression using bilateral models remain to be investigated in the future, such as CSI compression model matching between the UE and NW, and CSI compression model updates at the UE and / or NW sides.

[0064] The CSI framework was introduced in NR version 15. For example, the process for non-periodic CSI reporting assumes that a CSI report is triggered by a DCI with a format of 0_1 or 0_2 that includes a non-zero CSI request field.

[0065] The time and frequency resources that can be used by the UE to report CSI are controlled and indicated by the gNB. CSI may include Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) Block Resource Indicator (SSBRI), Layer Indicator (LI), Rank Indicator (RI), Layer 1 (L1) Reference Signal Received Power (RSRP), L1 Signal-to-Interference-plus-Noise Ratio (SINR), or Capability Index.

[0066] For CQI, PMI, CRI, SSBRI, LI, RI, L1-RSRP, L1-SINR, and / or CapabilityIndex, the UE is configured by a higher layer, where N ≥ 1. CSI-ReportConfig Report settings, M≥1 CSI-ResourceConfig Resource settings, and one or two lists of trigger states (by higher-level parameters) CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerStateList (Given). CSI-AperiodicTriggerStateList Each triggered state contains an associated one. CSI-ReportConfig A list indicating resource set IDs used for channels, and optionally resource set IDs used for interference. CSI-SemiPersistentOnPUSCH-TriggerStateList Each triggered state contains an associated one. CSI-ReportConfig .

[0067] Each report setting CSI-ReportConfig All are related to channel measurements. CSI- ResourceConfigThe single downlink bandwidth portion (BWP) given in the text (composed of higher layer parameters) BWP-Id The indicator is associated with and contains (multiple) parameters for a CSI reporting band: codebook configuration (including codebook subset restrictions), time-domain behavior, frequency granularity for CQI and PMI, measurement restriction configuration, and CSI-related quantities to be reported by the UE, such as LI, L1-RSRP, L1-SINR, CRI, SSBRI, and CapabilityIndex.

[0068] CSI-ReportConfig The temporal behavior is determined by higher-level parameters. reportConfigType The indicator can be set to "aperiodic", "semiPersistentOnPUCCH", "semiPersistentOnPUSCH", or "periodic". For "periodic" and "semiPersistentOnPUCCH" / "semiPersistentOnPUSCH" CSI reports, the configured periodicity and slot offset are applied to the parameter set of the UL BWP in which the CSI report is configured to be sent. Higher layer parameters reportQuantity Indicates the quantity to be reported that is CSI-related, L1-RSRP-related, L1-SINR-related, or capability index-related. reportFreqConfiguration Indicates the reporting granularity in the frequency domain, including the CSI reporting band and whether the PMI / CQI report is broadband or subband. CSI-ReportConfig In timeRestrictionForChannelMea surements The parameters can be configured to enable time-domain constraints for channel measurements, and timeRestrictionForIn terferenceMeasurements The parameters can be configured to enable time-domain constraints for interference measurements. CSI- ReportConfig It can also include CodebookConfig It includes configuration parameters for selecting Type I, Type II, Enhanced Type II CSI, or Further Enhanced Type II ports, including applicable codebook subset limitations and group-based reporting configuration. If reportConfigType When set to "aperiodic", the UE does not expect to be configured with CSI reporting settings associated with a dormant DLBWP.

[0069] Additionally, each CSI resource setting CSI-ResourceConfig Each configuration includes a list of S≥1 CSI resource sets (determined by higher-level parameters). csi-RS-ResourceSetList(Given). This list includes references to one or both of the (multiple) Non-Zero Power (NZP) CSI Reference Signal (RS) resource sets and (multiple) SS / PBCH block sets, or the list includes references to (multiple) CSI Interference Measurement (IM) resource sets. Each CSI resource setting is located within a set of higher-level parameters. BWP-id The DL BWP is identified, and all CSI resource settings linked to CSI reporting settings have the same DL BWP.

[0070] The temporal behavior of CSI-RS resources within CSI resource settings is determined by higher-level parameters. resourceType The indicator can be set to non-periodic, periodic, or semi-persistent. For periodic and semi-persistent CSI resource settings, when the UE is configured with... groupBasedBeamReporting-r17 When the configuration is active, the number of CSI resource sets is S=2; otherwise, the number of CSI-RS resource sets is limited to S=1. For periodic and semi-persistent CSI resource settings, the configured periodicity and slot offset are given by the parameter set of their associated DL BWP, such as... BWP-id Given. When the UE is configured with multiple NZPCSI-RS resource IDs consisting of the same NZPCSI-RS resource ID. CSI-ResourceConfigs At the same time, the same time-domain behavior can be configured for CSI- ResourceConfigs When a UE is configured with multiple UEs consisting of the same CSI-IM resource ID... CSI-ResourceConfigs At the same time, the same time-domain behavior can be configured for CSI-ResourceConfigs All CSI resource settings linked to CSI reporting settings can have the same time-domain behavior.

[0071] For the reporting configuration, the UE may assume the following dependencies between the CSI parameters (if reported) to calculate the CSI parameters (if reported): (1) LI can be calculated based on the reported CQI, PMI, RI and CRI; (2) CQI can be calculated based on the reported PMI, RI and CRI; (3) PMI can be calculated based on the reported RI and CRI; and (4) RI can be calculated based on the reported CRI.

[0072] The reporting configuration for CSI can be periodic (using PUSCH), periodic (using PUCCH), or semi-persistent (using PUCCH, with PUSCH activated by DCI). CSI-RS resources can be periodic, semi-persistent, or aperiodic. In 3GPP Technical Specification TS38.214 v18.0.0, the supported combinations of CSI reporting configurations and CSI-RS resource configurations, and how CSI reports are triggered for each CSI-RS resource configuration, are shown in Table 5.2.1.4-1 of TS38.214 v18.0.0. Periodic CSI-RS are configured by higher layers. Semi-persistent CSI-RS are activated and deactivated as described in Clause 5.2.1.5.2 of TS38.214 v18.0.0. Aperiodic CSI-RS are configured and triggered / activated as described in Clause 5.2.1.5.1 of TS38.214 v18.0.0.

[0073] On the other hand, some conclusions have already been captured in TR 38.843. The following lists some possible specification effects of CSI feedback enhancement for CSI compression using a bilateral model, including but not limited to fallback mode, model input / output, UE-side data collection, NW-side data collection, CSI configuration and reporting, feasibility, and methods to support traditional CSI reporting principles.

[0074] For example, regarding fallback modes, there may be potential regulatory implications for the coexistence and fallback mechanisms between AI / ML-based CSI feedback modes and traditional non-AI / ML-based CSI feedback modes.

[0075] For NW / UE alignment, there may be potential canonical implications regarding the alignment of quantization / dequantization methods and feedback message sizes between the network and the UE, including: (1) for vector quantization schemes, the format and size of the VQ codebook, and the size and segmentation method of the CSI generation model output; and (2) for scalar quantization schemes, the format of uniform and non-uniform quantization (e.g., quantization granularity), consisting of the bit distribution allocated to each floating-point number; and (3) quantization alignment using 3GPP-aware mechanisms.

[0076] For model inputs / outputs, at least for the precoding matrix (e.g., a space-frequency domain precoding matrix or a precoding matrix represented using angular delay domain projection), there may be potential canonical effects regarding CSI output-CSI-UE and input-CSI-NW. In the case of a precoding matrix represented using angular delay domain projection, the explicit channel matrix (i.e., the complete Tx) The Rx MIMO channel also depends on the performance evaluation being studied, where the original channel is in the spatial frequency domain or the original channel is in the angular delay domain.

[0077] For UE-side data collection, there may be potential regulatory impacts on the following aspects: enhancements to CSI-RS configuration to enable higher accuracy measurements; auxiliary information for UE data collection to classify data into ID form for the purpose of distinguishing data due to the characteristics of specific configurations, scenarios, sites, etc. (the provision of auxiliary information needs to consider the feasibility of disclosing proprietary information to the other party); and signaling used to trigger data collection.

[0078] For network-side data collection, there may be potential regulatory impacts on the following aspects: (1) enhancements to Probe Reference Signal (SRS) and / or Channel State Information Reference Signal (CSI-RS) measurements and / or CSI reporting to enable higher accuracy measurements; (2) the content of Truth CSI, including data sample type (e.g., precoding matrix, channel matrix, etc.), data sample format (including scalar quantization and / or codebook-based quantization (e.g., e-type II, etc.)), and ancillary information (e.g., timestamps and / or cell IDs, ancillary information for network data collection to facilitate data processing). The classification is in the form of ID, used to distinguish the purpose of data due to specific configuration, scenario, site, etc., and data quality indicators); (3) latency requirements for data collection; (4) signaling used to trigger data collection; (5) real CSI reports for NW-side data collection for model performance monitoring, including scalar quantization for real CSI, codebook-based quantization for real CSI, radio resource control (RRC) signaling and / or L1 signaling procedures for enabling fast identification of AI / ML model performance, and non-periodic / semi-persistent or periodic real CSI reports; (6) For model training The Truth CSI format includes scalar quantization or codebook-based quantization for Truth CSI. In this paper, truth data is considered in relation to the number of layers it is collected from, and whether the UE or NW determines the number of layers used for Truth CSI data collection.

[0079] For CSI configuration and reporting, there may be potential specification impacts on the following aspects: (1) NW configuration for determining the CSI payload size, e.g., possible CSI payload sizes, possible rank limits and / or other related configurations; (2) how the UE determines / reports the actual CSI payload size and / or other CSI-related information within the constraints of network configuration; and (3) the related uplink control information (UCI) format, considering the traditional CSI reporting principle, where CSI Part 1 and Part 2 serve as starting points, where Part 1 has a fixed size configured by the network, and the size of Part 2 is dynamic, determined by the information in Part 1. For CQI determination in CSI reporting, if CQI is configured in CSI reporting, CQI is not calculated based on the output of the CSI reconstruction part from the actual channel estimation, but rather CQI can be calculated based on the target CSI with actual channel measurements, or CQI can be calculated based on the target CSI with actual channel measurements and potential adjustments, or CQI can be calculated based on the traditional codebook. Alternatively, for CQI determination in the CSI report, if the CQI in the CSI report is configured, the CQI can be calculated based on the output of the CSI reconstruction portion from the actual channel estimation. For example, if the CSI reconstruction model is available at the UE, and the UE can perform reconstruction model inference using potential adjustments (in which case the CSI reconstruction portion at the UE can differ from the actual CSI reconstruction portion used at the NW), and as another option, the CQI can be calculated using a two-stage method, with the UE deriving the CQI using precoded CSI-RS transmitted using the reconstruction precoder. Furthermore, the feasibility of different methods for calculating the CQI can be evaluated. Gap analysis between the UE-side CQI calculation results and the NW-side results, and the impact on scheduling performance, can also be evaluated. Additionally, the complexity of CQI calculation needs to be evaluated, including computational complexity and potential RS / signaling overhead.

[0080] For feasibility and to support traditional CSI reporting principles, there may be priority rules for CSI conflict handling and CSI omission, codebook subset restrictions (e.g., input CSI-NW / output CSI-UE considered in the angle delay domain, beam constraints may be based on traditional SD basis vector-based input CSI in the angle domain), and potential canonical effects on CSI processing units.

[0081] In addition to the potential regulatory impacts mentioned above, there are several potential regulatory enhancements regarding the following: (1) CSI-RS configuration (excluding CSI-RS mode design enhancements); (2) CSI configuration (for network-indicated information related to CSI reporting, such as gNB indications to the UE specifying CSI payload size, quantization method / granularity, rank limits, and one or more other payload-related aspects); (3) CSI reporting configuration (for the UE to determine / report the actual CSI payload size, and the UE to report relevant information as configured by the NW); (4) CSI reporting UCI mapping / priority / ignore; and (5) CSI processing procedures.

[0082] To better support CSI reporting based on CSI compression utilizing bilateral AI / ML models, the existing CSI reporting framework needs to be further enhanced.

[0083] This disclosure proposes a solution supporting CSI compression, for example, CSI compression using a bilateral model (e.g., an AI / ML model). In this solution, the UE can report its capability for CSI compression using a bilateral model to the base station. Based on the received UE capacity, the base station can configure several CSI compression models for the UE and can further activate some configured CSI compression models. When the base station activates a CSI building model, an indication associated with the activated CSI compression model can be sent to the UE. The UE can determine a suitable CSI generation model from the configured CSI compression models. In this way, CSI compression operations using a bilateral AI / ML model can be better supported on both the UE and base station sides.

[0084] The aspects of this disclosure will be described in the context of wireless communication systems.

[0085] Figure 1An example of a wireless communication system 100 supporting CSI compression is shown. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G. In addition, the wireless communication system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0086] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100. The network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RAN), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0087] Network entity 102 can provide a geographic coverage area 112 for which it can support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 can be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas 112 can be associated with different network entities 102. The information and signals described herein can be represented using a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned in the description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0088] One or more UEs 104 may be distributed across a geographical area of ​​the wireless communication system 100. UE 104 may include, or may be referred to as, a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0089] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1 It is shown in the middle. For example... Figure 1 As shown, UE 104 can communicate with various types of devices, such as network entity 102, other UE 104, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device). Alternatively or additionally, UE 104 can support communication with other network entities 102 or UE 104, which can act as relays in the wireless communication system 100.

[0090] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a side link. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0091] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with other core networks 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0092] In some implementations, network entity 102 can be configured in a decomposed architecture that can utilize a protocol stack physically or logically distributed across two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: CU, DU, radio unit (RU), RAN intelligent controller (RIC) (e.g., near-real-time RIC, non-real-time RIC), service management and orchestration (SMO) system, or any combination thereof.

[0093] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a decomposed RAN architecture, one or more components of network entity 102 may be co-located, or one or more components of network entity 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0094] The functional division among CU, DU, and RU can be flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU, or RU. For example, the functional division of the protocol stack can be adopted between the CU and DU, such that the CU can support one or more layers of the protocol stack, while the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC), Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0095] Alternatively, or alternatively, the functional division of the protocol stack can be adopted between DU and RU, such that DU can support one or more layers of the protocol stack, while RU can support one or more different layers of the protocol stack. DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between CU and DU or between DU and RU can be within the protocol layer (e.g., some functions for the protocol layer can be performed by one of CU, DU, or RU, while other functions of the protocol layer are performed by a different one of CU, DU, or RU).

[0096] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via mid-range communication links (e.g., F1, F1c, F1-u), while the DUs can be connected to one or more RUs via front-end communication links (e.g., open front-end (FH) interfaces). In some implementations, the mid-range or front-end communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack, supported by corresponding network entities 102 communicating via such communication links.

[0097] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core network (5GC), which may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Functions (AMF)) and user plane entities that route or interconnect packets to external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Functions (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0098] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 can communicate with application server 118. UE 104 can establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session can be one example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0099] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single-frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multi-frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more digital technologies.

[0100] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefix. The first digital technology (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first digital technique (e.g., ...) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. Second digital technologies (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. The third digital technology (e.g., μ =2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ =3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0101] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0102] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ =4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the digital technology. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the digital technology. It should be understood that for the first digital technology (e.g., quantity) associated with the first subcarrier spacing (e.g., 15 kHz), μ The reference of =0 can be used interchangeably between subframes and time slots.

[0103] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for short-range, high data rate capabilities.

[0104] FR1 can be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 can be associated with the following: a first digital technology (e.g., μ =0), which includes a 15 kHz subcarrier spacing; second digital technology (e.g., μ =1), which includes a 30 kHz subcarrier spacing; third digital technology (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 can be associated with a third digital technology (e.g., μ =2), which includes a 60 kHz subcarrier spacing; fourth digital technology (e.g., μ =3), which includes a subcarrier spacing of 120 kHz.

[0105] Figure 2 An example of a signaling procedure 200 for CSI compression according to this disclosure is shown. The signaling procedure 200 relates to base station 102 and UE 104, base station 102.

[0106] like Figure 2 As shown, at step 202, UE 104 may send capability information about CSI compression using a bilateral model to base station 102. This capability information may be determined by UE 104 for each UE, each frequency band, or each combination of frequency bands. That is, UE 104 may report its capability information for all frequency bands to base station 102, or UE 104 may report its capability information for each frequency band. Alternatively, UE 104 may report its capability information for each combination of frequency bands to base station 102.

[0107] In some embodiments of this disclosure, the capability information may include first information regarding whether CSI compression using a bilateral model (e.g., a bilateral AI / ML model) is supported by the UE 104. When CSI compression using a bilateral model is supported by the UE 104, the capability information may further include: the number of CSI compression models supported by the UE; second information regarding whether at least one of rank-based CSI reporting (or rank-based CSI compression) and / or layer-based CSI reporting (or / or layer-based CSI compression) is supported by the UE; the maximum rank supported by the CSI compression report for each CSI compression function or for each CSI compression model; and third information regarding the number of uplink control information (UCI) bits used for the compressed CSI report. In this document, a CSI compression model can be used to compress CSI so that a compressed CSI report can be obtained (generated). A CSI compression function can refer to a function or functional entity used for compressed CSI and may be associated with one or more CSI compression models.

[0108] As an example, if UE 104 supports CSI compression using a bilateral model, UE 104 may further indicate the number of CSI compression models configured by RRC, and whether it supports rank-based CSI compression (i.e., rank-based CSI reporting) and / or layer-based CSI compression (i.e., layer-based CSI reporting). If UE 104 supports rank-based CSI compression (i.e., rank-based CSI reporting), UE 104 may further indicate the maximum rank it supports for each function (e.g., CSI compression function) or for each model (e.g., CSI compression model), and the number of UCI bits required for each function or for each model for a compressed CSI report corresponding to each rank. For example, for the CSI compression function or CSI compression model, when the corresponding maximum rank is indicated as rank 1, the number of UCI bits required for a compressed CSI report corresponding to rank 1 can be N1; when the corresponding maximum rank is indicated as rank 2, the number of UCI bits required for a compressed CSI report corresponding to rank 2 can be N2; when the corresponding maximum rank is indicated as rank 8, the number of UCI bits required for a compressed CSI report corresponding to rank 8 can be N8, and so on. The above numbers of UCI bits required for compressed CSI reports are merely examples and not limitations.

[0109] Furthermore, in some embodiments of this disclosure, when rank-based CSI reporting is supported by the UE, the third information may include one or more candidate values ​​regarding the number of UCI bits used for each rank. As an example, assuming the maximum rank corresponding to the CSI compression function or CSI compression model is rank 2, candidate values ​​regarding the number of UCI bits used for a compressed CSI report corresponding to rank 2 may include 4, 8, etc. Each candidate value may correspond to an associated CSI compression rate, an associated CSI compression scenario, etc.

[0110] Alternatively, if UE 104 supports layer-by-layer CSI compression (i.e., layer-by-layer CSI reporting), UE 104 may further indicate the maximum rank it supports for each function (e.g., CSI compression function) or each model (e.g., CSI compression model), and the number of UCI bits required for the compressed CSI report corresponding to each transport layer (e.g., PUSCH transport layer) for each CSI compression function or for each CSI compression model. For example, for a CSI compression function or CSI compression model, if the corresponding maximum rank is indicated as rank 2, the number of UCI bits required for the compressed CSI report corresponding to each transport layer can be N. Rank 2 means that at most two transport layers can be used by base station 102 (e.g., gNB) for scheduling data. The number of UCI bits required for the compressed CSI report above is merely an example and not a limitation.

[0111] Furthermore, in some embodiments of this disclosure, when layer-by-layer CSI reporting is supported by the UE, similar to the case of rank-by-rank CSI reporting, the third information may include one or more candidate values ​​regarding the number of UCI bits for each layer. As an example, assuming the maximum rank corresponding to the CSI compression function or CSI compression model is rank 2, the candidate values ​​for the number of UCI bits for the CSI report corresponding to each transport layer may include N1, N2, etc. Each candidate value may correspond to an associated CSI compression rate, an associated CSI compression scenario, etc.

[0112] Back Figure 2 At step 204, base station 102 may receive capability information from UE 104, and at step 206, accordingly send at least one configuration corresponding to at least one CSI compression model. Each CSI compression model can be used to obtain a compressed CSI report.

[0113] At step 208, UE 104 receives at least one configuration corresponding to at least one CSI compression model. In some embodiments of this disclosure, the configuration in the at least one configuration may include: an identifier (ID) corresponding to the CSI compression model; the maximum rank supported by the compressed CSI report for the CSI compression model; the number of uplink control information (UCI) bits for the compressed CSI report corresponding to each rank when rank-based CSI reporting is configured; and the number of UCI bits for the compressed CSI report corresponding to each transport layer when layer-based CSI reporting is configured.

[0114] In other words, for CSI compression based on the UE's capabilities against the serving cell and using a bilateral model by RRC, base station 102 can configure a list of CSI compression models, each of which can have one. CSI-CompressionModelId These CSI compression models can be determined by base station 102 based on UE capabilities (e.g., capability information received from UE 104) and can be instructed to UE 104 for future use. For example, base station 102 can send configuration information of the CSI compression models corresponding to these CSI reconstruction models to UE 104. The CSI generation model corresponding to each of the received CSI compression models can be determined by the UE itself. A CSI compression model can correspond to one CSI generation model and one CSI reconstruction model. Table 1 shows an example of the CSI compression model configuration for a CSI compression model. Table 1. Examples of CSI compression model configurations

[0115] For example, as shown in Table 1, CSI-CompressionModelId Indicates the ID of the CSI compression model. SupportedMaxRank This indicates the maximum rank supported for compressing CSI reports for this CSI compression model. Additionally, when rank-based CSI reporting is configured, NofUCIbitsPerRankList Indicates the number of UCI bits used for the compressed CSI report corresponding to each rank; and when tier-by-tier CSI reporting is configured, NofUCIbitsPerLayer Indicates the number of UCI bits used for the compressed CSI report corresponding to each transport layer.

[0116] Based on the above configuration, for rank-based CSI feedback (i.e., rank-based CSI reporting), base station 102 can indicate the number of UCI bits used for the CSI report corresponding to each rank, and UE 104 can report the RI (rank indicator) and the corresponding compressed CSI. For layer-based CSI feedback (i.e., layer-based CSI reporting), base station 102 can indicate the number of UCI bits used for the CSI report corresponding to each layer, and UE 104 can report the RI and compressed CSI corresponding to each layer.

[0117] Following step 208, at step 210, base station 102 may send an indication corresponding to a first CSI compression model in at least one CSI compression mode. The first CSI compression model may be associated with a CSI reporting configuration, and it may be an activated CSI compression model (e.g., the associated CSI compression model corresponds to one of the activated CSI reconfiguration models in base station 102). At step 212, UE 104 may receive the indication. This document describes base station 102 sending an indication of a CSI compression model to UE 104; in other embodiments, base station 102 may send multiple indications, each corresponding to an activated CSI compression model, with similar operation for each indication.

[0118] In some embodiments of this disclosure, base station 102 may configure or associate a CSI compression model with a CSI reporting setting (e.g., a CSI reporting configuration). For example, an indication received by UE 104 may include a CSI compression model identifier (ID) of a first CSI compression model. Where the CSI reporting configuration associated with the first CSI compression model corresponds to periodic CSI reporting, this indication may be communicated via Radio Resource Control (RRC) signaling in the CSI reporting configuration (i.e., CSI-ReportConfig This is indicated in the CSI report configuration (i.e., ) associated with the first CSI compression model, where the CSI report configuration corresponds to a semi-persistent (SP) CSI report on the physical uplink control channel (PUCCH) (activated by MAC CE). As another example, this indication can be sent via RRC signaling to the CSI report configuration (i.e., ). CSI-ReportConfig The instruction may be made in the first MAC CE used to activate / deactivate the SP CSI report on the PUCCH, or it may be made in the first MAC CE used to activate / deactivate the SP CSI report on the PUCCH. The first MAC CE may be a dedicated MAC CE and an enhanced MAC CE used to activate / deactivate the SP CSI report on the PUCCH.

[0119] Figure 3 An example of a MAC CE (e.g., a first MAC CE) associated with a CSI compression model for SP CSI reporting on PUCCH is shown in accordance with aspects of this disclosure.

[0120] like Figure 3 As shown, the MAC CE used for CSI compression model association for SP CSI reports on PUCCH includes the serving cell ID field, BWP ID field, Si field, Ai field, CSI compression model ID field, and R field. The serving cell ID field indicates the identifier of the MAC CE for its applicable serving cell. The BWP ID field indicates the identifier of the MAC CE for its applicable ULBWP. The Si field indicates the identifier configured by RRC. csi-ReportConfigToAddModList The activation / deactivation status of the semi-persistent CSI reporting configuration within the system. S0 refers to the reporting configuration that includes the PUCCH resource used for indicating SP CSI reports in the BWP, and has the lowest [status] in the list. CSI-ReportConfigId (Right now, csi-ReportConfigToAddModList Its type is set to semiPersistentOnPUCCH S1 refers to the reporting configuration that includes the PUCCH resource used for indicative SP CSI reports in the BWP, and has a second minimum CSI-ReportConfigId The Si field being set to 1 indicates the corresponding semi-persistent CSI report configuration. i This should be activated. Setting the Si field to 0 indicates the corresponding semi-persistent CSI report configuration. i It should be deactivated. The Ai field indicates the CSI compression model ID used for the CSI report configuration corresponding to the Si field. i The presence of the field. An Ai field set to 1 indicates the existence of an active CSI compression model ID corresponding to the CSI report configuration for the Si field. An Ai field set to 0 indicates that there is no active CSI reconstruction model ID corresponding to the CSI report configuration for the Si field. Additionally, the CSI compression model ID... i The field indication is associated with the CSI report configuration corresponding to the Si field. CSI-CompressionModelId The identified CSI compression model. The R field refers to the reserved bits and is set to 0.

[0121] Additionally, in some embodiments of this disclosure, where the CSI report configuration associated with the first CSI compression model corresponds to an SP CSI report on the Physical Uplink Shared Channel (PUSCH) (activated by the CSI request field in a DCI scrambled with the SP-CSI Radio Network Temporary Identifier (RNTI)), the indication can be specified in the CSI report configuration by RRC signaling, or in the downlink control information (DCI) field included in the DCI used to activate the SP CSI report on the PUSCH. In this document, each SP CSI report configuration can be associated with a... CSI- SemiPersistentOnPUSCH-TriggerStateAssociated and can be activated via the CSI request field in the DCI scrambled using SP-CSI-RNTI; and each CSI request field code point can also be associated with a CSI- SemiPersistentOnPUSCH-TriggerState Related. For this DCI-based solution, the activated CSI compressed model ID can be indicated by the AI / ML model indicator field contained in the activated DCI.

[0122] Furthermore, when the CSI report configuration associated with the first CSI compression model corresponds to an aperiodic CSI report (triggered by a non-zero CSI request field in the DCI scrambled with the Cell Radio Network Temporary Identifier (C-RNTI)), this indication can be specified in the CSI report configuration by RRC signaling, or it can be specified in the second MAC CE, or it can be specified in the DCI field included in the DCI used to trigger the aperiodic CSI report. In this document, when the CSI compression model ID is configured for aperiodic CSI reports configured by RRC signaling, the CSI compression model ID can be... CSI- AperiodicTriggerStateListIE within CSI-AssociatedReportConfigInfo The parameters are configured within this field. When the CSI compressed model ID is configured via DCI for non-periodic CSI reporting, this CSI compressed model ID can be indicated by the AI / ML model indicator field included in the triggering DCI.

[0123] In some embodiments of this disclosure, base station 102 may send a third MAC CE to UE 104 for updating a first CSI compression model using a second CSI compression model. Upon receiving the third MAC CE from base station 102, UE 104 may update the first CSI compression model using the second CSI compression model. The third MAC CE may include an ID of a CSI report configuration associated with the first CSI compression model and an ID of a second CSI compression model associated with that CSI report configuration. The second CSI compression model may be activated by base station 102 or may correspond to a CSI reconstruction model already activated in base station 102.

[0124] Figure 4 An example of a MAC CE (e.g., a third MAC CE) for updating a CSI compression model configured for CSI reports is shown according to aspects of this disclosure.

[0125] like Figure 4As shown, the MAC CE used for CSI compression model updates includes a serving cell ID field, a CSI report configuration field, and an associated CSI compression model ID field. The serving cell ID field indicates the identifier of the MAC CE for its applicable serving cell. The BWP ID field indicates the MAC CE for its applicable UL BWP. The CSI report configuration ID field indicates the identifier of the MAC CE for its applicable UL BWP. CSI- ReportConfig The CSI report configuration is used to update its associated CSI compressed model ID. The associated CSI compressed model ID field indicates the configuration of the report. CSI-CompressionModelId The identified active CSI compression model, CSI- CompressionModelId Associated with the CSI report configuration indicated by the CSI report configuration ID field.

[0126] In some embodiments of this disclosure, UE 104 may determine a CSI report corresponding to the CSI report configuration associated with the CSI compression model. Unlike the CSI report specified in NR Release 16, the eigenvectors of the channel matrix are compressed and directly fed back to base station 102, and the two-stage PMI feedback used in the NR Release 16 CSI report is no longer assumed. In other words, all compressed CSIs for rank or for each layer can be reported together. The following reporting quantities can be reused: cri-RI-PMI, cri-RI-PMI-CQI, cri-RI-LI-PMI-CQI, where the PMI in the corresponding CSI report can be replaced by the compressed CSI.

[0127] When the CSI report is a rank-based CSI report, it may include at least an RI field and a single field for the compressed CSI corresponding to the rank indicated by the RI field. Furthermore, when the CSI report is a stratified CSI report, it may include at least an RI field and multiple fields, each of which indicates the compressed CSI corresponding to each stratum of the rank indicated by the RI field. k Corresponding to k One transport layer.

[0128] For example, for rank-based CSI compression, the CSI report may include a single field corresponding to the compressed CSI for the entire frequency band (i.e., wideband CSI) or each subband (i.e., subband CSI), and the bit width of this field can be configured via RRC signaling. For tier-based CSI compression, the CSI report may include N fields, each indicating the compressed CSI corresponding to each tier, where N is indicated by the RI field, and the bit width of each field can be configured via RRC signaling. Base station 102 may assume that the feature values ​​corresponding to each tier are arranged in descending order.

[0129] Since different AI generation models on the UE side can correspond to separate hardware resources, the number of simultaneous AI operations should not exceed the UE's capabilities. For example, if the UE only has a single CSI generation model for the CSI reconstruction model (both are models for CSI compression, i.e., CSI compression models), then UE 104 can only perform a single CSI generation process at a time. If UE 104 is configured / instructed to report another compressed CSI using AI operations, but UE 104 does not have the AI-related resources available for this CSI report, then the corresponding UE behavior can be specified.

[0130] In some embodiments of this disclosure, if there are no resources available for the first CSI compression model, UE104 may discard the entire CSI report, or it may discard only the PMI portion of the CSI report and send a CSI report without the PMI portion to the base station (i.e., other CSI parameters are still reported).

[0131] Alternatively, in the absence of resources available for the first CSI compression model, UE 104 may, based on the UE's capabilities, allocate resources associated with channel and / or interference resources according to the corresponding... CSI-ReportConfig of repor tQuantityForFallbackconfigured Reporting non-AI CSI (which can also be called fallback CSI), such as NR version 16 CSI. In other words, UE 104 can report based on the pre-defined reporting information included in the CSI reporting configuration (i.e., reportQuantityForFallback The fallback CSI is determined based on the same resources configured for channel and / or interference measurements for the CSI report.

[0132] Table 2 shows the configuration of the CSI refactoring model and examples of fallback behavior for CSI reporting:

[0133] In Table 4, higher-level parameters associatedCSI-CompressionModel Configure a CSI compression model for this CSI report. The corresponding CSI report format for this CSI report is implicitly determined by the configuration of the associated CSI reconstruction model. Higher-level parameters. reportQuantity The number of CSI reports configured for this CSI report configuration is determined by using the associated CSI compression model. When the UE cannot provide the corresponding compressed CSI, higher-layer parameters are used. reportQuantityForFallback Configure the number of CSI reports to roll back for this CSI report.

[0134] When UE 104 reports a UCI corresponding to a CSI report, UE 104 can indicate whether the reported CSI is a fallback CSI. For example, a special field can be included in the CSI report to indicate whether the reported CSI is a compressed CSI or a fallback CSI.

[0135] In some embodiments of this disclosure, the CSI report may include a rollback indicator that indicates whether the CSI report includes compressed CSI or rolled-back CSI, as shown in Tables 2 and 3. In the absence of resources available for the CSI compression model, the rollback indicator may indicate that rolled-back CSI is included in the CSI report; otherwise, the rollback indicator may indicate that compressed CSI is included in the CSI report.

[0136] Table 3 shows the UCI format for compressed CSI reports used for rank-based CSI compression, and Table 4 shows the UCI format for compressed CSI reports used for layer-based CSI compression. Table 3 UCI formats used for rank-CSI compression Table 4 UCI Formats for Layer-by-Layer CSI Compression

[0137] As shown in Table 2, when the CSI report is a rank-based CSI report, the CSI report includes at least the CSI Reference Signal (RS) Resource Indicator (CRI) field, the RI field, and the Precoding Matrix Indicator (PMI) section, which includes compressed CSI or backtracked CSI (also known as conventional CSI) corresponding to the RI indicated in the RI field. As shown in Table 3, when the CSI report is a layer-based CSI report, the CSI report includes at least the CRI field, the RI field, the Layer Indicator (LI) field, and the PMI section, which includes compressed CSI or backtracked CSI for each layer corresponding to the RI indicated in the RI field.

[0138] Furthermore, as shown in Tables 2 and 3, the content of the UCI format described above may vary depending on the fallback indicator field. To ensure a fixed size for the CSI report, the size of the PMI section can be determined by the maximum number of UCI bits used for the compressed CSI report and the maximum number of UCI bits used for the fallback CSI report corresponding to the CSI report configuration.

[0139] However, in cases where UE 104 discards the CSI report or the PMI portion of the CSI report when there are no resources available for AI inference in the CSI compression model, the fallback indication field can be omitted, and the compressed CSI field can have a fixed size based on the higher-level configuration.

[0140] Figure 5 An example of a device 500 supporting CSI compression according to aspects of this disclosure is shown. Device 500 may be an example of a UE 104 as described herein. Device 500 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 500 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 502, memory 504, transceiver 506, and optionally I / O controller 508. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0141] Processor 502, memory 504, transceiver 506, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the present disclosure as described herein. For example, processor 502, memory 504, transceiver 506, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0142] In some implementations, processor 502, memory 504, transceiver 506, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described herein. In some implementations, processor 502 and memory 504 coupled to processor 502 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 504 are executed by processor 502).

[0143] For example, processor 502 may support wireless communication at device 500 according to examples disclosed herein. Processor 502 may be configured to support components for transmitting capability information regarding channel state information (CSI) compression using a bilateral model to base station 102 via transceiver 506; components for receiving, correspondingly, from base station 102 via transceiver 506 at least one configuration corresponding to at least one CSI compression model for obtaining compressed CSI reports; and components for receiving, via transceiver 506 and from base station 102, an indication corresponding to a first CSI compression model among the at least one CSI compression model, which is associated with a CSI report configuration.

[0144] Processor 502 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 502 may be configured to operate a memory array using a memory controller. In other implementations, the memory controller may be integrated into processor 502. Processor 502 may be configured to execute computer-readable instructions stored in memory (e.g., memory 504) to cause device 500 to perform various functions of this disclosure.

[0145] Memory 504 may include random access memory (RAM) and read-only memory (ROM). Memory 504 may store computer-readable, computer-executable code, including instructions that, when executed by processor 502, cause device 500 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 502, but may cause a computer (e.g., at compile and execution time) to perform the functions described herein. In some implementations, memory 504 may include a basic I / O system (BIOS) or similar system that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0146] I / O controller 508 can manage input and output signals for device 500. I / O controller 508 can also manage peripheral devices not integrated into device 500. In some implementations, I / O controller 508 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 508 can utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 508 can be implemented as part of a processor (such as processor 506). In some implementations, a user can interact with device 500 via I / O controller 508 or via hardware components controlled by I / O controller 508.

[0147] In some implementations, device 500 may include a single antenna 610. However, in other implementations, device 500 may have more than one antenna 610 (i.e., multiple antennas), including multiple antenna panels or antenna arrays that can concurrently transmit or receive multiple wireless transmissions. Transceiver 506 can communicate bidirectionally via one or more antennas 610, wired or wireless links, as described herein. For example, transceiver 506 may represent a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. Transceiver 506 may also include a modem for modulating packets, providing modulated packets to one or more antennas 610 for transmission, and demodulating packets received from one or more antennas 610. Transceiver 506 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0148] The transmit chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmit chain may also include one or more antennas 610 for transmitting the amplified signal over the air or wireless medium.

[0149] The receiver chain can be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain may include one or more antennas 610 for receiving signals over the air or a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding and processing the demodulated signal to receive transmitted data.

[0150] Figure 6 An example of a device 600 supporting CSI compression according to aspects of this disclosure is shown. Device 600 may be an example of a base station 104 as described herein, and base station 102 may include multiple TRPs. Device 600 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 600 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 602, memory 604, transceiver 606, and optionally I / O controller 608. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0151] Processor 602, memory 604, transceiver 606, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the present disclosure as described herein. For example, processor 602, memory 604, transceiver 606, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0152] In some implementations, processor 602, memory 604, transceiver 606, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described herein. In some implementations, processor 602 and memory 604 coupled to processor 602 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 604 are executed by processor 602).

[0153] For example, processor 602 may support wireless communication at device 600 according to examples disclosed herein. Processor 602 may be configured to support components for receiving capability information about channel state information (CSI) compression using a bilateral model from user equipment (UE 104) via transceiver 606; components for correspondingly transmitting to UE 104 via transceiver 606 at least one configuration corresponding to at least one CSI compression model for obtaining compressed CSI reports; and components for transmitting via transceiver 606 and to UE 104 an indication corresponding to a first CSI compression model among the at least one CSI compression model, which is associated with a CSI report configuration.

[0154] Processor 602 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 602 may be configured to operate a memory array using a memory controller. In other implementations, the memory controller may be integrated into processor 602. Processor 602 may be configured to execute computer-readable instructions stored in memory (e.g., memory 604) to cause device 600 to perform various functions of this disclosure.

[0155] Memory 604 may include random access memory (RAM) and read-only memory (ROM). Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 602, cause device 600 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 602, but may cause a computer (e.g., during compilation and execution) to perform the functions described herein. In some implementations, memory 604 may include a basic I / O system (BIOS) or similar system that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0156] I / O controller 608 can manage input and output signals for device 600. I / O controller 608 can also manage peripheral devices not integrated into device 600. In some implementations, I / O controller 608 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 608 can utilize an operating system such as iOS®, Android®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 608 can be implemented as part of a processor (such as processor 606). In some implementations, a user can interact with device 600 via I / O controller 608 or via hardware components controlled by I / O controller 608.

[0157] In some implementations, device 600 may include a single antenna 710. However, in other implementations, device 600 may have more than one antenna 710 (i.e., multiple antennas), including multiple antenna panels or antenna arrays that can concurrently transmit or receive multiple wireless transmissions. Transceiver 606 can communicate bidirectionally via one or more antennas 710, wired or wireless links, as described herein. For example, transceiver 606 may represent a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. Transceiver 606 may also include a modem for modulating packets, providing modulated packets to one or more antennas 710 for transmission, and demodulating packets received from one or more antennas 710. Transceiver 606 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0158] The transmit chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmit chain may also include one or more antennas 710 for transmitting the amplified signal over the air or wireless medium.

[0159] The receiver chain can be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain may include one or more antennas 710 for receiving signals over the air or a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding and processing the demodulated signal to receive transmitted data.

[0160] Figure 7 An example of a processor 700 supporting CSI compression according to aspects of this disclosure is shown. Processor 700 may be an example of a processor configured to perform various operations as described herein. Processor 700 may include a controller 702 configured to perform various operations as described herein. Processor 700 may optionally include at least one memory 704, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 700 may optionally include one or more arithmetic logic units (ALUs) 706. One or more of these components may be electronically or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0161] Processor 700 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to or included in the processor chipset (e.g., processor 700)), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), static random access memory (SRAM), ferroelectric random access memory (FeRAM), magnetic random access memory (MRAM), resistive random access memory (RRAM), flash memory, phase-change memory (PCM), etc.).

[0162] Controller 702 can be configured to manage and coordinate various operations of processor 700 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 700 to support various operations according to the examples described herein. For example, controller 702 can operate as a control unit of processor 700 to generate control signals that manage the operation of various components of processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[0163] Controller 702 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 704 and determine subsequent instructions(s) to be executed, such that processor 700 supports various operations as described herein. Controller 702 may be configured to track the memory addresses of instructions associated with memory 704. Controller 702 may be configured to decode instructions to determine the operation to be performed and its operands. For example, controller 702 may be configured to interpret instructions and determine control signals to be output to other components of processor 700, such that processor 700 supports various operations as described herein. Alternatively or additionally, controller 702 may be configured to manage data flow within processor 700. Controller 702 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 700.

[0164] Memory 704 may include one or more caches (e.g., memory native to or included in the processor 700) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 704 may reside within the processor chipset or on the processor chipset (e.g., native to the processor 700). In other implementations, memory 704 may reside external to the processor chipset (e.g., remote from the processor 700).

[0165] Memory 704 may store computer-readable, computer-executable code, including instructions that, when executed by processor 700, cause processor 700 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 702 and / or processor 700 may be configured to execute computer-readable instructions stored in memory 704 to cause processor 700 to perform various functions (e.g., functions or tasks supporting transmit power prioritization). For example, processor 700 and / or controller 702 may be coupled to or coupled to memory 704, and processor 700, controller 702, and memory 704 may be configured to perform the various functions described herein. In some examples, processor 700 may include multiple processors, and memory 704 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0166] One or more ALU 706s can be configured to support various operations as described herein. In some implementations, one or more ALU 706s may reside within or on a processor chipset (e.g., processor 700). In other implementations, one or more ALU 706s may reside outside the processor chipset (e.g., processor 700). One or more ALU 706s can perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 706s can receive input operands and an operand code that determine the operation to be performed. One or more ALU 706s can be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU 706s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 706s to handle conditional operations, comparisons, and bitwise operations.

[0167] Processor 700 may support wireless communication according to examples disclosed herein. Processor 700 may be configured or operable to support components for transmitting capability information regarding channel state information (CSI) compression using a bilateral model to a base station via a transceiver; components for receiving, via a transceiver and from the base station, at least one configuration corresponding to at least one CSI compression model for obtaining compressed CSI reports; and components for receiving, via a transceiver and from the base station, an indication of a first CSI compression model among the at least one CSI compression model, the first CSI compression model being associated with a CSI reporting configuration.

[0168] Figure 8 An example of a processor 800 supporting CSI compression according to aspects of this disclosure is shown. Processor 800 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 800 may include a controller 802 configured to perform various operations according to the examples described herein. Processor 800 may optionally include at least one memory 804, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 800 may optionally include one or more arithmetic logic units (ALUs) 806. One or more of these components may be electronically or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0169] Processor 800 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to or included in the processor chipset (e.g., processor 800)), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), static random access memory (SRAM), ferroelectric random access memory (FeRAM), magnetic random access memory (MRAM), resistive random access memory (RRAM), flash memory, phase-change memory (PCM), etc.).

[0170] Controller 802 can be configured to manage and coordinate various operations of processor 800 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 800 to support various operations according to the examples described herein. For example, controller 802 can operate as a control unit of processor 800 to generate control signals that manage the operation of various components of processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[0171] Controller 802 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 804 and determine subsequent instructions(s) to be executed, enabling processor 800 to support various operations as described herein. Controller 802 may be configured to track memory addresses of instructions associated with memory 804. Controller 802 may be configured to decode instructions to determine the operation to be performed and its operands. For example, controller 802 may be configured to interpret instructions and determine control signals to be output to other components of processor 800, enabling processor 800 to support various operations as described herein. Alternatively or additionally, controller 802 may be configured to manage data flow within processor 800. Controller 802 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 800.

[0172] Memory 804 may include one or more caches (e.g., memory native to or included in the processor 800) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 804 may reside internally in the processor chipset or on the processor chipset (e.g., natively in the processor 800). In other implementations, memory 804 may reside externally to the processor chipset (e.g., remotely from the processor 800).

[0173] Memory 804 may store computer-readable, computer-executable code, including instructions that, when executed by processor 800, cause processor 800 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 802 and / or processor 800 may be configured to execute computer-readable instructions stored in memory 804 to cause processor 800 to perform various functions (e.g., functions or tasks supporting transmit power prioritization). For example, processor 800 and / or controller 802 may be coupled to or coupled to memory 804, and processor 800, controller 802, and memory 804 may be configured to perform the various functions described herein. In some examples, processor 800 may include multiple processors, and memory 804 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0174] One or more ALU 806s can be configured to support various operations as described herein. In some implementations, one or more ALU 806s may reside within or on a processor chipset (e.g., processor 800). In other implementations, one or more ALU 806s may reside outside the processor chipset (e.g., processor 800). One or more ALU 806s can perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 806s can receive input operands and an operand code that determine the operation to be performed. One or more ALU 806s can be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU 806s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 806s to handle conditional operations, comparisons, and bitwise operations.

[0175] Processor 800 may support wireless communication according to examples disclosed herein. Processor 800 may be configured or operable to support components for receiving, via a transceiver and from a user equipment (UE), capability information regarding channel state information (CSI) compression using a bilateral model; components for transmitting, via the transceiver and to the UE, at least one configuration corresponding to at least one CSI compression model for obtaining compressed CSI reports; and components for transmitting, via the transceiver and to the UE, an indication corresponding to a first CSI compression model among the at least one CSI compression model, the first CSI compression model being associated with a CSI report configuration.

[0176] Figure 9 A flowchart of a method 900 supporting CSI compression according to aspects of this disclosure is shown. Operation of method 900 can be implemented by a device or components thereof as described herein. For example, operation of method 900 can be performed by a UE 104 as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the function. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the function.

[0177] At 905, the method may include: transmitting capability information regarding channel state information (CSI) compression using a bilateral model to a base station via a transceiver. The operation of 905 can be performed according to the examples described herein. In some implementations, aspects of the operation of 905 may be as described in the references... Figure 1 The aforementioned device performs the operation.

[0178] At 910, the method may include: receiving, via a transceiver, from a base station at least one configuration corresponding to at least one CSI compression model for obtaining a compressed CSI report. The operation of 910 can be performed according to examples as described herein. In some implementations, aspects of the operation of 910 may be provided by reference to [reference]. Figure 1 The device described herein performs the operation.

[0179] At 915, the method may include: receiving, via a transceiver, an indication from a base station of a first CSI compression model corresponding to at least one CSI compression model, the first CSI compression model being associated with a CSI report configuration. The operation of 915 can be performed according to examples as described herein. In some implementations, aspects of the operation of 915 may be as described in references... Figure 1 The device described herein performs the operation.

[0180] Figure 10A flowchart of a method 1000 supporting CSI compression according to aspects of this disclosure is shown. Operation of method 1000 can be implemented by a device or components thereof as described herein. For example, operation of method 1000 can be performed by a base station 104 as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the function. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the function.

[0181] At 1005, the method may include: receiving capability information regarding channel state information (CSI) compression using a bilateral model from a user equipment (UE) via a transceiver. The operation at 1005 can be performed according to examples as described herein. In some implementations, aspects of the operation at 1005 may be as described in references... Figure 1 The device described herein performs the operation.

[0182] At point 1010, the method may include: transmitting via a transceiver to the UE at least one configuration corresponding to at least one CSI compression model for obtaining a compressed CSI report. The operation of 1010 can be performed according to examples as described herein. In some implementations, aspects of the operation of 1010 may be as described in references... Figure 1 The device described herein performs the operation.

[0183] At point 1015, the method may include: transmitting to the UE via a transceiver an indication corresponding to a first CSI compression model among at least one CSI compression model, the first CSI compression model being associated with a CSI report configuration. The operation of 1015 can be performed according to examples as described herein. In some implementations, aspects of the operation of 1015 may be as described in references... Figure 1 The device described herein performs the operation.

[0184] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0185] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0186] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.

[0187] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0188] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the use of “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” without departing from the scope of this disclosure could be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0189] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), comprising: processor; as well as A transceiver, the transceiver being coupled to the processor, The processor is configured as follows: The transceiver transmits information about the capability of using a bilateral model of Channel State Information (CSI) compression to the base station. The transceiver receives, via the transceiver, at least one configuration corresponding to at least one CSI compression model for obtaining a compressed CSI report from the base station. as well as The transceiver receives from the base station an indication corresponding to a first CSI compression model among the at least one CSI compression models, the first CSI compression model being associated with a CSI report configuration.

2. The UE according to claim 1, wherein the at least one CSI compression model is determined by the base station based on the capability information.

3. The UE according to claim 1, wherein the capability information includes: First information regarding whether the CSI compression using the bilateral model is supported by the UE.

4. The UE according to claim 3, wherein when the CSI compression using a bilateral model is supported by the UE, the capability information further includes: The number of CSI compression models supported by the UE; Second information regarding whether at least one of the rank-based CSI reports and tier-based CSI reports is supported by the UE; The maximum rank supported by the CSI compression report for each CSI compression function or for each CSI compression model, where a CSI compression function is associated with one or more CSI compression models; as well as Third information regarding the number of uplink control information (UCI) bits used in the compressed CSI report.

5. The UE according to claim 4, wherein When the rank-based CSI report is supported by the UE, the third information includes: For each CSI compression function or for each CSI compression model, the number of UCI bits corresponding to each rank of the compressed CSI report; as well as When the layer-by-layer CSI reporting is supported by the UE, the third information includes: the number of UCI bits corresponding to the compressed CSI report for each transport layer, for each CSI compression function or for each CSI compression model.

6. The UE according to claim 1, wherein the configuration in the at least one configuration includes: The identifier ID corresponding to the CSI compression model; For the aforementioned CSI compression model, the maximum rank supported by the compressed CSI report; When a rank-based CSI report is configured, the number of uplink control information (UCI) bits used for the compressed CSI report corresponding to each rank; as well as When layer-by-layer CSI reporting is configured, the number of UCI bits used for the compressed CSI report corresponding to each transport layer.

7. The UE of claim 6, wherein the processor is further configured to: Determine the CSI report corresponding to the CSI report configuration, and If the CSI report is a rank-based CSI report, the CSI report includes at least: The rank indicator RI field and a single field for the compressed CSI corresponding to the RI indicated in the RI field; as well as In the case that the CSI report is a tiered CSI report, the CSI report includes at least: an RI field and multiple fields, wherein each of the multiple fields indicates a compressed CSI corresponding to each of the tiers indicated by the RI field.

8. The UE according to claim 7, wherein If the CSI report is a rank-based CSI report, the CSI report includes at least: CSI Reference Signal RS Resource Indicator CRI field, RI field, and Precoded Matrix Indicator PMI portion, the PMI portion including the compressed CSI or backoff CSI corresponding to the RI indicated in the RI field; as well as In the case that the CSI report is a tiered CSI report, the CSI report includes at least: a CRI field, an RI field, a tier indicator LI field, and a PMI section, the PMI section including the compressed CSI or backtracked CSI corresponding to each tier of the RI indicated in the RI field.

9. The UE of claim 8, wherein the CSI report further includes a fallback indicator indicating whether the compressed CSI or the fallback CSI is included in the CSI report.

10. The UE of claim 8, wherein, in the absence of resources available for the first CSI compression model, the processor is further configured to: Discard the CSI report; or The PMI portion of the CSI report is discarded, and a CSI report without the PMI portion is sent to the base station.

11. A base station, comprising: processor; as well as A transceiver, the transceiver being coupled to the processor, The processor is configured as follows: The transceiver receives information about the ability to compress Channel State Information (CSI) using a bilateral model from the user equipment (UE). At least one configuration corresponding to at least one CSI compression model for obtaining compressed CSI reports is sent to the UE via the transceiver. as well as The transceiver sends an indication to the UE corresponding to a first CSI compression model among the at least one CSI compression models, the first CSI compression model being associated with a CSI report configuration.

12. The base station of claim 11, wherein the at least one CSI compression model is determined by the base station based on the capability information.

13. The base station according to claim 11, wherein the capability information includes: First information regarding whether the CSI compression using the bilateral model is supported by the UE.

14. The base station of claim 13, wherein when the CSI compression using a bilateral model is supported by the UE, the capability information further includes: The number of CSI compression models supported by the UE; Second information regarding whether at least one of the rank-based CSI reports and tier-based CSI reports is supported by the UE; The maximum rank supported by the CSI compression report for each CSI compression function or for each CSI compression model, where a CSI compression function is associated with one or more CSI compression models; as well as Third information regarding the number of uplink control information (UCI) bits used in the compressed CSI report.

15. The base station according to claim 14, wherein When the rank-based CSI report is supported by the UE, the third information includes: For each CSI compression function or for each CSI compression model, the number of UCI bits corresponding to each rank of the compressed CSI report; as well as When the layer-by-layer CSI reporting is supported by the UE, the third information includes: the number of UCI bits corresponding to the compressed CSI report for each transport layer, for each CSI compression function or for each CSI compression model.

16. The base station according to claim 11, wherein the configuration in the at least one configuration includes: The identifier ID corresponding to the CSI compression model; For the aforementioned CSI compression model, the maximum rank supported by the compressed CSI report; When a rank-based CSI report is configured, the number of uplink control information (UCI) bits used for the compressed CSI report corresponding to each rank; as well as When layer-by-layer CSI reporting is configured, the number of UCI bits used for the compressed CSI report corresponding to each transport layer.

17. The base station of claim 16, wherein the processor is further configured to: Receive the CSI report corresponding to the CSI report configuration, and If the CSI report is a rank-based CSI report, the CSI report includes at least: The rank indicator RI field and a single field for the compressed CSI corresponding to the RI indicated in the RI field; as well as In the case that the CSI report is a tiered CSI report, the CSI report includes at least: an RI field and multiple fields, wherein each of the multiple fields indicates a compressed CSI corresponding to each of the tiers indicated by the RI field.

18. The base station according to claim 17, wherein: When the CSI report is a rank-based CSI report, the CSI report includes at least: a CSI reference signal RS resource indicator (CRI) field, an RI field, and a precoded matrix indicator (PMI) portion, the PMI portion including the compressed CSI or backoff CSI corresponding to the RI indicated in the RI field; and In the case that the CSI report is a tiered CSI report, the CSI report includes at least: a CRI field, an RI field, a tier indicator LI field, and a PMI section, the PMI section including the compressed CSI or backtracked CSI corresponding to each tier of the RI indicated in the RI field.

19. The base station of claim 18, wherein the CSI report further includes a fallback indicator indicating whether the compressed CSI or the fallback CSI is included in the CSI report.

20. The base station of claim 18, wherein when there are no resources available for the first CSI compression model in the UE, the received CSI report does not include the PMI portion.

Images