Method and device for transmitting / receiving channel state information in wireless communication system

Abstract

A method and a device for transmitting / receiving channel state information in a wireless communication system are disclosed. The method according to one embodiment of the present disclosure may comprise steps in which a UE: receives configuration information related to a CSI report from a base station; receives a downlink RS on one or more resources from the base station; transmits, to the base station, a first uplink transmission related to whether an event related to the CSI report has occurred; and transmits, to the base station, a second uplink transmission including a report value derived on the basis of the downlink RS.

Description

Method and device for transmitting and receiving channel state information in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for transmitting and receiving channel state information in a wireless communication system.

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, they have expanded beyond voice to include data services. Currently, explosive growth in traffic is leading to resource shortages and users' demand for higher-speed services, necessitating a more advanced mobile communication system.

[0003] Next-generation mobile communication systems must support explosive data traffic growth, dramatically increasing data rates per user, a vastly increased number of connected devices, ultra-low end-to-end latency, and high energy efficiency. To achieve these goals, various technologies are being studied, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.

[0004] The technical problem of the present disclosure is to provide a method and device for transmitting and receiving channel state information (CSI) (including beam reporting).

[0005] In addition, an additional technical challenge of the present disclosure is to provide a method and apparatus for performing UE-initiated or event-driven beam reporting.

[0006] In addition, an additional technical problem of the present disclosure is to provide a method and device for counting activated resources of a downlink reference signal for UE-initiated or event-driven beam reporting.

[0007] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0008] A method according to an aspect of the present disclosure may include: receiving, by a user equipment (UE), configuration information related to channel state information (CSI) reporting from a base station; receiving, by the UE, a downlink reference signal (RS) from the base station on one or more resources; transmitting, by the UE, to the base station, a first uplink transmission related to whether an event related to the CSI reporting has occurred; and transmitting, by the UE, to the base station, a second uplink transmission including a report value derived based on the downlink RS. Occurrence of the event may be determined and / or the report value may be derived using one or more active resources among the one or more resources for the downlink RS, and the one or more active resources may be counted X times, where X is an integer greater than 0.

[0009] A method according to an additional aspect of the present disclosure may include: transmitting, to a user equipment (UE), configuration information related to channel state information (CSI) reporting; transmitting, by the base station, a downlink reference signal (RS) to the UE on one or more resources; receiving, by the base station, a first uplink transmission from the UE related to whether an event related to the CSI reporting has occurred; and receiving, by the base station, a second uplink transmission from the UE including a report value derived based on the downlink RS. Occurrence of the event may be determined and / or the report value may be derived using one or more active resources among the one or more resources for the downlink RS, and the one or more active resources may be counted X times, where X is an integer greater than 0.

[0010] According to an embodiment of the present disclosure, beam reporting is possible only when an event is satisfied without additional base station instructions / configuration for beam reporting.

[0011] Additionally, according to the implementation of the present disclosure, signaling overhead can be reduced and flexible / appropriate beam reporting can be performed as the surrounding conditions change.

[0012] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0013] The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.

[0014] Figure 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0015] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0016] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.

[0017] FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied.

[0018] FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0019] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the same.

[0020] FIG. 7 is a diagram illustrating a downlink beam management operation in a wireless communication system to which the present disclosure can be applied.

[0021] FIG. 8 is a diagram illustrating a downlink beam management procedure using SSB in a wireless communication system to which the present disclosure can be applied.

[0022] FIG. 9 is a diagram illustrating a downlink beam management operation using CSI-RS in a wireless communication system to which the present disclosure can be applied.

[0023] FIG. 10 is a diagram illustrating a process for determining a reception beam of a terminal in a wireless communication system to which the present disclosure can be applied.

[0024] FIG. 11 is a diagram illustrating a transmission beam determination process of a base station in a wireless communication system to which the present disclosure can be applied.

[0025] FIG. 12 is a diagram illustrating resource allocation in the time and frequency domains related to the operation of downlink beam management in a wireless communication system to which the present disclosure can be applied.

[0026] FIG. 13 illustrates a UE initiated beam reporting procedure according to one embodiment of the present disclosure.

[0027] FIG. 14 is a diagram illustrating a signaling procedure between a base station and a UE for a UE initiation beam reporting method according to one embodiment of the present disclosure.

[0028] FIG. 15 is a diagram illustrating the operation of a UE for reporting channel state information according to one embodiment of the present disclosure.

[0029] FIG. 16 is a diagram illustrating the operation of a base station for reporting channel state information according to one embodiment of the present disclosure.

[0030] FIG. 17 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0031] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.

[0032] In some cases, to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.

[0033] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0034] In this disclosure, terms such as “first,” “second,” etc. are used only to distinguish one component from another and are not used to limit the components, and do not limit the order or importance between the components unless specifically stated otherwise. Accordingly, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0035] The terminology used herein is for the purpose of describing particular embodiments and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. The term "and / or" as used herein may refer to any one of the associated enumerated items, or is meant to refer to and encompass any and all possible combinations of two or more of them. Furthermore, the use of " / " between words in this disclosure has the same meaning as "and / or" unless otherwise stated.

[0036] The present disclosure describes a wireless communication network or a wireless communication system, and an operation performed in a wireless communication network may be performed in a process of controlling the network and transmitting or receiving a signal from a device (e.g., a base station) that manages the wireless communication network, or may be performed in a process of transmitting or receiving a signal to or between terminals connected to the wireless network.

[0037] In the present disclosure, transmitting or receiving a channel means transmitting or receiving information or a signal through the channel. For example, transmitting a control channel means transmitting control information or a signal through the control channel. Similarly, transmitting a data channel means transmitting data information or a signal through the data channel.

[0038] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal, and a receiver may be part of a base station. A base station may be expressed as a first communication device, and a terminal may be expressed as a second communication device. A base station (BS) may be replaced by terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI (Artificial Intelligence) system / module, RSU (road side unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.In addition, the terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, RSU (road side unit), robot, AI (Artificial Intelligence) module, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0039] The following technologies can be used in various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, and SC-FDMA. CDMA can be implemented using wireless technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented using wireless technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented using wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0040] For clarity, the description is based on the 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​the present disclosure is not limited thereto. LTE refers to technology after 3GPP TS (Technical Specification) 36.xxx Release 8. Specifically, LTE technology after 3GPP TS 36.xxx Release 10 is referred to as LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 is referred to as LTE-A pro. 3GPP NR refers to technology after TS 38.xxx Release 15. LTE / NR may be referred to as a 3GPP system. "xxx" refers to a standard document detail number. LTE / NR may be collectively referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present disclosure, reference may be made to matters described in standard documents published prior to the present disclosure. For example, reference may be made to the following documents.

[0041] For 3GPP LTE, see TS 36.211 (Physical channels and modulation), TS 36.212 (Multiplexing and channel coding), TS 36.213 (Physical layer procedures), TS 36.300 (General description), and TS 36.331 (Radio resource control).

[0042] For 3GPP NR, see TS 38.211 (Physical channels and modulation), TS 38.212 (Multiplexing and channel coding), TS 38.213 (Physical layer procedures for control), TS 38.214 (Physical layer procedures for data), TS 38.300 (Overall description of NR and New Generation-Radio Access Network (NG-RAN)), and TS 38.331 (Radio Resource Control Protocol Specification).

[0043] Abbreviations for terms that may be used in this disclosure are defined as follows.

[0044] - BM: beam management

[0045] - CQI: Channel Quality Indicator

[0046] - CRI: Channel state information - reference signal resource indicator

[0047] - CSI: Channel State Information

[0048] - CSI-IM: Channel State Information - Interference Measurement

[0049] - CSI-RS: Channel state information - reference signal

[0050] - DMRS: Demodulation Reference Signal

[0051] - FDM: frequency division multiplexing

[0052] - FFT: fast Fourier transform

[0053] - IFDMA: interleaved frequency division multiple access

[0054] - IFFT: inverse fast Fourier transform

[0055] - L1-RSRP: Layer 1 reference signal received power

[0056] - L1-RSRQ: Layer 1 reference signal received quality

[0057] - MAC: Medium Access Control

[0058] - NZP: non-zero power

[0059] - OFDM: orthogonal frequency division multiplexing

[0060] - PDCCH: Physical downlink control channel

[0061] - PDSCH: Physical downlink shared channel

[0062] - PMI: precoding matrix indicator

[0063] - RE: resource element

[0064] - RI: Rank indicator

[0065] - RRC: Radio Resource Control

[0066] - RSSI: Received signal strength indicator

[0067] - Rx: Reception

[0068] - QCL: quasi co-location

[0069] - SINR: signal to interference and noise ratio

[0070] - SSB (or SS / PBCH block): Synchronization signal block (including primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH))

[0071] - TDM: Time Division Multiplexing

[0072] - TRP: transmission and reception point

[0073] - TRS: Tracking Reference Signal

[0074] - Tx: transmission

[0075] - UE: user equipment

[0076] - ZP: Zero Power

[0077] System General

[0078] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communications compared to existing radio access technologies (RATs) is emerging. Furthermore, massive Machine Type Communications (MTC), which connects numerous devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. Accordingly, the introduction of next-generation RATs that consider enhanced mobile broadband communication (eMBB), massive MTC (MMTC), and Ultra-Reliable and Low Latency Communication (URLLC) is being discussed. For convenience, these technologies are referred to as NR in this disclosure. NR is an expression representing an example of 5G RAT.

[0079] A new RAT system, including NR, uses OFDM or a similar transmission scheme. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Alternatively, a single cell may support multiple numerologies. That is, terminals operating under different numerologies can coexist within a single cell.

[0080] A numerology corresponds to a single subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

[0081] Figure 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0082] Referring to Fig. 1, the NG-RAN consists of gNBs that provide NG-RA (NG-Radio Access) user plane (i.e., new AS (access stratum) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and control plane (RRC) protocol termination for UE. The gNBs are interconnected via Xn interfaces. The gNBs are also connected to the NGC (New Generation Core) via the NG interface. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Function) via the N2 interface and to the UPF (User Plane Function) via the N3 interface.

[0083] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0084] NR systems can support multiple numerologies. Numerologies can be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings can be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). Furthermore, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies, the numerology used can be selected independently of the frequency band. Furthermore, NR systems can support various frame structures corresponding to multiple numerologies.

[0085] Below, we examine OFDM numerologies and frame structures that can be considered in NR systems. The various OFDM numerologies supported in NR systems can be defined as shown in Table 1 below.

[0086] μΔf=2 μ ·15 [kHz]CP015 Normal 130 Normal 260 Normal, Extended 3120 Normal 4240 Normal

[0087] NR supports multiple numerologies (or subcarrier spacings (SCS)) to support various 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0088] The NR frequency band is defined by two types of frequency ranges (FR1 and FR2). FR1 and FR2 can be configured as shown in Table 2 below. FR2 can also mean millimeter wave (mmW).

[0089] Frequency Range Designation Corresponding Frequency Range Subcarrier Spacing FR1410MHz - 7125MHz 15, 30, 60kHz FR224250MHz - 52600MHz 60, 120, 240kHz

[0090] Regarding the frame structure in the NR system, the sizes of the various fields in the time domain are T c =1 / (Δf max ·N f ) is expressed as a multiple of the time unit. Here, Δf max =480·10 3 Hz and N f =4096. Downlink and uplink transmissions are T f =1 / (Δf max N f / 100)·T c = It is organized into radio frames with a duration of 10ms. Here, each radio frame is T sf =(Δf max N f / 1000)·T c =1ms It consists of 10 subframes with an interval of . In this case, there may be one set of frames for uplink and one set of frames for downlink. In addition, transmission in uplink frame number i from a terminal is T earlier than the start of the corresponding downlink frame from the terminal.TA =(N TA +N TA,offset )T c It should start before. For the subcarrier spacing configuration μ, slots are n within a subframe. s μ ∈{0,..., N slot subframe,μ-1} are numbered in increasing order, and n within a radio frame. s,f μ ∈{0,..., N slot frame,μ -1} are numbered in increasing order. One slot is N symb slot It consists of consecutive OFDM symbols, and N symb slot is determined by CP. Slot n in subframe s μ The start of OFDM symbol n in the same subframe s μ N symb slot are aligned temporally with the start of the OFDM signal. Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in a downlink slot or uplink slot can be utilized.

[0091] Table 3 shows the number of OFDM symbols per slot in a general CP (N symb slot ), the number of slots per wireless frame (N slot frame,μ ), number of slots per subframe (N slot subframe,μ), and Table 4 shows the number of OFDM symbols per slot in the extended CP, the number of slots per radio frame, and the number of slots per subframe.

[0092] μN symb slot N slot frame,μ N slotsubframe,μ01410111420221440431480841416016

[0093] μN symb slot N slot frame,μ N slot subframe,μ212404

[0094] FIG. 2 is an example when μ=2 (SCS is 60 kHz), and referring to Table 3, 1 subframe can include 4 slots. 1 subframe={1,2,4} slot illustrated in FIG. 2 is an example, and the number of slot(s) that can be included in 1 subframe is defined as in Table 3 or Table 4. In addition, a mini-slot can include 2, 4, or 7 symbols, or more or fewer symbols.

[0095] Regarding physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. can be considered. Below, the physical resources that can be considered in an NR system will be examined in detail.

[0096] First, with respect to antenna ports, antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. Two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-location) relationship if the large-scale properties of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on another antenna port is carried. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0097] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.

[0098] Referring to Figure 3, the resource grid is N in the frequency domain. RB μ N sc RB It consists of subcarriers, and one subframe is 14·2 μ It is described as an example, but not limited to, that it consists of OFDM symbols. In an NR system, the transmitted signal is N RB μ N sc RB One or more resource grids consisting of subcarriers and 2 μ N symb (μ) is described by OFDM symbols. Here, N RB μ≤ N RB max,μ is. The above N RB max,μrepresents the maximum transmission bandwidth, which may vary between uplink and downlink as well as between numerologies. In this case, one resource grid may be configured for μ and each antenna port p. Each element of the resource grid for μ and each antenna port p is referred to as a resource element and is uniquely identified by an index pair (k, l'). Here, k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, and l'=0,...,2 μ N symb (μ) -1 indicates the position of the symbol within the subframe. When referring to a resource element in a slot, an index pair (k,l) is used. Here, l=0,...,N symb μ -1. The resource element (k,l') for μ and antenna port p is a complex value a k,l' (p,μ) . If there is no risk of confusion or if a particular antenna port or numerology is not specified, the indices p and μ can be dropped, resulting in a complex value of a k,l' (p) or a k,l' This can be. Also, a resource block (RB) is N in the frequency domain. sc RB =12 is defined as consecutive subcarriers.

[0099] Point A serves as a common reference point of the resource block grid and is obtained as follows.

[0100] - offsetToPointA for the Primary Cell (PCell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block used by the UE for initial cell selection. It is expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2.

[0101] - absoluteFrequencyPointA represents the frequency-position of point A expressed as ARFCN (absolute radio-frequency channel number).

[0102] Common resource blocks (CRBs) are numbered from 0 upwards in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of CRB 0 for a subcarrier spacing setting μ coincides with 'point A'. CRB number n in the frequency domain CRB μ The relationship between the resource elements (k,l) and the subcarrier spacing setting μ is given by the following mathematical expression 1.

[0103]

[0104] In Equation 1, k is defined relative to point A such that k = 0 corresponds to the subcarrier centered at point A. Physical resource blocks are numbered from 0 to N within the bandwidth part (BWP). BWP,i size,μ - Numbered from -1, where i is the number of the BWP. Physical resource block n in BWP i PRB and common resource block n CRB The relationship between them is given by the mathematical formula 2 below.

[0105]

[0106] N BWP,i start,μ is a common resource block where BWP starts relative to common resource block 0.

[0107] FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied. FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0108] Referring to FIGS. 4 and 5, a slot includes multiple symbols in the time domain. For example, in the case of a normal CP, one slot includes seven symbols, but in the case of an extended CP, one slot includes six symbols.

[0109] A carrier comprises multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) is defined as multiple consecutive (physical) resource blocks in the frequency domain, and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can comprise up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated for a single terminal. Each element in the resource grid is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0110] The NR system can support up to 400 MHz per component carrier (CC). If a terminal operating in such a wideband CC always operates with the radio frequency (RF) chip for the entire CC turned on, the terminal battery consumption may increase. Alternatively, when considering multiple use cases operating within a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band within the CC. Alternatively, each terminal may have different maximum bandwidth capabilities. Considering this, the base station can instruct the terminal to operate only on a portion of the bandwidth rather than the entire bandwidth of the wideband CC, and this portion of bandwidth is conveniently defined as the bandwidth part (BWP). A BWP can be composed of consecutive RBs on the frequency axis and can correspond to a single numerology (e.g., subcarrier spacing, CP length, slot / mini-slot interval).

[0111] Meanwhile, the base station can configure multiple BWPs even within a single CC configured for a terminal. For example, in the PDCCH monitoring slot, a BWP occupying a relatively small frequency range can be configured, and the PDSCH indicated by the PDCCH can be scheduled on a larger BWP. Alternatively, if UEs are concentrated on a specific BWP, some terminals can be configured to a different BWP for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, a portion of the spectrum in the middle of the entire bandwidth can be excluded and both BWPs can be configured within the same slot. In other words, the base station can configure at least one DL / UL BWP for a terminal associated with a wideband CC. The base station can activate at least one DL / UL BWP(s) among the configured DL / UL BWP(s) at a specific time (via L1 signaling, MAC CE (Control Element), RRC signaling, etc.). Additionally, the base station can instruct switching to another configured DL / UL BWP (e.g., via L1 signaling or MAC CE or RRC signaling). Alternatively, switching to a configured DL / UL BWP can be performed based on a timer when the timer value expires. In this case, the activated DL / UL BWP is defined as the active DL / UL BWP. However, in situations such as when the terminal is performing the initial access process or before the RRC connection is set up, the configuration for the DL / UL BWP may not be received. Therefore, in these situations, the DL / UL BWP assumed by the terminal is defined as the initially active DL / UL BWP.

[0112] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the same.

[0113] In wireless communication systems, terminals receive information from a base station via the downlink and transmit it to the base station via the uplink. The information transmitted and received between the base station and terminals includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.

[0114] When a terminal is powered on or enters a new cell, it performs an initial cell search operation, such as synchronizing with the base station (S601). To this end, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell identifier (ID). Afterwards, the terminal can receive a physical broadcast channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, the terminal can receive a downlink reference signal (DL RS) during the initial cell search phase to check the downlink channel status.

[0115] A terminal that has completed initial cell search can obtain more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information included in the PDCCH (S602).

[0116] Meanwhile, when accessing a base station for the first time or when there are no radio resources for signal transmission, the terminal may perform a random access procedure (RACH) for the base station (steps S603 to S606). To this end, the terminal may transmit a specific sequence as a preamble via the Physical Random Access Channel (PRACH) (steps S603 and S605) and receive a response message to the preamble via the Physical Data Channel Control Channel (PDCCH) and the corresponding PDSCH (steps S604 and S606). In the case of a contention-based RACH, a contention resolution procedure (Contention Resolution Procedure) may additionally be performed.

[0117] The terminal that has performed the procedure described above can then perform PDCCH / PDSCH reception (S607) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S608) as general uplink / downlink signal transmission procedures. In particular, the terminal receives downlink control information (DCI) through the PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format varies depending on the purpose of use.

[0118] Meanwhile, the control information that the terminal transmits to the base station via the uplink or that the terminal receives from the base station includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In the case of the 3GPP LTE system, the terminal can transmit the above-described control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

[0119] Table 5 shows an example of the DCI format in the NR system.

[0120] DCI Format Utilization 0_0 Scheduling of PUSCH within a cell 0_1 Scheduling of one or multiple PUSCH within a cell, or indicating cell group (CG: cell group) downlink feedback information to the UE 0_2 Scheduling of PUSCH within a cell 1_0 Scheduling of PDSCH within a DL cell 1_1 Scheduling of PDSCH within a cell 1_2 Scheduling of PDSCH within a cell

[0121] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to scheduling of PUSCH (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), HARQ (Hybrid - Automatic Repeat and request) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined.

[0122] DCI format 0_0 is used for scheduling PUSCH in a cell. The information contained in DCI format 0_0 is transmitted after being scrambled with a CRC (cyclic redundancy check) by a C-RNTI (Cell RNTI: Cell Radio Network Temporary Identifier), a CS-RNTI (Configured Scheduling RNTI), or a MCS-C-RNTI (Modulation Coding Scheme Cell RNTI).

[0123] DCI format 0_1 ​​is used to indicate scheduling of one or more PUSCHs in a single cell, or configure grant (CG: configure grant) downlink feedback information to the UE. The information contained in DCI format 0_1 ​​is CRC-scrambled and transmitted using the C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI.

[0124] DCI format 0_2 is used for scheduling PUSCH in a cell. The information contained in DCI format 0_2 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0125] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to scheduling of PDSCH (e.g., frequency resource allocation, time resource allocation, virtual resource block (VRB)-physical resource block (PRB) mapping, etc.), transport block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., antenna port, transmission configuration indicator (TCI), sounding reference signal (SRS) request, etc.), PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format may be predefined.

[0126] DCI format 1_0 is used for scheduling PDSCH in a DL cell. The information contained in DCI format 1_0 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0127] DCI format 1_1 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_1 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0128] DCI format 1_2 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_2 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0129] Quasi-Co Location (QCL)

[0130] Antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. Two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-location) relationship if the properties of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on another antenna port is carried.

[0131] Here, the channel characteristics include one or more of delay spread, Doppler spread, frequency / Doppler shift, average received power, received timing / average delay, and spatial Rx parameter. Here, the spatial Rx parameter refers to a spatial (reception) channel characteristic parameter such as angle of arrival.

[0132] A terminal may be configured with a list of up to M TCI-State settings in the upper layer parameter PDSCH-Config to decode PDSCHs based on detected PDCCHs having DCI intended for the terminal and a given serving cell. M depends on the UE capability.

[0133] Each TCI-State contains parameters for establishing a quasi co-location relationship between one or two DL reference signals and the DM-RS port of the PDSCH.

[0134] The quasi-colocation relationship is established by the upper-layer parameters qcl-Type1 for the first DL RS and qcl-Type2 (if set) for the second DL RS. For two DL RSs, the QCL types are not the same, regardless of whether the references are the same DL RS or different DL RSs.

[0135] The quasi co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type of QCL-Info, and can take one of the following values:

[0136] - 'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread}

[0137] - 'QCL-TypeB': {Doppler shift, Doppler spread}

[0138] - 'QCL-TypeC': {Doppler shift, average delay}

[0139] - 'QCL-TypeD': {Spatial Rx parameter}

[0140] For example, if a target antenna port is a specific NZP CSI-RS, the corresponding NZP CSI-RS antenna port(s) can be instructed / configured to be QCL with a specific TRS from a QCL-Type A perspective and with a specific SSB from a QCL-Type D perspective. A terminal that has received such an instruction / configuration can receive the corresponding NZP CSI-RS using the Doppler and delay values ​​measured at the QCL-TypeA TRS, and apply the reception beam used for QCL-TypeD SSB reception to the corresponding NZP CSI-RS reception.

[0141] The UE can receive an activation command by MAC CE signaling, which is used to map up to eight TCI states to codepoints in the DCI field 'Transmission Configuration Indication'.

[0142] beam management (BM)

[0143] BM procedures are L1 (layer 1) / L2 (layer 2) procedures for acquiring and maintaining a set of base station (e.g., gNB, TRP, etc.) and / or terminal (e.g., UE) beams that can be used for downlink (DL) and uplink (UL) transmission / reception, and may include the following procedures and terminology.

[0144] - Beam measurement: An operation in which a base station or UE measures the characteristics of a received beam-forming signal.

[0145] - Beam determination: An operation in which a base station or UE selects its own transmit beam (Tx beam) / receive beam (Rx beam).

[0146] - Beam sweeping: The operation of covering a spatial area using a transmit and / or receive beam over a predetermined time interval in a predetermined manner.

[0147] - Beam report: An operation in which a UE reports information about a beam-formed signal based on beam measurement.

[0148] The BM procedure can be divided into (1) a DL BM procedure using SS (synchronization signal) / PBCH (physical broadcast channel) Block or CSI-RS, and (2) a UL BM procedure using SRS (sounding reference signal).

[0149] Additionally, each BM procedure may include transmit beam sweeping (Tx beam sweeping) to determine a transmit beam (Tx beam) and receive beam sweeping (Rx beam sweeping) to determine a receive beam (Rx beam).

[0150] Below, the DL BM procedure is described.

[0151] The DL BM procedure may include (1) transmission of beamformed DL RSs (reference signals) (e.g., CSI-RS or SS Block (SSB)) of the base station and (2) beam reporting of the terminal.

[0152] Here, beam reporting may include preferred DL RS ID(identifier)(s) and corresponding L1-RSRP (Reference Signal Received Power).

[0153] The above DL RS ID may be an SSBRI (SSB Resource Indicator) or a CRI (CSI-RS Resource Indicator).

[0154] Below, the DL BM procedure using SSB is described.

[0155] FIG. 7 is a diagram illustrating a downlink beam management operation in a wireless communication system to which the present disclosure can be applied.

[0156] Referring to Figure 7, SSB beam and CSI-RS beam can be used for beam measurement. The measurement metric is L1-RSRP per resource / block. SSB is used for coarse beam measurement, and CSI-RS can be used for fine beam measurement. SSB can be used for both Tx beam sweeping and Rx beam sweeping.

[0157] Rx beam sweeping using SSB can be performed by the UE changing the Rx beam for the same SSBRI across multiple SSB bursts, where one SS burst includes one or more SSBs, and one SS burst set includes one or more SSB bursts.

[0158] FIG. 8 is a diagram illustrating a downlink beam management procedure using SSB in a wireless communication system to which the present disclosure can be applied.

[0159] The configuration for beam report using SSB is performed during CSI / beam configuration in the RRC connected state (or RRC connected mode).

[0160] Referring to FIG. 8, the terminal receives a CSI-ResourceConfig IE including a CSI-SSB-ResourceSetList including SSB resources used for BM from the base station (S410).

[0161] Table 6 shows an example of the CSI-ResourceConfig IE. As shown in Table 6, the BM configuration using SSB is not defined separately, and SSB is set as a CSI-RS resource.

[0162] -- ASN1START-- TAG-CSI-RESOURCECONFIG-STARTCSI-ResourceConfig ::= SEQUENCE {csi-ResourceConfigId CSI-ResourceConfigId,csi-RS-ResourceSetList CHOICE {nzp-CSI-RS-SSB SEQUENCE {nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetId OPTIONAL,csi-SSB-ResourceSetListSEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetIdOPTIONAL},csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId},bwp-Id BWP-Id,resourceType ENUMERATED { aperiodic, semiPersistent, periodic},...}-- TAG-CSI-RESOURCECONFIGTOADDMOD-STOP-- ASN1STOP

[0163] In Table 6, the csi-SSB-ResourceSetList parameter represents a list of SSB resources used for beam management and reporting in a resource set. Here, the SSB resource set can be set to {SSBx1, SSBx2, SSBx3, SSBx4, ...}. The SSB index can be defined from 0 to 63.

[0164] The terminal receives SSB resources from the base station based on the CSI-SSB-ResourceSetList (S420).

[0165] When CSI-RS reportConfig related to reporting on SSBRI and L1-RSRP is set, the terminal reports (beams) the best SSBRI and its corresponding L1-RSRP to the base station (S430).

[0166] Below, the DL BM procedure using CSI-RS is described.

[0167] Regarding the usage of CSI-RS, i) if the repetition parameter is set for a specific CSI-RS resource set and TRS_info is not set, CSI-RS is used for beam management. ii) if the repetition parameter is not set and TRS_info is set, CSI-RS is used for TRS (tracking reference signal). iii) if the repetition parameter is not set and TRS_info is not set, CSI-RS is used for CSI acquisition.

[0168] This repetition parameter can only be set for CSI-RS resource sets associated with a CSI-ReportConfig that has a report of L1 RSRP or 'No Report (or None)'.

[0169] If a terminal is configured with a CSI-ReportConfig with reportQuantity set to 'cri-RSRP' or 'none', and a CSI-ResourceConfig (upper layer parameter resourcesForChannelMeasurement) for channel measurement does not include the upper layer parameter 'trs-Info' and includes an NZP-CSI-RS-ResourceSet with the upper layer parameter 'repetition' set, the terminal may be configured with only the same number of ports (1-port or 2-port) with the upper layer parameter 'nrofPorts' for all CSI-RS resources in the NZP-CSI-RS-ResourceSet.

[0170] (Upper layer parameter) When repetition is set to 'ON', it is related to the Rx beam sweeping procedure of the terminal. In this case, when the terminal receives the NZP-CSI-RS-ResourceSet, the terminal can assume that at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted through the same downlink spatial domain transmission filter. That is, at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted through the same Tx beam. Here, at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet can be transmitted in a different OFDM symbol. In addition, the terminal does not expect to receive different periods in periodicityAndOffset among all CSI-RS resources in the NZP-CSI-RS-Resourceset.

[0171] On the other hand, when Repetition is set to 'OFF', it is related to the Tx beam sweeping procedure of the base station. In this case, when repetition is set to 'OFF', the terminal does not assume that at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted through the same downlink spatial domain transmission filter. That is, at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted through a different Tx beam.

[0172] That is, when the reportQuantity of the above CSI-RS reportConfig IE is set to 'ssb-Index-RSRP', the terminal reports the best SSBRI and the corresponding L1-RSRP to the base station.

[0173] And, if the terminal sets the CSI-RS resource in the same OFDM symbol(s) as the SSB (SS / PBCH Block) and 'QCL-TypeD' is applicable, the terminal can assume that the CSI-RS and the SSB are quasi co-located from the 'QCL-TypeD' perspective.

[0174] Here, the QCL TypeD may mean that the antenna ports are QCL-connected from the perspective of spatial Rx parameters. When the terminal receives multiple DL antenna ports in a QCL Type D relationship, the same reception beam may be applied. In addition, the terminal does not expect the CSI-RS to be configured in an RE that overlaps with an SSB RE.

[0175] FIG. 9 is a diagram illustrating a downlink beam management operation using CSI-RS in a wireless communication system to which the present disclosure can be applied.

[0176] Fig. 9(a) illustrates a terminal's Rx beam determination (or refinement) procedure, and Fig. 9(b) illustrates a base station's Tx beam sweeping procedure. Furthermore, Fig. 9(a) illustrates a case where the repetition parameter is set to 'ON', and Fig. 9(b) illustrates a case where the repetition parameter is set to 'OFF'.

[0177] FIG. 10 is a diagram illustrating a process for determining a reception beam of a terminal in a wireless communication system to which the present disclosure can be applied.

[0178] Referring to FIG. 9(a) and FIG. 10, the terminal's Rx beam determination process will be examined.

[0179] The terminal receives an NZP CSI-RS resource set IE including an upper layer parameter repetition from the base station via RRC signaling (S610). Here, the repetition parameter is set to 'ON'.

[0180] The terminal repeatedly receives resource(s) within the CSI-RS resource set with repetition 'ON' in different OFDM symbols through the same Tx beam (or DL ​​spatial domain transmission filter) of the base station (S620).

[0181] The terminal determines its own Rx beam (S630).

[0182] The terminal skips CSI reporting (S640). In this case, the reportQuantity of the CSI reporting setting can be set to 'No report (or None)'.

[0183] That is, the terminal may omit CSI reporting when repetition is set to 'ON'.

[0184] FIG. 11 is a diagram illustrating a transmission beam determination process of a base station in a wireless communication system to which the present disclosure can be applied.

[0185] Referring to FIG. 9(b) and FIG. 11, the Tx beam determination process of the base station will be examined.

[0186] The terminal receives an NZP CSI-RS resource set IE including an upper layer parameter repetition from the base station via RRC signaling (S710). Here, the repetition parameter is set to 'OFF' and is related to the Tx beam sweeping procedure of the base station.

[0187] The terminal receives resources within the CSI-RS resource set with repetition set to 'OFF' through different Tx beams (DL spatial domain transmission filters) of the base station (S720).

[0188] The terminal selects (or determines) the best beam (S740)

[0189] The terminal reports the ID and related quality information (e.g., L1-RSRP) for the selected beam to the base station (S740). In this case, the reportQuantity of the CSI reporting configuration can be set to 'CRI + L1-RSRP.'

[0190] That is, the terminal reports the CRI and the L1-RSRP for the CSI-RS to the base station when the CSI-RS is transmitted for the BM.

[0191] FIG. 12 is a diagram illustrating resource allocation in the time and frequency domains related to the operation of downlink beam management in a wireless communication system to which the present disclosure can be applied.

[0192] Referring to FIG. 12, when repetition 'ON' is set to the CSI-RS resource set, multiple CSI-RS resources are repeatedly used by applying the same transmission beam, and when repetition 'OFF' is set to the CSI-RS resource set, different CSI-RS resources are transmitted with different transmission beams.

[0193] Below, a beam indication method related to downlink BM is described.

[0194] A terminal may receive an RRC configuration list of at most M candidate Transmission Configuration Indication (TCI) states for the purpose of at least QCL (Quasi Co-location) indication, where M may be 64.

[0195] Each TCI state can be configured with one RS set. At least, each ID of a DL RS for spatial QCL purposes (QCL Type D) within an RS set can refer to one of the DL RS types, such as SSB, P(periodic)-CSI RS, SP(semi-persistent)-CSI RS, and A(aperiodic)-CSI RS.

[0196] At least the initialization / update of the IDs of DL RS(s) within the RS set used for spatial QCL purposes can be performed at least through explicit signaling.

[0197] Table 7 illustrates the TCI-State information element (IE).

[0198] The TCI-State IE associates one or two DL reference signals (RS) with their corresponding quasi co-location (QCL) types.

[0199] -- ASN1START-- TAG-TCI-STATE-STARTTCI-State ::= SEQUENCE {tci-StateId TCI-StateId,qcl-Type1 QCL-Info,qcl-Type2 QCL-Info OPTIONAL, -- Need R...}QCL-Info ::= SEQUENCE {cell ServCellIndex OPTIONAL, -- Need Rbwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-IndicatedreferenceSignal CHOICE {csi-rs NZP-CSI-RS-ResourceId,ssb SSB-Index},qcl-Type ENUMERATED {typeA, typeB, typeC, typeD},...}-- TAG-TCI-STATE-STOP-- ASN1STOP

[0200] In Table 7, the bwp-Id parameter indicates the DL BWP (bandwidth part) where the RS is located, the cell parameter indicates the carrier where the RS is located, and the referencesignal parameter indicates the reference antenna port(s) or a reference signal including the reference antenna port(s) that is the source of quasi co-location for the corresponding target antenna port(s). The target antenna port(s) may be a CSI-RS, a PDCCH DMRS, or a PDSCH DMRS. For example, in order to indicate QCL reference RS information for a non-zero power (NZP) CSI-RS, a corresponding TCI state ID (identifier) ​​may be indicated in the NZP CSI-RS resource configuration information. In another example, in order to indicate QCL reference information for a PDCCH DMRS antenna port(s), a TCI state ID may be indicated in each CORESET configuration. As another example, the TCI state ID can be indicated via DCI to indicate QCL reference information for the PDSCH DMRS antenna port(s).

[0201] UE initiated beam reporting method

[0202] In wireless communication systems, uplink control information at layer 1 (e.g., the physical layer) has the advantage of shorter transmission delay than control information at higher layers. For example, for a terminal to transmit information to a base station using a MAC CE or RRC message, a scheduling request (SR) procedure by the terminal and a PUSCH allocation procedure by the base station (based on the SR) may be required, resulting in delay and overhead. Furthermore, higher-layer information generally requires longer time (e.g., decoding time, processing time) for the receiving device to decode the information. On the other hand, because uplink physical channel resources (e.g., PUCCH, PUSCH) must be (preliminarily) configured / allocated to the corresponding terminal in order to transmit layer-1 uplink control information, from the base station / network's perspective, the more terminals / UEs there are, the more uplink (UL) resources must be allocated to each terminal / UE, which may increase the burden on the overall UL resource overhead. Therefore, in wireless communication systems, information that must be transmitted relatively urgently for the operation of the physical layer, such as SR (e.g., for PUSCH allocation), HARQ-ACK (e.g., for retransmission), CSI (e.g., for scheduling / MCS / precoder decision), and beam information (e.g., for (analog) beam decision) are transmitted as physical layer uplink control information (UCI). Except for SR, the base station / network determines / controls the timing of information reporting by the terminal. This network (NW)-initiated / triggered report has the limitation that the terminal must be configured / instructed to send UCI frequently in environments where the wireless channel is likely to change rapidly / highly.That is, in such an environment, the UL resource overhead for UCI reporting and the related downlink (DL) measurement reference signal (RS) overhead increase, and the power consumption of the terminal also increases due to frequent uplink transmission of the terminal. In addition, the more terminals there are within the cell / TRP coverage, the more UL resources must be allocated to each terminal, which increases the UL resource overhead. To overcome the limitations of such NW-initiated / triggered reports, a method that has recently emerged is the UE-initiated / triggered report method or event-based / triggered report method. The UE-initiated / triggered (UCI) report method or event-based / triggered report method lets the terminal decide whether / when to report. That is, there is a potential benefit in performing rapid reporting to the network because the information is reported on a layer-1 / lower layer basis, while reducing UL resource overhead and terminal power consumption by performing the (UCI) reporting only when necessary (e.g., only when a specific event occurs). For the above reasons, standardization of UE-initiated / triggered beam reports is scheduled to proceed in NR Rel-19.

[0203] A portion of the work item description (WID) for Rel-19 NR MIMO is as follows:

[0204] Leverages legacy CSI measurement and reporting configuration frameworks (where possible) assuming unified TCI, targets FR2 and single TRP (sTRP) with intra-cell and inter-cell beam management, and specifies enhancements to facilitate UE-initiated / event-driven beam management to reduce overhead and / or latency.

[0205] - UL signaling content(s) (and procedure(s) if required) for UE-initiated / event-driven beam reporting to facilitate fast beam switching.

[0206] - UL signal medium / container considering the UE-initiated / event-driven nature of UL transmission, designed primarily for beam reporting purposes.

[0207] Current NR standards support beam reporting, a form of CSI feedback in which a UE reports L1-RSRP or L1-SINR values ​​to a base station based on the measured power of SSB or CSI-RS. Here, the base station pre-configures and informs the UE of UL resources and settings for beam reporting, and the UE reports beams to the base station based on those settings.

[0208] As described above, in Rel-19, a method is being considered in which a specific event for beam reporting is defined differently from the existing one, and a method is being considered in which the UE determines whether an event has occurred and performs beam reporting only when an event has occurred. This may be referred to as UE initiated beam reporting or event-driven beam reporting. Hereinafter, in the description of the present disclosure, for the convenience of explanation, it is mainly referred to as UE initiated beam reporting, but the proposed method of the present disclosure is not limited to this name and may be referred to by other names.

[0209] In the following description of the present disclosure, beam reporting may be interpreted as a concept included in CSI reporting (or one type of CSI reporting), and thus beam reporting settings may be configured for a UE by upper layer signaling for CSI reporting configuration. In addition, beam reporting may include L1-RSRP reporting and / or L1-SINR reporting. Beam reporting quantity may mean information reported to a base station through beam reporting, and may include, for example, i) ID / index(s) of downlink reference signals (e.g., CRI, SSB index) and ii) L1-RSRP or L1-SINR corresponding thereto.

[0210] Furthermore, although the proposed method in the description of the present disclosure below primarily describes beam reporting, the proposed method can equally be applied to other CSI reporting (e.g., reporting of CRI, RI, PMI, CQI, etc.). In other words, if UE-initiated CSI reporting is supported in addition to UE-initiated beam reporting, the proposed method described below can equally be applied.

[0211] Additionally, in the description of the present disclosure below, an identifier (ID) may be interpreted as having the same meaning as an index.

[0212] Additionally, in the description of the present disclosure below, CMR / IMR / CSI-RS resources mean at least one of CMR, IMR, and CSI-RS resources set for UE initiated beam reporting.

[0213] Additionally, in the description of the present disclosure below, ' / ' means 'and', 'or', or 'and / or' depending on the context.

[0214] In addition, in the description of the present disclosure below, 'beam' may mean a source reference signal (RS) for a 'spatial filter' or a 'spatial relation', and may be interpreted equivalently to a QCL (type-D) RS or a (DL / UL / joint) TCI state or a spatial relation RS (in the case of uplink).

[0215] In this disclosure, a method for counting the number of active resources / ports of channel measurement resources (CMR) / interference measurement resources (IMR) set for a UE-initiated beam report and a method for calculating active start / end points are proposed.

[0216] Before describing the proposed method of the present disclosure, referring to Table 8, the current standard calculates the active CSI-RS resources, the number of active ports, and the active start / end time as follows. Here, the active CSI-RS resources refer to the CSI-RS resources being measured by the UE, and the more active CSI-RS resources there are, the higher the implementation complexity of the UE. In addition, the implementation complexity of the UE increases not only as the number of CSI-RS resources but also as the number of ports of the active CSI-RS resources. Considering this implementation complexity, the UE reports to the base station the maximum number of active CSI-RS resources / ports that can be supported by its capability.

[0217] In any slot, a UE is not expected to have more active CSI-RS ports or active CSI-RS resources in active BWPs than its reported capabilities. An NZP CSI-RS resource is activated for a time period defined as follows: For aperiodic CSI-RS, it starts from the end of the PDCCH containing the request and ends at the end of the scheduled PUSCH containing the report associated with this aperiodic CSI-RS. If the PDCCH candidates are associated with a search space set configured with the searchSpaceLinkingId, the PDCCH candidate that ends later in time among the two linked PDCCH candidates is used to determine the NZP CSI-RS resource active duration. For semi-persistent CSI-RS, it starts from the end of the application of the activation command and ends at the end of the application of the deactivation command. For periodic CSI-RS, it starts when the periodic CSI-RS is configured via higher layer signaling and ends when the periodic CSI-RS configuration is released. If a CSI-RS resource is referenced N times by one or more CSI reporting configurations, the CSI-RS resource and the CSI-RS port within the CSI-RS resource are counted N times. For a set of CSI-RS resources for channel measurement configured with two resource groups and N resource pairs, if a CSI-RS resource is referenced X times by one of M CSI-RS resources (where M is defined in Section 5.2.1.4.2) and / or one or two resource pairs, the CSI-RS resource and the CSI-RS port within the CSI-RS resource are counted X times.For a CSI reporting configuration including sub-configuration(s) indicated in a CSI reporting configuration (CSI-ReportConfig), if a CSI-RS resource is referenced by M sub-configurations out of X sub-configurations, the CSI-RS resource is counted M times, and a CSI-RS port within the CSI-RS resource is counted as follows: - If each sub-configuration out of the M sub-configurations is set to a CSI-RS antenna port subset provided in a [port-subsetIndicator], - If each sub-configuration among M sub-configurations is set to one or more CSI-RS resource lists provided by [NZP CSI-RS resource list (nzp-CSI-RS-resourceList)] and / or is set to a power offset provided by [powerOffset], M×P, where P is the number of ports configured by the number of ports (nrofPorts) and P s is the number of CSI-RS ports of the sub-configuration s derived from the corresponding antenna port subset indicator [port-subsetIndicator] according to section 5.2.1.4.2. For periodic or semi-persistent CSI-RS resources within the set of CSI-RS resources for channel measurements associated with a CSI reporting configuration (CSI-ReportConfig) configured with the upper layer parameter codebook type (codebookType) set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', the CSI-RS resources and the CSI-RS ports within the CSI-RS resources are K P The number is counted. Here, K P The value of ∈{1,2,4} is dictated by the UE capability.

[0218] Example 1: UE initiated beam reporting may be activated (active) only when an event occurs and may not be activated otherwise.

[0219] For example, a UE initiated beam report may be reported in two stages (e.g., reported in a time division multiplexing (TDM) manner): reporting whether an event has occurred (stage 1) (e.g., an uplink transmission notifying that an event has occurred) and reporting beam quantity (e.g., CRI / SSB index and / or L1-RSRP / L1-SINR) when an event has occurred (stage 2).

[0220] For example, when an event occurs, the UE may request scheduling for beam reporting to the base station (e.g., via SR / RACH (random access channel)), the base station may schedule an UL channel for beam quantity reporting with DCI, and the UE may perform beam reporting on the scheduled UL channel. As another example, when an event occurs, the UE may report to the base station (e.g., via SR / RACH / PUCCH / PUSCH) whether an event has occurred (or indicate that an event has occurred), and if the event has occurred, the UE may perform beam reporting on a UL channel (e.g., a configured grant PUSCH, etc.) thereafter (either pre-configured or determined by the UE).

[0221] FIG. 13 illustrates a UE initiated beam reporting procedure according to one embodiment of the present disclosure.

[0222] Figure 13 illustrates the two-step reporting method described above. In Figure 13, circles and squares represent CMRs and potential UL channels, respectively. For convenience of explanation, it is assumed that one periodic (P) CSI-RS is configured in the CMR.

[0223] In the second stage, the start time of the CMR / IMR / CSI-RS active can be defined / set / promised as from the (earliest, or N-th earliest) CMR / IMR / CSI-RS occasion for beam quantity report after the report for the first stage is completed, and the end time of the CMR / IMR / CSI-RS active can be defined / set / promised as from the (latest, or N-th latest) CMR / IMR / CSI-RS occasion for beam quantity report before the report for the second stage is completed. In other words, the active time interval of CMR / IMR / CSI-RS for the second phase can be defined / set / promised to start at the beginning of the (earliest, or Nth-earliest) CMR / IMR / CSI-RS occasion for beam quantity report after the reporting for the first phase is completed and end at the end of the (most recent, or Nth-most recent) CMR / IMR / CSI-RS occasion for beam quantity report before the reporting for the second phase is completed. Here, (the value of N or the maximum value of N or the minimum value of N) can be reported by the UE to the base station as a capability or can be set by the base station or can be determined as a fixed value.

[0224] If no event occurs, the beam quantity report itself is not performed, and therefore CMR / IMR / CSI-RS measurements for beam quantity report calculation do not need to be performed. Therefore, if no event occurs, the CMR / IMR / CSI-RS resources / ports in the beam quantity report (i.e., step 2) are not counted as active resources / ports.

[0225] In the first stage, for the CMR / IMR / CSI-RS resources referenced to determine whether an event has occurred, the start time of the resource / port can be defined / set / promised as from the (earliest, or Nth-earliest) CMR / IMR / CSI-RS occasion after which the report for the previous last second stage is completed, and the end time can be defined / set / promised as until the (most recent, or Nth-most recent) CMR / IMR / CSI-RS occasion before which the report for the first stage is completed. In other words, the active time interval of the CMR / IMR / CSI-RS for the first stage can be defined / set / promised as starting from the start of the (earliest, or Nth-earliest) CMR / IMR / CSI-RS occasion after which the report for the previous last second stage is completed, and ending at the end of the (most recent, or Nth-most recent) CMR / IMR / CSI-RS occasion before which the report for the first stage is completed.

[0226] Alternatively, for the CMR / IMR / CSI-RS resources referenced in the second step to determine whether an event has occurred, the active resource / port may follow the legacy method for determining the active start / end time (see Table 8). For example, the active time interval for an aperiodic CSI-RS may start from the end of the PDCCH containing the request and end at the end of the uplink transmission containing the report associated with this aperiodic CSI-RS (i.e., the report on the event occurrence). In addition, the active time interval for a semi-persistent CSI-RS may start from the end of the application of an activation command and end at the end of the application of a deactivation command. The active time interval for a periodic CSI-RS may start when the periodic CSI-RS is configured via a higher layer signal and end when the periodic CSI-RS configuration is released.

[0227] Example 2: For the CMR / IMR / CSI-RS resources referenced in the first step to determine whether an event has occurred, the active start time of the resource / port can be defined / set / promised as from the (earliest, or N-th earliest) CMR / IMR / CSI-RS occasion set after the report for the previous last second step is completed, and the end time can be defined / set / promised as until the (latest, or N-th latest) CMR / IMR / CSI-RS occasion set before the report for the first step is completed. In other words, the active time interval of the CMR / IMR / CSI-RS resources for the first step can be defined / set / promised as starting from the start of the (earliest, or N-th earliest) CMR / IMR / CSI-RS occasion after the report for the previous last second step is completed, and ending at the end of the (most recent, or N-th most recent) CMR / IMR / CSI-RS occasion before the report for the first step is completed.

[0228] Regardless of whether an event occurs or not, the CMR / IMR / CSI-RS resources / ports for beam quantity report (i.e., step 2) may not be active.

[0229] This is proposed considering the following UE implementation method. Since the UE performs event detection and completes beam quantity calculation in the first step, it can report the quantity value calculated in the first step to the base station as is in the second step. Accordingly, the CMR / IMR / CSI-RS resources / ports in the beam quantity report (i.e., the second step) may not be counted as active resources / ports.

[0230] Example 3: The current standard content exemplified in Table 8 ('typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18') is introduced because it utilizes not only the latest occasion of periodic (P) CSI-RS but also the Kp-th, Kp-1-th, ..., 1st latest occasion (i.e., using Kp opportunities of each CMR resource) for PMI prediction. In UE initiated beam reporting, multiple occasions from the x-th latest occasion to the first latest occasion can also be used for event monitoring and beam quantity calculation. For this purpose, the active CSI-RS resource for UE initiated beam reporting and the active CSI-RS port(s) within the corresponding CSI-RS resource can be counted x times.

[0231] If only the latest occasion is used for event monitoring and beam quantity calculation, the event determination and reporting quantity may be unstable because the event determination and reporting quantity are calculated based on only one occasion for each CMR / IMR / CSI-RS resource. For example, suppose that the RSRP of the CMR measured at the most recent occasion exceeds the threshold (i.e., the event condition is met), and a UE-initiated beam report is performed. In this case, if the event condition is met at the most recent occasion but has not been met for a continuous period prior to the most recent occasion, the UE-initiated beam reported value cannot be considered stable. This is simply because the event may have been met once exceptionally at the most recent occasion. Therefore, it is desirable to calculate the event determination and reporting quantity based on multiple occasions over a longer period. To this end, multiple occasions, from the x-th most recent occasion to the first most recent occasion, can be used for event determination and reporting quantity calculation.

[0232] Additionally, in the case of UE initiated beam reporting, the CMR / IMR / CSI-RS for determining whether an event condition is satisfied and the CMR / IMR / CSI-RS that becomes the beam report target when the event condition is satisfied (i.e., the CMR / IMR / CSI-RS used for calculating the beam quantity to be reported) may be the same or different.

[0233] - Examples of cases where the CMR / IMR / CSI-RS for determining whether an event condition is satisfied and the CMR / IMR / CSI-RS that becomes the beam reporting target when the event condition is satisfied are different are as follows.

[0234] For example, as a CMR / IMR / CSI-RS to determine whether an event condition is satisfied, the UE can monitor whether the RSRP of the DL beam currently in use (e.g., the beam(s) / TCI state(s) currently being applied when applying a unified beam / TCI indication) falls below a certain value, and if it falls below the certain value, the UE can calculate the L1-RSRP in the CMR configured with the certain beam set and report it to the base station.

[0235] Additionally, the number of active resources / ports of CMR / IMR / CSI-RS for determining whether an event condition is satisfied and the number of active resources / ports of CMR / IMR / CSI-RS for which beam reporting is performed can be counted separately.

[0236] - Examples of cases where the CMR / IMR / CSI-RS for determining whether an event condition is satisfied and the CMR / IMR / CSI-RS that becomes the beam reporting target when the event condition is satisfied are the same are as follows.

[0237] For example, the UE can monitor whether the RSRP of a CMR configured with a specific beam set is greater than or equal to a specific value, and if so, calculate the L1-RSRP in the CMR configured with the specific beam set and report it to the base station.

[0238] In this case, since the CMR / IMR / CSI-RS for event monitoring and beam quantity calculation are the same, the number of active ports / resources may be counted twice. Alternatively, if only some CMR / IMR / CSI-RS are the same, the number of active ports / resources of those CMR / IMR / CSI-RS may be counted twice.

[0239] Alternatively, the UE may have performed event detection and completed beam quantity calculation in step 1. In this case, the quantity value calculated in step 1 may be reported to the base station as is in step 2. Therefore, the number of active ports / resources of CMR / IMR / CSI-RS in the beam quantity report (i.e., step 2) may not be counted additionally. Consequently, the number of active ports / resources of CMR / IMR / CSI-RS for event monitoring and beam quantity calculation may be counted as 1 instead of 2.

[0240] Example 4: Contrary to the above-described Example 1, the base station ( / UE) can determine that the CMR / IMR / CSI-RS resource / port of the beam quantity report (i.e., the second step) is active only when no event occurs (i.e., event condition is not satisfied).

[0241] The active time point of CMR / IMR / CSI-RS for the second phase can be defined / set / committed to be from the (earliest, or Nth-earliest) CMR / IMR / CSI-RS occasion for beam quantity reporting after the reporting for the first phase is completed, and the end time point can be defined / set / committed to be until the (most recent, or Nth-most recent) CMR / IMR / CSI-RS occasion for beam quantity reporting before the reporting for the second phase is completed. In other words, the active time period of CMR / IMR / CSI-RS for the second phase can be defined / set / committed to be from the beginning of the (earliest, or Nth-earliest) CMR / IMR / CSI-RS occasion for beam quantity reporting after the reporting for the first phase is completed, and the end of the (most recent, or Nth-most recent) CMR / IMR / CSI-RS occasion for beam quantity reporting before the reporting for the second phase is completed. Here, (N value or maximum value of N or minimum value of N) can be reported by the UE to the base station as a capability or can be set by the base station or can be determined as a fixed value.

[0242] If no event has occurred (i.e., no event has been reported in step 1), the UE may perform measurements for the CMR / IMR / CSI-RS occasions set from the time of the event report (i.e., the report that no event has occurred) to the time of the beam quantity report, and may then re-determine (evaluate) whether the event has occurred. Accordingly, the CMR / IMR / CSI-RS resources / ports for beam quantity reporting (step 2) may be determined to be active only when no event has occurred.

[0243] Conversely, if an event occurs, the UE can report the quantity value calculated in the first step to the base station in the second step, taking into account the implementation method described in the above-described embodiment 2. Therefore, the CMR / IMR / CSI-RS resources / ports in the beam quantity report (i.e., the 2nd step) may not be counted as active resources / ports.

[0244] Here, if a collision with another UL channel or another CSI / beam report occurs in the second step and the beam quantity report is dropped, the CMR / IMR / CSI-RS resource / port may not be counted as an active resource / port until the beam quantity is actually reported on the potential UL channel for the next beam quantity report. In addition, since no further determination is made as to whether an event occurred in the next first step until the beam quantity is actually reported on the potential UL channel for the next beam quantity report, it can be assumed that the CMR / IMR / CSI-RS resource / port for both the first and second steps is not active until the beam quantity is actually reported on the potential UL channel for the next beam quantity report.

[0245] In the first stage, for the CMR / IMR / CSI-RS resources referenced to determine whether an event has occurred, the active start time of the resource / port can be defined / set / promised as from the (earliest, or Nth-most) CMR / IMR / CSI-RS occasion after which the report for the previous last second stage is completed, and the end time can be defined / set / promised as until the (most recent, or Nth-most recent) CMR / IMR / CSI-RS occasion before which the report for the first stage is completed. In other words, the active time interval of the CMR / IMR / CSI-RS for the first stage can be defined / set / promised as starting from the start of the (earliest, or Nth-most) CMR / IMR / CSI-RS occasion after which the report for the previous last second stage is completed, and ending at the end of the (most recent, or Nth-most) CMR / IMR / CSI-RS occasion before which the report for the first stage is completed.

[0246] Alternatively, for the CMR / IMR / CSI-RS resources referenced in the first step to determine whether an event has occurred, the active resource / port may follow the legacy method for determining the active start / end time (see Table 8). For example, the active time interval for an aperiodic CSI-RS may start from the end of the PDCCH containing the request and end at the end of the uplink transmission containing the report associated with this aperiodic CSI-RS (i.e., the report on the event occurrence). In addition, the active time interval for a semi-persistent CSI-RS may start from the end of the application of an activation command and end at the end of the application of a deactivation command. The active time interval for a periodic CSI-RS may start when the periodic CSI-RS is configured via a higher layer signal and end when the periodic CSI-RS configuration is released.

[0247] In the description of the present disclosure described above, the first step may correspond to an uplink transmission in which the UE requests the base station to schedule an UL channel for a specific CSI report (or beam report) when an event occurs (or an event condition is met) for the CSI report, or may correspond to an uplink transmission in which the UE notifies the base station that an event for the CSI report (or beam report) has occurred (or an event condition is met).

[0248] FIG. 14 is a diagram illustrating a signaling procedure between a base station and a UE for a UE initiation beam reporting method according to one embodiment of the present disclosure.

[0249] FIG. 14 illustrates a signaling procedure between a UE and a base station based on the proposed methods in Embodiments 1 to 4 described above. The example in FIG. 14 is provided for convenience of explanation and does not limit the scope of the present disclosure. Some step(s) illustrated in FIG. 14 may be omitted depending on the situation and / or setting. In addition, the base station and the UE in FIG. 14 are only examples and may be implemented as the devices illustrated in FIG. 17 below. For example, the processor (102 / 202) in FIG. 17 may control the transceiver (106 / 206) to transmit and receive channels / signals / data / information, etc., and may also control the processor (102 / 202) in FIG. 17 to store transmitted or received channels / signals / data / information, etc., in the memory (104 / 204).

[0250] Referring to Figure 14, the base station transmits configuration information to the UE (S1401).

[0251] Here, the configuration information may mean configuration information related to UE-initiated beam reporting or event-driven beam reporting.

[0252] Here, the beam (or beam RS or RS) may mean a beamformed RS (e.g., SSB, CSI-RS, etc.). In addition, the beam (or beam RS or RS) may have different directionality depending on the resource to which it is transmitted, and different resource(s) to which the beamformed RS is transmitted may mean different beams (or beam RS or RS).

[0253] Additionally, the configuration information may mean configuration information for one or more parameter(s) related to the Tx beam (or beam RS or RS) of the base station and / or the Rx beam (or beam RS or RS) of the UE. For example, the configuration information may be configuration information related to beam (or CSI) reporting (e.g., configuration information related to reporting of CSI (including L1-RSRP and / or L1-SINR) (e.g., CSI-ReportConfig)), configuration information related to resources for beam (or CSI) reporting (e.g., CSI-ResourceConfig)), or configuration information related to beam configuration for a specific channel / signal, BWP, serving cell, etc. (e.g., configuration information including (DL / UL or unified) TCI state(s)).

[0254] Additionally, the configuration information may include information about events (or criteria) used to determine whether the UE will perform initiated / event-driven beam reporting. These events (or criteria) may be configured individually for each CSI report, or multiple events (or criteria) may be configured within a single CSI report.

[0255] Although not shown in FIG. 14, the base station may transmit control information to the UE.

[0256] Here, the control information may mean information for activating and / or indicating a beam (or beam RS or RS) (i.e., QCL type-D RS (or TCI state)). Or, it may mean control information for activating / triggering a beam report (e.g., L1-RSRP / SINR) to assist in selecting a Tx beam (or beam RS or RS) of a base station and / or an Rx beam (or beam RS or RS) of a UE. Such control information may be transmitted via MAC CE, DCI, or both MAC CE and DCI.

[0257] The base station transmits a downlink reference signal (i.e., beam) (e.g., SSB, CSI-RS, etc.) to the UE from one or more resources (S1402).

[0258] As described above, a beam (or beam RS or RS) may mean a beamformed reference signal (e.g., SSB, CSI-RS, etc.) as described above. In addition, a beam (or beam RS or RS) may have different directionality depending on the resource to which it is transmitted, and different resource(s) to which the beamformed RS is transmitted may mean different beams (or beam RS or RS).

[0259] That is, the base station can transmit downlink RS to the UE through different beams on one or more resources.

[0260] The UE performs a UE-initiated / event-driven beam report to the base station (S1403).

[0261] Here, when an event set by the configuration information is satisfied, UE-initiated / event-driven beam reporting can be performed.

[0262] Here, the UE can transmit a first uplink transmission related to occurrence / satisfaction of a relevant event related to an initiated / event-driven beam report to the base station, and thereafter, the UE can transmit a second uplink transmission including a report value derived based on a downlink reference signal to the base station. Here, the report value can be i) a pair of an identifier of a reference signal resource (e.g., CRI, SSBRI) and L1-RSRP, or ii) a pair of an identifier of a reference signal resource and L1-SNIR.

[0263] Here, the first uplink transmission may be an uplink transmission notifying that the event has occurred.

[0264] Alternatively, the first uplink transmission may be an uplink transmission notifying that the event did not occur.

[0265] Although not illustrated in Figure 14, the UE may transmit information about its capabilities to the base station. In this case, resources for the downlink RS may not be activated more than those reported as capabilities within any slot. Alternatively, the UE may expect that resources for the downlink RS will not be activated more than those reported as capabilities within any slot. In other words, resources for the downlink RS need to be activated within the UE's capabilities, and for this purpose, the number of activated resources for the downlink RS needs to be accurately counted.

[0266] Here, the occurrence of the event may be determined and / or the report value may be derived using one or more active resources among the one or more resources for the downlink RS. Here, the occurrence of the event may be determined and / or the report value may be derived using the same one or more active resources, or the occurrence of the event may be determined and / or the report value may be derived using one or more different active resources.

[0267] For example, according to the above-described embodiment 3, the one or more activated resources may be counted X times (X is an integer greater than 0). For example, if the occurrence of the event is determined and / or the report value is derived using the same one or more activated resources, the one or more activated resources may be counted X times (X is an integer greater than 0). Alternatively, if the occurrence of the event is determined and / or the report value is derived using different one or more activated resources, the one or more active resources for each or either of them may be counted X times (X is an integer greater than 0).

[0268] Additionally, based on the fact that one or more first activated resources used to determine the occurrence of the event and one or more second activated resources used to derive the reporting value are different, the one or more first activated resources and the one or more second resources may be counted individually.

[0269] Additionally, based on the one or more activated resources being equally utilized to determine the occurrence of the event and derive the reporting value, the one or more activated resources may be counted twice.

[0270] Additionally, based on the fact that the one or more activated resources are equally utilized to determine the occurrence of the event and derive the report value, the report value is calculated when determining the occurrence of the event, and the one or more activated resources may be counted as 1.

[0271] For example, according to the above-described embodiment 1, based on the occurrence of the event, it can be determined that one or more resources set for the downlink RS are activated for deriving the report value after the completion of the first uplink transmission and before the second uplink transmission.

[0272] Additionally, it may be determined that one or more resources set for the downlink RS before the first uplink transmission have been activated for deriving the report value since the last report value transmission before the first uplink transmission.

[0273] For example, according to the above-described embodiment 2, regardless of whether the event occurs or not, the resource for the downlink RS is not separately activated to derive the report value, and the report value can be calculated when determining the occurrence of the event and reported through the second uplink transmission.

[0274] For example, according to the above-described embodiment 4, based on the fact that the event has not occurred, it may be determined that one or more resources set for the downlink RS are activated to determine the occurrence of the event after the completion of the first uplink transmission and before the second uplink transmission.

[0275] Additionally, based on the occurrence of the event, resources for the downlink RS are not separately activated to derive the report value, and the report value can be calculated when determining the occurrence of the event and reported through the second uplink transmission.

[0276] FIG. 15 is a diagram illustrating the operation of a UE for reporting channel state information according to one embodiment of the present disclosure.

[0277] FIG. 15 illustrates the operation of a UE based on the proposed methods in Embodiments 1 to 4 described above. The example in FIG. 15 is provided for convenience of explanation and does not limit the scope of the present disclosure. Some of the step(s) illustrated in FIG. 15 may be omitted depending on the situation and / or setting. In addition, the UE in FIG. 15 is only an example and may be implemented as a device illustrated in FIG. 17 below. For example, the processor (102 / 202) in FIG. 17 may control the transceiver (106 / 206) to transmit and receive channels / signals / data / information, etc., and may also control the processor (102 / 202) in FIG. 17 to store the channels / signals / data / information to be transmitted or received in the memory (104 / 204).

[0278] Additionally, the operation of FIG. 15 may be processed by one or more processors (102, 202) of FIG. 17. Additionally, the operation of FIG. 15 may be stored in a memory (e.g., one or more memories (104, 204) of FIG. 17) in the form of a command / program (e.g., an instruction, an executable code) for driving at least one processor (e.g., 102, 202) of FIG. 17.

[0279] Referring to FIG. 15, the UE receives configuration information related to CSI reporting from the base station (S1501).

[0280] Here, the CSI report may include a beam report (e.g., L1-RSRP and / or L1-SINR), and the configuration information related to the CSI report (e.g., CSI-ReportConfig) may correspond to one example of the configuration information in FIG. 14 above.

[0281] Additionally, configuration information related to CSI reporting may include information about events (or criteria) used to determine whether a UE performs initiated / event-driven beam reporting. These events (or criteria) may be configured individually for each CSI report, or multiple events (or criteria) may be configured within a single CSI report.

[0282] The UE receives a downlink reference signal (i.e., beam) (e.g., SSB, CSI-RS, etc.) from one or more resources from the base station (S1502).

[0283] As described above, a beam (or beam RS or RS) may mean a beamformed RS (e.g., SSB, CSI-RS, SRS, etc.) as described above. In addition, a beam (or beam RS or RS) may have different directionality depending on the resource to which it is transmitted, and different resource(s) to which the beamformed RS is transmitted may mean different beams (or beam RS or RS).

[0284] That is, downlink RSs can be transmitted through different beams from one or more of the above resources.

[0285] For example, the downlink RS may correspond to either a synchronization signal block (SSB) or a CSI-RS.

[0286] The UE transmits a first uplink transmission to the base station regarding the occurrence of an event related to the CSI report (S1503).

[0287] In other words, UE-initiated / event-driven beam reporting can be performed when an event set by configuration information related to CSI reporting is satisfied.

[0288] Here, the first uplink transmission may be an uplink transmission notifying that the event has been satisfied. For example, the first uplink transmission may be transmitted via the PUCCH. As another example, the notification that the event has been satisfied may apply a transmission method for a scheduling request (SR).

[0289] Alternatively, the first uplink transmission may be an uplink transmission notifying that the event did not occur.

[0290] The UE transmits a second uplink transmission (i.e., beam report or CSI report) to the base station including a report value derived (calculated) based on the downlink RS (S1504).

[0291] Here, the reporting value can be i) a pair of an identifier of a reference signal resource (e.g., CRI, SSBRI) and L1-RSRP, or ii) a pair of an identifier of a reference signal resource and L1-SNIR.

[0292] Although not illustrated in Figure 15, the UE may transmit information about its capabilities to the base station. In this case, resources for the downlink RS may not be activated more than those reported as capabilities within any slot. Alternatively, the UE may expect that resources for the downlink RS will not be activated more than those reported as capabilities within any slot. In other words, resources for the downlink RS need to be activated within the UE's capabilities, and for this purpose, the number of activated resources for the downlink RS needs to be accurately counted.

[0293] Here, the occurrence of the event may be determined and / or the report value may be derived using one or more active resources among the one or more resources for the downlink RS. Here, the occurrence of the event may be determined and / or the report value may be derived using the same one or more active resources, or the occurrence of the event may be determined and / or the report value may be derived using one or more different active resources.

[0294] For example, according to the above-described embodiment 3, the one or more activated resources may be counted X times (X is an integer greater than 0). For example, if the occurrence of the event is determined and / or the report value is derived using the same one or more activated resources, the one or more activated resources may be counted X times (X is an integer greater than 0). Alternatively, if the occurrence of the event is determined and / or the report value is derived using different one or more activated resources, the one or more active resources for each or either of them may be counted X times (X is an integer greater than 0).

[0295] Additionally, based on the fact that one or more first activated resources used to determine the occurrence of the event and one or more second activated resources used to derive the reporting value are different, the one or more first activated resources and the one or more second resources may be counted individually.

[0296] Additionally, based on the one or more activated resources being equally utilized to determine the occurrence of the event and derive the reporting value, the one or more activated resources may be counted twice.

[0297] Additionally, based on the fact that the one or more activated resources are equally utilized to determine the occurrence of the event and derive the report value, the report value is calculated when determining the occurrence of the event, and the one or more activated resources may be counted as 1.

[0298] For example, according to the above-described embodiment 1, based on the occurrence of the event, it can be determined that one or more resources set for the downlink RS are activated for deriving the report value after the completion of the first uplink transmission and before the second uplink transmission.

[0299] Additionally, it may be determined that one or more resources set for the downlink RS before the first uplink transmission have been activated for deriving the report value since the last report value transmission before the first uplink transmission.

[0300] For example, according to the above-described embodiment 2, regardless of whether the event occurs or not, the resource for the downlink RS is not separately activated to derive the report value, and the report value can be calculated when determining the occurrence of the event and reported through the second uplink transmission.

[0301] For example, according to the above-described embodiment 4, based on the fact that the event has not occurred, it may be determined that one or more resources set for the downlink RS are activated to determine the occurrence of the event after the completion of the first uplink transmission and before the second uplink transmission.

[0302] Additionally, based on the occurrence of the event, resources for the downlink RS are not separately activated to derive the report value, and the report value can be calculated when determining the occurrence of the event and reported through the second uplink transmission.

[0303] FIG. 16 is a diagram illustrating the operation of a base station for reporting channel state information according to one embodiment of the present disclosure.

[0304] FIG. 16 illustrates the operation of a base station based on the proposed methods in Embodiments 1 to 4 described above. The example in FIG. 16 is provided for convenience of explanation and does not limit the scope of the present disclosure. Some of the step(s) illustrated in FIG. 16 may be omitted depending on the situation and / or setting. In addition, the base station in FIG. 16 is only an example and may be implemented with the device illustrated in FIG. 17 below. For example, the processor (102 / 202) in FIG. 17 may control the transceiver (106 / 206) to transmit and receive channels / signals / data / information, etc., and may also control the processor (102 / 202) in FIG. 17 to store the channels / signals / data / information to be transmitted or received in the memory (104 / 204).

[0305] Additionally, the operation of FIG. 16 may be processed by one or more processors (102, 202) of FIG. 17. Additionally, the operation of FIG. 16 may be stored in a memory (e.g., one or more memories (104, 204) of FIG. 17) in the form of a command / program (e.g., an instruction, an executable code) for driving at least one processor (e.g., 102, 202) of FIG. 17.

[0306] Referring to FIG. 16, the base station transmits configuration information related to CSI reporting to the UE (S1601).

[0307] Here, the CSI report may include a beam report (e.g., L1-RSRP and / or L1-SINR), and the configuration information related to the CSI report (e.g., CSI-ReportConfig) may correspond to one example of the configuration information in FIG. 14 above.

[0308] Additionally, configuration information related to CSI reporting may include information about events (or criteria) used to determine whether a UE performs initiated / event-driven beam reporting. These events (or criteria) may be configured individually for each CSI report, or multiple events (or criteria) may be configured within a single CSI report.

[0309] The base station transmits a downlink reference signal (i.e., beam) (e.g., SSB, CSI-RS, etc.) to the UE from one or more resources (S1602).

[0310] As described above, a beam (or beam RS or RS) may mean a beamformed RS (e.g., SSB, CSI-RS, SRS, etc.) as described above. In addition, a beam (or beam RS or RS) may have different directionality depending on the resource to which it is transmitted, and different resource(s) to which the beamformed RS is transmitted may mean different beams (or beam RS or RS).

[0311] That is, downlink RSs can be transmitted through different beams from one or more of the above resources.

[0312] For example, the downlink RS may correspond to either a synchronization signal block (SSB) or a CSI-RS.

[0313] The base station receives a first uplink transmission related to whether an event related to the CSI report has occurred from the UE (S1603).

[0314] In other words, UE-initiated / event-driven beam reporting can be performed when an event set by configuration information related to CSI reporting is satisfied.

[0315] Here, the first uplink transmission may be an uplink transmission notifying that the event has been satisfied. For example, the first uplink transmission may be transmitted via the PUCCH. As another example, the notification that the event has been satisfied may apply a transmission method for a scheduling request (SR).

[0316] Alternatively, the first uplink transmission may be an uplink transmission notifying that the event did not occur.

[0317] The base station receives a second uplink transmission (i.e., beam report or CSI report) including a report value derived (calculated) based on the downlink RS from the UE (S1604).

[0318] Here, the reporting value can be i) a pair of an identifier of a reference signal resource (e.g., CRI, SSBRI) and L1-RSRP, or ii) a pair of an identifier of a reference signal resource and L1-SNIR.

[0319] Although not illustrated in Figure 16, the UE may transmit information about its capabilities to the base station. In this case, resources for the downlink RS may not be activated more than those reported as capabilities within any slot. Alternatively, the UE may expect that resources for the downlink RS will not be activated more than those reported as capabilities within any slot. In other words, resources for the downlink RS need to be activated within the UE's capabilities, and for this purpose, the number of activated resources for the downlink RS needs to be accurately counted.

[0320] Here, the occurrence of the event may be determined and / or the report value may be derived using one or more active resources among the one or more resources for the downlink RS. Here, the occurrence of the event may be determined and / or the report value may be derived using the same one or more active resources, or the occurrence of the event may be determined and / or the report value may be derived using one or more different active resources.

[0321] For example, according to the above-described embodiment 3, the one or more activated resources may be counted X times (X is an integer greater than 0). For example, if the occurrence of the event is determined and / or the report value is derived using the same one or more activated resources, the one or more activated resources may be counted X times (X is an integer greater than 0). Alternatively, if the occurrence of the event is determined and / or the report value is derived using different one or more activated resources, the one or more active resources for each or either of them may be counted X times (X is an integer greater than 0).

[0322] Additionally, based on the fact that one or more first activated resources used to determine the occurrence of the event and one or more second activated resources used to derive the reporting value are different, the one or more first activated resources and the one or more second resources may be counted individually.

[0323] Additionally, based on the one or more activated resources being equally utilized to determine the occurrence of the event and derive the reporting value, the one or more activated resources may be counted twice.

[0324] Additionally, based on the fact that the one or more activated resources are equally utilized to determine the occurrence of the event and derive the report value, the report value is calculated when determining the occurrence of the event, and the one or more activated resources may be counted as 1.

[0325] For example, according to the above-described embodiment 1, based on the occurrence of the event, it can be determined that one or more resources set for the downlink RS are activated for deriving the report value after the completion of the first uplink transmission and before the second uplink transmission.

[0326] Additionally, it may be determined that one or more resources set for the downlink RS before the first uplink transmission have been activated for deriving the report value since the last report value transmission before the first uplink transmission.

[0327] For example, according to the above-described embodiment 2, regardless of whether the event occurs or not, the resource for the downlink RS is not separately activated to derive the report value, and the report value can be calculated when determining the occurrence of the event and reported through the second uplink transmission.

[0328] For example, according to the above-described embodiment 4, based on the fact that the event has not occurred, it may be determined that one or more resources set for the downlink RS are activated to determine the occurrence of the event after the completion of the first uplink transmission and before the second uplink transmission.

[0329] Additionally, based on the occurrence of the event, resources for the downlink RS are not separately activated to derive the report value, and the report value can be calculated when determining the occurrence of the event and reported through the second uplink transmission.

[0330] General devices to which the present disclosure may be applied

[0331] FIG. 17 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0332] Referring to FIG. 17, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR).

[0333] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0334] A second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0335] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in the present disclosure, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in the present disclosure.

[0336] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0337] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0338] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of the present disclosure, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure, via one or more antennas (108, 208). In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0339] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0340] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics thereof. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

[0341] The scope of the present disclosure includes software or machine-executable instructions (e.g., an operating system, an application, firmware, a program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and executable on the device or computer. Instructions that can be used to program a processing system to perform the features described in the present disclosure can be stored on / in a storage medium or a computer-readable storage medium, and a computer program product including such a storage medium can be used to implement the features described in the present disclosure. The storage medium can include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and can include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory optionally includes one or more storage devices remotely located from the processor(s). The memory or, alternatively, the non-volatile memory device(s) within the memory comprise a non-transitory computer-readable storage medium. The features described in this disclosure may be incorporated into software and / or firmware stored on any of the machine-readable media, which may control the hardware of the processing system and allow the processing system to interact with other mechanisms that utilize results according to embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0342] Here, the wireless communication technology implemented in the wireless device (100, 200) of the present disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present disclosure may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present disclosure can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0343] The method proposed in this disclosure is explained with a focus on examples applied to 3GPP LTE / LTE-A and 5G systems, but can be applied to various wireless communication systems in addition to 3GPP LTE / LTE-A and 5G systems.

Claims

1. A step of receiving, by a user equipment (UE), configuration information related to channel state information (CSI) reporting from a base station; A step of receiving, by the UE, a downlink reference signal (RS) from the base station on one or more resources; A step of transmitting, by the UE, a first uplink transmission related to whether an event related to the CSI report has occurred to the base station; and A step of transmitting, by the UE, a second uplink transmission to the base station, the second uplink transmission including a report value derived based on the downlink RS, The occurrence of the event is determined and / or the report value is derived by using one or more active resources among the one or more resources for the downlink RS, A method wherein said one or more activated resources are counted X times, where X is an integer greater than 0.

2. In paragraph 1, A method wherein the one or more first activated resources used to determine the occurrence of the event and the one or more second activated resources used to derive the report value are different, wherein the one or more first activated resources and the one or more second resources are counted individually.

3. In paragraph 1, A method wherein said one or more activated resources are counted twice based on the same utilization of said one or more activated resources to determine the occurrence of said event and to derive said reporting value.

4. In paragraph 1, A method wherein the report value is calculated when determining the occurrence of the event based on the one or more activated resources being equally utilized to determine the occurrence of the event and deriving the report value, and the one or more activated resources are counted as 1.

5. In paragraph 1, A method wherein the first uplink transmission is an uplink transmission notifying that the event has occurred.

6. In paragraph 1, A method wherein, based on the occurrence of the above event, it is determined that one or more resources set for the downlink RS are activated for deriving the report value after the completion of the first uplink transmission and before the second uplink transmission.

7. In paragraph 6, A method wherein it is determined that one or more resources set for the downlink RS before the first uplink have been activated for deriving the report value since the last report value transmission before the first uplink transmission.

8. In paragraph 1, Regardless of whether the above event occurs or not, the resources for the downlink RS are not separately activated to derive the above reporting value. A method wherein the above-mentioned report value is calculated when determining the occurrence of the above-mentioned event and reported through the second uplink transmission.

9. In paragraph 1, A method wherein, based on the above event not occurring, it is determined that one or more resources set for the downlink RS are activated to determine occurrence of the event after completion of the first uplink transmission and before the second uplink transmission.

10. In paragraph 9, A method wherein the first uplink transmission is an uplink transmission that notifies that the event has not occurred.

11. In paragraph 9, Based on the occurrence of the above event, the resources for the downlink RS are not separately activated for deriving the above reporting value. A method wherein the above-mentioned report value is calculated when determining the occurrence of the above-mentioned event and reported through the second uplink transmission.

12. In paragraph 1, Further comprising a step of transmitting, by the UE, information about the capability of the UE to the base station, A method in which no more resources for the downlink RS are activated than are reported as the capability within any slot.

13. In paragraph 1, A method according to claim 1, wherein the above-mentioned reporting value is a pair of a resource identifier for the downlink RS and a Layer 1 reference signal received power (L1-RSRP) or a pair of a resource identifier for the downlink RS and a Layer 1 signal to interference and noise ratio (L1-SNIR).

14. In paragraph 1, A method wherein the above downlink RS corresponds to either a synchronization signal block (SSB) or a CSI-RS.

15. One or more transceivers for transmitting and receiving wireless signals; and comprising one or more processors controlling one or more of the above transceivers; One or more of the above processors: Receives configuration information related to channel state information (CSI) reporting from a base station; Receive a downlink reference signal (RS) on one or more resources from the base station; Transmitting a first uplink transmission related to the occurrence of an event related to the CSI report to the base station; and is configured to transmit a second uplink transmission including a report value derived based on the downlink RS to the base station; The occurrence of the event is determined and / or the report value is derived by using one or more active resources among the one or more resources for the downlink RS, A user device wherein one or more of the above activated resources are counted X times, where X is an integer greater than 0.

16. One or more non-transitory computer-readable media storing one or more instructions, The above one or more commands are executed by one or more processors so that a user equipment (UE): Receives configuration information related to channel state information (CSI) reporting from a base station; Receive a downlink reference signal (RS) on one or more resources from the base station; Transmitting a first uplink transmission related to the occurrence of an event related to the CSI report to the base station; and Controlling the base station to transmit a second uplink transmission including a report value derived based on the downlink RS, The occurrence of the event is determined and / or the report value is derived by using one or more active resources among the one or more resources for the downlink RS, A computer-readable medium, wherein said one or more activated resources are counted X times, where X is an integer greater than 0.

17. A processing device configured to control a user equipment (UE), wherein the processing device: one or more processors; and One or more computer memories operably connected to said one or more processors and storing instructions that perform operations based on execution by said one or more processors, The above actions are: A step of receiving configuration information related to channel state information (CSI) reporting from a base station; A step of receiving a downlink reference signal (RS) on one or more resources from the base station; A step of transmitting a first uplink transmission related to whether an event related to the CSI report has occurred to the base station; and comprising a step of transmitting a second uplink transmission including a report value derived based on the downlink RS to the base station; The occurrence of the event is determined and / or the report value is derived by using one or more active resources among the one or more resources for the downlink RS, A processing device, wherein one or more of the above activated resources are counted X times, where X is an integer greater than 0.

18. A step of transmitting, by a base station, configuration information related to reporting channel state information (CSI) to a user equipment (UE); A step of transmitting, by the base station, a downlink reference signal (RS) to the UE on one or more resources; A step of receiving, by the base station, a first uplink transmission related to whether an event related to the CSI report has occurred from the UE; and comprising a step of receiving, by the base station, a second uplink transmission from the UE, the second uplink transmission including a report value derived based on the downlink RS; The occurrence of the event is determined and / or the report value is derived by using one or more active resources among the one or more resources for the downlink RS, A method wherein said one or more activated resources are counted X times, where X is an integer greater than 0.

19. One or more transceivers for transmitting and receiving wireless signals; and comprising one or more processors controlling one or more of the above transceivers; One or more of the above processors: Transmits configuration information related to reporting channel state information (CSI) to a user equipment (UE); Transmitting a downlink reference signal (RS) on one or more resources to the UE; Receiving a first uplink transmission related to whether an event related to the CSI report has occurred from the UE; and is configured to receive a second uplink transmission including a report value derived based on the downlink RS from the UE; The occurrence of the event is determined and / or the report value is derived by using one or more active resources among the one or more resources for the downlink RS, A base station, wherein one or more of the above activated resources are counted as X times, where X is an integer greater than 0.

Images