Power headroom reporting method and device for uplink-only base station in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. More particularly, the present disclosure relates to a method performed by a terminal in a wireless communication system, the method comprising the steps of: receiving downlink control information (DCI) for scheduling resources for transmitting a first physical uplink shared channel (PUSCH) related to a first transmission and reception point (TRP) for uplink transmission and downlink reception of the terminal and a second PUSCH related to a second TRP for only uplink transmission of the terminal; and transmitting a power headroom report (PHR) including a first PHR related to the first PUSCH and / or a second PHR related to the second PUSCH, wherein the first PHR is calculated on the basis of a downlink path loss calculated using a reference signal, the second PHR is calculated on the basis of the downlink path loss and a path loss offset, both the first PHR and the second PHR are configured to be transmitted, both the first PUSCH and the second PUSCH are transmitted in slot n in which the PHR is transmitted, and, when the first PUSCH is scheduled at a time point earlier than that of the second PUSCH, the PHR including the first PHR calculated on the basis of actual transmission of the first PUSCH and the second PHR calculated on the basis of actual transmission of the second PUSCH can be transmitted.

Description

Power headroom reporting method and device for an uplink-only base station in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a power headroom reporting method for supporting an uplink-only base station (UL-only TRP) in network cooperative communications, and a device capable of performing the same.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) 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 latency time that is reduced to one-tenth.

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

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

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

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

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

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

[0009] The present disclosure, for solving the above problems, is a method performed by a terminal in a wireless communication system, the method comprising: receiving downlink control information (DCI) for scheduling resources for transmitting a first physical uplink shared channel (PUSCH) associated with a first transmission and reception point (TRP) for uplink transmission and downlink reception of the terminal and a second PUSCH associated with a second TRP for only uplink transmission of the terminal; And a step of transmitting a PHR including at least one of a first power headroom report (PHR) related to the first PUSCH or a second PHR related to the second PUSCH, wherein the first PHR is calculated based on downlink path loss calculated using a reference signal, and the second PHR is calculated based on the downlink path loss and a path loss offset, and wherein both the first PHR and the second PHR are configured to be transmitted, and both the first PUSCH and the second PUSCH are transmitted in slot n in which the PHR is transmitted, and when the first PUSCH is scheduled at an earlier time than the second PUSCH, the PHR including the first PHR calculated based on actual transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH may be transmitted.

[0010] A method performed by a base station in a wireless communication system, the method comprising: transmitting downlink control information (DCI) scheduling resources for transmitting a first physical uplink shared channel (PUSCH) associated with a first transmission and reception point (TRP) for uplink transmission and downlink reception of a terminal and a second PUSCH associated with a second TRP for only uplink transmission of the terminal; And a step of receiving a PHR including at least one of a first power headroom report (PHR) associated with the first PUSCH or a second PHR associated with the second PUSCH, wherein the first PHR is calculated based on downlink path loss calculated using a reference signal, and the second PHR is calculated based on the downlink path loss and a path loss offset, wherein both the first PHR and the second PHR are configured to be transmitted, and both the first PUSCH and the second PUSCH are transmitted in slot n in which the PHR is transmitted, and when the first PUSCH is scheduled at an earlier time than the second PUSCH, the PHR including the first PHR calculated based on actual transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH may be transmitted.

[0011] In a wireless communication system, a terminal comprises: a transceiver; And a controller connected to the transceiver, wherein the controller receives downlink control information (DCI) for scheduling resources for transmitting a first physical uplink shared channel (PUSCH) associated with a first transmission and reception point (TRP) for uplink transmission and downlink reception of the terminal and a second PUSCH associated with a second TRP for only uplink transmission of the terminal, and is configured to transmit a PHR including at least one of a first power headroom report (PHR) associated with the first PUSCH or a second PHR associated with the second PUSCH, wherein the first PHR is calculated based on downlink path loss calculated using a reference signal, and the second PHR is calculated based on the downlink path loss and path loss offset, and both the first PHR and the second PHR are configured to be transmitted, and both the first PUSCH and the second PUSCH are configured to be transmitted. The PHR may be transmitted in slot n in which the PHR is transmitted, and when the first PUSCH is scheduled at an earlier time than the second PUSCH, the PHR may be transmitted including the first PHR calculated based on actual transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH.

[0012] In a wireless communication system, a base station comprises: a transceiver; and a controller connected to the transceiver, wherein the controller transmits downlink control information (DCI) scheduling resources for transmitting a first physical uplink shared channel (PUSCH) associated with a first transmission and reception point (TRP) for uplink transmission and downlink reception of a terminal and a second PUSCH associated with a second TRP for only uplink transmission of the terminal; And a step of receiving a PHR including at least one of a first power headroom report (PHR) associated with the first PUSCH or a second PHR associated with the second PUSCH, wherein the first PHR is calculated based on downlink path loss calculated using a reference signal, and the second PHR is calculated based on the downlink path loss and a path loss offset, wherein both the first PHR and the second PHR are configured to be transmitted, and both the first PUSCH and the second PUSCH are transmitted in slot n in which the PHR is transmitted, and when the first PUSCH is scheduled at an earlier time than the second PUSCH, the PHR including the first PHR calculated based on actual transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH may be transmitted.

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

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

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

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

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

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

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

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

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

[0022] Figure 9 illustrates a process for beam setting and activation of PDSCH.

[0023] FIG. 10 is a diagram illustrating an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to one embodiment of the present disclosure.

[0024] FIG. 11 is a diagram illustrating an example of configuring downlink control information (DCI) for cooperative communication in a wireless communication system according to one embodiment of the present disclosure.

[0025] Figure 12 is a diagram showing the Enhanced PDSCH TCI state activation / deactivation MAC-CE structure.

[0026] FIG. 13 is a diagram illustrating an example of the operation of a base station and a terminal operating in multiple TRPs, including a TRP that supports only an uplink reception function according to one embodiment of the present disclosure.

[0027] FIG. 14 is a diagram illustrating an example of the operation of a base station and a mobile terminal operating with multiple TRPs, including UL only TRP, according to one embodiment of the present disclosure.

[0028] FIGS. 15A to 15D illustrate examples of a terminal reporting triggered power headroom to a base station using DCI-based Dynamic grant PUSCH resources for a single carrier according to one embodiment of the present disclosure.

[0029] FIG. 16 illustrates an example of an enhanced MAC CE format with an additional field for indicating the type of TRP associated with each power headroom region when twoPHRMode is supported according to one embodiment of the present disclosure.

[0030] FIG. 17 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0031] FIG. 18 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

[0039] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

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

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

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

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

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

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

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

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

[0048] [NR time-frequency resources]

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

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

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

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

[0053] Figure 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 10ms. One subframe (201) can be defined as 1ms, 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 an example of FIG. 2, 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, the number of slots per 1 subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ and can be defined as [Table 1] below.

[0054] μ 0141011142022144043148084141601651432032

[0055] [Bandwidth Part (BWP)]

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

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

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

[0059]

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

[0061] According to some embodiments, a terminal before RRC connection can 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 can receive configuration information about a control resource set (CORESET) and a search space in which a PDCCH for receiving system information required for initial access (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) and search space can be transmitted through the MIB during the initial access phase. The control space and search space configured by the MIB can each be regarded as identifier (ID) 0. The base station can notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for control space #0 through the MIB. Additionally, the base station can notify the terminal of the monitoring cycle and monitoring occasion settings for control area #0, i.e., search space #0, via the MIB. The terminal can consider the frequency range set as control area #0 obtained from the MIB as the initial bandwidth portion for initial access. At this time, the identifier (ID) of the initial bandwidth portion can be considered as 0.

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

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

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

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

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

[0067] [Bandwidth Part (BWP) Change]

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

[0069] As described above, since DCI-based bandwidth part change can be indicated by DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth part change request, it must be able to receive or transmit PDSCH or PUSCH scheduled by the corresponding DCI without difficulty in the changed bandwidth part. To this end, the standard stipulates the delay time (T) required when changing the bandwidth part. BWP ) and can be defined as in [Table 3] below, for example.

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

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

[0072] According to the requirement for bandwidth part change delay time mentioned above, when the terminal receives DCI including bandwidth part change indicator in slot n, the terminal changes to the new bandwidth part indicated by the bandwidth part change indicator in slot n+T. BWPThe completion can be done at a later time, and transmission and reception for the data channel scheduled by the DCI can be performed in the new bandwidth portion that has been changed. When the base station wants to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP ), time domain resource allocation for the data channel can be determined. That is, when the base station schedules the data channel with a new bandwidth portion, the data channel can be scheduled after the bandwidth portion change delay time in the method of determining the time domain resource allocation for the data channel. Accordingly, the terminal can determine whether the DCI instructing the bandwidth portion change is after the bandwidth portion change delay time (T BWP ) may not be expected to indicate a slot offset (K0 or K2) value smaller than that.

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

[0074] [CA / DC related]

[0075] FIG. 4 is a diagram illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation according to one embodiment of the present disclosure.

[0076] Referring to FIG. 4, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (Service Data Adaptation Protocol S25, S70), NR PDCP (Packet Data Convergence Protocol S30, S65), NR RLC (Radio Link Control S35, S60), and NR MAC (Medium Access Control S40, S55) in the terminal and NR base station, respectively.

[0077] Key features of NR SDAP (S25, S70) may include some of the following:

[0078] - Transfer of user plane data

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

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

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

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

[0083] The main functions of NR PDCP (S30, S65) may include some of the following functions:

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

[0085] - User data transfer function

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

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

[0088] - PDCP PDU reordering for reception

[0089] - Duplicate detection of lower layer SDUs

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

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

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

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

[0094] The main functions of NR RLC (S35, S60) may include some of the following functions:

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

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

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

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

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

[0100] - Re-segmentation of RLC data PDUs

[0101] - Reordering of RLC data PDUs

[0102] - Duplicate detection function

[0103] - Protocol error detection

[0104] - RLC SDU discard function

[0105] - RLC re-establishment function

[0106] In the above, the in-sequence delivery function of the NR RLC device refers to the function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering a single RLC SDU when it is received divided into multiple RLC SDUs, a function of rearranging received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number), a function of recording lost RLC PDUs by rearranging the order, a function of reporting the status of lost RLC PDUs to the transmitting side, and a function of requesting retransmission of lost RLC PDUs. The in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer only the RLC SDUs up to the lost RLC SDU when there is a lost RLC SDU, or may include a function to sequentially deliver to the upper layer all RLC SDUs received before the timer starts if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer all RLC SDUs received up to the present if a predetermined timer has expired even if there is a lost RLC SDU.In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the order of the sequence number) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, the segments stored in the buffer or to be received later may be received, reconstructed into a complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

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

[0108] NR MAC (S40, S55) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions.

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

[0110] - Multiplexing / demultiplexing of MAC SDUs

[0111] - Scheduling information reporting function

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

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

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

[0115] - MBMS service identification function

[0116] - Transport format selection function

[0117] - Padding function

[0118] The NR PHY layer (S45, S50) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it over a wireless channel, or demodulating and channel decoding OFDM symbols received over a wireless channel and transmitting them to a higher layer.

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

[0120] [Unified TCI state]

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

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

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

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

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

[0126] Among the separate TCI states, the UL TCI state can be set to a maximum of 32 or 64 upper layer signaling for each specific bandwidth part within a specific cell based on the terminal capability report, and like the relationship between the DL TCI state and the joint TCI state among the separate TCI states, the UL TCI state and the joint TCI state among the separate TCI can also use the same upper layer signaling structure, and the UL TCI state among the separate TCI can use different upper layer signaling structures from the joint TCI state and the DL TCI state among the separate TCI states.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0140] 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).

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

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

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

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

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

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

[0147] [Unified TCI state MAC-CE]

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

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

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

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

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

[0153] - Pi (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 the value of Pi is 1, it means that the corresponding ith 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 the value of Pi is 0, it means that the corresponding ith code point has a single TCI state, which may mean that the corresponding code point may include either a joint TCI state, a separate DCI TCI state, or a separate UL TCI state.

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

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

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

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

[0158] [PDCCH: DCI related]

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

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

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

[0162] 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).

[0163] 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 4] below.

[0164]

[0165] 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 5] below.

[0166]

[0167]

[0168] 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 6] below.

[0169]

[0170] 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 7] below.

[0171]

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

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

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

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

[0176]

[0177] In [Table 8], the tci-StatesPDCCH (simply named TCI (Transmission Configuration Indication) state) configuration information may include information on one or more SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) block indices or CSI-RS (Channel State Information Reference Signal) indices that are in a QCL (Quasi Co Located) relationship with the DMRS transmitted in the corresponding control region.

[0178] FIG. 8 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G. According to FIG. 8, the basic unit of time and frequency resources that constitute a control channel can be referred to as a REG (Resource Element Group, 803), and a REG (803) can be defined as 1 OFDM symbol (801) on the time axis and 1 PRB (Physical Resource Block, 802) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (803) to constitute a downlink control channel allocation unit.

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

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

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

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

[0183]

[0184]

[0185] Depending on the configuration information, the base station may configure one or more search space sets for the terminal. In some embodiments, the base station may configure search space set 1 and search space set 2 for the terminal, and may configure the terminal to monitor DCI format A scrambled with X-RNTI in search space set 1 in a common search space, and may configure the terminal to monitor DCI format B scrambled with Y-RNTI in search space set 2 in a terminal-specific search space.

[0186] According to the configuration information, one or more search space sets may exist in a common search space or a terminal-specific search space. For example, search space set #1 and search space set #2 may be configured as a common search space, and search space set #3 and search space set #4 may be configured as terminal-specific search spaces.

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

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

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

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

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

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

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

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

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

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

[0197] C-RNTI (Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0198] TC-RNTI (Temporary Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0199] CS-RNTI (Configured Scheduling RNTI): Used for terminal-specific PDSCH scheduling that is set semi-statically.

[0200] RA-RNTI (Random Access RNTI): Used for PDSCH scheduling in the random access phase.

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

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

[0203] INT-RNTI (Interruption RNTI): Used to indicate whether pucturing is in progress for PDSCH.

[0204] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to indicate power control commands for PUSCH.

[0205] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to indicate power control commands for PUCCH.

[0206] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to indicate power control commands for SRS.

[0207] The aforementioned specified DCI formats may follow the definitions in [Table 10] below.

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

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

[0210] [Mathematical Formula 1]

[0211]

[0212] The value can be 0 for a common search space.

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

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

[0215] [PUCCH: Transmission Related]

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

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

[0218] More specifically, Long PUCCH can be used for uplink cell coverage enhancement purposes, and thus can be transmitted using DFT-S-OFDM, a single-carrier transmission method, rather than OFDM transmission. Long PUCCH supports transmission formats such as PUCCH format 1, PUCCH format 3, and PUCCH format 4, depending on the number of control information bits that can be supported and whether terminal multiplexing is supported through Pre-DFT OCC support in front of the IFFT.

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

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

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

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

[0223] w i (m) is the length of the spreading code (NSF) given It is determined as follows, and is specifically given as in [Table 11]. 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 11] mean φ(m), and for example, if the length of the spreading code is 2 and the index of the set spreading code is i=0, the spreading code w i (m) is , This is w i (m)=

[0011] .

[0224]

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

[0226]

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

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

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

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

[0231] 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 13] below, and can generate the final CS by adding 0 to the initial CS if it is NACK. The CS value 0 for NACK and the CS value 6 for ACK are defined in the standard, and the terminal can transmit 1-bit HARQ-ACK by generating PUCCH format 0 according to the values ​​defined in the standard.

[0232]

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

[0234]

[0235] Next, PUCCH format 2 is a short PUCCH format that supports control information exceeding 2 bits, and the number of RBs used can be set through a higher layer. The control information can be composed of a combination of HARQ-ACK, SR, and CSI, or each of them. When the index of the first subcarrier is #0, the location of the subcarrier where the DMRS is transmitted within one OFDM symbol in PUCCH format 2 can be fixed to the subcarriers with indices of #1, #4, #7, and #10. The control information can be mapped to the remaining subcarriers except for the subcarrier where the DMRS is located through a modulation process after channel coding.

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

[0237]

[0238] Meanwhile, to improve uplink coverage, multi-slot repetition can be supported for PUCCH formats 1, 3, and 4, and PUCCH repetition can be configured for each PUCCH format. The UE can perform repeated transmissions on PUCCH including UCI as many slots as configured through the higher layer signaling nrofSlots. For repeated PUCCH transmissions, PUCCH transmissions in each slot are performed using the same number of consecutive symbols, and the corresponding number of consecutive symbols can be configured through nrofSymbols in the higher layer signaling PUCCH-format1, PUCCH-format3, or PUCCH-format4. For repeated PUCCH transmissions, PUCCH transmissions in each slot are performed using the same starting symbol, and the corresponding starting symbol can be configured through startingSymbolIndex in the higher layer signaling PUCCH-format 1, PUCCH-format 3, or PUCCH-format 4. For repeated PUCCH transmissions, a single PUCCH-spatialRelationInfo can be configured for a single PUCCH resource. For repeated PUCCH transmissions, if the UE is configured to perform frequency hopping in PUCCH transmissions in different slots, the UE can perform frequency hopping on a slot-by-slot basis. In addition, if the UE is configured to perform frequency hopping in PUCCH transmissions in different slots, the UE can start PUCCH transmission from the first PRB index configured through the higher layer signaling startingPRB in even slots, and start PUCCH transmission from the second PRB index configured through the 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 instructed to perform the first PUCCH transmission to the terminal is 0, and the number of PUCCH repetitions may increase regardless of the PUCCH transmission performed in each slot during the configured total number of PUCCH repetitions. If the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the terminal does not expect frequency hopping to be configured within a slot when transmitting PUCCH. If the terminal is not configured to perform frequency hopping in PUCCH transmissions in different slots but is configured to perform frequency hopping within a slot, the first and second PRB indices may be applied equally within the slot. If the number of uplink symbols available for PUCCH transmission is less than nrofSymbols configured by higher layer signaling, the terminal may not transmit the PUCCH. Even if the terminal fails to transmit PUCCH in a slot for some reason during PUCCH repetition transmission, the terminal can increase the number of PUCCH repetition transmissions.

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

[0240] [PUCCH: Transmission Power Related]

[0241] In one embodiment of the present disclosure, when uplink control information is transmitted through an uplink control channel (PUCCH; Physical Uplink Control Channel) in response to a power control command received from a base station, a method for transmitting by setting the transmission power of the uplink control channel by a terminal is described. The method comprises: a PUCCH power control adjustment state corresponding to the i-th transmission unit, a closed loop index l, and an uplink control channel transmission power (P) of the terminal. PUCCH ) can be determined as shown in [Mathematical Formula 2] below, which is expressed in dBm units. In [Mathematical Formula 2] below, when a terminal supports multiple carrier frequencies in multiple cells, each parameter can be determined for each primary cell c, carrier frequency f, and bandwidth part b, and can be distinguished by indices b, f, and c.

[0242] [Equation 2]

[0243]

[0244] P CMAX,f,c (i): The maximum transmission power available to the terminal in the i-th transmission unit is determined by the power class of the terminal, parameters activated from the base station, and various parameters built into the terminal.

[0245] P 0_PUCCH,b,f,c (q u ): P 0_PUCCH,b,f,c (q u ) is P 0_NOMINAL_PUCCH Wow P 0_UE_PUCCH (q u ) can be composed of the sum of P 0_NOMINAL_PUCCH is set via p0-nominal, a Cell Specific upper layer signaling with a cell-specific value, and if there is no such setting, P 0_NOMINAL_PUCCH can be 0 dBm. P0_UE_PUCCH (q u ) is set through p0-PUCCH-Value in upper layer signaling p0-PUCCH in primary cell c, bandwidth part b, carrier frequency f, and terminal-specific value, q u is greater than or equal to 0 and Q u It can be a smaller value than Q u is P 0_UE_PUCCH It can mean the size of the set of values ​​and can be set via the upper layer signaling maxNrofPUCCH-P0-PerSet. P 0_UE_PUCCH A set of values ​​can be set via the upper layer signaling p0-Set, or if there is no such set = can be considered as 0.

[0246] -μ: Subcarrier spacing configuration value

[0247] - : It may mean the bandwidth part b, the carrier frequency f, and the amount of resources used in the ith PUCCH transmission unit within the primary cell c (e.g., the number of Resource Blocks (RBs) used for PUCCH transmission on the frequency axis).

[0248] - PL b,f,c (q d ): Pathloss is the path loss that indicates the path loss between the base station and the terminal. The terminal uses the reference signal (RS) resource q signaled by the base station. d Path loss is calculated from the difference between the transmission power and the terminal reception signal level of the reference signal.

[0249] - Δ F_PUCCH(F): For PUCCH format 0, if deltaF-PUCCH-f0, which is an upper layer signaling, is set, the corresponding value is used. For PUCCH format 1, if deltaF-PUCCH-f1, which is an upper layer signaling, is set, the corresponding value is used. For PUCCH format 2, if deltaF-PUCCH-f2, which is an upper layer signaling, is set, the corresponding value is used. For PUCCH format 3, if deltaF-PUCCH-f3, which is an upper layer signaling, is set, the corresponding value is used. For PUCCH format 4, if deltaF-PUCCH-f4, which is an upper layer signaling, is set, the corresponding value is used. For all PUCCH formats, if no upper layer signaling is set, 0 can be used.

[0250] - Δ TF,b,f,c (i): Bandwidth part b, carrier frequency f, PUCCH transmission power adjustment factor within primary cell c, different calculation methods can be used depending on the PUCCH format.

[0251] - g b,f,c (i,l): This may refer to a PUCCH power control adjustment state value for the i-th PUCCH transmission unit corresponding to the closed loop index l within the bandwidth part b, carrier frequency f, and primary cell c. Here, the closed loop power adjustment for PUCCH transmission may use an accumulation method that accumulates and applies a value indicated by a TPC command.

[0252] PUCCH power control adjustment state g b,f,c (i,l) can be determined through the bandwidth part b, carrier frequency f, primary cell c, i-th transmission unit, and closed loop index l.

[0253] - δPUCCH,b,f,c(i,l): A value indicated by a TPC command field included in DCI format 1_0, 1_1, or 1_2 that schedules the i-th PUCCH transmission unit and PDSCH reception corresponding to the closed loop index l within bandwidth part b, carrier frequency f, and primary cell c, or a value indicated by a TPC command field included in DCI format 2_2 transmitted together with a CRC scrambled with TPC-PUCCH-RNTI.

[0254] ○ If the terminal has received upper layer signaling of twoPUCCH-PC-AdjustmentStates and PUCCH-SpatialRelationInfo, the closed loop index l can have a value of 0 or 1.

[0255] ○ If the terminal does not receive the upper layer signaling twoPUSCH-PC-AdjustmentStates or PUCCH-SpatialRelationInfo, the closed loop index l may have a value of 0.

[0256] ○ If the terminal obtains a TPC command value through a TPC command field included in DCI format 1_0, 1_1, or 1_2 that schedules PDSCH reception, and the terminal has been configured with PUCCH-SpatialRelationInfo, which is an upper layer signaling, the terminal can obtain a connection relationship between the pucch-SpatialRelationInfoId value and the closedLoopIndex value that sets a closed loop index value based on an index that can be configured through p0-PUCCH-Id, which is an upper layer signaling. If the terminal has received a MAC-CE corresponding to pucch-SpatialRelationInfoId, the terminal can determine the closedLoopIndex value that sets a closed loop index value based on the corresponding p0-PUCCH-Id index.

[0257] ○ If the terminal obtains one TPC command value from the TPC command field included in the DCI format 2_2 transmitted with the CRC scrambled with TPC-PUCCH-RNTI, the l value can be obtained based on the closed loop index field included in the DCI format 2_2.

[0258] - PUCCH power control adjustment state g for the i-th PUCCH transmission unit corresponding to the closed loop index l within the bandwidth part b, carrier frequency f, and primary cell c. b,f,c (i,l) can be calculated as in [Mathematical Formula 3].

[0259] [Equation 3]

[0260]

[0261] ○ δPUCCH,b,f,c(m,l) may be a value indicated by a TPC command field included in DCI format 1_0, 1_1 or 1_2 that schedules the m-th PUCCH transmission unit and PDSCH reception corresponding to the closed loop index l within the bandwidth part b, the carrier frequency f and the primary cell c as described above, or may be a value indicated by a TPC command field included in DCI format 2_2 transmitted together with a CRC scrambled with TPC-PUCCH-RNTI. When TPC command accumulation operation is possible, the δPUCCH,b,f,c value may have a corresponding value in [dB] units depending on which value the TPC command field included in DCI format 1_0, 1_1, 1_2 or 2_2 is indicated with, as shown in [Table 18]. For example, if the value of the TPC command field is 0, δPUCCH,b,f,c may have a value of -1 dB.

[0262] ○ is a specific set C of TPC command values ​​described above. iIt can mean the sum of δPUCCH,b,f,c for all transmission units corresponding to it. In this case, c(C i ) is a set C i It can mean the number of all elements belonging to C i may mean a set of DCIs containing all TPC command values ​​for performing TPC command accumulation operation for the i-th PUCCH transmission unit. C i To determine the starting point and the ending point in the time dimension, all DCIs received by the terminal within the two points are defined as C. i can be included as an element of .

[0263] ● C i The end point for determining is K from the start symbol of the i-th PUCCH transmission unit. PUCCH (i) It can be a point as far back as the symbol.

[0264] ● C i The starting point for determining is K from the starting symbol of the i-i0th PUCCH transmission unit. PUCCH It can be a point that is as far back as (i-i0)-1 symbols. In this case, i0, which is a positive integer, is the C i The end point for determining (K from the start symbol of the i-th PUCCH transmission unit) PUCCH (i) from the starting symbol of the i-i0th PUCCH transmission unit, K symbols earlier than the previous point. PUCCH It can be determined as the smallest value that satisfies that the time point that is earlier than (i-i0) symbols becomes an earlier time point in time.

[0265] ● For example, C i The end point for determining can be defined as sym(i), and K is defined as the starting symbol of the i-i0th PUCCH transmission unit. PUCCHIf the time point prior to (i-i0) symbols can be defined as sym(i-i0), then if sym(i) = sym(i-1) > sym(i- 2) > sym(i-3) holds, then i0 can be determined as 2.

[0266] [PUSCH: Transmission method related]

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

[0268] Configured grant Type 1 PUSCH transmission can be semi-statically configured by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of [Table 16] through higher-order signaling, without receiving UL grant in DCI. Configured grant Type 2 PUSCH transmission can be semi-persistently scheduled by UL grant in DCI after receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant of [Table 16] through higher-order signaling. When PUSCH transmission operates by configured grant, parameters applied to PUSCH transmission are applied through configuredGrantConfig of higher-order signaling of [Table 16], except dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, scaling of UCI-OnPUSCH provided by pusch-Config of [Table 17]. If the terminal has been provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 16], the terminal applies tp-pi2BPSK in pusch-Config of [Table 17] to PUSCH transmission operated by the configured grant.

[0269]

[0270]

[0271] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission is the same as the antenna port for SRS transmission. PUSCH transmission can follow a codebook-based or non-codebook-based transmission method, respectively, depending on whether the value of txConfig in the upper signaling, pusch-Config in [Table 17], is 'codebook' or 'nonCodebook'.

[0272] 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 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 does not configure txConfig in pusch-Config of [Table 17], the UE does not expect to be scheduled with DCI format 0_1.

[0273]

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

[0275] At this time, the SRI can be given through the SRS resource indicator field in the DCI or configured through the srs-ResourceIndicator higher-level signaling. The UE is configured with at least one SRS resource when transmitting a codebook-based PUSCH, and can be configured with up to two. When the UE receives an SRI through the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. In addition, the TPMI and transmission rank can be given through the precoding information and number of layers fields in the DCI or configured through the precodingAndNumberOfLayers higher-level signaling. The TPMI is used to indicate the precoder applied to the PUSCH transmission. If the UE is configured with one SRS resource, the TPMI is used to indicate the precoder to be applied to the configured 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.

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

[0277] The terminal can be configured with one SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource in the SRS resource set can be indicated via SRI. If multiple SRS resources are configured in the SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', the terminal expects that the value of nrofSRS-Ports in the upper signaling SRS-Resource is set to the same value for all SRS resources.

[0278] 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 the 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.

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

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

[0281] 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, the presence of the connected NZP CSI-RS is indicated when the value of the SRS request field 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 the SRS request indicates the presence of an NZP CSI-RS, the NZP CSI-RS is located in the slot in which the PDCCH including the SRS request field is transmitted. At this time, the TCI states set for the scheduled subcarriers are not set to QCL-TypeD.

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

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

[0284] The base station transmits one NZP-CSI-RS associated with an SRS resource set to the terminal, and the terminal calculates a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the result measured upon reception of the NZP-CSI-RS. When the terminal transmits one or more SRS resources within the SRS resource set with usage set to 'nonCodebook' to the base station, the terminal applies the calculated precoder, and the base station selects one or more SRS resources from the received one or more SRS resources. At this time, in non-codebook based PUSCH transmission, the SRI represents an index that can express a combination of one or more SRS resources, and the SRI is included in the DCI. 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 to each layer.

[0285] [PUSCH: Transmission Power Related]

[0286] In one embodiment of the present disclosure, when uplink data is transmitted through an uplink data channel (PUSCH; Physical Uplink Shared Channel) in response to a power control command received from a base station, a method for transmitting by setting the transmission power of the uplink data channel by a terminal is described. The uplink data channel transmission power of the terminal can be determined as shown in [Mathematical Formula 4] below, expressed in units of dBm, together with the i-th transmission unit, the parameter set configuration index j, and the PUSCH power control adjustment state corresponding to the closed loop index l. In [Mathematical Formula 4] below, when the terminal supports multiple carrier frequencies in multiple cells, each parameter can be set for each cell c, each carrier frequency f, and each bandwidth part b, and can be distinguished by indices b, f, and c.

[0287] [Equation 4]

[0288]

[0289] P CMAX,f,c (i): The maximum transmission power available to the terminal in the i-th transmission unit is determined by the power class of the terminal, parameters activated from the base station, and various parameters built into the terminal.

[0290] P 0_PUSCH,b,f,c (j): P 0_PUSCH,b,f,c (j) is P 0_NOMINAL_PUSCH,f,c (j) and P 0_UE_PUSCH,b,f,c It consists of the sum of (j). P 0_NOMINAL_PUSCH,f,c (j) is set to cell-specific upper layer signaling to the terminal, and P 0_UE_PUSCH,b,f,c (j) is a value set by terminal-specific upper layer signaling. Here, when j = 0, it means PUSCH for transmitting msg3, when j = 1, it means configured grant PUSCH, and when j = {2, … , J-1} is one of the values, it means grant PUSCH.

[0291] -μ: Subcarrier spacing configuration value

[0292] - : It may mean the amount of resources used in the i-th PUSCH transmission unit (e.g., the number of Resource Blocks (RBs) used for PUSCH transmission on the frequency axis).

[0293] - α b,f,c (j) It 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.

[0294] - PL b,f,c (q d ): Pathloss is the path loss that indicates the path loss between the base station and the terminal. The terminal uses the reference signal (RS) resource q signaled by the base station. d The path loss is calculated from the difference between the transmission power and the terminal reception signal level of the reference signal. 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. d The UE can decide this via upper layer configuration and SRI (in case of dynamic grant PUSCH or configured grant PUSCH based on ConfiguredGrantConfig that does not include upper layer configuration rrc-ConfiguredUplinkGrant (type 2 configured grant PUSCH)) or via upper layer configuration.

[0295] - Δ TF,b,f,c(i): This refers to a value determined according to the MCS (Modulation Coding Scheme) and the format of information transmitted via PUSCH (TF: transport format, e.g., whether UL-SCH is included or CSI is included, etc.).

[0296] - f b,f,c (i,l): A closed-loop power control adjustment value refers to a value for a closed-loop index l that can be determined by a higher layer setting and SRI for PUSCH. Here, the closed-loop power adjustment for PUSCH transmission can be supported by dividing it into an accumulation method that accumulates and applies a value indicated by a TPC command and an absolute method that directly applies the value indicated by the TPC command, and this can be determined depending on whether the higher layer parameter tpc-Accumulation is set. If the higher layer parameter tpc-Accumulation is set to disabled, the closed-loop power adjustment for PUSCH transmission is performed by the absolute method, and if tpc-Accumulation is not set, the closed-loop power adjustment for PUSCH transmission is performed by the accumulation method.

[0297] PUSCH power control adjustment state f b,f,c (i,l) can be determined through the bandwidth part b, carrier frequency f, cell c, i-th transmission unit, and closed loop index l.

[0298] - δPUSCH,b,f,c(i,l): : A value indicated by a TPC command field included in DCI format 0_0, 0_1, or 0_2 that schedules the i-th PUSCH transmission unit corresponding to the closed loop index l within the bandwidth part b, carrier frequency f, and cell c, or a value indicated by a TPC command field included in DCI format 2_2 transmitted together with a CRC scrambled with TPC-PUSCH-RNTI.

[0299] ○ If the terminal has received the upper layer signaling twoPUSCH-PC-AdjustmentStates, the closed loop index l can have a value of 0 or 1.

[0300] ○ If the terminal has not received the upper layer signaling twoPUSCH-PC-AdjustmentStates or has been scheduled for PUSCH transmission based on RAR UL grant, the closed loop index l may have a value of 0.

[0301] ● If the terminal has set ConfiguredGrantConfig, which is a higher layer signaling, and performs PUSCH transmission or retransmission, the closed loop index l can follow the powerControlLoopToUse value, which is a higher layer signaling.

[0302] ● If the terminal has been configured with the upper layer signaling SRI-PUSCH-PowerControl, the terminal can obtain a connection relationship between the value indicated by the SRI (SRS resource indicator) field in the DCI format that schedules PUSCH transmission and the closed loop index l configured through the upper layer signaling sri-PUSCH-ClosedLoopIndex, and can determine the closed loop index l based on the value indicated by the SRI field in the DCI format based on the connection relationship.

[0303] ● If the terminal is scheduled for PUSCH transmission based on a DCI format that does not include the SRI field, or if the upper layer signaling SRI-PUSCH-PowerControl is not set, the terminal may regard the closed loop index as 0.

[0304] ● If the terminal is indicated with a TPC command value through a TPC command field included in DCI format 2_2 transmitted with a CRC scrambled with TPC-PUSCH-RNTI, the closed loop index l can be indicated through the closed loop index field included in DCI format 2_2.

[0305] - If the terminal has not been configured with the upper layer signaling tpc-Accumulation, i.e., if the TPC command accumulation operation is possible for the terminal, the PUSCH power control adjustment state f for the i-th PUSCH transmission unit corresponding to the closed loop index l within the bandwidth part b, carrier frequency f, and cell c b,f,c (i,l) can be calculated as in [Equation 5].

[0306] [Equation 5]

[0307]

[0308] ○ δPUSCH,b,f,c(m,l) may be a value indicated by a TPC command field included in DCI format 0_0, 0_1, or 0_2 that schedules the m-th PUSCH transmission unit corresponding to the closed loop index l within the bandwidth part b, carrier frequency f, and cell c as described above, or may be a value indicated by a TPC command field included in DCI format 2_2 transmitted together with a CRC scrambled with TPC-PUSCH-RNTI. When TPC command accumulation operation is possible, the δPUSCH,b,f,c value may have a corresponding value in [dB] units depending on which value the TPC command field included in DCI format 0_0, 0_1, 0_2, or 2_2 indicates, as shown in [Table 18] below. For example, if the value of the TPC command field is 0, δPUSCH,b,f,c may have a value of -1 dB.

[0309] ○ is a specific set of TPC command values ​​described above D i It can mean the sum of δPUSCH,b,f,c for all transmission units corresponding to it. In this case, c(D i ) is a set D i It can mean the number of all elements belonging to D i may mean a set of DCIs containing all TPC command values ​​for which TPC command accumulation operation is to be performed for the i-th PUSCH transmission unit. D i To determine the start and end points in the time dimension, all DCIs received by the terminal within the two points are defined as D. i can be included as an element of .

[0310] ● D i The end point for determining is K from the start symbol of the i-th PUSCH transmission unit. PUSCH (i) It can be a point as far back as the symbol.

[0311] ● D i The starting point for determining is K from the starting symbol of the i-i0th PUSCH transmission unit. PUSCH It can be a point that is as far back as (i-i0)-1 symbols. In this case, i0, which is a positive integer, is the D i The end point for determining (K from the start symbol of the i-th PUSCH transmission unit) PUSCH (i) from the starting symbol of the i-i0th PUSCH transmission unit, K symbols earlier than the previous point. PUSCH It can be determined as the smallest value that satisfies that the previous time point becomes an earlier time point in time by (i-i0) symbols.

[0312] ● For example, D i The end point for determining can be defined as sym(i), and K is defined as the starting symbol of the i-i0th PUSCH transmission unit. PUSCHIf the time point prior to (i-i0) symbols can be defined as sym(i-i0), then if sym(i) = sym(i-1) > sym(i-2) > sym(i-3) holds, then i0 can be determined as 2.

[0313] - If the terminal has been set to the upper layer signaling tpc-Accumulation, i.e., if the TPC command accumulation operation is not possible for the terminal, then the PUSCH power control adjustment state f for the i-th PUSCH transmission unit corresponding to the closed loop index l within the bandwidth part b, carrier frequency f, and cell c b,f,c (i,l) can be calculated as in [Equation 6].

[0314] [Equation 6]

[0315]

[0316] ○ δPUSCH,b,f,c(i,l) may be a value indicated by a TPC command field included in DCI format 0_0, 0_1, or 0_2 that schedules the i-th PUSCH transmission unit corresponding to the closed loop index l within the bandwidth part b, the carrier frequency f, and the cell c as described above, or may be a value indicated by a TPC command field included in DCI format 2_2 transmitted together with a CRC scrambled with TPC-PUSCH-RNTI. When TPC command accumulation operation is impossible, the δPUSCH,b,f,c value may have a corresponding value in [dB] units depending on which value the TPC command field included in DCI format 0_0, 0_1, 0_2, or 2_2 indicates, as shown in [Table 18] below. For example, if the value of the TPC command field is 0, δPUSCH,b,f,c may have a value of -4 dB.

[0317] TPC command fieldAccumulated δPUSCH,b,f,c[dB]Absolute δPUSCH,b,f,c[dB]0-1-410-1211334

[0318] [SRS related]

[0319] Next, we describe an uplink channel estimation method using the Sounding Reference Signal (SRS) transmission of a terminal. The base station can configure at least one SRS configuration for each uplink BWP to convey configuration information for SRS transmission to the terminal, and can also configure at least one SRS resource set for each SRS configuration. For example, the base station and the terminal can exchange the following upper-level signaling information to convey information regarding the SRS resource set.

[0320] - srs-ResourceSetId: SRS resource set index

[0321] - srs-ResourceIdList: A set of SRS resource indices referenced in the SRS resource set.

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

[0323] - 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'.

[0324] - alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter settings for adjusting the transmission power of the SRS resource referenced in the SRS resource set.

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

[0326] 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 the slot of the SRS resource, which can include information about frequency hopping within or between slots of the SRS resource. In addition, the individual configuration information for the SRS resource can include the 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 the SRS resource set including the SRS resource. If the time axis transmission configuration of the SRS resource is set to 'periodic' or 'semi-persistent', the SRS resource transmission period and slot offset (e.g., periodicityAndOffset) can additionally be included in the time axis transmission configuration.

[0327] The base station can activate, deactivate, or trigger SRS transmission to the UE 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 UE through higher layer signaling. The base station can instruct the UE to activate an SRS resource set with resourceType set to periodic through higher layer signaling, and the UE can transmit an SRS resource referenced in the activated SRS resource set. The time-frequency domain resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, follows the periodicityAndOffset set in the SRS resource. In addition, the spatial domain transmission filter applied to the transmitted SRS resource can refer to the spatial relation information set in the SRS resource, or the associated CSI-RS information set in the SRS resource set that includes the SRS resource. A terminal can transmit SRS resources within an activated uplink BWP for periodic SRS resources activated through upper layer signaling.

[0328] For example, a base station can activate or deactivate semi-persistent SRS transmission to a terminal through upper layer signaling. The base station can instruct the terminal 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 with resourceType set to semi-persistent. The time-frequency domain resource mapping within the slot of the transmitted SRS resource follows the resource mapping information configured in the SRS resource, and the slot mapping including the transmission period and slot offset follows the periodicityAndOffset configured in the SRS resource. In addition, the spatial domain transmission filter applied to the transmitted SRS resource can refer to the spatial relation information configured in the SRS resource, or the associated CSI-RS information configured in the SRS resource set that includes the SRS resource. If spatial relation info is configured in an SRS resource, the spatial domain transmission filter can be determined by referring to the configuration information for spatial relation info transmitted through MAC CE signaling that activates semi-persistent SRS transmission without following it. The terminal can transmit SRS resources within the activated uplink BWP for the semi-persistent SRS resource activated through upper layer signaling.

[0329] For example, a base station can trigger aperiodic SRS transmission to a terminal via DCI. The base station can indicate one of the aperiodic SRS resource triggers (aperiodicSRS-ResourceTrigger) via the SRS request field of the DCI. The terminal can understand that an SRS resource set including the aperiodic SRS resource trigger indicated via DCI in the aperiodic SRS resource trigger list among the configuration information of the SRS resource set has been triggered. The terminal can transmit an SRS resource referenced in the triggered SRS resource set. The time-frequency domain resource mapping within the slot of the transmitted SRS resource follows the 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 the DCI and the SRS resource, which 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 be applied by applying the value indicated in the time domain resource assignment field of the DCI among the offset value(s) included in the slot offset set configured in the SRS resource set. In addition, the spatial domain transmission filter applied to the transmitted SRS resource can refer to the spatial relation information configured in the SRS resource, or can refer to the associated CSI-RS information configured 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.

[0330] When a base station triggers aperiodic SRS transmission to a terminal through DCI, a minimum time interval may be required between a PDCCH including the DCI that triggers aperiodic SRS transmission and the SRS to be transmitted, so that the terminal can transmit the SRS by applying configuration information for the SRS resource. The time interval for SRS transmission of the terminal can be defined as the number of symbols between the last symbol of the PDCCH including the DCI that triggers aperiodic SRS transmission and the first symbol to which the first SRS resource to be transmitted among the SRS resource(s) is mapped. The minimum time interval can be determined with reference to the PUSCH preparation procedure time required for the terminal to prepare for 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, which are defined by considering 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.

[0331]

[0332] The spatialRelationInfo setting information in [Table 19] above refers to a single reference signal and applies the beam information of the reference signal to the beam used for the corresponding SRS transmission. For example, the spatialRelationInfo setting may include information such as [Table 20] below.

[0333]

[0334] Referring to the above spatialRelationInfo setting, in order to use the beam information of a specific reference signal, the index of the reference signal to be referenced, i.e., the SS / PBCH (synchronization signal / physical broadcast channel) block (or SSB, synchronization signal block) index, CSI-RS index, or SRS index can be set. The upper signaling referenceSignal is setting information indicating which beam information of which 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 the csi-RS-Index as the transmission beam for 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.

[0335] [SRS Transmission Power Related]

[0336] In one embodiment of the present disclosure, a method is described in which a terminal sets and transmits the transmission power of an uplink reference signal (SRS; Sounding Reference Signal) in response to a power control command received from a base station. The method comprises: an SRS power control adjustment state corresponding to an I-th transmission unit, a closed loop index l, and an uplink reference signal transmission power (P) of the terminal. SRS ) can be determined as shown in [Mathematical Formula 7] below, which is expressed in dBm units. In [Mathematical Formula 7] below, when a terminal supports multiple carrier frequencies in multiple cells, each parameter can be determined for each cell c, carrier frequency f, and bandwidth part b, and can be distinguished by indices b, f, and c.

[0337] [Equation 7]

[0338]

[0339] - P CMAX,f,c (i): The maximum transmission power available to the terminal in the i-th transmission unit is determined by the power class of the terminal, parameters activated from the base station, and various parameters built into the terminal.

[0340] - P 0_SRS,b,f,c (q s ): Bandwidth part b, carrier frequency f, can be set to p0, which is the upper layer signaling for cell c, and SRS resource set q s can be set through upper layer signaling, SRS-ResourceSet and SRS-ResourceSetId.

[0341] -μ: Subcarrier spacing configuration value

[0342] - M SRS,b,f,c(i): It may mean the amount of resources used in the i-th SRS transmission unit (e.g., the number of Resource Blocks (RBs) used for SRS transmission on the frequency axis).

[0343] - α SRS,b,f,c (j): Bandwidth part b, carrier frequency f, can be set to alpha, which is the upper layer signaling for cell c, and SRS resource set q s can be set through upper layer signaling, SRS-ResourceSet and SRS-ResourceSetId.

[0344] - PL b,f,c (q d ): Pathloss is the path loss that indicates the path loss between the base station and the terminal. The terminal uses the reference signal (RS) resource q signaled by the base station. d Path loss is calculated from the difference between the transmission power and the terminal reception signal level of the reference signal.

[0345] - h b,f,c (i,l): It may mean an SRS power control adjustment state value for the i-th SRS transmission unit corresponding to the closed loop index l within the bandwidth part b, carrier frequency f, and cell c.

[0346] The SRS power control adjustment state can be determined through the bandwidth part b, carrier frequency f, cell c, and i-th transmission unit.

[0347] - If the terminal is configured to have the same power control adjustment state value between SRS transmission and PUSCH transmission through the upper layer signaling srs-PowerControlAdjustmentStates, the SRS power control adjustment state can be expressed as in [Mathematical Formula 8] below, and in [Mathematical Formula 8], f b,f,c (i,l) may mean the current PUSCH power control adjustment state. In this case, f can be achieved through various methods of the above-described embodiment 1. b,f,cWe can compute (i,l) and its value is h b,f,c It can be used by substituting (i,l).

[0348] [Equation 8]

[0349]

[0350] - If the terminal is not configured for PUSCH transmission in bandwidth part b, carrier frequency f, and cell c, or is configured to have separate power control adjustment state values ​​between SRS transmission and PUSCH transmission through upper layer signaling srs-PowerControlAdjustmentStates, and upper layer signaling tpc-Accumulation is not configured, the SRS power control adjustment state can be expressed regardless of closed loop l as in [Mathematical Formula 9] below.

[0351] [Equation 9]

[0352]

[0353] - δ SRS,b,f,c (m): It may be a value indicated by the TPC command field included in DCI format 2_3, and the value may follow [Table 17] above.

[0354] ○ is a specific set S of TPC command values ​​described above. i δ for all transmission units corresponding to SRS,b,f,c can mean the sum of . At this time, c(S i ) is a set S i It can mean the number of all elements belonging to S i S may mean a set of DCIs containing all TPC command values ​​for which TPC command accumulation operation is to be performed for the i-th PUSCH transmission unit. i To determine the starting point and the ending point in the time dimension, all DCIs received by the terminal within the two points are defined as Si can be included as an element of .

[0355] ● S i The end point for determining is K from the start symbol of the i-th SRS transmission unit. SRS (i) It can be a point as far back as the symbol.

[0356] ● S i The starting point for determining is K from the starting symbol of the i-i0th SRS transmission unit. SRS It can be a point that is as far back as (i-i0)-1 symbols. In this case, i0, which is a positive integer, is the S i End point for determining (K from the start symbol of the i-th SRS transmission unit) SRS (i) from the starting symbol of the i-i0th SRS transmission unit, K SRS It can be determined as the smallest value that satisfies that the previous time point becomes an earlier time point in time by (i-i0) symbols.

[0357] ● For example, S i The end point for determining can be defined as sym(i), and K is the starting symbol of the i-i0th SRS transmission unit. SRS If the time point prior to (i-i0) symbols can be defined as sym(i-i0), then if sym(i) = sym(i-1) > sym(i-2) > sym(i-3) holds, then i0 can be determined as 2.

[0358] - If the terminal is not configured for PUSCH transmission in bandwidth part b, carrier frequency f, and cell c, or is configured to have separate power control adjustment state values ​​between SRS transmission and PUSCH transmission through upper layer signaling srs-PowerControlAdjustmentStates, and upper layer signaling tpc-Accumulation is configured (i.e., TPC command accumulation operation cannot be performed and absolute TPC command value can be applied), the SRS power control adjustment state can be expressed regardless of closed loop l as in [Mathematical Formula 10] below.

[0359] [Equation 10]

[0360]

[0361] ○ δ SRS,b,f,c (i) may be a value indicated by the TPC command field included in DCI format 2_3 within the bandwidth part b, carrier frequency f, and cell c as described above, and the value may follow [Table 18] above. For example, if the value of the TPC command field is 0, δ SRS,b,f,c can have a value of -4 dB.

[0362] [Regarding terminal capability reporting]

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

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

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

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

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

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

[0369] 4. The terminal selects BCs to report by selecting BCs that match the requested RAT type from the final "candidate BC list" above. In this step, the terminal constructs the supportedBandCombinationList in a set order. That is, the terminal constructs BCs and UE capabilities to report according to the preset rat-Type order (nr -> eutra-nr -> eutra). In addition, it constructs a featureSetCombination for the constructed supportedBandCombinationList, and constructs a list of "candidate feature set combinations" from the candidate BC list after removing the list for the fallback BC (which contains capabilities of the same or lower level). The "candidate feature set combinations" above include feature set combinations for both NR and EUTRA-NR BCs, and can be obtained from the feature set combinations in the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

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

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

[0372] [NC-JT related]

[0373] According to one embodiment of the present disclosure, Non-Coherent Joint Transmission (NC-JT) may be used for a terminal to receive PDSCH from multiple TRPs.

[0374] Unlike existing systems, 5G wireless communication systems can support not only services requiring high transmission speeds, but also services with very short transmission delays and high connection density. In a wireless communication network comprising multiple cells, transmission and reception points (TRPs), or beams, coordinated transmission between each cell, TRP, or / and beam can increase the signal strength received by a terminal or efficiently control interference between each cell, TRP, or / and beam, thereby satisfying diverse service requirements.

[0375] Joint Transmission (JT) is a representative transmission technology for the aforementioned cooperative communication, which increases the signal strength or processing rate 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 (NC-JT) 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.

[0376] The above-described NC-JT transmission can be applied to at least one channel among the downlink data channel (PDSCH), downlink control channel (PDCCH), uplink data channel (PUSCH), and uplink control channel (PUCCH). When transmitting PDSCH, transmission information such as precoding, MCS, resource allocation, and TCI are indicated as 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.

[0377] FIG. 10 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 one embodiment of the present disclosure.

[0378] Referring to FIG. 10, examples for PDSCH transmission are explained for each technique of joint transmission (JT), and examples for allocating radio resources for each TRP are shown.

[0379] Referring to FIG. 10, an example (1000) for coherent joint transmission (C-JT) supporting coherent precoding between each cell, TRP or / and beam is illustrated.

[0380] In the case of C-JT, TRP A (1005) and TRP B (1010) transmit a single data (PDSCH) to the terminal (1015), and joint precoding can be performed on multiple TRPs. This may mean that DMRS is transmitted through the same DMRS ports for TRP A (1005) and TRP B (1010) to transmit the same PDSCH. For example, TRP A (1005) and TRP B (1010) 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 that is demodulated based on the DMRS transmitted through DMRS port A and DMRS B.

[0381] FIG. 10 illustrates an example (1020) of Non-Coherent Joint Transmission (NC-JT) supporting non-coherent precoding between each cell, TRP or / and beam for PDSCH transmission.

[0382] In the case of NC-JT, each cell, TRP, or / and beam transmits a PDSCH to the terminal (1035), and individual precoding can be applied to each PDSCH. Each cell, TRP, or / and beam transmits a different PDSCH or a different PDSCH layer to the terminal, thereby improving the throughput compared to single cell, TRP, or / and beam transmission. In addition, each cell, TRP, or / and beam repeatedly transmits the same PDSCH to the terminal, thereby improving the reliability compared to single cell, TRP, or / and beam transmission. For convenience of explanation, cells, TRPs, or / and beams are collectively referred to as TRPs hereinafter.

[0383] At this time, various wireless resource allocations can be considered, such as when the frequency and time resources used by multiple TRPs for PDSCH transmission are all the same (1040), when the frequency and time resources used by multiple TRPs do not overlap at all (1045), and when some of the frequency and time resources used by multiple TRPs overlap (1050).

[0384] To support NC-JT, DCIs of various forms, structures, and relationships can be considered to simultaneously allocate multiple PDSCHs to a single terminal.

[0385] FIG. 11 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 one embodiment of the present disclosure.

[0386] Referring to FIG. 11, case #1 (1100) is an example in which, in addition to the 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 the control information for the PDSCHs transmitted from the serving TRP. That is, the terminal 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)). The formats between the independent DCIs may be the same or different, and the 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 may occur for each DCI, which may deteriorate reception performance.

[0387] Case #2 (1105) shows an example in which, in addition to the 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)), control information (DCI) for the 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.

[0388] 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 cooperative 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 cooperative 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.

[0389] In the aforementioned case #2, 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.

[0390] Case #3 (1110) shows an example in which, in a situation 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, 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.

[0391] For example, in the case of DCI#0, which is control information for 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 cooperative 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 piece of information among HARQ-related information such as frequency domain resource assignment, time domain resource assignment, and MCS of cooperative TRPs. In addition, for information not included in sDCI, such as BWP (bandwidth part) indicator or carrier indicator, the DCI (DCI#0, normal DCI, nDCI) of serving TRP can be followed.

[0392] Case #3 (1110) may limit the degree of freedom in controlling or allocating each PDSCH depending on the content of the information element included in sDCI, but it is possible to control the reception performance of sDCI and the complexity of blind decoding of DCI of the terminal may be reduced compared to case #1 (1100) or case #2 (1105).

[0393] Case #4 (1115) 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 in addition to 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 (1115), 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.

[0394] In the following descriptions 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) containing PDSCH control information transmitted in a cooperative TRP, and unless a special limitation is specified, the description can be similarly applied to the various auxiliary DCIs described above.

[0395] In the following description and examples, the aforementioned cases #1 (1100), #2 (1105), and #3 (1110), in which more than one DCI (PDCCH) is used to support NC-JT, may be classified as multiple PDCCH-based NC-JT, and the aforementioned case #4 (1115), in which a single DCI (PDCCH) is used to support NC-JT, may be classified 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 DCI 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 for distinguishing through an upper layer indicator for each CORESET, a method for distinguishing through beam setting for each CORESET, etc. Additionally, 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 layer can be indicated through a Transmission Configuration Indicator (TCI) indication for the layer. In the embodiments of the present disclosure, "cooperative TRP" can be replaced with various terms such as "cooperative panel" or "cooperative beam" in actual application.

[0396] In the embodiments of the present disclosure, “when NC-JT is applied” can be interpreted in various ways depending on the situation, such as “when a terminal simultaneously receives one or more PDSCHs in one BWP,” “when a terminal simultaneously receives PDSCHs based on two or more TCI (Transmission Configuration Indicator) indications in one BWP,” or “when a PDSCH received by a terminal is associated with one or more DMRS port groups,” but is used as a single expression for convenience of explanation.

[0397] The wireless protocol architecture for NC-JT in the present disclosure can be used in various ways depending on the TRP deployment scenario. For example, when there is no or small backhaul delay between cooperative TRPs, a method using a structure based on MAC layer multiplexing (CA-like method) similar to S10 of FIG. 4 is possible. On the other hand, when the backhaul delay between cooperative TRPs is so large that it cannot be ignored (for example, when it takes more than 2 ms to exchange information 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, similar to S20 of FIG. 4.

[0398] A terminal supporting C-JT or / and NC-JT can receive C-JT or / and NC-JT related parameters or setting values ​​from a higher layer configuration, and set the RRC parameters of the terminal based on the parameters. For the higher 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, 128 in FR1, and to 64 and 128 in FR2, and among the set number, up to 8 states can be set that can be indicated by 3 bits of the TCI field of the DCI via a MAC CE message. 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.

[0399] [Multi-DCI based Multi-TRP]

[0400] 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 can establish a downlink control channel for NC-JT transmission based on a multi-PDCCH.

[0401] 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 configured as in at least one of the following cases.

[0402] * 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 with 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 index for each CORESET may be named as CORESETPoolIndex, and for CORESETs with the same CORESETPoolIndex value set, it may be considered that the PDCCH is transmitted from the same TRP. For 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.

[0403] ** 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 may consider that the base station can use the multi-DCI based multi-TRP transmission method.

[0404] ** 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, that is, if all CORESETs have the same CORESETPoolIndex of 0 or 1, the terminal can assume that the base station transmits using a single-TRP rather than using a multi-DCI based multi-TRP transmission method.

[0405] * Multiple PDCCH-Config settings: Multiple PDCCH-Configs are configured 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 to correspond to a specific TRP.

[0406] * CORESET Beam / Beam Group Configuration: The TRP corresponding to the CORESET can be distinguished through the beam or beam group configured 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 can be considered to be transmitted in the CORESET.

[0407] * Search space beam / beam group configuration: A beam or beam group is configured for each search space, and this allows TRPs for each search space to 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 a PDCCH in the corresponding search space, or that a PDCCH that schedules the PDSCH of the same TRP is transmitted in the corresponding search space.

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

[0409] The above settings can be independent on a per-cell or per-BWP basis. For example, a PCell may have two different CORESETPoolIndex values, while a specific SCell may not have a CORESETPoolIndex value set. In this case, it can be assumed that NC-JT transmission is configured on the PCell, while NC-JT transmission is not configured on the SCell without the CORESETPoolIndex value set.

[0410] The PDSCH TCI state activation / deactivation MAC-CE applicable to the multi-DCI based multi-TRP transmission method may follow the above-described FIG. 9. If the UE does not have CORESETPoolIndex set for each of all CORESETs in the upper layer signaling PDCCH-Config, the UE may ignore the CORESET Pool ID field (955) in the corresponding MAC-CE (950). 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 (955) value in the corresponding MAC-CE (950). For example, if the value of the CORESET Pool ID field (955) within the MAC-CE (950) is 0, the TCI state within the DCI included in the PDCCH transmitted from CORESETs with CORESETPoolIndex of 0 may follow the activation information of the MAC-CE.

[0411] 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 the upper layer signaling PDCCH-Config 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.

[0412] 1) If the PDSCHs indicated by the PDCCHs within each CORESET having two different CORESETPoolIndexes completely or partially overlap, the TCI states indicated by each PDCCH can be applied to different CDM groups. That is, two or more TCI states may not be applied to a single CDM group.

[0413] 2) The terminal can expect that the actual number of front-loaded DMRS symbols, the actual number of additional DMRS symbols, the location 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.

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

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

[0416] [Single-DCI based Multi-TRP]

[0417] 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 establish a downlink control channel for NC-JT transmission based on a single-PDCCH.

[0418] In a single DCI-based multi-TRP transmission method, a PDSCH transmitted by multiple TRPs can be scheduled with a single DCI. At this time, the number of TCI states can be used as a method of indicating the number of TRPs transmitting the corresponding PDSCH. That is, if the number of TCI states indicated in the DCI scheduling the PDSCH is two, it can be considered as a single PDCCH-based NC-JT transmission, and if the number of TCI states is one, it can be considered as a single-TRP transmission. The TCI states indicated in the above DCI can correspond to one or both of the 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 is established between the TCI codepoint indicated in the DCI and the TCI states activated by MAC-CE, and this can be the case when there are two TCI states activated by MAC-CE corresponding to the above TCI codepoint.

[0419] As another example, if at least one codepoint among all codepoints in the TCI state field within the DCI indicates two TCI states, the UE may assume that the base station can transmit based on the single-DCI based multi-TRP method. In this case, at least one codepoint indicating two TCI states within the TCI state field may be activated via the Enhanced PDSCH TCI state activation / deactivation MAC-CE.

[0420] Figure 12 is a diagram illustrating the structure of the Enhanced PDSCH TCI state activation / deactivation MAC-CE. The meaning of each field in the MAC CE and the values ​​that can be set for each field are as shown in [Table 21] below.

[0421]

[0422] In Fig. 12, if the value of the C0 field (1205) is 1, the corresponding MAC-CE is the TCI state ID 0,1 Additionally, TCI state ID in field (1210) 0,2 It may include field (1215). This is the 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 the MAC-CE is activated, and if the base station instructs the terminal with the corresponding codepoint, the terminal can be instructed with two TCI states. If the value of the C0 field (1205) is 0, the corresponding MAC-CE is the TCI state ID. 0,2 It cannot contain field (1215), 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.

[0423] The above configuration can be independent on a per-cell or per-BWP basis. For example, a PCell may have up to two activated TCI states corresponding to a single TCI codepoint, while a specific SCell may have up to one activated TCI state corresponding to a single TCI codepoint. In this case, it can be assumed that NC-JT transmission is configured on the PCell, while NC-JT transmission is not configured on the aforementioned SCell.

[0424] [Distinguishing between Single-DCI-based Multi-TRP PDSCH Repetitive Transmission Techniques (TDM / FDM / SDM)]

[0425] Next, we describe a method for distinguishing between single-DCI-based multi-TRP PDSCH repetition transmission techniques. A UE may be instructed to use different single-DCI-based multi-TRP PDSCH repetition transmission techniques (e.g., TDM, FDM, SDM) based on values ​​indicated by a DCI field from a base station and higher-layer signaling configurations. Table 22 below illustrates a method for distinguishing between single- and multiple-TRP-based techniques indicated to a UE based on values ​​of specific DCI fields and higher-layer signaling configurations.

[0426] Number of combinations of TCI states Number of CDM groups repetitionNumber setting and instruction conditions repetitionScheme setting Transmission scheme indicated to the relevant terminal 11≥1 Condition 2 Not configured Single-TRP 2 1≥1 Condition 2 Configured Single-TRP 3 1≥1 Condition 3 Configured Single-TRP 4 11 Condition 1 Configured or not configured Single-TRP TDM scheme B 5 22 Condition 2 Not configured Multi-TRP SDM 6 22 Condition 3 Not configured Multi-TRP SDM 7 22 Condition 3 Configured Multi-TRP SDM 8 21 Condition 3 Configured Multi-TRP FDM scheme A / FDM scheme B / TDM scheme A 9 21 Condition 1 Not configured Multi-TRP TDM scheme B

[0427] In the above [Table 22], each column can be explained as follows.

[0428] - Number of TCI states (2 columns): This refers to the number of TCI states indicated by the TCI state field in DCI, and can be 1 or 2.

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

[0430] - repetitionNumber setting and indication conditions (column 4): There are 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.

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

[0432] * 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 the TDRA entry indicated by the Time Domain Resource Allocation field in the DCI does not contain a setting for repetitionNumber.

[0433] * Condition 3: If all TDRA entries that can be indicated by the Time Domain Resource Allocation field do not contain a setting for repetitionNumber.

[0434] - RepetitionScheme setting related (column 5): This indicates whether the upper layer signaling repetitionScheme is set. The upper layer signaling repetitionScheme can be set to one of 'tdmSchemeA', 'fdmSchemeA', or 'fdmSchemeB'.

[0435] - 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 22] above.

[0436] * Single-TRP: This refers to a single TRP-based PDSCH transmission. If the UE has configured the 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 single-TRP-based PDSCH transmission.

[0437] * Single-TRP TDM scheme B: This refers to PDSCH repeated transmission based on time resource division between single TRP slots. According to Condition 1 related to repetitionNumber described above, the UE repeatedly transmits PDSCH in the time dimension for the number of slots with 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 equal to the repetitionNumber number, the start symbol and symbol length of the PDSCH indicated by the TDRA entry are applied identically, and the same TCI state is applied for each PDSCH repeated transmission. This technique is similar to the slot aggregation method in that it performs PDSCH repeated transmission between slots on time resources, but it differs from slot aggregation in that it can dynamically determine whether to indicate repeated transmission based on the Time Domain Resource Allocation field in the DCI.

[0438] * Multi-TRP SDM: This refers to a PDSCH transmission method based on spatial resource division based on multiple TRPs. This is a method of receiving by dividing layers from each TRP. Although it is not a repetitive transmission method, it can increase the reliability of PDSCH transmission by increasing the number of layers and lowering the coding rate. The terminal can receive PDSCH by applying the two TCI states indicated through the TCI state field in the DCI for each of the two CDM groups indicated by the base station.

[0439] * 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 for non-overlapping frequency resources. If the PRB bundling size is determined as wideband, if the number of RBs indicated by the Frequency Domain Resource Allocation field is N, the terminal applies the first TCI state to the first ceil(N / 2) RBs and applies the second TCI state to the remaining floor(N / 2) RBs. Here, ceil(.) and floor(.) are operators that indicate rounding up and down to the first decimal place. If the PRB bundling size is determined as 2 or 4, even-numbered PRGs receive the first TCI state, and odd-numbered PRGs receive the second TCI state.

[0440] * Multi-TRP FDM scheme B: This refers to a multi-TRP based frequency resource division PDSCH repeated transmission method, and it has two PDSCH transmission positions (occasions) so that PDSCH can be repeatedly transmitted in 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, if the number of RBs indicated by the Frequency Domain Resource Allocation field is N, the UE applies the first TCI state to the first ceil (N / 2) RBs 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 to the first decimal place. If the PRB bundling size is determined as 2 or 4, even-numbered PRGs receive the first TCI state, and odd-numbered PRGs receive the second TCI state.

[0441] * 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 by the upper layer signaling StartingSymbolOffsetK from the last symbol of the first transmission position, and the transmission position can be determined by the indicated symbol length. If the upper layer signaling StartingSymbolOffsetK is not set, the symbol offset can be regarded as 0.

[0442] * Multi-TRP TDM scheme B: This refers to a PDSCH repeated transmission method between time resource division slots based on multiple TRPs. The UE has one PDSCH transmission position (occasion) in one slot, and can receive repeated transmissions based on the start symbol and symbol length of the same PDSCH for the number of slots indicated by the repetitionNumber 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.

[0443] 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 (frequency division duplex), TDD (time division duplex) and / or XDD (cross division duplex) (and / or SBFD (subband non-overlapping full duplex), full duplex) systems. In the present disclosure below, upper signaling (or upper layer signaling) refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of a physical layer, or a terminal transmits a signal to a base station using an uplink data channel of a physical layer, and may also be referred to as RRC signaling, PDCP signaling, or MAC (medium access control) control element (MAC control element; MAC CE).

[0444] For convenience in the following description of the present disclosure, 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 can be appropriately replaced with one of the above terms.

[0445] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as having the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied have a specific format, or including a specific indicator that indicates whether cooperative communication is applied, or scrambled with a specific RNTI by the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied, or assuming cooperative communication is applied in a specific section indicated by a higher layer. For the convenience of the following description, the case where the terminal receives the PDSCH to which cooperative communication is applied based on conditions similar to the above will be referred to as the NC-JT case.

[0446] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Hereinafter, a base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, a gNB, 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. Although embodiments of the present disclosure are described below using a 5G system as an example, embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type. For example, LTE or LTE-A mobile communication and mobile communication technologies developed after 5G may be included here. Therefore, embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure as determined by a person skilled in the art. The contents of the present disclosure can be applied to FDD, TDD, and / or XDD (and / or SBFD, full duplex) systems.

[0447] Additionally, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of the present disclosure.

[0448] In the following description of the present disclosure, upper layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

[0449] - MIB (Master Information Block)

[0450] - SIB (System Information Block) or SIB

[0451] - RRC (Radio Resource Control)

[0452] - MAC (Medium Access Control) CE (Control Element)

[0453] In addition, L1 (layer 1) signaling may be signaling corresponding to at least one or a combination of one or more signaling methods using the following physical layer channels or signaling.

[0454] - PDCCH (Physical Downlink Control Channel)

[0455] - DCI (Downlink Control Information)

[0456] - UE-specific DCI

[0457] - Group common DCI

[0458] - Common DCI

[0459] - Scheduling DCI (e.g. DCI used for scheduling downlink or uplink data)

[0460] - Non-scheduled DCI (e.g. DCI not intended for scheduling downlink or uplink data)

[0461] - PUCCH (Physical Uplink Control Channel)

[0462] - UCI (Uplink Control Information)

[0463] In the present disclosure, determining the priority between A and B may be referred to in various ways, such as selecting a higher priority according to a predetermined priority rule and performing an action corresponding to it, or omitting or dropping an action for a lower priority.

[0464] The term slot used in the present disclosure below is a general term that may refer to a specific time unit corresponding to a TTI (Transmit Time Interval), and may specifically mean a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system.

[0465] In the present disclosure below, 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.

[0466] In the description of one embodiment of the present disclosure, "more than" may be replaced with "more than," and "less than" may be replaced with "less than." In the description of one embodiment of the present disclosure, "more than" may be replaced with "more than," and "less than" may be replaced with "less than."

[0467] <Example 1: UL-only TRP support method>

[0468] As one embodiment of the present disclosure, a method for supporting UL-only TRP, which supports only UL reception among multi-TRPs operated in a base station, is described. This embodiment can be operated in combination with other embodiments. Hereinafter, in the present disclosure, UL-only TRP, uplink-only TRP, UL-only TRP, and various terms that can be interpreted identically or similarly thereto can be interpreted to mean a TRP that supports only uplink signal reception among TRPs that can be operated in a base station.

[0469] When transmitting an uplink channel, the terminal can determine the uplink transmission power based on the TCI state. At this time, depending on the supported TCI state, the terminal and base station can operate in either the joint TCI mode (indicating the uplink transmission power parameter using the TCI-State) or the separate TCI mode (indicating the uplink transmission power parameter using the TCI-UL-State). The transmission power parameter can be applied to the uplink channel to be transmitted using the following method.

[0470] [Method 1-1] How to determine the basic transmission power: Applying common transmission power parameters

[0471] The terminal can apply a set of transmission power parameters (e.g., p0, alpha, closed circuit index) that can be known through ul-powerControl set for the uplink bandwidth portion for all uplink transmissions within each uplink bandwidth portion.

[0472] [Method 1-2] Additional transmission power determination method: Different transmission power parameters can be applied.

[0473] The terminal can apply a set of transmit power parameters (e.g., p0, alpha, closed circuit index) known through upper layer signaling ul-powerControl-r17 within a joint TCI state (TCI-State) or a separate TCI state (TCI-UL-State).

[0474] The terminal may report to the base station whether it supports at least one combination of [Method 1-1] and [Method 1-2] through a terminal capability report. In addition, the terminal may receive configuration from the base station for at least one combination of [Method 1-1] and [Method 1-2] through upper layer signaling.

[0475] FIG. 13 is a diagram illustrating an example of the operation of a base station and a terminal operating with multiple TRPs, including a TRP that supports only an uplink reception function according to one embodiment of the present disclosure.

[0476] The terminal (13-10) can be connected to and operate with a base station that operates with multiple TRPs as described above. Basically, the terminal can assume that each of the multiple TRPs supports both uplink reception and downlink transmission. At this time, in addition to the conventional TRP (13-00) that supports both uplink reception and downlink transmission, the base station can also operate a TRP (13-05) that supports only uplink reception, for the purpose of improving uplink coverage from the terminal's perspective or for the purpose of energy saving benefits that can be obtained by saving downlink transmission power at the base station. This TRP that supports only uplink reception can be called a UL-only TRP. The terminal can assume that no downlink transmission is performed from this UL-only TRP. At this time, the base station and the terminal can consider at least one or more combinations of the following as assumptions for this UL-only TRP.

[0477] - The UL-only TRP can operate as a UL-only TRP only for specific terminals. That is, although the UL-only TRP actually has both uplink reception and downlink transmission functions, it can only support the uplink reception function for specific terminals under specific conditions (for example, notifying the terminal that it is connected to the UL-only TRP through a combination of at least one of a specific upper layer signaling, MAC-CE, and L1 signaling). That is, it can support downlink transmission for other terminals. This UL-only TRP can expand the uplink coverage by additionally operating only the reception function of a TRP that is already installed near the location or a newly installed TRP when specific terminals exist at the boundary of a certain cell coverage.

[0478] - The UL-only TRP may be a TRP that does not support downlink transmission functions for all terminals, but only uplink reception functions. In other words, the UL-only TRP is a TRP with relatively low production and installation costs, and can be used to receive uplink transmissions from terminals in addition to existing TRPs, thereby obtaining reception diversity from the base station's perspective.

[0479] Although the terminal can receive a path loss measurement reference signal from a TRP (1300) capable of uplink and downlink operations, since downlink transmission is not performed from a UL-only TRP (1305), there may be a problem in that the path loss between the UL-only TRP and the terminal cannot be known when the terminal (1310) performs uplink transmission toward the UL-only TRP (1305). To solve this situation, the base station and the terminal can perform the following process to obtain path loss information between the UL-only TRP and the terminal according to [Method 2-1].

[0480] [Method 2-1]

[0481] [Process 2-1] Uplink transmission of the terminal

[0482] [Process 2-2] Calculating the difference in path loss at the base station

[0483] [Process 2-3] Transmitting the difference in path loss to the terminal

[0484] [Process 2-4] After obtaining the difference value d_P between the path loss of the TRP that can support both uplink and downlink and the TRP that can support only uplink, the terminal transmits uplink without applying d_P.

[0485] [Process 2-5] Calculating the difference in path loss at the base station

[0486] [Process 2-6] Transmitting the difference in path loss to the terminal

[0487] The terminal can perform the following process to obtain path loss information using another [Method 2-2].

[0488] [Method 2-2]

[0489] [Process 3-1] Terminal Uplink Transmission

[0490] [Process 3-2] Calculating the difference in path loss at the base station

[0491] [Process 3-3] Transmitting the difference in path loss to the terminal

[0492] [Process 3-4] After obtaining the difference value d_P between the path loss of the TRP that can support both uplink and downlink and the TRP that can support only uplink, d_P is applied and the terminal transmits on the uplink.

[0493] [Process 3-5] Calculating the difference in path loss at the base station

[0494] [Process 3-6] Transmitting the difference in path loss to the terminal

[0495] Through the above-described [Method 2-1] and [Method 2-2], the terminal can use the following modified transmission power calculation formula when determining uplink transmission power for UL-only TRP.

[0496] For example, when determining the PUCCH transmission power for UL-only TRP that supports only uplink reception operation, the terminal can modify [Equation 2] as shown in [Equation 11] below and use it. That is, Equation 2 can be modified to Equation 11. In this case, PL in [Equation 11] below off,b,f,c (q d * ) can be regarded as the above d_P value, which is the difference in path loss, and q d * may mean that the difference in the corresponding path loss corresponds to one or more path loss measurement reference signals. In this case, the terminal q d * If q corresponds to one path loss measurement reference signal, d * =q d It can be considered as

[0497] [Equation 11]

[0498]

[0499] As another example, when determining PUSCH transmission power for UL-only TRP that supports only uplink reception operation, the terminal can modify [Equation 4] as in [Equation 12] or [Equation 13] below and use it. That is, Equation 4 can be modified as Equation 12 or Equation 13. In this case, PL in [Equation 12] or [Equation 13] below off,b,f,c (q d * ) can be regarded as the above d_P value, which is the difference in path loss, and q d * may mean that the difference in the corresponding path loss corresponds to one or more path loss measurement reference signals. In this case, the terminal q d * If q corresponds to one path loss measurement reference signal,d * =q d It can be considered as [Mathematical expression 12] or [Mathematical expression 13] below is the difference in path loss, PL off,b,f,c (q d * ) can be distinguished depending on whether the value is directly applied to the path loss amount.

[0500] [Equation 12]

[0501]

[0502] [Equation 13]

[0503]

[0504] As another example, when determining PUSCH transmission power for UL-only TRP that supports only uplink reception operation, the terminal can modify [Equation 7] as in [Equation 14] or [Equation 15] below and use it. That is, Equation 7 can be modified to Equation 14 or Equation 15. In this case, PL in [Equation 14] or [Equation 15] below off,b,f,c (q d * ) can be regarded as the above d_P value, which is the difference in path loss, and q d * may mean that the difference in the corresponding path loss corresponds to one or more path loss measurement reference signals. In this case, the terminal q d * If q corresponds to one path loss measurement reference signal, d * =q d It can be considered as [Mathematical Formula 14] or [Mathematical Formula 15] below is the difference in path loss, PL off,b,f,c (q d * ) can be distinguished depending on whether the value is directly applied to the path loss amount.

[0505] [Equation 14]

[0506]

[0507] [Equation 15]

[0508]

[0509] The terminal may be notified from the base station through at least one combination of upper layer signaling, MAC-CE signaling, and L1 signaling for at least one combination of [Method 2-1] and [Method 2-2], or may expect that at least one combination of [Method 2-1] and [Method 2-2] is fixedly defined in the standard.

[0510] The terminal can report to the base station whether it can support at least one combination of [Method 2-1] and [Method 2-2] as a terminal capability.

[0511] The terminal may consider a combination of at least one of the following items in a method of receiving information from the base station about the difference value or change in path loss amount.

[0512] [Method 3-1]

[0513] The terminal can receive the d_P value, which is the difference value of the path loss amount, or the d_P'' value, which is the change amount of the d_P value, from the base station through upper layer signaling.

[0514] [Method 3-2]

[0515] The terminal receives the d_P value, which is the difference value of the path loss amount, or the d_P'' value, which is the change amount of the d_P value, from the base station through upper layer signaling, and can then update the preset value by receiving MAC-CE signaling from the base station.

[0516] [Method 3-3]

[0517] The terminal may receive the d_P value, which is the difference value of the path loss amount, or the d_P'' value, which is the change amount of the d_P value, from the base station through upper layer signaling, and thereafter be instructed through DCI.

[0518] [Method 3-4]

[0519] The terminal receives the d_P value, which is the difference value of the path loss amount, or the d_P'' value, which is the change amount of the d_P value, from the base station through upper layer signaling, and then receives two or more CSI-RSs from the base station and implicitly receives the d_P or d_P'' value through the difference in reception power of the corresponding CSI-RSs.

[0520] [Method 3-5]

[0521] The terminal can receive the d_P or d_P'' value from the base station through a combination of at least one of [Method 3-1] to [Method 3-4] and update the preset value.

[0522] A method for a terminal to receive uplink scheduling including information related to a difference value of path loss from a base station may consider a combination of at least one of the following items.

[0523] [Method 4-1]

[0524] A terminal can receive one or more joint TCI states or UL TCI states from a base station through upper layer signaling, and at this time, as shown in [Table 23] below, the terminal can receive information on the difference value of path loss within one or more joint TCI states or UL TCI states. The names of the RRC IEs (information elements) in Table 23 are only examples and can be expressed by other names.

[0525]

[0526] In the above [Table 23], the terminal can set pathlossOffset as upper layer signaling for the difference value of the path loss amount, and the value can be an integer from Xs to Xe.

[0527] For example, Xs and Xe can be 0 and 30, respectively. As another example, Xs and Xe can be -10 and 50, respectively, and the values ​​can be in increments of 1 dB. As another example, Xs and Xe can be 2 and 32, respectively, and the values ​​can be in increments of 2 dB.

[0528] [Method 4-2]

[0529] The terminal can receive one or more joint TCI states or UL TCI states from the base station as upper layer signaling, and the terminal can receive one or more difference values ​​for path loss in the BWP-UplinkDedicated, which is upper layer signaling for the uplink bandwidth, and each difference value for path loss can be linked to one or more groups of path loss measurement reference signals. In addition, the terminal can additionally receive upper layer signaling in the joint TCI state or UL TCI state, which indicates whether to apply the difference value for path loss in addition to the path loss measured through the path loss measurement reference signal that can be set as upper layer signaling. [Table 24] below is one example that can express the above method, and the link between the difference values ​​for path loss and the groups of path loss measurement reference signals may not be limited thereto. The names of the RRC IEs in Table 24 are only examples and may be expressed by other names.

[0530]

[0531] The terminal can receive a pathlossOffset as a higher layer signaling for the difference value of the path loss amount, and the value can be an integer from Xs to Xe.

[0532] For example, Xs and Xe can be 0 and 30, respectively. As another example, Xs and Xe can be -10 and 50, respectively, and the values ​​can be in increments of 1 dB. As another example, Xs and Xe can be 2 and 32, respectively, and the values ​​can be in increments of 2 dB.

[0533] [Method 4-3]

[0534] The terminal can receive one or more joint TCI states or UL TCI states as upper layer signaling from the base station, and the terminal can receive one path loss difference value set within the BWP-UplinkDedicated, which is an upper layer signaling for the uplink bandwidth. In this case, the terminal can assume that the path loss difference value is always applied to a specific TCI state depending on how it operates with multiple TRPs.

[0535] [Table 25] below may be one example of how the above method can be expressed, but may not be limited thereto. The names of the RRC IEs in Table 25 are only examples and may be expressed with other names.

[0536]

[0537] ULonlyNode2 can be defined as a condition for the pathlossOffset to be set by the base station within BWP-UplinkDedicated, which is an upper layer signaling for the terminal. The condition ULonlyNode2 can mean that the terminal operates within a cell that includes a UL-only TRP, which can mean when a specific upper layer signaling is set.

[0538] If the terminal does not set the above pathlossOffset in BWP-UplinkDedicated, the terminal may consider the difference value of the path loss amount as 0.

[0539] The terminal can receive a pathlossOffset as a higher layer signaling for the difference value of the path loss amount, and the value can be an integer from Xs to Xe.

[0540] For example, Xs and Xe can be 0 and 30, respectively. As another example, Xs and Xe can be -10 and 50, respectively, and the values ​​can be in increments of 1 dB. As another example, Xs and Xe can be 2 and 32, respectively, and the values ​​can be in increments of 2 dB.

[0541] [Method 4-4]

[0542] The terminal can receive a path loss difference value from the base station through upper layer signaling. The path loss difference value setting may vary by bandwidth part, or may vary by cell, so that the same value is set for all bandwidth parts within the cell. In this case, the terminal can expect that a new field indicating whether to apply the path loss difference value is included in the DCI when the path loss difference value is set. Through this new field in the DCI, the terminal can distinguish whether the uplink transmission is for a UL-only TRP or an uplink transmission for a TRP that can operate both uplink and downlink through the DCI from the base station.

[0543] [Method 4-5]

[0544] The terminal may consider at least one combined method among the above [Method 4-1] to [Method 4-4].

[0545] The terminal may be notified from the base station through at least one combination of upper layer signaling, MAC-CE signaling, and L1 signaling for at least one combination of [Method 4-1] to [Method 4-5], or may expect that at least one combination of [Method 4-1] to [Method 4-5] is fixedly defined in the standard.

[0546] The terminal may report to the base station, based on its terminal capabilities, whether it can support at least one combination of [Method 4-1] to [Method 4-5]. In this case, if the terminal reports to the base station, based on its terminal capabilities, that it can support a combination of one or more specific methods, it may be considered that the terminal has reported that it cannot support one or more other combinations of specific methods.

[0547] The terminal may determine whether to apply the difference value of the path loss amount by considering at least one combination of [Method 4-1] to [Method 4-5] when performing dynamic grant-based PUSCH transmission scheduled based on DCI, Type-2 configured grant-based PUSCH transmission activated through DCI, Type-1 configured grant-based PUSCH transmission configured through upper layer signaling, PUCCH transmission, SRS transmission, and PRACH transmission.

[0548] <Second Embodiment: Enhanced PHR Trigger Method for Performing Power Headroom Reporting for UL Only TRP>

[0549] A method for triggering power headroom (PHR) for uplink channel transmission when supporting uplink-only (UL only or UL only) TRP according to one embodiment of the present disclosure is described. This embodiment can be operated in combination with other embodiments described in the present disclosure. Hereinafter, in the present disclosure, UL only TRP, uplink only TRP, UL only TRP, and various terms that can be interpreted identically or similarly thereto can be interpreted to mean a TRP that supports only reception of uplink signals among TRPs that can be operated at a base station.

[0550] As described in the first embodiment, the UL only TRP is a TRP that can only receive UL signals (channels), and the terminal cannot receive DL signals (channels) including DL reference signals through the TRP operated as the UL only TRP. In this way, various methods for determining the path loss value for the UL only TRP, in which the DL signal, in particular, the periodic DL reference signal (periodic DL RS) required for measuring the path loss value used in determining the UL transmission power, is not transmitted, have been described in the first embodiment.

[0551] When the following trigger event occurs, the terminal can report the power headroom, which means the difference between the maximum transmission power calculated by the terminal and the transmission power of the current transmitting uplink channel (or the transmission power for the reference format if the cell is not currently transmitting an uplink signal), to the base station through the MAC CE format.

[0552] - [Trigger Event 1] When the upper layer parameter phr-ProhibitTimer expires and the MAC entity has uplink resources for a new transmission, the path loss for at least one activated serving 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 serving cell is not a dormant bandwidth part. In this case, the path loss change for a 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 time of the most recent PHR transmission.

[0553] - [Trigger Event 2] Upper layer parameter phr-PeriodicTimer expired.

[0554] - [Trigger Event 3] Power headroom reporting is not supported by the setting or reset, but by the upper layer, or the power headroom reporting function is set or reset by the upper layer.

[0555] - [Trigger Event 4] SCell is activated for any 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).

[0556] - [Trigger Event 5] Activation of SCG

[0557] - [Trigger Event 6] PSCell is added, except when SCG is disabled (i.e., a new PSCell is added or changed).

[0558] - [Trigger Event 7] The upper layer parameter phr-PrhoibitTimer has expired, and the MAC entity has uplink resources for a new transmission, and for any activated supporting cells of any MAC entity with configured uplink, all of the following conditions a) and b) are met:

[0559] a) There are uplink resources allocated for transmission or PUCCH is transmitted to the corresponding cell.

[0560] b) When the MAC entity has uplink resources for transmission or transmits PUCCH to the corresponding cell, the required power backoff due to power management for the corresponding cell is greater than the upper layer parameter phr-Tx-PowerFactorChange dB since the most recent PHR transmission.

[0561] - [Trigger Event 8] When the activated bandwidth part is switched to the non-dormant downlink bandwidth part of the SCell for any MAC entity having an uplink configured in the dormant bandwidth part.

[0562] - [Trigger Event 9] If the upper layer parameter mpe-Reporting-FR2 is set in the terminal to indicate whether to report MPE P-MPR (Maximum allowed UE output power reduction) to meet the maximum permissible exposure (MPE) in FR2, and mpe-ProhibitTimer is not running, and one or more of the following conditions a) and b) are met:

[0563] a) For the MAC entity, the measured P-MPR applied to satisfy the FR2 MPE requirements specified in Technical Specification TS 38.101-2 for at least one activated FR2-capable cell since the most recent PHR report is greater than or equal to the mpe-Threshold set as a higher layer parameter, or

[0564] b) For the MAC entity, since the most recent PHR transmission performed with a measured P-MPR greater than or equal to the higher layer parameter mpe-Threshold to satisfy the MPE requirements, the measured P-MPR applied to satisfy the FR2 MPE requirements specified in Technical Specification TS 38.101-2 for at least one activated FR2-capable cell has changed by more than the higher layer parameter phr-Tx-PowerFactorChange dB.

[0565] Power headroom reporting may be triggered based on the above trigger events, and the terminal may decide to report power headroom based on the following additional conditions.

[0566] - [Additional conditions for temporary required power backoff] When the required power backoff is temporarily reduced (i.e., up to tens of milliseconds (ms)) due to power management, the MAC entity shall not trigger power headroom reporting. If the required power backoff is temporarily reduced and power headroom reporting is triggered by other trigger events, this results in a P value representing the ratio between the maximum power and the remaining (available) power. CMAX,f,cThe value of / PH must not be temporarily reduced. That is, the PHR must not be triggered due to a temporary power backoff. For example, if the PHR is triggered by another PHR trigger event (such as the expiration of a periodic timer), the PH reflecting the temporary power reduction due to the demand power backoff will not be reported, and the PH excluding the effect due to the demand power backoff will be reported. This condition was added to ensure that

[0567] - [Power headroom reporting conditions according to terminal implementation] If a HARQ process is set based on cg-RetransmissionTimer, and a power headroom report has already been included in the MAC PDU for transmission by the HARQ process, but transmission through the lower layer has not yet been performed, the method of processing the corresponding power headroom report may be determined depending on the terminal implementation.

[0568] If one or more of the trigger events described above occur and a power headroom report is triggered, and the uplink transmission resources allocated through the downlink control information can accommodate the MAC entity and subheader for the power headroom report, the terminal can perform the power headroom report through the uplink resources.

[0569] The above-described PHR trigger events can occur based on cell activation / deactivation, BWP switching, the total amount / change in measured P-MPR applied to meet MPE requirements when supporting FR2, the expiration of a timer for periodic PHR, or the change in DL path loss value measured by periodic DL RS. In particular, a PHR trigger event based on the change in DL path loss value measured by DL RS can be used as a key trigger event that allows the base station to identify changes in the channel quality of uplink and downlink.

[0570] FIG. 14 is a diagram illustrating an example of the operation of a base station and a mobile terminal operating with multiple TRPs, including UL only TRP, according to one embodiment of the present disclosure.

[0571] A TRP (1400, hereinafter TRP1) that supports both uplink and downlink and a UL only TRP (1405, hereinafter TRP2) that supports only uplink reception can be supported for terminals (1410, 1420). In this case, the downlink can be supported by a single TRP (1400) and the uplink can be supported by multiple TRPs (1400, 1405). The path loss (1411) of the uplink and downlink signal for TRP1 measured based on the initial terminal position (1410) and the path loss (1421) of the uplink and downlink signal for TRP1 measured based on the terminal position (1420) to which the terminal has moved thereafter may be the same, or the change between the path loss (1411) and the path loss (1421) may be less than a certain threshold (e.g., a higher layer parameter phr-Tx-PowerFactorChange dB). Meanwhile, the change between the path loss (1412) of the uplink signal for TRP2 measured based on the initial terminal location (1410) and the path loss (1422) of the uplink signal for TRP2 measured based on the subsequently moved terminal location (1420) may be greater than a certain threshold (e.g., the upper layer parameter phr-Tx-PowerFactorChange dB). Depending on the movement direction and distance of the terminal, a situation such as the example illustrated in FIG. 14 may occur.

[0572] As shown in Fig. 14, when a terminal moves, the change in path loss (1411, 1421) of the uplink / downlink signal for TRP1 (1400) may be very small, but the change in path loss (1412, 1422) of the uplink signal for TRP2 (1405), which is a UL only TRP, may be large. In this case, since the terminal can receive the downlink reference signal from TRP1 (1400), the terminal can determine that the change in path loss (1411, 1421) of the uplink / downlink signal is small.

[0573] However, since the terminal cannot receive the downlink reference signal from TRP2 (1405), which is a UL only TRP, as described in the first embodiment, the terminal can determine the path loss for the UL only TRP based on the path loss (1411, 1421) measured by the downlink reference signal received from TRP1 (1400) measured by the terminal and the path loss offset (or d_P as described above in the first embodiment, and pathloss offset and d_P can be regarded as having the same meaning) which is the difference value between the path loss amount between TRP1 (1400) and TRP2 (1405) instructed to the terminal by the base station. Accordingly, if the pathloss offset instructed by the base station to the terminal is not updated, the terminal cannot determine that the change in the path loss (1412, 1422) of the uplink signal for TRP2 (1405), which is a UL only TRP, is large. In this way, since the terminal determines the change in path loss (1412, 1422) for the UL only TRP (1405) based on the path loss (1411, 1421) measured by the downlink reference signal received from TRP1 (1400) associated with TRP 2 (1405) and the pathloss offset instructed by the base station to the terminal, the terminal may not be able to use the method of triggering the power headroom by comparing the path loss change measured through the pathloss reference (e.g., the downlink reference signal received from TRP1 (1400)) with a threshold, as in [Trigger Event 1], in the case where the change in path loss (1412, 1422) for the UL only TRP (1405) is large, as in the example illustrated in FIG. 14.

[0574] In order to solve the problem that power headroom is not triggered due to the small change in path loss measured based on the downlink reference signal associated with the UL only TRP despite the large change in path loss value for the UL only TRP due to the movement of the terminal as described above, the following options or combinations of options may be considered.

[0575] [Option 1] The terminal can change the meaning of the pathloss reference it refers to to determine whether a PHR trigger event has occurred.

[0576] If UL only TRP is operated for the terminal, the base station can set the upper layer parameters for supporting UL only TRP for the terminal. That is, if the upper layer parameters for supporting UL only TRP are set for the terminal, the meaning of the pathloss reference used by the terminal to determine whether the above-described [trigger event 1] has occurred can be changed or expanded. That is, the terminal can interpret the meaning of the pathloss reference by changing or expanding it when determining whether the above-described [trigger event 1] has occurred.

[0577] If [Option 1] is not applied, in the above-described [Trigger Event 1], the DL RS, which is referenced in determining the transmission power of the uplink signal, may be defined as a pathloss reference for determining whether to trigger power headroom reporting. That is, if the change in pathloss measured by the DL RS, which is referenced in determining the transmission power of the uplink signal, is greater than a certain threshold (e.g., a higher layer parameter phr-Tx-PowerFactorChange dB), power headroom reporting may be triggered.

[0578] In case UL only TRP is operated in the terminal according to [Option 1], in addition to the DL RS referred to in determining the transmission power of the uplink signal, the pathloss offset indicated by the base station to the terminal may be considered together when defining the pathloss reference to determine whether to trigger power headroom reporting. That is, if the sum of the pathloss value measured by the DL RS referred to in determining the transmission power of the uplink signal transmitted with UL only TRP and the value indicated by the pathloss offset is greater than a certain threshold (e.g., the upper layer parameter phr-Tx-PowerFactorChange dB), power headroom reporting may be triggered.

[0579] According to [Option 1], whether or not to trigger a power headroom report is determined by considering both the change in the pathloss value measured by the DL RS, which is referenced to determine the transmission power of the uplink signal transmitted with the referenced UL only TRP, and the change in the value indicated by the updated pathloss offset. At this time, the base station can update the pathloss offset and set / instruct the terminal. The base station can update the pathloss offset set / instructed to the terminal through MAC CE. Alternatively, the base station can reset the pathloss offset set / instructed to the terminal through RRC. Alternatively, the base station can instruct the terminal about the pathloss offset set / instructed through DCI. [Option 2] If the pathloss offset for supporting UL only TRP is supported, power headroom reporting can be triggered depending on the change in the value indicated by the updated pathloss offset. That is, if the base station updates the pathloss offset of the terminal as described in [Option 1], power headroom reporting can be triggered.

[0580] At this time, the terminal's decision on whether to trigger power headroom reporting based on the pathloss offset update may be as follows.

[0581] [Option 2-1] If the base station updates the pathloss offset of the terminal, the terminal may trigger a power headroom report. More specifically, according to [Option 2-1], if the base station updates the pathloss offset to the terminal with a MAC CE (or instructs the terminal to do so via RRC reconfiguration or DCI), the terminal may trigger a power headroom report without any additional conditions. In this case, the power headroom report may be triggered regardless of whether a timer (e.g., phr-ProhibitTimer) for prohibiting power headroom reporting has expired. Alternatively, if the timer (e.g., phr-ProhibitTimer) for prohibiting power headroom reporting has expired and the base station updates the pathloss offset to the terminal with a MAC CE (or instructs the terminal to do so via RRC reconfiguration or DCI), the terminal may trigger a power headroom report.

[0582] Alternatively, according to [Option 2-1], if the base station updates the pathloss offset to the terminal with MAC CE (or instructs the terminal via RRC reset or DCI), a new timer (e.g., phr-ProhibitTimerforULTRP, etc.) for prohibiting the triggered power headroom reporting is defined, and the base station can set the timer related to the power headroom reporting triggered based on the pathloss offset to the terminal as a higher layer parameter, and the time unit (e.g., subframe unit) can be set as the value of the timer by the higher layer parameter. When the new timer is set in this way, and the set new timer has expired, and the base station updates the pathloss offset to the terminal with MAC CE (or instructs the terminal via RRC reset or DCI), the terminal can trigger the power headroom reporting.

[0583] [Option 2-2] If the base station updates the pathloss offset of the terminal, and the change in the updated pathloss offset value is greater than a certain / specific threshold, the terminal may trigger a power headroom report. At this time, a certain / specific threshold may be defined according to the phr-Tx-PowerFactorChange value [dB] mentioned above or the value [dB] indicated by the new upper layer parameter phr-Tx-PowerFactorChangeforULTRP. According to [Option 2-2], if the base station updates the pathloss offset to the terminal via MAC CE (or indicates it to the terminal via RRC reconfiguration or DCI), and the change in the updated pathloss offset value is greater than a certain / specific threshold (e.g., the new upper layer parameter phr-Tx-PowerFactorChangeforULTRP dB), the terminal may trigger a power headroom report. Alternatively, the expiration of a timer (e.g. phr-ProhibitTimer or a new timer phr-ProhibitTimerforULTRP) to prohibit power headroom reporting as described in [Option 2-1] with some / specific threshold according to Option [2-2] may be additionally considered in determining whether the terminal will trigger power headroom reporting.

[0584] [Option 2-3] The base station has updated the pathloss offset of the terminal, and the transmission power calculated for the uplink signal to be transmitted with reference to the updated pathloss offset is the maximum transmission power (P) of the terminal. CMAX) is greater than or equal to, the terminal can trigger power headroom reporting. In case of [Option 2-3], unlike [Option 2-1], the terminal can decide whether to report power headroom based on the transmission power value calculated by the terminal for the uplink signal to be transmitted along with the update of the pathloss offset. Alternatively, in addition to the conditions described in [Option 2-3], the terminal can decide whether to report power headroom by additionally considering whether the timer for inhibiting power headroom reporting described in [Option 2-1] or [Option 2-2] has expired.

[0585] [Option 2-4] The base station has updated the pathloss offset of the terminal, and the amount of change in the updated pathloss offset value is greater than a certain threshold, and the transmission power calculated for the uplink signal to be transmitted with reference to the updated pathloss offset is greater than the maximum transmission power (P) of the terminal. CMAX ) is greater than or equal to, the terminal may trigger a power headroom report. In addition to the conditions described in [Option 2-4], the terminal may additionally consider whether the timer for inhibiting power headroom reporting described in [Option 2-1] or [Option 2-2] has expired to decide whether to report power headroom.

[0586] [Option 3] When UL only TRP is operated, power headroom reporting of the terminal may be triggered by DCI. As described above, even if the path loss value measured by the terminal based on the DL RS does not change, the base station may determine that power headroom reporting of the terminal is necessary as the received signal strength (e.g., SNR, SINR, RSRP, etc.) of the UL signal received from the terminal through UL only TRP changes. At this time, the base station may transmit DCI for triggering power headroom reporting to the terminal. The DCI transmitted by the base station to trigger power headroom to the terminal may be scheduling DCI for scheduling PUSCH transmission, such as DCI format 0_1 ​​or DCI format 0_2. The base station may additionally schedule PUSCH resources for transmitting a MAC CE format for power headroom reporting to the terminal through DCI format 0_1 ​​or DCI format 0_2 for triggering power headroom. A base station can add a new DCI area in DCI format 0_1 ​​or DCI format 0_2 to trigger power headroom. A terminal can be scheduled to trigger power headroom reporting based on configuration information of the newly added DCI area. The new area for triggering power headroom reporting of a terminal included in the DCI area can be configured with 1 bit. For example, if the 1-bit new area in the DCI is set to '0', the terminal does not report power headroom, and if the 1-bit new area in the DCI is set to '1', the terminal can report power headroom. Alternatively, if the 1-bit new area in the DCI is set to '1', the terminal does not report power headroom, and if the 1-bit new area in the DCI is set to '0', the terminal can report power headroom.

[0587] <Example 3: Power headroom calculation method for UL-only TRP>

[0588] A method for calculating power headroom for reporting power headroom for uplink channel transmission when supporting UL-only TRP according to one embodiment of the present disclosure is described. This embodiment can be operated in combination with other embodiments described in the present disclosure.

[0589] When a terminal reports power headroom to a base station, the terminal may calculate the reported power headroom value based on the transmission power of an uplink signal that is actually transmitted, or based on a reference format. Whether the terminal calculates the power headroom based on the actual transmission or based on the reference format may be determined by a timeline along which the terminal calculates the power headroom. More specifically, the power headroom for uplink signal transmissions scheduled by DCI received up to a time point prior to the reception of a DCI scheduling a PUSCH on which a MAC CE for reporting power headroom is transmitted may be calculated based on the actual transmission. Alternatively, the power headroom for uplink signal transmissions scheduled by DCI received up to a time point prior to a PUSCH preparation procedure time based on the first symbol of a CG (configured grant) PUSCH may be calculated based on the actual transmission. Alternatively, the boundaries of the timeline may be adjusted and determined depending on the terminal implementation.

[0590] If the terminal calculates the type 1 power headroom (i.e., the power headroom for PUSCH transmission) based on the actual transmission, the terminal can determine the power headroom value for the TRP for which uplink reception and downlink transmission are possible according to the following mathematical expression 16.

[0591] [Equation 16]

[0592]

[0593] Here, the parameter of mathematical expression 16 may mean the same parameter as defined in mathematical expression 4.

[0594] If the terminal calculates the type 1 power headroom (i.e., the power headroom for PUSCH transmission) based on the actual transmission, the terminal can determine the power headroom value for the UL only TRP that can support only uplink reception as in the following mathematical expression 17 or mathematical expression 18.

[0595] [Equation 17]

[0596]

[0597] [Equation 18]

[0598]

[0599] Here, mathematical expressions 17 and 18 define the difference between the maximum transmission power of the terminal and the transmission power of the PUSCH transmitted with UL only TRP as the power headroom value, with reference to mathematical expressions 12 and 13 described in the first embodiment.

[0600] If the terminal calculates the type 1 power headroom (i.e., the power headroom for PUSCH transmission) based on the reference format, the terminal can determine the power headroom value for the TRP for which uplink reception and downlink transmission are possible as shown in the following mathematical expression 19.

[0601] [Equation 19]

[0602]

[0603] Here The terminal is defined in technical specifications TS 38.101-1, TS 38.101-2 and TS 38.101-3 as MPR (Allowed Maximum Power Reduction), A-MPR (Additional Maximum Power Reduction), P-MPR (Power Management Maximum Power Reduction) and ΔT C (Allowed operating band edge transmission power relaxation) to 0dB each (i.e., MPR = 0dB and A-MPR=0dB and P-MPR=0dB and ΔT C =0dB) means the maximum transmission power of the terminal calculated assuming that ul-powerControl is not set in the terminal. If P 0_PUSCH,b,f,c (j) and α b,f,c (j) is P 0_NOMINAL,PUSCH,f,c (0) and p0-PUSCH-AlpharSetId = 0 are determined through PL b,f,c (q d ) is determined by pusch-PathlossReferenceRS-Id = 0 and l = 0. If ul-powerControl is set in the terminal, P 0_PUSCH,b,f,c (j) and α b,f,c (j) And l is determined via p0AlphaSetforPUSCH associated with the indicated TCI-State or TCI-UL-State, and PL b,f,c (q d ) is determined via the PL-RS associated with the indicated TCI-State or TCI-UL-State.

[0604] If the terminal calculates the type 1 power headroom (i.e., the power headroom for PUSCH transmission) based on the reference format, the terminal can determine the power headroom value for the UL only TRP that can support only uplink reception as in the following mathematical expression 20 or mathematical expression 21.

[0605] [Equation 20]

[0606]

[0607] [Equation 21]

[0608]

[0609] In this way, when a power headroom report is triggered for a terminal, the terminal can calculate the power headroom according to one of mathematical equations 16 to 21 according to the TRP in which the PUSCH including the MAC CE format for the power headroom report is transmitted and according to the actual transmission or reference format.

[0610] Or, if the terminal calculates the type 1 power headroom (i.e., the power headroom for PUSCH transmission) as a virtual power headroom for UL only TRP based on the reference format, the terminal may use path loss offset PL instead of Equation 20 or Equation 21. off,b,f,c (q d *) can also be calculated using Equation 19, which does not apply the virtual power headroom calculation. This is because the virtual power headroom is a method of calculating the power headroom based on the reference format when there is no uplink signal transmitted by the terminal as an actual UL only TRP or due to a timeline condition that determines whether to calculate actual or virtual power headroom, the terminal can also calculate the virtual power headroom using only Equation 19 without applying the path loss offset value set as an RRC parameter that the base station knows. That is, if the base station sets a UL only TRP that can only receive uplink to the terminal and supports single-TRP or multi-TRP-based PUSCH transmission including the UL only TRP, and the terminal triggers the power headroom report as described above and performs the power headroom report at the next PUSCH transmission, the terminal can calculate the actual power headroom for the UL only TRP by applying Equation 17 or Equation 18, and the terminal can calculate the virtual power headroom for the UL only TRP by applying Equation 19. At this time, the base station setting UL only TRP to the terminal may mean that (1) the base station can set TCI-State or TCI-UL-State to the terminal, and (2) a new RRC parameter is additionally set to indicate path loss offset in some of these TCI-States or TCI-UL-States.Supporting PUSCH transmission based on a single TRP or multiple TRPs including UL-only TRP may mean that the base station has indicated to the terminal a TCI-State or TCI-UL-State with a new RRC parameter added to indicate a path loss offset to the terminal, and the terminal transmits a PUSCH associated with the TCI-State or TCI-UL-State. The power control parameter P used to calculate the actual power headroom or virtual power headroom by applying the above-described mathematical expression 17, 18, or 19. 0_PUSCH,b,f,c (j) and α b,f,c (j) and l is determined via p0-AlphaSetforPUSCH of Uplink-PowerControl indicated via TCI-State or TCI-UL-State, which is associated with power headroom for UL only TRP, and PL b,f,c (q d ) can be determined via a PL-RS identified by a PathlossReferenceRS-Id indicated via a TCI-State or TCI-UL-State associated with the power headroom for UL only TRP.

[0611] Figures 15 a to 15 d illustrate examples of a terminal reporting triggered power headroom for a single carrier to a base station using DCI-based Dynamic grant PUSCH resources.

[0612] Referring to FIG. 15 a, the terminal can report triggered power headroom information (1500) to the base station using the PUSCH (1502) resource scheduled with the DCI (1501). At this time, the PUSCH (1502) scheduled with the DCI (1501) can be transmitted with a TRP that supports both DL and UL. In this case, the terminal calculates the power headroom by referring to [Mathematical Formula 16] considering the actual transmission of the PUSCH, and transmits the MAC CE including the calculated power headroom value to the scheduled PUSCH (1502).

[0613] Referring to FIG. 15 b, the terminal can report triggered power headroom information (1510) to the base station using the PUSCH (1512) resource scheduled with the DCI (1511). At this time, the PUSCH (1512) scheduled with the DCI (1511) can be transmitted as a UL-only TRP that only supports UL. In this case, the terminal calculates the power headroom by referring to [Mathematical Formula 17] or [Mathematical Formula 18] considering the actual transmission of the PUSCH, and transmits the MAC CE including the calculated power headroom value to the scheduled PUSCH (1512).

[0614] Referring to FIG. 15 c, the terminal may report the triggered power headroom information (1520) to the base station using the PUSCH (1522) resource scheduled with the DCI (1521), or may report the information to the base station using both the first PUSCH (1522) and the second PUSCH (1523) resources. If the first PUSCH (1522) and the second PUSCH (1523) scheduled with the DCI (1521) do not overlap in the time domain or may overlap in the time domain, the two PUSCHs (1522, 1523) may be repeatedly transmitted with different TRPs. If the first PUSCH (1522) and the second PUSCH (1523) scheduled with DCI (1521) do not overlap in the time domain but are scheduled to be transmitted both within a slot n (1525), the UE may perform power headroom calculation differently depending on whether the upper layer parameter twoPHRMode (or a new upper layer parameter introduced considering UL only TRP, e.g., twoPHRModeforULonly, is set. For convenience of explanation, we assume that twoPHRMode is reused, but a new upper layer parameter may be introduced) is set.

[0615] If the first PUSCH (1522) and the second PUSCH (1523) scheduled with DCI (1521) do not overlap in the time domain but are scheduled to be transmitted both within a slot n (1525), and if twoPHRMode is supported by the UE, the UE can calculate both the power headroom for the PUSCH (1522) transmitted in a TRP that both DL and UL can support, and the power headroom for the PUSCH (1523) transmitted in a TRP that only UL can support, based on actual transmission. That is, the UE can calculate the power headroom for the PUSCH (1522) transmitted in a TRP that both DL and UL can support based on [Equation 16], and the power headroom for the PUSCH (1523) transmitted in a TRP that only UL can support, based on [Equation 17] or [Equation 18], and report both of them to the base station.

[0616] If the first PUSCH (1522) and the second PUSCH (1523) scheduled with DCI (1521) do not overlap in the time domain but are scheduled to be transmitted both within a slot n (1525), and the UE does not support twoPHRMode, the UE may calculate only the power headroom for the PUSCH (1522) transmitted in a TRP that both DL and UL can support based on the actual transmission and report it to the base station. That is, the UE calculates the power headroom for the PUSCH (1522) transmitted in a TRP that both DL and UL can support based on [Equation 16] and reports it to the base station, and does not report the power headroom for the PUSCH (1523) transmitted in a TRP that only UL can support. Alternatively, for a support cell that supports UL only TRP, the terminal may calculate and report to the base station the power headroom for the PUSCH (1523) transmitted with the TRP that can only support UL unconditionally based on the actual transmission. That is, the terminal calculates the power headroom for the PUSCH (1523) transmitted with the TRP that can only support UL based on [Equation 17] or [Equation 18] and reports it to the base station, but may not report the power headroom for the PUSCH (1522) transmitted with the TRP that can support both DL and UL.

[0617] If the first PUSCH (1522) and the second PUSCH (1523) scheduled with DCI (1521) overlap in the time domain and are scheduled to be transmitted all within a slot n (1525), the mathematical equations for calculating the power headroom reported by the UE and the reported power headroom, depending on whether twoPHRMode is supported, can be determined in the same way as described above (if the first PUSCH (1522) and the second PUSCH (1523) scheduled with DCI (1521) do not overlap in the time domain but are scheduled to be transmitted all within a slot n (1525)).

[0618] If the first PUSCH (1526) and the second PUSCH (1527) scheduled with DCI (1521) do not overlap in the time domain and both PUSCHs (1526, 1527) are not scheduled to be transmitted within any slot n (1525), the UE may perform power headroom calculation differently depending on whether the upper layer parameter twoPHRMode is set as follows.

[0619] More specifically, if the first PUSCH (1526) and the second PUSCH (1527) scheduled with DCI (1521) do not overlap in the time domain, and both PUSCHs (1526, 1527) are not scheduled to be transmitted within any slot n (1525), and if twoPHRMode is supported by the UE, the UE can calculate the power headroom for the PUSCH (1522) transmitted in a TRP that both DL and UL can support based on the actual transmission, and calculate the power headroom for the PUSCH (1523) transmitted in a TRP that only UL can support based on the reference format. That is, the terminal can calculate the power headroom for the PUSCH (1522) transmitted in a TRP that can support both DL and UL based on [Mathematical Expression 16], and calculate the power headroom for the PUSCH (1523) transmitted in a TRP that can support only UL based on [Mathematical Expression 20] or [Mathematical Expression 21], and report all of these to the base station.

[0620] In addition, if the first PUSCH (1526) and the second PUSCH (1527) scheduled with DCI (1521) do not overlap in the time domain, and if both PUSCHs (1526, 1527) are not scheduled to be transmitted within any slot n (1525), and if twoPHRMode is not supported by the UE, the UE may calculate only the power headroom for the PUSCH (1522) transmitted in the TRP that both DL and UL can support based on the actual transmission and report it to the base station. That is, the UE calculates the power headroom for the PUSCH (1522) transmitted in the TRP that both DL and UL can support based on [Equation 16] and reports it to the base station, but does not report the power headroom for the PUSCH (1523) transmitted in the TRP that only UL can support. Alternatively, for a support cell that supports UL only TRP, the terminal may calculate the power headroom for the PUSCH (1523) transmitted with the UL only TRP based on the actual transmission and report it to the base station. That is, the terminal may calculate the power headroom for the PUSCH (1523) transmitted with the UL only TRP based on [Equation 17] or [Equation 18] and report it to the base station, but may not report the power headroom for the PUSCH (1522) transmitted with the DL and UL both TRPs.

[0621] The first PUSCH (1522) and the second PUSCH (1523) scheduled by DCI (1521) may not overlap in the time domain or may overlap in the time domain, and different data (or TBs or layers) may be transmitted on the two PUSCHs (1522, 1523). Even if the terminal transmits different data through the two PUSCHs (1522, 1523), if the first PUSCH (1522) and the second PUSCH (1523) scheduled by the DCI (1521) do not overlap in the time domain and are scheduled to transmit both PUSCHs (1526, 1527) within a slot n (1525), or if the first PUSCH (1522) and the second PUSCH (1523) scheduled by the DCI (1521) do not overlap in the time domain and are scheduled to transmit both PUSCHs (1526, 1527) within a slot n (1525), or if the first PUSCH (1522) and the second PUSCH (1523) scheduled by the DCI (1521) overlap in the time domain and are scheduled to transmit both PUSCHs (1526, 1527) within a slot n (1525), The power headroom can be calculated in the same way as the power headroom calculation method described for the case where both PUSCHs (1526, 1527) are scheduled to be transmitted) and reported to the base station through the first PUSCH (1522) (or the second PUSCH (1523)). Alternatively, even if different data are transmitted through the two PUSCHs (1522, 1523), the MAC CE including the power headroom can be multiplexed and transmitted on both PUSCHs (1522, 1523).Alternatively, differently from the above, the terminal may calculate the power headroom based on actual transmission only for one PUSCH (i.e., the PUSCH on which MAC CE for power headroom reporting is transmitted or the first PUSCH (1522)) regardless of whether both PUSCHs (1522, 1523) are transmitted within a slot n (1525) and may calculate the power headroom based on reference format for the other PUSCH (i.e., the PUSCH on which MAC CE for power headroom reporting is not transmitted or the second PUSCH (1523)) (e.g., if the terminal supports twoPHRMode). Alternatively, the terminal may calculate and report power headroom based on actual transmission to the base station only for one PUSCH (i.e., the PUSCH on which MAC CE for power headroom reporting is transmitted or the first PUSCH (1522)) regardless of whether both PUSCHs (1522, 1523) are transmitted within a slot n (1525) and may not perform power headroom reporting for the other PUSCH (i.e., the PUSCH on which MAC CE for power headroom reporting is not transmitted or the second PUSCH (1523)) (e.g., if the terminal does not support twoPHRMode).

[0622] Referring to FIG. 15d, the terminal may report the triggered power headroom information (1530) to the base station using the PUSCH (1532) resource scheduled by the DCI (1531), or may report it to the base station using both the first PUSCH (1532) and the second PUSCH (1533) resources. The first PUSCH (1532) and the second PUSCH (1533) scheduled by the DCI (1531) may not overlap in the time domain or may overlap in the time domain, and the two PUSCHs (1532, 1533) may be repeatedly transmitted to different TRPs. If the first PUSCH (1532) and the second PUSCH (1533) scheduled by DCI (1531) do not overlap in the time domain but are scheduled to be transmitted both within a slot n (1535), the UE may perform power headroom calculation differently depending on whether the upper layer parameter twoPHRMode (or a new upper layer parameter introduced considering UL only TRP, e.g., twoPHRModeforULonly, is set. For convenience of explanation, we assume that twoPHRMode is reused, but a new upper layer parameter may be introduced) is set.

[0623] More specifically, if the first PUSCH (1532) and the second PUSCH (1533) scheduled by DCI (1531) do not overlap in the time domain but are scheduled to be transmitted both within a slot n (1535), and if twoPHRMode is supported by the UE, the UE can calculate both the power headroom for the PUSCH (1532) transmitted in the TRP that can only support UL and the power headroom for the PUSCH (1533) transmitted in the TRP that can support both DL and UL based on the actual transmission. That is, the UE can calculate the power headroom for the PUSCH (1532) transmitted in the TRP that can only support UL based on [Equation 17] or [Equation 18] and the power headroom for the PUSCH (1533) transmitted in the TRP that can support both DL and UL based on [Equation 16], and report both of these to the base station.

[0624] In addition, if the first PUSCH (1532) and the second PUSCH (1533) scheduled by DCI (1531) do not overlap in the time domain but are scheduled to be transmitted both within a slot n (1535), and if the twoPHRMode is not supported by the UE, the UE may calculate and report to the base station only the power headroom for the PUSCH (1532) transmitted in the TRP that can only be supported by UL based on the actual transmission. That is, the UE may calculate and report to the base station the power headroom for the PUSCH (1532) transmitted in the TRP that can only be supported by UL based on [Equation 17] or [Equation 18], but may not report the power headroom for the PUSCH (1533) transmitted in the TRP that can support both DL and UL. Alternatively, for a support cell that supports UL only TRP, the terminal may unconditionally calculate the power headroom for the PUSCH (1533) transmitted with a TRP that both DL and UL can support based on the actual transmission and report it to the base station. That is, the terminal calculates the power headroom for the PUSCH (1533) transmitted with a TRP that both DL and UL can support based on [Mathematical Formula 16] and reports it to the base station, but may not report the power headroom for the PUSCH (1532) transmitted with a TRP that only UL can support.

[0625] If the first PUSCH (1532) and the second PUSCH (1533) scheduled by DCI (1531) overlap in the time domain and are scheduled to be transmitted all within a slot n (1535), the mathematical equations for calculating the power headroom reported by the terminal and the reported power headroom depending on whether twoPHRMode is supported can be determined in the same way as the power headroom calculation method described above (the case where the first PUSCH (1532) and the second PUSCH (1533) scheduled by DCI (1531) do not overlap in the time domain but are scheduled to be transmitted all within a slot n (1535).

[0626] If the first PUSCH (1536) and the second PUSCH (1537) scheduled by DCI (1531) do not overlap in the time domain and both PUSCHs (1536, 1537) are not scheduled to be transmitted within any slot n (1535), the UE may perform power headroom calculation differently depending on whether the upper layer parameter twoPHRMode is set as follows.

[0627] More specifically, if the first PUSCH (1536) and the second PUSCH (1537) scheduled by DCI (1531) do not overlap in the time domain, and both PUSCHs (1536, 1537) are not scheduled to be transmitted within any slot n (1535), and if twoPHRMode is supported by the UE, the UE can calculate the power headroom for the PUSCH (1532) transmitted in a TRP that can support only UL based on the actual transmission, and calculate the power headroom for the PUSCH (1533) transmitted in a TRP that can support both DL and UL based on the reference format. That is, the terminal can calculate the power headroom for the PUSCH (1532) transmitted in a TRP that can support only UL based on [Mathematical Formula 17] or [Mathematical Formula 18], calculate the power headroom for the PUSCH (1533) transmitted in a TRP that can support both DL and UL based on [Mathematical Formula 19], and report all of these to the base station.

[0628] In addition, if the first PUSCH (1536) and the second PUSCH (1537) scheduled by DCI (1531) do not overlap in the time domain, and if both PUSCHs (1536, 1537) are not scheduled to be transmitted within any slot n (1535), and if twoPHRMode is not supported by the UE, the UE may calculate and report to the base station only the power headroom for the PUSCH (1532) transmitted in the TRP that can only be supported by UL based on the actual transmission. That is, the UE calculates the power headroom for the PUSCH (1532) transmitted in the TRP that can only be supported by UL based on [Equation 17] or [Equation 18], and reports it to the base station, and does not report the power headroom for the PUSCH (1533) transmitted in the TRP that can support both DL and UL.

[0629] In addition, for a support cell that supports UL only TRP, the terminal may calculate the power headroom for the PUSCH (1533) transmitted with a TRP that can be supported in both DL and UL based on the actual transmission and report it to the base station. That is, the terminal calculates the power headroom for the PUSCH (1533) transmitted with a TRP that can be supported in both DL and UL based on [Mathematical Formula 16] and reports it to the base station, but may not report the power headroom for the PUSCH (1532) transmitted with a TRP that can be supported in UL only.

[0630] The first PUSCH (1532) and the second PUSCH (1533) scheduled by DCI (1531) may not overlap in the time domain or may overlap in the time domain, and different data (or TBs or layers) may be transmitted through the two PUSCHs (1532, 1533). Even if the terminal transmits different data on two PUSCHs (1532, 1533), the power headroom is calculated in the same way as the power headroom calculation method described above (when the first PUSCH (1532) and the second PUSCH (1533) scheduled by DCI (1531) overlap in the time domain and are scheduled to be both transmitted within a slot n (1535), or when the first PUSCH (1532) and the second PUSCH (1533) scheduled by DCI (1531) do not overlap in the time domain and are scheduled to be both transmitted within a slot n (1535), or when the first PUSCH (1532) and the second PUSCH (1533) scheduled by DCI (1531) do not overlap in the time domain and are scheduled to be neither transmitted within a slot n (1535), and this is multiplied by the power headroom for the first PUSCH (1532) (or the two The MAC CE with power headroom can be multiplexed and transmitted on both PUSCHs (1532, 1533) even if different data are transmitted on the two PUSCHs (1532, 1533).Alternatively, differently from the above, the terminal may calculate the power headroom based on actual transmission only for one PUSCH (i.e., the PUSCH on which MAC CE for power headroom reporting is transmitted or the first PUSCH (1532)), regardless of whether both PUSCHs (1532, 1533) are transmitted within a slot n (1535), and may calculate the power headroom based on reference format for the other PUSCH (i.e., the PUSCH on which MAC CE for power headroom reporting is not transmitted or the second PUSCH (1533)) (e.g., if the terminal supports twoPHRMode). Alternatively, the terminal may calculate and report power headroom to the base station based on actual transmission only for one PUSCH (i.e., the PUSCH on which MAC CE for power headroom reporting is transmitted or the first PUSCH (1532)), regardless of whether both PUSCHs (1532, 1533) are transmitted within a slot n (1535), and may not perform power headroom reporting for the other PUSCH (i.e., the PUSCH on which MAC CE for power headroom reporting is not transmitted or the second PUSCH (1533)) (e.g., if the terminal does not support twoPHRMode).

[0631] If power headroom is reported to the base station through a MAC CE format for multiple entry-based power headroom reporting considering multiple supporting cells, when the terminal calculates the power headroom report for a supporting cell supporting UL only TRP based on actual transmission, the terminal determines the power headroom according to [Mathematical Expression 17] or [Mathematical Expression 18], and when calculating based on a reference format, the terminal determines the power headroom according to [Mathematical Expression 20] or [Mathematical Expression 21].

[0632] Although the third embodiment specifically describes a method for reporting type 1 power headroom, the mathematical equations for calculating power headroom described in the third embodiment can be similarly applied to calculating power headroom for SRS transmission when reporting type 3 power headroom based on SRS. In addition, the terminal can calculate power headroom by selecting one of various modified power headroom calculation methods for SRS transmission according to the TRP in which the PUSCH including the power headroom MAC CE format for type 3 is transmitted.

[0633] <Example 4: Method for configuring a MAC CE format for reporting power headroom for UL-only TRP>

[0634] A method for configuring a MAC CE format for reporting power headroom for uplink channel transmission when supporting UL-only TRP according to one embodiment of the present disclosure is described. This embodiment can be operated in combination with other embodiments described in the present disclosure.

[0635] As described in the third embodiment, depending on whether the terminal supports twoPHRMode, two power headroom values ​​considering multiple TRPs may be reported to the base station, or only one power headroom value may be reported to the base station.

[0636] If the terminal supports twoPHRMode and reports two power headrooms to the base station when reporting power headroom, the first power headroom value and the second power headroom value can be determined by the following rules.

[0637] [Rule 1] The UE may define the first power headroom value as the power headroom for transmission of the first PUSCH (1522, 1526, 1532, 1536) among the multiple PUSCHs illustrated in FIG. 15, and may define the second power headroom value as the power headroom for transmission of the second PUSCH (1523, 1527, 1533, 1537). Alternatively, the UE may define the first power headroom value as the power headroom for a PUSCH transmitted in association with the first SRS resource set (or a lower SRS resource set having a lower SRS resource set ID), and may define the second power headroom value as the power headroom for a PUSCH transmitted in association with the second SRS resource set (or a higher SRS resource set having a higher SRS resource set ID).

[0638] [Rule 2] The terminal may define the first power headroom value as the power headroom for PUSCH (1522, 1526, 1533, 1537) transmissions that are transmitted in TRPs that can support both DL and UL among multiple PUSCHs, and may define the second power headroom value as the power headroom for PUSCH (1523, 1527, 1532, 1536) transmissions that are transmitted in TRPs that can support only UL among multiple PUSCHs. Here, the terminal may identify TRPs that can support both DL and UL and TRPs that can support only UL by whether or not a pathloss offset is applied to calculate the transmission power for the corresponding uplink transmission during uplink transmission. The terminal may identify the pathloss offset to be applied to a TRP that can support only UL by referring to a higher layer parameter or an indicated TCI state as described in the first embodiment.

[0639] [Rule 3] A terminal may report power headroom to a base station using an enhanced MAC CE format. When twoPHRMode is supported, the terminal may use an additional bit in the MAC CE format for reporting power headroom to the base station to indicate the type of TRP to which each power headroom is associated. For example, the MAC CE format for reporting power headroom to the base station may be supplemented with one bit corresponding to an area for reporting each power headroom value. The one bit corresponding to the first power headroom area may indicate whether the value indicated by the corresponding power headroom area is calculated based on an uplink transmission transmitted with a TRP that supports both DL and UL or based on an uplink transmission transmitted with a TRP that supports only UL. The additional bit for indicating the type of TRP to which each power headroom is associated may be either a new bit area added or a reserved bit reused.

[0640] FIG. 16 illustrates an example of an enhanced MAC CE format with an additional field for indicating the type of TRP associated with each power headroom region when twoPHRMode is supported according to one embodiment of the present disclosure.

[0641] The MAC CE format (1600) illustrates a PHR MAC CE for reporting two power headrooms with a single entry. The terminal can report power headroom levels to the base station through multiple PH fields (1601, 1604) for reporting quantized power headroom values. The uplink transmission associated with the power headroom reported in each PH field can be determined according to [Rule 1] or [Rule 2] described above. If the upper layer parameter mpe-Reporting-FR2 for MPE reporting is configured for a serving cell operating in FR2, the UE sets the P field (1602) to 0 if a P-MPR value smaller than P-MPR_00 defined in the RAN4 standard (e.g., TS 38.101-2) is applied to satisfy the MPE requirement for PH reporting corresponding to the serving cell operating in FR2, and sets the P field (1602) to 1 if a P-MPR value larger than P-MPR_00 defined in the RAN4 standard is applied to satisfy the MPE requirement for PH reporting corresponding to the serving cell operating in FR2. If the terminal calculates the PH value reported to the corresponding PH area (1601), (1604) based on real transmission, the terminal sets the V area (1603) to 0, and if the terminal calculates the PH value reported to the corresponding PH area (1601, 1604) based on a reference format, the terminal sets the V area (1603) to 1.

[0642] The terminal maximum transmit power P used to determine the reported PH value CMAX,f,cTo report, determine the nominal UE transmit power levels as defined in RAN4 specifications (e.g., TS 38.133), and P CMAX,f,c The index for the nominal UE transmit power level determined through the area (1605) can be reported to the base station. If the upper layer parameter mpe-Reporting-FR2 for MPE reporting is set for a serving cell operating in FR2, and the P area (1602) is set to 1, the terminal can set the MPE area (1606) to indicate the power backoff applied to the PH report corresponding to the serving cell operating in FR2 in order to satisfy the MPE requirement. At this time, the terminal determines the P-MPR level defined in the RAN4 standard (e.g., TS 38.101-2) and reports the index thereof to the base station through the MPE area (1606).

[0643] T of Fig. 16 iAreas (1607, 1608) may be defined as bit areas for indicating the type of TRP to which each power headroom is associated according to [Rule 3]. That is, T1 (1607) is 1 bit corresponding to the first power headroom area (1601), and T1 (1607) may indicate whether the value indicated by the corresponding power headroom area (1601) is calculated based on uplink transmission transmitted with a TRP supporting both DL and UL or based on uplink transmission transmitted with a TRP supporting only UL. For example, if T1 (1607) is indicated as 0, it may mean that the first power headroom area (1601) is calculated based on uplink transmission transmitted with a TRP supporting both DL and UL. If T1 (1607) is indicated as 1, it may mean that the first power headroom region (1601) was calculated based on uplink transmissions transmitted in a TRP that supports only UL (or vice versa). Similarly, T2 (1608) is a 1-bit corresponding to the second power headroom region (1604), and T2 (1608) may indicate whether the value indicated by the corresponding power headroom region (1604) was calculated based on uplink transmissions transmitted in a TRP that supports both DL and UL or based on uplink transmissions transmitted in a TRP that supports only UL. For example, if T2 (1608) is indicated as 0, it may mean that the second power headroom region (1604) was calculated based on uplink transmissions transmitted in a TRP that supports both DL and UL. If T2 (1608) is indicated as 1, it may mean that the second power headroom region (1604) is calculated based on uplink transmissions transmitted with TRPs that support UL only (or vice versa).

[0644] Rules 1 to 3 described above may be combined and used. For example, Rules 1 and 3 may be combined, or Rules 2 and 3 may be combined to form a MAC CE format.

[0645] In order to support UL only TRP as described in the first to fourth embodiments and to support enhanced power headroom reporting to effectively support it, additional terminal capabilities may be required, and when the terminal supports the additional terminal capabilities, the terminal can support UL only TRP and perform enhanced power headroom reporting. The terminal capabilities to support UL only TRP and the terminal capabilities to support enhanced power headroom reporting can be reported to the base station using separate parameters for terminal capability reporting. That is, the terminal can support UL only TRP but not enhanced power headroom reporting. Alternatively, the terminal can support both UL only TRP and the corresponding enhanced power headroom reporting. The additional terminal capability reporting to support enhanced power headroom may include both a new power headroom trigger condition and a method for configuring a MAC CE for power headroom, or the new power headroom trigger condition and a method for configuring a MAC CE for power headroom may be reported separately via parameters for individual terminal capability reporting.

[0646] The above flowchart illustrates exemplary methods that can be implemented according to the principles of the present disclosure, and various modifications may be made to the methods depicted in the flowcharts of the present disclosure. For example, although depicted as a series of steps, 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.

[0647] FIG. 17 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0648] Referring to FIG. 17, the terminal may include a transceiver, which refers to a terminal receiving unit (17-00) and a terminal transmitting unit (17-10), a memory (not shown), and a terminal processing unit (17-05, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (17-00, 17-10), the memory, and the terminal processing unit (17-05) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

[0649] A transceiver unit can transmit and receive signals to and from a base station. The signals may include control information and data. To this end, the transceiver unit may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is merely one embodiment of the transceiver unit, and the components of the transceiver unit are not limited to the RF transmitter and RF receiver.

[0650] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit a signal output from the processor through the wireless channel.

[0651] Memory can store programs and data necessary for the terminal's operation. Furthermore, memory can store control information or data included in signals transmitted and received by the terminal. Memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0652] Additionally, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiments. For example, the processor can receive DCI consisting of two layers and control components of the terminal to simultaneously receive multiple PDSCHs. There may be multiple processors, and the processors can perform component control operations of the terminal by executing programs stored in memory.

[0653] FIG. 18 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0654] Referring to FIG. 18, the base station may include a transceiver, which refers to a base station receiver (18-00) and a base station transmitter (18-10), a memory (not shown), and a base station processing unit (18-05, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver units (18-00, 18-10), the memory, and the base station processing unit (18-05) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

[0655] The transceiver can transmit and receive signals with the terminal. Here, the signals may include control information and data. To this end, the transceiver may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.

[0656] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit the signal output from the processor through the wireless channel.

[0657] Additionally, a base station according to one embodiment of the present disclosure may be a base station operating with multiple TRPs. In this case, the base station may operate a TRP capable of both uplink reception and downlink transmission, and a TRP that supports only uplink reception. The TRP operated by the base station and capable of both uplink reception and downlink transmission may include the base station reception unit (18-00) and the base station transmission unit (18-10) of FIG. 18. Furthermore, the TRP operated by the base station and supporting only the uplink reception function may include only the base station reception unit (18-00) of FIG. 18. For example, if a base station operates one TRP capable of both uplink reception and downlink transmission and one TRP that supports only uplink reception, the base station may include (1) a base station reception unit (18-00) and a base station transmission unit (18-10) that constitute a TRP capable of both uplink reception and downlink transmission, and (2) a base station reception unit (18-00) that constitutes a TRP that supports only uplink reception.

[0658] The memory can store programs and data necessary for the operation of the base station. Furthermore, the memory can store control information or data included in signals transmitted and received by the base station. The memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0659] The processor can control a series of processes to enable the base station to operate according to the aforementioned embodiments of the present disclosure. For example, the processor can configure two layers of DCIs containing allocation information for multiple PDSCHs and control each component of the base station to transmit them. There may be multiple processors, and the processors can perform component control operations of the base station by executing programs stored in memory.

[0660] The methods according to the claims of the present disclosure or the embodiments described in the disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0661] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the claims or embodiments of the present disclosure.

[0662] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0663] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.

[0664] In the specific embodiments of the present disclosure described above, components included in the embodiments are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0665] Meanwhile, the embodiments of the present disclosure disclosed in the present disclosure and the drawings are merely specific examples to easily explain the technical contents of the present disclosure and to help the understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-mentioned respective embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and another embodiment can be combined with each other to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure can be combined with each other to operate a base station and a terminal. In addition, other modifications based on the technical idea of ​​the above-mentioned embodiments can be implemented with each other in other systems, such as an FDD LTE system, a TDD LTE system, a 5G or NR system.

[0666] Meanwhile, the order of description in the drawings explaining the method of the present disclosure does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel.

[0667] Alternatively, the drawings illustrating the method of the present disclosure may omit some components and include only some components without detracting from the essence of the present disclosure.

[0668] In addition, the method of the present disclosure may be implemented by combining some or all of the contents included in each embodiment within a scope that does not harm the essence of the present disclosure.

[0669] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only, and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will appreciate that the present disclosure can be readily modified into other specific forms without altering the technical spirit or essential characteristics of the present disclosure. The scope of the present disclosure is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included within the scope of the present disclosure.

Claims

1. In a method performed by a terminal in a wireless communication system, the method comprises: A step of receiving downlink control information (DCI) for scheduling resources for transmitting a first physical uplink shared channel (PUSCH) associated with a first transmission and reception point (TRP) for uplink transmission and downlink reception of the terminal and a second PUSCH associated with a second TRP for only uplink transmission of the terminal; and A step of transmitting a PHR including at least one of a first power headroom report (PHR) associated with the first PUSCH or a second PHR associated with the second PUSCH, The above first PHR is calculated based on the downlink path loss calculated using the reference signal, The above second PHR is calculated based on the downlink path attenuation and path attenuation offset, A method in which the first PHR and the second PHR are both set to be transmitted, the first PUSCH and the second PUSCH are both transmitted in slot n in which the PHR is transmitted, and the first PUSCH is scheduled at an earlier time than the second PUSCH, wherein the PHR is transmitted including the first PHR calculated based on actual transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH.

2. In paragraph 1, A method in which the PHR is transmitted, wherein the first PHR and the second PHR are both set to be transmitted, the first PUSCH and the second PUSCH are both transmitted in the slot n, and the second PUSCH is scheduled at an earlier time than the first PUSCH, and the PHR includes the first PHR calculated based on an actual transmission of the first PUSCH and the second PHR calculated based on an actual transmission of the second PUSCH.

3. In paragraph 2, When both the first PHR and the second PHR are set to be transmitted and only the first PUSCH is transmitted in the slot n, the PHR is transmitted including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the reference transmission of the second PUSCH, A method in which the PHR is transmitted, including the first PHR calculated based on reference transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH, when both the first PHR and the second PHR are set to be transmitted and only the second PUSCH is transmitted in the slot n.

4. In paragraph 3, If only one of the above first PHR and the above second PHR is set to be transmitted: The PHR is transmitted, including only the PHR related to the PUSCH scheduled at an earlier point in time among the first PUSCH and the second PUSCH, A method in which, when the PUSCH scheduled at the earlier time is transmitted in the slot n, the PHR associated with the PUSCH scheduled at the earlier time is calculated based on the actual transmission of the PUSCH scheduled at the earlier time.

5. In a method performed by a base station in a wireless communication system, the method comprises: A step of transmitting downlink control information (DCI) for scheduling resources for transmitting a first physical uplink shared channel (PUSCH) associated with a first transmission and reception point (TRP) for uplink transmission and downlink reception of a terminal and a second PUSCH associated with a second TRP for only uplink transmission of the terminal; and A step of receiving a PHR including at least one of a first power headroom report (PHR) associated with the first PUSCH or a second PHR associated with the second PUSCH, The above first PHR is calculated based on the downlink path loss calculated using the reference signal, The above second PHR is calculated based on the downlink path attenuation and path attenuation offset, A method in which the first PHR and the second PHR are both set to be transmitted, the first PUSCH and the second PUSCH are both transmitted in slot n in which the PHR is transmitted, and the first PUSCH is scheduled at an earlier time than the second PUSCH, wherein the PHR is transmitted including the first PHR calculated based on actual transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH.

6. In paragraph 5, A method in which the PHR is transmitted, wherein the first PHR and the second PHR are both set to be transmitted, the first PUSCH and the second PUSCH are both transmitted in the slot n, and the second PUSCH is scheduled at an earlier time than the first PUSCH, and the PHR includes the first PHR calculated based on an actual transmission of the first PUSCH and the second PHR calculated based on an actual transmission of the second PUSCH.

7. In paragraph 6, When both the first PHR and the second PHR are set to be transmitted and only the first PUSCH is transmitted in the slot n, the PHR is transmitted including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the reference transmission of the second PUSCH, A method in which the PHR is transmitted, including the first PHR calculated based on reference transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH, when both the first PHR and the second PHR are set to be transmitted and only the second PUSCH is transmitted in the slot n.

8. In paragraph 7, If only one of the above first PHR and the above second PHR is set to be transmitted: The PHR is transmitted, including only the PHR related to the PUSCH scheduled at an earlier point in time among the first PUSCH and the second PUSCH, A method in which, when the PUSCH scheduled at the earlier time is transmitted in the slot n, the PHR associated with the PUSCH scheduled at the earlier time is calculated based on the actual transmission of the PUSCH scheduled at the earlier time.

9. In a wireless communication system, the terminal, transceiver; and Including a controller connected to the above transceiver, The above controller, Receive downlink control information (DCI) for scheduling resources for transmitting a first physical uplink shared channel (PUSCH) associated with a first transmission and reception point (TRP) for uplink transmission and downlink reception of the terminal and a second PUSCH associated with a second TRP for only uplink transmission of the terminal; configured to transmit a PHR including at least one of a first power headroom report (PHR) associated with the first PUSCH or a second PHR associated with the second PUSCH, The above first PHR is calculated based on the downlink path loss calculated using the reference signal, The above second PHR is calculated based on the downlink path attenuation and path attenuation offset, A terminal in which the PHR is transmitted, including the first PHR calculated based on actual transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH, when both the first PUSCH and the second PUSCH are set to be transmitted, and the first PUSCH and the second PUSCH are both transmitted in slot n in which the PHR is transmitted, and the first PUSCH is scheduled at an earlier time than the second PUSCH.

10. In paragraph 9, A terminal in which the PHR is transmitted, wherein the first PHR and the second PHR are both set to be transmitted, the first PUSCH and the second PUSCH are both transmitted in the slot n, and the second PUSCH is scheduled at an earlier time than the first PUSCH, and the PHR includes the first PHR calculated based on actual transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH.

11. In paragraph 10, When both the first PHR and the second PHR are set to be transmitted and only the first PUSCH is transmitted in the slot n, the PHR is transmitted including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the reference transmission of the second PUSCH, A terminal in which the PHR is transmitted, including the first PHR calculated based on reference transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH, when both the first PHR and the second PHR are set to be transmitted and only the second PUSCH is transmitted in the slot n.

12. In paragraph 11, If only one of the above first PHR and the above second PHR is set to be transmitted: The PHR is transmitted, including only the PHR related to the PUSCH scheduled at an earlier point in time among the first PUSCH and the second PUSCH, A terminal, wherein, if the PUSCH scheduled at the earlier time is transmitted in the slot n, the PHR associated with the PUSCH scheduled at the earlier time is calculated based on the actual transmission of the PUSCH scheduled at the earlier time.

13. In a wireless communication system, at a base station, the base station, transceiver; and Including a controller connected to the above transceiver, The above controller, A step of transmitting downlink control information (DCI) for scheduling resources for transmitting a first physical uplink shared channel (PUSCH) associated with a first transmission and reception point (TRP) for uplink transmission and downlink reception of a terminal and a second PUSCH associated with a second TRP for only uplink transmission of the terminal; and A step of receiving a PHR including at least one of a first power headroom report (PHR) associated with the first PUSCH or a second PHR associated with the second PUSCH, The above first PHR is calculated based on the downlink path loss calculated using the reference signal, The above second PHR is calculated based on the downlink path attenuation and path attenuation offset, A base station, wherein the first PHR and the second PHR are both set to be transmitted, the first PUSCH and the second PUSCH are both transmitted in slot n in which the PHR is transmitted, and the first PUSCH is scheduled at an earlier time than the second PUSCH, wherein the PHR is transmitted including the first PHR calculated based on actual transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH.

14. In paragraph 13, A base station, wherein the PHR is transmitted including the first PHR calculated based on actual transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH, when both the first PUSCH and the second PUSCH are set to be transmitted, and the first PUSCH and the second PUSCH are both transmitted in the slot n, and the second PUSCH is scheduled at an earlier time than the first PUSCH.

15. In paragraph 14, When both the first PHR and the second PHR are set to be transmitted and only the first PUSCH is transmitted in the slot n, the PHR is transmitted including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the reference transmission of the second PUSCH, A base station, wherein the PHR is transmitted including the first PHR calculated based on reference transmission of the first PUSCH and the second PHR calculated based on actual transmission of the second PUSCH, when both the first PHR and the second PHR are set to be transmitted and only the second PUSCH is transmitted in the slot n.

Images