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

Abstract

A method and apparatus for performing uplink transmission / reception in a wireless communication system are disclosed. The method according to an embodiment of the disclosure can include the steps of receiving, by a terminal, first configuration information related to an event from a base station; encoding, by the terminal, information related to the event on a first uplink channel according to second configuration information related to a scheduling request (SR) based on occurrence of the event; and transmitting, by the terminal, the first or second uplink channel to the base station based on a priority of the information related to the event based on the first uplink channel overlapping with a second uplink channel including the SR or a link recovery request (LRR). The priority of the information related to the event can be higher than or equal to a priority of the SR, and can be lower than or equal to a priority of the LRR.

Description

Technical Field

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

[0002] A mobile communication system has been developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded to include data and voice services, and the current explosive growth in these services has led to resource shortages. Users are demanding faster services and therefore require more advanced mobile communication systems.

[0003] The overall requirements for next-generation mobile communication systems should be able to support the capacity for explosive data traffic, significantly increased per-user transmission rates, a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To this end, various technologies such as dual connectivity, massive MIMO, in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and device networking have been investigated. Summary of the Invention

[0004] Technical issues

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

[0006] Furthermore, an additional technical objective of this disclosure is to provide a method and apparatus for performing event-based sending and receiving processes.

[0007] The technical objectives to be achieved by this disclosure are not limited to those described above, and other technical objectives not described herein will be clearly understood by those skilled in the art through the following description.

[0008] Technical solution

[0009] A method according to one embodiment of the present disclosure may include: receiving first configuration information related to an event from a base station by a user equipment (UE); encoding information related to the event on a first uplink channel by the UE according to second configuration information related to a scheduling request (SR) based on the occurrence of the event; and, based on the overlap between the first uplink channel and a second uplink channel including the SR or a link recovery request (LRR), transmitting the first uplink channel or the second uplink channel to the base station according to the priority of the information related to the event, wherein the priority of the information related to the event may be higher than or equal to the priority of the SR and lower than or equal to the priority of the LRR.

[0010] A method according to one embodiment of this disclosure may include: a base station sending first configuration information related to an event to a user equipment (UE); based on the occurrence of the event, the base station receiving from the UE i) a first uplink channel including information related to the event or ii) a second uplink channel including a scheduling request (SR) or a link recovery request (LRR), wherein the first uplink channel and the second uplink channel may overlap in the same time resource, the information related to the event may be encoded on the first uplink channel based on the second configuration information related to the SR, and the priority of the information related to the event may be higher than or equal to the priority of the SR and lower than or equal to the priority of the LRR.

[0011] Technical effect

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

[0013] Furthermore, through various embodiments of this disclosure, a method and apparatus for performing event-based sending and receiving processes can be provided.

[0014] Furthermore, through various embodiments of this disclosure, the overhead associated with uplink resources used for beam / CSI reporting can be reduced during the event-based transmission process.

[0015] The effects achievable by this disclosure are not limited to those described above, and those skilled in the art can clearly understand other effects not described herein through the following description. Attached Figure Description

[0016] The accompanying drawings, which are included as part of the detailed description for understanding this disclosure, provide embodiments of the disclosure and describe the technical features of the disclosure through detailed description.

[0017] Figure 1 The structure of a wireless communication system to which this disclosure can be applied is illustrated.

[0018] Figure 2 A frame structure in a wireless communication system to which this disclosure can be applied is illustrated.

[0019] Figure 3 An example is shown of a resource grid in a wireless communication system to which this disclosure can be applied.

[0020] Figure 4 Examples of physical resource blocks in wireless communication systems to which this disclosure can be applied are provided.

[0021] Figure 5The time slot structure in a wireless communication system to which this disclosure can be applied is illustrated.

[0022] Figure 6 Examples are given of physical channels used in wireless communication systems to which this disclosure may be applied, as well as general signal transmission and reception methods using such physical channels.

[0023] Figure 7 This is a flowchart illustrating a method for a UE to perform a communication process according to an embodiment of the present disclosure.

[0024] Figure 8 This is a flowchart illustrating a method for a base station to perform a communication process according to an embodiment of the present disclosure.

[0025] Figure 9 This is a diagram illustrating signaling processing according to an embodiment of the present disclosure.

[0026] Figure 10 This is a diagram illustrating the block configuration of a wireless communication device according to an embodiment of the present disclosure. Detailed Implementation

[0027] In the following, embodiments according to this disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed with reference to the drawings is intended to describe exemplary embodiments of this disclosure and not to represent the only embodiments in which this disclosure can be implemented. The following detailed description includes specific details to provide a complete understanding of this disclosure. However, those skilled in the art will recognize that this disclosure can be implemented without these specific details.

[0028] In some cases, known structures and devices may be omitted, or they may be shown in block diagram form based on the core functions of each structure and device in order to prevent ambiguity of the concepts in this disclosure.

[0029] In this disclosure, when an element is referred to as “connected,” “combined,” or “linked” to another element, it can include both indirect and direct connections between the two elements. Furthermore, in this disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, operations, components, and / or elements, but do not exclude the presence or addition of one or more other features, stages, operations, components, elements, and / or groups thereof.

[0030] In this disclosure, terms such as "first" and "second" are used only to distinguish one element from another and are not used to limit the elements. Unless otherwise stated, they do not limit the order or importance of the elements. Therefore, within the scope of this disclosure, a first element in one embodiment may be referred to as a second element in another embodiment, and similarly, a second element in one embodiment may be referred to as a first element in another embodiment.

[0031] The terminology used in this disclosure is for the purpose of describing particular embodiments and not for limiting the claims. As used in the description of embodiments and the appended claims, the singular form is intended to include the plural form unless the context clearly indicates otherwise. The term “and / or” as used in this disclosure may refer to one of the associated enumerations, or is intended to refer to and include any and all possible combinations of two or more of them. Furthermore, unless otherwise stated, the “ / ” between words in this invention has the same meaning as “and / or”.

[0032] This disclosure describes a wireless communication network or wireless communication system, and operations performed in the wireless communication network can be performed during the process of controlling the network and transmitting or receiving signals by a device (e.g., a base station) that controls the corresponding wireless communication network, or during the process of transmitting or receiving signals between a terminal associated with the corresponding wireless network and the network or between the terminal.

[0033] In this disclosure, the term "transmit or receive channel" includes the meaning of transmitting or receiving information or signals through a corresponding channel. For example, transmitting a control channel means transmitting control information or control signals through a control channel. Similarly, transmitting a data channel means transmitting data information or data signals through a data channel.

[0034] In the following text, downlink (DL) refers to communication from a base station to a terminal, while uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter can be part of the base station, and the receiver can be part of the terminal. In the uplink, the transmitter can be part of the terminal, and the receiver can be part of the base station. A base station can be referred to as a first communication device, and a terminal can be referred to as a second communication device. A base station (BS) can be replaced by terms such as fixed station, Node B, eNB (evolved Node B), gNB (next-generation Node B), BTS (Base Transceiver System), Access Point (AP), Network (5G network), AI (Artificial Intelligence) system / module, RSU (Roadside Unit), robot, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, terminals can be fixed or mobile, and can be replaced by 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) equipment, M2M (Machine-to-Machine) equipment, D2D (Device-to-Device) equipment, vehicle, RSU (Roadside Unit), robot, AI (Artificial Intelligence) module, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) equipment, VR (Virtual Reality) equipment, etc.

[0035] The following descriptions can be applied to various radio access systems, such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented using technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented using radio technologies such as GSM (Global System for Mobile Communications) / GPRS (General Packet Radio Service) / EDGE (GSM Evolution with Enhanced Data Rates). OFDMA can be implemented using radio 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 part of E-UMTS (Evolved UMTS) using E-UTRA, and LTE-A (Advanced) / LTE-A pro are advanced versions of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE / LTE-A / LTE-A pro.

[0036] To make the description clearer, it is based on 3GPP communication systems (e.g., LTE-A, NR), but the technical ideas of this disclosure are not limited thereto. LTE refers to technology from 3GPP TS (Technical Specification) version 8 onwards. Specifically, LTE technology in or after 3GPP TS 36.xxx is referred to as LTE-A, and LTE technology in or after 3GPP TS 36.xxx version 13 is referred to as LTE-A pro. 3GPP NR refers to technology in or after TS 38.xxx. LTE / NR can be referred to as a 3GPP system. "xxx" refers to the detailed number of the standard document. LTE / NR is generally referred to as a 3GPP system. For background information, terminology, abbreviations, etc., used to describe this disclosure, reference can be made to the matters described in the standard documents previously published. For example, the following documents can be consulted.

[0037] For 3GPP LTE, you can refer to TS 36.211 (Physical Channels and Modulation), TS 36.212 (Multiplexing and Channel Coding), TS 36.213 (Physical Layer Procedures), TS 36.300 (General Description), and TS 36.331 (Radio Resource Control).

[0038] For 3GPP NR, you can refer to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Coding), TS 38.213 (Physical Layer Procedures for Control), TS 38.214 (Physical Layer Procedures for Data), TS38.300 (General Description of NR and NG-RAN (Next Generation Radio Access Networks)), and TS 38.331 (Radio Resource Control Protocol Specification).

[0039] The abbreviations of terms that may be used in this disclosure are defined as follows.

[0040] - BM: Beam Management

[0041] - CQI: Channel Quality Indicator

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

[0043] - CSI: Channel State Information

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

[0045] - CSI-RS: Channel State Information - Reference Signal

[0046] - DMRS: Demodulation Reference Signal

[0047] - FDM: Frequency Division Multiplexing

[0048] - FFT: Fast Fourier Transform

[0049] - IFDMA: Interleaved Frequency Division Multiple Access

[0050] - IFFT: Inverse Fast Fourier Transform

[0051] - L1-RSRP: Layer 1 Reference Signal Received Power

[0052] - L1-RSRQ: Layer 1 reference signal reception quality

[0053] - MAC: Media Access Control

[0054] - NZP: Non-zero power

[0055] - OFDM: Orthogonal Frequency Division Multiplexing

[0056] - PDCCH: Physical Downlink Control Channel

[0057] - PDSCH: Physical Downlink Shared Channel

[0058] - PMI: Precoding Matrix Indicator

[0059] - RE: Resource Elements

[0060] - RI: Rank Indicator

[0061] - RRC: Radio Resource Control

[0062] - RSSI: Received Signal Strength Indicator

[0063] - Rx: Receive

[0064] - QCL: Quasi-co-location

[0065] - SINR: Signal-to-Interference-Noise Ratio

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

[0067] - TDM: Time Division Multiplexing

[0068] - TRP: Transmitting and Receiving Point

[0069] - TRS: Tracking Reference Signal

[0070] - Tx: Send

[0071] - UE: User Equipment

[0072] - ZP: Zero Power

[0073] Overall System

[0074] With more communication devices requiring higher capacity, there has been a demand for improved mobile broadband communications compared to existing radio access technologies (RATs). Furthermore, massive MTC (machine-type communication) that provides various services anytime, anywhere by connecting multiple devices and things is also one of the main issues to be considered in next-generation communications. In addition, communication system designs considering services / terminals sensitive to reliability and latency are discussed. Therefore, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), mMTC (massive MTC), URLLC (ultra-reliable low-latency communication), etc., is discussed, and for convenience, the corresponding technologies are referred to as NR in this disclosure. NR is an example expression representing 5G RAT.

[0075] New RAT systems, including NR, use OFDM or similar transmission methods. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow existing LTE / LTE-A parameters as is, but may support a wider system bandwidth (e.g., 100MHz). Alternatively, a single cell may support multiple parameter sets. In other words, terminals operating according to different parameter sets can coexist in a single cell.

[0076] The parameter set corresponds to a subcarrier spacing in the frequency domain. Different parameter sets can be defined as the reference subcarrier spacing is scaled by an integer N.

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

[0078] Referring to Figure 1, the NG-RAN is configured with gNBs providing control plane (RRC) protocol endpoints for the NG-RA (NG Radio Access) user plane (i.e., the new AS (Access Layer) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and UE. The gNBs interconnect via the Xn interface. Furthermore, the gNBs are connected to the NGC (Next Generation Core) via the NG interface. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Power) via the N2 interface and to the UPF (User Plane Functions) via the N3 interface.

[0079] Figure 2 illustrates a frame structure in a wireless communication system to which this disclosure can be applied.

[0080] NR systems can support multiple parameter sets. These parameter sets can be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings can be derived by scaling the basic (reference) subcarrier spacing by an integer N (or μ). Furthermore, while it is assumed that very low subcarrier spacings are not used at very high carrier frequencies, the parameter set used can be selected independently of the frequency band. Moreover, various frame structures based on multiple parameter sets can be supported in NR systems.

[0081] The OFDM parameter sets and frame structures that can be considered in NR systems are described below. Several OFDM parameter sets supported in NR systems can be defined as shown in Table 1 below.

[0082] [Table 1]

[0083] NR supports multiple parameter sets (or subcarrier spacing (SCS)) to support various 5G services. For example, a 15kHz SCS supports wide-area coverage of traditional cellular bands; a 30kHz / 60kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidth; and a 60kHz or higher SCS supports bandwidths exceeding 24.25GHz to overcome phase noise. NR bands are defined as frequency ranges of two types (FR1, FR2). FR1 and FR2 can be configured as shown in Table 2 below. Additionally, FR2 can refer to millimeter wave (mmW).

[0084] [Table 2]

[0085] Regarding the frame structure in the NR system, the size of various fields in the time domain is expressed as T. c =1 / (Δf max ·N f A multiple of the time unit. Here, Δf max It is 480 × 10³ Hz, and N f The value is 4096. Downlink and uplink transmissions are configured (organized) to have a duration T. f =1 / Δf max N f / 100)·T c A radio frame of 10ms. Here, the radio frame is configured with 10 subframes, each with a duration of T. sf =(Δf max N f / 1000)·T c =1ms duration. In this case, there may be one frame set for the uplink and one frame set for the downlink. Furthermore, the transmission in the i-th uplink frame from the terminal should begin T earlier than the corresponding downlink frame in the corresponding terminal. TA =(N TA +N TA,offset )T c Begin. For the subcarrier spacing configuration μ, the time slots are arranged in n-order within the subframe. s μ ∈{0,...,N slot subframe,μ The numbers are numbered in ascending order from -1, and in the radio frames, they are numbered in n... s , f μ ∈{0,..., N slot frame,μThe time slot is configured with N in ascending order of -1. symb slot N consecutive OFDM symbols, and N symb slot Determined based on CP. Slot n in the subframe s μ The start of the OFDM symbol n in the same subframe s μ N symb slot The start dates are arranged in time. Not all terminals may perform transmission and reception simultaneously, meaning that all OFDM symbols in either the downlink or uplink time slots may not be available.

[0086] Table 3 shows the number of OFDM symbols (N) in each time slot during normal CP. symb slot ), Number of time slots per radio frame (N) slot frame,μ ) and the number of time slots per subframe (N) slot subframe,μ Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0087] [Table 3]

[0088] [Table 4]

[0089] Figure 2 shows an example with μ=2 (SCS = 60kHz). Referring to Table 3, one subframe can include four time slots. The example shown in Figure 2, where one subframe = {1, 2, 4}, illustrates this. The number of time slots that can be included in one subframe is defined in Table 3 or Table 4. Additionally, micro-time slots can include 2, 4, or 7 symbols, or more or fewer symbols. Regarding physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier portions, etc., can be considered.

[0090] The physical resources that can be considered in an NR system will be described in detail below. First, regarding antenna ports, an antenna port is defined such that the channel carrying a symbol in the antenna port can be inferred from the channels carrying other symbols in the same antenna port. Two antenna ports can be said to be in a QC / QCL (quasi-co-located or quasi-co-located) relationship when the large-scale properties of the channel carrying a symbol in one antenna port can be inferred from the channels carrying symbols in another antenna port. In this case, large-scale properties include at least one of delay spread, Doppler spread, frequency shift, average received power, and receive timing.

[0091] Figure 3 The illustration depicts a resource grid in a wireless communication system to which this disclosure can be applied. Referring to Figure 3, the resource grid is illustrated with N in the frequency domain. RB μ N sc RB There are 14.2 subcarriers, and one subframe is configured with 14.2 μ The number of OFDM symbols is not limited to this. In an NR system, the transmitted signal consists of 2 OFDM symbols. μ N symb （μ） One OFDM symbol and configuration with N RB μ N sc RB It is described by one or more resource grids of N subcarriers. Here, N RB μ ≤ N RB max,μ N RB max,μ This represents the maximum transmission bandwidth, which may differ between uplink and downlink, and between parameter sets. In this case, each μ and antenna port p can be configured with a resource grid. Each element of the resource grid used for μ and antenna port p is called a resource element and is uniquely identified by an index pair (k, l').

[0092] 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 symbol position within the subframe. When referencing resource elements in a time slot, index pairs (k, l) are used. Here, l = 0,...,N symb μ-1. The resource element (k,l') used for μ and antenna port p corresponds to the complex value a. k,l' （p,μ） When there is no risk of confusion or when a specific antenna port or parameter set is not specified, the indices p and μ may be discarded, and the complex value may be ak,l'(p) or ak,l'. Furthermore, a resource block (RB) is defined as N in the frequency domain. sc RB =12 consecutive subcarriers.

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

[0094] - The offsetToPointA of the downlink in the primary cell (PCell) represents the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block used by the terminal for initial cell selection. It is assumed that a 15kHz subcarrier spacing is used for FR1 and a 60kHz subcarrier spacing is used for FR2, expressed in units of resource blocks.

[0095] -absoluteFrequencyPointA indicates the frequency location of point A, expressed in ARFCN (Absolute Radio Frequency Channel Number).

[0096] For subcarrier spacing configuration μ, common resource blocks are numbered from 0 upwards in the frequency domain. The center of subcarrier 0 of common resource block 0 used for subcarrier spacing configuration μ is the same as "point A". The common resource block number n of subcarrier spacing configuration μ in the frequency domain is... CRB μ The relationship between the resource element (k,l) and the resource element (k,l) is given by Equation 1 below.

[0097] [Equation 1]

[0098] In Equation 1, k is defined relative to point A such that k = 0 corresponds to a subcarrier centered at point A. The physical resource block (BWP) ranges from 0 to N. BWP,i size,μ -1 is the number, and i is the number of the BWP. The physical resource block n in BWP i. PRB and public resource block n CRB The relationship between them is given by the following equation 2.

[0099] [Equation 2]

[0100] N BWP,i start,μ It is a public resource block that starts relative to public resource block 0 in BWP.

[0101] Figure 4 illustrates physical resource blocks in a wireless communication system to which the present disclosure can be applied. Furthermore, Figure 5 The time slot structure in a wireless communication system to which this disclosure can be applied is illustrated.

[0102] Referring to Figures 4 and 5, a time slot includes multiple symbols in the time domain. For example, for a normal CP, one time slot includes 7 symbols, but for an extended CP, one time slot includes 6 symbols.

[0103] 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 Component) is defined as multiple consecutive (physical) resource blocks in the frequency domain and can correspond to a set of parameters (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through active BWPs, and only one BWP can be active for a single terminal. In the resource grid, each element is called a resource element (RE) and can be mapped to a complex number of symbols.

[0104] In NR systems, each component carrier (CC) can support up to 400MHz. If a terminal operating in such a wideband CC always operates with the radio frequency (FR) chip turned on for the entire CC, terminal battery consumption may increase. Alternatively, when considering multiple application scenarios operating in a wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different sets of parameters (e.g., subcarrier spacing, etc.) can be supported in each band of the corresponding CC. Alternatively, each terminal may have different capabilities for the maximum bandwidth. With this in mind, the base station can instruct the terminal to operate only in a portion of the bandwidth, rather than in the full bandwidth of the wideband CC, and for convenience, the corresponding portion of the bandwidth is defined as the bandwidth portion (BWP). The BWP can be configured with consecutive RBs on the frequency axis and can correspond to a set of parameters (e.g., subcarrier spacing, CP length, slot / microslot duration).

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

[0106] Alternatively, when a UE is congested in a specific BWP, other BWPs can be configured for some terminals to achieve load balancing. Alternatively, considering factors such as frequency domain inter-cell interference cancellation between neighboring cells, some full-bandwidth intermediate spectrum can be excluded, and two edge BWPs can be configured in the same time slot. In other words, the base station can configure at least one DL / UL BWP for a terminal associated with a broadband CC.

[0107] The base station can activate at least one of the configured DL / UL BWPs at a specific time (via L1 signaling, MAC CE (control element), or RRC signaling, etc.). Furthermore, the base station can instruct a handover to another configured DL / UL BWP (via L1 signaling, MAC CE, or RRC signaling, etc.). Alternatively, based on a timer, a handover to a specific DL / UL BWP can be initiated when the timer value expires. Here, the activated DL / UL BWP is defined as the active DL / UL BWP. However, the terminal may not receive the configuration on the DL / UL BWP before performing the initial access procedure or establishing an RRC connection; therefore, the DL / UL BWP assumed by the terminal in these cases is defined as the initially active DL / UL BWP.

[0108] Figure 6 illustrates a physical channel used in a wireless communication system to which this disclosure can be applied, and a general method for transmitting and receiving signals using that physical channel.

[0109] In wireless communication systems, terminals receive information from base stations via downlink and transmit information to base stations via uplink. The information sent and received by base stations and terminals includes data and various control information, and various physical channels exist depending on the type / purpose of the information they send and receive.

[0110] When a terminal is powered on or enters a new cell, it performs an initial cell search (S601), including synchronization with the base station. For the initial cell search, the terminal synchronizes with the base station by receiving the primary synchronization signal (PSS) and secondary synchronization signal (SSS) from the base station, and obtains information such as the cell identifier (ID). Then, the terminal obtains broadcast information within the cell by receiving the physical broadcast channel (PBCH) from the base station. Simultaneously, the terminal checks the downlink channel state by receiving the downlink reference signal (DL RS) during the initial cell search phase.

[0111] Terminals that have completed the initial cell search can obtain more detailed system information by receiving the Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH) based on the information carried in the PDCCH (S602).

[0112] Simultaneously, when a terminal first accesses a base station or when there are no radio resources available for signal transmission, it can perform a random access (RACH) procedure (S603 to S606) with the base station. For the random access procedure, the terminal can send a specific sequence as a preamble via the Physical Random Access Channel (PRACH) (S603 and S605), and can receive response messages to the preamble via the PDCCH and the corresponding PDSCH (S604 and S606). Contention-based RACH can further execute a contention resolution procedure.

[0113] The terminal that subsequently performs the above process can execute PDCCH / PDSCH reception (S607) and PUSCH (Physical Uplink Shared Channel) / PUCCH (Physical Uplink Control Channel) transmission (S608) as a general uplink / downlink signal transmission process. Specifically, the terminal receives downlink control information (DCI) via PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format varies depending on its intended use.

[0114] Meanwhile, control information sent by the terminal to the base station via the uplink or received by the terminal from the base station includes downlink / uplink ACK / NACK (acknowledgment / non-acknowledgment) signals, CQI (Channel Command Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. For 3GPP LTE systems, the terminal can send the aforementioned control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

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

[0116] [Table 5]

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

[0118] DCI format 0_0 is used for scheduling PUSCH within a cell. The information included in DCI format 0_0 is scrambled with a CRC (Cyclic Redundancy Check) using C-RNTI (Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and transmitted. DCI format 0_1 ​​is used to indicate the scheduling of one or more PUSCHs or to provide downlink feedback information to the Terminal Configuration Grant (CG) within a cell. The information included in DCI format 0_1 ​​is scrambled with C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSIRNTI), or MCS-C-RNTI and transmitted. DCI format 0_2 is used for scheduling PUSCH within a cell. The information included in DCI format 0_2 is scrambled with C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI and transmitted.

[0119] Next, DCI formats 1_0, 1_1, and 1_2 can include resource information (e.g., frequency resource allocation, time resource allocation, VRB (Virtual Resource Block) - PRB (Physical Resource Block) mapping, etc.), information related to transport blocks (TB) (e.g., MCS, NDI, RV, etc.), information related to HARQ (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., antenna port, TCI (Transmission Configuration Indicator), SRS (Sound Reference Signal) request, etc.), PUCCH-related information regarding PDSCH scheduling (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format can be predefined.

[0120] DCI format 1_0 is used to schedule PDSCH in a DL cell. The information included in DCI format 1_0 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0121] DCI format 1_1 is used to schedule PDSCH in a cell. The information included in DCI format 1_1 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0122] DCI format 1_2 is used to schedule PDSCH in a cell. The information contained in DCI format 1_2 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0123] Basic Beam Fault Recovery (BFR)

[0124] The UE and / or base station may perform uplink / downlink beam management (BM) for data transmission / reception. Here, BM may refer to the process of acquiring and maintaining a set of beams available for downlink and uplink transmission / reception.

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

[0126] While performing the aforementioned uplink / downlink beamforming (BM) processing, beam mismatch issues may occur due to various factors. For example, the optimal uplink / downlink beam pair may change when the UE moves or rotates, or when the radio channel environment changes due to the movement of nearby objects (e.g., when it is a line-of-sight (LoS) environment and then becomes a non-LoS environment when the beam is blocked). In this case, a beam failure can be considered to have occurred when the UE or base station fails to track the changed optimal uplink / downlink beam pair (i.e., BM tracking).

[0127] The UE can determine whether a beam fault has occurred based on the received quality of the downlink reference signal (RS). Additionally, the UE must report a beam fault report message or a beam recovery request message (BFRQ message) to the base station. Upon receiving this message, the base station can perform beam recovery processing through various steps, such as beam RS transmission or beam report requests for beam recovery. This series of beam recovery processes is called beam fault recovery (BFR) processing.

[0128] Basic BFR operations include BFR processing for special cells (SpCell) (i.e., primary cells, PCell) or primary-secondary cells (PScell) where contention-based PRACH resources exist. BFR processing may include UE beam fault detection (BFD) processing, BFRQ transmission processing, and monitoring of the base station's response to BFRQs, and each processing can be performed in the serving cell.

[0129] Beam Fault Detection (BFD)

[0130] A beam failure instance can be considered to have occurred when the quality value (Q_out) of all PDCCH beams is lower than a predefined value. Here, the quality value can be determined based on the Hypothetical Block Error Rate (BLER). That is, the theoretical BLER can refer to the probability that demodulation of control information will fail when control information is transmitted on a particular PDCCH.

[0131] Additionally, one or more search spaces can be configured in the UE for monitoring the PDCCH, and the PDCCH beams can be configured differently for each search space. In this case, when the quality values ​​of all PDCCH beams are lower than a predefined value, it means that the quality values ​​of all PDCCH beams are lower than the BLER threshold.

[0132] Two methods (described later) can be supported as the means for the UE to receive BFD-RS indication / configuration from the base station to determine whether a beam failure instance has occurred.

[0133] As a first approach, implicit configuration of BFD-RS can be supported. In each search space, a Control Resource Set (CORESET) ID is configured as the resource area where PDCCH can be transmitted, and RS information via QCL (e.g., CSI-RS Resource ID, SSB ID) can be indicated / configured for each CORESET ID in terms of spatial RX parameters. Given the spatial reception parameters, RS via QCL can be indicated or configured by transmitting Configuration Information (TCI). That is, BFD-RS can be implicitly configured / indicated to the UE based on the QCL information indicated or configured via TCI.

[0134] Here, when the base station indicates or configures the RS (i.e., QCLType D RS) to the UE from the perspective of spatial reception parameters, the UE can use the beam used to receive the RS that is QCL from the perspective of spatial reception parameters when it receives a specific PDCCH DMRS. That is, signals can be transmitted between antenna ports via the spatial QCL using the same or similar transmit beams (e.g., when the beamwidths are different but the beam directions are the same / similar).

[0135] As a second approach, an explicit configuration method for BFD-RS can be supported. The base station can explicitly configure or instruct the UE to use the beam RS for BFD. In this case, the beam RS can correspond to "all PDCCH beams".

[0136] Whenever an event occurs in which the theoretical BLER degradation based on configured (or indicated) BFD-RS measurements exceeds a certain threshold, the UE physical layer can notify the MAC sublayer that a beam failure instance (BFI) has occurred. Furthermore, when the BFI occurs a specific number of times within a specific time period (e.g., 'BFD timer'), the UE MAC sublayer can determine that a beam failure has occurred and initiate the relevant RACH operation.

[0137] BFRQ (based on PRACH): New Beam Identification and PRACH Transmission

[0138] As described above, when a certain number of BFIs are generated, the UE can determine that a beam fault has occurred and can perform a beam fault recovery operation. As an example of a beam fault recovery operation, the UE can perform RACH-based (i.e., PRACH) BFRQ processing. The corresponding BFRQ processing will be described in detail below.

[0139] When a beam failure occurs, the base station can configure a candidate beam RS list ('candidateBeamRSList') for the terminal via RRC signaling. The base station can also configure dedicated PRACH resources for the candidate beam RSs. In this case, the dedicated PRACH resources can be contention-free PRACH resources (or contention-free PRACH resources). When no alternative beam RS is found in the candidate beam RS list, the UE can select at least one of the preset SSB resources. The UE can then send a contention-based PRACH to the base station based on the selected resource.

[0140] Enhanced beam fault recovery

[0141] When carrier aggregation (CA) is applied, a particular SCell may not have an uplink carrier (UL carrier). That is, uplink transmission is impossible in an SCell with only a downlink carrier. Furthermore, even if an SCell has an uplink carrier, contention-based PRACH cannot be configured. Therefore, PRACH-based BFR processing using CA may be limited to SpCells (PCCell or PSCell), and the SCell may not support BFR processing. In other words, PRACH-based BFR operations in SpCells may not be supported in the SCell based on basic BFR operations.

[0142] Specifically, when a high-frequency band requiring BFR is configured in an SCell, PRACH-based BFR processing may not be supported in the corresponding high-frequency band. For example, when the PCell operates in a low-frequency band (e.g., 6 GHz or lower) while the SCell operates in a high-frequency band (e.g., 30 GHz), there is a problem that PRACH-based BFR processing is not supported in the high-frequency band that requires more BFR support.

[0143] To address the aforementioned issues, the improved BFR operation includes BFR operation for SCells. For example, the UE can perform BFRQ for an SCell by using a dedicated PUCCH resource configured in the SpCell for BFRQ. In the following text, for ease of description, the "dedicated PUCCH resource" will be referred to as BFR-PUCCH.

[0144] The function of BFR-PUCCH is to report only "BF occurrence information of SCell" to the base station. Furthermore, detailed information related to the generated BF can be sent to the base station as a subsequent report via BFR MAC-CE or UCI.

[0145] Here, the detailed information sent as a follow-up report may include information about the SCell where a BF has occurred, whether there are new candidate beams for the SCell where a BF has occurred, and (if there are new candidate beams) the corresponding beam RS ID.

[0146] Additionally, the BFR-PUCCH can use the same PUCCH format as the SR (Schedule Request) and can be defined by a specific SR ID for BFR use. If a UL-SCH allocated from the base station exists when the UE detects a BF in the SCell, the UE can omit the BFR-PUCCH transmission process as in the SR transmission process and send the BFR MAC-CE to the base station via the directly allocated UL-SCH.

[0147] In a multi-TRP environment, TRP-specific BFR operations based on multiple DCIs and / or a single DCI can be applied. First, the base station can explicitly or implicitly configure BFD RSs for the UE. For example, the base station can configure two or more BFD-RS sets for the UE via RRC and / or MAC-CE. As another example, BFD-RS sets can be configured based on the TCI state of each CORESET pool. The UE can then determine whether a beam is faulty for each TRP based on these BFD-RS sets.

[0148] When a beam fault is detected, SR PUCCH resources can be configured for the UE based on the base station's BFRQ resources. Individual SR PUCCH resources can be configured for each TRP, or two TRPs can use the same SR PUCCH resource. When a beam fault occurs in a specific TRP, the UE can send the configured BFRQ SR PUCCH (to the TRP where the beam fault did not occur). The TRP receiving the BFRQ can send a UL-authorized DCI to the UE, and the UE can send a BFR MAC-CE via a PUCCH scheduled / assigned by the UL-authorized DCI. The BFR MAC-CE can include a list of CCs where a beam fault occurred, information about the faulty BFR RS set, information about whether a new beam has occurred, etc.

[0149] PUCCH Configuration and Format

[0150] 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 acknowledgment signal for DL ​​signals. HARQ-ACK responses can include ACK, NACK (negative acknowledgment), DTX (discontinuous transmission), and NACK / DTX. HARQ-ACK can be used interchangeably with A / N, ACK / NACK, and HARQ-ACK / NACK. HARQ-ACK can be generated in units of TB or CBG.

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

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

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

[0154] Scheduling Request (SR)

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

[0156] For logical channel or SCell beam fault recovery and persistent LBT (Listen-After-Talk) fault recovery, the PUCCH resources for SR can be configured up to 1 per BWP. For logical channels providing radio bearers configured for SDT (Small Data Transmission), the PUCCH resources for SR may not be configured for SDT. For beam fault recovery of the serving cell's BFD-RS set, the PUCCH resources for SR can be configured up to 2 per BWP. A dedicated SR configuration can be configured to locate measurement gap activation / deactivation requests.

[0157] Each SR configuration can correspond to one or more logical channels and / or SCell beam fault recovery and / or persistent LBT fault recovery and / or BFD-RS set beam fault recovery and / or position measurement gap activation / deactivation requests. Each logical channel, SCell beam fault recovery, BFD-RS set beam fault recovery, and persistent LBT fault recovery can be mapped to zero or one SR configuration set in the RRC. The SR configuration of the logical channel that triggers the BSR or DSR, or SCell beam fault recovery, or BFD-RS set beam fault recovery, or persistent LBT fault recovery (if such a configuration exists), or position measurement gap activation / deactivation request can be considered as the SR configuration corresponding to the triggered SR. All SR configurations can be used for SRs triggered by preemptive BSR or timed advance reporting.

[0158] Event-based / trigger-based send and receive process

[0159] In describing this disclosure, " / " means "and", "or", or "and / or", depending on the context. Additionally, "beam" in this disclosure can refer to a source RS used for "spatial filtering" or "spatial relation" and can be interpreted as a QCL (Type-D) RS, a (DL / UL / joint) TCI state, or (in the case of uplink) a spatial relation RS.

[0160] In wireless communication systems, uplink control information based on Layer 1 (e.g., the physical layer) has the advantage of lower transmission latency compared to control information based on higher layers. For example, in order for a UE to send information to a base station via MAC-CE or RRC messages, it may require the UE's SR procedure and the base station's PUSCH allocation procedure (based on SR), and there are associated delays and overheads. Furthermore, generally, the higher the layer of information, the longer the time required to decode the information (e.g., decoding time and / or processing time).

[0161] On the other hand, in order to send Layer 1 based uplink control information, UL physical channel resources (e.g., PUCCH, PUSCH) must be (pre)configured / allocated to the terminal. Therefore, from the perspective of the base station / network, as the number of UEs increases, the amount of UL resources allocated to each UE may increase, and the total UL resource overhead may increase accordingly.

[0162] Therefore, in a wireless communication system, information that needs to be transmitted relatively urgently for physical layer operations (e.g., SR (e.g., SR for PUSCH allocation), HARQ-ACK (e.g., HARQ-ACK for retransmission), CSI (e.g., CSI for scheduling / MCS / precoder determination), and beam information (e.g., beam information for (analog) beam determination) can be transmitted and received via the physical layer UCI.

[0163] Here, the base station and / or network can determine / control the reporting timing of HARQ-ACK, CSI, beam information, etc., excluding SR. When applying this network-initiated / triggered reporting procedure, there is a limitation that in environments where wireless channel conditions may change rapidly, the reporting timing must be configured / indicated so that the terminal can frequently send UCI.

[0164] That is, in environments where wireless channel conditions change rapidly, the overhead of UL resources used for UCI reporting and the associated RS overhead for DL ​​measurements may increase, and there may be issues with increased power consumption of the terminal due to frequent UL transmissions. Additionally or alternatively, the more terminals present within the cell / TRP coverage area, the greater the UL resource overhead, because UL resources must be allocated to each UE.

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

[0166] When applying UE-initiated / triggered reporting methods or event-based / triggered reporting methods, the UE can decide whether or when to report (e.g., UCI). That is, the UE can perform relevant (UCI) reports only when necessary (e.g., only when a specific event occurs). Therefore, UL resource overhead and UE power consumption can be reduced. Furthermore, since the UE reports information based on Layer 1 / lower layers, reporting can be performed more quickly.

[0167] Therefore, the standardization of UE-initiated / triggered beam reporting methods can be implemented in next-generation wireless communication systems.

[0168] Furthermore, in order to effectively operate UL resources in next-generation wireless communication systems, UE-initiated / triggered or event-based transmission methods can be applied to control information, TB (transmission block), and user plane data transmission processes via UCI and / or MAC-CE.

[0169] Examples of event-based or UE-initiated / triggered transmit and receive procedures in wireless communication systems include SR and BFR reporting methods. The SR reporting method includes reporting whether a PUSCH allocation is required for UL-SCH transmission.

[0170] For example, the BFR reporting method includes reporting whether a BF has occurred and information related to the new beam. Here, information regarding whether a BF has occurred and information related to the new beam can be sent to the base station explicitly or implicitly (e.g., by sending the new beam index as PRACH resource selection information). Alternatively, information regarding whether a BF has occurred and information related to the new beam can be sent in one or more steps via one or two UL resources. For example, the UE can send a BFRQ to the base station via PUCCH and send beam information to the base station via MAC-CE on the PUCCH.

[0171] In describing this disclosure, information (e.g., SR, BFRQ, new beam information, etc.) sent by the UE to the network via event-based and / or UE-initiated / triggered transmission methods will be collectively referred to as “event information”.

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

[0173] This disclosure is primarily described in relation to event-based or UE-initiated / triggered beam reporting, but is not limited thereto. The methods according to this disclosure can also be applied to other event-based or UE-initiated / triggered transmission and reception procedures (e.g., UCI / CSI / MAC-CE reporting procedures, uplink transmission and reception procedures, etc.).

[0174] In describing this disclosure, "beam" may be interpreted / replaced as the source RS, or QCL (Type D) RS, TCI state, or (in the case of uplink) spatial relation RS used for "spatial filtering" or "spatial relation". Additionally, "service beam" may include the beam associated with the PDCCH / PDSCH.

[0175] The following describes how to support UE-initiated / triggered transmission methods (e.g., reporting methods) or event-based / triggered transmission methods (e.g., reporting methods) and improve reliability.

[0176] Figure 7 This is a flowchart illustrating a method for a UE to perform a communication process as an embodiment of this disclosure.

[0177] The UE can receive first configuration information related to the event from the base station (S710).

[0178] For example, the first configuration information related to the event may include at least one of the following: the type of the event, the criteria related to the event, the type of information to be reported when the event occurs (e.g., event-related information), and resources for the uplink channel used to report the event-related information (e.g., (CG)PUSCH, PUCCH, etc.). That is, the event-related configuration information may include criteria and / or thresholds and / or the type of event used to determine whether an event has occurred. The UE can monitor whether an event has occurred based on the first configuration information. Here, the first uplink channel may include (configuration grant (CG))PUSCH and / or PUCCH, etc.

[0179] Based on the occurrence of the event, the UE can encode event-related information onto the first uplink channel based on the second configuration information related to the scheduling request (SR) (S720).

[0180] The type of information associated with an event can vary depending on the type of event that occurs, and can be configured or predefined by the first configuration information. For example, if the event is associated with beam reporting, the information associated with the event may include beam reporting information (e.g., information about new / serving beams, etc.), information about whether beam reporting information is included on uplink channels transmitted after the first uplink channel, etc. Here, the information associated with the event may be included in uplink control information (UCI).

[0181] For example, if information regarding whether beam reporting information is included on an uplink channel (e.g., a third uplink channel) transmitted after the first uplink channel is included on the first uplink channel, then the UE can transmit a third uplink channel including the beam reporting information to the base station. Furthermore, the encoding method associated with the beam reporting information can be an encoding / multiplexing / mapping method applied to the SR, as described below, but is not limited thereto.

[0182] As an example of this disclosure, the UE may encode / map event-related information on a first uplink channel based on second configuration information associated with a scheduling request (SR). Here, the second configuration information associated with the SR may include, but is not limited to, at least one of the SR's period, offset, priority, resources, encoding method, or ID (identifier).

[0183] Alternatively, event-related information may be encoded / mapped / multiplexed on the first uplink channel according to a predefined encoding / mapping / multiplexing method for SR.

[0184] That is, event-related information can be mapped, multiplexed, and encoded on the first uplink channel based on the RE mapping / multiplexing / coding method applied to SR.

[0185] Since the first uplink channel overlaps with a second uplink channel including SR or LRR (on the same time / frequency resources), the UE can transmit the first uplink channel or the second uplink channel to the base station based on the priority of event-related information (S730). In one example of this disclosure, the priority of the event-related information can be higher than or equal to the priority of SR, and lower than or equal to the priority of Link Recovery Request (LRR) (or BFRQ). Therefore, when the first uplink channel including event-related information overlaps with the second uplink channel including SR and / or LRR, the UE can determine the uplink channel to be transmitted preferentially based on the priority of each piece of information.

[0186] For example, given the overlap between the first uplink channel and a second uplink channel including SR (Signal Transfer Rate), the UE can prioritize sending the first uplink channel to the base station based on the priority of event-related information. That is, the second uplink channel (or SR) can be discarded. Similarly, given the overlap between the first uplink channel and a second uplink channel including LRR (Low-Rate Transfer Rate), the terminal can prioritize sending the second uplink channel to the base station based on the priority of event-related information. That is, the first uplink channel (or event-related information) can be discarded.

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

[0188] However, this is merely one implementation method, and information regarding the transmission cycle and / or number of transmissions of event-related information can be sent to the UE through separate configuration information. The UE can repeatedly send event-related information to the base station based on the transmission cycle and number of transmissions.

[0189] Additionally or alternatively, based on the transmission of the first uplink channel to the base station, a timer (e.g., an event-related timer) related to the retransmission of event-related information can be operated. The duration of the event-related timer can be configured, but is not limited to, by timer-related configuration information sent from the base station, and can be predefined.

[0190] If no response message regarding event-related information is received from the base station before the timer expires, the UE can retransmit the event-related information to the base station. If a response message regarding event-related information is received from the base station before the timer expires, the timer can be paused / stopped, and the terminal's retransmission of event-related information can be paused / stopped (or prepared / awaited for retransmission). Here, the response message may include an ACK (acknowledgment) message for the first uplink channel, etc.

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

[0192] Alternatively, the UE may receive downlink control information related to the first uplink channel from the base station. Here, the UE may send an ACK message for the downlink control information to the base station.

[0193] Figure 7 The method described in the example can be derived from Figure 10 The first device (100) performs the operation. For example, Figure 10One or more processors (102) of the first device (100) can receive first configuration information related to an event from the base station via one or more transceivers (106). Based on the occurrence of the event, one or more processors (102) can encode the event-related information onto a first uplink channel based on second configuration information related to the SR. Based on the overlap between the first uplink channel and a second uplink channel including SR or LRR, one or more processors (102) can transmit the first uplink channel or the second uplink channel to the base station via one or more transceivers (106) based on the priority of the event-related information.

[0194] Furthermore, one or more memories (104) of the first device (100) may store information for execution by one or more processors (102) when performing tasks in... Figure 7 The instructions for the methods described in the examples or examples described below.

[0195] Figure 8 This is a flowchart illustrating a method for a base station to perform a communication process as an embodiment of this disclosure.

[0196] The base station can receive first configuration information related to the event from the UE (S810). Specifically, the base station can send the first configuration information related to the event and / or configuration information related to the first uplink channel to the UE. (This is based on previous information.) Figure 7 An example of configuration information has been described, so redundant descriptions will be omitted.

[0197] Based on the occurrence of an event, the base station can receive from the UE either i) a first uplink channel including event-related information or ii) a second uplink channel including a scheduling request (SR) or a link recovery request (LRR) (S820) based on the event-related priority. Here, the event-related information can be encoded on the first uplink channel based on second configuration information related to the SR or according to a predefined method related to the SR. Furthermore, the first uplink channel and the second uplink channel can overlap at the same time resource.

[0198] For example, based on the overlap between a first uplink channel and a second uplink channel including an SR, the base station can receive the first uplink channel from the UE based on the priority of event-related information. In another example, based on the overlap between a first uplink channel and a second uplink channel including an LRR, the base station can receive the second uplink channel from the UE based on the priority of event-related information.

[0199] Figure 8 The method described in the example can be derived from Figure 10 The second device (200) performs the operation. For example, Figure 10 One or more processors (202) of the second device (200) can send first configuration information related to the event to the UE through one or more transceivers (206). Based on the occurrence of the event, one or more processors (202) can receive a first uplink channel including event-related information or a second uplink channel including SR or LRR from the UE through one or more transceivers (106) based on the event-related priority.

[0200] Furthermore, one or more memories (204) of the second device (200) may store information for execution by one or more processors (202) when performing the operation. Figure 8 The instructions for the methods described in the examples or examples described below.

[0201] The following text will describe in more detail the UE-initiated / triggered transmit / receive methods (e.g., reporting methods, etc.) or event-based / triggered transmit / receive methods.

[0202] Event-based beam reporting methods can include a UCI-based beam reporting method (Method 1), a MAC-CE-based beam reporting method (Method 2), and a PRACH-based beam reporting method (Method 3).

[0203] UCI-based beam reporting method

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

[0205] Alternatively, the UE may send a MAC-CE to the base station via the assigned PUSCH, and the MAC-CE may include information for reporting the occurrence of an event and / or information related to beam reporting (method 1-1a). That is, similar to the enhanced beam fault recovery operation described above, information for reporting the occurrence of an event and / or information related to beam reporting may be sent to the base station.

[0206] Additionally or alternatively, conventional UCI may include information for reporting the occurrence of an event and / or information related to beam reporting (method 1-1b). In this case, the SR sent by the UE may be triggered by requesting beam reporting from the AP, rather than by UL-SCH assignment.

[0207] As an example of this disclosure, UCI-based beam reporting operations can be performed via a dedicated / configured CSI PUCCH (methods 1-2). Methods 1-2 are extensions of the SR PUCCH method to an event-based beam reporting method. Some CSIPUCCH resources can be configured for event-based reporting, such as P / SP CSI reporting for PUCCH, but the UE can decide whether to send CSI at every transmission opportunity.

[0208] As an example of this disclosure, UCI-based beam reporting operations (methods 1-3) can be performed via a configured PUSCH.

[0209] As an example of this disclosure, when a CG PUSCH resource based on CG PUSCH type 1 is set via RRC signaling, or when a CG PUSCH resource based on CG PUSCH type 2 is set / indicated via RRC signaling and DCI, the UE may send a CSI (along with UL-SCH) to the base station when an event occurs in the CGPUSCH resource (methods 1-3a).

[0210] As another example of this disclosure, when an event occurs, the UE can send a CSI to the base station via SP CSI PUSCH resources configured / indicated by RRC signaling and DCI (method 1-3b).

[0211] Beam Reporting Method Based on MAC-CE

[0212] A normal SR can be used to request a PUSCH assignment. Furthermore, operations according to method 1-1a described above can be performed. For example, the MAC-CE can include information for reporting the occurrence of an event and / or information related to beam reporting.

[0213] PRACH-based beam reporting method

[0214] As an example of this disclosure, a PRACH-based beam reporting method can be used to report the occurrence of an event (method 3-1). In this case, the PRACH transmission procedure can include a contention-based PRACH transmission procedure or a contention-free PRACH transmission procedure. Specifically, when performing a contention-free PRACH transmission procedure, a connection between a new beam and PRACH resources / timing can be established, for example, during a BFR procedure. Thus, information about the new beam and the occurrence of the event can be sent to the UE via PRACH (selected by the terminal).

[0215] Alternatively, beam information may be transmitted to the base station via MAC-CE or UCI, as in methods 1-1a and 1-1b.

[0216] As another example of this disclosure, a beam reporting method can be performed based on a PUSCH after a PRACH (e.g., similar to the transmission procedure of Msg. A for a contention-based 2-step RACH) (Method 3-2). For example, when an event occurs, the UE can select a PRACH preamble and send the selected PRACH preamble to the base station. The UE can then perform beam reporting via a PUSCH connected to the PRACH preamble. For example, the PRACH preamble may include information related to whether an event has occurred, and the PUSCH may include CSI / UCI information, etc.

[0217] When applying methods 3-1 and 3-2, the base station can send an ACK to the UE regarding information related to the occurrence of an event via a response to PRACH (e.g., RAR MAC-CE). Additionally or alternatively, the base station can instruct / change the UE's beam based on new beam information sent via PRACH.

[0218] Implementation Method 1

[0219] A method can be applied to enable event-based transmission or associated UL channel resources via DCI. Furthermore, this method can be applied to the methods described above.

[0220] For example, as in methods 1-3b, the SP CSI reporting method via PUSCH can be utilized / applied to event-based reporting methods. For instance, when the PUSCH resource for SP CSI is activated, the UE can perform event-based reporting through the activated PUSCH resource.

[0221] As another example, the CG PUSCH (Type 2) method, as described in methods 1-3a, can be used for event-based UCI / MAC-CE reporting. While the CG PUSCH method is used for TB transmissions in basic wireless communication systems, the method described above can be used for beam / CSI reporting. Beam / CSI reporting information can be transmitted to the base station via UCI / MAC-CE.

[0222] As described above, assume that an event-based transmission or its associated UL channel resource is activated via DCI. In this case, a problem #1 may arise, where the base station may incorrectly determine that the resource is activated even if the UE fails to detect / decode the DCI.

[0223] Implementation 1 relates to a method for solving problem #1. In one embodiment of this disclosure, when an event-based transmission / report or associated channel resource is activated by DCI, the UE can perform CSI / beam reporting after receiving DCI, regardless of whether an event occurred during the first transmission / report, or send an ACK for DCI to the base station.

[0224] For example, suppose we configure CG PUSCH type 1 / 2 via RRC signaling as in method 1-3a, and activate (specific) CG PUSCH resources via DCI. The terminal receives DCI (regardless of whether an event occurs), and on the first transmission / report, performs a CSI / beam reporting procedure based on the (specific) CG PUSCH resources activated by DCI, or sends an ACK for DCI to the base station.

[0225] As another example, suppose the PUSCH resources for SP CSI transmission are configured via RRC signaling as in method 1-3b, and the PUSCH resources are indicated / activated via DCI. The terminal receives the DCI (regardless of whether an event occurs), and on the first transmission / report, performs a CSI / beam reporting procedure based on the PUSCH resources activated / indicated by the DCI, or sends an ACK for the DCI to the base station.

[0226] Implementation Method 2

[0227] The UE can perform event-based transmission / reporting operations, but the base station may not detect / decode the terminal's event reports. That is, problem #2 may occur, where the terminal performs event-based transmission / reporting operations, but the base station may not detect the terminal's operations. For example, when methods 1-2, 1-3, and 3-2 are applied, problem #2 related to the transmission of (some) event information may occur.

[0228] The detailed implementation of Implementation 2 relates to a method for solving problem #2. When the UE transmits event-based beaming information, it can perform operations according to at least one of Implementation 2-1, Implementation 2-2, Implementation 2-3, and Implementation 2-4. For example, operations according to at least one of Implementation 2-1, Implementation 2-2, Implementation 2-3, and Implementation 2-4 can be applied / used simultaneously.

[0229] Implementation Method 2-1

[0230] In one embodiment of this disclosure (Embodiment 2-1), the UE can repeatedly send event-related information or reports to the base station based on the base station's configuration (e.g., configuration information sent from the base station to the UE). For example, multiple report transmission times can be configured / defined, and the terminal can repeatedly send event-related information to the base station during the configured / defined report transmission times.

[0231] Implementation method 2-1 relates to a method for increasing transmission reliability by repeatedly transmitting event-related information. The UE may repeatedly transmit event-related information to the base station continuously or discontinuously. According to at least one of the embodiments described below, the UE may repeatedly transmit event-related information.

[0232] Implementation Method 2-1-1

[0233] The base station can send configuration information related to the transmission period and / or the number of times event-related information is repeatedly transmitted to the UE. For example, the base station can configure P time slots (where P is a natural number greater than or equal to 1) for the UE as the reporting period for event-related information. Furthermore, the base station can configure R (where R is a natural number greater than or equal to 1) for the UE as the number of times event-related information is repeatedly transmitted.

[0234] (When an event occurs) the UE can perform repeated transmission of information related to the same event through each of R time slots with a time slot interval P. That is, the UE can send information related to the same event in each of the R time slots, and each of the R time slots can have a time slot interval P.

[0235] Implementation Method 2-1-2

[0236] The reporting period for event-related information can be configured / defined (by the base station) using P time slots. Additionally, within a period, R time slots with a smaller P' time slot interval can be set (by the base station). (When an event occurs) the UE can repeatedly transmit information related to the same event through R time slots with a P' time slot interval (within the event's period).

[0237] For example, suppose we set / define "P=4, P'=1, and R=2", where the time slot as event TO is represented as 0, and the time slot not representing event TO is represented as x. In this case, the time slots {1, 2, 3, 4} within one cycle can be configured as {TO, TO, x, x}, and the time slots {1, 2, 3, 4, 5, 6, 7, 8} within two cycles can be set as {TO, TO, x, x, TO, TO, x, x}.

[0238] Here, event TO can refer to both the TO that sends information related to the event and / or the TO that will send information related to the event.

[0239] Implementation Method 2-1-3

[0240] The base station can send configuration information to the UE regarding the transmission period and / or the number of retransmissions of event-related information. For example, the base station can configure P time slots (where P is a natural number greater than or equal to 1) for the UE as the reporting period for event-related information. Additionally, the base station can configure R (where R is a natural number greater than or equal to 1) for the UE as the number of retransmissions of event-related information.

[0241] (When an event occurs) the UE can repeatedly send event-related information R times using different information within a time slot with the same P time slot interval.

[0242] For example, a UE can repeatedly send event-related information to the base station R times within a time slot with P time slot intervals, using different time resources (e.g., symbols), frequency resources (e.g., frequency locations), and / or spatial resources (e.g., layers, ports, spatial filters).

[0243] Alternatively, the UE may use different beams / panels to transmit event-related information to base station R times. For example, the UE may use a simultaneous transmission method across multiple panels to transmit event-related information to base station R times.

[0244] Implementation Method 2-2

[0245] If an event-based report (e.g., transmission of event-related information) is performed, and the base station does not take any action regarding the report even after a specific period of time has elapsed, the UE may perform an event-based re-report (e.g., retransmission of event-related information).

[0246] For example, when performing an event-based report, a timer associated with the report can be operated / started. When the timer expires, the UE can perform a re-report based on the event (e.g., retransmission of event-related information).

[0247] The above operation can be interpreted as an operation in which retransmission of event-related information is not performed within a specific time period following an event-based report. That is, the UE can send event-related information and not perform retransmission within the specific time period. If event-related information is sent and operations performed by the base station (e.g., transmission of information indicating beam change and / or transmission of event-related ACK information) are performed within the specific time period, the UE can stop / pause the (re)transmission process of event-related information.

[0248] Implementation Methods 2-3

[0249] Response messages / signals from the base station for event-based reporting can be defined. If the UE performs an event-based reporting and does not receive a response message / signal from the base station for a predefined / configured duration or at a specific time, the UE can retransmit the event-related information to the base station.

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

[0251] For example, when performing an event-based report, a timer associated with the report can be operated / started. If no response message / signal is received before the timer expires, the UE can perform an event-based re-report (e.g., retransmission of information associated with the event).

[0252] The above operation can be interpreted as an operation in which the (re)transmission of event-related information for the UE is suspended until a response message / signal is received from the base station or until the timer expires. That is, the UE sends event-related information, and retransmission may not be performed during a predefined / configured time interval (e.g., during the duration of the timer operation).

[0253] Implementations 2-2 and 2-3 relate to a method for improving the reception performance of event-related information at a base station by retransmitting the event-related information to the base station when the normal reception of event-related information at the base station is questionable.

[0254] For example, the timer started / operated after the UE sends event-related information can be configured or predefined by the base station. Additionally, the UE's retransmission operation can be suspended for a specific time period after the event-related information is sent. That is, after sending event-related information, the UE can choose not to retransmit the event-related information for a specific period (e.g., during a time interval configured in the timer).

[0255] Implementation methods 2-4

[0256] When the UE (re)transmits event-related information (e.g., when performing an event-based (re)reporting operation), high UL transmission power can be configured / applied to the UE's (re)transmission operation. For example, when transmitting event-related information, the UE can configure / apply high UL transmission power or perform a power boost.

[0257] For example, the operations and characteristics associated with methods for setting up open-loop power control configurations in a basic wireless communication system (e.g., methods with an SRI field on the DCI) are as follows: When a URLLC transmission conflicts with an eMBB service from another terminal, a method for configuring an open-loop power control set can be executed to amplify the power of the URLLC transmission. When a conflict occurs with an eMBB service from another terminal, the P0 value can be modified to control the open-loop power. Specifically, DCI format 0_1 ​​or 0_2 can be configured to include an "Open-Loop Power Control Parameter Set Indication" field. This field can have a size of 1 bit (if the DCI includes an SRI field). If the value of this field is set to 1, different P0 values ​​can be used for open-loop power control (e.g., power amplification). The value of P0 can be determined based on a list of P0 values ​​set in the RRC (e.g., "p0-PUSCH-SetList-r16") using a one-to-one mapping to SRI code points.

[0258] As an example of this disclosure, when sending event-related information to a base station via an uplink channel (e.g., PUSCH, etc.), power boost can be performed based on the value of the open-loop power control parameter set indicator field (included in the DCI). For example, if the SRI field is present in the DCI, the value of the open-loop power control parameter set indicator field can be set to 1, while if the SRI field is not present in the DCI, the value of the open-loop power control parameter set indicator field can be set to 01 or 10. Additionally, the terminal may expect the value of the open-loop power control parameter set indicator field to be set to 1, 01, or 10.

[0259] Implementation Method 3

[0260] A process, such as that described in Method 1-1, can be applied to send "information about whether an event has occurred" as an SR (or information related to the SR). In this case, conflicts / overlaps may occur between the PUCCH resources used to send information about whether an event has occurred and other BFRQ / SR PUCCH resources. If such conflicts / overlaps occur, it may be necessary to define the type of UCI and / or related UL channel to be sent first.

[0261] In basic wireless communication systems, the coding / RE mapping method for BFRQs can be the same as that for SRs. That is, a BFRQ can be considered as a type of SR and (if necessary) can be represented as an SR for SCell beam fault recovery or a Link Recovery Request (LRR). If a BFRQ overlaps / conflicts with other UL channel resources, it can be transmitted with a higher priority than a regular SR.

[0262] Similar to BFRQ in Method 1-1, the same encoding / RE mapping method as SR can be used to send information about whether an event has occurred to the base station.

[0263] Simultaneously, a BFRQ can be generated in cases where all serving beams are faulty or where no current serving beam is faulty but a new beam with higher quality has been discovered. In such cases, the BFRQ can be more urgent information than information about whether an event has occurred. Furthermore, event-related information can include information about analog beams in the high-frequency band, and because the reliability and efficiency of TB transmission can be improved through beam management processing, event-related information can be more important than a general SR.

[0264] Therefore, for example, the priority of information regarding whether an event has occurred can be equal to or lower than the priority of BFRQ. Furthermore, the priority of information regarding whether an event has occurred can be equal to or higher than the priority of general SR.

[0265] Additionally or alternatively, the priority of event-related information may be defined as the same as that of SR or BFRQ.

[0266] Implementation 3 relates to a method for transmitting information about whether an event (e.g., a beam-related event, etc.) has occurred in the same manner as the SR. For example, the UE may transmit information about whether an event has occurred to the base station based on the encoding, RE mapping, and multiplexing methods applied to the SR.

[0267] For example, if information about whether an event has occurred (e.g., UCI) or an uplink channel containing such information overlaps or conflicts with another channel, the UE can determine the type of information to send based on the priority of each channel / information. For instance, the priority of information about whether an event has occurred may be equal to or lower than the priority of BFRQ. Furthermore, the priority of information about whether an event has occurred may be equal to or higher than the priority of a general SR.

[0268] When performing event-based transmission / reporting via MAC-CE, the method according to Implementation 3 described above can also be used / applied. That is, when transmitting event-based information (e.g., information about whether an event has occurred, or reporting information about an event) via MAC-CE, or / and when no available UL-SCH is assigned, the UE can request UL-SCH from the base station via SR to transmit MAC-CE.

[0269] In basic wireless communication systems, with exceptions (e.g., BFR MAC-CE), a typical MAC-CE may not support triggering SR. That is, even if a MAC-CE has data to transmit, SR transmission may not be triggered. Furthermore, UCI may not be supported for triggering SR.

[0270] Therefore, MAC-CE / UCI for event-based transmission / reporting can be defined / configured to trigger SR transmissions. Additionally, SRs can be mapped to (only) dedicated SR PUCCH resources (such as BFR procedures), ii) enabling the use of SR PUCCH resources for triggering logical channels, or iii) enabling the use of SR PUCCH resources for BFR.

[0271] Implementation Method 4

[0272] Implementation 4 relates to a method for performing MAC-CE or UCI-triggered SRs based on event-based transmission / reporting.

[0273] For example, when methods 1-1a, 1-1b and 2 are applied, event-related information (e.g., information about whether the event occurred, event-related report information, etc.) can be sent to the base station via MAC-CE and / or UCI.

[0274] For example, a MAC-CE or UCI containing event-related information can trigger the transmission of an SR (for example, UL-SCH resources, uplink channel-related resources such as PUSCH, PUCCH, etc.) to send a MAC-CE or UCI.

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

[0276] Implementation Method 5

[0277] Implementation 5 relates to a method for transmitting SRs related to event-based transmission / reporting.

[0278] Specifically, SRs related to event-based transmissions / reports (sent via MAC-CE and / or UCI) can be sent according to at least one of the methods described below. SRs related to event-based transmissions / reports can collectively refer to SRs requesting UL-SCH resources to send event-related information.

[0279] Method 5-1: SRs related to event-based transmission / reporting can use dedicated SR PUCCH resources. For example, SRs related to event-based transmission / reporting can be sent to the base station via dedicated SR PUCCH resources based on the assigned SR ID / configuration. That is, the UE can send SRs related to event-based transmission / reporting to the base station based on dedicated PUCCH resources associated with the dedicated SR ID / configuration.

[0280] Method 5-2: SRs related to event-based transmission / reporting can use the SR PUCCH resource of the triggering logical channel. That is, the UE can send SRs related to event-based transmission / reporting to the base station based on the SR PUCCH resource of the triggering logical channel.

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

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

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

[0284] Here, according to Implementation 3, a priority can be applied between SR PUCCHs. For example, the priority of an SR PUCCH associated with MAC-CE / UCI for event-based transmission / reporting (e.g., event-related SR PUCCH) can be lower than or equal to the priority of an SR PUCCH for BFR. Furthermore, the priority of an SR PUCCH associated with MAC-CE / UCI for event-based transmission / reporting (e.g., event-related SR PUCCH) can be higher than or equal to the priority of an SR PUCCH for logical channels. If an SR PUCCH associated with MAC-CE / UCI for event-based transmission / reporting (e.g., event-related SR PUCCH) overlaps with other SR PUCCH resources, the UE can preferentially transmit the SR PUCCH with the higher priority to the base station according to the aforementioned priority rules.

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

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

[0287] Figure 9This is a diagram illustrating the signaling process between the network side and the UE according to one embodiment of the present disclosure.

[0288] Figure 9 Examples of signaling between the network side and the terminal (UE) are illustrated in M-TRP scenarios where the examples disclosed above (e.g., implementation 1, implementation 2, implementation 3, implementation 4, implementation 5, or / and a combination of one or more detailed implementations of the examples) can be applied.

[0289] Here, the UE / network side is exemplary and can be referenced. Figure 10 The various devices described are used as alternatives. Figure 9 This is for illustrative purposes only and does not limit the scope of this disclosure. Furthermore, depending on the circumstances and / or configuration, details may be omitted. Figure 9 Some of the steps shown. Additionally, the above-described uplink transmission and reception operations, M-TRP related operations, etc., may involve or be used for... Figure 9 Operations on the network side / UE.

[0290] In the following description, the network side may be a base station comprising multiple TRPs, or it may be a cell comprising multiple TRPs. Alternatively, the network side may include multiple RRHs (Remote Radio Headers) / RRUs (Remote Radio Units).

[0291] For example, ideal / non-ideal backhaul can be configured between TRP 1 and TRP 2 that constitute the network side. Furthermore, the following description is based on multiple TRPs, but it can also be extended and applied to transmissions through multiple panels / cells, and to transmissions through multiple RRH / RRUs, etc.

[0292] Additionally, the following description is based on "TRP," but as mentioned above, "TRP" can be applied by replacing it with expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pecimen cell, etc.), TP (transmitter point), base station (gNB, etc.). As mentioned above, TRPs can be classified based on information about CORESET groups (or CORESET pools) (e.g., CORESET index, ID).

[0293] For example, when a UE is configured to transmit and receive with multiple TRPs (or cells), it may mean that multiple CORESET groups (or CORESET pools) are configured for a UE. The configuration of such CORESET groups (or CORESET pools) can be performed via higher-layer signaling (e.g., RRC signaling, etc.).

[0294] Additionally, a base station can generally refer to the entity that performs data transmission and reception with the UE. For example, a base station can be a concept that includes at least one TP (transmitter point) and at least one TRP (transmitter and receiver point). Furthermore, the TP and / or TRP can include the base station's panel, transmission and reception units, etc.

[0295] The UE can receive configuration information from the network (S105).

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

[0297] For example, UL channel resources used for reporting may include information for configuring UL channel resources for reporting event-related information and / or information for describing resources for reporting other information (e.g., information for reporting separate information unrelated to the event).

[0298] Alternatively or additionally, the configuration information may include configuration information relating to each of one or more combinations of implementation methods 1, 2, 3, 4, 5, and / or the detailed implementation methods of the examples. Alternatively or additionally, the configuration information may include configuration information relating to methods 1-1, 1-1a, 1-1b, 1-2, 1-3, 1-3a, 1-3b, 2, 3, 3-1, and 3-2.

[0299] The configuration information described above can be sent to the UE via upper-layer signaling (e.g., SIB, RRC messages, MAC CE, etc.), but is not limited to this. Additionally, the configuration information can be sent to the terminal via separate higher-layer signaling, but some configuration information can be sent to the terminal via a single higher-layer signaling.

[0300] The UE can receive messages / signals (or control information) (e.g., MAC-CE, DCI, etc.) from the base station to activate / initiate event-based reporting and / or UL channel resources (S110). For example, the UE can receive activation messages / signals for UL channel resources from the base station to send event-related information. For example, if event-related reporting and / or UL channel resources are indicated / configured via configuration information (e.g., RRC messages, etc.), the operation according to step S110 can be omitted.

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

[0302] The general apparatus disclosed herein can be used

[0303] Figure 10 This is a block diagram illustrating a wireless communication system according to an embodiment of the present disclosure.

[0304] Reference Figure 10 The first device 100 and the second device 200 can transmit and receive wireless signals through various radio access technologies (e.g., LTE, NR).

[0305] The first device 100 may include 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 processors 102 may control the memories 104 and / or the transceivers 106, and may be configured to implement the descriptions, functions, processes, suggestions, methods and / or operation flowcharts included in this disclosure.

[0306] For example, after generating first information / signal by processing information in memory 104, processor 102 can transmit a wireless signal including the first information / signal via transceiver 106. Alternatively, processor 102 can receive a wireless signal including second information / signal via transceiver 106, and then store the information obtained through signal processing of the second information / signal in memory 104.

[0307] Memory 104 may be connected to processor 102 and may store various information related to the operation of processor 102. For example, memory 104 may store software code including commands for performing all or part of the processing controlled by processor 102 or for performing commands included in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts herein. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). Transceiver 106 may be connected to processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used with an RF (radio frequency) unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0308] The second device 200 may include one or more processors 202 and one or more memories 204, and may additionally include one or more transceivers 206 and / or one or more antennas 208. The processors 202 may control the memories 204 and / or the transceivers 206, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. For example, the processors 202 may generate third information / signals by processing information in the memories 204, and then transmit a wireless signal including the third information / signals via the transceivers 206. Additionally, the processors 202 may receive wireless signals including fourth information / signals via the transceivers 206, and then store information obtained through signal processing of the fourth information / signals in the memories 204. The memories 204 may be connected to the processors 202 and may store various information related to the operation of the processors 202. For example, the memories 204 may store software code including commands for performing all or part of the processing controlled by the processors 202 or for executing the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). Transceiver 206 may be connected to processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used with an RF unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0309] The hardware components of devices 100 and 200 will be described in more detail below. Not limited thereto, one or more protocol layers may be implemented by one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102 and 202 may generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. One or more processors 102, 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information, in accordance with the functions, processes, suggestions, and / or methods disclosed in this disclosure, to provide them to one or more transceivers 106, 206. One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206, and obtain PDUs, SDUs, messages, control information, data, or information, in accordance with the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure.

[0310] One or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application-Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field-Programmable Gate Arrays) may be included in one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, etc. Firmware or software configured to execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure may be included in one or more processors 102, 202, or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods and / or operation flowcharts included in this disclosure can be implemented using firmware or software in the form of codes, commands and / or command sets.

[0311] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, signals, messages, information, programs, code, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located internally and / or externally to one or more processors 102, 202. Furthermore, one or more memories 104, 204 may be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0312] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or operation flowcharts of this disclosure to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this 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 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure, via one or more antennas 108, 208. In this disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received wireless signals / channels, etc., from RF band signals into baseband signals for processing using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, wireless signals / channels, etc., processed using one or more processors 102, 202, from baseband signals into RF band signals. Therefore, one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0313] The above embodiments combine the elements and features of this disclosure in a predetermined form. Unless otherwise expressly stated, each element or feature should be considered optional. Each element or feature may be implemented without being combined with other elements or features. Furthermore, embodiments of this disclosure may include combinations of some elements and / or features. The order of operations described in embodiments of this disclosure may be changed. Some elements or features of one embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. Obviously, embodiments may include claims that are not explicitly referenced in the claims, or may be included as new claims after the application has been amended.

[0314] It will be apparent to those skilled in the art that this disclosure may be implemented in other specific forms without departing from its essential characteristics. Therefore, the foregoing detailed description should not be construed as restrictive in every respect, but rather as illustrative. The scope of this disclosure should be determined by a reasonable interpretation of the appended claims, and all variations within the equivalent scope of this disclosure are included within its scope.

[0315] The scope of this disclosure includes software or machine-executable commands (e.g., operating systems, applications, firmware, programs, etc.) that operate in a device or computer according to methods of various embodiments, as well as non-transitory computer-readable media that cause software or commands to be stored and executable in a device or computer. Commands that can be used to program a processing system to perform the features described in this disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in this disclosure can be implemented by using a computer program product including such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, and may include non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory may optionally include one or more storage devices located remotely from the processor. The memory, or alternatively, the non-volatile memory devices in the memory include non-transitory computer-readable storage media. The features described in this disclosure can be stored in any machine-readable medium to control the hardware of a processing system and can be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using results from embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0316] The wireless communication technologies implemented in the devices 100 and 200 of this disclosure may include narrowband Internet of Things (IoT) for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the aforementioned names. Additionally or alternatively, the wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (Enhanced Machine-Type Communication). For example, LTE-M technology may be implemented in at least any of various standards, including 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, etc., and is not limited to the aforementioned names. Additionally or alternatively, the wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may include at least any one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and are not limited to the aforementioned names. For example, ZigBee technology can generate PANs (Personal Area Networks) associated with small / low-power digital communication based on various standards (e.g., IEEE 802.15.4, etc.) and may be referred to by various names.

[0317] Industrial applicability

[0318] The method presented in this disclosure is primarily illustrated based on examples applied to 3GPP LTE / LTE-A and 5G systems, but it can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method, the method comprising: The user equipment (UE) receives the first configuration information related to the event from the base station; Based on the occurrence of the event, the UE encodes information related to the event on the first uplink channel according to the second configuration information related to the scheduling request SR; as well as Based on the overlap between the first uplink channel and a second uplink channel including the SR or Link Recovery Request (LRR), the UE transmits either the first uplink channel or the second uplink channel to the base station according to the priority of the information related to the event. The priority of information related to the event is higher than or equal to the priority of the SR and lower than or equal to the priority of the LRR.

2. The method according to claim 1, wherein, Based on the overlap between the first uplink channel and the second uplink channel including the SR, the first uplink channel is transmitted to the base station according to the priority of the information related to the event, and Based on the overlap between the first uplink channel and the second uplink channel including the LRR, the second uplink channel is sent to the base station according to the priority of the information related to the event.

3. The method according to claim 1, wherein, The second configuration information associated with the SR includes at least one of the SR's period, offset, priority, resources, encoding method, or identifier ID.

4. The method according to claim 1, wherein, The first configuration information includes information related to the transmission period and number of transmissions of information related to the event, and Based on the transmission period and the number of transmissions related to the event, the information related to the event is repeatedly sent to the base station.

5. The method according to claim 1, wherein, Based on the first uplink channel being transmitted to the base station, a timer is run for retransmitting information related to the event, and If no response message related to the event is received from the base station before the timer expires, the information related to the event is retransmitted to the base station.

6. The method according to claim 5, wherein, Based on receiving a response message from the base station regarding information related to the event before the timer expires, the operation of the timer and the retransmission of information related to the event are stopped.

7. The method according to claim 6, wherein, The response message includes an ACK message for the first uplink channel.

8. The method according to claim 1, wherein, The downlink control information associated with the first uplink channel includes a power control parameter set indication field, and The power of the first uplink channel is determined based on the power control parameter set indication field.

9. The method according to claim 1, wherein, The base station sends downlink control information related to the first uplink channel to the UE, and The UE sends an ACK message for the downlink control information to the base station.

10. The method according to claim 1, wherein, The first uplink channel is either the Configuration Authorized CG Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH).

11. The method according to claim 1, wherein, The information related to the event is included in the uplink control information (UCI).

12. A user equipment (UE), the UE comprising: At least one transceiver; as well as At least one processor, said at least one processor being coupled to said at least one transceiver, The at least one processor is configured to: Receive first configuration information related to the event from the base station through the at least one transceiver; Based on the occurrence of the event, information related to the event is encoded on the first uplink channel according to the second configuration information related to the scheduling request SR; and Based on the overlap between the first uplink channel and a second uplink channel including the SR or Link Recovery Request (LRR), the first uplink channel or the second uplink channel is transmitted to the base station through the at least one transceiver according to the priority of the information related to the event. The priority of information related to the event is higher than or equal to the priority of the SR and lower than or equal to the priority of the LRR.

13. A method, the method comprising: The base station sends the first configuration information related to the event to the user equipment (UE); as well as Based on the occurrence of the event, the base station receives from the UE, according to the priority associated with the event: i) a first uplink channel including information related to the event, or ii) a second uplink channel including a scheduling request (SR) or a link recovery request (LRR). The first uplink channel and the second uplink channel overlap in the same time resource. The information related to the event is encoded on the first uplink channel based on second configuration information related to the SR, and The information related to the event has a priority higher than or equal to the priority of the SR and lower than or equal to the priority of the LRR.

14. A base station, the base station comprising: At least one transceiver; as well as At least one processor, said at least one processor being coupled to said at least one transceiver, The at least one processor is configured to: First configuration information related to the event is sent to the user equipment (UE) through the at least one transceiver; and Based on the occurrence of the event, the at least one transceiver receives from the UE, according to the priority associated with the event, either i) a first uplink channel including information related to the event, or ii) a second uplink channel including a scheduling request (SR) or a link recovery request (LRR). The first uplink channel and the second uplink channel overlap in the same time resource. The information related to the event is encoded on the first uplink channel based on second configuration information related to the SR, and The information related to the event has a priority higher than or equal to the priority of the SR and lower than or equal to the priority of the LRR.

15. A processing apparatus configured to control a user equipment (UE), the processing apparatus comprising: One or more processors; as well as One or more computer memories, operatively coupled to the one or more processors and storing instructions that, based on execution by the one or more processors, perform the method according to any one of claims 1 to 11.

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

Images