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

Abstract

A method and apparatus for transmitting and receiving channel state information in a wireless communication system are disclosed. The method according to an embodiment of the disclosure can comprise the steps of receiving, by a UE, configuration information related to a CSI report from a base station; receiving, by the UE, downlink RSs from the base station on one or more RS resources; transmitting, by the UE, a first uplink transmission to the base station based on an event related to the CSI report being satisfied; and transmitting, by the UE, a second uplink transmission to the base station including a report value derived based on the downlink RSs.

Description

Technical Field

[0001] This disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for transmitting and receiving channel state information in the wireless communication system. Background Technology

[0002] A mobile communication system has been developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded to include data and voice services, and the current explosive growth in these services has led to resource shortages. Users are demanding faster services and therefore require more advanced mobile communication systems.

[0003] The overall requirements for next-generation mobile communication systems should be able to support the capacity for explosive data traffic, significantly increased per-user transmission rates, a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To this end, various technologies have been investigated, including dual connectivity, massive MIMO, in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and device networking. Summary of the Invention

[0004] Technical issues

[0005] The technical objective of this disclosure is to provide a method and apparatus for transmitting and receiving channel state information (CSI) (including beam reports).

[0006] Additionally, an additional technical objective of this disclosure is to provide a method and apparatus for performing UE-initiated (UE-initiated) or event-driven (event-driven) beam reporting.

[0007] The technical objectives achieved through this disclosure are not limited to those described above, and those skilled in the art will clearly understand from the following description other technical objectives not described herein.

[0008] Technical solution

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

[0010] The method according to an additional aspect of this disclosure may include: a base station sending configuration information related to a channel state information (CSI) report to a user equipment (UE); a base station sending a downlink RS to the UE on one or more reference signal (RS) resources; the base station receiving a first uplink transmission from the UE based on an event related to the CSI report being satisfied; and the base station receiving a second uplink transmission from the UE including a report value derived from the downlink RS.

[0011] Beneficial effects

[0012] According to embodiments of this disclosure, beam reporting is possible only when an event is met, without requiring additional indication / configuration from the base station for beam reporting.

[0013] Furthermore, embodiments of this disclosure can reduce signaling overhead and enable flexible / appropriate beam reporting as environmental conditions change.

[0014] The effects achievable by this disclosure are not limited to those described above, and those skilled in the art can clearly understand from the following description other effects not described herein. Attached Figure Description

[0015] The accompanying drawings, included as part of the detailed description for understanding this disclosure, provide embodiments of the disclosure and describe the technical features of the disclosure through detailed description.

[0016] Figure 1 The diagram illustrates the structure of a wireless communication system to which this disclosure can be applied.

[0017] Figure 2 The diagram illustrates the frame structure applicable to wireless communication systems disclosed herein.

[0018] Figure 3 The diagram illustrates a resource grid that can be applied to a wireless communication system according to this disclosure.

[0019] Figure 4 The diagram illustrates physical resource blocks in a wireless communication system that can be applied according to this disclosure.

[0020] Figure 5 The diagram illustrates a time slot structure applicable to wireless communication systems according to this disclosure.

[0021] Figure 6 The diagram illustrates a physical channel used in a wireless communication system to which this disclosure can be applied, as well as general signal transmission and reception methods using that physical channel.

[0022] Figure 7 This is a diagram illustrating downlink beam management operations in a wireless communication system to which the present disclosure can be applied.

[0023] Figure 8 This is a diagram illustrating the downlink beam management process using SSB in a wireless communication system to which this disclosure may be applied.

[0024] Figure 9 This is a diagram illustrating downlink beam management operation using CSI-RS in a wireless communication system to which this disclosure may be applied.

[0025] Figure 10 This is a diagram illustrating the Rx beam determination process of a terminal in a wireless communication system to which the present disclosure can be applied.

[0026] Figure 11 This is a diagram illustrating the Tx beam determination process of a base station in a wireless communication system to which the present disclosure can be applied.

[0027] Figure 12 This is a diagram illustrating the allocation of resources in the time and frequency domains related to downlink beam management operations in a wireless communication system to which this disclosure can be applied.

[0028] Figure 13 This is a diagram illustrating the signaling process between a base station and a UE for a UE-initiated beam reporting method according to an embodiment of the present disclosure.

[0029] Figure 14 This is a diagram illustrating the operation of a UE for reporting channel state information according to an embodiment of the present disclosure.

[0030] Figure 15 This is a diagram illustrating the operation of a base station for reporting channel state information according to an embodiment of the present disclosure.

[0031] Figure 16 The figure shows a block diagram of a wireless communication device according to an embodiment of the present disclosure. Detailed Implementation

[0032] In the following, embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed with reference to the drawings is intended to describe exemplary embodiments of the present disclosure and not to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the art will recognize that the present disclosure may be practiced without these specific details.

[0033] In some cases, known structures and devices may be omitted, or they may be shown in block diagram form based on the core functions of each structure and device in order to prevent ambiguity of the concepts in this disclosure.

[0034] In this disclosure, when an element is referred to as “connected,” “combined,” or “linked” to another element, it can include both indirect and direct connections between the two elements. Furthermore, in this disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, operations, components, and / or elements, but do not exclude the presence or addition of one or more other features, stages, operations, components, elements, and / or groups thereof.

[0035] In this invention, terms such as "first" and "second" are used only to distinguish one element from another and are not used to limit the elements. Unless otherwise stated, they do not limit the order or importance of the elements. Therefore, within the scope of this disclosure, a first element in one embodiment may be referred to as a second element in another embodiment, and similarly, a second element in one embodiment may be referred to as a first element in another embodiment.

[0036] The terminology used in this disclosure is for the purpose of describing particular embodiments and not for limiting the claims. As used in the description of the embodiments and the appended claims, the singular forms are intended to include the plural forms unless the context clearly indicates otherwise. The term “and / or” as used in this disclosure may refer to one of the associated enumerations, or is intended to refer to and include any and all possible combinations of two or more of them. Furthermore, unless otherwise stated, the “ / ” between words in this invention has the same meaning as “and / or”.

[0037] This disclosure describes a wireless communication network or wireless communication system, and operations performed in the wireless communication network can be performed in the process of a device (e.g., a base station) controlling the network and transmitting or receiving signals, or in the process of a terminal associated with the corresponding wireless network transmitting or receiving signals with the network or between the terminal.

[0038] In this disclosure, the term "transmit or receive channel" includes the meaning of transmitting or receiving information or signals through a corresponding channel. For example, transmitting a control channel means transmitting control information or control signals through a control channel. Similarly, transmitting a data channel means transmitting data information or data signals through a data channel.

[0039] In the following text, downlink (DL) refers to communication from a base station to a terminal, while uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter can be part of the base station, and the receiver can be part of the terminal. In the uplink, the transmitter can be part of the terminal, and the receiver can be part of the base station. A base station can be referred to as a first communication device, and a terminal can be referred to as a second communication device. A base station (BS) can be replaced by terms such as fixed station, Node B, eNB (evolved Node B), gNB (next-generation Node B), BTS (Base Transceiver System), Access Point (AP), Network (5G network), AI (Artificial Intelligence) system / module, RSU (Roadside Unit), robot, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, terminals can be fixed or mobile, and can be replaced by 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) equipment, M2M (Machine-to-Machine) equipment, D2D (Device-to-Device) equipment, vehicle, RSU (Roadside Unit), robot, AI (Artificial Intelligence) module, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) equipment, VR (Virtual Reality) equipment, etc.

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

[0041] To make the description clearer, it is based on 3GPP communication systems (e.g., LTE-A, NR), but the technical ideas of this disclosure are not limited thereto. LTE refers to technology from 3GPP TS (Technical Specification) version 8 onwards. Specifically, LTE technology in or after 3GPP TS 36.xxx version 10 is referred to as LTE-A, and LTE technology in or after 3GPP TS 36.xxx version 13 is referred to as LTE-A pro. 3GPP NR refers to technology in or after TS 38.xxx version 15. LTE / NR can be referred to as a 3GPP system. "xxx" refers to the detailed number of the standard document. LTE / NR is generally referred to as a 3GPP system. For background technology, terminology, abbreviations, etc., used to describe this disclosure, reference can be made to the matters described in the standard documents previously published. For example, the following documents can be consulted.

[0042] For 3GPP LTE, you can refer to 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).

[0043] For 3GPP NR, you can refer to 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 (General Description of NR and NG-RAN (Next Generation Radio Access Network)), and TS 38.331 (Radio Resource Control Protocol Specification).

[0044] The abbreviations of terms that may be used in this disclosure are defined as follows.

[0045] - BM: Beam Management

[0046] - CQI: Channel Quality Indicator

[0047] - CRI: Channel State Information - Reference Signal Resource Indicator

[0048] - CSI: Channel State Information

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

[0050] - CSI-RS: Channel State Information - Reference Signal

[0051] - DMRS: Demodulation Reference Signal

[0052] - FDM: Frequency Division Multiplexing

[0053] - FFT: Fast Fourier Transform

[0054] - IFDMA: Interleaved Frequency Division Multiple Access

[0055] - IFFT: Inverse Fast Fourier Transform

[0056] - L1-RSRP: Layer 1 Reference Signal Received Power

[0057] - L1-RSRQ: Layer 1 Reference Signal Receive Quality

[0058] - MAC: Media Access Control

[0059] - NZP: Non-zero power

[0060] - OFDM: Orthogonal Frequency Division Multiplexing

[0061] - PDCCH: Physical Downlink Control Channel

[0062] - PDSCH: Physical Downlink Shared Channel

[0063] - PMI: Precoding Matrix Indicator

[0064] - RE: Resource Elements

[0065] - RI: Rank Indicator

[0066] - RRC: Radio Resource Control

[0067] - RSSI: Received Signal Strength Indicator

[0068] - Rx: Receive

[0069] - QCL: Quasi-co-located

[0070] SINR: Signal-to-Interference-plus-Noise Ratio

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

[0072] - TDM: Time Division Multiplexing

[0073] - TRP: Transmitting and Receiving Point

[0074] - TRS: Tracking Reference Signal

[0075] - Tx: Send

[0076] - UE: User Equipment

[0077] - ZP: Zero Power

[0078] Overall System

[0079] With more communication devices requiring higher capacity, there has been a demand for improved mobile broadband communications compared to existing radio access technologies (RATs). Furthermore, massive MTC (machine-type communication) that provides various services anytime, anywhere by connecting multiple devices and things is also one of the main issues to be considered in next-generation communications. In addition, communication system designs considering services / terminals sensitive to reliability and latency are discussed. Therefore, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), mMTC (massive MTC), URLLC (ultra-reliable low-latency communication), etc., is discussed, and for convenience, the corresponding technologies are referred to as NR in this disclosure. NR is an example expression representing 5G RAT.

[0080] New RAT systems, including those for NR, use OFDM or similar transmission methods. These new RAT systems may follow OFDM parameters different from those used in LTE. Alternatively, the new RAT system may follow existing LTE / LTE-A parameters as is, but may support a wider system bandwidth (e.g., 100MHz). Alternatively, a single cell may support multiple parameter sets. In other words, terminals operating according to different parameter sets can coexist in a single cell.

[0081] The parameter set corresponds to a subcarrier spacing in the frequency domain. Different parameter sets can be defined as the reference subcarrier spacing is scaled by an integer N.

[0082] Figure 1 The diagram illustrates the structure of a wireless communication system to which this disclosure can be applied.

[0083] refer to Figure 1 The NG-RAN is configured with gNBs that provide control plane (RRC) protocol support for the NG-RA (NG Radio Access) user plane (i.e., the new AS (Access Layer) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and UE. The gNBs interconnect via the Xn interface. Furthermore, the gNBs are connected to the NGC (Next Generation Core) via the NG interface. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Power) via the N2 interface and to the UPF (User Plane Functions) via the N3 interface.

[0084] Figure 2 The diagram illustrates a frame structure in a wireless communication system to which this disclosure can be applied.

[0085] NR systems can support multiple parameter sets. These parameter sets can be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings can be derived by scaling the basic (reference) subcarrier spacing by an integer N (or μ). Furthermore, while it is assumed that very low subcarrier spacings are not used at very high carrier frequencies, the parameter set used can be selected independently of the frequency band. Moreover, various frame structures based on multiple parameter sets can be supported in NR systems.

[0086] The OFDM parameter sets and frame structures that can be considered in an NR system are described below. Several OFDM parameter sets supported in an NR system can be defined as shown in Table 1 below.

[0087] [Table 1]

[0088] NR supports multiple sets of parameters (or subcarrier spacing (SCS)) to support various 5G services. For example, a 15kHz SCS supports wide-area coverage of traditional cellular bands; a 30kHz / 60kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidth; and a 60kHz or higher SCS supports bandwidths exceeding 24.25GHz to overcome phase noise.

[0089] The NR band is defined as frequency ranges of two types (FR1, FR2). FR1 and FR2 can be configured as shown in Table 2 below. Additionally, FR2 can refer to millimeter wave (mmW).

[0090] [Table 2]

[0091] Regarding the frame structure in the NR system, the size of various fields in the time domain is expressed as T. c =1 / (Δf max ·N f A multiple of the time unit. Here, Δf max i is 480·10 3 Hz, and N f The value is 4096. Downlink and uplink transmissions are configured (organized) to have a duration T. f= 1 / (Δf) max N f / 100)·T c A radio frame of 10ms. Here, the radio frame is configured with 10 subframes, each with a T... sf =(Δf max N f / 1000)·T c=1ms duration. In this case, there may be one frame set for the uplink and one frame set for the downlink. Furthermore, the transmission in the i-th uplink frame from the terminal should begin T earlier than the corresponding downlink frame in the corresponding terminal. TA =(N TA +N TA,offset )T c Begin. For the subcarrier spacing configuration μ, the time slots are arranged in n-order within the subframe. s μ ∈{0,..., N slot subframe,μ The numbers are numbered in ascending order from -1, and in the radio frames, they are numbered in n... s,f μ ∈{0,..., N slot frame,μ The time slot is configured with N in ascending order of -1. symb slot N consecutive OFDM symbols, and N symb slot Determined based on CP. Slot n in the subframe s μ The start of the OFDM symbol n in the same subframe s μ N symb slot The start dates are arranged in time. Not all terminals may perform transmission and reception simultaneously, meaning that all OFDM symbols in either the downlink or uplink time slots may not be available.

[0092] Table 3 shows the number of OFDM symbols (N) in each time slot during normal CP. symb slot ), Number of time slots per radio frame (N) slot frame,μ ) and the number of time slots per subframe (N) slot subframe,μ Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0093] [Table 3]

[0094] [Table 4]

[0095] Figure 2 This is an example of μ=2 (SCS is 60kHz), see Table 3. One subframe can include 4 time slots. For example... Figure 2The subframe shown as {1,2,4} is an example. The number of time slots that can be included in a subframe is defined in Table 3 or Table 4. Additionally, micro-time slots can include 2, 4, or 7 symbols, or more or fewer symbols.

[0096] Regarding physical resources in an NR system, factors such as antenna ports, resource grids, resource elements, resource blocks, and carrier components can be considered. The following sections will describe these physical resources in detail.

[0097] First, regarding antenna ports, an antenna port is defined such that the channel carrying symbols in that antenna port can be inferred from the channels carrying other symbols in the same antenna port. Two antenna ports can be said to be in a QC / QCL (quasi-co-location or quasi-co-addressable) relationship when the large-scale properties of the channel carrying symbols in one antenna port can be inferred from the channels carrying symbols in another antenna port. In this case, the large-scale properties include at least one of delay spread, Doppler spread, frequency shift, average received power, and receive timing.

[0098] Figure 3 The illustration shows a resource grid in a wireless communication system to which this disclosure can be applied.

[0099] refer to Figure 3 The diagram illustrates the resource grid configuration with N in the frequency domain. RB μ N sc RB There are 14.2 subcarriers, and one subframe is configured with 14.2 μ The number of OFDM symbols is not limited to this. In an NR system, the transmitted signal consists of 2 OFDM symbols. μ N symb （μ） Each OFDM symbol and configuration has N RB μ N sc RB It is described by one or more resource grids of N subcarriers. Here, N RB μ ≤ N RB max,μ N RB max,μ This represents the maximum transmission bandwidth, which may differ between uplink and downlink, and between parameter sets. In this case, each μ and antenna port p can be configured with a resource grid. Each element of the resource grid used for μ and antenna port p is called 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 symbol position within the subframe. When referencing resource elements in a time slot, index pairs (k, l) are used. Here, l = 0,..., N. symb μ -1. The resource element (k, l') used for μ and antenna port p corresponds to the complex value a. k,l' （p,μ） When there is no risk of confusion or when a specific antenna port or parameter set is not specified, the indices p and μ may be discarded, and the complex value may be a. k,l' （p） or a k,l' Furthermore, a resource block (RB) is defined as N in the frequency domain. sc RB =12 consecutive subcarriers.

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

[0101] - The offsetToPointA of the downlink in the primary cell (PCell) represents the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block, which is used by the terminal for initial cell selection. It is assumed that a 15kHz subcarrier spacing is used for FR1 and a 60kHz subcarrier spacing is used for FR2, expressed in units of resource blocks.

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

[0103] For subcarrier spacing configuration μ, common resource blocks are numbered from 0 upwards in the frequency domain. The center of subcarrier 0 of common resource block 0 used for subcarrier spacing configuration μ is the same as "point A". The common resource block number n of subcarrier spacing configuration μ in the frequency domain is... CRB μ The relationship between the resource element (k,l) and the resource element (k,l) is given by Equation 1 below.

[0104] [Formula 1]

[0105] In Equation 1, k is defined relative to point A, such that k = 0 corresponds to a subcarrier centered at point A. The physical resource block (BWP) ranges from 0 to N. BWP,i size,μ -1 is the number, and i is the number of the BWP. The physical resource block n in BWP i. PRB and public resource block nCRB The relationship between them is given by Equation 2.

[0106] [Equation 2]

[0107] N BWP,i start,μ It is a public resource block relative to public resource block 0 in BWP.

[0108] Figure 4 The diagram illustrates physical resource blocks in a wireless communication system to which this disclosure can be applied. Furthermore, Figure 5 The diagram illustrates a time slot structure in a wireless communication system to which this disclosure can be applied.

[0109] refer to Figure 4 and Figure 5 A time slot includes multiple symbols in the time domain. For example, for a normal CP, one time slot includes 7 symbols, but for an extended CP, one time slot includes 6 symbols.

[0110] 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 Component) is defined as multiple consecutive (physical) resource blocks in the frequency domain and can correspond to a set of parameters (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through active BWPs, and only one BWP can be active for a single terminal. In the resource grid, each element is called a resource element (RE) and can be mapped to a complex number of symbols.

[0111] In NR systems, each component carrier (CC) can support up to 400MHz. If a terminal operating in such a wideband CC always operates with the radio frequency (FR) chip turned on for the entire CC, terminal battery consumption may increase. Alternatively, when considering multiple application scenarios operating in a wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different sets of parameters (e.g., subcarrier spacing, etc.) can be supported in each frequency band of the corresponding CC. Alternatively, each terminal may have different capabilities for the maximum bandwidth. With this in mind, the base station can instruct the terminal to operate only in a portion of the bandwidth, rather than in the full bandwidth of the wideband CC, and for convenience, the corresponding portion of the bandwidth is defined as the bandwidth portion (BWP). The BWP can be configured with consecutive RBs on the frequency axis and can correspond to a set of parameters (e.g., subcarrier spacing, CP length, slot / microslot duration).

[0112] Simultaneously, even within a single CC configured for a terminal, the base station can configure multiple BWPs. For example, a BWP occupying a relatively small frequency domain can be configured in the PDCCH monitoring slot, and PDSCH indicated by the PDCCH can be scheduled in a larger BWP. Alternatively, when a UE is congested in a particular BWP, other BWPs can be configured for some terminals for load balancing. Alternatively, considering inter-cell interference cancellation in the frequency domain between neighboring cells, some intermediate spectrum of the full bandwidth can be excluded, and two edge BWPs can be configured in the same time slot. In other words, the base station can configure at least one DL / UL BWP for a terminal associated with a broadband CC. The base station can activate at least one DL / UL BWP among the configured DL / UL BWPs at a specific time (via L1 signaling, MAC CE (control element), or RRC signaling, etc.). Furthermore, the base station can instruct a handover to other configured DL / UL BWPs (via L1 signaling, MAC CE, or RRC signaling, etc.). Alternatively, based on a timer, a handover to a specific DL / UL BWP can be performed when the timer value expires. Here, the active DL / UL BWP is defined as the active DL / UL BWP. However, the terminal may not receive the configuration on the DL / UL BWP before performing the initial access procedure or establishing an RRC connection. Therefore, in these cases, the DL / UL BWP assumed by the terminal is defined as the initially active DL / UL BWP.

[0113] Figure 6 The illustration shows a physical channel used in a wireless communication system to which this disclosure can be applied, as well as general signal transmission and reception methods using the physical channel.

[0114] In wireless communication systems, terminals receive information from base stations via downlink and transmit information to base stations via uplink. The information sent and received by base stations and terminals includes data and various control information, and various physical channels exist depending on the type / purpose of the information they send and receive.

[0115] When a terminal is powered on or enters a new cell, it performs an initial cell search (S601), including synchronization with the base station. For the initial cell search, the terminal synchronizes with the base station by receiving the primary synchronization signal (PSS) and secondary synchronization signal (SSS) from the base station, and obtains information such as the cell identifier (ID). Then, the terminal obtains broadcast information within the cell by receiving the physical broadcast channel (PBCH) from the base station. Simultaneously, the terminal checks the downlink channel state by receiving the downlink reference signal (DL RS) during the initial cell search phase.

[0116] Terminals that have completed the initial cell search can obtain more detailed system information by receiving the Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH) based on the information carried in the PDCCH (S602).

[0117] Simultaneously, when a terminal first accesses a base station or when there are no radio resources available for signal transmission, it can perform a random access (RACH) procedure (S603 to S606). For the random access procedure, the terminal can send a specific sequence as a preamble via the Physical Random Access Channel (PRACH) (S603 and S605), and can receive response messages to the preamble via the PDCCH and the corresponding PDSCH (S604 and S606). Contention-based RACH can further execute a contention resolution procedure.

[0118] The terminal that subsequently performs the above process can execute PDCCH / PDSCH reception (S607) and PUSCH (Physical Uplink Shared Channel) / PUCCH (Physical Uplink Control Channel) transmission (S608) as a general uplink / downlink signal transmission process. Specifically, the terminal receives downlink control information (DCI) via PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format varies depending on its intended use.

[0119] Meanwhile, control information sent by the terminal to the base station via the uplink or received by the terminal from the base station includes downlink / uplink ACK / NACK (acknowledgment / non-acknowledgment) signals, CQI (Channel Command Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. For 3GPP LTE systems, the terminal can send the aforementioned control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

[0120] Table 5 shows examples of DCI format in NR systems.

[0121] [Table 5]

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

[0123] DCI format 0_0 is used to schedule PUSCH in a cell. The information included in DCI format 0_0 is scrambled with CRC (Cyclic Redundancy Check) by C-RNTI (Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and transmitted.

[0124] DCI format 0_1 ​​is used to indicate the scheduling of one or more PUSCHs or to provide downlink feedback information to the Terminal Configuration Grant (CG) in a cell. The information included in DCI format 0_1 ​​is scrambled and transmitted by C-RNTI, CS-RNTI, SP-CSI-RNTI (semi-persistent CSI RNTI), or MCS-C-RNTI.

[0125] DCI format 0_2 is used to schedule PUSCH within a cell. The information included in DCI format 0_2 is scrambled and transmitted using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0126] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information (e.g., frequency resource allocation, time resource allocation, VRB (Virtual Resource Block) - PRB (Physical Resource Block) mapping, etc.), information related to transport blocks (TB) (e.g., MCS, NDI, RV, etc.), information related to HARQ (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., antenna port, TCI (Transmission Configuration Indicator), SRS (Sound Reference Signal) request, etc.), PUCCH-related information regarding PDSCH scheduling (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format can be predefined.

[0127] DCI format 1_0 is used to schedule PDSCH in a DL cell. The information included in DCI format 1_0 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0128] DCI format 1_1 is used to schedule PDSCH in a cell. The information included in DCI format 1_1 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0129] DCI format 1_2 is used to schedule PDSCH in a cell. The information contained in DCI format 1_2 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0130] Quasi-co-located (QCL)

[0131] Define an antenna port such that the channel transmitting a symbol in the same antenna port can be inferred from the channel transmitting other symbols in the same antenna port. When the properties of the channel carrying a symbol in one antenna port can be inferred from the channel carrying symbols in other antenna ports, it can be said that two antenna ports are in a QC / QCL (quasi-co-location or quasi-co-addressable) relationship.

[0132] Here, channel attributes include at least one of delay spread, Doppler spread, frequency / Doppler shift, average received power, receive timing / average delay, or spatial Rx parameters. Here, spatial Rx parameters refer to spatial (Rx) channel attribute parameters, such as angle of arrival.

[0133] The terminal can configure up to a list of M TCI-State configurations in the higher-level parameter PDSCH-Config to decode the PDSCH based on the detected PDCCH with the expected DCI for the corresponding terminal and a given serving cell. M depends on the UE capability.

[0134] Each TCI-State includes parameters for configuring the quasi-co-address relationship between the ports of one or two DL reference signals and the DM-RS (demodulation reference signal) of the PDSCH.

[0135] The quasi-co-address relationship is configured by the higher-level parameter qcl-Type1 for the first DL RS and qcl-Type2 (if configured) for the second DL RS. The QCL types are different for the two DL RSs, regardless of whether the references are the same or different DL RSs.

[0136] The QCL type corresponding to each DL RS is given by the higher-level parameter qcl-Type of QCL-Info, and can take one of the following values.

[0137] - "QCL-TypeA": {Doppler frequency shift, Doppler spread, average delay, delay spread}

[0138] - "QCL-TypeB": {Doppler frequency shift, Doppler spread}

[0139] - "QCL-TypeC": {Doppler frequency shift, average delay}

[0140] - "QCL-TypeD": {Space Rx parameter}

[0141] For example, when the target antenna port is a specific NZP CSI-RS, the corresponding NZP CSI-RS antenna port can be instructed / configured to be quasi-co-located with a specific TRS for QCL-Type A and quasi-co-located with a specific SSB for QCL-Type D. The terminal receiving such instruction / configuration can receive the corresponding NZP CSI-RS TRS by using the Doppler and delay values ​​measured in QCL-Type A, and apply the Rx beam used for receiving the QCL-Type D SSB to the reception of the corresponding NZP CSI-RS.

[0142] The UE can receive activation commands via MAC CE signaling, which is used to map up to 8 TCI states to code points in the DCI field "Transmission Configuration Indication".

[0143] Beam management (BM)

[0144] The BM process is an L1 (Layer 1) / L2 (Layer 2) process used to obtain and maintain a set of beams that can be used for downlink (DL) and uplink (UL) transmission / reception of base station (e.g., gNB, TRP, etc.) and / or terminal (e.g., UE) beams, which may include the following procedures and terms.

[0145] Beam measurement: The operation by which a base station or UE measures the properties of the received beamformed signal.

[0146] Beam determination: The operation of a base station or UE selecting its Tx beam / Rx beam.

[0147] Beam scanning: the operation of covering a spatial region in a predetermined manner within a certain time interval using Tx and / or Rx beams.

[0148] Beam Reporting: UE operations based on beamforming signal information from beam measurement reports.

[0149] BM processes can be classified as (1) DL BM processes using SS (synchronization signal) / PBCH (physical broadcast channel) blocks or CSI-RS, and (2) UL BM processes using SRS (sound reference signal).

[0150] In addition, each BM process may include a Tx beam scan for determining the Tx beam and an Rx beam scan for determining the Rx beam.

[0151] The DL BM process will be described below.

[0152] The DL BM process may include (1) the transmission of the DL RS (reference signal) (e.g., CSI-RS or SS block (SSB)) of the base station beamforming and (2) the beam reporting of the terminal.

[0153] Here, the beam report may include the preferred DL RS ID (identifier) ​​and the corresponding L1-RSRP (reference signal received power).

[0154] The DL RS ID can be either SSBRI (SSB Resource Indicator) or CRI (CSI-RS Resource Indicator).

[0155] The DL BM process using SSB will be described below.

[0156] Figure 7 This is a diagram illustrating downlink beam management operations in a wireless communication system to which the present disclosure can be applied.

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

[0158] An Rx beam scan using an SSB can be performed simultaneously across multiple SSB bursts while the Rx beam targeting the same SSBRI is changed. In this case, an SS burst includes one or more SSBs, and an SS burst set includes one or more SSB bursts.

[0159] Figure 8 This is a diagram illustrating the downlink beam management process using SSB in a wireless communication system to which this disclosure may be applied.

[0160] In RRC connection state (or RRC connection mode), perform the configuration of beam reporting using SSB in CSI / beam configuration.

[0161] refer to Figure 8 The terminal receives from the base station a CSI-ResourceConfig IE (S410) which includes a CSI-SSB-ResourceSetList containing SSB resources used for BM.

[0162] Table 6 shows an example of a CSI-ResourceConfig IE, and as shown in Table 6, the BM configuration of the SSB is configured like a CSI-RS resource without needing to be defined separately.

[0163] [Table 6]

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

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

[0166] When the CSI-RS reportConfig related to the reporting of SSBRI and L1-RSRP is configured, the terminal performs a (beam) report to the base station for the optimal SSBRI and the corresponding L1-RSRP (S430).

[0167] The DL BM process using CSI-RS will be described below.

[0168] The use of CSI-RS is described as follows: i) Repetition parameters are configured for a specific CSI-RS resource set, and CSI-RS is used for beam management when TRS_info is not configured. ii) When repetition parameters are not configured and TRS_info is configured, CSI-RS is used for TRS (Tracking Reference Signal). iii) When repetition parameters are not configured and TRS_info is not configured, CSI-RS is used for CSI acquisition.

[0169] Such repeated parameters can be configured only for CSI-RS resource sets associated with CSI-ReportConfig that have L1 RSRP reports or "no reports (or none)".

[0170] If the terminal is configured with a CSI-ReportConfig where reportQuantity is configured as "ci-RSRP" or "none" and the CSI-ResourceConfig for channel measurement (higher-level parameter resourceForChannelMeasurement) does not include the higher-level parameter "trs-Info" and includes an NZP-CSI-RS-ResourceSet where the higher-level parameter "repeated" is configured, then the terminal may be configured with only the same number of ports (1-port or 2-port) with the higher-level parameter "nrofPorts" for all CSI-RS resources in the NZP-CSI-RS-ResourceSet.

[0171] When (higher-layer parameters) are repeatedly configured to "on", it is related to the terminal's Rx beam scanning process. At this time, when the terminal is configured with an NZP-CSI-RS-ResourceSet, the terminal can assume that it uses the same downlink spatial domain transmission filter to transmit at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet. In other words, 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 different OFDM symbols. Furthermore, the terminal does not expect to receive different periodicities in periodicityAndOffset among all CSI-RS resources in the NZP-CSI-RS-ResourceSet.

[0172] Meanwhile, when repetition is configured to "off," it is related to the base station's Tx beam scanning process. In this case, when repetition is configured to "off," the terminal does not assume that at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted in the same downlink spatial domain transmission filter. In other words, at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted via a different Tx beam.

[0173] In other words, when the reportQuantity of CSI-RS reportConfig IE is configured as "ssb-Index-RSRP", the terminal reports the best SSBRI and the corresponding L1-RSRP to the base station.

[0174] Additionally, when CSI-RS resources can be configured in the same OFDM symbol as SSB (SS / PBCH block) and "QCL-TypeD" applies, the terminal can assume that CSI-RS and SSB are quasi-co-located with respect to "QCL-TypeD".

[0175] Here, QCLTypeD can mean that the antenna ports are quasi-co-located with respect to the spatial Rx parameters. When a terminal receives multiple DL antenna ports with a QCLTypeD relationship, it allows them to apply the same Rx beam. Additionally, the terminal does not expect to configure CSI-RS in REs that overlap with the SSB's REs.

[0176] Figure 9 This is a diagram illustrating downlink beam management operation using CSI-RS in a wireless communication system to which this disclosure may be applied.

[0177] Figure 9 (a) represents the Rx beamforming (or refinement) process of the terminal, and Figure 9 (b) shows the Tx beam scanning process of the base station. Additionally, Figure 9 (a) is the case where the repeat parameter is configured to "on", and Figure 9 (b) is the case where the repeat parameter is configured to "off".

[0178] Figure 10 This is a diagram illustrating the Rx beam determination process of a terminal in a wireless communication system to which the present disclosure can be applied.

[0179] refer to Figure 9 (a) and Figure 10 This describes the Rx beam determination process of the terminal.

[0180] The terminal receives the NZP CSI-RS resource set IE (S610) from the base station via RRC signaling, which includes repetition of higher-level parameters. Here, the repetition parameter is configured to be "enabled".

[0181] The terminal repeatedly receives resources in the CSI-RS resource set that are configured to be repeatedly "on" in different OFDM symbols through the same Tx beam (or DL ​​spatial domain transmission filter) of the base station (S620).

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

[0183] The terminal omits the CSI report (S640). In this case, the reportQuantity of the CSI report configuration can be configured as "No report (or none)".

[0184] In other words, when a terminal is configured to repeatedly "on", it can omit CSI reports.

[0185] Figure 11 This is a diagram illustrating the Tx beam determination process of a base station in a wireless communication system to which the present disclosure can be applied.

[0186] refer to Figure 9 (b) and Figure 11 This describes the Tx beam determination process of a base station.

[0187] The terminal receives the NZP CSI-RS resource set IE (S710) from the base station via RRC signaling, which includes repetition of higher-level parameters. Here, the repetition parameter is configured to be "off" and is related to the base station's Tx beam scanning process.

[0188] The terminal receives resources from the CSI-RS resource set that is configured to be repeatedly "off" through different Tx beams (or DL ​​spatial domain transmission filters) of the base station (S720).

[0189] The terminal selects (or determines) the optimal beam (S740).

[0190] The terminal reports the selected beam ID and related quality information (e.g., L1-RSRP) to the base station (S740). In this case, the reportQuantity configured in the CSI report can be set to "CRI+L1-RSRP".

[0191] In other words, when sending CSI-RS for BM, the terminal reports CRI and the associated L1-RSRP.

[0192] Figure 12 This is a diagram illustrating the allocation of resources in the time and frequency domains related to downlink beam management operations in a wireless communication system to which this disclosure can be applied.

[0193] refer to Figure 12 This demonstrates that when the CSI-RS resource set is configured to be repeatedly "on", multiple CSI-RS resources are reused by applying the same Tx beam, and when the CSI-RS resource set is configured to be repeatedly "off", different CSI-RS resources are transmitted in different Tx beams.

[0194] The beam indication method associated with the downlink BM will be described below.

[0195] The terminal can be configured via RRC with a list of up to M candidate Transport Configuration Indicator (TCI) states, at least for the purpose of QCL (Quasi-Co-location) indication. Here, M can be 64.

[0196] Each TCI state can be configured as an RS set. Each ID of a DL RS for at least the spatial QCL purpose (QCLTypeD) in the RS set can refer to one of the DL RS types, such as SSB, P (periodic)-CSI RS, SP (semi-persistent)-CSI RS, A (aperiodic)-CSI RS, etc.

[0197] The ID of the DL RS in the RS set used for the purpose of the spatial QCL can be initialized / updated at least by explicit signaling.

[0198] Table 7 illustrates the TCI - Status Information Element (IE).

[0199] The TCI state IE is associated with a quasi-common address (QCL) type corresponding to one or two DL reference signals (RS).

[0200] [Table 7]

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

[0202] UE-initiated beam reporting method

[0203] In the current NR standard, beam reporting is supported as a form of CSI feedback, where the UE reports the L1-RSRP or L1-SINR value to the base station based on the measured power of the SSB or CSI-RS. Here, the base station pre-configures and notifies the UE of the UL resources and configurations used for beam reporting, and the UE reports the beam to the base station according to the corresponding configuration.

[0204] The following is a portion of the Working Item Description (WID) for Version-19 NR MIMO.

[0205] It is assumed that the Unified Transmission Configuration Indicator (TCI) enhancement is specified to utilize the legacy CSI Measurement and Reporting Configuration Framework, Target FR2, and Single Transmitter Receiver Point (sTRP) as much as possible through intra-cell and inter-cell beam management, and to facilitate UE-initiated / event-driven beam management in order to reduce overhead and / or latency.

[0206] - UL signaling content (and procedures, if necessary) for UE-initiated / event-driven beam reporting to facilitate fast beam switching.

[0207] - UL signal media / container designed primarily for beam reporting purposes, considering UE-initiated / event-driven characteristics of UL transmissions.

[0208] Therefore, in version 19, unlike existing methods, a scheme is being considered where a specific event for beam reporting is defined, and the UE determines whether the event has occurred and performs beam reporting only if the event has occurred. This can be referred to as UE-initiated beam reporting or event-driven beam reporting. In the following description of this disclosure, for ease of explanation, it will primarily be referred to as UE-initiated beam reporting; however, the method proposed in this disclosure is not limited to this name and may be referred to by another name.

[0209] In the following description of this disclosure, beam reports can be interpreted as a concept included in CSI reports (or a type of CSI report), and therefore, the UE can be configured for beam reporting via higher-layer signaling for CSI report configuration. Additionally, beam reports may include L1-RSRP reports and / or L1-SINR reports. The number of beam reports may refer to information reported to the base station via beam reports and may include, for example, i) the ID / index of the downlink reference signal (e.g., Channel State Information - Reference Signal Resource Indicator (CRI), Synchronization Signal Block (SSB) index), ii) the corresponding L1-RSRP or L1-SINR.

[0210] Furthermore, in the following description of this disclosure, the proposed method is primarily described in relation to beam reporting; however, the proposed method can be applied equally to other CSI reports (e.g., CRI, Rank Indicator (RI), Precoding Matrix Indicator (PMI), Channel Quality Indicator (CQI), etc.). In other words, when UE-initiated CSI reports are supported in addition to UE-initiated beam reporting, the proposed method described below can be applied in the same way.

[0211] In the following, this disclosure presents a UE-initiated beam reporting method.

[0212] Example 1: The UE can send the CSI report configuration identifier (ID) in the beam report initiated by the UE.

[0213] Table 9 illustrates the CSI reporting configuration defined in 3GPP TS 38.331.

[0214] [Table 8]

[0215] Referring to Table 8, configure a CSI report configuration ID for each CSI report, and configure it to indicate the type of CSI report to be reported (e.g., periodic CSI (P-CSI), semi-persistent CSI on PUCCH (SP-CSI), SP-CSI on PUSCH, or aperiodic CSI (AP-CSI)).

[0216] In addition, in the case of beam reports initiated by the UE, RRC parameters can be configured separately, as shown in Table 9 below.

[0217] [Table 9]

[0218] Referring to Table 9, additional RRC parameters (e.g., reportSlotOffsetList) for configuring the timing of beam reports initiated by the UE and RRC parameters (e.g., pucch-CSI-ResourceList) for configuring the PUCCH resources through which UE-initiated beam reports are sent can be configured.

[0219] The base station can configure the report configuration type for the UE to be one or more CSI report configurations initiated by the UE, and can configure different events for the corresponding CSI reports (i.e., for the corresponding CSI report configurations). Alternatively, a common event can be configured for all CSI reports (i.e., CSI report configurations). Alternatively, a common event can be configured for each of some groups among all CSI reports (i.e., CSI report configurations).

[0220] For example, the base station can configure CSI report configurations 1, 2, and 3 for UE-initiated beam reports via RRC signaling (i.e., CSI report configuration IDs = 1, 2, and 3). Additionally, specific CSI reports can be activated by the base station via dynamic signaling such as MAC Control Elements (MAC CEs) or Downlink Control Information (DCIs). 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) the event conditions for each activated CSI report. When the event conditions for a specific CSI report are met, the UE can perform beam reporting for the corresponding CSI report. For example, the number of beam reports (or beam reports) can include i) the ID / index of the UE's preferred downlink reference signal (e.g., CRI, SSB index) and ii) the corresponding L1-RSRP or L1-SINR.

[0221] Here, the UE can report the CSI report configuration ID to the base station to report (or indicate) which CSI report to perform beam reporting for. For example, the CSI report configuration ID can be reported together with the number of beam reports (e.g., CRI, SSB index, L1-RSRP, or L1-SINR), or it can be reported separately before reporting the number of beam reports.

[0222] Example 2: The UE can send the number of beam reports (e.g., i) downlink reference signal ID / index (CRI, SSB index, etc.) and ii) L1-RSRP or L1-SINR to the base station through the uplink channel (e.g., PUCCH or PUSCH) used for UE-initiated beam reports.

[0223] Here, the uplink channel for UE-initiated beam reports can be pre-secured / configured from the base station.

[0224] - For example, ensuring / configuring uplink channels in advance from the base station for beam reports initiated by the UE can mean that the UE can use the corresponding uplink channels, such as Configuration Grant (CG) PUSCH or Scheduling Request (SR) PUCCH, as needed. Alternatively, this can mean that the UE can use the corresponding uplink channels as needed in a state where periodic (P) or semi-persistent (SP) PUCCH resources are periodically or semi-persistently allocated.

[0225] In this scenario, the UE can initiate a beam report to the base station for a CSI report that meets the event conditions via CG PUSCH, SR PUCCH, or P / SP PUCCH. In other words, the UE can send the number of beam reports to the base station for a CSI report that meets the event conditions via CG PUSCH, SR PUCCH, or P / SP PUCCH.

[0226] - Alternatively, as another example, the fact that the base station pre-secures / configures the uplink channel for UE-initiated beam reports can mean a situation where the UE requests the uplink channel for UE-initiated beam reports from the base station and configures / allocates the uplink PUSCH via DCI for uplink scheduling.

[0227] Here, the SR (Schedule Request) PUCCH transmission can be used to request an uplink channel. That is, the UE can request a UL channel from the base station for a UE-initiated beam report by using the SR PUCCH to report a CSI that satisfies an event condition. For example, while legacy SR PUCCHs only indicate whether a scheduling request for an uplink transport block (TB) exists, the SR PUCCH for a UE-initiated beam report according to this disclosure may additionally indicate whether a scheduling request for a beam report exists. For this purpose, the base station can configure the SR PUCCH for the UE to indicate whether it is for i) a scheduling request for a TB, ii) a scheduling request for a beam report, or iii) a scheduling request for both TB and beam reports. Here, when the corresponding SR PUCCH is for both TB and beam reports (BR), the UE can use 2-bit information to distinguish four cases to request from the base station: i) TB+BR, ii) TB, iii) BR, and iv) no.

[0228] Meanwhile, the operations of Embodiment 1 and Embodiment 2 described above can be applied together, and accordingly, when the uplink channel for beam reports initiated by the UE is secured / configured in advance from the base station, the UE can send the CSI report configuration ID together with the number of beam reports (e.g., i) downlink reference signal ID / index (CRI, SSB index, etc.) and ii) L1-RSRP or L1-SINR).

[0229] Here, the encoding order of the CSI report configuration ID can be before or after the beam report number. For example, since the CSI report configuration ID is information that needs to be known before interpreting the beam report number, placing the CSI report configuration ID before the beam report number may be advantageous for decoding implementation at the receiver and for the bit sequence parsing scheme. Alternatively, by placing the CSI report configuration ID after the beam report number, the transmitting side can utilize existing legacy bit sequence concatenation, and the CSI report configuration ID can be appended only at the end.

[0230] CSI can be configured to include part 1 CSI and part 2 CSI, and the CSI report configuration ID can be configured to be included in part 1 CSI.

[0231] In existing beam reporting processes, the number of beam reports is configured as part 1 CSI. However, in the case of UE-initiated beam reporting according to this disclosure, since the number of beam reports and the payload size of the number of beam reports can vary depending on the CSI reporting configuration, the number of beam reports can be configured to be included in part 2 CSI.

[0232] Alternatively, to avoid variations in the number of beam reports and the payload size of the beam reports based on the CSI report configuration, the UE can expect that the number of beam reports and the payload size of the beam reports in the CSI report configuration used for UE-initiated beam reports will be configured to be the same (i.e., can be configured identically). To this end, the UE can expect that the number of CSI-RS / SSBs and the number of reports corresponding to the Channel Measurement Resources (CMR) subjected to channel measurements for each CSI report configuration will be configured to be the same (i.e., can be configured identically).

[0233] As another example, beam reporting for multiple CSI report configurations can be performed together in the UE's CSI report configuration ID / beam report quantity report. In this case, the UE can perform reporting by placing the CSI report configuration ID / beam report quantity for a specific CSI report configuration that includes the CRI (or SSB index) with the best quality (e.g., the highest L1-RSRP / SINR value) before the report payload. Here, the L1-RSRP / SINR value associated with / related to the CRI (or SSB index) with the best quality within the corresponding specific CSI report configuration can be reported as an absolute value (e.g., represented by 7 bits). Furthermore, L1-RSRP / SINR values ​​associated with / related to other CRIs (or SSB indices) within the corresponding specific CSI report configuration, or with CRIs (or SSB indices) related to / related to CSI report configurations other than the corresponding specific CSI report configuration, can be reported as differential values ​​(e.g., represented by 4 bits).

[0234] For example, suppose CSI report configurations 1, 2, and 3 are configured, and CRIs 1 and 2, CRIs 3 and 4, and CRIs 5 and 6 are configured within each CSI report configuration. Here, if CRI 4 within CSI report configuration 2 is measured using the highest L1-RSRP / SINR value, then CSI report configuration 2 is initially within the report payload, and the L1-RSRP / SINR value associated with CRI 4 can be reported as an absolute value (e.g., represented by 7 bits), while the L1-RSRP / SINR values ​​associated with the remaining CRIs can be reported as differential values ​​(e.g., represented by 4 bits). Through this corresponding operation, the CSI report payload can be saved as the number of bits representing the L1-RSRP / SINR value for each CRI is reduced.

[0235] Furthermore, in the example above, the number of bits representing CRIs can be determined by: i) performing a local index based on the number of CRIs in each CSI report across multiple CSI report configurations (specifically for each CSI report configuration), or ii) performing a local index based on the total number of CRIs included in multiple CSI report configurations (across multiple CSI report configurations).

[0236] Regarding local indexing, Method i considers determining the number of bits representing the CRI in each reporting configuration, similar to deriving the CRI for each sub-configuration in Network Energy Saving (NES), and Method ii considers determining the number of bits representing the CRI from the total number of CRIs across multiple CSI reporting configurations. For example, suppose CSI reporting configurations #1, #2, and #3 include 2, 3, and 3 CMRs, respectively. In this case, in Method i, by considering the number of CRIs included in each reporting configuration (= the number of CSI-RS or SSB candidates as CRIs), the CRI representation for reporting configurations #1, #2, and #3 might require 1 bit, 2 bits, and 2 bits, respectively. In Method ii, by considering the total number of CRIs across all reporting configurations, 3 bits might be required. Here, in Method i, the CSI reporting configuration ID should be included in the report content used for the CRI representation for each CSI reporting configuration, while in Method ii, the CSI reporting configuration ID does not need to be included.

[0237] Example 3: After the uplink transmission related to the UE initiating a beam report, the UE can send the number of beam reports (e.g., i) downlink reference signal ID / index (CRI, SSB index, etc.), ii) L1-RSRP or L1-SINR to the base station through the uplink channel (e.g., PUCCH or PUSCH) used for the UE to initiate the beam report.

[0238] For example, uplink transmissions associated with a beam report initiated by a UE can correspond to uplink transmissions used to request uplink channels (or multiple uplink channel resources) from a base station for a beam report initiated by a UE.

[0239] For this purpose, SR (Schedule Request) PUCCH transmission can be used. That is, the UE can request the UL channel for beam reporting initiated by the UE from the base station by using SR PUCCH for CSI reporting that meets event conditions.

[0240] Furthermore, the operations of Embodiment 1 and Embodiment 2 described above can be applied together, and when the UE requests an uplink channel from the base station for a UE-initiated beam report, the CSI report configuration ID can be reported via a request message before the beam report quantity is reported.

[0241] For example, when using legacy schemes, because up to 2 bits of information can be carried on an SR PUCCH, an uplink channel (or uplink channel resource) can be requested for up to one of four CSI report configuration IDs via SR PUCCH. Alternatively, a RACH (Random Access Channel) transmission can be used to request an uplink channel. In this case, the CSI report configuration ID can be mapped one-to-one to a specific SSB index, or the CSI report configuration ID can be included in the RACH message.

[0242] And / or, when using the legacy scheme, since the information that can be carried on the SR PUCCH is up to 2 bits, when up to four CMRs exist within a specific CSI reporting configuration (or its associated set of CMRs) for a UE-initiated beam report, the reporting indicating that one of the four CMRs has a good L1-RSRP / SINR value can be performed solely via the SR-PUCCH transmission. That is, a specific CMR within a specific CSI reporting configuration can be reported (e.g., via CRI) instead of sending the specific CSI reporting configuration ID via the SR PUCCH. In this case, i) the beam report including the L1-RSRP / SINR value of the CRI reported via the corresponding SR-PUCCH can then be reported via a scheduled PUSCH transmission, or ii) the PUSCH transmission associated with the CSI report can be omitted without any subsequent reporting.

[0243] As another example, when the UE determines the UL channel / resource for a UE-initiated beam report and notifies its base station, it can include and report the CSI report configuration ID in the notification message before reporting the number of beam reports. That is, when an event occurs, the UE can include and report the CSI report configuration ID in the corresponding notification message, and thereafter the UE can report the number of beam reports corresponding to the CSI report configuration ID on the uplink resources indicated by the notification message. Such a notification message can be sent, for example, using a CG PUSCH, and can include CSI report configuration ID information and CSI report time information (e.g., timeslot, start symbol, or duration). For example, the PUCCH resource configured within the corresponding CSI report configuration can be identified by the CSI report configuration ID in the notification message (see Table 9), and the transmission timeslot information of the PUCCH resource can be identified by the CSI report time information (see Embodiment 4, described later). Here, because the start symbol, symbol duration, and resource block (RB) information for the PUCCH resource are pre-configured, the base station and the UE (e.g., UE A) can know the UL frequency-time resource information. When a PUCCH resource conflicts with a PUSCH resource already configured by the base station for another UE (e.g., UE B), the base station can notify UE B to cancel the corresponding PUSCH resource via a cancellation indication. Furthermore, to prevent conflicts with uplink channels allocated to another UE in advance, the base station can notify UE A in advance of impossible uplink transmission resource information, and UE A can determine the UL resource while avoiding the corresponding resource.

[0244] As another example, the uplink transmission associated with a beam report initiated by the UE can correspond to an uplink transmission used to notify the base station that an event has occurred (has been satisfied). In this case, the base station can autonomously determine whether to schedule the uplink channel for the beam report initiated by the UE.

[0245] Subsequently, the UE can send beam report numbers (e.g., i) downlink reference signal IDs / indexes (CRI, SSB index, etc.), ii) L1-RSRP or L1-SINR to the base station through uplink channels (e.g., PUCCH, PUSCH) used for UE-initiated beam reports.

[0246] Here, the operations based on Embodiment 2 and Embodiment 3 are applied together. The UE can send an uplink transmission to the base station to notify that an event related to the beam report initiated by the UE has occurred (has been satisfied). The UE can also send the number of beam reports (e.g., i) downlink reference signal ID / index (CRI, SSB index, etc.), ii) L1-RSRP or L1-SINR to the base station through a pre-secured / configured uplink channel.

[0247] Meanwhile, in embodiments 1-3 above, the scheme of configuring different CSI report configurations for the UE for each beam report has been mainly described. However, unlike this, beam reports can be defined / configured within a single CSI report configuration. In this case, beam reports share a single CSI report configuration ID, and beam reports can be distinguished when sub-configurations are configured within the CSI report configuration. For example, beam reports 1, 2, and 3 can be configured by configuring sub-configurations 1, 2, and 3, and for each sub-configuration, independent CMRs (and / or Interference Measurement Resources (IMRs)) and event conditions can be configured. For example, such sub-configurations can be configured in the form of CMR (and / or IMR) sets. In this case, the CMRs corresponding to beam reports 1, 2, and 3 can be configured by configuring CMR sets 1, 2, and 3 within the CSI report configuration. In such a structure, the UE can notify the base station about which beam report is being reported by reporting the sub-configuration ID or the CMR (and / or IMR) set ID instead of the CSI report configuration ID in embodiments 1-3 above.

[0248] In other words, when introducing a subconfiguration ID or a CMR (and / or IMR) set ID, embodiments 1 to 3 can be applied by replacing the CSI report configuration ID with the subconfiguration ID or the CMR (and / or IMR) set ID.

[0249] Furthermore, in embodiments 1 to 3 above, the reporting scheme of CSI report configuration ID can also be applied to event ID reporting. That is, multiple events related to the beam report initiated by the UE can be configured for the UE, and during the beam report initiated by the UE, the UE can report to the base station which event the beam report corresponds to.

[0250] For example, when multiple different events are defined within the same CSI resource configuration and CSI report configuration, an event ID can be defined for each event. The UE can report to the base station which event satisfies a beam report initiated by the UE. For example, event 1 can be defined as reporting a beam for which its RSRP exceeds the CMR of the beam report used for the UE-initiated beam report by more than 20 dB, and event 2 can be defined as reporting a beam for which its received power exceeds the CMR of the beam report used for the UE-initiated beam report by more than 10 dB from the beam currently used for DL / UL reception. In this case, the UE can further report to the base station which event triggered the beam report.

[0251] Meanwhile, in the above embodiments 1-3, ID can be interpreted as having the same meaning as index.

[0252] Furthermore, the reporting scheme for the CSI report configuration ID described in Embodiments 1 to 3 above can also be applied to the reporting of the CRI / SSB index in the same way. For example, when configuring a CSI report for a beam report initiated by the UE, the UE does not need to report the CSI report configuration ID, but can utilize the scheme described in Embodiments 1 to 3 above to report the CRI / SSB index among the corresponding number of CSI reports.

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

[0254] Here, the beam reporting time (i.e., CSI reporting time) for the beam report initiated by the UE can be determined as the offset from the time point of the uplink transmission for the (UE-initiated) beam report.

[0255] When the UE sends an uplink transmission to the base station for a (UE-initiated) beam report (e.g., a request for uplink scheduling), and / or when the UE determines the uplink channel / resource for the (UE-initiated) beam report and notifies its base station, the UE can report CSI report timing information to the base station. For example, CSI report timing information can be reported using the transmission scheme of the CSI report configuration ID in Example 3.

[0256] Compared to Embodiment 3 described above, when sending an uplink transmission to the base station for a (UE-initiated) beam report (e.g., a request for uplink scheduling), the UE can send the report time information for the corresponding beam report by including it in the uplink transmission.

[0257] The reporting time information can be about the time point at which the UE performs beam reporting (e.g., time slot, start symbol, symbol duration, etc.), and in such cases, the UE can autonomously determine the reporting time and report it to the base station. Furthermore, the reporting time can be expressed as an offset based on the request time, as described later.

[0258] Alternatively, the reporting time information can indicate the duration during which beam reporting is to be performed. Considering the time variations of the channel, the UE can predict the duration during which the corresponding beam report will not become outdated (or that the beam report is valid / meaningful), and the base station can perform uplink scheduling to ensure that beam reporting is performed within the corresponding duration. For example, the reporting time information can be configured as an offset relative to the request time (i.e., the transmission time point for the uplink transmission of the (UE-initiated) beam report). In this case, assuming the request time (i.e., the transmission time point for the uplink transmission of the (UE-initiated) beam report) is time slot n, the base station can perform uplink scheduling with a reporting offset k to ensure that beam reporting is performed within time slot n+k (i.e., in time slot n+k or earlier). If the base station performs uplink scheduling to ensure that beam reporting is performed after time slot n+k, the UE can ignore the corresponding scheduling, or even if the UE performs beam reporting according to the corresponding scheduling, the validity of the corresponding beam information cannot be guaranteed. Alternatively, the UE may expect the base station to perform uplink scheduling so that beam reporting is performed within time slot n+k (or, the UE may not expect the base station to perform uplink scheduling so that beam reporting is performed after time slot n+k).

[0259] For offset k, the offset candidate values ​​can be configured by the base station for the UE, such as the report slot offset list illustrated in Table 9 (e.g., reportSlotOffsetList), and the UE can determine k as one of these values ​​and report it to the base station.

[0260] Furthermore, compared to Embodiment 2 above, when the UE determines the uplink channel / resource for the (UE-initiated) beam report and notifies its base station, the reporting time information can be the time point at which the UE performs the beam report (e.g., time slot, start symbol, symbol duration, etc.). In this case, the UE can autonomously determine the reporting time and report it to the base station. Additionally, the reporting time can be expressed as an offset based on the request time (i.e., the transmission time point of the uplink transmission for the (UE-initiated) beam report), as described above.

[0261] Furthermore, the reporting time can be interpreted as the "valid time of the event," which can be determined not only by the time variation of the channel but also by the measurement window / method (e.g., whether L3 filtering is applied). With this in mind, in addition to the method by which the UE reports the reporting time, the reporting time can also be predefined (in the standard) or configured by the base station.

[0262] Furthermore, in this case, as described above, for example, the reporting time can be configured as an offset relative to the transmission time of the uplink transmission used for the beam report initiated by the UE. For example, since the offset candidate value is configured as a single value, the offset k can be configured by the base station for the UE, similar to the report slot offset list illustrated in Table 9 (e.g., reportSlotOffsetList).

[0263] In addition, the reporting time can be predefined (in the standard) or configured by the base station for each event (or for each event type).

[0264] Example 5: Counting method for the number of activated (active) CSI-RS resources and the number of activated ports in NZP CSI-RS configuration for beam reporting initiated by UE

[0265] Table 10 is described in section 2.1.6 of TS 38.214 as follows.

[0266] [Table 10]

[0267] The UE can count the NZP CSI-RS resources of the CSI report configured for the beam report initiated by the UE as the activated resources from the time the corresponding CSI report is activated to the time it is disabled, and can count the number of ports of the corresponding resources as the number of activated ports.

[0268] For example, the base station can configure CSI report configurations 1, 2, and 3 for the UE in response to beam reports initiated by the UE (i.e., CSI report configuration IDs = 1, 2, and 3), and can activate specific CSI reports via dynamic signaling such as MAC-CE / DCI (or, the RRC configuration itself can be used / treated as active without a separate activation indication). The UE can count the CSI-RS resources / ports configured in each activated CSI report as activated resources / ports until they are disabled via dynamic signaling such as MAC-CE / DCI or until an RRC release is performed.

[0269] Here, unlike traditional CSI reporting, the above CSI reporting configurations 1, 2, and 3 are reported based on events, so even if they are activated, reporting may not be performed. However, because the UE needs to measure the corresponding NZP CSI-RS to monitor event conditions, the UE can count the corresponding NZP CSI-RS as the activated resource / port, regardless of whether reporting is performed.

[0270] Considering this operational difference, the active CSI-RS resources / ports used for UE-initiated beam reports can be counted separately from the conventional active CSI-RS resources / ports. Therefore, when reporting UE capabilities, the UE can separately distinguish and report to the base station the maximum number of existing supported active CSI-RS resources / ports and the maximum number of active CSI-RS resources / ports that can be supported for UE-initiated beam reports.

[0271] Figure 13 This is a diagram illustrating the signaling process between a base station and a UE for a UE-initiated beam reporting method according to an embodiment of the present disclosure.

[0272] Figure 13 An example is given of the signaling process between the UE and the base station based on the method proposed in Examples 1 to 5 above. Figure 13 Examples are provided for ease of description and do not limit the scope of this disclosure. Depending on the situation and / or configuration, examples may be omitted. Figure 13 Some steps are illustrated in the example. Furthermore, in Figure 13 In this example, the base station and UE are just one example, and can be derived from the following: Figure 16 The device illustrated in the example is used to implement this. For example, Figure 16 The processor (102 / 202) can control the transmission / reception of channels / signals / data / information, etc. by using transceivers (106 / 206), and can also control the storage of channels / signals / data / information, etc. to be transmitted or received in memory (104 / 204).

[0273] refer to Figure 13 The base station sends configuration information to the UE (S1301).

[0274] Here, configuration information may refer to configuration information related to beam reports initiated by the UE or event-driven beam reports.

[0275] Here, a beam (or beam RS or RS) can refer to a beam-shaped RS (e.g., SSB, CSI-RS, etc.). Furthermore, a beam (or beam RS or RS) can have different directions of transmission to its respective resources, and different resources through which a beam-shaped RS is transmitted can refer to different beams (or beam RS or RS).

[0276] Furthermore, configuration information can refer to configuration information relating to one or more parameters 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 CSI reporting (e.g., CSI-ReportConfig including (L1-RSRP and / or L1-SINR))), configuration information related to resources used 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 status).

[0277] In addition, the configuration information may include information about events (or determination criteria) used to determine whether the UE performs an initiated / event-driven beam reporting. Such events (or determination criteria / standards) may be configured one for each CSI report, or multiple such criteria may be configured within a single CSI report.

[0278] although Figure 13 Although not shown in the diagram, the base station can send control information to the UE.

[0279] Here, control information may refer to information used to activate and / or guide a beam (or beam RS or RS) (i.e., QCL type-DRS (or TCI state)). Alternatively, it may refer to control information used to activate / trigger beam reporting (e.g., L1-RSRP / SINR) to assist in selecting the base station's Tx beam (or beam RS or RS) and / or the UE's Rx beam (or beam RS or RS). Such control information may be transmitted via MAC CE, via DCI, or via both MAC CE and DCI.

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

[0281] As mentioned above, a beam (or beam RS or RS) can refer to a beamforming reference signal (e.g., SSB, CSI-RS, etc.). Additionally, depending on the resource being transmitted to, a beam (or beam RS or RS) can have different directions, and different resources to which a beamforming RS is transmitted can refer to different beams (or beam RS or RS).

[0282] In other words, the base station can send downlink RS to the UE through different beams on one or more downlink RS resources.

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

[0284] Here, when an event configured through the configuration information is met, a UE-initiated / event-driven beam report can be executed.

[0285] Here, based on the event associated with the initiated / event-driven beam report, the UE can send a first uplink transmission to the base station, and subsequently, the UE can send a second uplink transmission to the base station containing a report value derived from the downlink reference signal. Here, the report value can be i) a pair of the identifier of the reference signal resource (e.g., CRI, SSBRI) and L1-RSRP, or ii) a pair of the identifier of the reference signal resource and L1-SNIR.

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

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

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

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

[0290] Alternatively, based on configuring multiple CSI reports for the UE, the second uplink transmission can include multiple report values ​​for the multiple CSI reports. In this case, for multiple CSI reports, the highest report value can be located first, reported as an absolute value, and the remaining report values ​​can be reported as differences from the highest report value.

[0291] Additionally, based on configuring multiple events for the UE (e.g., for a single 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.

[0292] Furthermore, the transmission time of the second uplink transmission can be determined as an offset from the transmission time of the first uplink transmission. For example, the transmission time of the second uplink transmission can be determined by the UE and included in the first uplink transmission. Alternatively, the transmission time of the second uplink transmission can be predefined or configured by the base station. For example, one or more offset candidates for the transmission time of the second uplink transmission can be configured for the UE, and the offset can be determined based on one or more offset candidates.

[0293] Figure 14 This is a diagram illustrating the operation of a UE for reporting channel state information according to an embodiment of the present disclosure.

[0294] Figure 14 The illustration shows the operation of a UE based on the methods proposed in Examples 1 to 5 above. Figure 14 The examples in this document are for illustrative purposes only and are not intended to limit the scope of this disclosure. Depending on the situation and / or configuration, some examples may be omitted. Figure 14 Some steps are illustrated in the diagram. Furthermore... Figure 14 The UE in the example is just that, and can be implemented as follows Figure 16 The device illustrated in the image. For example... Figure 16 The processor (102 / 202) can use the transceiver (106 / 206) to control the transmission and reception of channels / signals / data / information, etc., and can also control the storage of channels / signals / data / information, etc. to be transmitted or received in the memory (104 / 204).

[0295] in addition, Figure 14 The operation can be performed by Figure 16 It is processed by one or more processors (102, 202). Additionally, Figure 14 The operation can be used to drive Figure 16 The instructions / program (e.g., instructions, executable code) of at least one processor (e.g., 102, 202) are stored in memory (e.g., Figure 16 In one or more memories (104, 204).

[0296] refer to Figure 14 The UE receives configuration information related to the CSI report from the base station (S1401).

[0297] Here, the CSI report may include beam reports (e.g., L1-RSRP and / or L1-SINR), and the configuration information associated with the CSI report (e.g., CSI-ReportConfig) may correspond to... Figure 13 An example of configuration information in [the system / system].

[0298] Additionally, configuration information related to CSI reports may include information about events (or criteria) used to determine whether the UE will perform an initiated / event-driven beam report. These events (or criteria) may be configured one per CSI report, or multiple within a single CSI report.

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

[0300] As mentioned above, a beam (or beam RS or RS) can refer to a beamforming reference signal (e.g., SSB, CSI-RS, etc.). Additionally, depending on the resource being transmitted to, a beam (or beam RS or RS) can have different directions, and different resources to which a beamforming RS is transmitted can refer to different beams (or beam RS or RS).

[0301] In other words, it is possible to transmit downlink RS through one or more different beams from the RS resources above.

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

[0303] Based on the fulfillment of the event related to the CSI report, the UE sends the first uplink transmission to the base station (S1403).

[0304] In other words, when an event configured by the configuration information associated with the CSI report is met, a UE-initiated / event-driven beam report can be executed.

[0305] Here, the first uplink transmission can be an uplink transmission notifying that an event has been satisfied. For example, the first uplink transmission can be sent via PUCCH. As another example, the notification that an event has been satisfied can be sent using the transmission method for a schedule request (SR).

[0306] The UE sends 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).

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

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

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

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

[0311] Alternatively, based on configuring multiple CSI reports for the UE, the second uplink transmission can include multiple report values ​​for the multiple CSI reports. In this case, for multiple CSI reports, the highest report value can be located first, reported as an absolute value, and the remaining report values ​​can be reported as differences from the highest report value.

[0312] Additionally, based on configuring multiple events for the UE (e.g., for a single 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.

[0313] Furthermore, the transmission time of the second uplink transmission can be determined as an offset from the transmission time of the first uplink transmission. For example, the transmission time of the second uplink transmission can be determined by the UE and included in the first uplink transmission. Alternatively, the transmission time of the second uplink transmission can be predefined or configured by the base station. For example, one or more offset candidates for the transmission time of the second uplink transmission can be configured for the UE, and the offset can be determined based on one or more offset candidates.

[0314] Figure 15 This is a diagram illustrating the operation of a base station for reporting channel state information according to an embodiment of the present disclosure.

[0315] Figure 15 The illustration shows the operation of a base station based on the method proposed in embodiments 1 to 5 above. Figure 15 The examples in this document are for illustrative purposes only and are not intended to limit the scope of this disclosure. Depending on the situation and / or configuration, some examples may be omitted. Figure 15 Some steps are illustrated in the diagram. Furthermore... Figure 15 The base station in the example is just that—an example—and can be implemented as follows: Figure 16 The device illustrated in the image. For example... Figure 16 The processor (102 / 202) can use the transceiver (106 / 206) to control the transmission and reception of channels / signals / data / information, etc., and can also control the storage of channels / signals / data / information, etc. to be transmitted or received in the memory (104 / 204).

[0316] in addition, Figure 15 The operation can be performed by Figure 16 One or more processors (102, 202) process it. Additionally, Figure 15The operation can be used to drive Figure 16 The instructions / program (e.g., instructions, executable code) of at least one processor (e.g., 102, 202) are stored in memory (e.g., Figure 16 In one or more memories (104, 204).

[0317] refer to Figure 15 The base station sends configuration information related to the CSI report to the UE (S1501).

[0318] Here, the CSI report may include beam reports (e.g., L1-RSRP and / or L1-SINR), and the configuration information associated with the CSI report (e.g., CSI-ReportConfig) may correspond to... Figure 13 An example of configuration information in [the system / system].

[0319] Additionally, configuration information related to CSI reports may include information about events (or criteria) used to determine whether the UE will perform an initiated / event-driven beam report. These events (or criteria) may be configured one per CSI report, or multiple within a single CSI report.

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

[0321] As mentioned above, a beam (or beam RS or RS) can refer to a beamforming reference signal (e.g., SSB, CSI-RS, etc.). Furthermore, depending on the resource being transmitted, the beam (or beam RS or RS) can have different directions, and different resources to which the beamforming RS is transmitted can refer to different beams (or beam RS or RS).

[0322] In other words, it is possible to transmit downlink RS through different beams from one or more of the aforementioned RS resources.

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

[0324] Based on the events related to the CSI report, the base station receives the first uplink transmission from the UE (S1503).

[0325] In other words, when an event configured by the configuration information associated with the CSI report is met, a UE-initiated / event-driven beam report can be executed.

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

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

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

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

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

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

[0332] Alternatively, based on configuring multiple CSI reports for the UE, the second uplink transmission can include multiple report values ​​for the multiple CSI reports. In this case, for multiple CSI reports, the highest report value can be located first, reported as an absolute value, and the remaining report values ​​can be reported as differences from the highest report value.

[0333] Additionally, based on configuring multiple events for the UE (e.g., for a single 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.

[0334] Furthermore, the transmission time of the second uplink transmission can be determined as an offset from the transmission time of the first uplink transmission. For example, the transmission time of the second uplink transmission can be determined by the UE and included in the first uplink transmission. Alternatively, the transmission time of the second uplink transmission can be predefined or configured by the base station. For example, one or more offset candidates for the transmission time of the second uplink transmission can be configured for the UE, and the offset can be determined based on one or more offset candidates.

[0335] The general-purpose devices disclosed herein can be used.

[0336] Figure 16This is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure.

[0337] refer to Figure 16 The first wireless device 100 and the second wireless device 200 can transmit and receive wireless signals through various radio access technologies (e.g., LTE, NR).

[0338] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may additionally include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor 102 may transmit a wireless signal including the first information / signal via the transceiver 106 after generating first information / signal by processing information in the memory 104. Furthermore, the processor 102 may receive a wireless signal including a second information / signal via the transceiver 106, and then store information obtained through 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 relating to the operation of the processor 102. For example, the memory 104 may store software code including commands for performing all or part of the processes controlled by the processor 102 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). Transceiver 106 may be connected to processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used with an RF (radio frequency) unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0339] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may additionally include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure. For example, the processor 202 may generate third information / signals by processing information in the memory 204, and then transmit a wireless signal including the third information / signals via the transceiver 206. Additionally, the processor 202 may receive wireless signals including fourth information / signals via the transceiver 206, and then store information obtained through 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 store software code including commands for executing all or part of the processes controlled by the processor 202 or for executing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). Transceiver 206 may be connected to processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used with an RF unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0340] The hardware components of wireless devices 100 and 200 will be described in more detail below. However, they are not limited to this; one or more protocol layers may be implemented by one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102 and 202 may generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, processes, proposals, and / or methods disclosed in this disclosure to provide them to one or more transceivers 106 and 206. One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206 and obtain PDUs, SDUs, messages, control information, data, or information in accordance with the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure.

[0341] One or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. In examples, one or more ASICs (Application-Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field-Programmable Gate Arrays) may be included in one or more processors 102, 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, etc. Firmware or software configured to perform the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure may be included in one or more processors 102, 202 or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this invention may be implemented by firmware or software in the form of code, commands, and / or command sets.

[0342] One or more memories 104, 204 may be connected to one or more processors 102, 202 and are capable of storing data, signals, messages, information, programs, code, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard disk drive, registers, digital memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located internally and / or externally to one or more processors 102, 202. Furthermore, one or more memories 104, 204 may be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0343] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or operation flowcharts, etc., disclosed herein to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein 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. Furthermore, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein through one or more antennas 108, 208. In this invention, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may process the received wireless signals / channels, etc., by converting them from RF band signals to baseband signals using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, wireless signals / channels, etc., processed by using one or more processors 102, 202 from baseband signals to RF band signals. Therefore, the one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0344] The above embodiments combine the elements and features of this disclosure in a predetermined form. Unless otherwise expressly stated, each element or feature should be considered optional. Each element or feature can be implemented without combination with other elements or features. Furthermore, embodiments of this disclosure may include combinations of certain elements and / or features. The order of operations described in the embodiments of this disclosure may be changed. Some elements or features of one embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. It is clear that embodiments may include combinations of claims where there is no explicit dependency in the claims, or may be included as new claims by amendment after the application.

[0345] It will be apparent to those skilled in the art that this disclosure may be practiced in other specific forms without departing from the essential characteristics of this disclosure. Therefore, the foregoing detailed description should not be construed as restrictive in every respect, but rather as illustrative. The scope of the invention should be determined by a reasonable interpretation of the appended claims, and all variations within the equivalent scope of this disclosure are included within the scope of the invention.

[0346] The scope of this disclosure includes software or machine-executable commands (e.g., operating systems, applications, firmware, programs, etc.) that operate in a device or computer according to methods of various embodiments, and non-transitory computer-readable media that store such software or commands and can be executed in a device or computer. Commands that can be used to program a processing system to perform the features described in this disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in this disclosure can be implemented using a computer program product including such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, and may include non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory may optionally include one or more storage devices located remote from the processor. Alternatively, the non-volatile memory devices in the memory may include non-transitory computer-readable storage media. The features described in this disclosure can be stored in any machine-readable medium to control the hardware of a processing system and can be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using results from embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0347] The wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may include narrowband Internet of Things (IoT) for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the aforementioned names. Alternatively, the wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may perform communication based on LTE-M technology. Here, in examples, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (Enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least any of the following standards: 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 aforementioned names. Alternatively, the wireless communication technology implemented in the wireless devices 100 and 200 of this disclosure may include at least any one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and it is not limited to the aforementioned names. In the example, ZigBee technology can generate a PAN (Personal Area Network) associated with small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0348] Industrial availability

[0349] The method proposed in this invention is mainly described using 3GPP LTE / LTE-A and 5G systems as examples, but it can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method comprising: The user equipment (UE) receives configuration information related to the channel state information (CSI) report from the base station; The UE receives downlink RS from the base station on one or more reference signal (RS) resources; Based on the fulfillment of the event related to the CSI report, the UE sends a first uplink transmission to the base station; as well as The UE sends a second uplink transmission to the base station, including a report value derived from the downlink RS.

2. The method according to claim 1, wherein, The first uplink transmission is an uplink transmission that notifies that the event has been satisfied.

3. The method according to claim 1, wherein, The first uplink transmission is performed via the Physical Uplink Control Channel (PUCCH).

4. The method according to claim 2, wherein, The notification that the event has been satisfied applies the transmission scheme for the scheduling request (SR).

5. The method according to claim 1, wherein, The second uplink transport is performed by configuring a licensed (CG) physical uplink shared channel (PUSCH).

6. The method according to claim 1, wherein, The second uplink transmission is performed via the Physical Uplink Shared Channel (PUSCH) scheduled by the base station.

7. The method according to claim 1, wherein, Based on configuring multiple CSI reports for the UE, the first uplink transmission or the second uplink transmission includes information indicating which of the multiple CSI reports the report value is associated with.

8. The method according to claim 1, wherein, Based on configuring multiple CSI reports for the UE, the second uplink transmission includes multiple report values ​​for the multiple CSI reports.

9. The method according to claim 8, wherein, For the multiple CSI reports, the highest reported value is listed first. The highest reported value is reported as an absolute value, and the remaining reported values ​​are reported as differences relative to the highest reported value.

10. The method according to claim 1, wherein, Based on configuring multiple events for the UE, the first uplink transmission or the second uplink transmission includes information indicating which of the multiple events the reported value is associated with.

11. The method according to claim 1, wherein, The transmission timing of the second uplink transmission is determined to be an offset from the transmission timing of the first uplink transmission.

12. The method according to claim 11, wherein, The transmission timing of the second uplink transmission is determined by the UE and is sent by being included in the first uplink transmission.

13. The method according to claim 11, wherein, Configure one or more offset candidates for the transmission timing of the second uplink transmission for the UE, and The offset is determined from one or more offset candidates.

14. The method according to claim 1, wherein, The reported value is a pair of RS resource identifier and Layer 1 reference signal received power (L1-RSRP), or a pair of RS resource identifier and Layer 1 signal-to-interference-plus-noise ratio (L1-SNIR).

15. The method according to claim 1, wherein, The downlink RS corresponds to one of the synchronization signal block (SSB) and the CSI-reference signal (CSI-RS).

16. A user equipment (UE), comprising: At least one transceiver, the at least one transceiver being used to transmit and receive wireless signals; as well as At least one processor, the at least one processor being used to control the at least one transceiver, Wherein, the at least one processor is configured to: Receive configuration information related to Channel State Information (CSI) reports from the base station; Receive downlink RS from the base station on one or more reference signal (RS) resources; Based on the fulfillment of the event associated with the CSI report, a first uplink transmission is sent to the base station; and A second uplink transmission, including a report value derived from the downlink RS, is sent to the base station.

17. At least one non-transitory computer-readable medium, said non-transitory computer-readable medium storing at least one instruction, wherein, The user equipment (UE) is controlled by at least one instruction executable by at least one processor: Receive configuration information related to Channel State Information (CSI) reports from the base station; Receive downlink RS from the base station on one or more reference signal (RS) resources; Based on the fulfillment of the event related to the CSI report, a first uplink transmission is sent to the base station; as well as A second uplink transmission, including a report value derived from the downlink RS, is sent to the base station.

18. A processing apparatus configured to control a user equipment (UE), the processing apparatus comprising: At least one processor; as well as At least one computer memory, operatively connected to the at least one processor and storing instructions that perform operations based on execution by the at least one processor, the operations including: The user equipment receives configuration information related to the Channel State Information (CSI) report from the base station; The UE receives downlink RS from the base station on one or more reference signal (RS) resources; Based on the fulfillment of the event associated with the CSI report, the UE sends a first uplink transmission to the base station; and The UE sends a second uplink transmission to the base station, including a report value derived from the downlink RS.

19. A method comprising: The base station sends configuration information related to the Channel State Information (CSI) report to the user equipment (UE); The base station transmits downlink RS to the UE on one or more reference signal (RS) resources; Based on the fulfillment of the event associated with the CSI report, the base station receives a first uplink transmission from the UE; as well as The base station receives a second uplink transmission from the UE, including a report value derived from the downlink RS.

20. A base station, comprising: At least one transceiver, the at least one transceiver being used to transmit and receive wireless signals; as well as At least one processor, the at least one processor being used to control the at least one transceiver, Wherein, the at least one processor is configured to: Send configuration information related to Channel State Information (CSI) reports to the User Equipment (UE); Send downlink RS to the UE on one or more Reference Signal (RS) resources; Based on the fulfillment of the event associated with the CSI report, a first uplink transmission is received from the UE; and The UE receives a second uplink transmission including a report value derived from the downlink RS.

Images