Method and device for reporting channel information for simultaneous multi-panel transmission in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. The present disclosure relates to the operations of a terminal and a base station in a wireless communication system and, more specifically, to a method for transmitting and receiving beam-related information in order to perform simultaneous transmission and reception by using multiple panels in a wireless communication system, and a device capable of performing same. The present disclosure provides a device and method capable of effectively providing a service in a mobile communication system by using multiple panels.

Description

Method and device for reporting channel information for simultaneous multi-panel transmission in wireless communication system The present disclosure relates to operations of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for performing group-based beam reporting to support a multi-panel simultaneous transmission technique and a device capable of performing the same. 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, such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (㎜Wave), such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced by one-tenth. In the early stages of 5G mobile communication technology, the goal was to support services and meet performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and Massive Machine-Type Communications (mMTC), including 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, early 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. Currently, discussions are underway on improving and enhancing the initial 5G mobile communication technology in consideration of the services that the 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 location and status information transmitted by the vehicle, 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. In addition, standardization of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) to provide nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step RACH for NR to simplify random access procedures is also in progress, and standardization of system architecture / services for 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 is also in progress. When such 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, which will require enhanced functions and performance of 5G mobile communication systems and integrated operation of connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, AI service support, metaverse service support, drone communications, etc. using extended reality (XR), artificial intelligence (AI), and machine learning (ML) to efficiently support augmented reality (AR), virtual reality (VR), and mixed reality (MR). In addition, the development of these 5G mobile communication systems will require 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), and 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, and AI (Artificial Intelligence) from the design stage and AI-based communication technology that implements end-to-end AI support functions to realize system optimization, and ultra-high-performance communication and computing resources to provide services with a level of complexity that goes beyond the limits of terminal computing capabilities. It could serve as a basis for the development of next-generation distributed computing technologies that utilize this. The disclosed embodiment is intended to provide a device and method capable of effectively providing a service in a mobile communication system. Specifically, a device and method capable of efficiently performing uplink transmission using multiple panels are provided. In order to solve the above problems, the present invention relates to a method performed by a terminal of a communication system, comprising: a step of receiving, from a base station, configuration information regarding an additional beam-related information report for simultaneous transmission using multiple panels; and a step of transmitting the additional beam-related information to the base station, characterized in that the additional beam-related information is transmitted while being included in a PHR (power headroom report) MAC CE (medium access control control element) or transmitted while being included in a CSI (channel state information) report. In addition, in a method performed by a base station of a communication system, the method comprises: a step of transmitting configuration information for reporting additional beam-related information for simultaneous transmission using multiple panels to a terminal; and a step of receiving the additional beam-related information from the terminal, wherein the additional beam-related information is received while being included in a PHR (power headroom report) MAC CE (medium access control control element) or a CSI (channel state information) report. In addition, in a terminal of a communication system, a transmitter / receiver; and a control unit configured to receive setting information for reporting additional beam-related information for simultaneous transmission using multiple panels from a base station, and transmit the additional beam-related information to the base station, characterized in that the additional beam-related information is transmitted while being included in a PHR (power headroom report) MAC CE (medium access control control element) or transmitted while being included in a CSI (channel state information) report. In addition, in a base station of a communication system, a transmitter / receiver; and a control unit configured to transmit setting information for reporting additional beam-related information for simultaneous transmission using multiple panels to a terminal, and receive the additional beam-related information from the terminal, characterized in that the additional beam-related information is received while being included in a PHR (power headroom report) MAC CE (medium access control control element) or included in a CSI (channel state information) report. The disclosed embodiments provide a device and method capable of effectively providing a service in a mobile communication system. Specifically, according to at least one embodiment of the present disclosure, a terminal and a base station can efficiently perform uplink simultaneous transmission using multiple panels. FIG. 1 is a diagram illustrating an example of 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. FIG. 2 is a diagram illustrating an example of a frame, subframe, and slot structure in a 5G system. Figure 3 is a diagram illustrating an example of bandwidth portion settings of a 5G system. Figure 4 is a diagram illustrating an example of base station beam allocation according to TCI state settings. FIG. 5 is a diagram illustrating an example of a beam application time that can be considered when using an integrated TCI method in a 5G system. FIG. 6 is a diagram illustrating an example of a MAC-CE structure for activating and indicating a joint TCI state or separate DL or UL TCI state in a 5G system. Figure 7 is a diagram illustrating an example of frequency axis resource allocation of PDSCH or PUSCH in a 5G system. Figure 8 is a diagram illustrating an example of time axis resource allocation of PDSCH in a 5G system. FIG. 9 is a diagram illustrating an example of MAC CE for PUCCH resource group-based spatial relationship activation in a 5G system. FIG. 10 is a diagram illustrating an example of PUSCH repetition transmission type B in a 5G system. FIG. 11 is a diagram illustrating an example of a MAC CE format for a PHR with a single entry according to a 5G system. FIG. 12a is a diagram illustrating an example of a MAC CE format for a PHR with multiple entries according to a 5G system. FIG. 12b is a diagram illustrating another example of a MAC CE format for a PHR with multiple entries according to a 5G system. FIG. 13 is a diagram illustrating an example of antenna port configuration and resource allocation for transmitting a PDSCH using cooperative communication in a wireless communication system according to an embodiment of the present disclosure. FIG. 14 is a diagram illustrating an example of a configuration of downlink control information (DCI) for NC-JT in which each TRP transmits a different PDSCH or a different PDSCH layer to a terminal in a wireless communication system according to an embodiment of the present disclosure. FIG. 15 is a diagram illustrating an example of a PDSCH TCI state indication method that can be applied to a multi-DCI based multi-TRP transmission method. Figure 16 is a diagram illustrating an example of an Enhanced PDSCH TCI state activation / deactivation MAC-CE structure. FIG. 17 is a diagram illustrating an example of a MAC-CE structure for activating and indicating multiple joint TCI states or separate DL or UL TCI states in a wireless communication system according to one embodiment of the present disclosure. FIG. 18 is a diagram illustrating another example of a MAC-CE structure for activating and indicating multiple joint TCI states or separate DL or UL TCI states in a wireless communication system according to an embodiment of the present disclosure. FIG. 19 is a diagram illustrating an example of two overlapping beams transmitted simultaneously by a terminal using a multi-panel. Figure 20 is a diagram illustrating an example in which a terminal adjusts the transmission power of two beams by considering the total EIRP. FIG. 21 is a diagram illustrating an example of a group-based beam report with additional information associated therewith when a PHR containing additional information about a beam combination reported by a terminal is not performed simultaneously with the group-based beam report. FIG. 22 is a diagram illustrating an example of an operation in which a terminal reports a group-based beam report and additional information associated therewith along with PH. Figure 23a is an example of a PH MAC CE format for a terminal to report the maximum transmission power value per beam of each beam combination to a base station along with PH information. Figure 23b is another example of a PH MAC CE format for a terminal to report the maximum transmit power value per beam of each beam combination to a base station along with PH information. Figure 24a is an example of a PH MAC CE format for a terminal to report the PH value for each beam combination to a base station together with existing PH information. Figure 24b is another example of a PH MAC CE format for a terminal to report the PH value per beam of each beam combination to the base station together with existing PH information. Figure 25a is an example of a PH MAC CE format for a terminal to report beam-specific MPE values ​​of each beam combination to a base station along with PH information. Figure 25b is another example of a PH MAC CE format for a terminal to report beam-specific MPE values ​​of each beam combination to a base station along with PH information. Figure 26a is an example of a PH MAC CE format for a terminal to report the degree of overlap for beams of each beam combination to a base station along with PH information. Figure 26b is another example of a PH MAC CE format for a terminal to report the degree of overlap for beams of each beam combination to a base station along with PH information. FIG. 27a is a diagram illustrating an example of operation of a terminal when supporting a power headroom-based multi-panel simultaneous transmission beam information reporting method according to the present disclosure. FIG. 27b is a diagram illustrating an example of the operation of a base station when supporting a power headroom-based multi-panel simultaneous transmission beam information reporting method according to the present disclosure. FIG. 28a is a diagram illustrating an example of operation of a terminal when supporting a CSI-based enhanced multi-panel simultaneous transmission beam information reporting method according to the present disclosure. FIG. 28b is a diagram illustrating an example of the operation of a base station when supporting a CSI-based enhanced multi-panel simultaneous transmission beam information reporting method according to the present disclosure. FIG. 29 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure. FIG. 30 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure. Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. In describing the embodiments, descriptions of technical contents that are well known in the technical field to which the present disclosure belongs and are not directly related to the present disclosure are omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary descriptions. For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically illustrated. In addition, the size of each component does not entirely reflect the actual size. The same or corresponding components in each drawing are given the same reference numbers. The advantages and features of the present disclosure, and the methods for achieving them, will become clear 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, but may be implemented in various different forms, and these embodiments are provided only to make the disclosure of the present disclosure complete and to fully inform a person having ordinary skill in the art to which the present disclosure belongs of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification. In addition, when describing the present disclosure, if it is determined that a specific description of a related function or configuration may 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 in the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definitions should be made based on the contents throughout the specification. Hereinafter, the base station is an entity that performs resource allocation of a 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, the downlink (DL) refers to a wireless transmission path of a signal that a base station transmits to a terminal, and the uplink (UL) refers to a wireless transmission path of a signal that a terminal transmits to a base station. In addition, although the LTE or LTE-A system may be described as an example below, the embodiments of the present disclosure may 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 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 through some modifications without significantly departing from the scope of the present disclosure, as judged by a person having skilled technical knowledge. At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be loaded onto 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 flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can be directed to 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 an article of manufacture that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing apparatus, a series of operational steps may be performed on the computer or other programmable data processing apparatus to produce a computer-implemented process, so that the instructions executing the computer or other programmable data processing apparatus may also provide steps for executing the functions described in the flowchart block(s). Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a particular logical function(s). It should also be noted that in some alternative implementation examples, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may in fact be performed substantially concurrently, or the blocks may sometimes be performed in reverse order, depending on the functionality they perform. 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 in an addressable storage medium and may be configured to reproduce one or more processors. Accordingly, 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 in the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. In addition, the components and '~parts' may be implemented to play one or more CPUs within the device or secure multimedia card. Also, in an embodiment, the '~part' may include one or more processors. Wireless communication systems are evolving from providing initial voice-oriented services 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. 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 and the SC-FDMA (single carrier frequency division multiple access) method in the uplink. The above multiple access method is usually allocated and operated so that the time-frequency resources for transmitting data or control information to each user do not overlap with each other, that is, so that orthogonality is established, thereby enabling the data or control information of each user to be distinguished. The 5G communication system, the future communication system after LTE, must be able to freely reflect various requirements of users and service providers, and therefore services that simultaneously satisfy various requirements must be supported. Services considered for the 5G communication system include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra reliability low latency communication (URLLC). eMBB aims to provide a data transmission rate that is higher than that supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, eMBB should be able to provide 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. In addition, the 5G communication system should provide an increased user perceived data rate while providing the peak data rate. To meet these requirements, it requires improvements in various transmission / reception technologies, including further improved multi-input multi-output (MIMO) transmission technology. In addition, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can satisfy the data transmission rate required by the 5G communication system by using a wider frequency bandwidth than 20 MHz in the 3 to 6 GHz or higher frequency band. 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 Internet of Things, mMTC requires support for connection of large numbers of terminals within a cell, improved coverage of terminals, improved battery life, and reduced cost of terminals. The Internet of Things provides communication functions by being attached to various sensors and devices, so a large number of terminals (for example, 1,000,000 terminals / km) are required within a cell. 2 ) must be able to support. In addition, terminals supporting mMTC are likely to be located in shadow areas that cells do not cover, such as basements of buildings, due to the nature of the service, and thus may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be composed of low-cost terminals, and since it is difficult to frequently replace the terminal's battery, a very long battery life time, such as 10 to 15 years, may be required. Finally, URLLC is a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, services used for remote control of robots or machinery, industrial automation, unmanaged aerial vehicles, remote health care, emergency alert, etc. 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 air interface latency less than 0.5 milliseconds and at the same time, must have a latency of 10 -5It has the following packet error rate requirements. Therefore, for services supporting URLLC, the 5G system must provide a smaller transmit time interval (TTI) than other services, and at the same time, a design requirement may be required to allocate a wide resource in the frequency band to secure the reliability of the communication link. The three services of 5G, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted in one system. At this time, different transmission and reception techniques and transmission and reception parameters can be used between services to satisfy the different requirements of each service. Of course, the 5G system is not limited to the three services mentioned above. Hereinafter, a / b can be understood as at least one of a or b. Below, the frame structure of the 5G system is described in more detail with reference to the drawings. FIG. 1 is a diagram illustrating an example of 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. The horizontal axis of Figure 1 represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time and frequency domains 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. FIG. 2 is a diagram illustrating an example of a frame, subframe, and slot structure in a 5G system. FIG. 2 illustrates an example of a structure of a frame (frame, 200), a subframe (subframe, 201), and a slot (slot, 202). 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. In the example of Fig. 2, the cases where the subcarrier spacing setting value μ = 0 (204) and μ = 1 (205) are illustrated. When μ = 0 (204), 1 subframe (201) may be composed of one slot (202), and when μ = 1 (205), 1 subframe (201) may be composed of two slots (203). That is, depending on the setting value μ for the subcarrier spacing, the number of slots ( ) 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. μ 0141011142022144043148084141601651432032 Next, the bandwidth part (BWP) setting in the 5G communication system will be specifically explained with reference to the drawing. Figure 3 is a diagram illustrating an example of bandwidth portion settings of a 5G system. FIG. 3 shows an example in which the UE bandwidth (300) is set to two bandwidth parts, namely, bandwidth part #1 (BWP#1, 301) and bandwidth part #2 (BWP#2, 302). The base station can set one or more bandwidth parts to the UE, and can set the information in Table 2 below for each bandwidth part. 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)} Of course, it is not limited to the above example, and in addition to the above setting information, various parameters related to the bandwidth portion can be set for the terminal. The above information can be transmitted from the base station to the terminal through 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 through RRC signaling or dynamically transmitted through DCI. According to some embodiments, a terminal before an RRC connection may be configured with an initial bandwidth portion (initial BWP) for initial access from a base station through a master information block (MIB). More specifically, the terminal may receive, through the MIB in the initial access phase, configuration information about a control resource set (CORESET) and a search space in which physical downlink control channel (PDCCH) s for receiving system information required for initial access (which may correspond to remaining system information (RMSI) or system information block 1 (SIB1)) may be transmitted. The CORESET and the search space configured by the MIB may each be regarded as an identifier (ID) 0. The base station may notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for CORESET#0 through the MIB. In addition, the base station can notify the terminal of the configuration information for the monitoring period and monitoring occasion for CORESET#0, i.e., the configuration information for the search space#0, through the MIB. The terminal can regard the frequency range set to CORESET#0 obtained from the MIB as an initial bandwidth part for initial access, and the terminal can receive the PDSCH (physical downlink shared channel) on which the SIB is transmitted through the set initial bandwidth part. At this time, the identifier (ID) of the initial bandwidth part can be regarded as 0. In addition to the purpose of receiving the SIB, the initial bandwidth part can also be utilized for other system information (OSI), paging, and random access. In a wireless communication system, one or more different antenna ports (or may be replaced with one or more channels, signals, and combinations thereof, but for convenience, they will be referred to as different antenna ports in the following description of the present disclosure) may be associated with each other by a QCL (quasi co-location) setting as shown in Table 3 below. The TCI state is to notify the QCL relationship between the PDCCH (or PDCCH DMRS) and other RSs or channels. When a certain reference antenna port A (reference RS #A) and another target antenna port B (target RS #B) are QCLed with each other, it means that the terminal is allowed to apply some or all of the large-scale channel parameters estimated at the antenna port A to the channel measurement from the antenna port B. QCL may need to relate different parameters depending on the situation, such as 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) radio resource management (RRM) affected by average gain, and 4) beam management (BM) affected by spatial parameters. Accordingly, 5G systems support four types of QCL relationships, as shown in Table 3 below. QCL typeLarge-scale characteristicsADoppler shift, Doppler spread, average delay, delay spreadBDoppler shift, Doppler spreadCDoppler shift, average delayDSpatial Rx parameter The above spatial RX parameter may collectively refer to some or all of various parameters, such as Angle of arrival (AoA), Power Angular Spectrum (PAS) of AoA, Angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, and spatial channel correlation. The above QCL relationship can be set to the terminal through the RRC parameters TCI-State and QCL-Info as shown in Table 4 below. Referring to Table 4, the base station can set one or more TCI states to the terminal and inform the RS referring to the ID of the TCI state, i.e., up to two QCL relationships (qcl-Type1, qcl-Type2) for the target RS. At this time, each QCL information (QCL-Info) included in the above TCI state includes the serving cell index and BWP index of the reference RS indicated by the corresponding QCL information, the type and ID of the reference RS, and the QCL type as shown in Table 3 above. TCI-State ::= SEQUENCE {tci-StateId TCI-StateId,(ID of the corresponding TCI state)qcl-Type1 QCL-Info,(QCL information of the first reference RS of the RS (target RS) referencing the corresponding TCI state ID)qcl-Type2 QCL-Info OPTIONAL, -- Need R(QCL information of the second reference RS of the RS (target RS) referencing the corresponding TCI state ID)...}QCL-Info ::= SEQUENCE {cell ServCellIndex OPTIONAL, -- Need R(serving cell index of the reference RS indicated by the corresponding QCL information)bwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-Indicated(BWP index of the reference RS indicated by the corresponding QCL information)referenceSignal CHOICE {csi-rs NZP-CSI-RS-ResourceId,ssb SSB-Index(Among the CSI-RS ID or SSB ID indicated by the corresponding QCL information) one)},qcl-Type ENUMERATED {typeA, typeB, typeC, typeD},...} Figure 4 is a diagram illustrating an example of base station beam allocation according to TCI state settings. Referring to FIG. 4, the base station can transmit information about N different beams to the terminal through N different TCI states. For example, when N=3 as in FIG. 4, the base station can notify that antenna ports referencing different TCI states 400, 405, or 410 have different spatial Rx parameters, that is, are associated with different beams, by causing the qcl-Type2 parameter included in three TCI states (400, 405, and 410) to be associated with CSI-RS or SSB corresponding to different beams and to be set to QCL type D. Tables 5 to 9 below show valid TCI state settings according to target antenna port type. Table 5 shows valid TCI state settings when the target antenna port is CSI-RS for tracking (i.e., TRS). The TRS refers to NZP CSI-RS in which the repetition parameter is not set among CSI-RSs and trs-Info is set to true. Setting 3 in Table 5 can be used for aperiodic TRS. Valid TCI state configurationDL RS1qcl-Type1DL RS2 (if configured)qcl-Type2 (if configured)1SSBQCL-TypeCSSBQCL-TypeD2SSBQCL-TypeCCSI-RS (BM)QCL-TypeD3TRS (periodic)QCL-TypeATRS (same as DL RS1)QCL-TypeD Table 6 shows valid TCI state settings when the target antenna port is CSI-RS for CSI. The CSI-RS for CSI means NZP CSI-RS in which a parameter indicating repetition (e.g., repetition parameter) among CSI-RSs is not set and trs-Info is not set to true. Valid TCI state configurationDL RS1qcl-Type1DL RS2 (if configured)qcl-Type2 (if configured)1TRSQCL-TypeASSBQCL-TypeD2TRSQCL-TypeACSI-RS (BM)QCL-TypeD3TRSQCL-TypeATRS (same as DL RS1)QCL-TypeD4TRSQCL-TypeB Table 7 shows valid TCI state settings when the target antenna port is CSI-RS for beam management (BM, which is the same as CSI-RS for L1 RSRP reporting). The CSI-RS for BM refers to NZP CSI-RS in which the repetition parameter is set among CSI-RSs and has a value of On or Off, and trs-Info is not set to true. Valid TCI state configurationDL RS1qcl-Type1DL RS2 (if configured)qcl-Type2 (if configured)1TRSQCL-TypeATRS (same as DL RS1)QCL-TypeD2TRSQCL-TypeACSI-RS (BM)QCL-TypeD3SSBQCL-TypeCSSBQCL-TypeD Table 8 shows the valid TCI state settings when the target antenna port is PDCCH DMRS. Valid TCI state configurationDL RS1qcl-Type1DL RS2 (if configured)qcl-Type2 (if configured)1TRSQCL-TypeATRS (same as DL RS1)QCL-TypeD2TRSQCL-TypeACSI-RS (BM)QCL-TypeD3CSI-RS (CSI)QCL-TypeACSI-RS (same as DL RS1)QCL-TypeD Table 9 shows the valid TCI state settings when the target antenna port is PDSCH DMRS. Valid TCI state configurationDL RS1qcl-Type1DL RS2 (if configured)qcl-Type2 (if configured)1TRSQCL-TypeATRSQCL-TypeD2TRSQCL-TypeACSI-RS (BM)QCL-TypeD3CSI-RS (CSI)QCL-TypeACSI-RS (CSI)QCL-TypeD A representative QCL setting method according to Tables 5 to 9 above is to operate by setting the target antenna port and reference antenna port for each step as "SSB" -> "TRS" -> "CSI-RS for CSI, or CSI-RS for BM, or PDCCH DMRS, or PDSCH DMRS". Through this, it is possible to link statistical characteristics that can be measured from SSB and TRS to each antenna port to assist the receiving operation of the terminal. Hereinafter, a single TCI state indication and activation method based on the unified TCI scheme is described. The unified TCI scheme can mean a method of integrating and managing the transmission / reception beam management methods, which were distinguished into the TCI state scheme used in downlink reception of the terminal and the spatial relation info scheme used in uplink transmission in the existing Rel-15 and 16, into a TCI state. Therefore, if the terminal is instructed by the base station based on the unified TCI scheme, the terminal 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 having tci-stateId-r17, which is an upper layer signaling, from the base station, the terminal can perform an operation 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. The first form is a joint TCI state, and a terminal can be instructed of both TCI states to be applied to uplink transmission and downlink reception through a single TCI-State from a base station. If the terminal is instructed of a TCI-State based on a joint TCI state, the terminal can be instructed of a parameter to be used for downlink channel estimation using an RS corresponding to qcl-Type1 in the TCI-State based on the joint TCI state, and a parameter to be used as a downlink reception beam or reception filter using an RS corresponding to qcl-Type2. If the terminal is instructed of a TCI-State based on a joint TCI state, the terminal can be instructed of a parameter to be used as an uplink transmission beam or transmission filter using an RS corresponding to qcl-Type2 in the joint DL / UL TCI state based TCI-State. In this case, if the terminal is instructed of a joint TCI state, the terminal can apply the same beam to both uplink transmission and downlink reception. The second form is a separate TCI state, and the terminal can be individually instructed by the base station of the UL TCI state to be applied to uplink transmission and the DL TCI state to be applied to downlink reception. If the terminal is instructed of the UL TCI state, the terminal can be instructed of parameters to be used as an uplink transmission beam or a transmission filter by using the reference RS or source RS set in the corresponding UL TCI state. If the terminal is instructed of the DL TCI state, the terminal can be instructed of parameters to be used for downlink channel estimation by using the RS corresponding to qcl-Type1 set in the corresponding DL TCI state, and parameters to be used as a downlink reception beam or a reception filter by using the RS corresponding to qcl-Type2. 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 by 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 by 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 by 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. A terminal can receive up to 128 joint TCI states from a base station for each bandwidth part in a specific cell through upper layer signaling, and among separate TCI states, DL TCI states can be set up to 64 or 128 for each bandwidth part in a specific cell through upper layer signaling based on terminal capability reporting. Among separate TCI states, DL TCI states and joint TCI states can use the same upper layer signaling structure. For example, if 128 joint TCI states are set and 64 DL TCI states are set among separate TCI states, the 64 DL TCI states can be included in the 128 joint TCI states. Among separate TCI states, the UL TCI state can be set to up to 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 separate TCI states, the UL TCI state and the joint TCI state among separate TCI may also use the same upper layer signaling structure, and the UL TCI state among separate TCI may use different upper layer signaling structures from the joint TCI state and the DL TCI state among separate TCI states. The use of such 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 terminal capability reports containing information on which of the two usage modes the terminal can support. The terminal can receive transmission / reception beam-related instructions in an integrated TCI manner by 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 through upper layer signaling as to whether to use one of the joint TCI state and separate TCI state. 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 can 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. If a terminal receives an instruction related to a transmit / receive beam using a joint TCI state method through upper layer signaling, the terminal can perform a transmit / receive beam application operation by receiving a MAC-CE indicating the joint TCI state from the base station, and the base station can schedule reception of a PDSCH including the corresponding MAC-CE through a PDCCH to the terminal. If the MAC-CE includes one joint TCI state, the UE can determine the uplink transmission beam or transmission filter and the downlink reception beam or reception filter using the indicated joint TCI state starting from 3 ms after the PUCCH transmission including HARQ-ACK information indicating the successful reception of the PDSCH including the MAC-CE, and 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 from 3 ms after the PUCCH transmission including HARQ-ACK information indicating the successful reception of the PDSCH including the MAC-CE, and activate the indicated joint TCI state. Thereafter, the UE can receive the 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). 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 the terminal to receive a PDSCH including the corresponding MAC-CE 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 by 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, a separate TCI state set can 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 can 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 can 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 the PUCCH transmission including HARQ-ACK information indicating whether reception for the corresponding PDSCH was successful, and can 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, the 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). FIG. 5 is a diagram illustrating an example of a beam application time that can be considered when using an integrated TCI scheme in a 5G system. As described above, a terminal may receive DCI format 1_1 or 1_2 including (with DL assignment) or not including (without DL assignment) downlink data channel scheduling information from a base station, and apply one joint TCI state or a separate TCI state set indicated by a TCI state field in the corresponding DCI to uplink transmission and downlink reception beams. - 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 one joint TCI state or a separate TCI state set based on the integrated TCI method is indicated, the terminal receives a PDSCH scheduled based on the received DCI (505), and can transmit a PUCCH including HARQ-ACK indicating whether reception of the DCI and the PDSCH was successful (510). At this time, the HARQ-ACK can include the meaning of whether reception of the DCI and the PDSCH was successful, and if at least one of the DCI and the PDSCH is not received, the terminal can transmit NACK, and if reception of both is successful, the terminal can transmit ACK. - 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 one joint TCI state or a separate TCI state set based on the integrated TCI scheme is indicated, the terminal may assume at least one combination of the following for the corresponding DCI. * Includes scrambled CRC using CS-RNTI. * All bits assigned to all fields used as RV (redundancy version) fields have a value of 1. * All bits assigned to all fields used as MCS (modulation and coding scheme) fields have a value of 1. * All bits assigned to all fields used as NDI (new data indication) fields have the value 0. * For FDRA (frequency domain resource allocation) Type 0, all bits allocated to the FDRA field have values ​​of 0, for FDRA Type 1, all bits allocated to the FDRA field have values ​​of 1, and when the FDRA method is dynamicSwitch, all bits allocated to the FDRA field have values ​​of 0. 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). - 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 point after the first slot (520, 570) after BAT (beam application time, 515, 565) after the PUCCH transmission (530, 580), and the previously indicated TCI state can be used until (525, 575) before the corresponding slot (520, 570). - For both DCI format 1_1 or 1_2 with DL assignment (500) and without DL assignment (550), the BAT can be configured 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 DCI is applied. A terminal can apply one joint TCI state indicated via MAC-CE or DCI to reception for all CORESETs connected to a terminal-specific search space, reception for PDSCHs scheduled as PDCCHs transmitted from the corresponding CORESETs, transmission for PUSCHs, and transmission of all PUCCH resources. A terminal can apply a separate TCI state set to all CORESETs connected to a terminal-specific search space, to the reception of PDSCHs scheduled as PDCCHs transmitted from the corresponding CORESETs, if a separate TCI state set indicated via MAC-CE or DCI includes a DL TCI state, and to all PUSCH and PUCCH resources based on the previously indicated UL TCI state. A terminal can apply a separate TCI state set indicated via MAC-CE or DCI to all PUSCH and PUCCH resources if the set includes one UL TCI state, and can apply the same to reception for CORESETs connected to all terminal-specific search spaces based on the previously indicated DL TCI state, and to reception for PDSCHs scheduled as PDCCHs transmitted from the corresponding CORESETs. A terminal may apply the DL TCI state to reception for all CORESETs associated with a terminal-specific search space and to reception for PDSCHs scheduled with PDCCHs transmitted from the corresponding CORESETs, when a separate set of TCI states indicated via MAC-CE or DCI includes one DL TCI state and one UL TCI state, and may apply the UL TCI state to all PUSCH and PUCCH resources. Hereinafter, a single TCI state indication and activation method based on the integrated TCI scheme is described. A terminal receives a PDSCH including the following MAC-CE from a 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. Fig. 6 is a diagram illustrating an example of a MAC-CE structure for activating and indicating a joint TCI state or a separate DL or UL TCI state in a 5G system. The meaning of each field in the MAC-CE structure may be as follows. - Serving Cell ID (600): This field can indicate to which serving cell the corresponding MAC-CE is applied. 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 corresponding 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, and simultaneousU-TCI-UpdateList4 that include the serving cell indicated by this field. - DL BWP ID (605): This field can indicate which DL BWP the corresponding MAC-CE is applied to, and the meaning of each code point of this field can correspond to each code point of the BWP indicator (bandwidth part indicator) in the DCI. The length of this field can be 2 bits. - UL BWP ID (610): This field can indicate which UL BWP the corresponding MAC-CE is applied to, and the meaning of each code point of this field can correspond to each code point of the BWP indicator in the DCI. The length of this field can be 2 bits. - 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 P is 1, it means that the corresponding i-th code point has multiple TCI states, which may mean that the corresponding code point may include a separate DL TCI state and a separate UL TCI state. If P i If the value is 0, it means that the corresponding i-th code point has a single TCI state, which may mean that the corresponding code point can include either a joint TCI state, a separate DCI TCI state, or a separate UL TCI state. - D / U (620): This field can indicate whether the TCI state ID field within the same octet is a joint TCI state, a separate DL TCI state, or a separate UL TCI state. If this field is 1, the TCI state ID field within the same octet can be a joint TCI state or a separate DL TCI state, and if this field is 0, the TCI state ID field within the same octet can be a separate UL TCI state. - 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 a TCI-StateId that 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. - R: Indicates reserved bit and can be set to 0. For the MAC-CE structure of Fig. 6 described above, the terminal sets P in Fig. 6 regardless of whether unifiedTCI-StateType-r17 in MIMOparam-r17 in ServingCellConfig, which is an upper layer signaling, is set to joint or separate. 1 , P 2 , 쪋, P 8 The third octet including the field can be included in the MAC-CE structure. In this case, the terminal can perform TCI state activation using the fixed MAC-CE structure regardless of the upper layer signaling set from the base station. As another example, for the MAC-CE structure of FIG. 6 described above, if unifiedTCI-StateType-r17 in MIMOparam-r17 in ServingCellConfig, which is an upper layer signaling, is set to joint, the terminal can perform TCI state activation using the fixed MAC-CE structure regardless of the upper layer signaling set from the base station. 1 , P 2 , ..., P 8The third octet containing the field can be omitted. 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. Next, we will specifically describe downlink control information (DCI) in 5G systems. In a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink data 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 with respect to the PUSCH or PDSCH. The fallback DCI format can be composed of fixed fields selected between the base station and the terminal, and the non-fallback DCI format can include configurable fields. DCI can be transmitted through PDCCH, which is a physical downlink control channel, after going through channel coding and modulation process. A CRC (cyclic redundancy check) is attached to the DCI message payload, and the CRC can be scrambled with an RNTI (radio network temporary identifier) ​​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 and transmitted. When receiving a DCI message transmitted on PDCCH, the UE checks the CRC using the allocated RNTI, and if the CRC check result is correct, the UE can know that the message was transmitted to the UE. 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). DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI can include, for example, the information in Table 10 below. - Identifier for DCI formats (DCI format identifier) ​​- [1] bit- Frequency domain resource assignment (Frequency domain resource assignment) - [ ] bits- Time domain resource assignment - X bits- Frequency hopping flag - 1 bit.- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- TPC command for scheduled PUSCH - [2] bits- UL / SUL indicator (uplink / supplementary UL indicator) - 0 or 1 bit DCI format 0_1 ​​can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI can include, for example, the information in Table 11 below. - Carrier indicator - 0 or 3 bits- UL / SUL indicator - 0 or 1 bit- Identifier for DCI formats - [1] bits- Bandwidth part indicator - 0, 1 or 2 bits- Frequency domain resource assignment- For resource allocation type 0 (For resource allocation type 0), bits- For resource allocation type 1 (For resource allocation type 1), bits- Time domain resource assignment -1, 2, 3, or 4 bits- VRB-to-PRB mapping (virtual resource block-to-physical resource block mapping) - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- Frequency hopping flag - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- 1st downlink assignment index (first downlink allocation index)- 1 or 2 bits○ 1 bit for semi-static HARQ-ACK codebook (semi-static HARQ-ACK In case of codebook);○ 2 bits for dynamic HARQ-ACK codebook with single HARQ-ACK codebook(When dynamic HARQ-ACK codebook is used together with single HARQ-ACK codebook). - 2nd downlink assignment index (2nd downlink assignment index) - 0 or 2 bits○ 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks(When dynamic HARQ-ACK codebook is used together with two HARQ-ACK sub-codebooks);○ 0 bit otherwise.TPC command for scheduled PUSCH - 2 bits- SRS resource indicator (SRS resource indicator) -. or bits○ bits for non-codebook based PUSCH transmission(If PUSCH transmission is not codebook based);○ bits for codebook based PUSCH transmission (When PUSCH transmission is codebook based). - Precoding information and number of layers (Precoding information and number of layers) - up to 6 bits - Antenna ports (Antenna ports) - up to 5 bits - SRS request (SRS request) - 2 bits - CSI request (Channel state information request) - 0, 1, 2, 3, 4, 5, or 6 bits - CBG transmission information (Code block group transmission information) - 0, 2, 4, 6, or 8 bits - PTRS-DMRS association (Phase tracking reference signal-Demodulation reference signal relationship) - 0 or 2 bits. - beta_offset indicator (Beta offset indicator) - 0 or 2 bits - DMRS sequence initialization (Demodulation reference signal sequence initialization) - 0 or 1 bit DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI can include, for example, the information in Table 12 below. - Identifier for DCI formats - [1] bit- Frequency domain resource assignment -[ ] bits- Time domain resource assignment - X bits- VRB-to-PRB mapping - 1 bit.- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- Downlink assignment index - 2 bits- TPC command for scheduled PUCCH - [2] bits- PUCCH resource indicator (physical uplink control channel, PUCCH) resource indicator- 3 bits- PDSCH-to-HARQ feedback timing indicator (PDSCH-to-HARQ feedback timing indicator)- [3] bits DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include, for example, the information in Table 6 below. - Carrier indicator - 0 or 3 bits- Identifier for DCI formats - [1] bits- Bandwidth part indicator - 0, 1 or 2 bits- Frequency domain resource assignment○ For resource allocation type 0, bits○ For resource allocation type 1, bits- Time domain resource assignment -1, 2, 3, or 4 bits- VRB-to-PRB mapping - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- PRB bundling size indicator - 0 or 1 bit- Rate matching indicator - 0, 1, or 2 bits- ZP CSI-RS trigger (Zero Power Channel State Information Reference Signal Trigger) - 0, 1, or 2 bitsFor transport block 1:- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bitsFor transport block 2:- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- Downlink assignment index - 0 or 2 or 4 bits- TPC command for scheduled PUCCH - 2 bits- PUCCH resource indicator - 3 bits- PDSCH-to-HARQ_feedback timing indicator - 3 bits- Antenna ports - 4, 5 or 6 bits- Transmission configuration indication - 0 or 3 bits- SRS request - 2 bits- CBG transmission information - 0, 2, 4, 6, or 8 bits- CBG flushing out information - 0 or 1 bit- DMRS sequence initialization - 1 bit. Next, we describe frequency domain resource allocation (FDRA) for PDSCH and PUSCH in 5G systems. Figure 7 is a diagram illustrating an example of frequency axis resource allocation of PDSCH or PUSCH in a 5G system. In Fig. 7, three frequency axis resource allocation methods, FDRA type 0 (700), FDRA type 1 (705), and dynamic switch (710), which can be set via upper layer, are illustrated. Referring to Fig. 7, if a terminal is set to use only FDRA type 0 (700) via upper layer signaling, some downlink control information (DCI) for scheduling PDSCH or PUSCH to the terminal is N RBG It contains a bitmap consisting of bits of N. The conditions for this will be explained later. At this time, N RBG It means the number of RBG (resource block group) determined according to the size of the bandwidth portion allocated by the bandwidth portion indicator and the upper layer parameter rbg-Size as shown in Table 14 below, and data is transmitted to the RBG indicated as 1 by the bitmap. Bandwidth Part SizeConfiguration 1Configuration 21-362437-724873-144816145-2751616 The size of a BWP is the number of RBs included in the BWP. More specifically, when a terminal is instructed to allocate type-0 resources, the length of the frequency domain resource assignment (FDRA) field of the DCI received by the terminal is the number of RBGs (N RBG ) is the same as Here, the first RBG is It contains RBs of the dog, and the last RBG is On the other hand, Contains the RBs of the dog, otherwise, contains RBs of the dog. The remaining RBGs contain P RBs, where P is the number of nominal RBGs determined according to Table 14. If the terminal is set to use only FDRA type 1 through upper layer signaling (705), the DCI that allocates PDSCH or PUSCH to the terminal It contains frequency domain resource allocation information (FDRA) consisting of bits of is the number of RBs included in the bandwidth portion. Through this, the base station can set the starting VRB (720) and the length of frequency axis resources (725) allocated sequentially therefrom. If the terminal has been set to the FDRA type-2 resource allocation method through upper layer signaling, the terminal can be instructed by the base station about the FDRA type-2 resource allocation method according to the following method. A terminal can be instructed of a set of M interlace indices from a base station. The interlace index m ∈ {0, 1, ..., M-1} can be composed of common RBs {m, M+m, 2M+m, 3M+m, ...}, and M can be defined as in Table 15. μM01015 RB in interlace m and bandwidth part i and common RB The relationship with can be defined as follows: - - where is the common resource block where bandwidth part starts relative to common resource block 0. μ is subcairre spacing index When the subcarrier spacing is 15 kHz (u=0), RB allocation information for an interlace set with m0 + l indices can be notified from the base station to the terminal. In addition, the resource allocation field can be configured with a resource individuation value (RIV). The resource individuation value is 0≤RIV. <M(M+1) / 2, L=0, 1, ... , L-1 일 때, 시작 인터레이스 m 0 It can be composed of a number of consecutive interlaces L (L≥1), the values ​​of which are as follows. if then RIV = M(L-1)+m 0 else RIV = M(M-L+1) + (M-1-m 0 ) When the resource indicator value is RIV ≥ M(M+1) / 2, the resource indicator value is the starting interlace index m. 0 It consists of values ​​of and l and can be configured as shown in Table 16. RIV-M(M+1) / 2m 0 l00{0, 5}10{0, 1, 5, 6}21{0, 5}31{0, 1, 2, 3, 5, 6, 7, 8}42{0, 5}52{0, 1, 2, 5, 6, 7}63{0, 5}74{0, 5} When the subcarrier spacing is 30 kHz (u=1), RB allocation information can be notified from the base station to the terminal in the form of a bitmap indicating interlaces allocated to the terminal. The size of the bitmap is M, and each bit of the bitmap corresponds to an interlace. The order of the interlace bitmap can be mapped from the MSB to the LSB (least significant bit) from the interlace index 0 to M-1. In addition, for 15 kHz and 30 kHz, the least significant bit (LSB) of the FDRA field can mean a set of consecutive RBs of PUSCH scheduled with DCI format 0_1. The Y bit is a resource indication value (RIV RBset ) can be composed of. , l=0, 1, ... L RBset - RIV in 1 RBset The value is the starting RB set ( ) and the number of consecutive RB sets (L RBset , L RBset ≥1) can be determined. RIV RBset The value can be defined as follows: if then else It refers to the number of RB sets included in the bandwidth portion, and can be determined by the number of guard gaps (or bands) within the carrier set by upper signaling (or preset). Below, a time domain resource allocation method for data channels in a 5G system is described. The base station can set a table (ㅅable) for time domain resource allocation information for downlink data channel (PDSCH) and uplink data channel (PUSCH) to the terminal through higher layer signaling (e.g. RRC signaling). For PDSCH, a table consisting of at most maxNrofDL-Allocations=16 entries can be set, and for PUSCH, a table consisting of at most maxNrofUL-Allocations=16 entries can be set. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to a time interval in slot units between a time point when a PDCCH is received and a time point when a PDSCH scheduled by the received PDCCH is transmitted, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to a time interval in slot units between a time point when a PDCCH is received and a PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information about a position and a length of a start symbol in which a PDSCH or a PUSCH is scheduled within a slot, a mapping type of the PDSCH or PUSCH, etc. For example, information such as Table 17 or Table 18 below may be transmitted from a base station to a terminal. PDSCH-TimeDomainResourceAllocationList information elementPDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocationPDSCH-TimeDomainResourceAllocation ::= SEQUENCE {k0 INTEGER(0..32) OPTIONAL, -- Need S(PDCCH-to-PDSCH timing, in slot units)mappingType ENUMERATED {typeA, typeB},(PDSCH mapping type)startSymbolAndLength INTEGER (0..127)(PDSCH start symbol and length)} PUSCH-TimeDomainResourceAllocation information elementPUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation ::= SEQUENCE {k2 INTEGER(0..32) OPTIONAL, -- Need S(PDCCH-to-PUSCH timing, in slot units)mappingType ENUMERATED {typeA, typeB},(PUSCH mapping type)startSymbolAndLength INTEGER (0..127)(PUSCH start symbol and length)} The base station can notify the terminal of one of the entries in the table for the time domain resource allocation information described above via L1 signaling (e.g., DCI) (e.g., it can be indicated by the 'time domain resource allocation' field in the DCI). The terminal can obtain the time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station. Figure 8 is a diagram illustrating an example of time axis resource allocation of PDSCH in a 5G system. Referring to Figure 8, the base station sets the subcarrier spacing (μ) of the data channel and the control channel using the upper layer. PDSCH , μ PDCCH ), the scheduling offset (K0) value, and the time axis position of the PDSCH resource can be indicated according to the start position (800) and length (805) of an OFDM symbol within a slot that are dynamically indicated through DCI. In a 5G system, a terminal can transmit control information (UCI) to a base station via PUCCH. The control information may include at least one of HARQ-ACK indicating whether demodulation / decoding was successful for a TB (transport block) received by the terminal via PDSCH, SR (scheduling request) requesting resource allocation to a PUSCH base station for uplink data transmission, and channel state information (CSI) which is information for reporting the channel status of the terminal. PUCCH resources can be broadly divided into long PUCCH and short PUCCH depending on the length of the allocated symbol. In a 5G system, long PUCCH has a length of 4 symbols or more within a slot, and short PUCCH has a length of 2 symbols or less within a slot. To explain Long PUCCH in more detail, Long PUCCH can be used for the purpose of improving uplink cell coverage, and therefore can be transmitted in DFT-S-OFDM, which is 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 IFFT. First, PUCCH format 1 is a long PUCCH format based on DFT-S-OFDM that can support control information of up to 2 bits and uses frequency resources of 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 including a demodulation reference signal (DMRS), which is a demodulation reference signal (or reference signal), and OFDM symbols including a UCI that are repeatedly configured. 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,) in the time axis in a sequence corresponding to the length of 1 RB in the frequency axis within one OFDM symbol. ) can be spread and transmitted after performing IFFT. 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, )) can be spread using and transmitted after performing IFFT. 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. w i(m) is the length of the spreading sign (N SF ) is given as in Table 19 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 19 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 silver , This is w i(m) =

[0011] This is it. [Table 19] Next, PUCCH format 3 is a long PUCCH format based on DFT-S-OFDM that can support control information exceeding 2 bits, and the number of RBs used can be set through the upper layer. Control information can be composed of a combination of HARQ-ACK, SR, and CSI or each of them. In PUCCH format 3, DMRS symbol positions are presented in Table 20 below depending on whether frequency hopping occurs within a slot and whether additional DMRS symbols are set. [Table 20] 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 8 symbols as 0. [Table 21] is applied in the same way to the DMRS symbol positions of PUCCH format 4. 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 of 1 RB. Control information can be composed of a combination of HARQ-ACK, SR, and CSI, or each of them. What makes PUCCH format 4 different from PUCCH format 3 is that in the case of PUCCH format 4, PUCCH format 4 of multiple terminals can be multiplexed within one RB. It is possible to multiplex PUCCH format 4 of multiple terminals by applying Pre-DFT OCC (Orthogonal cover code) to control information in front of the IFFT. However, the number of control information symbols that can be transmitted for 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 OCC index to be applied can be set through a higher layer. Next, we will explain short PUCCH. Short PUCCH can be transmitted in both downlink centric slot and uplink centric slot, and generally can be transmitted in the last symbol of the slot, or OFDM symbol in the latter part (e.g., the last OFDM symbol, the penultimate OFDM symbol, or the last 2 OFDM symbols). Of course, Short PUCCH can also be transmitted at any position in the slot. And Short PUCCH can be transmitted using one OFDM symbol or two OFDM symbols. Short PUCCH can be used to reduce delay time compared to long PUCCH in a situation where uplink cell coverage is good, and can be transmitted in CP-OFDM scheme. 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 1RB. Control information can be configured as a combination of HARQ-ACK and SR or each. PUCCH format 0 does not transmit DMRS and is structured to transmit only a sequence 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 set ID set as an upper signal from the base station, and can cyclically shift the generated sequence as a final CS value by adding another CS value depending on whether it is ACK or NACK to the indicated initial CS (cyclic shift) value and map it to 12 subcarriers to transmit it. 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 21 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 generate PUCCH format 0 according to the values ​​defined in the standard to transmit 1-bit HARQ-ACK. 1-bit HARQ-ACKNACKACKFinal CS(Initial CS + 0) mod 12 = Initial CS(Initial CS + 6) mod 12 For example, if HARQ-ACK is 2-bit, 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 22 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 according to ACK or NACK, modulo 12 can be applied to the final CS value because the length of the sequence is 12. 2-bit HARQ-ACKNACK, NACKNACK, ACKACK, ACKACK, NACKFinal CS(Initial CS + 0) mod 12= Initial CS(Initial CS + 3) mod 12(Initial CS + 6) mod 12(Initial CS + 9) mod 12 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, PUCCH format 2 can be fixed to the subcarriers having indices of #1, #4, #7, and #10 for the positions of the subcarriers on which the DMRS is transmitted within one OFDM symbol. The control information can be mapped to the remaining subcarriers except for the subcarriers on which the DMRS is located through a modulation process after channel encoding. In summary, the values ​​and ranges that can be set for each PUCCH format described above can be organized as shown in Table 23 below. In Table 23 below, if a value does not need to be set, it is indicated as NA. [Table 23] Meanwhile, in order to improve uplink coverage, multi-slot repetition may be supported for PUCCH formats 1, 3, and 4, and PUCCH repetition may be set for each PUCCH format. The UE may perform repeated transmission for PUCCH including UCI as many as the number of slots set via upper layer signaling nrofSlots. For PUCCH repeated transmission, PUCCH transmission of each slot is performed using the same number of consecutive symbols, and the number of corresponding consecutive symbols can be set via nrofSymbols in upper layer signaling PUCCH-format1 or PUCCH-format3 or PUCCH-format4. For PUCCH repeated transmission, PUCCH transmission of each slot is performed using the same starting symbol, and the corresponding starting symbol can be set via startingSymbolIndex in upper layer signaling PUCCH-format 1 or PUCCH-format 3 or PUCCH-format 4. For PUCCH repeated transmission, a single PUCCH-spatialRelationInfo can be set for a single PUCCH resource. For PUCCH repetitive 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. In addition, if the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the terminal can start PUCCH transmission from a first PRB index configured through a higher layer signaling, startingPRB, in even slots, and start PUCCH transmission from a second PRB index configured through a higher 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 to which the first PUCCH transmission is instructed to the terminal is 0, and the PUCCH repetitive transmission count value can increase regardless of PUCCH transmission performance in each slot during the configured total number of PUCCH repetitive transmissions. If the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the terminal does not expect frequency hopping within a slot to be configured for PUCCH transmissions. If the terminal is not configured to perform frequency hopping in PUCCH transmissions in different slots, but is configured to perform frequency hopping within a slot, the first and second PRB indices can be applied equally within a slot. If the number of uplink symbols that can be transmitted by PUCCH is less than nrofSymbols set by upper layer signaling, the terminal may not transmit PUCCH. Even if the terminal fails to transmit PUCCH in a slot for some reason during PUCCH repetition transmission, the terminal may increase the number of PUCCH repetition transmissions. In NR Release 17, the number of slots 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 in which the corresponding PUCCH resource is repeatedly transmitted through pucch-RepetitionNrofSlots-r17 and ignores the upper layer signaling nrofSlots. Next, we describe the PUCCH resource configuration of a base station or terminal. The base station may be able to configure PUCCH resources for each BWP through a higher layer for a specific terminal. The PUCCH resource configuration may be as shown in Table 24 below. 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]]}. According to Table 24, one or more PUCCH resource sets may be configured in 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 PUCCH resource sets, the first PUCCH resource set may have its maximum payload value fixed to 2 bits. Accordingly, the value may not be set separately through upper layers, 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 set for the last PUCCH resource set. The upper layer configuration for the PUCCH resource set may be as shown in Table 25 below. PUCCH-ResourceSet ::= SEQUENCE {pucch-ResourceSetId PUCCH-ResourceSetId,resourceList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerSet)) OF PUCCH-ResourceId,maxPayloadSize INTEGER (4..256) OPTIONAL -- Need R} The resourceList parameter in Table 25 may include IDs of PUCCH resources belonging to the PUCCH resource set. If the initial access is made or the PUCCH resource set is not set, a PUCCH resource set consisting of multiple cell-specific PUCCH resources, as shown in Table 26 below, can be used in the initial BWP. The PUCCH resource to be used for the initial access within this PUCCH resource set can be indicated via SIB1. IndexPUCCH formatFirst symbolNumber of symbolsPRB offset Set of initial CS indexes001220{0, 3}101220{0, 4, 8}201223{0, 4, 8}311040{0, 6}411040{0, 3, 6, 9}511042{0, 3, 6, 9}611044{0, 3, 6, 9}714100{0, 6}814100{0, 3, 6, 9}914102{0, 3, 6, 9}1014104{0, 3, 6, 9}1110140{0, 6}1210140{0, 3, 6, 9}1310142{0, 3, 6, 9}1410144{0, 3, 6, 9}151014 {0, 3, 6, 9} The maximum payload of each PUCCH resource included in a PUCCH resource set can be 2 bits for PUCCH format 0 or 1, and can be determined by the symbol length, number of PRBs, and maximum code rate for the remaining formats. 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. Next, PUCCH resource selection for UCI transmission is described. In the case of SR transmission, PUCCH resources for SR corresponding to schedulingRequestID can be set through upper layers as shown in Table 27 below. PUCCH resources can be resources belonging to PUCCH format 0 or PUCCH format 1. 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} The configured PUCCH resource can have a transmission period and offset set through the periodicityAndOffset parameter in Table 27. If the terminal has uplink data to transmit at a time corresponding to the configured period and offset, the corresponding PUCCH resource is transmitted; otherwise, the corresponding PUCCH resource may not be transmitted. For CSI transmission, PUCCH resources to transmit periodic or semi-persistent CSI reports via PUCCH can be set in the pucch-CSI-ResourceList parameter as shown in Table 28 below. The pucch-CSI-ResourceList parameter can include a list of PUCCH resources for each BWP for the cell or CC to transmit the corresponding CSI reports. 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 via reportSlotConfig in Table 28. 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)}},...} In case of HARQ-ACK transmission, the resource set of PUCCH resources to be transmitted may be first selected according to the payload of UCI including the corresponding HARQ-ACK. That is, a PUCCH resource set having a minimum payload not smaller than the UCI payload may be selected. Next, a PUCCH resource in the PUCCH resource set may be selected through a PUCCH resource indicator (PRI) in the DCI that schedules a TB corresponding to the corresponding HARQ-ACK, and the PRI may be a PUCCH resource indicator specified in Table 12 or Table 13. The relationship between the PRI and the PUCCH resource selected from the PUCCH resource set may be as shown in Table 29 below. PUCCH resource indicatorPUCCH resource'000'1 st PUCCH resource provided by pucch-ResourceId obtained from the 1 st value of resourceList'001'2 nd PUCCH resource provided by pucch-ResourceId obtained from the 2 nd value of resourceList'010'3 rd PUCCH resource provided by pucch-ResourceId obtained from the 3 rd value of resourceList'011'4 th PUCCH resource provided by pucch-ResourceId obtained from the 4 th value of resourceList'100'5 th PUCCH resource provided by pucch-ResourceId obtained from the 5 thvalue of resourceList'101'6 th PUCCH resource provided by pucch-ResourceId obtained from the 6 th value of resourceList'110'7 th PUCCH resource provided by pucch-ResourceId obtained from the 7 th value of resourceList'111'8 th PUCCH resource provided by pucch-ResourceId obtained from the 8 th value of resourceList 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 expression 1. [Mathematical Formula 1] r in mathematical expression 1 PUCCH R is the index of the selected PUCCH resource within the PUCCH resource set. PUCCH is the number of PUCCH resources belonging to the PUCCH resource set, Δ PRI is the PRI value, N cce,p is the total number of CCEs of CORESET p to which the receiving DCI belongs, n cce,p Indicates the first CCE index for the received DCI. The time at which the corresponding PUCCH resource is transmitted is K from the TB transmission corresponding to the corresponding HARQ-ACK. 1 After the slot. K 1 The candidate for the value is set by the upper layer, and more specifically, it can be set in the dl-DataToUL-ACK parameter in PUCCH-Config as specified in Table 24. One of these candidates K 1The value 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 12 or Table 13. Meanwhile, K 1 The unit of value can be a slot unit or a subslot unit. Here, a subslot is a unit of length smaller than a slot, and one or more symbols can form one subslot. Next, a case where two or more PUCCH resources are located in one slot is described. A UE can transmit UCI through one or two PUCCH resources in one slot or subslot, and when UCI is transmitted through two PUCCH resources in one slot / subslot, i) each PUCCH resource does not overlap in symbol units, and ii) at least one PUCCH resource can be a short PUCCH. Meanwhile, a UE may not expect to transmit multiple PUCCH resources for HARQ-ACK transmission in one slot. Next, the uplink transmission beam configuration to be used for PUCCH transmission is described. If the terminal does not have a terminal-specific configuration (dedicated PUCCH resource configuration) for PUCCH resource configuration, the PUCCH resource set is provided through upper layer signaling, pucch-ResourceCommon, and the beam configuration for PUCCH transmission follows the beam configuration used in the PUSCH transmission scheduled through the Random Access Response (RAR) UL grant. If a terminal has a dedicated PUCCH resource configuration, beam configuration for PUCCH transmission can be provided through upper layer signaling, pucch-spatialRelationInfoId, included in Table 24. If a terminal is configured with one pucch-spatialRelationInfoId, beam configuration for PUCCH transmission of the terminal can be provided through one pucch-spatialRelationInfoId. If a terminal is configured with multiple pucch-spatialRelationInfoIDs, the terminal can be instructed to activate one of the multiple pucch-spatialRelationInfoIDs through MAC CE (control element). A terminal can be configured with up to eight pucch-spatialRelationInfoIDs through upper layer signaling, and can be instructed to activate only one pucch-spatialRelationInfoID among them. If the terminal is instructed to activate any pucch-spatialRelationInfoID through MAC CE, the terminal transmits HARQ-ACK for the PDSCH on which the MAC CE containing activation information for the pucch-spatialRelationInfoID is transmitted, 3 times from the slot in which the terminal transmits. Starting from the slot that first appears after the slot, activation of pucch-spatialRelationInfoID through MAC CE can be applied. μ is the numerology applied to PUCCH transmission, means the number of slots per subframe in a given numerology. The upper layer configuration for pucch-spatialRelationInfo can be as shown in Table 30 below. PUCCH-SpatialRelationInfo ::= SEQUENCE {pucch-SpatialRelationInfoId PUCCH-SpatialRelationInfoId,servingCellId ServCellIndex OPTIONAL, -- Need SreferenceSignal CHOICE {ssb-Index SSB-Index,csi-RS-Index NZP-CSI-RS-ResourceId,srs PUCCH-SRS},pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id,p0-PUCCH-Id P0-PUCCH-Id,closedLoopIndex ENUMERATED { i0, i1}}PUCCH-SpatialRelationInfoId ::= INTEGER (1..maxNrofSpatialRelationInfos) According to Table 30, there can be one referenceSignal setting within a specific pucch-spatialRelationInfo setting, and the referenceSignal can be an ssb-Index indicating a specific SS / PBCH, a csi-RS-Index indicating a specific CSI-RS, or an srs indicating a specific SRS. If referenceSignal is set to ssb-Index, the terminal can set the beam used when receiving an SS / PBCH corresponding to ssb-Index among SS / PBCHs in the same serving cell as a beam for PUCCH transmission, or if servingCellId is provided, the terminal can set the beam used when receiving an SS / PBCH corresponding to ssb-Index among SS / PBCHs in the cell indicated by servingCellId as a beam for PUCCH transmission. If referenceSignal is set to csi-RS-Index, the terminal can set the beam used when receiving an CSI-RS corresponding to csi-RS-Index among CSI-RSs in the same serving cell as a beam for PUCCH transmission, or if servingCellId is provided, the terminal can set the beam used when receiving an CSI-RS corresponding to csi-RS-Index among CSI-RSs in the cell indicated by servingCellId as a beam for PUCCH transmission. If referenceSignal is set to srs, the terminal may set the transmission beam used when transmitting SRS corresponding to the resource index provided by upper signaling within the same serving cell and / or within the activated uplink BWP to the beam for PUCCH transmission, or, if servingCellID and / or uplinkBWP are provided, set the transmission beam used when transmitting SRS corresponding to the resource index provided by upper signaling within the cell indicated by servingCellID and / or uplinkBWP and / or in the uplink BWP to the beam for PUCCH transmission. There can be one pucch-PathlossReferenceRS-Id setting in a specific pucch-spatialRelationInfo setting. PUCCH-PathlossReferenceRS in Table 31 can be mapped to pucch-PathlossReferenceRS-Id in Table 30, and up to four can be set through pathlossReferenceRSs in upper signaling PUCCH-PowerControl in Table 31. If PUCCH-PathlossReferenceRS is connected to SS / PBCH through upper signaling referenceSignal, ssb-Index can be set, and if connected to CSI-RS, csi-RS-Index can be set. PUCCH-PowerControl ::= SEQUENCE {deltaF-PUCCH-f0 INTEGER (-16..15) OPTIONAL, -- Need RdeltaF-PUCCH-f1 INTEGER (-16..15) OPTIONAL, -- Need RdeltaF-PUCCH-f2 INTEGER (-16..15) OPTIONAL, -- Need RdeltaF-PUCCH-f3 INTEGER (-16..15) OPTIONAL, -- Need RdeltaF-PUCCH-f4 INTEGER (-16..15) OPTIONAL, -- Need Rp0-Set SEQUENCE (SIZE (1..maxNrofPUCCH-P0-PerSet)) OF P0-PUCCH OPTIONAL, -- Need MpathlossReferenceRSs SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRS OPTIONAL, -- Need MtwoPUCCH-PC-AdjustmentStates ENUMERATED {twoStates} OPTIONAL, -- Need S...,[[pathlossReferenceRSs-v1610 SetupRelease { PathlossReferenceRSs-v1610} OPTIONAL -- Need M]]}P0-PUCCH ::= SEQUENCE {p0-PUCCH-Id P0-PUCCH-Id,p0-PUCCH-Value INTEGER (-16..15)}P0-PUCCH-Id ::= INTEGER (1..8)PathlossReferenceRSs-v1610 ::= SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSsDiff-r16)) OF PUCCH-PathlossReferenceRS-r16PUCCH-PathlossReferenceRS ::= SEQUENCE {pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id,referenceSignal CHOICE {ssb-Index SSB-Index,csi-RS-Index NZP-CSI-RS-ResourceId}}PUCCH-PathlossReferenceRS-r16 ::= SEQUENCE {pucch-PathlossReferenceRS-Id-r16 PUCCH-PathlossReferenceRS-Id-v1610,referenceSignal-r16 CHOICE {ssb-Index-r16 SSB-Index,csi-RS-Index-r16 NZP-CSI-RS-ResourceId}}. In Rel-15, if a terminal has multiple pucch-spatialRelationInfoIDs set, it can determine the spatial relationship of the corresponding PUCCH resource by receiving a MAC CE for activating the spatial relationship for each PUCCH resource. However, this method has a disadvantage in that it requires a lot of signaling overhead for activating the spatial relationships of multiple PUCCH resources. Therefore, Rel-16 introduces a new MAC CE for adding a PUCCH resource group and activating the spatial relationship for each PUCCH resource group. Up to four PUCCH resource groups can be set through resourceGroupToAddModList in Table 24, and for each PUCCH resource group, multiple PUCCH resource IDs can be set as a list within one PUCCH resource group as shown in Table 32 below. PUCCH-ResourceGroup-r16 ::= SEQUENCE {pucch-ResourceGroupId-r16 PUCCH-ResourceGroupId-r16,resourcePerGroupList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerGroup-r16)) OF PUCCH-ResourceId}PUCCH-ResourceGroupId-r16 ::= INTEGER (0..maxNrofPUCCH-ResourceGroups-1-r16) In Rel-16, the base station can set each PUCCH resource group to the terminal through the resourceGroupToAddModList in Table 224 and the upper layer settings in Table 32, and configure MAC CE to simultaneously activate the spatial relationship of all PUCCH resources in one PUCCH resource group. FIG. 9 is a diagram illustrating an example of MAC CE for PUCCH resource group-based spatial relationship activation in a 5G system. Referring to FIG. 9, the support cell ID (910) and the bandwidth part ID (920) for which the PUCCH resource to which the corresponding MAC CE is to be applied are set are indicated as Oct 1 (900). The PUCCH Resource ID (931, 941) indicates the ID of the PUCCH resource, and if the indicated PUCCH resource is included in a PUCCH resource group according to resourceGroupToAddModList, other PUCCH resource IDs within the same PUCCH resource group are not indicated to the same MAC CE, and all PUCCH resources within the same PUCCH resource group are activated with the same Spatial Relation Info ID (936, 946). At this time, the Spatial Relation Info ID (936, 946) includes a value corresponding to PUCCH-SpatialRelationInfoId - 1 to be applied to the PUCCH resource group of Table 30. Next, the scheduling method of PUSCH transmission is described. PUSCH transmission can be dynamically scheduled by UL grant in DCI, or can operate by configured grant Type 1 or Type 2. Dynamic scheduling instruction for PUSCH transmission is possible in DCI format 0_0 or 0_1. Configured grant Type 1 PUSCH transmission can be semi-statically scheduled by reception of configuredGrantConfig including rrc-ConfiguredUplinkGrant of Table 33 via higher layer signaling, without reception of UL grant in DCI. Configured grant Type 2 PUSCH transmission can be semi-persistently scheduled by UL grant in DCI after reception of configuredGrantConfig not including rrc-ConfiguredUplinkGrant of Table 33 via higher layer signaling. When PUSCH transmission operates by configured grant, parameters applied to PUSCH transmission are applied by configuredGrantConfig of higher layer signaling as Table 33, except dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, scaling of UCI-OnPUSCH provided by pusch-Config of Table 34. If the terminal is provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of Table 33, the terminal applies tp-pi2BPSK in pusch-Config of Table 34 for PUSCH transmission operated by configured grant. ConfiguredGrantConfig ::= SEQUENCE {frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S,cg-DMRS-Configuration DMRS-UplinkConfig,mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH} OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},rbg-Size ENUMERATED {config2} OPTIONAL, -- Need SpowerControlLoopToUse ENUMERATED {n0, n1},p0-PUSCH-Alpha P0-PUSCH-AlphaSetId,transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need SnrofHARQ-Processes INTEGER(1..16),repK ENUMERATED {n1, n2, n4, n8},repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need Rperiodicity ENUMERATED {sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14,sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12,sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,sym1280x12, sym2560x12},configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need Rrrc-ConfiguredUplinkGrant SEQUENCE {timeDomainOffset INTEGER (0..5119),timeDomainAllocation INTEGER (0..15),frequencyDomainAllocation BIT STRING (SIZE(18)),antennaPort INTEGER (0..31),dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need RprecodingAndNumberOfLayers INTEGER (0..63),srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need RmcsAndTBS INTEGER (0..31),frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need RpathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),...} OPTIONAL, -- Need R...}. 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 the codebook-based transmission method and the non-codebook-based transmission method, respectively, depending on whether the value of txConfig in the upper signaling, pusch-Config in Table 34, is 'codebook' or 'nonCodebook'. As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically configured by 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 at this time, the PUSCH transmission is based on a single antenna port. 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 has not configured txConfig in pusch-Config of Table 34, the UE does not expect to be scheduled with DCI format 0_1. PUSCH-Config ::= SEQUENCE {dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need StxConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need Sdmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mdmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mpusch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need MfrequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need SfrequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1)OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList} OPTIONAL, -- Need Mpusch-AggregationFactor ENUMERATED { n2, n4, n8} OPTIONAL, -- Need Smcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need StransformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need ScodebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}OPTIONAL, -- Cond codebookBasedmaxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBasedrbg-Size ENUMERATED { config2} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need Mtp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S...}. Next, codebook-based PUSCH transmission is described. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically by configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via configured grant, the UE determines a precoder for PUSCH transmission based on SRS Resource Indicator (SRI), Transmission Precoding Matrix Indicator (TPMI), and transmission rank (the number of PUSCH transmission layers). At this time, SRI can be given through field SRS resource indicator in DCI or set through upper signaling srs-ResourceIndicator. When codebook-based PUSCH transmission is performed, the UE is configured with at least one SRS resource, and can be configured with up to two SRS resources. When the UE receives SRI through DCI, the SRS resource indicated by the SRI means an SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the SRI. In addition, TPMI and transmission rank can be given through field precoding information and number of layers in DCI or set through upper signaling precodingAndNumberOfLayers. TPMI is used to indicate a precoder to be applied to PUSCH transmission. If the UE is configured with one SRS resource, TPMI is used to indicate a precoder to be applied in the configured one SRS resource. When a terminal is configured with multiple SRS resources, TPMI is used to indicate the precoder to be applied in the SRS resource indicated through SRI. A 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 a codebook subset based on 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 that the UE reports to the base station. If the UE reports 'partialAndNonCoherent' as the UE capability, the UE does not expect the value of codebookSubset in the upper layer signaling to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the UE reports 'nonCoherent' as the UE capability, the UE does not expect the value of codebookSubset in the upper signaling 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 codebookSubset in the upper signaling to be set to 'partialAndNonCoherent'. A terminal can receive 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 corresponding SRS resource set can be indicated via SRI. If multiple SRS resources are set in an 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. 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. At this time, 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 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. Next, non-codebook based PUSCH transmission is described. Non-codebook based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically by configured grant. If at least one SRS resource is configured in an SRS resource set in which the value of usage in upper signaling SRS-ResourceSet is set to 'nonCodebook', the UE can be scheduled for non-codebook based PUSCH transmission via DCI format 0_1. 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 calculation of 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. 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. At this time, if the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, it indicates the existence of the connected NZP CSI-RS when the value of the field SRS request in DCI format 0_1 ​​or 1_1 is not '00'. At this time, the DCI must not indicate cross carrier or cross BWP scheduling. In addition, if the value of SRS request indicates the existence of the NZP CSI-RS, the NZP CSI-RS is located in the slot in which the PDCCH including the SRS request field is transmitted. At this time, the TCI states set for the scheduled subcarriers are not set to QCL-TypeD. If a periodic or semi-persistent SRS resource set is configured, the associated NZP CSI-RS can be indicated via the associatedCSI-RS in the upper layer signaling SRS-ResourceSet. For non-codebook based transmission, the terminal does not expect that the upper layer signaling spatialRelationInfo for SRS resource and the associatedCSI-RS in the upper layer signaling SRS-ResourceSet are configured together. When multiple SRS resources are set, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. At this time, the SRI can be indicated through the field SRS resource indicator in the DCI or set through the upper signaling srs-ResourceIndicator. Similar to the codebook-based PUSCH transmission described above, when the UE is provided with an SRI through the DCI, the SRS resource indicated by the SRI means an SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including 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 that the UE reports to the base station. At this time, the SRS resources that the UE simultaneously transmits occupy the same RB. The UE sets 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. 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 a result measured upon reception of the NZP-CSI-RS. When the terminal transmits one or more SRS resources within the SRS resource set of which usage is 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. At this time, in non-codebook based PUSCH transmission, SRI represents an index that can express a combination of one or more SRS resources, and the SRI is included in the DCI. At this time, 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 for each layer. Next, the PUSCH preparation procedure time is described. When the base station schedules the UE to transmit the PUSCH using DCI format 0_0, 0_1, or 0_2, the UE may need a PUSCH preparation procedure time to transmit the PUSCH by applying the transmission method (transmission precoding method of SRS resource, number of transmission layers, spatial domain transmission filter) indicated through the DCI. NR defines the PUSCH preparation procedure time considering this. The PUSCH preparation procedure time of the UE can follow the following mathematical expression 2. [Mathematical formula 2] T proc,2 = max(( N2 + d 2,1 + d 2 )( 2048 + 144 ) κ2 -μ T c + T ext + T switch , d 2,2 ) T as described in mathematical formula 2 proc,2 In , each variable can have the following meanings. - N 2 : The number of symbols determined by the terminal processing capability (UE processing capability) 1 or 2 and the numerology μ according to the capability of the terminal. If the terminal processing capability is reported as 1 according to the capability report of the terminal, it may have the value of Table 35, and if the terminal processing capability is reported as 2 and it is set through upper layer signaling that the terminal processing capability 2 can be used, it may have the value of Table 36. μPUSCH preparation time N 2 [symbols]010112223336 μPUSCH preparation time N 2 [symbols]0515.5211 for frequency range 1 - d 2,1 : The number of symbols set to 0 if all REs of the first OFDM symbol of PUSCH transmission are configured to consist of DM-RS only, otherwise set to 1. - κ: 64 - μ: μ DL or μ UL Medium, T proc,2 This follows the larger value μ DL refers to the numerology of the downlink in which the PDCCH containing the DCI scheduling the PUSCH is transmitted, and μ UL It refers to the numerology of the uplink in which PUSCH is transmitted. - T c : 1 / (Δf max ·N f), Δf max = 480·10 3 Hz, N f = has 4096. - d 2,2 : If the DCI scheduling the PUSCH indicates BWP switching, it follows the BWP switching time, otherwise it has 0. - d 2 : When OFDM symbols of PUCCH and PUSCH with high priority index and PUCCH with low priority index overlap in time, d of PUSCH with high priority index 2 The value is used. Otherwise d 2 is 0. - T ext : When the terminal uses the shared spectrum channel access method, the terminal uses T ext can be calculated and applied to the PUSCH preparation process time. Otherwise, T ext is assumed to be 0. - T switch : T when the uplink switching interval is triggered switch is assumed to be the switching interval time. Otherwise, it is assumed to be 0. When the base station and terminal consider the time domain resource mapping information of the PUSCH scheduled through DCI and the influence of the timing advance between uplink and downlink, T is calculated from the last symbol of the PDCCH including the DCI that scheduled the PUSCH. proc,2 If the first symbol of PUSCH starts before the first uplink symbol that CP starts, it is determined that the PUSCH preparation time is not sufficient. If not, the base station and the terminal determine that the PUSCH preparation time is sufficient. The terminal transmits the PUSCH only when the PUSCH preparation time is sufficient, and can ignore the DCI that schedules the PUSCH when the PUSCH preparation time is not sufficient. The following describes in detail the repetitive transmission of uplink data channels in 5G systems. The 5G system supports two types of repetitive transmission methods for uplink data channels: PUSCH repetitive transmission type A and PUSCH repetitive transmission type B. A terminal can be set to either PUSCH repetitive transmission type A or B through upper layer signaling. Below we describe PUSCH repetition type A. As described above, the symbol length and the position of the start symbol of the uplink data channel are determined by the time domain resource allocation method within one slot, and the base station can notify the terminal of the number of repeated transmissions through higher layer signaling (e.g. RRC signaling) or L1 signaling (e.g. DCI). The terminal can repeatedly transmit an uplink data channel having the same length and start symbol as the uplink data channel set based on the number of repeated transmissions received from the base station in consecutive slots. At this time, if at least one symbol among the slots set by the base station to the terminal as downlink or the symbols of the uplink data channel set by the terminal is set as downlink, the terminal omits the uplink data channel transmission, but counts the number of repeated transmissions of the uplink data channel. In other words, the number of repeated transmissions of the uplink data channel is included, but the uplink data channel may not be transmitted. On the other hand, a terminal supporting Rel-17 uplink data repetition transmission determines a slot in which uplink data repetition transmission is possible as an available slot, and can count the number of transmissions when uplink data channels are repeated in a slot determined as an available slot. If uplink data channel repetition transmission is omitted in a slot determined as an available slot, transmission can be postponed and repeated transmission can be performed through a slot in which transmission is possible. In order to determine the available slot, if at least one symbol set to TDRA (time domain resource allocation) for PUSCH in a slot for PUSCH transmission overlaps with a symbol for a purpose other than uplink transmission (e.g., downlink), the slot is determined as an unavailable slot (e.g., a slot that is not an available slot and is determined to be unavailable for PUSCH transmission). In addition, the available slot may be considered as an uplink resource for determining resources for PUSCH transmission and transport block size (TBS) in repeated PUSCH transmission and multi-slot PUSCH transmission consisting of one TB (or transport block on multiple slots, TBoMS). Below, PUSCH repetition type B is described. As described above, the start symbol and length of the uplink data channel are determined by the time domain resource allocation method within one slot, and the base station can notify the terminal of the number of repetitions of the repetition transmission through upper signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI). First, the nominal repetition of the uplink data channel is determined based on the start symbol and length of the established uplink data channel as follows. The slot where the nth nominal repetition starts is The symbol given by and starting in that slot is is given by . The slot where the nth nominal repetition ends is The symbol given by and ending in that slot is is given by , where n=0, ..., numberofrepetitions-1, S represents the start symbol of the established uplink data channel, and L represents the symbol length of the established uplink data channel. K s Indicates the slot where PUSCH transmission starts. Indicates the number of symbols per slot. A terminal may determine a specific OFDM symbol as an invalid symbol for the following cases for PUSCH repetition transmission type B. o Symbols set to downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated may be determined as invalid symbols for PUSCH repetition transmission type B. o In unpaired spectrum (TDD spectrum), symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon, which is a higher layer signaling, for SSB reception may be determined as invalid symbols for PUSCH repetition transmission type B. o In unpaired spectrum (TDD spectrum), symbols indicated through pdcch-ConfigSIB1 in the MIB for transmitting CORESET associated with Type0-PDCCH CSS set may be determined as invalid symbols for PUSCH repetition transmission Type B. o In unpaired spectrum (TDD spectrum), if the upper layer signaling numberOfInvalidSymbolsForDL-UL-Switching is set, symbols set to downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for numberOfInvalidSymbolsForDL-UL-Switching symbols can be determined as invalid symbols. - Additionally, an invalid symbol can be set in a higher layer parameter (e.g., InvalidSymbolPattern). The higher layer parameter (e.g., InvalidSymbolPattern) provides a symbol level bitmap spanning one slot or two slots, where an invalid symbol can be set. In the bitmap, 1 indicates an invalid symbol. Additionally, a periodicity and a pattern of the bitmap can be set via a higher layer parameter (e.g., periodicityAndPattern). If the higher layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter indicates 1, the terminal applies the invalid symbol pattern, and if the parameter indicates 0, the terminal does not apply the invalid symbol pattern. If a higher layer parameter (e.g. InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter is not set, the terminal applies an invalid symbol pattern. After the invalid symbols are determined, for each nominal repetition, the terminal can consider symbols other than the invalid symbol as valid symbols. If each nominal repetition includes one or more valid symbols, the nominal repetition may include one or more actual repetitions. Here, each actual repetition includes a contiguous set of valid symbols that can be used for PUSCH repetitive transmission type B in one slot. If the OFDM symbol length of the nominal repetition is not 1, the terminal can ignore the transmission for the corresponding actual repetition if the length of the actual repetition becomes 1. FIG. 10 is a diagram illustrating an example of PUSCH repetition transmission type B in a 5G system. The terminal may set the start symbol S of the uplink data channel to 0, the length L of the uplink data channel to 14, and the number of repeated transmissions to 16. In this case, the nominal repetition is indicated in 16 consecutive slots (1001). After that, the terminal may determine that the symbol set as the downlink symbol in each nominal repetition (01) is an invalid symbol. In addition, the terminal determines that the symbols set to 1 in the invalid symbol pattern (1002) are invalid symbols. If valid symbols that are not invalid symbols in each nominal repetition consist of one or more consecutive symbols in one slot, they are set as actual repetition and transmitted (1003). Below, we specifically describe frequency hopping of the uplink data channel (PUSCH) in a 5G system. In the 5G system, two methods are supported for each PUSCH repetition transmission type as a frequency hopping method of the uplink data channel. First, PUSCH repetition transmission type A supports intra-slot frequency hopping and inter-slot frequency hopping, and PUSCH repetition transmission type B supports inter-repetition frequency hopping and inter-slot frequency hopping. The intra-slot frequency hopping method supported in PUSCH repetitive transmission type A is a method in which a terminal changes the allocated resources of the frequency domain by a set frequency offset and transmits them in two hops within one slot. In intra-slot frequency hopping, the start RB of each hop can be expressed by mathematical expression 3. [Mathematical Formula 3] In Equation 3, i=0 and i=1 represent the first and second hops, respectively, and RB start Indicates the starting RB in the UL BWP and is calculated from the frequency resource allocation method. RB offset The upper layer parameter indicates the frequency offset between two hops. The number of symbols in the first hop is can be expressed as , and the number of symbols in the second hop is can be expressed as is the length of PUSCH transmission within one slot, expressed as the number of OFDM symbols. Next, the inter-slot frequency hopping method supported by PUSCH repetitive transmission types A and B is a method in which the terminal changes the allocated resources of the frequency domain by the set frequency offset for each slot and transmits them. In inter-slot frequency hopping, The starting RB during a slot can be expressed by mathematical expression 4. [Mathematical Formula 4] In mathematical expression 4, is the current slot number, RB in multi-slot PUSCH transmission. start Indicates the starting RB in the UL BWP and is calculated from the frequency resource allocation method. RB offset Indicates the frequency offset between two hops via upper layer parameters. Next, the inter-repetition frequency hopping method supported by PUSCH repetitive transmission type B is to transmit the allocated resources in the frequency domain for one or more actual repetitions within each nominal repetition by shifting them by a set frequency offset. RB, which is the index of the starting RB in the frequency domain for one or more actual repetitions within the nth nominal repetition. start (n) can follow the following mathematical formula 5. [Mathematical Formula 5] In Equation 5, n is the index of the nominal repetition, RB offset Indicates the RB offset between two hops via upper layer parameters. Below, a method for determining the transmission power of an uplink data channel in a 5G system is specifically described. In a 5G system, the transmission power of an uplink data channel can be determined using the following mathematical expression 6. [Mathematical Formula 6] In mathematical expression 6, j represents the grant type of PUSCH. Specifically, j = 0 represents a PUSCH grant for random access response, j = 1 represents a configured grant, and j ∈ {2,3,...J-1} represents a dynamic grant. means the maximum output power set to the terminal for carrier f of supporting cell c for PUSCH transmission occasion i. is set as a higher layer parameter and can be determined through upper layer settings and SRI (in case of dynamic grant PUSCH). is a parameter composed of the sum of . refers to the bandwidth for resource allocation expressed as the number of resource blocks for PUSCH transmission occasion i. refers to a value determined according to the type of information transmitted through MCS and PUSCH (e.g., whether UL-SCH is included or CSI is included, etc.). refers to a value that can be determined (in case of dynamic grant PUSCH) through upper layer settings and SRI (SRS resource Indicator) as a value to compensate for path loss. The reference signal index is q d It means the downlink path loss estimate estimated by the terminal through the reference signal, and the reference signal index q. dThe UE can decide this either through higher layer configuration and SRI (in case of dynamic grant PUSCH or configured grant PUSCH based on ConfiguredGrantConfig that does not include higher layer configuration rrc-ConfiguredUplinkGrant (type 2 configured grant PUSCH)) or through higher layer configuration. can be supported as a closed loop power adjustment value in an accumulation manner and an absolute manner. If the upper layer parameter tpc-Accumulation is not set in the terminal, the closed loop power adjustment value can be determined in an accumulation manner. In this case, is the previous PUSCH transmission occasion ii 0 Closed loop power adjustment values ​​for PUSCH transmission occasion ii 0 To send K PUSCH (ii 0 )-1 to transmit PUSCH transmission occasion i from symbol K PUSCH (i) Between symbols, the sum of TPC command values ​​for closed loop index l received via DCI. is determined. If the upper layer parameter tpc-Accumulation is set on the terminal, is the TPC command value for closed loop index l received via DCI. is determined. The closed loop index l can be set to 0 or 1 if the upper layer parameter twoPUSCH-PC-AdjustmentStates is set in the terminal, and its value can be determined through the upper layer configuration and SRI (in case of dynamic grant PUSCH). TPC command field and TPC value in DCI according to the accumulation method and the absolute method. The mapping relationship can be defined as shown in Table 37 below. TPC command fieldAccumulated [dB]Absolute [dB]0-1-410-1211334 Hereinafter, a power headroom report (PHR) in a 5G system is described. The power headroom report means that the UE measures and transmits to the base station the difference between the nominal UE maximum transmit power and the estimated power for uplink transmission (i.e., represents the available transmit power of the UE). The power headroom report can be used to support power aware packet scheduling. The estimated power for uplink transmission can be the estimated power for UL-SCH (PUSCH) transmission per activated serving cell, the estimated power for UL-SCH and PUCCH transmission in SpCell of another MAC entity (e.g., E-UTRA MAC entity in EN-DC, NE-DC, and NGEN-DC cases in 3GPP standard), the estimated power for SRS transmission per activated serving cell, etc. The UE can trigger the power headroom report if any one of the following trigger events is met. - [Trigger Event 1] When the upper layer parameter phr-ProhibitTimer expires and the MAC entity has uplink resources for new transmission, the path loss for at least one activated supporting cell changes by more than the upper layer parameter phr-Tx-PowerFactorChange dB since the most recent PHR transmission, wherein the activated downlink bandwidth part for the at least one activated supporting cell may not be a dormant bandwidth part. In this case, the path loss change for one cell is determined as the difference between the currently measured path loss with respect to the current path loss reference and the path loss measured at that point in time with respect to the path loss reference at the most recent PHR transmission. - [Trigger Event 2] The upper layer parameter phr-PeriodicTimer expires. - [Trigger Event 3] The power headroom reporting function is set or reset by a higher layer, rather than being set or reset to not support power headroom reporting. - [Trigger Event 4] A SCell is activated for a MAC entity having an uplink for which firstActiveDownlinkBWP-Id is not set to dormant bandwidth part. The firstActiveDownlinkBWP-Id means the identifier of the DL BWP to be activated when performing RRC (re)configuration (if configured for the SpCell) or the identifier of the DL BWP to be used when activating the SCell (if configured for the SCell). - [Trigger Event 5] PSCell is added (i.e. PSCell is newly added or changed). - [Trigger Event 6] The upper layer parameter phr-PrhoibitTimer has expired, and for any activated supporting cells of any MAC entity with uplink configured while the MAC entity has uplink resources for new transmission, both of the following conditions a) and b) are met: a) There are uplink resources allocated for transmission or PUCCH is transmitted to the cell. b) When the MAC entity has uplink resources for transmission or transmits PUCCH to that cell, the required power backoff due to power management for that cell is greater than the upper layer parameter phr-Tx-PowerFactorChange dB since the most recent PHR transmission. - [Trigger Event 7] Change the activated bandwidth part of the SCell for any MAC entity with configured uplink from the dormant bandwidth part to the non-dormant downlink bandwidth part. - [Trigger Event 8] If the higher layer parameter mpe-Reporting-FR2 is set in the UE to indicate whether to report MPE P-MPR (Maximum allowed UE output power reduction) to satisfy the maximum permissible exposure (MPE) in FR2, and mpe-ProhibitTimer is not running, and the measured P-MPR applied to satisfy the FR2 MPE requirement for at least one activated FR2 capable cell since the most recent power headroom report is greater than or equal to the higher layer parameter mpe-Threshold, in case the power headroom report is referred to as 'MPE P-MPR report'. Power headroom reporting may be triggered based on the above trigger events, and the terminal may decide whether to report power headroom based on the following additional conditions. - [Additional conditions due to temporary required power backoff] When the required power backoff is reduced temporarily (i.e., up to tens of milliseconds) due to power management, the MAC entity shall not trigger a power headroom report. If the required power backoff is reduced temporarily and power headroom reporting is triggered by other trigger events, this results in a P CMAX,f,c / PH value should not be temporarily reduced. That is, PHR should not be triggered due to temporary power backoff. For example, if PHR is triggered by another PHR trigger event (such as expiration of periodic timer), PH reflecting temporary power reduction due to demand power backoff is not reported, and a condition is added so that PH excluding the effect due to demand power backoff is reported. - [Power headroom reporting conditions according to terminal implementation] If a HARQ process is set to cg-RetransmissionTimer and a power headroom report has already been included in the MAC PDU for transmission by the corresponding HARQ process but transmission through the lower layer has not yet been performed, the method of processing the corresponding power headroom report is determined according to the terminal implementation. If one or more of the above trigger events occur and a power headroom report is triggered, and an uplink transmission resource allocated through downlink control information can accommodate a MAC entity and a subheader therefor for power headroom reporting, the terminal performs a power headroom report through the corresponding uplink resource. In this case, the corresponding uplink resource means a resource for an uplink transmission scheduled by the first downlink control information format (first DCI format) that schedules the initial transmission of TB after the power headroom trigger or the first uplink grant. That is, after the power headroom trigger occurs, the terminal can perform a power headroom report through an uplink transmission scheduled by the first downlink control information format or the first uplink grant among the uplink resources that can accommodate a MAC entity for power headroom and a subheader therefor or the first DCI format. Alternatively, after a power headroom trigger occurs, the terminal can perform power headroom reporting via a configured grant PUSCH transmission capable of accommodating a MAC entity for power headroom and its subheader. When reporting power headroom for a specific cell, a terminal can select one of two types of power headroom information to calculate and report. The first type is actual PHR, which is power headroom information calculated based on the transmit power of an uplink signal (e.g., PUSCH) actually transmitted. The second type is virtual PHR (or reference format), which is power headroom information calculated based on transmit power parameters set in a higher layer, but without an uplink signal (e.g., PUSCH) actually transmitted. After the power headroom report is triggered, the terminal can calculate the actual PHR based on the downlink control information received up to the time including the PDCCH monitoring interval in which the first DCI format for scheduling the PUSCH to transmit the MAC CE including the power headroom report is received as described above and the upper layer information for periodic / semi-persistent SRS transmission and configured grant transmission. If the terminal receives the downlink control information or decides to transmit the periodic / semi-persistent SRS or configured grant transmission after the PDCCH monitoring interval in which the first DCI format is received, the terminal can calculate the virtual PHR for the corresponding cell. Alternatively, after the power headroom report is triggered, the terminal can calculate the actual PHR based on the first uplink symbol of the configured grant PUSCH capable of transmitting the corresponding power headroom information, T' corresponding to the PUSCH preparation process time described above based on the first uplink symbol of the configured grant PUSCH. proc,2 = T proc,2 Based on the downlink control information received up to the previous point in time and the upper layer information for periodic / semi-persistent SRS transmission and configured grant transmission, the actual PHR can be calculated. If T' is based on the first uplink symbol of the configured grant PUSCH, proc,2 If the terminal receives downlink control information after the previous point in time, or decides to transmit periodic / semi-persistent SRS or configured grant, the terminal can calculate virtual PHR for the corresponding cell. If the terminal calculates the actual PHR based on the actual PUSCH transmission, the power headroom reporting information for the supporting cell c, carrier f, bandwidth part b, and PUSCH transmission time point i can be expressed as in the following mathematical expression 7. [Mathematical formula 7] As another example, if the terminal calculates the virtual PHR based on the transmission power parameter set in the upper layer, the power headroom reporting information for the support cell c, carrier f, bandwidth part b, and PUSCH transmission time point i can be expressed as in the following mathematical expression 8. [Mathematical formula 8] According to the above mathematical expression 7, power headroom information can be calculated by using the difference in transmission power for PUSCH transmission occasion i at the maximum output power. According to mathematical expression 8, parameters related to MPR (Maximum Power Reduction) (e.g., MPR, A-MPR (Additional MPR), P-MPR (Power Management MPR), etc.) and ΔT c The maximum output power when assuming 0 is and default transmit power parameters (e.g., , p0 and alpha of P0-PUSCH-AlphaSetId=0, corresponding to pusch-PathlossReferenceRS-Id=0. And the power headroom information can be calculated by using the difference of the reference PUSCH transmission power using the closed loop power adjustment value with the closed loop index l = 0. For the description of each variable in the above mathematical expressions 7 and 8, refer to the variable description for the above mathematical expression 6. The above A-MPR is an MPR that satisfies an additional emission requirement indicated by a base station by upper layer signaling (for example, by combining additionalSpectrumEmission indicated by RRC signaling and NR freq. band (Table 6.2.3.1-1A in TS 38.101-1), a network signaling label is identified, and the A-MPR value according to it is defined as Table 6.2.3.1-1 in TS 38.101-1). The P-MPR is a maximum allowed UE output power reduction for serving cell c, and its purpose is an MPR that can satisfy applicable electromagnetic energy absorption requirements. The A-MPR and P-MPR can refer to 3GPP standard TS 38.101-1 section 6.2. If MR-DC or UL-CA is not supported, the base station sets the upper layer parameter 'multiplePHR' to 'false' for the corresponding terminal. This means that the terminal supports power headroom reporting for PCell with MAC CE having a single entry as in 1110 of Fig. 11. FIG. 11 is a diagram illustrating an example of a MAC CE format for a PHR with a single entry according to a 5G system. Each field of FIG. 11 can be defined as in Table 38 below. Meanwhile, this is only an example and the present disclosure is not limited thereto. - P: P, consisting of 1 bit, is set to 0 if mpe-Reporting-FR2 is set and the serving cell operates in FR2 and the applied P-MPR according to TS38.133 is less than P-MPR_00, otherwise it is set to 1. If mpe-Reporting-FR2 is not set or the serving cell operates in FR1, P indicates whether power back-off is applied for transmission power control. If power back-off is not applied due to power management and the corresponding Pcmax,c field has a different value, the corresponding P field is set to 1;- P CMAX,f,c : This field indicates the maximum transmit power value used to calculate the power headroom when reporting the power headroom. With 6 bits of information, one of a total of 64 nominal UE transmit power levels can be selected; - MPE: When mpe-Reporting-FR2 is configured, the serving cell operates in FR2, and the P field is set to 1, the MPE field indicates the power backoff value applied to satisfy the MPE (maximum permissible exposure) requirement. It is a 2-bit field and indicates one of a total of four measured P-MPR value steps. If mpe-Reporting-FR2 is not set, or if the serving cell operates in FR1, or if the P field is set to 0, it can exist as a reserved (reversed) bit like R; - R: As a reserved bit, it is set to 0; PH: This field indicates the power headroom level. It consists of 6 bits and can select one value out of a total of 64 power headroom levels. When a terminal supports MR-DC (multi-RAT dual connectivity) or UL-CA (uplink carrier aggregation), the base station sets the upper layer parameter 'multiplePHR' to 'true' for the corresponding terminal to perform power headroom reporting for each supported cell. This means that the terminal supports power headroom reporting for multiple supported cells with a MAC CE having multiple entries, such as the first format (1200) illustrated in FIG. 12a or the second format (1202) illustrated in FIG. 12b. FIG. 12a is a diagram illustrating an example of a MAC CE format for a PHR having multiple entries according to a 5G system, and FIG. 12b is a diagram illustrating another example of a MAC CE format for a PHR having multiple entries according to a 5G system. The first format (1200) of FIG. 12a is a PHR MAC CE format that can be used when a plurality of serving cells are set and the largest index value among the serving cells is less than 8. The second format (1202) of FIG. 12b is a PHR MAC CE format that can be used when a plurality of serving cells are set and the largest index value among the serving cells is greater than or equal to 8. Unlike the PHR MAC CE format illustrated in FIG. 11, the first format (1200) illustrated in FIG. 12a or the second format (1202) illustrated in FIG. 12b may have a variable size depending on the set or number of serving cells set. The information may include a second type of PH information for a SpCell (special cell) of another MAC entity (e.g., LTE) and a first type of PH information for a PCell. If the largest value of the index among the serving cells is less than 8, the field indicating the serving cell information may consist of one octet. If the largest value of the index among the serving cells is greater than or equal to 8, the field indicating the serving cell information may consist of four octets. In the PHR MAC CE, power headroom information may be included in the order of the serving cell index. The MAC entity may transmit the PHR MAC CE including the power headroom information through the transmittable PUSCH when the power headroom report is triggered. At this time, whether the power headroom information is calculated based on actual transmission (i.e., actual PHR) or calculated based on the transmission power parameter set in the upper layer (i.e., virtual PHR) is determined at a specific time point (a time point including the PDCCH monitoring period in which the first DCI format is detected or T' in the first symbol of the first PUSCH, as described above. proc,2It can be determined based on the upper signal and downlink control information received up to the previous point in time. Meanwhile, the fields of the PHR MAC CE format illustrated in FIGS. 12a and 12b may have the same meaning (definition) as most of the fields of the PHR MAC CE format illustrated in FIG. 11, and C i and V can have the same meanings as described in Table 39 below. - C i : This field indicates the presence of a power headroom area for the supporting cell with ServCellIndex i. If power headroom is reported for supporting cell i, the corresponding C i Set the region to 1. If power headroom for support cell i is not reported, the corresponding C i Set the field to 0; V: This field indicates whether the power headroom value is calculated based on actual transmission or reference format. For the first type power headroom information, if the PUSCH is actually transmitted, V is set to 0, and if the reference format for the PUSCH is used, it is set to 1. For the second type PH information, if the PUCCH is actually transmitted, V is set to 0, and if the reference format for the PUCCH is used, it is set to 1. For the third type PH information, if the SRS is actually transmitted, V is set to 0, and if the reference format for the SRS is used, it is set to 1. In addition, if the V value is 0 for the first type, the second type, and the third type power headroom information, P for this cmax,f,c and MPE field exists, and if the V value is 1, P for it cmax,f,c and MPE fields may be omitted. Next, a method for estimating an uplink channel using a sounding reference signal (SRS) transmission of a terminal is described. A base station can set at least one SRS configuration for each uplink BWP to transmit configuration information for SRS transmission to a terminal, and can also set at least one SRS resource set for each SRS configuration. For example, a base station and a terminal can exchange the following upper signaling information to transmit information about an SRS resource set. - srs-ResourceSetId: SRS resource set index - srs-ResourceIdList: A set of SRS resource indices referenced in the SRS resource set. - resourceType: This is the time axis transmission setting of the SRS resource referenced in the SRS resource set, and can be set to one of 'periodic', 'semi-persistent', and 'aperiodic'. If set to 'periodic' or 'semi-persistent', associated CSI-RS information can be provided depending on the usage of the SRS resource set. If set to 'aperiodic', an aperiodic SRS resource trigger list and slot offset information can be provided, and associated CSI-RS information can be provided depending on the usage of the SRS resource set. - usage: This is a setting for the usage of the SRS resource referenced in the SRS resource set, and can be set to one of 'beamManagement', 'codebook', 'nonCodebook', and 'antennaSwitching'. - alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter settings for adjusting the transmission power of SRS resources referenced in the SRS resource set. The terminal can understand that the SRS resource included in the set of SRS resource indices referenced in the SRS resource set follows the information set in the SRS resource set. In addition, the base station and the terminal can transmit and receive upper layer signaling information to convey individual configuration information for the SRS resource. For example, the individual configuration information for the SRS resource can include time-frequency axis mapping information within a slot of the SRS resource, which can include information about frequency hopping within a slot or between slots of the SRS resource. In addition, the individual configuration information for the SRS resource can include a time axis transmission configuration of the SRS resource, which can be set to one of 'periodic', 'semi-persistent', and 'aperiodic'. This can be restricted to have the same time axis transmission configuration as an SRS resource set including the SRS resource. If the time axis transmission configuration of the SRS resource is set to 'periodic' or 'semi-persistent', an SRS resource transmission period and slot offset (e.g., periodicityAndOffset) can be additionally included in the time axis transmission configuration. The base station can activate, deactivate, or trigger SRS transmission to the terminal through higher layer signaling including RRC signaling or MAC CE signaling, or L1 signaling (e.g., DCI). For example, the base station can activate or deactivate periodic SRS transmission to the terminal through higher layer signaling. The base station can instruct the terminal to activate an SRS resource set in which resourceType is set to periodic through higher layer signaling, and the terminal can transmit an SRS resource referenced in the activated SRS resource set. Time-frequency domain resource mapping within a slot of the transmitted SRS resource follows resource mapping information set in the SRS resource, and slot mapping including a transmission period and a slot offset follows periodicityAndOffset set in the SRS resource. In addition, a spatial domain transmission filter applied to the transmitted SRS resource can refer to spatial relation info set in the SRS resource, or can refer to associated CSI-RS information set in an SRS resource set including the SRS resource. A terminal can transmit SRS resources within an activated uplink BWP for activated periodic SRS resources through upper layer signaling. For example, the base station can activate or deactivate semi-persistent SRS transmission to the terminal through upper layer signaling. The base station can instruct to activate an SRS resource set through MAC CE signaling, and the terminal can transmit an SRS resource referenced in the activated SRS resource set. The SRS resource set activated through MAC CE signaling can be limited to an SRS resource set of which resourceType is set to semi-persistent. Time-frequency domain resource mapping within a slot of the transmitted SRS resource follows resource mapping information set in the SRS resource, and slot mapping including a transmission period and a slot offset follows periodicityAndOffset set in the SRS resource. In addition, the spatial domain transmission filter applied to the transmitted SRS resource can refer to spatial relation info set in the SRS resource, or can refer to associated CSI-RS information set in an SRS resource set including the SRS resource. If spatial relation info is set in the SRS resource, the spatial domain transmission filter can be determined by referring to the configuration information for spatial relation info delivered through MAC CE signaling that activates semi-persistent SRS transmission without following it. The terminal can transmit the SRS resource within the activated uplink BWP for the semi-persistent SRS resource activated through upper layer signaling. For example, a base station can trigger aperiodic SRS transmission to a terminal through DCI. The base station can indicate one of aperiodic SRS resource triggers (aperiodicSRS-ResourceTrigger) through an SRS request field of the DCI. The terminal can understand that an SRS resource set including an aperiodic SRS resource trigger indicated through DCI in an aperiodic SRS resource trigger list among configuration information of an SRS resource set is triggered. The terminal can transmit an SRS resource referenced in the triggered SRS resource set. Time-frequency axis resource mapping within a slot of the transmitted SRS resource follows resource mapping information configured in the SRS resource. In addition, the slot mapping of the transmitted SRS resource can be determined through a slot offset between a PDCCH including DCI and the SRS resource, and this can refer to value(s) included in a slot offset set configured in the SRS resource set. Specifically, the slot offset between the PDCCH including DCI and the SRS resource can apply a value indicated in the time domain resource assignment field of the DCI among the offset value(s) included in the slot offset set in the SRS resource set. In addition, the spatial domain transmission filter applied to the transmitted SRS resource can refer to the spatial relation info set in the SRS resource, or can refer to the associated CSI-RS information set in the SRS resource set including the SRS resource. The UE can transmit the SRS resource within the activated uplink BWP for the aperiodic SRS resource triggered through the DCI.When a base station triggers an aperiodic SRS transmission to a terminal through DCI, a minimum time interval may be required between a PDCCH including the DCI triggering the aperiodic SRS transmission and the SRS to be transmitted, in order for the terminal to transmit the SRS by applying configuration information for the SRS resource. The time interval for the SRS transmission of the terminal can be defined as the number of symbols between the last symbol of the PDCCH including the DCI triggering the aperiodic SRS transmission and the first symbol to which the SRS resource to be transmitted is mapped first among the SRS resource(s) to be transmitted. The minimum time interval can be determined with reference to the PUSCH preparation procedure time required for the terminal to prepare for the PUSCH transmission. In addition, the minimum time interval can have different values ​​depending on the usage of the SRS resource set including the SRS resource to be transmitted. For example, the minimum time interval can be determined as N2 symbols defined in consideration of the terminal processing ability according to the capability of the terminal with reference to the PUSCH preparation procedure time of the terminal. In addition, considering the usage of the SRS resource set including the SRS resource being transmitted, if the usage of the SRS resource set is set to 'codebook' or 'antennaSwitching', the minimum time interval can be set to N2 symbols, and if the usage of the SRS resource set is set to 'nonCodebook' or 'beamManagement', the minimum time interval can be set to N2+14 symbols.The terminal may transmit an aperiodic SRS if the time interval for aperiodic SRS transmission is greater than or equal to the minimum time interval, and may ignore the DCI that triggers the aperiodic SRS if the time interval for aperiodic SRS transmission is less than the minimum time interval. SRS-Resource ::= SEQUENCE {srs-ResourceId SRS-ResourceId,nrofSRS-Ports ENUMERATED {port1, ports2, ports4},ptrs-PortIndex ENUMERATED {n0, n1} OPTIONAL, -- Need RtransmissionComb CHOICE {n2 SEQUENCE {combOffset-n2 INTEGER (0..1),cyclicShift-n2 INTEGER (0..7)},n4 SEQUENCE {combOffset-n4 INTEGER (0..3),cyclicShift-n4 INTEGER (0..11)}},resourceMapping SEQUENCE {startPosition INTEGER (0..5),nrofSymbols ENUMERATED {n1, n2, n4},repetitionFactor ENUMERATED {n1, n2, n4}},freqDomainPosition INTEGER (0..67),freqDomainShift INTEGER (0..268),freqHopping SEQUENCE {c-SRS INTEGER (0..63),b-SRS INTEGER (0..3),b-hop INTEGER (0..3)},groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping},resourceType CHOICE {aperiodic SEQUENCE {...},semi-persistent SEQUENCE {periodicityAndOffset-sp SRS-PeriodicityAndOffset,...},periodic SEQUENCE {periodicityAndOffset-p SRS-PeriodicityAndOffset,...}},sequenceId INTEGER (0..1023),spatialRelationInfo SRS-SpatialRelationInfo OPTIONAL, -- Need R...} The spatialRelationInfo setting information of Table 40 above refers to one reference signal and applies the beam information of the reference signal to the beam used for the SRS transmission. For example, the setting of spatialRelationInfo may include information such as Table 41 below. SRS-SpatialRelationInfo ::= SEQUENCE {servingCellId ServCellIndex OPTIONAL, -- Need SreferenceSignal CHOICE {ssb-Index SSB-Index,csi-RS-Index NZP-CSI-RS-ResourceId,srs SEQUENCE {resourceId SRS-ResourceId,uplinkBWP BWP-Id}}} Referring to the above spatialRelationInfo setting, the index of the reference signal to be referenced in order to use the beam information of a specific reference signal, that is, the SS / PBCH block index, the CSI-RS index, or the SRS index can be set. The upper signaling referenceSignal is setting information indicating which beam information of a reference signal is to be referenced for the corresponding SRS transmission, and ssb-Index means the index of the SS / PBCH block, csi-RS-Index means the index of the CSI-RS, and srs means the index of the SRS, respectively. If the value of the upper signaling referenceSignal is set to 'ssb-Index', the terminal can apply the reception beam used when receiving the SS / PBCH block corresponding to ssb-Index as the transmission beam of the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'csi-RS-Index', the terminal can apply the reception beam used when receiving the CSI-RS corresponding to csi-RS-Index as the transmission beam of the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'srs', the terminal can apply the transmission beam used when transmitting the SRS corresponding to the srs as the transmission beam for the corresponding SRS transmission. In LTE and NR, a terminal can perform a procedure to report the capabilities supported by the terminal to the serving base station while connected to the serving base station. In the explanation below, this is referred to as a UE capability report. A base station can transmit a UE capability enquiry message requesting a capability report to a terminal in a connected state. 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 enquiry message, multiple UE capabilities for each RAT type can be requested through one RRC message container transmitted by the base station, or the base station can include the UE capability inquiry message including the UE capability request for each RAT type multiple times and transmit it to the terminal. That is, the UE capability inquiry can be repeated multiple times in one message, and the terminal can configure a corresponding UE capability information message and report it multiple times. In a 5G 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 above terminal capability inquiry message is typically transmitted initially after the terminal is connected to the base station, but it can be requested under any conditions when the base station is needed. In the above step, the terminal that receives the UE capability report request from the base station configures the terminal capability according to 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. 1. If the UE receives a list of LTE and / or NR bands from the base station as a UE capability request, 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 as FreqBandList. In addition, the priority of the bands is given in the order listed in FreqBandList. 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 candidate list of the configured BCs. This behavior can only occur when the LTE base station (eNB) requests the "eutra" capability. 3. After that, the terminal removes fallback BCs from the candidate list of BCs configured in the above step. Here, fallback BC means a BC that can be obtained by removing at least one band corresponding to SCell from any BC, and can be omitted because the BC before removing the band corresponding to at least one SCell can already cover the fallback BC. This step is also applied to MR-DC, i.e., to LTE bands. The BCs remaining after this step are the final "candidate BC list." 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 configures the supportedBandCombinationList in a set order. That is, the terminal configures BCs and UE capabilities to report in the order of the preset rat-Type (nr -> eutra-nr -> eutra). In addition, it configures featureSetCombination for the configured supportedBandCombinationList, and configures a list of "candidate feature set combinations" from the candidate BC list from which the list for the fallback BC (which includes capabilities of the same or lower level) is removed. The "candidate feature set combination" above includes feature set combinations for both NR and EUTRA-NR BCs, and can be obtained from feature set combinations of the UE-NR-Capabilities and UE-MRDC-Capabilities containers. 5. Also, if the requested rat Type is eutra-nr and influential, featureSetCombinations are included in both containers: UE-MRDC-Capabilities and UE-NR-Capabilities. However, the feature set of NR is included only in UE-NR-Capabilities. After the terminal capability is configured, the terminal transmits a terminal capability information message containing the terminal capability to the base station. Based on the terminal capability received from the terminal, the base station then performs appropriate scheduling and transmission / reception management for the terminal. According to one embodiment of the present disclosure, non-coherent joint transmission (NC-JT) may be used for a terminal to receive a PDSCH from multiple transmission and reception points (TRPs). Unlike conventional wireless communication systems, 5G wireless communication systems can support not only services requiring high transmission rates, but also services with very short transmission delays and services requiring high connection density. In a wireless communication network including multiple cells, TRPs, or beams, coordinated transmission between each cell, TRP, or / and beam can increase the strength of a signal received by a terminal or efficiently perform interference control between each cell, TRP, or / and beam, thereby satisfying various service requirements. Joint transmission (JT) is a representative transmission technology for the aforementioned cooperative communication, which increases the intensity or processing rate of a signal received by a terminal by transmitting a signal to a single terminal through a number of different cells, TRPs, or / and beams. At this time, the channel between each cell, TRP or / and beam and the terminal may have significantly different characteristics, and in particular, in the case of non-coherent joint transmission that supports non-coherent precoding between each cell, TRP or / and beam, individual precoding, MCS, resource allocation, TCI indication, etc. may be required depending on the channel characteristics of each link between each cell, TRP or / and beam and the terminal. The above-described NC-JT transmission can be applied to at least one channel among the downlink data channel (PDSCH), the downlink control channel (PDCCH), the uplink data channel (PUSCH), and the uplink control channel (PUCCH). When transmitting PDSCH, transmission information such as precoding, MCS, resource allocation, and TCI are indicated by DL DCI, and for NC-JT transmission, the transmission information must be independently indicated for each cell, TRP, or / and beam. This is a major factor that increases the payload required for DL ​​DCI transmission, and this may adversely affect the reception performance of the PDCCH transmitting the DCI. Therefore, in order to support JT of PDSCH, it is necessary to carefully design a tradeoff between the amount of DCI information and the reception performance of control information. FIG. 13 is a diagram illustrating an example of antenna port configuration and resource allocation for transmitting a PDSCH using cooperative communication in a wireless communication system according to an embodiment of the present disclosure. In Fig. 13, examples for PDSCH transmission are explained for each joint transmission technique, and examples for allocating radio resources for each TRP are illustrated. An example (1300) for coherent joint transmission supporting coherent precoding between each cell, TRP or / and beam is illustrated. In the case of C-JT, TRP A (1305) and TRP B (1310) transmit a single data (PDSCH) to the terminal (1315), and joint precoding can be performed on multiple TRPs. This may mean that DMRS is transmitted through the same DMRS ports for TRP A (1305) and TRP B (1310) to transmit the same PDSCH. For example, TRP A (1305) and TRP B (1310) may each transmit DRMS ​​to the terminal through DMRS port A and DMRS B. In this case, the terminal may receive one DCI information for receiving one PDSCH demodulated based on the DMRS transmitted through DMRS port A and DMRS B. An example (1320) of non-coherent joint transmission supporting non-coherent precoding between each cell, TRP or / and beam for PDSCH transmission is illustrated. In the case of NC-JT, PDSCH is transmitted to the terminal (1335) for each cell, TRP or / and beam, and individual precoding can be applied to each PDSCH. Each cell, TRP or / and beam can transmit different PDSCHs or different PDSCH layers to the terminal, thereby improving throughput compared to single cell, TRP or / and beam transmission. In addition, each cell, TRP or / and beam can repeatedly transmit the same PDSCH to the terminal, thereby improving reliability compared to single cell, TRP or / and beam transmission. For convenience of explanation, a cell, TRP or / and beam are collectively referred to as TRP hereinafter. At this time, various radio resource allocations can be considered, such as when the frequency and time resources used by multiple TRPs for PDSCH transmission are all the same (1340), when the frequency and time resources used by multiple TRPs do not overlap at all (1345), and when some of the frequency and time resources used by multiple TRPs overlap (1350). To support NC-JT, DCIs of various shapes, structures, and relationships can be considered to simultaneously allocate multiple PDSCHs to a single terminal. FIG. 14 is a diagram illustrating an example of a configuration of downlink control information (DCI) for NC-JT in which each TRP transmits a different PDSCH or a different PDSCH layer to a terminal in a wireless communication system according to an embodiment of the present disclosure. Case #1 (1400) is an example in which, in addition to a serving TRP (TRP#0) used for single PDSCH transmission, (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)), and control information for PDSCHs transmitted from the (N-1) additional TRPs is transmitted independently from control information for PDSCHs transmitted from the serving TRP. That is, a UE can obtain control information for PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through independent DCIs (DCI#0 to DCI#(N-1)). Formats between the independent DCIs may be the same or different, and payloads between the DCIs may also be the same or different. In the aforementioned case #1, each PDSCH control or allocation freedom can be fully guaranteed, but if each DCI is transmitted in different TRPs, coverage differences for each DCI may occur, which may deteriorate reception performance. Case #2 (1405) shows an example in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for single PDSCH transmission, control information (DCI) for PDSCHs of the (N-1) additional TRPs is transmitted respectively, and each of these DCIs is dependent on the control information for the PDSCH transmitted from the serving TRP. For example, in the case of DCI#0, which is control information for a PDSCH transmitted from a serving TRP (TRP#0), it includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, but in the case of shortened DCI (hereinafter, sDCI) (sDCI#0 to sDCI#(N-2)), which is control information for PDSCHs transmitted from cooperating TRPs (TRP#1 to TRP#(N-1)), it may include only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. Therefore, in the case of sDCI, which transmits control information for PDSCHs transmitted from cooperating TRPs, since the payload is smaller than that of normal DCI (nDCI), which transmits PDSCH-related control information transmitted from a serving TRP, it is possible to include reserved bits compared to nDCI. In the case #2 described above, the degree of freedom in controlling or allocating each PDSCH may be limited depending on the content of the information elements included in sDCI, but since the reception performance of sDCI is superior to that of nDCI, the probability of a difference in coverage by DCI may be reduced. Case #3 (1410) illustrates an example in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than a serving TRP (TRP#0) used for single PDSCH transmission, one control information for the PDSCHs of the (N-1) additional TRPs is transmitted, and this DCI is dependent on the control information for the PDSCH transmitted from the serving TRP. For example, in the case of DCI#0, which is control information for a PDSCH transmitted from a serving TRP (TRP#0), it includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, and in the case of control information for PDSCHs transmitted from cooperating TRPs (TRP#1 to TRP#(N-1)), it is possible to collect only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 into one 'secondary' DCI (sDCI) and transmit them. For example, the sDCI may include at least one of HARQ-related information such as frequency domain resource assignment, time domain resource assignment, and MCS of cooperating TRPs. In addition, for information not included in sDCI, such as BWP indicator or carrier indicator, the DCI (DCI#0, normal DCI, nDCI) of serving TRP can be followed. Case #3 (1410) may limit the degree of freedom in controlling or allocating each PDSCH depending on the content of information elements included in sDCI, but it is possible to control the reception performance of sDCI and reduce the complexity of blind decoding of DCI of a terminal compared to case #1 (1400) or case #2 (1405). Case #4(1415) is an example of transmitting control information for PDSCHs transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in the same DCI (Long DCI) as the control information for PDSCHs transmitted from the serving TRP, in a situation where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for single PDSCH transmission. That is, the UE can obtain control information for PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In case #4(1415), the complexity of DCI blind decoding of the UE may not increase, but the degree of freedom in PDSCH control or allocation may be low, such as because the number of cooperative TRPs is limited due to the long DCI payload limitation. In the following description and examples, sDCI may refer to various auxiliary DCIs, such as shortened DCI, secondary DCI, or normal DCI (DCI format 1_0 to 1_1 described above) including PDSCH control information transmitted in a cooperative TRP, and unless otherwise specified, the description is similarly applicable to the various auxiliary DCIs. In the following description and examples, the cases of case #1 (1400), case #2 (1405), and case #3 (1410), where more than one DCI (PDCCH) is used to support NC-JT, may be distinguished as multiple PDCCH-based NC-JT, and the case of case #4 (1415), where a single DCI (PDCCH) is used to support NC-JT, may be distinguished as single PDCCH-based NC-JT. In PDSCH transmission based on multiple PDCCH, a CORESET in which the DCI of the serving TRP (TRP#0) is scheduled and a CORESET in which the DCIs of the cooperating TRPs (TRP#1 to TRP#(N-1)) are scheduled may be distinguished. As a method for distinguishing the CORESETs, there may be a method of distinguishing through an upper layer indicator for each CORESET, a method of distinguishing through beam setting for each CORESET, etc. In addition, in single PDCCH based NC-JT, instead of a single DCI scheduling multiple PDSCHs, a single PDSCH having multiple layers is scheduled, and the multiple layers described above can be transmitted from multiple TRPs. In this case, the connection relationship between a layer and a TRP transmitting the corresponding layer can be indicated through a TCI indication for the layer. In the embodiments of the present disclosure, “cooperative TRP” may be replaced with various terms such as “cooperative panel” or “cooperative beam” in actual application. In the embodiments of the present disclosure, “when NC-JT is applied” may be interpreted in various ways depending on the situation, such as “when a terminal receives one or more PDSCHs simultaneously in one BWP,” “when a terminal receives PDSCHs based on two or more TCI indications simultaneously in one BWP,” or “when a PDSCH received by the terminal is associated with one or more DMRS port groups,” but is used as a single expression for convenience of explanation. In the present invention, the wireless protocol structure for NC-JT can be used in various ways depending on the TRP deployment scenario. For example, if there is no or small backhaul delay between cooperative TRPs, a method using a structure based on MAC layer multiplexing (CA-like method) is possible. On the other hand, if the backhaul delay between cooperative TRPs is large enough to be ignored (for example, if more than 2 ms is required for information exchange such as CSI, scheduling, and HARQ-ACK between cooperative TRPs), a method (DC-like method) is possible to secure delay-robust characteristics by using an independent structure for each TRP starting from the RLC layer. A terminal supporting C-JT or / and NC-JT can receive C-JT or / and NC-JT related parameters or setting values ​​from an upper layer configuration, and set the RRC parameters of the terminal based on the parameters. For the upper layer configuration, the terminal can utilize a UE capability parameter, for example, tci-StatePDSCH. Here, the UE capability parameter, for example, tci-StatePDSCH, can define TCI states for the purpose of PDSCH transmission, and the number of TCI states can be set to 4, 8, 16, 32, 64, and 128 in FR1, and to 64 and 128 in FR2, and among the set number, up to 8 states that can be indicated with 3 bits of the TCI field of DCI via a MAC CE message can be set. The maximum value 128 means the value indicated by maxNumberConfiguredTCIstatesPerCC in the tci-StatePDSCH parameter included in the capability signaling of the terminal. In this way, a series of configuration processes from upper layer configuration to MAC CE configuration can be applied to a beamforming instruction or beamforming change command for at least one PDSCH in one TRP. As one embodiment of the present disclosure, a multi-DCI based multi-TRP transmission method is described. The multi-DCI based multi-TRP transmission method may be a method of setting a downlink control channel for NC-JT transmission based on a multi-PDCCH. In NC-JT based on multiple PDCCHs, when transmitting DCI for the PDSCH schedule of each TRP, a CORESET or search space can be distinguished for each TRP. The CORESET or search space for each TRP can be set as in at least one of the following cases. * Setting of upper layer index for each CORESET: The CORESET setting information set as an upper layer may include an index value, and the TRP transmitting the PDCCH in the corresponding CORESET may be distinguished by the set index value for each CORESET. That is, in a set of CORESETs having the same upper layer index value, it may be considered that the same TRP transmits the PDCCH, or it may be considered that a PDCCH scheduling the PDSCH of the same TRP is transmitted. The above-described CORESET-specific index may be named as CORESETPoolIndex, and for CORESETs having the same CORESETPoolIndex value, it may be considered that the PDCCH is transmitted from the same TRP. In the case of a CORESET for which the CORESETPoolIndex value is not set, it may be considered that the default value of CORESETPoolIndex is set, and the above-described default value may be 0. ** In the present disclosure, if the number of types of CORESETPoolIndex of each of the multiple CORESETs included in the upper layer signaling PDCCH-Config exceeds 1, i.e., if each CORESET has a different CORESETPoolIndex, the terminal can consider that the base station can use the multi-DCI based multi-TRP transmission method. ** Differently, in the present disclosure, if each of the multiple CORESETs included in the upper layer signaling PDCCH-Config has only one type of CORESETPoolIndex, i.e., if all CORESETs have the same CORESETPoolIndex of 0 or 1, the terminal can assume that the base station transmits using single-TRP without using the multi-DCI based multi-TRP transmission method. * Multiple PDCCH-Config settings: Multiple PDCCH-Configs are set within one BWP, and each PDCCH-Config can include PDCCH settings for each TRP. That is, a list of CORESETs for each TRP and / or a list of search spaces for each TRP can be configured in one PDCCH-Config, and one or more CORESETs and one or more search spaces included in one PDCCH-Config can be considered as corresponding to a specific TRP. * CORESET beam / beam group configuration: The TRP corresponding to the CORESET can be distinguished through the beam or beam group set for each CORESET. For example, if the same TCI state is set for multiple CORESETs, the CORESETs can be considered to be transmitted through the same TRP, or the PDCCH that schedules the PDSCH of the same TRP in the CORESET can be considered to be transmitted. * Search space beam / beam group configuration: A beam or beam group is configured for each search space, through which TRPs for each search space can be distinguished. For example, if the same beam / beam group or TCI state is set for multiple search spaces, it can be considered that the same TRP transmits PDCCH in the corresponding search space, or it can be considered that a PDCCH that schedules the PDSCH of the same TRP is transmitted in the corresponding search space. By dividing the CORESET or search space by TRP as described above, PDSCH and HARQ-ACK information classification for each TRP is possible, and this enables independent HARQ-ACK codebook generation and independent PUCCH resource use for each TRP. The above configuration can be independent per cell or per BWP. For example, a PCell may have two different CORESETPoolIndex values ​​set, while a specific SCell may not have any CORESETPoolIndex value set. In this case, it can be considered that NC-JT transmission is configured on the PCell, while NC-JT transmission is not configured on the SCell that does not have any CORESETPoolIndex value set. The PDSCH TCI state activation / deactivation MAC-CE applicable to the multi-DCI based multi-TRP transmission method can follow the above Fig. 15. Fig. 15 is a diagram illustrating an example of a PDSCH TCI state indication method applicable to the multi-DCI based multi-TRP transmission method. In Fig. 15, a list of TCI states for a PDSCH can be indicated through a list of upper layers such as RRC (1500). The list of TCI states can be indicated, for example, as tci-StatesToAddModList and / or tci-StatesToReleaseList in the PDSCH-Config IE for each BWP. Next, some of the list of TCI states can be activated through MAC-CE (1520). The maximum number of TCI states to be activated can be determined according to the capability reported by the terminal. Among these, one TCI state can be indicated using DCI. 1550 illustrates an example of a MAC-CE structure for PDSCH TCI state activation / deactivation. If the UE does not set CORESETPoolIndex for each of all CORESETs in the upper layer signaling PDCCH-Config, the UE may ignore the CORESET Pool ID field (1555) in the corresponding MAC-CE (1550). If the UE can support the multi-DCI based multi-TRP transmission method, i.e., if each CORESET in the upper layer signaling PDCCH-Config of the UE has a different CORESETPoolIndex, the UE may activate the TCI state in the DCI included in the PDCCH transmitted in the CORESETs having the same CORESETPoolIndex value as the CORESET Pool ID field (1555) value in the corresponding MAC-CE (1550). For example, if the value of the CORESET Pool ID field (1555) in the corresponding MAC-CE (1550) is 0, the TCI state in the DCI included in the PDCCH transmitted from CORESETs having CORESETPoolIndex of 0 may follow the activation information of the corresponding MAC-CE. When a terminal is configured to use a multi-DCI based multi-TRP transmission method from a base station, that is, when each of multiple CORESETs included in PDCCH-Config, which is an upper layer signaling, has more than one type of CORESETPoolIndex or when each CORESET has a different CORESETPoolIndex, the terminal can know that the following restrictions exist for PDSCHs scheduled from PDCCHs within each CORESET having two different CORESETPoolIndexes. 1) If the PDSCHs indicated from the PDCCHs within each CORESET having two different CORESETPoolIndexes completely or partially overlap, the TCI states indicated from each PDCCH can be applied to different CDM groups, respectively. That is, two or more TCI states may not be applied to one CDM group. 2) The terminal can expect that the actual number of front-loaded DMRS symbols, the actual number of additional DMRS symbols, the positions of actual DMRS symbols, and the DMRS type of each PDSCH will not be different when the PDSCHs indicated from the PDCCHs within each CORESET having two different CORESETPoolIndexes overlap completely or partially. 3) The terminal can expect that the bandwidth portion indicated by the PDCCH within each CORESET having two different CORESETPoolIndexes will be the same and that the subcarrier spacing will also be the same. 4) The terminal can expect that each PDCCH will fully contain information about the PDSCH scheduled from the PDCCH within each CORESET having two different CORESETPoolIndexes. As one embodiment of the present disclosure, a single-DCI based multi-TRP transmission method is described. The single-DCI based multi-TRP transmission method can set a downlink control channel for NC-JT transmission based on a single-PDCCH. In a single DCI based multi-TRP transmission method, PDSCHs transmitted by multiple TRPs can be scheduled with one DCI. At this time, the number of TCI states can be used as a method for indicating the number of TRPs transmitting the corresponding PDSCH. That is, if the number of TCI states indicated in the DCI for scheduling the PDSCH is 2, it can be considered as a single PDCCH based NC-JT transmission, and if the number of TCI states is 1, it can be considered as a single-TRP transmission. The TCI states indicated by the above DCI can correspond to one or two TCI states activated by MAC-CE. When the TCI states of the DCI correspond to two TCI states activated by MAC-CE, a correspondence relationship between the TCI codepoint indicated by the DCI and the TCI states activated by MAC-CE is established, and it can be the case when there are two TCI states activated by MAC-CE corresponding to the above TCI codepoint. As another example, if at least one codepoint among all codepoints in the TCI state field in the DCI indicates two TCI states, the UE can consider that the BS can transmit based on the single-DCI based multi-TRP method. In this case, at least one codepoint indicating two TCI states in the TCI state field can be activated via the Enhanced PDSCH TCI state activation / deactivation MAC-CE. Fig. 16 is a diagram illustrating an example of an Enhanced PDSCH TCI state activation / deactivation MAC-CE structure. The meaning of each field in the MAC CE and the values ​​that can be set for each field are as shown in Table 42 below. - Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits. If the indicated Serving Cell is configured as part of a simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 as specified in TS 38.331 [5], this MAC CE applies to all the Serving Cells configured in the set simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2, respectively;- BWP ID: This field indicates a DL BWP for which the MAC CE applies as the codepoint of the DCI bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits;- C i : This field indicates whether the octet containing TCI state ID i,2 is present. If this field is set to "1", the octet containing TCI state ID i,2 is present. If this field is set to "0", the octet containing TCI state ID i,2 is not present;- TCI state ID i,j: This field indicates the TCI state identified by TCI-StateId as specified in TS 38.331 [5], where i is the index of the codepoint of the DCI Transmission configuration indication field as specified in TS 38.212 [9] and TCI state ID i,j denotes the j-th TCI state indicated for the i-th codepoint in the DCI Transmission Configuration Indication field. The TCI codepoint to which the TCI States are mapped is determined by its ordinal position among all the TCI codepoints with sets of TCI state ID i,j fields, i.e. the first TCI codepoint with TCI state ID 0,1 and TCI state ID 0,2 shall be mapped to the codepoint value 0, the second TCI codepoint with TCI state ID 1,1 and TCI state ID 1,2 shall be mapped to the codepoint value 1 and so on. The TCI state ID i,2is optional based on the indication of the Ci field. The maximum number of activated TCI codepoint is 8 and the maximum number of TCI states mapped to a TCI codepoint is 2.R: Reserved bit, set to "0". In Fig. 16, if C 0 If the value of field (1605) is 1, the corresponding MAC-CE has a TCI state ID 0,1 In addition to field (1610) TCI state ID 0,2 It may include a field (1615), which is a TCI state ID for the 0th codepoint of the TCI state field included in the DCI. 0,1 and TCI state ID 0,2 This means that C is activated, and if the base station instructs the terminal to the corresponding codepoint, the terminal can be instructed to two TCI states. If C 0 If the value of field (1605) is 0, the corresponding MAC-CE is the TCI state ID. 0,2 It cannot contain field (1615), which is the TCI state ID for the 0th codepoint of the TCI state field contained within the DCI. 0,1 This means that one TCI state corresponding to is activated. The above configuration can be independent per cell or per BWP. For example, a PCell can have at most two activated TCI states corresponding to one TCI codepoint, while a specific SCell can have at most one activated TCI state corresponding to one TCI codepoint. In this case, it can be considered that the PCell is configured for NC-JT transmission, while the above-mentioned SCell is not configured for NC-JT transmission. Next, a method for distinguishing single-DCI based multi-TRP PDSCH repetition transmission techniques is described. A terminal may be instructed to use different single-DCI based multi-TRP PDSCH repetition transmission techniques (e.g., TDM, FDM, SDM) depending on a value indicated by a DCI field from a base station and a higher layer signaling configuration. Table 43 below shows a method for distinguishing between single or multiple TRP based techniques indicated to a terminal depending on a value of a specific DCI field and a higher layer signaling configuration. Number of combinations TCI states Number of CDM groups repetitionNumber Setting and instruction conditions repetitionScheme Setting Transmission scheme indicated to the relevant terminal 11≥1Condition 2Not configuredSingle-TRP21≥1Condition 2ConfiguredSingle-TRP31≥1Condition 3ConfiguredSingle-TRP411Condition 1Configured or not configuredSingle-TRP TDM scheme B522Condition 2Not configuredMulti-TRP SDM622Condition 3Not configuredMulti-TRP SDM722Condition 3ConfiguredMulti-TRP SDM821Condition 3ConfiguredMulti-TRP FDM scheme A / FDM scheme B / TDM scheme A921Condition 1Not configuredMulti-TRP TDM scheme B In Table 43 above, each column can be explained as follows. - Number of TCI states (2 columns): This refers to the number of TCI states indicated by the TCI state field in the DCI, and can be 1 or 2. - Number of CDM groups (column 3): This indicates the number of different CDM groups of DMRS ports indicated by the Antenna port field in the DCI. It can be 1, 2, or 3. - repetitionNumber setting and indication conditions (column 4): There can be three conditions depending on whether repetitionNumber is set for all TDRA entries that can be indicated by the Time Domain Resource Allocation field in DCI and whether the actually indicated TDRA entry has repetitionNumber setting. * Condition 1: At least one of all TDRA entries that can be indicated by the Time Domain Resource Allocation field contains a setting for repetitionNumber, and the TDRA entry indicated by the Time Domain Resource Allocation field in the DCI contains a setting for repetitionNumber greater than 1. * Condition 2: At least one of all TDRA entries that can be indicated by the Time Domain Resource Allocation field contains a setting for repetitionNumber, and no TDRA entry indicated by the Time Domain Resource Allocation field in the DCI contains a setting for repetitionNumber. * Condition 3: If all TDRA entries that can be indicated by the Time Domain Resource Allocation field do not contain a setting for repetitionNumber. - Relating to repetitionScheme setting (column 5): This refers to whether repetitionScheme, which is an upper layer signaling, is set. The upper layer signaling repetitionScheme can be set to one of 'tdmSchemeA', 'fdmSchemeA', and 'fdmSchemeB'. - Transmission technique indicated to the terminal (column 6): refers to single or multiple TRP techniques indicated according to each combination (column 1) expressed in Table 43 above. * Single-TRP: Refers to a single TRP-based PDSCH transmission. If the UE has set pdsch-AggegationFactor in the upper layer signaling PDSCH-config, the UE can be scheduled for the configured number of repeated single TRP-based PDSCH transmissions. Otherwise, the UE can be scheduled for a single TRP-based PDSCH single transmission. * Single-TRP TDM scheme B: This refers to PDSCH repetitive transmission based on time resource division between single TRP-based slots. According to Condition 1 related to repetitionNumber described above, the UE repetitively transmits PDSCH in the time dimension as many times as the number of slots of repetitionNumber that is greater than 1 set in the TDRA entry indicated by the Time Domain Resource Allocation field. At this time, for each slot of the repetitionNumber number, the start symbol and symbol length of the PDSCH indicated by the TDRA entry are applied equally, and the same TCI state is applied to each PDSCH repetitive transmission. This technique is similar to the slot aggregation method in that it performs PDSCH repetitive transmission between slots on time resources, but it differs from slot aggregation in that it can dynamically determine whether to indicate repetitive transmission based on the Time Domain Resource Allocation field in the DCI. * Multi-TRP SDM: This refers to a multi-TRP based spatial resource division PDSCH transmission method. This is a method of receiving by dividing layers from each TRP, and although it is not a repetitive transmission method, it can increase the reliability of PDSCH transmission in that it can transmit by lowering the coding rate by increasing the number of layers. The terminal can receive PDSCH by applying two TCI states indicated through the TCI state field in the DCI for each of the two CDM groups indicated by the base station. * Multi-TRP FDM scheme A: This refers to a multi-TRP based frequency resource division PDSCH transmission method. It has one PDSCH transmission position (occasion), so it is not repetitive transmission like multi-TRP SDM, but it is a technique that can transmit with high reliability by increasing the frequency resource amount and lowering the coding rate. Multi-TRP FDM scheme A can apply two TCI states indicated through the TCI state field in the DCI to non-overlapping frequency resources. If the PRB bundling size is determined as wideband, the terminal applies the first TCI state to the first ceil (N / 2) RBs when the number of RBs indicated by the Frequency Domain Resource Allocation field is N, and applies the second TCI state to the remaining floor (N / 2) RBs. Here, ceil (.) and floor (.) are operators indicating round up and down to the first decimal place. If the PRB bundling size is determined as 2 or 4, even-numbered PRGs receive by applying the first TCI state, and odd-numbered PRGs receive by applying the second TCI state. * Multi-TRP FDM scheme B: This refers to a multi-TRP based frequency resource division PDSCH repeated transmission method, which has two PDSCH transmission positions (occasions) and can repeatedly transmit PDSCH at each position. Multi-TRP FDM scheme B, like A, can apply two TCI states indicated through the TCI state field in the DCI to non-overlapping frequency resources. If the PRB bundling size is determined as wideband, the UE applies the first TCI state to the first ceil (N / 2) RBs when the number of RBs indicated by the Frequency Domain Resource Allocation field is N, and applies the second TCI state to the remaining floor (N / 2) RBs and receives them. Here, ceil (.) and floor (.) are operators indicating round up and down for the first decimal place. If the PRB bundling size is determined as 2 or 4, even-numbered PRGs receive by applying the first TCI state, and odd-numbered PRGs receive by applying the second TCI state. * Multi-TRP TDM scheme A: This refers to a PDSCH repeated transmission method within a multi-TRP based time resource division slot. A terminal has two PDSCH transmission positions (occasions) within one slot, and the first reception position can be determined based on the starting symbol and symbol length of the PDSCH indicated through the Time Domain Resource Allocation field in the DCI. The starting symbol of the second reception position of the PDSCH can be a position that applies a symbol offset equal to StartingSymbolOffsetK, which is an upper layer signaling, from the last symbol of the first transmission position, and the transmission position can be determined equal to the indicated symbol length. If the upper layer signaling StartingSymbolOffsetK is not set, the symbol offset can be regarded as 0. * Multi-TRP TDM scheme B: This refers to a PDSCH repetition transmission scheme between multi-TRP based time resource division slots. The UE has one PDSCH transmission position (occasion) in one slot, and can receive repeated transmission based on the start symbol and symbol length of the same PDSCH for the number of slots equal to the repetitionNumber indicated through the Time Domain Resource Allocation field in the DCI. If the repetitionNumber is 2, the UE can receive the PDSCH repeated transmissions of the first and second slots by applying the first and second TCI states, respectively. If the repetitionNumber is greater than 2, the UE can use different TCI state application methods depending on how the upper layer signaling tciMapping is set. If tciMapping is set to cyclicMapping, the first and second TCI states are applied to the first and second PDSCH transmission positions, respectively, and the same TCI state application method is applied to the remaining PDSCH transmission positions. If tciMapping is set to sequentialMapping, the first TCI state is applied to the first and second PDSCH transmission positions, the second TCI state is applied to the third and fourth PDSCH transmission positions, and the same TCI state application method is applied to the remaining PDSCH transmission positions. Below, an additional multi-TCI state indication and activation method based on the integrated TCI scheme is described. A terminal receives a PDSCH including a MAC-CE that can be configured with at least one combination of various MAC-CE structures below from a base station, and after 3 slots in which a HARQ-ACK for the corresponding PDSCH is transmitted 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. If the terminal has been set with two different CORESETPoolIndexes by upper layer signaling and has been set with DLorJointTCIState or UL-TCIState as upper layer signaling, the base station and the terminal can expect that the R field (630) present in the first octet of FIG. 6, which is one of the MAC-CE structures indicating unified TCI state activation, is interpreted as a field indicating a CORESET Pool ID. If the corresponding CORESET Pool ID is set to 0, the terminal can consider that the corresponding MAC-CE can be applied to each code point of the TCI state field in the PDCCH transmitted in the CORESET corresponding to CORESETPoolIndex 0. If the corresponding CORESET Pool ID is set to 1, the terminal can consider that the corresponding MAC-CE can be applied to each code point of the TCI state field in the PDCCH transmitted in the CORESET corresponding to CORESETPoolIndex 1. FIG. 17 is a diagram illustrating an example of a MAC-CE structure for activating and indicating multiple joint TCI states or separate DL or UL TCI states in a wireless communication system according to one embodiment of the present disclosure. The meaning of each field in the MAC-CE structure may be as follows. - Serving Cell ID (1700): This field can indicate to which serving cell the corresponding MAC-CE is applied. 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 corresponding 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, and simultaneousU-TCI-UpdateList4 that include the serving cell indicated by this field. - DL BWP ID (1705): This field can indicate which DL BWP the corresponding MAC-CE applies to, and the meaning of each code point of 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. - UL BWP ID (1710): This field can indicate which UL BWP the corresponding MAC-CE is applied to, and the meaning of each code point of 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. - P i (1715): 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 the terminal can set unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig, which is the upper layer signaling, to either joint or separate, this field can be interpreted as follows, regardless of which of the two settings is set. ** If P i If the value is '00', it means that the corresponding i-th code point has a single TCI state, which may mean that the corresponding code point can include either a joint TCI state, a separate DCI TCI state, or a separate UL TCI state. ** If P i If the value of is '01', it means that the corresponding i-th code point has two TCI states, which can mean that the corresponding code point can include one of two joint TCI states, one separate DL TCI state and one separate UL TCI state, two separate DL TCI states, or two separate UL TCI states. ** If P iIf the value of is '10', it means that the corresponding i-th code point has 3 TCI states, which can mean that the corresponding code point can contain 1 separate DL TCI state and 2 separate UL TCI states, or 2 separate DL TCI states and 1 separate UL TCI state. ** If P i If the value is '11', it means that the corresponding i-th code point has 4 TCI states, which may mean that the corresponding code point may contain 2 separate DL TCI states and 2 separate UL TCI states. * If the terminal can set unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig, which is an upper layer signaling, to one of joint, separate, and mixed mode, this field can be interpreted as follows, regardless of which of the possible setting values ​​is set. The mixed mode can be expressed as a single setting value meaning that a general mixed mode of joint TCI state and separate DL or UL TCI state is possible, or it can be expressed as multiple setting values ​​such as '1joint+1DL', '1joint+1UL', and configured to indicate a specific combination of a specific number of joint TCI states and a specific number of separate DL or UL TCI states. ** If P iIf the value is '00', it means that the corresponding i-th code point has a single TCI state, which may mean that the corresponding code point can include either a joint TCI state, a separate DCI TCI state, or a separate UL TCI state. ** If P iIf the value of is '01', it means that the corresponding i-th code point has two TCI states, which may mean that the corresponding code point can include one of two joint TCI states, one joint TCI state and one separate DL TCI state, one joint TCI state and one separate UL TCI state, one separate DL TCI state and one separate UL TCI state, two separate DL TCI states, or two separate UL TCI states. If the UE has unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig, which is an upper layer signaling, set to a value that means that a general mixed mode of a joint TCI state and separate DL or UL TCI states is possible, both of the above-mentioned one joint TCI state and one separate DL TCI state, and one joint TCI state and one separate UL TCI state can be possible. If the UE has unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig, which is an upper layer signaling, set to one of '1joint+1DL' and '1joint+1UL', only one of the above-mentioned one joint TCI state and one separate DL TCI state, and one joint TCI state and one separate UL TCI state that corresponds to the setting value of unifiedTCI-StateType-r17 can be possible. ** If P iIf the value of is '10', it means that the corresponding i-th code point has 3 TCI states, which can mean that the corresponding code point can contain 1 separate DL TCI state and 2 separate UL TCI states, or 2 separate DL TCI states and 1 separate UL TCI state. ** If P i If the value is '11', it means that the corresponding i-th code point has 4 TCI states, which may mean that the corresponding code point may contain 2 separate DL TCI states and 2 separate UL TCI states. * This field can be 2 bits. - D / U (1720): This field can indicate whether the TCI state ID field within the same octet is a joint TCI state, a separate DL TCI state, or a separate UL TCI state. If this field is 1, the TCI state ID field within the same octet can be a joint TCI state or a separate DL TCI state, and if this field is 0, the TCI state ID field within the same octet can be a separate UL TCI state. - TCI state ID (1725): 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 a TCI-StateId that 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. - R: Indicates reserved bit and can be set to 0. FIG. 18 is a diagram illustrating another example of a MAC-CE structure for activating and indicating multiple joint TCI states or separate DL or UL TCI states in a wireless communication system according to an embodiment of the present disclosure. The meaning of each field in the MAC-CE structure may be as follows. - Serving Cell ID (1800): This field can indicate to which serving cell the corresponding MAC-CE is applied. 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 corresponding MAC-CE can be applied to all serving cells included in one or more of the lists of simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, and simultaneousU-TCI-UpdateList4 that include the serving cell indicated by this field. - DL BWP ID (1805): This field can indicate which DL BWP the corresponding MAC-CE applies to, and the meaning of each code point of 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. - UL BWP ID (1810): This field can indicate which UL BWP the corresponding MAC-CE is applied to, and the meaning of each code point of 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. - P i,1 (1815), P i,2(1820): These two fields 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 the terminal can set unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig, which is a higher layer signaling, to one of joint and separate, or to one of joint, separate, and mixed mode, and the upper layer signaling unifiedTCI-StateType-r17 is set to joint, P in Fig. 18 1,2 , P 2,2 , ... , P 8,2 The fourth octet containing the field can be omitted, P i,1 can be interpreted as follows only for . The mixed mode may be expressed as a single setting value that means that a general mixed mode of a joint TCI state and a separate DL or UL TCI state is possible, or it may be expressed as multiple setting values ​​such as '1joint+1DL', '1joint+1UL', and set to indicate a specific combination of a specific number of joint TCI states and a specific number of separate DL or UL TCI states. ** If P i,1 - If the value of is '0', it means that the corresponding i-th code point has 1 TCI state, which may mean that the corresponding code point includes 1 joint TCI state. ** If P i,1- If the value is '1', it means that the corresponding i-th code point has two TCI states, which may mean that the corresponding code point includes two joint TCI states. * If the terminal can set unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig, which is a higher layer signaling, to one of joint and separate, or to one of joint, separate, and mixed mode, and the upper layer signaling, unifiedTCI-StateType-r17, is set to separate, the terminal sets P in the third octet. i,1 And the P in the 4th octet i,2 can be interpreted as a 2-bit field as follows. The mixed mode can be expressed as a single setting value that means that a general mixed mode of a joint TCI state and a separate DL or UL TCI state is possible, or it can be expressed as multiple setting values ​​such as '1joint+1DL', '1joint+1UL', and set to indicate a specific combination of a specific number of joint TCI states and a specific number of separate DL or UL TCI states. ** If P i,1 The value of and P i,2 If the values ​​are '0' and '0' respectively, it means that the corresponding i-th code point has a single TCI state, which may mean that the corresponding code point can include either a separate DL TCI state or a separate UL TCI state. ** If P i,1 The value of and P i,2If the values ​​of are '0' and '1' respectively, it means that the corresponding i-th code point has two TCI states, which can mean that the corresponding code point can include one separate DL TCI state and one separate UL TCI state, two separate DL TCI states, or two separate UL TCI states. ** If P i,1 The value of and P i,2 If the values ​​of are '1' and '0' respectively, it means that the corresponding i-th code point has three TCI states, which may mean that the corresponding code point may include one separate DL TCI state and two separate UL TCI states, or two separate DL TCI states and one separate UL TCI state. ** If P i,1 The value of and P i,2 If the values ​​of are '1' and '1' respectively, it means that the corresponding i-th code point has four TCI states, which may mean that the corresponding code point may include two separate DL TCI states and two separate UL TCI states. * If the terminal can set unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig, which is the upper layer signaling, to one of joint, separate, and mixed mode, and if unifiedTCI-StateType-r17, which is the upper layer signaling, is set to mixed mode, the terminal sets P in the third octet. i,1can be interpreted as follows, and the 4th octet may not be transmitted. The above mixed mode can be expressed as one setting value that means that a general mixed mode of a joint TCI state and a separate DL or UL TCI state is possible. ** If P i,1 If the value is '0', it may mean that the corresponding i-th code point contains one joint TCI state and one separate DL TCI state. ** If P i,1 If the value is '1', it may mean that the corresponding ith code point contains one joint TCI state and one separate UL TCI state. * If the terminal can set unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig, which is the upper layer signaling, to one of joint, separate, and mixed mode, and if unifiedTCI-StateType-r17, which is the upper layer signaling, is set to mixed mode, the terminal sets P in the third octet. i,1 And P of the 4th octet i,2 can be interpreted as follows. The above mixed mode can be expressed as one setting value that means that a general mixed mode of a joint TCI state and a separate DL or UL TCI state is possible. ** If P i,1 If the value of is '0', it can mean that the corresponding i-th code point contains only one joint TCI state. That is, mixed mode is not used, so P i,2 The value of can be ignored. ** If P i,1If the value of is '1', it may mean that the corresponding i-th code point includes one of one of the separate UL TCI states and one of the separate DL TCI states in addition to one joint TCI state. That is, mixed mode may be used for the corresponding code point, and P i,2 If the value of is '0', one additional separate UL TCI state can be used, P i,2 If the value is '1', one additional separate UL TCI state can be used. - D / U (1825): This field can indicate whether the TCI state ID field within the same octet is a joint TCI state, a separate DL TCI state, or a separate UL TCI state. If this field is 1, the TCI state ID field within the same octet can be a joint TCI state or a separate DL TCI state, and if this field is 0, the TCI state ID field within the same octet can be a separate UL TCI state. - TCI state ID (1830): 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 a TCI-StateId that 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. - R: Indicates reserved bit and can be set to 0. The unifiedTCI-StateType-r17 in MIMOparam-r17 in ServingCellConfig, which is the upper layer signaling described above, may be defined as a new parameter, such as unifiedTCI-StateType-r18 in MIMOparam-r18 in ServingCellConfig, or an existing parameter may be reused. Next, if a terminal can simultaneously receive multiple (for example, two) reference signals (for example, CSI-RS or SSB resources, etc.), the terminal can report channel state information about the simultaneously receivable reference signals to the base station through group based beam reporting. Group based beam reporting can be broadly classified into two methods. The first method of group based beam reporting is that the terminal reports to the base station indices (for example, CRI or SSBRI) of two different reference signals that can be simultaneously received at a single reporting instance. The second method of group based beam reporting is that the terminal reports one or more group(s) to the base station at a single CSI reporting instance. The following is a detailed description of the second method of group based beam reporting. When performing group-based beam reporting of the second method, a group can be composed of indices of two reference signals (for example, CRI or SSBRI) that the terminal can receive simultaneously, and the base station can set the number of groups that the terminal can report to the terminal by referring to the terminal capability report reported by the terminal, such as a higher layer parameter such as 'nrofReportedGroups'. The higher layer parameter 'nrofReportedGroups' can be set to one of 1 to 4 by the base station to the terminal. The two reference signals that the terminal can receive simultaneously, which can be identified through the reference signal indices included in one group, can be one CSI-RS or SSB each selected from two CSI resource sets for CSI reporting settings (which can be defined as two CSI resource sets as specified in TS 38.214, or can also be defined as a channel measurement resource set as specified in TS 38.212). For example, the index of the first reference signal in one group reported by the terminal to the base station may be determined by selecting one reference signal (e.g., the reference signal having the largest measured RSRP value among the reference signals in the CSI resource set) from one of the two CSI resource sets (e.g., the CSI resource set including the reference signal having the largest measured RSRP value among the two CSI resource sets may be selected, and the terminal may report an indicator for the corresponding resource set to the base station as a 'Resource set indicator' in order to report CSI). As described above, the index of the first reference signal in the first group may be the reference signal having the largest RSRP value among all reference signals in the two resource sets, and based on this, the terminal may select the CSI resource set in which the index of the first reference signal in the group is selected from among the two CSI resource sets, and the terminal may report a Resource set indicator for the same to the base station as CSI information. After selecting the index of the first reference signal in the first group, the terminal may select the index of the second reference signal in the first group. The terminal may select the index of the second reference signal in the first group as an index for one of the reference signals in a different resource set among the two resource sets other than the resource set from which the first reference signal in the first group was selected (for example, a reference signal with the largest RSRP measured among multiple reference signals that can be simultaneously received with the first reference signal in the first group). The terminal can report the RSRP of the reference signal indicated by the index of the first reference signal in the first group. For reference signals indicated by indices of other reference signals (e.g., the index of the second reference signal in the first group, etc.), the terminal reports Differential RSRP, which means a difference value from the measured RSRP of the reference signal indicated by the index of the first reference signal in the first group. For example, if the measured RSRP of the reference signal indicated by the index of the first reference signal in the first group is defined as RSRP1 and the measured RSRP of the reference signal indicated by the index of the second reference signal in the first group is defined as RSRP2, the Differential RSRP reported together with the index of the second reference signal in the first group can be determined by the terminal as a value representing the value of RSRP1-RSRP2 in 2-dB intervals. To perform group-based beam reporting in the second method, two sets of CSI resources must be defined as described above. If the resourceType in the upper layer parameter 'CSI-ResourceConfig' is set to 'periodic' or 'semiPersistent' and 'groupBasedBeamReporting-v1710' is set, the base station can set two NZP CSI-RS resource sets (for example, two NZP-CSI-RS-ResourceSetIds can be set in nzp-CSI-RS-ResourceSetList), or two CSI SSB resource sets (for example, two CSI-SSB-ResourceSetIds can be set in csi-SSB-ResourceSetList), or one NZP CSI-RS resource set and one CSI SSB resource set (for example, one NZP-CSI-RS-ResourceSetId can be set in nzp-CSI-RS-ResourceSetList and one CSI-SSB-ResourceSetId can be set in csi-SSB-ResourceSetList). If one NZP CSI-RS resource set and one CSI SSB resource set are configured and the terminal performs group-based beam reporting of the second method to the base station, the terminal can report to the base station that one CSI SSB resource set includes a reference signal indicated by the index of the first reference signal in the first group by setting the resource set indicator to '1'. If one NZP CSI-RS resource set and one CSI SSB resource set are configured and the terminal performs group-based beam reporting of the second method to the base station, the terminal can report to the base station that one NZP CSI resource set includes a reference signal indicated by the index of the first reference signal in the first group by setting the resource set indicator to '0'. If two NZP CSI-RS resource sets are set and the terminal performs group-based beam reporting of the second method to the base station, the terminal may report to the base station that the first NZP CSI resource set includes a reference signal indicated by the index of the first reference signal in the first group by setting the resource set indicator to '0', or may report to the base station that the second NZP CSI resource set includes a reference signal indicated by the index of the first reference signal in the first group by setting the resource set indicator to '1'.If two CSI SSB resource sets are set and the terminal performs group-based beam reporting of the second method to the base station, the terminal may report to the base station that the first CSI SSB resource set includes a reference signal indicated by the index of the first reference signal within the first group by setting the resource set indicator to '0', or may report to the base station that the second CSI SSB resource set includes a reference signal indicated by the index of the first reference signal within the first group by setting the resource set indicator to '1'. If the upper layer parameter groupBasedBeamResporting-v1710 (or groupBasedBeamReporting-r17) is configured in the terminal, the terminal does not need to update measurements for more than 64 CSI-RS and / or SSB resources. And the terminal can report nrofReportedGroups (if configured) number of group(s) to the base station at a single reporting time, and the terminal selects one CSI-RS or SSB from each CSI resource set of the two CSI Resource Sets according to the reporting setting as described above, and selects the two CRIs or SSBRIs as one group. Here, the CSI-RS and / or SSB resources of each group are selected as resources that can be simultaneously received by the terminal. The following Table 44 is a table explaining how to configure the CSI field (field, region) for the nth CSI report when the terminal performs the group-based beam report of the second method to the base station. As described above, the terminal can configure the CSI field with a resource set indicator for selecting and indicating one of two CSI resource sets (or channel measurement resource sets), and two reference resource indexes included in up to four resource groups and RSRP or differential RSRP for the same, and report them to the base station. CSI report numberCSI fieldsCSI report #nResource set indicatorCRI or SSBRI #1 of 1st resource group, if reportedCRI or SSBRI #2 of 1st resource group, if reportedCRI or SSBRI #1 of 2nd resource group, if reportedCRI or SSBRI #2 of 2nd resource group, if reportedCRI or SSBRI #1 of 3rd resource group, if reportedCRI or SSBRI #2 of 3rd resource group, if reportedCRI or SSBRI #1 of 4th resource group, if reportedCRI or SSBRI #2 of 4th resource group, if reportedRSRP of CRI or SSBRI #1 of 1st resource groupDifferential RSRP of CRI or SSBRI #2 of 1st resource groupDifferential RSRP of CRI or SSBRI #1 of 2nd resource group, if reportedDifferential RSRP of CRI or SSBRI #2 of 2nd resource group, if reportedDifferential RSRP of CRI or SSBRI #1 of 3rd resource group, if reportedDifferential RSRP of CRI or SSBRI #2 of 3rd resource group, if reportedDifferential RSRP of CRI or SSBRI #1 of 4th resource group, if reportedDifferential RSRP of CRI or SSBRI #2 of 4th resource group, if reported Here, each component included in the CSI field can be determined as shown in Table 45 below. Here means the number of CSI-RS resources set in the corresponding CSI resource set, means the number of SS / PBCH blocks set within the corresponding CSI resource set. FieldBitwidthCRI SSBRI RSRP7Differential RSRP4Capability Index2 Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. The contents of the present disclosure can be applied to FDD and TDD systems. In the present disclosure below, determining the priority between A and B can be referred to in various ways, such as selecting a higher priority according to a predetermined priority rule and performing an operation corresponding to it, or omitting or dropping an operation for a lower priority. In the following disclosure, the above examples are described through a number of embodiments, but they are not independent and one or more embodiments may be applied simultaneously or in combination. In the following description of the present disclosure, for convenience, cells, transmission points, panels, beams, and / or transmission directions, which can be distinguished through upper layer / L1 parameters such as TCI state or spatial relation information, or indicators such as cell ID, TRP ID, and panel ID, may be uniformly described as TRP (transmission reception point), beam, or TCI state. Therefore, in actual application, TRP, beam, or TCI state may be appropriately replaced with one of the above terms. In describing the present disclosure below, upper layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling. - MIB (Master Information Block) - SIB (System Information Block) or SIB - RRC (Radio Resource Control) - MAC (Medium Access Control) CE (Control Element) In addition, L1 signaling may be signaling corresponding to at least one or a combination of one or more of the following physical layer channels or signaling methods. - PDCCH (Physical Downlink Control Channel) - DCI (Downlink Control Information) - UE-specific DCI - Group common DCI - Common DCI - Scheduling DCI (DCI used for scheduling downlink or uplink data, for example) - Non-scheduled DCI (e.g. DCI not intended for scheduling downlink or uplink data) - PUCCH (Physical Uplink Control Channel) - UCI (Uplink Control Information) The term slot used in the present disclosure below is a general term that may refer to a specific time unit corresponding to a Transmit Time Interval (TTI), and specifically may mean a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system. In the following disclosure, the above examples are described through a number of embodiments, but they are not independent and one or more embodiments may be applied simultaneously or in combination. <First embodiment: Terminal beam reporting method and base station uplink beam instruction method for supporting multi-panel simultaneous transmission> In the first embodiment, a method for a terminal to report a combination of beams capable of simultaneous transmission to a base station in order to support a multi-panel simultaneous transmission technique is specifically described. A terminal can receive multiple (for example, two) reference signals (for example, SSB or CSI-RS) transmitted by a base station simultaneously (here, 'simultaneously' means a case where downlink signal reception or uplink transmission is performed with the same resource for at least one or more time symbols (symbols in time domain)) by using a multi-panel. In this case, the terminal can simultaneously receive only some combinations of reference signals among all reference signals set for the terminal through the multi-panel. Since the base station cannot know the combinations of reference signals that the terminal can simultaneously receive through the multi-panel, the base station can request a CSI report (which can be expressed as a 'group-based beam report') from the terminal in order to find out this. In this way, the terminal can perform group-based beam reporting to the base station by grouping the 'indices of reference signal resources' that can be simultaneously received through multiple panels into 'one group' (or can be expressed as a resource group or a beam pair or a beam combination or a beam group, etc.), and the terminal can select one or more resource groups (the value set by the upper layer parameter 'nrofReportedGroups') and report them to the base station according to the terminal capability and the upper layer parameter set by the base station based on the terminal capability. At this time, an indicator (e.g., 'Resource set indicator') for indicating a CSI resource set (meaning a resource set including the reference signal among two SSB or CSI-RS resource sets (two CSI-SSB-ResourceSets or two NZP-CSI-RS-ResourceSets or a combination of one CSI-SSB-ResourceSet and one NZP-CSI-RS-ResourceSet) set in the upper layer parameter 'CSI-ResourceConfig' when the upper layer parameter 'groupBasedBeamReporting-v1710' is set) including the reference signal received with the largest RSRP value measured through reference signals included in the entire resource group, and a value expressed in bits by quantizing the RSRP value of the reference signal received with the largest RSRP and the differential RSRP of other reference signals included in the group beam report (the difference value between the largest RSRP and the RSRP at which the reference signal is received) may be reported together. Or, depending on the upper layer parameter settings, some differential RSRP or resource groups may not be reported and only some values ​​may be reported.This is a method for reporting to the base station that the terminal can simultaneously receive downlink signals through multiple panels. Additionally, the terminal may support the ability of the terminal to simultaneously transmit multiple uplink signals (e.g., including both channels such as PUCCH or PUSCH or SRS and reference signals, etc.) to the base station using multiple panels. Similarly, since the base station may not know the combination of reference signals that the terminal refers to in determining the uplink beam over which the terminal can simultaneously transmit uplink signals via multiple panels, the base station may request the terminal to report CSI (which may be expressed as 'group-based beam reporting') in order to find out. That is, if the base station can know the combination of reference signals that the terminal refers to in determining an uplink beam through which the terminal can transmit an uplink signal simultaneously through multiple panels, the base station can instruct the terminal to activate a TCI state that can designate a reference signal within the corresponding combination of reference signals as a reference signal of QCL info. That is, if the referenceSignal of the QCL info (for example, the type of QCL info is type D) of the two TCI states (two joint TCI states or two UL TCI states) indicated by the base station are each set to an index of a reference signal resource included in a certain resource group that the terminal reported to the base station, the terminal can determine an uplink beam by referring to the indicated TCI state and simultaneously transmit an uplink signal based on a multi-panel simultaneous transmission technique. In this case, the terminal can perform group-based beam reporting to the base station for simultaneous uplink transmission according to one of the following methods or a combination thereof. [Method 1: Using the same group-based beam report for simultaneous downlink reception and simultaneous uplink transmission] If a terminal can simultaneously receive multiple downlink signals (including channels and reference signals) using multiple panels, and can simultaneously transmit multiple uplink signals using multiple panels, the terminal can report the corresponding terminal capability (simultaneous uplink and downlink transmission and reception capability) to the base station. In addition, the terminal can use one group-based beam report to report a resource group capable of simultaneous uplink and downlink transmission and reception to the base station, as in the operation described in Method 1. The terminal can perform multi-panel simultaneous uplink transmission and downlink simultaneous reception based on reference signals included in the resource group(s) reported to the base station through the group-based beam report. That is, the terminal can simultaneously notify the base station of a resource group capable of simultaneous uplink transmission and a resource group capable of simultaneous downlink reception through one group-based beam report, rather than separate group-based beam reports. Method 1 can be combined with a TCI state indication method based on joint TCI state. Alternatively, Method 1 can also be combined with a TCI state indication method based on separate TCI state (DL TCI state and UL TCI state are indicated respectively). For example, the base station can activate codepoints for single or multiple TCI state indications through MAC CE by referring to group-based beam report reported by terminal through Method 1. If the base station sets upper layer parameter unifiedTCI-StateType-r17 to 'joint' to the terminal, one or multiple (for example, two) TCI states can correspond to each codepoint for TCI state indication activated by MAC CE. In order for the base station to schedule multi-panel based simultaneous uplink transmission to the terminal, the codepoints including two TCI states should be indicated, and the base station can indicate two TCI states based on group-based beam report reported by the terminal. For example, the reference signal for QCL type D of the two TCI states instructed by the base station to the terminal may be set to two reference signals included in one group of the group-based beam report information reported by the terminal. More specifically, the first TCI state of the two TCI states instructed by the base station to the terminal may be one of the TCI states in which the reference signal for QCL type D is set to the first reference signal within the nth (where n is a value of 1 to 4) group of the group-based beam information reported by the terminal to the base station. The second TCI state of the two TCI states instructed by the base station to the terminal may be one of the TCI states in which the reference signal for QCL type D is set to the second reference signal within the nth group of the group-based beam information reported by the terminal to the base station. In this way, if a terminal reports to the base station a beam combination capable of simultaneous multi-panel based uplink transmission to the base station through group-based beam reporting, and the base station instructs the terminal based on this TCI state, the base station can schedule an uplink data channel to be simultaneously transmitted through multiple panels to the terminal. If the two TCI states instructed by the base station are not values ​​selected based on the group-based beam reporting reported by the terminal, the uplink signal simultaneously transmitted by the terminal through multiple panels may not be received by the base station at the SNR expected by the base station. Alternatively, multi-panel based simultaneous uplink transmission may not be performed depending on the implementation of the terminal. This means that the terminal may transmit an uplink signal only through one panel and not through the other panel. [Method 2: Using separate group-based beam reporting for simultaneous downlink reception and simultaneous uplink transmission] If the terminal can receive / transmit downlink / uplink channels simultaneously by using multiple panels, the terminal can report the corresponding terminal capability (simultaneous uplink and downlink transmission and reception) to the base station. Unlike method 1, method 2 is a method that performs group-based beam reporting for simultaneous downlink reception and group-based beam reporting for simultaneous uplink transmission, respectively. This is because the downlink reception beam for simultaneous downlink reception and the uplink transmission beam for simultaneous uplink transmission may not match. Therefore, the terminal can perform group-based beam reporting separately for uplink and downlink to report each transmission beam group and reception beam group to the base station. The same type of group-based beam reporting method as described in Method 1 can be used, but the terminal must report separate terminal capability and must receive separate upper layer parameters for configuring uplink simultaneous transmission group-based beam reporting from the base station. In addition, the terminal performs separate uplink simultaneous transmission group-based group beam reporting through separate CSI reporting. At this time, the field of the CSI information used for performing the group-based beam reporting for uplink simultaneous transmission performed separately can be configured identically to the field of the CSI information used for performing the group-based beam reporting for downlink simultaneous reception. That is, it can be configured with a resource set indicator for indicating a resource set including a reference signal received with the largest value of RSRP, a field for reporting a beam group, a field for reporting the largest value of RSRP, and a field for reporting differential RSRP for reference signals other than the reference signal received with the largest value of RSRP. For example, fields in Tables 76 and 77 can be used. [Method 3: New beam reporting method for multi-panel simultaneous transmission] Method 3 is a method in which the terminal performs group-based beam reporting for simultaneous downlink reception and group-based beam reporting for simultaneous uplink transmission, respectively. At this time, the terminal can report to the base station the terminal capability for reporting a new beam reporting method for reporting beam groups capable of simultaneous multi-panel transmission, along with the terminal capability for simultaneous multi-panel transmission. As an example of a new possible beam reporting method, when a terminal performs a CSI report to a base station, the terminal may report additional information about the reported beam together with the reported beam. When the terminal performs information about the beam through a CSI report, the terminal may report an indicator indicating that the corresponding beam can be simultaneously transmitted to multiple panels together with the reported beam information. For example, if the terminal can simultaneously transmit an uplink channel to multiple panels using uplink beams referencing K (where K is one of the values ​​greater than 1, for example 2) different CSI-RSs (or SSBs), the terminal may include one new indicator related to the simultaneous uplink transmission in the CSI information for each CSI-RS along with the CSI information for the K different CSI-RSs. For example, the terminal may set all new indicators included in the CSI information for the K CSI-RSs that can be referenced for performing the simultaneous uplink transmission to the base station and report them. For example, if a terminal can perform multi-panel uplink simultaneous transmission by referencing a CSI-RS having a CRI (CSI-RS resource indicator) of 1 and a CSI-RS having a CRI of 2, the terminal can report CSI information to the base station by setting a new indicator to '1' in the CSI information for the CSI-RS having a CRI of 1 and also setting a new indicator to '1' in the CSI information for the CSI-RS having a CRI of 2. In addition, if the terminal can perform multi-panel uplink simultaneous transmission by referencing other CSI-RS combinations, the terminal can additionally consider this and perform CSI reporting to the base station. For example, if the terminal can perform multi-panel uplink simultaneous transmission by referencing a CSI-RS having a CRI of 5 and a CSI-RS having a CRI of 7, the terminal can report CSI information to the base station by setting a new indicator in the CSI information for the CSI-RS having a CRI of 5 to '2' (or any value excluding the value of the new indicator used for other simultaneous transmission-enabled beam combinations ('1' in the example) and any value of the new indicator for indicating a beam that does not support multi-panel simultaneous transmission (for example, '0')) and setting the new indicator to '2' in the CSI information for the CSI-RS having a CRI of 7. For other beam combinations that can perform multi-panel simultaneous transmission, the terminal can equally set new indicators in the CSI information for each beam and report them to the base station. Although described for CSI-RS, it can be similarly applied to SSB, and the terminal can distinguish the beam combinations that can be simultaneously transmitted based on SSBRI instead of CRI and report them to the base station. If the uplink beam determined based on a specific reference signal cannot support simultaneous transmission based on multi-panel, the terminal can set a new indicator included in the CSI report for the reference signal to a specific value and report it to the base station. The value of the new indicator included in the CSI report for the reference signal that does not support multi-panel simultaneous transmission may be set to '0', for example. Alternatively, if the base station sets the number of beam combinations that the terminal can report to the terminal + 1 to 'X' through a higher layer parameter, the base station and the terminal can define 'X' as the value of the new indicator included in the CSI report for the reference signal that does not support multi-panel simultaneous transmission. Another example of additional information reported together with the beam information may be an operation in which the terminal reports CSI information to the base station by adding some indicators. If the terminal can simultaneously transmit an uplink channel with multiple panels using uplink beams referencing K (where K is one of the values ​​greater than 1, for example 2) different CSI-RSs (or SSBs), the terminal may include a new indicator set to some value X (where X is, for example, 0) for CSI reports for some of the reference signals among the entire reference signals, and may also include a new indicator set to some value Y (for example, 1) for CSI reports for some of the reference signals among the entire reference signals. If the terminal reports CSI information to the base station with a new indicator set to X for some reference signal 1, and reports CSI information to the base station with a new indicator set to Y for some reference signal 2, it may mean that the terminal can perform multi-panel-based simultaneous transmission with reference to reference signal 1 and reference signal 2. This may mean that the terminal can perform multi-panel-based simultaneous transmission referring to multiple reference signals, each of which is set with a new indicator of different values. Implicitly, the new indicator may be understood as an indicator indicating one panel of the multi-panels, and the CSI information report may mean that the terminal can perform multi-panel-based simultaneous transmission by simultaneously using a first panel corresponding to the new indicator X for reference signal 1 and a second panel corresponding to the new indicator Y for reference signal 2. As described above, the base station can refer to the CSI information with the new indicator added reported by the terminal to instruct the terminal to perform multi-panel-based simultaneous transmission, and set two TCI states based on this. That is, as described above, the base station can identify reference signals that can be used as a reference for determining an uplink beam combination that the terminal can simultaneously transmit to multiple panels through one or a combination of various CSI reporting methods that the terminal can perform. The base station can activate codepoints for indicating TCI states using a combination of identified reference signals. For example, codepoints for MAC CE-based TCI states can be activated up to a maximum of 8 or any value greater than 8 (e.g., 16). Each codepoint can indicate one or two TCI states in the case of a joint TCI state, and one or two TCI-states and / or one or two TCI-UL-states in the case of a separate TCI state. The base station can indicate one of the activated codepoints as a DCI (if two or more codepoints are activated via MAC CE). At this time, two TCI states (assuming a joint TCI state) can be indicated to the code point indicated by the base station to the terminal through DCI, and the combination of reference signals of QCL type D of the two TCI states can be a combination of reference signals for which the terminal reported CSI to the base station through the above-described method (one or more combined methods). Since this combination of reference signals means reference signals that the terminal can refer to in determining an uplink beam for simultaneous uplink signal transmission with multiple panels, the terminal can perform simultaneous multi-panel transmission by using the TCI state indicated by the corresponding code point. <Second embodiment: Method for reporting beam information for selecting a beam combination suitable for simultaneous transmission of multiple panels> In the second embodiment, we specifically describe beam information additionally required for a base station to determine and direct a transmission beam of a terminal supporting multi-panel simultaneous transmission, and propose a method for a terminal to report this to the base station. If the terminal performs group-based beam reporting as described in the first embodiment, the terminal reports to the base station a differential RSRP calculated based on the largest RSRP among the reception RSRPs of the reference signal resources in the reporting resource group or the reception RSRPs of the reporting resources. At this time, when the terminal supports multiple panel-based simultaneous transmission techniques, two transmission power determination methods can be considered depending on the panel configuration implementation of the terminal. As the first transmission power determination method, the terminal can simultaneously transmit an uplink channel by increasing the sum of the transmission power in multi-panel transmission compared to single-panel transmission. This first transmission power determination method can be used when the terminal is implemented so that it can use the maximum transmission power for each panel. As another second transmission power determination method, the terminal can simultaneously transmit an uplink channel by maintaining the sum of the transmission power that the terminal can operate in multi-panel transmission compared to single-panel transmission the same as in the case of transmitting with a single panel. This second transmission power determination method can be used when multiple panels implemented in the terminal share the total power that the terminal can operate. If the terminal can simultaneously transmit uplink channels using multiple panels and can utilize the first transmission power determination method, the terminal should control the transmission power so that the total EIRP (effective isotropic radiated power) of uplink signals transmitted by multiple panels during simultaneous multi-panel transmission does not exceed a value limited by regulations. That is, even if the terminal can simultaneously transmit uplink channels in different directions using multiple panels and increase the transmission power using each panel, it may not be able to allocate power exceeding a certain transmission power depending on the total EIRP value of the simultaneously transmitted uplink signals. FIG. 19 is a diagram illustrating an example of two overlapping beams that a terminal simultaneously transmits using multiple panels. The terminal can transmit two beams (1901, 1902) using two panels (or more panels). The two beams may overlap for some areas and some angles, and the sum of EIRPs may increase in the area where the two beams overlap. For example, the sum of EIRPs (1905) in the two overlapping areas (1903, 1904) may be defined. At this time, considering the EIRP limitation (1910) set as a regulation, the terminal must determine the transmission power of the two beams such that not only each EIRP of the two transmitted beams but also the total EIRP of the overlapping area (e.g., 1905) is less than the EIRP proposal (1910) set as a regulation. FIG. 20 is a diagram illustrating an example in which a terminal adjusts the transmission power of two beams in consideration of the total EIRP. Unlike the example illustrated in FIG. 19, the case in which the two beams (2001, 2002) transmitted by the terminal overlap (2003, 2004) more is illustrated, so that the total EIRP (2005) is larger than the EIRP limit (2010) set by the regulation. In this case, the terminal must reduce the transmission power of the two beams (2021, 2022), and the total EIRP (2025) in the part where the two beams overlap (2023, 2024) must be smaller than or equal to the EIRP limit (2010). In this way, even if a single beam is not larger than the EIRP limit, the total EIRP may become larger than the EIRP limit in the area where multiple beams overlap, depending on the degree to which multiple beams transmitted by the terminal to the multi-panel overlap. In such a case, the terminal may reduce the transmission power of each beam so that the total EIRP in all areas (including the total EIRP in the overlapping areas) becomes less than the EIRP limit in order to perform multi-panel-based simultaneous transmission. A terminal can report to a base station, through group-based beam reporting, a beam combination capable of simultaneously transmitting multiple uplink signals using multiple panels and a beam combination capable of simultaneously receiving multiple downlink signals using multiple panels, and also reports the reception RSRP of each beam in the beam combination. However, when the terminal performs simultaneous transmission based on the beam combination selected by the base station, the terminal does not report to the base station, information such as the degree of overlap between two beams or the maximum transmission power of each beam considering the EIRP limitation when transmitting two beams simultaneously. Therefore, the base station selects one of the multiple beam combinations reported by the terminal without considering the overlap information between the two beams or the size of the maximum transmission power of each beam considering the EIRP limitation. If the beams that the base station has selected and instructed to the terminal to support simultaneous multi-panel transmission and reception are significantly overlapped (two beams that are 'largely overlapped' may mean that their directions are similar, so that the total EIRP, which is the sum of the EIRPs of the two beams, is greatly increased. Conversely, two beams that are 'smallly overlapped' may mean that their directions are different, so that the total EIRP, which is the sum of the EIRPs of the two beams, is not greatly increased), the terminal may significantly reduce the transmit power of each beam when transmitting simultaneously on the two beams instructed, subject to regulatory EIRP limitations. In this way, if the base station instructs the terminal to transmit and receive beams simultaneously based only on the information about the beam combination and the RSRP of each beam in the beam combination, the transmission power of each beam may be significantly reduced during simultaneous uplink transmission to the terminal. In this case, the base station may receive the uplink channel with a lower reception SNR than the expected reception SNR based on the RSRP information of each beam reported. In addition, even if the base station instructs the terminal to increase the transmission power of the uplink channel that is received at a lower level, the terminal may no longer be able to increase the transmission power of each beam due to the EIRP limitation. As another example, the base station can instruct beams for multi-panel simultaneous transmission by referring to the beam combination of the group-based beam report reported by the terminal and the RSRP of the beams. And when the RSRP of the beams is large, the base station can schedule a PUSCH with a high MCS to the terminal in order to increase the throughput of uplink data. At this time, the base station can instruct the terminal to perform PUSCH transmission with a high transmission power in order to realize a sufficient data throughput, but the terminal may not perform multi-panel simultaneous transmission with a sufficiently high transmission power depending on the degree of overlap between two beams in the beam combination described above. If the terminal simultaneously transmits a PUSCH scheduled with a high MCS to multi-panels with insufficient transmission power, the base station may not successfully receive the corresponding PUSCH. If the base station can determine information such as the degree of overlap of beam combinations reported by the terminal or the maximum transmission power determined considering the EIRP limitation when transmitting multiple beams simultaneously according to the beam combination, the base station can utilize additional information about the beam combination (such as the degree of overlap or the maximum transmission power) when determining the beam combination for simultaneous transmission and reception of multiple panels and instructing it to the terminal. For example, if the base station has received additional information about the beam combination from the terminal, the base station can select a beam combination in which the multiple beams overlap less and instruct it to the terminal, or it can select a beam combination in which the multiple beams overlap significantly but have good reception RSRP and instruct it to the terminal. In other words, the base station can perform more flexible beam instruction to the terminal by utilizing specific additional beam information. There are two main methods that can be considered for a terminal to report such additional beam information to a base station. In the first method, when a terminal performs a power headroom report (PHR), the terminal can report additional information on beam combination to the base station together. In the second method, the terminal can report additional information on beam combination to the base station by supplementing the group-based beam report, which is a CSI report. In the second embodiment, a method for a terminal to report additional information on beam combination to a base station using the power headroom report method and the additional information reported are specifically described, and in the second embodiment, a method for a terminal to report additional information on beam combination to a base station using the group-based beam report method and the additional information reported are specifically described. <Example 2-1: Power headroom-based multi-panel simultaneous transmission beam information reporting method> In the second embodiment, a method of reporting beam information of beam combinations for multi-panel simultaneous transmission using a power headroom reporting method is specifically proposed, along with additional information to be reported. When a PHR (Power Headroom Report) event occurs, the terminal transmits a MAC CE for performing PHR to the base station. At this time, the terminal transmits the MAC CE for PHR reporting to the base station using the PUSCH. As described above, in order to support the multi-panel simultaneous transmission / reception technique, the base station can request group-based beam reporting to the terminal. For example, group-based beam reporting can be requested based on periodic or semi-persistant or aperiodic CSI reporting. Along with the group-based beam reporting request, the terminal can transmit additional information about the reported beam group to the base station, and the additional information can be transmitted to the base station together with the PH reporting. As described above, representative PHR trigger conditions may be considered, such as when a change in downlink path loss associated with uplink transmission power is greater than a specific threshold with respect to the previous PH reporting time, or when a timer that operates at a certain period expires. The same PHR trigger conditions may also be used to transmit additional information about beam combinations that the terminal reports to the base station to support multi-panel simultaneous transmission, as a PHR. If the same PHR trigger condition is used, the terminal can determine the additional information to be reported as a PHR by referring to the group-based beam information that it reported to the base station most recently. FIG. 21 is a diagram illustrating an example of group-based beam reporting with additional information when a PHR including additional information of a beam combination reported by a terminal is not performed simultaneously with group-based beam reporting. The terminal may transmit a PUSCH (2111) multiplexed with CSI information (2112) for group-based beam reporting to the base station at some previous point in time. Thereafter, the base station may transmit a DCI (2120) to the terminal for performing aperiodic CSI reporting (or for indicating a CSI request field) for updating the CSI information. Alternatively, unlike FIG. 21 , semi-persistant or periodic CSI reporting may be periodically activated or configured. The terminal may determine CSI information (2122) for group-based beam reporting according to the received DCI (2120) and multiplex it onto the PUSCH (2121) and report it. If periodic CSI reporting or semi-persistant CSI reporting is performed, the UE may transmit PUSCH (2121) or PUCCH (not PUSCH (2121)) depending on the semi-persistant or periodic CSI reporting configuration without receiving a separate DCI (2120). It is assumed that PHR, which can transmit additional information about a beam combination reported by the UE up to this point, has not been triggered. At some point thereafter, a PHR may be triggered (2130), and the UE may determine (2132) a MAC CE for a PHR report including additional beam information about a beam combination reported by the UE in association with the CSI information (2122) most recently reported by the UE through a group-based beam report. The UE multiplexes the MAC CE for the PHR report determined in this manner with data of the PUSCH (2131) and transmits it to the base station.Fig. 21 is only an example and PH information including CSI information and additional information associated therewith for group-based beam reporting may be reported to the base station in other timelines depending on the PHR trigger conditions described later. In addition to the above-mentioned PHR trigger conditions, new PHR trigger conditions can be added by additionally considering conditions for multi-panel simultaneous transmission. The following describes examples of additional PHR trigger conditions that can be considered to support multi-panel simultaneous transmission and reception when the base station and terminal support multi-panel simultaneous transmission and reception. PHR can be triggered according to one or more combinations of the trigger conditions below. [Additional Condition 1] If the base station requests the terminal to perform group-based beam reporting in order to support the multi-panel simultaneous transmission / reception method, the terminal may trigger a PH report. At this time, the PH report may be triggered depending on whether the group-based beam report is performed, regardless of whether the phr-ProhibitTimer for preventing PHR triggering for a certain period has expired. Or, the PH report may be triggered only when the phr-ProhibitTimer of the terminal has expired and the terminal performs the group-based beam report. In this case, if the phr-ProhibitTimer of the terminal has not expired but the terminal performs the group-based beam report, the PH report may not be triggered. If the group-based beam report is performed and the terminal performs the PH report at the same time, the triggered PHR information may be transmitted together with the PUSCH on which the CSI information for the group-based beam report is transmitted. FIG. 22 is a diagram illustrating an example of an operation in which a terminal reports group-based beam reporting and additional information related thereto along with PH. The terminal may determine CSI information (2222) for group-based beam reporting according to the received DCI (2220) and multiplex it onto a PUSCH (2221) and report it. If periodic CSI reporting or semi-persistant CSI reporting is performed, the terminal may transmit a PUSCH without receiving a separate DCI (2220). Since PUCCH cannot be used to perform PHR reporting, which will be described later, only PUSCH, not PUCCH, may be considered in order to simultaneously perform group-based beam reporting and the PHR related thereto, as illustrated in FIG. 22. According to [Additional Condition 1], when a terminal performs group-based beam reporting, a PH report may be triggered together, and the terminal may determine a MAC CE for a PHR report including additional beam information for a beam combination reported by a group-based beam report (2223). Thereafter, the terminal multiplexes the determined MAC CE (2223) for the PH report together with the CSI information (2222) for the group-based beam report onto a PUSCH (2221) and transmits the same to the base station. Alternatively, unlike the example illustrated in FIG. 22, the PHR information may be transmitted on a separate PUSCH from the PUSCH on which the CSI information for the group-based beam report is transmitted. For example, similar to the example illustrated in FIG. 21, the terminal may multiplex a PHR MAC CE (2132) including additional information for a beam combination (2122) reported by the most recently transmitted group-based beam report onto a PUSCH (2131) transmitted after the PUSCH (2121) on which the CSI information is transmitted. [Additional Condition 2] If the base station requests the terminal to perform group-based beam reporting to support the multi-panel simultaneous transmission / reception method, and if the additional information about the beam combination transmitted to the base station through the group-based beam reporting changes by a greater than a threshold value compared to the value reported in the previous PH report, the terminal can trigger a PH report. Similar to Additional Condition 1, the terminal can perform group-based beam reporting regardless of whether phr-ProhibitTimer has expired, and if the amount of change in the additional information about the beam combination being reported changes by a greater than threshold value compared to the value reported in the previous PH report, the terminal can trigger a PH report. Alternatively, if the phr-ProhibitTimer of the terminal has expired and the terminal performs group-based beam reporting and the amount of change in the additional information about the beam combination being reported changes by a greater than threshold value compared to the value reported in the previous PH report, a PH report can be triggered. As an example of additional information to be specifically described later, when the terminal simultaneously transmits beams in a beam combination, the terminal may report to the base station the transmission power of each beam that the terminal can transmit at maximum. If the configuration of the beam combination reported by the terminal changes or the configuration of the beam combination is the same but the amount of change in the transmission power of the beams is greater than a certain threshold, the terminal may trigger a PH report. Here, the threshold may be set by the base station to the terminal as a higher layer parameter or may be predetermined. Since a CSI report for performing group-based beam reporting may include an indicator for indicating multiple beam combinations and multiple beams in one beam combination, a rule may be required between the base station and the terminal to determine a value to be compared with the threshold to determine whether to trigger a PH report. At least one combination of the following rules may be used. - 1) If the amount of change in any one or more additional beam information for all beam combinations reported by the terminal and all beams included in the beam combinations is greater than the threshold, the terminal can trigger a PH report. - 2) If the average change in additional beam information for all beam combinations reported by the terminal and all beams included in the beam combinations is greater than the threshold, the terminal can trigger a PH report. - 3) If the amount of change in one or more (or all, or the average of the beam information values) of the additional beam information values ​​among the beams included in the first (or k-th) beam combination among all beam combinations reported by the terminal is greater than the threshold, the terminal can trigger a PH report. If whether to trigger a PH report is determined based on the k-th beam combination, the base station and the terminal can define a value for k in advance, and set k as a defined rule or a higher layer parameter. The additional beam information reported by the terminal is described as an example of a value compared to a threshold to determine whether the above PH report is triggered. However, the terminal may also determine whether PH is triggered by comparing the threshold with information that is not reported to the base station, not the additional beam information reported to the base station. For example, as in the example described above, when simultaneously transmitting with a beam combination, the terminal may compare the change in path loss value of the downlink reference signal selected to report the beam combination, not the transmission power that can be transmitted, with the threshold. When a terminal performs group-based beam reporting for multi-panel simultaneous transmission and the associated PH report is triggered, the following information may be considered as additional beam information for beam combinations that can be reported together with PH. - Additional beam information 1) When a terminal simultaneously transmits all beams included in a beam combination, the maximum transmission power value that the terminal can transmit for each beam can be determined as additional beam information. If the terminal reports multiple beam combinations to the base station, the terminal can determine the maximum transmission power for transmitting each beam when simultaneously transmitting each beam combination and report it together with the PH. In this way, in order to report the maximum transmission power for all beams in the entire beam group together with the PH, P for each serving cell CMAX,f,c The number of fields to report can be increased, i.e., one P per serving cell. CMAX,f,c The number of fields to report can be increased to multiple, and P per serving cell CMAX,f,c The total number of fields to report can be defined as mg, which takes into account both the number of beam combinations reported by the terminal (e.g., the number of groups indicated by the 'higher layer parameter 'nrofReportedGroups', g) and the number of beams included in each beam combination (e.g., m). The MAC CE format for reporting the maximum transmit power values ​​of each beam, which is PH and additional beam information, will be described in detail later. - Additional beam information 2) When a terminal simultaneously transmits all beams included in a beam combination, the terminal can determine the power headroom (PH) for each beam as additional beam information. If the terminal reports multiple beam combinations to the base station, the terminal can determine the maximum transmission power for transmitting each beam when simultaneously transmitting each beam combination, and calculate the virtual PH according to the reference format, or calculate the actual PH according to the actually transmitted signal if there is an actual transmitted signal. The terminal can perform PH reporting by adding the virtual PH or actual PH for all beams in all beam combinations calculated in this way. That is, the terminal can transmit to the base station PH information for all beams in all beam combinations transmitted (or transmitted) to the base station according to group-based beam reporting together with the PH information reported to the PUSCH (meaning the PH information described above in the PHR related paragraph). Similarly to the case where the maximum transmit power is selected as additional beam information, the terminal can report mg PH fields to the base station by adding them to the PH report, considering both the number of beam combinations reported per serving cell (e.g., the number of groups indicated by the 'higher layer parameter 'nrofReportedGroups', g) and the number of beams included in each beam combination (e.g., m). - Additional beam information 3) If the terminal simultaneously transmits all beams included in a beam combination and reports MPE (maximum permissible exposure, when the upper layer parameter 'mpe-Reporting-FR2' is set and the 'P' field of the MAC CE format for PH reporting is set to '1') together with the PH report, the terminal can determine the MPE for each beam as additional beam information. If the terminal reports multiple beam combinations to the base station and reports MPE together with the PH report, the terminal can determine the MPE to be applied for transmitting each beam when transmitting each beam combination and report it together with the PH. In the same way as when the maximum transmit power is selected as additional beam information, the terminal can add mg MPE fields to the PH report and report them to the base station, considering both the number of reported beam combinations to be reported per serving cell (e.g., the number of groups indicated by the 'upper layer parameter 'nrofReportedGroups', g) and the number of beams included in each beam combination (e.g., m). - Additional beam information 4) When the terminal simultaneously transmits all beams included in a beam combination, the terminal may determine a field for reporting the degree of overlap of beams in the beam combination to the base station as new additional beam information. If the terminal reports multiple beam combinations to the base station, the terminal may report a field, overlapping indicator (OI), along with PH to indicate the degree of overlap of multiple beams used for simultaneously transmitting each beam combination. For example, the OI may be as shown in Table 46. New FieldOverlapping0Non overlapping1Low overlapping2Medium overlapping3Fully overlapping Table 46 is only an example and the new field can consist of a larger or smaller number of bits than 2 bits, and the degree of overlap of the beams signified by each field can consist of information about the angular difference between the two beams other than Non, Low, Medium, and Fully (for example, the angular difference of the main lob of each beam is 136 to 180 degrees, 91 to 135 degrees, 46 to 90 degrees, and 0 to 45 degrees). In the same way as when the maximum transmit power is selected as the additional beam information, the terminal can report to the base station an additional field to report the degree of overlap of two beams mg considering both the number of reported beam combinations to report per serving cell (for example, the number of groups indicated by the 'higher layer parameter 'nrofReportedGroups', g) and the number of beams included in each beam combination (for example, m). In this way, a base station and a terminal can define a method for determining one of the various additional beam information (at least one of the additional beam information 1 to 4), so that the terminal can report the additional beam information together with the PH information when reporting a PH associated with a group-based beam report. To support this, a MAC CE format for PH reporting can be configured as follows. FIGS. 23a to 26b are MAC CE formats supplemented based on a single entry PHR MAC CE, but they can also be extended by supplementing based on a multiple entry PHR MAC CE instead of a single entry. FIG. 23a is an example of a PH MAC CE format for reporting, by a terminal, the maximum transmission power value of each beam combination to a base station together with PH information when the terminal determines the maximum transmission power of each beam combination as additional beam information according to additional beam information 1, and FIG. 23b is another example of a PH MAC CE format for reporting, by a terminal, the maximum transmission power value of each beam combination to a base station together with PH information when the terminal determines the maximum transmission power of each beam combination as additional beam information according to additional beam information 1. In Figs. 23a and 23b, it is assumed that 6 bits are used to report the maximum transmission power value per beam of each beam combination, and the PH MAC CE for PH reporting can be configured differently as in the cases of Figs. 23a and 23b (2300, 2310). The MAC CE format (2300) for the first PH transmission of Fig. 23a includes, as described above, a P field required to interpret the MPE field, a PH field for reporting the PH value, an MPE field, and a P field for reporting the maximum transmission power. CMAX,f,c P to report the maximum transmit power value per beam within all beam combinations of group-based beam reports associated with the corresponding PH report along with the field. CMAX,f,c The terminal may additionally include fields (2301 to 2308). Or, as shown in FIG. 23b, the terminal may perform PH reporting using the MAC CE format (2310) for the second PH transmission to reduce the bits of the reserved area (2309) included in the first PH MAC CE format (2300). Similar to the first PH MAC CE format (2300), the second PH MAC CE format (2310) may include a P field, a PH field for reporting a PH value, an MPE field, a P CMAX,f,cA field may be included, and in addition, a P field to report the maximum transmit power value per beam within all beam combinations of group-based beam reports associated with that PH report. CMAX,f,c Fields (2311 to 2318) may be arranged sequentially. The 6-bit fields (2301 to 2308 or 2311 to 2318) added to report the maximum transmission power value mean indicators for indicating the maximum transmission power when each corresponding beam is transmitted by the terminal, and the maximum transmission power value indicated by each indicator may be the same as the transmission power value of the terminal defined in the standard specification TS 38.133 as shown in Table 47 below, or may be defined as a separate new value as shown in Table 48 below. Reported valueMeasured quantity valueUnitPCMAX_C_00P CMAX,c,f < -29dBmPCMAX_C_01-29 ≤ P CMAX,c,f < -28dBmPCMAX_C_02-28 ≤ P CMAX,c,f < -27dBm......PCMAX_C_6131 ≤ P CMAX,c,f < 32dBmPCMAX_C_6232 ≤ P CMAX,c,f < 33dBmPCMAX_C_6333 ≤ P CMAX,c,f dBm Reported valueMeasured quantity valueUnitPCMAX_C_00P CMAX,c,f < X 1 dBmPCMAX_C_01X 1 ≤ P CMAX,c,f < X 2 dBmPCMAX_C_02X 2 ≤ P CMAX,c,f < X 3 dBm........PCMAX_C_61X 61 ≤ P CMAX,c,f < X 62 dBmPCMAX_C_62X 62 ≤ P CMAX,c,f < X 63 dBmPCMAX_C_63X63 ≤ P CMAX,c,f dBm The two MAC CE formats (2300, 2310) illustrated in FIGS. 23a and 23b are only examples, and other MAC CE formats may be configured to perform the same function, and the positions of each field may be different. In addition, FIGS. 23a and 23b are examples for the case where the base station reports a total of four beam combinations to the terminal by setting 'nrofReportedGroups' to 'n4', and if 'nrofReportedGroups' is set to a number other than 'n4' (for example, 'n2'), the terminal can configure a MAC CE format for reporting the set number of beam combinations and perform a PH report to the base station. FIG. 24a is an example of a PH MAC CE format for reporting, by a terminal, the PH values ​​for each beam combination to a base station together with existing PH information when the terminal determines the PH values ​​for each beam combination as additional beam information according to additional beam information 2, and FIG. 24b is another example of a PH MAC CE format for reporting, by a terminal, the PH values ​​for each beam combination to a base station together with existing PH information when the terminal determines the PH values ​​for each beam combination as additional beam information according to additional beam information 2. In Figs. 24a and 24b, it is assumed that 6 bits are used to report the PH value per beam of each beam combination, and the PH MAC CE for PH reporting can be configured differently as in Figs. 24a and 24b (2400, 2410). The MAC CE format (2400) for the first PH transmission of Fig. 24a includes a P field required for interpreting the MPE field as described above, a PH field for reporting the PH value, an MPE field, and a P field for reporting the maximum transmission power. CMAX,f,cIn addition to the field, the terminal may additionally include PH fields (2401 to 2408) for reporting PH values ​​per beam in all beam combinations of group-based beam reports associated with the PH report. Alternatively, as shown in FIG. 24b, the terminal may perform PH reporting using the MAC CE format (2410) for the second PH transmission to reduce the bits of the reserved area (2409) included in the first PH MAC CE format (2400). Similar to the first PH MAC CE format 2400, the second PH MAC CE format (2410) may include a P field, a PH field for reporting PH values, an MPE field, a P CMAX,f,c The field may be included, and in addition, PH fields (2411 to 2418) may be arranged sequentially to report beam-specific PH values ​​within all beam combinations of group-based beam reports associated with that PH report. The 6-bit fields (2401 to 2408 or 2411 to 2418) added to report the PH value are indicators for indicating the PH, which means the residual power when the terminal transmits each corresponding beam, and the PH value indicated by each indicator may be the same as the PH value defined in the standard specification TS 38.133 as shown in Table 49 below, or may be defined as a separate new value as shown in Table 50 below, for example. Reported valueMeasured quantity value (dB)POWER_HEADROOM_0PH < -32POWER_HEADROOM_1-32 ≤ PH < -31POWER_HEADROOM_2-31 ≤ PH < -30POWER_HEADROOM_3-30 ≤ PH < -29......POWER_HEADROOM_5320 ≤ PH < 21POWER_HEADROOM_5421 ≤ PH < 22POWER_HEADROOM_5522 ≤ PH < 24POWER_HEADROOM_5624 ≤ PH < 26POWER_HEADROOM_5726 ≤ PH < 28POWER_HEADROOM_5828 ≤ PH < 30POWER_HEADROOM_5930 ≤ PH < 32POWER_HEADROOM_6032 ≤ PH < 34POWER_HEADROOM_6134 ≤ PH < 36POWER_HEADROOM_6236 ≤ PH < 38POWER_HEADROOM_63PH ≥ 38 Reported valueMeasured quantity value (dB)POWER_HEADROOM_0PH < Y 1 POWER_HEADROOM_1Y 1 ≤ PH < Y 2 POWER_HEADROOM_2Y 2 ≤ PH < Y 3 POWER_HEADROOM_3Y 3 ≤ PH < Y 4 ......POWER_HEADROOM_53Y 53 ≤ PH < Y 54 POWER_HEADROOM_54Y 54 ≤ PH < Y 55 POWER_HEADROOM_55Y 55 ≤ PH < Y 56 POWER_HEADROOM_56Y 56 ≤ PH < Y 57 POWER_HEADROOM_57Y 57 ≤ PH < Y 58POWER_HEADROOM_58Y 58 ≤ PH < Y 59 POWER_HEADROOM_59Y 59 ≤ PH < Y 60 POWER_HEADROOM_60Y 60 ≤ PH < Y 61 POWER_HEADROOM_61Y 61 ≤ PH < Y 62 POWER_HEADROOM_62Y 62 ≤ PH < Y 63 POWER_HEADROOM_63PH ≥Y 63 The two MAC CE formats (2400, 2410) illustrated in FIGS. 24a and 24b are only examples, and other MAC CE formats may be configured to perform the same function, and the positions of each field may be different. In addition, FIGS. 24a and 24b are examples for the case where the base station reports a total of four beam combinations to the terminal by setting 'nrofReportedGroups' to 'n4', and if 'nrofReportedGroups' is set to a number other than 'n4' (for example, 'n2'), the terminal can configure a MAC CE format for reporting the set number of beam combinations and perform a PH report to the base station. FIG. 25a is an example of a PH MAC CE format for reporting, by a terminal, an MPE value for each beam of each beam combination to a base station together with PH information when the terminal determines an MPE determined for each beam of each beam combination as additional beam information according to additional beam information 3, and FIG. 25b is another example of a PH MAC CE format for reporting, by a terminal, an MPE value for each beam of each beam combination to a base station together with PH information when the terminal determines an MPE determined for each beam of each beam combination as additional beam information according to additional beam information 3. Assuming that 2 bits are used to report the beam-specific MPE value of each beam combination as in Fig. 25a, a PH MAC CE for PH reporting can be configured (2500). Alternatively, assuming that 4 bits are used to report the beam-specific MPE value of each beam combination as in Fig. 25b, a PH MAC CE can be configured (2510). The first PH MAC CE format (2500) of Figure 25a includes a P field required to interpret the MPE field as described above, a PH field for reporting the PH value, an MPE field, and a P field for reporting the maximum transmit power. CMAX,f,c In addition to the field, the MPE fields (2501 to 2508) each consisting of 2 bits may be additionally included to report the beam-specific MPE values ​​in all beam combinations of the group-based beam report associated with the corresponding PH report. Alternatively, as shown in FIG. 25b, the terminal may perform the PH report using the MAC CE format (2510) in which the MPE fields each consisting of 4 bits are configured to report the beam-specific MPE values ​​in all beam combinations of the group-based beam report associated with the corresponding PH report. Similar to the first PH MAC CE format (2500), the second PH MAC CE format (2510) may include a P field, a PH field for reporting the PH value, an MPE field, a P CMAX,f,c The field may be included, and additionally, MPE fields (2511 to 2518) each consisting of 4 bits may be included to report per-beam MPE values ​​within all beam combinations of group-based beam reports associated with the PH report. The 2-bit fields (2501 to 2508) added to report the MPE values ​​of FIG. 25a mean indicators for indicating the MPE values ​​applied to determine the maximum transmission power when the terminal transmits each corresponding beam, and the MPE values ​​indicated by each indicator may be the same as the P-MPR values ​​defined in the standard specification TS 38.133 as shown in Table 51 below, or, for example, a separate new value may be defined as shown in Table 52 below. Similarly, for the PH MAC CE format (2510) including the 4-bit fields (2511 to 2518) for reporting the MPE values ​​per beam in all beam combinations of FIG. 25b, the 4-bit MPE field may be used to report to the base station one of the multiple P-MPR values ​​included in the table for indicating a separate new P-MPR as shown in Table 53 below, for example. Reported valueMeasured quantity value (dB)P-MPR_003 ≤ P-MPR < 6P-MPR_016 ≤ P-MPR < 9P-MPR_029 ≤ P-MPR < 12P-MPR_03P-MPR ≥ 12 Reported valueMeasured quantity value (dB)P-MPR_00Z 0 ≤ P-MPR < Z 1 P-MPR_01Z 1 ≤ P-MPR < Z 2 P-MPR_02Z 2 ≤ P-MPR < Z 3 P-MPR_03P-MPR ≥ Z 3 Reported valueMeasured quantity value (dB)P-MPR_00Z 0 ≤ P-MPR < Z 1 P-MPR_01Z 1 ≤ P-MPR < Z 2 P-MPR_02Z 2 ≤ P-MPR < Z 3......P-MPR_14Z 14 ≤ P-MPR < Z 15 P-MPR_15P-MPR ≥ Z 15 The two MAC CE formats (2500, 2510) illustrated in FIGS. 25a and 25b are only examples, and other MAC CE formats may be configured to perform the same function, and the positions of each field may be different. In addition, FIGS. 25a and 25b are examples for the case where the base station reports a total of four beam combinations to the terminal by setting 'nrofReportedGroups' to 'n4', and if 'nrofReportedGroups' is set to a number other than 'n4' (for example, 'n2'), the terminal can configure a MAC CE format for reporting the set number of beam combinations and perform a PH report to the base station. FIG. 26a is an example of a PH MAC CE format for reporting, by a terminal, the degree of overlap of beams of each beam combination to a base station together with PH information when the terminal determines the degree of overlap of beams of each beam combination as additional beam information according to additional beam information 4, and FIG. 26b is another example of a PH MAC CE format for reporting, by a terminal, the degree of overlap of beams of each beam combination to a base station together with PH information when the terminal determines the degree of overlap of beams of each beam combination as additional beam information according to additional beam information 4. A new PH MAC CE format for PH reporting can be configured (2600) assuming that 2 bits are used to report the degree of overlap between beams of each beam combination as in Fig. 26a. Alternatively, a PH MAC CE can be configured (2610) for the case where 4 bits are used to report the degree of overlap between beams of each beam combination as in Fig. 26b. The first PH MAC CE format (2600) of Fig. 26a includes a P field required to interpret the MPE field as described above, a PH field for reporting a PH value, an MPE field, and a P field for reporting the maximum transmission power. CMAX,f,c In addition to the field, OI (overlapping indicator) fields (2601 to 2604) each consisting of 2 bits may be additionally included to report the degree of overlap between beams in all beam combinations of group-based beam reports associated with the corresponding PH report. Alternatively, as shown in FIG. 26b, the terminal may perform PH reporting using a MAC CE format (2610) in which OI fields each consisting of 4 bits are configured to report the degree of overlap between beams in all beam combinations of group-based beam reports associated with the corresponding PH report. Similar to the first PH MAC CE format (2610), the second PH MAC CE format (2610) may include a P field, a PH field for reporting a PH value, an MPE field, a P CMAX,f,c The field may be included, and additionally OI fields (2611 to 2614) each consisting of 4 bits may be included to report the degree of overlap between beams within all beam combinations of group-based beam reports associated with the PH report. The 2-bit fields (2601 to 2604) added to report the degree of overlap between beams within a beam combination represent indicators for indicating the degree of overlap between two beams when the terminal simultaneously transmits each corresponding beam combination, and the degree of overlap indicated by each indicator can be indicated as in Table 54 below, for example. Similarly, for the PH MAC CE format (2610) including 4-bit fields (2611 to 2614) for reporting the degree of overlap between beams within all beam combinations, the 4-bit OI field can be used to indicate one of 16 different degrees of overlap included in the table for indicating the degree of overlap as in Table 55 below and report it to the base station. When the angular difference values ​​between the main lobes of two beams are used to express the degree of overlap between the beams in the beam combination, the terminal may determine the OI field by referring to Tables 54 and 55, for example, and perform a PH report to the base station by including it in the PH MAC CE format. If OI expresses the degree of overlap between beams in a beam combination as in Table 46 described above, the terminal may determine the OI field by referring to Table 46 and perform a PH report to the base station by including it in the PH MAC CE format. At this time, the terminal may determine the degree of overlap (fully overlapping, medium overlapping, low overlapping, non overlapping) between beams according to the implementation of the terminal or the UE capability of the terminal (i.e., the terminal may arbitrarily determine it). Reported valueMeasured quantity value (degree)OI_00Angle 0 ≤ Overlapping angle < Angle 1 OI_01Angle 1 ≤ Overlapping angle < Angle 2 OI_02Angle2 ≤ Overlapping angle < Angle 3 OI_03Overlapping angle ≥ Angle 3 Reported valueMeasured quantity value (degree)OI_00Angle 0 ≤ Overlapping angle < Angle 1 OI _01Angle 1 ≤ Overlapping angle < Angle 2 OI _02Angle 2 ≤ Overlapping angle < Angle 3 ......OI _14Angle 14 ≤ Overlapping angle < Angle 15 OI_15Overlapping angle ≥ Angle 15 The two MAC CE formats (2600, 2610) illustrated in FIGS. 26a and 26b are only examples, and other MAC CE formats may be configured to perform the same function, and the positions of each field may be different. In addition, FIGS. 26a and 26b are examples for the case where the base station reports a total of four beam combinations to the terminal by setting 'nrofReportedGroups' to 'n4', and if 'nrofReportedGroups' is set to a number other than 'n4' (for example, 'n2'), the terminal can configure a MAC CE format for reporting the set number of beam combinations and perform a PH report to the base station. FIG. 27a is a diagram illustrating an example of operation of a terminal when supporting a power headroom-based multi-panel simultaneous transmission beam information reporting method according to the present disclosure. An operation of a terminal according to one embodiment of the present disclosure will be described (2700). The terminal can report the terminal capability to the base station (2701). At this time, the terminal can inform the base station whether it supports a multi-panel based simultaneous uplink / downlink channel transmission / reception technique through the terminal capability report, and can also inform the base station through the terminal capability report that it can support the power headroom based multi-panel simultaneous transmission beam information reporting method as described in the second embodiment. For example, the terminal can perform the terminal capability report to the base station by setting a certain parameter 'enablePHRforSTxMP' (or any other parameter name) to 'supported' or 'enable' or any value meaning that it can support. Thereafter, the terminal can receive RRC settings from the base station (2702). The RRC parameters set by the base station can include at least one of a parameter for supporting multi-panel simultaneous transmission and reception and an RRC parameter for supporting the power headroom-based multi-panel simultaneous transmission beam information reporting method described in the second embodiment (for example, the parameter can be 'PHRforSTxMP' or any other name). Thereafter, when a PHR triggering event occurs (2703) and the terminal performs a PH report, the terminal can perform an enhanced PH report including additional information for reporting the degree of overlap between beams to the base station (2704). The flowcharts described above illustrate exemplary methods that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts herein. For example, although illustrated as a series of steps, the various steps in each drawing may overlap, occur in parallel, occur in different orders, or occur multiple times. In other instances, steps may be omitted or replaced with other steps. FIG. 27b is a diagram illustrating an example of the operation of a base station when supporting a power headroom-based multi-panel simultaneous transmission beam information reporting method according to the present disclosure. An operation of a base station according to one embodiment of the present disclosure is described (2710). The base station can receive a terminal capability report from a terminal (2711). At this time, at least one of a terminal capability report on whether a multi-panel based uplink / downlink channel simultaneous transmission / reception technique can be supported and a terminal capability report on whether a power headroom based multi-panel simultaneous transmission beam information reporting method can be supported may be included. Thereafter, the base station can set RRC parameters based on the terminal capability report received from the terminal (2712). The base station can set parameters for supporting the multi-panel simultaneous transmission / reception technique and parameters for supporting the power headroom based multi-panel simultaneous transmission beam information reporting method to the terminal together. Thereafter, if the terminal performs PHR using PUSCH when a PHR triggering event occurs, the base station can receive the enhanced power headroom report transmitted by the terminal (2713). That is, the base station can receive power headroom information and additional information about the degree of overlap between beams in the beam combination through the power headroom report transmitted by the terminal. Based on the received power headroom information and the additional information about the degree of overlap between beams in the beam combination, the base station can support a multi-panel simult...

Claims

1. In a method performed by a terminal of a communication system, A step of receiving setup information for reporting additional beam-related information for simultaneous transmission using multiple panels from a base station; and Comprising a step of transmitting the additional beam related information to the base station, A method characterized in that the above additional beam-related information is transmitted by being included in a PHR (power headroom report) MAC CE (medium access control control element) or transmitted by being included in a CSI (channel state information) report.

2. In paragraph 1, If the above additional beam information is transmitted by being included in the PHR MAC CE, A method characterized in that the additional beam information is at least one of: maximum transmission power information for each beam combination that the terminal can report, power headroom information for each beam combination that the terminal can report, maximum permissible exposure (MPE) information for each beam combination that the terminal can report, or information indicating the degree of overlap of multiple beams for each beam combination that the terminal can report.

3. In paragraph 1, If the above additional beam information is transmitted as included in the above CSI report, A method characterized in that the additional beam information is at least one of RSRP (received signal received power) information for a beam combination included in the CSI report or information indicating the degree of overlap of multiple beams of the beam combination.

4. In paragraph 1, A method characterized by further comprising the step of transmitting terminal capability information capable of supporting the additional beam related information reporting for the simultaneous transmission using the multi-panel to the base station.

5. In a method performed by a base station of a communication system, A step for transmitting setting information for reporting additional beam-related information for simultaneous transmission using multiple panels to a terminal; and Comprising a step of receiving the additional beam related information from the terminal, A method characterized in that the above additional beam-related information is received by being included in a PHR (power headroom report) MAC CE (medium access control control element) or a CSI (channel state information) report.

6. In paragraph 5, If the above additional beam information is received and included in the PHR MAC CE, A method characterized in that the additional beam information is at least one of: maximum transmission power information for each beam combination that the terminal can report, power headroom information for each beam combination that the terminal can report, maximum permissible exposure (MPE) information for each beam combination that the terminal can report, or information indicating the degree of overlap of multiple beams for each beam combination that the terminal can report.

7. In paragraph 5, If the above additional beam information is received as included in the above CSI report, A method characterized in that the additional beam information is at least one of RSRP (received signal received power) information for a beam combination included in the CSI report or information indicating the degree of overlap of multiple beams of the beam combination.

8. In paragraph 5, A method characterized by further comprising the step of receiving terminal capability information capable of supporting reporting of additional beam-related information for the simultaneous transmission using the multi-panel from the terminal.

9. At the terminal of the communication system, Transmitter and receiver; and Receives setup information for reporting additional beam-related information for simultaneous transmission using multiple panels from a base station, Including a control unit set to transmit the additional beam related information to the base station, A terminal characterized in that the above additional beam-related information is transmitted by being included in a PHR (power headroom report) MAC CE (medium access control control element) or transmitted by being included in a CSI (channel state information) report.

10. In paragraph 9, If the above additional beam information is transmitted by being included in the PHR MAC CE, A terminal characterized in that the additional beam information is at least one of: maximum transmission power information for each beam combination that the terminal can report, power headroom information for each beam combination that the terminal can report, maximum permissible exposure (MPE) information for each beam combination that the terminal can report, or information indicating the degree of overlap of multiple beams for each beam combination that the terminal can report.

11. In paragraph 9, If the above additional beam information is transmitted as included in the above CSI report, A terminal characterized in that the additional beam information is at least one of RSRP (received signal received power) information for a beam combination included in the CSI report or information indicating the degree of overlap of multiple beams of the beam combination.

12. In paragraph 9, A terminal characterized in that the control unit is further set to transmit terminal capability information capable of supporting reporting of additional beam related information for simultaneous transmission using the multi-panel to the base station.

13. In the base station of the communication system, Transmitter and receiver; and Transmits configuration information for reporting additional beam-related information for simultaneous transmission using multiple panels to the terminal, Including a control unit set to receive the additional beam related information from the terminal, A base station characterized in that the above additional beam-related information is received by being included in a PHR (power headroom report) MAC CE (medium access control control element) or a CSI (channel state information) report.

14. In paragraph 13, If the above additional beam information is received and included in the PHR MAC CE, A base station, characterized in that the additional beam information is at least one of: maximum transmission power information for each beam combination that the terminal can report; power headroom information for each beam combination that the terminal can report; maximum permissible exposure (MPE) information for each beam combination that the terminal can report; or information indicating the degree of overlap of multiple beams for each beam combination that the terminal can report.

15. In paragraph 13, If the above additional beam information is received as included in the above CSI report, A base station, characterized in that the additional beam information is at least one of RSRP (received signal received power) information for a beam combination included in the CSI report or information indicating the degree of overlap of multiple beams of the beam combination.

Images