Method and apparatus for two-step beam reporting in communication system

Abstract

A method and an apparatus for two-step beam reporting in a communication system are disclosed. The method of a terminal comprises the steps of: performing a first beam quality measurement operation on the current beam; performing a second beam quality measurement operation on one or more candidate beams; determining whether an event condition is satisfied on the basis of a result of the first beam quality measurement operation and the results of the second beam quality measurement operation; transmitting, to a base station, a first uplink (UL) signal in a first UL resource if the event condition is satisfied; and transmitting, to the base station, a second UL signal including beam report information in a second UL resource.

Description

Method and device for two-stage beam reporting in a communication system

[0001] The present disclosure relates to a beam reporting technique, and more particularly, to a technique for reporting beam information based on a plurality of UL (uplink) transmissions in a communication system.

[0002] The development of next-generation communication systems (e.g., new radio (NR) communication systems, sixth generation (6G) communication systems, etc.) is becoming increasingly important as infrastructure for the proliferation of diverse future convergence services. Next-generation communication systems can support not only conventional mobile communication frequency bands, but also millimeter wave bands, terahertz bands, and upper-mid bands. Next-generation communication systems can support a wider range of performance indicators and scenarios than conventional communication systems (e.g., long term evolution (LTE) communication systems). In communications using high-frequency bands, technologies for stably managing terminal beams may be required to support beamforming-based transmission, and technologies for optimizing the overhead required for beam management and beam switching delay may also be required.

[0003] The purpose of the present disclosure to solve the above problems is to provide a method and device for two-stage beam reporting in a communication system.

[0004] According to embodiments of the present disclosure for achieving the above object, a method of a terminal includes the steps of: performing a first beam quality measurement operation for a current beam; performing a second beam quality measurement operation for one or more candidate beams; determining whether an event condition is satisfied based on a result of the first beam quality measurement operation and a result of the second beam quality measurement operation; transmitting a first UL (uplink) signal to a base station in a first UL (uplink) resource when the event condition is satisfied; and transmitting a second UL signal including beam report information to the base station in a second UL resource, wherein the current beam corresponds to transmission configuration information (TCI) indicated to the terminal, and the one or more candidate beams correspond to one or more beam quality measurement resources determined based on configuration information received from the base station.

[0005] The first UL signal may be a physical uplink control channel (PUCCH), the PUCCH may include uplink control information (UCI), and the UCI may include information requesting the second UL resource to the base station.

[0006] The second UL resource may be a PUSCH (physical uplink shared channel) resource scheduled by DCI (downlink control information) received from the base station, the second UL signal may be a PUSCH, and the DCI may include information indicating that beam reporting information is to be included in the PUSCH.

[0007] The first UL signal may be a PUCCH, the PUCCH may include a UCI, and the UCI may include information informing the base station whether the terminal transmits the second UL signal on the second UL resource.

[0008] The second UL resource may be a PUSCH resource having a mutual relationship with the first UL resource, the second UL signal may be a PUSCH, the second UL resource may be mapped to a time resource that is at least N symbols later than the first UL resource, and N may be a natural number.

[0009] The above PUSCH may not include UL-SCH (shared channel).

[0010] The repetition periods of the first UL resource and the second UL resource can be determined based on the same period value.

[0011] The first beam quality measurement operation may include an operation of measuring L1-RSRP (layer1-reference signal received power) for the current beam, and the second beam quality measurement operation may include an operation of measuring L1-RSRP for the one or more candidate beams.

[0012] The beam report information may include at least one of a beam quality measurement result regarding the current beam or a beam quality measurement result regarding the one or more candidate beams.

[0013] The above TCI may be a DL (downlink) TCI, and the one or more beam quality measurement resources corresponding to the one or more candidate beams may include at least one of a SSB (synchronization signal block) resource or a CSI (channel state information)-RS (reference signal) resource.

[0014] According to embodiments of the present disclosure for achieving the above object, a terminal includes at least one processor, wherein the at least one processor causes the terminal to perform a first beam quality measurement operation for a current beam; perform a second beam quality measurement operation for one or more candidate beams; determine whether an event condition is satisfied based on a result of the first beam quality measurement operation and a result of the second beam quality measurement operation; and, when the event condition is satisfied, transmit a first UL (uplink) signal to a base station in a first UL resource; and transmit a second UL signal including beam report information to the base station in a second UL resource, wherein the current beam corresponds to transmission configuration information (TCI) indicated to the terminal, and the one or more candidate beams correspond to one or more beam quality measurement resources determined based on configuration information received from the base station.

[0015] The first UL signal may be a physical uplink control channel (PUCCH), the PUCCH may include uplink control information (UCI), and the UCI may include information requesting the second UL resource to the base station.

[0016] The second UL resource may be a PUSCH (physical uplink shared channel) resource scheduled by DCI (downlink control information) received from the base station, the second UL signal may be a PUSCH, and the DCI may include information indicating that beam reporting information is to be included in the PUSCH.

[0017] The first UL signal may be a PUCCH, the PUCCH may include a UCI, and the UCI may include information informing the base station whether the terminal transmits the second UL signal on the second UL resource.

[0018] The second UL resource may be a PUSCH resource having a mutual relationship with the first UL resource, the second UL signal may be a PUSCH, the second UL resource may be mapped to a time resource that is at least N symbols later than the first UL resource, and N may be a natural number.

[0019] The above PUSCH may not include UL-SCH (shared channel).

[0020] The repetition periods of the first UL resource and the second UL resource can be determined based on the same period value.

[0021] The first beam quality measurement operation may include an operation of measuring L1-RSRP (layer1-reference signal received power) for the current beam, and the second beam quality measurement operation may include an operation of measuring L1-RSRP for the one or more candidate beams.

[0022] The beam report information may include at least one of a beam quality measurement result regarding the current beam or a beam quality measurement result regarding the one or more candidate beams.

[0023] The above TCI may be a DL (downlink) TCI, and the one or more beam quality measurement resources corresponding to the one or more candidate beams may include at least one of a SSB (synchronization signal block) resource or a CSI (channel state information)-RS (reference signal) resource.

[0024] According to the present disclosure, a terminal can perform a beam quality measurement operation for one or more beams, and if the beam quality measurement result satisfies an event condition, transmit a first UL (uplink) signal to a base station from a first UL resource. After transmitting the first UL signal, the terminal can transmit a second UL signal including beam report information to the base station from a second UL resource. According to the above-described method, the overhead required for beam management can be reduced, and the beam switching delay time can be minimized.

[0025] Figure 1 is a conceptual diagram illustrating embodiments of a communication system.

[0026] Figure 2 is a block diagram illustrating embodiments of the device.

[0027] Figure 3 is a conceptual diagram illustrating embodiments of a TCI instruction method by DCI.

[0028] Figure 4 is a conceptual diagram illustrating embodiments of a two-step beam reporting method.

[0029] Figure 5 is a conceptual diagram illustrating embodiments of a two-step beam reporting method that considers ineffective resources.

[0030] Figure 6 is a conceptual diagram illustrating embodiments of a two-step beam reporting method considering ineffective resources.

[0031] Figure 7 is a conceptual diagram illustrating embodiments of a two-step beam reporting method that considers ineffective resources.

[0032] Figure 8 is a conceptual diagram illustrating embodiments of a method for setting up a first UL resource.

[0033] Figure 9 is a conceptual diagram illustrating embodiments of a method for setting up a first UL resource.

[0034] Figure 10 is a conceptual diagram illustrating embodiments of a method for setting up a second UL resource.

[0035] This disclosure may be subject to various modifications and various embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the disclosure to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the disclosure.

[0036] While terms such as "first" and "second" may be used to describe various components, these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present disclosure, a first component could be referred to as a "second component," and similarly, a second component could also be referred to as a "first component." The term "and / or" encompasses any combination of multiple related items or any one of multiple related items.

[0037] In embodiments of the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.” Furthermore, in embodiments of the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.”

[0038] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0039] The terminology used in this disclosure is only used to describe specific embodiments and is not intended to limit the present disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, it should be understood that the terms "comprises" or "has" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not preclude the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

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

[0041] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. In order to facilitate an overall understanding in describing the present disclosure, identical reference numerals will be used for identical components in the drawings, and redundant descriptions of identical components will be omitted.

[0042] A communication system to which embodiments according to the present disclosure are applied will be described. The communication system may be a 4G communication system (e.g., a long-term evolution (LTE) communication system, LTE-A communication system), a 5G communication system (e.g., a new radio (NR) communication system), a 6G communication system, etc. The 4G communication system can support communication in a frequency band below 6 GHz, and the 5G communication system can support communication in a frequency band above 6 GHz as well as a frequency band below 6 GHz. The communication system to which embodiments according to the present disclosure are applied is not limited to the contents described below, and the embodiments according to the present disclosure can be applied to various communication systems. Here, the communication system may be used with the same meaning as a communication network, and “LTE” may indicate a “4G communication system,” an “LTE communication system,” or an “LTE-A communication system,” and “NR” may indicate a “5G communication system” or an “NR communication system.”

[0043] In an embodiment, “an operation (e.g., a transmission operation) is set to a communication node” may mean that “setting information for the operation (e.g., an information element, a parameter)” and / or “information instructing performance of the operation” are signaled to the communication node. In other words, “an operation (e.g., a transmission operation) is set to a communication node” may mean that the communication node receives “setting information for the operation (e.g., an information element, a parameter)” and / or “information instructing performance of the operation.” “An information element (e.g., a parameter) is set to a communication node” may mean “the information element is signaled to the communication node (e.g., the communication node receives the information element).” The signaling may be at least one of SI (system information) signaling (e.g., transmission of a system information block (SIB) and / or a master information block (MIB)), RRC signaling (e.g., transmission of RRC parameters and / or upper layer parameters), MAC CE (control element) signaling, or PHY signaling (e.g., transmission of DCI (downlink control information), UCI (uplink control information), and / or SCI (sidelink control information)).

[0044] In this disclosure, "time" may refer to a time point, and "time point" may refer to time. "Time" and "point point" may be used interchangeably. The reception time of a signal or channel may refer to the start time of reception or the end time of reception. The transmission time of a signal or channel may refer to the start time of transmission or the end time of transmission.

[0045] Figure 1 is a conceptual diagram illustrating embodiments of a communication system.

[0046] 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). In addition, the communication system (100) may further include a core network (e.g., a serving-gateway (S-GW), a packet data network (PDN)-gateway (P-GW), a mobility management entity (MME)). If the communication system (100) is a 5G communication system (e.g., a new radio (NR) system), the core network may include an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc.

[0047] A plurality of communication nodes (110 to 130) can support a communication protocol (e.g., LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.) specified in the 3GPP (3rd generation partnership project) standard. The plurality of communication nodes (110 to 130) may 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 plurality of communication nodes may mean an apparatus or a device. The embodiments may be performed by a device or apparatus. The structure of the apparatus (e.g., device) may be as follows.

[0048] Figure 2 is a block diagram illustrating embodiments of the device.

[0049] Referring to FIG. 2, the device (200) may include at least one processor (210), a memory (220), and a transmission / reception device (230) that is connected to a network and performs communication. In addition, the device (200) may further include an input interface device (240), an output interface device (250), a storage device (260), etc. Each component included in the device (200) may be connected by a bus (270) and communicate with each other.

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

[0051] 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 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 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 within the cell coverage of the third base station (110-3). The first terminal (130-1) may be within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be within the cell coverage of the fifth base station (120-2).

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

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

[0054] Meanwhile, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may operate in a different frequency band or may operate in the same frequency band. Each of the plurality of 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 the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to the core network via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of 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.

[0055] Additionally, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may support MIMO transmission (e.g., single user (SU)-MIMO, multi user (MU)-MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, device to device communication (D2D) (or, proximity services (ProSe)), Internet of Things (IoT) 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 scheme, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) by the SU-MIMO scheme. Alternatively, the second base station (110-2) can transmit signals 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 signals from the second base station (110-2) based on the MU-MIMO method.

[0056] 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 scheme, 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) based on the CoMP scheme. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive a signal with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) within its cell coverage based on the CA scheme. Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can control D2D 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 D2D under the control of the second base station (110-2) and the third base station (110-3).

[0057] In a communication system (e.g., NR communication system, 6G communication system), the numerology applied to the physical signal and channel can be variable. The numerology can be variable to meet various technical requirements of the communication system. In a communication system to which CP (cyclic prefix)-based OFDM waveform technology is applied, the numerology can include subcarrier spacing and CP length (or CP type). Table 1 may be a first embodiment of a numerology configuration for a CP-OFDM-based communication system. Adjacent subcarrier spacings can have a relationship of exponentiation of 2 with each other, and the CP length can be scaled at the same rate as the OFDM symbol length. At least some of the numerologies in Table 1 may be supported depending on the frequency band in which the communication system operates. In addition, the communication system may additionally support numerologies not listed in Table 1. Additional CP types (e.g., extended CP) not listed in Table 1 may be supported for specific subcarrier spacing (e.g., 60 kHz).

[0058]

[0059] Below, the frame structure of a communication system will be described. In the time domain, elements (e.g., resource elements) that constitute the frame structure may include subframes, slots, mini-slots, and symbols. A subframe may be used as a unit for transmission, measurement, etc., and the length of a subframe may have a fixed value (e.g., 1 ms) regardless of the subcarrier spacing. A slot may include consecutive symbols (e.g., 14 OFDM symbols). The length of a slot may be variable, unlike the length of a subframe. For example, the length of a slot may be inversely proportional to the subcarrier spacing.

[0060] A slot can be used as a unit for transmission, measurement, scheduling, resource configuration, timing (e.g., scheduling timing, hybrid automatic repeat request (HARQ) timing, channel state information (CSI) measurement and reporting timing, etc.). The length of the actual time resource used for transmission, measurement, scheduling, resource configuration, etc. may or may not match the length of the slot. A minislot can include consecutive symbol(s), and the length of a minislot can be shorter than the length of a slot. A minislot can be used as a unit for transmission, measurement, scheduling, resource configuration, timing, etc. A minislot (e.g., minislot length, minislot boundary, etc.) can be predefined in a technical specification. Alternatively, a minislot (e.g., minislot length, minislot boundary, etc.) can be configured (or instructed) to a terminal. It can be configured (or instructed) to a terminal that a minislot is used when a specific condition is satisfied.

[0061] A base station can schedule a data channel (e.g., a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), a physical sidelink shared channel (PSSCH)) using some or all of the symbols constituting a slot. In particular, a data channel can be transmitted using a part of a slot for Ultra Reliable Low Latency Communication (URLLC) transmission, unlicensed band transmission, transmission in a situation where NR communication systems and LTE communication systems coexist, analog beamforming-based multi-user scheduling, etc. In addition, the base station can schedule a data channel using a plurality of slots. In addition, the base station can schedule a data channel using at least one mini-slot.

[0062] In the frequency domain, elements that constitute a frame structure may include resource blocks (RBs), subcarriers, etc. One RB may include consecutive subcarriers (e.g., 12 subcarriers). The number of subcarriers constituting one RB may be constant regardless of the numerology. In this case, the bandwidth occupied by one RB may be proportional to the subcarrier spacing of the numerology. An RB may be used as a transmission and resource allocation unit for data channels, control channels, etc. Resource allocation for a data channel may be performed in units of RBs or RB groups (e.g., resource block groups (RBGs)). One RBG may include one or more consecutive RBs. Resource allocation for a control channel may be performed in units of control channel elements (CCEs). In the frequency domain, one CCE may include one or more RBs.

[0063] In a communication system (e.g., an NR communication system), the unit time resource (hereinafter referred to as a "slot") described above may be composed of a combination of one or more of a downlink (DL) interval, a flexible interval (or an unknown interval), and an uplink (UL) interval. Each of the DL interval, the flexible interval, and the UL interval may be composed of one or more consecutive symbols. The flexible interval may be located between a DL interval and an UL interval, between a first DL interval and a second DL interval, between a first UL interval and a second UL interval, etc. When a flexible interval is inserted between a DL interval and a UL interval, the flexible interval may be used as a guard interval.

[0064] A slot may include one or more flexible periods. Alternatively, a slot may not include a flexible period. A terminal may perform a predefined operation in a flexible period. Alternatively, the terminal may perform an operation that is semi-statically or periodically configured by a base station in the flexible period. For example, the operation that is periodically configured by the base station may include a physical downlink control channel (PDCCH) monitoring operation, a synchronization signal block (SSB) reception and measurement operation, a CSI-RS (reference signal) reception and measurement operation, a DL SPS (semi-persistent scheduling) PDSCH reception operation, a sounding reference signal (SRS) transmission operation, a physical random access channel (PRACH) transmission operation, a periodically configured PUCCH transmission operation, a PUSCH transmission operation according to a configured grant (CG), etc. A flexible symbol may be overridden by a DL symbol or an UL symbol. When a flexible symbol is overridden by a DL symbol or an UL symbol, the terminal may perform a new operation instead of the existing operation on the flexible symbol (e.g., the overridden flexible symbol).

[0065] In the present disclosure, SSB may refer to a set of signals including a synchronization signal and / or a broadcast channel. The synchronization signal may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), etc., and the broadcast channel may include a physical broadcast channel (PBCH). The SSB may further include a reference signal. The reference signal (e.g., a reference signal included in the SSB) may refer to a demodulation reference signal (DM-RS), a CSI-RS, a tracking reference signal (TRS), a positioning reference signal (PRS), a phase tracking reference signal (PT-RS), etc. for decoding the PBCH. In an NR communication system, the SSB may refer to a synchronization signal / physical broadcast channel (SS / PBCH) block. The SSB may be transmitted periodically, and one or more SSB(s) may be repeatedly transmitted in one period.

[0066] The format of a unit time resource (hereinafter referred to as "slot format") can be semi-statically set by higher layer signaling (e.g., radio resource control (RRC) signaling). Information indicating a semi-static slot format can be included in system information, and the semi-static slot format can be set cell-specifically. In addition, the semi-static slot format can be additionally set for each terminal through terminal-specific higher layer signaling (e.g., RRC signaling). A flexible symbol of a cell-specifically set slot format can be overridden to a DL symbol or an UL symbol by terminal-specific higher layer signaling. In addition, the slot format can be dynamically indicated by physical layer signaling (e.g., a slot format indicator (SFI) included in downlink control information (DCI)). A semi-statically set slot format can be overridden by a dynamically indicated slot format. For example, a flexible symbol set to semi-fixed can be overridden by SFI to a DL symbol or an UL symbol.

[0067] A terminal can perform DL operation, UL operation, sidelink operation, etc. in a bandwidth part. A bandwidth part can be defined as a set of consecutive RBs (e.g., physical resource blocks (PRBs)) in a frequency domain having a specific numerology. One numerology can be used for signal transmission (e.g., transmission of a control channel or a data channel) in one bandwidth part. In the present disclosure, "signal" may mean any physical signal and channel when used in a broad sense. A terminal performing an initial access procedure can obtain configuration information of an initial bandwidth part from a base station through system information. A terminal operating in an RRC connected state can obtain configuration information of a bandwidth part from a base station through terminal-specific upper layer signaling.

[0068] The configuration information of the bandwidth portion may include information about the numerology and / or RB set applied to the bandwidth portion. At least one of the bandwidth portion(s) configured for the terminal may be activated. For example, one UL bandwidth portion and one DL bandwidth portion may each be activated within one carrier. In a time division duplex (TDD)-based communication system, a pair of UL bandwidth portions and DL bandwidth portions may be activated. The base station may configure multiple bandwidth portions for the terminal within one carrier and switch the active bandwidth portion of the terminal.

[0069] In embodiments, "a frequency band (e.g., a carrier, a bandwidth portion, a set of RBs, a listen before talk (LBT) subband, a guard band, etc.) is activated" may mean "a base station or a terminal is in a state where it can transmit and receive signals using the frequency band." In addition, "a frequency band is activated" may mean "a state where an RF (radio frequency) filter (e.g., a band-pass filter) of a transceiver is operating including the frequency band."

[0070] In embodiments, RB may mean CRB (common RB). Alternatively, RB may mean PRB or VRB (virtual RB). In a communication system (e.g., NR communication system), CRB may mean RB that constitutes a set of consecutive RBs (e.g., common RB grid) based on a reference frequency (e.g., point A). Carriers, bandwidth portions, etc. may be arranged on the common RB grid. In other words, carriers, bandwidth portions, etc. may be configured as CRB(s). RBs or CRBs that constitute bandwidth portions may be referred to as PRBs, and within bandwidth portions, CRB indices may be appropriately converted to PRB indices. In embodiments, RB may mean IRB (interlace RB).

[0071] The PDCCH can be used to transmit DCI or DCI formats to a terminal. The minimum resource unit constituting the PDCCH can be a resource element group (REG). For example, an REG can be composed of one RB in the frequency domain and one OFDM symbol in the time domain. DM-RS for decoding the PDCCH can be mapped to some of the REs constituting the REG, and control information (e.g., modulated DCI) can be mapped to the remaining REs. A PDCCH candidate can be composed of one CCE or aggregated CCEs. A CCE can be composed of multiple REGs. In an NR communication system, CCE aggregation levels 1, 2, 4, 8, and 16 can be supported, and a CCE can be composed of six REGs.

[0072] A CORESET (control resource set) may be a resource region in which a terminal performs blind decoding of a PDCCH. A CORESET may be composed of multiple REGs. A CORESET may be composed of one or more RBs in the frequency domain and one or more symbols (e.g., OFDM symbols) in the time domain. The symbols constituting a CORESET may be consecutive in the time domain. The RBs constituting a CORESET may be consecutive or non-contiguous in the frequency domain. One DCI (e.g., one DCI format, one PDCCH) may be transmitted within a CORESET. Multiple CORESETs may be configured from a cell perspective or a terminal perspective, and the time-frequency resource regions to which the multiple CORESETs are mapped may or may not overlap with each other.

[0073] A CORESET may be set in a terminal during the initial access procedure. For example, a CORESET may be set in a terminal by an initial access signal (e.g., PBCH or system information transmitted via PBCH). The ID (identifier) ​​of the CORESET set by the initial access signal may be 0. The CORESET set by the initial access signal may be referred to as CORESET 0. A terminal operating in an RRC idle state may perform a monitoring operation in CORESET 0 to receive the first PDCCH in the initial access procedure. Not only a terminal operating in an RRC idle state but also a terminal operating in an RRC connected state may perform a monitoring operation in CORESET 0. In addition to system information transmitted via an initial access signal (e.g., PBCH), a CORESET may be set in a terminal by other system information (e.g., SIB1 (system information block type 1)). For example, a terminal may receive SIB1 containing configuration information of CORESET for receiving a random access response (e.g., Msg2). CORESET may be configured in the terminal by terminal-specific higher layer signaling (e.g., RRC signaling).

[0074] A search space may refer to a set of candidate resource regions where PDCCHs can be transmitted. The UE may perform blind decoding on each PDCCH candidate within a predefined search space or a search space established by the base station. The UE may determine whether the PDCCH has been transmitted to itself by performing a cyclic redundancy check (CRC) on the blind decoding results. If the PDCCH is determined to be intended for the UE, the UE may receive the PDCCH.

[0075] One or more search spaces may constitute a search space set. The search spaces may be defined / configured for each CCE aggregation level, and the search space set may refer to a search space for each CCE aggregation level or a sum of search spaces for all CCE aggregation levels. For each CCE aggregation level, the PDCCH candidate may be composed of CCE(s) selected by a predefined hash function within a CORESET or a search space occasion. In an embodiment, the "search space set" may refer to a "search space."

[0076] A search space set can be logically associated (e.g., combined) with one CORESET. One CORESET can be logically associated with one or more search space sets. A common search space set configured via PBCH can be used to monitor a DCI scheduling a PDSCH for transmitting SIB1. The ID of the common search space set configured via PBCH can be set to 0. In other words, the common search space set configured via PBCH can be defined as a type 0 PDCCH common search space set or search space set #0. Search space set #0 can be logically associated with CORESET 0.

[0077] The search space set can be divided into a common search space set and a UE-specific search space set depending on the purpose or terminal operation. In the common search space set, common DCI or UE-specific DCI (e.g., UE-specific DCI) can be transmitted, and in the UE-specific search space set (e.g., UE-specific search space set), UE-specific DCI can be transmitted. For example, the common DCI can include resource allocation information of the PDSCH including system information, paging messages, etc., power control commands, slot format indicators (SFIs), and / or preemption indicators. The UE-specific DCI can include resource allocation information of the PDSCH and / or resource allocation information of the PUSCH. Depending on the purpose, multiple DCI formats can be defined, and the multiple DCI formats can be distinguished at the terminal by the DCI payload, DCI fields, DCI sizes, and / or radio network temporary identifiers (RNTIs).

[0078] In the present disclosure, a common search space may be referred to as a CSS (common search space), and a set of common search spaces may be referred to as a CSS set. A terminal-specific search space may be referred to as a USS (UE-specific search space), and a set of terminal-specific search spaces may be referred to as a USS set.

[0079] The terminal can assume that the PDCCH DM-RS has a QCL (quasi co-location) relationship with a signal (e.g., SSB, CSI-RS, PDSCH DM-RS, PDCCH DM-RS, etc.). The PDCCH DM-RS can refer to a DM-RS used for modulation and / or demodulation of the PDCCH. The PDSCH DM-RS can refer to a DM-RS used for modulation and / or demodulation of the PDSCH. Since the PDCCH has the same antenna port as the PDCCH DM-RS, the PDCCH and the PDCCH DM-RS can have a QCL relationship with each other. Through the QCL assumption, the terminal can obtain information about the large-scale propagation characteristics of the wireless channel experienced by the PDCCH and PDCCH DM-RS, and can utilize the large-scale propagation characteristics of the wireless channel for channel estimation, reception beamforming, etc. The QCL parameter may include at least one of a delay spread, a Doppler spread, a Doppler shift, an average gain, an average delay, or a spatial Rx parameter. The spatial Rx parameter may correspond to at least one characteristic of a receive beam, a receive channel spatial correlation, or a transmit / receive beam pair. The spatial Rx parameter may be referred to as "spatial QCL." The PDCCH may be used to mean including a PDCCH DM-RS. That the PDCCH has a QCL relationship with a certain signal may mean that the DM-RS of the PDCCH has a QCL relationship with the certain signal. A signal having a QCL relationship with the PDCCH or a resource of the signal may be referred to as a QCL source, a QCL source signal, a QCL source resource, etc.

[0080] PDCCHs transmitted in the same CORESET (e.g., a search space set corresponding to the same CORESET, a PDCCH monitoring occasion, etc.) may have the same QCL relationship. In other words, a unit of a set in which a UE assumes the same QCL may be a CORESET, and the QCL assumptions may be independent for each CORESET. In an embodiment, each of a QCL and a QCL source of a CORESET may mean the QCL and a QCL source of a PDCCH received through the corresponding CORESET. Exceptionally, different QCL assumptions may be applied to search space sets corresponding to a single CORESET. For example, a search space set for monitoring RA (random access)-RNTI (e.g., a type 1 CSS set) and a search space set other than the search space set may have different QCL relationships.

[0081] The QCL relationship or QCL assumption (e.g., QCL source, QCL type, etc.) of a CORESET can be determined by a predefined method. For example, a UE can assume that a PDCCH DM-RS received through a certain CORESET or a certain search space set has a QCL relationship with respect to an SSB and / or CSI-RS selected during an initial access or random access procedure and a predefined QCL type. A QCL type can mean a set of one or more QCL parameters. The QCL relationship or QCL assumption (e.g., QCL source, QCL type, etc.) of a CORESET can be signaled from a base station to a UE (e.g., RRC signaling, MAC (medium access control) CE (control element) signaling, DCI signaling, a combination of the above signaling, etc.). In other words, the base station can set a transmission configuration information (TCI) state for a CORESET to the UE. In general, a TCI state may include at least one of an ID of a signal having a QCL relationship with a DM-RS of a physical channel to which the TCI is applied (e.g., a PDCCH DM-RS) (e.g., a QCL source of the PDCCH DM-RS, a QCL source resource) or a QCL type for the signal. For example, a base station may configure one or more TCI state candidates for each CORESET to a terminal via RRC signaling, and may indicate (e.g., configure) one TCI state used for CORESET monitoring of the terminal among the one or more TCI state candidates via MAC signaling (or DCI signaling). If there is only one TCI state candidate configured by RRC signaling, the MAC signaling procedure (or DCI signaling procedure) may be omitted.The terminal can perform PDCCH monitoring and reception operations for the corresponding CORESET based on TCI state setting information received from the base station.

[0082] In the present disclosure, the TCI state may be conveniently referred to as TCI. While TCI may generally refer to a broad concept including a beam or signaling information corresponding to a beam, it may be conveniently used in the present disclosure in a meaning corresponding to a beam. DL TCI, or a TCI for DL ​​signal reception, may correspond to a reception beam, and UL TCI, or a TCI for UL signal transmission, may correspond to a transmission beam. A transmission beam may refer to spatial relation information, a transmission spatial filter, etc.

[0083] Meanwhile, in communication systems, beam operation in high-frequency and low-frequency bands can differ. In low-frequency bands (e.g., bands below 6 GHz), signal path loss due to the channel is relatively small, so signals can be transmitted and received using beams with wide beamwidths. Control channel transmission can cover the entire cell (or sector) with a single beam. In high-frequency bands (e.g., bands above 6 GHz) where signal path loss is high, beamforming using large antennas can be used to extend signal reach. Beamforming can be applied not only to data channels but also to common signal and control channels. A communication node (e.g., a base station) can form a beam with a narrow beamwidth through multiple antennas and transmit and receive signals multiple times using multiple beams with different directivity in different directions to cover the entire spatial area of ​​a cell (or sector). This operation of repeatedly transmitting signals using multiple beams across multiple time resources can be referred to as beam sweeping. A system that transmits signals using multiple beams with narrow beamwidths may be referred to as a multi-beam system.

[0084] In a multi-beam system, the beams of a terminal can be managed by a base station. The terminal can measure beam quality for a received signal (e.g., SSB, CSI-RS, etc.) and report the beam quality measurement results to the base station. For example, the terminal can calculate beam quality measurements such as RSRP (reference signal received power) (e.g., L1 (layer1)-RSRP) and SINR (signal-to-interference-plus-noise ratio) for each beam (e.g., each signal, each resource), and report optimal beam(s) and / or measurement value(s) corresponding to the optimal beam(s) to the base station. The terminal can report beam index(es) corresponding to the measurement value(s) to the base station. The beam index can mean information about SSB resources, CSI-RS resources, etc. (e.g., SSB resource indicator, CSI-RS resource indicator, etc.). Information on beam indexes may be included in CSI, and the CSI may be transmitted through an uplink channel such as PUCCH, PUSCH, etc. The base station may determine a transmission beam for the terminal based on beam index(es) and / or beam quality measurement information (e.g., beam quality measurement value(s)) reported from the terminal. The base station may set a TCI state for reception of physical signals and channels (e.g., PDCCH, PDSCH, CSI-RS, PUCCH, PUSCH, SRS, PRACH, etc.) of the terminal based on beam index(es) and / or beam quality measurement information (e.g., beam quality measurement value(s)) reported from the terminal.

[0085] A multi-beam can be formed by a plurality of TRPs and / or panels. In the present disclosure, TRPs and panels may be collectively referred to as TRPs. TRPs may be arranged based on different spatial locations, antenna shapes, boresights, etc. Different beams (e.g., a transmit beam, a receive beam, a transmit / receive beam pair) may be formed on each channel formed between TRPs and a terminal. A base station may perform multi-beam transmission using multiple TRPs. Transmission reliability may be improved by beam selection gain or beam diversity gain. A multi-TRP transmission scheme may be referred to as coordinated multipoint (CoMP). TRPs participating in multi-TRP transmission may belong to the same base station or the same serving cell. Alternatively, TRPs participating in multi-TRP transmission may belong to multiple base stations or multiple serving cells. Ideal backhaul and non-ideal backhaul may be considered as backhaul environments between TRPs. Joint scheduling may be difficult to apply between TRPs connected by non-ideal backhauls.

[0086] The PDCCH reception beam (e.g., TCI) and the PDSCH reception beam (e.g., TCI) of the terminal can be individually managed by the base station. The TCI of the PDCCH can be set for the CORESET corresponding to the PDCCH. The terminal can perform PDCCH monitoring and reception operations in the search space set, PDCCH candidates, etc. corresponding to the CORESET based on the TCI state included in the configuration information of the CORESET. In the present disclosure, the signal reception operation based on the TCI can include operations such as determining and applying a reception beam, and estimating a channel. The TCI of the PDSCH can be set (e.g., indicated) separately from the TCI of the PDCCH. The TCI of the PDSCH can be included in the DCI for scheduling the PDSCH, and the DCI can be transmitted to the terminal. In other words, the DCI of the PDSCH can be dynamically indicated to the terminal. The base station can select one TCI from among the candidate TCI(s) of the PDSCH set to the terminal (e.g., candidate TCI(s) of the activated PDSCH) through upper layer signaling, and can indicate the selected TCI to the terminal through scheduling DCI. In multiple TRP transmission, the DCI can include multiple TCIs, and the terminal can receive the PDSCH using the indicated multiple TCIs. The TCI of other downlink signals (e.g., CSI-RS, TRS, PRS) can be determined independently from the TCI of the PDCCH or PDSCH.

[0087] In the uplink, the PUCCH transmission beam (e.g., TCI) and the PUSCH transmission beam (e.g., TCI) of the terminal can be managed separately. The TCI (e.g., transmission spatial filter or spatial relationship information) of the PUCCH can be semi-statically configured for the terminal. The TCI (e.g., transmission spatial filter or spatial relationship information) of the PUSCH can be semi-statically configured. Alternatively, the TCI of the PUSCH can be included in scheduling DCI, and the scheduling TCI can be transmitted to the terminal. In other words, the TCI of the PUSCH can be dynamically indicated to the terminal. The TCI of the PUSCH can be indirectly indicated by SRS resource indication information, and the terminal can transmit the PUSCH by applying the same TCI (e.g., transmission spatial filter or spatial relationship information) set for the indicated SRS resource to the PUSCH. The TCI of other uplink signals (e.g., SRS, PRACH) can be determined independently from the TCI of PUCCH or PUSCH.

[0088] The above-described method allows for individual beam management for each transmission signal or channel, thereby achieving a high degree of freedom and flexibility. However, if beams are to be changed simultaneously for all signals, separate signaling procedures are required for each signal, potentially resulting in significant signaling overhead and increased beam management delays.

[0089] To address the above issues, a method of indicating TCIs of multiple signals (e.g., physical signals and / or physical channels) to a terminal with a single signaling may be considered. In the downlink, the terminal may receive an indication of a downlink TCI via DCI, and the indicated downlink TCI may be applied to both the PDCCH and the PDSCH. The indicated downlink TCI may be applied to downlink signals other than the PDCCH and the PDSCH (e.g., CSI-RS, TRS, PRS). In the uplink, the terminal may receive an indication of an uplink TCI via DCI, and the indicated uplink TCI may be applied to both the PUCCH and the PUSCH. The indicated uplink TCI may be applied to uplink signals other than the PUCCH and the PUSCH (e.g., SRS, PRACH). The downlink TCI and the uplink TCI may be individually indicated via different DCIs. Alternatively, the downlink TCI and the uplink TCI may be indicated together via the same DCI. Downlink TCI and uplink TCI may be identical. In this case, the TCI may be referred to as a joint TCI. The joint TCI may be indicated to the terminal via DCI. The joint TCI may be applied to both the above-described downlink signals (e.g., PDCCH, PDSCH, and the non-channel signal(s)) and the above-described uplink signals (e.g., PUCCH, PUSCH, and the non-channel signal(s)). Since the above-described TCI is applied equally to multiple signals (specifically, physical signals and / or physical channels), it may be referred to as a unified TCI, a single TCI, etc.

[0090] A signal to which the integrated TCI is applied may be a signal for transmitting terminal-specific information. For example, a PDSCH may include unicast data (e.g., a DL-SCH). A PDCCH may include DCI for scheduling a data channel (e.g., a PDSCH, a PUSCH, a PSSCH) containing unicast data or DCI containing terminal-specific control information. A PDCCH may be a PDCCH transmitted in a USS set and / or a specific CSS set (e.g., a Type 3 CSS set). CSI-RS, TRS, PRS, etc. may be configured terminal-specifically. In other words, CSI-RS, TRS, PRS, etc. may be signals transmitted terminal-specifically. For another example, a PUSCH may include unicast data (e.g., an uplink-shared channel (UL-SCH)). SRS, PRACH, etc. may be configured terminal-specifically. In other words, SRS, PRACH, etc. may be signals transmitted terminal-specifically. Terminal-specific signals can be configured in the terminal through terminal-specific RRC signaling procedures, MAC CE, DCI, etc.

[0091] The integrated TCI can be indicated by a scheduling DCI. The downlink DCI format (e.g., DCI format 1_1, 1_2) that schedules the PDSCH can be used to indicate the TCI (e.g., the integrated TCI).

[0092] Figure 3 is a conceptual diagram illustrating embodiments of a TCI instruction method by DCI.

[0093] Referring to FIG. 3, a base station can transmit a DL (downlink) DCI for scheduling a PDSCH. A terminal can receive the DL DCI for scheduling a PDSCH. The terminal can check the indication of the TCI based on the downlink DCI. Generally, the DCI can schedule a PDSCH, but if certain field(s) of the DCI are set to a predefined value, the PDSCH may not be scheduled. In this case, the DCI may be used for other purposes. Even if the scheduling DCI is used for purposes other than scheduling a PDSCH, the terminal can check the indication of the TCI from the scheduling DCI. The terminal can report a HARQ-ACK (acknowledgement) to the base station as a response to receiving the PDSCH or the DL DCI. The HARQ-ACK may be composed of an ACK or a NACK. Alternatively, the HARQ-ACK may be composed of only an ACK. The transmission resources (e.g., PUCCH resources) of HARQ-ACK can be determined based on the resource locations of PDSCH. Even when PDSCH is not transmitted, the transmission resources of HARQ-ACK can be determined based on the virtual PDSCH resources allocated by the DCI.

[0094] In the above-described operation, the beam quality measurement and reporting operation of the terminal may be triggered by the base station. The terminal may perform a beam measurement operation based on a DL signal (e.g., SSB, CSI-RS, etc.) set (or indicated) by the base station, and may transmit the measurement result to the base station through a UL (uplink) resource (e.g., PUCCH, PUSCH, etc.) set (or indicated) by the base station. In the above-described operation, the entity that determines and manages the beam of the terminal may be the base station. The base station may determine and manage the most suitable transmit / receive beam for the terminal based on the beam report (e.g., measurement result) received from the terminal. When a beam change is required, the base station may indicate a new beam to the terminal through a beam-related signaling message (e.g., TCI, spatial relationship information, QCL, etc.). According to the above-described operation, it may be difficult to efficiently manage the number of beam reports, beam report timings, etc., and the delay time and signaling overhead required for beam reporting and / or beam switching may increase.

[0095] As a method for solving the above problem, a method for a terminal to trigger its own beam quality measurement and / or beam reporting operation may be considered. The terminal may arbitrarily trigger a beam reporting operation when it determines that a beam change is necessary. For example, the terminal may transmit beam reporting information to the base station using a preset UL resource only when beam reporting is required. Alternatively, the terminal may request a second UL resource for beam reporting from the base station using a preset first UL resource, and transmit beam reporting information to the base station using the second UL resource (e.g., a second UL resource allocated by the base station). The latter method may be referred to as a two-step beam reporting method. In the present disclosure, specific operations related to the two-step beam reporting method by the terminal will be described.

[0096] [Step 2 Beam Reporting Method]

[0097] Figure 4 is a conceptual diagram illustrating embodiments of a two-step beam reporting method.

[0098] Referring to FIG. 4, a terminal can measure beam quality based on a received DL signal. If a predetermined event occurs due to a measurement result of the beam quality, the terminal can perform a beam reporting operation by directly triggering a beam reporting operation. The event may be referred to as a beam reporting trigger event. The occurrence of the event may be one of the necessary condition(s) for the terminal to trigger the beam reporting operation. The beam reporting operation of the terminal may include at least two UL transmissions. The two UL transmissions may be performed in a first UL resource and a second UL resource, respectively. In the present disclosure, a UL transmission in the first UL resource may be referred to as a first UL transmission, and a UL transmission in the second UL resource may be referred to as a second UL transmission. The first UL transmission may mean transmission of a first UL signal, and the second UL transmission may mean transmission of a second UL signal.

[0099] A beam report trigger event can be defined based on an integrated TCI. The terminal can measure metrics such as L1-RSRP (layer 1-reference signal received power), L1-SINR (layer 1-signal-to-interference-plus-noise ratio), and hypothetical SINR for SSB or CSI-RS, which are QCL source signals (or source beams) of a directed beam or a currently applied beam. The terminal can consider a metric falling below a first reference value as a trigger event (e.g., a beam report trigger event). The current beam (e.g., the currently applied beam) can be a DL TCI, an UL TCI, and / or a joint TCI. The event (e.g., a trigger event, a beam report trigger event) can be referred to as a first event. The SSB and CSI-RS can be transmitted to the terminal periodically or semi-permanently. Alternatively, the SSB and CSI-RS can be transmitted aperiodically within a predetermined time interval. The CSI-RS resource may be a channel measurement resource (CMR). When the metric is L1-SINR, the CSI-RS resource may include both a CMR and an interference measurement resource (IMR), and the beam quality measurement operation may be performed based on a plurality of non-zero power (NZP) CSI-RS resources or a plurality of ZP CSI-RS resources.

[0100] Simultaneously with or separately from the above-described operations, the terminal may measure the beam quality for the new beam(s), and may consider that the beam quality of the new beam(s) satisfies a second threshold value as a beam report trigger event (e.g., occurrence of a beam report trigger event). The new beam(s) may refer to beams other than the current beams, and may belong to a candidate beam set configured by the base station. Even if the current beam is included in the candidate beam set, the current beam may be excluded from the candidate beam set. Alternatively, if the current beam is included in the candidate beam set, the terminal may perform a beam quality measurement operation for the remaining new beam(s) excluding the current beam. Alternatively, the terminal may perform the beam quality measurement operation in the same manner even when the new beam is the current beam. The candidate beam set may be a candidate beam set explicitly configured for a two-step beam reporting operation. Alternatively, the candidate beam set may be a set configured with at least some beam(s) included in a TCI pool configured in the terminal (e.g., a TCI state pool). The TCI pool may be a DL TCI pool, a UL TCI pool, or a joint TCI pool, and at least some of the beam(s) may be activated TCIs. In an embodiment where a candidate beam set is explicitly configured, the terminal may receive a configuration for a CSI-RS resource set (or, a CSI resource set, a CSI resource setting), and may measure beam quality for CSI-RS resource(s) and / or SSB resource(s) included in the CSI-RS resource set (or, a CSI resource set, a CSI resource setting). The second reference value may be a value defined or configured separately from the first reference value for L1-RSRP, L1-SINR, hypothetical SINR, etc. Alternatively, the second reference value may be the first reference value or a beam quality value of the current beam. The above definition means that a beam reporting operation may be triggered when the quality of the new beam(s) is higher than the quality of the current beam. The event may be referred to as a second event.

[0101] The terminal can determine a beam report trigger event by comparing the beam quality between the new beam(s) and the TCI(s) activated on the terminal. For example, if the beam quality of the new beam(s) is better than the beam quality of at least one TCI among the activated TCIs, the terminal can trigger a beam report operation. The operation of deriving the at least one TCI can be predefined in the technical specification or can be configured in the terminal from the base station. For example, the at least one TCI can mean a TCI having the highest beam quality among the activated TCIs, a TCI having the lowest beam quality, a TCI having the Nth highest beam quality, a TCI having the Nth lowest beam quality, etc., where N can be a natural number. Based on the beam report by the event, the base station can update the TCI pool of the terminal with a list of better beams. The event can be referred to as a third event. The activated TCIs can include a current beam (e.g., a current TCI). The at least one TCI among the activated TCIs may not necessarily match the current TCI. Among the activated TCIs, at least one TCI may or may not match the current TCI. If the at least one TCI matches the current TCI, the operation for the third event in the corresponding section may be identical to or similar to the operation for the second event. Each of the activated TCI(s) in the terminal may be regarded as a current beam of the terminal. In this case, the definition of the current beam and / or the number of current beams in the third event may be different from the definition of the current beam and / or the number of current beams in the second event, and the operation other than the definition of the current beam and / or the number of current beams may be similar in the second and third events.

[0102] In order to increase the reliability of the beam quality measurement result (e.g., beam quality measurement value(s)), the terminal may repeatedly perform the above-described beam quality measurement and comparison operation. The terminal may determine that an event has occurred when the above-described event determination criterion is satisfied M times. M may be a natural number. The value of M may be signaled to the terminal by the base station. The terminal may measure the beam quality M1 times in a plurality of periods (e.g., a plurality of occasions) for the DL resource corresponding to the current beam (hereinafter referred to as “first DL resource”), and may compare the beam quality measurement result (e.g., beam quality measurement value(s)) with a first reference value. M1 may be a natural number. For example, the comparison operation between the beam quality measurement result and the first reference value may be performed M1 times. In other words, each of the M1 beam quality measurement values ​​may be compared with the first reference value. If the number of times that the beam quality of the current beam is determined to be lower than the first reference value is M1, the terminal can trigger a beam reporting operation according to the first event. Simultaneously with the above-described method, the terminal can measure the beam quality M2 times in a plurality of periods (e.g., a plurality of occasions) for a DL resource corresponding to the candidate beam (hereinafter, referred to as “second DL resource”), and compare the beam quality measurement result (e.g., beam quality measurement value(s)) with the beam quality of the current beam (or the second reference value). If the number of times that the beam quality of the candidate beam is determined to be higher than the beam quality of the current beam is M2, the terminal can trigger a beam reporting operation according to the second event.

[0103] In the above embodiment, the period value of the first DL resource may be different from the period value of the second DL resource. In this case, while the terminal performs the beam measurement operation for the first DL resource M1 times, the beam measurement operation for the second DL resource may be performed M2 times. M1 and M2 may have different values. If a predefined condition is satisfied, M1 and M2 may match. For example, M1 and M2 may have the same value, and the base station may configure (e.g., instruct) the terminal to configure M1 and M2 with the same value. Simultaneously or separately from the above-described operation, the period value of the first DL resource and the period value of the second DL resource may be configured to match. In this case, M1 and M2 may match. In this case, the judgment condition of the second event may be defined based on M1. In other words, the terminal may perform a beam quality comparison operation between the current beam and the candidate beam M1 times within the above section based on the resource of the current beam. If there are multiple candidate beams, each candidate beam can be compared with the current beam the same number of times (e.g., M1 times). In this case, the event determination period (e.g., period value) may match the period (e.g., period value) of the first DL resource. Alternatively, the determination condition of the second event can be defined based on M2. In other words, the terminal can perform the beam quality comparison operation between the current beam and the candidate beams M2 times based on the resource of the candidate beam within the section. If there are multiple candidate beams, the value of M2 may be different for each candidate beam, and the number of times the candidate beams are compared with the current beam within the section may be different for each candidate beam. In this case, the event determination period (e.g., period value) may match the period (e.g., period value) of the second DL resource.Alternatively, the event determination period (e.g., period value) may be set to match a smaller period (e.g., period value) or a larger period (e.g., period value) among the period (e.g., period value) of the first DL resource and the period (e.g., period value) of the second DL resource. Alternatively, even when multiple candidate beams exist, the event determination period (e.g., period value) may match the period (e.g., period value) of the first DL resource. The terminal may repeatedly perform a beam measurement operation M3 times for the DL resource corresponding to the activated TCI, and may determine the third event by comparing the beam measurement result (e.g., beam quality measurement result) with the candidate beam measured M2 times within the same section. At this time, the event determination period (e.g., period value) may match the period (e.g., period value) of the DL resource corresponding to the activated TCI or the period (e.g., period value) of the second DL resource. The event determination period (e.g., period value) can be set to match the smaller period (e.g., period value) or the larger period (e.g., period value) among the two periods (e.g., period values). If a predefined condition is satisfied, M3 can match M2 or M1. For example, the period value of the second DL resource can be set to match the period value of the activated TCI(s), and M2 and M3 can match.

[0104] The above-described beam quality measurement operation can be performed within a predefined time window. The time window may be a sliding window, and the start and end times of the time window may change over time. The time window may have a fixed length. In this case, the time window may be set to have a length sufficiently long to include at least M DL resources involved in one or more event(s). For example, a first DL resource may exist at least M1 times within the time window. This condition may be referred to as a first condition. Simultaneously or separately from the above-described embodiment, a second DL resource may exist at least M2 times within the time window. This condition may be referred to as a second condition. A DL resource corresponding to an activated TCI may exist at least M3 times within the time window. The above conditions may be satisfied simultaneously. Alternatively, the time window may be set such that only some of the above conditions are satisfied. In this case, the time window may be set to include all DL resources involved in one or more event(s) at least once. For example, the time window may be set such that at least M1 current beam comparison operations can be performed within the time window. Alternatively, the time window may be set such that at least M2 candidate beam comparison operations can be performed within the time window. Alternatively, the time window may be set such that at least M1 current beam comparison operations and at least M2 candidate beam comparison operations can be performed within the time window. When the first condition is considered in setting the time window and the second condition is not considered, the beam measurement operation for the second DL resource(s) can be performed regardless of the inclusion relationship between the second DL resource(s) and the time window.For example, the terminal can measure both the second DL resource(s) within the time window and the second DL resource(s) outside the time window, and compare the measurement value(s) obtained through the above measurements with the measurement value(s) of the first DL resource within the time window M1 times. Conversely, if the second condition is considered in the time window configuration and the first condition is not considered, the beam measurement operation for the first DL resource can be performed regardless of the inclusion relationship between the first DL resource and the time window. For example, the terminal can measure both the first DL resource within the time window and the first DL resource outside the time window, and compare the measurement value(s) obtained through the above measurements with the measurement value(s) of the second DL resource within the time window M2 times. The above configuration may mean that the length (e.g., period value) of the time window must be greater than or equal to the largest period value of the DL resources. In other words, the minimum length of the time window may be determined by the period value(s) of the DL resource(s) that are the beam measurement target. Alternatively, time windows can be managed on a per-DL resource or per-event basis. In other words, multiple time windows corresponding to multiple DL resources or multiple events can be determined (e.g., set), and beam measurement operations can be performed for each DL resource corresponding to each time window or each event corresponding to each time window.

[0105] The periodic values ​​of DL resources may have a relationship with each other. For example, the periodic value of the first DL resource may be set to a divisor or multiple of the periodic value of the second DL resource. The first DL resource and the second DL resource may be measured in the same measurement window (e.g., time window), and M1 may be a divisor or multiple of M2. For another example, the periodic value of the DL resource corresponding to the activated TCI may be set to a divisor or multiple of the periodic value of the second DL resource. The DL resource corresponding to the activated TCI may be measured in the same measurement window (e.g., time window) as the second DL resource, and M3 may be a divisor or multiple of M2. When a plurality of second DL resources are set, the periodic values ​​of the plurality of second DL resources may be identical or have a multiple relationship with each other.

[0106] If the prerequisite(s) for a beam report trigger are met, the terminal may first perform a first UL transmission on a first UL resource. The purpose of the first UL transmission may include at least "the terminal requests a second UL resource for transmitting beam report information to the base station" or "the terminal notifies the base station that it will transmit beam report information through the second UL resource." The first UL resource may be mapped to a resource that is later than a DL resource (e.g., an SSB resource and / or a CSI-RS resource) that is the basis of the beam report trigger event by a time T1. T1 may be set to a value not smaller than a first time gap predefined in the technical specification, and the first time gap may be defined as a value that includes at least a time taken by the terminal to perform a beam measurement operation on the DL resource and / or a time to prepare for the first UL transmission. The first time gap may be defined as an absolute time value (e.g., ms (millisecond)). Alternatively, the first time gap may be defined or set as a multiple of a unit time defined in the technical specifications (e.g., the number of slots, the number of symbols, or a combination of the number of slots and the number of symbols). The first time gap may have different values ​​depending on the capabilities of the terminal, the frequency band, and / or the subcarrier spacing.

[0107] Multiple trigger events can be used together in a single terminal. The terminal can simultaneously (e.g., in parallel) monitor a first event in which the beam quality of the current beam is determined to be degraded and a second event in which a new candidate beam satisfying a reference value is determined to be discovered. In this case, the first time gap may include the time required for the first event operation (or the second event operation) and may not include the time required for the second event operation (or the first event operation). The event operation may refer to an operation for determining the occurrence of an event. In other words, the terminal can trigger a beam reporting operation and perform a first UL transmission operation based on the occurrence of only one event (e.g., the first event or the second event). The second event operation (or the first event operation) of the terminal can be performed together with or in parallel with the first UL transmission operation, and the second event operation (or the first event operation) may not be involved in the first transmission operation (e.g., the first UL transmission operation). For example, if the terminal determines that the beam quality of the current beam is degraded, the terminal may perform the first UL transmission operation regardless of the beam measurement operation (or the result of the beam measurement operation) for the new candidate beam(s).

[0108] The terminal may perform a second UL transmission corresponding to the first UL transmission. In this case, if an event other than the event that triggered the first UL transmission occurs before the second UL transmission time, the second UL transmission may include beam report information for at least the other event. In the above embodiment, if the first UL transmission is triggered by the first event, the beam report information reported through the second UL transmission following the first UL transmission may include information about the second event (e.g., new candidate beam(s) and / or beam quality value of the new candidate beam(s)). Alternatively, if the first UL transmission is triggered by the second event, the beam report information reported through the second UL transmission following the first UL transmission may include information about the first event (e.g., beam quality value of the current beam). In this case, the beam report information may not include information about the new candidate beam(s). On the other hand, if an event other than the event that triggered the first UL transmission does not occur before the second UL transmission time, the second UL transmission may include beam reporting information regarding the event that triggered the first UL transmission. For example, the first UL transmission may be triggered by the second event, and the beam information included in the second UL transmission may include information regarding the second event. In this case, the beam quality measured up to the time of the first UL transmission may be updated before the time of the second UL transmission, and the second UL transmission may include information regarding the updated beam quality. In the above embodiment, the second UL resource may be mapped to a resource that is sufficiently later than the DL resource or the first UL resource in consideration of the additional time required for the operation of the other event.The time resource (e.g., slot, symbol) to which the second UL resource is mapped may be a time point later than a predetermined time gap from the time point (e.g., slot, symbol) at which the terminal determines the other event or performs a DL measurement operation corresponding to the other event (e.g., slot symbol). The predetermined time gap may coincide with the first time gap. Alternatively, the predetermined time gap may be defined or set to a value different from the first time gap.

[0109] In another embodiment, the first event may be used in conjunction with a third event. In the third event, the TCIs activated in the terminal may not include the TCI currently applied (or instructed) to the terminal. For example, an operation of comparing K TCIs with the highest beam quality in the list of activated TCIs with the candidate beams may be configured (e.g., instructed) in the terminal. K may be a natural number. If the beam quality of the current TCI of the terminal deteriorates, the K TCIs may not include the current TCI. In this case, the terminal may perform an operation of comparing the beam quality of the K activated TCIs with the candidate beams, and at the same time, perform an operation of measuring the beam quality of the current TCI and / or an operation of comparing the beam quality measurement result of the current TCI with the candidate beams. Alternatively, the second event may be used in conjunction with the third event. The terminal may perform a beam measurement operation on new candidate beams, and compare the beam quality of the first candidate beams with the beam quality of the current TCI (or a second reference value). Simultaneously with the above-described operation, the terminal can compare the beam quality of the second candidate beams with the beam quality of the activated TCIs. The set of the first candidate beams and the set of the second candidate beams may be identical. In other words, the second event and the third event may be evaluated based on a common set of candidate beams. Within the common set of candidate beams, the new beam(s) selected for the second event and the new beam(s) selected for the third event may be different from each other.

[0110] After performing a first transmission (e.g., a first UL transmission), the terminal may perform a second transmission (e.g., a second UL transmission) and transmit beam report information to the base station. The beam report information may be transmitted via the second UL transmission. The beam report information may include at least one of information about a current beam (or a previous beam) (e.g., beam quality measurement information, a beam or resource index), information about a beam report trigger event, or information about a new beam (e.g., a beam or resource index, beam quality measurement information). In a beam report procedure triggered by the terminal, the beam report information may include information specifying a transmission direction (e.g., DL and / or UL) of the reported beam. For example, the reported beam may be expressed in the form of a DL TCI, a UL TCI, a joint TCI (or a TCI index corresponding to the beam, a resource index of a TCI source signal), etc. The base station can specify (e.g., confirm) the transmission direction of the reported beam (e.g., the degraded beam and / or the selected candidate beam) based on the above information, transmit a reception confirmation message (e.g., a response message) or beam indication information to the terminal, and permit or instruct the terminal to apply the reported beam to the specified transmission direction.

[0111] Beam report information can be generated in the physical layer of the terminal. For example, an operation for determining whether a beam report trigger event has occurred, an operation for measuring beam quality for the determination operation, and / or a beam search operation for the determination operation can be performed in the physical layer without intervention of a higher layer of the terminal. The beam report information can be defined as uplink control information (UCI). The beam report information can be generated in the physical layer of the terminal, and the beam report information (e.g., UCI including the beam report information) can be transmitted via PUCCH or PUSCH. In other words, the second UL resource can be a PUCCH resource or a PUSCH resource. At least a part of the beam report information can be determined by intervention of a higher layer operation of the terminal. In this case, the beam report information can be defined as a MAC CE or set as a part of a field of the MAC CE. The beam report information (e.g., a MAC CE including the beam report information) can be included in a TB (transport block), and the TB can be transmitted via a PUSCH. In other words, the second UL resource may be a PUSCH resource.

[0112] Multiple events may occur simultaneously. Specifically, the terminal may perform a measurement operation on a DL resource. The DL resource may be a resource corresponding to at least one of a current beam, a candidate beam, or an activated TCI. As a result of the measurement operation, multiple events may occur simultaneously. For example, the DL resource may be a QCL source resource of the current TCI, and if "the beam quality measured on the DL resource falls below a first reference value, and the beam quality measured on the DL resource falls below the beam quality of the candidate beam(s)", the terminal may determine that the first event and the second event have occurred. For another example, the DL resource may be a candidate beam (or a DL resource corresponding to a candidate beam), and if "the beam quality of the DL resource is better than the beam quality of the current TCI (or the second reference value), and the beam quality of the DL resource is better than the beam quality of the activated TCI set as the comparison target in the third event," the terminal may determine that the second event and the third event have occurred.

[0113] Multiple events may occur at different times, and the different times may satisfy the same first UL resource and the time gap condition described above. Alternatively, the different times may satisfy the same second UL resource and the time gap condition described above. For example, a first event may be triggered as a result of measuring a first DL resource, and a second event may be triggered as a result of measuring a second DL resource. The terminal may determine a common first UL resource that satisfies the multiple events and the time condition. The terminal may determine a common second UL resource that satisfies the multiple events and the time condition.

[0114] In the above-described embodiment, the beam reporting operation may be triggered by a plurality of events. Alternatively, the beam reporting operation may be considered to be triggered by any one of the plurality of events. Any one of the events may be determined by the terminal arbitrarily or based on a predetermined rule. Alternatively, any one of the events may be determined as an event with a high priority based on a priority order among the events. The terminal may perform the first UL transmission and the second UL transmission based on the plurality of events.

[0115] In the above-described embodiment, the beam report information included in the second UL transmission may include beam information for a plurality of events. For example, the beam report information may include at least one of information regarding a beam quality of a current beam in relation to a first event, information regarding new beam(s) in relation to a second event, or information regarding a beam quality of the new beam(s) in relation to the second event. For another example, the beam report information may include at least one of new beam(s) derived from the second event, information regarding a beam quality corresponding to the new beam(s), new beam(s) derived from a third event, or information regarding a beam quality corresponding to the new beam(s) derived from the third event. The beam report information may include indices indicating a plurality of events.

[0116] Alternatively, the beam report information included in the second UL transmission may include beam information for some events (e.g., any one of the events described above). The beam report information may include an index indicating the some events (e.g., any one of the events described above). The beam information for other event(s) may not be transmitted to the base station. Alternatively, the beam information for other event(s) may be reported to the base station via another UL transmission (e.g., another second UL transmission). For example, a plurality of CSI reporting configurations may be configured for the terminal, and a plurality of second UL resources and / or a plurality of first UL resources corresponding to the plurality of second UL resources may be configured by the plurality of CSI reporting configurations. The beam information for the plurality of events may be divided into the plurality of second UL resources and transmitted to the base station.

[0117] An inclusion relationship may exist between certain events in terms of beam information. For example, the beam information of a second event may include not only the beam quality value of the new beam(s) but also the beam quality value of the current beam. The base station may compare the beam quality value of the current beam reported by the terminal with a first reference value set in the terminal, and may infer whether the first event has occurred based on the comparison result. In this case, even if the first event has occurred (e.g., even if the first event has occurred together with the second event), it may not be necessary for the terminal to additionally report the beam information of the first event to the base station. Alternatively, the beam information of the first event may be included in the beam information of the second event. In this case, the beam report information may include the beam information of the second event and may not include the beam information of the first event. The beam report information may include an index indicating the second event and may not include an index indicating the first event. The second event may take precedence over the first event. Similarly, the beam information derived from the second event and the beam information derived from the third event may be similar or identical. The beam report information may include only one of the beam information of the second event and the beam information of the third event. For example, the second event may take precedence over the third event. Generalizing the above-described embodiment, it may not be supported for certain combinations of events to be reported together using the same beam report procedure.

[0118] The priorities between events may be predefined in the technical specifications. For example, a second event may have a higher priority than a first event. The second event may have a higher priority than a third event. The first event may have a higher priority than a third event. Alternatively, considering that the importance of events may vary depending on the situation, the priorities between events may be determined based on configuration information signaled from the base station to the terminal. The priorities between events may be defined for some combinations of events. Some events may not have priorities defined. For example, the priorities between the first and third events may or may not be defined. When the first and third events occur together, both the beam information for the first event and the beam information for the third event may be reported to the base station.

[0119] When a certain condition is satisfied in a certain event, the certain event may be converted to another event. For example, if a new beam satisfying the condition is not found in the candidate beam set configured for the second event, the beam report information may not include information about the new beam, and the beam report information may include information about the current beam (e.g., beam quality of the current beam). The information about the current beam included in the beam report information may correspond to the beam information of the first event. In the above-described embodiment, the terminal may perform a beam report operation for the first event instead of a beam report operation for the second event. In other words, the second event may be temporarily converted to the first event. For example, the UL resource for transmitting the beam report of the first event may be configured by the first CSI report configuration, and the UL resource for transmitting the beam report of the second event may be configured by the second CSI report configuration. In the above-described embodiment, the terminal may perform the beam report operation for the first event on the UL resource configured by the first CSI report configuration. The payload size of the beam report information set for the first event may be smaller than the payload size of the beam report information set for the second event, and the UL signaling overhead may be reduced through the above-described event switching operation. Similarly, if any of the activated TCIs compared to the candidate beam(s) in the third event matches the current beam, the terminal may perform the beam report operation for the first event instead of the beam report operation for the third event. In other words, the third event may be temporarily switched to the first event.

[0120] The second UL resource can be semi-statically or semi-permanently configured for the terminal based on higher layer signaling (e.g., RRC message). The second UL resource can be allocated repeatedly and periodically, and the same resource configuration and transmission parameters for the second UL resource can be applied in each period. The message size of the beam report information can be limited to several to several tens of bits. The message size of the beam report information can be constant each time. Alternatively, the message size of the beam report information can have a small range of variation. In a channel environment without fast fading, the reception performance of the second UL transmission can be sufficiently guaranteed with only a semi-static configuration without applying a link adaptation technique, and signaling overhead can be minimized because DCI transmission for dynamic scheduling is unnecessary. The above-described method may be referred to as (method 100).

[0121] At this time, the first UL resource and the second UL resource can be configured independently of each other without any correlation. For example, the time resource to which the second UL resource is mapped and / or the period of the second UL resource can be configured to the terminal through independent configuration parameters regardless of the first UL resource. Considering the beam reporting delay time and efficiency, it is impractical for the first UL resource and the second UL resource to be arranged too far apart in time and / or for the period of the first UL resource and the period of the second UL resource to be configured so as to be misaligned. Therefore, excessive configuration freedom may result in an unnecessarily increased signaling overhead.

[0122] The second UL resource (or first UL resource) may be determined based on the configuration parameters of the first UL resource (or second UL resource). The configuration parameters may be shared between the first UL resource and the second UL resource. For example, the repetition periods of the first UL resource and the second UL resource may be determined by the same period value. Alternatively, the period value of one UL resource may be determined as a multiple or divisor of the period value of the other UL resource. The first UL resource and the second UL resource may be respectively mapped to time resources to which different time offsets are applied from a common reference point in time. Alternatively, the time resource (e.g., slot, symbol) to which the second UL resource (or the first UL resource) is mapped can be expressed as a point in time at which a predetermined time offset is applied from the time resource to which the first UL resource (or the second UL resource) is mapped, and the time resource to which the second UL resource (or the first UL resource) is mapped can be set to the terminal based on the above-described method. According to the above embodiment, the signaling overhead for setting a plurality of UL resources to the terminal can be reduced.

[0123] According to (Method 100), since the UL resource is periodically occupied by the second UL resource regardless of whether the beam reporting operation is triggered (e.g., whether the second UL transmission is actually performed), resource waste may occur if the beam reporting operation is intermittently triggered compared to the period of the second UL resource. According to embodiments for improving resource efficiency, if the second UL transmission is not performed in the second UL resource, the base station can opportunistically reuse the second UL resource by dynamically allocating another signal to the second UL resource. In other words, the second UL resource can be opportunistically canceled or overridden by another signal.

[0124] To support the above-described operation, a correlation may be established between the first UL resource and the second UL resource. For example, the first UL resource and the second UL resource belonging to the same resource cycle may be correlated with each other. The terminal may perform the second UL transmission on the second UL resource only when the first transmission is performed on the first UL resource that is correlated with the second UL resource. Alternatively, the terminal may perform the second UL transmission on the second UL resource even when the first UL transmission is performed on a first UL resource other than the first UL resource that is correlated with the second UL resource. In other words, the terminal may perform the second UL transmission on a second UL resource that is not correlated with the first UL resource on which the first UL transmission is performed. Alternatively, the terminal may perform the second UL transmission on the second UL resource when a predetermined condition is satisfied, regardless of whether the first UL transmission is performed.

[0125] If the terminal does not perform the first UL transmission on the first UL resource that is interrelated with the second UL resource, the terminal may transmit another uplink signal on the second UL resource. In other words, if the first UL transmission is not performed on the first UL resource that is interrelated with a certain second UL resource, the second UL resource may be considered deactivated. In other words, the second UL resource may be activated (or exist) only when the first UL transmission is performed on the interrelated first UL resource. Conversely, even if the terminal does not perform the first UL transmission on the first UL resource, transmission of another uplink signal may not be permitted on the second UL resource that is not interrelated with the first UL resource. In other words, the second UL resource may be considered activated regardless of whether the first UL transmission is performed on the interrelated first UL resource. If the second UL resource includes a flexible symbol, the terminal may transmit another downlink signal on the second UL resource. The other uplink / downlink signal may be a signal dynamically allocated by the base station (e.g., PDSCH, PUSCH, PUCCH, CSI-RS, SRS, etc.). Alternatively, the other uplink / downlink signal may be a signal semi-statically set to overlap with the second UL resource (e.g., SPS PDSCH, CG PUSCH, PUCCH, CSI-RS, SRS, etc.). In the present disclosure, the first UL resource and the second UL resource may mean valid resources, and when the first UL resource and the second UL resource are associated with each other, both the first UL resource and the second UL resource may be valid resources. The first UL resource and the second UL resource may not overlap with a downlink resource (e.g., a downlink symbol, an SSB resource, etc.).

[0126] Meanwhile, it may take a certain amount of time for the base station to perform the operation of receiving the first UL transmission and checking the presence or absence of the second UL transmission. In order to enable opportunistic reuse of the second UL resource, it may be necessary for the terminal to receive the DCI indicating resource allocation that overrides the second UL resource at a time earlier than the second UL resource. Considering the timeline described above, a certain time gap may also be required between the first UL resource and the second UL resource. To distinguish it from the first time gap, the time gap between the first UL resource and the second UL resource may be referred to as the second time gap. Referring again to FIG. 4, the second UL resource may be mapped to a period that is later than the first UL resource by a time T2. T2 may be set to a value not smaller than a second time gap predefined in the technical specification, and the second time gap may be defined as a value including at least a time for the base station to receive and process the first UL resource (e.g., a first UL transmission on the first UL resource), a time for the base station to generate and transmit a DCI for rescheduling the second UL resource, and a time for the terminal to generate and prepare for transmission a signal scheduled by the DCI (e.g., the other uplink / downlink signal). The second time gap may be defined or set as an absolute time value (e.g., ms). Alternatively, the second time gap may be defined or set as a multiple of a unit time defined in the technical specification (e.g., a number of slots, a number of symbols, or a combination of a number of slots and a number of symbols). When the first UL resource and the second UL resource are mapped to different serving cells (or different carriers), the unit time (e.g., slot, symbol, etc.) may be determined based on the numerology (e.g., subcarrier spacing) of one of the two serving cells (or one of the two carriers).The above-mentioned one serving cell (or one carrier) may mean a serving cell having a low cell index, a serving cell having a high cell index, a serving cell to which the first UL resource is mapped, a serving cell to which the second UL resource is mapped, etc. The second time gap may have different values ​​depending on the capability of the terminal, the frequency band, and / or the subcarrier spacing.

[0127] The second time gap may be defined as the minimum time distance (e.g., symbol offset) from any symbol (e.g., the first symbol or the last symbol) to which the first UL resource is mapped to any symbol (e.g., the first symbol or the last symbol) to which the second UL resource is mapped. Alternatively, the second time gap may be defined as the minimum time distance (e.g., slot offset) from a slot to which the first UL resource is mapped to a slot to which the second UL resource is mapped. If the interrelated first UL resources and second UL resources do not satisfy the above condition, the terminal may consider the resources (e.g., the first UL resource and the second UL resource) to be invalid and may not perform a beam reporting operation on the resources. Alternatively, the terminal may determine that only one of the first UL resource and the second UL resource is valid and may perform UL transmission on the valid resource. For example, if there is no valid second UL resource correlated with the first UL resource, the terminal can perform the first UL transmission on the first UL resource that does not have the valid second UL resource. The base station can dynamically schedule a UL resource (e.g., PUSCH) for the terminal to transmit beam report information to the terminal when receiving the first UL transmission. For another example, if there is no valid first UL resource correlated with the second UL resource, the terminal can perform the second UL transmission including the beam report information on the second UL resource that does not have the valid first UL resource. Alternatively, at least one valid (e.g., satisfying the second time gap condition) second UL resource may exist for each first UL resource. For example, the second UL resource associated with the first UL resource may be determined as the earliest valid second UL resource that appears after the second time gap.Alternatively, the condition satisfying the second time gap can be defined as a necessary condition for the first UL resource and the second UL resource to be interrelated.

[0128] Meanwhile, a maximum time gap may be defined between the first UL resource and the second UL resource. The maximum time gap may be referred to as a third time gap. The third time gap may be defined as a maximum time distance (e.g., symbol offset) from any symbol (e.g., a first symbol or a last symbol) to which the first UL resource is mapped to any symbol (e.g., a first symbol or a last symbol) to which the second UL resource is mapped. Alternatively, the third time gap may be defined as a maximum time distance (e.g., slot offset) from a slot to which the first UL resource is mapped to a slot to which the second UL resource is mapped. If the distance between the interrelated first UL resources and the second UL resources exceeds the third time gap, the terminal may determine that at least one of the resources (e.g., the first UL resource and the second UL resource) is invalid, and may not perform UL transmission for beam reporting on at least one of the resources. For example, even if a terminal performs a first transmission on a first UL resource and reports to the base station that it will transmit beam report information on a second UL resource, the terminal may not perform the second UL transmission if there is no valid second UL resource that satisfies the condition of the third time gap with the first UL resource. Alternatively, the terminal may perform the first UL transmission only on a first UL resource that has at least one valid second UL resource that satisfies the condition of the third time gap.

[0129] Figure 5 is a conceptual diagram illustrating embodiments of a two-step beam reporting method that considers ineffective resources.

[0130] Referring to FIG. 5, a first UL resource and a second UL resource may be configured in a terminal for a two-step beam report. The terminal may determine a beam report trigger event based on the above embodiments, and perform a beam report operation based on the first UL resource and the second UL resource after the event occurrence time. The first UL resource may include a first occasion and a second occasion, and the second UL resource may include a first occasion and a second occasion.

[0131] The first occasion of the first UL resource may be a valid resource, and the first occasion of the second UL resource may be an invalid resource. In this case, there may not be a second UL resource that is correlated with the first UL resource within the first occasion. Both the second occasion of the first UL resource and the second occasion of the second UL resource may be valid resources. In this case, the first UL resource and the second UL resource within the second occasion may be correlated. In this case, several embodiments may be considered for the beam reporting operation of the terminal.

[0132] In one embodiment, since the first occasion of the first UL resource does not have a second UL resource associated with it, the terminal may not perform the first UL transmission according to the event in the first occasion of the first UL resource. This action may mean that the terminal does not perform the second UL transmission according to the event in the first occasion of the second UL resource either. In this case, the terminal may cancel or omit the beam reporting operation according to the event. Alternatively, the terminal may perform the beam reporting operation according to the event in a second occasion after the first occasion. The beam reporting operation according to the event may be postponed. In other words, the terminal may perform the first UL transmission according to the event in the second occasion of the first UL transmission, and may perform the second UL transmission according to the event in the second occasion of the second UL transmission.

[0133] In another embodiment, the terminal may perform the first UL transmission according to the event in the first occasion of the first UL resource. The terminal may not perform the second UL transmission in the second UL resource because the first occasion of the second UL resource is an invalid resource. The second UL transmission of the terminal may be postponed to a next occasion, and the second UL transmission may be performed in the next occasion. In other words, the terminal may perform the second UL transmission according to the event in the second occasion of the second UL resource. In this case, the terminal may transmit (e.g., retransmit) the first UL transmission once again in the second occasion of the first UL resource. In other words, the first UL transmission may be performed repeatedly. In this case, the second occasion of the second UL resource may be considered to be interrelated with the first occasion of the first UL resource and the second occasion of the first UL resource. Alternatively, the terminal may not perform the first UL transmission in the second occasion of the first UL resource. In this case, the second occasion of the second UL resource may be considered to be correlated with the first occasion of the first UL resource. In this case, even though the first UL transmission is not performed in the second occasion of the first UL resource, the second occasion of the first UL resource may be considered to be correlated with the second occasion of the second UL resource. Alternatively, the second occasion of the first UL resource may be considered not to be correlated with the second occasion of the second UL resource. Accordingly, a one-to-one mapping relationship may be established between the first UL resource and the second UL resource. In the above embodiment, the first occasion of the first UL resource may be considered to be correlated with the second occasion of the second UL resource.For example, each first UL resource may be correlated with an earliest valid second UL resource among second UL resources that appear after each first UL resource (e.g., after a predetermined time offset from each first UL resource). In this case, a certain second UL resource (e.g., a second occasion of the second UL resource) may be correlated with a plurality of first UL resources (e.g., a first occasion of the first UL resource and a second occasion of the first UL resource). If a first UL transmission is performed on at least one first UL resource among the plurality of first UL resources correlated with the second UL resource, the terminal may perform a second UL transmission on the second UL resource.

[0134] Figure 6 is a conceptual diagram illustrating embodiments of a two-step beam reporting method considering ineffective resources.

[0135] Referring to FIG. 6, a first UL resource appearing after an event occurrence time may include a first occasion and a second occasion, and the second UL resource may include a first to a third occasion. A plurality of second UL resources may be mapped between the first occasion of the first UL resource and the second occasion of the first UL resource, and among the plurality of second UL resources, a first occasion of the second UL resource may be an invalid resource, and a second occasion of the second UL resource may be a valid resource. In this case, the first occasion of the first UL resource may be correlated with the second occasion of the second UL resource. In other words, the first occasion of the first UL resource may be correlated with at least one valid second UL resource (e.g., an occasion of the second UL resource). The first occasion of the invalid second UL resource may be considered as not being correlated with the first occasion of the first UL resource. In other words, the first UL resource may be correlated with the earliest valid second UL resource among a plurality of second UL resources existing within a given time interval. Alternatively, the first occasion of the second UL resource may also be considered to be correlated with the first occasion of the first UL resource. As in the above-described embodiment, the correlation between the first UL resource and the second UL resource may include not only a one-to-one mapping but also a one-to-many mapping or a many-to-one mapping. The correlated first UL resource and the second UL resource may include an invalid resource.

[0136] Figure 7 is a conceptual diagram illustrating embodiments of a two-step beam reporting method that considers ineffective resources.

[0137] Referring to FIG. 7, similarly to the embodiment of FIG. 5, a first UL resource after a first event occurrence time may include a first occasion, and a second UL resource may include a second occasion. The first occasion of the first UL resource may be a valid resource, and the second occasion of the second UL resource may be an invalid resource. Accordingly, a second UL resource that is correlated with the first UL resource within the first occasion may not exist. On the other hand, both the second occasion of the first UL resource and the second occasion of the second UL resource may be valid resources. Accordingly, the first UL resource and the second UL resource within the second occasion may be correlated.

[0138] Similar to the above embodiment, the terminal may perform a first UL transmission according to a first event (e.g., occurrence of the first event) in a first occasion of the first UL resource, and may not perform a second UL transmission according to the first event (e.g., occurrence of the first event) in a first occasion of the second UL resource. In this case, the second event may occur before the second occasion of the first UL resource and the second occasion of the second UL resource. The second event may be a different event from the first event. In this case, the second UL transmission may reflect both the first event and the second event. For example, the terminal may transmit a second UL transmission including both beam information of the first event and beam information of the second event in the second occasion of the second UL resource. The first UL transmission in the second occasion of the first UL resource may or may not be transmitted again by the method described above. Alternatively, the second UL transmission may only reflect the first event, which is the event that previously triggered the first UL transmission, and the terminal may transmit the second UL transmission including beam information of the first event at a second occasion of the second UL resource. Alternatively, the second UL transmission may only reflect the second event, which is the most recently occurred event, and the terminal may transmit the second UL transmission including beam information of the second event at a second occasion of the second UL resource. In this case, the first UL transmission and the second UL transmission may reflect different events.

[0139] Meanwhile, in order to minimize the beam reporting delay time, the second UL resource may be set to a shorter cycle than the frequency at which the beam reporting operation of the terminal is actually triggered. Among the second UL resource cycles, there may be frequent cycles in which the second UL transmission is not performed, and the signaling overhead reduction effect of (method 100) may be reduced due to frequent transmission of DCI for rescheduling the second UL resource. Since a sufficient time gap must be secured between the first UL resource and the second UL resource in order to enable reuse of the second UL resource, the beam reporting delay reduction effect of (method 100) may be minimal compared to a method of dynamically scheduling the second UL resource.

[0140] In an environment where the advantages of (method 100) are difficult to utilize, the second UL resource can be dynamically indicated to the terminal based on DCI. The base station can receive a scheduling request for the second UL resource through the first UL transmission received from the terminal, and can schedule the second UL resource by transmitting a UL grant (e.g., uplink scheduling DCI) to the terminal. In a communication system, the UL grant can include DCI format 0_0, DCI format 0_1, DCI format 0_2, etc., and the UL grant can include DCI format 0_3 for scheduling PUSCH for a plurality of serving cells. The above-described method can be referred to as (method 200).

[0141] In one embodiment, the base station can semi-statically configure or dynamically instruct the terminal to apply either (method 100) or (method 200) depending on the situation. A signaling message for configuring / instructing (method 100) or (method 200) can be defined, and the message can be at least one of an RRC message, a MAC CE, or a DCI payload. The message can be transmitted and applied to each serving cell configured in the terminal.

[0142] In another embodiment, (method 100) and (method 200) may be used together. For example, the beam change cycle / frequency of the terminal may vary for each serving cell. Typically, beam report trigger events may occur more frequently in a serving cell supporting a higher frequency band (e.g., frequency range 2 (FR2)). (Method 100) may be applied to a first serving cell (e.g., a serving cell in a higher frequency band), and (method 200) may be applied to a second serving cell (e.g., a serving cell in a lower frequency band). (Method 100) and (method 200) may be used together in a single serving cell. For example, (Method 100) may be applied to some cycles of the first UL resource, and (Method 200) may be applied to other cycles of the first UL resource. For another example, different methods (e.g., (method 100) or (method 200)) may be applied to multiple TRPs belonging to the same serving cell. Different methods may be applied to bandwidth portions belonging to the same serving cell. Different methods may be applied to subbands. Different methods may be applied to duplex sections (e.g., subband-based full duplex (SBFD) symbols and non-SBFD symbols). For another example, either method (method 100) or (method 200) may serve as a fallback to the other method. For example, if a predetermined condition is satisfied while the terminal performs a second UL transmission on a second UL resource periodically configured based on (method 100), it may fallback to (method 200). When the method supported by the terminal falls back from (method 100) to (method 200), the terminal can dynamically receive scheduling information of the second UL resource from the base station and perform second UL transmission in the dynamically scheduled second UL resource.Alternatively, the same method may be applied to all serving cells configured in the terminal or all serving cells belonging to the same cell group. In this case, a message indicating the application of the same method may be applied commonly to the multiple serving cells.

[0143] According to the two-step beam reporting method, the first UL transmission may include only a small amount of information for determining whether a second UL transmission is performed on a second UL resource preset by the base station or whether a scheduling request for the second UL resource is made. The first UL transmission may preferably be transmitted via a PUCCH resource. When (method 200) is used, the terminal may transmit an SR (scheduling request) via the first UL resource and dynamically receive scheduling information for the second UL resource. In other words, the PUCCH resource on which the SR is transmitted (hereinafter referred to as an SR resource or PUCCH SR resource) may be set as the first UL resource.

[0144] The first UL resource may be a legacy SR resource, and the base station may transmit scheduling information for the UL-SCH or the PUSCH including a higher layer control message (e.g., MAC CE, RRC message) to the terminal in response to receiving the first UL transmission. If the beam report information is MAC CE, the MAC CE is included in a TB, and the TB is transmitted on the PUSCH, the above embodiment may operate normally. If the beam report information is UCI, the base station may have difficulty in distinguishing whether the purpose of the SR transmission by the terminal is to transmit UCI (e.g., beam report information) or other information as described above, based only on signal detection in the legacy SR resource. Below, several embodiments for solving the above problem will be described. In the embodiments below, it may be assumed that the second UL resource is a PUSCH resource.

[0145] According to a first embodiment, a terminal may generate a PUSCH including an indicator indicating whether beam report information is included in the PUSCH, and may transmit the PUSCH. The indicator may be transmitted for the purpose of allowing a base station to check whether UCI and / or TB are included in UL transmission, the UCI type, information included in the TB (e.g., UL-SCH, higher layer control message), etc. The beam report information may be a part of the UCI or one type of the UCI. The indicator may be mapped to a part of a PUSCH resource region, and the location of a resource to which the indicator is mapped may be determined based on a rule predefined in a technical specification and / or configuration information signaled from a base station (e.g., a resource size, a code rate, or a parameter corresponding to the information). Since the indicator must be detected before the UCI or TB included in the PUSCH, the indicator may be mapped to the earliest symbol(s) (e.g., the first A symbol(s)) among the symbols constituting the PUSCH resource.

[0146] The above indicator may be transmitted based on a sequence. For example, whether the PUSCH includes beam report information and / or type information of data included in the PUSCH (e.g., type information of the more detailed data described above) may be distinguished by a plurality of different sequences. A Zadoff-Chu (ZC) sequence having excellent correlation characteristics and characteristics advantageous for UL transmission may be used as the sequence. The sequence may be mapped to only one symbol among the symbols to which the PUSCH is mapped. For example, the sequence may be mapped to a symbol to which the PUSCH DM-RS is mapped. The sequence may be mapped to REs (or subcarriers) to which the PUSCH DM-RS is not mapped so as not to overlap with the PUSCH DM-RS. Alternatively, the indicator (e.g., the sequence) may be mapped to a symbol following the symbol to which the PUSCH DM-RS is mapped.

[0147] The above indicator may be transmitted via a PUSCH DM-RS. In other words, the PUSCH DM-RS may be transmitted for the purpose of indicating whether the PUSCH includes UCI (or beam report information) and / or the type of data included in the PUSCH, in addition to UL channel estimation. To support the above operation, a plurality of sequences may be defined as PUSCH DM-RS, and the plurality of sequences may be mapped to information indicating whether the PUSCH includes UCI (or beam report information) and / or to different data types (e.g., PUSCH data types), respectively. The UE may select one of the plurality of sequences, and may transmit the PUSCH DM-RS based on the selected one sequence, thereby informing the base station of the type of data included in the PUSCH and / or whether the PUSCH includes beam report information. According to the above-described method, the UL channel estimation performance based on DM-RS (e.g., PUSCH DM-RS) may be somewhat degraded, but an advantage may be obtained in that a large amount of PUSCH resources do not need to be allocated for transmission of the indicator.

[0148] In another embodiment, the indicator may be transmitted encoded using a forward error correction (FEC) code. For example, the indicator may be regarded as control information and may be polar encoded. If the number of bits constituting the indicator is less than or equal to a reference value (e.g., 13 bits), zero padding may be applied to the indicator until the payload size is greater than or equal to the reference value to ensure the performance of the polar code. Since the indicator must be individually decoded before other UCI (e.g., beam report information) or TB included in the PUSCH, it may be encoded and decoded separately from the UCI or TB.

[0149] According to a second embodiment, SR for beam reporting can be transmitted in a separate SR resource (hereinafter referred to as beam reporting SR resource) separated from legacy SR resources. The terminal can receive configuration information of a first SR resource (e.g., legacy SR resource) and a second SR resource (e.g., beam reporting SR resource) from the base station. The plurality of SR resources can be used for different purposes. For example, the terminal can transmit SR in the beam reporting SR resource to request a PUSCH resource to transmit beam reporting information, and can transmit SR in the legacy SR resource (or an SR resource other than the beam reporting SR resource) to request a PUSCH resource to transmit other information (e.g., another UCI, TB, UL-SCH, higher layer control message). The first SR resource and the second SR resource can be configured by independent SR settings, and the SR resources or the SR settings corresponding to the SR resources can be distinguished by different SR IDs (identifiers). In other words, a separate SR ID can be assigned to the beam reporting SR resource, which is distinct from other SR resources.

[0150] The beam report SR resource can be set to PUCCH format 0 or PUCCH format 1, and positive SR or negative SR can be transmitted in the beam report SR resource by being distinguished by multiple sequences. The multiple sequences can correspond to the same root sequence and can be distinguished by different cyclic shifts. The root sequence can be a ZC sequence.

[0151] The SR transmission procedure in the first SR resource and the SR transmission procedure in the second SR resource can be triggered independently. The SR transmission procedure in the first SR resource and the SR transmission procedure in the second SR resource can be managed independently. For example, the SR transmission in the first SR resource can be triggered by a higher layer of the terminal, and the SR transmission can be managed based on an SR_COUNTER. The SR transmission in the second SR resource can be triggered by a physical layer of the terminal based on a beam measurement result. The SR transmission in the second SR resource can be managed based on an SR_COUNTER, and the SR_COUNTER for the second resource can be managed (e.g., counted, reset) independently from the SR_COUNTER for the first SR resource. Based on the above-described settings, the SR transmission procedure for the first SR resource may not affect the SR transmission procedure for the second SR resource. If transmission of both UL-SCH and UCI (e.g., beam report information) is required, the terminal can transmit SR on both the first SR resource and the second SR resource. Considering the transmission power limitation of the terminal, there may be a constraint in the resource configuration so that the first SR resource and the second SR resource are not mapped on the same symbol. Alternatively, the terminal can transmit SR on only one of the first SR resource and the second SR resource that overlap in time, and can suspend SR transmission on the remaining SR resources. SR transmission on the remaining SR resources can be postponed to the next cycle. Alternatively, SR transmission on the remaining SR resources can be transmitted based on a counter operation.

[0152] Multiple SR transmission procedures may be interrelated. For example, when an SR for beam reporting and an SR for UL TB transmission occur simultaneously, the upper layer of the terminal may select one SR and transmit the selected SR to the physical layer. The operation of selecting one SR may be determined based on the priorities among SRs and / or the priorities among SR resources. For example, an SR for beam reporting may have priority over other SRs. For another example, the priority between an SR for beam reporting and an SR for UL SCH transmission may be determined based on the type of traffic included in the UL-SCH, QoS, logical channel, etc.

[0153] The first SR resource and the second SR resource may completely overlap in the time-frequency domain. The resource configuration parameters of the first SR resource and the second SR resource may be identical. If the two SR resources completely overlap, it may be difficult for the base station to determine which SR resource a detected signal (e.g., a sequence) corresponds to. To solve this problem, the sequences transmitted in the second SR resource may be composed of different sequences from the sequences transmitted in the first SR resource. For example, when a ZC sequence is used, different sequences corresponding to different cyclic shift values ​​may be used in the first SR resource and the second SR resource. For example, when there is a sequence group distinguished by 12 cyclic shifts, sequences corresponding to cyclic shifts 0 and 6 may be used in the first SR resource, and sequences corresponding to cyclic shifts 3 and 9 may be used in the second SR resource. Even if the two SR resources above completely overlap, the sequences can still be distinguished, and the SR detection performance may deteriorate somewhat as the cyclic shift distance between the sequences decreases. The terminal may not expect the configuration to partially overlap the first SR resource and the second SR resource. To avoid the above-described ambiguity problem, the terminal may not expect the first SR resource and the second SR resource to be arranged to overlap. The terminal may regard the case where the first SR resource and the second SR resource overlap as an error configuration, and may not perform SR transmission on the first SR resource and the second SR resource.

[0154] According to a third embodiment, a terminal can perform multiple SR transmissions for different purposes through a single SR resource. The multiple purposes can include at least a first purpose and a second purpose, and the first purpose can be to request UL resources for transmitting UCI (e.g., beam report information), and the second purpose can be to request UL resources for transmitting information other than the UCI (e.g., other UCI, TB, UL-SCH, upper layer control message). A positive SR can be subdivided into the multiple purposes. For example, K positive SRs and one negative SR corresponding to K purposes can be transmitted through the same SR resource, and the SR can have an information amount of ceil(log2(K+1)) bits. The (K+1) SRs can be distinguished by (K+1) sequences corresponding to the (K+1) SRs. The above sequences may correspond to the same root sequence, and the sequences may be distinguished by different cyclic shifts. Alternatively, the (K+1) SRs may be distinguished by both sequences and resources. For example, an SR resource may be configured with two sub-resources, and two candidate sequences may be transmitted in each sub-resource. In this case, the four SRs corresponding to K=3 may be distinguished by a combination of two sub-resources and two sequences.

[0155] The above embodiments may be implemented in combination. The base station may optionally configure (e.g., instruct) the terminal to use one or a combination of the above embodiments. According to the above embodiments, the base station may recognize the purpose of transmitting the SR from the terminal based on an indicator included in the received SR and / or PUSCH, and may receive a PUSCH corresponding to the purpose from the terminal. Alternatively, the base station may schedule the terminal to use the PUSCH corresponding to the purpose. The base station receiving the PUSCH corresponding to the purpose from the terminal may correspond to the case where (method 100) is used. The base station scheduling the terminal to use the PUSCH corresponding to the purpose may correspond to the case where (method 200) is used. When the base station schedules the terminal to use the PUSCH corresponding to the purpose, the DCI for scheduling the PUSCH (e.g., the second resource) may include a UCI indicator field (e.g., a UCI request field). According to the present disclosure, the UCI may be beam report information, and the UCI request field may mean a beam report indicator field. When the UCI request field is set to a predefined value, the UCI (e.g., beam report information) may be mapped to the PUSCH. The DCI scheduling the second resource may be transmitted via the PDCCH.

[0156] The beam report information can be interpreted as a category of CSI, and the UCI request field can be a CSI request field. For example, the existing CSI request field can be reused for the purpose of triggering transmission of beam report information initiated by the terminal. For another example, the existing CSI request field can still be used for the purpose of triggering a CSI report, and the UCI (e.g., beam report information initiated by the terminal) can be included in the CSI report as a type of the CSI report. In this case, transmission of the beam report information initiated by the terminal can be triggered by a specific codepoint of the CSI request field. The specific codepoint can be associated with a CSI trigger state for a beam report (e.g., beam report information) initiated by the terminal, and the CSI trigger state can be preset in the terminal based on RRC signaling. Alternatively, the UCI request field can be a separate DCI field that is distinct from the existing CSI request field. For example, a DCI scheduling a second UL transmission may include both a UCI request field and a CSI request field, and the DCI may simultaneously trigger "transmit a UE-initiated beam report" and "transmit a conventional CSI report." The UE may map both the UCI (e.g., a UE-initiated beam report) and the conventional CSI report to a PUSCH, and transmit the PUSCH to the base station via the second UL resource. Alternatively, if the DCI includes the UCI request indicator field, the DCI may not include the CSI request field. In other words, the DCI may trigger only one of the UCI request and the CSI request. Consequently, only one of the UCI report (e.g., a UE-initiated beam report) and the conventional CSI report may be mapped to a single PUSCH (e.g., a PUSCH that is a second UL resource).For example, each code point of the CSI request field may correspond to either the UCI report (e.g., a terminal-initiated beam report) or a conventional CSI report, and the CSI request field may include either a code point indicating the UCI report (e.g., a terminal-initiated beam report) or a code point indicating a conventional CSI report.

[0157] (In method 200), the terminal can expect to receive DCI scheduling the second UL transmission at a time that is not too late based on the time point at which the first UL transmission was performed. For example, the DCI scheduling the second UL transmission can be received within a time interval / window determined based on the first UL resource. If the terminal is instructed to perform the second UL transmission by a UCI request field (or, CSI request field) included in the DCI received within the time interval (e.g., window), the terminal can consider the instruction (e.g., instruction to perform the second UL transmission) to be valid and can transmit a PUSCH including at least beam report information to the base station. In other words, the second UL transmission including at least beam report information can be performed. If the UE is instructed to perform a second UL transmission by a UCI request field (or a CSI request field) included in DCI received outside the above time interval (e.g., window), the UE may consider the instruction (e.g., instruction to perform the second UL transmission) as invalid (e.g., outdated) and may not perform the second UL transmission (e.g., PUSCH transmission including at least beam report information). Alternatively, in this case, the UE may still follow the instruction. In other words, the UE may map the most recently generated beam report information to the PUSCH and transmit the PUSCH to the base station. Alternatively, the UE may not expect to receive a DCI instructing the second UL transmission outside the time interval. Alternatively, the UE may consider a DCI instructing the second UL transmission received after the time interval as invalid.If a DCI indicating a second UL transmission is received before the above time interval, the terminal may consider the second UL transmission to be for the first UL transmission prior to the first UL transmission, and may transmit a PUSCH including beam report information corresponding to the first UL transmission prior to the first UL transmission to the base station.

[0158] The DCI may include a UL-SCH indicator field. If the UL-SCH indicator field is set to a predefined specific value, the UL-SCH (or TB, upper layer control message) may be mapped to the PUSCH. The UE may determine resource configuration of the PUSCH, which is a second UL resource, by a combination of the UCI indicator field and the UL-SCH indicator field. If the DCI includes the UCI request field, the DCI may not include the UL-SCH indicator field. Alternatively, if the DCI includes the UCI request field, the UL-SCH field included in the DCI may be fixed to a value indicating that the UL-SCH is not to be loaded on the PUSCH. In this case, beam reporting information in the PUSCH, which is a second UL resource, may not be mapped together with the UL-SCH. In other words, the PUSCH may be a dedicated resource for transmitting UCI including beam reporting information initiated by the UE. The above embodiment can be equally applied to (Method 100). In (Method 100), the second UL resource may be a CG (configured grant)-PUSCH, and the CG-PUSCH may be configured in the terminal not to include the UL-SCH. The CG-PUSCH may be a dedicated resource for transmitting UCI including beam report information. Even without performing a separate signaling procedure with the base station, the terminal may regard the second UL resource as a PUSCH not including the UL-SCH, and thus may transmit the second UL resource without mapping the UL-SCH to the second UL resource. A type of UCI other than the UCI including beam report information may be mapped to the second UL resource (e.g., the CG-PUSCH) together with (or multiplexed with) the UCI including beam report information.In other words, other types of UCI than UCI including beam reporting information can be multiplexed with UCI including beam reporting information on the second UL resource (e.g., the CG-PUSCH). The other types of UCI can include SR, LRR (link recovery request), HARQ-ACK, CSI, etc.

[0159] (In method 200), for a terminal supporting carrier aggregation, a carrier (or serving cell) for which a second UL resource is configured may be different from a carrier (or serving cell) for which a DCI for scheduling the second UL resource is transmitted. In other words, the terminal may receive DCI in a first carrier, and the DCI may schedule a second UL resource in a second carrier. The terminal may perform a second UL transmission (e.g., PUSCH transmission) in the second UL resource scheduled by the DCI in the second carrier. The subcarrier spacing applied to the first carrier may be the same as or different from the subcarrier spacing applied to the second carrier.

[0160] Even when (method 100) is used to configure a second UL resource, the terminal may transmit an SR on the first UL resource. In this case, the purpose of the SR transmission may not be to request a second UL resource from the base station, but to notify the base station that a signal will be transmitted on the already configured second UL resource. If a positive SR (e.g., a positive SR corresponding to a beam report) is received on the first UL resource, the base station may perform an operation for receiving a second UL transmission on the second UL resource associated with the first UL resource. If another SR is received on the first UL resource, the base station may omit the operation for receiving the second UL transmission. If the terminal transmits a positive SR on the first UL resource, the terminal may perform the second UL transmission on the second UL resource associated with the first UL resource. If the terminal transmits an SR other than a positive SR (e.g., a negative SR) in the first UL resource, the terminal may not perform a second UL transmission in the second UL resource associated with the first UL resource. In (method 100), the first UL resource is not necessarily an SR resource. The first UL resource may be a PUCCH resource, and a UCI other than an SR may be transmitted in the first UL resource. The UCI may be control information indicating "whether the terminal will perform the second UL transmission in the second UL resource", "whether the terminal will transmit beam report information in the second UL resource", "whether the terminal will activate the second UL resource", etc. The second UL resource may be a resource interrelated with the first UL resource. When the UCI is used, the first UL resource may be distinguished from an SR resource, and the first UL resource may not be associated with an SR ID. As another example, the terminal can inform the base station of the presence or absence of a second UL transmission by transmitting a reference signal (e.g., SRS) in the first UL resource.

[0161] (Method 100), if the opportunistic reuse of the second UL resource is abandoned, the second UL resource may be arranged closer to the first UL resource. The first UL resource and the second UL resource may be mapped to a common resource region, and the first UL resource and the second UL resource may not be distinguished separately. In other words, the second-stage beam reporting operation may be performed based on one UL resource. For example, the second-stage beam reporting operation may be performed based on one PUSCH resource, and the one PUSCH resource may include a first resource region that functions as a first UL resource and a second resource region that functions as a second UL resource. The terminal may perform the first UL transmission in the first resource region of the PUSCH, and may perform the second UL transmission in the second resource region of the PUSCH. The base station may attempt a reception operation for the second resource region when the first UL transmission is detected in the first resource region. The base station may omit a reception operation for the second resource region if the first UL transmission is not detected in the first resource region. The reception operations for the first resource region and the second resource region may be performed based on a common DM-RS (e.g., a PUSCH DM-RS) and / or a common beam (e.g., a terminal transmission beam and / or a base station reception beam). In an embodiment, the PUSCH may be a CG PUSCH, and a PUSCH including at least CG-UCI may be transmitted in the first resource region, and a PUSCH including at least UCI (e.g., beam reporting information) may be transmitted in the second resource region.

[0162] In the above embodiments, the second UL transmission may be retransmitted. The terminal may transmit the second UL transmission to the base station, and may retransmit the second UL transmission if a response signal (e.g., a response message) for the second UL transmission is not received. In (method 100), the response signal may be a signal including an acknowledgement message or a HARQ-ACK for the second UL transmission. The second UL transmission may be a CG-PUSCH, and the response signal may be a PDCCH having a CRC scrambled by a CS (configured scheduling)-RNTI or a DCI included in the PDCCH. In (method 200), the second UL transmission may be a dynamically scheduled PUSCH, and the response signal may be a DCI scheduling a retransmission of the PUSCH. The DCI may be transmitted through a PDCCH having a CRC scrambled by a C-RNTI or an MCS-C-RNTI. If the second UL transmission does not include the UL-SCH, the second UL transmission may not be assigned a HARQ process ID and the HARQ retransmission procedure may not be applied. In this case, the retransmission of the second UL transmission may simply mean a PUSCH scheduled by a DCI other than the DCI that scheduled the initial PUSCH, a PUSCH transmitted on the CG-PUSCH resource allocated in the next period, etc.

[0163] A retransmission of a second UL transmission may include the same beam report information (e.g., the same UCI payload) as the initial transmission (e.g., the initial transmission, the first transmission). The base station may receive the initial transmission and the retransmission of the second UL transmission, and may improve reception performance by performing soft combining for the initial transmission and the retransmission. Additional beam measurement operations may be performed and the beam report information may be updated before the retransmission of the second UL transmission. Alternatively, a new event may occur before the retransmission of the second UL transmission. In this case, the beam report information (e.g., UCI) included in the retransmission of the second UL transmission may be different from the beam report information (e.g., UCI) included in the initial transmission of the second UL transmission. For example, a retransmission of the second UL transmission may include updated beam report information for the same event (e.g., new beam(s), beam quality value of the new beam(s), current beam(s), and / or beam quality value of the current beam(s)). Alternatively, a retransmission of the second UL transmission may include beam report information for the new event or "beam report information for the event reflected in the initial transmission and beam report information for the new event." The second UL transmission may include a UL-SCH (e.g., TB, UL data). In this case, a retransmission of the second UL transmission may include the same UL-SCH (e.g., TB, UL data) as the initial transmission of the second UL transmission. In other words, even if a UCI mapped to each PUSCH transmission changes, a TB mapped to each PUSCH transmission may be the same. Retransmission of the second UL transmission may be performed when the second UL transmission includes a UL-SCH (e.g., TB). For example, the method may be applied only to (method 200).

[0164] A PUSCH containing beam report information may have a higher priority than other uplink transmissions (e.g., other PUSCHs or PUCCHs). If a transmission collision occurs, the PUSCH containing the beam report information may be transmitted preferentially. Or, if a transmission collision occurs, at least the beam report information may be transmitted preferentially. The priority between the beam report information and other UCIs may be defined. If the beam quality of a terminal is degraded, the procedure for recovering the beam may be more important than traffic transmission, and based on the importance, the beam report information may have a higher priority than SR and HARQ-ACK. The beam report information may have a higher priority than CSI. Meanwhile, the beam report information may be defined as a part of CSI or a subtype of CSI. In this case, the beam report information may have a higher priority than other types of CSI (e.g., PMI, CQI, RI, LI, SSBRI, CRI, etc.). If transmissions of multiple UCI types collide and it is difficult to transmit all of the conflicting UCI types together, some UCI types may be dropped based on the priorities among the UCIs.

[0165] If at least one of the first UL resource and the second UL resource is not configured, the terminal may not perform a beam reporting operation initiated by the terminal. The operation may include not performing an operation of monitoring a beam reporting trigger event. If a beam reporting trigger event occurs but at least one of the first UL resource and the second UL resource is not configured or is deactivated, the terminal may trigger a random access procedure by transmitting a preamble on a PRACH resource. The random access procedure may be a non-contention-based random access, and the PRACH resource and the preamble may be preset in the terminal. Alternatively, the random access procedure may be a contention-based random access, and the preamble may be randomly selected by a higher layer of the terminal.

[0166] When a beam report trigger event occurs but the terminal has not yet performed the first UL transmission and receives scheduling information of a valid PUSCH, the terminal may transmit beam report information by piggybacking or multiplexing it on the PUSCH. To support the above operation, the base station may reserve a resource region in the PUSCH to which beam report information (e.g., UCI) may be mapped. If there is beam report information to be reported by the terminal, the terminal may map the beam report information to the resource region reserved by the base station and transmit a PUSCH including the beam report information. If there is no beam report information to be reported by the terminal, the terminal may not map the beam report information to the resource region reserved by the base station. If there is no beam report information to be reported by the terminal, the terminal may additionally map PUSCH data other than beam report information to the resource region reserved by the base station. The performance of the additional mapping operation may be notified to the base station by separate indication information included in the PUSCH. Alternatively, the base station can implementally verify the performance of the additional mapping operation. The piggybacking operation or multiplexing operation can be indicated based on a UCI request field included in the DCI scheduling the PUSCH. The PUSCH (e.g., PUSCH resource) can be interpreted as a second UL resource in terms of including beam report information. In other words, the second UL resource does not necessarily have to be requested only by the first UL resource, and the second UL resource can be constantly allocated by the base station. The terminal can receive allocation information of the second UL resource for transmitting UCI (e.g., a beam report initiated by the terminal) without performing the first UL transmission, and can transmit the UCI (e.g., a beam report initiated by the terminal) to the base station through the second UL resource.That the second UL resource includes the UCI may be indicated by a UCI request field of the DCI scheduling the second UL resource.

[0167] In a certain time interval (e.g., a certain slot, a certain symbol set), a first UL transmission may collide with another UL transmission. For example, the other UL transmission may be a PUCCH transmission for transmitting another UCI other than beam report information. The other UCI may have the same priority as the beam report UCI. Alternatively, the other UCI may have a lower priority than the beam report UCI. The other UCI may include SR, LRR, etc. If the first UL resource overlaps with another PUCCH resource including a UCI having a lower priority than the beam report UCI in the same slot and / or the same symbol, the terminal may preferentially perform the first UL transmission. The terminal may omit PUCCH transmission in the other PUCCH resource. Conversely, if the first UL resource overlaps with another PUCCH resource including a UCI having a higher priority than the beam report UCI in the same slot and / or the same symbol, the terminal may omit the first UL transmission and transmit the PUCCH in the other PUCCH resource. For example, SR, LRR, etc. may have the same priority as the beam report UCI. Messages (e.g., UCIs) included in the transmissions may be multiplexed and transmitted in one UL resource. The one UL resource may be determined by a predetermined rule. If the first UL resource is an SR resource, the one UL resource may be determined as another UL resource (e.g., another PUCCH resource) that collided with the first UL resource or a third UL resource. The third UL resource may be a resource included in a PUCCH resource candidate set configured for the terminal.

[0168] [Resource settings considering multiple beams]

[0169] Considering multi-beam operation, the first UL resource and the second UL resource can be configured as multiple resources. In the unified TCI framework, the terminal can perform the first UL transmission based on the UL TCI currently applied if the UL TCI is valid. The beam report trigger event may include that the beam quality of the current UL TCI is lower than a reference value (e.g., the beam quality of the current UL TCI is degraded), and the current UL TCI may be invalid. In this case, the first UL transmission can be performed based on a UL TCI different from the current UL TCI (e.g., a different UL beam).

[0170] As a method for flexibly supporting UL beam replacement operation, a method of configuring a first UL resource into multiple resources may be considered. The first UL resource may include M resources that are periodically repeated by the same period value, and the M resources may follow the same resource configuration. M may be a natural number. Different beams (e.g., UL TCIs) may be applied to the M resources. If it is necessary to distinguish between the M resources and the first UL resource, each of the M resources may be referred to as an occasion or a sub-resource. For example, if the first UL resource is an SR resource, a plurality of resources constituting the SR resource may be referred to as SR occasions or SR sub-resources.

[0171] Figure 8 is a conceptual diagram illustrating embodiments of a method for setting up a first UL resource.

[0172] Referring to FIG. 8, the first UL resource may be configured with M resources, and M may be 6. M may be the number of new candidate beams (e.g., UL TCIs, resource indices corresponding to UL beams) configured for the beam report trigger event. The M first UL resources may be respectively correlated with the M candidate beams. If there is a new beam among the M candidate beams to replace the degraded current beam, the terminal may perform a first UL transmission based on the beam (e.g., the new beam) in the first UL resource associated with the beam. In this case, the base station may implicitly find out the new beam selected by the terminal based on the received first UL transmission without receiving beam report information. If the beam report information is configured to include only index information of the new beam, the second UL transmission in the above embodiment may be omitted, and the second UL resource may not be configured for the terminal. The operation according to the above embodiment may be effective when a beam report trigger event includes UL beam degradation, when a joint TCI is set in a terminal, etc.

[0173] In the above embodiment, the value of M can be dynamically changed by DCI or MAC CE signaling. Resetting the first UL resource every time the value of M changes can be burdensome, and beam reporting delay time can increase when beam reporting is triggered in the reset period. As a method for solving the above problem, the first UL resource can be configured to include L resources. L can be a natural number. M can be managed as a value that is always less than or equal to L, and the M candidate beams can be mapped to M resources among the L resources, and no beams can be mapped to the remaining (LM) resources. The terminal can regard the M resources as valid resources, and can perform the first UL transmission by selecting one of the M resources. In other words, the first UL transmission can be performed on the selected one resource. The remaining (LM) resources can not be used for the first UL transmission. The remaining (LM) resources can be dynamically overridden by other transmissions. The above beam mapping can be updated whenever the set of candidate beams changes, and the beam of the first UL resource can be managed without reset signaling of the first UL resource.

[0174] Figure 9 is a conceptual diagram illustrating embodiments of a method for setting up a first UL resource.

[0175] Referring to FIG. 9, a first UL resource may include M resources, and M may be 4. UL beams (e.g., UL TCIs, resource indexes corresponding to the UL beams) may be configured for each of the first UL resources, and M may denote the number of UL beams configured for the first UL resources. If a current UL beam (e.g., UL TCI) matches one of the M UL beams, the terminal may perform a first UL transmission based on the current UL beam in the first UL resource corresponding to the current UL beam. If the current UL beam does not match the M UL beams, the terminal may select one beam from the M UL beams, and perform a first UL transmission based on the selected beam in the first UL resource associated with the selected beam. The one beam may be arbitrarily selected by the terminal. For example, the terminal can perform a beam measurement operation and select one beam having the highest beam quality among the M UL beams based on the beam measurement result. The base station can monitor all of the M first UL resources and successfully detect the first UL transmission in one of the M first UL resources. Alternatively, the one beam can be determined based on beam report information previously reported by the terminal to the base station. In this case, the base station can specify some UL beams (e.g., one UL beam) among the M UL beams and perform monitoring for the specified some UL beams. Therefore, the reception complexity of the base station can be reduced.

[0176] In the embodiment of FIG. 9, unlike the first UL resource, the second UL resource associated with the first UL resource may be configured as a single resource. The terminal may equally apply a beam applied to the first UL transmission to the second UL transmission, and the base station may equally use a beam used for reception of the first UL transmission for reception of the second UL transmission. Alternatively, the terminal may apply a beam (e.g., a UL TCI corresponding to the DL TCI, the joint TCI) corresponding to a beam used for reception of a DCI scheduling the second UL resource to the second UL transmission. Alternatively, information indicating a beam of the second UL resource may be included in the DCI, and the beam of the second UL resource may be dynamically indicated to the terminal. The beam indicated by the DCI may be a beam determined by the terminal to be outdated (e.g., a beam having a beam quality below a reference value, a degraded beam). In this case, the terminal may omit the second UL transmission operation scheduled by the DCI. Alternatively, the terminal may perform the second UL transmission by replacing the indicated beam with another beam. For example, the other beam may be the beam used for the first UL transmission, and the base station may receive the second UL transmission by considering both the indicated beam and the possibility that the other beam was applied. According to the above embodiments, the UL beam to be applied to the second UL transmission may be specified in advance, and it may be sufficient for the second UL resource to have one resource.

[0177] Figure 10 is a conceptual diagram illustrating embodiments of a method for setting up a second UL resource.

[0178] Referring to FIG. 10, the second UL resource may include N resources. N may be a natural number. For example, each of N and M may be 4. UL beams (e.g., UL TCIs, resource indices corresponding to the UL beams) may be configured for each of the second UL resources, and N may denote the number of UL beams configured for the second UL resources. The beam of the second UL resource may be configured independently from the beam of the first UL resource. N may be configured to be the same value as M. Alternatively, N may be configured to be different from M. N may be restricted to not have a value greater than M. The terminal may first select one beam from among the N beams, and perform second UL transmission based on the selected beam in the second UL resource associated with the selected beam. The beam selected for the second UL transmission may be the same as or different from the beam selected for the first UL transmission. In other words, the two-step beam reporting method can be performed based on a plurality of different UL beams. The above-described embodiment can flexibly support situations where the coverage of the first UL transmission and the second UL transmission are different, situations where the beam shapes of the first UL transmission and the second UL transmission are different, situations where the channel or beam environment changes rapidly between the first UL transmission and the second UL transmission, etc.

[0179] The above embodiments can also be applied when beam management is performed based on an integrated TCI. For example, a single UL TCI can be indicated to a terminal, and the UL TCI can be applied collectively to terminal-specific UL transmissions. In this case, in order to flexibly support UL beam replacement operations, the first UL resource and / or the second UL resource can include multiple resources based on the above embodiments, and multiple beams can exceptionally be involved in the first UL transmission and / or the second UL transmission. The candidate beams applied to the first UL resource can include at least the UL integrated TCI indicated to the terminal (e.g., currently applied). The candidate beams applied to the second UL resource can include at least the UL integrated TCI indicated to the terminal. On the other hand, when multiple UL integrated TCIs are indicated to the terminal to support multi-TRP transmission, the first UL transmission and the second UL transmission can each be transmitted based on any one of the multiple UL integrated TCIs. In this case, the values ​​of M and N may not exceed the number of indicated UL integrated TCIs.

[0180] The above embodiments can be applied at least when the first UL resource and the second UL resource are transmitted on the same carrier. For a terminal supporting carrier aggregation, the first UL resource and the second UL resource can be allocated to different carriers. The first beam(s) applied to the first UL resource can be different from the second beam(s) applied to the second UL resource, and the above-described correlation relationship between the first beam(s) and the second beam(s) may not be established. The second beam(s) can be configured independently of the first beam(s). For example, the QCL source signal(s) of the UL TCI(s) corresponding to the second beam(s) can be configured independently of the QCL source signal(s) of the UL TCI(s) corresponding to the first beam(s). Even if the first UL resource and the second UL resource are configured on different carriers, the above embodiments can be applied when the first beams and the second beams have a QCL relationship with each other.

[0181] When (method 200) is used for configuring the second UL resource, the terminal may perform a PDCCH monitoring operation to receive scheduling information of the second UL resource after the first UL transmission. The DCI for scheduling the second UL resource may be monitored in a CORESET and / or a search space set separately configured for a beam reporting operation. The search space set may be a USS set, and the search space set may be configured terminal-specifically. Alternatively, the search space set may be a CSS set, and the search space set may be configured commonly for a plurality of terminals, and the search space set may be shared by a plurality of terminals. The search space set may be conveniently referred to as a beam reporting search space set, and a CORESET corresponding to the beam reporting search space set may be referred to as a beam reporting CORESET.

[0182] Monitoring of beam report CORESET can be performed as part of beam report procedure, and beam report CORESET may not be monitored before beam report procedure is triggered or after beam report procedure is completed. The period during which the terminal monitors beam report CORESET can be explicitly defined or set. For example, the terminal can monitor beam report CORESET after transmission of SR. The start time of beam report CORESET monitoring may be a time point after a predetermined time has passed from the first UL resource. When the first UL resource is composed of multiple resources, the first UL resource, which is a criterion for determining the start time of beam report CORESET monitoring, may be a resource through which the terminal transmitted SR. Alternatively, the first UL resource, which is a criterion for determining the start time of beam report CORESET monitoring, may be the last resource among the resources constituting the first UL resource.

[0183] The end point of beam report CORESET monitoring can be defined in several ways. In one embodiment, the terminal may no longer monitor the beam report CORESET after successfully receiving the DCI scheduling the second UL resource. In this case, the end point of beam report CORESET monitoring may be a point in time after a predetermined time offset has passed from the resource on which the DCI was received. In another embodiment, the end point of beam report CORESET monitoring may be determined as a point in time after a predetermined time offset has passed from the second UL resource on which the second UL transmission was performed or a point in time before the second UL resource on which the second UL transmission was performed. If the second UL resource is configured with multiple resources, the second UL resource, which is a criterion for determining the end point of beam report CORESET monitoring, may be a resource on which the terminal performed the second UL transmission. Alternatively, the second UL resource, which is a criterion for determining the end point of the beam report CORESET monitoring, may be any one of the resources constituting the second UL resource (e.g., the last resource or the first resource).

[0184] Reception of the second UL transmission may fail at the base station, in which case the second UL transmission may be retransmitted. The retransmission of the second UL transmission may be performed on a resource dynamically allocated by DCI. Alternatively, if the second UL resource is a CG PUSCH, the retransmission of the second UL transmission may be performed on a CG PUSCH resource that is configured semi-statically. The above operation may be applied to a communication system in an unlicensed band. According to another embodiment that takes into account the possibility of retransmission of the second UL resource, the terminal may terminate the monitoring operation of the beam report CORESET after completion of the beam report procedure. For example, the terminal may determine that the beam report procedure is completed if it receives a response or confirmation message for the second UL transmission from the base station. Alternatively, the terminal may determine that the beam report procedure is completed if it receives beam indication information from the base station after the second UL transmission. The beam(s) indicated by the beam indication information may match the candidate beam(s) reported by the terminal. Alternatively, even if the beam(s) indicated by the beam indication information do not match the candidate beam(s) reported by the terminal, the terminal may determine that the beam reporting procedure is completed. Alternatively, the terminal may determine that the beam reporting procedure is completed "after the terminal performs retransmission of the second UL transmission an allowed number of times" or "if the terminal does not receive a response message or confirmation message for the retransmission."

[0185] The number of blind decodings performed in the beam reporting CORESET, the number of channel-estimated CCEs, and / or the number of monitored DCI sizes may be counted for the corresponding serving cell only during the beam reporting CORESET monitoring period. Alternatively, the number of blind decodings performed in the beam reporting CORESET, the number of channel-estimated CCEs, and / or the number of monitored DCI sizes may be exceptionally excluded from the counting. In other words, the operation of the terminal additionally monitoring the beam reporting CORESET may not affect other PDCCH monitoring operations of the terminal.

[0186] The beam reporting CORESET may be monitored based on a DL beam corresponding to the UL beam applied to the first UL transmission (e.g., a beam of the same source signal as the UL beam or a DL beam associated with the UL beam). This operation may be applied when the first UL transmission and the beam reporting CORESET monitoring operation are performed on the same carrier. The DL beam corresponding to the UL beam applied to the first UL transmission may not exist. For example, when the DL TCI and the UL TCI are separately set and managed, the UL beam and the DL beam may not correspond one-to-one. When the carrier on which the first UL resource is transmitted and the carrier on which the beam reporting CORESET is monitored are different, the DL beam corresponding to the UL beam applied to the first UL transmission may not exist. In this case, the reception beam of the beam reporting CORESET may be determined as the DL TCI indicated to the terminal (e.g., the currently applied DL TCI). When multiple DL TCIs are indicated to a terminal, the reception beam of the beam reporting CORESET may be determined as at least one DL TCI among the multiple DL TCIs. If the beam quality of the DL TCI(s) is deteriorated, the DL TCI(s) may be difficult to use as the CORESET reception beam. In this case, the terminal may selectively apply the DL beam(s) corresponding to the DL TCI(s) or the UL beam used for the first UL transmission to the monitoring of the beam reporting CORESET according to a predetermined rule or condition.

[0187] In one embodiment, the DCI scheduling the second UL resource may be considered a response message or an acknowledgement message for the first UL transmission of the terminal, and the base station may not separately transmit an acknowledgement message (e.g., a response message) for the second UL transmission to the terminal. If the terminal does not receive the DCI scheduling a retransmission of the second UL transmission for a predetermined period of time, the base station may consider that the second UL transmission has been normally received. In this case, the terminal may determine that the beam reporting procedure has been completed. The predetermined period of time may be determined by a timer operation initiated by the second UL transmission.

[0188] In another embodiment, the base station may transmit a response message or an acknowledgement message to the terminal for receiving the second UL transmission. The terminal may monitor a DCI having a predefined format or field settings, and may complete a beam reporting procedure by receiving the DCI. The DCI may be monitored in a separately configured CORESET and / or search space set, and the DCI may be monitored temporarily after the second UL transmission. In one embodiment, the beam reporting information may be transmitted via another UL resource (e.g., a PUSCH allocated for TB or CSI transmission) that is not requested by the first UL transmission. In this case, it may be desirable to transmit a response message for the transmission of the beam reporting information. Considering the above embodiment, the DCI may be transmitted in a search space set that the terminal constantly monitors, and the DCI may follow a DCI format that includes DL / UL scheduling information.

[0189] The operations of the method according to the embodiments of 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 that stores information readable by a computer system. Furthermore, a computer-readable recording medium can be distributed across network-connected computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.

[0190] Additionally, the computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. The program instructions may include not only machine language codes produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc.

[0191] While some aspects of the present disclosure have been described in the context of a device, they may also represent a description of 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 as 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 or more of the most significant method steps may be performed by such a device.

[0192] In embodiments, 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 herein. In embodiments, the field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described herein. In general, the methods are preferably performed by some hardware device.

[0193] Although the present disclosure has been described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the claims below.

Claims

1. By terminal method, A step of performing a first beam quality measurement operation on the current beam; A step of performing a second beam quality measurement operation on one or more candidate beams; A step of determining whether an event condition is satisfied based on the result of the first beam quality measurement operation and the result of the second beam quality measurement operation; When the above event condition is satisfied, a step of transmitting a first UL signal to a base station from a first UL (uplink) resource; and A step of transmitting a second UL signal including beam reporting information from a second UL resource to the base station, The current beam corresponds to the TCI (transmission configuration information) indicated to the terminal, and the one or more candidate beams correspond to one or more beam quality measurement resources determined based on configuration information received from the base station. Terminal method.

2. In claim 1, The first UL signal is a physical uplink control channel (PUCCH), the PUCCH includes uplink control information (UCI), and the UCI includes information requesting the second UL resource to the base station. Terminal method.

3. In claim 1, The second UL resource is a PUSCH (physical uplink shared channel) resource scheduled by DCI (downlink control information) received from the base station, the second UL signal is a PUSCH, and the DCI includes information indicating that beam reporting information is to be included in the PUSCH. Terminal method.

4. In claim 1, The first UL signal is a PUCCH, the PUCCH includes a UCI, and the UCI includes information informing the base station whether the terminal transmits the second UL signal in the second UL resource. Terminal method.

5. In claim 1, The second UL resource is a PUSCH resource having a correlation with the first UL resource, the second UL signal is a PUSCH, the second UL resource is mapped to a time resource that is at least N symbols later than the first UL resource, and N is a natural number. Terminal method.

6. In claim 5, The above PUSCH does not include UL-SCH (shared channel). Terminal method.

7. In claim 1, The repetition cycles of the first UL resource and the second UL resource are determined based on the same cycle value. Terminal method.

8. In claim 1, The first beam quality measurement operation includes an operation of measuring L1-RSRP (layer1-reference signal received power) for the current beam, and the second beam quality measurement operation includes an operation of measuring L1-RSRP for the one or more candidate beams. Terminal method.

9. In claim 1, The beam report information includes at least one of a beam quality measurement result regarding the current beam or a beam quality measurement result regarding one or more candidate beams. Terminal method.

10. In claim 1, The above TCI is a DL (downlink) TCI, and the one or more beam quality measurement resources corresponding to the one or more candidate beams include at least one of a SSB (synchronization signal block) resource or a CSI (channel state information)-RS (reference signal) resource. Terminal method.

11. As a terminal, The terminal comprises at least one processor, At least one processor of the terminal, Perform a first beam quality measurement operation on the current beam; Performing a second beam quality measurement operation on one or more candidate beams; Determine whether an event condition is satisfied based on the result of the first beam quality measurement operation and the result of the second beam quality measurement operation; If the above event condition is satisfied, transmit a first UL signal to the base station from the first UL (uplink) resource; and Causing the base station to transmit a second UL signal including beam reporting information in the second UL resource, The current beam corresponds to the TCI (transmission configuration information) indicated to the terminal, and the one or more candidate beams correspond to one or more beam quality measurement resources determined based on configuration information received from the base station. Terminal.

12. In claim 11, The first UL signal is a physical uplink control channel (PUCCH), the PUCCH includes uplink control information (UCI), and the UCI includes information requesting the second UL resource to the base station. Terminal.

13. In claim 11, The second UL resource is a PUSCH (physical uplink shared channel) resource scheduled by DCI (downlink control information) received from the base station, the second UL signal is a PUSCH, and the DCI includes information indicating that beam reporting information is to be included in the PUSCH. Terminal.

14. In claim 11, The first UL signal is a PUCCH, the PUCCH includes a UCI, and the UCI includes information informing the base station whether the terminal transmits the second UL signal in the second UL resource. Terminal.

15. In claim 11, The second UL resource is a PUSCH resource having a correlation with the first UL resource, the second UL signal is a PUSCH, the second UL resource is mapped to a time resource that is at least N symbols later than the first UL resource, and N is a natural number. Terminal.

16. In claim 15, The above PUSCH does not include UL-SCH (shared channel). Terminal.

17. In claim 11, The repetition cycles of the first UL resource and the second UL resource are determined based on the same cycle value. Terminal.

18. In claim 11, The first beam quality measurement operation includes an operation of measuring L1-RSRP (layer1-reference signal received power) for the current beam, and the second beam quality measurement operation includes an operation of measuring L1-RSRP for the one or more candidate beams. Terminal.

19. In claim 11, The beam report information includes at least one of a beam quality measurement result regarding the current beam or a beam quality measurement result regarding one or more candidate beams. Terminal.

20. In claim 11, The above TCI is a DL (downlink) TCI, and the one or more beam quality measurement resources corresponding to the one or more candidate beams include at least one of a SSB (synchronization signal block) resource or a CSI (channel state information)-RS (reference signal) resource. Terminal.

Images