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

Abstract

A method and apparatus for performing uplink transmission and reception in a wireless communication system are disclosed. A method according to one embodiment of the present disclosure comprises: receiving first configuration information related to a first uplink resource for transmitting first information from a base station by a terminal; and transmitting second information related to the first event by the terminal to the base station through a first uplink channel based on the first uplink resource, based on the occurrence of a first event, wherein the first uplink channel may include third information related to whether the second information is information related to the first event.

Description

Technology Field

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for performing uplink transmission and reception in a wireless communication system. Background Technology

[0002] Mobile communication systems were developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded their scope to include data services as well as voice. Currently, due to the explosive increase in traffic leading to resource shortages and users demanding higher-speed services, more advanced mobile communication systems are required.

[0003] The requirements for next-generation mobile communication systems largely include the ability to accommodate explosive data traffic, a dramatic increase in transmission rates per user, a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To achieve this, various technologies are being researched, such as dual connectivity, massive multiple input multiple output (MMIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking. The problem to be solved

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

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

[0006] The technical problems to be solved in this disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this disclosure belongs from the description below. means of solving the problem

[0007] A method according to one embodiment of the present disclosure comprises: receiving first configuration information related to a first uplink resource for transmitting first information from a base station by a terminal; and transmitting second information related to the first event by the terminal to the base station through a first uplink channel based on the first uplink resource based on the occurrence of a first event, wherein the first uplink channel may include third information related to whether the second information is information related to the first event.

[0008] A method according to another embodiment of the present disclosure comprises: a step of transmitting first configuration information related to a first uplink resource for transmitting first information to a terminal by a base station; and a step of receiving second information related to the first event from the terminal by the base station through a first uplink channel based on the first uplink resource based on the occurrence of a first event, wherein the first uplink channel may include third information related to whether the second information is information related to the first event. Effects of the invention

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

[0010] In addition, by various embodiments of the present disclosure, a method and apparatus for performing an event-based transmission and reception procedure may be provided.

[0011] In addition, by various embodiments of the present disclosure, overhead associated with uplink resources for beam / CSI reporting can be reduced during event-based transmission procedures.

[0012] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below. Brief explanation of the drawing

[0013] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and explain the technical features of the present disclosure together with the detailed description. FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied. FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure may be applied. FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure may be applied. FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure may be applied. FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure may be applied. FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure may be applied, and a general method of transmitting and receiving signals using these channels. FIG. 7 is a flowchart illustrating a method for a terminal to perform a communication procedure as an embodiment of the present disclosure. FIG. 8 is a flowchart illustrating a method for a base station to perform a communication procedure as an embodiment of the present disclosure. FIG. 9 is a drawing for explaining a signaling process according to one embodiment of the present disclosure. FIG. 10 is a drawing illustrating a block diagram of a wireless communication device according to one embodiment of the present disclosure. Specific details for implementing the invention

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

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

[0016] In the present disclosure, when a component is described as being “connected,” “combined,” or “joined” with another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, in the present disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, actions, elements, components, and / or groups thereof.

[0017] In the present disclosure, terms such as "first," "second," etc. are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor do they limit the order or importance of the components unless specifically stated otherwise. Accordingly, within the scope of the present disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and likewise, a second component in one embodiment may be referred to as a first component in another embodiment.

[0018] The terms used in this disclosure are for the description of specific embodiments and are not intended to limit the claims. As used in the description of embodiments and in the appended claims, the singular form is intended to include the plural form unless the context clearly indicates otherwise. The term "and / or" as used in this disclosure may refer to any one of the related enumerated items, or refers to and includes any and all possible combinations of two or more of them. Additionally, the " / " between words in this disclosure has the same meaning as "and / or" unless otherwise noted.

[0019] 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 the process of controlling the network and transmitting or receiving signals by a device (e.g., a base station) governing the wireless communication network, or in the process of transmitting or receiving signals with or between the network and terminals by a terminal connected to the wireless network.

[0020] In the present disclosure, transmitting or receiving a channel includes the meaning of transmitting or receiving information or a signal through said 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.

[0021] In the following, the downlink (DL) refers to communication from a base station to a terminal, and the uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter may be part of the base station, and the receiver may be part of the terminal. In the uplink, the transmitter may be part of the terminal, and the receiver may be part of the base station. The base station may be referred to as the first communication device, and the terminal as the second communication device. The term base station (BS) may be replaced by terms such as fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), Access Point (AP), network (5G network), AI (Artificial Intelligence) system / module, RSU (roadside 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, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device.

[0022] 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), and 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 the UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) using E-UTRA, and LTE-A (Advanced) / LTE-A pro 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.

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

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

[0025] For 3GPP NR, you may refer to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Coding), TS 38.213 (Physical Layer Procedures for Control), TS 38.214 (Physical Layer Procedures for Data), TS 38.300 (General Description of NR and NG-RAN (New Generation-Radio Access Network)), and TS 38.331 (Radio Resource Control Protocol Specification).

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

[0027] - BM: Beam management

[0028] - CQI: Channel quality indicator

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

[0030] - CSI: Channel state information

[0031] - CSI-IM: Channel state information - interference measurement

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

[0033] - DMRS: demodulation reference signal

[0034] - FDM: Frequency Division Multiplexing

[0035] - FFT: Fast Fourier Transform

[0036] - IFDMA: Interleaved frequency division multiple access

[0037] - IFFT: Inverse Fast Fourier Transform

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

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

[0040] - MAC: Medium Access Control

[0041] - NZP: Non-zero power

[0042] - OFDM: Orthogonal Frequency Division Multiplexing

[0043] - PDCCH: Physical downlink control channel

[0044] - PDSCH: Physical downlink shared channel

[0045] - PMI: Precoding Matrix Indicator

[0046] - RE: resource element

[0047] - RI: Rank indicator

[0048] - RRC: Radio Resource Control

[0049] - RSSI: Received signal strength indicator

[0050] - Rx: Reception

[0051] - QCL: quasi co-location

[0052] - SINR: Signal to interference and noise ratio

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

[0054] - TDM: Time Division Multiplexing

[0055] - TRP: transmission and reception point

[0056] - TRS: Tracking Reference Signal

[0057] - Tx: transmission

[0058] - UE: User equipment

[0059] - ZP: Zero Power

[0060] General System

[0061] As more communication devices require larger communication capacities, the need for enhanced mobile broadband communication compared to existing radio access technology (RAT) is emerging. In addition, massive machine-type communications (MTC), which connects multiple devices and objects to provide various services anytime and anywhere, is also one of the major issues to be considered in next-generation communication. Furthermore, communication system designs that take into account services and terminals sensitive to reliability and latency are being discussed. As such, the introduction of next-generation RAT considering eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), and URLLC (ultra-reliable and low latency communication) is being discussed, and for convenience, this technology is referred to as NR in this disclosure. NR is an expression representing an example of 5G RAT.

[0062] A new RAT system including NR uses an OFDM transmission method or a similar transmission method. 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). Or, a single cell may support multiple numerologies. That is, terminals operating with different numerologies can coexist within a single cell.

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

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

[0065] 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 endpoints for the UE. The gNBs are interconnected via Xn interfaces. The gNBs are also connected to the NGC (New Generation Core) via NG interfaces. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Function) via N2 interfaces and to the UPF (User Plane Function) via N3 interfaces.

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

[0067] An NR system can support multiple numerologies. Here, the numerology can be defined by subcarrier spacing and cyclic prefix (CP) overhead. In this case, multiple subcarrier spacings can be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). Furthermore, the numerology used can be selected independently of the frequency band, even if it is assumed that very low subcarrier spacings are not used at very high carrier frequencies. Additionally, various frame structures based on multiple numerologies can be supported in an NR system.

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

[0069] μ Δf=2 μ ·15 [kHz] CP 0 15 Normal 1 30 common 2 60 General, Extended 3 120 common 4 240 common

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

[0071] Frequency Range Designation Corresponding frequency range Subcarrier Spacing FR1 410MHz - 7125MHz 15, 30, 60kHz FR2 24250MHz - 52600MHz 60, 120, 240kHz

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

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

[0074] μ N symb slot N slot frame,μ N slot subframe,μ 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

[0075] μ N symb slot N slot frame,μ N slot subframe,μ 2 12 40 4

[0076] FIG. 2 is an example of the case where μ=2 (SCS is 60kHz), and referring to Table 3, one subframe can contain four slots. The slots in the one subframe={1,2,4} shown in FIG. 2 are examples, and the number of slot(s) that can be included in one subframe is defined as in Table 3 or Table 4. Additionally, a mini-slot can contain 2, 4, or 7 symbols, or more or fewer symbols. Regarding physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc., may be considered.

[0077] Below, the aforementioned physical resources that can be considered in an NR system are examined in detail. First, regarding antenna ports, an antenna port is defined such that the channel carrying a symbol on the antenna port can be inferred from the channel carrying another symbol on the same antenna port. If the large-scale property of the channel carrying a symbol on one antenna port can be inferred from the channel carrying a symbol on another antenna port, the two antenna ports can be said to be in 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.

[0078] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure may 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 by way of example as being composed of OFDM symbols, but is not limited thereto. In an NR system, the transmitted signal is N RB μ N sc RB One or more resource grids composed of subcarriers and 2 μ N symb (μ) It is described by the OFDM symbols of. Here, N RB μ ≤N RB max,μ It is. The above NRB max,μ represents the maximum transmission bandwidth, which can vary between uplink and downlink as well as between numerologies. In this case, a resource grid can be established 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').

[0079] Here, k=0,...,N RB μ N sc RB -1 is an index in the frequency domain, and l'=0,...,2 μ N symb (μ) -1 refers to the location of a symbol within a subframe. When referring to resource elements in a slot, an index pair (k,l) is used. Here, l=0,...,N symb μ It is -1. The resource factor (k,l') for μ and antenna port p is the complex value a k,l' (p,μ) It corresponds to. If there is no risk of confusion or if a specific antenna port or numerology is not specified, the indices p and μ may be dropped, and the resulting complex value is a k,l' (p) or a k,l' This can be. In addition, the resource block (RB) is N in the frequency domain. sc RB =12 is defined by consecutive subcarriers.

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

[0081] - OffsetToPointA for the Primary Cell (PCell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block used by the terminal for initial cell selection. It is expressed in resource block units assuming a 15 kHz subcarrier interval for FR1 and a 60 kHz subcarrier interval for FR2.

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

[0083] Common resource blocks are numbered from 0 upward in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of common resource block 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 element (k,l) and the subcarrier spacing setting μ is given as Equation 1 below.

[0084]

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

[0086]

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

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

[0089] Referring to FIGS. 4 and 5, a slot contains multiple symbols in the time domain. For example, in the case of a standard CP, one slot contains 7 symbols, but in the case of an extended CP, one slot contains 6 symbols.

[0090] A carrier includes multiple subcarriers in the frequency domain. A Resource Block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A Bandwidth Part (BWP) 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 may include up to N (e.g., 5) BWPs. Data communication is performed through the active BWPs, and only one BWP can be active for a single terminal. In the resource grid, each element is referred to as a Resource Element (RE) and can be mapped to a single complex symbol.

[0091] NR systems can support up to 400 MHz per component carrier (CC). If a terminal operating in such a wideband CC always keeps its radio frequency (RF) chip turned on for the entire CC, the terminal's battery consumption may increase. Alternatively, considering various use cases operating within a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different numerologies (e.g., subcarrier spacing) may be supported for each frequency band within that CC. Or, the capability regarding the maximum bandwidth may vary by terminal. Taking this into account, the base station may instruct the terminal to operate only in a portion of the bandwidth rather than the entire bandwidth of the wideband CC, and for convenience, this portion of bandwidth is defined as the bandwidth part (BWP). 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).

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

[0093] Alternatively, if UEs are concentrated in a specific BWP, some terminals may be configured to a different BWP for load balancing. Alternatively, both BWPs may be configured within the same slot by excluding a portion of the spectrum in the middle of the total bandwidth, taking into account frequency domain inter-cell interference cancellation between neighboring cells. That is, the base station may configure at least one DL / UL BWP for terminals associated with the broadband CC.

[0094] A base station may activate at least one of the DL / UL BWP(s) configured at a specific time (by L1 signaling, MAC CE (Control Element), RRC signaling, etc.). Additionally, the base station may instruct a switching to another configured DL / UL BWP (by L1 signaling, MAC CE, RRC signaling, etc.). Alternatively, a switching to a specified DL / UL BWP may occur based on a timer when the timer value expires. In this case, the activated DL / UL BWP is defined as the active DL / UL BWP. However, since the terminal may not receive the configuration for the DL / UL BWP in situations such as when the terminal is performing the initial access process or before the RRC connection is set up, the DL / UL BWP assumed by the terminal in such situations is defined as the initial active DL / UL BWP.

[0095] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure may be applied, and a general method of transmitting and receiving signals using these channels.

[0096] In a wireless communication system, a terminal receives information from a base station via the downlink and transmits information to the base station via the uplink. The information transmitted and received by the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.

[0097] 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 do this, 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). After that, the terminal receives a physical broadcast channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, during the initial cell search stage, the terminal receives a downlink reference signal (DL RS) to check the downlink channel status.

[0098] 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 sharing channel (PDSCH) according to the information carried on the PDCCH (S602).

[0099] Meanwhile, when a terminal first connects to a base station or when there are no wireless resources for signal transmission, the terminal may perform a random access procedure (RACH) with respect to the base station (steps S603 to S606). To do this, the terminal transmits a specific sequence as a preamble through a random access channel (RACH) (S603 and S605), and may receive a response message for the preamble through a PDCCH and a corresponding PDSCH (S604 and S606). In the case of a collision-based RACH, a contention resolution procedure may additionally be performed.

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

[0101] Meanwhile, control information transmitted by the terminal to the base station via the uplink or received by the terminal 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 a 3GPP LTE system, the terminal may transmit the aforementioned control information, such as CQI / PMI / RI, via PUSCH and / or PUCCH.

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

[0103] DCI format conjugation 0_0 Scheduling of PUSCH within a single cell 0_1 Scheduling of one or multiple PUSCHs within a single cell, or instruction to the UE regarding cell group (CG) downlink feedback information 0_2 Scheduling of PUSCH within a single cell 1_0 Scheduling of PDSCH within a single DL cell 1_1 Scheduling of PDSCH within a single cell 1_2 Scheduling of PDSCH within a single cell

[0104] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to PUSCH scheduling (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.), and power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined.

[0105] DCI format 0_0 is used for PUSCH scheduling in a single cell. The information contained in DCI format 0_0 is transmitted after being scrambled with a Cyclic Redundancy Check (CRC) by a Cell Radio Network Temporary Identifier (C-RNTI), Configured Scheduling RNTI, or Modulation Coding Scheme Cell RNTI. DCI format 0_1 ​​is used for scheduling one or more PUSCHs in a single cell, or to instruct the terminal on Configure Grant (CG) downlink feedback information. The information contained in DCI format 0_1 ​​is transmitted after being scrambled with a CRC by a Cell Radio Network Temporary Identifier (C-RNTI), CS-RNTI, Semi-Persistent CSI RNTI (SP-CSI-RNTI), or MCS-C-RNTI. DCI format 0_2 is used for PUSCH scheduling in a single cell. The information contained in DCI format 0_2 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

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

[0107] DCI format 1_0 is used for scheduling PDSCH in a single DL cell. The information contained in DCI format 1_0 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

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

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

[0110] Basic beam failure recovery (BFR)

[0111] 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 set of beams that can be used for downlink and uplink transmission and reception.

[0112] Specifically, the BM may include a beam measurement process for measuring the characteristics of a beamforming signal received from a base station or terminal, a beam determination process for determining the base station or terminal's own transmit beam (Tx beam) and receive beam (Rx beam), a beam sweeping process for covering a spatial area using the transmit beam and / or receive beam for a set time interval in a predetermined manner, and a beam reporting process in which the terminal reports information of the beam signal to the base station based on the beam measurement results.

[0113] During the uplink / downlink BM process described above, beam mismatch problems may occur 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 it changes from a line-of-sight (LoS) environment to a non-LoS environment as the beam is blocked), 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.

[0114] 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 to the base station a report message regarding the occurrence of a beam failure or a beam failure recovery request message (BFRQ message). Upon receiving the message, the base station may perform the beam recovery process through various steps, such as transmitting a beam RS or requesting a beam report. This series of beam recovery processes is referred to as the beam failure recovery (BFR) process.

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

[0116] Beam failure detection (BFD)

[0117] 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 hypothetical block error rate (BLER). That is, the hypothetical BLER can represent the probability that the demodulation of control information will fail when control information is transmitted to a specific PDCCH.

[0118] In addition, one or more search spaces for monitoring PDCCH can be configured on the terminal, and PDCCH beams can be configured differently for each search space. In this case, when the quality value of all PDCCH beams falls below a predefined value, it means that the quality value of all PDCCH beams falls below the BLER threshold.

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

[0120] As a first method, an implicit configuration method for BFD-RS may be supported. In each search space, a control resource set (CORESET) ID, which is a resource area where PDCCH can be transmitted, is set, and for each CORESET ID, RS information (e.g., CSI-RS resource ID, SSB ID) that is QCLed in terms of spatial RX parameters can be indicated / set. RS information that is QCLed in terms of spatial RX parameters can be indicated or set through TCI (transmit configuration information). That is, BFD-RS can be implicitly configured / instructed to the terminal based on QCL information indicated or set through TCI.

[0121] Here, when the base station instructs or sets the terminal to an RS that is QCL in terms of spatial reception parameters (i.e., QCL Type D RS), the terminal may use the beam that was used for receiving the RS that is QCL in terms of spatial reception parameters when receiving a specific PDCCH DMRS. That is, between spatially QCL antenna ports, signals can be transmitted via the same transmission beam or similar transmission beams (for example, cases where the beam direction is the same / similar but the beam width is different).

[0122] As a second method, an explicit configuration method for BFD-RS may be supported. The base station may explicitly configure or instruct the terminal to use a beam RS for BFD purposes. In this case, the beam RS may correspond to the 'all PDCCH beams' mentioned above.

[0123] 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 against the configured (or specified) BFD-RS degrades above a certain threshold. Then, the terminal MAC sublayer can determine that a beam failure has occurred and initiate the relevant RACH operation if a BFI occurs a certain number of times (e.g., 'beamFailureInstanceMaxCount') within a certain time (e.g., 'BFD timer').

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

[0125] As described above, when a certain number of BFIs occur, the terminal determines that a beam failure has occurred and can perform a beam failure recovery operation. As an example of a beam failure recovery operation, the terminal can perform a BFRQ process based on RACH (i.e., PRACH). Below, the BFRQ process will be examined in detail.

[0126] The base station may configure a candidate Beam RS List ('candidateBeamRSList') containing candidate Beam RSs that can be substituted in the event of a beam failure to the terminal via RRC signaling. Additionally, the base station may configure dedicated PRACH resources for the said candidate Beam RSs. In this case, the dedicated PRACH resources may be non-contention-based PRACH resources (or contention-free PRACH resources). If a substitute Beam RS is not found in the candidate Beam RS List, the terminal may select at least one of the pre-configured SSB resources. Then, the terminal may transmit a collision-based PRACH to the base station based on the selected at least one.

[0127] Improved beam failure recovery

[0128] When Carrier Aggregation (CA) is applied, a specific SCell may not have an uplink carrier (UL carrier). In other words, for a SCell that has only a downlink carrier, uplink transmission is impossible. Furthermore, even if an SCell has an uplink carrier, collision-based PRACH cannot be established. Therefore, the PRACH-based BFR process with CA applied can be applied exclusively to SpCells (PCells or PSCells), and BFR processing may not be supported in SCells. That is, according to basic BFR operation, PRACH-based BFR operation in SpCells may not be supported in SCells.

[0129] Specifically, if a high-frequency band requiring BFR is configured as SCell, the PRACH-based BFR process may not be supported in that high-frequency band. For example, if you intend to operate a PCell in a low-frequency band (e.g., 6 GHz or lower) and a SCell in a high-frequency band (e.g., 30 GHz), there is a problem in that the PRACH-based BFR process is not supported in the high-frequency band where BFR support is more necessary.

[0130] To resolve the aforementioned problem, the improved BFR operation includes an operation for BFR of the SCell. For example, the terminal can perform a BFRQ for the SCell using a dedicated PUCCH resource for BFRQ configured in the SpCell. For convenience of explanation, the above 'dedicated PUCCH resource' will be referred to as BFR-PUCCH below.

[0131] The role of the aforementioned BFR-PUCCH is to report only 'information on BF occurrences for the SCell' to the base station. Additionally, detailed information related to the occurred BF may be transmitted to the base station via BFR MAC-CE or UCI as a subsequent report.

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

[0133] In addition, the above 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, when a terminal detects a BFR for SCell, there is an UL-SCH allocated from the base station, the terminal can skip the BFR-PUCCH transmission procedure, just like the SR transmission procedure, and immediately transmit the BFR MAC-CE to the base station through the allocated UL-SCH.

[0134] In a multi-TRP environment, multi-DCI and / or single-DCI-based TRP-specific BFR behaviors may be applied. First, the base station may explicitly or implicitly set BFD RS for the terminal. For example, the base station may set two or more BFD-RS sets for the terminal via RRC or / and MAC-CE. As another example, BFD-RS sets may be set based on the TCI status per CORESET pool. The terminal may determine whether a beam has failed per TRP based on the aforementioned BFD-RS sets.

[0135] When a beam failure is detected, an SR PUCCH resource may be configured for the terminal according to the base station's BFRQ resource. Separate SR PUCCH resources may be configured for each TRP, or the same SR PUCCH resource may be used by two TRPs. When a beam failure occurs at a specific TRP, the terminal can transmit the configured BFRQ SR PUCCH (to a TRP where no beam failure has occurred). The TRP that receives the BFRQ may transmit a UL Grant DCI to the terminal, and the terminal may transmit a BFR MAC-CE via a PUCCH scheduled / assigned by the UL Grant DCI. The BFR MAC-CE may include a CC list where the beam failure occurred, information about the failed BFR RS set, and information on whether a new beam has occurred.

[0136] PUCCH Configuration and Format

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

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

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

[0140] As another example, when the PUCCH format is 1, the supported UCI payload size is up to 2 bits, and the number of OFDM symbols constituting a single PUCCH can be 4 to 14. As another example, when the PUCCH format is 3 or 4, the supported UCI payload size is greater than 2 bits, and the number of OFDM symbols constituting a single PUCCH can be 4 to 14.

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

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

[0143] In wireless communication systems, Layer-1 (e.g., physical layer) based uplink control information has the advantage of having a smaller transmission delay compared to higher-layer based control information. For example, in order for a terminal to transmit information to a base station via MAC-CE or RRC messages, the terminal's SR procedure and the base station's PUSCH allocation procedure (based on the SR) may be required, resulting in delay and overhead. Additionally, generally, the higher the layer of information, the longer the time required to decode the information (e.g., decoding time or / and processing time).

[0144] On the other hand, in order to transmit Layer-1 based uplink control information, UL physical channel resources (e.g., PUCCH, PUSCH) must be (pre-)configured / allocated to the corresponding terminal. Therefore, from the perspective of the base station / network, 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.

[0145] Accordingly, in a wireless communication system, information that must be transmitted relatively urgently for the operation of the physical layer (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 determination), beam information (e.g., beam information for (analog) beam determination) can be transmitted and received via the physical layer UCI.

[0146] Here, the base station or / and the network can determine / control the reporting timing of HARQ-ACK, CSI, beam information, etc., excluding SR. When such network-initiated / triggered reporting procedures are applied, there is a limitation that in environments where the wireless channel condition is likely to change rapidly, the reporting timing must be set / instructed so that the terminal can frequently transmit UCI.

[0147] In other words, in environments where 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 where the power consumption of the terminal increases due to frequent UL transmissions. Additionally, or alternatively, the more terminals there are within the cell / TRP coverage, the greater the UL resource overhead may become, as UL resources must be allocated to each terminal.

[0148] To overcome the limitations of such NW-initiated / triggered reporting, UE-initiated / triggered reporting methods or event-based / triggered reporting methods may be applied.

[0149] When UE-initiated / triggered reporting methods or event-based / triggered reporting methods are applied, the terminal can determine whether and when to report (such as UCI). That is, the terminal can perform the relevant (UCI) report only when necessary (e.g., only when a specific event occurs). Accordingly, UL resource overhead and terminal power consumption can be reduced. Additionally, since the terminal reports information based on Layer-1 / lower layers, faster reporting may be possible.

[0150] Accordingly, standardization of UE-initiated / triggered beam reporting schemes can proceed in next-generation wireless communication systems.

[0151] In addition, for the efficient operation of UL resources in next-generation wireless communication systems, UE-initiated / triggered or event-based transmission methods can be definitively applied to control information, TB (transport block), and user-plane data transmission procedures transmitted via UCI and / or MAC-CE.

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

[0153] For example, a BFR reporting method includes an operation to report whether a BF has occurred and information related to a new beam. Here, information regarding whether a BF has occurred and information related to a new beam may be transmitted to a base station according to an explicit or implicit method (e.g., a method of transmitting a new beam index as PRACH resource selection information). Additionally, information regarding whether a BF has occurred and information related to a new beam may be transmitted in stages, either at once or in multiple steps, through one or two UL resources. For example, a terminal may transmit a BFRQ to a base station via PUCCH and transmit beam information to a base station via MAC-CE on PUCCH.

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

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

[0156] This disclosure describes, but is not limited to, event-based or terminal-initiated / triggered beam reporting. The method according to this disclosure may also be applied to other event-based or terminal-initiated / triggered transmission and reception procedures (e.g., UCI reporting procedures, uplink transmission and reception procedures, etc.).

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

[0158] The following describes a method to utilize UL resources more efficiently while reducing UL overhead in UE-initiated / triggered transmission methods (e.g., reporting methods) or event-based / triggered transmission methods (e.g., reporting methods).

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

[0160] The terminal can receive first configuration information related to a first uplink resource for transmitting the first information from the base station (S710).

[0161] For example, the first configuration information may include, but is not limited to, the period and size of the first uplink resource, the period of the first uplink channel based on the first uplink resource, the (maximum) payload size, the time of transmission of the first information, the priority of the first information or / and the first uplink channel.

[0162] Additionally or alternatively, the terminal may receive second configuration information related to the first event from the base station. The second configuration information may include, but is not limited to, at least one of the type of the first event, the condition related to the first event, or the resource related to the first event. Additionally or alternatively, the terminal may receive third configuration information from the base station regarding whether to include both the first information and the second information related to the first event on the first uplink channel based on the first uplink resource.

[0163] Each of the first configuration information, the second configuration information, and the third configuration information may be transmitted to the terminal via one upper layer signaling (e.g., SIB, RRC message, MAC-CE) and / or DCI, but is not limited thereto. Each of the first configuration information, the second configuration information, and the third configuration information may be transmitted to the terminal via separate upper layer signaling and / or DCI. Additionally, the terminal may receive at least one of the configuration information described with reference to FIG. 9 from the base station.

[0164] As an example of the present disclosure, the first information may collectively refer to information intended to be transmitted through a first uplink resource regardless of the occurrence of a first event.

[0165] For example, the first information includes channel state information (CSI), and the first uplink resource may include a periodic or semi-persistent (physical) uplink control channel resource or a (physical) uplink shared channel resource.

[0166] As another example, the first information includes at least one of SR, HARQ-ACK, CSI, and LRR (link recovery request), and the first uplink resource may include a configured grant (physical) uplink control channel resource or a (physical) uplink shared channel resource. The first information may be included in the first UCI, but is not limited thereto.

[0167] Based on the occurrence of a first event, the terminal can transmit second information related to the first event to the base station through a first uplink channel based on a first uplink resource (S720).

[0168] Specifically, the terminal may monitor whether a first event occurs based on at least one set information. For example, the first event may include, but is not limited to, an event related to whether the quality value of a serving beam is below a first threshold, or an event related to the identification of at least one beam whose quality value exceeds a second threshold. The type of the first event may be set to various events according to the second set information. For example, if the type of the first event is an event related to whether the quality value of a serving beam is below a first threshold, the second information may include the quality value of the serving beam, information about the cell associated with the serving beam, information about the new beam, etc. Based on the fact that the type of the first event is an event related to the identification of at least one beam whose quality value exceeds a second threshold, the second information may include the index of at least one beam and the quality value of said at least one beam. The second information may be transmitted to a base station via a UCI (e.g., a second UCI), but is not limited thereto.

[0169] When it is identified that a first event has occurred, the terminal may transmit second information to a base station via a first uplink channel using a first uplink resource for the first information. Here, the first uplink channel may include third information related to whether the second information is information related to the first event. The third information may include an indicator or flag related to the type of the second information included in the first uplink channel. However, this is merely one embodiment, and the third information may be omitted on the first uplink channel.

[0170] For example, based on the third setting information, the second information may be included on the first uplink channel and the first information may not be included, so that the second information is included on the first uplink channel.

[0171] As another example, whether the first information is included on the first uplink channel may be determined based on the priority of the first information and the second information. For example, based on the fact that the priority of the second information is higher than the priority of the first information, the first uplink channel may include only the second information and not the first information. Based on the fact that the priority of the first information is higher than the priority of the second information, the first uplink channel may include both the first information and the second information.

[0172] Additionally or alternatively, whether the first information is included on the first uplink channel may be determined based on the size of the (maximum) payload of the first uplink channel based on the first uplink resource. For example, if the (maximum) payload size of the first uplink channel is greater than or equal to the sum of the sizes of the first information and the second information, the first uplink channel may include both the first information and the second information. If the payload size of the first uplink channel is smaller than the sum of the sizes of the first information and the second information, the first uplink channel may include only the second information and not the first information.

[0173] The above-described operation may be performed when the transmission time of the first information and the transmission time of the second information overlap. For example, if the interval between the transmission time of the first information and the transmission time of the second information is less than or equal to a predefined value (e.g., a predefined slot / symbol size, etc.), the terminal may transmit the second information related to the first event to the base station through a first uplink channel based on the first uplink resource.

[0174] Additionally or alternatively, if the transmission time of the first information and the transmission time of the second information overlap, an operation to determine whether the third setting information is valid and / or whether the above-described first information and / or second information is included in the first uplink channel (e.g., an operation related to the (maximum) size of the first uplink payload, priority related to the first / second information, etc.) may be performed.

[0175] Additionally or alternatively, the terminal may monitor the occurrence of two or more events. For example, the second configuration information may include information related to another event (e.g., the second event). Additionally or alternatively, the terminal may receive configuration information related to another event from the base station.

[0176] Based on the fact that the first event and the second event occur in the same time interval (e.g., when the occurrence times of the first event and the second event overlap and / or the difference in the occurrence times of the first event and the second event is less than a predefined value), the terminal can identify the event associated with the information to be transmitted through the first uplink channel according to the priority of the first event and the second event.

[0177] For example, if the priority of the first event is higher than the priority of the second event, the terminal can transmit second information related to the first event to the base station through the first uplink channel. That is, the terminal can preferentially transmit information related to the event with higher priority to the base station through the first uplink channel.

[0178] In one example of the present disclosure, a terminal may transmit a second uplink channel containing fourth information indicating that second information related to a first event is included on a first uplink channel to a base station. In one example, based on the occurrence of a first event, the terminal may transmit a second uplink channel containing fourth information to a base station and then transmit a first uplink channel containing first information.

[0179] The method described in the example of FIG. 7 can 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 a first uplink resource for transmitting first information from a base station through one or more transceivers (106). Based on the occurrence of a first event, one or more processors (102) may transmit second information related to the first event to a base station through one or more transceivers (106) via a first uplink channel based on the first uplink resource.

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

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

[0182] The base station can transmit first configuration information related to the first uplink resource for transmitting the first information to the terminal (S810).

[0183] Examples of one or more configuration information transmitted by the base station have been explained with reference to FIG. 7, so redundant explanations will be omitted.

[0184] Based on the occurrence of a first event, the base station can receive second information related to the first event from the terminal through a first uplink channel based on a first uplink resource (S820).

[0185] In one example of the present disclosure, a base station may receive from a terminal a second uplink channel containing fourth information indicating that second information is included on a first uplink channel. And, the base station may receive from a terminal a first uplink channel containing second information.

[0186] The method described in the example of FIG. 8 can 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 can transmit first configuration information related to a first uplink resource for transmitting first information from a terminal through one or more transceivers (206). Based on the occurrence of a first event, one or more processors (202) can receive second information related to the first event from a terminal through one or more transceivers (206) via a first uplink channel based on the first uplink resource.

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

[0188] Below, UE-initiated / triggered transmission / reception methods (e.g., reporting methods, etc.) or event-based / triggered transmission / reception methods will be explained in more detail.

[0189] Example 1

[0190] Example 1 relates to a method for transmitting / reporting event information through UL channel resources for other UL transmission / reporting (e.g., P(periodic) / SP(semi-persistence) CSI / beam reporting on PUCCH / PUSCH, etc.).

[0191] The base station can set / instruct the terminal to perform event-based transmission / reporting through the same UL channel resources and the same resources configured to perform other UCI transmissions / reports (e.g., transmissions / reports unrelated to events).

[0192] When an event occurs, the terminal may transmit event information through UL channel resources (e.g., resources configured for transmission / reporting unrelated to the event, etc.) by using / applying at least one of the methods described below:

[0193] Method 1-1: How to transmit event information (e.g., transmission / reporting information related to the event) instead of other transmission / reporting information

[0194] Method 1-2: A method of transmitting some or all of other transmission / reporting information together with some or all of event information (e.g., transmission / reporting information related to the event).

[0195] That is, Example 1 relates to a method for performing event-based reporting by reusing UL channel resources configured for other UCI transmissions / reports. According to Method 1-1, even without configuring separate UL channel resources for event-based transmissions / reports, the terminal can perform event-based transmissions / reports (based on UL channel resources configured for other UCI transmissions / reports), and thereby save UL channel resources. Additionally, according to Method 1-2, other transmission / report information can be transmitted along with information related to the event.

[0196] In one example of the present disclosure, when Method 1-1 is applied, to resolve ambiguities related to information decoding / interpretation by a base station, the terminal may transmit an indicator or flag indicating whether the information being reported (at each reporting time) is pre-set information or event information. For example, the terminal may transmit an indicator or flag indicating the type of information being reported (e.g., whether the information being reported is event-related information or pre-set information) to the base station along with the information. Here, the pre-set information may include a UCI (not related to an event), and a UL resource for transmitting the said UCI may be set by the base station.

[0197] Additionally or alternatively, when multiple events (i.e., multiple types of events) are applied, the terminal may include an indicator or flag, etc., indicating whether the information currently being reported is related to which event.

[0198] As an example of the present disclosure, when Method 1-2 is applied, the terminal may transmit and / or report other reporting information (e.g., UCI unrelated to the event) and information related to the event (via UL channel resources for other reporting information).

[0199] Additionally or alternatively, the terminal may transmit some or all of the other reporting information and / or some or all of the information related to the event to the base station, taking into account the capacity of the relevant UL channel resource and / or the importance of the information (e.g., the importance of each of the other reporting information and / or the information related to the event).

[0200] Additionally, similar to Method 1-1, the terminal may transmit information regarding the type of information being reported and / or the event associated with the information being reported to the base station via separate indicators and / or flags. Accordingly, the base station can easily identify and interpret the type of information reported by the terminal. For example, the indicators and / or flags may be included in UCI Part 1, and information related to the event may be included in UCI Part 2. By preferentially decoding the indicators and / or flags, the base station can determine the type of information included in UCI Part 2 (e.g., whether only pre-set information is included in UCI Part 2, or whether both pre-set information and information related to the event are included). Accordingly, the base station can easily determine the payload size of UCI Part 2.

[0201] As an example of the present disclosure, a base station may set / instruct a terminal whether to apply Method 1-1 and / or Method 1-2. Additionally or alternatively, one of Method 1-1 and / or Method 1-2 may be adaptively applied depending on the type / priority of information (e.g., information related to an event or / and other reporting information) and / or the capacity of the UL channel (e.g., (maximum) payload size), etc.

[0202] For example, if the importance or priority of information related to an event is high (e.g., if the importance or priority of information related to an event is higher than the importance or priority of pre-set information), Method 1-1 is applied, and if not, Method 1-2 is applied.

[0203] As another example, if the capacity of the UL channel (e.g., the capacity of the UL resource set by the base station) is sufficient to transmit information related to the event and other reporting information, Method 1-2 is applied, and if not, Method 1-1 is applied.

[0204] Example 1-1

[0205] Example 1-1 relates to a method for performing event-based CSI / beam reporting through PUCCH / PUSCH resources for P / SP CSI / beam reporting.

[0206] The base station may configure uplink resources (e.g., PUCCH or / and PUSCH resources) for the terminal to report periodic (P) or semi-continuous (SP) CSI / beam information to the terminal. Additionally, the base station may enable P / SP CSI / beam reporting operations via RRC / MAC-CE / DCI, etc. The terminal may periodically report CSI / beam information requested by the base station via uplink resources. Additionally, or alternatively, when an "event" occurs, the terminal may transmit information related to the event instead of CSI / beam information (Method 1-1), or transmit information related to the event and CSI / beam information together (Method 1-2).

[0207] Examples 1-2

[0208] Examples 1-2 relate to a method for performing event-based CSI / beam reporting operations through a configured grant (CG) uplink resource (e.g., PUSCH resource) (for TB transmission).

[0209] The base station configures the CG uplink resource for the terminal, and the terminal can perform TB transmission through the configured CG uplink resource. Additionally or alternatively, the terminal can perform event-based reporting (e.g., event-based CSI / beam / UCI reporting, etc.) using the said CG uplink resource.

[0210] In particular, when event-based reporting is performed via UCI and an event occurs or Method 1-1 applies, at the time of transmission of the relevant CG uplink resource (e.g., at the time of transmission of the PUSCH resource), an uplink containing UCI (e.g., PUSCH) may be transmitted to the base station. As another example, when the occurrence of the relevant event and TB transmission occur simultaneously (e.g., when Method 1-2 applies), an uplink containing UCI and UL-SCH may be transmitted to the base station at the time of transmission of the relevant uplink resource.

[0211] For example, assume a case where event-based reporting is performed via MAC-CE and information related to the event and TB transmission occur simultaneously (e.g., when Method 1-2 is applied). In this case, the MAC-CE and the TB can be transmitted together to the base station via UL-SCH transmitted at the time of transmission of the CG uplink resource.

[0212] For example, considering various applications such as voice calls, the above TB transmission may have the characteristics of event-based transmission (e.g., occurrence of voice information / TB). Event-based TB transmission may have a higher priority than event-based CSI / beam / UCI reporting. In this case, (unlike Method 1-1) if an event related to TB transmission and an event related to CSI / beam / UCI occur simultaneously, the terminal may perform TB transmission first.

[0213] The method associated with Example 1 (e.g., Method 1 and Method 2, etc.) can be applied to various operations as well as to the above-described Examples 1-1 and 1-2. For example, the method associated with Example 1 can be applied to non-periodic CSI / beam reporting. In this case, the base station can configure event-based transmission / reporting for the terminal as an "add-on feature."

[0214] Examples 1-3

[0215] Examples 1-3 relate to a method for performing multiple event-based transmissions / reports through the same UL channel resource. That is, Examples 1-3 is an extension of Examples 1, 1-1, 1-2, and 1-4 into multiple event-based transmission / reporting techniques.

[0216] For example, a base station may configure a terminal to report event information #1 for event #1 and event information #2 for event #2 based on the same UL channel resource. Accordingly, if only event #1 occurs at a specific reporting time, the terminal may report event information #1 to the base station via the UL channel. If only event #2 occurs at a specific reporting time, the terminal may report event information #2 to the base station via the UL channel. If both event #1 and event #2 occur at a specific reporting time, the terminal may report one of event information #1 and event information #2 to the base station via the UL channel (e.g., Method 1-1), or report all or part of event information #1 and all or part of event information #2 to the base station (e.g., Method 1-2).

[0217] For the operation described above, priorities may be defined / set per event or per event information. For example, if multiple events occur simultaneously or within a predefined time interval, the terminal may be defined / set / instructed to prioritize transmitting / reporting the event or event information having a higher priority to the base station.

[0218] In the example described above, two events (e.g., Event #1 and Event #2) or two event information (e.g., Event Information #1 and Event Information #2) were described, but the number of events and event information is not limited. That is, the method described above (e.g., transmitting event / event information through the same UL channel resource) can be extended to three or more events / event information.

[0219] Examples 1-4

[0220] Examples 1-4 relate to a method of using separate UL channel resources according to the configuration of reporting information. Examples 1-4 relate to a method of extending Examples 1, 1-1, 1-2, and 1-3.

[0221] The base station may separately configure UL channel resources (e.g., PUCCH resources and / or PUSCH resources, etc.) to be used for the terminal according to the configuration of the reported information. The terminal may perform the information / reporting through the UL channel resources according to the configuration of the information to be transmitted / reported at that time (e.g., information on whether an event has occurred, etc.). For example, when Method 1-1 or Method 1-2 is applied, the terminal may use different UL channel resource formats depending on whether the event information is transmitted (considering the payload size and reliability suitable for each information configuration).

[0222] Additionally or alternatively, when transmitting one of the two pieces of information (e.g., reporting information related to an event and other reporting information (e.g., information not related to an event)) or transmitting the two pieces of information together, rules regarding which of the UL channel resources to use / apply according to the configuration of each piece of information may be defined / set.

[0223] For example, assume that UL channel resource #1 for event reporting and UL channel resource 2 for "transmission / reporting of other information" are configured for a terminal. In this case, when an event occurs, Method 1-1 or Method 1-2 may be applied, and whether to report the information through UL channel resource #1 or UL channel resource #2 may be configured / defined as a rule.

[0224] For example, a base station can verify the composition of information transmitted by a terminal (e.g., information on whether an event has occurred) by blind detection of multiple pre-configured UL channel resource candidates at each time the terminal reports.

[0225] Additionally or alternatively, the base station may set the transmission / reporting (possible) timing and / or period for each piece of information and / or related UL channel resource for the terminal. For example, when the method according to Example 1 is applied, i) the period of event reporting or the period of the UL channel resource corresponding to the event reporting and ii) the period of "other transmission / reporting" or the period of the UL channel resource related thereto, each may be set for the terminal. In addition, i) the slot offset applied to the period of event reporting or the UL channel resource corresponding to the event reporting and ii) the slot offset applied to the period of "other transmission / reporting" or the UL channel resource related thereto, each may be set for the terminal.

[0226] Here, the methods according to the above-described Examples 1, 1-1, 1-2, 1-3, and 1-4 may be utilized only when the reporting (possible) times of each information overlap. When the reporting (possible) times of each information do not overlap, the terminal may use the UL channel resources configured for each information / transmission.

[0227] For example, assume that an event reporting period / resource and another UCI (or UL) transmission period / resource are each configured for the terminal. At an event reporting time that does not overlap with another UCI (or UL) transmission time, the terminal can transmit information related to the event to the base station through the resource configured for the event reporting. At an event reporting time that overlaps with another UCI (or UL) transmission time, the terminal can transmit information related to the event to the base station through the resource configured for the other UCI transmission.

[0228] As another example, if the event reporting period is a multiple of another UCI (or UL) transmission period, at another UCI (or UL) transmission time that does not overlap with the event reporting time, the terminal can perform another UCI (or UL) transmission through the resources configured for the other UCI (or UL) transmission. And, at another UCI (or UL) transmission time that overlaps with the event reporting time, the terminal can perform another UCI transmission through the resources configured for the event reporting.

[0229] In one example of the present disclosure, when event information is divided into one or more information parts / blocks, the method(s) according to Example 1 and detailed embodiments thereof may be applied to only some of the information parts / blocks among the one or more information parts / blocks. For example, when information regarding whether an event has occurred is transmitted via a UCI having a small number of bits, such as SR / BFRQ, and the remaining event information (e.g., information about a new beam) is transmitted via a UCI or MAC-CE having a large number of bits, the method(s) according to Example 1 and detailed embodiments thereof may be applied / utilized to only one of the two event information parts / blocks.

[0230] For example, the method(s) according to Example 1 and its detailed embodiments may be applied only to event information applied through a UCI having a small number of bits, or only to event information transmitted through a UCI having a large number of bits. However, this is merely one example, and the method(s) according to Example 1 and its detailed embodiments may be applied to all information related to the event.

[0231] Example 2

[0232] Example 2 relates to a method for event-based beam reporting through a (dedicated) uplink resource (e.g., PUCCH resource or PUSCH resource, etc.).

[0233] (Unlike the method according to Example 1 and its detailed embodiments) a dedicated UL channel resource for event-based beam reporting may be configured / used. For example, information related to an event, including whether an event has occurred, may be defined / configured as a UCI that occurs / is generated when a specific event occurs (such as a positive SR (scheduling request)). Additionally, a separate PUCCH resource may be configured for the terminal to transmit the said information / UCI.

[0234] To this end, PUCCH resources having PUCCH formats capable of transmitting information of 2 bits or less (e.g., PUCCH format 0 / 1), as well as PUCCH formats capable of transmitting information exceeding 2 bits (e.g., PUCCH format 2 / 3 / 4), can be configured / used for the terminal for event-based beam reporting purposes. That is, the terminal can transmit a PUCCH containing event-related information to the base station based on the PUCCH resources having the aforementioned PUCCH formats. Here, methods such as UCI encoding, multiplexing, and RE mapping applied to CSI can also be applied to PUCCH resources.

[0235] Here, if the PUCCH resource is a resource transmitted only when an event occurs, the base station cannot predict the timing of the event; therefore, orthogonal / independent PUCCH resources may be allocated to each terminal for each event. Consequently, a problem arises in which UL resource overhead increases in proportion to the PUCCH resource. A similar problem existed with SR PUCCH resources in basic wireless communication systems. However, in this case, PUCCH resources using small time / frequency code resources of 2 bits or less were used, and this did not pose a significant problem.

[0236] To address the aforementioned problem, the (maximum) payload size of the beam report information reported as event information can be limited to reduce the PUCCH resource overhead associated with the report.

[0237] In one example of the present disclosure, when a terminal performs an event-based beam reporting operation (via a dedicated PUCCH resource), the terminal may transmit beam indicators (e.g., CRI, SSBRI) and / or beam quality value information (e.g., L1-RSRP, L1-SINR) to a base station in addition to information regarding whether an event has occurred. In this case, the beam indicators and / or beam quality value information may be limited as described below.

[0238] For example, with respect to beam indicators, the number of reported beams may be limited or fixed. For example, only information regarding a single beam (e.g., indicator information for a single beam) may be reported to the base station. Additionally, or alternatively, one or more beam groups / sets may be configured, and a beam group / set ID may be reported to the base station instead of a beam ID.

[0239] For example, beam quality information may be omitted, or only coarse beam quality information may be transmitted to the base station through a predefined number of bits (e.g., 3 to 4 bits). Additionally or alternatively, beam quality value information may include the difference in quality values ​​of a target beam relative to a specific beam (e.g., RSRP / SINR difference).

[0240] As an example of coarsely configuring the beam quality value in Example 2, the payload size can be reduced by considering a step size of n dB or more for the L1-RSRP / SINR value (e.g., n is a value greater than 1 (e.g., 2)). In a basic wireless communication system, the L1-RSRP / SINR value is reported using 7 bits ([-140, -44] dBm) with a 1 dB step size, but the method described above can set the step size value to a large value.

[0241] Additionally, regarding the method of configuring the difference in quality values ​​of a target beam relative to a specific beam, the specific beam may include i) a designated TCI, ii) a CRI / SSBRI having the highest RSRP / SINR in the beam reports set by the base station and / or terminal-initiated, iii) a CORESET TCI, iv) the first / highest RSRP / SINR among the reported RSRP / SINRs, etc. The case related to iv) may apply when reporting RSRP / SINRs for two or more beams.

[0242] Additionally or alternatively, if two or more TCI / CORESETpools are configured / instructed to the terminal for mTRP operation, etc., the terminal may configure / transmit beam information (e.g., beam indicator and / or beam quality value information) to which the method described above is applied based on one of the two or more TCI / CORESETpools.

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

[0244] 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 above-described disclosure (e.g., Example 1, Example 1-1, Example 1-2, Example 1-3, Example 1-4, Example 2 or / and a combination of one or more of the detailed embodiments thereof) may be applied.

[0245] Here, the UE / network side is exemplary and can be replaced with various devices as described with reference to FIG. 10. FIG. 9 is for convenience of explanation and is not intended to limit the scope of the present disclosure. Also, some step(s) shown in FIG. 9 may be omitted depending on the situation and / or settings, etc. Additionally, 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.

[0246] 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 RRHs (remote radio heads) / RRUs (remote radio units).

[0247] For example, an ideal / non-ideal backhaul may be established between TRP 1 and TRP 2 that constitute the network side. Additionally, although the following description is based on multiple TRPs, it can be extended and applied equally to transmission through multiple panels / cells, and can also be extended and applied to transmission through multiple RRH / RRUs, etc.

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

[0249] 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 that single terminal. Configuration of such CORESET groups (or CORESET pools) can be performed through upper-layer signaling (e.g., RRC signaling).

[0250] In addition, the term "base station" may refer collectively to an object that performs data transmission and reception 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. Additionally, the TPs and / or TRPs may include the base station's panels, transmission and reception units, etc.

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

[0252] For example, the configuration information may include event-related configuration information (or / and event-based reporting-related configuration information), reporting information configuration information, and UL channel resource information for reporting (e.g., PUCCH / PUSCH). 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 event, etc.

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

[0254] Additionally or alternatively, the configuration information may include configuration information associated with each of Example 1, Example 1-1, Example 1-2, Example 1-3, Example 1-4, Example 2, or / and one or more combinations of the detailed embodiments. For example, the configuration information may include information for configuring one of Method 1-1 and Method 1-2 according to Example 1. For another example, the configuration information may include information for configuring a method of configuring reporting information according to Example 2.

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

[0256] The base station can transmit RS (e.g., CSI-RS, SSB, etc.) related to an event (e.g., an event related to configuration information) to the terminal (S110). The terminal can perform measurements based on the RS received from the base station and monitor whether an event has occurred based on the measurement results (S115). That is, the terminal can monitor whether an event has occurred based on the configuration information.

[0257] If, depending on the characteristics / definition / setting of the "event" or / and the triggering condition of the UL channel resource, the event / condition is not related to RS reception / measurement, step S110 may be omitted, and the terminal may perform separate event occurrence monitoring according to the triggering condition.

[0258] The terminal can report / transmit information related to the event and / or "other information" to the base station based on the configuration information and RS measurement (S120). For example, the terminal can report / transmit information related to the event and / or "other information" to the base station according to the period set by the configuration information.

[0259] For example, the terminal may perform a reporting operation according to the method(s) according to Example 1, Example 1-1, Example 1-2, Example 1-3, Example 1-4, Example 2 or / and a combination of one or more of the detailed embodiments.

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

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

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

[0263] The 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 memory (104) and / or transceivers (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed in this disclosure.

[0264] For example, the processor (102) can process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) can receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the signal processing of the second information / signal in the memory (104).

[0265] 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 store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the descriptions, functions, procedures, proposals, methods, and / or sequences of operation disclosed in this disclosure. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement 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 through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be combined with an RF (Radio Frequency) unit. In the present disclosure, the device may refer to a communication modem / circuit / chip.

[0266] The second device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed in this disclosure. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code including instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or sequences of operation disclosed in this disclosure. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with an RF unit. In this disclosure, the term "device" may refer to a communication modem / circuit / chip.

[0267] Hereinafter, 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 Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this 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 flowcharts disclosed in this disclosure. One or more processors (102, 202) may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this disclosure and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., a baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this disclosure.

[0268] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or 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 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. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this disclosure may be included in 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 sequences disclosed in this disclosure may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0269] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0270] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of the present disclosure to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in the present disclosure from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may 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 connected 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, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this disclosure through one or more antennas (108, 208). In this disclosure, one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0271] The embodiments described above are combinations of the components and features of the present disclosure in a specific form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, it is possible to construct 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 obvious that embodiments may be constructed by combining claims that are not explicitly related in the claims, or that they may be included as new claims by amendment after filing.

[0272] It is obvious to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential features of the present disclosure. Accordingly, the detailed description set forth above should not be interpreted restrictively in all respects and should be considered exemplary. The scope of the present disclosure shall be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are included within the scope of the present disclosure.

[0273] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that enable operations according to the methods of various embodiments to be executed on a device or computer, and a non-transitory computer-readable medium on which such software or instructions, etc. are stored and executable on a device or computer. Instructions that may be used to program a processing system to perform the features described in the present disclosure may be stored on or within a storage medium or a computer-readable storage medium, and the features described in the present disclosure may be implemented using a computer program product comprising such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and may 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 may optionally include one or more storage devices located remotely from the processor(s). Memory or alternatively, non-volatile memory device(s) within memory comprises a non-transient computer-readable storage medium. The features described in this disclosure may be stored in any one of the machine-readable media and integrated into software and / or firmware that can control the hardware of a processing system and allow the processing system to interact with other mechanisms utilizing results according to the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0274] Here, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include LTE, NR, and 6G, as well as Narrowband Internet of Things for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally or generally, the wireless communication technology implemented in the device (100, 200) of the present disclosure may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least 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 names mentioned above. Additionally or generally, wireless communication technology implemented in the device (100, 200) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology may create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names. Industrial applicability

[0275] Although the method proposed in this disclosure has been described with an example applied to 3GPP LTE / LTE-A and 5G systems, it can be applied to various wireless communication systems in addition to 3GPP LTE / LTE-A and 5G systems.

Claims

Claim 1 A method comprising: receiving first configuration information related to a first uplink resource for transmitting first information from a base station by a terminal; and transmitting second information related to the first event to the base station by the terminal through a first uplink channel based on the first uplink resource based on the occurrence of a first event, wherein the first uplink channel includes third information related to whether the second information is information related to the first event. Claim 2 A method according to claim 1, wherein, based on the priority of the second information being higher than the priority of the first information, the first uplink channel does not include the first information, and based on the priority of the first information being higher than the priority of the second information, the first uplink channel includes the first information. Claim 3 A method according to claim 1, wherein if the payload size of the first uplink channel is greater than or equal to the sum of the sizes of the first information and the second information, the first uplink channel includes the first information, and if the payload size of the first uplink channel is smaller than the sum of the sizes of the first information and the second information, the first uplink channel does not include the first information. Claim 4 A method according to claim 1, wherein the transmission time of the first information and the transmission time of the second information overlap. Claim 5 A method according to claim 1, wherein the priority of the first event is higher than the priority of the second event, based on the fact that the first event and the second event occur in the same time interval. Claim 6 A method according to claim 1, wherein a second uplink channel containing fourth information indicating that the second information is included on the first uplink channel is transmitted from the terminal to the base station. Claim 7 A method according to claim 1, wherein second setting information including at least one of the type of the first event, a condition related to the first event, or a resource related to the first event is transmitted from the terminal to the base station. Claim 8 A method according to claim 1, wherein the first information includes channel state information (CSI), and the first uplink resource includes a periodic or semi-persistent uplink control channel resource or an uplink shared channel resource. Claim 9 A method according to claim 1, wherein the first information comprises at least one of a scheduling request (SR), a HARQ-ACK (hybrid automatic repeat request-acknowledgement), or a link recovery repeat (LRR), and the first uplink resource comprises a configured grant uplink control channel resource or an uplink shared channel resource. Claim 10 A method according to claim 1, wherein the first event includes an event related to whether the quality value of a serving beam is less than a first threshold value or an event related to the identification of at least one beam whose beam quality value exceeds a second threshold value. Claim 11 A method according to claim 1, wherein a third setting information related to whether to include both the first information and the second information on the first uplink channel is transmitted from the terminal to the base station. Claim 12 A method according to claim 1, wherein, based on the first event being an event related to whether the quality value of the serving beam is less than the first threshold, the second information comprises at least one of the quality value of the serving beam and information about a cell associated with the serving beam or information about a new beam for beam failure recovery, and based on the first event being an event related to the identification of at least one beam whose beam quality value exceeds the second threshold, the second information comprises at least one of the index of the at least one beam or the quality value of the at least one beam. Claim 13 A terminal comprising: one or more transceivers; and one or more processors connected to the one or more transceivers, wherein the one or more processors: receive first configuration information related to a first uplink resource for transmitting first information from a base station through the one or more transceivers; and, based on the occurrence of a first event, are configured to transmit second information related to the first event to the base station through the one or more transceivers via a first uplink channel based on the first uplink resource, and the first uplink channel comprises third information related to whether the second information is information related to the first event. Claim 14 A method comprising: a step of transmitting first configuration information related to a first uplink resource for transmitting first information to a terminal by a base station; and a step of receiving second information related to the first event from the terminal by the base station through a first uplink channel based on the first uplink resource based on the occurrence of a first event, wherein the first uplink channel includes third information related to whether the second information is information related to the first event. Claim 15 A base station comprising: one or more transceivers; and one or more processors connected to the one or more transceivers, wherein the one or more processors transmit first configuration information related to a first uplink resource for transmitting first information to a terminal via the one or more transceivers; and, based on the occurrence of a first event, are configured to receive second information related to the first event from the terminal via the one or more transceivers through a first uplink channel based on the first uplink resource, wherein the first uplink channel comprises third information related to whether the second information is information related to the first event. Claim 16 A processing device configured to control a terminal, wherein the processing device comprises: one or more processors; and one or more computer memories operably connected to the one or more processors and storing instructions for performing a method according to any one of claims 1 to 11 based on execution by the one or more processors. Claim 17 One or more non-transitory computer-readable media storing one or more instructions, wherein the 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 through 11.

Images