Method and device for transmitting CSI report in UE-initiated beam management operation

Abstract

This method of a UE may comprise the steps of: receiving at least one first CSI report configuration and at least one second CSI report configuration from a base station; generating at least one CSI report on the basis of the at least one first CSI report configuration; generating at least one beam report on the basis of the at least one second CSI report configuration; determining whether a first UL resource on which the at least one CSI report is to be transmitted and a second UL resource on which the at least one beam report is to be transmitted at least partially overlap; on the basis of a determination that the first UL resource and the second UL resource overlap, selecting at least one report among the at least one CSI report and the at least one beam report according to a priority determination rule; and transmitting the at least one report to the base station through a UL resource corresponding to the at least one report among the first UL resource and the second resource.

Description

Method and device for transmitting CSI reports 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 transmitting a CSI (channel state information) report 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] When multiple CSI (channel state information) report configurations are set for terminal-led / event-based beam management, further discussion is required regarding the method of establishing the relationship between the beam reports transmitted by the terminal and the CSI report configurations, as well as the method of transmitting the corresponding beam reports.

[0006] The objective of the present disclosure to solve the above-mentioned problems is to provide a method and apparatus for transmitting a beam report in a UE-initiated / event-driven beam reporting operation.

[0007] A method of a terminal according to embodiments of the present disclosure for achieving the above objective comprises: receiving at least one first CSI (channel state information) report setting and at least one second CSI report setting from a base station, wherein each of the at least one first CSI report setting sets a CSI report and each of the at least one second CSI report setting sets a beam report; generating at least one CSI report based on the at least one first CSI report setting; detecting at least one event based on the at least one second CSI report setting and generating at least one beam report corresponding to the at least one event; determining whether a first uplink (UL) resource to which the at least one CSI report is to be transmitted and a second UL resource to which the at least one beam report is to be transmitted overlap at least partially; and selecting at least one report among the at least one CSI report and the at least one beam report according to a priority determination rule based on the determination that the first UL resource and the second UL resource overlap. and may include the step of transmitting the selected at least one report to the base station through the UL resource corresponding to the at least one report among the first UL resource or the second resource.

[0008] The first UL resource may be a PUCCH (physical uplink control channel) resource or a PUSCH (physical uplink shared channel) resource, and the second UL resource may be a PUCCH resource.

[0009] The above at least one report may have the maximum report payload size among the report payload sizes according to the above at least one first CSI report setting and the above at least one second CSI report setting.

[0010] If the size of the valid information of at least one report is smaller than the maximum report payload size, the at least one report may include zero-padding bits in addition to the valid information to satisfy the maximum report payload size.

[0011] The above priority determination rule may be set through RRC (radio resource control) signaling from the base station or predefined in technical specifications.

[0012] The above priority determination rule can cause event-based Mode-A beam reporting to have a higher priority than aperioditic CSI reporting transmitted via PUCCH.

[0013] The above priority determination rule can cause event-based Mode-B beam reporting to have a higher priority than semi-persistent CSI reporting transmitted via PUSCH.

[0014] The above priority determination rule can ensure that non-periodic CSI reports transmitted via PUCCH have a higher priority than event-based Mode-B beam reports.

[0015] The above priority determination rule can cause event-based Mode-A beam reporting and event-based Mode-B beam reporting to have higher priority than semi-persistent CSI reporting to be transmitted via PUCCH and periodic CSI reporting to be transmitted via PUCCH.

[0016] A method of a base station according to embodiments of the present disclosure for achieving the above objective comprises: transmitting to a terminal at least one first CSI (channel state information) reporting setting and at least one second CSI reporting setting, wherein each of the at least one first CSI reporting setting sets a CSI report and each of the at least one second CSI reporting setting sets a beam report; and receiving from the terminal at least one report selected from at least one CSI report based on the at least one first CSI reporting setting and at least one beam report based on the at least one second CSI reporting setting, wherein the at least one report is selected by the terminal according to a priority determination rule from the at least one CSI report and the at least one beam report based on at least a partial overlap between a first uplink (UL) resource to which the at least one CSI report is to be received and a second UL resource to which the at least one beam report is to be received, and the at least one report may be transmitted to the terminal through a UL resource corresponding to the at least one report among the first UL resource or the second resource.

[0017] The first UL resource may be a PUCCH (physical uplink control channel) resource or a PUSCH (physical uplink shared channel) resource, and the second UL resource may be a PUCCH resource.

[0018] The above at least one report may have the maximum report payload size among the report payload sizes according to the above at least one first CSI report setting and the above at least one second CSI report setting.

[0019] The above priority determination rule may be set to the terminal through RRC (radio resource control) signaling or predefined in technical specifications.

[0020] The above priority determination rule can cause event-based Mode-A beam reporting to have a higher priority than aperioditic CSI reporting transmitted via PUCCH.

[0021] The above priority determination rule can cause event-based Mode-B beam reporting to have a higher priority than semi-persistent CSI reporting transmitted via PUSCH.

[0022] The above priority determination rule can ensure that non-periodic CSI reports transmitted via PUCCH have a higher priority than event-based Mode-B beam reports.

[0023] The above priority determination rule can cause event-based Mode-A beam reporting and event-based Mode-B beam reporting to have higher priority than semi-persistent CSI reporting to be transmitted via PUCCH and periodic CSI reporting to be transmitted via PUCCH.

[0024] A terminal according to embodiments of the present disclosure for achieving the above objective comprises at least one processor, wherein the at least one processor comprises: receiving at least one first CSI (channel state information) report setting and at least one second CSI report setting from a base station, wherein each of the at least one first CSI report setting sets a CSI report and each of the at least one second CSI report setting sets a beam report; generating at least one CSI report based on the at least one first CSI report setting; detecting at least one event based on the at least one second CSI report setting and generating at least one beam report corresponding to the at least one event; determining whether a first uplink (UL) resource to which the at least one CSI report is to be transmitted and a second UL resource to which the at least one beam report is to be transmitted overlap at least partially; and selecting at least one report among the at least one CSI report and the at least one beam report according to a priority determination rule based on the determination that the first UL resource and the second UL resource overlap. and the step of transmitting the selected at least one report to the base station through the UL resource corresponding to the at least one report among the first UL resource or the second resource may be performed.

[0025] The first UL resource may be a PUCCH (physical uplink control channel) resource or a PUSCH (physical uplink shared channel) resource, and the second UL resource may be a PUCCH resource.

[0026] The above at least one report may have the maximum report payload size among the report payload sizes according to the above at least one first CSI report setting and the above at least one second CSI report setting.

[0027] When using the embodiments according to the present disclosure, resources for the transmission of a first UL channel (i.e., first PUCCH) for a plurality of CSI reporting settings can be efficiently configured in a terminal-initiated (UE-initiated) / event-driven beam reporting operation. That is, a common PUCCH resource for the transmission of the first PUCCH for a plurality of CSI reporting settings can be configured, and while transmitting the beam report using the common PUCCH resource, the CSI reporting setting associated with the beam report can be identified between the base station and the terminal without ambiguity among the beam report and the plurality of CSI reporting settings. Thus, consistency between the operation of the base station and the operation of the terminal can be maintained while pursuing resource efficiency.

[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 for explaining a beam reporting transmission method according to a first embodiment of the present disclosure.

[0040] FIG. 12 is a flowchart for explaining a beam reporting transmission method according to a second embodiment of the present disclosure.

[0041] FIG. 13 is a flowchart for explaining a beam reporting transmission method according to a third embodiment of the present disclosure.

[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] Discussions were held regarding the method for establishing the relationship between the terminal's beam reporting and the CSI report configuration in the aforementioned terminal-initiated / event-driven beam management (hereinafter referred to as UEI / ED BM operation or UEI / ED beam reporting operation), and the following agreement was reached.

[0145] A single PUCCH resource for transmission via the first UL channel (i.e., first PUCCH) for UEI / ED BM operation may be associated with one or more CSI reporting settings in relation to Event-2. Only a single beam report is transmitted via the second UL channel (i.e., PUSCH), and the report format is provided with an additional instruction field for one 'CSI reporting setting'.

[0146] CSI report configurations associated with the same PUCCH resource are sorted in ascending order of their corresponding CSI-ReportConfigIds, and the number of bits in the additional instruction field is ceil(log2(N_CSIconfig)). Here, N_CSIconfig represents the number of CSI report configurations associated with the same PUCCH resource.

[0147] The payload size of a single beam report is determined by the maximum payload size among the associated CSI reporting settings. If the payload size of the beam report is smaller than the maximum payload size, zero padding may be added.

[0148] The reported beam report must satisfy the triggering conditions.

[0149] If multiple UEI / ED beam reporting procedures occur, one of the following options may be selected.

[0150] Option-1: The selection of one of the CSI reporting settings is left to the terminal implementation.

[0151] Option-2: The beam report with the highest priority is reported.

[0152] Option-3: The beam report triggered in the most recent measurement is reported as PUSCH.

[0153] Multiple CSI reporting settings associated with a single first PUCCH resource must be configured in the same CC.

[0154] In Mode-A, multiple CSI reporting settings associated with the same PUCCH resource are assumed to be associated with the same CSI-AperiodicTriggerState.

[0155] In the case of Mode-B, multiple CSI reporting settings associated with the same PUCCH resource must be associated with the same second UL channel (i.e., PUSCH).

[0156]

[0157] In the present disclosure, transmission methods for beam reports are proposed that take into account the relationship between beam reports and CSI report settings.

[0158]

[0159] First Embodiment: Beam Report Transmission (PUSCH) using PUCCH resources associated with multiple CSI report settings

[0160] A case may be considered where a single PUCCH resource is utilized by multiple CSI report configurations. A base station can configure a single PUCCH resource for a terminal and associate that PUCCH resource with multiple CSI report configurations. That is, the base station can manage multiple event triggers or different reporting conditions corresponding to different CSI report configurations through a single PUCCH resource. With this configuration, the base station does not need to individually allocate a separate control channel resource for each event trigger, which can reduce control channel overhead and lower the possibility of collisions between control channels.

[0161] When a specific event trigger condition is satisfied and the terminal initiates a UEI / ED beam reporting operation, the terminal may transmit detailed information (i.e., a beam report) regarding the beam associated with the triggered event through the second UL channel. The format of the beam report transmitted through the second UL channel may include an indicator to identify which CSI reporting setting triggered the beam report. If a single PUCCH resource is associated with multiple CSI reporting settings, the base station can check the corresponding indicator included in the received beam report to accurately identify which CSI reporting setting the reported beam report corresponds to.

[0162] For example, an indicator set to '01' can be predefined to indicate the first CSI report setting associated with the corresponding PUCCH resource, and an indicator set to '10' can be predefined to indicate the second CSI report setting associated with the corresponding PUCCH resource. In this case, the Beam report corresponding to the first CSI report setting and the Beam report corresponding to the second CSI report setting may be reports for the same event or reports for different events. As an example of reports for different events, an indicator set to '01' can be predefined to indicate the first CSI report setting corresponding to Event-2, and an indicator set to '10' can be predefined to indicate the second CSI report setting corresponding to Event-7. In this way, by including identifiers within the Beam report, the network can interpret the reported Beam report without confusion, even in situations where multiple event triggers exist.

[0163] The payload size of a beam report transmitted through the second UL channel can be defined to match the maximum payload size required by multiple CSI report configurations associated with the corresponding PUCCH resource. In other words, the payload size of the beam report can be defined based on the report format requiring the largest number of bits among the CSI report configurations bound to a single PUCCH resource. Accordingly, since a payload of sufficient size can always be secured regardless of which event trigger initiates the beam report, a situation in which part of the beam report cannot be transmitted can be prevented.

[0164] If the amount of information that the terminal actually needs to report falls short of the maximum payload size mentioned above, the terminal may perform zero-padding on the remaining payload area. For example, if the maximum payload size required by the CSI reporting settings associated with the corresponding PUCCH resource is defined as 40 bits, the terminal may reserve a payload size of 40 bits for the beam report. Subsequently, if a beam report containing only 20 bits of information occurs, the terminal may transmit a total of 40 bits by padding 20 bits of zeros after the 20 bits of valid information. Since the base station knows the actual payload size for each of the pre-configured CSI reporting settings, the base station may interpret only the bits corresponding to the payload size according to the CSI reporting setting indicated by the indicator as valid data from the received 40-bit payload, and ignore the remaining padding bits.

[0165] As described above, the base station and the terminal can efficiently transmit and receive beam reports while maintaining a consistent PUSCH resource size.

[0166] FIG. 11 is a flowchart for explaining a beam reporting transmission method according to a first embodiment of the present disclosure.

[0167] Referring to FIG. 11, the base station can transmit multiple CSI report settings to the terminal (S1110). FIG. 11 illustrates a case where N CSI report settings are set to the terminal.

[0168] According to a plurality of CSI reporting settings configured from a base station, the terminal can detect at least one event (S1120). In this case, according to the plurality of CSI reporting settings, the terminal may detect one event or multiple events. The first embodiment assumes the case where the terminal detects one event.

[0169] For beam reporting of a detected event, the terminal can transmit the first UL channel (i.e., first PUCCH) to the base station (S1130). As previously mentioned, one PUCCH resource can be configured for the first UL channel (i.e., first PUCCH). That is, one PUCCH resource can be linked to multiple CSI reporting configurations.

[0170] The terminal can transmit a beam report containing an indicator that directs a CSI report setting corresponding to the generated event through the second UL channel (i.e., PUSCH) (S1140). Meanwhile, the transmission resource of the second UL channel is a resource allocated by the DCI received from the base station in the case of Mode-A (as exemplified in FIG. 9), and may be a pre-set resource in the case of Mode-B (as exemplified in FIG. 10).

[0171] The base station can check the beam report containing the relevant indicator to determine which CSI reporting setting the beam report corresponds to.

[0172]

[0173] Second Embodiment: Prioritization among beam reports

[0174] Cases may be considered where events corresponding to two or more different CSI reporting settings occur simultaneously or at close points in time (i.e., within a specified time interval). When a single PUCCH resource is associated with multiple CSI reporting settings, the terminal may be configured to transmit only one beam report per beam reporting opportunity. In this case, the terminal may determine which beam report corresponding to which CSI reporting setting to transmit preferentially based on predefined rules or priorities.

[0175] For example, the terminal may operate to transmit a beam report corresponding to the most recently occurred event. This method may involve transmitting information about the most recent event to the network so that the network can reflect the terminal's latest state.

[0176] As another example, priorities can be defined among multiple CSI reporting settings. The base station can pre-set priorities for each CSI reporting setting, and the terminal can prioritize the transmission of beam reports corresponding to the CSI reporting setting with the highest priority. For instance, degradation of the quality of the current serving link (i.e., the current beam) may be considered a more urgent situation than the discovery of a new beam; accordingly, a CSI reporting setting to detect degradation of the current serving link (i.e., an event to detect degradation of the current serving link (i.e., the current beam)) may be set with a higher priority. Such prioritization rules among CSI reporting settings can be pre-established through RRC signaling or defined in advance by standards. Through this, the terminal and the network can maintain consistency in the beam reporting procedure even when multiple events occur simultaneously (or at close intervals). Additionally, for events for which a beam report was not transmitted due to priority determination, the terminal may re-evaluate the event during a subsequent reporting opportunity, and if it is confirmed that the trigger conditions for the event are consistently satisfied, it may transmit a beam report for the event during the next reporting cycle (i.e., the next PUCCH resource).

[0177] As a specific embodiment, the base station may set two event-based CSI reporting settings for the terminal. For example, the first CSI reporting setting may be a report associated with Event-2, and the second CSI reporting setting may be a report associated with Event-1. Both CSI reporting settings may be defined based on SSB or CSI-RS measurements performed in the same cell or the same CC to which the terminal belongs. Additionally, as previously described, the two CSI reporting settings may be associated with the same first PUCCH resource. The base station may allocate the resource of the second UL channel (i.e., PUSCH) to be used by the terminal to transmit beam reports according to Mode-A or Mode-B.

[0178] When beam reporting based on the first CSI reporting setting is selected (i.e., when the trigger condition of Event-2 is satisfied), the terminal may set a code value (e.g., 0 or 01) corresponding to the first CSI reporting setting in the indicator included in the PUSCH payload. The terminal may load specific information required according to the first CSI reporting setting into the PUSCH payload. For example, the terminal may include the identifier of a newly discovered beam (e.g., the index of the corresponding SSB) or a quality indicator for that beam (e.g., RSRP, etc.) in the PUSCH payload. This information may have a predefined bit length. Alternatively, a specific bit length may be set at an upper layer, or if no separate setting is made, a specific bit length based on a default value may be applied. For example, 5 bits may be assigned to the new beam identifier, and 10 bits may be assigned to a quality indicator such as RSRP.

[0179] If the total amount of information (i.e., payload size) according to the first CSI report configuration is 20 bits, the terminal can include 20 bits of valid information in the payload and then perform zero-padding on the remaining payload area. As previously assumed, if the maximum required payload size required by the first and second CSI report configurations is set to 40 bits (i.e., this means that the payload size required by the second CSI report configuration is 40 bits), the terminal can transmit a total of 40 bits, including 20 bits of valid information and 20 bits of padding. In this case, considering the number of bits in the indicator field described earlier, the number of bits in the beam identifier can be variable, for example, between 2 and 5 bits, and accordingly, zero-padding can be performed on the range of 15 to 18 bits.

[0180] When beam reporting based on the second CSI reporting setting is selected (i.e., when the trigger condition of Event-1 is satisfied), the terminal may transmit the identifier of the current serving beam and measured quality indicators, etc., along with an indicator set with a code value (e.g., 1 or 10) corresponding to the second CSI reporting setting. Alternatively, the terminal may report only the poor condition of the current serving beam in a situation where no suitable candidate beam exists. In this case, the terminal may indicate "no available alternative beam" using a predefined code value.

[0181] After receiving the PUSCH payload, the base station can determine which CSI reporting setting triggered the received beam report by reading the indicator field located at the beginning of the payload. As described above, if the received beam report corresponds to the first CSI reporting setting, the base station can interpret the bits following the indicator field according to the new beam report format. Through this, the base station can obtain the identifier of the new candidate beam reported by the terminal and the quality information of the corresponding beam. As a result, the base station can identify the presence and quality of the new candidate beam discovered by the terminal in the vicinity of the terminal and, if necessary, rapidly perform subsequent actions such as deciding on a beam switch to the corresponding beam or a handover. For example, the base station can transmit a DCI containing a TCI field indicating the selected new beam to the terminal, thereby enabling the terminal to use that beam in subsequent data transmission or reception.

[0182]

[0183] FIG. 12 is a flowchart for explaining a beam reporting transmission method according to a second embodiment of the present disclosure.

[0184] Referring to FIG. 12, the base station can transmit multiple CSI report settings to the terminal (S1210). FIG. 12 illustrates a case where N CSI report settings are set to the terminal.

[0185] According to a plurality of CSI reporting settings configured from a base station, the terminal can detect at least one event (S1220). In this case, according to the plurality of CSI reporting settings, the terminal may detect one event or multiple events. The second embodiment assumes a case where the terminal detects two or more events simultaneously (or at close points in time).

[0186] The terminal can determine which CSI reporting setting the beam report to be transmitted from the PUCCH resource will follow until the resource of the first UL channel (i.e., first PUCCH) associated with multiple CSI reporting settings arrives. That is, the terminal can perform the priority determination procedure described above to determine which CSI reporting setting the beam report to be transmitted through the second UL channel (i.e., PUSCH) will follow (S1230).

[0187] For beam reporting according to the determined CSI reporting settings, the terminal can transmit the first UL channel (i.e., first PUCCH) to the base station (S1240). As previously mentioned, one PUCCH resource can be set for the first UL channel (i.e., first PUCCH). That is, one PUCCH resource can be linked to multiple CSI reporting settings.

[0188] Meanwhile, although step (S1230) is depicted in FIG. 12 as being performed before step (S1240), step (S1230) may be performed after step (S1240). That is, before transmitting the first UL channel, only whether to transmit a beam report from the corresponding PUCCH resource may be determined first, and after transmitting the first UL channel, before the step (S1250) of transmitting the second UL channel, it may be determined which CSI report setting to transmit a beam report. This may be useful when an event is detected close to the PUCCH resource for transmitting the first UL channel, or when there is insufficient processing time for priority determination.

[0189] The terminal can transmit a beam report containing an indicator indicating a determined CSI report setting through the second UL channel (i.e., PUSCH) (S1250). Meanwhile, the transmission resource of the second UL channel is a resource allocated by the DCI received from the base station in the case of Mode-A (as exemplified in FIG. 9), and may be a pre-set resource in the case of Mode-B (as exemplified in FIG. 10).

[0190] The base station can check the beam report containing the relevant indicator to determine which CSI reporting setting the beam report corresponds to.

[0191]

[0192] Third Embodiment: Beam Report Transmission (PUCCH) using PUCCH resources linked to multiple CSI report settings

[0193] Multiple CSI reporting settings can be configured on the terminal, and said CSI reporting settings can be associated with a single PUCCH resource. Under such a configuration, the terminal can perform beam reporting selection and payload configuration operations.

[0194] CSI reporting settings can be configured in various forms. For example, periodic CSI reporting or non-periodic CSI reporting can be configured by the CSI reporting settings, and multiple CSI feedbacks based on different reference signals can be configured. Additionally, some of the CSI reporting settings can configure UEI / ED beam reporting. That is, the third embodiment can assume a case where general CSI reporting setting(s) and CSI reporting setting(s) for UEI / ED beam reporting are configured together, and a second UL channel for beam reporting (i.e., PUCCH) is shared by the CSI reporting(s) according to the general CSI reporting setting(s) and the UEI / ED beam reporting(s).

[0195] As a specific example, the first CSI reporting setting may set a precoding matrix indicator (PMI) or channel quality indicator (CQI) reporting related to beamforming, the second CSI reporting setting may set a CQI reporting for the entire bandwidth (i.e., wideband CQI), and the third CSI reporting setting may set a UEI / ED beam reporting. All three CSI reporting settings may be linked to a single PUCCH resource, and the reporting cycles of the three CSI reporting settings may be configured to overlap. In this case, the terminal may determine which CSI reporting setting (or beam report) to transmit according to the first CSI reporting setting or the third CSI reporting setting. For example, the terminal may select and transmit a CSI reporting (or beam report) with a higher priority according to a predefined rule. Alternatively, if supported by the terminal, the terminal may multiplex and transmit at least two CSI reports (or CSI report(s) or beam report(s)).

[0196] Therefore, if two or more triggered CSI reports, periodic CSI report cycles, and beam reports overlap at the same timing, the terminal may select the single CSI report (or beam report) with the highest priority and send it to the PUCCH. In this case, the priority may be determined based on the report type (e.g., periodic CSI report or event-triggered CSI report (or beam report)), the importance of the report content, and / or the report identifier. For example, an event-based Mode-A beam report may have a higher priority than an aperiodic CQI report sent via the PUCCH. Therefore, if two reports conflict at the same time, the terminal may send the event-based Mode-A beam report to the PUCCH and drop the aperiodic CQI report. Additionally, an aperiodic CSI report sent via the PUCCH may have a higher priority than an event-based Mode-B beam report. Therefore, if two reports conflict at the same time, the terminal may transmit the non-periodic CQI report and drop the event-based Mode-B Beam report. Additionally, the event-based Mode-B Beam report may have a higher priority than the semi-persistent CSI report transmitted via PUSCH. Consequently, if two reports conflict at the same time, the terminal may transmit the event-based Mode-B Beam report and drop the semi-persistent CSI report transmitted via PUSCH. As a result, the order of priority may be higher as follows: event-based Mode-A Beam report > non-periodic CSI report transmitted via PUSCH > event-based Mode-B Beam report > semi-persistent CSI report transmitted via PUSCH (i.e., the event-based Mode-A Beam report has the highest priority).

[0197] Meanwhile, event-based Mode-A beam reporting and Mode-B beam reporting can have a higher priority than semi-persistent CSI reports transmitted via PUCCH and periodic CSI reports transmitted via PUCCH.

[0198] As another example, a case may be considered where multiple periodic CSI processes are linked to a single PUCCH resource. In this case, the network may pre-configure priority or grouping information for each CSI process. Depending on such configuration, the terminal may select and transmit only one CSI report (or beam report) from a single PUCCH transmission opportunity. Alternatively, if supported by the terminal, the terminal may multiplex and transmit at least two CSI reports (or CSI report(s) or beam report(s)) together. In a multiplexing scenario, the terminal may combine at least two CSI reports (or CSI report(s) or beam report(s)) into a single codeword and transmit them using a format capable of accommodating a relatively long UCI payload (e.g., PUCCH Format 3 or PUCCH Format 4). However, for the sake of simplicity, it may be assumed below that the terminal transmits only one CSI report (or beam report) at a time, and that the selection is made based on priority criteria.

[0199] Depending on the selected CSI report type, the size and configuration of the PUCCH payload may also vary. The expected number of bits for each CSI report configuration associated with a single PUCCH resource may be predefined, and the PUCCH format may also be configured to match the maximum payload size among the corresponding CSI report configurations. For example, a case may be considered where the first CSI report configuration contains 10 bits of CQI or PMI, the second CSI report configuration contains 20 bits of CSI information, and the third CSI report configuration sets the payload size to 20 bits for Veeam reporting. In this case, the PUCCH resource to accommodate the corresponding CSI reports or Veeam reporting may be allocated in a format that supports a maximum UCI payload of 20 bits (e.g., PUCCH format 3).

[0200] At a specific point in time, if the terminal decides to transmit a CSI report by selecting the first CSI report setting or to transmit a beam report by selecting the third CSI report setting, the UCI to be transmitted may have a length of 10 bits. However, since the payload capacity of the allocated PUCCH resource is 20 bits, the terminal can transmit it by performing zero-padding on the remaining 10 bits. In this way, even if the base station decodes a fixed 20-bit length UCI, it can recognize that the corresponding CSI report (or beam report) is a report according to the first CSI report setting (or the third CSI report setting) by seeing that the latter 10 bits are all set to 0, or at least maintain consistency in the payload length. On the other hand, when transmitting a 20-bit CSI according to the second CSI report setting, zero-padding may not be necessary, and the entire 20 bits can be used as valid information.

[0201] In this way, the method of maintaining the payload size invariantly can provide the advantage of being able to interpret the form of the received UCI at the receiving end without additionally including a separate payload size exchange or report type identifier between the terminal and the base station. However, as another embodiment, optimization may be performed, such as pre-allocating different PUCCH resources for each CSI report setting to reduce the need for zero padding, or adjusting the coding rate to minimize zero padding.

[0202] As a variation of the multi-CSI report configuration scenario described above, a case may be considered in which a terminal is allowed to transmit at least two CSI reports (or CSI report(s) or beam report(s)) all in a single PUCCH. In this case, the terminal may construct a larger payload by concatenating bit sequences corresponding to at least two CSI reports (or CSI report(s) or beam report(s)) in a predefined order, and transmit the payload using PUCCH format 4, etc. At this time, since the boundaries of the bit intervals corresponding to each CSI report can be distinguished according to a predefined bit length, the base station can separate and interpret the CSI reports (or CSI report(s) or beam report(s)) from the received payload.

[0203] Conversely, cases may be considered where the informational volume of a specific CSI report is too large to be included in PUCCH (e.g., subband PMI reports). In such cases, the UE may be designed to transmit only a portion of the CSI report, or to switch the CSI report to PUSCH for transmission. Additionally, if two or more CSI report triggers or CSI report cycles overlap at the same timing, the UE may transmit the single CSI report with the highest priority to PUCCH and switch the remaining CSI reports to PUSCH.

[0204] FIG. 13 is a flowchart for explaining a beam reporting transmission method according to a third embodiment of the present disclosure.

[0205] Referring to FIG. 13, a base station can transmit a plurality of CSI report settings to a terminal (S1310). Here, the plurality of CSI report settings may include at least one first CSI report setting for setting conventional CSI reports and at least one second CSI report setting for setting event-based beam reports. That is, each of the at least one first CSI report setting can set a CSI report, and each of the at least one second CSI report setting can set an event-based beam report.

[0206] According to at least one first CSI report setting configured from the base station, the terminal can generate at least one CSI report (S1320). That is, each of the at least one CSI report generated in step S1320 may include PMI, CQI, and / or RI (rank indicator).

[0207] According to at least one second CSI report setting configured from the base station, the terminal can detect at least one event and generate at least one beam report corresponding to at least one event (S1330). In this case, according to the at least one second CSI report setting, the terminal may detect one event or multiple events.

[0208] Meanwhile, the terminal may transmit a first UL channel (first PUCCH) to the base station for the transmission of at least one beam report according to at least one detected event (S1340). In FIG. 13, for convenience of explanation, the step S1340 of transmitting the first UL channel is shown as being performed after at least one beam report is generated; however, step S1340 may be transmitted after at least one event is detected, or after at least one beam report to be actually reported is generated, as will be described later. It should be noted that, considering these various possibilities, step S1340 in FIG. 13 is shown as a dotted line.

[0209] The terminal determines whether the first UL resource to which the at least one CSI report is to be transmitted and the second UL resource to which the at least one beam report is to be transmitted overlap at least partially, and based on the determination that the first UL resource and the second UL resource overlap, the terminal may select at least one of the at least one CSI report and the at least one beam report according to a priority determination rule (S1350).

[0210] Here, the first UL resource may be a PUCCH resource or a PUSCH resource, and the second UL resource may be a PUCCH resource. That is, the third embodiment may assume a case where at least one CSI report is transmitted via PUCCH or PUSCH and at least one beam report is transmitted via PUCCH.

[0211] The above priority determination rule may be set from the base station to the terminal via RRC signaling or predefined in the technical specifications. For example, the above priority determination rule may be a rule that causes event-based Mode-A beam reports to have a higher priority than aperiodic CSI reports transmitted via PUCCH. Additionally or generally, the above priority determination rule may be a rule that causes event-based Mode-B beam reports to have a higher priority than semi-persistent CSI reports transmitted via PUSCH. Additionally or generally, the above priority determination rule may be a rule that causes aperiodic CSI reports transmitted via PUCCH to have a higher priority than event-based Mode-B beam reports. Additionally or generally, the above priority determination rule may be a rule that causes event-based Mode-A beam reports and event-based Mode-B beam reports to have a higher priority than semi-persistent CSI reports transmitted via PUCCH and periodic CSI reports transmitted via PUCCH.

[0212] Finally, the terminal can transmit the selected at least one report to the base station through the UL resource corresponding to the at least one report among the first UL resource or the second resource (S1360).

[0213] For convenience of explanation, the preceding embodiments have been described individually, but at least two of the preceding embodiments may be applied in combination. For example, the first embodiment and the second embodiment may be applied together.

[0214]

[0215] Hereinafter, a comprehensive terminal-base station procedure including the individual procedures described in the above embodiments is described.

[0216] (Event Detection Phase) The terminal can monitor the quality of the downlink signal in time slot units. The terminal can measure quality indicators such as RSRP, RSRQ, or SINR for a specific reference signal (e.g., SSB or CSI-RS) received from the serving cell, and filter the measured values ​​to evaluate event trigger conditions corresponding to pre-configured CSI reporting setting(s). These CSI reporting setting(s) may include CSI reporting settings for UEI / ED beam reporting. For example, CSI reporting settings for UEI / ED beam reporting may include events corresponding to the quality degradation of the serving beam or events corresponding to the quality improvement of an adjacent beam. The terminal can continuously evaluate event trigger conditions according to multiple CSI reporting settings, and if any one trigger condition is satisfied, the terminal can internally trigger the corresponding event and prepare a subsequent reporting procedure.

[0217] (PUCCH notification stage) The terminal may notify the base station of the occurrence of an event by transmitting a first UL channel (i.e., first PUCCH) immediately after the event occurs or at the nearest pre-designated PUCCH opportunity (i.e., the PUCCH resource associated with the CSI reporting setting(s)). The PUCCH may consist, for example, of a 1-bit flag or a small number of bits. Through the PUCCH, the terminal promptly notifies the "occurrence of a beam reporting event," and, if necessary, may carry additional information such as information distinguishing whether the event occurring in the PUCCH is Event-1 or Event-2, or the reporting readiness status. If multiple CSI reporting settings are associated with a single PUCCH resource, the terminal may prioritize the transmission of the event notification, omitting other periodic CSI reports, etc., at the time of transmitting the event occurrence notification. If event triggers corresponding to multiple CSI reporting settings occur simultaneously at the same time or at close intervals, the terminal may operate to transmit only one beam report at a single reporting opportunity. At this time, the terminal may determine which beam report corresponding to which CSI reporting setting to transmit based on predefined rules or priorities. For example, the terminal may select the beam report corresponding to the most recently occurred event. Alternatively, the terminal may select the beam report corresponding to the CSI reporting setting with the highest priority based on priorities pre-set by the base station. For unselected events, re-reporting may be performed if the trigger condition continues to be satisfied during subsequent reporting opportunities.

[0218] (Second UL Channel Transmission Step) After notifying of the occurrence of an event, the terminal may transmit a beam report containing detailed information through the second UL channel. The second UL channel may be configured as a PUSCH, and the base station may instruct the terminal to transmit the beam report from an allocated resource by issuing a UL grant through the PDCCH (in the case of Mode-A), or instruct the terminal to transmit the beam report from a specific resource pre-configured through an upper layer signal (in the case of Mode-B). That is, in the case of Mode-A, the second UL channel may be transmitted through a resource allocated by dynamic scheduling, and in the case of Mode-B, the second UL channel may be transmitted through a pre-configured resource dedicated to reporting.

[0219] A beam report transmitted via the second UL channel may include an indicator to identify which CSI report configuration triggered the beam report. CSI report configurations associated with the same PUCCH resource may be sorted according to a predefined order (e.g., ascending or descending order of CSI-ReportConfigId), and the terminal may set the indicator based on that order. The base station may determine which CSI report configuration the beam report corresponds to by interpreting the indicator of the received beam report.

[0220] Meanwhile, the case where the second UL channel is configured as PUCCH may also be considered. That is, it may be assumed that a beam report is transmitted via PUCCH rather than PUSCH. In this case, for multiple CSI report configurations associated with a single PUCCH resource, the terminal may select which CSI report or beam report to transmit from the single PUCCH resource according to which CSI report configuration. The terminal may select and transmit only one CSI report or beam report according to priority rules. If supported by the terminal, the terminal may multiplex two or more CSI report(s) and / or beam report(s) and transmit them over a single PUCCH. When multiplexing is applied, the terminal may use a PUCCH format that supports a relatively large UCI payload (e.g., PUCCH format 3 or format 4).

[0221] (Base Station Interpretation and Response Phase) The base station can decode the contents of the received beam report and interpret the beam-related information reported by the terminal. If a new candidate beam is reported, the base station can take appropriate measures, such as downlink beam switching, based on the information. For example, the base station can switch its transmission beam to the highest quality beam reported by the terminal and inform the terminal of the identifier of that beam so that a procedure to synchronize the terminal's reception beam can proceed. Specifically, the base station can use the identifier of the reported beam to prepare for data transmission in the direction of that beam and set the TCI (transmission configuration indication) field in the DCI scheduling the transmission port PDSCH to instruct the terminal to use the new beam. If the beam report indicates "no candidate beams" or if available beams are limited, the base station may maintain the current beam and request additional measurements from the terminal, or prepare higher-level procedures such as cell handover if necessary. The base station determines the link status based on the beam report from the terminal and can transmit an appropriate response signal, such as updating the beam settings via an RRC reconfiguration message or notifying the beam recovery result via a MAC CE (control element). Once all procedures are successfully completed, the terminal and the base station can continue communication through the selected optimal beam to improve link quality.

[0222]

[0223] In the above embodiments, if the base station fails to receive the first UL channel (i.e., first PUCCH) transmitted by the terminal or fails to receive the second UL channel containing the beam report due to an error, the base station may not recognize the change in the terminal's beam state and may maintain the original setting. In such cases, the terminal may re-trigger the same event after a certain period of time to transmit the first UL channel again, or if a specific threshold condition is met, it may consider it a beam failure and perform a separate beam failure recovery procedure (e.g., a RACH-based beam recovery request). Additionally, in the response phase of the base station, the base station may not immediately switch beams and may order the terminal to perform repeated measurements for further verification.

[0224]

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

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

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

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

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

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

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

[0232]

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

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

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

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

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

Claims

1. In the method of the terminal, A step of receiving at least one first CSI (channel state information) report setting and at least one second CSI report setting from a base station, wherein each of the at least one first CSI report setting sets a CSI report and each of the at least one second CSI report setting sets a beam report; A step of generating at least one CSI report based on the above at least one first CSI report setting; A step of detecting at least one event based on the at least one second CSI report setting and generating at least one beam report corresponding to the at least one event; A step of determining whether the first uplink (UL) resource to which the at least one CSI report is to be transmitted and the second UL resource to which the at least one beam report is to be transmitted overlap at least partially; and Based on the determination that the first UL resource and the second UL resource overlap, a step of selecting at least one report among the at least one CSI report and the at least one beam report according to a priority determination rule; and A step comprising transmitting the selected at least one report to the base station through the UL resource corresponding to the at least one report among the first UL resource or the second resource, method.

2. In Claim 1, The above-mentioned first UL resource is a PUCCH (physical uplink control channel) resource or a PUSCH (physical uplink shared channel) resource, and the above-mentioned second UL resource is a PUCCH resource, method.

3. In Claim 1, The above at least one report has the maximum report payload size among the report payload sizes according to the above at least one first CSI report setting and the above at least one second CSI report setting, method.

4. In Claim 3, If the size of the valid information of at least one report is smaller than the maximum report payload size, the at least one report additionally includes zero-padding bits in the valid information to satisfy the maximum report payload size. method.

5. In Claim 1, The above priority determination rule is established through RRC (radio resource control) signaling from the base station or is predefined in technical specifications, method.

6. In Claim 1, The above priority determination rule ensures that event-based Mode-A beam reporting has a higher priority than aperioditic CSI reporting transmitted via PUCCH, method.

7. In Claim 1, The above priority determination rule ensures that event-based Mode-B Beam reporting has a higher priority than semi-persistent CSI reporting transmitted via PUSCH, method.

8. In Claim 1, The above priority determination rule ensures that non-periodic CSI reports transmitted via PUCCH have a higher priority than event-based Mode-B beam reports, method.

9. In Claim 1, The above priority determination rule ensures that event-based Mode-A beam reporting and event-based Mode-B beam reporting have higher priority than semi-persistent CSI reporting to be transmitted via PUCCH and periodic CSI reporting to be transmitted via PUCCH. method.

10. Regarding the method of base stations, A step of transmitting at least one first CSI (channel state information) report setting and at least one second CSI report setting to a terminal, wherein each of the at least one first CSI report setting sets a CSI report and each of the at least one second CSI report setting sets a beam report; and The method includes the step of receiving from the terminal at least one report selected from at least one CSI report based on at least one first CSI report setting and at least one beam report based on at least one second CSI report setting. The at least one report is selected by the terminal according to a priority determination rule from the at least one CSI report and the at least one beam report, based on the fact that the first uplink (UL) resource to which the at least one CSI report is received and the second UL resource to which the at least one beam report is received overlap at least partially, and the at least one report is transmitted to the terminal through the UL resource corresponding to the at least one report among the first UL resource or the second resource. method.

11. In Claim 10, The above-mentioned first UL resource is a PUCCH (physical uplink control channel) resource or a PUSCH (physical uplink shared channel) resource, and the above-mentioned second UL resource is a PUCCH resource, method.

12. In Claim 10, The above at least one report has the maximum report payload size among the report payload sizes according to the above at least one first CSI report setting and the above at least one second CSI report setting, method.

13. In Claim 10, The above priority determination rule is set to the terminal via RRC (radio resource control) signaling or is predefined in technical specifications, method.

14. In Claim 10, The above priority determination rule ensures that event-based Mode-A beam reporting has a higher priority than aperioditic CSI reporting transmitted via PUCCH, method.

15. In Claim 10, The above priority determination rule ensures that event-based Mode-B Beam reporting has a higher priority than semi-persistent CSI reporting transmitted via PUSCH, method.

16. In Claim 10, The above priority determination rule ensures that non-periodic CSI reports transmitted via PUCCH have a higher priority than event-based Mode-B beam reports, method.

17. In Claim 10, The above priority determination rule ensures that event-based Mode-A beam reporting and event-based Mode-B beam reporting have higher priority than semi-persistent CSI reporting to be transmitted via PUCCH and periodic CSI reporting to be transmitted via PUCCH. method.

18. In a terminal comprising at least one processor, The above at least one processor is the terminal: A step of receiving at least one first CSI (channel state information) report setting and at least one second CSI report setting from a base station, wherein each of the at least one first CSI report setting sets a CSI report and each of the at least one second CSI report setting sets a beam report; A step of generating at least one CSI report based on the above at least one first CSI report setting; A step of detecting at least one event based on the at least one second CSI report setting and generating at least one beam report corresponding to the at least one event; A step of determining whether the first uplink (UL) resource to which the at least one CSI report is to be transmitted and the second UL resource to which the at least one beam report is to be transmitted overlap at least partially; and Based on the determination that the first UL resource and the second UL resource overlap, a step of selecting at least one report among the at least one CSI report and the at least one beam report according to a priority determination rule; and Performing the step of transmitting the selected at least one report to the base station through the UL resource corresponding to the at least one report among the first UL resource or the second resource. Terminal.

19. In Claim 18, The above-mentioned first UL resource is a PUCCH (physical uplink control channel) resource or a PUSCH (physical uplink shared channel) resource, and the above-mentioned second UL resource is a PUCCH resource, Terminal.

20. In Claim 1, The above at least one report has the maximum report payload size among the report payload sizes according to the above at least one first CSI report setting and the above at least one second CSI report setting, Terminal.

Images