Methods for signaling of channel and / or interference measurements based on DMRS for CSI reporting
Integrating DMRS configuration into the CSI framework for channel and interference measurements addresses inefficiencies in existing systems, enhancing accuracy and reducing resource overhead, resulting in improved throughput and energy efficiency.
Patent Information
- Application Number
- PCT/IB2026/054496
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-06
- Filing Date
- 2026-05-06
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems face inefficiencies in channel and interference measurements due to the reliance on sparse and resource-intensive CSI-RS, with DMRS-based CSI feedback not being adequately integrated into the CSI framework.
Integrate DMRS configuration information into the CSI framework for channel and interference measurements, allowing UEs to compute CSI based on DMRS, reducing the need for frequent CSI-RS transmissions and enhancing accuracy.
This approach provides more accurate and frequent CSI feedback, leading to improved throughput and energy savings for both network and UE, while minimizing resource overhead.
Smart Images

Figure IMGF000006_0001 
Figure IMGF000006_0002 
Figure IMGF000007_0001
Abstract
Description
METHODS FOR SIGNALING OF CHANNEL AND / OR INTERFERENCE MEASUREMENTS BASED ON DMRS FOR CSI REPORTINGRELATED APPLICATIONS
[0001] This application claims the benefit of U.S. Provisional Patent Application No.63 / 800,852, filed May 6, 2025, the disclosure of which is hereby incorporated herein by reference in its entirety.TECHNICAL FIELD
[0002] The present disclosure relates to a wireless communication network and, more specifically, to channel and / or interference measurements for Channel State Information (CSI) measurement and reporting.BACKGROUND CSI Feedback
[0003] For CSI feedback, NR has adopted an implicit channel state information (CSI) mechanism where a UE feeds back the downlink CSI including typically a transmission rank indicator (RI), a precoder matrix indicator (PMI), and channel quality indicator (CQI) for each codeword. The CQI / RI / PMI report can be either wideband or subband based on configuration.
[0004] The RI corresponds to a recommended number of layers that are to be spatially multiplexed and thus transmitted at the same time and frequency resources over the effective channel; the PMI identifies a recommended precoding matrix to use; the CQI represents a recommended modulation level (i.e. QPSK, 16QAM, etc.) and coding rate for each codeword or transport block (TB). NR supports transmission of one or two codewords to a UE in a slot where two codewords are used for 5 to 8 layer transmission, and one codeword is used for 1 to 4 layer transmission. There is thus a relation between a CQI and a SINR of the spatial layers over which the codewords are transmitted and for two codewords there are two CQI values fed back.Channel State Information Reference Signals (CSI-RS)
[0005] For CSI measurement and feedback, dedicated reference signals called CSI-RS are defined. A CSI-RS resource consists of between 1 and 32 CSI-RS ports and each port is typically transmitted on each transmit antenna (or virtual transmit antenna in case the port is precoded and mapped to multiple transmit antennas). The CSI-RS resource is used by a UE to measure downlinkchannel between each of the transmit antenna ports and each of its receive antenna ports. The antenna ports are also referred to as CSI-RS ports. The supported number of antenna ports in NR are {1,2,4,8,12,16,24,32,48,64,128}. By measuring the received CSI-RS, a UE can estimate the channel that the CSI-RS is traversing, including the radio propagation channel, potential precoding or beamforming, and antenna gains. The CSI-RS for the above purpose is also referred to as NonZero Power (NZP) CSI-RS but there are also zero power (ZP) CSI-RS used for other purposes than coherent channel measurements.
[0006] CSI-RS can be configured to be transmitted in certain REs in a slot and certain slots. Figure 1 shows an example of a CSI-RS resource mapped to REs for 12 antenna ports, where IRE per RB per port is shown.
[0007] In addition, interference measurement resource for CSI feedback (CSI-IM) is also defined in NR for a UE to measure interference. A CSI-IM resource contains 4 REs, either 4 adjacent RE in frequency in the same OFDM symbol or 2 by 2 adjacent REs in both time and frequency in a slot. By measuring both the channel based on NZP CSI-RS and the interference based on CSI-IM, a UE can estimate the effective channel and noise plus interference to better determine the CSI, i.e. RI, PMI, and the CQI.
[0008] Furthermore, a UE in NR may be configured to measure interference based on one or multiple NZP CSI-RS resource.CSI framework in NR
[0009] In NR, a UE can be RRC configured with multiple CSI reporting settings and multiple CSI resource settings. Different CSI resource settings can be configured for channel and interference measurements. For each CSI reporting setting, a UE feeds back a CSI report.
[0010] Each CSI resource setting can contain a list of CSI resource sets where the list is a choice between one of the following:• The list is comprised of references to either or both of NZP CSI-RS resource set(s) and SSB set(s)• The list can be comprised of references to CSI-IM resource set(s).
[0011] Each NZP CSI-RS resource set can contain up to 8 NZP CSI-RS resources. The number of CSI-IM resources in a CSI-IM resource set is equal to the number of NZP CSI-RS resources in the NZP CSI-RS resource set used for channel measurement.
[0012] Each CSI reporting setting can contain the following information:• An identifier of resource setting containing NZP CSI-RS or SSB resources for channel measurementOptionally, an identifier of resource setting containing CSI-IM resources for interference measurement• Optionally, an identifier of resource setting containing NZP CSI-RS resources for interference measurement• Time-domain behavior for CSI reporting, i.e. periodic, semi-persistent, or aperiodic reporting• Frequency granularity for CQI and PMI, i.e. wideband CQI vs subband CQI, and wideband PMI vs subband PMI• CSI parameters to be reported such as RI, PMI, CQI, layer indicator (LI) and CSI-RS resource indicator (CRI) in case of multiple NZP CSI-RS resources in a resource set • Codebook configuration, codebook types (i.e., type I or II), and codebook subset restriction • Measurement restriction• Information of which CQI table to use for CSI feedback (note that there are 3 different CQI tables defined in NR Rel-15 with different combination of modulation schemes and code rates suitable for different applications).
[0013] When a NZP CSI-RS resource set of a CSI resource setting for channel measurement contains multiple NZP CSI-RS resources, one of the NZP CSI-RS resources is selected by a UE. In this case, a NZP CSI-RS resource indicator (CRI) is also reported by the UE as part of the CSI report to indicate to the gNB about the selected NZP CSI-RS resource in the NZP CSI-RS resource set, together with RI, PMI and CQI associated with the selected NZP CSI-RS resource.
[0014] For aperiodic CSI reporting in NR, more than one CSI reporting settings with different CSI resource settings for channel measurement and / or CSI resource settings for interference measurement can be configured and triggered at the same time with a DCI. In this case, multiple CSI reports are aggregated and sent from the UE to the gNB in a single PUSCH transmission. This is done by defining multiple CSI triggering states, with each CSI triggering state including up to 16 CSI reporting settings in NR. A CSI request field in an uplink DCI (i.e., DCI format 0-1) is used to select one of the triggering states for CSI reporting.
[0015] In NR, the following types of CSI reporting are supported:• Periodic CSI Reporting: CSI is reported periodically by the UE. Parameters such as periodicity and slot offset are configured semi-statically, by higher layer signaling from the gNB to the UE.• Aperiodic CSI Reporting (AP CSI Reporting): This type of CSI reporting involves a singleshot (i.e., one time) CSI report by the UE which is dynamically triggered by the gNB, e.g. by the DCI in Physical Downlink Control Channel (PDCCH). Some of the parametersrelated to the configuration of the aperiodic CSI report is semi-statically configured from the gNB to the UE but the triggering is dynamic.• Semi-Persistent CSI Reporting: similar to periodic CSI reporting, semi-persistent CSI reporting has a periodicity and slot offset which may be semi-statically configured by the gNB to the UE. However, a dynamic trigger from gNB to UE may be needed to allow the UE to begin semi-persistent CSI reporting. In some cases, a dynamic trigger from gNB to UE may be needed to command the UE to stop the semi-persistent transmission of CSI reports.
[0016] In NR, the following three types of CSI-RS transmissions are supported:• Periodic CSI-RS (P CSI-RS): CSI-RS is transmitted periodically in certain slots. This CSI- RS transmission is semi-statically configured using parameters such as CSI-RS resource, periodicity and slot offset.• Aperiodic CSI-RS (AP CSI-RS): This is a one-shot CSI-RS transmission that can happen in any slot. Here, one-shot means that CSI-RS transmission only happens once per trigger. The CSI-RS resources for aperiodic CSI-RS are semi-statically configured. The transmission of aperiodic CSI-RS is triggered by dynamic signaling through PDCCH using the CSI request field in UL DCI. One or multiple aperiodic CSI-RS resource(s) can be included in a CSI-RS resource set and the triggering of aperiodic CSI-RS is on a resource set basis.• Semi-Persistent CSI-RS (SP CSI-RS): Similar to periodic CSI-RS, resources for semi- persistent CSI-RS transmissions are semi-statically configured with parameters such as periodicity and slot offset. However, unlike periodic CSI-RS, dynamic signaling via MAC CE activation / deactivation is needed to activate / deactivate the CSI-RS transmission.
[0017] In the case of aperiodic CSI-RS and / or aperiodic CSI reporting, the gNB RRC configures the UE with ScCSI triggering states. Each triggering state contains the aperiodic CSI report setting to be triggered along with the associated aperiodic CSI-RS resource sets.DMRS Configuration
[0018] Demodulation reference signals (DMRS) are used for coherent demodulation of physical layer data channels, i.e., Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH), as well as of Physical Downlink Control Channel (PDCCH). The DMRS is confined to resource blocks carrying the associated physical layer channel and is mapped on allocated resource elements of the time-frequency resource grid such that the receiver can efficiently handle time / frequency-selective fading radio channels.
[0019] The mapping of DMRS to resource elements is configurable in both frequency and time domain. There are two mapping types in the frequency domain in the NR specification, i.e., type 1 and type 2. In addition, there are two mapping types in the time domain, i.e., mapping type A and type B, which defines the symbol position of the first OFDM symbol containing DMRS within a transmission interval.
[0020] The DMRS mapping in time domain can further be single-symbol based or doublesymbol based, where the latter means that DMRS is mapped in pairs of two adjacent OFDM symbols. For single symbol based DMRS, a UE can be configured with one, two, three, or four single-symbol DMRS in a slot. For double-symbol based DMRS, a UE can be configured with one or two such double-symbol DMRS in a slot. In scenarios with low Doppler or low frequency offset, it may be sufficient to configure front-loaded DMRS only, i.e. one single-symbol DMRS or one double-symbol DMRS, whereas in scenarios with high Doppler and / or carrier frequency offset, additional DMRS will be required in a slot.
[0021] Figures 2A and 2B show an example of type 1 and type 2 front-loaded DMRS with single-symbol and double-symbol DMRS and time domain mapping type A with first DMRS in the third OFDM symbol of a transmission interval of 14 symbols. We observe from this figure that type 1 and type 2 differ with respect to both the mapping structure and the number of supported DMRS CDM groups where type 1 support 2 CDM groups and Type 2 support 3 CDM groups.
[0022] A DMRS antenna port is mapped to the resource elements within one CDM group only. For single-symbol DMRS, two or four (in Rel-18, the original NR design was extended to support 4 ports in each CDM group) antenna ports can be mapped to each CDM group whereas for double-symbol DMRS four or eight antenna ports can be mapped to each CDM group. Hence, for DMRS type 1 the maximum number of DMRS ports is four or eight for a single-symbol based DMRS configuration and eight or 16 for double-symbol based DMRS configuration (the latter values for both single and double symbol DMRS comes from the Rel-18 extension, if used). For DMRS type 2, the maximum number of DMRS ports is six or 12 for a single-symbol based DMRS configuration and twelve or 24 for double-symbol based DMRS configuration (the latter values for both single and double symbol DMRS comes from the Rel-18 extension, if used).
[0023] An orthogonal cover code (OCC) of length 2 (1. e., [+1, +1] or [+1, —1]) is used to separate antenna ports mapped in the same two resource elements within a CDM group in the original NR design. The OCC is applied in frequency domain (FD) as well as in time domain (TD) when double-symbol DMRS is configured. This is illustrated in Figures 2A and 2B for CDM group 0. In NR Rel-18, the OCC length in frequency domain was extended to length 4, while the time domain OCC was kept to length 2.
[0024] In NR Rel-15, the mapping of a PDSCH DMRS sequence r(m), m = 0,1, ... on antenna port Pj and subcarrier k in OFDM symbol I for the numerology index p is specified in 3GPP TS38.211 as14 / 7 + 2k' + A Configuration type 1&=i6n + k' + A Configuration type 2k' = 0,1i =T+i'77 = 0,1,...where w (fc') represents a frequency domain length-2 OCC code and wt(Z') represents a time domain length-2 OCC code. Table 1 and Table 2 show the PDSCH DMRS mapping parameters for configuration type 1 and type 2, respectively.Table 1. PDSCH DMRS mapping parameters for configuration type 1.CDM wfWt( / ')p group 2 A k' = 0 k' =l r = o r = i 1000 0 0 + 1 + 1 +1 +1 1001 0 0 + 1 -1 +1 +1 1002 1 1 + 1 + 1 +1 +1 1003 1 1 + 1 -1 +1 +1 1004 0 0 + 1 + 1 +1 -1 1005 0 0 + 1 -1 +1 -1 1006 1 1 + 1 + 1 +1 -11007 1 1 + 1 -1 +1 -1Table 2. PDSCH DMRS mapping parameters for configuration type 2.CDM wfT') lEt( / ')P group 2 A k' = 0 k' = i l' =0 / ' = 1 1000 0 0 +1 +1 +1 + 1 1001 0 0 +1 -1 +1 + 1 1002 1 2 +1 +1 +1 + 1 1003 1 2 +1 -1 +1 + 1 1004 2 4 +1 +1 +1 + 1 1005 2 4 +1 -1 +1 + 1 1006 0 0 +1 +1 +1 -1 1007 0 0 +1 -1 +1 -1 1008 1 2 +1 +1 +1 -1 1009 1 2 +1 -1 +1 -1 1010 2 4 +1 +1 +1 -11011 2 4 +1 -1 +1 -1 NOTE: The extended mapping table for Rel-18 are not shown here for brevity.
[0025] For PDSCH mapping type A, DMRS mapping is relative to slot boundary. That is, the first front-loaded DMRS symbol in DMRS mapping type A is in either the 3rdor 4thsymbol of theslot. In addition to the front-loaded DMRS, type A DMRS mapping can consist of up to 3 additional DMRS. Some examples of DMRS for mapping type A are shown in Figure 3 (note that PDSCH length of 14 symbols is assumed in the examples). The mappings with light and dark blue symbols reflect the cases when one or more additional symbols are added to the single-symbol mappings, which are depicted with light blue symbols, to obtain double-symbol mappings.
[0026] For PDSCH mapping type B, DMRS mapping is relative to transmission start. That is, the first DMRS symbol in DMRS mapping type B is in the first symbol in which type B PDSCH starts. Some examples of DMRS for mapping type B are shown in Figure 4.DMRS Sequence Generation
[0027] The DMRS sequence r(n) for both PDSCH and PUSCH when transform precoding is not enabled is defined byr(n) = ^=(1 - 2 • c(2n)) + j^=(l - 2 • c(2n + 1)).where the pseudo-random sequence c(i) is defined in clause 5.2.1 of3GPPTS38.211. The pseudo-random sequence generator is initialized withnit 21Wnlb<(+1+ 0 (2^™ + 1) + 217+ 2N^ + n’CID)mod 231where I is the OFDM symbol number within the slot, n^ S,f1 is the slot number within a frame, and •For PDSCH DMRS, / V^, Ajp 6 {0,1, ... ,65535} are given by the higher-layer parameters scramblingIDO and scrambling! D L respectively, in the DMRS-DownlinkConfig IE if provided and the PDSCH is scheduled by PDCCH using DCI format 1 1 or 1 2 with the CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI;• For PUSCH DMRS,Ajp G {0,1, ... ,65535} are given by the higher-layer parameters scramblingIDO and scramblingID 1 , respectively, in the DMRS-UplinkConfig IE if provided and the PUSCH is scheduled by DCI format 0 1 or 0 2, or by a PUSCH transmission with a configured grant;• For PDSCH DMRS, Ajp G {0,1, ...,65535} is given by the higher-layer parameter scramblingIDO in the DMRS-DownlinkConfig IE if provided and the PDSCH is scheduled by PDCCH using DCI format 1 0 with the CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI;• For PUSCH DMRS, Ajp G {0,1, ...,65535} is given by the higher-layer parameter scramblingIDO in the DMRS-UplinkConfig IE if provided and the PUSCH is scheduled by DCI format 0 1 or 0 2, or by a PUSCH transmission with a configured grant;N^cm= <De" otherwise;fisciD and A are given byo if the higher-layer parameter dmrs-Downlink in the DMRS-DownlinkConfig IE or dmrs-Uplink in the DMRS-UplinkConfig IE is provided, the corresponding fisciDand A are determined as-A > (nsciD A — 0 or A — 2nSCID 3 - 1I1 nSCID t - 1A = Awhere X is the CDM group index,o otherwise bynSCID -nSCIDA = 0
[0028] The quantity nSCIDG {0, 1} is given by the DMRS sequence initialization field, if present, in the DCI associated with the PDSCH transmission if DCI format 1 1 or 1 2 is used or the PUSCH transmission if DCI format 0 1 or 0 2 is used, or indicated by the higher layer parameter dmrs-Seqlnitialization, if present, for a Type 1 PUSCH transmission with a configured grant; otherwise nSCID= 0.SUMMARY
[0029] Systems and methods are disclosed for signaling of channel and / or interference measurements based on Demodulation Reference Signals (DMRS) for Channel State Information (CSI) reporting. In one embodiment, a method performed by a User Equipment (UE) for CSI reporting comprises receiving configuration information related to a CSI reporting configuration, receiving first signaling for CSI measurement and / or computation related to the CSI reporting configuration, and determining whether the configuration information related to the CSI reporting configuration indicates channel measurement based on DMRS or based on Non-Zero Power (NZP) CSI Reference Signal (CSI-RS) and / or Synchronization Signal Block (SSB). The method further comprises, if a result of the determining is that the configuration information related to the CSI reporting configuration indicates channel measurement based on DMRS, computing CSI based on DMRS. The method further comprises, if the result of the determining is that the configuration information related to the CSI reporting configuration indicates channel measurement based on NZP CSI-RS and / or SSB, computing CSI based on NZP CSI-RS and / or SSB. The method further comprises reporting the computed CSI to a network node. In this manner, more accurate CSIfeedback from the UE may be achieved as compared to CSI based on Non-Zero Power (NZP) CSI-RS and / or CSI for Interference Measurement (CSI-IM).
[0030] In one embodiment, computing CSI based on DMRS comprises computing the CSI based on one or more DMRS ports for channel measurement indicated in the first signaling.
[0031] In one embodiment, computing CSI based on DMRS comprises computing the CSI based on one or more DMRS ports for channel measurement indicated in the first signaling and based on one or more DMRS ports for interference measurement indicated in the first signaling.
[0032] In one embodiment, computing CSI based on NZP CSI-RS comprises computing the CSI based on one or more NZP CSI-RS and / or SSB ports for channel measurement indicated in the first signaling.
[0033] In one embodiment, computing CSI based on NZP CSI-RS comprises computing the CSI based on one or more NZP CSI-RS and / or SSB ports for channel measurement indicated in the first signaling and based on one or more DMRS ports for interference measurement indicated in the first signaling.
[0034] In one embodiment, the configuration information related to the CSI reporting configuration comprises an indication that indicates whether channel measurement is to be performed based on DMRS or NZP CSI-RS or SSB. In one embodiment, the indication comprised in the configuration information related to the CSI reporting configuration indicates that channel measurement is to be performed based on DMRS. In one embodiment, the configuration information related to the CSI reporting configuration further comprises an identifier that identifies a DMRS downlink configuration for channel measurement. In another embodiment, the configuration information related to the CSI reporting configuration further comprises a list of DMRS resources for channel measurement. In another embodiment, the configuration information related to the CSI reporting configuration further comprises a list of DMRS resources or a list of DMRS configurations for channel measurement. In one embodiment, the UE selects one DMRS resource or one DMRS configuration from the list to use for channel measurement. In one embodiment, the CSI report comprises information that indicates the selected DMRS resource or DMRS configuration used for channel measurement.
[0035] In one embodiment, the configuration information related to the CSI reporting configuration comprises an indication that indicates whether interference measurement is to be performed based on DMRS or CSI-IM. In one embodiment, the indication comprised in the configuration information related to the CSI reporting configuration indicates that interference measurement is to be performed based on DMRS. In one embodiment, the configuration information related to the CSI reporting configuration further comprises an identifier that identifiesa DMRS downlink configuration for interference measurement. In another embodiment, the configuration information related to the CSI reporting configuration further comprises a list of DMRS resources for interference measurement. In another embodiment, the configuration information related to the CSI reporting configuration further comprises a list of DMRS resources or a list of DMRS configurations for interference measurement. In one embodiment, the UE selects one DMRS resource or one DMRS configuration from the list to use for interference measurement. In one embodiment, the CSI report comprises information that indicates the selected DMRS resource or DMRS configuration used for interference measurement.
[0036] In one embodiment, the configuration information related to the CSI reporting configuration comprises an indication that indicates that both channel measurement and interference measurement are to be performed based on the same DMRS resource(s) or the same DMRS configuration(s).
[0037] In one embodiment, the configuration information related to the CSI reporting configuration comprises information that provides a pair-wise configuration of channel measurement configuration(s) or resource(s) and interference measurement configuration(s) or resource(s).
[0038] In one embodiment, the configuration information related to the CSI reporting configuration comprises an indication that indicates that channel measurement is to be performed based on DMRS, and the DMRS resource(s) or DMRS configuration s) to be used for channel measurement are predefined.
[0039] In one embodiment, the method further comprises receiving configuration information about a DMRS configuration, wherein the configuration information related to the CSI reporting configuration comprises an indication that indicates that channel measurement is to be performed based on DMRS where the DMRS are defined by the DMRS configuration.
[0040] In one embodiment, the configuration information related to the CSI reporting configuration comprises information that configures the UE to report a channel quality indicator, CQI, based on DMRS as the CSI reporting quantity.
[0041] In one embodiment, the configuration information related to the CSI reporting configuration comprises information that configures the UE to report a rank indicator (RI) and channel quality indicator (CQI) based on DMRS as the CSI reporting quantity.
[0042] In one embodiment, the configuration information related to the CSI reporting configuration comprises information that configures the UE to report a layer 1 reference signal received power (Ll-RSRP) based on DMRS as the CSI reporting quantity.
[0043] In one embodiment, the configuration information related to the CSI reporting configuration comprises information that configures the UE to report layer 1 signal to interference plus noise ratio (Ll-SINR) based on DMRS as the CSI reporting quantity.
[0044] In one embodiment, the first signaling is via layer 2 signaling or via downlink control information (DCI) in a physical downlink control channel (PDCCH).
[0045] In one embodiment, the method further comprises receiving second signaling that triggers the reporting of the computed CSI to the network node.
[0046] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE for CSI reporting comprises a communication interface comprising a transmitter and a receiver. The UE further comprises processing circuitry associated with the communication interface. The processing circuitry is configured to cause the UE to receive configuration information related to a CSI reporting configuration, receive first signaling for CSI measurement and / or computation related to the CSI reporting configuration, and determine whether the configuration information related to the CSI reporting configuration indicates channel measurement based on DMRS or based on NZP CSI-RS and / or SSB. The processing circuitry is further configured to cause the UE to, if a result of the determining is that the configuration information related to the CSI reporting configuration indicates channel measurement based on DMRS, computing CSI based on DMRS. The processing circuitry is further configured to cause the UE to, if the result of the determining is that the configuration information related to the CSI reporting configuration indicates channel measurement based on NZP CSI-RS and / or SSB, compute CSI based on NZP CSI-RS and / or SSB. The processing circuitry is further configured to cause the UE to report the computed CSI to a network node.
[0047] Embodiments of a method performed by a network node are also disclosed. In one embodiment, a method performed by a network node for configuration of CSI reporting comprises transmitting configuration information related to a CSI reporting configuration to a UE wherein the configuration information related to the CSI reporting configuration comprises information that indicates whether channel measurement is to be performed by the UE based on DMRS or based on NZP CSI-RS and / or SSB.
[0048] In one embodiment, the method further comprises transmitting, to the UE, first signaling for CSI measurement and / or computation related to the CSI reporting configuration.
[0049] In one embodiment, the method further comprises receiving, from the UE, a report (e.g., a CSI report) comprising CSI in accordance with the CSI reporting configuration.
[0050] Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node for configuration of CSI reporting comprises processing circuitryconfigured to cause the network node to transmit configuration information related to a CSI reporting configuration to a UE wherein the configuration information related to the CSI reporting configuration comprises information that indicates whether channel measurement is to be performed by the UE based on DMRS or based on NZP CSI-RS and / or SSB.BRIEF DESCRIPTION OF THE DRAWINGS
[0051] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.
[0052] Figure 1 illustrates an example of RE allocation for a 12-port CSI-RS resource in NR.
[0053] Figures 2A and 2B illustrate front-loaded DMRS for configuration type 1 and type 2 where different CDM groups indicated by different colors.
[0054] Figure 3 illustrates examples of DMRS configurations for PDSCH Mapping Type A. The figure assumes that the PDSCH duration is the full slot of 14 symbols. If the scheduled PDSCH duration is shorter than the full slot of 14 symbols, the positions of the DMRS changes according to the specification TS 38.211.
[0055] Figure 4 illustrates examples of DMRS configurations for PDSCH Mapping Type B.
[0056] Figure 5 illustrates a comparison of CSI-RS-based and DMRS-based CQI.
[0057] Figure 6 is a flowchart showing the proposed DMRS based CSI reporting scheme, in accordance with embodiments of the present disclosure.
[0058] Figure 7 illustrates an example DMRS configuration in accordance with an embodiment of the present disclosure.
[0059] Figure 8 illustrates a first example embodiment of CSI reporting configuration.
[0060] Figure 9 illustrates a second example embodiment of CSI reporting configuration.
[0061] Figure 10 illustrates a third example embodiment of CSI reporting configuration.
[0062] Figure 11 is a flow chart that illustrates the operation of a network node (e.g., a RAN node such as, e.g., a gNB) for configuring a UE for CSI reporting, in accordance with an embodiment of the present disclosure.
[0063] Figure 12 shows an example of a communication system in accordance with some embodiments of the present disclosure.
[0064] Figure 13 is another example of a communication system according to some embodiments of the present disclosure.
[0065] Figure 14 shows a wireless device, which may be configured to operate in the communication system of Figure 12 or in the communication system of Figure 13.
[0066] Figure 15 shows a network node in accordance with some embodiments of the present disclosure.
[0067] Figure 16 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.DETAILED DESCRIPTION
[0068] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.
[0069] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
[0070] There currently exist certain challenge(s). The existing 3rdGeneration Partnership Project (3GPP) New Radio (NR) specification allows for a User Equipment (UE) to report the Channel State Information (CSI) for the experienced downlink (DL) channel conditions based on specific reference signals, namely, CSI Reference Signal (CSI-RS) and Synchronization Signal Block (SSB) (also referred to as Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) Block). Such reference signals are configured as part of the existing NR CSI framework. Such reference signals take up resource overhead and are sparse in time. CSI feedback based on Demodulation Reference Signal (DMRS) is more efficient as the UE can reuse DMRS it receives while receiving DL data to compute the CSI. However, how to signal DMRS related information in the CSI framework is an open problem to be solved.
[0071] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Systems and methods are disclosed herein that provide a mechanism to configure DMRS related information in the CSI framework for the UE to perform CSI based on channel and / or interference measurements performed on DMRS. This includes how to configure, signal (or trigger), and report such CSI based on DMRS measurements.
[0072] Embodiments of the present disclosure may include any one or more of the following aspects:• Mechanism(s) for how to configure DMRS configuration information for channel and / or interference measurement in a CSI framework,• Mechanism(s) for indicating DMRS ports corresponding to the DMRS configuration information that are to be used for channel and / or interference measurement(s),• Mechanism(s) for computing CSI reporting quantity(ies).
[0073] Certain embodiments may provide one or more of the following technical advantage(s). Embodiments of the present disclosure may achieve a more accurate CSI feedback from the UE as compared to CSI based on Non-Zero Power (NZP) CSI-RS and / or CSI for Interference Measurement (CSI-IM). The reception schemes used by the UE for Physical Downlink Shared Channel (PDSCH) / payload reception is now also used to send the channel state feedback to the network (which in turn will use the feedback to schedule future PDSCHs). Embodiments of the present disclosure may provide less aging in CSI reporting quantities from the UE as compared to CSI based on NZP CSI-RS and / or CSI-IM. A report can be provided based on DMRS associated with previously transmitted PDSCHs. These are expected to be more frequent than periodically scheduled CSI-RS and also will incur no additional RS overhead.
[0074] One difference between DMRS-based and CSI-RS-based Channel Quality Indicator (CQI) is provided in Figure 5 where it can be seen that DMRS-based CQI can be more frequent and, due to this, follow channel variations more accurately, providing more accurate feedback from the UE to the network on the channel state.
[0075] The teachings of certain embodiments may improve the accuracy of channel quality indication which should lead to throughput improvement. Also, since the proposed solution leads to less frequency CSI-RS transmissions, the proposed solution also leads to energy savings for both the network and UE. The network saves energy as it does not have to transmit CSI-RS frequently. The UE saves energy as it does not have to measure CSI-RS with large number of ports frequently and does not need to compute the precoder matrix based on CSI-RS measurements frequently.
[0076] Note that the description herein uses terminology from NR to explain and expand on Radio Resource Control (RRC) and Layer 1 (Ll) / Layer 2 (L2) functionality. However, it should be understood that the exact naming and functionality of related functionality in e.g. a 6thGeneration (6G) specification could be different, but still the overall functionality of the solution(s) disclosed herein would still apply.
[0077] Figure 6 is a flow chart that illustrates the operation of a UE for an exemplary embodiment of the proposed DMRS based CSI reporting procedure. The steps of the procedure are described below.
[0078] In Step 600, the UE receives from a network node (e.g., a Radio Access Network (RAN) node such as, e.g., a gNodeB (gNB)) a first configuration including a DMRS configuration.An example DMRS configuration information element is shown in Figure 7 and includes a DMRS configuration ID that represents an identifier for the DMRS configuration. In some embodiments, a DMRS configuration ID is a field that is present in the DMRS configuration to uniquely identify the DMRS configuration within a serving cell (or component carrier) in case multiple DMRS configurations are configured within a serving cell (component carrier). In different embodiments, the motivation for such separation of DMRS configurations are:• different lengths of DMRS in terms of consecutive Orthogonal Frequency Division Multiplexing (OFDM) symbols used for DMRS (or different maxLength values) and / or different number of additional DMRSs, different bandwidths of the DMRS compared to the associated PDSCH / PUSCH, different scrambling IDs, different DMRS patterns (e.g. typel ortype2).• multiple bandwidth parts within a serving cell and each bandwidth part is associated with a DMRS configuration• Different number of Code Division Multiplexing (CDM) groups• DMRS used in PDCCH or PDSCH• Time domain property, e.g., periodic such as DL Semi-Persistent Scheduling (SPS) or aperiodic such as dynamic assignment• Different bandwidths of different DMRSs configurations (which allow the UE to compute, e.g. CSI for the PDSCH bandwidth or for the entire carrier bandwidth)• Different measurement occasions in time.
[0079] In some embodiments, the DMRS configuration ID field is not present in the DMRS configuration which may correspond to the case where there is only one DMRS configuration that is configured within a serving cell (or component carrier) and hence the DMRS configuration to be used by the UE for CSI reporting is uniquely identified. In an alternative embodiment, the network / specification may not want to distinguish between different DMRS configurations (e.g. different maxLength values) but instead have the UE measure on all DMRS resources it has been configured and provide an associated CSI report across such configurations. In yet another alternative embodiment, there may be another implicit rule for the UE to measure on certain DMRS resources in case the DMRS configuration ID field is not present in DMRS-DownlinkConfig IE. For example, the UE may measure on the DMRS resource associated to the lowest configuration ID, or in DMRS resource(s) chosen by the UE (here the UE can decide which resource(s) is( / are) more important to measure upon).
[0080] In another embodiment, the DMRS configuration is optional to include, and if left out, the UE behavior is determined by 3GPP specification. For example, when the network triggers aDMRS-based CSI report, the UE can assume that it shall measure on the provided DMRS configuration(s) by the network, e.g. “In case the UE receives a trigger for DMRS-based CSI and no dmrs-DownlinkConfigID has been provided in the DMRS-DownlinkConfig, the UE shall measure CSI on the received DMRS resource associated with PDSCH”.
[0081] In another embodiment, the DMRS configuration is pre-defined in the specification, e.g. default DMRS configuration such as the DMRS used in PDCCH in a control resource set (CORESET) or DMRS used in PDSCH carrying system common signaling, such as System Information Block 1 (SIB1), paging, Msg4. Another example using default DMRS configuration is the group common signaling, that multiple UEs are listening to a same PDCCH scrambled with same Radio Network Temporary Identity (RNTI), e.g. the DCI format 2 3 with SRS-TCP-RNTI (i.e., the RNTI specifically used for controlling the transmission power of Sounding Reference Signal (SRS)) in NR, and each UE derives partial of or all of the information from the PDSCH. For such cases an explicit DMRS configuration via higher layer signaling may be unnecessary. The pre-defined DMRS configuration can be a set of fixed parameters including antenna port index, DMRS type and mapping type / pattern, e.g., the antenna port index 0 with DMRS type 1. In a further embodiment, some of the DMRS configuration parameters can be pre-configured in MIB or SIB1, e.g. the mapping type / pattern is preconfigured as Type A or Type B.
[0082] For the purpose of defining a configuration ID for DMRS, different DMRS configurations can be seen as different DMRS resources which the UE is configured to measure and report based upon. With that, there is a maximum number of DMRS configurations / resource which a UE can be configured with. Denote that maximum number by maxNrofCSI-DMRS-Resource. The highlighted line in Figures 2A, 2B, and 3-7 in that case may be changed todmrs-DownlinkConfigID INTEGER (0... maxNrofCSI-DMRS-Resource-1) OPTIONAL, — Need S
[0083] The field maxNrofCSI-DMRS-Resource may be the maximum number of DMRS configurations that can possible be configured by a serving cell / component carrier.
[0084] In Step 602, the UE receives from the network node a second configuration including information related to a CSI reporting configuration.
[0085] A first example embodiment of CSI reporting configuration is shown in Figure 8. Each box shown in the example embodiment may represent an information element or a signaling structure.
[0086] In this example embodiment, the field ‘resourcesForChannelMeasuremenf refers to a CSI-ResourceConfig which contains information related to which type of reference signal(s) (e.g., NZP CSI-RS or DMRS) is to be used for channel measurement. In different embodiments, such reference signal could be one of a choice of reference signals (e.g. NZP CSI-RS or DMRS) / configuration IDs, or, multiple reference signals ( / configuration IDs). Below, the embodiment of a choice of reference signal is shown (e.g. Figure 8).
[0087] In the first CSI-ResourceConfig (shown in upper part of Figure 8), a field (e.g., ‘ChannelMeasuremenf ) signals a choice between NZP CSI-RS and DMRS for channel measurement. If the field ‘ChannelMeasuremenf signals NZP CSI-RS for channel measurement, then a field ‘nzp-CSI-RS-ResourceSetLisf can be configured. The field ‘nzp-CSI-RS-ResourceSetLisf refers to a list of NZP-CSI-RS-ResourceSets where each NZP-CSI-RS-ResourceSet consists of a set of NZP CSI-RS resources. nNZP-CSI-RS-ResourceSet, a field ‘nzp-CSI-RS-Resources’ refers to one or more NZP-CSI-RS resources. Fields that provide information related to a NZP CSI-RS resource are configured within each NZP-CSI-RS resource configuration. Note that in some cases only a single NZP CSI-RS resource set may be configured as part of ‘nzp-CSI-RS-ResourceSetLisf and / or a single NZP CSI-RS resource may be configured as part of ‘NZP-CSI-RS-ResourceSef .
[0088] If the field ‘ChannelMeasuremenf signals DMRS for channel measurement, then a field ‘dmrs-DownlinkConfigID’ or a list of DMRS resources, e.g., ‘dmrs-DownlinkConfigLisf or ‘csi-DMRS-ResourceLisf can be configured for channel measurement corresponding to the CSI-ReportConfig. The ‘dmrs-DownlinkConfigID’ field points to the identifier for DMRS configuration as defined in Figures 2A, 2B, and 3-7, or the fields ‘dmrs-DownlinkConfigLisf or ‘csi-DMRS-ResourceSetLisf point to a list of DMRS configurations / resources. From ‘dmrs-DownlinkConfiglD’ or ‘dmrs-DownlinkConfigLisf or ‘csi-DMRS-ResourceSetLisf, the UE determines which DMRS configuration(s) or DMRS resource(s) to use when performing channel measurement on DMRS. In case no explicit DMRS config ID has been provided to the UE in step 600, the UE can assume it shall compute a CSI report based on the single DMRS configuration and / or perform measurements across multiple DMRS configurations. In this case ‘dmrs-DownlinkConfiglD’ would be replaced with an indicator / field indicating DMRS e.g., ‘dmrs’ (see step 600 for more information). Alternatively, the UE can assume it shall compute a CSI report based on channel measurements performed on the DMRS with which PDSCH is scheduled when ‘dmrs-DownlinkConfigID’ is replaced with an indicator / field indicating DMRS e.g., ‘dmrs’. In some embodiments, when a list of DMRS configurations / resources is configured (e.g., either via ‘dmrs-DownlinkConfigLisf or ‘csi-DMRS-ResourceSetList’), the UE may select one DMRSconfiguration / resource to perform channel measurement. In one further embodiment, which DMRS configuration / resource to perform channel measurement on is prespecified in 3GPP specifications. In another further embodiment, an indicator indicating the one DMRS configuration / resource chosen by the UE to perform channel measurement is included as part of the DMRS based CSI report.
[0089] In the second CSI-ResourceConfig (shown in lower part of Figure 8), a field (e.g., ‘InterferenceMeasuremenf ) signals a choice between CSI-IM and DMRS for interference measurement. If the field ‘InterferenceMeasuremenf signals CSI-IM for interference measurement, then a field ‘csi-IM-ResourceSetLisf is configured. The field ‘csi-IM-ResourceSetLisf refers to a list of CSI-IM-ResourceSets where each CSI-IM-ResourceSet consists of a set of CSI-IM resources. In CSI-IM-ResourceSet, a field ‘csi-IM-Resources’ refers to one or more CSI-IM resources. Fields that provide information related to a CSI-IM resource are configured within each CSI-IM resource configuration. Note that in some cases only a single CSI-IM resource set may be configured as part of ‘csi-IM-ResourceSetLisf and / or a single CSI-IM resource may be configured as part of ‘CSI-IM-ResourceSef .
[0090] If the field ‘InterferenceMeasuremenf signals DMRS for interference measurement, then a field ‘dmrs-DownlinkConfigID’ or a list of DMRS configurations / resources, e.g., ‘dmrs-DownlinkConfigLisf or ‘csi-DMRS-ResourceLisf can be configured. The ‘dmrs-DownlinkConfiglD’ field points to the identifier for DMRS configuration as defined in Figures 2A, 2B, and 3-7, or the fields ‘dmrs-DownlinkConfigLisf or ‘csi-DMRS-ResourceLisf point to the list of DMRS configurations / resources. From ‘dmrs-DownlinkConfigID’ or ‘dmrs-DownlinkConfigLisf or ‘csi-DMRS-ResourceLisf, the UE determines which DMRS configuration(s) or DMRS resource(s) to use when performing interference measurement on DMRS. In case no explicit DMRS config ID has been provided to the UE in step 600, the UE can assume it shall compute a CSI report based on the single DMRS configuration and / or perform measurements across multiple DMRS configurations. In this case ‘dmrs-DownlinkConfigID’ would be replaced with e.g. ‘dmrs’ (see step 600 for more information). Alternatively, the UE can assume it shall compute a CSI report based on interference measurements performed on the DMRS with which PDSCH is scheduled when ‘dmrs-DownlinkConfigID’ is replaced with an indicator / field indicating DMRS e.g., ‘dmrs’. In some embodiments, when a list of DMRS configurations / resources is configured (e.g., either via ‘dmrs-DownlinkConfigLisf or ‘csi-DMRS-ResourceSetLisf ), the UE may select one DMRS configuration / resource to perform interference measurement. In one further embodiment, which DMRS configuration / resource to perform interference measurement on is prespecified in 3GPP specifications. In another furtherembodiment, an indicator indicating the one DMRS configuration / resource chosen by the UE to perform interference measurement is included as part of the DMRS based CSI report.
[0091] In one embodiment, CSI measurements and interference measurements are provided based on the same DMRS configuration(s) / resource(s). Based on the known DMRS sequence, the UE could estimate the channel and use that estimate to subtract the received channel measurement part from the total received signal. The residual signal, which consists of noise and interference, can be used as the measure of interference.
[0092] A second example embodiment of CSI reporting configuration is shown in Figure 9 where the wanted channel measurement configuration(s) / resource(s) and interference measurement configuration(s) / resource(s) are pair-wise configured. Each box shown in the example embodiment may represent an information element or a signaling structure. According to this second example embodiment, in CSI-ReportConfig, a common or joint field ‘resourcesForMeasurement’ refers to one or more CSI-MeasurementResourceSets. The common or joint field ‘resourcesForMeasurement’ provides information on one or more identifiers corresponding to one or more CSI-MeasurementResourceSets. Within each CSI-MeasurementResourceSet, a field ‘C Si-Measurement’ signals a choice between the following:• if ‘C Si-Measurement’ signals the choice of ‘CSI-MeasurementResourcePair’, then anNZP CSI-RS resource referred by the field ‘nzp-CSI-RS-Resource’ is used for channel measurement, and a CSI-IM resource referred by the field ‘csi-IM-Resource’ is used for interference measurement.• if ‘C Si-Measurement’ signals the choice of DMRS for channel and / or interference measurement, then a field ‘dmrs-DownlinkConfigID’ is configured. This ‘dmrs- DownlinkConfiglD’ field points to the identifier for DMRS configuration as defined in Figure 7. From the ‘dmrs-DownlinkConfigID’ field, the UE determines which DMRS configuration to use when performing channel and / or interference measurement on DMRS. In case no explicit DMRS config ID has been provided to the UE in Step 600, the UE can assume it shall compute a CSI report based on the single DMRS configuration and / or perform measurements across multiple DMRS configurations. In this case ‘dmrs- DownlinkConfiglD’ would be replaced with e.g. ‘dmrs’ (see Step 600 for more information). In some embodiments, to indicate both channel measurements and interference measurements needs to be performed based on DMRS, two fields may be configured as part of CSI-MeasrementResourcePair, e.g. CSI-MeasurementResourcePair’ = {‘dmrs’, ‘dmrs-IM’}.
[0093] It could be noted that other hierarchical configurations are also possible of the resources to be used, e.g. as shown in Figure 10. In this example embodiment, if ‘resourcesForMeasuremenf signals the choice of DMRS for channel and / or interference measurement, then a field ‘dmrs-DownlinkConfigID’ is configured. This ‘dmrs-DownlinkConfiglD’ field points to the identifier for DMRS configuration as defined in Figure 7. From the ‘dmrs-DownlinkConfigID’ field, the UE determines which DMRS configuration to use when performing channel and / or interference measurement on DMRS. In case no explicit DMRS config ID has been provided to the UE in Step 600, the UE can assume it shall compute a CSI report based on the single DMRS configuration.
[0094] In some embodiments, the UE may be configured to report CQI based on DMRS measurements as the CSI reporting quantity as part of the CSI reporting configuration. In some other embodiments, the UE may be configured to report Rank Indictor (RI) and CQI based on DMRS measurements as the CSI reporting quantities as part of CSI reporting configuration. In yet another embodiment, the UE may be configured to report LI -Reference Signal Received Power (RSRP) based on DMRS measurements as the CSI reporting quantity as part of the CSI reporting configuration. In another embodiment, the UE may be configured to report LI -Signal to Interference plus Noise Ratio (SINR) based on DMRS measurements as the CSI reporting quantity as part of the CSI reporting configuration.
[0095] In some embodiments, the CSI report can be configured with some pre-defined (e.g., in 3GPP specifications) DMRS to be used for channel and / or interference measurement without explicit configuration of dmrs-DownlinkConfigID. For example, the pre-defined DMRS can be the DMRS configured for PDSCH reception. In an example, the DMRS in PDSCH used for group common signaling or broadcast signaling, such as SIB1, paging, can be configured for channel and / or interference measurement for computing and reporting CSI.
[0096] In some embodiments, the field in resourcesForChannelMeasurement is made Optional in CSI-ReportConfig, and in some configuration instances the field resourcesForMeasurements is not configured. In such instances, the UE may or may not be configured with the field ‘dmrs-DownlinkConfigID’ or a list of DMRS configurations / resources, e.g., ‘dmrs-DownlinkConfigLisf or ‘csi-DMRS-ResourceLisf . In this case, there may be a rule defined in the specification saying that the UE can assume it shall compute a CSI report based on channel and / or interference measurements performed on DMRS corresponding to a DMRS configuration in DMRS-DownlinkConfig information element. For example, if the UE was not configured with the field ‘dmrs-DownlinkConfigID’ or a list of DMRS resources, e.g., ‘dmrs-DownlinkConfigLisf or ‘csi-DMRS-ResourceLisf, the UE can assume it shall compute a CSIreport based on channel and / or interference measurements performed on one or more of the DMRS configurations / resources configured by DMRS-DownlinkConfig. If the UE was configured with the field ‘dmrs-DownlinkConfigID’ or a list of DMRS resources ,e.g., ‘dmrs-DownlinkConfigList’ or ‘csi-DMRS-ResourceList’, the UE can assume it shall compute a CSI report based on channel and / or interference measurements performed on the one or more of the DMRS configuration / resources indicated by dmrs-DownlinkConfigID’ or ‘dmrs-DownlinkConfigList’ or ‘csi-DMRS-ResourceList’.
[0097] In Step 604, the UE receives a first signaling (e.g., a first trigger) for CSI measurement and / or computation related to the CSI reporting configuration.
[0098] In one embodiment, the first signaling of DMRS based CSI measurement and / or computation can be via layer 2 signaling, e.g. via Medium Access Control (MAC) Control Element (CE) signaling. A MAC CE can activate and / or deactivate a DMRS based CSI measurement and / or computation corresponding to the CSI reporting configuration which is configured in Step 602.
[0099] In another embodiment, the first signaling of DMRS based CSI measurement and / or computation can be signaled via a Downlink Control Information (DCI) in PDCCH. The DCI can be in e.g., a DL PDCCH indicating a DL assignment in PDSCH or a UL PDCCH scheduling a PUSCH. Following are embodiments related to the first signaling for CSI measurement and / or computation based on a DCI received in PDCCH:• In one embodiment, a first bit field in DCI may indicate explicitly which DMRS port(s) are to be used for channel measurement and / or interference measurement corresponding to CSI computation. Note that the DMRS port(s) indicated herein may also be used for downlink data demodulation, i.e. there is a corresponding PDSCH data layer for each of these DMRS port(s).• In another embodiment, a second bit field in DCI may indicate explicitly which DMRS port(s) are to be used for interference measurement only. Note that these DMRS port(s) may not be used for data demodulation, i.e. there is no corresponding PDSCH data layer for each of these ports. In some cases, there may not be DMRSs transmitted in these DMRS port(s) in which case these DMRS port(s) may be used to measure inter-cell interference.• In yet another embodiment, the DMRS port(s) indicated in the first bit field and second bit field in the DCI are received in different CDM groups.• In some embodiments, the DMRS port(s) indicated by the first field in DCI are used for both channel measurement and interference measurement.• In an alternative embodiment, the DMRS port(s) indicated by the first field in DCI are used for channel measurement, and the DMRS port(s) indicated by the second field in DCI are used for interference measurement.
[0100] In some embodiments, the DL DCI signaling (or trigger) includes one or more fields that include information related the DMRS ports to be used for channel measurement by the UE, and / or the DMRS ports to be used for interference measurement. In other embodiments, this is not explicitly signaled in relation to the triggering for CSI measurements, but rather stated in the specification that the DMRS ports to be used for measurements are the same as the DMRS ports used for PDSCH reception.
[0101] In a further embodiment, the DL DCI includes a field that activates or triggers the CSI reporting corresponding to the CSI reporting configuration. It could be noted that the trigger for measurement and / or computation and the trigger for CSI reporting could be the same. That is, in some embodiments, the first signaling received in Step 604 also triggers the CSI reporting in addition to triggering CSI measurement and / or computation (in this case, the second signaling of Step 610 is not necessary).
[0102] In Step 606, the UE determines whether channel measurement is to be based on the DMRS and / or NZP CSLRS according to the second configuration. This determination can be done according to various embodiments disclosed as part of Step 602.
[0103] In Step 608a, the UE computes the CSI reporting based on DMRS ports for channel measurement indicated in the first signaling, and optionally based on DMRS ports for interference measurement indicated in the first signaling.
[0104] The UE performs this step if channel measurements are configured based on DMRS configuration(s) / resource(s). Here, the UE may perform measurements based on resources / configuration indicated in DMRS-DownlinkConfig IE (as per embodiments in Step 600) as well as DMRS ports for channel measurements signaled in the first signaling. If no resources for interference measurements are configured in RRC, and / or no DMRS ports for interference measurement are signaled in the first signaling, or if the interference measurement resources share the same DMRS configuration as those for resource channel measurements, the UE could still estimate interference by estimating the intended channel and use that estimate to subtract the received channel part from the received signal. The residual signal, which consists of noise and interference, can be used to estimate interference. Alternatively, distinct DMRS configuration(s) / resource(s) for interference measurements may be configured different from the DMRS configuration(s) / resource(s) for channel measurements, and DMRS ports for interferencemeasurements can be signaled in the first signaling - the UE may measure upon these ports to compute interference aspects.
[0105] In an alternative embodiment, in Step 608b, the UE computes the CSI reporting based on non-DMRS ports for channel measurement indicated in the first signaling, and based on DMRS ports for interference measurement indicated in the first signaling.
[0106] In this alternative embodiment, the UE may be configured with CSI-RS resource sets and / or SSB resource sets as channel measurement resources. For interference measurements, the UE is configured with DMRS configuration(s) / resource(s) indicated in DMRS-DownlinkConfig IE (as previous embodiments), and the interference measurement DMRS ports are signaled in DCI in the first signaling. The UE computes CSI based on the interference measurements performed on these DMRS port(s) as well as channel measurements performed on CSI-RS and / or SSB resources sets.
[0107] In Step 610, the UE receives a second signaling (or second trigger) for CSI reporting related to the CSI reporting configuration. It could be noted that such second trigger is only received if Step 604 does not include a trigger for CSI reporting but only a trigger for CSI measurement and / or computation.
[0108] In one example, the second trigger for CSI reporting is indicated in an UL DCI. A bit field in the UL DCI is used to indicate which CSI report, e.g. associated with CSI report ID, the UE shall send in the UL transmission channels. In this case, the CSI report is a report based on channel and / or interference measured on DMRS as described in above embodiments.
[0109] In Step 612, the UE reports the computed CSI to the network node.
[0110] Figure 11 is a flow chart that illustrates the operation of a network node (e.g., a RAN node such as, e.g., a gNB) for configuring a UE for CSI reporting, in accordance with an embodiment of the present disclosure. Steps 1101, 1102, 1103, 1104, and 1105 correspond to Steps 600, 602, 604, 610, and 612 of Figure 6, but from the network node perspective. As such, details regarding Steps 600, 602, 604, 610, and 612 of Figure 6 are equally applicable here to Steps 1101, 1102, 1103, 1104, and 1105 of Figure 11.[OHl] In Step 1101, the network node transmits, to the UE, first configuration information regarding a DMRS configuration. The DMRS configuration may be as described above with respect to Step 600 of Figure 6.
[0112] In Step 1102, the network node transmits, to the UE, second configuration information related to a CSI reporting configuration. The CSI reporting configuration and the second configuration information may be as described above with respect to Step 602 of Figure 6.
[0113] In Step 1103, the network node transmits, to the UE, a first signaling (e.g., a first trigger) for CSI measurement and / or computation related to the CSI reporting configuration. The details regarding the first signaling are as described above with respect to Step 604 of Figure 6.
[0114] In Step 1104, the network node may optionally transmit, to the UE, a second trigger for CSI reporting, as described above with respect to Step 610 of Figure 6.
[0115] In Step 1105, the network node (or alternatively some other network node) receives a report (e.g., a CSI report) that includes CSI computed and reported by the UE in accordance with the CSI reporting configuration, as described above with respect to Step 612 of Figure 6.
[0116] Figure 12 shows an example of a communication system 1200 in accordance with some embodiments. The UE described in the embodiments above may be, for example, one of the UEs 1212 of Figure 12. The network node (e.g., gNB) described in the embodiments above may be, for example, one of the network nodes 1210 of Figure 12.
[0117] In the example, the communication system 1200 includes a telecommunications network 1202 that includes an access network 1204, such as a radio access network (RAN), and a core network 1206, which includes one or more core network nodes 1208. The access network 1204 includes one or more access network nodes or base stations of various types, access network nodes 1210A and 1210B are depicted (which may be collectively referred to as network nodes 1210), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 1204 may include more than one access network technology. The network nodes 1210 of access network 1204 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 1212A, 1212B, 1212C, and 1212D (one or more of which may be generally referred to as UEs 1212) to the core network 1206 over one or more wireless connections.
[0118] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 1202 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 1202 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 1202, including one or more access network nodes 1210 and / or core network nodes 1208.
[0119] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.
[0120] The network nodes 1210 facilitate direct or indirect connection of one or more UEs 1212 to the core network 1206 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1200 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1200 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0121] The UEs 1212 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1210 and other communication devices. Similarly, the network nodes 1208, 1210 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 1202) with the UEs 1212 and / or with other network nodes or equipment in the telecommunications network 1202 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 1202. More specifically, UEs 1212 may send messages, data, and / or other signals to network nodes 1208, 1210 or other elements of the telecommunicationsnetwork 1202 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 1208, 1210 may send messages, data, and other signals to UEs 1212, other network nodes 1208, 1210, and other devices in telecommunications network 1202 directly or indirectly. As one specific example, a core network node 1208 may transmit a particular message to a UE 1212 by transmitting the message to an access network node 1210 that will then transmit the message to the intended UE 1212. Similarly, a core network node 1208 may receive a particular message from a UE 1212 by receiving the message from an access network node 1210 that itself received the message from the UE 1212.
[0122] In the depicted example, the core network 1206 connects elements of the access network 1204 (e.g., one or more of the network nodes 1210) to one or more host computing systems, such as host 1216. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1206 includes one or more core network nodes (e.g., core network node 1208) of various types, one or more of which may be generally referred to as network nodes 1208. Network nodes 1208 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1208. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).
[0123] The host 1216 may be under the ownership or control of a service provider other than an operator or provider of the access network 1204 and / or the telecommunications network 1202. The host 1216 may be operated by the service provider or on behalf of the service provider. The host 1216 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remotedevices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0124] As a whole, the communication system 1200 of Figure 12 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1200 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 1200 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 1200 supporting different standards, protocols, or rule sets.
[0125] As one example, in certain embodiments, access network 1204 may contain some access network nodes 1210 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 1210 support (or the same access network nodes 1210 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 1202 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 1204 and / or a core network 1206 that supports multiple different standard generations or may include multiple access networks 1204 and / or multiple core networks 1206 with individual networks 1204, 1206 supporting different standard generations.
[0126] Telecommunications network 1202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 1202. For example, the telecommunications network 1202 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.
[0127] In some examples, one or more of the UEs 1212 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1204 on a predetermined schedule, when triggered byan internal or external event, or in response to requests from the access network 1204. Additionally, a UE may be configured for operating in single- or multi-RAT or multi -standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
[0128] In the example, the hub 1214 communicates with the access network 1204 to facilitate indirect communication between one or more UEs (e.g., UE 1212C and / or 1212D) and network nodes (e.g., network node 1210B). In some examples, the hub 1214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1214 may be a broadband router enabling access to the core network 1206 for the UEs. As another example, the hub 1214 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1210, or by executable code, script, process, or other instructions in the hub 1214.
[0129] As another example, the hub 1214 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1214 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1214 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0130] The hub 1214 may have a constant / persistent or intermittent connection to the network node 1210B. The hub 1214 may also allow for a different communication scheme and / or schedule between the hub 1214 and UEs (e.g., UE 1212C and / or 1212D), and between the hub 1214 and the core network 1206. In other examples, the hub 1214 is connected to the core network 1206 and / or one or more UEs via a wired connection. Moreover, the hub 1214 may be configured to connect to an M2M service provider over the access network 1204 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1210 while still connected via the hub 1214 via a wired or wireless connection. In some embodiments, the hub 1214 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1210B. In other embodiments, the hub 1214 may be a non-dedicated hub - that is, a device which is capable of operating to routecommunications between the UEs and network node 1210B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0131] Figure 13 is another example of a communication system 1300 according to some embodiments. As used herein, the communication system 1300 includes multiple access points (APs) 1310 (with four exemplary APs 1310A, 1310B, 1310C, and 1310D being depicted) and multiple wireless devices, referred to in the context of communication system 1300 as stations (ST As) 1312 (referred to individually as ST A 1312A, ST A 1312B, ST A 1312C, STA 1312D, and STA 1312E). STA 1312A is served by AP 1310A in a first basic service set (BSS) 1320A. STA 1312B and STA 1312C are served by AP 1310B in a second BSS, BSS 1320B. STA 1312D is served by AP 1310C in a third BSS, BSS 1320C. STA 1312E is served by AP 1310D in a fourth BSS, BSS 1320D. Stations 1312 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, headmounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 1312 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.
[0132] Each of STAs 1312 may connect through a radio link to one of APs 1310. For example, depending on location or channel conditions experienced by a given STA 1312, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.
[0133] Each AP 1310 may provide data connectivity to STAs 1312 connected to a particular AP 1310. As illustrated, APs 1310 may be connected to a data network 1330. In this way, APs 1310 may also provide data connectivity between STAs 1312 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 1312 and its serving AP 1310 may be used for providing various kinds of services to STA 1312, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 1312 and / or on a device linked to STA 1312. By way of example, Figure 13 illustrates an application service platform 1332 provided in data network 1330. The application(s) executed on STA 1312 and / or on one or more other devices linked to STA 1312 may use the radio link for datacommunication with one or more other STA 1312 and / or the application service platform 1332, thereby enabling utilization of the corresponding service(s) at STA 1312.
[0134] Figure 14 shows a wireless device 1400, which may be configured to operate in communication system 1200 of Figure 12 or in communication system 1300 of Figure 13. The wireless device 1400 may be alternatively referred to as a UE 1400, like a UE 1212 within the context of communication system 1200, or as a station (STA) 1400 or as a non-access-point station (non-AP STA) 1400, like a STA 1312 within the context of the communication system 1300, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0135] A wireless device 1400 may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 1400 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 1400 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 1400 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0136] In particular embodiments, wireless device 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input / output interface 1406, a power source 1408, a memory 1410, a communication interface 1412, and / or any other component, or any combination thereof. Certain embodiments of wireless device 1400 may include all or a subset of the components shown in Figure 14. The level of integration between the components may vary fromone embodiment of wireless device 1400 to another. In general, in a particular embodiment of wireless device 1400, processing circuitry 1402, input / output interface 1406, power source 1408, memory 1410, and communication interface 1412 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 1400. Further, certain embodiments of wireless devices 1400 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0137] The processing circuitry 1402 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1410. The processing circuitry 1402 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1402 may include multiple central processing units (CPUs).
[0138] In the example, the input / output interface 1406 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 1400. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
[0139] In some embodiments, the power source 1408 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 1408 may further include power circuitry for delivering power from the power source 1408 itself, and / or an external power source, to the various parts of wireless device 1400 via input circuitry or an interface such as an electrical power cable. Powersource 1408 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 1400 to which power is supplied.
[0140] The memory 1410 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1410 includes one or more programs 1414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1416. The memory 1410 may store, for use by wireless device 1400, any of a variety of various operating systems or combinations of operating systems.
[0141] The memory 1410 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1410 may allow wireless device 1400 to access instructions, programs, and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1410, which may be or comprise a device-readable storage medium.
[0142] The processing circuitry 1402 may be configured to communicate with an access network or other network via or using the communication interface 1412. The communication interface 1412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1422. The communication interface 1412 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 1418 and / or a receiver 1420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1418 and receiver 1420 may be coupled toone or more antennas (e.g., antenna 1422) and may share circuit components, software, or firmware, or alternatively be implemented separately.
[0143] In the illustrated embodiment, communication functions of the communication interface 1412 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0144] In particular embodiments, wireless device 1400 may provide an output of data captured via a sensor, through its communication interface 1412, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 1400 can be communicated through a wireless connection to a network node via another wireless device 1400. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0145] As another example, wireless device 1400 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 1400 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
[0146] Wireless device 1400, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voicecontrolled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 1400 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 1400 shown in Figure 14.
[0147] As yet another specific example, in an loT scenario, wireless device 1400 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 1400 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 1400 may implement the 3 GPP NB-IoT standard. In other scenarios, wireless device 1400 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.
[0148] In practice, any number of wireless devices 1400 may be used together with respect to a single use case. For example, a first wireless device 1400 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 1400 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 1400 may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 1400 can also include more than one of the functionalities described above. For example, wireless device 1400 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0149] Figure 15 shows a network node 1500 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 1500 may be configured to operate in communication system 1200 of Figure 12, like network nodes 1208 or 1210, or in communication system 1300 of Figure 13, like an AP 1310 or a station 1312.Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, 0-DU, O-CU).
[0150] Network nodes 1500 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 1500 may be a relay node or a relay donor node controlling a relay. Network nodes 1500 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an 0-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0151] Other examples of network nodes 1500 include multiple transmission point (multi -TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0152] In particular embodiments, network node 1500 includes a processing circuitry 1502, a memory 1504, a communication interface 1506, and a power source 1508. In general, in a particular embodiment of network node 1500, processing circuitry 1502, memory 1504, communication interface 1506, and power source 1508 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1500.
[0153] The network node 1500 may be composed of multiple distinct network entities (e.g., a NodeB entity and an RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 1500 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1500 may be configured to support multiple radio access technologies (RATs). In such embodiments, somecomponents may be duplicated (e.g., separate memories 1504 or portions of memory 1504 for different RATs) and some components may be reused (e.g., a same antenna 1510 may be shared by different RATs). The network node 1500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1500, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1500.
[0154] The processing circuitry 1502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 1504, to provide network node 1500 functionality.
[0155] In some embodiments, the processing circuitry 1502 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1502 includes one or more of radio frequency (RF) transceiver circuitry 1512 and baseband processing circuitry 1514. In some embodiments, the RF transceiver circuitry 1512 and the baseband processing circuitry 1514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1512 and baseband processing circuitry 1514 may be on the same chip or set of chips, boards, or units.
[0156] The memory 1504 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1502. The memory 1504 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1502 and utilized by the network node 1500. The memory 1504 may be used to store any calculations made by the processing circuitry 1502 and / or any data received via the communication interface 1506. In some embodiments, the processing circuitry 1502 and memory 1504 is integrated.
[0157] The communication interface 1506 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 1506 comprises port(s) / terminal(s) 1516 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 1500 may be capable of wireless communication and communication interface 1506 may also include radio front-end circuitry 1518 that may be coupled to, or in certain embodiments a part of, an antenna 1510. Particular embodiments of radio front-end circuitry 1518 include filter(s) 1520 and amplifier(s) 1522. The radio front-end circuitry 1518 may be connected to an antenna 1510 and processing circuitry 1502. The radio front-end circuitry may be configured to condition signals communicated between antenna 1510 and processing circuitry 1502. The radio front-end circuitry 1518 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1518 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 1520 and / or amplifiers 1522. The radio signal(s) may then be transmitted via the antenna 1510. Similarly, when receiving data, the antenna 1510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1518. The digital data may be passed to the processing circuitry 1502. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0158] In certain alternative embodiments, network node 1500 may be capable of wireless communication but does not include separate radio front-end circuitry 1518, instead, the processing circuitry 1502 includes radio front-end circuitry and is connected to the antenna 1510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1512 is part of the communication interface 1506. In still other embodiments, the communication interface 1506 includes one or more ports or terminals 1516, the radio front-end circuitry 1518, and the RF transceiver circuitry 1512, as part of a radio unit (not shown), and the communication interface 1506 communicates with the baseband processing circuitry 1514, which is part of a digital unit (not shown).
[0159] The antenna 1510 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1510 may be coupled to the radio front-end circuitry 1518 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1510 is separate from the network node 1500 and connectable to the network node 1500 through one or more interfaces or ports.
[0160] The antenna 1510, communication interface 1506, and / or the processing circuitry 1502 may be configured to perform some or all of the receiving operations and / or obtaining operationsdescribed herein as being performed by the network node 1500. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 1510, the communication interface 1506, and / or the processing circuitry 1502 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1500. Any information, data and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.
[0161] The power source 1508 provides power to the various components of network node 1500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1500 with power for performing the functionality described herein. For example, the network node 1500 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1508. As a further example, the power source 1508 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0162] Embodiments of the network node 1500 may include additional components beyond those shown in Figure 15 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1500 may include user interface equipment to allow input of information into the network node 1500 and to allow output of information from the network node 1500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1500.
[0163] Figure 16 is a block diagram illustrating a virtualization environment 1600 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1600 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, inembodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1600 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.
[0164] Applications 1602 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1600 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0165] Hardware 1604 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 1608 A and VM 1608B (which may be collectively referred to as VMs 1608), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1606 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 1608.
[0166] The VMs 1608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 1606. Different embodiments of the instance of a virtual appliance 1602 may be implemented on one or more of VMs 1608, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
[0167] In the context of NFV, each of the VMs 1608 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1608, and that part of hardware 1604 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 1608 on top of the hardware 1604 and corresponds to an application 1602.
[0168] Hardware 1604 may be implemented in a standalone network node with generic or specific components. Hardware 1604 may implement some functions via virtualization. Alternatively, hardware 1604 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1610, which, among others, oversees lifecycle management of applications 1602. In some embodiments, hardware 1604 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1612 which may alternatively be used for communication between hardware nodes and radio units.
[0169] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0170] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.
[0171] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.
[0172] Some exemplary embodiments of the present disclosure are as follows:Group A Embodiments
[0173] Embodiment 1: A method performed by a User Equipment, UE, for Channel State Information, CSI, reporting, the method comprising any one or more of the following: Receiving (602) configuration information related to a CSI reporting configuration; receiving (604) first signaling for CSI measurement and / or computation related to the CSI reporting configuration; determining (606) whether the configuration information related to the CSI reporting configuration indicate channel measurement based on Demodulation Reference Signal, DMRS, or based on NonZero Power, NZP, CSI Reference Signal, CSI-RS, and / or Synchronization Signal Block, SSB; if a result of the determining is that the configuration information related to the CSI reporting configuration indicates channel measurement based on DMRS, computing (608a) CSI based on DMRS; if the result of the determining is that the configuration information related to the CSI reporting configuration indicates channel measurement based on NZP CSI-RS and / or SSB, computing (608b) CSI based on NZP CSI-RS and / or SSB; and reporting (612) the computed CSI to a network node.
[0174] Embodiment 2: The method of embodiment 1, wherein computing (608a) CSI based on DMRS comprises computing the CSI (e.g., a CSI reporting quantity) based on one or more DMRS ports for channel measurement indicated in the first signaling.
[0175] Embodiment 3: The method of embodiment 1, wherein computing (608a) CSI based on DMRS comprises computing the CSI (e.g., a CSI reporting quantity) based on one or more DMRS ports for channel measurement indicated in the first signaling and based on one or more DMRS ports for interference measurement indicated in the first signaling.
[0176] Embodiment 4: The method of any of embodiments 1 to 3, wherein computing (608b) CSI based on NZP CSI-RS comprises computing the CSI (e.g., a CSI reporting quantity) based on one or more NZP CSI-RS and / or SSB ports for channel measurement indicated in the first signaling.
[0177] Embodiment 5: The method of any of embodiments 1 to 3, wherein computing (608b) CSI based on NZP CSI-RS comprises computing the CSI (e.g., a CSI reporting quantity) based on one or more NZP CSI-RS and / or SSB ports for channel measurement indicated in the first signaling and based on one or more DMRS ports for interference measurement indicated in the first signaling.
[0178] Embodiment 6: The method of any of embodiments 1 to 5, wherein the configuration information related to the CSI reporting configuration comprises an indication (e.g., a field) that indicates (e.g., explicitly) whether channel measurement is to be performed based on DMRS or NZP CSI-RS or SSB.
[0179] Embodiment 7: The method of embodiment 6, wherein indication comprised in the configuration information related to the CSI reporting configuration indicates that channel measurement is to be performed based on DMRS.
[0180] Embodiment 8: The method of embodiment 7, wherein the configuration information related to the CSI reporting configuration further comprises an identifier that identifies a DMRS downlink configuration for channel measurement.
[0181] Embodiment 9: The method of embodiment 7, wherein the configuration information related to the CSI reporting configuration further comprises a list of DMRS resources for channel measurement.
[0182] Embodiment 10: The method of embodiment 7, wherein the configuration information related to the CSI reporting configuration further comprises a list of DMRS resources or a list of DMRS configurations for channel measurement.
[0183] Embodiment 11: The method of embodiment 10, wherein the UE selects one DMRS resource or one DMRS configuration from the list to use for channel measurement.
[0184] Embodiment 12: The method of embodiment 11, wherein the CSI report comprises information that indicates the selected DMRS resource or DMRS configuration used for channel measurement.
[0185] Embodiment 13: The method of any of embodiments 1 to 12, wherein the configuration information related to the CSI reporting configuration comprises an indication (e.g., a field) that indicates (e.g., explicitly) whether interference measurement is to be performed based on DMRS or CSI-IM.
[0186] Embodiment 14: The method of embodiment 13, wherein indication comprised in the configuration information related to the CSI reporting configuration indicates that interference measurement is to be performed based on DMRS.
[0187] Embodiment 15: The method of embodiment 14, wherein the configuration information related to the CSI reporting configuration further comprises an identifier that identifies a DMRS downlink configuration for interference measurement.
[0188] Embodiment 16: The method of embodiment 14, wherein the configuration information related to the CSI reporting configuration further comprises a list of DMRS resources for interference measurement.
[0189] Embodiment 17: The method of embodiment 14, wherein the configuration information related to the CSI reporting configuration further comprises a list of DMRS resources or a list of DMRS configurations for interference measurement.
[0190] Embodiment 18: The method of embodiment 17, wherein the UE selects one DMRS resource or one DMRS configuration from the list to use for interference measurement.
[0191] Embodiment 19: The method of embodiment 18, wherein the CSI report comprises information that indicates the selected DMRS resource or DMRS configuration used for interference measurement.
[0192] Embodiment 20: The method of any of embodiments 1 to 5, wherein the configuration information related to the CSI reporting configuration comprises an indication (e.g., a field) that indicates (e.g., explicitly) that both channel measurement and interference measurement are to be performed based on the same DMRS resource(s) or the same DMRS configuration(s).
[0193] Embodiment 21 : The method of any of embodiments 1 to 5, wherein the configuration information related to the CSI reporting configuration comprises information that provides a pair-wise configuration of channel measurement configuration(s) or resource(s) and interference measurement configuration(s) or resource(s).
[0194] Embodiment 22: The method of any of embodiments 1 to 5, wherein the configuration information related to the CSI reporting configuration comprises an indication (e.g., a field) that indicates (e.g., explicitly) that channel measurement is to be performed based on DMRS, and the DMRS resource(s) or DMRS configuration(s) to be used for channel measurement are predefined.
[0195] Embodiment 23: The method of any of embodiments 1 to 5, further comprises receiving configuration information about a DMRS configuration, wherein the configuration information related to the CSI reporting configuration comprises an indication (e.g., a field) that indicates (e.g., explicitly) that channel measurement is to be performed based on DMRS where the DMRS are defined by the DMRS configuration.
[0196] Embodiment 24: The method of any of embodiments 1 to 23, wherein the configuration information related to the CSI reporting configuration comprises information that configures the UE to report CQI based on DMRS as the CSI reporting quantity.
[0197] Embodiment 25: The method of any of embodiments 1 to 23, wherein the configuration information related to the CSI reporting configuration comprises information that configures the UE to report RI and CQI based on DMRS as the CSI reporting quantity.
[0198] Embodiment 26: The method of any of embodiments 1 to 23, wherein the configuration information related to the CSI reporting configuration comprises information that configures the UE to report LI -RSRP based on DMRS as the CSI reporting quantity.
[0199] Embodiment 27: The method of any of embodiments 1 to 23, wherein the configuration information related to the CSI reporting configuration comprises information that configures the UE to report LI -SINR based on DMRS as the CSI reporting quantity.
[0200] Embodiment 28: The method of any of embodiments 1 to 27, wherein the first signaling is via layer 2 signaling (e.g., MAC CE signaling) or via DCI in PDCCH.
[0201] Embodiment 29: The method of any of embodiments 1 to 28, further comprising receiving (610) second signaling that triggers the reporting (612) of the computed CSI to the network node.
[0202] Embodiment 30: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.Group B Embodiments
[0203] Embodiment 31 : A method performed by a network node for configuration of Channel State Information, CSI, reporting, the method comprising: transmitting (1102) configuration information related to a CSI reporting configuration to a User Equipment, UE, wherein the configuration information related to the CSI reporting configuration comprises information that indicates whether channel measurement is to be performed by the UE based on Demodulation Reference Signal, DMRS, or based on Non-Zero Power, NZP, CSI Reference Signal, CSLRS, and / or Synchronization Signal Block, SSB.
[0204] Embodiment 32: The method of embodiment 31, further comprising transmitting (1103), to the UE, first signaling for CSI measurement and / or computation related to the CSI reporting configuration.
[0205] Embodiment 33: The method of embodiment 31 or 32, further comprising receiving (1105), from the UE, a report (e.g., a CSI report) comprising CSI in accordance with the CSI reporting configuration.
[0206] Embodiment 34: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.Group C Embodiments
[0207] Embodiment 35. A User Equipment, UE, comprising: processing circuitry configured to perform any of the operations of any of the Group A embodiments; and a power source configured to supply power to the processing circuitry.
[0208] Embodiment 36: A network node comprising: processing circuitry configured to perform any of the operations of any of the Group B embodiments; and a power source circuitry configured to supply power to the processing circuitry.
[0209] Embodiment 37: A User Equipment, UE, comprising: one or more antennas; communication interface connected to the one or more antennas and to processing circuitry; the processing circuitry being configured to perform any of the operations of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the UE.
Claims
CLAIMS1. A method performed by a User Equipment, UE, for Channel State Information, CSI, reporting, the method comprising:receiving (602) configuration information related to a CSI reporting configuration; receiving (604) first signaling for CSI measurement and / or computation related to the CSI reporting configuration;determining (606) whether the configuration information related to the CSI reporting configuration indicates channel measurement based on Demodulation Reference Signal, DMRS, or based on Non-Zero Power, NZP, CSI Reference Signal, CSLRS, and / or Synchronization Signal Block, SSB;if a result of the determining is that the configuration information related to the CSI reporting configuration indicates channel measurement based on DMRS, computing (608a) CSI based on DMRS;if the result of the determining is that the configuration information related to the CSI reporting configuration indicates channel measurement based on NZP CSI-RS and / or SSB, computing (608b) CSI based on NZP CSI-RS and / or SSB; andreporting (612) the computed CSI to a network node.
2. The method of claim 1, wherein computing (608a) CSI based on DMRS comprises computing the CSI based on one or more DMRS ports for channel measurement indicated in the first signaling.
3. The method of claim 1, wherein computing (608a) CSI based on DMRS comprises computing the CSI based on one or more DMRS ports for channel measurement indicated in the first signaling and based on one or more DMRS ports for interference measurement indicated in the first signaling.
4. The method of any of claims 1 to 3, wherein computing (608b) CSI based on NZP CSI-RS comprises computing the CSI based on one or more NZP CSI-RS and / or SSB ports for channel measurement indicated in the first signaling.
5. The method of any of claims 1 to 3, wherein computing (608b) CSI based on NZP CSI-RS comprises computing the CSI based on one or more NZP CSI-RS and / or SSB ports for channel measurement indicated in the first signaling and based on one or more DMRS ports for interferencemeasurement indicated in the first signaling.
6. The method of any of claims 1 to 5, wherein the configuration information related to the CSI reporting configuration comprises an indication that indicates whether channel measurement is to be performed based on DMRS or NZP CSI-RS or SSB.
7. The method of claim 6, wherein the indication comprised in the configuration information related to the CSI reporting configuration indicates that channel measurement is to be performed based on DMRS.
8. The method of claim 7, wherein the configuration information related to the CSI reporting configuration further comprises an identifier that identifies a DMRS downlink configuration for channel measurement.
9. The method of claim 7, wherein the configuration information related to the CSI reporting configuration further comprises a list of DMRS resources for channel measurement.
10. The method of claim 7, wherein the configuration information related to the CSI reporting configuration further comprises a list of DMRS resources or a list of DMRS configurations for channel measurement.
11. The method of claim 10, wherein the UE selects one DMRS resource or one DMRS configuration from the list to use for channel measurement.
12. The method of claim 11, wherein the CSI report comprises information that indicates the selected DMRS resource or DMRS configuration used for channel measurement.
13. The method of any of claims 1 to 12, wherein the configuration information related to the CSI reporting configuration comprises an indication that indicates whether interference measurement is to be performed based on DMRS or CSI-IM.
14. The method of claim 13, wherein indication comprised in the configuration information related to the CSI reporting configuration indicates that interference measurement is to be performed based on DMRS.
15. The method of claim 14, wherein the configuration information related to the CSI reporting configuration further comprises an identifier that identifies a DMRS downlink configuration for interference measurement.
16. The method of claim 14, wherein the configuration information related to the CSI reporting configuration further comprises a list of DMRS resources for interference measurement.
17. The method of claim 14, wherein the configuration information related to the CSI reporting configuration further comprises a list of DMRS resources or a list of DMRS configurations for interference measurement.
18. The method of claim 17, wherein the UE selects one DMRS resource or one DMRS configuration from the list to use for interference measurement.
19. The method of claim 18, wherein the CSI report comprises information that indicates the selected DMRS resource or DMRS configuration used for interference measurement.
20. The method of any of claims 1 to 5, wherein the configuration information related to the CSI reporting configuration comprises an indication that indicates that both channel measurement and interference measurement are to be performed based on the same DMRS resource(s) or the same DMRS configuration(s).
21. The method of any of claims 1 to 5, wherein the configuration information related to the CSI reporting configuration comprises information that provides a pair-wise configuration of channel measurement configuration(s) or resource(s) and interference measurement configuration(s) or resource(s).
22. The method of any of claims 1 to 5, wherein the configuration information related to the CSI reporting configuration comprises an indication that indicates that channel measurement is to be performed based on DMRS, and the DMRS resource(s) or DMRS configuration(s) to be used for channel measurement are predefined.
23. The method of any of claims 1 to 5, further comprises receiving configuration informationabout a DMRS configuration, wherein the configuration information related to the CSI reporting configuration comprises an indication that indicates that channel measurement is to be performed based on DMRS where the DMRS are defined by the DMRS configuration.
24. The method of any of claims 1 to 23, wherein the configuration information related to the CSI reporting configuration comprises information that configures the UE to report a channel quality indicator, CQI, based on DMRS as the CSI reporting quantity.
25. The method of any of claims 1 to 23, wherein the configuration information related to the CSI reporting configuration comprises information that configures the UE to report a rank indicator, RI, and channel quality indicator, CQI, based on DMRS as the CSI reporting quantity.
26. The method of any of claims 1 to 23, wherein the configuration information related to the CSI reporting configuration comprises information that configures the UE to report a layer 1 reference signal received power, Ll-RSRP, based on DMRS as the CSI reporting quantity.
27. The method of any of claims 1 to 23, wherein the configuration information related to the CSI reporting configuration comprises information that configures the UE to report layer 1 signal to interference plus noise ratio, Ll-SINR, based on DMRS as the CSI reporting quantity.
28. The method of any of claims 1 to 27, wherein the first signaling is via layer 2 signaling or via downlink control information, DCI, in a physical downlink control channel, PDCCH.
29. The method of any of claims 1 to 28, further comprising receiving (610) second signaling that triggers the reporting (612) of the computed CSI to the network node.
30. A User Equipment, UE, (1212; 1400) for Channel State Information, CSI, reporting, the UE (1212; 1400) comprising:a communication interface (1412) comprising a transmitter (1418) and a receiver (1420); processing circuitry (1402) associated with the communication interface (1412), the processing circuitry (1402) configured to cause the UE (1212; 1400) to:receive (602) configuration information related to a CSI reporting configuration; receive (604) first signaling for CSI measurement and / or computation related to the CSI reporting configuration;determine (606) whether the configuration information related to the CSI reporting configuration indicates channel measurement based on Demodulation Reference Signal, DMRS, or based on Non-Zero Power, NZP, CSI Reference Signal, CSI-RS, and / or Synchronization Signal Block, SSB;if a result of the determining is that the configuration information related to the CSI reporting configuration indicates channel measurement based on DMRS, computing (608a) CSI based on DMRS;if the result of the determining is that the configuration information related to the CSI reporting configuration indicates channel measurement based on NZP CSI-RS and / or SSB, compute (608b) CSI based on NZP CSI-RS and / or SSB; andreport (612) the computed CSI to a network node.
31. A method performed by a network node for configuration of Channel State Information, CSI, reporting, the method comprising:transmitting (1102) configuration information related to a CSI reporting configuration to a User Equipment, UE, wherein the configuration information related to the CSI reporting configuration comprises information that indicates whether channel measurement is to be performed by the UE based on Demodulation Reference Signal, DMRS, or based on Non-Zero Power, NZP, CSI Reference Signal, CSI-RS, and / or Synchronization Signal Block, SSB.
32. The method of claim 31, further comprising transmitting (1103), to the UE, first signaling for CSI measurement and / or computation related to the CSI reporting configuration.
33. The method of claim 31 or 32, further comprising receiving (1105), from the UE, a report comprising CSI in accordance with the CSI reporting configuration.
34. A network node (1210; 1500) for configuration of Channel State Information, CSI, reporting, the network node (1210; 1500) comprising processing circuitry (1502) configured to cause the network node (1210; 1500) to:transmit (1102) configuration information related to a CSI reporting configuration to a User Equipment, UE, wherein the configuration information related to the CSI reporting configuration comprises information that indicates whether channel measurement is to be performed by the UE based on Demodulation Reference Signal, DMRS, or based on Non-Zero Power, NZP, CSI Reference Signal, CSI-RS, and / or Synchronization Signal Block, SSB.
