Method and apparatus for reporting power headroom of uplink-only base stations in wireless communication systems

By using power margin reports for DCI scheduling and path loss calculation in mobile communication systems, the problem of low resource scheduling efficiency in cooperative communication between terminals and base stations is solved, achieving more efficient resource utilization and service capabilities.

CN123125976APending Publication Date: 2026-11-17SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480090742.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-08-13
Filing Date
2024-11-22
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In mobile communication systems, existing technologies struggle to effectively support collaborative communication between terminals and base stations, especially in scenarios involving only uplink transmit/receive points (TRPs), where power headroom report (PHR) calculations and resource scheduling suffer from inefficiencies.

Method used

By receiving and transmitting downlink control information (DCI) to schedule the physical uplink shared channel (PUSCH) and calculating the power headroom report (PHR) based on the path loss and path loss offset of the reference signal, the efficient scheduling and reporting of the first and second PUSCHs can be achieved, ensuring accurate resource allocation within the same time slot.

Benefits of technology

It improves the efficiency of collaborative communication between terminals and base stations in mobile communication systems, ensures the rational use of PUSCH resources scheduled at different times, and enhances the system's service capabilities and resource utilization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125976A_ABST
    Figure CN123125976A_ABST
Patent Text Reader

Abstract

This disclosure relates to 5G or 6G communication systems for supporting higher data transmission rates. More specifically, this disclosure relates to a method performed by a terminal in a wireless communication system, the method comprising the steps of: receiving downlink control information (DCI), the DCI scheduling resources for transmitting a first physical uplink shared channel (PUSCH) and a second PUSCH, the first PUSCH being associated with a first transmit-receive point (TRP) for uplink transmission and downlink reception of the terminal, and the second PUSCH being associated with a second TRP for uplink transmission only of the terminal; and transmitting a power headroom report (PHR), the PHR including a first PHR associated with the first PUSCH and / or a second PHR associated with the second PUSCH, wherein the first PHR is calculated based on downlink path loss calculated using a reference signal, and the second PHR is calculated based on downlink path loss and path loss offset, both the first PHR and the second PHR are configured to be transmitted, both the first PUSCH and the second PUSCH are transmitted in a time slot n of the transmission PHR, and when the first PUSCH is scheduled at an earlier time point than the second PUSCH, a PHR including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH can be transmitted.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the operation of terminals and base stations in wireless communication systems. Specifically, this disclosure relates to methods and apparatus for supporting uplink-only transmit / receive points (UL-only TRPs) in network cooperative communication. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in sub-6GHz bands (such as 3.5GHz) but also in "above 6GHz" bands (including 28GHz and 39GHz), known as mmWave. Furthermore, 6G mobile communication technology (called Super 5G systems) is being considered in terahertz (THz) bands (e.g., the 95GHz to 3THz band) to achieve transmission rates fifty times faster and ultra-low latency one-tenth that of 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology development, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization has been carried out on the following aspects: beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission distance in mmWave; parameter set support for dynamic operation (e.g., operating multiple subcarrier spacings) for efficient utilization of mmWave resources and time slot formats; initial access technologies for supporting multi-beam transmission and broadband; definition and operation of BWP (bandwidth portion); new channel coding methods (such as LDPC (low-density parity-check) codes for large data transmissions and polar codes for high-reliability transmission of control information); L2 preprocessing; and network slicing for providing dedicated networks for specific services.

[0004] Currently, regarding the services that 5G mobile communication technology will support, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology. Physical layer standardization has been implemented for the following technologies: V2X (Vehicle-to-Everything), used to assist autonomous vehicles in making driving decisions and enhance user convenience based on information sent by vehicles regarding their location and status; NR-U (New Radio Unlicensed Band), designed to comply with various regulatory requirements for unlicensed bands; NR UE power saving; NTN (Non-Terrestrial Network), i.e., UE-satellite direct communication, used to provide coverage in areas where communication with terrestrial networks is unavailable; and positioning.

[0005] Furthermore, standardization has been implemented in the air interface architecture / protocol for technologies such as: IIoT (Industrial Internet of Things) to support new services through interoperability and convergence with other industries; IAB (Integrated Access and Backhaul) for providing nodes for network service area extension by supporting radio backhaul and access links in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Stack) handover; and two-step random access (2-step RACH for NR) to simplify the random access process. Standardization has also been implemented in the system architecture / services for: 5G baseline architectures (e.g., service-based architectures or service-based interfaces) combining NFV (Network Functions Virtualization) and SDN (Software Defined Networking) technologies, and MEC (Mobile Edge Computing) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, an exponential increase in connected devices will be added to the communication network, thus necessitating enhanced functionality and performance of 5G mobile communication systems, as well as integrated operation of connected devices. To this end, new research is planned related to: XR (Extended Reality) for effective support of AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), etc.; 5G performance improvements and complexity reductions through the utilization of AI (Artificial Intelligence) and ML (Machine Learning); AI service support; metaverse service support; and drone communication.

[0007] Furthermore, this development of 5G mobile communication systems will not only lay the foundation for the development of: new waveforms for providing coverage in the terahertz band of 6G mobile communication technology; multi-antenna transmission technologies (such as FD-MIMO (full-dimensional MIMO), array antennas, and massive MIMO); metamaterial-based lenses and antennas for improving terahertz band signal coverage; high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum); and RIS (reconfigurable smart surfaces), but also for: full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks; AI-based communication technologies for system optimization from the design stage by leveraging satellites and AI and internalizing end-to-end AI support functions; and next-generation distributed computing technologies for enabling services with complexity levels exceeding UE operational capability limitations by utilizing ultra-high-performance communication and computing resources. Summary of the Invention

[0008] [Technical Issues]

[0009] The embodiments described herein are intended to provide devices and methods that can effectively provide services in mobile communication systems.

[0010] [Technical Solution]

[0011] To achieve the above aspects, according to this disclosure, a method performed by a terminal in a wireless communication system may include: receiving downlink control information (DCI), the DCI scheduling resources for transmitting a first physical uplink shared channel (PUSCH) and a second PUSCH, the first PUSCH being associated with a first transmit-receive point (TRP) for uplink transmission and downlink reception of the terminal, and the second PUSCH being associated with a second TRP for uplink transmission only of the terminal; and transmitting a power headroom report (PHR), the PHR including either the first PHR associated with the first PUSCH or the second PHR associated with the second PUSCH. At least one of the following, wherein the first PHR can be calculated based on the downlink path loss calculated using a reference signal, wherein the second PHR can be calculated based on the downlink path loss and the path loss offset, and wherein when both the first PHR and the second PHR are configured to be transmitted, both the first PUSCH and the second PUSCH are transmitted in the time slot n of the transmission of the PHR, and the first PUSCH is scheduled at an earlier time than the second PUSCH, the PHR including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH can be transmitted.

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

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

[0014] A base station in a wireless communication system may include: a transceiver; and a controller connected to the transceiver, wherein the controller may be configured to: transmit downlink control information (DCI), the DCI scheduling resources for transmitting a first physical uplink shared channel (PUSCH) and a second PUSCH, the first PUSCH being associated with a first transmit-receive point (TRP) for uplink transmission and downlink reception of a terminal, and the second PUSCH being associated with a second TRP for uplink transmission only of a terminal; and receive power headroom reports (PHR), the PHR including a first PHR associated with the first PUSCH or a second PUSCH associated with the second PUSCH. At least one of the PHRs, wherein the first PHR can be calculated based on the downlink path loss calculated using a reference signal, wherein the second PHR can be calculated based on the downlink path loss and the path loss offset, and wherein when both the first PHR and the second PHR are configured to be transmitted, both the first PUSCH and the second PUSCH are transmitted in the time slot n of the transmission of the PHR, and the first PUSCH is scheduled at an earlier time than the second PUSCH, the PHR including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH can be transmitted.

[0015] [Beneficial Effects]

[0016] The embodiments described herein provide devices and methods for effectively providing services in mobile communication systems. Attached Figure Description

[0017] Figure 1 The basic structure of the time-frequency domain in a wireless communication system according to an embodiment of the present disclosure is shown.

[0018] Figure 2 The structure of frames, subframes, and time slots in a wireless communication system according to an embodiment of the present disclosure is shown.

[0019] Figure 3 An example of bandwidth configuration in a wireless communication system according to an embodiment of this disclosure is shown.

[0020] Figure 4 The wireless protocol structures of a base station and a UE in single-cell, carrier aggregation, and dual connectivity scenarios in a wireless communication system according to embodiments of the present disclosure are shown.

[0021] Figure 5 The beam application time that can be considered in the case of using a unified TCI scheme in a wireless communication system according to an embodiment of the present disclosure is shown.

[0022] Figure 6 Another MAC-CE structure for activating and indicating a combined TCI state or a separate DL or ULTCI state is shown in a wireless communication system according to an embodiment of this disclosure.

[0023] Figure 7 An example of the control resource set configuration of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown.

[0024] Figure 8 The structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown.

[0025] Figure 9 The process of beam configuration and activation for PDSCH is shown.

[0026] Figure 10 An example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to an embodiment of this disclosure is shown.

[0027] Figure 11 An example of downlink control information (DCI) configuration for cooperative communication is shown in a wireless communication system according to an embodiment of the present disclosure.

[0028] Figure 12 An enhanced PDSCH TCI state-activated / deactivated MAC-CE structure is shown.

[0029] Figure 13An operational example is shown of a UE and a base station operating with multiple TRPs, including a TRP that only supports uplink reception, according to embodiments of the present disclosure.

[0030] Figure 14 An operational example is shown of a base station operating with a plurality of TRPs, including only UL TRPs, and a mobile UE according to an embodiment of the present disclosure.

[0031] Figures 15a to 15d An example is shown whereby a UE, according to an embodiment of the present disclosure, reports trigger power margin for a single carrier to a base station via DCI-based dynamically licensed PUSCH resources.

[0032] Figure 16 An example of an enhanced MAC CE format, in which a field of the TRP type associated with each power margin field is added when twoPHRMode is supported, is shown according to an embodiment of this disclosure.

[0033] Figure 17 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0034] Figure 18 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown. Detailed Implementation

[0035] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0036] In describing the embodiments, technical details well-known in the art to which this disclosure pertains and not directly related to this disclosure have been omitted. This is to convey the essence of this disclosure more clearly by omitting unnecessary explanations.

[0037] For the same reason, some components in the accompanying drawings are exaggerated, omitted, or shown schematically. Furthermore, the dimensions of the individual components do not perfectly reflect their actual dimensions. Consistent reference numerals are assigned to the same or corresponding components in each drawing.

[0038] The advantages and features of this disclosure, as well as methods for implementing them, will become clear upon reference to the embodiments described in detail below with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments disclosed below, but can be implemented in various different forms; these embodiments are provided merely to ensure the completeness of this disclosure and to fully inform those skilled in the art to which this disclosure pertains, and this disclosure is limited only by the scope of the claims. Throughout this disclosure, the same reference numerals denote the same components. Furthermore, in describing this disclosure, detailed explanations of relevant functions or configurations are omitted where such detailed explanations might unnecessarily obscure the essence of this disclosure. The terms described below are defined according to the functions described in this disclosure; however, their meanings may vary depending on the intent or habit of the user or operator. Therefore, their definitions should be determined based on the overall content of this disclosure.

[0039] In the following description, a base station refers to an entity that performs resource allocation to a terminal and can be at least one of the following: gNode B, eNode B, Node B, BS (base station), radio access unit, base station controller, or a node on a network. A terminal can include a UE (user equipment), MS (mobile station), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In this disclosure, downlink (DL) refers to the radio transmission path of a signal from the base station to the terminal, and uplink (UL) refers to the radio transmission path of a signal from the terminal to the base station. Furthermore, in the following description, LTE or LTE-A systems are described as examples, but embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems can include fifth-generation mobile communication technologies (5G, New Radio, or NR) developed after LTE-A, and in the following description, "5G" can be a concept encompassing existing LTE, LTE-A, and other similar services. Furthermore, based on the determination of those skilled in the art, this disclosure can also be applied to other communication systems with some modifications without significantly departing from the scope of this disclosure.

[0040] At this point, it should be understood that each block in the flowchart and combinations thereof can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, the execution of these instructions by the processor of the computer or other programmable data processing apparatus creates means for performing the functions described in the flowchart blocks. Since these computer program instructions can also be stored in computer-accessible or computer-readable memory (which can instruct the computer or other programmable data processing apparatus to perform its functions in a particular manner), the instructions stored in such computer-accessible or computer-readable memory can also be used to produce an article of writing embodying instruction means for performing the functions described in the flowchart blocks. Since computer program instructions can be loaded into a computer or other programmable data processing apparatus, a series of operational steps can be performed on the computer or other programmable data processing apparatus to generate a process executed by the computer; therefore, the instructions that cause the computer or other programmable data processing apparatus to perform the functions described in the flowchart blocks also provide steps for performing these functions.

[0041] Furthermore, each block may represent a module, segment, or code section containing one or more executable instructions for performing a specified logical function. It should also be noted that in some alternative embodiments, the functions mentioned in a block may occur out of order. For example, two blocks shown consecutively may actually execute substantially simultaneously, or these blocks may sometimes execute in reverse order according to their corresponding functions.

[0042] In this context, the term "~unit" as used in this embodiment refers to a software or hardware component, such as an FPGA (Field-Programmable Gate Array) or ASIC (Application-Specific Integrated Circuit), and the "~unit" performs a specific function. However, the term "~unit" is not limited to software or hardware. A "~unit" can be configured to reside on addressable storage media or be executed by one or more processors. Thus, as an example, a "~unit" can include components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within components and "~units" can be combined into a smaller number of components and "~units," or further divided into additional components and "~units." Furthermore, components and "~units" can be implemented to run on one or more CPUs or secure multimedia cards within a device. Additionally, in embodiments, a "~unit" can include one or more processors.

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

[0044] As a typical example of a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) in the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) in the uplink (UL). The uplink refers to the radio link through which user equipment (UE) or mobile station (MS) transmits data or control signals to the base station (BS) (or eNode B), while the downlink refers to the radio link through which the base station transmits data or control signals to the UE. These multiple access schemes separate the data or control information of each user by allocating and manipulating time-frequency resources for transmitting data or control information to each user, thus avoiding overlap and establishing orthogonality.

[0045] As a post-LTE communication system, 5G communication systems must freely reflect the diverse needs of users, service providers, and others, and therefore must support services that meet these diverse needs. Services considered in 5G communication systems include enhanced mobile broadband (eMBB) communication, massive machine-type communication (mMTC), and ultra-reliable low-latency communication (URLLC), among others.

[0046] eMBB aims to provide higher data rates than those supported by existing LTE, LTE-A, or LTE-Pro systems. For example, in 5G communication systems, eMBB must provide a peak data rate of 20Gbps in the downlink and 10Gbps in the uplink for a single base station. Furthermore, 5G communication systems must provide the UE with improved user-perceived data rates and maximum data rates. To meet these requirements, improved transmit / receive technologies, including further enhanced multiple-input multiple-output (MIMO) transmission techniques, are needed. Moreover, the data rates required by 5G communication systems can be achieved by using frequency bandwidths exceeding 20MHz in the 3-6GHz band or above 6GHz, instead of the maximum 20MHz transmission bandwidth used in the 2GHz band of LTE.

[0047] Furthermore, mMTC is being considered for supporting application services such as the Internet of Things (IoT) in 5G communication systems. To effectively deliver IoT, mMTC has requirements such as supporting a large number of UEs within a cell, enhancing UE coverage, improving battery life, and reducing UE costs. Since IoT provides communication capabilities while being supplied to various sensors and devices, it must support a large number of UEs within a cell (e.g., 1,000,000 UEs / km). 2 Furthermore, mMTC-enabled UEs may require wider coverage than other services offered by 5G communication systems because the UE may be located in shaded areas (such as the basement of a building) that are not covered by the cell due to the nature of the service. mMTC-enabled UEs must be configured for low cost and may require very long battery life (such as 10 to 15 years) because frequent battery replacements are difficult.

[0048] Finally, URLLC is a mission-critical wireless communication service based on cellular networks. For example, URLLC can be used for services such as remote control of robots or machines, industrial automation, drones, telemedicine, and emergency alerts. Therefore, URLLC must provide communication with ultra-low latency and ultra-high reliability. For example, services supporting URLLC must meet an air interface latency of less than 0.5ms and may also require 10... -5 Or even lower packet error rates. Therefore, for services that support URLLC, 5G systems must provide shorter transmission time intervals (TTIs) than other services, and may also require designs that allocate significant resources in the frequency band to ensure the reliability of the communication link.

[0049] The three services in 5G—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. In this case, different transmit / receive technologies and parameters can be used between services to meet their different requirements. Of course, 5G is not limited to these three services.

[0050] In the following description, the term "a / b" can be understood as at least one of a and b.

[0051] [NR Time and Frequency Resources]

[0052] The frame structure of a 5G system will be described in more detail below with reference to the accompanying drawings.

[0053] Figure 1 The basic structure of the time-frequency domain, which serves as a radio resource domain for transmitting data or control channels in a 5G system, is shown.

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

[0055] Figure 2 The structure of frames, subframes, and time slots in a wireless communication system according to an embodiment of the present disclosure is shown.

[0056] Figure 2 An example of the structure of frame 200, subframe 201, and time slot 202 is shown. A frame 200 can be defined as 10 ms. A subframe 201 can be defined as 1 ms, therefore a frame 200 can include a total of ten subframes 201. A time slot 202 or 203 can be defined as 14 OFDM symbols (i.e., the number of symbols per time slot). =14). A subframe 201 may include 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 the configuration value μ204 or 205 of the subcarrier spacing. Figure 2 The examples illustrate the cases where the subcarrier spacing configuration value is µ=0 (204) and µ=1 (205). In the case of µ=0 (204), a subframe 201 may include one time slot 202, and in the case of µ=1 (205), a subframe 201 may include two time slots 203. That is, the number of time slots in each subframe... It can vary depending on the subcarrier spacing configuration value µ, and the number of time slots per frame. And it changes accordingly. and The value µ can be defined based on the configuration of each subcarrier spacing, as shown in Table 1 below.

[0057] [Table 1]

[0058] [Bandwidth Component (BWP)]

[0059] The bandwidth portion (BWP) configuration in a 5G communication system will now be described in detail with reference to the accompanying drawings.

[0060] Figure 3 An example of bandwidth configuration in a wireless communication system according to an embodiment of this disclosure is shown.

[0061] Figure 3An example is shown where the UE bandwidth 300 is configured to include two bandwidth portions, namely bandwidth portion #1 (BWP#1) 301 and bandwidth portion #2 (BWP#2) 302. The base station can configure one or more bandwidth portions for the UE, and can configure the information given in Table 2 below for each bandwidth portion.

[0062] [Table 2]

[0063] Of course, the above examples are not limiting, and various parameters related to the bandwidth portion can also be configured for the UE in addition to the configuration information described above. The base station can transmit the configuration information to the UE via higher-layer signaling (e.g., Radio Resource Control (RRC) signaling). One or more configured bandwidth portions, or at least one of them, can be activated. Whether a configured bandwidth portion is activated can be semi-statically transmitted from the base station to the UE via RRC signaling or dynamically transmitted via downlink control information (DCI).

[0064] According to some embodiments, prior to Radio Resource Control (RRC) connection, the initial bandwidth portion (BWP) for initial access can be configured by the base station for the UE via the Master Information Block (MIB). More specifically, the UE can receive configuration information about the control resource set (CORESET) and search space via the MIB, which can be used to transmit PDCCH for receiving system information (which may correspond to the Remaining System Information (RMSI) or System Information Block 1 (SIB1) received via the MIB during the initial access step and necessary for initial access). The control resource set and search space configured via the MIB can each be considered as ID 0. The base station can notify the UE of configuration information about CORESET #0 via the MIB, such as frequency allocation information, time allocation information, and parameter sets. Furthermore, the base station can notify the UE of configuration information about the monitoring period and timing of control resource set #0 via the MIB, i.e., configuration information about search space #0. The UE can consider the frequency domain configured by control resource set #0 obtained from the MIB as the initial bandwidth portion for initial access. The ID of the initial bandwidth portion can be considered as 0.

[0065] The bandwidth-related configurations supported by 5G can be used for various purposes.

[0066] According to some embodiments, if the bandwidth supported by the UE is less than the system bandwidth, this can be achieved through bandwidth configuration. For example, the base station can configure the frequency position of the bandwidth portion for the UE, enabling the UE to send / receive data at a specific frequency position within the system bandwidth.

[0067] Furthermore, according to some embodiments, the base station can configure multiple bandwidth portions for the UE to support different parameter sets. For example, to support UE data transmission / reception using both 15kHz and 30kHz subcarrier spacings, the two bandwidth portions can be configured with subcarrier spacings of 15kHz and 30kHz, respectively. Frequency division multiplexing (FDM) can be applied to the different bandwidth portions, and the bandwidth portion configured for the corresponding subcarrier spacing can be activated if data needs to be transmitted / received at a specific subcarrier spacing.

[0068] Furthermore, according to some embodiments, the base station can configure bandwidth portions with different bandwidth sizes for the UE to reduce the power consumption of the UE. For example, if the UE supports a fairly large bandwidth, such as 100MHz, and always transmits / receives data at that bandwidth, considerable power consumption may occur. In particular, unnecessarily monitoring the downlink control channel with a large bandwidth of 100MHz when there is no service can be quite inefficient from a power consumption perspective. To reduce the power consumption of the UE, the base station can configure a bandwidth portion with a relatively small bandwidth for the UE (e.g., a bandwidth portion of 20MHz). The UE can perform monitoring operations in the 20MHz bandwidth portion when there is no service, and transmit / receive data in the 100MHz bandwidth portion according to the base station's instructions if data is received.

[0069] Regarding the bandwidth configuration method, the UE can receive configuration information about the initial bandwidth portion via the MIB during the initial access step before RRC connection. More specifically, the UE can have a control resource set (i.e., CORESET) configured for the downlink control channel, which can be used to transmit downlink control information (DCI) for scheduling System Information Blocks (SIBs) from the MIB via the Physical Broadcast Channel (PBCH). The bandwidth of the control resource set configured by the MIB can be considered as the initial bandwidth portion, and the UE can receive the Physical Downlink Shared Channel (PDSCH) that transmits the SIBs via the configured initial bandwidth portion. In addition to receiving SIBs, the initial bandwidth portion can also be used for other System Information (OSI), paging, and random access.

[0070] [Bandwidth Component (BWP) Change]

[0071] If the UE has one or more bandwidth portions configured for it, the base station can indicate to the UE to change (or switch or convert) the bandwidth portion by using the bandwidth portion indicator field within the DCI. For example, if the UE's currently active bandwidth portion is Figure 3If the bandwidth portion #1 301 is in the DCI, the base station can use the bandwidth portion indicator in the DCI to indicate the bandwidth portion #2 302, and the UE can change the bandwidth portion to the bandwidth portion #2 302 indicated by the bandwidth portion indicator in the received DCI.

[0072] As mentioned above, bandwidth portion changes based on DCI can be indicated by the DCI used to schedule PDSCH or PUSCH. Therefore, upon receiving a bandwidth portion change request, the UE needs to be able to receive or transmit PDSCH or PUSCH scheduled by the corresponding DCI without problems within the changed bandwidth portion. To this end, the standard specifies the required delay time (T) during the bandwidth portion change. BWP The requirements can be defined, for example, as shown in Table 3 below.

[0073] [Table 3]

[0074] The requirement for bandwidth portion delay time is supported as either Type 1 or Type 2, depending on the UE's capabilities. The UE can report the supported bandwidth portion delay time types to the base station.

[0075] If the UE receives a DCI including a bandwidth partial change indicator in time slot n, then, based on the requirement for bandwidth partial change delay time, the UE can proceed no later than time slot n+T. BWP The change is completed at the point in time from the new bandwidth portion indicated by the bandwidth portion change indicator, and the UE can transmit and / or receive data channels scheduled by the corresponding DCI in the new bandwidth portion. If the base station wants to use the new bandwidth portion to schedule data channels, the base station can change the delay time (T) taking into account the UE's bandwidth portion. BWP In this case, the time-domain resource allocation for the data channel is determined. That is, when a new bandwidth portion is used to schedule the data channel, combined with the method used to determine the time-domain resource allocation for the data channel, the base station can schedule the corresponding data channel after the bandwidth portion change delay time. Therefore, the UE may not expect the DCI indicating the bandwidth portion change to indicate a delay time less than the bandwidth portion change delay time (T). BWP The time slot offset (K0 or K2) value.

[0076] If the UE has received a DCI indicating a partial change in bandwidth (e.g., DCI format 1_1 or 0_1), the UE may refrain from transmitting or receiving for a period of time from the third symbol of the slot used to receive the PDCCH containing the corresponding DCI to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the corresponding DCI. For example, if the UE receives a DCI indicating a partial change in bandwidth in slot n, and if the slot offset value indicated by the corresponding DCI is K, the UE may refrain from transmitting or receiving from the third symbol of slot n to the symbols preceding slot n+K (e.g., the last symbol of slot n+K-1).

[0077] [About CA / DC]

[0078] Figure 4 The radio protocol structures of the base station and UE in single-cell, carrier aggregation, and dual connectivity scenarios according to embodiments of this disclosure are shown.

[0079] refer to Figure 4 The next-generation mobile communication system's wireless protocols include NR Service Data Adaptation Protocol (SDAP) S25 or S70, NR Packet Data Convergence Protocol (PDCP) S30 or S65, NR Radio Link Control (RLC) S35 or S60, and NR Media Access Control (MAC) S40 or S55 on the UE and NR base station sides, respectively.

[0080] The main functions of NR SDAP S25 and S70 may include some of the following functions.

[0081] - Transmission of user plane data

[0082] - Mapping between QoS flows and DRB for both UL and DL

[0083] - Mark QoS flow IDs in DL and UL groups

[0084] - Reflective QoS flow to DRB mapping for UL SDAP PDU

[0085] Regarding SDAP layer devices, the UE can be configured via RRC messages to determine whether to use the SDAP layer device header or its functions for each PDCP layer device, bearer, or logical channel. If the SDAP header is configured, it can include a 1-bit indicator for Non-Access Stratum (NAS) QoS reflection configuration (NAS reflected QoS) and a 1-bit indicator for AS QoS reflection configuration (AS reflected QoS), allowing the UE to update or reconfigure the mapping information for uplink and downlink QoS flows and data bearers. The SDAP header can include QoS flow ID information indicating QoS. QoS information can be used for data processing priority, scheduling information, etc., to smoothly support service.

[0086] The main functions of NR PDCP S30 and S65 may include some of the following functions.

[0087] - Header compression and decompression: ROHC only

[0088] - Transmission of user data

[0089] - Sequential delivery of upper-layer PDUs

[0090] - Unordered delivery of upper-layer PDUs

[0091] - PDCP PDU reordering for received PDUs

[0092] - Duplicate detection of lower-level SDUs

[0093] - PDCP SDU retransmission

[0094] - Encryption and decryption

[0095] - Timer-based SDU dropping in the uplink

[0096] In the aforementioned functions, the reordering of the NR PDCP device refers to the function of reordering PDCP PDUs received from the lower layer based on the PDCP sequence number (SN), and may include the function of delivering data to the upper layer in the reordered order. Alternatively, the reordering of the NR PDCP device may include the function of directly transmitting data regardless of order, the function of reordering and recording lost PDCP PDUs, the function of reporting the status of lost PDCP PDUs to the transmitting side, and the function of requesting retransmission of lost PDCP PDUs.

[0097] The main functions of NR RLC S35 and S60 may include some of the following functions.

[0098] - Transmission of upper-layer PDUs

[0099] - Sequential delivery of upper-layer PDUs

[0100] - Unordered delivery of upper-layer PDUs

[0101] - Error correction via ARQ

[0102] - Cascading, segmentation, and reassembly of RLC SDUs

[0103] - Resegmentation of RLC data PDUs

[0104] - Reordering of RLC data PDUs

[0105] - Duplicate Detection

[0106] - Protocol error detection

[0107] - RLC SDU discard

[0108] - RLC Reconstruction

[0109] In the above functions, the sequential delivery of NR RLC devices refers to the function of delivering RLC SDUs received from lower layers to upper layers in sequence. Sequential delivery of NR RLC devices may include the function of reassembling and delivering the reassembled RLC SDUs if the original RLC SDU is segmented into multiple RLC SDUs and the segmented RLC SDUs are received; the function of reordering received RLC PDUs with reference to the RLC sequence number (SN) or PDCP sequence number (SN); the function of recording RLC PDUs lost due to reordering; the function of reporting the status of lost RLC PDUs to the transmitting side; and the function of requesting retransmission of lost RLC PDUs. Sequential delivery of NR RLC devices may also include the function of sequentially delivering only RLC SDUs preceding the lost RLC SDU to the higher layer if a lost RLC SDU exists; and the function of sequentially delivering all RLCSDUs received before the timer starts, even if a lost RLC SDU exists, if a predetermined timer has expired. Alternatively, the sequential delivery of RLC devices may include the function of sequentially delivering all received RLC SDUs to the upper layer, even if a pre-defined timer has expired and there are lost RLC SDUs. Furthermore, RLC PDUs may be processed in the order they were received (according to arrival order, regardless of sequence number order) and then delivered out of order to the PDCP device (out-of-order delivery). In the case of fragmentation, segments stored in a buffer or segments to be received later may be received, reconstructed into a complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include cascading functionality, and this cascading functionality may be implemented in the NR MAC layer or replaced by multiplexing functionality in the NR MAC layer.

[0110] In the above functions, the out-of-order delivery of NR RLC devices refers to the function of immediately delivering RLC SDUs received from the lower layer to the upper layer regardless of the order. It may include the function of reassembling and delivering multiple RLC SDUs (a single original RLC SDU is segmented into these RLC SDUs) if multiple RLC SDUs are received, and the function of storing the RLC SN or PDCP SN of the received RLC PDUs and recording RLC PDUs lost due to reordering.

[0111] The NR MAC S40 or S55 can connect to multiple NR RLC layer devices configured in a UE, and the main functions of the NR MAC can include some of the following functions.

[0112] - Mapping between logical channels and transport channels

[0113] - MAC SDU multiplexing / demultiplexing

[0114] - Scheduling Information Report

[0115] - Error correction via HARQ

[0116] Priority handling between logical channels of a UE

[0117] - Priority handling between UEs via dynamic scheduling

[0118] - MBMS service identifier

[0119] - Transmission format selection

[0120] - Fill

[0121] The NR PHY layer S45 or S50 can perform channel coding and modulation of upper-layer data, generate OFDM symbols and transmit them through the wireless channel, or demodulate OFDM symbols received through the wireless channel, channel decode them and deliver them to the upper layer.

[0122] The detailed structure of a wireless protocol architecture can vary depending on the carrier (or cell) operation scheme. For example, when a base station transmits data to a UE based on a single carrier (or cell), the base station and UE can use a protocol architecture with a single structure for each layer, such as S00. Conversely, when a base station transmits data to a UE based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and UE have a single structure up to RLC, but use a protocol architecture that multiplexes the PHY layer through the MAC layer, such as S10. As another example, when a base station transmits data to a UE based on dual connectivity (DC) using multiple carriers in multiple TRPs, the base station and UE have a single structure up to RLC, but use a protocol architecture that multiplexes the PHY layer through the MAC layer, such as S20.

[0123] [Unified TCI Status]

[0124] The following describes a single TCI state indication and activation method based on a unified TCI scheme. A unified TCI scheme can refer to a scheme that unifies the existing Rel-15 / 16 transmit and receive beam management schemes, which are divided into a TCI state scheme used in downlink reception and a spatial relationship information scheme used in uplink transmission, into a single TCI state scheme and operates accordingly. Therefore, when the UE receives an indication from the base station based on the unified TCI scheme, the UE can also perform beam management for uplink transmission using the TCI state. If the UE is configured with a higher-layer signaling TCI-State from the base station with higher-layer signaling tci-stateId-r17, the UE can use the corresponding TCI-State to perform operations based on the unified TCI scheme. TCI-States can exist in two types: joint TCI states or individual TCI states.

[0125] The first type is a joint TCI state, where all TCI states to be applied to uplink transmission and downlink reception can be indicated to the UE by the base station through a TCI-State. If a TCI-State based on a joint TCI state is indicated to the UE, the parameters to be used for downlink channel estimation and the parameters to be used as the downlink receive beam or receive filter can be indicated to the UE using the RS corresponding to the qcl-Type1 of the corresponding joint TCI-State. If a TCI-State based on a joint TCI state is indicated to the UE, the parameters to be used as the uplink transmit beam or transmit filter can be indicated to the UE using the RS corresponding to the qcl-Type2 of the corresponding joint DL / UL TCI-State. If a joint TCI state is indicated to the UE, the UE can apply the same beam to both uplink transmission and downlink reception.

[0126] The second type is a separate TCI state, where the base station can indicate to the UE the UL TCI state to be applied to uplink transmission and the DL TCI state to be applied to downlink reception, respectively. If the UL TCI state is indicated to the UE, the parameters to be used as the uplink transmission beam or transmission filter can be indicated to the UE using the reference RS or source RS configured in the corresponding UL TCI state. If the DL TCI state is indicated to the UE, the parameters to be used for downlink channel estimation can be indicated to the UE using the RS corresponding to qcl-Type1 of the corresponding DL TCI state, and the parameters to be used as the downlink reception beam or reception filter can be indicated to the UE using the RS corresponding to qcl-Type2.

[0127] If both the DL TCI state and the UL TCI state are indicated to the UE, the parameters to be used as the uplink transmit beam or transmit filter can be indicated to the UE using the reference RS or source RS configured in the UL TCI state. The parameters to be used for downlink channel estimation can be indicated to the UE using the RS corresponding to qcl-Type1 configured in the DL TCI state, and the parameters to be used as the downlink receive beam or receive filter can be indicated to the UE using the RS corresponding to qcl-Type2. In this case, if the reference RS or source RS configured in the DL TCI state and the UL TCI state indicated to the UE are different, the UE can apply the beam to the uplink transmit and downlink receive states respectively based on the indicated UL TCI state and DL TCI state.

[0128] For a specific bandwidth portion within a specific cell, the base station can configure up to 128 joint TCI states for the UE via higher-layer signaling. Based on the UE capability report, it can also configure up to 64 or 128 individual TCI states within a specific TCI state for the same bandwidth portion within a specific cell via higher-layer signaling. Furthermore, the DL TCI states within an individual TCI state and the joint TCI states can use the same higher-layer signaling structure. For example, if 128 joint TCI states are configured and 64 DL TCI states are configured within an individual TCI state, then the 64 DL TCI states can be included within the 128 joint TCI states.

[0129] Based on the UE capability report, up to 32 or 64 UL TCI states can be configured for each specific BWP in a specific cell via higher-layer signaling. The UL TCI states of individual TCI states and the joint TCI states can use the same higher-layer signaling structure, such as the relationship between the DL TCI states of individual TCI states and the joint TCI states. However, the UL TCI states of individual TCI states can use different higher-layer signaling structures than the DL TCI states of the joint TCI states and the DL TCI states of individual TCI states.

[0130] This situation, where different or the same higher-layer signaling structures are used, can be defined in the specifications, or it can be distinguished by another higher-layer signaling configured by the base station based on a UE capability report containing information about which of the two schemes the UE supports.

[0131] The UE can receive transmit and receive beam-related indications based on a unified TCI scheme, either a joint TCI state or a separate TCI state configured by the base station. Which of the joint or separate TCI states to use can be configured by the base station for the UE via higher-layer signaling.

[0132] The UE can receive transmit and receive beam-related indications via higher-layer signaling by using a scheme selected from the joint TCI state and the individual TCI state. The base station's method of indicating transmit / receive beams can be divided into two types: MAC-CE-based indication method and MAC-CE-based activation and DCI-based indication method.

[0133] If the UE uses joint TCI states to receive transmit and receive beam-related indications via higher-layer signaling, the UE can perform transmit and receive beam application operations by receiving a MAC-CE indicating the joint TCI states from the base station, and the base station can schedule PDSCH reception including the corresponding MAC-CE to the UE via PDCCH. If the MAC-CE includes a set of joint TCI states, the UE can determine the uplink transmit beam or transmit filter and the downlink receive beam or receive filter using the joint TCI states included in the indicated set of joint TCI states 3ms after transmitting a PUCCH including HARQ-ACK information indicating whether the PDSCH has been successfully received. If the MAC-CE includes two or more sets of joint TCI states, the UE can identify the corresponding code points of the TCI state fields in DCI format 1_1 or 1_2 corresponding to the multiple sets of joint TCI states indicated by the MAC-CE, and then activate the indicated set of joint TCI states 3ms after transmitting a PUCCH including HARQ-ACK information indicating whether the PDSCH has been successfully received. Subsequently, the UE can receive DCI format 1_1 or 1_2, and can apply a joint TCI state indicated by the TCI state field in the corresponding DCI to the uplink transmit and downlink receive beams. DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL allocation) or may not include downlink data channel scheduling information (without DL allocation).

[0134] When a UE receives an indication of transmit / receive beams using individual TCI states via higher-layer signaling, the UE can receive a MAC-CE indicating the individual TCI states from the base station, thereby performing transmit / receive beam application operations. The base station can also schedule the reception of a PDSCH including the MAC-CE to the UE via the PDCCH. If the MAC-CE includes a single TCI state set, the UE can determine the uplink transmit beam, transmit filter, and downlink receive beam or receive filter using the individual TCI states included in the indicated single TCI state set 3ms after transmitting a PUCCH including HARQ-ACK information indicating whether the corresponding PDSCH has been successfully received. A single TCI state set can refer to one or more individual TCI states that a code point in the TCI state field of DCI format 1_1 or 1_2 can have, and a single TCI state set can include a DLTCI state, a UL TCI state, or a DL TCI state and a UL TCI state. If the MAC-CE includes two or more separate TCI state sets, the UE can identify and activate the indicated separate TCI state sets 3ms after transmitting the PUCCH, which includes HARQ-ACK information indicating whether the corresponding PDSCH has been successfully received, corresponding to the code points of the TCI state fields of DCI format 1_1 or 1_2 as indicated by the MAC-CE. In this case, each code point of the TCI state field of DCI format 1_1 or 1_2 can indicate a DL TCI state, a UL TCI state, or a DL TCI state and a UL TCI state. The UE can receive DCI format 1_1 or 1_2 and apply the separate TCI state sets indicated by the corresponding DCI TCI state fields to the uplink transmit beam and downlink receive beam. DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL allocation) or may not include downlink data channel scheduling information (without DL allocation).

[0135] Figure 5 The present disclosure illustrates beam application times that can be considered when using a unified TCI scheme in a wireless communication system according to embodiments of the present disclosure. As described above, the UE can receive DCI format 1_1 or 1_2 from the base station with or without downlink data channel scheduling information (DL allocation), and apply a joint TCI state or a set of individual TCI states indicated by the TCI state field of the corresponding DCI to the uplink transmit beam and the downlink receive beam.

[0136] - DCI format 1_1 or 1_2 with DL allocation (500): If the UE receives DCI format 1_1 or 1_2 (501) from the base station, which includes downlink data channel scheduling information, such that a joint TCI state or a single TCI state set based on a unified TCI scheme is indicated, the UE may receive PDSCH (505) based on the received DCI scheduling and send a PUCCH (510) including a HARQ-ACK indicating whether the reception of DCI and PDSCH was successful. In this case, HARQ-ACK may include whether the reception of both DCI and PDSCH was successful. If the UE fails to receive at least one of DCI and PDSCH, the UE may send NACK, and if the UE successfully receives both, the UE may send ACK.

[0137] - DCI format 1_1 or 1_2 (550) without DL allocation: If the UE receives DCI format 1_1 or 1_2 (555) from the base station that does not include downlink data channel scheduling information, such that a joint TCI state or a single TCI state set based on a unified TCI scheme is indicated, the UE may assume at least one combination of the following for the DCI.

[0138] ■ DCI includes CRC scrambling using CS-RNTI.

[0139] ■ All bits assigned to all fields used as the Redundancy Version (RV) field have a value of 1.

[0140] ■ All bits assigned to all fields used as modulation and coding scheme (MCS) fields have a value of 1.

[0141] ■ All bits assigned to all fields used as New Data Indicator (NDI) fields have a value of 0.

[0142] ■ In the case of Frequency Domain Resource Allocation (FDRA) type 0, all bits allocated to the FDRA field have a value of 0; in the case of FDRA type 1, all bits allocated to the FDRA field have a value of 1; and in the case of FDRA scheme dynamicSwitch, all bits allocated to the FDRA field have a value of 0.

[0143] The UE may send a PUCCH (560) that includes a HARQ-ACK indicating whether the DCI format 1_1 or 1_2 assuming the above entry has been successfully received.

[0144] - Regarding both DCI formats 1_1 and 1_2 with and without DL allocation (500), if the new TCI state indicated by DCI 501 or 555 is the same as the previously indicated TCI state and thus applied to the uplink transmit beam and downlink receive beam, the UE can maintain the previously applied TCI state. If the new TCI state is different from the previously indicated TCI state, the UE can determine the application time of the joint TCI state or individual TCI state set, which can be indicated by the TCI state field included in the DCI, as time point 530 or 580 after the first time slot 520 or 570 after a time interval of beam application time (BAT) 515 or 565 following the PUCCH transmission, and can use the previously indicated TCI state at time point 525 or 575 before time slot 520 or 570.

[0145] - Regarding both DCI formats 1_1 and 1_2 with and without DL allocation (500), BAT is a specific number of OFDM symbols and can be configured via higher-layer signaling based on UE capability report information. The parameter set of BAT and the first time slot after BAT can be determined based on the minimum parameter set of all cells to which the joint TCI state or individual TCI state set indicated by DCI is applied.

[0146] The UE can apply a joint TCI state indicated by MAC-CE or DCI to the reception of control resource sets connected to all UE-specific search spaces, the reception of PDSCH scheduled by PDCCH sent from these control resource sets, the transmission of PUSCH, and the transmission of all PUCCH resources.

[0147] If a single TCI state set indicated by MAC-CE or DCI includes a DL TCI state, the UE may apply that single TCI state set to reception for control resource sets connected to all UE-specific search spaces and to reception of PDSCH scheduled by PDCCHs sent from these control resource sets, and apply the previously indicated UL TCI state to all PUSCH and PUCCH resources.

[0148] If a single TCI state set indicated by MAC-CE or DCI includes a UL TCI state, the UE may apply that single TCI state set to all PUSCH and PUCCH resources and apply the previously indicated DL TCI state to reception of control resource sets connected to all UE-specific search spaces and reception of PDSCH scheduled by PDCCHs sent from these control resource sets.

[0149] If a single TCI state set indicated by MAC-CE or DCI includes a DL TCI state and a ULTCI state, the UE may apply the DL TCI state to reception of control resource sets connected to all UE-specific search spaces and reception of PDSCH scheduled by PDCCHs sent from these control resource sets, and apply the ULTCI state to all PUSCH and PUCCH resources.

[0150] [Unified TCI Status MAC-CE]

[0151] The following describes a single TCI state indication and activation method based on a unified TCI scheme. The PDSCH including MAC-CE described below can be scheduled to the UE by the base station, and the UE can interpret each code point of the TCI state field in DCI format 1_1 or 1_2 based on information in the MAC-CE received from the base station within three time slots after sending a HARQ-ACK for the PDSCH to the base station. That is, the UE can activate each entry of the MAC-CE received from the base station in each code point of the TCI state field in DCI format 1_1 or 1_2.

[0152] Figure 6 Another MAC-CE structure for activating and indicating a combined TCI state or a separate DL or ULTCI state in a wireless communication system according to an embodiment of this disclosure is shown. Each field in the MAC-CE structure may have the following meaning.

[0153] - Serving Cell ID 600: This field indicates the serving cell to which the corresponding MAC-CE is applied. The field can be 5 bits long. If the serving cell indicated by this field is included in at least one of the higher-layer signaling lists simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4, then the MAC-CE can be applied to all serving cells included in one or more of these higher-layer signaling lists, where the serving cell indicated by this field is included.

[0154] - DL BWP ID 605: This field indicates the DL BWP to be applied to MAC-CE, and the code points in this field can correspond to the code points of the bandwidth section indicator in DCI. This field can be 2 bits long.

[0155] - UL BWP ID 610: This field indicates the UL BWP to be applied to MAC-CE, and the code points in this field can correspond to the code points of the bandwidth section indicator in DCI. The length of this field can be 2 bits.

[0156] - P i 615: This field can indicate whether each code point in the TCI status field of DCI format 1_1 or 1_2 has multiple TCI statuses or one TCI status. If P i A value of 1 indicates that the corresponding i-th code point has multiple TCI states, and may imply that the code point can include a separate DL TCI state and a separate UL TCI state. If P i A value of 0 indicates that the corresponding i-th code point has a single TCI state, and may imply that the code point may include one of the following types: joint TCI state, individual DCI TCI state, or individual UL TCI state.

[0157] - D / U 620: This field indicates whether the TCI status ID field in the same octet is a combined TCI status, a separate DL TCI status, or a separate UL TCI status. If this field is 1, the TCI status ID field in the same octet can be a combined TCI status or a separate DL TCI status; if this field is 0, the TCI status ID field in the same octet can be a separate UL TCI status.

[0158] - TCI State ID 625: This field indicates a TCI state that can be identified by the higher-layer signaling TCI-StateId. If the D / U field is configured to 1, this field can be used to represent the TCI-StateId, which can be represented by 7 bits. If the D / U field is configured to 0, the most significant bit (MSB) of the TCI State ID field can be considered a reserved bit, and the remaining 6 bits can be used to represent the higher-layer signaling UL-TCIState-Id. The maximum number of active TCI states can be 8 in the case of combined TCI states, and 16 in the case of individual DL or UL TCI states.

[0159] - R: This indicates that the reserved bit can be configured to 0.

[0160] about Figure 6The MAC-CE structure allows the UE to include... Figure 6 The third octet in the MAC-CE configuration, regardless of whether the unifiedTCI-StateType-r17 in MIMOparam-r17 of the upper-layer signaling ServingCellConfig is configured as unified or separate, includes the P1, P2, ..., and P8 fields. In this case, the UE can perform TCI state activation using a fixed MAC-CE structure, regardless of the upper-layer signaling configured by the base station. As another example, regarding... Figure 6 In the MAC-CE structure, if the unifiedTCI-StateType-r17 in MIMOparam-r17 of the upper-layer signaling ServingCellConfig is configured as united, the UE can omit... Figure 6 The third octet shown includes the P1, P2, ..., and P8 fields. In this case, the UE can save up to 8 bits of the corresponding MAC-CE payload based on the higher-layer signaling configured by the base station. Furthermore, Figure 6 All D / U fields in the first bit of the octet starting from the fourth octet can be considered as R fields, and all R fields can be configured to 0 bits.

[0161] [PDCCH: About DCI]

[0162] Next, we will describe downlink control information (DCI) in a 5G system in detail.

[0163] In 5G systems, scheduling information for uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) is included in the DCI and transmitted from the base station to the UE via the DCI. The UE can monitor the backoff DCI format and the non-backoff DCI format for either the PUSCH or the PDSCH. The backoff DCI format may include predefined fixed fields between the base station and the UE, while the non-backoff DCI format may include configurable fields.

[0164] The DCI message undergoes channel coding and modulation, and is transmitted via the Physical Downlink Control Channel (PDCCH) after these processes. Cyclic Redundancy Check (CRC) can be attached to the DCI message payload, and the CRC can be scrambled using the RNTI corresponding to the UE identifier. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control commands, or random access responses. That is, the RNTI is not explicitly sent but is included in the CRC calculation process. Once a DCI message transmitted via the PDCCH is received, the UE can identify the CRC using the assigned RNTI, and if the CRC identification result is correct, the UE knows that the corresponding message has been sent.

[0165] For example, the DCI used for scheduling PDSCH about System Information (SI) can be scrambled by SI-RNTI. The DCI used for scheduling PDSCH about Random Access Response (RAR) messages can be scrambled by RA-RNTI. The DCI used for scheduling PDSCH about paging messages can be scrambled by P-RNTI. The DCI used for notifying Slot Format Indicator (SFI) can be scrambled by SFI-RNTI. The DCI used for notifying Transmit Power Control (TPC) can be scrambled by TPC-RNTI. The DCI used for scheduling UE-specific PDSCH or PUSCH can be scrambled by Cell RNTI (C-RNTI).

[0166] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, and in this case, CRC can be scrambled by C-RNTI. DCI format 0_0 with CRC scrambled by C-RNTI can, for example, include the information given in Table 4 below.

[0167] [Table 4]

[0168] DCI format 0_1 ​​can be used as a non-back-off DCI for scheduling PUSCH, and in this case, CRC can be scrambled by C-RNTI. DCI format 0_1 ​​with CRC scrambled by C-RNTI can, for example, include the information given in Table 5 below.

[0169] [Table 5]

[0170] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, and in this case, CRC can be scrambled by C-RNTI. DCI format 1_0 with CRC scrambled by C-RNTI can, for example, include the information given in Table 6 below.

[0171] [Table 6]

[0172] DCI format 1_1 can be used as a non-back-off DCI for scheduling PDSCH, and in this case, CRC can be scrambled by C-RNTI. DCI format 1_1 with CRC scrambled by C-RNTI can, for example, include the information given in Table 7 below.

[0173] [Table 7]

[0174] [PDCCH: CORESET, REG, CCE, and Search Space]

[0175] The downlink control channel in a 5G communication system will be described in more detail below with reference to the accompanying drawings.

[0176] Figure 7 An example of a control resource set (CORESET) for transmitting downlink control channels in a 5G wireless communication system is shown. Figure 7 An example is shown where a UE bandwidth portion 710 is configured along the frequency axis, and two control resource sets (control resource set #1 701 and control resource set #2 702) are configured along the time axis within a timeslot 720. Control resource sets 701 and 702 can be configured along the frequency axis within a specific frequency resource 703 throughout the entire UE bandwidth portion 710. Control resource sets 701 and 702 can each be configured along the time domain as one or more OFDM symbols, and the number of OFDM symbols can be defined as the control resource set duration 704. Reference Figure 7 In the example shown, control resource set #1 701 is configured to have control resource set durations corresponding to two symbols, and control resource set #2 702 is configured to have control resource set durations corresponding to one symbol.

[0177] The control resource set in 5G described above can be configured by the base station for the UE via upper-layer signaling (e.g., system information, Master Information Block (MIB), or Radio Resource Control (RRC) signaling). Configuring the control resource set for the UE means providing information including the control resource set identifier, the frequency location of the control resource set, and the symbol duration of the control resource set. For example, this information may include the information given in Table 8 below.

[0178] [Table 8]

[0179] In Table 8, the tci-StatesPDCCH (Transmission Configuration Indication (TCI) status) configuration information may include information about one or more SS / PBCH block indices or Channel State Information Reference Signal (CSI-RS) indices that correspond to the DMRS Quasi-Co-located (QCLed) transmitted in the corresponding CORESET.

[0180] Figure 8 An example of the basic units constituting the time and frequency resources available in the downlink control channel in 5G is shown. Figure 8 The basic unit constituting the time and frequency resources of the control channel can be called a resource element group (REG) 803, and a REG 803 can be defined by an OFDM symbol 801 on the time axis and a physical resource block (PRB) 802 (i.e., 12 subcarriers) on the frequency axis. The base station can configure the downlink control channel allocation unit by cascading REG 803.

[0181] Assuming the basic unit of downlink control channel allocation in 5G is as follows: Figure 8 The control channel element 804 shown can be a single CCE 804 that may include multiple REG 803s. (For description...) Figure 8 The REG 803 shown, for example, may include 12 REs, and if a CCE 804 includes six REG 803s, then a CCE 804 may include 72 REs. Once a downlink control resource set is configured, it may include multiple CCE 804s, and a specific downlink control channel may be mapped to one or more CCE 804s and then transmitted according to the aggregation level (AL) in the control resource set. CCE 804s in the control resource set are distinguished by numbers, and the numbers of CCE 804s may be assigned according to a logical mapping scheme.

[0182] Figure 8 The basic unit of the downlink control channel shown, REG 803, can include the RE mapped to by the DCI and the region mapped to by the reference signal (DMRS 805) used to decode the DCI. Figure 8As shown, three DMRS 805s can be transmitted within a single REG 803. The number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8, or 16 depending on the aggregation level (AL), and link adaptation of the downlink control channel can be achieved using different numbers of CCEs. For example, in the case of AL=L, a downlink control channel can be transmitted using L CCEs. The UE needs to detect the signal without information about the downlink control channel, therefore a search space indicating the set of CCEs has been defined for blind decoding. The search space is the set of downlink control channel candidates, which includes the CCEs that the UE needs to attempt to decode under a given AL, and since 1, 2, 4, 8, or 16 CCEs can form a bundle under various ALs, the UE can have multiple search spaces. The search space set can be defined as the set of search spaces under all configured aggregation levels.

[0183] The search space can be divided into a common search space and a UE-specific search space. A group of UEs or all UEs can search the common search space of the PDCCH to receive cell common control information, such as dynamic scheduling of system information or paging messages. For example, PDSCH scheduling allocation information used to transmit SIBs, including cell operator information, can be received by searching the common search space of the PDCCH. In the case of the common search space, a group of UEs or all UEs need to receive the PDCCH, so the common search space can be defined as a predetermined set of CCEs. Scheduling allocation information for UE-specific PDSCH or PUSCH can be received by searching the UE-specific PDCCH search space. The UE-specific search space can be specifically defined for each UE as functions of various system parameters and the UE's identifier.

[0184] In 5G, parameters regarding the PDCCH search space can be configured by the base station for the UE via upper-layer signaling (e.g., SIB, MIB, or RRC signaling). For example, the base station can provide the UE with configurations such as: the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring timing for each symbol within a time slot of the search space, the search space type (public search space or UE-specific search space), the combination of RNTI and DCI formats to be monitored in the corresponding search space, and the control resource set index used for monitoring the search space. For example, the configuration information may include the information given in Table 9 below.

[0185] [Table 9]

[0186] Based on the configuration information, the base station can configure one or more search space sets for the UE. According to some embodiments, the base station can configure search space set 1 and search space set 2 for the UE, and can be configured to monitor DCI format A scrambled by X-RNTI in the common search space of search space set 1, and can be configured to monitor DCI format B scrambled by Y-RNTI in the UE-specific search space of search space set 2.

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

[0188] The following combinations of DCI formats and RNTI can be monitored in the public search space. Obviously, the following examples are not limiting.

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

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

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

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

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

[0194] The following combinations of DCI formats and RNTI can be monitored within the UE-specific search space. Obviously, the following examples are not limiting.

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

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

[0197] The enumerated RNTI can follow the definitions and uses given below.

[0198] Cell RNTI (C-RNTI): Used for scheduling UE-specific PDSCH

[0199] Temporary Cell RNTI (TC-RNTI): Used for scheduling UE-specific PDSCH

[0200] Configured Scheduling RNTI (CS-RNTI): Used to schedule UE-specific PDSCHs with semi-static configuration.

[0201] Random Access RNTI (RA-RNTI): Used to schedule PDSCH during the random access step.

[0202] Paging RNTI (P-RNTI): Used to schedule the PDSCH in which paging is sent.

[0203] System Information RNTI (SI-RNTI): Used to schedule the PDSCH in which system information is sent.

[0204] Interrupt RNTI (INT-RNTI): Used to indicate whether the PDSCH has been punched.

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

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

[0207] Transmit power control for SRS RNTI (TPC-SRS-RNTI): Used to indicate power control commands regarding the SRS.

[0208] The DCI formats enumerated above can follow the definitions given in Table 10 below.

[0209] [Table 10]

[0210] In 5G, the search space associated with the control resource set p and the search space set s at the aggregation level L can be represented by the following Equation 1.

[0211] [Equation 1]

[0212] - L: Aggregation Level

[0213] - Carrier index

[0214] - Control resource set pThe total number of CCEs existing in

[0215] - Time slot index

[0216] - Number of PDCCH candidates under aggregation level L

[0217] - = 0, ..., -1: PDCCH candidate index under aggregation level L

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

[0219] - , , , ,

[0220] - UE identifier

[0221] In the context of public search spaces, The value can correspond to 0.

[0222] In the case of a specific search space for the UE The value can correspond to a value that varies based on the UE's identifier (C-RNTI or ID configured by the base station for the UE) and time index.

[0223] In 5G, multiple search space sets can be configured with different parameters (e.g., the parameters in Table 9), and the group of search space sets monitored by the UE at each time point can be different accordingly. For example, if search space set #1 is configured periodically with time slot X, and search space set #2 is configured periodically with time slot Y, and if X and Y are different, then the UE can monitor both search space set #1 and search space set #2 in a specific time slot, and can monitor only one of search space set #1 and search space set #2 in another specific time slot.

[0224] [PUCCH: About Transmission]

[0225] In an NR system, a UE can send control information (UCI) to a base station via PUCCH. The control information may include at least one of the following: a HARQ-ACK indicating whether the UE has successfully demodulated / decoded a transport block (TB) received via PDSCH, a scheduling request (SR) (through which the UE requests the PUSCH base station to allocate resources for uplink data transmission), and channel state information (CSI) as information for reporting the UE's channel state.

[0226] PUCCH resources are typically categorized into long PUCCHs and short PUCCHs based on the length of the allocated symbols. In NR systems, long PUCCHs have a length of 4 or more symbols in a time slot, while short PUCCHs have a length of 2 or fewer symbols in a time slot.

[0227] In a more detailed description of long PUCCH, long PUCCH can be used to increase uplink cell coverage and therefore can be transmitted in a DFT-S-OFDM scheme associated with single-carrier transmission, rather than in OFDM transmission. Depending on the number of control information bits supported and whether or not UE multiplexing is supported via pre-DFT OCC supported at the IFFT front end, long PUCCH supports transmission formats such as PUCCH format 1, PUCCH format 3, and PUCCH format 4.

[0228] First, PUCCH format 1 is a long PUCCH format based on DFT-S-OFDM, capable of supporting up to 2 bits of control information and using as many frequency resources as 1 RB. The control information can be configured by a combination of HARQ-ACK and SR, or each of them. PUCCH format 1 has a structure that includes OFDM symbols comprising a demodulation reference signal (DMRS) (which is a demodulation reference signal (or reference signal)) and repeated OFDM symbols including UCI.

[0229] For example, if the number of transmission symbols in PUCCH format 1 is 8, these 8 symbols can be configured sequentially from the first start symbol: DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, and UCI symbol. For a sequence within an OFDM symbol corresponding to a length of 1 RB on the frequency axis, orthogonal codes (or orthogonal sequences or spreading codes) can be used on the time axis. The DMRS symbols are spread, processed by IFFT, and then transmitted.

[0230] Regarding UCI symbols, the UE can perform BPSK modulation on 1 bit of control information or QPSK modulation on 2 bits of control information to generate d(0). The generated d(0) is then multiplied by a sequence corresponding to a length of 1 RB on the frequency axis for scrambling, and an orthogonal code (or orthogonal sequence or spreading code) is used on the time axis. The scrambled sequence is spread, the spread sequence is IFFTed, and then transmitted.

[0231] The UE generates a sequence based on the group transition or sequence transition configuration configured by the base station through higher-layer signaling and the configured ID, and cyclically shifts the generated sequence by using the initial cyclic shift (CS) value configured through higher-layer signaling to generate a sequence corresponding to a length of 1 RB.

[0232] If the length of the spreading code (NSF) is given, and specifically as shown in Table 11 below, then It can be determined as . i represents the index of the spreading code itself, and m represents the index of each element of the spreading code. Here, the numbers in square brackets [ ] in Table 11 can represent For example, if the length of the spreading code is 2 and the configured spreading code index i is 0 (i=0), then the spreading code... It can be and Therefore, it can be equal to [1 1] ( =[1 1]).

[0233] [Table 11]

[0234] Next, PUCCH format 3 is a long PUCCH format based on DFT-S-OFDM, which can support control information greater than 2 bits, and the number of RBs used can be configured by the upper layer. The control information can be configured by a combination of HARQ-ACK, SR, and CSI, or each of them individually. The DMRS symbol positions in PUCCH format 3 are determined by whether frequency hopping exists in the time slot and whether additional DMRS symbols are configured, as shown in Table 12 below.

[0235] [Table 12]

[0236] If the number of transmission symbols for PUCCH format 3 is 8, then DMRS is transmitted on the first and fifth symbols by using the 0th symbol, which is the first start symbol of the 8 symbols. Table 12 also applies to the DMRS symbol positions for PUCCH format 4.

[0237] Next, PUCCH format 4 is a long PUCCH format based on DFT-S-OFDM, capable of supporting control information greater than 2 bits and using as many frequency resources as 1 RB. Control information can be configured by a combination or individual of HARQ-ACK, SR, and CSI. The difference between PUCCH format 4 and PUCCH format 3 is that in PUCCH format 4, PUCCH format 4 for several UEs is multiplexed within one RB. Multiple UEs' PUCCH format 4 can be multiplexed by applying pre-DFT orthogonal overlay codes (OCCs) to the control information at the IFFT front end. However, the number of control information symbols a UE can transmit decreases depending on the number of multiplexed UEs. The number of multiplexed UEs, i.e., the number of different available OCCs, can be 2 or 4, and the number of OCCs to be applied and the OCC index can be configured through higher layers.

[0238] Next, the short PUCCH will be described. The short PUCCH can be transmitted on both the downlink center time slot and the uplink center time slot, and is typically transmitted on the last symbol of the time slot or on a later OFDM symbol (e.g., the last OFDM symbol, the penultimate OFDM symbol, or the last two OFDM symbols). The short PUCCH can also be transmitted at random locations within the time slot. The short PUCCH can also be transmitted using one or two OFDM symbols. Compared to the long PUCCH, the short PUCCH can be used to reduce latency when uplink cell coverage is good, and it can be transmitted in the CP-OFDM scheme.

[0239] Depending on the number of control information bits supported, short PUCCHs can support transmission formats such as PUCCH format 0 and PUCCH format 2. First, PUCCH format 0 is a short PUCCH format capable of supporting up to 2 bits of control information and using the same number of frequency resources as 1 RB. The control information can be configured by a combination of HARQ-ACK and SR, or each of them individually. PUCCH format 0 has a structure that transmits only a sequence mapped to 12 subcarriers on the frequency axis within a single OFDM symbol, without transmitting DMRS. The UE generates the sequence based on a group hopping or sequence hopping configuration configured by the base station via higher-layer signaling and a configured ID. The generated sequence is cyclically shifted (CS) by adding a final CS value obtained by adding the indicated initial CS value to the CS value after changes based on ACK or NACK, mapping the sequence to the 12 subcarriers, and then transmitting the mapped sequence.

[0240] For example, if HARQ-ACK has 1 bit, as shown in Table 13 below, if HARQ-ACK is ACK, the UE generates the final CS by adding 6 to the initial CS value; if HARQ-ACK is NACK, the UE generates the final CS by adding 0 to the initial CS value. The CS value of 0 for NACK and 6 for ACK are defined in the specification. The UE can generate PUCCH format 0 to send a 1-bit HARQ-ACK based on the values ​​defined in the specification.

[0241] [Table 13]

[0242] For example, if the HARQ-ACK has 2 bits as shown in Table 14, then if the HARQ-ACK is (NACK, NACK), the UE adds 0 to the initial CS value; if the HARQ-ACK is (NACK, ACK), the UE adds 3 to the initial CS value; if the HARQ-ACK is (ACK, ACK), the UE adds 6 to the initial CS value; and if the HARQ-ACK is (ACK, NACK), the UE adds 9 to the initial CS value. The values ​​0 (NACK, NACK), 3 (NACK, ACK), 6 (ACK, ACK), and 9 (ACK, NACK) are defined in the specification. The UE can generate PUCCH format 0 to send a 2-bit HARQ-ACK based on the values ​​defined in the specification. If the final CS value exceeds 12 due to adding a CS value to the initial CS value based on ACK or NACK, since the sequence length is 12, a modulo 12 is applied to the final CS value.

[0243] [Table 14]

[0244] Next, 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 configured by the upper layer. The control information can be configured by a combination of HARQ-ACK, SR, and CSI, or each of them individually. If the index of the first subcarrier is #0, then PUCCH format 2 can be fixed to subcarriers with indices #1, #4, #7, and #10 as the positions of the subcarriers in which the DMRS is transmitted within an OFDM symbol. The control information can be channel-coded and then modulated to map to the remaining subcarriers other than the subcarrier containing the DMRS.

[0245] In summary, the configurable values ​​and their ranges for each of the above PUCCH formats can be organized as shown in Table 15 below. In Table 15, cases where no configuration value is required are marked as "NA".

[0246] [Table 15]

[0247] To improve uplink coverage, multi-slot repetition is supported for PUCCH formats 1, 3, and 4, and PUCCH repetition can be configured for each PUCCH format. The UE can perform PUCCH repetition including UCI, the same number of times as the number of slots configured via the higher-layer signaling `nrofSlots`. For PUCCH repetition, the same number of consecutive symbols can be used for PUCCH transmissions in each slot, and the number of consecutive symbols can be configured via `nrofSymbols` in the higher-layer signaling PUCCH-format1, PUCCH-format3, or PUCCH-format4. For PUCCH repetition, the same start symbol can be used for PUCCH transmissions in each slot, and the start symbol can be configured via `startingSymbolIndex` in the higher-layer signaling PUCCH-format1, PUCCH-format3, or PUCCH-format4. For PUCCH repetition, a single `PUCCH-spatialRelationInfo` can be configured for a single PUCCH resource. For PUCCH repetitive transmissions, if the UE is configured to perform frequency hopping between PUCCH transmissions on different time slots, the UE can perform frequency hopping on a time slot basis. Furthermore, if the UE is configured to perform frequency hopping between PUCCH transmissions on different time slots, the UE can start PUCCH transmission on the even-numbered time slot at the first PRB index configured via the higher-layer signaling startingPRB, and on the odd-numbered time slot at the second PRB index configured via the higher-layer signaling secondHopPRB. Additionally, if the UE is configured to perform frequency hopping between PUCCH transmissions on different time slots, the index of the time slot instructing the UE to perform the first PUCCH transmission is 0, and the PUCCH repetitive transmission count value can increase independently of whether a PUCCH transmission is performed on each time slot, based on the configured total PUCCH repetitive transmission count. If the UE is configured to perform frequency hopping between PUCCH transmissions on different time slots, the UE does not expect to configure frequency hopping within the time slot during PUCCH transmission. If frequency hopping is not configured for UE to perform PUCCH transmissions between different time slots and intra-slot frequency hopping is configured, the first and second PRB indices can also be applied equally within the time slot. If the number of uplink symbols that can be transmitted for PUCCH is less than the number indicated by nrofSymbols configured via higher-layer signaling, the UE may not transmit a PUCCH. Even if the UE fails to transmit a PUCCH in a time slot for some reason during a PUCCH retransmission, the UE can increment the PUCCH retransmission count.

[0248] In NR Release 17, the number of time slots for repeated transmission of each PUCCH resource in the extended PUCCH-ResourceExt of the higher-layer signaling PUCCH-Resource, which serves as a PUCCH resource, can be configured via the upper-layer signaling pucch-RepetitionNrofSlots-r17. If the upper-layer signaling pucch-RepetitionNrofSlots-r17 is configured, the corresponding PUCCH is configured, and the higher-layer signaling nrofSlots is also configured, the UE can determine the number of time slots for repeated transmission of the corresponding PUCCH through pucch-RepetitionNrofSlots-r17 and ignore the higher-layer signaling nrofSlots.

[0249] [PUCCH: Regarding transmit power]

[0250] Embodiments of this disclosure illustrate a method for a UE to configure the transmit power of the Physical Uplink Control Channel (PUCCH) and transmit uplink control information via the PUCCH in response to a power control command received from a base station. The transmit power of the UE for the Physical Uplink Control Channel (PUCCH), and the PUCCH power control adjustment state corresponding to the i-th transmission timing and closed-loop index l, can be determined by Equation 2, expressed in dBm. In Equation 2 below, when the UE supports multiple carrier frequencies in multiple cells, each parameter can be defined for the primary cell c, carrier frequency f, and bandwidth portion b, and can be distinguished by indices b, f, and c.

[0251] [Equation 2] [dBm] The maximum transmit power available to the UE during the i-th transmission is determined by the UE's power level, the base station activation parameters, and various internal parameters configured in the UE.

[0252] : It can be configured as and sum. This is a cell-specific value, configured via cell-specific high-rise signaling p0-nominal. If not configured, then... It can be 0 dBm. It is a UE-specific value, configured through the bandwidth portion b, carrier frequency f, and the p0-PUCCH-Value in the higher-layer signaling p0-PUCCH of the primary cell c. It can be greater than or equal to 0 and less than The value, It can represent The size of the set of values, which can be configured via the higher-level signaling maxNrofPUCCH-P0-PerSet. The set of values ​​can be configured via higher-level signaling p0-Set; if not configured, then... Can be considered = 0.

[0253] - Subcarrier spacing configuration value

[0254] - : can represent the amount of resources used in the bandwidth portion b, carrier frequency f, and primary cell c during the i-th PUCCH transmission (e.g., the number of resource blocks (RBs) on the frequency axis used for PUCCH transmission).

[0255] - : This represents the path loss between the base station and the UE. The UE uses reference signal (RS) resources notified by the base station. The path loss is calculated by the difference between the transmit power and the signal level of the reference signal received by the UE.

[0256] - When higher-layer signaling deltaF-PUCCH-f0 is configured for PUCCH format 0, the corresponding value can be used; when higher-layer signaling deltaF-PUCCH-f1 is configured for PUCCH format 1, the corresponding value can be used; when higher-layer signaling deltaF-PUCCH-f2 is configured for PUCCH format 2, the corresponding value can be used; when higher-layer signaling deltaF-PUCCH-f3 is configured for PUCCH format 3, the corresponding value can be used; when higher-layer signaling deltaF-PUCCH-f4 is configured for PUCCH format 4, the corresponding value can be used; when no higher-layer signaling is configured for any PUCCH format, 0 can be used.

[0257] - The PUCCH transmit power adjustment factor in the bandwidth portion b, carrier frequency f, and main cell c can be calculated using different methods based on the PUCCH format.

[0258] - This can represent the PUCCH power control adjustment status value corresponding to the i-th PUCCH transmission timing in the bandwidth portion b, carrier frequency f, and primary cell c, at the closed-loop index l. The closed-loop power adjustment for PUCCH transmission can be achieved using an accumulation method applying the accumulated value indicated by the TPC command.

[0259] PUCCH power control adjustment status It can be determined based on the bandwidth portion b, carrier frequency f, primary cell c, the timing of the i-th transmission, and closed-loop index l.

[0260] - : It can be the value indicated by the TPC command field included in DCI format 1_0, 1_1 or 1_2 at the time of the i-th PUCCH transmission corresponding to the closed-loop index l in bandwidth part b, carrier frequency f and primary cell c, or the value indicated by the TPC command field included in DCI format 2_2 transmitted together with the CRC scrambled with TPC-PUCCH-RNTI.

[0261] ○ If the UE is configured with higher-layer signaling twoPUCCH-PC-AdjustmentStates and PUCCH-SpatialRelationInfo, then the closed-loop index l can have a value of 0 or 1.

[0262] ○ If the UE is not configured with higher-layer signaling twoPUSCH-PC-AdjustmentStates or PUCCH-SpatialRelationInfo, the closed-loop index l can have a value of 0.

[0263] If the UE receives the TPC command value via the scheduling PDSCH and obtains it from the TPC command field included in the DCI format 1_0, 1_1, or 1_2 of the higher-layer signaling PUCCH-SpatialRelationInfo, then the UE can obtain the connection relationship between the configured closed-loop index l, the pucch-SpatialRelationInfoId value, and the closedLoopIndex value based on the index that can be configured via the higher-layer signaling p0-PUCCH-Id. If the UE receives a MAC-CE corresponding to pucch-SpatialRelationInfoId, then the UE can determine the closedLoopIndex value of the configured closed-loop index l based on the corresponding p0-PUCCH-Id index.

[0264] ○ If the UE obtains a single TPC command value from the TPC command field included in DCI format 2_2, which is sent together with the CRC scrambled with TPC-PUCCH-RNTI, then the UE can obtain the value of l based on the closed-loop index field included in DCI format 2_2.

[0265] - Bandwidth portion b, carrier frequency f, and PUCCH power control adjustment status corresponding to the i-th PUCCH transmission timing at closed-loop index l in the primary cell c. It can be calculated using Equation 3.

[0266] [Equation 3]

[0267] ○ As mentioned above, This can be the value indicated by the TPC command field included in DCI format 1_0, 1_1, or 1_2 corresponding to the m-th PUCCH transmission timing in the primary cell c, which includes the PDSCH reception and bandwidth portion b, carrier frequency f, and closed-loop index l; or the value indicated by the TPC command field included in DCI format 2_2, which is transmitted together with the CRC scrambled with TPC-PUCCH-RNTI. When TPC command accumulation is feasible, The corresponding value in dB can be determined based on the value indicated by the TPC command field included in DCI formats 1_0, 1_1, 1_2, or 2_2, as shown in Table 18. For example, if the value of the TPC command field is 0, then... It can have a value of -1 dB.

[0268] ○ It can be represented in relation to a specific set TPC command values ​​at all transmission times sum. Can represent a set The number of all elements included in it. This can represent the set of DCIs that include all TPC command values ​​used for the cumulative operation of the TPC command at the i-th PUCCH transmission timing. To determine... A start and end point can be defined in the time domain, and all DCIs received by the UE between the two points can be included. Element.

[0269] ● Used to determine The endpoint can be before the start symbol of the i-th PUCCH transmission. A dot with a symbol.

[0270] ● Used to determine The starting point can be before the start symbol of the (i-i0)th PUCCH transmission. The point of the symbol. A positive integer i0 can be determined as the symbol preceding the start symbol of the (i-i0)th PUCCH transmission. The time point of the symbol is earlier than that used to determine... The endpoint (before the start symbol of the i-th PUCCH transmission) The minimum value of (points with symbols).

[0271] ● For example, when used to determine The endpoint can be defined as sym(i), and the timing of the (i-i0)th PUCCH transmission is before the start symbol. The time point of a symbol can be defined as sym(i-i0). If sym(i) = sym(i-1) > sym(i-2) > sym(i-3), then i0 can be determined as 2.

[0272] [PUSCH: Regarding the transmission scheme]

[0273] Next, the PUSCH transmission scheduling scheme will be described. PUSCH transmissions can be dynamically scheduled by UL authorization within the DCI, or operated by configuring authorization type 1 or type 2. Dynamic scheduling instructions for PUSCH transmissions can be implemented using DCI format 0_0 or 0_1.

[0274] Configuration authorization type 1 PUSCH transports can be semi-statically configured via upper-layer signaling by receiving the configuredGrantConfig, which includes the rrc-ConfiguredUplinkGrant in Table 17, without receiving UL authorization within the DCI. Configuration authorization type 2 PUSCH transports can be semi-persistently scheduled by UL authorization within the DCI after receiving the configuredGrantConfig, which does not include the rrc-ConfiguredUplinkGrant in Table 16, via upper-layer signaling. If the PUSCH transport is configured via authorization, the parameters applied to the PUSCH transport are applied via the configuredGrantConfig (upper-layer signaling) in Table 16, except for the scaling of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and UCI-OnPUSCH provided by pusch-Config (upper-layer signaling) in Table 17. If a transformPrecoder is provided via configuredGrantConfig (upper-layer signaling) in Table 16, the UE will apply tp-pi2BPSK in pusch-Config in Table 17 to PUSCH transports via configured grant operations.

[0275] [Table 16]

[0276] Next, the PUSCH transmission method will be described. The DMRS antenna port used for PUSCH transmission is the same as the antenna port used for SRS transmission. PUSCH transmission can follow either a codebook-based transmission method or a non-codebook-based transmission method depending on whether the value of txConfig in pusch-Config (which is the upper-layer signaling) in Table 17 is "codebook" or "nonCodebook".

[0277] As described above, PUSCH transmissions can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically configured via configuration authorization. Once a scheduling instruction for a PUSCH transmission is received via DCI format 0_0, the UE performs beam configuration for the PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource with the smallest ID within the active uplink BWP in the serving cell, and the PUSCH transmission is based on a single antenna port. The UE does not expect PUSCH transmissions to be scheduled via DCI format 0_0 within a BWP that does not have a configured PUCCH resource including pucch-spatialRelationInfo, and the UE does not expect scheduling via DCI format 0_1. If the UE has not configured txConfig in the pusch-Config in Table 17, the UE does not expect scheduling via DCI format 0_1.

[0278] [Table 17]

[0279] Next, codebook-based PUSCH transmission will be described. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can be operated semi-statically via configuration authorization. If codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via configuration authorization, the UE determines the precoder for PUSCH transmission based on the SRS resource indicator (SRI), the transport precoding matrix indicator (TPMI), and the transport rank (PUSCH transport layer number).

[0280] In this scenario, the SRI can be provided via the SRS resource indicator in the DCI, or configured via the srs-ResourceIndicator as upper-layer signaling. When transmitting codebook-based PUSCH, the UE can be configured with at least one SRS resource, and at most two. When the UE is provided with an SRI via the DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to that SRI among the SRS resources transmitted before the PDCCH including that SRI. Furthermore, the TPMI and transport rank can be provided via the precoding information and layer number fields in the DCI, or configured via precodingAndNumberOfLayers as upper-layer signaling. The TPMI is used to indicate the precoder applied to the PUSCH transmission. If the UE is configured with one SRS resource, the TPMI is used to indicate the precoder applied to the configured SRS resource. If the UE is configured with multiple SRS resources, the TPMI is used to indicate the precoder to be applied to the SRS resource indicated by the SRI.

[0281] The precoder used for PUSCH transmission is selected from the uplink codebook, which has the same number of antenna ports as the nrofSRS-Ports value in the upper-layer signaling SRS-Config. In codebook-based PUSCH transmission, the UE determines the codebook subset based on TPMI and the codebookSubset in the upper-layer signaling pusch-Config. The codebookSubset in the upper-layer signaling pusch-Config can be configured as one of "fullyAndPartialAndNonCoherent", "partialAndNonCoherent", or "noncoherent" based on the UE capabilities reported by the UE to the base station. If the UE has reported 'partialAndNonCoherent' as a UE capability, the UE does not expect the value of the upper-layer signaling codebookSubset to be configured as 'fullyAndPartialAndNonCoherent'. Furthermore, if the UE has reported "noncoherent" as a UE capability, the UE does not expect the value of the upper-layer signaling codebookSubset to be configured as either "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent". If the nrofSRS-Ports in the upper-layer signaling SRS-ResourceSet indicates two SRS antenna ports, the UE does not expect the value of the upper-layer signaling codebookSubset to be configured as "partialAndNonCoherent".

[0282] A UE can be configured with an SRS resource set in which the usage value in the SRS-ResourceSet (used as upper-layer signaling) is configured as "codebook". Furthermore, an SRS resource can be indicated via an SRI within this corresponding SRS resource set. If multiple SRS resources are configured in the SRS resource set (in which the usage value in the SRS-ResourceSet (used as upper-layer signaling) is configured as "codebook"), the UE expects the nrofSRS-Ports value in the SRS-Resource (used as upper-layer signaling) to be configured identically for all SRS resources.

[0283] The UE sends one or more SRS resources from an SRS resource set (where the usage value is configured as "codebook") to the base station according to upper-layer signaling. The base station instructs the UE to perform PUSCH transmission using the transmission beam information of one SRS resource selected by the UE from the SRS resources sent by the UE. In this case, in codebook-based PUSCH transmission, the SRI is information used as an index for selecting an SRS resource and is included in the DCI. Furthermore, the base station may include information in the DCI indicating the TPMI and rank used by the UE for PUSCH transmission. The UE performs PUSCH transmission by using the SRS resource indicated by the SRI and applying the precoder indicated by the rank and TPMI based on the transmission beam indication of the corresponding SRS resource.

[0284] Next, non-codebook-based PUSCH transport will be described. Non-codebook-based PUSCH transport can be dynamically scheduled via DCI format 0_0 or 0_1, and can be operated semi-statically with configuration authorization. If at least one SRS resource is configured within an SRS resource set (where the usage value in the SRS-ResourceSet (higher-layer signaling) is "nonCodebook"), non-codebook-based PUSCH transport can be scheduled for the UE via DCI format 0_1.

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

[0286] If the resourceType configuration value in the SRS-ResourceSet (higher-layer signaling) is "aperiodic", the connected NZP CSI-RS is indicated by the SRS request as a field within DCI format 0_1 ​​or 1_1. If the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS can be indicated if the value of the SRS request (the field within DCI format 0_1 ​​or 1_1) is not "00". The corresponding DCI should not indicate cross-carrier or cross-BWP scheduling. Furthermore, if the SRS request value indicates the presence of an NZP CSI-RS, the NZP CSI-RS is located in the time slot used to transmit the PDCCH including the SRS request field. In this case, the TCI state configured for the scheduled subcarrier is not configured as QCL-TypeD.

[0287] If a periodic or semi-persistent SRS resource set is configured, the associated CSI-RS within the SRS-ResourceSet (higher-layer signaling) can indicate the connected NZP CSI-RS. Regarding non-codebook-based transports, the UE does not expect the higher-layer signaling spatialRelationInfo for SRS resources and the associated CSI-RS within the SRS-ResourceSet (higher-layer signaling) to be configured together.

[0288] If the UE is configured with multiple SRS resources, the UE can determine the precoder and transmission rank applied to PUSCH transmission based on the SRI indicated by the base station. In this case, the SRI can be indicated by the SRS resource indicator field in the DCI, or configured by the srs-ResourceIndicator as upper-layer signaling. Similar to the codebook-based PUSCH transmission described above, if the UE is provided with an SRI via the DCI, the SRS resource corresponding to that SRI is indicated by the SRS resource in the SRS resources transmitted before the PDCCH including the SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously in the same symbol within an SRS resource set, as well as the maximum number of SRS resources, is determined by the UE capabilities reported by the UE to the base station. In this case, the SRS resources transmitted simultaneously by the UE occupy the same RB. The UE configures one SRS port for each SRS resource. Only one SRS resource set with the usage value set to "nonCodebook" can be configured in the SRS-ResourceSet used for upper-layer signaling, and a maximum of four SRS resources can be configured for non-codebook-based PUSCH transmission.

[0289] The base station sends an NZP-CSI-RS connected to the SRS resource set to the UE, and the UE calculates a precoder for transmitting one or more SRS resources within the corresponding SRS resource set based on the measurement results received when the corresponding NZP-CSI-RS is received. When the UE transmits one or more SRS resources in an SRS resource set where usage is configured as "nonCodebook", the UE applies the calculated precoder, and the base station selects one or more SRS resources from the received one or more SRS resources. In this case, the SRI indication in the nonCodebook-based PUSCH transmission can represent an index of a combination of one or more SRS resources, and the SRI is included in the DCI. In this case, the number of SRS resources indicated by the SRI sent by the base station can be the same as the number of transmission layers of the PUSCH, and the UE transmits the PUSCH by applying the precoder used for SRS resource transmission to each layer.

[0290] [PUSCH: Regarding transmit power]

[0291] Embodiments of this disclosure illustrate a method for a UE to configure the transmit power of the Physical Uplink Shared Channel (PUSCH) and transmit uplink data via the PUSCH in response to a power control command received from a base station. The UE's transmit power for the PUSCH, and the PUSCH power control adjustment state corresponding to the i-th transmission timing, parameter set configuration index j, and closed-loop index l, can be determined by Equation 4, expressed in dBm. In Equation 4 below, when the UE supports multiple carrier frequencies in multiple cells, each parameter can be defined for each cell c, carrier frequency f, and bandwidth portion b, and can be distinguished by indices b, f, and c.

[0292] [Equation 4] The maximum transmit power available to the UE during the i-th transmission is determined by the UE's power level, the base station activation parameters, and various internal parameters configured in the UE.

[0293] : Configured as and sum. It is a value configured for the UE through cell-specific high-rise signaling. This is a value configured through UE-specific higher-layer signaling. Here, j=0 indicates the PUSCH used to send msg3, j=1 indicates the configured authorized PUSCH, and j is one of {2, ..., J-1}, representing the authorized PUSCH.

[0294] - Subcarrier spacing configuration value

[0295] - : can represent the amount of resources used during the i-th PUSCH transmission (e.g., the number of resource blocks (RBs) on the frequency axis used for PUSCH transmission).

[0296] - : This represents the value used to compensate for path loss, which can be determined through higher-level configuration and SRS resource indicator (SRI) (in the case of dynamically authorized PUSCH).

[0297] - : This represents the path loss between the base station and the UE. The UE receives the reference signal (RS) resources from the base station. The path loss is calculated from the difference between the transmit power and the signal level of the reference signal received by the UE. This indicates that the UE is indexed by the reference signal. The downlink path loss is estimated using the reference signal, and the reference signal index is used for estimation. It can be determined by the UE through higher-level configuration and SRI (in the case of dynamically authorized PUSCH or configuredGrantConfig-based configuration authorized PUSCH (type 2 configuration authorized PUSCH) without higher-level configuration rrc-ConfiguredUplinkGrant) or higher-level configuration.

[0298] - : Represents a value determined based on the modulation and coding scheme (MCS) and format (transmission format (TF), e.g., whether it includes UL-SCH or CSI) of the information transmitted via PUSCH.

[0299] - : Represents the closed-loop power control adjustment value, which is the value of the closed-loop index l used for PUSCH, and can be determined by higher-layer configuration and SRI. Closed-loop power adjustment for PUSCH transmission can be supported by an accumulation method applying the accumulated value indicated by the TPC command or an absolute method directly applying the value indicated by the TPC command, depending on whether the higher-layer parameter tpc-Accumulation is configured. When the higher-layer parameter tpc-Accumulation is configured to be disabled, closed-loop power adjustment for PUSCH transmission is performed using the absolute method; when tpc-Accumulation is not configured, closed-loop power adjustment for PUSCH transmission is performed using the accumulation method.

[0300] PUSCH power control adjustment status It can be determined based on the bandwidth portion b, carrier frequency f, cell c, the timing of the i-th transmission, and the closed-loop index l.

[0301] - : It can be the value indicated by the TPC command field included in DCI format 0_0, 0_1 or 0_2 corresponding to the timing of the i-th PUSCH transmission in bandwidth portion b, carrier frequency f and cell c corresponding to the closed-loop index l, or the value indicated by the TPC command field included in DCI format 2_2 which is transmitted together with the CRC scrambled with TPC-PUSCH-RNTI.

[0302] ○ If the UE is configured with higher-layer signaling twoPUSCH-PC-AdjustmentStates, the closed-loop index l can have a value of 0 or 1.

[0303] ○ If the UE is not configured with higher-layer signaling twoPUSCH-PC-AdjustmentStates, or if the UE is scheduled for PUSCH transmission based on RAR UL authorization, the closed-loop index l can have a value of 0.

[0304] ● If the UE is configured with the higher-layer signaling ConfiguredGrantConfig and performs PUSCH transmission or retransmission in response to it, the closed-loop index l can follow the value of the higher-layer signaling powerControlLoopToUse.

[0305] ● If the UE is configured with higher-layer signaling SRI-PUSCH-PowerControl, the UE can obtain the connection relationship between the value indicated by the SRS Resource Indicator (SRI) field in the DCI format transmitted by the scheduling PUSCH and the closed-loop index l configured by the higher-layer signaling sri-PUSCH-ClosedLoopIndex, and determine the closed-loop index l based on the value indicated by the SRI field in the DCI format based on this connection relationship.

[0306] ● If the UE is scheduled to send PUSCH based on a DCI format that does not include the SRI field, or if the UE is not configured with higher-layer signaling SRI-PUSCH-PowerControl, the UE can consider the closed-loop index l to be 0.

[0307] ● If the UE receives the TPC command value via the TPC command field included in DCI format 2_2, which is sent along with the CRC scrambled with TPC-PUSCH-RNTI, the closed-loop index l can be indicated by the closed-loop index field included in DCI format 2_2.

[0308] - If the UE is not configured with higher-layer signaling tpc-Accumulation, i.e., if the UE may perform TPC command accumulation, then the PUSCH power control adjustment state corresponding to the i-th PUSCH transmission timing in the bandwidth portion b, carrier frequency f, and cell c, is... It can be calculated using Equation 5.

[0309] [Equation 5]

[0310] ○ As mentioned above, This can be the value indicated by the TPC command field included in DCI format 0_0, 0_1, or 0_2, which corresponds to the m-th PUSCH transmission timing in bandwidth portion b, carrier frequency f, and cell c, and closes-loop index l; or the value indicated by the TPC command field included in DCI format 2_2, which is transmitted along with a CRC scrambled with TPC-PUSCH-RNTI. This applies when TPC command accumulation is feasible. The TPC command field, as indicated by the DCI format 0_0, 0_1, 0_2, or 2_2, can have a corresponding value in dB, as shown in Table 18. For example, if the value of the TPC command field is 0, then... It can have a value of -1 dB.

[0311] ○ It can be represented in relation to a specific set TPC command values ​​at all transmission times sum. Can represent a set The number of all elements included in it. This can represent the set of DCIs that include all TPC command values ​​used for the cumulative operation of the TPC command at the i-th PUSCH transmission timing. To determine... A start and end point can be defined in the time domain, and all DCIs received by the UE between the two points can be included. Element.

[0312] ● Used to determine The endpoint can be before the start symbol of the i-th PUSCH transmission. A dot with a symbol.

[0313] ● Used to determine The starting point can be the ( ) The timing of the PUSCH transmission before the start symbol A point with a symbol. A positive integer. It can be determined such that the ( The timing of the PUSCH transmission before the start symbol The time point of the symbol is earlier than that used to determine... The endpoint (before the start symbol of the i-th PUSCH transmission) The minimum value of (points with symbols).

[0314] ● For example, when used to determine The endpoint can be defined as sym(i), and the (i)th endpoint can be defined as sym(i). The timing of the PUSCH transmission before the start symbol The time point of a symbol can be defined as sym( If sym(i) = sym(i-1) > sym(i-2) > sym(i-3), then i0 can be determined as 2.

[0315] - If the UE is configured with higher-layer signaling tpc-Accumulation, i.e., if the UE cannot perform TPC command accumulation, then the PUSCH power control adjustment state corresponding to the i-th PUSCH transmission timing in the bandwidth portion b, carrier frequency f, and cell c, is... It can be calculated using Equation 6.

[0316] [Equation 6]

[0317] ○ As mentioned above, This can be the value indicated by the TPC command field included in DCI format 0_0, 0_1, or 0_2, which corresponds to the timing of the i-th PUSCH transmission in bandwidth portion b, carrier frequency f, and cell c, corresponding to the closed-loop index l; or the value indicated by the TPC command field included in DCI format 2_2, which is transmitted together with the CRC scrambled with TPC-PUSCH-RNTI. When TPC command accumulation is not feasible... The TPC command field, as indicated by the DCI format 0_0, 0_1, 0_2, or 2_2, can have a corresponding value in dB, as shown in Table 18. For example, if the value of the TPC command field is 0, then... It can have a value of -4 dB.

[0318] [Table 18]

[0319] [About SRS]

[0320] Next, an uplink channel estimation method utilizing the UE's Sounding Reference Signal (SRS) transmission will be described. The base station can configure at least one SRS configuration for each uplink base station (BWP) to transmit configuration information for SRS transmission to the UE, and can also configure at least one SRS resource set for each SRS configuration. As an example, the base station and the UE can exchange higher-layer signaling information as follows to transmit information about the SRS resource set.

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

[0322] - srs-ResourceIdList: A collection of SRS resource indexes referenced by an SRS resource set.

[0323] - resourceType: The time-domain transport configuration of the SRS resource referenced by the SRS resource set, and can be configured as one of "periodic", "semi-persistent", and "aperiodic". If configured as "periodic" or "semi-persistent", associated CSI-RS information can be provided based on the usage location of the SRS resource set. If configured as "aperiodic", an aperiodic SRS resource trigger list and slot offset information can be provided, and associated CSI-RS information can be provided based on the usage location of the SRS resource set.

[0324] - usage: Configuration about where the SRS resources referenced by the SRS resource set are used, and can be configured as one of "beamManagement", "codebook", "nonCodebook" and "antennaSwitching".

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

[0326] The UE can understand that the SRS resources included in the set of SRS resource indexes referenced by the SRS resource set follow the information configured for the SRS resource set.

[0327] Furthermore, the base station and UE can send / receive upper-layer signaling information to transmit separate configuration information regarding SRS resources. As an example, the separate configuration information regarding SRS resources may include intra-slot time-frequency domain mapping information for the SRS resources, and this may include intra-slot or inter-slot frequency hopping information for the SRS resources. Additionally, the separate configuration information regarding SRS resources may include the time-domain transmission configuration of the SRS resources, and may be configured as one of "periodic," "semi-persistent," and "aperiodic." The time-domain transmission configuration of the SRS resources may be restricted to having the same time-domain transmission configuration as the set of SRS resources that includes the SRS resources. If the time-domain transmission configuration of the SRS resources is configured as "periodic" or "semi-persistent," the time-domain transmission configuration may further include the SRS resource transmission period and slot offset (e.g., periodicityAndOffset).

[0328] The base station can activate or deactivate the UE's SRS transmission via higher-layer signaling or L1 signaling (e.g., DCI), including RRC signaling or MAC CE signaling. For example, the base station can activate or deactivate the UE's periodic SRS transmission via higher-layer signaling. The base station can indicate the activation of an SRS resource set with resourceType configured as "periodic" via higher-layer signaling, and the UE can transmit SRS resources referenced by the activated SRS resource set. The intra-slot time-frequency domain resource mapping of the transmitted SRS resources follows the resource mapping information configured for the SRS resources, and the slot mapping, including the transmission period and slot offset, follows periodicityAndOffset configured for the SRS resources. Furthermore, the spatial transmission filter applied to the transmitted SRS resources can refer to spatial relationship information configured for the SRS resources, or it can refer to associated CSI-RS information configured for the SRS resource set including the SRS resources. The UE can transmit SRS resources within the uplink BWP activated with respect to the periodic SRS resources activated via higher-layer signaling.

[0329] For example, a base station can activate or deactivate a UE's semi-persistent SRS transmission via higher-layer signaling. The base station can indicate 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 SRS resource sets with resourceType configured as "semi-persistent". The intra-slot time-frequency domain resource mapping of the transmitted SRS resources follows the resource mapping information configured for the SRS resources, and the slot mapping, including transmission period and slot offset, follows periodicityAndOffset configured for the SRS resources. Furthermore, the spatial transmission filter applied to the transmitted SRS resources can refer to the spatial relation information configured for the SRS resources, or it can refer to the associated CSI-RS information configured for the SRS resource set including the SRS resource. If the SRS resources are configured with spatial relation information, the spatial transmission filter can be determined by referring to the configuration information about the spatial relation information transmitted via the MAC CE signaling activating the semi-persistent SRS transmission, rather than following the same information. The UE can transmit SRS resources within the uplink BWP that is activated with respect to semi-persistent SRS resources activated via higher-layer signaling.

[0330] For example, a base station can trigger aperiodic SRS transmissions by a UE via a DCI. The base station can indicate one of the aperiodic SRS triggers (Aperiodic SRS-ResourceTrigger) via the SRS Request field of the DCI. The UE understands that the SRS resource set, including the one indicated in the aperiodic SRS resource trigger list via the DCI, has been triggered in the SRS resource set configuration information. The UE can then transmit the SRS resource referenced by the triggered SRS resource set. The time-frequency domain resource mapping within the time slot of the transmitted SRS resource follows the resource mapping information configured for the SRS resource. Furthermore, the time slot mapping of the transmitted SRS resource can be determined by the time slot offset between the SRS resource and the PDCCH including the DCI, and this can be referenced to values ​​included in the time slot offset set configured for the SRS resource set. Specifically, as the time slot offset between the SRS resource and the PDCCH including the DCI, the value indicated by the time-domain resource allocation field of the DCI among the offset values ​​included in the time slot offset set configured for the SRS resource set can be applied. Furthermore, the spatial transmission filter applied to the transmitted SRS resource can refer to the spatial relationship information configured for the SRS resource, or it can refer to the associated CSI-RS information configured for the SRS resource set including the SRS resource. The UE can transmit the SRS resource within the uplink BWP activated with respect to the aperiodic SRS resource triggered by DCI.

[0331] If the base station triggers aperiodic SRS transmissions by the UE via DCI, a minimum time interval may be required between the transmitted SRS and the PDCCH containing the DCI that triggered the aperiodic SRS transmission in order for the UE to transmit SRS by applying configuration information about SRS resources. The time interval for the UE to perform SRS transmissions 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 transmitted SRS resource mapped to the transmitted SRS resource. The minimum time interval can be determined with reference to the PUSCH preparation time required by the UE to prepare for PUSCH transmissions. Furthermore, the minimum time interval can have different values ​​depending on the usage context of the SRS resource set including the transmitted SRS resources. For example, the minimum time interval can be determined as N² symbols, considering the UE's PUSCH preparation time and the UE's processing capabilities. Furthermore, if the usage location of the SRS resource set, including the transmitted SRS resources, is configured as "codebook" or "antennaSwitching," the minimum time interval can be determined to be N² symbols. If the usage location of the SRS resource set is configured as "nonCodebook" or "beamManagement," the minimum time interval can be determined to be N²+14 symbols. If the time interval of the aperiodic SRS transmission is greater than or equal to the minimum time interval, the UE can transmit aperiodic SRS. If the time interval of the aperiodic SRS transmission is less than the minimum time interval, the UE can ignore the DCI that triggers the aperiodic SRS.

[0332] [Table 19]

[0333] The configuration information spatialRelationInfo in Table 19 above can be applied to the beams used for SRS transmission with reference to a reference signal and corresponding to the beam information of that reference signal. For example, the configuration of spatialRelationInfo may include the information in Table 20 below.

[0334] [Table 20]

[0335] Referring to the spatialRelationInfo configuration above, the synchronization signal / physical broadcast channel (SS / PBCH) block (or synchronization signal block (SSB)) index, CSI-RS index, or SRS index can be configured as the index of a reference signal to be referenced, so as to use the beam information of a specific reference signal. The higher-layer signaling referenceSignal corresponds to the configuration information indicating which reference signal's beam information should be referenced for the corresponding SRS transmission. ssb-Index refers to the SS / PBCH block index, csi-RS-Index refers to the CSI-RS index, and srs refers to the SRS index. If the upper-layer signaling referenceSignal is configured to have a value of "ssb-Index", the UE can apply the receive beam used to receive the SS / PBCH block corresponding to ssb-Index as the transmission beam corresponding to the SRS transmission. If the upper-layer signaling referenceSignal is configured to have a value of "csi-RS-Index", the UE can apply the receive beam used to receive CSI-RS corresponding to the csi-RS-Index as the transmit beam corresponding to the SRS transmission. If the upper-layer signaling referenceSignal is configured to have a value of "srs", the UE can apply the transmit beam used to transmit SRS corresponding to the SRS as the transmit beam corresponding to the SRS transmission.

[0336] [SRS: Regarding transmit power]

[0337] Embodiments of this disclosure illustrate a method by which a UE configures the transmit power of a sounding reference signal (SRS) in response to a power control command received from a base station and performs transmission via the SRS. The UE's transmit power (PSRS) for the SRS, and the SRS power control adjustment state corresponding to the i-th transmission timing and closed-loop index l, can be determined by Equation 7, expressed in dBm. In Equation 7 below, when the UE supports multiple carrier frequencies in multiple cells, each parameter can be defined for each cell c, carrier frequency f, and bandwidth portion b, and can be distinguished by indices b, f, and c.

[0338] [Equation 7]

[0339] - The maximum transmit power available to the UE during the i-th transmission is determined by the UE's power level, the base station activation parameters, and various internal parameters configured in the UE.

[0340] - The bandwidth portion b, carrier frequency f, and cell c can be configured via higher-layer signaling p0, and the SRS resource set... It can be configured via higher-level signaling SRS-ResourceSet and SRS-ResourceSetId.

[0341] - Subcarrier spacing configuration value

[0342] - : can represent the amount of resources used during the i-th SRS transmission (e.g., the number of resource blocks (RBs) on the frequency axis used for SRS transmission).

[0343] - : The bandwidth portion b, carrier frequency f, and cell c can be configured via higher-layer signaling alpha, and the SRS resource set It can be configured via higher-level signaling SRS-ResourceSet and SRS-ResourceSetId.

[0344] - Path loss refers to the path loss between the base station and the UE. The UE uses reference signal (RS) resources transmitted by the base station. The path loss is calculated by the difference between the transmit power and the signal level of the reference signal received by the UE.

[0345] - : can represent the SRS power control adjustment state value corresponding to the i-th SRS transmission timing in the bandwidth portion b, carrier frequency f, and main cell c, which is the closed-loop index l.

[0346] The SRS power control adjustment state can be determined based on the bandwidth portion b, carrier frequency f, cell c, and the timing of the i-th transmission.

[0347] - If the UE is configured via higher-layer signaling srs-PowerControlAdjustmentStates to have the same power control adjustment state value for SRS transmissions and PUSCH transmissions, then the SRS power control adjustment state can be represented by Equation 8, and in Equation 8, This can indicate the current PUSCH power control adjustment status. In this case, The values ​​can be calculated using the various methods described in Embodiment 1 above, and the calculated values ​​can be applied to... .

[0348] [Equation 8]

[0349] - If the UE is not configured for PUSCH transmission in bandwidth portion b, carrier frequency f, and cell c, or is configured via higher-layer signaling srs-PowerControlAdjustmentStates to have separate power control adjustment state values ​​for SRS transmission and PUSCH transmission and is not configured with higher-layer signaling tpc-Accumulation, then the SRS power control adjustment state can be represented independently of closed-loop l by Equation 9.

[0350] [Equation 9]

[0351] - : This can be a value indicated by the TPC command field included in DCI format 2_3, which can follow Table 17.

[0352] ○ It can be represented in relation to a specific set TPC command values ​​at all transmission times sum. Can represent a set The number of all elements included in it. This can represent the set of DCIs that include all TPC command values ​​used to perform the TPC command accumulation operation for the i-th PUSCH transmission timing. To determine... A start and end point can be defined in the time domain, and all DCIs received by the UE between the two points can be included. Element.

[0353] ● Used to determine The endpoint can be before the start symbol of the i-th SRS transmission timing. A dot with a symbol.

[0354] ● Used to determine The starting point can be before the start symbol of the (i-i0)th SRS transmission timing. The point of the symbol. A positive integer i0 can be determined such that the point is before the start symbol of the (i-i0)th SRS transmission timing. The time point of the symbol is earlier than that used to determine... The endpoint (before the start symbol of the i-th SRS transmission timing) The minimum value of (points with symbols).

[0355] ● For example, when used to determine The endpoint can be defined as sym(i), and is defined before the start symbol of the (i-i0)th SRS transmission. The time point of a symbol can be defined as sym(i-i0). If sym(i) = sym(i-1) > sym(i-2) > sym(i-3), then i0 can be determined as 2.

[0356] - If the UE is not configured for PUSCH transmission in bandwidth portion b, carrier frequency f, and cell c, or is configured via higher-layer signaling srs-PowerControlAdjustmentStates to have separate power control adjustment state values ​​for SRS transmission and PUSCH transmission and is configured with higher-layer signaling tpc-Accumulation (i.e., TPC command accumulation operation is disabled and absolute TPC command values ​​are applicable), then the SRS power control adjustment state can be represented independently of closed-loop l by Equation 10.

[0357] [Equation 10]

[0358] ○ As mentioned above, This can be the value indicated by the TPC command field included in DCI format 2_3 in bandwidth portion b, carrier frequency f, and cell c, which can follow Table 18. For example, if the value of the TPC command field is 0, then... It can have a value of -4 dB.

[0359] [Regarding UE Capability Report]

[0360] In LTE and NR, a UE can perform a process of reporting its supported capabilities to the corresponding base station while connecting to the serving base station. In the following description, this process will be referred to as UE capability reporting.

[0361] A base station can send a UE capability query message to a connected UE to request capability reports. This message can include UE capability requests for each Radio Access Technology (RAT) type of the base station. RAT type-specific requests can include information such as supported frequency band combinations. Furthermore, in the case of a UE capability query message, UE capabilities for multiple RAT types can be requested through a single RRC message container sent by the base station, or the base station can send a UE capability query message including multiple UE capability requests for each RAT type. That is, capability queries can be repeated multiple times in a single message, and the UE can configure corresponding UE capability information messages and report the same number of times. In next-generation mobile communication systems, UE capability requests can be made for multi-RAT dual connectivity (MR-DC) (such as NR, LTE, E-UTRA-NR dual connectivity (EN-DC)). UE capability query messages are typically initially sent after the UE connects to the base station, but can be requested under any conditions if the base station requires it.

[0362] In the above steps, once the UE capability report request is received from the base station, the UE configures its capabilities based on the frequency band information and RAT type requested by the base station. The following summarizes the methods for configuring UE capabilities in the NR system.

[0363] 1. If the UE receives a list of LTE and / or NR frequency bands from the base station in the UE capability request, the UE constructs a frequency band combination (BC) for EN-DC and NR Independent (SA). That is, the UE configures a candidate list of BCs for EN-DC and NR SA based on the frequency bands received from the base station at the time of request via FreqBandList. Furthermore, the frequency bands are prioritized according to the order described in the FreqBandList.

[0364] 2. If the base station sets the “eutra-nr-only” flag or the “eutra” flag and requests a UE capability report, the UE removes all content related to NR SA BC from the configured BC candidate list. This operation can only occur when the LTE base station (eNB) requests “eutra” capability.

[0365] 3. Next, the UE removes the fallback BC from the BC candidate list configured in the above steps. As used herein, a fallback BC refers to a BC obtained by removing the band corresponding to at least one SCell from a specific BC, and since the BC prior to removing the band corresponding to at least one SCell can already cover the fallback BC, the same can be omitted. This step also applies to MR-DC, i.e., LTE bands also apply. The BCs remaining after the above steps constitute the final "candidate BC list".

[0366] 4. The UE can select a BC suitable for the requested RAT type from the final "Candidate BC List" and choose the BC to report. In this step, the UE configures the supportedBandCombinationList in a defined order. That is, the UE configures the BCs to be reported and UE capabilities according to the pre-configured rat-Type order (NR -> EUTRA-NR -> EUTRA). Furthermore, the UE configures the featureSetCombination for the configured supportedBandCombinationList and configures a list of "Candidate Feature Set Combinations" from the candidate BC list, removing fallback BCs (including capabilities of the same or lower level) from the candidate BC list. The "Candidate Feature Set Combinations" can include all feature set combinations for NR BCs and EUTRA-NR BCs, and can be obtained from feature set combinations in the UE-NR-Capabilities container and the UE-MRDC-Capabilities container.

[0367] 5. If the requested RAT type is eutra-nr and has an impact, featureSetCombinations are included in both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, NR feature sets are only included in UE-NR-Capabilities.

[0368] After configuring UE capabilities, the UE transmits a UE capability information message, including the UE capabilities, to the base station. Based on the UE capabilities received from the UE, the base station performs scheduling and transmit / receive management suitable for the UE.

[0369] [About NC-JT]

[0370] According to embodiments of this disclosure, in order to receive PDSCH from multiple TRPs, the UE may use noncoherent joint transmission (NC-JT).

[0371] Unlike traditional systems, 5G wireless communication systems can support services with very short transmission latency, services requiring high connection density, and services requiring high transmission rates. In wireless communication networks that include multiple cells, transmit / receive points (TRPs), or beams, cooperative communication (coordinated transmission) between cells, TRPs, and / or beams can meet various service requirements by enhancing the strength of the signal received by the UE or effectively performing interference control between cells, TRPs, and / or beams.

[0372] Joint transmission (JT) is a representative transmission technology for the aforementioned cooperative communication. It refers to a technique that increases the strength or throughput of the signal received by a UE by transmitting signals to a UE via multiple different cells, TRPs, and / or beams. In this case, the channels between the UE and each cell, TRP, and / or beam may have significantly different characteristics. In particular, noncoherent joint transmission (NC-JT) that supports non-interference coding between cells, TRPs, and / or beams may require separate precoding, MCS, resource allocation, TCI indication, etc., based on the channel characteristics of each link between the UE and each cell, TRP, and / or beam.

[0373] The aforementioned NC-JT transmission can be applied to at least one of the downlink data channel (PDSCH), downlink control channel (PDCCH), uplink data channel (PUSCH), and uplink control channel (PUCCH). During PDSCH transmission, transmission information such as precoding, MCS, resource allocation, and TCI can be indicated via DL DCI, and for NC-JT, this should be indicated independently for each cell, TRP, and / or beam. This becomes a major factor increasing the payload required for DL ​​DCI transmission, which may adversely affect the reception performance of the PDCCH transmitting DCI. Therefore, to support JT with PDSCH, a careful design is needed to balance the DCI information volume with the control information reception performance.

[0374] Figure 10 An example of antenna port configuration and resource allocation for PDSCH transmission using cooperative communication in a wireless communication system according to an embodiment of this disclosure is shown.

[0375] refer to Figure 10 Examples of PDSCH transmissions are described for each scheme of Joint Transmission (JT), and an example of allocating radio resources for each TRP is shown.

[0376] refer to Figure 10 Example 1000 is shown that supports coherent joint transmission (C-JT) with phase interference coding between individual cells, TRPs and / or beams.

[0377] In the C-JT scenario, TRP A 1005 and TRP B 1010 can send a single data transmission (PDSCH) to UE 1015, and multiple TRPs can perform joint precoding. This likely means that in order for TRP A 1005 and TRP B 1010 to send the same PDSCH, the DMRS must be transmitted through the same DMRS port. For example, TRP A 1005 and TRP B 1010 can each send DMRS to the UE through DMRS port A and DMRS port B, respectively. In this case, the UE can receive a DCI to receive a PDSCH based on the DMRS demodulated through DMRS port A and DMRS port B.

[0378] Figure 10 Example 1020 is shown for noncoherent joint transmission (NC-JT) that supports non-interference coding between individual cells, TRPs, and / or beams for PDSCH transmission.

[0379] In the NC-JT scenario, PDSCH can be transmitted to UE 1035 by cell, by TPR, and / or by beam, and individual precoding can be applied to each PDSCH. Different cells, TPRs, and / or beams can send different PDSCHs or different PDSCH layers to the UE, thereby improving throughput compared to single-cell, TPR, and / or beam transmission. Furthermore, different cells, TPRs, and / or beams can repeatedly transmit the same PDSCH to the UE, thereby improving reliability compared to single-cell, TPR, and / or beam transmission. For ease of description, cells, TPRs, and / or beams are collectively referred to as TRPs.

[0380] In this case, various wireless resource allocations can be considered, such as the case where multiple TRPs use the same frequency and time resources for PDSCH transmission 1040, the case where multiple TRPs use completely non-overlapping frequency and time resources 1045, and the case where multiple TRPs use partially overlapping frequency and time resources 1050.

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

[0382] Figure 11 An example of downlink control information (DCI) configuration for NC-JT (where each TRP sends different PDSCH or different PDSCH layers to the UE) in a wireless communication system according to an embodiment of the present disclosure is shown.

[0383] refer to Figure 11Case #1 1100 is an example where (N-1) different PDSCHs are transmitted on (N-1) additional TRPs (TRP #1 to TRP #(N-1)) besides the serving TRP (TRP #0) used for single PDSCH transmission. In this case, the control information for the PDSCHs transmitted from these (N-1) additional TRPs is transmitted independently relative to the control information for the PDSCHs transmitted from the serving TRP. That is, the UE can obtain the control information for the PDSCHs transmitted from different TRPs (TRP #0 to TRP #N-1) via independent DCIs (DCI #0 to DCI #(N-1)). The formats of the independent DCIs can be the same or different from each other, and the payloads of the DCIs can also be the same or different from each other. In Case #1 above, the freedom of control or allocation for each PDSCH can be fully guaranteed; however, if each DCI is transmitted from a different TRP, coverage differences may occur for each DCI, thus potentially degrading reception performance.

[0384] Case #2 1105 is a case in which (N-1) different PDSCHs are sent on (N-1) additional TRPs (TRP #1 to TRP #(N-1)) other than the serving TRP (TRP #0) used for a single PDSCH transmission, and control information (DCI) for the PDSCHs of the (N-1) additional TRPs is sent, and each DCI depends on an example of the control information for the PDSCH sent from the serving TRP.

[0385] For example, the control information DCI#0 for PDSCH sent from the serving TRP (TRP#0) includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. However, the shortened DCI (hereinafter, sDCI) (sDCI#0 to sDCI#N-2) for control information of PDSCH sent from the cooperating TRPs (TRP#1 to TRP#(N-1)) may only include some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. Therefore, in the case of sDCI used to send control information of PDSCH sent from the cooperating TRP, its payload is smaller than that of the normal DCI (nDCI) used to send control information of PDSCH sent from the serving TRP, and therefore can include reserved bits compared to nDCI.

[0386] In scenario #2 above, the control or allocation of each PDSCH degree of freedom may be limited by the content of the information elements included in the sDCI. However, since the reception performance of the sDCI is better than that of the nDCI, the probability of coverage differences occurring in each DCI can be reduced.

[0387] Case #3 1110 is an example of sending a control message for the PDSCH of the (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) for a single PDSCH transmission, and the DCI depends on the control message for the PDSCH sent from the serving TRP.

[0388] For example, DCI#0, which is the control information for PDSCH transmitted from the serving TRP (TRP#0), includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. For control information for PDSCH transmitted from cooperating TRPs (TRP#1 to TRP#N-1), it may only collect some of the information elements from DCI format 1_0, DCI format 1_1, and DCI format 1_2 and transmit them in a single "auxiliary" DCI (sDCI). For example, the sDCI may include at least one HARQ-related piece of information, such as the frequency domain resource allocation, time domain resource allocation, and MCS of the cooperating TRP. Furthermore, information not included in the sDCI, such as the bandwidth portion (BWP) indicator or carrier indicator, may follow the serving TRP's DCI (DCI#0, normal DCI, or nDCI).

[0389] In case #3 1110, the control or allocation freedom of each PDSCH may be limited depending on the content of the information elements included in the sDCI, but the sDCI reception performance can be adjusted, and the DCI blind decoding complexity of the UE can be reduced compared to case #1 1100 or case #2 1105.

[0390] Case #4 1115 is an example where (N-1) additional TRPs (TRP#1 to TRP#(N-1)) transmit different (N-1) PDSCHs besides the serving TRP (TRP#0) used for single PDSCH transmission. In this case, the control information for the PDSCHs transmitted from these (N-1) additional TRPs is transmitted in the same DCI (long DCI) as the DCI used to transmit the control information for the PDSCHs transmitted from the serving TRP. That is, the UE can obtain the control information for the PDSCHs transmitted from different TRPs (TRP#0 to TRP#N-1) via a single DCI. In Case #4 1115, the UE's blind decoding complexity of the DCI may not increase, but the number of cooperating TRPs is limited due to the long DCI payload limitation, thus potentially reducing the freedom of PDSCH control or allocation.

[0391] In the following description and embodiments, sDCI may refer to various auxiliary DCIs, such as shortened DCIs, auxiliary DCIs, or normal DCIs including PDSCH control information sent in the cooperative TRP (DCI formats 1_0 and 1_1 above), and unless specific limitations are mentioned, the corresponding descriptions may be similarly applied to various auxiliary DCIs.

[0392] In the following description and embodiments, cases #11100, #2 1105, and #3 1110 that use one or more DCIs (or PDCCHs) to support NC-JT can be classified as multi-PDCCH-based NC-JT, and case #4 1115 that uses a single DCI (or PDCCH) to support NC-JT can be classified as single-PDCCH-based NC-JT. In multi-PDCCH-based PDSCH transmission, the CORESET of the DCI for the scheduling service TRP (TRP#0) and the CORESET of the DCI for the scheduling cooperation TRPs (TRP#1 to TRP#N-1) can be distinguished. Methods for distinguishing CORESETs may include a method of distinction based on higher-layer indicators for each CORESET and a method of distinction based on beam configuration for each CORESET. Furthermore, in single-PDCCH-based NC-JT, a single DCI schedules a single PDSCH with multiple layers, rather than scheduling multiple PDSCHs, and multiple layers can be transmitted from multiple TRPs. In this context, the connection between a layer and the TRP that transmits that layer can be indicated by a Transmission Configuration Indicator (TCI) for that layer. In embodiments of this disclosure, the term "cooperative TRP" can be replaced with various terms in practical application, such as "cooperative panel" or "cooperative beam."

[0393] In the embodiments of this disclosure, "the case of applying NC-JT" can be interpreted differently depending on the circumstances as "the case where the UE simultaneously receives one or more PDSCHs in a BWP", "the case where the UE simultaneously receives PDSCHs in a BWP based on two or more Transport Configuration Indicators (TCIs)", and "the case where the PDSCHs received by the UE are associated with one or more DMRS port groups", but for the sake of convenience, it is used by way of expression.

[0394] As used in this article, the wireless protocol architecture for NC-JT can be used in various ways depending on the TRP deployment scenario. For example, if the return latency between cooperating TRPs is small or non-existent, it can be similar to... Figure 4The attached figure, labeled "S10," uses a MAC layer multiplexing-based architecture (similar to the CA approach). Conversely, if the return latency between cooperative TRPs is too large to be ignored (e.g., when exchanging information such as CSI, scheduling, and HARQ-ACK between cooperative TRPs takes 2ms or more), it can be similar to... Figure 4 The way the attached figure is labeled "S20" is to use a method that ensures latency robustness by using an independent structure for each TRP starting from the RLC layer (similar to the DC method).

[0395] UEs supporting C-JT / NC-JT can receive C-JT / NC-JT related parameters or settings from higher-layer configuration and set the UE's RRC parameters accordingly. For higher-layer configuration, the UE can use UE capability parameters (e.g., tci-StatePDSCH). UE capability parameters (e.g., tci-StatePDSCH) can define TCI states for PDSCH transmission purposes. The number of TCI states can be configured as 4, 8, 16, 32, 64, and 128 in FR1, and as 64 and 128 in FR2. Of the configured numbers, up to eight states, indicated by the 3 bits of the TCI field in the DCI, can be configured via MAC CE messages. The maximum value of 128 can refer to the value indicated by maxNumberConfiguredTCI statesPerCC in the tci-StatePDSCH parameters included in the UE's capability signaling. In this way, a series of configuration procedures from higher-layer configuration to MAC CE configuration can be applied to beamforming change commands or beamforming indications for at least one PDSCH in a TRP.

[0396] [Multi-DCI-based Multi-TRP]

[0397] As an embodiment of this disclosure, a multi-DCI-based multi-TRP transmission method will be described. In this multi-DCI-based multi-TRP transmission method, the downlink control channel for NC-JT can be configured based on multiple PDCCHs.

[0398] In a multi-PDCCH-based NC-JT, when sending DCI for PDSCH scheduling for each TRP, a CORESET or search space distinct for each TRP can be provided. The CORESET or search space for each TRP can be configured according to at least one of the following configuration options.

[0399] For each CORESET, the upper-level index configuration includes index values. These index values ​​can be used to distinguish the TRPs used for PDCCH transmission within a given CORESET. Specifically, within a set of CORESETs with the same upper-level index value, it can be assumed that the same TRP is sending PDCCH, or that PDCCHs used to schedule PDSCHs for the same TRP are being sent. The index for each CORESET can be referred to as the CORESETPoolIndex, and for CORESETs with the same CORESETPoolIndex value, it can be assumed or determined that the PDCCH is sent from the same TRP. For CORESETs without a configured CORESETPoolIndex value, it can be assumed that a default value has been configured for CORESETPoolIndex, and this default value can be 0.

[0400] As used in this paper, when the number of types of each CORESETPoolIndex in multiple CORESETs included in the higher-layer signaling PDCCH-Config is greater than 1, that is, when each CORESET has a different CORESETPoolIndex, the UE can assume that the base station can use the multi-TRP transmission method based on multiple DCI.

[0401] In contrast, in this disclosure, when the number of CORESETPoolIndex types for each of the multiple CORESETs included in the higher-layer signaling PDCCH-Config is 1, that is, when all CORESETs have the same CORESETPoolIndex 0 or 1, the UE can assume that the base station uses a single TRP to perform transmission, rather than using a multi-TRP transmission method based on multiple DCIs.

[0402] Configuration of multiple PDCCH-Configs: Multiple PDCCH-Configs can be configured in a single BWP, and each PDCCH-Config can include PDCCH configurations for each TRP. That is, a list of CORESETs and / or a list of search spaces for each TRP can be configured in a single PDCCH-Config, and one or more CORESETs and one or more search spaces included in a single PDCCH-Config can be considered to correspond to a specific TRP.

[0403] CORESET beam / beam group configuration: The TRP corresponding to a CORESET can be distinguished by the beam or beam group configured for each CORESET. For example, if the same TCI state is configured for multiple CORESETs, it can be assumed or determined that the CORESETs are transmitted through the same TRP, or that a PDCCH for scheduling the same TRP is transmitted in the corresponding CORESET.

[0404] Search Space Beam / Beamgroup Configuration: Beams or beamgroups can be configured for each search space, and the TRP for each search space can be distinguished based on the configured beams or beamgroups. For example, if the same beam / beamgroup or TCI state is configured in multiple search spaces, the same TRP can send PDCCH in the corresponding search space, or it can send PDCCH for scheduling the same TRP in the corresponding search space.

[0405] As described above, by distinguishing the CORESET or search space according to the TRP, the PDSCH and HARQ-ACK information can be classified for each TRP, and based on this, the HARQ-ACK codebook can be generated independently and the PUCCH resources for each TRP can be used independently.

[0406] This configuration can be independent for each cell or each BWP. For example, while two different CORESETPoolIndex values ​​can be configured for a PCell, a CORESETPoolIndex value may not be configured for a specific SCell. In this case, it can be assumed that NC-JT transmission is configured for the PCell, while NC-JT transmission is not configured for the SCells without a configured CORESETPoolIndex value.

[0407] The PDSCH TCI state activation / deactivation MAC-CE applicable to multi-DCI-based multi-TRP transmission methods can follow the following rules. Figure 9If the UE does not receive the CORESETPoolIndex configuration for each of all CORESETs within the higher-layer signaling PDCCH-Config, the UE can ignore the CORESET Pool ID field 955 within the corresponding MAC-CE 950. If the UE supports a multi-DCI-based multi-TRP transmission method, i.e., when the various CORESETs within the upper-layer signaling PDCCH-Config have different CORESETPoolIndex values, the UE can activate the TCI state included in the DCI within the PDCCH, which is transmitted in a CORESET having the same CORESETPoolIndex value as the CORESET Pool ID field 955 within the corresponding MAC-CE 950. For example, if the value of the CORESET Pool ID field 955 within the corresponding MAC-CE 950 is 0, the TCI state included in the DCI within the PDCCH transmitted by a CORESET with a CORESET having a CORESETPoolIndex of 0 can follow the activation information of the corresponding MAC-CE.

[0408] If the UE receives from the base station a configuration that enables the use of a multi-DCI-based multi-TRP transmission method, i.e., the number of types of CORESETPoolIndex in multiple CORESETs included in the higher-layer signaling PDCCH-Config is greater than 1 or each CORESET has a different CORESETPoolIndex, then the UE can know that for a PDSCH scheduled by a PDCCH in each CORESET with two different CORESETPoolIndexes, the following limitations exist.

[0409] 1) If the PDSCH indicated by the PDCCH in each CORESET with two different CORESETPoollndex completely or partially overlaps, the UE may apply the TCI state indicated by each PDCCH to different CDM groups. That is, two or more TCI states cannot be applied to one CDM group.

[0410] 2) If the PDSCH indicated by the PDCCH in each of the two different CORESETPoolIndexes completely or partially overlaps, the UE can expect that the actual number of leading DMRS symbols, the actual number of additional DMRS symbols, the actual DMRS symbol positions and DMRS types of each PDSCH are different.

[0411] 3) The UE can expect that the bandwidth portion indicated by the PDCCH in each CORESET with two different CORESETPoolIndex is the same, and the subcarrier spacing is also the same.

[0412] 4) The UE can expect that the information of the PDSCH scheduled by the PDCCH in each of the two different CORESETPoolIndexes is fully included in the corresponding PDCCH.

[0413] [Multi-TRP based on a single DCI]

[0414] As an embodiment of this disclosure, a multi-TRP transmission method based on a single DCI will be described. In this multi-TRP transmission method based on a single DCI, the downlink control channel for NC-JT can be configured based on a single PDCCH.

[0415] In a multi-TRP transmission method based on a single DCI, PDSCHs transmitted by multiple TRPs can be scheduled by a single DCI. In this case, the number of TCI states can be used as a method to indicate the number of TRPs transmitting the corresponding PDSCH. That is, if the number of TCI states indicated in the DCI scheduling the PDSCH is 2, the transmission can be considered as a single-PDCCH-based NC-JT; if the number of TCI states is 1, the transmission can be considered as a single-TRP transmission. The TCI states indicated in the DCI can correspond to one or two TCI states activated by the MAC-CE. If the TCI states in the DCI correspond to two TCI states activated by the MAC-CE, then the TCI code point indicated by the DCI is associated with the TCI states activated by the MAC-CE, and this can correspond to the case where the number of TCI states activated by the MAC-CE corresponding to that TCI code point is 2.

[0416] As another example, if at least one code point in the TCI state field of the DCI indicates two TCI states, the UE can assume that the base station is capable of performing transmission based on a multi-TRP method based on a single DCI. At least one code point in the TCI state field indicating two TCI states can be activated by enhancing the PDSCH TCI state activation / deactivation MAC-CE.

[0417] Figure 12 The enhanced PDSCH TCI state activation / deactivation MAC-CE structure is shown. The meaning of each field within the MAC-CE and the configurable values ​​for each field are shown in Table 21 below.

[0418] [Table 21]

[0419] exist Figure 12 In the context of MAC-CE, if the value of field C01205 is 1, then the corresponding MAC-CE can be configured to include, except for the TCI status ID. 0,1 In addition to field 1210, it also includes the TCI status ID. 0,2 Field 1215. This could mean that for the 0th code point in the TCI status field included within the DCI, the TCI status ID... 0,1 and TCI status ID 0,2 If activated, and if the base station indicates the corresponding code point to the UE, it can indicate two TCI states to the UE. If the value of C0 field 1205 is 0, the corresponding MAC-CE cannot include the TCI state ID. 0,2 Field 1215, and this may mean that for the 0th code point of the TCI state field included in the DCI, it corresponds to the TCI state ID. 0,1 One of the TCI states is activated.

[0420] The above configuration can be independent for each cell or each BWP. For example, although one TCI code point can correspond to a maximum of two active TCI states in a PCell, one TCI code point can correspond to a maximum of one active TCI state in a specific SCell. In this case, it can be considered that although NC-JT is configured in the PCell, it is not configured in the aforementioned SCell.

[0421] [Methods for distinguishing between multiple TRP PDSCH retransmission schemes based on a single DCI (TDM / FDM / SDM)]

[0422] Next, a method for distinguishing multiple TRP PDSCH retransmission schemes based on a single DCI will be described in detail. Different multiple TRP PDSCH retransmission schemes based on a single DCI (e.g., TDM, FDM, and SDM) can be indicated to the UE by the base station based on the value indicated by the DCI field and the upper-layer signaling configuration. Table 22 below shows the method for distinguishing single or multiple TRP schemes indicated to the UE based on specific DCI field values ​​and upper-layer signaling configurations.

[0423] [Table 22]

[0424] Each column in Table 22 above can be described as follows.

[0425] - Number of TCI states (second column): can refer to the number of TCI states indicated by the TCI state field in the DCI, and can be 1 or 2.

[0426] - Number of CDM Groups (Third Column): This can refer to the number of different CDM groups for the DRMS ​​port indicated by the antenna port field within the DCI. This number can be 1, 2, or 3.

[0427] - RepetitionNumber configuration and indication conditions (fourth column): There are three conditions based on whether all TDRA entries that can be indicated by the time-domain resource allocation field in DCI are configured with repetitionNumber and whether the TDRA entry that is actually indicated has repetitionNumber configuration.

[0428] Condition 1: At least one of all TDRA entries indicated by the time-domain resource allocation field includes a configuration of repetitionNumber, and the TDRA entries indicated by the time-domain resource allocation field within the DCI include a configuration of repetitionNumber greater than 1.

[0429] Condition 2: At least one of all TDRA entries indicated by the time-domain resource allocation field includes a configuration of repetitionNumber, and the TDRA entries indicated by the time-domain resource allocation field within the DCI do not include a configuration of repetitionNumber.

[0430] Condition 3: The case where none of the TDRA entries indicated by the Time Domain Resource Allocation field include the configuration of repetitionNumber.

[0431] - Regarding the repetitionScheme configuration (fifth column): This indicates whether an upper-layer signaling repetitionScheme is configured. The upper-layer signaling repetitionScheme can be configured as one of "tdmSchemeA", "fdmSchemeA", or "fdmSchemeB".

[0432] - Transmission scheme indicated to UE (sixth column): can refer to a single or multiple TRP scheme indicated according to each combination shown in Table 22 above (first column).

[0433] Single TRP: Refers to PDSCH transmission based on a single TRP. If the UE receives the pdsch-AggegationFactor configuration in the higher-layer signaling PDSCH-config, it can schedule the UE to repeat PDSCH transmissions based on a single TRP as many times as configured. Otherwise, the UE can receive scheduling for a single PDSCH transmission based on a single TRP.

[0434] Single TRP TDM Scheme B: This refers to the repeated transmission of PDSCH between time slots based on time resource allocation within a single TRP. According to condition 1 related to repetitionNumber mentioned above, the UE repeatedly transmits PDSCH on time resources corresponding to the number of time slots with a repetitionNumber greater than 1 configured in the TDRA entry indicated by the time domain resource allocation field. In this case, the start symbol and symbol length of the PDSCH indicated by the TDRA entry are also applied to each time slot corresponding to the repetitionNumber, and the same TCI state is applied to each PDSCH repeated transmission. This scheme is similar to the time slot aggregation scheme in that it performs inter-slot PDSCH repeated transmission on time resources, but unlike time aggregation, whether to indicate repeated transmission can be dynamically determined based on the time domain resource allocation field within the DCI.

[0435] Multi-TRP SDM: This can refer to a PDSCH transmission scheme based on the spatial resource partitioning of multiple TRPs. It's a method of receiving PDSCH from each TRP by dividing the space into layers. Although not a repetitive transmission scheme, the reliability of PDSCH transmission can be improved by increasing the number of layers to perform transmission at a reduced coding rate. The UE can receive PDSCH by applying each of the two TCI states indicated by the TCI state field within the DCI to each of the two CDM groups indicated by the base station.

[0436] Multi-TRP FDM Scheme A: This refers to a PDSCH transmission scheme based on the frequency resource allocation of multi-TRP. It has a single PDSCH transmission opportunity and, therefore, while not a repetitive transmission scheme, it can achieve high reliability by increasing the amount of frequency resources to reduce the coding rate, similar to multi-TRP SDM. Multi-TRP FDM Scheme A applies each of the two TCI states indicated by the TCI state field within the DCI to non-overlapping frequency resources. If the PRB bundle size is determined to be "wideband" and the number of RBs indicated by the frequency domain resource allocation field is N, the UE receives the PDSCH by applying the first TCI state to the first ceil (N / 2) RBs and the second TCI state to the remaining floor (N / 2) RBs. Here, ceil(.) and floor(.) are operators for rounding up and down to the first decimal place, respectively. If the PRB bundle size is determined to be 2 or 4, the PDSCH can be received by applying the first TCI state to the even-numbered PRGs and the second TCI state to the odd-numbered PRGs.

[0437] Multi-TRP FDM Scheme B: This refers to a PDSCH repetitive transmission scheme based on frequency resource allocation in Multi-TRP, which can have two PDSCH transmission opportunities, allowing PDSCH to be repeatedly transmitted on each opportunity. Similar to Multi-TRP FDM Scheme A, Multi-TRP FDM Scheme B can also apply each of the two TCI states indicated by the TCI state field within the DCI to non-overlapping frequency resources. If the PRB bundle size is determined to be "wideband" and the number of RBs indicated by the frequency domain resource allocation field is N, the UE can receive PDSCH by applying the first TCI state to the first ceil (N / 2) RBs and the second TCI state to the remaining floor (N / 2) RBs. Here, ceil(.) and floor(.) are operators used for rounding up and rounding down to the first decimal place, respectively. If the PRB bundle size is determined to be 2 or 4, PDSCH can be received by applying the first TCI state to the even-numbered PRGs and the second TCI state to the odd-numbered PRGs.

[0438] Multi-TRP TDM Scheme A: This refers to a PDSCH repetitive transmission scheme within a time slot based on multi-TRP time resource allocation. The UE can have two PDSCH transmission opportunities within a time slot, and the first reception opportunity can be determined based on the start symbol and symbol length of the PDSCH indicated by the time domain resource allocation field within the DCI. The start symbol of the second PDSCH reception opportunity can be obtained by applying the symbol offset corresponding to the higher-layer signaling StartingSymbolOffsetK from the last symbol of the first transmission opportunity, and the actual transmission can be determined as the indicated symbol length starting from that start symbol. If the higher-layer signaling StartingSymbolOffsetK is not configured, the symbol offset can be considered 0.

[0439] Multi-TRP TDM Scheme B: This refers to a PDSCH repetition transmission scheme based on the time resource allocation of multiple TRPs between time slots. A UE can have one PDSCH transmission opportunity within a time slot and can receive PDSCH repetition transmissions based on the same PDSCH start symbol and symbol length during a period of time slots up to the repetitionNumber indicated by the time domain resource allocation field in the DCI. If repetitionNumber is 2, the UE can receive PDSCH repetition transmissions in the first and second time slots by applying the first and second TCI states respectively. If repetitionNumber is greater than 2, the UE can use different TCI state application schemes according to the configured upper-layer signaling tciMapping. If tciMapping is configured as "cyclicMapping", the first and second TCI states can be applied to the first and second PDSCH transmission opportunities respectively, and the same TCI state application scheme can be applied to other PDSCH transmission opportunities. If tciMapping is configured as "sequenticalMapping", then the first TCI state can be applied to the first and second PDSCH transmission times, the second TCI state can be applied to the third and fourth PDSCH transmission times, and the same TCI state application scheme can be applied to other PDSCH transmission times.

[0440] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The content of this disclosure can be applied to frequency division duplex (FDD), time division duplex (TDD), and / or cross-duplex (XDD) (and / or subband non-overlapping full-duplex (SBFD)) systems. As used herein, high-level signaling (or higher-layer signaling) is a method of transmitting signals from a base station to a UE using downlink data channels of the physical layer, or from a UE to a base station using uplink data channels of the physical layer, and may also be referred to as “RRC signaling,” “PDCP signaling,” or “Media Access Control (MAC) control element (MAC CE).”

[0441] In the following text, for ease of description, TRP, beam, and / or transmission direction, which can be distinguished by upper-layer / L1 parameters such as TCI status or spatial relationship information, cell ID, TRP ID, or panel ID, can be collectively described as TRP, beam, or TCI status. Therefore, in practical applications, TRP, beam, or TCI status can be appropriately replaced with one of the aforementioned terms.

[0442] As used herein, the UE can use various methods to determine whether cooperative communication is applied, including a PDCCH with a specific format for allocating a PDSCH with cooperative communication, a PDCCH with a specific indicator indicating whether cooperative communication is applied, a PDCCH with a specific RNTI scrambling, or assuming that cooperative communication is applied in a specific section indicated by a higher layer. In the following text, for ease of description, the reception of a PDSCH with cooperative communication based on conditions similar to those described above will be referred to as the NC-JT case.

[0443] In the following description, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this description, a base station is an entity that allocates resources to terminals and can be at least one of a gNode B, gNB, eNode B, Node B, base station (BS), radio access unit, base station controller, or node on a network. Terminals may include user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In the following description of embodiments of the present disclosure, a 5G system will be used as an example, but embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. For example, such communication systems may include mobile communication technologies such as LTE or LTE-A, as well as mobile communication technologies developed after 5G. Therefore, based on the determination of those skilled in the art, embodiments of the present disclosure can also be applied to other communication systems with some modifications without departing from the scope of the present disclosure. The content of this disclosure can be applied to FDD, TDD, and / or XDD (and / or SBFD) systems.

[0444] Furthermore, in describing this disclosure, detailed descriptions of known functions or configurations incorporated herein will be omitted where it is determined that the description may unnecessarily obscure the subject matter of the disclosure. Additionally, the terminology described below is defined in consideration of the functions in this disclosure and may vary depending on the user, the user's intent, or habits. Therefore, the definitions of terms should be made based on the entirety of the specification.

[0445] In the following description of this disclosure, higher-level signaling may refer to signaling corresponding to at least one of the following signaling, or a combination of one or more of them.

[0446] Master Information Block (MIB)

[0447] System Information Block (SIB) or SIB X (X=1, 2, ...)

[0448] Radio Resource Control (RRC)

[0449] Media Access Control (MAC) Control Element (CE)

[0450] In addition, L1 signaling can refer to signaling corresponding to at least one of the following signaling methods using physical layer channels or signaling, or a combination of one or more of them.

[0451] Physical Downlink Control Channel (PDCCH)

[0452] Downlink Control Information (DCI)

[0453] UE-specific DCI

[0454] Group Public DCI

[0455] Public DCI

[0456] Scheduling DCI (e.g., DCI used to schedule downlink or uplink data)

[0457] Non-scheduled DCI (e.g., DCI not used to schedule downlink or uplink data)

[0458] Physical Uplink Control Channel (PUCCH)

[0459] Uplink Control Information (UCI)

[0460] As used in this article, determining the priority between A and B can refer to various operations, such as selecting the one with higher priority according to a predetermined priority rule and executing the operation corresponding to the selected one, omitting or discarding the operation corresponding to the one with lower priority, etc.

[0461] As used herein, the term “slot” can generally refer to a specific time unit corresponding to a transmission time interval (TTI), specifically a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system.

[0462] As used herein, the above examples can be described through a number of embodiments, but the above examples are not independent of each other and one or more embodiments can be applied simultaneously or in combination.

[0463] In the description of embodiments of this disclosure, the term "greater than or equal to" can be replaced with "greater than", and the term "less than or equal to" can be replaced with "less than".

[0464] <First Implementation: A Method Supporting UL-Only TRP>

[0465] Embodiments of this disclosure illustrate a method for supporting a UL-only TRP capable of UL reception only among a plurality of TRPs operating in a base station. This embodiment can be operated in combination with other embodiments. Hereinafter, in this disclosure, the terms UL-only TRP, uplink-dedicated TRP, UL-only TRP, and various terms that can be interpreted equivalently or similarly can be construed as referring to a TRP that supports only uplink signal reception among the operable TRPs of a base station.

[0466] The UE can determine the uplink transmit power based on the TCI state when transmitting uplink channels. Depending on the supported TCI states, the UE and base station can operate using a joint TCI scheme (indicating uplink transmit power parameters via TCI-State) or a separate TCI scheme (indicating uplink transmit power parameters via TCI-UL-State). The transmit power parameters can be applied to the uplink channel to be transmitted using the following methods.

[0467] [Method 1-1] Basic Transmit Power Determination Method: Application of Common Transmit Power Parameters

[0468] For all uplink transmissions within each uplink bandwidth segment, the UE can apply a set of transmit power parameters (e.g., p0, alpha, and closed-loop index) that can be identified by the ul-powerControl configured for the corresponding uplink bandwidth segment.

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

[0470] The UE can apply a set of transmit power parameters (e.g., p0, alpha, and closed-loop index) that can be identified by the higher-layer signaling ul-powerControl-r17 within the joint TCI state (TCI-State) or the individual TCI state (TCI-UL-State).

[0471] The UE can report to the base station via a UE capability report whether the UE supports a combination of at least one of Method 1-1 and Method 1-2. Furthermore, the UE can be configured by the base station via higher-layer signaling to use a combination of Method 1-1 and Method 1-2.

[0472] Figure 13 An operational example is shown of a UE and a base station operating with multiple TRPs, including a TRP that only supports uplink reception, according to embodiments of the present disclosure.

[0473] UE 13-10 can operate while connected to a base station that operates multiple TRPs as described above. Typically, the UE can assume that each of the multiple TRPs supports both uplink reception and downlink transmission. In addition to the conventional TRP 13-00, which is capable of both uplink reception and downlink transmission, the base station can jointly operate a TRP 13-05 that only supports uplink reception to enhance the UE's uplink coverage or achieve energy savings by conserving the base station's downlink transmit power. A TRP that only supports uplink reception can be referred to as a UL-only TRP. The UE can assume that downlink transmission is not performed from a UL-only TRP. As an assumption regarding UL-only TRPs, the base station and UE can consider combinations of at least one of the following.

[0474] A UL-only TRP can operate as a UL-only TRP for a specific UE. That is, while a UL-only TRP actually has both uplink reception and downlink transmission capabilities, it can support only uplink reception for a specific UE under certain conditions (e.g., by notifying the UE to connect to the UL-only TRP via a combination of specific higher-layer signaling, MAC-CE, and L1 signaling). In other words, a UL-only TRP can support downlink transmission for other UEs. When a specific UE is located at the boundary of any cell coverage area, the UL-only TRP can extend uplink coverage by additionally operating a pre-installed TRP or a newly installed TRP near the location specifically for reception.

[0475] A UL-only TRP can be a TRP that does not support downlink transmission functionality for all UEs but only supports uplink reception functionality. That is, a UL-only TRP can be a TRP that is cost-effective to produce and install, and can obtain receive diversity from the base station's perspective by additionally receiving uplink transmissions from UEs in addition to existing TRPs.

[0476] The UE can receive the path loss measurement reference signal from TRP 13-00, which is capable of both uplink and downlink operation, while downlink transmissions from UL-only TRP 13-05 are not performed. Therefore, when UE 13-10 performs an uplink transmission to UL-only TRP 13-05, the path loss between the UE and the UL-only TRP may be unknown. To resolve this issue, the base station and UE can perform the following procedure to obtain path loss information between the UL-only TRP and the UE according to method 2-1.

[0477] [Method 2-1]

[0478] [Process 2-1] UE uplink transmission

[0479] [Process 2-2] Calculation of path loss difference at the base station

[0480] [Process 2-3] Send the path loss difference to the UE

[0481] [Procedure 2-4] After obtaining the path loss difference d_P between the TPR that supports both uplink and downlink and the UL-only TRP, the UE does not apply uplink transmission with d_P.

[0482] [Procedure 2-5] Calculation of path loss difference at the base station

[0483] [Process 2-6] Send the path loss difference to the UE

[0484] The UE can perform the following procedure to obtain path loss information according to method 2-2.

[0485] [Method 2-2]

[0486] [Process 3-1] UE uplink transmission

[0487] [Procedure 3-2] Calculation of path loss difference at the base station

[0488] [Process 3-3] Send the path loss difference to the UE

[0489] [Procedure 3-4] After obtaining the path loss difference d_P between the TPR that supports both uplink and downlink and the UL-only TRP, the UE applies the uplink transmission of d_P.

[0490] [Procedure 3-5] Calculation of path loss difference at the base station

[0491] [Process 3-6] Send the path loss difference to the UE

[0492] Using methods 2-1 and 2-2 described above, the UE can use the following modified transmit power calculation equation when determining the uplink transmit power for UL TRP only.

[0493] For example, when determining the PUCCH transmit power for a UL TRP-only system that only supports uplink reception, the UE can modify Equation 2 to Equation 11 for use. That is, Equation 2 can be modified to Equation 11. In this case, in Equation 11... The d_P value can be considered as the difference in path loss, and This could mean that the path loss difference corresponds to one or more path loss measurement reference signals. When When corresponding to a path loss measurement reference signal, the UE can consider .

[0494] [Equation 11]

[0495] In another example, when determining the PUSCH transmit power for a UL TRP that only supports uplink reception, the UE can modify Equation 4 to Equation 12 or Equation 13 for use. That is, Equation 4 can be modified to Equation 12 or Equation 13. In this case, Equation 12 or Equation 13... The d_P value can be considered as the difference in path loss, and This could mean that the path loss difference corresponds to one or more path loss measurement reference signals. When When corresponding to a path loss measurement reference signal, the UE can consider Equation 12 or Equation 13 can be based on the value of the difference in path loss. Whether it is directly applied to path loss is used to distinguish them.

[0496] [Equation 12]

[0497] [Equation 13]

[0498] In another example, when determining the PUSCH transmit power for a UL TRP that only supports uplink reception, the UE can modify Equation 7 to Equation 14 or Equation 15 for use. That is, Equation 7 can be modified to Equation 14 or Equation 15. In this case, Equation 14 or Equation 15... The d_P value can be considered as the difference in path loss, and This could mean that the path loss difference corresponds to one or more path loss measurement reference signals. When When corresponding to a path loss measurement reference signal, the UE can consider Equation 14 or Equation 15 can be based on the value of the difference in path loss. Whether it is directly applied to path loss is used to distinguish them.

[0499] [Equation 14]

[0500] [Equation 15]

[0501] The UE may be notified by the base station of at least one combination of method 2-1 and method 2-2 through a combination of at least one of higher-layer signaling, MAC-CE signaling and L1 signaling, or it may be expected that the combination of at least one of method 2-1 and method 2-2 is fixedly defined in the standard.

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

[0503] The UE may consider a combination of at least one of the following options as a method for receiving path loss difference or variation from the base station.

[0504] [Method 3-1]

[0505] The UE can be configured by the base station via higher-layer signaling to determine the path loss difference d_P or the change in d_P'' value.

[0506] [Method 3-2]

[0507] The UE can be configured by the base station via higher-layer signaling to specify the path loss difference d_P value or the change in d_P value d_P'', and then receive MAC-CE signaling from the base station to update the pre-configured value.

[0508] [Method 3-3]

[0509] The UE can be configured by the base station via higher-layer signaling to determine the path loss difference d_P value or the change in d_P value d_P'', and then receive the indication via DCI.

[0510] [Methods 3-4]

[0511] The UE can be configured by the base station via higher-layer signaling to receive two or more CSI-RS and implicitly receive the d_P or d_P'' value through the difference in the received power of the CSI-RS.

[0512] [Methods 3-5]

[0513] The UE can receive the d_P or d_P'' value from the base station and update the pre-configured value through a combination of at least one of methods 3-1 to 3-4.

[0514] As a method for the UE to receive UL scheduling information from the base station, including information related to the path loss difference, at least one of the following options may be considered.

[0515] [Method 4-1]

[0516] The UE can be configured by the base station via higher-layer signaling to have one or more joint TCI states or UL TCI states configured. In this case, the UE can configure information about path loss difference in one or more joint TCI states or UL TCI states, as shown in Table 23. The names of the RRC information elements (IEs) in Table 23 are just examples and can be replaced with other names.

[0517] [Table 23]

[0518] In Table 23, the UE can configure the pathlossOffset for the path loss difference via higher-layer signaling, and its value can be an integer from Xs to Xe.

[0519] For example, Xs and Xe can be 0 and 30 respectively. In another example, Xs and Xe can be -10 and 50 respectively, and their values ​​can be in 1 dB. In yet another example, Xs and Xe can be 2 and 32 respectively, and their values ​​can be in 2 dB.

[0520] [Method 4-2]

[0521] The UE can be configured by the base station via higher-layer signaling to have one or more joint TCI states or UL TCI states, and the UE can configure one or more path loss differentials within the higher-layer signaling BWP-UplinkDedicated for the uplink bandwidth portion, wherein each path loss differential can be mapped to at least one set of path loss measurement reference signals. Furthermore, in the joint TCI state or UL TCI state, the UE can be further configured with higher-layer signaling indicating whether path loss differentials are applied in addition to the path loss measured via path loss measurement reference signals configurable via higher-layer signaling. Table 24 shows an example of this method, and the mapping of path loss differentials to sets of path loss measurement reference signals is not limited to this. The names of RRC IEs in Table 24 are merely examples and can be replaced with other names.

[0522] [Table 24]

[0523] The UE can configure the pathlossOffset for the path loss difference via higher-layer signaling, and its value can be an integer from Xs to Xe.

[0524] For example, Xs and Xe can be 0 and 30 respectively. In another example, Xs and Xe can be -10 and 50 respectively, and their values ​​can be in 1 dB. In yet another example, Xs and Xe can be 2 and 32 respectively, and their values ​​can be in 2 dB.

[0525] [Method 4-3]

[0526] The UE can be configured with one or more joint TCI states or UL TCI states by the base station via higher-layer signaling, and the UE can configure a single path loss difference within the higher-layer signaling BWP-UplinkDedicated for the uplink bandwidth portion. In this case, the UE can assume that the path loss difference is always applied for a specific TCI state, based on the operating methods with multiple TRPs.

[0527] Table 25 shows an example of this method, and the method is not limited to this. The names of RRC IEs in Table 25 are merely examples and can be replaced with other names.

[0528] [Table 25]

[0529] ULonlyNode2 can be defined as a condition by which the base station configures the pathlossOffset for the UE via the higher-layer signaling BWP-UplinkDedicated. The condition ULonlyNode2 can instruct the UE to operate in a cell that includes UL-only TRPs, which may imply a situation where specific higher-layer signaling is configured.

[0530] If the UE does not configure pathlossOffset in BWP-UplinkDedicated, the UE can consider the path loss difference to be 0.

[0531] The UE can configure the pathlossOffset for the path loss difference via higher-layer signaling, and its value can be an integer from Xs to Xe.

[0532] For example, Xs and Xe can be 0 and 30 respectively. In another example, Xs and Xe can be -10 and 50 respectively, and their values ​​can be in 1 dB. In yet another example, Xs and Xe can be 2 and 32 respectively, and their values ​​can be in 2 dB.

[0533] [Method 4-4]

[0534] The UE can be configured with a single path loss difference by the base station via higher-layer signaling. The path loss difference configuration can be different for each bandwidth segment, or for each cell, allowing the same value to be configured for all bandwidth segments within the cell. In this case, when the path loss difference is configured, the UE can expect a new field in the DCI indicating whether the path loss difference is applied. The UE can use this new field in the DCI to distinguish from the base station whether uplink transmission is for a UL-only TRP or for a TRP capable of both uplink and downlink operation.

[0535] [Methods 4-5]

[0536] UE may consider a combination of at least one of methods 4-1 to 4-4.

[0537] The UE may be notified by the base station through a combination of at least one of the higher-layer signaling, MAC-CE signaling and L1 signaling, or it may be expected that the combination of at least one of the methods 4-1 to 4-5 is fixedly defined in the standard.

[0538] The UE can report to the base station whether it can support a combination of at least one of methods 4-1 to 4-5 as a UE capability. When the UE reports to the base station a UE capability that supports a combination of one or more specific methods, it can be assumed that the UE reports that a combination of one or more other specific methods is not supported.

[0539] The UE can determine whether to apply the path loss difference by considering a combination of at least one of methods 4-1 to 4-5 in PUSCH transmissions based on dynamic authorization and DCI scheduling, PUSCH transmissions based on type 2 configuration authorization activated by DCI, PUSCH transmissions based on type 1 configuration authorization configured by higher-layer signaling, PUCCH transmissions, SRS transmissions, and PRACH transmissions.

[0540] <Second Embodiment: Enhanced PHR Triggering Method for Reporting Power Margin of UL TRP Only>

[0541] Embodiments of this disclosure illustrate a method for triggering a power headroom report (PHR) for uplink channel transmission when an uplink-dedicated TRP (UL-only TRP or UL-only TRP) is supported. This embodiment can be operated in combination with other embodiments shown in this disclosure. Hereinafter, in this disclosure, the terms UL-only TRP, uplink-dedicated TRP, UL-only TRP, and various terms that can be interpreted equivalently or similarly can be construed as referring to a TRP that supports only uplink signal reception among the operable TRPs of a base station.

[0542] As described in the first embodiment, a UL-only TRP is a TRP capable only of receiving UL signals (channels), and the UE cannot receive DL signals (channels) including DL reference signals through a TRP operating as a UL-only TRP. In the first embodiment, various methods for determining the path loss value of a UL-only TRP have been described, for which the DL signals required for measuring the path loss value used in determining the UL transmit power, particularly the periodic DL reference signal (periodic DL RS), are not transmitted.

[0543] When the following triggering events occur, the UE can report the power margin to the base station in MAC CE format, which indicates the difference between the maximum transmit power calculated by the UE and the transmit power of the currently transmitted uplink channel (or the transmit power in reference format if no uplink signal is currently being transmitted to the corresponding cell).

[0544] - [Trigger Event 1] When the higher-layer parameter phr-ProhibitTimer expires and the MAC entity has uplink resources for a new transmission, the path loss change of at least one active supporting cell exceeds the higher-layer parameter phr-Tx-PowerFactorChange dB since the most recent PHR transmission. The active downlink bandwidth portion of this at least one active supporting cell is not the dormant bandwidth portion. In this case, the path loss change of a single cell is determined by the difference between the current path loss relative to the current path loss reference measurement and the path loss relative to the path loss reference measurement at the most recent PHR transmission time.

[0545] - [Triggering Event 2] The high-level parameter phr-PeriodicTimer expired.

[0546] - [Trigger Event 3] The situation where the power headroom reporting function is configured or reconfigured by a higher layer, rather than the configuration or reconfiguration of disabling power headroom reporting.

[0547] - [Trigger Event 4] Activation of an SCell for a MAC entity with an uplink, where firstActiveDownlinkBWP-Id is not configured as a dormant bandwidth portion. firstActiveDownlinkBWP-Id refers to the identifier of the DL BWP to be activated during RRC (re)configuration (when configured for SpCell) or the identifier of the DL BWP to be used when SCell is activated (when configured for SCell).

[0548] - [Trigger Event 5] SCG Activation

[0549] - [Trigger Event 6] Addition of PSCell unless SCG is deactivated (i.e., PSCell is newly added or changed).

[0550] - [Trigger Event 7] When the higher-layer parameter phr-ProhibitTimer expires and the MAC entity has uplink resources for a new transmission, for any active supporting cell with an uplink-configured MAC entity, both of the following conditions a) and b) are met: a) Uplink resources for transmission have been allocated, or a PUCCH has been sent to the corresponding cell; b) When a MAC entity has uplink resources for transmission or sends a PUCCH to the corresponding cell, the required power backoff due to the power management of the corresponding cell is greater than the higher-layer parameter phr-Tx-PowerFactorChange dB since the most recent PHR transmission.

[0551] - [Trigger Event 8] For MAC entities configured with an uplink in the dormant bandwidth portion, the active bandwidth portion is switched to the non-dormant downlink bandwidth portion of the SCell.

[0552] - [Trigger Event 9] When the higher-layer parameter mpe-Reporting-FR2 is configured for the UE to indicate whether to report the maximum permissible UE output power reduction (MPE P-MPR) to meet the maximum permissible exposure (MPE) in FR2, and mpe-ProhibitTimer is not running, at least one of the following conditions a) and b) is met: a) For a MAC entity, the measured P-MPR applied to meet the FR2 MPE requirements specified in TS 38.101-2 since the most recent PHR report is equal to or greater than the mpe-Threshold configured as a higher-layer parameter for at least one active FR2 supporting cell; or b) For a MAC entity, the measured P-MPR applied to meet the FR2MPE requirements specified in TS 38.101-2 for at least one active FR2 supporting cell changes exceeding the phr-Tx-PowerFactorChange dB configured as a higher-layer parameter since the most recent PHR transmission performed when the measured P-MPR is equal to or greater than the higher-layer parameter mpe-Threshold was applied to meet the MPE requirements.

[0553] The power headroom report can be triggered based on the above-mentioned triggering events, and the UE can determine the power headroom report based on the following additional conditions.

[0554] - [Additional Conditions Based on Temporary Required Power Back-off] When required power back-off due to power management is temporarily reduced (i.e., for a maximum of tens of milliseconds (ms)), the MAC entity is not required to trigger a power headroom report. If required power back-off is temporarily reduced and a power headroom report is triggered by another event, the PCMAX,f,c / PH value, representing the ratio between maximum power and remaining (available) power, is prevented from being temporarily reduced. That is, the PHR is prevented from being triggered by temporary power back-off. For example, this condition is added to ensure that when the PHR is triggered by another PHR triggering event (such as a periodic timer expiration), instead of reporting a PH that reflects the temporary power reduction due to required power back-off, a PH excluding any effects of required power back-off is reported.

[0555] - [Power headroom reporting conditions based on UE implementation] If a single HARQ process is configured based on cg-RetransmissionTimer, and the power headroom report has been included in the MAC PDU transmitted by the corresponding HARQ process, but the transmission through the lower layer has not yet been performed, the method for processing the power headroom report can be determined based on the UE implementation.

[0556] When one or more of the above-mentioned triggering events occur to trigger a power headroom report, and if the uplink transmission resources allocated via downlink control information can accommodate the MAC entity and its subheadings for the power headroom report, the UE can perform the power headroom report through the uplink resources.

[0557] The aforementioned PHR triggering events can occur based on cell activation / deactivation, BWP handover, the total amount / change of measured P-MPR applied to meet MPE requirements in FR2 support, the expiration of a periodic PHR timer, or changes in DL path loss values ​​measured by periodic DL RS. In particular, PHR triggering events based on changes in DL path loss values ​​measured by DL RS can be used as primary triggering events enabling the base station to identify changes in uplink and downlink channel quality.

[0558] Figure 14 An operational example is shown of a base station operating with a plurality of TRPs, including only UL TRPs, and a mobile UE according to an embodiment of the present disclosure.

[0559] For UE 1410 or 1420, a TRP 1400 (hereinafter, TRP1) supporting both uplink and downlink can be supported, and a UL-only TRP 1405 (hereinafter, TRP2) supporting only uplink reception can be supported. The downlink can be supported by a single TRP 1400, and the uplink can be supported by multiple TRPs 1400 and 1405. The path loss 1411 of the uplink and downlink signals of TRP1 measured based on the initial UE location 1410 and the path loss 1421 of the uplink and downlink signals of TRP1 measured based on the subsequently moved UE location 1420 can be the same as each other, or the variation between path loss 1411 and path loss 1421 can be less than a threshold (e.g., the higher-layer parameter phr-Tx-PowerFactorChange dB). The variation between the path loss 1412 of the uplink signal of TRP2 measured based on the initial UE position 1410 and the path loss 1422 of the uplink signal of TRP2 measured based on the subsequently moved UE position 1420 can exceed a threshold (e.g., the higher-layer parameter phr-Tx-PowerFactorChange dB). Depending on the UE's direction of movement and distance, variations may occur, such as... Figure 14 The situation is shown below.

[0560] like Figure 14 As shown, when the UE moves, the change between path losses 1411 and 1421 for the uplink / downlink signals of TRP1 1400 is negligible, while the change between path losses 1412 and 1422 for the uplink signals of TRP2 1405, which is a UL-only TRP, may be significant. In this case, since the UE is able to receive the downlink reference signal from TRP1 1400, the UE can recognize that the change between path losses 1411 and 1421 for the uplink and downlink signals is small.

[0561] However, since the UE cannot receive the downlink reference signal from TRP2 1405, which is a UL-only TRP, as described in the first embodiment, the UE can identify the path loss of the UL-only TRP based on the path losses 1411 and 1421 measured by the UE using the downlink reference signal received from TRP1 1400 and the path loss offset indicated to the UE by the base station (which may correspond to d_P described in the first embodiment, and the path loss offset and d_P can be considered to have the same meaning) (i.e., the difference in the amount of path loss between TRP1 1400 and TRP2 1405). Therefore, when the path loss offset indicated to the UE by the base station is not updated, the UE cannot identify the significant change between the path losses 1412 and 1422 of the uplink signal of TRP2 1405, which is a UL-only TRP. Because the UE identifies the variation between path losses 1412 and 1422 of UL TRP 1405 based on path losses 1411 and 1421 measured using downlink reference signals received from TRP1 1400 associated with TRP2 1405 and the path loss offset indicated by the base station to the UE, therefore, in situations such as Figure 14 As shown, in cases where the path loss changes significantly only between UL TRP 1412 and 1422, the UE may not use the method described in Trigger Event 1, which involves comparing the path loss change measured via a path loss reference (e.g., the downlink reference signal received from TRP1 1400) with a threshold to trigger the power margin.

[0562] As described above, in order to address the issue that although the path loss of UL TRP-only varies greatly due to UE movement, the power margin is not triggered because the path loss variation measured based on the downlink reference signal associated with UL TRP-only is small, the following options or combinations thereof can be considered.

[0563] [Option 1] The UE can change the meaning of the path loss reference that the UE refers to in order to determine the occurrence of the PHR triggering event.

[0564] If UL-only TRP is operated for the UE, the base station can configure higher-layer parameters for the UE to support UL-only TRP. That is, when higher-layer parameters for supporting UL-only TRP are configured for the UE, the meaning of the path loss reference used by the UE to determine the occurrence of the aforementioned triggering event 1 can be modified or extended. In other words, when the occurrence of the aforementioned triggering event 1 is determined, the UE can interpret the path loss reference with a modified or extended meaning.

[0565] When option 1 is not applied, the DL RS referenced for determining the transmit power of the uplink signal can be defined as a path loss reference used to determine whether a power headroom report is triggered in trigger event 1 above. That is, a power headroom report can be triggered when the path loss change measured by the DL RS referenced for determining the transmit power of the uplink signal is greater than a threshold (e.g., the higher-layer parameter phr-Tx-PowerFactorChange dB).

[0566] When running UL TRP only for the UE according to Option 1, the path loss offset indicated by the base station to the UE can be considered together with the DL RS referenced for determining the transmit power of the uplink signal when defining the path loss reference used to determine whether to trigger a power headroom report. That is, a power headroom report can be triggered when the sum of the path loss value measured by the DL RS referenced for determining the transmit power of the uplink signal sent to UL TRP only and the path loss offset indication value is greater than a threshold (e.g., the higher-layer parameter phr-Tx-PowerFactorChange dB).

[0567] According to Option 1, whether to trigger a power headroom report is determined by considering both the change in the path loss value measured by the DL RS (referenced to determine the transmit power of the uplink signal sent to UL TRP only) and the change in the value indicated by the updated path loss offset. In this case, the base station can update the path loss offset and configure / indicate it for the UE. The base station can update the path loss offset configured / indicated for the UE via MAC CE. Alternatively, the base station can reconfigure the path loss offset configured / indicated for the UE via RRC. Alternatively, the base station can indicate the path loss offset configured / indicated for the UE via DCI. [Option 2] When path loss offset for supporting UL TRP only is supported, a power headroom report can be triggered based on the change in the value indicated by the updated path loss offset. That is, as described in Option 1, a power headroom report can be triggered when the base station updates the path loss offset for the UE.

[0568] The UE can determine whether to trigger a power margin report based on the following path loss offset update.

[0569] [Option 2-1] The UE may trigger a power headroom report when the base station updates the path loss offset for the UE. More specifically, according to Option 2-1, the UE may trigger a power headroom report without any additional conditions when the base station updates the path loss offset for the UE via MAC CE (or indicates the same to the UE via RRC reconfiguration or DCI). In this case, the power headroom report may be triggered regardless of whether the timer used to disable power headroom reporting (e.g., phr-ProhibitTimer) has expired. Alternatively, the UE may trigger a power headroom report when the timer used to disable power headroom reporting (e.g., phr-ProhibitTimer) has expired and the base station updates the path loss offset for the UE via MAC CE (or indicates the same to the UE via RRC reconfiguration or DCI).

[0570] Alternatively, according to option 2-1, when the base station updates the path loss offset for the UE via MAC CE (or indicates the same to the UE via RRC reconfiguration or DCI), a new timer (e.g., phr-ProhibitTimerforULTRP) can be defined to prohibit the triggering of power headroom reports. The base station can configure the timer related to the power headroom report triggered based on the path loss offset for the UE via higher-layer parameters, and the time unit (e.g., subframe unit) can be configured by higher-layer parameters as the value of the timer. As described above, when the new timer is configured, the configured new timer expires, and the base station updates the path loss offset for the UE via MAC CE (or indicates the same to the UE via RRC reconfiguration or DCI), the UE can trigger a power headroom report.

[0571] [Option 2-2] When the base station updates the path loss offset for the UE and the change in the updated path loss offset value is greater than a certain / specific threshold, the UE may trigger a power headroom report. In this case, the certain / specific threshold may be defined based on the phr-Tx-PowerFactorChange value [dB] mentioned above or by the value [dB] indicated by the new higher-layer parameter phr-Tx-PowerFactorChangeforULTRP. According to Option 2-2, when the base station updates the path loss offset for the UE via MAC CE (or indicates the same to the UE via RRC reconfiguration or DCI) and the change in the updated path loss offset value is greater than a certain / specific threshold (e.g., the new higher-layer parameter phr-Tx-PowerFactorChangeforULTRPdB), the UE may trigger a power headroom report. Alternatively, when the UE determines whether to trigger a power headroom report, in addition to the certain / specific threshold of Option 2-2, the expiration of the timer (e.g., phr-ProhibitTimer or the new timer phr-ProhibitTimerforULTRP) used to disable power headroom reporting as described in Option 2-1 may be further considered.

[0572] [Option 2-3] When the base station updates the path loss offset for the UE and the transmit power of the uplink signal to be transmitted, calculated with reference to the updated path loss offset, is equal to or greater than the UE's maximum transmit power (PCMAX), the UE may trigger a power headroom report. In Option 2-3, unlike Option 2-1, the UE can determine whether to report a power headroom based not only on the updated path loss offset but also on the transmit power value calculated by the UE for the uplink signal to be transmitted. Alternatively, the UE can determine whether to report a power headroom by additionally considering the expiration of the timer used to disable power headroom reporting as described in Option 2-1 or Option 2-2, in addition to the conditions described in Option 2-3.

[0573] [Option 2-4] The UE may trigger a power headroom report when the base station updates the path loss offset for the UE, the change in the updated path loss offset value is greater than a specific threshold, and the transmit power of the uplink signal to be transmitted, calculated with reference to the updated path loss offset, is equal to or greater than the UE's maximum transmit power (PCMAX). The UE may determine whether to report the power headroom by additionally considering the expiration of the timer for disabling power headroom reporting as described in Option 2-1 or Option 2-2, in addition to the conditions described in Option 2-4.

[0574] [Option 3] When operating UL TRP only, the UE's power headroom report can be triggered by a DCI. As described above, when the path loss value measured by the UE based on DL RS remains unchanged but the received signal strength (e.g., SNR, SINR, or RSRP) of the UL signal received from the UE via UL TRP only changes, the base station can determine that the UE needs to report power headroom. The base station can send a DCI to the UE to trigger the power headroom report. The DCI sent by the base station to the UE to trigger the power headroom report can be a scheduling DCI used to schedule PUSCH transmissions, such as DCI format 0_1 ​​or DCI format 0_2. The base station can additionally schedule PUSCH resources for the UE to send MAC CE format for power headroom reports using DCI format 0_1 ​​or DCI format 0_2. The base station can add a new DCI field for triggering the power headroom report to DCI format 0_1 ​​or DCI format 0_2. The UE can be scheduled to trigger the power headroom report based on the configuration information in the newly added DCI field. The new field included in the DCI for UE to trigger power headroom reporting can be configured with 1 bit. For example, when the 1-bit new field in the DCI is configured to 0, the UE may not perform a power headroom report, and when the 1-bit new field in the DCI is configured to 1, the UE may perform a power headroom report. Alternatively, when the 1-bit new field in the DCI is configured to 1, the UE may not perform a power headroom report, and when the 1-bit new field in the DCI is configured to 0, the UE may perform a power headroom report.

[0575] <Third Embodiment: Method for Calculating Power Margin of UL TRP Only>

[0576] Embodiments of this disclosure illustrate a method for calculating power headroom to report power headroom for uplink channel transmission when UL-only TRP is supported. This embodiment can be combined with other embodiments described in this disclosure.

[0577] When a UE reports power headroom to the base station, it can calculate the reported power headroom value based on the actual transmit power of the uplink signal or based on a reference format. Whether the UE calculates the power headroom based on actual transmission or a reference format can be determined by the timeline in which the UE calculates the power headroom. More specifically, the power headroom of uplink signal transmissions scheduled by a DCI received before the time point of receiving the DCI for the PUSCH of the MAC CE used to send the power headroom report can be calculated based on actual transmission. Alternatively, the power headroom of uplink signal transmissions scheduled by a DCI received before the PUSCH preparation time of the first symbol of the Configuration Grant (CG) PUSCH can be calculated based on actual transmission. Alternatively, the boundaries of the corresponding timeline can be adjusted and determined according to the UE implementation.

[0578] When the UE calculates the Type 1 power margin based on the actual transmission (i.e., the power margin for PUSCH transmission), the UE can determine the power margin value of the TRP that enables uplink reception and downlink transmission according to Equation 16.

[0579] [Equation 16]

[0580] Refer to the actual transmission for the power margin calculation of TRP type 1 that supports both DL and UL.

[0581] The parameters in Equation 16 can represent the same parameters defined in Equation 4.

[0582] When the UE calculates the Type 1 power margin (i.e., the power margin for PUSCH transmission) based on actual transmissions, the UE can determine the power margin value for UL TRP that can support uplink-only reception according to Equation 17 or Equation 18.

[0583] [Equation 17]

[0584] Referencing actual transmission data, power margin calculations are performed for Type 1 TRPs that support only UL.

[0585] [Equation 18]

[0586] Referencing actual transmission data, for TRP types that support only UL, calculate the power margin 1 2.

[0587] Equations 17 and 18 refer to Equations 12 and 13 described in the first embodiment, defining the difference between the UE’s maximum transmit power and the transmit power sent to the PUSCH of UL TRP only as a power margin value.

[0588] When the UE calculates the Type 1 power margin (i.e., the power margin for PUSCH transmission) based on the reference format, the UE can determine the power margin value of the TRP that enables uplink reception and downlink transmission according to Equation 19.

[0589] [Equation 19]

[0590] Refer to the reference format for TRP type 1 power margin calculation that supports both DL and UL.

[0591] here, This is expressed by assuming the maximum allowable power reduction (MPR), additional maximum power reduction (A-MPR), power management maximum power reduction (P-MPR), and allowable transmit power relaxation at the edge of the operating frequency band as defined in TS 38.101-1, TS 38.101-2, and TS38.101-3. =0 dB (i.e., MPR = 0 dB, A-MPR = 0 dB, P-MPR = 0 dB, = 0 dB) and the calculated maximum transmit power of the UE. If ul-powerControl is not configured for the UE, then and pass And p0-PUSCH-AlpharSetId = 0 determines, and By using pusch-PathlossReferenceRS-Id = 0 and OK. If ul-powerControl is configured for the UE, then , and Determined by p0AlphaSetforPUSCH associated with the indicated TCI-State or TCI-UL-State, and Determined by the PL-RS associated with the indicated TCI-State or TCI-UL-State.

[0592] When the UE calculates the Type 1 power margin (i.e., the power margin for PUSCH transmission) based on the reference format, the UE can determine the power margin value that can support uplink-only reception of UL TRP according to Equation 20 or Equation 21.

[0593] [Equation 20]

[0594] Reference format for TRP type 1 power margin calculation that supports UL only 1

[0595] [Equation 21]

[0596] Reference format for TRP type 1 that supports UL only 2 Power margin calculation

[0597] When a power headroom report is triggered for a UE, the UE can calculate the power headroom based on the TRP sent to it, which includes a PUSCH in MAC CE format for power headroom reporting, and based on the actual transmission or reference format, according to one of Equations 16 to 21.

[0598] Alternatively, when the UE calculates the Type 1 power margin as a virtual power margin for UL TRP only (i.e., the power margin for PUSCH transmission) based on the reference format, the UE can use Equation 19 to calculate the power margin instead of Equation 20 or Equation 21, in which the path loss offset is calculated. This should not be applied to the calculation of virtual power headroom. That is, since virtual power headroom is calculated based on a reference format when the UE does not actually send uplink signals to a UL TRP-only uplink, or due to timeline conditions determining whether to calculate actual or virtual power headroom, the UE can calculate virtual power headroom using only Equation 19 without applying the path loss offset value configured by the RRC parameters known to the base station. Specifically, if the base station configures the UE for a UL TRP-only uplink reception and supports PUSCH transmissions based on a single TRP or multiple TRPs including the UL TRP-only, and the UE triggers a power headroom report as described above to perform a power headroom report in the next PUSCH transmission, the UE can calculate the actual power headroom for the UL TRP-only by applying Equation 17 or Equation 18, and can calculate the virtual power headroom for the UL TRP-only by applying Equation 19. Configuring a UL-only TRP for the UE by the base station can mean (1) that the base station can configure a TCI-State or TCI-UL-State for the UE, and (2) that new RRC parameters for indicating path loss offset are additionally configured in some TCI-States or TCI-UL-States. Supporting PUSCH transmission based on a single TRP or multiple TRPs including a UL-only TRP can mean that the base station indicates to the UE a TCI-State or TCI-UL-State to which new RRC parameters for indicating path loss offset have been added, and the UE sends a PUSCH associated with the corresponding TCI-State or TCI-UL-State. The power control parameters used to calculate the actual power margin or virtual power margin by applying Equation 17 or Equation 18, or Equation 19. , and This can be determined by the p0-AlphaSetforPUSCH of the Uplink-PowerControl, which is indicated by the TCI-State or TCI-UL-State associated with the power margin of the UL TRP only, and The PL-RS can be determined by the PathlossReferenceRS-Id indicated by the TCI-State or TCI-UL-State associated with the power margin of only ULTRP.

[0599] Figures 15a to 15d An example is shown whereby the UE reports the power margin for triggering a single carrier to the base station via DCI-based dynamically granted PUSCH resources.

[0600] refer to Figure 15a The UE can report triggered power headroom information 1500 to the base station via the PUSCH 1502 resource scheduled by DCI 1501. The PUSCH 1502 scheduled by DCI 1501 can be sent to a TRP that supports both DL and UL. In this case, the UE can calculate the power headroom according to Equation 16, taking into account the actual transmission of the PUSCH, and can send a MAC CE including the calculated power headroom value via the scheduled PUSCH 1502.

[0601] refer to Figure 15b The UE can report triggered power margin information 1510 to the base station via the PUSCH 1512 resource scheduled by DCI 1511. The PUSCH 1512 scheduled by DCI 1511 can be sent to a UL-only TRP that only supports UL. In this case, the UE can calculate the power margin according to Equation 17 or Equation 18, taking into account the actual transmission of the PUSCH, and can send a MAC CE including the calculated power margin value via the scheduled PUSCH 1512.

[0602] refer to Figure 15cThe UE can report triggered power margin information 1520 to the base station via PUSCH 1522 resources scheduled by DCI 1521, or via both the first PUSCH 1522 and the second PUSCH 1523 resources. The first PUSCH 1522 and the second PUSCH 1523 scheduled by DCI 1521 may or may not overlap in the time domain, and both PUSCH 1522 and 1523 may be repeatedly sent to different TRPs. If the first PUSCH 1522 and the second PUSCH 1523 scheduled by DCI 1521 do not overlap in the time domain but are both scheduled for transmission in time slot n 1525, the UE can perform power margin calculations differently depending on whether the higher-layer parameter twoPHRMode is configured (or a new higher-layer parameter introduced when considering only UL TRPs, such as twoPHRModeforULonly. For ease of description, it is assumed that twoPHRMode is reused, but new higher-layer parameters can be introduced).

[0603] When the first PUSCH 1522 and the second PUSCH 1523, scheduled by DCI 1521, do not overlap in the time domain but are both scheduled to be transmitted within time slot n 1525, and the UE supports twoPHRMode, the UE can calculate both the power margin sent to PUSCH 1522, which can support both DL and UL, and the power margin sent to PUSCH 1523, which can only support UL, based on the actual transmission. That is, the UE can calculate the power margin sent to PUSCH 1522, which can support both DL and UL, according to Equation 16, and calculate the power margin sent to PUSCH 1523, which can only support UL, according to Equation 17 or Equation 18, and send them to the base station.

[0604] When the first PUSCH 1522 and the second PUSCH 1523 scheduled by DCI 1521 do not overlap in the time domain but are both scheduled to be transmitted within time slot n 1525 and the UE does not support twoPHRMode, the UE can only calculate the power margin for PUSCH 1522 sent to TRPs that support both DL and UL based on actual transmission and report it to the base station. That is, the UE can calculate the power margin for PUSCH 1522 sent to TRPs that support both DL and UL according to Equation 16 and report it to the base station, but can choose not to report the power margin for PUSCH 1523 sent to TRPs that only support UL. Alternatively, for supporting cells that support only UL TRPs, the UE can unconditionally calculate the power margin for PUSCH 1523 sent to TRPs that only support UL based on actual transmission and report it to the base station. That is, the UE can calculate the power margin sent to PUSCH 1523, which can only support UL, according to Equation 17 or Equation 18, and report it to the base station, but may not report the power margin sent to PUSCH 1522, which can support both DL and UL.

[0605] If the first PUSCH 1522 and the second PUSCH 1523 scheduled by DCI 1521 overlap in the time domain and are both scheduled to be transmitted in time slot n 1525, then the power margin reported by the UE and the equation to be referenced for calculating the power margin can be determined in the same way as above (the case where the first PUSCH 1522 and the second PUSCH 1523 scheduled by DCI 1521 do not overlap in the time domain but are both scheduled to be transmitted in time slot n 1525) depending on whether twoPHRMode is supported.

[0606] If the first PUSCH 1526 and the second PUSCH 1527 scheduled by DCI 1521 do not overlap in the time domain and neither PUSCH 1526 nor 1527 is scheduled to be transmitted in time slot n 1525, then the UE can perform power margin calculation differently depending on whether the higher-layer parameter twoPHRMode is configured, as follows.

[0607] More specifically, when the first PUSCH 1526 and the second PUSCH 1527 scheduled by DCI 1521 do not overlap in the time domain and are not scheduled to be transmitted in time slot n 1525, and the UE supports twoPHRMode, the UE can calculate the power margin sent to PUSCH 1522, which can support both DL and UL, based on the actual transmission, and calculate the power margin sent to PUSCH 1523, which can only support UL, based on the reference format. That is, the UE can calculate the power margin sent to PUSCH 1522, which can support both DL and UL, according to Equation 16, and calculate the power margin sent to PUSCH 1523, which can only support UL, according to Equation 20 or Equation 21, and send the calculated power margin to the base station.

[0608] Furthermore, when the first PUSCH 1526 and the second PUSCH 1527 scheduled by DCI 1521 do not overlap in the time domain and are not scheduled to be transmitted in time slot n 1525, and the UE does not support twoPHRMode, the UE can calculate the power margin for PUSCH 1522 sent to TRPs that support both DL and UL based on actual transmission and report it to the base station. That is, the UE can calculate the power margin for PUSCH 1522 sent to TRPs that support both DL and UL according to Equation 16 and report it to the base station, but may not report the power margin for PUSCH 1523 sent to TRPs that only support UL. Alternatively, for supporting cells that support only UL TRPs, the UE can unconditionally calculate the power margin for PUSCH 1523 sent to TRPs that only support UL based on actual transmission and report it to the base station. That is, the UE can calculate the power margin sent to PUSCH 1523, which can only support UL, according to Equation 17 or Equation 18, and report it to the base station, but may not report the power margin sent to PUSCH 1522, which can support both DL and UL.

[0609] The first PUSCH 1522 and the second PUSCH 1523 scheduled by DCI 1521 may or may not overlap in the time domain, and different data (or TB or layer) may be transmitted in the two PUSCH 1522 and 1523. Even if the UE transmits different data via two PUSCHs 1522 and 1523, the UE can calculate the power margin in the same way as described above (the power margin calculation method described in the cases where the first PUSCH 1522 and the second PUSCH 1523 scheduled by DCI 1521 do not overlap in the time domain and both PUSCHs 1526 and 1527 are scheduled for transmission in time slot n 1525; the cases where the first PUSCH 1522 and the second PUSCH 1523 scheduled by DCI 1521 do not overlap in the time domain and neither PUSCH 1526 nor 1527 are scheduled for transmission in time slot n 1525; or the cases where the first PUSCH 1522 and the second PUSCH 1523 scheduled by DCI 1521 overlap in the time domain and both PUSCHs 1526 and 1527 are scheduled for transmission in time slot n 1525). The power margin is calculated via the first PUSCH. The UE can report this to the base station via PUSCH 1522 (or the second PUSCH 1523). Alternatively, even if different data is transmitted via the two PUSCHs 1522 and 1523, the UE can multiplex and transmit a MAC CE including power margin in both PUSCHs 1522 and 1523. Alternatively, in a different manner than described above, the UE can calculate the power margin of any PUSCH (i.e., the PUSCH in which the MAC CE for power margin reporting is transmitted or the first PUSCH 1522) based on actual transmission, regardless of whether both PUSCHs 1522 and 1523 are transmitted within time slot n 1525 (e.g., when the UE supports twoPHRMode), and calculate the power margin of the other PUSCH (i.e., the PUSCH in which the MAC CE for power margin reporting is transmitted or the second PUSCH 1523) based on a reference format. Alternatively, the UE may calculate the power headroom of only one PUSCH (i.e., the PUSCH 1522 or the first PUSCH 1522 in which the MAC CE for power headroom reporting is transmitted, based on the actual transmission, regardless of whether both PUSCH 1522 and 1523 are transmitted within time slot n 1525 (e.g., when the UE does not support twoPHRMode), and report it to the base station. It may not perform power headroom reporting for the other PUSCH (i.e., the PUSCH 1523 in which the MAC CE for power headroom reporting is not transmitted).

[0610] refer to Figure 15dThe UE can report triggered power margin information 1530 to the base station via PUSCH 1532 resources scheduled by DCI 1531, or via both the first PUSCH 1532 and the second PUSCH 1533 resources. The first PUSCH 1532 and the second PUSCH 1533 scheduled by DCI 1531 may or may not overlap in the time domain, and both PUSCH 1532 and 1533 may be repeatedly sent to different TRPs. If the first PUSCH 1532 and the second PUSCH 1533 scheduled by DCI 1531 do not overlap in the time domain but are both scheduled for transmission in time slot n 1535, the UE can perform power margin calculations differently depending on whether the higher-layer parameter twoPHRMode is configured (or a new higher-layer parameter introduced when considering only UL TRPs, such as twoPHRModeforULonly. For ease of description, it is assumed that twoPHRMode is reused, but new higher-layer parameters can be introduced).

[0611] More specifically, when the first PUSCH 1532 and the second PUSCH 1533 scheduled by DCI 1531 do not overlap in the time domain but are both scheduled to be transmitted within time slot n 1535 and the UE supports twoPHRMode, the UE can calculate both the power margin sent to the PUSCH 1532 that can only support UL TRP and the power margin sent to the PUSCH 1533 that can support both DL and UL TRP based on the actual transmission. That is, the UE can calculate the power margin sent to the PUSCH 1532 that can only support UL TRP according to Equation 17 or Equation 18, and calculate the power margin sent to the PUSCH 1533 that can support both DL and UL TRP according to Equation 16, and send them to the base station.

[0612] Furthermore, when the first PUSCH 1532 and the second PUSCH 1533 scheduled by DCI 1531 do not overlap in the time domain but are both scheduled to be transmitted within time slot n 1535 and the UE does not support twoPHRMode, the UE can calculate only the power margin sent to the PUSCH 1532 that can only support UL based on the actual transmission and report it to the base station. That is, the UE can calculate the power margin sent to the PUSCH 1532 that can support UL only according to Equation 17 or Equation 18 and report it to the base station, but may not report the power margin sent to the PUSCH 1533 that can support both DL and UL. Alternatively, for a supporting cell that supports only UL TRPs, the UE can unconditionally calculate the power margin sent to the PUSCH 1533 that can support both DL and UL based on the actual transmission and report it to the base station. That is, the UE can calculate the power margin sent to PUSCH 1533, which is capable of supporting both DL and UL, according to Equation 16, and report it to the base station, but may not report the power margin sent to PUSCH 1532, which is capable of supporting only UL.

[0613] If the first PUSCH 1532 and the second PUSCH 1533 scheduled by DCI 1531 overlap in the time domain and are both scheduled to be transmitted in time slot n 1535, then the power margin reported by the UE and the equation to be referenced for calculating the reported power margin can be determined in the same way as described above (the power margin calculation method described in the case where the first PUSCH 1532 and the second PUSCH 1533 scheduled by DCI 1531 do not overlap in the time domain but are both scheduled to be transmitted in time slot n 1535) depending on whether twoPHRMode is supported.

[0614] If the first PUSCH 1536 and the second PUSCH 1537 scheduled by DCI 1531 do not overlap in the time domain and neither PUSCH 1536 nor 1537 is scheduled to be transmitted in time slot n 1535, the UE may perform power margin calculation differently depending on whether the higher-layer parameter twoPHRMode is configured.

[0615] More specifically, when the first PUSCH 1536 and the second PUSCH 1537 scheduled by DCI 1531 do not overlap in the time domain and are not scheduled to be transmitted in time slot n 1535, and the UE supports twoPHRMode, the UE can calculate the power margin sent to PUSCH 1532, which can only support UL, based on the actual transmission, and calculate the power margin sent to PUSCH 1533, which can support both DL and UL, based on the reference format. That is, the UE can calculate the power margin sent to PUSCH 1532, which can only support UL, according to Equation 17 or Equation 18, and calculate the power margin sent to PUSCH 1533, which can support both DL and UL, according to Equation 19, and send the calculated power margin to the base station.

[0616] Furthermore, when the first PUSCH 1536 and the second PUSCH 1537 scheduled by DCI 1531 do not overlap in the time domain and are not scheduled to be transmitted in time slot n 1535, and the UE does not support twoPHRMode, the UE can calculate the power margin to be sent to PUSCH 1532, which can only support UL, based on the actual transmission and report it to the base station. That is, the UE can calculate the power margin to be sent to PUSCH 1532, which can only support UL, according to Equation 17 or Equation 18 and report it to the base station, but may not report the power margin to PUSCH 1533, which can support both DL and UL.

[0617] Furthermore, for cells supporting only UL TRPs, the UE can unconditionally calculate the power margin for PUSCH 1533, which supports both DL and UL TRPs, based on actual transmissions, and report it to the base station. That is, the UE can calculate the power margin for PUSCH 1533, which supports both DL and UL TRPs, according to Equation 16 and report it to the base station, but may not report the power margin for PUSCH 1532, which supports only UL TRPs.

[0618] The first PUSCH 1532 and the second PUSCH 1533 scheduled by DCI 1531 may or may not overlap in the time domain, and different data (or TB or layer) may be transmitted in the two PUSCH 1532 and 1533. Even if the UE transmits different data through two PUSCH 1532 and 1533, the UE can calculate the power margin in the same way as described above (the power margin calculation method described in the cases where the first PUSCH 1532 and the second PUSCH 1533 scheduled by DCI 1531 overlap in the time domain and are both scheduled to be transmitted in time slot n 1535, the first PUSCH 1532 and the second PUSCH 1533 scheduled by DCI 1531 do not overlap in the time domain and are both scheduled to be transmitted in time slot n 1535, or the first PUSCH 1532 and the second PUSCH 1533 scheduled by DCI 1531 do not overlap in the time domain and are not scheduled to be transmitted in time slot n 1535) and report it to the base station through the first PUSCH 1532 (or the second PUSCH 1533). Alternatively, even if different data is transmitted via two PUSCHs 1532 and 1533, the UE can multiplex and transmit a MAC CE including power margin in both PUSCHs 1532 and 1533. Alternatively, in a different manner, the UE can calculate the power margin of any PUSCH (i.e., the PUSCH in which the MAC CE for power margin reporting is transmitted or the first PUSCH 1532) based on actual transmission, regardless of whether both PUSCHs 1532 and 1533 are transmitted within time slot n 1535 (e.g., when the UE supports twoPHRMode), and calculate the power margin of the other PUSCH (i.e., the PUSCH in which the MAC CE for power margin reporting is transmitted or the second PUSCH 1533) based on a reference format. Alternatively, the UE may calculate the power margin of only one PUSCH (i.e., the PUSCH 1532 or 1533 in which the MAC CE for power margin reporting is transmitted or the first PUSCH 1532) based on the actual transmission, regardless of whether both PUSCH 1532 and 1533 are transmitted within time slot n 1535 (e.g., when the UE does not support twoPHRMode), and may not perform power margin reporting for the other PUSCH (i.e., the PUSCH 1533 in which the MAC CE for power margin reporting is not transmitted or the second PUSCH 1533).

[0619] When reporting power margin to the base station using the MAC CE format for multi-entry power margin reporting while considering multiple supporting cells, the UE determines the power margin according to Equation 17 or Equation 18 when calculating the power margin report for supporting cells supporting only UL TRP based on actual transmission, and can determine the power margin according to Equation 20 or Equation 21 when calculating the power margin report based on the reference format.

[0620] Although the method for reporting type 1 power headroom has been specifically described in the third embodiment, the equation for calculating power headroom described in the third embodiment can be similarly applied to the calculation of power headroom for SRS transmissions when reporting type 3 power headroom based on SRS. The UE can select a power headroom calculation method from various power headroom calculation methods modified for SRS transmissions based on the TRP to which the PUSCH, including the type 3 power headroom MAC CE format, is to be sent.

[0621] <Fourth Embodiment: Method for Configuring MAC CE Format for Reporting Power Margin Only for UL TRP>

[0622] Embodiments of this disclosure illustrate a method for configuring a MAC CE format for reporting power margins for uplink channel transmissions when UL TRP-only is supported. This embodiment can be operated in combination with other embodiments described in this disclosure.

[0623] As described in the third embodiment, depending on whether the UE supports twoPHRMode, it can report two power margin values ​​considering multiple TRPs to the base station, or it can report only one power margin value to the base station.

[0624] If the UE supports twoPHRMode and reports two power margin values ​​to the base station during the power margin reporting period, the first power margin value and the second power margin value can be determined according to the following rules.

[0625] [Rule 1] The UE may define a first power margin value as the power margin for transmission of a first PUSCH 1522, 1526, 1532, or 1536 among the multiple PUSCHs shown in Figure 15, and may define a second power margin value as the power margin for transmission of a second PUSCH 1523, 1527, 1533, or 1537. Alternatively, the UE may define a first power margin value as the power margin for PUSCHs transmitted associated with a first SRS resource set (or an SRS resource set with a lower SRS resource set ID), and may define a second power margin value as the power margin for PUSCHs transmitted associated with a second SRS resource set (or an SRS resource set with a higher SRS resource set ID).

[0626] [Rule 2] The UE may define a first power margin value as the power margin for PUSCH 1522, 1526, 1533, or 1537 among a plurality of PUSCHs that are sent to TRPs capable of supporting both DL and UL, and may define a second power margin value as the power margin for PUSCH 1523, 1527, 1532, or 1536 among a plurality of PUSCHs that are sent to TRPs capable of supporting only UL. In this case, in order to calculate the transmit power of uplink transmission during uplink transmission, the UE may identify TRPs capable of supporting both DL and UL and TRPs capable of supporting only UL based on whether a path loss offset is applied. The UE may refer to higher-layer parameters or indicated TCI states to identify the path loss offset to be applied to TRPs capable of supporting only UL, as described in the first embodiment.

[0627] [Rule 3] The UE can report power headroom to the base station using an enhanced MAC CE format. When twoPHRMode is supported, the UE can indicate the type of TRP associated with each power headroom by using additional bits in the MAC CE format used to report power headroom to the base station. For example, 1 bit corresponding to the field used to report each power headroom value can be added to the MAC CE format used to report power headroom to the base station. The 1 bit corresponding to the first power headroom field can indicate whether the value indicated by the power headroom field is calculated based on an uplink transmission to a TRP that supports both DL and UL, or based on an uplink transmission to a TRP that only supports UL. Additional bits indicating the type of TRP associated with each power headroom can be provided by adding a new bit field or by reusing reserved bits.

[0628] Figure 16 An example of an enhanced MAC CE format, in which a field of the TRP type associated with each power margin field is added when twoPHRMode is supported, is shown according to an embodiment of this disclosure.

[0629] MAC CE format 1600 illustrates a PHR MAC CE for reporting two power margins with a single entry. The UE can report the power margin level for reporting quantized power margin values ​​to the base station via multiple PH fields 1601 and 1604. The uplink transmission associated with the power margin reported via each PH field can be determined according to Rule 1 or Rule 2 above. If the higher-layer parameter mpe-Reporting-FR2 for MPE reporting is configured for a serving cell operating in FR2, the UE can configure P field 1602 to 0 when applying a P-MPR value less than P-MPR_00 as defined in the RAN4 specification (e.g., TS 38.101-2) to satisfy the MPE requirements for PH reporting corresponding to a serving cell operating in FR2, and can configure P field 1602 to 1 when applying a P-MPR value greater than P-MPR_00 as defined in the RAN4 specification to satisfy the MPE requirements for PH reporting corresponding to a serving cell operating in FR2. When the UE calculates the PH value reported by the corresponding PH fields 1601 and 1604 based on the actual transmission, the UE configures the V field 1603 to 0, and when the UE calculates the PH value reported by the corresponding PH fields 1601 and 1604 based on the reference format, the UE configures the V field 1603 to 1.

[0630] To report the maximum UE transmit power used to determine the reported pH value. The UE can determine the nominal UE transmit power level as defined in the RAN4 specification (e.g., TS 38.133) and report the index of the determined nominal UE transmit power level to the base station via the PCMAX,f,c field 1605. If the higher-layer parameter mpe-Reporting-FR2 for MPE reporting is configured for the serving cell operating in FR2 and the P field 1602 is configured to 1, the UE can configure the MPE field 1606 to indicate the power backoff applied to the PH report corresponding to the serving cell operating in FR2 in order to meet the MPE requirements. In this case, the UE determines the P-MPR level as defined in the RAN4 specification (e.g., TS 38.101-2) and reports its index to the base station via the MPE field 1606.

[0631] Figure 16The Ti fields 1607 and 1608 can be defined as bit fields used to indicate the TRP type associated with each power margin according to Rule 3. That is, T1 1607 is a 1-bit field corresponding to the first power margin field 1601, and can indicate whether the value indicated by the power margin field 1601 is calculated based on uplink transmissions to TRPs supporting both DL and UL, or based on uplink transmissions to TRPs supporting only UL. For example, T1 1607 being indicated as 0 could mean that the first power margin field 1601 is calculated based on uplink transmissions to TRPs supporting both DL and UL. T1 1607 being indicated as 1 could mean that the first power margin field 1601 is calculated based on uplink transmissions to TRPs supporting only UL (and vice versa). Similarly, T2 1608 corresponds to 1 bit of the second power headroom field 1604 and can indicate whether the value indicated by the power headroom field 1604 is calculated based on uplink transmissions to TRPs supporting both DL and UL, or based on uplink transmissions to TRPs supporting only UL. For example, T2 1608 being indicated as 0 could mean that the second power headroom field 1604 is calculated based on uplink transmissions to TRPs supporting both DL and UL. T2 1608 being indicated as 1 could mean that the second power headroom field 1604 is calculated based on uplink transmissions to TRPs supporting only UL (and vice versa).

[0632] Rules 1 through 3 above can be used in combination. For example, MAC CE format can be configured by combining rule 1 and rule 3 or by combining rule 2 and rule 3.

[0633] As described in the first to fourth embodiments, additional UE capabilities may be required to support UL TRP only and to support enhanced power headroom reporting for effective support of UL TRP only. When the UE supports additional UE capabilities, the UE can support UL TRP only and perform enhanced power headroom reporting. The UE capability supporting UL TRP only and the UE capability supporting enhanced power headroom reporting can be reported to the base station through separate parameters for UE capability reporting. That is, the UE can support UL TRP only but may not support enhanced power headroom reporting. Alternatively, the UE can support both UL TRP only and the corresponding enhanced power headroom reporting. Additional UE capability reports for supporting enhanced power headroom may include both new power headroom triggering conditions and a method for configuring power headroom MAC CE, or the new power headroom triggering conditions and the method for configuring power headroom MAC CE can be reported separately through separate UE capability reporting parameters.

[0634] The flowcharts above illustrate exemplary methods that can be implemented according to the principles of this disclosure, and various modifications can be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the various steps in each diagram may overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, steps may be omitted or replaced by other steps.

[0635] Figure 17 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0636] refer to Figure 17 The UE may include transceivers, collectively referred to as UE receiver 17-00 and UE transmitter 17-10, memory (not shown), and UE processor 17-05 (or UE controller or processor). UE transceivers 17-00 and 17-10, memory, and UE processor 17-05 may operate according to the communication method of the UE described above. However, the components of the UE are not limited to the examples described above. For example, the UE may also include more or fewer components than those described above. Furthermore, the transceivers, memory, and processor may be implemented as a single chip.

[0637] A transceiver can transmit / receive signals with a base station. These signals can include control information and data. For this purpose, a transceiver may include an RF transmitter configured to perform frequency amplification and up-conversion of the transmitted signals, an RF receiver configured to perform low-noise amplification and down-conversion of the received signals, and so on. However, this is merely one embodiment of a transceiver, and the components of the transceiver are not limited to RF transmitters and RF receivers.

[0638] In addition, the transceiver can receive signals via a wireless channel, output them to the processor, and transmit signals output from the processor via a wireless channel.

[0639] The memory can store the programs and data required for the UE to run. Additionally, the memory can store control information or data included in signals sent / received by the UE. The memory can include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Furthermore, the memory can include multiple memories.

[0640] The processor can control a series of processes that enable the UE to operate according to the embodiments described above. For example, the processor can control the UE's components to receive DCIs configured in two layers to receive multiple PDSCHs simultaneously. The processor may include multiple processors, and the processors can perform control operations on the UE's components by executing programs stored in memory.

[0641] Figure 18 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown.

[0642] refer to Figure 18 The base station may include transceivers, collectively referred to as base station receiver 18-00 and base station transmitter 18-10, memory (not shown), and base station processor 18-05 (or base station controller or processor). Base transceivers 18-00 and 18-10, memory, and base station processor 18-05 may operate according to the communication methods described above for the base station. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than those described above. Furthermore, the transceivers, memory, and processor may be implemented as a single chip.

[0643] A transceiver can transmit / receive signals with a UE. These signals may include control information and data. For this purpose, a transceiver may include an RF transmitter configured to perform frequency amplification and up-conversion of the transmitted signals, an RF receiver configured to perform low-noise amplification and down-conversion of the received signals, and so on. However, this is merely one embodiment of a transceiver, and the components of the transceiver are not limited to RF transmitters and RF receivers.

[0644] In addition, the transceiver can receive signals via a wireless channel, output them to the processor, and transmit signals output from the processor via a wireless channel.

[0645] Furthermore, the base station according to embodiments of this disclosure can be a base station operating as a multi-TRP. In this case, a TRP capable of uplink reception and downlink transmission, as well as a TRP that only supports uplink reception, can operate together in the base station. The TRPs operating in the base station capable of uplink reception and downlink transmission may include... Figure 18 The base station receiver 18-00 and base station transmitter 18-10 are included. A TRP operating in the base station that only supports uplink reception may include only... Figure 18 The base station receiver 18-00 in the base station. For example, if a TRP capable of uplink reception and downlink transmission and a TRP that only supports uplink reception are operated in the base station, the base station may include (1) a base station receiver 18-00 and a base station transmitter 18-10 constituting a TRP capable of uplink reception and downlink transmission, and (2) a base station receiver 18-00 constituting a TRP that only supports uplink reception.

[0646] The memory can store programs and data required for base station operation. Additionally, the memory can store control information or data included in signals transmitted / received by the UE. The memory can include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or combinations of storage media. Furthermore, the memory can include multiple memories.

[0647] The processor can control a series of processes that enable the base station to operate according to the embodiments described above. For example, the processor can control each component of the base station to configure and transmit a two-layer DCI including allocation information for multiple PDSCHs. The processor may include multiple processors, and the processors can perform control operations on the components of the base station by executing programs stored in memory.

[0648] The methods disclosed in the claims or the methods of the embodiments described in this disclosure can be implemented by hardware, software, or a combination of hardware and software.

[0649] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). The one or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors within an electronic device. The at least one program includes instructions that cause the electronic device to perform methods according to various embodiments of the present disclosure as defined in the appended claims and / or as disclosed herein.

[0650] These programs (software modules or software) can be stored in non-volatile memory, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, compact disc ROM (CD-ROM), digital versatile disc (DVD) or other types of optical storage devices, or magnetic tape cassettes. Alternatively, the program can be stored in memory configured as some or all of these combinations. Furthermore, multiple such memories may be included.

[0651] Furthermore, the program can be stored in an attachable storage device that can be accessed by the electronic device via a communication network, such as the Internet, intranet, local area network (LAN), wide area network (WLAN), and storage area network (SAN) or a combination thereof. Such a storage device can be accessed by the electronic device via an external port. Additionally, a separate storage device on the communication network can access the device used to execute embodiments of this disclosure.

[0652] In the specific embodiments of this disclosure described above, the components included in the embodiments are represented in a singular or plural form according to the specific embodiments presented. However, the choice of singular or plural form is for ease of interpretation and appropriate to the presented context; this disclosure is not limited to the singular or plural number of components, and even components described in plural form may consist of a single unit, while components described in singular form may consist of multiple units.

[0653] The embodiments of this disclosure described and illustrated in the specification and drawings are merely specific examples presented to facilitate the explanation of the technical content of this disclosure and to aid in understanding it, and are not intended to limit the scope of this disclosure. That is, it will be apparent to those skilled in the art that other variations based on the technical concept of this disclosure can be implemented. Furthermore, the various embodiments described above can be combined where necessary. As an example, a portion of one embodiment of this disclosure can be combined with a portion of another embodiment to operate a base station and a terminal. As an example, a portion of a first embodiment of this disclosure can be combined with a portion of a second embodiment to operate a base station and a terminal. Moreover, other variations based on the technical concept of the embodiments can also be implemented in other communication systems (such as FDD LTE, TDD LTE, 5G, or NR systems).

[0654] In the accompanying drawings illustrating the methods of this disclosure, the order described does not always correspond to the order in which the steps are performed, and the order between the steps may be changed or the steps may be performed in parallel.

[0655] In the accompanying drawings illustrating the methods of this disclosure, the order described does not always correspond to the order in which the steps are performed, and the order between the steps may be changed or the steps may be performed in parallel.

[0656] Furthermore, in the methods of this disclosure, some or all of the contents of each embodiment may be combined to implement the methods without departing from the basic spirit and scope of this disclosure.

[0657] Various embodiments of this disclosure have been described above. The above description of this disclosure is for illustrative purposes and is not intended to limit the embodiments of this disclosure to those set forth herein. Those skilled in the art will understand that other specific modifications and changes can be readily made to the form of this disclosure without altering its technical concept or essential characteristics. The scope of this disclosure is defined by the appended claims rather than the detailed description above, and the scope of this disclosure should be construed as including all changes or modifications derived from the meaning and scope of the claims and their equivalents.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: The system receives downlink control information (DCI), which schedules resources for transmitting a first physical uplink shared channel (PUSCH) and a second PUSCH. The first PUSCH is associated with a first transmit-receive point (TRP) for uplink transmission and downlink reception of the terminal, and the second PUSCH is associated with a second TRP for uplink transmission only of the terminal. Send a Power Headroom Report (PHR), the PHR including at least one of a first PHR associated with the first PUSCH or a second PHR associated with the second PUSCH. The first PHR is calculated based on the downlink path loss obtained using a reference signal. Wherein, the second PHR is calculated based on the downlink path loss and path loss offset, and Specifically, when both the first PHR and the second PHR are configured to be transmitted, both the first PUSCH and the second PUSCH are transmitted in the time slot n in which the PHR is transmitted, and the first PUSCH is scheduled at an earlier time than the second PUSCH, the PHR including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH are transmitted.

2. The method according to claim 1, wherein, Both the first PHR and the second PHR are configured to be transmitted. Both the first PUSCH and the second PUSCH are transmitted in the time slot n. The second PUSCH is scheduled at an earlier time than the first PUSCH. The PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH are transmitted.

3. The method according to claim 2, wherein, When both the first PHR and the second PHR are configured to be transmitted and only the first PUSCH is transmitted in the time slot n, a PHR including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the reference transmission of the second PUSCH is transmitted, and Where both the first PHR and the second PHR are configured to be transmitted and only the second PUSCH is transmitted in the time slot n, the PHR including the first PHR calculated based on the reference transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH is transmitted.

4. The method according to claim 3, wherein, If only one of the first PHR and the second PHR is configured to send... Only PHRs related to the PHRs of the first and second PUSCHs that were scheduled earlier are sent, and In the case where a PUSCH scheduled at an earlier time is transmitted in time slot n, the PHR associated with the PUSCH scheduled at an earlier time is calculated based on the actual transmission of the PUSCH scheduled at an earlier time.

5. A method performed by a base station in a wireless communication system, the method comprising: Sending downlink control information (DCI), the DCI scheduling resources for sending a first physical uplink shared channel (PUSCH) and a second PUSCH, the first PUSCH being associated with a first transmit-receive point (TRP) for uplink transmission and downlink reception of the terminal, and the second PUSCH being associated with a second TRP for uplink transmission only of the terminal; and Receive Power Headroom Report (PHR), wherein the PHR includes at least one of a first PHR associated with the first PUSCH or a second PHR associated with the second PUSCH. The first PHR is calculated based on the downlink path loss obtained using a reference signal. Wherein, the second PHR is calculated based on the downlink path loss and path loss offset, and Specifically, when both the first PHR and the second PHR are configured to be transmitted, both the first PUSCH and the second PUSCH are transmitted in the time slot n in which the PHR is transmitted, and the first PUSCH is scheduled at an earlier time than the second PUSCH, the PHR including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH are transmitted.

6. The method according to claim 5, wherein, Both the first PHR and the second PHR are configured to be transmitted. Both the first PUSCH and the second PUSCH are transmitted in the time slot n. The second PUSCH is scheduled at an earlier time than the first PUSCH. The PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH are transmitted.

7. The method according to claim 6, wherein, When both the first PHR and the second PHR are configured to be transmitted and only the first PUSCH is transmitted in the time slot n, a PHR including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the reference transmission of the second PUSCH is transmitted, and Where both the first PHR and the second PHR are configured to be transmitted and only the second PUSCH is transmitted in the time slot n, the PHR including the first PHR calculated based on the reference transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH is transmitted.

8. The method according to claim 7, wherein, If only one of the first PHR and the second PHR is configured to send... Only PHRs related to the PHRs of the first and second PUSCHs that were scheduled earlier are sent, and In the case where a PUSCH scheduled at an earlier time is transmitted in time slot n, the PHR associated with the PUSCH scheduled at an earlier time is calculated based on the actual transmission of the PUSCH scheduled at an earlier time.

9. A terminal in a wireless communication system, the terminal comprising: transceiver; as well as The controller is connected to the transceiver. The controller is configured as follows: The system receives downlink control information (DCI), which schedules resources for transmitting a first physical uplink shared channel (PUSCH) and a second PUSCH. The first PUSCH is associated with a first transmit-receive point (TRP) for uplink transmission and downlink reception of the terminal, and the second PUSCH is associated with a second TRP for uplink transmission only of the terminal. Send a Power Headroom Report (PHR), the PHR including at least one of a first PHR associated with the first PUSCH or a second PHR associated with the second PUSCH. The first PHR is calculated based on the downlink path loss obtained using a reference signal. Wherein, the second PHR is calculated based on the downlink path loss and path loss offset, and Specifically, when both the first PHR and the second PHR are configured to be transmitted, both the first PUSCH and the second PUSCH are transmitted in the time slot n in which the PHR is transmitted, and the first PUSCH is scheduled at an earlier time than the second PUSCH, the PHR including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH are transmitted.

10. The terminal according to claim 9, wherein, Both the first PHR and the second PHR are configured to be transmitted. Both the first PUSCH and the second PUSCH are transmitted in the time slot n. The second PUSCH is scheduled at an earlier time than the first PUSCH. The PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH are transmitted.

11. The terminal according to claim 10, wherein, When both the first PHR and the second PHR are configured to be transmitted and only the first PUSCH is transmitted in the time slot n, a PHR including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the reference transmission of the second PUSCH is transmitted, and Where both the first PHR and the second PHR are configured to be transmitted and only the second PUSCH is transmitted in the time slot n, the PHR including the first PHR calculated based on the reference transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH is transmitted.

12. The terminal according to claim 11, wherein, If only one of the first PHR and the second PHR is configured to send... Only PHRs related to the PHRs of the first and second PUSCHs that were scheduled earlier are sent, and In the case where a PUSCH scheduled at an earlier time is transmitted in time slot n, the PHR associated with the PUSCH scheduled at an earlier time is calculated based on the actual transmission of the PUSCH scheduled at an earlier time.

13. A base station in a wireless communication system, the base station comprising: transceiver; as well as The controller is connected to the transceiver. The controller is configured as follows: Sending downlink control information (DCI), the DCI scheduling resources for sending a first physical uplink shared channel (PUSCH) and a second PUSCH, the first PUSCH being associated with a first transmit-receive point (TRP) for uplink transmission and downlink reception of the terminal, and the second PUSCH being associated with a second TRP for uplink transmission only of the terminal; and Receive Power Headroom Report (PHR), wherein the PHR includes at least one of a first PHR associated with the first PUSCH or a second PHR associated with the second PUSCH. The first PHR is calculated based on the downlink path loss obtained using a reference signal. Wherein, the second PHR is calculated based on the downlink path loss and path loss offset, and Specifically, when both the first PHR and the second PHR are configured to be transmitted, both the first PUSCH and the second PUSCH are transmitted in the time slot n in which the PHR is transmitted, and the first PUSCH is scheduled at an earlier time than the second PUSCH, the PHR including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH are transmitted.

14. The base station according to claim 13, wherein, Both the first PHR and the second PHR are configured to be transmitted. Both the first PUSCH and the second PUSCH are transmitted in the time slot n. The second PUSCH is scheduled at an earlier time than the first PUSCH. The PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH are transmitted.

15. The base station according to claim 14, wherein, When both the first PHR and the second PHR are configured to be transmitted and only the first PUSCH is transmitted in the time slot n, a PHR including the first PHR calculated based on the actual transmission of the first PUSCH and the second PHR calculated based on the reference transmission of the second PUSCH is transmitted, and Where both the first PHR and the second PHR are configured to be transmitted and only the second PUSCH is transmitted in the time slot n, the PHR including the first PHR calculated based on the reference transmission of the first PUSCH and the second PHR calculated based on the actual transmission of the second PUSCH is transmitted.