Method and device for configuring and transmitting first pucch in ue-initiated beam management operation

Abstract

A beam reporting method for a terminal may comprise the steps of: detecting at least one event; when the at least one event is detected, determining a first transmission time point of a first UL channel for beam reporting; determining whether the first transmission time point overlaps at least partially with a transmission time point of at least one second channel; and when the first transmission time point overlaps at least partially with the transmission time point of the at least one second channel, applying a priority-based drop scheme or a multiplexing scheme in order to transmit at least one of the first UL channel or the at least one second channel.

Description

Method and apparatus for establishing and transmitting a first PUCCH in terminal-led beam management operation

[0001] The present invention relates to a beam management method in a mobile communication system, and more specifically, to a method and apparatus for setting and transmitting a first PUCCH 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] For UEI / ED beam management, the terminal transmits a first uplink (UL) channel (i.e., first PUCCH) to the base station, and in response to the first UL channel, transmits a second UL channel containing a beam report using resources configured by the base station or pre-configured resources. When the first UL channel collides with another channel, methods are required to resolve the collision.

[0006] The objective of the present disclosure to solve the above-mentioned problems is to provide a method and apparatus for resolving a conflict between a first UL channel for beam reporting and another channel 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 may include: detecting at least one event; determining a first transmission time of a first UL channel for beam reporting when the at least one event is detected; determining whether the first transmission time overlaps at least partially with the transmission time of at least one second channel; and, when the first transmission time overlaps at least partially with the transmission time of at least one second channel, applying a priority-based drop method or a multiplexing method to transmit at least one of the first UL channel or the at least one second channel.

[0008] The above at least one second channel may include a scheduling request (SR), a link recovery request (LRR), a physical uplink shared channel (PUSCH), and / or a first UL channel according to a second CSI reporting setting different from the first channel state information (CSI) reporting setting for the first UL channel.

[0009] The above priority-based drop method may include: a step of checking the priorities of the first UL channel and the at least one second channel; and a step of dropping the at least one second channel and transmitting the first UL channel or dropping the first UL channel and transmitting the at least one second channel based on the checked priorities.

[0010] The priorities of the first UL channel and at least one second channel can be determined by a priority rule.

[0011] The above priority rules can be indicated or updated by the base station through upper-layer signaling.

[0012] The above priority rule may be a rule that causes the first UL channel to have a lower priority than PUSCH or LRR, and the first UL channel to have a higher priority than SR.

[0013] The above priority rule may be a rule for determining the priority of the first UL channel according to the first CSI report setting and the priority of the first UL channel according to the second CSI report setting based on the priority of the first CSI report setting and the priority of the second CSI report setting.

[0014] The above priority rule may be a rule that determines the priority of the first UL channel according to the first CSI reporting setting and the priority of the first UL channel according to the second CSI reporting setting based on the priority of the event type reported by the first CSI reporting setting and the priority of the event type reported by the second CSI reporting setting.

[0015] The above multiplexing method may include: a step of generating a third channel in which the contents of the first UL channel and the contents of at least one second channel are multiplexed; and a step of transmitting the third channel in which the contents of the first UL channel and the contents of at least one second channel are multiplexed.

[0016] The third channel may be at least one of: the first UL channel in which the content of the first UL channel and the content of the at least one second channel are multiplexed using the plurality of bits when the first UL channel includes a plurality of bits; the at least one second channel in which the content of the first UL channel and the content of the at least one second channel are multiplexed; or the first UL channel in which the content of the first UL channel and the content of the at least one second channel are multiplexed using the divided time and / or frequency domains of the first UL channel.

[0017] A method of a base station according to embodiments of the present disclosure for achieving the above objective comprises: receiving at least one of a first uplink (UL) channel for beam reporting or at least one second channel whose transmission time overlaps at least partially with a first transmission time of the first UL channel from a terminal that has detected at least one event; and, when the first UL channel is received from the terminal, receiving a beam report through a UL resource allocated to the terminal or a UL resource pre-allocated to the terminal in response to the first UL channel, wherein the first UL channel or at least one of the at least one second channel may be received through a priority-based drop method or a multiplexing method.

[0018] The above at least one second channel may include a scheduling request (SR), a link recovery request (LRR), a physical uplink shared channel (PUSCH), and / or a first UL channel according to a second CSI reporting setting different from the first channel state information (CSI) reporting setting for the first UL channel.

[0019] The above priority-based drop method may be a method of receiving the at least one second channel or the first UL channel based on the priorities of the first UL channel and the at least one second channel.

[0020] The priorities of the first UL channel and at least one second channel can be determined by a priority rule.

[0021] The above method may further include the step of transmitting the above priority rule to the terminal through upper-layer signaling to instruct or update the terminal.

[0022] The above multiplexing method may be a method of receiving a third channel in which the contents of the first UL channel and the contents of at least one second channel are multiplexed.

[0023] 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 may enable the terminal to perform: a step of detecting at least one event; a step of determining a first transmission time of a first uplink (UL) channel for beam reporting when the at least one event is detected; a step of determining whether the first transmission time overlaps at least partially with a transmission time of at least one second channel; and a step of applying a priority-based drop method or a multiplexing method to transmit at least one of the first UL channel or the at least one second channel when the first transmission time overlaps at least partially with a transmission time of at least one second channel.

[0024] The above at least one second channel may include a scheduling request (SR), a link recovery request (LRR), a physical uplink shared channel (PUSCH), and / or a first UL channel according to a second CSI reporting setting different from the first channel state information (CSI) reporting setting for the first UL channel.

[0025] In the above priority-based drop method, the at least one processor may enable the terminal to perform: the step of checking the priorities of the first UL channel and the at least one second channel; and the step of dropping the at least one second channel and transmitting the first UL channel or dropping the first UL channel and transmitting the at least one second channel based on the checked priorities.

[0026] In the above multiplexing method, the at least one processor may enable the terminal to perform the steps of: generating a third channel in which the contents of the first UL channel and the contents of the at least one second channel are multiplexed; and transmitting the third channel in which the contents of the first UL channel and the contents of the at least one second channel are multiplexed.

[0027] According to embodiments of the present disclosure, collisions between a first UL channel and another channel for beam reporting can be prevented in a UE-initiated / event-driven beam reporting operation. Additionally, if a collision between the first UL channel and another channel is expected to occur, a priority-based drop method or multiplexing method may be applied to the first channel and the other channel. Accordingly, the transmission delay of the first UL channel and the transmission delay of the other channel resulting from the collision between the first UL channel and the other channel can be adjusted considering the overall performance of the system.

[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 invention are applied.

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

[0039] FIG. 11 is a flowchart illustrating a beam reporting operation according to one embodiment of the present invention.

[0040] FIG. 12 is a flowchart illustrating a first UL channel transmission method based on a priority-based drop method according to an embodiment of the present invention.

[0041] FIG. 13 is a flowchart illustrating a first UL channel transmission method based on a multiplexing method according to an embodiment of the present invention.

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

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

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

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

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

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

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

[0049] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. To facilitate overall understanding in describing 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0093]

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

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

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

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

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

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

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

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

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

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

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

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

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

[0107]

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

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

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

[0111]

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

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

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

[0115] Step 1: The terminal may transmit a first UL channel requesting resources for a 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 req terminal st) or a new UCI type.

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

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

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

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

[0120] 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 the existing SR (scheduling request terminal st) or the new UCI type.

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

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

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

[0124]

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

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

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

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

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

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

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

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

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

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

[0135]

[0136] 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 may 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 may notify the base station that it intends to use the pre-allocated resources for beam reporting. In Step 1, the terminal may 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.

[0137]

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

[0139] 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 resources for beam reporting through the first UL channel (i.e., first PUCCH) (S920), and the base station that received the first UL channel may indicate resources for the second UL channel to be used by the terminal to transmit the beam report through the DCI (S930). Subsequently, the terminal can transmit the second UL channel including the beam report using the said resources (S940).

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

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

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

[0143]

[0144] The conditions and methods for triggering a beam report in the above-described UEI / ED beam reporting operation (i.e., conditions and methods for transmitting the first PUCCH) were defined through the following discussion process.

[0145]

[0146] In the transmission procedure of UEI / ED beam reporting, regarding the setting of the first PUCCH, it was determined that either the following Alt-1 or Alt-2 is selected for both Mode A and Mode B.

[0147] Alt-1 (dedicated SR)

[0148] An RRC parameter (e.g., reportResourceRequest-UEIBR / reportNotification-UEIBR) corresponding to the 1-bit instruction of the first PUCCH is introduced, and the RRC parameter is associated with a dedicated SchedulingRequestId.

[0149] Alt-2 (Definition of the new UCI type)

[0150] - RRC parameters (e.g., firstPUCCHResourceConfig-UEIBR) are introduced for the configuration of periodic PUCCH resources, and these RRC parameters are not associated with the SchedulingRequestId. Positive / negative SR encoding schemes are reused for mapping between 1-bit indications and PUCCH resources. Dedicated RRC parameters include at least periododicityAndOffset and PUCCH-ResourceID.

[0151] The above Alt-1 and Alt-2 apply to at least a single CC (component carrier) case and reuse the existing SR multiplexing / drop rule as a baseline.

[0152] Finally, regarding the configuration of the first PUCCH in the transmission procedure of UEI / ED beam reporting, it was decided to support Alt-2 in both Mode A and Mode B. In other words, it was decided that the first PUCCH would have a new UCI type.

[0153]

[0154] Meanwhile, regarding the transmission procedure for UEI / ED beam reporting, it was decided that the following cases would be additionally reviewed in relation to the multiplexing / dropping rules of the first PUCCH.

[0155] · Case-1: When a 1-bit first PUCCH collides / overlaps with a PUCCH containing a normal SR or a PUCCH containing a normal LRR (link recovery request).

[0156] · Case-2: When the 1-bit first PUCCH conflicts / overlaps with PUSCH

[0157] · Case-3: Case where 1-bit first PUCCHs corresponding to different CSI settings for UEI / ED beam reporting overlap in the time domain

[0158]

[0159] In addition, for each of Mode A and Mode B, a 1-bit instruction in the first PUCCH is supported to request resources for the second UL channel to transmit beam reports, and it was determined that periodic PUCCH resources (PUCCH format 0 / 1) for the first PUCCH are set by dedicated RRC signaling.

[0160] Upon reviewing the above discussion points, a method (Alt-2) was selected to introduce a new UCI type for the first PUCCH in both Mode A and Mode B. Specifically, a dedicated RRC parameter (firstPUCCHResourceConfig-UEIBR) is defined for configuring periodic PUCCH resources unrelated to the SchedulingRequestId. Additionally, the 1-bit first PUCCH can be encoded by reusing the existing positive / negative SR encoding method. Furthermore, the dedicated RRC parameter for configuring the periodic PUCCH resource may include at least periododicityAndOffset and PUCCH-ResourceID. In this case, while existing SR multiplexing / dropping rules are used by default, it is necessary to consider a handling method for cases where the 1-bit first PUCCH conflicts with existing SRs (Scheduling Requests), LRRs (link recovery requests), or PUSCHs.

[0161] The (1-bit) first PUCCH can be used to request resources for the second UL channel to transmit a beam report (in the case of Mode A) or to announce the transmission of a beam report (in the case of Mode B). In this case, periodic PUCCH resources (format 0 / 1) for transmitting the first PUCCH can be configured through dedicated RRC signaling, and consideration must be given to how to configure such RRC signaling. Additionally, consideration must be given to how to implement a multi-bit first PUCCH when it is used to support multiple events (e.g., Event-2, Event-1, or Event-7).

[0162] Accordingly, the present disclosure provides a method for setting the first PUCCH and a method for resolving conflicts between the first PUCCH and other signals.

[0163]

[0164] Collision between First PUCCH and SR / LLR / PUSCH

[0165] As described above, in the UEI / ED beam reporting operation, the first PUCCH is determined to be a new UCI type, but a conflict may occur between the first PUCCH and the existing SR, LRR, or PUSCH. That is, with the introduction of the PUCCH of the new UCI type, a conflict may occur in the time domain with the SR, LRR, or PUSCH.

[0166] First, collisions with SRs may occur. A terminal may periodically transmit SRs for scheduling requests, and a collision may occur if the transmission time of the first PUCCH for beam reporting overlaps with the transmission time of an SR. In this case, the transmission of the SR may be delayed or lost, which can lead to delays in uplink data transmission. To resolve this, a method may be needed to determine which channel to prioritize, or to determine which channel to drop in the event of a collision.

[0167] Next, collisions with LRRs may occur. LRRs are used as messages or signals to request link recovery in wireless communication systems and can be used to report link quality degradation, failure to retransmit more than a certain number of times, or signal strengths (SINR, RSRP, etc.) below a specific threshold. A collision may occur if the transmission time of the first PUCCH for beam reporting overlaps with the transmission time of the LRR. In this case, the transmission of the LRR may be delayed or lost, which can affect the downlink scheduling of the base station. To resolve this, a method to determine which channel to prioritize may be required, similar to the collisions with SRs described earlier.

[0168] Finally, when a terminal uses a PUSCH to transmit uplink data, a collision may occur if the transmission times of the first PUCCH and the PUSCH overlap. In this case, data transmission may be delayed or lost, which can lead to a degradation of service quality. To address this, for example, a higher priority can be assigned to the PUSCH considering the importance of data transmission; however, the priority may be changed depending on the situation (e.g., the urgency of beam reporting) (e.g., the first PUCCH may have a higher priority than the PUSCH).

[0169]

[0170] As described above, to resolve collisions between the first PUCCH and existing channels (SR, LRR, PUSCH), methods may be used to determine which channel to transmit on when a collision occurs, and / or to adjust the timing of transmission through scheduling or other means to prevent collisions. For this purpose, priority-based dropping methods, time-domain coordination methods, and / or multiplexing methods may be considered. Priority-based dropping is a method that stops (drops) transmissions of lower priority according to predefined priorities when a collision occurs, and the priority of each channel can be determined by considering the importance of each channel. For example, the priority of each channel can be determined as follows.

[0171] SR: Since an SR is generally a request for uplink data transmission, it can have a medium priority. If urgent data transmission is required, an SR may be given a high priority.

[0172] LRR: In situations where a serious problem occurs in the wireless link between a terminal and a network and connection restoration is required, an LRR is transmitted to trigger a procedure for the terminal to request connection restoration from the network; it can be transmitted via PUCCH or PUSCH. Therefore, an LRR transmitted in the event of a serious wireless link problem may have a high priority. However, an LRR transmitted to report a certain number of retransmission failures or signal strength below a specific threshold (SINR, RSRP, etc.) may have a medium priority.

[0173] PUSCH: As it is an uplink data transmission channel, it can have a high priority.

[0174] First PUCCH: Beam management plays a critical role in link adaptation and handover, so it may have a medium or high priority. In particular, reporting related to beam failure recovery may need to have a high priority.

[0175]

[0176] In one embodiment, priorities for SR, LRR, PUSCH, and first PUCCH are defined, and based on these priorities, the channel to transmit or the channel to drop when a collision occurs may be determined. For example, priorities for signals or channels may be determined in descending order of PUSCH / LRR --> first PUCCH (beam failure recovery request / notification) --> SR --> first PUCCH (general beam report request / notification) (i.e., PUSCH or LRR has the highest priority, and first PUCCH (general beam report) has the lowest priority). Alternatively, priorities for signals or channels may be determined in descending order of PUSCH / LRR --> first PUCCH --> SR, regardless of whether first PUCCH directs a beam failure recovery request / notification or a general beam report request / notification (i.e., PUSCH or LRR has the highest priority, and SR has the lowest priority).

[0177] The terminal can detect whether a collision has occurred by checking the transmission times of channels or signals. If a collision is detected, the channel with the relatively lower priority can be dropped according to the determined priorities. For example, if the first PUCCH and PUSCH collide, the first PUCCH can be dropped and the PUSCH transmission performed. The priorities of each channel may be predetermined by technical standards, or the network may notify the terminal through higher-layer signaling (e.g., RRC signaling or MAC CE). Additionally, these priorities can be updated. These priorities may be updated at regular intervals, by instructions from the network, or upon an update request from the terminal.

[0178]

[0179] In another embodiment, if a collision is anticipated, the collision may be resolved by adjusting the transmission times of the channels where the collision is anticipated (i.e., a time-domain coordination scheme). The network (or base station) may adjust the scheduling of SR, LRR, and / or PUSCH so that the transmission times do not overlap with the first PUCCH. For example, the base station may ensure that SR, LRR, and / or PUSCH transmissions are not scheduled near the time when the transmission of the first PUCCH is scheduled. For example, collisions may be prevented by applying an offset to the transmission times of each channel. For instance, the transmission time of an SR where a collision with the first PUCCH is anticipated may be shifted by a few slots or symbols to avoid a collision with the first PUCCH. Alternatively, the period and offset of the first PUCCH may be set through the periododicityAndOffset parameter for setting the PUCCH resource for the first PUCCH. By appropriately adjusting the said parameter, collisions with other channels may be (partially) avoided. As another example, the possibility of collisions can be reduced by adjusting the transmission cycle of (some) channels. However, methods of adjusting transmission timing in the time domain can limit the scheduling flexibility of (some) channels and increase complexity. Effective coordination can be difficult, particularly in dynamic traffic environments, and may cause transmission delays for some channels.

[0180]

[0181] In another embodiment, collisions can be resolved through improvements in the multiplexing method. That is, a method of resolving collisions can be used by enabling multiple types of information to be transmitted simultaneously through a single channel (i.e., by improving the channel structure). For example, the PUCCH format for transmitting the first PUCCH can be extended so that when transmitting the first PUCCH, the SR, LRR, and / or beam report information (i.e., PUSCH) and the contents of the first PUCCH (e.g., 1-bit instruction) can be multiplexed and transmitted on a single channel.

[0182] A single channel multiplexed with the contents of the First PUCCH and SR, LRR, and / or beam report information may be a First PUCCH generated by encoding multiple pieces of information using multiple bits if the First PUCCH is a multi-bit First PUCCH (2-bit or more). Alternatively, each piece of information may be transmitted independently using multiple subchannels. Or, in the event of a collision between the First PUCCH and the PUSCH, the contents of the First PUCCH (i.e., 1-bit instructions) may be multiplexed and transmitted on the PUSCH. As another example, multiple pieces of information may be multiplexed by dividing the time or frequency domain within the First PUCCH. For instance, some symbols within the First PUCCH may be used for beam management, while others may be used for SR. While this approach can improve resource utilization efficiency and resolve collision issues, it may increase the complexity of the channel structure and the implementation complexity for the UE and base station. Additionally, the possibility of performance degradation for each piece of information due to multiplexing must be considered.

[0183]

[0184] Since the methods proposed in the embodiments described above have advantages and disadvantages, it may be effective to use a combination of two or more methods. For example, while using a priority-based drop method as the primary method, collisions can be minimized in specific situations by improving the time-domain adjustment method and / or multiplexing method. In this case, the base station may instruct the terminal on the period, start time, and / or end time for changing from the primary method (e.g., priority-based drop method) to another method (e.g., time-domain adjustment method). Alternatively, after changing to another method, the terminal may return to the primary method after a specific time has elapsed, or continue to operate in that method until a signal instructing to return to the primary method after changing to another method is received.

[0185]

[0186] As described with reference to FIGS. 9 and 10, the first PUCCH serves only as a control signal for the transmission of the second UL channel, and the actual beam reporting can be done through the second UL channel (PUSCH or PUCCH). That is, in the above embodiments, the PUSCH that may conflict with the first PUCCH may be the second UL channel transmitted for beam reporting.

[0187] Therefore, the priority settings for the priority-based drop method described above can be extended as follows. For example, priorities can be determined in descending order: (General) PUSCH / LRR --> (PUSCH as a second UL channel) (Beam Report) --> first PUCCH (Beam Failure Recovery Request / Notification) --> (Urgent transmission required) SR --> first PUCCH (General Beam Report Request / Notification) (i.e., PUSCH / LRR has the highest priority and first PUCCH (General Beam Report Request / Notification) has the lowest priority). Alternatively, regardless of whether first PUCCH directs a Beam Failure Recovery Request / Notification or a General Beam Report Request / Notification, priorities for signals or channels can be determined in descending order: PUSCH / LRR --> (PUSCH as a second UL channel) (Beam Report) --> first PUCCH --> SR (i.e., PUSCH or LRR has the highest priority and SR has the lowest priority).

[0188] In addition, time domain adjustment methods can also be applied to the second UL channel in a manner similar to the first PUCCH. Furthermore, a method of transmitting data and beam control-related information together using the second UL channel (primarily PUSCH) can also be considered. This can be implemented by allocating separate resources for beam control-related information within the second UL channel (PUSCH) or by extending the PUSCH format. For example, bits representing beam selection information or beam quality indicators (e.g., RSRP, SINR) can be added. This information can be multiplexed together with existing data and transmitted via PUSCH.

[0189]

[0190] Conflict between First PUCCHs

[0191] When a single terminal must simultaneously perform beam reporting procedures for multiple CSI reporting configurations (e.g., different beams or different frequency bands), the first PUCCHs for each beam reporting procedure may overlap in time. In other words, a conflict situation may arise where the terminal must decide which CSI reporting configuration to report for. To mitigate this conflict, one or more of the previously described priority-based drop method, time-domain adjustment method, and multiplexing method may be utilized.

[0192]

[0193] In one embodiment, the priorities of channels in a priority-based drop method may be determined by considering the following specific factors. For example, if a specific beam or frequency band is more important than others (e.g., if the channel quality of the frequency band is significantly different), a higher priority may be assigned to the corresponding CSI reporting setup. As another example, if reporting for a specific CSI reporting setup is more urgent than others (e.g., if a beam failure is imminent), a higher priority may be assigned to the corresponding CSI reporting setup. As yet another example, depending on the type of event, a higher priority may be assigned to a CSI reporting setup associated with a specific event (e.g., Event-1 or Event-2 having a higher priority than Event-7). In this case, the network may inform the terminal of the priorities of the CSI reporting setups through upper-layer signals (e.g., RRC signaling or MAC CE). Additionally, the priorities may be updated. The priorities may be updated at regular intervals, by instructions from the network, or upon an update request from the terminal. In addition, in the event of a collision (i.e., when multiple first PUCCH transmissions overlap), the terminal may transmit only the first PUCCH with the highest priority and drop the remaining first PUCCHs.

[0194]

[0195] In another embodiment, the collision can be resolved by adjusting the transmission times of each channel. That is, the occurrence of the collision itself can be prevented by temporally separating the first PUCCH transmission times according to the CSI reporting settings. For example, the periodicity and offset of each first PUCCH can be appropriately adjusted to adjust the period and offset of the first PUCCH(s). For example, if the first PUCCH transmission period of CSI reporting setting 1 is 2 slots and the offset is 0, then if the first PUCCH transmission period of CSI reporting setting 2 is set to 2 slots and the offset is set to 1 slot, the transmission times of the first PUCCHs of CSI reporting setting 1 and 2 can be separated.

[0196]

[0197] In another embodiment, a method of simultaneously transmitting beam reports according to multiple CSI reporting settings in a single first PUCCH may be considered. For example, if the first PUCCH contains two or more multi-bits, beam reports according to multiple CSI reporting settings may be transmitted simultaneously by the codepoint indicated by the multi-bits. For example, two bits may be used to simultaneously indicate beam reports for two CSI reporting settings (e.g., 00: report for CSI reporting setting 1, 01: report for CSI reporting setting 2, 10: report for CSI reporting setting 1 and report for CSI reporting setting 2).

[0198]

[0199] Since the methods proposed in the embodiments described above have advantages and disadvantages, it may be effective to use a combination of two or more methods. For example, conflicts can be resolved by using a priority-based drop method as the basis, while conflicts can be prevented through a time-domain adjustment method in specific situations (e.g., some critical CSI reporting settings). If a multi-bit first PUCCH or a new first PUCCH format is introduced in the future, more efficient beam reporting can be implemented by utilizing it.

[0200] Meanwhile, in priority-based drop methods, in addition to the fixed priority settings based on channel types described earlier, a method to dynamically change priorities depending on the situation may be considered. For example, if beam quality degradation exceeding a specific threshold is detected, a method such as temporarily raising the priority of the corresponding first PUCCH may be used. For instance, criteria for dynamically determining priorities in this manner may include beam quality indicators (RSRP, SINR, etc.) and / or the number of beam failures. Specific trigger conditions that induce priority changes may be transmitted via upper-layer signals between the network and the terminal (e.g., RRC signaling or MAC CE).

[0201]

[0202] FIG. 11 is a flowchart illustrating a beam reporting operation according to one embodiment of the present invention.

[0203] Referring to FIG. 11, the terminal can detect at least one event (S1110). In this case, the at least one event detected by the terminal may be at least one of the previously described events-1 to-9.

[0204] If at least one event is detected in step S1110, the terminal can determine a first transmission time for a first uplink (UL) channel for beam reporting (S1120). The terminal can transmit the first UL channel on one of the PUCCH resources periodically configured by the dedicated RRC signaling described above (e.g., firstPUCCHResourceConfig-UEIBR). Generally, the time of the PUCCH resource that arrives first from the time the time required to create the first UL channel has elapsed from the time the event is detected can be determined as the transmission time of the first UL channel (i.e., the first transmission time).

[0205] Next, the terminal can determine whether the first transmission time overlaps at least partially with the transmission time of at least one second channel (S1130). As previously described, the at least one second channel that may collide with the first UL channel may include a SR (scheduling request), LRR (link recovery request), PUSCH (physical uplink shared channel), and / or a first UL channel according to a second CSI reporting setting different from the first channel state information (CSI) reporting setting for the first UL channel.

[0206] Next, if the first transmission time overlaps at least partially with the transmission time of at least one second channel, the terminal may apply a priority-based drop method or a multiplexing method to transmit at least one of the first UL channel or at least one of the at least one second channel (S1140).

[0207] Here, the terminal may selectively apply a priority-based drop method or a multiplexing method depending on whether the content of the at least one second channel can be multiplexed to the first UL channel (i.e., whether the first UL channel includes a plurality of bits or whether divided time and / or frequency domains can be set in the first UL channel), or whether the multiplexing of the content of the first UL channel and the content of the at least one second channel can be completed by the transmission time of the first UL channel (i.e., the first transmission time).

[0208] In another embodiment, the terminal may always apply a multiplexing method or a priority-based drop method. For example, the base station may instruct the terminal to apply a multiplexing method or a priority-based drop method via upper layer signaling (RRC signaling or MAC CE signaling). Alternatively, the base station may include a 1-bit indicator in the DCI that schedules the PUSCH and use the 1-bit indicator to instruct whether to allow (i.e., apply a multiplexing method) or prohibit (i.e., apply a priority-based drop method) multiplexing of the first UL channel (first PUCCH) for the PUSCH. In yet another embodiment, the terminal may selectively apply a multiplexing method or a priority-based drop method depending on whether specific conditions other than those described above are satisfied.

[0209] Below, the case where the terminal selects a priority-based drop method in step S1140 is described with reference to FIG. 12, and the case where the terminal selects a multiplexing method in step S1140 is described with reference to FIG. 13.

[0210] FIG. 12 is a flowchart illustrating a first UL channel transmission method based on a priority-based drop method according to an embodiment of the present invention.

[0211] Referring to FIG. 12, the priority-based drop method may include: a step (S1210) of checking the priorities of the first UL channel and the at least one second channel; and a step (S1220) of dropping the at least one second channel and transmitting the first channel or dropping the first channel and transmitting the at least one second channel based on the checked priorities.

[0212] In step S1210, the priorities of the first UL channel and the at least one second channel can be determined by a priority rule.

[0213] Priority rules may be predetermined by technical standards or instructed by the base station (i.e., network) via higher-layer signaling (e.g., RRC signaling or MAC CE). Additionally, priority rules may be instructed or updated by higher-layer signaling.

[0214] For example, the above priority rule may be a rule that causes the first UL channel to have a lower priority than PUSCH or LRR, and the first UL channel to have a higher priority than SR.

[0215] Additionally or generally, the priority rule may be a rule for determining the priority of the first UL channel according to the first CSI reporting setting and the priority of the first UL channel according to the second CSI reporting setting based on the priority of the first CSI reporting setting and the priority of the second CSI reporting setting.

[0216] Additionally or generally, the priority rule may be a rule that determines the priority of the first UL channel according to the first CSI reporting setting and the priority of the first UL channel according to the second CSI reporting setting based on the priority of the event type reported by the first CSI reporting setting and the priority of the event type reported by the second CSI reporting setting.

[0217] FIG. 13 is a flowchart illustrating a first UL channel transmission method based on a multiplexing method according to an embodiment of the present invention.

[0218] Referring to FIG. 13, the multiplexing method may include: a step (S1310) of generating a third channel in which the contents of the first UL channel and the contents of at least one second channel are multiplexed; and a step (S1320) of transmitting the third channel in which the contents of the first UL channel and the contents of at least one second channel are multiplexed.

[0219] In the above step (S1310), the third channel may be at least one of the following: the first UL channel in which the content of the first UL channel and the content of the at least one second channel are multiplexed using the plurality of bits when the first UL channel includes a plurality of bits; the at least one second channel in which the content of the first UL channel and the content of the at least one second channel are multiplexed; or the first UL channel in which the content of the first UL channel and the content of the at least one second channel are multiplexed using the divided time and / or frequency domains of the first UL channel.

[0220]

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

[0222] 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. For example, a priority-based drop method may be applied to the initial transmission of the first PUCCH (or second UL channel), and a time-domain adjustment method or a multiplexing method may be applied to the retransmission.

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

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

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

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

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

[0228]

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

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

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

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

[0233] 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 a method of a terminal for beam reporting, A step of detecting at least one event; When at least one of the above events is detected, a step of determining a first transmission time of a first uplink (UL) channel for beam reporting; A step of determining whether the first transmission time point overlaps at least partially with the transmission time point of at least one second channel; and If the first transmission time overlaps at least partially with the transmission time of at least one second channel, the method comprises the step of applying a priority-based drop method or a multiplexing method to transmit at least one of the first UL channel or the at least one second channel. Method of the terminal.

2. In Claim 1, The at least one second channel comprises a first UL channel according to a second CSI reporting setting different from a first channel state information (CSI) reporting setting for the first UL channel, and / or a scheduling request (SR), a link recovery request (LRR), a physical uplink shared channel (PUSCH), and / or a first UL channel according to a second CSI reporting setting different from a first CSI reporting setting for the first UL channel. Method of the terminal.

3. In Claim 1, The above priority-based drop method is: A step of verifying the priorities of the first UL channel and the at least one second channel; and Based on the above-mentioned identified priorities, the method comprises the step of dropping the at least one second channel and transmitting the first UL channel, or dropping the first UL channel and transmitting the at least one second channel. Method of the terminal.

4. In Claim 3, The priorities of the first UL channel and the at least one second channel are determined by a priority rule, Method of the terminal.

5. In Claim 4, The above priority rules are indicated or updated by the base station through upper-layer signaling, Method of the terminal.

6. In Claim 4, The above priority rule is a rule that causes the first UL channel to have a lower priority than PUSCH or LRR, and the first UL channel to have a higher priority than SR, Method of the terminal.

7. In Claim 4, The above priority rule is a rule that determines the priority of the first UL channel according to the first CSI reporting setting and the priority of the first UL channel according to the second CSI reporting setting based on the priority of the first CSI reporting setting and the priority of the second CSI reporting setting, Method of the terminal.

8. In Claim 4, The above priority rule is a rule that determines the priority of the first UL channel according to the first CSI reporting setting and the priority of the first UL channel according to the second CSI reporting setting based on the priority of the event type reported by the first CSI reporting setting and the priority of the event type reported by the second CSI reporting setting, Method of the terminal.

9. In Claim 1, The above multiplexing method is: A step of generating a third channel in which the contents of the first UL channel and the contents of at least one second channel are multiplexed; and A step comprising transmitting the third channel in which the contents of the first UL channel and the contents of at least one second channel are multiplexed, Method of the terminal.

10. In Claim 9, The above third channel is: In the case where the first UL channel includes a plurality of bits, the first UL channel, wherein the content of the first UL channel and the content of the at least one second channel are multiplexed using the plurality of bits; The at least one second channel in which the content of the first UL channel and the content of the at least one second channel are multiplexed; or At least one of the first UL channels, wherein the content of the first UL channel and the content of the at least one second channel are multiplexed using the divided time and / or frequency domains of the first UL channel, Method of the terminal.

11. A method of a base station for receiving beam reports, A step of receiving at least one of a first uplink (UL) channel for beam reporting or at least one second channel whose transmission time at least partially overlaps with a first transmission time of the first UL channel from a terminal that has detected at least one event; and When the first UL channel is received from the terminal, the method includes the step of receiving a beam report in response to the first UL channel through a UL resource allocated to the terminal or a UL resource pre-allocated to the terminal. At least one of the first UL channel or at least one second channel is received through a priority-based drop method or a multiplexing method, Base station method.

12. In Claim 11, The at least one second channel comprises a first UL channel according to a second CSI reporting setting different from a first channel state information (CSI) reporting setting for the first UL channel, and / or a scheduling request (SR), a link recovery request (LRR), a physical uplink shared channel (PUSCH), and / or a first UL channel according to a second CSI reporting setting different from a first CSI reporting setting for the first UL channel. Base station method.

13. In Claim 11, The above priority-based drop method is: a method of receiving the at least one second channel or the first UL channel based on the priorities of the first UL channel and the at least one second channel, Base station method.

14. In Claim 13, The priorities of the first UL channel and the at least one second channel are determined by a priority rule, Base station method.

15. In Claim 14, The method further includes the step of transmitting to the terminal via upper-layer signaling to instruct or update the above priority rule to the terminal. Base station method.

16. In Claim 11, The above multiplexing method is: a method of receiving a third channel in which the contents of the first UL channel and the contents of at least one second channel are multiplexed, Base station method.

17. In a terminal comprising at least one processor, The above at least one processor is the terminal: A step of detecting at least one event; When the above at least one event is detected, a step of determining a first transmission time of a first uplink (UL) channel for beam reporting; A step of determining whether the first transmission time point overlaps at least partially with the transmission time point of at least one second channel; and If the first transmission time overlaps at least partially with the transmission time of at least one second channel, the step of applying a priority-based drop method or a multiplexing method to transmit at least one of the first UL channel or the at least one second channel is performed. Terminal.

18. In Claim 17, The at least one second channel comprises a first UL channel according to a second CSI reporting setting different from a first channel state information (CSI) reporting setting for the first UL channel, and / or a scheduling request (SR), a link recovery request (LRR), a physical uplink shared channel (PUSCH), and / or a first UL channel according to a second CSI reporting setting different from a first CSI reporting setting for the first UL channel. Terminal.

19. In Claim 17, In the above priority-based drop method, the at least one processor is the terminal: A step of verifying the priorities of the first UL channel and the at least one second channel; and Based on the above identified priorities, performing the step of dropping the at least one second channel and transmitting the first UL channel, or dropping the first UL channel and transmitting the at least one second channel. Terminal.

20. In Claim 17, In the above multiplexing method, the at least one processor is the terminal: A step of generating a third channel in which the contents of the first UL channel and the contents of at least one second channel are multiplexed; and Performing the step of transmitting the third channel in which the contents of the first UL channel and the contents of at least one second channel are multiplexed Terminal.

Images