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

Abstract

A method and a device for performing uplink transmission / reception in a wireless communication system are disclosed. The method according to one embodiment of the present disclosure comprises steps in which a terminal: receives configuration information related to an event from a base station; and, on the basis the configuration information, transmits, through an uplink channel, first uplink control information (UCI) including a payload related to the event to the base station, wherein, on the basis of whether the event has occurred, the payload includes at least one from among information related to the occurrence of the event, first report information, and second report information related to the event, and first UCI and second UCI can be multiplexed on the uplink channel.

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 challenge of the present disclosure is to provide a method and device for multiplexing uplink control information during an event-based transmission 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, configuration information related to an event from a base station; and transmitting, by the terminal, first uplink control information (UCI) including a payload related to the event to the base station through an uplink channel based on the configuration information, wherein, based on whether the event has occurred, the payload includes at least one of information related to whether the event has occurred, first report information, or second report information related to the event, and wherein the first UCI and the second UCI can be multiplexed on the uplink channel.

[0008] According to another embodiment of the present disclosure, a method comprises the steps of: transmitting, by a base station, configuration information related to an event to a terminal; and receiving, by the base station, from the terminal, first uplink control information (UCI) including a payload related to the event through an uplink channel based on the configuration information, wherein, based on whether the event has occurred, the payload includes at least one of information related to whether the event has occurred, first report information, or second report information related to the event, and wherein the first UCI and the second UCI can be multiplexed on the uplink channel.

[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 multiplexing uplink control information during an event-based transmission procedure.

[0011] Additionally, encoding, multiplexing, and dropping for event-based uplink transmissions with variable payloads can be efficiently performed by various embodiments of the present disclosure.

[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 slotare aligned temporally with the start of the OFDM symbol. Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in a downlink slot or uplink slot can be used. Table 3 shows the number of OFDM symbols per slot (N) in a general CP. 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.

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

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

[0085] 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} slots 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. Hereinafter, the physical resources that can be considered in an NR system will be described in detail. First, with respect to antenna ports, antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. Two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-location) relationship if the large-scale properties 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. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0086] 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 N RB 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').

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

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

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

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

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

[0092]

[0093] 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 to 1, where i is the number of the 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.

[0094]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0118] Basic beam failure recovery (BFR)

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

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

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

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

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

[0124] Beam failure detection (BFD)

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

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

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

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

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

[0130] 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."

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

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

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

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

[0135] Improved beam failure recovery

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

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

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

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

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

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

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

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

[0144] PUCCH configuration and format

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

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

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

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

[0149] Two-step uplink transmission scheme for event-based transmission

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

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

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

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

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

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

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

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

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

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

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

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

[0162] 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.”

[0163] For efficient UL resource management / allocation, multiplexing / dropping rules between event information and other UCIs must be defined. For example, in a wireless communication system, when overlap occurs between UL resources in the same symbol, multiplexing or dropping rules for various types of UCI and / or related channel resources may be applied depending on the type / format of the UL resources, the UCI / information transmitted through the resources, etc.

[0164] In basic wireless communication systems, when BFR is performed, information related to new beams reported via BFR MAC-CE among event information is not subject to UCI multiplexing / dropping rules because physical layer control information is not UCI. Therefore, in basic wireless communication systems, only event information with a small amount of information (e.g., less than 10 bits) such as SR / BFRQ and dropping / multiplexing operations with other UCIs were considered.

[0165] The present disclosure may apply new event information (or / and UCI) (e.g., event-based reporting information) having a larger amount of information (e.g., tens to hundreds of bits) and multiplexing / dropping rules between different UCIs. Here, the event-based reporting information may include, but is not limited to, at least one CRI / SSBRI and its L1-RSRP / SINR values.

[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] Additionally, in describing the present disclosure, the payload size associated with event information required when an event occurs may be larger than the payload size associated with event information required when no event occurs, but is not limited thereto. Furthermore, it may be difficult for a base station to predict at what point an event will occur for a specific terminal.

[0169] Below, we will explain the multiplexing / dropping method of event information (e.g., UCI) in an event-based transmission / reception procedure.

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

[0171] The terminal may receive configuration information related to an event (or / and configuration information related to uplink transmission) from the base station (S710). For example, the configuration information related to uplink transmission (or / and event) may correspond to the configuration information of FIG. 9.

[0172] For example, the configuration information may include event-related configuration information (or / and event-based report-related configuration information), report information configuration information (e.g., size of payload related to an event), UL channel resource for reporting (e.g., PUCCH / PUSCH) information, etc. Additionally or alternatively, the configuration information may include information related to an uplink channel (e.g., information related to an uplink control / shared channel, information about the (maximum) size of the payload of an uplink control channel transmitted via the uplink control / shared channel, etc.).

[0173] In describing the present disclosure, a payload may be expressed / replaced by a unit to which information can be mapped, such as an information bit, at least one field, etc.

[0174] Additionally or alternatively, the configuration information may include at least one candidate for information to be reported upon non-occurrence of an event (e.g., the type or candidate for the first report information) or at least one type of event. Each of the aforementioned configuration information may be transmitted to the terminal via separate upper layer signaling, but may also be transmitted to the terminal via a single upper layer signaling.

[0175] Each of the above-described configuration information may be transmitted as a separate message (e.g., RRC message (or signaling), SIB, MAC-CE, etc.), but is not limited thereto, and may be transmitted as a single message.

[0176] The terminal can transmit first uplink control information (UCI) including a payload related to an event to the base station through an uplink channel based on the configuration information (S720).

[0177] As an example of the present disclosure, a payload associated with an event may be included on the first UCI, regardless of whether the event occurred. The payload size may be predefined / set / indicated or determined based on the maximum amount of second report information associated with the event.

[0178] Here, the first UCI may be multiplexed with a second UCI (e.g., a UCI not related to an event) on an uplink channel (e.g., PUCCH, PUSCH, etc.), but is not limited thereto. Either the first UCI or the second UCI may be dropped depending on priority.

[0179] Here, the second UCI may collectively refer to UCI that does not include event-related information / payload, etc. For example, the second UCI (e.g., non-event-related UCI) may include at least one of non-event-related channel state information, hybrid automatic repeat request-acknowledgement (HARQ-ACK), and scheduling request (SR). That is, the terminal may multiplex the first event-related UCI and the second event-related UCI on the uplink channel.

[0180] As an example of the present disclosure, based on whether an event has occurred, the payload may include at least one of information related to whether the event has occurred (e.g., information indicating that the event has not occurred), first report information, or second report information related to the event.

[0181] For example, the type of the first report information may be set / indicated by the base station through configuration information or may be predefined. That is, the terminal may receive configuration information including the type of the first report information, or may receive separate instruction / control information including the type of the first report information. As another example, as described above, the configuration information may include at least one information candidate to be reported based on the non-occurrence of an event, and the terminal may select the first report information from among the candidates.

[0182] Additionally or alternatively, information regarding whether an event has occurred may include a predefined value indicating the non-occurrence of the event. For example, information regarding whether an event has occurred may include a predefined value indicating the non-occurrence of the event.

[0183] For example, assume that the event is related to whether the quality value of the serving beam is less than a first threshold. For example, if the quality value of the serving beam is less than the first threshold, the terminal may determine that the event has occurred. Even if the event does not occur (or, even if the event is issued), the payload of the first UCI may include first report information, and the first report information may include at least one of: i) information about a specific RS among at least one candidate RS configured by the base station, or ii) information about the serving beam.

[0184] And, information about a specific RS may include at least one of an index value of the specific RS and a reference signal received power (RSRP) or a signal to inference plus noise ratio (SINR) of the specific RS.

[0185] Additionally or alternatively, the event may include an event related to whether the terminal identifies at least one beam (or RS (e.g., CSI-RS, SSB, etc.)) having a beam quality value (e.g., RSRP, SINR, etc.) exceeding a second threshold. That is, if the terminal identifies / discovers at least one beam having a beam quality value exceeding the second threshold, the terminal may consider / interpret the event as having occurred.

[0186] For example, based on the fact that the event did not occur, the payload associated with the event of the first UCI may include at least one of information related to whether the event occurred or the first reporting information.

[0187] That is, even if an event does not occur (or even if an event does occur), the payload of the first UCI may include first report information, and the first report information may include at least one of an index of at least one beam or a beam quality value of at least one beam.

[0188] As described above, the type of the event (e.g., an event related to whether the quality value of the serving beam is less than a first threshold, or / and an event related to the identification of at least one beam whose beam quality value exceeds a second threshold, etc.) or / and the condition of the event (e.g., the magnitude of the first / second threshold, etc.) may be set by the configuration information, but may also be predefined.

[0189] As an example of the present disclosure, based on the occurrence of an event, the payload may include secondary reporting information related to the event and / or information related to whether the event occurred.

[0190] Additionally or alternatively, the priorities of the first UCI and the second UCI may be determined based on whether an event has occurred. Based on whether an event has occurred, the priority of the first UCI may be higher than that of the second UCI, and based on whether an event has not occurred, the priority of the second UCI may be higher than that of the first UCI. The terminal may multiplex or drop the first UCI and the second UCI on the uplink channel based on the priorities.

[0191] 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 configuration information related to uplink transmission from a base station through one or more transceivers (106). The one or more processors (102) can transmit a first UCI including a payload related to an event to the base station through one or more transceivers (106) over an uplink channel based on the configuration information.

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

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

[0194] The base station can transmit setting information related to the event (or / and setting information related to the event) to the terminal (S810).

[0195] An example of setting information has been described with reference to Fig. 7, so any redundant description will be omitted.

[0196] Based on the configuration information, the base station can receive a first UCI including a payload related to an event from the terminal through an uplink channel (S820).

[0197] For example, the base station can determine whether an event has occurred through the first UCI. Alternatively, even if an event has not occurred, the base station can decode other types of reporting information through the first UCI.

[0198] 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 configuration information related to uplink transmission to a terminal via one or more transceivers (206). Based on the configuration information, the one or more processors (202) can receive a first UCI including a payload related to an event from the terminal via one or more transceivers (206) via an uplink channel.

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

[0200] Below, various embodiments related to the multiplexing / dropping method of event information in an event-based transmission / reception procedure are described.

[0201] Example 1

[0202] Embodiment 1 relates to a UCI payload size and configuration method for event information when an event occurs. That is, Embodiment 1 relates to a method for allocating a UCI payload size for event information in preparation for the occurrence of an event and a method for performing a UCI multiplexing operation.

[0203] In one embodiment of the present disclosure, in order to multiplex event information (e.g., UCI including event information) and information different from event information (e.g., UCI not including event information), the terminal may perform multiplexing based on a maximum size and / or a fixed (or indicated) UCI ​​payload size in the event of an event occurrence. The UCI payload size may be determined by the maximum amount of information in the event information, a value set by the base station, or a predefined value (for the case of UCI multiplexing).

[0204] When a terminal event occurs, the UCI payload determined / allocated according to the above-described method can be utilized to its fullest extent. However, to avoid ambiguity regarding the overall UCI payload size when the base station decodes multiplexed UCI, specific information may need to be configured / mapped within the UCI payload even when no event occurs. Accordingly, if no event is issued, utilization of the UCI payload may be difficult.

[0205] Therefore, if no event occurs, the UCI payload may be configured according to at least one of the embodiments described below (e.g., embodiment 1-1, embodiment 1-2, embodiment 1-3).

[0206] Example 1-1

[0207] Example 1-1 relates to a method of transmitting information that an event has not occurred through the UCI payload.

[0208] Specifically, if an event does not occur, the UCI payload (e.g., the UCI payload corresponding to the event) may be configured with a maximum set or fixed (or set) value for the event occurrence, and a value set to all 0s to notify the network (e.g., the base station, etc.) that the event did not occur. The larger the size of the UCI payload corresponding to the event information, the larger the size of the UCI bits in the case where the event did not occur.

[0209] Example 1-2

[0210] Example 1-2 relates to a method for reporting preset / indicated reporting information via a UCI payload corresponding to event information even when no event occurs.

[0211] Specifically, if an event has not occurred, the UCI payload corresponding to the event information may include pre-configured / indicated report information (or part of the report information) (retrieved by the terminal in a best-effort manner). Additionally or alternatively, the UCI payload corresponding to the event information may include information indicating that the event has not occurred.

[0212] For example, for event-based beam reporting, it is assumed that an event in which "the quality of the serving beam falls below a certain level" is defined / configured / instructed. And, it is assumed that when the event occurs, the terminal is instructed / configured / defined to report information (e.g., beam index (e.g., CRI / SSBRI) and L1-RSRP of the beam) about a new beam (that can replace the serving beam or has better quality than the serving beam).

[0213] At this time, when the method according to Example 1-2 is applied, even if the quality of the serving beam does not fall below a certain level, information about a new beam may be included in the UCI payload corresponding to the event information. Here, the information about the new beam may include the CRI / SSBRI and the RSRP / SINR of those selected from the newly configured RS resource(s).

[0214] As another example of the present disclosure, assume that an event of "finding a new beam having a quality value higher than a certain value than a serving beam (e.g., a beam having a quality that is better than a certain level than a serving beam)" is defined / set / instructed. In this case, if the method according to embodiment 1-2 is applied, even if a new beam having a quality value higher than the certain value than the serving beam is not found, the terminal can transmit information about a new beam (that can replace the serving beam) to the base station (via a UCI payload corresponding to the event information).

[0215] When the method according to embodiment 1-2 is applied, "information on whether an event has occurred" may be configured as a separate field, and the field may be included in a UCI payload corresponding to the event information. For example, the UCI payload corresponding to the event information may include an indicator related to whether an event has occurred of 1 bit, new beam index(es) of N bits, and an L1-RSRP value of M bits. As another example, the payload corresponding to the event information includes new beam index(es) of N bits and an L1-RSRP value of M bits, and the indicator related to whether an event has occurred may be omitted. Since whether switching to a new beam and whether an event has occurred can be implementedly determined based on beam quality value information reported by the terminal (e.g., L1-RSRP), the indicator related to whether an event has occurred may be omitted.

[0216] Example 1-3

[0217] Embodiments 1-3 relate to a method for reporting "other information" to a base station instead of event information when an event has not occurred. Specifically, the UCI payload corresponding to the event information may include information indicating that the event has not occurred and / or an indicator related to the information reported by the terminal. Additionally, the UCI payload corresponding to the event information may include other information (or other report information) defined / regulated / configured / instructed to be transmitted when the event condition is not met.

[0218] Here, "other information" may include information set by the base station, information predefined according to the standard, and / or information selected and reported by the terminal. For example, in an event-based beam reporting procedure, if no event occurs, the terminal may be configured / instructed / defined to report information about the serving beam(s) to the base station instead of information about the new beam(s). Based on this serving beam information, the base station can identify variability in serving beam quality, etc.

[0219] As another example of the present disclosure, in an event-based beam report, if no event occurs, the terminal may be configured / instructed / defined to transmit other (regular) beam report information described above instead of information about new beam(s). The base station may determine the index of the beam with the highest quality and the change in quality based on the information reported by the terminal. To this end, the base station may transmit to the terminal not only the report configuration information when an event occurs, but also the report configuration information when no event occurs.

[0220] Additionally, multiple candidate report information items that can be transmitted in the event that no event occurs may be configured or predefined for the terminal. The terminal may select at least one of the configured / defined candidate report information items, and the selected information may be included in the UCI payload corresponding to the event information.

[0221] When the method according to embodiment 1-3 is applied, the terminal can select one of at least two reporting settings for cases where an event occurs and cases where an event does not occur, and perform a reporting operation based on the selected setting. Accordingly, the UCI payload corresponding to the event may include an indicator of the report / setting type instead of an indicator of whether an event has occurred. For example, the UCI payload corresponding to the event may include a report indicator of X bits, a beam index of N bits, and an L1-RSRP value of M bits. Additionally or alternatively, the UCI payload corresponding to the event may include information related to whether an event has occurred.

[0222] Example 2

[0223] Example 2 describes a method for applying the two-part encoding method used in CSI reporting to event-related information. Example 2 can be utilized when the amount of event information is large, thereby enabling efficient use of UL resources.

[0224] Specifically, event information may be included in a first part UCI having a fixed / set UCI payload size value, and the presence of information to be transmitted via the first part UCI (e.g., information on whether an event occurred) and / or a feature determining the payload size may be included in a second part UCI.

[0225] For example, the first part may contain information with a small fixed amount of information (e.g., information about whether an event occurred), and the second part may contain information with a variable amount of information (e.g., new beam information when an event occurs).

[0226] Each of the first part UCI and the second part UCI can be (separately) encoded / rate-matched / RE-matched.

[0227] Additionally, the first part UCI can be encoded / rate-mapped / RE-matched (joint) with other single-part UCIs (e.g., HARQ-ACK, SR, etc.) and other first part UCIs, and the second part UCI can be encoded / rate-mapped / RE-matched (joint) with other second part UCIs.

[0228] When two-part encoding is applied, the base station can determine the size of the second UCI by first decoding the first UCI. Therefore, while two-part encoding complicates the encoding / decoding process compared to single-part encoding, it allows for more efficient UCI payload configuration when the amount of reported information is variable.

[0229] Embodiment 2 relates to a method for performing UCI multiplexing according to two-part encoding, based on the feature that the payload size required for reporting when an event occurs is larger than the payload size required for reporting when an event does not occur.

[0230] When UCI multiplexing is applied / performed, the first part UCI can be encoded / rate-mapped / RE-matched only with a single part UCI and other first part UCIs, and thus the first part UCI can have a fixed size. The second part UCI can be encoded / rate-mapped / RE-matched only with other second part UCIs, and thus the second part UCI can have a variable size.

[0231] As an example of the present disclosure, a method may be applied in which no information is transmitted via the second part UCI when an event does not occur. That is, the presence or absence of the second part UCI may be conveyed / transmitted / determined by the first part UCI. In this case, a second part UCI with a 0 bit and another second part UCI may be multiplexed. For example, single-part encoding (when no event occurs) and two-part encoding (when an event occurs) may be selectively applied depending on the condition, and this method may be referred to as a "conditional two-part encoding method."

[0232] Example 3

[0233] Embodiment 3 relates to a method for setting / defining different UCI payload sizes and / or UL channel resources for cases where an event occurs and cases where an event does not occur, respectively. That is, since different UCI configurations / payload sizes and / or related UL channel resources are set / defined depending on whether an event occurs, UL resources can be used efficiently.

[0234] Specifically, the terminal may select and transmit UCI and / or UL channel resources depending on whether an event has occurred. If overlap occurs between different UCI and / or related UL channel resources, multiplexing / dropping rules may be applied to the selected UCI and / or UL channel resources. Additionally or alternatively, the base station may assume the UCI payload size and / or UL channel resources for the event occurrence and the event non-occurrence cases, respectively (since it does not know whether the event has occurred at the terminal), and perform UCI decoding / detection / demultiplexing.

[0235] UCI multiplexing / dropping rules can also be applied in response to UCI / UL channel resources set / defined depending on whether an event occurs.

[0236] As a special case of Example 3, if an event does not occur, the UCI payload size (corresponding to the event information) may be set / defined as 0 and / or the UL channel resources (related to event information reporting) may be set / defined as “none.” That is, if an event does not occur, the terminal may not transmit the UCI and / or UL channel resources corresponding to the event information. From a UCI multiplexing perspective, the UCI field corresponding to the event information may be omitted, and the base station may determine whether an event has occurred based on the presence or absence of the corresponding UCI and / or UL channel resources.

[0237] Example 4

[0238] Example 4 relates to a method for setting priorities between event information (and / or UL channels associated with transmitting the event information) and other UCIs (and / or the UL channels).

[0239] UCI dropping rules can be defined for event information. For example, in a basic wireless communication system, priorities are defined in the order of HARQ-ACK, SR, and CSI. In certain cases / conditions, lower priority UCI(s) can be dropped, and only higher priority UCI(s) can be transmitted.

[0240] Additionally, with respect to CSI, priorities may be defined in the following order: aperiodic CSI on PUSCH, SP CSI on PUSCH, SP CSI on PUCCH, and periodic CSI on PUCCH, depending on the UL resource type. From a CSI parameter / information perspective, priorities may also be defined, such as L1-RSRP / SINR being given priority over CSI that does not include L1-RSRP / SINR.

[0241] Additionally, in order to transmit UCIs related to urgent services / information, such as URLLC services, a priority index may be applied to UCIs, and priorities among UCIs may be handled accordingly.

[0242] Priorities associated with event information (e.g., UCI priority with event information) can also be defined. Since the base station cannot determine whether a UCI associated with event information will be transmitted, ambiguity may arise regarding which UCI to drop when it overlaps with another UCI.

[0243] More specifically, when an event occurs, it may be desirable for the UCI associated with the event to be reported with priority over other UCIs. However, when an event does not occur, the UCI associated with the event may prevent other, more important UCIs from being reported. In this case, the other UCIs may be reported to the base station with priority over the UCI associated with the event.

[0244] The priorities of event information (and / or the corresponding UL channel associated therewith) and other UCI (and / or the corresponding UL channel associated therewith) may be defined according to at least one of the embodiments described below (e.g., embodiments 4-1, 4-2, 4-3, and 4-4).

[0245] Example 4-1

[0246] In one embodiment of the present disclosure, whether to transmit / drop may be determined based on a priority set for UCI (e.g., UCI corresponding to event information).

[0247] If a UCI corresponding to event information (according to priority) needs to be transmitted but no event has occurred, a UCI payload may be constructed based on Embodiments 1, 2, and 3. For example, if the UCI needs to be transmitted according to a dropping rule, UCI construction and / or encoding for UCI multiplexing according to Embodiments 1, 2, and 3 may be applied.

[0248] That is, when only UCI corresponding to event information must be transmitted by the UCI dropping rule, event information can be transmitted without ambiguity regarding the UCI payload size by applying the corresponding UCI configuration and / or encoding methods.

[0249] Example 4-2

[0250] In one embodiment of the present disclosure, UCI corresponding to / related to event information may have a lower priority than existing UCI (e.g., HARQ-ACK, SR, CSI, etc.). By lowering the priority of event information compared to existing UCI, the probability of an issue occurring where other important UCI is not reported due to UCI reporting related to an event when no event has occurred can be reduced.

[0251] As another example, event information may have a lower priority than at least HARQ-ACK and SR. That is, event information (or event-related report information) may have a lower priority than HARQ-ACK and SR, but a higher priority than CSI.

[0252] Example 4-3

[0253] In one embodiment of the present disclosure, when Embodiment 2 is applied, the priorities of the first part UCI and the second part UCI may be different. That is, when the conditional two-part UCI encoding method according to Embodiment 2 is applied, different priorities may be set / defined / applied for each part.

[0254] In particular, the first part UCI or single part UCI may be defined / configured to have a higher priority, while the second part UCI may have a lower priority. For example, the priorities may be set / defined in the following order: first part UCI, CSI, and second part UCI.

[0255] According to the dropping rules described above, the first part UCI can be transmitted to the base station with priority, allowing the base station to at least confirm whether an event has occurred. Furthermore, because the first part UCI carries a small amount of information, it can be multiplexed with other high- and low-priority UCIs. In other words, the first part UCI can be transmitted to the base station along with other UCIs.

[0256] For example, HARQ-ACK, SR, and first part UCI can be multiplexed on PUCCH resources with a limited maximum number of UCI bits, and CSI and second part UCI can be dropped.

[0257] Example 4-4

[0258] In one embodiment of the present disclosure, different priorities can be set / applied for cases where an event occurs and cases where an event does not occur. That is, the present disclosure relates to a method for setting / defining different priorities for UCI (e.g., UCI corresponding to event information) and / or UL channel resources associated with the UCI, depending on whether an event occurs.

[0259] As an example of the present disclosure, the base station can perform UCI detection / decoding for each case where an event has occurred and each case where an event has not occurred in order to determine whether an event has occurred at the terminal.

[0260] For example, assume that there is a UCI #1 and another UCI #B related to event information. In this case, if an event occurs, UCI #A with a higher priority can be transmitted to the base station, and if no event is generated, UCI #B with a higher priority can be transmitted to the base station. The base station can blindly detect whether the terminal transmitted UCI #A or UCI #B. For example, the base station can perform blind detection based on different UCI formats, payload sizes, etc. between UCI #A and UCI #B.

[0261] When Embodiment 4-4 and Embodiment 3 are applied together, different UCI payload sizes and / or UL channel resources may be set depending on whether an event occurs, and the UCI payload sizes and / or UL channel resources may be set, and each UL / UCI channel resource may have different priorities.

[0262] Two or more of Embodiments 4-1, 4-2, 4-3, and 4-4 may be applied together. For example, in a case where the priority of UCI related to event information is lowered according to Embodiment 4-2 (e.g., lower than the priority of other UCIs), but UCI related to event information must be transmitted due to reasons such as high priority of UL resources transmitting UCI related to event information, Embodiment 4-1 and / or Embodiment 4-3 may be applied.

[0263] Embodiment 4 can be applied to priority handling between UCIs and between channels carrying UCIs (e.g., PUCCH, PUSCH, etc.). Priority can be applied not only to information configuration (e.g., dropping low-priority information) but also to transmission power application. For example, in a carrier aggregation situation, transmission power for channels carrying event-related information and / or other UCIs can be differentially applied / allocated according to priority. That is, transmission power can be preferentially allocated to channels containing high-priority information.

[0264] The above-described embodiments of the present disclosure can be applied not only to multiplexing / dropping methods between event information and non-event information, but also to multiplexing / dropping methods between event-based reports. In addition, the above-described embodiments of the present disclosure can also be applied when transmitting multiple CSI beams / reports together with one PUSCH or PUCCH. For example, assume that the base station configures the terminal to report multiple CSI / beam reports including one or more event-based CSI / beam report(s) through the same UL channel resource (e.g., multi-CSI reporting on PUCCH / PUSCH). In this case, the method of transmitting (e.g., encoding, rate matching, RE mapping, etc.) multiple CSI / beam information according to Embodiments 1, 2, 3, and 4 (or / and detailed embodiments of Embodiments 1, 2, 3, and 4) together or separately can be applied.

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

[0266] 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 2, Embodiment 3, Embodiment 4, Embodiment 4-1, Embodiment 4-2, Embodiment 4-3, Embodiment 4-4 or / and detailed embodiments thereof) may be applied.

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

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

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

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

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

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

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

[0274] 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, etc. The UL channel resources for reporting may include information for configuring UL channel resources for reporting event-related information, etc. The terminal may monitor whether an event has occurred based on the configuration information.

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

[0276] When an event occurs (S110), the terminal can transmit event information to the network via UL resources according to the configuration information (S115). The event information and / or non-event information transmitted by the terminal can be multiplexed or dropped based on the methods described in Embodiments 1, 2, 3, 4, and their related detailed embodiments.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0292] 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 setting information related to an event from a base station by a terminal; and Based on the above setting information, the method comprises a step of transmitting, by the terminal, first uplink control information (UCI) including a payload related to an event to the base station through an uplink channel, Based on whether the above event has occurred, the payload includes at least one of information related to whether the event has occurred, first report information, or second report information related to the event, A method wherein the first UCI and the second UCI are multiplexed on the uplink channel.

2. In paragraph 1, Information related to the type of the above first report information is transmitted from the base station to the terminal, A method wherein the payload includes information related to whether the event has occurred and the first report information, based on the above event not occurring.

3. In paragraph 1, A method wherein the payload size is predefined or based on a maximum amount of second reporting information associated with the event.

4. In paragraph 3, A method wherein, based on the occurrence of said event, said payload includes at least one of information related to whether said event occurred or second reporting information related to said event.

5. In paragraph 1, The above event includes an event related to whether the quality value of the serving beam is less than a first threshold, A method according to claim 1, wherein the first report information includes at least one of i) information about a specific RS among at least one candidate RS set by the base station or ii) information about the serving beam.

6. In paragraph 5, A method, wherein the information about the specific RS includes at least one of an index value of the specific RS and a reference signal received power (RSRP) or a signal to inference plus noise ratio (SINR) of the specific RS.

7. In paragraph 1, A method wherein information related to whether the above event has occurred includes a predefined value related to non-occurrence of the above event.

8. In paragraph 1, A method wherein the above configuration information includes at least one information candidate to be reported according to non-occurrence of the event or at least one of the types of the event.

9. In paragraph 1, A method wherein the first report information among the at least one information candidate is selected by the terminal.

10. In paragraph 1, A method in which the priority of each of the first UCI or the second UCI is determined depending on whether the above event occurs.

11. In paragraph 10, Based on the occurrence of the above event, the priority of the first UCI is higher than the priority of the second UCI, A method wherein the priority of the second UCI is higher than the priority of the first UCI based on the above event not occurring.

12. In paragraph 1, The above event comprises an event related to the identification of at least one beam whose beam quality value exceeds a second threshold, A method wherein the first report information comprises at least one of an index of the at least one beam or a beam quality value of the at least one beam.

13. In paragraph 1, A method wherein the second UCI includes at least one of channel state information not related to the event, hybrid automatic repeat request-acknowledgement (HARQ-ACK), and a scheduling request (SR).

14. One or more transceivers; and comprising one or more processors coupled to said one or more transceivers; One or more of the above processors: Receiving setup information related to an event from a base station via one or more of the transceivers; and Based on the above setting information, the first uplink control information (UCI) including a payload related to an event is set to be transmitted to the base station through the one or more transceivers via an uplink channel, Based on whether the above event has occurred, the payload includes at least one of information related to whether the event has occurred, first report information, or second report information related to the event, A terminal wherein the first UCI and the second UCI are multiplexed on the uplink channel.

15. A step of transmitting setting information related to an event to a terminal by a base station; and Based on the above setting information, the method comprises the step of receiving, by the base station, first uplink control information (UCI) including a payload related to an event from the terminal through an uplink channel, Based on whether the above event has occurred, the payload includes at least one of information related to whether the event has occurred, first report information, or second report information related to the event, A method wherein the first UCI and the second UCI are multiplexed on the uplink channel.

16. 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 event-related configuration information to the terminal via one or more of the above transceivers; and Based on the above setting information, the first uplink control information (UCI) including a payload related to an event is set to be received from the terminal through the one or more transceivers via an uplink channel, Based on whether the above event has occurred, the payload includes at least one of information related to whether the event has occurred, first report information, or second report information related to the event, A base station, wherein the first UCI and the second UCI are multiplexed on the uplink channel.

17. 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 10.

18. 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 10.

Images