Terminal, radio communication method, and base station

The terminal's CSI reporting mechanism addresses the challenge of inadequate CSI reporting by evaluating and reporting channel and interference measurements, improving downlink data transmission efficiency.

WO2026239581A1PCT designated stage Publication Date: 2026-11-19NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2025/017825
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-16
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in properly reporting channel state information (CSI) due to the lack of support for UE-initiated CSI reporting, which can lead to inadequate modulation and coding in downlink data transmission.

Method used

A terminal equipped with a receiving unit for setting information and a control unit to evaluate channel and interference measurement results, allowing appropriate reporting of UE-initiated CSI when specific conditions are met, utilizing various reference signals and reporting configurations.

Benefits of technology

Enables proper reporting of CSI, enhancing the accuracy of downlink data transmission by adapting modulation and coding based on dynamic channel and interference conditions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2025017825_19112026_PF_FP_ABST
    Figure JP2025017825_19112026_PF_FP_ABST
Patent Text Reader

Abstract

A terminal according to one aspect of the present disclosure is characterized by comprising: a receiving unit that receives setting information for reporting channel state information (UEI-CSI) initiated by the terminal; and a control unit that evaluates an event related to at least one of a channel measurement result and an interference measurement result on the basis of the setting information, and performs control to report the UEI-CSI when a specific condition related to the event is satisfied. According to one aspect of the present disclosure, CSI can be reported appropriately.
Need to check novelty before this filing date? Find Prior Art

Description

Terminal, wireless communication method, and base station

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) has been specified for the purpose of achieving higher data rates, lower latency, and the like (Non-Patent Document 1). Further, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of further increasing capacity, enhancing sophistication, and the like of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (also referred to as, for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later, etc.) are also under consideration.

[0004] 3GPP TS 36.300 V8.12.0 "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)", April 2010

[0005] In existing wireless communication systems (for example, NR), a terminal (user terminal, User Equipment (UE)) reports channel state information (CSI) to a network (NW, base station), whereby the NW can apply appropriate modulation and coding to downlink (DL) data.

[0006] The inventors are considering supporting UE-initiated CSI reporting (UEI-CSI reporting) in future wireless communication systems (e.g., 6G).

[0007] If UEI-CSI reporting is supported, the events / procedures for UEI-CSI reporting must be considered. Failure to do so may result in the inability to properly report CSIs.

[0008] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately report CSI.

[0009] A terminal according to one aspect of the present disclosure is characterized by comprising: a receiving unit that receives setting information for reporting channel state information (UEI-CSI) initiated by the terminal; and a control unit that evaluates an event related to at least one of the channel measurement results and interference measurement results based on the setting information, and controls the terminal to report the UEI-CSI when specific conditions related to the event are met.

[0010] According to one aspect of this disclosure, CSI can be properly reported.

[0011] Figure 1 shows an example of the UEIBR and UEI-CSI framework. Figure 2 shows an example of the schematic configuration of a wireless communication system according to one embodiment of this disclosure. Figure 3 shows an example of the configuration of a base station according to one embodiment of this disclosure. Figure 4 shows an example of the configuration of a terminal according to one embodiment of this disclosure. Figure 5 shows an example of the hardware configuration of a base station and terminal according to one embodiment of this disclosure.

[0012] (CSI Reporting) Rel. 15 In NR, a terminal (also called a user terminal, User Equipment (UE), etc.) generates (also called determining, calculating, estimating, measuring, etc.) Channel State Information (CSI) based on a Reference Signal (RS) (or a resource for said RS), and transmits (also called reporting, feedback, etc.) the generated CSI to the network (e.g., a base station). The CSI may be transmitted to the base station using, for example, an uplink control channel (e.g., a Physical Uplink Control Channel (PUCCH)) or an uplink shared channel (e.g., a Physical Uplink Shared Channel (PUSCH)).

[0013] The RS used to generate the CSI may be at least one of the following: Channel State Information Reference Signal (CSI-RS), Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, Synchronization Signal (SS), or Demodulation Reference Signal (DMRS).

[0014] The CSI-RS may include at least one of Non Zero Power (NZP) CSI-RS and CSI-Interference Management (CSI-Interference Measurement, CSI-IM). The SS / PBCH block is a block that includes SS and PBCH (and corresponding DMRS), and may be called an SS block (SSB), etc. The SS may also include at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS).

[0015] Furthermore, CSI may include at least one of the following: Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Block Resource Indicator (SSBRI, SSB Index), Layer Indicator (LI), Rank Indicator (RI), L1-RSRP (Layer 1 Reference Signal Received Power), L1-RSRQ (Reference Signal Received Quality), L1-SINR (Signal to Interference plus Noise Ratio), L1-SNR (Signal to Noise Ratio).

[0016] The UE may receive information regarding CSI reporting (report configuration information) and control CSI reporting based on that report configuration information. This report configuration information may be, for example, the "CSI-ReportConfig" information element (IE) of Radio Resource Control (RRC).

[0017] The reporting configuration information (for example, "CSI-ReportConfig" in RRC IE) may include, for example, at least one of the following: ◆ Information about the type of CSI report (report type information, for example, "reportConfigType" in RRC IE) ◆ Information about one or more quantities (one or more CSI parameters) of CSI to be reported (report quantity information, for example, "reportQuantity" in RRC IE) ◆ Information about the RS resources used to generate the quantity (the CSI parameter) (resource information, for example, "CSI-ResourceConfigId" in RRC IE) ◆ Information about the frequency domain to which the CSI report is applied (frequency domain information, for example, "reportFreqConfiguration" in RRC IE)

[0018] For example, the reporting type information may indicate a periodic CSI (P CSI) report, an aperiodic CSI (A CSI, AP CSI) report, or a semi-persistent CSI (SP CSI) report.

[0019] Furthermore, the reported quantity information may specify at least one combination of the above-mentioned CSI parameters (e.g., CRI, RI, PMI, CQI, LI, L1-RSRP, etc.).

[0020] Furthermore, the resource information may also be the ID of the RS resource. The RS resource may include, for example, a non-zero power CSI-RS resource or SSB and a CSI-IM resource (for example, a zero-power CSI-RS resource).

[0021] Furthermore, frequency domain information may indicate the frequency granularity of the CSI report. This frequency granularity may include, for example, wideband and subband. The wideband is the entire CSI reporting band. The wideband may be, for example, the entire carrier (component carrier (CC), cell, serving cell) or the entire bandwidth part (BWP) within a carrier. The wideband may also be referred to as the CSI reporting band, the entire CSI reporting band, etc.

[0022] Furthermore, a subband may be part of the wideband and may consist of one or more resource blocks (Resource Blocks (RBs) or Physical Resource Blocks (PRBs)). The size of the subband may be determined according to the size of the BWP (number of PRBs).

[0023] Frequency domain information may indicate whether to report wideband or subband PMI (frequency domain information may include, for example, the RRC IE's "pmi-FormatIndicator" used to determine whether to report wideband PMI or subband PMI). Based on at least one of the above-mentioned reporting quantity information and frequency domain information, the UE may determine the frequency granularity of the CSI report (i.e., whether to report wideband PMI or subband PMI).

[0024] If wideband PMI reporting is established (decided), one wideband PMI may be reported for the entire CSI reporting band. On the other hand, if subband PMI reporting is established, a single wideband indication i1 may be reported for the entire CSI reporting band, and one subband indication i2 (e.g., subband indication for each subband) may be reported for one or more subbands within the entire CSI reporting band.

[0025] The UE performs channel estimation using the received RS and estimates the channel matrix H. The UE then feeds back the index (PMI) determined based on the estimated channel matrix.

[0026] PMI may represent a precoder matrix (also simply called a precoder) that a UE considers appropriate for use in downlink (DL) transmissions to the UE. Each value of PMI may correspond to a single precoder matrix. A set of PMI values ​​may correspond to a different set of precoder matrices called a precoder codebook (also simply called a codebook).

[0027] In a spatial domain, a CSI report may include one or more types of CSIs. For example, the CSI may include at least one of a first type (Type 1 CSI) used for single-beam selection and a second type (Type 2 CSI) used for multi-beam selection. A single beam may be rephrased as a single layer, and a multi-beam as multiple beams. Furthermore, a Type 1 CSI may not assume multi-user multiple input multiple output (MU-MIMO), while a Type 2 CSI may assume multi-user MIMO.

[0028] The above codebooks may include a codebook for Type 1 CSI (also referred to as a Type 1 codebook, etc.) and a codebook for Type 2 CSI (also referred to as a Type 2 codebook, etc.). Furthermore, Type 1 CSI may include Type 1 single-panel CSI and Type 1 multi-panel CSI, and different codebooks (Type 1 single-panel codebook and Type 1 multi-panel codebook) may be specified for each.

[0029] The Upbound Control Information (UCI) type may include at least one of Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), scheduling request (SR), or CSI. The UCI may be carried by PUCCH or by PUSCH.

[0030] In Rel. 15 NR, the UCI may include one CSI part for wideband PMI feedback. CSI report #n includes PMI wideband information, if reported.

[0031] In Rel. 15 NR, the UCI may include two CSI parts for subband PMI feedback. CSI part 1 contains wideband PMI information. CSI part 2 contains one wideband PMI piece and several subband PMI pieces. CSI parts 1 and 2 are encoded separately.

[0032] In Rel. 15 NR, the UE is configured by a higher layer with N (N≧1) CSI reporting settings and M (M≧1) CSI resource settings. For example, a CSI reporting setting (CSI-ReportConfig) includes a resource setting for channel measurement (resourcesForChannelMeasurement), a CSI-IM resource setting for interference (csi-IM-ResourceForInterference), an NZP CSI-RS setting for interference (nzp-CSI-RS-ResourceForInterference), and a report quantity (reportQuantity). Each of the resource settings for channel measurement, the CSI-IM resource setting for interference, and the NZP CSI-RS setting for interference is associated with a CSI resource setting (CSI-ResourceConfig, CSI-ResourceConfigId). The CSI resource configuration includes a list of CSI-RS resource sets (csi-RS-ResourceSetList, for example, the NZP CSI-RS resource set or the CSI-IM resource set).

[0033] To enable more dynamic channel / interference hypotheses for NCJT, targeting both FR1 and FR2, evaluation and specification of CSI reporting for at least one multi-TRP and multi-panel transmission of DL are being considered.

[0034] In this disclosure, Type 1 and Type I may be interpreted as interchangeable. In this disclosure, Type 2 and Type II may be interpreted as interchangeable.

[0035] In this disclosure, CSI-RS, periodic CSI-RS (P CSI-RS), semi-persistent CSI-RS (SP CSI-RS), and aperiodic CSI-RS (AP CSI-RS, A CSI-RS) may be interpreted interchangeably. In this disclosure, CSI-RS, periodic CSI reporting (P CSI reporting), semi-persistent CSI reporting (SP CSI reporting), and aperiodic CSI reporting (AP CSI reporting, A CSI reporting) may be interpreted interchangeably.

[0036] (CSI Reporting Configuration) The CSI reporting configuration (CSI-ReportConfig) includes the codebook configuration (CodebookConfig), channel measurement resource (CMR), interference measurement resource (IMR), etc. The IMR may be at least one of zero power-interference measurement resource (ZP-IMR) and non-zero power-interference measurement resource (NZP-IMR).

[0037] The UE (User Environment) configures the codebook (CB) parameters (CodebookConfig) through higher-layer signaling (RRC signaling). The codebook configuration is included in the higher-layer (RRC) parameter CSI-ReportConfig.

[0038] In the codebook configuration, at least one codebook is selected from among several codebooks, including Type I Single Panel (typeI-SinglePanel), Type I Multi Panel (typeI-MultiPanel), Type II, and Type II Port Selection (typeII-PortSelection, PS).

[0039] The codebook parameters include parameters related to codebook subset restrictions (CBSRs) ("...Restriction" in CodebookConfig). The CBSR setting is a bit that indicates which PMI reports are allowed ("1") and which are not allowed ("0") for the precoder associated with the CBSR bit. Each bit in the CBSR bitmap corresponds to one codebook index / antenna port.

[0040] In this disclosure, the Codebook (CB), the CB for Type 1 / Type 2 / Type 2PS, the Extended CB based on the CB for Type 1 / Type 2 / Type 2PS, the CSI, and the PMI may be interpreted interchangeably.

[0041] In this disclosure, CMR, NZP CSI-RS resources, and resourcesForChannelMeasurement may be interpreted as interchangeable. In this disclosure, ZP-IMR, CSI-IM resources, and csi-IM-ResourcesForInterference may be interpreted as interchangeable. In this disclosure, NZP-IMR, NZP CSI-RS resources for interferometry, and nzp-CSI-RS-ResourcesForInterference may be interpreted as interchangeable.

[0042] (L1 / L2 Inter-Cell Mobility) A UE may perform UL transmissions to one or more cells / TRPs. In this case, the following Scenario 1 or Scenario 2 procedures are possible. In this disclosure, a serving cell may be interpreted as a TRP within a serving cell. Layer 1 / layer 2 (L1 / L2) and DCI / Medium Access Control Control Element (MAC CE) may be interpreted as mutually exclusive. In this disclosure, a PCI different from the Physical Cell Identity (PCI) of the current serving cell may be simply referred to as a "different PCI". Non-serving cells, cells with different PCIs, and additional cells may be interpreted as mutually exclusive.

[0043] <Scenario 1> Scenario 1 corresponds to, for example, inter-cell mobility of multi-TRP, but may be a scenario that does not correspond to inter-cell mobility of multi-TRP.

[0044] (1) A UE receives, from a serving cell, an SSB configuration for beam measurement of a TRP corresponding to a PCI different from the serving cell, and configurations necessary for using radio resources for data transmission and reception, including resources of the different PCI. (2) The UE performs beam measurement of the TRP corresponding to the different PCI, and reports the beam measurement result to the serving cell. (3) Based on the above report, a Transmission Configuration Indication (TCI) state associated with the TRP corresponding to the different PCI is activated by L1 / L2 signaling from the serving cell. (4) The UE performs transmission and reception using a UE-dedicated channel on the TRP corresponding to the different PCI. (5) The UE needs to always cover the serving cell, including in the case of multi-TRP. The UE needs to use common channels from the serving cell (Broadcast Control Channel (BCCH), Paging Channel (PCH)) and the like, as in conventional systems.

[0045] In Scenario 1, when the UE transmits and receives signals to and from an additional cell / TRP (TRP corresponding to the PCI of the additional cell), the serving cell (assumption of the serving cell in the UE) is not changed. The UE is configured with higher layer parameters related to the PCI of the non-serving cell from the serving cell. Scenario 1 may be applied in Rel-17, for example.

[0046] Assume a case where the UE moves from the cell of PCI#1 (serving cell) to the cell of PCI#3 (additional cell) (overlapping with the serving cell). In this case, in Rel-17, switching of the serving cell by L1 / L2 is not supported.

[0047] The additional cell is a cell having an additional PCI different from the PCI of the serving cell. The UE can receive / transmit a UE-dedicated channel from the additional cell. The UE needs to be within the coverage of the serving cell in order to receive UE common channels (e.g., system information / paging / short messages). When the UE moves out of the coverage of the serving cell, cell switching is required by handover (also referred to as L3 mobility) or the like.

[0048] <Scenario 2> In Scenario 2, inter-L1 / L2 cell mobility is applied. In inter-L1 / L2 cell mobility, a serving cell can be changed using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with the additional cell is possible without handover. Since a data communication unavailable period occurs, such as RRC reconnection being required for handover, by applying handover-free inter-L1 / L2 cell mobility, data communication can be continued even when the serving cell is changed. Scenario 2 may be applied in, for example, Rel.18. In Scenario 2, for example, the following procedure is performed.

[0049] (1) The UE receives, from the serving cell, SSB configuration of a cell (additional cell) having a different PCI for beam measurement / serving cell change. (2) The UE performs beam measurement on the cell using the different PCI, and reports the measurement result to the serving cell. (3) The UE may receive configuration of the cell having the different PCI (serving cell configuration) via higher layer signaling (e.g., RRC). That is, pre-configuration related to serving cell change may be performed. This configuration may be performed together with the configuration in (1), or may be performed separately. (4) Based on the above report, the TCI state of the cell having the different PCI may be activated by L1 / L2 signaling in accordance with the change of the serving cell. The activation of the TCI state and the change of the serving cell may be performed separately. (5) The UE changes the serving cell (assumption of the serving cell), and starts reception / transmission using the preset UE-specific channel and TCI state.

[0050] In other words, in Scenario 2, the serving cell (the assumed serving cell in the UE) is updated by L1 / L2 signaling. Scenario 2 may also be applied in Rel. 18.

[0051] In Rel. 18, serving cells are switched via L1 / L2 (e.g., DCI / MAC CE). UEs can receive / transmit UE-dedicated / common channels to and from the new serving cell (or target serving cell). UEs may be removed from the coverage of the current serving cell (e.g., Current serving cell).

[0052] <Rel. 18 LTM> The primary motivation for lower layer-triggered mobility (LTM) is to reduce downtime [in RACH-based cell switching]. LTM has several characteristics: ◆Handover can be performed without using RACH / RRC reconfiguration / MAC reset. ◆One or more candidate cells are in the same CU as the serving cell. ◆One or more candidate cells are on the same or different frequencies as the serving cell.

[0053] After the UE receives the LTM-Config from the serving cell, several steps are taken before a cell switch decision is made for one or more candidate cells: ◆ DL synchronization [between the UE and one or more candidate cells] ◆ L1 measurement report ◆ UL synchronization [between the UE and one or more candidate cells] ◆ TCI status activation [from the serving cell to the UE]

[0054] Subsequently, the serving cell determines the cell switch and, upon selecting one target cell from one or more candidate cells, sends a cell switch command (CSC, LTM cell switch command) MAC CE to the UE. The CSC MAC CE contains several pieces of information about the target cell of the cell switch [from one or more candidate cells], including: ◆ Configuration ID [to indicate the target cell] ◆ TCI status ID ◆ Timing advance (TA) value ◆ CFRA resource index (optional)

[0055] <Conditional LTM> This section describes examples of providing / signaling / evaluating execution conditions (e.g., execution conditions) for candidate cells when conditional LTM (e.g., conditional LTM (CLTM)) is supported.

[0056] Execution conditions may be set for each candidate cell by RRC signaling / MAC CE. The execution conditions (or simply called "conditions") may include at least one of the following: event, reference signal type (RS type), reference signal configuration (RS configuration), and measurement quantity. The reference signal type (RS type) may indicate SSB / CSI-RS. The measurement quantity may indicate L1-RSRP / L3-RSRP / SINR / RSRQ.

[0057] The execution conditions may be set separately for each candidate cell (for example, different conditions may be supported). Alternatively, the execution conditions may be set in common for multiple candidate cells (for example, a group of candidate cells) or for all candidate cells. Alternatively, some of the execution conditions may be set in common for each candidate cell, while the rest are set separately. Some of the execution conditions may be events, and the rest may be condition values, etc. Of course, this is not limited to these.

[0058] The number of candidate cells for which implementation conditions are provided may be defined in advance by the specification, set by the UE from the network (e.g., base stations), or determined based on UE capabilities. For example, the number of cells for which implementation conditions are provided may be the same as the set candidate cells, or it may be less than the total number of set candidate cells.

[0059] The settings for the implementation conditions (e.g., detailed settings) may be the same as the settings for the existing system. The settings for the existing system may be, for example, the settings supported by CHO supported in Rel. 16 (e.g., settings based on L3 measurement).

[0060] Alternatively, the settings for the implementation conditions may be the same as new condition settings for event-triggered L1 reporting (e.g., event-triggered L1 report). An example of a condition (or event) is shown below. Event A2: The measurement result of the serving cell is worse than the threshold. Event A3: The measurement result of the adjacent cell (the measurement result plus an offset) is better than the measurement result of the SpCell (the measurement result plus an offset). Event A4: The measurement result of the adjacent cell (the measurement result plus an offset) is better than the threshold. Event A5: The measurement result of the SpCell is worse than the first threshold, and the measurement result of the adjacent cell (the measurement result plus an offset) is better than the second threshold. Event A6: The measurement result of the adjacent cell (the measurement result plus an offset) is better than the measurement result of the serving cell (Secondary Cell (SCell)) (the measurement result plus an offset). Event I1: The interference measurement result is higher than the threshold. Event A4': The measurement result of one beam from an adjacent cell is better than the threshold. Event A4'': The statistical value (e.g., mean, sum, etc.) of the measurement results of multiple beams (e.g., the best X beams) is better than the threshold. X may be fixed or can be set by upper-layer signaling, etc. Event A4'''': The L1-RSRP measurement result of one beam from an adjacent cell is better than the threshold. Event A4'''': The L1-RSRP of each of the X beams from adjacent cells is better than the threshold.

[0061] Note that the applicable conditions / events are not limited to those listed above; multiple events may be applied in combination, or other events may be applied.

[0062] (Event-Triggered Beam Reporting / UE-Initiated Beam Report (UEIBR)) In future wireless communication systems (e.g., Rel. 19 and beyond), support for event-based beam reporting is being considered. Event-based beam reporting may also be called event-triggered beam reporting, or UE-initiated beam reporting (UEIBR).

[0063] Beam management (UEIBM) initiated by UEIBR / UE can be used for measurement reporting, beam switching, cell switching, etc.

[0064] <Applicable Cases> UEIBR may be applied, for example, in at least one of the following Case 1 or Case 2: • Case 1: L1-RSRP / SINR beam reporting including serving cell PCI / additional PCI (e.g., L1 / L2 inter-cell mobility / inter-cell multi-TRP (M-TRP inter-cell) / L1-RSRP / SINR beam reporting including serving cell / additional PCI cell for Rel. 18 L1 / L2 mobility with cell switching). • Case 2: L1-RSRP / SINR beam reporting including serving cell PCI only.

[0065] The UE may report the measurement results (e.g., at least L1-RSRP / L1-SINR and the corresponding resource indicator / RS index) to the NW when a specific event occurs (which may be interpreted in this disclosure as a specific condition being met / not met, a specific event being matched, etc.).

[0066] The specific event may be, for example, at least one of an event relating to a serving cell and an additional cell, and at least one of an event relating to a beam report including at least one of the PCI of the serving cell and the PCI of the additional cell.

[0067] <UEIBR Trigger Conditions / Events for Rel. 19> The UEIBR may be triggered when certain conditions (events) are met. For example, the UE may apply different / same conditions / events to the triggers of the following beam reports.

[0068] UE Feature #1: UEIBR for MIMO in Rel. 19. UE Feature #2: UEIBR for mobility in Rel. 19.

[0069] Different UE capabilities may be introduced / defined between UE features #1 and #2. Furthermore, different higher-level parameters may be set to enable each UE feature. UE features and UE capabilities may be interchangeable.

[0070] UE does not expect UE features #1 and #2 to be set simultaneously in a given BWP / CC / band / frequency range / frequency (or per UE).

[0071] A UE may have UE features #1 and #2 set simultaneously in a given BWP / CC / band / frequency range / frequency (or per UE). For example, a UE may have predefined which events (which UE features) to prioritize, if set, and this may be set / instructed by upper-layer signaling / physical-layer signaling.

[0072] This disclosure may be applied within the Unified TCI Framework.

[0073] This disclosure may apply only if the corresponding UE capability is reported, or if the corresponding higher-layer parameter (e.g., RRC) is notified / reported.

[0074] <UEIBR for MIMO> The following may apply to the UEIBR for MIMO in Rel. 19.

[0075] - MAC CE in PUCCH. - UCI in periodic / semi-persistent PUCCH, UCI in dynamic grant (DG) / configured grant (CG) PUCCH. - The relationship between the MAC CE-based method and the UCI-based method described above. For example, two independent methods may be configurable. Alternatively, a UCI-based method may be applied in addition to a MAC CE-based method (a combination of the two methods (2-step method) may be applied).

[0076] The report content may be essentially the same as existing L1 beam measurement reports, and may include at least one of the following, for example: • SSBRI / CRI. • Number of beams to be reported (X). • Method for selecting X beams. • L1-RSRP / SINR (absolute value / difference value) for each SSBRI / CRI. If MAC CE is used, • Indicator indicating whether the following octets are included. If MAC CE / UCI is used, • Serving cell ID, BWP ID (if the report requires activation of the TCI state or beam switching).

[0077] Events related to the UEIBR for MIMO may be broadly categorized into the following event types: • Event 1: The quality of the current beam falls below a certain threshold. • Event 2: The quality of at least one new beam (e.g., L1-RSRP) is better than a certain threshold compared to the quality of the current beam. • Event 3: The quality of a new beam is better than a certain threshold. • Event 4: The quality of the current beam falls below a first threshold, and the quality of at least one new beam is better than a second threshold. • Event 5: The absolute difference between the quality of the current beam and the quality of at least one new beam falls below a certain threshold. • Event 6: The current beam is no longer included in the best K beams (more than 1: K > 1) (of the beams set up for measurement / reporting). - Event 7: The quality of at least one new beam (e.g., L1-RSRP) improves by a threshold beyond the RS derived from the Q-th (Q may be M; Q or M is 1 or greater; Q or M may be set in the RRC (based on UE capability reporting)) quality good activated (active) TCI state. - Event 8: The quality of M (more than 1: M > 1) new beams (e.g., L1-RSRP) improves by a threshold beyond the current beam. - Event 9: The quality of at least one new beam (e.g., L1-RSRP) improves by a threshold beyond the set reference RS (which may be SSB / CSI-RS).

[0078] It should be noted that the events exemplified in this way do not exclude other events.

[0079] Priorities may be assigned to events 1 through 9. For example, one of events 1 through 9 (e.g., event 2) may have the highest priority (e.g., event 2 may be given priority in the decision-making process).

[0080] For example, in event 2, the current beam may be determined / derived based on the QCL RS of the indicated TCI state (e.g., QCL source RS).

[0081] For example, for the current beam in event 2, at least one of the following beam options 2a to 2c may be supported: • Beam option 2a: The RS corresponding to the current beam is implicitly derived / determined based on the QCL RS in the indicated TCI state. • Beam option 2b: The RS corresponding to the current beam is an SSB that is QCL'd with the QCL RS in the indicated TCI state. • Beam option 2c: The RS corresponding to the current beam is explicitly set / indicated using RRC signaling / MAC CE.

[0082] For example, for a new beam in Event 2, at least one of the following beam options 3a to 3c may be supported: • Beam option 3a: The RS corresponding to the new beam is [explicitly] set using RRC signaling (e.g., resetting of existing RS measurements, or setting parameters for TCI states (e.g., TCI-State)) / MAC CE. • Beam option 3b: The RS corresponding to the new beam is [implicitly] derived / determined based on the QCL RS of the activated TCI state (active TCI state). • Beam option 3c: The RS corresponding to the new beam is [implicitly] derived / determined based on the QCL RS of one or more TCI states in a setting subset of the list of TCI states set by RRC (set TCI states).

[0083] For example, multiple schemes may be supported for the reference signal measurement (RS measurement) of the current beam for event 2 (and beam option 2a): • Scheme 1: The RS of the current beam is the QCL RS in the indicated TCI state. • Scheme 2: The RS of the current beam is the QCL RS in the indicated TCI state and the QCLed SSB.

[0084] If there are two QCL RSs in the indicated TCI state, the QCL RSs may be of QCL type D.

[0085] At least one of CSI-RS and SSB may be supported as a QCL RS to be set / applied to the indicated TCI state. When CSI-RS is set / applied as the QCL RS, at least one of a tracking CSI-RS (TRS) and a measurement CSI-RS may be supported. The measurement CSI-RS may be a CSI-RS used for L1-RSRP / L1-SINR or a CSI-RS used for beam management (BM).

[0086] In Scheme 1, only a TRS (e.g., one tracking CSI-RS) may be set as the QCL-RS (e.g., type A / D) for the indicated TCI state.

[0087] If only TRS is set as the QCL-RS for the indicated TCI state, a reference signal different from the TRS (e.g., the RS corresponding to the TRS) may be selected for measuring / reporting the RS of the current beam.

[0088] For the current beam RS measurement in Event 2 / Option 2a, [in addition to Schemes 1 and 2], at least one of the following processing options 1 to 4 may be applied when only one TRS is set in the indicated TCI state:

[0089] • Processing Option 1: An additional scheme is introduced. The RS for the current beam can be the CSI-RS for beam management derived from the QCL RS in the indicated TCI state. • Processing Option 2: TRS is further supported as the measured RS for the current beam to determine the L1-RSRP. • Processing Option 3: An additional scheme is introduced. The RS for the current beam is explicitly set / indicated by the RRC or MAC CE. • Processing Option 4: No further extensions are made.

[0090] Explicit RS settings for measuring new beams in Event 2 may be configured in a single RS resource set associated with the CSI reporting settings.

[0091] In this case, if existing UE capabilities cannot be reused, a UE capability indicating the maximum number of RSs to be set within the RS resource set may be defined / introduced.

[0092] The RS within that single RS resource set may be updated by MAC CE.

[0093] UEIBR for MIMO may be transmitted using UCI.

[0094] In a UCI-based UEIBR procedure using UCI, the following modes may be supported:

[0095] <<Mode A>> Mode A relates to the dynamic scheduling of UCI by NW (gNB). That is, in Mode A, resources for UCI are scheduled by gNB. Mode A may be a basic function of the UE (a UE that supports UEIBR may naturally support this function).

[0096] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is a UL channel that pre-notifies / requests a second UL channel (e.g., PUCCH) for transmitting beam reports, and may consist of one or more bits.

[0097] Step 2: The UE detects a DCI format (which may also be called the first DL signal) indicating the second UL channel resource.

[0098] Step 3: The UE transmits the beam report using the resource (UCI) on the second UL channel.

[0099] In mode A, a 1-bit instruction in at least the first UL channel (PUCCH) may be supported to request resources on the second UL channel for transmitting beam reports.

[0100] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.

[0101] An RRC parameter (e.g., reportResourceRequest-UEIBR) corresponding to the one-bit instruction (for setting the one-bit instruction) may be defined. The RRC parameter may be identified using a specific ID (e.g., a dedicated SchedulingRequestId).

[0102] Furthermore, an RRC parameter (e.g., firstPUCCHResourceConfig-ModeA-UEIBR) for periodic PUCCH resource configuration corresponding to the 1-bit instruction may be defined. This RRC parameter does not need to be associated with the SR ID (e.g., SchedulingRequestId).

[0103] The RRC parameters may include, for example, period and offset setting parameters (periodicityAndOffset) and a PUCCH resource ID (e.g., PUCCH-ResourceID).

[0104] These RRC parameter specifications may also apply to cases using at least one CC (single CC).

[0105] The DCI format in step 2 may be, for example, UL Grant DCI (e.g., DCI format 0_1 / 0_2 / 0_3), and the second UL channel in step 3 may utilize at least PUSCH.

[0106] Furthermore, the DCI format in step 2 may be, for example, DL Grant DCI (e.g., DCI format 1_1 / 1_2), and the second UL channel in step 3 may utilize PUCCH.

[0107] A new 1-bit field in the DL grant DCI may be defined to instruct the transmission of the UEIBR.

[0108] PUCCH resources intended for HARQ-ACK transmission may be (re)used to transmit both HARQ-ACK and UEIBR.

[0109] <<Mode B>> Mode B relates to the UCI in the resources pre-configured for the second UL channel.

[0110] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is a UL channel that notifies a second UL channel for transmitting beam reports, and may consist of one or more bits.

[0111] Step 2: The UE transmits a beam report on the second UL channel (for example, using a specific resource (UCI) within the channel).

[0112] Note that the notification in Step 1 may be included in a separate reporting instance from the beam report in Step 2.

[0113] In mode B, a one-bit instruction on at least the first UL channel (PUCCH) may be supported to indicate that the second UL channel will transmit a beam report.

[0114] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.

[0115] In either mode A or B as described above, cross-CC (component carrier) beam reporting may be supported.

[0116] An RRC parameter (e.g., reportResourceRequest-UEIBR) corresponding to the one-bit instruction (for setting the one-bit instruction) may be defined. The RRC parameter may be identified using a specific ID (e.g., a dedicated SchedulingRequestId).

[0117] Furthermore, an RRC parameter (e.g., firstPUCCHResourceConfig-ModeB-UEIBR) for periodic PUCCH resource configuration corresponding to the 1-bit instruction may be defined. This RRC parameter does not need to be associated with the SR ID (e.g., SchedulingRequestId).

[0118] The RRC parameters may include, for example, period and offset setting parameters (periodicityAndOffset) and a PUCCH resource ID (e.g., PUCCH-ResourceID).

[0119] These RRC parameter specifications may also apply to cases using at least one CC (single CC).

[0120] The second UL channel in step 2 may be, for example, a type 1 configured grant (CG) PUSCH or PUCCH.

[0121] <UEIBR for Mobility> With respect to the UEIBR for mobility (e.g., LTM) in Rel. 19, the following may apply:

[0122] - MAC CE in semi-persistent / aperiodic PUCCH. - UCI in periodic / semi-persistent PUCCH, UCI in semi-persistent / aperiodic PUCCH.

[0123] The report may include, for example, at least one of the following: If the measurement report is used for cell switching reporting, in addition to MIMO-related information: an indicator showing whether or not a cell switch has occurred, or TA-related information. Otherwise (if the measurement report is not used for cell switching reporting): the same information as MIMO-related information (the only difference being whether it is within a cell or between cells).

[0124] The supported events may be the same as those for a Conditional Hand-Over (CHO).

[0125] For example, since candidate cells are set based on the L3 measurement report, L1-RSRP / SINR may be used as the threshold.

[0126] If the report is used for cell switching commands, specific domain filters (e.g., time / frequency / space) may be considered / applied to prevent frequent switching.

[0127] It may also be specified whether flexibility in the trigger time (e.g., 5 milliseconds, 10 milliseconds, 20 milliseconds) is required.

[0128] In the case of L1 measurements using UEIBR, at least the results of beam-level measurements may be used for event evaluation.

[0129] Events related to UEIBR for mobility may be broadly categorized into the following event types: • Event LTM2: The serving cell's beam quality falls below an (absolute) threshold. • Event LTM3: The candidate cell's beam quality improves beyond a certain offset amount compared to the serving cell's beam quality. • Event LTM4: The candidate cell's beam quality falls below an (absolute) threshold. • Event LTM5: The serving cell's beam quality falls below a first (absolute) threshold, AND the candidate cell's beam quality improves above a second (absolute) threshold.

[0130] It should be noted that the events exemplified in this way do not exclude other events. Furthermore, the MIMO-oriented events described above may be reused as appropriate (in this case, "current beam" may be replaced with "serving cell beam," and "new beam" with "candidate cell beam"). These reused / re-interpreted events may be called mobility / LTM-oriented events corresponding to MIMO-oriented events.

[0131] In the LTM configuration, the L1 measurement resource setting may support both SSB and CSI-RS beam settings.

[0132] In events LTM3 and LTM5, the same type of RS (e.g., CSI-RS / SSB) may be used for both the serving cell and the candidate cell (adjacent cell).

[0133] In mobility event evaluation, at least one of the following may be applied: TimeToTrigger (TTT), hysteresis for entering / leaving, and beam-specific / cell-specific offsets.

[0134] UEIBR for mobility may be transmitted using MAC CE.

[0135] <Definition of wording for specific events> In the existing events described above, the definitions of Serving [cell] and Neighbor [cell] may be reinterpreted / updated as follows in the UEIBR for Rel. 19.

[0136] For example, in existing L3 events, Serving [Cell], SpCell, and PCell may be interpreted interchangeably with the current beam (e.g., the RS ID associated with the indicated [Joint / DL]TCI state) in event-triggered beam reports for MIMO in Rel. 19.

[0137] Furthermore, in existing L3 events, Serving [Cell], SpCell, and PCell may be interpreted interchangeably with the current beam (e.g., the RS ID associated with the indicated [Joint / DL] TCI state) or the serving cell's beam (e.g., the RS ID associated with the serving cell's PCI TCI state) in the event-triggered beam reports for mobility in Rel. 19.

[0138] In existing L3 events, adjacent [cells] may be interpreted interchangeably with other beams (e.g., RS IDs that are not associated with the indicated [joint / DL]TCI state but are associated with the RS ID for the L1 beam measurement) in event-triggered beam reports for MIMO (which may be mobility) in Rel. 19.

[0139] Furthermore, adjacent [cells] in existing L3 events may be interpreted as corresponding to beams of non-serving cells / target cells / candidate cells (e.g., RS IDs associated with the TCI status of the PCI of target cells / candidate cells) in event-triggered beam reports for mobility in Rel. 19.

[0140] The measured values ​​of each reference signal (RS) may be RSRP / SINR, L3-RSRP / SINR, L1-RSRP / SINR, or the average of multiple L1-RSRP / SINR values.

[0141] For example, L1-RSRP / SINR can change dynamically. Therefore, by averaging multiple (X) L1-RSRP / SINR values ​​(e.g., X=5), control hunting (frequent switching of trigger states) in beam reporting triggers can be avoided.

[0142] (Analysis) As mentioned above, support for MIMO-oriented UEIBR is being considered in Rel. For MIMO-oriented UEIBR, a new event [related to the current beam quality / candidate beam quality] is being considered. Furthermore, the UE is considering sending an SR to the NW to trigger a beam report. This beam report is being considered to be reported via a DG PUSCH scheduled by the NW, or via a UCI in a pre-configured CG PUSCH.

[0143] Furthermore, support for a mobility-oriented UEIB is being considered in Rel. For the mobility-oriented UEIB, a new event [different from the MIMO-oriented UEIB] is being considered. Additionally, the UE is considering transmitting beam reports to the NW via MAC CE. In the mobility-oriented UEIB, the MAC layer is being considered to handle event evaluation and triggering measurement reports.

[0144] Here, the inventors are considering applying a UE-initiated reporting mechanism to CSI in addition to beam reporting in future wireless communication systems (e.g., 6G). UE-initiated CSI reporting may be called UEI-CSI reporting (or simply UEI-CSI).

[0145] If UEI-CSI reporting is supported, a unified framework for both UEIBR and UEI-CSI reporting may be used.

[0146] Similar to the UEIBR in Rel. 19, both CSI reporting scheduled by gNB and UEI-CSI reporting are supported and may be configured by the network.

[0147] As shown in Figure 1, for a unified framework for both UEIBR and UEI-CSI reporting, the trigger / reporting procedures for UEIBR are essentially reusable for UEI-CSI. On the other hand, as also shown in Figure 1, some procedures may be extended.

[0148] As shown in Figure 1, at least one of the following challenges 1 and 2 needs to be considered: ◆Challenge 1: Defining new events. ◆Challenge 2: How to reuse procedures for event evaluation, reporting triggers, and reporting signals.

[0149] If these issues are not adequately considered, there is a risk that CSIs may not be reported properly.

[0150] Therefore, the present inventors have conceived of the following embodiments. According to one aspect of this disclosure, CSI can be appropriately reported.

[0151] The embodiments relating to this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination. This disclosure also provides embodiments in which some / all of one embodiment is combined with some / all of another embodiment.

[0152] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets ([]) may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets ([]) may be used for purposes / meanings other than those described above.

[0153] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0154] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

[0155] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0156] In this disclosure, terms such as signaling, message, field, parameter, information, and payload may be interpreted interchangeably.

[0157] In this disclosure, the upper-layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, Non-Access Stratum (NAS) signaling [of the control plane], and other messages (e.g., messages communicated with the core network, such as positioning protocol (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).

[0158] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0159] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0160] In this disclosure, base station, gNB, and network (NW) may be interpreted as interchangeable.

[0161] In this disclosure, cell group, serving cell group, master cell group (MCG), and secondary cell group (SCG) may be interpreted interchangeably. L1 / L2, L1 / L2 signaling, and DCI / MAC CE may be interpreted interchangeably. A serving cell may be replaced with a cell that transmits a PDSCH. A candidate cell may mean a cell that is a candidate to become a serving cell through L1 / L2 inter-cell mobility. L1 / L2-triggered mobility (or Lower layer triggered mobility, LTM) and L1 / L2 inter-cell mobility may be interpreted interchangeably.

[0162] In this disclosure, cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within CC, and band may be interpreted interchangeably. In this disclosure, cell, PCI, cell with additional PCI, additional cell, other cell, non-serving cell, cell with a different PCI, candidate cell, candidate serving cell, cell with a PCI different from the current serving cell's PCI, another serving cell, and target cell may be interpreted interchangeably. A target cell may be a cell selected from among several candidate cells. In this disclosure, switch, change, and update may be interpreted interchangeably. A serving cell may be interpreted as a serving cell before a switch or a serving cell after a switch.

[0163] In this disclosure, "transmission" and "reception" may be interpreted interchangeably.

[0164] In this disclosure, MAC CE, UCI, cell switching command, beam switching command, MAC CE for beam reporting, MAC CE for cell switching, MAC CE for UEI-CSI reporting, and UCI for UEI-CSI reporting may be interpreted as mutually exclusive.

[0165] In this disclosure, "Serving" may be interpreted as "Serving beam," "Serving cell," or "SpCell."

[0166] In this disclosure, "Neighbor" may be interpreted as any beam or cell other than a serving beam / serving cell / SpCell / SCell.

[0167] In this disclosure, candidate cells, target cells, adjacent cells, cells, etc., may be interpreted interchangeably.

[0168] In this disclosure, the beam, RS, RS index (CRI / SSBRI), and [L1 / L3] measurement results may be interpreted interchangeably.

[0169] In this disclosure, the measured RS may be the QCL source RS in an active TCI state / indicated TCI state.

[0170] In this disclosure, the terms event-based beam reporting, event-triggered beam reporting, UE-triggered beam reporting, UE-initiated beam reporting (UEIBR), UE-initiated beam management (UEIBMM), beam reporting, etc., [for Rel. 19] may be interpreted interchangeably.

[0171] In this disclosure, the terms event-based CSI reporting for 6G, event-triggered CSI reporting, UE-triggered CSI reporting, UE-initiated CSI reporting (UEI-CSI reporting), UEI-CSI, CSI reporting, CSI, etc., may be interpreted interchangeably.

[0172] In this disclosure, indicated TCI state, active TCI state, activated TCI state, configured TCI state, and RS set in RRC may be interpreted interchangeably.

[0173] Each embodiment of this disclosure is applicable to any event.

[0174] In this disclosure, rules, cases, factors, conditions, events, thresholds, etc., may be interpreted as interchangeable.

[0175] In this disclosure, the terms "report content," "field," "ID," "measurement result," and "reported quantity" may be interpreted interchangeably.

[0176] In this disclosure, CSI reporting settings, reporting settings, CSI reporting settings for UEI-CSI, [Report] settings for UEI-CSI, UEI-CSI [Report] settings, setting information for UEI-CSI, etc., may be interpreted interchangeably.

[0177] In this disclosure, measurement resources, CSI-RS resources, measurement occasions, CMR, IMR, ZP-IMR, NZP-IMR, etc., may be interpreted interchangeably.

[0178] In this disclosure, the terms measurement, measurement result, measured value, CMR measurement, IMR measurement, ZP-IMR measurement, NZP-IMR measurement, measurement for UEI-CSI, etc., may be interpreted interchangeably.

[0179] In this disclosure, words related to report, determine, indicate, select, notify, configure, etc., may be interpreted as interchangeable.

[0180] In this disclosure, terms related to determine, evaluate, measure, count, etc., may be interpreted as interchangeable.

[0181] In this disclosure, CSI [information], UEI-CSI, reporting volume, reporting volume set / instructed by BS / NW, reporting volume reported / determined / displayed / selected by UE, CQI, PMI, CRI, SSBRI, LI, RI, RSRP, RSRQ, SINR, SNR, L1-RSRP, L1-RSRQ, L1-SINR, L1-SNR, etc., may be interpreted as one another.

[0182] (Wireless communication method) The UE may receive configuration information for UEI-CSI (e.g., CSI reporting settings for UEI-CSI). This configuration information may include at least one of the following: information about events for UEI-CSI and information about measurement resources used to evaluate events for UEI-CSI (e.g., CMR / ZP-IMR / NZP-IMR). The UE may also determine whether an event for UEI-CSI is met based on the configuration information [at least one of the events for UEI-CSI and the measurement results of the measurement resources set in the configuration information]. The UE may also report a UEI-CSI if at least one of the events for UEI-CSI is met.

[0183] <First Embodiment> The first embodiment relates to events for UEI-CSI.

[0184] <<Analysis>> Considering the various types of CSI reporting volumes and usage scenarios in 6G, UEI-CSI events may differ depending on the type of reporting volume or usage scenario.

[0185] For example, in the case of a regular CSI report or a report of individual long-term codebook information, events based on fluctuations in channel quality can be considered.

[0186] For example, in the case of a CSI report solely for CQI, or a CSI report for reporting individual interference information, the event may be based on variations in interference.

[0187] In addition, CSI reporting can be triggered by changes in other conditions.

[0188] Therefore, we need to consider events for UEI-CSI.

[0189] The event for UEI-CSI may be at least one of the following events 1-x.

[0190] <<Event 1-1>> Event 1-1 may be an event related to channel measurement results [based on CMR measurement]. Event 1-1 may include at least one of the following events 1-1a to 1-1d.

[0191] <<<Event 1-1a>>> Event 1-1a may involve a change in the best set of X ports (e.g., X=1,2,3,4,…) of a CSI-RS resource with multiple ports (e.g., 32 ports) configured as a CMR. This change may involve a change in Y% of that set (e.g., Y=0,5,10,…,100).

[0192] According to Event 1-1a, it is possible to measure the RSRP for each port, which reflects the change in CSI.

[0193] <<<Event 1-1b>>> Event 1-1b may involve a change in the best set of X spatial vectors (e.g., X=1,2,3,4,…) for multiple CSI-RS resources (e.g., 32 ports) configured as CMRs. This change may involve a change in Y% of the set (e.g., Y=0,5,10,…,100).

[0194] Event 1-1b may also mean that long-term codebook information is changed.

[0195] The spatial vector in event 1-1b may be interpreted as at least one of the following: ◆ A vector in the spatial / frequency domain. ◆ A vector in the delay domain. ◆ A vector in the Doppler domain. ◆ A vector in the time domain.

[0196] <<<Event 1-1c>>> Event 1-1c may involve changing the best set of X CSI-RS resources (e.g., X=1,2,3,4,…) from among the multiple CSI-RS resources set as CMRs. This change may involve changing Y% (e.g., Y=0,5,10,…,100) of that set.

[0197] Event 1-1c may mean that the CRI selected for reporting is changed.

[0198] <<<Event 1-1d>>> Event 1-1d may also occur when the relative fluctuation of L1-RSRP / L1-SINR (or RI / CQI) exceeds a certain threshold.

[0199] Fluctuations in L1-RSRP / L1-SINR may imply that the rank is fluctuating. Also, RI / CQI may be applicable only when RI / CQI [alone] is the reported quantity (set as the reported quantity).

[0200] <<Event 1-2>> Event 1-2 may be an event related to the interference measurement results [based on CMR / ZP-IMR / NZP-IMR measurements]. Event 1-2 may include at least one of the following events 1-2a to 1-2d.

[0201] <<<Event 1-2a>>> Event 1-2a may occur when the measured absolute interference / noise level exceeds a specific threshold P1.

[0202] <<<Event 1-2b>>> Event 1-2b may also occur when the relatively increased / decreased level of interference / noise exceeds a certain threshold P2.

[0203] <<<Event 1-2c>>> Event 1-2c may be a case where multiple IMRs are set, and the strongest set of X IMRs (for example, X=1,2,3,4,...) is changed.

[0204] <<<Event 1-2d>>> Event 1-2d may also occur when the relatively changed CQI exceeds a specific threshold P3.

[0205] Event 1-2d may be applicable only if CQI is the only reported quantity (set as the reported quantity).

[0206] <<Event 1-3>> Events 1-3 may be events related to both channel measurement results and interference measurement results.

[0207] Events 1-3 may be any combination of the above-mentioned events 1-1a / 1-1b / 1-1c / 1-1d and events 1-2a / 1-2b / 1-2c / 1-2d.

[0208] <<Event 1-4>> Event 1-4 may be an event related to other conditions. Event 1-4 may include at least one of the following events 1-4a to 1-4c.

[0209] <<<Event 1-4a>>> Event 1-4a may be an event that depends on the UE implementation.

[0210] If event 1-4a is met, the UE may or may not report in the UEI-CSI supplementary information to notify the NW of the reason / cause for the UEI-CSI being triggered.

[0211] <<<Event 1-4b>>> Event 1-4b may also be an event that occurs when the UE sends UL data.

[0212] For example, for events 1-4b, the UE may provide separate or combined reports as buffer status reports.

[0213] If UL scheduling is required for UL data transmission, in a TDD scenario, the DL CSI may be reported to the network to facilitate the acquisition of the UL CSI.

[0214] <<<Event 1-4c>>> Event 1-4c may be a condition for CLTM.

[0215] For example, events 1-4c may be events A3 / A5 as described above, or events LTM3 / 5 as described above. Note that these are merely examples, and any combination of events for CLTM may be defined / selected as events 1-4c.

[0216] <<Note>> Events in the MIMO / mobility-oriented UEIBR of Rel. 19 may be reused as events for UEI-CSI. That is, events for UEI-CSI may include events in the MIMO / mobility-oriented UEIBR of Rel. 19.

[0217] In the event of this embodiment, X, Y, P1, P2, and P3 may be predefined or set [by RRC signaling].

[0218] According to the first embodiment described above, the UEI-CSI can be appropriately reported based on whether or not the events for the UEI-CSI are met.

[0219] <Second Embodiment> The second embodiment relates to triggers / reports for UEI-CSI.

[0220] <<Embodiment 2-1>> Embodiment 2-1 relates to the evaluation of events for UEI-CSI.

[0221] Events for UEI-CSI (e.g., events in the first embodiment) may be evaluated according to at least one of the following options 2-1-1 to 2-1-4.

[0222] Option 2-1-1: Events for UEI-CSI may be evaluated once per measurement occasion. UEI-CSI may be reported / triggered when certain conditions for events for UEI-CSI are met (for example, the measurement results in a certain measurement occasion satisfy the conditions for UEI-CSI).

[0223] Option 2-1-2: An event for UEI-CSI may be evaluated once based on the averaged measurement results of multiple measurement occasions within a specific time window. UEI-CSI may be reported / triggered if certain conditions for an event for UEI-CSI are met (for example, the averaged measurement results satisfy the event for UEI-CSI).

[0224] Option 2-1-3: Events for UEI-CSI may be evaluated for each measurement occasion. The UE may count / evaluate multiple times whether or not an event for UEI-CSI is met for multiple measurement occasions within a specific time window. The UE may compare the counted number (e.g., the number of times an event for UEI-CSI is met) with a predefined / set threshold. If a specific condition for an event for UEI-CSI is met (e.g., the counted number exceeds (or becomes equal to) the threshold), the UEI-CSI may be reported / triggered.

[0225] Option 2-1-4: Events for UEI-CSI may be evaluated for each measurement occasion. If a condition / event is met during a measurement occasion (e.g., an event for UEI-CSI is input), a specific timer may be started / restarted. If a specific condition for an event for UEI-CSI is met (e.g., an event for UEI-CSI is met in one or more measurement occasions while the specific timer is running), UEI-CSI may be reported / triggered. If a condition / event is not met during a measurement occasion while the specific timer is running (e.g., no event for UEI-CSI is input), the specific timer may be reset.

[0226] For each event using UEI-CSI, it may be predefined / configured which of the above options 2-1-1 to 2-1-4 applies.

[0227] The specific conditions in options 2-1-1 to 2-1-4 above may also be called reporting conditions / trigger conditions [for UEI-CSI].

[0228] Furthermore, the events for UEI-CSI (for example, the events in the first embodiment) may or may not include elements (operations / controls) related to the specific time window / timer described above.

[0229] One or more events for UEI-CSI may be configured in the CSI reporting settings for UEI-CSI.

[0230] The evaluation of events for UEI-CSI may be defined at the physical layer / MAC layer. Furthermore, the evaluation of events for UEI-CSI may or may not involve the exchange of information between the physical layer and MAC layer on the UE side. The information exchanged may be the measurement results [for each measurement occasion / multiple measurement occasions] as described in options 2-1-1 to 2-1-4 above, the averaged measurement results, whether or not an event for UEI-CSI is met [indicated], or the number of times it has been counted.

[0231] <<Embodiment 2-2>> Embodiment 2-2 relates to a signal that triggers the UEI-CSI.

[0232] The UE may transmit a signal (e.g., SR) that triggers the UEI-CSI.

[0233] For triggering the UEI-CSI, a standard SR (which may be interpreted as an SR not dedicated to the UEIBR / UEI-CSI, etc.) may be set / reused, a dedicated SR for the UEI-CSI may be set, or a dedicated SR for the MIMO / mobility-oriented UEIBR in Rel. 19 may be set / reused.

[0234] If a dedicated SR for MIMO / mobility in Rel. 19 is reused, the SR may include additional reporting information to inform the network whether the SR is for the MIMO / mobility network or for the UEI-CSI. This additional reporting information may be explicitly indicated in the SR, or implicitly indicated by the reporting ID.

[0235] <<Embodiment 2-3>> Embodiment 2-3 relates to a signal for reporting UEI-CSI.

[0236] UE may report the UEI-CSI using UCI / MAC CE.

[0237] When UCI is used for UEI-CSI reporting, existing specifications (e.g., existing UCI for CSI reporting / UEIBR) may be reused.

[0238] If MAC CE is used for reporting UEI-CSI, a [new] MAC CE (which may be called a MAC CE for UEI-CSI, etc.) may be defined for transmitting CSI information for UEI-CSI (e.g., CRI / RI / PMI / CQI / LI).

[0239] The above UCI / MAC CE may report / transmit periodically between the time a specific condition (for example, the reporting / triggering condition for the UEI-CSI in options 2-1-1 to 2-1-4 above) is met and a specific timing. At least one of the following options 2-3-1 and 2-3-2 may be applied to that specific timing. ◆ Option 2-3-1: The above specific timing may be the timing when the number of UCI / MAC CE transmissions reaches a specific number. ◆ Option 2-3-2: The above specific timing may be the timing when the exit condition for the event for the UEI-CSI is met.

[0240] For the UCI / MAC CEs that are reported / transmitted periodically as described above, the report content within each UCI / MAC CE (the UCI / MAC CE in each period) may be the same or different. If the report content within each UCI / MAC CE is different, the report content within each UCI / MAC CE may be set by RRC signaling, predefined by specification, selected by the UE and shown in the UEI-CSI, or depend on the UE implementation.

[0241] According to the second embodiment described above, the UEI-CSI can be appropriately triggered / reported.

[0242] <Third Embodiment> The third embodiment relates to the contents of the UEI-CSI report.

[0243] <<Analysis>> In the case of CSI reporting, unlike beam reporting, it is expected that at least some of the CSI information (e.g., amplitude / phase coefficients of SD / FD / DD vectors) will need to be reported frequently in order for the gNB to keep up with channel state fluctuations. In this case, the set report itself will always be performed as set, but the content of the report may differ on different occasions.

[0244] <<Embodiment 3>> The contents of the UEI-CSI report may be set by the NW, or they may be reported / determined / displayed by the UE in the corresponding CSI report (UEI-CSI).

[0245] In this case, the overhead for reporting with UEI-CSI can be optimized on a case-by-case basis.

[0246] Information regarding the reporting content [set by the NW or reported / determined / displayed by the UE] may be displayed using one or more bits / fields [in the UCI / MAC CE for UEI-CSI]. In such display, it may be indicated / notified [to the NW / BS] whether the reporting content of the UEI-CSI includes at least one of the following options 3-1-0 to 3-1-4 (or that it includes at least one of the following options 3-1-0 to 3-1-4): ◆ Option 3-1-0: Full CSI / Partial CSI (the content of Full CSI / Partial CSI may be predefined). ◆ Option 3-1-1: Long-term CSI / Short-term CSI. ◆ Option 3-1-2: Spatial / Frequency / Doppler domain vector with / without corresponding coefficients. ◆ Option 3-1-3: Quantization of channel covariance. ◆Option 3-1-4: CRI / RI / PMI / CQI / LI.

[0247] If the UE reports information regarding the above-mentioned report in the UCI, such reporting may be done in accordance with at least one of the following options 3-2-1 and 3-2-2: ◆ Option 3-2-1: The bits for the above-mentioned reporting may be included in Part 1 UCI (or part of UCI with a fixed payload). The bits may indicate whether or not the above-mentioned report is included. ◆ Option 3-2-2: The bits for the above-mentioned reporting may be included in Part 1 UCI (or part of UCI with a fixed payload). The bits may indicate whether or not the above-mentioned report is modified.

[0248] According to the third embodiment described above, the contents of the UEI-CSI report can be appropriately set and displayed.

[0249] <Supplement> <<Notification of Information to UE / BS>> In the embodiments described above, notification of any information from the Network (NW) (e.g., Base Station (BS)) / NW node) to the UE / BS (in other words, reception of any information from the BS / NW node at the UE / BS) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE, NAS signaling, LPP messages, NRPPa messages), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or a combination thereof.

[0250] When the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader. The MAC CE may be an extension of an existing MAC CE. For example, the MAC CE may introduce a new octet into an existing MAC CE.

[0251] If the above notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI. The specific field may be an existing DCI field or a new DCI field. The RNTI may be an existing RNTI or a new RNTI. The format of the DCI may be an existing DCI format or a new DCI format.

[0252] Furthermore, the notification of arbitrary information to the UE / BS in the above-described embodiments may be periodic, semi-persistent, or aperiodic. Semi-persistent or aperiodic notification of information may be triggered by instructions from the UE / BS / NW.

[0253] In the embodiments described above, the UE may receive information from the NW of at least one of the following QCL rules: • QCL Type A • QCL Type B • QCL Type C • QCL Type D

[0254] In the embodiments described above, information from the network may be set / instructed by any or a combination thereof in the following ways: - Common to multiple UEs, or individual to each UE (per UE); - Common to multiple BSs, or individual to each BS (per BS); - Common to multiple frequencies (e.g., one or a combination thereof, such as a cell, band, band combination, bandwidth part (BWP), component carrier, etc.), or frequency-specific (per frequency, e.g., per cell).

[0255] <<Notification of Information from UE / BS>> Notification of any information from UE / BS to the NW in the embodiments described above (in other words, transmission / reporting of any information from UE / BS to BS / NW nodes) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE, NAS signaling, LPP messages, NRPPa messages), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0256] When the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader. The MAC CE may be an extension of an existing MAC CE. For example, the MAC CE may introduce a new octet into an existing MAC CE.

[0257] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

[0258] Furthermore, notifications of arbitrary information from the UE / BS in the above-described embodiments may be periodic, semi-persistent, or aperiodic. Semi-persistent or aperiodic notifications of information may be triggered by instructions from the UE / BS / NW.

[0259] <<Regarding the application of each embodiment>> In a UE / BS, specific (e.g., one or more, or some) processing / operation / control / assumption / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific processing / operation / control / assumption / information is set in the UE / BS; - The specific processing / operation / control / assumption / information is determined in the UE / BS based on the relevant higher-layer parameter; - The specific processing / operation / control / assumption / information is instructed / specified / activated / triggered to the UE / BS by MAC CE / DCI / UCI / Resource / Channel / RS; - The UE / BS reports or supports a specific capability (e.g., UE capability) indicating (or related to) the specific processing / operation / control / assumption / information; - The application of the specific processing / operation / control / assumption / information is determined in the UE / BS based on specific conditions.

[0260] The above-mentioned specific capabilities may represent at least one of the following: supporting the above-mentioned specific processing / operation / control / assumption / information; the capabilities of each embodiment; the capabilities of each option in each embodiment, or the capabilities of a combination of multiple options in each embodiment; the capabilities of each choice in each embodiment, or the capabilities of a combination of multiple choices in each embodiment; supporting measurement / reporting for UEI-CSI; and supporting evaluation of specific events for UEI-CSI (e.g., at least one of the events in the first embodiment).

[0261] In this disclosure, "to support" and "whether or not to support" may be interpreted interchangeably.

[0262] Furthermore, the above-mentioned specific capabilities may be capabilities that apply across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities per subcarrier spacing (SCS), or capabilities per feature set (FS) or feature set per component-carrier (FSPC).

[0263] Furthermore, the specific capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

[0264] If the above conditions are not met, UE / BS may follow the behavior specified in existing 3GPP releases.

[0265] Information regarding whether one or more of the above embodiments / options / choices / examples apply / are used, or which of the above embodiments / options / choices / examples apply / are used, may be based on several of the following methods: • The information is set by one or more higher-layer parameters / RRC IEs. • The information is determined by one or more relevant higher-layer parameters / RRC IEs. • The information is indicated by MAC CE / DCI. • The information is determined based on one or more UE capabilities. • The information is described / defined in the specification. • The information is based on conditions described / defined in the specification. • The information is determined by a combination of several of the above methods. For example, the information is determined by the setting / indication of higher-layer parameters / MAC CE / DCIs and reported by UE capabilities.

[0266] The above multiple embodiments / options / choices may be combined into a single embodiment / option / choice.

[0267] In the embodiments described above, the measured RS may be a QCL source RS in an active TCI state / indicated / unified TCI state.

[0268] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal having: a receiving unit that receives setting information for reporting channel state information (UEI-CSI) initiated by the terminal; and a control unit that evaluates an event related to at least one of the channel measurement results and interference measurement results based on the setting information, and controls the terminal to report the UEI-CSI when specific conditions relating to the event are met. [Note 2] The terminal according to Note 1, wherein the control unit evaluates whether the event is met once or multiple times for each measurement occasion. [Note 3] The terminal according to Note 1 or Note 2, wherein the control unit evaluates the event based on the averaged measurement results of multiple measurement occasions within a specific period. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the control unit determines the content of the report in the UEI-CSI and controls the transmission of information indicating the content of the report.

[0269] (Wireless Communication System) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any of the wireless communication methods according to the above embodiments of this disclosure, or a combination thereof.

[0270] Figure 2 shows an example of a schematic configuration of a wireless communication system according to one embodiment of the present disclosure. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0271] Furthermore, the wireless communication system 1 may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like.

[0272] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0273] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity where both MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0274] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. Terminals 20 may be located within at least one cell. The arrangement, number, shape, size, etc., of each cell and terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

[0275] The wireless communication system 1 may utilize Multi Input Multi Output (MIMO). For example, one cell may be formed by one antenna / base station 10, or by multiple antennas / base stations 10. One [virtual] cell (which may be called a supercell, for example) may be composed of multiple [virtual] cells (which may be called subcells, for example). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell whose physical range fluctuates quasi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

[0276] Terminal 20 may be connected to at least one of the multiple base stations 10. Terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

[0277] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz. Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be in a frequency band higher than FR2.

[0278] Furthermore, terminal 20 may communicate in each CC using at least one of time division duplex (TDD) and frequency division duplex (FDD).

[0279] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 / Xn interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0280] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN, 5GC), Next Generation Core (NGC), etc.

[0281] The core network 30 may include, for example, network functions (Network Functions (NFs)) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM)). Multiple functions may be provided by a single network node (which may simply be called a node). Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

[0282] Terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0283] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0284] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

[0285] In the wireless communication system 1, a Physical Downlink Shared Channel (PDSCH), a Broadcast Channel (PBCH), or a Physical Downlink Control Channel (PDCCH) may be used as the downlink channel, which is shared by each terminal 20.

[0286] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Random Access Channel (PRACH), or the like, all of which are shared by each terminal 20.

[0287] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

[0288] Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH.

[0289] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

[0290] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. A UE may monitor CORESETs associated with a given search space based on the search space configuration.

[0291] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0292] PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery acknowledgment information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0293] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[0294] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc., may be transmitted. In the wireless communication system 1, the DL-RS may include a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc.

[0295] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0296] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

[0297] (Base Station) Figure 3 shows an example of the configuration of a base station according to one embodiment of the present disclosure. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

[0298] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0299] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

[0300] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 120, transmitting / receiving antenna 130, and transmission path interface 140. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 120. The control unit 110 may also perform call processing of communication channels (setting, releasing, etc.), status management of the base station 10, management of wireless resources, etc.

[0301] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0302] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0303] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0304] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

[0305] The transmitting / receiving unit 120 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0306] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), and the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), to generate a bit sequence to be transmitted.

[0307] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0308] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

[0309] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 130.

[0310] The transmitting / receiving unit 120 (receiving processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0311] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc., based on the received signal. The measurement unit 123 may also measure received power (e.g., Reference Signal Received Power (RSRP)), reception quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0312] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the terminal 20.

[0313] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0314] The base station 10 may be separated into three elements: a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU may implement higher-level physical layer functions (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0315] In this disclosure, base station 10 may include a single device that implements all the functions of RU, DU, and CU, or it may include multiple devices that each implement some of the functions of RU, DU, and CU and are connected to each other. In this disclosure, base station 10 may be interpreted as RU / DU / CU.

[0316] The transmitting / receiving unit 120 may also transmit configuration information for reporting channel status information (UEI-CSI) initiated by the terminal.

[0317] The control unit 110 may instruct the system to evaluate events related to at least one of the channel measurement results and interference measurement results using the setting information, and may control the reception of the UEI-CSI reported when specific conditions related to the event are met.

[0318] (Terminal) Figure 4 shows an example of the configuration of a terminal according to one embodiment of the present disclosure. The terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0319] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0320] The control unit 210 performs control of the entire terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

[0321] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 220 and the transmitting / receiving antenna 230. The control unit 210 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 220.

[0322] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0323] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0324] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0325] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0326] The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0327] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210 to generate a bit sequence to be transmitted.

[0328] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0329] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

[0330] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.

[0331] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 230.

[0332] The transmitting / receiving unit 220 (receiving processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0333] The transmitting / receiving unit 220 (measuring unit 223) may perform measurements related to the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measuring unit 223 may also measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0334] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may be, for example, Non Zero Power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

[0335] In this disclosure, the transmitting unit and receiving unit of the terminal 20 may be composed of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0336] The transmitting / receiving unit 220 may receive configuration information for reporting channel status information (UEI-CSI) initiated by the terminal. The control unit 210 may evaluate an event related to at least one of the channel measurement results and interference measurement results based on the configuration information, and control the system to report the UEI-CSI when specific conditions related to the event are met. (First Embodiment / Second Embodiment)

[0337] The control unit 210 may evaluate whether the event is met once or multiple times for each measurement occasion (second embodiment).

[0338] The control unit 210 may evaluate the event based on the averaged measurement results of multiple measurement occasions within a specific period (specific time window) (second embodiment).

[0339] The control unit 210 may determine the report content in the UEI-CSI and control the transmission of information indicating the report content (third embodiment).

[0340] (Hardware Configuration) The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by hardware, software, or a combination thereof. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0341] For example, a base station, terminal, network node, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 5 is a diagram showing an example of the hardware configuration of a base station and terminal according to one embodiment of the present disclosure. The base station 10 and terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0342] In this disclosure, any two terms selected from the set of terms such as apparatus, circuit, device, section, unit, module, chip, and means may be read as interchangeable. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0343] Each function in the base station 10 and terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or to control the reading, writing, or both of the reading and writing of data in the memory 1002 and storage 1003.

[0344] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001. Although only one processor 1001 is shown, there may be multiple processors.

[0345] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from the storage 1003, the communication device 1004, or both the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

[0346] The various processes described above may be executed by a single processor 1001, or by two or more processors 1001 simultaneously, sequentially, or by other means. The processor 1001 may be implemented using one or more chips. The program may be transmitted from a network via a telecommunications line, or provided to the computer device via, for example, a communication device 1004.

[0347] Furthermore, this disclosure also provides a computer program product, which includes a computer program. This computer program product may implement the steps of the method described in the above embodiments when the computer program is executed by a computer (for example, a processor 1001).

[0348] Memory 1002 is a non-temporary computer-readable recording medium and may consist of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or at least two combinations thereof. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of the present disclosure.

[0349] The storage 1003 is a [non-temporary] computer-readable recording medium, which may consist of, for example, a flexible disk, a floppy disk, an optical disk (e.g., Compact Disc ROM (CD-ROM), etc.), a digital multipurpose disk, a Blu-ray disk), a magneto-optical disk, a removable disk, a hard disk drive, a smart card, flash memory (e.g., a card, stick, key drive), a magnetic stripe, or at least two of these. The storage 1003 may also be called an auxiliary storage device.

[0350] The recording medium described above may be, for example, a memory 1002, a storage 1003, or a database, server, or other suitable medium including both the memory 1002 and the storage 1003.

[0351] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, or at least two combinations thereof. For example, the above-mentioned transmit / receive unit 120 (220), transmit / receive antenna 130 (230), etc., may be implemented by the communication device 1004. The transmit / receive unit 120 (220) may be implemented in physically or logically separated form, consisting of a transmit unit 120a (220a) and a receive unit 120b (220b).

[0352] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc., or at least two combinations thereof). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc., or at least two combinations thereof). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0353] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0354] Furthermore, the base station 10 and terminal 20 may be configured with hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), a graphics processing unit (GPU), a neural processing unit (NPU), or a combination of at least two of these, and some or all of each functional block may be realized using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0355] In this disclosure, the term “processor” may encompass a single processor or a group of processors, including, for example, a single-core processor, a multi-core processor, multiple processors in a single device, or multiple processors that can communicate with each other by wire or wireless means. Similarly, the term “[non-temporary] computer-readable recording medium” may encompass a single storage medium or a group of storage mediums, including multiple storage mediums that can communicate with each other by wire or wireless means.

[0356] The devices in this disclosure, such as processors and storage media, may be distributed locally or remotely, and may perform processing by operating cooperatively or independently using buses, networks, the internet, clouds, etc.

[0357] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

[0358] (Modifications) Each aspect / embodiment described in this disclosure is Long Term Evolution (LTE), LTE-Advanced (LTE-A), International Mobile Telecommunications-Advanced (IMT-Advanced), 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G-Advanced (5G-A), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), Open Radio Access Network (Open RAN (O-RAN)), Wideband Code Division Multiple Access (W-CDMA®), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.11x (where x is any string such as b, a, g, n, ac, ax, be, bn, etc., and x=n is Wi-Fi4, x=ac is Wi-Fi5, x=ax is Wi-Fi6 or Wi-Fi6E, x=be is Wi-Fi7, x=bn is Wi-Fi8, etc.)The invention may also be applied to systems based on technologies such as Wi-Fi (a registered trademark), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, network virtualization technologies (e.g., Network Function Virtualization (NFV), Service Function Chaining (SFC), Software Defined Networking (SDN)), or Low Power Wide Area (LPWA). Furthermore, each aspect / embodiment described in this disclosure may be applied to systems based on a combination of at least two of these technologies. Hereinafter, "based on" means not only systems that utilize the technologies, but also systems that utilize extensions or modifications of the technologies.

[0359] In this disclosure, the terms "Base Station (BS)", "Radio Base Station", "Fixed Station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "Access Point (AP)", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Radio Unit (RU)", "Remote Unit (RU)", "Control Unit (CU)", "Distributed Unit (DU)", "Remote Radio Head (RRH)", "Node", "Gateway", "Ground Base Station", "Stratospheric Base Station", "Unmanned Aerial Vehicle", "High Altitude Platform Station (HAPS)", "Airborne Platform", "Panel", "Cell", and "Radio Access Network (Radio Access)" are used. Any two terms selected from the set of terms such as "Network (RAN)" and "Network" may be used interchangeably. Each cell accommodated by a base station may be referred to by terms such as macrocell, small cell, femtocell, picocell, serving cell, or supercell. In this disclosure, any two terms selected from the set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.

[0360] In this disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "module", and "terminal" may be used interchangeably.

[0361] The terminal may be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, router (e.g., home router, mobile router, etc.), Telematics Control Unit (TCU), or some other appropriate term.

[0362] A base station and a terminal may each consist of one or more devices. At least some of the devices constituting a base station and a terminal may be called a transmitting device, a receiving device, a wireless communication device, etc. Furthermore, the devices constituting at least a part of each base station and terminal may be, but are not limited to, objects themselves such as vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, and Internet of Things (IoT) devices (e.g., smart meters, sensors), or include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object in question may be a moving object (hereinafter referred to as a "moving object," without prejudice that the moving object may be in a stationary state) or a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0363] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the various aspects / embodiments of this disclosure may be applied to configurations in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.) or communication over a Non-Terrestrial Network (NTN). In this case, the terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink") or terms corresponding to NTN (for example, feeder link, service link). For example, uplink channel, downlink channel, etc., may be interpreted as sidelink channel.

[0364] Furthermore, this disclosure is also applicable when at least some of the equipment constituting the base station and terminal operates outside of the ground (for example, in the atmosphere or in outer space).

[0365] Similarly, the term "terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the terminal 20 described above.

[0366] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node, or by a part of it (e.g., CU, RU, DU, etc.). It is clear that various operations performed for communication with terminals in a RAN or core network may be performed by at least a part of the base station and other network nodes other than the base station. The other network nodes may be a single node or a combination of multiple nodes. A network node is, for example, a node provided in various core networks such as an Evolved Packet Core (EPC) or a 5G Core Network (5GCN, 5GC), and provides one or more Network Functions (NFs).

[0367] Furthermore, in this disclosure, the action of "a terminal receiving information from a base station" is accompanied by the actions of "a base station transmitting the information to the terminal," "a base station generating the information," or both. Similarly, the action of "a terminal transmitting information to a base station" is accompanied by the action of "a base station receiving the information from the terminal." In addition, actions such as "a terminal is configured to..." or "a terminal is configured to..." may include the actions of "a base station transmitting configuration information regarding the terminal's settings" or "the terminal configuring a predetermined action based on the configuration information."

[0368] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or at least two combinations thereof.

[0369] Physical layer signaling may also be called Layer 1 (L1) control information. MAC signaling may be called, for example, a MAC control element (CE), a MAC protocol data unit (PDU), etc. RRC signaling may also be called an RRC message or an information element (IE) within such an RRC message. Such RRC signaling may be a message used for, for example, controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, measurement report, terminal capability notification, etc., or it may be an information element within such a message.

[0370] Furthermore, notification of information may be explicit or implicit. Explicit notification of information means notifying the information itself, while implicit notification of information may be notification of other information or the fulfillment of certain conditions which constitutes notification of the information.

[0371] Furthermore, information notification may include not only notifications between the same layer of different devices (for example, between lower layers or upper layers of base station 10 and terminal 20), but also notifications between different layers within the same or different devices (for example, between lower layers and upper layers within base station 10 or terminal 20). Also, information notification from one device to another may be carried out via one or more devices.

[0372] Any information described in this disclosure (e.g., variables, constants, parameters, settings) may be communicated from any first device (e.g., terminal / base station) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any first device (e.g., base station / terminal) to any secondbase station) to any second device (e.g., base station / base station) to any second device (e.g., base station / base station) to any second device (e.g., base station / base station) to

[0373] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented. Also, at least one step may be omitted in the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure.

[0374] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0375] In this disclosure, a radio resource may be defined as a combination of units of resources in one or more domains, such as the time domain, frequency domain, spatial domain, code domain, and power domain.

[0376] For example, a resource in the time domain (which may also be called a time resource) may be defined by one or more time units. These one or more time units may include, for example, a radio frame, a subframe, a slot, a symbol, and a transmission time interval (TTI), or at least two of these, but the names of the time units are not limited to these. Furthermore, these time units may be fixed-length time units that do not depend on numerology, variable-length time units that depend on numerology, or both.

[0377] Examples of fixed-length time units include, but are not limited to, subframes consisting of one or more slots, and wireless frames containing multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots containing a fixed number of symbols. A certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, mini-slots consisting of fewer symbols than the number of symbols that make up a slot. Such time units may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in this disclosure may be interpreted as a substitute for another time unit.

[0378] Numerology refers to parameters that define the physical layer structure, and may be parameters based on at least one of the following: subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time.

[0379] Resources in the frequency domain (which may also be called frequency resources) may be defined, for example, by one or more frequency units. Such one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or at least two combinations thereof, but the names of frequency units are not limited to these. Furthermore, the number of subcarriers included in a frequency unit may be a fixed number regardless of the neurology, or it may be a variable number that changes depending on the neurology.

[0380] For example, an RB consists of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of the neurology, and may be, for example, 12, but is not limited thereto. Also, a BWP may consist of, for example, one or more consecutive RBs within a certain carrier bandwidth, but is not limited thereto. One or more BWPs may be set up for a terminal 20 within a single carrier, and at least one of the BWPs may be activated. Furthermore, any frequency unit in this disclosure may be interpreted as any other frequency unit.

[0381] Furthermore, resources in both the time domain and the frequency domain may be defined in one or more time / frequency units, for example, consisting of time units and frequency units. Such time / frequency units are, but are not limited to, a Resource Element (RE) consisting of one symbol and one subcarrier, a Resource Element Group (REG) consisting of a predetermined number of REs, or a Control Resource Set (CORESET) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0382] Resources in a spatial domain (which may also be called spatial resources) may be defined, for example, by one or more spatial units. Such one or more spatial units include, but are not limited to, beams, Multi Input Multi Output (MIMO) layers, antenna ports, or at least two combinations thereof.

[0383] Resources in the code domain (which may also be called code resources) may be defined, for example, by one or more code units. These one or more code units include, but are not limited to, cyclic shifts (CS), orthogonal cover codes (OCC), or combinations thereof.

[0384] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0385] In this disclosure, the words "decide," "determine," "judge," "select," "specify," "compute," "calculate," "process," "derive," "look up / search / inquiry," "confirm," "assume," "expect," and "consider" may be interpreted interchangeably. Also, in this disclosure, performing a certain process (e.g., sending, receiving) may be interpreted interchangeably with deciding to perform that process. Furthermore, in this disclosure, "do not assume that..." may be interpreted interchangeably with "assume that..."

[0386] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased as "An apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

[0387] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0388] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0389] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

[0390] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0391] In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial relation information,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “port,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably.

[0392] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel (e.g., a DeModulation Reference Signal (DMRS) port)." In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel (e.g., a reference signal resource)." Furthermore, a spatial domain filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0393] In this disclosure, beam, sounding reference signal (SRS), resource indicator (SRS Resource Indicator (SRI)), control resource set (CORESET), CORESET pool, physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH), codeword (CW), transport block (TB), reference signal (RS) and the like may be interchangeable.

[0394] In this disclosure, TCI state, TCI, Downlink (DL) TCI state, Uplink (UL) TCI state, unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.

[0395] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

[0396] In this disclosure, the terms index, identifier (ID), identity (ID), indicator, indication, resource ID, etc., may be interpreted interchangeably. In this disclosure, the terms sequence, list, set, group, cluster, subset, etc., may be interpreted interchangeably.

[0397] In this disclosure, the group may include, for example, at least one of the following: a spatial relationship group, a Code Division Multiplexing (CDM) group, an RS group, a CORESET group, a Physical Uplink Control Channel (PUCCH) group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, or a panel group.

[0398] The information in this disclosure (e.g., variables, constants, parameters, settings) may be interpreted as IDs of such information. For example, TCI status and TCI status ID may be interpreted as IDs of such information. In addition, the information in this disclosure may be interpreted as "a set of such information," "one or more such pieces of information," etc.

[0399] Any signal / channel in this disclosure (e.g., PUCCH) may be interpreted as another signal / channel (e.g., PUSCH, PDSCH, any RS). A signal / channel may be interpreted as a signal / channel for the same direction (e.g., if the above signal / channel is in the UL direction, it is UL, and if it is in the DL direction, it is DL), or as a signal / channel for the opposite direction (e.g., if the above signal / channel is in the UL direction, it is DL, and if it is in the DL direction, it is UL). Also, in this disclosure, descriptions relating to DL communication and descriptions relating to UL communication may be interpreted as one another. In this case, the operation of DL (UL) may be interpreted as the operation of the corresponding UL (DL). For example, the reception of PDSCH at a terminal may be interpreted as the transmission of PUSCH at the same terminal.

[0400] In this disclosure, "X's number," "X number," "the number of X(s)," and "a number of X(s)" may be interpreted as interchangeable. Herein, X may be replaced with a noun, gerund, or ordinary sentence as appropriate, depending on the context. In this disclosure, "number" may be interpreted as maximum number, minimum number, average number, total number, etc. Furthermore, in this disclosure, terms related to "value," "index," "number," and "quantity" may be interpreted as interchangeable.

[0401] Values / ranges in this disclosure may be interpreted as approximations, as if preceded by the words “about” or “near.” In this disclosure, “[A and B] [are] the same” (where A and B are any words) may mean “[A and B] [are] identical,” “[A and B] [are] almost the same,” “[A and B] [are] partly the same (or [partly] overlapped),” or “[There is] an error within a certain range [between A and B]” (i.e., these words may be interpreted as interchangeable). Furthermore, in this disclosure, "A and B are the same" may mean that at least part of A and at least part of B are the same (or overlapped).

[0402] In this disclosure, “one embodiment,” “several embodiments,” and “another embodiment” may be used interchangeably. In this disclosure, the terms “one embodiment,” “several embodiments,” and “another embodiment” do not necessarily all refer to the same embodiment, nor do they necessarily mean that they are mutually exclusive.

[0403] In this disclosure, expressions such as “at least one of A and B,” “at least one of A or B,” “A and / or B,” and “A / B” may be interpreted as including “only A,” “only B,” or “both A and B.” Furthermore, in this disclosure, expressions such as “at least one of A, B or C,” “at least one of A, B or C,” “A, B and / or C,” and “A / B / C” may be interpreted as including “only A,” “only B,” “only C,” “A and B,” “B and C,” “C and A,” or “all of A, B and C.” Similar reinterpretations may be applied to any expression in this disclosure that means "at least X of ..." (where the number of elements in "..." and X are arbitrary numbers).

[0404] In this disclosure, expressions such as “A, [and] B, and the like” / “such as A and B”,” “A, [or] B, or the like” / “such as A or B”,” “A, B, etc.” / “A, B, and so on” / “A, B, and so forth”,” and “A, B, [and / or] the others” may be interpreted as one another.

[0405] In this disclosure, expressions representing one / singular X (e.g., "a X," "one X," "a single X"), expressions representing one or more X (e.g., "one or more X(s)," "at least one of X(s)"), and expressions representing multiple X (e.g., "Xs," "more than one X(s)," "multiple X(s)," "a plurality of X(s)") may be interpreted as one another. These expressions may also be interpreted as one another with expressions that include specific wording (e.g., "pieces of," "amount of," etc., when X is an uncountable noun). For example, "a plurality of pieces of spatial relation information" may be interpreted as "a plurality of spatial relation information."

[0406] The above description of the disclosure is illustrative, and the present invention is not limited to the embodiments described herein. The disclosure can be implemented as modified and altered forms without departing from the spirit of the invention. The disclosure and its modifications and altered forms are included within the scope of the present invention and its equivalents.

Claims

1. A terminal having a receiving unit that receives setting information for reporting channel status information (UEI-CSI) initiated by the terminal, and a control unit that evaluates an event related to at least one of the channel measurement results and interference measurement results based on the setting information, and controls the terminal to report the UEI-CSI when specific conditions related to the event are met.

2. The terminal according to claim 1, wherein the control unit evaluates whether the event is met once or multiple times for each measurement occasion.

3. The terminal according to claim 1, wherein the control unit evaluates the event based on the averaged measurement results of multiple measurement occasions within a specific period.

4. The terminal according to claim 1, wherein the control unit determines the report content in the UEI-CSI and controls the transmission of information indicating the report content.

5. A wireless communication method for a terminal, comprising the steps of: receiving configuration information for reporting channel status information (UEI-CSI) initiated by the terminal; and evaluating an event related to at least one of channel measurement results and interference measurement results based on the configuration information, and controlling the terminal to report the UEI-CSI when specific conditions relating to the event are met.

6. A base station having: a transmitting unit that transmits configuration information for reporting channel status information (UEI-CSI) initiated by a terminal; and a control unit that instructs the evaluation of an event related to at least one of the channel measurement results and interference measurement results using the configuration information, and controls the reception of the UEI-CSI reported when specific conditions related to the event are met.