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

Abstract

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

Description

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

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

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

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

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

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

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

[0007] A method according to one embodiment of the present disclosure comprises the steps of: receiving, by a terminal, first configuration information related to a first uplink resource for transmitting first information from a base station; and transmitting, by the terminal, second information related to the first event to the base station through a first uplink channel based on the first uplink resource based on 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] According to another embodiment of the present disclosure, a method includes the steps of: transmitting, by a base station, first configuration information related to a first uplink resource for transmitting first information to a terminal; and receiving, by the base station, second information related to the first event from the terminal through a first uplink channel based on the first uplink resource based on 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0037] - BM: beam management

[0038] - CQI: Channel Quality Indicator

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

[0040] - CSI: Channel State Information

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

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

[0043] - DMRS: Demodulation Reference Signal

[0044] - FDM: frequency division multiplexing

[0045] - FFT: fast Fourier transform

[0046] - IFDMA: interleaved frequency division multiple access

[0047] - IFFT: inverse fast Fourier transform

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

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

[0050] - MAC: Medium Access Control

[0051] - NZP: non-zero power

[0052] - OFDM: orthogonal frequency division multiplexing

[0053] - PDCCH: Physical downlink control channel

[0054] - PDSCH: Physical downlink shared channel

[0055] - PMI: precoding matrix indicator

[0056] - RE: resource element

[0057] - RI: Rank indicator

[0058] - RRC: Radio Resource Control

[0059] - RSSI: Received signal strength indicator

[0060] - Rx: Reception

[0061] - QCL: quasi co-location

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

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

[0064] - TDM: Time Division Multiplexing

[0065] - TRP: transmission and reception point

[0066] - TRS: Tracking Reference Signal

[0067] - Tx: transmission

[0068] - UE: user equipment

[0069] - ZP: Zero Power

[0070] System General

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0088] Fig. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied. Referring to Fig. 3, the resource grid is N in the frequency domain. RB μ N sc RB It consists of subcarriers, and one subframe is 14·2 μ It is described as an example, but not limited to, that it consists of OFDM symbols. In an NR system, the transmitted signal is N RB μ N sc RB One or more resource grids consisting of subcarriers and 2 μ N symb (μ) is described by OFDM symbols. Here, N RB μ ≤N RB max,μ is. The above NRB max,μ represents the maximum transmission bandwidth, which may vary not only between numerologies but also between uplink and downlink. In this case, one resource grid may be configured for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is referred to as a resource element and is uniquely identified by an index pair (k, l').

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

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

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

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

[0093] Common resource blocks (CRBs) are numbered from 0 upwards in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of CRB 0 for a subcarrier spacing setting μ coincides with 'point A'. Common resource block number n in the frequency domain CRB μ The relationship between the resource elements (k, l) and the subcarrier spacing setting μ is given by the following mathematical expression 1.

[0094]

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

[0096]

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

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

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

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

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

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

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

[0104] The base station can activate at least one DL / UL BWP among the DL / UL BWP(s) configured at a specific point in time (by L1 signaling or MAC CE (Control Element) or RRC signaling, etc.). In addition, the base station can instruct switching to another configured DL / UL BWP (by L1 signaling or MAC CE or RRC signaling, etc.). Alternatively, switching to a designated DL / UL BWP may be performed when a timer value expires based on a timer. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP. However, since the UE may not receive the configuration for the DL / UL BWP when performing the initial access process or before the RRC connection is set up, the DL / UL BWP assumed by the UE in such a situation is defined as the initially active DL / UL BWP.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0120] Basic beam failure recovery (BFR)

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

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

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

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

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

[0126] Beam failure detection (BFD)

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

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

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

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

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

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

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

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

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

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

[0137] Improved beam failure recovery

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

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

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

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

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

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

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

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

[0146] PUCCH configuration and format

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0168] Below, we describe a method for more efficiently managing UL resources while reducing UL overhead in UE-initiated / triggered transmission / reception schemes (e.g., reporting schemes) or event-based / triggered transmission / reception schemes (e.g., reporting schemes).

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

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

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

[0172] 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, a condition related to the first event, or a 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.

[0173] Each of the first configuration information, the second configuration information, and the third configuration information may be transmitted to the terminal via, but is not limited to, a single upper layer signaling (e.g., SIB, RRC message, MAC-CE) and / or DCI. 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. In addition, the terminal may receive at least one of the configuration information described with reference to FIG. 9 from the base station.

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

[0175] For example, the first information may include 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.

[0176] As another example, the first information may include 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.

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

[0178] Specifically, the terminal may monitor whether a first event occurs based on at least one piece of configuration information. For example, the first event may include, but is not limited to, an event related to whether a quality value of a serving beam is less than a first threshold or an event related to the identification of at least one beam having a beam quality value exceeding a second threshold. The type of the first event may be set to various events according to the second configuration information. For example, if the type of the first event is an event related to whether a quality value of a serving beam is less than the first threshold, the second information may include a quality value of the serving beam, information about a cell related to the serving beam, information about a new beam, and the like. Based on the type of the first event being an event related to the identification of at least one beam having a beam quality value exceeding the second threshold, the second information may include an index of at least one beam and a quality value of the at least one beam, and the like. The second information may be transmitted to the base station via UCI (e.g., a second UCI), but is not limited thereto.

[0179] If the first event is identified as occurring, the terminal may transmit second information to the base station via the first uplink channel using the 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 only one embodiment, and the third information may be omitted from the first uplink channel.

[0180] For example, based on the third configuration information being set to include only the second information on the first uplink channel, the second information may be included on the first uplink channel and the first information may not be included.

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

[0182] 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 less than the sum of the sizes of the first information and the second information, the first uplink channel may not include the first information but may include only the second information.

[0183] 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 via the first uplink channel based on the first uplink resource.

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

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

[0186] Based on the occurrence of the first event and the second event in the same time interval (e.g., the occurrence times of the first event and the second event overlap and / or the difference in occurrence times of the first event and the second event is less than a predefined value), the terminal may identify an event associated with information to be transmitted over the first uplink channel according to the priorities of the first event and the second event.

[0187] For example, if the priority of the first event is higher than that of the second event, the terminal may transmit second information related to the first event to the base station via the first uplink channel. In other words, the terminal may preferentially transmit information related to the event with the higher priority to the base station via the first uplink channel.

[0188] As an example of the present disclosure, a terminal may transmit a second uplink channel to a base station, the second uplink channel including fourth information indicating that second information related to a first event is included on the first uplink channel. For example, based on the occurrence of a first event, the terminal may transmit the second uplink channel including the fourth information to the base station and then transmit the first uplink channel including the first information.

[0189] 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 can 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, the one or more processors (102) can transmit second information related to the first event to the base station through one or more transceivers (106) through a first uplink channel based on the first uplink resource.

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

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

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

[0193] An example of one or more configuration information transmitted by a base station has been described with reference to FIG. 7, so a redundant description will be omitted.

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

[0195] As an example of the present disclosure, a base station may receive from a terminal a second uplink channel including fourth information indicating that second information is included on a first uplink channel. Furthermore, the base station may receive from the terminal a first uplink channel including the second information.

[0196] 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 the terminal through one or more transceivers (206) through a first uplink channel based on the first uplink resource.

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

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

[0199] Example 1

[0200] Embodiment 1 relates to a method for transmitting / reporting event information via UL channel resources for other UL transmissions / reports (e.g., P(periodic) / SP(semi-persistence) CSI / beam reporting on PUCCH / PUSCH, etc.).

[0201] The base station may configure / instruct the terminal to perform event-based transmission / reporting through the same UL channel resources and resources configured to perform other UCI transmissions / reporting (e.g., transmissions / reporting not related to events).

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

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

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

[0205] That is, Embodiment 1 relates to a method for performing event-based reporting by reusing UL channel resources set for other UCI transmission / reporting. In the case of method 1-1, even if separate UL channel resources for event-based transmission / reporting are not set, a terminal can perform event-based transmission / reporting (based on UL channel resources set for other UCI transmission / reporting), thereby saving UL channel resources. In addition, in the case of method 1-2, other transmission / reporting information can be transmitted together with event-related information.

[0206] As an example of the present disclosure, when Method 1-1 is applied, in order to resolve ambiguity related to information decoding / interpretation of the base station, the terminal may transmit an indicator or flag indicating whether the reported information is preset information or event information (at each reporting time). For example, the terminal may transmit an indicator or flag indicating the type of the reported information (e.g., whether the reported information is event-related information or preset information) to the base station together with the information. Here, the preset information may include UCI (not related to an event), and the base station may configure UL resources for transmitting the UCI.

[0207] Additionally or alternatively, when multiple events (i.e., multiple types of events) apply, the terminal may include an indicator or flag indicating which event the currently reported information relates to.

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

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

[0210] In addition, similar to method 1-1, the terminal may transmit information about the type of information being reported and / or events associated with the reported information to the base station via separate indicators and / or flags. Accordingly, the base station may easily identify / 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 events may be included in UCI Part 2. The base station may determine the type of information included in UCI Part 2 (e.g., whether UCI Part 2 includes only preset information or both preset information and event-related information) by preferentially decoding the indicators and / or flags. Accordingly, the base station may easily determine the payload size of UCI Part 2.

[0211] As an example of the present disclosure, the base station can configure / instruct the 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 can be adaptively applied depending on the type / priority of information (e.g., event-related information or / and other reporting information) and / or the capacity of the UL channel (e.g., (maximum) payload size).

[0212] 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 preset information), method 1-1 may be applied, and if not, method 1-2 may be applied.

[0213] As another example, if the capacity of the UL channel (e.g., the capacity of the UL resources set by the base station) is sufficient to transmit event-related information and other reporting information, method 1-2 may be applied, otherwise method 1-1 may be set / defined to be applied.

[0214] Example 1-1

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

[0216] A base station may configure uplink resources (e.g., PUCCH and / or PUSCH resources) for a terminal for periodic (P) or semi-persistent (SP) CSI / beam reporting to the terminal. In addition, the base station may activate P / SP CSI / beam reporting operation 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 the CSI / beam information (Method 1-1), or transmit the event-related information and CSI / beam information together (Method 1-2).

[0217] Example 1-2

[0218] Embodiment 1-2 relates to a method for performing event-based CSI / beam reporting operation via configured grant (CG) uplink resources (e.g., PUSCH resources) (for TB transmission).

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

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

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

[0222] For example, considering various applications such as voice calls, the 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 with priority.

[0223] The method related to Embodiment 1 (e.g., Methods 1 and 2, etc.) can be applied not only to Embodiments 1-1 and 1-2 described above, but also to various operations. For example, the method related to Embodiment 1 can be applied to aperiodic CSI / beam reporting. In this case, the base station can configure event-based transmission / reporting as an "add-on feature" for the terminal.

[0224] Example 1-3

[0225] Embodiment 1-3 relates to a method for performing multiple event-based transmissions / reports through the same UL channel resource. That is, Embodiment 1-3 extends Embodiments 1, 1-1, 1-2, and 1-4 into a multiple event-based transmission / reporting technique.

[0226] For example, the base station can configure the 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 can report event information #1 to the base station via the UL channel. If only event #2 occurs at a specific reporting time, the terminal can report event information #2 to the base station via the UL channel. If both events #1 and #2 occur at a specific reporting time, the terminal can report either event information #1 or event information #2 to the base station via the UL channel (e.g., method 1-1), or all / part of event information #1 and all / part of event information #2 to the base station (e.g., method 1-2).

[0227] For the above-described operations, priorities may be defined / configured for each event or event information. For example, if multiple events occur simultaneously or within a predefined time period, the terminal may be defined / configured / instructed to preferentially transmit / report to the base station the event or event information with the highest priority.

[0228] Although the above-described examples describe two events (e.g., event #1 and event #2) or two pieces of event information (e.g., event information #1 and event information #2), the number of events and event information is not limited. That is, the above-described method (e.g., transmitting events / event information through the same UL channel resource) can be extended to three or more events / event information.

[0229] Example 1-4

[0230] Embodiment 1-4 relates to a method of using separate UL channel resources according to the configuration of reporting information. Embodiment 1-4 relates to a method of extending Embodiments 1, 1-1, 1-2, and 1-3.

[0231] The base station can separately configure UL channel resources (e.g., PUCCH resources and / or PUSCH resources) for each UE according to the configuration of the reported information. The UE can perform the information / report through the corresponding UL channel resources according to the configuration of the information to be transmitted / reported at that time (e.g., information regarding the occurrence of an event). For example, when Method 1-1 or Method 1-2 is applied, the UE can use different UL channel resource formats depending on whether event information is transmitted (taking into account the payload size and reliability appropriate for each information configuration).

[0232] Additionally or alternatively, when transmitting one of two pieces of information (e.g., event-related report information and other report information (e.g., non-event-related information)) or transmitting both pieces of information together, a rule may be defined / established as to which of the UL channel resources to use / apply depending on the configuration of each piece of information.

[0233] 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 the terminal. In this case, when an event occurs, either method 1-1 or method 1-2 can be applied, and whether the corresponding information is reported through UL channel resource #1 or UL channel resource #2 can be configured / defined as a rule.

[0234] For example, the base station can check the composition of information transmitted by the terminal (e.g., information on whether an event occurred, etc.) through blind detection of multiple UL channel resource candidates set in advance at each reporting time of the terminal.

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

[0236] Here, the methods according to the above-described embodiments 1, 1-1, 1-2, 1-3, and 1-4 can be utilized only when the reporting (possible) timings of each piece of information overlap. If the reporting (possible) timings of each piece of information do not overlap, the terminal can utilize the UL channel resources set for each piece of information / transmission.

[0237] For example, assume that an event reporting cycle / resource and another UCI (or UL) transmission cycle / 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 event-related information to the base station through the resources configured for event reporting. At an event reporting time that overlaps with another UCI (or UL) transmission time, the terminal can transmit event-related information to the base station through the resources configured for the other UCI transmission.

[0238] 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 set 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 set for event reporting.

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

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

[0241] Example 2

[0242] Embodiment 2 relates to a method related to event-based beam reporting via (dedicated) uplink resources (e.g., PUCCH resources or PUSCH resources, etc.).

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

[0244] 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 of more than 2 bits (e.g., PUCCH format 2 / 3 / 4) can be configured / used for terminals 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 above-described PUCCH formats. Here, methods such as UCI encoding / multiplexing / RE mapping applied to CSI can also be applied to PUCCH resources.

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

[0246] To solve the above-described problem, the (maximum) payload size of beam report information reported as event information can be limited, thereby reducing the PUCCH resource overhead associated with the report.

[0247] As an 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 the base station in addition to information related to whether an event has occurred. In this case, the beam indicators and / or beam quality value information may be restricted as described below.

[0248] For example, with respect to beam indicators, the number of beams reported may be limited or fixed. For example, only information about 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 beam group / set IDs may be reported to the base station instead of beam IDs.

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

[0250] As an example of coarsely configuring the beam quality value in Example 2, the payload size can be reduced by considering the L1-RSRP / SINR value with a step size of n dB or more (e.g., n is a value exceeding 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 above-described method can set the step size value to a large value.

[0251] Additionally, for the method of configuring the difference in quality values ​​of a target beam versus a specific beam, the specific beam may include i) the indicated TCI, ii) the CRI / SSBRI with the highest RSRP / SINR in the beam report set by the base station and / or terminal-initiated, iii) the CORESET TCI, iv) the first / highest RSRP / SINR among the reported RSRP / SINRs, etc. The case related to iv) may be applied when reporting RSRP / SINR for more than one beam.

[0252] Additionally or alternatively, if two or more TCI / CORESETpools are configured / instructed for a 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 above-described method is applied based on one of the two or more TCI / CORESETpools.

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

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

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

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

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

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

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

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

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

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

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

[0264] Additionally or alternatively, the configuration information may include configuration information related to each of one or more combinations of Embodiment 1, Embodiment 1-1, Embodiment 1-2, Embodiment 1-3, Embodiment 1-4, Embodiment 2, or / and their detailed embodiments. As an example, the configuration information may include information for setting one of Method 1-1 and Method 1-2 according to Embodiment 1. As another example, the configuration information may include information for setting a method for configuring report information according to Embodiment 2.

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

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

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

[0268] The terminal may report / transmit event-related information and / or "other information" to the base station based on configuration information and RS measurements (S120). For example, the terminal may report / transmit event-related information and / or "other information" to the base station according to a cycle set by the configuration information.

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

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

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

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

[0273] A first device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A step of receiving, by a terminal, first configuration information related to a first uplink resource for transmitting first information from a base station; and Based on the occurrence of a first event, the method comprises the step of 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, A method wherein the first uplink channel includes third information related to whether the second information is information related to the first event.

2. In paragraph 1, 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, A method wherein the first uplink channel includes the first information, based on the priority of the first information being higher than the priority of the second information.

3. In paragraph 1, 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, A method wherein, 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.

4. In paragraph 1, A method in which the transmission time of the first information and the transmission time of the second information overlap.

5. In paragraph 1, A method wherein the priority of the first event is higher than the priority of the second event, based on the first event and the second event occurring in the same time interval.

6. In paragraph 1, A method in which a second uplink channel including fourth information indicating that the second information is included on the first uplink channel is transmitted from the terminal to the base station.

7. In paragraph 1, A method in which second configuration information including at least one of a 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.

8. In paragraph 1, The above first information includes channel state information (CSI), A method wherein the first uplink resource comprises a periodic or semi-persistent uplink control channel resource or an uplink shared channel resource.

9. In paragraph 1, The first information includes at least one of a scheduling request (SR), a hybrid automatic repeat request-acknowledgement (HARQ-ACK), or a link recovery repeat (LRR). A method wherein the first uplink resource includes a configured grant uplink control channel resource or an uplink shared channel resource.

10. In paragraph 1, A method wherein the first event comprises an event related to whether a quality value of a serving beam is less than a first threshold or an event related to identification of at least one beam whose beam quality value exceeds a second threshold.

11. In paragraph 1, A method in which third configuration 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.

12. In paragraph 1, 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 includes at least one of the quality value of the serving beam and information about a cell related to the serving beam or information about a new beam for beam failure recovery, A method wherein the second information comprises at least one of an index of the at least one beam or a quality value of the at least one beam, based on the first event being an event related to the identification of the at least one beam having a beam quality value exceeding the second threshold.

13. One or more transceivers; and comprising one or more processors coupled to said one or more transceivers; One or more of the above processors: Receiving first configuration information related to a first uplink resource for transmitting first information from a base station through one or more transceivers; and Based on the occurrence of the first event, second information related to the first event is set to be transmitted to the base station through the one or more transceivers via the first uplink channel based on the first uplink resource, A terminal wherein the first uplink channel includes third information related to whether the second information is information related to the first event.

14. A step of transmitting first configuration information related to first uplink resource for transmitting first information to a terminal by a base station; and Based on the occurrence of a first event, the 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, A method wherein the first uplink channel includes third information related to whether the second information is information related to the first event.

15. In the base station, the base station: one or more transceivers; and comprising one or more processors coupled to said one or more transceivers; One or more of the above processors: Transmitting first configuration information related to a first uplink resource for transmitting first information to a terminal through one or more transceivers; and Based on the occurrence of the first event, second information related to the first event is set to be received from the terminal through the one or more transceivers through the first uplink channel based on the first uplink resource, A base station, wherein the first uplink channel includes third information related to whether the second information is information related to the first event.

16. In a processing device set to control a terminal, the processing device: one or more processors; and A processing device comprising one or more computer memories operatively connected to said one or more processors and storing instructions that, when executed by said one or more processors, perform a method according to any one of claims 1 to 11.

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

Images