Method and apparatus for transmitting phase tracking reference signal based on simultaneous transmission across multiple panels in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. In particular, the present disclosure provides a method and apparatus for uplink transmission taking into account simultaneous transmissions across multiple panels.

Description

Technical Field

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system (or mobile communication system). Specifically, the present disclosure relates to a method for performing simultaneous uplink transmission using multiple panels in a wireless communication system, a method for configuring a reference signal for phase tracking when transmitting a reference signal for corresponding operation, a method for transmitting the configured reference signal together with a scheduled uplink channel, and a device capable of performing the method. Background Art

[0002] 5G mobile communication technology defines a wide frequency band to enable high transmission rates and new services, and is achievable not only in "sub-6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands, known as millimeter waves (mmWave), including 28 GHz and 39 GHz. Furthermore, consideration is being given to implementing 6G mobile communication technology (referred to as a "super 5G system") in the terahertz frequency band (e.g., the 95 GHz to 3 THz band) to achieve transmission rates fifty times faster than 5G mobile communication technology and ultra-low latency one-tenth that of 5G mobile communication technology.

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

[0004] Currently, in view of the services to be supported by 5G mobile communication technology, discussions are underway on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as vehicle-to-everything (V2X) for assisting autonomous vehicles in making driving decisions based on information about the position and status of vehicles transmitted by vehicles and for enhancing user convenience, new radio unlicensed (NR-U) for system operation intended to comply with various regulatory requirements in unlicensed bands, NR UE power saving, non-terrestrial network (NTN) (which is UE-satellite direct communication for securing coverage in areas where communication with terrestrial networks is unavailable), and positioning.

[0005] Furthermore, in the area of ​​radio interface architecture / protocols, standardization is already underway on technologies such as the Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (2-step RACH for NR) for simplifying the random access procedure. There is also ongoing standardization on the 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software-defined networking (SDN) technologies, as well as system architecture / services for mobile edge computing (MEC) for receiving services based on UE location.

[0006] If such 5G mobile communication systems are commercialized, the already exponentially growing number of connected devices will be connected to the communication network, and accordingly, it is expected that enhanced functionality and performance of the 5G mobile communication systems and the integrated operation of connected devices will be necessary. To this end, new research is being planned related to extended reality (XR) for effectively supporting augmented reality (AR), virtual reality (VR), etc., 5G performance improvements and complexity reduction through the use of artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communications.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a foundation for developing not only new waveforms for ensuring coverage in the terahertz band for 6G mobile communication technology, full-dimensional MIMO (FD-MIMO), multi-antenna transmission technologies such as array antennas and massive antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS), but also full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization by leveraging satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at a complexity level that exceeds the limits of UE operating capabilities by utilizing ultra-high-performance communication and computing resources.

[0008] Meanwhile, with the development of communication systems, research on uplink transmission and reception processes using multiple panels is being conducted, and demand for achieving simultaneous uplink transmission using multiple panels is growing. Summary of the Invention

[0009] Technical issues

[0010] Various embodiments of the present disclosure are intended to provide an apparatus and method capable of efficiently providing services in a mobile communication system. Various embodiments of the present disclosure may provide a specific method for configuring a phase tracking reference signal for simultaneously transmitting multiple uplink channels using multiple panels in a wireless communication system, and transmitting the phase tracking reference signal together with the uplink channels.

[0011] Technical Solution

[0012] In order to solve the above problems, the present disclosure provides a method performed by a terminal in a communication system, the method comprising: receiving high-layer signaling from a base station, wherein the high-layer signaling includes information for configuring a simultaneous uplink transmission scheme for two transmission and reception points (TRPs) as a scheme of a single frequency network (SFN) and information for configuring uplink phase tracking reference signal (PTRS) transmission; receiving downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH) and a second PUSCH from the base station; mapping the first PUSCH to a first uplink PTRS and mapping the second PUSCH to a second uplink PTRS based on a first transmit precoding matrix indicator (TPMI) or a second sounding reference signal resource indicator (SRI) included in the DCI; and transmitting the first PUSCH, the first uplink PTRS, the second PUSCH, and the second uplink PTRS, wherein the same rate matching is applied to uplink data transmitted via the first PUSCH and the second PUSCH, and the first uplink PTRS and the second uplink PTRS are mapped to the same time-frequency resources.

[0013] In addition, a method performed by a base station in a communication system includes: sending high-layer signaling to a terminal, wherein the high-layer signaling includes information for configuring a simultaneous uplink transmission scheme of two transmission and reception points (TRPs) as a single frequency network (SFN) scheme and information for configuring uplink phase tracking reference signal (PTRS) transmission; sending downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH) and a second PUSCH to the terminal; receiving a first PUSCH, a first uplink PTRS, a second PUSCH, and a second uplink PTRS, wherein, based on a first transmit precoding matrix indicator (TPMI) or a second sounding reference signal resource indicator (SRI) included in the DCI, the first PUSCH is mapped to the first uplink PTRS and the second PUSCH is mapped to the second uplink PTRS, and the same rate matching is applied to uplink data sent via the first PUSCH and the second PUSCH, and the first uplink PTRS and the second uplink PTRS are mapped to the same time-frequency resources.

[0014] In addition, a terminal in a communication system includes a transceiver and a controller, wherein the controller is configured to: receive high-layer signaling from a base station, wherein the high-layer signaling includes information for configuring a simultaneous uplink transmission scheme of two transmit and receive points (TRPs) as a single frequency network (SFN) scheme and information for configuring uplink phase tracking reference signal (PTRS) transmission; receive downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH) and a second PUSCH from the base station; map the first PUSCH to a first uplink PTRS, map the second PUSCH to a second uplink PTRS based on a first transmit precoding matrix indicator (TPMI) or a second sounding reference signal resource indicator (SRI) included in the DCI, and send the first PUSCH, the first uplink PTRS, the second PUSCH, and the second uplink PTRS, wherein the same rate matching is applied to the uplink data sent via the first PUSCH and the second PUSCH, and the first uplink PTRS and the second uplink PTRS are mapped to the same time-frequency resources.

[0015] In addition, a base station in a communication system includes a transceiver and a controller, wherein the controller is configured to: send high-layer signaling to a terminal, wherein the high-layer signaling includes information for configuring a simultaneous uplink transmission scheme of two transmission and reception points (TRPs) as a single frequency network (SFN) scheme and information for configuring uplink phase tracking reference signal (PTRS) transmission, send downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH) and a second PUSCH to the terminal, and receive a first PUSCH, a first uplink PTRS, a second PUSCH, and a second uplink PTRS, wherein the first PUSCH is mapped to the first uplink PTRS and the second PUSCH is mapped to the second uplink PTRS based on a first transmit precoding matrix indicator (TPMI) or a second sounding reference signal resource indicator (SRI) included in the DCI, and the same rate matching is applied to uplink data sent via the first PUSCH and the second PUSCH, and the first uplink PTRS and the second uplink PTRS are mapped to the same time-frequency resources.

[0016] Beneficial effects

[0017] Various embodiments of the present disclosure can provide a device and method capable of efficiently providing services in a mobile communication system. According to various embodiments of the present disclosure, a method for configuring multiple uplink channels together with a phase tracking reference signal and performing simultaneous transmission through multiple panels in a wireless communication system, and a device for performing the method can be provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 The basic structure of the time-frequency domain in the 5G system is shown, where the time-frequency domain is a radio resource domain used to send data or control channels.

[0019] Figure 2 Shows the structure of frames, subframes, and time slots in the 5G system.

[0020] Figure 3 An example of bandwidth portion configuration in a 5G system is shown.

[0021] Figure 4 An example of base station beam allocation configured according to TCI status is shown.

[0022] Figure 5 An example of time domain resource allocation for a PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0023] Figure 6 An example of antenna port configuration and resource allocation for PDSCH transmission using cooperative communication in a communication system is shown.

[0024] Figure 7 An example of downlink control information (DCI) configuration for NC-JT in a wireless communication system is shown, where each TRP sends a different PDSCH or a different PDSCH layer to the UE.

[0025] Figure 8 An example of PDSCH TCI state activation / deactivation of MAC-CE is shown.

[0026] Figure 9 The enhanced PDSCH TCI state activation / deactivation MAC-CE structure is shown.

[0027] Figure 10 FIG. 4 shows beam application time that can be considered when a unified TCI scheme is used in a wireless communication system.

[0028] Figure 11 An example of a MAC-CE structure for activation and indication of a joint TCI state or a separate DL or UL TCI state in a wireless communication system is shown.

[0029] Figure 12 Another example of a MAC-CE structure for activation and indication of multiple joint TCI states or separate DL or UL TCI states in a wireless communication system is shown.

[0030] Figure 13Another example of a MAC-CE structure for activation and indication of multiple joint TCI states or separate DL or UL TCI states in a wireless communication system is shown.

[0031] Figure 14 An example is shown of a case where two SRS resource sets in a wireless communication system according to an embodiment of the present disclosure each include two SRS resources and a UE can support simultaneous uplink transmission using two panels.

[0032] Figure 15 An example is shown of a case where two SRS resource sets in a wireless communication system according to an embodiment of the present disclosure each include two SRS resources and a UE can support simultaneous uplink transmission using two panels.

[0033] Figure 16 An example of an uplink channel repetitive transmission method based on mTRP TDM and an SDM and Single Frequency Network (SFN) scheme as a multi-panel based uplink channel simultaneous transmission method is shown.

[0034] Figure 17 An example of the number of actual PTRS ports for PUSCH transmitted through each panel during codebook-based SFN PUSCH multi-panel transmission is shown.

[0035] Figure 18 An example of the number of actual PTRS ports for PUSCH transmitted through each panel during non-codebook based SFN PUSCH multi-panel transmission is shown.

[0036] Figure 19 An example is shown of a case where each PTRS port is transmitted through each panel during simultaneous SFN PUSCH multi-panel transmission.

[0037] Figure 20 An example of transmitting PUSCH according to the maximum number of actual PTRS ports during simultaneous SFN PUSCH multi-panel transmission is shown.

[0038] Figure 21 is a flowchart illustrating an example of operations of a base station and a UE to configure and transmit a PTRS depending on signaling between the base station and the UE and whether SFN PUSCH multi-panel simultaneous transmission is scheduled.

[0039] Figure 22A is a flowchart illustrating an example of operation of a UE receiving and transmitting a configured PTRS according to at least one embodiment of the present disclosure.

[0040] Figure 22B is a flowchart illustrating an example of operations of a base station configuring and receiving a PTRS according to at least one embodiment of the present disclosure.

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

[0042] Figure 24 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

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

[0044] When describing the embodiments, descriptions related to technical contents known in the relevant field and not directly related to the present disclosure will be omitted. Such omission of unnecessary descriptions is intended to prevent the main concept of the present disclosure from being obscured and to convey the main concept more clearly.

[0045] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted or schematically shown. In addition, the size of each element does not fully reflect the actual size. In the various drawings, the same or corresponding elements are assigned the same reference numerals.

[0046] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the ways of achieving them will be apparent. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose the present disclosure and inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar figure marks represent the same or similar elements. In addition, when describing the present disclosure, when it is determined that a detailed description of a known function or configuration incorporated herein may make the subject matter of the present disclosure unnecessarily unclear, the description will be omitted. The terms to be described below are terms defined in consideration of the functions in the present disclosure and may vary according to the user, the user's intention or custom. Therefore, the definition of the terms should be based on the content in the entire specification.

[0047] Here, it should be understood that each block of the flowchart diagram and the combination of blocks in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a component for implementing the function specified in one or more flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can instruct the computer or other programmable data processing device to act in a specific manner, so that the instructions stored in the computer-usable or computer-readable memory produce an article of manufacture including an instruction component that implements the function specified in one or more flowchart blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing device to cause a series of operating steps to be performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the function specified in one or more flowchart blocks.

[0048] Furthermore, each block in the flowchart illustration may represent a module, segment, or portion of code that includes one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order, depending on the functions involved.

[0049] As used in the embodiments of the present disclosure, the term "unit" refers to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and a "unit" can perform certain functions. However, "unit" does not always have a meaning limited to software or hardware. A "unit" can be configured to be stored in an addressable storage medium or to execute one or more processors. Therefore, a "unit" includes, for example, a software element, an object-oriented software element, a class element or a task element, a process, a function, a property, a procedure, a subroutine, a program code segment, a driver, firmware, microcode, a circuit, data, a database, a data structure, a table, an array, and a parameter. The elements and functions provided by a "unit" can be combined into a smaller number of elements or "units" or divided into a larger number of elements or "units". In addition, elements and "units" can be implemented as one or more CPUs within a reproduction device or a secure multimedia card. In addition, a "unit" in the embodiments may include one or more processors.

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

[0051] As a typical example of a broadband wireless communication system, the LTE system adopts an orthogonal frequency division multiplexing (OFDM) scheme in the downlink (DL) and a single-carrier frequency division multiple access (SC-FDMA) scheme in the uplink (UL). The uplink refers to the radio link via which a user equipment (UE) or mobile station (MS) transmits data or control signals to a base station (BS, eNodeB, or gNodeB), and the downlink refers to the radio link via which a base station transmits data or control signals to a UE. This multiple access scheme can separate the data or control information of each user by allocating and operating the time-frequency resources used to transmit each user's data or control information, thereby avoiding overlap, that is, establishing orthogonality.

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

[0053] eMBB is designed to provide higher data rates than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink for a single base station. Furthermore, 5G communication systems must provide increased user-perceived data rates and maximum data rates to UEs. To meet these requirements, improved transmission / reception technologies, including further enhanced multiple-input multiple-output (MIMO) transmission technology, are needed. Furthermore, the data rates required by 5G communication systems can be achieved using frequency bandwidths greater than 20 MHz in frequency bands between 3 and 6 GHz, or 6 GHz or higher, rather than using transmission bandwidths of up to 20 MHz to transmit signals in the 2 GHz frequency band used in LTE.

[0054] Furthermore, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. mMTC has requirements such as supporting connections for a large number of UEs in a cell, enhancing UE coverage, improving battery life, and reducing UE costs in order to effectively provide the IoT. Because the IoT provides communication capabilities to various sensors and devices, it must support a large number of UEs in a cell (e.g., 1,000,000 UEs / km²). Furthermore, since mMTC-enabled UEs may be located in shadowed areas, such as building basements, that are not covered by the cell due to the nature of the service, UEs may require wider coverage than other services provided by 5G communication systems. mMTC-enabled UEs must be configured to be inexpensive and may require very long battery life, such as 10 to 15 years, due to the difficulty of frequently replacing UE batteries.

[0055] Finally, URLLC is a cellular-based mission-critical wireless communication service. For example, URLLC can be used for services such as remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, and emergency alerts. Therefore, URLLC should provide communications with very low latency and very high reliability. For example, services supporting URLLC must meet an air interface latency of less than 0.5ms and may also require 10 -5 Therefore, for services supporting URLLC, the 5G system must provide a shorter transmission time interval (TTI) than other services, and may also require a design for allocating a large amount of resources in the frequency band to ensure the reliability of the communication link.

[0056] The three services in 5G, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted in a single system. In this case, different transmission / reception technologies and transmission / reception parameters can be used between the services to meet the different requirements of each service. Of course, the 5G system is not limited to the three services described above.

[0057] In the following description, a base station is an entity that allocates resources to a terminal and may be at least one of a gNode B, eNode B, Node B, base station (BS), wireless access unit, base station controller, and a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Furthermore, in the following description, LTE or LTE-A systems may be described by way of example, but embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include fifth-generation mobile communication technologies (5G, New Radio, and NR), which are being developed beyond LTE-A. In the following description, "5G" may be a concept covering existing LTE, LTE-A, and other similar services. Furthermore, based on the determination of those skilled in the art, the present disclosure may also be applied to other communication systems with some modifications without significantly departing from the scope of this disclosure.

[0058] In the following description, the term “a / b” may be understood as at least one of a and b.

[0059] Hereinafter, the frame structure of the 5G system will be described in more detail with reference to the accompanying drawings.

[0060] Figure 1 The basic structure of the time-frequency domain in the 5G system is shown, where the time-frequency domain is a radio resource domain used to send data or control channels.

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

[0062] Figure 2 Shows the structure of frames, subframes, and time slots in the 5G system.

[0063] exist Figure 2 An example of the structure of a frame 200, a subframe 201, and a time slot 202 is shown in FIG. One frame 200 may be defined as 10 ms. One subframe 201 may be defined as 1 ms, so one frame 200 may include a total of ten subframes 201. One time slot 202 or 203 may be defined as 14 OFDM symbols (i.e., the number of symbols per time slot). =14). One subframe 201 may include one or more time slots 202 and 203, and the number of time slots 202 and 203 of each subframe 201 may vary depending on the configured value μ of the subcarrier spacing 204 or 205. Figure 2 The example shows a case of μ = 0 (204) and a case of μ = 1 (205) as configuration values ​​for subcarrier spacing. In the case of μ = 0 (204), one subframe 201 may include one time slot 202, and in the case of μ = 1 (205), one subframe 201 may include two time slots 203. That is, the number of time slots per subframe is The number of slots per frame may vary depending on the subcarrier spacing configuration value μ and Can be different accordingly. and It can be defined according to each subcarrier spacing configuration μ as shown in Table 1 below.

[0064] [Table 1]

[0065]

[0066] Next, a bandwidth part (BWP) configuration in a 5G communication system will be described in detail with reference to the accompanying drawings.

[0067] Figure 3 An example of bandwidth portion configuration in a 5G communication system is shown;

[0068] Figure 3 An example is shown in which a UE bandwidth 300 is configured to include two bandwidth parts, namely, bandwidth part #1 (BWP#1) 301 and bandwidth part #2 (BWP#2) 302. The base station can configure one or more bandwidth parts for the UE and can configure the following pieces of information about each bandwidth part, as given below.

[0069] [Table 2]

[0070]

[0071] Obviously, the above examples are not limiting, and in addition to the above configuration information, various parameters related to bandwidth parts may be configured for the UE. The base station may transmit the configuration information to the UE via higher-layer signaling (e.g., radio resource control (RRC) signaling). One configured bandwidth part or at least one of multiple configured bandwidth parts may be activated. Whether a configured bandwidth part is activated may be semi-statically transmitted from the base station to the UE via RRC signaling, or dynamically transmitted from the base station to the UE via downlink control information (DCI). According to some embodiments, before establishing a radio resource control (RRC) connection, the base station may configure an initial bandwidth part (BWP) for the UE for initial access via a master information block (MIB). More specifically, the UE may receive configuration information regarding a control resource set (CORESET) and search space via the MIB during initial access. This configuration information may be used to transmit a PDCCH for receiving system information (which may correspond to residual system information (RMSI) required for initial access or system information block 1 (SIB1)). Each of the CORESET and search space configured via the MIB may be considered as identity (ID) 0. The base station can notify the UE of configuration information about control resource set #0, such as frequency allocation information, time allocation information, and parameter sets, through the MIB. In addition, the base station can notify the UE of configuration information about the monitoring period and timing of control resource set #0, that is, configuration information about search space #0, through the MIB. The UE can consider the frequency domain configured by control resource set #0 obtained from the MIB to be the initial bandwidth part used for initial access. The ID of the initial bandwidth part can be considered to be 0. The UE can receive the physical downlink shared channel (PDSCH) through which the SIB is transmitted through the configured initial bandwidth part. The initial bandwidth part can be used not only for the purpose of receiving SIBs, but also for other system information (OSI), paging, random access, etc.

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

[0073] According to some embodiments, if the bandwidth supported by the UE is less than the system bandwidth, this can be supported by bandwidth fraction configuration. For example, the base station can configure the frequency location of the bandwidth fraction for the UE, so that the UE can transmit / receive data at a specific frequency location within the system bandwidth.

[0074] In addition, according to some embodiments, a base station can configure multiple bandwidth parts for a UE to support different parameter sets. For example, to support data transmission / reception for a UE using both a 15 kHz subcarrier spacing and a 30 kHz subcarrier spacing, two bandwidth parts can be configured with subcarrier spacings of 15 kHz and 30 kHz, respectively. The different bandwidth parts can be frequency-division multiplexed (FDM), and if data is to be transmitted / received with a specific subcarrier spacing, the bandwidth part configured with the corresponding subcarrier spacing can be activated.

[0075] In addition, according to some embodiments, a base station may configure bandwidth portions of different sizes for a UE to reduce the power consumed by the UE. For example, if a UE supports a relatively large bandwidth (e.g., 100 MHz) and always transmits / receives data using this bandwidth, considerable power consumption may occur. Specifically, from a power consumption perspective, unnecessarily monitoring a downlink control channel with a large bandwidth of 100 MHz when there is no traffic may be substantially inefficient. To reduce the power consumed by the UE, the base station may configure a bandwidth portion of a relatively small bandwidth (e.g., a 20 MHz portion) for the UE. The UE can perform monitoring operations in the 20 MHz bandwidth portion when there is no traffic, and if data is available, it can transmit / receive data using the 100 MHz bandwidth portion as instructed by the base station. The following describes the QCL and Transmission Configuration Indicator (TCI) states.

[0076] In wireless communication systems, one or more different antenna ports (which can also be replaced by one or more channels, signals, or combinations thereof, but for ease of description, will be referred to as different antenna ports below) can be associated with each other via a quasi-co-location (QCL) configuration, as shown in Table 3 below. The TCI state is used to communicate the QCL relationship between the PDCCH (or PDCCH DRMS) and another RS ​​or channel. The description of QCL between a reference antenna port A (reference RS#A) and a target antenna port B (target RS#B) allows the UE to apply some or all of the large-scale channel parameters estimated for antenna port A to the channel measurement from antenna port B. QCL needs to be associated with different parameters depending on the scenario, such as 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) radio resource management (RRM) affected by average gain, or 4) beam management (BM) affected by spatial parameters. Therefore, four types of QCL relationships are supported in NR, as shown in Table 3 below.

[0077] [Table 3]

[0078]

[0079] Spatial RX parameters may refer to some or all of various parameters as a whole, such as angle of arrival (AoA), power angle spectrum (PAS) of AoA, angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, and spatial channel correlation. The QCL relationship can be configured for the UE through the RRC parameters TCI-state and QCL-info as shown in Table 4 below. Referring to Table 4, the base station can configure one or more TCI states for the UE, thereby notifying up to two QCL relationships (qcl-Type1, qcl-Type2) of the RS (i.e., target RS) with respect to the ID of the reference TCI state. Each piece of QCL information (QCL-Info) included in each TCI state includes the serving cell index and BWP index of the reference RS indicated by the corresponding QCL information, the type and ID of the reference RS, and the QCL type as shown in Table 3 above.

[0080] [Table 4]

[0081]

[0082]

[0083] Figure 4 An example of base station beam allocation according to TCI state configuration is shown. Figure 4 , the base station can transmit information about N different beams to the UE through N different TCI states. Figure 4 In the case of N=3, the base station can configure the qcl-Type2 parameters included in the three TCI states 400, 405 and 410 in QCL typeD while being associated with CSI-RS or SSB corresponding to different beams, thereby notifying the antenna ports pointing to different TCI states 400, 405 and 410 to be associated with different spatial Rx parameters (i.e., different beams).

[0084] Tables 5 to 9 below list valid TCI state configurations based on the target antenna port type.

[0085] Table 5 lists valid TCI state configurations when the target antenna port is a CSI-RS (i.e., TRS) for tracking. TRS indicates non-zero power (NZP) CSI-RS for which no repetition parameters are configured and whose trs-Info is configured as "true." In Table 5, configuration number 3 can be used for periodic TRS.

[0086] [Table 5]

[0087]

[0088] Table 6 lists valid TCI state configurations when the target antenna port is a CSI-RS for CSI. The CSI-RS for CSI indicates an NZP CSI-RS for which no parameter indicating repetition (eg, a repetition parameter) is configured and trs-Info is not configured as "true" among CSI-RSs.

[0089] [Table 6]

[0090]

[0091] Table 7 lists the valid TCI state configurations when the target antenna port is the CSI-RS for beam management (BM) (which has the same meaning as the CSI-RS for L1 RSRP reporting). The CSI-RS for BM indicates the NZP CSI-RS with a repetition parameter configured with a value of "on" or "off" among the CSI-RSs and whose trs-Info is not configured as "true".

[0092] [Table 7]

[0093]

[0094] Table 8 lists the valid TCI state configurations when the target antenna port is PDCCH DMRS.

[0095] [Table 8]

[0096]

[0097] Table 9 lists the valid TCI state configurations when the target antenna port is PDSCH DMRS.

[0098] [Table 9]

[0099]

[0100] According to the representative QCL configuration method based on Tables 5 to 9 above, the target antenna port and the reference antenna port for each step are configured and operated as "SSB" - "TRS" - "CSI-RS for CSI, or CSI-RS for BM, or PDCCH DMRS, or PDSCH DMRS." Therefore, it is possible to assist the reception operation of the UE by associating statistical characteristics that can be measured from the SSB and TRS with each antenna port.

[0101] Next, downlink control information (DCI) in the 5G system will be described in detail.

[0102] 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 DCI and transmitted from the base station to the UE via DCI. Regarding PUSCH or PDSCH, the UE can monitor fallback DCI formats and non-fallback DCI formats. The fallback DCI format may include fixed fields predefined between the base station and the UE, while the non-fallback DCI format may include configurable fields.

[0103] The DCI may undergo a channel coding and modulation process and then be sent through a physical downlink control channel (PDCCH) after the channel coding and modulation process. A cyclic redundancy check (CRC) may be attached to the DCI message payload, and the CRC may be scrambled by a radio network temporary identifier (RNTI) corresponding to the identity of the UE. Different RNTIs may be used depending on the purpose of the DCI message, for example, UE-specific data transmission, power control commands, or random access responses. That is, the RNTI may not be sent explicitly, but may be sent while being included in the CRC calculation process. Upon receiving a DCI message sent through the PDCCH, the UE may identify the CRC by using the allocated RNTI, and if the CRC identification result is correct, the UE may know that the corresponding message has been sent to the UE.

[0104] For example, the DCI used to schedule the PDSCH regarding system information (SI) may be scrambled by the SI-RNTI. The DCI used to schedule the PDSCH regarding the random access response (RAR) message may be scrambled by the RA-RNTI. The DCI used to schedule the PDSCH regarding the paging message may be scrambled by the P-RNTI. The DCI used to notify the slot format indicator (SFI) may be scrambled by the SFI-RNTI. The DCI used to notify the transmit power control (TPC) may be scrambled by the TPC-RNTI. The DCI used to schedule the UE-specific PDSCH or PUSCH may be scrambled by the cell RNTI (C-RNTI).

[0105] DCI format 0_0 may be used as a fallback DCI for scheduling PUSCH, and in this case, the CRC may be scrambled by the C-RNTI. For example, DCI format 0_0 in which the CRC is scrambled by the C-RNTI may include the following information given in Table 10 below.

[0106] [Table 10]

[0107]

[0108] DCI format 0_1 ​​may be used as a non-fallback DCI for scheduling PUSCH, and in this case, the CRC may be scrambled by the C-RNTI. For example, DCI format 0_1 ​​in which the CRC is scrambled by the C-RNTI may include the following information given in Table 11 below.

[0109] [Table 11]

[0110]

[0111]

[0112] DCI format 1_0 may be used as a fallback DCI for scheduling PDSCH, and in this case, the CRC may be scrambled by the C-RNTI. For example, DCI format 1_0 in which the CRC is scrambled by the C-RNTI may include the following information given in Table 12 below.

[0113] [Table 12]

[0114]

[0115] DCI format 1_1 may be used as a non-fallback DCI for scheduling PDSCH, and in this case, the CRC may be scrambled by the C-RNTI. For example, DCI format 1_1 in which the CRC is scrambled by the C-RNTI may include the following information given in Table 13 below.

[0116] [Table 13]

[0117]

[0118]

[0119] Hereinafter, a time domain resource allocation method for a data channel in a 5G system will be described.

[0120] A base station can configure a table for the UE using higher-layer signaling (e.g., RRC signaling) regarding time-domain resource allocation information for the Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH). A table containing up to 16 entries (maxNrofDL-Allocations) can be configured for the PDSCH, and a table containing up to 16 entries (maxNrofUL-Allocations) can be configured for the PUSCH. In embodiments, the time-domain resource allocation information may include PDCCH-to-PDSCH slot timing (e.g., the time slot interval corresponding to the time point between the time point when a PDCCH is received and the time point when a PDSCH scheduled by the received PDCCH is transmitted; denoted as K0), PDCCH-to-PUSCH slot timing (e.g., the time slot interval corresponding to the time point between the time point when a PDCCH is received and the time point when a PUSCH scheduled by the received PDCCH is transmitted; denoted as K2 below), information regarding the position and length of the starting symbol for scheduling a PDSCH or PUSCH within a slot, and the mapping type of the PDSCH or PUSCH. For example, information such as that in Table 14 or Table 15 below may be sent from the base station to the UE.

[0121] [Table 14]

[0122]

[0123] [Table 15]

[0124]

[0125] The base station may notify the UF of one of the entries in the table of the above-mentioned time domain resource allocation information through L1 signaling (e.g., DCI) (e.g., the "time domain resource allocation" field in the DCI may indicate the same). The UE may obtain the time domain resource allocation information about the PDSCH or PUSCH based on the DCI obtained from the base station.

[0126] Figure 5 An example of time domain resource allocation for a PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0127] refer to Figure 5 , the base station can configure the subcarrier spacing (μ PDSCH , μ PDCCH ), scheduling offset (K0) value and the OFDM symbol starting position 500 and length 505 within a time slot dynamically indicated by DCI to indicate the time domain position of the PDSCH resource.

[0128] Next, the PUSCH transmission scheduling scheme will be described. PUSCH transmission can be dynamically scheduled by UL grants in DCI, or by configured grant type 1 or type 2. Dynamic scheduling instructions for PUSCH transmission can be performed in the following ways:

[0129] Configured grant type 1 PUSCH transmissions may be semi-statically configured by receiving configuredGrantConfig including the rrc-ConfiguredUplinkGrant in Table 16 via higher layer signaling, without receiving a UL grant within the DCI. Configured grant type 2 PUSCH transmissions may be semi-persistently scheduled via a UL grant within the DCI after receiving configuredGrantConfig not including the rrc-ConfiguredUplinkGrant in Table 16 via higher layer signaling. If PUSCH transmission is operated via a configured grant, the parameters applied to PUSCH transmissions via configuredGrantConfig (higher layer signaling) in Table 16 are applied, in addition to the scaling of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and UCI-OnPUSCH provided by pusch-Config (higher layer signaling) in Table 17. If TransformMPrecoder is provided in configuredGrantConfig (higher layer signaling) in Table 16, the UE applies tp-pi2BPSK in pusch-Config in Table 17 to PUSCH transmissions operated by the configured grant.

[0130] [Table 16]

[0131]

[0132]

[0133]

[0134]

[0135] 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. Depending on whether the value of txConfig within pusch-Config as high-layer signaling in Table 17 is "codebook" or "nonCodebook", PUSCH transmission can follow the codebook-based transmission method and the non-codebook-based transmission method. As described above, PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1, and can be semi-statically configured through the configured grant. Upon receiving an indication of scheduling regarding PUSCH transmission through DCI format 0_0, the UE performs beam configuration for PUSCH transmission by using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the minimum ID within the activated uplink BWP within the serving cell, and PUSCH transmission is based on a single antenna port. The UE does not expect scheduling for PUSCH transmission via DCI format 0_0 within a BWP without a configured PUCCH resource including pucch-spatialRelationInfo. If the UE does not have a configured txConfig within pusch-Config in Table 17, the UE does not expect scheduling via DCI format 0_1.

[0136] [Table 17]

[0137]

[0138]

[0139]

[0140] Next, we will describe codebook-based PUSCH transmission. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and semi-statically configured via a configured grant. If codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via a configured grant, the UE determines the precoder used for PUSCH transmission based on the SRS Resource Indicator (SRI), the Transmit Precoding Matrix Indicator (TPMI), and the transmit rank (number of PUSCH transmission layers). The SRI can be provided via the SRS Resource Indicator (a field within the DCI) or configured via the srs-ResourceIndicator (higher layer signaling). During codebook-based PUSCH transmission, the UE has at least one SRS resource configured for it and can have up to two SRS resources configured for it. If the UE is provided with an SRI via DCI, the SRS resource indicated by the corresponding SRI indicates the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the corresponding SRI. In addition, TPMI and transmission rank can be given through "precoding information and number of layers" (fields within the DCI) or configured through precodingAndNumberOfLayers (higher layer signaling). TPMI is used to indicate the precoder to be applied to PUSCH transmission. If one SRS resource is configured for a UE, TPMI can be used to indicate the precoder to be applied to the configured SRS resource. If multiple SRS resources are configured for a UE, TPMI is used to indicate the precoder to be applied to the SRS resource indicated by SRI.

[0141] The precoder to be used for PUSCH transmission is selected from an uplink codebook with the same number of antenna ports as the value of nrofSRS-Ports in SRS-Config (higher layer signaling). In conjunction with codebook-based PUSCH transmission, the UE determines the codebook subset based on codebookSubset and TPMI in pusch-Config (higher layer signaling). Based on the UE capabilities reported by the UE to the base station, the codebook subset in pusch-Config (higher layer signaling) can be configured as "fullyAndPartialAndNonCoherent," "partialAndNonCoherent," or "noncoherent." If the UE reports "partialAndNonCoherent" as a UE capability, the UE does not expect the codebookSubset (higher layer signaling) value to be configured as "fullyAndPartialAndNonCoherent." Additionally, if the UE reports "nonCoherent" as a UE capability, the UE does not expect the codebookSubset (higher layer signaling) value to be configured as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent." If nrofSRS-Ports within the SRS-ResourceSet (higher layer signaling) indicates two SRS antenna ports, the UE does not expect that the value of codebookSubset (higher layer signaling) will be configured as "partialAndNonCoherent".

[0142] A UE may have one SRS resource set configured for it, where the value of usage in SRS-ResourceSet (higher layer signaling) is "codebook", and one SRS resource may be indicated by the SRI in the corresponding SRS resource set. If multiple SRS resources are configured in an SRS resource set, where the value of usage in SRS-ResourceSet (higher layer signaling) is "codebook", the UE expects the value of nrofSRS-Ports in SRS-Resource (higher layer signaling) to be the same for all SRS resources.

[0143] The UE transmits one or more SRS resources included in an SRS resource set configured with the usage value of "codebook" to the base station based on high-layer signaling. The base station selects one of the SRS resources transmitted by the UE and instructs the UE to transmit the PUSCH by using the transmit beam information of the corresponding SRS resource. In conjunction with codebook-based PUSCH transmission, the SRI is used as index information for selecting an SRS resource and is included in the DCI. In addition, the base station adds information indicating the rank and TPMI to be used by the UE for PUSCH transmission to the DCI. By using the SRS resource indicated by the SRI, the UE applies the precoder indicated by the rank and the TPMI indicated based on the transmit beam of the corresponding SRS resource when performing PUSCH transmission, thereby performing PUSCH transmission.

[0144] Next, we will describe non-codebook-based PUSCH transmissions. Non-codebook-based PUSCH transmissions can be dynamically scheduled using DCI formats 0_0 or 0_1 and can be semi-statically operated using a configured grant. If at least one SRS resource is configured within an SRS resource set, where the usage value within the SRS-ResourceSet (higher layer signaling) is "nonCodebook," non-codebook-based PUSCH transmissions can be scheduled for the UE using DCI format 0_1.

[0145] Regarding SRS resource sets, where the usage value within the SRS-ResourceSet (higher layer signaling) is "nonCodebook", 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 resources connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission in the UE is less than 42 symbols, the UE does not expect the information about the precoder used for SRS transmission to be updated.

[0146] If the configured value of resourceType within the SRS-ResourceSet (higher layer signaling) is "aperiodic," the attached NZP CSI-RS is indicated by the SRS request, which is a field within DCI format 0_1 ​​or 1_1. If the attached NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the attached NZP CSI-RS is indicated when the value of the SRS request (a field within DCI format 0_1 ​​or 1_1) is not "00." The corresponding DCI should not indicate cross-carrier or cross-BWP scheduling. In addition, if the value of the SRS request indicates the presence of NZP CSI-RS, the NZP CSI-RS is positioned 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.

[0147] If a periodic or semi-persistent SRS resource set is configured, the connected NZP CSI-RS can be indicated by the associatedCSI-RS in the SRS-ResourceSet (higher layer signaling). For non-codebook based transmission, the UE does not expect that the spatialRelationInfo as the higher layer signaling about the SRS resource and the associatedCSI-RS in the SRS-ResourceSet (higher layer signaling) will be configured together.

[0148] If multiple SRS resources are configured for a UE, the UE can determine the precoder and transmission rank to be applied to the PUSCH transmission based on the SRI indicated by the base station. The SRI can be indicated by the SRS resource indicator (a field within the DCI) or configured by the srs-ResourceIndicator (higher layer signaling). Similar to the above-mentioned codebook-based PUSCH transmission, if the SRI is provided to the UE via the DCI, the SRS resource indication indicated by the corresponding SRI includes the SRS resources corresponding to the SRI among the SRS resources transmitted before the PDCCH corresponding to 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 and the maximum number of SRS resources are determined by the UE capabilities reported by the UE to the base station. The SRS resources transmitted simultaneously by the UE occupy the same RB. The UE is configured with one SRS port for each SRS resource. There can be only one configured SRS resource set, where the usage value in the SRS-ResourceSet (higher layer signaling) is "nonCodebook", and a maximum of four SRS resources can be configured for non-codebook based PUSCH transmission.

[0149] The base station sends one NZP-CSI-RS connected to the SRS resource set to the UE, and the UE calculates the precoder to be used when sending one or more SRS resources within the corresponding SRS resource set based on the result of the measurement when the corresponding NZP-CSI-RS is received. When sending one or more SRS resources within the SRS resource set to the base station, the UE applies the calculated precoder, wherein the configured usage is "nonCodebook", and the base station selects one or more SRS resources from the received one or more SRS resources. In conjunction with non-codebook based PUSCH transmission, the SRI indication can represent an index of one SRS resource or a combination of multiple SRS resources, and the SRI is included in the DCI. The number of SRS resources indicated by the SRI sent by the base station can be the number of transmission layers of the PUSCH, and the UE transmits the PUSCH by applying the precoder applied to the SRS resource transmission to each layer.

[0150] Below, a method for determining the transmit power of an uplink data channel in a 5G system is described in detail.

[0151] In the 5G system, the transmission power of the uplink data channel can be determined using the following mathematical expression 1.

[0152] [Mathematical formula 1]

[0153]

[0154] In Mathematical Expression 1, j represents a grant type of PUSCH, specifically, j=0 represents a PUSCH grant for a random access response, j=1 represents a configured grant, and j∈{2,3,...,J-1} represents a dynamic grant. represents the maximum output power configured in the UE for PUSCH transmission opportunity i relative to carrier f supporting cell c. is and The sum of the configured parameters, is configured via high-level parameters, and It can be determined by higher layer configuration and SRI (in the case of dynamic PUSCH grant). denotes the bandwidth for resource allocation represented by the number of RBs used for PUSCH transmission opportunity i, and Indicates a value determined based on the modulation and coding scheme (MCS) and the type of information transmitted through the PUSCH (for example, whether UL-SCH or CSI is included).

[0155] is a value used to compensate for path loss and indicates a value that may be determined via higher layer configuration and SRI (in the case of dynamically granted PUSCH). represents the downlink path loss estimate, which is obtained by the UE through the reference signal index q d The reference signal is estimated, and the reference signal index q d It can be determined by the UE via higher layer configuration and SRI (in the case of dynamic grant PUSCH or grant PUSCH based on ConfigureGrantConfig configuration (grant PUSCH of type 2 configuration), which does not include the higher layer configuration rrc-ConfiguredUplinkGrant) or via higher layer configuration.

[0156] is the closed-loop power adjustment value and can be supported by both the accumulation method and the absolute method. When the higher-layer parameter tpc-Accumulation is not configured in the UE, the closed-loop power adjustment value can be determined using the accumulation method. Here, Depend on is determined by dividing K for transmission of PUSCH transmission opportunity i-i0 by the closed-loop power adjustment value for the previous PUSCH transmission opportunity i-i0. PUSCH (i-i0)-1 symbol and K for transmission of PUSCH transmission opportunity i PUSCH (i) The TPC command values ​​of the closed-loop index 1 received through DCI are added between symbols. If the high-layer parameter tpc-Accumulation is configured in the UE, then Determined as the TPC command value for closed-loop index 1 received via DCI If the high-level parameter twoPUSCH-PC-AdjustmentStates is configured in the UE, the closed-loop index 1 can be configured with a value of 0 or 1, and the value can be determined by the high-level configuration and SRI (in the case of dynamic grant PUSCH). TPC command field according to the accumulation method and absolute method and TPC value in DCI The mapping relationship between them can be defined as shown in Table 18 below.

[0157] [Table 18]

[0158]

[0159] Next, we will describe an uplink channel estimation method using a UE's Sounding Reference Signal (SRS) transmission. The base station can configure at least one SRS configuration for each uplink BWP to transmit SRS transmission configuration information to the UE. Furthermore, the base station can configure at least one SRS resource set for each SRS configuration. For example, the base station and the UE can exchange higher-layer signaling information as follows to transmit information about the SRS resource set.

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

[0161] -srs-ResourceIdList: A collection of SRS resource indexes referenced by the SRS resource set

[0162] -resourceType: The time domain transmission 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 location of the SRS resource set used. If configured as "aperiodic," aperiodic SRS resource trigger list / slot offset information can be provided, and associated CSI-RS information can be provided based on the location of the SRS resource set used.

[0163] -usage: configuration regarding usage location of SRS resources referenced by an SRS resource set, and can be configured as one of "beamManagement", "codebook", "nonCodebook", and "antennaSwitching".

[0164] -alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter configuration for adjusting the transmit power of the SRS resources referenced by the SRS resource set.

[0165] The UE may 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.

[0166] In addition, the base station and the UE may send / receive higher-layer signaling information to convey separate configuration information about the SRS resources. As an example, the separate configuration information about the SRS resources may include time-frequency domain mapping information within the time slot of the SRS resources, and this may include information about frequency hopping within or between time slots of the SRS resources. The separate configuration information about the 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 SRS resource set 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 also include the SRS resource transmission period and time slot offset (e.g., periodicityAndOffset).

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

[0168] For example, a base station may activate or deactivate semi-persistent SRS transmission for a UE through higher-layer signaling. The base station may indicate activation of an SRS resource set through MAC CE signaling, and the UE may transmit SRS resources referenced by the activated SRS resource set. The SRS resource set activated through MAC CE signaling may be limited to SRS resource sets with a resourceType configured as "semi-persistent." The intra-slot time-frequency domain resource mapping of the transmitted SRS resource complies with the resource mapping information configured for the SRS resource, and the slot mapping (including the transmission period and slot offset) complies with the periodicityAndOffset configured for the SRS resource. In addition, the spatial domain transmit filter applied to the transmitted SRS resource may indicate the spatial relationship information configured for the SRS resource, or may indicate the associated CSI-RS information configured for the SRS resource set including the SRS resource. If the SRS resource has spatial relationship information configured for it, the spatial domain transmit filter may be determined by referring to the configuration information regarding the spatial relationship information transmitted through the MAC CE signaling for activating semi-persistent SRS transmission, without complying with the configuration information. The UE may transmit SRS resources within an uplink BWP activated with respect to semi-persistent SRS resources activated by higher layer signaling.

[0169] For example, a base station can trigger aperiodic SRS transmission by a UE via a DCI. The base station can indicate one of the aperiodic SRS triggers (aperiodicSRS-ResourceTrigger) via the SRS Request field of the DCI. The UE can understand that the SRS resource set configuration information, including the aperiodic SRS resource trigger list indicated by the DCI, has been triggered. The UE can transmit SRS resources referenced by the triggered SRS resource set. The intra-slot time-frequency domain resource mapping of the transmitted SRS resources complies with the resource mapping information configured for the SRS resources. Furthermore, the slot mapping of the transmitted SRS resources can be determined by the slot offset between the SRS resource and the PDCCH containing the DCI, which can indicate a value (or values) included in the slot offset set configured for the SRS resource set. Specifically, the value indicated in the time-domain resource assignment field of the DCI, among the offset values ​​(or values) included in the slot offset set configured for the SRS resource set, can be applied as the slot offset between the SRS resource and the PDCCH containing the DCI. In addition, the spatial domain transmit filter applied to the transmitted SRS resource may indicate spatial relationship information configured for the SRS resource, or may indicate associated CSI-RS information configured for the SRS resource set including the SRS resource. The UE may transmit the SRS resource within the uplink BWP regarding the aperiodic SRS resource activation triggered by the DCI.

[0170] If a base station triggers aperiodic SRS transmission by a UE via DCI, a minimum time interval may be required between the transmitted SRS and the PDCCH containing the DCI triggering the aperiodic SRS transmission, so that the UE can transmit the SRS by applying the configuration information regarding the SRS resources. The time interval for SRS transmission by the UE may be defined as the number of symbols between the last symbol of the PDCCH containing the DCI triggering the aperiodic SRS transmission and the first symbol of the first transmitted SRS resource mapped to the transmitted SRS resource(s). The minimum time interval may be determined with reference to the PUSCH preparation process time required for the UE to prepare for PUSCH transmission. The minimum time interval may have different values ​​depending on the location of the SRS resource set containing the transmitted SRS resource. For example, the minimum time interval may be determined as N2 symbols, defined in consideration of the UE's processing capability, where the UE processing capability is determined by the UE's capability with reference to the UE's PUSCH preparation process time. In addition, if the location of use of the SRS resource set including the transmitted SRS resource is considered, the location of use of the SRS resource set is configured as "codebook" or "antenna switching", then the minimum time interval may be determined as N2 symbols, and if the location of use of the SRS resource set is configured as "noncodebook" or "beam management", then the minimum time interval may be determined as N2+14 symbols. If the time interval for aperiodic SRS transmission is greater than or equal to the minimum time interval, the UE may transmit the aperiodic SRS, and if the time interval for aperiodic SRS transmission is less than the minimum time interval, the DCI triggering the aperiodic SRS may be ignored.

[0171] [Table 19]

[0172]

[0173]

[0174]

[0175] With reference to one reference signal, the configuration information spatialRelationInfo in Table 19 above may be applied to a beam for SRS transmission corresponding to the beam information of the corresponding reference signal. For example, the configuration of spatialRelationInfo may include the following pieces of information as given in Table 20 below.

[0176] [Table 20]

[0177]

[0178] Referring to the spatialRelationInfo configuration, the SS / PBCH block index, CSI-RS index, or SRS index can be configured as the index of the reference signal to be referenced in order 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 will be referenced for the corresponding SRS transmission, ssb-Index indicates the index of the SS / PBCH block, csi-RS-Index indicates the index of the CSI-RS, and srs indicates the index of the SRS. If the higher-layer signaling referenceSignal has a configuration value of "ssb-Index", the UE can apply the receive beam used to receive the SS / PBCH block corresponding to ssb-Index as the transmit beam for the corresponding SRS transmission. If the higher-layer signaling referenceSignal has a configuration value of "csi-RS-Index", the UE can apply the receive beam used to receive the CSI-RS corresponding to csi-RS-Index as the transmit beam for the corresponding SRS transmission. If the higher layer signaling referenceSignal has a configuration value of "srs", the UE can apply the reception beam used to transmit the SRS corresponding to the srs as the transmission beam for the corresponding SRS transmission. Next, the uplink PTRS is described.

[0179] The UE may be configured with the higher-layer parameter phaseTrackingRS for PTRS in the higher-layer parameter DMRS-UplinkConfig. When the UE transmits a PUSCH to the base station, the UE may transmit a phase tracking reference signal (PTRS) for phase tracking of the uplink channel. The process by which the UE transmits UL PTRS may be determined depending on whether transform precoding is performed when transmitting the PUSCH. In the case where the UE performs transform precoding and the transformPrecoderEnabled region is configured in the higher-layer parameter PTRS-UplinkConfig, the sampleDensity in the transformPrecoderEnabled region may indicate the value indicated by N in Table 21 below. RB0 to N RB4 In the case where the UE performs transform precoding and the transformPrecoderEnabled region is configured in the higher layer parameter PTRS-UplinkConfig, the UE may determine the resource N for scheduling according to the following Table 21: RBIn addition, if the transform precoder is applied to PUSCH transmission, the bits in the PTRS-DMRS association field for indicating the association between the PTRS and DMRS of DCI format 0_1 ​​or 0_2 may be 0.

[0180] [Table 21]

[0181]

[0182] In case transform precoding is not applied to PUSCH transmission and the higher-layer parameter phaseTrackingRS is configured, the UE may be indicated in the transformMPRecoderDisabled field of the higher-layer parameter PTRS-UplinkConfig. RB0 to N RB1 The frequencyDensity and timeDensity of ptrs-MCS1 to ptrs-MCS3. The UE can schedule the PUSCH according to the MCS (l MCS ) and RB (N RB ) to determine the PT-RS density (L) in the time domain as described in Tables 22 and 23 PT-RS ) and PT-RS density in the frequency domain (K PT-RS In Table 22, ptrs-MCS4 is not specified as a higher-layer parameter, but the base station and UE can know that it is 29 or 28 according to the configured MCS table.

[0183] [Table 22]

[0184]

[0185] [Table 23]

[0186]

[0187] In the case where the transform precoder is not applied to PUSCH transmission and PTRS-UplinkConfig is configured, the base station may indicate a 2-bit "PTRS-DMRS Association" field to the UE to indicate the association between the PTRS and DMRS of DCI format 0_1 ​​or 0_2. The indicated 2-bit PTRS-DMRS Association field may be applied in Table 24 or Table 25 below according to the maximum number of PTRS ports configured by maxNrofPorts in the higher-layer parameter PTRS-UplinkConfig. In the case where the maximum number of PTRS ports is 1, the UE may determine the association between the PTRS and the DMRS using the PTRS-DMRS Association field and the 2 bits indicated by Table 24, and transmit the PTRS according to the determined association. In the case where the maximum number of PTRS ports is 2, the UE may determine the association between the PTRS and the DMRS using the PTRS-DMRS Association field and the 2 bits indicated by Table 25, and transmit the PTRS according to the determined association.

[0188] [Table 24]

[0189]

[0190] [Table 25]

[0191]

[0192] The DMRS ports in Tables 24 and 25 can be determined using a table determined by the "antenna port" field indicated by the same DCI and higher-layer parameter configuration as the DCI indicating PTRS-DMRS association. If the transform precoder is not configured by the higher-layer configuration of the PUSCH, and for DMRS, dmrs-Type is configured as 1, maxLength is configured as 2, and the rank of the PUSCH is 2, the UE can determine the DMRS port using the "antenna port(s)" table shown in Table 26 and the bits indicated by the antenna port field. If non-codebook-based PUSCH is supported, the UE can determine the rank value by referring to the SRI field indicated by the same DCI as the DCI including the "antenna port" field (i.e., if the SRI field is absent, the rank can be considered 1). If codebook-based PUSCH is supported, the UE can determine the rank value by referring to the TPMI field indicated by the same DCI as the DCI including the "antenna port" field. Table 26 is an example of an antenna port table referenced during configuration of the PUSCH described above, and if the PUSCH is configured with other parameters, the DMRS port can be determined based on the antenna port table according to the configuration and the bits in the antenna port field indicated by the DCI.

[0193] [Table 26]

[0194]

[0195] The first through fourth scheduled DMRSs in Table 24 can be defined as sequentially mapping the bits of the antenna port field of the DCI and the values ​​of the DMRS ports indicated by the antenna port table according to higher-layer configuration. For example, if the bits of the antenna port field of the DCI are 0001 and the DMRS port is determined by referring to Table 26 above, the scheduled DMRS ports can be 0 and 1, and DMRS port 0 can be defined as the first scheduled DMRS, and DMRS port 1 can be defined as the second scheduled DMRS. Similar applications can be applied to other antenna port fields and DMRS port bits determined by the antenna port table according to other higher-layer configurations. The UE can determine the single DMRS port associated with the PTRS port among the DMRS ports defined above by referring to the bit indicated by the PTRS-DMRS association in the DCI, and transmit the PTRS according to the determined DMRS port. In Table 25, the DMRS ports sharing PTRS port 0 and the DMRS ports sharing PTRS port 1 can be defined based on codebook-based PUSCH transmission or non-codebook-based PUSCH transmission. If the UE transmits PUSCH based on a partially coherent or non-coherent codebook, the uplink layers transmitted to PUSCH antenna ports 1000 and 1002 are associated with PTRS port 0, and the uplink layers transmitted to PUSCH antenna ports 1001 and 1003 are associated with PTRS port 1. To explain with a more specific example, if layer 3: TPMI=2 is selected for codebook-based PUSCH transmission, the first layer is associated with PTRS port 0 because the first layer is transmitted to PUSCH antenna ports 1000 and 1002, and the second and third layers are associated with PTRS port 1 because the second layer is transmitted to PUSCH antenna port 1001 and the third layer is transmitted to PUSCH antenna port 1002. Each of the three layers represents a DMRS port, the DMRS port for the first layer corresponds to the "first DMRS port of shared PTRS port 0" in Table 25, the DMRS port for the second layer corresponds to the "first DMRS port of shared PTRS port 1" in Table 25, and the DMRS port for the third layer corresponds to the "second DMRS port of shared PTRS port 1" in Table 25. Similarly, the DMRS port associated with PTRS port 0 and the DMRS port associated with PTRS port 1 can be determined based on different layer numbers and TPMIs.

[0196] If the UE transmits a PUSCH based on a non-codebook, the DMRS port can be distinguished as a DMRS port associated with PTRS port 0 and a DMRS port associated with PTRS port 1 according to the SRI and antenna port indicated by the DCI. More specifically, the SRS resources with usage of "nonCodebook" included in the SRS resource set are configured to be associated with PTRS port 0 or PTRS port 1 through the high-level parameter ptrs-PortIndex. The base station indicates the SRS resources used to transmit the non-codebook-based PUSCH through the SRI. At this time, each port of the indicated SRS resource is mapped one-to-one to each PUSCH DMRS port. The association between the PUSCH DMRS port and the PTRS port is determined according to the high-level parameter ptrs-PortIndex of the SRS resource mapped to the DMRS port. To explain with a more specific example, it is assumed that the ptrs-PortIndex of SRS resources 1 to 4 included in the SRS resource set with usage of "nonCodebook" are configured as n0, n0, n1 and n1, respectively. In addition, it is assumed that the PUSCH is indicated by the SRI as being transmitted through SRS resources 1, 2, and 4, and DMRS ports 0, 1, and 2 are indicated for the antenna port field. The ports of SRS resources 1, 2, and 4 are mapped to DMRS ports 0, 1, and 2, respectively. In addition, according to the ptrs-PortIndex in the SRS resource, DMRS ports 0 and 1 are associated with PTRS port 0, and DMRS port 2 is associated with PTRS port 1. Therefore, in Table 25, DMRS port 0 corresponds to the "first DMRS port sharing PTRS port 0", DMRS port 1 corresponds to the "second DMRS port sharing PTRS port 0", and DMRS port 2 corresponds to the "first DMRS port sharing PTRS port 1". Similarly, the DMRS port associated with PTRS port 0 and the DMRS port associated with PTRS port 1 can be determined by different SRI values ​​and ptrs-PortIndex configuration methods in different modes of the SRS resource. As described above for two PTRS ports, the UE determines the association between the DMRS port and the PTRS port. Thereafter, the UE determines a DMRS port to be associated with PTRS port 0 among multiple DMRS ports associated with each PTRS port by referring to the MSB bit of the PTRS-DMRS association, and determines a DMRS port to be associated with PTRS port 1 by referring to the LSB bit to transmit PTRS.

[0197] Hereinafter, UE capability reporting will be described.

[0198] In LTE and NR systems, a UE may perform the following procedure: in this procedure, while connected to a serving base station, the UE may report the capabilities supported by the UE to the corresponding base station. In the following description, the above-described procedure will be referred to as UE capability reporting.

[0199] A base station can transmit a UE Capability Query message to a connected UE to request a capability report. The message may include a UE capability request for each radio access technology (RAT) type of the base station. The RAT-type-specific request may include information such as supported frequency band combinations. Furthermore, in the case of a UE Capability Query message, the base station can request UE capabilities for multiple RAT types using a single RRC message container, or the base station can transmit a UE Capability Query message including multiple UE capability requests for each RAT type. This capability query can be repeated multiple times in a single message, and the UE can configure and report corresponding UE capability information messages multiple times. In next-generation mobile communication systems, UE capability requests for Multi-RAT Dual Connectivity (MR-DC), such as NR, LTE, and E-UTRA-NR Dual Connectivity (EN-DC), can be made. Typically, the UE Capability Query message is initially sent after the UE connects to the base station, but the base station can request the UE Capability Query message under any conditions if desired.

[0200] After the UE receives the UE capability report request from the base station in the above steps, the UE configures the UE capabilities based on the frequency band information and RAT type requested by the base station. The following summarizes the method for the UE to configure UE capabilities in the NR system.

[0201] 1. If the UE receives a list of LTE and / or NR frequency bands from the base station in response to a UE capability request, the UE can construct a frequency band combination (BC) for EN-DC and NR standalone (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 via the FreqBandList upon request. The frequency bands have priority in the order described in the FreqBandList.

[0202] 2. If the base station has set the "eutra-nr-only" flag or the "eutra" flag and requested UE capability reporting, the UE can remove all content related to NR SA BC from the configured BC candidate list. Such an operation can only happen when the LTE base station (eNB) requests the "eutra" capability.

[0203] 3. The UE can then remove the fallback BC from the candidate BC list configured in the above steps. As used herein, a fallback BC refers to a BC that can be obtained by removing the frequency band corresponding to at least one SCell from a specific BC. Since the BC before removing the frequency band corresponding to at least one SCell can already cover the fallback BC, it can be omitted. This step also applies to MR-DC, that is, also applies to LTE bands. The BCs remaining after the above steps constitute the final "candidate BC list."

[0204] 4. The UE selects a BC suitable for the requested RAT type from the final "candidate BC list" and selects the BC to be reported. In this step, the UE configures the supportedBandCombinationList in a predetermined order. That is, the UE configures the BC and UE capabilities for reporting according to the pre-configured rat-Type command (nr->eutra-nr->eutra). In addition, the UE configures the featureSetCombination for the configured supportedBandCombinationList and configures a list of "candidate feature set combinations" from the candidate BC list, where the list of fallback BCs (including capabilities of the same or lower steps) is removed from the candidate BC list. "Candidate feature set combinations" can include all feature set combinations for NR and EUTRA-NR BCs and can be obtained from the feature set combinations of the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0205] In addition, if the requested RAT type is eutra-nr and has an impact, featureSetCombinations can be included in both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, the feature set of NR is only included in UE-NR-Capabilities.

[0206] After the UE capabilities are configured, the UE transmits a UE capability information message including the UE capabilities to the base station. The base station performs scheduling and transmission / reception management suitable for the UE based on the UE capabilities received from the UE.

[0207] Hereinafter, non-coherent joint transmission (NC-JT) will be described. A UE can receive PDSCH from multiple TRPs using NC-JT.

[0208] Unlike traditional systems, 5G wireless communication systems can support not only services requiring high transmission rates, but also services with very short transmission delays and services requiring high connection density. In a wireless communication network that includes multiple cells, transmission and reception points (TRPs), or beams, coordinated transmission between various cells, TRPs, and / or beams can meet various service requirements by increasing the strength of the signal received by the UE or effectively controlling interference between cells, TRPs, and / or beams.

[0209] Joint transmission (JT) is a representative transmission scheme for the cooperative communication mentioned above, and is a scheme for increasing the strength or throughput of a signal received by a UE by transmitting a signal to one UE via multiple different cells, TRPs and / or beams. Here, the channels between each cell, TRP and / or beam and the UE may have different characteristics, and in particular, according to the channel characteristics of each link between each cell, TRP and / or beam and the UE, NC-JT that supports non-coherent precoding between each cell, TRP and / or beam may require separate precoding, MCS, resource allocation and TCI indication.

[0210] The NC-JT transmission described above 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). In PDSCH transmission, transmission information such as precoding, MCS, resource allocation, and TCI can be indicated through DL DCI and should be indicated independently for each cell, TRP, and / or beam used for NC-JT. This is a significant factor in increasing the payload required for DL ​​DCI transmission, which may have an adverse impact on the reception performance of the PDCCH used to transmit the DCI. Therefore, in order to support JT of PDSCH, it is necessary to carefully design the trade-off between the amount of DCI information and the control information reception performance.

[0211] Figure 6 An example of antenna port configuration and resource allocation for PDSCH transmission using cooperative communication in a communication system is shown.

[0212] refer to Figure 6 , an example for PDSCH transmission is described for each scheme of joint transmission (JT), and an example of radio resource allocation for each TRP is shown.

[0213] refer to Figure 6 , an example 600 is shown of supporting coherent joint transmission (C-JT) with interfering coding between various cells, TRPs and / or beams.

[0214] In the case of C-JT, TRP A 605 and TRP B 610 transmit a single data (PDSCH) to UE 615, and multiple TRPs can perform joint precoding. This can mean that TRPA 605 and TRPB 610 transmit DMRS through the same DMRS port to transmit the same PDSCH. For example, TRP A 605 and TRP B 610 can transmit DMRS to the UE through DMRS port A and DMRS port B, respectively. In this case, the UE can receive a piece of DCI information for receiving a PDSCH demodulated based on the DMRS transmitted through DMRS port A and DMRS port B.

[0215] Figure 6 An example 620 is shown of supporting non-coherent joint transmission (NC-JT) with non-coherent precoding between various cells, TRPs, or / and beams for PDSCH transmission.

[0216] In the case of NC-JT, the PDSCH is transmitted to the UE 635 on a per-cell, per-TRP, and / or per-beam basis, and separate precoding may be applied to each PDSCH. Each cell, TRP, and / or beam may transmit different PDSCHs or different PDSCH layers to the UE, thereby improving throughput compared to a single cell, TRP, and / or beam transmission. In addition, each cell, TRP, and / or beam may repeatedly transmit the same PDSCH to the UE, thereby improving reliability compared to a single cell, TRP, and / or beam transmission. For ease of description, a cell, TRP, and / or beam is generally referred to as a TRP.

[0217] In this case, various radio resource allocations can be considered, such as the case 640 where the frequency and time resources used for PDSCH transmission in multiple TRPs are the same, the case 645 where the frequency and time resources used in multiple TRPs do not overlap at all, and the case 650 where some frequency and time resources used in multiple TRPs overlap.

[0218] To support NC-JT, various forms, structures, and relationships of DCI can be considered to allocate multiple PDSCHs to one UE simultaneously.

[0219] Figure 7 An example of downlink control information (DCI) configuration for NC-JT in a wireless communication system is shown, where each TRP sends a different PDSCH or a different PDSCH layer to the UE.

[0220] refer to Figure 7, Case #1 700 is an example in which, in the case where N-1 different PDSCHs are transmitted from N-1 additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) for a single PDSCH transmission, control information for the PDSCHs transmitted from the N-1 additional TRPs is transmitted independently from control information for the PDSCHs transmitted from the serving TRP. That is, the UE can obtain control information for the PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through independent DCIs (DC1#0 to DCI#(N-1)). The formats between independent DCIs may be the same as or different from each other, and the payloads between DCls may also be the same as or different from each other. In Case #1 described above, the freedom of PDSCH control or allocation can be fully guaranteed, but when each DCI is transmitted by a different TRP, a difference between DCI coverage may be generated, and reception performance may be deteriorated.

[0221] Case #2 705 may depend on the control information used for the PDSCH, where, in addition to the serving TRP (TRP#0) used during a single PDSCH transmission, N-1 different PDSCHs are sent from N-1 additional TRPs (TRP#1 to TRP#(N-1)), control information (DCI) for the PDSCHs of each additional N-1 TRP is sent, and each DCI is sent from the serving TRP.

[0222] For example, DCI#0, which is control information for the PDSCH transmitted from the serving TRP (TRP#0), may include all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, but shortened DCI (hereinafter referred to as sDCI) (sDCI#0 to sDCI#(N-2)), which is control information for the PDSCH transmitted from the collaborative TRPs (TRP#1 to TRP#(N-1)), may include only some information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. Therefore, sDCI for transmitting control information for the PDSCH transmitted from the collaborative TRP has a smaller payload than normal DCI (nDCI) for transmitting control information related to the PDSCH transmitted from the serving TRP, and is therefore able to include reserved bits compared to nDCI.

[0223] In case #2 described above, the degree of freedom of each PDSCH control or allocation can be limited according to the content of the information elements included in the sDCI, but the reception capability of sDCI is better than nDCI, so the probability of generating differences between DCI coverage becomes lower.

[0224] Case #3 710 is an example in which, in the case where N-1 different PDSCHs are transmitted from N-1 additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) for a single PDSCH transmission, one piece of control information for the PDSCHs of the N-1 additional TRPs is transmitted and the DCI depends on the control information for the PDSCH transmitted from the serving TRP.

[0225] For example, in the case of DCI#0 as control information for the PDSCH transmitted from the serving TRP (TRP#0), all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 may be included. In the case of control information for the PDSCH transmitted from the collaborative TRPs (TRP#1 to TRP#(N-1)), only some information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 may be collected and transmitted in one "secondary" DCI (sDCI). For example, the sDCI may include at least one piece of HARQ-related information, such as frequency domain resource allocation and time domain resource allocation for the collaborative TRP and MCS. In addition, information not included in the sDCI, such as the bandwidth part (BWP) indicator and carrier indicator, may follow the DCI of the serving TRP (DCI#0, normal DCI, or nDCI).

[0226] In case #3 710, the freedom of PDSCH control or allocation can be limited according to the content of the information elements included in the sDCI, but the reception performance of the sDCI can be controlled, and compared with case #1 700 or case #2 705, case #3 710 can have smaller complexity of DCI blind decoding of the UE.

[0227] Case #4 715 is an example of transmitting control information for PDSCHs transmitted from N-1 additional TRPs in the same DCI (long DCI) as the control information for PDSCHs transmitted from the serving TRP (TRP#0), in a case where different N-1 PDSCHs are transmitted from N-1 additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) for a single PDSCH transmission. That is, the UE can obtain control information for PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In case #4 715, the complexity of DCI blind decoding of the UE may not be increased, but the degree of freedom of PDSCH control or allocation may be low, for example, the number of collaborative TRPs is limited according to the long DCI payload restriction.

[0228] In the following description and embodiments, sDCI may indicate each supplementary DCI such as shortened DCI, auxiliary DCI or normal DCI (DCI formats 1_0 and 1_1 described above) that includes PDSCH control information sent in a collaborative TRP, and unless specific limitations are mentioned, the corresponding description may be similarly applied to each supplementary DCI.

[0229] In the following description and embodiments, Case #1 700, Case #2 705, and Case #3 710, in which one or more DCIs (or PDCCHs) are used to support NC-JT, can be classified as multi-PDCCH-based NC-JT, and Case #4 715, in which a single DCI (or PDCCH) is used to support NC-JT, can be classified as single-PDCCH-based NC-JT. In multi-PDCCH-based PDSCH transmission, the CORESET used to schedule DCI for the serving TRP (TRP#0) is separated from the CORESET used to schedule DCI for the cooperating TRPs (TRP#1 to TRP#(N-1)). Methods for distinguishing CORESETs include distinguishing by a higher layer indicator for each CORESET and distinguishing by the beam configuration for each CORESET. Furthermore, in single-PDCCH-based NC-JT, a single DCI schedules a single PDSCH with multiple layers, rather than multiple PDSCHs, and multiple layers can be transmitted from multiple TRPs. In this case, the association between the layer and the TRP transmitting the corresponding layer may be indicated by a transmission configuration indicator (TCI) indication for the layer.

[0230] According to an embodiment of the present disclosure, when actually applied, "collaborative TRP" may be replaced by various terms such as "collaborative panel" or "collaborative beam".

[0231] According to an embodiment of the present disclosure, "a case where NC-JT is applied" may be interpreted differently depending on the situation as "a case where the UE simultaneously receives one or more PDSCHs in one BWP", "a case where the UE simultaneously receives PDSCHs in one BWP based on two or more transmission configuration indicators (TCI) indications", and "a case where the PDSCH received by the UE is associated with one or more DMRS port groups", but is used by one expression for convenience of description.

[0232] In the present disclosure, the wireless protocol structure for NC-JT can be used differently depending on the TRP development scenario. For example, if there is no backhaul delay or a small backhaul delay between the cooperating TRPs, a method using a structure based on MAC layer multiplexing (a method similar to CA) can be used. On the other hand, when the backhaul delay between the cooperating TRPs is too large to be ignored (for example, when it takes 2ms or longer to exchange information such as CSI, scheduling, and HARQ-ACK between the cooperating TRPs), a method that ensures robustness to delay can be used through an independent structure for each TRP from the RLC layer (a method similar to DC).

[0233] A UE that supports C-JT / NC-JT can receive C-JT / NC-JT related parameters or setting values ​​from a higher-layer configuration and set the UE's RRC parameters based on them. For higher-layer configuration, the UE can use UE capability parameters, such as tci-StatePDSCH. Here, the UE capability parameter (e.g., tci-StatePDSCH) can define the TCI states used for PDSCH transmission. 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, and a maximum of 8 states that can be indicated by 3 bits of the TCI field of the DCI can be configured through a MAC CE message among the configured number. The maximum value of 128 indicates the value indicated by the maxNumberConfiguredTCIstatesPerCC parameter in the tci-StatePDSCH 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 a beamforming change command or beamforming indication for at least one PDSCH in one TRP.

[0234] Next, the multi-TRP transmission method based on multi-DCI will be described. The multi-TRP transmission method based on multi-DCI is a method of configuring a downlink control channel for NC-JT based on multiple PDCCHs to transmit PDSCH.

[0235] When DCI scheduled by PDSCH for each TRP is transmitted, NC-JT based on multiple PDCCHs can have a CORESET or search space distinguished between each TRP. The CORESET or search space for each TRP can be configured according to at least one of the following configuration cases.

[0236] -High-layer index configuration for each CORESET: CORESET configuration information configured via a high-layer may include an index value, and the TRP used for PDCCH transmission in the corresponding CORESET may be distinguished by the configured index value for each CORESET. That is, in a set of CORESETs having the same high-layer index value, it may be considered that the same TRP transmits a PDCCH or that a PDCCH for scheduling a PDSCH of the same TRP is transmitted. The index for each CORESET may be named CORESETPoolIndex, and it may be considered that PDCCHs are transmitted from the same TRP in a CORESET configured with the same CORESETPoolIndex value. For a CORESET for which a CORESETPoolIndex value has not been configured, it may be considered that a default value has been configured for CORESETPoolIndex, and the default value may be 0.

[0237] >In the present disclosure, when the number of types of CORESETPoolIndex of each of the 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 may consider that the base station is capable of using a multi-TRP transmission method based on multi-DCI.

[0238] >Different from this, in the present disclosure, when the number of types of CORESETPoolIndex of each of the multiple CORESETs included in the higher layer signaling PDCCH-Config is 1, that is, when all CORESETs have the same CORESETPoolIndex of 0 or 1, the UE can regard the base station as performing transmission using a single TRP instead of using a multi-TRP transmission method based on multi-DCI.

[0239] -Multi-PDCCH-Config configuration: Multiple values ​​of PDCCH-Config can be configured in one BWP, and each PDCCH-Config can include a PDCCH configuration for each TRP. That is, a list of CORESETs for each TRP and / or a list of search spaces for each TRP can be included in one PDCCH-Config, and one or more CORESETs and one or more search spaces included in one PDCCH-Config can be considered to correspond to a specific TRP.

[0240] -CORESET beam / beam group configuration: The TRP corresponding to the corresponding 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 considered or determined that the same TRP is transmitted via the CORESET, or the PDCCH for scheduling the PDSCH of the same TRP is transmitted in the corresponding CORESET.

[0241] -Search space beam / beam group configuration: A beam or beam group can be configured for each search space, and the TRP used for each search space can be differentiated based on the configured beam or beam group. For example, if the same beam / beam group or TCI state is configured for multiple search spaces, it can be considered or determined that the same TRP is transmitted in the corresponding search space, or the PDCCH for scheduling the PDSCH of the same TRP is transmitted in the corresponding search space.

[0242] As described above, by distinguishing CORESET or search space according to TRP, it is possible to classify PDSCH and HARQ-ACK information for each TRP, and based on this, it is possible to independently generate a HARQ-ACK codebook for each TRP and independently use PUCCH resources.

[0243] Configuration can be independent for each cell or BWP. For example, although two different CORESETPoolIndex values ​​are configured for the PCell, a CORESETPoolIndex value may not be configured for a specific SCell. In this case, NC-JT transmission can be considered to have been configured for the PCell, while NC-JT transmission has not been configured for the SCell for which the CORESETPoolIndex value is not configured.

[0244] The PDSCH TCI state activation / deactivation MAC-CE that can be applied to the multi-TRP transmission method based on multi-DCI can follow Figure 8 .

[0245] Figure 8An example of a PDSCH TCI state activation / deactivation MAC-CE is shown. If the UE does not receive the configuration of the CORESETPoolIndex for each of all CORESETs within the higher-layer signaling PDCCH-Config, the UE may ignore the CORESET Pool ID field 955 within the corresponding MAC-CE 950. If the UE is capable of supporting a multi-DCI-based multi-TRP transmission method, that is, when each CORESET within the higher-layer signaling PDCCH-Config has a different CORESETPoolIndex, the UE may activate the TCI state within the DCI included in the PDCCH transmitted by the CORESET having the same CORESETPoolIndex value as the CORESET Pool ID field 955 within the corresponding MAC-CE 950. For example, if the CORESET Pool ID field 955 within the corresponding MAC-CE 950 has a value of 0, the TCI state within the DCI included in the PDCCH transmitted by the CORESET having a CORESETPoolIndex of 0 may follow the activation information of the corresponding MAC-CE.

[0246] If the UE receives a configuration from the base station that enables the use of a multi-TRP transmission method based on multi-DCI, that is, the number of types of CORESETPoolIndex of multiple CORESETs included in the high-layer signaling PDCCH-Config is greater than 1 or each CORESET has a different CORESETPoolIndex, the UE is able to know that there are the following restrictions regarding the PDSCH scheduled by the PDCCH within each CORESET with two different CORESETPoolIndex.

[0247] First, if the PDSCHs indicated by the PDCCHs in each CORESET with two different CORESETPoolIndex overlap completely or partially, the UE may apply the TCI states indicated by each PDCCH to different CDM groups. That is, two or more TCI states may not be applied to one CDM group.

[0248] Second, if the PDSCHs indicated by PDCCHs within respective CORESETs with two different CORESETPoolIndex overlap completely or partially, the UE can expect that the number of actual front-loaded DMRS symbols, the number of actual additional DMRS symbols, the position of the actual DMRS symbols and the DMRS type of the respective PDSCHs are no different.

[0249] Third, the UE can expect that the bandwidth part indicated by the PDCCH within each CORESET with two different CORESETPoolIndex is the same and the subcarrier spacing is also the same.

[0250] Fourth, the UE may expect that information on the PDSCH scheduled by the PDCCH within each CORESET with two different CORESETPoolIndex is fully included in each PDCCH.

[0251] Next, a multi-TRP transmission method based on a single DCI will be described. The multi-TRP transmission method based on a single DCI is a method of configuring a downlink control channel for NC-JT based on a single PDCCH to transmit a PDSCH.

[0252] In a multi-TRP transmission method based on a single DCI, a PDSCH transmitted by multiple TRPs can be scheduled by one DCI. Here, as a method of indicating the number of TRPs transmitting the corresponding PDSCH, the number of TCI states can be used. That is, when the number of TCI states indicated by the DCI for scheduling the PDSCH is 2, NC-JT transmission based on a single PDCCH can be considered, and when the number of TCI states is 1, single TRP transmission can be considered. The TCI state indicated by the DCI can correspond to one or two TCI states among the TCI states activated by the MAC CE. If the TCI state of the DCI corresponds to two TCI states activated by the MAC CE, the TCI code point indicated by the DCI is associated with the TCI state 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 the TCI code point) is 2.

[0253] As another example, when at least one of all codepoints in the TCI state field within the DCI indicates two TCI states, the UE may assume that the base station is capable of performing transmission according to the multi-TRP method based on a single DCI. In this case, at least one codepoint indicating two TCI states within the TCI state field may be activated using an enhanced PDSCH TCI state activation / deactivation MAC-CE.

[0254] Figure 9 The enhanced PDSCH TCI state activation / deactivation MAC-CE structure is shown; the meaning of each field in the MAC CE and the configurable value for each field are as follows.

[0255] - Serving Cell ID: This field indicates the identity of the serving cell for which the MAC CE applies. The length of the field is 5 bits. If the indicated serving cell is configured as part of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 as specified in TS 38.331 [5], then this MAC CE applies to all serving cells configured in the set simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2, respectively;

[0256] - BWP ID: This field indicates the DLB WP for which the MAC CE applies, as the code point of the DCI Bandwidth Part Indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits.

[0257] -Ci: This field indicates whether there is an octet containing TCI status IDi,2. If this field is set to 1, there is an octet containing TCI status IDi,2. If this field is set to 0, there is no octet containing TCI status IDi,2.

[0258] -TCI State IDi,j: This field indicates the TCI state identified by TCI-StateId as specified in TS 38.331 [5], where i is the index of the codepoint of the DCI Transmission Configuration Indication field as specified in TS 38.212 [9], and TCI State IDi,j represents the jth TCI state indicated for the i-th codepoint in the DCI Transmission Configuration Indication field. The TCI codepoint to which the TCI state is mapped is determined by its ordinal position among all TCI codepoints in the set with TCI State IDi,j fields, i.e., the first TCI codepoint with TCI State ID0,1 and TCI State ID0,2 shall be mapped to codepoint value 0, the second TCI codepoint with TCI State ID1,1 and TCI State ID1,2 shall be mapped to codepoint value 1, and so on. Indication of TCI State IDi,2 based on the Ci field is optional. The maximum number of activated TCI codepoints is 8, and the maximum number of TCI states mapped to a TCI codepoint is 2.

[0259] -R: Reserved bit, set to 0.

[0260] exist Figure 9In the MAC-CE, if the C0 field 905 has a value of 1, the corresponding MAC-CE may also include a TCI state ID 0,2 field 915 in addition to the TCI state ID 0,1 field 910. This indicates that TCI state ID 0,1 and TCI state ID 0,2 are activated for the zeroth code point of the TCI state field included in the DCI, and when the base station indicates the corresponding code point to the UE, the UE can receive an indication of both TCI states. If the C0 field 905 has a value of 0, the corresponding MAC-CE cannot include the TCI state ID 0,2 field 915, and this indicates that one TCI state corresponding to TCI state ID 0,1 is activated for the zeroth code point of the TCI state field included in the DCI.

[0261] Configuration can be independent for each cell or BWP. For example, while the maximum number of activated TCI states corresponding to one TCI code point in the PCell is 2, the maximum number of activated TCI states corresponding to one TCI code point in a specific SCell may be 1. In this case, it can be considered that NC-JT is configured for the PCell, but not for the SCell.

[0262] Next, we describe a method for distinguishing between single-DCI-based multi-TRP PDSCH repetition transmission schemes. The UE can receive indications of different single-DCI-based multi-TRP PDSCH repetition transmission schemes (e.g., time division multiplexing (TDM), FDM, and spatial division multiplexing (SDM)) from the base station based on the value indicated by the DCI field and higher-layer signaling configuration. Table 27 below shows a method for distinguishing between single and multiple TRP-based schemes indicated to the UE based on specific DCI field values ​​and higher-layer signaling configuration.

[0263] [Table 27]

[0264]

[0265] Each column in the above Table 27 can be described as follows.

[0266] - Number of TCI states (second column): indicates the number of TCI states indicated by the TCI state field within the DCI, and can be 1 or 2.

[0267] - Number of CDM groups (third column): Indicates the number of different CDM groups for the DRMS ​​port indicated by the Antenna Port field in the DCI. The number of CDM groups can be 1, 2, or 3.

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

[0269] >Condition 1: At least one of all TDRA entries that can be indicated by the time domain resource allocation field includes a configuration of repetitionNumber and the TDRA entry indicated by the time domain resource allocation field in the DCI includes a configuration of repetitionNumber greater than 1.

[0270] >Condition 2: A case where at least one of all TDRA entries that can be indicated by the time domain resource allocation field includes a configuration of repetitionNumber and a TDRA entry indicated by the time domain resource allocation field within the DCI does not include a configuration of repetitionNumber.

[0271] >Condition 3: All TDRA entries that can be indicated by the time domain resource allocation field do not include the configuration of repetitionNumber.

[0272] - Regarding repetitionScheme configuration (fifth column): Indicates whether repetitionScheme as a higher layer signaling is configured. RepetitionScheme as a higher layer signaling can receive the configuration of one of "tdmSchemeA", "fdmSchemeA" and "fdmSchemeB".

[0273] -Transmission scheme indicated to UE (sixth column): Indicates the single TRP or multi-TRP scheme indicated according to each combination (first column) represented by Table 29 above.

[0274] > Single TRP: Indicates PDSCH transmission based on a single TRP. If the UE receives the configuration of pdsch-aggregationfactor in the higher-layer signaling PDSCH-config, the UE can receive multiple scheduling of PDSCH repetitive transmissions based on a single TRP received through this configuration. Otherwise, the UE can receive scheduling of a single PDSCH transmission based on a single TRP.

[0275] >Single TRP TDM scheme B: indicates PDSCH repetition transmission based on time resource division between time slots based on a single TRP. The UE retransmits the PDSCH in the time dimension a number of times 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, according to condition 1 described above related to the repetitionNumber. In this case, the starting symbol and symbol length of the PDSCH indicated by the TDRA entry are equally applied to each time slot corresponding to the repetitionNumber, and the same TCI state is applied to each PDSCH repetition transmission. The corresponding scheme is similar to the time slot aggregation scheme in that PDSCH repetition transmission between time slots is performed in the time resource, but the difference is that the repetition transmission indication is dynamically determined based on the time domain resource allocation field within the DCI.

[0276] >Multi-TRP SDM: Indicates a multi-TRP-based spatial resource division PDSCH transmission scheme. This is a method of dividing layers and performing reception from each TRP, and can increase the reliability of PDSCH transmission because it is possible to perform transmission at a reduced coding rate by increasing the number of layers even if it is not a repeated transmission scheme. The UE can receive the PDSCH by applying each of the two TCI states indicated by the TCI state field within the DCI to two CDM groups indicated by the base station.

[0277] Multi-TRP FDM Scheme A: This scheme indicates a PDSCH transmission scheme with frequency resource partitioning based on multiple TRPs. It has a single PDSCH transmission opportunity and is capable of performing transmission with higher reliability by increasing frequency resources and reducing the coding rate. However, it does not perform repeated transmission like Multi-TRP SDM. Multi-TRP FDM Scheme A applies two TCI states, indicated by the TCI state field within the DCI, to non-overlapping frequency resources. If the PRB bundling size is determined as wideband and the number of RBs indicated by the frequency-domain resource allocation field is N, the UE can receive the first ceil(N / 2) RBs by applying the first TCI state and the remaining floor(N / 2) RBs by applying the second TCI state. Here, ceil(.) and floor(.) are operators for rounding the first decimal place up and down. If the PRB bundling size is determined as 2 or 4, even-numbered PRGs are received by applying the first TCI state, and odd-numbered PRGs are received by applying the second TCI state.

[0278] >Multi-TRP FDM Scheme B: Indicates a PDSCH repetition transmission scheme based on frequency resource partitioning based on multiple TRPs, with two PDSCH transmission opportunities to repeatedly transmit the PDSCH at each opportunity. In the same manner as Multi-TRP FDM Scheme A, Multi-TRP FDM Scheme B can also apply two TCI states indicated by the TCI state field within the DCI to frequency resources that do not overlap with each other. If the PRB cluster size is determined as wideband and the number of RBs indicated by the frequency domain resource allocation field is N, the UE can receive the first ceil(N / 2) RBs by applying the first TCI state and the remaining floor(N / 2) RBs by applying the second TCI state. Here, ceil(.) and floor(.) are operators used to round the first decimal place up and down. If the PRB cluster size is determined to be 2 or 4, even-numbered PRGs are received by applying the first TCI state, and odd-numbered PRGs are received by applying the second TCI state.

[0279] >Multi-TRP TDM scheme A: Indicates a PDSCH repetition transmission scheme within a time slot based on time resource division of multiple TRPs. The UE has two PDSCH transmission opportunities within one time slot, and the first reception opportunity can be determined based on the starting symbol and symbol length of the PDSCH indicated by the time domain resource allocation field within the DCI. The starting symbol of the second reception opportunity of the PDSCH can be the opportunity where the symbol offset is applied from the last symbol of the first transmission opportunity by the higher-layer signaling StartingSymbolOffsetK, and the transmission opportunity corresponding to the symbol length indicated thereby can be determined. If the higher-layer signaling StartingSymbolOffsetK is not configured, the symbol offset can be considered to be 0.

[0280] >Multi-TRP TDM Scheme B: Indicates the PDSCH repetition transmission scheme between time slots based on the time resource division of multiple TRPs. The UE has one PDSCH transmission opportunity within a time slot and can receive repetition transmission based on the start symbol and symbol length of the same PDSCH during the time slot corresponding to the repetitionNumber indicated by the time domain resource allocation field within the DCI. If the repetitionNumber is 2, the UE can receive the PDSCH repetition transmission of the first and second time slots by applying the first and second TCI states, respectively. If the repetitionNumber is greater than 2, the UE can use different TCI state application schemes according to the configured high-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 method is applied identically to the remaining PDSCH transmission opportunities. If tciMapping is configured as sequentialMapping, the first TCI state can be applied to the first and second PDSCH transmission opportunities, the second TCI state can be applied to the third and fourth PDSCH transmission opportunities, and the same TCI state application method can be equally applied to the remaining PDSCH transmission opportunities.

[0281] Hereinafter, a single TCI state indication and activation method based on a unified TCI scheme will be described. The unified TCI scheme may refer to a scheme for unifying and managing the TCI state scheme used in downlink reception and the transmission and reception beam management scheme for spatial relationship information used in uplink transmission of the UE, which are divided in the existing Rel-15 / 16 as TCI states. Therefore, if instructed by the base station to perform beam management using the TCI state even for uplink transmission based on the unified TCI scheme, the UE can perform beam management using the TCI state. In the case where the UE is configured with a higher-layer signaling TCI-State with higher-layer signaling tci-stateId-r17 from the base station, the UE can perform operations based on the unified TCI scheme using the corresponding TCI-State.

[0282] The TCI-status based on the unified TCI scheme may include two types of joint TCI states or individual TCI states.

[0283] The first type is a joint TCI state, and a TCI state for applying to uplink transmission and downlink reception through one TCI-State can be indicated from the base station to the UE. In the case where the TCI state is indicated to the UE based on the joint TCI state, the RS corresponding to the qcl-Type1 of the TCI-State based on the corresponding joint TCI state can be used to indicate to the UE the parameters for downlink channel estimation, and the RS corresponding to the qcl-Type2 can be used to indicate to the UE the parameters used as a downlink reception beam or reception filter. In the case where the TCI-State is indicated to the UE based on the joint TCI state, the RS corresponding to the qcl-Type2 of the TCI-State based on the corresponding joint DL / UL TCI state can be used to indicate to the UE the parameters used as an uplink transmission beam or transmission filter. In doing so, if the joint TCI state is indicated to the UE, the UE can apply the same beam to uplink transmission and downlink reception.

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

[0285] If the DL TCI state and the UL TCI state are indicated to the UE together, the reference RS or source RS configured in the corresponding UL TCI state may be used to indicate to the UE the parameters used for the uplink transmit beam or transmit filter. In addition, if the DL TCI state and the UL TCI state are indicated to the UE together, the RS corresponding to the qcl-Type1 of the corresponding DL TCI state may be used to indicate to the UE the parameters for downlink channel estimation, and the RS corresponding to the qcl-Type2 may be used to indicate to the UE the parameters used for the downlink receive beam or receive filter. At this time, 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 may apply the beam separately to uplink transmission and downlink reception based on the indicated UL TCI state and DL TCI state.

[0286] The UE can be configured with up to 128 joint TCI states from the base station for each specific BWP in a specific cell through higher-layer signaling. Additionally, up to 64 or 128 DL TCI states can be configured for each specific BWP in a specific cell through higher-layer signaling based on the UE capability report. The DL TCI states for the individual TCI states 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 in the individual TCI states, then the 64 DL TCI states can be included in the 128 joint TCI states.

[0287] Based on the UE capability report, up to 32 or 64 UL TCI states of the individual TCI state can be configured for each specific BWP in a specific cell through high-layer signaling. The UL TCI state and the joint TCI state of the individual TCI state can use the same high-layer signaling structure, as the relationship between the DL TCI state and the joint TCI state of the individual TCI state, and the UL TCI state of the individual TCI state can use a different high-layer signaling structure from the DL TCI state of the joint TCI state and the individual TCI state.

[0288] Therefore, the use of different or the same higher layer signaling structures can be defined in the standard, and the use of different or the same higher layer signaling structures can be distinguished by another higher layer signaling configured by the base station based on the UE capability report containing information about whether one of the two types supported by the UE is used.

[0289] The UE can use one of the joint TCI state and the separate TCI state configured from the base station to receive transmit and receive beam-related indications in a unified TCI manner. Whether the UE uses the joint TCI state or the separate TCI state can be configured by the base station through higher layer signaling.

[0290] The UE can receive transmit and receive beam-related indications using a method selected from the joint TCI state and the separate TCI state through high-layer signaling. When doing so, the UE's transmit and receive beam indication method from the base station can include two methods: a MAC-CE-based indication method and a MAC-CE-based activation and DCI-based indication method.

[0291] In the case where the UE receives a transmit and receive beam-related indication using a joint TCI state through higher layer signaling, the UE can perform transmit and receive beam application operations by receiving a MAC-CE indicating the joint TCI state from the base station, and the base station can schedule the UE to receive the PDSCH including the corresponding MAC-CE on the PDCCH. In the case where the MAC-CE includes one joint TCI state, the UE can use the joint TCI state indicated 3 ms after PUCCH transmission to determine the uplink transmit beam, transmit filter and downlink receive beam, or receive filter, wherein the PUCCH transmission includes HARQ-ACK information indicating whether the PDSCH including the corresponding MAC-CE is successfully received. In the case where the MAC-CE includes two or more joint TCI states, the UE can identify multiple joint TCI states indicated by the MAC-CE corresponding to each code point of the TCI state field of DCI format 1_1 or 1_2, and activate the indicated joint TCI state 3 ms after the PUCCH transmission including HARQ-ACK information, wherein the HARQ-ACK information indicates whether the PDSCH including the corresponding MAC-CE is successfully received. Next, the UE may receive DCI format 1_1 or 1_2 and apply a joint TCI state indicated by the TCI state field of the corresponding DCI to the uplink transmit and downlink receive beams. In doing so, 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).

[0292] In the case where the UE receives transmit and receive beam-related indications using a separate TCI state through higher layer signaling, the UE can perform transmit and receive beam application operations by receiving a MAC-CE indicating a separate TCI state from the base station, and the base station can schedule PDSCH reception including the corresponding MAC-CE for the UE on the PDCCH. In the case where the MAC-CE includes a separate TCI state set, the UE can use the separate TCI state included in the separate TCI state set indicated 3ms after PUCCH transmission to determine the uplink transmit beam, transmit filter and downlink receive beam, or receive filter, wherein the PUCCH transmission includes HARQ-ACK information indicating whether the corresponding PDSCH is successfully received. At this time, the separate TCI state set can indicate one or more separate TCI states of a code point of the TCI state field of DCI format 1_1 or 1_2. In addition, the separate TCI state set can include one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state. In the case where the MAC-CE includes two or more separate TCI state sets, the UE can identify the multiple separate TCI state sets indicated by the MAC-CE corresponding to the respective codepoints of the TCI state field of DCI format 1_1 or 1_2, and activate the indicated separate TCI state sets 3 ms after the PUCCH transmission including HARQ-ACK information indicating whether the corresponding PDSCH was successfully received. In this case, each codepoint of the TCI state field of DCI format 1_1 or 1_2 can indicate one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state. The UE can receive DCI format 1_1 or 1_2 and apply the separate TCI state set indicated by the TCI state field of the corresponding DCI to uplink transmit and downlink receive beams. In doing so, 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).

[0293] Figure 10 FIG. 4 shows beam application time that can be considered when using a unified TCI scheme in a wireless communication system.

[0294] As described above, the UE can receive DCI format 1_1 or 1_2 with or without downlink data channel scheduling information (DL allocation) from the base station, and apply one joint TCI state or separate TCI state set indicated by the TCI state field of the corresponding DCI to the uplink transmit beam and the downlink receive beam.

[0295] - DCI format 1_1 or 1_2 with DL allocation 1000: If a UE receives DCI format 1_1 or 1_2 (PDCCH) from a base station including downlink data channel scheduling information (indicated by reference numeral 1001) indicating a joint TCI state or a set of individual TCI states based on a unified TCI scheme, the UE may receive a PDSCH (indicated by reference numeral 1005) scheduled based on the received DCI and transmit a PUCCH (indicated by reference numeral 1010) including a HARQ-ACK indicating the success or failure of receiving the DCI and PDSCH. In this case, the HARQ-ACK may include the success or failure of both the DCI and the PDSCH. If at least one of the DCI and the PDSCH is not received, the UE may transmit a NACK. If both the DCI and the PDSCH are successfully received, the UE may transmit an ACK.

[0296] - DCI format 1_1 or 1_2 without DL allocation 1050: If the UE receives DCI format 1_1 or 1_2 (PDCCH) (indicated by reference numeral 1055) from the base station to indicate one joint TCI state or separate TCI state set based on the unified TCI scheme, the UE may assume the following for the corresponding DCI:

[0297] - Includes CRC scrambled by CS-RNTI

[0298] - Each bit value allocated to a field used as a redundancy version (RV) field is 1.

[0299] -The value of each bit assigned to the field used as the MCS field is.

[0300] - Each bit value allocated to a field used as a New Data Indication (NDI) field is 0.

[0301] -For FDRA type 0, each bit value assigned to the FDRA field is 0, for FDRA type 1, each bit value assigned to the FDRA field is 1, and for FDRA scheme dynamicSwitch, each bit value assigned to the FDRA field is 0.

[0302] The UE may transmit a PUCCH (indicated by reference numeral 1060 ) including HARQ-ACK indicating reception success or failure of the DCI format 1_1 or 1_2 assuming the above details.

[0303] - Regarding DCI format 1_1 or 1_2 with DL allocation 1000 and without DL allocation 1050, if the new TCI state indicated by DCI 1001 and 1055 has been indicated and is the same as the TCI state applied to the uplink transmission and downlink reception beams, the UE may maintain the previously applied TCI state. In the event that the new TCI state is different from the existing TCI state, the UE may determine the application time 1030 and 1080 of the joint TCI state or the individual TCI state set indicated by the TCI state field of the DCI after the initial time slots 1020 and 1070 corresponding to the beam application time (BAT) 1015 and 1065 after PUCCH transmission, and may use the previously indicated TCI state 1025 and 1075 until the corresponding time slots 1020 and 1070.

[0304] -For DCI formats 1_1 or 1_2 with DL allocation 1000 and without DL allocation 1050, BAT can be configured with higher layer signaling based on UE capability reporting information using a specific number of OFDM symbols. The parameter set for BAT and the first slot after BAT can be determined based on the minimum parameter set among all cells applying the joint TCI state or individual TCI state set indicated by the DCI.

[0305] The UE can apply one joint TCI state indicated by MAC-CE or DCI to the reception of the CORESET connected to each UE-specific search space, the reception of the PDSCH and the transmission of the PUSCH scheduled by the PDCCH transmitted from the corresponding CORESET, and the transmission of each PUCCH resource.

[0306] In the case where a single TCI state set indicated by MAC-CE or DCI includes a DL TCI state, the UE may apply a single TCI state set to the reception of the CORESET connected to each UE-specific search space and to the reception of the PDSCH scheduled by the PDCCH sent from the corresponding CORESET, and may apply a single TCI state set to each PUSCH and PUCCH resource based on the indicated existing UL TCI state.

[0307] In the case where a single TCI state set indicated by MAC-CE or DCI contains a UL TCI state, the UE can apply the UL TCI state to each PUSCH and PUCCH resource, and can apply it to the reception of the CORESET connected to each UE-specific search space and the reception of the PDSCH scheduled by the PDCCH sent from the corresponding CORESET based on the previously indicated DL TCI state.

[0308] -If a single TCI state set indicated by MAC-CE or DCI includes a DL TCI state and a UL TCI state, the UE can apply the DL TCI state to the reception of the CORESET connected to each UE-specific search space and the reception of the PDSCH scheduled by the PDCCH sent from the corresponding CORESET, and can apply the UL TCI state to each PUSCH and PUCCH resource.

[0309] The following describes a single TCI status indication and activation method based on a unified TCI scheme. The UE receives scheduling of a PDSCH including the following MAC-CE from the base station, and starting from three slots after transmitting the HARQ-ACK for the corresponding PDSCH to the base station, the UE can interpret each code point of the TCI status field of DCI format 1_1 or 1_2 based on the information in the MAC-CE received from the base station. In other words, the UE can activate each entry of the MAC-CE received from the base station to each code point of the TCI status field in DCI format 1_1 or 1_2.

[0310] Figure 11 An example of a MAC-CE structure for activation and indication of a joint TCI state or a separate DL or UL TCI state in a wireless communication system is shown. The meaning of each field in the MAC-CE structure may be as follows.

[0311] -Serving Cell ID 1100: This field may indicate the serving cell to which the corresponding MAC-CE applies. The length of this field may be 5 bits. In the case where the serving cell indicated by this field is included in one or more of simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4 of the higher layer signaling, the MAC-CE may be applied to all serving cells included in one or more of simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, and simultaneousU-TCI-UpdateList4 in which the serving cell indicated by this field is included.

[0312] -DL BWP ID 1105: This field may indicate the DL BWP to which the corresponding MAC-CE is to be applied, and the meaning of each code point in this field may correspond to each code point of the BWP indicator in the DCI. The length of this field may be 2 bits.

[0313] -UL BWP ID 1110: This field may indicate the UL BWP to which the corresponding MAC-CE is to be applied, and the meaning of each code point of this field may correspond to each code point of the BWP indicator in the DCI. The length of this field may be 2 bits.

[0314] -P i 1115: This field may indicate whether each code point of the TCI status field in DCI format 1_1 or 1_2 has multiple TCI states or a single TCI state. i In case of having a value of 1, it indicates that the corresponding i-th code point has multiple TCI states, and this may indicate that the corresponding code point may include a separate DL TCI state and a separate UL TCI state. i With a value of 0, it indicates that the corresponding i-th codepoint has a single TCI state, and this may indicate that the corresponding codepoint may include one of a joint TCI state, a separate DCI TCI state, or a separate UL TCI state.

[0315] -D / U 1120: This field may indicate whether the TCI State ID field in the same octet is a joint TCI state, a separate DL TCI state, or a separate UL TCI state. If this field has a value of 1, the TCI State ID field in the same octet may be a joint TCI state or a separate DL TCI state, and if this field has a value of 0, the TCI State ID field in the same octet may be a separate UL TCI state.

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

[0317] -R: Indicates a reserved bit and can be configured as 0.

[0318] For the above described Figure 11 MAC-CE structure, the UE may include in the corresponding MAC-CE structure Figure 11 The third octet of the P1, P2, ..., P8 fields in ServingCellConfig is used, regardless of whether unifiedTCI-StateType-r17 in MIMOparam-r17 in ServingCellConfig as a higher layer signaling is configured as a joint type or a separate type. In this case, the UE can perform TCI state activation by using a fixed MAC-CE structure regardless of the higher layer signaling configured from the base station. As another example, for the above-described Figure 11 MAC-CE structure, when the high-level signaling unifiedTCI-StateType-r17 in MIMOparam-r17 in ServingCellConfig is configured as a joint type, the UE can omit the Figure 11 In this case, the UE can save a maximum of 8 bits of the payload of the corresponding MAC-CE according to the higher layer signaling configured from the base station. In addition, Figure 11 Starting from the fourth octet in the byte, all D / U fields located in the first bit of the corresponding octet can be regarded as R fields, and all R fields can be configured as 0 bits.

[0319] Next, additional single and multiple TCI status indication and activation methods based on the unified TCI scheme are described. The UE receives a PDSCH schedule including a MAC-CE from the base station, and starting from three slots after sending the HARQ-ACK for the corresponding PDSCH to the base station, the UE can interpret each code point of the TCI status field in DCI format 1_1 or 1_2 based on the information in the MAC-CE received from the base station. In other words, the UE can activate each entry of the MAC-CE received from the base station to each code point of the TCI status field in DCI format 1_1 or 1_2.

[0320] If the UE has been configured with two different CORESETPoolIndexes via higher layer signaling and has been configured with DLorJointTCIState or UL-TCIState as higher layer signaling, the base station and the UE can expect to be in Figure 11The R field 1130 in the first octet of the MAC-CE structure indicating unified TCI state activation is interpreted as a field indicating the CORESET pool ID. If the corresponding CORESET pool ID is configured as 0, the UE may consider that the corresponding MAC-CE is applicable to each code point of the TCI state field in the PDCCH transmitted by the CORESET corresponding to CORESETPoolIndex0. If the corresponding CORESET pool ID is configured as 1, the UE may consider that the corresponding MAC-CE is applicable to each code point of the TCI state field in the PDCCH transmitted by the CORESET corresponding to CORESETPoolIndex1.

[0321] Figure 12 Another example of another MAC-CE structure for activation and indication of multiple joint TCI states or separate DL or UL TCI states in a wireless communication system is shown. The meaning of each field in the MAC-CE structure may be as follows.

[0322] -Serving Cell ID 1200: This field may indicate the serving cell to which the corresponding MAC-CE applies. The length of this field may be 5 bits. In the case where the serving cell indicated by this field is included in one or more of the higher layer signaling simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4, the corresponding MAC-CE may be applied to all serving cells included in one or more of the simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, and simultaneousU-TCI-UpdateList4 in which the serving cell indicated by this field is included.

[0323] -DL BWP ID 1205: This field may indicate the DL BWP to which the corresponding MAC-CE is to be applied, and the meaning of each code point in this field may correspond to each code point of the BWP indicator in the DCI. The length of this field may be 2 bits.

[0324] -UL BWP ID 1210: This field may indicate the UL BWP to which the corresponding MAC-CE is to be applied, and the meaning of each code point of this field may correspond to each code point of the BWP indicator in the DCI. The length of this field may be 2 bits.

[0325] -P i 1215: This field may indicate whether each code point of the TCI status field in DCI format 1_1 or 1_2 has multiple TCI states or one TCI state.

[0326] >In the case where the UE is capable of configuring unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig as higher layer signaling as joint or separate, this field may be interpreted as follows regardless of which of the two configuration information is configured.

[0327] >>In P i When the value of is '00', it indicates that the corresponding i-th code point has a single TCI state, and this may indicate that the corresponding code point may include one of a joint TCI state, a separate DCI TCI state, or a separate UL TCI state.

[0328] >>In P i When the value of is '01', it indicates that the corresponding i-th code point has two TCI states, and this may indicate that the corresponding code point may include one of the following: two joint TCI states, one separate DL TCI state and one separate UL TCI state, two separate DL TCI states, or two separate UL TCI states.

[0329] >>In P i When the value of is '10', it indicates that the corresponding i-th code point has 3 TCI states, and this may indicate that the corresponding code point may include one separate DL TCI state and two separate UL TCI states, or two separate DL TCI states and one separate UL TCI state.

[0330] >>In P i When the value of is '11', it indicates that the corresponding i-th code point has 4 TCI states, and this may indicate that the corresponding code point may include two separate DL TCI states and two separate UL TCI states.

[0331] > In the case where the UE is capable of configuring the higher layer signaling unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig as one of joint, separate, and mixed modes, this field can be interpreted as follows, regardless of which possible configuration value is configured. Mixed mode can be represented by a single configuration value, where the single configuration value indicates that a general mixed mode of joint TCI state and separate DL or UL TCI state is possible, and it can be represented by multiple configuration values ​​such as "1 joint + 1DL" and "1 joint + 1UL", and configured to indicate a specific combination of a specific number of joint TCI states and a specific number of separate DL or UL TCI states.

[0332] >>In P i In case the value of is '00', it indicates that the corresponding i-th code point has a single TCI state, and this may indicate that the corresponding code point may include one of a joint TCI state, a separate DCI TCI state, or a separate UL TCI state.

[0333] >>In P i When the value of is "01", it indicates that the corresponding i-th code point has two TCI states, and this may indicate that the corresponding code point may include one of the following: two joint TCI states, one joint TCI state and a separate DL TCI state, one joint TCI state and a separate UL TCI state, one separate DL TCI state and a separate UL TCI state, two separate DL TCI states, or two separate UL TCI states. In the case that the UE has received higher layer signaling unifiedTCI-StateType-r17 configured with a value indicating that a general mixed mode of joint TCI state and separate DL or UL TCI state is possible, in MIMOparam-r17 of ServingCellConfig, both the above-described one joint TCI state and one separate DL TCI state and one joint TCI state and one separate UL TCI state are possible. In the case where the UE has a higher layer signaling unifiedTCI-StateType-r17 configured with "1joint+1DL" or "1joint+1UL" in the MIMOparam-r17 of ServingCellConfig, only the configuration value of unifiedTCI-StateType-r17 corresponding to one of the following described above is possible: 1 joint TCI state and one separate DL TCI state and 1 joint TCI state and one separate UL TCI state.

[0334] >>In P iWhen the value of is '10', it indicates that the corresponding i-th code point has 3 TCI states, and this may indicate that the corresponding code point may include one separate DL TCI state and two separate UL TCI states, or two separate DL TCI states and one separate UL TCI state.

[0335] >>In P i When the value of is '11', it indicates that the corresponding i-th code point has 4 TCI states, and this may indicate that the corresponding code point may include two separate DL TCI states and two separate UL TCI states.

[0336] >This field can be 2 bits.

[0337] -D / U 1220: This field may indicate whether the TCI State ID field in the same octet is a joint TCI state, a separate DL TCI state, or a separate UL TCI state. If this field has a value of 1, the TCI State ID field in the same octet may be a joint TCI state or a separate DL TCI state, and if this field has a value of 0, the TCI State ID field in the same octet may be a separate UL TCI state.

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

[0339] -R: Indicates a reserved bit and can be configured as 0.

[0340] Figure 13 Another example of a MAC-CE structure for activation and indication of multiple joint TCI states or separate DL or UL TCI states in a wireless communication system is shown. The meaning of each field in the MAC-CE structure may be as follows.

[0341] -Serving Cell ID 1300: This field may indicate the serving cell to which the corresponding MAC-CE applies. The length of this field may be 5 bits. In the case where the serving cell indicated by this field is included in one or more of the higher layer signaling simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4, the corresponding MAC-CE may be applied to all serving cells included in one or more of the simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, and simultaneousU-TCI-UpdateList4 in which the serving cell indicated by this field is included.

[0342] -DL BWP ID 1305: This field may indicate the DL BWP to which the corresponding MAC-CE is to be applied, and the meaning of each code point in this field may correspond to each code point of the BWP indicator in the DCI. The length of this field may be 2 bits.

[0343] -UL BWP ID 1310: This field may indicate the UL BWP to which the corresponding MAC-CE is to be applied, and the meaning of each code point of this field may correspond to each code point of the BWP indicator in the DCI. The length of this field may be 2 bits.

[0344] -P i,1 1315、P i,2 1320: These two fields may indicate whether each code point of the TCI status field in DCI format 1_1 or 1_2 has multiple TCI states or one TCI state.

[0345] > In the case where the UE is capable of configuring the higher layer signaling unifiedTCI-StateType-r17 in MIMOparam-r17 in ServingCellConfig as one of joint mode and separate mode, or one of joint mode, separate mode and hybrid mode, and if the higher layer signaling unifiedTCI-StateType-r17 is configured as joint, the inclusion of Figure 13 P in 1,2 、P 2,2 , ... and P 8,2 The fourth octet of the field and may only be interpreted as follows i,1The hybrid mode may be represented by a single configuration value indicating that a general hybrid mode of joint TCI states and separate DL or UL TCI states is possible, or it may be represented by multiple configuration values ​​such as "1joint+1DL" and "1joint+1UL" and configured to indicate a specific combination of a specific number of joint TCI states and a specific number of separate DL or UL TCI states.

[0346] >>In P i,1 When the value of is "0", it indicates that the corresponding i-th code point has 1 TCI state, and this may indicate that the corresponding code point includes 1 joint TCI state.

[0347] >>In P i,1 When the value of is "1", it indicates that the corresponding i-th code point has two TCI states, and this may indicate that the corresponding code point includes two joint TCI states.

[0348] > In the case that the UE is capable of configuring the higher layer signaling unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig as one of joint and separate modes, or one of joint, separate and mixed modes, and if the higher layer signaling unifiedTCI-StateType-r17 is configured with "single", the UE may set the P value of the third octet to i,1 and the fourth octet P i,2 Treated as a single 2-bit field, it is interpreted as follows. The hybrid mode can be represented by a single configuration value indicating that a general hybrid mode of joint TCI states and separate DL or UL TCI states is possible, and can be represented by multiple configuration values ​​such as "1joint+1DL" and "1joint+1UL" and configured to indicate a specific combination of a specific number of joint TCI states and a specific number of separate DL or UL TCI states.

[0349] >In P i,1 and P i,2 When the values ​​of are "0" and "0" respectively, it indicates that the corresponding i-th code point has a single TCI state, and this may indicate that the corresponding code point may include a separate DL TCI state or a separate UL TCI state.

[0350] >>In P i,1 and P i,2When the values ​​of are "0" and "1" respectively, it indicates that the corresponding i-th code point has two TCI states, and this may indicate that the corresponding code point may include one separate DL TCI state and one separate UL TCI state, two separate DL TCI states, or two separate UL TCI states.

[0351] >>In P i,1 and P i,2 When the values ​​of are "1" and "0" respectively, it indicates that the corresponding i-th code point has three TCI states, and this may indicate that the corresponding code point may include one separate DL TCI state and two separate UL TCI states, or two separate DL TCI states and one separate UL TCI state.

[0352] >>In P i,1 and P i,2 When the values ​​of are "1" and "1" respectively, it indicates that the corresponding i-th code point has four TCI states, and this may indicate that the corresponding code point may include two separate DL TCI states and two separate UL TCI states.

[0353] > In the case where the UE is capable of configuring the higher layer signaling unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig as one of joint, separate and hybrid modes, and if the higher layer signaling unifiedTCI-StateType-r17 is configured with hybrid mode, the UE may interpret the P in the third octet as follows i,1 , and the fourth octet may not be sent. The mixed mode may be represented by a single configuration value, where the single configuration value indicates that a general mixed mode of joint TCI state and separate DL or UL TCI state is possible.

[0354] >>In P i,1 When the value of is "0", it may indicate that the corresponding i-th code point includes a joint TCI state and a separate DL TCI state.

[0355] >>In P i,1 When the value of is "1", it may indicate that the corresponding i-th code point includes a joint TCI state and a separate UL TCI state.

[0356] > In the case where the UE is capable of configuring the higher layer signaling unifiedTCI-StateType-r17 in MIMOparam-r17 of ServingCellConfig as one of joint, separate and hybrid modes, and if the higher layer signaling unifiedTCI-StateType-r17 is configured with hybrid mode, the UE may interpret the P in the third octet as follows i,1 and the fourth octet P i,2 The mixed mode may be represented by a single configuration value, where the single configuration value indicates that a general mixed mode of joint TCI state and separate DL or UL TCI state is possible.

[0357] >In P i,1 When the value of is "0", it can indicate that the corresponding i-th code point contains only one joint TCI state. In other words, since the hybrid mode is not used, P can be ignored. i,2 The value of .

[0358] >>In P i,1 If the value of is "1", it may indicate that the corresponding i-th code point includes a joint TCI state and additionally includes one of a separate UL TCI state and a separate DL TCI state. In other words, the hybrid mode may be used for the corresponding code point, and if P i,2 If the value of P is "0", a separate UL TCI state can be used in addition, and if P i,2 If the value of is "1", a separate UL TCI state can be used in addition.

[0359] -D / U 1325: This field may indicate whether the TCI State ID field in the same octet is a joint TCI state, a separate DL TCI state, or a separate UL TCI state. If this field has a value of 1, the TCI State ID field in the same octet may be a joint TCI state or a separate DL TCI state, and if this field has a value of 0, the TCI State ID field in the same octet may be a separate UL TCI state.

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

[0361] -R: Indicates a reserved bit and can be configured as 0.

[0362] UnifiedTCI-StateType-r17 in MIMOparam-r17 in ServingCellConfig, which is the higher layer signaling described above, may be defined as a new parameter, such as UnifiedTCI-StateType-r18 in higher layer signaling MIMOparam-r18 in ServingCellConfig, or an existing parameter may be reused.

[0363] In this specification, the technology of transmitting and receiving resources may be understood as transmitting and receiving a reference signal corresponding to the resources.

[0364] <First Embodiment: Beam Reporting Method for Simultaneous Transmission Using Multiple Panels>

[0365] Hereinafter, a method in which a UE performs beam reporting to a base station to simultaneously transmit uplink channels using multiple panels according to an embodiment of the present disclosure is described in detail.

[0366] NR Release 17 has newly introduced and enhanced transmission / reception technology, making it possible to use a single unified TCI framework to support beams that were managed separately for uplink and downlink in previous releases. Based on the unified TCI described above, not only can the receive beam used to receive downlink signals be indicated by TCI, but the transmit beam used to transmit uplink signals can also be indicated by TCI. Specifically, the UE can determine the transmit beam or receive beam based on the transmit filter or receive filter used to transmit or receive the reference signal indicated by the TCI status.

[0367] In order for a UE to simultaneously transmit uplink signals using multiple panels, each panel may require an uplink transmit filter. If the UE selects two panels from among the multiple panels and transmits uplink signals using each transmit beam, two transmit beams should be determined. Expanding on this, if N panels are selected from the multiple panels and each transmits an uplink signal using a transmit beam, N transmit beams should be determined. To support simultaneous uplink transmission using multiple panels, the method for reporting and determining N transmit beams can be applied commonly to systems supporting simultaneous multi-panel transmission based on single DCI (sDCI) and systems supporting simultaneous multi-panel transmission based on multi-DCI (mDCI), and the transmit beams determined in the same manner can be applied to simultaneous uplink transmission. Alternatively, while the method for reporting and determining N transmit beams can be applied commonly to both sDCI-based and mDCI-based systems, separate transmit beam application methods suitable for each system may be considered. Alternatively, a method of reporting and determining N transmission beams suitable for each sDCI-based system and a method of reporting and determining N transmission beams suitable for each mDCI-based system may be applied separately, and the determined transmission beams may be applied separately.

[0368] The UE may perform beam reporting to the base station to determine a transmit beam. To perform beam reporting, the UE may use a beam reporting method supported up to NR Release 17. Alternatively, the UE may use an enhanced method of the beam reporting method supported up to NR Release 17, or a new beam reporting method different from the beam reporting method supported up to Release 17 may be introduced. For example, to support simultaneous uplink transmission using multiple panels, the UE may perform beam reporting by reporting the enhanced group-based beam reporting introduced in NR Release 17. Specifically describing the enhanced group-based beam reporting, the CSI information reported by the UE to the base station may include the following information (here, the group-based beam reporting method supported by NR Release 17 may be assumed to be the same as the case where N=2 in the N transmit beams described above. In other words, the transmit beam reporting and determination method supporting simultaneous transmission using multiple panels based on NR Release 17, which will be described later, assumes the case of N=2, however, this is merely an example, and the case may be applied by extending N to an integer greater than 2):

[0369] - a resource set indicator,

[0370] - The first and second CSI-RS resource indicators (CRIs) or SSB resource indicators (SSBRIs) for each reported resource group (or, for ease of explanation, "reported resource group" may also be defined as a "beam group". A maximum of four groups may be defined, and the number of groups configured for the corresponding UE is determined based on a higher-layer parameter (e.g., "nrofReportedGroups") configured by the base station)

[0371] - RSRP or differential RSRP for the reported CRI or SSBRI. In this case, 7 bits of RSRP are reported only for the first resource of the first resource group, and 4 bits of differential RSRP may be reported for each of the other resource groups and resources in the resource groups.

[0372] -CORESETPoolIndex (This information may be implicitly omitted, and if omitted, the first beam information of each resource group may be associated with the case where CORESETPoolIndex is configured as "0" or CORESETPoolIndex is not configured, and the second beam information of each resource group may also be associated with the case where CORESETPoolIndex is "1". There may be mapping information between CORESETPoolIndex, and beam information other than the described example may be included)

[0373] -Associated SRS resource sets (this information may be implicitly omitted or not reported. If not reported, a certain association between each resource group and each SRS resource set may be predefined. For example, the first beam information in a resource group may be associated with a first SRS resource set (e.g., an SRS resource set with a smaller ID value among multiple SRS resource sets used as a "codebook" or a "nonCodebook"), and the second beam information in a resource group may be associated with a second SRS resource set (e.g., an SRS resource set with a larger ID value among multiple SRS resource sets used as a "codebook" or a "nonCodebook").

[0374] Here, one piece of information about the first reporting resource (or first reporting beam) and one piece of information about the second reporting resource (or second reporting beam) in a reported resource group (or beam group) are selected from multiple (e.g., two in NR Release 17) resource sets for group-based beam reporting introduced in NR Release 17, and each selected resource (or beam) can be reported. In other words, to indicate the first beam of a predetermined beam group, the UE can select one of the CSI-RS resources in the first resource set or one of the SSB resources in the first resource set. In other words, to indicate the second beam of a predetermined beam group, the UE can select one of the CSI-RS resources in the second resource set or one of the SSB resources in the second resource set. In this case, the UE should be able to simultaneously transmit / receive uplink / downlink channels using multiple panels based on the receive beams used to receive the two selected CSI-RS resources or SSB resources in each beam group.

[0375] Alternatively, similar to the support groupBasedBeamReporting introduced before NR Release 17, CRI or SSBRI can be selected from two different CSI-RS resources or two different SSB resources that can be simultaneously transmitted and received by the UE through one or more spatial domain receive filters. In the beam reporting method based on releases before NR Release 17, unlike the group-based beam reporting based on NR Release 17, two separate resource sets may not be configured, and the resources selected by the UE can be any two different CSI-RS or SSB resources among the multiple resources that the UE can simultaneously transmit and receive using multiple panels.

[0376] As described above, the CSI information reported by the UE to the base station may follow the CSI reporting method supported by NR Release 17, and the UE may also report additional CSI information for simultaneous multi-panel transmission to the base station. Specifically, the UE may additionally report the following information:

[0377] - The UE may report a CapabilityIndex for indicating the capability value of the reported CRI or SSBRI (or any indicator that can be used to indicate the name of the maximum number of SRS ports that the UE can support for the reported CRI or SSBRI, such as the UE Capability Set Index) using 2 bits for each resource group and resource of the resource group. Alternatively, depending on the maximum number of SRS ports that can be supported, the number of bits used for CapabilityIndex reporting may be greater than 2 bits. As another example of CapabilityIndex reporting, instead of reporting CapabilityIndex for each beam group and the resources within the group, the UE may also report CapabilityIndex only for each beam group. In this case, it is understood that the maximum number of SRS ports according to the same CapabilityIndex can be supported for multiple resources in the reported beam group.

[0378] In other words, the UE may additionally report the maximum number of SRS ports that can be supported for each beam group and resource in the beam group, thereby supporting the base station to use this information to configure two TCI states for simultaneous support using multiple panels. For example, the base station may expect to receive two resources included in the same beam group through different panels. If the beam group and the CSI resource set based thereon are configured as described above, the base station may activate two TCI states by using the reported beam group pair. Alternatively, as in groupBasedBeamReporting before NR Release 17, the base station may activate two TCI states by using a beam pair within a beam group reported from two different CSI-RS resources or two different SSB resources, wherein the UE is capable of simultaneously receiving the two different CSI-RS resources or two different SSB resources through one or more spatial domain receive filters as described above.

[0379] In other words, for the MAC CE for activating / deactivating the enhanced unified TCI state in NR Release 17, only one TCI state corresponding to a single code point could be indicated in the past, but this can be extended so that up to two TCI states corresponding to a single code point can be indicated. At this time, the two TCI states for supporting simultaneous transmission using multiple panels to a single code point can be determined by referring to the beam group pair reported by the UE. In the above description, although the case of indicating two TCI states by a single code point has been described for ease of explanation, when the UE uses N with a number greater than 2, UL,panels When the panels send signals simultaneously, N UL,panelsInstead of indicating two TCI states using one code point, a single TCI state can be indicated by one code point. As another example, the base station can configure the same CSI resources for each CSI resource set included in the same group via higher layer configuration. Furthermore, the UE can receive the same CSI resources using different panels. This can be used as a method to allow a single TRP and UE to transmit and receive signals simultaneously using multiple panels.

[0380] As another method, when the UE reports a beam to the base station, panel information about the reported beam can be configured as additional CSI information and reported. For example, when the maximum number of panels that the UE can support is defined as N panel When , UE can log2N panel A bit is added to each reported CRI or SSBRI to inform the base station about the corresponding panel. This can be defined as a "panel index" or can be configured as another form of CSI report information that can implicitly indicate rather than explicitly indicate that it is information about the panel.

[0381] As a specific example, if the number of resources in the CSI resource set associated with the CSI report is 8, and a CSI-RS resource with a CRI of 0, 1, 2, or 3 is received via the first panel of two panels that the UE can operate, the UE can report the CRI and RSRP (or SINR or any channel measurement information as applicable) based on it, along with one additional bit configured as "0". In other words, the UE can report to the base station via the first panel of the two panels that it has received the CSI-RS resource. Similarly, if a CSI-RS resource with a CRI of 4, 5, 6, or 7 is received via the second panel of the two panels that the UE can operate, the UE can report the CRI and RSRP (or SINR or any channel measurement information as applicable) based on it, along with one additional bit configured as "1".

[0382] In this way, when the UE adds additional information to the CSI report, the base station can configure a beam combination that can be transmitted simultaneously using multiple panels based on the reported beam information and the panel information thereof, thereby sending a MAC CE that configures multiple TCI states through a single code point to the UE. The UE can receive the MAC CE from the base station, activate the TCI state, and finally apply the TCI state indicated by the single code point specified by DCI format 1_1 or DCI format 1_2 to transmit the uplink signal starting from the BAT time. Even in the case where the panel information is added, it is possible to consider an operation in which the base station configures the same CSI resources for each CSI resource set included in the same group via higher layer configuration and the UE uses different panels to receive the same CSI resources. Similarly, even in the case in which the same CSI resources are configured for different resource sets within the group, the UE can also combine CRI and RSRP (or SINR or any channel measurement information may be applicable) based on the panel information (for example, including log2N as described above). panel bits) are reported to the base station.

[0383] As described above, in the first embodiment, the UE may report beam information to the base station, and the base station may configure higher layer parameters based on the beam information to support simultaneous transmission using multiple panels, and send a MAC CE to the UE to activate the TCI state. Here, the MAC CE sent by the base station to the UE may be the same as Figure 11 The example of a MAC CE for indicating multiple TCI states based on a unified TCI method (such as the TCI state indication method based on the unified TCI method described above) is the same as shown in FIG. Alternatively, the MAC CE may be as follows: Figure 12 or Figure 13 The diagram is configured to indicate multiple TCI states through a single code point, so that multiple TCI states for supporting simultaneous transmission of multiple panels can be activated through a single code point.

[0384] Such as MAC CE ( Figure 11 、 Figure 12 or Figure 13 ), the multiple TCI states activated for a single codepoint may be multiple TCI states that allow simultaneous transmission of multiple panels, or multiple TCI states that do not support simultaneous transmission of multiple panels. The former and the latter can be identified and configured by the base station through a group-based beam report sent by the UE to the base station, and the UE and the base station can implicitly identify whether a combination of TCI states allows simultaneous transmission of multiple panels or whether a combination of TCI states does not allow simultaneous transmission of multiple panels through the reported (received) group-based beam report.

[0385] Alternatively, an indicator can be added using unused fields in the reserved field (R field) of the MAC CE to indicate whether simultaneous multi-panel transmission is performed for each codepoint. Alternatively, if the reserved field cannot guarantee the total number of codepoints, a new indicator field can be added to the MAC CE using a new octet (8 bits) to indicate whether simultaneous multi-panel transmission is performed. For example, when there are a total of 8 codepoints, the additional bit for indicating simultaneous multi-panel transmission can be configured to a total of 8 bits, and the MAC CE can be configured using the reserved field or by adding a new octet. In this case, when the first bit (MSB) is set to 1 and multiple (e.g., two) TCI states are indicated for the first codepoint, the TCI state can be activated to perform simultaneous uplink transmission using multiple panels based on the multiple TCI states. Alternatively, when the first bit (MSB) is set to 0 and multiple (e.g., two) TCI states are indicated for the first codepoint, it can indicate that simultaneous uplink transmission using multiple panels based on the multiple TCI states is not possible. In this case, when simultaneous transmission using multiple panels is not performed, multiple TCI states indicated by corresponding code points can support TDM-based multi-TRP transmission.

[0386] As described above, a single code point can be used to activate / configure / indicate multiple TCI states, and a method of indicating a single code point indicating multiple TCI states through a field in a single DCI is suitable for a method of simultaneous transmission of multiple panels based on sDCI. For a method of simultaneous transmission of multiple panels based on mDCI, in which a UE performs uplink transmission to a TRP that can correspond to each CORESETPoolIndex through multiple DCIs, a plurality of (e.g., N=2) transmit beam pairs can be determined as one beam group through the same or similar process as described above, and the UE can report the determined beam group to the base station. The base station and the UE may define an explicit rule in the 3GPP standard such that the first transmit beam information within the beam group is associated with CORESETPoolIndex = 0 (here, when the groupBasedBeamReporting method is considered, the first transmit beam information may imply the first reported beam information in any beam group of the CSI information included in the UCI, and the beam information includes CRI or SSBRI), and the second reported beam information among the CSI information included in the UCI is associated with CORESETPoolIndex = 1 (here, when the groupBasedBeamReporting method is considered, the second reported beam information may imply the second reported beam information in the beam group including the first transmit beam information of the CSI information included in the UCI, and the beam information includes CRI or SSBRI). In addition, an explicit mapping rule between the transmit beam information and the CORESETPoolIndex may be defined without limitation to this example.

[0387] Alternatively, the base station and the UE may define the association between the reported beam group and the CORESETPoolIndex in an implicit manner. In this case, the relationship between the first beam information and the second beam information in the reported beam group and the CORESETPoolIndex with different indices follows the explicit rules described above, such that the first beam information in the beam group can be associated with CORESETPoolIndex=0, and the second beam information in the beam group can be associated with CORESETPoolIndex=1. In the case of following the implicit method, such association may not be specified in the 3GPP specification, but the base station may consider the implicit relationship to indicate beam information (e.g., CRI or SSBRI), where the beam information is associated with the corresponding CORESETPoolIndex within the beam group through DCI associated with the corresponding CORESETPoolIndex (i.e., PDCCH received via the CORESET, where CORESETPoolIndex is 0 (or may not be configured) or 1), as a reference signal (referenceSigal) of the TCI state (DLorJoint-TCIstate-r17 or UL-TCIstate) of the scheduled uplink channel transmission. Here, the DCI indicating the TCI state may correspond to the DL DCI format (e.g., DCI format 1_1 or 1_2) for indicating downlink scheduling or TCI state in the same manner as the conventional unified TCI framework, and the indicated TCI state may be applied to the uplink transmission after the beam application time (BAT). In addition, the DCI indicating the TCI state may correspond to the UL DCI format (e.g., DCI format 0_1 ​​or 0_2) used to schedule the uplink PUSCH, and the indicated TCI state may be applied after the BAT or immediately when the PUSCH scheduled by the corresponding DCI is transmitted. In addition, an implicit mapping rule between transmit beam information and CORESETPoolIndex may be defined without being limited to these examples.

[0388] <Second Embodiment: Method for Configuring SRS for Simultaneous Transmission of Codebook-Based PUSCH Using Multiple Panels>

[0389] In this embodiment, a method for configuring an SRS resource set and SRS resources to support simultaneous codebook-based PUSCH transmission using multiple panels is described in detail.

[0390] In the event that simultaneous uplink transmission using multiple panels is possible depending on the UE capabilities, the UE may configure the corresponding UE capabilities as supportable and report it to the base station. For example, the UE capability reporting parameter reported by the UE to the base station may be "simulTx-PUCCH-PUSCH", and the value of the corresponding parameter may be configured as "supported" or "enable" to report that the UE can use multiple panels to simultaneously transmit PUCCH or PUSCH. In this case, the UE may use multiple panels to simultaneously transmit multiple PUCCHs or PUCCH repetitions or multiple PUSCHs or PUSCH repetitions. On the other hand, the operation of the UE using multiple panels to simultaneously transmit PUCCH and PUSCH may not be supported. The UE capability reporting parameter "simulTx-PUCCH-PUSCH" reported by the UE to the base station is merely an example, and the UE may report to the base station that it is capable of simultaneous uplink transmission using multiple panels by using parameters with different names that may perform similar or identical UE capability reporting.

[0391] Thereafter, the base station may configure higher-layer parameters to support the UE, and the configured higher-layer parameters may include higher-layer parameters for simultaneous uplink transmission using multiple panels. The base station may use the higher-layer parameters for simultaneous uplink transmission using multiple panels to configure SRS resource sets for PUSCH transmission in the UE. In this case, if codebook-based PUSCH transmission using multiple panels is supported, the base station may configure SRS resource sets with "usage" set to "codebook" in the UE. One or more (e.g., up to two) SRS resource sets with "usage" set to "codebook" may be configured for simultaneous codebook-based PUSCH transmission using multiple panels. Configuring multiple SRS resource sets with "usage" set to "codebook" may indicate that the UE may transmit uplink signals to as many Transmission Relays (TRPs) as the number of configured SRS resource sets, based on the relationship between TCI states. For example, if the base station configures two SRS resource sets with "usage" set to "codebook" in the UE, the UE may transmit uplink signals to up to two TRPs. For ease of explanation, the present disclosure mainly describes a method for sending uplink signals to two TRPs at the same time, but the present disclosure can be expanded based on the described method so that the UE can send uplink signals to more than two TRPs at the same time.

[0392] When the base station configures "usage" as multiple SRS resource sets of the codebook, one or more SRS resources can be configured in each SRS resource set. When the base station configures the higher-layer parameters for the SRS resource set for the UE, the base station can additionally configure "followUnifiedTCTstate-r17". When "followUnifiedTCTstate-r17" is configured for the SRS resource set, the UE sends the SRS resources in the SRS resource set by considering the reference signal whose qcl-Type is configured as "typeD" in the QCL-Info of the indicated "TCI-State" (if the higher-layer parameter "unifiedTCI-StateType" is configured as "joint") or the reference signal configured in "TCI-UL-State" (if the higher-layer parameter "unifiedTCI-StateType" is configured as "separate"). At this time, if the reference signal whose qcl-Type is configured as "typeD" is a downlink reference signal, the UE can transmit the SRS by considering the spatial filter used when receiving the corresponding reference signal, and if the reference signal configured as "typeD" is an uplink reference signal, the UE can transmit the SRS by considering the spatial filter used when transmitting the corresponding reference signal. At this time, the reference RS indicated by DLorJoint-TCIstate-r17 can be the CSI-RS within the NZP-CSI-RS-ResourceSet configured with the higher-layer parameter repetition or the CSI-RS within the NZP-CSI-RS-ResourceSet configured with the higher-layer parameter "trs-Info set". Alternatively, the reference RS indicated by "UL-TCIstate" can be a CSI-RS within an NZP-CSI-RS-ResourceSet configured with a higher-layer parameter repetition, a CSI-RS within an NZP-CSI-RS-ResourceSet configured with a higher-layer parameter "trs-Info set", an SRS resource whose "usage" is configured as "beamManagemet", or an SSB associated with a PCI that is the same as or different from the PCI of the serving cell.

[0393] In the present disclosure, for ease of explanation, it is assumed that the high-level parameter "followUnifiedTCTstate-r17" is configured for multiple SRS resource sets, and the SRS resources are sent according to the spatial relationship determined by referring to the TCI state indicated by DCI (e.g., TCI-State or DLorJoint-TCIstate-r17 or UL-TCIstate).

[0394] As described in the first embodiment, when a UE receives a MAC CE from a base station activating multiple TCI states to support simultaneous uplink transmission using multiple panels, if a single codepoint including multiple (e.g., N) TCI states is indicated via DCI or the like, a first SRS resource set among the multiple SRS resource sets is associated with the first TCI state among the indicated N TCI states. In other words, the UE may transmit all SRS resources in the first SRS resource set based on a spatial relationship determined with reference to the first TCI state among the indicated N TCI states. Here, the first SRS resource set may indicate the SRS resource set with the smallest SRS-ResourceSetId value among the multiple SRS resource sets whose "usage" is configured as "codebook" (for ease of description, the SRS resource set described in the second and third embodiments refers to the SRS resource set whose "usage" is configured as "codebook"). Similarly, a second SRS resource set among the multiple SRS resource sets may be associated with the second TCI state among the indicated N TCI states. In other words, the UE may transmit all SRS resources in the second SRS resource set based on a spatial relationship determined with reference to the second TCI state among the N TCI states indicated. Similarly, for more than two SRS resource sets and TCI states, the UE may transmit all SRS resources included in the nth SRS resource set based on a spatial relationship determined with reference to the nth TCI state. The association between TCI states and SRS resource sets described above is merely an example, and the present disclosure is not limited to the examples not described above.

[0395] At this time, if multiple SRS resources are included in one SRS resource set, each of the SRS resources can be associated with a panel according to the following different methods. When the UE has reported through the UE capability report that it can perform simultaneous uplink transmission using multiple panels, and the base station considers this and configures higher-layer parameters for simultaneous uplink transmission using multiple panels, the association between the SRS resources and the above-described panels can be established.

[0396] -[Association 1] Each SRS resource included in an SRS resource set can be associated with a panel supported by the UE. For example, the first SRS resource in the first SRS resource set can be associated with the first panel among the panels supported by the UE (if the information about the panel is implicitly configured and indicated, the order among the multiple panels can be determined by the UE implementation. Alternatively, if the information about the panel is explicitly configured and indicated, it can be determined as the lowest panel indicator. The second, third, and other panels thereafter can be defined similarly. The present disclosure is not limited to this example). The second SRS resource in the first SRS resource set can be associated with the second panel among the panels supported by the UE. The configuration method described above is merely an example; a number of SRS resources other than two can be configured in an SRS resource set, and each SRS resource can be associated with a predetermined panel supported by the UE. However, this association should be configured so that the base station and the UE can have the same understanding, and a method of defining the association between SRS resources and panels supported by the UE in order as in the example described above can be considered.

[0397] In addition, the group-based beam reporting information described above can be used so that the base station and the UE have the same understanding of the association between SRS resources and panels. Alternatively, information about the panels supported by the UE can be added and configured in the SRS-Rource, where the SRS-Rource is explicitly configured by high-level parameters. For example, a high-level parameter such as "panel_Index" can be added to the high-level parameter SRS-Rource, and the high-level parameter can use a range from 0 to N. panel-1 One of the values ​​to indicate the panel supported by the UE.

[0398] Figure 14 An example is shown of a case where two SRS resource sets in a wireless communication system according to an embodiment of the present disclosure each include two SRS resources and a UE can support simultaneous uplink transmission using two panels.

[0399] according to Figure 14 , two TCI states 1402 and 1403 for simultaneous transmission using multiple panels are indicated by a code point indicated by the TCI field of DCI 1401 received by the UE from the base station. In this case, the first TCI state 1402 can be used to determine the spatial relationship between SRS resources 1411 and 1412 within the first SRS resource set 1410 for transmission. The second TCI state 1403 can be used to determine the spatial relationship between SRS resources 1421 and 1422 within the second SRS resource set 1420 for transmission.

[0400] In addition, the first panel 1431 of the UE may be implicitly or explicitly associated with the first SRS resource 1411 within the first SRS resource set 1410. If the first TCI state includes an RS transmitted from a first TRP among a plurality of TRPs as a reference RS, the UE may understand that the first SRS resource 1411 within the first SRS resource set 1410 is configured to transmit an SRS to the first TRP by using the first panel 1431 of the UE. In addition, the first panel 1431 may also be implicitly or explicitly associated with the first SRS resource 1421 within the second SRS resource set 1420. If the second TCI state includes an RS transmitted from a second TRP among a plurality of TRPs as a reference RS, the UE may understand that the first SRS resource 1421 in the second SRS resource set 1420 is configured to transmit an SRS to the second TRP by using the first panel 1431 of the UE.

[0401] The second panel 1432 of the UE may be implicitly or explicitly associated with the second SRS resource 1412 within the first SRS resource set 1410. If the first TCI state includes an RS transmitted from a first TRP among a plurality of TRPs as a reference RS, the UE may understand that the second SRS resource 1412 within the first SRS resource set 1410 is configured to transmit an SRS to the first TRP by using the second panel 1432 of the UE. In addition, the second panel 1432 may also be implicitly or explicitly associated with the second SRS resource 1422 within the second SRS resource set 1420. If the second TCI state includes an RS transmitted from a second TRP among a plurality of TRPs as a reference RS, the UE may understand that the second SRS resource 1422 in the second SRS resource set 1420 is configured to transmit an SRS to the second TRP by using the second panel 1432 of the UE. Figure 14 A case where the number of SRS ports of the SRS resources included in each SRS resource set is 2 is shown.

[0402] - [Association 2] The SRS resources included in an SRS resource set can be associated with one panel or multiple panels. For example, the first SRS resource in the first SRS resource set can be associated with the first panel (or second panel) among the panels supported by the UE, and the second SRS resource in the first SRS resource set can be associated with the first and second panels among the panels supported by the UE. Similarly, the first SRS resource in the second SRS resource set can be associated with the second panel (or first panel) among the panels supported by the UE, and the second SRS resource in the second SRS resource set can be associated with the first and second panels among the panels supported by the UE. The configuration method described is merely an example, and multiple SRS resources other than two can be configured in a single SRS resource set, and each SRS resource can be associated with any panel supported by the UE. In addition, unlike the described example, the first SRS resource in an SRS resource set can be associated with multiple panels. However, [Association 2] should also be configured similarly to [Association 1] so that the base station and UE can have the same understanding, and the example described above can be considered as one method for defining associations between SRS resources and panels supported by the UE.

[0403] In addition, the group-based beam reporting information described above can be used so that the base station and the UE have the same understanding of the association between SRS resources and panels. Alternatively, information about the panels supported by the UE can be added and configured in the SRS-Rource, where the SRS-Rource is explicitly configured by a high-level parameter. For example, a high-level parameter such as "panel_Index" can be added to the high-level parameter SRS-Rource, and the high-level parameter can indicate the panel index with a range from 0 to N. panel-1 Alternatively, the “panel_Index” may be in the form of a bitmap, wherein each bit of the bitmap corresponds to a panel, and each bit may be configured as 1 for a panel associated with the corresponding SRS resource and as 0 for a panel not associated therewith. In this case, the “panel_Index” may be represented by N panel Alternatively, the "panel_Index" can be configured by bits to account for all possible combinations of supported panels.

[0404] Figure 15 An example is shown of a case where two SRS resource sets in a wireless communication system according to an embodiment of the present disclosure each include two SRS resources and a UE can support simultaneous uplink transmission using two panels.

[0405] according to Figure 15, two TCI states 1502 and 1503 for simultaneous transmission using multiple panels are indicated by a code point indicated by the TCI field of DCI 1501 received by the UE from the base station. In this case, the first TCI state 1502 can be used to determine the spatial relationship between SRS resources 1511 and 1512 within the first SRS resource set 1510 for transmission. The second TCI state 1503 can be used to determine the spatial relationship between SRS resources 1521 and 1522 within the second SRS resource set 1520 for transmission.

[0406] In addition, the UE's first panel 1531 may be implicitly or explicitly associated with the first SRS resource 1511 in the first SRS resource set 1510. If the first TCI state includes an RS transmitted from a first TRP among multiple TRPs as a reference RS, the UE may understand that the first SRS resource 1511 in the first SRS resource set 1510 is configured to transmit an SRS to the first TRP using the UE's first panel 1531. In this case, for example, the number of SRS ports configured in the first SRS resource 1511 in the first SRS resource set 1510 may be two. The UE's second panel 1532 may be implicitly or explicitly associated with the first SRS resource 1521 in the second SRS resource set 1520. If the second TCI state includes an RS transmitted from a second TRP among multiple TRPs as a reference RS, the UE may understand that the first SRS resource 1521 in the second SRS resource set 1520 is configured to transmit an SRS to the second TRP using the UE's second panel 1532. In this case, for example, the number of SRS ports configured in the first SRS resource 1521 in the second SRS resource set 1520 may be two.

[0407] The second SRS resource 1512 configured in the first SRS resource set 1510 may be implicitly or explicitly associated with the first panel 1531 and the second panel 1532, both of which are supported by the UE. If the first TCI state includes an RS transmitted from a first TRP among a plurality of TRPs as a reference RS, it can be understood that the second SRS resource 1512 in the first SRS resource set 1510 is configured to transmit an SRS to the first TRP using the first panel 1531 and the second panel 1532 supported by the UE.

[0408] At this point, the number of SRS ports configured in the second SRS resource 1512 in the first SRS resource set 1510 may be four, a number that can be supported using two panels. Here, the first two SRS ports may be associated with the first panel 1531, and the remaining two SRS ports may be associated with the second panel 1532. The relationship between these SRS ports and multiple panels can be implicitly associated in sequence, or can be explicitly indicated by a new high-level parameter. For example, as many Panel_Index values ​​as SRS ports of the SRS resource can be configured in a sequence.

[0409] The second SRS resources 1522 configured in the second SRS resource set 1520 can be implicitly or explicitly associated with the first panel 1531 and the second panel 1532, both of which are supported by the UE. If the second TCI state includes an RS transmitted from a second TRP among multiple TRPs as a reference RS, it can be understood that the second SRS resources 1522 in the second SRS resource set 1520 are configured to transmit an SRS to the second TRP using the first panel 1531 and the second panel 1532, both of which are supported by the UE. In this case, the number of SRS ports configured in the second SRS resources 1522 in the second SRS resource set 1520 can be equal to four, which is the number that can be supported using two panels. As with the second SRS resource 1512 within the first SRS resource set 1510 described above, an implicit or explicit association can be established between an SRS port and a panel supported by the UE.

[0410] The above description is specifically described assuming that the SRS resources are sent based on the indicated TCT state. However, even if "followUnifiedTCTstate-r17" is not configured, simultaneous transmission using multiple panels can be supported by applying the method described above based on the spatial relationship information configured for the SRS resources in each SRS resource set. In this case, the first TCI state described above can be replaced by spatialRelationInfo configured by high-level parameters for the SRS resources in the first SRS resource set, and the second TCI state can be replaced by spatialRelationInfo configured by high-level parameters for the SRS resources in the second SRS resource set.

[0411] According to the method described above, multiple TCI states are indicated by sDCI, and each indicated TCI state can be associated with each SRS resource set and the SRS (or multiple) resources included in each SRS resource set. In other words, if each TCI state is associated with an SRS resource set, the UE can transmit the SRS resource by referring to the reference signal (referenceSignal) indicated by the TCI state. In addition, the UE can transmit the PUSCH by configuring the PUSCH transmission port to be the same as the SRS port of the SRS resource indicated by the SRI (in the case of supporting non-codebook-based PUSCH), or can transmit the PUSCH by applying the precoder indicated by the TPMI to the PUSCH transmission port configured to be the same as the SRS port of the SRS resource indicated by the SRI (in the case of supporting codebook-based PUSCH).

[0412] With mDCI, multiple DCIs can be used to schedule each PUSCH, and each scheduled PUSCH can fully, partially, or non-overlap in the time / frequency domain. Each DCI is associated with a different CORESETPoolIndex, and each scheduled PUSCH is also associated with a different CORESETPoolIndex. In this case, two different SRS resource sets can be configured by higher-layer parameters to transmit the PUSCH scheduled by each DCI. Based on explicit or implicit rules between the base station and the UE in the 3GPP technical specifications, the first SRS resource set (which can indicate the usage as "codebook" or "non-codebook" and is configured with a low (small) SRS-ResourceSetId) can be associated with the CORESET within the CORESET with CORESETPoolIndex = 0 (or no CORESETPoolIndex is configured) and the PUSCH scheduled by the DCI. The second SRS resource set (which may indicate an SRS resource set with a high (large) SRS-ResourceSetId among two different SRS resource sets whose usage is "codebook" or "nonCodebook") may be associated with a CORESET with CORESETPoolIndex=1 within a CORESET and a PUSCH scheduled by DCI.

[0413] The DCI associated with each CORESETPoolIndex may indicate the TCI state based on the beam information within the beam group that may be associated with each CORESETPoolIndex described in the first embodiment to schedule the corresponding PUSCH transmission. For example, the TCI state (DLorJoint-TCIstate-r17 or UL-TCIstate) within the DCI received by a CORESET with CORESETPoolIndex=0 (or CORESETPoolIndex is not configured) may be indicated by the first beam information within the beam group. As described in the first embodiment, the base station may indicate the TCI state through DCI corresponding to a DL DCI format (e.g., DCI format 1_1 or 1_2), and the UE may also apply the beam information indicated by the TCI state indicated by the DCI to uplink transmission after BAT. Alternatively, as described in the first embodiment, the base station may indicate the TCI state through a DCI corresponding to a UL DCI format (e.g., DCI format 0_1 ​​or 0_2), and the UE may apply the beam information indicated by the indicated TCI state to uplink transmission after BAT, or may immediately apply the beam information corresponding to the indicated TCI state when sending an uplink PUSCH scheduled by the corresponding DCI.

[0414] <Third Embodiment: Configuration Method and Association between SRS Ports and PUSCH Ports When Simultaneous Multi-Panel Transmission Based on a Single DCI>

[0415] In the third embodiment, for a UE supporting simultaneous transmission of multiple panels based on single DCI (sDCI), a configuration method and association between a PUSCH port and an SRS port are described in detail.

[0416] In the second embodiment, two methods (association 1 and association 2) for configuring an SRS resource set to support simultaneous multi-panel transmission are specifically described. If the UE is capable of simultaneously transmitting a PUSCH to two TRPs by using two panels based on sDCI, the base station can indicate the SRS resources used for PUSCH transmission through SRI by using an SRS resource set associated with each TRP (each TRP can indirectly indicate to the UE through multiple TCI states determined through group-based beam reporting) (or higher-layer parameters can be configured to follow the beam information configured in the SRS resource set or the beam information configured in the SRS resources within the SRS resource set, rather than following a unified TCI state. However, for ease of explanation, it is assumed that the UE transmits an SRS resource set according to multiple TCI states indicated by a unified TCI state, and the present disclosure can be applied to the two cases described above).

[0417] At this time, similar to the two SRI fields used to support NR Release 17 sDCI TDM mTRP PUSCH repetition transmission, the base station can send one DCI including two SRI fields to the UE. In the two SRI fields, unlike NR Release 17, when non-codebook PUSCH is supported, bits can be configured so that the second SRI field can also indicate the number of layers (rank) of the PUSCH sent to the second TRP. In addition, the number of SRS resources that can be configured in each SRS resource set can be the same or different. In the case where the number of SRS resources included in the first SRS resource set and the second SRS resource set is different, since both SRI fields should be able to indicate the rank, unlike NR Release 17, the number of bits of the first SRI field and the number of bits of the second SRI field can be different, and depending on the configuration, the number of bits of the second SRI field can be greater than the number of bits of the first SRI field.

[0418] Similarly, when codebook PUSCH is supported, the second TPMI field should be able to indicate the number of ranks of the second PUSCH to be transmitted, and the number of bits of each TPMI field can be selected differently depending on the number of SRS ports of the SRS resource indicated by each SRI field. Alternatively, if a constraint is added to ensure that the number of SRS ports of the SRS resource in each SRS resource set indicated by each SRI field is the same, then unlike NR Release 17, the number of bits of the two TPMI fields can be selected to be the same, because the second TPMI field should also be able to indicate the number of ranks.

[0419] If the base station schedules the UE to send two PUSCHs by simultaneously using each panel toward each TRP through mTRP multi-panel simultaneous transmission, the base station can include information for mTRP multi-panel simultaneous transmission in the DCI used for PUSCH scheduling. For example, the base station can use the SRS resource set indicator sent to the UE to indicate multi-panel simultaneous transmission. In NR Release 17, the SRS resource set indicator already indicated single-TRP TDM PUSCH repetition transmission or multi-TRP TDM PUSCH repetition transmission, but in NR Release 18, the SRS resource set indicator can be used to indicate single TRP transmission or multi-TRP transmission. In this case, single TRP transmission can be single-TRP panel selection-based transmission through a single panel or multi-panel simultaneous transmission for a single TRP through multiple panels. After the base station indicates single TRP transmission through the SRS resource set indicator, the UE can select one SRS resource associated with one panel (for transmission based on single TRP panel selection) or two SRS resources associated with two panels (for single TRP multi-panel simultaneous transmission) from the SRS resources with associations between SRS resources and panels as in Association 1 of the second embodiment through the SRI field (since two SRI fields are included in the DCI when two SRS resource sets are established, the UE can use only the first SRI field or the second SRI field and ignore the remaining fields, or can use all bits of the first SRI field and the second SRI field to configure a single SRI, thereby enabling the use of more code points). In other words, the base station can schedule transmission based on single TRP panel selection or single TRP multi-panel simultaneous transmission for the UE through a combination of the SRS resource set indicator indication for single TRP transmission and the SRI field.

[0420] Here, the transmission based on the single TRP panel selection can be the same as the single TRP transmission of the version before NR version 18, and the association between the SRS port and the PUSCH port can be determined in the same manner accordingly. In other words, in the case of codebook PUSCH, the PUSCH port is configured to be the same as the SRS port of the indicated SRS resource, and the same number of PUSCH ports as the number of SRS ports determined according to the high-level parameter configuration for the SRS resource can be configured. For example, if the number of SRS ports of the SRS resource selected by SRI for scheduling PUSCH transmission is four, the UE can use 4 PUSCH ports for PUSCH transmission, and each PUSCH port can be configured to be the same as the SRS port. In addition, the first SRS port can be mapped to PUSCH port 0, the second SRS port can be mapped to PUSCH port 1, the third SRS port can be mapped to PUSCH port 2, and the fourth SRS port can be mapped to PUSCH port 3. For non-codebook PUSCH, each SRS resource is configured by only one SRS port, and the SRS port of the i+1th SRS resource in the SRS resource set can be mapped to PUSCH port i. For example, if four SRS resources are configured in the SRS resource set, the SRS port of the first SRS resource can be mapped to PUSCH port 0, the SRS port of the second SRS resource can be mapped to PUSCH port 1, the SRS port of the third SRS resource can be mapped to PUSCH port 2, and the SRS port of the fourth SRS resource can be mapped to PUSCH port 3.

[0421] In the case where single TRP multi-panel simultaneous transmission is supported, if two SRS resources are indicated by SRI (which can be one field or two SRI fields), it may be necessary to determine the mapping relationship between the SRS ports and PUSCH ports within the two SRS resources. The following two mapping methods can be considered:

[0422] Mapping method 1: a method of mapping each SRS resource selected by SRI to PUSCH transmission for each panel and individually indexing PUSCH ports.

[0423] Mapping method 1 is a method of indexing PUSCH ports based on each PUSCH transmitted through each panel. Describes the codebook PUSCH. When the first SRS resource is used to transmit the PUSCH, SRS ports 0 to 3 (when the number of SRS ports of the first SRS resource is four) that are equal to the SRS ports of the first SRS resource are mapped to PUSCH ports 0 to 3, which are configured with the same ports as the first SRS resource and transmitted. Furthermore, when the second SRS resource is used to transmit the PUSCH, SRS ports 0 to 3 (when the number of SRS ports of the second SRS resource is four) that are equal to the SRS ports of the second SRS resource are mapped to PUSCH ports 0 to 3, which are configured with the same ports as the second SRS resource and transmitted. In the case where two SRS resources are indicated by a single SRI field, the first SRS resource may correspond to the SRS resource indicated first by the SRI field, and the second SRS resource may correspond to the SRS resource indicated second by the SRI field. In the case where both SRI fields indicate one SRS resource, the first SRS resource may be the SRS resource indicated by the first SRI field, and the second SRS resource may be the SRS resource indicated by the second SRI field. This specific example describes a case where the SRS resource is configured with four ports. However, even if the SRS resource is configured with multiple ports other than four, the SRS ports and PUSCH ports can be mapped in a similar manner.

[0424] Describes non-codebook PUSCH. For a PUSCH transmitted through a first panel, among SRS resources associated with the first panel (the association between an SRS resource and a panel may be defined by an implicit or explicit higher-layer parameter), a port of a first SRS resource may be mapped to PUSCH port 0 transmitted through the first panel, a port of a second SRS resource may be mapped to PUSCH port 1 transmitted through the first panel, a port of a third SRS resource may be mapped to PUSCH port 2 transmitted through the first panel, and a port of a fourth SRS resource may be mapped to PUSCH port 3 transmitted through the first panel. Additionally, for the PUSCH transmitted via the second panel, among the SRS resources associated with the second panel (the association between SRS resources and panels may be defined by implicit or explicit higher-layer parameters), the port of the first SRS resource may be mapped to PUSCH port 0 transmitted via the second panel, the port of the second SRS resource may be mapped to PUSCH port 1 transmitted via the second panel, the port of the third SRS resource may be mapped to PUSCH port 2 transmitted via the second panel, and the port of the fourth SRS resource may be mapped to PUSCH port 3 transmitted via the second panel. This is merely an example, and the number of SRS resource ports, or the number of SRS resources associated with each panel, may be a value other than four in the example. In this case, the mapping between SRS ports and PUSCH ports may be performed in the same manner as described above. In the case where the SRS resources to be transmitted via both panels are indicated by a single SRI field, in the above example, a total of eight SRS resources, including the first to fourth SRS resources capable of being transmitted via the first panel and the first to fourth SRS resources capable of being transmitted via the second panel, may be indicated by the single SRI field. In this case, the first four SRS resources among the eight indicated SRS resources may correspond to resources transmitted via the first panel, and the remaining four SRS resources may correspond to resources transmitted via the second panel. In the case where the SRS resources to be transmitted via each panel are indicated by two SRI fields, the four SRS resources indicated by the first SRI field may be the first to fourth SRS resources that can be transmitted via the first panel. The four SRS resources indicated by the second SRI field may be the first to fourth SRS resources that can be transmitted via the second panel.

[0425] Mapping method 2: a method of mapping both of two SRS resources selected by SRI to PUSCH transmission and indexing PUSCH ports by considering all SRS ports of the two SRS resources.

[0426] Mapping method 2 is a method of indexing PUSCH ports by considering all ports transmitted through two panels together. Describing the codebook PUSCH. When a PUSCH is transmitted based on a first SRS resource, SRS ports 0 to 3 (when the number of SRS ports of the first SRS resource is four) that are equal to the SRS ports of the first SRS resource are mapped to PUSCH ports 0 to 3, which are configured with the same ports as the first SRS resource and transmitted. And when a PUSCH is transmitted based on a second SRS resource, SRS ports 0 to 3 (when the number of SRS ports of the second SRS resource is four) that are equal to the SRS ports of the second SRS resource are mapped to PUSCH ports 4 to 7, which are configured with the same ports as the second SRS resource and transmitted. In the case where two SRS resources are indicated by a single SRI field, the first SRS resource may be the SRS resource indicated first by the SRI field, and the second SRS resource may be the SRS resource indicated second by the SRI field. In the case where both SRI fields indicate one SRS resource, the first SRS resource may be the SRS resource indicated by the first SRI field, and the second SRS resource may be the SRS resource indicated by the second SRI field. In the specific example, the case where the SRS resource is configured by four ports has been described. However, even if the SRS resource is configured by multiple ports other than four, the SRS ports and PUSCH ports can be mapped in a similar manner.

[0427] Describes non-codebook PUSCH. For a PUSCH transmitted through a first panel, in an SRS resource associated with the first panel (the association between an SRS resource and a panel may be defined by an implicit or explicit higher-layer parameter), a port of the first SRS resource may be mapped to PUSCH port 0 transmitted through the first panel, a port of the second SRS resource may be mapped to PUSCH port 1 transmitted through the first panel, a port of the third SRS resource may be mapped to PUSCH port 2 transmitted through the first panel, and a port of the fourth SRS resource may be mapped to PUSCH port 3 transmitted through the first panel. Additionally, for the PUSCH transmitted via the second panel, among the SRS resources associated with the second panel (the association between SRS resources and panels may be defined by implicit or explicit higher-layer parameters), the port of the first SRS resource may be mapped to PUSCH port 4 transmitted via the second panel, the port of the second SRS resource may be mapped to PUSCH port 5 transmitted via the second panel, the port of the third SRS resource may be mapped to PUSCH port 6 transmitted via the second panel, and the port of the fourth SRS resource may be mapped to PUSCH port 7 transmitted via the second panel. This is merely an example, and the number of SRS resource ports, or the number of SRS resources associated with each panel, may be a value other than four in the example. In this case, the mapping between SRS ports and PUSCH ports may be performed in the same manner as described above. In the case where the SRS resources to be transmitted via both panels are indicated by a single SRI field, in the above example, a total of eight SRS resources, including the first to fourth SRS resources capable of being transmitted via the first panel and the first to fourth SRS resources capable of being transmitted via the second panel, may be indicated by the single SRI field. In this case, the first four SRS resources among the eight indicated SRS resources may correspond to resources transmitted via the first panel, and the remaining four SRS resources may correspond to resources transmitted via the second panel. In the case where the SRS resources to be transmitted via each panel are indicated by two SRI fields, the four SRS resources indicated by the first SRI field may be the first to fourth SRS resources that can be transmitted via the first panel. The four SRS resources indicated by the second SRI field may be the first to fourth SRS resources that can be transmitted via the second panel.

[0428] Mapping methods 1 and 2 are specifically described assuming single-DCI-based single-TRP panel selection or single-DCI-based single-TRP multi-panel simultaneous transmission. However, in order to support single-DCI-based multi-TRP multi-panel simultaneous transmission for multiple TRPs using the same mapping method, mapping method 1 or mapping method 2 can be used to perform port indexing between the PUSCH transmitted to each TRP through each panel and the SRS resource set associated with the corresponding PUSCH transmission and the SRS resource indicated by each SRI field.

[0429] For example, when multi-TRP multi-panel simultaneous codebook PUSCH transmission based on a single DCI is supported according to mapping method 1, in order for the UE to send PUSCH to TRP1 by using the first panel, the first SRS port of the SRS resource indicated by the SRI within the first SRS resource configured for sending PUSCH to TRP1 can be mapped to PUSCH port 0 sent to TRP1, the second SRS port can be mapped to PUSCH port 1 sent to TRP1, the third SRS port can be mapped to PUSCH port 2 sent to TRP1, and the fourth SRS port can be mapped to PUSCH port 3 sent to TRP1. In addition, in order to send PUSCH to TRP2 by using the second panel, the first SRS port of the SRS resource indicated by the SRI within the second SRS resource configured for sending PUSCH to TRP2 can be mapped to PUSCH port 0 sent to TRP2, the second SRS port can be mapped to PUSCH port 1 sent to TRP2, the third SRS port can be mapped to PUSCH port 2 sent to TRP2, and the fourth SRS port can be mapped to PUSCH port 3 sent to TRP2.

[0430] When multi-TRP multi-panel simultaneous codebook PUSCH transmission based on a single DCI is supported according to mapping method 2, the relationship between the PUSCH port of the SRS resource indicated by the SRI in the first SRS resource set and the SRS port is the same as that in mapping method 1, and the first SRS port of the SRS resource indicated by the SRI in the second SRS resource configured to send PUSCH to TRP2 using the second panel can be mapped to PUSCH port 4 sent to TRP2, the second SRS port can be mapped to PUSCH port 5 sent to TRP2, the third SRS port can be mapped to PUSCH port 6 sent to TRP2, and the fourth SRS port can be mapped to PUSCH port 7 sent to TRP2.

[0431] When simultaneous non-codebook PUSCH transmission of multiple TRPs and multiple panels based on a single DCI is supported according to mapping method 1, for the PUSCH sent to TRP1, among the SRS resources associated with the first panel in the first SRS resource set (the association between the SRS resources and the panel can be defined by implicit or explicit higher-level parameters), the port of the first SRS resource can be mapped to PUSCH port 0 sent through the first panel, the port of the second SRS resource can be mapped to PUSCH port 1 sent through the first panel, the port of the third SRS resource can be mapped to PUSCH port 2 sent through the first panel, and the port of the fourth SRS resource can be mapped to PUSCH port 3 sent through the first panel. In addition, for the PUSCH sent through the second panel, among the SRS resources associated with the second panel in the second SRS resource set (the association between the SRS resources and the panel can be defined by implicit or explicit high-level parameters), the port of the first SRS resource can be mapped to the PUSCH port 0 sent through the second panel, the port of the second SRS resource can be mapped to the PUSCH port 1 sent through the second panel, the port of the third SRS resource can be mapped to the PUSCH port 2 sent through the second panel, and the port of the fourth SRS resource can be mapped to the PUSCH port 3 sent through the second panel.

[0432] Similarly, when multi-TRP multi-panel simultaneous non-codebook PUSCH transmission based on a single DCI is supported according to mapping method 2, for the PUSCH sent to TRP1 using the first panel, the PUSCH ports are indexed in the same manner as in mapping method 1, and for the PUSCH sent to TRP2 using the second panel, among the SRS resources associated with the second panel in the second SRS resource set (the association between the SRS resources and the panels can be defined by implicit or explicit higher-layer parameters), the port of the first SRS resource can be mapped to PUSCH port 4 sent through the second panel, the port of the second SRS resource can be mapped to PUSCH port 5 sent through the second panel, the port of the third SRS resource can be mapped to PUSCH port 6 sent through the second panel, and the port of the fourth SRS resource can be mapped to PUSCH port 7 sent through the second panel.

[0433] The above example assumes that the first SRS resource set is associated with the first panel, and the second SRS resource set is associated with the second panel. However, in addition to the association described in the above example, as described in the second embodiment (Association 1 or Association 2), even if the SRS resource set includes SRS resources associated with the first panel or the second panel, the SRS port through which the SRS resource is transmitted can be mapped to the PUSCH port by considering the panel to which the SRS resource is associated.

[0434] In other words, when multi-TRP multi-panel simultaneous non-codebook PUSCH transmission based on a single DCI is supported according to mapping method 1, the ports of the PUSCH transmitted to TRP1 can be mapped as follows. Among some of the SRS resources associated with the first panel in the first SRS resource set, the ports of the first SRS resources can be mapped to PUSCH port 0 transmitted through the first panel, and the ports of the second SRS resources can be mapped to PUSCH port 1 transmitted through the first panel. Among some of the resources associated with the first panel in the second SRS resource set, the ports of the first SRS resources can be mapped to PUSCH port 2 transmitted through the first panel, and the ports of the second SRS resources can be mapped to PUSCH port 3 transmitted through the first panel. In addition, the ports of the PUSCH transmitted to TRP2 can be mapped as follows. Among some of the SRS resources associated with the second panel in the first SRS resource set, a port of the first SRS resource may be mapped to PUSCH port 0 transmitted through the second panel, a port of the second SRS resource may be mapped to PUSCH port 1 transmitted through the second panel, a port of the first SRS resource associated with the second panel in the second SRS resource set may be mapped to PUSCH port 2 transmitted through the second panel, and a port of the second SRS resource may be mapped to PUSCH port 3 transmitted through the second panel.

[0435] Similarly, when multi-TRP multi-panel simultaneous non-codebook PUSCH transmission based on a single DCI is supported according to mapping method 2, in the case of a PUSCH sent to TRP1 using the first panel, the PUSCH ports are indexed in the same manner as in mapping method 1. In addition, in the case of a PUSCH sent to TRP2 using the second panel, among the SRS resources associated with the second panel in the first SRS resource set, a port of the first SRS resource may be mapped to PUSCH port 4 sent through the second panel, and a port of the second SRS resource may be mapped to PUSCH port 5 sent through the second panel; and among the SRS resources associated with the second panel in the second SRS resource set, a port of the first SRS resource may be mapped to PUSCH port 6 sent through the second panel, and a port of the second SRS resource may be mapped to PUSCH port 7 sent through the second panel.

[0436] <Fourth Embodiment: Method for Scheduling and Determining Multi-Panel-Based Simultaneous Transmission Technology>

[0437] In a fourth embodiment, a method is described in detail, in which a base station performs scheduling according to one of several methods for simultaneously transmitting uplink channels based on multiple panels, and a UE determines and performs one of several simultaneous transmission techniques based on multiple panels based on scheduling information.

[0438] NR Release 18 can not only support the uplink channel repetition transmission method based on mTRP TDM introduced in NR Release 17, but also support a method for simultaneous transmission of uplink channels based on multiple panels.

[0439] Figure 16 An example of an uplink channel repetitive transmission method based on mTRP TDM, and an SDM and single frequency network (SFN) scheme corresponding to an uplink channel simultaneous transmission method based on multiple panels are shown.

[0440] according to Figure 16 , the uplink channel repetition transmission methods 1600 and 1610 based on mTRP TDM can be distinguished into a "sequential mapping" method 1600 and a "cyclic mapping" method 1610 depending on a method of mapping uplink beams (or TRPs of received signals) for multiple repeated transmissions. The uplink channel repetition transmission method based on mTRP TDM transmitted based on the "sequential mapping" method is such that, in the first and second transmission opportunities 1601 or 1602, the PUSCH is transmitted to the first TRP (or the first UL beam indicated by the first spatial relationship information or the first TCI state (the DL and UL joint TCI state or UL TCI state described above)), and in the third and fourth transmission opportunities 1603 or 1604, the PUSCH is transmitted to the second TRP (or the second UL beam indicated by the second spatial relationship information or the second TCI state (the DL and UL joint TCI state or UL TCI state described above)), etc.). Even for more than four repeated transmissions, the transmission opportunities and TRPs to which the uplink is directed can be mapped in the same pattern (ie, the TRP of the received signal changes every two transmission opportunities).

[0441] The uplink channel repetition transmission method based on mTRP TDM transmitted based on the "cyclic mapping" method is to transmit the PUSCH to the first TRP (or the first UL beam indicated by the first spatial relationship information or the first TCI state (the DL and UL joint TCI state or UL TCI state described above)) in the first and third transmission opportunities 1611 or 1613, and to transmit the PUSCH to the second TRP (or the second UL beam indicated by the second spatial relationship information or the second TCI state (the DL and UL joint TCI state or UL TCI state described above)) in the second and fourth transmission opportunities 1612 or 1614. Even for more than four repeated transmissions, the transmission opportunity and TRP to which the uplink is directed can be mapped in the same pattern (that is, the TRP of the received signal changes in each transmission opportunity).

[0442] The SDM scheme 1620 is a method that treats the total number of layers as one TB to configure a scheduled PUSCH resource and encodes information bits based on this configuration. Subsequently, according to the SDM scheme, the UE can divide the spatial domain resources into two halves and simultaneously transmit the PUSCH at the same time using each panel. In other words, the UE transmits different layers of the PUSCH separately via each panel. For example, the UE may transmit the first part (including the portion of the low-indexed layers) via the first panel (indicated by reference numeral 1621) and the second part (excluding the first part) via the second panel (indicated by reference numeral 1622). This is merely an example, and each part may be mapped to a panel and transmitted in an order different from the example (for example, the first part may be transmitted via the second panel, and the second part may be transmitted via the first panel). The DMRS 1625 of the PUSCH transmitted via each panel is configured with different DMRS ports, and the different DMRS ports may be included in different CDM groups. Alternatively, the different DMRS ports may be included in the same CDM group. In this case, when a single TB is split in half and transmitted through each panel, and then transmitted to a different TRP using each panel, part of the TB will be received by a single TRP. The base station can then collect them into a single signal and perform joint decoding or individual decoding on them, depending on the base station implementation, so that the UE can receive the transmitted signal.

[0443] SFN scheme 1630 is a method in which a UE configures and transmits the same TB and the same DMRS on the same frequency and time resources. The PUSCH transmitted by each panel may include the same data and the same DMRS. In other words, the UE may transmit the first part via the first panel (indicated by reference numeral 1631) and the second part via the second panel (indicated by reference numeral 1632). This is merely an example, and each part may be mapped to a panel and transmitted in a different order than this example (for example, the first part may be transmitted via the second panel, and the second part may be transmitted via the first panel). In this case, when the same TB is transmitted by each panel and sent to a different TRP using each panel, the same TB is received by a single TRP. The base station can then combine them into a single signal and perform joint or separate decoding on it, depending on the base station implementation, allowing the UE to receive the transmitted signal. In SFN scheme 1630, the DMRS transmitted by each panel may be configured using the same DMRS port (indicated by reference numeral 1635). However, different precoding matrices may be applied to the DMRS of each panel with the same DMRS port index. In other words, although two panels transmit the same TB through the same DMRS port, precoding for DMRS and data for each panel may be applied individually.

[0444] In addition to the above Figure 16 In addition to the sending method described in , repeated transmission based on the SDM scheme can also be supported to send the same TB. Figure 16 The uplink channel transmission using mTRP and multiple panels is mainly described, but dynamic switching can be considered in addition, and accordingly, the transmission method based on sTRP and panel switching using a single panel can also be considered.

[0445] <Fifth Embodiment: Method for Configuring Phase Tracking Reference Signals for Uplink Data Transmission Simultaneously Sent Through Multiple Panels Based on SFN>

[0446] In the fifth embodiment, a method for transmitting a PTRS for PUSCH transmission using an SFN-based multi-panel simultaneous transmission method is specifically described.

[0447] As described above in the fourth embodiment, in the SFN-based multi-panel simultaneous transmission method, the UE transmits the same TB via two panels, and the same DMRS port index is applied to each panel transmission. However, since the channel between each panel and the TRP is different, precoding can be applied separately to the PUSCH and DMRS transmitted via each panel. In other words, when the base station schedules SFN-based multi-panel simultaneous transmission for the UE, the base station can indicate the same TB, the same antenna port field (indicating the DMRS port index), the same PUSCH resources, etc. for the PUSCH transmitted via all panels via the scheduling DCI. Furthermore, the scheduling DCI can indicate a separate SRI and TPMI for the PUSCH applied to each panel. In this case, even if separate SRI and TPMI are applied to the PUSCH transmission for each panel, the same data should be transmitted using the same TB size, and therefore the precoding matrix (or the same number of SRS ports) should be indicated for transmitting the same number of layers.

[0448] Because DMRS is sparsely placed in the time domain, PTRS is used to measure the phase error in the time domain and correct the phase error to perform channel estimation with higher reliability. In order to accurately measure the phase error, the phase error in the time domain should be measured for all DMRS ports, but in this case, the overhead caused by RS increases significantly. Therefore, in the NR system, one PTRS port or a maximum of two PTRS ports are designed to be operated when performing uplink data transmission. Unlike the downlink PTRS, the base station indicates to the UE via scheduling DCI which of the DMRS ports is associated with the PTRS port among the DMRS ports of the scheduled PUSCH.

[0449] The downlink PTRS for receiving PDSCH based on mTRP can operate up to two ports (in this case, the RRC parameter maxNrofPorts used to support this should be configured as "n2"), and each PTRS port is associated with the lowest-indexed DMRS port among the DMRS sent to the PDSCH of each TCI state. This is because the base station can identify information about layers with good channel conditions and layers with relatively poor channel conditions based on the channel state information reported by the UE, and can then sort these layers based on this information to send downlink signals. In other words, the base station can determine the lowest-indexed DMRS port as the appropriate layer to be associated with the PTRS based on the CSI reported by the UE.

[0450] However, since the UE does not receive a report of separate status information about the uplink channel from the base station, there is a problem that the UE cannot determine the uplink layer that is suitable for associating with the PTRS port. Taking this into account, in the NR system, a DCI field is added to the DCI format 0_1 ​​or 0_2 for scheduling PUSCH, allowing the base station to determine and indicate the DMRS associated with the PTRS, and the DCI is sent to the UE. As described above, in the NR system, DMRS port candidates that can be associated with PTRS port 0 or PTRS port 1 are predefined, and the base station can indicate the DMRS port that is associated with the PTRS and transmitted when sending the scheduled PUSCH by using 2 bits of the PTRS-DMRS association field in the DCI for scheduling PUSCH.

[0451] When a UE transmits PUSCH, the number of PTRS ports indicating the PTRS ports through which data is actually transmitted can be determined by the configured maximum number of uplink PTRS ports and the SRI (SRS Resource Indicator) or TPMI (Transmit Precoding Matrix Indicator) indicated by the scheduling DCI (or RRC parameters configured for configured grant-based PUSCH transmission). As described above, in the case of codebook-based PUSCH, the DMRS ports corresponding to a layer can be associated with a specific PTRS port depending on the PUSCH port used to transmit that layer. Specifically, the DMRS ports for layers transmitted via PUSCH port 0 (the first PUSCH port) and / or PUSCH port 2 (the third PUSCH port) can be associated with PTRS port 0. The DMRS ports for layers transmitted via PUSCH port 1 (the second PUSCH port) and / or PUSCH port 3 (the fourth PUSCH port) can be associated with PTRS port 1. In the case of non-codebook-based PUSCH, the PTRS ports that can be associated with SRS resources for a transport layer are configured by RRC parameters. For example, SRS resource 0 and SRS resource 1 may be associated with PTRS port 0, and SRS resource 2 and SRS resource 3 may be associated with PTRS port 1. Furthermore, if a scheduled PUSCH is transmitted via the same PUSCH port as SRS resource 0 and SRS resource 2, the first layer of the corresponding PUSCH may be associated with PTRS port 0, and the second layer may be associated with PTRS port 1. All of the examples described specifically correspond to the case where the maximum number of supportable uplink PTRS ports, "maxNrofPorts," configured in the RRC parameter PTRS-UplinkConfig, is configured as "n2." When "maxkNrofPorts" is configured as "n1," one of the four DMRS ports may be associated with PTRS port 0. In this way, if the maximum number of supported uplink PTRS ports is 2, in the case of codebook-based PUSCH, the number of PTRS ports actually transmitted associated with the layer of PUSCH scheduled by TPMI can be determined by the PUSCH antenna port used for the transmitted layer, and in the case of non-codebook-based PUSCH, the number of PTRS actually transmitted associated with the layer of PUSCH scheduled by SRI can be determined by the RRC configuration for the SRS resource configuration indicated by SRI.

[0452] When the UE supports SFN-based multi-panel simultaneous transmission, the number of actual PTRS ports transmitted along with the SFN PUSCH scheduled for each panel may be different because different SRI or / and TPMI may be indicated for the PUSCH transmitted through each panel.

[0453] Figure 17 An example of the number of actual PTRS ports for PUSCH transmitted through each panel during codebook-based SFN PUSCH multi-panel transmission is shown.

[0454] Figure 17 Assume that UE 1700 performs codebook-based SFN PUSCH multi-panel simultaneous transmission 1710 or 1720 with respect to two TRPs 1701 and 1702, scheduled by a single DCI 1705. The precoder and the number of actual PTRS ports used for PUSCH 1710 and 1720 transmitted by each panel are determined by DCI format 0_1 ​​or 0_2 1705 that schedules the corresponding PUSCH (or, in the case of configured grant-based PUSCH, by the precoder indicator configured by RRC (e.g., "precodingAndNumberOfLayers" and "precodingAndNumberOfLayers2" in "rrc-ConfiguredUplinkGrant" in "ConfiguredGrantConfig")). Assume that UE 1700 has two panels, and the two panels can support 4 PUSCH ports.

[0455] The base station may transmit a single DCI 1705 including a first TPMI 1706 and a second TPMI 1707 to the UE within a single DCI 1705 for scheduling simultaneous SFN-based multi-panel transmission, indicating the precoder and layer to be used for PUSCHs 1710 and 1720 to be transmitted via each panel. The UE may apply a precoder 1708 for two-layer transmission using the four PUSCH ports indicated by the first TPMI 1706 to the PUSCH 1710 transmitted via the first panel (associated with the first SRS resource set or the first unified TCI state). At this point, the UE may configure a DMRS 1711 based on the RRC configuration for the DMRS and the number of symbols in the time domain of the scheduled PUSCH 1710, and then transmit the DMRS together with the PUSCH. In the case where the PUSCH 1710 transmitted via the first panel (associated with the first SRS resource set or the first unified TCI state) is transmitted by applying the indicated precoder 1708, it can be seen that both the first layer and the second layer are transmitted via the first PUSCH port or the third PUSCH port. This is understood to mean that both layers can be associated with PTRS port 0, and therefore PTRS port 0 can be transmitted in association with one of the two DMRS ports (indicated by reference numeral 1712).

[0456] Similarly, the UE may apply a precoder 1709 for two-layer transmission using four PUSCH ports indicated by the second TPMI 1707 to a PUSCH 1720 transmitted via the second panel (associated with a second SRS resource set or a second unified TCI state). In this case, the UE may similarly configure a DMRS 1721 based on the RRC configuration for the DMRS and the number of symbols in the time domain of the scheduled PUSCH 1720, and then transmit the DMRS along with the PUSCH. The corresponding DMRS is transmitted using the same resources as the DMRS 1711 transmitted along with the PUSCH 1710 transmitted via the first panel, and even though the DMRS port index is the same, the UE transmits the corresponding DMRS by applying a different precoding matrix. When the PUSCH 1720 transmitted through the second panel (associated with the second SRS resource set or the second unified TCI state) is transmitted by applying the indicated precoder 1709, the first layer is transmitted through the first PUSCH port and the third PUSCH port, and the second layer is transmitted through the second PUSCH port and the fourth PUSCH port. Since the first layer may be associated with PTRS port 0 and the second layer may be associated with PTRS port 1, PTRS port 0 and PTRS port 1 may be associated with DMRS ports and transmitted to the DMRS ports (indicated by reference numerals 1722 and 1723), respectively.

[0457] like Figure 17 As shown in the example in FIG, the number of actual PTRS ports transmitted along with PUSCH 1710 transmitted through the first panel may be different from the number of actual PTRS ports transmitted along with PUSCH 1720 transmitted through the second panel. In other words, an example is shown in which, when codebook-based SFN PUSCH multi-panel simultaneous transmission is supported, the actual number of PTRS ports of the PUSCH simultaneously transmitted through each panel may be different.

[0458] The same situation can also occur when non-codebook based SFN PUSCH multi-panel simultaneous transmission is supported. Figure 18 An example of the number of actual PTRS ports for PUSCH transmitted through each panel during non-codebook based SFN PUSCH multi-panel transmission is shown.

[0459] Figure 18Assume that UE 1800 performs simultaneous non-codebook-based SFN PUSCH multi-panel transmission 1810 or 1820 scheduled by a single DCI 1805 with respect to two TRPs 1801 and 1802. The precoder and the number of actual PTRS ports through which PUSCH 1810 and 1820 are transmitted on each panel are determined by scheduling DCI format 0_1 ​​or 0_2 1805 for the corresponding PUSCH (or, in the case of a configured grant-based PUSCH, utilizing an RRC-configured precoder indicator (e.g., "srs-ResourceIndicator" and "srs-ResourceIndicator2" in "rrc-ConfiguredUplinkGrant" in "ConfiguredGrantConfig"). Assume that UE 1800 has two panels, and both panels can support SRS resource sets based on four SRS resources. The base station may indicate to the UE SRS resources for indicating the precoder and layer of PUSCHs 1810 and 1820 transmitted through each panel by using a first SRI 1806 and a second SRI 1807 in a single DCI 1805 for scheduling SFN-based multi-panel simultaneous transmission.

[0460] The UE uses the first panel (based on the first SRS resource set or the first unified TCI state) to perform two-layer PUSCH transmission by configuring PUSCH ports in the same manner as SRS resource #1 and SRS resource #4 in the first SRS resource set #1 1808 indicated by the first SRI 1806 in DCI 1805 and transmitting each layer through each PUSCH port. In this case, each layer can have a one-to-one mapping relationship with each DMRS port. SRS resource #1 and SRS resource #3 in the first SRS resource set #1 1808 are associated with PTRS port 0, and SRS resource #2 and SRS resource #4 are associated with PTRS port 1. Thus, the first layer of the PUSCH 1810 transmitted through the first panel (associated with the first SRS resource set or the first unified TCI state) is transmitted in association with PTRS port 0 1812 because it is transmitted using the same antenna port configuration as SRS resource #1, and the second layer is transmitted in association with PTRS port 1 1813 because it is transmitted using the same antenna port configuration as SRS resource #4. Therefore, PTRS port 0 and PTRS port 1 can be associated with and transmitted to DMRS ports (indicated by reference numerals 1812 and 1813), respectively.

[0461] The UE performs two-layer PUSCH transmission via the second panel (based on the second SRS resource set or the second unified TCI state) by configuring PUSCH ports in the same manner as SRS resources #1 and SRS resources #2 in the second SRS resource set #2 1809 indicated by the second SRI 1807 in DCI 1805, and transmitting each layer via each PUSCH port. In this case, each layer can have a one-to-one mapping relationship with each DMRS port, similar to the case of transmission via the first panel. SRS resources #1 and SRS resources #2 in the second SRS resource set #2 1809 are associated with PTRS port 0, while SRS resources #3 and SRS resources #4 are associated with PTRS port 1. Therefore, since both layers of PUSCH 1820 (associated with the second SRS resource set or the second unified TCI state) transmitted via the second panel can be associated with PTRS port 0, PTRS port 0 can be transmitted in association with one of the two DMRS ports (indicated by reference numeral 1822).

[0462] As described above, when SFN PUSCH multi-panel simultaneous transmission is supported and up to 2 PTRS ports are supported not only for codebook-based PUSCH but also for non-codebook-based PUSCH, it can be recognized that the actual number of PTRS ports for PUSCH transmitted through each panel may be different. Figure 17 and Figure 18 In addition to the SRI and / or TPMI indication examples specifically described in

[0045] , the actual number of PTRS ports for PUSCH sent by each panel may also be different due to other SRI and / or TPMI.

[0463] If the number of actual PTRS ports transmitted along with the PUSCH transmitted through each panel is different, as in the specific example, the UE may need to perform rate matching separately for each PUSCH transmission. In other words, this is understood to mean that even if the same data is transmitted according to the SFN-based multi-panel simultaneous transmission method, the amount of resources required for actual data transmission may vary depending on the number of actual PTRS ports. In addition, it can be inferred that the amount of resources required for data transmission when the number of actual PTRS ports is 2 is less than the amount of resources required for data transmission when the number of actual PTRS ports is 1. In other words, even if the same data is transmitted, the UE may need to perform rate matching separately considering the different amounts of resources used for data transmission. This may lead to additional complexity because it requires additional operations from the UE.

[0464] On the other hand, SFN PUSCH transmitted with the same rate matching and multiplexing pattern can allow the base station to process uplink data channels using various combining methods. For example, signals transmitted with the same pattern can be combined at various layers, such as symbol-level combining, log-likelihood ratio (LLR)-level combining, and bit-level combining after decoding. However, if the same rate matching cannot be performed, the multiplexing pattern of data and UCI cannot be maintained identically. Therefore, there are cases where combining methods that can be considered when transmitting with the same pattern (such as symbol-level combining) cannot be performed.

[0465] As in Figure 17 and Figure 18 In the example, when the rate matching and the multiplexing mode are different, additional complexity may be required for the UE, or a limit may be imposed on the improved reception gain according to the combination method. In view of this, the present disclosure specifically describes a method for determining a PTRS port during simultaneous SFN PUSCH multi-panel transmission and operations of a base station and a UE based thereon. In the present disclosure, [Method 1] to [Method 6] are specifically described assuming that the number of uplink PTRS ports supportable by the UE is two and the base station has configured RRC parameters for the UE to achieve support for up to two uplink PTRS ports. However, the number of uplink PTRS ports is not limited to two, and the following method can be used even when a larger number of uplink PTRS ports is supported.

[0466] [Method 1] Allocate one PTRS port for each PUSCH transmitted in association with each panel (or each SRS resource set)

[0467] The base station and UE can allocate one PTRS port for the PUSCH transmitted via each panel (or each SRS resource set). As a specific example, the PUSCH associated with panel 1 (or the first SRS resource set) can be transmitted with PTRS port 0, and the PUSCH associated with panel 2 (or the second SRS resource set) can be transmitted with PTRS port 1. Alternatively, one PTRS port can be transmitted with the PUSCH associated with each panel (or each SRS resource set), without the need to individually index the PTRS ports. Of course, if the higher-layer parameters (RRC parameters) for uplink PTRS are not configured, uplink PTRS cannot be transmitted with PUSCH.

[0468] When one PTRS port is transmitted in association with a DMRS port of a PUSCH transmitted through each panel (or each SRS resource set) and the number of DMRS ports of the corresponding PUSCH is two, the PTRS port should be transmitted in association with one of the two DMRS ports. At this time, as described above, the PTRS-DMRS association field in the DCI that schedules the PUSCH is also indicated, and the UE can determine a single DMRS port associated with the PTRS port among the two DMRS ports based on the code point indicated by the corresponding field. For example, the MSB M (e.g., 1) bit of the PTRS-DMRS association field can be used to determine up to two DMRS ports transmitted together with the PUSCH associated with the first panel (associated with the first SRS resource set or associated with the first TCI state). m One DMRS port (e.g., two) of the DMRS ports that is associated with the PTRS port. The LSB M (e.g., 1) bit of the PTRS-DMRS association field may be used to determine up to 2 DMRS ports transmitted with the PUSCH associated with the second panel (associated with the second SRS resource set or associated with the second TCI state). m One of the (e.g., two) DMRS ports that is associated with the PTRS port. Alternatively, if a second SRS resource set (usage is "codebook" or "non-Codebook") is configured, the second PTRS-DMRS association field may be additionally indicated by the DCI along with the existing PTRS-DMRS association field.

[0469] When [Method 1] is used, the number of actual PTRS ports used for PUSCH transmission sent for each panel can be maintained the same, so rate matching may not be performed for each PUSCH. However, the subcarrier offset value within the RB for the PTRS sent for each panel may be different depending on the code point indicated by the PTRS-DMRS association field. When the PTRS ports are multiplexed within the RB, the subcarrier offset within the RB may be determined based on the index value of the DMRS port associated with the PTRS port and the "resourceElementOffset" value configured by the RRC parameter by referring to Table 6.4.1.2.2.1-1 in technical specification TS 38.211 (or Table 28 below). ). The relationship between "resourceElementOffset" and the subcarrier offset within an RB is not limited by the table below.

[0470] [Table 28]

[0471]

[0472] For example, "0" and "1" have been indicated as indices of DMRS ports for two-layer PUSCH transmission, and the PTRS DMRS association field in the DCI that schedules simultaneous transmission of multiple panels of the corresponding SFN PUSCH may be indicated as "01." The PTRS port transmitted together with the PUSCH associated with the first panel (or associated with the first SRS resource set or associated with the first TCI state) is transmitted in association with DMRS port 0 (associated with DMRS port 0, which is the first DMRS port among the two DMRS ports because the MSB1 bit is 0), and the PTRS port transmitted together with the PUSCH associated with the second panel (or associated with the second SRS resource set or associated with the second TCI state) is transmitted in association with DMRS port 1 (associated with DMRS port 1, which is the second DMRS port among the two DMRS ports because the LSB1 bit is 1). In case of configuration type 1 and when resourceElementOffset is configured as "offset00", the PTRS port associated with the first panel (or associated with the first SRS resource set or associated with the first TCI state) is associated with DMRS port 0, so the offset within the RB of the PTRS port is The value of is determined to be 0, and the PTRS port associated with the second panel (or associated with the second SRS resource set or associated with the second TCI state) is associated with DMRS port 1, so the offset within the RB of the PTRS port is The value of is determined to be 2.

[0473] Figure 19 An example is shown in which each PTRS port is transmitted through each panel during SFN PUSCH multi-panel simultaneous transmission. Figure 19 As described above, the PTRS DMRS association field is indicated as '01', and the UE transmits the scheduled two-layer PUSCH 1910 and 1920 by using the SFN-based multi-panel simultaneous transmission method. Since the PTRS 1912 transmitted through the PUSCH 1910 transmitted via the first panel (or the first SRS resource set or the first TCI state) is transmitted in association with the DMRS port 0 1911, the offset within the RB The value of may be determined to be 0. Since the PTRS 1922 transmitted through the PUSCH 1920 transmitted via the second panel (or the second SRS resource set or the second TCI state) is transmitted in association with the DMRS port 1 1921, the value within the RB is offset by It may be determined to be 2. In other words, although the same rate matching is performed, since the PTRS is transmitted in association with different DMRS ports, a pattern in which the PTRS is multiplexed onto the PUSCH may be different.

[0474] On the other hand, if the PTRS DMRS association field is indicated as "00", two PTRS ports associated with two panels (or associated with two SRS resource sets or associated with two TCI states) can be associated with DMRS port 0, and the offset within the RB of the PTRS port in both cases is The value of can be determined to be 0.

[0475] When SFN PUSCH multi-panel simultaneous transmission is supported by [Method 1], for PUSCHs sent through different panels, the base station may allow different offsets within the RB for which the PTRS port is sent. , similar to Figure 19 As shown. In this case, the UE can perform the same rate matching on the SFN PUSCHs transmitted through the two panels and can multiplex the PTRS onto the PUSCH at the same position or multiplex the PTRS onto the PUSCH at different positions according to the value indicated by the PTRSDMRS association field. Alternatively, when SFN PUSCH multi-panel simultaneous transmission is supported by [Method 1], for PUSCHs transmitted through PTRS ports of different panels, the base station can allow the same offset only within the RB for which the PTRS port is transmitted. When the base station only allows the same offset The following scheduling constraints can be considered.

[0476] -[Detailed Method 1] If SFN PUSCH multi-panel simultaneous transmission is scheduled by DCI format 0_1 ​​or DCI format 0_2 (or if type 2 configured granted PUSCH is activated), the UE may not expect the association between PTRS ports and different DMRS ports through the PTRS-DMRS association field in the corresponding DCI. In other words, for PUSCHs sent using different panels, the UE may not expect the PTRS ports to be associated with different DMRS ports used for PUSCH (as indicated by the PTRS-DMRS association field in the DCI). Whether the PUSCH is associated with a panel can be determined based on the SRS resources or TCI status configured using the method described above.

[0477] -[Detailed Method 2] If SFN PUSCH multi-panel simultaneous transmission is scheduled by DCI format 0_1 ​​or DCI format 0_2 (or if type 2 configured granted PUSCH is activated), the UE can expect the PTRS port to be associated with the same DMRS port via the PTRS-DMRS association field in the corresponding DCI. In other words, for PUSCHs sent using different panels, the UE can expect the PTRS port to be associated with the same DMRS port for each PUSCH (as indicated by the PTRS-DMRS association field in the corresponding DCI). Whether a PUSCH is associated with a panel can be determined based on the SRS resources or TCI status configured using the method described above.

[0478] -[Detailed method 3] If SFN PUSCH multi-panel simultaneous transmission is scheduled by DCI format 0_1 ​​or DCI format 0_2 (or if type 2 configured granted PUSCH is activated), the UE may not expect that the "DMRS port (associated with the PTRS port) used for PUSCH sent via the first SRS resource set (or the first indicated TCI state)" and the "another DMRS port (associated with the PTRS port) used for PUSCH sent via the second SRS resource set (or the second indicated TCI state)" indicated by the PTRS-DMRS association field within the DCI are different (here, this indicates the case where the usage of the SRS resource set is configured as "codebook" or "nonCodebook").

[0479] -[Detailed method 4] If SFN PUSCH multi-panel simultaneous transmission is scheduled by DCI format 0_1 ​​or DCI format 0_2 (or if type 2 configured granted PUSCH is activated), the UE may expect that the "DMRS port (PTRS port associated with it) used for PUSCH sent via the first SRS resource set (or the first indicated TCI state)" and the "another DMRS port (PTRS port associated with it) used for PUSCH sent via the second SRS resource set (or the second indicated TCI state)" indicated by the PTRS-DMRS association field within the DCI are the same (here, this indicates the case where the usage of the SRS resource set is configured as "codebook" or "nonCodebook").

[0480] -[Detailed Method 5] If SFN PUSCH multi-panel simultaneous transmission is scheduled by a higher layer parameter (RRC parameter for scheduling granted PUSCH of type 1 configuration), the UE may operate in the same manner as when the value of the PTRS-DMRS association field is '0' or '00'.

[0481] When SFN PUSCH is supported for transmission between PUSCH and PTRS in the same multiplexing mode as in [Detailed Method 1] to [Detailed Method 5], the UE only needs to transmit SFN PUSCH with the same rate matching and the same multiplexing mode, thereby reducing the complexity of the processing required for the UE to transmit SFN PUSCH and enabling the base station to support a wider range of combining methods during reception. However, since the association between PTRS and DMRS ports cannot be specified based on the channel state that cannot be indicated for each panel, performance degradation may occur in terms of phase error estimation and compensation.

[0482] [Method 2] Configure the PTRS ports based on the PUSCH transmitted using the maximum (or minimum) number of actual PTRS ports.

[0483] If SFN PUSCH multi-panel simultaneous transmission is scheduled by DCI format 0_1 ​​or DCI format 0_2 (or if the granted PUSCH of type 2 configuration is activated) or scheduled via higher layer parameters (RRC parameters for scheduling the granted PUSCH of type 1 configuration), the PTRS port transmitted based on the PUSCH transmission using the maximum (or minimum) number of actual PTRS ports among the PUSCHs transmitted via each panel (or SRS resource set or TCI state) can be determined.

[0484] Figure 20 An example of transmitting PUSCH according to the maximum number of actual PTRS ports during simultaneous SFN PUSCH multi-panel transmission is shown. Assume that PUSCH 2010 transmitted via a first panel (or a first SRS resource set or a first TCI state) and PUSCH 2020 transmitted via a second panel (or a second SRS resource set or a second TCI state) are scheduled using DCI format 0_1 ​​or 0_2 2005.

[0485] If the number of actual PTRS ports for PUSCH 2010 transmitted via the first panel (or the first SRS resource set or the first TCI state) is 1 (indicated by reference numeral 2012) and the number of actual PTRS ports for PUSCH 2020 transmitted via the second panel (or the second SRS resource set or the second TCI state) is 2 (indicated by reference numerals 2022 and 2023), the UE may configure the PTRS ports for PUSCH 2010 transmitted via the first panel (or the first SRS resource set or the first TCI state) using the same pattern as the PTRS ports for PUSCH 2020 transmitted via the second panel (or the second SRS resource set or the second TCI state) (indicated by reference numerals 2016 and 2017) according to the maximum number of actual PTRS ports and transmit them (indicated by reference numeral 2015). In this case, PTRS 2016 and 2017 for PUSCH 2015 transmitted via the first panel may have the same configuration as PTRS 2022 and 2023 for PUSCH 2020 transmitted via the second panel, such as an offset within an RB of a PTRS port.

[0486] Alternatively, with Figure 20 Unlike the example of , the UE may configure and transmit the PTRS ports for PUSCH 2020 transmitted via the second panel (or the second SRS resource set or the second TCI state) using the same pattern as the PTRS ports for PUSCH 2010 transmitted via the first panel (or the first SRS resource set or the first TCI state) based on the minimum number of actual PTRS ports. In this case, the PTRS for PUSCH 2020 transmitted via the second panel may have one actual PTRS port, and the configuration of the PTRS port (such as the offset within the RB) may also follow the same configuration as the PTRS 2012 for PUSCH 2010 transmitted via the first panel.

[0487] [Method 3] Two PTRS ports are allocated to each PUSCH transmitted in association with each panel (or each SRS resource set).

[0488] If SFN PUSCH multi-panel simultaneous transmission is scheduled by DCI format 0_1 ​​or DCI format 0_2 (or if type 2 configured granted PUSCH is activated) or via higher layer parameters (RRC parameters for scheduling type 1 configured granted PUSCH), the actual number of PTRS ports used for PUSCH transmitted through each panel may be 2. In the case where the actual number of PTRS ports used for PUSCH transmitted through each panel is always 2, the UE may ignore the PTRS-DMRS association field in the DCI used to schedule SFN PUSCH multi-panel simultaneous transmission. Alternatively, when SFN PUSCH multi-panel simultaneous transmission is scheduled, the base station is required to configure the PTRS-DMRS association field in the corresponding DCI to "00", and the UE may not expect the PTRS-DMRS association field in the corresponding DCI to be configured with a value other than "00".

[0489] When [Method 3] is used, the accuracy of phase error estimation can be improved when performing two-layer SFN PUSCH multi-panel repeated transmission, thereby improving reception performance due to improved channel estimation. However, since more resources are used for PTRS transmission, a loss in resources used for data transmission may occur (i.e., the actual code rate used for data transmission may increase). [Method 3] can only work when the UE is capable of supporting a maximum of two uplink PTRS ports and the base station has configured higher-layer parameters so that the UE can operate a maximum of two uplink PTRS ports. In the case of simultaneous transmission of two-layer SFN PUSCH multi-panel, since two DMRS ports are associated with two PTRS ports, the multiplexing pattern of PUSCH and PTRS transmitted through each panel (or SRS resource set or TCI state) can be the same. However, when simultaneous transmission of three-layer or four-layer SFN PUSCH multi-panel is allowed as described later, the multiplexing pattern of PUSCH and PTRS transmitted through each panel (or SRS resource set or TCI state) may be the same or may be different depending on the value indicated by the PTRS-DMRS association field associated with each panel (or SRS resource set or TCI state).

[0490] [Method 4] The PTRS port for the PUSCH transmitted in association with the second panel (or the second SRS resource set or the second TCI state) is configured in the same manner as the PTRS port for the PUSCH transmitted in association with the first panel (or the first SRS resource set or the first TCI state).

[0491] If simultaneous SFN PUSCH multi-panel transmission is scheduled using DCI format 0_1 ​​or DCI format 0_2 (or if a Type 2-configured granted PUSCH is activated) or via higher-layer parameters (RRC parameters for scheduling a Type 1-configured granted PUSCH), the UE determines the PUSCH, DMRS port, and PTRS port to be transmitted in association with the first panel (or the first SRS resource set or the first TCI state) based on the scheduling information. The UE then performs resource mapping, including the PTRS, to transmit the corresponding PUSCH according to the configuration. Subsequently, based on the PUSCH transmitted in association with the first panel (or the first SRS resource set or the first TCI state), the UE may similarly configure the PUSCH to be transmitted in association with the second panel (or the second SRS resource set or the second TCI state). In other words, the UE may determine the port of the PTRS for the PUSCH transmitted in association with the second panel based on the configuration of the PTRS to be transmitted with the PUSCH transmitted in association with the first panel, and may generate and map the PTRS.

[0492] In other words, if SFN PUSCH multi-panel simultaneous transmission is scheduled by DCI format 0_1 ​​or DCI format 0_2 (or if the granted PUSCH of type 2 configuration is activated) or via higher layer parameters (RRC parameters for scheduling the granted PUSCH of type 1 configuration), the UE performs multi-panel simultaneous transmission by configuring the PUSCH to be transmitted in association with the second panel (or the second SRS resource set or the second TCI state) to be the same as the PUSCH transmitted in association with the first panel (or the first SRS resource set or the first TCI state) based on the scheduling information.

[0493] [Method 5] The PTRS port for the PUSCH transmitted in association with the first panel (or the first SRS resource set or the first TCI state) is configured in the same manner as the PTRS for the PUSCH transmitted in association with the second panel (or the second SRS resource set or the second TCI state).

[0494] Although [Method 5] is similar to [Method 4], the UE may determine the PTRS port configuration and multiplexing mode to be transmitted based on the PUSCH transmitted in association with the second panel (or the second SRS resource set or the second TCI state). In other words, the UE may determine the port of the PTRS of the PUSCH transmitted in association with the first panel based on the configuration of the PTRS transmitted together with the PUSCH transmitted in association with the second panel, and may generate and map the PTRS.

[0495] [Method 6] Perform rate matching based on the maximum number of actual PTRS ports or PUSCH transmitted through the first panel (or second panel), and transmit only the PTRS determined based on the information indicated by the SRI, TPMI, and PTRS-DMRS association field.

[0496] When performing rate matching on PUSCH (transmitted via the first and second panels), the UE can perform rate matching based on the maximum number of actual PTRS ports associated with the scheduled PUSCH. In this case, while the UE performs rate matching in the same manner for PUSCH transmitted via actual PTRS ports other than the maximum number of actual PTRS ports, the UE may not transmit the number of PTRS ports other than the actual PTRS ports along with the PUSCH transmitted via the corresponding panel, unlike [Method 2] or [Method 3]. In other words, the number of actual PTRS ports used as the basis for rate matching may differ from the number of PTRS ports used for actual transmission. The UE may maintain the resources mapped to PTRS other than the corresponding actual PTRS ports empty, without transmitting any channels or reference signals. In this case, the transmit power per symbol of the transmitted PUSCH may be reduced for the PTRS ports not used for transmission. In this case, the UE can increase the transmit power of the PTRS ports used for transmission by taking into account the transmit power of the PTRS ports not used for transmission. Alternatively, the UE can increase the transmit power of resources used for PUSCH data by taking into account the transmit power of the PTRS ports not used for transmission. Alternatively, the UE may transmit the PUSCH at reduced power depending on the PTRS port not used for transmission.

[0497] [Method 1] to [Method 6] are described using specific examples. In this case, the explanation is based on the assumption that the maximum number of uplink PTRS ports that the UE can support is 2. In the case where the maximum number of uplink PTRS ports that the UE can support is one, or the base station has configured the RRC parameters in the UE to support at most one uplink PTRS port, the descriptions of [Method 1] to [Method 6] can be modified to apply to the operation of one uplink PTRS port. Of course, when a maximum of one uplink PTRS port is supported, some methods (e.g., [Method 3]) may not be valid, but other methods can be explained and applied by modifying them for one uplink PTRS port.

[0498] For the method described above, whether the UE is scheduled for SFN PUSCH multi-panel simultaneous transmission may be determined based on the following higher-layer parameter configuration and the indication value of a specific field indicated in the scheduling DCI.

[0499] Figure 21 is a flowchart illustrating an example of operations in which a base station and a UE configure and transmit a PTRS depending on signaling between the base station and the UE and whether SFN PUSCH multi-panel simultaneous transmission is scheduled.

[0500] The base station may receive a UE capability report from the UE for supporting SFN PUSCH multi-panel simultaneous transmission (operation 2100). Thereafter, the base station may configure higher-layer parameters (RRC parameters) in the UE (operation 2110). The RRC parameters included in the RRC configuration may include parameters for uplink transmission and parameters for configuring the technologies to be supported among various transmission technologies for multi-panel simultaneous transmission. For example, an RRC parameter such as "ULTransmissionScheme" may be configured, and the corresponding RRC parameter may be configured as either "SFN" or "SDM." In the present disclosure, it is assumed that the corresponding RRC parameter is configured as "SFN." Furthermore, RRC parameters for supporting a unified TCI framework may also be configured. "unifiedTCI-StateType" may be configured via RRC signaling and may be configured to support NR Release 17 or NR Release 18. Furthermore, RRC parameters such as "enableMultipleTCIState" may be configured to support the transmission / reception of mTRPs based on multiple TCI states. In addition to the RRC parameters described above, the base station can configure two SRS resource sets in the UE to support the mTRP PUSCH transmission method, each SRS resource set having a usage configured as "codebook" or "non-Codebook". When two SRS resource sets, each with a usage of "codebook" or "non-Codebook", are configured, the base station can additionally indicate a 2-bit SRS resource set indicator (described later) in DCI format 0_1 ​​or 0_2 for scheduling PUSCH.

[0501] The base station may indicate the TCI state to the UE via DCI (operation 2120). The base station and the UE operate according to the unified TCI framework described above, and the number of TCI states indicated by the codepoint indicated by the corresponding DCI may be one or two. If the base station indicates only one TCI state via DCI, the base station and the UE support the sTRP-based transmission / reception method after the beam application time (BAT) (operation 2130).

[0502] When the base station indicates both TCI states via DCI, it can then schedule the PUSCH via DCI (operation 2140). The DCI used to schedule the PUSCH includes not only fields indicating the resources, precoding, and other information used for the scheduled PUSCH, but also an SRS resource set indicator field used to determine whether the corresponding PUSCH is transmitted to the sTRP or mTRP. When two SRS resource sets are configured (each with a usage configured as "codebook" or "non-codebook"), the SRS resource set indicator can be indicated by two bits in the DCI. When the SRS resource set indicator is indicated as "00" or "01," the PUSCH scheduled by the corresponding DCI is transmitted to the sTRP (operation 2150). sTRP PUSCH transmissions can be transmitted in the same manner as in existing NR Release 17, and the PTRS, which can be transmitted together at this time, can also be transmitted in the same manner (operation 2160).

[0503] If the SRS resource set indicator is indicated as "10" or "11," the PUSCH scheduled by the corresponding DCI may be transmitted using the mTRP SFN PUSCH multi-panel simultaneous transmission method (operation 2170). This is because the RRC parameters used to configure the uplink transmission method in operation 2110 already assume support for SFN in the RRC configuration. Regarding the PTRS transmitted together with the sDCI-based mTRPS SFN PUSCH multi-panel simultaneous transmission scheduled by the corresponding DCI, the PTRS port may be configured by considering one or a combination of the various [Methods 1] to [Method 6] described in the fifth embodiment, and transmitted by the UE together with the PUSCH (operation 2180).

[0504] In each of the above operations, certain operations may be omitted, or the operations may be performed in a different order. Additional operations not described herein may also be performed. The operations do not necessarily have to be performed sequentially.

[0505] Figure 22A is a flowchart illustrating an example of operation of a UE receiving and transmitting a configured PTRS according to at least one embodiment of the present disclosure.

[0506] according to Figure 22AThe UE may report its capabilities related to simultaneous PUSCH transmission using multiple panels to the base station (operation 2200). The UE capabilities may include the UE capability information described above. The UE may receive RRC configuration information from the base station for configuring simultaneous PUSCH transmission using multiple panels (operation 2205). The RRC configuration information may include the higher-layer parameters described above. The UE may then receive DCI from the base station indicating multiple unified TCI states (operation 2210). For example, the DCI may indicate two unified TCI states. The UE may then receive DCI from the base station for scheduling a PUSCH (operation 2215). The DCI may include at least one of resource information on the PUSCH, an SRS resource set indicator, a TPMI, and PTRS-DMRS association information for simultaneous PUSCH transmission using multiple panels. Based on the DCI for scheduling the PUSCH, the UE may transmit the PUSCH along with the PTRS and DMRS to the base station based on at least one combination of methods 1 to 6 described above (operation 2220).

[0507] The flowcharts described above illustrate exemplary methods that can be implemented according to the principles of the present disclosure, and various modifications can be made to the methods shown in the flowcharts herein. For example, although shown as a series of actions, the various operations in each figure can overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, operations can be omitted or replaced by other operations.

[0508] Figure 22B is a flowchart illustrating an example of operations of a base station configuring and receiving a PTRS according to at least one embodiment of the present disclosure.

[0509] according to Figure 22BThe base station may receive a UE capability report related to simultaneous PUSCH transmission using multiple panels from the UE (operation 2250). The UE capabilities may include the UE capability information described above. The base station may send RRC configuration information to the UE for configuring simultaneous PUSCH transmission using multiple panels (operation 2255). The RRC configuration information may include the higher-layer parameters described above. Thereafter, the base station sends DCI indicating multiple unified TCI states to the UE (operation 2260). For example, the DCI may indicate two unified TCI states. Thereafter, the base station sends DCI scheduling a PUSCH to the UE (operation 2265). The DCI may include at least one of resource information on the PUSCH, an SRS resource set indicator, a TPMI, and PTRS-DMRS association information for simultaneous PUSCH transmission using multiple panels. Based on the DCI scheduling the PUSCH, the UE may send a PUSCH along with a PTRS and a DMRS to the base station based on at least one combination of methods 1 to 6 described above, and the base station may receive the PUSCH along with the PTRS and DMRS (operation 2270).

[0510] The flowcharts described above illustrate exemplary methods that can be implemented according to the principles of the present disclosure, and various modifications may be made to the methods shown in the flowcharts herein. For example, although shown as a series of operations, the various operations in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, operations may be omitted or replaced by other operations.

[0511] The method specifically described in the fifth embodiment assumes that when performing SFN PUSCH multi-panel simultaneous transmission, the number of PUSCH layers transmitted via each panel (or each SRS resource set, or each TCI state) is at most two. However, a three-layer or four-layer SFN PUSCH multi-panel simultaneous transmission method with more than two layers is also contemplated. Even in this case, the UE determines the SRS resources and precoder to be referenced for transmission for each SRI field or TPMI field associated with the PUSCH transmitted via each panel (or each SRS resource set, or each TCI state). Therefore, as discussed above, the number of actual PTRS ports transmitted via each panel may be different (when scheduling up to two layers), or even if the number of actual PTRS ports is the same (two), the pattern in which PTRS is mapped to resources may be different. When [Method 1] to [Method 6] are explained in detail, although the method of reinterpreting 2 bits of a single PTRS-DMRS association field included in the DCI has been mainly explained, if three-layer or four-layer transmission is allowed for the SFN PUSCH multi-panel simultaneous transmission method, a second PTRS-DMRS association field included in the DCI associated with the second SRS resource set, as introduced in NR Release 17, can be used instead of reinterpreting the single PTRS-DMRS association field. Even when three-layer or four-layer SFN PUSCH multi-panel simultaneous transmission is performed by applying [Method 1] to [Method 6] described previously using two PTRS-DMRS association fields, PTRS ports can be mapped to resources and transmitted together.

[0512] Specifically, when supporting simultaneous transmission of multiple SFN PUSCH panels, two PTRS-DMRS association fields for scheduling PUSCH to the UE, included in DCI format 0_1 ​​or 0_2, may be indicated. In this case, the first PTRS-DMRS association field may be used to determine the association between the DMRS port and the PTRS port of the PUSCH transmitted via the first panel (or the first SRS resource set or the first TCI state). The second PTRS-DMRS association field may be used to determine the association between the DMRS port and the PTRS port of the PUSCH transmitted via the second panel (or the second SRS resource set or the second TCI state).

[0513] More specifically, assuming that four-layer SFN PUSCH multi-panel simultaneous transmission is scheduled via DCI format 0_1 ​​and RRC parameters are configured such that the UE can support two uplink PTRS ports. As a specific example, if the first PTRS-DMRS association field is indicated as "00" and the second PTRS-DMRS association field is indicated as "11," PTRS port 0 for PUSCH transmitted via the first panel (or the first SRS resource set or the first TCI state) can be associated with the first DMRS port that can be associated with PTRS port 0 (for "codebook"-based PUSCH, a PUSCH layer transmitted through PUSCH antenna ports 1000 (the first PUSCH antenna port) and / or 1002 (the third PUSCH antenna port) according to the TPMI, or for "non-Codebook"-based PUSCH, a PUSCH layer transmitted by referencing an SRS resource, among the SRS resources indicated by the SRI, that is configured with RRC to be associated with PTRS port 0). PTRS port 1 for PUSCH transmitted via the first panel (or the first SRS resource set or the first TCI state) may be associated with the first DMRS port among the two DMRS ports that may be associated with PTRS port 1 (for "codebook"-based PUSCH, a PUSCH layer transmitted through PUSCH antenna port 1001 (the second PUSCH antenna port) and / or 1003 (the fourth PUSCH antenna port) according to the TPMI, or for "non-Codebook"-based PUSCH, a PUSCH layer transmitted by referencing an SRS resource configured with RRC to be associated with PTRS port 1 among the SRS resources indicated by the SRI).

[0514] Similarly, since the second PTRS-DMRS association field is indicated as "11", the PTRS port 0 for the PUSCH sent via the second panel (or the second SRS resource set or the second TCI state) can be associated with the second DMRS port among the two DMRS ports, where the two DMRS ports can be associated with the PTRS port 0 (for "codebook" based PUSCH, the PUSCH layer transmitted through the PUSCH antenna port 1000 (first PUSCH antenna port) and / or 1002 (third PUSCH antenna port) according to the TPMI, or for "non-Codebook" based PUSCH, the PUSCH layer transmitted by referring to the SRS resources configured with RRC to be associated with the PTRS port 0 among the SRS resources indicated by the SRI). PTRS port 1 for PUSCH transmitted via the second panel (or second SRS resource set or second TCI state) may be associated with a second DMRS port among the two DMRS ports that may be associated with PTRS port 1 (for "codebook"-based PUSCH, a PUSCH layer transmitted through PUSCH antenna port 1001 (second PUSCH antenna port) and / or 1003 (fourth PUSCH antenna port) according to TPMI, or for "nonCodebook"-based PUSCH, a PUSCH layer transmitted by referencing an SRS resource configured with RRC to be associated with PTRS port 1 among the SRS resources indicated by SRI).

[0515] As discussed above, also in this case, the PTRS ports can be mapped to the PUSCH transmitted by each panel in different patterns. Therefore, one or a combination of [Method 1] to [Method 6] can be applied to support mapping the PTRS ports in the same pattern or performing the same PUSCH rate matching. Alternatively, since the actual number of PTRS ports is the same, it is possible to allow the PTRS ports to be transmitted using different mapping patterns. Even in the case of performing three-layer SFN PUSCH multi-panel simultaneous transmission, the actual number of PTRS ports is two, so four-layer SFN PUSCH multi-panel simultaneous transmission can also be handled in the same manner.

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

[0517] refer to Figure 23The UE may include a transceiver (collectively, a UE receiver 2300 and a UE transmitter 2310), a memory (not shown), and a UE processor 2305 (or a UE controller or processor). UE transceivers 2300 and 2310, the memory, and the UE processor may operate according to the communication method of the UE described above. The components of the UE are not limited to the examples described above. For example, the UE may include a greater or lesser number of components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

[0518] A transceiver can transmit and receive signals with a base station. The signals may include control information and data. To this end, the transceiver may include an RF transmitter configured to amplify and up-convert the frequency of the transmitted signal, an RF receiver configured to perform low-noise amplification and down-conversion of the frequency of the received signal, and the like. However, this is merely an embodiment of a transceiver, and the components of a transceiver are not limited to an RF transmitter and an RF receiver.

[0519] In addition, the transceiver may receive a signal through a radio channel, output the signal to the processor, and transmit a signal output from the processor through the radio channel.

[0520] The memory can store programs and data necessary for the operation of the base station. In addition, the memory can store control information or data included in the 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. In addition, the memory can include multiple memories.

[0521] In addition, the processor may control a series of processes so that the UE can operate according to the above-described embodiments.The processor may include a plurality of processors, and the processor may perform operations of controlling components of the UE by executing a program stored in a memory.

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

[0523] refer to Figure 24 The base station may include a transceiver (collectively, a base station receiver 2400 and a base station transmitter 2410), a memory (not shown), and a base station processor 2405 (or base station controller or processor). Base station transceivers 2400 and 2410, the memory, and the base station processor 2405 may operate according to the communication method of the base station described above. However, the components of the base station are not limited to the examples described above. For example, the base station may include a greater or lesser number of components than those described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of a single chip.

[0524] The transceiver can transmit and receive signals with the UE. The signals may include control information and data. To this end, the transceiver may include an RF transmitter configured to amplify and up-convert the frequency of the transmitted signal, an RF receiver configured to perform low-noise amplification and frequency down-conversion of the received signal, and the like. However, this is merely an embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and the RF receiver.

[0525] In addition, the transceiver may receive a signal through a radio channel, output the signal to the processor, and transmit a signal output from the processor through the radio channel.

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

[0527] The processor may control a series of processes so that the base station can operate according to the above-described embodiments of the present disclosure. The processor may include multiple processors, and the processor may execute the operation of controlling the components of the base station by executing the program stored in the memory.

[0528] The methods disclosed in the claims and / or the methods according to the embodiments described in the specification of the present disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0529] When the method is implemented via software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium 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 the method according to the various embodiments of the present disclosure as defined in the appended claims and / or disclosed herein.

[0530] These programs (software modules or software) may be stored in non-volatile memory including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage devices, compact disk-ROM (CD-ROM), digital versatile disk (DVD) or other types of optical storage devices or magnetic tape cartridges. Alternatively, any combination of some or all of them may form the memory in which the program is stored. In addition, multiple such memories may be included in the electronic device.

[0531] In addition, the program may be stored in an attachable storage device that is accessible to the electronic device via a communication network such as the Internet, an intranet, a local area network (LAN), a wide area LAN (WLAN), and a storage area network (SAN), or a combination thereof. Such a storage device may be accessible to the electronic device via an external port. Furthermore, a separate storage device on a communication network may be accessible to the portable electronic device.

[0532] In the detailed embodiments described above of the present disclosure, the elements included in the present disclosure are expressed in the singular or plural, depending on the detailed embodiment presented. However, for ease of description, the singular or plural form is appropriately selected according to the presented situation, and the present disclosure is not limited to the elements expressed in the singular or plural. Therefore, an element expressed in the plural may also include a single element, or an element expressed in the singular may also include a plurality of elements.

[0533] The embodiments of the present disclosure described and illustrated in the specification and the drawings are merely specific examples that have been presented to easily explain the technical content of the present disclosure and to help understand the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical ideas of the present disclosure can be implemented. In addition, the above-mentioned various embodiments can be used in combination as needed. For example, a part of an embodiment of the present disclosure can be combined with a part of another embodiment to operate a base station and a terminal. As an example, a part of the first embodiment of the present disclosure can be combined with a part of the second embodiment to operate a base station and a terminal. Moreover, other variations based on the technical ideas of the embodiments can also be implemented in other communication systems such as TDD LTE, 5G or NR systems.

[0534] In the drawings describing the methods of the present disclosure, the order of description does not always correspond to the order of performing the steps of each method, and the sequential relationship between the steps may be changed or the steps may be performed in parallel.

[0535] Alternatively, in the drawings describing the method of the present disclosure, some elements may be omitted, and only some elements may be included without departing from the basic spirit and scope of the present disclosure.

[0536] In addition, in the method of the present disclosure, some or all of the contents of each embodiment may be implemented in combination without departing from the basic spirit and scope of the present disclosure.

[0537] Various embodiments of the present disclosure have been described above. The above description of the present disclosure is for illustrative purposes and is not intended to limit the embodiments of the present disclosure to the embodiments set forth herein. Those skilled in the art will recognize that other specific modifications and changes to the form of the present disclosure can be easily made without changing the technical ideas or basic features of the present disclosure. The scope of the present disclosure is defined by the appended claims, rather than by the above detailed description, and the scope of the present disclosure should be interpreted 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 communication system, the method comprising: receiving higher layer signaling from a base station, the higher layer signaling including information for configuring a simultaneous uplink transmission scheme for two transmit and receive points (TRPs) as a single frequency network (SFN) scheme and information for configuring uplink phase tracking reference signal (PTRS) transmission; receiving downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH) and a second PUSCH from a base station; Mapping a first PUSCH to a first uplink PTRS and mapping a second PUSCH to a second uplink PTRS based on a first transmit precoding matrix indicator (TPMI) or a second sounding reference signal resource indicator (SRI) included in the DCI; as well as Sending a first PUSCH, a first uplink PTRS, a second PUSCH, and a second uplink PTRS, Herein, the same rate matching is applied to uplink data transmitted via the first PUSCH and the second PUSCH, and the first uplink PTRS and the second uplink PTRS are mapped to the same time-frequency resources.

2. The method according to claim 1, wherein In case that the first PUSCH and the second PUSCH are transmitted through a codebook-based scheme, a first uplink PTRS is identified based on a first TPMI and a first demodulation reference signal (DMRS) configuration transmitted along with the first PUSCH.

3. The method according to claim 1, wherein In case that the first PUSCH and the second PUSCH are transmitted through a non-codebook based scheme, a first uplink PTRS is identified based on a first SRI and a first demodulation reference signal (DMRS) configuration transmitted along with the first PUSCH.

4. The method according to claim 1, wherein The first PUSCH is transmitted based on a first transmission configuration indicator TCI state indicated to the terminal, and the second PUSCH is transmitted based on a second TCI state indicated to the terminal.

5. A method performed by a base station in a communication system, the method comprising: sending higher layer signaling to the terminal, the higher layer signaling including information for configuring a simultaneous uplink transmission scheme of two transmission and reception points (TRPs) as a single frequency network (SFN) scheme and information for configuring uplink phase tracking reference signal (PTRS) transmission; transmitting downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH) and a second PUSCH to the terminal; and receiving a first PUSCH, a first uplink PTRS, a second PUSCH, and a second uplink PTRS, wherein, based on a first transmit precoding matrix indicator (TPMI) or a second sounding reference signal resource indicator (SRI) included in the DCI, the first PUSCH is mapped to a first uplink PTRS, and the second PUSCH is mapped to a second uplink PTRS, and Herein, the same rate matching is applied to uplink data transmitted via the first PUSCH and the second PUSCH, and the first uplink PTRS and the second uplink PTRS are mapped to the same time-frequency resources.

6. The method according to claim 5, wherein: In case that the first PUSCH and the second PUSCH are transmitted through a codebook-based scheme, the first uplink PTRS is associated with a first TPMI and a first demodulation reference signal (DMRS) configuration transmitted together with the first PUSCH.

7. The method according to claim 5, wherein: In case that the first PUSCH and the second PUSCH are transmitted through a non-codebook based scheme, the first uplink PTRS is associated with a first SRI and a first demodulation reference signal (DMRS) configuration transmitted together with the first PUSCH.

8. The method according to claim 5, wherein The first PUSCH is transmitted based on a first transmission configuration indicator TCI state indicated to the terminal, and the second PUSCH is transmitted based on a second TCI state indicated to the terminal.

9. A terminal in a communication system, the terminal comprising: transceiver; as well as The controller is configured as: receiving higher layer signaling from a base station, the higher layer signaling including information for configuring a simultaneous uplink transmission scheme of two transmit and receive points (TRPs) as a single frequency network (SFN) scheme and information for configuring uplink phase tracking reference signal (PTRS) transmission, receiving downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH) and a second PUSCH from a base station, Based on a first transmit precoding matrix indicator (TPMI) or a second sounding reference signal resource indicator (SRI) included in the DCI, mapping the first PUSCH to a first uplink PTRS and mapping the second PUSCH to a second uplink PTRS, and Sending a first PUSCH, a first uplink PTRS, a second PUSCH, and a second uplink PTRS, Herein, the same rate matching is applied to uplink data transmitted via the first PUSCH and the second PUSCH, and the first uplink PTRS and the second uplink PTRS are mapped to the same time-frequency resources.

10. The terminal according to claim 9, wherein: In case that the first PUSCH and the second PUSCH are transmitted through a codebook-based scheme, a first uplink PTRS is identified based on a first TPMI and a first demodulation reference signal (DMRS) configuration transmitted along with the first PUSCH. The terminal according to claim 9 , wherein: In case that the first PUSCH and the second PUSCH are transmitted through a non-codebook based scheme, a first uplink PTRS is identified based on a first SRI and a first demodulation reference signal (DMRS) configuration transmitted along with the first PUSCH.

12. The terminal according to claim 9, wherein: The first PUSCH is transmitted based on a first transmission configuration indicator TCI state indicated to the terminal, and the second PUSCH is transmitted based on a second TCI state indicated to the terminal.

13. A base station in a communication system, the base station comprising: transceiver; as well as The controller is configured as: Sending high-layer signaling to the terminal, the high-layer signaling including information for configuring a simultaneous uplink transmission scheme of two transmission and reception points (TRPs) as a single frequency network (SFN) scheme and information for configuring uplink phase tracking reference signal (PTRS) transmission, Sending downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH) and a second PUSCH to the terminal, and receiving a first PUSCH, a first uplink PTRS, a second PUSCH, and a second uplink PTRS, wherein, based on a first transmit precoding matrix indicator (TPMI) or a second sounding reference signal resource indicator (SRI) included in the DCI, the first PUSCH is mapped to a first uplink PTRS, and the second PUSCH is mapped to a second uplink PTRS, and Herein, the same rate matching is applied to uplink data transmitted via the first PUSCH and the second PUSCH, and the first uplink PTRS and the second uplink PTRS are mapped to the same time-frequency resources.

14. The base station according to claim 13, wherein: In case that the first PUSCH and the second PUSCH are transmitted through a codebook-based scheme, the first uplink PTRS is associated with a first TPMI and a first demodulation reference signal (DMRS) configuration transmitted together with the first PUSCH.

15. The base station according to claim 13, wherein: In case that the first PUSCH and the second PUSCH are transmitted through a non-codebook based scheme, the first uplink PTRS is associated with a first SRI and a first demodulation reference signal (DMRS) configuration transmitted together with the first PUSCH.

Images