Method and apparatus for uplink data repetition in network cooperative communications

Abstract

The present disclosure relates to a communication technique and a system for integrating a 5G communication system with IoT technology to support higher data transmission rates than those of 4G systems. The present disclosure may be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. According to various embodiments of the present disclosure, a method for repeatedly transmitting and receiving uplink data in a network cooperative communication system and an apparatus capable of performing the same are provided.

Description

Technology Field

[0001] The present disclosure relates to a method and apparatus for repeatedly transmitting and receiving uplink data in a network cooperative communication system. Background Technology

[0002] Efforts are being made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems. For this reason, 5G or pre-5G communication systems are referred to as systems beyond the 4G network or systems following the LTE system. To achieve high data transmission rates, the implementation of 5G communication systems in the mmWave band (e.g., the 60 GHz band) is being considered. To mitigate path loss and increase transmission distance in the mmWave band, technologies such as beamforming, massive MIMO, full Dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antennas are being discussed for 5G communication systems. In addition, to improve the network of the system, the development of technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation is taking place in 5G communication systems.In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access), are being developed in 5G systems.

[0003] Meanwhile, the Internet is evolving from a human-centered network where humans generate and consume information into an IoT (Internet of Things) network where distributed components, such as objects, exchange and process information. IoE (Internet of Everything) technology, which combines IoT with Big Data processing technologies through connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; consequently, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are currently being researched to facilitate the connection of objects. In an IoT environment, intelligent IT services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT technologies with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0004] Accordingly, various attempts are being made to apply 5G communication systems (5th generation communication systems or New Radio (NR)) to IoT networks. For example, technologies such as sensor networks, Machine to Machine (M2M), and Machine Type Communication (MTC) are being implemented using 5G communication technologies such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN) as the big data processing technology described earlier can also be considered an example of the convergence of 3eG and IoT technologies.

[0005] As a result of the aforementioned development and advancements in wireless communication systems, it has become possible to provide various services, and thus measures are required to provide these services smoothly. The problem to be solved

[0006] Through various embodiments of the present disclosure, we aim to provide an apparatus and method capable of effectively providing services in a mobile communication system. means of solving the problem

[0007] 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. Effects of the invention

[0008] According to various embodiments of the present disclosure, a method for repeatedly transmitting and receiving uplink data in a network cooperative communication system and an apparatus capable of performing the same are provided. Through this, improved performance gains can be obtained. Brief explanation of the drawing

[0009] 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. 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. 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. FIG. 4 is a diagram illustrating an example of setting a control area of ​​a downlink control channel in a wireless communication system according to one embodiment of the present disclosure. FIG. 5a is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure. FIG. 5b is a diagram illustrating, through a Span, a case in which a terminal in a wireless communication system according to one embodiment of the present disclosure may have a plurality of PDCCH (physical downlink control channel) monitoring positions within a slot. FIG. 6 is a diagram illustrating an example of a DRX (discontinuous reception) operation in a wireless communication system according to an embodiment of the present disclosure. FIG. 7 is a diagram illustrating an example of base station beam allocation according to the TCI (transmission configuration indication) state setting in a wireless communication system according to one embodiment of the present disclosure. FIG. 8 is a diagram illustrating an example of a method for allocating a TCI state to a PDCCH in a wireless communication system according to an embodiment of the present disclosure. FIG. 9 is a diagram illustrating a TCI indication MAC (medium access control) CE (control element) signaling structure for a PDCCH DMRS (demodulation reference signal) in a wireless communication system according to one embodiment of the present disclosure. FIG. 10 is a drawing illustrating an example of CORESET and search space beam settings in a wireless communication system according to one embodiment of the present disclosure. FIG. 11 is a diagram illustrating an example of frequency axis resource allocation of a PDSCH in a wireless communication system according to one embodiment of the present disclosure. FIG. 12 is a diagram illustrating an example of time axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure. FIG. 13a is a diagram illustrating an example of time-axis resource allocation according to the subcarrier interval of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure. FIG. 13b illustrates an example of PUSCH repeat transmission type B in a wireless communication system according to one embodiment of the present disclosure. FIG. 14 is a diagram illustrating the wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation (CA), and dual connectivity (DC) situation in a wireless communication system according to one embodiment of the present disclosure. FIG. 15 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. FIG. 16 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. FIG. 17 illustrates the operation of a base station and a terminal for PUSCH repetitive transmission considering a single DCI transmission-based multiple TRP having a plurality of SRI or TPMI fields according to one embodiment of the present disclosure. FIG. 18 illustrates the operation of a base station and a terminal for PUSCH repetitive transmission considering a single DCI transmission-based multiple TRP using an enhanced SRI and TPMI field according to one embodiment of the present disclosure. FIG. 19 is a diagram illustrating a method for independently determining frequency hopping and transmission beam mapping during PUSCH iterative transmission considering multiple TRPs according to one embodiment of the present disclosure. FIG. 20 is a diagram illustrating a transmission beam mapping unit setting based on a frequency hopping unit setting according to one embodiment of the present disclosure. FIG. 21 is a drawing illustrating an example of an uplink-downlink configuration (UL / DL configuration) in a wireless communication system according to one embodiment of the present disclosure. FIG. 22 is a diagram illustrating various transmission beam mapping methods according to slot format for dynamic grant-based PUSCH iterative transmission according to one embodiment of the present disclosure. FIG. 23a is a diagram illustrating the operation of a terminal for transmission beam mapping considering a slot format according to one embodiment of the present disclosure. FIG. 23b is a diagram illustrating the operation of a base station for transmission beam mapping considering a slot format according to one embodiment of the present disclosure. FIG. 24 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure. FIG. 25 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure. Specific details for implementing the invention

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

[0011] In describing the embodiments, technical details that are well known in the technical field 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.

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

[0013] 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 specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of related functions or configurations 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 specification.

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

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

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

[0017] 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 may be configured to run one or more processors. Accordingly, 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. Furthermore, in the embodiment, the 'part' may include one or more processors.

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

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

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

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

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

[0023] Finally, URLLC is a mission-critical cellular-based wireless communication service. Examples include 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 require a packet error rate of 10⁻⁵ or less. Consequently, for services supporting URLLC, 5G systems must provide a smaller Transmit Time Interval (TTI) than other services, and design considerations may be required to allocate wide resources within the frequency band to ensure the reliability of the communication link.

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

[0025] [NR Time-Frequency Resources]

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

[0027] FIG. 1 is a diagram illustrating the basic structure of the time-frequency domain, which is a wireless resource domain in which data or a control channel is transmitted in a wireless communication system according to one embodiment of the present disclosure.

[0028] 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, 1-01), which can be defined as one OFDM (Orthogonal Frequency Division Multiplexing) symbol (1-02) on the time axis and one subcarrier (1-03) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can form a single resource block (Resource Block, RB, 1-04).

[0029] FIG. 2 is a drawing illustrating a slot structure considered in a wireless communication system according to one embodiment of the present disclosure.

[0030] 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 set as the subcarrier spacing value are illustrated. 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.

[0031] [Table 1]

[0032]

[0033] [Bandwidth Section (BWP)]

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

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

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

[0037] [Table 2]

[0038]

[0039] 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 higher-layer signaling, for example, RRC (radio resource control) 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 DCI (downlink control information).

[0040] According to some embodiments, prior to the RRC (radio resource control) 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 (which may correspond to remaining system information, RMSI, or system information block 1, SIB1). The control resource set and the 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.

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

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

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

[0044] In addition, according to some embodiments, a base station may set bandwidth portions with 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 unnecessary downlink control channels using a large bandwidth of 100 MHz may be very inefficient in terms of power consumption. To reduce the power consumption of the terminal, the base station may set a bandwidth portion with 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.

[0045] In the method for setting the above bandwidth part, terminals prior to RRC connection can receive setting 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 set 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.

[0046] [SS / PBCH Block]

[0047] Next, we will explain the SS (synchronization signal) / PBCH block in 5G.

[0048] An SS / PBCH block may refer to a physical layer channel block composed of PSS (primary SS), SSS (secondary SS), and PBCH (physical broadcast channel). Specifically, it is as follows.

[0049] - PSS: A signal that serves as the reference for downlink time / frequency synchronization and provides some information about the cell ID.

[0050] - SSS: Serves as the reference for downlink time / frequency synchronization and provides the remaining cell ID information not provided by PSS. Additionally, it can serve as a reference signal for PBCH demodulation.

[0051] - PBCH: Provides essential system information required for transmitting and receiving data channels and control channels of the terminal. The essential system information may include search space-related control information representing wireless resource mapping information of the control channel, scheduling control information for a separate data channel that transmits system information, etc.

[0052] - SS / PBCH block: An SS / PBCH block is composed of a combination of PSS, SSS, and PBCH. One or more SS / PBCH blocks may be transmitted within a time of 5ms, and each transmitted SS / PBCH block may be distinguished by an index.

[0053] The terminal can detect PSS and SSS during the initial connection phase and can decode PBCH. It can obtain MIB from PBCH and receive a Control Resource Set (CORESET) #0 from it (which may correspond to a control resource set with a control resource index of 0). The terminal can perform monitoring of Control Resource Set #0 by assuming that the selected SS / PBCH block and the demodulation reference signal (DMRS) transmitted from Control Resource Set #0 are quasi-co-located (QCL). The terminal can receive system information using downlink control information transmitted from Control Resource Set #0. The terminal can obtain configuration information related to the random access channel (RACH) required for initial connection from the received system information. The terminal can transmit a physical RACH (PRACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information regarding the SS / PBCH block index selected by the terminal. The base station can know that the terminal has selected a block among the respective SS / PBCH blocks and is monitoring the associated control area #0.

[0054] [DRX]

[0055] FIG. 6 is a diagram illustrating an example of a discontinuous reception (DRX) operation in a wireless communication system according to an embodiment of the present disclosure.

[0056] DRX (discontinuous reception) is an operation in which a terminal using a service receives data discontinuously while in an RRC connected state, where a wireless link is established between the base station and the terminal. When DRX is applied, the terminal can turn on the receiver at specific points to monitor the control channel, and turn off the receiver if no data is received for a certain period to reduce the terminal's power consumption. DRX operation can be controlled by a MAC layer device based on various parameters and timers.

[0057] Referring to FIG. 6, Active time (605) is the time during which the terminal wakes up at each DRX cycle to monitor the PDCCH. Active time (605) can be defined as follows.

[0058]

[0059] Here, drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, ra-ContentionResolutionTimer, etc. are timers whose values ​​are set by the base station, and have the function of setting the terminal to monitor the PDCCH when certain conditions are satisfied.

[0060] drx-onDurationTimer (615) is a parameter for setting the minimum time the terminal stays awake in the DRX cycle. drx-InactivityTimer (620) is a parameter for setting the additional time the terminal stays awake when receiving a PDCCH (630) instructing a new uplink transmission or downlink transmission. drx-RetransmissionTimerDL is a parameter for setting the maximum time the terminal stays awake to receive a downlink retransmission in the downlink HARQ procedure. drx-RetransmissionTimerUL is a parameter for setting the maximum time the terminal stays awake to receive an uplink retransmission grant in the uplink HARQ procedure. drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, and drx-RetransmissionTimerUL can be set, for example, to time, number of subframes, number of slots, etc. ra-ContentionResolutionTimer is a parameter for monitoring the PDCCH in the random access procedure.

[0061] The inActive time (610) is the time during which the PDCCH is not monitored or / or the PDCCH is not received during the DRX operation. The remaining time after subtracting the Active time (605) from the total time of performing the DRX operation may be the inActive time (610). If the terminal does not monitor the PDCCH during the Active time (605), it may enter a sleep or inActive state to reduce power consumption.

[0062] The DRX cycle refers to the period during which a terminal wakes up and monitors the PDCCH. In other words, it refers to the time interval or on-duration occurrence cycle between when the terminal monitors a PDCCH and when it monitors the next PDCCH. There are two types of DRX cycles: short DRX cycle and long DRX cycle. The short DRX cycle can be applied optionally.

[0063] Long DRX cycle (625) is the longer of the two DRX cycles set in the terminal. While operating as Long DRX, the terminal restarts drx-onDurationTimer (615) at a point where Long DRX cycle (625) has elapsed from the starting point (e.g., start symbol) of drx-onDurationTimer (615). When operating as Long DRX cycle (625), the terminal may start drx-onDurationTimer (615) in a slot after drx-SlotOffset in a subframe satisfying Equation 1 below. Here, drx-SlotOffset refers to the delay before starting drx-onDurationTimer (615). drx-SlotOffset can be set, for example, as time, the number of slots, etc.

[0064] [Mathematical Formula 1]

[0065]

[0066] At this time, drx-LongCycleStartOffset can be used to define the subframe to start the Long DRX cycle (625) and drx-StartOffset can be used to define the subframe to start the Long DRX cycle (625). drx-LongCycleStartOffset can be set, for example, to time, number of subframes, number of slots, etc.

[0067] [PDCCH: DCI related]

[0068] Next, downlink control information (DCI) in 5G systems will be explained in detail.

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

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

[0071] For example, a DCI scheduling a PDSCH for system information (SI) can be scrambled to SI-RNTI. A DCI scheduling a PDSCH for a random access response (RAR) message can be scrambled to RA-RNTI. A DCI scheduling a PDSCH for a paging message can be scrambled to P-RNTI. A DCI notifying a slot format indicator (SFI) can be scrambled to SFI-RNTI. A DCI notifying a 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).

[0072] 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 following information.

[0073] [Table 3]

[0074]

[0075] DCI format 0_1 ​​can be used as a non-defense DCI for scheduling PUSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI may include, for example, the following information.

[0076] [Table 4]

[0077]

[0078]

[0079]

[0080] DCI format 1_0 can be used as a countermeasure DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI may include, for example, the following information.

[0081] [Table 5]

[0082]

[0083] 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 following information.

[0084] [Table 6]

[0085]

[0086]

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

[0088] In the following, the downlink control channel in a 5G communication system will be explained in more detail with reference to the drawings.

[0089] FIG. 4 illustrates an example of a control resource set (CORESET) setting in which a downlink control channel is transmitted in a wireless communication system according to an embodiment of the present disclosure. FIG. 4 illustrates an example in which two control resources (control resource #1 (401), control resource #2 (402)) are set within a terminal bandwidth part (UE bandwidth part) (410) on the frequency axis and one slot (420) on the time axis. The control resources (401, 402) may be set in a specific frequency resource (403) within the entire terminal bandwidth part (410) on the frequency axis. On the time axis, they may be set with one or more OFDM symbols and can be defined as the control resource set duration (404). Referring to the example illustrated in FIG. 4, control resource #1 (401) is set with a control resource set duration of 2 symbols, and control resource #2 (402) is set with a control resource set duration of 1 symbol.

[0090] The control domain in the aforementioned 5G can be configured by a base station to a terminal via upper-layer signaling (e.g., system information, MIB (master information block), RRC (radio resource control) signaling). Configuring a control domain to a terminal means providing information such as a control domain identifier (Identity), the frequency location of the control domain, and the symbol length of the control domain. For example, it may include the following information.

[0091] [Table 7]

[0092]

[0093]

[0094] In Table 7, the tci-StatesPDCCH (hereinafter referred to as the TCI (transmission configuration indication) state) configuration information may include information on one or more SS (synchronization signal) / PBCH (physical broadcast channel) block indices or CSI-RS (channel state information reference signal) indices that are in a quasi-co-located relationship with the DMRS transmitted in the corresponding control area.

[0095] FIG. 5a is a diagram showing an example of a basic unit of time and frequency resources that can be used in a wireless communication system according to an embodiment of the present disclosure. According to FIG. 5a, the basic unit of time and frequency resources that constitute the control channel can be called a REG (resource element group, 503), and the REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (physical resource block, 502) on the frequency axis, that is, 12 subcarriers. A base station can concatenate REGs (503) to form a downlink control channel allocation unit.

[0096] As illustrated in FIG. 5a, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (control channel element, 504), then 1 CCE (504) can be composed of multiple REGs (503). For example, if the REG (503) illustrated in FIG. 5 is described, the REG (503) can be composed of 12 REs, and if 1 CCE (504) is composed of 6 REGs (503), then 1 CCE (504) can be composed of 72 REs. When a downlink control area is established, the area can be composed of multiple CCEs (504), and a specific downlink control channel can be mapped to one or multiple CCEs (504) and transmitted according to the aggregation level (AL) within the control area. The CCEs (504) within the control area are distinguished by numbers, and the numbers of the CCEs (504) can be assigned according to a logical mapping method.

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

[0098] Search spaces can be classified into common search spaces and UE-specific search spaces. A certain group of terminals or all terminals may examine the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling or paging messages regarding system information. For example, PDSCH scheduling allocation information for the transmission of SIBs containing cell operator information can be received by examining the common search space of the PDCCH. In the case of the common search space, since a certain group of terminals or all terminals must receive the PDCCH, it can be defined as a set of pre-agreed CCEs. Scheduling allocation information for a UE-specific PDSCH or PUSCH can be received by examining the UE-specific search space of the PDCCH. The UE-specific search space can be defined specifically as a function of the terminal's identity and various system parameters.

[0099] In 5G, parameters for the search space for a PDCCH can be configured from the base station to the terminal via upper-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station may configure the terminal the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the occasion for monitoring in slot-symbol units for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the search space, and the control domain index to be monitored in the search space. For example, the following information may be included.

[0100] [Table 8]

[0101]

[0102]

[0103]

[0104] According to the configuration information, the base station may set one or multiple sets of search spaces for the terminal. According to some embodiments, the base station may set search space set 1 and search space set 2 for the terminal, and may set DCI format A scrambled with X-RNTI in search space set 1 to be monitored in a common search space, and may set DCI format B scrambled with Y-RNTI in search space set 2 to be monitored in a terminal-specific search space.

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

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

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

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

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

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

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

[0112] In terminal-specific search spaces, the following combinations of DCI formats and RNTI can be monitored. Of course, they are not limited to the examples below.

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

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

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

[0116] C-RNTI (Cell RNTI): Used for terminal-specific PDSCH scheduling

[0117] TC-RNTI (Temporary Cell RNTI): Used for terminal-specific PDSCH scheduling

[0118] CS-RNTI (Configured Scheduling RNTI): Used for semi-statically configured terminal-specific PDSCH scheduling.

[0119] RA-RNTI (Random Access RNTI): Used for PDSCH scheduling during the random access phase

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

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

[0122] INT-RNTI (Interruption RNTI): Used to indicate whether PDSCH is pucturing.

[0123] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to instruct power control commands to the PUSCH

[0124] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to instruct power control commands to the PUCCH

[0125] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to instruct power regulation commands to the SRS

[0126] The aforementioned specified DCI formats may follow the definitions below.

[0127] [Table 9]

[0128]

[0129] In 5G, the search space of aggregation level L in the control domain p and search space set s can be expressed as Equation 2 below.

[0130] [Mathematical Formula 2]

[0131]

[0132] - L: Lamination Level

[0133] - : Carrier Index

[0134] - NCCE,p: Total number of CCEs existing within control domain p

[0135] - ,f: slot index

[0136] - M(L)p,s,max: Number of PDCCH candidates for assembly level L

[0137] - msnCI = 0, … , M(L)p,s,max -1: PDCCH candidate index of aggregation level L

[0138] - i = 0, … , L-1

[0139] -

[0140] - nRNTI: Terminal identifier

[0141] Y_(p, The value of ,f) can be 0 in the case of a common search space.

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

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

[0144] [PDCCH: span]

[0145] A terminal can perform terminal capability reporting for cases where it has multiple PDCCH monitoring locations within a slot at each subcarrier interval, and in this case, the concept of a Span can be used. A Span refers to a sequence of consecutive symbols within a slot through which the terminal can monitor a PDCCH, and each PDCCH monitoring location is within one Span. A Span can be expressed as (X,Y), where x represents the minimum number of symbols that must be separated between the first symbols of two consecutive Spans, and Y represents the number of consecutive symbols through which a PDCCH can be monitored within one Span. In this case, the terminal can monitor a PDCCH within a Span in a range of Y symbols from the first symbol of the Span.

[0146] FIG. 5b is a diagram illustrating, through a Span, a case in which a terminal in a wireless communication system can have multiple PDCCH monitoring locations within a slot. The Span can be (X,Y) = (7,4), (4,3), or (2,2), and each of the three cases is represented as (5b-00), (5b-05), and (5b-10) in FIG. 5b. For example, (5b-00) represents a case where there are two Spans within the slot that can be represented as (7,4). The spacing between the first symbols of the two Spans is represented as X=7, and PDCCH monitoring locations can exist within a total of Y=3 symbols from the first symbol of each Span, and it is indicated that search spaces 1 and 2 exist respectively within Y=3 symbols. As another example, (5b-05) shows a case where there are a total of 3 spans in the slot that can be expressed as (4,3), and the distance between the second and third spans is shown to be X'=5 symbols greater than X=4.

[0147] [PDCCH: Terminal Capability Report]

[0148] The slot locations where the aforementioned common search space and terminal-specific search space are located are indicated by the monitoringSymbolsWithinSlot parameter in Table 10-1, and the symbol locations within the slot are indicated by a bitmap through the monitoringSymbolsWithinSlot parameter in Table 9. Meanwhile, the symbol locations within the slot where the terminal can monitor the search space can be reported to the base station through the following terminal capabilities (UE capabilities).

[0149] - Terminal Capability 1 (hereinafter referred to as FG 3-1). This terminal capability refers to the capability to monitor a monitoring occasion (MO) when that MO is located within the first 3 symbols of the slot, provided that there is one monitoring occasion for a Type 1 and Type 3 common search space or a terminal-specific search space within the slot, as shown in Table 10-1 below. This terminal capability is a mandatory capability that all terminals supporting NR must support, and whether this capability is supported is not explicitly reported to the base station.

[0150] [Table 10-1]

[0151]

[0152] - Terminal capability 2 (hereinafter referred to as FG 3-2). This terminal capability refers to the capability to monitor regardless of the starting symbol position of a monitoring occasion (MO) for a common search space or a terminal-specific search space, as shown in Table 10-2 below, when there is one monitoring occasion (MO) within the slot. This terminal capability is optional for the terminal to support, and whether this capability is supported is explicitly reported to the base station.

[0153] [Table 10-2]

[0154]

[0155] - Terminal Capability 3 (hereinafter referred to as FG 3-5, 3-5a, and 3-5b). This terminal capability indicates a pattern of monitoring occasions (MOs) that the terminal can monitor when multiple monitoring occasions exist within a slot for a common search space or a terminal-specific search space, as shown in Table 10-3 below. The aforementioned pattern consists of an interval X between start symbols of different MOs and a maximum symbol length Y for one MO. The combinations of (X,Y) supported by the terminal may be one or more of {(2,2), (4,3), (7,3)}. This terminal capability is optional for the terminal to support, and whether this capability is supported and the aforementioned combinations of (X,Y) are explicitly reported to the base station.

[0156] [Table 10-3]

[0157]

[0158]

[0159]

[0160]

[0161] The terminal may report to the base station whether it supports the aforementioned terminal capability 2 and / or terminal capability 3 and related parameters. Based on the reported terminal capability, the base station may perform time-axis resource allocation for a common search space and a terminal-specific search space. When allocating resources, the base station may ensure that the MO is not placed in a location where the terminal cannot monitor.

[0162] [PDCCH: BD / CCE limit]

[0163] When multiple sets of search spaces are configured for a terminal, the following conditions may be considered in determining the set of search spaces that the terminal must monitor.

[0164] If the terminal receives the value of monitoringCapabilityConfig-r16, which is an upper layer signaling, as r15monitoringcapability, the terminal defines the maximum value for the number of PDCCH candidates that can be monitored and the number of CCEs constituting the entire search space (where the entire search space refers to the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per slot, and if the value of monitoringCapabilityConfig-r16 is received as r16monitoringcapability, the terminal defines the maximum value for the number of PDCCH candidates that can be monitored and the number of CCEs constituting the entire search space (where the entire search space refers to the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per span.

[0165] [Condition 1: Limit on the maximum number of PDCCH candidates]

[0166] As described above, depending on the setting value of the upper layer signaling, the maximum number of PDCCH candidate groups Mμ that the terminal can monitor follows Table 11-1 below when defined based on slots in a cell set to a subcarrier interval of 15·2μ kHz, and follows Table 11-2 below when defined based on spans.

[0167] [Table 11-1]

[0168]

[0169] [Table 11-2]

[0170]

[0171] [Condition 2: Limit on Maximum CCEs]

[0172] As described above, depending on the setting value of the upper layer signaling, Cμ, which is the maximum number of CCEs constituting the entire search space (where the entire search space refers to the entire set of CCEs corresponding to the union region of multiple search space sets), follows Table 11-3 below when defined based on slots in a cell set to a subcarrier interval of 15·2μ kHz, and follows Table 11-4 below when defined based on spans.

[0173] [Table 11-3]

[0174]

[0175] [Table 11-4]

[0176]

[0177] For the convenience of explanation, a situation in which both of the above conditions 1 and 2 are satisfied at a specific point in time is defined as “condition A.” Therefore, not satisfying condition A may mean not satisfying at least one of the above conditions 1 and 2.

[0178] Depending on the configuration of the base station's search space sets, there may be cases where Condition A is not satisfied at a specific point in time. If Condition A is not satisfied at a specific point in time, the terminal may select and monitor only some of the search space sets configured to satisfy Condition A at that point in time, and the base station may transmit a PDCCH to the selected search space sets.

[0179] [PDCCH: Overbooking]

[0180] You can follow the method below to select some of the navigation spaces from the entire set of configured navigation spaces.

[0181] [Method 1]

[0182] If condition A for PDCCH is not satisfied at a specific time point (slot),

[0183] The terminal (or base station) may preferentially select a search space set whose search space type is set as a common search space among the search space sets existing at that time, over a search space set whose search space type is set as a terminal-specific search space.

[0184] When all sets of search spaces configured as common search spaces have been selected (i.e., when Condition A is satisfied even after selecting all search spaces configured as common search spaces), the terminal (or base station) may select sets of search spaces configured as terminal-specific search spaces. In this case, if there are multiple sets of search spaces configured as terminal-specific search spaces, the search space set with a lower search space set index may have a higher priority. Considering the priority, sets of terminal-specific search spaces may be selected within the range where Condition A is satisfied.

[0185] [QCL, TCI state]

[0186] In a wireless communication system, one or more different antenna ports (or may be replaced by one or more channels, signals, and combinations thereof, but for convenience in the following description of the disclosure, they will be referred to collectively as different antenna ports) may be associated with each other by a quasi-co-location (QCL) setting as shown in [Table 12] below. The TCI state is intended to disclose the QCL relationship between a PDCCH (or PDCCH DMRS) and other RS ​​or channels. When a reference antenna port A (reference RS #A) and another target antenna port B (target RS #B) are said to be QCLed with each other, it means that the terminal is allowed to apply some or all of the large-scale channel parameters estimated from the antenna port A to the channel measurement from the antenna port B. QCL may require associating different parameters depending on the situation, such as 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) RRM (radio resource management) affected by average gain, and 4) BM (beam management) affected by spatial parameters. Accordingly, NR supports four types of QCL relationships as shown in Table 12 below.

[0187] [Table 12]

[0188]

[0189] The above spatial RX parameter may collectively refer to some or all of various parameters, such as Angle of arrival (AoA), Power Angular Spectrum (PAS) of AoA, Angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, and spatial channel correlation.

[0190] The above QCL relationship can be configured for the terminal through the RRC parameters TCI-State and QCL-Info as shown in Table 13 below. Referring to Table 13, the base station can configure one or more TCI states for the terminal and provide up to two QCL relationships (qcl-Type1, qcl-Type2) for the RS that references the ID of the said TCI state, i.e., the target RS. At this time, each QCL information (QCL-Info) included in each said TCI state includes the serving cell index and BWP index of the reference RS pointed to by the corresponding QCL information, the type and ID of the reference RS, and the QCL type as shown in Table 12 above.

[0191] [Table 13]

[0192]

[0193] FIG. 7 is a diagram illustrating an example of base station beam allocation according to TCI state settings in a wireless communication system according to an embodiment of the present disclosure. Referring to FIG. 7, the base station can transmit information about N different beams to a terminal through N different TCI states. For example, as in FIG. 7, when N=3, the base station can notify that antenna ports referencing the different TCI states 700, 705, or 710 are associated with different spatial Rx parameters, i.e., different beams, by setting the qcl-Type2 parameters included in the three TCI states (700, 705, 710) to QCL type D and associating them with CSI-RS or SSB corresponding to different beams.

[0194] Tables 14-1 to 14-5 below show valid TCI state settings according to the target antenna port type.

[0195] Table 14-1 shows valid TCI state settings when the target antenna port is CSI-RS for tracking (TRS). The TRS mentioned above refers to an NZP CSI-RS in which the repetition parameter is not set and trs-Info is set to true. In Table 14-1, setting 3 can be used for aperiodic TRS.

[0196] [Table 14-1] Valid TCI state settings when the target antenna port is CSI-RS for tracking (TRS)

[0197]

[0198] Table 14-2 shows valid TCI state settings when the target antenna port is CSI-RS for CSI. The above CSI-RS for CSI refers to an NZP CSI-RS in which the parameter indicating repetition (e.g., the repetition parameter) is not set and trs-Info is not set to true.

[0199] [Table 14-2] Valid TCI state settings when the target antenna port is CSI-RS for CSI

[0200]

[0201] Table 14-3 shows valid TCI state settings when the target antenna port is CSI-RS for beam management (BM, synonymous with CSI-RS for L1 RSRP reporting). The above CSI-RS for BM refers to an NZP CSI-RS in which the repetition parameter is set to On or Off and trs-Info is not set to true.

[0202] [Table 14-3] Valid TCI state settings when the target antenna port is CSI-RS for BM (for L1 RSRP reporting)

[0203]

[0204] Table 14-4 shows the valid TCI state settings when the target antenna port is a PDCCH DMRS.

[0205] [Table 14-4] Valid TCI state settings when the target antenna port is PDCCH DMRS

[0206]

[0207] Table 14-5 shows the valid TCI state settings when the target antenna port is PDSCH DMRS.

[0208] [Table 14-5] Valid TCI state settings when the target antenna port is PDSCH DMRS

[0209]

[0210] A representative QCL setting method according to Tables 14-1 to 14-5 above is to operate by setting the target antenna port and reference antenna port for each stage as "SSB" -> "TRS" -> "CSI-RS for CSI, or CSI-RS for BM, or PDCCH DMRS, or PDSCH DMRS". Through this, it is possible to link the statistical characteristics measurable from the SSB and TRS to each antenna port to assist the reception operation of the terminal.

[0211] [PDCCH: TCI state related]

[0212] Specifically, the TCI state combinations applicable to the PDCCH DMRS antenna port are as shown in Table 14-6 below. The fourth row of Table 14-6 represents the combinations assumed by the terminal prior to RRC setup, and setup after RRC is not possible.

[0213] [Table 14-6]

[0214]

[0215] NR supports a hierarchical signaling method as shown in Fig. 8 for dynamic allocation of PDCCH beams.

[0216] FIG. 8 is a diagram illustrating an example of a method for allocating a TCI state to a PDCCH in a wireless communication system according to an embodiment of the present disclosure.

[0217] Referring to FIG. 8, the base station can set N TCI states (805, 810, …, 820) to the terminal through RRC signaling (800), and some of these can be set as TCI states for CORESET (825). Subsequently, the base station can instruct the terminal to one of the TCI states for CORESET (830, 835, 840) through MAC CE signaling (845). Subsequently, the terminal receives a PDCCH based on beam information contained in the TCI state indicated by the MAC CE signaling.

[0218] FIG. 9 is a diagram illustrating a TCI indication MAC CE signaling structure for a PDCCH DMRS in a wireless communication system according to one embodiment of the present disclosure.

[0219] Referring to FIG. 9, the TCI indication MAC CE signaling for the PDCCH DMRS consists of 2 bytes (16 bits) and includes a 1-bit reserved bit (910), a 5-bit serving cell ID (915), a 2-bit BWP ID (920), a 2-bit CORESET ID (925), and a 6-bit TCI state ID (930).

[0220] FIG. 10 is a diagram illustrating an example of CORESET and search space beam configuration in a wireless communication system according to an embodiment of the present disclosure. Referring to FIG. 10, a base station may indicate one of the TCI state lists included in the CORESET (1000) configuration through MAC CE signaling (1005). Subsequently, until another TCI state is indicated to the corresponding CORESET through another MAC CE signaling, the terminal considers that the same QCL information (beam #1, 1005) is applied to all one or more search spaces (1010, 1015, 1020) connected to the CORESET. The PDCCH beam allocation method described above has the disadvantage that it is difficult to indicate a beam change faster than the MAC CE signaling delay, and also that the same beam is applied collectively to all CORESETs regardless of search space characteristics, which makes flexible PDCCH beam operation difficult. The embodiments of the present disclosure below provide a more flexible PDCCH beam configuration and operation method. In describing the embodiments of the present disclosure below, several distinct examples are provided for convenience of explanation; however, these are not mutually exclusive and can be appropriately combined and applied depending on the situation.

[0221] The base station may set one or more TCI states for a specific control area for the terminal, and may activate one of the set TCI states through a MAC CE activation command. For example, if {TCI state#0, TCI state#1, TCI state#2} are set as TCI states for control area #1, the base station may transmit a command to the terminal via MAC CE to activate TCI state#0 as the TCI state for control area #1. Based on the activation command for the TCI state received via MAC CE, the terminal can correctly receive the DMRS of the corresponding control area based on the QCL information within the activated TCI state.

[0222] For a control area (control area #0) with an index set to 0, if the terminal has not received a MAC CE activation command for the TCI state of control area #0, it can be assumed that the terminal has QCL with an SS / PBCH block identified in a non-contention-based random access process that is not triggered by an initial access process or a PDCCH command for DMRS transmitted from control area #0.

[0223] For a control area (control area #X) where the index is set to a value other than 0, if the terminal has not received a TCI state for control area #X, or has received one or more TCI states but has not received a MAC CE activation command to activate one of them, it can be assumed that the terminal has QCL with the SS / PBCH block identified during the initial connection process with the DMRS transmitted from control area #X.

[0224] [PDSCH: Regarding Frequency Resource Allocation]

[0225] FIG. 11 is a diagram illustrating an example of frequency axis resource allocation of a physical downlink shared channel (PDSCH) in a wireless communication system according to one embodiment of the present disclosure.

[0226] FIG. 11 is a diagram illustrating three frequency axis resource allocation methods that can be configured through the upper layer in an NR wireless communication system: type 0 (11-00), type 1 (11-05), and dynamic switch (11-10).

[0227] Referring to FIG. 11, if a terminal is configured to use only resource type 0 through upper layer signaling (11-00), some downlink control information (DCI) that assigns PDSCH to the terminal includes a bitmap consisting of NRBG bits. The conditions for this will be explained later. In this case, NRBG refers to the number of RBGs (resource block groups) determined as shown in [Table 15-1] below according to the BWP size assigned by the BWP indicator and the upper layer parameter rbg-Size, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0228] [Table 15-1]

[0229]

[0230] If a terminal is configured to use only resource type 1 through upper layer signaling (11-05), some DCIs that assign PDSCH to the terminal are It includes frequency axis resource allocation information consisting of bits. The conditions for this will be explained later. Through this, the base station can set the starting VRB (11-20) and the length (11-25) of the frequency axis resources continuously allocated therefrom.

[0231] If the terminal is configured to use both resource type 0 and resource type 1 through upper layer signaling (11-10), some DCIs that allocate PDSCH to the terminal include frequency axis resource allocation information consisting of bits of the larger value (11-35) of the payload for setting resource type 0 (11-15) and the payload for setting resource type 1 (11-20, 11-25). The conditions for this will be explained later. At this time, one bit may be added to the beginning part (MSB) of the frequency axis resource allocation information within the DCI, and if the bit has a value of '0', it indicates that resource type 0 is used, and if it has a value of '1', it indicates that resource type 1 is used.

[0232] [PDSCH / PUSCH: Time Resource Allocation]

[0233] The following describes a time-domain resource allocation method for data channels in next-generation mobile communication systems (5G or NR systems).

[0234] The base station may set a table for time domain resource allocation information for the physical downlink shared channel (PDSCH) and the physical uplink shared channel (PUSCH) for the terminal using upper-layer signaling (e.g., RRC signaling). For PDSCH, a table consisting of a maximum of maxNrofDL-Allocations = 16 entries may be set, and for PUSCH, a table consisting of a maximum of maxNrofUL-Allocations = 16 entries may be set. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to a slot-unit time interval between the time when the PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to a slot-unit time interval between the time when the PDCCH is received and the time when the PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information regarding the position and length of the start symbol in which the PDSCH or PUSCH is scheduled within the slot, and the mapping type of the PDSCH or PUSCH. For example, information such as [Table 15-2] or [Table 15-3] below may be transmitted from the base station to the terminal.

[0235] [Table 15-2]

[0236]

[0237] [Table 15-3]

[0238]

[0239] The base station may notify the terminal of one of the entries in the table for the time domain resource allocation information described above via L1 signaling (e.g., DCI) (e.g., indicated by the 'time domain resource allocation' field within the DCI). The terminal may obtain time domain resource allocation information for PDSCH or PUSCH based on the DCI received from the base station.

[0240] FIG. 12 is a diagram illustrating an example of time-axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.

[0241] Referring to FIG. 12, the base station can indicate the time axis position of the PDSCH resource according to the subcarrier spacing (SCS) (μPDSCH, μPDCCH) of the data channel and control channel set using the upper layer, the scheduling offset (K0) value, and the OFDM symbol start position (12-00) and length (12-05) within one slot dynamically indicated through DCI.

[0242] FIG. 13a is a diagram illustrating an example of time-axis resource allocation according to the subcarrier interval of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure.

[0243] Referring to Fig. 13a, when the subcarrier spacing of the data channel and the control channel is the same (13a-00, μPDSCH = μPDCCH), the slot number for data and control is the same, so the base station and the terminal can generate a scheduling offset by aligning it with a predetermined slot offset K0. On the other hand, when the subcarrier spacing of the data channel and the control channel is different (13a-05, μPDSCH ≠ μPDCCH), the slot number for data and control is different, so the base station and the terminal can generate a scheduling offset by aligning it with a predetermined slot offset K0 based on the subcarrier spacing of PDCCH.

[0244] [Regarding SRS]

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

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

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

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

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

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

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

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

[0253] 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, a 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.

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

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

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

[0257] [Table 16-1]

[0258]

[0259]

[0260]

[0261] The spatialRelationInfo setting information in [Table 16-1] 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 16-2] below.

[0262] [Table 16-2]

[0263]

[0264] 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—namely, the SS / PBCH block index, CSI-RS index, or SRS index—can be set. The upper signaling referenceSignal is configuration 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 transmission beam used during the transmission of the SRS corresponding to srs as the transmission beam for the transmission of the SRS.

[0265] [PUSCH: Regarding transmission method]

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

[0267] Configured grant Type 1 PUSCH transmissions can be semi-statically configured by receiving configuredGrantConfig, which includes rrc-ConfiguredUplinkGrant of [Table 16-3], 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 of [Table 16-3], 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 16-3], with the exception of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH, which are provided by pusch-Config, the upper signaling of [Table 16-4]. If the terminal is provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 16-3], the terminal applies tp-pi2BPSK in pusch-Config of [Table 16-4] to PUSCH transmissions operated by configured grant.

[0268] [Table 16-3]

[0269]

[0270]

[0271]

[0272] 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 16-4], the upper signaling, is 'codebook' or 'nonCodebook'.

[0273] 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 an 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 has not been configured with txConfig within pusch-Config of [Table 16-4], the terminal does not expect to be scheduled via DCI format 0_1.

[0274] [Table 16-4]

[0275]

[0276]

[0277]

[0278] 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), TPMI (transmission precoding matrix indicator), and transmission rank (number of PUSCH transmission layers).

[0279] 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. When transmitting a codebook-based PUSCH, 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.

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

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

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

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

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

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

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

[0287] 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, 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.

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

[0289] [PUSCH: Preparation Process Time]

[0290] Next, the PUSCH preparation procedure time is described. When a base station schedules a terminal to transmit a PUSCH using DCI format 0_0 or DCI format 0_1, the terminal may require a PUSCH preparation procedure time to transmit the PUSCH by applying the transmission method specified via DCI (transmission precoding method of SRS resources, number of transmission layers, spatial domain transmission filter). In consideration of this, NR has defined the PUSCH preparation procedure time. The terminal's PUSCH preparation procedure time may follow [Equation 3] below.

[0291] [Mathematical Formula 3]

[0292]

[0293] The aforementioned In this, each variable can have the following meanings.

[0294] - N2: A number of symbols determined by the terminal processing capability (UE processing capability) 1 or 2 and the numerology μ according to the terminal's capability. If the terminal processing capability is reported as 1 according to the terminal's capability report, it has the value of [Table 16-5], and if the terminal processing capability is reported as 2 and the ability to use terminal processing capability 2 is set through upper layer signaling, it can have the value of [Table 16-6].

[0295] [Table 16-5]

[0296]

[0297] [Table 16-6]

[0298]

[0299] - d2,1: A number of symbols determined as 0 if the resource elements of the first OFDM symbol of the PUSCH transmission are all configured to consist only of DM-RS, and 1 otherwise.

[0300] - κ: 64

[0301] - μ: or Among them, it follows the value where Tproc,2 becomes larger. represents the numerology of the downlink through which a PDCCH containing a DCI that schedules the PUSCH is transmitted, and represents the numerology of the uplink through which PUSCH is transmitted.

[0302] - Tc: , , has.

[0303] - d2,2: Follows the BWP switching time if the DCI scheduling PUSCH directs BWP switching, and 0 otherwise.

[0304] - d2: If the OFDM symbols of PUCCH, PUSCH with a higher priority index, and PUCCH with a lower priority index overlap in time, the d2 value of PUSCH with the higher priority index is used. Otherwise, d2 is 0.

[0305] - Text: If the terminal uses a shared spectrum channel access method, the terminal can calculate Text and apply it to the PUSCH preparation procedure time. Otherwise, Text is assumed to be 0.

[0306] - Tswitch: If the uplink switching interval is triggered, Tswitch assumes the switching interval time. Otherwise, it assumes 0.

[0307] When the base station and the terminal consider the timing advance (TA) effect between the uplink and downlink and the time-axis resource mapping information of the PUSCH scheduled through the DCI, if the first symbol of the PUSCH starts before the first uplink symbol where the CP starts after Tproc,2 from the last symbol of the PDCCH including the DCI that scheduled the PUSCH, the base station and the terminal determine that the PUSCH preparation procedure time is insufficient. If this is not the case, the base station and the terminal determine that the PUSCH preparation procedure time is sufficient. The terminal transmits the PUSCH only when the PUSCH preparation procedure time is sufficient, and may ignore the DCI that schedules the PUSCH when the PUSCH preparation procedure time is insufficient.

[0308] Next, PUSCH repeat transmissions are described. When a terminal is scheduled to send a PUSCH transmission with DCI format 0_1 ​​in a PDCCH containing a CRC scrambled with C-RNTI, MCS-C-RNTI, or CS-RNTI, and the terminal is set to the upper layer signaling pusch-AggregationFactor, the same symbol allocation is applied to consecutive slots equal to pusch-AggregationFactor, and the PUSCH transmission is limited to a single rank transmission. For example, the terminal must repeat the same TB in consecutive slots equal to pusch-AggregationFactor, and the same symbol allocation must be applied for each slot. [Table 16-7] shows the redundancy version applied to PUSCH repeat transmissions for each slot. If a terminal is scheduled to perform PUSCH repeated transmissions in multiple slots in DCI format 0_1, and at least one symbol among the slots where PUSCH repeated transmissions are performed is indicated as a downlink symbol according to the information in the upper layer signaling tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the terminal does not perform PUSCH transmission in the slot where the symbol is located.

[0309] [Table 16-7]

[0310]

[0311] [PUSCH: Repetitive transmission related]

[0312] The following describes in detail the repetitive transmission of uplink data channels in 5G systems. 5G systems support two types of repetitive transmission methods for uplink data channels: PUSCH repetitive transmission type A and PUSCH repetitive transmission type B. A terminal can receive either PUSCH repetitive transmission type A or B as a setting for upper layer signaling.

[0313] PUSCH Repeated Transmission Type A

[0314] - As described above, the symbol length of the uplink data channel and the position of the start symbol are determined by a time domain resource allocation method within a single slot, and the base station can notify the terminal of the number of repeated transmissions through upper layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0315] - The terminal may repeatedly transmit an uplink data channel in consecutive slots that has the same length and starting symbol as the uplink data channel configured based on the number of repeated transmissions received from the base station. In this case, if at least one of the slots configured as downlink by the base station to the terminal, or at least one of the symbols of the uplink data channel configured to the terminal, is configured as downlink, the terminal skips the transmission of the uplink data channel, but counts the number of repeated transmissions of the uplink data channel.

[0316] PUSCH Repeated Transmission Type B

[0317] - As described above, the start symbol and length of the uplink data channel are determined by a time domain resource allocation method within a single slot, and the base station can notify the terminal of the number of repetitions through upper signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0318] - Based on the start symbol and length of the uplink data channel configured first, the nominal repetition of the uplink data channel is determined as follows. The slot where the nth nominal repetition starts is The symbol given by and starting in that slot is It is given by. The slot where the nth nominal repetition ends is The symbol given by and ending in that slot is It is given by, where n=0,…, numberofrepetitions-1 and S represents the starting symbol of the configured uplink data channel, and L represents the symbol length of the configured uplink data channel. indicates the slot where the PUSCH transmission starts. Indicates the number of symbols per slot.

[0319] - The terminal determines invalid symbols for PUSCH repeat transmission type B. Symbols configured for the downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are determined as invalid symbols for PUSCH repeat transmission type B. Additionally, invalid symbols may be set in upper layer parameters (e.g., InvalidSymbolPattern). Invalid symbols may be set by providing a symbol-level bitmap spanning one or two slots. In the bitmap, 1 represents an invalid symbol. Additionally, the periodicity and pattern of the bitmap may be set through upper layer parameters (e.g., periodicityAndPattern). If an upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter indicates 1, the terminal applies the invalid symbol pattern, and if the parameter indicates 0, the terminal does not apply the invalid symbol pattern. If an upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter is not set, the terminal applies the invalid symbol pattern.

[0320] After an invalid symbol is determined, for each nominal repetition, the terminal may consider symbols other than the invalid symbol as valid symbols. If one or more valid symbols are included in each nominal repetition, the nominal repetition may include one or more actual repetitions. Here, each actual repetition contains a consecutive set of valid symbols that can be used for PUSCH repeat transmission type B within a single slot.

[0321] FIG. 13b illustrates an example of PUSCH repeat transmission type B in a wireless communication system according to an embodiment of the present disclosure. The terminal may set the start symbol S of the uplink data channel to 0 and the length L of the uplink data channel to 14, and the number of repeat transmissions to 16. In this case, the nominal repetition is shown in 16 consecutive slots (301). Subsequently, the terminal may determine that the symbol set as the downlink symbol in each nominal repetition (301) is an invalid symbol. Additionally, the terminal determines that the symbols set to 1 in the invalid symbol pattern (302) are invalid symbols. If valid symbols that are not invalid symbols in each nominal repetition consist of one or more consecutive symbols in a single slot, they are set as actual repetitions and transmitted (303).

[0322] In addition, for PUSCH repeated transmissions, NR Release 16 may define the following additional methods for UL grant-based PUSCH transmissions that cross slot boundaries and configured grant-based PUSCH transmissions.

[0323] - Method 1 (mini-slot level repetition): Through a single UL grant, two or more PUSCH repeat transmissions are scheduled within a single slot or across the boundaries of consecutive slots. Additionally, for Method 1, the time-domain resource allocation information within the DCI indicates the resources for the first repeat transmission. Furthermore, the time-domain resource information for the remaining repeat transmissions can be determined based on the time-domain resource information of the first repeat transmission and the uplink or downlink direction determined for each symbol in each slot. Each repeat transmission occupies consecutive symbols.

[0324] - Method 2 (multi-segment transmission): Two or more PUSCH repeat transmissions are scheduled in consecutive slots through a single UL grant. In this case, one transmission is assigned per slot, and each transmission may have a different starting point or repeat length. Additionally, in Method 2, time-domain resource allocation information within the DCI indicates the starting point and repeat length of all repeat transmissions. Furthermore, when repeat transmissions are performed within a single slot via Method 2, if there are multiple consecutive uplink symbol bundles within that slot, each repeat transmission is performed for each uplink symbol bundle. If there is only a unique consecutive uplink symbol bundle within that slot, one PUSCH repeat transmission is performed according to the method of NR Release 15.

[0325] - Method 3: Two or more repeated PUSCH transmissions are scheduled in consecutive slots through two or more UL grants. In this case, one transmission is assigned per slot, and the n-th UL grant can be received before the PUSCH transmission scheduled by the n-1-th UL grant is finished.

[0326] - Method 4: Through one UL grant or one configured grant, one or more PUSCH repeat transmissions within a single slot, or two or more PUSCH repeat transmissions across the boundaries of consecutive slots, may be supported. The number of repeats instructed by the base station to the terminal is merely a nominal value, and the number of PUSCH repeat transmissions actually performed by the terminal may be greater than the nominal number of repeats. Time-domain resource allocation information within the DCI or within the configured grant refers to the resources of the first repeat transmission instructed by the base station. Time-domain resource information for the remaining repeat transmissions may be determined by referencing at least the resource information of the first repeat transmission and the uplink or downlink direction of the symbols. If the time-domain resource information of the repeat transmission instructed by the base station spans a slot boundary or includes an uplink / downlink switching point, the repeat transmission may be divided into multiple repeat transmissions. In this case, one repeat transmission may be included within a single slot for each uplink period.

[0327] [PUSCH: Frequency Hopping Process]

[0328] The following describes frequency hopping of the Physical Uplink Shared Channel (PUSCH) in a 5G system in detail.

[0329] In 5G, two methods are supported for the frequency hopping method of the uplink data channel for each PUSCH repeat transmission type. First, PUSCH repeat transmission type A supports intra-slot frequency hopping and inter-slot frequency hopping, and PUSCH repeat transmission type B supports inter-repetition frequency hopping and inter-slot frequency hopping.

[0330] The intra-slot frequency hopping method supported by PUSCH repeat transmission type A is a method in which a terminal transmits by changing the allocated resources in the frequency domain by a set frequency offset between two hops within a single slot. In intra-slot frequency hopping, the starting RB of each hop can be represented by Equation 4.

[0331] [Mathematical Formula 4]

[0332]

[0333] In mathematical equation 4, i=0 and i=1 represent the first hop and the second hop, respectively, and represents the starting RB within the UL BWP and is calculated from the frequency resource allocation method. It represents the frequency offset between two hops through the upper-layer parameters. The number of symbols in the first hop is It can be represented as, and the number of symbols for the second hop is It can be represented as. is the length of PUSCH transmission within one slot, represented by the number of OFDM symbols.

[0334] Next, the inter-slot frequency hopping method supported by PUSCH repeating transmission types A and B is a method in which the terminal transmits by changing the allocated resource in the frequency domain by a set frequency offset for each slot. In inter-slot frequency hopping The starting RB during the slot can be represented through mathematical formula 5.

[0335] [Mathematical Formula 5]

[0336]

[0337] In mathematical formula 5, is the current slot number in a multi-slot PUSCH transfer, represents the starting RB within the UL BWP and is calculated from the frequency resource allocation method. It represents the frequency offset between two hops through the upper layer parameters.

[0338] Next, the inter-repetition frequency hopping method supported by PUSCH repeat transmission type B transmits the resources allocated in the frequency domain for one or more actual repetitions within each nominal repetition by shifting them by a set frequency offset. The index of the starting RB, RBstart(n), in the frequency domain for one or more actual repetitions within the nth nominal repetition can follow Equation 6 below.

[0339] [Mathematical Formula 6]

[0340]

[0341] In mathematical equation 6, n is the index of the nominal repetition, represents the RB offset between two hops through the upper layer parameter.

[0342] [Regarding Terminal Capability Reporting]

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

[0344] 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 whenever necessary.

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

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

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

[0348] 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."

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

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

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

[0352] [CA / DC Related]

[0353] FIG. 14 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.

[0354] Referring to Fig. 14, 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.

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

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

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

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

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

[0360] 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, bearer, or logical channel. If the SDAP header is configured, the terminal may instruct the NAS QoS reflective setting 1-bit indicator (NAS reflective QoS) and the AS QoS reflective setting 1-bit indicator (AS reflective QoS) of the SDAP header to update or reset the mapping information for the QoS flow of the uplink and downlink and the data bearer. 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.

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

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

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

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

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

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

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

[0368] - Retransmission of PDCP SDUs

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

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

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

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

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

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

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

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

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

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

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

[0380] - Duplicate detection

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

[0382] - RLC SDU discard function

[0383] RLC re-establishment function

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

[0385] 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 them 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.

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

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

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

[0389] - Scheduling information reporting function

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

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

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

[0393] - MBMS service identification

[0394] - Transport format selection function

[0395] - Padding

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

[0397] The detailed structure of the above wireless protocol structure may vary 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.

[0398] [Regarding NC-JT]

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

[0400] Unlike conventional 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 density. 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 a terminal or by efficiently performing interference control between each cell, TRP, or / and beam. For convenience in the following description of the disclosure, cells, transmission points, panels, beams, or / and 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, are uniformly referred to as TRPs (transmission reception points). Therefore, in actual application, TRPs can be appropriately replaced with one of the above terms.

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

[0402] The aforementioned NC-JT transmission may be applied to at least one of the physical downlink shared channel (PDSCH), physical downlink control channel (PDCCH), physical uplink shared channel (PUSCH), and physical uplink control channel (PUCCH). During PDSCH transmission, transmission information such as precoding, MCS, resource allocation, and TCI is indicated by DL DCI, and for NC-JT transmission, the 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 the 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.

[0403] FIG. 15 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.

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

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

[0406] In the case of C-JT, TRP A (N005) and TRP B (N010) transmit a single data (PDSCH) to a terminal (N015), and joint precoding can be performed in multiple TRPs. This may mean that DMRS is transmitted through the same DMRS ports for TRP A (N005) and TRP B (N010) to transmit the same PDSCH. For example, TRP A (N005) and TRP B (N010) can each 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.

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

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

[0409] 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 (N040), when the frequency and time resources used by multiple TRPs do not overlap at all (N045), or when some of the frequency and time resources used by multiple TRPs overlap (N050).

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

[0411] FIG. 16 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.

[0412] Referring to FIG. 16, case #1 (N100) 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.

[0413] Case #2 (N105) illustrates a situation 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, wherein control information (DCI) for the PDSCHs of the (N-1) additional TRPs is transmitted separately, and each of these DCIs is dependent on the control information for the PDSCH transmitted from the serving TRP.

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

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

[0416] Case #3 (N110) illustrates a situation where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) 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.

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

[0418] In case #3 (N110), 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 may be reduced compared to case #1 (N100) or case #2 (N105).

[0419] Case #4 (N115) 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 within the same DCI (Long DCI) as the control information for the PDSCH transmitted from the serving TRP. In other words, the terminal can obtain control information for PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In the case of Case #4 (N115), the complexity of the terminal's DCI blind decoding may not increase, but the degree of freedom for PDSCH control or allocation may be low, such as when the number of cooperating TRPs is limited due to the long DCI payload limit.

[0420] In the following description 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, the description may be similarly applied to the various auxiliary DCIs.

[0421] In the following description and embodiments, the aforementioned cases #1 (N100), #2 (N105), and #3 (N110), 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 (N115), 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, the CORESET where the DCI of the serving TRP (TRP#0) is scheduled and the CORESET where 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. At this time, 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.

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

[0423] In the embodiments of the present disclosure, the phrase “when NC-JT is applied” can be interpreted in various ways depending on the situation, such as “when a terminal receives one or more PDSCHs simultaneously in one BWP,” “when a terminal receives PDSCHs based on two or more TCI (Transmission Configuration Indicator) indications simultaneously in one BWP,” or “when 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.

[0424] 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. 14 (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 the exchange of information such as CSI, scheduling, and HARQ-ACK between cooperative TRPs), a method using a structure independent of each TRP from the RLC layer, similar to S20 in FIG. 14, to ensure robustness against delay (DC-like method) is possible.

[0425] A terminal supporting C-JT / NC-JT can receive C-JT / NC-JT-related parameters or setting values ​​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, such as tci-StatePDSCH. Here, UE capability parameters, such as tci-StatePDSCH, can define TCI states for the purpose of PDSCH transmission. 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 configured, which can be indicated by the 3 bits of the TCI field of the DCI via a MAC CE message. The maximum value of 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.

[0426] [Introduction to the Example]

[0427] 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, are uniformly referred to as TRP (transmission reception point). Therefore, in actual application, TRP can be appropriately replaced with one of the above terms.

[0428] Referring to the aforementioned descriptions regarding PUSCH, current Rel-15 / 16 NR focuses on PUSCH repeated transmissions for a single cell or / and a single TRP or / and a single panel or / and a single beam or / and a single transmission direction. Specifically, for PUSCH repeated transmissions, transmission to a single TRP is considered regardless of whether the transmission is codebook-based or non-codebook-based. For example, in codebook-based PUSCH transmissions, the terminal's transmit beam can be determined by the SRI and TPMI transmitted from the base station, i.e., the single TRP, to the terminal. Similarly, for non-codebook-based PUSCH transmissions, the NZP CSI-RS, which can be set by the base station, i.e., the single TRP, can be set for the terminal, and the terminal's transmit beam can be determined by the SRI transmitted from the single TRP. Therefore, if degradation factors with high temporal and spatial correlation, such as blockage, exist in the channel between the terminal and a specific TRP, PUSCH repeated transmission to a single TRP is highly likely to fail to satisfy the expected performance. Therefore, to overcome such degradation, Rel-17 or later releases may support PUSCH iterations that consider multiple TRPs. This can be a method to maximize diversity gain by considering the channels between the terminal and multiple TRPs that have different spatial characteristics. To support this, the terminal must support configurations for PUSCH iterations to multiple TRPs. For example, configuration or instruction methods are required for multiple transmission beams, power modulation, etc., to be used during PUSCH iterations that consider multiple TRPs. Additionally, upper-layer signaling or dynamic instruction is required to distinguish between the iterations considering a single TRP defined in Rel-15 / 16 and the PUSCH iterations considering multiple TRPs that will be newly defined in Rel-17.Furthermore, as a method to improve PUSCH reception performance, it is necessary to determine the transmission beam and frequency hopping in conjunction so that spatial diversity gain through iterative transmission to multiple TRPs and frequency diversity through frequency hopping can be obtained simultaneously in order to maximize diversity gain.

[0429] In this disclosure, by providing a method for processing the aforementioned requirements, the loss of uplink data and transmission delay time during repeated PUSCH transmission considering multiple TRPs can be minimized. For various cases, the method for setting or instructing repeated PUSCH transmission to multiple TRPs of a terminal is described in detail in the following embodiments.

[0430] Embodiments of the present disclosure will be 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, provided that they do not deviate significantly 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 and TDD systems.

[0431] 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 intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

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

[0433] - MIB (Master Information Block)

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

[0435] - RRC (Radio Resource Control)

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

[0437] In addition, L1 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 using signaling.

[0438] - PDCCH (Physical Downlink Control Channel)

[0439] - DCI (Downlink Control Information)

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

[0441] - Group common DCI

[0442] - Common DCI

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

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

[0445] - PUCCH (Physical Uplink Control Channel)

[0446] - UCI (Uplink Control Information)

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

[0448] In the following disclosure, the above 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.

[0449] <1st Embodiment: PUSCH Repeated Transmission Method Considering Multiple TRPs>

[0450] The first embodiment of the present disclosure describes a method for setting up and indicating L1 signaling as upper-layer signaling for PUSCH repetitive transmission considering multiple TRPs. PUSCH repetitive transmission considering multiple TRPs can be operated through single or multiple DCI-based indications, which are described in the first-1 and first-2 embodiments, respectively.

[0451] In addition, the terminal may support one of the repeated PUSCH transmissions via single or multiple DCI-based instructions based on the base station settings, or it may support both methods and use L1 signaling to distinguish between the two methods. This is explained in the 1-3rd embodiment.

[0452] In addition, the first to fourth embodiments of the present disclosure describe a method for setting an SRS resource set for PUSCH repetitive transmission considering a single or multiple DCI-based multiple TRP.

[0453] <Embodiment 1-1: PUSCH iterative transmission method considering multiple TRPs based on a single DCI>

[0454] In one embodiment of the present disclosure, the 1-1 embodiment describes a PUSCH repeat transmission method that considers multiple TRPs based on a single DCI. A terminal may report that a PUSCH repeat transmission method that considers multiple TRPs based on a single DCI is possible through a terminal capability report. For a terminal that has reported the terminal capability (e.g., a terminal capability that supports PUSCH repeat transmission considering multiple TRPs based on a single DCI), the base station may configure which PUSCH repeat transmission method to use through upper layer signaling. At this time, the upper layer signaling may be configured by selecting one of two types: PUSCH repeat transmission type A or PUSCH repeat transmission type B.

[0455] In Rel-15 / 16, for PUSCH repeat transmission methods considering a single TRP, both codebook and non-codebook based transmission methods were performed based on a single DCI. When transmitting codebook-based PUSCH, the terminal can apply the same value to each PUSCH repeat transmission using an SRI or TPMI indicated by a single DCI. Additionally, when transmitting non-codebook-based PUSCH, the terminal can apply the same value to each PUSCH repeat transmission using an SRI indicated by a single DCI. For example, if codebook-based PUSCH transmission and PUSCH repeat transmission method A are configured via upper layer signaling, and the time resource allocation index with a PUSCH repeat count of 4, SRI index 0, and TPMI index 0 are indicated via the DCI, the terminal applies both SRI index 0 and TPMI index 0 to each of the 4 PUSCH repeat transmissions. Here, SRI may be related to the transmission beam, and TPMI may be related to the transmission precoder. Unlike the PUSCH iterative transmission method considering a single TRP, the PUSCH iterative transmission method considering multiple TRPs may require applying different transmission beams and transmission precoders for transmission to each TRP. Therefore, the terminal can perform PUSCH iterative transmission considering multiple TRPs by receiving multiple SRIs or TPMIs through the DCI and applying them to each PUSCH iterative transmission.

[0456] When instructing a terminal to use a PUSCH repetitive transmission method that considers multiple TRPs based on a single DCI, methods for instructing multiple SRIs or TPMIs for cases where the PUSCH transmission method is codebook or non-codebook can be considered as follows.

[0457] [Method 1] Single DCI transmission with multiple SRI or TPMI fields

[0458] To support a PUSCH repetitive transmission method considering multiple TRPs based on a single DCI, a base station may transmit a DCI with multiple SRI or TPMI fields to a terminal. The DCI may be a new format (e.g., DCI format 0_3) or an existing format (e.g., DCI format 0_1, 0_2) but with additional upper layer signaling configured (e.g., signaling capable of determining whether multiple SRI or TPMI fields can be supported). For example, if codebook-based PUSCH transmission is configured as the upper layer signaling, the terminal may receive a DCI of a new format having two SRI fields and two TPMI fields (e.g., DCI format 0_3) and perform PUSCH repetitive transmission considering multiple TRPs. As another example, in the case of non-codebook-based PUSCH transmission, the terminal is configured to support multiple SRI fields through upper-layer signaling and can receive DCI of an existing format having two SRI fields (e.g., DCI format 0_1, 0_2). When multiple SRS resources are indicated using multiple SRI fields, the transmission power control parameters of the SRS resources are set per SRS resource set; therefore, in order to set different transmission power control parameters for each TRP, each SRS resource may exist within a different SRS resource set. Consequently, there may be two or more SRS resource sets where the usage, which is the upper-layer signaling, is set to codebook or non-codebook.

[0459] FIG. 17 illustrates the operation of a base station and a terminal regarding a PUSCH repetitive transmission considering a single DCI transmission-based multiple TRP having a plurality of SRI or TPMI fields according to an embodiment of the present disclosure. The terminal performs a terminal capability report regarding whether it supports a PUSCH repetitive transmission considering a single DCI-based multiple TRP (1751), and the base station that receives the terminal capability report (1701) transmits a PUSCH repetitive transmission setting considering a single DCI-based multiple TRP to the terminal (1702). At this time, the transmitted setting information may include a repetitive transmission method, the number of repetitive transmissions, a transmission beam mapping unit or method, whether a plurality of SRI or TPMI fields are supported, a plurality of SRS resource sets for codebooks or non-codebooks, etc. A terminal that receives the setting (1752) performs a first PUSCH transmission operation (1755) if the number of repeated transmissions is 2 or more, if there are multiple SRI fields and TPMI fields in the DCI that succeeded in receiving the codebook-based PUSCH transmission, or if there are multiple SRI fields in the DCI that succeeded in receiving the non-codebook-based PUSCH transmission, and performs a second PUSCH transmission operation (1756). The first PUSCH transmission operation is an operation to repeatedly transmit PUSCH using a single SRI and TPMI field in the case of codebook-based PUSCH transmission, and a single SRI field in the case of non-codebook-based PUSCH transmission, and to repeatedly transmit PUSCH by applying one transmission beam and / or one transmission precoder.The second PUSCH transmission operation is an operation that repeatedly transmits PUSCH using multiple SRI and TPMI fields in the case of codebook-based PUSCH transmission, and multiple SRI fields in the case of non-codebook-based PUSCH transmission, and repeatedly transmits PUSCH by applying multiple transmission beams and / or multiple transmission precoders. The method for mapping multiple transmission beams is explained in detail in the second embodiment.

[0460] [Method 2] DCI transmission with enhanced SRI and TPMI fields

[0461] To support a PUSCH iterative transmission method considering multiple TRPs based on a single DCI, the terminal may receive a MAC-CE from the base station for enhanced SRI or TPMI field support. The MAC-CE contains information to change the interpretation of codepoints in the DCI field so that multiple transmission beams are indicated for a specific codepoint in the SRI field within the DCI, or multiple transmission precoders are indicated for a specific codepoint in the TPMI field. The following two methods may be considered for indicating multiple transmission beams.

[0462] - MAC-CE receiver enabling a specific codepoint in the SRI field to point to a single SRS resource where multiple SRS spatial relation infos are linked.

[0463] - MAC-CE receiver enabling a specific codepoint in the SRI field to indicate multiple connected SRS resources to a single SRS spatial relation info

[0464] When multiple SRS resources are indicated using an enhanced SRI field, the transmission power control parameters of the SRS resources are set per SRS resource set. Therefore, in order to set different transmission power control parameters for each TRP, each SRS resource may exist within a different SRS resource set. Consequently, there may be two or more SRS resource sets where the usage, which is the upper layer signaling, is set to codebook or non-codebook.

[0465] FIG. 18 illustrates the operation of a base station and a terminal regarding a PUSCH repetitive transmission considering multiple TRPs based on a single DCI transmission using enhanced SRI and TPMI fields according to an embodiment of the present disclosure. The terminal performs a terminal capability report regarding whether it supports PUSCH repetitive transmission considering multiple TRPs based on a single DCI and a terminal capability report regarding whether MAC-CE can be enabled for an enhanced SRI field or TPMI field instruction (1851). Upon receiving the terminal capability report, the base station (1801) transmits a PUSCH repetitive transmission setting considering multiple TRPs based on a single DCI to the terminal (1802). At this time, the transmitted setting information may include a repetitive transmission method, the number of repetitive transmissions, a transmission beam mapping unit or method, and a set of multiple SRS resources for codebooks or non-codebooks. Upon receiving the setting, the terminal (1852) receives a MAC-CE that enables an enhanced SRI field or enhanced TPMI field instruction (1853), and transmits a HARQ-ACK to the base station 3 ms after receiving (1803). If the number of repeated transmissions is 2 or more (1854), if the received DCI has an enhanced SRI field and a TPMI field in the case of a codebook-based PUSCH transmission, or if the received DCI has an enhanced SRI field in the case of a non-codebook-based PUSCH transmission (1855), a first PUSCH transmission operation is performed (1856), otherwise a second PUSCH transmission operation is performed (1857). The first PUSCH transmission operation is an operation to repeatedly transmit PUSCH by receiving a DCI in which all codepoints of the SRI field and TPMI field represent a single SRI and a single TPMI instruction, and the PUSCH is repeatedly transmitted by applying one transmission beam and / or one transmission precoder.The second PUSCH transmission operation is an operation that repeatedly transmits PUSCH using codepoints in SRI and TPMI fields indicating multiple SRIs and TPMIs in the case of codebook-based PUSCH transmission, and codepoints in SRI fields indicating multiple SRIs in the case of non-codebook-based PUSCH transmission, and repeatedly transmits PUSCH by applying multiple transmission beams and / or multiple transmission precoders. The method for mapping multiple transmission beams is described in detail in the second embodiment.

[0466] <1-2 Embodiment: PUSCH iterative transmission method considering multiple TRPs based on multiple DCI>

[0467] In one embodiment of the present disclosure, the first and second embodiments describe a PUSCH iterative transmission method considering multiple TRPs based on multiple DCIs. As described above, since all PUSCH iterative transmission methods in Rel-15 / 16 consider a single TRP, it was possible to use the same values ​​for the transmission beam, transmission precoder, resource allocation, and power control parameters for each iterative transmission. However, when PUSCH iterative transmission considering multiple TRPs, it may be necessary to apply different parameters for each TRP regarding PUSCH transmission-related parameters that are set as upper-layer signaling or indicated by DCI for each PUSCH iterative transmission to multiple TRPs. For example, if multiple TRPs exist in different directions from the terminal, the transmission beam or transmission precoder may be different, so it is necessary to set or indicate the transmission beam or transmission precoder for each TRP separately. As another example, when multiple TRPs are located at different distances from the terminal, independent power control methods between the multiple TRPs and the terminal may be required, and accordingly, different time / frequency resource allocations may be made. For instance, for a TRP located at a relatively far distance compared to a specific TRP, a relatively small number of RBs and a large number of symbols may be allocated to increase the power per RE. Therefore, if one attempts to transmit different information to the terminal via a single DCI, the bit length of that DCI may become very large; thus, it may be more efficient to instruct the terminal to repeat PUSCH transmissions using multiple DCIs.

[0468] A terminal may report, through a terminal capability report, that a PUSCH repeated transmission method considering multiple TRPs based on multiple DCIs is possible. A base station may notify a terminal that has reported such terminal capability (e.g., a terminal capability supporting PUSCH repeated transmission considering multiple TRPs based on multiple DCIs) to perform PUSCH repeated transmission considering multiple TRPs via multiple DCIs by using configuration via upper layer signaling, instruction via L1 signaling, or configuration and instruction via a combination of upper layer signaling and L1 signaling. The base station may use a method for configuring or instructing PUSCH repeated transmission considering multiple TRPs based on multiple DCIs as follows.

[0469] When a terminal performs repeated PUSCH transmission considering multiple TRPs based on multiple DCIs, it can expect that the time / frequency resource allocation information indicated by each DCI differs, taking into account TRPs at different distances from the terminal. The terminal can report to the base station, at its capability, whether different time / frequency resource allocations are possible. The base station can configure the terminal regarding the availability of different time / frequency resource allocations via upper-layer signaling, and the terminal receiving such configuration can expect that the time / frequency resource allocation information indicated by each DCI will differ. In this case, the terminal can configure or receive instructions from the base station for repeated PUSCH transmission considering multiple TRPs based on multiple DCIs, by considering the upper-layer signaling configuration and conditions between multiple DCI fields. When transmission beam and transmission precorder information is received through multiple DCIs, the SRI and TPMI within the first received DCI can be applied first when applying the transmission beam mapping method of the second embodiment below, and the SRI and TPMI within the second received DCI can be applied second when applying the transmission beam mapping method of the second embodiment below.

[0470] The base station can set the CORESETPoolIndex, which is a higher layer signaling, for each CORESET, and the terminal can know from which TRP the CORESET is transmitted when it receives a CORESET. For example, if the CORESETPoolIndex is set to 0 for CORESET#1 and the CORESETPoolIndex is set to 1 for CORESET#2, the terminal can know that CORESET#1 is transmitted from TRP#0 and CORESET#2 is transmitted from TRP#1. Additionally, that the DCI transmitted within each CORESET, for which the CORESETPoolIndex value is set to 0 and 1 respectively, points to a repeating PUSCH can be implicitly indicated by a condition between specific fields within the multiple transmitted DCIs. For example, if the HARQ process number field values ​​and NDI field values ​​within multiple DCIs transmitted by a base station to a terminal are identical, the terminal may implicitly assume that the corresponding multiple DCIs each schedule repeated PUSCHs considering multiple TRPs. Meanwhile, if the HARQ process number field values ​​and NDI field values ​​are identical, there may be restrictions on the reception of multiple DCIs. For example, the maximum interval between the reception of the above multiple DCIs may be defined as within one or more specific slots or within one or more specific symbols. In this case, the terminal may perform PUSCH transmission based on the minimum Transport Block size calculated (or verified) based on time / frequency resource allocation information that is indicated differently in the multiple DCIs.

[0471] <Embodiment 1-3: Configured grant PUSCH repeated transmission method considering multiple TRPs>

[0472] In one embodiment of the present disclosure, the first to third embodiments describe a method for repeated transmission of a configured grant PUSCH considering multiple TRPs. A terminal may report to a base station, by its terminal capability, whether to repeat transmission of a configured grant PUSCH considering multiple TRPs. The base station may set and instruct the terminal regarding repeated transmission of a configured grant PUSCH considering multiple TRPs by using various methods such as setting it with upper layer signaling, instructing it with L1 signaling, or setting and instructing it using a combination of upper layer signaling and L1 signaling.

[0473] [Method 1] Enable a single configured grant setting based on a single DCI

[0474] Method 1 is a method of instructing a terminal to multiple SRIs or TPMIs based on the single DCI above, and activating a single configured grant setting along with said instruction. The method of instructing multiple SRIs or TPMIs with a single DCI may follow the method of the above-mentioned embodiment 1-1, and if the terminal has only one configured grant setting, all bits of the HARQ process number field and the redundancy version field within the DCI may be instructed to 0. If the terminal has multiple configured grant settings and one of them is activated with the DCI, the HARQ process number field within the DCI may indicate the index of the configured grant setting, and all bits of the redundancy version field may be instructed to 0. Using the multiple SRIs or TPMIs instructed by the single DCI, the terminal may map a transmission beam and a transmission precoder to each of the activated configured grant PUSCH repeated transmissions according to the transmission beam mapping method in the following embodiment 2.

[0475] [Method 2] Enable a single configured grant setting based on multiple DCIs

[0476] Method 2 is a method of instructing each SRI or TPMI to each DCI based on the above-mentioned multiple DCIs to the terminal, and activating a single configured grant setting along with said instruction. The method of instructing each SRI or TPMI to each DCI based on the above-mentioned multiple DCIs may follow the method of the above-mentioned first and second embodiments. If only one configured grant setting exists for the terminal, all bits of the HARQ process number field and the redundancy version field within the corresponding multiple DCI may be indicated as 0. If multiple configured grant settings exist for the terminal and one of them is activated for the corresponding multiple DCI, all HARQ process number fields within the corresponding multiple DCI may indicate the index of the same configured grant setting, and all bits of the redundancy version field within the corresponding multiple DCI may be indicated as 0. Depending on the conditions of the DCI fields during the above-mentioned multiple DCI-based PUSCH repeated transmission, the NDI field may also have the same value in addition to the HARQ process number field. The terminal can map a transmission beam and a transmission precoder to each of the activated configured grant PUSCH iterations according to the following transmission beam mapping method, using multiple SRIs or TPMIs indicated by multiple DCIs. For example, if the transmission beam and transmission precoder information indicated by the first received DCI is SRI#1 and TPMI#1, and the transmission beam and transmission precoder information indicated by the second received DCI is SRI#2 and TPMI#2, and the transmission beam mapping method set as the upper layer signaling is cyclical, the terminal maps the odd-numbered transmissions (1, 3, 5, ...) of the activated configured grant PUSCH iterations.PUSCH transmission can be performed by applying SRI#1 and TPMI#1 to ) and SRI#2 and TPMI#2 to the even-numbered transmissions (2, 4, 6, ...) of the repeated transmission.

[0477] [Method 3] Enable Multi-DCI Based Multi-Configured Grant Settings

[0478] Method 3 is a method of instructing each SRI or TPMI to each DCI based on the above multiple DCIs to a terminal, and activating multiple configured grant settings along with said instruction. The method of instructing each SRI or TPMI to each DCI based on multiple DCIs may follow the method of the above 1-2 embodiments, and multiple configured grant settings may exist for the terminal, and the index of each configured grant setting may be indicated through the HARQ process number field within each DCI. Additionally, all bits of all redundancy version fields within the corresponding multiple DCIs may be indicated as 0. Depending on the conditions of the DCI fields during the above multiple DCI-based PUSCH repeated transmission, the NDI field may also have the same value in addition to the HARQ process number field. The terminal may receive MAC-CE signaling that instructs (commands) a connection between multiple configured grant settings activated by the multiple DCIs. After 3 ms following the transmission of a HARQ-ACK for MAC-CE signaling, the terminal may receive multiple DCIs from the base station, and if the configured grant setting index pointed to by each DCI matches the configured grant setting indices that were instructed (commanded) to connect via the MAC-CE signaling, the terminal may perform repeated PUSCH transmissions considering multiple TRPs based on the instructed configured grant settings. At this time, some settings may be shared as the same value among the connected multiple configured grant settings.For example, repK, an upper-layer signaling representing the number of iterations; repK-RV, an upper-layer signaling representing the order of redundancy versions during iterations; and periodicity, an upper-layer signaling representing the period of iterations, can be configured to have the same value within the connected configured grant settings.

[0479] <Embodiment 1-4: Method for configuring an SRS resource set for repeated PUSCH transmission considering multiple TRPs>

[0480] In one embodiment of the present disclosure, the 1-4 embodiments describe a method for setting an SRS resource set for PUSCH iterative transmission considering multiple TRPs. Since the power control parameters of the SRS (e.g., alpha, p0, pathlossReferenceRS, srs-PowerControlAjdustmentStates, etc., which can be set as upper layer signaling) may vary for each SRS resource set, the number of SRS resource sets may be increased to two or more to allow for different power control of the SRS for each TRP during PUSCH iterative transmission considering multiple TRPs, and different SRS resource sets may be used for the purpose of supporting different TRPs. The method for setting an SRS resource set considered in the present embodiment can be applied to the 1-1 to 1-3 embodiments.

[0481] When PUSCH iterative transmission considering multiple TRPs based on a single DCI, multiple SRIs indicated by a single DCI can be selected from among SRS resources existing in different SRS resource sets. For example, if two SRIs are indicated by a single DCI, the first SRI can be selected from SRS resource set #1 and the second SRI can be selected from SRS resource set #2.

[0482] When performing repeated PUSCH transmissions considering multiple TRPs based on multiple DCIs, each SRI indicated by each of the two DCIs can be selected from among the SRS resources existing within different SRS resource sets, and each SRS resource set can be explicitly or implicitly associated (correspond) with upper-layer signaling (e.g., CORESETPoolIndex) representing each TRP. As an explicit association method, the terminal can be notified of the quasi-static connection status between the CORESET and the SRS resource set by setting the CORESETPoolIndex value within the SRS resource set configuration configured at the upper layer. As another example, as a more dynamic explicit association method, a MAC-CE can be used to enable the connection between a specific CORESET (including cases where the CORESETPoolIndex value is set to 0 or 1, or not set) and the SRS resource set. A terminal may consider the connection between a specific CORESET (including cases where the value of CORESETPoolIndex is set to 0 or 1, or not set) and an SRS resource set to be active after 3 ms of transmitting a HARQ-ACK after receiving a MAC-CE that enables the connection between the CORESET and the SRS resource set. An implicit method is to assume an implicit connection state using a specific criterion between the CORESETPoolIndex and the index of the SRS resource set. For example, if a terminal assumes that it has received two SRS resource sets, #0 and #1, the terminal may assume that SRS resource set #0 is connected to the CORESETs where CORESETPoolIndex is not set or is set to 0, and that SRS resource set #1 is connected to the CORESET where CORESETPoolIndex is set to 1.

[0483] For the single or multiple DCI-based methods described above, a terminal that has explicitly or implicitly established or been instructed to establish a connection between a different SRS resource set and each TRP may expect the srs-PowerControlAdjustmentStates value, which is set as upper layer signaling within each SRS resource set, to be set to sameAsFci2 and may not expect it to be set to separateClosedLoop. Additionally, it may expect the usage, which is set as upper layer signaling within each SRS resource set, to be set to codebook or noncodebook.

[0484] <Embodiments 1-5: Dynamic switching method for determining PUSCH transmission considering a single TRP or multiple TRPs based on a codebook>

[0485] In one embodiment of the present disclosure, embodiments 1-5 describe a dynamic switching method for determining a PUSCH transmission considering a single codebook-based TRP or a PUSCH transmission considering multiple TRPs.

[0486] According to the above embodiments 1-1 and 1-4, for a terminal capable of performing codebook-based PUSCH repetitive transmission by considering multiple TRPs based on a single DCI, the base station receives a terminal capability report from the terminal and can set up upper-layer signaling to the terminal to perform PUSCH repetitive transmission through multiple TRPs. At this time, when performing PUSCH repetitive transmission considering multiple TRPs based on a single DCI as in the embodiment 1-4, the base station may transmit a single DCI containing multiple SRI fields to the terminal to indicate SRS resources existing within different SRS resource sets. At this time, each of the multiple SRI fields can be interpreted in the same way as NR Release 15 / 16. More specifically, the first SRI field can select an SRS resource from the first SRS resource set, and the second SRI field can select an SRS resource from the second SRS resource set. Similar to multiple SRI fields, in order to repeatedly transmit PUSCH considering multiple TRPs, the base station may transmit a single DCI containing multiple TPMI fields to the terminal so that it can select a TPMI corresponding to the SRS resource indicated by each SRI field. In this case, the multiple TPMI fields may be indicated through the same DCI as the DCI containing the multiple SRI fields described above. Meanwhile, the multiple TPMIs to be used for PUSCH transmission to each TRP may be selected through the following methods utilizing multiple TPMI fields:

[0487] - [Method 1] Each TPMI field can be interpreted in the same way as in NR Release 15 / 16. For example, the first TPMI field may indicate the TPMI index and layer information for the SRS resource indicated by the first SRI field, and the second TPMI field may indicate the TPMI index and layer information for the SRS resource indicated by the second SRI field.

[0488] - [Method 2] The first TPMI field can indicate the TPMI index and layer information for the SRS resource indicated by the first SRI field in the same way as in NR Release 15 / 16. In contrast, the second TPMI field may not indicate layer information, as it selects the TPMI index for the same layer as the layer indicated by the first TPMI field, and may indicate the TPMI index information for the SRS resource indicated by the second SRI field.

[0489] In both the above methods 1 and 2, for codebook-based PUSCH iterative transmission, the number of layers indicated by the two TPMI fields (the first TPMI field and the second TPMI field) may be the same, and for non-codebook-based PUSCH iterative transmission, the number of layers indicated by the two SRI fields (the first SRI field and the second SRI field) may be the same.

[0490] Meanwhile, when multiple TPMIs are selected through Method 2, the bit length of the second TPMI field may be smaller compared to the first TPMI field. This is because the second TPMI field indicates the value (index) of one of the TPMI index candidates identical to the layer indicated by the first TPMI field, and thus may not indicate layer information.

[0491] The terminal may support a dynamic switching method that receives a single DCI containing multiple SRI fields and multiple TPMI fields, and based thereon determines whether to perform repeated PUSCH transmission considering multiple TRPs or repeated PUSCH transmission considering a single TRP. The terminal may support dynamic switching by utilizing a reserved value that has no meaning among the values ​​that the multiple TPMI fields or SRI fields included in the received DCI can have. For example, if the bit length of the SRI field is 2 bits, a total of 4 cases can be represented, and each of these representable cases can be defined as a code point. Furthermore, if three of the total 4 code points have meaning regarding which SRI to indicate, and the remaining 1 code point has no meaning, this code point can be referred to as a code point pointing to a reserved value (in the following description, a code point pointing to a reserved value may be described as being set to reserved). This will be explained in more detail through the content described below.

[0492] To explain a specific example of a dynamic switching method that multiple TPMI fields can support through reserved values, we assume a case where the PUSCH antenna port is 4. Additionally, we assume that the first TPMI field consists of 6 bits, the upper layer parameter codebookSubset is set to fullyAndPartialAndNonCoherent, and is indicated in the same way as NR Release 15 / 16. In this case, in the first TPMI field, indices 0 through 61 are set to indicate valid TPMI indices and layer information, and indices 62 through 63 can be set to reserved. If the second TPMI field contains only TPMI index information excluding layer information as in Method 2 above, the second TPMI field can indicate only the TPMI index for the case where the layer for PUSCH transmission is limited to a single value (e.g., one of 1 through 4) according to the first TPMI field. In this case, the number of bits in the second TPMI field can be set based on the number of bits that can represent the layer with the most candidates among the TPMI index candidates that can be set for each layer. For example, according to an example where layer 1 has candidates from 0 to 27, layer 2 has candidates from 0 to 21, layer 3 has candidates from 0 to 6, and layer 4 has candidates from 0 to 4, layer 1 has the most candidates. Therefore, the number of bits in the second TPMI field can be set to 5 according to the number of TPMI index candidates for layer 1. To explain the configuration of the second TPMI field in detail, if the first TPMI field indicates layer 1 and the corresponding TPMI index, the terminal can interpret the second TPMI field as a code point indicating one of the TPMI index values ​​from 0 to 27 for layer 1 and a code point indicating a reserved value.For example, if the first TPMI field indicates layer 2 and the corresponding TPMI index, the terminal can interpret the second TPMI field as a code point indicating a value among 0 to 21 for the TPMI index for layer 2 and a code point indicating a reserved value. In addition, for example, if the first TPMI field indicates layer 3 or layer 4 and the corresponding TPMI index, the terminal can interpret the second TPMI field in a similar manner as above. In this case, if there are two or more code points indicating a reserved value in addition to the code point indicating the TPMI index in the second TPMI field, the two code points indicating the reserved values ​​can be used to indicate dynamic switching. That is, among the code points of the second TPMI field composed of 5 bits, the second-to-last code point corresponding to the code point pointing to the reserved value (i.e., the 31st code point in the example) can be used to indicate a PUSCH repeated transmission considering a single TRP with the first TRP, and the last code point (i.e., the 32nd code point in the example) can be used to indicate a PUSCH repeated transmission considering a single TRP with the second TRP. At this time, the terminal may be instructed with layer information and TPMI index information for a PUSCH repeated transmission considering a single TRP in the first TPMI field. Meanwhile, the assumptions described above are for convenience of explanation and the present disclosure is not limited thereto.

[0493] For convenience of explanation, the above specific example regarding two TRPs is generalized as follows: A terminal receives a single DCI containing two SRI fields and two TPMI fields, and can perform dynamic switching according to the code point indicated by the second TPMI field. If the code point of the second TPMI field indicates a TPMI index for the layer indicated by the first TPMI field, the terminal can perform repeated PUSCH transmission considering multiple TRPs. If the second TPMI field indicates the second-to-last code point corresponding to the code point pointing to the reserved value, the terminal can perform repeated PUSCH transmission considering a single TRP for TRP 1, and can check layer information and TPMI index information for codebook-based PUSCH transmission from the first TPMI field. If the second TPMI field indicates the last code point corresponding to the code point pointing to the reserved value, the terminal can perform repeated PUSCH transmission considering a single TRP for TRP 2 and can check layer information and TPMI index information for codebook-based PUSCH transmission from the first TPMI field.

[0494] Meanwhile, although the above-described example used two reserved code points at the end of the second TPMI field to indicate dynamic switching, the present embodiment is not limited thereto. That is, dynamic switching can be indicated by using code points pointing to the other two reserved values ​​of the second TPMI field, and PUSCH repeated transmission considering a single TRP for TRP 1 or PUSCH repeated transmission considering a single TRP for TRP 2 can be indicated by mapping each code point pointing to a reserved value.

[0495] In addition, although the above example describes the case where the second TPMI field is determined by Method 2, dynamic switching can also be supported using the reserved code points of the TPMI in the same way as the above example, even when the second TPMI field is determined to be the same as NR Release 15 / 16 as in Method 1.

[0496] For example, if the number of code points pointing to the reserved value of the second TPMI field is less than 2, the number of bits in the second TPMI field is increased by 1, and based on the increased number of bits, the second-to-last code point and the last code point can be used to support dynamic switching.

[0497] When two TPMI fields are determined as in Method 1, a method to support dynamic switching may be additionally considered depending on whether each TPMI field is indicated as a code point pointing to a reserved value. That is, if the first TPMI field is indicated as a code point pointing to a reserved value, the terminal can perform repeated PUSCH transmissions considering a single TRP for TRP 2, and if the second TPMI field is indicated as a code point pointing to a reserved value, the terminal can perform repeated PUSCH transmissions considering a single TRP for TRP 1. If both TPMI fields indicate code points for TPMI rather than code points pointing to reserved values, the terminal can perform repeated PUSCH transmissions considering multiple TRPs. If there is no code point with a reserved value, the number of bits in the TPMI field is increased by 1, and the last code point based on the increased number of bits can be used to support dynamic switching.

[0498] Meanwhile, as another method to support dynamic switching, dynamic switching is indicated by two SRI fields, and the terminal can check layer information and TPMI index information for PUSCH repeated transmission considering multiple TRPs or a single TRP from two TPMI fields. If there is one or more code points pointing to reserved values ​​in each SRI field, dynamic switching can be supported depending on whether the corresponding SRI field indicates a code point pointing to a reserved value. If the first SRI field indicates a code point pointing to a reserved value and the second SRI field indicates an SRS resource of the second SRS resource set, the terminal can perform PUSCH repeated transmission considering a single TRP for TRP 2. At this time, the terminal can check layer information and TPMI index information from the first TPMI field to perform PUSCH repeated transmission considering a single TRP for TRP 2. If the second SRI field indicates a code point pointing to a reserved value and the second SRI field indicates an SRS resource of the second SRS resource set, the terminal can perform repeated PUSCH transmissions considering a single TRP for TRP 1. In this case, the terminal can check layer information and TPMI index information from the first TPMI field to perform repeated PUSCH transmissions considering a single TRP for TRP 1. If both SRI fields indicate an SRS resource of each SRS resource set rather than a code point pointing to a reserved value, the terminal can perform repeated PUSCH transmissions considering multiple TRPs.At this time, the terminal can check layer information and TPMI index information from the first TPMI field to perform repeated PUSCH transmission for TRP 1, and can check TPMI index information from the second TPMI field to perform repeated PUSCH transmission for TRP 2. At this time, the layer can be set identically for PUSCH transmission for TRP 1 and TRP 2. If there is no code point pointing to a reserved value in the two SRI fields, the number of bits in each SRI field is increased by 1, and the last code point among those pointing to a reserved value based on the increased number of bits can be used to support dynamic switching.

[0499] <Embodiment 1-6: Dynamic switching method for determining PUSCH transmission considering a single TRP or multiple TRPs based on a non-codebook>

[0500] In one embodiment of the present disclosure, embodiments 1-6 describe a dynamic switching method for determining a PUSCH transmission considering a non-codebook-based single TRP or a PUSCH transmission considering multiple TRPs.

[0501] According to the above embodiments 1-1 and 1-4, a base station receives a terminal capability report from a terminal capable of performing non-codebook-based PUSCH repetitive transmission by considering multiple TRPs based on a single DCI, and can set up upper-layer signaling to the terminal to perform PUSCH repetitive transmission through multiple TRPs. At this time, when performing PUSCH repetitive transmission considering multiple TRPs based on a single DCI as in the embodiment 1-4, the base station may transmit a single DCI containing multiple SRI fields to the terminal to indicate SRS resources existing within different SRS resource sets. Meanwhile, the multiple SRI fields may be selected, for example, according to the following method.

[0502] - [Method 1] Each SRI field can be selected in the same way as in NR Release 15 / 16. For example, the first SRI field can indicate an SRS resource for PUSCH transmission within the first SRS resource set, and the second SRI field can indicate an SRS resource for PUSCH transmission within the second SRS resource set.

[0503] - [Method 2] The first SRI field may indicate SRS resource(s) for PUSCH transmission within the first SRS resource set in the same way as in NR Release 15 / 16. The second SRI field may indicate SRS resource(s) for PUSCH transmission within the second SRS resource set for the same layer as the layer indicated by the first SRI field.

[0504] For both Method 1 and Method 2, in the case of codebook-based PUSCH iterative transmission, the number of layers indicated by the two TPMI fields (the first TPMI field and the second TPMI field) may be the same, and in the case of non-codebook-based PUSCH iterative transmission, the number of layers indicated by the two SRI fields (the first SRI field and the second SRI field) may be the same.

[0505] When selecting multiple SRIs through Method 2, the bit length of the second SRI field may be smaller than that of the first SRI field. This is because the second SRI is determined from among the SRI candidates for the same layer as the layer determined by the first SRI field among the SRI candidates for the entire supportable layer.

[0506] The terminal may support a dynamic switching method that receives a single DCI containing multiple SRIs and determines whether to perform repeated PUSCH transmission considering multiple TRPs or repeated PUSCH transmission considering a single TRP based thereon. The terminal may support dynamic switching by using code points pointing to reserved values ​​of multiple SRI fields included in the received DCI.

[0507] To explain a specific example of a dynamic switching method that can be supported through code points pointing to reserved values ​​of multiple SRI fields, we assume that the PUSCH antenna ports are up to 4 and the number of SRS resources within each SRS resource set is 4. Additionally, we assume that the first SRI field consists of 4 bits and is indicated in the same way as NR Release 15 / 16. In this case, in the first SRI area, indices 0 through 14 are set to indicate the SRS resource for PUSCH transmission and the layer corresponding to the selected SRS resource, and index 15 can be set as a code point pointing to a reserved value. If the second SRI field selects the same number of SRS resources as the number of layers indicated by the first SRI as in Method 2 above, the second SRI field can indicate a candidate for SRS resource selection when the layer for PUSCH transmission is limited to a single value (e.g., one of 1 to 4) according to the first SRI field. At this time, the number of bits in the second SRI field can be set based on the layer having the largest number of candidates among the number of SRS resource selection candidates for each layer. For example, there may be a total of 4 candidates with values ​​of 0 to 3 for the SRI field representing the SRS resource selection candidates for layer 1, a total of 6 candidates with values ​​of 4 to 9 for the SRI field representing the SRS resource selection candidates for layer 2, a total of 4 candidates with values ​​of 10 to 13 for the SRI field representing the SRS resource selection candidates for layer 3, and a total of 1 candidate with values ​​of 14 for the SRI field representing the SRS resource selection candidates for layer 4.In this case, since there are a total of 6 candidates for layer 2, which is the largest value, the number of bits in the second SRI field can be set to 3. To explain the configuration of the second SRI field in detail, if the first SRI field indicates an SRI value for the case where the layer for PUSCH transmission is 1, the terminal can interpret the second SRI field as a code point indicating one of the SRI candidates 0 to 3 for layer 1, or as a code point having a reserved value for any other value. For example, if the first SRI field indicates an SRI value for the case where the layer for PUSCH transmission is 2, the terminal can interpret the second SRI field as a code point indicating one of the SRI candidates 0 to 5 for layer 2, or as a code point having a reserved value for any other value. Additionally, for example, if the first SRI field indicates an SRI value for the case where the layer for PUSCH transmission is 3 or 4, the terminal can interpret the second SRI field in a similar manner. In this case, if there are two or more code points pointing to reserved values ​​in addition to the code point indicating the SRI value according to the layer in the second SRI field, the two code points pointing to reserved values ​​can be used to indicate dynamic switching. That is, among the code points of the second SRI field composed of 3 bits, the second-to-last code point corresponding to the code point pointing to the reserved value (i.e., the 7th code point in the example) can be used to indicate repeated PUSCH transmission considering a single TRP with the first TRP, and the last code point (i.e., the 8th code point in the example) can be used to indicate repeated PUSCH transmission considering a single TRP with the second TRP. In this case, the terminal can be instructed with the SRI for repeated PUSCH transmission considering a single TRP in the first SRI field.Meanwhile, the assumptions set forth above are for the convenience of explanation and the present disclosure is not limited thereto.

[0508] For convenience of explanation, the above specific example regarding two TRPs is generalized as follows: A terminal receives a single DCI containing two SRI fields and can perform dynamic switching according to the code point indicated by the second SRI field. If the code point of the second SRI field indicates an SRI value for the layer indicated by the first SRI field, the terminal can perform repeated PUSCH transmissions considering multiple TRPs. If the second SRI field indicates the second-to-last code point corresponding to the code point pointing to the reserved value, the terminal can perform repeated PUSCH transmissions considering a single TRP for TRP 1 and can identify the SRI for non-codebook-based PUSCH transmission from the first SRI field. If the second SRI field indicates the last code point corresponding to the code point pointing to the reserved value, the terminal can perform repeated PUSCH transmissions considering a single TRP for TRP 2 and can identify the SRI for non-codebook-based PUSCH transmission from the first SRI field.

[0509] Meanwhile, although the above-described example used code points pointing to two reserved values ​​at the end of the second SRI field to indicate dynamic switching, the present embodiment is not limited thereto. That is, dynamic switching can be indicated by using code points pointing to the other two reserved values ​​of the second SRI field, and PUSCH repeated transmission considering a single TRP for TRP 1 or PUSCH repeated transmission considering a single TRP for TRP 2 can be indicated by mapping each code point pointing to a reserved value.

[0510] In addition, although the above example describes the case where the second SRI field is determined by Method 2, dynamic switching can also be supported by using a code point pointing to the reserved value of the SRI field in the same way as the above example, even when the second SRI field is determined to be the same as NR Release 15 / 16 as in Method 1.

[0511] For example, if the number of code points pointing to the reserved value of the second SRI field is less than 2, the number of bits in the second SRI field is increased by 1, and based on the increased number of bits, the second-to-last code point and the last code point can be used to support dynamic switching.

[0512] When two SRI fields are determined as in Method 1, a method to support dynamic switching may be additionally considered depending on whether each SRI field is indicated as a code point pointing to a reserved value. That is, if the first SRI field is indicated as a code point pointing to a reserved value, the terminal can perform repeated PUSCH transmissions considering a single TRP for TRP 2, and if the second SRI field is indicated as a code point pointing to a reserved value, the terminal can perform repeated PUSCH transmissions considering a single TRP for TRP 1. If both SRI fields indicate code points for indicating SRI rather than code points pointing to a reserved value, the terminal can perform repeated PUSCH transmissions considering multiple TRPs. If there is no code point pointing to a reserved value, the number of bits in the SRI area is increased by 1, and the last code point based on the increased number of bits can be used to support dynamic switching.

[0513] <Embodiment 1-7: Dynamic switching method between single or multiple TRP-based PUSCH transmissions using a novel DCI field>

[0514] The first-seventh embodiments of the present disclosure describe a method for supporting dynamic switching between single or multiple TRP-based PUSCH transmissions using a novel DCI field.

[0515] The aforementioned embodiments 1-5 to 1-6 can perform dynamic switching between single or multiple TRP-based PUSCH transmissions through multiple SRI fields or multiple TPMI fields indicated when performing support considering multiple TRPs, rather than through a separate additional new field within the DCI. Meanwhile, depending on whether the number of reserved code points in SRI or TPMI is equal to the number of code points required to indicate dynamic switching between single or multiple TRP-based PUSCH transmissions, there may be cases where operation is impossible with only the SRI field or TPMI field, or the bitwidth of the SRI field or TPMI field may need to be increased to secure an additional number of reserved code points. Therefore, an additional new DCI field may be used to support dynamic switching between single or multiple TRP-based PUSCH transmissions independently of the number of reserved code points in the SRI field or TPMI field. The additional new DCI field for supporting dynamic switching between single or multiple TRP-based PUSCH transmissions may be considered to have a bitwidth of 1 bit or 2 bits. Meanwhile, in this embodiment, the bitwidth of the new DCI field may be the aforementioned 1 bit or 2 bits, or it may have more bits. Below, we will explain using the case where the bitwidth of the new DCI field is 1 bit or 2 bits as an example.

[0516] [Method 1-7-1] Using a new DCI field with the bitwidth fixed at 2 bits

[0517] If an additional 2-bit new DCI field is used, up to 4 code points can be used for dynamic switching between single or multiple TRP-based PUSCH transmissions. For example, the first code point '00' for the additional new DCI field can be used to indicate a PUSCH repetitive transmission considering multiple TRPs. In this case, in the case of a codebook-based PUSCH repetitive transmission, when transmitting to each TRP, the first SRI and first TPMI fields corresponding to the first TRP can be used for transmission first, and then the second SRI and second TPMI fields corresponding to the second TRP can be used for transmission. Alternatively, in the case of a non-codebook-based PUSCH repetitive transmission, when transmitting to each TRP, the first SRI field corresponding to the first TRP can be used for transmission first, and then the second SRI field corresponding to the second TRP can be used for transmission. That is, when mapping each TRP for each PUSCH repetitive transmission based on a codebook or non-codebook, the mapping can be done in the order of the first TRP and the second TRP (this content may be referred to as the “beam mapping order for multiple TRPs” when described later). The second code point ‘01’ for the additional new DCI field can be used to indicate a PUSCH repetitive transmission considering a single TRP using the first TRP. The third code point ‘10’ for the additional new DCI field can be used to indicate a PUSCH repetitive transmission considering a single TRP using the second TRP.The fourth code point '11' for the additional new DCI field may be set as a reserved code point, or, when the base station receives a terminal capability report supporting a change in beam mapping order for multiple TRPs from the terminal and a corresponding upper layer signaling (e.g., an upper layer setting for changing the beam mapping order for TRPs) is set, it may be used to instruct a PUSCH repeated transmission considering multiple TRPs with a beam mapping order for multiple TRPs applied that is different from the first code point described above. Additionally, regardless of whether the terminal capability report described above and the corresponding upper layer signaling are set, it may be used to instruct a PUSCH repeated transmission considering multiple TRPs with a beam mapping order for multiple TRPs applied that is different from the first code point. Here, changing the beam mapping order for multiple TRPs may mean performing transmission in the order of the second TRP and the first TRP, contrary to the case where transmission was performed in the order of the first TRP and the second TRP when using the first code point mentioned above. Regarding the PUSCH repeat transmission considering a single TRP among the descriptions of the four code points mentioned above, if a code point instructing a first TRP-based PUSCH repeat transmission is instructed to the terminal by the base station through an additional new DCI field, if it is a codebook-based PUSCH repeat transmission, the terminal can perform the first TRP-based PUSCH repeat transmission using the first SRI field and the first TPMI field, and if it is a non-codebook-based PUSCH repeat transmission, the terminal can perform the first TRP-based PUSCH repeat transmission using the first SRI field. In this case, the first SRI field is connected to the first SRS resource set and can be used to indicate an SRS resource within the said SRS resource set.Additionally, if the terminal is instructed by a code point from the base station through an additional new DCI field to instruct a second TRP-based PUSCH repeat transmission, if it is a codebook-based PUSCH repeat transmission, the terminal can perform a second TRP-based PUSCH repeat transmission using the first SRI field and the first TPMI field, and if it is a non-codebook-based PUSCH repeat transmission, the terminal can perform a second TRP-based PUSCH repeat transmission using the first SRI field. In this case, the first SRI field is associated with the second SRS resource set and can be used to indicate an SRS resource within the said SRS resource set. The above-described single TRP (first or second TRP)-based PUSCH repetitive transmission method can be considered as a method in which, when either the first TRP or the second TRP is selected according to a code point indicated by an additional new DCI field, the first SRI field and the first TPMI field among the two SRI fields and two TPMI fields are used for codebook-based PUSCH repetitive transmission, and the first SRI field among the two SRI fields is used for non-codebook-based PUSCH repetitive transmission, and the second fields (the second SRI field and the second TPMI field) are not used.Meanwhile, the single TRP-based PUSCH repetitive transmission method described immediately below can be considered as a method that uses the first field (the first SRI field or the first TPMI field) if it is the first TRP-based PUSCH repetitive transmission method (i.e., when the first TRP is selected or when the first TRP-based PUSCH repetitive transmission is indicated according to the code point), and uses the second field (the second SRI field or the second TPMI field) if it is the second TRP-based PUSCH repetitive transmission method (i.e., when the second TRP is selected or when the second TRP-based PUSCH repetitive transmission is indicated according to the code point). As another example of a PUSCH repeat transmission considering a single TRP among the descriptions of the four code points mentioned above, if a code point instructing a first TRP-based PUSCH repeat transmission is instructed to the terminal by the base station through an additional new DCI field, if it is a codebook-based PUSCH repeat transmission, the terminal can perform the first TRP-based PUSCH repeat transmission using the first SRI field and the first TPMI field, and if it is a non-codebook-based PUSCH repeat transmission, the terminal can perform the first TRP-based PUSCH repeat transmission using the first SRI field. In this case, the first SRI field is connected to the first SRS resource set and can be used to indicate an SRS resource within that SRS resource set.Additionally, if the terminal is instructed by a code point from the base station through an additional new DCI field to instruct a second TRP-based PUSCH repeat transmission, if it is a codebook-based PUSCH repeat transmission, the terminal can perform the second TRP-based PUSCH repeat transmission using the second SRI field and the second TPMI field, and if it is a non-codebook-based PUSCH repeat transmission, the terminal can perform the second TRP-based PUSCH repeat transmission using the second SRI field. In this case, the second SRI field is associated with the second SRS resource set and can be used to indicate an SRS resource within the said SRS resource set.

[0518] The above example illustrates a PUSCH iterative transmission considering multiple TRPs or a PUSCH iterative transmission considering a single TRP based on four code points, and each code point and the corresponding operation may differ from the example (for example, code point “11” may be used to indicate a PUSCH iterative transmission considering multiple TRPs, code point “10” may be used to indicate a PUSCH iterative transmission considering multiple TRPs with a beam mapping order applied for multiple TRPs different from code point “11”, and code point ‘00’ may be used to indicate a PUSCH iterative transmission considering a single TRP using the first TRP).

[0519] [Method 1-7-2] Using a new DCI field with the bitwidth fixed at 1 bit

[0520] The example described in Method 1-7-1 above is an example of using a fixed 2 bits for the length (bitwidth) of the additional new DCI field. Meanwhile, to reduce DCI overhead, the bit length of the additional new DCI field may be fixed to 1 bit, and two SRI fields or two TPMI fields may be used together to support dynamic switching between single or multiple TRP-based PUSCH transmissions. For example, the additional new DCI field may be used to indicate whether the PUSCH transmission is based on a single TRP or multiple TRPs. For example, if the new DCI field is indicated as '0', the terminal may perform a PUSCH transmission based on a single TRP. Also, the second field (the second SRI field or the second TPMI field) of the two SRI fields or (if available) two TPMI fields may be used to indicate the TRP, and the first SRI field or the first TPMI field may be used as information for the PUSCH transmission. That is, the second SRI field or the second TPMI field indicates one of the two SRS resource sets, either 'codebook' or 'nonCodebook', to be used for PUSCH transmission, and the first SRI field or the first TPMI field may indicate SRS resource or TPMI index and layer information for the SRS resource set indicated by the second SRI field or the second TPMI field. Since the second SRI field and the second TPMI field are not used for PUSCH transmission considering a single TRP, the second SRI field or the second TPMI field may be reused for selecting a TRP.For example, when an additional new DCI field for dynamic switching between single or multiple TRP-based PUSCH transmissions is set to '0' to perform a PUSCH transmission considering a single TRP, the first code point of the second SRI field may be reinterpreted to mean that a PUSCH transmission should be performed based on the first TRP (the first TRP), i.e., the first SRS resource set (used as 'codebook' or 'nonCodebook'). Alternatively, if the second code point of the second SRI field is reinterpreted to mean that a PUSCH transmission should be performed based on the second TRP (the second TRP), i.e., the second SRS resource set (used as 'codebook' or 'nonCodebook'). Meanwhile, this is merely an example given to explain the present embodiment, and the present embodiment is not limited thereto.

[0521] Alternatively, if an additional new DCI field is indicated as '1', the terminal may perform a PUSCH transmission considering multiple TRPs. In this case, both SRI fields (the first SRI field and the second SRI field) or two TPMI fields (the first TPMI field and the second TPMI field) may be used as information for a PUSCH transmission considering multiple TRPs. For example, a PUSCH transmission may be performed using the first SRI field and the first TPMI field corresponding to the first TRP, and a PUSCH transmission may be performed using the second SRI field and the second TPMI field corresponding to the second TRP. Meanwhile, this is merely an example given to explain the present embodiment, and the present embodiment is not limited thereto.

[0522] [Method 1-7-3] Case where the bitwidth of the new DCI field is determined to be either 1 bit or 2 bits based on the upper layer signaling

[0523] As another method for performing dynamic switching between single or multiple TRP-based PUSCH transmissions using an additional new DCI field, the bitwidth of the additional new DCI field can be determined according to the conditions of the upper layer signaling. The aforementioned method for dynamic switching between single or multiple TRP-based PUSCH transmissions using an additional new DCI field of 1 bit length can be used when a second SRI field or a second TPMI field exists. That is, it cannot be used if the second SRI field or the second TPMI field does not exist. Meanwhile, whether the second SRI field or the second TPMI field exists can be determined based on the upper layer settings. For example, when performing a non-codebook-based PUSCH transmission, if the number of SRS resources included in the second SRS resource set is 1, the second SRI field may not exist. As another example, when performing codebook-based PUSCH transmission, if the number of SRS resources included in the second SRS resource set is 1 and the number of antenna ports configured in that SRS resource is 1, then both the second SRI field and the second TPMI field may not exist. Based on this rule, the base station can determine the presence or absence of the second SRI field or the second TPMI field according to the upper layer settings configured on the terminal, and based on this, the base station can set the bitwidth of an additional new DCI field for dynamic switching between single or multiple TRP-based PUSCH transmissions to 1 bit or 2 bits.If a second SRI field or a second TPMI field exists depending on the upper layer configuration of the base station, the base station may set the bitwidth of an additional new DCI field for dynamic switching between single or multiple TRP-based PUSCH transmissions to 1 bit. If a second SRI field or a second TPMI field does not exist depending on the upper layer configuration of the base station, the base station may set the bitwidth of an additional new DCI field for dynamic switching between single or multiple TRP-based PUSCH transmissions to 2 bits.

[0524] Through the above 1-7 embodiments, [Methods 1-7-1] to [Methods 1-7-3], which perform dynamic switching between single or multiple TRP-based PUSCH transmissions using an additional novel DCI field, can be described as a series of operations below. Meanwhile, the following operations may be performed in sequence or simultaneously, and some of them may be omitted.

[0525] 1) The terminal may report to the base station a UE capability for operation considering multiple TRPs. In this case, the reported UE capability may include support for at least one of [Method 1-7-1] to [Method 1-7-3], information regarding the multi-TRP transmission mapping order when reporting support for [Method 1-7-1], etc.

[0526] 2) The base station may set and use one of [Method 1-7-1] to [Method 1-7-3] as an upper layer signaling according to the reported UE capability, or, regardless of the UE capability, perform dynamic switching for PUSCH repetitive transmission considering a single or multiple TRP based on one of [Method 1-7-1] to [Method 1-7-3] without a specific upper layer signaling according to a method predetermined by the specification between the terminal and the base station.

[0527] A. When one of [Method 1-7-1] to [Method 1-7-3] is configured and used according to upper layer signaling, the terminal can perform dynamic switching for PUSCH repetitive transmission considering a single or multiple TRP based on one of the configured [Method 1-7-1] to [Method 1-7-3].

[0528] B. When a standardized predetermined method is used between a terminal and a base station, dynamic switching for PUSCH repetitive transmission considering a single or multiple TRP can be performed based on any one of the methods [Method 1-7-1] to [Method 1-7-3] described above, determined according to the predetermined method.

[0529] <Second Embodiment: Frequency Hopping and Transmission Beam Mapping Method for Repeated PUSCH Transmission Considering Multiple TRPs>

[0530] The second embodiment of the present disclosure describes frequency hopping and transmission beam mapping methods for each PUSCH during repeated PUSCH transmission considering multiple TRPs. Here, the transmission beam may be an indicator collectively referring to an SRS resource, an SRS spatial relation, or an SRS spatial relation and TPMI connected to a single SRS spatial relation info. The frequency hopping method and the transmission beam mapping method may operate independently or dependently by being set to upper layer signaling, indicated by L1 signaling, or a combination of being set to upper layer signaling and indicated by L1 signaling. The fact that the frequency hopping method and the transmission beam mapping method are performed independently means that the two methods are transmitted to the terminal with independent signaling (e.g., being set to upper layer signaling, indicated by L1 signaling, or a combination of being set to upper layer signaling and indicated by L1 signaling). However, not all possible combinations of the frequency hopping method and all possible combinations of the transmission beam mapping method may be possible. For example, if there are three frequency hopping methods and four transmission beam mapping methods, not all 12 combinations are supported, and only 10 combinations may be supported. Each item will be explained in detail through the following detailed embodiments.

[0531] <Embodiment 2-1: Transmission Beam Mapping Method for Repeated PUSCH Transmission Considering Multiple TRPs>

[0532] In the 2-1 embodiment, a transmission beam mapping method for PUSCH repetitive transmission considering multiple TRPs is described. When a base station transmits multiple transmission beams by setting them as upper layer signaling, instructing them as L1 signaling, or transmitting them as a combination of setting them as upper layer signaling and instructing them as L1 signaling, the terminal can determine how to perform transmission beam mapping for PUSCH repetitive transmission considering multiple TRPs. The information regarding the multiple transmission beams may be an SRI where multiple SRS spatial relation infos are connected, or an SRI where one SRS spatial relation info is connected. Among the multiple transmission beam information received by the terminal, the base station may transmit information on how to map which transmission beam to each PUSCH repetitive transmission—that is, the transmission beam mapping unit—by setting it as upper layer signaling, instructing it as L1 signaling, or transmitting it as a combination of setting it as upper layer signaling and instructing it as L1 signaling. Additionally, when considering multiple TRPs, the total number of PUSCH repeated transmissions can be set via upper layer signaling, indicated via L1 signaling, or conveyed as a combination of upper layer signaling setting and L1 signaling indication.

[0533] The transmission beam mapping unit may be one of the following candidates.

[0534] - Each slot, subslot, or multiple slots, subslots

[0535] - Each iteration transmission (nominal or actual) or multiple iteration transmissions (nominal or actual)

[0536] - Each symbol or multiple symbols

[0537] - 1 / N of the total number of repeated transmissions

[0538] If the unit of transmission beam mapping is a slot, the same transmission beam is applied to all PUSCH repeat transmissions (nominal or actual) within the slot, and transmission beam changes are performed on a slot basis. For example, if the total number of PUSCH repeat transmissions is 4, the number of transmission beams is 2, the unit of transmission beam mapping is a slot, and there are 2 PUSCH repeat transmissions within each slot, the first transmission beam may be applied to the first and second PUSCH repeat transmissions transmitted in the first slot, and the second transmission beam may be applied to the third and fourth PUSCH repeat transmissions transmitted in the second slot. As another example, if the total number of repeated transmissions is 4, the number of transmission beams is 2, the transmission beam mapping unit is 2 slots, and 1 PUSCH repeated transmission is performed within each slot, the first transmission beam may be applied to the first and second PUSCH repeated transmissions transmitted in the first and second slots, respectively, and the second transmission beam may be applied to the third and fourth PUSCH repeated transmissions transmitted in the third and fourth slots, respectively.

[0539] If the unit of transmission beam mapping is 1 / N of the total number of PUSCH repeat transmissions, N may be a divisor of the total number of repeat transmissions or a natural number greater than or equal to 2 and less than or equal to the total number of repeat transmissions. For example, if the total number of PUSCH repeat transmissions is 6, the number of transmission beams is 2, and the unit of transmission beam mapping is 1 / 2 of the total number of repeat transmissions (N=2), the terminal may apply the first transmission beam to the 1st to 3rd PUSCH repeat transmissions and apply the second transmission beam to the 4th to 6th PUSCH repeat transmissions.

[0540] In addition, regarding a fixed transmission beam mapping unit among the above transmission beam mapping units, or a transmission beam mapping unit received by the terminal from the base station as a combination of upper layer signaling, L1 signaling, or a combination of upper layer signaling and L1 signaling, the base station may transmit to the terminal a transmission beam mapping method as either cyclical or sequential, as a combination of upper layer signaling and L1 signaling. For example, if the total number of PUSCH repeat transmissions is 6, the number of transmission beams is 2, the transmission beam mapping unit is each repeat transmission (nominal or actual), and the transmission beam mapping method is cyclical, the terminal may apply the first transmission beam to the odd-numbered PUSCH repeat transmissions and apply the second transmission beam to the even-numbered PUSCH repeat transmissions. In addition, when the transmission beam mapping method is sequential, the number of transmission beam mapping units to which the same transmission beam is applied may be 2 or a divisor of the total number of repeated transmissions, and the information may be predetermined (e.g., fixed at 2 without specific signaling), set as upper layer signaling, indicated as L1 signaling, or transmitted as a combination of setting as upper layer signaling and indicating as L1 signaling. In the above example, if the transmission beam mapping method is sequential and the number of transmission beam mapping units to which the same transmission beam is applied is 2, the terminal may apply the 1st transmission beam for the 1st and 2nd PUSCH repeated transmissions, apply the 2nd transmission beam for the 3rd and 4th PUSCH repeated transmissions, and apply the 1st transmission beam for the 5th and 6th PUSCH repeated transmissions.

[0541] <Embodiment 2-2: Independent Frequency Hopping and Transmission Beam Mapping Method>

[0542] In the 2-2 embodiment, a method for performing frequency hopping and transmission beam mapping independently of each other during PUSCH iterative transmission considering multiple TRPs is described. Similar to the transmission beam mapping unit transmission process from the base station, the frequency hopping method may be transmitted from the base station to the terminal as set to upper layer signaling, instructed as L1 signaling, or a combination of set to upper layer signaling and instruction of L1 signaling. Additionally, the terminal may receive the frequency hopping method from the base station independently of the transmission beam mapping unit transmission process from the base station. For the frequency hopping unit, the following candidates may be possible.

[0543] - Between slots or multiple slots

[0544] - Frequency hopping method within the slot

[0545] - Frequency hopping method between repeated transmissions or between multiple repeated transmissions

[0546] - Frequency hopping method within iterative transmission

[0547] The terminal can independently apply a frequency hopping method and a transmission beam mapping unit received by being set to upper layer signaling, indicated by L1 signaling, or a combination of being set to upper layer signaling and indicated by L1 signaling.

[0548] FIG. 19 is a diagram illustrating a method for independently determining frequency hopping and transmission beam mapping during PUSCH repeated transmission considering multiple TRPs according to one embodiment of the present disclosure. For example, when the PUSCH repeated transmission method is PUSCH repeated transmission type B, the total number of PUSCH repeated transmissions (e.g., the number of nominal repetitions) is 5, the symbol length of the nominal repetition is 10, the frequency hopping method used is a frequency hopping method between nominal repetitions, the transmission beam mapping unit is a slot, the number of PUSCH repeated transmissions within the slot is 1, the starting RB position is 0 RB, and the RB offset due to frequency hopping is 10 RB, the terminal applies the 1st transmission beam in the 1st (1901, 1902) and 3rd (1905, 1906) slots, and applies the 2nd transmission beam in the 2nd (1903, 1904) and 4th (1907) slots. The terminal transmits the 1st actual repetition (1901) from RB#0 in slot #1 and the 2nd actual repetition (1902) from RB#10 in slot #1. The terminal transmits the 3rd actual repetition (1903) from RB#10 in slot #2 and the 4th actual repetition (1904) from RB#0 in slot #2. The terminal transmits the 5th actual repetition (1905) from RB#0 in slot #3 and the 6th actual repetition (1906) from RB#10 in slot #3. The terminal transmits the 7th actual repetition (1907) from RB#0 in slot #4.

[0549] In addition, when a combination of a specific frequency hopping method and a transmission beam mapping unit is set to upper layer signaling, indicated to L1 signaling, or transmitted as a combination of setting to upper layer signaling and indicating to L1 signaling, the base station and the terminal may insert one or more symbol gaps between each frequency hopping or between each repeated transmission of frequency hopping, along with changes in transmission power due to the application of different transmission beams, or drop one or more transmission symbols.

[0550] Additionally, the base station and the terminal may not support a combination of a specific frequency hopping method and a transmission beam mapping unit as described above. For example, when a combination of a specific frequency hopping method and a transmission beam mapping unit is used, if no frequency hopping occurs or only one transmission beam mapping occurs, the combination may not be supported. For example, if the total number of PUSCH repeat transmissions is 2, the frequency hopping unit is a slot, the transmission beam mapping unit is each PUSCH repeat transmission, and the number of PUSCH repeat transmissions within a slot is 2, the terminal maps the first transmission beam for the first PUSCH repeat transmission in the first slot, maps the second transmission beam for the second PUSCH repeat transmission, and does not perform frequency hopping. The terminal may not expect to receive such a combination from the base station as a higher layer signaling, as an instruction as an L1 signaling, or as a combination of a higher layer signaling and an instruction as an L1 signaling.

[0551] <2-3rd Embodiment: Dependent Frequency Hopping and Transmission Beam Mapping Method>

[0552] In the 2nd and 3rd embodiments, a method is described for performing frequency hopping and transmission beam mapping methods dependently on each other during repeated PUSCH transmission considering multiple TRPs. Determining the frequency hopping and transmission beam mapping methods dependently is intended to maximize frequency diversity and spatial diversity for repeated PUSCH transmission considering multiple TRPs. For example, the frequency hopping unit may be larger than the transmission beam mapping unit. That is, the terminal can transmit PUSCH at the same frequency location by applying different transmission beams, and then perform frequency hopping to another frequency location to transmit PUSCH at that location by applying different transmission beams. As another example, the frequency hopping unit may be smaller than the transmission beam mapping unit. That is, the terminal can transmit PUSCH at different frequency locations by applying the same transmission beam, and then transmit PUSCH at different frequency locations by applying different transmission beams. The method of having dependency between the frequency hopping unit and the transmission beam mapping unit as described above can consider the following three cases.

[0553] [Method 1] Use independent configuration of frequency hopping and transmission beam mapping units

[0554] The terminal can perform dependent frequency hopping and transmission beam mapping using the frequency hopping method and each transmission method of the transmission beam mapping unit described above. Each transmission method may be the same as described above, but additional constraints may exist.

[0555] For example, if a terminal is configured by the base station for a frequency hopping method and a transmission beam mapping method using upper layer signaling, L1 signaling, or a combination of upper layer signaling and L1 signaling, the frequency hopping unit can be expected to be smaller than the transmission beam mapping unit. For instance, if the terminal is configured by the upper layer signaling for a frequency hopping method in slot units, L1 signaling, or a combination of upper layer signaling and L1 signaling, the terminal does not expect to be configured by the upper layer signaling for a transmission beam mapping unit larger than a slot, L1 signaling, or a combination of upper layer signaling and L1 signaling.

[0556] As another example, if a terminal is configured by the base station for frequency hopping methods and transmission beam mapping methods using upper layer signaling, L1 signaling, or a combination of upper layer signaling and L1 signaling, the frequency hopping unit can be expected to be larger than the transmission beam mapping unit. For instance, if the terminal is configured by the upper layer signaling for frequency hopping methods in slot units, instructed by L1 signaling, or configured and instructed by a combination of upper layer signaling and L1 signaling, the terminal does not expect to be configured by the upper layer signaling, instructed by L1 signaling, or configured and instructed by a combination of upper layer signaling and L1 signaling for transmission beam mapping units smaller than slots.

[0557] [Method 2] Frequency Hopping Unit Setting-Based Transmission Beam Mapping Unit Setting

[0558] The terminal can support transmission beam mapping units according to a frequency hopping method that is set or instructed by the base station as upper layer signaling, as L1 signaling, or as a combination of upper layer signaling and L1 signaling. That is, the terminal can set or instruct transmission beam mapping units as multiples of the set or instructed frequency hopping units. For example, if the terminal sets or instructs a slot-unit frequency hopping method from the base station, the terminal can set or instruct transmission beam mapping units as one slot or multiple slots.

[0559] FIG. 20 is a diagram illustrating a transmission beam mapping unit setting based on a frequency hopping unit setting according to one embodiment of the present disclosure. Assuming that the number of repeated PUSCH transmissions is 4, the frequency hopping method is slot-based, the transmission beam mapping unit is set or specified to 2 so that transmission beam mapping is performed in units of 2 slots, the number of repeated PUSCH transmissions within a slot is 1, the starting RB position is RB 0, and the frequency hopping RB offset is 10 RB, then the terminal transmits PUSCH by applying the 1st transmission beam at RB 0 for the 1st repeated PUSCH transmission in the 1st slot (2001), transmits PUSCH by applying the 1st transmission beam at RB 10 for the 2nd repeated PUSCH transmission in the 2nd slot (2002), transmits PUSCH by applying the 2nd transmission beam at RB 0 for the 3rd repeated PUSCH transmission in the 3rd slot (2003), and transmits PUSCH by applying the 2nd transmission beam at RB 10 for the 4th repeated PUSCH transmission in the 4th slot Transmits (2004).

[0560] Additionally, the terminal may set or be instructed to set a transmission beam mapping unit in a unit lower than the set or instructed frequency hopping unit. To set or instruct the transmission beam mapping unit to be lower than the frequency hopping unit, the base station may apply the following two methods.

[0561] [Method 3] Define available frequency hopping units as a set, and select a transmission beam mapping unit from that set.

[0562] The terminal may predefine a set containing units of available frequency hopping. The set may be defined in the following order.

[0563] - Unit 1. Within actual PUSCH repeated transmissions

[0564] - Unit 2. Actual PUSCH repeated transmission

[0565] - Unit 3. Within nominal PUSCH repeated transmission

[0566] - Unit 4. Nominal PUSCH repeated transmission

[0567] - Unit 5. Slot

[0568] The terminal may be configured or instructed by the base station via upper layer signaling, L1 signaling, or a combination of upper layer signaling and L1 signaling to determine which unit lower than the frequency hopping unit within the set the transmission beam mapping unit uses. For example, if the terminal is configured or instructed by the base station to use a slot unit frequency hopping method of unit 5, and is configured or instructed to use a transmission beam mapping unit one step lower than the frequency hopping unit, the terminal may perform transmission beam mapping with a nominal PUSCH iterative transmission unit of unit 4.

[0569] Additionally, when a transmission beam mapping unit, transmission beam mapping method, or frequency hopping method is set to upper layer signaling or indicated by L1 signaling, or transmitted as a combination of being set to upper layer signaling and being indicated by L1 signaling, the terminal may ignore the frequency hopping method to reduce the burden on the terminal during PUSCH repeated transmission considering multiple TRPs. Furthermore, when a transmission beam mapping unit, transmission beam mapping method, or frequency hopping method is set to upper layer signaling or indicated by L1 signaling, or transmitted as a combination of being set to upper layer signaling and being indicated by L1 signaling, the terminal does not expect both the transmission beam mapping unit and the frequency hopping unit to be applied within the slot (e.g., when the transmission beam mapping unit is actual repetition and the frequency hopping unit is repeated transmission within the slot).

[0570] <Third Embodiment: PUSCH transmission beam mapping method considering slot format during PUSCH repetitive transmission considering multiple TRPs>

[0571] In one embodiment of the present disclosure, a PUSCH transmission beam mapping method considering a slot format is described. In the 3-1 embodiment, a method for a base station to instruct a terminal on a slot format is described, and in the 3-2 embodiment, a transmission beam mapping method considering a slot format for dynamic grant-based or configured grant-based PUSCH repetitive transmission considering multiple TRPs is described.

[0572] <3-1 Embodiment: Slot Format Indication Method>

[0573] In the 3-1 embodiment, a method for a base station to instruct a terminal on a slot format is described. In a 5G communication system, the downlink signal transmission interval and the uplink signal transmission interval may be dynamically changed. To this end, the base station may instruct the terminal via a Slot Format Indicator (SFI) whether each OFDM symbol constituting a slot is a downlink symbol, an uplink symbol, or a flexible symbol. Here, a flexible symbol may refer to a symbol that is neither a downlink nor an uplink symbol, or a symbol that can be changed into a downlink or an uplink symbol by terminal-specific control information or scheduling information. In this case, the flexible symbol may include a gap guard required during the transition from downlink to uplink.

[0574] A terminal that receives the above slot format indicator may perform a downlink signal reception operation from a base station in the symbol indicated by the downlink symbol, and perform an uplink signal transmission operation to a base station in the symbol indicated by the uplink symbol. For the symbol indicated by the flexible symbol, the terminal may perform at least a PDCCH monitoring operation, and through another indicator, e.g. DCI, the terminal may perform a downlink signal reception operation from a base station in the flexible symbol (e.g., when receiving DCI format 1_0 or 1_1) or perform an uplink signal transmission operation to a base station (e.g., when receiving DCI format 0_0 or 0_1).

[0575] FIG. 21 is a drawing illustrating an example of an uplink-downlink configuration (UL / DL configuration) in a wireless communication system according to one embodiment of the present disclosure.

[0576] Referring to FIG. 21, three steps of uplink-downlink configuration for a symbol / slot are illustrated. In the first step, the uplink-downlink of a symbol / slot can be configured using cell-specific configuration information (2110) for semi-static uplink-downlink configuration, such as system information like SIB. Specifically, the cell-specific uplink-downlink configuration information (2010) within the system information may include uplink-downlink pattern information and information indicating a reference subcarrier interval. The above uplink-downlink pattern information may indicate the transmission periodicity (2103) of each pattern, the number of consecutive full DL slots at the beginning of each DL-UL pattern (2111), the number of consecutive DL symbols in the beginning of the slot following the last full DL slot (2112), the number of consecutive full UL slots at the end of each DL-UL pattern (2113), and the number of consecutive UL symbols in the end of the slot preceding the first full UL slot (2114). At this time, the terminal may determine a slot / symbol that is not indicated as an uplink or downlink as a flexible slot / symbol.

[0577] In the second step, terminal-specific configuration information (2120) transmitted via terminal-specific upper layer signaling (i.e., RRC signaling) may indicate symbols to be configured as downlink or uplink within a flexible slot or a slot (2121, 2122) containing a flexible symbol. For example, the terminal-specific uplink-downlink configuration information (2120) may include a slot index indicating a slot (2121, 2122) containing a flexible symbol, a number of consecutive downlink symbols in the beginning of each slot (2123, 2125), and a number of consecutive uplink symbols in the end of each slot (2124, 2126), or may include information indicating the entire downlink or the entire uplink for each slot. At this time, a symbol / slot set as an uplink or downlink through the cell-specific setting information (2110) of the first step cannot be changed to a downlink or uplink through the terminal's unique upper layer signaling (2120).

[0578] Finally, in order to dynamically change the downlink signal transmission section and the uplink signal transmission section, the downlink control information of the downlink control channel may include a slot format indicator (2130) that indicates whether each symbol within each slot is a downlink symbol, an uplink symbol, or a flexible symbol among a plurality of slots starting from the slot where the terminal detected the downlink control information. At this time, for a symbol / slot set as uplink or downlink in the first and second steps, the slot format indicator cannot indicate that it is a downlink or an uplink. The slot format of each slot (2131, 2132) containing at least one symbol that was not set as uplink or downlink in the first and second steps may be indicated by the corresponding downlink control information.

[0579] Slot format indicators can indicate uplink-downlink configurations for 14 symbols within a single slot, as shown in Table 17-1 below. Slot format indicators can be transmitted simultaneously to multiple terminals via a terminal group (or cell) common control channel. In other words, downlink control information containing slot format indicators can be transmitted via a PDCCH that is CRC scrambled with an identifier different from the terminal's unique C-RNTI (cell-RNTI), for example, SFI-RNTI. Downlink control information may include slot format indicators for one or more slots, i.e., N slots. Here, the value of N may be an integer greater than 0, or a value set by the terminal from the base station via upper-layer signaling from a predefined set of possible values ​​such as 1, 2, 5, 10, 20, etc. The size of the slot format indicator may be set by the base station to the terminal via upper-layer signaling.

[0580] [Table 17-1]

[0581]

[0582] In [Table 17-1], D represents a downlink symbol, U represents an uplink symbol, and F represents a flexible symbol. According to [Table 17-1], the total number of slot formats that can be supported for a single slot is 256. The maximum size of information bits that can be used to indicate a slot format in an NR system is 128 bits, and the base station can set this to the terminal through upper layer signaling, for example, 'dci-PayloadSize'.

[0583] At this time, a cell operating in a licensed or unlicensed band may set and direct additional slot formats as shown in [Table 17-2] by introducing one or more additional slot formats or by modifying at least one of the existing slot formats. [Table 17-2] shows an example of additional slot formats in which a single slot consists only of uplink symbols and flexible symbols (F).

[0584] [Table 17-2]

[0585]

[0586] In one embodiment, the downlink control information used for slot format indication may indicate slot format(s) for a plurality of serving cells, and the slot format(s) for each serving cell may be distinguished by a serving cell ID. Additionally, for each serving cell, a slot format combination for one or more slots may be indicated by the downlink control information. For example, if the size of a slot format indicator index field within the downlink control information is 3 bits and indicates a slot format for a single serving cell, the 3-bit slot format indicator index field may indicate one of a total of 8 slot formats (or slot format combinations), and the base station may indicate the slot format indicator index field through the terminal group common downlink control information (common DCI).

[0587] In one embodiment, at least one slot format indicator index field included in the downlink control information may be composed of a slot format combination indicator for a plurality of slots. For example, [Table 17-3] shows a 3-bit slot format combination indicator composed of the slot formats of [Table 17-1] and [Table 17-2]. Among the values ​​of the slot format combination indicator, {0, 1, 2, 3, 4} indicate a slot format for one slot. The remaining three values ​​{5, 6, 7} indicate a slot format for four slots, and the terminal may sequentially apply the indicated slot formats to four slots starting from the slot where downlink control information including the slot format combination indicator was detected.

[0588] [Table 17-3]

[0589]

[0590] In one embodiment, if the terminal is not configured to monitor DCI format 2_0, if some symbols of a specific slot are configured as flexible symbols (F) according to the slot format configured through upper layer signaling, or if the slot format of a specific slot is not configured, the terminal may receive DCI, RAR UL grant, fallbackRAR UL grant, or successRAR for the corresponding symbols within the slot and transmit PUSCH, PUCCH, PRACH, or SRS indicated in the received information.

[0591] In one embodiment, if some symbols of a specific slot are set to flexible symbols (F) based on a slot format set through upper layer signaling, the terminal does not expect to receive uplink transmission settings to be transmitted from the corresponding symbols of the slot based on upper layer signaling, e.g., configured grant-based PUSCH, PUCCH, or SRS.

[0592] In one embodiment, if a terminal is scheduled to transmit PUSCH for multiple slots in DCI format 0_1, and at least one of the symbols at the location where PUSCH is to be transmitted in one of the multiple slots is set to DL through upper layer signaling, the terminal does not transmit PUSCH in that slot.

[0593] In one embodiment, if some symbols of a specific slot are set as flexible symbols (F) by upper layer signaling or no slot format is set for a specific slot, and the terminal receives DCI format 2_0 and the slot format indicator value is not 255 and indicates flexible symbols (F) for some symbols of the slot, and the terminal receives DCI format, RAR UL grant, successRAR indicating PUSCH, PUCCH, PRACH, or SRS within the flexible symbols, then the terminal can perform transmission for PUSCH, PUCCH, PRACH, or SRS within the flexible symbols within the slot.

[0594] In one embodiment, if some symbols of a specific slot are set to flexible symbols (F) by upper layer signaling or no slot format is set for a specific slot, and the terminal receives DCI format 2_0 and the slot format indicator value is not 255, and the terminal is set to transmit PUCCH, PUSCH, or PRACH through upper layer signaling for some symbols within the slot, the terminal may transmit the pre-set PUCCH, PUSCH, or PRACH only when the uplink symbol (UL) is indicated by DCI format 2_0 for the corresponding some symbols within the slot.

[0595] <Embodiment 3-2: Transmission Beam Mapping Method Considering Slot Format During Repeated PUSCH Transmission>

[0596] In one embodiment of the present disclosure, the 3-2 embodiment describes a transmission beam mapping method that considers a slot format for dynamic grant or configured grant-based PUSCH repetitive transmission considering multiple TRPs. At this time, as in the 1-1 and 1-2 embodiments, dynamic grant-based PUSCH repetitive transmission considering multiple TRPs means a case where PUSCH repetitive transmission considering multiple TRPs is indicated based on DCI, and as in the 1-3 embodiment, configured grant-based PUSCH repetitive transmission considering multiple TRPs means that PUSCH repetitive transmission considering multiple TRPs based on upper layer settings can be configured or enabled / disabled.

[0597] As described above, the terminal can be configured with uplink symbols (UL), downlink symbols (DL), or flexible symbols (F) for a specific slot or some symbols within slots via upper layer signaling regarding slot format information. Additionally, as described above, if the terminal has not been configured with monitoring for DCI format 2_0, the terminal can follow the slot format configured via upper layer signaling. In this case, since the terminal can know about the semi-static slot format based on upper layer signaling without additional information dynamically indicated, it can know in advance which symbols in which slots PUSCH transmission will be impossible for dynamic grant or configured grant-based PUSCH repeat transmissions. Therefore, if the terminal has not been configured with monitoring for DCI format 2_0, the terminal can apply transmission beam mapping to the actual transmitted PUSCH transmission for dynamic grant or configured grant-based PUSCH repeat transmissions considering multiple TRPs. Alternatively, even if information regarding the quasi-static slot format is known, transmission beam mapping can be applied to the PUSCH transmission location, taking into account both the actual transmitted PUSCH and the cancelled PUSCH transmissions. As mentioned above, PUSCH repeated transmission considering multiple TRPs based on a dynamic grant enables the actual transmission of PUSCH at the flexible symbol (F) or the uplink symbol (UL), and PUSCH repeated transmission considering multiple TRPs based on a configured grant enables the actual transmission of PUSCH at the uplink symbol (UL). Further details are explained below with reference to Fig. 22.

[0598] Additionally, as described above, if the terminal is configured to monitor DCI format 2_0, the terminal may receive slot format indicators within DCI format 2_0 and be indicated as uplink symbols (UL), downlink symbols (DL), or flexible symbols (F) for specific slots or some symbols within slots. In this case, due to slot format information dynamically indicated via DCI format 2_0 in addition to semi-statically configured information, it is difficult for the terminal to know in advance which symbols in which slots will be unable to transmit PUSCH for dynamic grant or configured grant-based PUSCH repeat transmissions. Therefore, if the terminal is configured to monitor DCI format 2_0, the terminal may apply transmission beam mapping to PUSCH transmission locations that consider both actual transmitted PUSCH and cancelled PUSCH transmissions for dynamic grant or configured grant-based PUSCH repeat transmissions. Alternatively, transmission beam mapping may be performed only for actual transmitted PUSCH transmissions, taking into account dynamic slot formats as well. As mentioned above, PUSCH repeated transmission considering dynamic grant-based multiple TRPs enables actual transmission of PUSCH at flexible symbols (F) or uplink symbols (UL), and PUSCH repeated transmission considering configured grant-based multiple TRPs enables actual transmission of PUSCH at uplink symbols (UL). Further details will be explained with reference to Fig. 22.

[0599] FIG. 22 illustrates various transmission beam mapping methods according to a slot format for dynamic grant-based PUSCH repeat transmission according to an embodiment of the present disclosure. The slot format (22-001) of FIG. 22 may be a slot format set by upper layer signaling, or a slot format that additionally considers instructions through DCI format 2_0 in addition to the setting through upper layer signaling. If a terminal is set to PUSCH repetition type B as an upper layer signaling method for PUSCH repeat transmission, the number of repeat transmissions is 10, and the number of transmission symbols per nominal repetition is 10, then the nominal repetition may be expressed as 22-002. At this time, considering downlink (DL) symbols (22-008), flexible (F) symbols (22-009), and uplink (UL) symbols (22-010), the actual repetition actually transmitted among the nominal repetitions may be expressed as 22-003. At this time, two transmission beam mapping types can be determined by considering the slot format. Transmission beam mapping type 1 (22-004, 22-006) means performing transmission beam mapping for PUSCH transmission locations that consider both actual transmitted PUSCH and canceled PUSCH transmissions, and transmission beam mapping type 2 (22-005, 22-007) means performing transmission beam mapping only for actual transmitted PUSCH transmissions. Figures 22-004 to 22-007 of FIG. 22 illustrate how transmission beam mapping is performed according to each transmission beam mapping type and transmission beam mapping method (e.g., sequential and cyclical). Here, the transmission beam mapping unit is actual repetition.

[0600] FIG. 23a is a diagram illustrating the operation of a terminal regarding transmission beam mapping considering a slot format according to an embodiment of the present disclosure. The terminal reports to the base station its capability to support dynamic grant or configured grant-based PUSCH repetitive transmission considering a single or multiple DCI-based multiple TRP as described above (2301). Subsequently, the terminal receives configuration information related to dynamic grant or configured grant-based PUSCH repetitive transmission considering a single or multiple DCI-based multiple TRP through upper layer signaling (2302). Additionally, the terminal receives information related to slot format configuration through upper layer signaling (2303). Depending on whether the terminal has DCI format 2_0 monitoring configured (2304), if the terminal has DCI format 2_0 monitoring configured and has been instructed to repetitive transmission for a PUSCH scheduled with DCI (2305), the terminal can perform a first-1 beam mapping-based transmission operation (2306). Here, the 1-1 beam mapping-based transmission operation can be determined through a combination of the above-mentioned transmission beam mapping type 1 or 2, the transmission beam mapping method cyclic or sequential, the transmission beam mapping unit, etc., and since it is a PUSCH scheduled by DCI as described above, PUSCH transmission can be performed on flexible symbols (F) and uplink (UL) symbols. If the terminal is configured or instructed to perform a configured grant-based PUSCH transmission (2305), the terminal can perform the 2-1 beam mapping-based transmission operation (2307). Here, the 2-1 beam mapping-based transmission operation can be the above-mentioned transmission beam mapping type 1 or 2, and since it is a configured grant-based PUSCH as described above, PUSCH transmission can be performed only on uplink (UL) symbols.Additionally, depending on whether the terminal has DCI format 2_0 monitoring configured (2304), if the terminal has not been configured with DCI format 2_0 monitoring and has been instructed to repeat transmission for a DCI-scheduled PUSCH (2308), the terminal can perform a first-second beam mapping-based transmission operation (2309). Here, the first-second beam mapping-based transmission operation can be determined through a combination of the above-mentioned transmission beam mapping type 1 or 2, a transmission beam mapping method such as cyclical or sequential, and a transmission beam mapping unit, and as such, since it is a DCI-scheduled PUSCH, PUSCH transmission can be performed on flexible symbols (F) and uplink (UL) symbols. If the terminal has been configured or instructed to perform a configured grant-based PUSCH transmission (2308), the terminal can perform a second-second beam mapping-based transmission operation (2310). Here, the 2-2 beam mapping-based transmission operation can be determined through a combination of the above-mentioned transmission beam mapping type 1 or 2, the transmission beam mapping method cyclic or sequential, the transmission beam mapping unit, etc., and since it is a grant-based PUSCH configured as above, PUSCH transmission can be performed only on uplink (UL) symbols.

[0601] FIG. 23b is a diagram illustrating the operation of a base station for transmission beam mapping considering a slot format according to an embodiment of the present disclosure. The base station may receive a report from the terminal regarding the terminal's capability to support dynamic grant or configured grant-based PUSCH repetitive transmission considering a single or multiple DCI-based multiple TRP as described above (2351). Subsequently, the base station may transmit configuration information related to dynamic grant or configured grant-based PUSCH repetitive transmission considering a single or multiple DCI-based multiple TRP through upper layer signaling (2352). Additionally, the base station may transmit information related to slot format configuration through upper layer signaling (2353). Depending on whether the terminal has configured DCI format 2_0 monitoring (2354), if the terminal has configured DCI format 2_0 monitoring and has instructed repetitive transmission for a PUSCH scheduled with DCI (2355), the base station may perform a first-1 beam mapping-based reception operation (2356). Here, the 1-1 beam mapping-based receiving operation can be determined through a combination of the above-mentioned transmission beam mapping type 1 or 2, the transmission beam mapping method cyclic or sequential, the transmission beam mapping unit, etc., and can perform the operation of receiving a PUSCH transmitted in a flexible symbol (F) and uplink (UL) symbol, as a PUSCH scheduled in DCI as described above. If the terminal has set or instructed a configured grant-based PUSCH transmission (2355), the base station can perform the 2-1 beam mapping-based receiving operation (2357).Here, the 2-1 beam mapping-based reception operation can be the transmission beam mapping type 1 or 2 described above, and since it is a PUSCH based on a configured grant as described above, it can perform the operation of receiving a PUSCH transmitted only in uplink (UL) symbols. Additionally, depending on whether DCI format 2_0 monitoring is configured in the terminal (2354), if DCI format 2_0 monitoring is not configured in the terminal and repeated transmission is instructed for a PUSCH scheduled via DCI (2358), the base station can perform the 1-2 beam mapping-based reception operation (2359). Here, the 1-2 beam mapping-based reception operation can be determined through a combination of the transmission beam mapping type 1 or 2 described above, a transmission beam mapping method such as cyclic or sequential, and a transmission beam mapping unit, and since it is a PUSCH scheduled via DCI as described above, it can perform the operation of receiving a PUSCH transmitted in flexible symbols (F) and uplink (UL) symbols. If the terminal is configured or instructed to transmit a configured grant-based PUSCH (2358), the base station may perform a second-2 beam mapping-based reception operation (2360). Here, the second-2 beam mapping-based reception operation may be determined by a combination of the transmission beam mapping type 1 or 2, the transmission beam mapping method cyclic or sequential, the transmission beam mapping unit, etc., and since it is a configured grant-based PUSCH as described above, it may perform an operation to receive a PUSCH transmitted only in uplink (UL) symbols.

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

[0603] Referring to FIG. 24, the terminal may include a transceiver (referring to a terminal receiver (24-00) and a terminal transmitter (24-10)), a memory (not shown), and a terminal processing unit (24-05, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver (24-00, 24-10), memory, and terminal processing unit (24-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.

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

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

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

[0607] In addition, 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.

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

[0609] Referring to FIG. 25, the base station may include a transceiver unit, a memory (not shown), and a base station processing unit (25-05, or a base station control unit or processor), which refer to a base station receiver (25-00) and a base station transmitter (25-10). Depending on the communication method of the base station described above, the transceiver unit (25-00, 25-10), the memory, and the base station processing unit (25-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.

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

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

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

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

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

[0615] 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 embodiments described in the claims or specification of this disclosure.

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

[0617] 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 the device performing the embodiment of the present disclosure through an external port. Additionally, a separate storage device on the communication network may be connected to the device performing the embodiment of the present disclosure.

[0618] In the specific embodiments of the present disclosure described above, the components included in the invention 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, or even if a component is expressed in the singular form, it may be composed of a plural form.

[0619] Meanwhile, the embodiments of the present disclosure disclosed in this specification and 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, parts of one embodiment of the present disclosure and parts of another embodiment may be combined to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure may be combined to operate a base station and a terminal. In addition, although the above embodiments are presented based on an FDD LTE system, other variations based on the technical concept of the above embodiments may be implemented in other systems such as a TDD LTE system, 5G, or NR system.

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

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

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

[0623] 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

Claim 1 A method performed by a terminal in a communication system comprises the steps of: receiving a PUSCH (physical uplink shared channel) setting and an SRS (sounding reference signal) setting through upper layer signaling, wherein the PUSCH setting includes information regarding a PUSCH repetition, the SRS setting includes information regarding a first SRS resource set and information regarding a second SRS resource set, and wherein the first SRS resource set and the second SRS resource set each include one or more SRS resources; receiving a DCI (downlink control information) format, wherein the DCI format includes an SRS resource set indicator field, a first SRS resource indicator field and a second SRS resource indicator field, wherein the SRS resource set indicator field is 2 bits, and the code point of the SRS resource set indicator field is mapped to the association of the first SRS resource set and the second SRS resource set with the PUSCH repetition; A method comprising the step of transmitting the PUSCH repetition by applying one or more of the first SRS resource indicator field or the second SRS resource indicator field according to one or more of the first SRS resource set or the second SRS resource set identified as associated with the PUSCH repetition based on the SRS resource set indicator field. Claim 2 A method according to claim 1, wherein if the SRS resource set indicator field indicates a first code point, the first SRS resource set is mapped to the PUSCH iteration; if the SRS resource set indicator field indicates a second code point, the second SRS resource set is mapped to the PUSCH iteration; if the SRS resource set indicator field indicates a third code point, the first SRS resource set and the second SRS resource set are associated with the PUSCH iteration according to a mapping pattern for the PUSCH iteration; and if the SRS resource set indicator field indicates a fourth code point, the second SRS resource set and the first SRS resource set are associated with the PUSCH iteration according to a mapping pattern for the PUSCH iteration. Claim 3 In claim 2, where the mapping pattern is set to cyclic mapping and the SRS resource set indicator field indicates the third code point, the first SRS resource set is applied to the first PUSCH of the PUSCH iteration and the second SRS resource set is applied to the second PUSCH of the PUSCH iteration; where the mapping pattern is set to sequential mapping and the SRS resource set indicator field indicates the third code point, the first SRS resource set is applied to the first and second PUSCH of the PUSCH iteration and the second SRS resource set is applied to the third and fourth PUSCH of the PUSCH iteration; where the mapping pattern is set to cyclic mapping and the SRS resource set indicator field indicates the fourth code point, the first SRS resource set is applied to the second PUSCH of the PUSCH iteration and the second SRS resource set is applied to the first PUSCH of the PUSCH iteration, and the mapping A method in which, when the pattern is set to the above sequential mapping and the SRS resource set indicator field indicates the fourth code point, the first SRS resource set is applied to the third and fourth PUSCH of the PUSCH iteration and the second SRS resource set is applied to the first and second PUSCH of the one or more PUSCH iterations. Claim 4 A method according to claim 2, wherein when the SRS resource set indicator field indicates the first code point, the first SRS resource indicator field is associated with the first SRS resource set; when the SRS resource set indicator field indicates the second code point, the first SRS resource indicator field is associated with the second SRS resource set; when the SRS resource set indicator field indicates the third code point, the first SRS resource indicator field is associated with the first SRS resource set; and when the SRS resource set indicator field indicates the fourth code point, the first SRS resource indicator field is associated with the first SRS resource set; and when the SRS resource set indicator field indicates the fourth code point, the first SRS resource indicator field is associated with the first SRS resource set; and the second SRS resource indicator field is associated with the second SRS resource set. Claim 5 In claim 2, information for setting one of non-codebook-based transmission or codebook-based transmission for the PUSCH repetition is received through the upper layer signaling, and when the codebook-based transmission is set for the PUSCH repetition, the DCI format includes a first precoding information field and a second precoding information field, the number of bits in the second precoding information field depends on the number of TPMI (transmission precoding matrix indicators) per layer associated with the first precoding information field, and when the SRS resource set indicator field indicates the first code point, the first SRS resource indicator field and the first precoding information field are associated with the first SRS resource set, and when the SRS resource set indicator field indicates the second code point, the first SRS resource indicator field and the first precoding information field are associated with the second SRS resource set, and when the SRS resource set indicator field indicates the third code point A method wherein, in the case where the first SRS resource indicator field and the first precoding information field are related to the first SRS resource set and the second SRS resource indicator field and the second precoding information field are related to the second SRS resource set, and where the SRS resource set indicator field indicates the fourth code point, the first SRS resource indicator field and the first precoding information field are related to the first SRS resource set and the second SRS resource indicator field and the second precoding information field are related to the second SRS resource set. Claim 6 A method performed by a base station in a communication system comprises the steps of: transmitting a PUSCH (physical uplink shared channel) setting and an SRS (sounding reference signal) setting through upper layer signaling, wherein the PUSCH setting includes information for a PUSCH repetition, the SRS setting includes information for a first SRS resource set and information for a second SRS resource set, and the first SRS resource set and the second SRS resource set each include one or more SRS resources; transmitting a DCI (downlink control information) format, wherein the DCI format includes an SRS resource set indicator field, a first SRS resource indicator field and a second SRS resource indicator field, wherein the SRS resource set indicator field is 2 bits, and the code point of the SRS resource set indicator field is mapped to the association of the first SRS resource set and the second SRS resource set to the PUSCH repetition; A method comprising the step of receiving the PUSCH iteration, wherein the PUSCH iteration is associated with one or more of the first SRS resource indicator field or the second SRS resource indicator field according to one or more of the first SRS resource set or the second SRS resource set indicated as associated with the PUSCH iteration based on the SRS resource set indicator field. Claim 7 A method according to claim 6, wherein if the SRS resource set indicator field indicates a first code point, the first SRS resource set is mapped to the PUSCH iteration; if the SRS resource set indicator field indicates a second code point, the second SRS resource set is mapped to the PUSCH iteration; if the SRS resource set indicator field indicates a third code point, the first SRS resource set and the second SRS resource set are associated with the PUSCH iteration according to a mapping pattern for the PUSCH iteration; and if the SRS resource set indicator field indicates a fourth code point, the second SRS resource set and the first SRS resource set are associated with the PUSCH iteration according to a mapping pattern for the PUSCH iteration. Claim 8 In claim 7, where the mapping pattern is set to cyclic mapping and the SRS resource set indicator field indicates the third code point, the first SRS resource set is associated with the first PUSCH of the PUSCH iteration and the second SRS resource set is associated with the second PUSCH of the PUSCH iteration; where the mapping pattern is set to sequential mapping and the SRS resource set indicator field indicates the third code point, the first SRS resource set is associated with the first and second PUSCH of the PUSCH iteration and the second SRS resource set is associated with the third and fourth PUSCH of the PUSCH iteration; where the mapping pattern is set to cyclic mapping and the SRS resource set indicator field indicates the fourth code point, the first SRS resource set is associated with the second PUSCH of the PUSCH iteration and the second SRS resource set is associated with the first PUSCH of the PUSCH iteration, and the mapping A method in which, when the pattern is set to the above sequential mapping and the SRS resource set indicator field indicates the fourth code point, the first SRS resource set is related to the third and fourth PUSCH of the PUSCH iteration and the second SRS resource set is related to the first and second PUSCH of the one or more PUSCH iterations. Claim 9 A method according to claim 7, wherein when the SRS resource set indicator field indicates the first code point, the first SRS resource indicator field is associated with the first SRS resource set; when the SRS resource set indicator field indicates the second code point, the first SRS resource indicator field is associated with the second SRS resource set; when the SRS resource set indicator field indicates the third code point, the first SRS resource indicator field is associated with the first SRS resource set; and when the SRS resource set indicator field indicates the fourth code point, the first SRS resource indicator field is associated with the first SRS resource set; and when the SRS resource set indicator field indicates the fourth code point, the first SRS resource indicator field is associated with the first SRS resource set; and the second SRS resource indicator field is associated with the second SRS resource set. Claim 10 In claim 7, information for setting one of non-codebook-based transmission or codebook-based transmission for the PUSCH repetition is transmitted through the upper layer signaling, and when the codebook-based transmission is set for the PUSCH repetition, the DCI format includes a first precoding information field and a second precoding information field, and the number of bits of the second precoding information field depends on the number of TPMI (transmission precoding matrix indicators) per layer associated with the first precoding information field, and when the SRS resource set indicator field indicates the first code point, the first SRS resource indicator field and the first precoding information field are associated with the first SRS resource set, and when the SRS resource set indicator field indicates the second code point, the first SRS resource indicator field and the first precoding information field are associated with the second SRS resource set, and when the SRS resource set indicator field indicates the third code point A method wherein, in the case where the first SRS resource indicator field and the first precoding information field are related to the first SRS resource set and the second SRS resource indicator field and the second precoding information field are related to the second SRS resource set, and where the SRS resource set indicator field indicates the fourth code point, the first SRS resource indicator field and the first precoding information field are related to the first SRS resource set and the second SRS resource indicator field and the second precoding information field are related to the second SRS resource set. Claim 11 A terminal of a communication system comprises: a transceiver; and a processor connected to the transceiver, wherein the processor receives, through upper layer signaling, a PUSCH (physical uplink shared channel) setting and an SRS (sounding reference signal) setting, wherein the PUSCH setting includes information for a PUSCH repetition, the SRS setting includes information for a first SRS resource set and information for a second SRS resource set, and wherein the first SRS resource set and the second SRS resource set each include one or more SRS resources; receives a DCI (downlink control information) format, wherein the DCI format includes an SRS resource set indicator field, a first SRS resource indicator field and a second SRS resource indicator field, wherein the SRS resource set indicator field is 2 bits, and the code point of the SRS resource set indicator field is mapped to the association of the first SRS resource set and the second SRS resource set to the PUSCH repetition; A terminal configured to transmit the PUSCH repetition by applying one or more of the first SRS resource indicator field or the second SRS resource indicator field according to one or more of the first SRS resource set or the second SRS resource set identified as associated with the PUSCH repetition based on the SRS resource set indicator field. Claim 12 A terminal according to claim 11, wherein if the SRS resource set indicator field indicates a first code point, the first SRS resource set is mapped to the PUSCH iteration; if the SRS resource set indicator field indicates a second code point, the second SRS resource set is mapped to the PUSCH iteration; if the SRS resource set indicator field indicates a third code point, the first SRS resource set and the second SRS resource set are associated with the PUSCH iteration according to a mapping pattern for the PUSCH iteration; and if the SRS resource set indicator field indicates a fourth code point, the second SRS resource set and the first SRS resource set are associated with the PUSCH iteration according to a mapping pattern for the PUSCH iteration. Claim 13 In claim 12, where the mapping pattern is set to cyclic mapping and the SRS resource set indicator field indicates the third code point, the first SRS resource set is applied to the first PUSCH of the PUSCH iteration and the second SRS resource set is applied to the second PUSCH of the PUSCH iteration; where the mapping pattern is set to sequential mapping and the SRS resource set indicator field indicates the third code point, the first SRS resource set is applied to the first and second PUSCH of the PUSCH iteration and the second SRS resource set is applied to the third and fourth PUSCH of the PUSCH iteration; where the mapping pattern is set to cyclic mapping and the SRS resource set indicator field indicates the fourth code point, the first SRS resource set is applied to the second PUSCH of the PUSCH iteration and the second SRS resource set is applied to the first PUSCH of the PUSCH iteration, and the A terminal in which, when the mapping pattern is set to the sequential mapping and the SRS resource set indicator field indicates the fourth code point, the first SRS resource set is applied to the third and fourth PUSCH of the PUSCH iteration and the second SRS resource set is applied to the first and second PUSCH of the one or more PUSCH iterations. Claim 14 A terminal according to claim 12, wherein when the SRS resource set indicator field indicates the first code point, the first SRS resource indicator field is associated with the first SRS resource set; when the SRS resource set indicator field indicates the second code point, the first SRS resource indicator field is associated with the second SRS resource set; when the SRS resource set indicator field indicates the third code point, the first SRS resource indicator field is associated with the first SRS resource set and the second SRS resource indicator field is associated with the second SRS resource set; and when the SRS resource set indicator field indicates the fourth code point, the first SRS resource indicator field is associated with the first SRS resource set and the second SRS resource indicator field is associated with the second SRS resource set. Claim 15 In claim 12, information for setting one of non-codebook-based transmission or codebook-based transmission for the PUSCH repetition is received through the upper layer signaling, and when the codebook-based transmission is set for the PUSCH repetition, the DCI format includes a first precoding information field and a second precoding information field, the number of bits in the second precoding information field depends on the number of TPMI (transmission precoding matrix indicators) per layer associated with the first precoding information field, and when the SRS resource set indicator field indicates the first code point, the first SRS resource indicator field and the first precoding information field are associated with the first SRS resource set, and when the SRS resource set indicator field indicates the second code point, the first SRS resource indicator field and the first precoding information field are associated with the second SRS resource set, and when the SRS resource set indicator field indicates the third code point A terminal, wherein the first SRS resource indicator field and the first precoding information field are related to the first SRS resource set and the second SRS resource indicator field and the second precoding information field are related to the second SRS resource set, and when the SRS resource set indicator field indicates the fourth code point, the first SRS resource indicator field and the first precoding information field are related to the first SRS resource set and the second SRS resource indicator field and the second precoding information field are related to the second SRS resource set. Claim 16 A base station of a communication system comprises: a transceiver; and a processor connected to the transceiver, wherein the processor transmits, through upper layer signaling, a PUSCH (physical uplink shared channel) setting and an SRS (sounding reference signal) setting, wherein the PUSCH setting includes information for a PUSCH repetition, the SRS setting includes information for a first SRS resource set and information for a second SRS resource set, and wherein the first SRS resource set and the second SRS resource set each include one or more SRS resources; transmits a DCI (downlink control information) format, wherein the DCI format includes an SRS resource set indicator field, a first SRS resource indicator field and a second SRS resource indicator field, wherein the SRS resource set indicator field is 2 bits and the code point of the SRS resource set indicator field is mapped to the association of the first SRS resource set and the second SRS resource set to the PUSCH repetition; A base station configured to receive the PUSCH repetition, wherein the PUSCH repetition is associated with one or more of the first SRS resource indicator field or the second SRS resource indicator field according to one or more of the first SRS resource set or the second SRS resource set indicated as associated with the PUSCH repetition based on the SRS resource set indicator. Claim 17 A base station according to claim 16, wherein if the SRS resource set indicator field indicates a first code point, the first SRS resource set is mapped to the PUSCH iteration; if the SRS resource set indicator field indicates a second code point, the second SRS resource set is mapped to the PUSCH iteration; if the SRS resource set indicator field indicates a third code point, the first SRS resource set and the second SRS resource set are associated with the PUSCH iteration according to a mapping pattern for the PUSCH iteration; and if the SRS resource set indicator field indicates a fourth code point, the second SRS resource set and the first SRS resource set are associated with the PUSCH iteration according to a mapping pattern for the PUSCH iteration. Claim 18 In claim 17, where the mapping pattern is set to cyclic mapping and the SRS resource set indicator field indicates the third code point, the first SRS resource set is associated with the first PUSCH of the PUSCH iteration and the second SRS resource set is associated with the second PUSCH of the PUSCH iteration; where the mapping pattern is set to sequential mapping and the SRS resource set indicator field indicates the third code point, the first SRS resource set is associated with the first and second PUSCH of the PUSCH iteration and the second SRS resource set is associated with the third and fourth PUSCH of the PUSCH iteration; where the mapping pattern is set to cyclic mapping and the SRS resource set indicator field indicates the fourth code point, the first SRS resource set is associated with the second PUSCH of the PUSCH iteration and the second SRS resource set is associated with the first PUSCH of the PUSCH iteration, and the A base station, wherein the mapping pattern is set to the sequential mapping and the SRS resource set indicator field indicates the fourth code point, the first SRS resource set is related to the third and fourth PUSCH of the PUSCH iteration and the second SRS resource set is related to the first and second PUSCH of the one or more PUSCH iterations. Claim 19 A base station according to claim 17, wherein when the SRS resource set indicator field indicates the first code point, the first SRS resource indicator field is associated with the first SRS resource set; when the SRS resource set indicator field indicates the second code point, the first SRS resource indicator field is associated with the second SRS resource set; when the SRS resource set indicator field indicates the third code point, the first SRS resource indicator field is associated with the first SRS resource set and the second SRS resource indicator field is associated with the second SRS resource set; and when the SRS resource set indicator field indicates the fourth code point, the first SRS resource indicator field is associated with the first SRS resource set and the second SRS resource indicator field is associated with the second SRS resource set. Claim 20 In claim 17, information for setting one of non-codebook-based transmission or codebook-based transmission for the PUSCH repetition is transmitted through the upper layer signaling, and when the codebook-based transmission is set for the PUSCH repetition, the DCI format includes a first precoding information field and a second precoding information field, the number of bits of the second precoding information field depends on the number of TPMI (transmission precoding matrix indicators) per layer associated with the first precoding information field, and when the SRS resource set indicator field indicates the first code point, the first SRS resource indicator field and the first precoding information field are associated with the first SRS resource set, and when the SRS resource set indicator field indicates the second code point, the first SRS resource indicator field and the first precoding information field are associated with the second SRS resource set, and when the SRS resource set indicator field indicates the third code point A base station, wherein the first SRS resource indicator field and the first precoding information field are related to the first SRS resource set and the second SRS resource indicator field and the second precoding information field are related to the second SRS resource set, and when the SRS resource set indicator field indicates the fourth code point, the first SRS resource indicator field and the first precoding information field are related to the first SRS resource set and the second SRS resource indicator field and the second precoding information field are related to the second SRS resource set.

Images