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

Abstract

Disclosed are a method and apparatus for transmitting and receiving channel state information in a wireless communication system. The method according to an embodiment of the present disclosure may comprise the steps of: receiving, by a UE, configuration information related to a CSI report from a base station; receiving, by the UE from the base station, a downlink RS on one or more RS resources; transmitting, by the UE, a first uplink transmission to the base station on the basis that an event related to the CSI report is satisfied; and transmitting, by the UE 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] 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.

[0007] A method according to an aspect of the present disclosure may include: receiving, by a user equipment (UE), configuration information related to a channel state information (CSI) report from a base station; receiving, by the UE, a downlink reference signal (RS) from the base station on one or more RS resources; transmitting, by the UE, a first uplink transmission to the base station based on a satisfaction of an event related to the CSI report; and transmitting, by the UE, a second uplink transmission to the base station including a report value derived based on the downlink RS.

[0008] A method according to an additional aspect of the present disclosure may include: transmitting, by a base station, configuration information related to channel state information (CSI) reporting to a user equipment (UE); transmitting, by the base station, a downlink reference signal (RS) to the UE on one or more RS resources; receiving, by the base station, a first uplink transmission from the UE based on a satisfaction of an event related to the CSI reporting; and 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.

[0009] 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.

[0010] 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.

[0011] 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.

[0012] 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.

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

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

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

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

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

[0018] 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.

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

[0020] 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.

[0021] 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.

[0022] 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.

[0023] 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.

[0024] 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.

[0025] FIG. 13 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.

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

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

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

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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.

[0039] 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).

[0040] 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).

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

[0042] - BM: beam management

[0043] - CQI: Channel Quality Indicator

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

[0045] - CSI: Channel State Information

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

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

[0048] - DMRS: Demodulation Reference Signal

[0049] - FDM: frequency division multiplexing

[0050] - FFT: fast Fourier transform

[0051] - IFDMA: interleaved frequency division multiple access

[0052] - IFFT: inverse fast Fourier transform

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

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

[0055] - MAC: Medium Access Control

[0056] - NZP: non-zero power

[0057] - OFDM: orthogonal frequency division multiplexing

[0058] - PDCCH: Physical downlink control channel

[0059] - PDSCH: Physical downlink shared channel

[0060] - PMI: precoding matrix indicator

[0061] - RE: resource element

[0062] - RI: Rank indicator

[0063] - RRC: Radio Resource Control

[0064] - RSSI: Received signal strength indicator

[0065] - Rx: Reception

[0066] - QCL: quasi co-location

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

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

[0069] - TDM: Time Division Multiplexing

[0070] - TRP: transmission and reception point

[0071] - TRS: Tracking Reference Signal

[0072] - Tx: transmission

[0073] - UE: user equipment

[0074] - ZP: Zero Power

[0075] System General

[0076] 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.

[0077] 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.

[0078] 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.

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

[0080] 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.

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

[0082] 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.

[0083] 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.

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

[0085] 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.

[0086] 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).

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

[0088] 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.

[0089] 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.

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

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

[0092] 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.

[0093] 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.

[0094] 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.

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

[0096] 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.

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

[0098] - 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.

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

[0100] 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.

[0101]

[0102] 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.

[0103]

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

[0105] 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.

[0106] 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.

[0107] 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.

[0108] 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).

[0109] 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.

[0110] 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.

[0111] 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.

[0112] 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.

[0113] 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).

[0114] 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.

[0115] 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.

[0116] 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.

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

[0118] 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

[0119] 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.

[0120] 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).

[0121] 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.

[0122] 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.

[0123] 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.

[0124] 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.

[0125] 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.

[0126] 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.

[0127] Quasi-Co Location (QCL)

[0128] 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.

[0129] 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.

[0130] 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.

[0131] 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.

[0132] 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.

[0133] 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:

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

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

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

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

[0138] 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.

[0139] 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'.

[0140] beam management (BM)

[0141] 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.

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

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

[0144] - 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.

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

[0146] 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).

[0147] 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).

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

[0149] 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.

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

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

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

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

[0154] 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.

[0155] 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.

[0156] 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.

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

[0158] 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).

[0159] 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.

[0160] -- 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

[0161] 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.

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

[0163] 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).

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

[0165] 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.

[0166] 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)'.

[0167] 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.

[0168] (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.

[0169] 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.

[0170] 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.

[0171] 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.

[0172] 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.

[0173] 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.

[0174] 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'.

[0175] 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.

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

[0177] 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'.

[0178] 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).

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

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

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

[0182] 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.

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

[0184] 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.

[0185] 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).

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

[0187] 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.'

[0188] 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.

[0189] 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.

[0190] 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.

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

[0192] 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.

[0193] 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.

[0194] 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.

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

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

[0197] -- 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

[0198] 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).

[0199] UE initiated beam reporting method

[0200] 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.

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

[0202] 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.

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

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

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

[0206] 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.

[0207] 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.

[0208] Hereinafter, the present disclosure proposes a UE initiated beam reporting method.

[0209] Example 1: The UE may transmit a CSI reporting configuration identifier (ID: identifier) ​​when the UE initiates a beam report.

[0210] Table 9 illustrates the CSI reporting settings defined in 3GPP TS 38.331.

[0211] CSI-ReportConfig ::= SEQUENCE {reportConfigId CSI-ReportConfigId,carrier ServCellIndex OPTIONAL, -- Need SresourcesForChannelMeasurement CSI-ResourceConfigId,csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need Rnzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need RreportConfigType CHOICE {periodic SEQUENCE {reportSlotConfig CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUCCH SEQUENCE {reportSlotConfig CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUSCH SEQUENCE {reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320},reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),p0alpha P0-PUSCH-AlphaSetId},aperiodic SEQUENCE {reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32)}},

[0212] Referring to Table 8, a CSI report configuration ID (CSI report config ID) is set for each CSI report, and the type of CSI report (e.g., periodic CSI (P CSI), semi-persistent CSI (SP CSI) on PUCCH, SP CSI on PUSCH, aperiodic CSI (AP CSI)) is set.

[0213] In addition, for UE initiated beam reporting, RRC parameters may be additionally set as shown in Table 9 below.

[0214] CSI-ReportConfig ::= SEQUENCE {reportConfigId CSI-ReportConfigId,carrier ServCellIndex OPTIONAL, -- Need SresourcesForChannelMeasurement CSI-ResourceConfigId,csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need Rnzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need RreportConfigType CHOICE {periodic SEQUENCE {reportSlotConfig CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUCCH SEQUENCE {reportSlotConfig CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUSCH SEQUENCE {reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320},reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),p0alpha P0-PUSCH-AlphaSetId},aperiodic SEQUENCE {reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32)}UE-initiated SEQUENCE {reportSlotOffsetListpucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource}},.

[0215] Referring to Table 9, an RRC parameter (e.g., reportSlotOffsetList) for setting the timing for UE initiated beam reporting and an RRC parameter (e.g., pucch-CSI-ResourceList) for setting the PUCCH resource on which the UE initiated beam reporting is transmitted may be additionally set.

[0216] The base station can configure one or more CSI report configurations (CSI report configs) for the UE, each of which has a report configuration type set to UE-initiated. Different events can be configured for each CSI report (i.e., for each CSI report configuration). Alternatively, common events can be configured for all CSI reports (i.e., CSI report configurations). Alternatively, common events can be configured for some groups of all CSI reports (i.e., CSI report configurations).

[0217] For example, the base station can set CSI report configurations 1, 2, 3 (i.e., CSI report config ID = 1,2,3) for UE initiated beam reporting to the UE through RRC signaling. Then, specific CSI report(s) can be activated by the base station through dynamic signaling such as MAC-CE / DCI. Alternatively, CSI reports can be activated by the RRC configuration itself (i.e., only by the RRC configuration) without separate activation by the base station. The UE can monitor (or measure) an event condition for each activated CSI report. If the event condition for a specific CSI report is satisfied, the UE can perform a beam report for the corresponding CSI report. For example, the beam reporting quantity (or beam report) may include i) the identifier / index(s) of the downlink reference signal preferred by the UE (e.g., CRI, SSB index) and ii) the corresponding L1-RSRP or L1-SINR.

[0218] Here, the UE may report a CSI reporting configuration ID to the base station to inform the base station of which CSI report is being reported. For example, the CSI reporting configuration ID may be reported together with the beam reporting quantity (e.g., CRI, SSB index, L1 RSRP, or L1 SINR) or may be reported separately before reporting the beam reporting quantity.

[0219] Example 2: The UE may transmit beam reporting quantity (e.g., i) downlink reference signal ID / index(s) (CRI, SSB index, etc.), ii) L1-RSRP or L1-SINR) to the base station via an uplink channel (e.g., PUCCH, PUSCH) for UE initiated beam reporting.

[0220] Here, the uplink channel for UE initiated beam reporting can be secured / configured in advance from the base station.

[0221] - For example, the fact that an uplink channel for UE-initiated beam reporting has been secured / configured in advance by the base station may mean that the UE can use the corresponding uplink channel as needed, such as a configured grant (CG) PUSCH or a scheduling request (SR) PUCCH. Alternatively, it may mean that the UE can use the corresponding uplink channel as needed in a state where periodic (P) / semi-persistent (SP) PUCCH resources are allocated periodically / semi-persistently.

[0222] In this case, the UE can perform UE-initiated beam reporting to the base station via the CG PUSCH, SR PUCCH, or P / SP PUCCH for CSI reports that satisfy the event conditions. In other words, the UE can transmit beam reporting quantities to the base station via the CG PUSCH, SR PUCCH, or P / SP PUCCH for CSI reports that satisfy the event conditions.

[0223] - Or, as another example, the fact that an uplink channel for UE initiated beam reporting has been secured / configured in advance from a base station may mean that the UE requests an uplink channel for UE initiated beam reporting from the base station and an uplink PUSCH is configured / allocated through DCI for uplink scheduling.

[0224] Here, SR (scheduling request) PUCCH transmission can be used to request an uplink channel. That is, the UE can utilize the SR PUCCH for a CSI report that satisfies the event condition to request an UL channel for UE-initiated beam reporting from the base station. For example, while the legacy SR PUCCH only expresses / indicates whether a scheduling request is made for an uplink transport block (TB), the SR PUCCH for a UE-initiated beam report according to the present disclosure needs to be able to additionally express / indicate whether a scheduling request is made for the beam report. To this end, the base station can configure the UE by distinguishing whether the SR PUCCH is a scheduling request for a TB or a beam report. For example, the base station can configure the UE by distinguishing whether the SR PUCCH is for i) a TB, ii) a beam report, iii) or both a TB and a beam report. Here, if the SR PUCCH is for both TB and beam reporting (BR), the UE can request the base station to distinguish between four cases: i) TB+BR, ii) TB, iii) BR, and iv) none, using 2-bit information.

[0225] Meanwhile, the operations of the above-described embodiment 1 and embodiment 2 may be applied together, and accordingly, if an uplink channel for UE-initiated beam reporting is secured / configured in advance from a base station, the UE may transmit a CSI reporting configuration ID together with beam reporting quantity (e.g., i) downlink reference signal ID / index(s) (CRI, SSB index, etc.), ii) L1-RSRP or L1-SINR).

[0226] Here, the encoding order of the CSI reporting configuration ID can be positioned before or after the beam reporting quantity. For example, since the CSI reporting configuration ID is information that must be known before interpreting the beam reporting quantity, positioning it before the beam reporting quantity can facilitate the receiver's decoding implementation and bit sequence parsing method. Alternatively, by positioning the CSI reporting configuration ID after the beam reporting quantity, the transmitter can utilize the existing legacy bit sequence concatenation implementation and only add the CSI reporting configuration ID at the end.

[0227] CSI can be configured to include part 1 CSI and part 2 CSI, and the CSI reporting configuration ID can be configured to be included within the part 1 CSI.

[0228] In the existing beam reporting procedure, beam reporting quantity is configured as part 1 CSI, but in the case of UE initiated beam reporting according to the present disclosure, beam reporting quantity and payload size of beam reporting quantity may vary depending on the CSI reporting settings, and in this case, beam reporting quantity may be configured to be included in part 2 CSI.

[0229] Alternatively, to prevent the beam reporting quantity and the payload size of the beam reporting quantity from being different depending on the CSI reporting configuration, the UE may expect that the beam reporting quantity and the payload size of the beam reporting quantity of the CSI reporting configurations for UE-initiated beam reporting are set to be the same (i.e., can be set to be the same). To this end, the number of CSI-RSs / SSBs that are channel measurement targets (i.e., corresponding to channel measurement resources (CMRs)) for each CSI reporting configuration may be expected to be the same (i.e., can be set to be the same) and the report quantity (reportQuantity) may be set to be the same.

[0230] As another example, in reporting the CSI reporting configuration ID / beam reporting quantity of the UE, beam reporting for multiple CSI reporting configurations may be performed together. In this case, the UE may perform reporting by placing the CSI reporting configuration ID / beam reporting quantity for a specific CSI reporting configuration that includes the CRI (or SSB index) with the best quality (e.g., having the highest L1-RSRP / SINR value) at the front of the reporting payload. Here, the L1-RSRP / SINR value associated / associated with the CRI (or SSB index) with the best quality within the specific CSI reporting configuration may be reported as an absolute value (e.g., expressed in 7 bits). And, the L1-RSRP / SINR value related to / associated with another CRI (or SSB index) within the specific CSI reporting configuration or with a CRI (or SSB index) related to a CSI reporting configuration other than the specific CSI reporting configuration may be reported as a differential value (e.g., expressed as 4 bits).

[0231] For example, assuming that CSI reporting configurations 1, 2, and 3 are configured, and CRIs 1, 2, 3, 4, and 5, 6 within each CSI reporting configuration are configured, if CRI 4 within CSI reporting configuration 2 is measured with the highest L1-RSRP / SINR value, CSI reporting configuration 2 may be located first in the report payload, and the L1-RSRP / SINR value associated with / associated with CRI 4 may be reported as an absolute value (e.g., expressed with 7 bits), and the L1-RSRP / SINR values ​​associated with / associated with the remaining CRIs may be reported as differential values ​​(e.g., expressed with 4 bits). This operation may save the CSI reporting payload because the number of bits of the L1-RSRP / SINR value expressed for each CRI is reduced.

[0232] Additionally, in the above example, the number of bits representing a CRI may be localized by i) the number of CRIs in each CSI report among the multiple CSI report settings (dedicated to the CSI report settings), or ii) the number of all CRIs included in the multiple CSI report settings (across the multiple CSI report settings).

[0233] For the above local indexing, method i is a method that considers determining the number of bits to express a CRI in each reporting configuration, similar to obtaining CRIs by sub-configuration in network energy saving (NES), and method ii is a method that considers determining the number of bits to express a CRI from all CRI counts in multiple CSI reporting configurations. For example, assume that there are 2, 3, and 3 CMRs in CSI reporting configurations #1, #2, and #3, respectively. In this case, method i may require 1 bit, 2 bits, and 2 bits, respectively, to express the CRIs of reporting configurations #1, #2, and #3, considering the number of CRIs included in each reporting configuration (= the number of CSI-RS or SSB candidates that can be selected as CRIs). Method ii may require 3 bits considering all CRI counts in all reporting configurations. Here, in method i, the CSI reporting setting ID must be included in the reporting content for CRI expression by CSI reporting setting, whereas in method ii, it does not need to be included.

[0234] Example 3: After uplink transmission related to UE initiated beam reporting, the UE may transmit beam reporting quantity (e.g., i) downlink reference signal ID / index(s) (CRI, SSB index, etc.), ii) L1-RSRP or L1-SINR) to the base station via uplink channel (e.g., PUCCH, PUSCH) for UE initiated beam reporting.

[0235] - For example, an uplink transmission related to a UE initiated beam report may correspond to an uplink transmission requesting an uplink channel (or resources of an uplink channel) for the UE initiated beam report to the base station.

[0236] For this purpose, SR (scheduling request) PUCCH transmission can be utilized. That is, the UE can utilize SR PUCCH to request a UL channel for UE-initiated beam reporting from the base station for CSI reports that satisfy the above event conditions.

[0237] In addition, the operations of the above-described embodiment 1 and the operation of the embodiment 2 may be applied together, and when the UE requests an uplink channel for a UE-initiated beam report to the base station, the CSI reporting configuration ID may be reported through a request message before the beam reporting quantity report.

[0238] For example, if the legacy method is used, since the maximum amount of information that can be carried on the SR PUCCH is 2 bits, an uplink channel (or uplink channel resource) for one of up to four CSI reporting configuration IDs can be requested through the SR PUCCH. Alternatively, a random access channel (RACH) transmission can be used to request such an uplink channel. In this case, the CSI reporting configuration ID can be mapped 1:1 to a specific SSB index, or the CSI reporting configuration ID can be included in the RACH message.

[0239] And / or, since the information that can be carried on the SR PUCCH is at most 2 bits when using the legacy method, if there are at most 4 CMRs within a specific CSI reporting configuration (or a CMR set related thereto) for UE-initiated beam reporting, the report (that the quality of L1-RSRP / SINR value is good) for one of the at most 4 CMRs can be performed only through the SR-PUCCH transmission. That is, instead of transmitting a specific CSI reporting configuration ID via the SR PUCCH, a specific CMR within a specific CSI reporting configuration can be reported (e.g., via CRI). In this case, i) a beam report including the L1-RSRP / SINR value of the CRI reported via the corresponding SR-PUCCH can be reported via a subsequently scheduled PUSCH transmission, or ii) the PUSCH transmission (related to the CSI report) can be omitted without any subsequent report.

[0240] As another example, when the UE determines the UL channel / resource for UE-initiated beam reporting and notifies the base station, the CSI reporting configuration ID may be included in the notification message and reported before the beam reporting quantity is reported. That is, the UE may include the CSI reporting configuration ID in the notification message and report it when an event occurs, and thereafter, the UE may report the beam reporting quantity corresponding to the CSI reporting configuration ID on the uplink resource indicated by the notification message. Such a notification message may be transmitted using, for example, a CG PUSCH, and the notification message may include information about the CSI reporting configuration ID and the CSI reporting time (e.g., slot, start symbol, time period). For example, the PUCCH resource (see Table 9) configured in the corresponding CSI reporting configuration may be identified through the CSI reporting configuration ID in the notification message, and the transmission slot information of the PUCCH resource may be identified through the CSI reporting time information (see Example 4 described below). Here, since the start symbol, symbol duration, resource block (RB) information, etc. for PUCCH resources are set in advance, the base station and the UE (e.g., UE A) can know the UL frequency time resource information. If the PUCCH resource collides with the PUSCH resource that the base station has already set for another UE (e.g., UE B), the base station can notify UE B of the cancellation of the corresponding PUSCH resource through a cancellation indication. In addition, in order to prevent collision with the uplink channel allocated to such another UE in advance, the base station can notify UE A in advance of information on resources that cannot be used for uplink transmission, so that UE A can avoid the corresponding resources and determine UL resources.

[0241] - As another example, an uplink transmission related to a UE-initiated beam report may correspond to an uplink transmission for the UE to notify the base station that an event has occurred (or been satisfied). In this case, the base station may independently determine whether to schedule an uplink channel for the UE-initiated beam report.

[0242] Next, the UE can transmit beam reporting quantity (e.g., i) downlink reference signal ID / index(s) (CRI, SSB index, etc.), ii) L1-RSRP or L1-SINR) to the base station via uplink channel (e.g., PUCCH, PUSCH) for UE initiated beam reporting.

[0243] Here, based on the operation of Embodiment 2 and the operation of Embodiment 3 being applied together, the UE transmits an uplink transmission to the base station to notify that an event related to UE initiated beam reporting has occurred (has been satisfied), and the UE can transmit beam reporting quantity (e.g., i) downlink reference signal ID / index(s) (CRI, SSB index, etc.), ii) L1-RSRP or L1-SINR) to the base station through an uplink channel secured / configured in advance.

[0244] Meanwhile, although the above-described embodiments 1 to 3 mainly described how different CSI reporting configurations are configured for the UE for each beam report, beam reports may be defined / configured differently from this within a single CSI reporting configuration. In this case, beam reports share a single CSI reporting configuration ID, and beam reports may be distinguished according to how sub-configurations are configured within the CSI reporting configuration. For example, beam reports 1, 2, and 3 may be configured by configuring sub-configurations 1, 2, and 3, and each sub-configuration may have independent CMRs (and / or interference measurement resources (IMRs)) and event conditions configured. For example, such sub-configurations may be configured in the form of CMR (and / or IMR) sets. In this case, CMRs corresponding to beam reports 1, 2, and 3 may be configured by configuring CMR sets 1, 2, and 3 within the CSI reporting configuration. In this structure, the UE can inform the base station which beam report it is reporting by reporting a sub-set ID or a CMR (and / or IMR) set ID instead of the CSI report set ID in the embodiments 1 to 3 described above.

[0245] In other words, when a sub-setting ID or a CMR (and / or IMR) set ID is introduced, the CSI reporting setting ID in embodiments 1 to 3 can be applied by replacing it with the sub-setting ID or the CMR (and / or IMR) set ID.

[0246] Additionally, the reporting method of the CSI report configuration ID in the above-described embodiments 1 to 3 can also be applied to event ID reporting. That is, multiple events related to UE-initiated beam reporting can be set for the UE, and the UE can report to the base station which event the beam report is for when the UE-initiated beam report is made.

[0247] For example, if multiple different events are defined within the same CSI resource configuration and CSI reporting configuration, an event ID may be defined for each event. The UE may report to the base station which event the UE initiated beam report satisfied. For example, event 1 may be defined as reporting a beam with an RSRP of over 20 dB for the CMR for the UE initiated beam report, and event 2 may be defined as reporting a beam with a receive power that is over 10 dB higher than the beam currently used for DL / UL reception for the CMR for the UE initiated beam report. In this case, the UE may additionally report to the base station which event causes the beam report.

[0248] Meanwhile, in the above-described examples 1 to 3, ID can be interpreted as having the same meaning as index.

[0249] In addition, the reporting method of the CSI report configuration ID in the above-described embodiments 1 to 3 can be equally applied to reporting the CRI / SSB index. For example, if one CSI report for UE-initiated beam reporting is configured, the UE does not need to report the CSI report configuration ID, and instead can utilize the method of the above-described embodiments 1 to 3 to report the CRI / SSB index among the quantities of the corresponding CSI report.

[0250] Example 4: The beam reporting time (i.e., CSI reporting time) for a UE initiated beam report can be determined by the UE / base station.

[0251] Here, the beam reporting time (i.e., CSI reporting time) for the UE initiated beam reporting can be determined as an offset from the time of uplink transmission for the (UE initiated) beam reporting.

[0252] - When the UE transmits an uplink transmission (e.g., a request for uplink scheduling) for a (UE-initiated) beam report to the base station and / or the UE determines an uplink channel / resource for a (UE-initiated) beam report and notifies the base station, the UE may report CSI reporting time information to the base station. For example, the CSI reporting time information may be reported by applying the transmission method of the CSI reporting configuration ID in Embodiment 3.

[0253] Regarding Example 3 above, when transmitting an uplink transmission (e.g., requesting uplink scheduling) for a beam report (UE initiated) to a base station, the UE may transmit the reporting time information for the beam report by including it in the uplink transmission.

[0254] The above reporting time information may be information regarding the time at which the UE performs beam reporting (e.g., slot, start symbol, symbol time interval, etc.). In this case, the UE may independently determine the reporting time and report it to the base station. Furthermore, the reporting time may be expressed as an offset relative to the request time, as described below.

[0255] Alternatively, the reporting time information may indicate a time interval during which beam reporting should be performed. The UE can predict a time interval during which the beam reporting will not be outdated (or the beam reporting is valid / meaningful) by considering the time variation of the channel, and the base station may perform uplink scheduling so that the beam reporting can be performed within the time interval. For example, the reporting time information may be set as an offset for a request time (i.e., a transmission time of uplink transmission for (UE initiated) beam reporting). In this case, assuming that the request time (i.e., a transmission time of uplink transmission for (UE initiated) beam reporting) is slot n, by reporting the offset k, the base station can perform uplink scheduling so that the beam reporting is performed within slot n+k (i.e., slot n+k or earlier). If the base station performs uplink scheduling so that the beam reporting is performed after slot n+k, the UE may ignore the scheduling, or even if the beam reporting is performed according to the scheduling, the validity of the beam information may not be guaranteed. Alternatively, the UE may expect the base station to be uplink scheduled to perform beam reporting within slot n+k (or the UE may not expect the base station to be uplink scheduled to perform beam reporting after slot n+k).

[0256] The above offset k can be set by the base station to the UE as offset candidate values, such as the report slot offset list (e.g., reportSlotOffsetList) exemplified in Table 9 above, and the UE can determine k as one of the values ​​and report it to the base station.

[0257] In addition, with respect to Example 2 above, when the UE determines an uplink channel / resource for (UE initiated) beam reporting and notifies the base station, the reporting time information may be the time point (e.g., slot, start symbol, symbol time interval, etc.) at which the UE performs beam reporting. In this case, the UE may determine the reporting time itself and report it to the base station. In addition, the reporting time may be expressed as an offset based on the request time (i.e., the transmission time point of uplink transmission for (UE initiated) beam reporting) as described above.

[0258] - Additionally, the reporting time can be interpreted as the "event validity time," which can be determined not only by the channel's temporal variability but also by the measurement window / method (e.g., whether L3 filtering is used). Considering this, the reporting time can be predefined (in the standard) or set by the base station, in addition to the method by which the terminal reports it.

[0259] Even in this case, as described above, for example, the reporting time may be set as an offset relative to the timing of uplink transmission for UE-initiated beam reporting. For example, the offset k may be set by the base station to the UE as the offset candidate values ​​are set to 1, such as the report slot offset list (e.g., reportSlotOffsetList) exemplified in Table 9 above.

[0260] Additionally, reporting times can be predefined (in the standard) per event (or per event type) or set by the base station.

[0261] Example 5: Method for counting the number of active CSI-RS resources and the number of activated ports of NZP CSI-RS configured for UE initiated beam reporting

[0262] Table 10 is currently described in TS 38.214 Section 5.2.1.6 as follows:

[0263] In any slot, a UE is not expected to have more activated CSI-RS ports or activated CSI-RS resources in its activated BWPs than its reported capabilities. An NZP CSI-RS resource is activated for a time interval 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 related to this aperiodic CSI-RS. If the PDCCH candidates are associated with a search space set configured with the search space link identifier (searchSpaceLinkingId), the PDCCH candidate that ends later in time among the two linked PDCCH candidates is used to determine the activation interval of the NZP CSI-RS resource. 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 periodic CSI-RS is set as a higher layer signal and ends when the periodic CSI-RS configuration is cleared. 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 consisting of 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 that includes sub-configuration(s) indicated in the 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. It's counting.

[0264] The UE may count the NZP CSI-RS resources of the CSI report as active resources from the moment the CSI report configured for UE-initiated beam reporting is activated until the moment the CSI report is deactivated, and may count the number of ports of the resources as the active number.

[0265] For example, the base station can RRC configure the UE with CSI reporting configuration 1, 2, 3 (i.e., CSI reporting configuration ID = 1, 2, 3) for UE initiated beam reporting, and activate specific CSI report(s) through dynamic signaling such as MAC-CE / DCI (or, the RRC configuration itself can be used / considered as activation without a separate activation instruction). The UE can count the configured CSI-RS resources / ports in each activated CSI report as activated resources / ports until they are deactivated through dynamic signaling such as MAC-CE / DCI or RRC is released.

[0266] Here, the aforementioned CSI reporting settings 1, 2, and 3 are event-based, unlike conventional CSI reporting, and thus may not be reported even if enabled. However, to monitor event conditions, the UE must measure the corresponding NZP CSI-RS, so the corresponding NZP CSI-RS can be counted as an activated resource / port regardless of whether it is reported.

[0267] Considering these operational differences, activated CSI-RS resources / ports for UE-initiated beam reporting can be counted separately from existing activated CSI-RS resources / ports. Accordingly, when reporting UE capabilities, the UE can separately report to the base station the maximum number of activated CSI-RS resources / ports that can be supported for existing and the maximum number of activated CSI-RS resources / ports that can be supported for UE-initiated beam reporting.

[0268] FIG. 13 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.

[0269] FIG. 13 illustrates a signaling procedure between a UE and a base station based on the proposed methods in Embodiments 1 to 5 described above. The example in FIG. 13 is provided for convenience of explanation and does not limit the scope of the present disclosure. Some step(s) illustrated in FIG. 13 may be omitted depending on circumstances and / or settings. In addition, the base station and the UE in FIG. 13 are merely examples and may be implemented as devices illustrated in FIG. 16 below. For example, the processor (102 / 202) in FIG. 16 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. 16 to store transmitted or received channels / signals / data / information, etc., in the memory (104 / 204).

[0270] Referring to Fig. 13, the base station transmits configuration information to the UE (S1301).

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

[0272] 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).

[0273] 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)).

[0274] 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.

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

[0276] 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.

[0277] The base station transmits a downlink reference signal (i.e., beam) (e.g., SSB, CSI-RS, etc.) to the UE (S1302).

[0278] 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).

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

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

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

[0282] Here, based on the satisfaction of the relevant event related to the initiated / event-driven beam report, the UE can transmit a first uplink transmission to the base station, and thereafter, the UE can transmit a second uplink transmission to the base station including a report value derived based on a downlink reference signal. 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.

[0283] 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).

[0284] Additionally, the second uplink transmission can be performed via CG PUSCH.

[0285] Alternatively, the second uplink transmission may be performed via a PUSCH scheduled from the base station.

[0286] Additionally, based on multiple CSI reports being set for the UE, the first uplink transmission or the second uplink transmission may include information indicating which CSI report among the multiple CSI reports the report value is associated with.

[0287] Alternatively, based on multiple CSI reports being configured for the UE, the second uplink transmission may include multiple report values ​​for the multiple CSI reports. In this case, the highest report value for the multiple CSI reports may be located first, the highest report value may be reported as an absolute value, and the remaining report values ​​may be reported as differential values ​​with respect to the highest report value.

[0288] Additionally, based on multiple events being set for the UE (e.g., for one CSI report or for multiple CSI reports), the first uplink transmission or the second uplink transmission may include information indicating which of the multiple events the report value is associated with.

[0289] Additionally, the transmission time of the second uplink transmission may be determined as an offset from the transmission time of the first uplink transmission. For example, the transmission time of the second uplink transmission may be determined by the UE and transmitted as included in the first uplink transmission. Alternatively, the transmission time of the second uplink transmission may be predefined or set by the base station. For example, one or more offset candidates for the transmission time of the second uplink transmission may be set for the UE, and the offset may be determined from the one or more offset candidates.

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

[0291] FIG. 14 illustrates the operation of a UE based on the proposed methods in Embodiments 1 to 5 described above. The example in FIG. 14 is provided for convenience of explanation and does not limit the scope of the present disclosure. Some of the step(s) illustrated in FIG. 14 may be omitted depending on the situation and / or setting. In addition, the UE in FIG. 14 is only an example and may be implemented as a device illustrated in FIG. 16 below. For example, the processor (102 / 202) in FIG. 16 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. 16 to store the channels / signals / data / information to be transmitted or received in the memory (104 / 204).

[0292] Additionally, the operation of FIG. 14 may be processed by one or more processors (102, 202) of FIG. 16. Additionally, the operation of FIG. 14 may be stored in a memory (e.g., one or more memories (104, 204) of FIG. 16) 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. 16.

[0293] Referring to FIG. 14, the UE receives configuration information related to CSI reporting from the base station (S1401).

[0294] 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. 13 above.

[0295] 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.

[0296] The UE receives a downlink RS on one or more reference signal (RS) resources from a base station (S1402).

[0297] 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).

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

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

[0300] Based on the satisfaction of the event related to the CSI report, the UE transmits a first uplink transmission to the base station (S1403).

[0301] 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.

[0302] 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).

[0303] 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 (S1404).

[0304] 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.

[0305] Here, the second uplink transmission can be performed via CG PUSCH.

[0306] Alternatively, the second uplink transmission may be performed via a PUSCH scheduled from the base station.

[0307] Additionally, based on multiple CSI reports being set for the UE, the first uplink transmission or the second uplink transmission may include information indicating which CSI report among the multiple CSI reports the report value is associated with.

[0308] Alternatively, based on multiple CSI reports being configured for the UE, the second uplink transmission may include multiple report values ​​for the multiple CSI reports. In this case, the highest report value for the multiple CSI reports may be located first, the highest report value may be reported as an absolute value, and the remaining report values ​​may be reported as differential values ​​with respect to the highest report value.

[0309] Additionally, based on multiple events being set for the UE (e.g., for one CSI report or for multiple CSI reports), the first uplink transmission or the second uplink transmission may include information indicating which of the multiple events the report value is associated with.

[0310] Additionally, the transmission time of the second uplink transmission may be determined as an offset from the transmission time of the first uplink transmission. For example, the transmission time of the second uplink transmission may be determined by the UE and transmitted as included in the first uplink transmission. Alternatively, the transmission time of the second uplink transmission may be predefined or set by the base station. For example, one or more offset candidates for the transmission time of the second uplink transmission may be set for the UE, and the offset may be determined from the one or more offset candidates.

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

[0312] FIG. 15 illustrates the operation of a base station based on the proposed methods in Embodiments 1 to 5 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 base station in FIG. 15 is only an example and may be implemented with the device illustrated in FIG. 16 below. For example, the processor (102 / 202) in FIG. 16 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. 16 to store the channels / signals / data / information to be transmitted or received in the memory (104 / 204).

[0313] Additionally, the operation of FIG. 15 may be processed by one or more processors (102, 202) of FIG. 16. Additionally, the operation of FIG. 15 may be stored in a memory (e.g., one or more memories (104, 204) of FIG. 16) 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. 16.

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

[0315] 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. 13 above.

[0316] 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.

[0317] The base station transmits a downlink RS to the UE on one or more reference signal (RS) resources (S1502).

[0318] 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).

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

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

[0321] Based on the satisfaction of an event related to CSI reporting, the base station receives a first uplink transmission from the UE (S1503).

[0322] 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.

[0323] 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).

[0324] 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 (S1504).

[0325] 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.

[0326] Here, the second uplink transmission can be performed via CG PUSCH.

[0327] Alternatively, the second uplink transmission may be performed via a PUSCH scheduled from the base station.

[0328] Additionally, based on multiple CSI reports being set for the UE, the first uplink transmission or the second uplink transmission may include information indicating which CSI report among the multiple CSI reports the report value is associated with.

[0329] Alternatively, based on multiple CSI reports being configured for the UE, the second uplink transmission may include multiple report values ​​for the multiple CSI reports. In this case, the highest report value for the multiple CSI reports may be located first, the highest report value may be reported as an absolute value, and the remaining report values ​​may be reported as differential values ​​with respect to the highest report value.

[0330] Additionally, based on multiple events being set for the UE (e.g., for one CSI report or for multiple CSI reports), the first uplink transmission or the second uplink transmission may include information indicating which of the multiple events the report value is associated with.

[0331] Additionally, the transmission time of the second uplink transmission may be determined as an offset from the transmission time of the first uplink transmission. For example, the transmission time of the second uplink transmission may be determined by the UE and transmitted as included in the first uplink transmission. Alternatively, the transmission time of the second uplink transmission may be predefined or set by the base station. For example, one or more offset candidates for the transmission time of the second uplink transmission may be set for the UE, and the offset may be determined from the one or more offset candidates.

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

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

[0334] Referring to FIG. 16, 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).

[0335] 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.

[0336] 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.

[0337] 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.

[0338] 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.

[0339] 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.

[0340] 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.

[0341] 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.

[0342] 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.

[0343] 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.

[0344] 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.

[0345] 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 RS on one or more reference signal (RS) resources from the base station; A step of transmitting a first uplink transmission to the base station based on the event related to the CSI report being satisfied by the UE; and A method comprising the 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.

2. In paragraph 1, A method wherein the first uplink transmission is an uplink transmission notifying that the event has been satisfied.

3. In paragraph 1, A method wherein the first uplink transmission is performed via a physical uplink control channel (PUCCH).

4. In paragraph 2, A method for notifying that the above event has been satisfied, wherein a transmission method for a scheduling request (SR) is applied.

5. In paragraph 1, A method in which the second uplink transmission is performed through a configured grant (CG) PUSCH (physical uplink shared channel).

6. In paragraph 1, A method in which the second uplink transmission is performed through a PUSCH (physical uplink shared channel) scheduled from the base station.

7. In paragraph 1, A method wherein, based on a plurality of CSI reports being set for the UE, the first uplink transmission or the second uplink transmission includes information indicating which CSI report among the plurality of CSI reports the report value is related to.

8. In paragraph 1, A method wherein the second uplink transmission includes multiple report values ​​for the multiple CSI reports, based on multiple CSI reports being set for the UE.

9. In paragraph 8, For the above multiple CSI reports, the highest report value is located first, A method wherein the highest reported value is reported as an absolute value and the remaining reported values ​​are reported as differential values ​​with respect to the highest reported value.

10. In paragraph 1, A method wherein, based on a plurality of events being set for the UE, the first uplink transmission or the second uplink transmission includes information indicating which event among the plurality of events the report value is related to.

11. In paragraph 1, A method wherein the transmission time of the second uplink transmission is determined as an offset from the transmission time of the first uplink transmission.

12. In paragraph 11, A method wherein the transmission time of the second uplink transmission is determined by the UE and transmitted as included in the first uplink transmission.

13. In paragraph 11, One or more offset candidates are set for the transmission time of the second uplink transmission for the UE, A method wherein the offset is determined from one or more offset candidates.

14. In paragraph 1, The above reporting value is a pair of an identifier of an RS resource and a Layer 1 reference signal received power (L1-RSRP) or a pair of an identifier of an RS resource and a Layer 1 signal to interference and noise ratio (L1-SNIR).

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

16. User equipment (UE): 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 RS on one or more reference signal (RS) resources from the base station; transmitting a first uplink transmission to the base station based on the event related to the above CSI report being satisfied; and A UE configured to transmit a second uplink transmission including a report value derived based on the downlink RS to the base station.

17. 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 RS on one or more reference signal (RS) resources from the base station; transmitting a first uplink transmission to the base station based on the event related to the above CSI report being satisfied; and A computer-readable medium for controlling the base station to transmit a second uplink transmission including a report value derived based on the downlink RS.

18. In a processing device configured to control a user equipment (UE), the processing device: one or more processors; and One or more computer memories operatively 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 RS on one or more reference signal (RS) resources from the base station; A step of transmitting a first uplink transmission to the base station based on the event related to the above CSI report being satisfied; and A processing device comprising the step of transmitting a second uplink transmission including a report value derived based on the downlink RS to the base station.

19. 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 RS to the UE on one or more reference signal (RS) resources; A step of receiving a first uplink transmission from the UE based on the event related to the CSI report being satisfied by the base station; and A method comprising the 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.

20. The base station: 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 RS on one or more reference signal (RS) resources to the UE; receiving a first uplink transmission from the UE based on the event related to the above CSI report being satisfied; and A base station configured to receive a second uplink transmission including a report value derived based on the downlink RS from the UE.

Images