Method and apparatus for power headroom reporting for uplink-only base station in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to an embodiment of the present disclosure, a method of a user equipment comprises the steps of: receiving, from a base station, simultaneous transmission across multiple panels (STxMP)-based SRS information; identifying a first SRS resource set corresponding to a first TRP on the basis of the STxMP-related SRS information; transmitting first SRSs to the first TRP on the basis of the first SRS resource set; and reporting, to the base station, CSI for beam combination candidates for STxMP, wherein at least one of the first TRP or the second TRP supports only uplink reception for the user equipment.

Description

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

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

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

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

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

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] The disclosed embodiments aim to provide an apparatus and method capable of effectively providing services in a mobile communication system.

[0009] The present disclosure, for solving the above-mentioned problems, is characterized in that a method for processing a control signal in a wireless communication system comprises: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

[0010] The disclosed embodiments provide an apparatus and method capable of effectively providing services in a mobile communication system.

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

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

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

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

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

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

[0017] Figure 7 illustrates the process for beam setup and activation of PDSCH.

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

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

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

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

[0022] Figure 12 shows an example of supporting mTRP uplink transmission using a TRP that supports only multiple uplink reception functions.

[0023] Figure 13 is a diagram showing an example of a MAC CE format for updating an SRS resource within an SRS resource set.

[0024] FIG. 14a is a drawing illustrating the operation of a terminal according to a first embodiment of the present disclosure.

[0025] FIG. 14b is a drawing illustrating the operation of a base station according to a first embodiment of the present disclosure.

[0026] FIG. 15a is a drawing illustrating the operation of a terminal according to a second embodiment of the present disclosure.

[0027] FIG. 15b is a drawing illustrating the operation of a terminal according to a second embodiment of the present disclosure.

[0028] FIG. 16 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0029] FIG. 17 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

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

[0031] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0032] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0033] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the disclosure, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the present disclosure.

[0034] Hereinafter, a base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. A terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technologies (5G, new radio, NR) developed after LTE-A may be included therein, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0035] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing instruction means to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0036] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.

[0037] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

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

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

[0040] As a future communication system following LTE, that is, a 5G communication system, it must be able to freely reflect the diverse requirements of users and service providers, and therefore, services that satisfy various requirements simultaneously must be supported. Services being considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0041] eMBB aims to provide data transmission speeds that are superior to those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink from the perspective of a single base station. Furthermore, while providing these peak data rates, the 5G communication system must also provide an increased user-perceived data rate. To satisfy these requirements, it necessitates improvements in various transmission and reception technologies, including enhanced Multi-Input Multi-Output (MIMO) transmission technology. Additionally, while LTE transmits signals using a maximum bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can meet the data transmission speeds required by using a frequency bandwidth wider than 20 MHz in frequency bands of 3–6 GHz or above 6 GHz.

[0042] Simultaneously, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT, mMTC requires support for a large number of terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT devices are attached to various sensors and equipment to provide communication functions, the system must be able to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km²). Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in dead zones not covered by cells, such as building basements; therefore, they may require wider coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must consist of low-cost devices, and since it is difficult to frequently replace terminal batteries, a very long battery life of 10 to 15 years may be required.

[0043] Finally, URLLC is a mission-critical cellular-based wireless communication service. For example, consider services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For instance, services supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds, and simultaneously 10 -5The following packet error rate requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a Transmit Time Interval (TTI) smaller than other services, and at the same time, design considerations may be required to allocate a wide resource in the frequency band to ensure the reliability of the communication link.

[0044] The three 5G services, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. In this case, different transmission and reception techniques and parameters may be used between the services to satisfy the different requirements of each service. Of course, 5G is not limited to the three services mentioned above.

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

[0046] [NR Time-Frequency Resources]

[0047] The frame structure of the 5G system will be explained in more detail below with reference to the drawings.

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

[0049] The horizontal axis of FIG. 1 represents the time domain, and the vertical axis represents the frequency domain. In the time and frequency domains, the basic unit of a resource is a resource element (RE, 101), which can be defined as one OFDM (Orthogonal Frequency Division Multiplexing) symbol (102) on the time axis and one subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can form a single resource block (Resource Block, RB, 104). In the time axis, a single subframe (110) may contain multiple OFDM symbols (102). For example, the length of one subframe may be 1 ms.

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

[0051] FIG. 2 illustrates an example of a frame (200), subframe (201), and slot (202) structure. One frame (200) can be defined as 10ms. One subframe (201) can be defined as 1ms, and thus one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( = 14). One subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per one subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In one example of FIG. 2, cases where μ=0 (204) and μ=1 (205) are shown as the setting value for the subcarrier spacing. When μ=0 (204), one subframe (201) may be composed of one slot (202), and when μ=1 (205), one subframe (201) may be composed of two slots (203). That is, the number of slots per one subframe ( ) may vary, and accordingly, the number of slots per frame ( ) may vary. Depending on each subcarrier spacing setting μ and It can be defined by Table 1 below.

[0052] [Table 1]

[0053]

[0054] [Bandwidth Section (BWP)]

[0055] Next, the Bandwidth Part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.

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

[0057] FIG. 3 shows an example in which the terminal bandwidth (UE bandwidth) (300) is configured into two bandwidth portions, namely bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station may configure one or more bandwidth portions for the terminal and may configure the following information for each bandwidth portion.

[0058] [Table 2]

[0059]

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

[0061] According to some embodiments, prior to the Radio Resource Control (RRC) connection, the terminal may receive an Initial Bandwidth Part (Initial BWP) for initial connection from the base station via a Master Information Block (MIB). More specifically, during the initial connection phase, the terminal may receive configuration information for a Control Resource Set (CORESET) and a Search Space via the MIB, through which a PDCCH can be transmitted to receive system information required for initial connection (Remaining System Information; which may correspond to RMSI or System Information Block 1; SIB1). The Control Resource Set and Search Space configured via the MIB may each be considered as Identity (ID) 0. The base station may notify the terminal via the MIB of configuration information, such as frequency allocation information, time allocation information, and numerology, for Control Resource Set #0. Additionally, the base station may notify the terminal via the MIB of configuration information regarding the monitoring period and occasion for Control Resource Set #0, i.e., configuration information for Search Space #0. The terminal may consider the frequency region set as control region #0 obtained from the MIB as the initial bandwidth portion for initial access. In this case, the identifier (ID) of the initial bandwidth portion may be considered as 0.

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

[0063] According to some embodiments, if the bandwidth supported by the terminal is smaller than the system bandwidth, this can be supported through the bandwidth portion setting. For example, by setting the frequency position of the bandwidth portion (setting information 2) to the terminal, the terminal can transmit and receive data at a specific frequency position within the system bandwidth.

[0064] In addition, according to some embodiments, a base station may set multiple bandwidth portions for a terminal for the purpose of supporting different numerologies. For example, to support data transmission and reception using both a 15 kHz subcarrier interval and a 30 kHz subcarrier interval for a terminal, two bandwidth portions may be set to subcarrier intervals of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be frequency division multiplexed, and when data transmission and reception is to be performed with a specific subcarrier interval, the bandwidth portion set to that subcarrier interval may be activated.

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

[0066] In the method for configuring the above bandwidth portion, terminals prior to RRC connection (Connected) can receive configuration information for the Initial Bandwidth Part through the Master Information Block (MIB) during the initial connection phase. More specifically, the terminal can receive a Control Resource Set (CORESET) for a downlink control channel through which Downlink Control Information (DCI) scheduling System Information Blocks (SIB) can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the control resource set by the MIB can be considered as the Initial Bandwidth Part, and through the configured Initial Bandwidth Part, the terminal can receive the Physical Downlink Shared Channel (PDSCH) through which SIBs are transmitted. In addition to receiving SIBs, the Initial Bandwidth Part may also be utilized for Other System Information (OSI), paging, and Random Access.

[0067] [Bandwidth Section (BWP) Change]

[0068] When one or more bandwidth parts are set for a terminal, the base station may instruct the terminal to change (or switch, transition) the bandwidth part using the Bandwidth Part Indicator field within the DCI. For example, in FIG. 3, if the currently active bandwidth part of the terminal is Bandwidth Part #1 (301), the base station may instruct the terminal to Bandwidth Part #2 (302) using the Bandwidth Part Indicator within the DCI, and the terminal may perform a bandwidth part change to Bandwidth Part #2 (302) indicated by the received Bandwidth Part Indicator within the DCI.

[0069] As mentioned above, since DCI-based bandwidth portion changes can be directed by the DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth portion change request, it must be able to receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth portion without difficulty. To this end, the standard specifies the delay time (T) required when changing the bandwidth portion. BWP The requirements for ) have been defined, and can be defined as, for example, as follows.

[0070] [Table 3]

[0071] *

[0072] The requirements for bandwidth portion change delay time support Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth portion delay time type to the base station.

[0073] In accordance with the aforementioned requirements for the bandwidth portion change delay time, if the terminal receives a DCI containing a bandwidth portion change indicator in slot n, the terminal performs a change to the new bandwidth portion indicated by the bandwidth portion change indicator in slot n+T BWP Completion can be performed at a time no later than the new bandwidth portion, and transmission and reception for the data channel scheduled by the corresponding DCI can be performed in the changed new bandwidth portion. If the base station intends to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP By considering ), time-domain resource allocation for a data channel can be determined. That is, when a base station schedules a data channel with a new bandwidth portion, in the method for determining time-domain resource allocation for a data channel, the data channel can be scheduled after the bandwidth portion change delay time. Accordingly, the terminal [is notified] that the DCI instructing the bandwidth portion change is the bandwidth portion change delay time (T BWPYou may not expect to indicate a slot offset (K0 or K2) value smaller than )

[0074] If a terminal receives a DCI (e.g., DCI format 1_1 or 0_1) instructing a change in the bandwidth portion, the terminal may not perform any transmission or reception during a time interval corresponding to the time interval from the third symbol of the slot in which the PDCCH containing the said DCI was received to the beginning of the slot indicated by the slot offset value (K0 or K2) indicated by the time domain resource allocation indicator field within the said DCI. For example, if a terminal receives a DCI instructing a change in the bandwidth portion in slot n, and the slot offset value indicated by the said DCI is K, the terminal may not perform any transmission or reception from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+K-1).

[0075] [CA / DC Related]

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

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

[0078] The main functions of NR SDAP (S25, S70) may include some of the following functions.

[0079] - User data transfer function (transfer of user plane data)

[0080] - Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

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

[0082] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0083] Regarding the SDAP layer device, the terminal may receive a setting via an RRC message indicating whether to use the header of the SDAP layer device or the functions of the SDAP layer device for each PDCP layer device, for each bearer, or for each logical channel. If the SDAP header is set, the terminal may be instructed to update or reset the mapping information for the uplink and downlink QoS flows and data bearers to the NAS reflective QoS and AS reflective QoS 1-bit indicators of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priority, scheduling information, etc., to support smooth service.

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

[0085] - Header compression and decompression features (ROHC only)

[0086] - User data transfer function (Transfer of user data)

[0087] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

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

[0089] - Reordering function (PDCP PDU reordering for reception)

[0090] - Duplicate detection function (Duplicate detection of lower layer SDUs)

[0091] - Retransmission of PDCP SDUs

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

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

[0094] In the above, the reordering function of the NR PDCP device refers to a function that reorders PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function that transmits data to an upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP device may include a function that transmits immediately without considering the order, a function that records lost PDCP PDUs by reordering, a function that reports the status of lost PDCP PDUs to the transmitting side, and a function that requests retransmission of lost PDCP PDUs.

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

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

[0097] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

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

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

[0100] - Concatenation, segmentation, and reassembly functions of RLC SDUs

[0101] - Re-segmentation function (Re-segmentation of RLC data PDUs)

[0102] - Reordering function (Reordering of RLC data PDUs)

[0103] - Duplicate detection

[0104] - Error detection function (Protocol error detection)

[0105] - RLC SDU discard function

[0106] RLC re-establishment function

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

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

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

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

[0111] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)

[0112] - Scheduling information reporting function

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

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

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

[0116] - MBMS service identification function

[0117] - Transport format selection function

[0118] - Padding

[0119] The NR PHY layer (S45, S50) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0120] The above wireless protocol structure may vary in detail depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure having a single structure for each layer, as shown in S00. On the other hand, when a base station transmits data to a terminal based on Carrier Aggregation (CA) using multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to the RLC, as shown in S10, but multiplexes the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on Dual Connectivity (DC) using multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to the RLC, as shown in S20, but multiplexes the PHY layer through the MAC layer.

[0121] [Unified TCI state]

[0122] The following describes a method for instructing and activating a single TCI state based on the unified TCI scheme. The unified TCI scheme refers to a method of managing transmit and receive beams by integrating the TCI state used for downlink reception and the spatial relation info used for uplink transmission—which were distinguished in the existing Rel-15 and Rel-16—into a single TCI state. Therefore, when a terminal receives instructions from a base station based on the unified TCI scheme, it can perform beam management using the TCI state for uplink transmission as well. If the terminal receives a TCI-State, which is a higher-layer signaling with the tci-stateId-r17, from the base station, the terminal can perform operations based on the unified TCI scheme using that TCI-State. The TCI-State can exist in two forms: a joint TCI state or a separate TCI state.

[0123] The first form is a joint TCI state, and the terminal can receive instructions from the base station regarding the TCI state to be applied for both uplink transmission and downlink reception through a single TCI-State. If the terminal receives a TCI-State based on the joint TCI state, the terminal can receive instructions regarding parameters to be used for downlink channel estimation using the RS corresponding to qcl-Type1 within the joint TCI state-based TCI-State, and parameters to be used as a downlink reception beam or reception filter using the RS corresponding to qcl-Type2. If the terminal receives a TCI-State based on the joint TCI state, the terminal can receive instructions regarding parameters to be used as an uplink transmission beam or transmission filter using the RS corresponding to qcl-Type2 within the joint DL / UL TCI state-based TCI-State. In this case, if the terminal receives a joint TCI state, the terminal can apply the same beam to both uplink transmission and downlink reception.

[0124] The second form is a separate TCI state, and the terminal can individually receive instructions from the base station for an UL TCI state to be applied for uplink transmission and a DL TCI state to be applied for downlink reception. If the terminal is instructed with an UL TCI state, the terminal can be instructed with parameters to be used as an uplink transmission beam or transmission filter using a reference RS or source RS set within the corresponding UL TCI state. If the terminal is instructed with a DL TCI state, the terminal can be instructed with parameters to be used for downlink channel estimation using an RS corresponding to qcl-Type1 set within the corresponding DL TCI state, and parameters to be used as a downlink reception beam or reception filter using an RS corresponding to qcl-Type2.

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

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

[0127] Among the separate TCI states, the UL TCI state can be configured with up to 32 or 64 upper layer signalings for each specific bandwidth part within a specific cell based on terminal capability reports, and like the relationship between the DL TCI state and the joint TCI state among the separate TCI states, the UL TCI state and the joint TCI state among the separate TCIs may also use the same upper layer signaling structure, or the UL TCI state among the separate TCIs may use a different upper layer signaling structure from the joint TCI state and the DL TCI state among the separate TCIs.

[0128] Using different or identical upper-layer signaling structures as described above may be defined in the specifications, or may be distinguished through another upper-layer signaling configured by the base station based on a terminal capability report containing information on which of the two usage modes the terminal can support.

[0129] The terminal can receive instructions regarding transmit / receive beams in an integrated TCI manner by utilizing one of the joint TCI state and separate TCI state configured by the base station. The terminal can receive a configuration from the base station via upper-layer signaling regarding whether to use one of the joint TCI state or separate TCI state.

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

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

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

[0133] FIG. 5 is a diagram of the beam application time that can be considered when using an integrated TCI method in a wireless communication system according to one embodiment of the present disclosure. As described above, the terminal receives DCI format 1_1 or 1_2 from a base station that includes downlink data channel scheduling information (with DL assignment) or does not include it (without DL assignment), and can apply one joint TCI state or a set of separate TCI states indicated by the TCI state field within the DCI to the uplink transmit and downlink receive beams.

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

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

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

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

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

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

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

[0141] The terminal may transmit a PUCCH containing a HARQ-ACK indicating whether reception of DCI format 1_1 or 1_2, in which the above-described items are assumed, was successful (560).

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

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

[0144] A terminal can apply a single joint TCI state indicated via MAC-CE or DCI to the reception of control resource sets connected to all terminal-specific search spaces, the reception of PDSCH scheduled to PDCCH transmitted from said control resource set, the transmission of PUSCH, and the transmission of all PUCCH resources.

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

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

[0147] If a separate set of TCI states indicated by MAC-CE or DCI includes one DL TCI state and one UL TCI state, the terminal may apply the DL TCI state to the reception of control resource sets connected to all terminal-specific search spaces and to the reception of PDSCH scheduled to PDCCH transmitted from said control resource sets, and may apply the UL TCI state to all PUSCH and PUCCH resources.

[0148] [Unified TCI state MAC-CE]

[0149] The following describes a single TCI state instruction and activation method based on an integrated TCI method. A terminal receives a PDSCH containing the following MAC-CE from a base station and, starting from the third slot after transmitting a HARQ-ACK for the PDSCH to the base station, can interpret each code point of the TCI state field in DCI format 1_1 or 1_2 based on the information within the MAC-CE received from the base station. That is, the terminal can activate each entry of the MAC-CE received from the base station to each code point of the TCI state field in DCI format 1_1 or 1_2.

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

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

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

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

[0154] - Pi (615): This field indicates whether each code point in the TCI state field within DCI format 1_1 or 1_2 has multiple TCI states or one TCI state. If the value of Pi is 1, it means that the corresponding i-th code point has multiple TCI states, which may mean that the code point may contain separate DL TCI states and separate UL TCI states. If the value of Pi is 0, it means that the corresponding i-th code point has a single TCI state, which may mean that the code point may contain one of a joint TCI state, a separate DCI TCI state, or a separate UL TCI state.

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

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

[0157] - R: Represents a reserved bit and can be set to 0.

[0158]

[0159] Regarding the MAC-CE structure of FIG. 6 described above, the terminal may include a third octet containing fields P1, P2, ..., P8 in FIG. 6 within the MAC-CE structure, regardless of whether unifiedTCI-StateType-r17 in MIMOparam-r17 within ServingCellConfig, which is an upper layer signaling, is set to joint or separate. In this case, the terminal may perform TCI state activation using a fixed MAC-CE structure, regardless of the upper layer signaling received from the base station. As another example, regarding the MAC-CE structure of FIG. 6 described above, if unifiedTCI-StateType-r17 in MIMOparam-r17 within ServingCellConfig, which is an upper layer signaling, is set to joint, the terminal may omit the third octet containing fields P1, P2, ..., P8 in FIG. 6. In this case, the terminal can save up to 8 bits of the payload of the corresponding MAC-CE according to the upper layer signaling set by the base station. Additionally, all D / U fields located from the fourth octet to the first bit in FIG. 6 can be considered as R fields, and all corresponding R fields can be set to 0 bits.

[0160] [PDCCH: DCI related]

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

[0162] In a 5G system, scheduling information for uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) is transmitted from the base station to the terminal via DCI. The terminal can monitor the fallback DCI format and the non-fallback DCI format for PUSCH or PDSCH. The fallback DCI format may consist of fixed fields selected between the base station and the terminal, and the non-fallback DCI format may include configurable fields.

[0163] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after undergoing channel coding and modulation processes. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled into a Radio Network Temporary Identifier (RNTI) corresponding to the terminal's identity. Different RNTIs may be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control commands, or random access responses. In other words, the RNTI is not transmitted explicitly but is included in the CRC calculation process. Upon receiving a DCI message transmitted over the PDCCH, the terminal checks the CRC using the assigned RNTI; if the CRC check result is correct, the terminal knows that the message has been transmitted to it.

[0164] For example, a DCI scheduling a PDSCH for System Information (SI) can be scrambled to SI-RNTI. A DCI scheduling a PDSCH for Random Access Response (RAR) messages can be scrambled to RA-RNTI. A DCI scheduling a PDSCH for Paging messages can be scrambled to P-RNTI. A DCI notifying a Slot Format Indicator (SFI) can be scrambled to SFI-RNTI. A DCI notifying Transmit Power Control (TPC) can be scrambled to TPC-RNTI. A DCI scheduling a terminal-specific PDSCH or PUSCH can be scrambled to C-RNTI (Cell RNTI).

[0165] DCI format 0_0 can be used as a countermeasure DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI may include, for example, the information in [Table 4] below.

[0166] [Table 4]

[0167]

[0168] DCI format 0_1 ​​can be used as a non-defense DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI may include, for example, the information in [Table 5] below.

[0169] [Table 5]

[0170]

[0171]

[0172] DCI format 1_0 can be used as a countermeasure DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI may include, for example, the information in [Table 6] below.

[0173] [Table 6]

[0174]

[0175] DCI format 1_1 can be used as a non-defense DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI may include, for example, the information in [Table 7] below.

[0176] [Table 7]

[0177]

[0178]

[0179] [PUCCH: Transmission Related]

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

[0181] PUCCH resources can be broadly classified into long PUCCH and short PUCCH depending on the length of the allocated symbols. In an NR system, long PUCCH has a length of 4 symbols or more within a slot, while short PUCCH has a length of 2 symbols or less within a slot.

[0182] To explain Long PUCCH in more detail, Long PUCCH can be used to improve uplink cell coverage and therefore can be transmitted via a single carrier transmission method, DFT-S-OFDM, rather than OFDM transmission. Long PUCCH supports transmission formats such as PUCCH format 1, PUCCH format 3, and PUCCH format 4, depending on the number of control information bits supported and whether terminal multiplexing is supported through Pre-DFT OCC support in front of the IFFT.

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

[0184] For example, if the number of transmitted symbols in PUCCH format 1 is 8 symbols, the 8 symbols may be composed sequentially of DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, and UCI symbol, starting from the first starting symbol. The DMRS symbol is an orthogonal code (or orthogonal sequence or spreading code, ) on the time axis within a sequence corresponding to a length of 1 RB on the frequency axis within a single OFDM symbol. It can be spread using ) and transmitted after performing IFFT.

[0185] For the UCI symbol, the terminal generates d(0) by modulating 1-bit control information with BPSK and 2-bit control information with QPSK, scrambles the generated d(0) by multiplying it by a sequence of length 1 RB along the frequency axis, and applies an orthogonal code (or orthogonal sequence or spreading code, ) along the time axis to the scrambled sequence It can be spread using )) and transmitted after performing IFFT.

[0186] The terminal generates a sequence based on the group hopping or sequence hopping settings and the configured ID received from the base station as upper layer signaling, and generates a sequence corresponding to a length of 1 RB by cyclic shifting the generated sequence with the initial CS (cyclic shift) value configured as the upper signal.

[0187] If the length of the spreading code (NSF) is given It is determined as follows, and specifically given as shown in the following [Table 8]. i represents the index of the spreading code itself, and m represents the indices of the elements of the spreading code. Here, the numbers inside [ ] in [Table 8] are It means, for example, if the length of the spreading code is 2 and the index i of the set spreading code is 0, the spreading code silver It became =

[0011] becomes.

[0188] [Table 8]

[0189]

[0190] Next, PUCCH format 3 is a long PUCCH format based on DFT-S-OFDM that can support control information of more than 2 bits, and the number of RBs used can be configured through the upper layer. The control information can be composed of a combination of HARQ-ACK, SR, and CSI, or each of them. In PUCCH format 3, the DMRS symbol positions are presented in the following [Table 9] depending on whether frequency hopping within the slot is performed and whether additional DMRS symbols are configured.

[0191] [Table 9]

[0192]

[0193] For example, if the number of transmitted symbols in PUCCH format 3 is 8 symbols, the first starting symbol of the 8 symbols is 0, and DMRS is transmitted at the 1st and 5th symbols. [Table 9] applies in the same way to the DMRS symbol positions in PUCCH format 4.

[0194] Next, PUCCH format 4 is a long PUCCH format based on DFT-S-OFDM capable of supporting control information exceeding 2 bits, and it utilizes 1 RB of frequency resources. The control information can consist of a combination of HARQ-ACK, SR, and CSI, or each of them individually. The difference between PUCCH format 4 and PUCCH format 3 is that PUCCH format 4 for multiple terminals can be multiplexed within a single RB. Multiplexing of PUCCH format 4 for multiple terminals is possible by applying Pre-DFT OCC (Orthogonal Cover Code) to the control information before the IFFT layer. However, the number of control information symbols that can be transmitted by a single terminal decreases depending on the number of terminals being multiplexed. The number of multiplexable terminals, i.e., the number of different available OCCs, can be 2 or 4, and the number of OCCs and the OCC index to be applied can be configured through the upper layer.

[0195] Next, we will explain short PUCCH. Short PUCCH can be transmitted in both the downlink centric slot and the uplink centric slot, and generally, it can be transmitted at the last symbol of the slot or at the OFDM symbols following it (e.g., the very last OFDM symbol, the second-to-last OFDM symbol, or the last two OFDM symbols). Of course, it is also possible for a short PUCCH to be transmitted at any location within the slot. Furthermore, a short PUCCH can be transmitted using either one OFDM symbol or two OFDM symbols. Short PUCCH can be used to reduce latency compared to long PUCCH in situations where uplink cell coverage is good, and it can be transmitted via the CP-OFDM method.

[0196] Short PUCCH can support transmission formats such as PUCCH format 0 and PUCCH format 2 depending on the number of supported control information bits. First, PUCCH format 0 is a short PUCCH format capable of supporting up to 2 bits of control information and uses 1 RB of frequency resources. The control information can consist of a combination of HARQ-ACK and SR, or each individually. PUCCH format 0 is structured to transmit only a sequence mapped to 12 subcarriers along the frequency axis within a single OFDM symbol, without transmitting DMRS. The terminal can generate a sequence based on the group hopping or sequence hopping settings and the configured ID received as an upper signal from the base station, cyclic shift the generated sequence using the final CS value obtained by adding a different CS value depending on whether it is an ACK or a NACK to the indicated initial CS (cyclic shift) value, map it to 12 subcarriers, and transmit it.

[0197] For example, if the HARQ-ACK is 1 bit, the terminal can generate the final CS by adding 6 to the initial CS value if it is an ACK, and the final CS by adding 0 to the initial CS if it is a NACK, as shown in [Table 10] below. The CS value 0 for NACK and the CS value 6 for ACK are defined in the standard, and the terminal can transmit a 1-bit HARQ-ACK by generating PUCCH format 0 according to the values ​​defined in the standard.

[0198] [Table 10]

[0199]

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

[0201] [Table 11]

[0202]

[0203] Next, PUCCH format 2 is a short PUCCH format that supports control information exceeding 2 bits, and the number of RBs used can be set through the upper layer. The control information can consist of a combination of HARQ-ACK, SR, and CSI, or each of them. When the index of the first subcarrier is #0, PUCCH format 2 allows the position of the subcarrier where the DMRS is transmitted within a single OFDM symbol to be fixed to the subcarriers having indices #1, #4, #7, and #10. The control information can be mapped to the remaining subcarriers, excluding the subcarrier where the DMRS is located, through a modulation process following channel coding.

[0204] To summarize, the settable values ​​and their ranges for each PUCCH format described above can be summarized as shown in [Table 12] below. In [Table 12] below, cases where a value does not need to be set are indicated as NA.

[0205] [Table 12]

[0206]

[0207] Meanwhile, to improve uplink coverage, multi-slot repetition may be supported for PUCCH formats 1, 3, and 4, and PUCCH repetition may be configured per PUCCH format. The terminal may perform repeated transmissions for PUCCH containing UCIs for a number of slots configured via nrofSlots, which is an upper layer signaling. For PUCCH repeated transmissions, the PUCCH transmission for each slot is performed using the same number of consecutive symbols, and the corresponding number of consecutive symbols can be configured via nrofSymbols within PUCCH-format1, PUCCH-format3, or PUCCH-format4, which is an upper layer signaling. For PUCCH repeated transmissions, the PUCCH transmission for each slot is performed using the same starting symbol, and the corresponding starting symbol can be configured via startingSymbolIndex within PUCCH-format1, PUCCH-format3, or PUCCH-format4, which is an upper layer signaling. For PUCCH repeated transmissions, a single PUCCH-spatialRelationInfo can be configured for a single PUCCH resource. For PUCCH repeated transmissions, if the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the terminal can perform frequency hopping on a slot-by-slot basis. Additionally, if the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the terminal can start PUCCH transmission from the first PRB index configured via the upper layer signaling 'startingPRB' in even-numbered slots, and start PUCCH transmission from the second PRB index configured via the upper layer signaling 'secondHopPRB' in odd-numbered slots.Additionally, if the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the index of the slot in which the first PUCCH transmission is directed to the terminal is 0, and the PUCCH repeat count value may be incremented regardless of whether PUCCH transmission is performed in each slot during the total configured PUCCH repeat transmission count. If the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the terminal does not expect frequency hopping within the slot to be configured during PUCCH transmission. If the terminal is not configured to perform frequency hopping in PUCCH transmissions in different slots but is configured to perform frequency hopping within the slot, the first and second PRB indices may be applied equally within the slot. If the number of uplink symbols available for PUCCH transmission is less than nrofSymbols configured in the upper layer signaling, the terminal may not transmit PUCCH. Even if the terminal fails to perform a PUCCH transmission in any slot for any reason during a PUCCH repeat transmission, the terminal can increase the number of PUCCH repeat transmissions.

[0208] In NR Release 17, the number of slots for repeated transmission for each PUCCH resource can be set via the upper layer signaling pucch-RepetitionNrofSlots-r17 within PUCCH-ResourceExt, which is an extension of PUCCH-Resource, an upper layer signaling for PUCCH resources. If the upper layer signaling pucch-RepetitionNrofSlots-r17 is set, the corresponding PUCCH resource is scheduled, and the upper layer signaling nrofSlots is also set, the terminal determines the number of slots for repeated transmission of the corresponding PUCCH resource via pucch-RepetitionNrofSlots-r17 and ignores the upper layer signaling nrofSlots.

[0209] [PUCCH: Regarding transmission power]

[0210] In one embodiment of the present disclosure, a method is described in which a terminal sets and transmits the transmission power of the uplink control channel when transmitting uplink control information through the uplink control channel (PUCCH; Physical Uplink Control Channel) in response to a power control command received from a base station. The uplink control channel transmission power (P) of the terminal is set together with the PUCCH power control adjustment state corresponding to the i-th transmission unit and closed-loop index l. PUCCH ) can be determined as shown in the following [Equation 1], which is expressed in dBm units. In the following [Equation 1], if the terminal supports multiple carrier frequencies in multiple cells, each parameter can be determined separately for the primary cell c, the carrier frequency f, and the bandwidth part b, and can be distinguished by indices b, f, and c.

[0211] [Mathematical Formula 1]

[0212]

[0213] : The maximum transmission power available to the terminal in the i-th transmission unit, determined by the terminal's power class, parameters activated from the base station, and various parameters built into the terminal.

[0214] : Is and It can be composed of the sum of. It is set to a cell-specific value via p0-nominal, which is cell-specific upper-layer signaling, and if such a setting does not exist It can be 0 dBm. is set to a terminal-specific value through the p0-PUCCH-Value within the p0-PUCCH, which is an upper layer signaling in the primary cell c, bandwidth part b, carrier frequency f, and, is greater than or equal to 0 and It can be a smaller value, Is It can represent the size of the set of values ​​and can be set through the upper layer signaling maxNrofPUCCH-P0-PerSet. The set of values ​​can be configured through the upper-layer signaling p0-Set, and if such a configuration does not exist It can be considered as =0.

[0215] - : Subcarrier spacing configuration value

[0216] - : Bandwidth part b, carrier frequency f, and the amount of resources used in the i-th PUCCH transmission unit within the primary cell c (e.g., the number of Resource Blocks (RBs) used for PUCCH transmission in the frequency axis) can be represented.

[0217] - : As pathloss representing the path loss between the base station and the terminal, the terminal uses the Reference Signal (RS) resource signaled by the base station Path loss is calculated from the difference between the transmission power and the terminal received signal level of the reference signal.

[0218] - : For PUCCH format 0, if the upper layer signaling deltaF-PUCCH-f0 is set, the corresponding value is used; for PUCCH format 1, if the upper layer signaling deltaF-PUCCH-f1 is set, the corresponding value is used; for PUCCH format 2, if the upper layer signaling deltaF-PUCCH-f2 is set, the corresponding value is used; for PUCCH format 3, if the upper layer signaling deltaF-PUCCH-f3 is set, the corresponding value is used; for PUCCH format 4, if the upper layer signaling deltaF-PUCCH-f4 is set, the corresponding value is used; and for all PUCCH formats, if the upper layer signaling is not set, 0 may be used.

[0219] - : As a PUCCH transmission power adjustment factor within the bandwidth part b, carrier frequency f, and primary cell c, different calculation methods can be used depending on the PUCCH format.

[0220] - : This may refer to the PUCCH power control adjustment status value for the i-th PUCCH transmission unit corresponding to the closed-loop index l within the primary cell, with bandwidth part b, carrier frequency f. Here, the closed-loop power adjustment for PUCCH transmission may use an accumulation method that applies values ​​instructed by the TPC command by accumulating them.

[0221] PUCCH power control adjustment status It can be determined through bandwidth part b, carrier frequency f, primary cell c, i-th transmission unit, and closed-loop index l.

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

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

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

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

[0226] If the terminal obtains a TPC command value from the TPC command field included in DCI format 2_2 that is transmitted along with a CRC scrambled in TPC-PUCCH-RNTI, it can obtain a value based on the closed-loop index field included in the DCI format 2_2.

[0227] - PUCCH power control regulation state for the i-th PUCCH transmission unit corresponding to the closed-loop index l within the primary cell, bandwidth part b, carrier frequency f. It can be calculated as in [Equation 2].

[0228] [Mathematical Formula 2]

[0229]

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

[0231] ○ is a specific set of the aforementioned TPC command values for all transmission units corresponding within It can mean the sum of. At this time is a set It can mean the number of all elements belonging to it. can mean a set of DCIs containing all TPC command values ​​to perform TPC command accumulation operations for the i-th PUCCH transmission unit. To determine, define a start point and an end point in the time dimension, and all DCIs received by the terminal within the two points It can be included as an element of.

[0232] ● The end point for determining is from the start symbol of the i-th PUCCH transmission unit. It could be a previous point as much as the symbol.

[0233] ● The starting point for determining is from the start symbol of the i-i0th PUCCH transmission unit. It can be a point earlier by a number of symbols. In this case, the positive integer i0 is the above The end point for determining (from the start symbol of the i-th PUCCH transmission unit) From the start symbol of the i-i0th PUCCH transmission unit compared to the point (previous by a number of symbols) The time point that was earlier by the symbol can be determined as the smallest value that satisfies the condition that it is an earlier point in time.

[0234] ● For example, The end point for determining can be defined as sym(i), and from the start symbol of the i-i0th PUCCH transmission unit If a time point earlier by a number of symbols can be defined as sym(i - i0), then if sym(i) = sym(i-1) > sym(i-2) > sym(i-3) holds, then i0 can be determined as 2.

[0235] [PUSCH: Regarding transmission method]

[0236] Next, the scheduling method for PUSCH transfers is described. PUSCH transfers can be dynamically scheduled by UL grants within the DCI, or operated by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transfers can be provided in DCI format 0_0 or 0_1.

[0237] Configured grant Type 1 PUSCH transmissions can be configured semi-statically by receiving configuredGrantConfig, which includes rrc-ConfiguredUplinkGrant from [Table 13], through the upper signaling, without receiving UL grants within the DCI. Configured grant Type 2 PUSCH transmissions can be semi-continuously scheduled by UL grants within the DCI after receiving configuredGrantConfig, which does not include rrc-ConfiguredUplinkGrant from [Table 13], through the upper signaling. When a PUSCH transmission is operated by a configured grant, the parameters applied to the PUSCH transmission are applied through configuredGrantConfig, the upper signaling of [Table 13], with the exception of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH, which are provided by pusch-Config, the upper signaling of [Table 14]. If the terminal is provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 13], the terminal applies tp-pi2BPSK in pusch-Config of [Table 14] to PUSCH transmissions operated by the configured grant.

[0238] [Table 13]

[0239]

[0240]

[0241]

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

[0243] As described above, PUSCH transmissions can be dynamically scheduled via DCI format 0_0 or 0_1 and semi-statically configured by a configured grant. If a terminal is instructed to schedule a PUSCH transmission via DCI format 0_0, the terminal performs beam configuration for the PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the terminal-specific PUCCH resource corresponding to the minimum ID within the active uplink BWP in the serving cell, wherein the PUSCH transmission is based on a single antenna port. The terminal does not expect scheduling for the PUSCH transmission via DCI format 0_0 within a BWP where the PUCCH resource containing pucch-spatialRelationInfo is not configured. If the terminal is not configured with txConfig within pusch-Config of [Table 14], the terminal does not expect to be scheduled via DCI format 0_1.

[0244] [Table 14]

[0245]

[0246]

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

[0248] In this case, the SRI can be provided via the SRS resource indicator field within the DCI or configured via the higher-level signaling srs-ResourceIndicator. During codebook-based PUSCH transmission, the terminal receives at least one SRS resource and can receive up to two. When the terminal receives an SRI via the DCI, the SRS resource indicated by that SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing that SRI. Additionally, the TPMI and transmission rank can be provided via the precoding information and number of layers field within the DCI or configured via the higher-level signaling precodingAndNumberOfLayers. The TPMI is used to indicate the precoder applied to the PUSCH transmission. If the terminal receives one SRS resource, the TPMI is used to indicate the precoder to be applied from that one configured SRS resource. If the terminal is configured with multiple SRS resources, TPMI is used to specify the precoder to be applied to the SRS resource indicated by SRI.

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

[0250] A terminal may receive one SRS resource set in which the value of usage in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource within that SRS resource set may be indicated via SRI. If multiple SRS resources are set in the SRS resource set in which the value of usage in the upper signaling SRS-ResourceSet is set to 'codebook', the terminal expects that the value of nrofSRS-Ports in the upper signaling SRS-Resource will be set to the same value for all SRS resources.

[0251] The terminal transmits one or more SRS resources included in an SRS resource set in which the usage value is set to 'codebook' according to the upper signaling to the base station, and the base station selects one of the SRS resources transmitted by the terminal and instructs the terminal to perform PUSCH transmission using the transmit beam information of the corresponding SRS resource. In this case, in codebook-based PUSCH transmission, SRI is used as information to select the index of one SRS resource and is included in the DCI. Additionally, the base station includes information in the DCI that instructs the TPMI and rank to be used by the terminal for PUSCH transmission. The terminal performs PUSCH transmission using the SRS resource instructed by the SRI, by applying the instructed rank and the precoder instructed by the TPMI based on the transmit beam of the corresponding SRS resource.

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

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

[0254] If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS is indicated by the SRS request field in DCI format 0_1 ​​or 1_1. In this case, if the connected NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, the existence of the connected NZP CSI-RS is indicated if the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. In this case, the corresponding DCI must not indicate cross-carrier or cross-BWP scheduling. Additionally, if the value of the SRS request indicates the existence of the NZP CSI-RS, the NZP CSI-RS is located in the slot where the PDCCH containing the SRS request field was transmitted. In this case, the TCI states set on the scheduled subcarrier are not set to QCL-TypeD.

[0255] If a periodic or semi-persistent SRS resource set is established, the associated NZP CSI-RS can be indicated via the associated CSI-RS within the parent signaling SRS-ResourceSet. For non-codebook-based transmissions, the terminal does not expect the parent signaling spatialRelationInfo for the SRS resource and the associated CSI-RS within the parent signaling SRS-ResourceSet to be established together.

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

[0257] The base station transmits one NZP-CSI-RS associated with an SRS resource set to the terminal, and the terminal calculates a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the results measured upon receiving the NZP-CSI-RS. When the terminal transmits one or more SRS resources within an SRS resource set where usage is set to 'nonCodebook' to the base station, it applies the calculated precoder, and the base station selects one or more SRS resources from among the received one or more SRS resources. At this time, in non-codebook-based PUSCH transmission, the SRI represents an index capable of expressing a combination of one or more SRS resources, and the SRI is included within the DCI. At this time, the number of SRS resources indicated by the SRI transmitted by the base station may be the number of transmission layers of the PUSCH, and the terminal transmits the PUSCH by applying the precoder applied for SRS resource transmission to each layer.

[0258] [PUSCH: Regarding transmission power]

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

[0260] [Mathematical Formula 3]

[0261]

[0262] : The maximum transmission power available to the terminal in the i-th transmission unit, determined by the terminal's power class, parameters activated from the base station, and various parameters built into the terminal.

[0263] : Is and It consists of the sum of is configured to the terminal with cell-specific upper-layer signaling, and is a value set to terminal-specific upper layer signaling. Here, when j=0, it means PUSCH to transmit msg3; when j=1, it means configured grant PUSCH; and if j={2, ..., J-1}, it means grant PUSCH.

[0264] - : Subcarrier spacing configuration value

[0265] - : Can refer to the amount of resources used in the i-th PUSCH transmission unit (e.g., the number of Resource Blocks (RBs) used for PUSCH transmission in the frequency axis).

[0266] - It refers to a value used to compensate for path loss that can be determined through upper-layer settings and the SRI (SRS Resource Indicator) (in the case of dynamic grant PUSCH).

[0267] - : As pathloss representing the path loss between the base station and the terminal, the terminal uses the Reference Signal (RS) resource signaled by the base station Pathloss is calculated from the difference between the transmitted power and the terminal received signal level of the reference signal. The reference signal index is It refers to the estimated downlink path loss estimated by the terminal through the reference signal, and the reference signal index The terminal can determine this through upper layer settings and SRI (in the case of dynamic grant PUSCH or ConfiguredGrantConfig-based configured grant PUSCH (type 2 configured grant PUSCH) that does not include upper layer settings rrc-ConfiguredUplinkGrant) or through upper layer settings.

[0268] - : It refers to a value determined by the format of the information transmitted via MCS (Modulation Coding Scheme) and PUSCH (TF: transport format, e.g., whether UL-SCH is included or CSI is included, etc.).

[0269] - : This refers to the value for the closed-loop index l, which can be determined by the upper layer setting and SRI for PUSCH, as the closed-loop power control adjustment value. Here, closed-loop power adjustment for PUSCH transmission can be supported by dividing it into an accumulation method, which applies the value indicated by the TPC command by accumulating it, and an absolute method, which applies the value indicated by the TPC command directly; this can be determined based on whether the upper layer parameter tpc-Accumulation is set. If the upper layer parameter tpc-Accumulation is set to disabled, closed-loop power adjustment for PUSCH transmission is performed using the absolute method, and if tpc-Accumulation is not set, closed-loop power adjustment for PUSCH transmission is performed using the accumulation method.

[0270] PUSCH power control adjustment status It can be determined through bandwidth part b, carrier frequency f, cell c, i-th transmission unit, and closed-loop index l.

[0271] - : In the band part b, carrier frequency f, cell c, the value indicated by the TPC command field included in DCI format 0_0, 0_1, or 0_2 that schedules the i-th PUSCH transmission unit corresponding to the closed loop index l, or the value indicated by the TPC command field included in DCI format 2_2 that is transmitted with a CRC scrambled with TPC-PUSCH-RNTI.

[0272] ○ If the terminal is set to twoPUSCH-PC-AdjustmentStates, which is an upper layer signaling, the closed loop index l can have a value of 0 or 1.

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

[0274] ● If the terminal receives the upper layer signaling ConfiguredGrantConfig and performs a PUSCH transmission or retransmission for it, the closed loop index l may follow the upper layer signaling powerControlLoopToUse value.

[0275] ● If the terminal has received the upper layer signaling SRI-PUSCH-PowerControl, the terminal can obtain the connection between the value indicated by the SRI (SRS resource indicator) field within the DCI format that scheduled the PUSCH transmission and the closed loop index l established through the upper layer signaling sri-PUSCH-ClosedLoopIndex, and can determine the closed loop index l based on the value indicated by the SRI field within the DCI format based on the corresponding connection.

[0276] ● If the terminal has been scheduled to send a PUSCH transmission based on a DCI format that does not include an SRI field, or has not been set to SRI-PUSCH-PowerControl, which is an upper layer signaling, the terminal may consider the closed-loop index l to be 0.

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

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

[0279] [Mathematical Formula 4]

[0280]

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

[0282] ○ is a specific set of the aforementioned TPC command values for all transmission units corresponding within It can mean the sum of. At this time is a set It can mean the number of all elements belonging to it. can mean a set of DCIs containing all TPC command values ​​to perform TPC command accumulation operations for the i-th PUSCH transmission unit. To determine, define a start point and an end point in the time dimension, and all DCIs received by the terminal within the two points It can be included as an element of.

[0283] ● The end point for determining is from the start symbol of the i-th PUSCH transmission unit. It could be a previous point as much as the symbol.

[0284] ● The starting point for determining is From the start symbol of the nth PUSCH transmission unit It can be a point earlier by a number of symbols. In this case, a positive integer The above The end point for determining (from the start symbol of the i-th PUSCH transmission unit) Compared to the previous point by the symbol, From the start symbol of the nth PUSCH transmission unit It can be determined as the smallest value that satisfies the condition that the time point prior by the symbol becomes an earlier point in time.

[0285] ● For example, The endpoint for determining can be defined as sym(i), and From the start symbol of the nth PUSCH transmission unit sym( If it can be defined as ), then if sym(i) = sym(i-1) > sym(i-2) > sym(i-3) holds, then i0 can be determined as 2.

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

[0287] [Mathematical Formula 5]

[0288]

[0289] ○ may be a value indicated by the TPC command field included in DCI format 0_0, 0_1, or 0_2 for scheduling the i-th PUSCH transmission unit corresponding to the closed-loop index l within bandwidth part b, carrier frequency f, and cell c as described above, or a value indicated by the TPC command field included in DCI format 2_2 transmitted together with a CRC scrambled by TPC-PUSCH-RNTI. If TPC command accumulation operation is not possible, The value may have a corresponding value in [dB] units depending on the value indicated by the TPC command field included within the DCI format 0_0, 0_1, 0_2, or 2_2, as shown in [Table 15] below. For example, if the value of the TPC command field is 0, It can have a value of -4 dB.

[0290] [Table 15]

[0291]

[0292] [Regarding SRS]

[0293] Next, a method for estimating the uplink channel using the transmission of the terminal's Sounding Reference Signal (SRS) is described. To transmit configuration information for SRS transmission to the terminal, the base station may set at least one SRS configuration for each uplink BWP, and may also set at least one SRS resource set for each SRS configuration. For example, the base station and the terminal may exchange upper-level signaling information as follows to transmit information regarding the SRS resource set.

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

[0295] - srs-ResourceIdList: A set of SRS resource indices referenced by the SRS resource set

[0296] - resourceType: This is the time-axis transmission setting for the SRS resource referenced in the SRS resource set, and can be set to one of 'periodic', 'semi-persistent', or 'aperiodic'. If set to 'periodic' or 'semi-persistent', associated CSI-RS information may be provided depending on the usage of the SRS resource set. If set to 'aperiodic', a non-periodic SRS resource trigger list and slot offset information may be provided, and associated CSI-RS information may be provided depending on the usage of the SRS resource set.

[0297] - usage: A setting regarding the usage of the SRS resource referenced in the SRS resource set, which can be set to one of 'beamManagement', 'codebook', 'nonCodebook', or 'antennaSwitching'.

[0298] - alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter settings for controlling the transmit power of the SRS resource referenced in the SRS resource set.

[0299] The terminal can understand that the SRS resources included in the set of SRS resource indices referenced in the SRS resource set follow the information set in the SRS resource set.

[0300] Additionally, the base station and the terminal may transmit and receive upper-layer signaling information to convey individual configuration information for the SRS resource. For example, the individual configuration information for the SRS resource may include time-frequency axis mapping information within the slot of the SRS resource, which may include information regarding frequency hopping within or between slots of the SRS resource. Furthermore, the individual configuration information for the SRS resource may include the time-axis transmission setting of the SRS resource, which may be set to one of 'periodic', 'semi-persistent', or 'aperiodic'. This may be restricted to having the same time-axis transmission setting as the SRS resource set containing the SRS resource. If the time-axis transmission setting of the SRS resource is set to 'periodic' or 'semi-persistent', the SRS resource transmission period and slot offset (e.g., periodicityAndOffset) may additionally be included in the time-axis transmission setting.

[0301] A base station may enable, deactivate, or trigger SRS transmission to a terminal via upper-layer signaling, including RRC signaling or MAC CE signaling, or L1 signaling (e.g., DCI). For example, a base station may enable or deactivate periodic SRS transmission to a terminal via upper-layer signaling. A base station may instruct a terminal to activate an SRS resource set with resourceType set to periodic via upper-layer signaling, and the terminal may transmit an SRS resource referenced in the activated SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, follows the periodicityAndOffset set in the SRS resource. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to associated CSI-RS information set in the SRS resource set containing the SRS resource. The terminal can transmit an SRS resource within an active uplink BWP for a periodic SRS resource activated through upper layer signaling.

[0302] For example, a base station can enable or disable semi-persistent SRS transmission to a terminal via upper-layer signaling. The base station can instruct the terminal to enable an SRS resource set via MAC CE signaling, and the terminal can transmit an SRS resource referenced in the enabled SRS resource set. The SRS resource set enabled via MAC CE signaling may be limited to an SRS resource set where resourceType is set to semi-persistent. The time-frequency axis resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, follows the periodicityAndOffset set in the SRS resource. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to associated CSI-RS information set in the SRS resource set containing the SRS resource. If spatial relation info is configured in the SRS resource, the spatial domain transmission filter can be determined by referring to the configuration information regarding the spatial relation info transmitted via MAC CE signaling that enables semi-persistent SRS transmission without following it. The terminal can transmit the SRS resource within the uplink BWP enabled for the semi-persistent SRS resource activated via upper layer signaling.

[0303] For example, a base station can trigger an aperiodic SRS transmission to a terminal via the DCI. The base station can specify one of the aperiodic SRS resource triggers (aperiodicSRS-ResourceTrigger) through the SRS request field of the DCI. The terminal can understand that among the configuration information of the SRS resource set, an SRS resource set containing the aperiodic SRS resource trigger specified via the DCI from the list of aperiodic SRS resource triggers has been triggered. The terminal can transmit the SRS resource referenced in the triggered SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource. Additionally, the slot mapping of the transmitted SRS resource can be determined through the slot offset between the PDCCH containing the DCI and the SRS resource, which can refer to the value(s) included in the set of slot offsets set in the SRS resource set. Specifically, the slot offset between the PDCCH containing the DCI and the SRS resource may be the value specified in the time domain resource assignment field of the DCI among the offset value(s) included in the slot offset set configured in the SRS resource set. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to the spatial relation info configured in the SRS resource, or may refer to the associated CSI-RS information configured in the SRS resource set containing the SRS resource. The terminal may transmit the SRS resource within an uplink BWP that is enabled for a non-periodic SRS resource triggered via the DCI.

[0304] When a base station triggers aperiodic SRS transmission to a terminal via DCI, a minimum time interval may be required between the PDCCH containing the DCI triggering the aperiodic SRS transmission and the transmitted SRS so that the terminal can apply configuration information for the SRS resource and transmit the SRS. The time interval for the terminal's SRS transmission can 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 mapped to the first transmitted SRS resource(s). The minimum time interval can be determined by referencing the PUSCH preparation procedure time required for the terminal to prepare for PUSCH transmission. Additionally, the minimum time interval may have different values ​​depending on the usage of the SRS resource set containing the transmitted SRS resource. For example, the minimum time interval can be determined by N2 symbols defined by considering the terminal's processing capability based on the terminal's capability, referencing the terminal's PUSCH preparation procedure time. Additionally, considering the usage of the SRS resource set including the transmitted SRS resource, if the usage of the SRS resource set is set to 'codebook' or 'antennaSwitching', the minimum time interval can be set to N2 symbols, and if the usage of the SRS resource set is set to 'nonCodebook' or 'beamManagement', the minimum time interval can be set to N2+14 symbols.The terminal transmits an aperiodic SRS when the time interval for the aperiodic SRS transmission is greater than or equal to the minimum time interval, and can ignore the DCI that triggers the aperiodic SRS when the time interval for the aperiodic SRS transmission is less than the minimum time interval.

[0305] [Table 16]

[0306]

[0307]

[0308] The spatialRelationInfo setting information in [Table 16] above is intended to apply the beam information of a reference signal to the beam used for SRS transmission by referencing a single reference signal. For example, the spatialRelationInfo setting may include information such as that shown in [Table 17] below.

[0309] [Table 17]

[0310]

[0311] Referring to the spatialRelationInfo setting above, the index of the reference signal to be referenced in order to use the beam information of a specific reference signal can be set as the SS / PBCH (synchronization signal / physical broadcast channel) block (or SSB, synchronization signal block) index, CSI-RS index, or SRS index. The upper signaling referenceSignal is setting information indicating which reference signal's beam information to reference for the corresponding SRS transmission, and ssb-Index represents the SS / PBCH block index, csi-RS-Index represents the CSI-RS index, and srs represents the SRS index, respectively. If the value of the upper signaling referenceSignal is set to 'ssb-Index', the terminal can apply the receiving beam used when receiving the SS / PBCH block corresponding to ssb-Index as the transmitting beam for the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'csi-RS-Index', the terminal can apply the receiving beam used when receiving the CSI-RS corresponding to csi-RS-Index as the transmitting beam for the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'srs', the terminal can apply the transmitting beam used when transmitting the SRS corresponding to srs as the transmitting beam for the corresponding SRS transmission.

[0312] [Regarding SRS transmission power]

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

[0314] [Mathematical Formula 6]

[0315]

[0316] - : The maximum transmission power available to the terminal in the i-th transmission unit, determined by the terminal's power class, parameters activated from the base station, and various parameters built into the terminal.

[0317] - : Bandwidth part b, carrier frequency f, and cell c can be set to p0, which is the upper layer signaling, and SRS resource set It can be configured through the upper layer signaling, SRS-ResourceSet and SRS-ResourceSetId.

[0318] - : Subcarrier spacing configuration value

[0319] - : Can refer to the amount of resources used in the i-th SRS transmission unit (e.g., the number of Resource Blocks (RBs) used for SRS transmission in the frequency axis).

[0320] - : Bandwidth part b, carrier frequency f, and cell c can be set to alpha, which is the upper layer signaling, and SRS resource set It can be configured through the upper layer signaling, SRS-ResourceSet and SRS-ResourceSetId.

[0321] - : As pathloss representing the path loss between the base station and the terminal, the terminal uses the Reference Signal (RS) resource signaled by the base station Path loss is calculated from the difference between the transmission power and the terminal received signal level of the reference signal.

[0322] - : Can represent the SRS power control adjustment status value for the i-th SRS transmission unit corresponding to the closed-loop index l within the band part b, carrier frequency f, and cell c.

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

[0324] - If the terminal is configured to have the same power control adjustment state value between SRS transmission and PUSCH transmission via the upper layer signaling srs-PowerControlAdjustmentStates, the SRS power control adjustment state can be represented as shown in [Equation 5] below, and in [Equation 5] may refer to the current PUSCH power control adjustment state. In this case, through the various methods of Example 1 described above It can calculate, and that value It can be used by substituting it into.

[0325] [Mathematical Formula 7]

[0326]

[0327] - If the terminal is not configured for PUSCH transmission in bandwidth part b, carrier frequency f, and cell c, or if it is configured to have separate power control adjustment state values ​​between SRS transmission and PUSCH transmission through the upper layer signaling srs-PowerControlAdjustmentStates and the upper layer signaling tpc-Accumulation is not configured, the SRS power control adjustment state can be represented independently of the closed loop l as shown in [Equation 8] below.

[0328] [Mathematical Formula 8]

[0329]

[0330] - : It may be a value indicated by the TPC command field included in DCI format 2_3, and the value may follow [Table 17] above.

[0331] ○ is a specific set of the aforementioned TPC command values for all transmission units corresponding within It can mean the sum of. At this time is a set It can mean the number of all elements belonging to it. can mean a set of DCIs containing all TPC command values ​​to perform TPC command accumulation operations for the i-th PUSCH transmission unit. To determine, define a start point and an end point in the time dimension, and all DCIs received by the terminal within the two points It can be included as an element of.

[0332] ● The end point for determining is from the start symbol of the i-th SRS transmission unit. It could be a previous point as much as the symbol.

[0333] ● The starting point for determining is from the start symbol of the i-i0th SRS transmission unit. It can be a point earlier by a number of symbols. In this case, the positive integer i0 is the above The end point for determining (from the start symbol of the i-th SRS transmission unit) From the start symbol of the i - i0th SRS transmission unit compared to the point (previous by a number of symbols) It can be determined as the smallest value that satisfies the condition that the time point prior by the symbol becomes an earlier point in time.

[0334] ● For example, The end point for determining can be defined as sym(i), and from the start symbol of the i-i0th SRS transmission unit If a time point earlier by a number of symbols can be defined as sym(i - i0), then if sym(i) = sym(i - 1) > sym(i - 2) > sym(i - 3) holds, then i0 can be determined as 2.

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

[0336] [Mathematical Formula 9]

[0337]

[0338] ○ As described above, within bandwidth part b, carrier frequency f, and cell c, it may be a value indicated by the TPC command field included in DCI format 2_3, and the value may follow [Table 15] above. For example, if the value of the TPC command field is 0, It can have a value of -4 dB.

[0339] [Regarding Terminal Capability Reporting]

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

[0341] A base station may transmit a UE capability enquiry message requesting capability reporting to a connected terminal. The message may include a request for terminal capability specific to the base station's RAT (radio access technology) type. The request for each RAT type may include information such as supported frequency band combinations. Furthermore, in the case of the UE capability enquiry message, multiple UE capabilities for each RAT type may be requested through a single RRC message container transmitted by the base station, or the base station may transmit the UE capability enquiry message, which includes the request for each RAT type, to the terminal multiple times. That is, the UE capability inquiry may be repeated multiple times within a single message, and the terminal may construct and report the corresponding UE capability information message multiple times. In next-generation mobile communication systems, UE capability requests can be made for NR, LTE, EN-DC (E-UTRA - NR dual connectivity), and MR-DC (Multi-RAT dual connectivity). Additionally, while the UE capability enquiry message is generally transmitted initially after the terminal connects with the base station, the base station may request it under any conditions when necessary.

[0342] In the above step, the terminal that receives a request for a UE capability report from the base station configures the terminal capability according to the RAT type and band information requested from the base station. The method by which the terminal configures the UE capability in the NR system is summarized below.

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

[0344] 2. If the base station requests a UE capability report by setting the “eutra-nr-only” flag or the “eutra” flag, the terminal completely removes NR SA BCs from the above-mentioned list of configured BC candidates. This operation may occur only when the LTE base station (eNB) requests the “eutra” capability.

[0345] 3. Subsequently, the terminal removes fallback BCs from the candidate list of BCs configured in the above step. Here, a fallback BC refers to a BC that can be obtained by removing a band corresponding to at least one SCell from any BC; this step can be omitted because the BC before removing the band corresponding to at least one SCell already covers the fallback BC. This step applies to MR-DC as well, meaning it applies to LTE bands. The BCs remaining after this step constitute the final "candidate BC list."

[0346] 4. The terminal selects the BCs to be reported by selecting BCs that match the requested RAT type from the final "Candidate BC List" above. In this step, the terminal constructs the supportedBandCombinationList in a predetermined order. That is, the terminal constructs the BCs and UE capabilities to be reported according to the pre-set order of rat-Type (nr -> eutra-nr -> eutra). Additionally, it constructs a featureSetCombination for the constructed supportedBandCombinationList and constructs a list of "Candidate Feature Set Combinations" from the Candidate BC List from which the list of fallback BCs (containing capabilities of the same or lower level) has been removed. The above "Candidate Feature Set Combinations" include feature set combinations for both NR and EUTRA-NR BCs and can be obtained from the feature set combinations of the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0347] 5. Additionally, if the requested rat Type is eutra-nr and has an influence, featureSetCombinations is included in both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, the NR feature set is included only in UE-NR-Capabilities.

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

[0349] [Regarding NC-JT]

[0350] According to one embodiment of the present disclosure, non-coherent joint transmission (NC-JT) may be used for a terminal to receive PDSCH from a plurality of TRPs.

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

[0352] Joint Transmission (JT) is a representative transmission technology for the aforementioned cooperative communication that increases the signal strength or throughput received by a terminal by transmitting signals to a single terminal through multiple different cells, TRPs, and / or beams. In this case, the characteristics of the channels between each cell, TRP, or / or beam and the terminal may differ significantly. In particular, in the case of Non-Coherent Joint Transmission (NC-JT), which supports non-coherent precoding between each cell, TRP, or / or beam, individual precoding, MCS, resource allocation, TCI instructions, etc., may be required depending on the link-specific channel characteristics between each cell, TRP, or / or beam and the terminal.

[0353] The aforementioned NC-JT transmission may be applied to at least one of the downlink data channel (PDSCH), downlink control channel (PDCCH), uplink data channel (PUSCH), and uplink control channel (PUCCH). During PDSCH transmission, transmission information such as precoding, MCS, resource allocation, and TCI is indicated as DL DCI, and for NC-JT transmission, said transmission information must be indicated independently by cell, TRP, and / or beam. This is a major factor in increasing the payload required for DL ​​DCI transmission, which can adversely affect the reception performance of the PDCCH transmitting DCI. Therefore, to support JT in PDSCH, it is necessary to carefully design the tradeoff between the amount of DCI information and the reception performance of control information.

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

[0355] Referring to Fig. 8, examples for PDSCH transmission are described according to the Joint Transmission (JT) technique, and examples for allocating radio resources by TRP are illustrated.

[0356] Referring to FIG. 8, an example (800) of a Coherent Joint Transmission (C-JT) that supports coherent precoding between each cell, TRP or / and beam is shown.

[0357] In the case of C-JT, TRP A (805) and TRP B (810) transmit a single data (PDSCH) to the terminal (815), and joint precoding can be performed in multiple TRPs. This may mean that DMRS is transmitted through the same DMRS ports for TRP A (805) and TRP B (810) to transmit the same PDSCH. For example, TRP A (805) and TRP B (810) each can transmit DRMS ​​to the terminal through DMRS port A and DMRS B. In this case, the terminal can receive one DCI information for receiving a single PDSCH that is demodulated based on the DMRS transmitted through DMRS port A and DMRS B.

[0358] FIG. 8 shows an example (820) of Non-Coherent Joint Transmission (NC-JT) that supports non-coherent precoding between each cell, TRP or / and beam for PDSCH transmission.

[0359] In the case of NC-JT, a PDSCH is transmitted to the terminal (835) for each cell, TRP or / and beam, and individual precoding may be applied to each PDSCH. Each cell, TRP or / and beam can transmit a different PDSCH or a different PDSCH layer to the terminal to improve throughput compared to single cell, TRP or / and beam transmission. Additionally, each cell, TRP or / and beam can repeatedly transmit the same PDSCH to the terminal to improve reliability compared to single cell, TRP or / and beam transmission. For convenience of explanation, the cell, TRP or / and beam is collectively referred to as TRP below.

[0360] At this time, various wireless resource allocations may be considered, such as when the frequency and time resources used by multiple TRPs for PDSCH transmission are all the same (840), when the frequency and time resources used by multiple TRPs do not overlap at all (845), or when some of the frequency and time resources used by multiple TRPs overlap (850).

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

[0362] FIG. 9 is a diagram illustrating an example of the configuration of downlink control information (DCI) for NC-JT in which each TRP transmits different PDSCH or different PDSCH layers to a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0363] Referring to FIG. 9, case #1 (900) is an example in which, in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)), and control information for the PDSCHs transmitted from the (N-1) additional TRPs is transmitted independently of the control information for the PDSCH transmitted from the serving TRP. That is, the terminal can obtain control information for the PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through independent DCIs (DCI#0 to DCI#(N-1)). The formats between the independent DCIs may be the same or different from each other, and the payloads between the DCIs may also be the same or different from each other. In the aforementioned case #1, the degrees of freedom for each PDSCH control or allocation can be fully guaranteed, but if each DCI is transmitted from different TRPs, coverage differences per DCI may occur, which may degrade reception performance.

[0364] Case #2 (905) shows an example in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, and control information (DCI) for the PDSCHs of the (N-1) additional TRPs is transmitted to each, and each of these DCIs is dependent on the control information for the PDSCH transmitted from the serving TRP.

[0365] For example, DCI#0, which is control information for PDSCH transmitted from a serving TRP (TRP#0), includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, but shortened DCI (hereinafter sDCI) (sDCI#0 to sDCI#(N-2)), which is control information for PDSCH transmitted from cooperative TRPs (TRP#1 to TRP#(N-1)), may include only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. Therefore, in the case of sDCI transmitting control information for PDSCH transmitted from cooperative TRPs, since the payload is smaller compared to normal DCI (nDCI) transmitting PDSCH-related control information transmitted from a serving TRP, it is possible to include reserved bits compared to nDCI.

[0366] In the aforementioned case #2, the degree of freedom for each PDSCH control or allocation may be limited depending on the content of the information elements included in sDCI, but since the receiving performance of sDCI becomes superior to that of nDCI, the probability of coverage difference between DCIs occurring may be reduced.

[0367] Case #3 (910) illustrates an example in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for a single PDSCH transmission, and a single control information for the PDSCHs of the (N-1) additional TRPs is transmitted, and this DCI is dependent on the control information for the PDSCH transmitted from the serving TRP.

[0368] For example, DCI#0, which is control information for a PDSCH transmitted from a serving TRP (TRP#0), includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, and for control information for PDSCHs transmitted from cooperative TRPs (TRP#1 to TRP#(N-1)), it is possible to collect and transmit only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 into a single 'secondary' DCI (sDCI). For example, the sDCI may include at least one piece of HARQ-related information such as frequency domain resource assignment, time domain resource assignment, and MCS of cooperative TRPs. In addition, for information not included in sDCI, such as BWP (bandwidth part) indicators or carrier indicators, the DCI of the serving TRP (DCI#0, normal DCI, nDCI) may be followed.

[0369] In case #3 (910), the degree of freedom for each PDSCH control or allocation may be limited depending on the content of the information element included in the sDCI, but the reception performance of the sDCI can be adjusted, and the complexity of the terminal's DCI blind decoding can be reduced compared to case #1 (900) or case #2 (905).

[0370] Case #4 (915) is an example in which, in a situation where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, control information for the PDSCHs transmitted from the (N-1) additional TRPs is transmitted in the same DCI (Long DCI) as the control information for the PDSCH transmitted from the serving TRP. That is, the terminal can obtain control information for the PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In the case of Case #4 (915), the complexity of the terminal's DCI blind decoding may not increase, but the freedom of PDSCH control or allocation may be low, such as when the number of cooperating TRPs is limited by the long DCI payload limit.

[0371] In the following descriptions and embodiments, sDCI may refer to various auxiliary DCIs, such as shortened DCI, secondary DCI, or normal DCI (DCI formats 1_0 to 1_1 described above) containing PDSCH control information transmitted from a cooperative TRP, and unless a specific limitation is specified, such description may be similarly applied to the various auxiliary DCIs.

[0372] In the following description and embodiments, the aforementioned cases #1 (900), #2 (905), and #3 (910), in which one or more DCIs (PDCCHs) are used to support NC-JT, may be classified as multiple PDCCH-based NC-JT, and the aforementioned case #4 (915), in which a single DCI (PDCCH) is used to support NC-JT, may be classified as single PDCCH-based NC-JT. In PDCCH transmission based on multiple PDCCHs, a CORESET in which the DCI of the serving TRP (TRP#0) is scheduled and a CORESET in which the DCIs of the cooperating TRPs (TRP#1 to TRP#(N-1)) are scheduled may be distinguished. Methods for distinguishing the CORESETs may include distinguishing them through upper layer indicators for each CORESET, or distinguishing them through beam settings for each CORESET. In addition, in a single PDCCH-based NC-JT, instead of a single DCI scheduling multiple PDSCHs, a single PDSCH having multiple layers is scheduled, and the aforementioned multiple layers can be transmitted from multiple TRPs. In this case, the connection relationship between a layer and the TRP transmitting that layer can be indicated through a TCI (Transmission Configuration Indicator) indication for the layer.

[0373] In the embodiments of the present disclosure, "cooperative TRP" may be replaced with various terms such as "cooperative panel" or "cooperative beam" in actual application.

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

[0375] In the present disclosure, the wireless protocol structure for NC-JT can be used in various ways depending on the TRP deployment scenario. For example, when there is no or small backhaul delay between cooperative TRPs, a method using a structure based on MAC layer multiplexing similar to S10 in FIG. 4 (CA-like method) is possible. On the other hand, when the backhaul delay between cooperative TRPs is large enough to be negligible (e.g., when more than 2 ms is required for information exchange such as CSI, scheduling, and HARQ-ACK between cooperative TRPs), a method using a structure independent of each TRP from the RLC layer to secure delay-robust characteristics (DC-like method) is possible, similar to S20 in FIG. 4.

[0376] A terminal supporting C-JT and / or NC-JT can receive C-JT and / or NC-JT related parameters or setting values, etc., from the upper layer configuration and set the terminal's RRC parameters based on this. For the upper layer configuration, the terminal can utilize UE capability parameters, for example, tci-StatePDSCH. Here, UE capability parameters, for example, tci-StatePDSCH, can define TCI states for the purpose of PDSCH transmission, and the number of TCI states can be set to 4, 8, 16, 32, 64, or 128 in FR1, and to 64 or 128 in FR2. Among the set number, up to 8 states can be set, which can be indicated by the 3 bits of the TCI field of the DCI via a MAC CE message. The maximum value 128 refers to the value indicated by maxNumberConfiguredTCIstatesPerCC within the tci-StatePDSCH parameter included in the terminal's capability signaling. In this way, a series of configuration processes from upper layer configuration to MAC CE configuration can be applied to beamforming instructions or beamforming change commands for at least one PDSCH in one TRP.

[0377] [Multi-DCI-based Multi-TRP]

[0378] As an embodiment of the present disclosure, a multi-DCI-based multi-TRP transmission method is described. The multi-DCI-based multi-TRP transmission method can establish a downlink control channel for NC-JT transmission based on a multi-PDCCH.

[0379] In NC-JT based on multiple PDCCH, when transmitting DCI for the PDSCH schedule of each TRP, a CORESET or search space separate for each TRP may be provided. The CORESET or search space per TRP can be configured as in at least one of the following cases.

[0380] * Setting the upper layer index per CORESET: The CORESET setting information configured as the upper layer may include an index value, and the TRP transmitting the PDCCH from the corresponding CORESET can be distinguished by the configured CORESET-specific index value. That is, in a set of CORESETs with the same upper layer index value, it can be assumed that the same TRP transmits the PDCCH, or that a PDCCH scheduling the PDCCH of the same TRP is transmitted. The aforementioned CORESET-specific index may be named as CORESETPoolIndex, and for CORESETs with the same CORESETPoolIndex value configured, it can be assumed that the PDCCH is transmitted from the same TRP. For a CORESET where the CORESETPoolIndex value is not configured, it can be assumed that the default value of CORESETPoolIndex is configured, and the aforementioned default value may be 0.

[0381] ** In the present disclosure, if the type of CORESETPoolIndex that each of the multiple CORESETs included in the upper layer signaling PDCCH-Config has exceeds one, that is, if each CORESET has a different CORESETPoolIndex, the terminal may consider that the base station can use a multi-DCI-based multi-TRP transmission method.

[0382] ** In contrast, in the present disclosure, if there is only one type of CORESETPoolIndex that each of the multiple CORESETs included in the upper layer signaling PDCCH-Config has, that is, if all CORESETs have the same CORESETPoolIndex of 0 or 1, the terminal may consider that the base station transmits using single-TRP rather than using a multi-DCI-based multi-TRP transmission method.

[0383] * Multiple PDCCH-Config Settings: Multiple PDCCH-Configs are configured within a single BWP, and each PDCCH-Config may include PDCCH settings per TRP. That is, a single PDCCH-Config may contain a list of CORESETs and / or a list of search spaces per TRP, and one or more CORESETs and one or more search spaces included in a single PDCCH-Config may be considered to correspond to a specific TRP.

[0384] * CORESET Beam / Beam Group Configuration: TRPs corresponding to a given CORESET can be distinguished through beams or beam groups configured per CORESET. For example, if the same TCI state is configured for multiple CORESETs, those CORESETs can be considered to be transmitted through the same TRP, or a PDCCH scheduling a PDSCH of the same TRP within that CORESET can be considered to be transmitted.

[0385] * Search Space Beam / Beam Group Configuration: Beams or beam groups are configured for each search space, allowing TRPs to be distinguished by search space. For example, if the same beam / beam group or TCI state is set in multiple search spaces, it can be assumed that the same TRP is transmitting a PDCCH in that search space, or that a PDCCH scheduling the same TRP's PDSCH is being transmitted in that search space.

[0386] As described above, by separating the CORESET or search space by TRP, it is possible to classify PDSCH and HARQ-ACK information for each TRP, which enables the generation of independent HARQ-ACK codebooks and the use of independent PUCCH resources for each TRP.

[0387] The above settings may be independent per cell or per BWP. For example, two different CORESETPoolIndex values ​​may be set for a PCell, while a specific SCell may not have a CORESETPoolIndex value set. In this case, NC-JT transmission may be configured for the PCell, whereas NC-JT transmission may not be configured for the SCell where the CORESETPoolIndex value is not set.

[0388] A PDSCH TCI state activation / deactivation MAC-CE applicable to a multi-DCI-based multi-TRP transmission method may follow FIG. 7 above. If the terminal has not received a CORESETPoolIndex for each of all CORESETs in the upper layer signaling PDCCH-Config, the terminal may ignore the CORESET Pool ID field (755) in the corresponding MAC-CE (750). If the terminal can support a multi-DCI-based multi-TRP transmission method, that is, if the terminal has different CORESETPoolIndexes for each CORESET in the upper layer signaling PDCCH-Config, the terminal may activate the TCI state in the DCI containing the PDCCH transmitted from CORESETs having a CORESETPoolIndex value equal to the value of the CORESET Pool ID field (755) in the corresponding MAC-CE (750). For example, if the value of the CORESET Pool ID field (755) in the MAC-CE (750) is 0, the TCI state in the DCI containing the PDCCH transmitted from the CORESETs with CORESETPoolIndex 0 can follow the activation information of the MAC-CE.

[0389] When a terminal is configured by a base station to use a multi-DCI-based multi-TRP transmission method, that is, when the types of CORESETPoolIndexes possessed by each of the multiple CORESETs included in the upper layer signaling PDCCH-Config exceed one, or when each CORESET has different CORESETPoolIndexes, the terminal can see that the following constraints exist for PDSCHs scheduled from PDCCHs within each CORESET having two different CORESETPoolIndexes.

[0390] 1) When the terminals have PDSCHs indicated from PDCCHs within each CORESET with two different CORESETPoolIndexes that completely or partially overlap, the TCI states indicated from each PDCCH may be applied to different CDM groups. That is, two or more TCI states may not be applied to a single CDM group.

[0391] 2) When the terminal completely or partially overlaps the PDSCHs indicated from the PDCCHs within each CORESET having two different CORESETPoolIndexes, the actual number of front-loaded DMRS symbols, the actual number of additional DMRS symbols, the location of the actual DMRS symbols, and the DMRS type of each PDSCH can be expected not to differ.

[0392] 3) The terminal can expect that the bandwidth portion indicated by the PDCCH in each CORESET having two different CORESETPoolIndexes will be the same and the subcarrier spacing will also be the same.

[0393] 4) The terminal can expect that each PDCCH will fully contain information about the PDSCH scheduled from the PDCCH within each CORESET having two different CORESETPoolIndexes.

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

[0395] As an embodiment of the present disclosure, a single-DCI-based multi-TRP transmission method is described. The single-DCI-based multi-TRP transmission method can establish a downlink control channel for NC-JT transmission based on a single-PDCCH.

[0396] In a single DCI-based multi-TRP transmission method, a PDSCH transmitted by multiple TRPs can be scheduled using a single DCI. In this case, the number of TCI states can be used as a method to indicate the number of TRPs transmitting the PDSCH. That is, if the number of TCI states indicated in the DCI scheduling the PDSCH is 2, it can be considered as single PDCCH-based NC-JT transmission, and if the number of TCI states is 1, it can be considered as single-TRP transmission. The TCI states indicated in the above-mentioned DCI may correspond to one or two TCI states among the TCI states activated by MAC-CE. When the TCI states of the DCI correspond to two TCI states activated by MAC-CE, a correspondence relationship is established between the TCI codepoint indicated in the DCI and the TCI states activated by MAC-CE, and this may be the case when there are two TCI states activated by MAC-CE corresponding to the said TCI codepoint.

[0397] As another example, if at least one of the codepoints in the TCI state field within the DCI points to two TCI states, the terminal can assume that the base station can transmit based on a single-DCI-based multi-TRP method. In this case, at least one codepoint pointing to two TCI states within the TCI state field can be activated via the Enhanced PDSCH TCI state activation / deactivation MAC-CE.

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

[0399] [Table 18]

[0400]

[0401] In FIG. 10, if the value of the C0 field (1005) is 1, the corresponding MAC-CE is the TCI state ID 0,1 In addition to field (1010), TCI state ID 0,2 It may include a field (1015). This is the TCI state ID for the 0th codepoint of the TCI state field included in the DCI. 0,1 and TCI state ID 0,2 This means that it is activated, and if the base station instructs the terminal with the corresponding codepoint, the terminal may be instructed with two TCI states. If the value of the C0 field (1005) is 0, the MAC-CE is the TCI state ID 0,2 The field (1015) cannot be included, which is the TCI state ID for the 0th codepoint of the TCI state field included in the DCI. 0,1 This means that one TCI state corresponding to it is activated.

[0402] The above-described settings may be independent per cell or per BWP. For example, a PCell may have up to two activated TCI states corresponding to a single TCI codepoint, whereas a specific SCell may have up to one activated TCI state corresponding to a single TCI codepoint. In this case, it can be considered that NC-JT transmission is configured in the PCell, whereas NC-JT transmission is not configured in the aforementioned SCell.

[0403] [How to Distinguish Single-DCI-based Multi-TRP PDSCH Iterative Transmission Techniques (TDM / FDM / SDM)]

[0404] Next, a method for distinguishing single-DCI-based multi-TRP PDSCH repetitive transmission techniques is described. Depending on the value indicated by the DCI field from the base station and the upper layer signaling settings, the terminal may be instructed to use different single-DCI-based multi-TRP PDSCH repetitive transmission techniques (e.g., TDM, FDM, SDM). Table 19 below shows a method for distinguishing between single or multi-TRP-based techniques instructed to the terminal based on the value of a specific DCI field and the upper layer signaling settings.

[0405] [Table 19]

[0406]

[0407] In the above [Table 19], each column can be explained as follows.

[0408] - Number of TCI states (Column 2): Refers to the number of TCI states indicated by the TCI state field within the DCI, and can be 1 or 2.

[0409] - Number of CDM groups (Column 3): Refers to the number of different CDM groups of DMRS ports indicated by the Antenna port field within the DCI. It can be 1, 2 to 3.

[0410] - RepetitionNumber setting and indication conditions (Column 4): There can be 3 conditions depending on whether the repetitionNumber is set for all TDRA entries that can be indicated by the Time Domain Resource Allocation field within the DCI and whether the actual indicated TDRA entry has the repetitionNumber setting.

[0411] * Condition 1: If at least one of all TDRA entries that can be indicated by the Time Domain Resource Allocation field contains a setting for repetitionNumber, and a TDRA entry indicated by the Time Domain Resource Allocation field within the DCI contains a setting for repetitionNumber greater than 1

[0412] * Condition 2: If at least one of all TDRA entries that can be indicated by the Time Domain Resource Allocation field includes a setting for repetitionNumber, and the TDRA entry indicated by the Time Domain Resource Allocation field within the DCI does not include a setting for repetitionNumber

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

[0414] - Regarding repetitionScheme settings (Column 5): Indicates whether the upper layer signaling repetitionScheme is set. The upper layer signaling repetitionScheme can be set to one of 'tdmSchemeA', 'fdmSchemeA', or 'fdmSchemeB'.

[0415] - Transmission technique instructed to the terminal (Column 6): Refers to single or multiple TRP techniques instructed according to each combination (Column 1) expressed in [Table 19] above.

[0416] * Single-TRP: Refers to a single TRP-based PDSCH transmission. If the terminal has the pdsch-AggegationFactor configured within the upper-layer signaling PDSCH-config, the terminal can be scheduled for repeated single-TRP-based PDSCH transmissions as many times as configured. Otherwise, the terminal can be scheduled for a single single-TRP-based PDSCH transmission.

[0417] * Single-TRP TDM scheme B: Refers to PDSCH repetitive transmission based on time resource partitioning between slots based on a single TRP. In accordance with Condition 1 regarding the repetitionNumber described above, the terminal repetitively transmits PDSCH in the time dimension for a number of slots equal to the repetitionNumber set in the TDRA entry specified by the Time Domain Resource Allocation field, which is greater than 1. At this time, for each slot corresponding to the repetitionNumber, the starting symbol and symbol length of the PDSCH specified by the TDRA entry are applied identically, and the same TCI state is applied for each PDSCH repetitive transmission. This technique is similar to the slot aggregation method in that it performs PDSCH repetitive transmission between slots in the time resource, but it differs from slot aggregation in that it can dynamically determine whether to instruct repetitive transmission based on the Time Domain Resource Allocation field within the DCI.

[0418] * Multi-TRP SDM: Refers to a multi-TRP-based spatial resource partitioning PDSCH transmission method. This is a method of receiving layers by dividing them from each TRP; although it is not a repetitive transmission method, it can increase the reliability of PDSCH transmission by increasing the number of layers and lowering the coding rate. For each of the two CDM groups instructed by the base station, the terminal can receive PDSCH by applying the two TCI states instructed through the TCI state field within the DCI.

[0419] * Multi-TRP FDM scheme A: This refers to a multi-TRP-based Frequency Resource Allocation PDSCH transmission method. It utilizes a single PDSCH transmission occasion; unlike multi-TRP SDM, it does not involve repetitive transmission, but it is a technique that enables high-reliability transmission by increasing the amount of frequency resources and lowering the coding rate. Multi-TRP FDM scheme A can apply two TCI states, indicated via the TCI state field within the DCI, to non-overlapping frequency resources. If the PRB bundling size is determined to be wideband, the terminal receives the first TCI state applied to the first ceil(N / 2) RBs and the second TCI state applied to the remaining floor(N / 2) RBs when the number of RBs indicated by the Frequency Domain Resource Allocation field is N. Here, ceil(.) and floor(.) are operators representing rounding up and rounding down to the first decimal place. If the PRB bundling size is determined to be 2 or 4, even-numbered PRGs apply the first TCI state and odd-numbered PRGs apply the second TCI state to receive.

[0420] * Multi-TRP FDM scheme B: This refers to a multi-TRP-based frequency resource partitioning PDSCH repetitive transmission scheme. It has two PDSCH transmission occasions, allowing for the repetitive transmission of PDSCH to each occasion. Similar to A, Multi-TRP FDM scheme B can apply two TCI states, indicated via the TCI state field within the DCI, to non-overlapping frequency resources. If the PRB bundling size is determined to be wideband, the terminal receives 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, provided that the number of RBs indicated by the Frequency Domain Resource Allocation field is N. Here, ceil(.) and floor(.) are operators representing rounding up and rounding down to the first decimal place. If the PRB bundling size is determined to be 2 or 4, even-numbered PRGs apply the first TCI state and odd-numbered PRGs apply the second TCI state to receive.

[0421] * Multi-TRP TDM scheme A: Refers to a PDSCH repetitive transmission scheme within a time resource allocation slot based on multiple TRPs. A terminal has two PDSCH transmission occasions within a single slot, and the first reception occasion 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 occasion of the PDSCH can be the position obtained by applying a symbol offset of StartingSymbolOffsetK, an upper-layer signaling, from the last symbol of the first transmission occasion, and the transmission occasion can be determined by the indicated symbol length from this. If the upper-layer signaling StartingSymbolOffsetK is not set, the symbol offset can be considered as 0.

[0422] * Multi-TRP TDM scheme B: Refers to a PDSCH repetitive transmission scheme between slots based on multi-TRP time resource allocation. A terminal has one PDSCH transmission occasion within a slot and can receive repetitive transmissions based on the same PDSCH start symbol and symbol length for a number of slots specified by the repetitionNumber in the Time Domain Resource Allocation field within the DCI. If the repetitionNumber is 2, the terminal can receive the PDSCH repetitive transmissions of the first and second slots by applying the first and second TCI states, respectively. If the repetitionNumber is greater than 2, the terminal can use different TCI state application methods depending on how the upper layer signaling, tciMapping, is set. If tciMapping is set to cyclicMapping, the first and second TCI states are applied to the first and second PDSCH transmission occasions, respectively, and this same TCI state application method is applied to the remaining PDSCH transmission occasions. If tciMapping is set to sequenticalMapping, the first TCI state is applied to the first and second PDSCH transmission locations, the second TCI state is applied to the third and fourth PDSCH transmission locations, and the same method of applying TCI states is applied to the remaining PDSCH transmission locations.

[0423] Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The contents of the present disclosure are applicable to FDD (frequency division duplex), TDD (time division duplex) and / or XDD (cross division duplex) (and / or SBFD (subband non-overlapping full duplex), full duplex) systems. In the present disclosure, upper signaling (or upper layer signaling) is a signal transmission method transmitted from a base station to a terminal using a downlink data channel of the physical layer, or from a terminal to a base station using an uplink data channel of the physical layer, and may be referred to as RRC signaling, PDCP signaling, or a MAC (medium access control) control element (MAC control element; MAC CE).

[0424] For convenience in the following description of the present disclosure, cells, transmission points, panels, beams, and / or transmission directions that can be distinguished through upper layer / L1 parameters such as TCI state or spatial relation information, or indicators such as cell ID, TRP ID, and panel ID, may be described uniformly as TRP (transmission reception point), beam, or TCI state. Therefore, in actual application, TRP, beam, or TCI state can be appropriately replaced with one of the above terms.

[0425] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied having a specific format, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied including a specific indicator indicating whether cooperative communication is applied, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied being scrambled with a specific RNTI, or assuming the application of cooperative communication in a specific section indicated to an upper layer. For convenience of explanation thereafter, the case in which the terminal receives a PDSCH to which cooperative communication is applied based on conditions similar to those above will be referred to as the NC-JT case.

[0426] Embodiments of the present disclosure are described in detail below with reference to the accompanying drawings. Hereinafter, a base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, gNB, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. A terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. Although embodiments of the present disclosure are described below using a 5G system as an example, embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. For example, LTE or LTE-A mobile communication and mobile communication technologies developed after 5G may be included therein. Accordingly, embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure, in the judgment of a person skilled in the art. The contents of the present disclosure are applicable to FDD, TDD, and / or XDD (and / or SBFD, full duplex) systems.

[0427] Furthermore, in describing the present disclosure, if it is determined that a detailed description of related functions or configurations could unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined in consideration of their functions within the present disclosure, and these definitions may vary depending on the intent or practices of the user or operator. Therefore, their definitions should be based on the content throughout the present disclosure.

[0428] In describing the present disclosure below, the term "upper layer signaling" may refer to a signaling corresponding to at least one or a combination of at least one of the following signalings.

[0429] - MIB (Master Information Block)

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

[0431] - RRC (Radio Resource Control)

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

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

[0434] - PDCCH (Physical Downlink Control Channel)

[0435] - DCI (Downlink Control Information)

[0436] - Terminal-specific (UE-specific) DCI

[0437] - Group common DCI

[0438] - Common DCI

[0439] - Scheduling DCI (e.g., DCI used for the purpose of scheduling downlink or uplink data)

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

[0441] - PUCCH (Physical Uplink Control Channel)

[0442] - UCI (Uplink Control Information)

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

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

[0445] In the following disclosure, the examples are described through a number of embodiments, but these are not independent, and one or more embodiments may be applied simultaneously or in combination.

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

[0447] <First Embodiment: UL only TRP support method>

[0448] In one embodiment of the present disclosure, a method for supporting a UL only TRP capable of receiving only UL among multi-TRPs operated at a base station is described. This embodiment may be operated in combination with other embodiments. Hereinafter, in the present disclosure, UL only TRP, uplink-only TRP, UL-only supported TRP, and various terms that can be interpreted identically or similarly thereto may be interpreted as meaning a TRP that supports only the reception of uplink signals among TRPs that can be operated at a base station.

[0449] When transmitting a signal through the uplink channel, the terminal can determine the uplink transmission power based on the TCI state. At this time, depending on the supported TCI state, the terminal and the base station may operate in one of two modes: the joint TCI mode (indicating uplink transmission power parameters via the TCI-State) or the separate TCI mode (indicating uplink transmission power parameters via the TCI-UL-State). Transmission power parameters can be applied to the uplink channel through the following methods.

[0450] [Method 1-1] Basic Transmission Power Determination Method: Application of Common Transmission Power Parameters

[0451] For every uplink transmission within each uplink bandwidth portion, the terminal may apply a set of transmission power parameters (e.g., p0, alpha, closed-circuit index) that can be determined through ul-powerControl set in the corresponding uplink bandwidth portion.

[0452] [Method 1-2] Additional method for determining transmission power: Different transmission power parameters can be applied

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

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

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

[0456] A terminal (11-10) can be connected to and operated by a base station that operates with multiple TRPs. Basically, the terminal can assume that each of the multiple TRPs supports both uplink reception and downlink transmission. In this case, the base station may operate a TRP (11-05) that supports only uplink reception functions in addition to the conventional TRP (1100) that supports both uplink reception and downlink transmission. For the purpose of improving uplink coverage from the perspective of the terminal or for the purpose of energy saving benefits obtainable by saving downlink transmission power at the base station, the base station may operate a TRP (11-05) that supports only uplink reception functions. Such a TRP that supports only uplink reception can be named a UL-only TRP. The terminal can assume that downlink transmission does not occur from such a UL-only TRP. In this case, as an assumption regarding such a UL-only TRP, the base station and the terminal may consider at least one of the following combinations.

[0457] - The UL-only TRP can operate as a UL-only TRP only for specific terminals. That is, although the UL-only TRP is equipped with both uplink reception and downlink transmission functions, it may support only the uplink reception function for specific terminals under specific conditions (e.g., notifying the terminal that it is connected to the UL-only TRP through a combination of at least one of specific upper layer signaling, MAC-CE, and L1 signaling). That is, the UL-only TRP may support downlink transmission for other terminals. When specific terminals are located at the boundary of an arbitrary cell coverage area, this UL-only TRP can expand uplink coverage by operating an existing TRP or a newly installed TRP near that location to additionally operate only the reception function.

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

[0459] Although the terminal can receive a reference signal for measuring path loss from a TRP (1100) capable of uplink and downlink operations, it does not receive a downlink signal from a UL-only TRP (1105). Therefore, when the terminal (1110) performs an uplink transmission toward the UL-only TRP (1105), there may be a problem in that the amount of path loss between the UL-only TRP and the terminal cannot be known. To solve this situation, the base station and the terminal can perform the following process [Method 2-1] to obtain information on the amount of path loss between the UL-only TRP and the terminal.

[0460] [Method 2-1]

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

[0462] [Process 2-2] Base station calculates the difference in path loss

[0463] [Process 2-3] Deliver the difference in path loss to the terminal

[0464] [Process 2-4] Obtain d_P, the difference in path loss between a TRP capable of supporting both uplink and downlink and a TRP capable of supporting only uplink. Uplink transmission of the terminal without applying d_P.

[0465] [Process 2-5] Base station calculates the difference in path loss

[0466] [Process 2-6] Deliver the difference in path loss to the terminal

[0467] That is, in order to obtain information on the amount of loss between the base station and the terminal, the terminal performs uplink transmission and can receive from the base station a difference value of the path loss amount determined based on the uplink signal. For example, the terminal can transmit an uplink signal with the same power through a TRP that supports both uplink and downlink (UL / DL TRP) and a TRP that supports only uplink (UL-only TRP), and the base station can determine the difference value (d_P) of the path loss amount of the received signal and transmit it to the terminal. Accordingly, the terminal determines the transmission power for uplink transmission to a TRP that supports only uplink (UL-only TRP) and can perform uplink transmission based on the transmission power. At this time, the terminal can determine the transmission power without applying the difference value of the path loss amount. For example, when the terminal transmits a UL RS (e.g., SRS), which is a signal for updating the path loss difference value, the terminal can determine the transmission power without applying the difference value of the path loss amount. In addition, the terminal may use at least one of the following Equation 1, Equation 3, or Equation 6 to determine the uplink transmission power to the UL-only TRP.

[0468] To obtain path loss information using another [Method 2-2], the terminal can perform the following process.

[0469] [Method 2-2]

[0470] [Process 3-1] Uplink transmission of the terminal

[0471] [Process 3-2] Base station calculates the difference in path loss

[0472] [Process 3-3] Deliver the difference in path loss to the terminal

[0473] [Process 3-4] Obtain d_P, the difference in path loss between a TRP capable of supporting both uplink and downlink and a TRP capable of supporting only uplink. Apply d_P and transmit the terminal's uplink.

[0474] [Process 3-5] Base station calculates the difference in path loss

[0475] [Process 3-6] Deliver the difference in path loss to the terminal

[0476] That is, in order to obtain information on the amount of loss between the base station and the terminal, the terminal performs uplink transmission and can receive from the base station the difference value of the path loss amount determined based on the uplink signal. Accordingly, the terminal determines the transmission power for uplink transmission to a TRP capable of supporting only uplink (UL-only TRP) and can perform uplink transmission based on the transmission power. At this time, the terminal can determine the transmission power by applying the difference value of the path loss amount. For example, the terminal can determine the transmission power by applying the difference value of the path loss amount in cases other than when transmitting UL RS (e.g., SRS), which is a signal for updating the path loss difference value. The terminal may use at least one of Equations 11 to 14 to determine the uplink transmission power to the UL-only TRP, and The d_P value can be used.

[0477] Through the above-described [Method 2-1] and [Method 2-2], the terminal may use the modified transmission power calculation formula as follows when determining the uplink transmission power for the UL-only TRP.

[0478] For example, when determining the PUCCH transmission power for a UL-only TRP that supports only uplink reception operations, the terminal may use the above [Equation 1] modified as shown in the following [Equation 10]. That is, Equation 1 can be modified to Equation 10. At this time, within the following [Equation 10] can be considered as the above d_P value, which is the difference in path loss amount, and This may mean that the difference in the corresponding path loss corresponds to one or more path loss measurement reference signals. In this case, the terminal If corresponds to a single path loss measurement reference signal, It can also be considered as.

[0479] [Mathematical Formula 10]

[0480]

[0481] As another example, when determining the PUSCH transmission power for a UL-only TRP that supports only uplink reception operations, the terminal may modify and use the above [Equation 3] as shown in the following [Equation 11] or [Equation 12]. That is, Equation 3 can be modified into Equation 11 or Equation 12. In this case, within the following [Equation 11] or [Equation 12] can be considered as the above d_P value, which is the difference in path loss amount, and This may mean that the difference in the corresponding path loss corresponds to one or more path loss measurement reference signals. In this case, the terminal If corresponds to a single path loss measurement reference signal, It can also be considered as. The following [Equation 11] or [Equation 12] is the difference in path loss amount It can be distinguished based on whether the value is directly applied to the path loss amount.

[0482] [Mathematical Formula 11]

[0483]

[0484] [Mathematical Formula 12]

[0485]

[0486] As another example, when determining the PUSCH transmission power for a UL-only TRP that supports only uplink reception operations, the terminal may modify and use the above [Equation 6] as shown in the following [Equation 13] or [Equation 14]. That is, Equation 6 can be modified to Equation 13 or Equation 14. In this case, within the following [Equation 13] or [Equation 14] can be considered as the above d_P value, which is the difference in path loss amount, and This may mean that the difference in the corresponding path loss corresponds to one or more path loss measurement reference signals. In this case, the terminal If corresponds to a single path loss measurement reference signal, It can also be considered as. The following [Equation 14] or [Equation 15] is the difference in path loss amount It can be distinguished based on whether the value is directly applied to the path loss amount.

[0487] [Mathematical Formula 13]

[0488]

[0489] [Mathematical Formula 14]

[0490]

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

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

[0493] The terminal may consider at least one combination of the following items as a method of receiving from the base station regarding the difference value of the path loss amount or the amount of change thereof.

[0494] [Method 3-1]

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

[0496] [Method 3-2]

[0497] The terminal can receive a value d_P, which is the difference value of the path loss amount, or a value d_P'', which is the change amount of the d_P value, as an upper layer signaling from the base station, and then receive MAC-CE signaling from the base station to update the preset value.

[0498] [Method 3-3]

[0499] The terminal receives the value d_P, which is the difference value of the path loss amount, or the value d_P'', which is the change amount of the d_P value, as upper layer signaling from the base station, and can then receive instructions through DCI.

[0500] [Method 3-4]

[0501] The terminal may receive a value of d_P, which is the difference in the path loss amount, or a value of d_P'', which is the change in the d_P value, as upper layer signaling from the base station. Additionally, the terminal may receive two or more CSI-RS signals from the base station and implicitly determine the d_P or d_P'' value through the difference in the received power of the CSI-RS signals.

[0502] [Method 3-5]

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

[0504] A method for a terminal to receive uplink scheduling from a base station that includes information regarding the difference value of path loss amount may consider at least one combination of the following items.

[0505] [Method 4-1]

[0506] The terminal may receive one or more joint TCI states or UL TCI states as upper layer signaling from the base station, and at this time, as shown in [Table 20] below, the terminal may receive information on the difference value of the path loss amount within one or more joint TCI states or UL TCI states. In [Table 20], the names of the RRC IE (information element) are examples only and may be expressed with other names.

[0507] [Table 20]

[0508]

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

[0510] For example, Xs and Xe may be 0 and 30, respectively. As another example, Xs and Xe may be -10 and 50, respectively, and their values ​​may be in units of 1 dB. As yet another example, Xs and Xe may be 2 and 32, respectively, and their values ​​may be in units of 2 dB. However, the embodiments of the present disclosure are not limited thereto, and any integer values ​​may be used for Xs and Xe.

[0511] [Method 4-2]

[0512] The terminal may receive one or more joint TCI states or UL TCI states as upper-layer signaling from the base station, and the terminal may receive one or more difference values ​​of path loss within BWP-UplinkDedicated, which is upper-layer signaling for the uplink bandwidth portion, and each difference value of path loss may be associated with one or more groups of path loss measurement reference signals. Additionally, within the joint TCI state or UL TCI state, the terminal may additionally receive upper-layer signaling that indicates whether to apply the difference value of path loss to the path loss measured through the path loss measurement reference signals that can be set as upper-layer signaling. Table 21 below is one example that can represent the above method, and the connection between the difference value of path loss and the group of path loss measurement reference signals may not be limited thereto. In Table 21, the names of the RRC IE are examples only and may be expressed by other names.

[0513] [Table 21]

[0514]

[0515]

[0516] The terminal can receive pathlossOffset as an upper layer signaling value for the difference in path loss amount, and the value can be an integer from Xs to Xe.

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

[0518] However, the embodiments of the present disclosure are not limited thereto, and any integer values ​​may be used for Xs and Xe.

[0519] [Method 4-3]

[0520] The terminal may receive one or more joint TCI states or UL TCI states as upper layer signaling from the base station, and the terminal may receive one difference value of path loss within BWP-UplinkDedicated, which is upper layer signaling for the uplink bandwidth portion. In this case, depending on the method of operation as a multiple TRP, it may be assumed that the difference value of path loss is always applied to a specific TCI state.

[0521] The following [Table 22] may be one example of how the above method can be expressed, but is not limited thereto. In [Table 22], the name of RRC IE is for illustrative purposes only and may be expressed by other names.

[0522] [Table 22]

[0523]

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

[0525] If the terminal does not receive the pathlossOffset within BWP-UplinkDedicated, the terminal may consider the difference value of the path loss amount to be 0.

[0526] The terminal can receive pathlossOffset as an upper layer signaling value for the difference in path loss amount, and the value can be an integer from Xs to Xe.

[0527] For example, Xs and Xe may be 0 and 30, respectively. As another example, Xs and Xe may be -10 and 50, respectively, and their values ​​may be in units of 1 dB. As yet another example, Xs and Xe may be 2 and 32, respectively, and their values ​​may be in units of 2 dB. However, the embodiments of the present disclosure are not limited thereto, and any integer values ​​may be used for Xs and Xe.

[0528] [Method 4-4]

[0529] The terminal may receive a single difference value for path loss from the base station via upper layer signaling. The setting for this difference value for path loss may vary by bandwidth portion, or it may vary by cell, resulting in the same value being set for all bandwidth portions within a cell. In this case, when a difference value for path loss is set, the terminal can expect a new field to be included within the DCI indicating whether to apply the difference value for path loss. Through this new field within the DCI, the terminal can distinguish from the base station via the DCI whether it is an uplink transmission to a UL-only TRP or an uplink transmission to a TRP capable of both uplink and downlink operations.

[0530] [Method 4-5]

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

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

[0533] The terminal may report to the base station, as a terminal capability, whether it is possible to support at least one combination of [Method 4-1] to [Method 4-5] above. At this time, if the terminal reports to the base station, as a terminal capability, that a combination of one or more specific methods is possible, it may be considered that the terminal has reported that support for one or more other specific combinations of methods is not possible.

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

[0535] <Second Embodiment: Method for reporting beam groups to support uplink multi-panel simultaneous transmission for UL only TRP>

[0536] A method for reporting beam groups to support uplink multi-panel simultaneous transmission when supporting uplink-only (UL only or UL-only supported) TRP according to one embodiment of the present disclosure is described. This embodiment may operate in combination with other embodiments described in the present disclosure.

[0537] An uplink-only TRP is a TRP operated for the purpose of receiving uplink channels or uplink reference signals, through which downlink channels and downlink reference signals are not transmitted. Uplink-only TRPs can be broadly classified into two types. The first type of uplink-only TRP can be defined as a case where it supports downlink transmission but is operated to perform only uplink reception for a specific terminal. The second type of uplink-only TRP is a TRP that does not include a transmitter for transmitting downlink channels and downlink reference signals, and can be defined as a TRP that supports only uplink reception for all terminals. For both types of uplink-only TRPs, it can be assumed that transmission of downlink channels and downlink reference signals is impossible for a specific terminal. Alternatively, it can be assumed that downlink reference signals can be transmitted to a specific terminal depending on the operating conditions. In this embodiment, a case is assumed where downlink reference signals cannot be transmitted through an uplink-only TRP.

[0538] If a terminal includes panels capable of multiple uplink transmissions, multiple uplink channels and / or multiple uplink reference signals can be transmitted simultaneously through the same or overlapping time resources using multiple panels as follows. The multi-panel-based uplink simultaneous transmission (STxMP) technique can be classified into single DCI (sDCI) based STxMP and multi DCI (mDCI) based STxMP techniques depending on the DCI that schedules the uplink channel or uplink reference signal (for convenience of explanation, it is assumed that 'uplink channel' below can refer to both the uplink channel and the uplink reference signal).

[0539] The sDCI-based STxMP technique is a method for scheduling uplink channels transmitted through multiple panels using a single DCI, which allows for scheduling uplink channels with the same time and frequency resources. In this case, the scheduled uplink channels can be classified into cases where different data is transmitted through each panel and cases where the same data is transmitted repeatedly.

[0540] A technique for dividing some layers of a PUSCH scheduled based on sDCI into different panels for transmission can be defined as an sDCI-based STxMP SDM (spatial division multiplexing) technique. For example, assume a PUSCH of N (e.g., 2) layers is scheduled based on sDCI. The first SRI (SRS resource indicator) and / or the first TPMI (transmit precoding matrix indicator) may be directed by the sDCI scheduling the PUSCH to transmit the N1 (e.g., 1)th layer from the first layer based on the first panel (or the first SRS resource set with a low SRS resource set Id among SRS resource sets whose usage is codebook or nonCodebook). And, based on the second panel (or the second SRS resource set in which the usage is codebook or nonCodebook and the SRS resource set Id has a high value), the second SRI and / or second TPMI may instruct the sDCI scheduling the corresponding PUSCH to transmit from the N1+1th layer to the N (e.g., 2)th layer.

[0541] On the other hand, a technique for repeatedly transmitting sDCI-based PUSCHs through different panels can be defined as an sDCI-based STxMP SFN (single frequency network) technique. For example, assume a case where N (e.g., 2) layer PUSCHs are scheduled based on sDCI. The first SRI and / or the first TPMI may be directed by the sDCI scheduling the PUSCH to transmit all N (e.g., 2) layers based on the first panel (or the first SRS resource set among SRS resource sets whose usage is codebook or nonCodebook that has a low SRS resource set Id). And based on the second panel (or the second SRS resource set in which the SRS resource set Id has a high value among the SRS resource sets whose usage is codebook or nonCodebook), the second SRI and / or second TPMI may be directed by the sDCI scheduling the corresponding PUSCH to transmit all N (e.g., 2) layers.

[0542] The mDCI-based STxMP technique is a method for scheduling multiple uplink channels transmitted through each panel using multiple DCIs, allowing uplink channels to be scheduled using different time and frequency resources. In this case, the multiple uplink channels scheduled by each DCI may completely overlap (furlly overlapping) or partially overlap in the time domain. Since different uplink channels are scheduled by each DCI, different data may be transmitted through said uplink channels. Alternatively, by reusing the method for scheduling retransmission, the terminal may repeatedly transmit the same data through multiple uplink channels (specifically PUSCH) scheduled by different DCIs.

[0543] As described above, the uplink channel can be scheduled using multiple panels, and the terminal can simultaneously transmit the scheduled uplink channel using each panel. In this case, the base station must instruct the TCI state for each panel so that the terminal can determine the uplink beam and transmission power applied to transmit the uplink channel through each panel. The terminal can report to the base station candidate beam combinations capable of simultaneous transmission using multiple panels (or panels that, depending on the implementation, are not actually multiple panels but can perform similar operations). The terminal can report to the base station the candidate beam combinations capable of simultaneous transmission configured identically to the candidate beam combinations capable of simultaneous reception. In this case, the reception spatial filter for downlink reception and the transmission spatial filter for uplink transmission must match each other. If the receiving space filter for downlink reception and the transmitting space filter for uplink transmission do not always match each other, the terminal reports its terminal capability to the base station, and the base station may separately report channel state information (CSI) regarding beam combination candidate(s) for downlink simultaneous reception and CSI regarding beam combination candidate(s) for uplink simultaneous transmission to the terminal.

[0544] A terminal can report beam combination candidate(s) capable of simultaneous uplink transmission to multiple panels to the base station using the following CSI reporting format.

[0545] [Table 23]

[0546]

[0547] Here, the resource set indicator is a field consisting of 1 bit, and the terminal reports the CSI to the base station by setting the resource set indicator field to either 0 or 1. If the terminal sets the resource set indicator field to 0, the CRI or SSBRI #1 of the first resource group reported to the base station through the CSI report containing that resource set indicator field is the first channel measurement resource set (1 st This means that it was selected from the channel measurement resource set. In this case, the CRI or SSBRI #1(s) of each resource group are selected from the first channel measurement resource set, and the CRI or SSBIRS #2(s) of each resource group are selected from the second channel measurement resource set (2 nd It is selected from the channel measurement resource set. If the terminal has set the resource set indicator field to 1, it means that the CRI or SSBRI #1 of the first resource group reported to the base station via the CSI report containing the resource set indicator field has been selected from the second channel measurement resource set. In this case, the CRI or SSBRI #1(s) of each resource group are selected from the second channel measurement resource set, and the CRI or SSBRI #2(s) of each resource group are selected from the first channel measurement resource set.

[0548] The reference signal designated as CRI or SSBRI #1 of the first resource group may be determined by a certain rule. For example, among all reference signals included in the first or second channel measurement resource set, the reference signal received by the terminal with the largest RSRP may be determined as the reference signal designated as CRI or SSBRI #1 of the first resource group. The terminal reports the CSI to the base station, including the RSRP measured when receiving the reference signal designated as CRI or SSBRI #1 of the first resource group. For the RSRP measured when receiving other reference signals designated as CRI or SSBRI, the terminal may perform CSI reporting to the base station by calculating a differential RSRP based on the RSRP measured when receiving the reference signal designated as CRI or SSBRI #1 of the first resource group. The number of bits for each resource group's CRI or SSBRI and the number of bits for the RSRP measured when receiving the reference signal indicated by CRI or SSBRI #1 of the first resource group, and the number of bits for the different RSRP to report the RSRP measured when receiving the reference signal indicated by CRI or SSBRI other than the reference signal indicated by CRI or SSBRI #1 of the first resource group, can be determined by referring to the following [Table 24].

[0549] [Table 24]

[0550]

[0551] Here represents the number of CSI-RS resources set in the corresponding resource set (i.e., the first channel measurement resource set or the second channel measurement resource set), and represents the number of SSB (SS / PBCH block) set in the corresponding resource set (i.e., the first channel measurement resource set or the second channel measurement resource set).

[0552] The base station can set the first channel measurement resource set and the second channel measurement resource set indicated by the resource set indicator described above through an RRC message to the terminal as shown in the following [Table 25].

[0553] [Table 25]

[0554]

[0555] The base station can set nzp-CSI-RS-SSB in csi-RS-ResourceSetList in [Table 25]. And, if the base station sets RRC parameters for group-based beam reporting (e.g., groupBasedBeamReporting-v1710 or groupBasedBeamReporting-v1800), it can set csi-SSB-ResourceSetList in nzp-CSI-RS-SSB as the first channel measurement resource set and additionally set csi-SSB-ResourceSetListExt-r17 as the second measurement resource set. Alternatively, if the base station sets the RRC parameters for group-based beam reporting (e.g., groupBasedBeamReporting-v1710 or groupBasedBeamReporting-v1800) and sets the resourceType to periodic or semiPersistent, the base station may set two NZP-CSI-RS-ResourceSetIds in nzp_CSI-RS-ResourceSetList to the terminal to set two NZP-CSI-RS-ResourceSets as channel measurement resource sets for performing group-based beam reporting. At this time, the base station may set the first NZP CSI-RS resource set (for example, the NZP CSI-RS resource set indicated by the first value among the NZP-CSI-RS-ResourceSetIds set in the NZP-CSI-RS-ResourceSet) among the two NZP-CSI-RS-ResourceSets as the first channel measurement resource set and the second NZP CSI-RS resource set (for example, the NZP CSI-RS resource set indicated by the second value among the NZP-CSI-RS-ResourceSetIds set in the NZP-CSI-RS-ResourceSet) as the second channel measurement resource set.

[0556] In order for a base station to set two channel measurement resource sets to a terminal as shown in [Table 25] above, the terminal must be capable of simultaneous uplink transmission and / or simultaneous downlink reception and must support group-based beam reporting to support this. That is, if the terminal reports to the base station that it is capable of simultaneous uplink transmission and / or simultaneous downlink reception, and reports that it supports group-based beam reporting to support simultaneous transmission and / or simultaneous reception, the base station can set the first channel measurement resource set and the second channel measurement resource set to the terminal via RRC.

[0557] Meanwhile, if a TRP is a UL-only TRP that cannot transmit a downlink reference signal and supports uplink multi-panel simultaneous transmission including the UL-only TRP, it may not be able to support group-based beam reporting to support uplink simultaneous transmission for the UL-only TRP. This is because, as can be seen in [Table 25], the channel measurement reference signal used for group-based beam reporting is composed of a downlink reference signal. If a terminal is to report an uplink transmit beam (or transmit space filter) combination for uplink multi-panel simultaneous transmission for a TRP that cannot transmit a downlink reference signal, such as a UL-only TRP, it is necessary to define the uplink reference signal as a channel measurement reference signal and add corresponding RRC parameters.

[0558] An SRS may be used as an uplink reference signal to indicate the transmit beam to be applied for transmitting an uplink channel or an uplink reference signal. Specifically, a terminal may transmit an SRS to a UL-only TRP to determine the transmit beam for transmitting an uplink channel or an uplink reference signal to a UL-only TRP that does not support downlink transmission. A base station may receive the SRS through the UL-only TRP and select an SRS that supports the UL-only TRP. Subsequently, to indicate the selected SRS to the terminal, the base station may indicate a TCI (e.g., TCI-UL-State) set as a QCL reference signal to the terminal through a TRP capable of downlink transmission (i.e., a TRP capable of DCI transmission rather than a UL-only TRP). As a more specific example, the terminal may transmit SRS resources within an SRS resource set with usage 'beamManagement' to the base station.

[0559] At this time, the terminal can transmit SRS resources to the base station while changing the transmit beam (or transmit space filter) according to the terminal implementation. The base station can receive the SRS resources transmitted by the terminal through the UL only TRP. The base station can select one SRS resource from among the SRS resources received through the UL only TRP based on a specific method (e.g., the SRS resource with the best reception quality or the SRS resource received with the largest RSRP). The base station can transmit a DCI to the terminal using a TRP capable of downlink support to indicate the TCI (e.g., TCI-UL-State) set as the reference signal for the selected SRS resource. Subsequently, after the beam application time (BAT), the terminal can transmit the uplink channel or uplink reference signal to the UL only TRP using the TCI-UL-State.

[0560] As described above, if uplink multi-panel simultaneous transmission is supported for an mTRP including a UL only TRP, the terminal may perform enhanced group-based beam reporting to report uplink beam combination(s) for uplink multi-panel simultaneous transmission to the base station. Cases in which a UL only TRP is included can be broadly divided into the following cases.

[0561] - Case 1) Uplink channels or uplink reference signals transmitted simultaneously through multiple panels may be received through multiple UL only TRPs. In Case 1, the terminal receives downlink channels or downlink reference signals from a TRP other than a UL only TRP, and the base station may assume a case where it receives the uplink signal or uplink reference signal transmitted by the terminal through a UL only TRP other than a TRP that supports downlink transmission.

[0562] FIG. 12 illustrates an example of supporting mTRP uplink transmission using TRPs that support only uplink reception functions. A terminal (1210) can be connected to and operated by a base station that operates with multiple TRPs. In this case, it can be assumed that TRP (1200) supports only downlink transmission and other TRPs (1205, 1215) support only uplink reception. In this case, the base station can operate the TRP (1200) that supports only downlink transmission and the TRPs (1205, 1215) that support only uplink reception together.

[0563] - Case 2) An uplink channel or uplink reference signal transmitted simultaneously through multiple panels may be received not only through a UL only TRP but also through a TRP that supports downlink transmission. In Case 2, the terminal receives the downlink channel or downlink reference signal from a TRP capable of both uplink reception and downlink transmission, and the base station may assume a case where it receives the uplink signal or uplink reference signal transmitted by the terminal through a TRP that supports uplink and downlink transmission and reception and a UL only TRP. This allows the base station to receive the uplink signal through multiple TRPs by utilizing both a TRP that supports uplink and downlink transmission and reception and a TRP that supports only uplink reception, as described above in FIG. 11.

[0564] Considering the above-described case 1 or / and case 2, if a multi-TRP uplink simultaneous transmission and reception technique including a UL only TRP is supported (e.g., an RRC parameter for pathloss offset as described in the first embodiment may be included in the RRC parameter set by the base station, or an RRC parameter for supporting any new UL only TRP may be defined) and an RRC parameter for supporting a group-based beam reporting technique for multi-panel uplink simultaneous transmission (e.g., groupBasedBeamReporting-v1800, etc.) or an RRC parameter for supporting a group-based beam reporting technique for multi-TRP multi-panel uplink simultaneous transmission including a UL only TRP (e.g., groupBasedBeamReporting-v1900, etc.) is set, the base station may support one or a combination of the following methods to the terminal so that the terminal can report a beam combination capable of simultaneous transmission to the base station.

[0565] - [Method 1] A base station may set an SRS resource set as a channel measurement reference signal set. The base station may set an SRS resource set as a channel measurement reference signal set within CSI-ResourceConfig to perform group-based beam reporting to support Case 1 and Case 2, where UL only TRP may be included. Specifically, the base station may set an srs-ResourceSetList within csi-RS-ResourceSetList in nzp-CSI-RS-SSB or a newly defined RRC parameter (e.g., nzp-CSI-RS-SSB-SRS, etc.). The srs-ResourceSetList may consist of a list of SRS-ResourceSetIds. A single SRS-ResourceSetId may be set within the srs-ResourceSetList, or multiple (e.g., two) SRS-ResourceSetIds may be set. If multiple SRS-ResourceSetIds are set in srs-ResourceSetList, nzp-CSI-RS-ResourceSetList with an NZP-CSI-RS-ResourceSetId pointing to an additional NZP-CSI-RS-ResourceSet or csi-SSB-ResourceSetList with an NZP-CSI-RS-ResourceSetId pointing to an additional CSI-SSB-ResourceSet may not be set in nzp-CSI-RS-SSB or a new RRC parameter (e.g., nzp-CSI-RS-SSB-SRS).

[0566] And if multiple SRS-ResourceSetIds are set within srs-ResourceSetList, according to a certain rule, among the SRS resource sets indicated by the SRS-ResourceSetIds, one SRS resource set may be defined as the first channel measurement reference signal set and another SRS resource set may be defined as the second channel measurement reference signal set. As a specific example, if two different SRS-ResourceSetIds are set within srs-ResourceSetList, the SRS resource set identified by the SRS-ResourceSetId with the smaller value of the two SRS-ResourceSetIds may be defined as the first channel measurement reference signal set, and the SRS resource set identified by the SRS-ResourceSetId with the larger value of the two SRS-ResourceSetIds may be defined as the second channel measurement reference signal set. If one SRS-ResourceSetId is set in srs-ResourceSetList, an nzp-CSI-RS-ResourceSetList with an NZP-CSI-RS-ResourceSetId pointing to one (or more) NZP-CSI-RS-ResourceSets or a csi-SSB-ResourceSetList with an NZP-CSI-RS-ResourceSetId pointing to one (or more) CSI-SSB-ResourceSets may be additionally set in nzp-CSI-RS-SSB or a new RRC parameter (e.g., nzp-CSI-RS-SSB-SRS, etc.).

[0567] The following [Table 26] shows an example of a set of channel measurement reference signals configured within a CSI-ResourceConfig associated with a CSI report for performing group-based beam reporting. Here, the CSI-ResourceConfig associated with a CSI report for performing group-based beam reporting refers to a CSI-ResourceConfig identified by the CSI-ResourceConfigId of resourcesForChannelMeasurement configured in a CSI-ReportConfig that has RRC parameters (e.g., groupBasedBeamReporting-v1800, etc.) configured to support a group-based beam reporting technique for multi-panel uplink simultaneous transmission, or RRC parameters (e.g., groupBasedBeamReporting-v1900, etc.) configured to support a group-based beam reporting technique for multi-panel uplink simultaneous transmission including UL only TRP.

[0568] [Table 26]

[0569]

[0570] maxNrofSRS-ResourceSetsPerConfig represents the maximum number of SRS resource sets that can be set as channel measurement reference signal sets per CSI-ResourceConfig, and in the example of Case 2 described above, maxNrofSRS-ResourceSetsPerConfig may be defined as 2, and in the example of Case 1, maxNrofSRS-ResourceSetPerConfig may be defined as 1. Unlike the example described above, maxNrofSRS-ResourceSetPerConfig may be a value greater than 2, and maxNrofSRS-ResourceSetPerConfig may implicitly represent the number of UL only TRPs to support uplink multi-panel simultaneous transmission.

[0571] Alternatively, srs-ResourceSetListExt within CSI-ResourceConfig may be configured as shown in the following [Table 27] or [Table 28].

[0572] [Table 27]

[0573]

[0574] [Table 28]

[0575]

[0576] In [Table 28], maxNrofSRS-ResourceSetsPerConfig can be set to 1, and srs-ResourceSetListExt can be additionally set to set two SRS resource sets as channel measurement reference signal sets.

[0577] When setting an SRS resource set as a channel measurement reference signal set as in [Table 26], [Table 27], or [Table 28], an SRS resource with usage set to a specific value may be set as a channel measurement reference signal set. For example, one or more of the SRS resource sets with usage 'beamManagement' may be set through the SRS-ResourceSetId(s) of srs-ResourceSetList or srs-ResourceSetListExt in CSI-ResourceConfig described in [Table 26] or [Table 27].

[0578] - [Method 2] RRC setting parameters for an SRS resource set. A new RRC parameter can be set within the SRS-ResourceSet to indicate that it is a channel measurement reference signal set. For example, as shown in [Table 29] below, a new RRC parameter resourceSet-Indicator can be set to indicate that it is the first channel measurement reference signal set or the second channel measurement reference signal set within the SRS-ResourceSet. The value that can be indicated by resourceSet-Indicator can be from 0 to n, where n represents a positive integer greater than 0. For example, n can be defined as 1.

[0579] [Table 29]

[0580]

[0581]

[0582] If the resourceSet-Indicator in the SRS-ResourceSet is set to an RRC parameter for an SRS resource set of a specific usage (e.g., beamManagement) when an RRC parameter (e.g., groupBasedBeamReporting-v1800, etc.) for supporting a group-based beam reporting technique for multi-panel uplink simultaneous transmission including UL only TRP is set as described above, or an RRC parameter (e.g., groupBasedBeamReporting-v1900, etc.) for supporting a group-based beam reporting technique for multi-panel uplink simultaneous transmission including UL only TRP is set, the resourceSet-Indicator in the SRS-ResourceSet may be set to 0 for the SRS resource set that is the first channel measurement reference signal set, and if the resourceSet-Indicator in the SRS-ResourceSet is set to 1 for the SRS resource set that is the second channel measurement reference signal set.

[0583] If a resourceSet-Indicator is set for one SRS-ResourceSet, an nzp-CSI-RS-ResourceSetList with an NZP-CSI-RS-ResourceSetId indicating one (or more) NZP-CSI-RS-ResourceSets or a csi-SSB-ResourceSetList with an NZP-CSI-RS-ResourceSetId indicating one (or more) CSI-SSB-ResourceSets may be additionally set in a new RRC parameter (e.g., nzp-CSI-RS-SSB-SRS) or a CSI-SSB-ResourceSet associated with CSI reporting for performing group-based beam reporting.

[0584] If resourceSet-Indicator is set for multiple SRS-ResourceSets, CSI-ResourceConfig associated with CSI reporting for performing group-based beam reporting may not be set. In CSI-ReportConfig where RRC parameters for supporting group-based beam reporting techniques for multi-panel uplink simultaneous transmission (e.g., groupBasedBeamReporting-v1800, etc.) or RRC parameters for supporting group-based beam reporting techniques for multi-panel uplink simultaneous transmission including UL only TRP (e.g., groupBasedBeamReporting-v1900, etc.) are set, SRS-ResourceSetId may be set for the reference signal for channel measurement as shown in [Table 30] below. In this case, if resourcesForChannelMeasurementExt containing multiple SRS-ResourceSetIds is set, resourcesForChannelMeasurement that sets CSI-ResourceConfigId may be omitted. If resourcesForChannelMeasurementExt containing a single SRS-ResourceSetId is configured, resourcesForChannelMeasurement configuring CSI-ResourceConfigId can be configured.

[0585] [Table 30]

[0586]

[0587] To support a multi-panel simultaneous transmission technique including a UL only TRP configured as above, the base station and the terminal can set RRC parameters and perform group-based beam reporting through the following procedure.

[0588] [Option 1]

[0589] - The terminal can transmit an SRS for beam management purposes to the base station.

[0590] - The base station can receive an SRS for beam management purposes from the terminal.

[0591] - The base station can reset RRC parameters by referring to the received SRS for beam management purposes. In this case, the RRC message may include a set of channel measurement reference signals as follows.

[0592] ■ A CSI-ReportConfig can be reconfigured with RRC parameters (e.g., groupBasedBeamReporting-v1800, etc.) to support a group-based beam reporting technique for simultaneous transmission of multiple panels uplinks, or RRC parameters (e.g., groupBasedBeamReporting-v1900, etc.) to support a group-based beam reporting technique for simultaneous transmission of multiple TRPs including UL only TRPs, and a channel measurement reference signal set can be configured with a new SRS resource set and / or an NZP CSI-RS resource set or an SSB resource set as described in [Method 1] above.

[0593] ■ A CSI-ReportConfig can be reset with RRC parameters (e.g., groupBasedBeamReporting-v1800, etc.) for supporting a group-based beam reporting technique for simultaneous transmission of multiple panels uplinks, or RRC parameters (e.g., groupBasedBeamReporting-v1900, etc.) for supporting multiple TRPs including UL only TRPs for simultaneous transmission of multiple panels uplinks, and a new SRS resource set including a resourceSetIndicator can be set as described in [Method 2] above, or a resourceSet-Indicator can be additionally set in the SRS resource set that was set with the RRC parameters.

[0594] [Option 2]

[0595] - The terminal can transmit an SRS for beam management purposes to the base station.

[0596] - The base station can receive an SRS for beam management purposes from the terminal.

[0597] - The base station can transmit a MAC CE to the terminal to update the SRS resources within the SRS resource set. The base station can update the SRS resources within the SRS resource set according to the SNR of the received SRS resources within the SRS resource set for beam management purposes. The MAC CE can be configured as shown in Fig. 13 below.

[0598] FIG. 13 is a diagram illustrating an example of a MAC CE format for updating an SRS resource within an SRS resource set. A base station may include a Serving Cell ID (1300) and a BWP ID (1301) in the MAC CE to indicate the serving cell where the SRS resource set is configured, in order to indicate the SRS resource set and the SRS resource to be updated. The base station may indicate the SRS resource set to be updated by an SRS Resource Set ID (1302), and in this case, a field to indicate the number of SRS resources included in the SRS resource set indicated by the SRS Resource Set ID may be configured as a 4-bit M field (1303). Depending on the value indicated by the M field (1303), an SRS Resource ID field (1304) to indicate a corresponding number of SRS resources may be defined. For example, if the value of the M field (1303) is set to 4-1=3 (or 0011 in bits), it means that 4 SRS resources are set within the SRS resource set indicated by the SRS Resource Set ID (1302), and the 4 SRS Resource ID fields (1304) can be configured from Oct 3 to Oct 6 of the MAC CE. If the value of the M field (1303) is set to 0, it means that 1 SRS resource is set within the SRS resource set indicated by the SRS Resource Set ID (1302). The base station can configure the L field (1305) within the MAC CE, and the L field (1305) can be used to update the resourceSetIndicator as described above in [Method 2].For example, if the L field (1305) is set to 0, the SRS resource set indicated by the SRS Resource Set ID within the MAC CE can be defined as the first channel measurement reference signal set, and if the L field (1305) is set to 1, the SRS resource set indicated by the SRS Resource Set ID within the MAC CE can be defined as the second channel measurement reference signal set.

[0599] FIG. 14a is a drawing illustrating the operation of a terminal according to a first embodiment of the present disclosure.

[0600] Referring to FIG. 14a, the terminal may receive an RRC message from the base station at step 1410. The RRC message may include a path loss difference value (e.g., pathloss offset) associated with the UL only TRP. Specifically, the base station may receive an uplink signal transmitted from the terminal via the UL only TRP, determine the path loss difference value based thereon, and transmit it to the terminal. For example, the base station may set a TCI state in the terminal that indicates the pathloss offset value. Additionally, the base station may update the pathloss offset using MAC CE. When the pathloss value is received via MAC CE, the terminal may override (or update) the value indicated by MAC CE as the pathloss value and use it.

[0601] Alternatively, the terminal may receive an RRC message from the base station containing candidates for path loss difference values. In such a case, the terminal may perform an uplink transmission based on the RRC message and the received DCI, and the path loss difference value may be determined based on the uplink transmission. Accordingly, in such a case, the path loss difference value may be indicated to the terminal via the DCI or MAC CE.

[0602] In addition, the terminal may receive the amount of change of the path loss difference value instead of the path loss difference value. For specific details, refer to Methods 3-1 to 3-4 and 4-1 to 4-4.

[0603] And, the terminal can check the path loss difference value based on the RRC message in step 1411.

[0604] In addition, the terminal may perform uplink transmission based on the path loss difference value in step 1412. At this time, the terminal may determine the transmission power by not applying the path loss difference value according to Method 2-1 or by applying the path loss difference value according to Method 2-2. Accordingly, the terminal may perform uplink transmission based on the determined transmission power. In addition, although not disclosed in this drawing, the terminal may receive a terminal capability request message from a base station and transmit terminal capability information to the base station. The specific details of the information included in the terminal capability information are the same as those described above and are therefore omitted below. In addition, if the base station has already received the terminal capability information, the procedure for transmitting the terminal capability information may be omitted.

[0605] FIG. 14b is a drawing illustrating the operation of a base station according to a first embodiment of the present disclosure.

[0606] Referring to FIG. 14b, the base station may transmit an RRC message to the terminal in step 1420. The RRC message may include a path loss difference value (e.g., pathloss offset) associated with the UL only TRP. Specifically, the base station may receive an uplink signal transmitted from the terminal via the UL only TRP, determine the path loss difference value based thereon, and transmit it to the terminal. For example, the base station may set a TCI state in the terminal that indicates the pathloss offset value. Additionally, the base station may update the pathloss offset using MAC CE. When the pathloss value is received via MAC CE, the terminal may override (or update) the value indicated by MAC CE as the pathloss value and use it.

[0607] Alternatively, the base station may transmit an RRC message to the terminal containing candidates for path loss difference values. In this case, the base station may receive an uplink signal based on the RRC message and the received DCI, and determine the path loss difference value based thereon. Accordingly, in this case, the base station may indicate the path loss difference value to the terminal via the DCI or MAC CE.

[0608] In addition, the base station may transmit the amount of change of the path loss difference value to the terminal instead of the path loss difference value. For specific details, refer to Methods 3-1 to 3-4 and 4-1 to 4-4.

[0609] In addition, the base station may receive an uplink signal based on the path loss difference value in step 1422. At this time, the base station may receive the uplink signal transmitted based on the transmission power determined by applying the path loss difference value according to Method 2-1 or by applying the path loss difference value according to Method 2-2. Additionally, although not disclosed in this drawing, the base station may receive terminal capability information from the terminal by transmitting a terminal capability request message to the terminal. The specific details of the information included in the terminal capability information are the same as those described above and are therefore omitted below. Furthermore, if the base station has already received the terminal capability information, the procedure for transmitting the terminal capability information may be omitted.

[0610] FIG. 15a is a drawing illustrating the operation of a terminal according to a second embodiment of the present disclosure.

[0611] Referring to FIG. 15a, the terminal can receive an RRC message from the base station at step 1510. The RRC message may include SRS configuration information (e.g., SRS-ResourceSet). Additionally, the RRC message may include RRC parameters to support simultaneous uplink transmission through multiple panels.

[0612] In addition, a list of SRS resource sets may be included in the CSI resource setting information included in the RRC message so that the terminal can report beam combinations (or beam groups) capable of simultaneous transmission to the base station. If multiple SRS resource sets are included in the list of SRS resource sets, one of the SRS resource sets included in the list may be defined as the first channel measurement reference signal set, and another SRS resource set may be defined as the second channel measurement reference signal set. Alternatively, srs-ResourceSetListExt may be additionally configured. Furthermore, as described above, when an SRS resource set is configured as a channel measurement reference signal set, one or more of the SRS resource sets whose usage is beamManagement may be configured as channel measurement reference signal sets. Specific details are the same as those described in Tables 26 to 28 and Method 1 above and are omitted below.

[0613] Alternatively, new RRC parameters may be set in the SRS configuration information included in the RRC message. For example, a parameter such as a resourceSet indicator may be added within the SRS-ResourceSet. If the indicator is 0, the corresponding SRS resource set indicates the first channel measurement reference signal set, and if the indicator is 1, the corresponding SRS resource set indicates the second channel measurement reference signal set. Additionally, if a resource set indicator is set for a single SRS-ResourceSet, nzp-CSI-RS-ResourceSetList or csi-SSB-ResourceSetList may be additionally set in the CSI resource configuration information, and if a resource set indicator is set for multiple SRS-ResourceSets, the CSI configuration information for group-based beam reporting may not be set. Specific details are the same as those described in Tables 29 to 30 and Method 2 above, and are omitted below.

[0614] And, the terminal may transmit an SRS based on the RRC message in step 1511. According to the above settings, the terminal may transmit a specific SRS to TRP1 and another SRS to TRP2. For example, one of the above-described channel measurement reference sets may be set for TRP1 and the other for TRP2. In this case, at least one of TRP1 or TRP2 may be a UL-only TRP.

[0615] Then, the terminal can transmit the CSI to the base station in step 1512. The terminal can transmit the CSI to the base station when it receives scheduling information from the base station to perform CSI reporting. The terminal can report the CSI to the base station by selecting up to four pairs of candidate combinations of RS (which may also include SRS) that can be transmitted simultaneously.

[0616] Meanwhile, if it is necessary to update the list of SRS resource sets included in the CSI resource setting information or to update the SRS-ResourceSet including the resourceSet indicator, the terminal may receive an RRC message containing the reset parameters. The specific details are the same as those described in Option 1.

[0617] Alternatively, the terminal may transmit a MAC CE to update (or reset) the SRS resource. Upon receiving the MAC CE, the base station may update (or reset) the SRS resource (Option 2). The specific structure of the MAC CE is the same as described in FIG. 13, so it is omitted below.

[0618] Meanwhile, although not illustrated in the drawing, the terminal may receive a terminal capability information request message from the base station and transmit the terminal capability information to the base station. For example, the terminal capability information may include information indicating whether simultaneous uplink transmission and / or simultaneous downlink reception is possible. Additionally, the terminal capability information may include information indicating whether group-based beam reporting is supported to support simultaneous transmission and / or simultaneous reception. However, the step of transmitting the terminal capability information may be omitted.

[0619] FIG. 15b is a drawing illustrating the operation of a base station according to a second embodiment of the present disclosure.

[0620] Referring to FIG. 15a, the base station can transmit an RRC message to the terminal. The RRC message may include SRS configuration information (e.g., SRS-ResourceSet). Additionally, the RRC message may include RRC parameters to support simultaneous uplink transmission through multiple panels.

[0621] In addition, the base station may receive an SRS based on the RRC message in step 1520. The SRS may be an SRS for beam management purposes. That is, the base station may receive an SRS based on a resource whose usage is set to beamManagement, which is included in the SRS-resourceSet. Furthermore, a list of SRS resource sets may be included in the CSI resource setting information included in the RRC message so that the terminal can report to the base station beam combinations (or beam groups) that can be transmitted simultaneously. If multiple SRS resource sets are included in the list of SRS resource sets, one of the SRS resource sets included in the list may be defined as the first channel measurement reference signal set, and another SRS resource set may be defined as the second channel measurement reference signal set. Alternatively, srs-ResourceSetListExt may be additionally configured. Also, as described above, when an SRS resource set is configured as a channel measurement reference signal set, one or more of the SRS resource sets whose usage is beamManagement may be configured as channel measurement reference signal sets. The specific details are the same as those described in Tables 26 to 28 and Method 1 above, and will be omitted below.

[0622] Alternatively, new RRC parameters may be set in the SRS configuration information included in the RRC message. For example, a parameter such as a resourceSet indicator may be added within the SRS-ResourceSet. If the indicator is 0, the corresponding SRS resource set indicates the first channel measurement reference signal set, and if the indicator is 1, the corresponding SRS resource set indicates the second channel measurement reference signal set. Additionally, if a resource set indicator is set for a single SRS-ResourceSet, nzp-CSI-RS-ResourceSetList or csi-SSB-ResourceSetList may be additionally set in the CSI resource configuration information, and if a resource set indicator is set for multiple SRS-ResourceSets, the CSI configuration information for group-based beam reporting may not be set. Specific details are the same as those described in Tables 29 to 30 and Method 2 above, and are omitted below.

[0623] And the base station can transmit an SRS based on an RRC message in step 1521. According to the above configuration, the base station can expect to receive a specific SRS through TRP1 and another SRS through TRP2. For example, one of the above-described channel measurement reference sets may be configured for TRP1 and the other for TRP2. In this case, at least one of TRP1 or TRP2 may be a UL-only TRP.

[0624] And the base station can receive the CSI from the terminal in step 1522. The base station transmits scheduling information for performing CSI reporting and can receive the CSI from the terminal. The CSI may include up to four pairs of candidate combinations of RS (which may also include SRS) that can be transmitted simultaneously.

[0625] Meanwhile, if the base station determines that it is necessary to update the list of SRS resource sets included in the CSI resource setting information or to update the SRS-ResourceSet including the resourceSet indicator, it may transmit an RRC message containing the reset parameters to the terminal. The specific details are the same as those described in Option 1.

[0626] Alternatively, the base station may receive a MAC CE to update (or reset) the SRS resource. Upon receiving the MAC CE, the base station may update (or reset) the SRS resource (Option 2). The specific structure of the MAC CE is the same as described in FIG. 13, so it is omitted below.

[0627] <Third Embodiment: CSI report format for reporting beam groups to support uplink multi-panel simultaneous transmission for UL only TRP>

[0628] A method for configuring CSI report information for reporting beam groups to support uplink multi-panel simultaneous transmission for a UL only TRP is described according to a second embodiment of the present disclosure. This embodiment may operate in combination with other embodiments described in the present disclosure.

[0629] As described above, to support uplink multi-panel simultaneous transmission for multiple TRPs including UL only TRPs, the terminal may report information regarding beam groups capable of simultaneous transmission to multiple panels to the base station. As described in the second embodiment, an SRS resource set may be configured as a resource set within CSI-ResourceConfig to direct a beam for an uplink transmission TRP. In this case, an SRS-ResourceSetId may be utilized to direct the SRS resource set, and one of the multiple SRS resources configured within the directed SRS resource set may be selected to direct a beam for the uplink transmission TRP corresponding to that resource set. Alternatively, a resource set within CSI-ResourceConfig may be utilized to direct a beam for an uplink transmission TRP, and in this case, an SRS-ResourceId for directing the SRS resource may be configured in a sequence form. In this case, one of the multiple SRS resources identified by multiple SRS-ResourceIds within the sequence may be selected to direct a beam for the uplink transmission TRP corresponding to that resource set. If the base station can simultaneously set RRC parameters to support mTRP including an uplink-only TRP in the terminal (e.g., one or more TCI-States including a path loss offset are set, or new RRC parameters to support mTRP including an uplink-only TRP are set in the terminal) and RRC parameters to support multi-panel simultaneous transmission (e.g., sTx_2panel or multipanelSchemeSDM or multipanelSchemeSFN, etc.).And as described in the second embodiment, the base station may set together RRC parameters (groupBasedBeamReporting_vxxxx (where xxxx is a four-digit number to indicate support for additional functions, such as introduction releases) and an SRS resource set or a resource set setting including an SRS resource, etc.) for reporting a beam combination for uplink simultaneous transmission to the terminal.

[0630] When the above RRC parameters are configured in the terminal, the terminal may perform group-based beam reporting to the base station to simultaneously transmit uplink channels using a multi-panel simultaneous transmission technique with an mTRP including an uplink transmission TRP. In this case, the format of the CSI report information for the group-based beam reporting that the terminal reports to the base station may be configured as follows.

[0631] [Table 31]

[0632]

[0633] [Table 32]

[0634]

[0635] Here, the CRI, SSBRI, RSRP, and Differential RSRP, etc., in Tables 31 and 32 can be defined in the same way as previously described in Tables 23 and 24. The SRI in Tables 31 and 32 may refer to an SRS resource within an SRS resource set configured in a resource set, or the index of an SRS resource configured in a resource set. If SRI is 0, it may refer to the first SRS resource configured among the SRS resources within the configured SRS resource set, or it may refer to the first SRS resource configured among the SRS resources configured in the resource set. If SRI is 1, it may refer to the second SRS resource configured among the SRS resources within the configured SRS resource set, or it may refer to the second SRS resource configured among the SRS resources configured in the resource set. The number of bits in the SRI area is of Table 32. It can be defined as, It can be defined as the number of SRS resources within the SRS resource set configured in the resource set or the number of SRS resources configured in the resource set. or or It can be defined as the number of NZP-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet or the number of SSB-Indexes in the CSI-SSB-ResourceSet or the number of SRS-Resources in the SRS resource set or the list of SRS resources included in the corresponding resource set to select the first beam and the second beam of each resource group.The number of resources set in Resource set 0 (e.g., NZP-CSI-RS-ResourceSet identified according to the first NZP-CSI-RS-ResourceSetId set in CSI-ResourceConfig or CSI-SSB-ResourceSet identified according to the CSI-SSB-ResourceSetId set in csi-SSB-ResourceSetList or SRS-ResourceSet identified according to the first SRS-ResourceSetId set in CSI-ResourceConfig according to the second embodiment or an SRS-ResourceSet among which the resourceSet-Indicator is set to 0, etc.) and Resource set 1 (e.g., NZP-CSI-RS-ResourceSet identified according to the second NZP-CSI-RS-ResourceSetId set in CSI-ResourceConfig or CSI-SSB-ResourceSetId identified according to the second csi-SSB-ResourceSetList or csi-SSB-ResourceSetListExt) The number of resources set in CSI-SSB-ResourceSet or SRS-ResourceSet identified by the second SRS-ResourceSetId set in CSI-ResourceConfig according to the second embodiment, such as an SRS-ResourceSet where the resourceSet-Indicator is set to 1, may be the same or may not be the same. If the number of resources in the two resource sets is the same, the number of bits of the two CRIs, SSBRIs, and SRIs in each resource group of Table 31 is the same. If the number of resources in the two resource sets is not the same, the number of bits of the two CRIs, SSBRIs, and SRIs in each resource group of Table 31 may be different.At this time, after indicating whether the first resource set in the resource group is resource set 0 or resource set 1 according to the Resource set indicator, the CRI, SSBRI, and SRI regions for indicating the beam selected from the resource set determined according to the Resource set indicator are placed as the first region in the resource group, and the CRI, SSBRI, and SRI regions for indicating the beam selected from the other resource set are placed as the second region to construct a bit sequence.

[0636] Meanwhile, although not illustrated in the drawing, the terminal may receive a terminal capability information request message from the base station and transmit the terminal capability information to the base station. For example, the terminal capability information may include information indicating whether simultaneous uplink transmission and / or simultaneous downlink reception is possible. Additionally, the terminal capability information may include information indicating whether group-based beam reporting is supported to support simultaneous transmission and / or simultaneous reception. However, the step of receiving the terminal capability information may be omitted.

[0637] The above-described flowchart illustrates an exemplary method that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart of the present disclosure. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0638] FIG. 16 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0639] Referring to FIG. 16, the terminal may include a transceiver (referring to a terminal receiver (16-00) and a terminal transmitter (16-10)), a memory (not shown), and a terminal processing unit (16-05, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver (16-00, 16-10), memory, and terminal processing unit (16-05) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of a single chip.

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

[0641] In addition, the transceiver receives a signal through a wireless channel and outputs it to a processor, and can transmit the signal output from the processor through a wireless channel.

[0642] Memory can store programs and data necessary for the operation of the terminal. Additionally, memory can store control information or data included in signals transmitted and received by the terminal. Memory may be composed of storage media or combinations of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.

[0643] Additionally, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiment. For example, the processor can receive a DCI composed of two layers and control the components of the terminal to receive multiple PDSCHs simultaneously. There may be multiple processors, and the processors can perform the operation of controlling the components of the terminal by executing a program stored in memory.

[0644] FIG. 17 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

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

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

[0647] In addition, the transceiver receives a signal through a wireless channel and outputs it to a processor, and can transmit the signal output from the processor through a wireless channel.

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

[0649] Memory can store programs and data necessary for the operation of the base station. Additionally, memory can store control information or data included in signals transmitted and received by the base station. Memory can be composed of storage media or combinations of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.

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

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

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

[0653] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0654] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

[0655] In the specific embodiments of the present disclosure described above, the components included in the embodiments are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0656] Meanwhile, the embodiments of the present disclosure disclosed in the drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding 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 concept of the present disclosure are possible. Furthermore, each of the above embodiments may be combined and operated as needed. For example, a base station and a terminal may be operated by combining parts of one embodiment of the present disclosure with parts of another embodiment. For example, a base station and a terminal may be operated by combining parts of the first embodiment and the second embodiment of the present disclosure. In addition, other variations based on the technical concept of the above embodiments may be implemented in other systems, such as FDD LTE systems, TDD LTE systems, 5G or NR systems.

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

[0658] Alternatively, drawings describing the method of the present disclosure may omit some components and include only some components to the extent that the essence of the present disclosure is not impaired.

[0659] Additionally, the method of the present disclosure may be implemented by combining some or all of the contents included in each embodiment to the extent that it does not impair the essence of the present disclosure.

[0660] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only and is not limited to the embodiments disclosed. Those skilled in the art will understand that other specific forms can be easily modified without altering the technical spirit or essential features of the present disclosure. The scope of the present disclosure is defined by the claims set forth below rather than by the foregoing detailed description, and all modifications or variations derived from the meaning and scope of the claims and equivalent concepts should be interpreted as being included within the scope of the present disclosure.

Claims

1. In the method of the terminal, A step of receiving sounding reference signal (SRS) information related to simulanteous transmission with multi-panel (STxMP) from a base station; A step of identifying a first SRS resource set corresponding to a first TRP based on the above STxMP-related SRS information; A step of transmitting first SRSs to the first TRP based on the first SRS resource set; and The method includes the step of reporting channel state information (CSI) regarding beam combination candidates for STxMP to the base station. The CSI for the beam combination candidates for the STxMP above includes a combination of the CSI based on the first SRSs and the CSI related to the second TRP, and A method characterized in that at least one of the first TRP or the second TRP supports only uplink reception for the terminal.

2. In Paragraph 1, A step of identifying a second SRS resource set corresponding to the second TRP based on the STxMP-related SRS information; The method further includes the step of transmitting second SRSs to the second TRP based on the second SRS resource set, and A method characterized in that the CSI associated with the above-mentioned second TRP is based on the above-mentioned second SRSs.

3. In Paragraph 1, The above STxMP-related SRS information is: Set as an RRC parameter in CSI-ResourceConfig or It is set as an RRC parameter within SRS-ResourceSet, and A method characterized in that the first SRS resource set corresponding to the first TRP is identified by an SRS resource set related ID (identifier) ​​included in the STxMP related information or an SRS resource set related indicator included in the STxMP related information.

4. In Paragraph 1, The method further includes the step of transmitting STxMP-related terminal capability information to the base station, The above STxMP-related terminal capability information is: Whether the above terminal supports STxMP or Whether group-based beam reporting is supported to support the above STxMP A method characterized by including at least one of the following.

5. Regarding the base station method, A step of transmitting sounding reference signal (SRS) information related to simulanteous transmission with multi-panel (STxMP) to a terminal; and The method includes the step of receiving channel state information (CSI) regarding beam combination candidates for STxMP from the terminal, and The first SRS resource set is identified based on the STxMP-related SRS information, and Based on the above first SRS resource set, the first SRSs are transmitted to the first TRP, and The CSI for the beam combination candidates for the STxMP above includes a combination of the CSI based on the first SRSs and the CSI related to the second TRP, and A method characterized in that at least one of the first TRP or the second TRP supports only uplink reception for the terminal.

6. In Paragraph 5, The second SRS resource set is identified based on the STxMP-related SRS information, and Based on the above second SRS resource set, the second SRSs are transmitted to the second TRP, and A method characterized in that the CSI associated with the above-mentioned second TRP is based on the above-mentioned second SRSs.

7. In Paragraph 5, The above STxMP-related SRS information is: Set as an RRC parameter in CSI-ResourceConfig or It is set as an RRC parameter within SRS-ResourceSet, and A method characterized in that the first SRS resource set corresponding to the first TRP is identified by an SRS resource set related ID (identifier) ​​included in the STxMP related information or an SRS resource set related indicator included in the STxMP related information.

8. In Paragraph 5, The method further includes the step of receiving STxMP-related terminal capability information from the above terminal, The above STxMP-related terminal capability information is: Whether the above terminal supports STxMP or Whether group-based beam reporting is supported to support the above STxMP A method characterized by including at least one of the following.

9. Regarding the terminal, Transmitter / receiver; and Receive SRS (sounding reference signal) information related to simulanteous transmission with multi-panel (STxMP) from the base station, and Based on the above STxMP-related SRS information, identify the first SRS resource set corresponding to the first TRP, and To the first TRP, transmit the first SRSs based on the first SRS resource set, and The control unit configured to report channel state information (CSI) regarding beam combination candidates for STxMP to the base station, and The CSI for the beam combination candidates for the STxMP above includes a combination of the CSI based on the first SRSs and the CSI related to the second TRP, and A terminal characterized in that at least one of the first TRP or the second TRP supports only uplink reception for the terminal.

10. In Paragraph 9, The above control unit is: Based on the STxMP-related SRS information above, identify a second SRS resource set corresponding to the second TRP, and The above-mentioned second TRP is further configured to transmit second SRSs based on the above-mentioned second SRS resource set, and A terminal characterized in that the CSI associated with the above-mentioned second TRP is based on the above-mentioned second SRSs.

11. In Paragraph 9, The above STxMP-related SRS information is: Set as an RRC parameter in CSI-ResourceConfig or It is set as an RRC parameter within SRS-ResourceSet, and A terminal characterized in that the first SRS resource set corresponding to the first TRP is identified by an SRS resource set related ID (identifier) ​​included in the STxMP related information or an SRS resource set related indicator included in the STxMP related information.

12. In Paragraph 9, The above control unit is: It is further configured to transmit STxMP-related terminal capability information to the above base station, and The above STxMP-related terminal capability information is: Whether the above terminal supports STxMP or Whether group-based beam reporting is supported to support the above STxMP A terminal characterized by including at least one of the following.

13. Regarding base stations, Transmitter / receiver; and Transmitting sounding reference signal (SRS) information related to simulanteous transmission with multi-panel (STxMP) to a terminal, and It includes a control unit configured to receive channel state information (CSI) regarding beam combination candidates for STxMP from the above terminal, and The first SRS resource set is identified based on the STxMP-related SRS information, and Based on the above first SRS resource set, the first SRSs are transmitted to the first TRP, and The CSI for the beam combination candidates for the STxMP above includes a combination of the CSI based on the first SRSs and the CSI related to the second TRP, and A base station characterized in that at least one of the first TRP or the second TRP supports only uplink reception for the terminal.

14. In Paragraph 13, The second SRS resource set is identified based on the STxMP-related SRS information, and Based on the above second SRS resource set, the second SRSs are transmitted to the second TRP, and A base station characterized by the CSI associated with the above-mentioned second TRP being based on the above-mentioned second SRSs.

15. In Paragraph 13, The above STxMP-related SRS information is: Set as an RRC parameter in CSI-ResourceConfig or It is set as an RRC parameter within SRS-ResourceSet, and A base station characterized in that the first SRS resource set corresponding to the first TRP is identified by an SRS resource set related ID (identifier) ​​included in the STxMP related information or an SRS resource set related indicator included in the STxMP related information.

Images