Method and device for controlling pucch transmission for beam reporting in user equipment-initiated beam management operation

By controlling PUCCH transmissions with prohibit timers for UEI/ED beam management, the method addresses resource waste and power consumption issues, enhancing resource efficiency.

WO2026235281A1PCT designated stage Publication Date: 2026-11-12HYUNDAI MOTOR CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/004015
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-07
Filing Date
2026-03-12
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In UE-initiated/event-driven beam management, the frequent transmission of physical uplink control channels (PUCCH) leads to resource waste and increased power consumption due to unnecessary transmissions, overwhelming the network.

Method used

Implement a method where a terminal transmits a first UL channel to notify an event, followed by a second UL channel with a beam report using allocated resources, and initiates prohibit timers to prevent additional transmissions if the triggering beams are the same, with different timers for each event and modes of operation.

Benefits of technology

This approach reduces excessive PUCCH transmissions, minimizing resource overhead and improving UL resource utilization in UEI/ED beam management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026004015_12112026_PF_FP_ABST
    Figure KR2026004015_12112026_PF_FP_ABST
Patent Text Reader

Abstract

This method of a user equipment comprises the steps of: if a first event is detected, transmitting a first UL channel notifying of the first event to a base station; and transmitting a second UL channel including a beam report based on the first event to the base station by using a UL resource allocated through DCI from the base station or a UL resource pre-allocated from the base station, wherein the user equipment starts a first prohibit timer at a first time point after the transmission of the first UL channel, and starts a second prohibit timer at a second time point after the transmission of the second UL channel, and the transmission of an additional first UL channel for notifying of a detected second event may be prohibited during the period during which the first prohibit timer is operated and the period during which the second prohibit timer is operated.
Need to check novelty before this filing date? Find Prior Art

Description

Method and apparatus for controlling PUCCH transmission for beam reporting in terminal-led beam management operation

[0001] The present disclosure relates to a beam management method in a mobile communication system, and more specifically, to a method and apparatus for controlling a physical uplink control channel (PUCCH) transmission for beam reporting in a UE-initiated / event-driven beam reporting operation.

[0002] Communication networks (e.g., 5G communication networks, 6G communication networks, etc.) are being developed to provide communication services that are improved over existing communication networks (e.g., LTE (long term evolution), LTE-A (advanced), etc.). 5G communication networks (e.g., NR (new radio) communication networks) can support frequency bands above 6 GHz as well as frequency bands below 6 GHz. That is, 5G communication networks can support the FR1 band and / or FR2 band. 5G communication networks can support a wider variety of communication services and scenarios compared to LTE communication networks. For example, usage scenarios for 5G communication networks may include eMBB (enhanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication), mMTC (massive Machine Type Communication), etc.

[0003] 6G communication networks can support a wider variety of communication services and scenarios compared to 5G communication networks. 6G communication networks can meet the requirements for ultra-high performance, ultra-bandwidth, ultra-spatial, ultra-precision, ultra-intelligence, and / or ultra-reliability. 6G communication networks can support a wide range of frequency bands and can be applied to various usage scenarios (e.g., terrestrial communication, non-terrestrial communication, sidelink communication, etc.).

[0004] Meanwhile, 3GPP (3 rd Release-19 of the generation partnership project is proceeding with standardization for user equipment-initiated (UEI) and event-driven (ED) beam management to address the problems of conventional network-driven beam management. Unlike conventional network-driven beam management, user equipment-initiated / event-driven beam management is a method in which a terminal, which can recognize the current state of the beam and the trend of beam changes relatively faster than the base station, proactively performs beam management.

[0005] In UEI / ED beam management, the first UL (uplink) channel (i.e., the first PUCCH (physical uplink control channel)) is a short control signal that can be transmitted very frequently. Therefore, if the terminal frequently detects events due to changes in channel quality, the network may become overloaded due to the frequent occurrence of UL control signals. The unnecessarily frequent transmission of the first PUCCH can lead to the waste of UL resources and increased power consumption by the terminal. Therefore, a method is required to prevent the transmission of unnecessary first PUCCHs.

[0006] The purpose of the present disclosure to solve the above-mentioned problems is to provide a method and apparatus for controlling a physical uplink control channel (PUCCH) transmission for beam reporting in a UE-initiated / event-driven beam reporting operation.

[0007] A method of a terminal according to embodiments of the present disclosure for achieving the above objective comprises: a step of transmitting a first uplink (UL) channel to a base station to notify the first event when a first event is detected; and a step of transmitting a second UL channel to a base station, including a beam report according to the first event, using a UL resource allocated from the base station via downlink control information (DCI) or a UL resource pre-allocated from the base station, wherein the terminal starts a first prohibit timer at a first time after the transmission of the first UL channel and starts a second prohibit timer at a second time after the transmission of the second UL channel, and during the period in which the first prohibit timer is operated and during the period in which the second prohibit timer is operated, the transmission of an additional first UL channel notifying the detected second event may be prohibited.

[0008] The transmission of the additional first UL channel may be prohibited if the beam(s) triggering the first event and the beam(s) triggering the second event are the same.

[0009] The first event and the second event are Event-2 for UEI / ED (UE-initiated / Event-drvien) beam reporting operations, and the beam(s) triggering the first event and the beam(s) triggering the second event may be the same current beam and / or the same new beam.

[0010] The first prohibition timer can be set to a value smaller than the second prohibition timer.

[0011] The first prohibition timer and the second prohibition timer may each be set to a parameter signaled from the base station and a value derived from the parameter, or each may be set to values ​​derived from the parameter.

[0012] The parameter signaled from the base station may be an SR (scheduling request) prohibition timer value or a PUCCH (physical uplink control channel) prohibition timer value defined separately from the SR prohibition timer.

[0013] When the terminal performs a UEI / ED beam reporting operation according to Mode B, the first UL channel is transmitted repeatedly according to a predetermined number of repeated transmissions, and the first prohibition timer may start after the last repetition of the first channel has been transmitted.

[0014] The first point in time above may be a point in time corresponding to the first symbol after the transmission of the first UL channel has ended.

[0015] The above first point in time may be a point in time corresponding to the first symbol after the reception of the DCI has ended.

[0016] The above second point in time may be a point in time corresponding to the first symbol after the transmission of the above second UL channel has ended.

[0017] When the terminal performs a UEI / ED beam reporting operation according to Mode A, the first prohibition timer may be set to a value smaller than the first prohibition timer when the terminal performs a UEI / ED beam reporting operation according to Mode B.

[0018] When the terminal performs a UEI / ED beam reporting operation according to Mode A, the first prohibition timer is set to 0, and when the terminal performs a UEI / ED beam reporting operation according to Mode B, the first prohibition timer can be set to a value greater than 0.

[0019] A terminal according to embodiments of the present disclosure for achieving the above objective comprises at least one processor, and the at least one processor enables the terminal to perform the steps of: transmitting a first uplink (UL) channel to a base station to notify the first event when a first event is detected; and transmitting a second UL channel to the base station to include a beam report according to the first event using a UL resource allocated from the base station via downlink control information (DCI) or a UL resource pre-allocated from the base station, and the terminal starts a first prohibit timer at a first time after the transmission of the first UL channel and starts a second prohibit timer at a second time after the transmission of the second UL channel, and during the period when the first prohibit timer is in operation and during the period when the second prohibit timer is in operation, the transmission of an additional first UL channel notifying the detected second event may be prohibited.

[0020] The transmission of the additional first UL channel may be prohibited if the beam(s) triggering the first event and the beam(s) triggering the second event are the same.

[0021] The first event and the second event are Event-2 for UEI / ED (UE-initiated / Event-drvien) beam reporting operations, and the beam(s) triggering the first event and the beam(s) triggering the second event may be the same current beam and / or the same new beam.

[0022] The first prohibition timer can be set to a value smaller than the second prohibition timer.

[0023] When the terminal performs a UEI / ED beam reporting operation according to Mode B, the first UL channel is transmitted repeatedly according to a predetermined number of repeated transmissions, and the first prohibition timer may start after the last repetition of the first channel has been transmitted.

[0024] The above first point in time may be a point in time corresponding to the first symbol after the reception of the DCI has ended.

[0025] When the terminal performs a UEI / ED beam reporting operation according to Mode A, the first prohibition timer may be set to a value smaller than the first prohibition timer when the terminal performs a UEI / ED beam reporting operation according to Mode B.

[0026] When the terminal performs a UEI / ED beam reporting operation according to Mode A, the first prohibition timer is set to 0, and when the terminal performs a UEI / ED beam reporting operation according to Mode B, the first prohibition timer can be set to a value greater than 0.

[0027] According to embodiments of the present disclosure, the first PUCCH transmission of a terminal can be appropriately controlled in a UEI / ED beam management operation. Accordingly, by preventing excessive first PUCCH transmission, the overhead of the UEI / ED beam management operation can be reduced and the utilization rate of UL resources can be improved.

[0028] FIG. 1 is a conceptual diagram illustrating a first embodiment of a communication system.

[0029] FIG. 2 is a block diagram illustrating a first embodiment of a communication node constituting a communication system.

[0030] FIG. 3 is a block diagram illustrating a first embodiment of communication nodes performing communication.

[0031] FIG. 4a is a block diagram illustrating a first embodiment of a transmission path.

[0032] FIG. 4b is a block diagram illustrating a first embodiment of a receiving path.

[0033] FIG. 5 is a conceptual diagram illustrating a first embodiment of a system frame in a communication system.

[0034] FIG. 6 is a conceptual diagram illustrating a first embodiment of a subframe in a communication system.

[0035] FIG. 7 is a conceptual diagram illustrating a first embodiment of a slot in a communication system.

[0036] FIG. 8 is a conceptual diagram illustrating a first embodiment of a time-frequency resource in a communication system.

[0037] FIG. 9 is a flowchart for explaining Mode A operation to which embodiments of the present disclosure are applied.

[0038] FIG. 10 is a flowchart illustrating a Mode B operation to which embodiments of the present disclosure are applied.

[0039] FIGS. 11 to 13 are flowcharts for explaining UEI / ED beam management operations according to the present disclosure.

[0040] The present disclosure is capable of various modifications and may have various embodiments, and specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present disclosure to specific embodiments and should be understood to include all modifications, equivalents, and substitutions that fall within the spirit and scope of the present disclosure.

[0041] Terms such as "first," "second," etc., may be used to describe various components, but said components should not be limited by said terms. Such terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the present disclosure, the first component may be named the second component, and similarly, the second component may be named the first component. The term "and / or" may mean a combination of a plurality of related described items or any of a plurality of related described items.

[0042] In the present disclosure, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B". Additionally, in the present disclosure, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B".

[0043] In the present disclosure, (re)transmission may mean "transmission," "retransmission," or "transmission and retransmission"; (re)setting may mean "setting," "resetting," or "setting and resetting"; (re)connection may mean "connection," "reconnection," or "connection and reconnection"; and (re)connection may mean "connection," "reconnection," or "connection and reconnection".

[0044] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0045] The terms used in this disclosure are used merely to describe specific embodiments and are not intended to limit this disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, terms such as “comprising” or “having” are intended to specify the existence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0046] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which this disclosure pertains. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this disclosure.

[0047] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. To facilitate an overall understanding of the present disclosure, the same reference numerals are used for identical components in the drawings, and redundant descriptions of identical components are omitted. Operations according to combinations of embodiments, extensions of embodiments, and / or modifications of embodiments may be performed, as well as the embodiments explicitly described in the present disclosure. The performance of some operations may be omitted, and the order of operations may be changed.

[0048] In the embodiments, even when a method performed at a first communication node among the communication nodes (e.g., transmission or reception of a signal) is described, the corresponding second communication node may perform a method corresponding to the method performed at the first communication node (e.g., reception or transmission of a signal). That is, when the operation of a UE (user equipment) is described, the corresponding base station may perform an operation corresponding to the operation of the UE. Conversely, when the operation of a base station is described, the corresponding UE may perform an operation corresponding to the operation of the base station.

[0049] A base station may be referred to as Node B, evolved Node B, gNode B (next generation node B), gNB, device, apparatus, node, communication node, BTS (base transceiver station), RRH (radio remote head), TRP (transmission reception point), RU (radio unit), RSU (road side unit), radio transceiver, access point, access node, etc. A UE may be referred to as terminal, device, apparatus, node, communication node, end node, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, OBU (on-broad unit), etc.

[0050] In the present disclosure, signaling may be at least one of upper-layer signaling, MAC signaling, or PHY (physical) signaling. A message used for upper-layer signaling may be referred to as an "upper-layer message" or an "upper-layer signaling message." A message used for MAC signaling may be referred to as a "MAC message" or a "MAC signaling message." A message used for PHY signaling may be referred to as a "PHY message" or a "PHY signaling message." Upper-layer signaling may refer to the transmission and reception operations of system information (e.g., MIB (master information block), SIB (system information block)) and / or RRC messages. MAC signaling may refer to the transmission and reception operations of MAC-CE (control element). PHY signaling may refer to the transmission and reception operations of control information (e.g., DCI (downlink control information), UCI (uplink control information), SCI (sidelink control information)).

[0051] In the present disclosure, "setting an operation (e.g., a transmission operation)" may mean that "setting information for said operation (e.g., an information element, a parameter)" and / or "information directing the performance of said operation" is signaled. "Setting an information element (e.g., a parameter)" may mean that said information element is signaled. In the present disclosure, "signal and / or channel" may mean a signal, a channel, or "signal and channel," and "signal" may be used to mean "signal and / or channel."

[0052] The communication networks to which the embodiments are applied are not limited to those described below, and the embodiments may be applied to various communication networks (e.g., 4G communication networks, 5G communication networks, and / or 6G communication networks). Here, the term "communication network" may be used interchangeably with "communication system."

[0053] FIG. 1 is a conceptual diagram illustrating a first embodiment of a communication system.

[0054] Referring to FIG. 1, the communication system (100) may include a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Additionally, the communication system (100) may further include a core network (e.g., an S-GW (serving-gateway), a P-GW (PDN (packet data network)-gateway), and an MME (mobility management entity)). If the communication system (100) is a 5G communication system (e.g., a new radio (NR) system), the core network may include an AMF (access and mobility management function), a UPF (user plane function), an SMF (session management function), etc.

[0055] Multiple communication nodes (110 to 130) can support communication protocols defined in 3GPP (3rd generation partnership project) standards (e.g., LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.). Multiple communication nodes (110 to 130) can support CDMA (code division multiple access) technology, WCDMA (wideband CDMA) technology, TDMA (time division multiple access) technology, FDMA (frequency division multiple access) technology, OFDM (orthogonal frequency division multiplexing) technology, Filtered OFDM technology, CP (cyclic prefix)-OFDM technology, DFT-s-OFDM (discrete Fourier transform-spread-OFDM) technology, OFDMA (orthogonal frequency division multiple access) technology, SC (single carrier)-FDMA technology, NOMA (non-orthogonal multiple access) technology, GFDM (generalized frequency division multiplexing) technology, FBMC (filter bank multi-carrier) technology, UFMC (universal filtered multi-carrier) technology, SDMA (space division multiple access) technology, etc. Each of the multiple communication nodes may have the following structure.

[0056] FIG. 2 is a block diagram illustrating a first embodiment of a communication node constituting a communication system.

[0057] Referring to FIG. 2, the communication node (200) may include at least one processor (210), a memory (220), and a transceiver (230) that is connected to a network to perform communication. Additionally, the communication node (200) may further include an input interface device (240), an output interface device (250), a storage device (260), etc. Each component included in the communication node (200) may be connected by a bus (270) to communicate with one another.

[0058] The processor (210) can execute a program command stored in at least one of the memory (220) and the storage device (260). The processor (210) may mean a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which the methods according to embodiments of the present disclosure are performed. Each of the memory (220) and the storage device (260) may be composed of at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory (220) may be composed of at least one of read-only memory (ROM) and random access memory (RAM).

[0059] Referring again to FIG. 1, the communication system (100) may include a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) and a plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) may form a macro cell. Each of the fourth base station (120-1) and the fifth base station (120-2) may form a small cell. The fourth base station (120-1), the third terminal (130-3), and the fourth terminal (130-4) may be located within the cell coverage of the first base station (110-1). The second terminal (130-2), the fourth terminal (130-4), and the fifth terminal (130-5) may be located within the cell coverage of the second base station (110-2). The fifth base station (120-2), the fourth terminal (130-4), the fifth terminal (130-5), and the sixth terminal (130-6) may be located within the cell coverage of the third base station (110-3). The first terminal (130-1) may be located within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be located within the cell coverage of the fifth base station (120-2).

[0060] Here, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be referred to as NB (NodeB), eNB (evolved NodeB), gNB, ABS (advanced base station), HR-BS (high reliability-base station), BTS (base transceiver station), radio base station, radio transceiver, access point, access node, RAS (radio access station), MMR-BS (mobile multihop relay-base station), RS (relay station), ARS (advanced relay station), HR-RS (high reliability-relay station), HNB (home NodeB), HeNB (home eNodeB), RSU (road side unit), RRH (radio remote head), TP (transmission point), TRP (transmission and reception point), etc.

[0061] Each of the multiple terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) may be referred to as UE (user equipment), TE (terminal equipment), AMS (advanced mobile station), HR-MS (high reliability-mobile station), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, node, device, OBU (on board unit), etc.

[0062] Meanwhile, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may operate in different frequency bands or in the same frequency band. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to each other via an ideal backhaul link or a non-ideal backhaul link, and may exchange information with each other via an ideal backhaul link or a non-ideal backhaul link. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to a core network via an ideal backhaul link or a non-ideal backhaul link. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit a signal received from the core network to the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6), and can transmit a signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) to the core network.

[0063] In addition, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can support MIMO transmission (e.g., SU (single user)-MIMO, MU (multi user)-MIMO, massive MIMO, etc.), CoMP (coordinated multipoint) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, sidelink communication (e.g., D2D (device to device communication), ProSe (proximity services)), IoT (Internet of Things) communication, dual connectivity (DC), etc. Here, each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) can perform an operation corresponding to the base station (110-1, 110-2, 110-3, 120-1, 120-2) and an operation supported by the base station (110-1, 110-2, 110-3, 120-1, 120-2). For example, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) based on the SU-MIMO method, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) based on the SU-MIMO method. Alternatively, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) and the fifth terminal (130-5) based on the MU-MIMO method, and each of the fourth terminal (130-4) and the fifth terminal (130-5) can receive a signal from the second base station (110-2) by the MU-MIMO method.

[0064] Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can transmit a signal to the fourth terminal (130-4) based on the CoMP method, and the fourth terminal (130-4) can receive a signal from the first base station (110-1), the second base station (110-2), and the third base station (110-3) by the CoMP method. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive signals based on the CA method with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) within its cell coverage area. Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can control sidelink communication between the fourth terminal (130-4) and the fifth terminal (130-5), and each of the fourth terminal (130-4) and the fifth terminal (130-5) can perform sidelink communication by controlling each of the second base station (110-2) and the third base station (110-3).

[0065] Meanwhile, communication nodes performing communication in a communication network may be configured as follows. The communication node shown in FIG. 3 may be a specific embodiment of the communication node shown in FIG. 2.

[0066] FIG. 3 is a block diagram illustrating a first embodiment of communication nodes performing communication.

[0067] Referring to FIG. 3, the first communication node (300a) and the second communication node (300b) may each be a base station or a UE. The first communication node (300a) may transmit a signal to the second communication node (300b). A transmission processor (311) included in the first communication node (300a) may receive data (e.g., a data unit) from a data source (310). The transmission processor (311) may receive control information from a controller (316). The control information may include at least one of system information, RRC setting information (e.g., information set by RRC signaling), MAC control information (e.g., MAC-CE), or PHY control information (e.g., DCI, SCI).

[0068] The transmitting processor (311) can generate data symbol(s) by performing processing operations on data (e.g., encoding operations, symbol mapping operations, etc.). The transmitting processor (311) can generate control symbol(s) by performing processing operations on control information (e.g., encoding operations, symbol mapping operations, etc.). Additionally, the transmitting processor (311) can generate synchronization / reference symbol(s) for synchronization signals and / or reference signals.

[0069] The Tx MIMO processor (312) can perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or synchronization / reference symbol(s). The output of the Tx MIMO processor (312) (e.g., a symbol stream) can be provided to modulators (MODs) included in transceivers (313a to 313t). The modulators (MODs) can perform processing operations on the symbol stream to generate modulated symbols and perform additional processing operations on the modulated symbols (e.g., analog conversion operations, amplification operations, filtering operations, up-conversion operations) to generate signals. The signals generated by the modulators (MODs) of the transceivers (313a to 313t) can be transmitted through antennas (314a to 314t).

[0070] Signals transmitted by the first communication node (300a) can be received at the antennas (364a to 364r) of the second communication node (300b). Signals received at the antennas (364a to 364r) can be provided to demodulators (DEMODs) included in the transceivers (363a to 363r). The demodulators (DEMODs) can obtain samples by performing processing operations on the signals (e.g., filtering, amplification, down-conversion, digital conversion). The demodulators (DEMODs) can obtain symbols by performing additional processing operations on the samples. The MIMO detector (362) can perform MIMO detection operations on the symbols. The receiving processor (361) can perform processing operations on the symbols (e.g., deinterleaving, decoding). The output of the receiving processor (361) can be provided to the data sink (360) and the controller (366). For example, data can be provided to the data sink (360), and control information can be provided to the controller (366).

[0071] Meanwhile, the second communication node (300b) can transmit a signal to the first communication node (300a). The transmission processor (368) included in the second communication node (300b) can receive data (e.g., a data unit) from the data source (367) and can generate data symbol(s) by performing a processing operation on the data. The transmission processor (368) can receive control information from the controller (366) and can generate control symbol(s) by performing a processing operation on the control information. Additionally, the transmission processor (368) can generate reference symbol(s) by performing a processing operation on a reference signal.

[0072] The Tx MIMO processor (369) can perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or reference symbol(s). The output of the Tx MIMO processor (369) (e.g., a symbol stream) can be provided to modulators (MODs) included in transceivers (363a to 363t). The modulators (MODs) can perform processing operations on the symbol stream to generate modulated symbols and perform additional processing operations on the modulated symbols (e.g., analog conversion operations, amplification operations, filtering operations, up-conversion operations) to generate signals. The signals generated by the modulators (MODs) of the transceivers (363a to 363t) can be transmitted through antennas (364a to 364t).

[0073] Signals transmitted by the second communication node (300b) can be received at the antennas (314a to 314r) of the first communication node (300a). Signals received at the antennas (314a to 314r) can be provided to demodulators (DEMODs) included in the transceivers (313a to 313r). The demodulators (DEMODs) can obtain samples by performing processing operations on the signals (e.g., filtering operation, amplification operation, down-conversion operation, digital conversion operation). The demodulators (DEMODs) can obtain symbols by performing additional processing operations on the samples. The MIMO detector (320) can perform MIMO detection operations on the symbols. The receiving processor (319) can perform processing operations on the symbols (e.g., deinterleaving operation, decoding operation). The output of the receiving processor (319) can be provided to the data sink (318) and the controller (316). For example, data can be provided to the data sink (318), and control information can be provided to the controller (316).

[0074] The memories (315 and 365) may store data, control information, and / or program code. The scheduler (317) may perform scheduling operations for communication. The processors (311, 312, 319, 361, 368, 369) and controllers (316, 366) shown in FIG. 3 may be the processor (210) shown in FIG. 2 and may be used to perform the methods described in this disclosure.

[0075] FIG. 4a is a block diagram illustrating a first embodiment of a transmission path, and FIG. 4b is a block diagram illustrating a first embodiment of a reception path.

[0076] Referring to FIGS. 4a and 4b, a transmission path (410) may be implemented at a communication node that transmits a signal, and a reception path (420) may be implemented at a communication node that receives a signal. The transmission path (410) may include a channel coding and modulation block (411), an S-to-P (serial-to-parallel) block (512), an N IFFT (Inverse Fast Fourier Transform) block (413), a P-to-S (parallel-to-serial) block (414), a CP (cyclic prefix) addition block (415), and an UC (up-converter) (UC) (416). The reception path (420) may include a DC (down-converter) (421), a CP removal block (422), an S-to-P block (423), an N FFT block (424), a P-to-S block (425), and a channel decoding and demodulation block (426). Here, N can be a natural number.

[0077] Information bits in the transmission path (410) can be input to the channel coding and modulation block (411). The channel coding and modulation block (411) can perform coding operations (e.g., LDPC (low-density parity check) (LDPC) coding operations, polar coding operations, etc.) and modulation operations (e.g., QPSK (Quadrature Phase Shift Keying), QAM (Quadrature Amplitude Modulation), etc.) on the information bits. The output of the channel coding and modulation block (411) may be a sequence of modulation symbols.

[0078] The S-to-P block (412) can convert modulated symbols in the frequency domain into parallel symbol streams to generate N parallel symbol streams. N can be the IFFT size or the FFT size. The N IFFT block (413) can generate signals in the time domain by performing an IFFT operation on the N parallel symbol streams. The P-to-S block (414) can convert the output of the N IFFT block (413) (e.g., parallel signals) into a serial signal to generate a serial signal.

[0079] The CP addition block (415) can insert CP into the signal. The UC (416) can up-convert the frequency of the output of the CP addition block (415) to an RF (radio frequency) frequency. Additionally, the output of the CP addition block (415) can be filtered in the baseband before up-conversion.

[0080] A signal transmitted from the transmission path (410) can be input to the reception path (420). The operation in the reception path (420) may be the inverse operation of the operation in the transmission path (410). The DC (421) may down-convert the frequency of the received signal to a baseband frequency. The CP removal block (422) may remove CP from the signal. The output of the CP removal block (422) may be a serial signal. The S-to-P block (423) may convert the serial signal into parallel signals. The N FFT block (424) may generate N parallel signals by performing an FFT algorithm. The P-to-S block (425) may convert the parallel signals into a sequence of modulation symbols. The channel decoding and demodulation block (426) may perform a demodulation operation on the modulation symbols and perform a decoding operation on the result of the demodulation operation to restore the data.

[0081] In FIGS. 4a and 4b, Discrete Fourier Transform (DFT) and Inverse DFT (IDFT) may be used instead of FFT and IFFT. In FIGS. 4a and 4b, each of the blocks (e.g., components) may be implemented by at least one of hardware, software, or firmware. For example, in FIGS. 4a and 4b, some blocks may be implemented by software, and the remaining blocks may be implemented by hardware or a "combination of hardware and software." In FIGS. 4a and 4b, one block may be subdivided into multiple blocks, multiple blocks may be integrated into one block, some blocks may be omitted, and blocks supporting other functions may be added.

[0082] FIG. 5 is a conceptual diagram illustrating a first embodiment of a system frame in a communication system.

[0083] Referring to FIG. 5, time resources in a communication system can be divided into frames. For example, system frames can be set consecutively in the time domain of the communication system. The length of a system frame can be 10 ms (millisecond). The system frame number (SFN) can be set from #0 to #1023. In this case, 1024 system frames can be repeated in the time domain of the communication system. For example, the SFN of a system frame after system frame #1023 can be #0.

[0084] A single system frame may contain two half frames. The length of a single half frame may be 5ms. A half frame located at the beginning of the system frame may be referred to as "Half Frame #0", and a half frame located at the end of the system frame may be referred to as "Half Frame #1". A system frame may contain 10 subframes. The length of a single subframe may be 1ms. Within a single system frame, the 10 subframes may be referred to as "Subframe #0-9".

[0085] FIG. 6 is a conceptual diagram illustrating a first embodiment of a subframe in a communication system.

[0086] Referring to FIG. 6, one subframe may include n slots, where n is a natural number. Thus, one subframe may consist of one or more slots.

[0087] FIG. 7 is a conceptual diagram illustrating a first embodiment of a slot in a communication system.

[0088] Referring to FIG. 7, a slot may contain one or more symbols. A slot illustrated in FIG. 7 may contain 14 symbols. The length of the slot may vary depending on the number of symbols included in the slot and the length of the symbols. Alternatively, the length of the slot may vary depending on the numerology.

[0089] Numerals applied to physical signals and channels in a communication system may be variable. Numerals may be variable to meet various technical requirements of the communication system. In a communication system where CP (cyclic prefix) based OFDM waveform technology is applied, numerals may include subcarrier spacing and CP length (or CP type). Table 1 may be a first embodiment of a method for configuring numerals for a CP-OFDM based communication system. Depending on the frequency band in which the communication system operates, at least some of the numerals in Table 1 may be supported. Additionally, numerals not listed in Table 1 may be further supported in the communication system.

[0090] Subcarrier Spacing 15kHz 30kHz 60kHz 120kHz 240kHz 480kHz OFDM Symbol Length (μs) 66.733.316.78.34.22.1 CP Length (μs) 4.762.381.190.600.300.151 ms Number of OFDM Symbols within 142856112224448

[0091]

[0092] When the subcarrier spacing is 15 kHz (e.g., μ=0), the slot length may be 1 ms. In this case, one system frame may contain 10 slots. When the subcarrier spacing is 30 kHz (e.g., μ=1), the slot length may be 0.5 ms. In this case, one system frame may contain 20 slots.

[0093] When the subcarrier spacing is 60 kHz (e.g., μ=2), the slot length may be 0.25 ms. In this case, one system frame may contain 40 slots. When the subcarrier spacing is 120 kHz (e.g., μ=3), the slot length may be 0.125 ms. In this case, one system frame may contain 80 slots. When the subcarrier spacing is 240 kHz (e.g., μ=4), the slot length may be 0.0625 ms. In this case, one system frame may contain 160 slots.

[0094] The symbol can be set as a downlink (DL) symbol, a flexible (FL) symbol, or an uplink (UL) symbol. A slot consisting only of a DL symbol may be referred to as a "DL slot," a slot consisting only of an FL symbol may be referred to as an "FL slot," and a slot consisting only of a UL symbol may be referred to as an "UL slot."

[0095] The slot format can be semi-fixed by upper-layer signaling (e.g., RRC signaling). Information indicating the semi-fixed slot format may be included in system information, and the semi-fixed slot format can be set cell-specifically. Additionally, the semi-fixed slot format can be additionally set per terminal through terminal-specific upper-layer signaling (e.g., RRC signaling). The flexible symbols of the cell-specific slot format can be overridden as downlink symbols or uplink symbols by the terminal-specific upper-layer signaling. Furthermore, the slot format can be dynamically indicated by physical layer signaling (e.g., the SFI (slot format indicator) included in the DCI). The semi-fixed slot format can be overridden by the dynamically indicated slot format. For example, the semi-fixed flexible symbols can be overridden as downlink symbols or uplink symbols by the SFI.

[0096] The reference signal may be a CSI-RS (channel state information-reference signal), SRS (sounding reference signal), DM-RS (demodulation-reference signal), PT-RS (phase tracking-reference signal), etc. The channel may be a PBCH (physical broadcast channel), PDCCH (physical downlink control channel), PDSCH (physical downlink shared channel), PUCCH (physical uplink control channel), PUSCH (physical uplink shared channel), PSCCH (physical sidelink control channel), PSSCH (physical sidelink shared channel), etc. In the present disclosure, the control channel may mean PDCCH, PUCCH, or PSCCH, and the data channel may mean PDSCH, PUSCH, or PSSCH.

[0097] FIG. 8 is a conceptual diagram illustrating a first embodiment of a time-frequency resource in a communication system.

[0098] Referring to FIG. 8, a resource consisting of one symbol (e.g., an OFDM symbol) in the time domain and one subcarrier in the frequency domain can be defined as a "RE (resource element)." A resource consisting of one OFDM symbol in the time domain and K subcarriers in the frequency domain can be defined as a "REG (resource element group)." A REG can include K REs. A REG can be used as the basic unit of resource allocation in the frequency domain. K can be a natural number. For example, K can be 12. N can be a natural number. In the slot illustrated in FIG. 7, N can be 14. N OFDM symbols can be used as the basic unit of resource allocation in the time domain.

[0099] In the present disclosure, RB may mean a common RB (CRB). Alternatively, RB may mean a PRB or a virtual RB (VRB). In a communication system, a CRB may mean an RB that constitutes a set of consecutive RBs (e.g., a common RB grid) based on a reference frequency (e.g., point A). A carrier and / or bandwidth portion may be placed on the common RB grid. That is, the carrier and / or bandwidth portion may be composed of CRB(s). An RB or CRB constituting the bandwidth portion may be referred to as a PRB, and within the bandwidth portion, a CRB index may be appropriately converted to a PRB index.

[0100] Downlink data may be transmitted via PDSCH. A base station may transmit configuration information of the PDSCH (e.g., scheduling information) to a terminal via PDCCH. A terminal may obtain the configuration information of the PDSCH by receiving the PDCCH (e.g., downlink control information (DCI)). For example, the configuration information of the PDSCH may include a modulation coding scheme (MCS) used for transmitting and receiving the PDSCH, time resource information of the PDSCH, frequency resource information of the PDSCH, feedback resource information for the PDSCH, etc. PDSCH may refer to a radio resource where downlink data is transmitted and received. Alternatively, PDSCH may refer to the downlink data itself. PDCCH may refer to a radio resource where downlink control information (e.g., DCI) is transmitted and received. Alternatively, PDCCH may refer to the downlink control information itself.

[0101] The terminal may perform a monitoring operation for the PDCCH to receive the PDSCH transmitted from the base station. The base station may notify the terminal of configuration information for the monitoring operation of the PDCCH using a higher-layer message (e.g., a radio resource control (RRC) message). The configuration information for the monitoring operation of the PDCCH may include CORESET (control resource set) information and search space information.

[0102] CORESET information may include PDCCH DMRS (demodulation reference signal) information, PDCCH precoding information, PDCCH occasion information, etc. The PDCCH DMRS may be a DMRS used to demodulate the PDCCH. A PDCCH occasion may be an area where the PDCCH can exist. That is, a PDCCH occasion may be an area where DCI can be transmitted. A PDCCH occasion may be referred to as a PDCCH candidate. PDCCH occasion information may include time resource information and frequency resource information of the PDCCH occasion. In the time domain, the length of the PDCCH occasion may be indicated in symbol units. In the frequency domain, the size of the PDCCH occasion may be indicated in RB units (e.g., PRB (physical resource block) units or CRB (common resource block) units).

[0103] The search space information may include a CORESET ID (identifier) ​​associated with the search space, the period of PDCCH monitoring, and / or an offset. The period and offset of PDCCH monitoring may each be specified in slot units. Additionally, the search space information may further include the index of the symbol where the PDCCH monitoring operation begins.

[0104] A base station may configure a Bandwidth Part (BWP) for downlink communication. BWPs may be configured differently for each terminal. The base station may notify the terminal of the BWP configuration information using upper-layer signaling. Upper-layer signaling may refer to "transmission operations of system information" and / or "transmission operations of Radio Resource Control (RRC) messages." One or more BWPs may be configured for a single terminal. The terminal may receive BWP configuration information from the base station and identify the BWP(s) configured by the base station based on the BWP configuration information. If multiple BWPs are configured for downlink communication, the base station may activate one or more of the multiple BWPs. The base station may transmit the configuration information of the activated BWP(s) to the terminal using at least one of upper-layer signaling, a Medium Access Control (MAC) Control Element (CE), or a DCI. The base station may perform downlink communication using the activated BWP(s). The terminal can identify the activated BWP(s) by receiving configuration information of the activated BWP(s) from the base station, and can perform a downlink reception operation on the activated BWP(s).

[0105]

[0106] In accordance with the Work Item Description (WID) for 3GPP Rel-19 NR MIMO discussions, discussions are underway regarding improvements to intra-cell and inter-cell beam management. These improvements primarily target the FR2 band and single transmission / reception point (sTRP) scenarios, aiming to reduce overhead or latency while utilizing existing legacy CSI measurement and reporting configuration procedures.

[0107] To this end, UE-initiated (UEI) and event-driven (ED) beam management procedures are being discussed. The beam management methods defined up to Rel-18 consisted of network-based operations. That is, in network-driven beam management, the network (i.e., the base station) can instruct the terminal to switch to a specific beam for DL ​​reception or UL transmission. In this case, since the base station receives a measurement report from the terminal and issues instructions based on that report, the base station cannot identify the optimal beam until it receives the measurement report transmitted by the terminal.

[0108] If beam management operations are initiated at the terminal side, which can detect changes in the beam first, latency (e.g., the time required for a base station to instruct a terminal to report a measurement and to receive a measurement report from the terminal based on that instruction) and signal overhead (e.g., the overhead of the signal in which the network instructs the terminal to report a measurement) can be reduced compared to network-based beam management operations.

[0109]

[0110] Meanwhile, at 3GPP RAN 1 meetings (RAN #116 and RAN #116-bis), outlined beam reporting transmission procedures for UEI / ED beam reporting were approved.

[0111] First, the beam report transmission procedure is broadly divided into Mode A and Mode B, and an overview of the procedure for each mode is as follows.

[0112] First, Mode A is a method in which the base station dynamically schedules UCI (uplink control information) for beam reporting, and can be performed in the following three steps.

[0113] Step 1: The terminal may transmit the first UL channel requesting resources for the second UL channel to transmit a beam report. The first UL channel consists of a PUCCH (i.e., first PUCCH) containing one bit information or multi-bit information, and the PUCCH may follow the type of an existing SR (scheduling request) or a new UCI type.

[0114] Step 2: The terminal can detect a DCI format indicating a resource of the second UL channel. In this case, a new DCI format is not introduced.

[0115] Step 3: The terminal can transmit a beam report on the second UL channel. In this case, PUCCH, PUSCH, or both can be used as the second UL channel.

[0116] Mode A is a basic function of the terminal, and all terminals that support UEI / ED beam reporting must support this function.

[0117] Meanwhile, Mode B is a method of transmitting UCI from a pre-configured resource for a second UL channel, and can be performed in the following two steps.

[0118] Step 1: The terminal may transmit the first UL channel to notify that a beam report will be transmitted on the second UL channel. The first UL channel consists of a PUCCH (i.e., first PUCCH) containing one bit information or multi-bit information, and the PUCCH may follow the type of an existing SR (scheduling request) or a new UCI type.

[0119] Step 2: The terminal can transmit a beam report on the second UL channel. As with Mode A, PUCCH, PUSCH, or both can be used as the second UL channel.

[0120] In Mode B, the notification in Step 1 and the beam report in Step 2 are transmitted as separate report instances, and it is not determined whether the terminal receives confirmation information in response to each step in Mode A and Mode B.

[0121] In addition, cross-CC (component carrier) beam reporting can be supported in both Mode A and Mode B in the above procedures.

[0122]

[0123] Meanwhile, the following events are being discussed as triggering the aforementioned UEI / ED beam reporting.

[0124] -Event-1: The quality of the current beam (e.g., L1-RSRP, etc.) falls below a specific threshold.

[0125] -Event-2: The quality of at least one new beam is improved by a threshold amount compared to the current beam.

[0126] -Event-3: New beam quality exceeds a specific threshold.

[0127] -Event-4: Current beam quality drops below threshold 1, and at least one new beam quality rises above threshold 2.

[0128] -Event-5: The absolute difference between the quality of the current beam and the quality of at least one new beam becomes smaller than a specific threshold.

[0129] -Event-6: The current beam is not included in the top K (>1) beams among the beams configured for measurement and reporting.

[0130] -Event-7: The quality of at least one new beam (L1-RSRP, etc.) is improved by a specific threshold compared to the RS derived from the active TCI state with the Mth best quality.

[0131] -Event-8: The quality of M (>1) new beams (L1-RSRP, etc.) has improved by a specific threshold compared to the current beam.

[0132] -Event-9: The quality of at least one new beam (L1-RSRP, etc.) is improved by a specific threshold compared to the configured reference RS (SSB or CSI-RS possible).

[0133]

[0134] As described above, for UEI / ED beam reporting operations, a process of first transmitting information from the terminal to the base station (Step 1) is required in all modes. In the case of Mode A, where resources for beam reporting are not pre-allocated, the terminal can request resources for beam reporting from the base station. In the case of Mode B, where resources for beam reporting are pre-allocated, the terminal can notify the base station that it intends to use the pre-allocated resources for beam reporting. In Step 1, the terminal can transmit the relevant information to the base station via PUCCH, and the information may consist of 1-bit information or multi-bit information. If the information consists of 1 bit, it may simply be information requesting resources from the base station or information notifying the fact that pre-allocated resources are being used. On the other hand, if the information consists of multi-bit information, it may be used for various purposes in addition to information requesting resources or notifying the fact that pre-allocated resources are being used.

[0135]

[0136] FIG. 9 is a flowchart for explaining Mode A operation to which embodiments of the present disclosure are applied.

[0137] Referring to FIG. 9, the terminal can detect at least one event (S910). In this case, the terminal can detect at least one event among the previously described event(s) (e.g., Event-1 to Event-9). When at least one event is detected, the terminal requests a resource for beam reporting via the first UL channel (i.e., first PUCCH) (S920), and the base station that received the first UL channel may indicate a resource for the second UL channel to be used by the terminal to transmit the beam reporting via the DCI (S930). Subsequently, the terminal can transmit the second UL channel including the beam reporting using the said resource (S940).

[0138] FIG. 10 is a flowchart illustrating a Mode B operation to which embodiments of the present disclosure are applied.

[0139] Referring to FIG. 10, the terminal can detect at least one event (S1010). In this case, the terminal can detect at least one event among the previously described event(s) (e.g., Event-1 to Event-9). When at least one event is detected, the terminal can notify the base station that it is transmitting the second UL channel(s) using a pre-configured resource through the first UL channel (i.e., first PUCCH) (S1020). Subsequently, the terminal can transmit the second UL channel(s), including a beam report, to the base station using the pre-configured resource (S1040).

[0140] In this case, the terminal may transmit the second UL channel(s) after receiving an acknowledgment message (e.g., an ACK (acknowledgement) message or a notification message consisting of a 1-bit indicator) (i.e., S1330 of FIG. 13) indicating that the first PUCCH has been received from the base station. Alternatively, the terminal may transmit the second UL channel(s) at a slot or symbol after a predetermined offset from the time point associated with the transmission of the first PUCCH (e.g., the slot or symbol in which the first PUCCH (e.g., the last symbol constituting the first PUCCH) was transmitted) without receiving an acknowledgment message for the first PUCCH from the base station. For example, if it is not confirmed that the first PUCCH was not normally received by the base station until the predetermined offset has elapsed from the time point associated with the transmission of the first PUCCH, the terminal may transmit the second UL channel(s) at a slot or symbol after a predetermined offset from the time point associated with the transmission of the first PUCCH. In this case, the offset may be set from the base station to the terminal in units of symbols, subslots, slots, subframes, or absolute time, or may be predefined in the technical specifications. Meanwhile, since there may be cases where the terminal does not receive the acknowledgment message even though the base station has transmitted the acknowledgment message, the base station may transmit the acknowledgment message one or more times.

[0141]

[0142] In the above-described UEI / ED beam management operation (hereinafter referred to as UEI BM operation), the first UL channel (i.e., first PUCCH) is a short control signal that can be transmitted very frequently. Therefore, if the terminal frequently detects events due to changes in channel quality, the network may become overloaded due to the frequent occurrence of UL control signals. Furthermore, the first PUCCH transmitted unnecessarily frequently can lead to the waste of UL resources and increased power consumption by the terminal. To prevent this, the 3GPP RAN (radio access network) working group 1 (WG1) introduced a mechanism to limit the transmission of the first PUCCH. The basic idea of ​​this mechanism is to introduce a prohibit timer or time interval to prevent the terminal from transmitting the first PUCCH too frequently in succession. This was designed to be applicable in both operation modes (Mode-A and Mode-B).

[0143] In relation to Mode-A and / or Mode-B in the beam report transmission procedure for UEI / ED beam reporting, the following additional considerations may be made regarding the transmission of the first PUCCH.

[0144] - UCI multiplexing / dropping / prioritization rules

[0145] - Conditions for First PUCCH transmission

[0146] - Whether a PUCCH resource in the First PUCCH channel can be associated with multiple CSI report configurations for UEI / ED beam reporting from one or more CCs

[0147] - Whether to re-transmit the First PUCCH channel and the method of re-transmitting the First PUCCH channel

[0148] - Whether to apply a prohibit timer or maximum (re)transmission count to the First PUCCH channel and how to apply it

[0149] Regarding the beam report transmission procedure for UEI / ED beam reporting on CSI reporting settings, at least one of the following candidates may be down-selected.

[0150] Candidate #1: Introduce a ban timer for Mode A and / or Mode B

[0151] Option-1A) If the triggering event associated with the CSI reporting setting is determined by the same triggering beam(s) as the last transmitted PUCCH, and the prohibition timer is not active, the terminal may transmit the first UL channel (i.e., first PUCCH). The terminal may start the prohibition timer at the first symbol after the transmission of the second UL channel (i.e., PUSCH) has ended.

[0152] Option-1B) When a triggering event associated with the CSI reporting setting is determined, and the prohibit timer is not running, the terminal may transmit the first PUCCH. The terminal may start the prohibit timer at the first symbol after the transmission of the first PUCCH has ended.

[0153] Candidate #2: Introduce a prohibited time interval for Mode A and / or Mode B

[0154] Option-2A) For the first PUCCH transmission occasion, if there is a transmission of another second UL channel (PUSCH) corresponding to a beam report determined by the same triggering beam(s) as the first PUCCH within a configurable time interval prior to the first PUCCH transmission occasion, the terminal must not transmit the first PUCCH.

[0155] Option-2B) For a first PUCCH transmission opportunity, if another first PUCCH transmission exists within a configurable time interval prior to the said PUCCH transmission opportunity, the terminal must not transmit the first PUCCH.

[0156]

[0157] The above-described Mode A and Mode B can be summarized as follows.

[0158] Mode A: A terminal transmits the first PUCCH to a base station, and the base station that receives the first PUCCH can allocate resources for the second UL channel through DCI scheduling. That is, the terminal can transmit the second UL channel according to the network's explicit schedule.

[0159] Mode B: Since the terminal has a pre-configured UL resource, the terminal can autonomously transmit a second UL channel without scheduling by the base station after transmitting the first PUCCH to the base station. In this case, the base station can anticipate whether the second UL channel will be received from the pre-configured UL resource based on the first PUCCH transmitted by the terminal.

[0160] Mode A requires the base station's schedule information (DCI), so the time required to transmit the second UL channel may be long, and if the transmission of the first PUCCH fails, the second UL channel is not transmitted, which may result in a beam reporting failure. On the other hand, in Mode B, since the terminal transmits the second UL channel even if the base station does not receive the first PUCCH, unexpected UL signal interference may occur from the network's perspective.

[0161] Accordingly, in the first PUCCH transmission operation, matters related to the restriction of first PUCCH transmission may be considered, such as (1) whether to allow consecutive first PUCCH transmission attempts - whether to allow the terminal to immediately attempt to re-transmit the first PUCCH when the first PUCCH is not successfully received, and (2) whether to restrict additional beam reporting after a successful beam report - whether to prohibit the transmission of another first PUCCH for a time interval after the beam report is completed.

[0162] The aforementioned Option-1B / 2B are options focused on the former aspect (whether to allow consecutive first PUCCH transmission attempts), and Option-1A / 2A can be viewed as a proposal focused on the latter aspect (whether to restrict additional beam reporting after a successful beam report). Option-1A / 1B are options that utilize a prohibit timer to ban transmission for a certain period, and Option-2A / 2B are options that introduce a prohibit time interval. The operation or application conditions of the prohibit timer (or prohibit time interval) may be attributed to a specific CSI reporting configuration (CSI-ReportConfigID), and even for triggering events by the same triggering beam(s), if they are mapped to different CSI reporting configurations, the prohibit timer or prohibit time interval may be applied independently.

[0163]

[0164] In this disclosure, methods are proposed to effectively control first PUCCH transmission for purposes such as UL resource efficiency, reporting reliability, and terminal power consumption optimization in UEI / ED beam reporting operations.

[0165]

[0166] First, it is necessary to clearly define the operation for each Option.

[0167] Option-1A (PUSCH-based prohibit timer): If a new triggering event is based on the same triggering beam(s) as the first PUCCH transmitted immediately prior (i.e., the current beam and / or the same new beam) (i.e., the "same triggering beam" condition), the terminal may transmit the first PUCCH if the prohibit timer is not currently active. At this time, the terminal starts the prohibit timer at a point in time after the transmission of the first PUCCH (e.g., the first symbol after the transmission of the first PUCCH has ended), and while the prohibit timer is active, the transmission of a new first PUCCH by the same triggering beam(s) may be prohibited. That is, the transmission of a new first PUCCH may be allowed after the previous beam reporting procedure (transmission of the first UL channel (first PUCCH) and the second UL channel) is completed. In Option-1A, a prohibition period is set based on whether the second UL channel was actually transmitted to the base station after the terminal transmitted the first PUCCH (i.e., in the case of Mode A, whether the network received the first PUCCH and scheduled resources for the second UL channel), so the prohibition timer can operate only for successful beam reports. Since the prohibition timer is applied separately per beam according to the "same triggering beam" condition, for a triggering event caused by a triggering beam(s) different from the triggering beam(s) of the first PUCCH transmitted immediately before, the terminal can transmit the first PUCCH regardless of the prohibition timer.

[0168] Option-1B (PUCCH-based prohibit timer): When a new triggering event occurs, if the prohibit timer is not active, the terminal transmits the first PUCCH and may start the prohibit timer at a point after the transmission of the first PUCCH (i.e., the first symbol after the transmission of the first PUCCH has ended). During the operation of the prohibit timer, the transmission of the first PUCCH is prohibited by any new triggering event. Unlike Option-1A, the prohibition period by the prohibit timer can always be set immediately after the transmission of the first PUCCH (i.e., at the first symbol after the transmission of the first PUCCH), regardless of whether the second UL channel is transmitted. In other words, Option-1B treats the first PUCCH attempt itself as a cycle and corresponds to a method that prohibits additional attempts to transmit the first PUCCH for a certain period of time, regardless of whether the transmission of the first PUCCH is successful. This option has the advantage of being simple to implement and can suppress the transmission of the first PUCCH unnecessarily frequently, but it may have the disadvantage of delaying retries if the transmission attempt of the first PUCCH fails. In Option-1B, unlike Option-1A, specific beam conditions (conditions that a new triggering event must be based on the same triggering beam(s) as the first PUCCH transmitted immediately prior (e.g., the same current beam and / or the same new beam)) are not applied, so the prohibit timer operates as a global timer, and the transmission of the first PUCCH is prohibited for any new triggering event based on any beam before the prohibit timer expires.

[0169] Option-2A (PUSCH-based Bound Time Interval): The terminal checks for a set Bound Time Interval (e.g., X ms) from the scheduled first PUCCH transmission opportunity and may not transmit the first PUCCH if there has been a transmission of a second UL channel for the same current beam and / or the same new beam within that Bound Time Interval. Option-2A corresponds to a method that prohibits additional beam reporting based on the same current beam and / or the same new beam within the set time interval if a recent beam reporting has been completed. In this case, if the previous beam reporting was due to a triggering beam(s) different from the first PUCCH resulting from the current triggering event, the terminal may immediately transmit the first PUCCH. Option-2A is similar to Option-1A in terms of effect, but corresponds to a method that applies the Bound Interval using a rule instead of a timer. The network may set the Bound Time Interval X to the terminal via RRC signaling, and the terminal may decide whether to transmit the first PUCCH based on past transmission history. This method sets a prohibition time interval based on the transmission time of the second UL channel, so it can achieve the effect of restricting the transmission of the first PUCCH for a certain period after the beam report is successfully completed.

[0170] Option-2B (PUCCH-based prohibition time interval): The terminal checks for a set prohibition time interval (e.g., X ms) from the scheduled first PUCCH transmission opportunity and may not transmit a new first PUCCH within that prohibition time interval. In other words, Option-2B corresponds to a method that prohibits the terminal from transmitting additional first PUCCHs within a set prohibition time interval (e.g., X ms) from the time of the last first PUCCH transmission. The network can set the prohibition time interval X for the terminal via RRC signaling, and the terminal can determine whether to transmit the first PUCCH based on the time of the last first PUCCH transmission. Option-2B may be similar to Option-1B in that it applies a time interval limit to all first PUCCH transmissions. However, there is a difference in that Option-1B is a timer-based method, whereas Option-2B is a rule-based method. In this method, even if the first PUCCH transmission attempt fails, a retry of the first PUCCH transmission is possible only after the set prohibition time interval has ended, so it may be a conservative method that strictly limits the transmission frequency rather than easily allowing retransmission.

[0171] In summary, the Option-1 family consists of methods that control the first PUCCH transmission using an internal terminal timer called a prohibition timer, while the Option-2 family consists of methods that control the first PUCCH transmission by applying a prohibition time interval set by a conditional rule. However, the actual operation may be similar in each Option pair (1A-2A, 1B-2B). The advantages, disadvantages, and differences of each option can be summarized as follows, based on the allowance of consecutive first PUCCH transmission attempts, suppression of unnecessary triggers after reporting, RRC signaling and implementation complexity, and the presence or absence of network feedback.

[0172] Aspect of allowing consecutive first PUCCH transmission attempts: Option-1A has the advantage that if the base station does not respond (e.g., resource scheduling for the second UL channel) after the first PUCCH transmission, the terminal can immediately retry the first PUCCH transmission. For example, in Mode A, if the base station does not receive the first PUCCH, the terminal cannot transmit the second UL channel and the prohibition timer does not start, so the terminal can retry the transmission of the first PUCCH at the next PUCCH transmission opportunity. On the other hand, in Option-1B / 2B, a prohibition period is set after the transmission of the first PUCCH regardless of whether the first PUCCH was successfully received by the base station, so the retry of the first PUCCH transmission may be delayed. In particular, in Mode B, the terminal must decide on its own to retry the first PUCCH transmission even without feedback (e.g., ACK information) from the base station, but since this operation is difficult in Option-1B / 2B, there may be reliability issues.

[0173] Suppression of unnecessary triggers after reporting: If a terminal transmits another first PUCCH immediately after the first PUCCH transmission is successful and a beam report is transmitted, without giving the base station time to reflect beam updates, etc., problems such as duplicate reporting or resource waste may occur. Option-1A and Option-2A suppress the transmission of a new first PUCCH for a certain period after the second UL channel is transmitted, thereby giving the base station time to perform beam synchronization / compensation and reducing the terminal's transmission resource waste. Meanwhile, in Option-1B / 2B, the prohibition timer starts immediately after the transmission of the first PUCCH, but if the prohibition timer operates until the first PUCCH is successfully received by the base station and the transmission of the second UL channel proceeds, a similar suppression effect can be achieved. However, in Option-1B / 2B, the prohibition period after the successful transmission of the second UL channel may not be sufficient.

[0174] RRC Signaling and Implementation Complexity: In Option-1A / 1B, the base station can set the value of the prohibit timer to the terminal via upper-layer signaling (e.g., MAC-CE or RRC signaling). In Option-2A / 2B as well, since the base station must set the length X of the prohibit time interval to the terminal via RRC signaling, the signaling burden of Option-1A / 1B and Option-2A / 2B may be at the same level. However, if the application of the "same triggering beam(s)" condition is to be controllable in Option-1A and Option-2A, additional information such as whether the condition is applied or UE capability (beam-specific application) may be required in the RRC signaling. Additionally, instead of providing a single prohibit timer value or prohibit time interval value, a method of providing multiple prohibit timer values ​​or multiple prohibit time interval values ​​may be considered.

[0175] Difference in the presence or absence of network feedback: In Mode A, the terminal can verify whether the transmission of the first PUCCH was successful by receiving scheduling information (i.e., DCI) from the device station after the transmission of the first PUCCH. In Mode B, since there is no scheduling information from the base station, it is difficult for the terminal to verify whether the base station has received the first PUCCH. If Option-1A / 2A is applied in Mode B, a blackout period is established after the terminal transmits the second UL channel; therefore, even if the base station fails to receive the first PUCCH normally, the terminal cannot transmit the first PUCCH during the blackout period. Consequently, if Option-1A / 2A is applied in Mode B, a retry of the first PUCCH transmission may be delayed if the transmission fails. On the other hand, if Option-1B / 2B is applied in Mode B, the terminal can retry the transmission of the first PUCCH once the blackout timer set after the transmission of the first PUCCH expires.

[0176]

[0177] In the following, methods are proposed that take into account the trade-off between the advantages and disadvantages of the aforementioned Option-1A / 1B and Option-2A / 2B (i.e., the trade-off between transmission reliability and overhead). The methods proposed below also take into account the differences in requirements between Mode A and Mode B. The following methods may be considered.

[0178] Dual Timer Application: A dual timer method may be considered as a compromise approach, applying a first prohibition timer and a second prohibition timer separately. The first and second prohibition timers may be set to different values. For example, the first prohibition timer may be set to a value smaller (or larger) than the second prohibition timer. That is, a method may be applied where a short timer (i.e., a first prohibition timer set to a small value) is used immediately after the first PUCCH transmission, and a long timer (i.e., a second prohibition timer set to a large value) is used immediately after the PUSCH transmission. In this case, the settings for the first and second prohibition timers can be configured via upper-layer signaling. For example, in Mode A, the first prohibition timer may be set to a very short value (or zero or close to zero) to allow for substantially consecutive first PUCCH transmissions, and in Mode B, a first prohibition timer set to a short value may also be utilized to allow for consecutive first PUCCH transmissions. Meanwhile, the second prohibition timer may suppress the first PUCCH transmission during the prohibition period after the beam report is successfully completed.

[0179] Same Trigger Beam Condition: It is necessary to decide whether to maintain the "same trigger beam" condition of Option-1A / 2A. If the condition is removed, the prohibition mechanism is applied globally to all beams, simplifying implementation, but reporting may be delayed if events occur consecutively from multiple different beams. On the other hand, if the "same trigger beam" condition is maintained, implementation becomes more complex as the terminal must determine the prohibition status on a per-beam basis, but rapid beam switching may be possible as reporting to other beams can be done immediately.

[0180] Differential application of Mode A and Mode B: Considering the feedback differences between the two modes, a separate retransmission procedure for Mode B only may be discussed. For example, in Mode B, instead of ending after sending the first PUCCH once, it may be allowed to be transmitted repeatedly, during which time a prohibition timer is not applied, or a method may be used where a prohibition interval is set only after all transmission attempts on the second UL channel have ended. Alternatively, the network may transmit feedback confirming receipt of the first PUCCH (e.g., ACK or NACK information) to the terminal exclusively for Mode B. It is possible to decide whether to separate these modes or to group them into a single rule while setting parameters (e.g., prohibition time) differently depending on the mode.

[0181] RRC Signaling Simplification: Depending on the applied method or option, the base station may need to inform the terminal of the prohibition timer setting value or the prohibition time interval. To minimize this, existing parameters (e.g., SR prohibit timer) can be reused. Alternatively, Mode A and Mode B can use the same value, or only one PUCCH-ProhibitTimer value can be transmitted via RRC signaling, allowing the terminal to decide which prohibition timer setting value to apply for each mode based on that single PUCCH-ProhibitTimer value. Furthermore, if a dual timer is used, it may be inefficient as both values ​​must be signaled; therefore, a single parameter can be defined to operate appropriately in both modes. For example, it can operate as Option-1A if the value is below a certain threshold and as Option-1B if the value is above that threshold. As another example, if the parameter value is not set (i.e., default operation), it can operate as Option-1A (to a pre-set specific value), and if the parameter value is set, it can operate as Option-1B to the set specific value.

[0182] Additional network control: In addition to simple timers / rules, a method for the base station to control the terminal's beam reporting frequency may be considered. For example, the base station may provide control information to the terminal to increase or decrease the beam reporting period based on the current cell load. Based on such control information, the terminal may act by extending (or stopping) the prohibition timer or increasing (or decreasing) the threshold.

[0183]

[0184] Based on the above methods, specific embodiments as follows may be considered.

[0185] Dual Timer Application: Two-stage prohibition periods can be operated following the transmission of the First PUCCH. That is, it can operate in a dual-timer manner (applied separately as a First Prohibition Timer and a Second Prohibition Timer), and the First and Second Prohibition Timers can be set to different values. For example, the First Prohibition Timer can be shorter (longer) than the Second Prohibition Timer. In other words, the first acts as a short retransmission timer, starting immediately after the transmission of the First PUCCH and operating for only a very short time (e.g., a few slot intervals). If the same event persists and the Second PUCCH is not delivered before this timer expires, it allows the UE to retransmit the First PUCCH. The second timer starts after the transmission of the Second PUCCH is complete and sets a longer prohibition period (e.g., tens of milliseconds), thereby suppressing unnecessary additional triggering events for already reported beams. Parameters can be added to the RRC signaling to allow the two timer values ​​to be set separately, or the two timers can be operated proportionally using a single parameter. This method combines the advantages of Option-1A and 1B. In Mode A, the first prohibit timer is set to 0 to allow immediate first PUCCH transmission (i.e., first PUCCH transmission is allowed without a prohibit period), and in Mode B, the first prohibit timer is set to a small value to allow continuous transmission of the first PUCCH (e.g., one or two consecutive first PUCCH transmissions).

[0186] Dynamic prohibit timer control (success / failure based): The terminal's prohibit timer operation can be performed dynamically depending on whether the base station provides feedback regarding the first PUCCH. For example, in a Mode A environment, the terminal can utilize scheduling information for the second UL channel (e.g., DCI) received from the base station as success feedback for the first PUCCH. For example, if the DCI is not received within a certain time after the first PUCCH is transmitted, the terminal determines that the first PUCCH was not successfully received by the base station and can retransmit the first PUCCH immediately without starting the prohibit timer. On the other hand, if the DCI is received from the base station (e.g., at the first symbol after the reception of the DCI has ended), the prohibit timer can be started to stop the transmission of a new first PUCCH for a certain period thereafter. In the case of Mode B, since there is no explicit feedback, the terminal does not start the prohibit timer until the transmission of the second UL channel, and starts the prohibit timer after the transmission of the second UL channel ends (at the first symbol after the transmission of the second UL channel ends), and thereafter can perform a PUCCH trigger check at short intervals. If the network sends a message that has already compensated the beam (e.g., a TCI State update RRC message), the timer is terminated normally, and if there is no such feedback, the terminal can review the trigger again through another mechanism (e.g., re-satisfaction of a threshold) after the prohibit timer expires. That is, the operation period can be adjusted in real time to a long timer upon success and a short timer upon suspected failure, allowing for quick retries when necessary.

[0187] Allowing Repeated PUCCH Transmission (in Mode B): To improve the Mode B scenario, repeated transmission of the first PUCCH may be allowed. Specifically, when the terminal detects a triggering event, it may repeatedly transmit the same 1-bit signal (or indicator) over N consecutive first PUCCH opportunities, rather than relying solely on a single first PUCCH resource. For example, if the first PUCCH is repeatedly transmitted up to three times at intervals of two slots, the base station may proceed with subsequent procedures (waiting for reception of the second UL channel in Mode B) if it receives even one of those first PUCCHs. To support this, the base station may set a parameter for the number of repeated transmissions for the terminal. The terminal may start a blackout timer after the last repetition of the PUCCH has been transmitted. In this case, to increase UL resource efficiency during the repetition process, different encoding or power control may be applied when sending the same 1-bit to enable soft combining of multiple PUCCHs, or the network may be designed to recognize this and detect summation upon multiple receptions. Consequently, even during the ban period, retransmission is performed internally, but externally it can still be treated as a single reporting cycle.

[0188] Threshold-based Ignore Action Trigger: Even if the prohibition timer is active or within the prohibition time interval, if a particularly critical new event occurs, the terminal may ignore the prohibition timer or prohibition time interval and transmit the first PUCCH. For example, if a new beam of significantly higher quality (e.g., +X dB or more) than the current beam is detected during the prohibition period, or if a critical impact on the terminal's communication (e.g., the current beam is nearly cut off) is predicted, the terminal may ignore the current prohibition timer or prohibition time interval and transmit the first PUCCH according to internal rules. These override conditions can be defined by hysteresis values ​​or multiple thresholds through upper-layer signaling. For example, the prohibition timer can be interpreted in conjunction with multiple thresholds. The terminal may apply general prohibition rules to low-importance events and transmit the first PUCCH with an 'urgent' flag set for events exceeding a specific (e.g., a second) threshold. When the base station receives the first PUCCH, it checks the corresponding flag (or a separate indication bit) to recognize a situation requiring beam reporting due to an urgent event and can promptly process the beam reporting.

[0189] Improvements to UE Beam Report Priority and Collision Management: In multi-event situations, it is necessary to consider cases where first PUCCHs collide or priorities are ambiguous. For example, if UEI / ED beam reports corresponding to two different CSI reporting configurations are triggered nearly simultaneously, causing first PUCCH resources to overlap, the terminal can select and transmit one first PUCCH based on priority, or transmit them simultaneously (via methods such as multiplexing). In this case, the lower-priority report can be automatically deferred by combining it with a prohibit timer mechanism. Specifically, priorities can be assigned to each beam report within the terminal (e.g., Event-2 > Event-1 > Event-7, or the order of the configured CSI-ReportConfigID), and if a higher-priority beam report preempts the first PUCCH, a prohibit timer can be applied to the lower-priority beam report to delay the transmission of the first PUCCH to the next opportunity. In this case, the terminal can minimize the delay by setting the prohibit timer to a value shorter than usual. Additionally, if multiplexing of first PUCCHs is required, a method of transmitting multiple bits of instructions within a single PUCCH can also be considered. In this case, a rule that operates a separate prohibition timer for each instruction, or a rule that operates a single prohibition timer for multiplexed instructions, may be applied.

[0190]

[0191] FIGS. 11 to 13 are flowcharts for explaining UEI / ED beam management operations according to the present disclosure.

[0192] Referring to FIG. 11, the terminal can detect a first event (S1110) and transmit a first UL channel (i.e., first PUCCH) notifying the detected first event to the base station (S1120).

[0193] The terminal may start a first prohibit timer at a first point in time after the transmission of the first UL channel (S1130). For example, the first point in time may be the first symbol at which the transmission of the first UL channel ends. Or, the first point in time may be the last symbol at which the first UL channel is transmitted. Meanwhile, if the terminal performs a UEI / ED beam reporting operation according to Mode B, the first UL channel may be transmitted repeatedly according to a predetermined number of repeated transmissions. In this case, the first prohibit timer may start at a point in time corresponding to the first symbol at which the transmission of the last repetition of the first UL channel ends or the last symbol at which the last repetition is transmitted.

[0194] A prohibited section may be set by the above-mentioned first prohibited timer, and this may be referred to as the 'first prohibited section' to distinguish it from the prohibited section set by the second prohibited timer to be described later.

[0195] After transmitting the first UL channel, the terminal may transmit a second UL channel (e.g., PUSCH) including a beam report according to the first event to the base station using a UL resource allocated via DCI from the base station (in the case of Mode A) or a UL resource pre-allocated from the base station (in the case of Mode B) (S1140).

[0196] Meanwhile, although FIG. 11 shows that the second UL channel is transmitted after the end of the first prohibition period (i.e., after the expiration of the first prohibition timer), the second UL channel can be transmitted even before the end of the first prohibition period. That is, the transmission of the second UL channel can be performed independently of the first prohibition period.

[0197] The terminal may start a second prohibition timer at a second point in time after the transmission of the second UL channel (S1150). For example, the second point in time may be the first symbol at which the transmission of the second UL channel ends. Or, the second point in time may be the last symbol at which the second UL channel is transmitted.

[0198] A prohibition period may be set by the above-mentioned second prohibition timer, and this may be referred to as a 'second prohibition period' to distinguish it from the second prohibition period set by the aforementioned first prohibition timer.

[0199] The first prohibition timer and the second prohibition timer may be set to different values. For example, the first prohibition timer may be set to a value smaller than the second prohibition timer. For the simplification of RRC signaling, the first prohibition timer and the second prohibition timer may each be set to a single parameter signaled from the base station and a value derived from the single parameter, or each may be set to values ​​derived from the single parameter. The parameter signaled from the base station may be an SR (scheduling request) prohibition timer value or a PUCCH (physical uplink control channel) prohibition timer value defined separately from the SR prohibition timer.

[0200] When the terminal performs a UEI / ED beam reporting operation according to Mode A, the first prohibition timer may be set to a value smaller than the first prohibition timer when the terminal performs a UEI / ED beam reporting operation according to Mode B.

[0201] More specifically, when the terminal performs a UEI / ED beam reporting operation according to Mode A, the first prohibition timer is set to 0, and when the terminal performs a UEI / ED beam reporting operation according to Mode B, the first prohibition timer may be set to a value greater than 0.

[0202] FIG. 11 is intended to explain that, in accordance with an embodiment of the present disclosure, two prohibition periods can be set by two timers, excluding a situation in which a second event different from the first event is detected in a prohibition period (a first prohibition period or a second prohibition period). Below, a specific situation in which the first PUCCH transmission according to the second event is prohibited when the second event is detected in each prohibition period is described.

[0203] Referring to FIG. 12, a second event different from the first event may be detected in a first prohibition period set by a first prohibition timer (S1131). Similar to Option-1A, when the first prohibition timer is in operation and the beam(s) triggering the first event and the beam(s) triggering the second event are the same, the transmission of an additional first UL channel (i.e., first PUCCH) of the terminal announcing the second event may be prohibited (S1132). Alternatively, similar to Option-1B, when the first prohibition timer is in operation, the transmission of an additional first UL channel (i.e., first PUCCH) of the terminal announcing the second event may be prohibited regardless of whether the beam(s) triggering the first event and the beam(s) triggering the second event are the same. Meanwhile, in FIG. 12, the first event and the second event are Event-2 for UEI / ED beam reporting operation, and the beam(s) triggering the first event and the beam(s) triggering the second event may be the same current beam and / or the same new beam.

[0204] Referring to FIG. 13, a second event different from the first event may be detected in a second prohibition period set by a second prohibition timer (S1151). Since the second prohibition period is a period that prohibits additional first PUCCH transmission after the transmission of the second UL channel is completed, additional transmission of the first UL channel (i.e., first PUCCH) of the terminal announcing the second event may be prohibited (S1152).

[0205]

[0206] The information(s) described in this disclosure may apply not only to Mode A and Mode B described in this disclosure but also to Mode(s) to be defined later. The information(s) described in this disclosure may be applied differently depending on the Mode.

[0207] The information(s) or operations(s) described in this disclosure may be applied in the same way to the initial transmission and retransmission of the first PUCCH (or second UL channel), or may be applied in different ways to the initial transmission and retransmission.

[0208] In the above embodiments, the first PUCCH may be transmitted in only one CC. Alternatively, if multiple CCs exist, the first PUCCH may be transmitted equally in all CCs or in only a specific CC among the multiple CCs.

[0209] The information(s) described above may be transmitted via MAC-CE signaling, UCI, and / or RRC signaling (and / or another channel).

[0210] In the present disclosure, the statement that a terminal-led / event-based beam management operation is performed can be interpreted to mean that the terminal transmits a signaling instructing a base station to perform a terminal-led / event-based beam management operation.

[0211] In the present disclosure, the term "terminal-led / event-based beam management operation is stopped" can be interpreted to mean that the terminal transmits a signaling to the base station indicating that it does not perform a terminal-led / event-based beam management operation, or performs an existing base station-led beam management operation.

[0212] The methods proposed in this disclosure may be applied to additionally defined event(s) in addition to the currently defined events. The methods proposed in this disclosure may be applied to intra-cell beam management and inter-cell beam management. The methods proposed in this disclosure may be similarly applied to multi-TRP (mTRP) operations.

[0213]

[0214] The operation of the method according to the present disclosure can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device in which information that can be read by a computer system is stored. Additionally, a computer-readable recording medium may be distributed across networked computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.

[0215] In addition, computer-readable recording media may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Program instructions may include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc.

[0216] Some aspects of the present disclosure have been described in the context of a device, but may also be described according to a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described according to a corresponding block or item or a feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one of the most important method steps may be performed by such a device.

[0217] A programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described in this disclosure. A field-programmable gate array may operate with a microprocessor to perform one of the methods described in this disclosure. Generally, it is preferable that the methods be performed by some hardware device.

[0218] Although the present disclosure has been described with reference to preferred embodiments, those skilled in the art will understand that various modifications and changes can be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the following claims.

Claims

1. In the method of the terminal, When a first event is detected, a step of transmitting a first uplink (UL) channel to a base station to notify the first event; and The method includes the step of transmitting a second UL channel, including a beam report according to the first event, to the base station using a UL resource allocated from the base station via DCI (downlink control information) or a UL resource pre-allocated from the base station. The terminal starts a first prohibit timer at a first time point after the transmission of the first UL channel and starts a second prohibit timer at a second time point after the transmission of the second UL channel, and during the period in which the first prohibit timer is in operation and during the period in which the second prohibit timer is in operation, additional transmission of the first UL channel notifying a detected second event is prohibited. method.

2. In Claim 1, The transmission of the additional first UL channel is prohibited when the beam(s) triggering the first event and the beam(s) triggering the second event are the same, method.

3. In Claim 2, The first event and the second event are Event-2 for UEI / ED (UE-initiated / Event-driven) beam reporting operation, and the beam(s) triggering the first event and the beam(s) triggering the second event are the same current beam and / or the same new beam, method.

4. In Claim 1, The first prohibition timer is set to a value smaller than the second prohibition timer, method.

5. In Claim 4, The first prohibition timer and the second prohibition timer are each set to a parameter signaled from the base station and a value derived by said parameter, or each set to values ​​derived by said parameter. method.

6. In Claim 5, The parameter signaled from the base station is an SR (scheduling request) prohibition timer value or a PUCCH (physical uplink control channel) prohibition timer value defined separately from the SR prohibition timer, method.

7. In Claim 1, When the above terminal performs a UEI / ED beam reporting operation according to Mode B, the first UL channel is repeatedly transmitted according to a predetermined number of repeated transmissions, and the first prohibition timer starts after the last repetition of the first channel is transmitted. method.

8. In Claim 1, The above first point in time is the point in time corresponding to the first symbol after the transmission of the above first UL channel has ended, method.

9. In Claim 1, The above first point in time is a point in time corresponding to the first symbol after the reception of the DCI has ended, method.

10. In Claim 1, The above second point in time is the point in time corresponding to the first symbol after the transmission of the above second UL channel has ended, method.

11. In Claim 1, The first prohibition timer when the terminal performs a UEI / ED beam reporting operation according to Mode A is set to a value smaller than the first prohibition timer when the terminal performs a UEI / ED beam reporting operation according to Mode B. method.

12. In Claim 1, When the terminal performs a UEI / ED beam reporting operation according to Mode A, the first prohibition timer is set to 0, and when the terminal performs a UEI / ED beam reporting operation according to Mode B, the first prohibition timer is set to a value greater than 0. method.

13. A terminal comprising at least one processor, The above at least one processor is the terminal: When a first event is detected, a step of transmitting a first uplink (UL) channel to a base station to notify the first event; and Performing the step of transmitting a second UL channel, including a beam report according to the first event, to the base station using a UL resource allocated from the base station via DCI (downlink control information) or a UL resource pre-allocated from the base station, and The terminal starts a first prohibit timer at a first time point after the transmission of the first UL channel and starts a second prohibit timer at a second time point after the transmission of the second UL channel, and during the period in which the first prohibit timer operates and the period in which the second prohibit timer operates, additional transmission of the first UL channel notifying a detected second event is prohibited. Terminal.

14. In Claim 13, The transmission of the additional first UL channel is prohibited when the beam(s) triggering the first event and the beam(s) triggering the second event are the same, Terminal.

15. In Claim 14, The first event and the second event are Event-2 for UEI / ED (UE-initiated / Event-driven) beam reporting operation, and the beam(s) triggering the first event and the beam(s) triggering the second event are the same current beam and / or the same new beam, Terminal.

16. In Claim 13, The first prohibition timer is set to a value smaller than the second prohibition timer, Terminal.

17. In Claim 13, When the above terminal performs a UEI / ED beam reporting operation according to Mode B, the first UL channel is repeatedly transmitted according to a predetermined number of repeated transmissions, and the first prohibition timer starts after the last repetition of the first channel is transmitted. Terminal.

18. In Claim 13, The above first point in time is a point in time corresponding to the first symbol after the reception of the DCI has ended, Terminal.

19. In Claim 13, The first prohibition timer when the terminal performs a UEI / ED beam reporting operation according to Mode A is set to a value smaller than the first prohibition timer when the terminal performs a UEI / ED beam reporting operation according to Mode B. Terminal.

20. In Claim 13, When the terminal performs a UEI / ED beam reporting operation according to Mode A, the first prohibition timer is set to 0, and when the terminal performs a UEI / ED beam reporting operation according to Mode B, the first prohibition timer is set to a value greater than 0. Terminal.