Method and apparatus for transmitting channel state information of terminal in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a terminal in a wireless communication system, according to an embodiment of the present disclosure, comprises the steps of: receiving reception beam report-related configuration information from a base station through higher layer signaling; and transmitting a reception beam report to the base station on the basis of the reception beam report-related configuration information, wherein the reception beam report includes at least one of a performance value of a current reception beam, an index of a new reception beam, and a performance value of at least one new reception beam.

Description

Method and device for transmitting channel state information of a terminal 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 transmitting channel state information by a terminal in a wireless communication system and a device 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 the sub-6GHz frequency band ('Sub 6GHz') such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band ('Above 6GHz') called millimeter wave (mmWave) such as 28GHz and 39GHz. In addition, 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G),

[0003] Implementation in the terahertz band (e.g., 3 terahertz (3THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster than mobile communication technology and ultra-low latency that is reduced to one-tenth.

[0004] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0005] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

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

[0007] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0008] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0009] The disclosed embodiment seeks to provide a device and method capable of effectively providing a service in a mobile communication system.

[0010] A method performed by a terminal in a wireless communication system according to one embodiment of the present disclosure includes the steps of: receiving, from a base station, configuration information related to a reception beam report through upper layer signaling; and transmitting, to the base station, a configuration information related to the reception beam report, wherein the configuration information related to the reception beam report includes at least one of a performance value of a current reception beam, an index of a new reception beam, or a performance value of at least one new reception beam.

[0011] A method performed by a base station in a wireless communication system according to one embodiment of the present disclosure includes the steps of: transmitting, to a terminal, configuration information related to a reception beam report through upper layer signaling; and receiving, from the terminal, a configuration information related to the reception beam report, wherein the configuration information related to the reception beam report includes at least one of a performance value of a current reception beam, an index of a new reception beam, or a performance value of at least one new reception beam.

[0012] In a wireless communication system according to one embodiment of the present disclosure, a terminal includes a transceiver; and at least one processor; wherein the at least one processor is configured to receive, from a base station, configuration information related to a reception beam report through upper layer signaling, and transmit a reception beam report to the base station based on the configuration information related to the reception beam report, wherein the reception beam report includes at least one of a performance value of a current reception beam, an index of a new reception beam, or a performance value of at least one new reception beam.

[0013] In a wireless communication system according to one embodiment of the present disclosure, a base station includes a transceiver; and at least one processor; wherein the at least one processor is configured to transmit, to a terminal, configuration information related to a reception beam report through upper layer signaling, and to receive, from the terminal, a reception beam report based on the configuration information related to the reception beam report, wherein the reception beam report includes at least one of a performance value of a current reception beam, an index of a new reception beam, or a performance value of at least one new reception beam.

[0014] The disclosed embodiment provides a device and method capable of effectively providing a service in a mobile communication system.

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

[0016] FIG. 2 is a diagram 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 diagram illustrating an example of bandwidth portion settings in a wireless communication system according to one embodiment of the present disclosure.

[0018] FIG. 4a, FIG. 4b, and FIG. 4c are diagrams illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation in a wireless communication system according to one embodiment of the present disclosure.

[0019] FIG. 5a and FIG. 5b are diagrams of beam application times that can be considered when using an integrated transmission configuration indication (TCI) method in a wireless communication system according to an embodiment of the present disclosure.

[0020] FIG. 6 is a diagram illustrating another MAC-CE (medium access control-control element) structure for activating and indicating a joint TCI state or a separate DL (downlink) or UL (uplink) TCI state in a wireless communication system according to an embodiment of the present disclosure.

[0021] FIG. 7 is a diagram illustrating an example of an aperiodic CSI (channel state information) reporting method.

[0022] FIG. 8 is a diagram illustrating an example of setting a control region 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 the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0024] FIG. 10A and FIG. 10B are diagrams illustrating a channel measurement and channel status reporting method according to the setting and instruction of a base station according to one embodiment of the present disclosure.

[0025] FIG. 11 is a diagram illustrating an example of an operation process of a terminal and a base station for a CSI report initiated by a terminal using a physical uplink control channel (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 an example of an 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 (physical uplink shared channel) transmissions according to one embodiment of the present disclosure.

[0027] FIG. 13 is a diagram illustrating the operation of a terminal according to one embodiment of the present disclosure.

[0028] FIG. 14 is a diagram illustrating the operation of a base station according to one embodiment of the present disclosure.

[0029] FIG. 15 is a diagram illustrating the structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.

[0030] FIG. 16 is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

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

[0032] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanations.

[0033] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0034] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present 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. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and these may vary depending on the intention or custom of the user or operator. Therefore, their definitions should be made based on the contents throughout the specification.

[0035] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although the LTE or LTE-A system may be described below as an example, the embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and the 5G below may also 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 within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.

[0036] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0037] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0038] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, 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'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

[0039] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 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.

[0040] As a representative example of the above broadband wireless communication system, the LTE system adopts the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink (DL) and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B or base station (BS)), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so as to achieve orthogonality.

[0041] As a future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0042] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band.

[0043] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting large-scale terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in shadow areas, such as basements, beyond cell coverage. This may require broader coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, they may require extremely long battery lifespans, such as 10 to 15 years.

[0044] Finally, URLLC refers to a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, services such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts can be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds and, at the same time, must have a 10 -5The following packet error rate (PER) requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a smaller Transmit Time Interval (TTI) than other services. Simultaneously, design considerations may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0045] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

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

[0047] [NR time-frequency resources]

[0048] Below, the frame structure of the 5G system is described in more detail with reference to drawings.

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

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

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

[0052] Referring to FIG. 2, an example of a structure of a frame (200), a subframe (201), and a slot (202) is illustrated. One frame (200) can be defined as 10 ms. One subframe (201) can be defined as 1 ms, and therefore 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). 1 subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per 1 subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing.

[0053] In Fig. 2, the cases where μ=0(204) and μ=1(205) are illustrated as the subcarrier spacing setting values. When μ=0(204), 1 subframe (201) can be composed of 1 slot (202), and when μ=1(205), 1 subframe (201) can be composed of 2 slots (203). That is, depending on the setting value μ for the subcarrier spacing, the number of slots per subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ and can be defined as [Table 1] below.

[0054]

[0055] [Bandwidth Part (BWP)]

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

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

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

[0059] BWP ::= SEQUENCE {bwp-Id BWP-Id,(bandwidth part identifier)locationAndBandwidth INTEGER (1..65536),(bandwidth part location)subcarrierSpacing ENUMERATED {n0, n1, n2, n3, n4, n5},(subcarrier spacing)cyclicPrefix ENUMERATED { extended}(cyclic prefix)}

[0060] Of course, the above example is not limited, and in addition to the above configuration information, various parameters related to the bandwidth portion can be configured for the terminal. The above information can be transmitted from the base station to the terminal via upper layer signaling, for example, RRC (Radio Resource Control) signaling. At least one bandwidth portion among the configured one or more bandwidth portions can be activated. Whether or not the configured bandwidth portion is activated can be semi-statically transmitted from the base station to the terminal via RRC signaling or dynamically transmitted via DCI.

[0061] In some embodiments, a terminal prior to RRC connection may receive an initial bandwidth portion (Initial BWP) for initial access from a base station via a Master Information Block (MIB). More specifically, during the initial access phase, the terminal may receive configuration information regarding a Control Resource Set (CORESET) and a Search Space, where a PDCCH for receiving system information (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) required for initial access may be transmitted. The Control Space and Search Space configured via the MIB may each be regarded as having an identifier (Identity: ID) of 0.

[0062] The base station can notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for control area #0 through MIB. In addition, the base station can notify the terminal of configuration information for monitoring cycle and monitoring occasion for control area #0, i.e. configuration information for search space #0, through MIB. The terminal can regard the frequency area set as control area #0 obtained from the MIB as the initial bandwidth portion for initial access. At this time, the identifier (ID) of the initial bandwidth portion can be regarded as 0.

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

[0064] In some embodiments, when the bandwidth supported by a terminal is smaller than the system bandwidth, this can be supported through bandwidth portion configuration. For example, the base station can configure the bandwidth portion frequency location (configuration information 2) for the terminal, thereby allowing the terminal to transmit and receive data at a specific frequency location within the system bandwidth.

[0065] Additionally, in some embodiments, a base station may configure multiple bandwidth segments for a terminal to support different numerologies. For example, to support data transmission and reception using both a 15 kHz subcarrier spacing and a 30 kHz subcarrier spacing for a given terminal, two bandwidth segments may be configured with subcarrier spacings of 15 kHz and 30 kHz, respectively. The different bandwidth segments may be frequency-division multiplexed (FDM), and when data is to be transmitted and received using a specific subcarrier spacing, the bandwidth segment configured with the subcarrier spacing may be activated.

[0066] Furthermore, in some embodiments, the base station may configure bandwidth portions with different bandwidth sizes for the terminal for the purpose of reducing power consumption of the terminal. For example, if the terminal supports a very large bandwidth (e.g., 100 MHz bandwidth) and constantly transmits and receives data within the bandwidth, very large power consumption may occur. In particular, monitoring unnecessary downlink control channels with a large bandwidth of 100 MHz in a situation where there is no traffic may be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station may configure a bandwidth portion with a relatively small bandwidth, for example, 20 MHz, for the terminal. In a situation where there is no traffic, the terminal may perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it may transmit and receive data in the 100 MHz bandwidth portion according to the instructions of the base station.

[0067] In the method for setting the bandwidth portion, terminals prior to RRC connection (Connected) can receive configuration information for the initial bandwidth portion (Initial BWP) through the MIB during the initial access phase. More specifically, the terminal can set a control region (i.e., CORESET) for a downlink control channel on which a DCI scheduling a System Information Block (SIB) can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth portion, and the terminal can receive the Physical Downlink Shared Channel (PDSCH) on which the SIB is transmitted through the set initial bandwidth portion. In addition to receiving the SIB, the initial bandwidth portion can also be utilized for other system information (Other System Information (OSI), paging, and random access).

[0068] [Bandwidth Part (BWP) Change]

[0069] When one or more bandwidth part values ​​are set for a terminal, the base station can instruct the terminal to change (or switch, transition) the bandwidth part value using the bandwidth part indicator field in the DCI. For example, in FIG. 3, when the currently activated bandwidth part of the terminal is bandwidth part #1 (301), the base station can instruct the terminal to bandwidth part #2 (302) using the bandwidth part indicator in the DCI, and the terminal can perform a bandwidth part change to bandwidth part #2 (302) indicated by the bandwidth part indicator in the received DCI.

[0070] As described above, since DCI-based bandwidth part change can be indicated by DCI scheduling physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH), when a terminal receives a bandwidth part change request, it must be able to perform reception or transmission of PDSCH or PUSCH scheduled by the DCI without difficulty in the changed bandwidth part. To this end, the standard specifies the delay time (T) required when changing the bandwidth part. BWP ) and can be defined as in [Table 3] below, for example.

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

[0072] The bandwidth-partial change delay time requirement supports Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth-partial delay time type to the base station.

[0073] According to the requirement for the bandwidth part change delay time described above, when the terminal receives DCI including the bandwidth part change indicator in slot n, the terminal can complete the change to the new bandwidth part indicated by the bandwidth part change indicator at a time not later than slot n+TBWP, and can perform transmission and reception for the data channel (e.g., PUSCH or PDSCH) scheduled by the DCI in the changed new bandwidth part.

[0074] When a base station wants to schedule a data channel in a new bandwidth portion, it can determine the time domain resource allocation for the data channel by considering the bandwidth portion change delay time (TBWP) of the terminal. That is, when scheduling a data channel in a new bandwidth portion, the base station can schedule the data channel after the bandwidth portion change delay time in the method of determining the time domain resource allocation for the data channel. Accordingly, the terminal may not expect the DCI indicating the bandwidth portion change to indicate a slot offset (K0 or K2) value smaller than the bandwidth portion change delay time (TBWP).

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

[0076] [CA / DC related]

[0077] FIGS. 4A, 4B, and 4C are diagrams illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation (CA), and dual connectivity (DC) according to one embodiment of the present disclosure.

[0078] Referring to FIGS. 4a, 4b, and 4c, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (Service Data Adaptation Protocol) (425, 470), NR PDCP (Packet Data Convergence Protocol) (430, 465), NR RLC (Radio Link Control) (435, 460), and NR MAC (Medium Access Control) (440, 455) in the terminal and the NR base station, respectively.

[0079] The main functions of NR SDAP (425, 470) may include at least some of the following functions:

[0080] - Transfer of user plane data

[0081] - Mapping function between QoS flow and data bearer for both DL and UL

[0082] - Marking function of QoS flow ID for both uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0083] - Ability to map reflective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0084] For the above SDAP layer device, the terminal can be configured by an RRC message for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device, and when the SDAP header is configured, the terminal can instruct the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) of the SDAP header to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support a smooth service.

[0085] The main functions of NR PDCP (430, 465) may include at least some of the following functions:

[0086] - Header compression and decompression (ROHC only)

[0087] - User data transfer function

[0088] - In-sequence delivery of upper layer PDUs

[0089] - Out-of-sequence delivery of upper layer PDUs

[0090] - PDCP PDU reordering for reception

[0091] - Duplicate detection of lower layer SDUs

[0092] - Retransmission function (Retransmission of PDCP SDUs)

[0093] - Encryption and decryption functions (Ciphering and deciphering)

[0094] - Timer-based SDU discard in uplink.

[0095] The reordering function of the NR PDCP device above refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP device may include a function of transmitting data directly without considering the order, a function of recording lost PDCP PDUs by reordering the order, a function of reporting a status of lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of lost PDCP PDUs.

[0096] The main functions of NR RLC (435, 460) may include at least some of the following functions:

[0097] - Data transfer function (Transfer of upper layer PDUs)

[0098] - In-sequence delivery of upper layer PDUs

[0099] - Out-of-sequence delivery of upper layer PDUs

[0100] - ARQ function (Error Correction through ARQ)

[0101] - Concatenation, segmentation and reassembly of RLC SDUs

[0102] - Re-segmentation of RLC data PDUs

[0103] - Reordering of RLC data PDUs

[0104] - Duplicate detection function

[0105] - Protocol error detection

[0106] - RLC SDU discard function

[0107] - RLC re-establishment function

[0108] In the above, the in-sequence delivery function of the NR RLC device refers to the function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering a single RLC SDU when it is received divided into multiple RLC SDUs, a function of rearranging received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number), a function of recording lost RLC PDUs by rearranging the order, a function of reporting the status of lost RLC PDUs to the transmitting side, and a function of requesting retransmission of lost RLC PDUs.

[0109] The in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer only the RLC SDUs up to the lost RLC SDU when there is a lost RLC SDU, or may include a function to sequentially deliver to the upper layer all RLC SDUs received before the timer starts if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer all RLC SDUs received up to the present if a predetermined timer has expired even if there is a lost RLC SDU.

[0110] In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the order of the sequence number) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, the segments stored in the buffer or to be received later may be received, reconstructed into a complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

[0111] The out-of-sequence delivery function of the NR RLC device above refers to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order, and may include a function of reassembling and delivering RLC SDUs when one RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing and arranging the RLC SN or PDCP SN of received RLC PDUs to record lost RLC PDUs.

[0112] NR MAC (440, 455) can be connected to multiple NR RLC layer devices configured in one terminal, and the main function of NR MAC can include at least some of the following functions.

[0113] - Mapping function (Mapping between logical channels and transport channels)

[0114] - Multiplexing / demultiplexing of MAC SDUs

[0115] - Scheduling information reporting function

[0116] - HARQ function (Error correction through HARQ)

[0117] - Priority handling between logical channels of one UE

[0118] - Priority handling between UEs by means of dynamic scheduling

[0119] - MBMS service identification function

[0120] - Transport format selection function

[0121] - Padding function

[0122] The NR PHY layer (445, 450) can perform operations of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.

[0123] The above wireless protocol structure can have various detailed structures depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure having a single structure for each layer, as shown in 400. On the other hand, when a base station transmits data to a terminal based on CA (carrier aggregation) using multiple carriers in a single TRP, the base station and the terminal use a protocol structure having a single structure up to RLC but multiplexing the PHY layer through the MAC layer, as shown in 410. As another example, when a base station transmits data to a terminal based on DC (dual connectivity) using multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure having a single structure up to RLC but multiplexing the PHY layer through the MAC layer, as shown in 420.

[0124] [Unified TCI state]

[0125] Hereinafter, a single TCI state indication and activation method based on the unified TCI scheme is described. The unified TCI scheme can refer to a method of integrating and managing the transmission and reception beam management methods, which were distinguished into the TCI state method used for downlink reception of the terminal in the existing Rel-15 and 16 and the spatial relation info method used for uplink transmission, into a TCI state. Therefore, when the terminal is instructed by the base station based on the unified TCI scheme, it can perform beam management using the TCI state even for uplink transmission. If the terminal has set a TCI-State, which is an upper layer signaling with the tci-stateId-r17, which is an upper layer signaling, from the base station, the terminal can perform operations based on the unified TCI scheme using the corresponding TCI-State. The TCI-State can exist in two forms: a joint TCI state or a separate TCI state.

[0126] The first type is a joint TCI state, and the terminal can be instructed by the base station to use both the TCI state to apply to uplink transmission and downlink reception through a single TCI-State. If the terminal is instructed to use a TCI-State based on a joint TCI state, the terminal can use the RS corresponding to qcl-Type1 in the TCI-State based on the joint TCI state to instruct the parameters to use for downlink channel estimation, and the RS corresponding to qcl-Type2 to instruct the parameters to use as a downlink reception beam or reception filter. If the terminal is instructed to use a TCI-State based on a joint TCI state, the terminal can use the RS corresponding to qcl-Type2 in the TCI-State based on the joint DL / UL TCI state to instruct the parameters to use as an uplink transmission beam or transmission filter. In this case, if the terminal is instructed to use a joint TCI state, the terminal can apply the same beam to both uplink transmission and downlink reception.

[0127] The second form is a separate TCI state, in which the terminal can be individually instructed by the base station to select a UL TCI state to apply to uplink transmission and a DL TCI state to apply to downlink reception. If the terminal is instructed to select a UL TCI state, the terminal can be instructed to select parameters to use as an uplink transmission beam or transmission filter using the reference RS or source RS configured in the UL TCI state. If the terminal is instructed to select a DL TCI state, the terminal can be instructed to select parameters to use for downlink channel estimation using the RS corresponding to qcl-Type1 configured in the DL TCI state, and to select parameters to use as a downlink reception beam or reception filter using the RS corresponding to qcl-Type2.

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

[0129] A terminal can receive a joint TCI state from a base station for each bandwidth part within a specific cell through upper layer signaling up to 128 times, and among the separate TCI states, a DL TCI state can be set for each bandwidth part within a specific cell up to 64 or 128 times through upper layer signaling based on a terminal capability report. Among the separate TCI states, the DL TCI state and the joint TCI state 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.

[0130] Among the separate TCI states, the UL TCI state can be set to a maximum of 32 or 64 upper layer signaling for each specific bandwidth part within a specific cell based on the terminal capability report, 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 TCI can also use the same upper layer signaling structure, and the UL TCI state among the separate TCI can use different upper layer signaling structures from the joint TCI state and the DL TCI state among the separate TCI states.

[0131] The use of different or identical upper layer signaling structures may be defined in the specification, or may be distinguished through another upper layer signaling established by the base station based on a terminal capability report containing information on which of the two usage modes the terminal can support.

[0132] The terminal can receive transmission and reception beam-related instructions in an integrated TCI manner using one of the joint TCI state and separate TCI state configured by the base station. The terminal can be configured by the base station via upper layer signaling whether to use either the joint TCI state or separate TCI state.

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

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

[0135] If a terminal receives an instruction related to a transmit / receive beam 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 indicating a separate TCI state from a base station, and the base station can schedule reception of a PDSCH including the corresponding MAC-CE to the terminal through a PDCCH. If the MAC-CE includes only one set of separate TCI states, the terminal can determine an uplink transmit beam or transmit filter and a downlink receive beam or receive filter using the separate TCI states included in the indicated separate TCI state set starting from 3 ms after transmitting a PUCCH including HARQ-ACK information indicating whether reception of the corresponding PDSCH was successful. At this time, the separate TCI state set may mean single or multiple separate TCI states that one code point of the TCI state field in DCI format 1_1 or 1_2 can have, and one 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 in the MAC-CE, the UE may confirm that the multiple separate TCI state sets indicated by the MAC-CE correspond to each code point of the TCI state field of DCI format 1_1 or 1_2 starting from 3 ms after transmitting the PUCCH including HARQ-ACK information indicating whether reception for the corresponding PDSCH was successful, and may activate the indicated separate TCI state set.At this time, each code point of the TCI state field of DCI format 1_1 or 1_2 can indicate one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state each. The terminal can receive DCI format 1_1 or 1_2 and apply a separate set of TCI states indicated by the TCI state field in the corresponding DCI to the uplink transmission and downlink reception beams. At this time, 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).

[0136] FIG. 5A and FIG. 5B are diagrams illustrating beam application times that may be considered when using an integrated TCI scheme in a wireless communication system according to an embodiment of the present disclosure. As described above, a terminal may receive DCI format 1_1 or 1_2 from a base station, including (with DL assignment) or not including (without DL assignment) downlink data channel scheduling information, and may apply one joint TCI state or a separate set of TCI states indicated by the TCI state field in the corresponding DCI to uplink transmission and downlink reception beams.

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

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

[0139] - Includes scrambled CRC using CS-RNTI.

[0140] - All bits assigned to all fields used as RV (Redundancy Version) fields have a value of 1.

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

[0142] - All bits assigned to all fields used as NDI (New Data Indication) fields have values ​​of 0.

[0143] - For FDRA (Frequency Domain Resource Allocation) Type 0, the value of all bits assigned to the FDRA field is 0, for FDRA Type 1, the value of all bits assigned to the FDRA field is 1, and when the FDRA method is dynamicSwitch, the value of all bits assigned to the FDRA field is 0.

[0144] The terminal can transmit a PUCCH including a HARQ-ACK indicating whether reception was successful for the DCI format 1_1 or 1_2 assuming the above-described matters (560).

[0145] - For both DCI format 1_1 or 1_2 with DL assignment (500) and without DL assignment (550), if a new TCI state indicated through DCI (501, 555) is the same as a TCI state that has already been indicated and applied to an uplink transmission and downlink reception beam, the UE can maintain the previously applied TCI state, and if the new TCI state is different from the previously indicated TCI state, the UE can determine the application time of a joint TCI state or a separate TCI state set that can be indicated from the TCI state field included in the DCI as the time after the first slot (520, 570) after the time equal to BAT (beam application time, 515, 565) after the PUCCH transmission (530, 580), and can use the previously indicated TCI-state until (525, 575) before the corresponding slot (520, 570).

[0146] - For both DCI format 1_1 or 1_2 with DL assignment (500) and without DL assignment (550), the BAT can be set by upper layer signaling based on terminal capability report information as a specific number of OFDM symbols, and the numerology for the BAT and the first slot after the 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 the DCI is applied.

[0147] A terminal can apply one joint TCI state indicated via MAC-CE or DCI to reception of control resource sets connected to all terminal-specific search spaces, reception of PDSCHs scheduled as PDCCHs transmitted from the control resource sets, transmission of PUSCHs, and transmission of all PUCCH resources.

[0148] A terminal may apply one separate TCI state set, if one separate TCI state set indicated via MAC-CE or DCI includes one DL TCI state, to reception for control resource sets connected to all terminal-specific search spaces, to reception for PDSCH scheduled as PDCCH transmitted from the control resource set, and to all PUSCH and PUCCH resources based on the previously indicated UL TCI state.

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

[0150] When a separate set of TCI states indicated via MAC-CE or DCI includes one DL TCI state and one UL TCI state, the terminal may apply the DL TCI state to reception for all control resource sets associated with the terminal-specific search space and to reception for PDSCH scheduled as PDCCH transmitted from the control resource set, and may apply the UL TCI state to all PUSCH and PUCCH resources.

[0151] [Unified TCI state MAC-CE]

[0152] Hereinafter, a single TCI state indication and activation method based on the integrated TCI scheme is described. The terminal receives a PDSCH including the following MAC-CE from the base station, and from 3 slots after transmitting a HARQ-ACK for the corresponding PDSCH to the base station, the terminal can interpret each code point of the TCI state field in DCI format 1_1 or 1_2 based on the information in 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.

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

[0154] - Serving Cell ID (600): This field can indicate which serving cell the MAC-CE is applied to. The length of this field can be 5 bits. If the serving cell indicated by this field is included in one or more of the upper layer signaling simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4, the MAC-CE can 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 include the serving cell indicated by this field.

[0155] - DL BWP ID (605): This field can indicate to which DL BWP the corresponding MAC-CE applies, and the meaning of each code point in this field can correspond to each code point of the bandwidth part indicator in the DCI. The length of this field can be 2 bits.

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

[0157] - P i (615): This field can indicate whether each code point in the TCI state field in DCI format 1_1 or 1_2 has multiple TCI states or a single 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 corresponding code point may contain a separate DL TCI state and a separate UL TCI state. If P i If the value is 0, it means that the corresponding ith code point has a single TCI state, which may mean that the corresponding code point may contain either a joint TCI state, a separate DCI TCI state, or a separate UL TCI state.

[0158] - D / U (620): This field can indicate whether the TCI state ID field in 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 in the same octet can be a joint TCI state or a separate DL TCI state, and if this field is 0, the TCI state ID field in the same octet can be a separate UL TCI state.

[0159] - TCI state ID (625): This field can 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 can be used to express the TCI-StateId, which can be expressed in 7 bits. If the D / U field is set to 0, the MSB (most significant bit) of this field can be considered a reserved bit, and the remaining 6 bits can be used to express the upper layer signaling UL-TCIState-Id. The maximum number of TCI states that can be activated can be 8 for a joint TCI state and 16 for separate DL or UL TCI states.

[0160] - R: Indicates reserved bit and can be set to 0.

[0161] For the MAC-CE structure of FIG. 6 described above, the terminal can include the third octet including the P1, P2, ..., P8 fields in FIG. 6 in the MAC-CE structure, regardless of whether unifiedTCI-StateType-r17 in MIMOparam-r17 in ServingCellConfig, which is an upper layer signaling, is set to joint or separate. In this case, the terminal can perform TCI state activation using the fixed MAC-CE structure regardless of the upper layer signaling set by the base station. As another example, for the MAC-CE structure of FIG. 6 described above, the terminal can omit the third octet including the P1, P2, ..., P8 fields in FIG. 6 when unifiedTCI-StateType-r17 in MIMOparam-r17 in ServingCellConfig, which is an upper layer signaling, is set to joint. 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. In addition, all D / U fields located from the fourth octet to the first bit in Fig. 6 can be regarded as R fields, and all corresponding R fields can be set to 0 bits.

[0162] [CSI resource configuration]

[0163] NR has a Channel State Information (CSI) framework that directs base stations to measure and report channel state information (CSI) for terminals. The NR CSI framework can consist of at least two elements: resource settings and report settings. Report settings can reference at least one ID of resource settings to establish a connection relationship with each other.

[0164] According to one embodiment of the present disclosure, resource settings may include information related to a reference signal (RS) for measuring channel state information by a terminal. The base station may configure at least one resource setting for the terminal. For example, the base station and the terminal may exchange signaling information as shown in [Table 4] to convey information regarding resource settings.

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

[0166] In [Table 4], the signaling information CSI-ResourceConfig contains information about each resource setting. According to the signaling information, each resource setting may include a resource setting index (csi-ResourceConfigId) or a BWP index (bwp-ID) or a time-domain transmission configuration of the resource (resourceType) or a resource set list (csi-RS-ResourceSetList) including at least one resource set. The time-domain transmission configuration of the resource may be set to aperiodic transmission, semi-persistent transmission or periodic transmission. The resource set list may be a set including a resource set for channel measurement or a set including a resource set for interference measurement. If the resource set list is a set including resource sets for channel measurement, each resource set may include at least one resource, which may be an index of a channel state information reference signal (CSI-RS) resource or a synchronization / broadcast channel block (SS / PBCH block, SSB). If the resource set list is a set including resource sets for interference measurement, each resource set may include at least one interference measurement resource (CSI interference measurement, CSI-IM).

[0167] For example, if the resource set includes CSI-RS, the base station and the terminal can exchange signaling information as in [Table 5] to convey information about the resource set.

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

[0169] 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 about a resource set index (nzp-CSI-ResourceSetId) or a set of indexes of CSI-RSs included (nzp-CSI-RS-Resources), and may include part of information about a spatial domain transmission filter of the included CSI-RS resource (repetition) or whether the included CSI-RS resource is used for tracking (trs-Info).

[0170] CSI-RS may be the most representative reference signal included in a resource set. The base station and terminal can exchange signaling information, as shown in [Table 6], to convey information about CSI-RS resources.

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

[0172] In [Table 6], the signaling information NZP-CSI-RS-Resource contains information about each CSI-RS. The information contained in the signaling information NZP-CSI-RS-Resource may have the following meanings.

[0173] - nzp-CSI-RS-ResourceId: CSI-RS resource index

[0174] - resourceMapping: Resource mapping information for CSI-RS resources

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

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

[0177] - scramblingID: scrambling index of the CSI-RS sequence

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

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

[0180] The resourceMapping included in the above signaling information NZP-CSI-RS-Resource indicates resource mapping information of the CSI-RS resource, and may include frequency resource 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 set through this may have a value set in one of the rows of [Table 7] below.

[0181]

[0182] [Table 7] shows the frequency resource density, CDM type, CSI-RS component RE pattern frequency axis and time axis start position that can be set 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 configuring 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 position may be designated without limitation of subcarriers in a PRB (Physical Resource Block), and the CSI-RS RE position may be designated 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 positions can be specified for every two subcarriers in the PRB, and the CSI-RS RE positions can be specified by a 6-bit bitmap. When the number of CSI-RS ports is 4 ports and Y=4, CSI-RS RE positions can be specified for every four subcarriers in the PRB, and the CSI-RS RE positions can be specified by a 3-bit bitmap. Similarly, time axis RE positions can be specified by a bitmap of a total of 14 bits.

[0183] [CSI report configuration]

[0184] According to one embodiment of the present disclosure, a report setting can have a connection relationship with at least one ID of a resource setting by referencing the ID of the resource setting, and the resource setting(s) having a connection relationship with the report setting provide configuration information including information on 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 can be used for reporting channel information according to a reporting method set in the report setting having the connection relationship.

[0185] According to one embodiment of the present disclosure, report settings may include configuration information related to a CSI reporting method. For example, a base station and a terminal may exchange signaling information as shown in [Table 8] to convey information regarding report settings.

[0186] -- 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]]}.

[0187] In [Table 8], the signaling information CSI-ReportConfig contains information about each report setting. The information contained in the signaling information CSI-ReportConfig may have the following meanings.

[0188] - reportConfigId: report setting index

[0189] - carrier: serving cell index

[0190] - resourcesForChannelMeasurement: resource setting index for channel measurement that has a relationship with report settings

[0191] - csi-IM-ResourcesForInterference: Resource setting index containing CSI-IM resources for interference measurement that have a relationship with report settings.

[0192] - nzp-CSI-RS-ResourcesForInterference: Resource setting index containing CSI-RS resources for interference measurement that are linked to report settings.

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

[0194] - reportQuantity: Indicates the type of channel information to be reported. It can have the types of channel information ('cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RI-LI-PMI-CQI') when no channel report is transmitted and when a channel report is transmitted. Here, the elements included in the types of channel information mean 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).

[0195] - reportFreqConfiguration: Indicates whether the channel information being reported includes only information about the entire wideband or information about each subband. If it includes information about each subband, it can have configuration information about the subband that contains the channel information.

[0196] - timeRestrictionForChannelMeasurements: Whether the reference signal for channel measurement among the reference signals referenced by the reported channel information has a time axis restriction.

[0197] - timeRestrictionForInterferenceMeasurements: Whether the time axis of the reference signal for interference measurement is restricted among the reference signals referenced by the reported channel information.

[0198] - codebookConfig: Codebook information referenced by the channel information being reported

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

[0200] - cqi-Table: CQI table index referenced by the reported channel information

[0201] - subbandSize: Index indicating the subband size of channel information

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

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

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

[0205] For example, a base station can instruct a terminal to perform an aperiodic channel information report (CSI report) through higher layer signaling or DCI using DCI format 0_1. The base station sets a parameter for the aperiodic CSI report of the terminal, or a plurality of CSI report trigger states including parameters for the CSI report, through higher layer signaling. The parameters for the CSI report or the CSI report trigger states can include a set including a slot interval or a possible slot interval between a PDCCH including the DCI and a PUSCH including the CSI report, a reference signal ID for channel state measurement, a type of channel information to be included, etc. When the base station instructs the terminal to perform some of the multiple CSI report trigger states through the DCI, the terminal reports channel information according to the CSI report settings of the report settings set in the instructed CSI report trigger states. The channel information reporting can be performed through a PUSCH scheduled with DCI format 0_1. The time domain resource allocation of the PUSCH including the CSI report of the terminal can be performed through the slot interval with the PDCCH indicated through the DCI, the start symbol and symbol length indication within the slot for the time domain resource allocation of the PUSCH, etc. For example, the position of the slot in which the PUSCH including the CSI report of the terminal is transmitted can be indicated through the slot interval with the PDCCH indicated through the DCI, and the start symbol and symbol length within the slot can be indicated through the time domain resource assignment field of the DCI described above.

[0206] For example, a base station can instruct a terminal to transmit a semi-persistent CSI report on the PUSCH via DCI using DCI format 0_1. The base station can activate or deactivate the semi-persistent CSI report transmitted on the PUSCH via DCI scrambled with SP-CSI-RNTI. When the semi-persistent CSI report is activated, the terminal can periodically report channel information according to the configured slot interval. When the semi-persistent CSI report is deactivated, the terminal can stop the activated periodic channel information reporting. The base station configures a parameter for the terminal's semi-persistent CSI report or multiple CSI report trigger states including the parameters for the semi-persistent CSI report through upper layer signaling. Parameters for a CSI report, or a CSI report trigger state, may include a slot interval or a set including possible slot intervals between a PDCCH including DCI indicating a CSI report and a PUSCH including the CSI report, a slot interval between a slot in which upper layer signaling indicating a CSI report is activated and a PUSCH including the CSI report, a slot interval period of the CSI report, a type of channel information included, etc. When a base station activates some of a plurality of CSI report trigger states or some of a plurality of report settings for a terminal through upper layer signaling or DCI, the terminal may report channel information according to a report setting included in the indicated CSI report trigger state or a CSI report setting set in an activated report setting.The above channel information reporting can be performed through a PUSCH that is semi-persistently scheduled with DCI format 0_1 ​​scrambled with SP-CSI-RNTI. The time domain resource allocation of the PUSCH including the CSI report of the terminal can be performed through the slot interval period of the CSI report, the slot interval with respect to the slot in which upper layer signaling is activated, the slot interval with respect to the PDCCH indicated through DCI, the start symbol and symbol length indication within the slot for time domain resource allocation of the PUSCH, etc. For example, the position of the slot in which the PUSCH including the CSI report of the terminal is transmitted can be indicated through the slot interval with respect to the PDCCH indicated through DCI, and the start symbol and symbol length within the slot can be indicated through the time domain resource assignment field of the DCI format 0_1 ​​described above.

[0207] For example, a base station can instruct a terminal to transmit a semi-persistent CSI report to a PUCCH through upper layer signaling such as MAC-CE. Through the MAC-CE signaling, the base station can activate or deactivate the semi-persistent CSI report transmitted to the PUCCH. When the semi-persistent CSI report is activated, the terminal can periodically report channel information according to the configured slot interval. When the semi-persistent CSI report is deactivated, the terminal can stop the activated periodic channel information reporting. The base station configures parameters for the semi-persistent CSI report of the terminal through upper layer signaling. The parameters for the CSI report can include a PUCCH resource through which the CSI report is transmitted, a slot interval period of the CSI report, the type of channel information included, etc. The terminal can transmit the CSI report through the PUCCH. Alternatively, if the PUCCH for the CSI report overlaps with the PUSCH, the CSI report can be transmitted through the PUSCH. The location of the PUCCH transmission slot including the CSI report can be indicated through the slot interval period of the CSI report set through upper layer signaling, the slot interval between the slot in which the upper layer signaling is activated and the PUCCH including the CSI report, and the start symbol and symbol length within the slot can be indicated through the start symbol and symbol length to which the PUCCH resource is allocated set through upper layer signaling.

[0208] For example, a base station can instruct a terminal to perform a periodic CSI report through upper layer signaling. The base station can activate or deactivate the periodic CSI report through upper layer signaling including RRC signaling. When the periodic CSI report is activated, the terminal can periodically report channel information according to a configured slot interval. When the periodic CSI report is deactivated, the terminal can stop the activated periodic channel information reporting. The base station configures a report setting including parameters for the terminal's periodic CSI report through upper layer signaling. The parameters for the CSI report can include a PUCCH resource setting for the CSI report, a slot interval between a slot in which upper layer signaling indicating the CSI report is activated and a PUCCH including the CSI report, a slot interval period of the CSI report, a reference signal ID for channel state measurement, the type of channel information included, etc. The terminal can transmit the CSI report through the PUCCH. Alternatively, if the PUCCH for the CSI report overlaps with the PUSCH, the CSI report can be transmitted on the PUSCH. The position of the slot in which the PUCCH including the CSI report is transmitted can be indicated through the slot interval period of the CSI report set through upper layer signaling, the slot interval between the slot in which the upper layer signaling is activated and the PUCCH including the CSI report, and the start symbol and symbol length within the slot can be indicated through the start symbol and symbol length to which the PUCCH resource is allocated set through upper layer signaling.

[0209] For the aforementioned CSI report setting (CSI-ReportConfig), each report setting CSI-ReportConfig can be associated with one downlink (DL) bandwidth part identified by the upper layer parameter bandwidth part identifier (bwp-id) given by the CSI resource setting, CSI-ResourceConfig, associated with the corresponding report setting. For the time domain reporting operation for each report setting CSI-ReportConfig, 'Aperiodic', 'Semi-Persistent', and 'Periodic' methods are supported, which can be configured from the base station to the terminal by the reportConfigType parameter configured from the upper layer. The semi-persistent CSI reporting method supports 'PUCCH-based semi-persistent (semi-PersistentOnPUCCH)' and 'PUSCH-based semi-persistent (semi-PersistentOnPUSCH)'. For periodic or semi-permanent CSI reporting methods, the UE can receive PUCCH or PUSCH resources for transmitting CSI from the base station through higher-layer signaling. The period and slot offset of the PUCCH or PUSCH resources for transmitting CSI can be given as numerology of the uplink (UL) bandwidth portion configured for CSI report transmission. For aperiodic CSI reporting methods, the UE can receive scheduling of PUSCH resources for transmitting CSI from the base station through L1 signaling (the aforementioned DCI format 0_1).

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

[0211] - CSI-IM resources for interference measurements

[0212] - NZP CSI-RS resources for interference measurements

[0213] - NZP CSI-RS resources for channel measurements

[0214] For CSI-RS resource sets associated with resource settings where the upper layer parameter resourceType is set to 'aperiodic', 'periodic', or 'semi-persistent', the trigger state for the CSI report setting where reportType is set to 'aperiodic' and the resource settings for channel or interference measurements for one or more component cells (CCs) can be set with the upper layer parameter CSI-AperiodicTriggerStateList.

[0215] Aperiodic CSI reporting of a terminal can utilize PUSCH, periodic CSI reporting can utilize PUCCH, and semi-persistent CSI reporting can be performed using PUSCH when triggered or activated by DCI, or PUCCH after activation by MAC control element (MAC CE). As mentioned above, CSI resource settings can also be configured as aperiodic, periodic, or semi-persistent. Combinations between CSI reporting settings and CSI resource settings can be supported based on [Table 9] below.

[0216] Table 5.2.1.4-1: Triggering / Activation of CSI Reporting for the possible CSI-RS Configurations.

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

[0218] Aperiodic CSI reporting can be triggered by the "CSI request" field of the aforementioned DCI format 0_1 ​​corresponding to scheduling DCI for PUSCH. The UE can monitor the PDCCH, acquire the DCI format 0_1, and acquire scheduling information and a CSI request indicator for the PUSCH. The CSI request indicator can be set to NTS (=0, 1, 2, 3, 4, 5, or 6) bits and can be determined by higher layer signaling (reportTriggerSize). One of one or more aperiodic CSI reporting trigger states that can be set by higher layer signaling (CSI-AperiodicTriggerStateList) can be triggered by the CSI request indicator.

[0219] - If all bits in the CSI request field are 0, this may mean that no CSI report is requested.

[0220] - If the number of CSI trigger states (M) in the configured CSI-AperiodicTriggerStateLite is greater than 2NTs-1, M CSI trigger states can be mapped to 2NTs-1 according to the mapping relationship defined, and one of the trigger states of 2NTs-1 can be indicated by the CSI request field.

[0221] - 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 can be indicated by the CSI request field.

[0222] [Table 10] below shows an example of the relationship between a CSI request indicator and the CSI trigger state that can be indicated by the indicator.

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

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

[0225] Figure 7 is a diagram illustrating an example of an aperiodic CSI reporting method.

[0226] In an example (700) of FIG. 7, the terminal can monitor the PDCCH (701) to obtain DCI format 0_1, from which it can obtain scheduling information and CSI request information for the PUSCH (705). The terminal can obtain resource information for the CSI-RS (702) to be measured from the received CSI request indicator. The terminal can determine when to perform measurement on the transmitted CSI-RS (702) resource based on the time point of receiving DCI format 0_1 ​​and the parameter (aperiodicTriggeringOffset described above) for the offset in the CSI resource set configuration (e.g., NZP CSI-RS resource set configuration (NZP-CSI-RS-ResourceSet)). More specifically, the terminal can receive an offset value X of the parameter aperiodicTriggeringOffset in the NZP-CSI-RS resource set configuration from the base station through upper layer signaling, and the set offset value X can mean an offset between a slot in which a DCI that triggers aperiodic CSI reporting is received and a slot in which a CSI-RS resource is transmitted. For example, the aperiodicTriggeringOffset parameter value and the offset value X can have a mapping relationship described in [Table 11] below.

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

[0228] An example (700) of Fig. 7 shows an example in which the aforementioned offset value is set to X=0. In this case, the terminal can receive the CSI-RS (702) in a slot (corresponding to slot 0 (706) of Fig. 7) in which the DCI format 0_1 ​​that triggers the aperiodic CSI report is received, and can report the CSI information measured with the received CSI-RS to the base station through the PUSCH (705). The terminal can obtain scheduling information (information corresponding to each field of the aforementioned DCI format 0_1) for the PUSCH (705) for CSI reporting from the DCI format 0_1. As an example, the terminal can obtain information on a slot in which the PUSCH (705) is to be transmitted from the aforementioned time domain resource allocation information for the PUSCH (705) in the DCI format 0_1. In an example (700) of FIG. 7, the terminal acquires a K2 value corresponding to a slot offset value for PDCCH-to-PUSCH as 3, and accordingly, the PUSCH (705) can be transmitted in slot 3 (709), which is 3 slots away from slot 0 (706), at the time when the PDCCH (701) is received.

[0229] In an example (710) of FIG. 7, the terminal can monitor the PDCCH (711) to obtain DCI format 0_1, and from this, can obtain scheduling information and CSI request information for the PUSCH (715). The terminal can obtain resource information for the CSI-RS (712) to be measured from the received CSI request indicator. An example (710) of FIG. 7 shows an example in which the offset value for the aforementioned CSI-RS is set to X=1. In this case, the terminal can receive the CSI-RS (712) in a slot (corresponding to slot 0 (716) of FIG. 7) in which the DCI format 0_1 ​​that triggers aperiodic CSI reporting is received, and can report the CSI information measured with the received CSI-RS to the base station through the PUSCH (715).

[0230] An aperiodic CSI report may include at least one or both of CSI part 1 and CSI part 2, and when the aperiodic CSI report is transmitted via PUSCH, it may be multiplexed with a transport block. For multiplexing, a CRC is inserted into the input bits of the aperiodic CSI, and after encoding and rate matching, it may be mapped to a resource element in the PUSCH in a specific pattern and transmitted. The 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 when multiplexing CSI Part 1 or CSI part 2 included in the aperiodic CSI report may be calculated as shown in [Table 12] below.

[0231]

[0232]

[0233] In particular, in the case of PUSCH repetition transmission methods A and B, the UE can transmit the aperiodic CSI report by multiplexing it only in the first repetition transmission among the PUSCH repetition transmissions. This is because the aperiodic CSI report information to be multiplexed is encoded in a polar code manner, and in this case, in order to be multiplexed in multiple PUSCH repetitions, each PUSCH repetition must have the same frequency and time resource allocation. In particular, in the case of PUSCH repetition type B, each actual repetition can have a different OFDM symbol length, so the aperiodic CSI report can be multiplexed and transmitted only in the first PUSCH repetition.

[0234] In addition, for PUSCH repetition transmission scheme B, if the UE schedules aperiodic CSI reporting without scheduling a transport block or receives a DCI activating semi-persistent CSI reporting, the nominal repetition value may be assumed to be 1 even if the number of PUSCH repetition transmissions configured by upper layer signaling is greater than 1. In addition, if the UE schedules or activates aperiodic or semi-persistent CSI reporting without scheduling a transport block based on PUSCH repetition transmission scheme B, the UE may expect the first nominal repetition to be the same as the first actual repetition. For a PUSCH transmitted including semi-persistent CSI based on PUSCH repetition transmission scheme B without scheduling a DCI after semi-persistent CSI reporting is activated by DCI, if the first nominal repetition is different from the first actual repetition, the transmission for the first nominal repetition may be ignored.

[0235] [CSI computation time]

[0236] When a base station instructs a terminal to perform an aperiodic CSI report or a semi-persistent CSI report through DCI, the terminal can determine whether or not a valid channel report can be performed through the instructed CSI report by considering the channel calculation time (CSI computation time) required for the CSI report. For an aperiodic CSI report or a semi-persistent CSI report instructed through DCI, the terminal can perform a valid CSI report starting from the uplink symbol following the Z symbol after the last symbol included in the PDCCH including the DCI instructing the CSI report. The Z symbol described above may vary depending on the numerology of the downlink bandwidth part to which the PDCCH including the DCI instructing the CSI report corresponds, the numerology of the uplink bandwidth part to which the PUSCH transmitting the CSI report corresponds, and the type or characteristics (report quantity, frequency band granularity, number of ports of the reference signal, codebook type, etc.) of the channel information reported in the CSI report. In other words, in order for a CSI report to be judged as a valid CSI report (if the CSI report is a valid CSI report), the uplink transmission of the CSI report must not be performed before the Zref symbol, including the timing advance. In this case, the Zref symbol is the time starting from the moment when the last symbol of the triggering PDCCH ends. This is the uplink symbol that starts the CP (cyclic prefix). Here, the detailed value of Z is as described below. κ=64, and μ is the numerology. Here, μ is ( ) is the largest It can be promised that it will use what causes the value, is the subcarrier spacing used for PDCCH transmission, is the subcarrier spacing used for CSI-RS transmission, may refer to the subcarrier spacing of the uplink channel used for transmitting UCI (Uplink control information) for CSI reporting. As another example, μ is ( , ) is the largest It is also possible to promise to use something that causes a value. and The definition of is referred to above. For convenience of future explanation, satisfying the above conditions is referred to as satisfying CSI reporting validity condition 1.

[0237] In addition, if the reference signal for channel measurement for an aperiodic CSI report indicated to a terminal through DCI is an aperiodic reference signal, a valid CSI report can be performed starting from the uplink symbol after the Z' symbol after the last symbol including the reference signal ends, and the above-mentioned Z' symbol may vary depending on the numerology of the downlink bandwidth part corresponding to the PDCCH including the DCI indicating the CSI report, the numerology of the bandwidth corresponding to the reference signal for channel measurement for the CSI report, the numerology of the uplink bandwidth part corresponding to the PUSCH transmitting the CSI report, and the type or characteristics of the channel information reported in the CSI report (report quantity, frequency band granularity, number of ports of the reference signal, codebook type, etc.). In other words, in order for a CSI report to be determined to be a valid CSI report (if the CSI report is a valid CSI report), the uplink transmission of the CSI report must not be performed before the Zref' symbol, including the timing advance. At this time, the Zref' symbol starts from the moment when the last symbol of the aperiodic CSI-RS or aperiodic CSI-IM triggered by the triggering PDCCH ends. This is an uplink symbol that starts CP (cyclic prefix). Here, the detailed value of Z' is explained below. , κ=64, and μ is the numerology. Here, μ is ( , ) is the largest It can be promised that it will use what causes the value, is the subcarrier spacing used for triggering PDCCH transmission, is the subcarrier spacing used for CSI-RS transmission, may refer to the subcarrier spacing of the uplink channel used for transmitting UCI (Uplink control information) for CSI reporting. As another example, μ is ( , ) is the largest It can be promised that the value will be used. At this time, and The definition of is referred to above. For convenience of future explanation, satisfying the above conditions is referred to as satisfying CSI reporting validity condition 2.

[0238] If the base station instructs the terminal to perform an aperiodic CSI report for an aperiodic reference signal through DCI, the terminal can perform a valid CSI report starting from the first uplink symbol that satisfies both the point in time Z symbols after the last symbol included in the PDCCH including the DCI indicating the CSI report and the point in time Z' symbols after the last symbol including the reference signal. That is, in the case of aperiodic CSI reporting based on the aperiodic reference signal, both CSI reporting validity conditions 1 and 2 must be satisfied to be considered a valid CSI report.

[0239] If the CSI report time indicated by the base station does not satisfy the CSI computation time requirement, the terminal may determine the CSI report to be invalid and may not consider updating the channel information status for the CSI report.

[0240] The Z, Z' symbols for calculating the CSI computation time mentioned above follow [Table 13] and [Table 14] below. For example, if the channel information reported in the CSI report includes only wideband information, the number of ports of the reference signal is 4 or less, there is one reference signal resource, and the codebook type is 'typeI-SinglePanel' or the type of channel information to be reported (report quantity) is 'cri-RI-CQI', the Z, Z' symbols follow [Table 14]. follows the value. This will be referred to as delay requirement 2 in the future. In addition, if the PUSCH containing the CSI report does not contain TB or HARQ-ACK and the CPU occupation of the terminal is 0, the Z and Z' symbols are as in [Table 13]. The value is followed and is named as delay requirement 1. The description of the CPU occupation mentioned above is described in detail below. In addition, when the report quantity is 'cri-RSRP' or 'ssb-Index-RSRP', the Z, Z' symbols are as shown in [Table 14]. Follow the values. X1, X2, X3, and X4 in [Table 14] represent the UE capability for beam reporting time, and KB1 and KB2 in [Table 14] represent the UE capability for beam change time. In case it does not correspond to the type or characteristic of channel information reported in the above-mentioned CSI report, the Z and Z' symbols are in [Table 14]. Follow the value.

[0241] [symbols] 0108113112252134336

[0242]

[0243] [CSI reference resource]

[0244] When a base station instructs a terminal to perform an aperiodic / semi-persistent / periodic CSI report, it may configure a CSI reference resource to determine a reference time and frequency for a channel to be reported in the CSI report. The frequency of the CSI reference resource may be the carrier and subband information for measuring CSI, which are indicated in the CSI report configuration, and these may correspond to the carrier and reportFreqConfiguration in the upper layer signaling CSI-ReportConfig, respectively. The time of the CSI reference resource may be defined based on the time at which the CSI report is transmitted. For example, when instructing to transmit CSI report #X in the uplink slot n' of the carrier and BWP where the CSI report is to be transmitted, the time of the CSI reference resource of CSI report #X may be defined as the carrier on which the CSI report is to be transmitted and the downlink slot n of the BWP, n-nCSI-ref. Downlink slot n is named as μDL for the carrier measuring CSI and the numerology of BWP, and μUL for the carrier transmitting CSI report #X and the numerology of BWP. It is calculated as follows. The slot interval between the downlink slot n and the CSI reference signal, nCSI-ref, is the number of CSI-RS / SSB resources for channel measurement when the CSI report #X transmitted in the uplink slot n' is a semi-persistent or periodic CSI report. If a single CSI-RS / SSB resource is connected to the corresponding CSI report, , and if multiple CSI-RS / SSB resources are connected to the corresponding CSI report. If the CSI report #X transmitted in uplink slot n' is an aperiodic CSI report, the CSI computation time Z' for channel measurement is considered. is calculated as mentioned above is the number of symbols contained in one slot, and in NR Assume =14.

[0245] When a base station instructs a terminal to transmit a CSI report in uplink slot n' through upper layer signaling or DCI, the terminal may report CSI by performing channel measurement or interference measurement on a CSI-RS resource, CSI-IM resource, or SSB resource that is transmitted no later than the CSI reference resource slot of the CSI report transmitted in uplink slot n' among the CSI-RS resources, CSI-IM, or SSB resources associated with the CSI report. The CSI-RS resource, CSI-IM resource, or SSB resource associated with the above-mentioned CSI report may mean a CSI-RS resource, CSI-IM resource, or SSB resource included in a resource set set in a resource setting referenced by a report setting for a CSI report of a terminal set through upper layer signaling, or a CSI-RS resource, CSI-IM resource, or SSB resource referenced by a CSI report trigger state including parameters for the CSI report, or a CSI-RS resource, CSI-IM resource, or SSB resource indicated by an ID of a reference signal (RS) set.

[0246] In embodiments of the present disclosure, a CSI-RS / CSI-IM / SSB occasion refers to a transmission time of CSI-RS / CSI-IM / SSB resource(s) determined by a higher layer configuration or a combination of the higher layer configuration and DCI triggering. For example, a semi-persistent or periodic CSI-RS resource determines a slot to be transmitted according to a slot period and slot offset configured by higher layer signaling, and the transmission symbol(s) within the slot are determined according to resource mapping information (resourceMapping). As another example, an aperiodic CSI-RS resource determines a slot to be transmitted according to a slot offset from a PDCCH including a DCI indicating channel reporting configured by higher layer signaling, and the transmission symbol(s) within the slot are determined according to resourceMapping information.

[0247] The above-mentioned CSI-RS occasion can be determined by independently considering the transmission time of each CSI-RS resource or by comprehensively considering the transmission time of one or more CSI-RS resource(s) included in the resource set, and accordingly, the following two interpretations are possible for the CSI-RS occasion according to each resource set configuration.

[0248] Interpretation 1-1: The time from the start of the earliest symbol to the end of the latest symbol in which one or more specific resources among the CSI-RS resources included in the resource set(s) set in the resource setting referenced by the report setting set for the CSI report are transmitted.

[0249] Interpretation 1-2: Among all CSI-RS resources included in the resource set(s) set in the resource setting referenced by the report setting set for the CSI report, the time from the start of the earliest symbol transmitted by the CSI-RS resource to the end of the latest symbol transmitted by the CSI-RS resource

[0250] In the embodiments of the present disclosure below, it is possible to consider both interpretations of CSI-RS occasions and apply them individually. Furthermore, it is possible to consider both interpretations for CSI-IM occasions and SSB occasions, similar to CSI-RS occasions. However, since the principles are similar to those described above, any redundant explanation will be omitted below.

[0251] In embodiments of the present disclosure, 'CSI-RS / CSI-IM / SSB occasion' for CSI report #X transmitted in 'uplink slot n' means a set of CSI-RS occasions, CSI-IM occasions, and SSB occasions that are not later than the CSI reference resource of CSI report #X transmitted in 'uplink slot n' among CSI-RS resources, CSI-IM resources, and SSB resources included in a resource set set in a resource setting referenced by a report setting set for CSI report #X.

[0252] In the embodiments of the present disclosure, the latest CSI-RS / CSI-IM / SSB occasion among the CSI-RS / CSI-IM / SSB occasions for CSI report #X transmitted in 'uplink slot n' can be interpreted in the following two ways.

[0253] Interpretation 2-1: A set of occasions including the latest CSI-RS occasion among the CSI-RS occasions for CSI report #X transmitted in uplink slot n', the latest CSI-IM occasion among the CSI-RS occasions for CSI report #X transmitted in uplink slot n', and the latest SSB occasion among the SSB occasions for CSI report #0 transmitted in uplink slot n'.

[0254] Interpretation 2-2: The latest occasion among all CSI-RS occasions, CSI-IM occasions, and SSB occasions for CSI report #X transmitted in uplink slot n'

[0255] In the embodiments of the present disclosure, it is possible to individually apply both interpretations of the “latest CSI-RS / CSI-IM / SSB occasion among the CSI-RS / CSI-IM / SSB occasions for CSI report #X transmitted in uplink slot n”. In addition, when the two interpretations (Interpretation 1-1, Interpretation 1-2) for the CSI-RS occasion, CSI-IM occasion, and SSB occasion described above are considered, in the embodiments of the present disclosure, it is possible to individually apply the “latest CSI-RS / CSI-IM / SSB occasion among the CSI-RS / CSI-IM / SSB occasions for CSI report #X transmitted in uplink slot n” by considering all four different interpretations (applying Interpretation 1-1 and Interpretation 2-1, applying Interpretation 1-1 and Interpretation 2-2, applying Interpretation 1-2 and Interpretation 2-1, applying Interpretation 1-2 and Interpretation 2-2).

[0256] The base station can instruct the CSI report by considering the amount of channel information that the terminal can calculate simultaneously for the CSI report, i.e. the number of channel information calculation units (CSI processing units, CPUs) of the terminal. The number of channel information calculation units that the terminal can calculate simultaneously is N. CPU If so, the terminal is N CPU Do not expect CSI report instructions from base stations that require more channel information calculations, or N CPU We may not consider updating channel information that requires more channel information calculations. N CPU The terminal can report to the base station through upper layer signaling or the base station can set it through upper layer signaling.

[0257] The CSI report that the base station instructs the terminal is the total number of channel information that the terminal can calculate simultaneously, N. CPU Assume that some or all of the CPU is occupied for channel information calculation. For each CSI report, for example, the number of channel information calculation units required for CSI report n (n=0,1,…,N-1) is Then, the number of channel information calculation units required for a total of N CSI reports is It can be said that. The calculation unit of channel information required for each reportQuantity set in the CSI report can be set as shown in [Table 15] below.

[0258]

[0259] The number of channel information calculations required by a terminal for multiple CSI reports at a given point in time is the number of channel information calculation units that the terminal can calculate simultaneously, N. CPUIf there are more than this, the terminal may not consider updating channel information for some CSI reports. Among the multiple indicated CSI reports, the CSI reports that do not consider updating channel information are determined at least by considering the CPU time required for calculating channel information for the CSI report and the priority of the channel information being reported. For example, the channel information update may not be considered for the CSI report whose channel information calculation requires the latest CPU time, and it is also possible to preferentially not consider updating channel information for CSI reports with lower channel information priorities.

[0260] The priority of the above channel information can be determined by referring to [Table 16] below.

[0261]

[0262] The CSI priority for the CSI report is determined through the priority value PriiCSI(y,k,c,s) in [Table 16].

[0263] Referring to [Table 16], the CSI priority value is determined through the type of channel information included in the CSI report, the time axis reporting characteristics of the CSI report (aperiodic, semi-persistent, periodic), the channel on which the CSI report is transmitted (PUSCH, PUCCH), the serving cell index, and the CSI report configuration index. The CSI priority for a CSI report is determined by comparing the priority values ​​PriiCSI(y,k,c,s) and determining that the CSI priority for a CSI report with a smaller priority value is higher.

[0264] If the time taken by the CPU to calculate the channel information required for the CSI report instructed by the base station to the terminal is called CPU occupation time, then the CPU occupation time is determined by considering the type of channel information included in the CSI report (report quantity), the time axis characteristics of the CSI report (aperiodic, semi-persistent, periodic), the slot or symbol occupied by the upper layer signaling or DCI indicating the CSI report, and part or all of the slot or symbol occupied by the reference signal for channel state measurement.

[0265] [PDCCH: DCI related]

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

[0267] In a 5G system, scheduling information for uplink data (e.g., physical uplink shared channel (PUSCH)) or downlink data (e.g., physical downlink shared channel (PDSCH)) is transmitted from a base station to a terminal via DCI. The terminal can monitor a DCI format for fallback and a DCI format for non-fallback for the PUSCH or PDSCH. The fallback DCI format can be composed of fixed fields defined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.

[0268] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after going through the channel coding and modulation process. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the UE. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly, but is included in the CRC calculation process. When the UE receives a DCI message transmitted on the PDCCH, it verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the UE can determine that the message was transmitted to the UE.

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

[0270] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, and the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI can include, for example, the information in [Table 17] below.

[0271]

[0272] DCI format 0_1 ​​can be used as a fallback DCI for scheduling PUSCH, and the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI can include, for example, the information in [Table 18] below.

[0273]

[0274]

[0275]

[0276] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, and the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI can include, for example, the information in [Table 19] below.

[0277]

[0278] DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, and the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include, for example, the information in [Table 20] below.

[0279]

[0280]

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

[0282] Below, the downlink control channel in a 5G communication system will be described in more detail with reference to drawings.

[0283] FIG. 8 is a diagram illustrating an example of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 8 illustrates an example in which two control regions (Control Region #1 (801), Control Region #2 (802)) are set within a UE bandwidth part (810) in the frequency axis and within one slot (820) in the time axis. The control regions (801, 802) may be set to specific frequency resources (803) within the entire UE bandwidth part (810) in the frequency axis. The time axis may be set to one or more OFDM symbols, which may be defined as the control region length (Control Resource Set Duration, 804). Referring to the example illustrated in FIG. 8, Control Region #1 (801) is set to a control region length of two symbols, and Control Region #2 (802) is set to a control region length of one symbol.

[0284] The control region in the aforementioned 5G can be established by the base station to the terminal via higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Establishing a control region for the terminal means providing information such as the control region identifier, frequency location of the control region, and symbol length of the control region. For example, this information may include the information in [Table 21] below.

[0285] ControlResourceSet ::= SEQUENCE {-- Corresponds to L1 parameter 'CORESET-ID' controlResourceSetId ControlResourceSetId,(Control domain identifier (Identity)) frequencyDomainResources BIT STRING (SIZE (45)),(Frequency axis resource allocation information) duration INTEGER (1..maxCoReSetDuration),(Time axis resource allocation information) cce-REG-MappingType CHOICE {(CCE-to-REG mapping method) interleaved SEQUENCE {reg-BundleSize ENUMERATED {n2, n3, n6},(REG bundle size) precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs}, interleaverSize ENUMERATED {n2, n3, n6}(interleaver size) shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL(Interleaved Shift)},nonInterleaved NULL},tci-StatesPDCCH SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL,(QCL setting information)tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, -- Need S}

[0286] In [Table 21], 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 QCL (Quasi Co Located) relationship with the DMRS transmitted in the corresponding control region. FIG. 9 is a diagram showing an example of a basic unit of time and frequency resources constituting a downlink control channel that can be used in 5G. According to FIG. 9, the basic unit of time and frequency resources constituting the control channel can be referred to as a REG (Resource Element Group, 903), and the REG (903) can be defined as 1 OFDM symbol (901) in the time axis and 1 PRB (Physical Resource Block, 902) in the frequency axis, i.e., 12 subcarriers. The base station can configure a downlink control channel allocation unit by concatenating REGs (903). As illustrated in FIG. 9, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (Control Channel Element, 904), 1 CCE (904) can be composed of multiple REGs (903). Taking the REG (903) illustrated in FIG. 9 as an example, if the REG (903) can be composed of 12 REs, and if 1 CCE (904) is composed of 6 REGs (903), 1 CCE (904) can be composed of 72 REs. When a downlink control region is established, the region can be composed of multiple CCEs (904), and a specific downlink control channel can be mapped to one or multiple CCEs (904) and transmitted according to the aggregation level (AL) within the control region.CCEs (904) within the control area are distinguished by numbers, and the numbers of the CCEs (904) can be assigned according to a logical mapping method.

[0287] The basic unit of the downlink control channel illustrated in FIG. 9, that is, the REG (903), may include both the REs to which the DCI is mapped and the areas to which the DMRS (905), which is a reference signal for decoding the REs, is mapped. As shown in FIG. 9, three DMRSs (905) may be transmitted within one REG (903). The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 depending on the aggregation level (AL), 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 a 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 (CCEs) that a terminal must attempt to decode at a given aggregation level. Since there are multiple aggregation levels, each of which can be a set of 1, 2, 4, 8, or 16 CCEs, a terminal can have multiple search spaces. A search space set can be defined as the set of search spaces at all configured aggregation levels.

[0288] Search spaces can be categorized into common search spaces and UE-specific search spaces. A certain group of UEs, or all UEs, can search the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling of system information or paging messages. For example, PDSCH scheduling allocation information for transmitting SIBs, including cell operator information, can be received by searching the common search space of the PDCCH. In the case of the common search space, since a certain group of UEs, or all UEs, must receive the PDCCH, it can be defined as a set of pre-arranged CCEs. Scheduling allocation information for UE-specific PDSCH or PUSCH can be received by searching the UE-specific search space of the PDCCH. The UE-specific search space can be defined UE-specifically as a function of the UE's identity and various system parameters.

[0289] In 5G, parameters for the search space for PDCCH can be configured from the base station to the terminal through higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can configure the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol within the slot 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 corresponding search space, the control region index to be monitored for the search space, etc. to the terminal. For example, the information in [Table 22] below can be included.

[0290] SearchSpace ::= SEQUENCE {-- Identity of the search space. SearchSpaceId = 0 identifies the SearchSpace configured via PBCH (MIB) or ServingCellConfigCommon.searchSpaceId SearchSpaceId,(search space identifier)controlResourceSetId ControlResourceSetId,(control space identifier)monitoringSlotPeriodicityAndOffset CHOICE {(monitoring slot level period)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(monitoring length) INTEGER (2..2559)monitoringSymbolsWithinSlot BIT STRING (SIZE (14)) OPTIONAL,(슬롘 내 나이스 심보)nrofCandidates SEQUENCE {(집성 별보 PDCCH 이리군 수)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},...}.

[0291] According to the configuration information, the base station can set one or more search space sets for the terminal. In some embodiments, the base station can set search space set 1 and search space set 2 for the terminal, and can set the terminal to monitor DCI format A scrambled with X-RNTI in search space set 1 in a common search space, and can set the terminal to monitor DCI format B scrambled with Y-RNTI in search space set 2 in a terminal-specific search space. According to the configuration information, one or more search space sets 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 set as common search spaces, and search space set #3 and search space set #4 may be set as terminal-specific search spaces. In the common search space, the following combinations of DCI formats and RNTIs may be monitored. Of course, the present invention is not limited to the following examples.

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

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

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

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

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

[0297] In a terminal-specific search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these examples.

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

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

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

[0301] - C-RNTI (Cell RNTI): Terminal-specific PDSCH scheduling

[0302] - TC-RNTI (Temporary Cell RNTI): Terminal-specific PDSCH scheduling

[0303] - CS-RNTI (Configured Scheduling RNTI): Semi-statically configured terminal-specific PDSCH scheduling

[0304] - RA-RNTI (Random Access RNTI): PDSCH scheduling in the random access phase

[0305] - P-RNTI (Paging RNTI): PDSCH scheduling where paging is transmitted

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

[0307] - INT-RNTI (Interruption RNTI): Indicates whether pucturing is taking place on the PDSCH.

[0308] - TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Power control command for PUSCH

[0309] - TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Power control command for PUCCH

[0310] - TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Power control command for SRS (sounding reference signal)

[0311] The aforementioned specified DCI formats may follow the definitions in [Table 23] below.

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

[0313] In 5G, the search space of aggregation level L in the control region p and search space set s can be expressed as in [Mathematical Formula 1] below. [Mathematical Formula 1]

[0314]

[0315]

[0316] In 5G, since multiple search space sets can be configured with different parameters (e.g., parameters in [Table 22]), the set of search space sets monitored by a terminal at each point in time can be different. 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 can monitor both search space set #1 and search space set #2 in a specific slot, or can monitor either search space set #1 or search space set #2 in a specific slot.

[0317] [PUCCH: Transmission Related]

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

[0319] PUCCH resources can be broadly categorized into long PUCCH and short PUCCH, depending on the length of the allocated symbols. In NR systems, long PUCCHs have a length of four or more symbols within a slot, while short PUCCHs have a length of two or fewer symbols within a slot.

[0320] More specifically, Long PUCCH can be used for uplink cell coverage enhancement purposes, and thus can be transmitted using DFT-S-OFDM, a single-carrier transmission method, 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 that can be supported and whether terminal multiplexing is supported through Pre-DFT OCC support in front of the IFFT.

[0321] 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 frequency resources equivalent to 1 RB. Control information can be composed of a combination of HARQ-ACK and SR, or each of them. PUCCH format 1 is composed of OFDM symbols containing a demodulation reference signal (or reference signal), DMRS (DeModulation Reference Signal), and OFDM symbols containing UCI, which are repeatedly transmitted.

[0322] For example, if the number of transmission symbols of PUCCH format 1 is 8 symbols, it can be composed of DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol in order from the first start symbol of 8 symbols. The DMRS symbol is an orthogonal code (or orthogonal sequence or spreading code, w) in the time axis in a sequence corresponding to the length of 1 RB in the frequency axis within one OFDM symbol. i (m)) can be spread and transmitted after performing IFFT.

[0323] The UCI symbol is generated by the terminal modulating 1-bit control information with BPSK and 2-bit control information with QPSK to generate d(0), scrambling the generated d(0) by multiplying it by a sequence corresponding to the length of 1 RB in the frequency axis, and then applying an orthogonal code (or orthogonal sequence or spreading code, w) to the scrambled sequence in the time axis. i (m))) can be used to spread the signal and then transmitted after performing IFFT.

[0324] The terminal generates a sequence based on the group hopping or sequence hopping setting and the set ID set by the upper layer signaling from the base station, and cyclically shifts the generated sequence with the initial CS (cyclic shift) value set by the upper layer signal to generate a sequence corresponding to the length of 1 RB.

[0325] w i (m) is the length of the spreading code (NSF) given is determined as follows, for example, spreading code for PUCCH format 1 is given as in [Table 24] below. i means the index of the spreading code itself, and m means the index of the elements of the spreading code. Here, the numbers in [ ] in [Table 24] are , for example, if the length of the spreading code is 2 and the index of the set spreading code is i=0, the spreading code w i (m) is , This is w i (m)=

[0011] .

[0326]

[0327] Next, PUCCH format 3 is a long PUCCH format based on DFT-S-OFDM that can support control information exceeding 2 bits. The number of RBs used can be configured through upper layers. Control information can be composed of HARQ-ACK, SR, and CSI, or a combination thereof. In PUCCH format 3, DMRS symbol locations are presented in [Table 25] below, depending on whether frequency hopping occurs within a slot and whether additional DMRS symbols are configured.

[0328]

[0329] For example, if the number of transmission symbols of PUCCH format 3 is 8 symbols, DMRS is transmitted in the 1st and 5th symbols, starting with the first start symbol of the 8 symbols as 0. [Table 25] is applied in the same way to the DMRS symbol positions of PUCCH format 4.

[0330] Next, PUCCH format 4 is a long PUCCH format based on DFT-S-OFDM that can support control information exceeding 2 bits, and uses frequency resources equivalent to 1 RB. Control information can be composed of HARQ-ACK, SR, and CSI, or a combination thereof. What differentiates PUCCH format 4 from PUCCH format 3 is that PUCCH format 4 can multiplex PUCCH format 4 of multiple terminals within one RB. Multiplexing of PUCCH format 4 of multiple terminals is possible by applying Pre-DFT OCC (Orthogonal Cover Code) to control information before the IFFT. However, the number of control information symbols that can be transmitted by one terminal decreases depending on the number of multiplexed terminals. 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 applicable OCC index can be set through a higher layer.

[0331] Next, let's explain the short PUCCH. The short PUCCH can be transmitted in both the downlink centric slot and the uplink centric slot, and is typically transmitted in the last symbol of the slot or the OFDM symbol at the end (e.g., the last OFDM symbol, the penultimate OFDM symbol, or the last two OFDM symbols). Of course, the short PUCCH can also be transmitted at any location within the slot. The short PUCCH can be transmitted using one OFDM symbol or two OFDM symbols. The short PUCCH can be used to reduce delay compared to the long PUCCH in situations where uplink cell coverage is good, and can be transmitted using the CP-OFDM scheme.

[0332] Short PUCCH can support transmission formats such as PUCCH format 0 and PUCCH format 2 depending on the number of control information bits that can be supported. First, PUCCH format 0 is a short PUCCH format that can support up to 2 bits of control information and uses frequency resources of 1 RB. Control information can be composed of HARQ-ACK and SR, or a combination thereof. PUCCH format 0 does not transmit DMRS, and is structured to transmit only sequences mapped to 12 subcarriers in the frequency axis within one OFDM symbol. The terminal generates a sequence based on the group hopping or sequence hopping setting and the configured ID set by the upper signal from the base station, and adds another CS value depending on whether it is ACK or NACK to the indicated initial CS (cyclic shift) value, and cyclically shifts the generated sequence with the final CS value, and maps it to 12 subcarriers for transmission.

[0333] For example, if HARQ-ACK is 1 bit, the terminal can generate the final CS by adding 6 to the initial CS value if it is ACK, as shown in [Table 26] below, and can generate the final CS by adding 0 to the initial CS if it is NACK. The CS value 0 for NACK and the CS value 6 for ACK are defined in the standard, and the terminal can transmit 1-bit HARQ-ACK by generating PUCCH format 0 according to the values ​​defined in the standard.

[0334]

[0335] For example, if HARQ-ACK is 2 bits, the terminal adds 0 to the initial CS value if (NACK, NACK), adds 3 to the initial CS value if (NACK, ACK), adds 6 to the initial CS value if (ACK, ACK), and adds 9 to the initial CS value if (ACK, NACK) as shown in [Table 27] below. The CS value 0 for (NACK, NACK), the CS value 3 for (NACK, ACK), the CS value 6 for (ACK, ACK), and the CS value 9 for (ACK, NACK) are defined in the standard, and the terminal can transmit 2-bit HARQ-ACK by generating PUCCH format 0 according to the values ​​defined in the standard. If the final CS value exceeds 12 due to the CS value added to the initial CS value depending on ACK or NACK, modulo 12 can be applied to the final CS value because the length of the sequence is 12.

[0336]

[0337] 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 a higher layer. The control information can be composed of a combination of HARQ-ACK, SR, and CSI, or each of them. When the index of the first subcarrier is #0, the location of the subcarrier where the DMRS is transmitted in PUCCH format 2 within one OFDM symbol can be fixed to the subcarriers with indices of #1, #4, #7, and #10. The control information can be mapped to the remaining subcarriers except for the subcarrier where the DMRS is located through a modulation process after channel coding.

[0338] In summary, the values ​​and ranges that can be set for each PUCCH format described above can be summarized as shown in [Table 28] below. In [Table 28] below, values ​​that do not need to be set are indicated as NA.

[0339]

[0340]

[0341] Meanwhile, to improve uplink coverage, multi-slot repetition can be supported for PUCCH formats 1, 3, and 4, and PUCCH repetition can be configured for each PUCCH format. The UE can perform repeated transmissions on PUCCH including UCI as many slots as configured through the upper layer signaling nrofSlots. For repeated PUCCH transmissions, PUCCH transmissions in each slot are performed using the same number of consecutive symbols, and the number of corresponding consecutive symbols can be configured through nrofSymbols in the upper layer signaling PUCCH-format1, PUCCH-format3, or PUCCH-format4.

[0342] For PUCCH repeated transmission, PUCCH transmission in each slot is performed using the same starting symbol, and the corresponding starting symbol can be set through startingSymbolIndex in PUCCH-format 1, PUCCH-format 3, or PUCCH-format 4, which is a higher layer signaling. For PUCCH repeated transmission, a single PUCCH-spatialRelationInfo can be set for a single PUCCH resource. For PUCCH repeated transmission, if the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the terminal can perform frequency hopping on a slot-by-slot basis.

[0343] Additionally, if the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the terminal may start PUCCH transmission from the first PRB index configured through the upper layer signaling startingPRB in even slots, and may start PUCCH transmission from the second PRB index configured through the upper layer signaling secondHopPRB in odd slots. Additionally, if the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the index of the slot instructed to perform the first PUCCH transmission to the terminal is 0, and the PUCCH repetition transmission count value may increase regardless of the PUCCH transmission performed in each slot during the configured total number of PUCCH repetition transmissions.

[0344] If the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the terminal does not expect frequency hopping within the slot when transmitting PUCCH. If the terminal is not configured to perform frequency hopping in PUCCH transmissions in different slots, but is configured to perform frequency hopping within the slot, the first and second PRB indices can be applied equally within the slot. If the number of uplink symbols available for PUCCH transmission is less than nrofSymbols configured by higher layer signaling, the terminal may not transmit the PUCCH. If the terminal fails to transmit the PUCCH in a slot for some reason during repeated PUCCH transmission, the terminal may increase the number of repeated PUCCH transmissions.

[0345] In NR Release 17, the number of slots to be repeatedly transmitted for each PUCCH resource can be configured through the upper layer signaling pucch-RepetitionNrofSlots-r17 in PUCCH-ResourceExt, which is an extension of PUCCH-Resource, which is the upper layer signaling for PUCCH resources. If the upper layer signaling pucch-RepetitionNrofSlots-r17 is configured, the corresponding PUCCH resource is scheduled, and the upper layer signaling nrofSlots is also configured, the UE determines the number of slots to be repeatedly transmitted for the corresponding PUCCH resource through pucch-RepetitionNrofSlots-r17 and ignores the upper layer signaling nrofSlots.

[0346] [PUCCH: PUCCH Resource Setting]

[0347] Next, we describe the PUCCH resource configuration of a base station or terminal. A base station may configure PUCCH resources for specific terminals via higher layers, per BWP. PUCCH resource configurations may be as shown in [Table 29] below.

[0348] 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]]}.

[0349] According to [Table 29], one or more PUCCH resource sets may be configured within the PUCCH resource configuration for a specific BWP, and some of the PUCCH resource sets may be configured with a maximum payload value for UCI transmission. Each PUCCH resource set may include one or more PUCCH resources, and each PUCCH resource may belong to one of the PUCCH formats described above. For the PUCCH resource set, the maximum payload value of the first PUCCH resource set may be fixed to 2 bits. Accordingly, the value may not be separately configured through a higher layer, etc. When the remaining PUCCH resource sets are configured, the indexes of the corresponding PUCCH resource sets may be set in ascending order according to the maximum payload value, and the maximum payload value may not be configured for the last PUCCH resource set. The upper layer configuration for the PUCCH resource set may be as shown in [Table 30] below.

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

[0351] The resourceList parameter in [Table 30] may include the IDs of PUCCH resources belonging to a PUCCH resource set. If the PUCCH resource set is not configured during initial access, a PUCCH resource set consisting of multiple cell-specific PUCCH resources, as shown in [Table 31] below, may be used in the initial BWP. The PUCCH resources to be used for initial access within this PUCCH resource set may be indicated via SIB1.

[0352]

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

[0354] Next, we describe PUCCH resource selection for UCI transmission. For SR transmission, PUCCH resources for SR corresponding to schedulingRequestID can be configured through upper layers, as shown in [Table 32] below. The PUCCH resources can be resources belonging to PUCCH format 0 or PUCCH format 1.

[0355] SchedulingRequestResourceConfig ::= SEQUENCE {schedulingRequestResourceId SchedulingRequestResourceId,schedulingRequestID SchedulingRequestId,periodicityAndOffset CHOICE {sym2 NULL,sym6or7 NULL,sl1 NULL, -- Recurs in every slotsl2 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),sl40 INTEGER (0..39),sl80 INTEGER (0..79),sl160 INTEGER (0..159),sl320 INTEGER (0..319),sl640 INTEGER (0..639)} OPTIONAL, -- Need Mresource PUCCH-ResourceId OPTIONAL -- Need M}

[0356] The configured PUCCH resource can have a transmission period and offset set through the periodicityAndOffset parameter in [Table 32]. If the UE has uplink data to transmit at the time corresponding to the configured period and offset, the corresponding PUCCH resource is transmitted, otherwise the corresponding PUCCH resource may not be transmitted. In the case of CSI transmission, the PUCCH resource to transmit periodic or semi-persistent CSI reports through PUCCH can be set in the pucch-CSI-ResourceList parameter as shown in [Table 33] below. The pucch-CSI-ResourceList parameter can include 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 can be a resource belonging to PUCCH format 2, PUCCH format 3, or PUCCH format 4. The transmission period and offset of the PUCCH resource can be set through reportSlotConfig in [Table 33].

[0357] CSI-ReportConfig ::= SEQUENCE {reportConfigId CSI-ReportConfigId,carrier ServCellIndex OPTIONAL, -- Need S...reportConfigType 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)}},...}

[0358] In the case of HARQ-ACK transmission, the resource set of the PUCCH resource to be transmitted may be first selected based on the payload of the UCI including the HARQ-ACK. That is, the PUCCH resource set having the minimum payload not smaller than the UCI payload may be selected. Next, the PUCCH resource within the PUCCH resource set may be selected through the PUCCH resource indicator (PRI) within the DCI that schedules the TB corresponding to the HARQ-ACK. The PRI may be a PUCCH resource indicator specified in [Table 19] or [Table 20]. The relationship between the PRI and the PUCCH resource selected from the PUCCH resource set may be as shown in [Table 34] below.

[0359]

[0360] If the number of PUCCH resources in the selected PUCCH resource set is greater than 8, the PUCCH resource can be selected by the following [Mathematical Formula 2].

[0361] [Equation 2]

[0362]

[0363] In [Equation 2], r PUCCH is the index of the selected PUCCH resource within the PUCCH resource set, R PUCCH is the number of PUCCH resources belonging to the PUCCH resource set, 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 Indicates the first CCE index for the received DCI.

[0364] The point in time when the corresponding PUCCH resource is transmitted is K1 slots after the TB transmission corresponding to the corresponding HARQ-ACK. The candidate for the K1 value is set by the upper layer, and more specifically,

[0365] It can be set in the dl-DataToUL-ACK parameter in the PUCCH-Config specified in [Table 29]. One of these candidates' K1 values ​​can be selected by the PDSCH-to-HARQ feedback timing indicator in the DCI that schedules the TB, and this value can be a value specified in [Table 18] or [Table 19]. Meanwhile, the unit of the K1 value can be a slot unit or a subslot unit. Here, a subslot is a unit with a length smaller than a slot, and one or more symbols can constitute one subslot.

[0366] Next, we describe the case where two or more PUCCH resources are located within a single slot. A UE can transmit UCI via one or two PUCCH resources within a single slot or subslot. When UCI is transmitted via two PUCCH resources within a single slot / subslot, i) each PUCCH resource does not overlap symbol-wise, and ii) at least one PUCCH resource may be a short PUCCH. Meanwhile, a UE may not expect to transmit multiple PUCCH resources for HARQ-ACK transmission within a single slot.

[0367] [PUSCH: Transmission Method Related]

[0368] Next, we describe the scheduling method for PUSCH transmission. PUSCH transmission can be dynamically scheduled by the UL grant within the DCI or can operate by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission are possible in DCI format 0_0 or 0_1.

[0369] Configured grant Type 1 PUSCH transmissions can be semi-statically scheduled by receiving configuredGrantConfig containing rrc-ConfiguredUplinkGrant of [Table 35] via higher-level signaling, without receiving UL grants in DCI. Configured grant Type 2 PUSCH transmissions can be semi-persistently scheduled by UL grants in DCI after receiving configuredGrantConfig not containing rrc-ConfiguredUplinkGrant of [Table 35] via higher-level signaling.

[0370] When PUSCH transmission operates by configured grant, parameters applied to PUSCH transmission are applied through configuredGrantConfig of upper signaling of [Table 35], except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH provided by pusch-Config of upper signaling of [Table 36]. If the terminal has been provided with transformPrecoder in configuredGrantConfig of upper signaling of [Table 35], the terminal applies tp-pi2BPSK in pusch-Config of [Table 36] for PUSCH transmission operated by configured grant.

[0371]

[0372]

[0373] 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 or non-codebook-based transmission method, respectively, depending on whether the value of txConfig in the upper signaling, pusch-Config in [Table 36], is 'codebook' or 'nonCodebook'.

[0374] As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically set by configured grant. If the UE is instructed to schedule PUSCH transmission via DCI format 0_0, the UE performs beam configuration for PUSCH transmission using pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the minimum ID within the activated uplink BWP within the serving cell, and the PUSCH transmission is based on a single antenna port.

[0375] The UE does not expect scheduling for PUSCH transmission via DCI format 0_0 within a BWP where a PUCCH resource including pucch-spatialRelationInfo is not configured. If the UE does not receive txConfig in pusch-Config of [Table 36], the UE does not expect scheduling via DCI format 0_1.

[0376]

[0377] Next, we describe codebook-based PUSCH transmission. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, or can operate semi-statically based on a configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via a configured grant, the UE determines a precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), Transmission Precoding Matrix Indicator (TPMI), and transmission rank (the number of PUSCH transmission layers).

[0378] SRI can be given through the SRS resource indicator field in DCI or can be set through the upper signaling srs-ResourceIndicator. When transmitting a codebook-based PUSCH, the UE is set with at least one SRS resource, and can be set with up to two. When the UE receives the SRI through DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI.

[0379] The TPMI and transmission rank can be provided through the 'precoding information and number of layers' field in the DCI, or can be configured through the higher-level signaling precodingAndNumberOfLayers. The TPMI is used to indicate the precoder to be applied to PUSCH transmission. If the UE is configured with one SRS resource, the TPMI is used to indicate the precoder to be applied to the configured SRS resource. If the UE is configured with multiple SRS resources, the TPMI is used to indicate the precoder to be applied to the SRS resource indicated by the SRI.

[0380] 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 layer signaling, SRS-Config. In codebook-based PUSCH transmission, the UE determines the codebook subset based on the TPMI and codebookSubset in the upper layer signaling, pusch-Config. The codebookSubset in the upper layer signaling, pusch-Config, can be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the UE to the base station. If the UE reported 'partialAndNonCoherent' as the UE capability, the UE does not expect the value of codebookSubset in the upper layer signaling to be set to 'fullyAndPartialAndNonCoherent'.

[0381] Additionally, if the UE reports 'nonCoherent' as the UE capability, the UE does not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the upper signaling SRS-ResourceSet points to two SRS antenna ports, the UE does not expect the value of the upper signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0382] The terminal can be configured with one SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource in the SRS resource set can be indicated via SRI. If multiple SRS resources are configured in the SRS resource set in which the usage value 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 is set to the same value for all SRS resources.

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

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

[0385] For an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'nonCodebook', the UE can be configured with one connected NZP CSI-RS resource (non-zero power CSI-RS). The UE 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 UE is less than 42 symbols, the UE does not expect information on the precoder for SRS transmission to be updated.

[0386] 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. If the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS is indicated when the value of the field SRS request in DCI format 0_1 ​​or 1_1 is not '00'. The DCI (e.g., DCI format 0_1 ​​or 1_1) must not indicate cross-carrier or cross BWP scheduling. In addition, if the value of the SRS request indicates the presence of an NZP CSI-RS, the NZP CSI-RS is located in the slot in which the PDCCH including the SRS request field is transmitted. The TCI states set for the scheduled subcarriers are not set to QCL-TypeD.

[0387] If a periodic or semi-persistent SRS resource set is configured, the associated NZP CSI-RS can be indicated through the associatedCSI-RS within the upper-level signaling SRS-ResourceSet. For non-codebook-based transmission, the UE does not expect the upper-level signaling spatialRelationInfo for the SRS resource and the associatedCSI-RS within the upper-level signaling SRS-ResourceSet to be configured together.

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

[0389] 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 result measured upon reception of the NZP-CSI-RS. When the terminal transmits one or more SRS resources within the SRS resource set with usage set to 'nonCodebook' to the base station, the terminal applies the calculated precoder, and the base station selects one or more SRS resources from the received one or more SRS resources. In non-codebook based PUSCH transmission, the SRI represents an index that can express a combination of one or more SRS resources, and the SRI is included in the DCI. The number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of the PUSCH, and the terminal transmits the PUSCH by applying the precoder applied to SRS resource transmission to each layer.

[0390] [Regarding terminal capability reporting]

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

[0392] A base station can transmit a UE capability inquiry message requesting a capability report to a connected terminal. The message can include a UE capability request for each RAT (radio access technology) type of the base station. The RAT type-specific request can include information on a combination of supported frequency bands, etc. In addition, in the case of the UE capability inquiry message, UE capabilities for multiple RAT types can be requested through a single RRC message container transmitted by the base station, or the base station can include multiple UE capability inquiry messages including UE capability requests for each RAT type and transmit them to the terminal. That is, the UE capability inquiry can be repeated multiple times in one message, and the terminal can compose a corresponding UE capability information message and report it multiple times. In the next-generation mobile communication system, a UE capability request can be made for MR-DC (Multi-RAT dual connectivity), including NR, LTE, and EN-DC (E-UTRA - NR dual connectivity). Additionally, the terminal capability inquiry message is typically transmitted initially after the terminal is connected to the base station, but the base station may request it under any conditions when necessary.

[0393] In the above step, the terminal that receives the UE capability report request from the base station configures the terminal capability based on the RAT type and band information requested from the base station. Below is a summary of how the terminal configures the UE capability in the NR system.

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

[0395] 2. If the base station requests UE capability reporting by setting the "eutra-nr-only" flag or the "eutra" flag, the UE completely removes NR SA BCs from the list of configured BC candidates. This operation can only occur when the LTE base station (eNB) requests the "eutra" capability.

[0396] 3. The terminal then removes fallback BCs from the BC candidate list constructed in the above step. Here, a fallback BC is a BC obtained by removing at least one band corresponding to an SCell from a random BC. This step can be omitted because the BC before removing the band corresponding to at least one SCell can already cover the fallback BC. This step also applies to MR-DC, i.e., to LTE bands. The BCs remaining after this step are the final "candidate BC list."

[0397] 4. The terminal selects BCs to report 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 set order. That is, the terminal constructs BCs and UE capabilities to report according to the preset rat-Type order (nr -> eutra-nr -> eutra). In addition, it constructs a featureSetCombination for the constructed supportedBandCombinationList, and constructs a list of "candidate feature set combinations" from the candidate BC list after removing the list for the fallback BC (which contains capabilities of the same or lower level). The "candidate feature set combinations" above include feature set combinations for both NR and EUTRA-NR BCs, and can be obtained from the feature set combinations in the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0398] 5. Also, if the requested rat Type is eutra-nr and has an effect, featureSetCombinations are included in both containers: UE-MRDC-Capabilities and UE-NR-Capabilities. However, the NR feature set is included only in UE-NR-Capabilities.

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

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

[0401] For L1-RSRP calculation, the following may be considered:

[0402] - A terminal may be configured with one or more CSI-RS resources, one or more SSB resources, or a CSI-RS resource and an SSB resource having a QCL relationship with QCL-TypeC and QCL-TypeD between resources, and the CSI-RS resources and SSB resources may be included in different resource sets.

[0403] - A terminal can set up to 64 CSI-RS resources within one CSI-RS resource set.

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

[0405] - The terminal can set the number of different CSI-RS resources to a maximum of 128 across all CSI-RS resource sets.

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

[0407] If the upper layer signaling timeRestrictionForChannelMeasurements configured in 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 linked to the L1-RSRP report received in or before the CSI reference resource that can be defined on the time resource.

[0408] If the upper layer signaling timeRestrictionForChannelMeasurements set in CSI-ReportConfig is set 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 reception position among the CSI-RS or SSB in the CSI resource setting linked to the L1-RSRP report received in or before the CSI reference resource that can be defined on the time resource.

[0409] [Table 37] below shows the order of information arrangement when reporting L1-RSRP. At this time, the bit length of the CRI and SSBRI below is the number of bits that can express the number of CSI-RS resources in the CSI-RS resource set (for example, ), can be defined as the number of bits that can express the number of SSB resources in the SSB resource set (for example, ). At this time and may respectively mean the number of CSI-RS resources in the CSI-RS resource set and the number of SSB resources in the SSB resource set. As described above, RSRP and Differential RSRP can be expressed with 7 bits and 4 bits, respectively.

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

[0411] As one embodiment of the present disclosure, a method for setting resources for L1-SINR measurement and reporting is described. The above [Table 26] relates to CSI-ReportConfig set through upper layer signaling related to CSI reporting, and can be used for a description of L1-SINR measurement to be described later. If one resource setting is set in CSI-ReportConfig, which is an upper layer signaling, for L1-SINR measurement, the resource setting (e.g., resourcesForChannelMeasurement, which is an upper layer signaling) may be an NZP CSI-RS for channel and interference measurement. In this case, the terminal may assume that an NZP CSI-RS having one port and a density value of 3 REs / RB is used for channel and interference measurement. If two resource settings are set in CSI-ReportConfig, which is an upper layer signaling, for L1-SINR measurement, the first resource setting (e.g., resourcesForChannelMeasurement, which is an upper layer signaling) can be SSB or NZP CSI-RS for channel measurement, and the second resource setting (e.g., csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference, which is an upper layer signaling) can be CSI-IM for interference measurement, or NZP CSI-RS with 1 port and 3 REs / RB as density value.At this time, an SSB or NZP CSI-RS for channel measurement can 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 can be the same as the number of CSI-IM or NZP CSI-RS for interference measurement. - At this time, when the terminal determines the reference RS for QCL-TypeD of a CSI-IM connected to an SSB or NZP CSI-RS for channel measurement or an NZP CSI-RS for interference measurement, it can use the reference RS for QCL-TypeD of an SSB for channel measurement or an NZP CSI-RS for channel measurement.

[0412] - Additionally, the terminal can expect that the NZP CSI-RS resource set for channel measurement and the NZP CSI-RS resource set for interference measurement will have repetition, which is a higher layer signaling, set. In other words, 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.

[0413] For L1-SINR measurement 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.

[0414] For L1-SINR calculation, the terminal can 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. At this time, the terminal can be configured with up to 16 CSI resource sets for channel measurement, and a total of 64 CSI-RS or 64 SSB resources across all resource sets.

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

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

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

[0418] - If timeRestrictionForInterferenceMeasurements is set to 'notConfigured' in the upper layer signaling CSI-ReportConfig, the terminal may have to derive interference measurement for calculating 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 one or two resource settings described above.

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

[0420] Describes the L1-SINR reporting method of the terminal.

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

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

[0423] - If nrofReportedRS in the upper layer signaling CSI-ReportConfig is greater than 1, or 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 bits using a step size of 0.5 dB for a value within the range of [-23, 40] dB, and the differential L1-SINR value can be quantized to 4 bits using a step size of 1 dB for the difference from the maximum L1-SINR reported together with the differential L1-SINR. If the NZP CSI-RS is configured for channel measurement and / or interference measurement, the reported L1-SINR value can be expected not to be compensated for power offset such as powerControlOffsetSS or powerControlOffset in the upper layer signaling.

[0424] If the terminal has set reportQuantity to 'cri-SINR' or 'ssb-Index-SINR' in the upper layer signaling CSI-ReportConfig, the terminal may consider the following operations related to group-based beam reporting.

[0425] - If the terminal has set the upper layer signaling groupBasedBeamReporting to 'disabled', the terminal can report to the base station by including nrofReportedRS different CRIs or SSBRIs set by the upper layer signaling in a single report.

[0426] - If the terminal has the upper layer signaling, groupBasedBeamReporting, set to 'enabled', the terminal can report two different CRIs or SSBRIs to the base station in a single report. In this case, the CSI-RS and / or SSB indicated by the CRI or SSBRI may be received simultaneously from the terminal.

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

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

[0429] The mathematical formula for the priority rule described above is , and for CSI reports including L1-SINR reports, k = 0 can be considered.

[0430] [Table 38] below shows the order of information arrangement when reporting L1-SINR. At this time, the bit length of the CRI and SSBRI below is the number of bits that can express the number of CSI-RS resources in the CSI-RS resource set (for example, ), can be defined as the number of bits that can express the number of SSB resources in the SSB resource set (for example, ). At this time and may respectively mean the number of CSI-RS resources in the CSI-RS resource set and the number of SSB resources in the SSB resource set. As described above, SINR and Differential SINR can be expressed with 7 bits and 4 bits, respectively.

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

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

[0433] FIG. 10A and FIG. 10B are diagrams illustrating a channel measurement and channel status reporting method according to the setting and instruction of a base station according to one embodiment of the present disclosure.

[0434] Within FIG. 10a, process (1000) relates to a method for securing and managing downlink beam performance between a terminal and a base station according to a periodic reference signal reception and periodic channel state information reporting at a terminal, or / and an aperiodic channel state information reporting trigger at a base station and an aperiodic channel state information reporting method at the terminal.

[0435] The base station (1002) can notify the terminal (1001) 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 the periodic reference signal transmitted from the base station (1005) and report the corresponding periodic channel state information (1010). At this time, the corresponding periodic channel state information may include the performance of the downlink reception beam calculated by the terminal. The base station can determine the downlink reception beam performance of the terminal based on the periodic reference signal reception and measurement and the periodic channel state information reporting of the terminal. The shorter the period of reference signal reception and measurement and channel state information reporting, the more accurately the downlink reception beam performance of the terminal can be determined. However, a lot of signaling overhead may be consumed for the transmission and reception of reference signals and channel state information reports between the terminal and the base station. In contrast, if the cycle of receiving and measuring the reference signal and reporting the channel state information is long, the base station may be relatively inaccurate in determining the reception beam performance of the terminal, so an aperiodic channel state information report may be triggered from the terminal in the middle of the long cycle to determine the reception beam performance (1035). Thereafter, the terminal may perform an aperiodic channel state information report corresponding to the aperiodic channel state information report triggering of the base station (1040), and the base station may synthesize this information and, if the beam performance of the downlink reception beam of the terminal is insufficient and needs to be changed to another beam, may notify beam switching (1045), and the beam switching may be performed by changing the TCI state indicated to the terminal, or by using a method such as RRC reconfiguration to change the settings of the source RS within the TCI state.However, in order for the base station to trigger an aperiodic channel state information report to the terminal, the base station implementation may assume implicit information from the terminal to make such a decision. Typical implicit information for this may include the PDCCH transmitted by the base station to the terminal and the reception of the PDSCH that can be scheduled therethrough (1020), and the PUCCH transmission from the terminal that includes HARQ-ACK information indicating whether the reception was successful (1025). Based on information such as the periodic channel state information report that can be received from the terminal (1010) and the PUCCH that includes HARQ-ACK information corresponding to the PDSCH scheduled for the terminal (1025), the base station can make a decision (1015) as to whether the terminal needs to change the downlink reception beam or, if not, whether the current reception beam can be maintained. However, since such information is likely to be implicit information or, even if it is direct information, it is highly likely that the base station cannot obtain it when it wants, the amount of information about the downlink reception beam performance of the terminal at the base station may be insufficient in absolute terms or may already be outdated.

[0436] Within FIG. 10b, process (1050) relates to a method for securing and managing transmission and reception beam performance between a terminal and a base station according to a channel state information reporting method initiated from a terminal upon occurrence of a specific event at the terminal.

[0437] In order to solve the problems in the above-described process (1000), the base station can notify the terminal of a channel state information reporting method initiated from the terminal based on a combination of at least one of upper layer signaling, MAC-CE signaling, and L1 signaling. Based on this, the terminal can receive a combination of at least one of a periodic reference signal, a semi-persistent reference signal, and an aperiodic reference signal (1055), and the terminal can perform a channel state information report initiated from the terminal (1065) when a specific event defined in the terminal occurs (1060). Thereafter, the base station can notify beam switching based on the information transmitted from the terminal (1070).

[0438] This method of reporting channel state information initiated from the terminal is different from the method in which the base station triggers aperiodic channel state information reporting or notifies beam switching based on implicit information. In this way, the terminal arbitrarily informs the base station about the downlink reception beam performance of the terminal. Even if the base station does not trigger it, the base station can immediately check if the downlink reception beam performance of the terminal changes according to a specific event defined in the terminal and take corresponding action (for example, triggering aperiodic channel state information reporting or instructing beam switching). Based on the channel state information reporting initiated from the terminal, the base station can immediately respond if a change in the downlink reception beam is required, thereby reducing the delay time for beam management. In addition, unlike the method in which the base station can quickly check the downlink reception beam performance of the terminal without the terminal-initiated channel state information reporting by reducing the cycle 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.

[0439] For the aforementioned terminal-initiated channel state information reporting method, the terminal needs to define a specific event (1060) and, when the event occurs, notify the base station that the terminal's downlink reception beam performance has changed. The terminal may consider at least one combination of the following items for defining a specific event for performing the terminal-initiated channel state information reporting described above.

[0440] [Incident 1]

[0441] If a new receiving beam exists with a performance index higher than a specific reference value than the performance of the current receiving beam, the terminal may perform a channel state information report originating from the terminal, including information about the corresponding receiving beam. In this case, for [Event 1], the new receiving beam and the current receiving beam may be defined as follows.

[0442] - For [Incident 1], the current reception beam may be defined as a reference signal set as a QCL source within the TCI state indicated and applied to the terminal, or may be defined as an SSB that is in a QCL relationship with the reference signal set as the QCL source. The meaning of the technology of defining the current reception beam as a specific reference signal may be understood to mean that the terminal determines a parameter to be used as a reception beam or reception filter corresponding to the current reception beam based on the received specific reference signal. In another meaning, the meaning of the technology of defining the current reception beam as a specific reference signal may be understood to mean that when the terminal measures and determines the performance of the current reception beam, the terminal measures the performance of a specific reference signal that the terminal can receive and determines the performance of the current reception beam based on the measured performance. A specific current reception beam determination method may be a combination of one or more of the methods below.

[0443] ■ If there is only one reference signal set as the above QCL source, that is, if the QCL source for QCL-TypeA, B, or C is set in the TCI state indicated to the terminal and the QCL source for QCL-TypeD is not set, the terminal can use the reference signal set as the QCL source for QCL-TypeA, B, or C when determining the current reception beam.

[0444] ■ If there are multiple reference signals set as the above QCL source, that is, if the indicated 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 the QCL source for QCL-TypeD instead of the reference signal set as the QCL source for QCL-TypeA, B, or C when determining the current reception beam. For example, if the TCI state indicated and applied to the terminal has reference signals set as the QCL source for QCL-TypeA and QCL-TypeD, respectively (i.e., if each of the two reference signals is set as the QCL source for QCL-TypeA and QCL-TypeD), the terminal checking the performance of the reference signal set as the QCL source for the indicated and applied TCI state may mean checking the performance of the reference signal set as the QCL source for QCL-TypeD.

[0445] ■ The terminal may consider CSI-RS as a reference signal that can be set as the QCL source. At this time, the CSI-RS may be a TRS (Tracking Reference Signal) in which trs-info, which is an upper layer signaling, is set, a CSI-RS for beam management in which repetition, which is an upper layer signaling, is set to on or off, or a CSI-RS for CSI in which neither trs-info nor repetition, which are upper layer signaling, are set. In addition, 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.

[0446] ■ The terminal may be notified by the base station through a combination of at least one of upper layer signaling, MAC-CE signaling, and L1 signaling as to whether to regard the reference signal set as the QCL source of the applied TCI state as the current reception beam or to regard the SSB having a QCL relationship with the reference signal set as the QCL source as the current reception beam.

[0447] ◆ For example, when reporting the reception beam performance originating from the terminal through upper layer signaling, the terminal can be configured to determine the current reception beam based on either the reference signal set as the QCL source of the TCI state indicated and applied to the current reception beam or an SSB having a QCL relationship with the reference signal. In this case, the terminal can maintain the definition of the current reception beam without changing it according to the configured upper layer signaling, regardless of which TCI state is indicated.

[0448] ◆ As another example, the terminal can be configured with upper layer signaling for each TCI state. Depending on which TCI state is instructed and applied by the base station, the terminal can decide whether to regard the reference signal of the QCL source within the TCI state as the current reception beam, or to regard the SSB that is in a QCL relationship with the reference signal of the QCL source within the TCI state as the current reception beam, depending on the upper layer signaling configuration within the TCI state. For example, if the terminal is instructed to apply a specific TCI state and the upper layer signaling within the TCI state is configured to mean to regard the reference signal of the QCL source within the TCI state as the current reception beam, the terminal can regard the reference signal of the QCL source within the TCI state instructed and applied by the base station as the current reception beam. For another example, if a terminal is instructed to apply a specific TCI state and the upper layer signaling within the TCI state is set to mean that the SSB having a QCL relationship with the reference signal of the QCL source within the TCI state is to be regarded as the current reception beam, the terminal can consider the SSB having a QCL relationship with the reference signal of the QCL source within the TCI state instructed and applied by the base station as the current reception beam.

[0449] - For [Event 1], a new receive beam can be set to the terminal through upper layer signaling. At this time, the terminal may be set to a different new receive beam (or a reference signal corresponding to the new receive beam) according to the current receive beam, or may be set to a new receive beam (or a reference signal corresponding to the new receive beam) regardless of how the current receive beam is determined. In addition, the terminal may receive an activation instruction from the base station to perform measurement for some or all of the new receive beams set to the terminal through MAC-CE. The terminal may consider CSI-RS or SSB as the new receive beam. The meaning of the technology of defining a new receive beam with a specific reference signal can be understood to mean that the terminal determines a parameter to be used as a receive beam or a receive filter corresponding to the new receive beam based on the received specific reference signal. A specific new receive beam determination method may be a combination of one or more of the methods below. In another sense, the meaning of the technology of defining a new reception beam with a specific reference signal can be understood to mean that when a terminal measures and determines the performance of a new reception beam, the terminal measures the performance of a specific reference signal that can be received and determines the performance of the new reception beam based on the measured performance.

[0450] ■ When a terminal is configured with a new reception beam through upper layer signaling, it can expect that information about the new reception beam is configured within each TCI state (within each TCI state configuration information or for each TCI state). The terminal can configure reference signals having reception beam directions similar to the reference signals configured as QCL sources within each TCI state as new reception beams within the corresponding TCI state. At this time, the upper layer signaling for the new reception beam can be configured based on the index for each reference signal, or can be configured based on a TCI state of another index in which the reference signal corresponding to the new reception beam is configured as a QCL source.

[0451] ■ As described above, the terminal can expect that the types of the current reception beam and the new reception beam will remain the same, depending on whether the terminal regards the current reception beam as a reference signal set as a QCL source within the TCI state through notification from the base station or as an SSB having a QCL relationship with the reference signal.

[0452] ■ For example, if the terminal regards the current reception beam as a CSI-RS according to the above-described methods from the base station, the terminal may consider the CSI-RS as a new reception beam for performing a performance comparison with the current reception beam. At this time, the current reception beam and the new reception beam are the same only in that they are CSI-RS, and it may not matter whether the CSI-RS is a TRS, a CSI-RS for beam management, or a CSI-RS for CSI. For example, the terminal may regard the current reception beam as a TRS set to a QCL source within the currently indicated TCI state, and may consider the CSI-RS for beam management as the new reception beam. For another example, the terminal may regard the current reception beam as a CSI-RS for beam management set to a QCL source within the currently indicated TCI state, and may consider the TRS as the new reception beam.

[0453] ■ As another example, if the terminal considers the current receive beam as a specific type of CSI-RS (for example, one of TRS, CSI-RS for beam management, and CSI-RS for CSI) according to the above-described methods from the base station, the terminal may consider the same type of CSI-RS as a new receive beam on which to perform performance comparison with the current receive beam. For example, the terminal may consider the current receive beam as a TRS set to a QCL source within the currently indicated TCI state, and may consider a TRS of the same type as the new receive beam.

[0454] ■ If the current receiving beam is SSB, the terminal can consider SSB as the new receiving beam.

[0455] - For [Incident 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 a terminal capability, or that the base station sets to the terminal through upper layer signaling, or a value fixedly defined in the standard.

[0456] - For [Event 1], the terminal may introduce a specific time interval and counter to determine that the performance of the new reception beam is higher than a specific reference value compared to the reception performance of the current reception beam. The terminal may determine whether [Event 1] has occurred within the time interval, using a time interval starting from the time at which information about the current reception beam is determined. At this time, the time at which information about the current reception beam is determined may be the time at which the currently indicated TCI state is applied, or the time at which a reference signal (CSI-RS or SSB as described above) corresponding to the current reception beam is received after the time at which 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 reception beam, or a frame, subframe, slot, symbol, or absolute time (for example, msec) of a real number shorter or longer than the period value, and may be set by the terminal through upper layer signaling from the base station. The terminal may reset the time interval whenever it receives a reference signal corresponding to the current reception beam, or when the time interval ends. Within the time interval, the terminal receives each reference signal (CSI-RS or SSB as described above) corresponding to each of one or more new receive beams, and if [event 1] occurs for a specific new receive beam more than a certain number of times, the terminal can perform a receive beam performance report initiated from the terminal to the base station. In addition, the terminal stores the number of times [event 1] occurs continuously in the counter described above from the start point of the time interval, and if it is confirmed that the value of the counter is more than a certain number of times, the terminal can report the receive beam performance initiated from the terminal to the base station. In this case, the number of times [event 1] occurs continuously may mean a case where the performance of a specific new receive beam is higher than a certain reference value compared to a current receive beam.For example, if the performance of each of two different new receiving beams is higher than that of the current receiving beam by a certain reference value or more, it can be regarded that [Event 1] has occurred once for each new receiving beam. The terminal checks whether [Event 1] has occurred for each cycle of the current receiving beam within the time interval, and if [Event 1] has occurred continuously within the time interval but has not yet occurred more than a certain number of times, and [Event 1] has not occurred in a specific cycle of the current receiving beam so that the number of times [Event 1] has occurred continuously is no longer more than a certain number, the last point in the specific cycle of the current receiving beam can be reset as the starting point of the time interval. In this way, the terminal can check the number of times [Event 1] has occurred continuously within a specific time interval and report the performance of the receiving beam starting from the terminal to the base station. At this time, the specific number of times can be basically 1, and the terminal can receive a specific natural number X greater than 1 from the base station. The terminal can report to the base station whether it supports the method of considering the above specific number of times as 1 or as X times, which is a specific natural number greater than 1, as an individual terminal capability.

[0457] - For [Incident 1], when reporting the reception beam performance originating from the terminal, the terminal may report to the base station including at least one of the following items.

[0458] ■ The terminal can report to the base station including the index of the current reception beam and / or the performance of the current reception beam. At this time, the index of the current reception beam can be the index of the CSI-RS resource if the current reception beam is CSI-RS as described above, or can be the index of the SSB if the current reception beam is SSB. The terminal can be configured by the base station through upper layer signaling whether to report to the base station including the index of the current reception beam and / or the performance of the current reception beam. That is, if the terminal has configured upper layer signaling from the base station, the terminal can report including the index of the current reception beam and / or the performance of the current reception beam when reporting the performance of the reception beam originating from the terminal. If the terminal has not configured upper layer signaling from the base station, the performance of the reception beam originating from the terminal can be reported without including the index of the current reception beam and / or the performance of the current reception beam.

[0459] ■ When a terminal reports to a base station including the performance of the current reception beam (for example, in the case of L1-RSRP), the terminal may report the L1-RSRP performance of the current reception beam by quantizing it into a value in units of 1 dB from -140 dBm to -44 dBm with a total of 7 bits. This reporting method is only an example, and the present disclosure is not limited by the above example.

[0460] ■ The terminal may report to the base station the index of a new receiving beam and / or the performance of the new receiving beam. The terminal may be configured to include the performance of a number of new receiving beams to report to the base station through upper layer signaling from the base station. For example, the terminal may be configured to include the number of new receiving beams to report from the base station. At this time, the number of new receiving beams to report may be N, which is 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. At this time, the number of new receiving beams to report by the terminal may follow the above-described upper layer signaling.

[0461] ■ When the terminal reports the performance of the N new receiving beams, it can expect that all of the N new receiving beams satisfy [Event 1]. That is, the terminal can assume that the performance of the N new receiving beams is higher than the performance of the current receiving beam by a certain reference value or more.

[0462] ◆ In this case, when the terminal reports the performance of the N new reception beams to the base station (for example, in the case of L1-RSRP), regardless of whether the upper layer signaling indicating whether the performance of the current reception beam is included in the same report is set (i.e., for both cases where the performance of the current reception beam is included or not), the terminal may report the L1-RSRP performance of each new reception beam by quantizing it into a value in units of 1 dB from -140 dBm to -44 dBm with a total of 7 bits. This reporting method is merely an example, and the present disclosure is not limited by the example.

[0463] ◆ In another way, when the terminal reports the performance of the N new receive beams to the base station (for example, in the case of L1-RSRP), regardless of whether the upper layer signaling indicating whether the performance of the current receive beam is included in the same report is set (i.e., for both the case where the performance of the current receive beam is included and the case where the performance of the current receive beam is not included), the terminal can report the L1-RSRP performance of the new receive beam having the largest L1-RSRP value among one or more new receive beams by quantizing the value in units of 1 dB from -140 dBm to -44 dBm into a total of 7 bits, and the performances of the remaining N-1 new receive beams can be expressed as a difference value from the performance of the new receive beam having the largest L1-RSRP value. At this time, the difference value can be expressed as X bits and can be expressed in units of Y dB, where X can be a natural number less than 7 (for example, one of 1, 2, 3, 4, 5, or 6), and Y can be a real number greater than 0 (for example, one of 0, 0.5, 1, 1.5, 2, 2.5, 3, ...). For example, the difference value can be expressed in units of Y=2 dB with X=4 bits. This reporting method is merely an example, and the present disclosure is not limited by the above example.

[0464] ◆ In another way, when the terminal reports the performance of the N new receive beams to the base station (for example, in the case of L1-RSRP), and when upper layer signaling is set to indicate whether the performance of the current receive beam is included in the same report (i.e., for the case where the performance of the current receive beam is included), the terminal can express the L1-RSRP performance of the new receive beam as a difference value from a value higher by a certain reference value than the performance of the current receive beam. At this time, the difference value can be expressed as X bits and can be expressed in units of Y dB, X can be a natural number less than 7 (for example, one of 1, 2, 3, 4, 5, or 6), and Y can be a real number greater than or equal to 1 (for example, one of 1, 1.5, 2, 2.5, 3, ...). This reporting method is only an example, and the present disclosure is not limited by the above example. For example, the above difference value can be expressed in units of Y=2 dB with X=4 bits. At this time, since the performance of the new reception beam reported by the terminal all satisfies [Event 1], it can be a value greater than or equal to a value higher than the performance of the current reception beam by a certain reference value.

[0465] ◆ In another method, when the terminal reports the performance of the N new receive beams to the base station (for example, in the case of L1-RSRP), if upper layer signaling is set to indicate whether the performance of the current receive beam is included in the same report (i.e., for the case where the performance of the current receive beam is included), the terminal can express the L1-RSRP performance of the new receive beam as a difference value from a value higher by a certain reference value than the performance of the current receive beam. At this time, the difference value can be expressed as X bits and can be expressed in units of Y dB, X can be a natural number less than 7 (for example, one of 1, 2, 3, 4, 5, or 6), and Y can be a real number greater than or equal to 1 (for example, one of 1, 1.5, 2, 2.5, 3, ...). This reporting method is only an example, and the present disclosure is not limited by the above example. For example, the difference value can be expressed in units of Y=2 dB with X=4 bits. If no upper layer signaling is established to indicate whether the performance of the current receive beam is included in the same report (i.e., for the case where the performance of the current receive beam is not included), the terminal can report the L1-RSRP performance of the new receive beam with the largest L1-RSRP value among one or more new receive beams by quantizing the value in units of 1 dB from -140 dBm to -44 dBm into a total of 7 bits, and express the performances of the remaining N-1 new receive beams as difference values ​​from the performance of the new receive beam with the largest L1-RSRP value. At this time, the difference value can be expressed as X bits, and can be expressed in Y dB units, where X can be a natural number less than 7 (for example, one of 1, 2, 3, 4, 5, or 6), and Y can be a real number greater than 0 (for example, one of 0, 0.5, 1, 1.5, 2, 2.5, 3, ...).For example, the difference value can be expressed in units of Y=2 dB with X=4 bits. This reporting method is only an example, and the present disclosure is not limited by the above example. Through this, the terminal can keep the bit length of the receive beam performance report initiated from the terminal the same for the case where the upper layer signaling indicating whether the performance of the current receive beam is included in the same report or not set. Accordingly, for the two cases described above (where the upper layer signaling indicating whether the performance of the current receive beam is included in the same report or not set), the terminal can keep the bit length of the receive beam performance report initiated from the terminal the same, and if one case is shorter in bit length than the other case, the two cases can include a specific number of 0 bits so that the bit lengths are the same.

[0466] ■ When the terminal reports the N new receiving beams, it can expect that at least one new receiving beam among the N satisfies [Event 1]. That is, the terminal can assume that the performance of some of the N new receiving beams is higher than a specific reference value or more compared to the performance of the current receiving beam, and can assume that the remaining new receiving beams, excluding some of the above, are not higher than a specific reference value or more compared to the performance of the current receiving beam.

[0467] ◆ In this case, when the terminal reports the performance of the N new receive beams to the base station (for example, in the case of L1-RSRP), regardless of whether the upper layer signaling indicating whether the performance of the current receive beam is included in the same report is set (i.e., for both the case where the performance of the current receive beam is included or not), the terminal can report the L1-RSRP performance of each new receive beam by quantizing it into a total of 7 bits in units of 1 dB from -140 dBm to -44 dBm. For this method, if the terminal has been set to report the performance of the current receive beam, the terminal may not include the number of new receive beams that satisfy [Event 1] when reporting the receive beam performance starting from the terminal. Even if the terminal does not report the number of new receive beams that satisfy [Event 1], the base station can determine whether the performance of the new receive beam reported by the terminal satisfies [Event 1] based on the performance value of the current receive beam reported by the terminal and a specific reference value set for the terminal. For the method, if the terminal is not configured with upper layer signaling to report the performance of the current receive beam, the terminal can include the number of new receive beams that satisfy [Event 1] when reporting to the base station. Since the terminal does not report the performance of the current receive beam, the base station cannot know which new receive beams satisfy [Event 1] if the terminal does not report the number of new receive beams that satisfy [Event 1]. For example, if N=4, that is, 2 out of 4 new receive beams satisfy [Event 1], the terminal can report the performance of the 4 new receive beams and use ceil(log2(N)) bits (2 bits when N=4) to express that the number of new receive beams that satisfy [Event 1] is 2. In this case, ceil(.) can represent a rounding function, and log2(.) can represent a logarithmic function with a base of 2.The terminal can report four new receiving beams in order of performance, and the base station can determine that the new receiving beams with the two highest performance values ​​among the four new receiving beams satisfy [Event 1], and that the remaining two new receiving beams do not satisfy [Event 1].

[0468] ◆ In another way, when the terminal reports the performance of the N new receive beams to the base station (for example, in the case of L1-RSRP), regardless of whether the upper layer signaling indicating whether the performance of the current receive beam is included in the same report is set (i.e., for both the case where the performance of the current receive beam is included and the case where the performance of the current receive beam is not included), the terminal can report the L1-RSRP performance of the new receive beam having the largest L1-RSRP value among one or more new receive beams by quantizing the value in units of 1 dB from -140 dBm to -44 dBm into a total of 7 bits, and the performances of the remaining N-1 new receive beams can be expressed as a difference value from the performance of the new receive beam having the largest L1-RSRP value. At this time, the difference value can be expressed as X bits and can be expressed in units of Y dB, where X can be a natural number less than 7 (for example, one of 1, 2, 3, 4, 5, or 6), and Y can be a real number greater than 0 (for example, one of 0, 0.5, 1, 1.5, 2, 2.5, 3, ...). For example, the difference value can be expressed in units of Y=2 dB with X=4 bits. This reporting method is only an example, and the present disclosure is not limited by the example. For the method, if the terminal has been set up with upper layer signaling to report the performance of the current reception beam, the terminal may not include the number of new reception beams that satisfy [Event 1] when reporting the reception beam performance starting from the terminal. Even if the terminal does not report the number of new reception beams that satisfy [Event 1], the base station can determine whether the performance of the new reception beam reported by the terminal satisfies [Event 1] based on the performance value of the current reception beam reported by the terminal and a specific reference value set for the terminal.For the method, if the terminal is not configured with upper layer signaling to report the performance of the current receive beam, the terminal may include the number of new receive beams that satisfy [Event 1] when reporting to the base station. Since the terminal does not report the performance of the current receive beam, the base station cannot know which new receive beams satisfy [Event 1] if the terminal does not report the number of new receive beams that satisfy [Event 1]. For example, if N=4, that is, 2 out of 4 new receive beams satisfy [Event 1], the terminal may report the performance of the 4 new receive beams and use ceil(log2(N)) bits (e.g., 2 bits when N=4) to express that the number of new receive beams that satisfy [Event 1] is 2. In this case, ceil(.) may represent a rounding function, and log2(.) may represent a logarithmic function with a base of 2. The terminal can report four new receiving beams in order of performance, and the base station can determine that the new receiving beams with the two highest performance values ​​among the four new receiving beams satisfy [Event 1], and that the remaining two new receiving beams do not satisfy [Event 1].

[0469] ◆ In another way, when the terminal reports the performance of the N new receive beams to the base station (for example, in the case of L1-RSRP), and when upper layer signaling indicating whether the performance of the current receive beam is included in the same report is set (i.e., for the case where the performance of the current receive beam is included), the terminal can express the L1-RSRP performance of the new receive beam as a difference value from a value higher by a certain reference value than the performance of the current receive beam. At this time, the difference value can be expressed with X bits and can be expressed in units of Y dB, and X can be a natural number less than 7 (for example, one of 1, 2, 3, 4, 5, or 6), and Y can be a real number greater than or equal to 1 (for example, one of 1, 1.5, 2, 2.5, 3, ...). As an example, the difference value can be expressed with X=4 bits and Y=2 dB units. This reporting method is only an example, and the present disclosure is not limited by the above example. At this time, the terminal may include the number of new reception beams that satisfy [Event 1] when reporting to the base station. Through this method, the performance of the new reception beam reported by the terminal is expressed as a difference value from a value that is higher by a certain reference value than the performance of the current reception beam, so if a specific new reception beam does not satisfy [Event 1], it may mean that it is lower than a value that is higher by a certain reference value than the performance of the current reception beam described above.Accordingly, when the terminal expresses the performance of a new reception beam as a difference value from a value higher by a specific reference value than the performance of the current reception beam, the performance values ​​of the new reception beams for the number of new reception beams that satisfy [Event 1] additionally reported by the terminal can be assumed to be positive difference values ​​from a value higher by a specific reference value than the performance of the current reception beam, and the performance values ​​of the new reception beams for the number of new reception beams that do not satisfy [Event 1] among all new reception beams can be assumed to be negative difference values ​​from a value higher by a specific reference value than the performance of the current reception beam. In this case, since the reception beam performance report originating from the terminal does not include such sign information such as positive or negative, among the performances of the new reception beams reported by the terminal, the performance of the new reception beam that satisfies [Event 1] is arranged first, and the performance of the new reception beam that does not satisfy [Event 1] is arranged later, so that the base station can check the performance of the new reception beam by applying the positive or negative difference value.

[0470] ◆ In another way, when the terminal reports the performance of the N new receive beams to the base station (for example, in the case of L1-RSRP), the terminal may include the number of new receive beams that satisfy [Event 1] to the base station. For example, if N=4, that is, 2 out of 4 new receive beams satisfy [Event 1], the terminal may report the performance of the 4 new receive beams and use ceil(log2(N)) bits (2 bits when N=4) to express that the number of new receive beams that satisfy [Event 1] is 2. In this case, ceil(.) may represent a rounding function, and log2(.) may represent a logarithmic function with a base of 2. If upper layer signaling is established to indicate whether the performance of the current receive beam is included in the same report (i.e., for the case where the performance of the current receive beam is included), and there are N new receive beams that satisfy [Event 1] (i.e., all N new receive beams satisfy [Event 1]), the terminal can express the L1-RSRP performance of the new receive beam as a difference value from a value higher by a certain threshold value than the performance of the current receive beam. In this case, the difference value can be expressed with X bits and expressed in units of Y dB, where X can be a natural number less than 7 (for example, one of 1, 2, 3, 4, 5, or 6), and Y can be a real number greater than 0 (for example, one of 0, 0.5, 1, 1.5, 2, 2.5, 3, ...). As an example, the difference value can be expressed with X=4 bits and Y=2 dB. These reporting methods are merely examples, and the present disclosure is not limited by the above examples.If upper layer signaling is set to indicate whether the performance of the current receive beam is included in the same report (i.e., for the case where the performance of the current receive beam is included), and if there are fewer than N new receive beams that satisfy [Event 1] (i.e., at least one new receive beam does not satisfy [Event 1]), the terminal may report the L1-RSRP performance of the new receive beam having the largest L1-RSRP value among the one or more new receive beams by quantizing the value in units of 1 dB from -140 dBm to -44 dBm into a total of 7 bits, and the performances of the remaining N-1 new receive beams may be expressed as a difference value from the performance of the new receive beam having the largest L1-RSRP value. At this time, the difference value can be expressed as X bits and expressed in Y dB units, where X can be a natural number less than 7 (for example, one of 1, 2, 3, 4, 5, or 6), and Y can be a real number greater than 0 (for example, one of 0, 0.5, 1, 1.5, 2, 2.5, 3, ...). For example, the difference value can be expressed in X=4 bits and Y=2 dB units. This reporting method is only an example, and the present disclosure is not limited by the example. Through this, the terminal can decide whether to express the performance of all new receiving beams as a difference value from a value equal to or greater than a certain reference value from the performance of the current receiving beam, or whether to express the performance of one new receiving beam with the highest receiving performance and the performance of another new receiving beam expressed as a difference value therefrom, depending on whether all new receiving beams satisfy [Event 1].

[0471] [Incident 2]

[0472] The terminal may perform channel state information reporting starting from the terminal, including the corresponding reception beam information, when the performance of the current reception beam is below a specific reference value.

[0473] - For the [Event 2], the terminal can determine the current receiving beam in a similar manner to the above [Event 1]. That is, the terminal can use the reference signal set as the QCL source within the currently indicated and applied TCI state as the current receiving beam, or use the SSB that is in a QCL relationship with the reference signal.

[0474] - Alternatively, the terminal may consider the current reception beam as a reference signal set by upper layer signaling for the corresponding [event 2].

[0475] - For the [Incident 2], the specific reference value used when checking the performance of the current receiving beam may be a value that the terminal reports to the base station as a terminal capability, or that the base station sets to the terminal through upper layer signaling, or a value fixedly defined in the standard.

[0476] - For [Event 2], the terminal may introduce a specific time interval and counter to determine whether the performance of the current reception beam is below a specific reference value. The terminal may use a time interval starting from the time at which information about the current reception beam is determined to determine whether [Event 2] has occurred within the time interval. At this time, the time at which information about the current reception beam is determined may be the time at which the currently indicated TCI state is applied, or the time at which a reference signal (CSI-RS or SSB, as described above) corresponding to the current reception beam is received after the time at which 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 reception beam, or a frame, subframe, slot, symbol, or absolute time (for example, msec) of a real number shorter or longer than the period value, and may be set by the base station to the terminal through upper layer signaling. The terminal may confirm that [Event 2] has occurred from the start point of the time interval to the length of the time interval. The terminal may store the number of times [Event 2] occurs in a counter from the start point of the above time interval, and if the value of the counter is greater than a specific number, the terminal may report the reception beam performance starting from the terminal to the base station. In addition, the terminal may store the number of times [Event 2] continuously occurs in the above-described counter from the start point of the above time interval, and if the value of the counter is greater than a specific number, the terminal may report the reception beam performance starting from the terminal to the base station.The terminal checks whether [Event 2] has occurred at each cycle of the current reception beam within the time interval, and if [Event 2] has occurred continuously within the time interval but has not yet occurred more than a specific number of times, and if [Event 2] does not occur at a specific cycle of the current reception beam so that the number of times [Event 2] has occurred continuously is no longer more than a specific number, the last point in time of the specific cycle of the current reception beam can be reset as the starting point of the time interval. In this way, the terminal can check the number of times [Event 2] has occurred continuously within the specific time interval and report the reception beam performance starting from the terminal to the base station. At this time, the specific number of times may be 1 by default, and the terminal can receive from the base station a specific natural number X greater than 1. The terminal can report to the base station whether it supports a method of regarding the specific number of times as 1 or as X greater than 1 as an individual terminal capability.

[0477] - For [Incident 2], when reporting the reception beam performance originating from the terminal, the terminal may report to the base station including at least one of the following items.

[0478] ■ When the terminal reports the performance of the current reception beam to the base station (for example, in the case of L1-RSRP), the terminal may report the L1-RSRP performance of the current reception beam by quantizing it into a value in units of 1 dB from -140 dBm to -44 dBm with a total of 7 bits. This reporting method is only an example, and the present disclosure is not limited by the above example.

[0479] ■ When the terminal reports the performance of the current reception beam to the base station (for example, in the case of L1-RSRP), the terminal may express the L1-RSRP performance of the current reception beam as a difference value from the specific reference value. At this time, the difference value may be expressed in X bits and may be expressed in units of Y dB, and X may be a natural number less than 7 (one of 1, 2, 3, 4, 5, or 6), and Y may be a real number greater than 0 (one of 0, 0.5, 1, 1.5, 2, 2.5, 3, ...). For example, the difference value may be expressed in units of Y=2 dB with X=4 bits. This reporting method is merely an example, and the present disclosure is not limited by the above example.

[0480] [Incident 3]

[0481] If the performance of at least one new receiving beam is higher than the performance of the current receiving beam by a certain threshold value or more, the terminal may perform a channel state information report starting from the terminal, including the new receiving beam information. In this case, for [Event 3], the new receiving beam and the current receiving beam may be defined as follows.

[0482] - For [Event 3], the terminal can determine the current receiving beam in a similar manner to [Event 1] above. That is, the terminal can use the reference signal set as the QCL source within the currently indicated and applied TCI state as the current receiving beam, or use the SSB that is in a QCL relationship with the reference signal.

[0483] - In another way, for the [event 3], the current reception beam may be defined as the reception beam when receiving the reference signal having the lowest reception performance value among the reference signals set as QCL sources in one or more TCI states activated for the terminal. For example, if the reference signal set as QCL source in the second TCI state among the eight TCI states activated for the terminal has the lowest performance (e.g., L1-RSRP or L1-SINR), the terminal may define the reception beam used when receiving the reference signal set as QCL source in the second TCI state among the activated TCI states as the current reception beam. If a terminal has a QCL source set for QCL-TypeD as well as QCL-TypeA, B, or C in a specific TCI state among one or more activated TCI states, when the terminal verifies the reception performance of a reference signal set as the QCL source, the terminal may use the reference signal set as the QCL source for QCL-TypeD instead of the reference signal set as the QCL source for QCL-TypeA, B, or C. For example, if the second TCI state has reference signals set as the QCL source for QCL-TypeA and QCL-TypeD, respectively (i.e., if the two reference signals are each set as the QCL source for QCL-TypeA and QCL-TypeD), when the terminal verifies the performance of the reference signal set as the QCL source for the second TCI state, it may mean that the terminal verifies the performance of the reference signal set as the QCL source for QCL-TypeD.

[0484] - Alternatively, the terminal may define the current reception beam for the [event 3] as the SSB with the lowest reception performance value among one or more SSBs that have a QCL relationship with the reference signal set as the QCL source within one or more TCI states activated by the terminal.

[0485] - For [Event 3], a new reception beam may be set to the terminal via upper layer signaling. At this time, the terminal may be set to a different new reception beam depending on the current reception beam, or may be set to a new reception beam regardless of which current reception beam is determined. In addition, the terminal may receive an activation instruction from the base station via MAC-CE to perform measurements on some or all of the new reception beams set to the terminal.

[0486] ■ When a terminal is set to a new reception beam by upper layer signaling, it can expect that information about the new reception beam is set within each TCI state (in each TCI state configuration information or for each TCI state). The terminal can set reference signals having reception beam directions similar to the reference signals set to the QCL source within each TCI state as new reception beams within the corresponding TCI state. In this case, the upper layer signaling for the new reception beam can be set based on the index for each reference signal, or can be set based on a TCI state of another index in which the reference signal corresponding to the new reception beam is set to the QCL source.

[0487] ■ As described above, the terminal can expect that the types of the current reception beam and the new reception beam will remain the same, depending on whether the terminal regards the current reception beam as a reference signal set as a QCL source within the TCI state through notification from the base station or as an SSB having a QCL relationship with the reference signal.

[0488] ■ For example, if the terminal regards the current reception beam as a CSI-RS according to the above-described methods from the base station, the terminal may consider the CSI-RS as a new reception beam for performing a performance comparison with the current reception beam. At this time, the current reception beam and the new reception beam are the same only in that they are CSI-RS, and it may not matter whether the CSI-RS is a TRS, a CSI-RS for beam management, or a CSI-RS for CSI. For example, the terminal may regard the current reception beam as a TRS set to a QCL source within the currently indicated TCI state, and may consider the CSI-RS for beam management as the new reception beam. For another example, the terminal may regard the current reception beam as a CSI-RS for beam management set to a QCL source within the currently indicated TCI state, and may consider the TRS as the new reception beam.

[0489] ■ As another example, if the terminal considers the current receive beam as a specific type of CSI-RS (for example, one of TRS, CSI-RS for beam management, and CSI-RS for CSI) according to the above-described methods from the base station, the terminal may consider the same type of CSI-RS as a new receive beam on which to perform performance comparison with the current receive beam. For example, the terminal may consider the current receive beam as a TRS set to a QCL source within the currently indicated TCI state, and may consider a TRS of the same type as the new receive beam.

[0490] - For [Incident 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 a terminal capability, or that the base station sets to the terminal through upper layer signaling, or a value fixedly defined in the standard.

[0491] - For [Event 3], the terminal may introduce a specific time interval and counter to determine that the performance of the new reception beam is higher than a specific reference value compared to the reception performance of the current reception beam. The terminal may determine whether [Event 3] has occurred at a point in time within the time interval using a time interval starting from the point in time when information about the current reception beam is determined. At this time, the point in time when information about the current reception beam is determined 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 reception 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 reception beam, or a frame, subframe, slot, symbol, or absolute time (for example, msec) of a real number shorter or longer than the period value, and may be set by the terminal through upper layer signaling from the base station. The terminal may reset the time interval whenever it receives a reference signal corresponding to the current reception beam, or when the time interval ends. Within the time interval, the terminal receives each reference signal (CSI-RS or SSB as described above) corresponding to each of one or more new receive beams, and if [event 3] occurs for a specific new receive beam more than a certain number of times, the terminal may perform a receive beam performance report initiated from the terminal to the base station. In addition, the terminal may store the number of times that [event 3] occurs continuously in the counter described above from the start point of the time interval, and if it is confirmed that the value of the counter is more than a certain number of times, the terminal may report the receive beam performance initiated from the terminal to the base station. In this case, the number of times that [event 3] occurs continuously may mean a case where the performance of a specific new receive beam is higher than a certain reference value compared to a current receive beam.For example, if the performance of each of two different new receiving beams is higher than a specific reference value compared to the current receiving beam, it can be considered that [Event 3] has occurred once for each new receiving beam. The terminal checks whether [Event 3] has occurred for each cycle of the current receiving beam within the time interval, and 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] has not occurred in a specific cycle of the current receiving beam so that the number of times [Event 3] has occurred continuously is no longer more than a specific number, the last point in the specific cycle of the current receiving beam can be reset as the starting point of the time interval. In this way, the terminal can check the number of times [Event 3] has occurred continuously within a specific time interval and report the performance of the receiving beam starting from the terminal to the base station. At this time, the specific number of times can be basically 1, and the terminal can receive a specific natural number X greater than 1 from the base station. The terminal can report to the base station whether it supports the method of considering the above specific number of times as 1 or as X times, which is a specific natural number greater than 1, as an individual terminal capability.

[0492] - For [Incident 3], when reporting the reception beam performance originating from the terminal, the terminal may report to the base station including at least one of the following items.

[0493] ■ The terminal can report to the base station the index of the current reception beam and / or the performance of the current reception beam. At this time, the index of the current reception beam can be the index of the CSI-RS resource if the current reception beam is CSI-RS as described above, or can be the index of the SSB if the current reception beam is SSB. When the terminal performs the index of the current reception beam and / or the performance of the current reception beam as a reception beam performance report starting from the terminal corresponding to [Event 3], the terminal can perform the reception beam performance report without setting a specific upper layer signaling from the base station.

[0494] ■ The terminal can be configured by the base station through upper layer signaling whether to report the reception beam performance starting from the terminal, including the index of the current reception beam and / or the performance of the current reception beam. That is, if the terminal has been configured by the base station through upper layer signaling, the terminal can report the reception beam performance starting from the terminal, including the index of the current reception beam and / or the performance of the current reception beam. If the terminal has not been configured by the base station through the upper layer signaling, the reception beam performance starting from the terminal can be reported without including the index of the current reception beam and / or the performance of the current reception beam.

[0495] ■ When the terminal reports the performance of a new receiving beam, the method of [Event 1] above can be used similarly.

[0496] [Incident 4]

[0497] If the performance of at least one new receiving beam is higher than the performance of the current receiving beam by a specific reference value or more, the terminal may perform channel state information reporting starting from the terminal, including the new receiving beam information. At this time, for the [Event 4], the new receiving beam and the current receiving beam may be defined as follows. The difference between Event 3 and Event 4 is that in the case of Event 3, the current receiving beam is defined as the reference signal with the lowest receiving performance value, but in the case of Event 4, the current receiving beam is defined as the reference signal with the highest receiving performance value.

[0498] - For [Event 4], the terminal can determine the current receiving beam in a similar manner to [Event 1] above. That is, the terminal can use the reference signal set as the QCL source within the currently indicated and applied TCI state as the current receiving beam, or use the SSB that is in a QCL relationship with the reference signal.

[0499] - In another way, for the [event 3], the current reception beam may be defined as the reception beam when receiving the reference signal having the highest reception performance value among the reference signals set as QCL sources in one or more TCI states activated for the terminal. For example, if the reference signal set as QCL source in the second TCI state among the eight TCI states activated for the terminal has the highest performance (e.g., L1-RSRP or L1-SINR), the terminal may define the reception beam used when receiving the reference signal set as QCL source in the second TCI state among the activated TCI states as the current reception beam. If a terminal has a QCL source set for QCL-TypeD as well as QCL-TypeA, B, or C in a specific TCI state among one or more activated TCI states, when the terminal verifies the reception performance of a reference signal set as the QCL source, the terminal may use the reference signal set as the QCL source for QCL-TypeD instead of the reference signal set as the QCL source for QCL-TypeA, B, or C. For example, if the second TCI state has reference signals set as the QCL source for QCL-TypeA and QCL-TypeD, respectively (i.e., if the two reference signals are each set as the QCL source for QCL-TypeA and QCL-TypeD), when the terminal verifies the performance of the reference signal set as the QCL source for the second TCI state, it may mean that the terminal verifies the performance of the reference signal set as the QCL source for QCL-TypeD.

[0500] - Alternatively, the terminal may define the current reception beam for the [event 4] as the SSB with the highest reception performance value among one or more SSBs that have a QCL relationship with the reference signal set as the QCL source within one or more TCI states activated in the terminal.

[0501] - For [Event 4], a new reception beam may be set to the terminal via upper layer signaling. At this time, the terminal may be set to a different new reception beam depending on the current reception beam, or may be set to a new reception beam regardless of which current reception beam is determined. In addition, the terminal may receive an activation instruction from the base station via MAC-CE to perform measurements on some or all of the new reception beams set to the terminal.

[0502] ■ When a terminal is set to a new reception beam by upper layer signaling, it can expect that information about the new reception beam is set within each TCI state (in each TCI state configuration information or for each TCI state). The terminal can set reference signals having reception beam directions similar to the reference signals set to the QCL source within each TCI state as new reception beams within the corresponding TCI state. In this case, the upper layer signaling for the new reception beam can be set based on the index for each reference signal, or can be set based on a TCI state of another index in which the reference signal corresponding to the new reception beam is set to the QCL source.

[0503] ■ As described above, the terminal can expect that the types of the current reception beam and the new reception beam will remain the same, depending on whether the terminal regards the current reception beam as a reference signal set as a QCL source within the TCI state through notification from the base station or as an SSB having a QCL relationship with the reference signal.

[0504] ■ For example, if the terminal regards the current reception beam as a CSI-RS according to the above-described methods from the base station, the terminal may consider the CSI-RS as a new reception beam for performing a performance comparison with the current reception beam. At this time, the current reception beam and the new reception beam are the same only in that they are CSI-RS, and it may not matter whether the CSI-RS is a TRS, a CSI-RS for beam management, or a CSI-RS for CSI. For example, the terminal may regard the current reception beam as a TRS set to a QCL source within the currently indicated TCI state, and may consider the CSI-RS for beam management as the new reception beam. For another example, the terminal may regard the current reception beam as a CSI-RS for beam management set to a QCL source within the currently indicated TCI state, and may consider the TRS as the new reception beam.

[0505] ■ As another example, if the terminal considers the current receive beam as a specific type of CSI-RS (for example, one of TRS, CSI-RS for beam management, and CSI-RS for CSI) according to the above-described methods from the base station, the terminal may consider the same type of CSI-RS as a new receive beam on which to perform performance comparison with the current receive beam. For example, the terminal may consider the current receive beam as a TRS set to a QCL source within the currently indicated TCI state, and may consider a TRS of the same type as the new receive beam.

[0506] ■ When a terminal is configured with upper layer signaling for a new receive beam, it can expect it to be configured within each TCI state. The terminal can configure reference signals having a receive beam direction similar to the reference signal configured as a QCL source within each TCI state as a new receive beam within the corresponding TCI state. At this time, the upper layer signaling for the new receive beam can be configured based on the index for each reference signal, or can be configured based on a TCI state of another index in which the reference signal corresponding to the new receive beam is configured as a QCL source.

[0507] ■ As described above, the terminal can expect that the types of the current reception beam and the new reception beam will remain the same, depending on whether the terminal regards the current reception beam as a reference signal set as a QCL source within the TCI state through notification from the base station or as an SSB having a QCL relationship with the reference signal.

[0508] ■ For example, if the terminal regards the current reception beam as a CSI-RS according to the above-described methods from the base station, the terminal may consider the CSI-RS as a new reception beam for performing a performance comparison with the current reception beam. At this time, the current reception beam and the new reception beam are the same only in that they are CSI-RS, and it may not matter whether the CSI-RS is a TRS, a CSI-RS for beam management, or a CSI-RS for CSI. For example, the terminal may regard the current reception beam as a TRS set to a QCL source within the currently indicated TCI state, and may consider the CSI-RS for beam management as the new reception beam. For another example, the terminal may regard the current reception beam as a CSI-RS for beam management set to a QCL source within the currently indicated TCI state, and may consider the TRS as the new reception beam.

[0509] ■ As another example, if the terminal considers the current receive beam as a specific type of CSI-RS (for example, one of TRS, CSI-RS for beam management, and CSI-RS for CSI) according to the above-described methods from the base station, the terminal may consider the same type of CSI-RS as a new receive beam on which to perform performance comparison with the current receive beam. For example, the terminal may consider the current receive beam as a TRS set to a QCL source within the currently indicated TCI state, and may consider a TRS of the same type as the new receive beam.

[0510] - For [Incident 4], 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 a terminal capability, or that the base station sets to the terminal through upper layer signaling, or a value fixedly defined in the standard.

[0511] - For [Event 4], the terminal may introduce a specific time interval and counter to determine that the performance of the new reception beam is higher than a specific reference value compared to the reception performance of the current reception beam. The terminal may determine whether [Event 3] has occurred at a point in time within the time interval, using a time interval starting from the point in time when information about the current reception beam is determined. At this time, the point in time when information about the current reception beam is determined 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 reception 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 reception beam, or a frame, subframe, slot, symbol, or absolute time (for example, msec) of a real number shorter or longer than the period value, and may be set by the terminal through upper layer signaling from the base station. The terminal may reset the time interval whenever it receives a reference signal corresponding to the current reception beam, or when the time interval ends. Within the time interval, the terminal receives each reference signal (CSI-RS or SSB as described above) corresponding to each of one or more new receive beams, and if [event 4] occurs for a specific new receive beam more than a certain number of times, the terminal may perform a receive beam performance report initiated from the terminal to the base station. In addition, the terminal may store the number of times that [event 4] occurs continuously in the counter described above from the start point of the time interval, and if the value of the counter is determined to be greater than the certain number of times, the terminal may report the receive beam performance initiated from the terminal to the base station. In this case, the number of times that [event 4] occurs continuously may mean a case where the performance of a specific new receive beam is higher than a certain reference value compared to a current receive beam.For example, if the performance of each of two different new receive beams is higher than that of the current receive beam by a specific reference value or more, it can be regarded that [Event 4] has occurred once for each new receive beam. The terminal checks whether [Event 4] has occurred for each cycle of the current receive beam within the time interval, and if [Event 4] has occurred continuously within the time interval but has not yet occurred more than a specific number of times, and [Event 4] has not occurred in a specific cycle of the current receive beam so that the number of times [Event 4] has occurred continuously is no longer more than a specific number, the last point in the specific cycle of the current receive beam can be reset as the starting point of the time interval. In this way, the terminal can check the number of times [Event 4] has occurred continuously within a specific time interval and report the performance of the receive beam starting from the terminal to the base station. At this time, the specific number of times can be basically 1, and the terminal can receive a specific natural number X greater than 1 from the base station. The terminal can report to the base station whether it supports the method of considering the above specific number of times as 1 or as X times, which is a specific natural number greater than 1, as an individual terminal capability.

[0512] - For [Incident 4], when reporting the reception beam performance originating from the terminal, the terminal may report to the base station including at least one of the following items.

[0513] ■ The terminal can report to the base station the index of the current reception beam and / or the performance of the current reception beam. In this case, the index of the current reception beam can be the index of the CSI-RS resource if the current reception beam is CSI-RS as described above, or can be the index of the SSB if the current reception beam is SSB. The terminal can perform the index of the current reception beam and / or the performance of the current reception beam without setting a specific upper layer signaling from the base station if the reception beam performance report is initiated from the terminal corresponding to [Event 3].

[0514] ■ The terminal can be configured by the base station through upper layer signaling whether to include the index of the current reception beam and / or the performance of the current reception beam in the report. That is, if the terminal has been configured by the base station through upper layer signaling, the terminal can include the index of the current reception beam and / or the performance of the current reception beam when reporting the performance of the reception beam originating from the terminal. If the terminal has not been configured by the base station through upper layer signaling, the performance of the reception beam originating from the terminal can be reported without including the index of the current reception beam and / or the performance of the current reception beam.

[0515] ■ When the terminal reports the performance of a new receiving beam, the method of [Event 1] above can be used similarly.

[0516] The terminal may use the following when reporting reception beam performance originating from the terminal for at least one combination of [Event 1], [Event 2], [Event 3], or [Event 4]. For example, the terminal may report reception beam performance originating from the terminal to the base station in consideration of [Event 1]. As another example, the terminal may each be configured with upper layer signaling for reception beam performance reports originating from the terminal for [Event 1] and [Event 2], and may individually check and report reception beam performance for [Event 1] and [Event 2]. When [Event 1] occurs, the terminal may report reception beam performance originating from the corresponding terminal. When [Event 2] occurs, the terminal may report reception beam performance originating from the corresponding terminal. When [Event 1] and [Event 2] occur simultaneously, the terminal may report reception beam performance starting from the terminal corresponding to [Event 1] and [Event 2] respectively, select only one of the two, or report reception beam performance related to the event with the highest priority.

[0517] A terminal may perform a terminal capability report to a base station through the terminal capability, indicating that it can support at least one combination of [Event 1], [Event 2], [Event 3], and [Event 4]. For example, the terminal may report to the base station through the terminal capability that it can support a receive beam performance report initiated from the terminal for [Event 1]. For example, the terminal may report to the base station through the terminal capability that it can support a receive beam performance report initiated from the terminal for [Event 2]. For example, the terminal may report to the base station through the terminal capability that it can support receive beam performance reports initiated from the terminal for [Event 1] and [Event 2].

[0518] For the above-described [Event 1], [Event 2], [Event 3], or [Event 4], the terminal may define a timer for not monitoring the occurrence of a specific event. For example, when beam switching occurs from the base station, the terminal may not monitor the specific event defined in [Event 1] to [Event 4] for a certain period of time from that time. For another example, after the specific event defined in [Event 1] to [Event 4] occurs, the terminal may not monitor the specific event defined in [Event 1] to [Event 4] for a certain period of time from that time. This prevents frequent information exchange and beam switching between the terminal and the base station by preventing channel state information reporting initiated from the terminal for a certain period of time after the base station sets or instructs beam switching.

[0519] The terminal may monitor only one of the above-described [Event 1], [Event 2], [Event 3], or [Event 4] and perform channel state information reporting initiated from the terminal when the corresponding event occurs, or may independently monitor one or more specific events and perform channel state information reporting initiated from the terminal corresponding to each event, or may individually monitor one or more specific events, but if more than one event occurs simultaneously, perform channel state information reporting initiated from 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 commonly. If the terminal monitors one or more events, commonly applying the timer may mean that the timer to be applied when a specific event occurs is applied equally to other events.

[0520] As one embodiment of the present disclosure, a terminal-initiated CSI reporting method is described. This embodiment can be operated in combination with other embodiments.

[0521] After the specific event described above occurs for reporting channel state information originating from the terminal, the terminal may perform terminal-initiated channel state information reporting to transmit reception beam performance-related information to the base station. At this time, the terminal may perform terminal-initiated channel state information reporting by considering a combination of at least one of the following methods.

[0522] [Method 3-1]

[0523] A terminal may be configured with a PUCCH resource for requesting PUSCH resource allocation that can be transmitted to a base station, including a reception beam performance report originating from the terminal, and when the above-described specific event 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 be configured with a PUCCH resource from the base station through upper layer signaling for reporting on the reception beam performance originating from the terminal, and this may be separate configuration information from a PUCCH resource for a conventional uplink data scheduling request. Such a PUCCH resource may include 1 bit of information.

[0524] In addition, the terminal may be configured with one PUCCH resource that can simultaneously request a combination of at least one 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 uplink data scheduling, and two bits of information can be transmitted in the PUCCH resource. If the PUCCH resource has an information bit of "01", the PUCCH resource may mean a conventional uplink data scheduling request, and if it is "10", the PUCCH resource may trigger 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 if it is "11", the PUCCH resource may trigger both a request for PUSCH resource allocation that can be transmitted to the base station including an uplink data scheduling request and a reception beam performance report originating from the terminal. If the base station receives the corresponding PUCCH resource with information bits of "11" from the terminal, the base station may force the terminal to transmit one DCI to include both PUSCH scheduling information and PUSCH scheduling information for receiving beam performance reporting initiated from the terminal and information indicating that the PUSCH should include receiving beam performance reporting initiated from the terminal. In this case, the DCI may also schedule a PUSCH that may include both uplink data and receiving beam performance reporting. This technique is merely an example, and the present disclosure is not limited by the above example.

[0525] At this time, the terminal may be configured with a slot-based period and offset for a PUCCH resource that triggers a reception beam performance report initiated from the terminal, or a PUCCH resource that can simultaneously request at least one combination of a reception beam performance report initiated from the terminal and uplink data scheduling, and the terminal may transmit the described information on the PUCCH resource at the closest period after a specific time offset from the time of occurrence of the specific event when the specific event occurs. The described information may be referred to as a scheduling request. At this time, the specific time offset may be defined in units of slots or ms, and may include 0 among possible values ​​(i.e., a specific time offset may not be required). This time offset may be defined as a terminal capability and reported by the terminal to the base station, or 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.

[0526] FIG. 11 is a diagram illustrating an example of an 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.

[0527] The terminal (1101) can receive a set of periodic channel measurement reference signals from the base station (1102) through upper layer signaling, and can measure reception beam performance by periodically receiving the periodic channel measurement reference signals (1105). Thereafter, if a specific event occurs in the terminal (1110), the terminal can transmit a signal to the base station on a PUCCH resource that triggers a reception beam performance report initiated from the terminal. The specific event may correspond to at least one of the events 1 to 4 described above. The corresponding PUCCH resource may be a PUCCH resource for an uplink data scheduling request and an individual PUCCH resource as described above, or may be a PUCCH resource for requesting a combination of at least one of an uplink data scheduling request and a reception beam performance report request initiated from the terminal to the base station. In response, the base station may transmit to the terminal a PDCCH that triggers a reception beam performance report initiated from the terminal (or schedules a PUSCH for transmitting the reception beam performance report) (1120), and the terminal may calculate a UCI according to a reception beam performance report request initiated from the terminal in response thereto and transmit it to the base station by including it in a PUSCH scheduled by the PDCCH (1125). Thereafter, if the base station determines that beam switching is necessary for the terminal (1130), the base station may set or instruct the terminal to perform beam switching (1135).

[0528] Considering the aforementioned [Method 3-1], the process of reporting channel state information (CSI) initiated by the terminal may be relatively lengthy, resulting in insufficient gains in terms of latency. However, as previously described, since the base station must transmit aperiodic CSI report triggering to the terminal based on non-direct information according to the existing standards, although the aperiodic CSI reporting method exists, it may not be fully utilized. Therefore, when the terminal initiates the CSI report triggering, there may be a clear gain in latency compared to the conventional method. Furthermore, since the CSI triggering is transmitted to the base station via a single PUCCH resource along with the uplink data scheduling request, there may be gains in terms of signaling overhead. Furthermore, since the CSI report initiated by the corresponding terminal is transmitted via the PUSCH, UCIs of various maximum lengths can be transmitted from the terminal to the base station, allowing for a wide range of information volumes exchanged between the terminal and the base station, from a small number of bits to a large number of bits, the method can be applied to a variety of methods.

[0529] [Method 3-2]

[0530] For reporting channel state information initiated from the terminal, the terminal can receive from the base station a pair of PUCCH resources and PUSCH transmissions for which transmission is reserved. At this time, the terminal can generate the channel state information initiated 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 can receive configuration of a slot-based period and offset for the PUCCH resource and PUSCH transmission, and can receive configuration of PUSCH transmission-related parameters such as a time offset between the PUCCH resource and PUCCH transmission, time and frequency resource allocation information for PUSCH transmission, MCS (e.g., the lowest value), the number of MIMO layers (e.g., 1), DMRS ports (e.g., 0), and waveform (e.g., CP-OFDM).

[0531] In another method, the terminal may be configured with a slot-based period and offset for the PUCCH resource, and may be configured with upper layer signaling related to the Configured Grant Type 1 PUSCH transmission assuming a PUSCH transmission based on a configured grant of the first type for PUSCH transmission, and may consider a method of transmitting the PUSCH in a period only when a signal is transmitted in the PUCCH resource before the PUSCH transmission period, rather than transmitting the PUSCH in every period. In addition, when the specific event occurs, the terminal may transmit a signal in the PUCCH resource of the period closest after a specific time offset from the time point of occurrence of the specific event. In this case, the specific time offset may be defined in units of slots or ms, and may include 0 among possible values ​​(i.e., the specific time offset may not be required). Such time offsets may be defined as terminal capabilities and reported by the terminal to the base station, or notified by the base station through a combination of at least one of upper layer signaling, MAC-CE signaling, L1 signaling, or through a combination of at least one of the methods fixed in the standard.

[0532] FIG. 12 is a diagram illustrating an example of an 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.

[0533] A terminal (1201) can receive a set of periodic channel measurement reference signals from a base station (1202) through upper layer signaling, and can periodically receive the periodic channel measurement reference signals to measure reception beam performance (1205). Thereafter, if a specific event occurs in the terminal (1210) (the specific event may correspond to at least one of events 1 to 4 described above), the terminal can transmit a signal to the base station on the PUCCH resource (1215), and thereafter, the terminal can perform PUSCH transmission after a time offset between the PUCCH resource set for the terminal and the PUSCH transmission (1220), and may include UCI or MAC-CE in the PUSCH. Thereafter, if the base station determines that beam switching is necessary for the terminal (1225), it can set or instruct this to the terminal (1230).

[0534] Considering the above-described [Method 3-2], there may be an advantage in terms of delay time since the process of reporting channel state information initiated by the terminal may be relatively shortened. However, the terminal requires reserved PUCCH resources and PUSCH transmission resources, and if at least one of the two channels is incorrect during blind decoding at the base station, the base station may fail to decode the received beam performance report initiated by the terminal that the terminal intended to transmit, and may need to perform decoding again for the PUCCH and PUSCH transmitted again by the terminal in order to properly receive it.

[0535] The terminal may be notified by the base station of at least one combination of [Method 3-1] or [Method 3-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 3-1] or [Method 3-2] is fixedly defined in the standard. Additionally, if the terminal is notified by the base station of at least one combination of specific methods 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 combinations of methods. For example, the terminal may expect that [Method 3-2] is fixedly defined in the standard for the channel state information reporting method and process initiated from the terminal described above. As another example, the terminal may be notified from the base station about the above [Method 3-1] through a combination of at least one of upper layer signaling, MAC-CE signaling, and L1 signaling, and in this case, the terminal may consider that it has been notified by the base station that the above [Method 3-2] is not supported.

[0536] The terminal may report to the base station, based on the terminal capability, whether it can support at least one combination of [Method 3-1] or [Method 3-2]. In this case, if the terminal reports to the base station, based on the terminal capability, that it can support a combination of one or more specific methods, it may be regarded as reporting that the terminal cannot support one or more other combinations of methods. For example, the terminal may report to the base station, based on the terminal capability, whether it can support [Method 3-1] or [Method 3-2]. As another example, the terminal may report to the base station that it can support [Method 3-1], and this terminal capability report may mean that the terminal cannot support [Method 3-2].

[0537] The above-described [Method 3-1] or [Method 3-2] both consider periodic channel state information reporting as a conventional channel state information reporting method, but the terminal may also consider a semi-persistent channel state information reporting method or / and an aperiodic channel state information reporting method for channel state information reporting initiated from the terminal, and in the case of a channel measurement reference signal for this, not only a periodic reference signal but also semi-persistent and aperiodic reference signals may be considered.

[0538] For the above-described [Method 3-1] or [Method 3-2], the terminal may define an arbitrary timer to not perform channel state information reporting initiated from the terminal for a certain period of time after performing channel state information reporting initiated from the terminal according to each method. This prevents frequent channel state information reporting from the terminal, 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.

[0539] As one embodiment of the present disclosure, a method for initiating a reception beam performance report starting from a terminal is described. This embodiment may operate in combination with other embodiments.

[0540] A terminal can be notified by a base station to perform a terminal-initiated receive beam report through various methods. The terminal can perform terminal-initiated receive beam performance reporting while minimizing terminal power consumption in situations where terminal-initiated receive beam performance reporting is required by receiving control signaling from the base station, such as to continue or stop the terminal-initiated receive beam performance reporting. If there is no such control signaling from the base station, the terminal can perform terminal-initiated receive beam performance reporting without restriction, and if the link between the terminal and the base station is very good, there may be periods where the terminal power is wasted.

[0541] Accordingly, the terminal can be notified by the base station that it will perform a reception beam report initiated by the terminal, and conversely, it can be notified that it will stop performing a reception beam report initiated by the terminal. The notification method from the base station can be received by the terminal using a combination of at least one of the following items.

[0542] [Method 4-1]

[0543] A terminal can be configured to initiate a reception beam performance report initiated from the terminal via upper layer signaling from a base station. That is, when a specific upper layer signaling is configured from the base station, the terminal can perform a reception beam performance report initiated from the terminal and also perform measurement for a corresponding reference signal. When the terminal receives a signaling to release the configuration of the corresponding upper layer signaling from the base station (e.g., an RRC release message), the terminal can stop performing the reception beam performance report initiated from the terminal that was previously configured and also stop performing measurement for the corresponding reference signal.

[0544] A terminal may receive configuration information from a base station regarding a reception beam performance report initiated from the terminal for one of the upper layer signaling, CSI-ReportConfig. At this time, the terminal may expect the following to be included in the upper layer signaling, CSI-ReportConfig.

[0545] - The terminal may be configured with either [Method 3-1] or [Method 3-2] for reporting reception beam performance starting from the terminal. If the terminal is configured with [Method 3-1], the terminal may be configured with PUCCH resource-related information, and may be configured with a period and slot offset for the corresponding PUCCH resource. If the terminal is configured with [Method 3-2], in addition to being configured with PUCCH resource-related information and a period and slot offset for the corresponding PUCCH resource, the terminal may also be configured with PUSCH transmission-related information. At this time, the terminal may be configured based on upper layer signaling information related to the configured grant when the PUSCH transmission-related information is configured, and the configuration information may include a period, slot offset, MCS, DMRS port, TPMI, transmission method, etc. for transmitting the corresponding PUSCH.

[0546] - The terminal may be configured with one of the conventional periodic (periodic CSI reporting), semiPersistentOnPUCCH (semi-persistent CSI reporting via PUCCH), semiPersistentOnPUSCH (semi-persistent CSI reporting via PUSCH), and aperiodic (aperiodic CSI reporting via PUSCH) for the upper layer signaling reportConfigType, or may be configured with a new type to indicate a reception beam performance report initiated from the terminal (e.g., ueInitiated). The terminal may configure PUCCH resource or PUSCH transmission-related configuration information that can be configured according to the above-described [Method 3-1] or [Method 3-2] in the reportConfigType, or may be configured in another part of CSI-ReportConfig.

[0547] - The terminal can expect the upper layer signaling, reportQuantity, to be set to a value that can indicate that L1-RSRP is reported and that it is reported based on some kind of reference signal and that it is a receive beam performance report initiated from the terminal. For example, the terminal can be set to a value such as cri-RSRP or ssb-Index-RSRP, which are upper layer signaling, or cri-RSRP-UEinitiated or ssb-Index-RSRP-UEinitiated, which can indicate that it is a receive beam performance report initiated from the terminal. The above are examples and may not be limited thereto.

[0548] - The terminal can expect to be configured with the events to be considered when reporting the reception beam performance originating from the terminal. If only one of the above-mentioned events is defined in the standard, the terminal can be configured to monitor and report on that one event through upper layer signaling. If one or more of the above-mentioned events are defined in the standard, the terminal can be configured by the base station to monitor and report on any of the events through upper layer signaling. In addition, the terminal can be configured with additional information depending on which event is configured.

[0549] ■ For example, if the terminal is set to one of the above [Event 1], [Event 3], or [Event 4], the terminal may be set to the number of new receiving beams that can be monitored.

[0550] ■ Also, especially in the case of [Event 1], the terminal can be set by upper layer signaling whether to determine the current receiving beam as a reference signal set as a QCL source within the currently indicated and applied TCI state, or as an SSB in a QCL relationship with the reference signal.

[0551] ■ Also, especially in the case of [Event 1], the terminal can be set by upper layer signaling for a specific reference value that can determine whether an event has occurred, and the specific reference value can be used when the terminal determines whether an event has occurred, when detecting the presence of a new reception beam that is higher than the performance of the current reception beam by the specific reference value. This specific reference value can be similarly applied to [Event 3] or [Event 4].

[0552] ■ In case of [Case 2], the terminal can set a specific reference value to compare with the performance of the current receiving beam.

[0553] ■ In the case of [Event 1], the terminal may receive upper layer signaling that determines whether the performance of the current receive beam is included in the receive beam performance report originating from the terminal. This upper layer signaling can be similarly applied to [Event 3] or [Event 4], and when applied to [Event 3] or [Event 4], the reference signal index of the current receive beam may also be included in the receive beam performance report originating from the terminal.

[0554] - The terminal can set timers and counters for each event to be used when determining that a specific event has occurred.

[0555] - If the terminal is configured with [Method 3-1], the terminal may set a timer to retransmit the signal on the first PUCCH resource if the terminal does not receive DCI from the base station within a certain time after transmitting the signal on the first PUCCH resource. In addition, the terminal may set a timer to not report the reception beam performance initiated from the terminal for a certain time after the second PUSCH transmission.

[0556] - If the terminal is set to [Method 3-2], the terminal may be set to a timer that prevents the terminal from reporting the reception beam performance initiated from the terminal for a specific period of time after signal transmission on the first PUCCH resource or after the second PUSCH transmission.

[0557] The terminal can receive configuration information for a reception beam performance report initiated from the terminal from the base station through a method of receiving configuration information in a configured grant-related setting other than the CSI-ReportConfig or in a new upper layer signaling for the above-described matters.

[0558] When the terminal operates in the above [Method 3-1], if the terminal operates in [Method 4-1] based on CSI-ReportConfig including upper layer signaling configuration information considering the above-described matters, the terminal can expect that the code point of the CSI request field in the PDCCH received from the base station during the process of the above [Method 3-1] triggers the CSI-ReportConfig. Through this, the terminal can report to the base station including the reception beam report information initiated from the terminal in the PUSCH during the process of the above [Method 3-1].

[0559] - If the terminal has configured the reception beam reporting method initiated from the terminal based on one event from the base station, the terminal can configure one CSI-ReportConfig from the base station, and the CSI-ReportConfig can be expected to include configuration information for the reception beam performance report initiated from the terminal. In addition, if the terminal receives the configuration for each code point in the CSI request field in DCI format 0_1, 0_2, or 0_3 from the base station through upper layer signaling, the CSI-ReportConfig including the configuration information for the reception beam reporting method initiated from the terminal may not be expected to be configured to the same code point as another CSI-ReportConfig. That is, if the terminal receives the configuration for the reception beam reporting method initiated from the terminal when the CSI-ReportConfig including the configuration information for the reception beam reporting method initiated from the terminal is connected to a specific code point of the CSI request field when the terminal receives the configuration for the upper layer signaling from the base station, the terminal can consider that only the trigger for the corresponding CSI-ReportConfig is possible through the corresponding code point, and that the trigger for another CSI-ReportConfig is impossible.

[0560] - If the terminal has been configured by the base station for a terminal-initiated reception beam reporting method based on one event, the terminal can expect to receive one CSI-ReportConfig from the base station, and the CSI-ReportConfig includes configuration information for a terminal-initiated reception beam performance report. At this time, the terminal can expect that in addition to the CSI-ReportConfig for the terminal-initiated reception beam report, the configuration for another CSI-ReportConfig can also be included in a specific code point of the CSI request field in the DCI. That is, if the terminal has been instructed by the base station for a code point of the CSI request field in the DCI that includes a CSI-ReportConfig including information for a terminal-initiated reception beam report, the terminal can expect that the terminal will also perform channel state information reporting for another CSI-ReportConfig within the corresponding code point.

[0561] - If a terminal has been configured with one or more terminal-initiated reception beam reporting schemes by the base station, and each terminal-initiated reception beam reporting scheme is based on a single event, i.e., if there are multiple events that the terminal should consider, the terminal can expect to receive individual CSI-ReportConfigs configured for each terminal-initiated reception beam reporting scheme corresponding to each event. In this case, the terminal can expect that there is no restriction on each of the one or more CSI-ReportConfigs being associated with each code point of the CSI request field in the DCI. At this time, if a specific event does not occur among the reception beam report configurations initiated from one or more terminals and thus the terminal does not transmit a signal in the first PUCCH resource based on upper layer signaling for the event, if the terminal is triggered by a specific codepoint through a CSI request field in DCI from the base station and the codepoint includes a CSI-ReportConfig that includes information about a reception beam report initiated from a terminal in which the event did not occur, the terminal may ignore the reception beam report for the corresponding CSI-ReportConfig, and if another CSI-ReportConfig is set for the same codepoint, channel state information reporting for the other CSI-ReportConfigs may be performed conditionally.

[0562] - If a terminal has been configured with one or more terminal-initiated reception beam reporting schemes by the base station, and each terminal-initiated reception beam reporting scheme is based on a single event, i.e., if there are multiple events that the terminal should consider, the terminal can expect to receive individual CSI-ReportConfigs configured for each terminal-initiated reception beam reporting scheme corresponding to each event. In this case, the terminal can receive one or more CSI-ReportConfigs from the base station through upper layer signaling, configured to be linked to the same codepoint of the CSI request field. That is, the terminal can expect that one or more CSI-ReportConfigs related to reception beam reporting initiated from the terminal are all set within CSI-AperiodicTriggerState, which is an upper layer signaling that contains information about a specific code point of a CSI request field in DCI, and the base station can instruct the terminal with additional information within CSI-AperiodicTriggerState, which is an upper layer signaling, so that reception beam reporting for the corresponding event can be triggered depending on which event the terminal transmitted a signal on the first PUCCH resource for which one or more CSI-ReportConfigs were set, i.e., depending on which event occurred from the terminal. For example, the terminal may receive a bitmap having a length equal to the number of one or more CSI-ReportConfigs related to reception beam reporting initiated from the terminal in the upper layer signaling CSI-AperiodicTriggerState from the base station, and when a bit at a specific position of the bitmap is 1, the terminal may be instructed to trigger reception beam reporting (for an event corresponding to the corresponding CSI-ReportConfig) for the corresponding CSI-ReportConfig.

[0563] - If a terminal has been configured by a base station with one or more terminal-initiated reception beam reporting schemes, and each terminal-initiated reception beam reporting scheme is based on a single event, i.e., if the terminal has multiple events to consider, the terminal can expect to receive individual upper layer signaling configurations for each terminal-initiated reception beam reporting scheme corresponding to each event within a single CSI-ReportConfig. That is, the terminal can receive from the base station a configuration method for detailed channel state information reporting for each terminal-initiated reception beam reporting scheme within a single CSI-ReportConfig. For example, if a terminal has been configured by a base station with terminal-initiated channel state information reporting for each of two events within a single CSI-ReportConfig, the terminal can be individually configured for either [Method 3-1] or [Method 3-2] for each event, or can be configured to have the same one of [Method 3-1] or [Method 3-2] applied to both events. The terminal may be instructed by the base station via DCI which detailed channel state information report within the CSI-ReportConfig is triggered, for example via upper layer signaling associated with each code point of the CSI request field, when the corresponding CSI-ReportConfig is associated with a specific code point of the CSI request field within the DCI.

[0564] When the terminal operates in the above [Method 3-1], if the terminal operates in [Method 4-1] based on a configured grant or a new upper layer signaling that includes upper layer signaling configuration information that takes into account the above-described matters, the terminal may expect that a CSI request field in a PDCCH received from the base station during the process of the above [Method 3-1] or a new field in the corresponding PDCCH triggers a reception beam report. In this case, if the terminal is triggered to report a reception beam based on a new field, the terminal may assume that the length of the new field is based on an event configured by the terminal from the base station. If the terminal has been configured by the base station to report a reception beam initiated by the terminal based on one event, the terminal may assume that the length of the new field is 1 bit. If a terminal has been configured by the base station to report a reception beam originating from one or more terminals, and if each reception beam report originating from a terminal is based on a single event, i.e., if there are multiple events that the terminal should consider, the terminal can expect the length of the new field to be defined as ceil(log2(N+1)), where ceil(.) is a rounding function, log2(.) is a logarithmic function with a base of 2, and N can mean the number of events.

[0565] If the terminal has initiated a terminal-initiated receive beam performance reporting operation by receiving the above-described upper layer signaling and has not yet received an initial indication of the integrated TCI state from the base station, the terminal may determine the current receive beam as the SSB identified in the most recent random access process for [Event 1] to [Event 4]. In addition, the terminal may expect that the number of new receive beams for [Event 1] will be set equal to the number of SSBs that the terminal is set to be able to monitor. For example, the terminal may expect that the value of the upper layer signaling set to the number of new receive beams and the number of 1s in ssb-positionsinburst, which is an upper layer signaling that can express the number of SSBs that the terminal can monitor in bitmap form, are equal.

[0566] If the terminal can start the reception beam performance reporting operation initiated from the terminal by receiving the above-described upper layer signaling, but before the terminal receives the integrated TCI state related upper layer signaling, the terminal can define the current reception beam and the new reception beam through SSB as described above before receiving the integrated TCI state related upper layer signaling.

[0567] When the terminal receives a release request (RRC release message) from the base station for the upper layer signaling (e.g., CSI-ReportConfig, configured grant related settings, or new upper layer signaling), the terminal can stop receiving beam reporting initiated from the terminal. That is, the terminal can perform receiving beam reporting initiated from the terminal through semi-static signaling, and then stop performing receiving beam reporting initiated from the terminal by receiving semi-static signaling again.

[0568] [Method 4-2]

[0569] The terminal may be instructed to start receiving beam performance reporting initiated from the terminal via DCI format 1_1 or 1_2 indicating an integrated TCI state without downlink scheduling information from the base station. The terminal may receive configuration information for receiving beam reporting initiated from the terminal from the base station via upper layer signaling similar to [Method 4-1], and may receive additional configuration information from the base station indicating that it operates as [Method 4-2].

[0570] A terminal may be instructed to receive an integrated TCI state without downlink scheduling information (without DL assignment) based on the conditions of one or more specific DCI fields located in DCI format 1_1 or 1_2. If a terminal receives DCI format 1_1 or 1_2 from a base station that does not include downlink data channel scheduling information and is instructed to receive a joint TCI state or a set of separate TCI states based on the integrated TCI method, the terminal may assume at least one combination of the following for the corresponding DCI.

[0571] - Includes scrambled CRC using CS-RNTI.

[0572] - All bits assigned to all fields used as RV (Redundancy Version) fields have a value of 1.

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

[0574] - All bits assigned to all fields used as NDI (New Data Indication) fields have values ​​of 0.

[0575] - For FDRA (Frequency Domain Resource Allocation) Type 0, the value of all bits assigned to the FDRA field is 0, for FDRA Type 1, the value of all bits assigned to the FDRA field is 1, and when the FDRA method is dynamicSwitch, the value of all bits assigned to the FDRA field is 0.

[0576] A terminal may be instructed to initiate a reception beam performance report initiated from the terminal without downlink scheduling information (without DL assignment) based on the conditions of one or more specific DCI fields located within DCI format 1_1 or 1_2. If the terminal receives DCI format 1_1 or 1_2 from the base station that does not include downlink data channel scheduling information and indicates one joint TCI state or a set of separate TCI states based on the integrated TCI scheme, the terminal may assume at least one combination of the following for the corresponding DCI.

[0577] - As an example, the terminal may be instructed to start receiving beam performance reporting initiated from the terminal when the terminal includes a scrambled CRC using a new RNTI instead of CS-RNTI under the condition of the DCI format 1_1 or 1_2 that can indicate an integrated TCI state without the downlink scheduling information.

[0578] - As an example, in addition to the conditions of the DCI format 1_1 or 1_2 that can indicate an integrated TCI state without the downlink scheduling information, the terminal can receive an instruction to start a reception beam performance report initiated from the terminal, rather than an integrated TCI state instruction, through conditions for fields other than the RV, MCS, NDI, and FDRA fields used. In this case, other fields other than the RV, MCS, NDI, and FDRA fields that can be used, such as a HARQ process ID field, a TDRA field, and an Antenna port field, may exist, and if the values ​​of all bits assigned to these fields are 1 or 0, the terminal can regard it as an instruction to start a reception beam performance report initiated from the terminal. When instructing to start a reception beam report initiated from a terminal, if the condition of a specific field in the DCI format 1_1 or 1_2 below is that all bits have a value of 0, the terminal may consider that when receiving an instruction to stop a reception beam report initiated from the terminal, the condition of a specific field in the DCI format 1_1 or 1_2 below is that all bits have a value of 1.

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

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

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

[0582] ■ 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 when the FDRA method is dynamicSwitch, the value of all bits allocated to the FDRA field is 0.

[0583] ■ HARQ process ID field: All bits have values ​​of 0 or 1

[0584] ■ TDRA field: All bits have values ​​of 0 or 1

[0585] ■ Antenna port field: All bits have values ​​of 0 or 1

[0586] [Method 4-3]

[0587] A terminal may be instructed to start receiving beam performance reporting initiated from the terminal via DCI format 1_1 or 1_2, which indicates an integrated ...

Claims

1. In a method performed by a terminal in a wireless communication system, A step of receiving, from a base station, configuration information related to receiving beam reporting through upper layer signaling; and A step of transmitting a reception beam report to a base station based on the above reception beam report-related setting information; A method characterized in that the above receive beam report includes at least one of a performance value of a current receive beam, an index of a new receive beam, or a performance value of at least one new receive beam.

2. A method according to claim 1, characterized in that the performance value of at least one new receiving beam is higher than the performance value of the current receiving beam.

3. In paragraph 1, the reception beam report is initiated by the terminal based on a predefined event, and A method characterized in that the above-defined event comprises a performance value of at least one new receiving beam being higher than a performance value of the current receiving beam.

4. A method according to claim 1, characterized in that the performance value of the current reception beam and the performance value of the at least one new reception beam include L1-RSRP (reference signal received power).

5. In the first paragraph, the performance value of at least one new receiving beam is: A method characterized in that it includes a performance value of a first new receiving beam having the largest performance value among the at least one new receiving beam.

6. In paragraph 4, wherein said at least one new receive beam is a plurality of new receive beams, and A method characterized in that the performance value of at least one new receiving beam, excluding the performance value of the first new receiving beam, among the performance values ​​of the plurality of new receiving beams is expressed as a difference value with respect to the performance value of the first new receiving beam.

7. In a method performed by a base station in a wireless communication system, A step of transmitting, to the terminal, setting information related to receiving beam reporting through upper layer signaling; and A step of receiving a reception beam report from the terminal based on the above reception beam report-related setting information; A method characterized in that the above receive beam report includes at least one of a performance value of a current receive beam, an index of a new receive beam, or a performance value of at least one new receive beam.

8. A method according to claim 7, characterized in that the performance value of at least one new receiving beam is higher than the performance value of the current receiving beam.

9. A method according to claim 7, characterized in that the performance value of the current reception beam and the performance value of the at least one new reception beam include L1-RSRP (reference signal received power).

10. In the 7th paragraph, the performance value of the at least one new receiving beam is: A method characterized in that it includes a performance value of a first new receiving beam having the largest performance value among the at least one new receiving beam.

11. In paragraph 10, wherein said at least one new receive beam is a plurality of new receive beams, and A method characterized in that the performance value of at least one new receiving beam, excluding the performance value of the first new receiving beam, among the performance values ​​of the plurality of new receiving beams is expressed as a difference value with respect to the performance value of the first new receiving beam.

12. In a wireless communication system, at a terminal, Transmitter and receiver; and At least one processor; comprising: From the base station, receive the configuration information related to the reception beam report through upper layer signaling, and Based on the above reception beam report related setting information, the reception beam report is configured to be transmitted to the base station, A terminal characterized in that the above-mentioned reception beam report includes at least one of a performance value of a current reception beam, an index of a new reception beam, or a performance value of at least one new reception beam.

13. In the 12th paragraph, the at least one new receiving beam is a plurality of new receiving beams, The performance values ​​of the plurality of new receiving beams include the performance value of the first new receiving beam having the largest performance value among the at least one new receiving beam, and A terminal characterized in that the performance value of at least one new receiving beam, excluding the performance value of the first new receiving beam, among the performance values ​​of the plurality of new receiving beams is expressed as a difference value with respect to the performance value of the first new receiving beam.

14. In a wireless communication system, at a base station, Transmitter and receiver; and At least one processor; comprising: Transmitting the configuration information related to receiving beam report to the terminal through upper layer signaling, and Based on the above reception beam report related setting information, the reception beam report is configured to be received from the terminal, A base station, characterized in that the above receive beam report includes at least one of a performance value of a current receive beam, an index of a new receive beam, or a performance value of at least one new receive beam.

15. In paragraph 14, the at least one new receiving beam is a plurality of new receiving beams, The performance values ​​of the plurality of new receiving beams include the performance value of the first new receiving beam having the largest performance value among the at least one new receiving beam, and A base station characterized in that the performance value of at least one new receiving beam, excluding the performance value of the first new receiving beam, among the performance values ​​of the plurality of new receiving beams is expressed as a difference value with respect to the performance value of the first new receiving beam.

Images