Method and device for performing uplink transmission / reception in wireless communication system

Abstract

Disclosed are a method and a device for performing uplink transmission / reception in a wireless communication system. A method according to an embodiment of the present disclosure may comprise the steps of: receiving, by a terminal, first configuration information related to an event from a base station; encoding, by the terminal, the information related to the event on a first uplink channel on the basis of second configuration information related to a scheduling request (SR) on the basis of the occurrence of the event; and on the basis that the first uplink channel overlaps a second uplink channel including the SR or a link recovery request (LRR), transmitting the first or second uplink channel to the base station by the terminal on the basis of the priority of the information related to the event. The priority of the information related to the event may be higher than or equal to the priority of the SR and may be lower than or equal to the priority of the LRR.

Description

Method and device for performing uplink transmission and reception in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for performing uplink transmission and reception in a wireless communication system.

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

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

[0004] The technical problem of the present disclosure is to provide a method and device for performing uplink transmission and reception in a wireless communication system.

[0005] In addition, an additional technical problem of the present disclosure is to provide a method and device for performing an event-based transmission and reception procedure.

[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 comprises the steps of: receiving, by a terminal, first configuration information related to an event from a base station; and encoding, by the terminal, the information related to the event on a first uplink channel based on second configuration information related to a scheduling request (SR) based on occurrence of the event; and transmitting, by the terminal, the first uplink channel or the second uplink channel to the base station based on a priority of information related to the event based on whether the first uplink channel overlaps with a second uplink channel including the SR or a link recovery request (LRR), wherein the priority of the information related to the event may be higher than or equal to a priority of the SR and lower than or equal to a priority of the LRR.

[0008] According to another embodiment of the present disclosure, a method comprises the steps of: transmitting, by a base station, first configuration information related to an event to a terminal; and, based on occurrence of the event, receiving, by the base station, from the terminal, i) a first uplink channel including information related to the event or ii) a second uplink channel including a scheduling request (SR) or a link recovery request (LRR), based on a priority related to the event, wherein the first uplink channel and the second uplink channel overlap in the same time resource, and the information related to the event is encoded on the first uplink channel based on second configuration information related to the SR, and a priority of the information related to the event may be higher than or equal to a priority of the SR and lower than or equal to a priority of the LRR.

[0009] According to various embodiments of the present disclosure, a method and apparatus for performing uplink transmission and reception in a wireless communication system can be provided.

[0010] Additionally, various embodiments of the present disclosure may provide a method and device for performing an event-based transmission and reception procedure.

[0011] Additionally, various embodiments of the present disclosure may reduce overhead associated with uplink resources for beam / CSI reporting in event-based transmission procedures.

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

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

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

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

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

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

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

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

[0020] FIG. 7 is a flowchart illustrating a method for a terminal to perform a communication procedure according to an embodiment of the present disclosure.

[0021] FIG. 8 is a flowchart illustrating a method for a base station to perform a communication procedure according to an embodiment of the present disclosure.

[0022] FIG. 9 is a diagram for explaining a signaling process according to one embodiment of the present disclosure.

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

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

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

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

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

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

[0029] The present disclosure describes a wireless communication network or a wireless communication system, and operations performed in the 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 in a process of transmitting or receiving a signal to or between terminals connected to the wireless network.

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

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

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

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

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

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

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

[0037] - BM: beam management

[0038] - CQI: Channel Quality Indicator

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

[0040] - CSI: Channel State Information

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

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

[0043] - DMRS: Demodulation Reference Signal

[0044] - FDM: frequency division multiplexing

[0045] - FFT: fast Fourier transform

[0046] - IFDMA: interleaved frequency division multiple access

[0047] - IFFT: inverse fast Fourier transform

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

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

[0050] - MAC: Medium Access Control

[0051] - NZP: non-zero power

[0052] - OFDM: orthogonal frequency division multiplexing

[0053] - PDCCH: Physical downlink control channel

[0054] - PDSCH: Physical downlink shared channel

[0055] - PMI: precoding matrix indicator

[0056] - RE: resource element

[0057] - RI: Rank indicator

[0058] - RRC: Radio Resource Control

[0059] - RSSI: Received signal strength indicator

[0060] - Rx: Reception

[0061] - QCL: quasi co-location

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

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

[0064] - TDM: Time Division Multiplexing

[0065] - TRP: transmission and reception point

[0066] - TRS: Tracking Reference Signal

[0067] - Tx: transmission

[0068] - UE: user equipment

[0069] - ZP: Zero Power

[0070] System General

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0088] Fig. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied. Referring to Fig. 3, the resource grid is N in the frequency domain. RB μ N sc RB It consists of subcarriers, and one subframe is 14·2 μ It is described as an example, but not limited to, that it consists of OFDM symbols. In an NR system, the transmitted signal is N RB μ N sc RB One or more resource grids consisting of subcarriers and 2 μ N symb (μ) is described by OFDM symbols. Here, N RB μ ≤N RB max,μ is. The above NRB max,μ represents the maximum transmission bandwidth, which may vary not only between numerologies but also between uplink and downlink. In this case, one resource grid may be configured 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').

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

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

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

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

[0093] Common resource blocks (CRBs) are numbered from 0 upwards in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of CRB 0 for a subcarrier spacing setting μ coincides with 'point A'. 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.

[0094]

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

[0096]

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

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

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

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

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

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

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

[0104] 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. However, since the UE may not receive the configuration for the DL / UL BWP when performing the initial access process or before the RRC connection is set up, the DL / UL BWP assumed by the UE in such a situation is defined as the initially active DL / UL BWP.

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

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

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

[0108] A terminal that has completed an 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).

[0109] 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 random access channel (RACH) (steps S603 and S605) and receive a response message to the preamble via the PDCCH and the corresponding PDSCH (steps S604 and S606). In the case of a contention-based RACH, a contention resolution procedure may additionally be performed.

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

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

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

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

[0114] 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 control information included in each DCI format may be predefined.

[0115] DCI format 0_0 is used for scheduling PUSCH in a cell. The information included in DCI format 0_0 is transmitted after being CRC (cyclic redundancy check) scrambled by the cell radio network temporary identifier (C-RNTI), the configured scheduling RNTI (CS-RNTI), or the modulation coding scheme cell RNTI (MCS-C-RNTI). DCI format 0_1 ​​is used to schedule one or more PUSCHs in a cell, or to indicate configured grant (CG) downlink feedback information to a UE. The information included in DCI format 0_1 ​​is transmitted after being CRC scrambled by the C-RNTI, the CS-RNTI, the semi-persistent CSI RNTI (SP-CSI-RNTI), or the MCS-C-RNTI. DCI format 0_2 is used for scheduling PUSCH in a cell. Information included in DCI format 0_2 is transmitted CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

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

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

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

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

[0120] Basic beam failure recovery (BFR)

[0121] The terminal and / or base station may perform uplink / downlink beam management (BM) for data transmission and reception. Here, BM may refer to the process of acquiring and maintaining a beam set that can be used for downlink and uplink transmission / reception.

[0122] Specifically, the BM may include a beam measurement process for measuring the characteristics of a beam forming signal received from a base station or a terminal, a beam determination process for determining a transmission beam (Tx beam) and a reception beam (Rx beam) of the base station or the terminal itself, a beam sweeping process for covering a spatial area using the transmission beam and / or the reception beam for a predetermined time interval in a predetermined manner, and a beam reporting process for the terminal to report information on the beam signal to the base station based on the beam measurement result.

[0123] During the above-described uplink / downlink beam matching (BM) process, beam mismatch issues may arise due to various factors. For example, if the terminal moves or rotates, or if the wireless channel environment changes due to the movement of surrounding objects (e.g., if the environment changes from a line-of-sight (LoS) environment to a non-LoS environment due to a beam block), the optimal uplink / downlink beam pair may change. In this case, if the terminal or base station fails to track the changed optimal uplink / downlink beam pair (i.e., BM tracking), it can be considered that a beam failure has occurred.

[0124] The terminal can determine whether a beam failure has occurred based on the reception quality of the downlink reference signal (RS). The terminal must then report a beam failure occurrence report message or a beam failure recovery request message (BFRQ) to the base station. Upon receiving the message, the base station can perform a beam recovery process through various processes, such as beam RS transmission or a beam report request. This series of beam recovery processes is called the beam failure recovery (BFR) process.

[0125] The basic BFR operation includes a BFR process for a special cell (SpCell) (i.e., a primary cell (PCell) or a primary secondary cell (PScell)) in which contention-based PRACH resources exist. The BFR process consists of a UE beam failure detection (BFD) process, a BFRQ transmission process, and a process for monitoring a base station's response to the BFRQ, and each process can be performed within a serving cell.

[0126] Beam failure detection (BFD)

[0127] If the quality value (Q_out) of all PDCCH beams falls below a predefined value, it can be considered that a beam failure instance has occurred. Here, the quality value can be determined based on the theoretical BLER (block error rate). In other words, the theoretical BLER can mean the probability that demodulation of control information will fail when the control information is transmitted through a specific PDCCH.

[0128] In addition, one or more search spaces for monitoring PDCCHs can be set for the terminal, and different PDCCH beams can be set for each search space. In this case, the quality values ​​of all PDCCH beams falling below a predefined value means that the quality values ​​of all PDCCH beams fall below the BLER threshold.

[0129] Two methods described below can be supported in which the terminal receives instructions / configuration from the base station for BFD-RS to determine whether a beam failure instance has occurred.

[0130] In the first method, an implicit configuration method of BFD-RS can be supported. A control resource set (CORESET) ID, which is a resource region in which a PDCCH can be transmitted, is set for each search space, and RS information (e.g., CSI-RS resource ID, SSB ID) that is QCLed from a spatial RX parameter perspective can be indicated / set for each CORESET ID. The RS that is QCLed from a spatial RX parameter perspective can be indicated or set through transmit configuration information (TCI). That is, BFD-RS can be implicitly set / instructed to a terminal based on the QCL information indicated or set through TCI.

[0131] Here, when the base station instructs or configures the terminal to use an RS that is QCLed in terms of spatial reception parameters (i.e., QCL Type D RS), the terminal can use the beam used for reception of the RS that is QCLed in terms of spatial reception parameters when receiving a specific PDCCH DMRS. That is, signals can be transmitted between spatially QCLed antenna ports through the same transmission beam or similar transmission beams (e.g., beam directions are the same / similar but beam widths are different).

[0132] Second, explicit configuration of BFD-RS can be supported. The base station can explicitly configure or instruct the terminal to configure or instruct the beam RS for BFD purposes. In this case, the beam RS may correspond to the aforementioned "all PDCCH beams."

[0133] The terminal physical layer can notify the MAC sublayer that a beam failure instance (BFI) has occurred whenever an event occurs in which the theoretical BLER measured based on the configured (or indicated) BFD-RS degrades beyond a certain threshold. In addition, the terminal MAC sublayer can determine that a beam failure has occurred and initiate a related RACH operation if the BFI occurs a certain number of times (e.g., 'beamFailureInstanceMaxCount') within a certain time (e.g., 'BFD timer').

[0134] BFRQ (PRACH-based): New beam identification and PRACH transmission

[0135] As described above, if a certain number of BFIs occur, the terminal may determine that a beam failure has occurred and perform a beam failure recovery operation. As an example of a beam failure recovery operation, the terminal may perform a beam failure recovery procedure based on the RACH (i.e., PRACH). The BFRQ procedure will be described in detail below.

[0136] The base station can set a candidate beam RS list ('candidateBeamRSList') including candidate beam RSs that can be replaced when a beam failure occurs, to the terminal through RRC signaling. Then, the base station can set a dedicated PRACH resource for the candidate beam RSs. At this time, the dedicated PRACH resource can be a non-contention based PRACH resource (or, contention free PRACH resource). If a replacement beam RS is not found in the candidate beam RS list, the terminal can select at least one of the preset SSB resources. Then, the terminal can transmit a contention-based PRACH to the base station based on at least one of the selected beam RSs.

[0137] Improved beam failure recovery

[0138] When carrier aggregation (CA) is applied, a specific SCell may not have an uplink carrier (UL carrier). That is, uplink transmission is not possible for an SCell with only a downlink carrier. Furthermore, even if an SCell has an uplink carrier, a collision-based PRACH cannot be established. Therefore, the PRACH-based BFR process with CA applied can only be applied to SpCells (PCells or PSCells), and BFR may not be supported on SCells. In other words, according to basic BFR operations, PRACH-based BFR operations on SpCells may not be supported on SCells.

[0139] Specifically, if a high-frequency band requiring BFR is configured as an SCell, PRACH-based BFR procedures may not be supported in that high-frequency band. For example, if a PCell is operated in a low-frequency band (e.g., 6 GHz or lower) while an SCell is operated in a high-frequency band (e.g., 30 GHz), the PRACH-based BFR procedure may not be supported in the high-frequency band where BFR support is more necessary.

[0140] To address the aforementioned issues, the improved BFR operation includes operations for BFR of the SCell. For example, a terminal can perform BFRQ for the SCell using dedicated PUCCH resources configured for BFRQ in the SpCell. For convenience, the "dedicated PUCCH resources" will hereinafter be referred to as BFR-PUCCH.

[0141] The role of the above BFR-PUCCH is to report only "BF occurrence information for SCells" to the base station. Further details regarding the BF occurrence can be transmitted to the base station as a follow-up report via the BFR MAC-CE or UCI.

[0142] Here, the detailed information transmitted as the follow-up report may include information about the SCell(s) where the BF occurred (e.g., CC (component carrier) index information), whether a new candidate beam exists for the SCell(s) where the BF occurred, and, if a new candidate beam exists, the corresponding beam RS ID.

[0143] In addition, the BFR-PUCCH uses the same PUCCH format as the SR (scheduling request) and can be defined through the ID of a specific SR for BFR purposes. If the UL-SCH allocated from the base station exists when the terminal detects a BF for the SCell, the terminal can skip the BFR-PUCCH transmission procedure, similar to the SR transmission procedure, and directly transmit the BFR MAC-CE to the base station through the allocated UL-SCH.

[0144] In a multi-TRP environment, multi-DCI and / or single-DCI based TRP-specific BFR operations can be applied. First, the base station can explicitly or implicitly configure BFD RS for the terminal. For example, the base station can configure two or more BFD-RS sets for the terminal via RRC and / or MAC-CE. In another example, the BFD-RS sets can be configured based on the TCI status of each CORESET pool. The terminal can determine whether a beam fails for each TRP based on the BFD-RS sets described above.

[0145] When a beam failure is detected, SR PUCCH resources can be set for the UE according to the BFRQ resources of the base station. Separate SR PUCCH resources can be set for each TRP, or the same SR PUCCH resource can be used by two TRPs. When a beam failure occurs in a specific TRP, the UE can transmit the set BFRQ SR PUCCH (to a TRP where the beam failure did not occur). The TRP that receives the BFRQ can transmit a UL grant DCI to the UE, and the UE can transmit a BFR MAC-CE through the PUSCH scheduled / allocated by the UL grant DCI. The BFR MAC-CE can include a list of CCs where a beam failure occurred, information about the failed BFD RS set, and information about whether a new beam has been generated.

[0146] PUCCH configuration and format

[0147] PUCCH can carry uplink control information (UCI). UCI can include SR, HARQ-ACK, CSI, etc. SR can be used to request UL-SCH resources. HARQ-ACK is a reception response signal for a DL signal. HARQ-ACK response can include ACK, NACK (negative acknowledgment), DTX (discontinuous transmission), NACK / DTX. HARQ-ACK can be used interchangeably with A / N, ACK / NACK, and HARQ-ACK / NACK. HARQ-ACK can be generated on a TB basis or a CBG basis.

[0148] PUCCH formats can be distinguished based on UCI payload size, transmission length (e.g., the number of symbols constituting a PUCCH resource), and transmission structure. PUCCH formats can be classified into short PUCCH (formats 0 and 2) and long PUCCH (formats 1, 3, and 4) based on transmission length.

[0149] For example, when the PUCCH format is 0, the supportable UCI payload size is at most 2 bits, and the number of OFDM symbols constituting a single PUCCH may be 1 to 2. As another example, when the PUCCH format is 2, the supportable UCI payload size is greater than 2 bits, and the number of OFDM symbols constituting a single PUCCH may be 1 to 2.

[0150] As another example, when the PUCCH format is 1, the supportable UCI payload size is at most 2 bits, and the number of OFDM symbols constituting a single PUCCH may be 4 to 14. As another example, when the PUCCH format is 3 or 4, the supportable UCI payload size is greater than 2 bits, and the number of OFDM symbols constituting a single PUCCH may be 4 to 14.

[0151] SR (scheduling request)

[0152] SR can be used to request UL-SCH resources for new transmissions. A terminal (e.g., its MAC entity) can be configured with zero or more SR configurations. An SR configuration can consist of a set of PUCCH resources for SR across different BWPs and cells.

[0153] For logical channel or SCell beam failure recovery and consistent listen before talk (LBT) failure recovery, PUCCH resources for SR may be configured at most 1 per BWP. For logical channels providing radio bearers configured with small data transmission (SDT), PUCCH resources for SR may not be configured for SDT. For beam failure recovery of a BFD-RS set of a serving cell, PUCCH resources for SR may be configured at most 2 per BWP. For positioning measurement gap activation / deactivation requests, dedicated SR configurations may be configured.

[0154] Each SR configuration may correspond to one or more logical channels and / or SCell beam failure recovery and / or consistent LBT failure recovery and / or beam failure recovery of a BFD-RS set and / or position measurement gap enable / disable request. Each logical channel, SCell beam failure recovery, beam failure recovery of a BFD-RS set and consistent LBT failure recovery may be mapped to zero or one SR configuration configured in RRC. The SR configuration of a logical channel that triggered BSR or DSR or SCell beam failure recovery or beam failure recovery of a BFD-RS set or consistent LBT failure recovery (if such configuration exists) or position measurement gap enable / disable request may be considered as an SR configuration corresponding to the triggered SR. Any SR configuration can be used for pre-emptive BSR or SR triggered by timing advance reporting.

[0155] Event-based / triggered transmission and reception procedures

[0156] In describing the present disclosure, " / " means "and", "or", or "and / or" depending on the context. In addition, "beam" in the present disclosure may mean a source RS for a "spatial filter" or a "spatial relationship", and may be interpreted as a QCL (type-D) RS, a (DL / UL / joint) TCI state, or (in the case of uplink) a spatial relationship RS.

[0157] In wireless communication systems, Layer-1 (e.g., physical layer)-based uplink control information has the advantage of shorter transmission delay compared to higher-layer-based control information. For example, when a terminal transmits information to a base station via a MAC-CE or RRC message, the terminal may require an SR procedure and the base station's PUSCH allocation procedure (based on the SR), resulting in delay and overhead. Furthermore, higher-layer information generally requires longer decoding time (e.g., decoding time and / or processing time).

[0158] On the other hand, in order to transmit layer-1 based uplink control information, UL physical channel resources (e.g., PUCCH, PUSCH) must be (preliminarily) set / allocated to the corresponding terminal. Therefore, from the base station / network's perspective, as the number of terminals increases, the amount of UL resources to be allocated to each terminal may increase, and the overall UL resource overhead burden may increase accordingly.

[0159] Accordingly, in a wireless communication system, information that must be transmitted relatively urgently for the operation of the physical layer, etc. (e.g., SR (e.g., SR for PUSCH allocation), HARQ-ACK (e.g., HARQ-ACK for retransmission), CSI (e.g., CSI for scheduling / MCS / precoder decision), beam information (e.g., beam information for (analog) beam decision) can be transmitted and received as physical layer UCI.

[0160] Here, the base station and / or the network can determine / control the reporting timing of HARQ-ACK, CSI, beam information, etc., excluding SR. If this NW (network)-initiated / triggered reporting procedure is applied, there is a limitation that in an environment where the wireless channel condition is likely to change rapidly / highly, the reporting timing must be set / instructed so that the terminal can transmit UCI frequently.

[0161] That is, in an environment where the wireless channel conditions change rapidly, the UL resource overhead for UCI reporting and the related DL measurement RS overhead may increase, and there may also be a problem that the power consumption of the terminal increases due to the frequent UL transmission of the terminal. Additionally or alternatively, the UL resource overhead may increase as the number of terminals within the cell / TRP coverage increases, as each terminal must be allocated UL resources.

[0162] To overcome the limitations of these NW-initiated / triggered reports, UE-initiated / triggered reporting schemes or event-based / triggered reporting schemes may be applied.

[0163] When UE-initiated / triggered reporting or event-based / triggered reporting is applied, the terminal can determine whether and when to report (e.g., UCI). That is, the terminal can perform the (UCI) reporting only when necessary (e.g., only when a specific event occurs). This can reduce UL resource overhead and terminal power consumption. Furthermore, since the terminal reports information based on Layer 1 / lower layers, faster reporting can be achieved.

[0164] Accordingly, standardization of UE-initiated / triggered beam reporting methods may be pursued in next-generation wireless communication systems.

[0165] Additionally, for efficient operation of UL resources in next-generation wireless communication systems, UE-initiated / triggered or event-based transmission schemes may be specifically applied to control information, transport blocks (TBs), and user-plane data transmission procedures transmitted via UCI and / or MAC-CE.

[0166] Examples of event-based or terminal-initiated / triggered transmission / reception procedures in wireless communication systems include SR and BFR reporting methods. SR reporting involves reporting whether PUSCH allocation is required for UL-SCH transmission.

[0167] For example, the BFR reporting method includes an operation of reporting whether a BF has occurred and new beam-related information. Here, the BF occurrence and new beam-related information may be conveyed / transmitted to the base station in an explicit or implicit manner (e.g., by conveying a new beam index as PRACH resource selection information). In addition, the BF occurrence and new beam-related information may be transmitted all at once or in multiple stages via one or two UL resources. For example, the terminal may transmit a BFRQ to the base station via the PUCCH and transmit beam information to the base station via the MAC-CE on the PUSCH.

[0168] In describing the present disclosure, information (e.g., SR, BFRQ, new beam information, etc.) that a terminal transmits to a network via an event-based and / or terminal-initiated / triggered transmission method is collectively referred to as “event information.”

[0169] Event information can be composed of one or more information parts / blocks, and encoding / rate matching / RE mapping can be performed on a per-part / block basis. Furthermore, each information part / unit can be transmitted via different transmission methods. For example, BFRQ can be transmitted and received as an L1 message via UCI, and new beam information can be transmitted and received as an L2 message via MAC-CE.

[0170] This disclosure focuses on, but is not limited to, event-based or terminal-initiated / triggered beam reporting. The method described herein can also be applied to other event-based or terminal-initiated / triggered transmission and reception procedures (e.g., UCI / CSI / MAC-CE reporting procedures, uplink transmission and reception procedures, etc.).

[0171] In describing the present disclosure, "beam" may be interpreted / replaced as a source RS for a "spatial filter" or a "spatial relationship", or as a QCL (Type D) RS, a TCI state, or (in the case of uplink) a spatial relationship RS. Additionally, a "serving beam" may include a beam associated with a PDCCH / PDSCH.

[0172] Below, we describe how to support UE-initiated / triggered transmission / reception schemes (e.g., reporting schemes) or event-based / triggered transmission / reception schemes (e.g., reporting schemes) and improve reliability.

[0173] FIG. 7 is a flowchart illustrating a method for a terminal to perform a communication procedure according to an embodiment of the present disclosure.

[0174] The terminal can receive first setting information related to the event from the base station (S710).

[0175] For example, the first configuration information related to an event may include at least one of information about the type of the event, a criterion related to the event, a type of information to be reported upon occurrence of the event (e.g., information related to the event), and information about resources of an uplink channel for reporting the information related to the event (e.g., (CG) PUSCH, PUCCH, etc.). That is, the event-related configuration information may include a criterion and / or threshold for determining whether an event has occurred or / and a type of event, etc. The terminal may monitor whether an event configured according to the first configuration information has occurred. Here, the first uplink channel may include (configured grant (CG)) PUSCH or / and PUCCH, etc.

[0176] Based on the occurrence of an event, the terminal may encode information related to the event on a first uplink channel based on second configuration information related to a scheduling request (SR) (S720).

[0177] The type of information related to an event may vary depending on the type of event occurring and may be set or predefined by the first configuration information. For example, if the event is related to a beam report, the information related to the event may include beam report information (e.g., information about a new / serving beam), information related to whether beam report information is included on an uplink channel transmitted after the first uplink channel, etc. Here, the information related to the event may be included in uplink control information (UCI).

[0178] For example, if the first uplink channel includes information regarding whether beam report information is included on an uplink channel (e.g., a third uplink channel) transmitted after the first uplink channel, the terminal may transmit the third uplink channel including the beam report information to the base station. In addition, the encoding method related to the beam report information may also be applied to the encoding / multiplexing / mapping method applied to SR, as described below, but is not limited thereto.

[0179] As an example of the present disclosure, information related to an event may be encoded / mapped by a terminal on a first uplink channel based on second configuration information related to a scheduling request (SR). Here, the second configuration information related to the SR may include, but is not limited to, at least one of a period, an offset, a priority, a resource, an encoding method, or an identifier (ID) of the SR.

[0180] Additionally or alternatively, information related to the event may be encoded / mapped / multiplexed onto the first uplink channel according to a predefined encoding / mapping / multiplexing scheme for SR.

[0181] That is, information related to the event can be mapped / multiplexed / encoded on the first uplink channel based on the RE mapping / multiplexing / encoding scheme applied to the SR.

[0182] Based on whether the first uplink channel overlaps with the second uplink channel including SR or LRR (on the same time / frequency resources), the terminal may transmit the first uplink channel or the second uplink channel to the base station based on the priority of the information related to the event (S730). As an example of the present disclosure, the priority of the information related to the event may be higher than or equal to the priority of the SR and lower than or equal to the priority of the link recovery request (LRR) (or, BFRQ). Accordingly, when the first uplink channel including the information related to the event overlaps with the second uplink channel including the SR or / and LRR, the terminal may determine the uplink channel to be transmitted preferentially based on the priority of each piece of information.

[0183] For example, based on the overlap of a first uplink channel with a second uplink channel including SR, the terminal may transmit the first uplink channel to the base station with priority based on the priority of information related to the event. That is, the second uplink channel (or SR) may be dropped. For example, based on the overlap of a first uplink channel with a second uplink channel including LRR, the terminal may transmit the second uplink channel to the base station with priority based on the priority of information related to the event. That is, the first uplink channel (or information related to the event) may be dropped.

[0184] Additionally or alternatively, the terminal may repeatedly transmit event-related information to the base station. For example, the first configuration information may include information related to the transmission cycle of the event-related information (e.g., the cycle of transmission occasions (TOs) for transmitting event-related information, etc.) and / or the number of transmissions (e.g., the number of TOs for transmitting event-related information, etc.).

[0185] However, this is merely an example, and information related to the transmission cycle and / or number of transmissions of event-related information may be transmitted to the terminal via separate configuration information. The terminal may repeatedly transmit event-related information to the base station based on the transmission cycle and number of transmissions of event-related information.

[0186] Additionally or alternatively, a timer associated with the retransmission of event-related information (e.g., an event-related timer) may be initiated based on the transmission of the first uplink channel to the base station. The time period for the event-related timer may be set by, but is not limited to, timer-related configuration information transmitted from the base station, and may be predefined.

[0187] Based on the fact that a response message regarding event-related information is not received from the base station before the timer expires, the terminal may retransmit the event-related information to the base station. Based on the fact that a response message regarding event-related information is received from the base station before the timer expires, the timer may be stopped / suspended, and the terminal's retransmission (or preparation / standby for retransmission) of the event-related information may be stopped / suspended. Here, the response message may include an ACK (acknowledgement) message for the first uplink channel, etc.

[0188] Additionally or alternatively, downlink control information associated with the first uplink channel (e.g., control information for scheduling the first uplink channel or / and activating resources associated with the first uplink channel) may include an (open-loop) power control parameter set indication field. Power of the first uplink channel may be determined based on the power control parameter set indication field. For example, when an SRI (SRS resource indicator) is included in the downlink control field, the power control parameter set indication field value may be set to 1. When the SRI is not included in the downlink control field, the power control parameter set indication field value may be set to 01 or 10.

[0189] Additionally or alternatively, the terminal may receive downlink control information related to the first uplink channel from the base station. At this time, the terminal may transmit an ACK message for the downlink control information to the base station.

[0190] The method described in the example of FIG. 7 may be performed by the first device (100) of FIG. 10. For example, one or more processors (102) of the first device (100) of FIG. 10 may receive first configuration information related to an event from a base station through one or more transceivers (106). Based on the occurrence of an event, the one or more processors (102) may encode the information related to the event onto a first uplink channel based on second configuration information related to SR. Based on whether the first uplink channel overlaps with a second uplink channel including SR or LRR, the one or more processors (102) may transmit the first uplink channel or the second uplink channel to the base station through one or more transceivers (106) based on a priority of the information related to the event.

[0191] Furthermore, one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 7 or the examples described below when executed by one or more processors (102).

[0192] FIG. 8 is a flowchart illustrating a method for a base station to perform a communication procedure according to an embodiment of the present disclosure.

[0193] The base station may receive first configuration information related to an event from the terminal (S810). Specifically, the base station may transmit first configuration information related to the event and / or configuration information related to the first uplink channel to the terminal. Examples of configuration information have been described with reference to FIG. 7, so a redundant description will be omitted.

[0194] Upon occurrence of an event, the base station may receive from the terminal i) a first uplink channel containing information related to the event, or ii) a second uplink channel containing a scheduling request (SR) or a link recovery request (LRR) based on a priority associated with the event (S820). At this time, the information related to the event may be encoded on the first uplink channel based on second configuration information related to the SR or according to a predefined method related to the SR. In addition, the first uplink channel and the second uplink channel may overlap in the same time resource.

[0195] For example, based on the overlap of a first uplink channel with a second uplink channel including SR, the base station may receive the first uplink channel from the terminal based on the priority of information related to the event. In another example, based on the overlap of a first uplink channel with a second uplink channel including LRR, the base station may receive the second uplink channel from the terminal based on the priority of information related to the event.

[0196] The method described in the example of FIG. 8 may be performed by the second device (200) of FIG. 10. For example, one or more processors (202) of the second device (200) of FIG. 10 may transmit first configuration information related to an event to a terminal via one or more transceivers (206). Based on the occurrence of an event, the one or more processors (202) may receive a first uplink channel including information related to the event or ii) a second uplink channel including SR or LRR from the terminal via one or more transceivers (106) based on a priority related to the event.

[0197] Furthermore, one or more memories (204) of the second device (200) may store instructions for performing the method described in the example of FIG. 8 or the examples described below when executed by one or more processors (202).

[0198] Below, we will describe in more detail the UE-initiated / triggered transmission / reception method (e.g., reporting method, etc.) or the event-based / triggered transmission / reception method.

[0199] Event-based beam reporting schemes may include UCI-based beam reporting schemes (method 1), MAC-CE-based beam reporting schemes (method 2), and PRACH-based beam reporting schemes (method 3).

[0200] UCI-based beam reporting method

[0201] As an example of the present disclosure, a UCI-based beam reporting operation may be performed via a dedicated SR PUCCH for reporting an event occurrence (method 1-1). For example, for event-related reporting, the dedicated SR PUCCH may include information (e.g., UCI) for reporting the event occurrence, and the terminal may transmit the dedicated SR PUCCH to the base station. Thereafter, the terminal may transmit information related to the beam reporting (e.g., information about a new beam ID via CRI / SSBRI, information about a beam quality value via L1-RSRP / SINR, etc.) to the base station (via an uplink control channel, etc.). That is, the UCI-based beam reporting operation may be performed in two steps.

[0202] Additionally or alternatively, the terminal may transmit a MAC-CE to the base station via the allocated PUSCH, and the MAC-CE may include information for reporting an event occurrence and / or information related to beam reporting (method 1-1a). That is, similar to the improved beam failure recovery operation described above, information for reporting an event occurrence and / or information related to beam reporting may be transmitted to the base station.

[0203] Additionally or alternatively, regular UCI may include information for reporting event occurrences and / or information related to beam reporting (method 1-1b). In this case, the SR transmitted by the terminal may request beam reporting triggering from the AP rather than UL-SCH allocation.

[0204] As an example of the present disclosure, UCI-based beam reporting can be performed via a dedicated / configured CSI PUCCH (method 1-2). Method 1-2 extends the SR PUCCH scheme to an event-based beam reporting scheme. (Some) CSI PUCCH resources can be configured for event-based reporting, such as P / SP CSI reporting on the PUCCH, but the UE can determine whether to transmit CSI at each transmission occasion.

[0205] As an example of the present disclosure, UCI-based beam reporting operation can be performed via established PUSCH (method 1-3).

[0206] As an example of the present disclosure, when CG PUSCH resources based on CG PUSCH Type 1 are configured via RRC signaling, or CG PUSCH resources based on CG PUSCH Type 2 are configured / indicated via RRC signaling and DCI, the UE may transmit CSI (together with UL-SCH) to the base station when an event occurs in the corresponding CG PUSCH resource (method 1-3a).

[0207] As another example of the present disclosure, the terminal may transmit CSI to the base station via SP CSI PUSCH resources configured / indicated via RRC signaling and DCI when an event occurs (method 1-3b).

[0208] MAC-CE based beam reporting method

[0209] A normal SR can be used to request PUSCH allocation. Then, operations according to method 1-1a described above can be performed. For example, the MAC-CE can include information for reporting event occurrences and / or information related to beam reporting.

[0210] PRACH-based beam reporting method

[0211] As an example of the present disclosure, a PRACH-based beam reporting method may be utilized to report an event occurrence (method 3-1). In this case, the PRACH transmission procedure may include a contention-based PRACH transmission procedure or a non-contention-based PRACH transmission procedure. In particular, when a non-contention-based PRACH transmission procedure is performed, a connection relationship between a new beam and a PRACH resource / occasion can be established, similar to a BFR procedure. Through this, not only the event occurrence but also information about the new beam can be transmitted to the terminal via the PRACH (selected by the terminal).

[0212] Additionally or alternatively, beam information may be transmitted to the base station via MAC-CE or UCI, such as in Methods 1-1a and 1-1b.

[0213] As another example of the present disclosure, a beam reporting method may be performed based on a PUSCH following a PRACH (e.g., similar to the Msg. A transmission procedure of a contention-based 2-step RACH) (method 3-2). For example, when an event occurs, the terminal may select a PRACH preamble and transmit the selected PRACH preamble to the base station. Then, the terminal may perform beam reporting through the PUSCH connected to the PRACH preamble. For example, the PRACH preamble may include information related to whether an event has occurred, and the PUSCH may include CSI / UCI information, etc.

[0214] When Methods 3-1 and 3-2 are applied, the base station may transmit an ACK for information related to the occurrence of an event to the terminal via a response to the PRACH (e.g., RAR MAC-CE). Additionally or alternatively, the base station may direct / change the beam of the terminal based on new beam information transmitted via the PRACH.

[0215] Example 1

[0216] Event-based transmission or related UL channel resource activation via DCI may be applied. Furthermore, this method may be applied to the methods described above.

[0217] For example, the SP CSI reporting method via PUSCH, such as method 1-3b, can be utilized / applied to an event-based / reporting method. For example, if PUSCH resources for SP CSI are activated, the UE can perform event-based reporting via the activated PUSCH resources.

[0218] As another example, the CG PUSCH (Type 2) scheme, like scheme 1-3a, can be utilized for event-based UCI / MAC-CE reporting. While the CG PUSCH scheme in a basic wireless communication system is intended for TB transmission, the scheme described above can be used for beam / CSI reporting. Beam / CSI reporting information can be transmitted to the base station via UCI / MAC-CE.

[0219] As described above, let's assume that event-based transmission or the associated UL channel resources are activated via DCI. In this case, even if the terminal fails to detect / decode the DCI, the base station may incorrectly determine that the resource is activated, which is problem #1.

[0220] Embodiment 1 relates to a method for solving problem #1. In one embodiment of the present disclosure, when event-based transmission / reporting or channel resources related thereto are activated by DCI, the terminal can perform CSI / beam reporting or transmit an ACK for the DCI to the base station at the first transmission / reporting time after receiving the DCI, regardless of whether an event has occurred.

[0221] For example, assume that CG PUSCH type 1 / 2 is set by RRC signaling as in method 1-3a, and (specific) CG PUSCH resources are activated by DCI. The UE may receive the DCI (regardless of whether an event occurs) and perform a CSI / beam reporting procedure based on the (specific) CG PUSCH resources activated by the DCI at the time of the first transmission / report, or transmit an ACK for the DCI to the base station.

[0222] As another example, assume that PUSCH resources for SP CSI transmission are configured by RRC signaling, as in method 1-3b, and the corresponding PUSCH resources are indicated / activated by DCI. The UE may receive the DCI (regardless of whether an event has occurred) and, at the time of the first transmission / report, perform the CSI / beam reporting procedure based on the PUSCH resources activated / indicated by the DCI, or transmit an ACK for the DCI to the base station.

[0223] Example 2

[0224] Even if the terminal performs an event-based transmission / reporting operation, the base station may not be able to detect / decode the terminal's event report. In other words, problem #2 may occur, in which the terminal performs an event-based transmission / reporting operation, but the base station may not be able to detect the terminal's operation. For example, when methods 1-2, 1-3, and 3-2 are applied, problem #2 may occur with respect to the transmission of (some) event information.

[0225] Detailed embodiments of Embodiment 2 relate to a method for solving problem #2. When transmitting event-based beam information, the terminal may perform an operation according to at least one of Embodiments 2-1, 2-2, 2-3, and 2-4. For example, the operations according to at least one of Embodiments 2-1, 2-2, 2-3, and 2-4 may be applied / used simultaneously.

[0226] Example 2-1

[0227] In one embodiment of the present disclosure (Embodiment 2-1), a terminal may repeatedly transmit event-related information or reports to a base station based on the base station's settings (e.g., configuration information transmitted by the base station to the terminal). For example, multiple report transmission points may be set / defined, and the terminal may repeatedly transmit event-related information to the base station at the set / defined report transmission points.

[0228] Example 2-1 relates to a method for increasing transmission reliability by repeatedly transmitting event-related information. A terminal may repeatedly transmit event-related information to a base station, either continuously or discontinuously. The terminal may repeatedly transmit event-related information according to at least one of the embodiments described below.

[0229] Example 2-1-1

[0230] The base station may transmit configuration information related to the transmission cycle and / or the number of repeated transmissions of event-related information to the terminal. For example, the base station may set P slots (where P is a natural number greater than or equal to 1) as the reporting cycle for event-related information to the terminal. Additionally, the base station may set R (where R is a natural number greater than or equal to 1) as the number of repeated transmissions of event-related information to the terminal.

[0231] (When an event occurs) The terminal can repeatedly transmit information related to the same event through R slots each having P slot intervals. That is, the terminal can transmit information related to the same event in each of R slots, and each of the R slots can have P slot intervals from each other.

[0232] Example 2-1-2

[0233] The reporting cycle of event-related information can be set / defined (by the base station) as P slots. Additionally, R slots with P' slot intervals smaller than P can be additionally set (by the base station) within one cycle. (When an event occurs) the terminal can repeatedly transmit information related to the same event through R slots with P' slot intervals (within the cycle in which the event occurs).

[0234] For example, assume that "P=4, P'=1 and R=2" are set / defined, and slots that are event TOs are represented by O, and slots that are not event TOs are represented by x. In this case, slots {1, 2, 3, 4} within one cycle can be set to {TO, TO, x, x}, and slots {1, 2, 3, 4, 5, 6, 7, 8} within two cycles can be set to {TO, TO, x, x, TO, TO, x, x}.

[0235] Here, event TO may collectively refer to a TO that transmits information related to an event or / and a TO that transmits information related to an event.

[0236] Example 2-1-3

[0237] The base station may transmit configuration information related to the transmission cycle and / or the number of repeated transmissions of event-related information to the terminal. For example, the base station may set P slots (where P is a natural number greater than or equal to 1) as the reporting cycle for event-related information to the terminal. Additionally, the base station may set R (where R is a natural number greater than or equal to 1) as the number of repeated transmissions of event-related information to the terminal.

[0238] (When an event occurs) The terminal can repeatedly transmit information related to the event R times using different information within slots having the same P slot intervals.

[0239] For example, a terminal may repeatedly transmit event-related information to a base station R times using different time resources (e.g., symbols), frequency resources (e.g., frequency positions), and / or spatial resources (e.g., layers, ports, spatial filters) within slots having P slot intervals.

[0240] Additionally or alternatively, the terminal may transmit event-related information to the base station R using different beams / panels. For example, the terminal may transmit event-related information to the base station R times using a simultaneous transmission method across multiple panels.

[0241] Example 2-2

[0242] If an event-based report (e.g., transmission of information related to an event) is performed and there is no action on the report from the base station after a certain period of time, the terminal may perform an event-based re-report (e.g., re-transmission of information related to the event).

[0243] For example, when an event-based report is performed, a timer associated with that report may be triggered / started. When the timer expires, the terminal may perform an event-based re-report (e.g., retransmit information related to the event).

[0244] The above-described behavior can be interpreted as an action of not performing retransmission of event-related information for a certain period of time after an event-based report. That is, the terminal may transmit event-related information and not perform retransmission for a certain period of time. If the terminal transmits event-related information and the base station performs an action (e.g., transmitting information indicating a beam change or / and transmitting ACK information for the event-related information) within a certain period of time, the terminal may suspend / stop the (re)transmission procedure of the event-related information.

[0245] Example 2-3

[0246] A base station response message / signal for event-based reporting may be defined. If an event-based report is performed and the base station's response message / signal is not received within a predefined / configured time period or at a specific time, the terminal may retransmit event-related information to the base station.

[0247] Here, the response message / signal may include an ACK message / signal for PUCCH / PUSCH that includes information related to the event (e.g., beam / CSI information related to the event, etc.).

[0248] For example, when an event-based report is performed, a timer associated with the report may be triggered / started. If a response message / signal is not received by the time the timer expires, the terminal may perform an event-based re-report (e.g., retransmit information related to the event).

[0249] The above-described operation may be interpreted as an operation in which the (re)transmission of information related to the event of the terminal is suspended until a response message / signal from the base station is received or until the timer expires. That is, the terminal may transmit information related to the event and not perform retransmission for a predefined / set time period (e.g., during the time period in which the timer is running).

[0250] Embodiments 2-2 and 2-3 relate to a method for improving the reception performance of event-related information by a base station by having a terminal retransmit event-related information to the base station when normal reception of event-related information by the base station is suspected.

[0251] For example, a timer that starts / operates after a terminal transmits event-related information may be set or predefined by the base station. Furthermore, after transmitting event-related information, the terminal's retransmission operations may be suspended for a certain period of time. In other words, after transmitting event-related information, the terminal may not retransmit event-related information for a certain period of time (e.g., for the time period set in the timer).

[0252] Example 2-4

[0253] When a terminal (re)transmits event-related information (e.g., when performing an event-based (re)reporting operation), a high UL transmit power may be set / applied for the terminal's (re)transmission operation. For example, when transmitting event-related information, the terminal may set / apply a high UL transmit power or perform power boosting.

[0254] As an example, the operations and features related to a method for setting an open loop power control set in a basic wireless communication system (e.g., a method when an SRI field exists on DCI) are as follows:

[0255] - The method for setting an open-loop power control set can be performed to amplify the power of URLLC transmission when it collides with eMBB traffic of another terminal. When a collision occurs with eMBB traffic of another terminal, the P0 value can be modified to control the open-loop power. Specifically, the DCI format 0_1 ​​or 0_2 can be set to include an "Open-loop power control parameter set indication" field. The field can have a size of 1 bit (if the corresponding DCI includes an SRI field). When the value of the field is set to 1, another P0 value can be used for open-loop power control (e.g., power amplification). The value of P0 can be determined based on a list of P0 values ​​(e.g., "p0-PUSCH-SetList-r16") set in RRC using a one-to-one mapping for SRI code points.

[0256] As an example of the present disclosure, when information related to an event is transmitted to a base station via an uplink channel (e.g., PUSCH, etc.), power boosting may be performed based on an open-loop power control parameter set indication field value (included in the DCI). For example, when an SRI field exists in the corresponding DCI, the open-loop power control parameter set indication field value may be set to 1, and when an SRI field does not exist in the corresponding DCI, the open-loop power control parameter set indication field value may be set to 01 or 10. Furthermore, a terminal may expect that the open-loop power control parameter set indication field value is set to 1, 01, or 10.

[0257] Example 3

[0258] A procedure for transmitting "information on whether an event has occurred" as SR (or information related to SR), as in Method 1-1, may also be applied. In this case, collisions / overlaps may occur between the PUCCH resources used to transmit information on whether an event has occurred and other BFRQ / SR PUCCH resources. If such collisions / overlaps occur, a definition of the type of UCI or / and associated UL channel to be transmitted preferentially may be required.

[0259] In a basic wireless communication system, the encoding / RE mapping method of BFRQ can be identical to the encoding / RE mapping method of SR. That is, BFRQ can be treated as a type of SR and (if necessary) can be expressed as an SR for SCell beam failure recovery or a link recovery request (LRR). If BFRQ overlaps / collides with other UL channel resources, BFRQ can be transmitted with a higher priority than a general SR.

[0260] As with BFRQ in method 1-1, information about whether an event has occurred can be transmitted to the base station in the same encoding / RE mapping manner as SR.

[0261] Meanwhile, since BFRQs can be generated in situations where all serving beams have failed or where no failure has occurred for the current serving beam but a new, higher-quality beam has been found, BFRQs may be more urgent information than information about the occurrence of an event. Furthermore, event-related information may include information about analog beams in high-frequency bands, and since processing of the corresponding beam management can improve the reliability and efficiency of TB transmission, event-related information may be more important than general SRs.

[0262] Accordingly, for example, the priority of information regarding the occurrence of an event may be equal to or lower than that of BFRQ. Furthermore, the priority of information regarding the occurrence of an event may be equal to or higher than that of a typical SR.

[0263] Additionally or alternatively, the priority of information related to an event may be defined as being equal to the priority of one of SR and BFRQ.

[0264] Example 3 relates to a method for transmitting information regarding the occurrence of an event (e.g., a beam-related event) in the same manner as SR. For example, a terminal may transmit information regarding the occurrence of an event to a base station based on the encoding, RE mapping, and multiplexing methods applied to SR.

[0265] For example, if information related to the occurrence of an event (e.g., UCI) or an uplink channel containing such information overlaps / conflicts with another channel, the terminal can determine the type of information to transmit based on the priority of each channel / information. For example, the priority of information related to the occurrence of an event may be equal to or lower than that of BFRQ. Furthermore, the priority of information related to the occurrence of an event may be equal to or higher than that of a general SR.

[0266] The method according to the above-described embodiment 3 can also be used / applied when event-based transmission / reporting is performed via MAC-CE. That is, when transmitting event-based information (e.g., information related to whether an event has occurred, event-related reporting information) via MAC-CE or / and when no available UL-SCH is allocated, the terminal can request the base station via SR for a UL-SCH for transmitting the corresponding MAC-CE.

[0267] In basic wireless communication systems, except in exceptional cases (e.g., BFR MAC-CE), the behavior of a general MAC-CE triggering SR may not be supported. That is, even if a MAC-CE to transmit exists, SR transmission may not be triggered. Furthermore, the behavior of UCI triggering SR may not be supported.

[0268] Accordingly, the MAC-CE / UCI for event-based transmission / reporting can be defined / configured to trigger transmission of SR. In addition, the SR can be i) mapped to (only) dedicated SR PUCCH resources (such as BFR procedures), ii) enabled to use SR PUCCH resources that trigger logical channels, or iii) enabled to use SR PUCCH resources for BFR.

[0269] Example 4

[0270] Example 4 relates to a method in which a MAC-CE or UCI performing event-based transmission / reporting triggers SR.

[0271] For example, when Method 1-1a, Method 1-1b, and Method 2 are applied, information related to an event (e.g., information on whether an event has occurred, event-related reporting information, etc.) may be transmitted to the base station via MAC-CE or / and UCI.

[0272] For example, a MAC-CE or UCI containing information related to an event may trigger an SR (transmission) to request resources (e.g., UL-SCH resources, resources related to an uplink channel (e.g., PUSCH, PUCCH, etc.)) for transmitting the MAC-CE or UCI.

[0273] That is, the terminal can transmit an SR to the base station to transmit MAC-CE or / and UCI containing information related to an event, and the terminal can receive information corresponding to the SR (e.g., information on UL-SCH / uplink resources requested according to the SR, etc.) from the base station. The terminal can transmit the MAC-CE or / and UCI to the base station based on the resources related to the information received from the base station.

[0274] Example 5

[0275] Example 5 relates to a method related to transmission of SR in connection with event-based transmission / reporting.

[0276] Specifically, SRs related to event-based transmission / reporting (transmitted via MAC-CE and / or UCI) may be transmitted according to at least one of the methods described below. SRs related to event-based transmission / reporting may collectively refer to SRs for requesting UL-SCH resources for transmitting event-related information.

[0277] Method 5-1: SRs associated with event-based transmission / reporting can (together) utilize dedicated SR PUCCH resources. For example, SRs associated with event-based transmission / reporting can be transmitted to the base station via dedicated SR PUCCH resources based on the assigned SR ID / configuration. That is, the UE can transmit SRs associated with event-based transmission / reporting to the base station based on dedicated PUCCH resources associated with the dedicated SR ID / configuration.

[0278] Method 5-2: SR related to event-based transmission / reporting can use (together) SR PUCCH resources that trigger logical channels. That is, the terminal can transmit SR related to event-based transmission / reporting to the base station based on SR PUCCH resources that trigger logical channels.

[0279] Method 5-3: SR related to event-based transmission / reporting can (together) use SR PUCCH resources for BFR purposes. That is, the terminal can transmit SR related to event-based transmission / reporting to the base station based on SR PUCCH resources for BFR purposes.

[0280] As described above, the number of SR PUCCH resources configured / supported per BWP in a basic wireless communication system may be limited. For example, only one SR PUCCH resource for a logical channel may be supported per BWP. For SCell BFR, one (e.g., for STRP BFR) or two (e.g., for MTRP BFR) SR PUCCH resources may be supported per BWP.

[0281] Method 5-1 relates to a method for separately configuring SR PUCCH resources associated with MAC-CE / UCI for event-based transmission / reporting from SR PUCCH resources in a basic wireless communication system. For example, the base station may transmit to the terminal configuration information for configuring SR PUCCH resources associated with MAC-CE / UCI for event-based transmission / reporting. Additionally, the base station may transmit to the terminal configuration information for configuring separate SR PUCCH resources (e.g., SR PUCCH resources not related to events).

[0282] At this time, priorities between SR PUCCHs may be applied according to Embodiment 3. For example, the priority of an SR PUCCH associated with MAC-CE / UCI for event-based transmission / reporting (e.g., an event-related SR PUCCH) may be lower than or equal to the priority of an SR PUCCH for BFR. In addition, the priority of an SR PUCCH associated with MAC-CE / UCI for event-based transmission / reporting (e.g., an event-related SR PUCCH) may be higher than or equal to the priority of an SR PUCCH for logical channels. If an SR PUCCH associated with MAC-CE / UCI for event-based transmission / reporting (e.g., an event-related SR PUCCH) overlaps or overlaps with another SR PUCCH resource, the UE may preferentially transmit an SR PUCCH with a higher priority to the base station according to the priority rules described above.

[0283] Method 5-2 relates to a method of using SR PUCCH resources that trigger logical channels together for event-based transmission / reporting. For example, SR PUCCH resources that trigger logical channels can be used for SR PUCCH transmissions associated with MAC-CE / UCI for event-based transmission / reporting. The priority of the SR PUCCH resources associated with MAC-CE / UCI for event-based transmission / reporting may be the same as the priority of the SR PUCCH resources that trigger logical channels.

[0284] Method 5-3 relates to a method of using SR PUCCH resources for BFR together for event-based transmission / reporting. For example, SR PUCCH resources for BFR can be used for SR PUCCH transmissions associated with MAC-CE / UCI for event-based transmission / reporting. The priority of the SR PUCCH resources associated with MAC-CE / UCI for event-based transmission / reporting may be the same as the priority of the SR PUCCH resources for BFR.

[0285] FIG. 9 is a diagram for explaining a signaling procedure of a network side and a terminal according to one embodiment of the present disclosure.

[0286] FIG. 9 illustrates an example of signaling between a network side and a terminal (UE) in an M-TRP situation to which the examples of the present disclosure described above (e.g., one or more combinations of Embodiments 1, 2, 3, 4, 5, or / and detailed embodiments of the above embodiments) may be applied.

[0287] Here, the UE / network side is exemplary and can be replaced with various devices as described with reference to FIG. 10. FIG. 9 is provided for convenience of explanation and does not limit the scope of the present disclosure. In addition, some of the steps shown in FIG. 9 may be omitted depending on the situation and / or settings. In addition, in the operation of the network side / UE of FIG. 9, the aforementioned uplink transmission / reception operation, M-TRP-related operation, etc. may be referenced or utilized.

[0288] In the following description, the network side may be a single base station including multiple TRPs, or a single cell including multiple TRPs. Alternatively, the network side may include multiple remote radio heads (RRHs) / remote radio units (RRUs).

[0289] For example, ideal / non-ideal backhauls can be established between TRP 1 and TRP 2, which constitute the network side. Furthermore, while the following description is based on multiple TRPs, it can be equally extended to transmissions through multiple panels / cells, and can also be extended to transmissions through multiple RRHs / RRUs, etc.

[0290] In addition, although the following description is based on "TRP", as described above, "TRP" can be replaced and applied with expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pico cell, etc.), transmission point (TP), base station (gNB, etc.). As described above, TRP can be distinguished according to information about CORESET group (or CORESET pool) (e.g., CORESET index, ID).

[0291] For example, if a single terminal is configured to transmit and receive with multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for the single terminal. The configuration of such CORESET groups (or CORESET pools) can be performed via higher-layer signaling (e.g., RRC signaling).

[0292] Additionally, a base station may be a general term for an object that transmits and receives data with a terminal. For example, the base station may be a concept that includes one or more Transmission Points (TPs), one or more Transmission and Reception Points (TRPs), etc. Furthermore, the TPs and / or TRPs may include a panel of the base station, a transmission and reception unit, etc.

[0293] The terminal can receive configuration information from the network (S105).

[0294] For example, the configuration information may include event-related configuration information (or / and event-based reporting-related configuration information), reporting information configuration information, UL channel resource (e.g., PUCCH / PUSCH) information for reporting, etc. For example, the event-related configuration information may include the type of event, criteria related to the event, thresholds, etc. That is, the event-related configuration information may include criteria and / or thresholds for determining whether an event has occurred or / and the type of the event.

[0295] For example, a UL channel resource for reporting may include information for setting up a UL channel resource for reporting event-related information, etc., and / or information for describing a resource for reporting other information (e.g., information for reporting separate information unrelated to the event).

[0296] Additionally or alternatively, the configuration information may include configuration information related to each of one or more combinations of Embodiments 1, 2, 3, 4, 5, or / and detailed embodiments of the above embodiments. Additionally or alternatively, the configuration information may include configuration information related to Method 1-1, Method 1-1a, Method 1-1b, Method 1-2, Method 1-3, Method 1-3a, Method 1-3b, Method 2, Method 3, Method 3-1, and Method 3-2.

[0297] The above-described configuration information may be transmitted to the terminal via, but is not limited to, higher-layer signaling (e.g., SIB, RRC message, MAC CE, etc.). Furthermore, the above-described configuration information may be transmitted to the terminal via separate higher-layer signaling, but some configuration information may be transmitted to the terminal via a single higher-layer signaling.

[0298] The terminal may receive a message / signal (or control information) (e.g., MAC-CE, DCI, etc.) from the base station to activate / start event-based reporting and / or UL channel resources (S110). For example, the terminal may receive an activation message / signal of UL channel resources for transmitting event-related information from the base station. For example, if event-related reporting and / or UL channel resources are indicated / configured by configuration information (e.g., RRC message, etc.), the operation according to step S110 may be omitted.

[0299] The terminal can monitor whether an event has occurred based on control information and / or configuration information received from the base station. If an event has occurred (S115), the terminal can transmit information related to the event to the base station (S120). For example, the terminal can transmit information related to the event to the base station using UL channel resources based on the control information / configuration information. When transmitting information related to the event, an operation according to one or more of the embodiments described above (e.g., one or more combinations of embodiments 1, 2, 3, 4, 5, or / and detailed embodiments of the above embodiments) can be performed.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0315] 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 first setting information related to an event from a base station by a terminal; and Based on the occurrence of the above event, a step of encoding, by the terminal, information related to the event on a first uplink channel based on second configuration information related to a scheduling request (SR); and A step of transmitting the first uplink channel or the second uplink channel to the base station by the terminal based on a priority of information related to the event, based on the first uplink channel overlapping with a second uplink channel including the SR or link recovery request (LRR), A method wherein the priority of information related to the above event is higher than or equal to the priority of the SR and lower than or equal to the priority of the LRR.

2. In paragraph 1, Based on the fact that the first uplink channel overlaps with the second uplink channel including the SR, the first uplink channel is transmitted to the base station based on the priority of information related to the event, A method wherein the second uplink channel is transmitted to the base station based on a priority of information related to the event, based on the first uplink channel overlapping with the second uplink channel including the LRR.

3. In paragraph 1, A method wherein the second configuration information related to the SR includes at least one of a period, an offset, a priority, a resource, an encoding method, or an ID (identifier) of the SR.

4. In paragraph 1, The above first setting information includes information related to the transmission cycle and number of transmissions of information related to the event, A method in which information related to the event is repeatedly transmitted to the base station based on the transmission cycle and the number of transmissions of information related to the event.

5. In paragraph 1, Based on the above first uplink channel being transmitted to the base station, a timer related to retransmission of information related to the event is started, A method wherein information related to the event is retransmitted to the base station based on a response message for information related to the event not being received from the base station before the timer expires.

6. In paragraph 5, A method wherein operation of the timer and retransmission of information related to the event are stopped based on reception of a response message for information related to the event from the base station before the timer expires.

7. In paragraph 6, A method wherein the above response message includes an ACK (acknowledgement) message for the first uplink channel.

8. In paragraph 1, The downlink control information related to the first uplink channel includes a power control parameter set indication field, A method wherein the power of the first uplink channel is determined based on the power control parameter set indication field.

9. In paragraph 1, Downlink control information related to the first uplink channel is transmitted from the base station to the terminal, A method in which an ACK message for the above downlink control information is transmitted from the terminal to the base station.

10. In paragraph 1, A method according to claim 1, wherein the first uplink channel is a configured grant (CG) physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).

11. In paragraph 1, A method in which information related to the above event is included in uplink control information (UCI).

12. 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 first setting information related to an event from a base station via said one or more transceivers; Based on the occurrence of the above event, information related to the event is encoded by the terminal on the first uplink channel based on second configuration information related to a scheduling request (SR); and Based on the fact that the first uplink channel overlaps with the second uplink channel including the SR or link recovery request (LRR), the first uplink channel or the second uplink channel is set to be transmitted to the base station through the one or more transceivers based on the priority of the information related to the event. The priority of the information related to the above event is higher than or equal to the priority of the SR and lower than or equal to the priority of the LRR.

13. A step of transmitting first setting information related to an event to a terminal by a base station; and Based on the occurrence of the above event, the step of receiving, by the base station, from the terminal, i) a first uplink channel including information related to the event or ii) a second uplink channel including a scheduling request (SR) or a link recovery request (LRR), based on a priority related to the event, The first uplink channel and the second uplink channel overlap in the same time resource, Information related to the above event is encoded on the first uplink channel based on second configuration information related to the SR, A method wherein the priority of information related to the above event is higher than or equal to the priority of the SR and lower than or equal to the priority of the LRR.

14. In the base station, the base station: one or more transceivers; and comprising one or more processors coupled to said one or more transceivers; One or more of the above processors: Transmitting first setting information related to the event to the terminal via one or more of the transceivers; and Based on the occurrence of the above event, i) a first uplink channel including information related to the event or ii) a second uplink channel including a scheduling request (SR) or a link recovery request (LRR) is set to be received from the terminal through the one or more transceivers based on a priority related to the event, The first uplink channel and the second uplink channel overlap in the same time resource, Information related to the above event is encoded on the first uplink channel based on second configuration information related to the SR, The priority of the information related to the above event is higher than or equal to the priority of the SR and lower than or equal to the priority of the LRR.

15. In a processing device set to control a terminal, the processing device: 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 that, when executed by said one or more processors, perform a method according to any one of claims 1 to 11.

16. One or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium, wherein said one or more instructions are executed by one or more processors to control a device to perform a method according to any one of claims 1 to 11.

Images