Method and device for reporting channel state information in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. The present disclosure relates to operations of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for performing a reception beam performance report initiated from a terminal in a wireless communication system, and a device capable of performing same.

Description

Method and device for reporting channel status information in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for reporting channel state information in a wireless communication system and an apparatus capable of performing the same.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and Massive Machine-Type Communications (mMTC), technologies included beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands; support for various numerologies (such as operating multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources; initial access techniques to support multi-beam transmission and broadband; the definition and operation of Band-Width Parts (BWP); Low Density Parity Check (LDPC) codes for high-volume data transmission; new channel coding methods such as Polar Codes for the reliable transmission of control information; and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes to expand network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) to incorporate Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas to guarantee coverage in the terahertz band of 6G mobile communication technology; metamaterial-based lenses and antennas; high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM); and Reconfigurable Intelligent Surface (RIS) technology to improve terahertz band signal coverage; as well as full-duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and Artificial Intelligence (AI) from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] The disclosed embodiments aim to provide devices and methods capable of effectively providing services in a mobile communication system. Specifically, the present disclosure proposes a method and device for efficiently performing terminal initiation beam reporting. The technical objectives to be achieved by the present disclosure are not limited to those mentioned above, and other unmentioned technical problems may be considered by those skilled in the art from the embodiments of the present invention described below.

[0009] The disclosed embodiment provides an apparatus and a method capable of effectively providing a service in a mobile communication system. Specifically, a method performed by a terminal of a communication system comprises the step of receiving configuration information for a user equipment initiated beam reporting from a base station, wherein the configuration information is channel state information (CSI) reporting configuration information, and the configuration information includes PUCCH (physical uplink control channel) resource information for the terminal to initiate a received beam reporting when Event 1 occurs, and information indicating whether an indicator indicating whether a specific new received beam transmitted through the received beam reporting satisfies the conditions of Event 1 is included in the received beam reporting; the step of confirming that Event 1 has occurred because the conditions of Event 1 are satisfied; the step of generating the received beam reporting including information about the specific new received beam; and the step of transmitting an indicator for the received beam reporting on the PUCCH resource indicated by the PUCCH resource information. The method includes the step of transmitting the received beam report over a PUSCH (physical uplink shared channel), wherein the received beam report includes an indicator indicating whether the specific new received beam satisfies the condition of event 1, and the condition of event 1 corresponds to the case where the RSRP value of the new received beam is greater than the threshold value of the current received beam.

[0010] Additionally, in a method performed by a base station of a communication system, the method comprises the step of transmitting configuration information for a user equipment-initiated beam reporting to a terminal, wherein the configuration information is channel state information (CSI) reporting configuration information, and wherein the configuration information includes PUCCH (physical uplink control channel) resource information for the terminal to initiate a received beam reporting when Event 1 occurs, and information indicating whether an indicator indicating whether a specific new received beam transmitted through the received beam reporting satisfies the conditions of Event 1 is included in the received beam reporting; and the step of receiving an indicator for the received beam reporting on the PUCCH resource indicated by the PUCCH resource information. The method includes the step of receiving the received beam report over a PUSCH (physical uplink shared channel), wherein the received beam report includes information about the specific new received beam and an indicator indicating whether the specific new received beam satisfies the condition of the event 1, and the condition of the event 1 corresponds to the case where the RSRP value of the new received beam is greater than the threshold value of the current received beam.

[0011] In addition, a terminal of a communication system comprises: at least one transceiver; and at least one processor connected to the at least one transceiver to enable communication. A memory storing instructions that are connected to communicate with at least one processor and can be executed individually or in any combination of the at least one processor, wherein the terminal: receives configuration information for a beam reporting initiated by the terminal from a base station, wherein the configuration information is channel state information (CSI) reporting configuration information, wherein the configuration information includes PUCCH (physical uplink control channel) resource information for the terminal to initiate a received beam reporting when Event 1 occurs, and information indicating whether a specific new received beam transmitted through the received beam reporting satisfies the conditions of Event 1, and whether an indicator indicating whether the specific new received beam satisfies the conditions of Event 1 is included in the received beam reporting; confirm that Event 1 has occurred because the conditions of Event 1 are satisfied; generate the received beam reporting including information about the specific new received beam; transmit the indicator for the received beam reporting on the PUCCH resource indicated by the PUCCH resource information; and transmit the received beam reporting over a PUSCH (physical uplink shared channel); The receiving beam report includes an indicator that indicates whether the specific new receiving beam satisfies the condition of event 1, and the condition of event 1 corresponds to the case where the RSRP value of the new receiving beam is greater than the threshold value of the current receiving beam.

[0012] Additionally, in a base station of a communication system, at least one transceiver; at least one processor connected to communicate with the at least one transceiver; and a memory connected to communicate with the at least one processor and executable individually or in any combination of the at least one processor, wherein the base station: transmits configuration information for a user equipment initiated beam reporting to a terminal, wherein the configuration information is channel state information (CSI) reporting configuration information, wherein the configuration information includes PUCCH (physical uplink control channel) resource information for the terminal to initiate a received beam reporting when Event 1 occurs, and information indicating whether an indicator indicating whether a specific new received beam transmitted through the received beam reporting satisfies the conditions of Event 1 is included in the received beam reporting; and a memory storing an instruction to receive an indicator for the received beam reporting on the PUCCH resource indicated by the PUCCH resource information, and to receive the received beam reporting on a PUSCH (physical uplink shared channel). The receiving beam report includes information about the specific new receiving beam and an indicator indicating whether the specific new receiving beam satisfies the condition of Event 1, wherein the condition of Event 1 corresponds to the case where the RSRP value of the new receiving beam is greater than the threshold value of the current receiving beam.

[0013] The disclosed embodiments provide an apparatus and a method capable of effectively providing services in a mobile communication system. Specifically, through at least one embodiment of the present disclosure, a terminal can effectively perform terminal-based beam reporting.

[0014] The effects obtainable from the various embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by those skilled in the art based on the following detailed description.

[0015] FIG. 1 is a diagram illustrating the basic structure of the time-frequency domain in a wireless communication system according to one embodiment of the present disclosure.

[0016] FIG. 2 is a drawing illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0017] FIG. 3 is a drawing illustrating an example of a bandwidth portion setting in a wireless communication system according to one embodiment of the present disclosure.

[0018] FIG. 4 is a diagram of the beam application time that can be considered when using an integrated TCI method in a wireless communication system according to one embodiment of the present disclosure.

[0019] FIG. 5 is a diagram showing another MAC-CE structure for activating and indicating a joint TCI state or a separate DL or UL TCI state in a wireless communication system according to one embodiment of the present disclosure.

[0020] Figure 6 is a diagram illustrating an example of a non-periodic CSI reporting method.

[0021] FIG. 7 is a diagram illustrating an example of setting a control area of ​​a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0022] FIG. 8 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0023] FIG. 9 is a diagram illustrating a channel measurement and channel status reporting method according to the setting and instructions of a base station according to one embodiment of the present disclosure.

[0024] FIG. 10 is a diagram illustrating a method for determining the current receiving beam in [Event 3] according to one embodiment of the present disclosure.

[0025] FIG. 11 is a diagram illustrating the operation process of a terminal and a base station for a CSI report initiated by a terminal using a PUCCH resource that triggers a reception beam performance report initiated by a terminal according to one embodiment of the present disclosure.

[0026] FIG. 12 is a diagram illustrating the operation process of a terminal and a base station for a CSI report initiated by a terminal using a pair of reserved PUCCH resources and PUSCH transmissions according to one embodiment of the present disclosure.

[0027] FIG. 13 is a diagram illustrating a receiving beam reporting operation process initiated from a terminal when a second PUSCH resource is shared among upper layer signaling for one or more events according to one embodiment of the present disclosure.

[0028] FIG. 14 is a diagram illustrating a receiving beam reporting operation process initiated from another terminal when a second PUSCH resource is shared among upper layer signaling for one or more events according to one embodiment of the present disclosure.

[0029] FIG. 15 is a diagram illustrating a receiving beam reporting operation process initiated from another terminal when a second PUSCH resource is shared among upper layer signaling for one or more events according to one embodiment of the present disclosure.

[0030] FIG. 16 is a diagram illustrating a receiving beam reporting operation process initiated from another terminal when a second PUSCH resource is shared among upper layer signaling for one or more events according to one embodiment of the present disclosure.

[0031] FIG. 17 is a diagram showing a receiving beam performance reporting format initiated from a terminal when one or more events occur according to one embodiment of the present disclosure.

[0032] FIG. 18 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0033] FIG. 19 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0034] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0035] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0036] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0037] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.

[0038] Hereinafter, a base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. A terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technologies (5G, new radio, NR) developed after LTE-A may be included therein, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0039] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing instruction means to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0040] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.

[0041] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0042] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards like 3GPP’s HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2’s HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE’s 802.16e.

[0043] As a representative example of the above-mentioned broadband wireless communication system, the LTE system employs the orthogonal frequency division multiplexing (OFDM) method for the downlink (DL) and the single carrier frequency division multiple access (SC-FDMA) method for the uplink (UL). The uplink refers to a wireless link through which a terminal transmits data or control signals to a base station, and the downlink refers to a wireless link through which a base station transmits data or control signals to a terminal. The above-mentioned multiple access method can distinguish the data or control information of each user by allocating and operating time-frequency resources to be sent for each user so that they do not overlap, that is, so that orthogonality is established.

[0044] As a future communication system following LTE, that is, a 5G communication system, it must be able to freely reflect the diverse requirements of users and service providers, and therefore, services that satisfy various requirements simultaneously must be supported. Services being considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0045] eMBB aims to provide data transmission speeds that are superior to those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink from the perspective of a single base station. Furthermore, while providing these peak data rates, the 5G communication system must also provide an increased user-perceived data rate. To satisfy these requirements, it necessitates improvements in various transmission and reception technologies, including enhanced multi-input multi-output (MIMO) transmission technology. Additionally, while LTE transmits signals using a maximum bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can meet the data transmission speeds required by using a frequency bandwidth wider than 20 MHz in frequency bands of 3–6 GHz or above 6 GHz.

[0046] Simultaneously, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT, mMTC requires support for a large number of terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT devices are attached to various sensors and equipment to provide communication functions, the system must be able to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km²). Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in dead zones not covered by cells, such as building basements; therefore, they may require wider coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must consist of low-cost devices, and since it is difficult to frequently replace terminal batteries, a very long battery life of 10 to 15 years may be required.

[0047] Finally, URLLC is a mission-critical cellular-based wireless communication service. For example, consider services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For instance, services supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds, and simultaneously 10 -5It has the following packet error rate requirements. Therefore, for services supporting URLLC, 5G systems must provide a transmit time interval (TTI) smaller than other services, and at the same time, design considerations may be required to allocate a wide resource in the frequency band to ensure the reliability of the communication link.

[0048] The three 5G services, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. In this case, different transmission and reception techniques and parameters may be used between the services to satisfy the different requirements of each service. Of course, 5G is not limited to the three services mentioned above.

[0049] Hereinafter, a / b may be understood as at least one of a or b.

[0050] [NR Time-Frequency Resources]

[0051] The frame structure of the 5G system will be explained in more detail below with reference to the drawings.

[0052] Figure 1 is a diagram illustrating the basic structure of the time-frequency domain, which is a wireless resource domain where data or control channels are transmitted in a 5G system.

[0053] The horizontal axis of FIG. 1 represents the time domain, and the vertical axis represents the frequency domain. In the time and frequency domains, the basic unit of a resource is a resource element (RE, 101), which can be defined as one OFDM symbol (102) on the time axis and one subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can form a resource block (RB, 104). In the time axis, one subframe (110) may contain multiple OFDM symbols (102). For example, the length of one subframe may be 1 ms.

[0054] FIG. 2 is a drawing illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0055] FIG. 2 illustrates an example of a frame (200), subframe (201), and slot (202) structure. One frame (200) can be defined as 10ms. One subframe (201) can be defined as 1ms, and thus one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot). = 14). One subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per one subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In an example of FIG. 2, cases where μ=0 (204) and μ=1 (205) are shown as the setting value for the subcarrier spacing. When μ=0 (204), one subframe (201) may be composed of one slot (202), and when μ=1 (205), one subframe (201) may be composed of two slots (203). That is, the number of slots per one subframe ( ) may vary, and accordingly, the number of slots per frame ( ) may vary. Depending on each subcarrier spacing setting μ and It can be defined by [Table 1] below.

[0056] μ 014101114202214404314808414160165143203261464064

[0057] [Bandwidth Section (BWP)]

[0058] Next, the configuration of the bandwidth part (BWP) in a 5G communication system will be explained in detail with reference to the drawing.

[0059] FIG. 3 is a drawing illustrating an example of a bandwidth portion setting in a wireless communication system according to one embodiment of the present disclosure.

[0060] FIG. 3 shows an example in which the terminal bandwidth (UE bandwidth) (300) is configured into two bandwidth portions, namely bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station may configure one or more bandwidth portions for the terminal and may configure the information in [Table 2] below for each bandwidth portion.

[0061] BWP ::= SEQUENCE {bwp-Id BWP-Id,(Bandwidth Identifier)locationAndBandwidth INTEGER (1..65536),(Bandwidth Location)subcarrierSpacing ENUMERATED {n0, n1, n2, n3, n4, n5},(Subcarrier Spacing)cyclicPrefix ENUMERATED { extended}(Cyclical Prefix)}

[0062] Of course, the above examples are not limited, and various parameters related to bandwidth portions may be configured for the terminal in addition to the above configuration information. The above information may be transmitted by the base station to the terminal via higher-layer signaling, for example, RRC (radio resource control) signaling. At least one of the configured bandwidth portions may be activated. Whether a configured bandwidth portion is activated may be transmitted semi-statically from the base station to the terminal via RRC signaling or dynamically via DCI.

[0063] According to some embodiments, prior to the RRC connection, the terminal may receive an Initial Bandwidth Part (Initial BWP) for initial connection from the base station via a Master Information Block (MIB). More specifically, during the initial connection phase, the terminal may receive configuration information for a control resource set (CORESET) and a search space via the MIB, through which a PDCCH can be transmitted to receive system information required for initial connection (which may correspond to remaining system information (RMSI) or system information block 1 (SIB1)). The control resource set and the search space configured via the MIB may each be considered as Identity (ID) 0. The base station may notify the terminal via the MIB of configuration information, such as frequency allocation information, time allocation information, and numerology, for control resource set #0. Additionally, the base station may notify the terminal via the MIB of configuration information regarding the monitoring period and monitoring occasion for control resource set #0, i.e., configuration information for search space #0. The terminal may consider the frequency region set as control region #0 obtained from the MIB as the initial bandwidth portion for initial access. In this case, the identifier (ID) of the initial bandwidth portion may be considered as 0.

[0064] The settings for the bandwidth portion supported by the above 5G can be used for various purposes.

[0065] According to some embodiments, if the bandwidth supported by the terminal is smaller than the system bandwidth, this can be supported through the bandwidth portion setting. For example, by setting the frequency position of the bandwidth portion (setting information 2) to the terminal, the terminal can transmit and receive data at a specific frequency position within the system bandwidth.

[0066] In addition, according to some embodiments, a base station may set multiple bandwidth portions for a terminal for the purpose of supporting different numerologies. For example, to support data transmission and reception using both a 15 kHz subcarrier interval and a 30 kHz subcarrier interval for a terminal, two bandwidth portions may be set to subcarrier intervals of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be frequency division multiplexed (FDM), and when data transmission and reception is to be performed with a specific subcarrier interval, the bandwidth portion set to that subcarrier interval may be activated.

[0067] In addition, according to some embodiments, a base station may set a bandwidth portion having different bandwidth sizes for the purpose of reducing the power consumption of the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and always transmits and receives data using that bandwidth, very large power consumption may occur. In particular, in a situation where there is no traffic, performing monitoring of an unnecessary downlink control channel using a large bandwidth of 100 MHz may be very inefficient in terms of power consumption. To reduce the power consumption of the terminal, the base station may set a bandwidth portion of a relatively small bandwidth, such as 20 MHz, for the terminal. In a situation where there is no traffic, the terminal can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it can transmit and receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0068] In the method for configuring the above bandwidth portion, terminals prior to RRC connection can receive configuration information for the Initial Bandwidth Part (Initial BWP) via the MIB during the initial connection phase. More specifically, the terminal can receive a configuration of a control area (i.e., CORESET) for a downlink control channel through which a DCI scheduling SIBs can be transmitted from the MIB of the PBCH (physical broadcast channel). The bandwidth of the control area configured by the MIB can be considered as the Initial Bandwidth Part, and through the configured Initial Bandwidth Part, the terminal can receive the PDSCH (physical downlink shared channel) through which SIBs are transmitted. In addition to receiving SIBs, the Initial Bandwidth Part may also be utilized for other system information (OSI), paging, and random access.

[0069] [Bandwidth Section (BWP) Change]

[0070] When one or more bandwidth parts are set for a terminal, the base station may instruct the terminal to change (or switch, transition) the bandwidth part using the bandwidth part indicator field in the DCI. For example, in FIG. 3, if the currently active bandwidth part of the terminal is bandwidth part #1 (301), the base station may instruct the terminal to bandwidth part #2 (302) using the bandwidth part indicator in the DCI, and the terminal may perform a bandwidth part change to bandwidth part #2 (302) indicated by the received bandwidth part indicator in the DCI.

[0071] As mentioned above, since DCI-based bandwidth portion changes can be directed by the DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth portion change request, it must be able to receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth portion without difficulty. To this end, the standard specifies the delay time (T) required when changing the bandwidth portion. BWP The requirements for ) have been specified and can be defined, for example, as shown in [Table 3] below.

[0072] μNR Slot length (ms)BWP switch delay T BWP (slots)Type 1 Note 1 Type 2 Note 1 011310.52520.253930.125618Note 1: Depends on UE capability.Note 2: If the BWP switch involves changing of SCS, the BWP switch delay is determined by the larger one between the SCS before BWP switch and the SCS after BWP switch.

[0073] The requirements for bandwidth portion change delay time support Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth portion delay time type to the base station.

[0074] In accordance with the aforementioned requirements for bandwidth portion change delay time, if the terminal receives a DCI containing a bandwidth portion change indicator in slot n, the terminal performs a change to the new bandwidth portion indicated by the bandwidth portion change indicator in slot n+T BWPCompletion can be performed at a time no later than the new bandwidth portion, and transmission and reception for the data channel scheduled by the corresponding DCI can be performed in the changed new bandwidth portion. If the base station intends to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP By considering ), time-domain resource allocation for a data channel can be determined. That is, when a base station schedules a data channel with a new bandwidth portion, in the method for determining time-domain resource allocation for a data channel, the data channel can be scheduled after the bandwidth portion change delay time. Accordingly, the terminal [is notified] that the DCI instructing the bandwidth portion change is the bandwidth portion change delay time (T BWP You may not expect to indicate a slot offset (K0 or K2) value smaller than )

[0075] If a terminal receives a DCI (e.g., DCI format 1_1 or 0_1) instructing a change in the bandwidth portion, the terminal may not perform any transmission or reception during a time interval corresponding to the time interval from the third symbol of the slot in which the PDCCH containing the said DCI was received to the beginning of the slot indicated by the slot offset value (K0 or K2) indicated by the time domain resource allocation indicator field within the said DCI. For example, if a terminal receives a DCI instructing a change in the bandwidth portion in slot n, and the slot offset value indicated by the said DCI is K, the terminal may not perform any transmission or reception from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+K-1).

[0076] [Unified TCI state]

[0077] The following describes a method for instructing and activating a single TCI state based on the unified TCI scheme. The unified TCI scheme refers to a method of managing transmit and receive beams by integrating the TCI state used for downlink reception and the spatial relation info used for uplink transmission—which were distinguished in the existing Rel-15 and Rel-16—into a single TCI state. Therefore, when a terminal receives instructions from a base station based on the unified TCI scheme, it can perform beam management using the TCI state for uplink transmission as well. If the terminal receives a TCI-State, which is a higher-layer signaling with the tci-stateId-r17, from the base station, the terminal can perform operations based on the unified TCI scheme using that TCI-State. The TCI-State can exist in two forms: a joint TCI state or a separate TCI state.

[0078] The first form is a joint TCI state, and the terminal can receive instructions from the base station regarding the TCI state to be applied for both uplink transmission and downlink reception through a single TCI-State. If the terminal receives a TCI-State based on the joint TCI state, the terminal can receive instructions regarding parameters to be used for downlink channel estimation using the RS corresponding to qcl-Type1 within the joint TCI state-based TCI-State, and parameters to be used as a downlink reception beam or reception filter using the RS corresponding to qcl-Type2. If the terminal receives a TCI-State based on the joint TCI state, the terminal can receive instructions regarding parameters to be used as an uplink transmission beam or transmission filter using the RS corresponding to qcl-Type2 within the joint DL / UL TCI state-based TCI-State. In this case, if the terminal receives a joint TCI state, the terminal can apply the same beam to both uplink transmission and downlink reception.

[0079] The second form is a separate TCI state, and the terminal can individually receive instructions from the base station for an UL TCI state to be applied for uplink transmission and a DL TCI state to be applied for downlink reception. If the terminal is instructed with an UL TCI state, the terminal can be instructed with parameters to be used as an uplink transmission beam or transmission filter using a reference RS or source RS set within the corresponding UL TCI state. If the terminal is instructed with a DL TCI state, the terminal can be instructed with parameters to be used for downlink channel estimation using an RS corresponding to qcl-Type1 set within the corresponding DL TCI state, and parameters to be used as a downlink reception beam or reception filter using an RS corresponding to qcl-Type2.

[0080] If the terminal is instructed with both a DL TCI state and a UL TCI state, the terminal may be instructed with parameters to be used as an uplink transmission beam or transmission filter using a reference RS or source RS set within the corresponding UL TCI state, parameters to be used for downlink channel estimation using an RS corresponding to qcl-Type1 set within the corresponding DL TCI state, and parameters to be used as a downlink reception beam or reception filter using an RS corresponding to qcl-Type2. In this case, if the reference RS or source RS set within the DL TCI state and the UL TCI state instructed to the terminal are different, the terminal may apply beams individually to uplink transmission and downlink reception, respectively, based on the instructed UL TCI state and DL TCI state.

[0081] A terminal can receive up to 128 upper-layer signalings for each specific bandwidth part within a specific cell from the base station for joint TCI states, and among the separate TCI states, DL TCI states can be received as upper-layer signalings for each specific bandwidth part within a specific cell, up to 64 or 128 based on terminal capability reports, and among the separate TCI states, DL TCI states and joint TCI states can use the same upper-layer signaling structure. For example, if 128 joint TCI states are set and 64 DL TCI states are set among the separate TCI states, the 64 DL TCI states can be included in the 128 joint TCI states.

[0082] Among the separate TCI states, the UL TCI state can be configured with up to 32 or 64 upper layer signalings for each specific bandwidth part within a specific cell based on terminal capability reporting, and like the relationship between the DL TCI state and the joint TCI state among the separate TCI states, the UL TCI state and the joint TCI state among the separate TCIs may also use the same upper layer signaling structure, or the UL TCI state among the separate TCIs may use a different upper layer signaling structure from the joint TCI state and the DL TCI state among the separate TCIs.

[0083] Using different or identical upper-layer signaling structures in this way may be defined in the specifications, or may be distinguished through another upper-layer signaling configured by the base station based on a terminal capability report containing information on which of the two usage modes the terminal can support.

[0084] The terminal can receive instructions regarding transmit / receive beams in an integrated TCI manner by utilizing one of the joint TCI state and separate TCI state configured by the base station. The terminal can receive a configuration from the base station via upper-layer signaling regarding whether to use one of the joint TCI state or separate TCI state.

[0085] The terminal receives instructions related to the transmit / receive beam using one of the selected methods among the joint TCI state and the separate TCI state through upper layer signaling, and at this time, there may be two types of transmit / receive beam instructions from the base station: a MAC-CE based instruction method and a MAC-CE based activation and DCI based instruction method.

[0086] If a terminal receives instructions related to transmit / receive beams using the joint TCI state method through upper layer signaling, the terminal can perform a transmit / receive beam application operation by receiving a MAC-CE indicating the joint TCI state from the base station, and the base station can schedule the terminal to receive a PDSCH containing the corresponding MAC-CE through the PDCCH. If there is only one joint TCI state included in the MAC-CE, the terminal can determine the uplink transmit beam or transmit filter and the downlink receive beam or receive filter using the indicated joint TCI state starting 3 ms after the PUCCH transmission containing HARQ-ACK information indicating whether reception of the PDSCH including the MAC-CE was successful. If there are two or more joint TCI states included in the MAC-CE, the terminal can confirm that the multiple joint TCI states indicated by the MAC-CE correspond to each code point in the TCI state field of DCI format 1_1 or 1_2 starting 3 ms after the PUCCH transmission containing HARQ-ACK information indicating whether reception of the PDSCH including the MAC-CE was successful, and activate the indicated joint TCI states. Subsequently, the terminal can receive DCI format 1_1 or 1_2 and apply the one joint TCI state indicated by the TCI state field within the DCI to the uplink transmit and downlink receive beams. In this case, DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include it (without DL assignment).

[0087] If a terminal receives instructions regarding transmit / receive beams using a separate TCI state method through upper layer signaling, the terminal can perform a transmit / receive beam application operation by receiving a MAC-CE from the base station that indicates a separate TCI state, and the base station can schedule the terminal to receive a PDSCH containing the MAC-CE via a PDCCH. If there is only one set of separate TCI states included in the MAC-CE, the terminal can determine the uplink transmit beam or transmit filter and the downlink receive beam or receive filter by using the separate TCI states included in the indicated set of separate TCI states starting 3 ms after the transmission of a PUCCH containing HARQ-ACK information indicating whether the PDSCH was successfully received. At this time, a separate TCI state set may refer to a single or multiple separate TCI states that a single code point of the TCI state field in DCI format 1_1 or 1_2 may have, and a separate TCI state set may include one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state. If there are two or more separate TCI state sets included by MAC-CE, the terminal may confirm that the multiple separate TCI state sets indicated by MAC-CE correspond to each code point of the TCI state field in DCI format 1_1 or 1_2 starting 3 ms after a PUCCH transmission containing HARQ-ACK information indicating whether the PDSCH was successfully received, and activate the indicated separate TCI state sets.In this case, each code point in the TCI state field of DCI format 1_1 or 1_2 may indicate one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state each. The terminal receives DCI format 1_1 or 1_2 and can apply the separate set of TCI states indicated by the TCI state field within the corresponding DCI to the uplink transmit and downlink receive beams. In this case, DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include it (without DL assignment).

[0088] FIG. 4 is a diagram of the beam application time that can be considered when using an integrated TCI method in a wireless communication system according to one embodiment of the present disclosure. As described above, the terminal receives DCI format 1_1 or 1_2 from a base station that includes downlink data channel scheduling information (with DL assignment) or does not include it (without DL assignment), and can apply one joint TCI state or a set of separate TCI states indicated by the TCI state field within the DCI to the uplink transmit and downlink receive beams.

[0089] - DCI format 1_1 or 1_2 with DL assignment (400): If a terminal receives DCI format 1_1 or 1_2 containing downlink data channel scheduling information from a base station (401) and indicates a set of one joint TCI state or separate TCI state based on the integrated TCI method, the terminal receives a PDSCH scheduled based on the received DCI (405) and can transmit a PUCCH containing a HARQ-ACK indicating whether the reception of the DCI and PDSCH was successful (410). At this time, the HARQ-ACK may include the meaning of whether the reception of the DCI and PDSCH was successful, and if at least one of the DCI and PDSCH is not received, the terminal can transmit a NACK, and if both are successfully received, the terminal can transmit an ACK.

[0090] - DCI format 1_1 or 1_2 without DL assignment (450): If a terminal receives DCI format 1_1 or 1_2 from a base station that does not include downlink data channel scheduling information (455) and indicates one joint TCI state or a separate set of TCI states based on a combined TCI method, the terminal may assume at least one combination of the following for the DCI.

[0091] ■ Includes scrambled CRC using CS-RNTI.

[0092] ■ The value of all bits assigned to all fields used as RV (Redundancy Version) fields is 1.

[0093] ■ The value of all bits assigned to all fields used as MCS (Modulation and Coding Scheme) fields is 1.

[0094] ■ The value of all bits assigned to all fields used as NDI (New Data Indication) fields is 0.

[0095] ■ For FDRA (Frequency Domain Resource Allocation) Type 0, the value of all bits allocated to the FDRA field is 0; for FDRA Type 1, the value of all bits allocated to the FDRA field is 1; and for the FDRA method dynamicSwitch, the value of all bits allocated to the FDRA field is 0.

[0096] The terminal may transmit a PUCCH containing a HARQ-ACK indicating whether reception of DCI format 1_1 or 1_2, in which the above-described items are assumed, was successful (460).

[0097] - For both DCI format 1_1 or 1_2 with DL assignment (400) and without DL assignment (450), if the new TCI state indicated by DCI (401, 455) is the same as the TCI state that was previously indicated and applied to the uplink transmit and downlink receive beams, the terminal can maintain the previously applied TCI state; if the new TCI state is different from the previously indicated TCI state, the terminal can determine the application time of the joint TCI state or separate TCI state set that can be indicated from the TCI state field included in the DCI as after the first slot (420, 470) (430, 480) after a time equal to BAT (beam application time, 415, 465) after PUCCH transmission, and can use the previously indicated TCI-state until before the slot (420, 470) (425, 475).

[0098] - For both DCI format 1_1 or 1_2 with DL assignment (400) and without DL assignment (450), BAT can be set to upper layer signaling based on terminal capability reporting information as a specific number of OFDM symbols, and the numerology for BAT and the first slot after BAT can be determined based on the smallest numerology among all cells to which the joint TCI state or separate TCI state set indicated through DCI is applied.

[0099] A terminal can apply a single joint TCI state indicated via MAC-CE or DCI to the reception of control resource sets connected to all terminal-specific search spaces, the reception of PDSCH scheduled to PDCCH transmitted from said control resource set and the transmission of PUSCH, and the transmission of all PUCCH resources.

[0100] If a separate set of TCI states indicated via MAC-CE or DCI includes a DL TCI state, the terminal can apply the separate set of TCI states to the reception of control resource sets connected to all terminal-specific search spaces, and to the reception of PDSCH scheduled to PDCCH transmitted from said control resource sets, and can apply it to all PUSCH and PUCCH resources based on the previously indicated UL TCI state.

[0101] If a separate set of TCI states indicated via MAC-CE or DCI includes one UL TCI state, the terminal can apply it to all PUSCH and PUCCH resources, and based on the previously indicated DL TCI state, it can apply it to receiving control resource sets connected to all terminal-specific search spaces, and receiving PDSCH scheduled to PDCCH transmitted from said control resource set.

[0102] If a separate set of TCI states indicated by MAC-CE or DCI includes one DL TCI state and one UL TCI state, the terminal may apply the DL TCI state to the reception of control resource sets connected to all terminal-specific search spaces and to the reception of PDSCH scheduled to PDCCH transmitted from said control resource sets, and may apply the UL TCI state to all PUSCH and PUCCH resources.

[0103] [Unified TCI state MAC-CE]

[0104] The following describes a single TCI state instruction and activation method based on an integrated TCI method. A terminal receives a PDSCH containing the following MAC-CE from a base station and, starting from the third slot after transmitting a HARQ-ACK for the PDSCH to the base station, can interpret each code point of the TCI state field in DCI format 1_1 or 1_2 based on the information within the MAC-CE received from the base station. That is, the terminal can activate each entry of the MAC-CE received from the base station to each code point of the TCI state field in DCI format 1_1 or 1_2.

[0105] FIG. 5 is a diagram illustrating another MAC-CE structure for activating and indicating a joint TCI state or a separate DL or UL TCI state in a wireless communication system according to one embodiment of the present disclosure. The meaning of each field within the MAC-CE structure may be as follows.

[0106] - Serving Cell ID (500): This field may indicate which serving cell the MAC-CE is to be applied to. The length of this field may be 5 bits. If the serving cell indicated by this field is included in one or more of the upper layer signalings simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4, the MAC-CE may be applied to all serving cells included in one or more of the lists simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4 that contain the serving cell indicated by this field.

[0107] - DL BWP ID (505): This field may indicate which DL BWP the MAC-CE is to be applied to, and the meaning of each code point in this field may correspond to each code point of the bandwidth part indicator in the DCI. The length of this field may be 2 bits.

[0108] - UL BWP ID (510): This field may indicate which UL BWP the MAC-CE is to be applied to, and the meaning of each code point in this field may correspond to each code point of the bandwidth part indicator in the DCI. The length of this field may be 2 bits.

[0109] - P i (515): This field may indicate whether each code point of the TCI state field in DCI format 1_1 or 1_2 has multiple TCI states or one TCI state. If P i If the value of is 1, it means that the corresponding i-th code point has multiple TCI states, which may mean that the code point can include a separate DL TCI state and a separate UL TCI state. If P i If the value of is 0, it means that the corresponding i-th code point has a single TCI state, which may mean that the code point may contain one of a joint TCI state, a separate DCI TCI state, or a separate UL TCI state.

[0110] - D / U (520): This field may indicate whether the TCI state ID field within the same octet is a joint TCI state, a separate DL TCI state, or a separate UL TCI state. If this field is 1, the TCI state ID field within the same octet may be a joint TCI state or a separate DL TCI state, and if this field is 0, the TCI state ID field within the same octet may be a separate UL TCI state.

[0111] - TCI state ID (525): This field may indicate a TCI state that can be identified by the upper layer signaling TCI-StateId. If the D / U field is set to 1, this field may be used to represent the TCI-StateId, which can be represented by 7 bits. If the D / U field is set to 0, the MSB (most significant bit) of this field may be considered a reserved bit, and the remaining 6 bits may be used to represent the upper layer signaling UL-TCIState-Id. The maximum number of TCI states that can be enabled is 8 for joint TCI states and 16 for separate DL or UL TCI states.

[0112] - R: Represents a reserved bit and can be set to 0.

[0113] Regarding the MAC-CE structure of FIG. 5 described above, the terminal may include a third octet containing fields P1, P2, ..., P8 in FIG. 5 in the MAC-CE structure, regardless of whether unifiedTCI-StateType-r17 in MIMOparam-r17 within ServingCellConfig, which is an upper layer signaling, is set to joint or separate. In this case, the terminal may perform TCI state activation using a fixed MAC-CE structure, regardless of the upper layer signaling received from the base station. As another example, regarding the MAC-CE structure of FIG. 5 described above, if unifiedTCI-StateType-r17 in MIMOparam-r17 within ServingCellConfig, which is an upper layer signaling, is set to joint, the terminal may omit the third octet containing fields P1, P2, ..., P8 in FIG. 5. In this case, the terminal can save up to 8 bits of the payload of the corresponding MAC-CE according to the upper layer signaling set by the base station. Additionally, all D / U fields located from the fourth octet to the first bit in FIG. 5 can be considered as R fields, and all corresponding R fields can be set to 0 bits.

[0114] [CSI resource configuration]

[0115] NR has a CSI framework for directing the measurement and reporting of channel state information (CSI) from a terminal at a base station. The CSI framework of NR can be composed of at least two elements: a resource setting and a report setting, and the report setting can have a connection relationship with the resource setting by referencing at least one ID of the resource setting.

[0116] According to one embodiment of the present disclosure, a resource setting may include information related to a reference signal (RS) for a terminal to measure channel state information. A base station may set at least one resource setting for a terminal. For example, a base station and a terminal may exchange signaling information such as [Table 4] to transmit information regarding a resource setting.

[0117] -- ASN1START-- TAG-CSI-RESOURCECONFIG-STARTCSI-ResourceConfig ::= SEQUENCE {csi-ResourceConfigId CSI-ResourceConfigId,csi-RS-ResourceSetList CHOICE {nzp-CSI-RS-SSB SEQUENCE {nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetIdOPTIONAL, -- Need R},csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId},bwp-Id BWP-Id,resourceType ENUMERATED { aperiodic, semiPersistent, periodic},...}-- TAG-CSI-RESOURCECONFIG-STOP-- ASN1STOP

[0118] In [Table 4], the signaling information CSI-ResourceConfig contains information for each resource setting. According to the signaling information, each resource setting may include a resource setting index (csi-ResourceConfigId), a BWP index (bwp-ID), a resource time-axis transmission setting (resourceType), or a resource set list (csi-RS-ResourceSetList) containing at least one resource set. The resource time-axis transmission setting may be set to aperioditic transmission, semi-persistent transmission, or periodic transmission. The resource set list may be a set containing resource sets for channel measurement or a set containing resource sets for interference measurement. If the resource set list is a set containing resource sets for channel measurement, each resource set may include at least one resource, which may be a CSI reference signal (CSI-RS) resource or an index of a synchronous / broadcast channel block (SS / PBCH block, SSB). If the resource set list is a set containing resource sets for interference measurement, each resource set may include at least one interference measurement resource (CSI interference measurement, CSI-IM). For example, if the resource set includes CSI-RS, the base station and the terminal may exchange signaling information such as [Table 5] to transmit information about the resource set.

[0119] -- ASN1START-- TAG-NZP-CSI-RS-RESOURCESET-STARTNZP-CSI-RS-ResourceSet ::= SEQUENCE {nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId,nzp-CSI-RS-Resources SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceId,repetition ENUMERATED { on, off} OPTIONAL, -- Need SaperiodicTriggeringOffset INTEGER(0..6) OPTIONAL, -- Need Strs-Info ENUMERATED {true} OPTIONAL, -- Need R...}-- TAG-NZP-CSI-RS-RESOURCESET-STOP-- ASN1STOP

[0120] In [Table 5], the signaling information NZP-CSI-RS-ResourceSet contains information about each resource set. According to the signaling information, each resource set contains at least information regarding the resource set index (nzp-CSI-ResourceSetId) or the set of indices of the included CSI-RS (nzp-CSI-RS-Resources), and may include some information regarding the spatial domain transmission filter of the included CSI-RS resource (repetition) or whether the included CSI-RS resource is used for tracking (trs-Info). CSI-RS may be the most representative reference signal included in the resource set. The base station and the terminal may exchange signaling information such as [Table 6] to transmit information regarding the CSI-RS resource.

[0121] -- ASN1START-- TAG-NZP-CSI-RS-RESOURCE-STARTNZP-CSI-RS-Resource ::= SEQUENCE {nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId,resourceMapping CSI-RS-ResourceMapping,powerControlOffset INTEGER (-8..15),powerControlOffsetSS ENUMERATED{db-3, db0, db3, db6} OPTIONAL, -- Need RscramblingID ScramblingId,periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, -- Cond PeriodicOrSemiPersistentqcl-InfoPeriodicCSI-RS TCI-StateId OPTIONAL, -- Cond Periodic...}-- TAG-NZP-CSI-RS-RESOURCE-STOP-- ASN1STOP

[0122] In [Table 6], the signaling information NZP-CSI-RS-Resource contains information for each CSI-RS. The information included in the above signaling information NZP-CSI-RS-Resource may have the following meanings: - nzp-CSI-RS-ResourceId: CSI-RS resource index

[0123] - resourceMapping: Resource mapping information of CSI-RS resources

[0124] - powerControlOffset: Ratio between PDSCH EPRE (Energy Per RE) and CSI-RS EPRE

[0125] - powerControlOffsetSS: Ratio between SS / PBCH block EPRE and CSI-RS EPRE

[0126] - scramblingID: Scrambling index of the CSI-RS sequence

[0127] - periodicityAndOffset: Transmission period and slot offset of the CSI-RS resource

[0128] - qcl-InfoPeriodicCSI-RS: TCI-state information if the corresponding CSI-RS is a periodic CSI-RS

[0129] The resourceMapping included in the above signaling information NZP-CSI-RS-Resource represents resource mapping information of the CSI-RS resource and may include frequency resource element (RE) mapping, number of ports, symbol mapping, CDM type, frequency resource density, and frequency band mapping information. The number of ports, frequency resource density, CDM type, and time-frequency axis RE mapping that can be configured through this may have a value set in one of the rows of [Table 7] below.

[0130] [Table 7]

[0131]

[0132] [Table 7] shows the frequency resource density, CDM type, frequency axis, and time axis start position of the CSI-RS component RE pattern configurable according to the number of CSI-RS ports (X). ), represents the number of frequency axis REs (k') and the number of time axis REs (l') of the CSI-RS component RE pattern. The aforementioned CSI-RS component RE pattern may be a basic unit constituting a CSI-RS resource. Through Y=1+max(k') REs on the frequency axis and Z=1+max(l') REs on the time axis, the CSI-RS component RE pattern may be composed of YZ REs. When the number of CSI-RS ports is 1 port, the CSI-RS RE location can be specified without subcarrier restrictions within the PRB (Physical Resource Block), and the CSI-RS RE location can be specified by a 12-bit bitmap. When the number of CSI-RS ports is {2, 4, 8, 12, 16, 24, 32} ports and Y=2, CSI-RS RE locations can be assigned for every two subcarriers within the PRB and can be assigned by a 6-bit bitmap. When the number of CSI-RS ports is 4 ports and Y=4, CSI-RS RE locations can be assigned for every four subcarriers within the PRB and can be assigned by a 3-bit bitmap. Similarly, time axis RE locations can be assigned by a total of 14-bit bitmaps.

[0133] [CSI report configuration]

[0134] According to one embodiment of the present disclosure, a report setting may have a connection relationship with a resource setting by referencing at least one ID of the resource setting, and the resource setting(s) having a connection relationship with the report setting provide setting information including information about a reference signal for measuring channel information. When the resource setting(s) having a connection relationship with the report setting are used for measuring channel information, the measured channel information may be used for channel information reporting according to a reporting method set in the report setting having a connection relationship.

[0135] According to one embodiment of the present disclosure, the report setting may include setting information related to the CSI reporting method. For example, a base station and a terminal may exchange signaling information such as [Table 8] to transmit information regarding the report setting.

[0136] -- ASN1START-- TAG-CSI-REPORTCONFIG-STARTCSI-ReportConfig ::= SEQUENCE {reportConfigId CSI-ReportConfigId,carrier ServCellIndex OPTIONAL, -- Need SresourcesForChannelMeasurement CSI-ResourceConfigId,csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need Rnzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need RreportConfigType CHOICE {periodic SEQUENCE {reportSlotConfig CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUCCH SEQUENCE {reportSlotConfig CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUSCH SEQUENCE {reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320},reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),p0alpha P0-PUSCH-AlphaSetId},aperiodic SEQUENCE {reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32)}},reportQuantity CHOICE {none NULL,cri-RI-PMI-CQI NULL,cri-RI-i1 NULL,cri-RI-i1-CQI SEQUENCE {pdsch-BundleSizeForCSI ENUMERATED {n2, n4} OPTIONAL -- Need S},cri-RI-CQI NULL,cri-RSRP NULL,ssb-Index-RSRP NULL,cri-RI-LI-PMI-CQI NULL},reportFreqConfiguration SEQUENCE {cqi-FormatIndicator ENUMERATED { widebandCQI, subbandCQI} OPTIONAL, -- Need Rpmi-FormatIndicator ENUMERATED { widebandPMI, subbandPMI} OPTIONAL, -- Need Rcsi-ReportingBand CHOICE {subbands3 BIT STRING(SIZE(3)),subbands4 BIT STRING(SIZE(4)),subbands5 BIT STRING(SIZE(5)),subbands6 BIT STRING(SIZE(6)),subbands7 BIT STRING(SIZE(7)),subbands8 BIT STRING(SIZE(8)),subbands9 BIT STRING(SIZE(9)),subbands10 BIT STRING(SIZE(10)),subbands11 BIT STRING(SIZE(11)),subbands12 BIT STRING(SIZE(12)),subbands13 BIT STRING(SIZE(13)),subbands14 BIT STRING(SIZE(14)),subbands15 BIT STRING(SIZE(15)),subbands16 BIT STRING(SIZE(16)),subbands17 BIT STRING(SIZE(17)),subbands18 BIT STRING(SIZE(18)),...,subbands19-v1530 BIT STRING(SIZE(19))} OPTIONAL -- Need S} OPTIONAL, -- Need RtimeRestrictionForChannelMeasurements ENUMERATED {configured, notConfigured},timeRestrictionForInterferenceMeasurements ENUMERATED {configured, notConfigured},codebookConfig CodebookConfig OPTIONAL, -- Need Rdummy ENUMERATED {n1, n2} OPTIONAL, -- Need RgroupBasedBeamReporting CHOICE {enabled NULL,disabled SEQUENCE {nrofReportedRS ENUMERATED {n1, n2, n3, n4} OPTIONAL -- Need S}},cqi-Table ENUMERATED {table1, table2, table3, spare1} OPTIONAL, -- Need RsubbandSize ENUMERATED {value1, value2},non-PMI-PortIndication SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks OPTIONAL, -- Need R...,[[semiPersistentOnPUSCH-v1530 SEQUENCE {reportSlotConfig-v1530 ENUMERATED {sl4, sl8, sl16}} OPTIONAL -- Need R]]}.

[0137] In [Table 8], the signaling information CSI-ReportConfig contains information regarding each report setting. The information included in the above signaling information CSI-ReportConfig may have the following meanings: - reportConfigId: report setting index

[0138] - carrier: Serving cell index

[0139] - resourcesForChannelMeasurement: Resource setting index for channel measurement linked to report setting

[0140] - csi-IM-ResourcesForInterference: Resource setting index containing CSI-IM resources for interference measurement that have a connection with the report setting

[0141] - nzp-CSI-RS-ResourcesForInterference: Resource setting index containing CSI-RS resources for interference measurement that have a relationship with the report setting

[0142] - reportConfigType: Indicates the time-axis transmission settings and transmission channel of the channel report, and can have aperioditic transmission, semi-persistent PUCCH (Physical Uplink Control Channel) transmission, semi-persistent PUSCH transmission, or periodic transmission settings.

[0143] - reportQuantity: Indicates the type of channel information being reported, and may have the type of channel information when no channel report is transmitted ('none') or when channel report is transmitted ('cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RI-LI-PMI-CQI'). Here, the elements included in the type of channel information refer to CQI (Channel Quality Indicator), PMI (Precoding Matric Indicator), CRI (CSI-RS Resource Indicator), SSBRI (SS / PBCH block Resource Indicator), Layer Indicator (LI), Rank Indicator (RI), and / or L1-RSRP (Reference Signal Received Power).

[0144] - reportFreqConfiguration: Indicates whether the reported channel information includes only wideband information or information for each subband; if information for each subband is included, it can have configuration information for the subband containing the channel information.

[0145] - timeRestrictionForChannelMeasurements: Whether there are time axis constraints on the reference signal for channel measurement among the reference signals referenced by the reported channel information.

[0146] - timeRestrictionForInterferenceMeasurements: Whether there are time axis constraints on the reference signal for interference measurement among the reference signals referenced by the reporting channel information.

[0147] - codebookConfig: Codebook information referenced by the reporting channel information

[0148] - groupBasedBeamReporting: Whether to group beams in channel reporting

[0149] - cqi-Table: CQI table index referenced by the reporting channel information

[0150] - subbandSize: An index indicating the subband size of the channel information

[0151] - non-PMI-PortIndication: Port mapping information referenced when reporting non-PMI channel information

[0152] When a base station instructs a channel information report through upper layer signaling or L1 signaling, the terminal can perform the channel information report by referring to the above-mentioned setting information included in the instructed report setting.

[0153] The base station may instruct the terminal to report channel state information through upper layer signaling, including RRC signaling or MAC (Medium Access Control) CE (Control Element) signaling, or L1 signaling (e.g., common DCI, group-common DCI, terminal-specific DCI).

[0154] For example, a base station may instruct a terminal to report aperiodic channel information (CSI report) via upper layer signaling or DCI using DCI format 0_1. The base station sets parameters for the terminal's aperiodic CSI report, or a plurality of CSI report trigger states, which include parameters for the CSI report, via upper layer signaling. The parameters for the CSI report or the CSI report trigger states may include a slot interval or a set of possible slot intervals between a PDCCH containing DCI and a PUSCH containing the CSI report, a reference signal ID for measuring channel state, and the type of channel information included. When the base station instructs some of the plurality of CSI report trigger states to the terminal via DCI, the terminal reports channel information according to the CSI report settings of the report settings configured in the instructed CSI report trigger states. The channel information reporting may be performed via a PUSCH scheduled in DCI format 0_1. The time-domain resource allocation of a PUSCH containing a terminal's CSI report can be achieved through the slot interval with the PDCCH indicated via the DCI, and the indication of the starting symbol and symbol length within the slot for the time-domain resource allocation of the PUSCH. For example, the location of the slot in which the PUSCH containing the terminal's CSI report is transmitted can be indicated via the slot interval with the PDCCH indicated via the DCI, and the starting symbol and symbol length within the slot can be indicated via the time domain resource assignment field of the aforementioned DCI.

[0155] For example, a base station may instruct a terminal to send a semi-persistent CSI report via a DCI using DCI format 0_1. The base station may activate or deactivate the semi-persistent CSI report sent via a DCI scrambled with SP-CSI-RNTI. When the semi-persistent CSI report is activated, the terminal may periodically report channel information according to a set slot interval. When the semi-persistent CSI report is deactivated, the terminal may stop the periodic channel information reporting that was activated. The base station establishes a number of CSI report trigger states containing parameters for the terminal's semi-persistent CSI report or parameters for the semi-persistent CSI report through upper layer signaling. Parameters for a CSI report, or CSI report trigger states, may include a set of possible slot intervals or slot intervals between a PDCCH containing a DCI directing a CSI report and a PUSCH containing a CSI report, a slot interval between a slot where an upper-layer signaling directing a CSI report is activated and a PUSCH containing a CSI report, a slot interval period of the CSI report, and the type of channel information included. When a base station activates some of a plurality of CSI report trigger states or some of a plurality of report settings to a terminal via upper-layer signaling or DCI, the terminal may report channel information according to the report setting included in the directed CSI report trigger state or the CSI report setting configured in the activated report setting.The above channel information reporting can be performed through a PUSCH that is semi-continuously scheduled in DCI format 0_1 ​​scrambled with SP-CSI-RNTI. Time-axis resource allocation for a PUSCH containing a terminal's CSI report can be achieved through the slot interval period of the CSI report, the slot interval with the slot where upper-layer signaling is activated, the slot interval with the PDCCH indicated via DCI, and the indication of the start symbol and symbol length within the slot for time-axis resource allocation of the PUSCH. For example, the location of the slot in which the PUSCH containing the terminal's CSI report is transmitted can be indicated through the slot interval with the PDCCH indicated via DCI, and the start symbol and symbol length within the slot can be indicated through the time domain resource assignment field of the aforementioned DCI format 0_1.

[0156] For example, a base station may instruct a terminal to transmit a semi-persistent CSI report via PUCCH through upper-layer signaling such as MAC-CE. Through the MAC-CE signaling, the base station may activate or deactivate the semi-persistent CSI report transmitted via PUCCH. When the semi-persistent CSI report is activated, the terminal may periodically report channel information according to a set slot interval. When the semi-persistent CSI report is deactivated, the terminal may stop the periodic channel information reporting that was activated. The base station sets parameters for the terminal's semi-persistent CSI report through upper-layer signaling. The parameters for the CSI report may include the PUCCH resource to which the CSI report is transmitted, the slot interval period of the CSI report, and the type of channel information included. The terminal may transmit the CSI report via PUCCH. Alternatively, if the PUCCH for the CSI report overlaps with the PUSCH, the CSI report can be transmitted to the PUSCH. The location of the PUCCH transmission slot containing the CSI report is indicated by the slot interval period of the CSI report set through upper layer signaling, and the slot interval between the slot where the upper layer signaling is activated and the PUCCH containing the CSI report. The starting symbol and symbol length within the slot can be indicated by the starting symbol and symbol length assigned to the PUCCH resource set through upper layer signaling.

[0157] For example, a base station may instruct a terminal to issue a periodic CSI report via upper layer signaling. The base station may enable or disable the periodic CSI report via upper layer signaling, including RRC signaling. When the periodic CSI report is enabled, the terminal may periodically report channel information according to a set slot interval. When the periodic CSI report is disabled, the terminal may stop the periodic channel information reporting that was enabled. The base station establishes a report setting via upper layer signaling that includes parameters for the terminal's periodic CSI report. The parameters for the CSI report may include the PUCCH resource setting for the CSI report, the slot interval between the slot where the upper layer signaling instructing the CSI report is enabled and the PUCCH containing the CSI report, the slot interval period of the CSI report, a reference signal ID for measuring channel state, and the type of channel information included. The terminal may transmit the CSI report via the PUCCH. Alternatively, if the PUCCH for the CSI report overlaps with the PUSCH, the CSI report can be transmitted via the PUSCH. The slot location where the PUCCH containing the CSI report is transmitted is indicated by the slot interval period of the CSI report set through upper layer signaling, and the slot interval between the slot where the upper layer signaling is activated and the PUCCH containing the CSI report. The starting symbol and symbol length within the slot can be indicated by the starting symbol and symbol length assigned to the PUCCH resource set through upper layer signaling.

[0158] Regarding the aforementioned CSI report settings (CSI-ReportConfig), each report setting CSI-ReportConfig can be associated with a single downlink (DL) bandwidth portion identified by the upper-layer parameter bandwidth portion identifier (bwp-id) given by the CSI-ResourceConfig, which is associated with the corresponding report setting. As for the time domain reporting operation for each report setting CSI-ReportConfig, 'Aperiodic', 'Semi-Persistent', and 'Periodic' methods are supported, and these can be configured from the base station to the terminal by the reportConfigType parameter set from the upper layer. The semi-persistent CSI reporting methods support 'PUCCH-based semi-persistent (semi-PersistentOnPUCCH)' and 'PUSCH-based semi-persistent (semi-PersistentOnPUSCH)'. In the case of a periodic or semi-permanent CSI reporting method, the terminal may receive a PUCCH or PUSCH resource to transmit the CSI from the base station via upper layer signaling. The period and slot offset of the PUCCH or PUSCH resource to transmit the CSI may be given as the numerology of the uplink (UL) bandwidth portion configured for transmitting the CSI report. In the case of a non-periodic CSI reporting method, the terminal may receive a PUSCH resource to transmit the CSI scheduled from the base station via L1 signaling (the aforementioned DCI format 0_1).

[0159] For the aforementioned CSI resource setting (CSI-ResourceConfig), each CSI resource setting CSI-ReportConfig may include S (≥0) CSI resource sets (given by the upper-level parameter csi-RS-ResourceSetList). The CSI resource set list may consist of non-zero power (NZP) CSI-RS resource sets and SS / PBCH block sets, or may consist of CSI-interference measurement (CSI-IM) resource sets. Each CSI resource setting may be located in a downlink (DL) bandwidth portion identified by the upper-level parameter bwp-id, and the CSI resource setting may be linked to a CSI report setting in the same downlink bandwidth portion. The time domain operation of the CSI-RS resources within the CSI resource setting may be set to one of 'non-periodic', 'periodic', or 'semi-permanent' by the upper-level parameter resourceType. For periodic or semi-permanent CSI resource settings, the number of CSI-RS resource sets may be limited to S=1, and the set period and slot offset may be given by the numerology of the downlink bandwidth portion identified by bwp-id. The terminal may receive one or more CSI resource settings for channel or interference measurement from the base station via upper layer signaling, and may include, for example, the following CSI resources.

[0160] - CSI-IM resources for interference measurement

[0161] - NZP CSI-RS resources for interference measurement

[0162] - NZP CSI-RS resources for channel measurement

[0163] For CSI-RS resource sets associated with a resource setting where the upper-level parameter resourceType is set to 'Aperiodic', 'Periodic', or 'Semi-permanent', the Trigger State for a CSI reporting setting where reportType is set to 'Aperiodic' and the resource setting for channel or interference measurements for one or more component cells (CC) can be set as the upper-level parameter CSI-AperiodicTriggerStateList.

[0164] Non-periodic CSI reporting by the terminal can be performed using PUSCH, periodic CSI reporting can be performed using PUCCH, and semi-permanent CSI reporting can be performed using PUSCH when triggered or activated by DCI, and using PUCCH after activation by the MAC control element (MAC CE). As previously mentioned, CSI resource settings can also be configured as non-periodic, periodic, or semi-permanent. Combinations between CSI reporting settings and CSI resource settings can be supported based on [Table 9] below. Table 9 shows the Triggering / Activation of CSI Reporting for the possible CSI-RS Configurations.

[0165] CSI-RS ConfigurationPeriodic CSI ReportingSemi-Persistent CSI ReportingAperiodic CSI ReportingPeriodic CSI-RSNo dynamic triggering / activationFor reporting on PUCCH, the UE receives an activation command [10, TS 38.321]; for reporting on PUSCH, the UE receives triggering on DCITriggered by DCI; additionally, activation command [10, TS 38.321] possible as defined in Subclause 5.2.1.5.1.Semi-Persistent CSI-RSNot SupportedFor reporting on PUCCH, the UE receives an activation command [10, TS 38.321]; for reporting on PUSCH, the UE receives triggering on DCITriggered by DCI; additionally, activation command [10, TS 38.321] possible as defined in Subclause 5.2.1.5.1.Aperiodic CSI-RSNot SupportedNot SupportedTriggered by DCI; additionally, activation command [10, TS 38.321] possible as defined in Subclause 5.2.1.5.1.

[0166] Non-periodic CSI reporting can be triggered by the "CSI request" field of the aforementioned DCI format 0_1, which corresponds to the scheduling DCI for PUSCH. The terminal can monitor PDCCH, obtain DCI format 0_1, and obtain scheduling information and CSI request indicators for PUSCH. The CSI request indicator is N Ts It can be set to bits (=0, 1, 2, 3, 4, 5, or 6) and can be determined by the upper layer signaling (reportTriggerSize). One of the trigger states among one or more non-periodic CSI report trigger states that can be set by the upper layer signaling (CSI-AperiodicTriggerStateList) may be triggered by the CSI request indicator. - If all bits of the CSI request field are 0, this may mean that no CSI report is requested.

[0167] - If the number of CSI trigger states (M) within the configured CSI-AperiodicTriggerStateLite is 2N Ts If it is greater than -1, according to the selected mapping relationship, the M CSI trigger states are 2N Ts It can be mapped to -1, and 2N Ts One of the trigger states of -1 can be indicated by the CSI request field.

[0168] - If the number of CSI trigger states (M) in the configured CSI-AperiodicTriggerStateLite is less than or equal to 2NTs-1, one of the M CSI trigger states may be indicated as a CSI request field.

[0169] The following [Table 10] shows an example of the relationship between CSI request indicators and CSI trigger states that can be indicated by those indicators.

[0170] CSI request fieldCSI trigger stateCSI-ReportConfigIdCSI-ResourceConfigId00no CSI requestN / AN / A01CSI trigger state#1CSI report#1CSI resource#1,CSI report#2CSI resource#210CSI trigger state#2CSI report#3CSI resource#311CSI trigger state#3CSI report#4CSI resource#4

[0171] For a CSI resource within a CSI trigger state triggered by a CSI request field, the terminal can perform a measurement and generate a CSI therefrom (including at least one of the aforementioned CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP, etc.). The terminal can transmit the acquired CSI using a PUSCH scheduled by the corresponding DCI format 0_1. When the 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "1", the uplink data (UL-SCH) and the acquired CSI can be multiplexed and transmitted to the PUSCH resource scheduled by DCI format 0_1. If the 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "0", CSI can be mapped and transmitted without uplink data (UL-SCH) to the PUSCH resource scheduled by DCI format 0_1.

[0172] Figure 6 is a diagram illustrating an example of a non-periodic CSI reporting method.

[0173] In the example (600) of FIG. 6, the terminal can monitor the PDCCH (601) to obtain the DCI format 0_1, from which it can obtain scheduling information and CSI request information for the PUSCH (605). The terminal can obtain resource information for the CSI-RS (602) to be measured from the received CSI request indicator. The terminal can determine at what point in time to perform a measurement on the CSI-RS (602) resource being transmitted based on the time when it receives the DCI format 0_1 ​​and the parameter for the offset within the CSI resource set setting (e.g., the aperiodicTriggeringOffset mentioned above) within the NZP CSI-RS resource set setting (NZP-CSI-RS-ResourceSet). More specifically, the terminal may receive the offset value X of the parameter aperiodicTriggeringOffset within the NZP-CSI-RS resource set setting as an upper layer signaling from the base station, and the set offset value X may represent the offset between the slot in which the DCI triggering the non-periodic CSI report is received and the slot in which the CSI-RS resource is transmitted. For example, the aperiodicTriggeringOffset parameter value and the offset value X may have a mapping relationship as described in [Table 11] below.

[0174] aperiodicTriggeringOffsetOffset X00 slot11 slot22 slots33 slots44 slots516 slots624 slots

[0175] In an example (600) of FIG. 6, an example is shown in which the aforementioned offset value is set to X=0. In this case, the terminal can receive CSI-RS (602) in a slot (corresponding to slot 0 (606) in FIG. 6) that receives DCI format 0_1 ​​that triggers a non-periodic CSI report, and can report the CSI information measured by the received CSI-RS to the base station via PUSCH (605). The terminal can obtain scheduling information for PUSCH (605) for CSI reporting (information corresponding to each field of the aforementioned DCI format 0_1) from DCI format 0_1. For example, the terminal can obtain information about the slot to transmit PUSCH (605) from the aforementioned time domain resource allocation information for PUSCH (605) in DCI format 0_1. In the example (600) of FIG. 6, the terminal obtains a K2 (604) value corresponding to the slot offset value for PDCCH-to-PUSCH as 3, and accordingly, PUSCH (605) can be transmitted from slot 3 (609), which is 3 slots away from slot 0 (606), at the time when PDCCH (601) is received. In the example (610) of FIG. 6, the terminal can monitor PDCCH (611) in slot 0 (616) to obtain DCI format 0_1, and from this, can obtain scheduling information and CSI request information for PUSCH (615). The terminal can obtain resource information for CSI-RS (612) to be measured from the received CSI request indicator. The example (610) of FIG. 6 shows an example in which the offset (613) value for the aforementioned CSI-RS is set to X=1. In this case, the terminal can receive CSI-RS (612) in slot 1 (617). In the example (610) of FIG. 6, the terminal obtains a K2 (614) value corresponding to the slot offset value for PDCCH-to-PUSCH as 3, and can report the CSI information measured by the received CSI-RS to the base station via PUSCH (615) in slot 3 (619).

[0176] Aperiodic CSI reports may include at least one or both of CSI part 1 or CSI part 2, and when the aperiodic CSI reports are transmitted via PUSCH, they may be multiplexed with the transport block. For multiplexing, a CRC is inserted into the input bits of the aperiodic CSI, and after undergoing encoding and rate matching, it may be mapped to a specific pattern in a resource element within PUSCH and transmitted. The above CRC insertion may be omitted depending on the coding method or the length of the input bits. The number of modulation symbols calculated for rate matching during the multiplexing of CSI Part 1 or CSI part 2 included in the aperiodic CSI reports can be calculated as shown in [Table 12] below.

[0177] [Table 12]

[0178]

[0179]

[0180] In particular, for PUSCH repetition transmission methods A and B, the terminal can transmit aperiodic CSI reports by multiplexing them only during the first repetition of the PUSCH repetition. This is because the aperiodic CSI report information being multiplexed is encoded in a polar code format, and for it to be multiplexed across multiple PUSCH repetitions, each PUSCH repetition must have the same frequency and time resource allocation. Specifically, in the case of PUSCH repetition type B, since each actual repetition can have a different OFDM symbol length, the aperiodic CSI reports can be multiplexed and transmitted only during the first PUSCH repetition.

[0181] Additionally, regarding PUSCH repetitive transmission method B, if the terminal receives a DCI that schedules a non-periodic CSI report or enables semi-permanent CSI report without scheduling for the transport block, the value of the nominal repetition may be assumed to be 1 even if the number of PUSCH repetitive transmissions set by the upper layer signaling is greater than 1. Additionally, if the terminal schedules or enables a non-periodic or semi-permanent CSI report without scheduling for the transport block based on PUSCH repetitive transmission method B, the terminal may expect the first nominal repetition to be the same as the first actual repetition. For a PUSCH transmitted including the semi-permanent CSI based on PUSCH repetitive transmission method B without scheduling for the DCI after semi-permanent CSI report is enabled by the DCI, if the first nominal repetition is different from the first actual repetition, the transmission for the first nominal repetition may be ignored.

[0182] [PDCCH: DCI related]

[0183] Next, we will explain downlink control information (DCI) in 5G systems in detail.

[0184] In a 5G system, scheduling information for uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) is transmitted from the base station to the terminal via DCI. The terminal can monitor the fallback DCI format and the non-fallback DCI format for PUSCH or PDSCH. The fallback DCI format may consist of fixed fields selected between the base station and the terminal, and the non-fallback DCI format may include configurable fields.

[0185] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after undergoing channel coding and modulation processes. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled into a Radio Network Temporary Identifier (RNTI) corresponding to the terminal's identity. Different RNTIs may be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control commands, or random access responses. In other words, the RNTI is not transmitted explicitly but is included in the CRC calculation process. Upon receiving a DCI message transmitted over the PDCCH, the terminal checks the CRC using the assigned RNTI; if the CRC check result is correct, the terminal knows that the message has been transmitted to it.

[0186] For example, a DCI scheduling a PDSCH for System Information (SI) can be scrambled to SI-RNTI. A DCI scheduling a PDSCH for Random Access Response (RAR) messages can be scrambled to RA-RNTI. A DCI scheduling a PDSCH for Paging messages can be scrambled to P-RNTI. A DCI notifying a Slot Format Indicator (SFI) can be scrambled to SFI-RNTI. A DCI notifying Transmit Power Control (TPC) can be scrambled to TPC-RNTI. A DCI scheduling a terminal-specific PDSCH or PUSCH can be scrambled to C-RNTI (Cell RNTI).

[0187] DCI format 0_0 can be used as a countermeasure DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI may include, for example, the information in [Table 13] below.

[0188] - Identifier for DCI formats - [1] bit- Frequency domain resource assignment -[ ] bits- Time domain resource assignment - X bits- Frequency hopping flag - 1 bit- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- TPC command for scheduled PUSCH - [2] bits- UL / SUL indicator - 0 or 1 bit

[0189] DCI format 0_1 ​​can be used as a non-defense DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI may include, for example, the information in [Table 14] below.

[0190] - Carrier indicator - 0 or 3 bits - UL / SUL indicator - 0 or 1 bit - Identifier for DCI formats - [1] bits - Bandwidth part indicator - 0, 1 or 2 bits - Frequency domain resource assignment - For resource allocation type 0, bits- For resource allocation type 1, bits- Time domain resource assignment -1, 2, 3, or 4 bits- VRB-to-PRB mapping (virtual resource block-to-physical resource block mapping) - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- Frequency hopping flag - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- 1st downlink assignment index (first downlink allocation index)- 1 or 2 bits○ 1 bit for semi-static HARQ-ACK codebook (semi-static HARQ-ACK In case of codebook);○ 2 bits for dynamic HARQ-ACK codebook with single HARQ-ACK codebook (when a dynamic HARQ-ACK codebook is used with a single HARQ-ACK codebook).- 2nd downlink assignment index - 0 or 2 bits ○ 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks (when a dynamic HARQ-ACK codebook is used with two HARQ-ACK sub-codebooks); ○ 0 bit otherwise.TPC command for scheduled PUSCH - 2 bits- SRS resource indicator (SRS resource indicator) -. or bits○ bits for non-codebook based PUSCH transmission(if PUSCH transmission is not codebook-based);○ bits for codebook-based PUSCH transmission. - Precoding information and number of layers - up to 6 bits - Antenna ports - up to 5 bits - SRS request - 2 bits - CSI request - 0, 1, 2, 3, 4, 5, or 6 bits - CBG transmission information - 0, 2, 4, 6, or 8 bits - PTRS-DMRS association - 0 or 2 bits - beta_offset indicator - 0 or 2 bits - DMRS sequence initialization - 0 or 1 bit

[0191] DCI format 1_0 can be used as a countermeasure DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI may include, for example, the information in [Table 15] below.

[0192] - Identifier for DCI formats - [1] bit- Frequency domain resource assignment -[ ] bits- Time domain resource assignment - X bits- VRB-to-PRB mapping - 1 bit- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- Downlink assignment index - 2 bits- TPC command for scheduled PUCCH - [2] bits- PUCCH resource indicator - 3 bits- PDSCH-to-HARQ feedback timing indicator - [3] bits

[0193] DCI format 1_1 can be used as a non-defense DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI may include, for example, the information in [Table 16] below.

[0194] - Carrier indicator - 0 or 3 bits- Identifier for DCI formats - [1] bits- Bandwidth part indicator - 0, 1 or 2 bits- Frequency domain resource assignment○ For resource allocation type 0, bits○ For resource allocation type 1, bits- Time domain resource assignment -1, 2, 3, or 4 bits- VRB-to-PRB mapping - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- PRB bundling size indicator - 0 or 1 bit - Rate matching indicator - 0, 1, or 2 bits - ZP CSI-RS trigger - 0, 1, or 2 bits - For transport block 1: - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits - For transport block 2: - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits - HARQ process number - 4 bits - Downlink assignment index - 0 or 2 or 4 bits - TPC command for scheduled PUCCH - 2 bits - PUCCH resource indicator - 3 bits - PDSCH-to-HARQ_feedback timing indicator - 3 bits - Antenna ports 4, 5, or 6 bits - Transmission configuration indication - 0 or 3 bits - SRS request - 2 bits - CBG transmission information - 0, 2, 4, 6, or 8 bits - CBG flushing out information - 0 or 1 bit - DMRS sequence initialization - 1 bit.

[0195] [PDCCH: CORESET, REG, CCE, Search Space]

[0196] In the following, the downlink control channel in a 5G communication system will be explained in more detail with reference to the drawings.

[0197] FIG. 7 illustrates an example of a control resource set (CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 7 illustrates an example in which two control resources (control resource #1 (701), control resource #2 (702)) are set within a terminal bandwidth part (UE bandwidth part) (710) on the frequency axis and one slot (720) on the time axis. The control resources (701, 702) can be set in a specific frequency resource (703) within the entire terminal bandwidth part (710) on the frequency axis. On the time axis, they can be set with one or more OFDM symbols and can be defined as the control resource set duration (Control Resource Set Duration, 704). Referring to the example illustrated in FIG. 7, control resource #1 (701) is set with a control resource length of 2 symbols, and control resource #2 (702) is set with a control resource length of 1 symbol.

[0198] The control domain in the aforementioned 5G can be configured by the base station to the terminal through upper-layer signaling (e.g., System Information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Configuring the control domain to the terminal means providing information such as the control domain identifier (Identity), the frequency location of the control domain, and the symbol length of the control domain. For example, it may include the information in [Table 17] below.

[0199] ControlResourceSet ::= SEQUENCE {-- Corresponds to L1 parameter 'CORESET-ID'controlResourceSetId ControlResourceSetId,frequencyDomainResources BIT STRING (SIZE (45)),duration INTEGER (1..maxCoReSetDuration),cce-REG-MappingType CHOICE {interleaved SEQUENCE {reg-BundleSize ENUMERATED {n2, n3, n6},precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs},interleaverSize ENUMERATED {n2, n3, n6}shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL},nonInterleaved NULL},tci-StatesPDCCH SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL,tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, -- Need S}

[0200] In [Table 17], the tci-StatesPDCCH (simply named TCI (transmission configuration indication) state) configuration information may include information on one or more SS (synchronization signal) / PBCH (physical broadcast channel) block indices or CSI-RS (channel state information reference signal) indices that are in a quasi-co-located relationship with the DMRS transmitted in the corresponding control area. FIG. 8 is a diagram showing an example of the basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G. According to FIG. 8, the basic unit of time and frequency resources that constitute a control channel can be called a REG (resource element group, 803), and the REG (803) can be defined as 1 OFDM symbol (801) on the time axis and 1 PRB (physical resource block, 802) on the frequency axis, that is, 12 subcarriers. The base station can connect REG (803) to form a downlink control channel allocation unit.

[0201] As illustrated in FIG. 8, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (control channel element, 804), then 1 CCE (804) can be composed of multiple REGs (803). For example, if the REG (803) illustrated in FIG. 8 is described, the REG (803) can be composed of 12 REs, and if 1 CCE (804) is composed of 6 REGs (803), then 1 CCE (804) can be composed of 72 REs. When a downlink control area is established, the area can be composed of multiple CCEs (804), and a specific downlink control channel can be mapped to one or multiple CCEs (804) and transmitted according to the aggregation level (AL) within the control area. The CCEs (804) within the control area are distinguished by numbers, and the numbers of the CCEs (804) can be assigned according to a logical mapping method.

[0202] The basic unit of the downlink control channel, namely the REG (803) illustrated in FIG. 8, may include both the REs to which the DCI is mapped and the DMRS (805), which is a reference signal for decoding, to which the area is mapped. As shown in FIG. 8, three DMRS (805) may be transmitted within one REG (803). The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 depending on the aggregation level, and different numbers of CCEs may be used to implement link adaptation of the downlink control channel. For example, when AL=L, one downlink control channel may be transmitted through L CCEs. The terminal must detect the signal without knowing information about the downlink control channel, and a search space representing a set of CCEs is defined for blind decoding. A search space is a set of downlink control channel candidates consisting of CCEs that a terminal must attempt to decode on a given aggregation level, and since there are various aggregation levels that form a group of 1, 2, 4, 8, or 16 CCEs, a terminal may have multiple search spaces. A search space set can be defined as a set of search spaces on all configured aggregation levels.

[0203] Search spaces can be classified into common search spaces and UE-specific search spaces. A certain group of terminals or all terminals may examine the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling or paging messages regarding system information. For example, PDSCH scheduling allocation information for the transmission of SIBs containing cell operator information can be received by examining the common search space of the PDCCH. In the case of the common search space, since a certain group of terminals or all terminals must receive the PDCCH, it can be defined as a set of pre-agreed CCEs. Scheduling allocation information for a UE-specific PDSCH or PUSCH can be received by examining the UE-specific search space of the PDCCH. The UE-specific search space can be defined specifically as a function of the terminal's identity and various system parameters.

[0204] In 5G, parameters for the search space for a PDCCH can be configured from the base station to the terminal via upper-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station may configure the terminal the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the occasion for monitoring in slot-symbol units for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the search space, and the control area index to be monitored in the search space. For example, the information in [Table 18] below may be included.

[0205] SearchSpace ::= SEQUENCE {-- Identity of the search space. SearchSpaceId = 0 identifies the SearchSpace configured via PBCH (MIB) or ServingCellConfigCommon.searchSpaceId SearchSpaceId,controlResourceSetId ControlResourceSetId,monitoringSlotPeriodicityAndOffset CHOICE {sl1 NULL,sl2 INTEGER (0..1),sl4 INTEGER (0..3),sl5 INTEGER (0..4),sl8 INTEGER (0..7),sl10 INTEGER (0..9),sl16 INTEGER (0..15),sl20 INTEGER (0..19)} OPTIONAL,duration INTEGER (2..2559)monitoringSymbolsWithinSlot BIT STRING (SIZE (14)) OPTIONAL,nrofCandidates SEQUENCE {aggregationLevel1 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel2 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel4 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel8 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel16 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}},searchSpaceType CHOICE {-- Configures this search space as common search space (CSS) and DCI formats to monitor.common SEQUENCE {}ue-Specific SEQUENCE {-- Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1.formats ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1},...}.

[0206] According to the configuration information, the base station may configure one or more sets of search spaces for the terminal. According to some embodiments, the base station may configure search space set 1 and search space set 2 for the terminal, configure DCI format A scrambled with X-RNTI in search space set 1 to be monitored in the common search space, and configure DCI format B scrambled with Y-RNTI in search space set 2 to be monitored in the terminal-specific search space. According to the configuration information, one or more sets of search spaces may exist in the common search space or the terminal-specific search space. For example, search space set #1 and search space set #2 may be configured as the common search space, and search space set #3 and search space set #4 may be configured as the terminal-specific search space.

[0207] In the common search space, the following combinations of DCI formats and RNTI can be monitored. Of course, they are not limited to the examples below.

[0208] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI

[0209] - DCI format 2_0 with CRC scrambled by SFI-RNTI

[0210] - DCI format 2_1 with CRC scrambled by INT-RNTI

[0211] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI

[0212] - DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI

[0213] In terminal-specific search spaces, the following combinations of DCI formats and RNTI can be monitored. Of course, they are not limited to the examples below.

[0214] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

[0215] - DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

[0216] The specified RNTIs may follow the definitions and uses below.

[0217] C-RNTI (Cell RNTI): Used for terminal-specific PDSCH scheduling

[0218] TC-RNTI (Temporary Cell RNTI): Used for terminal-specific PDSCH scheduling

[0219] CS-RNTI (Configured Scheduling RNTI): Used for semi-statically configured terminal-specific PDSCH scheduling.

[0220] RA-RNTI (Random Access RNTI): Used for PDSCH scheduling during the random access phase

[0221] P-RNTI (Paging RNTI): Used for PDSCH scheduling where paging is transmitted.

[0222] SI-RNTI (System Information RNTI): Used for PDSCH scheduling where system information is transmitted.

[0223] INT-RNTI (Interruption RNTI): Used to indicate whether PDSCH has been punctured.

[0224] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to instruct power control commands to the PUSCH

[0225] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to instruct power control commands to the PUCCH

[0226] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to instruct power control commands for the SRS (sounding reference signal).

[0227] The aforementioned specified DCI formats may follow the definitions in [Table 19] below.

[0228] DCI formatUsage0_0Scheduling of PUSCH in one cell0_1Scheduling of PUSCH in one cell1_0Scheduling of PDSCH in one cell1_1Scheduling of PDSCH in one cell2_0Notifying a group of UEs of the slot format2_1Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE2_2Transmission of TPC commands for PUCCH and PUSCH2_3Transmission of a group of TPC commands for SRS transmissions by one or more UEs

[0229] In a 5G system, the search space of aggregation level L in CORESET p and search space set s can be expressed as Equation 1 below.

[0230] [Mathematical Formula 1]

[0231]

[0232] - L: Lamination Level

[0233] - n CI : Carrier Index

[0234] - n CCE,p : Total number of CCEs existing in CORESET p

[0235] - : Slot Index

[0236] - : Number of PDCCH candidates at assembly level L

[0237] - = 0, ..., -1: PDCCH candidate index of aggregation level L

[0238] - l = 0, ..., L -1

[0239] - , Y p,-1 = nRNTI≠0, A p = 39827 for p mod 3 = 0, A p = 39829 for p mod 3 = 1, A p = 39839 for p mod 3 = 2, D= 65537

[0240] - n RNTI : Terminal identifier

[0241] The value may be 0 for the common search space.

[0242] In the case of a terminal-specific search space, the value may correspond to a value that changes according to the terminal's identity (C-RNTI or ID set by the base station for the terminal) and the time index.

[0243] In a 5G system, as multiple sets of search spaces can be configured with different parameters (e.g., the parameters in Table 9), the set of search space sets monitored by the terminal at each point in time may vary. For example, if search space set #1 is configured with an X-slot period and search space set #2 is configured with a Y-slot period and X and Y are different, the terminal may monitor both search space set #1 and search space set #2 in a specific slot, and monitor either search space set #1 or search space set #2 in a specific slot.

[0244] [PUCCH: Transmission Related]

[0245] In an NR system, a terminal can transmit uplink control information (UCI) to a base station via PUCCH. The control information may include at least one of the following: a HARQ-ACK indicating whether demodulation / decoding of a TB (transport block) received by the terminal via PDSCH was successful; a scheduling request (SR) in which the terminal requests resource allocation from the PUCCH base station for uplink data transmission; and channel state information (CSI), which is information for reporting the terminal's channel status. In the following, PUCCH transmission and transmission of PUCCH resources can be understood as signal transmission on the PUCCH from the PUCCH resource.

[0246] PUCCH resources can be broadly classified into long PUCCH and short PUCCH depending on the length of the allocated symbols. In an NR system, long PUCCH has a length of 4 symbols or more within a slot, while short PUCCH has a length of 2 symbols or less within a slot.

[0247] To explain Long PUCCH in more detail, Long PUCCH can be used to improve uplink cell coverage and therefore can be transmitted via a single carrier transmission method, DFT-S-OFDM, rather than OFDM transmission. Long PUCCH supports transmission formats such as PUCCH format 1, PUCCH format 3, and PUCCH format 4, depending on the number of control information bits supported and whether terminal multiplexing is supported through Pre-DFT OCC support in front of the IFFT.

[0248] First, PUCCH format 1 is a long PUCCH format based on DFT-S-OFDM that can support up to 2 bits of control information and uses 1 RB of frequency resources. The control information can be composed of a combination of HARQ-ACK and SR, or each of them. PUCCH format 1 is repeatedly composed of OFDM symbols containing a DMRS (DeModulation Reference Signal), which is a demodulation reference signal (or reference signal), and OFDM symbols containing a UCI.

[0249] For example, if the number of transmitted symbols in PUCCH format 1 is 8 symbols, the 8 symbols may be composed sequentially of DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, and UCI symbol, starting from the first starting symbol. The DMRS symbol is an orthogonal code (or orthogonal sequence or spreading code, w) on the time axis within a sequence corresponding to a length of 1 RB on the frequency axis within a single OFDM symbol. i(m) It can be spread using ) and transmitted after performing IFFT.

[0250] Next, PUCCH format 3 is a long PUCCH format based on DFT-S-OFDM capable of supporting control information exceeding 2 bits, and the number of RBs used can be configured through the upper layer. The control information can consist of a combination of HARQ-ACK, SR, and CSI, or each of them. In PUCCH format 3, the DMRS symbol position can be configured based on whether frequency hopping within the slot occurs and whether additional DMRS symbols are configured.

[0251] Next, PUCCH format 4 is a long PUCCH format based on DFT-S-OFDM capable of supporting control information exceeding 2 bits, and it utilizes 1 RB of frequency resources. The control information can consist of a combination of HARQ-ACK, SR, and CSI, or each of them individually. The difference between PUCCH format 4 and PUCCH format 3 is that PUCCH format 4 for multiple terminals can be multiplexed within a single RB. Multiplexing of PUCCH format 4 for multiple terminals is possible by applying Pre-DFT OCC (orthogonal cover code) to the control information before the IFFT layer. However, the number of control information symbols that can be transmitted by a single terminal decreases depending on the number of terminals being multiplexed. The number of multiplexable terminals, i.e., the number of different available OCCs, can be 2 or 4, and the number of OCCs and the OCC index to be applied can be configured through the upper layer.

[0252] Next, we will explain short PUCCH. Short PUCCH can be transmitted in both the downlink centric slot and the uplink centric slot, and generally, it can be transmitted at the last symbol of the slot or at the OFDM symbols at the end (e.g., the very last OFDM symbol, the second-to-last OFDM symbol, or the last two OFDM symbols). Of course, it is also possible for a short PUCCH to be transmitted at any location within the slot. Furthermore, a short PUCCH can be transmitted using one OFDM symbol or two OFDM symbols. Short PUCCH can be used to reduce latency compared to long PUCCH in situations where uplink cell coverage is good, and it can be transmitted via the CP-OFDM method.

[0253] Short PUCCH can support transmission formats such as PUCCH format 0 and PUCCH format 2 depending on the number of supported control information bits. First, PUCCH format 0 is a short PUCCH format capable of supporting up to 2 bits of control information and uses 1 RB of frequency resources. The control information can consist of a combination of HARQ-ACK and SR, or each individually. PUCCH format 0 is structured to transmit only a sequence mapped to 12 subcarriers along the frequency axis within a single OFDM symbol, without transmitting DMRS. The terminal can generate a sequence based on the group hopping or sequence hopping settings and the configured ID received as an upper signal from the base station, cyclic shift the generated sequence using the final CS value obtained by adding a different CS value depending on whether it is an ACK or a NACK to the indicated initial CS (cyclic shift) value, map it to 12 subcarriers, and transmit it.

[0254] Next, PUCCH format 2 is a short PUCCH format that supports control information exceeding 2 bits, and the number of RBs used can be set through the upper layer. The control information can consist of a combination of HARQ-ACK, SR, and CSI, or each of them. When the index of the first subcarrier is #0, PUCCH format 2 allows the position of the subcarrier where the DMRS is transmitted within a single OFDM symbol to be fixed to the subcarriers having indices #1, #4, #7, and #10. The control information can be mapped to the remaining subcarriers, excluding the subcarrier where the DMRS is located, through a modulation process following channel coding.

[0255] [PUCCH: PUCCH resource configuration]

[0256] Next, the PUCCH resource configuration of a base station or terminal is described. A base station may be able to configure PUCCH resources per BWP through an upper layer for a specific terminal. The PUCCH resource configuration may be as shown in the following [Table 20].

[0257] PUCCH-Config ::= SEQUENCE {resourceSetToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSet OPTIONAL, -- Need NresourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSetId OPTIONAL, -- Need NresourceToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-Resource OPTIONAL, -- Need NresourceToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceId OPTIONAL, -- Need Nformat1 SetupRelease { PUCCH-FormatConfig} OPTIONAL, -- Need Mformat2 SetupRelease { PUCCH-FormatConfig} OPTIONAL, -- Need Mformat3 SetupRelease { PUCCH-FormatConfig} OPTIONAL, -- Need Mformat4 SetupRelease { PUCCH-FormatConfig} OPTIONAL, -- Need MschedulingRequestResourceToAddModList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfig OPTIONAL, -- Need NschedulingRequestResourceToReleaseList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceId OPTIONAL, -- Need Nmulti-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId OPTIONAL, -- Need Mdl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need MspatialRelationInfoToAddModList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfo OPTIONAL, -- Need NspatialRelationInfoToReleaseList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoId OPTIONAL, -- Need Npucch-PowerControl PUCCH-PowerControl OPTIONAL, -- Need M...,[[resourceToAddModListExt-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-r16 OPTIONAL, -- Need Ndl-DataToUL-ACK-r16 SetupRelease { DL-DataToUL-ACK-r16} OPTIONAL, -- Need Mul-AccessConfigListDCI-1-1-r16 SetupRelease { UL-AccessConfigListDCI-1-1-r16} OPTIONAL, -- Need MsubslotLengthForPUCCH-r16 CHOICE {normalCP-r16 ENUMERATED {n2,n7},extendedCP-r16 ENUMERATED {n2,n6}} OPTIONAL, -- Need Rdl-DataToUL-ACK-DCI-1-2-r16 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r16} OPTIONAL, -- Need MnumberOfBitsForPUCCH-ResourceIndicatorDCI-1-2-r16 INTEGER (0..3) OPTIONAL, -- Need Rdmrs-UplinkTransformPrecodingPUCCH-r16 ENUMERATED {enabled} OPTIONAL, -- Cond PI2-BPSKspatialRelationInfoToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfo OPTIONAL, -- Need NspatialRelationInfoToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfoId OPTIONAL, -- Need NspatialRelationInfoToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoExt-r16 OPTIONAL, -- Need NspatialRelationInfoToReleaseListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoId-r16 OPTIONAL, -- Need NresourceGroupToAddModList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroup-r16 OPTIONAL, -- Need NresourceGroupToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroupId-r16 OPTIONAL, -- Need Nsps-PUCCH-AN-List-r16 SetupRelease { SPS-PUCCH-AN-List-r16} OPTIONAL, -- Need MschedulingRequestResourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1610 OPTIONAL -- Need N]]}.

[0258] According to [Table 20], one or more PUCCH resource sets may be configured within the PUCCH resource settings for a specific BWP, and some of the PUCCH resource sets may have a maximum payload value for UCI transmission. Each PUCCH resource set may contain one or more PUCCH resources, and each PUCCH resource may belong to one of the aforementioned PUCCH formats. The upper layer configuration for the PUCCH resource sets may be as shown in the following [Table 21].

[0259] PUCCH-ResourceSet ::= SEQUENCE {pucch-ResourceSetId PUCCH-ResourceSetId,resourceList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerSet)) OF PUCCH-ResourceId,maxPayloadSize INTEGER (4..256) OPTIONAL -- Need R}

[0260] The resourceList parameter in [Table 21] may include the IDs of PUCCH resources belonging to the PUCCH resource set. If, during initial connection or if no PUCCH resource set is configured, a predefined PUCCH resource set consisting of multiple cell-specific PUCCH resources may be used in the initial BWP. Within this PUCCH resource set, the PUCCH resource to be used for the initial connection may be specified via SIB1.

[0261] The maximum payload of each PUCCH resource included in the PUCCH resource set can be 2 bits for PUCCH format 0 or 1, and for other formats, it can be determined by the symbol length, the number of PRBs, and the maximum code rate. The symbol length and the number of PRBs can be set per PUCCH resource, and the maximum code rate can be set per PUCCH format.

[0262] Next, the selection of a PUCCH resource for UCI transmission is described. For SR transmission, a PUCCH resource for the SR corresponding to the schedulingRequestID can be configured through the upper layer. The PUCCH resource can be a resource belonging to PUCCH format 0 or PUCCH format 1.

[0263] For CSI transmission, the PUCCH resource to transmit periodic or semi-persistent CSI reports via PUCCH can be set in the pucch-CSI-ResourceList parameter. The pucch-CSI-ResourceList parameter may contain a list of PUCCH resources for each BWP for the cell or CC to which the corresponding CSI report will be transmitted. The PUCCH resource may be a resource belonging to PUCCH format 2, PUCCH format 3, or PUCCH format 4. For HARQ-ACK transmission, the resource set of PUCCH resources to be transmitted may be selected first based on the payload of the UCI containing the corresponding HARQ-ACK. That is, the PUCCH resource set having a minimum payload not smaller than the UCI payload may be selected. Next, a PUCCH resource within the PUCCH resource set can be selected through the PUCCH resource indicator (PRI) within the DCI that scheduled the TB corresponding to the HARQ-ACK, and the PRI may be the PUCCH resource indicator specified in [Table 15] or [Table 16]. The relationship between the PRI and the PUCCH resource selected in the PUCCH resource set may be as shown in the following [Table 22].

[0264] PUCCH resource indicatorPUCCH resource'000'1 st PUCCH resource provided bypucch-ResourceIdobtained from the 1 st value ofresourceList'001'2 nd PUCCH resource provided bypucch-ResourceIdobtained from the 2 nd value ofresourceList'010'3rd PUCCH resource provided bypucch-ResourceIdobtained from the 3 rd value ofresourceList'011'4 th PUCCH resource provided bypucch-ResourceIdobtained from the 4 th value ofresourceList'100'5 th PUCCH resource provided bypucch-ResourceIdobtained from the 5 th value ofresourceList'101'6 th PUCCH resource provided bypucch-ResourceIdobtained from the 6 th value ofresourceList'110'7 th PUCCH resource provided bypucch-ResourceIdobtained from the 7 th value ofresourceList'111'8 th PUCCH resource provided bypucch-ResourceIdobtained from the 8 th value ofresourceList

[0265] If the number of PUCCH resources in the selected PUCCH resource set is greater than 8, a PUCCH resource can be selected by the following [Equation 2].

[0266] [Mathematical Formula 2]

[0267]

[0268] r in mathematical equation 2 PUCCH is the index of the selected PUCCH resource within the PUCCH resource set, R PUCCHis the number of PUCCH resources belonging to the PUCCH resource set, Δ PRI is the PRI value, N cce,p is the total number of CCEs of CORESET p to which the receiving DCI belongs, n cce,p represents the first CCE index for the received DCI.

[0269] The point in time when the corresponding PUCCH resource is transmitted is K1 slot after the TB transmission corresponding to the HARQ-ACK. Candidates for the K1 value are set at the upper layer, and more specifically, can be set in the dl-DataToUL-ACK parameter within the PUCCH-Config specified in [Table 20]. One of these candidates for the K1 value may be selected by the PDSCH-to-HARQ feedback timing indicator within the DCI that schedules the TB, and this value may be the value specified in [Table 15] or [Table 16]. Meanwhile, the unit of the K1 value may be a slot unit or a subslot unit. Here, a subslot is a unit of length smaller than a slot, and one or more symbols may constitute a single subslot.

[0270] [PUSCH: Regarding transmission method]

[0271] Next, the scheduling method for PUSCH transfers is described. PUSCH transfers can be dynamically scheduled by UL grants within the DCI, or operated by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transfers can be provided in DCI format 0_0 or 0_1.

[0272] Configured grant Type 1 PUSCH transmissions can be semi-statically configured by receiving configuredGrantConfig, which includes rrc-ConfiguredUplinkGrant of [Table 23], through the upper signaling, without receiving UL grants within the DCI. Configured grant Type 2 PUSCH transmissions can be semi-continuously scheduled by UL grants within the DCI after receiving configuredGrantConfig, which does not include rrc-ConfiguredUplinkGrant of [Table 23], through the upper signaling. When a PUSCH transmission is operated by a configured grant, the parameters applied to the PUSCH transmission are applied through configuredGrantConfig, the upper signaling of [Table 23], with the exception of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH, which are provided by pusch-Config, the upper signaling of [Table 24]. If the terminal is provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 23], the terminal applies tp-pi2BPSK in pusch-Config of [Table 24] to PUSCH transmissions operated by the configured grant.

[0273] ConfiguredGrantConfig ::= SEQUENCE {frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S,cg-DMRS-Configuration DMRS-UplinkConfig,mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH} OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},rbg-Size ENUMERATED {config2} OPTIONAL, -- Need SpowerControlLoopToUse ENUMERATED {n0, n1},p0-PUSCH-Alpha P0-PUSCH-AlphaSetId,transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need SnrofHARQ-Processes INTEGER(1..16),repK ENUMERATED {n1, n2, n4, n8},repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need Rperiodicity ENUMERATED {sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14,sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12,sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,sym1280x12, sym2560x12},configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need Rrrc-ConfiguredUplinkGrant SEQUENCE {timeDomainOffset INTEGER (0..5119),timeDomainAllocation INTEGER (0..15),frequencyDomainAllocation BIT STRING (SIZE(18)),antennaPort INTEGER (0..31),dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need RprecodingAndNumberOfLayers INTEGER (0..63),srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need RmcsAndTBS INTEGER (0..31),frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need RpathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),...} OPTIONAL, -- Need R...}.

[0274] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission is the same as the antenna port for SRS transmission. PUSCH transmission can follow a codebook-based transmission method and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pusch-Config within the upper signaling [Table 24] is 'codebook' or 'nonCodebook'. As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically configured by a configured grant. If a terminal is instructed to schedule PUSCH transmission via DCI format 0_0, the terminal performs beam configuration for PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the terminal-specific PUCCH resource corresponding to the minimum ID within the active uplink BWP in the serving cell, and in this case, PUSCH transmission is based on a single antenna port. In a BWP where the PUCCH resource containing pucch-spatialRelationInfo is not configured, the terminal does not expect scheduling for PUSCH transmission via DCI format 0_0. If the terminal has not configured txConfig within pusch-Config of [Table 24], the terminal does not expect scheduling via DCI format 0_1.

[0275] PUSCH-Config ::= SEQUENCE {dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need StxConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need Sdmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mdmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mpusch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need MfrequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need SfrequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1)OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList} OPTIONAL, -- Need Mpusch-AggregationFactor ENUMERATED { n2, n4, n8} OPTIONAL, -- Need Smcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need StransformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need ScodebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}OPTIONAL, -- Cond codebookBasedmaxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBasedrbg-Size ENUMERATED { config2} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need Mtp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S...}.

[0276] Next, codebook-based PUSCH transmission is described. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can operate semi-statically via a configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via a configured grant, the terminal determines the precoder for PUSCH transmission based on the SRS resource indicator (SRI), the Transmission Precoding Matrix Indicator (TPMI), and the transmission rank (number of PUSCH transmission layers). In this case, the SRI can be provided via the SRS resource indicator field within the DCI or configured via the higher-level signaling srs-ResourceIndicator. When transmitting codebook-based PUSCH, the terminal is configured with at least one SRS resource and can be configured with up to two. When a terminal receives an SRI via DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the SRI. Additionally, the TPMI and transmission rank may be provided through the fields 'precoding information' and 'number of layers' within the DCI, or configured through the higher-level signaling 'precodingAndNumberOfLayers'. The TPMI is used to indicate the precoder applied to the PUSCH transmission. If the terminal is configured with a single SRS resource, the TPMI is used to indicate the precoder to be applied to that single configured SRS resource.If the terminal is configured with multiple SRS resources, TPMI is used to specify the precoder to be applied to the SRS resource indicated by SRI.

[0277] The precoder to be used for PUSCH transmission is selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper signaling SRS-Config. In codebook-based PUSCH transmission, the terminal determines the codebook subset based on TPMI and the codebookSubset in the upper signaling pusch-Config. The codebookSubset in the upper signaling pusch-Config can be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the terminal to the base station. If the terminal reports 'partialAndNonCoherent' as the UE capability, the terminal does not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the terminal reports 'nonCoherent' as a UE capability, the terminal does not expect the value of the parent signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the parent signaling SRS-ResourceSet points to two SRS antenna ports, the terminal does not expect the value of the parent signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0278] A terminal may receive one SRS resource set in which the value of usage in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource within that SRS resource set may be indicated via SRI. If multiple SRS resources are set in the SRS resource set in which the value of usage in the upper signaling SRS-ResourceSet is set to 'codebook', the terminal expects that the value of nrofSRS-Ports in the upper signaling SRS-Resource will be set to the same value for all SRS resources.

[0279] The terminal transmits one or more SRS resources included in an SRS resource set in which the usage value is set to 'codebook' according to the upper signaling to the base station, and the base station selects one of the SRS resources transmitted by the terminal and instructs the terminal to perform PUSCH transmission using the transmit beam information of the corresponding SRS resource. In this case, in codebook-based PUSCH transmission, SRI is used as information to select the index of one SRS resource and is included in the DCI. Additionally, the base station includes information in the DCI that instructs the TPMI and rank to be used by the terminal for PUSCH transmission. The terminal performs PUSCH transmission using the SRS resource instructed by the SRI, by applying the instructed rank and the precoder instructed by the TPMI based on the transmit beam of the corresponding SRS resource.

[0280] Next, non-codebook-based PUSCH transmission is described. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can operate semi-statically via configured grant. If at least one SRS resource is configured within an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive a non-codebook-based PUSCH transmission via DCI format 0_1.

[0281] For an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive one connected NZP CSI-RS resource (non-zero power CSI-RS). The terminal can perform calculations for a precoder for SRS transmission by measuring the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission at the terminal is less than 42 symbols, the terminal does not expect the information for the precoder for SRS transmission to be updated.

[0282] If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS is indicated by the SRS request field in DCI format 0_1 ​​or 1_1. In this case, if the connected NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, the existence of the connected NZP CSI-RS is indicated if the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. In this case, the corresponding DCI must not indicate cross-carrier or cross-BWP scheduling. Additionally, if the value of the SRS request indicates the existence of the NZP CSI-RS, the NZP CSI-RS is located in the slot where the PDCCH containing the SRS request field was transmitted. In this case, the TCI states set on the scheduled subcarrier are not set to QCL-TypeD.

[0283] If a periodic or semi-persistent SRS resource set is established, the associated NZP CSI-RS can be indicated via the associated CSI-RS within the parent signaling SRS-ResourceSet. For non-codebook-based transmissions, the terminal does not expect the parent signaling spatialRelationInfo for the SRS resource and the associated CSI-RS within the parent signaling SRS-ResourceSet to be established together.

[0284] When a terminal is configured with multiple SRS resources, it can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. In this case, the SRI can be indicated via the field SRS resource indicator within the DCI or configured via the higher-level signaling srs-ResourceIndicator. Similar to the codebook-based PUSCH transmission described above, when the terminal receives the SRI via the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the SRI. The terminal may use one or multiple SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously within the same symbol in a single SRS resource set, as well as the maximum number of SRS resources, are determined by the UE capability reported by the terminal to the base station. In this case, the SRS resources transmitted simultaneously by the terminal occupy the same RB. The terminal configures one SRS port for each SRS resource. Only one SRS resource set can be configured with the value of usage in the upper signaling SRS-ResourceSet set set to 'nonCodebook', and up to four SRS resources can be configured for non-codebook-based PUSCH transmission.

[0285] The base station transmits one NZP-CSI-RS associated with an SRS resource set to the terminal, and the terminal calculates a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the results measured upon receiving the NZP-CSI-RS. When the terminal transmits one or more SRS resources within an SRS resource set where usage is set to 'nonCodebook' to the base station, it applies the calculated precoder, and the base station selects one or more SRS resources from among the received one or more SRS resources. At this time, in non-codebook-based PUSCH transmission, the SRI represents an index capable of expressing a combination of one or more SRS resources, and the SRI is included within the DCI. At this time, the number of SRS resources indicated by the SRI transmitted by the base station may be the number of transmission layers of the PUSCH, and the terminal transmits the PUSCH by applying the precoder applied for SRS resource transmission to each layer.

[0286] [Regarding Terminal Capability Reporting]

[0287] In LTE and NR, a terminal can perform a procedure to report the capabilities supported by the terminal to the base station while connected to the serving base station. In the description below, this is referred to as a UE capability report.

[0288] A base station may transmit a UE capability enquiry message requesting capability reporting to a connected terminal. The message may include a request for terminal capability specific to the base station's RAT (radio access technology) type. The request for each RAT type may include information such as supported frequency band combinations. Furthermore, in the case of the UE capability enquiry message, multiple UE capabilities for each RAT type may be requested through a single RRC message container transmitted by the base station, or the base station may transmit the UE capability enquiry message, which includes the request for each RAT type, to the terminal multiple times. That is, the UE capability inquiry may be repeated multiple times within a single message, and the terminal may construct and report the corresponding UE capability information message multiple times. In next-generation mobile communication systems, UE capability requests can be made for NR, LTE, EN-DC (E-UTRA - NR dual connectivity), and MR-DC (Multi-RAT dual connectivity). Additionally, while the UE capability enquiry message is generally transmitted initially after the terminal connects with the base station, the base station may request it under any conditions when necessary.

[0289] In the above step, the terminal that receives a request for a UE capability report from the base station configures the terminal capability according to the RAT type and band information requested from the base station. The method by which the terminal configures the UE capability in the NR system is summarized below.

[0290] 1. If the terminal receives a list of LTE and / or NR bands from the base station via a UE capability request, the terminal configures a band combination (BC) for EN-DC and NR stand-alone (SA). That is, it constructs a candidate list of BCs for EN-DC and NR SA based on the bands requested from the base station via FreqBandList. Additionally, the bands have priority in the order listed in FreqBandList.

[0291] 2. If the base station requests a UE capability report by setting the “eutra-nr-only” flag or the “eutra” flag, the terminal completely removes NR SA BCs from the above-mentioned list of configured BC candidates. This operation may occur only when the LTE base station (eNB) requests the “eutra” capability.

[0292] 3. Subsequently, the terminal removes fallback BCs from the candidate list of BCs configured in the above step. Here, a fallback BC refers to a BC that can be obtained by removing a band corresponding to at least one SCell from any BC; this step can be omitted because the BC before removing the band corresponding to at least one SCell already covers the fallback BC. This step applies to MR-DC as well, meaning it applies to LTE bands. The BCs remaining after this step constitute the final "candidate BC list."

[0293] 4. The terminal selects the BCs to be reported by selecting BCs that match the requested RAT type from the final "Candidate BC List" above. In this step, the terminal constructs the supportedBandCombinationList in a predetermined order. That is, the terminal constructs the BCs and UE capabilities to be reported according to the pre-set order of rat-Type (nr -> eutra-nr -> eutra). Additionally, it constructs a featureSetCombination for the constructed supportedBandCombinationList and constructs a list of "Candidate Feature Set Combinations" from the Candidate BC List from which the list of fallback BCs (containing capabilities of the same or lower level) has been removed. The above "Candidate Feature Set Combinations" include feature set combinations for both NR and EUTRA-NR BCs and can be obtained from the feature set combinations of the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0294] 5. Additionally, if the requested rat Type is eutra-nr and has an influence, featureSetCombinations is included in both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, the NR feature set is included only in UE-NR-Capabilities.

[0295] After the terminal capability is configured, the terminal transmits a terminal capability information message containing the terminal capability to the base station. Based on the terminal capability received from the terminal, the base station subsequently performs appropriate scheduling and transmission / reception management for the terminal.

[0296] In one embodiment of the present disclosure, a method for measuring and reporting L1-RSRP of a terminal is described.

[0297] To calculate L1-RSRP, the following points may be considered.

[0298] - The terminal may be configured with one or more CSI-RS resources, one or more SSB resources, or a combination of CSI-RS resources and SSB resources that have a QCL relationship between resources as QCL-TypeC and QCL-TypeD, and the CSI-RS resources and SSB resources may be included in different resource sets.

[0299] - The terminal can receive up to 64 CSI-RS resources within a single CSI-RS resource set.

[0300] - The terminal can be configured with up to 16 CSI-RS resource sets.

[0301] - The terminal can be configured with up to 128 different CSI-RS resources across all CSI-RS resource sets.

[0302] For L1-RSRP reporting, if the terminal has nrofReportedRS in the upper layer signaling CSI-ReportConfig set to 1, the reported L1-RSRP value can be quantized into 7 bits and the range of the value can be defined in 1 dB increments from -140 dBm to -44 dBm. If the terminal has nrofReportedRS in the upper layer signaling CSI-ReportConfig set to greater than 1, or if the terminal has groupBasedBeamReporting in the upper layer signaling set to enabled, the terminal can quantize the largest measured L1-RSRP value into 7 bits and the range of the value can be defined in 1 dB increments from -140 dBm to -44 dBm, and the differential L1-RSRP, which represents the RSRP value relative to the largest L1-RSRP value, can be quantized into 4 bits and the interval of the value can be defined in 2 dB. The corresponding differential L1-RSRP can be reported along with the largest L1-RSRP value mentioned above.

[0303] If timeRestrictionForChannelMeasurements, which is a higher layer signaling configured within CSI-ReportConfig, is set to "notConfigured" for the terminal, the terminal can calculate the L1-RSRP value to be reported in uplink slot n based on the CSI-RS or SSB in the CSI resource setting associated with the L1-RSRP report received in or prior to the CSI reference resource that can be defined in the time resource.

[0304] If timeRestrictionForChannelMeasurements, which is a higher layer signaling configured within CSI-ReportConfig, is configured to "Configured" for the terminal, the terminal can calculate the L1-RSRP value to be reported in uplink slot n based only on the most recent received location among the CSI-RS or SSB in the CSI resource setting associated with the L1-RSRP report received in or prior to the CSI reference resource that can be defined in the time resource.

[0305] [Table 25] below shows the order of information placement during L1-RSRP reporting. In this case, the bit lengths of the following CRI and SSBRI are either a number of bits capable of expressing the number of CSI-RS resources within the CSI-RS resource set (for example, ), can be defined as the number of bits capable of representing the number of SSB resources within an SSB resource set (for example, ). At this time and can represent the number of CSI-RS resources in the CSI-RS resource set and the number of SSB resources in the SSB resource set, respectively. As described above, RSRP and Differential RSRP can be represented by 7 bits and 4 bits, respectively.

[0306] CSI report numberCSI fieldsCSI report #nCRI or SSBRI #1CRI or SSBRI #1CRI or SSBRI #1CRI or SSBRI #1RSRP #1Differential RSRP #2Differential RSRP #3Differential RSRP #4

[0307] In one embodiment of the present disclosure, a method for setting resources for L1-SINR measurement and reporting is described. [Table 26] above relates to a CSI-ReportConfig set through upper-layer signaling related to CSI reporting, and can be used for the explanation of L1-SINR measurement to be described later. If one resource setting is set within the upper-layer signaling CSI-ReportConfig for L1-SINR measurement, the resource setting (e.g., resourcesForChannelMeasurement, an upper-layer signaling) may be an NZP CSI-RS for channel and interference measurement. In this case, it can be assumed that the terminal uses an NZP CSI-RS with one port and a density value of 3 REs / RB for channel and interference measurement.

[0308] If two resource settings are configured within the upper layer signaling CSI-ReportConfig for L1-SINR measurement, the corresponding first resource setting (e.g., the upper layer signaling resourcesForChannelMeasurement) may be an SSB or NZP CSI-RS for channel measurement, and the corresponding second resource setting (e.g., the upper layer signaling csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference) may be a CSI-IM for interference measurement or an NZP CSI-RS with one port and a density value of 3 REs / RB. In this case, the SSB or NZP CSI-RS for channel measurement may be connected to one CSI-IM resource or one NZP CSI-RS for interference measurement within the same resource set. The number of SSB or NZP CSI-RS for channel measurement may be equal to the number of NZP CSI-RS for CSI-IM or interference measurement.

[0309] - At this time, the terminal can determine the reference RS for the QCL-TypeD of the CSI-IM or NZP CSI-RS for interference measurement connected to the SSB or NZP CSI-RS for channel measurement as the reference RS for the SSB for channel measurement or the QCL-TypeD of the NZP CSI-RS for channel measurement.

[0310] In addition, the terminal can expect that repetition, which is a higher-layer signaling, is set in the NZP CSI-RS resource set for channel measurement and the NZP CSI-RS resource set for interference measurement. That is, both the NZP CSI-RS resource set for channel measurement and the NZP CSI-RS resource set for interference measurement can be used for beam management purposes.

[0311] For L1-SINR measurements based on a specific interference measurement resource, the terminal may assume that the total power received from a specific NZP CSI-RS resource for interference measurement or a specific CSI-IM resource for interference measurement corresponds to interference and noise.

[0312] For L1-SINR calculation, the terminal may be configured with NZP CSI-RS resources and / or SSB resources for channel measurement, and NZP CSI-RS or CSI-IM resources for interference measurement. In this case, for channel measurement, the terminal may be configured with up to 16 CSI resource sets, and up to 64 CSI-RS or 64 SSB resources across all resource sets.

[0313] If one or two of the above resource settings are set for L1-SINR measurement, a time restriction for channel measurement or interference measurement, which will be described later, may be considered.

[0314] - If timeRestrictionForChannelMeasurements in the upper layer signaling CSI-ReportConfig is set to 'notConfigured', the terminal may need to derive a channel measurement for calculating the L1-SINR to be reported in the nth uplink slot based on an SSB or NZP CSI-RS that can be received temporally earlier than the CSI reference resource associated with the one or two resource settings described above.

[0315] - If timeRestrictionForChannelMeasurements in the upper layer signaling CSI-ReportConfig is set to 'configured', the terminal may need to derive a channel measurement for calculating the L1-SINR to be reported in the nth uplink slot based on the most recent of the SSB or NZP CSI-RS that can be received temporally earlier than the CSI reference resource associated with the one or two resource settings described above.

[0316] - If timeRestrictionForInterferenceMeasurements in the upper layer signaling CSI-ReportConfig is set to 'notConfigured', the terminal may need to derive an interference measurement for calculating the L1-SINR to be reported in the nth uplink slot based on the CSI-IM or NZP CSI-RS for interference measurement that can be received temporally earlier than the CSI reference resource associated with the one or two resource settings described above.

[0317] - If timeRestrictionForChannelMeasurements in the upper layer signaling CSI-ReportConfig is set to 'configured', the terminal may need to derive an interference measurement for calculating the L1-SINR to be reported in the nth uplink slot based on the most recent of the CSI-IM or NZP CSI-RS for interference measurement that can be received temporally earlier than the CSI reference resource associated with the one or two resource settings described above.

[0318] Explain the terminal's L1-SINR reporting method.

[0319] When reporting L1-SINR, the terminal may construct a UCI using a specific quantization level according to the conditions described below and report it to the base station.

[0320] - If nrofReportedRS is set to 1 in the upper layer signaling CSI-ReportConfig, L1-SINR values ​​can be reported in 7-bit quantized using a step size of 0.5 dB for values ​​within the range of [-23, 40] dB.

[0321] - If nrofReportedRS in the upper layer signaling CSI-ReportConfig is greater than 1, or if the upper layer signaling groupBasedBeamReporting is set to 'enabled', the terminal can use differential L1-SINR reporting. In this case, the maximum L1-SINR value is quantized to 7-bit using a step size of 0.5 dB for values ​​within the [-23, 40] dB range, and the differential L1-SINR value can be quantized to 4-bit using a step size of 1 dB for the difference between the differential L1-SINR and the maximum L1-SINR reported together. If NZP CSI-RS is configured for channel measurement and / or interference measurement, the reported L1-SINR value can be expected not to be compensated by a power offset such as the upper layer signaling powerControlOffsetSS or powerControlOffset.

[0322] If the terminal receives the reportQuantity set to 'cri-SINR' or 'ssb-Index-SINR' within the upper-layer signaling CSI-ReportConfig, the terminal may consider the operations described below related to group-based beam reporting.

[0323] - If the terminal is set to 'disabled' for the upper layer signaling groupBasedBeamReporting, the terminal may report to the base station nrofReportedRS different CRIs or SSBRIs set for the upper layer signaling within a single report.

[0324] - If the terminal has groupBasedBeamReporting, a higher-layer signaling, set to 'enabled', the terminal may report to the base station two different CRIs or SSBRIs within a single report. In this case, the CSI-RS and / or SSBs designated as CRIs or SSBRIs may be those received simultaneously from the terminal.

[0325] If the terminal receives the reportQuantity set to 'ssb-Index-SINR' within the upper-layer signaling CSI-ReportConfig, the terminal may need to derive the L1-SINR based on the SSBRI reported to the base station. In this case, the SSBRI k (k≥0) may correspond to the (k+1)th entry in the csi-SSB-ResourceList in the CSI-SSB-ResourceSet for channel measurement, and may be connected to the (k+1)th entry in the csi-IM-Resource in the csi-IM-ResourceSet or the (k+1)th entry in the nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet for interference measurement.

[0326] If a terminal receives a reportQuantity set to 'cri-RSRP', 'cri-SINR', or 'none' within a higher-layer signaling CSI-ReportConfig, and the CSI-ReportConfig is connected to a resource setting where the resourceType is set to 'aperiodic', the terminal may not expect more than 16 CSI-RS resources to be set within the CSI-RS resource set included in that resource setting.

[0327] The mathematical formula for the priority rule for CSI reporting is It can be like this, and in this case, for a CSI report including an L1-SINR report, k can be considered as 0.

[0328] [Table 26] below shows the arrangement order of information during L1-SINR reporting. In this case, the bit lengths of the following CRI and SSBRI are either a number of bits capable of expressing the number of CSI-RS resources within the CSI-RS resource set (for example, ), can be defined as the number of bits capable of representing the number of SSB resources within an SSB resource set (for example, ). At this time and can represent the number of CSI-RS resources in the CSI-RS resource set and the number of SSB resources in the SSB resource set, respectively. As described above, SINR and Differential SINR can be represented by 7 bits and 4 bits, respectively.

[0329] CSI report numberCSI fieldsCSI report #nCRI or SSBRI #1CRI or SSBRI #1CRI or SSBRI #1CRI or SSBRI #1SINR #1Differential SINR #2Differential SINR #3Differential SINR #4

[0330] In one embodiment of the present disclosure, a CSI reporting event initiated by a terminal and information reported are described. This embodiment may operate in combination with other embodiments.

[0331] FIG. 9 is a diagram illustrating a channel measurement and channel status reporting method according to the setting and instructions of a base station according to one embodiment of the present disclosure.

[0332] In FIG. 9, the process (900) relates to a method for securing and managing downlink beam performance between a terminal and a base station according to periodic reference signal reception and periodic channel state information reporting at a terminal, or / and a non-periodic channel state information reporting trigger at a base station and a method for reporting non-periodic channel state information at a terminal.

[0333] The base station (902) can notify the terminal (901) of configuration information related to periodic reference signal reception and corresponding periodic channel state information reporting through upper layer signaling. Accordingly, the terminal can receive periodic reference signals transmitted from the base station (905) and report corresponding periodic channel state information (910). At this time, the corresponding periodic channel state information may include performance for the downlink reception beam calculated by the terminal. The base station can determine the downlink reception beam performance of the terminal based on the terminal's periodic reference signal reception and measurement and periodic channel state information reporting. The shorter the period of reference signal reception and measurement and channel state information reporting, the more accurately the base station can determine the terminal's downlink reception beam performance, but the signaling overhead for transmitting and receiving reference signals and channel state information reports between the terminal and the base station may increase.

[0334] In contrast, if the period for receiving and measuring the reference signal and reporting the channel state information is long, the base station may be relatively inaccurate in determining the terminal's receiving beam performance. Therefore, the base station may trigger an aperiodic channel state information report to determine the terminal's receiving beam performance in the middle of the long period (935). Subsequently, the terminal may perform an aperiodic channel state information report in response to the base station's triggering of the aperiodic channel state information report (940). The base station may synthesize this information and, if the terminal's downlink receiving beam performance is insufficient and a change to another beam is required, notify the terminal of beam switching (945). The beam switching may be performed by changing the TCI state directed to the terminal or by methods such as RRC reconfiguration to change the settings for the source RS within the TCI state.

[0335] In order for a base station to trigger a non-periodic channel state information report to a terminal, it may assume implicit information from the terminal to make such a decision through the base station implementation. The implicit information may be information about the channel state, and representative implicit information may include a PDCCH transmitted by the base station to the terminal and a PDSCH reception (920) that can be scheduled through it, or a PUCCH transmission from the terminal containing HARQ-ACK information indicating whether the reception was successful (925). Based on information such as a periodic channel state information report (910) that can be received from the terminal and a PUCCH (925) containing HARQ-ACK information corresponding to the PDSCH scheduled for the terminal, the base station may make a decision as to whether the terminal needs to change the downlink reception beam, or if not, whether it is acceptable to maintain the current reception beam (915). However, since this information is implicit, or even if it is direct information, it is highly likely that the base station cannot obtain it when it wants to, the amount of information from the base station regarding the terminal's downlink reception beam performance may be insufficient in absolute terms or may be information that is already past.

[0336] In FIG. 9, the process (950) relates to a method for securing and managing transmission and reception beam performance between a terminal and a base station according to a channel status information reporting method initiated from a terminal in response to a specific event occurring at the terminal.

[0337] To resolve the problems in the above-described process (900), the base station may notify the terminal of configuration information regarding a channel state information reporting method initiated by the terminal based on at least one combination of upper layer signaling, MAC-CE signaling, and L1 signaling. Based on this, the terminal may receive at least one combination of periodic reference signals, semi-continuous reference signals, and non-periodic reference signals (955), and the terminal may perform channel state information reporting initiated by the terminal (965) as a specific event defined in the terminal occurs (960). Subsequently, the base station may instruct the terminal to perform beam switching based on the information transmitted from the terminal (970).

[0338] Unlike the method in which a base station relies on implicit information to trigger aperiodic channel state reports or notify beam switching, the terminal voluntarily transmits information regarding its downlink receive beam performance to the base station (e.g., without triggering the base station's channel state reports). According to this method, even if the base station does not trigger (channel state reports or beam switching), if the downlink receive beam performance at the terminal changes according to a specific event defined at the terminal, the terminal can immediately detect the change in downlink receive beam performance and take corresponding action (e.g., triggering aperiodic channel state reports or directing beam switching). Since the base station can respond immediately to downlink receive beam changes when necessary based on channel state reports initiated by the terminal, the latency for beam management can be reduced. In addition, by reducing the frequency of periodic reference signal reception and periodic channel state information reporting between the terminal and the base station, the signaling overhead for reference signals and channel state information reporting can be significantly reduced, unlike the method in which the base station can quickly verify the downlink reception beam performance of the terminal even without channel state information reporting originating from the terminal.

[0339] For a channel state information reporting method initiated from the terminal described above, the terminal needs to define a specific event (960) and, when the event occurs, notify the base station that the terminal's downlink receiving beam performance has changed. The terminal may define a specific event for the channel state information reporting initiated from the terminal described above to be performed. The specific event for initiating the terminal's channel state information reporting may be any one of the following items or a combination of at least two or more. Of course, it is not limited to the following examples.

[0340] [Case 1]

[0341] If there is a new receiving beam that has a performance indicator higher than a specific threshold value than the performance of the current receiving beam, the terminal may perform a channel state information report originating from the terminal, including information on the new receiving beam. In this case, for the [Event 1], the new receiving beam and the current receiving beam may be defined as follows.

[0342] - For [Event 1], the new receiving beam can be set to the terminal through upper layer signaling.

[0343] ● Here, the fact that a new receiving beam is set to the terminal through upper layer signaling may mean that a reference signal corresponding to the new receiving beam is set to the terminal through upper layer signaling.

[0344] ● Therefore, in the following description, receiving a new received beam can be understood as receiving a reference signal corresponding to the new received beam. Additionally, the terminal measuring a new received beam can be understood as the terminal measuring a reference signal corresponding to the new received beam. The terminal may consider CSI-RS or SSB as the reference signal for the new received beam.

[0345] ● When a terminal is configured with an upper layer signaling for a new receiving beam, it may be configured with a set of reference signals containing one or more reference signals that may represent the new receiving beam within the upper layer signaling related to the channel status information report originating from the terminal described above (for example, the upper layer signaling CSI-ReportConfig).

[0346] ● For example, if a terminal and a base station consider CSI-RS as a reference signal for a new receiving beam, the terminal may set a CSI-RS resource set containing one or more CSI-RS resources as a set of new receiving beams.

[0347] ● In addition, if the terminal and the base station consider an SSB as a reference signal for a new receiving beam, the terminal may receive an SSB resource set containing one or more SSB resources as a set of new receiving beams.

[0348] - For [Event 1], the current receiving beam can be determined by considering the following points.

[0349] ● [Current Received Beam Determination Method 1] The terminal can define the current received beam as a reference signal set as a QCL source within the integrated TCI state applied to the terminal.

[0350] ● [Current Received Beam Determination Method 2] The terminal can define the current received beam as an SSB that is in a QCL relationship with the reference signal set as the QCL source.

[0351] ● The statement defining the current received beam as a specific reference signal can be understood to mean that the terminal determines parameters to be used as a receiving beam or receiving filter corresponding to the current received beam based on the received specific reference signal. Alternatively, the statement defining the current received beam as a specific reference signal can be understood to mean that when the terminal measures and judges the performance of the current received beam, it measures the performance of a specific reference signal that the terminal can receive and determines the performance of the current received beam based on the measured performance. The specific method for determining the current received beam may be any one of the following methods or a combination of two or more.

[0352] ● If there is only one reference signal set as a QCL source within the integrated TCI state applied to the above terminal, that is, if a QCL source for QCL-Type A, B, or C is set in the TCI state and a QCL source for QCL-Type D is not set, the terminal may use the reference signal set as a QCL source for QCL-Type A, B, or C when determining the current receiving beam.

[0353] ● If there are multiple reference signals set as QCL sources within the integrated TCI state applied to the above terminal, for example, if the TCI state has a QCL source for QCL-TypeD as well as QCL-TypeA, B, or C, the terminal may use the reference signal set as a QCL source for QCL-TypeD instead of the reference signal set as a QCL source for QCL-TypeA, B, or C when determining the current receiving beam. For example, if the TCI state applied to the terminal has a reference signal set as a QCL source for QCL-TypeA and a reference signal set as a QCL source for QCL-TypeD, respectively (for example, if each of the two reference signals is set as a QCL source for QCL-TypeA and QCL-TypeD, respectively), then the terminal checking the performance of the reference signal set as a QCL source for the TCI state applied to the terminal may mean checking the performance of the reference signal set as a QCL source for QCL-TypeD.

[0354] ● The terminal may consider CSI-RS as a reference signal that can be set as the above QCL source. In this case, the CSI-RS that the terminal considers as a reference signal may be a Tracking Reference Signal (TRS) with upper layer signaling trs-info set, a CSI-RS for beam management with upper layer signaling repetition set to on or off, or a CSI-RS for CSI with neither upper layer signaling trs-info nor repetition set. Additionally, the terminal may consider only TRS, only CSI-RS for beam management, or both TRS and CSI-RS for beam management as a reference signal that can be set as the above QCL source. Additionally, if the reference signal CSI-RS that can be set as the above QCL source is defined as a specific CSI-RS resource, the CSI-RS resource may be included in a CSI-RS resource set in which the upper layer signaling trs-info is set to true, and / or the CSI-RS resource may be set in a CSI-RS resource set in which the upper layer signaling repetition is set.

[0355] - Regarding [Event 1], the terminal can expect the types of the current receiving beam and the new receiving beam to remain the same. The terminal can be configured for the new receiving beam through upper layer signaling as described above, and according to the configuration, if the type of the new receiving beam is CSI-RS, the terminal can use the [Current Receiving Beam Determination Method 1] described above to determine the current receiving beam. Additionally, if the type of the new receiving beam is SSB, the terminal can use the [Current Receiving Beam Determination Method 2] described above to determine the current receiving beam.

[0356] - For [Event 1], the specific reference value used when comparing the performance of the new receiving beam and the current receiving beam may be a value that the terminal reports to the base station as terminal capability, a value that the base station sets to the terminal as upper layer signaling, a value that the base station selects from one or more values ​​reported to the base station as terminal capability and sets to the terminal as upper layer signaling, or a value fixedly defined in the standard.

[0357] - When determining whether [Event 1] has occurred, the terminal may consider single-event-based judgment and multiple-event-based judgment. The terminal may report the single-event-based judgment method as the basic judgment method for [Event 1] through terminal capabilities, and the multiple-event-based judgment method can be used as the judgment method for [Event 1] only if the terminal reports additional terminal capabilities. In the case of single-event-based judgment, the terminal can determine the performance of the new receiving beam and the current receiving beam by receiving the reference signal corresponding to the new receiving beam and the reference signal corresponding to the current receiving beam only once. When making a single-event-based judgment, the terminal can make a judgment on whether [Event 1] has occurred at each reception location of the new receiving beam that exists thereafter, while knowing the performance of the current receiving beam.

[0358] - For [Event 1], for multi-event-based judgment, the terminal may introduce a specific time interval and a counter to determine whether the performance of a new received beam is higher than a specific threshold value compared to the performance of the current received beam. The terminal may determine whether [Event 1] has occurred at a point within that time interval by using a time interval that starts based on the time when information about the current received beam is identified. At this time, the time when information about the current received beam is identified may be the time when the currently indicated TCI state is applied, or the time when a reference signal (CSI-RS or SSB, as described above) corresponding to the current received beam is received after the time when the currently indicated TCI state is applied. At this time, the length of the time interval may be the period value of the reference signal corresponding to the current received beam, or a real value frame, subframe, slot, symbol, or absolute time (e.g., msec) that is shorter or longer than that, and the length of such a time interval may be set by the terminal from the base station via upper layer signaling. The terminal may reset the time interval whenever it receives a reference signal corresponding to the current received beam, or at the time when the time interval ends. Within the time interval, the terminal may receive each reference signal (e.g., CSI-RS or SSB) corresponding to each of one or more new received beams. If [Event 1] occurs for a specific new received beam more than a certain number of times within the time interval, the terminal may report the received beam performance to the base station. Additionally, the terminal may store the number of times [Event 1] occurs continuously within the time interval from the start point of the time interval in the counter described above. If the terminal confirms that the value of the counter is greater than a certain number, the terminal may report the received beam performance to the base station. In this case, the number of times [Event 1] occurs continuously may mean that the performance of a specific new received beam is higher than a certain reference value compared to the current received beam.For example, if the performance of each of two different new receiving beams is higher than a specific threshold value compared to the current receiving beam, the terminal may consider that [Event 1] has occurred once for each new receiving beam. Within the corresponding time interval, the terminal can check whether [Event 1] has occurred for each period of the current receiving beam. If [Event 1] has occurred continuously within the time interval but has not yet occurred more than a specific number of times, and [Event 1] does not occur during a specific period of the current receiving beam, thereby causing the number of times [Event 1] has occurred continuously to be less than a specific number, the terminal may reset the end point of the specific period for the current receiving beam to the starting point of the said time interval. In this way, the terminal can check the number of times [Event 1] occurs continuously within the specific time interval and report the receiving beam performance originating from the terminal to the base station. In one embodiment, the specific number may be 1 by default, and the terminal may receive a specific natural number X greater than 1 from the base station. In one embodiment, the terminal may report a terminal capability to the base station that includes the meaning that the specific number is considered as 1 or as a specific natural number X greater than 1. Subsequently, the base station may set the specific number to the terminal based on the terminal capability received from the terminal. Accordingly, the terminal may ultimately determine the specific number based on the setting received from the base station. In another embodiment, the terminal may report a terminal capability to the base station that includes the meaning that the specific number is considered as 1 or as a specific natural number X greater than 1. And the base station that receives the terminal capability may determine or use the value reported by the terminal as the specific number value as is, without additional upper layer signaling settings for the terminal.

[0359] - For [Event 1], when the terminal reports the reception beam performance originating from the terminal, it may report to the base station including at least one of the following items.

[0360] ● The terminal may report to the base station including the index of the new received beam or / and the performance of the new received beam. The terminal may receive a setting from the base station via upper layer signaling to include the performance of the number of new received beams to report to the base station. For example, the terminal may receive a setting from the base station for the number of new received beams to report. In this case, the number of new received beams to report may be N, a natural number greater than or equal to 1. More specifically, N may be 1, 2, 3, or 4, or a natural number less than or equal to 64. In this case, the number of new received beams to report may follow the upper layer signaling described above. Additionally, if the terminal includes the index of each of N new receiving beams in the receiving beam performance report originating from the terminal, the index of each new receiving beam may be represented by the ceil(log2(K)) bit, where ceil(.) and log2(.) represent a ceiling function and a base-2 logarithmic function, respectively, and K may represent the number of new receiving beams set within the new receiving beam set. If the type of new receiving beam is CSI-RS, K may represent the number of CSI-RS resources set within the CSI-RS resource set, and if the type of new receiving beam is SSB, K may represent the number of SSB resources set within the SSB resource set.

[0361] ● When the terminal reports the N new received beams, it can expect that at least one of the N new received beams satisfies [Event 1]. For example, the terminal may assume that the performance of some of the N new received beams is higher than a specific threshold value compared to the performance of the current received beam. The terminal may also assume that the remaining new received beams, excluding some new received beams that are higher than a specific threshold value compared to the performance of the current received beam, are not higher than a specific threshold value compared to the performance of the current received beam.

[0362] ● The terminal may report the L1-RSRP value of the new receiving beam with the best performance among the N new receiving beams by quantizing it into a total of 7 bits in 1 dB increments from -140 dBm to -44 dBm. Additionally, the terminal may express the performance of the remaining N-1 new receiving beams as a difference value from the performance of the new receiving beam having the largest L1-RSRP value (for example, it may mean a differential L1-RSRP value), and may quantize the differential L1-RSRP value in 2 dB increments into a total of 4 bits.

[0363] ● The terminal may report to the base station including the index of the current receiving beam and / or the performance of the current receiving beam. In this case, the index of the current receiving beam may be the index of the CSI-RS resource if the current receiving beam is CSI-RS as described above, or the index of the SSB if the current receiving beam is SSB. The terminal may receive a setting from the base station via upper layer signaling as to whether to report to the base station including the index of the current receiving beam and / or the performance of the current receiving beam. For example, if the terminal receives an upper layer signaling setting from the base station, the terminal may report including the index of the current receiving beam and / or the performance of the current receiving beam when reporting the receiving beam performance originating from the terminal. If the terminal does not receive an upper layer signaling setting from the base station, the terminal may perform a report of the receiving beam performance originating from the terminal by including only the index of the new receiving beam and / or the performance value of the new receiving beam, without including the index of the current receiving beam and / or the performance of the current receiving beam.

[0364] ● When a terminal reports to a base station the performance of the current received beam (e.g., L1-RSRP performance), the terminal may express the L1-RSRP performance of the current received beam as a difference value from the performance of the new received beam with the best performance (e.g., may mean a differential L1-RSRP value), and may quantize the differential L1-RSRP value in units of 2 dB into a total of 4 bits. Additionally, the terminal may report the L1-RSRP performance of the current received beam by quantizing the value in units of 1 dB from -140 dBm to -44 dBm into a total of 7 bits. Such reporting methods of the terminal are merely examples, and the present disclosure is not limited by the above examples.

[0365] [Case 2]

[0366] If the performance of the current received beam is below a specific threshold value, the terminal may perform a channel status information report initiated by (or initiated by) the terminal, including current received beam information.

[0367] - For [Event 2], the new receiving beam can be set to the terminal through upper layer signaling.

[0368] ● Here, the fact that a new receiving beam is set to the terminal through upper layer signaling may mean that a reference signal corresponding to the new receiving beam is set to the terminal through upper layer signaling.

[0369] ● Therefore, in the following description, receiving a new received beam can be understood as receiving a reference signal corresponding to the new received beam. Additionally, the terminal measuring a new received beam can be understood as the terminal measuring a reference signal corresponding to the new received beam. The terminal may consider CSI-RS or SSB as the reference signal for the new received beam.

[0370] ● When a terminal is configured with an upper layer signaling for a new receiving beam, it may be configured with a set of reference signals containing one or more reference signals that may represent the new receiving beam within the upper layer signaling related to the channel status information report originating from the terminal described above (for example, the upper layer signaling CSI-ReportConfig).

[0371] ● For example, if a terminal and a base station consider CSI-RS as a reference signal for a new receiving beam, the terminal may set a CSI-RS resource set containing one or more CSI-RS resources as a set of new receiving beams.

[0372] ● In addition, if the terminal and the base station consider an SSB as a reference signal for a new receiving beam, the terminal may receive an SSB resource set containing one or more SSB resources as a set of new receiving beams.

[0373] ● The terminal may not define a new receiving beam for [Event 2]. That is, the terminal may perform a receiving beam performance report originating from the terminal associated with [Event 2] based only on the definition of the current receiving beam.

[0374] - For [Event 2], the current receiving beam can be determined as either [current receiving beam determination method 1] or [current receiving beam determination method 2], similar to [Event 1] described above.

[0375] ● If the terminal does not receive upper layer signaling settings related to the new receiving beam for [Event 2], the terminal may determine the type of the current receiving beam (one of CSI-RS or SSB) by receiving individual upper layer signaling settings instead of determining it through the upper layer signaling related to the new receiving beam. For example, the terminal may receive upper layer signaling from the base station that provides information about what type of current receiving beam is. For instance, the terminal may receive setting information related to the type of the current receiving beam within CSI-ReportConfig, which is an upper layer signaling related to the receiving beam performance report originating from the terminal. Such setting locations are merely examples and are not limited thereto. Additionally, the above-described setting information may be set within the upper layer signaling related to the serving cell in which the terminal operates, the bandwidth portion, or the serving cell in which the terminal reports the receiving beam performance originating from the terminal.

[0376] ● If the terminal receives upper-layer signaling settings related to the new receiving beam for [Event 2], the terminal can expect that the types of the current receiving beam and the new receiving beam remain the same depending on what type the new receiving beam is set to, similar to [Event 1]. The terminal can receive settings for the new receiving beam through upper-layer signaling as described above. Additionally, depending on the settings for the new receiving beam, if the type of the new receiving beam is CSI-RS, the terminal can use the [Current Receiving Beam Determination Method 1] described above to determine the current receiving beam. Additionally, if the type of the new receiving beam is SSB, the terminal can use the [Current Receiving Beam Determination Method 2] described above to determine the current receiving beam.

[0377] - Regarding [Event 2], the specific reference value used to verify the performance of the current receiving beam may be a value that the terminal reports to the base station as terminal capability, a value that the base station sets to the terminal as upper layer signaling, a value that the base station selects from one or more values ​​reported to the base station as terminal capability and sets to the terminal as upper layer signaling, or a value fixedly defined in the specifications. Additionally, the terminal may define different individual specific reference values ​​depending on the type of the current receiving beam.

[0378] - In determining whether [Event 2] has occurred, the terminal may consider single-event-based judgment and multiple-event-based judgment. The terminal may report the single-event-based judgment method as the basic judgment method for [Event 2] through terminal capabilities, and the multiple-event-based judgment method can be used as the judgment method for [Event 2] only if the terminal reports additional terminal capabilities. In the case of single-event-based judgment, the terminal can determine the performance of the current receiving beam by receiving a reference signal corresponding to the current receiving beam only once. When making a single-event-based judgment, the terminal can determine whether [Event 2] has occurred at each reception location of the current receiving beam. For example, the terminal can measure the performance of the current receiving beam at each reception location of the current receiving beam and compare it with the specific reference value described above. Furthermore, if the performance of the current receiving beam is lower than the specific reference value, the terminal can determine that [Event 2] has occurred when making a single-event-based judgment and can subsequently perform a report on the receiving beam performance starting from the terminal.

[0379] - Regarding [Event 2], the terminal may introduce a specific time interval and a counter to determine whether the performance of the current received beam is below a specific threshold value. The terminal may determine whether [Event 2] occurs within a time interval by using a time interval that starts based on the point in time when information about the current received beam is identified. At this time, the point in time when information about the current received beam is identified may be the point in time when the currently indicated TCI state is applied, or the point in time when a reference signal (CSI-RS or SSB, as described above) corresponding to the current received beam is received after the point in time when the currently indicated TCI state is applied. At this time, the length of the time interval may be the period value of the reference signal corresponding to the current received beam, or a real value frame, subframe, slot, symbol, or absolute time (e.g., msec) that is shorter or longer than that, and the length of such a time interval may be set by the terminal from the base station via upper layer signaling. The terminal may confirm that [Event 2] occurs from the start point of the time interval for the duration of the time interval. The terminal may store in a counter the number of times [Event 2] occurs within the time interval starting from the beginning of the time interval. If the terminal confirms that the value of the counter is greater than a specific number, the terminal may report the reception beam performance to the base station. Additionally, the terminal may store in the aforementioned counter the number of times [Event 2] occurs continuously within the time interval starting from the beginning of the time interval. If the terminal confirms that the value of the counter is greater than a specific number, the terminal may report the reception beam performance to the base station. Within the time interval, the terminal may check whether [Event 2] occurs at each period of the current reception beam.If [Event 2] occurs continuously within a time interval but has not yet occurred more than a specific number of times, and [Event 2] does not occur during a specific period of the current receiving beam, resulting in the number of times [Event 2] occurs continuously not exceeding the specific number, the terminal may reset the last point of the specific period of the current receiving beam to the starting point of the said time interval. In this way, the terminal can verify the number of times [Event 2] occurs continuously within a specific time interval and report the receiving beam performance originating from the terminal to the base station. At this time, the specific number may be basically 1 time, and the terminal may receive a specific natural number X greater than 1 as a setting from the base station. In one embodiment, the terminal may report a terminal capability to the base station that includes the meaning of considering the specific number as 1 or as a specific natural number X greater than 1. Subsequently, the base station may set the specific number to the terminal based on the terminal capability received from the terminal. Accordingly, the terminal may finally determine the specific number based on the setting received from the base station. In another embodiment, the terminal may report a terminal capability to the base station having the meaning that the specific number is considered as 1 or as a specific natural number X greater than 1. And the base station that receives the terminal capability may determine or use the value reported by the terminal as the specific number value as is, without additional upper layer signaling settings to the terminal.

[0380] - In the event that [Event 2] occurs, the terminal may consider at least one of the following items when reporting the reception beam performance originating from the terminal to the base station.

[0381] ● (Alt1) The terminal may not report the reception beam performance originating from the terminal to the base station. That is, the terminal may report to the base station that [Event 2] has occurred, but may not subsequently report the performance of the new reception beam or / and the current reception beam (e.g., L1-RSRP or L1-SINR). The base station may recognize that [Event 2] has occurred by receiving a PUCCH transmitted by the terminal, and thereby recognize that the performance of the terminal's current reception beam is lower than a certain threshold value that is commonly understood by the terminal and the base station.

[0382] ● (Alt2) Alternatively, the terminal may determine whether to report the received beam performance initiated by the terminal based on whether the index of the current received beam or / and the upper layer signaling having the meaning of reporting the current received beam performance to the base station is configured.

[0383] ■ If the terminal has not received the upper layer signaling described above, the terminal may not perform a report on the received beam performance originating from the terminal to the base station. That is, the terminal may report to the base station that [Event 2] has occurred, but may not subsequently report the performance of the new received beam or / and the current received beam (e.g., L1-RSRP or L1-SINR). The base station may recognize that [Event 2] has occurred by receiving a PUCCH transmitted by the terminal, and through this, the base station may recognize that the performance of the terminal's current received beam is lower than a specific threshold value that is commonly understood by the terminal and the base station.

[0384] ■ If the terminal receives the upper layer signaling described above, the terminal may perform a receiving beam performance report originating from the terminal to the base station, wherein the receiving beam performance report originating from the terminal may include the index of the current receiving beam or / and the performance of the current receiving beam. The index of the current receiving beam may be a CSI-RS resource or an SSB index. The terminal may report the L1-RSRP performance of the current receiving beam by quantizing values ​​in 1 dB increments from -140 dBm to -44 dBm into a total of 7 bits. Alternatively, when reporting the L1-RSRP performance of the current receiving beam, the terminal may express it as a difference value from the specific reference value described above (e.g., may mean a differential L1-RSRP value), and may quantize a differential L1-RSRP value in 2 dB increments into a total of 4 bits. Furthermore, such reporting methods of the terminal are merely examples, and the present disclosure is not limited by the above examples.

[0385] ● (Alt3) Alternatively, when the terminal reports the received beam performance originating from the terminal, it may include the index of the current received beam and / or the performance of the current received beam, depending on whether the terminal has an upper layer signaling setting that implies reporting the index of the current received beam and / or the performance of the current received beam to the base station. Additionally, if the terminal has received an upper layer signaling setting for a new received beam for [Event 2], the terminal may include the index of the new received beam and / or the performance of the new received beam in its report. Furthermore, when the terminal reports the received beam performance originating from the terminal, it may include the number of times the performance of the current received beam is lower than the aforementioned specific reference value within a specific time interval set to the terminal via the upper layer signaling.

[0386] ■ If the terminal receives an upper layer signaling that means to report the index of the current receiving beam or / and the performance of the current receiving beam to the base station, the terminal may report the L1-RSRP performance of the current receiving beam by quantizing it into a total of 7 bits in 1 dB increments from -140 dBm to -44 dBm, or when reporting the L1-RSRP performance of the current receiving beam, it may express it as a difference value from the specific reference value mentioned above (for example, it may mean a differential L1-RSRP value), and may quantize a differential L1-RSRP value in 2 dB increments into a total of 4 bits.

[0387] ■ At this time, the terminal may consider the performance of the new received beam, the specific reference value described above, and the performance of the current received beam to be unrelated to each other. In other words, when reporting the performance of a received beam initiated by the terminal based on [Event 2], the terminal may report the performance of the new received beams (e.g., N) as a number of the base stations with the best performance at the time of reporting, among all new received beams set by the base station. The terminal may report the L1-RSRP value of the new received beam with the best performance among the N new received beams by quantizing it into a total of 7 bits in 1 dB increments from -140 dBm to -44 dBm. Additionally, the terminal may express the performance of the remaining N-1 new received beams as a difference value from the performance of the new received beam having the largest L1-RSRP value (e.g., may mean a differential L1-RSRP value), and may quantize the differential L1-RSRP value in 2 dB increments into a total of 4 bits. Additionally, the terminal may use differential L1-RSRP values, which are differences from the aforementioned specific reference value, to represent the performance of N new receiving beams, and may add 1 bit to represent a code to indicate performance that is higher or lower than the specific reference value. For example, in the case of a new receiving beam that indicates high performance relative to the specific reference value, 1 bit may have a value of 1, and in the case of a new receiving beam that indicates low performance, 1 bit may have a value of 0. Additionally, the terminal may use differential L1-RSRP values, which are differences from the performance of the current receiving beam, to represent the performance of N new receiving beams. In this case, the terminal may add 1 bit to represent a code to indicate performance that is higher or lower than the specific reference value.For example, in the case of a new receiving beam that exhibits high performance relative to a specific reference value, 1 bit may have a value of 1, and in the case of a new receiving beam that exhibits low performance, 1 bit may have a value of 0.

[0388] [Case 3]

[0389] If the performance of at least one new received beam is higher than the performance of the current received beam by a specific threshold value or more, the terminal may perform a channel state information report initiated from the terminal, including new received beam information. At this time, for the [Event 3], the new received beam and the current received beam may be defined as follows.

[0390] - For [Event 3], the new receiving beam can be set to the terminal through upper layer signaling.

[0391] ● Here, the fact that a new receiving beam is set to the terminal through upper layer signaling may mean that a reference signal corresponding to the new receiving beam is set to the terminal through upper layer signaling.

[0392] ● Therefore, in the following description, receiving a new received beam can be understood as receiving a reference signal corresponding to the new received beam. Additionally, the terminal measuring a new received beam can be understood as the terminal measuring a reference signal corresponding to the new received beam. The terminal may consider CSI-RS or SSB as the reference signal for the new received beam.

[0393] ● When a terminal is configured with an upper layer signaling for a new receiving beam, it may be configured with a set of reference signals containing one or more reference signals that may represent the new receiving beam within the upper layer signaling related to the channel status information report originating from the terminal described above (for example, the upper layer signaling CSI-ReportConfig).

[0394] ● For example, if a terminal and a base station consider CSI-RS as a reference signal for a new receiving beam, the terminal may set a CSI-RS resource set containing one or more CSI-RS resources as a set of new receiving beams.

[0395] ● In addition, if the terminal and the base station consider an SSB as a reference signal for a new receiving beam, the terminal may receive an SSB resource set containing one or more SSB resources as a set of new receiving beams.

[0396] - For [Event 3], the current receiving beam can be determined by considering the following points.

[0397] ● When defining the current receive beam, the terminal may determine the Qth best reference signal among the reference signals set as QCL sources associated with one or more TCI states activated to the terminal. More specifically, the terminal may define the current receive beam based on the following two methods.

[0398] ■ [Current Receive Beam Determination Method 3] The terminal can define the current receive beam as the Qth best reference signal among the reference signals set as QCL sources within one or more TCI states activated to the terminal.

[0399] ■ [Current Receive Beam Determination Method 4] The terminal can define the current receive beam as the Qth best reference signal among the SSBs that have a QCL relationship with each reference signal set as a QCL source within one or more TCI states activated to the terminal.

[0400] ■ At this time, the terminal may report one Q value to the base station through terminal capability, and if not, the base station may consider that the terminal does not support [Event 3] described above. If the terminal reports one Q value, the base station may set the Q value to enable the terminal to perform a receive beam performance report initiated from the terminal based on [Event 3].

[0401] ● The statement defining the current received beam as a specific reference signal can be understood to mean that the terminal determines parameters to be used as a receiving beam or receiving filter corresponding to the current received beam based on the received specific reference signal. Alternatively, the statement defining the current received beam as a specific reference signal can be understood to mean that when the terminal measures and judges the performance of the current received beam, it measures the performance of the specific reference signal that the terminal can receive and determines the performance of the current received beam based on the measured performance. The specific method for determining the current received beam may be a combination of one or more of the methods below.

[0402] ● If there is one reference signal set as a QCL source within the integrated TCI state applied to the above terminal, for example, if a QCL source for QCL-Type A, B, or C is set in the TCI state and a QCL source for QCL-Type D is not set, the terminal may use the reference signal set as a QCL source for QCL-Type A, B, or C when determining the current receiving beam.

[0403] ● If there are multiple reference signals set as QCL sources within the integrated TCI state applied to the above terminal, for example, if a QCL source for QCL-TypeD is set in addition to QCL-TypeA, B, or C in the TCI state, the terminal may use the reference signal set as a QCL source for QCL-TypeD instead of the reference signal set as a QCL source for QCL-TypeA, B, or C when determining the current receiving beam. For example, if the TCI state applied to the terminal has a reference signal set as a QCL source for QCL-TypeA and a reference signal set as a QCL source for QCL-TypeD, respectively (for example, if each of the two reference signals is set as a QCL source for QCL-TypeA and QCL-TypeD, respectively), then the terminal checking the performance of the reference signal set as a QCL source for the TCI state applied to the terminal may mean checking the performance of the reference signal set as a QCL source for QCL-TypeD.

[0404] ● The terminal may consider CSI-RS as a reference signal that can be set as the QCL source. In this case, CSI-RS may be a TRS with upper layer signaling trs-info set, a CSI-RS for beam management with upper layer signaling repetition set to on or off, or a CSI-RS for CSI with neither upper layer signaling trs-info nor repetition set. Additionally, the terminal may consider only TRS, only CSI-RS for beam management, or both TRS and CSI-RS for beam management as a reference signal that can be set as the QCL source. Furthermore, if the CSI-RS, which is the reference signal that can be set as the QCL source, is defined as a specific CSI-RS resource, the CSI-RS resource may be included in a CSI-RS resource set where upper layer signaling trs-info is set to true, or / and the said CSI-RS resource may be set within a CSI-RS resource set where upper layer signaling repetition is set.

[0405] - Regarding [Event 3], the terminal can expect the types of the current receiving beam and the new receiving beam to remain the same. The terminal can receive the new receiving beam through upper layer signaling as described above. And according to the setting, if the type of the new receiving beam is CSI-RS, the terminal can use the [Current Receiving Beam Determination Method 3] described above to determine the current receiving beam. Also, if the type of the new receiving beam is SSB, the terminal can use the [Current Receiving Beam Determination Method 4] described above to determine the current receiving beam.

[0406] - For [Event 3], the specific reference value used when comparing the performance of the new receiving beam and the current receiving beam may be a value that the terminal reports to the base station as terminal capability, a value that the base station sets to the terminal as upper layer signaling, a value that the base station selects from one or more values ​​reported to the base station as terminal capability and sets to the terminal as upper layer signaling, or a value fixedly defined in the standard.

[0407] - Regarding [Event 3], when the terminal reports the reception beam performance originating from the terminal, it may report to the base station including at least one of the following items.

[0408] ● (Alt1 New Received Beam) The terminal may report to the base station including the index of the new received beam or / and the performance of the new received beam. The terminal may receive a setting from the base station via upper layer signaling to include the performance of the number of new received beams to report to the base station. For example, the terminal may receive a setting from the base station for the number of new received beams to report. In this case, the number of new received beams to report may be N, a natural number greater than or equal to 1. More specifically, N may be 1, 2, 3, or 4, or a natural number less than or equal to 64. In this case, the number of new received beams to report may follow the upper layer signaling described above. Additionally, if the terminal includes the index of each of N new receiving beams in the receiving beam performance report originating from the terminal, the index of each new receiving beam may be represented by the ceil(log2(K)) bit, where ceil(.) and log2(.) may represent a ceiling function and a base-2 logarithmic function, respectively, and K may represent the number of new receiving beams set within the new receiving beam set. If the type of new receiving beam is CSI-RS, K may represent the number of CSI-RS resources set within the CSI-RS resource set, and if the type of new receiving beam is SSB, K may represent the number of SSB resources set within the SSB resource set.

[0409] ● (Alt1 New Received Beam) When the terminal reports the N new received beams, it can expect that at least one of the N new received beams satisfies [Event 3]. For example, the terminal may assume that the performance of some of the N new received beams is higher than a specific reference value compared to the performance of the current received beam, and may assume that the remaining new received beams, excluding the said some, are not higher than a specific reference value compared to the performance of the current received beam.

[0410] ● (Alt1 New Received Beam) The terminal may report the L1-RSRP value of the new received beam with the best performance among the N new received beams by quantizing it into a total of 7 bits in 1 dB increments from -140 dBm to -44 dBm. Additionally, the terminal may express the performance of the remaining N-1 new received beams as a difference value from the performance of the new received beam having the largest L1-RSRP value (for example, it may mean a differential L1-RSRP value), and may quantize the differential L1-RSRP value in 2 dB increments into a total of 4 bits.

[0411] ● (Alt1 Current Received Beam and Index) The terminal may report to the base station including the index of the current received beam and / or the performance of the current received beam. In this case, the index of the current received beam may be the index of the CSI-RS resource if the current received beam is CSI-RS as described above, or the index of the SSB if the current received beam is SSB. The terminal may receive a setting from the base station via upper layer signaling as to whether to report to the base station including the index of the current received beam and / or the performance of the current received beam. For example, if the terminal receives an upper layer signaling setting from the base station, the terminal may report the performance of the received beam originating from the terminal including the index of the current received beam and / or the performance of the current received beam. If the terminal does not receive an upper layer signaling setting from the base station, the terminal may report the performance of the received beam originating from the terminal by including only the index of the new received beam and / or the performance value of the new received beam, without including the index of the current received beam and / or the performance of the current received beam.

[0412] ● (Alt1 Reporting only the current received beam) When the terminal reports to the base station including the performance of the current received beam (e.g., L1-RSRP performance), the terminal may express the L1-RSRP performance of the current received beam as a difference value from the performance of the newest received beam with the best performance (e.g., may mean a differential L1-RSRP value), and may quantize the differential L1-RSRP value in units of 2 dB into a total of 4 bits. Additionally, the terminal may report the L1-RSRP performance of the current received beam by quantizing values ​​in units of 1 dB from -140 dBm to -44 dBm into a total of 7 bits. Such reporting methods of the terminal are merely examples, and the present disclosure is not limited by the above examples.

[0413] ● (Method for Reporting Current Received Beam Index) When the terminal reports the index of the current received beam, it may report the index of the receiving beam having the Qth best performance according to the [Current Received Beam Determination Method 3] or [Current Received Beam Determination Method 4] described above. In this case, the terminal may report based on the bit length of the TCI state field within the DCI. For example, when considering the bit length of the TCI state field within the DCI, the terminal may consider all DCI formats among DCI formats 1_1, 1_2, and 1_3 that the terminal can set and monitor within the corresponding cell and the corresponding active downlink bandwidth portion. Additionally, the terminal may determine the bit length to be used when reporting the index of the current received beam in the receiving beam performance report originating from the terminal by using a combination of at least one of the following methods.

[0414] ■ If the terminal is configured to receive and monitor at least one combination of DCI format 1_1, 1_2, and 1_3, including DCI format 1_1, the terminal may report the index of the current receive beam in a receive beam performance report originating from the terminal by using the bit length of the TCI state field within DCI format 1_1, while ignoring the bit length of the TCI state field in other DCI formats. For example, the terminal may use 3 bits, which is the bit length of the TCI state field within DCI format 1_1. Thus, if the terminal determines that the Qth best reference signal is associated with the second active TCI state, the terminal may use 3 bits to report as "001" indicating the second active TCI state, where 1 can be the LSB (Least Significant Bit) or MSB (Most Significant Bit).

[0415] ■ If the terminal is configured to receive only DCI format 1_1 and DCI format 1_3 among DCI formats 1_1, 1_2, and 1_3, the terminal may report the index of the current receive beam in a receive beam performance report originating from the terminal using the largest bit length among the bit lengths of the TCI state fields in DCI formats 1_1 and 1_3. For example, if the bit length of the TCI state field in DCI format 1_1 is 4 and the bit length of the TCI state field in DCI format 1_3 is 4, the terminal may use 4 bits, which is the bit length of the TCI state field in DCI format 1_3.

[0416] ■ The terminal can report the index of the current receiving beam in a receiving beam performance report originating from the terminal by using a bit length capable of expressing the number of active TCI states in the TCI state field within DCI format 1_1 and 1_2. For example, if the terminal receives MAC-CE from the base station and receives TCI state information for 4 code points out of a total of 8 code points that can be represented by 3 bits in DCI format 1_1, the terminal can report the index of the current receiving beam in a receiving beam performance report originating from the terminal by considering the value 4, which is the number of active code points, without considering all 8 code points. For example, 2 bits may be sufficient in the above example, and if generalized to express this, if the number of active code points is A, the bit length required to report the index of the current receiving beam may be ceil(log2(A)), where ceil(.) and log2(.) may represent a ceiling function and a logarithmic function with base 2, respectively. At this time, whenever the terminal receives a TCI state activation MAC-CE transmitted by the base station, the bit length representing the index of the current receiving beam within the receiving beam performance report originating from the terminal may vary. Since the terminal and the base station recognize the MAC-CE activation time in the same way, the bit length representing the index of the current receiving beam may change from the activation time. The terminal can determine the bit length for the index of the current receiving beam within the receiving beam report originating from the terminal based on the number of TCI states included in the MAC-CE that activates the largest number of TCI states among the one or more MAC-CEs transmitted by the base station. For example, after the terminal receives a first MAC-CE indicating the activation of a total of four TCI states, and after the activation time of the MAC-CE, the terminal can determine the index of the current receiving beam using a total of two bits.After receiving a second MAC-CE that instructs the activation of a total of 8 TCI states, the terminal can determine the index of the current receiving beam using a total of 3 bits after the activation point. After receiving a third MAC-CE that instructs the activation of a total of 4 TCI states, the terminal can still determine the index of the current receiving beam using a total of 3 bits after the activation point.

[0417] ■ When [Event 3] is set, the terminal may expect that the bit length of the TCI state field in at least one of DCI formats 1_1, 1_2, or 1_3 is not zero. For example, the terminal may not expect that the bit length of the TCI state field in DCI formats 1_1, 1_2, or 1_3 is all zero. As for the upper layer signaling for this, the terminal may not expect that tci-PresentInDCI in ControlResourceSet, which is an upper layer signaling determining the existence of the TCI state field in DCI format 1_1; tci-PresentDCI-1-2-r16 in ControlResourceSet, which is an upper layer signaling determining the existence of the TCI state field in DCI format 1_2 and, if present, its bit length; and tci-ListDCI-1-3-r18 in MC-DCI-SetOfCells-r18, which is an upper layer signaling determining the existence of the TCI state field in DCI format 1_3 and, if present, its bit length, are all set to 0. Additionally, the terminal may expect that at least one of the above-described parameters is set.

[0418] ● (Method for reporting performance of current receiving beam + beams better than the Qth) The terminal may report not only the Qth best receiving beam among the reference signals associated with the QCL source set for each active TCI state determined based on the [Current Receiving Beam Determination Method 3] or [Current Receiving Beam Determination Method 4] described above, but also information on receiving beams better than the Qth (e.g., index or / and receiving performance (e.g., L1-RSRP)). This additional reporting behavior of the terminal may be configured by upper layer signaling settings that can be received from the base station. For example, if the base station sets a specific upper layer signaling that implies additional reporting on receiving beams with better performance than the current receiving beam, in addition to the upper layer signaling settings for reporting the current receiving beam index or / and current receiving beam performance described above, the terminal may also report information on receiving beams better than the Qth. For example, if a terminal reports terminal capability as Q=2 and is set to Q=2 by the base station, and the terminal is set to upper layer signaling for reporting the current receive beam index or / and current receive beam performance, and additionally is set to upper layer signaling for reporting the index or / and performance of a receive beam better than the Q-th, the terminal may report not only the index or / and performance of the reference signal associated with the QCL source in the active TCI state that has the best receive performance (e.g., L1-RSRP) at the Q=2nd level, but also the index or / and performance of the reference signal associated with the QCL source in the active TCI state that has the best receive performance (e.g., L1-RSRP) at the Q-1th level (e.g., 1st level).At this time, the terminal can report the performance of the reference signal associated with the QCL source in the active TCI state with the Qth best reception performance (e.g., L1-RSRP) based on the differential L1-RSRP, which can represent the difference value from the L1-RSRP of the new reception beam with the best performance in 2 dB intervals for a total of 4 bits as described above. In addition, regarding the performance of a reference signal associated with a QCL source in an active TCI state having better reception performance than the Qth, the terminal may report based on a differential L1-RSRP that can represent the difference value from the L1-RSRP of the new reception beam with the best performance in 2 dB increments in a total of 4 bits as described above (wherein, if the performance of the reception beam is better than the L1-RSRP performance of the new reception beam with the best performance, the terminal may report it together by including a 1 bit capable of expressing the code as a value of 1, and if the performance of the reception beam is lower than the L1-RSRP performance of the new reception beam with the best performance, the terminal may report it together by including a 1 bit capable of expressing the code as a value of 0), or quantize the L1-RSRP performance of each reception beam into a total of 7 bits in 1 dB increments from -140 dBm to -44 dBm. Through this, the base station can obtain information not only about the active TCI state with the Q-th best performance currently associated with the terminal, but also about TCI states with better performance than the Q-th. Therefore, the base station can continuously manage the performance of the top Q TCI states by modifying or updating the top Q TCI states, or by modifying or updating the lower TCI states excluding the top Q.

[0419] ● Alternatively, the terminal may measure the performance of reference signals associated with the QCL source configured within a total of A active TCI states, and then determine the active TCI states from the first best-performing reference signal to the Ath best-performing reference signal. Subsequently, after [Event 3] occurs, when the terminal includes information about new receiving beams in the receiving beam performance report initiated by the terminal, it may additionally report that the performance of each new receiving beam is better than the TCI state associated with a specific Xth best-performing reference signal. Such additional reporting can be performed based on upper-layer signaling that can be received from the base station. For example, when the terminal performs the receiving beam report initiated by the terminal after [Event 3] occurs, the terminal may include the performance of two new receiving beams in the report. Additionally, the terminal may additionally transmit to the base station, during the receiving beam performance report initiated by the terminal, information regarding which QCL source reference signal among all currently active TCI states the performance of each new receiving beam is better than. That is, the terminal may report the level of performance of the new beam compared to the performance of the QCL source reference signals for the currently active TCI state. For example, if a total of 8 TCI states are active for the terminal, the terminal may additionally report the number 3 in the performance of the new beam to indicate that the first best-performing new beam among the two new receiving beams is better than the third best-performing QCL source reference signal among each of the 8 currently active TCI states.In addition, the terminal may additionally report the number 5 along with the performance of the new receiving beam to indicate that the new receiving beam with the second best performance among the two new receiving beams has better performance than the fifth best QCL source reference signal among each QCL source reference signal within the eight currently active TCI states. At this time, the bit length representing the index of the current receiving beam described above may be used to express the number additionally reported to the new receiving beam.

[0420] ● Alternatively, the terminal may additionally report to the base station the number of times that, within a specific time interval, at least one new received beam had a performance higher than a specific reference value compared to the current received beam (the [Current Received Beam Determination Method 3] or [Current Received Beam Determination Method 4] described above). For example, the terminal may additionally report that within a specific time interval, the first new received beam had a performance higher than a specific reference value compared to the current received beam 2 times, and the second new received beam had a performance higher than a specific reference value compared to the current received beam 1 time. The number of times may have a defined maximum value, and based on the maximum value, a bit length capable of expressing information regarding the number of times may be determined within the received beam report originating from the terminal. For example, if the maximum value of the number of times is X, the bit length capable of expressing it may be determined as ceil(log2(X)), where ceil(.) and log2(.) may be a ceiling function and a logarithmic function with base 2, respectively. Such additional reporting may be possible by the terminal receiving specific upper-layer signaling from the base station.

[0421] - For [Event 3], the terminal can determine a method for determining a reference signal having the Qth best performance among reference signals set as QCL sources within one or more TCI states activated for the current receiving beam through at least one combination of the following items (e.g., the embodiment of FIG. 10).

[0422] FIG. 10 is a drawing illustrating an example of a method for determining the current receiving beam in [Event 3] according to one embodiment of the present disclosure.

[0423] The terminal can receive DCI from the base station (1000).

[0424] The terminal can schedule MAC-CE reception through DCI, and the MAC-CE can be included in PDSCH (1005). The MAC-CE can activate a total of 4 code points in the TCI state field within DCI (1010). The first code point may be TCI#1, which is set as the QCL source for reference signal RS#1; the second code point may be TCI#2, which is set as the QCL source for reference signal RS#2; the third code point may be TCI#3, which is set as the QCL source for reference signal RS#3; and the fourth code point may be TCI#4, which is set as the QCL source for reference signal RS#4.

[0425] The terminal can transmit a PUCCH containing HARQ-ACK information for receiving a PDSCH containing MAC-CE (1015).

[0426] After 3 ms from the time of HARQ-ACK transmission (1020), that is, from time t0 (1020), the terminal can apply the MAC-CE activation information. After that, the terminal can determine the current receiving beam while receiving each reference signal set as a QCL source in one or more newly activated TCI states.

[0427] If Q=2, the current receiving beam can be determined as the reference signal with the second best performance among the reference signals set as the QCL source in the activated TCI state, according to [Current receiving beam determination method 3] described above.

[0428] In one way, the terminal can determine which of the reference signals Q=2 among all reference signals associated with the activated TCI state is the current receiving beam from the time when the new TCI state activation is applied (i.e., from time t0 (1020)), when the terminal receives the reference signal with the best performance at time t1. Subsequently, if the terminal receives RS#1 (1025) at time t2, and if RS#1 is better than RS#2, the terminal can determine the current receiving beam as RS#2 and TCI#2 (i.e., as the reference signal with the second best performance at Q=2). Subsequently, the terminal can measure the performance of each RS at the reception locations of RS#3 (1035) and RS#4 (1040), and update the information of the current receiving beam (i.e., as the reference signal with the second best performance at Q=2) from RS#2 or maintain it as RS#2.

[0429] Alternatively, the terminal can determine which is the current receiving beam from the time when the new TCI state activation is applied (i.e., from time t0 (1020)) and from the time when all reference signals associated with the activated TCI state have been received at least once (i.e., from time t4 (1040)). For example, if the terminal receives RS#1 (1025) at time t1, it can determine RS#1 as the reference signal with the best performance at time t1. Subsequently, if the terminal receives RS#2 (1030) at time t2, and if RS#1 is better than RS#2, the terminal can determine RS#2 and TCI#2 as the current receiving beam (i.e., as the reference signal with Q=2nd best performance). Afterwards, the terminal measures the performance of each RS at the receiving positions of RS#3 (1035) and RS#4 (1040), and the terminal can determine that the receiving performance is good in the order of RS#3, RS#2, RS#4, RS#1, and through this, can determine RS#2 and TCI#2 as the current receiving beam (i.e., as a reference signal with Q=2nd best performance).

[0430] Alternatively, the terminal can determine the current receiving beam as the TCI state corresponding to Q=2nd best-performing reference signal by receiving an additional timer from the base station, from the time of new MAC-CE activation until the timer expires.

[0431] Using a method to determine the current receiving beam from a specific point in time in this way can implicitly set a timer to prevent frequent reports of the receiving beam originating from the terminal between the terminal and the base station. That is, if the terminal determines the current receiving beam determination time as time t2 (1030), the terminal and the base station can assume that no reports of the receiving beam originating from the terminal will occur between the terminal and the base station at least from the time of new MAC-CE activation application (i.e., time t0 (1020)), or from the time of HARQ-ACK transmission (1015) to time t2 (1030).

[0432] Among the methods described above, the method by which a terminal determines the current receiving beam for [Event 3] may be notified from a base station through a combination of at least one of upper layer signaling, MAC-CE signaling, and L1 signaling, or it may be assumed that a specific method fixed in the standard is followed for a terminal supporting [Event 3].

[0433] In determining whether [Event 3] has occurred, the terminal may consider single-event-based judgment and multiple-event-based judgment. The terminal may report the single-event-based judgment method as the basic [Event 3] judgment method through terminal capability, and the multiple-event-based judgment method can be used as the [Event 3] judgment method only if the terminal reports additional terminal capability. In the case of single-event-based judgment, the terminal can determine the performance of the new received beam and the current received beam by receiving the reference signal corresponding to the new received beam and the reference signal corresponding to the current received beam only once. When making a single-event-based judgment, the terminal can determine whether [Event 3] has occurred for each beam reception location (e.g., the reception location of the new received beam that exists thereafter, the location of the current received beam, or / and the reception location of the SSB that has a QCL relationship with the reference signal set in the QCL source within the activated TCI state or the reference signal set in the QCL source within the activated TCI state).

[0434] Regarding [Event 3], the terminal may introduce a specific time interval and a counter to determine whether the performance of a new received beam is higher than a specific threshold value compared to the performance of the current received beam. The terminal may determine whether [Event 3] has occurred within a time interval by using a time interval that starts based on the point in time when information about the current received beam is identified. At this time, the point in time when information about the current received beam is identified may be the point in time when the currently indicated TCI state is applied, or the point in time when a reference signal (CSI-RS or SSB, as described above) corresponding to the current received beam is received after the point in time when the currently indicated TCI state is applied. At this time, the length of the time interval may be the period value of the reference signal corresponding to the current received beam, or a real value frame, subframe, slot, symbol, or absolute time (e.g., msec) that is shorter or longer than that. The length of the time interval may be set by the terminal from the base station via upper layer signaling. The terminal may reset the time interval whenever it receives the reference signal corresponding to the current received beam, or at the point when the time interval ends. During the time interval, the terminal may receive each reference signal (e.g., CSI-RS or SSB) corresponding to one or more new received beams. If [Event 3] occurs for a specific new received beam more than a certain number of times within the time interval, the terminal may report the received beam performance to the base station. Additionally, the terminal may store the number of times [Event 3] occurs consecutively within the time interval, starting from the beginning of the time interval, in the counter described above. If the terminal confirms that the value of the counter is greater than a certain number, the terminal may report the received beam performance to the base station. In this case, the number of times [Event 3] occurs consecutively may mean that the performance of a specific new received beam is higher than a certain reference value compared to the current received beam.For example, if the performance of each of two different new receiving beams is higher than a specific threshold value compared to the current receiving beam, the terminal may consider that [Event 3] has occurred once for each new receiving beam. Within the corresponding time interval, the terminal can check whether [Event 3] has occurred for each period of the current receiving beam. If [Event 3] has occurred continuously within the time interval but has not yet occurred more than a specific number of times, and [Event 3] does not occur during a specific period of the current receiving beam, resulting in the number of consecutive occurrences of [Event 3] not exceeding the specific number, the terminal may reset the last point of the specific period of the current receiving beam to the starting point of the said time interval. In this way, the terminal can check the number of times [Event 3] occurs continuously within the specific time interval and report the receiving beam performance originating from the terminal to the base station. At this time, the specific number may be 1 by default, and the terminal may receive a specific natural number X greater than 1 from the base station. In one embodiment, the terminal may report a terminal capability to the base station that includes the meaning that the specific number is considered as 1 or as a specific natural number X greater than 1. Subsequently, the base station may set the specific number to the terminal based on the terminal capability received from the terminal. Accordingly, the terminal may ultimately determine the specific number based on the setting received from the base station. In another embodiment, the terminal may report a terminal capability to the base station that includes the meaning that the specific number is considered as 1 or as a specific natural number X greater than 1. And the base station that receives the terminal capability may determine or use the value reported by the terminal as the specific number value as is, without additional upper layer signaling settings for the terminal.

[0435] At least one combination of the above [Event 1], [Event 2], and [Event 3] may be used when reporting the received beam performance originating from the terminal. For example, the terminal may report the received beam performance originating from the terminal to the base station in consideration of [Event 1]. As another example, the terminal may receive upper-layer signaling for the report of the received beam performance originating from the terminal for [Event 1] and [Event 2], respectively, and may report the received beam performance by individually verifying [Event 1] and [Event 2]. When [Event 1] occurs, the terminal may report the received beam performance originating from the terminal corresponding to it. When [Event 2] occurs, the terminal may report the received beam performance originating from the terminal corresponding to it. When [Event 1] and [Event 2] occur simultaneously, the terminal may report the receiving beam performance starting from the terminal corresponding to [Event 1] and [Event 2], respectively, select only one of the two, or report the receiving beam performance related to the event with higher priority.

[0436] The terminal may perform a terminal capability report to the base station indicating that it is capable of supporting at least one combination of [Event 1], [Event 2], and [Event 3]. For example, the terminal may report to the base station via terminal capability that it is capable of supporting a receive beam performance report originating from the terminal for [Event 1]. For example, the terminal may report to the base station via terminal capability that it is capable of supporting a receive beam performance report originating from the terminal for [Event 2]. For example, the terminal may report to the base station via terminal capability that it is capable of supporting a receive beam performance report originating from the terminal for [Event 1] and [Event 2].

[0437] Regarding the aforementioned [Event 1], [Event 2], and [Event 3], the terminal may define a timer that does not monitor the occurrence of a specific event. As an example, if beam switching occurs from the base station, the terminal may not monitor the specific event defined in [Event 1] through [Event 3] for a certain period of time from that point in time. As another example, after the specific event defined in [Event 1] through [Event 3] occurs, the terminal may not monitor the specific event defined in [Event 1] through [Event 3] for a certain period of time from that point in time. By doing so, frequent information exchange and beam switching between the terminal and the base station can be prevented by preventing channel status information reports initiated by the terminal for a certain period of time after the base station has set or instructed beam switching.

[0438] The terminal may monitor only one of the aforementioned [Event 1], [Event 2], and [Event 3] and perform a channel status information report initiated by the terminal if the event occurs. Alternatively, the terminal may independently monitor one or more specific events and perform a channel status information report initiated by the terminal corresponding to each event. Alternatively, the terminal may monitor one or more specific events individually, but if one or more events occur simultaneously, it may perform a channel status information report initiated by the terminal corresponding to the event with the highest priority among them. In each of the above cases, the terminal may apply the timer individually or apply it commonly. If the terminal monitors one or more events, applying the timer commonly means applying the timer that is to be applied when a specific event occurs to other events in the same way.

[0439] In one embodiment of the present disclosure, a CSI reporting method initiated by a terminal is described. This embodiment may operate in combination with other embodiments.

[0440] The terminal may transmit information related to reception beam performance to the base station by performing a channel state information report initiated by the terminal after the aforementioned specific event occurs for the purpose of reporting channel state information initiated by the terminal. At this time, the terminal may perform a channel state information report initiated by the terminal by considering a combination of at least one of the following methods.

[0441] [Method 1-1]

[0442] The terminal may receive a PUCCH resource configured to request the allocation of a PUSCH resource that can be transmitted to the base station, including a report on the reception beam performance originating from the terminal. When a specific event according to any one or more combinations of [Event 1] to [Event 3] described above occurs from the terminal, the terminal may transmit a PUCCH (or PUSCH resource allocation request information, or a scheduling request) to the base station on the corresponding PUCCH resource. At this time, the terminal may receive a PUCCH resource configured as an upper layer signaling from the base station for reporting on the reception beam performance originating from the terminal, and this may be configuration information separate from the PUCCH resource for a conventional uplink data scheduling request. Such a PUCCH resource may include 1 bit of information.

[0443] Additionally, the terminal may receive a PUCCH resource configured to simultaneously request at least one combination of a request for PUSCH resource allocation that can be transmitted to the base station, including a reception beam performance report originating from the terminal, and an uplink data scheduling request, and 2 bits of information may be transmitted in the said PUCCH resource. If the said PUCCH resource has an information bit of "01", the said PUCCH resource may represent a conventional uplink data scheduling request; if it is "10", the said PUCCH resource may trigger a request for PUSCH resource allocation that can be transmitted to the base station, including the reception beam performance report originating from the terminal described above; and if it is "11", the said PUCCH resource may trigger both an uplink data scheduling request and a request for PUSCH resource allocation that can be transmitted to the base station, including a reception beam performance report originating from the terminal. If a base station receives a corresponding PUCCH resource from a terminal having an information bit of "11", the base station may transmit a DCI to the terminal to compel it to include all of the following within the DCI: PUCCH scheduling information, PUCCH scheduling information for a receive beam performance report originating from the terminal, and information instructing the terminal to include the receive beam performance report originating from the terminal within the corresponding PUCCH. In this case, the DCI may also schedule a PUCCH that includes both uplink data and a receive beam performance report. Such technology is merely an example, and the present disclosure is not limited by the above example.

[0444] At this time, the terminal may receive a slot-unit period and offset for a PUCCH resource that can simultaneously request at least one combination of a receive beam performance report originating from the terminal and uplink data scheduling, or a PUCCH resource that can simultaneously request at least one combination of a receive beam performance report originating from the terminal and uplink data scheduling, and the terminal may transmit the information described above on the PUCCH resource at the nearest period after a specific time offset from the time of occurrence of the specific event when the specific event occurs. The information described above may be referred to as a scheduling request, but such a designation is merely an example and does not limit the scope of the present invention. At this time, the specific time offset may be defined in slots or in milliseconds and may include 0 among possible values ​​(i.e., a specific time offset may not be required). This time offset may be defined by the terminal capability and reported by the terminal to the base station, notified by the base station through at least one combination of upper layer signaling, MAC-CE signaling, and L1 signaling, or defined through at least one combination of methods fixedly defined in the specification.

[0445] FIG. 11 is a diagram illustrating an example of the operation process of a terminal and a base station for a CSI report initiated by a terminal using a PUCCH resource that triggers a reception beam performance report initiated by a terminal according to one embodiment of the present disclosure.

[0446] A terminal (1101) can receive a set of periodic channel measurement reference signals through upper layer signaling from a base station (1102), and can measure reception beam performance by periodically receiving the periodic channel measurement reference signals (1105). Subsequently, if a specific event occurs at the terminal (1110), the terminal can transmit a signal to the base station on a PUCCH resource that triggers a reception beam performance report originating from the terminal (1115). The specific event may correspond to at least one of the events 1 to 3 described above. The PUCCH resource may be a PUCCH resource separate from the PUCCH resource for uplink data scheduling requests as described above, or it may be a PUCCH resource for requesting at least one combination of an uplink data scheduling request and a reception beam performance report request originating from the terminal to the base station. In response, the base station may transmit a PDCCH to the terminal that triggers a received beam performance report initiated by the terminal (or schedules a PUSCH to transmit the received beam performance report) (1120), and in response, the terminal may calculate a UCI based on a request for a received beam performance report initiated by the terminal and transmit it to the base station, including it in a PUSCH scheduled by the PDCCH (1125). Subsequently, if the base station determines that beam switching is required by the terminal (1130), it may set or instruct the terminal to perform beam switching (1135). The above-described flowchart illustrates an exemplary method that can be implemented according to the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart in this specification. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0447] When considering the aforementioned [Method 1-1], the process of channel state information reporting initiated by the terminal may be relatively long, so there may be insufficient gain in terms of latency. However, as described above, according to conventional standards, the base station must transmit non-periodic channel state information reporting triggering to the terminal based on indirect information; therefore, even though a non-periodic channel state information reporting method exists, it may not be fully utilized. Thus, when the terminal first performs the receive beam performance reporting triggering initiated by the terminal in this manner, there can clearly be a gain in terms of latency compared to the conventional method. Additionally, since the receive beam performance reporting triggering is transmitted to the base station via a single PUCCH resource along with the uplink data scheduling request, there may be a gain in terms of signaling overhead. Furthermore, since the receive beam performance reporting initiated by the corresponding terminal is transmitted via PUSCH in this method, various maximum lengths of UCI can be transmitted from the terminal to the base station; thus, the range of information exchanged between the terminal and the base station can be applied to various methods, ranging from a small number of bits to a large amount of information.

[0448] [Method 1-2]

[0449] The terminal may receive from the base station a pair of reserved PUCCH resources and PUSCH transmissions for reporting channel state information originating from the terminal. At this time, the terminal may generate channel state information originating from the terminal in the form of UCI or MAC-CE, include it in the PUSCH, and transmit it to the base station. The terminal may receive slot-unit periods and offsets for the PUCCH resources and PUSCH transmissions, and may receive PUSCH transmission-related parameters such as the time offset between the PUCCH resources and PUCCH transmissions, time and frequency resource allocation information for the PUSCH transmissions, MCS (e.g., the lowest value), the number of MIMO layers (e.g., 1), DMRS ports (e.g., 0), and waveforms (e.g., CP-OFDM). The PUSCH transmission-related parameters may be set to, for example, upper layer signaling, or a combination of upper layer signaling and L1 signaling.

[0450] Alternatively, the terminal may receive slot-unit period and offset settings for the PUCCH resource, and for PUSCH transmission, assuming a Type 1 configured grant-based PUSCH transmission, may receive upper-layer signaling related to the Configured grant Type 1 PUSCH transmission; and instead of transmitting PUSCH in every period, the terminal may transmit PUSCH in that period only when a signal was transmitted from the PUCCH resource prior to the PUSCH transmission period. The PUCCH resource may be configured with upper-layer signaling. Additionally, when the specific event occurs, the terminal may transmit a signal from the PUCCH resource of the period closest after a specific time offset from the time of the specific event. In this case, the specific time offset may be defined in slots or milliseconds and may include 0 among possible values ​​(i.e., a specific time offset may not be required). This time offset may be defined by terminal capability, reported by the terminal to the base station, notified by the base station through at least one combination of upper layer signaling, MAC-CE signaling, and L1 signaling, or defined through at least one combination of methods fixedly defined in the standard.

[0451] FIG. 12 is a diagram illustrating an example of the operation of a terminal and a base station for a CSI report initiated by a terminal using a pair of reserved PUCCH resources and PUSCH transmissions according to one embodiment of the present disclosure.

[0452] A terminal (1201) may receive a set of periodic channel measurement reference signals through upper layer signaling from a base station (1202) and may measure reception beam performance by periodically receiving the periodic channel measurement reference signals (1205). Subsequently, if a specific event occurs at the terminal (1210) (the specific event may correspond to at least one of the events 1 to 3 described above), the terminal may transmit a signal to the base station on the PUCCH resource (1215). Subsequently, the terminal may perform a PUSCH transmission after a time offset between the PUCCH resource set for the terminal and the PUSCH transmission (1220), and the PUSCH may include a UCI or MAC-CE containing a channel state information report initiated by the terminal. Subsequently, if the base station determines that beam switching is required for the terminal (1225), it may set or instruct the terminal to do so (1230). The above-described flowchart illustrates an exemplary method that can be implemented according to the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart in this specification. For example, although depicted as a series of steps, the various steps in each drawing may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0453] When considering the above-described [Method 1-2], the process of reporting channel status information starting from the terminal can be relatively short, so there may be an advantage in terms of latency. However, the terminal requires reserved PUCCH resources and PUSCH transmission resources, and if at least one of the two channels, PUCCH and PUSCH, is incorrect during blind decoding at the base station, the base station may fail to decode the reception beam performance report that the terminal intended to transmit, and in order to properly receive it, it may have to perform decoding again for the PUCCH and PUSCH that are subsequently transmitted from the terminal.

[0454] The terminal may be notified by the base station to perform at least one combination of [Method 1-1] or [Method 1-2] through at least one combination of upper layer signaling, MAC-CE signaling, and L1 signaling, or may expect that at least one combination of [Method 1-1] or [Method 1-2] is fixedly defined in the standard. Additionally, if the terminal is notified by the base station of a combination of at least one specific method through at least one combination of upper layer signaling, MAC-CE signaling, and L1 signaling, it may mean that the terminal cannot support one or more other specific combinations of methods. For example, the terminal may expect that [Method 1-2] is fixedly defined in the standard regarding the method and process of reporting channel state information originating from the terminal described above. As another example, the terminal may be notified of the above [Method 1-1] by a combination of at least one of upper layer signaling, MAC-CE signaling, and L1 signaling from a base station, and in this case, the terminal may be deemed to have been notified by the base station that the above [Method 1-2] is not supported.

[0455] The terminal may report to the base station, as a terminal capability, whether it is possible to support at least one combination of [Method 1-1] or [Method 1-2]. In this case, if the terminal reports to the base station, as a terminal capability, that a combination of one or more specific methods is possible, it may be considered that the terminal has reported that it is not possible to support one or more other specific combinations of methods. For example, the terminal may report to the base station whether it is possible to support [Method 1-1] or [Method 1-2]. As another example, the terminal may report to the base station that it is possible to support [Method 1-1], and such terminal capability reporting may mean that the terminal is not possible to support [Method 1-2].

[0456] Although the above-described [Method 1-1] or [Method 1-2] both consider periodic channel status information reporting as a conventional channel status information reporting method, Method 1-1 or Method 1-2 can also be used for semi-continuous channel status information reporting or / and non-periodic channel status information reporting for channel status information reporting originating from a terminal, and in the case of channel measurement reference signals for this, not only periodic reference signals but also semi-continuous and non-periodic reference signals can be considered.

[0457] For the above-described [Method 1-1] or [Method 1-2], the terminal may define an arbitrary timer and, after performing a channel state information report initiated by the terminal according to each method, not perform a channel state information report initiated by the terminal for a certain period of time. Through this, frequent channel state information reporting from the terminal can be prevented, and in the case of a method requiring blind decoding at the base station, blind decoding can be prevented from being performed for a certain period of time.

[0458] [Method for setting up multiple events]

[0459] The terminal can perform a received beam performance report initiated from the terminal based on the above [Event 1], [Event 2], or / and [Event 3] from the base station.

[0460] - In one way, the terminal may receive upper layer signaling from a base station to perform a receiving beam performance report initiated by the terminal for only one of the above [Event 1], [Event 2], or / and [Event 3], and the said upper layer signaling setting may have setting units by bandwidth portion, by serving cell, by cell group, and by terminal. For example, if the terminal receives setting information from a base station to perform a receiving beam performance report initiated by the terminal for only one event through the upper layer signaling setting unit by serving cell, the terminal may perform a receiving beam performance report initiated by the terminal for a specific event (e.g., one of the above [Event 1], [Event 2], [Event 3]) in a first serving cell, and may perform a receiving beam performance report initiated by the terminal for a specific event (e.g., one of the above [Event 1], [Event 2], [Event 3]) in a second serving cell. The terminal may not be restricted in the type of event corresponding to the receiving beam performance report originating from the terminal set in the first serving cell and the second serving cell (i.e., the terminal may receive receiving beam performance report settings originating from the terminal corresponding to the same or different events for each different serving cell), or may be expected to receive only receiving beam performance report settings originating from the terminal for the same type of event (i.e., if a corresponding setting exists for each unit of receiving beam performance report settings originating from the terminal, the type of event corresponding to that setting is restricted to be the same as one).

[0461] - Alternatively, the terminal may receive upper layer signaling related to a receive beam performance report originating from a terminal corresponding to each of one or more of [Event 1], [Event 2], or / and [Event 3] from a base station for specific upper layer signaling setting units. The upper layer signaling setting units may be by bandwidth portion, by serving cell, by cell group, or by terminal. For example, if the terminal has upper layer signaling setting units for each serving cell, and receives upper layer signaling settings from a base station such that a receive beam performance report setting originating from a first terminal in a specific serving cell corresponds to [Event 1] and a receive beam performance report setting originating from a second terminal corresponds to [Event 2], the terminal may perform a receive beam performance report originating from a terminal corresponding to [Event 1] and [Event 2], respectively, in the corresponding serving cell.

[0462] - Alternatively, the terminal may receive upper layer signaling related to a receive beam performance report originating from the terminal corresponding to at least one combination of [Event 1], [Event 2], or / and [Event 3] from the base station for each specific upper layer signaling setting unit. The upper layer signaling setting unit may be by bandwidth portion, by serving cell, by cell group, or by terminal. For example, if the terminal has upper layer signaling setting units by serving cell, and the receive beam performance report setting originating from the first terminal in a specific serving cell receives an upper layer signaling setting from the base station corresponding to an event in which [Event 1] and [Event 2] are combined, the terminal may perform a receive beam performance report originating from the terminal corresponding to the event in which [Event 1] and [Event 2] are combined in that serving cell.

[0463] In the case where one or more of the methods described above are set for a terminal, the terminal may expect that each of the one or more events is a different event, or that each of the one or more events is the same or different event. For example, if the terminal receives upper-layer signaling related to receiving beam performance reporting originating from the terminal for two events, the terminal may expect that the two events are different events (for example, the first event may be set as [Event 1] and the second event as [Event 2]). Or the terminal may expect that the two events are the same event (for example, if the terminal receives upper-layer signaling related to receiving beam performance reporting originating from two terminals, the event corresponding to each setting may be the same as [Event 1]).

[0464] According to the methods described above, the terminal may receive upper layer signaling regarding a reception beam performance report originating from the terminal corresponding to one or more events from the base station according to a combination of at least one of the following methods.

[0465] [Method 2-1]

[0466] The terminal may receive upper-layer signaling from the base station, respectively, regarding a reception beam performance report originating from the terminal corresponding to one or more events. That is, the terminal may individually receive upper-layer signaling from the base station, respectively, regarding one or more reception beam performance reports originating from the terminal. For example, if the terminal receives a first reception beam performance report setting originating from the terminal and a second reception beam performance report setting originating from the terminal, respectively, corresponding to two different events, the upper-layer signaling setting related to the first reception beam performance report originating from the terminal may include at least one combination of the following items.

[0467] - 1st CSI Report Settings

[0468] - A first reporting method (in which one of the above [Method 1-1] and [Method 1-2] may be established)

[0469] - The first event (in which one of the above [Event 1], [Event 2], and [Event 3] can be established)

[0470] - The first PUCCH resource (for the first step of [Method 1-1] and [Method 1-2] above)

[0471] - (Case corresponding to [Method 1-2] above) 1st PUSCH resource

[0472] - 1st new receiving beam set

[0473] - Reporting status of 1st current receiving beam performance

[0474] In addition, at least one combination of the following items may be included within the upper layer signaling settings related to the second receiving beam performance report originating from the terminal.

[0475] - 2nd CSI Report Settings

[0476] - A second reporting method (in which one of the above [Method 1-1] and [Method 1-2] may be established)

[0477] - The second event (in which one of the above [Event 1], [Event 2], and [Event 3] can be established)

[0478] - Second PUCCH resource (for the first step of [Method 1-1] and [Method 1-2] above)

[0479] - (Where the above second reporting method corresponds to the above [Method 1-2]) second PUSCH resource

[0480] - Second new receiving beam set

[0481] - Whether to report 2nd current receiving beam performance

[0482] As described above, the terminal can individually receive upper layer signaling related to receiving beam performance reporting originating from each terminal corresponding to a plurality of events. Based on this, the terminal can perform receiving beam performance reporting operations originating from the terminal for each event, as mentioned in [Event 1], [Event 2], [Event 3], and [Method 1-1], [Method 1-2].

[0483] The terminal may be notified of the priority of different events from the base station through a combination of at least one of upper layer signaling, MAC-CE signaling, and L1 signaling, or may follow rules fixedly defined in the standard. For example, the terminal may be configured from the base station via upper layer signaling regarding which event has a higher priority, which may be configured through upper layer signaling parameters that implicitly indicate priority, or the priority may be determined according to the index value of the CSI-ReportConfig corresponding to each event after implicitly defining that a lower index value of CSI-ReportConfig has a higher or lower priority. As another example, the terminal may consider [Event 1] to have a higher priority than [Event 2] and [Event 3], and [Event 2] to have a higher priority than [Event 3], according to a method fixedly defined in the standard.

[0484] Depending on the level of priority, when a receiving beam performance report operation originating from a terminal corresponding to each event occurs, if there is an overlap between channels transmitted from the terminal or the base station, the terminal may transmit the channel corresponding to the higher priority event and not transmit the channel corresponding to the lower priority event. Alternatively, when setting up upper-layer signaling related to receiving beam performance reports originating from terminals corresponding to the different events, if some channel settings are shared for the different events and transmission of the shared channel occurs simultaneously for both events, the terminal may prioritize transmitting the receiving beam performance report corresponding to the higher priority event to the base station.

[0485] If the terminal receives each upper layer signaling related to a received beam performance report originating from the terminal for one or more events, and the received beam performance report originating from the terminal for each event operates based on [Method 1-1] and / or [Method 1-2], the terminal may individually receive a PUCCH resource, which is the first resource used after the event occurs, for each event according to [Method 2-1]. In this case, if the first PUCCH resource for each event (after a specific time offset after the event occurs) overlaps with time and / or frequency resources, the terminal may not transmit a signal on the first PUCCH resource for a specific event with lower priority, but transmit a signal on the first PUCCH resource for a specific event with higher priority. In this case, the priority may be notified through a combination of at least one of upper layer signaling, MAC-CE signaling, and L1 signaling from the base station as described above, or may follow a fixed rule defined in the standard.

[0486] If a terminal receives each upper layer signaling related to a receive beam performance report originating from the terminal for one or more events, and all receive beam performance reports originating from the terminal for each event operate based on [Method 1-1] above, the terminal may receive a receive beam performance report triggered from the base station through the CSI request field in DCI format 0_1, 0_2, or 0_3, and the triggered receive beam performance report may be multiplexed within a PUSCH transmission resource scheduled in the same DCI format and transmitted to the base station.

[0487] At this time, when a code point of the CSI request field within DCI format 0_1, 0_2, or 0_3 is configured, the terminal can expect that a CSI-ReportConfig corresponding to one event is configured within a single code point. Through this, the terminal can perform a receive beam performance report originating from a single terminal through a single DCI, and can expect that information regarding the receive beam performance report of the same bit length is always multiplexed within a PUSCH scheduled through the same DCI. Through this, the terminal can receive only the receive beam report trigger corresponding to the first PUCCH transmitted by the terminal from the base station, and if the base station does not trigger the receive beam report corresponding to the first PUCCH transmitted by the terminal, the terminal can determine that the base station did not receive the terminal's first PUCCH transmission. The base station can select one receive beam performance report corresponding to information received from the terminal among one or more different first PUCCHs corresponding to each of one or more events that the terminal can transmit, and trigger the receive beam performance report to the terminal through the code point of the CSI request field in the DCI containing the information.

[0488] Alternatively, when a code point in the CSI request field within DCI format 0_1, 0_2, or 0_3 is configured, the terminal can expect that a CSI-ReportConfig corresponding to one or more events is configured within a single code point. Through this, the terminal can perform receive beam performance reporting originating from one or more terminals through a single DCI, and can expect that information regarding one or more receive beam performance reports is multiplexed within a PUSCH scheduled through the same DCI. Thus, if the terminal transmits a first PUCCH corresponding to each of one or more events to the base station and the base station receives signals on both PUCCH resources, the base station can simultaneously trigger a receive beam report for the one or more events to the terminal through the code point in the CSI request field within the DCI. That is, the terminal can expect that a specific code point in the CSI request field within the DCI contains (or corresponds to) a receive beam report configuration originating from one or more terminals.

[0489] In both of the above methods, if a terminal contains a CSI-ReportConfig setting related to a receiving beam report originating from at least one terminal in a code point of a CSI request field within the DCI, the terminal can expect that a CSI-ReportConfig setting not related to a receiving beam report originating from the terminal is not included (or does not correspond) in that code point.

[0490] If the terminal receives each upper layer signaling related to a receive beam performance report originating from the terminal for one or more events, and all receive beam performance reports originating from the terminal for each event operate based on [Method 1-2] above, the terminal may individually configure a first PUCCH resource and a second PUSCH resource based on a configured grant for each event according to [Method 2-1]. In the above, the first PUCCH resource may be a PUCCH resource that is used first for each event (after a specific time offset after the event occurs), and the second PUSCH resource may correspond to a PUSCH resource to which a receive beam performance report originating from the terminal corresponding to the PUCCH resource is transported.

[0491] - In this case, if the first PUCCH resource of a specific event and the second PUCCH resource of another specific event overlap in time or / and frequency resources,

[0492] ● The terminal may transmit the first PUCCH resource and not transmit the second PUCCH resource.

[0493] ● The terminal may transmit the second PUSCH resource and not transmit the first PUCCH resource.

[0494] ● The terminal transmits the channel corresponding to the event with the highest priority according to the priority for each event described above, and does not transmit the rest. For example, if the first PUCCH resource corresponds to [Event 1] and the second PUSCH resource corresponds to [Event 2], and [Event 1] has a higher priority than [Event 2], the terminal transmits the first PUCCH resource and does not transmit the second PUSCH resource, and can transmit including the received beam report information at the next transmission location.

[0495] ● The terminal can multiplex and transmit the information of the first PUCCH resource onto the second PUCCH resource of the other specific event.

[0496] - As another example, if there is an overlap in time or / and frequency resources between second PUSCH resources corresponding to one or more events, the terminal may not transmit all of the one or more overlapping second PUSCH resources except for the one with the highest priority, or it may multiplex the received beam report information contained in the remaining second PUSCH resources excluding the PUSCH resource with the highest priority and transmit it to the base station.

[0497] [Method 2-2]

[0498] A terminal may receive upper layer signaling regarding a receive beam performance report originating from a terminal corresponding to one or more events from a base station, and if all receive beam performance reports originating from a terminal for each event operate based on [Method 1-2] above, some of these may be set commonly for all events. As an example, the terminal may receive a first PUCCH resource for all of the one or more events commonly from the base station.

[0499] As an example, a terminal may receive the first PUCCH resource among the upper-layer signaling for a receive beam performance report originating from a terminal corresponding to one or more events, which is set commonly for all events. The base station may set the information reported differently for each event, or set at least one resource among time, frequency, CS, and orthogonal sequence differently for each event, so that the terminal can report that a specific event has occurred. For example, to report to the base station that a specific event has occurred, the terminal may receive upper-layer signaling to have an additional transmission symbol position for a PUCCH resource having a periodic transmission position. For example, the terminal may consider the number of transmitted symbols of the corresponding PUCCH resource to be two, and when a specific event (e.g., [Event 1]) occurs, the terminal may transmit the PUCCH only at the first symbol location to instruct the base station to consider that [Event 1] has occurred, and when another event (e.g., [Event 2]) occurs, the terminal may transmit the PUCCH only at the second symbol location to instruct the base station to consider that [Event 2] has occurred. Additionally, the terminal may receive the period and slot offset values ​​of the corresponding PUCCH resource through conventional parameters, and may receive an additional second slot offset value through upper layer signaling, and each slot offset may be considered to correspond to each event. Therefore, when one of multiple events occurs, the terminal may transmit the first PUCCH resource to the base station at the slot offset location corresponding to the event to instruct the base station to distinguish which event has occurred. Alternatively, the terminal may receive additional frequency resources for the first PUCCH resource through upper-layer signaling, and said additional frequency resources may be set for each event.Based on this, the base station can determine whether an event has occurred at the terminal depending on which frequency resource transmits the PUCCH resource.

[0500] As another example, a terminal may individually set the first PUCCH resource among the upper layer signaling for a receive beam performance report originating from a terminal corresponding to one or more events, and set the second PUSCH resource in common for all events. Accordingly, the base station can determine which event has occurred at the terminal by checking which first PUCCH resource the terminal transmits, and the terminal can transmit the receive beam report information corresponding to the first PUCCH resource by including it in the second PUSCH resource.

[0501] Alternatively, the terminal may receive a first PUCCH resource commonly configured for one or more events, and for the remaining upper layer signaling for each event (e.g., an index of the event, upper layer signaling indicating whether the performance of the current receiving beam is included when reporting the receiving beam, and a second PUSCH resource based on a Type-1 configured grant in accordance with [Method 1-2] above), it may receive individual CSI-ReportConfigs corresponding to each event from the base station. For example, the terminal may receive a first PUCCH resource with PUCCH resource ID 1 commonly configured for the first event and the second event, and may receive a first CSI-ReportConfig corresponding to the first event and a second CSI-ReportConfig corresponding to the second event from the base station. The terminal can report that an event has occurred at the terminal by transmitting a signal at the transmission location of the first PUCCH resource regarding the most recent event among one or more events that occurred prior to a specific time interval earlier from each periodic transmission location of the first PUCCH resource (e.g., time T1), a time point earlier by the number of OFDM symbols T_s prior to time T1, a time point earlier by the number of slots T_s prior, or a time point earlier by T_s seconds prior), the first event that occurred (in the time interval in which reporting of the event is performed at time T1), or an event of high priority, etc. Since the base station cannot confirm what event has occurred at the terminal solely through the transmission of this first PUCCH resource, when the terminal reports to the base station by generating a receive beam report format originating from the terminal within the second PUCCH resource provided to the terminal thereafter, the terminal can perform a receive beam report for a single event that includes information about what event has occurred.At this time, the terminal may include an index of an event or an index of a CSI-ReportConfig within the received beam report format. Additionally, the terminal may represent each event or each CSI-ReportConfig by using a number of bits capable of representing the number of CSI-ReportConfigs corresponding to each of one or more events corresponding to the first PUCCH resource (i.e., the number of different events or different CSI-ReportConfigs connected to the first PUCCH resource). Furthermore, if the lengths of the received beam report formats for one or more events corresponding to the first PUCCH resource are different, the terminal transmits information of the format corresponding to the longest bit length among the one or more received beam report formats into the second PUCCH resource, and if the event reported by the terminal has a bit length shorter than the format corresponding to the longest bit length, the remaining bit length may be padded with zeros (zero padding). When a terminal performs a receive beam performance report initiated by the terminal based on [Method 1-1] above, the terminal may expect that multiple CSI-ReportConfigs sharing the first PUCCH resource correspond to a specific code point in the code point of the CSI request field within the DCI, and may not expect any other CSI-ReportConfigs to be included. If the terminal shares the first PUCCH resource for one or more events as described above, when the terminal operates according to [Method 1-2] above, the terminal may use the Type-1 configured grant-based second PUCCH resource in common for one or more of the events described above.It can be expected that CSI-ReportConfigs corresponding to one or more events connected to the aforementioned PUCCH resource will all be configured in the same serving cell.

[0502] [Method 2-3]

[0503] A terminal may receive upper layer signaling regarding a receive beam performance report originating from a terminal corresponding to one or more events from a base station, and if all receive beam performance reports originating from a terminal for each event operate based on [Method 1-2] above, some of these may be commonly set for all events. As an example, a terminal may receive a second PUSCH resource based on a Type-1 configured grant from a base station commonly for all of the one or more events.

[0504] For example, two events configured for a terminal share upper-layer signaling related to a Type-1 configured grant-based second PUSCH resource, and the transmission location of said second PUSCH may occur periodically. Among the transmission locations of said periodic Type-1 configured grant-based second PUSCH resource, the terminal may transmit the second PUSCH only if an event occurred from the terminal prior to a specific transmission location and the first PUSCH resource was transmitted. Otherwise, if the terminal did not transmit the first PUSCH resource corresponding to that event because a specific event did not occur from the terminal prior to a specific transmission location among the transmission locations of said second PUSCH resource and the terminal did not transmit the first PUSCH resource corresponding to that event, the terminal may not transmit the second PUSCH at that specific transmission location.

[0505] FIGS. 13 to 16 are drawings illustrating a receiving beam reporting operation process initiated from a terminal when a second PUSCH resource is shared among upper layer signaling for one or more events according to one embodiment of the present disclosure.

[0506] FIGS. 13, 14, and 15 represent a case assuming that a Type-1 configured grant-based second PUSCH resource includes a receive beam report originating from a terminal for one event, and FIG. 16 represents a case assuming that a Type-1 configured grant-based second PUSCH resource includes a receive beam report originating from a terminal for one or more events. In FIGS. 13 to 16, the first PUCCH resource may be a PUCCH resource that is used first (after a specific time offset after the event occurs) configured for each event or commonly for the events, and the second PUSCH resource may correspond to a PUSCH resource to which a receive beam performance report originating from a terminal corresponding to the said PUCCH resource is transported.

[0507] FIG. 13 is a diagram illustrating a receiving beam reporting operation process initiated from a terminal when a second PUSCH resource is shared among upper layer signaling for one or more events according to one embodiment of the present disclosure.

[0508] In FIG. 13, the terminal (1301) may transmit a first PUCCH resource (1310) corresponding to the occurrence of the event to the base station to notify the base station of the occurrence of the event when a specific event (e.g., [Event 1]) among one or more events set for the terminal occurs (1303). Subsequently, the terminal may transmit a first PUCCH resource (1315) corresponding to the occurrence of the event to the base station to notify the base station of the occurrence of the event when another specific event (e.g., [Event 2]) among one or more events set for the terminal occurs (1304).

[0509] If the terminal transmits the first PUCCH resource corresponding to each event (1310, 1315) when both events set in the terminal occur (1303, 1304) before a specific time from the n-th transmission position (1320) of the second PUCCH resource, the terminal may include the reception beam report information for the event that occurred earlier in time (e.g., [Event 1]) in the PUCCH transmission at the n-th transmission position (1320) of the second PUCCH resource (1330), and may not include the reception beam report information for the event that occurred later in time (e.g., [Event 2]) in the PUCCH transmission at the n-th transmission position (1320) of the second PUCCH resource (1335), but may include it in the PUCCH transmission at the next transmission position, the n+1-th PUCCH transmission position (1325) (1340).

[0510] FIG. 14 is a diagram illustrating a receiving beam reporting operation process initiated from another terminal when a second PUSCH resource is shared among upper layer signaling for one or more events according to one embodiment of the present disclosure.

[0511] In FIG. 14, the terminal (1401) may transmit a first PUCCH resource (1410) corresponding to the occurrence of the event to the base station to notify the base station of the occurrence of the event when a specific event (e.g., [Event 1]) among one or more events set for the terminal occurs (1403). Subsequently, the terminal may transmit a first PUCCH resource (1415) corresponding to the occurrence of the event to the base station to notify the base station of the occurrence of the event when another specific event (e.g., [Event 2]) among one or more events set for the terminal occurs (1404).

[0512] If, at a specific time prior to the n-th transmission position (1420) of the second PUSCH resource, both events set in the terminal occur (1403, 1404) and the terminal transmits the first PUSCH resource corresponding to each event (1410, 1415), the terminal may consider the priority among one or more events and include the reception beam report information for the event with higher priority (e.g., [event 2]) in the PUSCH transmission at the n-th transmission position (1420) of the second PUSCH resource (1435), and may not include the reception beam report information for the event with lower priority (e.g., [event 1]) in the PUSCH transmission at the n-th transmission position (1420) of the second PUSCH resource (1430), but instead include it in the PUSCH transmission at the next transmission position, the n+1-th PUSCH transmission position (1425) (1440).

[0513] FIG. 15 is a diagram illustrating a receiving beam reporting operation process initiated from another terminal when a second PUSCH resource is shared among upper layer signaling for one or more events according to one embodiment of the present disclosure.

[0514] In FIG. 15, if a specific event (e.g., [Event 1]) among one or more events set for the terminal (1501) occurs (1503), the terminal may not check for the occurrence of all events set for the terminal for a specific period of time (1505) from the time the event occurred, and may transmit a first PUCCH resource (1510) corresponding to the event to the base station to notify the base station of the occurrence of the event. At this time, the terminal not checking for the occurrence of all events may be considered as not performing reception and performance calculations for the current reception beam and / or new reception beam corresponding to all events from the time the specific event occurred (1504), or it may be considered as performing such performance calculations but not transmitting the first PUCCH resource corresponding to each event (1535).

[0515] Therefore, since the terminal does not check for the occurrence of all events set for the terminal for a specific time after a specific event occurs, the terminal can include the specific event that occurred in a connected Type-1 configured grant-based second PUSCH resource and transmit it to the base station. In particular, if the first PUSCH resource corresponding to the specific event that occurred from the terminal is transmitted from the nth transmission position (1520) of the second PUSCH resource before a specific time, the terminal can include the reception beam report information originating from the terminal in the second PUSCH resource and transmit it to the base station (1530).

[0516] FIG. 16 is a diagram illustrating a receiving beam reporting operation process initiated from another terminal when a second PUSCH resource is shared among upper layer signaling for one or more events according to one embodiment of the present disclosure.

[0517] In FIG. 16, the terminal (1601) may transmit a first PUCCH resource (1610) corresponding to the event to the base station to notify the base station of the occurrence of the event, when a specific event (e.g., [Event 1]) among one or more events set for the terminal has occurred (1603). Subsequently, the terminal may transmit a first PUCCH resource (1615) corresponding to the event to the base station to notify the base station of the occurrence of the event, when another specific event (e.g., [Event 2]) among one or more events set for the terminal has occurred (1604).

[0518] If, prior to a specific time from the n-th transmission location (1620) of the second PUSCH resource, both events set in the terminal occur (1603, 1604) and the terminal transmits the first PUSCH resource corresponding to each event (1610, 1615), the terminal may transmit the received beam report information originating from the terminal for the two events that occurred, including it in the n-th transmission location (1620) of the second PUSCH resource. That is, the terminal may include the received beam report information originating from the terminal corresponding to one or more events at a specific transmission location of the second PUSCH resource. At this time, the terminal and the base station may define the maximum number of events corresponding to the received beam report information that can be included at the specific transmission location of the second PUSCH resource and reported to the base station. For example, the terminal may be notified of the maximum number through a combination of at least one of upper layer signaling, MAC-CE signaling, and L1 signaling from the base station. Additionally, the terminal may report one or more values ​​supported by the terminal as terminal capabilities for the aforementioned maximum number, and the value reported by the terminal may be used immediately without notification from the aforementioned base station when the terminal performs a received beam report originating from the terminal, or the value reported by the terminal may be utilized as information that the base station can refer to when determining the said maximum number upon notification from the aforementioned base station. Additionally, the said maximum number may be fixedly defined in the standard (e.g., one or two).

[0519] [Method 2-4]

[0520] A terminal may receive upper-layer signaling regarding a reception beam performance report originating from a terminal corresponding to one or more events from a base station, and if all reception beam performance reports originating from a terminal for each event operate based on [Method 1-2] above, some of these may be set commonly for all events. As an example, the terminal may receive upper-layer signaling related to channel state information reporting (e.g., CSI-ReportConfig) commonly from the base station for all of the one or more events. In this case, the terminal may receive upper-layer signaling related to the one or more events individually within a single CSI-ReportConfig.

[0521] For example, if a terminal receives upper-layer signaling corresponding to one or more different events within a single CSI-ReportConfig, the terminal can expect that upper-layer signaling for each event is included within the CSI-ReportConfig. The upper-layer signaling for each event can determine whether the terminal performs a receive beam reporting operation initiated by the terminal based on each event. For example, the terminal may receive upper-layer signaling for the first and second events that signifies performing a receive beam reporting operation based on each event, but may not receive such signaling for the third event. In such a case, the terminal can expect upper-layer signaling with a structure similar to [Table 27] below for the CSI-ReportConfig settings. The information in Table 27 below is merely an example, and at least one of the information described below may be included in the CSI-ReportConfig, and additional information not described may also be included.

[0522] CSI-ReportConfig...- Reporting mode: Mode-B- PUCCH resource ID: 1- PUSCH resource (Type-1 configured grant) ID: 1- New beam RS set ID: 1 (SSB resource set)- Reporting current beam's quality: enabled- Event-1: enabled- Event-2: enabled- Event-3: disabled

[0523] In the above, Reporting mode may mean one of [Method 1-1] or [Method 1-2], and Mode-B may be considered the same as [Method 1-2].

[0524] In the above, Event-1, Event-2, and Event-3 may each refer to the first event, the second event, and the third event.

[0525] In the above, among the upper layer signaling provided to the terminal through CSI-ReportConfig, Reporting Mode, PUCCH resource, PUSCH resource, New beam RS set, and reporting current beam's quality can be used commonly for both Event-1 and Event-2 configured within the CSI-ReportConfig.

[0526] As another example, the terminal can expect to be configured to distinguish between upper-layer signaling that is commonly applied to one or more events configured within a single CSI-ReportConfig and upper-layer signaling that is individually applied, through a structure such as [Table 28] below. The information in Table 28 below is merely an example, and at least one of the information described below may be included in the CSI-ReportConfig, and additional information not described below may also be included.

[0527] CSI-ReportConfig… - Reporting mode: Mode-B- PUSCH resource (Type-1 configured grant) ID: 1- Event-1: enabled● PUCCH resource ID: 1● New beam RS set ID: 1 (SSB resource set)● Reporting current beam's quality: enabled- Event-2: enabled● PUCCH resource ID: 2● New beam RS set ID: 2 (NZP CSI-RS resource set)● Reporting current beam's quality: disabled- Event-3: disabled

[0528] In the above, Reporting mode may mean one of [Method 1-1] or [Method 1-2], and Mode-B may be considered the same as [Method 1-2].

[0529] In the above, Event-1, Event-2, and Event-3 may each refer to the first event, the second event, and the third event.

[0530] In the above, among the upper layer signaling provided to the terminal through CSI-ReportConfig, the Reporting Mode and PUSCH resources can be used commonly for both Event-1 and Event-2 configured within the CSI-ReportConfig.

[0531] In the above, the terminal can receive a PUCCH resource, a new beam RS set, and a reporting status of the current beam's quality configured for each event through CSI-ReportConfig, and regarding the PUCCH resource, the new beam RS set, and the reporting status of the current beam's quality, the terminal can operate by referring to different upper-layer signaling for each event.

[0532] The situation described above is merely an example and is not limited thereto. As another example, the terminal may receive individual upper-layer signaling for each event regarding Reporting Mode, PUCCH resource, PUSCH resource, New beam RS set, and reporting current beam's quality.

[0533] As another example, when a terminal is configured within one CSI-ReportConfig for one or more events, the terminal may receive one or more CSI-ReportSubConfig configurations corresponding to each event from the base station within the CSI-ReportConfig, and it is expected that these will be configured by distinguishing them through a structure such as [Table 29] below. The information in Table 29 below is merely an example, and at least one of the information described below may be included in the CSI-ReportConfig and CSI-ReportSubConfig, and additional information not described may also be included.

[0534] CSI-ReportConfig… - CSI-ReportSubConfig ID: 1● Event ID: 1● Reporting mode: Mode-B● PUCCH resource ID: 1● PUSCH resource (Type-1 configured grant) ID: 1● New beam RS set ID: 1 (SSB resource set)● Reporting current beam's quality: enabled- CSI-ReportSubConfig ID: 2● Event ID: 2● Reporting mode: Mode-B● PUCCH resource ID: 1● PUSCH resource (Type-1 configured grant) ID: 1● New beam RS set ID: 2 (NZP CSI-RS resource set)● Reporting current beam's quality: disabled

[0535] In the above, Reporting mode may mean one of [Method 1-1] or [Method 1-2], and Mode-B may be considered the same as [Method 1-2].

[0536] In the above, Event-1, Event-2, and Event-3 may each refer to the first event, th...

Claims

1. In a method performed by a terminal of a communication system, A step of receiving configuration information for user equipment-initiated beam reporting from a base station, wherein the configuration information is channel state information (CSI) reporting configuration information, and the configuration information includes PUCCH (physical uplink control channel) resource information for the terminal to initiate a received beam report when Event 1 occurs, and information indicating whether an indicator indicating whether a specific new received beam transmitted through the received beam report satisfies the conditions of Event 1 is included in the received beam report; A step of confirming that Event 1 has occurred because the above conditions of Event 1 are satisfied; A step of generating the receiving beam report including information about the specific new receiving beam mentioned above; A step of transmitting an indicator for the received beam report on the PUCCH resource indicated by the above PUCCH resource information; and The method includes the step of transmitting the above-mentioned received beam report over a PUSCH (physical uplink shared channel), The above received beam report includes the indicator that indicates whether the specific new received beam satisfies the condition of the event 1, and A method characterized in that the above condition of Event 1 corresponds to the case where the RSRP value of the new receiving beam is greater than the threshold value of the current receiving beam.

2. A method according to claim 1, characterized in that the setting information further includes an indicator indicating whether the performance of the current receiving beam is reported.

3. In Paragraph 1, A method characterized in that the above-mentioned receiving beam report further includes an identifier of the above-mentioned CSI report setting information.

4. A method according to paragraph 3, characterized in that the identifier of the CSI report setting information indicates one of the CSI report setting informations that sets the PUCCH resource.

5. In the method performed by a base station of a communication system, A step of transmitting configuration information for user equipment-initiated beam reporting to a terminal, wherein the configuration information is channel state information (CSI) reporting configuration information, and wherein the configuration information includes PUCCH (physical uplink control channel) resource information for the terminal to initiate a received beam report when Event 1 occurs, and information indicating whether an indicator indicating whether a specific new received beam transmitted through the received beam report satisfies the conditions of Event 1 is included in the received beam report; A step of receiving an indicator for the received beam report on the PUCCH resource indicated by the above PUCCH resource information; and The method includes the step of receiving the above-mentioned received beam report over a PUSCH (physical uplink shared channel), and The above received beam report includes information regarding the specific new received beam and the indicator indicating whether the specific new received beam satisfies the conditions of the event 1, and A method characterized in that the above condition of Event 1 corresponds to the case where the RSRP value of the new receiving beam is greater than the threshold value of the current receiving beam.

6. A method according to claim 5, characterized in that the setting information further includes an indicator indicating whether the current receiving beam's performance is reported.

7. In Paragraph 5, A method characterized in that the above-mentioned receiving beam report further includes an identifier of the above-mentioned CSI report setting information.

8. A method according to claim 7, characterized in that the identifier of the CSI report setting information indicates one of the CSI report setting informations that sets the PUCCH resource.

9. In a terminal of a communication system, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and The terminal is connected to communicate with at least one processor and is capable of executing individually or in any combination of the at least one processor, so that the terminal: Receives configuration information for user equipment initiated beam reporting from a base station, wherein the configuration information is channel state information (CSI) reporting configuration information, and the configuration information includes PUCCH (physical uplink control channel) resource information for the terminal to initiate a received beam report when Event 1 occurs, and information indicating whether an indicator indicating whether a specific new received beam transmitted through the received beam report satisfies the conditions of Event 1 is included in the received beam report. Confirm that Event 1 has occurred because the above conditions of Event 1 are satisfied, and Generate the receiving beam report containing information about the specific new receiving beam mentioned above, and Transmitting an indicator for the received beam report on the PUCCH resource indicated by the above PUCCH resource information, and A memory storing a command to transmit the above-mentioned received beam report over the PUSCH (physical uplink shared channel); comprising The above received beam report includes the indicator that indicates whether the specific new received beam satisfies the condition of the event 1, and A terminal characterized in that the condition of the above event 1 corresponds to the case where the RSRP value of the new receiving beam is greater than the threshold value of the current receiving beam.

10. A terminal according to claim 9, characterized in that the setting information further includes an indicator indicating whether the performance of the current receiving beam is reported.

11. In Paragraph 9, A terminal characterized in that the above-mentioned receiving beam report further includes an identifier of the above-mentioned CSI report setting information.

12. A terminal according to claim 11, characterized in that the identifier of the CSI report setting information indicates one of the CSI report setting informations that sets the PUCCH resource.

13. In a base station of a communication system, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and Connected to communicate with at least one processor and capable of executing individually or in any combination of the at least one processor, the base station: A terminal transmits configuration information for user equipment-initiated beam reporting, wherein the configuration information is channel state information (CSI) reporting configuration information, wherein the configuration information includes PUCCH (physical uplink control channel) resource information for the terminal to initiate a received beam report when Event 1 occurs, and information indicating whether an indicator indicating whether a specific new received beam transmitted through the received beam report satisfies the conditions of Event 1 is included in the received beam report. Receiving an indicator for the received beam report on the PUCCH resource indicated by the above PUCCH resource information, and A memory storing a command to receive the above-mentioned received beam report over a PUSCH (physical uplink shared channel); comprising The above received beam report includes information regarding the specific new received beam and the indicator indicating whether the specific new received beam satisfies the conditions of the event 1, and A base station characterized by the above condition of Event 1 corresponding to the case where the RSRP value of the new receiving beam is greater than the threshold value of the current receiving beam.

14. A base station according to claim 13, characterized in that the setting information further includes an indicator indicating whether the performance of the current receiving beam is reported.

15. In Paragraph 13, The above-mentioned receiving beam report further includes an identifier of the above-mentioned CSI report setting information, and A base station characterized in that the identifier of the above CSI report setting information indicates one of the CSI report setting informations that sets the above PUCCH resource.

Images