Method and device for UE-initiated channel state information reporting in wireless communication system

Abstract

Disclosed are a method and device for channel state information (CSI) reporting initiated by a UE in a wireless communication system. The method according to an embodiment of the present disclosure may comprise the steps in which: a UE receives, from a network, a configuration related to a CSI report; and the UE transmits, to the network, one or more uplink channels on the basis of the priority for a first uplink channel including a first UE-initiated (UEI) CSI report and the priority for one or more second uplink channels. The priority for the first uplink channel including the first UEI CSI report may be based on at least one of event-related information, a priority index, or a power allocation order.

Description

Method and device for reporting terminal-initiated channel state information in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for reporting channel state information (CSI) initiated by a terminal in a wireless communication system.

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

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

[0004] The technical problem of the present disclosure is to provide a terminal-initiated CSI reporting method and device in a wireless communication system.

[0005] An additional technical challenge of the present disclosure is to provide a method and apparatus based on priority for terminal-initiated CSI reporting in a wireless communication system.

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

[0007] A method according to one embodiment of the present disclosure may include the steps of: receiving, by a terminal, from a network, a setting related to channel state information (CSI) reporting; and transmitting, by the terminal, to the network, one or more uplink channels based on a priority for a first uplink channel including a first terminal-initiated (UEI) CSI report and a priority for one or more second uplink channels. The priority for the first uplink channel including the first UEI CSI report may be based on one or more of event-related information, a priority index, or a power allocation order.

[0008] A method according to an additional embodiment of the present disclosure may include the steps of transmitting, by a base station, to a terminal, a configuration related to channel state information (CSI) reporting; and receiving, by the base station, from the terminal, one or more uplink channels based on a priority for a first uplink channel including a first terminal-initiated (UEI) CSI report and a priority for one or more second uplink channels. The priority for the first uplink channel including the first UEI CSI report may be based on one or more of event-related information, a priority index, or a power allocation order.

[0009] According to the present disclosure, a terminal-initiated CSI reporting method and device in a wireless communication system can be provided.

[0010] According to the present disclosure, a method and device based on priority for terminal-initiated CSI reporting in a wireless communication system can be provided.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0025] FIG. 13 is a diagram illustrating an uplink beam management operation using SRS in a wireless communication system to which the present disclosure can be applied.

[0026] FIG. 14 is a diagram illustrating an uplink beam management procedure in a wireless communication system to which the present disclosure can be applied.

[0027] FIG. 15 is a drawing for explaining an example of a method performed by a terminal according to the present disclosure.

[0028] FIG. 16 is a drawing for explaining an example of a method performed by a base station according to the present disclosure.

[0029] FIG. 17 is a drawing illustrating a block diagram of a wireless communication device according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0043] - BM: beam management

[0044] - CQI: Channel Quality Indicator

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

[0046] - CSI: Channel State Information

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

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

[0049] - DMRS: Demodulation Reference Signal

[0050] - FDM: frequency division multiplexing

[0051] - FFT: fast Fourier transform

[0052] - IFDMA: interleaved frequency division multiple access

[0053] - IFFT: inverse fast Fourier transform

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

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

[0056] - MAC: Medium Access Control

[0057] - NZP: non-zero power

[0058] - OFDM: orthogonal frequency division multiplexing

[0059] - PDCCH: Physical downlink control channel

[0060] - PDSCH: Physical downlink shared channel

[0061] - PMI: precoding matrix indicator

[0062] - RE: resource element

[0063] - RI: Rank indicator

[0064] - RRC: Radio Resource Control

[0065] - RSSI: Received signal strength indicator

[0066] - Rx: Reception

[0067] - QCL: quasi co-location

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

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

[0070] - TDM: Time Division Multiplexing

[0071] - TRP: transmission and reception point

[0072] - TRS: Tracking Reference Signal

[0073] - Tx: transmission

[0074] - UE: user equipment

[0075] - ZP: Zero Power

[0076] System General

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

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

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

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

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

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

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

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

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

[0086] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands, when the SCS is 30 kHz / 60 kHz, it supports dense-urban, lower latency, and wider carrier bandwidth, and when the SCS is 60 kHz or higher, it supports a bandwidth larger than 24.25 GHz to overcome phase noise. The NR frequency band is defined by two types of frequency ranges (FR1, FR2). FR1 and FR2 can be configured as shown in Table 2 below. In addition, FR2 can mean millimeter wave (mmW).

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

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

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

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

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

[0092] FIG. 2 is an example when μ=2 (SCS is 60 kHz), and referring to Table 3, 1 subframe can include 4 slots. 1 subframe={1,2,4} slot illustrated in FIG. 2 is an example, and the number of slot(s) that can be included in 1 subframe is defined as in Table 3 or Table 4. In addition, a mini-slot can include 2, 4, or 7 symbols, or more or fewer symbols. With respect to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. can be considered.

[0093] Hereinafter, the physical resources that can be considered in the NR system will be examined in detail. First, with respect to antenna ports, antenna ports are defined such that the channel through which a symbol on the antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. If the large-scale property of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on another antenna port is carried, then two antenna ports can be said to have a QC / QCL (quasi co-located or quasi co-location) relationship. Here, the large-scale property includes one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

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

[0095] Referring to Figure 3, the resource grid is N in the frequency domain. RB μ N sc RB It consists of subcarriers, and one subframe is 14·2 μ It is described as an example, but not limited to, that it consists of OFDM symbols. In an NR system, the transmitted signal is N RB μ N sc RB One or more resource grids consisting of subcarriers and 2 μ N symb (μ) is described by OFDM symbols. Here, N RB μ ≤N RBmax,μ is. The above N RB max,μ represents the maximum transmission bandwidth, which can vary between uplink and downlink as well as between numerologies.

[0096] In this case, one resource grid can be set for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is referred to as a resource element and is uniquely identified by an index pair (k, l'), where k=0,...,N. RB μ N sc RB -1 is the index in the frequency domain, and l'=0,...,2 μ N symb (μ) -1 indicates the position of the symbol within the subframe. When referring to a resource element in a slot, an index pair (k,l) is used. Here, l=0,...,N symb μ -1. The resource element (k,l') for μ and antenna port p is a complex value a k,l' (p,μ) . If there is no risk of confusion or if a particular antenna port or numerology is not specified, the indices p and μ can be dropped, resulting in a complex value of a k,l' (p) or a k,l' This can be. Also, a resource block (RB) is N in the frequency domain. sc RB =12 is defined as consecutive subcarriers.

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

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

[0099] - absoluteFrequencyPointA represents the frequency location of point A expressed as in ARFCN (absolute radio-frequency channel number). Common resource blocks (CRBs) are numbered from 0 upwards in the frequency domain for the subcarrier spacing setting μ. The center of subcarrier 0 of CRB 0 for the subcarrier spacing setting μ coincides with 'point A'. Common resource block number n in the frequency domain CRB μ The relationship between the resource elements (k, l) and the subcarrier spacing setting μ is given by the following mathematical expression 1.

[0100]

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

[0102]

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

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

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

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

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

[0108] Meanwhile, a base station can configure multiple BWPs even within a single CC configured for a terminal. For example, a BWP occupying a relatively small frequency domain can be configured in a PDCCH monitoring slot, while the PDSCH indicated by the PDCCH can be scheduled on a larger BWP.

[0109] Alternatively, if UEs are concentrated in a specific BWP, some UEs can be assigned to different BWPs for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, some spectrum in the middle of the total bandwidth can be excluded and both BWPs can be assigned within the same slot. In other words, the base station can assign at least one DL / UL BWP to UEs associated with a wideband CC.

[0110] The base station can activate at least one DL / UL BWP among the DL / UL BWP(s) configured at a specific point in time (by L1 signaling or MAC CE (Control Element) or RRC signaling, etc.). In addition, the base station can instruct switching to another configured DL / UL BWP (by L1 signaling or MAC CE or RRC signaling, etc.). Alternatively, switching to a designated DL / UL BWP may be performed when a timer value expires based on a timer. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP.

[0111] However, since the terminal may not receive the configuration for DL / UL BWP in situations such as when the terminal is performing the initial access process or before the RRC connection is set up, the DL / UL BWP assumed by the terminal in these situations is defined as the initial active DL / UL BWP.

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

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

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

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

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

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

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

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

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

[0121] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to scheduling of PUSCH (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), HARQ (Hybrid - Automatic Repeat and request) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined. DCI format 0_0 is used for scheduling of PUSCH in one cell. Information included in DCI format 0_0 is transmitted with CRC (cyclic redundancy check) scrambled by C-RNTI (cell radio network temporary identifier, Cell RNTI), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI).

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

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

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

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

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

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

[0128] beam management (BM)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0149] In Table 6, the csi-SSB-ResourceSetList parameter indicates a list of SSB resources used for beam management and reporting in one resource set. Here, the SSB resource set can be set to {SSBx1, SSBx2, SSBx3, SSBx4, ...}. The SSB index can be defined from 0 to 63. The terminal receives SSB resources from the base station based on the CSI-SSB-ResourceSetList (S420).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0186] Depending on the terminal implementation, UL BM may or may not have beam reciprocity (or beam correspondence) between the Tx beam and the Rx beam. If reciprocity between the Tx beam and the Rx beam is established at both the base station and the terminal, the UL beam pair can be aligned through the DL beam pair. However, if reciprocity between the Tx beam and the Rx beam is not established at either the base station or the terminal, a UL beam pair determination process is required separately from the DL beam pair determination.

[0187] Additionally, even if both the base station and the terminal maintain beam correspondence, the base station can use the UL BM procedure for DL ​​Tx beam determination without the terminal requesting reporting of a preferred beam.

[0188] UL BM can be performed via beamformed UL SRS transmission, and whether UL BM is applied to an SRS resource set is determined by the (higher layer parameter) usage. When usage is set to 'BeamManagement (BM)', only one SRS resource can be transmitted for each of multiple SRS resource sets at a given time instant.

[0189] A UE can be configured with one or more SRS (Sounding Reference Symbol) resource sets (via higher layer signaling, RRC signaling, etc.) configured by (higher layer parameter) SRS-ResourceSet. For each SRS resource set, the UE can be configured with K≥1 SRS resources (higher layer parameter SRS-resource). Here, K is a natural number, and the maximum value of K is indicated by SRS_capability.

[0190] Similar to DL BM, UL BM procedure can be divided into Tx beam sweeping of the terminal and Rx beam sweeping of the base station.

[0191] FIG. 13 is a diagram illustrating an uplink beam management operation using SRS in a wireless communication system to which the present disclosure can be applied.

[0192] Fig. 13(a) illustrates the Rx beam determination operation of the base station, and Fig. 13(b) illustrates the Tx beam sweeping operation of the terminal.

[0193] FIG. 14 is a diagram illustrating an uplink beam management procedure in a wireless communication system to which the present disclosure can be applied.

[0194] The terminal receives RRC signaling (e.g., SRS-Config IE) from the base station including the usage parameter (upper layer parameter) set to 'beam management' (S1010).

[0195] Table 8 shows an example of an SRS-Config IE (Information Element), which is used to configure SRS transmission. The SRS-Config IE includes a list of SRS-Resources and a list of SRS-ResourceSets. Each SRS resource set represents a set of SRS-resources.

[0196] The network can trigger the transmission of an SRS resource set using the configured aperiodicSRS-ResourceTrigger (L1 DCI).

[0197] -- ASN1START-- TAG-MAC-CELL-GROUP-CONFIG-STARTSRS-Config ::= SEQUENCE {srs-ResourceSetToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need Nsrs-ResourceSetToAddModList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need Nsrs-ResourceToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-ResourceId OPTIONAL, -- Need Nsrs-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-Resource OPTIONAL, -- Need Ntpc-Accumulation ENUMERATED {disabled} OPTIONAL, -- Need S...}SRS-ResourceSet ::= SEQUENCE {srs-ResourceSetId SRS-ResourceSetId,srs-ResourceIdList SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-ResourceId OPTIONAL, -- Cond SetupresourceType CHOICE {aperiodic SEQUENCE {aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates-1),csi-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebookslotOffset INTEGER (1..32) OPTIONAL, -- Need S...,[[aperiodicSRS-ResourceTriggerList SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-2))OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL -- Need M]]},semi-persistent SEQUENCE {associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook...},periodic SEQUENCE {associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook...}},usage ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching},alpha Alpha OPTIONAL, -- Need Sp0 INTEGER (-202..24) OPTIONAL, -- Cond SetuppathlossReferenceRS PathlossReferenceRS-Config OPTIONAL, -- Need Msrs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2, separateClosedLoop} OPTIONAL, -- Need S...,[[pathlossReferenceRSList-r16 SetupRelease { PathlossReferenceRSList-r16} OPTIONAL -- Need M]]}PathlossReferenceRS-Config ::= CHOICE {ssb-Index SSB-Index,csi-RS-Index NZP-CSI-RS-ResourceId}SRS-PosResourceSet-r16 ::= SEQUENCE {srs-PosResourceSetId-r16 SRS-PosResourceSetId-r16,srs-PosResourceIdList-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-PosResourceId-r16OPTIONAL, -- Cond SetupresourceType-r16 CHOICE {aperiodic-r16 SEQUENCE {aperiodicSRS-ResourceTriggerList-r16 SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-1))OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL, -- Need M...},semi-persistent-r16 SEQUENCE {...},periodic-r16 SEQUENCE {...}},alpha-r16 Alpha OPTIONAL, -- Need Sp0-r16 INTEGER (-202..24) OPTIONAL, -- Cond SetuppathlossReferenceRS-Pos-r16 CHOICE {ssb-IndexServing-r16 SSB-Index,ssb-Ncell-r16 SSB-InfoNcell-r16,dl-PRS-r16 DL-PRS-Info-r16} OPTIONAL, -- Need M...}SRS-SpatialRelationInfo ::= SEQUENCE {servingCellId ServCellIndex OPTIONAL, -- Need SreferenceSignal CHOICE {ssb-Index SSB-Index,csi-RS-Index NZP-CSI-RS-ResourceId,srs SEQUENCE {resourceId SRS-ResourceId,uplinkBWP BWP-Id}}}SRS-SpatialRelationInfoPos-r16 ::= CHOICE {servingRS-r16 SEQUENCE {servingCellId ServCellIndex OPTIONAL, -- Need SreferenceSignal-r16 CHOICE {ssb-IndexServing-r16 SSB-Index,csi-RS-IndexServing-r16 NZP-CSI-RS-ResourceId,srs-SpatialRelation-r16 SEQUENCE {resourceSelection-r16 CHOICE {srs-ResourceId-r16 SRS-ResourceId,srs-PosResourceId-r16 SRS-PosResourceId-r16},uplinkBWP-r16 BWP-Id}}},ssb-Ncell-r16 SSB-InfoNcell-r16,dl-PRS-r16 DL-PRS-Info-r16}SRS-ResourceId ::= INTEGER (0..maxNrofSRS-Resources-1).

[0198] In Table 8, usage represents a higher layer parameter indicating whether the SRS resource set is used for beam management, codebook-based or non-codebook-based transmission. The usage parameter corresponds to the L1 parameter 'SRS-SetUse'. 'spatialRelationInfo' or 'spatialRelationInfoPos-r16' is a parameter indicating the setting of the spatial relation between a reference RS and a target SRS. Here, the reference RS can be an SSB, CSI-RS, or SRS corresponding to the L1 parameter 'SRS-SpatialRelationInfo'. The usage is set for each SRS resource set. If the SRS is set by 'SRS-PosResourceSet-r16', the reference RS can correspond to a DL PRS (Positioning reference signal), and the usage can be set for each SRS resource set.

[0199] The terminal determines the Tx beam for the SRS resource to be transmitted based on the SRS-SpatialRelation Info included in the SRS-Config IE (S1020). Here, the SRS-SpatialRelation Info is set for each SRS resource and indicates whether to apply the same beam as the beam used in SSB, CSI-RS, or SRS for each SRS resource. In addition, the SRS-SpatialRelationInfo may or may not be set for each SRS resource.

[0200] If SRS-SpatialRelationInfo is set in the SRS resource, the same beam used in SSB, CSI-RS, or SRS is applied for transmission. However, if SRS-SpatialRelationInfo is not set in the SRS resource, the terminal randomly determines a Tx beam and transmits SRS through the determined Tx beam (S1030).

[0201] More specifically, for P-SRS with 'SRS-ResourceConfigType' or 'SRS-PosResource-r16' set to 'periodic':

[0202] i) If SRS-SpatialRelationInfo or SRS-PosResource-r16 is set to 'SSB / PBCH', the UE transmits the corresponding SRS resource by applying a spatial domain transmission filter that is the same as (or generated from) the spatial domain Rx filter used for receiving the SSB / PBCH; or

[0203] ii) If SRS-SpatialRelationInfo or SRS-PosResource-r16 is set to 'CSI-RS', the UE transmits the SRS resource by applying the same spatial domain transmission filter used for reception of periodic CSI-RS or SP (semi-persistent) CSI-RS; or

[0204] iii) If SRS-SpatialRelationInfo or SRS-PosResource-r16 is set to 'SRS', the UE transmits the corresponding SRS resource by applying the same spatial domain transmission filter used for transmitting periodic SRS.

[0205] iv) If spatialRelationInfoPos-r16 is set to 'PRS', the UE transmits the corresponding SRS resource by applying the same spatial domain transmission filter used for receiving DL PRS.

[0206] Beam decision and transmission behavior similar to the above can be applied even when 'resourceType' in 'SRS-Resource' or 'SRS-PosResource-r16' is set to 'SP-SRS' or 'AP-SRS'.

[0207] Additionally, the terminal may or may not receive feedback on SRS from the base station in the following three cases (S1040).

[0208] i) If Spatial_Relation_Info is set for all SRS resources within the SRS resource set, the terminal transmits SRS using the beam indicated by the base station. For example, if Spatial_Relation_Info indicates the same SSB, CRI, or SRI, the terminal repeatedly transmits SRS using the same beam. This case corresponds to Fig. 13(a) for the purpose of the base station selecting the Rx beam.

[0209] ii) Spatial_Relation_Info may not be set for all SRS resources within the SRS resource set. In this case, the terminal can freely change the SRS beam while transmitting. That is, this case corresponds to Fig. 13(b) for the purpose of the terminal sweeping the Tx beam.

[0210] iii) Spatial_Relation_Info may be set only for some SRS resources within an SRS resource set. In this case, SRS is transmitted using the indicated beam for the set SRS resources, and for SRS resources for which Spatial_Relation_Info is not set, the terminal may arbitrarily apply a Tx beam for transmission.

[0211] BM procedure in improved wireless communication systems

[0212] To ensure flexibility in beam indication in a basic wireless communication system, beams are indicated separately for each DL / UL channel / RS resource, and the indication method can be set for each channel / RS.

[0213] In the above-mentioned instruction method, in order to change the serving beam of multiple terminals communicating with the base station using a single beam, the base station must instruct each terminal to change the beam for each channel / RS resource. This can lead to increased signaling overhead and increased beam change latency.

[0214] Additionally, since UL power control related parameters (e.g., pathloss RS (PL RS)) must be changed for each UL channel / RS along with UL beam changes, there was a signaling overhead / latency problem.

[0215] To address this, the improved wireless communication system may apply i) default spatial relation / PL RS configuration, ii) multi-CC simultaneous TCI / spatial relation update, iii) PUCCH resource group configuration based on spatial relation update, iv) MAC CE-based spatial relation indication for aperiodic / semi-persistent SRS, and v) MAC CE-based PL RS update for aperiodic / semi-persistent SRS and PUSCH.

[0216] Additionally, in an improved wireless communication system, a base station can configure not only channel measurement RSs but also interference measurement resources for a terminal. The terminal can measure L1-SINR for the configured channel measurement RSs and interference measurement resources, and report one or more RSs corresponding to one or more LI-SINRs with a larger value among the measured L1-SINRs.

[0217] In addition, the method described below can be applied to set / indicate a beam in an integrated channel / RS manner for a terminal operating with a single serving beam. Hereinafter, the TCI that sets / indicates a beam in an integrated channel / RS manner for a terminal is referred to as an unified TCI state.

[0218] Specifically, the DL unified TCI state may indicate a QCL type-D RS applied to PDCCH, PDSCH, and / or CSI-RS resources, and the UL unified TCI state may indicate a spatial relationship RS (and / or PL RS) applied to PUCCH, PUSCH, and / or SRS resources.

[0219] In addition, for terminals where beam correspondence is established (as with the default spatial relationship / PL RS), the UL spatial relationship and PL RS can also be aligned with the DL beam RS, so that the unified TCI state can be applied to both DL / UL channels / RS. The unified TCI state that can be applied to both DL / UL channels / RS is called a joint DL / UL TCI state, and the following two modes can be supported.

[0220] i) Joint DL / UL TCI configuration / indication mode: The DL RS configured / indicated by the Joint TCI state can be applied as a QCL type-D RS for DL ​​channels / RSs. As another example, the DL RS configured / indicated by the Joint TCI state can also be applied as a spatial relationship RS (or / and PL RS) for UL channels / RSs. That is, when an update to the joint TCI state is indicated, the beam RS (or / and PL RS) for the corresponding DL channel / RSs and UL channels / RSs can be changed together.

[0221] ii) Separate DL and UL TCI setting / indication mode: QCL type-D source RS for DL ​​channels / RSs can be set / indicated by the DL TCI state, and spatial relationship RS (or / and PL RS) for UL channels / RSs can be set / indicated by the UL TCI state. In this case, the DL TCI state and UL TCI state can be set / indicated separately.

[0222] The above joint DL / UL TCI state can be indicated / updated via MAC-CE and / or DCI. Specifically, one or more TCI state(s) among multiple TCI states (i.e., TCI state pool) set by RRC signaling can be activated by MAC-CE.

[0223] When multiple TCI states are activated by MAC-CE, one of the multiple TCI states may be indicated by DCI. One of the multiple TCI states may be indicated by DL DCI format (DCI format 1-1 / 1-2) (or / and DCI without PDSCH scheduling). If the DCI does not include PDSCH scheduling information, the UE may transmit an ACK for the corresponding DCI to the base station (similar to the DCI-based SPS release method).

[0224] Additionally, the terminal can measure and report the optimal beam RS for each TRP. To this end, the base station can divide the beam measurement RS set / group into one or more subsets / subgroups and configure them for the terminal. The terminal can select one or more RS(es) for each subset / subgroup and report the selected RS along with its quality value (L1-RSRP, [L1-SINR]) to the base station.

[0225] Priority rules for CSI reports

[0226] For two overlapping PUSCHs, the priority rules described below can be applied to physical channels of the same priority in the terminal procedure for control information reporting.

[0227] A CSI report can be associated with a priority value. The priority value can be defined as Pri_iCSI(y,k,c,s) = 2 * N_cells * M_s * y + N_cells * M_s * k + M_s *c + s.

[0228] Here, y=0 for an aperiodic (AP) CSI report carried on PUSCH, y=1 for a semi-persistent (SP) CSI report carried on PUSCH, y=2 for an SP CSI report carried on PUCCH, and y=3 for a periodic (P) CSI report carried on PUCCH.

[0229] Additionally, k=0 for CSI reports that carry L1-RSRP or L1-SINR, and k=1 for CSI reports that do not carry L1-RSRP or L1-SINR.

[0230] Also, c is the serving cell index, and N_cells is the value of the upper layer parameter for the maximum number of serving cells (e.g., maxNrofServingCells).

[0231] Additionally, s is a report configuration identifier (e.g., reportConfigId), and M_s is the value of a higher-layer parameter for the maximum number of CSI-report configurations (e.g., maxNrofCSI-ReportConfigurations).

[0232] If the time occupancy of physical channels scheduled to carry two CSI reports overlaps in at least one OFDM symbol, the two CSI reports may be said to collide. When a terminal is configured to transmit two colliding CSI reports, the following behavior may occur:

[0233] If the y values ​​of two CSI reports are different, the CSI report with the higher Pri_iCSI(y,k,c,s) value is not transmitted by the terminal, except in certain cases. Here, the certain case may be a case where one y value is 2 and the other y value is 3 (e.g., a CSI report transmitted on PUSCH and a CSI report transmitted on PUCCH).

[0234] Otherwise (or if the y values ​​of the two CSI reports are the same), the two CSI reports may be multiplexed or dropped according to priority rules.

[0235] UE procedures for reporting control information

[0236] When a terminal determines overlapping for PUCCH and / or PUSCH transmissions of different priority indices and a parameter for multiplexing the different priorities for uplink control information (UCI) for the terminal (e.g., uci-MuxWithDiffPrio) is provided, the terminal may operate as follows.

[0237] If the terminal supports multiplexing of information of different priorities in PUCCH / PUSCH transmission,

[0238] - A PUCCH transmission containing HARQ-ACK information with a smaller priority index without repetition overlaps with a PUCCH transmission containing only HARQ-ACK information with a larger priority index without repetition, or

[0239] - A PUCCH transmission containing HARQ-ACK information with a smaller priority index without repetition overlaps with a PUCCH transmission using PUCCH resources of PUCCH format 2 / 3 / 4 containing HARQ-ACK and SR (scheduling request) with a larger priority index without repetition, or

[0240] - If a PUCCH transmission containing HARQ-ACK information with a smaller or larger priority index overlaps with a PUSCH transmission with a larger or smaller priority index, respectively, without repetition,

[0241] The terminal is

[0242] - If present, HARQ-ACK information of different priority indices and SR information of a larger priority index are multiplexed in the same PUCCH transmission of a larger priority index, or HARQ-ACK information that a terminal intends to provide in a PUCCH transmission of a smaller or larger priority index are multiplexed in a PUSCH transmission of a larger or smaller priority index, and a terminal procedure for UCI reporting of different priorities or a procedure for UCI reporting on PUSCH are applied, respectively.

[0243] - Drop CSI and / or SR carried in PUCCH transmissions with lower priority indices, if any.

[0244] - If the terminal wants to multiplex HARQ-ACK information of a higher priority index in a PUSCH transmission of a lower priority index, it drops the negative SR transmitted in the PUCCH transmission of the higher priority index, if any.

[0245] - When a terminal multiplexes HARQ-ACK information of a smaller priority index in a PUSCH transmission where the terminal multiplexes Part 1 CSI report and Part 2 CSI report of a larger priority index, the HARQ-ACK information of the smaller priority index is dropped.

[0246] - In a PUSCH transmission where the terminal multiplexes Part 1 CSI reports and Part 2 CSI reports of a smaller priority index, if the terminal wants to multiplex HARQ-ACK information of a smaller and larger priority index, the Part 2 CSI reports of the smaller priority index are dropped.

[0247] - When multiplexing HARQ-ACK information of a smaller priority index using the PUCCH resources provided by the n1PUCCH-AN parameter in a PUCCH transmission of a larger priority index, drop the HARQ-ACK information of the smaller priority index,

[0248] - When a UE multiplexes HARQ-ACK information of a larger priority index in a PUSCH transmission multiplexing CG (configured grant)-UCI, or UTO (unused transmission occasion)-UCI, Part 1 CSI report and Part 2 CSI report of a smaller priority index, the Part 2 CSI report of a smaller priority index may be dropped.

[0249] If not (or the terminal does not support multiplexing of information of different priorities in PUCCH / PUSCH transmission),

[0250] - When repetition is applied to channel transmission, the following description is applicable per repetition, and the terminals are overlapped in time with the channels described below.

[0251] -- Transmission of the first PUCCH with a higher priority index and transmission of the second PUCCH with a lower priority index

[0252] -- If the terminal cannot transmit the first PUCCH and the second PUSCH simultaneously, the first PUCCH transmission with a larger priority index and the second PUSCH transmission with a smaller priority index

[0253] -- When the terminal can transmit the first PUCCH and the second PUSCH simultaneously, the first PUCCH transmission with a smaller priority index and the second PUSCH transmission with a larger priority index

[0254] If you want to transmit, the terminal must

[0255] - Transmitting a PUCCH or PUSCH with a higher priority index that is subject to terminal procedures for slot setup, slot format determination, cancellation instructions, and terminal transmission restrictions in dual-active protocol stack-based handover;

[0256] - PUCCH or PUSCH with a lower priority index may not be transmitted.

[0257] Meanwhile, the channels described below, which overlap in time, including repetitions if any, are

[0258] - A first PUCCH with a higher priority index including SR and a second PUCCH or PUSCH with a lower priority index, or

[0259] - A configured grant PUSCH with a larger priority index and a PUCCH with a smaller priority index, or

[0260] - A first PUCCH of a larger priority index including HARQ-ACK information that responds only to reception of PDSCH(s) without corresponding PDCCH(s) and a second PUCCH of a smaller index including HARQ-ACK information that responds only to reception of PDSCH(s) without corresponding PDCCH(s), or a second PUCCH of a smaller priority index including SR and / or CSI, or a configured grant PUSCH of a smaller priority index, or a PUSCH of a smaller priority index including SP (semi-persistemt)-CSI report(s) without corresponding PDCCH, or

[0261] - PUSCH and SR of a higher priority index containing SP-CSI report(s) without corresponding PDCCH, or PUCCH of a lower priority index containing HARQ-ACK information that only responds to reception of CSI, or PDSCH(s) without corresponding PDCCH(s), or

[0262] - A configured grant PUSCH with a larger priority index and a configured grant PUSCH with a smaller priority index or a PUSCH with a smaller priority index that includes SP-CSI report(s) without a corresponding PDCCH on the same serving cell.

[0263] - A PUSCH of a higher priority index that includes SP-CSI report(s) without a corresponding PDCCH and a configured grant PUSCH of a lower priority index or a PUSCH of a lower priority index that includes SP-CSI report(s) without a corresponding PDCCH on the same serving cell.

[0264] - When parameters for low priority dynamic grant and high configured grant (e.g., prioLowDG-HighCG) are provided for the terminal, the PUSCH with a lower priority index scheduled by the DCI format and the configured grant PUSCH with a higher priority index on the same serving cell.

[0265] - When parameters for dynamic grants with high priority and configured grants with low priority (e.g., prioHighDG-LowCG) are provided for a terminal, a PUSCH with a higher priority index scheduled by the DCI format and a configured grant PUSCH with a lower priority index on the same serving cell

[0266] If the terminal wants to transmit,

[0267] The terminal is expected to cancel the repetition of the PUCCH / PUSCH transmission of the lower priority index before the first symbol that overlaps with the PUCCH / PUSCH transmission of the higher priority index, if the repetition of the PUCCH / PUSCH transmission of the lower priority index overlaps with the PUCCH / PUSCH transmission of the higher priority index in time.

[0268] Prioritizations for transmission power reductions

[0269] For single-cell operation including two uplink carriers or operation including carrier aggregation, if the total terminal transmit power for PUSCH or PUCCH or PRACH or SRS transmission on serving cells in a frequency range at each transmission opportunity i exceeds the linear value of P_CMAX(i) at transmission opportunity i, the terminal may allocate power for PUSCH / PUCCH / PRACH / SRS transmission according to the priority order (in descending order) described below, such that the total terminal transmit power transmitted on serving cells in the corresponding frequency range is less than or equal to the linear value of P_CMAX(i) for every symbol of transmission opportunity i in the corresponding frequency range. If the terminal transmits SRS on multiple SRS resources, the terminal may allocate all REs for SRS transmission to have the same power.

[0270] When a parameter (e.g., uci-MuxWithDiffPrio) for multiplexing different priorities for UCI) is provided to the terminal for the purpose of power allocation and the terminal multiplexes HARQ-ACK information on the PUSCH, the priority index of the PUSCH may be the larger one of (a) the priority index of the PUSCH in the aforementioned "Terminal Procedure for Control Information Reporting" and (b) the larger priority index of the HARQ-ACK information. When determining the total transmit power for serving cells in a frequency range in a symbol of transmission opportunity i, the terminal may not include power for transmissions starting after the corresponding symbol of transmission opportunity i. The total terminal transmit power in a symbol of a slot may be defined as the sum of the linear values ​​of the transmit powers for PUSCH, PUCCH, PRACH, and SRS in the corresponding symbol of the corresponding slot.

[0271] - PRACH transmission on candidate cell, if any

[0272] - PRACH transmission on PCell

[0273] - PUCCH or PUSCH transmission with a higher priority index

[0274] - For PUCCH or PUSCH transmissions with the same priority index

[0275] -- PUCCH transmission including HARQ-ACK information, and / or SR, and / or LRR (link recovery request), or PUSCH transmission including HARQ-ACK information of the corresponding priority index.

[0276] -- PUCCH transmission including CSI or PUSCH transmission including CSI

[0277] -- PUSCH transmission on PCell for type-2 random access procedure and PUSCH transmission that does not include HARQ-ACK information or CSI of the corresponding priority index.

[0278] - When a parameter (e.g. prioSCellPRACH-OverSP-PeriodicSRS) is set for priority performance of PRACH transmission on SCell over semi-static (SP) or periodic SRS transmission for the terminal.

[0279] -- Aperiodic SRS transmission or PRACH transmission on a serving cell other than PCell

[0280] -- Semi-static and / or periodic SRS transmission

[0281] - if not (e.g. prioSCellPRACH-OverSP-PeriodicSRS is not set)

[0282] -- SRS transmission including aperiodic SRS having a higher priority than semi-static and / or periodic SRS, or PRACH transmission on a serving cell other than PCell.

[0283] In the case of the same priority order and for the operation of carrier aggregation, the terminal may preferentially apply power allocation to transmission on a primary cell of a master cell group (MCG) or a secondary cell group (SCG) compared to transmission on a secondary cell. In the case of the same priority order and for the operation including two uplink carriers, the terminal may preferentially apply power allocation to transmission on a carrier configured to transmit a PUCCH for the terminal. If a PUCCH is not configured on any of the two uplink carriers, the terminal may preferentially apply power allocation to transmission on a non-supplementary uplink carrier.

[0284] Terminal-initiated CSI reporting

[0285] In wireless communication systems, layer-1 (or physical layer) uplink control information has the advantage of shorter transmission delay than higher-layer control information. For example, for a terminal to transmit information to a base station using layer-2 MAC-CE signaling or layer-3 RRC message, a scheduling request (SR) procedure by the terminal and a PUSCH resource allocation procedure by the base station (based on the SR) may be required, resulting in time delay and overhead. Furthermore, higher-layer information generally requires longer information acquisition times (e.g., decoding time, processing time, etc.). In order for a terminal to transmit layer-1 uplink control information, physical uplink channel (e.g., PUCCH, PUSCH) resources must be configured / allocated (in advance) to the terminal. Therefore, from the base station / network's perspective, the more terminals / UEs there are, the more uplink (UL) resources must be allocated to each terminal / UE, which may increase the burden of overall UL resource overhead.

[0286] Therefore, in a wireless communication system, information that must be transmitted relatively urgently for the operation of the physical layer, such as SR (e.g., control information for PUSCH allocation), HARQ-ACK (e.g., control information for retransmission), CSI (e.g., control information for scheduling / MCS / precoding decisions), beam information (e.g., control information for beam decision / beamforming)) can be transmitted from the terminal to the network as physical layer uplink control information (UCI). With the exception of SR among these UCIs, the base station / network can determine / control the timing of the terminal's control information reporting. In the case of such network-initiated or network-triggered reporting, there is a limitation that the terminal must be configured / instructed to send UCI frequently in an environment where the wireless channel is likely to change rapidly (or is highly likely). In other words, in these environments, the UL resource overhead for UCI reporting and the associated DL measurement RS overhead increase, and the power consumption of the terminals also increases due to frequent uplink transmissions. Furthermore, since UL resources must be allocated to each terminal, the UL resource overhead increases as the number of terminals within cell / TRP coverage increases.

[0287] To overcome the limitations of these NW-initiated / triggered reporting methods, terminal-initiated / triggered reporting methods or event-initiated / induced reporting methods are being discussed. In these methods, whether and / or when to report UCI can be determined by the terminal. That is, by performing the (UCI) report only when necessary (e.g., only when a specific event occurs), there is the advantage of performing rapid control information reporting through layer-1 (or lower layer)-based information reporting while reducing UL resource overhead and terminal power consumption.

[0288] In this regard, the introduction of UE-initiated or event-driven beam management or beam reporting is being discussed to reduce overhead and / or latency. Such UE-initiated beam management takes into account unified TCI and can be applied to various frequency ranges and network node structures, including Frequency Range 2 (FR2) and Single Transmission Relay (S-TRP), and can also be applied to intra-cell and inter-cell beam management. In this regard, uplink signaling content(s) for UE-initiated / event-induced beam reporting need to be defined for fast beam switching, and procedures for the same need to be defined. In addition, an uplink signaling medium / container needs to be defined considering the UE-initiated / event-driven nature of uplink transmission, which is primarily designed for the purpose of beam reporting.

[0289] In the present disclosure, beam reporting may mean CSI reporting including terminal measurement information for a beam (e.g., L1-RSRP, L1-SINR, etc.) and / or identification information for the beam (e.g., CSI-RS resource index, SSB resource index, etc.). For beam reporting corresponding to one type of existing NW-initiated / triggered CSI reporting (or CSI feedback), the network may provide the terminal with UL resources and reporting configurations for beam reporting in advance, and the terminal may perform beam reporting accordingly. In contrast, for terminal-initiated / event-induced beam reporting, an event for beam reporting is set / defined for the terminal, and the terminal may determine whether an event occurs and perform beam reporting only when the event occurs.

[0290] Priorities between existing uplink channels / signals (e.g., priority index and UCI content-based operation in the aforementioned "Terminal Procedure for Control Information Reporting" section, and power allocation priorities in the aforementioned "Priority Handling for Transmit Power Reduction" section) do not define priorities between an uplink channel including UEI CSI reporting, such as beam reporting initiated by a terminal on an event basis, and other uplink channel(s) / signal(s). Therefore, to address the ambiguity regarding priorities of event-based UEI CSI reporting, the present disclosure describes examples of priorities between an uplink channel including UEI CSI reporting and other uplink channels / signals when a collision (or partial / full overlap of time resources) occurs between them.

[0291] In the present disclosure, defining information / values ​​may mean that the base station and the terminal know the information / values ​​in advance without signaling / instruction between the base station and the terminal regarding the information. In the present disclosure, setting information / values ​​to the terminal may mean that the base station provides the information / values ​​to the terminal through upper layer (e.g., L3) signaling. In the present disclosure, indicating information / values ​​to the terminal may mean that the base station provides the information / values ​​to the terminal through L2 / L1 signaling such as MAC CE or DCI.

[0292] FIG. 15 is a drawing for explaining an example of a method performed by a terminal according to the present disclosure.

[0293] In step S1510, the terminal can receive settings related to CSI reporting from the network.

[0294] The configuration related to CSI reporting may include information about an identifier for the CSI reporting configuration (e.g., reportConfigId), a type related to the CSI reporting (e.g., reportConfigType for periodic / semi-static / aperiodic CSI reporting on PUCCH / PUSCH), and report content (e.g., reportQuantity for RI / PMI / CQI / CRI / SSB-Index / L1-RSRP / L1-SINR, etc.).

[0295] The settings related to CSI reporting may further include settings for terminal-initiated (or UEI) CSI reporting (e.g., resources for reporting whether an event has occurred, and / or resources for UEI CSI reporting).

[0296] In step S1520, the terminal may transmit one or more uplink channels to the network based on a priority for a first uplink channel including the first UEI CSI report and a priority for one or more second uplink channels.

[0297] One or more of the second uplink channels may include a second UEI CSI report or may include other information than a UEI CSI report.

[0298] For example, the priority for a first uplink channel (e.g., an uplink channel containing a first UEI CSI report) may be based on event-related information (e.g., event type, event time, etc.). For example, the priority for the first uplink channel may be based on a priority index (e.g., the same priority index as the existing larger priority index (e.g., 1) and the smaller priority index (e.g., 0) or a new priority index that is different therefrom). For example, the priority for the first uplink channel may be based on a power allocation order (e.g., the same order as the order based on a combination of UCI content (e.g., UCI type such as HARQ-ACK / SR / LRR / CSI or whether UCI is included) and channel type (e.g., PUCCH / PUSCH) or a new order that is different therefrom). For example, the priority for the first uplink channel may be defined / set based on one or more of event-related information, a priority index, or a power allocation order.

[0299] For example, when transmissions of multiple uplink channels including a first uplink channel and one or more second uplink channels collide, transmission of an uplink channel with the highest priority among the multiple uplink channels may be performed, and transmissions of the remaining one or more uplink channels may be dropped. For example, when transmissions of multiple uplink channels including a first uplink channel and one or more second uplink channels collide, transmissions of one or more uplink channels with a lower priority among the multiple uplink channels may be dropped, and transmissions of one or more uplink channels with a higher priority may be multiplexed. For example, when transmissions of multiple uplink channels including a first uplink channel and one or more second uplink channels collide, power may be allocated in descending order from highest priority to lowest priority among the multiple uplink channels.

[0300] For example, priorities may be applied per event type or per event time for different uplink channels including UEI CSI reports. For example, a first priority for a first UEI CSI report associated with a first type of event and a second priority for a second UEI CSI report associated with a second type of event may be the same or different. Here, the first priority and the second priority may be included in two or more priorities for two or more event types. Alternatively, a first priority for a first UEI CSI report associated with an event at a first time point and a second priority for a second UEI CSI report associated with an event at a second time point may be the same or different.

[0301] For example, the priority index for the first uplink channel including the first UEI CSI report may have the same priority index as the existing larger first priority index and smaller second priority index, or different priority index values. The different priority index may be defined / set as, for example, a third priority index having a middle value between the first priority index and the second priority index, a fourth priority index greater than the first priority index, or a fifth priority index less than the second priority index. For example, the value of the first priority index may be 1, the value of the second priority index may be 0, the value of the third priority index may be 0.5, the value of the fourth priority index may be 2, and the value of the fifth priority index may be -1.

[0302] For example, for uplink channel transmissions having the same priority index, the power allocation order for the first uplink channel transmission including the first UEI CSI report may be the same as one of the existing power allocation orders or may have a new order that is different from the existing power allocation order. For example, the existing power allocation orders may include a first order of an uplink control channel transmission including one or more of HARQ-ACK information, SR, or LRR, or an uplink shared channel transmission including HARQ-ACK information; a second order of an uplink control channel transmission including CSI or an uplink shared channel transmission including CSI; and a third order of an uplink channel transmission not including HARQ-ACK information or CSI, and an uplink shared channel transmission on the primary cell in a two-step random access procedure. For example, the power allocation order for the first uplink channel transmission including the first UEI CSI report may be the same as the first order, or a new order before the first order; It can be defined / set as one of the following: a sequence after the first sequence and before the second sequence; a sequence after the second sequence and before the third sequence; or a sequence identical to the third sequence, or a sequence after the third sequence.

[0303] For example, a UEI CSI report may include one or more of a first report regarding a specific event occurrence, or a second report including a beam report. For example, the priority of the first report may be the same as or different from the priority of the second report. If different, the priority of the first report may be defined / set higher than the priority of the second report.

[0304] The method described in the example of FIG. 15 may be performed by the first wireless device (100) of FIG. 17, which will be described later. For example, one or more processors (102) of the first wireless device (100) of FIG. 17 may be configured to receive settings related to CSI reporting from the network through one or more transceivers (106), and transmit one or more uplink channels to the network through one or more transceivers (106) based on a priority for a first uplink channel including the first UEI CSI report and a priority for one or more second uplink channels. Furthermore, one or more memories (104) of the first wireless device (100) may store commands for performing the method described in the example of FIG. 15 or the examples described later when executed by one or more processors (102).

[0305] FIG. 16 is a drawing illustrating an example of a method performed by a base station according to the present disclosure.

[0306] In step S1610, the base station can transmit settings related to CSI reporting to the terminal.

[0307] In step S1620, the base station may receive one or more uplink channels transmitted from the terminal based on a priority for a first uplink channel including a first UEI CSI report and a priority for one or more second uplink channels.

[0308] The specific characteristics of the priority for the uplink channel including the UEI CSI report and the priority for other uplink channels are the same as the description referring to the example of FIG. 15, so the redundant description is omitted.

[0309] The method described in the example of FIG. 16 may be performed by the second wireless device (200) of FIG. 17, which will be described later. For example, one or more processors (202) of the second wireless device (200) of FIG. 17 may be configured to transmit settings related to CSI reporting to a terminal via one or more transceivers (206), and to receive one or more uplink channels from the terminal via one or more transceivers (206) based on a priority for a first uplink channel including a first UEI CSI report and a priority for one or more second uplink channels. Furthermore, one or more memories (204) of the second wireless device (200) may store commands for performing the method described in the example of FIG. 16 or the examples described later when executed by one or more processors (202).

[0310] Although this disclosure primarily describes UEI beam reporting as a representative example, the examples in this disclosure can also be applied to UEI CSI reporting (i.e., UEI reporting such as RI / PMI / CQI that is not a beam report). That is, unless the examples in this disclosure distinguish between beam reporting and CSI reporting other than beam reporting, beam reporting can be replaced with CSI reporting.

[0311] In the examples of the present disclosure, when an event related to a specific CSI report occurs, the terminal's request for scheduling of the UL channel for the CSI report from the network may include the terminal notifying the network of the event occurrence itself. That is, the terminal may directly request scheduling of the uplink channel from the network, or the terminal may only notify the network of the occurrence of the event, and the network may determine whether to schedule the uplink channel.

[0312] In the examples of this disclosure, the identifier (ID) may be replaced with an index.

[0313] The term 'beam' in the present disclosure may correspond to a source RS for a spatial filter or a spatial relation, or a QCL (type-D) RS, or a (DL / UL / joint) TCI state, or a spatial relation RS.

[0314] Below, various examples of priority rules for resolving a case in which an uplink channel including a UEI beam report collides (or time overlaps) with an uplink channel of another UEI beam report or any other uplink channel are described in the present disclosure.

[0315] Example 1

[0316] It can be assumed that multiple events are set up for UEI beam reporting, and that each event reports a different UEI beam report. In this case, different priorities can be set / defined for each event.

[0317] For example, event-related priorities can be set / defined as two types: high priority events and low priority events. For example, the base station can set whether a specific event (or a specific type of event) is high priority or low priority to the terminal. Alternatively, whether an event is high priority or low priority can be fixedly predefined for each event (or event type), and the base station may not set the corresponding priority.

[0318] For example, the terminal may determine the priority for each event and report it to the network. As an additional example, the terminal may calculate the priority value of the UEI beam report (e.g., Pri_iCSI(y,k,c,s)) and report the calculated priority value to the network along with the corresponding event / CSI report.

[0319] The priority level for an event (or UEI report related to the event) may be set / defined as two levels, a high priority level and a low priority level, or may be set / defined as multiple priority levels greater than two (e.g., levels 1, 2, 3, 4, ..).

[0320] The priority set for an event can be applied as the priority of the UEI CSI report (or beam report) related to the event. For example, if a UEI beam report for a high priority event conflicts with a UEI beam report for a low priority event, the terminal may transmit the beam report for the high priority event and drop the beam report for the low priority event. Or, even if the terminal can multiplex UEI beam reports, if the given uplink channel capacity is smaller than the payload size of the UEI beam reports to be reported, the terminal may sequentially drop the UEI beam report for the lowest priority event and multiplex and transmit only the UEI beam reports that can be accommodated in the uplink channel capacity.

[0321] The priority of an event (or a UEI report associated with an event) may also be set / defined based on the timing of the event. For example, assuming that an AI / ML (artificial intelligence / machine learning) terminal can perform beam prediction for a future time, distinct priorities may be set / defined for UEI beam reports triggered by satisfying an event occurrence condition for the present or near future, and for UEI beam reports triggered by satisfying an event occurrence condition for the distant future. For example, an event may be assumed to occur when a condition is satisfied that the RSRP of an RS resource configured as a CMR (channel measurement resource) is greater than or equal to a certain value.

[0322] In this case, events for the present / near future can be set / defined as higher priority events, while those for the distant future can be set / defined as lower priority events. This can be used to prioritize reporting, considering that the further into the future from the present, the less accurate the prediction.

[0323] Alternatively, events for the present / near future can be set / defined as lower priority events, and events for the distant future as higher priority events. This may be relevant when prioritizing / assigning reports, considering that long-term reports for the distant future are more useful to the network than reports for the present.

[0324] In this regard, the network can set the time information for determining the event occurrence condition (e.g., information on which time resource (e.g., slot, symbol, etc.) should be used to determine whether the event occurrence condition is satisfied) to the terminal. For example, if a specific time (e.g., the latest CMR measurement time) is used as a standard, an event for determining whether the occurrence condition is satisfied at a point in time x symbols / slots / times later can be defined, and the base station can set the value of x to the terminal. Alternatively, the base station can set to the terminal whether to perform prediction-based event detection at a higher level.

[0325] For example, a terminal may report to the network information about a future point in time related to an event (e.g., information indicating whether the terminal has determined whether an event occurrence condition is satisfied for a certain time resource (e.g., slot, symbol, etc.)). This information about a future point in time related to an event may be reported from the terminal to the network together with a UEI report (e.g., together with a report on whether an event has occurred or together with a beam report).

[0326] For example, the terminal can predict a beam quality metric for slot n+k1 (where k1>0) based on the beam measured at slot index n. For example, the beam quality metric can be L1-RSRP, L1-SINR, a hypothetical BLER (block error rate), etc. The terminal can determine whether an event occurrence condition is satisfied based on the predicted beam quality metric for slot index n+k1. Furthermore, the terminal can determine whether an event occurrence condition is satisfied based on the predicted beam quality metric for slot index n+k2 (where k2>k1). In this example, information about a future point in time can correspond to k1 or k2. Furthermore, if the relationship k2>k1 is satisfied, the event for slot index n+k2 becomes an event for a relatively distant future compared to the event for slot index n+k1.

[0327] For example, examples of events might include:

[0328] Event 1: The quality of the current beam is worse than a certain threshold.

[0329] Second event: The quality of one or more new beams (e.g., L1-RSRP) becomes a threshold value better than the quality of the current beam.

[0330] Third Event: The quality of the new beam is better than a certain threshold.

[0331] Event 4: The quality of the current beam is worse than the first threshold, and the quality of one or more new beams is better than the second threshold.

[0332] Event 5: The absolute difference between the quality of the current beam and the quality of one or more new beams is less than the threshold.

[0333] Event 6: The current beam is not among the best K (where K>1) beams among the beams set for measurement and reporting.

[0334] Event 7: The quality of one or more new beams (e.g., L1-RSRP) becomes better by a threshold value than the RS derived from the activated TCI state with the Q-th best quality.

[0335] In the examples described above, the current beam corresponds to the beam currently being used by the terminal, which may correspond to a QCL source RS configured through a TCI state indicated by the base station to the terminal. Alternatively, in the examples described above, the current beam may correspond to an SSB that is in a QCL relationship with a QCL source RS configured through a TCI state indicated by the base station to the terminal. A new beam may also be separately configured by the base station to the terminal for event detection.

[0336] In the examples described above, present / near future (e.g., time point A) and distant future (e.g., time point B) are examples of temporal orderings, and the examples of the present disclosure are not necessarily limited to future time points. For example, even in a general temporal ordering such as past / present / future time points (i.e., when there is a relative past / future (or temporal before / after) relationship between time points A and B), different priorities can be set / defined for events (or UEI reports associated with events) at different time points.

[0337] Example 2

[0338] In order to transmit the existing uplink URLLC TB / UCI with priority over the other TB / UCIs, a priority index for the uplink channel may be applied. This priority index may be indicated via DCI for a dedicated grant (DG) PUSCH, or via RRC signaling / DCI for a configured grant (CG) PUSCH. For HARQ-ACK information (e.g., A / N), the priority index may be set (e.g., RRC signaling) for each PUCCH resource on which the A / N is transmitted. For SR, the priority index may be set (e.g., RRC signaling) for each SR resource. Depending on the multiplexing capability of the terminal, multiplexing between uplink channels corresponding to different priority indices may be supported, or in a terminal that does not support such a capability, only the uplink channel corresponding to a higher priority index may be reported, and uplink channels corresponding to lower priority indices may be dropped. This existing priority index-based operation can be found in some detail in the section "Terminal Procedure for Control Information Reporting" mentioned above.

[0339] Although these existing priority index based operations do not distinguish / consider UEI CSI reporting, various examples of the present disclosure for setting / defining priority indices for uplink channels for UEI CSI reporting are described below.

[0340] For example, the priority index for the uplink channel for UEI CSI reporting can be set to a larger value (e.g., 1) than the existing one. Since the UE is the subject of measurement for CMR (e.g., CSI-RS / SSB), it can first / better identify the time-varying / current state of the beam / CSI. Therefore, the UEI beam report can be a more valid / utilizable report than the existing CSI report (which is preset by the base station). For this reason, the priority index for the uplink channel for UEI CSI reporting can be set to a larger value (e.g., 1). Alternatively, the UE may expect that the priority index for the uplink channel for UEI CSI reporting will be set to a larger value (e.g., 1).

[0341] For example, the priority index for an uplink channel for UEI CSI reporting may be set to a medium value (e.g., 0.5) between a larger value (e.g., 1) and a smaller value (e.g., 0).

[0342] For example, the priority index for an uplink channel for UEI CSI reporting can be set to a larger value (e.g., 2) than the existing larger value (e.g., 1). Accordingly, a higher priority than the existing priority index-based high priority can be set / defined for UEI CSI reporting. Since beam determination / change is very important for securing UL / DL coverage in higher frequency bands, this example can be applied in cases where reporting UEI beams / CSI is more important and urgent than transmitting URLLC data.

[0343] For example, the priority index for an uplink channel for UEI CSI reporting can be set to a smaller value (e.g., -1) than a conventional smaller value (e.g., 0). Accordingly, a lower priority can be set / defined for UEI CSI reporting than the conventional low priority based on the priority index. In the case of UEI CSI / beam reporting, since only the UE knows whether an event has occurred until the UE reports it to the network, the eNB cannot know in advance whether UEI CSI / beam reporting will be performed by the UE. Therefore, the eNB may have uncertainty in applying the priority rule. For example, it is difficult for the eNB to clearly determine which of the two operations to apply: assuming that UEI beam reporting is performed, applying the priority rule and expecting uplink reception accordingly, or assuming that UEI beam reporting is not performed, applying the priority rule and expecting uplink reception accordingly. To resolve this ambiguity, the priority index for the uplink channel for UEI CSI / beam reporting can be set to a new value that is lower than the existing priority indices, so that the uplink channel for UEI CSI / beam reporting is always dropped when it collides with other uplink channels. That is, the UEI CSI / beam reporting can be transmitted only when the uplink channel does not collide with other uplink channels.

[0344] Example 3

[0345] In a carrier aggregation environment, power may be allocated preferentially to the uplink channel of a carrier (or cell) with a higher priority, depending on the priority of uplink power allocation. In a non-carrier aggregation environment (e.g., a single-cell environment), power control is applied so as not to exceed the maximum transmission power of a terminal in a single cell. However, in a carrier aggregation environment (e.g., a multi-cell environment), even if power control is applied to each cell, if uplink scheduling is performed simultaneously on multiple cells, the maximum transmission power of the terminal may be exceeded. Therefore, the priority of uplink power allocation needs to be defined.

[0346] As described in the "Priority Handling for Transmit Power Reduction" section above, for PUCCH or PUSCH transmissions of the same priority index, a PUCCH transmission including CSI or a PUSCH transmission report including CSI is defined to have a lower power allocation order than a PUCCH transmission including HARQ-ACK information, and / or SR, and / or LRR, or a PUSCH transmission including HARQ-ACK information of the corresponding priority index, and a PUSCH transmission not including HARQ-ACK information or CSI of the corresponding priority index and, for a Type-2 random access procedure, a PUSCH transmission on the PCell.

[0347] For UEI CSI reporting, a power allocation order (or priority) may be set / defined that is distinct from the PUCCH transmission including existing CSI or the PUSCH transmission including CSI (hereinafter, non-UEI-initiated (or non-UEI) CSI reporting).

[0348] Example 3-1

[0349] UEI CSI reporting may be assigned / defined a higher priority than non-UEI CSI reporting. This may be applied in terms of power allocation order.

[0350] For example, the corresponding part of the "Priority Handling for Transmit Power Reduction" section mentioned above could be modified as follows:

[0351] - For PUCCH or PUSCH transmissions with the same priority index

[0352] -- PUCCH transmission including HARQ-ACK information, and / or SR, and / or LRR (link recovery request), or PUSCH transmission including HARQ-ACK information of the corresponding priority index.

[0353] -- PUCCH or PUSCH transmission including terminal-initiated CSI / beam report

[0354] -- PUCCH transmission including CSI or PUSCH transmission including CSI

[0355] -- PUSCH transmission on PCell for type-2 random access procedure and PUSCH transmission that does not include HARQ-ACK information or CSI of the corresponding priority index.

[0356] Because the UE is the primary measurement entity for CMR (e.g., CSI-RS / SSB), it can first and most effectively identify the time-varying / current status of beams / CSI. Therefore, UEI beam reports may be more valid and useful than existing CSI reports (which are preset by the base station). For this reason, it may be beneficial to prioritize UEI beam reports when conflicts with existing CSI reports arise.

[0357] Alternatively, the corresponding portion of the "Priority Handling for Transmit Power Reduction" section mentioned above may be modified as follows:

[0358] - For PUCCH or PUSCH transmissions with the same priority index

[0359] -- PUCCH or PUSCH transmission including terminal-initiated CSI / beam report

[0360] -- PUCCH transmission including HARQ-ACK information, and / or SR, and / or LRR (link recovery request), or PUSCH transmission including HARQ-ACK information of the corresponding priority index.

[0361] -- PUCCH transmission including CSI or PUSCH transmission including CSI

[0362] -- PUSCH transmission on PCell for type-2 random access procedure and PUSCH transmission that does not include HARQ-ACK information or CSI of the corresponding priority index.

[0363] Alternatively, the corresponding portion of the "Priority Handling for Transmit Power Reduction" section mentioned above may be modified as follows:

[0364] - For PUCCH or PUSCH transmissions with the same priority index

[0365] -- PUCCH transmission including HARQ-ACK information, and / or SR, and / or LRR (link recovery request), or PUSCH transmission including HARQ-ACK information of the corresponding priority index, or PUCCH or PUSCH transmission including terminal-initiated CSI / beam reporting.

[0366] -- PUCCH transmission including CSI or PUSCH transmission including CSI

[0367] -- PUSCH transmission on PCell for type-2 random access procedure and PUSCH transmission that does not include HARQ-ACK information or CSI of the corresponding priority index.

[0368] Example 3-2

[0369] UEI CSI reporting may be assigned / defined a lower priority than non-UEI CSI reporting. This may be applicable in terms of power allocation order.

[0370] For example, the corresponding part of the "Priority Handling for Transmit Power Reduction" section mentioned above could be modified as follows:

[0371] - For PUCCH or PUSCH transmissions with the same priority index

[0372] -- PUCCH transmission including HARQ-ACK information, and / or SR, and / or LRR (link recovery request), or PUSCH transmission including HARQ-ACK information of the corresponding priority index.

[0373] -- PUCCH transmission including CSI or PUSCH transmission including CSI

[0374] -- PUCCH or PUSCH transmission including terminal-initiated CSI / beam report

[0375] -- PUSCH transmission on PCell for type-2 random access procedure and PUSCH transmission that does not include HARQ-ACK information or CSI of the corresponding priority index.

[0376] Traditionally, the base station is the entity that manages the UL resources of all terminals in the cell and issues settings / instructions to the terminals, so it is desirable to give priority to dynamic CSI reports triggered by the base station over dynamic beam / CSI reports triggered by the terminals.

[0377] Alternatively, the corresponding portion of the "Priority Handling for Transmit Power Reduction" section mentioned above may be modified as follows:

[0378] - For PUCCH or PUSCH transmissions with the same priority index

[0379] -- PUCCH transmission including HARQ-ACK information, and / or SR, and / or LRR (link recovery request), or PUSCH transmission including HARQ-ACK information of the corresponding priority index.

[0380] -- PUCCH transmission including CSI or PUSCH transmission including CSI

[0381] -- PUSCH transmission on PCell for type-2 random access procedure and PUSCH transmission that does not include HARQ-ACK information or CSI of the corresponding priority index.

[0382] -- PUCCH or PUSCH transmission including terminal-initiated CSI / beam report

[0383] Alternatively, the corresponding portion of the "Priority Handling for Transmit Power Reduction" section mentioned above may be modified as follows:

[0384] - For PUCCH or PUSCH transmissions with the same priority index

[0385] -- PUCCH transmission including HARQ-ACK information, and / or SR, and / or LRR (link recovery request), or PUSCH transmission including HARQ-ACK information of the corresponding priority index.

[0386] -- PUCCH transmission including CSI or PUSCH transmission including CSI

[0387] -- PUSCH transmission that does not include HARQ-ACK information or CSI of the given priority index, and PUSCH transmission on PCell for type-2 random access procedure, or PUCCH or PUSCH transmission that includes terminal-initiated CSI / beam reporting.

[0388] Example 4

[0389] In the examples described above, the UEI CSI report (or UEI beam report) may be split into two reports (i.e., two-phase reports). The two reports may be transmitted sequentially on different time resources in TDM, or may be transmitted (simultaneously) on different frequency resources in FDM.

[0390] For example, a first report occasion that reports information about whether an event occurred itself and a second report occasion that reports beam information related to the event (e.g., beam-related report quantity or content such as CRI / SSB index and / or L1-RSRP / L1-SINR) can be set / defined distinctly in a TDM / FDM manner. The priorities for the first report occasion and the second report occasion may be set / defined in the same manner or in different manners.

[0391] For example, a first reporting opportunity may contain a relatively high level of information and may influence the presence or absence of a second reporting opportunity or the reporting quantity at the second reporting opportunity, so a first reporting opportunity may have a relatively high priority and a second reporting opportunity may have a relatively low priority.

[0392] For example, assuming that the aforementioned embodiment 2 is applied, a small priority index (e.g., 0) may be set / defined for the second reporting opportunity, and a large priority index (e.g., 1) may be set / defined for the first reporting opportunity.

[0393] For example, assuming that the aforementioned embodiment 3 is applied, for the second reporting opportunity, a priority equal to or lower than that of a PUCCH transmission including existing CSI or a PUSCH transmission including CSI may be set / defined, and for the first reporting opportunity, a priority higher than that of a PUCCH transmission including existing CSI or a PUSCH transmission including CSI may be set / defined.

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

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

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

[0397] A first device (100) includes 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) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure.

[0398] For example, the processor (102) may process information in the memory (104) to generate first information / signal and then transmit a wireless signal including the first information / signal through the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal through the transceiver (106) and then store information obtained from signal processing of the second information / signal in the memory (104).

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A step of receiving settings related to channel state information (CSI) reporting from the network by the terminal; and A step of transmitting, by the terminal to the network, one or more uplink channels based on a priority for a first uplink channel including a first terminal-initiated (UEI) CSI report and a priority for one or more second uplink channels, A method wherein the priority for the first uplink channel including the first UEI CSI report is based on one or more of event related information, a priority index, or a power allocation order.

2. In paragraph 1, The one or more second uplink channels include a second UEI CSI report, A method, wherein a first priority for the first UEI CSI report associated with a first type of event and a second priority for the second UEI CSI report associated with a second type of event are different.

3. In paragraph 2, A method, wherein the first priority and the second priority are included in two or more priorities for two or more event types.

4. In paragraph 1, The one or more second uplink channels include a second UEI CSI report, A method, wherein a first priority for the first UEI CSI report associated with an event at a first time point is different from a second priority for the second UEI CSI report associated with an event at a second time point.

5. In paragraph 1, The priority index for the first uplink channel including the first UEI CSI report is: Larger first priority index; A third priority index having a median value between the value of the first priority index and the value of the smaller second priority index; a fourth priority index greater than the value of the first priority index; or A fifth priority index that is less than the value of the second priority index above. A method having one of the values.

6. In paragraph 5, The value of the above first priority index is 1, The value of the above second priority index is 0, The value of the above third priority index is 0.5, The value of the above 4th priority index is 2, Method where the value of the above fifth priority index is -1.

7. In paragraph 1, For uplink channel transmissions having the same priority index, the power allocation order for the first uplink channel transmission including the first UEI CSI report is: A first order of uplink control channel transmission including at least one of hybrid automatic repeat request-acknowledgement (HARQ-ACK) information, scheduling request (SR), or link recovery request (LRR), or uplink shared channel transmission including HARQ-ACK information; A second order of uplink control channel transmission including CSI or uplink shared channel transmission including CSI; Third order of uplink channel transmission without HARQ-ACK information or CSI, and uplink shared channel transmission on the primary cell in a two-step random access procedure is identical to one of, or A method different from the first order, the second order, and the third order.

8. In paragraph 7, The power allocation order for the first uplink channel transmission including the first UEI CSI report is: The same order as the first order above, or the order before the first order above; The order after the first order and before the second order; A sequence after the second sequence and before the third sequence; or Same order as the third order above, or a order after the third order above One of the methods.

9. In paragraph 1, The above UEI CSI report includes a UEI beam report, A method wherein the beam report includes at least one of L1-RSRP (layer 1-reference signal received power), L1-SINR (layer 1-signal to interference plus noise ratio), and beam corresponding resource index.

10. In paragraph 1, A method wherein the UEI CSI report comprises at least one of a first report for occurrence of a specific event, or a second report including a beam report.

11. In Article 10, The priority for the above first report is the same as or different from the priority for the above second report.

12. In paragraph 11, A method wherein the priority for the first report is higher than the priority for the second report.

13. In paragraph 1, Based on the collision of transmissions of a plurality of uplink channels including the first uplink channel and the one or more second uplink channels: Among the above multiple uplink channels, the highest priority uplink channel transmission is performed, and the remaining one or more uplink channel transmissions are dropped; or Among the plurality of uplink channels, one or more uplink channel transmissions with a lower priority are dropped, and one or more uplink channel transmissions with a higher priority are multiplexed; or A method in which power is allocated in descending order from highest priority to lowest priority among the plurality of uplink channels.

14. One or more transceivers; and comprising one or more processors coupled to said one or more transceivers; One or more of the above processors: Receiving settings related to channel state information (CSI) reporting from the network via one or more of the transceivers; and A first uplink channel including a first terminal-initiated (UEI) CSI report and a priority for one or more second uplink channels are configured to be transmitted to the network via the one or more transceivers, The terminal wherein the priority for the first uplink channel including the first UEI CSI report is based on one or more of event related information, a priority index, or a power allocation order.

15. A step of transmitting settings related to channel state information (CSI) reporting from a base station to a terminal; and A step of receiving, by the base station, from the terminal, one or more uplink channels based on a priority for a first uplink channel including a first terminal-initiated (UEI) CSI report and a priority for one or more second uplink channels, A method wherein the priority for the first uplink channel including the first UEI CSI report is based on one or more of event related information, a priority index, or a power allocation order.

16. One or more transmitters / receivers; and comprising one or more processors coupled to said one or more transceivers; One or more of the above processors: Transmitting settings related to channel state information (CSI) reporting to the terminal via one or more of the transceivers; and A first uplink channel including a first terminal-initiated (UEI) CSI report and one or more uplink channels based on a priority for a first uplink channel and a priority for one or more second uplink channels are configured to be received from the terminal through the one or more transceivers, A base station, wherein the priority for the first uplink channel including the first UEI CSI report is based on one or more of event related information, a priority index, or a power allocation order.

17. One or more processors; and A processing device comprising one or more computer memories operatively connected to said one or more processors and storing instructions for performing a method according to any one of claims 1 to 13 based on execution by said one or more processors.

18. One or more non-transitory computer-readable media storing one or more instructions that are executed by one or more processors to control performing a method according to any one of claims 1 to 13.

Images