Method and apparatus for transmitting and receiving uplink signal in a wireless communication system supporting cooperative communication

Abstract

A method and apparatus for transmitting / receiving a UL signal in a wireless communication system supporting cooperative communication are provided. A method for communicating by a UE includes transmitting, to a base station, UE capability information for changing at least one of a UL beam, a transmission power, or a frequency; receiving, from the base station, information on an offset in a time domain based on the UE capability information; and transmitting, to a plurality of TRPs, a UL signal by changing at least one of the UL beam, the transmission power, and the frequency in a case where the offset in the time domain is greater than or equal to a time for changing according to the UE capability.

Description

Technical Field

[0001] This disclosure generally relates to a method and apparatus for transmitting and receiving uplink (UL) signals in a wireless communication system. Background Technology

[0002] To meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as 'super 4G networks' or 'post-LTE systems'.

[0003] 5G communication systems are considered to be implemented in higher frequency (millimeter wave (mmWave)) bands (e.g., the 60GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G communication systems.

[0004] In addition, in 5G communication systems, development is underway to improve system networks based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receiver interference cancellation.

[0005] As mentioned above, with the development of wireless communication systems, various services can be provided, thus requiring a scheme for changing the beam and a scheme for adjusting the transmit power of user equipment (UE) to smoothly transmit UL control signals to each transmit-receive point (TRP) in a network cooperative communication system. Summary of the Invention

[0006] Technical issues

[0007] Therefore, one aspect of this disclosure is to provide a method and apparatus for efficiently transmitting / receiving UL signals in a wireless communication system that supports cooperative communication.

[0008] Another aspect of this disclosure is to provide a method and apparatus for efficiently repeating the transmission / reception of UL signals in a wireless communication system that supports cooperative communication.

[0009] Another aspect of this disclosure is to provide a method and apparatus for efficiently transmitting / receiving UL signals using time-domain offsets in a wireless communication system that supports cooperative communication.

[0010] Another aspect of this disclosure is to provide a method and apparatus for changing at least one of a UL beam, transmit power, and frequency in a wireless communication system during a time-domain offset based on the UE capability, and for transmitting / receiving UL signals.

[0011] Solution to the problem

[0012] According to an aspect of this disclosure, a method is provided for communication by a base station in a wireless communication system supporting cooperative communication. The method includes: receiving from a UE capability information for changing at least one of an uplink beam, transmit power, or frequency; determining a time-domain offset for uplink signal transmission based on the UE capability information; and transmitting information about the determined offset to the UE.

[0013] According to another aspect of this disclosure, a method is provided for communication by a UE in a wireless communication system supporting cooperative communication. The method includes: transmitting UE capability information to a base station for changing at least one of an uplink beam, transmit power, or frequency; receiving information about an offset in the time domain from the base station based on the UE capability information; and transmitting a UL signal to a plurality of TRPs by changing at least one of the uplink beam, transmit power, and frequency if the offset in the time domain is greater than or equal to the time of the change according to the UE capability.

[0014] According to another aspect of this disclosure, a base station is provided for use in a wireless communication system supporting cooperative communication. The base station includes a transceiver and a processor, the processor being configured to: receive, via the transceiver, UE capability information from a UE for changing at least one of an uplink beam, transmit power, or frequency; determine, based on the UE capability information, a time-domain offset for uplink signal transmission; and transmit, via the transceiver, information about the determined offset to the UE.

[0015] According to another aspect of this disclosure, a UE is provided for use in a wireless communication system supporting cooperative communication. The UE includes a transceiver and a processor, the processor being configured to: transmit UE capability information via the transceiver to a base station for changing at least one of an uplink beam, transmit power, or frequency; receive information about an offset in the time domain from the base station via the transceiver based on the UE capability information; and, if the offset in the time domain is greater than or equal to the time of the change according to the UE capability, transmit uplink signals via the transceiver to a plurality of TRPs by changing at least one of the uplink beam, transmit power, and frequency. Attached Figure Description

[0016] The above and other aspects, features, and advantages of certain embodiments of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, wherein:

[0017] Figure 1 The basic structure of the time-frequency radio resource domain according to an embodiment is shown;

[0018] Figure 2 The time slot structure according to an embodiment is shown;

[0019] Figure 3 The configuration of the bandwidth portion (BWP) according to an embodiment is shown;

[0020] Figure 4 A method for changing the BWP according to an embodiment is shown;

[0021] Figure 5 A control resource set (CORESET) in which the downlink control channel is transmitted is shown according to an embodiment;

[0022] Figure 6 The illustration shows multiple overlapping physical UL control channel (PUCCH) resources used for hybrid automatic repeat request acknowledgment (HARQ-ACK) transmission of the physical downlink shared channel (PDSCH) when multi-slot repetition is not configured, according to an embodiment.

[0023] Figure 7 The overlapping PUCCH resources are shown according to an embodiment when multiple time slot repetitions are configured;

[0024] Figure 8 The switching time for switching between a transmission off state and a transmission on state is shown according to an embodiment when the UE transmits a UL;

[0025] Figure 9A , Figure 9B , Figure 9C , Figure 9D and Figure 9E The switching time for a change in transmit power, a change in transmit resource block (RB), or a frequency hopping in a first frequency range (FR) (FR1) is shown according to an embodiment;

[0026] Figure 10A , Figure 10B , Figure 10C and Figure 10D The switching time for a change in transmit power, a change in transmit RB, or a frequency hopping in the second FR (FR2) is shown according to an embodiment;

[0027] Figure 11 The illustration shows repeated transmission of PUCCH in a time slot when an offset indicated by the base station is applied, according to an embodiment.

[0028] Figure 12A Media Access Control (MAC) control element (CE) according to an embodiment is shown for activating new higher-layer parameters for performing transmit power control for each TRP in FR1;

[0029] Figure 13A and Figure 13B A new MACCE for activating PUCCH transmit power control parameters is shown according to an embodiment;

[0030] Figure 14A A base station method according to an embodiment is shown for determining the offset of UL signal transmission based on the UE capability reported by the UE and providing the offset to the UE;

[0031] Figure 14B and Figure 14C A UE method for transmitting UL signals to one or more TRPs based on an offset configured by a base station, according to an embodiment, is illustrated.

[0032] Figure 15A A UE method is shown in which the transmit power of each TRP is determined in FR1 by a default transmit power control method and a PUCCH signal is transmitted to one or more TRPs, according to an embodiment.

[0033] Figure 15B A base station method for receiving a PUCCH in FR1 via one or more TRPs, according to an embodiment, is shown.

[0034] Figure 16A and Figure 16B A UE method for transmitting PUCCH signals using one or more TRPs in FR1 using PUCCH-SpatialRelationInfo according to an embodiment is shown;

[0035] Figure 16C and Figure 16D This illustrates a base station method for receiving PUCCH via one or more TRPs in FR1 using PUCCH-SpatialRelationInfo according to an embodiment;

[0036] Figure 17A and Figure 17B A UE method is illustrated according to an embodiment in which configuration information for controlling separate power control is used to send a PUCCH signal to one or more TRPs in FR1;

[0037] Figure 17C and Figure 17D A base station method for receiving PUCCH signals via one or more TRPs in FR1 using configuration information for controlling separate power control, according to an embodiment, is illustrated.

[0038] Figure 18A A UE method is illustrated according to an embodiment in which configuration information for controlling separate power control is used to send a PUCCH signal to one or more TRPs in FR1;

[0039] Figure 18B A base station method for receiving PUCCH signals via one or more TRPs in FR1 using configuration information for controlling separate power control, according to an embodiment, is illustrated.

[0040] Figure 19A A UE method for transmitting PUCCH signals to one or more TRPs using PUCCH power configuration information and control information in FR1 according to an embodiment is illustrated.

[0041] Figure 19B A base station method for receiving PUCCH signals via one or more TRPs using PUCCH power configuration information and control information in FR1, according to an embodiment, is illustrated.

[0042] Figure 20 A UE in a wireless communication system according to an embodiment is shown; and

[0043] Figure 21 A base station in a wireless communication system according to an embodiment is shown. Detailed Implementation

[0044] Various embodiments of this disclosure are described in detail below with reference to the accompanying drawings. Hereinafter, with respect to the methods and apparatus presented in the embodiments, the embodiments are described as example methods for transmitting UL control signals to each TRP in a network cooperative communication system. However, without being limited to each embodiment, combinations of all or some of the embodiments presented herein can be used for data channel, control channel, and reference signal (RS) transmission / reception methods corresponding to other additional services.

[0045] Furthermore, as will be known to those skilled in the art, modifications can be made to the embodiments without significantly departing from the scope of this disclosure, and such modifications may be applicable.

[0046] When it is determined that the subject matter of this disclosure is unclear, a detailed description of known techniques or functions may be omitted.

[0047] The terminology used herein is defined with reference to the functionality of this disclosure and may be replaced by other terms depending on the intent or practice of the user or operator. Therefore, the terminology should be defined based on the overall disclosure.

[0048] For similar reasoning, some elements may be exaggerated or shown schematically. The size of each element does not necessarily reflect its actual size. Throughout the figures, the same reference numerals may be used to refer to the same elements.

[0049] The advantages and features of this disclosure, as well as methods for achieving these advantages and features, can be understood from the embodiments described below in conjunction with the accompanying drawings. However, this disclosure is not limited to the embodiments disclosed herein, and various modifications can be made thereto. The embodiments disclosed herein are provided merely to inform those skilled in the art of the category of this disclosure.

[0050] The boxes and combinations of flowcharts in each flowchart can be executed by computer program instructions. Since the computer program instructions can be incorporated into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions, which execute via the processor of the computer or other programmable data processing equipment, generate a system for performing the functions described in conjunction with the boxes of each flowchart. Since the computer program instructions can be stored in a computer-usable or computer-readable storage device that can be oriented towards the computer or other programmable data processing equipment to implement its functions in a specified manner, the instructions stored in the computer-usable or computer-readable storage device can produce an article including instruction means for performing the functions described in conjunction with the boxes of each flowchart. Because the computer program instructions can be incorporated into a computer or other programmable data processing equipment, a process executed by the computer is generated when a series of operational steps are executed by the computer or other programmable data processing equipment, and the instructions operating the computer or other programmable data processing equipment can provide steps for performing the functions described in conjunction with the boxes of each flowchart.

[0051] Furthermore, each box can represent a module, segment, or portion of code that includes one or more executable instructions for performing a specific logical function. Additionally, in some alternative execution examples, the functions mentioned in the boxes can appear in different orders. For example, depending on the corresponding function, two boxes shown consecutively can be executed substantially simultaneously or in reverse order.

[0052] As used herein, the term "cell" can refer to a software element or a hardware element, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). A cell plays a certain role. However, the term "cell" is not limited to referring to software or hardware elements.

[0053] A unit can be configured in a storage medium that can be addressed or configured to reproduce one or more processors. For example, a "unit" includes elements such as software elements, object-oriented software elements, class elements and task elements, procedures, functions, properties, processes, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data schemas, tables, arrays, and variables.

[0054] The functionality provided in a component or unit can be combined with additional components, or can be divided into sub-components or sub-units. Furthermore, a component or unit can be implemented to reproduce one or more central processing units (CPUs) in a device or secure multimedia card. A "unit" may include one or more processors.

[0055] In this document, a base station can be an entity that allocates resources to a UE and can include a gNode B (gNB), an evolved Node B (eNode B or eNB), a Node B, a Radio Access Unit, a Base Station Controller, a Transmitting Point (TP), a TRP, or a node on a network. A base station can be a network entity that includes an Integrated Access and Backhaul Host (IAB Host) and IAB nodes. The IAB Host is a gNB that provides network access to the UE through a network of backhaul and access links in a New Radio (NR) system. An IAB node is a RAN node that supports NR backhaul links to an IAB Host or another IAB node and supports NR access links to the UE. The UE is radio-connected via IAB nodes and can send or receive data from an IAB Host connected to at least one IAB node via backhaul links.

[0056] The UE may include a terminal, mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions, but is not limited to the examples above.

[0057] This disclosure relates to a 5G communication system for supporting data rates higher than those of 4G communication systems. This disclosure can be applied to smart services based on 5G communication technology and Internet of Things (IoT) related technologies (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail businesses, security and safety-related services, etc.).

[0058] Furthermore, as will be known to those skilled in the art, embodiments may be modified without significantly departing from the scope of this disclosure, and such modifications may be applicable to other communication systems, such as LTE or LTE-A.

[0059] For ease of description, some terms and names defined in the 3GPP LTE standard may be used. However, this disclosure is not limited to such terms and names and may be equally applied to systems conforming to other standards.

[0060] Wireless communication systems have evolved from voice-centric services to broadband wireless communication systems that provide high data rates and high-quality packet data services, such as 3GPP High-Speed ​​Packet Access (HSPA), LTE or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-A, LTE-pro, 3GPP2 High-Speed ​​Packet Data (HRPD), Ultra Mobile Broadband (UMB), and the Institute of Electrical and Electronics Engineers (IEEE) 802.16e communication standard.

[0061] As a representative example of such a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) for the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) for the UL. UL can refer to the radio link through which the UE transmits data or control signals to the base station (e.g., eNodeB), and DL refers to the radio link through which the base station transmits data or control signals to the UE. This multiple access scheme allocates and operates time-frequency resources carrying data or control information for each user in a non-overlapping manner, i.e., maintaining orthogonality, thereby distinguishing the data and / or control information for each user.

[0062] Post-LTE communication systems, such as 5G communication systems, should simultaneously support various requirements of both users and service providers. Services considered for 5G communication systems include enhanced mobile broadband (eMBB), massive machine-type communications (MMTC), and ultra-reliable low-latency communications (URLLC).

[0063] eMBB is designed to provide further enhanced data transmission rates compared to LTE, LTE-A, or LTE-pro. For example, for a single base station, eMBB for a 5G communication system should provide a peak data rate of 20Gbps on DL and 10Gbps on UL.

[0064] 5G communication systems should also provide increased user-perceived data rates, as well as peak data rates. To meet this requirement, various transmit (TX) / receive (RX) technologies and MIMO may need to be further enhanced. While LTE uses up to 20MHz of TX bandwidth in the 2GHz band to transmit signals, 5G communication systems employ wider frequency bandwidths in the 3GHz to 6GHz or higher bands to meet the data rates required by 5G communication systems.

[0065] Furthermore, BWP technology is gaining attention. This technology divides the entire carrier frequency band into several bands, which can be supported by the base station for each UE when the base station supports wide-bandwidth frequencies. In other words, if the base station supports BWP and a particular UE has limited bandwidth, BWP can support a smaller frequency band for the UE, reducing UE power consumption while decreasing the frequency band by changing the BWP. It also allows for seamless support of various services for a UE by changing the BWP, while supporting different frame structures in each of the several BWPs. BWP technology can be applied to control or data channels that correspond one-to-one between a predetermined UE and a predetermined base station. Additionally, BWP can be applied to data and control channels that transmit common signals from the base station to multiple UEs in the system, such as synchronization signals, physical broadcast channels (PBCH), and system information, to reduce base station power consumption by transmitting only through BWPs configured for such control and data channels.

[0066] Furthermore, mMTC is designed to support application services such as IoT within 5G communication systems. To effectively deliver IoT, mMTC should support a large number of UEs within a cell, enhance UE coverage and battery life, and reduce UE costs. IoT UEs can be attached to various sensors or devices to provide communication functionality, and therefore, mMTC should support multiple UEs per cell (e.g., 1,000,000 UEs / km). 2 Because UEs supporting mMTC are often located in shadow areas not covered by the cell, such as basements of buildings, depending on the nature of the service, they require wider coverage compared to other services provided by 5G communication systems. UEs supporting mMTC should also have relatively long battery life, such as 10 to 15 years, due to the need for low cost and the potential difficulty of frequent battery replacements.

[0067] URLLC is a mission-critical, cellular-based wireless communication service. URLLC can be used for remote control of robots or machinery, industrial automation, drones, remote healthcare, or emergency alerts. Therefore, URLLC should provide extremely low latency and extremely high reliability communication. For example, services supporting URLLC should simultaneously meet an air interface latency of less than 0.5 milliseconds and 10... -5 Or even lower packet error rates. Therefore, for services supporting URLLC, 5G communication systems need to provide relatively shorter Transmission Time Intervals (TTIs) than other services, while ensuring reliable communication links by allocating extensive resources in the frequency band.

[0068] The three services mentioned above in 5G communication systems—eMBB, URLLC, and mMTC—can also be multiplexed and transmitted within a single system. In this case, different TX / RX schemes and TX / RX parameters can be used to meet their different requirements. For the definitions of the technical terms used in this document, relevant 3GPP standards can be referenced.

[0069] Figure 1 The basic structure of the time-frequency radio resource domain according to an embodiment is shown.

[0070] refer to Figure 1 The horizontal axis refers to the time domain, and the vertical axis refers to the frequency domain. In both the time and frequency domains, the basic unit of a resource can be defined using an OFDM symbol (or Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) symbol) 102 on the time axis (also called the time domain) and a subcarrier 103 on the frequency axis (also called the frequency domain). In the frequency domain, (For example, 12 consecutive resource elements (REs) can constitute an RB 104. In the time domain...) A series of consecutive OFDM symbols can form a subframe 110.

[0071] exist Figure 1 middle, This refers to the number of OFDM symbols per subframe 110 for the subcarrier spacing setting (μ). A more detailed description of the resource structure used in 5G systems can be found in Section 4 of the TS 38.211 standard.

[0072] Figure 2 A time slot structure according to an embodiment is shown.

[0073] refer to Figure 2 A frame 200, defined as 10 ms, can consist of a total of 10 subframes 201, each subframe being defined as 1 ms. A time slot 202 or 203 can be defined as 14 OFDM symbols (that is, the number of symbols per time slot). A subframe 201 may consist of one or more time slots 202 and 203, and the number of time slots 202 and 203 in each subframe 201 may vary depending on μ (204 or 205), which is a setting value for the subcarrier spacing.

[0074] exist Figure 2In the diagram, the time slot structure (204) with μ=0 and the time slot structure (205) with μ=1 are shown as the set subcarrier spacing values. When μ=0 (204), a subframe 201 consists of one time slot 202, while when μ=1 (205), a subframe 201 consists of two time slots (203). In other words, the number of time slots in each subframe depends on the set subcarrier spacing value μ. The number of time slots per frame can vary, and therefore, the number of time slots per frame can also vary. They can be different. Depending on the subcarrier spacing μ, and It can be defined in Table 1 below.

[0075] [Table 1]

[0076]

[0077] Figure 3 A configuration for BWP according to an embodiment is shown.

[0078] refer to Figure 3 The UE bandwidth 300 is divided into two BWPs, for example, BWP#1 (BWP#1) 305 and BWP#2 (BWP#2) 310. The base station can configure one or more BWPs in the UE, and can configure the information shown in Table 2 below for each BWP.

[0079] [Table 2]

[0080]

[0081] However, beyond this, various other BWP-related parameters can be configured for the UE. The base station can transmit information to the UE via higher-level signaling (e.g., Radio Resource Control (RRC) signaling). At least one of the one or more configured BWPs can be activated. Whether a configured BWP is activated can be transmitted from the base station to the UE semi-statically via RRC signaling or dynamically via DL control information (DCI).

[0082] Before being connected via RRC, the UE can be configured with an initial BWP by the base station via the Master Information Block (MIB) for initial access. More specifically, the UE can receive configuration information for the search space and CORESET in which the Physical DL Control Channel (PDCCH) can be transmitted, to receive system information (e.g., Residual System Information (RMSI) or System Information Block (SIB) 1) for initial access via the MIB. Each of the control region and search space configured with the MIB can be considered as ID 0. The base station can provide the UE with configuration information via the MIB, such as frequency allocation information, time allocation information, and the parameter set for control region #0. In addition, the base station can provide the UE with configuration information for the timing and listening period of control region #0 via the MIB, i.e., configuration information for search space #0. The UE can regard the FR set to control region #0 obtained from the MIB as the initial BWP for initial access. In this case, the ID of the initial BWP can be considered as 0.

[0083] The BWP configuration supported by the 5G communication system described above can be used for various purposes.

[0084] When the bandwidth supported by the UE is less than the system bandwidth, this can be supported through BWP configuration. For example, when the base station configures the UE with the frequency location of the BWP (configuration information 2), the UE can send / receive data at a specific frequency location within the system bandwidth.

[0085] To support different parameter sets, the base station can configure multiple BWPs for the UE. For example, to support data transmission / reception using 15kHz and 30kHz subcarrier intervals, the base station can configure the UE to have two bandwidths, namely 15kHz and 30kHz subcarrier intervals. Different BWPs can be frequency-division multiplexed, and the BWP configured for the corresponding subcarrier interval can be activated when data is transmitted / received at a specific subcarrier interval.

[0086] To reduce UE power consumption, the base station can configure the UE with BWPs of different bandwidth sizes. For example, when the UE supports bandwidths exceeding a very large bandwidth (e.g., 100MHz) and uses all of that bandwidth to send / receive data, considerable power consumption may occur. In particular, using a large 100MHz bandwidth to listen to unnecessary DL control channels when there is no service is very inefficient in terms of power consumption. To reduce UE power consumption, the base station can configure the UE with a relatively small bandwidth BWP, such as a 20MHz BWP. In the absence of service, the UE can perform listening in the 20MHz bandwidth, and if data is available, the UE can send / receive data in the 100MHz bandwidth according to instructions from the base station.

[0087] In the method for configuring the BWP, the UE, prior to RRC connection, can receive configuration information for the initial bandwidth via the MIB during the initial access phase. More specifically, the UE can be configured with a control area for the DL control channel (which can be interchanged with a control resource set or CORESET), where the DCI of the scheduling system information block (SIB) can be transmitted from the MIB of the PBCH. The bandwidth configured by the MIB can be considered as the initial BWP, and the UE can receive the PDSCH transmitting the SIB via the configured initial BWP. The initial BWP can be used for other system information (OSI), paging and random access, and for receiving SIBs.

[0088] If the UE is configured with one or more BWPs, the base station can use the BWP indicator in the DCI to indicate a change in the BWP to the UE. For example, when the UE's currently active BWP is Figure 3 When BWP#1 305 is received, the base station can use the BWP indicator in the DCI to indicate BWP#2 310 to the UE, and the UE can change the BWP to BWP#2 702, which is indicated by the BWP indicator in the received DCI.

[0089] As described above, since DCI-based BWP changes can be indicated by the DCI scheduling PDSCH or Physical UL Shared Channel (PUSCH), the UE should be able to receive or transmit the DCI-scheduled PDSCH or PUSCH without failure in the changed BWP if a BWP change request is received. To this end, the standard specifies the delay time T required for changing the BWP. BWP The requirements can be defined as follows.

[0090] [Table 3]

[0091]

[0092] Depending on the UE's capabilities, the delay requirement for BWP changes supports either Type 1 or Type 2. The UE can report the supported BWP delay time types to the base station.

[0093] Figure 4 A method for changing the BWP according to an embodiment is shown.

[0094] refer to Figure 4 If the UE receives the DCI (415) including the BWP change indicator in time slot n according to the above requirement of changing the delay time according to the BWP, then the UE can proceed no later than time slot n+T. BWPThe time is changed to a new BWP indicated by the BWP change indicator, and transmission / reception can be performed on the data channel scheduled by DCI in the new BWP 410.

[0095] When scheduling a data channel with the new BWP 410, the base station can consider the UE's BWP change delay time (T). BWP )420 determines the time-domain resource allocation (TDRA) for the data channel. That is, when scheduling a data channel with a new BWP 410, in the method for determining the TDRA of the data channel, the base station can schedule the corresponding data channel in time slots 435 and 440 after the BWP change delay time. Therefore, the UE may not expect the DCI indication indicating the BWP change to be less than the BWP change delay time (T). BWP The time slot offset (K0 or K2) of 420. K0 represents the time slot offset in DL, and K2 represents the time slot offset in UL.

[0096] If the UE has already received a DCI indicating a BWP change (e.g., DCI format 1_1 or 0_1), then during the time period from the third symbol of the slot in which the PDCCH including the DCI has been received to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by the TDRA indicator field in the DCI, the UE may not perform any transmission or reception. For example, if the UE receives a DCI indicating a BWP change in slot n, and the slot offset value indicated by the DCI is K, then the UE may not perform any transmission or reception from the third symbol of slot n to the symbols preceding slot n+K (i.e., the last symbol of slot n+K-1).

[0097] The UE can be configured with one or more BWPs by the base station, and can be further configured with transmission / reception parameters to be used for each configured BWP (e.g., UL / DL link data channel and control channel related configuration information). For example, Figure 3 As shown, when the UE is configured with BWP#1 305 and BWP#2 310, the UE can be configured with transmit / receive parameter #1 for BWP#1 and transmit / receive parameter #2 for BWP#2 310. When BWP#1 305 is active, the UE can perform transmit / receive with the base station based on transmit / receive parameter #1, and when BWP#2 310 is active, the UE can perform transmit / receive with the base station based on transmit / receive parameter #2. These transmit / receive parameters can be referred to as configuration information or control information for the BWP.

[0098] More specifically, the following parameters can be configured by the base station for the UE.

[0099] For UL BWP, the following information can be configured.

[0100] [Table 4]

[0101]

[0102] As shown in Table 4 above, the UE can be configured by the base station with cell-specific (or cell-common or common) transmission-related parameters (e.g., Random Access Channel (RACH), PUCCH, UL Data Channel (PUSCH) related parameters) (corresponding to BWP-UplinkCommon). In addition, the UE can be configured by the base station with UE-specific (or dedicated) transmission-related parameters (e.g., PUCCH, PUSCH, unlicensed UL transmission (licensed PUSCH), probe RS (SRS) related parameters) (corresponding to BWP-UplinkDedicated).

[0103] For DL ​​BWP, the following information can be configured.

[0104] [Table 5]

[0105]

[0106] As shown in Table 5 above, the UE can be configured by the base station with cell-specific (or cell-common or common) reception-related parameters (e.g., PDCCH, DL data channel (PDSCH) related parameters) (corresponding to BWP-DownlinkCommon). Furthermore, the UE can be configured by the base station with UE-specific (or dedicated) reception-related parameters (e.g., PDCCH, PDSCH, unlicensed DL data transmission based on PDSCH (e.g., semi-persistent scheduling PDSCH), radio link listening (RLM) related parameters) (corresponding to BWP-UplinkDedicated).

[0107] Figure 5 A CORESET is shown according to an embodiment in which the downlink control channel is transmitted.

[0108] refer to Figure 5Two CORESETs (CORESET#1 501 and CORESET#2 502) are configured in a time slot 520 on the time axis, and the UE BWP 510 is configured on the frequency axis. CORESETs 501 and 502 can be configured as specific frequency resources 503 within the entire system BWP 510 on the frequency axis. CORESETs 501 and 502 can be configured with one or more OFDM symbols on the time axis, and one or more OFDM symbols can be defined as the CORESET duration 504. CORESET#1 501 can be configured as a CORESET length of two symbols, and CORESET#2 502 can be configured as a CORESET length of one symbol.

[0109] In the aforementioned 5G system, the CORESET can be configured by the base station to the UE via higher-level signaling (e.g., system information, MIB, RRC signaling) (hereinafter referred to as "higher-level"). Configuring the CORESET for the UE includes providing the UE with information such as the CORESET ID, the CORESET frequency location, and the CORESET symbol length. For example, the information provided for configuring the CORESET is shown in Table 6.

[0110] [Table 6]

[0111]

[0112] In 5G systems, CORESET can include NRBCORESET RB in the frequency domain and N in the time axis. symb A CORESET consists of {1, 2, 3} symbols. A CCE can include 6 Resource Element Groups (REGs), and a REG can be defined as 1 RB during one OFDM symbol. Within a CORESET, REGs can be indexed in time-priority order, starting from REG index 0 (lowest RB) of the first OFDM symbol of the CORESET.

[0113] In 5G systems, both interleaving and non-interleaving schemes are supported as transmission schemes for the PDCCH. The base station can configure the UE to perform interleaved or non-interleaved transmission for each CORESET via higher-layer signaling. Interleaving can be performed within each REG bundle unit. A REG bundle can be defined as a set of one or more REGs. The UE can determine the control channel element (CCE)-REG mapping scheme in the corresponding CORESET based on whether interleaved or non-interleaved transmission is configured by the base station, as shown in Table 7 below.

[0114] [Table 7]

[0115]

[0116] The basic unit of a DL control channel, the REG, can include all REs to which the DCI is mapped, as well as the area to which the demodulation RS (DMRS) used to decode the REs is mapped. Three DMRS REs can be included in one REG. Depending on the aggregation level (AL), the number of CCEs transmitting the PDCCH can be 1, 2, 4, 8, or 16, and different numbers of CCEs can be used to implement link adaptation for the DL control channel. For example, if AL = L, then a DL control channel can be transmitted via L CCEs.

[0117] The UE should detect signals without knowing the information of the DL control channels, and for blind decoding, a search space is defined to indicate the set of CCEs. The search space can include a set of candidate control channels, which consist of the CCEs that the UE should attempt to decode at a given aggregation level. Since there are several aggregation levels to bundle, such as 1, 2, 4, 8, or 16 CCEs, the UE has multiple search spaces. The search space set can be defined as the set of search spaces for all configured aggregation levels.

[0118] The search space can be categorized into a common search space and a UE-specific search space. A predetermined group of UEs or all UEs can search the common search space of the PDCCH to receive cell common control information, such as paging messages, or dynamic scheduling for system information. For example, a UE can search the common search space of the PDCCH to receive PDSCH scheduling allocation information for transmitting SIBs that include cell service provider information. Regarding the common search space, since a certain group of UEs or all UEs should receive the PDCCH, the common search space can be defined as a previously agreed set of CCEs.

[0119] Scheduling allocation information for a 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 specifically defined by the UE and contains various system parameters and UE identification information (e.g., ID).

[0120] In 5G systems, parameters for the search space of PDCCH can be configured by the base station to the UE via higher-level signaling (e.g., SIB, MIB, or RRC signaling). For example, the base station can configure the number of PDCCH candidates at each aggregation level L, the listening period of the search space, the listening timing of symbol cells in the time slots of the search space, the search space type (e.g., public search space or UE-specific search space), the combination of Radio Network Temporary Identifier (RNTI) and DCI format to be listened to in the search space, and the CORESET index to be listened to in the search space. For example, the parameters for the search space of PDCCH may include the information shown in Table 8.

[0121] [Table 8]

[0122]

[0123]

[0124] Based on the configuration information, the base station can configure one or more search space sets for the UE. The base station can configure search space set 1 and search space set 2 for the UE. Search space set 1 can be configured to allow the UE to listen for DCI format A scrambled with X-RNTI in a common search space, and search space set 2 can be configured to allow the UE to listen for DCI format B scrambled with Y-RNTI in a UE-specific search space. In X-RNTI and Y-RNTI, "X" and "Y" can correspond to one of various RNTIs.

[0125] Based on the above configuration information, one or more search space sets can exist in a public search space or a UE-specific search space. For example, search space set #1 and search space set #2 can be configured as a public search space, while search space set #3 and search space set #4 can be configured as UE-specific search spaces.

[0126] In the public search space, combinations of DCI formats and RNTI, as shown below, can be monitored, but are not limited to the examples below.

[0127] - DCI format with cyclic redundancy check (CRC) scrambled by cell (C)-RNTI, configured scheduling (CS)-RNTI, semi-persistent (SP)-channel state information (CSI)-RNTI, random access (RA)-RNTI, temporary cell (TC)-RNTI, paging (P)-RNTI, and system information (SI)-RNTI. 0_0 / 1_0

[0128] - DCI format 2_0 with CRC scrambled by Slot Format Indicator (SFI) - RNTI

[0129] - DCI format 2_1 with CRC scrambled by interrupt (INT)-RNTI

[0130] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI and TPC-PUCCH-RNTI

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

[0132] Within a UE-specific search space, combinations of DCI formats and RNTI can be monitored, but are not limited to the examples below.

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

[0134] - RNTIs specified in DCI format 1_0 / 1_1 with CRCs scrambled by C-RNTI, CS-RNTI, and TC-RNTI can be defined and used as follows.

[0135] C-RNTI: Used for scheduling UE-specific PDSCH

[0136] TC-RNTI: Used for scheduling UE-specific PDSCH

[0137] CS-RNTI: UE-specific PDSCH used for scheduling semi-static configurations

[0138] RA-RNTI: Used for scheduling PDSCH during the random access phase.

[0139] P-RNTI: Used to schedule the PDSCH sent for paging.

[0140] SI-RNTI: PDSCH used to schedule the transmission of system information.

[0141] INT-RNTI: Used to notify whether to puncture the PDSCH (notifying the UE of a transmission interruption on the PDSCH).

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

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

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

[0145] The DCI format described above can follow the definitions shown in Table 9 below.

[0146] [Table 9]

[0147]

[0148] For example, a base station can use DCI format 0_0 or DCI format 0_1 ​​to assign a PUSCH to a cell.

[0149] When DCI format 0_0 is transmitted using a CRC scrambled by at least one of C-RNTI, CS-RNTI, or Modulation Coding Scheme (MCS) C-RNTI (MCS-C-RNTI), the following information is included:

[0150] -DCI format identifier (1 bit): DCI format indicator, which is always set to 0.

[0151] - Frequency domain resource allocation (determines payload based on frequency axis resource allocation): indicates frequency axis resource allocation. It refers to the size of the active UL BWP.

[0152] - Time-domain resource allocation (4 bits): Indicates the allocation of time-domain resources.

[0153] - Frequency hopping flag (1 bit): Indicates whether the PUSCH assigned by the corresponding DCI is frequency hopping on the frequency axis.

[0154] -MCS (5 bits): Indicates the modulation order and coding rate used for PUSCH transmission.

[0155] - New Data Indicator (NDI) (1 bit) field: depends on whether NDI is switched to indicate whether PUSCH is an initial transmission or a retransmission.

[0156] - Redundant Version (RV) (2 bits): Indicates the RV used for PUSCH transmission.

[0157] -HARQ process number (4 bits): Indicates the HARQ process number used for PUSCH transmission.

[0158] - Transmit Power Control (TPC) command for PUSCH scheduling (2 bits): An indicator used to adjust the transmission strength of PUSCHs allocated by DCI.

[0159] -UL / Supplementary UL (SUL) Indicator (1 bit): Indicates whether a SUL transfer is performed on the PUSCH allocated by the corresponding DCI. When a transfer using SUL is not performed, the bit length of the corresponding area is 0 bits.

[0160] When DCI format 0_1 ​​is transmitted together with a CRC scrambled by at least one of C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI, it includes the following information:

[0161] - DCI format identifier (1 bit): This is the DCI format indicator, which is always set to 0.

[0162] - Carrier indicator (0 or 3 bits): Indicates the component carrier (CC) (or cell) transmitted by the PUSCH allocated by the corresponding DCI.

[0163] -UL / SUL indicator (0 or 1 bit): Indicates whether a SUL transfer is performed on the PUSCH assigned by the corresponding DCI.

[0164] -BWP indicator (0, 1, or 2 bits): Indicates the BWP that is transmitted through the PUSCH allocated by the corresponding DCI.

[0165] - Frequency domain resource allocation (determines payload based on frequency axis resource allocation): indicates frequency axis resource allocation. It is the size of the activity DL BWP.

[0166] - Time-domain resource allocation (0, 1, 2, 3, or 4 bits): Indicates the time-domain resource allocation.

[0167] - Frequency hopping flag (0 or 1 bit): Indicates whether the PUSCH assigned by the corresponding DCI is frequency hopping on the frequency axis.

[0168] -MCS (5 bits): Indicates the modulation order and coding rate used for PUSCH transmission.

[0169] -NDI (1 bit) field: depends on whether PUSCH is switched to indicate whether it is an initial transmission or a retransmission.

[0170] -RV (2 bits): Indicates the RV used for PUSCH transmission.

[0171] -HARQ process number (4 bits): Indicates the HARQ process number used for PUSCH transmission.

[0172] - 1DL Allocation Index (DAI) (1 or 2 bits): Indicates the DAI used for HARQ-ACK codebook generation.

[0173] - 2nd DAI (0 or 2 bits: indicates the DAI used for HARQ-ACK codebook generation)

[0174] - TPC command (2 bits) for scheduling PUSCH: An indicator used to adjust the transmission strength of PUSCH allocated by DCI.

[0175] -SRS Resource Indicator (depending on SRS usage configuration): Indicates the transport precoding configuration of the PUSCH allocated by the corresponding DCI via SRS resources.

[0176] - Precoding information and number of layers (0, 1, 2, 3, 4, 5, or 6 bits): Indicates the transmission precoding information and transmission layer number of the PUSCH assigned by the corresponding DCI.

[0177] - Antenna Port (2, 3, 4, or 5 bits): Indicates the transmission of DMRS ports and code division multiplexing (CDM) groups for data that have not been allocated a PUSCH by the corresponding DCI.

[0178] -SRS Request (2 or 3 bits): Indicates the SRS resource transmitted via the corresponding DCI request.

[0179] -CSI Request (0, 1, 2, 3, 4, 5, or 6 bits): Indicates the CSI report trigger status transmitted via the corresponding DCI request.

[0180] - Code Block Group (CBG) Transmission Information (0, 2, 4, 6, or 8 bits): An indicator of whether the CBG is transmitted in the PUSCH allocated by the corresponding DCI.

[0181] - Phase Tracking RS (PTRS) - DMRS Association (0 or 2 bits): Indicates the port connection relationship between the PTRS and DMRS of the PUSCH assigned by the corresponding DCI.

[0182] -Beta_offset indicator (0 or 2 bits): Indicates the offset value used when multiplexing HARQ-ACK or CSI reports to PUSCH.

[0183] -DMRS sequence initialization (0 or 1 bit): Indicator for selecting DMRS scrambling ID.

[0184] -UL Shared Channel (SCH) Indicator (0 or 1 bit): Indicates whether the PUSCH allocated by the corresponding DCI includes UL-SCH.

[0185] For example, a base station can use DCI format 1_0 or DCI format 1_1 to allocate (schedule) a PDSCH to a cell.

[0186] When DCI format 1_0 is transmitted together with a CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI, it includes the following information:

[0187] -DCI format identifier (1 bit): DCI format indicator, which is always set to 1.

[0188] -Frequency domain resource allocation ( (Bit): Indicates frequency axis resource allocation. When DCI format 1_0 is detected in a specific UE search space... It is the size of the active DL BWP, otherwise, This is the initial DL BWP size. Refer to the frequency axis resource allocation for the detailed method.

[0189] When all frequency domain resource allocation areas are set to 1, DCI format 1_0 indicates the command used for the random access procedure, and all remaining areas are set as follows.

[0190] - Random Access Preamble Index (6 bits): Indicates the index of the preamble used to perform random access.

[0191] -UL / SUL indicator (1 bit): If the values ​​of the random access preamble index area are not all set to 0, and the UE has set the higher-level parameter ServingCellConfig to supplementaryUplink, then the corresponding area indicates the UL carrier used to transmit PRACH.

[0192] -SS / PBCH Index (6 bits): If none of the values ​​in the random access preamble index area are set to 0, the corresponding area indicates the SS / PBCH (i.e., synchronization signal block (SSB)) used for PRACH transmission.

[0193] -PRACH Mask Index (4 bits): If none of the values ​​in the random access preamble index region are set to 0, the corresponding region indicates the RACH period associated with the SS / PBCH indicated by the SS / PBCH index.

[0194] If none of the bits allocated to the frequency domain resources are set to 1, the remaining regions are set as follows.

[0195] - Time-domain resource allocation (4 bits): Indicates the time-domain resource allocation as described above.

[0196] - Virtual RB (VRB) to Physical RB (PRB) mapping (1 bit): 0 indicates non-interleaved, 1 indicates interleaved VRB to PRB mapping.

[0197] -MCS (5 bits): Indicates the modulation sequence and coding rate used for PDSCH transmission.

[0198] -NDI (1 bit) field: Depends on whether the NDI field is switched to indicate whether PDSCH is an initial transmission or a retransmission.

[0199] -RV (2 bits): Indicates the RV used for PDSCH transmission.

[0200] -HARQ process number (4 bits): Indicates the HARQ process number used for PDSCH transmission.

[0201] -DAI (2 bits): DAI indicator

[0202] - TPC command (2 bits) used to schedule PUCCH: PUCCH power control indicator

[0203] -PUCCH Resource Indicator (3 bits): Indicates one of the eight resources configured by the higher layer.

[0204] -PDSCH to HARQ_feedback timing indicator (3 bits): Indicates one of the eight feedback timing offsets set by the higher layer for the HARQ feedback timing indicator.

[0205] When DCI format 1_1 is transmitted together with a CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI, it includes the following information:

[0206] -DCI format identifier (1 bit): DCI format indicator, which is always set to 1.

[0207] - Carrier indicator (0 or 3 bits): Indicates the CC (or cell) whose PDSCH is being transmitted by the corresponding DCI.

[0208] -BWP indicator (0, 1, or 2 bits): Indicates the BWP that is transmitted via the PDSCH allocated by the corresponding DCI.

[0209] - Frequency domain resource allocation (determines payload based on frequency axis resource allocation): indicates frequency axis resource allocation. This refers to the size of the activity's deep learning (DL) resource allocation (BWP). For the detailed method described, refer to the frequency axis resource allocation section.

[0210] - Time-domain resource allocation (0, 1, 2, 3, or 4 bits): Indicates the time-domain resource allocation as described above.

[0211] -VRB to PRB mapping (0 or 1 bit): 0 indicates non-interleaved, 1 indicates interleaved VRB to PRB mapping. This is 0 bits when the frequency axis resource allocation is set to resource type 0.

[0212] -PRB Bundle Size Indicator (0 or 1 bit): This is 0 bits when the higher-level parameter prb-BundlingType is not set or is set to 'static', and 1 bit when the higher-level parameter is set to 'dynamic'.

[0213] - Rate Matching Indicator (0, 1, or 2 bits): Indicates the rate matching pattern.

[0214] - Zero Power (ZP) CSI-RS Trigger (0, 1, or 2 bits): Indicator used to trigger non-periodic ZP CSI-RS.

[0215] -For Transport Block (TB) 1:

[0216] -MCS (5 bits): Indicates the modulation sequence and coding rate used for PDSCH transmission.

[0217] -NDI (1 bit) field: Depends on whether the NDI field is switched to indicate whether PDSCH is an initial transmission or a retransmission.

[0218] -RV (2 bits): Indicates the RV used for PDSCH transmission.

[0219] -For TB 2:

[0220] MCS (5 bits): Indicates the modulation order and coding rate used for PDSCH transmission.

[0221] -NDI (1 bit) field: Depends on whether the NDI field is switched to indicate whether PDSCH is an initial transmission or a retransmission.

[0222] -RV (2 bits): Indicates the RV used for PDSCH transmission.

[0223] -HARQ process number (4 bits): Indicates the HARQ process number used for PDSCH transmission.

[0224] -DAI (0, 2, or 4 bits): DAI indicator

[0225] - TPC command (2 bits) used to schedule PUCCH: PUCCH power control indicator

[0226] -PUCCH Resource Indicator (3 bits): Indicates one of the eight resources configured by the higher layer.

[0227] -PDSCH to HARQ_feedback timing indicator (0, 1, 2, or 3 bits): Indicates one of the eight feedback timing offsets set by the higher layer for the HARQ feedback timing indicator.

[0228] - Antenna port (4, 5, or 6 bits): Indicates the DMRS port and CDM group where there is no data.

[0229] -Transmission Configuration Indicator (TCI) (0 or 3 bits): TCI indicator.

[0230] -SRS Request (2 or 3 bits): SRS transmission request indicator.

[0231] -CBG transmission information (0, 2, 4, 6, or 8 bits): An indicator of whether the code block group is transmitted in the allocated PDSCH. 0 indicates that the CBG is not transmitted, while 1 indicates that the CBG is transmitted.

[0232] -CBG Clear Information (0 or 1 bit): An indicator that the previous CBG has been contaminated - 0 indicates that the previous CBG may have been contaminated, while 1 indicates that the previous CBG can be used when receiving a retransmission (combinable).

[0233] -DMRS Sequence Initialization (1 bit): Indicator used for DMRS scrambling ID selection.

[0234] For example, a base station can use DCI format 2_2 to send a group of TPC commands for PUCCH and PUSCH transmissions to one or more UEs.

[0235] When DCI format 2_2 is transmitted together with a CRC scrambled by TPC-PUSCH-RNTI or TPC-PUCCH-RNTI, it includes the following information:

[0236] -Block number 1, Block number 2...Block number N

[0237] The higher-level parameter tpc-PUSCH or tpc-PUCCH determines the index of multiple blocks for a cell's UL, and each block includes the following fields.

[0238] -Loop closure indicator — 0 or 1 bit

[0239] For DCI format 2_2 detected by TPC-PUSCH-RNTI, if the UE is not configured with the higher-level parameter twoPUSCH-PC-AdjustmentStates, this region is 0 bits. The UE assumes that each block in DCI format 2_2 is 2 bits; otherwise, this region is 1 bit, and the UE assumes that each block in DCI format 2_2 is 3 bits.

[0240] The number of bits in format 2_2 can be less than or equal to the payload size of format 1_0 monitored in the common search space of the same supporting cell. If the number of bits in format 2_2 is less than the payload size of format 1_0, add 0s to format 2_2 until it equals the payload size of format 1_0.

[0241] The UE can receive a maximum of 4 DCIs of different sizes in each time slot of the corresponding cell. The UE can receive a maximum of 3 DCIs of different sizes scrambled with C-RNTI in each time slot of the corresponding cell.

[0242] In a 5G system, the search space of the aggregation level L and the search space set s in CORESET p can be represented as shown in equation (1).

[0243] [Equation 1]

[0244]

[0245] L: Aggregation Level

[0246] n Cl Carrier index

[0247] N CCE，p The total number of CCEs present in CORESET p

[0248] n μ s，f Time slot index

[0249] M (L) p，s，max Number of PDCCH candidate groups at aggregation level L

[0250] m snCl =0, ..., M (L) p，s，max -1 PDCCH candidate group index at aggregation level L

[0251] i = 0, ..., L-1

[0252] nRNTI: UE identifier

[0253] In the case of a public search space, it can be 0.

[0254] For the UE-specific search space, It can be a value that varies depending on the UE's identification information (e.g., the C-RNTI or ID configured for the UE by the base station) and the time index.

[0255] The base station can configure and indicate the TCI state between two different RSs or channels via appropriate signals, announcing the quasi-co-location (QCL) relationship between different RSs or channels. When different RSs or channels are QCL-ified, when estimating the channel via a reference RS antenna port A (reference RS#A) and an RS antenna port B (target RS#B) with a QCL relationship, the UE is allowed to apply all or some of the large-scale channel parameters estimated from antenna port A to the channel measurement from antenna port B. QCL may need to associate different parameters depending on the context, such as 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) radio resource management (RRM) affected by average gain, and 4) beam management (BM) affected by spatial parameters. NR supports four types of QCL relationships, as shown in Table 10 below.

[0256] [Table 10]

[0257] QCL type Large-scale characteristics A Doppler frequency shift, Doppler spread, average delay, delay spread B Doppler frequency shift, Doppler spread C Doppler shift, average delay D Spatial Rx parameters

[0258] Spatial RX parameters can be collectively referred to as all or some of various parameters, such as angle of arrival (AoA), power angular spectrum (PAS) of AoA, angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, spatial channel correlation, etc.

[0259] QCL relationships can be configured for the UE through the RRC parameter TCI status and QCL-Info, as shown in Table 11 below.

[0260] [Table 11]

[0261]

[0262] As shown in Table 11 above, a base station can configure a UE using one or more TCI states, indicating up to two QCL relationships (qcl-Type1 and qcl-Type2) for the RS (i.e., the target RS) referencing the TCI state ID. In this case, the QCL information (QCL-Info) included in each TCI state includes the serving cell index and BWP index of the reference RS indicated by the QCL information, the type and ID of the reference RS, and the QCL type, as shown in Table 10 above.

[0263] The following describes in detail the method for configuring SpatialRelationInfo, which indicates the UL beam information between the UE and the base station in a 5G communication system.

[0264] The base station can establish a relationship between a UL channel or signal A (the channel or signal referencing the SpatialRelationInfo) and another DL channel or signal, or a UL channel or signal B (the referenceSignal included in the SpatialRelationInfo configuration), through appropriate signaling (SpatialRelationInfo). Based on this, the UE uses the beam direction used to receive or transmit channel or signal B for transmitting channel or signal A.

[0265] The configuration of SpatialRelationInfo can be changed depending on the type of UL channel or signal that references it. For example, SpatialRelationInfo referenced by SRS resources may include referenceSignal information for determining the PUCCH transmission beam, as shown in Table 12.

[0266] [Table 12]

[0267]

[0268] As described above, the TCI state can be used for DL ​​channel beam indication (an indication of the UE's receive spatial filter value / type), and spatially related information (SpatialRelationInfo) can be used for UL channel beam indication (an indication of the UE's transmit spatial filter value / type). However, this disclosure is not limited to the type of UL / DL and can be extended to each other in the future. For example, a conventional DL TCI state can be extended to a UL TCI state by adding a UL channel or signal to the type of the target RS that can reference the TCI state, or by adding a UL channel or signal to the type of the reference signal (or reference RS) included in the QCL-Info or TCI state. Furthermore, various extension methods exist, such as DL-UL joint TCI states, but not all methods are described in a way that focuses on the subject matter described.

[0269] The base station can configure the UE with at least one SRS configuration for each UL BWP to transmit configuration information for SRS transmission, and can also configure the UE with at least one SRS resource set for each SRS configuration. For example, the base station and the UE can exchange the following signaling information to transmit information about the SRS resource set.

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

[0271] -srs-ResourceIdList: The SRS resource index set referenced by the SRS resource set.

[0272] -resourceType: The timeline transmission configuration of the SRS resource referenced by the SRS resource set. This can be periodic, semi-persistent, or aperiodic. When set to periodic or semi-persistent, the associated CSI-RS information may be provided depending on the use of the SRS resource set. If set to aperiodic, the aperiodic SRS resource trigger list and slot offset information may be provided, and the associated CSI-RS information may be provided depending on the use of the SRS resource set.

[0273] - Usage: Configuration for the use of SRS resources referenced by an SRS resource set, and can be 'beamManagement', 'codebook', 'nonCodebook', or 'antennaSwitching'.

[0274] -α, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: This provides parameter configuration for adjusting the transmit power of SRS resources referenced by the SRS resource set.

[0275] The UE can understand that the SRS resources included in the SRS resource index set referenced by the SRS resource set follow the information configured in the SRS resource set.

[0276] Furthermore, the base station and the UE can exchange higher-layer signaling information to transmit individual configuration information for SRS resources. For example, individual configuration information for SRS resources may include time-frequency axis mapping information in the time slots of the SRS resources, which may include frequency hopping information within or between time slots for the SRS resources.

[0277] As another example, individual configuration information for an SRS resource may include the time-domain transmission configuration of the SRS resource, and this configuration can be periodic, semi-persistent, or aperiodic. This may limit the use of the same time-domain transmission configuration as the set of SRS resources that includes the SRS resource. If the time-domain transmission configuration of the SRS resource is set to periodic or semi-persistent, the time-domain transmission configuration may further include the SRS resource transmission period and slot offset (e.g., periodicityAndOffset).

[0278] As another example, separate configuration information for SRS resources may include the configuration of the spatial domain transmission filter for the UE transmitting the SRS resource, which may be provided through spatial relation information for the SRS. When the spatial relation information included in the separate configuration information for the SRS resource references an index of an SSB or CSI-RS resource, the UE can understand that the same spatial domain transmission filter as the spatial domain receive filter used when receiving the referenced CSI-RS or SSB is being used. Alternatively, when the spatial relation information references a different SRS resource index, the UE can understand that the spatial domain transmission filter used when transmitting the referenced SRS resource is being used.

[0279] The base station can trigger activation or deactivation of SRS transmissions to the UE via RRC signaling or higher-level signaling (including MAC CE signaling or L1 signaling (e.g., DCI)).

[0280] For example, a base station can activate or deactivate periodic SRS transmissions to a UE via higher-layer signaling. The base station can instruct the activation of an SRS resource set with `resourceType` set to periodicity via higher-layer signaling, and the UE can transmit SRS resources referenced by the activated SRS resource set. The time-frequency axis resource mapping in the time slots of the transmitted SRS resources follows the resource mapping information configured in the SRS resources, and the time slot mapping, including the transmission period and time slot offset, follows the `periodicityAndOffset` configured in the SRS resources. Furthermore, the spatial domain transmission filter applied to the transmitted SRS resources can reference spatial relationship information configured in the SRS resources, or it can reference associated CSI-RS information configured in the SRS resource set that includes the SRS resources. The UE can transmit SRS resources within an activated ULBWP for periodic SRS resources activated via higher-layer signaling.

[0281] The base station can activate or deactivate semi-persistent SRS transmissions to the UE via higher-layer signaling. The base station can instruct the activation of an SRS resource set via MAC CE signaling, and the UE can transmit SRS resources referenced by the activated SRS resource set. The SRS resource set activated via MAC CE signaling can be restricted to an SRS resource set with resourceType set set to semi-persistent. The time-frequency axis resource mapping in the time slots of the transmitted SRS resources follows the resource mapping information configured in the SRS resources, and the time slot mapping, including transmission period and time slot offset, follows periodicityAndOffset configured in the SRS resources. Furthermore, the spatial domain transmission filter applied to the transmitted SRS resources can reference spatial relation information configured in the SRS resources, or it can reference associated CSI-RS information configured in the SRS resource set including the SRS resources. If spatial relation information is configured in the SRS resources but not followed, the configuration information for the spatial relation information transmitted via MAC CE signaling can be referenced to determine the spatial domain transmission filter, and the MAC CE signaling activates the semi-persistent SRS transmission. The UE can transmit SRS resources within a UL BWP activated for semi-persistent SRS resources activated via higher-layer signaling.

[0282] The base station can trigger aperiodic SRS transmissions to the UE via DCI. The base station can indicate aperiodic SRS resource triggering via the SRS request field of the DCI. The UE understands that the SRS resource set, including the one indicated by the DCI in the aperiodic SRS resource triggering list, has been triggered in the SRS resource set configuration information. The UE can transmit the SRS resources referenced by the triggered SRS resource set. The time-frequency axis resource mapping in the timeslot of the transmitted SRS resource follows the resource mapping information configured in the SRS resource. Furthermore, the timeslot mapping of the transmitted SRS resource can be determined by the timeslot offset between the PDCCH (including the DCI) and the SRS resource, and it can reference values ​​included in the timeslot offset set configured in the SRS resource set. Specifically, as the timeslot offset between the PDCCH (including the DCI) and the SRS resource, the value indicated by the time-domain resource allocation field of the DCI, which is included in the timeslot offset set configured in the SRS resource set, can be applied. Furthermore, the spatial domain transmission filter applied to the transmitted SRS resources can reference spatial relationship information configured in the SRS resources, or it can reference associated CSI-RS information configured in the SRS resource set that includes the SRS resources. The UE can transmit SRS resources within the UL BWP activated for aperiodic SRS resources triggered by DCI.

[0283] When a base station triggers an aperiodic SRS transmission to a UE via DCI, the UE may need a minimum time interval between the SRS being transmitted and the PDCCH containing the DCI that triggered the aperiodic SRS transmission in order to apply configuration information for the SRS resources and transmit the SRS. The time interval for the UE's SRS transmission can be defined as the number of symbols between the last symbol of the PDCCH containing the DCI that triggered the aperiodic SRS transmission and the first symbol of the first SRS resource mapped to the transmitted SRS resources. The minimum time interval can be determined by referencing the PUSCH preparation process time for the UE to prepare for PUSCH transmission. Furthermore, the minimum time interval can have different values ​​depending on the use of the SRS resource set including the transmitted SRS resources. For example, the minimum time interval can be determined as N² symbols, which are defined based on the UE's processing capacity by referencing the UE's PUSCH preparation process time. Furthermore, when the SRS resource set usage is set to 'codebook' or 'antennaSwitching', the minimum time interval can be determined to be N², taking into account the usage of the SRS resource set including the transmitted SRS resources. When the SRS resource set usage is set to 'nonCodebook' or 'beamManagement', the minimum time interval can be determined to be N² + 14 symbols. When the time interval used for SRS transmission is greater than or equal to the minimum time interval, the UE can transmit aperiodic SRS, and when the time interval used for SRS transmission is less than the minimum time interval, the UE can ignore the DCI that triggers aperiodic SRS.

[0284] In NR, the base station can schedule the UE to transmit PUSCH using either DCI format 0_0 or DCI format 0_1. The time-axis and frequency-axis resource mapping information of the PUSCH transmitted by the UE can be obtained by referring to the values ​​of the time-domain resource allocation and frequency-domain resource allocation fields of the DCI. The detailed mapping method can follow the time-axis resource allocation method and frequency-axis resource allocation method described above.

[0285] Furthermore, the transport precoding information, rank, and transport layer number of the PUSCH transmitted by the UE can reference the configuration information for the SRS resource indicated by the SRS Resource Indicator (SRI) field of the DCI, or follow the information indicated by the precoding information and layer number segment of the DCI. Specifically, when the base station schedules the UE to transmit the PUSCH using DCI format 0_0, the UE can transmit the PUSCH in a single layer without applying precoding. When the base station schedules the UE to transmit a codebook-based PUSCH using DCI format 0_1, the UE can determine the transport precoding and transport layer number based on the configuration information for the SRS resource indicated by the SRI field of the DCI and the information indicated by the precoding information and layer number segment of the DCI. When the base station schedules the UE to transmit a non-codebook-based PUSCH using DCI format 0_1, the UE can determine the transport precoding and the transport layer number to be applied to the PUSCH based on the transport precoding and transport layer number applied when transmitting the SRS resource indicated by the SRI field of the DCI, and then transmit the PUSCH.

[0286] The spatial domain transmission filter applied to the PUSCH transmitted by the UE can follow the value set in the SRS resource indicated by the SRI field of the DCI, or employ a predetermined spatial domain transmission filter. When the base station schedules the UE to transmit the PUSCH using DCI format 0_0, the UE follows the active spatial relation information of the PUCCH resource with the lowest index in the active UL BWP of the serving cell. When the spatial relation information references the index of an SSB or CSI-RS resource, the UE can use the same spatial domain transmission filter as the spatial domain receive filter used when receiving the referenced CSI-RS or SSB.

[0287] Alternatively, when spatial relation information references an SRS resource index, the UE can use the spatial domain transmission filter used when transmitting the referenced SRS resource. When the base station schedules the UE to transmit PUSCH using DCI format 0_1, the UE follows the spatial relation information or associated CSI-RS information configured by higher-layer signaling in the SRS resource indicated by the SRI field of the DCI. If the spatial relation information is configured in the SRS resource, the UE can use the spatial domain transmission filter according to the spatial relation information referencing method described above. If the spatial relation information is not configured in the SRS resource, and the CSI-RS or associated CSI-RS configuration information is included in the SRS resource set that includes the SRS resource, the UE can determine the spatial domain transmission filter by referencing the transmission precoding information calculated based on the associated CSI-RS information.

[0288] When the base station schedules the UE to transmit PUSCH using DCI format 0_0 or DCI format 0_1, the UE may require a PUSCH preparation process time to apply the transmission precoding method, transmission layer number, and spatial domain transmission filter to the transmission method indicated by the DCI (e.g., SRS resources) and transmit the PUSCH. Therefore, the NR can define the PUSCH preparation process time. The UE's PUSCH preparation process time can follow the following equation (2).

[0289] [Equation 2]

[0290] T proc，2 =max((N2+d 2，1 (2048+144)·κ2 -μ ·T c d 2，2 )

[0291] In equation (2), each variable represents the following.

[0292] N2: The number of symbols determined based on UE processing capability 1 or 2 and parameter set μ. When UE processing capability 1 is reported in the UE capability report, the number of symbols N2 can have the values ​​shown in Table 13 below.

[0293] [Table 13]

[0294] μ <![CDATA[PUSCH Preparation Time N2 [Symbols]]]> 0 10 1 12 2 23 3 36

[0295] When UE processing capability 2 is reported and configured to be available via higher-layer signaling, the symbol number N2 can have the values ​​shown in Table 14 below.

[0296] [Table 14]

[0297] μ <![CDATA[PUSCH preparation time N2 [symbols]]]> 0 5 1 5.5 2 For a frequency range of 1, the value is 11.

[0298] d 2，1 If the first symbol of PUSCH is configured to consist only of DM-RS, the symbol count is set to 0; otherwise, it is 1.

[0299] k:64

[0300] μ: This follows a value for which μ DL or μ UL T proc，2 It became larger. μ DL The parameter set of the DL that indicates the PDCCH of the DCI-scheduled PUSCH is transmitted, and μ UL The set of parameters of the UL that indicates the PUSCH is transmitted.

[0301] This has T c : 1 / (Δfmax ·N f ), Δf max =480·10 3 Hz, N f =4096.

[0302] d 2，2 : Follow the BWP handover time, at which point the DCI scheduler PUSCH indicates the BWP handover; otherwise, it is 0.

[0303] Considering the timeline resource mapping information of PUSCH scheduled via DCI and the impact of timing advance (TA) between UL and DL, if the first symbol of PUSCH is after the last symbol of the PDCCH, which includes the DCI that schedules the PUSCH, T... proc，2 If the PUSCH preparation process begins before the first UL symbol, the base station and UE determine that the PUSCH preparation time is insufficient. Otherwise, the base station and UE determine that the PUSCH preparation time is sufficient. The UE can send the PUSCH only if the PUSCH preparation time is sufficient, and can ignore the DCI-scheduled PUSCH if the PUSCH preparation time is insufficient.

[0304] In NR, the UE can send UL control information (UCI) to the base station via PUCCH. UCI may include at least one of the following: HARQ-ACK indicating whether the demodulation / decoding of TB received by the UE via PDSCH was successful, a scheduling request (SR) from the UE to the PUSCH base station requesting resource allocation for UL data transmission, and CSI, which is information used to report the channel state of the UE.

[0305] Based on the length of the allocated symbols, PUCCH resources can be divided into long PUCCHs and short PUCCHs. In NR, a long PUCCH has a length of 4 symbols or more in a time slot, while a short PUCCH has a length of 2 symbols or less in a time slot.

[0306] Long PUCCHs can be used to enhance UL cell coverage and therefore can be transmitted in DFT-S-OFDM schemes, which are single-carrier transmissions rather than OFDM transmissions. Long PUCCHs support transmission formats such as PUCCH format 1, PUCCH format 3, and PUCCH format 4, depending on the number of control information bits supported and whether UE multiplexing is supported via pre-discrete Fourier transform orthogonal cover codes (pre-DFT OCC) on the front end of the inverse fast Fourier transform (IFFT), which in turn depends on the number of control information bits and the number of allocated symbols.

[0307] PUCCH Format 1 is a long PUCCH format based on DFT-S-OFDM that supports up to 2 bits of control information and uses one RB of frequency resources. The control information may include a combination of HARQ-ACK and SR, or each of them. In PUCCH Format 1, OFDM symbols including DMRS (or RS) and OFDM symbols including UCI are repeatedly configured.

[0308] For example, if the number of transmitted symbols in PUCCH format 1 is 8, and starting from the first symbol of these 8 symbols, they sequentially include DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, and UCI symbol. The DMRS symbol is extended using an orthogonal code (or orthogonal sequence or spreading code w_i(m)) in a sequence corresponding to one RB length along the frequency axis in an OFDM symbol, and is transmitted after being IFFT-ized.

[0309] The UCI symbol can be generated as follows. The UE can generate d(0) by performing binary phase shift keying (BPSK) modulation on 1 bit of control information and quadrature phase shift keying (QPSK) modulation on 2 bits of control information. The generated d(0) is then scrambled by multiplying it by a sequence corresponding to one RB length on the frequency axis. Finally, the orthogonal code (or orthogonal sequence or spreading code w) from the scrambled sequence is used on the time axis. i(m) To expand d(0), perform an IFFT on d(0), and then send d(0).

[0310] The UE generates a sequence based on the configured ID and the group hop or sequence hop configuration configured from the base station through a higher layer. It uses the initial cyclic shift value set by the higher layer to cyclically shift the generated sequence and generate a sequence corresponding to the length of one RB.

[0311] If the length of the spreading code (NSF) is given, then the spreading code w i(m) It can be determined as

[0312] Table 15 below shows examples of spreading codes for PUCCH format 1. In Table 15 below, i is the index of the extension code itself, and m is the index of the element of the extension code. Here, the numbers in [] in Table 15 are φ(m). For example, when the length of the extension code is 2 and the index i of the configured extension code is 0, the extension code w i(m) yes Make w i(m) =[1 1].

[0313] [Table 15]

[0314]

[0315] PUCCH format 3 is a long PUCCH format based on DFT-S-OFDM that can support more than 2 bits of control information, and the number of RBs used can be set by higher layers. Control information can include combinations of HARQ-ACK, SR, and CSI, or each of them. In PUCCH format 3, the DMRS symbol positions can be as shown in Table 16, depending on whether frequency hopping is performed within a time slot and whether additional DMRS symbols are configured.

[0316] [Table 16]

[0317]

[0318] For example, when the number of transmission symbols in PUCCH format 3 is 8, DMRS is transmitted in the first and fifth symbols, starting with the first start symbol 0 out of the 8 symbols. Table 15 can also be applied in the same way to the DMRS symbol positions in PUCCH format 4.

[0319] PUCCH format 4 is a long PUCCH format based on DFT-S-OFDM that supports more than 2 bits of control information and uses one RB of frequency resources. Control information may include a combination of HARQ-ACK, SR, and CSI, or each of these. The difference between PUCCH format 4 and PUCCH format 3 is that PUCCH format 4 can reuse PUCCH format 4 for multiple UEs within one RB. Multiple UEs can reuse PUCCH format 4 by applying pre-DFT OCCs to the control information on the front end of the IFFT. However, the number of symbols of control information that a UE can transmit decreases depending on the number of UEs reused. The number of reusable UEs, i.e., the number of different available OCCs, can be 2 or 4, and the number of OCCs to be applied and their indexes can be configured through higher layers.

[0320] Short PUCCHs can be transmitted in both the DL center time slot and the UL center time slot, and are typically transmitted in the last symbol of the time slot or in subsequent OFDM symbols (e.g., the last OFDM symbol, the penultimate OFDM symbol, or the last two OFDM symbols). Short PUCCHs can also be transmitted anywhere within a time slot. Short PUCCHs can be transmitted using one or two OFDM symbols. When UL cell coverage is good and transmission is performed using a CP-OFDM scheme, short PUCCHs can be used to reduce latency compared to long PUCCHs.

[0321] Depending on the number of control information bits that can be supported, short PUCCH supports transmission formats such as PUCCH format 0 and PUCCH format 2.

[0322] PUCCH Format 0 is a short PUCCH format capable of supporting up to 2 bits of control information and using one RB of frequency resources. The control information may include a combination of HARQ-ACK and SR, or each of them. PUCCH Format 0 transmits only a sequence of 12 subcarriers mapped to a frequency axis in an OFDM symbol, without transmitting DMRS. The UE generates the sequence based on the configured ID and a group hop or sequence hop configuration configured from the base station at a higher layer. It then uses a final cyclic shift value obtained by adding different cyclic shift values ​​depending on the ACK or NACK to the indicated initial cyclic shift value, maps the generated sequence to the 12 subcarriers, and transmits it.

[0323] For example, when HARQ-ACK is 1 bit, the final cyclic shift (CS) is generated by adding 6 to the initial cyclic shift (CS) value for ACK and adding 0 to the initial cyclic shift for NACK, as shown in Table 17 below. The standard defines 0 as the cyclic shift value for NACK and 6 as the cyclic shift value for ACK. The UE generates PUCCH format 0 based on this value and transmits one bit of HARQ-ACK.

[0324] [Table 17]

[0325]

[0326] When HARQ-ACK is 2 bits, if (NACK, NACK), then 0 is added to the initial cyclic shift value; if (NACK, ACK), then 3 is added to the initial cyclic shift value; if (ACK, ACK), then 6 is added to the initial cyclic shift value; and if (ACK, NACK), then 9 is added to the initial cyclic shift value, as shown in Table 18 below. This standard defines 0 as the cyclic shift value for (NACK, NACK), 3 as the cyclic shift value for (NACK, ACK), 6 as the cyclic shift value for (ACK, ACK), and 9 as the cyclic shift value for (ACK, NACK). The UE generates PUCCH format 0 based on this value and transmits a two-bit HARQ-ACK.

[0327] The length of the sequence is 12 when the final cyclic shift (CS) value exceeds 12 plus the cyclic shift (CS) value of the initial cyclic shift value, depending on whether it is ACK or NACK. Therefore, modulo 12 is applied to the final cyclic shift value.

[0328] [Table 18]

[0329]

[0330] PUCCH Format 2 is a short PUCCH format that supports more than 2 bits of control information, and the number of RBs used can be set by higher layers. Control information can include combinations of HARQ-ACK, SR, and CSI, or each of these. In PUCCH Format 2, when the index of the first subcarrier is #0, the positions of the subcarriers where DMRS is transmitted in an OFDM symbol are fixed to subcarriers with indices #1, #4, #7, and #10. Through channel-coded modulation, the control information is mapped to the remaining subcarriers other than the subcarrier where DMRS resides.

[0331] For each of the above PUCCH formats, the settable values ​​and ranges can be summarized as shown in Table 19 below. In Table 19, values ​​that do not need to be set are indicated by NA.

[0332] [Table 19]

[0333]

[0334] To enhance UL coverage, multi-slot repetition can be supported for PUCCH formats 1, 3, and 4 corresponding to long PUCCH formats, and PUCCH repetition can be configured for each PUCCH format.

[0335] The UE can repeatedly transmit PUCCH, including the UCI, as many times as the number of time slots configured via the nrofSlots information about the number of time slots, which is higher-layer signaling. For repeated PUCCH transmissions, the PUCCH transmission for each time slot is performed using the same number of consecutive symbols, and the corresponding number of consecutive symbols can be set via the symbol quantity information (nrofSymbols) in higher-layer signaling, i.e., PUCCH-format1, PUCCH-format3, or PUCCH-format4. For repeated PUCCH transmissions, the PUCCH transmission for each time slot can be performed using the same start symbol, and the corresponding start symbol can be configured via the starting symbol index information (startingSymbolInde) for PUCCH-format1, PUCCH-format3, or PUCCH-format4 in the PUCCH configuration information (PUCCH-Config), which is higher-layer signaling.

[0336] For repeated PUCCH transmissions, if the UE is configured to perform frequency hopping in PUCCH transmissions across different time slots, the UE can perform frequency hopping on a time slot basis. If the UE is configured to perform frequency hopping in PUCCH transmissions across different time slots, the UE can start PUCCH transmission in even-numbered time slots from the first PRB index configured as a higher-layer signaling starting PRB, and in odd-numbered time slots from the second PRB index configured as a higher-layer signaling secondHop PRB.

[0337] Furthermore, if the UE is configured to perform frequency hopping in PUCCH transmissions via higher layers in different time slots, the index of the time slot to which the first PUCCH transmission is indicated to the UE is 0, and the number of repeated PUCCH transmissions is incremented for the total number of repeated PUCCH transmissions, regardless of whether the PUCCH transmission is performed in each time slot. If the UE is configured to perform frequency hopping in PUCCH transmissions in different time slots, the UE does not expect frequency hopping to be configured in a time slot during a PUCCH transmission. If the UE is not configured to perform frequency hopping in PUCCH transmissions in different time slots, but is configured to perform frequency hopping in a time slot, the first and second PRB indices are applied equally to the time slot.

[0338] The base station can configure PUCCH resources for each BWP for a specific UE at a higher layer. Examples of the corresponding configurations are shown in Table 20 below.

[0339] [Table 20]

[0340]

[0341] According to Table 20, one or more PUCCH resource sets can be configured in the PUCCH resource configuration for a specific BWP, and the maximum payload value for UCI transmission can be configured in some PUCCH resource sets. One or more PUCCH resources can belong to each PUCCH resource set, and each PUCCH resource can belong to one of the PUCCH formats mentioned above.

[0342] Regarding PUCCH resource sets, the maximum payload value of the first PUCCH resource set can be fixed at 2 bits, allowing the corresponding value to be set independently without going through higher layers. If the remaining PUCCH resource sets are configured, the indices of the corresponding PUCCH resource sets can be set in ascending order based on the maximum payload value, and the maximum payload value does not need to be set in the last PUCCH resource set. Examples of configuration information provided by higher layers for PUCCH resource sets are shown in Table 21.

[0343] [Table 21]

[0344]

[0345] The resourceList parameter in Table 21 can include the ID of the PUCCH resource belonging to the PUCCH resource set.

[0346] During initial connection setup or when the PUCCH resource set is not configured, the PUCCH resource set shown in Table 22 below can be used. This resource set includes multiple cell-specific PUCCH resources in the initial BWP. The PUCCH resources in the PUCCH resource set to be used for initial access can be indicated via SIB1.

[0347] [Table 22]

[0348]

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

[0350] For SR transmissions, the PUCCH resource corresponding to the schedulingRequestID can be configured at a higher layer, as shown in Table 23 below. The PUCCH resource can be a resource belonging to PUCCH format 0 or PUCCH format 1.

[0351] [Table 23]

[0352]

[0353] In the configured PUCCH resources, the transmission period and offset are set using the periodityAndOffset parameters in Table 23. If UL data to be transmitted by the UE exists at the time corresponding to the set period and offset, the corresponding PUCCH resource is transmitted; otherwise, the corresponding PUCCH resource may not be transmitted.

[0354] For CSI transmission, the PUCCH resources used to transmit periodic or semi-persistent CSI reports via PUCCH can be configured via higher-layer signaling using the pucch-CSI-ResourceList parameter, as shown in Table 24 below. This parameter includes a list of PUCCH resources for each BWP of a cell or CC to send the corresponding CSI report. The PUCCH resources can belong to PUCCH format 2, PUCCH format 3, or PUCCH format 4.

[0355] [Table 24]

[0356]

[0357] For PUCCH resources, the transmission period and offset are set via reportSlotConfig in Table 24.

[0358] For HARQ-ACK transmissions, the set of PUCCH resources to be transmitted is first selected based on the payload of the corresponding HARQ-ACK UCI. That is, the set of PUCCH resources with a minimum payload not less than the UCI payload is selected. The PUCCH resources in the PUCCH resource set can be selected by scheduling the PUCCH resource indicator (PRI) in the DCI corresponding to the HARQ-ACK TB, and the PRI can be the PUCCH resource indicator specified in DCI format 1_0 or 1_1 described above. An example of the relationship between the PRI configured by higher-layer signaling and the PUCCH resources selected from the PUCCH resource set is shown in Table 25 below.

[0359] [Table 25]

[0360]

[0361] If the number of PUCCH resources in the selected PUCCH resource set is greater than 8, then the PUCCH resources can be selected using equation (3).

[0362] [Equation 3]

[0363]

[0364] In equation (3), r PUCCH R represents the index of the selected PUCCH resource in the PUCCH resource set. PUCCH β represents the number of PUCCH resources belonging to the PUCCH resource set. PRI Indicates the PRI value, N CCE,p This represents the total number of CCEs in the CORESET p to which the received DCI belongs, and n CCE,p This indicates the first CCE index of the received DCI.

[0365] The corresponding PUCCH resource is transmitted K1 time slots after the TB transmission corresponding to HARQ-ACK. Candidates for the K1 value can be configured at higher layers, and more specifically, as shown in Table 20 above, via the dl-DataToUL-ACK parameter in PUCCH-Config. One candidate K1 value can be selected by the PDSCH-to-HARQ feedback timing indicator in the DCI used to schedule the TB, and this value can be the value specified in DCI format 1_0 or 1_1 above. The unit of the K1 value can be a time slot unit or a sub-time slot unit. Here, a sub-time slot is a unit of length less than the length of a time slot, and one or more symbols can constitute a sub-time slot. Sub-time slots can also be referred to as micro-time slots.

[0366] The UE may transmit a UCI via one or two PUCCH resources in a time slot or sub-time slot, and when the UCI is transmitted via two PUCCH resources in a time slot / sub-time slot, i) each PUCCH resource does not overlap in a symbol cell, and ii) at least one PUCCH resource may be a short PUCCH. The UE may not expect to transmit multiple PUCCH resources for HARQ-ACK transmission within a time slot.

[0367] When two or more PUCCH resources overlap, according to the aforementioned condition—that the transmitted PUCCH resources should not overlap in symbol cells—one of the overlapping PUCCH resources can be selected, or a new PUCCH resource can be selected. Furthermore, UCI payloads transmitted via overlapping PUCCH resources are fully multiplexed and transmitted, or a portion thereof can be discarded. The following describes the cases where multi-slot repetition is not configured in the PUCCH resources (Case 1) and the cases where multi-slot repetition is configured (Case 2).

[0368] Regarding Case 1, the case of overlapping PUCCH resources is divided into Case 1-1) where two or more PUCCH resources overlap for HARQ-ACK transmission and Case 1-2) for other cases.

[0369] Case 1-1) in Figure 6 As shown in the image.

[0370] Figure 6 The illustration shows multiple overlapping PUCCH resources used for HARQ-ACK transmission of PDSCH when multi-slot repetition is not configured, according to an embodiment.

[0371] refer to Figure 6For two or more different PDCCHs 610 and 611 used for scheduling PDSCH, if the transmission slots of the PUCCH resources corresponding to each PDCCH are the same, the corresponding PUCCH resources can be considered to overlap. That is, when the UL slots corresponding to the K1 values ​​650 and 651 indicated by multiple PDCCHs are the same, the PUCCH resources corresponding to the corresponding PDCCHs are considered to overlap.

[0372] Among the PUCCH resources indicated by PRI 640 and 641 in the PDCCH, only PUCCH resource 631 selected based on PRI 641 corresponding to PDCCH 611 sent most recently can be selected, allowing HARQ-ACK information to be sent on the PUCCH resource. Therefore, the HARQ-ACK information of PDSCH 621 via the selected PUCCH resource 631 and the HARQ-ACK information of another PUCCH 630 overlapping with PUCCH resource 631 are both encoded using a predefined HARQ-ACK codebook and then sent.

[0373] Next, cases where PUCCH resources used for HARQ-ACK transmission overlap with / or PUCCH resources used for SR and / or CSI transmission, or cases corresponding to cases 1-2) where multiple PUCCH resources used for SR and / or CSI transmission overlap, are described. In the above cases, the situation where multiple PUCCH resources transmitted in the same time slot overlap by one or more symbols on the time axis can be defined as 'corresponding PUCCH resource overlap', and whether or not the UCI in the multiplexed resources is reused can be summarized as shown in Table 26 below.

[0374] [Table 26]

[0375]

[0376] According to Table 26, UCI is always reused when the PUCCH resources sent by HARQ-ACK overlap, or when the PUCCH resources of SR and CSI overlap.

[0377] In cases where the PUCCH resources sent by SR and HARQ-ACK overlap, i.e., in case 1-2-1 above, whether UCI is reused can be determined based on the format of the PUCCH resources, as follows.

[0378] -SR on PUCCH format 0 + HARQ-ACK on PUCCH format 1: SR is discarded, and only HARQ-ACK is sent.

[0379] -For other parts: SR and HARQ-ACK are reused.

[0380] Furthermore, in the remaining cases corresponding to Case 1-2-2, i.e., when the PUCCH resources for sending HARQ-ACK and CSI overlap, or when multiple PUCCH resources for sending CSI overlap, whether to reuse UCI can follow higher-level configuration. Moreover, configuring whether to reuse HARQ-ACK and CSI, and configuring whether to reuse multiple CSIs, can be performed independently.

[0381] For example, for each of PUCCH formats 2, 3, and 4, whether HARQ-ACK and CSI are multiplexed can be configured via the simultaneous HARQ-ACK-CSI parameter, and for each PUCCH format, the corresponding parameter can be set to the same value. If multiplexing is configured not to occur via the parameter, only HARQ-ACK is transmitted, and overlapping CSIs may be discarded. Furthermore, whether multiple CSIs are multiplexed can be configured via the multi-CSI-PUCCH-ResourceList parameter in PUCCH-ConFIG. When the multi-CSI-PUCCH-ResourceList parameter is configured, multiplexing is possible among CSIs; otherwise, based on the priority of the CSIs, only the PUCCH corresponding to the higher-priority CSI can be transmitted.

[0382] When UCI multiplexing is performed as described above, the selection method and multiplexing method for the corresponding UCI resource used for PUCCH resource transmission can vary depending on the identification information for the overlapping UCI and the format of the PUCCH resource, as can be summarized in Table 27 below.

[0383] [Table 27]

[0384]

[0385] In Table 27:

[0386] Option 1: The UE changes the PUCCH resource selection based on the SR value of the SR PUCCH resource that overlaps with the HARQ-ACK PUCCH resource. If the SR value is positive, the PUCCH resource used for SR is selected; if the SR value is negative, the PUCCH resource used for HARQ-ACK is selected. The HARQ-ACK information is sent in the selected PUCCH resource.

[0387] - Option 2: The UE multiplexes the HARQ-ACK information and SR information into the PUCCH resource used for HARQ-ACK transmission and sends it.

[0388] - Option 3: The UE multiplexes the SR information and CSI information into the PUCCH resource used for CSI transmission and transmits it.

[0389] - Option 4: Detailed operations for PUCCH resource transfers for HARQ-ACK overlap are described in case 1-1 above.

[0390] - Option 5: When the PUCCH resource corresponding to PDSCH for HARQ-ACK overlaps with the PUCCH resource for CSI transmission, and the multiplexing between HARQ-ACK and CSI is configured by a higher layer, the UE multiplexes the HARQ-ACK information and CSI information into the PUCCH resource for HARQ-ACK and transmits it.

[0391] - Option 6: When the PUCCH resources for HARQ-ACK and PUCCH resources for CSI transmission corresponding to the semi-persistent scheduling (SPS) PDSCH overlap, and the multiplexing between HARQ-ACK and CSI is configured by a higher layer, the UE multiplexes the HARQ-ACK information and CSI information into the PUCCH resources for CSI transmission and transmits them.

[0392] When the PUCCH resource list used for multiplexing (i.e., multi-CSI-PUCCH-ResourceList) is configured through a higher layer, the UE selects the resource in the list that has the lowest index for all multiplexed UCI payloads and then transmits the UCI payloads. If no resource exists that can transmit all multiplexed UCI payloads in the list, the UE selects the resource with the highest index and then transmits HARQ-ACK and as many CSI reports as possible that can be transmitted in the corresponding resource.

[0393] Option 7: When multiple PUCCH resources used for CSI transmission overlap, and multiplexing among multiple CSIs is configured via a higher layer, the UE selects the resource with the lowest index for all multiplexed UCI payloads from the PUCCH source list for CSI multiplexing configured via a higher layer (i.e., multi-CSI-PUCCH-ResourceList), and then transmits the UCI payloads. If no resource exists that can transmit all multiplexed UCI payloads in the list, the UE selects the resource with the highest index and then transmits as many CSI reports as possible that can be transmitted in the corresponding resource.

[0394] For ease of description, the above description focuses primarily on the case of two overlapping PUCCH resources. However, the method described above can also be applied in a similar manner to cases where three or more PUCCH resources overlap. For example, the HARQ-ACK and CSI multiplexing method can be applied when SR+HARQ-ACK multiplexed PUCCH resources overlap with CSI PUCCH resources.

[0395] If configured not to perform multiplexing between specific UCIs, then according to the priority order HARQ-ACK > SR > CSI, higher-priority UCIs are transmitted, and lower-priority UCIs can be discarded. When configured not to perform multiplexing when multiple CSI PUCCH resources overlap, the PUCCH corresponding to the CSI with higher priority is transmitted, and the PUCCH corresponding to the other CSI can be discarded.

[0396] Case 2, which involves multiple time slots being configured repeatedly, is divided into Case 2-1) where two or more PUCCH resources used for HARQ-ACK transmission are located in the same starting time slot, and Case 2-2. Each case is further divided into Case 2-3 and Case 2-4. Figure 7 The explanation is as follows.

[0397] Figure 7 The PUCCH resource overlap is illustrated when multiple time slot repetitions are configured according to an embodiment.

[0398] refer to Figure 7 In Case 2-1), when multiple time slots are repeatedly configured in the PUCCH resource used for HARQ-ACK, i.e., when PUCCH#1 is repeatedly transmitted in multiple time slots (730, 740) and PUCCH#2 is also repeatedly transmitted in multiple time slots (731, 741), if the starting time slots of the two PUCCHs indicated by K1 are the same, a single PUCCH resource (the PUCCH transmitted most recently in a time slot), i.e., PUCCH#2, can be selected as in Case 1-1). Therefore, the HARQ-ACK information corresponding to PDSCH#1 and PDSCH#2 is multiplexed through the HARQ-ACK codebook and transmitted in the corresponding PUCCH.

[0399] Although examples of multiple PUCCHs repeating and overlapping in multiple time slots have been described, the same approach can be applied even in cases where multiple PUCCHs repeat in multiple time slots overlap with PUCCHs sent in a single time slot.

[0400] Case 2-2) corresponds to the overlap of PUCCH for HARQ-ACK transmission and PUCC for CSI transmission in a symbol cell, or the overlap of PUCCH or CSI transmissions for multiple SRs in a symbol cell. That is, when PUCCH#1 is repeatedly transmitted in multiple slots (750, 751) and PUCCH#2 is also repeatedly transmitted in multiple slots (760, 761), this corresponds to the case where PUCCH#1 and PUCCH#2 overlap in one or more symbols in a time slot 770.

[0401] Between overlapping PUCCHs in one or more symbols within time slot 770, the UCIs in the PUCCHs are compared by priority, and the higher-priority UCI is transmitted, while the other UCI is discarded in that time slot. In this case, the priority of UCIs follows the order HARQ-ACK > SR > CSI, starting with the highest priority.

[0402] When multiple CSI PUCCH resources overlap, the PUCCH corresponding to the CSI with the higher priority is transmitted, and the PUCCH corresponding to another CSI can be dropped in the corresponding time slot. This priority-dependent PUCCH or dropping is only performed in the time slot where symbol cell overlap occurs, and not in other time slots. That is, a PUCCH configured to repeat in multiple time slots can be dropped in the time slot where symbol cell overlap occurs, but can be transmitted in other time slots as configured.

[0403] Although examples of multiple PUCCHs repeating and overlapping in multiple time slots have been described, the same approach can be applied even in cases where multiple PUCCHs repeat in multiple time slots overlap with PUCCHs sent in a single time slot.

[0404] If in During repeated transmission, the UE transmits PUCCH in the first time slot and PUSCH in the second time slot, and PUCCH transmission overlaps with PUSCH transmission in one or more time slots, or PUCCH is transmitted when the UCI in PUSCH in the overlapping time slot is multiplexed, and PUSCH is not transmitted in the time slot where PUCCH and PUSCH overlap.

[0405] In single-slot transmissions and multi-slot repetitions of PUCCH, the aforementioned slots can be replaced by microslots and used for low-latency services such as URLLC. A microslot (i.e., a subslot) has a shorter length on the timeline than a slot, and a microslot can consist of fewer than 14 symbols. For example, 2 or 7 symbols can constitute a microslot. When microslots are configured at a higher layer, the units, such as the HARQ-ACK feedback timing K1 value or the repetition transmission value, can be changed from slots to microslots. Microslot configuration can be applied to all PUCCH transmissions or can be limited to PUCCH transmissions for a specific service. For example, while slot-based transmissions can be applied to PUCCHs for eMBB services, microslot-based transmissions can be applied to PUCCHs for URLLC services.

[0406] If the UE does not have a UE-specific configuration (dedicated PUCCH resource configuration) for PUCCH resource configuration, the PUCCH resource set is provided via higher-layer signaling pucch-ResourceCommon. In this case, the beam configuration for PUCCH transmission follows the beam configuration used in PUSCH transmissions scheduled via Random Access Response (RAR) UL authorization. If the UE has a UE-specific configuration (dedicated PUCCH resource configuration) for PUCCH resource configuration, the beam configuration for PUCCH transmission is provided via pucch-spatialRelationInfoId as higher-layer signaling, as shown in Table 28 below. If the UE is configured with one pucch-spatialRelationInfoId, the beam configuration for the UE's PUCCH transmission is provided via one pucch-spatialRelationInfoId. If the UE is configured with multiple pucch-spatialRelationInfoIDs, the UE is instructed to activate one of the multiple pucch-spatialRelationInfoIDs via MAC CE. The UE can be configured with up to 8 pucch-spatialRelationInfoIDs via higher-level signaling, and can be instructed to activate only one of them.

[0407] When the UE is instructed to activate any pucch-spatialRelationInfoID via MAC CE, the UE transmits the HARQ-ACK from the MAC CE via MAC CE after the first slot following the transmission of the activation information pucch-spatialRelationInfoID to the PDSCH. The pucch-spatialRelationInfoID is activated starting from each time slot. μ is the set of parameters applied to the PUCCH transmission. This indicates the number of time slots for each subframe in a given parameter set. Examples of higher-level configuration information for pucch-spatialRelationInfo are shown in Table 28. Here, pucch-spatialRelationInfo can be used interchangeably with PUCCH beam information.

[0408] [Table 28]

[0409]

[0410] As shown in Table 28, a referenceSignal configuration may exist in a specific pucch-spatialRelationInfo configuration. The referenceSignal can be an ssb-index indicating a specific SS / PBCH, a csi-RS-index indicating a specific CSI-RS, or an SRS indicating a specific SRS. If the referenceSignal is configured with an ssb-index, the UE can set the beam used to receive the SS / PBCH corresponding to the ssb-index in the SS / PBCH of the same serving cell as the beam for PUCCH transmission. Furthermore, if a servingCellId is provided, the UE can set the beam used to receive the SS / PBCH corresponding to the ssb-index in the SS / PBCH of the cell indicated by the servingCellId as the beam for PUCCH transmission. If the referenceSignal is configured with a csi-RS-Index, the UE can set the beam used to receive the CSI-RS corresponding to the csi-RS-Index in the CSI-RS in the same serving cell as the beam for PUCCH transmission. And if the servingCellId is provided, the UE can set the beam used to receive the CSI-RS corresponding to the csi-RS-Index in the CSI-RS in the cell indicated by the servingCellId as the beam for PUCCH transmission. If the referenceSignal is configured with SRS, the UE can set the transmission beam used to transmit the SRS as the beam used for PUCCH transmission, where the SRS corresponds to a resource index provided in the active UL BWP and / or higher-level signaling resources in the same serving cell. Alternatively, if the servingCellID and / or uplinkBWP are provided, the UE can set the transmission beam used to transmit the SRS corresponding to a resource index provided by the UL BWP and / or higher-level signaling resources in the cell indicated by the uplinkBWP and / or servingCellID as the beam used for PUCCH transmission.

[0411] A pucch-PathlossReferenceRS-Id configuration can exist in a specific pucch-spatialRelationInfo configuration. The Pucch-PathlossReferenceRS in Table 29 can be mapped to the pucch-PathlossReferenceRS-Id in Table 28. Up to four can be configured via pathlossReferenceRSs in the higher-level signaling Pucch-PowerControl in Table 29. If connected to the SS / PBCH via the referenceSignal in Table 29, the Pucch-pathlossReferenceRSs are configured with an ssb-Index, and if connected to the CSI-RS, they are configured with a csi-RS-Index.

[0412] [Table 29]

[0413]

[0414] The UE determines the PUCCH transmit power based on higher-layer parameter configuration, the activated PUCCH-SpatialRelationInfo, the PUCCH UCI payload size, the allocated PUCCH transmission resources, and / or the TPC command indicated by the DCI. If the UE transmits PUCCH to the primary cell c on carrier f in an activated UL BWP b, the transmit power P at time i during PUCCH transmission is determined. PUCCH，b，f，c (i, q) u q d ,l) can be defined as shown in equation (4).

[0415] [Equation 4]

[0416]

[0417] In equation (4), P CMAX，f，c (i) represents the maximum output power of PUCCH transmission time i in the primary cell c (carrier f).

[0418] P O_PUCCHb，f，c (q u The P value is defined as indicated by the higher-level parameter p0-nominal (or set to 0dBm if p0-nominal is not set). O_NOMINAL_PUCCH And P, indicated by p0-PUCCH-Value in the higher-level parameter p0-Set (or set to 0 if p0-Set is not set). O_UE_PUCCH (q uThe sum of the values ​​in the PUCCH-SpatialRelationInfo. If one PUCCH-SpatialRelationInfo configuration or one of the values ​​in multiple PUCCH-SpatialRelationInfo is activated, the UE selects the p0-PUCCH-Value of the P0-PUCCH set with p0-PUCCH-Id in the PUCCH-SpatialRelationInfo. If more than one PUCCH-SpatialRelationInfo is configured, and the PUCCH including HARQ-ACK information for the PDSCH providing the activation command for the PUCCH-SpatialRelationInfo is transmitted in k time slots, the UE applies the activation command from the first time slot after k+3 time slots. If the UE is not configured with a PUCCH-SpatialRelationInfo, the UE selects the p0-PUCCH-Value of the P0-PUCCH with the smallest p0-PUCCH-Id in the p0-Set.

[0419] It is the bandwidth allocated by PUCCH resources, and is expressed as the number of RBs in PUCCH transmission time i.

[0420] PL b，f，c (q d ) indicates that the UE is targeting the RS resource index q d The calculated DL path loss estimate. If the UE is not configured with pathlossReferenceRSs or dedicated higher-layer parameters, the UE uses the SS / PBCH block used for the receive MIB to calculate the PL. b，f，c (q d If the UE is configured with RS resource index q d Then index q d Using RS resources to calculate PL b，f，c (q d The RS resource set can be set as pathlossReferenceRSs, and the RS resource set can include SS / PBCH block indexes indicated by ssb-Index or CSI-RS resource indexes indicated by csi-RS-Index. If the UE is configured with higher-level parameters pathlossReferenceRSs and PUCCH-SpatialRelationInfo, the UE can determine the PL based on the referenceSignal of PUCCH-pathlossReferenceRSs corresponding to the pucch-PathlossReferenceRS-Id configured in PUCCH-SpatialRelationInfo. b，f，c(q d If more than one PUCCH-SpatialRelationInfo is configured, and the PUCCH including HARQ-ACK information for the PDSCH providing the activation command for the PUCCH-SpatialRelationInfo is transmitted in k time slots, the UE applies the activation command from the first time slot after k+3 time slots. If the PUCCH-SpatialRelationInfo includes servingCellId, the UE receives the resource index q for the activated DL BWP for the corresponding supporting cell. d The RS. If the UE is configured with pathlossReferenceRSs but not with PUCCH-SpatialRelationInfo, the UE can determine the PL based on the referenceSignal of the PUCCH-PathlossReferenceRS with index 0 of pucch-PathlossReferenceRS-Id in the RS resources of the supporting cell or primary cell indicated by the higher-level parameter pathlossReferenceLinking (if configured). b，f，c (q d When the UE is configured with the following higher-level parameters:

[0421] - If pathlossReferenceRSs is not configured

[0422] - If PUCCH-SpatialRelationInfo is not configured

[0423] -If the higher-level parameter enableDefaultBeamPL-ForPUCCH-r16 is configured, and

[0424] - If for any one of the CORESETs, CORESETPoolIndex is not set to 1, or for all CORESETs, CORESETPoolIndex is set to 1, and no code points in the DCI format are mapped to either TCI state.

[0425] The UE determines the QCL assumption for the lowest indexed CORESET in the DL BWP activated in the primary cell, or the RS resource index q for periodic RS resources including 'QCL-TypeD' as a TCI state. d If PUCCH transmission is performed over multiple time slots, then PUCCH is performed by applying the same q to each time slot. d It was sent.

[0426] Δ F_PUCCH (F) is defined as the higher-level parameter deltaF-PUCCH-f0 (or f1, f2, f3, or f4) value of PUCCH format 0 (or format 1, format 2, format 3, or format 4), and if the corresponding higher-level parameter is not configured, then Δ F_PUCCH (F) is set to 0.

[0427] Δ TF，b，f，c (i) is defined as the PUCCH transmit power adjustment component and is determined based on the PUCCH format, UCI payload, and resources allocated to PUCCH transmission.

[0428] g b，f，c (i, l) represents the PUCCH power control adjustment state, and is based on the TPC command value gP. UCCH b，f，c (i, l) and the accumulation method are used to determine this.

[0429] g PUCCH b，f，c (i, l) can be a TPC command value indicated in DCI format 2_2, which includes a CRC scrambled with TPC-PUCCH-RNTI, along with a TPC command for other UEs, or a TPC command value included in DCI format 1_0 or 1_1, which is detected by the UE for PUCCH transmission timing i.

[0430] - If twoPUCCH-PC-AdjustmentStates and PUCCH-SpatialRelationInfo are configured for the UE, they are set to l∈{0,1}.

[0431] - If twoPUCCH-PC-AdjustmentStates or PUCCH-SpatialRelationInfo is not configured for the UE, then 1 = 0.

[0432] If the UE has received a TPC command value in DCI format 1_0 or 1_1, and PUCCH-SpatialRelationInfo is configured, the UE can obtain a mapping between the set of values ​​of closedLoopIndex, including the value of 1, and the set of PUCCH-SpatialRelationInfoIds with an index set by p0-PUCCH-Id. If the UE receives an activation command indicating the value of PUCCH-SpatialRelationInfoId, the UE determines to set the closedLoopIndex with the value associated with the corresponding p0-PUCCH-Id index.

[0433] - If the UE receives a TPC command from DCI format 2_2 sent via a CRC scrambled with TPC-PUCCH-RNTI, then value 1 is set to the closed-loop indicator region in DCI format 2_2.

[0434] - This indicates the current PUCCH power control adjustment state at time i during PUCCH transmission.

[0435] -Here, δ PUCCHb，f，c The value can be one of the values ​​shown in Table 30 below.

[0436] [Table 30]

[0437] TPC command fields <![CDATA[Accumulated δ PUCCHb，f，c [dB]]]> 0 -1 1 0 2 1 3 3

[0438] - It is the K of the UE before the PUCCH transmission time i-i0. PUCCH The (i-i0)-1 symbol and the KPUCCH(i) symbol received before the PUCCH transmission timing i have a base C (C i TPC command set C i The sum of TPC command values ​​in the data. K before PUCCH transmission time i-i0. PUCCH The (i-i0)-1 symbol may be among the positive i0 values ​​of the KPUCCH(i) symbol that precedes the PUCCH transmission timing I, with the minimum value set to i0.

[0439] - If the UE detects DCI format 1_0 or 1_1 and sends a PUCCH, then KPUCCH(i) is the number of symbols between the last symbol of the corresponding PDCCH and the symbol before the first PUCCH transmission symbol.

[0440] - If the UE sends PUCCH without detecting DCI format 1_0 or 1_1, then KPUCCH(i) is the sum of k2 in the higher-layer parameter PUSCH-ConfigCommon and the number of symbols per slot. The product of the same KPUCCH is the smallest.

[0441] -If the maximum power is reached during PUCCH transmission at time i-i0 and Then g b，f，c (i, l) = g b，f，c (i-i0, l)

[0442] -If the minimum power is reached at time i-i0 during PUCCH transmission and Then g b，f，c (i, l) = g b，f，c (i-i0, l)

[0443] -If P O_PUCCHb，f，c (q u The value configuration is provided by the higher-level parameter for the corresponding PUCCH power control adjustment state l, then g b，f，c (k, l) = 0, k = 0, 1, ..., i.

[0444] If the UE is configured with PUCCH-SpatialRelationInfo, the UE determines I from the value qu based on the p0-PUCCH-Id value qu and the pucch-SpatialRelationId value associated with the closedLoopIndex value l. Otherwise, l = 0.

[0445] -In other cases, g b，f，c (0, l) = ΔP rampup，b，f，c +δ b，f，c At this point, l = 0. δ b，f，c This can be a TPC command containing a RAR grant instruction corresponding to the PRACH in a Type 1 random access procedure, or a TPC command containing a RAR grant instruction transmitted corresponding to the MsgA in a Type 2 random access procedure. Alternatively, δ b，f，c This could be a TPC command corresponding to the successRAR indication of MsgA in a Type 2 random access procedure. However, if it is the first PUCCH transmission 28 symbols after the last symbol of the first PDCCH, then δ b，f，c It may be a TPC command included in a DCI format, which is transmitted along with a CRC scrambled with C-RNTI or MCS-C-RNTI detected in the first PDCCH received in recoverySearchSpaceId.

[0446] -If the UE sends a PUCCH, and ΔP rampuprequested，b，f，c If the total power of higher-level requests increases, then ΔP rampup b，f，c It is determined according to PUCCH format 0 and 1 or other formats, as shown in equation (5).

[0447] [Equation 5]

[0448] or

[0449]

[0450] During UE UL transmission, a transition time (i.e., a shift time) may be required to meet the transmit power requirements for the on state when transitioning from a transmit-off state to a transmit-on state. Similarly, a transition time may be required to meet the transmit power requirements for the off state when transitioning from a transmit-on state to a transmit-off state. Alternatively, transition time may also be required when the transmit power or transmit RB changes in the transmit-on state or when frequency hopping occurs.

[0451] Figure 8 The transition time for switching between a transmission off (OFF) state and a transmission on (ON) state according to an embodiment is shown.

[0452] refer to Figure 8 The conversion time can be defined for each of FR1 and FR2 (805 and 810). In NR systems, FR is divided into FR1 and FR2. For example, FR1 can be from 450MHz to 7125MHz, and FR2 can be from 24250MHz to 52600MHz. However, the ranges of FR1 and FR2 can be changed and applied. For example, FR1 can be varied from 450MHz to 6000MHz.

[0453] Figures 9A to 9E The transition times for transmit power change, transmit RB change, or frequency hopping in FR1 during the transmit-on state, according to an embodiment, are shown.

[0454] refer to Figure 9A and 9B When a change in the transmission channel is accompanied by a change in transmit power, a change in transmit RB, or frequency hopping, the transition time can be defined as in 905 and 910. The transition time between an SRS channel and another channel can be defined differently depending on whether the SRS probe is performed through the same antenna port (905) as the other channel or through another antenna port (910).

[0455] refer to Figures 9C to 9E When accompanied by changes in transmit power, transmit RB changes, or frequency hopping, different switching times can be defined by the length of the transmission channel before and after the change / frequency hopping (915, 920, and 925).

[0456] When there is a change in transmit power, a change in transmit RB, or frequency hopping between long and short sub-slot transmissions, the switching time can be defined within the long sub-slot (915). When there is a change in transmit power, a change in transmit RB, or frequency hopping between short sub-slots, the switching time can be defined between the short sub-slots (920 and 925), and when the parameter set in FR1 is less than 60 kHz, blank symbols do not need to be configured between short sub-slots (920). However, when the parameter set in FR1 is 60 kHz, blank symbols should be configured between short sub-slots (925).

[0457] Long sub-slots can indicate PUSCH transmissions with more than 2 transmitted symbols or long PUCCH transmissions, while short sub-slots can indicate PUSCH transmissions with 2 or fewer transmitted symbols or short PUCCH transmissions.

[0458] Figures 10A to 10D The transition times for transmit power change, transmit RB change, or frequency hopping in FR2 under transmit-enabled state according to an embodiment are shown.

[0459] refer to Figure 10A and 10B When the transmission channel changes are accompanied by changes in transmit power, transmit RB changes, or frequency hopping, the switching time can be as defined in 1005.

[0460] refer to Figures 10B to 10D When accompanied by changes in transmit power, transmit RB changes, or frequency hopping, different switching times can be defined by the length of the transmission channel before and after the change / frequency hopping (1010, 1015, and 1020).

[0461] When there is a change in transmit power, a change in transmit RB, or frequency hopping between long sub-slot transmission and short sub-slot transmission, the switching time can be defined in the long sub-slot (1010).

[0462] When there are changes in transmit power, transmit RB, or frequency hopping between short sub-slots, the switching time can be defined between the short sub-slots (1015 and 1020), and when the parameter set in FR2 is less than 120 kHz, blank symbols do not need to be configured between the short sub-slots (1015). However, when the parameter set in FR2 is 120 kHz, blank symbols should be configured between the short sub-slots (1020).

[0463] Long sub-slots can indicate PUSCH transmissions with more than 2 transmitted symbols or long PUCCH transmissions, while short sub-slots can indicate PUSCH transmissions with 2 or fewer transmitted symbols or short PUCCH transmissions.

[0464] Unlike traditional systems, 5G wireless communication systems can support services requiring high transmission rates, services with very short transmission latency, and services requiring high connection density. In wireless communication networks comprising multiple cells, TRPs, or beams, coordinated transmission between cells, TRPs, and / or beams can increase the signal strength received by the UE or effectively perform interference control between cells, TRPs, and / or beams, thereby meeting various service requirements. Joint transmission (JT) is one of the representative transmission technologies for cooperative communication and can increase the signal strength or throughput received by the UE by transmitting signals to a UE via multiple cells, TRPs, and / or beams.

[0465] Referring to the PUCCH-related description above, the current 3GPP standard Rel-15 NR focuses on PDSCH transmission over a single cell / transmitter point / panel / beam (hereinafter referred to as TRP) or PDSCH transmission in a coherent scheme across multiple TRPs. As an optimized HARQ-ACK transmission scheme, at most one PUCCH resource for HARQ-ACK is transmitted in one time slot. 3GPP NR Release 16 can support incoherent transmission per TRP, i.e., incoherent JT (NC-JT), and in this case, each TRP participating in NC-JT can simultaneously transmit a separate PDSCH to the UE. HARQ-ACK information for PDSCH can be included in a single PUCCH resource and transmitted. Assuming that the overhead caused by information exchange between TRPs is burdensome, for example, when the backhaul delay for each TRP is long, HARQ-ACK information can be included in a separate PUCCH resource for each TRP and transmitted.

[0466] Furthermore, 3GPP NR Release 17 supports NC-JT for PDCCH, PUCCH, and PUSCH (these are physical channels other than PDSCH). For PUCCH, coverage can be increased using multiple TRPs. When congestion occurs between the UE and the base station, the receive power of PUCCH transmitted via a single TRP can be significantly reduced. However, retransmitting PUCCH through multiple TRPs can establish multiple links between the UE and the base station, and therefore may be more robust than transmitting PUCCH through a single TRP during congestion. Additionally, since PUCCH is retransmitted through multiple TRPs, gains occur due to macro diversity. In NR Release 15 or 16, since the method of retransmitting PUCCH through multiple TRPs is not supported, a single transmit power for PUCCH is determined. However, when multiple TRPs are located in different positions, the distance between the TRP and the UE and the channel state may differ. If the distance between the TRP and the UE differs, the path loss will differ accordingly, and the PUCCH transmit power can be calculated and supported for each TRP.

[0467] According to embodiments of this disclosure, a method is provided for repeatedly transmitting PUCCH based on NC-JT with a transmit power determined for each TRP, enabling the UE to support efficient PUCCH transmission.

[0468] Furthermore, when a UE changes its beam and / or transmit power to repeatedly transmit the PUCCH through multiple TRPs, the offset may need to be changed depending on the UE's capabilities. According to embodiments of this disclosure, a method is provided for repeatedly transmitting the PUCCH through multiple TRPs taking into account the offset determined by the base station based on the UE's capabilities and indicated to the UE, and a method is provided for transmitting UL signals (even for other UL signals such as PUSCH or SRS) through multiple TRPs while taking into account the offset.

[0469] This disclosure applies to FDD and / or TDD systems.

[0470] As used herein, the term "higher-layer signaling" can refer to a method for transmitting signals from a base station to a UE using the physical layer's DL data channel or from a UE to a base station using the physical layer's UL data channel, and can be used interchangeably with RRC signaling, PDCP signaling, or MAC CE. Information transmitted to the UE via MAC CE or L1 signaling, including DCI, can be simply referred to as control information.

[0471] Higher-level signaling may correspond to at least one or a combination of one or more of the following signaling types.

[0472] -MIB

[0473] -SIB or SIB X (X = 1, 2, ...)

[0474] -RRC

[0475] -MAC CE

[0476] In addition, L1 signaling can correspond to at least one or a combination of one or more of the following physical layer channels or signaling methods that use signaling.

[0477] -PDCCH

[0478] -DCI

[0479] -UE-specific DCI

[0480] -Group Public DCI

[0481] -Public DCI

[0482] - Scheduling DCI (e.g., DCI used to schedule DL or UL data)

[0483] - Non-scheduling DCI (e.g., DCI not used for scheduling DL or UL data)

[0484] -PUCCH

[0485] -UCI

[0486] The UE can determine whether to apply cooperative communication based on the following conditions:

[0487] - The PDSCH(multiple) PDCCHs to which collaborative communication is applied have a specific format;

[0488] - The PDSCH(s) to which cooperative communication is applied include specific indicators indicating whether cooperative communication is applied;

[0489] - The PDSCH(s) to which the cooperative communication is applied are scrambled with a specific RNTI; or

[0490] - To enable collaborative communication, a specific interval is assumed with higher layers.

[0491] In the following text, for ease of description, "NC-JT situation" refers to when the UE receives the PDSCH or PDCCH of application cooperative communication based on conditions similar to those described above, and sends cooperative communication PUCCH or PDSCH based on similar conditions.

[0492] In the following text, 'determining the priority between A and B' can be done in various other ways, such as by selecting the one with higher priority according to a predetermined priority rule and performing the operation accordingly, or by omitting or discarding the operation for the one with lower priority.

[0493] In the following description, the examples above are illustrated in conjunction with various embodiments. One or more of the embodiments may be applied simultaneously or in combination, rather than independently.

[0494] <First Embodiment: Offset Configuration and UL Signal Transmission Method Considering UE Capabilities>

[0495] In order to transmit UL signals, the UE can change at least one of the UL beam, transmit power, and frequency before the signal is transmitted.

[0496] The UE can change the panel before signal transmission to transmit a UL signal. Therefore, the UE can change at least one of the UL beam, transmit power, frequency, and panel before signal transmission to transmit a UL signal. When multiple beams are divided into multiple beam groups, the panel corresponding to each beam group can be configured, such as configuring panel #1 to beam group #1, panel #2 to beam group #2, and so on. As another example, when multiple antenna modules for beamforming are included in the UE and the multiple antenna modules are mounted in different locations, the panel corresponding to each antenna module can be configured. Multiple panels can be configured in various other ways to divide multiple beams with different beamwidths or beam directions.

[0497] Changes to UL signal transmission can be made in the following situations:

[0498] - Case 1) When the UL signal is repeatedly changed through multiple TRPs (e.g., PUCCH, PUSCH, or SRS), when the UL beam, transmit power, or frequency is changed to change the TRP between repeated transmissions and perform a transmission, or when the UE changes the TRP between repeated transmissions and performs a transmission.

[0499] -Scenario 2) When the base station instructs UL signal transmission via MAC CE signaling or L1 signaling including DCI, when the UE changes the UL beam, transmit power or frequency to transmit the UL signal, or when the UE changes the panel to transmit the UL signal.

[0500] -Scenario 3) When SRS transmission is indicated or configured, when the UL beam, transmit power or frequency is changed to use multiple SRS resource sets or multiple SRS resources included in an SRS resource set, or when the UE changes the panel to perform SRS transmission.

[0501] In Case 1, the change in transmission information used to modify the TRP between repeated transmissions can be determined based on the mapping pattern between repeated transmissions and TRPs. Here, repeated transmissions include sending the same UL signal. When the base station repeatedly transmits the PDSCH, the 3GPP Release 16 standard supports two mapping patterns (e.g., 'sequential' and 'cyclic'). When the UE repeatedly transmits the UL signal through multiple TRPs, the mapping pattern used for repeatedly transmitting the PDSCH through multiple TRPs can be applied. 'Sequential' mapping is a scheme that modifies the TRP (such as {TRP1, TRP1, TRP2, TRP2}) with two repeated transmission units and then transmits, while 'cyclic' mapping is a scheme that modifies the TRP (such as {TRP1, TRP2, TRP1, TRP2}) in each repeated transmission and then transmits. When at least one of the UL beam, transmit power, and frequency (or frequency hopping) to be transmitted for transmitting the UL signal through multiple TRPs is determined, the UE can apply the UL transmission modification information determined according to the mapping scheme and transmit the UL signal. When the panel used to transmit UL signals via multiple TRPs is determined, the UE can apply the UL transmission change information determined according to the mapping scheme described above and transmit the UL signal. Here, the UL transmission change information may include at least one of the UL beam used to transmit the UL signal, the transmission power, and the frequency to be transmitted.

[0502] UL transmission change information may include a panel used to transmit UL signals. Repeated transmission of PUSCH via multiple TRPs may include PUSCH repeat transmission type A and PUSCH repeat transmission type B. PUSCH repeat transmission type B can treat nominal and actual repeats as repeat transmission units.

[0503] In scenario 2, the base station can configure higher-layer parameters for UL signal transmission to the UE and indicate the UE's UL signal (e.g., PUCCH, PUSCH, or SRS) transmission via L1 signaling (e.g., DCI). The time interval between the signaling from the base station indicating UL signal transmission to the UE and the UL signal transmitted by the UE can be defined as 'time offset', which can be replaced by 'scheduling interval', 'scheduling offset', or 'time interval'. When indicating UL signal transmission to the UE via L1 signaling including DCI, the time offset can be calculated as 'from the last symbol of the PDCCH including DCI transmitted to the first symbol of the UL (e.g., aperiodic / semi-persistent SRS or PUCCH or PUSCH including HARQ-ACK for PDSCH) transmitted'. If the UE's DCI decoding time is further considered, the time offset can be calculated as 'from the last symbol of the PDCCH including DCI transmitted to the first symbol of the UL signal transmitted'. When the base station indicates UL signal transmission via MAC CE signaling, the time offset can be calculated using the following method.

[0504] - Method 1: From the end of the last symbol of the PDSCH, which includes MAC CE signaling, to the beginning of the first symbol of the UL signal (e.g., aperiodic / semi-persistent SRS), transmitted.

[0505] -Method 2: From the end of the last symbol of the PUCCH / PUSCH that includes the HARQ-ACK for the PDSCH that includes MAC CE signaling to the beginning of the first symbol of the UL signal being sent.

[0506] - Method 3: From the end of the last symbol of the PUCCH / PUSCH that includes the HARQ-ACK for the PDSCH that includes MAC CE signaling to the beginning of the first symbol of the UL signal that is sent after the MAC CE application delay time (e.g., to the first time slot after 3ms have elapsed).

[0507] The time offset can be converted to an absolute time unit (e.g., ms) or a symbolic unit. When the UE receives an indication for UL signal transmission from the base station, it can change at least one of the UL beam, transmit power, and frequency used for UL transmission during the time offset. Alternatively, the UE can change the panel used for UL transmission during the time offset.

[0508] In scenario 3, when the UE transmits an SRS scheduled by the base station, the UE can change the UL beam, transmit power, and frequency according to the higher-level configuration of the SRS resources included in the SRS resource set to be transmitted, and then transmit the SRS. Alternatively, the UE can change the panel according to the higher-level configuration of the SRS resources and then transmit the SRS.

[0509] Depending on the UE's capabilities, the UE may require a transition time to change at least one of the UL beam, transmit power, and frequency. Depending on the UE's capabilities, the UE may also require a transition time to change the panel used for UL transmission. For example, the transition time can be considered when repeated transmissions are performed in long or short sub-time slot units. The transition time, depending on the UE's capabilities, can be applied to all or some of the UL beam, transmit power, or frequency determined for transmitting UL signals, depending on whether the transition time is satisfied during a time offset or between repeated transmissions of the UL signal.

[0510] As described above, a predetermined time may be required to perform changes to the UL beam, transmit power, or frequency. To accommodate this, an offset interval may be added between repeated transmissions, or the base station may instruct the UE to transmit the UL signal such that the time offset is greater than the predetermined time for the change. Alternatively, even when additional panel changes for UL transmission are performed, a predetermined time may be required, and to accommodate this, an offset interval may be added between repeated transmissions, or the base station may instruct the UE to transmit the UL signal such that the time offset is greater than the predetermined time.

[0511] The offset in the time domain of the UE's UL transmission can be understood as the time interval between repeated transmissions of the UL signal or the aforementioned time offset.

[0512] Figure 11 The illustration shows that, according to an embodiment, the UE repeatedly transmits PUCCH in a time slot when an offset indicated by the base station is applied.

[0513] refer to Figure 11 Offset 1120 can be set to a value greater than or equal to the time 1115 required between repeated PUCCH transmission 1105 and repeated PUCCH transmission 1110.

[0514] The following describes in detail, with reference to Embodiments 1-1 and 1-2, a method for the base station to determine the offset in the time domain to ensure the time required for the UE to change the UL beam, transmit power, or frequency according to its capabilities, and a method for the UE to transmit a UL signal indicated by the base station. For ease of description, Embodiments 1-1 and 1-2 are thus separated, and the embodiments may be performed individually or in combination.

[0515] <Example 1-1: Method for a base station to determine the offset and configure the offset for the UE based on the UE's reported UE capabilities>

[0516] As an example of a method for determining the time-domain offset of UL signal transmission, the UE can report UE capability information to the base station, which includes at least one of the following: UE capability for performing UL beam changing, UE capability for performing transmit power changing, and UE capability for performing frequency changing considering frequency hopping. Alternatively, the three UE capabilities can be reported to the base station separately. The UE can select and report some of the three UE capabilities. The UE can report a representative value of the UE capability used to change the transmission configuration of the UL signal.

[0517] Furthermore, if the UE can use multiple panels to transmit UL signals, then UE capabilities for panel changes can also be considered when determining the UE capabilities to be reported. That is, UE capability information including at least one of the following: UE capabilities for performing UL beam changes, UE capabilities for performing transmit power changes, UE capabilities for performing frequency changes considering frequency hopping, and UE capabilities for performing panel changes, can be reported to the base station. Alternatively, the four UE capabilities can be reported to the base station individually. The UE can select and report some of the four UE capabilities. The UE can report a representative value of the UE capability used to change the transmission configuration of the UL signal.

[0518] In the following text, the terms UE capability and UE capability information are used interchangeably in this disclosure and can be understood to have the same meaning.

[0519] As described above, the UE can provide information to the base station to determine the offset when some or all of the UL beam, transmit power, or frequency are changed while transmitting UL signals. Furthermore, if the UE supports multiple panels, information for the base station to determine the offset in the event of panel changes can be provided. The UE can report its capabilities for each UL beam change, transmit power change, or frequency change using one of the following methods. Additionally, the UE capability for panel changes can also be reported using one of the following methods:

[0520] - UE capabilities for UL transmission configuration changes in NR Release 15 / 16 can be reported. For example, a UE can set 'beamSwitchTiming' to one of {14, 28, 48} as in NR Release 15 / 16 to report UE capabilities for beam switching and to the base station. A UE can set 'beamSwitchTiming' to one of {224, 336} to report UE capabilities for panel changes and to the base station. Here, the number indicating 'beamSwitchTiming' is in symbol units; for example, when 'beamSwitchTiming' is set to "224" in a UE capability report for panel changes, this indicates that the beam switching processing time in the UE capability for panel changes is 224 symbols. Furthermore, 'beamSwitchTiming' can be set for each subcarrier interval.

[0521] - The time required for a change can be reported in symbolic or absolute time units (such as ms).

[0522] - The base station and UE can predefine processing times that indicate processing capabilities. The processing time for N processing capabilities can be predefined, and the processing time can vary depending on μ, which indicates the subcarrier spacing.

[0523] Tables 31 and 32 below show examples of processing times predefined by the base station and UE for processing capabilities n and n_1 for UL beam changes, transmit power changes, or frequency changes. The values ​​of the required time range can be set to establish relationships, such as {a1 < a2 < a3 < a4}, {b1 < a1, b2 < a2, b3 < a3}. The unit of the required time can be set to symbols or milliseconds (ms).

[0524] [Table 31]

[0525]

[0526] [Table 32]

[0527]

[0528] When a UE reports processing time for changing at least one of UL beam, transmit power, and frequency as a UE capability, the UE can determine the value to report by considering each UL signal. For example, when reporting processing time for UL beam changing as a UE capability, the reporting can be done where the UE capability is divided into UE capability for beam changing for PUCCH, UE capability for beam changing for PUSCH, and UE capability for beam changing for SRS. UE capability for transmit power changing and capability for frequency changing can also be divided and reported in the same manner based on PUCCH, PUSCH, or SRS. When a UE reports UE capability for changing at least one of UL beam, transmit power, and frequency for PUCCH, the determination can be made by considering the number of PUCCH resources, the amount of configured spatial relationship information, the amount of activated spatial relationship information, and frequency hopping configuration. When a UE reports its capabilities to change each of the UL beam, transmit power, and frequency of a PUSCH, the determination can be made by considering the PUSCH precoding method (e.g., 'codebook' or 'non-codebook'), the number of SRS resource sets associated with the PUSCH transmission, the number of SRS resources configured in the associated SRS resource sets, the relationship between the PUSCH and SRS antenna ports, and the frequency hopping configuration.

[0529] When a UE reports its capability to change each of the UL beam, transmit power, and frequency of the SRS, the determination can be made by considering the SRS transmission indication method (e.g., DCI-based or MAC CE-based), SRS timeline information (e.g., periodic SRS, semi-persistent SRS, or aperiodic SRS), the use of the SRS (e.g., 'beamManagement', 'codebook', 'nonCodebook', or 'antennaSwitching'), the number of SRS resource sets, and the number of SRS resources. Furthermore, when a multi-panel UE reports the processing time used to change a panel as a UE capability, the UE can consider the UL signal to determine the value to report.

[0530] Alternatively, the UE may identify and report UE capabilities for at least one change in UL beam, transmit power, and frequency, without distinguishing UE capabilities for each UL signal. The UE may identify and report UE capabilities for panel changes, without distinguishing UE capabilities for each UL signal.

[0531] The UE can attach a report indicating whether the UL beam, transmit power, and frequency can be changed simultaneously or sequentially. Here, a multi-panel UE can report whether the panels can be changed simultaneously with the corresponding UE capabilities. That is, the UE can report whether the UL beam, transmit power, frequency, and panel can be changed simultaneously with the corresponding UE capabilities. As an example of a corresponding UE capability, the UE can choose either 'simultaneously' or 'sequentially' and report it to the base station. If the UE reports the UE capability as 'simultaneously', then the UE can change the UL beam, transmit power, and frequency simultaneously. If the UE supports multiple panels, the panels can also be changed simultaneously. If the UE reports the UE capability as 'sequentially', then the UE can change the UL beam, transmit power, and frequency sequentially. If the UE supports multiple panels, the panels can also be changed sequentially.

[0532] In addition to reporting UE capabilities for supporting changes in UL beams, transmit power, frequency, and panel, the UE can also report the UE capability 'beamCorrespondenceWithoutUL-BeamSweeping' to the base station to indicate whether beam correspondence requirements are met. Beam correspondence refers to the UE's ability to select the beam for UL transmission based on DL measurements without relying on UL beam scanning. If the UE reports that 'beamCorrespondenceWithoutUL-BeamSweeping' as a UE capability for beam correspondence is supported ('supported'), the UE can select the UL beam for UL transmission without UL beam scanning and then transmit the UL signal.

[0533] The base station can determine the time offset for ensuring the application of UL transmission change information by using the UE capabilities reported by the UE. The base station can consider one or a combination of the following options to determine the offset:

[0534] - Option 1) The offset may be determined based on the maximum value of at least one of the UE capabilities reported by the UE for UL beam changing, UE capabilities for transmit power changing, or UE capabilities for frequency changing.

[0535] - Option 2) The offset is determined based on the maximum value of the UE capabilities required to perform the actual UL transmission changes from the UE capabilities reported by the UE. For example, when the base station instructs the UE to change only the UL beam and transmit power of the UL signal, the offset can be determined based on the maximum value of the UE capabilities for UL beam changes and the UE capabilities for transmit power changes. For combinations of UL transmission change information other than those in the examples above, the offset can be determined in the same manner as in the examples above.

[0536] - Option 3) The offset can be determined based on the sum of the UE capabilities reported from the UE for UL beam changes, UE capabilities for transmit power changes, or UE capabilities for frequency changes.

[0537] - Option 4) The offset can be determined based on the sum of UE capabilities that perform the actual UL transmission changes from the UE capabilities reported by the UE. For example, when the base station instructs the UE to change only the UL beam and transmit power of the UL signal, the offset can be determined based on the sum of the UE capabilities for UL beam changing and the UE capabilities for transmit power changing. For combinations of UL transmission change information other than those in the examples above, the offset can be determined in the same manner as in the examples above.

[0538] - Option 5) When the offset is determined using one of Options 1 to 4 above, the offset may be determined taking into account the configuration of each UL transmission signal. For example, when the base station determines the offset for repeatedly transmitting PUCCH over multiple TRPs according to Option 1, the offset may be determined based on the UE capabilities reported by the UE, taking into account the PUCCH configuration. As another example, when the UE does not distinguish the UE capabilities of each UL signal, the offset is determined due to the additional time required by the base station to adjust the PUCCH configuration to the UE capabilities reported by the UE. This may also be applied when the base station determines the offset for transmitting another UL signal (e.g., PUSCH or SRS).

[0539] - Option 6) When the offset is determined using one of the options 1 to 4 above, the offset can be determined without distinguishing the configuration of each UL transmission signal.

[0540] - Option 7) The base station can determine any value as the offset. In this case, higher-level parameter configurations or UL resource configurations of the UL signal can be considered.

[0541] -Option 8) When the UE supports multiple panels, the UE's ability to change panels can be further considered when determining the offset using options 1 to 6.

[0542] Each of the options above is an example of the UE reporting all UE capabilities for the three types of UL transmission change information. However, if the UE only reports some UE capabilities, the base station can determine the offset by applying only the reported UE capabilities to each option.

[0543] When the UE reports that the UL beam, transmit power, and frequency can be changed simultaneously, the base station can select option 1 or option 2 to determine the offset. When the UE reports that the UL beam, transmit power, and frequency can be changed sequentially, the base station can select option 3 or 4 to determine the offset. When the UE supports multiple panels and reports that the UL beam, transmit power, frequency, and panel (or at least two or more of them) can be changed simultaneously, the base station can further consider the UE capabilities for panel changes in option 1 according to option 8 to determine the offset, or it can further consider the UE capabilities for panel changes in option 2 according to option 8 to determine the offset. This is an example of the above embodiment, and the base station can determine the offset by considering one or a combination of options 1 to 8 above based on the UE capabilities reported by the UE.

[0544] The base station can adjust the offset value determined by the above options based on whether the UE supports beam correspondence reported by the UE capability. For example, if the UE supports beam correspondence, the base station can determine the offset value determined using the above options as the final offset value or adjust it to a smaller value. If the UE does not support beam correspondence, the base station can add additional required time to the offset value determined using the above options.

[0545] The base station can adjust the offset value determined by the above options based on whether the UE reports a UL beam to be transmitted on the UL of multiple TRPs. For example, if the UL beam is reported to the base station, the corresponding UL beam is a 'known' beam for the UE. If the UL beam is not reported to the base station, the corresponding UL beam is an 'unknown' beam for the UE. If the UE reports a UL beam to be transmitted on the UL to the base station, the base station can determine the offset value determined by the above options as the final offset value or adjust it to a smaller value. If the UE does not report a UL beam to be transmitted on the UL to the base station, the base station can add additional time to the offset value determined by the above options.

[0546] The base station can notify the UE of the determined offset. In this case, the base station can notify the UE of the offset explicitly or implicitly:

[0547] - When the base station moves to the offset determined by the UE's explicit configuration:

[0548] The base station can configure the offset using new higher-layer parameters and explicitly notify the UE of the configured offset. For example, the new higher-layer parameter 'timeDurationForULSwitch' can be added to the configuration information used for PUCCH transmission, such as PUCCH-FormatConfig or PUCCH-ConFIG. Similarly, for PUSCH or SRS, new parameters for the offset can be added to the higher-layer parameters used for PUSCH transmission and the higher-layer parameters used for SRS transmission.

[0549] The above example is one of the methods for configuring new higher-layer parameters to indicate the offset determined by the base station to the UE, and can be defined as higher-layer parameters with different names that have the same function.

[0550] When the base station implicitly indicates the determined offset:

[0551] Instead of directly configuring the offset using higher-level parameters, the base station can implicitly indicate the offset through (multiple) other configurations used to transmit UL signals. For example, the offset can be indicated by 'startingSymbolIndex' configured in the higher-level parameter PUCCH-Resource's PUCCH-format[a] (where a is, for example, 0, 1, 2, 3, or 4).

[0552] More specifically, as an example of one of the enhanced methods for indicating repeated transmissions of PUCCH in a time slot, the startingSymbolIndex in the PUCCH-format[a] of the PUCCH-Resource can be configured as many times as the number of times the PUCCH is repeated in the time slot. If the number of repetitions in the time slot is 2, then startingSymbolIndex indicates the start symbol of the transmission for the first PUCCH repeated transmission in the time slot, and a newly added 'startingSymbolIndex2' can indicate the start symbol of the transmission for the second PUCCH repeated transmission in the time slot. The symbol position indicated by startingSymbolIndex must be earlier than the symbol position indicated by startingSymbolIndex2, and the interval between the two symbols can be set by the base station such that the interval becomes greater than the offset determined by the base station and the value of one PUCCH transmission symbol nrofSymbols. As another example, the base station can implicitly notify the UE of the offset through the PUCCH resource configuration for PUCCH transmission.

[0553] Alternatively, when the base station schedules a PUCCH that includes HARQ information for the PDSCH to the UE, a PDSCH-to-HARQ_feedback timing indicator can be provided to the UE, causing the time offset to become a larger value than the determined offset. For other UL signals besides the PUCCH (e.g., PUSCH or SRS), the UE can be implicitly notified of the offset via the transmission timing indicated by higher-layer parameters of the DCI or UL signal.

[0554] <Examples 1-2: Method for a UE to transmit a UL signal indicated by a base station according to its capabilities>

[0555] When a UE is instructed by a base station to repeatedly transmit UL signals, the UE can determine the operation of repeated UL transmissions based on whether the offset determined by the base station is explicitly configured or implicitly indicated. If the UE is explicitly configured with an offset by the base station, the UE can transmit the interval between repeated transmissions and transmit UL signals based on the offset in the time domain. If the UE is implicitly notified of the offset, the UE transmits UL signals according to the higher-level parameters configured by the base station for UL signals.

[0556] When a UE is explicitly configured with an offset or implicitly notified of an offset and applies that offset to repeated transmissions of UL signals, the UE may, depending on its capability, change at least one of the UL beam, transmit power, or frequency during the offset and transmit it. If the offset determined by the base station is set to be greater than the UE's capability to change the UL beam, transmit power, or frequency, the UE may change the UL beam or transmit power to change the TRP between repeated transmissions and then transmit it, or it may perform a frequency change for frequency hopping. If the offset determined by the base station is set to be less than the UE's capability to change the transmit power or frequency, the base station and the UE may consider one or a combination of the following operations to predefine a default UL transmission method for repeated transmissions of UL signals.

[0557] -Use the same UL beam, transmit power and frequency as the previous repeated transmission to transmit UL signals;

[0558] Because the offset determined by the base station is less than the UE's capability, the UE cannot satisfy the time requirement to change the beam, transmit power, or frequency between repetitive transmissions. Therefore, the UE can utilize the beam, transmit power, and frequency applied to the previous repetitive transmission to perform the next repetitive transmission. A previous repetitive transmission can refer to a repetitive transmission immediately preceding the repetitive transmission to be transmitted. Furthermore, at least one of the same UL beam, transmit power, or frequency as the previous (repetitive) transmission can be used to change the remaining items. For example, the same UL beam and frequency as the previous (repetitive) transmission can be used, and the transmit power can be changed for the next repetitive transmission.

[0559] - Transmit UL signals using the default settings for UL beam, transmit power, and frequency:

[0560] Because the offset determined by the base station is less than the UE's capability, the UE cannot satisfy the time requirement to change the beam, transmit power, or frequency between repeated transmissions. Therefore, the UE can utilize a default UL beam, default transmit power, and default frequency as previously defined to perform the next repeated transmission. Here, the base station and the UE can define default transmission information for each UL signal (e.g., PUCCH, PUSCH, or SRS).

[0561] Alternatively, the base station and the UE can jointly define default transmission information for the UL signal. Furthermore, at least one of the UL beam, transmit power, or frequency can be used as the default configuration, and the others can be changed. For example, the UL beam and frequency can be used as the default configuration, and the transmit power can be changed for the next repeated transmission.

[0562] -Conditionally change the UL beam, transmit power, or frequency, and transmit the UL signal:

[0563] If the mapping between UL repeat transmission and TRP is set to 'sequential', the UL beam, transmit power, or frequency can be changed and transmitted at the repeat transmission time that satisfies the UE's capabilities.

[0564] In cases where a retransmission timing does not meet the UE's capabilities, the UE can transmit a UL signal with the same configuration as the previous retransmission timing. For example, if the mapping is configured as {TRP1, TRP1, TRP2, TRP2}, the first two retransmission timings are transmitted using the UL beam, transmit power, and frequency for TRP1. The third retransmission timing should be changed with the UL beam, transmit power, and frequency for TRP2 and transmitted, but because the offset is less than the UE's capabilities, the UE transmits a UL signal with the configuration for TRP1 without changing the UL transmission information. The UE can then change to the UL beam, transmit power, and frequency for TRP2 and transmit a fourth retransmission timing.

[0565] - Repeated transmission of UL signals by applying variable configurations in UL beam, transmit power, or frequency:

[0566] When the UE compares the offset set by the base station with its capabilities, the UE can apply some variable configurations of its capabilities that are less than the offset to the next repetition timing. For example, if the offset is greater than the UE capability for UL beam change but less than the UE capability for transmit power change or frequency change, the UE can change only the UL beam and apply the same repetition timing as the previous repetition timing for transmit power and frequency, and then transmit that next repetition timing. If the UE changes the UL beam, transmit power, and frequency sequentially, the UE compares the offset determined by the base station with the combination of UE capabilities for UL beam change, transmit power change, and frequency change. If the combination is less than the offset, the change in UL beam, transmit power, or frequency is determined based on the priority of the UL beam, transmit power, or frequency previously determined between the base station and the UE. For example, if the offset determined by the base station is less than the sum of all UE capabilities, the sum of UE capabilities for UL beam and transmit power change, the sum of UE capabilities for UL beam and frequency change, and the sum of UE capabilities for transmit power and frequency change are less than the offset, and the base station and UE have previously defined priorities {UL beam > transmit power > frequency}, then the UE can change the UL beam and transmit power and transmit a UL signal.

[0567] - Discard some symbols or repeat transmission timings, and send UL signals:

[0568] To apply UL transmission change information and retransmit UL signals, the UE can discard some symbols during the retransmission timing to change at least one of the beam, transmit power, or frequency, and transmit UL signals using the remaining resources. For example, if the mapping between repeated PUCCH transmissions and TRPs is set to {TRP1, TRP1, TRP2, TRP2}, then in the third retransmission, no PUCCH is transmitted during the previous symbol period until the time required to change the UL beam, transmit power, and frequency for TRP2 is satisfied. For the remaining symbols, after the time required to change the UL beam, transmit power, and frequency is satisfied, the UE can retransmit the third PUCCH.

[0569] For example, if the time required for the UL beam, transmit power, and frequency of the retransmission with the changed TRP is not met, the UE can discard the corresponding UL retransmission opportunity. If the mapping between PUCCH retransmissions and TRPs is set to {TRP1, TRP1, TRP2, TRP2}, the third PUCCH retransmission opportunity may be discarded. Subsequently, the fourth PUCCH retransmission opportunity can be transmitted using the UL beam, transmit power, and frequency changed for TRP2. As another example, if the mapping between PUCCH retransmissions and TRPs is set to {TRP1, TRP2, TRP1, TRP2}, the second and fourth PUCCH retransmission opportunities can be discarded, and PUCCH retransmissions based on a single TRP can be supported.

[0570] If PUCCH retransmission is performed using the method presented herein, taking into account the channel state for each TRP, an increase in the coverage of the UL control signal can be expected. Furthermore, since transmit power is controlled per transmit / receive point, effective battery management of the UE can be anticipated.

[0571] A similar approach can be applied to the relationship between the time offset for UL signal transmission and the UE's capabilities. If the time offset is greater than the UE's capabilities for changing the UL beam, transmit power, or frequency, the UE can transmit the UL signal. If the time offset is less than the UE's capabilities for changing the UL beam, transmit power, or frequency, the UE can consider one or a combination of the following operations to transmit the UL signal, similar to the situation described above where the offset between repeated transmissions does not meet the UE's capabilities.

[0572] - UL signals are transmitted using the same UL beam, transmit power, and frequency as previous UL signal transmissions.

[0573] - Transmit UL signals using the default settings for UL beam, transmit power, and frequency.

[0574] - Repeated transmission of UL signals by applying variable configurations in UL beam, transmit power, or frequency.

[0575] - Discard some symbols or the first repeated transmission timing of the first repeat transmission timing and send the UL signal.

[0576] The operation based on the above conditions has been described regarding methods for a UE to change the UL beam, transmit power, or frequency for supporting a single panel. However, if the UE supports multiple panels, the UE identifies whether the offset determined by the base station is set to be less than the UE capability for changing the UL beam, transmit power, frequency, or panel. If the offset determined by the base station is greater than the UE capability for changing the UL beam, transmit power, frequency, or panel, the UE can transmit a UL signal. If the offset is set to be less than the UE capability for changing the UL beam, transmit power, frequency, or panel, the UE can further consider the UE capability for panel changing in the above-described situation, similar to the offset between repeated transmissions not meeting the UE capability, to transmit a UL signal according to one or a combination of the following operations.

[0577] - UL signals are transmitted using the same UL beam, transmit power, frequency, and panel as previous UL signal transmissions.

[0578] - Transmit UL signals using the default settings for UL beam, transmit power, frequency, and panel.

[0579] - Repeatedly transmit UL signals by applying variable configurations in the UL beam, transmit power, frequency, or panel.

[0580] - Discard some symbols or the first repeated transmission timing of the first repeat transmission timing and send the UL signal.

[0581] Here, the previous UL signal includes the most recently transmitted physical channel as the UL signal to be transmitted (e.g., PUCCH, PUSCH, or SRS). The base station and UE can define default transmission information for each UL signal (e.g., PUCCH, PUSCH, or SRS). Alternatively, the base station and UE can define default transmission information publicly for UL signals.

[0582] <Second Embodiment: Method for Controlling Transmission Power Divided by TRP in FR1>

[0583] If the UE repeatedly transmits the PUCCH through multiple TRPs in a congested environment, the PUCCH can be transmitted more stably than when it is repeatedly transmitted through a single TRP, since it is transmitted over multiple channel links. Furthermore, because the PUCCH is repeatedly transmitted using multiple TRPs, a significant performance gain due to macro diversity can be achieved. Each channel link is established between multiple TRPs and the UE, and the path loss and other channel characteristics may vary due to different distances between the TRPs and the UE. Therefore, to transmit the PUCCH over multiple TRPs, transmit power control needs to consider the UL beam and the different path losses of each TRP.

[0584] In FR2, the higher-layer parameter PUCCH-SpatialRelationInfo is defined for each PUCCH resource used to transmit the PUCCH. If only one PUCCH-SpatialRelationInfo is configured, the PUCCH resource is transmitted according to the corresponding PUCCH-SpatialRelationInfo without a separate activation process. If multiple PUCCH-SpatialRelationInfos are configured, the PUCCH-SpatialRelationInfo is activated for each PUCCH via MAC CE. Because PUCCH-SpatialRelationInfo includes reference RS information for configuring the UL beam and parameters for controlling the transmit power, the UL beam and transmit power can be determined when transmitting the PUCCH resource.

[0585] According to embodiments of this disclosure, by enhancing a PUCCH-SpatialRelationInfo in a PUCCH resource used to activate the UE to repeatedly transmit the same PUCCH over multiple TRPs, a number of PUCCH-SpatialRelationInfos can be activated as many as the number of supported TRPs. Since the 3GPP Release 17 standard supports up to two TRPs, up to two PUCCH-SpatialRelationInfos can be activated in a single PUCCH resource. Each PUCCH-SpatialRelationInfo can be used to determine the UL beam and transmit power for each TRP, and the PUCCH can be transmitted by referencing the PUCCH-SpatialRelationInfo corresponding to each TRP, depending on the mapping method between repeated transmissions and TRPs. According to embodiments, two or more PUCCH-SpatialRelationInfos can also be activated in a single PUCCH resource.

[0586] Unlike transmitting PUCCH in FR2, PUCCH-SpatialRelationInfo is not configured when transmitting PUCCH in FR1. One reason is that FR1 operates in a lower frequency band than FR2, and the UE uses omnidirectional beamforming for transmitting and receiving signals. In FR1, since PUCCH-SpatialRelationInfo is not configured for each PUCCH resource, the UE can determine the transmission power based on the default operation corresponding to the case where PUCCH-SpatialRelationInfo is not configured for the UE, in the aforementioned transmit power control method. However, when the UE repeatedly transmits PUCCH through multiple TRPs in FR1, the default transmit power control method of the NR version 15 / 16 standard cannot determine the transmit power for each TRP individually, therefore, FR1 requires an enhanced transmit power control method.

[0587] As an enhancement to the method for controlling the transmission power of multiple TRPs in FR1, an enhanced default transmission power control method and a method utilizing the PUCCH-SpatialRelationInfo framework are provided in FR1. This enhanced transmission power control method is not limited to repeated PUCCH transmissions, but can also be used for other methods of transmitting PUCCHs using multiple TRPs. For example, even when the UE performs a single transmission, rather than repeatedly transmitting PUCCHs including different UCIs through different TRPs, the enhanced transmission power control method can be used to apply transmission power to each TRP. For ease of description, embodiments 2-1 and 2-2 are thus separated, and the embodiments can be performed individually or in combination.

[0588] <Example 2-1: Enhanced Default Transmit Power Control Method for Sending PUCCH via Multiple TRPs in FR1>

[0589] The UE can determine the transmit power for each TRP by enhancing the method used to determine the transmit power of a PUCCH transmission using the existing default transmit power control method. If the UE transmits the PUCCH over multiple TRPs, the transmit power is determined according to the enhanced default transmit power control method, and if the PUCCH is transmitted over a single TRP, the transmit power is determined according to the default transmit power control method of the NR version 15 / 16 standard.

[0590] Before supporting the UE, the base station can receive reports from the UE regarding the UE's capability to perform transmit power control for each TRP in FR1. If the UE reports that its capability supports transmit power control for each TRP, the base station can configure higher-layer parameters to perform transmit power control for each TRP in FR1. For example, the UE can set the UE capability 'separatePC-FR1' to 'Support' or 'Enable' and report it to the base station. The base station and UE can predefine one or a combination of the following conditions as conditions for transmitting PUCCH through multiple TRPs:

[0591] The mapping pattern between multiple TRPs and repeated transmissions is set by higher-level parameters, and the sent PUCCH resources are configured to be sent repeatedly.

[0592] - The PDCCH of the DCI that schedules the PUCCH is sent through multiple TRPs, and the scheduled PUCCH resources are configured to be sent repeatedly.

[0593] - The UE is scheduled to receive PDSCH from multiple TRPs, and the PUCCH resources for transmitting the HARQ-ARQ of the received PDSCH are configured to be repeatedly transmitted. The PDSCH may include both repeatedly transmitted and non-repeated cases. Furthermore, it may include cases where the PDCCH scheduling the PDSCH is received from a CORESET configured with two different CORESETPoolIndexes, or cases where the PDCCH scheduling the PDSCH is received from a CORESET whose CORESETPoolIndex is not set and a CORESET whose CORESETPoolIndex is set to 1.

[0594] - This indicates that new parameters for transmit power control for each TRP are configured in the higher-level parameter configuration for PUCCH transmission, and that the transmitted PUCCH resources are configured to be transmitted repeatedly. For example, the new parameter 'enableTwoDefaultPowerControl' can be set to 'enabled' in the higher-level parameter PUCCH-ConFIG.

[0595] - New higher-level parameters are configured to indicate that each hop is transmitted through a different TRP, similar to intra-slot frequency hopping for a single PUCCH transmission. The first and second hops are transmitted through different TRPs. For example, the new higher-level parameter 'intraslotBeamHopping' in PUCCH-FormatConfig can be set to 'Enable'.

[0596] If none of the conditions previously defined by the base station and UE are met, the UE can transmit the PUCCH according to the default transmit power control method of the NR version 15 / 16 standard. If the conditions previously defined by the base station and UE are met, the default transmit power control method can be enhanced to select transmit power control parameters for each TRP based on the P0-PUCCH, PUCCH-PathlossReferenceRS, and closed-loop index in the transmit power control parameters.

[0597] -P0-PUCCH: The UE obtains the minimum value among the p0-PUCCH-Id values ​​configured in the higher-layer parameter p0-Set and the p0-PUCCH-Value for the next minimum value. The minimum value is applied to the P0 of the TRP for the first PUCCH transmission, and the next minimum value is applied to the P0 of another TRP. If only one P0-PUCCH is configured in p0-Set, the same P0-PUCCH-Value is applied, and the PUCCH is transmitted through two TRPs.

[0598] -PUCCH-PathlossReferenceRS: If the UE is configured with pathlossReferenceRS but not with PUCCH-SpatialRelationInfo, the UE obtains the PUCCH-PathlossReferenceRS with pucch-PathlossReferenceRS-IDs of indices 0 and 1 from among the PUCCH-PathlossReferenceRS (these PUCCH-PathlossReferenceRS are RS resources of the supporting cell or primary cell indicated by pathlossReferenceLinking (if configured)). The referenceSignal of the PUCCH-PathlossReferenceRS with index 0 is used to calculate the path loss of the TRP for the first PUCCH transmission, and the referenceSignal of the PUCCH-PathlossReferenceRS with index 0 is used to calculate the path loss of the other TRP. If only one PUCCH-PathlossReferenceRS is configured in the pathlossReferenceRS, the same referenceSignal is applied to transmit PUCCH through both TRPs.

[0599] Closed-loop index: If the UE is configured with twoPUCCH-PC-AdjustmentState and not configured with PUCCH-SpatialRelationInfo, the closed-loop index of the TRP of the first PUCCH transmission is set to 0, and the closed-loop index of the other TRP is set to 1.

[0600] <Example 2-2: Transmit Power Control Method for Each TRP Using the PUCCH-SpatialRelationInfo Framework in FR1>

[0601] In 3GPP Releases 15 and 16, PUCCH-SpatialRelationInfo was not configured in FR1. However, in Release 17, a framework associated with the existing PUCCH-SpatialRelationInfo can be introduced to transmit PUCCHs over multiple TRPs in FR1. The PUCCH-SpatialRelationInfo framework can include PUCCH-SpatialRelationInfo information and also includes higher-layer transmit power parameters associated with PUCCH-SpatialRelationInfo and a MAC CE for activation.

[0602] The base station can receive reports from the UE regarding its ability to control transmit power for each TRP in FR1. If the UE reports that its UE capability supports transmit power control for each TRP, the base station can configure higher-layer parameters to perform transmit power control for each TRP in FR1. For example, the UE can set the UE capability 'separatePC-FR1' to 'Support' or 'Enable' and report it to the base station.

[0603] The base station can support one or a combination of the following operations to perform transmit power control for each TRP in FR1:

[0604] - Example 2-2-1) Operations using PUCCH-SpatialRelationInfo in FR1:

[0605] The base station can even activate PUCCH-SpatialRelationInfo for PUCCH resources in FR1. If a PUCCH is transmitted via M TRPs, then for each PUCCH resource, at most M PUCCH-SpatialRelationInfos can be activated. In this disclosure, for ease of description, it is assumed that M = 2. If only two PUCCH-SpatialRelationInfos are configured, then the two PUCCH-SpatialRelationInfos can be applied to PUCCHs transmitted via multiple TRPs without additional MAC CE signaling. Whether a PUCCH is transmitted via multiple TRPs can follow the conditions for transmitting a PUCCH via multiple TRPs described above in conjunction with embodiment 2-1. If the corresponding conditions are not met, the UE can follow the transmit power control method of the NR version 15 to 16 standard. If more than two PUCCH-SpatialRelationInfos are configured for the UE, then MAC CE can be used to indicate the activated PUCCH-SpatialRelationInfo for each PUCCH resource. The MAC CE can use the same format as the MAC CE used to activate the PUCCH spatial relationship in the standard NR version 15 / 16, and up to two PUCCH-SpatialRelationInfos can be configured in the corresponding resource and PUCCH resource ID (only one PUCCH-SpatialRelationInfo can be activated in version 15 / 16). Since the PUCCH-SpatialRelationInfo can also include reference information for determining the UL beam, the UE can transmit the PUCCH according to the spatial settings when receiving or transmitting the DL RS or SRS indicated in the 'referenceSignal' area.

[0606] When the mapping between the TRP and PUCCH repetition transmissions is determined and the active PUCCH-SpatialRelationInfo is applied, mapping and connection need to be performed using the active PUCCH-SpatialRelationInfo. If the UE sends a PUCCH as {1,1,2,2}, since the mapping pattern between the TRP and PUCCH repetition transmissions is set to 'sequential', the smaller ID in the two active PUCCH-SpatialRelationInfos can be determined to correspond to "1", and the larger ID can be determined to correspond to "2". That is, when the UE sends a PUCCH corresponding to "1", the transmission power is determined based on the smaller ID PUCCH-SpatialRelationInfo, and the PUCCH is sent.

[0607] When sending a PUCCH corresponding to "2", the transmission power can be determined based on the larger ID PUCCH-SpatialRelationInfo, and the PUCCH can be sent. The same method can also be applied to other mapping styles.

[0608] Within the active values, the UE can determine the transmission power of the first repeated TRP based on the PUCCH-SpatialRelationInfo set to the smaller ID, and determine the transmission power of another TRP based on the PUCCH-SpatialRelationInfo set to the larger ID. This transmission method also applies to FR2. If only one PUCCH-SpatialRelationInfo is active in the PUCCH resource, the UE transmits the PUCCH according to the parameters configured in an active PUCCH-SpatialRelationInfo, instead of transmitting the PUCCH through multiple TRPs.

[0609] - Example 2-2-2) uses new higher-level parameters for transmit power control and the operation of MAC CE for activating these new higher-level parameters:

[0610] Similar to the configuration of PUCCH-SpatialRelationInfo, the base station can configure new higher-layer parameters for the transmit power in FR1 for the UE. Table 33 below provides examples of the new higher-layer parameters, which include transmit power control parameters for each TRP. In the following text, for ease of description, the new higher-layer parameter PUCCH-PowerControlInfo is designated as PUCCH-PowerControlInfo, but it can be referred to by the name of another higher-layer parameter that performs the same function.

[0611] [Table 33]

[0612]

[0613] Two or more PUCCH-PowerControlInfos can be configured. If the base station schedules PUCCHs to transmit PUCCHs over multiple TRPs, or configures periodic or semi-persistent PUCCHs, the number of configured PUCCH-PowerControlInfos may require MAC CE activation. If only two PUCCH-PowerControlInfos are configured, these two PUCCH-PowerControlInfos can be applied to PUCCHs transmitted over multiple TRPs without additional MAC CE signaling. Whether a PUCCH is transmitted over multiple TRPs can follow the conditions for transmitting PUCCHs over multiple TRPs described above in conjunction with embodiment 2-1. If the corresponding conditions are not met, the UE can follow the transmit power control method of NR version 15 to 16. If more than two PUCCH-PowerControlInfos are configured, MAC CE for two PUCCH-PowerControlInfos needs to be activated.

[0614] Figure 12 A MAC CE for activating new higher-level parameters according to an embodiment is shown, which are used to perform transmit power control for each TRP in FR1.

[0615] refer to Figure 12 PUCCH-PowerControlInfo can be activated using MACCE, which is similar to MAC CE used to activate PUCCH-SpatialRelationInfo.

[0616] MAC CE includes the supporting cell ID 1200 to which the MAC CE command will be applied, BWP ID 1205, PUCCH resource ID 1210 indicating the higher-layer parameter PUCCH-ResourceId, and S0 to S10 indicating the activation status of PUCCH-PowerControlInfo as indicated by PUCCH-PowerControlInfoId. k Area 1215. S k Indicates the activation status of PUCCH-PowerControlInfo with PUCCH-PowerControlInfoId = k. If S k If set to 1, this indicates that PUCCH-PowerControlInfo is activated for the indicated PUCCH resource, while if S kIf set to 0, this indicates that PUCCH-PowerControlInfo is deactivated. Here, K indicates the maximum number of PUCCH-PowerControlInfo that can be configured. A maximum of two active PUCCH-PowerControlInfo can be configured for a single PUCCH resource.

[0617] Similar to the case of reusing PUCCH-SpatialRelationInfo in FR1, the mapping between the active PUCCH-PowerControlInfo and the repeated transmission can be determined based on the mapping pattern between the repeated transmission and the TRP. When the mapping pattern between the repeated transmission and the TRP is {1,1,2,2}, when the UE transmits the PUCCH corresponding to "1", the transmission power is determined based on the small ID PUCCH-PowerControlInfo, and the PUCCH is transmitted.

[0618] When transmitting a PUCCH corresponding to "2", the transmission power can be determined based on the larger ID PUCCH-PowerControlInfo, and the PUCCH can be transmitted. The same method can also be applied to other mapping patterns. In the active value, the UE can determine the transmission power for the first repeated transmission TRP based on the PUCCH-PowerControlInfo set to the smaller ID, and can determine the transmission power for another TRP based on the PUCCH-PowerControlInfo set to the larger ID. If only one PUCCH-PowerControlInfo is active in the PUCCH resource, the UE transmits the PUCCH according to the parameters configured in one active PUCCH-PowerControlInfo, instead of transmitting the PUCCH through multiple TRPs.

[0619] - Example 2-2-3) Default transmit power control operation using new higher-level parameters for transmit power control:

[0620] To determine the PUCCH transmit power for each TRP, default transmit power control can be performed without using a separate MAC CE activation process. As in the example above, when only two PUCCH-PowerControlInfo values ​​are configured, the UE can determine the transmit power for each TRP without requiring additional MAC CE activation. Similarly, a new higher-layer parameter, PUCCH-PowerControlInfo-r17, can be defined as shown in Table 34 below to determine the transmit power for each TRP without using a MAC CE activation process.

[0621] [Table 34]

[0622]

[0623] As shown in Table 34 above, the parameters for transmit power control for two TRPs can be included in a new higher-layer parameter PUCCH-PowerControlInfo-r17 in sequence. The base station can configure a PUCCH-PowerControlInfo-r17 for the UE. If the UE transmits PUCCH through multiple TRPs, the default transmit power control can be performed according to a configured PUCCH-PowerControlInfo-r17. The UE can apply the first value of the sequence in a configured PUCCH-PowerControlInfo-r17 to determine the transmit power of the TRP for which the first PUCCH is repeatedly transmitted, and can apply the second value of the sequence to determine the transmit power of the other TRP. In this case, whether the PUCCH is transmitted through multiple TRPs can follow the conditions for transmitting PUCCH through multiple TRPs described above in conjunction with embodiment 2-1. If the corresponding conditions are not met, the UE can follow the transmit power control method of the NR version 15 to 16 standard.

[0624] Example 2-2-4) A new MACCE-based transmit power control operation for activating transmit power control parameters in NR version 15 / 16 standards:

[0625] The base station can use the power transmission control parameter set configured in NR Release 15 or 16 and the new MAC CE that activates that power transmission control parameter set to determine the transmit power for transmitting PUCCHs over multiple TRPs without adding separate new higher-layer parameters. As shown in Table 34 above, the parameters for transmit power control are configured in the higher-layer parameter PUCCH-PowerControl. Here, based on the NR Release 15 standard, a p0-Set with up to 8 P0-PUCCHs and a pathlossReferenceRS with up to 4 (up to 64 in NR Release 16) PUCCH-PathlossReferenceRS can be configured in PUCCH-PowerControl. Thus, the values ​​in each parameter set are activated by the new MAC CE to select the parameter from multiple transmit power control parameters used to determine the transmit power for each TRP.

[0626] Figure 13A and Figure 13BA new MACCE for activating PUCCH transmit power control parameters is illustrated according to an embodiment. Specifically, Figure 13 shows an example of a new MACCE that can be defined based on transmit power control parameters of NR versions 15 and 16.

[0627] Because the maximum configurable PUCCH-PathlossReferenceRS differs in NR versions 15 and 16, the number of bits and their format structure for the region used to activate the path loss reference RS ID can be different.

[0628] refer to Figure 13A and Figure 13B Each MAC CE includes the serving cell ID to which the MAC CE command will be applied (1300 or 1350), the BWP ID (1305 or 1355), and the PUCCH resource ID (1310 or 1360) indicating the higher-layer parameter PUCCH-ResourceID. The area used to determine the transmit power of the TRP for the first PUCCH retransmission is configured with path loss reference RS ID (1321 or 1372), P0 PUCCH ID (1322 or 1371), and ClosedLoopIndex (1320 or 1370).

[0629] The region used to determine the transmit power of another TRP is configured as Path Loss Reference RS ID 1331 or 1382, P0 PUCCH ID 1332 or 1381, and ClosedLoopIndex 1330 or 1380. The Path Loss Reference RS ID region represents the PUCCH-PathlossRefereceRS-Id of the PUCCH-PathlossRefereceRS activated in the higher-level PUCCH-PowerControl's pathlossReferenceRS, the P0 PUCCH ID represents the P0-PUCCH-Id of the P0-PUCCH activated in the p0-Set, and the ClosedLoopIndex represents the closed loop of the corresponding TRP. If the Path Loss Reference RS ID is set to 'a', then the PUCCH-PathlossReferenceRS with PUCCH-PathlossReferenceRS-Id 'a' is activated, and if the P0 PUCCH ID is set to 'b', then the P0-PUCCH with P0-PUCCH-Id 'b+1' is activated. If ClosedLoopIndex is 0, the transmission power of the corresponding TRP is adjusted according to closed loop 0; and if ClosedLoopIndex is 1, the transmission power of the corresponding TRP is adjusted according to closed loop 1.

[0630] As described above, when a UE transmits a PUCCH through a PUCCH resource activated by MAC CE using transmit power control parameters, the UE can apply the activated transmit power control parameters and transmit the PUCCH through each TRP. If the UE does not receive a MAC CE command for the PUCCH resource to be transmitted, the UE transmits the PUCCH according to the transmit power control method of the NR version 15 / 16 standard. If only one PUCCH resource is used for MAC CE activation of transmit power control parameters, the UE only applies the activated parameters to transmit power control and transmits the PUCCH.

[0631] Figure 14A A flowchart illustrating a base station method according to an embodiment for determining the offset of UL signal transmission based on UE capabilities reported by the UE and providing the offset to the UE.

[0632] As in the above embodiments, the base station can determine the offset based on the UE capabilities reported by the UE for at least one of UL beam changes, transmit power changes, or frequency changes, and can explicitly configure or implicitly indicate the determined offset to the UE. The UE can report its capabilities to the base station for at least one of UL beam changes, transmit power changes, or frequency changes, and can transmit UL signals through multiple TRPs according to the offset configured or indicated by the base station.

[0633] Specifically, refer to Figure 14A In step 1405, the base station receives from the UE UE configurable capabilities for changing at least one of the UL beam, transmit power, or frequency. As in the above scheme, the UE may report all or only some of the UE configurable capabilities for each change to the base station.

[0634] In step 1410, the base station can identify the UE capabilities reported by the UE.

[0635] In step 1420, the base station determines the offset of the UL signal transmission in the time domain based on the reported UE capabilities. The base station may use one or a combination of options 1 to 7 of the embodiments described above to determine the offset.

[0636] In step 1430, the base station sends information to the UE about the offset determined for the UE. This offset information can be explicitly sent to the UE or can be implicitly indicated, as is generally the case in the above scheme.

[0637] Figure 14B A flowchart illustrating a UE method for transmitting UL signals to one or more TRPs based on an offset configured by a base station, according to an embodiment.

[0638] refer to Figure 14BIn step 1440, the UE sends UE capability information to the base station for changing at least one of the UL beam, transmit power, or frequency.

[0639] In step 1450, the UE receives information about the offset in the time domain based on the UE capability information from the base station (or the UE can implicitly know the information about the offset through the above scheme).

[0640] In step 1460, the UE compares the offset with the UE capability.

[0641] If, in step 1460, the offset in the time domain received from the base station (or the implicitly identified offset) is greater than or equal to the time for change according to the UE's capabilities, then in step 1461, the UE changes at least one of the UL beam, transmit power, or frequency, and transmits the UL signal through multiple TRPs. Hereinafter, multiple TRPs can be understood to include the base station and at least one other base station (or IAB node) cooperating with that base station. The UL signal received from another base station can be transmitted to the base station.

[0642] If, in step 1460, the offset in the time domain received from the base station (or the offset of the implicit identifier) ​​is less than the time used for change according to the UE's capabilities, then in step 1462, the UE can send a UL signal according to the default UL transmission operation predefined / determined by the base station and the UE.

[0643] Figure 14C A flowchart illustrating a UE method for transmitting UL signals to one or more TRPs based on an offset configured by a base station, according to an embodiment.

[0644] refer to Figure 14C Steps 1484 to 1487 specifically illustrate Figure 14B The default UL transmission in step 1462.

[0645] also, Figure 14C Steps 1480 to 1483 and Figure 14B Steps 1440 to 1461 are the same, and detailed descriptions of these steps are omitted.

[0646] In step 1484, the UE changes at least one of the UL beam, transmit power, or frequency and transmits a UL signal according to a predetermined UL transmission operation (e.g., a default UL transmission operation). Regarding PUCCH transmission, at least one of the three conditions illustrated in steps 1485, 1486, and 1487 can be applied. For example, as in step 1485, the UL beam can be the same for all PUCCH transmission opportunities, or as in step 1486, some of the multiple PUCCHs can be transmitted while others can be discarded. Alternatively, as in step 1487, the PUCCH transmit power can be conditionally changed during a PUCCH transmission opportunity. However, the default UL transmission operation of this disclosure is not limited to the three conditions described above.

[0647] For example, the default UL transmission operation may include at least one of the following methods: a method for transmitting a UL signal using the same UL beam, transmission power, and frequency as the previous UL signal; a method for transmitting a UL signal using a default UL beam, transmission power, and frequency; a method for conditionally changing the UL beam, transmission power, and frequency before transmitting; a method for applying some modifiable configuration before transmitting; or a method for discarding some symbols or repeating transmission timings before transmitting, as described above in conjunction with embodiments 1-2.

[0648] Figures 14A to 14C The UE capability information can also include information about the panel.

[0649] Figure 15A This is a flowchart illustrating a UE method according to an embodiment of determining the transmit power of each TRP and transmitting a PUCCH signal to one or more TRPs in FR1 using a default transmit power control method.

[0650] refer to Figure 15A In step 1505, the UE reports to the base station the UE capability indicating whether transmit power control can be performed for each TRP, as UE capability information for individual power control for each TRP in FR1.

[0651] In step 1510, the UE receives higher-layer parameters (configuration information) related to PUCCH transmission from the base station.

[0652] In step 1515, the UE identifies the conditions for transmitting a PUCCH signal through multiple TRPs. Here, the conditions for transmitting PUCCH through multiple TRPs can be the conditions for transmitting PUCCH through multiple TRPs described above in conjunction with embodiment 2-1.

[0653] As a result of the identification in step 1515, if the UE transmits PUCCH through multiple TRPs in FR1, then in step 1520, the UE determines the transmission power of each TRP using a first PUCCH power control scheme (e.g., an enhanced default PUCCH transmission power control method), and applies the determined transmission power to transmit PUCCH through multiple TRPs. The enhanced default PUCCH transmission power control method can be used to support PUCCH transmission through multiple TRPs, as described above in conjunction with embodiment 2-1.

[0654] As a result of the identification in step 1515, if the UE transmits PUCCH through a single TRP in FR1, then in step 1530, the UE determines the transmit power according to a second PUCCH power control scheme (e.g., the default transmit power control method in NR version 15 / 16 standards) and applies the determined transmit power to transmit the PUCCH through the single TRP. The single TRP can be a base station receiving UE capability information or another base station cooperating with that base station.

[0655] Figure 15B A flowchart illustrating a base station method for receiving a PUCCH in FR1 via one or more TRPs, according to an embodiment, is provided.

[0656] refer to Figure 15B In step 1540, the base station receives UE capability information for power control separately for each TRP from FR1.

[0657] In step 1545, the base station that receives the UE capability information sends PUCCH-related configuration information to the UE.

[0658] In step 1550, the base station identifies whether to receive PUCCH (condition) through multiple TRPs based on PUCCH-related configuration information.

[0659] If, as a result of the identification in step 1550, a PUCCH is received through multiple TRPs, then in step 1551, the base station receives the PUCCH signal for which a first PUCCH power control scheme (e.g., an enhanced default PUCCH transmit power control method used in LTE systems) is applied through multiple TRPs.

[0660] If, as a result of the identification in step 1550, a PUCCH is received via a single TRP, then in step 1552, the base station receives the PUCCH signal for which a second PUCCH power control scheme (e.g., the default transmit power control method used in NR version 15 / 16 standards) is applied via a single TRP.

[0661] Figure 16A and Figure 16B A flowchart illustrating a UE method for transmitting PUCCH signals using one or more TRPs in FR1 using PUCCH-SpatialRelationInfo according to an embodiment is provided.

[0662] refer to Figure 16A In step 1605, the UE reports to the base station the UE capability indicating whether it can perform transmit power control for each TRP, as UE capability information for separate power control for each TRP in FR1.

[0663] In step 1610, the UE is configured by the base station with a higher-layer parameter PUCCH-SpatialRelationInfo (PUCCH spatial related information) to support transmit power control for each TRP in FR1. The UE can receive at least one PUCCH spatial related information.

[0664] In step 1615, the UE identifies whether the number of PUCCH-SpatialRelationInfo configured for the UE is greater than a predetermined number (e.g., 2 or more).

[0665] If the number of configured PUCCH-SpatialRelationInfos is greater than a predetermined number in step 1615, then in step 1620, the UE receives control information (e.g., a MAC CE command) from the base station indicating the activation status of the configured PUCCH-SpatialRelationInfos.

[0666] In step 1621, the UE identifies the number of PUCCH-SpatialRelationInfos activated by control information (e.g., MAC CE).

[0667] If multiple (e.g., two or more) PUCCH-SpatialRelationInfos are activated in step 1621, then in step 1622, the UE determines the transmit power of each TRP based on the multiple PUCCH-SpatialRelationInfos, applies the transmit power, and transmits PUCCHs through the multiple TRPs.

[0668] If a PUCCH-SpatialRelationInfo is activated in step 1621, then in step 1623, the UE determines a transmit power based on an activated PUCCH-SpatialRelationInfo, applies the transmit power, and transmits the PUCCH.

[0669] refer to Figure 16B If the number of PUCCH-SpatialRelationInfos configured for the UE in step 1615 is equal to a predetermined number (e.g., two or more), then in step 1630, the UE identifies the conditions for sending PUCCHs via multiple TRPs as described above in conjunction with embodiment 2-1. For example, the case of a predetermined number of two or more corresponds to the case of a number of TRPs of two or more.

[0670] If, as a result of the identification in step 1630, the UE transmits PUCCH through multiple TRPs, then in step 1631, the UE determines the transmit power of each TRP based on a predetermined number of PUCCH-SpatialRelationInfo without the need for control information (e.g., MAC CE command) for activation, applies the transmit power, and transmits PUCCH through multiple TRPs.

[0671] If, as a result of the identification in step 1630, the UE transmits PUCCH via a single TRP in FR1, then in step 1632, the UE determines the transmit power according to the default transmit power control method in the NR version 15 / 16 standard, and applies the determined transmit power to transmit PUCCH via a single TRP.

[0672] On the other hand, despite Figure 16B Not shown, but if the number of PUCCH-SpatialRelationInfos configured for the UE is less than a predetermined number (e.g., two or more), the UE performs a general PUCCH transmission operation. According to 3GPP Release 15 / 16 procedures, a general PUCCH transmission operation can be a single TRP PUCCH transmission operation.

[0673] Figure 16C and Figure 16D A flowchart illustrating a base station method for receiving PUCCH via one or more TRPs in FR1 using PUCCH-SpatialRelationInfo according to an embodiment is provided.

[0674] refer to Figure 16C In step 1645, the base station receives UE capability information for power control from each TRP in FR1.

[0675] In step 1650, the base station sends at least one PUCCH-SpatialRelationInfo (PUCCH spatial related information) from FR1 to the UE.

[0676] In step 1655, the base station identifies whether the number of PUCCH space-related information configured for the UE is greater than a predetermined number (e.g., two or more).

[0677] As a result of the identification, if the number of PUCCH space-related information configured to the UE in step 1655 is greater than a predetermined number, then in step 1660, the base station sends control information (e.g., MAC CE) to the UE to activate the PUCCH space-related information.

[0678] In step 1661, the base station identifies whether the number of PUCCH space-related information activated is greater than one.

[0679] If the number of activated PUCCH space-related information is greater than one in step 1661, then in step 1662, the base station performs PUCCH reception through multiple TRPs based on multiple activated PUCCH space-related information.

[0680] However, if the number of activated PUCCH space-related information is one in step 1661, then in step 1663, the base station performs PUCCH reception through a single TRP based on the single activated PUCCH space-related information.

[0681] refer to Figure 16D If the number of PUCCH space-related information configured to the UE in step 1655 is equal to a predetermined number (e.g., two or more), then in step 1670, the base station identifies the conditions for receiving PUCCH through multiple TRPs as described above in conjunction with embodiment 2-1.

[0682] On the other hand, despite Figure 16D Not shown, but if the number of PUCCH space-related information configured for the UE is less than a predetermined number (e.g., two or more), the base station performs a general PUCCH receive operation. According to 3GPP Release 15 / 16 procedures, a general PUCCH receive operation can be a single TRP PUCCH receive operation.

[0683] In step 1670, if PUCCH reception is performed through multiple TRPs, in step 1671, the base station performs PUCCH reception through multiple TRPs without control information for activating PUCCH space-related information.

[0684] In step 1670, if PUCCH reception is performed via a single TRP, in step 1672, the base station performs PUCCH reception via a single TRP without control information for activating PUCCH space-related information.

[0685] Figure 17Aand Figure 17B This is a flowchart illustrating a UE method for sending a PUCCH signal to one or more TRPs using configuration information for controlling separate power control in FR1 according to an embodiment. Specifically, Figure 17A and Figure 17B A method is shown for transmitting PUCCH over multiple TRPs in FR1 using new higher-level parameters for controlling the transmit power for each TRP and control information (MAC CE command) for activating the new higher-level parameters.

[0686] refer to Figure 17A In step 1705, the UE reports to the base station the UE capability indicating whether it can perform transmit power control for each TRP, as the UE capability information for power control separately for each TRP in FR1.

[0687] In step 1710, the UE is configured by the base station with new higher-layer parameters (configuration information for power control separate for each TRP) to support transmit power control for each TRP in FR1. The UE can receive at least one configuration information. The new higher-layer parameter can be defined as 'PUCCH-PowerControlInfo', as described above in conjunction with embodiment 2-2-2.

[0688] In step 1715, the UE identifies whether the number of new higher-level parameters PUCCH-PowerControlInfo configured is greater than a predetermined number (e.g., two or more).

[0689] If the number of configured PUCCH-PowerControlInfos is greater than a predetermined number in step 1715, then in step 1720, the UE receives control information (e.g., a MAC CE command) from the base station indicating the activation status of the configured PUCCH-PowerControlInfos.

[0690] In step 1721, the UE identifies whether the number of PUCCH-PowerControlInfo activated by the MAC CE is greater than one.

[0691] If multiple (e.g., two or more) PUCCH-PowerControlInfos are activated in step 1721, then in step 1722, the UE determines the transmit power for each TRP based on the multiple PUCCH-PowerControlInfos, applies the transmit power, and transmits the PUCCH through the multiple TRPs. However, if only one PUCCH-PowerControlInfo is activated in step 1721, then in step 1723, the UE determines a transmit power based on the single activated PUCCH-PowerControlInfo, applies the transmit power, and transmits the PUCCH.

[0692] refer to Figure 17B If the number of PUCCH-PowerControlInfo values ​​configured to the UE and recognized by the UE in step 1715 is equal to a predetermined number (e.g., two or more), then in step 1730, the UE recognizes the conditions described above in conjunction with embodiment 2-1 for sending PUCCH via multiple TRPs. For example, the case of a predetermined number of two or more corresponds to the case of a number of TRPs of two or more.

[0693] As a result of the identification, if the UE transmits PUCCH through multiple TRPs in step 1730, then in step 1731, the UE determines the transmit power of each TRP without control information (e.g., MAC CE command) based on a predetermined number of PUCCH-PowerControlInfo, applies the transmit power, and transmits PUCCH through multiple TRPs.

[0694] If, as a result of the identification in step 1730, the UE transmits PUCCH via a single TRP in FR1, then in step 1732, the UE determines the transmit power according to the default transmit power control method in the NR version 15 / 16 standard, and applies the determined transmit power to transmit PUCCH via a single TRP.

[0695] On the other hand, despite Figure 17B Not shown, but if the number of PUCCH-PowerControlInfos configured for the UE is less than a predetermined number (e.g., two or more), the UE performs a general PUCCH transmission operation. According to 3GPP Release 15 / 16 procedures, a general PUCCH transmission operation can be a single TRP PUCCH transmission operation.

[0696] Figure 17C and Figure 17DA flowchart illustrating a base station method for receiving PUCCH signals via one or more TRPs in FR1 using configuration information for controlling separate power control, according to an embodiment.

[0697] refer to Figure 17C In step 1745, the base station receives UE capability information from the UE, which is power control information for each TRP in FR1.

[0698] In step 1750, the base station sends at least one PUCCH-PowerControlInfo (configuration information) to the UE for separate power control for each TRP in FR1.

[0699] In step 1755, the base station identifies whether the number of configuration information configured for individual power control assigned to the UE is greater than a predetermined number (e.g., two or more).

[0700] As a result of the identification, if in step 1755 the number of configuration information configured for individual power control to the UE is greater than a predetermined number, then in step 1760, the base station sends control information (e.g., MAC CE) to the UE to activate the configuration information.

[0701] In step 1761, the base station identifies whether the number of activated configuration information is greater than one.

[0702] If in step 1761 the number of activated configuration information is greater than one (e.g., two or more), then in step 1762, the base station performs PUCCH reception through multiple TRPs based on the multiple activated configuration information.

[0703] If the number of activated configuration information is one in step 1761, then in step 1763, the base station performs PUCCH reception via a single TRP based on the single activated configuration information.

[0704] refer to Figure 17D If the number of PUCCH-PowerControlInfo (configuration information) configured for the UE in step 1755 is equal to a predetermined number (e.g., two or more), then in step 1770, the base station identifies the conditions for receiving PUCCH through multiple TRPs as described above in conjunction with embodiment 2-1. For example, the case of a predetermined number of two or more corresponds to the case of a number of TRPs of two or more.

[0705] In step 1770, if PUCCH reception is performed through multiple TRPs, in step 1771, the base station performs PUCCH reception through multiple TRPs without control information for activating configuration information. However, in step 1770, if PUCCH reception is performed through a single TRP, in step 1772, the base station performs PUCCH reception through a single TRP without control information for activating configuration information.

[0706] On the other hand, despite Figure 17D Not shown, but if the number of configuration information configured for the UE is less than a predetermined number (e.g., two or more), the base station performs a general PUCCH receive operation. According to 3GPP Release 15 / 16 procedures, a general PUCCH receive operation can be a single TRP PUCCH receive operation.

[0707] Figure 18A This is a flowchart illustrating a UE method for sending a PUCCH signal to one or more TRPs using configuration information for controlling separate power control in FR1 according to an embodiment. Specifically, Figure 18A A method for configuring new higher-level parameters is shown, which control the transmit power of each TRP in FR1 and transmit PUCCH through multiple TRPs without executing signaling control information (MAC CE command) for activation.

[0708] refer to Figure 18A In step 1805, the UE reports to the base station the UE capability indicating whether it can perform transmit power control for each TRP, as the UE capability information for power control separately for each TRP in FR1.

[0709] In step 1810, the UE receives new higher-layer parameters (configuration information for power control separate for each TRP) from the base station to support transmit power control for each TRP in FR1. The new higher-layer parameter can be defined, for example, 'PUCCH-PowerControlInfo-r17', as described above in conjunction with embodiments 2-2-3 detailed above. The new higher-layer parameter PUCCH-PowerControlInfo-r17 may include two or more of each parameter used for transmit power control for each TRP (refer to Table 34), and only one new higher-layer parameter PUCCH-PowerControlInfo-r17 is configured to the UE.

[0710] In step 1815, the UE identifies the conditions described above in conjunction with embodiment 2-1 for sending PUCCH via multiple TRPs.

[0711] If, as a result of the identification in step 1815, the UE transmits PUCCH through multiple TRPs, then in step 1820, the UE determines the transmission power based on the parameters for transmission power control for each TRP in the new higher-layer parameter PUCCH-PowerControlInfo-r17, applies the transmission power, and transmits PUCCH through multiple TRPs.

[0712] If, as a result of the identification in step 1815, the UE transmits PUCCH through a single TRP, then in step 1830, the UE determines the transmit power according to a predetermined PUCCH power control scheme (e.g., the default transmit power control method in the NR version 15 / 16 standard) and applies the determined transmit power to transmit PUCCH through a single TRP.

[0713] Figure 18B A flowchart illustrating a base station method for receiving PUCCH signals via one or more TRPs in FR1 using configuration information for controlling separate power control, according to an embodiment.

[0714] refer to Figure 18B In step 1845, the base station receives UE capability information for power control separately for each TRP from FR1.

[0715] In step 1850, the base station sends configuration information for power control separate for each TRP in FR1 (e.g., PUCCH-PowerControlInfo-r17) to the UE. PUCCH-PowerControlInfo-r17 may include two or more of each parameter for transmit power control for each TRP (refer to Table 34), and only one parameter is configured to the UE.

[0716] In step 1855, the base station identifies the conditions for receiving PUCCH through multiple TRPs as described above in conjunction with embodiment 2-1. As a result of the identification in step 1855, if the UE receives PUCCH through multiple TRPs, then in step 1860, the base station performs PUCCH reception through multiple TRPs based on configuration information. However, if in step 1855 it is identified that the base station receives PUCCH through a single TRP, then in step 1870, the base station receives the PUCCH signal through a single TRP with a predetermined PUCCH power control scheme (e.g., the default transmit power control method used in NR version 15 / 16 standards) applied.

[0717] Figure 19AThis is a flowchart illustrating a UE method for transmitting PUCCH signals to one or more TRPs using PUCCH power configuration information and control information in FR1 according to an embodiment. Specifically, Figure 19A It shows the use of Figure 13A or Figure 13B The new MAC CE transmits PUCCH via multiple TRPs, and this new MAC CE indicates the activation state of the parameters used for PUCCH transmission power control in FR1.

[0718] refer to Figure 19A In step 1905, the UE reports to the base station the UE capability indicating whether it can perform transmit power control for each TRP, as the UE capability information for power control separately for each TRP in FR1.

[0719] In step 1910, the UE receives higher-layer configuration information (e.g., PUCCH-PowerControl) for PUCCH power control (hereinafter referred to as PUCCH power configuration information) from the base station. The PUCCH power configuration information may include multiple parameter information as described in Table 29 above.

[0720] In step 1915, the UE receives control information (MAC CE command) from the base station to indicate the activation state of parameter information (e.g., ClosedLoopIndex, PathlossReferenceRS-Id, and / or P0-PUCCH-Id) for PUCCH transmit power control. In this case, the control information (e.g., MAC CE) can be configured as follows: Figure 13A or Figure 13B The example provides a format configuration to indicate parameter information used to determine the PUCCH transmit power for each TRP.

[0721] In step 1920, the UE identifies the number of active parameter information for each parameter information (e.g., ClosedLoopIndex, PathlossReferenceRS-Id, and P0-PUCCH-Id). Figure 13A and Figure 13BThe diagram illustrates two activation states for each parameter information (e.g., ClosedLoopIndex, PathlossReferenceRS-Id, and P0-PUCCH-Id). For example, the activated parameter information, indicated by reference numerals 1320, 1321, and 1322, can be applied to PUCCH transmissions via TRP#1, and the activated parameter information, indicated by reference numerals 1330, 1331, and 1332, can be applied to PUCCH transmissions via TRP#2. Thus, the UE can identify the number of activated parameter information for each parameter information (corresponding to the number of TRPs through which the PUCCH is transmitted) based on control information. For convenience, Figure 13A or Figure 13B The example illustrates the case where two parameters are activated for each parameter, but the number of activated parameters can be two or more.

[0722] If each parameter information is activated by two or more MAC CEs in step 1920, then in step 1930, the UE determines the PUCCH transmission power for each TRP based on the two or more activated parameter information, applies the determined PUCCH transmission power, and transmits the PUCCH through multiple TRPs corresponding to the number of parameter information activated for each parameter information. However, if only one parameter information is activated by a MAC CE in step 1920, then in step 1940, the UE determines a PUCCH transmission power based on one activated parameter information and applies that PUCCH transmission power to transmit the PUCCH through a single TRP.

[0723] Figure 19B A flowchart illustrating a base station method for receiving PUCCH signals via one or more TRPs using PUCCH power configuration information and control information in FR1 according to an embodiment.

[0724] refer to Figure 19B In step 1945, the base station receives UE capability information for power control separately for each TRP from FR1.

[0725] In step 1950, the base station sends PUCCH power configuration information (e.g., PUCCH-PowerControl) to the UE. The PUCCH power configuration information may include multiple parameter information as described in Table 29 above.

[0726] In step 1955, the base station sends control information (e.g., MAC CE command) to the UE to indicate the activation status of parameter information (e.g., ClosedLoopIndex, PathlossReferenceRS-Id, and / or P0-PUCCH-Id) for PUCCH transmit power control.

[0727] In step 1960, the base station identifies the number of parameter information activated for each parameter information (e.g., ClosedLoopIndex, PathlossReferenceRS-Id, P0-PUCCH-Id), and if in step 1960 the number of parameter information activated for each parameter information is two or more, such as... Figure 13A and 13B As shown, in step 1970, the base station performs PUCCH reception through multiple TRPs corresponding to the number of parameter information activated for each parameter information. However, if in step 1960 only one parameter information is activated through MAC CE, then in step 1980, the base station performs PUCCH reception through a single TRP based on the activated parameter information.

[0728] Figure 20 A UE according to an embodiment is shown.

[0729] refer to Figure 20 The UE 2000 includes a receiver 2000, a transmitter 2010, and a processor 2005. The receiver 2000 and transmitter 2010 can be collectively referred to as a transceiver. The UE may include memory. According to each or at least a combination of the above embodiments, the processor 2005 can control the operation of transmitting UL signals.

[0730] However, the components of the UE are not limited to these. For example, the UE may include more or fewer components than those described above. Transceivers 2000 and 2010 and processor 2005 may be implemented as a single chip.

[0731] Transceivers 2000 and 2010 can transmit signals to / receive signals from a base station. These signals may include control information and data. For this purpose, transceivers 2000 and 2010 may include a radio frequency (RF) transmitter for up-converting and amplifying the transmitted signals and an RF receiver for low-noise amplification of the received signals and down-converting the frequency of the received signals. However, this is merely an example of transceivers 2000 and 2010, and the components of transceivers 2000 and 2010 are not limited to RF transmitters and RF receivers.

[0732] Transceivers 2000 and 2010 can receive signals via a radio channel, output signals to processor 2005, and transmit signals output from processor 2005 via a radio channel.

[0733] Processor 2005 may store programs and data for operation of the UE. Processor 2005 may store control information or data included in signals received by the UE. Processor 2005 may include memory configured with storage media, such as read-only memory (ROM), random access memory (RAM), hard disk, optical disc ROM (CD-ROM), and digital versatile optical disc (DVD), or a combination of storage media.

[0734] The processor 2005 can control a series of processes of the UE so as to be able to operate according to at least one or a combination of the above embodiments.

[0735] Figure 21 A base station according to an embodiment is shown.

[0736] refer to Figure 21 The base station 2100 includes a receiver 2100, a transmitter 2110, and a processor 2105. The receiver 2100 and transmitter 2110 can be collectively referred to as a transceiver. The UE may include a memory. According to each or at least a combination of the above embodiments, the processor 2105 can control the operation of transmitting UL signals.

[0737] However, the components of a base station are not limited to these. For example, a base station may include more or fewer components than those described above. Transceivers 2100 and 2110 and processor 2105 may be implemented as a single chip.

[0738] Transceivers 2100 and 2110 can transmit signals to / receive signals from the UE. These signals may include control information and data. For this purpose, transceivers 2100 and 2110 may include an RF transmitter for up-converting and amplifying the transmitted signals and an RF receiver for low-noise amplification of the received signals and down-converting the frequency of the received signals. However, this is merely an example of transceivers 2100 and 2110, and the components of transceivers 2100 and 2110 are not limited to RF transmitters and RF receivers.

[0739] Transceivers 2100 and 2110 can receive signals via a radio channel, output signals to processor 2105, and transmit signals output from processor 2105 via a radio channel.

[0740] Processor 2105 may store programs and data for the operation of the base station. Processor 2105 may store control information or data included in signals acquired by the base station. Processor 2105 may include a memory configured with a storage medium, such as ROM, RAM, hard disk, CD-ROM, DVD, or a combination of storage media.

[0741] The processor 2105 can control a series of processes of the base station so as to be able to operate according to at least one or a combination of the above embodiments.

[0742] The methods described in the embodiments according to the specification or claims of this disclosure can be implemented using hardware, software, or a combination of hardware and software.

[0743] When implemented using software, a computer-readable storage medium may be provided to store one or more programs (software modules). The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions that enable the electronic device to perform methods according to embodiments described in the specification or claims of this disclosure.

[0744] Programs (software modules or software) can be stored in RAM, non-volatile memory including flash memory, ROM, electrically erasable programmable read-only memory (EEPROM), disk storage devices, CD-ROMs, DVDs, or other types of optical storage devices or magnetic tapes. Programs can also be stored in memory consisting of all or a combination of programs. Since each program constitutes memory, multiple memories can be included.

[0745] The program can be stored in an attachable storage device accessible via a communication network, such as the Internet, intranet, local area network (LAN), wide area network (WLAN), or storage area network (SAN), or a combination thereof. The storage device can be connected to the device executing the embodiment via an external port. A separate storage device on the communication network can be connected to the device executing the embodiment.

[0746] The embodiments described herein are provided merely to better understand this disclosure, and this disclosure should not be limited thereto. In other words, it will be apparent to those skilled in the art that various modifications can be made thereto without departing from the scope of this disclosure. Furthermore, these embodiments can be practiced in combination. For example, some of the first and second embodiments can be partially combined and can be operated by a base station and a UE.

[0747] In the specific embodiments described above, depending on the proposed specific embodiments, the components included in this disclosure are represented in either a singular or plural form. However, the singular or plural forms are chosen to suit the context suggested for ease of description, and this disclosure is not limited to singular or plural components. As used herein, unless the context explicitly indicates otherwise, the singular forms “a,” “an,” and “the” are also intended to include the plural forms.

[0748] Although certain embodiments have been described above, various changes can be made thereto without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the above embodiments, but should be defined by the appended claims and any equivalents thereof.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Send UE capability information to the base station, the UE capability information including information indicating that the UE supports power control of the Physical Uplink Control Channel (PUCCH) associated with the Multiple Transmitter Receiver Point (TRP); Receive configuration information from the base station, the configuration information including information about a set of power control parameters for the TRP configuration used for PUCCH transmission; Receive activation information from the base station for one or more sets of the power control parameter set; as well as Based on the configuration information and the activation information, the PUCCH transmission is repeated for one or more of the TRPs. The UE is configured for repetition of the PUCCH transmission based on a cyclic mapping mode, and performs PUCCH power control by alternating between the power control parameter set for each repetition of the PUCCH transmission.

2. The method according to claim 1, wherein, The activation information is received from the base station via the Media Access Control (MAC) control element (CE).

3. The method according to claim 1, wherein, The set of power control parameters is configured according to one or more TRPs for one or more PUCCH resources used in the PUCCH transmission.

4. The method according to claim 1, wherein, Based on the activation information of one set of the power control parameters, the PUCCH transmission is performed for one of the TRPs, and Specifically, based on the activation information of two sets in the set of power control parameters, the PUCCH transmission is performed for two TRPs in the TRP.

5. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; and The processor is configured as follows: The transceiver transmits UE capability information to the base station, the UE capability information including information indicating that the UE supports power control of the Physical Uplink Control Channel (PUCCH) associated with the Multiple Transmitter Receiver Point (TRP). The transceiver receives configuration information from the base station, the configuration information including information about a set of power control parameters configured for the TRP for PUCCH transmission. The transceiver receives activation information for one or more sets of the power control parameter set from the base station. Based on the configuration information and the activation information, the PUCCH transmission is repeated for one or more of the TRPs. The processor is further configured to: be configured for repetition of the PUCCH transmission based on a cyclic mapping mode, wherein for each repetition of the PUCCH transmission, the PUCCH power control is performed by alternating between the power control parameter set.

6. The UE according to claim 5, wherein, The activation information is received from the base station via the Media Access Control (MAC) control element (CE).

7. The UE according to claim 5, wherein, The set of power control parameters is configured according to one or more TRPs for one or more PUCCH resources used in the PUCCH transmission.

8. The UE according to claim 5, wherein, Based on the activation information of one set of the power control parameters, the PUCCH transmission is performed for one of the TRPs, and Specifically, based on the activation information of two sets in the set of power control parameters, the PUCCH transmission is performed for two TRPs in the TRP.

9. A method performed by a base station in a wireless communication system, the method comprising: Receive UE capability information from the user equipment (UE), the UE capability information including information indicating that the UE supports power control of the physical uplink control channel (PUCCH) associated with the multiple transmit receive point (TRP); Send configuration information to the UE, the configuration information including information about the set of power control parameters configured for TRP for PUCCH reception; Send activation information for one or more sets of the power control parameter set to the UE; as well as Based on the configuration information and the activation information, at least one PUCCH repeat is received from the UE via one or more TRPs. The at least one PUCCH repetition is received based on the PUCCH power control, wherein the PUCCH power control is configured for the received PUCCH repetition based on a cyclic mapping mode, alternating between the power control parameter set for each received PUCCH repetition.

10. The method according to claim 9, wherein, The activation information is sent to the UE using the Media Access Control (MAC) control element (CE).

11. The method according to claim 9, wherein, The power control parameter set is configured according to one or more TRPs for one or more PUCCH resources used in the at least one PUCCH repetition.

12. The method according to claim 9, wherein, Based on the activation information of one set of the power control parameters, the PUCCH repetition is received through one of the TRPs, and Specifically, based on the activation information of two sets in the set of power control parameters, the PUCCH repetition is received through two TRPs in the TRP.

13. A base station in a wireless communication system, the base station comprising: transceiver; and The processor is configured as follows: The transceiver receives UE capability information from the user equipment (UE), the UE capability information including information indicating that the UE supports power control of the physical uplink control channel (PUCCH) associated with the multiple transmit / receive point (TRP); The transceiver sends configuration information to the UE, the configuration information including information about a set of power control parameters configured for TRP for PUCCH reception; The transceiver sends activation information for one or more sets of the power control parameter set to the UE. as well as Based on the configuration information and the activation information, at least one PUCCH repeat is received from the UE via the transceiver through one or more TRPs. The at least one PUCCH repetition is received based on the PUCCH power control, wherein the PUCCH power control is configured for the received PUCCH repetition based on a cyclic mapping mode, alternating between the power control parameter set for each received PUCCH repetition.

14. The base station according to claim 13, wherein, The processor is configured to send the activation information to the UE via the transceiver using a Media Access Control (MAC) control element (CE).

15. The base station according to claim 13, wherein, The power control parameter set is configured according to one or more TRPs for one or more PUCCH resources used in the at least one PUCCH repetition.

16. The base station according to claim 13, wherein, Based on the activation information of one set of the power control parameters, the PUCCH repetition is received through one of the TRPs, and Specifically, based on the activation information of two sets in the set of power control parameters, the PUCCH repetition is received through two TRPs in the TRP.

Images