Uplink transmission and reception method and apparatus in a wireless communication system

Abstract

Disclosed are an uplink transmission and reception method and apparatus in a wireless communication system. According to one embodiment of the disclosure, a method of a terminal performing uplink transmission in a wireless communication system can include receiving configuration information related to a plurality of sounding reference signal (SRS) resource sets, receiving downlink control information (DCI) indicating at least one of a first SRS resource set, a second SRS resource set, or the first SRS resource set and the second SRS resource set and including information indicating at least one SRS resource in the indicated at least one SRS resource set, and performing uplink transmission based on the indicated at least one SRS resource.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to uplink transmission and reception methods and apparatus in wireless communication systems. Background Technology

[0002] A mobile communication system has been developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded to include data and voice services, and the current explosive growth in services has led to resource shortages. Users are demanding faster services and therefore require more advanced mobile communication systems.

[0003] The overall requirements for next-generation mobile communication systems should be able to support the capacity for explosive data traffic, significantly increased per-user transmission rates, a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To this end, various technologies such as dual connectivity, massive MIMO, in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and device networking have been investigated. Summary of the Invention

[0004] Technical issues

[0005] The technical objective of this disclosure is to provide an uplink transmission / reception method and apparatus in a wireless communication system.

[0006] The additional technical objective of this disclosure is to provide an uplink transmission / reception method and apparatus in a wireless communication system based on at least one of a plurality of probe reference signal resource sets.

[0007] The technical objectives to be achieved by this disclosure are not limited to those described above, and other technical objectives not described herein will be clearly understood by those skilled in the art through the following description.

[0008] Technical solution

[0009] A method for a UE to perform uplink transmission in a wireless communication system according to one aspect of the present disclosure may include the following steps: receiving configuration information associated with a plurality of sounding reference signal (SRS) resource sets; receiving downlink control information (DCI), the DCI including information indicating at least one of a first SRS resource set, a second SRS resource set, or the first SRS resource set and the second SRS resource set and indicating at least one SRS resource in the indicated at least one SRS resource set; and performing the uplink transmission based on the indicated at least one SRS resource.

[0010] A method for a base station to perform uplink reception in a wireless communication system according to an additional aspect of this disclosure may include the following steps: transmitting configuration information associated with a plurality of sounding reference signal (SRS) resource sets; transmitting downlink control information (DCI), the DCI including information indicating at least one of a first SRS resource set, a second SRS resource set, or the first SRS resource set and the second SRS resource set, and indicating at least one SRS resource in the indicated at least one SRS resource set; and performing uplink reception for transmission based on the indicated at least one SRS resource.

[0011] Technical effect

[0012] According to embodiments of this disclosure, an uplink transmitting / receiving method and apparatus can be provided in a wireless communication system.

[0013] According to embodiments of this disclosure, an uplink transmission / reception method and apparatus based on at least one of a plurality of probe reference signal resource sets can be provided in a wireless communication system.

[0014] The effects achievable by this disclosure are not limited to those described above, and those skilled in the art can clearly understand other effects not described herein through the following description. Attached Figure Description

[0015] The accompanying drawings, which are included as part of the detailed description for understanding this disclosure, provide embodiments of the disclosure and describe the technical features of the disclosure through detailed description.

[0016] Figure 1 The structure of a wireless communication system to which this disclosure can be applied is illustrated.

[0017] Figure 2 A frame structure in a wireless communication system to which this disclosure can be applied is illustrated.

[0018] Figure 3 An example is shown of a resource grid in a wireless communication system to which this disclosure can be applied.

[0019] Figure 4 Examples of physical resource blocks in wireless communication systems to which this disclosure can be applied are provided.

[0020] Figure 5 The time slot structure in a wireless communication system to which this disclosure can be applied is illustrated.

[0021] Figure 6 Examples are given of physical channels used in wireless communication systems to which this disclosure may be applied, as well as general signal transmission and reception methods using such physical channels.

[0022] Figure 7 A method for transmitting multiple TRPs in a wireless communication system to which this disclosure can be applied is illustrated.

[0023] Figure 8 This is a diagram illustrating an uplink transmission method for a terminal according to an embodiment of the present disclosure.

[0024] Figure 9 This is a diagram illustrating an uplink receiving method for a base station according to an embodiment of the present disclosure.

[0025] Figure 10 It is a diagram used to describe the signaling process of the network side and the terminal according to this disclosure.

[0026] Figure 11 A block diagram illustrating a wireless communication system according to an embodiment of the present disclosure is shown. Detailed Implementation

[0027] In the following, embodiments according to this disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed with reference to the drawings is intended to describe exemplary embodiments of this disclosure and not to represent the only embodiments in which this disclosure can be implemented. The following detailed description includes specific details to provide a complete understanding of this disclosure. However, those skilled in the art will recognize that this disclosure can be implemented without these specific details.

[0028] In some cases, known structures and devices may be omitted, or they may be shown in block diagram form based on the core functions of each structure and device in order to prevent ambiguity of the concepts in this disclosure.

[0029] In this disclosure, when an element is referred to as “connected,” “combined,” or “linked” to another element, it can include both indirect and direct connections between the two elements. Furthermore, in this disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, operations, components, and / or elements, but do not exclude the presence or addition of one or more other features, stages, operations, components, elements, and / or groups thereof.

[0030] In this disclosure, terms such as "first" and "second" are used only to distinguish one element from another and are not used to limit the elements. Unless otherwise stated, they do not limit the order or importance of the elements. Therefore, within the scope of this disclosure, a first element in one embodiment may be referred to as a second element in another embodiment, and similarly, a second element in one embodiment may be referred to as a first element in another embodiment.

[0031] The terminology used in this disclosure is for the purpose of describing particular embodiments and not for limiting the claims. As used in the description of embodiments and the appended claims, the singular form is intended to include the plural form unless the context clearly indicates otherwise. The term “and / or” as used in this disclosure may refer to one of the associated enumerations, or is intended to refer to and include any and all possible combinations of two or more of them. Furthermore, unless otherwise stated, the “ / ” between words in this invention has the same meaning as “and / or”.

[0032] This disclosure describes a wireless communication network or wireless communication system, and operations performed in the wireless communication network can be performed during the process of controlling the network and transmitting or receiving signals by a device (e.g., a base station) that controls the corresponding wireless communication network, or during the process of transmitting or receiving signals between a terminal associated with the corresponding wireless network and the network or between the terminal.

[0033] In this disclosure, the term "transmit or receive channel" includes the meaning of transmitting or receiving information or signals through a corresponding channel. For example, transmitting a control channel means transmitting control information or control signals through a control channel. Similarly, transmitting a data channel means transmitting data information or data signals through a data channel.

[0034] In the following text, downlink (DL) refers to communication from a base station to a terminal, while uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter can be part of the base station, and the receiver can be part of the terminal. In the uplink, the transmitter can be part of the terminal, and the receiver can be part of the base station. A base station can be referred to as a first communication device, and a terminal can be referred to as a second communication device. A base station (BS) can be replaced by terms such as fixed station, Node B, eNB (evolved Node B), gNB (next-generation Node B), BTS (Base Transceiver System), Access Point (AP), Network (5G network), AI (Artificial Intelligence) system / module, RSU (Roadside Unit), robot, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, terminals can be fixed or mobile, and can be replaced by terms such as UE (User Equipment), MS (Mobile Station), UT (User Terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless Terminal), MTC (Machine-Type Communication) equipment, M2M (Machine-to-Machine) equipment, D2D (Device-to-Device) equipment, vehicles, RSU (Roadside Unit), robots, AI (Artificial Intelligence) modules, drones (UAVs), AR (Augmented Reality) equipment, and VR (Virtual Reality) equipment.

[0035] The following descriptions can be applied to various radio access systems, such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented using technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented using radio technologies such as GSM (Global System for Mobile Communications) / GPRS (General Packet Radio Service) / EDGE (GSM Evolution with Enhanced Data Rates). OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) using E-UTRA, and LTE-A (Advanced) / LTE-A pro are advanced versions of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE / LTE-A / LTE-A pro.

[0036] To make the description clearer, it is based on 3GPP communication systems (e.g., LTE-A, NR), but the technical ideas of this disclosure are not limited thereto. LTE refers to technology from 3GPP TS (Technical Specification) version 8 onwards. Specifically, LTE technology in or after 3GPP TS 36.xxx is referred to as LTE-A, and LTE technology in or after 3GPP TS 36.xxx is referred to as LTE-A pro. 3GPP NR refers to technology in or after TS 38.xxx. LTE / NR can be referred to as a 3GPP system. "xxx" refers to the detailed number of the standard document. LTE / NR is generally referred to as a 3GPP system. For background information, terminology, abbreviations, etc., used to describe this disclosure, reference can be made to the matters described in the standard documents previously published. For example, the following documents can be consulted.

[0037] For 3GPP LTE, you can refer to TS 36.211 (Physical Channels and Modulation), TS 36.212 (Multiplexing and Channel Coding), TS 36.213 (Physical Layer Procedures), TS 36.300 (General Description), and TS 36.331 (Radio Resource Control).

[0038] For 3GPP NR, you can refer to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Coding), TS 38.213 (Physical Layer Procedures for Control), TS 38.214 (Physical Layer Procedures for Data), TS 38.300 (General Description of NR and NG-RAN (Next Generation Radio Access Network)), and TS 38.331 (Radio Resource Control Protocol Specification).

[0039] The abbreviations of terms that may be used in this disclosure are defined as follows.

[0040] -BM: Beam Management

[0041] -CQI: Channel Quality Indicator

[0042] -CRI: Channel State Information - Reference Signal Resource Indicator

[0043] -CSI: Channel State Information

[0044] -CSI-IM: Channel State Information - Interference Measurement

[0045] -CSI-RS: Channel State Information - Reference Signal

[0046] -DMRS: Demodulation Reference Signal

[0047] -FDM: Frequency Division Multiplexing

[0048] -FFT: Fast Fourier Transform

[0049] -IFDMA: Interleaved Frequency Division Multiple Access

[0050] -IFFT: Inverse Fast Fourier Transform

[0051] -L1-RSRP: Layer 1 Reference Signal Received Power

[0052] -L1-RSRQ: Layer 1 reference signal reception quality

[0053] -MAC: Media Access Control

[0054] -NZP: Non-zero power

[0055] -OFDM: Orthogonal Frequency Division Multiplexing

[0056] –PDCCH: Physical Downlink Control Channel

[0057] -PDSCH: Physical Downlink Shared Channel

[0058] -PMI: Precoding Matrix Indicator

[0059] -RE: Resource Element

[0060] -RI: Rank indicator

[0061] -RRC: Radio Resource Control

[0062] -RSSI: Received Signal Strength Indicator

[0063] -Rx: Receive

[0064] -QCL: Quasi-co-location

[0065] -SINR: Signal-to-Noise Ratio

[0066] -SSB (or SS / PBCH block): Synchronization signal block (including PSS (primary synchronization signal), SSS (secondary synchronization signal), and PBCH (physical broadcast channel)).

[0067] -TDM: Time Division Multiplexing

[0068] -TRP: Sending and Receiving Point

[0069] -TRS: Tracking Reference Signal

[0070] -Tx: Send

[0071] -UE: User Equipment

[0072] -ZP: Zero Power

[0073] Overall System

[0074] With more communication devices requiring higher capacity, there has been a demand for improved mobile broadband communications compared to existing radio access technologies (RATs). Furthermore, massive MTC (machine-type communication) that provides various services anytime, anywhere by connecting multiple devices and things is also one of the main issues to be considered in next-generation communications. In addition, communication system designs considering services / terminals sensitive to reliability and latency are discussed. Therefore, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), mMTC (massive MTC), URLLC (ultra-reliable low-latency communication), etc., is discussed, and for convenience, the corresponding technologies are referred to as NR in this disclosure. NR is an example expression representing 5G RAT.

[0075] New RAT systems, including those for NR, use OFDM or similar transmission methods. These new RAT systems may follow OFDM parameters different from those used in LTE. Alternatively, the new RAT system may follow existing LTE / LTE-A parameters as is, but may support a wider system bandwidth (e.g., 100MHz). Alternatively, a single cell may support multiple parameter sets. In other words, terminals operating according to different parameter sets can coexist in a single cell.

[0076] The parameter set corresponds to a subcarrier spacing in the frequency domain. Different parameter sets can be defined as the reference subcarrier spacing is scaled by an integer N.

[0077] Figure 1 The structure of a wireless communication system to which this disclosure can be applied is illustrated.

[0078] refer to Figure 1 The NG-RAN is configured with gNBs that provide control plane (RRC) protocol support for the NG-RA (NG Radio Access) user plane (i.e., the new AS (Access Layer) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and UE. The gNBs interconnect via the Xn interface. Furthermore, the gNBs are connected to the NGC (Next Generation Core) via the NG interface. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Power) via the N2 interface and to the UPF (User Plane Functions) via the N3 interface.

[0079] Figure 2 A frame structure in a wireless communication system to which this disclosure can be applied is illustrated.

[0080] NR systems can support multiple parameter sets. These parameter sets can be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings can be derived by scaling the basic (reference) subcarrier spacing by an integer N (or μ). Furthermore, while it is assumed that very low subcarrier spacings are not used at very high carrier frequencies, the parameter set used can be selected independently of the frequency band. Moreover, various frame structures based on multiple parameter sets can be supported in NR systems.

[0081] The OFDM parameter sets and frame structures that can be considered in an NR system are described below. Several OFDM parameter sets supported in an NR system can be defined as shown in Table 1 below.

[0082] [Table 1]

[0083] μ <![CDATA[Δf=2 μ ·15[kHz]]]> CP 0 15 normal 1 30 normal 2 60 Normal, expanded 3 120 normal 4 240 normal

[0084] NR supports multiple parameter sets (or subcarrier spacing (SCS)) to support various 5G services. For example, a 15kHz SCS supports wide-area coverage of traditional cellular bands; a 30kHz / 60kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidth; and a 60kHz or higher SCS supports bandwidths exceeding 24.25GHz to overcome phase noise. NR bands are defined as frequency ranges of two types (FR1, FR2). FR1 and FR2 can be configured as shown in Table 2 below. Additionally, FR2 can refer to millimeter wave (mmW).

[0085] [Table 2]

[0086]

[0087] Regarding the frame structure in the NR system, the size of various fields in the time domain is expressed as T. c =1 / (Δf) max ·N f A multiple of the time unit. Here, Δf max 480·10 3 Hz, and N f The value is 4096. Downlink and uplink transmissions are configured (organized) to have a duration T. f =1 / Δf max N f / 100)·T c A radio frame of 10ms. Here, the radio frame is configured with 10 subframes, each with a T... sf =(Δf max N f / 1000)·T c =1ms duration. In this case, there may be one frame set for the uplink and one frame set for the downlink. Furthermore, the transmission in the i-th uplink frame from the terminal should begin T seconds earlier than the corresponding downlink frame in the corresponding terminal. TA =(N TA +N TA,offset )T c Begin. For the subcarrier spacing configuration μ, the time slots are arranged in n-order within the subframe. s μ ∈{0,...,N slot subframe,μ The numbers are numbered in ascending order from -1 to n, and are placed in the radio frame according to n. s,f μ ∈{0,...,N slot frame,μ The time slot is configured with N in ascending order of -1. symb slotN consecutive OFDM symbols, and N symb slot Determined based on CP. Slot n in the subframe s μ The start of the OFDM symbol n in the same subframe s μ N symb slot The start dates are arranged in time. Not all terminals may perform transmission and reception simultaneously, meaning that all OFDM symbols in either the downlink or uplink time slots may not be available.

[0088] Table 3 shows the number of OFDM symbols (N) in each time slot during normal CP. symb slot ), Number of time slots per radio frame (N) slot frame,μ ) and the number of time slots per subframe (N) slot subframe,μ Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0089] [Table 3]

[0090] μ <![CDATA[N symb slot ]]> <![CDATA[N slot frame,μ ]]> <![CDATA[N slot subframe,μ ]]> 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

[0091] [Table 4]

[0092] μ <![CDATA[N symb slot ]]> <![CDATA[N slot frame,μ ]]> <![CDATA[N slot subframe,μ ]]> 2 12 40 4

[0093] Figure 2 This is an example of μ=2 (SCS is 60kHz), see Table 3. One subframe can include 4 time slots. Figure 2 The subframe shown as {1,2,4} is an example, and the number of time slots that can be included in a subframe is defined in Table 3 or Table 4. Additionally, micro-time slots can include 2, 4, or 7 symbols, or more or fewer symbols.

[0094] Regarding physical resources in an NR system, factors such as antenna ports, resource grids, resource elements, resource blocks, and carrier components can be considered. The following sections will describe these physical resources in detail.

[0095] First, regarding antenna ports, an antenna port is defined such that the channel carrying a symbol in that antenna port can be inferred from the channels carrying other symbols in the same antenna port. When the large-scale properties of the channel carrying a symbol in one antenna port can be inferred from the channel carrying symbols in another antenna port, it can be said that the two antenna ports are in a QC / QCL (quasi-co-located or quasi-co-located) relationship. In this case, the large-scale properties include at least one of delay spread, Doppler spread, frequency shift, average received power, and receive timing.

[0096] Figure 3 The illustration shows a resource grid in a wireless communication system to which this disclosure can be applied.

[0097] refer to Figure 3 The diagram illustrates the resource grid configuration with N in the frequency domain. RB μ N sc RB There are 14.2 subcarriers, and one subframe is configured with 14.2 μ The number of OFDM symbols is not limited to this. In an NR system, the transmitted signal consists of 2 OFDM symbols. μ N symb (μ) Each OFDM symbol and configuration has N RB μ N sc RB It is described by one or more resource grids of N subcarriers. Here, N RB μ ≤N RB max,μ N RB max,μ This represents the maximum transmission bandwidth, which may differ between uplink and downlink, and between parameter sets. In this case, each μ and antenna port p can be configured with a resource grid. Each element of the resource grid used for μ and antenna port p is called a resource element and is uniquely identified by an index pair (k, l'). Here, k = 0, ..., N RB μ N sc RB -1 is the index in the frequency domain, and l' = 0, ..., 2 μ N symb (μ) -1 indicates the symbol position within the subframe. When referencing resource elements in a time slot, the index pair (k, l) is used. Here, l = 0,...,N symb μ -1. The resource element (k,l') used for μ and antenna port p corresponds to the complex value a. k,l' (p,μ)When there is no risk of confusion or when a specific antenna port or parameter set is not specified, the indices p and μ may be discarded, and the complex value may be ak,l'(p) or ak,l'. Furthermore, a resource block (RB) is defined as N in the frequency domain. sc RB = 12 consecutive subcarriers.

[0098] Point A serves as a common reference point for the resource block grid and is obtained as follows.

[0099] - The offsetToPointA of the downlink in the primary cell (PCell) represents the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block, which is used by the terminal for initial cell selection. It is assumed that a 15kHz subcarrier spacing is used for FR1 and a 60kHz subcarrier spacing is used for FR2, expressed in units of resource blocks.

[0100] absoluteFrequencyPointA represents the frequency position of point A, expressed as ARFCN (Absolute Radio Frequency Channel Number).

[0101] For subcarrier spacing configuration μ, common resource blocks are numbered from 0 upwards in the frequency domain. The center of subcarrier 0 of common resource block 0 used for subcarrier spacing configuration μ is the same as "point A". The common resource block number n of subcarrier spacing configuration μ in the frequency domain is... CRB μ The relationship between the resource element (k,l) and the resource element (k,l) is given by Equation 1 below.

[0102] [Formula 1]

[0103]

[0104] In Equation 1, k is defined relative to point A, such that k = 0 corresponds to a subcarrier centered at point A. Physical resource blocks range from 0 to N in the bandwidth portion (BWP). BWP,i size,μ -1 is the number, and i is the number of the BWP. The physical resource block n in BWP i. PRB and public resource block n CRB The relationship between them is given by Equation 2.

[0105] [Equation 2]

[0106]

[0107] N BWP,i start,μ It is a public resource block relative to public resource block 0 in BWP.

[0108] Figure 4Examples of physical resource blocks in wireless communication systems that can utilize this disclosure are provided. Furthermore, Figure 5 The time slot structure in a wireless communication system to which this disclosure can be applied is illustrated.

[0109] refer to Figure 4 and Figure 5 A time slot comprises multiple symbols in the time domain. For example, for a normal CP, one time slot includes 7 symbols, but for an extended CP, one time slot includes 6 symbols.

[0110] A carrier comprises multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Component) is defined as multiple consecutive (physical) resource blocks in the frequency domain and can correspond to a set of parameters (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through active BWPs, and only one BWP can be active for a single terminal. In the resource grid, each element is called a resource element (RE) and can be mapped to a complex number of symbols.

[0111] In NR systems, each component carrier (CC) can support up to 400MHz. If a terminal operating in such a wideband CC always operates with the radio frequency (FR) chip turned on for the entire CC, terminal battery consumption may increase. Alternatively, when considering multiple application scenarios operating in a wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different sets of parameters (e.g., subcarrier spacing, etc.) can be supported in each frequency band of the corresponding CC. Alternatively, each terminal may have different capabilities for the maximum bandwidth. With this in mind, the base station can instruct the terminal to operate only in a portion of the bandwidth, rather than in the full bandwidth of the wideband CC, and for convenience, the corresponding portion of the bandwidth is defined as the bandwidth portion (BWP). The BWP can be configured with consecutive RBs on the frequency axis and can correspond to a set of parameters (e.g., subcarrier spacing, CP length, slot / microslot duration).

[0112] Simultaneously, even within a single CC configured for a terminal, the base station can configure multiple BWPs. For example, a BWP occupying a relatively small frequency domain can be configured in the PDCCH monitoring slot, and PDSCH indicated by the PDCCH can be scheduled in a larger BWP. Alternatively, when a UE is congested in a particular BWP, other BWPs can be configured for some terminals for load balancing. Alternatively, considering inter-cell interference cancellation between neighboring cells, some intermediate spectrum of the full bandwidth can be excluded, and two edge BWPs can be configured in the same time slot. In other words, the base station can configure at least one DL / UL BWP for a terminal associated with a broadband CC. The base station can activate at least one DL / UL BWP among the configured DL / UL BWPs at a specific time (via L1 signaling, MAC CE (control element), or RRC signaling, etc.). Furthermore, the base station can instruct a handover to other configured DL / UL BWPs (via L1 signaling, MAC CE, or RRC signaling, etc.). Alternatively, based on a timer, a handover to a specific DL / UL BWP can be performed when the timer value expires. Here, the active DL / UL BWP is defined as the active DL / UL BWP. However, the terminal may not receive the configuration on the DL / UL BWP before performing the initial access procedure or establishing an RRC connection. Therefore, in these cases, the DL / UL BWP assumed by the terminal is defined as the initially active DL / UL BWP.

[0113] Figure 6 Examples are given of physical channels used in wireless communication systems to which this disclosure may be applied, as well as general signal transmission and reception methods using such physical channels.

[0114] In wireless communication systems, terminals receive information from base stations via downlink and transmit information to base stations via uplink. The information sent and received by base stations and terminals includes data and various control information, and various physical channels exist depending on the type / purpose of the information they send and receive.

[0115] When a terminal is powered on or enters a new cell, it performs an initial cell search (S601), including synchronization with the base station. For the initial cell search, the terminal synchronizes with the base station by receiving the primary synchronization signal (PSS) and secondary synchronization signal (SSS) from the base station, and obtains information such as the cell identifier (ID). Then, the terminal obtains broadcast information within the cell by receiving the physical broadcast channel (PBCH) from the base station. Simultaneously, the terminal checks the downlink channel state by receiving the downlink reference signal (DL RS) during the initial cell search phase.

[0116] The terminal that has completed the initial cell search can obtain more detailed system information by receiving the Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH) based on the information carried in the PDCCH (S602).

[0117] Simultaneously, when a terminal first accesses a base station or when there are no radio resources available for signal transmission, it can perform a random access (RACH) procedure (S603 to S606). For the random access procedure, the terminal can send a specific sequence as a preamble via the Physical Random Access Channel (PRACH) (S603 and S605), and can receive response messages to the preamble via the PDCCH and the corresponding PDSCH (S604 and S606). Contention-based RACH can further execute a contention resolution procedure.

[0118] The terminal that subsequently performs the above process can execute PDCCH / PDSCH reception (S607) and PUSCH (Physical Uplink Shared Channel) / PUCCH (Physical Uplink Control Channel) transmission (S608) as a general uplink / downlink signal transmission process. Specifically, the terminal receives downlink control information (DCI) via PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format varies depending on its intended use.

[0119] Meanwhile, control information sent by the terminal to the base station via the uplink or received by the terminal from the base station includes downlink / uplink ACK / NACK (acknowledgment / non-acknowledgment) signals, CQI (Channel Command Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. For 3GPP LTE systems, the terminal can send the aforementioned control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

[0120] Table 5 shows examples of DCI format in the NR system.

[0121] [Table 5]

[0122]

[0123]

[0124] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information (e.g., UL / SUL (Supplemental UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), information related to transport blocks (TB) (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), information related to HARQ (Hybrid Automatic Repeat and Request) (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., DMRS sequence initialization information, antenna ports, CSI requests, etc.), power control information related to PUSCH scheduling (e.g., PUSCH power control, etc.), and control information included in each DCI format can be predefined.

[0125] DCI format 0_0 is used to schedule PUSCH in a cell. The information included in DCI format 0_0 is scrambled with CRC (Cyclic Redundancy Check) by C-RNTI (Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and transmitted.

[0126] DCI format 0_1 ​​is used to indicate the scheduling of one or more PUSCHs or to provide downlink feedback information to the Terminal Configuration Grant (CG) in a cell. The information included in DCI format 0_1 ​​is scrambled and transmitted by C-RNTI, CS-RNTI, SP-CSI-RNTI (semi-persistent CSI RNTI), or MCS-C-RNTI.

[0127] DCI format 0_2 is used to schedule PUSCH within a cell. The information included in DCI format 0_2 is scrambled and transmitted using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0128] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information (e.g., frequency resource allocation, time resource allocation, VRB (Virtual Resource Block) - PRB (Physical Resource Block) mapping, etc.), information related to transport blocks (TB) (e.g., MCS, NDI, RV, etc.), information related to HARQ (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., antenna port, TCI (Transmission Configuration Indicator), SRS (Sound Reference Signal) request, etc.), information related to PUCCH scheduling regarding PDSCH (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format can be predefined.

[0129] DCI format 1_0 is used to schedule PDSCH in a DL cell. The information included in DCI format 1_0 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0130] DCI format 1_1 is used to schedule PDSCH in a cell. The information included in DCI format 1_1 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0131] DCI format 1_2 is used to schedule PDSCH in a cell. The information contained in DCI format 1_2 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0132] Operations related to multiple TRPs

[0133] Cooperative Multipoint (CoMP) schemes refer to schemes in which multiple base stations effectively control interference by exchanging or utilizing channel information (e.g., RI / CQI / PMI / LI (layer indicator)) fed back by terminals and cooperatively sent to terminals (e.g., using the X2 interface). Depending on the scheme used, CoMP can be classified as Joint Transmission (JT), Coordinated Scheduling (CS), Coordinated Beamforming (CB), Dynamic Point Selection (DPS), Dynamic Point Blocking (DPB), etc.

[0134] M-TRP transmission schemes, in which M TRPs send data to a single terminal, can be broadly categorized into i) eMBBM-TRP transmission, which is a scheme designed to improve transmission rates, and ii) URLLC M-TRP transmission, which is a scheme designed to improve reception success rates and reduce latency.

[0135] Furthermore, regarding DCI transmission, M-TRP transmission schemes can be classified into i) M-DCI (multiple DCIs) transmission where each TRP sends a different DCI, and ii) S-DCI (single DCI) transmission where a DCI is sent based on a single TRP. For example, for S-DCI-based M-TRP transmission, all scheduling information about the data sent by M TRPs should be delivered to the terminal via a single DCI. This can be used in an ideal backhaul (ideal BH) environment where dynamic cooperation between two TRPs is possible.

[0136] For TDM-based URLLC M-TRP transmission, schemes 3 and 4 are discussed under the guise of standardization. Specifically, scheme 4 implies a scheme in which a TRP transmits a transport block (TB) in one time slot, and it has the effect of improving the probability of receiving the same TB of data from multiple TRPs in multiple time slots. Furthermore, scheme 3 implies a scheme in which a TRP transmits a TB through a consecutive number of OFDM symbols (i.e., symbol groups), and the TRP can be configured to transmit the same TB through different symbol groups in one time slot.

[0137] Additionally, the UE can identify PUSCH (or PUCCH) scheduled by DCI received in different control resource sets (CORESETs) (or CORESETs belonging to different CORESET groups) as PUSCH (or PUCCH) sent to different TRPs, or it can identify PDSCH (or PDCCH) from different TRPs. Furthermore, the method described below for UL transmissions (e.g., PUSCH / PUCCH) sent to different TRPs can be equivalently applied to UL transmissions (e.g., PUSCH / PUCCH) sent to different panels belonging to the same TRP.

[0138] The following text will describe incoherent joint transport (NCJT) based on multiple DCIs / NCJT based on a single DCI.

[0139] NCJT (Noncoherent Joint Transmission) is a scheme in which multiple transmission points (TPs) send data to a terminal using the same time and frequency resources. TPs send data between each other by using different DMRS (Demodulation Multiplexing Reference Signals) through different layers (i.e., through different DMRS ports).

[0140] The TP transmits data scheduling information to the receiving terminal via DCI. Here, the scheme where each TP participating in NCJT transmits scheduling information over its own data transmitted via DCI is called "NCJT based on multiple DCIs". When each of the N TPs participating in NCJT transmission sends a DL grant DCI and PDSCH to the UE, the UE receives N DCIs and N PDSCHs from the N TPs. Furthermore, the scheme where a representative TP transmits scheduling information over its own data and data transmitted by different TPs (i.e., TPs participating in NCJT) via a single DCI is called "NCJT based on a single DCI". Here, N TPs transmit one PDSCH, but each TP only transmits some of the multiple layers included in the PDSCH. For example, when transmitting 4 layers of data, TP1 can transmit 2 layers, and TP2 can transmit the remaining 2 layers to the UE.

[0141] Multiple TRPs (MTRPs) performing NCJT transmissions can send DL data to the terminal using either of the following two schemes.

[0142] First, a “MTRP scheme based on a single DCI” is described. MTRPs cooperatively transmit a common PDSCH, and each TRP participating in the cooperative transmission spatially partitions and sends its corresponding PDSCH to different layers (i.e., different DMRS ports) using the same time and frequency resources. Here, a single DCI indicates scheduling information about the PDSCH to the UE, and which DMRS (group) port uses which QCL RS and QCL type information is indicated by the corresponding DCI (which differs from the DCI indicating the QCL RS and type that will be applied to all DMRS ports in existing schemes). In other words, M TCI states (e.g., M=2 for 2TRP cooperative transmission) can be indicated by the TCI (Transmission Configuration Indicator) field in the DCI, and the QCL RS and type can be indicated by using M different TCI states for M DMRS port groups. Additionally, DMRS port information can be indicated using a new DMRS table.

[0143] Next, the "MTRP scheme based on multiple DCIs" is described. Each MTRP transmits different DCIs and PDSCHs, and (partially or entirely) corresponding PDSCHs overlap and are transmitted in frequency-time resources. Corresponding PDSCHs can be scrambled using different scrambling IDs (identifiers), and DCIs can be transmitted using CORESETs belonging to different CORESET groups. (Here, CORESET groups can be identified by an index defined in the CORESET configuration for each CORESET. For example, when index = 0 is configured for CORESET 1 and CORESET 2 and index = 1 is configured for CORESET 3 and CORESET 4, CORESET 1 and CORESET 2 are CORESET group 0, and CORESET 3 and CORESET 4 belong to CORESET group 1. Additionally, when no index is defined in a CORESET, it can be interpreted as index = 0.) When multiple scrambling IDs or two or more CORESET groups are configured in a serving cell, the UE can be aware that it receives data according to the MTRP operation based on multiple DCIs.

[0144] Alternatively, the UE can be instructed via separate signaling whether an MTRP scheme based on a single DCI or an MTRP scheme based on multiple DCIs is used. In the example, for a serving cell, the UE can be instructed to use multiple CRS (Cell Reference Signal) modes for MTRP operation. In this case, the PDSCH rate matching for CRS can be different depending on whether an MTRP scheme based on a single DCI or an MTRP scheme based on multiple DCIs is used (because the CRS modes are different).

[0145] In the following, the CORESET group ID described / mentioned in this disclosure may represent index / identification information (e.g., ID, etc.) used to distinguish CORESETs for each TRP / panel. Alternatively, a CORESET group may be a set / collection of CORESETs distinguished by index / identification information (e.g., ID) / CORESET group ID, etc., used to distinguish CORESETs for each TRP / panel. In the example, the CORESET group ID may be specific index information defined in the CORESET configuration. In this case, the CORESET group may be defined by index configuration / indication / definition defined in the CORESET configuration of each CORESET. Additionally / alternatively, the CORESET group ID may represent index / identification information / indicators, etc., used to distinguish / identify between configured / associated CORESETs with each TRP / panel. In the following, the CORESET group ID described / mentioned in this disclosure may be represented by a specific index / specific identification information / specific indicator used to distinguish / identify between configured / associated CORESETs with each TRP / panel. The CORESET group ID (i.e., a specific index / specific identification information / specific indicator used to distinguish / identify the CORESETs associated with each TRP / panel) can be configured / indicated to the terminal via higher-level signaling (e.g., RRC signaling) / L2 signaling (e.g., MAC-CE) / L1 signaling (e.g., DCI). In the example, it can be configured / indicated to cause PDCCH detection to be performed for each TRP / panel in the cell of the corresponding CORESET group (i.e., for TRPs / panels belonging to the same CORESET group). Additionally / alternatively, it can be configured / indicated to cause uplink control information (e.g., CSI, HARQ-A / N (ACK / NACK), SR (scheduling request)) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) to be separated and managed / controlled for each TRP / panel in the cell of the corresponding CORESET group (i.e., for TRPs / panels belonging to the same CORESET group). Alternatively, HARQ A / N (processing / retransmission) for PDSCH / PUSCH, etc., scheduled for each TRP / panel can be managed for the corresponding CORESET group (i.e., for TRPs / panels belonging to the same CORESET group).

[0146] The partially overlapping NCJT will be described below.

[0147] Furthermore, NCJTs can be classified into fully overlapping NCJTs, where the time and frequency resources transmitted by each TP completely overlap, and partially overlapping NCJTs, where only some time and frequency resources overlap. In other words, for a partially overlapping NCJT, data from both TP1 and TP2 are transmitted in some time and frequency resources, and data from only one of TP1 or TP2 is transmitted in the remaining time and frequency resources.

[0148] The following section describes methods for improving reliability in multiple TRPs.

[0149] As a method for improving reliability in sending and receiving when using multiple TRPs, the following two methods can be considered.

[0150] Figure 7 Methods for multiple TRP transmissions that can be applied in a wireless communication system according to this disclosure are illustrated.

[0151] Reference Figure 7 (a) illustrates the case where layer groups transmitting the same codeword (CW) / transmission block (TB) correspond to different TRPs. Here, a layer group can mean a predetermined set of layers comprising one or more layers. In this case, the advantage is that due to the increased number of layers, the amount of transmission resources increases, thus robust channel coding with low coding rates can be used for the TB. Additionally, since multiple TRPs have different channels, improved reliability of the received signal based on diversity gain can be expected.

[0152] Reference Figure 7 (b) illustrates an example of transmitting different CWs through layer groups corresponding to different TRPs. Here, it can be assumed that the TBs corresponding to CW#1 and CW#2 in the figure are the same. In other words, CW#1 and CW#2 mean that the same TB is transformed into different CWs by different TRPs through channel coding, etc. Therefore, examples of repeatedly transmitting the same TB can be considered. Figure 7 In case (b), with Figure 7 Compared to (a), it may have the disadvantage of a higher code rate corresponding to TB. However, it has the advantage that the code rate can be adjusted by indicating different RV (redundant version) values ​​or the modulation order of each CW can be adjusted according to the channel environment for the coded bits generated from the same TB.

[0153] According to the above Figure 7 (a) and Figure 7The method shown in (b) improves the data reception probability of the terminal because the same TB is repeatedly transmitted through different layer groups and each layer group is transmitted by different TRPs / panels. It is called the SDM (Space Division Multiplexing) based M-TRP URLLC transmission method. Layers belonging to different layer groups are transmitted through DMRS ports belonging to different DMRS CDM groups.

[0154] Furthermore, the above-mentioned content related to multiple TRPs is based on the SDM (Space Division Multiplexing) method using different layers, but it can be naturally extended and applied to FDM (Frequency Division Multiplexing) methods based on different frequency domain resources (e.g., RB / PRB (sets) etc.) and / or TDM (Time Division Multiplexing) methods based on different time domain resources (e.g., time slots, symbols, sub-symbols etc.).

[0155] The following methods are discussed for URLLC based on multiple TRPs and scheduled by a single DCI.

[0156] 1) Method 1 (SDM): Time and frequency resource allocation overlaps and there are n (n<=Ns) TCI states in a single time slot.

[0157] 1-a) Method 1a

[0158] - The same TB is sent in a layer or layer set at each transmission time (timing), and each layer or layer set is associated with a TCI and a DMRS port set.

[0159] - Use a single codeword with one RV in all spatial layers or all layer sets. Regarding UEs, map different coded bits to different layers or layer sets using the same mapping rules.

[0160] 1-b) Method 1b

[0161] - The same TB is sent in a layer or layer set at each transmission time (timing), and each layer or layer set is associated with a TCI and a DMRS port set.

[0162] - A single codeword with one RV is used in each spatial layer or each set of layers. The RV corresponding to each spatial layer or each set of layers can be the same or different.

[0163] 1-c) Method 1c

[0164] - Send the same TB with a DMRS port associated with multiple TCI status indices in a layer at a transmission time (timing), or send the same TB with multiple DMRS ports associated one-to-one with multiple TCI status indices in a layer.

[0165] In the cases of methods 1a and 1c above, the same MCS is applied to all layers or all sets of layers.

[0166] 2) Method 2 (FDM): Frequency resource allocation does not overlap and there are n (n<=Nf) TCI states in a single time slot.

[0167] - Each non-overlapping frequency resource allocation is associated with a TCI state.

[0168] - The same single / multiple DMRS ports are associated with all non-overlapping frequency resource allocations.

[0169] 2-a) Method 2a

[0170] - A single codeword with one RV is used for all resource allocations. For the UE, common RB matching (codeword-to-layer mapping) is applied to all resource allocations.

[0171] 2-b) Method 2b

[0172] A single codeword with one RV is used for each non-overlapping frequency resource allocation. The RV corresponding to each non-overlapping frequency resource allocation can be the same or different.

[0173] For method 2a above, the same MCS is applied to all non-overlapping frequency resource allocations.

[0174] 3) Method 3 (TDM): Time resource allocation does not overlap and there are n (n<=Nt1) TCI states in a single time slot.

[0175] - Each transmission time (opportunity) of a TB has a micro-slot time granularity and has a TCI and an RV.

[0176] - All transmission times (timings) in a time slot are used with a common MCS and one or more DMRS ports.

[0177] -RV / TCI can be the same or different at different transmission times (timings).

[0178] 4) Method 4 (TDM): n (n<=Nt2) TCI states in K (n<=K) different time slots

[0179] - Each transmission time (opportunity) of a TB has one TCI and one RV.

[0180] - All transmission times (timings) across K time slots use a common MCS and one or more DMRS ports.

[0181] -RV / TCI can be the same or different at different transmission times (timings).

[0182] The MTRP URLLC is described below.

[0183] In this disclosure, DL MTRP URLLC means that multiple TRPs transmit the same data (e.g., the same TB) / DCI using different tier / time / frequency resources. For example, TRP 1 transmits the same data / DCI in resource 1, and TRP 2 transmits the same data / DCI in resource 2. A UE configured with the DL MTRP-URLLC transmission method receives the same data / DCI using different tier / time / frequency resources. Here, the UE is configured from the base station to use which QCL RS / type (i.e., DL TCI state) should be used in the tier / time / frequency resources for receiving the same data / DCI. For example, when the same data / DCI is received in resource 1 and resource 2, the DL TCI state used in resource 1 and the DL TCI state used in resource 2 can be configured. The UE can achieve high reliability because it receives the same data / DCI through resource 1 and resource 2. This DL MTRP URLLC can be applied to PDSCH / PDCCH.

[0184] Furthermore, in this disclosure, UL MTRP-URLLC means that multiple TRPs receive the same data / UCI (uplink control information) from any UE using different layer / time / frequency resources. For example, TRP 1 receives the same data / DCI from the UE in resource 1, and TRP 2 receives the same data / DCI from the UE in resource 2, and shares the received data / DCI through a backhaul link connected between the TRPs. UEs configured with the UL MTRP-URLLC transmission method transmit the same data / UCI using different layer / time / frequency resources. Here, the UE is configured from the base station to use which Tx beam and which Tx power (i.e., UL TCI state) should be used in the layer / time / frequency resources for transmitting the same data / DCI. For example, when transmitting the same data / UCI in resource 1 and resource 2, the UL TCI state used in resource 1 and the UL TCI state used in resource 2 can be configured. Such UL MTRP URLLC can be applied to PUSCH / PUCCH.

[0185] Additionally, in this disclosure, when a specific TCI state (or TCI) is used (or mapped) when receiving data / DCI / UCI for any frequency / time / space resource (layer), it means the following: For DL, it may mean estimating the channel from the DMRS using the QCL type and QCL RS indicated by the corresponding TCI state in that frequency / time / space resource (layer), and receiving / demodulating the data / DCI based on the estimated channel. For UL, it may mean transmitting / modulating the DMRS and data / UCI using the Tx beam and power indicated by the corresponding TCI state in that frequency / time / space resource.

[0186] Here, instead of the TCI state, the UL TCI state contains the UE's Tx beam and / or Tx power information, as well as spatial relationship information, and can be configured to the UE using other parameters. The UL TCI state can be directly indicated by the UL-authorized DCI, or it can represent the spatial relationship information of the SRS resources indicated by the SRI (Probe Resource Indicator) field of the UL-authorized DCI. Alternatively, it can mean the open-loop (OL) Tx power control parameters connected to the values ​​indicated by the SRI field of the UL-authorized DCI (e.g., j: index of open-loop parameter Po and α (up to 32 parameter values ​​per cell), q_d: index of DL RS resources used for PL (path loss) measurements (up to 4 measurements per cell), l: index of closed-loop power control procedure (up to 2 procedures per cell).

[0187] The MTRP eMBB is described below.

[0188] In this disclosure, MTRP-eMBB means that multiple TRPs transmit different data (e.g., different TBs) using different layers / times / frequency. A UE configured with the MTRP-eMBB transmission method receives indications about multiple TCI states via DCI, and it is assumed that the data received using the QCL RS for each TCI state is different data.

[0189] On the other hand, the UE can distinguish between MTRP URLLC and MTRP eMBB transmissions / receives by separately defining the RNTI for MTRP-URLLC and the RNTI for MTRP-eMBB, and using them accordingly. In other words, when performing a CRC mask for DCI using the RNTI for URLLC, the UE is considered to be transmitting via URLLC, and when performing a CRC mask for DCI using the RNTI for eMBB, the UE is considered to be transmitting via eMBB. Alternatively, the base station can configure MTRP-URLLC transmission / receive for the UE, or it can configure TRP eMBB transmission / receive via other new signaling.

[0190] In the description of this disclosure, for ease of description, it is described by assuming cooperative transmission / reception between two TRPs. However, the method proposed in this disclosure can also be extended and applied in environments with three or more multi-TRPs, and additionally, it can be extended and applied to multiple panel environments (i.e., by matching TRPs with panels). Furthermore, different TRPs can be identified as different TCI states for the UE. Therefore, when the UE receives / transmits data / DCI / UCI using TCI state 1, it means receiving data / DCI / UCI from TRP 1 and sending data / DCI / UCI to TRP 1.

[0191] The embodiments of this disclosure described below can be used for situations where MTRP cooperatively transmits PDCCH (e.g., the same PDCCH is transmitted repeatedly or separately), and some embodiments can also be used for situations where MTRP cooperatively transmits PDSCH or cooperatively receives PUSCH / PUCCH.

[0192] Furthermore, in describing this disclosure, the meaning of multiple base stations (i.e., MTRPs) repeatedly transmitting the same PDCCH can mean that the same DCI is transmitted through multiple PDCCH candidates, and multiple base stations transmitting the same DCI can mean that it has been repeatedly transmitted. The same DCI can mean two DCIs with the same DCI format / size / payload. Alternatively, even if the payloads of two DCIs are different, if the scheduling results are the same, the two DCIs can also be said to be the same DCI. For example, the Time Domain Resource Allocation (TDRA) field of a DCI relatively determines the time slot / symbol position of the data and the time slot / symbol position of A / N based on the DCI reception time. In this case, when a DCI received at time n and a DCI received at time n+1 notify the UE of the same scheduling result, the TDRA fields of the two DCIs are different, therefore, the DCI payloads will inevitably be different. The number of repetitions R can be directly indicated to the terminal by the base station, or it can be mutually predicted. Alternatively, even if the payloads of two DCIs are different and the scheduling results are not identical, a DCI can still be considered the same DCI if the scheduling result of one DCI is a subset of the scheduling result of the other DCI. For example, when the same data is TDM and is transmitted N times, DCI 1, received before the first data, indicates that the data is repeated N times, and DCI 2, received after the first data and before the second data, indicates that the data is repeated N-1 times. The scheduled data of DCI 2 is a subset of the scheduled data of DCI 1, and since the two DCIs are scheduling the same data, they can also be considered the same DCI in this case.

[0193] Furthermore, in the description of this disclosure below, the transmission of the same PDCCH by multiple base stations may mean that a DCI is transmitted through a single PDCCH candidate. However, TRP 1 defines some resources for the PDCCH candidate, and TRP 2 allocates and transmits the remaining resources. For example, when TRP 1 and TRP 2 allocate and transmit PDCCH candidates corresponding to aggregation levels m1+m2, the PDCCH candidates are divided into PDCCH candidate 1 corresponding to aggregation level m1 and PDCCH candidate 2 corresponding to aggregation level m2. TRP 1 transmits PDCCH candidate 1, and TRP 2 transmits PDCCH candidate 2 using different time / frequency resources. After receiving PDCCH candidate 1 and PDCCH candidate 2, the UE can generate a PDCCH candidate corresponding to aggregation level m1+m2 and attempt DCI decoding.

[0194] In addition, when the same DCI is divided and sent to several PDCCH candidates, there are two possible implementation methods.

[0195] The first implementation method involves encoding the DCI payload (control information bits + CRC) using a channel encoder (e.g., a polar encoder), with the resulting encoded bits divided and transmitted by two TRPs. In this case, the entire DCI payload can be encoded in the encoded bits transmitted by each TRP, or only some of the DCI payload can be encoded. The second method divides the DCI payload (control information bits + CRC) into two parts (DCI 1 and DCI 2), and encodes each part separately using a channel encoder (e.g., a polar encoder). Subsequently, the two TRPs transmit the encoded bits corresponding to DCI 1 and the encoded bits corresponding to DCI 2, respectively.

[0196] In summary, dividing / repeating the same PDCCH for transmission across multiple MOs by multiple base stations (MTRP) can mean: 1) the encoded DCI bits that encode the entire DCI content of the corresponding PDCCH are repeatedly transmitted for each base station (STRP) through each MO; 2) the encoded DCI bits that encode the entire DCI content of the corresponding PDCCH are divided into multiple parts, and different parts are transmitted for each base station (STRP) through each MO; or 3) the DCI content of the corresponding PDCCH is divided into multiple parts, different parts are encoded separately for each base station (STRP), and different parts are transmitted through each MO.

[0197] Repeated or partitioned transmission of PDCCH can be understood as meaning that PDCCH is transmitted multiple times at multiple transmission times (TOs), and that a TO signifies a specific time / frequency resource unit for transmitting the PDCCH. For example, if PDCCH is transmitted multiple times on time slots 1, 2, 3, and 4 (to a specific RB), then TO can signify each time slot; if PDCCH is transmitted multiple times on RB sets 1, 2, 3, and 4 (within a specific time slot), then TO can signify each RB set; or if PDCCH is transmitted multiple times at different times and frequencies, then TO can signify each time / frequency resource. Furthermore, the TCI state used for DMRS channel estimation can be set differently for each TO, and it can be assumed that different TRPs / panels transmit TOs with different TCI states. Multiple base stations repeatedly transmitting or partitioning PDCCH for transmission can mean transmitting PDCCH across multiple TOs, and that the union of the TCI states established on those TOs includes two or more TCI states. For example, when PDCCH is sent at TO 1, TO 2, TO 3, TO 4, TCI states 1, 2, 3, and 4 can be configured at each of TO 1, TO 2, TO 3, TO 4, which means that TRP i cooperatively sends PDCCH at TO i.

[0198] Furthermore, as described below in this disclosure, the UE repeatedly transmits the same PUSCH, such that multiple base stations (i.e., MTRPs) receiving it can mean transmitting the same data through multiple PUSCHs, and each PUSCH can be optimized and transmitted for uplink channels of different TRPs. For example, the UE can repeatedly transmit the same data through PUSCH 1 and PUSCH 2, and the UE can transmit PUSCH 1 using UL TCI state 1 for TRP 1, and the UE can also receive and transmit channel-optimized values ​​for link adaptation (such as precoder / MCS) for TRP 1. The UE can transmit PUSCH 2 using UL TCI state 2 for TRP 2, and the UE can transmit by scheduling channel-optimized values ​​for link adaptation (such as precoder / MCS) for TRP 2. In this case, the repeatedly transmitted PUSCH 1 and PUSCH 2 can be transmitted at different times as TDM, FDM, or SDM.

[0199] Additionally, as described below in this disclosure, the UE partitioning and transmitting the same PUSCH allows multiple base stations (i.e., MTRPs) to receive it. This can mean that one data is transmitted via a single PUSCH, but the resources allocated to the PUSCH are partitioned and optimized for different TRPs using UL channels for transmission. For example, the UE can transmit the same data via a 10-symbol PUSCH and can transmit the first 5 symbols using UL TCI state 1 for TRP 1, and can receive and transmit values ​​optimized for link adaptation (e.g., precoder / MCS) and TRP 1 channels. The UE can transmit the remaining 5 symbols using UL TCI state 2 for TRP 2, and the UE can receive and transmit values ​​optimized for TRP 2 using link adaptation (e.g., precoder / MCS). In the above example, a PUSCH can be partitioned into time resources to perform TDM transmission for TRP 1 and TRP 2, but FDM / SDM transmission can also be used.

[0200] Similar to PUSCH transmission, PUCCH can also be transmitted by the UE, which may repeatedly transmit the same PUCCH or divide the same PUCCH to be received by multiple base stations (i.e., MTRPs).

[0201] The proposals in this disclosure can be extended and applied to various channels, such as PUSCH / PUCCH / PDSCH / PDCCH.

[0202] The proposals in this disclosure can be extended and applied to situations where channels are repeatedly transmitted on different time / frequency / spatial resources, as well as situations where channels are transmitted separately.

[0203] Detection Reference Signal (SRS)

[0204] In Rel-15 NR, spatialRelationInfo can be used to indicate the transmission beam used when a base station transmits a UL channel to a terminal. The base station can indicate which UL transmission beam will be used when transmitting PUCCH and SRS by configuring the DL reference signal (e.g., SSB-RI (SB Resource Indicator), CRI (CSI-RS Resource Indicator) (P / SP / AP: Periodic / Semi-Persistent / Aperiodic)) or the SRS (i.e., SRS resource) and / or the target RS as the reference RS for the target UL channel, using RRC configuration. Additionally, when the base station schedules PUSCH to the terminal, the transmission beam indicated by the base station and used for SRS transmission is indicated as the transmission beam for PUSCH via the SRI field and is used as the terminal's PUSCH transmission beam.

[0205] The SRS for codebook (CB) and non-codebook (NCB) are described below.

[0206] First, for a CB UL, the base station can configure and / or instruct the terminal to transmit the SRS resource set for 'CB'. Additionally, the terminal can transmit any n port SRS resources corresponding to the SRS resource set. The base station can transmit and receive UL channels based on the corresponding SRS and use them for the terminal's PUSCH scheduling. Subsequently, the base station can instruct the terminal's PUSCH (transmission) beam by indicating the SRS resources for 'CB' previously transmitted by the terminal via the SRI field of the DCI when performing PUSCH scheduling through the UL DCI. Furthermore, the base station can instruct the UL rank and UL precoder by instructing the uplink codebook using the TPMI (Transmitted Precoder Matrix Indicator) field. Therefore, the terminal can perform PUSCH transmission according to the corresponding instructions.

[0207] Next, for NCB UL, the base station can first configure and / or instruct the terminal to transmit SRS resource sets for 'non-CB'. Additionally, the terminal can simultaneously transmit the corresponding SRS resources by determining the precoder for the SRS resources (up to 4 resources, 1 port per resource) in the corresponding SRS resource set based on the reception of the NZP CSI-RS connected to the corresponding SRS resource set. Subsequently, the base station can simultaneously instruct the terminal's PUSCH (transmission) beam, UL rank, and UL precoder by instructing the portion of the 'non-CB' SRS resources previously transmitted by the terminal via the SRI field of the DCI when performing PUSCH scheduling through the UL DCI. Therefore, the terminal can perform PUSCH transmission according to the corresponding instructions.

[0208] The SRS used for beam management is described below.

[0209] SRS can be used for beam management. Specifically, UL BM can be performed via beamforming UL SRS transmission. Whether UL BM is applied to an SRS resource set (higher-layer parameter) depends on the 'usage' configuration. When usage is configured as 'BeamManagement(BM)', at a given time, only one SRS resource can be sent to each of the multiple SRS resource sets. The terminal can be configured with at least one Probe Reference Symbol (SRS) resource set configured by (higher-layer parameter) 'SRS-ResourceSet' (via higher-layer signaling, e.g., RRC signaling, etc.). For each SRS resource set, the UE can be configured with K ≥ 1 SRS resources (higher-layer parameter, 'SRS-resources'). In this case, K is a natural number and the maximum value of K is indicated by SRS_capability.

[0210] The SRS used for antenna switching is described below.

[0211] SRS can be used to acquire DL CSI (Channel State Information) information (e.g., DL CSI acquisition). As a specific example, the BS (Base Station) can measure the SRS from the UE (User Equipment) after SRS transmissions are scheduled to the UE (User Equipment) in a single cell or multiple cells (e.g., carrier aggregation (CA)) based on TDD. Here, the base station can perform DL signal / channel scheduling to the UE based on SRS measurements by assuming DL / UL reciprocity. Regarding SRS-based DL CSI acquisition, SRS can be configured for antenna switching use.

[0212] In the example, when following standards (e.g., 3GPP TS38.214), the use of SRS can be configured for the base station and / or terminal by using higher-layer parameters (e.g., the use of the RRC parameter SRS-ResourceSet). Here, the use of SRS can be configured for beam management, codebook transmission, non-codebook transmission, antenna switching, etc.

[0213] Furthermore, in the examples of this disclosure, the reference signal RS (e.g., CSI-RS, SRS, etc.) is used as a term that includes not only predetermined RSs but also various physical layer signals / channels such as synchronization signals or SS / PBCH blocks. Additionally, RS resources can be understood as units used to distinguish RS characteristics. For example, a first SRS resource and a second SRS resource can correspond to SRSs distinguished in terms of configuration parameters such as time / frequency / space / sequence. Similarly, a first CSI-RS resource and a second CSI-RS resource can correspond to different CSI-RSs in terms of configuration parameters such as time / frequency / space / sequence. Therefore, configuring RS resources can mean configuring specific parameters for a corresponding RS configuration, and transmitting / receiving RS resources (or transmitting / receiving RS resources) can mean transmitting / receiving RS based on the configured parameters of the RS resources.

[0214] Furthermore, in the examples of this disclosure, for clarity, it is assumed that one or more 1-port SRS resources are configured / transmitted in SRS configuration and transmission; however, the scope of this disclosure is not limited thereto. That is, in the following description, it is assumed that one SRS port is configured / transmitted, and one or more SRS resources are configured / transmitted through one SRS resource, but one or more SRS ports are configured / transmitted through one SRS resource, and the examples of this disclosure can be applied even when one or more SRS resources are configured / transmitted. For example, when configuration and transmission of multiple SRS ports per SRS resource are supported, in the following description, 'SRS port' can be used to replace 'SRS resource', and 'N SRS ports' can be used to replace 'N SRS resources', and these N SRS ports can be configured / transmitted through one or more SRS resources. For example, when N=4, it can be a 4-port SRS resource (i.e., 4 SRS ports are configured / transmitted through one SRS resource), or a 2-port SRS resource and an additional 2-port SRS resource (i.e., the first and second SRS ports are configured / transmitted through the first SRS resource, and the third and fourth SRS ports are configured / transmitted through the second SRS resource). For example, when N=3, it can be a 2-port SRS resource and a 1-port SRS resource (i.e., the first and second SRS ports are configured / transmitted through the first SRS resource, and the third SRS port can be configured / transmitted through the second SRS resource).

[0215] Furthermore, in the following description, uplink transmission will be described assuming PUSCH transmission, but the examples of this disclosure can also be applied to the transmission of various uplink channels / signals other than PUSCH (e.g., PUCCH, SRS, or PRACH).

[0216] Uplink transmission based on configuration of multiple probe reference signal resource sets

[0217] This disclosure relates to a method for a UE to perform uplink transmission based on one or more of a plurality of configured SRS resource sets.

[0218] Although this disclosure primarily describes non-codebook-based uplink transmission as a representative example, the scope of this disclosure is not limited thereto, and the examples of this disclosure can also be applied to codebook-based uplink transmission. That is, the scope of this disclosure includes various uplink transmission schemes based on multiple SRS resource sets configured for the UE.

[0219] Additionally, in the following description, for clarity, one SRS resource set corresponds to one TRP; however, the scope of this disclosure is not limited thereto. An SRS resource set includes all transmit / receive schemes based on other corresponding units. For example, in the examples of this disclosure, one TRP may correspond to units of one or more control resource sets (CORESETs). For example, a first TRP may correspond to a first CORESET pool (or CORESET group / set), and a second TRP may correspond to a second CORESET pool (or CORESET group / set). Furthermore, in the examples of this disclosure, one SRS resource set may correspond to an associated (NZP) CSI-RS resource. For example, a first SRS resource set and a first associated CSI-RS resource may correspond to each other, and a second SRS resource set and a second associated CSI-RS resource may correspond to each other.

[0220] In the following text, reference will be made to Figure 8 Describes a method for a UE to perform uplink transmission based on one or more SRS resource sets.

[0221] Figure 8 This is a flowchart illustrating an uplink transmission method for a UE in a wireless communication system to which this disclosure can be applied.

[0222] In step S810, the UE can receive configuration information related to multiple SRS resource sets from the base station.

[0223] For example, configuration information associated with multiple SRS resource sets can be configured based on 'SRS-ResourceSet' as a higher-level parameter, and an exemplary configuration of 'SRS-ResourceSet' can be shown in Table 6 below.

[0224] [Table 6]

[0225]

[0226] Specifically, the configuration information associated with multiple SRS resource sets may include information for configuring each use of the multiple SRS resource sets as a codebook, non-codebook, or for other purposes (e.g., beam management, antenna switching, etc.).

[0227] Additionally, the information associated with multiple SRS resource sets may include information for configuring the SRS resource set to be used for uplink transmission among the multiple SRS resource sets. For example, the configuration information associated with multiple SRS resource sets may include information for configuring a first SRS resource set and a second SRS resource set among the multiple SRS resource sets, and each of the first SRS resource set and the second SRS resource set may correspond to TRP 1 and TRP 2, respectively. However, this is only one implementation, and the configuration information associated with multiple SRS resource sets may include information for configuring two or more SRS resource sets among the multiple SRS resource sets.

[0228] The number of SRS resources configured in each SRS resource set can be different, but is not limited to this. Configuration information associated with multiple SRS resource sets may also include information for configuring the same number of SRS resources included in both the first and second SRS resource sets.

[0229] In step S820, the UE can receive a DCI indicating one or more of the SRS resource set or SRS resources from the base station.

[0230] Specifically, the UE can receive from the base station a DCI including information indicating a first SRS resource set, a second SRS resource set, or at least one of the first SRS resource set and the second SRS resource set. Additionally, the DCI may also include information indicating at least one SRS resource in each of the indicated one or more SRS resource sets.

[0231] Information indicating at least one SRS resource set and information indicating at least one SRS resource can be included in one or more fields of the DCI. For example, information indicating at least one SRS resource set and information indicating at least one SRS resource can be indicated by one field of the DCI, or it can be indicated by multiple fields. Additionally, information indicating at least one SRS resource in each of the one or more SRS resource sets can be indicated by one field of the DCI, or it can be indicated by multiple fields.

[0232] At least one SRS resource in the first SRS resource set and / or the second SRS resource set can be indicated by the DCI. If the first SRS resource set and the second SRS resource set are indicated, the SRS resource instructions in each of the first SRS resource set and the second SRS resource set can be executed independently (or separately).

[0233] For example, when the DCI includes a first SRI field and a second SRI field, the first SRI field can indicate at least one SRS resource in the first SRS resource set, and the second SRI field can independently indicate at least one SRS resource in the second SRS resource set.

[0234] By executing SRS resource indication independently in each SRS resource set, the degrees of freedom in selecting the rank / precoder / beam of uplink transmissions sent to each TRP are increased, and thus scheduling flexibility can be increased.

[0235] Furthermore, the number of SRS resources indicated in each SRS resource set via DCI can be the same. Therefore, the rank of the first uplink transmission associated with the first SRS resource set and the rank of the second uplink transmission associated with the second SRS resource set can be the same. Here, rank can represent the number of layers or the number of antenna ports. If all SRS resources included in each SRS resource set (i.e., SRS resource candidates) are 1-port SRS resources, the indicated number of SRS resources can correspond to the rank value, the number of layers, or the number of antenna ports.

[0236] In other words, when the first SRS resource set and the second SRS resource set are indicated by DCI, at least one of the number of SRS resources indicated in the first SRS resource set, the number of uplink transmission layers associated with the first SRS resource set, or the number of uplink transmission antenna ports associated with the first SRS resource set can be equal to at least one of the number of SRS resources indicated in the second SRS resource set, the number of uplink transmission layers associated with the second SRS resource set, or the number of uplink transmission antenna ports associated with the second SRS resource set.

[0237] In step S830, the UE can perform uplink transmission based on the indicated SRS resources.

[0238] When the first SRS resource set and the second SRS resource set are indicated by the DCI, the UE can transmit uplink through TPR 1 corresponding to the first SRS resource set, and can perform uplink transmission through TRP 2 corresponding to the second SRS resource set. That is, when multiple SRS resource sets are indicated by the DCI, the UE can perform uplink transmission operation (i.e., MTRP transmission operation) for each TRP based on the SRS resources indicated in the indicated SRS resource set.

[0239] For example, when M SRS resources are indicated in the first SRS resource set and M SRS resources are indicated in the second SRS resource set via DCI, the UE can send an uplink to TRP 1 based on the M SRS resources indicated in the first SRS resource set, and can send an uplink to TRP 2 based on the M SRS resources indicated in the second SRS resource set. Here, when all SRS resources included in the first and second SRS resource sets (i.e., SRS resource candidates) are 1-port SRS resources, the rank, number of layers, and number of antenna ports of the uplink sent via TRP 1 and TRP 2 can be the same as M.

[0240] The UE may perform a first uplink transmission at at least one first transmission time (TO). Furthermore, the UE may perform a second uplink transmission at at least one second TO.

[0241] Furthermore, when a first SRS resource set is indicated by the DCI and at least one SRS resource in the indicated first SRS resource set is indicated, the UE can send an uplink to TPR 1 based on at least one SRS resource indicated in the indicated first SRS resource set. And, when a second SRS resource set is indicated by the DCI and at least one SRS resource in the indicated second SRS resource set is indicated, the UE can send an uplink to TPR 2 based on at least one SRS resource indicated in the indicated second SRS resource set. In other words, when an SRS resource set is indicated by the DCI, the UE can perform a STRP transmission operation based on one indicated SRS resource set.

[0242] In the following text, reference will be made to Figure 9 Describes a method for a base station to perform uplink reception based on one or more SRS resource sets.

[0243] Figure 9 This is a flowchart illustrating an uplink receiving method for a base station in a wireless communication system to which the present disclosure can be applied.

[0244] In step 910, the base station may send configuration information related to multiple SRS resource sets to the UE.

[0245] Configuration information associated with multiple SRS resource sets may include information for configuring each use of the multiple SRS resource sets as a codebook, non-codebook, or for other purposes (e.g., beam management, antenna switching, etc.). Additionally, information associated with multiple SRS resource sets may include information for configuring the SRS resource sets among the multiple SRS resource sets to be used for uplink transmission.

[0246] Additionally, it may further include information for configuring the same number of SRS resources included in the first SRS resource set and the second SRS resource set based on configuration information associated with multiple SRS resource sets.

[0247] In step 920, the base station may send a DCI indicating the SRS resource set or one or more of the SRS resources to the terminal.

[0248] Specifically, the base station may send a DCI to the UE including information indicating a first SRS resource set, a second SRS resource set, or at least one of the first and second SRS resource sets. Additionally, the DCI may also include information indicating at least one SRS resource in each of the indicated one or more SRS resource sets. For example, the information indicating one or more SRS resource sets and the information indicating one or more SRS resources may be indicated by one field in the DCI, or by multiple fields. Furthermore, the information indicating one or more SRS resources in each of the one or more SRS resource sets may be indicated by one field in the DCI, or by multiple fields.

[0249] Furthermore, the number of SRS resources indicated in each SRS resource set via DCI can be the same. Therefore, the rank of the first uplink transmission associated with the first SRS resource set and the rank of the second uplink transmission associated with the second SRS resource set can be the same. Here, rank can represent the number of layers or the number of antenna ports. If all SRS resources included in each SRS resource set (i.e., SRS resource candidates) are 1-port SRS resources, the indicated number of SRS resources can correspond to the rank value, the number of layers, or the number of antenna ports.

[0250] In step 930, the base station can receive uplinks sent from the UE based on the indicated SRS resources.

[0251] When a first SRS resource set and a second SRS resource set are indicated via DCI, TRP 1 corresponding to the first SRS resource set and TRP 2 corresponding to the second SRS resource set can receive uplink from the UE. Specifically, TRP 1 can perform an uplink reception operation based on at least one SRS resource indicated in the first SRS resource set, and TRP 2 can perform an uplink reception operation based on at least one SRS resource indicated in the second SRS resource set. That is, when multiple SRS resource sets are indicated by DCI, multiple TRPs can receive uplink from the UE based on the SRS resources indicated in the indicated SRS resource sets (i.e., MTRP reception operation).

[0252] Furthermore, when a first SRS resource set is indicated via DCI and at least one SRS resource in the first SRS resource set is indicated, TRP 1 corresponding to the first SRS resource set can receive uplink from the UE based on the SRS resources indicated in the first SRS resource set. Similarly, when a second SRS resource set is indicated via DCI and at least one SRS resource in the second SRS resource set is indicated, TRP 2 corresponding to the second SRS resource set can receive uplink from the UE based on the SRS resources indicated in the second SRS resource set. In other words, when an SRS resource set is indicated by DCI, the TRP corresponding to the indicated SRS resource set can receive uplink from the UE based on the SRS resources indicated in the indicated SRS resource set (i.e., STRP receive operation).

[0253] The following describes a specific example of uplink transmission based on a configuration of multiple SRS resource sets according to this disclosure.

[0254] First, a method for configuring SRS resources in an SRS resource set based on an SRS resource set will be described.

[0255] In methods for determining the precoder used for uplink transmission (e.g., PUSCH transmission), in the case of a non-codebook-based method, N 1-port resources (e.g., N < 5) in an SRS resource set can be configured for the UE. The UE can indicate the precoder using the SRS Resource Indicator (SRI) field of the DCI by one or more Lmax or fewer SRS resources in the SRS resource set.

[0256] Therefore, the size of the SRI field can be determined as shown in Equation 3 below. In Equation 3, C(N,i) represents the number of cases where i items out of N items are selected regardless of order.

[0257] [Formula 3]

[0258]

[0259] The number of SRS resources indicated by the SRI field is the same as the PUSCH rank, and the UE can use the precoder / beamformer applied to the indicated SRS resources as the precoder / beamformer for PUSCH transmission.

[0260] When 'txConfig' (which is a higher-level parameter) is 'nonCodebook', the number of bits for SRI can be determined as shown in Equation 4 below.

[0261] [Formula 4]

[0262]

[0263] In Equation 4, N SRS It is the number of SRS resource sets in the SRS resource set configured by the upper-level parameter 'srs-ResourceSetToAddModList', and can be associated with 'nonCodebook' as the value of the upper-level parameter 'usage'.

[0264] If the UE supports the use of 'maxMIMO-Layers' and the upper-layer parameter 'maxMIMO-Layers of PUSCH-ServingCellConfig' of the serving cell is set, then Lmax can be determined by the corresponding parameter. Otherwise, Lmax can be determined by the maximum number of PUSCH layers supported by the UE for non-codebook-based operations on the serving cell.

[0265] When 'txConfig' (which is a higher-level parameter) is 'Codebook', the number of bits for SRI can be determined as shown in Equation 5 below.

[0266] [Formula 5]

[0267]

[0268] In Equation 5, N SRS It is the number of SRS resource sets in the SRS resource set configured by the higher-level parameter 'srs-ResourceSetToAddModList', and can be associated with 'Codebook' as the value of the higher-level parameter 'usage'.

[0269] When an SRS resource set is configured for UE to perform uplink transmission (e.g., PUSCH transmission), it may only support uplink transmission for STRP. Therefore, multiple SRS resource sets for uplink transmission for MTRP need to be configured for UE.

[0270] In the following sections, specific examples of this disclosure relating to the configuration of multiple SRS resource sets will be described.

[0271] Implementation Method 1

[0272] Since the uplink channel between the UE and each TRP is different in the MTRP PUSCH transmission method, it should be able to support an independent (e.g., different) precoder for PUSCH transmission for each TRP. That is, in a non-codebook-based transmission method, a method for instructing the precoder of the MTRP PUSCH is required.

[0273] Method 1 uses the existing non-codebook-based transmission method itself, but in the DCI, it indicates the precoder to be applied to the PUSCH pointing to each TRP.

[0274] Specifically, if we assume that the PUSCH is sent using two TRPs, the SRI field of the DCI can be extended to 2. If the PUSCH is sent using K TRPs, the number of SRI fields can be extended to K or less.

[0275] When the SRI field is expanded to 2, the size of each SRI field can be determined as follows: and Each SRI field can be used to indicate SRS resources from different SRS resource sets. For example, each of SRS resource sets 0 and 1 can be configured for precoder indication of TRP 1 and TRP 2, and each of SRI fields 0 and 1 can select SRS resources within SRS resource sets 0 and 1. That is, the SRS resource set for each TRP can be configured as shown in Table 6 below, and the size of the SRI field in the DCI increases to...

[0276] [Table 7]

[0277] SRS resource set 0 for TRP 0 SRS resource set 1 for TRP 1 SRS Resource 0 SRS Resource 0 SRS Resource 1 SRS Resource 1 ... ... SRS Resource N-1 SRS Resource M-1

[0278] According to Method 1, each SRI field in the multiple SRI fields can independently (or separately) indicate an SRS resource set and one or more SRS resources within the corresponding SRS resource set. Therefore, uplink transmission flexibility can be increased. On the other hand, the signaling overhead for scheduling uplink transmissions (e.g., DCI payload) can be increased. Method 2 is a method where only one SRI field exists in the DCI, as in existing methods, and the SRI values ​​indicated in the SRI fields are jointly applied to SRS resource sets 0 and 1. To determine the SRI field size, after setting Lmax 0 and Lmax 1 to the same value, the SRI field size can be determined based on Lmax 0 or Lmax 1. Alternatively, when Lmax 0 and Lmax 1 are different, the SRI field size of the DCI can be determined based on the minimum / maximum value among Lmax 0 and Lmax 1.

[0279] For example, when the SRI field, whose size is determined in the manner described above, indicates the second SRS resource in each of the SRS resource sets 0 and 1, the precoder can be applied to the PUSCH TO of TRP 0 using the second SRS resource in SRS resource set 0, and the precoder can be applied to the PUSCH TO of TRP 1 using the second SRS resource in SRS resource set 1. That is, there is a pairing between the SRS resources of TRP 0 and the SRS resources of TRP 1, and a specific pair can be indicated by the SRI field.

[0280] However, in Method 2, since the precoders for the two TRPs cannot be selected independently, it is impossible to apply the optimized precoder to the uplink channel of each TRP. On the other hand, in Method 2, it is possible to reduce the signaling overhead used to indicate multiple precoders (e.g., to minimize the increase in DCI payload).

[0281] Implementation Method 2

[0282] This embodiment relates to a method for configuring an SRI field that jointly indicates SRS resources of multiple TRPs in order to indicate a precoder for non-codebook-based MTRP PUSCH transmissions. In other words, this embodiment relates to a method for independently (or separately) selecting multiple sets of SRS resources within a single SRI field.

[0283] If N SRS resources are configured in SRS resource set 0, then to determine the rank L0 precoder, the following applies: L0 resources are selected from the N SRS resources (regardless of order), and a rank of 1 or greater and Lmax0 or less must be chosen. Conversely, when M SRS resources are configured in SRS resource set 1, to determine the rank L1 precoder, the following applies: L1 resources are selected from the M SRS resources (regardless of order), and a rank of 1 or greater and Lmax1 or less must be chosen. In this case, since SRS resources must be selected independently from both SRS resource sets, the SRI field size is determined as shown in Equation 6 below.

[0284] [Formula 6]

[0285]

[0286] When the joint SRI field is configured in this way, although the DCI payload is greater than the method of setting SRS resources in the SRS resource set for each of the two SRI fields, scheduling flexibility can be increased due to the high degree of freedom in selecting the rank / precoder / beamformer of the uplink transmission (e.g., PUSCH transmission) sent via TRP.

[0287] Additionally or alternatively, to further reduce the DCI payload, a specific transmission method (i.e., restriction) can be configured when indicating / selecting resources in each SRS resource set in SRS resource set 0, 1. This restriction can be applied to examples of combined SRI fields, and also to examples of multiple SRI fields.

[0288] For example, when indicating at least one SRS resource in each of one or more SRS resource sets via at least one field in the DCI, when indicating multiple SRS resource sets, the rank (or the number of SRS resources indicated when assuming 1-port SRS resources) of the multiple SRS resource sets can be restricted to the same.

[0289] Additionally, when indicating at least one SRS resource in each of one or more SRS resource sets through at least one field in the DCI, the used or unused SRS resource sets among multiple pre-configured SRS resource sets can be indicated. Alternatively, the number of used SRS resource sets (or the number of TRPs) or the number of unused SRS resource sets among multiple pre-configured SRS resource sets can be indicated through one or more fields in the DCI.

[0290] More specific examples are as follows.

[0291] The first transmission method (i.e., the first limiting method) is a method in which the rank of the PUSCH sent in each TRP is set / limited equally. That is, the same number of SRS resources can be indicated / selected in each of the SRS resource set 0 and the SRS resource set 1, and the same number of SRS resources can be configured / limited as in Equation 7 below.

[0292] [Formula 7]

[0293] Set A={(i,j)|(i,j)=(1,1),(2,2),…,(min(Lmax0,Lmax1),min(Lmax0,Lmax1))}

[0294] When the rank of the PUSCH transmitted through each TRP is constrained as in the first transmission method, the size of the SRI field decreases as the (i, j) combination is constrained to set A. In the case of non-codebook-based MTRP PUSCH transmission, the base station and UE can reduce DCI overhead by applying the first transmission method.

[0295] The second transmission method (i.e., the second restriction method) is a method of configuring / restricting the rank of TRP 1 to 0. That is, the second transmission method is a method of performing PUSCH transmission for TRP 0 without indicating / selecting SRS resources in SRS resource set 0, and performing PUSCH transmission only for TRP 1 by indicating / selecting SRS resources in SRS resource set 1. The second transmission method can be configured / restricted as shown in Equation 8 below.

[0296] [Formula 8]

[0297] Set B = {(i,j)|(i,j) = (0,1),(0,2),…,(0,Lmax1)}

[0298] The third transmission method (i.e., the third restriction method) is a method of setting / restricting the rank of TRP 0 to 0. In other words, the third transmission method is a method of performing PUSCH transmission solely using TRP 0 by indicating / selecting SRS resources in SRS resource set 0 without performing PUSCH transmission in TRP 1, without indicating / selecting SRS resources in SRS resource set 1. The third transmission method can be configured / restricted as shown in Equation 9 below.

[0299] [Formula 9]

[0300] Set C = {(i,j)|(i,j) = (1,0),(2,0),…,(Lmax0,0)}

[0301] The second or third transmission method involves sending PUSCH in a specific TRP and not sending PUSCH for the remaining TRPs by limiting / configuring the rank to 0. For example, the specific TRP through which PUSCH is sent can be dynamically indicated / determined based on channel quality. Alternatively, for example, based on an index associated with each TRP (e.g., CORESETpoolindex, etc.), the TRP corresponding to the minimum / maximum index can be selected. For example, when j = 0, the TRP corresponding to CORESET pool index 0 is selected, and the PUSCH transmission operation can be performed based on the uplink power control parameters, path loss (PL) reference signal, spatial relationship reference signal, QCL reference signal, etc., of the corresponding TRP. Furthermore, when i = 0, the TRP corresponding to CORESETpoolindex 1 is selected, and the PUSCH transmission operation can be performed based on the uplink power control parameters, path loss reference signal, spatial relationship reference signal, QCL reference signal, etc., of the corresponding TRP. Alternatively, in addition to CORESETpoolindex, the uplink power control parameters, path loss reference signals, spatial relationship reference signals, QCL reference signals, etc. to be used when j=0 and the uplink power control parameters, path loss reference signals, spatial relationship reference signals, QCL reference signals, etc. to be used when i=0 can be configured separately.

[0302] The base station can select at least one of the transmission methods (or restriction methods) and instruct the UE. However, when the transmission method is dynamically indicated, the size of the DCI can be dynamically changed. As a result, the number of blind detections of the UE's PDCCH increases, and therefore, the implementation complexity of the UE may increase. Therefore, the indication of the transmission method can be semi-statically indicated through RRC / MAC-CE signaling, etc.

[0303] For example, a base station can indicate A or B or C or A∪B or A∪C or B∪C or A∪B∪C. Here, it is assumed that A corresponds to the first transmission method described above, B corresponds to the second transmission method described above, and C corresponds to the third transmission method described above.

[0304] When indicated by A, the UE can perform MTRP PUSCH transmission operations under rank-restricted conditions.

[0305] When indicated by B or C, the UE can perform existing STRP PUSCH transmission operations.

[0306] When A∪B or A∪C is indicated, STRP PUSCH and MTRP PUSCH can be dynamically switched via the SRI field.

[0307] When B∪C is indicated, it is limited to STRP PUSCH, but the receiving point can be dynamically selected (point selection). That is, similar to downlink point selection, uplink transmission operations can be performed by dynamically selecting the received TRP based on the channel conditions in the uplink.

[0308] When A∪B∪C is indicated, the STRP PUSCH and MTRP PUSCH can be dynamically switched, and the receiving TRP for the STRP PUSCH can be dynamically indicated. For example, whether uplink transmission is for STRP or MTRP (or the number of TRPs or the number of SRS resource sets) can be dynamically indicated through one or more fields in the DCI. Additionally, one or more fields in the DCI can dynamically indicate uplink transmission for one or more TRPs (or based on one or more SRS resource sets). Furthermore, one or more fields in the DCI can dynamically indicate on which beam (or which SRS resource) (or within the indicated one or more SRS resource sets) uplink transmission is performed using one or more indicated TRPs.

[0309] For simpler signaling, the UE may additionally expect the base station to configure N=M and / or Lmax0=Lmax1.

[0310] Furthermore, the base station can freely define each code point of the SRI field as an SRS resource for a single SRS resource set or for multiple SRS resource sets via RRC / MAC-CE signaling. For example, as shown in Table 8 below, it can be configured for four code points that can be configured as a 2-bit SRI field.

[0311] [Table 8]

[0312]

[0313] When a code point (e.g., code point 00 or 01) is specified for configuring SRS resources for a single SRS resource set, STRP transmission can be performed using the precoder / beamforming corresponding to the SRS. When a code point (e.g., code point 10 or 11) is specified for configuring SRS resources for two (or more) SRS resource sets, the precoder / beamforming corresponding to the SRS is alternated for multiple PUSCH TOs. MTRP transmission can be performed by applying it during movement. In the examples disclosed in Table 8, for ease of explanation, it is assumed that the maximum value of two SRS resources is specified, but N SRS resources can be specified. In this case, N precoder / beamforming can be applied alternately to N PUSCH TOs or N or more PUSCH TOs. The same method can be applied even when a UL TCI field is introduced instead of an SRI field (applicable to both codebook-based and non-codebook-based methods). STRP UL transmission or MTRP UL transmission can be determined based on the presence of one or more SRS resource sets, SRS resources, or spatial relationships RS indicated in each UL TCI code point. For example, in the case of MTRP UL transmission (e.g., when multiple SRS resource sets / SRS resources / spatially related RSs are indicated based on each UL TCI code point), the precoders / beams of the multiple indicated SRS / spatially related RSs can be alternately applied to multiple PUSCH TOs to perform MTRP UL transmission operations.

[0314] Implementation Method 3

[0315] This implementation relates to a method for configuring the SRI field to indicate a precoder for codebook-based PUSCH transmissions.

[0316] In existing codebook-based PUSCH transmission methods, the rank / precoding matrix indicator (PMI) is indicated via the Transport Precoding Matrix Indicator (TPMI) field of the DCI. Additionally, one SRS resource from a set of 2 (4) SRS resources defined within an SRS resource set is selected via the 1 ( / 2) bit SRI field of the DCI. Furthermore, the UE can perform UL PUSCH transmission by applying the PMI indicated via the TPMI field to the port of the selected SRS resource. A specific uplink beam (e.g., an analog beam) is also applied to the port of the SRS resource. In this way, the UE can generate the final precoder by applying the PMI to the port where the specific uplink beam is applied. Since the uplink channel between the UE and each TRP is different in the MTRP PUSCH transmission method, an independent (e.g., different) precoder and SRS resource indication scheme are required for the PUSCH transmission of each TRP.

[0317] The base station can distinguish between precoders for PUSCH TO to be used for TRP 0 and precoders for PUSCH TO to be used for TRP 1 for the UE using any precoder indication method, and can instruct the UE accordingly. Specific examples of SRS resources used to indicate the PUSCH TO to be applied in each TRP will be described below.

[0318] As a first approach, the SRI field can be extended to multiple fields (e.g., two). For example, a first SRI field can be used to indicate the SRS resources in SRS resource set 0 to be applied to the PUSCH TO in TRP 0, and a second SRI field can be used to indicate the SRS resources in SRS resource set 1 to be applied to the PUSCH TO in TRP 1. This increases the flexibility of uplink transmission. On the other hand, it increases the signaling overhead (e.g., DCI payload) for scheduling uplink transmissions.

[0319] As a second method, only one SRI field exists (e.g., the same size as in existing methods), but the SRI value indicated by the SRI field can be applied jointly to SRS resource set 0 and SRS resource set 1. That is, when the SRI value is 0, a first SRS resource is selected from each of SRS resource set 0 and SRS resource set 1, and when the SRI value is 1, a second SRS resource from each of SRS resource set 0 and SRS resource set 1 can be selected. In other words, there is a pairing between the SRS resources of TRP 0 and the SRS resources of TRP 1, and a specific pair can be indicated by the SRI field. However, in the case of the second method, since the SRS resources for PUSCH transmission for each TRP cannot be independently indicated / selected, uplink channel-optimized precoder / beamforming for each TRP cannot be applied. On the other hand, in the case of method 2, the signaling overhead for indicating multiple precoders can be reduced (e.g., minimizing the increase in DCI payload).

[0320] As a third method, only one SRI field exists (with the same size as existing methods), but an SRS resource can be selected from a set of SRS resources by specifying a 1-bit SRI value. If two SRS resources exist in the set, the selected SRS resource can be applied to the PUSCH TO of TRP 0, and the unselected SRS resource can be applied to the PUSCH TO of TRP 1. Alternatively, the selected SRS resource can be applied to the PUSCH TO of TRP 1, and the unselected SRS resource can be applied to the PUSCH TO of TRP 0.

[0321] As a fourth method, only one SRI field exists (as in existing methods), but an SRS resource can be selected from a set of SRS resources by the indicated n-bit SRI value. The UE can assume that the set of SRS resources, besides the selected SRS resource, is indicated by the remaining SRS resources. That is, the remaining SRS resources, besides the SRS resource selected as the SRI, can be applied sequentially to PUSCH TO in a cyclical manner. For example, four SRS resources 0, 1, 2, and 3 are configured in the SRS resource set, and when SRS resource 0 is selected by the SRI field, SRS resource 0 is not applied to PUSCH TO, and the unselected SRS resources 1, 2, and 3 can be applied to PUSCH TO in a sequential, alternating manner.

[0322] As a fifth method, only one SRI field exists (as in existing methods), but an SRS resource can be selected from a set of SRS resources using the indicated n-bit SRI value. Multiple PUSCH TOs configured for MTRP PUSCH transmissions can be divided into a main PUSCH TO and a secondary PUSCH TO. In the main PUSCH TO, non-codebook-based precoding can be performed using the SRS resource indicated by the SRI. In the secondary PUSCH TO, precoding can be performed by sequentially applying the remaining SRS resources (excluding the SRS indicated by the SRI) in a cyclic manner. For example, if four SRS resources 0, 1, 2, and 3 are configured in the SRS resource set and SRS resource 0 is selected via the SRI field, non-codebook-based precoding using resource 0 is performed in the main PUSCH TO, and in the secondary PUSCH TO, precoding can be performed sequentially (e.g., 1, 2, 3, 1, 2, ...) using the unselected SRS resources 1, 2, and 3 in a cyclic manner.

[0323] Furthermore, for example, a primary TO can be defined as a TO of TRP 0, and a secondary TO can be defined as a TO of TRP 1, and the rank value indicated by the primary TO (e.g., rank 1) can also be applied to the secondary TO. In this case, the SRS resources to be used to generate a precoder in the secondary TO can be determined as a combination that can be generated by selecting one of the SRS resources not indicated by the SRI field. For example, suppose four SRS resources are configured for a set of SRS resources, and rank 2 is indicated by selecting SRS resources 0 and 1 via the SRI field. In this case, a precoder can be generated in the primary TO using SRS resources 0 and 1, and a rank 2 precoder can be generated in the secondary TO using SRS resources 2 and 3. When a primary TO and secondary TO are configured in multiple PUSCH TOs, the base station can select one of at least one modes and instruct the UE.

[0324] Implementation Method 4

[0325] This embodiment relates to a method for selecting SRS resources for MTRP PUSCH transmission. In this specification, it is assumed that multiple SRS resource sets defined in Rel-15 / 16 are configured to distinguish the SRS resources used in each TRP, and that the SRS resources in each SRS resource set are used in the same TRP. In another method, SRS group 0 and SRS group 1 can be configured for the UE for each SRS resource packet used by each TRP in an SRS resource set. In this case, SRS resource set 0 and SRS resource set 1 used in each TRP as described in this specification can be replaced by SRS group 0 and SRS group 1, respectively. That is, multiple SRS resource groups (or subsets of SRS resources) can exist in one SRS resource set, and each group (or subset) can correspond to a different TRP. In this case, since the SRS resources used for two different TRPs exist in the SRS resource set, the base station can configure different associated CSI-RS for SRS resources defined in the same set.

[0326] According to the current Rel-16 NR specification, there exists an associated CSI-RS within an SRS resource set. Therefore, all SRS resources in an SRS resource set are associated with the same CSI-RS. In other words, the associated CSI-RS can be indicated / configured as "the ID of the CSI-RS resource associated with this SRS resource set in non-codebook-based operations".

[0327] To remove the aforementioned limitations, in this embodiment, N associated CSI-RSs corresponding to N (e.g., N=2) TRPs in the SRS resource set can be configured. For example, N associated CSI-RSs in the SRS resource set can be configured. For example, multiple pairs can be configured / indicated when associated CSI-RS IDs and SRS groups / subsets are paired.

[0328] In this scenario, if m SRS resources indicated by the base station via DCI (one or more SRI fields) are associated with the same associated CSI-RS, a PUSCH transmission can be performed for a single TRP with rank m. Additionally, m1 of the m SRS resources can be associated with the same associated CSI-RS, and the remaining m2 SRS resources can be associated with another identical associated CSI-RS. In this case, the UE can perform an MTRPPUSCH transmission with rank m1 for TRP 1, sending multiple PUSCH TOs, and perform a PUSCH transmission with rank m2 for TRP 2.

[0329] For example, SRS resources #0, #1, #2, and #3 can be connected to associated CSI-RS resource #0, and SRS resources #4, #5, #6, and #7 can be connected to associated CSI-RS resource #1. SRS resources #0, #1, #2, #3, #4, #5, #6, #7, and #8 defined in an SRS resource set can be implicitly partitioned into TRPs, and the rank and precoder to be applied to each TO can be determined using the SRS indicated by the associated CSI-RS through the SRI field and the SRS. If the SRI indicated by the DCI is 0, 2, or 5, then in odd-numbered TOs, the UE can use SRI = 0 or 2 belonging to associated CSI-RS resource #0 to perform uplink transmission operations with rank 2, and in even-numbered TOs, the UE can use SRI = 5 belonging to associated CSI-RS resource #1 to perform uplink transmission operations with rank 1.

[0330] Implementation Method 5

[0331] This implementation relates to a method for applying the optimal SRI field for MTRP PUSCH (repeated) transmissions.

[0332] Two SRI fields can be introduced for MTRP PUSCH (repeated) transmission. The first SRI field can indicate the SRS resources of SRS resource set 0 and can be used to transmit PUSCH after the uplink channel for TRP 1 is optimized by indicating the power control parameters for TRP 1 defined by the RRC signal for each code point (e.g., path loss reference signal, closed-loop index, P0 value, α). The second SRI field can indicate the SRS resources of SRS resource set 1 and can be used to transmit PUSCH after the uplink channel for TRP 2 is optimized by indicating the power control parameters for TRP 2 defined by the RRC signal for each code point (e.g., path loss reference signal, closed-loop index, P0 value, α).

[0333] Implementation Method 5-1

[0334] This implementation relates to a method for reducing the SRI field size in non-codebook-based PUSCH transmissions by utilizing the same rank constraint.

[0335] In existing non-codebook-based PUSCH transmission schemes, the SRI field can be used to indicate the PUSCH rank. When sending an MTRP PUSCH, based on the principle of restricting the PUSCH rank pointing to each TRP to the same rank, the first SRI field can indicate the rank information in the same way as before. However, the method of reducing the field size by excluding the rank information in the second SRI field is under standardization discussion.

[0336] For example, if Lmax = 2 and two SRS resources are configured in each SRS resource set, the first SRI field can indicate SRS resource 0 or SRS resource 1 for rank 1 PUSCH in SRS resource set 0, or SRS resource 0 and SRS resource 1 for rank 2 PUSCH. Therefore, a total of three code points are used, and code points 0, 1, and 2 can indicate SRS resource 0 and SRS resource 1, and SRS resource 0 and SRS resource 1, respectively, and the size of the first SRI field is 2 bits. Furthermore, code point 3 is reserved because it is not used. When the first SRI field indicates rank 1, the second SRI field should indicate SRS resource 0 or SRS resource 1 in SRS resource set 1, and when the first SRI field indicates rank 2, it should indicate SRS resource 0 and SRS resource 1 in SRS resource set 1. Therefore, the size of the second SRI field can be determined as the maximum number of code points required for each rank. In the example above, since rank 1 requires 2 code points and rank 2 requires 1 code point, the size of the second SRI field is 1 bit.

[0337] Implementation Method 5-2

[0338] When two SRI fields are introduced, standardization is being discussed for the signaling method of dynamic switching between repeated MTRP PUSCH / STRP PUSCH transmissions. For example, a method of using reserved code points (in addition to reserved code points in the absence of reserved code points) for each SRI field can be discussed. When a reserved code point is indicated, the corresponding SRI field is not used; therefore, since PUSCH transmissions are not performed in the TRP corresponding to the corresponding SRI field (e.g., TRP2 when the second SRI field is indicated as a reserved code point), repeated STRP PUSCH transmissions can be performed.

[0339] Implementation Method 5-3

[0340] This implementation relates to a method for reducing the SRI field size by utilizing the same rank constraint (Implementation 5-1) and enabling dynamic switching between MTRP PUSCH, TRP 1(STRP)PUSCH and TRP 2(STRP)PUSCH (Implementation 5-2).

[0341] When simultaneously using the SRI field size reduction method with the same rank constraint described in Implementation 5-1 and the STRP / MTRP dynamic switching scheme using reserved code points described in Implementation 4-2, the following problem may occur. Since the second SRI field is defined using the rank value indicated by the first SRI field, if the PUSCH transmission of TRP 1 is disabled using the code points reserved in the first field, the rank value of the second field cannot be determined. Conversely, even if the PUSCH transmission of TRP 2 is disabled using the reserved code points in the second field, there is no problem in determining the rank value of the first SRI field, and it can operate without problems. Therefore, the reserved code points of the second SRI field can be used to send STRP PUSCH to TRP 1, but it is not possible to use the reserved code points of the first SRI field to send STRP PUSCH to TRP 2. Therefore, dynamic switching between MTRP PUSCH and TRP 1 PUSCH is possible, but dynamic switching between MTRP PUSCH and TRP 2 PUSCH may not be possible.

[0342] To address the aforementioned issues, two reserved code points are used in the second SRI field (or added if no reserved code point exists). The first reserved code point indicates a TRP 1PUSCH transmission, and the second reserved code point can be used to indicate a TRP 2PUSCH transmission. Specifically, when indicating TRP 1PUSCH, the first SRI field indicates an SRS resource in SRS resource set 0, and the value defined (mapped) in the first SRI field can also be applied to the PC parameter. On the other hand, when indicating TRP 2PUSCH, the first SRI field indicates an SRS resource in SRS resource set 1 instead of the previously defined SRS resource set 0, and the PC parameter defined (mapped) in the second SRI field is not the previously defined PC parameter. In other words, in the existing method, the first SRI field can be used to indicate the SRS resources of SRS resource set 0 and to indicate the PC parameters for TRP 1. However, in the method proposed in this embodiment, the first SRI field can be used to indicate the PC parameters for TRP 2 and to indicate the SRS resources of SRS resource set 1, depending on the value indicated by the second SRI field.

[0343] In the above proposal, the TRP 1PUSCH and TRP 2PUSCH indicators are indicated by a second SRI field, but this disclosure is not limited thereto, and the TRP 1PUSCH and TRP 2PUSCH indicators can be indicated by various DCI fields. For example, a new field can be introduced in the DCI used for the above operations, or if there is a reserved code point for another existing DCI field (e.g., a DMRS port indicator), it can be used to indicate the new field.

[0344] Alternatively, in the above embodiments, when a reserved code point is used for TRP selection, the reserved code point can be added / defined as a TRP selection code point instead of a reserved code point. Even if there is no reserved code point in the existing field, a TRP selection code point can be added / defined in the corresponding field used for TRP selection to perform the above operation.

[0345] Furthermore, while explaining this implementation, since excluding rank information and using reserved code points to indicate the second SRI field selected by the TRP, a method for determining whether to map the first SRI field to the SRS resource set and PC parameters of TRP 1 or to the SRS resource set and PC parameters of TRP 2 has been described. In this disclosure, even if a proposal applied to the second SRI field is applied to the first SRI field and a proposal applied to the first SRI field is applied to the second SRI field, the same effect that will be achieved in the above implementation can be expected.

[0346] Implementation Method 5-4

[0347] Whether to indicate MTRP or STRP can be specified using a new field defined in the DCI, instead of the SRI field used for dynamic MTRP / STRP switching, using only 1 bit. When indicating MTRP, the first and second SRI fields can be used to indicate the SRS resources and PC parameters for TRP 1 and TRP 2, respectively. When indicating STRP via the new field, the second SRI field may not be used to indicate SRS resources and PC parameters, but it can be used to indicate either TRP 1 or TRP 2. When indicating TRP 1 via the second SRI field, the SRS resources (i.e., SRS resources in SRS resource set 0) and PC parameters (i.e., PC parameters mapped to the first SRI field via RRC) for TRP 1 can be indicated using the first SRI field. Furthermore, when indicating TRP 2, the SRS resources (i.e., SRS resources in the second SRS resource set) and PC parameters (i.e., PC parameters mapped to the second SRI field via RRC using the first SRI field) for TRP 2 can be indicated.

[0348] In the above implementation, the number of SRS resources configured in each SRS resource set can be different. However, if the number of resources in SRS resource set 1 is greater than the number of SRS resources in SRS resource set 0, then when the resources of SRS resource set 1 are indicated through the first SRI field, not all SRS resource combinations can be indicated because the SRI field has insufficient code points; only some resource combinations can be indicated. To prevent this problem, the UE can expect that the number of SRS resources in each SRS resource set is always configured to be the same.

[0349] Figure 10 This is a diagram based on the present disclosure used to describe the signaling process between the network side and the UE.

[0350] Figure 10 Examples of signaling between the UE and the network side are provided, in which the examples described above in this disclosure (e.g., Embodiment 1 / Embodiment 2 / Embodiment 3 / Embodiment 4 / Embodiment 5-1 / Embodiment 5-2 / Embodiment 5-3 / Embodiment 5-4, etc.) can be applied. Here, the UE / network side is exemplary and can be understood by referring to... Figure 11 The various devices described are used as substitutes. Figure 10 This is for ease of description and does not limit the scope of this disclosure. Additionally, depending on the circumstances and / or configuration, etc., details may be omitted. Figure 10 Some steps are shown in the diagram. Additionally, in... Figure 10 In this context, the aforementioned uplink sending and receiving operations, MTRP-related operations, etc., can be referred to as or used for network-side / UE operations.

[0351] In the following description, the network side can be a base station comprising multiple TRPs, or a cell comprising multiple TRPs. Alternatively, the network side can include multiple RRHs (Remote Radio Headers) / RRUs (Remote Radio Units). For example, ideal / non-ideal backhaul can be configured between TRP 1 and TRP 2 constituting the network side. Furthermore, while the following description is based on multiple TRPs, it can be similarly extended and applied to transmissions through multiple panels / cells, and also to transmissions through multiple RRHs / RRUs, etc.

[0352] Furthermore, the following description is based on "TRP," but as mentioned above, "TRP" can be applied by replacing it with expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pec cell, etc.), TP (transmitting point), base station (gNB, etc.). As mentioned above, TRPs can be classified according to information about CORESET groups (or CORESET pools) (e.g., CORESET index, ID). For example, when a UE is configured to transmit and receive with multiple TRPs (or cells), it may mean that multiple CORESET groups (or CORESET pools) are configured for a terminal. Configuration of such CORESET groups (or CORESET pools) can be performed via higher-layer signaling (e.g., RRC signaling, etc.). Additionally, a base station can generally refer to the object that performs data transmission and reception with the terminal. For example, a base station can be a concept including at least one TP (transmitting point), at least one TRP (transmitting and receiving point), etc. Furthermore, TP and / or TRP can include the base station's panel, transmitting and receiving units, etc.

[0353] The UE can receive configuration information S105 from the network side via TRP 1 and / or TRP 2. The configuration information may include system information (SI), scheduling information, CSI-related configurations (e.g., CSI report configuration, CSI-RS resource configuration), etc. The configuration information may include information related to network-side configuration (i.e., TRP configuration), resource allocation information related to MTRP-based transmission and reception, etc. The configuration information can be sent through higher layers (e.g., RRC, MAC CE). Furthermore, when the configuration information is predefined or pre-configured, the corresponding stage can be omitted.

[0354] For example, in the method proposed above, the configuration information may include one or more of the following: SRS-related configuration (e.g., SRSresourceset / SRSresource, etc.), TO-related configuration / configuration information (e.g., the number of TOs / resource information constituting a TO, etc.), PUSCH repetitive transmission-related configuration, and rank information for each TO. For example, the configuration information may include reference signal (e.g., CSI-RS) related information for SRS spatial correlation / beamformer / precoder configuration.

[0355] For example, UE ( Figure 11 In the aforementioned stage S105, 100 or 200) are from the network side ( Figure 11 The operation of receiving configuration information (200 or 100) can be performed by Figure 11 The device implementation in [the document] (will be described later). For example, refer to [reference]. Figure 11 At least one processor 102 can control at least one transceiver 106 and / or at least one memory 104 to receive configuration information, and at least one transceiver 106 can receive configuration information from the network side.

[0356] The UE can transmit a reference signal S110 for UL transmission to the network side via TRP 1 and / or TRP 2. For example, the reference signal can be transmitted based on configuration information, and in this example, the reference signal can be an SRS. For example, another reference signal (e.g., CSI-RS) associated with the spatial relationship / beamformer / precoder to be applied to the reference signal can be configured based on the configuration information, and the reference signal (e.g., SRS) can be transmitted based on the spatial relationship / beamformer / precoder of the other reference signal (e.g., CSI-RS).

[0357] If the UE obtains the spatial parameters for uplink transmission directly from the network side based on the DL RS resources, the reference signal transmission (e.g., SRS) stage in stage S110 can be omitted. Therefore, it is not necessary to configure or define the association between the DL RS resources and the SRS resources for the UE.

[0358] For example, UE ( Figure 11 In the aforementioned stage S110, 100 or 200) are sent to the network side ( Figure 11 The operation of sending reference signals (200 or 100) can be performed by Figure 11 The device implementation in [the document] (will be described later). For example, refer to [reference]. Figure 11 At least one processor 102 can control at least one transceiver 106 and / or at least one memory 104 to transmit reference signals, and at least one transceiver 106 can transmit the reference signals to the network side.

[0359] The UE can receive control information S115 from the network side. In an example, the control information may include scheduling information / UL authorization for transmission of UL channels (e.g., PUCCH / PUSCH) / UL signals (e.g., SRS). For example, the control information may include information about at least one of the TCI status, QCL RS, and DMRS ports. The control information can be received via a control channel (e.g., PDCCH). In an example, the control information may be DCI. In an example, the control information can be configured according to DCI format 0-1 or DCI format 0-0.

[0360] For example, the UE may receive a DCI indicating a first SRS resource set, a second SRS resource set, or at least one of the first SRS resource set and the second SRS resource set. For example, the UE may receive a DCI indicating at least one SRS resource in the indicated at least one SRS resource set.

[0361] For example, UE ( Figure 11 In the aforementioned stage S115, 100 or 200) are from the network side ( Figure 11 The operation of receiving control information (200 or 100) can be performed by Figure 11 The device implementation in [the document] (will be described later). For example, refer to [reference]. Figure 11 At least one processor 102 can control at least one transceiver 106 and / or at least one memory 104 to receive control information, and at least one transceiver 106 can receive control information from the network side.

[0362] The UE can perform uplink transmission (e.g., UL data / signal transmission) S120 to the network side via TRP 1 and / or TRP 2. For example, UL data / signals can be transmitted via a UL channel (e.g., PUCCH / PUSCH). For example, UL data / signals can be transmitted based on the above suggestions (e.g., a combination of at least one of Embodiment 1, Embodiment 2, or detailed examples thereof).

[0363] For example, UE ( Figure 11 In the aforementioned stage S120, 100 or 200) are sent to the network side ( Figure 11 The operation of sending UL data / signals (in 200 or 100) can be performed by Figure 11 The device implementation in [the document] (will be described later). For example, refer to [reference]. Figure 11 At least one processor 102 can control at least one transceiver 106 and / or at least one memory 104 to transmit UL data / signals, and at least one transceiver 106 can transmit UL data / signals to the network side.

[0364] As described above, the network-side / UE operations (e.g., a combination of at least one of Embodiment 1, Embodiment 2, or detailed examples thereof) can be performed by means of devices (e.g., as described later) Figure 10 This can be achieved through devices in the network. For example, the UE may correspond to a first wireless device, and the network side may correspond to a second wireless device, and in some cases, the reverse may be considered.

[0365] For example, the aforementioned network-side / UE operations (e.g., a combination of at least one of Implementation 1, Implementation 2, or detailed examples thereof) can be performed by Figure 11 At least one processor (e.g., 102, 202) processes the above-described network-side / UE operations (e.g., a combination of at least one of Embodiment 1, Embodiment 2, or detailed examples thereof) and can be used to drive Figure 11 At least one processor (e.g., 102, 202) has its command / program form (e.g., instructions, executable code) stored in memory (e.g., ...). Figure 11 In at least one memory (e.g., 104, 204) in the memory.

[0366] The general apparatus disclosed herein can be used

[0367] Figure 11 This is a block diagram illustrating a wireless communication system according to an embodiment of the present disclosure.

[0368] Reference Figure 11 The first wireless device 100 and the second wireless device 200 can transmit and receive wireless signals through various radio access technologies (e.g., LTE, NR).

[0369] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may additionally include one or more transceivers 106 and / or one or more antennas 108. The processors 102 may control the memories 104 and / or the transceivers 106, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. For example, the processor 102 may transmit a wireless signal including the first information / signal via the transceivers 106 after generating first information / signal by processing information in the memories 104. Additionally, the processor 102 may receive a wireless signal including second information / signal via the transceivers 106, and then store information obtained through signal processing of the second information / signal in the memories 104. The memories 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memories 104 may store software code including commands for performing all or part of the processing controlled by the processor 102 or for executing the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). Transceiver 106 may be connected to processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used with an RF (radio frequency) unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0370] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may additionally include one or more transceivers 206 and / or one or more antennas 208. The processors 202 may control the memories 204 and / or the transceivers 206, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. For example, the processors 202 may generate third information / signals by processing information in the memories 204, and then transmit a wireless signal including the third information / signals via the transceivers 206. Additionally, the processors 202 may receive wireless signals including fourth information / signals via the transceivers 206, and then store information obtained through signal processing of the fourth information / signals in the memories 204. The memories 204 may be connected to the processors 202 and may store various information related to the operation of the processors 202. For example, the memories 204 may store software code including commands for performing all or part of the processing controlled by the processors 202 or for executing the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). Transceiver 206 may be connected to processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used with an RF unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0371] The hardware components of the wireless devices 100 and 200 will be described in more detail below. However, one or more protocol layers may be implemented by one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102 and 202 may generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. One or more processors 102, 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information, in accordance with the functions, processes, suggestions, and / or methods disclosed in this disclosure, to provide them to one or more transceivers 106, 206. One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206, and obtain PDUs, SDUs, messages, control information, data, or information, in accordance with the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure.

[0372] One or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application-Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field-Programmable Gate Arrays) may be included in one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, etc. Firmware or software configured to execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure may be included in one or more processors 102, 202, or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods and / or operation flowcharts included in this disclosure can be implemented using firmware or software in the form of codes, commands and / or command sets.

[0373] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, signals, messages, information, programs, code, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located internally and / or externally to one or more processors 102, 202. Furthermore, one or more memories 104, 204 may be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0374] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or operation flowcharts of this disclosure to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure from one or more other devices. For example, one or more transceivers 106, 206 can be connected to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure, via one or more antennas 108, 208. In this disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received wireless signals / channels, etc., from RF band signals into baseband signals for processing using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, wireless signals / channels, etc., processed using one or more processors 102, 202, from baseband signals into RF band signals. Therefore, one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0375] The above embodiments combine the elements and features of this disclosure in a predetermined form. Unless otherwise expressly stated, each element or feature should be considered optional. Each element or feature may be implemented without being combined with other elements or features. Furthermore, embodiments of this disclosure may include combinations of some elements and / or features. The order of operations described in embodiments of this disclosure may be changed. Some elements or features of one embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. Obviously, embodiments may include claims that are not explicitly referenced in the claims, or may be included as new claims after the application has been amended.

[0376] It will be apparent to those skilled in the art that this disclosure may be implemented in other specific forms without departing from its essential characteristics. Therefore, the above detailed description should not be construed as restrictive in every respect, but rather as illustrative. The scope of this disclosure should be determined by a reasonable interpretation of the appended claims, and all variations within the equivalent scope of this disclosure are included within its scope.

[0377] The scope of this disclosure includes software or machine-executable commands (e.g., operating systems, applications, firmware, programs, etc.) that operate in a device or computer according to methods of various embodiments, and non-transitory computer-readable media that cause software or commands to be stored and executable in a device or computer. Commands that can be used to program a processing system to perform the features described in this disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in this disclosure can be implemented by using a computer program product including such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, and may include non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory may optionally include one or more storage devices located remotely from the processor. The memory, or alternatively, the non-volatile memory devices in the memory include non-transitory computer-readable storage media. The features described in this disclosure can be stored in any machine-readable medium to control the hardware of a processing system and can be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using the results of embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0378] The wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may include narrowband Internet of Things (IoT) for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the aforementioned names. Additionally or alternatively, the wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (Enhanced Machine-Type Communication). For example, LTE-M technology may be implemented in at least any of various standards, including 1) LTE Cat 0; 2) LTE Cat M1; 3) LTE Cat M2; 4) LTE non-BL (non-bandwidth limited); 5) LTE-MTC; 6) LTE Machine-Type Communication; and / or 7) LTE M, etc., and is not limited to the aforementioned names. Additionally or alternatively, the wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may include at least any one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and are not limited to the aforementioned names. For example, ZigBee technology can generate PANs (Personal Area Networks) associated with small / low-power digital communication based on various standards (e.g., IEEE 802.15.4, etc.) and may be referred to by various names.

[0379] Industrial applicability

[0380] The method presented in this disclosure is primarily illustrated based on examples applied to 3GPP LTE / LTE-A and 5G systems, but it can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method performed by a user equipment (UE), the method comprising the following steps: Receive configuration information related to multiple sets of Sound Reference Signals (SRS) resources from the base station; The base station receives downlink control information (DCI), the DCI including first information indicating at least one of a first SRS resource set, a second SRS resource set, or the first SRS resource set and the second SRS resource set, and second information indicating at least one SRS resource in the indicated at least one SRS resource set; as well as Uplink retransmission is performed across K time slots based on at least one indicated SRS resource. The number of SRS resources included in the first SRS resource set and the second SRS resource set is the same.

2. The method according to claim 1, wherein, Based on the first SRS resource set and the second SRS resource set, as indicated by the DCI, the number of layers repeatedly transmitted on the first uplink associated with the first SRS resource set and the number of layers repeatedly transmitted on the second uplink associated with the second SRS resource set are the same.

3. The method according to claim 2, wherein, Configure an SRS port for each of at least one SRS resource in the first SRS resource set and the second SRS resource set.

4. The method according to claim 2, wherein, The first uplink retransmission associated with the first SRS resource set and the second uplink retransmission associated with the second SRS resource set are carried out in different time slots of the K time slots.

5. The method according to claim 1, wherein, Based on whether the first SRS resource set is indicated by the DCI or the second SRS resource set is not indicated by the DCI, the uplink retransmission is performed across the K time slots based on at least one indicated SRS resource in the first SRS resource set.

6. The method according to claim 1, wherein, Based on the second SRS resource set indicated by the DCI or the first SRS resource set not indicated by the DCI, the uplink retransmission is performed across the K time slots based on at least one indicated SRS resource in the second SRS resource set.

7. The method according to claim 1, wherein, The first SRS resource set corresponds to the first associated non-zero power NZP channel state information-reference signal CSI-RS resource, and The second SRS resource set corresponds to the second associated NZP CSI-RS resource.

8. The method according to claim 1, wherein, The uplink repeated transmission is based on non-codebook transmission or codebook-based transmission.

9. The method according to claim 1, wherein, The first information and the second information are indicated by different fields included in the DCI.

10. The method according to claim 1, wherein, The second information is indicated by the first field and the second field. The first field indicates at least one SRS resource in the first SRS resource set, and The second field indicates at least one SRS resource in the second SRS resource set.

11. The method according to claim 1, wherein, The uplink retransmission includes retransmission of the Physical Uplink Shared Channel (PUSCH).

12. A user equipment (UE), the UE comprising: At least one transceiver; as well as At least one processor, said at least one processor being connected to said at least one transceiver, The processor is configured as follows: The at least one transceiver receives configuration information related to multiple sets of Sound Reference Signals (SRS) resources from the base station; Downlink control information (DCI) is received from the base station via the at least one transceiver. The DCI includes first information indicating at least one of a first SRS resource set, a second SRS resource set, or both the first and second SRS resource sets, and second information indicating at least one SRS resource in the indicated at least one SRS resource set. Uplink retransmission is performed across K time slots based on at least one indicated SRS resource. The number of SRS resources included in the first SRS resource set and the second SRS resource set is the same.

13. A method performed by a base station, the method comprising the following steps: Send configuration information related to multiple Sounding Reference Signal (SRS) resource sets to the User Equipment (UE); Send downlink control information (DCI) to the UE. The DCI includes first information indicating at least one of a first SRS resource set, a second SRS resource set, or the first SRS resource set and the second SRS resource set, and second information indicating at least one SRS resource in the indicated at least one SRS resource set. as well as Uplink repeated reception across K time slots is performed based on at least one indicated SRS resource. The number of SRS resources included in the first SRS resource set and the second SRS resource set is the same.

Images