Method and apparatus for transmitting or receiving a PUSCH in a wireless communication system

Abstract

A method and apparatus for transmitting or receiving a PUSCH in a wireless communication system are disclosed. The method for transmitting a physical uplink shared channel (PUSCH) according to an embodiment of the present application can include the steps of receiving first configuration information related to a sounding reference signal (SRS) from a base station, receiving downlink control information (DCI) for PUSCH scheduling from the base station, and transmitting the PUSCH to the base station. Based on the first configuration information including information related to a plurality of SRS resource sets, the PUSCH is transmitted at N (N is a natural number) transmission occasions (TOs), and the DCI includes a plurality of SRS resource indicator (SRI) fields, the PUSCH can be transmitted at each TO based on an SRS resource in an SRS resource set identified by one SRI field among the plurality of SRI fields related to each TO.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to methods and apparatus for transmitting and receiving Physical Uplink Shared Channel (PUSCH) 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 these 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 have been investigated, including dual connectivity, massive MIMO, in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and device networking. Summary of the Invention

[0004] Technical issues

[0005] The technical problem of the present invention is to provide a method and apparatus for sending and receiving PUSCH.

[0006] Another technical problem of this disclosure is to provide a method and apparatus for transmitting and receiving SRS (Sound Reference Signal) and multiple PUSCH between a terminal and multiple TRPs (Transmit and Receive Points).

[0007] The technical objectives achieved through 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 from the following description.

[0008] Technical solution

[0009] A method for transmitting PUSCH (Physical Uplink Shared Channel) in a wireless communication system may include: receiving first configuration information related to a sounding reference signal (SRS) from a base station; receiving downlink control information (DCI) for PUSCH scheduling from the base station; and transmitting PUSCH to the base station. The first configuration information may include information about multiple SRS resource sets, the PUSCH of which may be transmitted in N (N is a natural number) transmission opportunities (TOs) and based on a DCI including multiple SRS resource indicator (SRI) fields, and the PUSCH for each TO may be transmitted based on SRS resources in the SRS resource set identified by one of the multiple SRI fields associated with each TO.

[0010] A terminal transmitting PUSCH (Physical Uplink Shared Channel) in a wireless communication system according to an additional aspect of this disclosure may include: at least one transceiver for transmitting and receiving wireless signals; and at least one processor for controlling the at least one transceiver. The at least one processor may be configured to receive first configuration information associated with a sounding reference signal (SRS) from a base station; receive downlink control information (DCI) for PUSCH scheduling from the base station; and transmit PUSCH to the base station based on the DCI. The first configuration information may include information about a plurality of SRS resource sets, which PUSCH may be transmitted in N (N is a natural number) transmission opportunities (TOs) and based on a DCI including a plurality of SRS resource indicator (SRI) fields, and may transmit PUSCH for each TO based on SRS resources in the SRS resource set identified by one of the plurality of SRI fields associated with each TO.

[0011] In at least one non-transitory computer-readable medium storing at least one instruction, one or more instructions executable by at least one processor can control a device transmitting a PUSCH (Physical Uplink Shared Channel) to receive first configuration information related to a sounding reference signal (SRS) from a base station; receive downlink control information (DCI) for PUSCH scheduling from the base station; and transmit the PUSCH to the base station based on the DCI. The first configuration information may include information about multiple SRS resource sets, the PUSCH may be transmitted in N (N is a natural number) transmission times (TOs) and based on a DCI including multiple SRS resource indicator (SRI) fields, and the PUSCH for each TO may be transmitted based on SRS resources in the SRS resource set identified by one of the multiple SRI fields associated with each TO.

[0012] In a processing apparatus configured to control a terminal for transmitting PUSCH (Physical Uplink Shared Channel) in a wireless communication system, the processing apparatus may include at least one processor; and at least one computer memory operatively connected to the at least one processor and storing instructions for performing operations based on execution by the at least one processor. The operations may include: receiving first configuration information associated with a sounding reference signal (SRS) from a base station; receiving downlink control information (DCI) for PUSCH scheduling from the base station; and transmitting PUSCH to the base station based on the DCI. The first configuration information may include information about multiple SRS resource sets, and PUSCH may be transmitted in N (N is a natural number) transmission opportunities (TOs) and based on a DCI including multiple SRS resource indicator (SRI) fields, wherein PUSCH for each TO may be transmitted based on SRS resources in the SRS resource set identified by one of the multiple SRI fields associated with each TO.

[0013] A method for receiving a PUSCH (Physical Uplink Shared Channel) in a wireless communication system may include: sending first configuration information relating to a sounding reference signal (SRS) to a terminal; sending downlink control information (DCI) for PUSCH scheduling to the terminal; and receiving the PUSCH from the terminal. The first configuration information may include information about multiple SRS resource sets, the PUSCH of which may be transmitted in N (N is a natural number) transmission opportunities (TOs) and based on a DCI including multiple SRS resource indicator (SRI) fields, and the PUSCH for each TO may be transmitted based on SRS resources in the SRS resource set identified by one of the multiple SRI fields associated with each TO.

[0014] A base station receiving a PUSCH (Physical Uplink Shared Channel) in a wireless communication system according to an additional aspect of this disclosure may include: at least one transceiver for transmitting and receiving wireless signals; and at least one processor for controlling the at least one transceiver. The at least one processor may be configured to transmit first configuration information related to a sounding reference signal (SRS) to a terminal; transmit downlink control information (DCI) for PUSCH scheduling to the terminal; and receive PUSCH from the terminal. The first configuration information may include information about multiple SRS resource sets, and the PUSCH may be transmitted in N (N is a natural number) transmission times (TOs) and based on a DCI including multiple SRS resource indicator (SRI) fields, and the PUSCH for each TO may be transmitted based on SRS resources in the SRS resource set identified by one of the multiple SRI fields associated with each TO.

[0015] Beneficial effects

[0016] According to embodiments of this disclosure, the reliability of data transmission and reception can be improved by sending and receiving multiple PUSCHs between multiple TRPs (transmitter-receiver points) and terminals.

[0017] Furthermore, according to embodiments of this disclosure, the reliability of data transmission and reception can be improved by sending multiple PUSCHs to multiple TRPs using a configuration of SRS resources / SRS resource sets configured according to each TRP.

[0018] Furthermore, according to embodiments of this disclosure, signaling overhead can be reduced by instructing information regarding the transmission and reception of multiple PUSCHs between multiple TRPs and the terminal via a single downlink control information.

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

[0020] The accompanying drawings, 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.

[0021] Figure 1 The diagram illustrates the structure of a wireless communication system to which this disclosure can be applied.

[0022] Figure 2 The diagram illustrates the frame structure applicable to wireless communication systems disclosed herein.

[0023] Figure 3 The diagram illustrates a resource grid that can be applied to a wireless communication system according to this disclosure.

[0024] Figure 4 The diagram illustrates physical resource blocks in a wireless communication system that can be applied according to this disclosure.

[0025] Figure 5 The diagram illustrates a time slot structure applicable to wireless communication systems according to this disclosure.

[0026] Figure 6 The diagram illustrates a physical channel used in a wireless communication system to which this disclosure can be applied, as well as general signal transmission and reception methods using that physical channel.

[0027] Figure 7 This is a diagram illustrating a multi-panel terminal that can be used in a wireless communication system according to the present disclosure.

[0028] Figure 8 The diagram illustrates a multi-TRP transmission method applicable to the wireless communication system disclosed herein.

[0029] Figure 9 This is a diagram illustrating the signaling process between a network and a terminal in a method for sending and receiving PUSCH according to an embodiment of the present disclosure.

[0030] Figure 10 This is a diagram illustrating the operation of a terminal for sending a PUSCH method according to an embodiment of the present disclosure.

[0031] Figure 11 This is a diagram illustrating the operation of a base station for transmitting a PUSCH method according to an embodiment of the present disclosure.

[0032] Figure 12 The figure shows a block diagram of a wireless communication system according to an embodiment of the present disclosure.

[0033] Figure 13 The illustration shows a vehicle device according to an embodiment of the present disclosure. Detailed Implementation

[0034] In the following, embodiments according to the present 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 the present disclosure and not to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the art will recognize that the present disclosure may be practiced without these specific details.

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

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

[0037] In this invention, 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.

[0038] 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 the embodiments and the appended claims, the singular forms are intended to include the plural forms 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”.

[0039] 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 a device (e.g., a base station) controlling the network and transmitting or receiving signals, or during the process of a terminal associated with the corresponding wireless network transmitting or receiving signals between the network or between the terminal.

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

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

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

[0043] 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 version 10 is referred to as LTE-A, and LTE technology in or after 3GPP TS 36.xxx version 13 is referred to as LTE-A pro. 3GPP NR refers to technology in or after TS 38.xxx version 15. 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 technology, 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.

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

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

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

[0047] -BM: Beam Management

[0048] -CQI: Channel Quality Indicator

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

[0050] -CSI: Channel State Information

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

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

[0053] -DMRS: Demodulation Reference Signal

[0054] -FDM: Frequency Division Multiplexing

[0055] -FFT: Fast Fourier Transform

[0056] -IFDMA: Interleaved Frequency Division Multiple Access

[0057] -IFFT: Inverse Fast Fourier Transform

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

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

[0060] -MAC: Media Access Control

[0061] -NZP: Non-zero power

[0062] -OFDM: Orthogonal Frequency Division Multiplexing

[0063] -PDCCH: Physical Downlink Control Channel

[0064] -PDSCH: Physical Downlink Shared Channel

[0065] -PMI: Precoding Matrix Indicator

[0066] -RE: Resource Elements

[0067] -RI: Rank indicator

[0068] -RRC: Radio Resource Control

[0069] -RSSI: Received Signal Strength Indicator

[0070] -Rx: Receive

[0071] -QCL: Quasi-co-addressable

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

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

[0074] -TDM: Time Division Multiplexing

[0075] -TRP: Sending and Receiving Point

[0076] -TRS: Tracking Reference Signal

[0077] -Tx: Send

[0078] -UE: User Equipment

[0079] -ZP: Zero Power

[0080] Overall System

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

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

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

[0084] Figure 1 The diagram illustrates the structure of a wireless communication system to which this disclosure can be applied.

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

[0086] Figure 2 The diagram illustrates a frame structure in a wireless communication system to which this disclosure can be applied.

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

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

[0089] [Table 1]

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

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

[0092] [Table 2]

[0093] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410MHz–7125MHz 15, 30, 60kHz FR2 24250MHz–52600MHz 60, 120, 240kHz

[0094] 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 i is 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 The duration. In this case, there may be one set of frames for the uplink and one set of frames for the downlink. Furthermore, the transmission in the i-th uplink frame from the terminal should begin T 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 beginning of the OFDM symbol n in the same subframe s μ N symb slot The start times are arranged chronologically. All terminals may not perform transmission and reception simultaneously, meaning that all OFDM symbols in either the downlink or uplink time slots may not be available. Table 3 shows the number of OFDM symbols (N) per time slot in a 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.

[0095] [Table 3]

[0096] μ <![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

[0097] [Table 4]

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

[0099] 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; 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. Regarding physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier portions, etc., can be considered. The physical resources that can be considered in an NR system will be described in detail below.

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

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

[0102] 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 a. k,l' (p) or a k,l' Furthermore, a resource block (RB) is defined as N in the frequency domain. sc RB = 12 consecutive subcarriers.

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

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

[0105] -absoluteFrequencyPointA represents the frequency location of point A, expressed in ARFCN (Absolute Radio Frequency Channel Number).

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

[0107] [Formula 1]

[0108]

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

[0110] [Equation 2]

[0111]

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

[0113] Figure 4 The diagram illustrates physical resource blocks in a wireless communication system to which this disclosure can be applied. Furthermore, Figure 5 The diagram illustrates a time slot structure in a wireless communication system to which this disclosure can be applied.

[0114] refer to Figure 4 and Figure 5 A time slot includes 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.

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

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

[0117] 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 in the frequency domain 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.

[0118] Figure 6 The illustration shows a physical channel used in a wireless communication system to which this disclosure can be applied, as well as general signal transmission and reception methods using the physical channel.

[0119] 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 / use of the information they send and receive.

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

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

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

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

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

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

[0126] [Table 5]

[0127]

[0128] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 can include resource information (e.g., UL / SUL (Supplemental UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), information related to transport blocks (TBs) (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., procedure 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. DCI format 0_0 is used to schedule PUSCHs within 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 and Coding Scheme Cell RNTI) and transmitted.

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

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

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

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

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

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

[0135] Multi-panel operation

[0136] The term "panel" as used in this disclosure can be interpreted / applied as "multiple (or at least) panels" or "groups of panels" (having similarities / common values ​​from the perspective of specific characteristics (e.g., timing advance (TA), power control parameters, etc.)). Alternatively, the term "panel" as used in this disclosure can be interpreted / applied as "multiple (or at least) antenna ports" or "multiple (or at least) uplink resources" or "groups of antenna ports" or "groups (or sets) of uplink resources" (having similarities / common values ​​from the perspective of specific characteristics (e.g., TA, power control parameters, etc.)). Alternatively, the term "panel" as used in this disclosure can be interpreted / applied as "multiple (or at least) beams" or "at least one group (or set) of beams" (having similarities / common values ​​from the perspective of specific characteristics (e.g., TA, power control parameters, etc.)). Alternatively, the term "panel" as used in this disclosure can be defined as a unit used for configuring transmit / receive beams in a terminal. For example, a "transmit panel" may generate multiple candidate transmit beams in a single panel, but can be defined as using only one beam for transmission at a specific time. In other words, each Tx panel can use only one transmission beam (spatial relation information RS) to transmit a specific uplink signal / channel. Furthermore, the term "panel" in this disclosure can refer to a "multiple (or at least one) antenna ports" or a "group of antenna ports" or an "uplink resource group (or set)" having common / similar uplink synchronization, and can be interpreted / applied as a generalized expression of "uplink synchronization unit (USU)". Additionally, the term "panel" in this disclosure can be interpreted / applied as a generalized expression of "uplink transmission entity (UTE)".

[0137] Additionally, "uplink resource (or resource group)" can be interpreted / applied as PUSCH / PUCCH / SRS / PRACH resource (or resource group (or set)). Furthermore, this interpretation / application can be reversed. Additionally, "antenna (or antenna port)" can refer to a physical or logical antenna (or antenna port) in this disclosure.

[0138] In other words, the term "panel" as used in this disclosure can be interpreted differently as "terminal antenna element group," "terminal antenna port group," "terminal logical antenna group," etc. Furthermore, various schemes can be considered regarding which physical / logical antennas or antenna ports will be combined and mapped to a single panel, taking into account factors such as the location / distance / correlation between antennas, RF configuration, and / or antenna (port) virtualization schemes. This mapping process may be modified depending on the terminal implementation. Additionally, the term "panel" as used in this disclosure can be interpreted / applied as "multiple panels" or "panel group" (possessing similarities from the perspective of specific characteristics).

[0139] The multi-panel structure will be described below.

[0140] Terminal modeling in high-frequency band implementations may involve installing multiple panels (e.g., configuring one or more antennas) (e.g., two bidirectional panels in 3GPP UE antenna modeling). Various forms can be considered when implementing multiple panels in such a terminal. The following description is based on terminals supporting multiple panels, but it can be extended and applied to base stations supporting multiple panels (e.g., TRPs). The subsequent descriptions related to multi-panel structures can be applied to the transmission and reception of signals and / or channels considering multiple panels as described in this disclosure.

[0141] Figure 7 This is a diagram illustrating a multi-panel terminal that can be used in a wireless communication system according to the present disclosure.

[0142] Figure 7 (a) This illustration shows an implementation of a multi-panel terminal based on an RF (radio frequency) switch, and Figure 7 (b) Illustration of an implementation of a multi-panel terminal based on RF (radio frequency) connection.

[0143] For example, it can be based on, such as Figure 7 This is achieved using the RF switch in (a). In this case, only one panel is temporarily activated, and it may not be possible to send a signal to change the active panel within a specific time (i.e., panel switching).

[0144] To implement multiple panels in different ways, they can be connected to RF chains separately, allowing each panel to be activated at any time, such as... Figure 7As shown in (b). In this case, the time for panel switching may be 0 or very short. Furthermore, depending on the model and power amplifier configuration, signals can be transmitted simultaneously by activating multiple panels at the same time (STxMP: simultaneous transmission across multiple panels).

[0145] For terminals with multiple panels, the radio channel states of each panel may differ, and furthermore, the RF / antenna configurations of each panel may differ, thus requiring a method for estimating the channel on a panel-by-pane basis. Specifically, a process is needed to measure uplink quality or manage uplink beams by transmitting one or more SRS resources for each panel separately, or to measure downlink quality or manage downlink beams for each panel by utilizing channel reciprocity. Here, multiple SRS resources can be SRS resources transmitted through different beams in a panel, or SRS resources repeatedly transmitted through the same beam. In the following text, for convenience, a set of SRS resources transmitted in the same panel (with specific usage parameters (e.g., beam management, antenna switching, codebook-based PUSCH, non-codebook-based PUSCH) and specific time-domain behavior (e.g., aperiodic, semi-persistent, or periodic)) can be referred to as an SRS resource group. For this SRS resource group, the SRS resource set configuration supported in the NR system version 15 can be utilized, or it can be configured individually by bundling one or more SRS resources (with the same time-domain behavior and usage).

[0146] For reference, in version 15, multiple SRS resource sets can only be configured when the usage is for beam management with the same usage and time-domain behavior. Furthermore, it is defined that simultaneous transmission between SRS resources configured within the same SRS resource set is not allowed, but simultaneous transmission between SRS resources belonging to different SRS resource sets is possible. Therefore, if panel implementation and simultaneous transmission of multiple panels are considered, such as... Figure 7 As shown in (b), the corresponding concept (SRS resource set) itself can match an SRS resource group. However, if we consider even... Figure 7 In the implementation of (a) (panel switching), SRS resource groups can be defined separately. In the example, this can be configured by assigning a specific ID to each SRS resource, so that resources with the same ID belong to the same SRS resource group, and resources with different IDs belong to different resource groups.

[0147] For example, assume that four SRS resource sets configured for BM usage (RRC parameter usage is configured as 'BeamManagement') are assigned to the UE. In the following text, for convenience, each will be referred to as SRS resource set A, B, C, and D. Furthermore, since the UE implements a total of four (Tx) panels, consider the scenario where SRS transmission is performed by assigning each set to one (Tx) panel.

[0148] [Table 6]

[0149]

[0150] In version 15 of the standard, such a UE implementation is more clearly supported by the following protocol. In other words, for a UE performing capability reporting for the values ​​reported in feature groups (FG) 2-30 in Table 6 (such as 7 or 8), a total of up to 4 SRS resource sets for BM can be configured (in terms of supported time-domain behavior), as shown in the right column of Table 6. As described above, an implementation method that maps a UE panel to each set to perform transmission can be applied. Here, when a 4-panel UE maps each panel to one SRS resource set for BM and transmits it, the number of configurable SRS resources for each set is itself supported by separate UE capability signaling. For example, assume 2 SRS resources are configured in each set. This can correspond to the "number of UL beams" that each panel can transmit. In other words, when implementing 4 panels, the UE can map 2 UL beams to 2 SRS resources configured according to each panel and transmit them. In this case, according to version 15 of the standard, one of the codebook-based (CB) or non-codebook-based (NCB) UL modes can be configured for the final UL PUSCH transmission schedule. In any case, only one SRS resource set configuration (with usage set to "CB-based UL" or "NCB-based UL") is supported in version 15 standard, that is, only one dedicated SRS resource set configuration (for PUSCH).

[0151] The multi-panel UE (MPUE) category will be described below.

[0152] Regarding the multi-panel operation described above, the following three MPUE categories can be considered. Specifically, the three MPUE categories are classified according to i) whether multiple panels can be activated, and / or ii) whether transmission using multiple panels is possible.

[0153] i) MPUE Category 1: In terminals implementing multiple panels, only one panel can be activated at a time. The panel switching / activation delay can be configured to [X] ms. In the example, the delay can be configured to be longer than the beam switching / activation delay and can be configured in symbols or time slots. MPUE Category 1 may correspond to MPUE-assumption 1 as described in standardized related documents (e.g., 3GPP protocols, Technical Report (TR) documents, and / or Technical Specification (TS) documents, etc.).

[0154] ii) MPUE Category 2: In terminals implementing multiple panels, multiple panels can be activated simultaneously. One or more panels can be used for transmission. In other words, transmission using panels can be performed simultaneously in the corresponding category. MPUE Category 2 may correspond to MPUE-assumption2 as described in standardized related documents (e.g., 3GPP protocol, TR document, and / or TS document, etc.).

[0155] iii) MPUE Category 3: In terminals implementing multiple panels, multiple panels can be activated at once, but only one panel can be used for transmission. MPUE Category 3 may correspond to MPUE-assumption 3 as described in standardization-related documents (e.g., 3GPP protocol, TR document, and / or TS document, etc.).

[0156] Regarding the multi-panel-based signal and / or channel transmission and reception proposed in this disclosure, at least one of the three MPUE categories mentioned above can be supported. In the example, in version 16, MPUE category 3 of the following three MPUE categories can be (selectively) supported.

[0157] Furthermore, information regarding MPUE categories can be predefined in specifications (i.e., standards). Alternatively, information regarding MPUE categories can be configured semi-statically and / or dynamically indicated based on system conditions (i.e., network aspects, terminal aspects). In this case, configurations / indications related to multi-panel-based signal and / or channel transmission and reception can be configured / indicated by taking MPUE categories into account.

[0158] The following section describes the configurations / instructions related to panel-specific send / receive operations.

[0159] Regarding multi-panel-based operation, it is possible to perform signal and / or channel transmission and reception in a panel-specific manner. Here, panel-specific can mean that signal and / or channel transmission and reception can be performed on a panel-by-pane basis. Panel-specific transmission and reception can be referred to as panel-selective transmission and reception.

[0160] Regarding panel-specific sending and receiving in a multi-panel-based operation proposed in this disclosure, a method using identification information (e.g., identifiers (IDs), indicators, etc.) configured and / or indicating which panel will be used for sending and receiving among one or more panels may be considered.

[0161] In the example, the panel ID can be used for panel-selective transmission of PUSCH, PUCCH, SRS, and / or PRACH among multiple active panels. The ID can be configured / defined based on at least one of the following four methods (options (Alts) 1, 2, 3, 4).

[0162] i) Option 1: The panel ID can be an SRS resource set ID.

[0163] In the example, when considering a) the aspect of simultaneously transmitting SRS resources of multiple SRS resource sets with the same time-domain behavior in the same BWP, b) the aspect of configuring power control parameters on a per-SRS resource set basis, and c) the aspect where the terminal can report up to four SRS resource sets (which may correspond to up to four panels) based on the supported time-domain behavior, it may be desirable to map each UETx panel to the SRS resource set configured in the terminal implementation. Additionally, Option 1 has the advantage that the SRS resource set associated with each panel can be used for both "codebook" and "non-codebook" PUSCH transmissions. Furthermore, for Option 1, multiple SRS resources belonging to multiple SRS resource sets can be selected by extending the SRI (SRS Resource Indicator) field of the DCI. Additionally, the SRI-to-SRS resource mapping table may need to be extended to include SRS resources across the entire SRS resource set.

[0164] ii) Option 2: The ID used for the panel can be an ID that is (directly) associated with the reference RS resource and / or the reference RS resource set.

[0165] iii) Option 3: The ID used for the panel can be an ID directly associated with the target RS resource (reference RS resource) and / or the reference RS resource set.

[0166] Option 3 offers the following advantages: it allows for easier control of the SRS resource set configured for a single UE Tx panel, and it allows the same panel identifier to be assigned to multiple SRS resource sets with different time-domain behaviors.

[0167] iv) Option 4: The ID used for the panel can be an ID that is separately configured into spatial relationship information (e.g., RRC_SpatialRelationInfo).

[0168] Option 4 could be a scheme that adds new information to represent the ID used for the panel. In this case, the advantage is that it is easier to control the configuration of the SRS resource set corresponding to a UE Tx panel, and the same panel identifier can be assigned to multiple SRS resource sets with different time-domain behaviors.

[0169] In this example, a similar approach to introducing UL TCI (Transmission Configuration Indication) could be considered, analogous to existing DL TCI. Specifically, the definition of the UL TCI state could include a list of reference RS resources (e.g., SRS, CSI-RS, and / or SSB). The current SRI field could be reused to select the UL TCI state from the set of configurations, or a new DCI field (e.g., a UL-TCI field) in DCI format 0_1 ​​could be defined for the appropriate purpose.

[0170] Information related to the transmission and reception of the specific panel (e.g., panel ID, etc.) can be transmitted via higher-layer signaling (e.g., RRC messages, MAC-CE, etc.) and / or lower-layer signaling (e.g., Layer 1 (L1) signaling, DCI, etc.). The corresponding information can be transmitted from the base station to the terminal, or, depending on the circumstances or as necessary, from the terminal to the base station.

[0171] In addition, the corresponding information can be configured through a hierarchical approach, which configures the set of candidate groups and indicates specific information.

[0172] Furthermore, the aforementioned panel-related identification information can be configured on a single panel basis or on a multiple panel basis (e.g., panel group, panel set).

[0173] Detection Reference Signal (SRS)

[0174] In version 15NR, spatialRelationInfo can be used to allow the base station to indicate to the terminal the transmission beam to be used when transmitting UL channels. The base station can indicate which UL transmission 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 SRS (i.e., SRS resource) as a reference RS for the target UL channel and / or the target RS via RRC configuration. Furthermore, 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.

[0175] The following describes SRS for codebook (CB) and non-codebook (NCB).

[0176] First, for CB UL, the base station can first configure and / or indicate the transmission of the SRS resource set for "CB" to the terminal. Additionally, the terminal can transmit any n-port SRS resources from the corresponding SRS resource set. The base station can receive the UL channel based on the transmission of the corresponding SRS and use it for the terminal's PUSCH scheduling. Subsequently, when performing PUSCH scheduling via the UL DCI, the base station can indicate the terminal's PUSCH (transmission) beam by indicating the SRS resources for "CB," which were previously transmitted by the terminal via the SRI field of the DCI. Furthermore, the base station can indicate the UL rank and UL precoder via the TPMI (Transmitted Precoder Matrix Indicator) field indicating the uplink codebook. Thus, the terminal can perform PUSCH transmission according to the corresponding indications.

[0177] Next, for NCB UL, the base station can first configure and / or instruct the terminal to transmit the SRS resource set for "non-CB". Furthermore, the terminal can simultaneously transmit the corresponding SRS resource sets by determining the precoder of 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 associated with the corresponding SRS resource. Subsequently, when performing PUSCH scheduling via the UL DCI, the base station can simultaneously instruct the terminal's PUSCH (transmission) beam and UL rank and UL precoder by instructing the portion of the SRS resources previously transmitted by the terminal for "non-CB" via the SRI field of the DCI. Thus, the terminal can perform PUSCH transmission according to the corresponding instructions.

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

[0179] SRS can be used for beam management. Specifically, UL BM can be performed via beamforming UL SRS transmission. Whether an SRS resource set's UL BM is applied is configured via the (higher-layer parameter) "Usage". When the usage is configured as "BeamManagement(BM)", only one SRS resource can be sent to each of the multiple SRS resource sets at a given time. The terminal can be configured with one or more Probe Reference Symbol (SRS) resource sets, which are configured by the (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). Here, K is a natural number, and the maximum value of K is indicated by SRS_capability.

[0180] The SRS used for antenna switching will be described below.

[0181] SRS can be used to acquire DL CSI (Channel State Information) information (e.g., DL CSI acquisition). In a specific example, the BS (Base Station) can measure the SRS from the UE (User Equipment) after scheduling SRS transmissions to the UE (User Equipment) based on TDD in a single-cell or multi-cell scenario (e.g., carrier aggregation (CA)). In this case, the base station can perform scheduling of the UE's DL signals / channels by assuming DL / UL reciprocity based on the measurement via SRS. Here, regarding SRS-based DL CSI acquisition, the SRS can be configured for antenna switching.

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

[0183] The following section will describe in detail the situation where SRS transmission (i.e., transmission of SRS resources or sets of SRS resources) is configured for antenna switching during use.

[0184] In the example, for terminals with partial reciprocity, in scenarios such as TDD (Time Division Duplex), SRS transmission based on antenna switching (i.e., transmission antenna switching) can be supported in order to obtain DL (Downlink) CSI (Channel State Information) via SRS transmission. When antenna switching is applied, it typically takes approximately 15 μs for the terminal's antenna switching to occur between SRS resources (and / or between SRS resources and PUSCH / PUCCH). Taking this into account, the (minimum) guard period can be defined in Table 7 below.

[0185] [Table 7]

[0186] μ <![CDATA[Δf=2 μ ·15[kHz]]]> Y [symbol] 0 15 1 1 30 1 2 60 1 3 120 2

[0187] In Table 7, μ represents the parameter set, Δf represents the subcarrier spacing, and Y represents the number of symbols in the guard period, i.e., the length of the guard period. Referring to Table 7, the guard period can be configured based on the parameter μ that determines the parameter set. During the guard period, the terminal can be configured not to transmit any other signals, and the guard period can be configured to be used entirely for antenna switching. In the example, the guard period can be configured by considering SRS resources transmitted in the same time slot. In particular, when the terminal is configured and / or instructed to transmit aperiodic SRS configured through in-slot antenna switching, the corresponding terminal can transmit SRS on each specified SRS resource using different transmission antennas, and the aforementioned guard period can be configured between each resource.

[0188] Furthermore, as mentioned above, when a terminal is configured with SRS resources and / or SRS resource sets configured for antenna switching via higher-layer signaling, the corresponding terminal can be configured to perform SRS transmission based on the UE capabilities associated with antenna switching. In this case, the UE capabilities associated with antenna switching can be "1T2R", "2T4R", "1T4R", "1T4R / 2T4R", "1T1R", "2T2R", "4T4R", etc. Here, "mTnR" can refer to a UE capability supporting m transmits and n receives.

[0189] (Example S1) For example, for a terminal supporting 1T2R, up to two SRS resource sets can be configured with different values ​​for the resourceType of the higher-layer parameter SRS-ResourceSet. In this case, each SRS resource set can have two SRS resources transmitted in different symbols, and each SRS resource can be configured with a single SRS port in a given SRS resource set. Furthermore, the SRS port used for the second SRS resource in the SRS resource set can be configured to be associated with a different UE antenna port than the SRS port used for the first SRS resource in the same SRS resource set.

[0190] (Example S2) In another example, for a 2T4R-enabled terminal, up to two SRS resource sets can be configured with different values ​​for the resourceType of the higher-layer parameter SRS-ResourceSet. Here, each SRS resource set can have two SRS resources transmitted in different symbols, and each SRS resource can be configured with two SRS ports in a given SRS resource set. Furthermore, the SRS port pair for the second SRS resource in the SRS resource set can be configured to be associated with a different UE antenna port than the SRS port pair for the first SRS resource in the same SRS resource set.

[0191] (Example S3) In another example, for a terminal supporting 1T4R, the SRS resource set can be configured according to different schemes depending on whether the SRS transmission is configured as periodic, semi-persistent, and / or aperiodic. First, when the SRS transmission is configured as periodic or semi-persistent, zero SRS resource sets configured based on the resourceType of the higher-layer parameter SRS-ResourceSet, or one SRS resource set configured with four SRS resources, can be configured for transmission in different symbols. Here, each SRS resource can be configured with a single SRS port within a given SRS resource set. Furthermore, the SRS port for each SRS resource can be configured to be associated with a different UE antenna port. On the other hand, when the SRS transmission is configured as aperiodic, zero SRS resource sets configured based on the resourceType of the higher-layer parameter SRS-ResourceSet, or two SRS resource sets configured with a total of four SRS resources, can be configured for transmission in different symbols across two different time slots. Here, the SRS port for each SRS resource in the two given SRS resource sets can be configured to be associated with a different UE antenna port.

[0192] (Example S4) In another example, for terminals supporting 1T1R, 2T2R, or 4T4R, up to two SRS resource sets, each with one SRS resource set, can be configured for SRS transmission. The number of SRS ports for each SRS resource can be configured to 1, 2, or 4.

[0193] When the indicated UE capability is 1T4R / 2T4R, the corresponding terminal may expect to configure the same number of SRS ports (e.g., 1 or 2) for all SRS resources in the SRS resource set. Furthermore, when the indicated UE capability is 1T2R, 2T4R, 1T4R, or 1T4R / 2T4R, the corresponding terminal may not expect one or more SRS resource sets configured for antenna switching in the same time slot to be configured or triggered. Additionally, when the indicated UE capability is 1T1R, 2T2R, or 4T4R, the corresponding terminal may not expect one or more SRS resource sets configured for antenna switching in the same time slot to be configured or triggered.

[0194] Operations related to multiple TRPs

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

[0196] M-TRP transmission schemes that send data from M TRPs to a terminal can be mainly classified into i) eMBB M-TRP transmission, a scheme used to improve the transmission rate, and ii) URLLC M-TRP transmission, a scheme used to increase the success rate of reception and reduce latency.

[0197] Furthermore, regarding DCI transmission, M-TRP transmission schemes can be classified into i) M-TRP transmission based on M-DCI (multiple DCIs), where each TRP sends a different DCI, and ii) M-TRP transmission based on S-DCI (single DCI), where only one TRP sends the DCI. For example, for S-DCI-based M-TRP transmission, all scheduling information regarding 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.

[0198] For TDM-based URLLC M-TRP transmission, schemes 3 and 4 are being discussed for standardization. Specifically, scheme 4 refers to a scheme where a TRP transmits a transport block (TB) in one time slot, and it has the effect of increasing the probability of data reception by receiving the same TB from multiple TRPs in multiple time slots. Meanwhile, scheme 3 refers to a scheme where 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.

[0199] 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) destined for different TRPs, or it can identify PDSCH (or PDCCH) from different TRPs. Furthermore, the method described below for UL transmissions (e.g., PUSCH / PUCCH) destined for different TRPs can be equivalently applied to UL transmissions (e.g., PUSCH / PUCCH) destined for different panels belonging to the same TRP.

[0200] In the following, the CORESET group ID described / mentioned in this disclosure may refer to index / identification information (e.g., ID, etc.) used to distinguish CORESETs for each TRP / panel. Alternatively, a CORESET group may be a group / union 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 can be configured / indicated / defined by the index defined in the CORESET configuration for each CORESET. Additionally / alternatively, the CORESET group ID may refer to index / identification information / indicators, etc., used to distinguish / identify CORESETs associated with each TRP / panel configuration. In the following, the CORESET group ID described / mentioned in this disclosure may be replaced by a specific index / specific identification information / specific indicator used to distinguish / identify CORESETs associated with each TRP / panel configuration. The CORESET group ID 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), i.e., a specific index / specific identification information / specific indicator used to distinguish / identify CORESETs configured / associated with each TRP / panel. In the example, it can be configured / indicated that PDCCH detection will be performed on a per-TRP / panel basis (i.e., per TRP / panel belonging to the same CORESET group) at the corresponding CORESET group level. Additionally / alternatively, it can be configured / indicated that uplink control information (e.g., CSI, HARQ-A / N (ACK / NACK), SR (Schedule Request)) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) are separated and managed / controlled on a per-TRP / panel basis (i.e., per TRP / panel belonging to the same CORESET group) at the corresponding CORESET group level (i.e., per TRP / panel belonging to the same CORESET group). Additionally / alternatively, HARQ A / N (processing / retransmission) for PDSCH / PUSCH, etc., scheduled per TRP / panel can be managed per corresponding CORESET group (i.e., per TRP / panel belonging to the same CORESET group).

[0201] 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. The TPs send data between each other using different DMRS (Demodulation Multiplexing Reference Signals) through different layers (i.e., through different DMRS ports).

[0202] The TP delivers data scheduling information to the receiving terminal via DCI. Here, the scheme where each TP participating in NCJT delivers scheduling information about its own transmitted data via DCI is called "multi-DCI-based NCJT". Since each of the N TPs participating in NCJT transmission sends a DL license DCI and a PDSCH to the UE, the UE receives N DCIs and N PDSCHs from the N TPs. Simultaneously, the scheme where a representative TP delivers scheduling information about data transmitted by itself and data transmitted by different TPs (i.e., TPs participating in NCJT) via a single DCI is called "single-DCI-based NCJT". Here, N TPs transmit one PDSCH, but each TP's transmission includes only some of the multiple layers in a single PDSCH. For example, when transmitting 4 layers of data, TP 1 can transmit 2 layers to the UE, and TP 2 can transmit the remaining 2 layers to the UE.

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

[0204] 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 partially overlapping NCJTs, data from both TP 1 and TP 2 are transmitted in some time and frequency resources, and data from only one of TP 1 or TP 2 is transmitted in the remaining time and frequency resources.

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

[0206] The following two methods can be considered as a method for improving the reliability of sending and receiving when using transmissions in multiple TRPs.

[0207] Figure 8 The illustration shows a method for multi-TRP transmission that can be applied to a wireless communication system according to the present disclosure.

[0208] refer to Figure 8(a) illustrates the case where layer groups transmitting the same codeword (CW) / transmission block (TB) correspond to different TRPs. Here, a layer group can refer to a predetermined set of layers comprising one or more layers. In this case, there are advantages: the amount of transmission resources increases due to the number of layers, allowing robust channel coding with low coding rates to be used for the TB; and additionally, since the multiple TRPs have different channels, improved reliability of the received signal can be expected based on diversity gain.

[0209] refer to Figure 8 (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 refer to the same TB being transformed into different CWs by different TRPs through channel coding, etc. Therefore, this can be seen as an example of repeatedly transmitting the same TB. Figure 8 In the case of (b), with Figure 8 (a) The disadvantage is that the code rate is higher corresponding to the TB. However, the advantage is that the code rate can be adjusted by indicating different RV (redundant version) values, or the modulation order of each CW generated from the same TB can be adjusted according to the channel environment.

[0210] According to the above Figure 8 (a) and Figure 8 The method shown in (b) can improve 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 a different TRP / panel. It is called the SDM (Space Division Multiplexing) based M-TRP URLLC transmission method. Layers belonging to different layer groups are transmitted separately through DMRS ports belonging to different DMRS CDM groups.

[0211] Furthermore, the above content related to multiple TRPs is described 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.).

[0212] Uplink power control

[0213] Depending on the situation in the wireless communication system, it may be necessary to increase or decrease the transmission power of terminals (e.g., user equipment (UE) and / or mobile devices). Thus, controlling the transmission power of terminals and / or mobile devices can be referred to as uplink power control. In this example, methods for controlling transmission power can be applied to meet the requirements of the base station (e.g., gNB, eNB, etc.) (e.g., SNR (signal-to-noise ratio), BER (bit error rate), BLER (block error rate), etc.).

[0214] As described above, power control can be performed using both open-loop and closed-loop power control methods.

[0215] Specifically, open-loop power control refers to a method of controlling transmit power without feedback from the transmitting device (e.g., base station, etc.) to the receiving device (e.g., terminal, etc.) and / or from the receiving device to the transmitting device. In the example, the terminal can receive a specific channel / signal (pilot channel / signal) from the base station and estimate the strength of the received power using it. Subsequently, the terminal can control the transmit power by using the estimated strength of the received power.

[0216] In contrast, closed-loop power control refers to a method of controlling transmission power based on feedback from the transmitting device to the receiving device and / or from the receiving device to the transmitting device. In this example, the base station receives a specific channel / signal from the terminal and determines the optimal power level for the terminal based on the power level measured by the received specific channel / signal, SNR, BER, BLER, etc. The base station delivers information about the determined optimal power level (i.e., feedback) to the terminal via a control channel, etc., and the terminal can control its transmission power using the feedback provided by the base station.

[0217] The following section will describe in detail a power control method for performing uplink transmissions to a base station in a wireless communication system by a terminal and / or mobile device.

[0218] Specifically, the following describes a power control method for transmissions of 1) uplink data channels (e.g., PUSCH (Physical Uplink Shared Channel)), 2) uplink control channels (e.g., PUCCH (Physical Uplink Control Channel), 3) sounding reference signals (SRS), and 4) random access channels (e.g., PRACH (Physical Random Access Channel)). Here, the transmission timing (i) for PUSCH, PUCCH, SRS, and / or PRACH can be defined by the slot index (n_s) in the frame of the system frame number (SFN), the first symbol (S) in the slot, the number of consecutive symbols (L), etc.

[0219] For ease of description, the power control method will be described below based on the case where the terminal performs PUSCH transmission. Of course, the corresponding method can be extended and applied to other uplink data channels supported by the wireless communication system.

[0220] For PUSCH transmission in the active UL bandwidth portion (UL BWP) of the carrier (f) of the serving cell (c), the terminal can calculate a linear power value of the transmission power determined by Equation 3 below. Subsequently, the corresponding terminal can control the transmission power by taking into account the number of antenna ports and / or the number of SRS ports used to calculate the linear power value, etc.

[0221] Specifically, when a terminal performs PUSCH transmission in the active UL BWP(b) of the carrier (f) of the serving cell (c) by using parameter set configuration based on index j and PUSCH power control adjustment state based on index l, the terminal can determine the PUSCH transmission power P at the PUSCH transmission timing (i) based on the following Equation 3. PUSCH,b,f,c (i,j,q d ,l)(dBm.

[0222] [Formula 3]

[0223]

[0224] In Equation 3, index j represents the index of the open-loop power control parameters (e.g., P0, alpha(α), etc.), and each cell can be configured with up to 32 parameter sets. Index q_d represents the index of the DL RS resources used for path loss (PL) measurement (e.g., PL...). b,f,c (q d Each cell can be configured with up to four measurements. Index l represents the index of the closed-loop power control process, and each cell can be configured with up to two processes.

[0225] Specifically, because P O (For example, P) O_PUSCH，b，f，c (j) is a parameter broadcast as part of system information, which can represent the target received power from the receiver. The appropriate Po value can be configured by considering factors such as terminal throughput, cell capacity, noise, and / or interference. Additionally, alpha (e.g., α) b，f，c (j) can represent the ratio at which compensation for path loss is performed. Alpha can be configured as a value from 0 to 1, and depending on the configured value, full-path loss compensation or partial-path loss compensation can be performed. In this case, the alpha value can be configured by taking into account interference between terminals and / or data rates, etc. Additionally, P CMAX,f,c(i) can represent the configured UE transmit power. In the example, the configured UE transmit power can be interpreted as the “configured maximum UE output power” defined in 3GPP TS 38.101-1 and / or TS38.101-2. Furthermore, M RB,b,f,c PUSCH (i) can represent the bandwidth of PUSCH resource allocation, which is expressed as the number of resource blocks (RBs) for PUSCH transmission timing based on subcarrier spacing (μ). Furthermore, f is related to the PUSCH power control adjustment state. b，f，c (i, l) can be configured or indicated based on the TPC command fields of DCI (e.g., DCI format 0_0, DCI format 0_1, DCI format 2_2, DCI format 2_3, etc.).

[0226] In this context, specific RRC (Radio Resource Control) parameters (e.g., SRI-PUSCHPowerControl-Mapping, etc.) can represent the link between the SRI (SRS Resource Indicator) field of the DCI (Downlink Control Information) and the aforementioned indices j, q_d, l. In other words, the aforementioned indices j, l, q_d, etc., can be associated with beams, panels, and / or spatial domain transmission filters based on specific information. Therefore, PUSCH transmission power control can be performed on a per-beam, per-panel, and / or spatial domain transmission filter basis.

[0227] The parameters and / or information used for the aforementioned PUSCH power control can be configured individually (i.e., independently) according to the BWP. In this case, the corresponding parameters and / or information can be configured or indicated via higher-level signaling (e.g., RRC signaling, MAC-CE (Media Access Control - Control Element) etc.) and / or DCI, etc. For example, the parameters and / or information used for PUSCH power control can be sent via RRC signaling such as PUSCH-ConfigCommon, PUSCH-PowerControl, etc., and PUSCH-ConfigCommon, PUSCH-PowerControl can be configured as shown in Table 8 below.

[0228] [Table 8]

[0229]

[0230] Using the method described above, the terminal can determine or calculate the PUSCH transmission power and send the PUSCH using the determined or calculated PUSCH transmission power.

[0231] For ease of description, the power control method will be described below based on the case where the terminal performs PUCCH transmission. Of course, the corresponding method can be extended and applied to other uplink control channels supported by the wireless communication system.

[0232] Specifically, when a terminal performs PUCCH transmission in the active UL BWP(b) of a carrier (f) of a primary (or secondary) cell by adjusting the state using PUCCH power control based on index l, the terminal can determine the PUCCH transmission power P at the PUCCH transmission timing (i) based on the following equation 4. PUCCH,b,f,c (i,q u ,q d ,l)(dBm.

[0233] [Formula 4]

[0234]

[0235] In Equation 4, q_d represents the open-loop power control parameter (e.g., P). O The index (e.g., PL) can be configured for each cell, with up to eight parameter values. The index q_d represents the index of the DL RS resources used for path loss (PL) measurement (e.g., PL...). b,f,c (q d Each cell can be configured with up to four measurements. Index l represents the index of the closed-loop power control process, and each cell can be configured with up to two processes.

[0236] Specifically, because P O (For example, P) O_PUCCH,b,f,c (q u The P parameter is broadcast as part of the system information, so it can represent the target received power from the receiver. The appropriate P can be configured by considering factors such as terminal throughput, cell capacity, noise, and / or interference. O Value. Additionally, P CMAX，f，c (i) can represent the configured UE transmit power. In the example, the configured UE transmit power can be interpreted as the “configured maximum UE output power” defined in 3GPP TS 38.101-1 and / or TS38.101-2. Furthermore, M RB,b,f,c PUCCH (i) can represent the bandwidth of PUCCH resource allocation, which is expressed as the number of resource blocks (RBs) based on the PUCCH transmission timing at subcarrier intervals (μ). Furthermore, the delta function (e.g., Δ) can be configured by considering the PUCCH format (e.g., PUCCH formats 0, 1, 2, 3, 4, etc.). F_PUCCH (F), Δ TF,b,f,c (i)). Furthermore, g related to the PUCCH power control adjustment stateb,f,c (i,l) can be configured or indicated based on the TPC command field of the DCI (e.g., DCI format 1_0, DCI format 1_1, DCI format 2_2, etc.) received or detected by the terminal.

[0237] In this scenario, specific RRC parameters (e.g., PUCCH-SpatialRelationInfo, etc.) and / or specific MAC-CE commands (e.g., PUCCH spatial relation activation / disable, etc.) can be used to activate or disable the link between PUCCH resources and the aforementioned indices q_u, q_d, and l. In the example, the PUCCH spatial relation activation / disable command in MAC-CE can activate or disable the link between PUCCH resources and the aforementioned indices q_u, q_d, and l based on the RRC parameters and PUCCH-SpatialRelationInfo. In other words, the aforementioned indices q_u, q_d, and l can be associated with beams, panels, and / or spatial domain transmission filters based on specific information. Therefore, PUCCH transmission power control can be performed on a per-beam, per-panel, and / or spatial domain transmission filter basis.

[0238] The parameters and / or information used for the PUCCH power control described above can be configured individually (i.e., independently) according to the BWP. In this case, the corresponding parameters and / or information can be configured or indicated by higher-level signaling (e.g., RRC signaling, MAC-CE, etc.) and / or DCI, etc. In the example, the parameters and / or information used for PUCCH power control can be sent via RRC signaling PUCCH-ConfigCommon, PUCCH-PowerControl, etc., and PUCCH-ConfigCommon, PUCCH-PowerControl can be configured as shown in Table 9 below.

[0239] [Table 9]

[0240]

[0241] Using the method described above, the terminal can determine or calculate the PUCCH transmission power and send the PUCCH using the determined or calculated PUCCH transmission power.

[0242] Multiple TRP PUSCH transmission method

[0243] In the method proposed in this disclosure, DL MTRP-URLLC means that multiple TRPs transmit the same data / DCI using different layer / 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 layer / time / frequency resources. Here, the base station indicates which QCL RS / type (i.e., DL TCI state) the UE should use in the layer / time / frequency resource 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 are indicated. The UE can achieve high reliability because it receives the same data / DCI through resource 1 and resource 2. This DLMTRP URLLC can be applied to PDSCH / PDCCH.

[0244] Conversely, UL MTRP-URLLC means that multiple TRPs receive the same data / UCI from the UE using different layer / time / frequency resources. For example, after TRP 1 receives the same data / UCI from the UE in resource 1 and TRP 2 receives the same data / UCI from the UE in resource 2, the received data / UCI is shared via a backhaul link connected between the TRPs. A UE configured with the UL MTRP-URLLC transmission method transmits the same data / UCI using different layer / time / frequency resources. Here, the base station instructs the UE 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 / UCI. 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 are indicated. This UL MTRP URLLC can be applied to PUSCH / PUCCH.

[0245] Furthermore, in the methods proposed in this disclosure, when a specific TCI state (or TCI) is used (or mapped) in receiving data / DCI / UCI of any frequency / time / space resource, it means the following: For DL, this may mean estimating the channel from the DMRS using the QCL type and QCL RS indicated by the corresponding TCI state in the corresponding frequency / time / space resource, and using the estimated channel to receive / demodulate data / DCI. For UL, this may mean transmitting / modulating the DMRS and data / UCI using the Tx beam and / or Tx power indicated by the corresponding TCI state in that frequency / time / space resource.

[0246] The UL TCI status includes the UE's Tx beam or Tx power information. Alternatively, spatial relationship information can be configured to the UE using other parameters besides the TCI status. The UL TCI status can be directly indicated to the UL-licensed DCI, or indirectly indicated as spatial relationship information of the SRS resources indicated by the SRI field of the UL-licensed DCI. Alternatively, it may mean open-loop (OL) Tx power control parameters connected to the values ​​indicated by the SRI field of the UL-licensed DCI (e.g., j: index of open-loop parameters Po and alpha (up to 32 parameter value sets per cell)), q_d: index of DLRS resources used for PL (path loss) measurements (up to 4 measurements per cell), and l: index of closed-loop power control procedures (up to 2 procedures per cell)).

[0247] On the other hand, MTRP-eMBB means that multiple TRPs transmit different data using different layers / times / frequency. A UE configured with the MTRP-eMBB transmission method receives indications about multiple TCI states via DCI and assumes that the data received using the QCL RS for each TCI state is different.

[0248] Furthermore, the UE can determine whether it is MTRP URLLC transmission / reception or MTRP eMBB transmission / reception by separating and using the RNTI for MTRP-URLLC and the RNTI for MTRP-eMBB. In other words, when using the RNTI for URLLC to perform CRC masking for DCI, the UE is considered to be transmitting via URLLC, and when using the RNTI for eMBB to perform CRC masking for DCI, the UE is considered to be transmitting via eMBB. Alternatively, the base station can configure MTRP URLLC transmission / reception, or it can configure TRP eMBB transmission / reception to the UE via other new signaling.

[0249] 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 to environments with three or more multi-TRPs. Furthermore, it can be extended and applied to multi-panel environments (i.e., by matching TRPs with panels). Additionally, for the UE, different TRPs can be considered to be in different TCI states. Therefore, when the UE receives / transmits data / DCI / UCI using TCI state 1, it means receiving / transmitting data / DCI / UCI from / to TRP 1.

[0250] The proposals disclosed herein can be used in situations where MTRP cooperatively sends PDCCH (repeatedly or partially sending the same PDCCH), and some proposals can also be used in situations where MTRP cooperatively sends PDSCH or cooperatively receives PDSCH / PUCCH.

[0251] Furthermore, in the following text, within this document, when a UE repeatedly transmits the same PUSCH so that multiple base stations (i.e., MTRPs) can receive it, this may mean transmitting the same data via multiple PUSCHs. Here, each PUSCH can be transmitted by optimizing the UL channel to different TRPs. For example, consider the case where the UE repeatedly transmits the same data via PUSCH 1 and 2. PUSCH 1 can be transmitted using UL TCI state 1 for TRP 1, and link adaptation such as precoder / MCS can also be transmitted after the channel optimization value for TRP 1 is scheduled. PUSCH 2 can be transmitted using ULTCI state 2 for TRP 2, and link adaptation such as precoder / MCS can also be transmitted after the channel optimization value for TRP 2 is scheduled. Here, the repeatedly transmitted PUSCH 1 and 2 can be transmitted at different times to be time-division multiplexed (TDM), frequency-division multiplexed (FDM), or space-division multiplexed (SDM).

[0252] Additionally, in this disclosure, when a UE partially transmits the same PUSCH so that multiple base stations (i.e., MTRPs) receive it, it can mean that one data is transmitted over one PUSCH, and the resources allocated to that PUSCH are transmitted through UL channels that are partitioned and optimized to different TRPs. For example, consider a UE transmitting the same data over 10 symbol PUSCHs. Here, in the first 5 symbols, the PUSCH can be transmitted using UL TCI state 1 for TRP 1, and link adaptation such as precoder / MCS can also be transmitted after the channel-optimized value for TRP 1 is scheduled. In the remaining 5 symbols, the PUSCH can be transmitted using UL TCI state 2 for TRP 2, and link adaptation such as precoder / MCS can also be transmitted after the channel-optimized value for TRP 2 is scheduled. In this example, the transmission for TRP 1 and the transmission for TRP 2 are time-division multiplexed (TDM) by partitioning a PUSCH into time resources, but it can be transmitted using other FDM / SDM methods.

[0253] Similar to PUSCH transmission, the UE can also repeatedly send the same PUCCH or partially send the same PUCCH, allowing multiple base stations (i.e., MTRPs) to receive the PUCCH.

[0254] The proposals disclosed herein can be extended and applied to various channels, such as PUSCH / PUCCH / PDSCH / PDCCH, etc.

[0255] In version 16eNR MIMO, standardization was implemented for PDSCH transmissions based on a single DCI and PDSCH transmissions based on multiple DCIs for multi-TRP PDSCH transmissions. In version 17FeNR MIMO, standardization will be implemented for multi-TRP transmissions that do not include PDSCH (e.g., PDCCH, PUCCH, PUSCH, etc.) (hereinafter, multi-TRP will be referred to as M-TRP, MTRP, etc.).

[0256] For M-TRP PUSCH transmission, the terminal's SRS transmission needs to precede UL channel estimation and link adaptation before the base station's PUSCH scheduling. However, according to the SRS architecture of version 15NR, there is a limitation that only one SRS resource set can be configured separately for CB (codebook) / NCB (non-codebook) (up to 2 resources can exist in the SRS resource set for CB and up to 4 resources can exist in the SRS resource set for NCB). Therefore, there are limitations on the terminal's SRS configuration / transmission for M-TRP PUSCH.

[0257] Additionally, when a base station performs M-TRP PUSCH scheduling, both single-DCI-based and multi-DCI-based scheduling are possible. However, it is necessary to define how information about PUSCHs directed to different TRPs (e.g., TRI (Transmission Rank Indicator), TPMI (Transmission Precoding Matrix Indicator), CQI) will be included in a single or multiple DCIs.

[0258] Against this background, this invention proposes an SRS configuration and a multi-TRP PUSCH scheduling method for base station scheduling to terminal multi-TRP PUSCH transmission, and proposes a subsequent terminal multi-TRP PUSCH transmission method.

[0259] In this document, " / " in the context means "and" or "or" or "and / or". This disclosure primarily describes the idea based on PUSCH, but is not limited to it, and the same / similar approach can be applied to PUCCHs configured with multiple TOs (transmission times). Furthermore, the following proposal is based on the scenario of sending PUSCHs for multiple TOs via DCI, but it can also be applied when sending corresponding PUSCHs at multiple TOs if PUSCH transmission is performed every specific cycle (e.g., semi-persistent PUSCH), or if the terminal sends PUSCHs in the appropriate resource (e.g., unlicensed PUSCH) when necessary after a UL resource that can send PUSCHs (for URLLC or voice services) has been (semi-statically) allocated to the terminal.

[0260] For base station-to-terminal PUSCH scheduling toward two or more TRPs, it needs to precede SRS transmission from the terminal for UL channel estimation and UL link adaptation. This SRS transmission can be performed with multiple TRPs listening to a single transmission; however, when considering beam-based operations or FR2-based systems (see Table 2), the terminal needs to send SRS toward each TRP separately. The SRS configuration / transmission method for transmitting SRS toward each TRP can be categorized into two methods.

[0261] Method 1 Implicit SRS configuration method for transporting SRS to each TRP (or SRS configuration method for different TRPs via multiple SRS resource sets).

[0262] Unlike version 15, where the SRS resource set configuration is limited to one for both codebook (CB) and non-codebook (NCB) usages, two or more SRS resource sets can be configured separately for CB and NCB usages. Therefore, different SRS resource sets for each usage can include SRS resources oriented towards different TRPs. In other words, two or more SRS resource sets can be configured for CB, and each SRS resource set can correspond to a different TRP. Similarly, two or more SRS resource sets can be configured for NCB, and each SRS resource set can correspond to a different TRP.

[0263] According to Method 1, power control parameters are configured at the SRS resource set level within the existing SRS configuration structure, thus offering the advantage of being able to perform power control operations according to the TRP. Furthermore, when different panels correspond to different SRS resource sets (e.g., when different panel IDs (P-IDs) are configured for different SRS resource sets), there is the advantage of being able to freely configure / indicate transmission panels for SRS resource sets facing different TRPs.

[0264] Method 2 : An explicit SRS configuration method for SRS transmissions toward each TRP (or an SRS configuration method for different TRPs via a single SRS resource set).

[0265] Usage parameters (i.e., "usage") defined / configured in the SRS resource set configuration, parameters for M-TRP PUSCH (e.g., "m-trpPUSCH") (or parameters for hybrid (e.g., "hybrid"), where hybrid means a mixture of codebook and non-codebook features present in the SRS resource set), can be newly added / defined. SRS resources oriented towards different TRPs can be configured in the SRS resource set for the corresponding M-TRP PUSCH. Here, all SRS resources configured in the corresponding SRS resource set can be used for CB, or for NCB, or SRS resources for CB and for NCB can be mixed.

[0266] According to Method 2, SRS resources for CB and NCB can be flexibly configured within a single SRS resource set, and there is an advantage that SRS resources for CB and NCB can be configured in a mixed manner. Here, the classification of SRS resources for CB and NCB can be predefined / configured / standardized. For example, CB usage can be configured as a multi-port SRS resource, and NCB usage can be configured as a single-port SRS resource. Simultaneously, for the transmission panel configuration / indication of each SRS resource, a P-ID configuration for each resource or a P-ID configuration of the spatial relation information (spatialRelationInfo) in the resource configuration (or / and UL TCI configuration) is required. However, there is a disadvantage that it is difficult to perform individual power control for different SRS resources towards each TRP.

[0267] Based on Method 1 and Method 2 above, the following proposals are made.

[0268] Example 1: The base station can configure DL / UL RS (e.g., SSB, CSI-RS, SRS) information, including the cell ID (or TRP ID), as spatial relationship information for each SRS resource (or each SRS resource set). Therefore, the terminal can distinguish / identify which TRP the SRS resource is directed towards for a specific SRS resource. For example, when applying method 1, i) the receiving cell ID (or TRP ID) can be configured in the configuration of the SRS resource set. Alternatively, when applying method 2, ii) the receiving cell ID (or TRP ID) can be configured in the configuration for the SRS resource.

[0269] Through Example 1, the terminal can identify a specific SRS resource set or SRS resource as an SRS resource for M-TRP PUSCH scheduling (used for UL channel estimation and link adaptation). The base station can measure the UL channel of each TRP by having the terminal send the corresponding SRS resource (e.g., SRS transmission triggered by DCI), and can subsequently schedule M-TRP PUSCH to the terminal. Additionally, when the base station subsequently performs M-TRP PUSCH scheduling, the SRS resource set / SRS resource can be indicated as a reference via the SRS Resource Indicator (SRI) field and / or the UL-TCI field (or a specific field in the DCI as proposed below) of the corresponding PUSCH scheduling DCI. Therefore, the terminal can identify the target TRP for multiple scheduled PUSCHs and send PUSCH according to the corresponding SRS configuration (and the configuration for PUSCH TO).

[0270] Example 2 The base station can use the following methods to schedule M-TRP PUSCH to the terminal.

[0271] Example 2-1 For parameters configuring the UL transmission mode of a terminal (e.g., "txConfig"), the M-TRP PUSCH configuration (e.g., "m-trpPUSCH" or "hybrid") excludes both "codebook" and "non-codebook" configurations. Here, "hybrid" means that features can be added / defined where codebook and non-codebook are mixed and utilized for PUSCH transmission. The base station can switch the terminal's UL transmission mode to M-TRP PUSCH transmission mode by configuring the UL transmission mode configuration (e.g., "txConfig") of a specific terminal to an M-TRP PUSCH configuration (e.g., "m-trpPUSCH" or "hybrid"). This method has the characteristics of semi-static scheduling. It is clear that the "m-trpPUSCH" or "hybrid" parameter name can include other names as examples and does not limit the scope of the proposals in this disclosure.

[0272] As described above, because the UL transmission mode configuration (e.g., “txConfig”) is configured as an M-TRP PUSCH configuration (e.g., “m-trpPUSCH” or “hybrid”), the DCI for PUSCH scheduling following this configuration refers to the scheduling of multiple PUSCH transmission opportunities (TOs) toward multiple TRPs. Therefore, the corresponding DCI fields obtain information about multiple sets of PUSCHs toward multiple TRPs. In other words, a set of PUSCHs including one or more PUSCH TOs can be scheduled per TRP. Specifically, for the beam indication of each PUSCH (i.e., for indicating the beam independently per TRP), multiple beams can be configured / indicated by the DCI through multiple SRI (or UL-TCI status) fields. Furthermore, multiple timing advance (TA) values ​​for each PUSCH can be configured / indicated / applied by the DCI (i.e., TAs are configured / indicated independently per TRP). Additionally, multiple power control parameter sets (or procedures) for each PUSCH can be configured / indicated / applied by the DCI (i.e., power control parameters are configured / indicated independently according to each TRP). Furthermore, multiple TPMIs (transmit PMIs) can be configured / indicated / applied by the DCI to determine the precoder for each PUSCH (i.e., TPMIs are configured / indicated independently according to each TRP).

[0273] Example 2-2 The base station can be configured with a separate CORESET and / or search space set for M-TRP PUSCH scheduling. The DCI received by the terminal in the corresponding CORESET and / or search space set can be regarded by the terminal as the DCI for scheduling M-TRP PUSCH.

[0274] Alternatively, i) a separate DCI format can be defined / configured for M-TRP PUSCH scheduling. And / or ii) when a separate RNTI is defined / configured for the terminal decoding the DCI for M-TRP PUSCH scheduling, the terminal can utilize the corresponding ID (i.e., RNTI) as a scrambling ID for blind detection. This approach has the advantage of enabling dynamic scheduling. In other words, for M-TRP PUSCH scheduling, the base station can send the DCI to the terminal via the aforementioned CORESET and / or search space set. Alternatively, for TRP PUSCH scheduling, the DCI can be sent to the terminal using the aforementioned separate DCI format and / or a separate RNTI.

[0275] When a terminal receives a DCI via a separately configured CORESET / search space set, or receives a DCI in a separate DCI format as in i), or successfully blindly detects a DCI via a separate RNTI as in ii), the terminal can identify / consider the scheduling of multiple PUSCH TOs (transmission timings) toward multiple TRPs indicated by the corresponding DCI. In this case, the fields of the corresponding DCI obtain information about multiple sets of multiple PUSCHs toward multiple TRPs. Specifically, for the beam indication of each PUSCH (i.e., for beams indicated independently according to each TRP), multiple beams can be configured / indicated by the DCI through multiple SRI (or UL-TCI status) fields. Furthermore, multiple timing advance (TA) values ​​for each PUSCH can be configured / indicated / applied by the DCI (i.e., TAs are configured / indicated independently according to each TRP). Additionally, multiple sets (or procedures) of power control parameters for each PUSCH can be configured / indicated / applied by the DCI (i.e., power control parameters are configured / indicated independently according to each TRP). Additionally, multiple TPMIs (send PMIs) can be configured / instructed / applied by the DCI to determine the precoder for each PUSCH (i.e., TPMIs can be configured / instructed independently for each TRP).

[0276] Example 3: A method for configuring / indicating multiple PUSCH transmission opportunities (TOs) for M-TRP PUSCH scheduling / DCI is proposed, as well as the assumptions and PUSCH transmission method for multiple TOs of subsequent terminals.

[0277] Two SRS resource sets can be configured for M-TRP PUSCH scheduling via Method 1 as described above, or the SRS resource set (or "hybrid") for M-TRP can be configured via Method 2 to perform UL channel estimation / UL link adaptation for M-TRP PUSCH scheduling. Subsequently, in Embodiment 2, the base station can indicate to the terminal via DCI the transmission timings (TOs) of multiple PUSCHs toward multiple TRPs. This configuration for each PUSCH TO toward each TRP can be pre-configured / updated via higher-layer signaling such as RRC / MAC CE (control element) prior to M-TRP PUSCH scheduling.

[0278] When specifically describing the configuration / instruction for each PUSCH TO toward each TRP, the terminal applies Tx beam and power control (PC) parameters (sets) corresponding to the SRS resource set / SRS resource toward each TRP, as indicated by specific fields (e.g., SRI field, UL-TCI field) of the DCI, in a specific order (or according to pre-configured rules) to multiple PUSCH TOs. In other words, PUSCH TOs corresponding to each TRP can be grouped among all PUSCH TOs, and PC parameters (sets) and Tx beams can be applied for the SRS resource set / SRS resource corresponding to each PUSCH TO group.

[0279] Here, according to a specific order (or pre-configured rules), as the TO increases (i.e., in ascending order of the TO index), the PC parameters (set) and Tx beams corresponding to the SRS resource set / SRS resource toward each TRP can be applied alternately (i.e., cyclically and sequentially). Here, as the TO increases (i.e., in ascending order of the TO index), the SRI field of each TRP is mapped alternately (i.e., cyclically and sequentially), so the PC parameters (set) and Tx beams corresponding to the SRS resource set / SRS resource can be applied alternately (i.e., cyclically and sequentially). For example, assume there are 4 PUSCH TOs for PUSCH transmissions for 2 TRPs. Furthermore, assume TRP 1 corresponds to SRS resource set / SRS resource 1, and TRP 2 corresponds to SRS resource set / SRS resource 2. In this case, the PC parameters (set) and Tx beam for SRS resource set / SRS resource 1 can be applied to the first PUSCH TO, and the PC parameters (set) and Tx beam for SRS resource set / SRS resource 2 can be applied to the second PUSCH TO, the PC parameters (set) and Tx beam for SRS resource set / SRS resource 1 can be applied to the third PUSCH TO, and the PC parameters (set) and Tx beam for SRS resource set / SRS resource 2 can be applied to the fourth PUSCH TO.

[0280] Alternatively, when N PUSCH TOs are configured, grouping can be performed according to adjacent ceil(N / 2) (ceil(x) is the smallest integer not less than x) or floor(N / 2) (floor(x) is the largest integer not greater than x). Furthermore, the PC parameters (sets) and Tx beams corresponding to the SRS resource set / SRS resource for each TO group and each TRP can be mapped cyclically or sequentially. In other words, the PC parameters (sets) and Tx beams corresponding to the SRS resource set / SRS resource for each TRP can be mapped cyclically or sequentially to the TRP according to each TO group (i.e., in ascending order of the TO group index). Here, because the SRI field of each TRP is mapped cyclically or sequentially according to each TO group (i.e., in ascending order of the TO group index), the PC parameters (sets) and Tx beams corresponding to the SRS resource set / SRS resource can be mapped cyclically or sequentially. For example, assume there are 6 PUSCH TOs for PUSCH transmissions of 2 TRPs. Furthermore, it is assumed that TRP 1 corresponds to SRS resource set / SRS resource 1, and TRP 2 corresponds to SRS resource set / SRS resource 2. In this case, the PC parameters (set) and Tx beam for SRS resource set / SRS resource 1 can be applied to the first PUSCH TO group (first, second, and third PUSCH TO), and the PC parameters (set) and Tx beam for SRS resource set / SRS resource 2 can be applied to the second PUSCH TO group (fourth, fifth, and sixth PUSCH TO).

[0281] Furthermore, using the same method, multiple precoders indicated by specific fields of DCI (i.e., SRI field, TPMI field) can also be applied to multiple PUSCH TOs in a specific order (or according to pre-configured rules).

[0282] Here, according to a specific order (or pre-configured rules), as the TO increases (i.e., in ascending order of the TO index), the precoder for each TRP can be applied alternately (i.e., cyclically, sequentially). Here, as the TO increases (i.e., in ascending order of the TO index), the SRI corresponding to each TRP is mapped alternately (i.e., cyclically, sequentially), so the precoder for each TRP can be applied alternately (i.e., cyclically, sequentially). For example, assume there are 4 PUSCH TOs for PUSCH transfers of 2 TRPs. Also, assume TRP 1 corresponds to precoder 1, and TRP 2 corresponds to precoder 2. In this case, precoder 1 can be applied to the first PUSCH TO, precoder 2 can be applied to the second PUSCH TO, precoder 1 can be applied to the third PUSCH TO, and precoder 2 can be applied to the fourth PUSCH TO.

[0283] Alternatively, when configuring N PUSCH TOs, grouping can be performed by adjacent floor (N / 2) or ceiling (N / 2) TOs. Furthermore, the precoders for each TO group and each TRP can be mapped cyclically or sequentially. Here, the precoders for each TRP can be mapped cyclically or sequentially according to the TO groups (i.e., in ascending order of the TO group indices). Since the SRI field corresponding to each TRP is mapped cyclically or sequentially according to the TO groups (i.e., in ascending order of the TO group indices), the precoders for each TRP can be mapped cyclically or sequentially. For example, assume there are 6 PUSCH TOs for PUSCH transfers of 2 TRPs. Also, assume TRP 1 corresponds to precoder 1 and TRP 2 corresponds to precoder 2. In this case, precoder 1 can be applied to the first PUSCH TO group (first, second, and third PUSCH TOs) and precoder 2 can be applied to the second PUSCH TO group (fourth, fifth, and sixth PUSCH TOs).

[0284] As a result of the mapping, the terminal can apply the same PC parameters (sets), Tx beams, and / or precoders to adjacent TOs included in the same group. In other words, through this operation, the power control parameters (sets), Tx beams, and / or precoders for multiple PUSCHTOs scheduled towards multiple different TRPs can be configured / indicated by the base station's M-TRP PUSCH scheduling DCI.

[0285] Additionally, the base station can configure / indicate / update the TA values ​​to be applied by the terminal for multiple PUSCH TOs toward multiple TRPs via higher-layer signaling such as RRC and MAC CE before M-TRP PUSCH scheduling. As described above, the terminal can apply the configured / indicated / updated TA values ​​to multiple PUSCH TOs in a specific order. In other words, as the PUSCH TOs increase (i.e., in ascending order of the TO index), the TA values ​​for each TRP can be applied alternately (i.e., cyclically and sequentially). Here, as the PUSCH TOs increase (i.e., in ascending order of the TO index), the SRI field corresponding to each TRP is mapped alternately (i.e., cyclically and sequentially), so the TA values ​​for each TRP can be applied alternately (i.e., cyclically and sequentially).

[0286] Alternatively, when N PUSCH TOs are configured, grouping can be performed according to adjacent floor (N / 2) or ceil (N / 2) TOs. Furthermore, the TA values ​​for each TO group and each TRP can be mapped cyclically or sequentially. Here, the TA values ​​for each TRP can be mapped cyclically or sequentially according to the TO groups (i.e., in ascending order of the TO group indices). In other words, because the SRI fields corresponding to each TRP are mapped cyclically or sequentially according to the TO groups (i.e., in ascending order of the TO group indices), the TA values ​​for each TRP can be mapped cyclically or sequentially.

[0287] In this disclosure, TO can refer to each channel transmitted at different times when multiple channels are time-division multiplexed (TDM), each channel transmitted to different frequencies / RBs when multiple channels are frequency-division multiplexed (FDM), and each channel transmitted to different layers / beams / DMRS ports when multiple channels are space-division multiplexed (SDM). A TCI state is mapped to each TO. When the same channel is repeatedly transmitted (e.g., when PDCCH, PDSCH, PUSCH, PUCCH are repeatedly transmitted), the entire DCI / data / UCI is transmitted to one TO, and the receiving unit increases the success rate of reception by receiving multiple TOs. When a channel is partially transmitted to multiple TOs, a portion of the DCI / data / UCI is transmitted to one TO, and the receiving unit can only receive the entire DCI / data / UCI by collecting the partitioned DCI / data / UCI after receiving all multiple TOs.

[0288] Additionally, when multiple PUSCH TOs are configured / indicated by the number of receiving TRPs for M-TRP PUSCHs, the terminal sends each PUSCH to each TRP. Alternatively, when multiple PUSCH TOs are configured / indicated by n times the number of receiving TRPs for M-TRP PUSCHs, the terminal sends n PUSCHs to each TRP. Information regarding the number of such PUSCH TOs and time-domain / frequency-domain resource allocation can be pre-configured / updated via higher-level configurations such as RRC / MAC CE before the DCI transmission of the base station used for PUSCH scheduling, or can be dynamically indicated via specific fields of the scheduling DCI for PUSCHs. In this case, for subsequent PUSCH transmissions in the terminal's PUSCH TOs, the base station's PC parameters (set), Tx (analog) beam, precoder, and TA configuration / indication can be applied / utilized.

[0289] Example 4: Proposes specific configuration / indication methods for multiple PC parameters (sets), Tx (analog) beams, pre-encoders and TAs of multiple PUSCH TOs in Example 3.

[0290] i) A method for configuring multiple TAs for multiple PUSCH TOs

[0291] The base station can configure / update multiple TA values ​​that should be applied by the terminal to multiple PUSCH TOs before M-TRP PUSCH scheduling. TA values ​​can be configured / indicated / updated to the terminal via higher-level signaling such as MAC CE messages (or RRC messages). Here, the number of TA values ​​can be the same as the number of TRPs participating in M-TRP PUSCH scheduling.

[0292] ii) A method for configuring / indicating multiple Tx beams for multiple PUSCH TOs

[0293] The base station can configure / update multiple Tx beams that should be applied by the terminal to multiple PUSCH TOs before M-TRP PUSCH scheduling. Specifically, the base station can pre-configure / update the PUSCH Tx beams that should be applied by the terminal to each PUSCH TO by linking / connecting / referencing DL RS (e.g., SSB-RI) (rank indicator), CRI (CSI-RS resource indicator) and UL RS (e.g., SRI (SRS resource indicator)) to the PUSCH TO configuration (via RRC / MAC-CE) via spatial relation information (e.g., "spatialRelationInfo") or uplink TCI (e.g., "UL-TCI"). Alternatively, as in methods 1 and 2, the base station can configure / indicate / update the Tx beams that should be applied by the terminal to each PUSCH TO by linking / connecting / referencing the SRS resource set / SRS resource to each PUSCH TO for UL channel estimation / UL link adaptive configuration / transmission.

[0294] Alternatively, the DCI used for M-TRP PUSCH scheduling can include multiple SRI fields or UL-TCI fields (as many as the number of TOs) for indicating the Tx beams that should be applied to multiple PUSCH TOs. Dynamic Tx beam indication is possible by indicating DL RS (e.g., SSB-RI, CRI) and UL RS (e.g., SRI) for each PUSCH TO via multiple SRI fields or UL-TCI fields. Alternatively, although one SRI field or UL-TCI field exists in the DCI, reference RSs (DL / UL RSs) for multiple Rx beams (as many as the number of TOs) can be linked / connected to the corresponding fields (in ordered pairs) via RRC configuration / description. For example, SRS resource 1 of SRS resource set 1 and SRS resource 1 of SRS resource set 2 can be linked / connected to a code point. When the code point is indicated by the SRI field in the DCI, according to Embodiment 3 above, as the PUSCH TO increases (in ascending order of the PUSCH TO index), the SRS resource 1 of SRS resource set 1 and the SRS resource 1 of SRS resource set 2 linked / connected to the code point can be alternately (or cyclically, sequentially) mapped to each PUSCH TO. Additionally, as described above, it is also possible to group adjacent PUSCH TOs. In this case, as the TO groups increase (in ascending order of the PUSCH TO index), the SRS resource 1 of SRS resource set 1 and the SRS resource 1 of SRS resource set 2 linked / connected to the code point can be alternately (or cyclically, sequentially) mapped to each TO group. As above, depending on the link / connection, multiple Tx beams for multiple PUSCH TOs toward multiple TRPs can be indicated by using a code point in one field.

[0295] By connecting the panel to the Tx beam indicated in method ii) for indicating the Tx beam, the terminal can identify the panel to be used for each PUSCH TO transmission. Alternatively, panels may exist pre-linked / connected by a higher layer (in ordered pairs) to the SRI field or UL-TCI field (or each code point in the field), and the terminal uses the panel for each PUSCH TO transmission when the corresponding code point is indicated by scheduling DCI. Additionally, the transmission panel used for each PUSCH TO can be configured / updated via higher-layer signaling before DCI scheduling.

[0296] iii) A method for configuring / indicating multiple PC parameters for multiple PUSCH TOs

[0297] The base station can configure / update multiple PC parameters (sets) that should be applied by the terminal to multiple PUSCH TOs before M-TRP PUSCH scheduling via higher-level signaling (e.g., RRC / MAC-CE, etc.). For example, as in Method 1 and Method 2, the base station can define / configure / indicate / update the PC parameters that should be applied by the terminal to each PUSCH TO by assigning an SRS resource set / SRS resource link / connection / reference to each PUSCH TO for UL channel estimation / UL link adaptation prior to M-TRP PUSCH scheduling.

[0298] Alternatively, multiple SRI fields or UL-TCI fields in the DCI can be defined as in method ii). Furthermore, the PC parameters(sets) corresponding to the PUSCH TOs toward each TRP can be configured / described via RRC to link / connect to each field in the DCI. Therefore, because of the specific code points indicating a particular SRI field or UL-TCI field in the scheduling DCI, the terminal can identify the PC parameters(sets) to be applied to each TO. For example, multiple first PC parameters(sets) corresponding to multiple code points that can be indicated in the first SRI field (or UL-TCI field) in the DCI and multiple second PC parameters(sets) corresponding to multiple code points that can be indicated in the second SRI field (or UL-TCI field) in the DCI can be configured via higher-level signaling such as RRC. Furthermore, a specific PC parameter (set) among multiple first PC parameter (sets) can be indicated by the code point indicated in the first SRI field of the DCI (corresponding to PUSCH TO 1), and a specific PC parameter (set) among multiple second PC parameter (sets) can be indicated by the code point indicated in the second SRI field (corresponding to PUSCH TO 2). Therefore, the terminal can identify the PC parameter (set) applied to each PUSCH TO.

[0299] Similarly, as in ii), an SRI field or a UL-TCI field may exist in the DCI. In this case, the same terminal operation is possible by linking / connecting the PC parameter(set) corresponding to each PUSCH TO to a corresponding field (in the form of ordered pairs) via RRC configuration / description. For example, ordered pairs such as {PC parameter(set)1, PC parameter(set)2, PC parameter(set)3}, {PC parameter(set)4, PC parameter(set)1, PC parameter(set)2}, etc., can be configured via higher-level signaling such as RRC, and any one of the ordered pairs can be indicated as a code point in an SRI field or a UL-TCI field in the DCI.

[0300] Here, the PC parameters (set) corresponding to each PUSCH TO may include the open-loop power control parameter P. O At least one or more of the following: alpha (α), path loss reference RS (i.e., the reference RS resource index for path loss measurement) and / or closed-loop parameters and closed-loop index.

[0301] The code point of the SRI field can be defined differently for enabling and disabling M-TRP PUSCH repetition based on specific conditions or signals. Specifically, this method can be applied when the enabling / disabling of M-TRP PUSCH repetition can be indicated at the MAC level or dynamically (e.g., via DCI). For example, when M-TRP PUSCH repetition is disabled, the code point of the SRI field can be configured / defined as a Tx beam reference DL / UL RS (e.g., SRS resource, CSI-RS, SSB) and / or a power control parameter in the same manner as before. In other words, a Tx beam reference DL / UL RS and / or a set of power control parameters can be configured / defined to be connected / mapped to a code point.

[0302] On the other hand, when M-TRP PUSCH repetitive transmission is enabled, the code point in the SRI field can be configured / defined as a Tx beam reference DL / UL RS (e.g., SRS resource, CSI-RS, SSB) and / or multiple (e.g., 2) power control parameter sets. In other words, a Tx beam reference DL / UL RS and / or multiple power control parameter sets can be configured / defined to be connected / mapped to a single code point. In this case, the Tx beam is fixed according to the PUSCH TO configuration / instruction, but one of multiple PC (power control) parameter sets can be applied to each TO.

[0303] Alternatively, when M-TRP PUSCH repetition is enabled, the code point of the SRI field can be configured / defined as multiple (e.g., 2) Tx beam reference DL / UL RSs (e.g., SRS resources, CSI-RS, SSB) and / or multiple (e.g., 2) power control parameter sets. In other words, multiple Tx beam reference DL / UL RSs and / or multiple power control parameter sets can be configured / defined to be connected / mapped to a single code point. In this case, one of the multiple Tx beam reference DL / UL RSs (e.g., SRS resources, CSI-RS, SSB) and PC parameter sets can be applied to each TO according to the PUSCH TO configuration / instruction.

[0304] The terminal can be configured with the SRI code point value from the base station via RRS signaling. When M-TRPPUSCH repetition is disabled / enabled, different SRI code point values ​​can be configured for each. In other words, when M-TRP PUSCH repetition is disabled / enabled, different Tx beam reference RS and / or PC parameter sets can be configured to connect to / map to each SRI code point.

[0305] In this scenario, depending on whether M-TRP PUSCH repetition is disabled / enabled, the terminal can use the corresponding SRI code point value. In other words, depending on whether M-TRP PUSCH repetition is performed, the terminal can use the Tx beam reference RS and / or PC parameter set that is connected / mapped to the corresponding SRI code point value.

[0306] Additionally, the SRI code point values ​​used for enabling M-TRP PUSCH repetition can be configured as a superset, which includes the values ​​of the SRI code points (connected / mapped to the Tx beam reference RS and / or PC parameter set) for the disabled case. In other words, the Tx beam reference RS and / or PC parameter set connected / mapped to the SRI code point values ​​for enabling M-TRP PUSCH repetition can include the Tx beam reference RS and / or PC parameter set connected / mapped to the SRI code point values ​​for the disabled case. For example, for code point 0 in the SRI field, when M-TRP PUSCH repetition is disabled, it can be configured as DL / UL RS index 0 or PC parameter set index 0 (for Tx beam reference), and when TRP PUSCH repetition is enabled, it can be configured as DL / UL RS index 0, DL / UL RS index 1, PC parameter set index 0, or PC parameter set index 1.

[0307] In the above description, the SRI field can be replaced by the UL TCI status field or / and the DL / UL unified TCI status field. Because the DL / UL unified TCI status field is used, the spatial relationship reference RS of the TCI status with a specific identifier (ID) (e.g., DL / UL RS) or / and QCL type-D RS can be used as the reference RS for the DL receive beam and the UL transmit beam.

[0308] iv) A method for configuring / indicating multiple precoders (e.g., TPMI indication, SRI indication) for multiple PUSCH TOs

[0309] In existing NR systems, "codebook" and "non-codebook" can be semi-statically configured for "txConfig," which configures the terminal's UL transmission mode. Fields of the PUSCH precoder sent by the base station to the terminal (e.g., TPMI field, SRI field) can vary according to the corresponding configuration. According to this disclosure, in examples (including purposes other than M-TRP PUSCH transmission), a UL transmission mode referred to as "m-trpPUSCH" (or "hybrid") can be configured in "txConfig." A method for indicating the precoder of the PUSCH scheduling DCI (or a method for indicating each precoder of the M-TRP PUSCH) through corresponding configuration is also proposed below. In other words, as a method for indicating the precoder of the M-TRP PUSCH, the following method is proposed to indicate the precoder by dividing the case into multiple SRS resource sets sent for each TRP's UL channel estimation / UL link adaptation / SRS resources being 1) SRS entirely for CB, 2) complete SRS for NCB, and 3) a mixture of SRS for CB and NCB.

[0310] - When all are SRS used for CB

[0311] As the simplest approach, the number of TPMI fields, which is the same as the number of PUSCH TOs, can be variable for M-TRP scheduling DCI. In other words, the number of TPMI fields can be changed based on the number of PUSCH TOs. However, this has the drawback of arbitrarily increasing DCI overhead.

[0312] Therefore, the TPMI field in DCI remains as a single field, and an operation is proposed whereby the TRI / TPMI value indicated by the TPMI field is shared among PUSCH TOs based on a specific rule (rule-based) (i.e., the precoder corresponding to the TPMI value is segmented and applied to the Tx beam corresponding to each PUSCH TO). This operation can be applied to a transmission scheme where the data layer of all M-TRP PUSCHs shares the layer according to each PUSCH TO. For example, when there are two PUSCH TOs and the rank-4 PMI = 2, the first and second precoder vectors (rank = 2) with PMI = 2 can be applied to the Tx beam of the first TO, and the remaining vectors can be applied to the Tx beams of the other TOs.

[0313] Here, because the mapping between PUSCH TO and Tx beam / PC (power control) is determined, a mapping between PUSCH TO and precoding vectors can also be established for precoding vectors. For example, for operations that share all PUSCH layers across each PUSCH TO, a partially coherent or incoherent codebook can be used for TPMI indication. Additionally, when the total number of PUSCH layers exceeds 4 rank, the LTE / NR DL 8-port codebook can be used to support operations that share the total number of layers across PUSCH TOs.

[0314] Alternatively, the maximum rank per TRP or PUSCH TO may be finite (e.g., 2 ranks) for the number of layers shared by each TRP or PUSCH TO. In this case, the accurate rank and precoder can be indicated by configuring as many TRI+TPMI fields as per PUSCH TO for scheduling in the DCI payload. Additionally, wasted bits in the corresponding fields can be reduced. For example, {TRI_1+TPMI_1} for TRP 1 PUSCH TO + {TRI_2+TPMI_2} for TRP 2 PUSCH TO can be configured in the DCI. Thus, when multiple TOs share the precoder vector indicated by TPMI, each TO can share the precoder vector symmetrically (the same number), or asymmetrically (i.e., different numbers, e.g., 3+1 / 1+3 for rank 4).

[0315] Here, for all M-TRP PUSCH data layers, there can be overlapping data layers according to PUSCH TO. In this case, for overlapping layers, it can be pre-configured / indicated which layer or which vector it is, so that the same precoding vector is applied to each TO. For example, when data layers 1, 2, and 3 are transmitted in the first PUSCH TO and data layers 3 and 4 are transmitted in the second PUSCH TO, the base station pre-configures / indicates / updates layer 3 as an overlapping layer or precoding layer before scheduling, thus defining / configuring terminal operation.

[0316] Regarding the above-described operation of sharing a layer per PUSCH TO, when configuring the SRS resource set / SRS resource for M-TRP PUSCH scheduling, there may be an effect where the number of layers toward a particular TRP is pre-configured based on the number of ports configured in the SRS resource configuration for CB. Alternatively, the number of layers toward each TRP can be configured / indicated in the pre-configuration of PUSCH TO or DCI scheduling.

[0317] Alternatively, for a total of M-TRP PUSCH data layers, the operation can be performed in a repetitive manner, transmitting all data layers separately for each PUSCH TO. In this case, the TPMI field indicated in the DCI can be applied to the Tx beam corresponding to a specific basic TO. Furthermore, different precoding vectors orthogonalized by the precoder indicated by the TPMI can be applied to the Tx beam corresponding to non-basic TOs. Such orthogonalization can be pre-defined using formulas. Alternatively, the orthogonalization process can be defined as TPMIs identified as TPMI candidates that exist in the null space of the TPMI precoder indicated in the DCI. In another example, the base station can pre-configure / indicate the offset values ​​for TPMI values ​​of other TOs based on the TPMI index of the basic TO, and the TPMI values ​​of TOs other than the basic TO can be configured / indicated using the offset of the basic TO and the TPMI index. In another example, since each TO transmits a different panel and / or transmits a different beam, the basic TPMI field can be applied equally to all TOs.

[0318] For the operations described above, namely the M-TRP PUSCH TO shared total data layer operation and the operation of repeating the total data layer with each PUSCH TO, which operation should be performed by the terminal can be indicated by the base station's pre-configuration / update (i.e., RRC / MAC signaling). Alternatively, the switching between the two operations can be indicated by a specific field of the M-TRP PUSCH scheduling DCI.

[0319] - When all are SRS used for NCB

[0320] For existing NRs, the maximum number of layers (Lmax) can be configured via the terminal's UL maximum layer capability or the maximum layer configuration (e.g., maxMIMO-Layers). Furthermore, the value of the SRI field in the DCI used for NCB PUSCH scheduling is changed by the maximum number of layers for each layer and the number of SRS resources in the SRS resource set used for CB. This disclosure proposes an operation where each PUSCH TO shares the Lmax value or the Lmax value for each PUSCH TO is configured separately.

[0321] First, the base station can configure the sum of the SRS resource values ​​allocated to all PUSCH TOs as the Lmax value by configuring / defining the number of SRS resources (configured for UL channel estimation / UL link adaptation) corresponding to each PUSCH. Through this operation, each PUSCH TO can share the Lmax value. Furthermore, enhanced operations are possible while maintaining the bit fields of the existing NCB's SRI field as is. Additionally, the base station and the terminal can have a common understanding of which PUSCH TO each RSR resource corresponds to through Embodiments 1 and 3, thus having the advantage of avoiding ambiguity.

[0322] Next, the base station can configure / define the Lmax value corresponding to each PUSCH TO separately using other methods. In this way, the base station can indicate the SRI corresponding to each PUSCH TO via the DCI (e.g., the SRI for combining the total number of layers in Lmax 1 and Lmax 2). In this case, when indicating the SRI field for each PUSCH TO, there may not be an SRI indicated for any particular TO at all, thus the advantage is that single TRP transmission becomes possible (e.g., when the indication is performed in Lmax 2 instead of Lmax 1, it becomes a single TRP PUSCH toward TRP 2). Here, when there is no SRI indicated for any particular TO, it may mean that the corresponding DCI includes only a single SRI field. Alternatively, when there is no SRI indicated for any particular TO, it may mean that there are multiple SRI fields in the corresponding DCI, but the specific code point for which the corresponding SRI field is disabled / turned off is indicated by any one of them. In this case, the PUSCH for each TO can be sent based on the SRS resources in the SRS resource set associated with each TO, i.e., identified by the enabled SRI field (i.e., the SRI field indicating code points other than those used for the specific code points to be disabled / turned off).

[0323] Additionally, the SRI field can indicate the SRI used for the base PUSCH TO, and the SRI used for a TO other than the base PUSCH TO can be indicated by an SRS resource with the same index. For example, when indicating the nth SRS resource in the SRS resource set of the NCB corresponding to the base PUSCH TO, the nth SRS resource can be indicated in the SRS resource set of the NCB corresponding to the corresponding TO, or it can be indicated in other TOs. Here, it is necessary to always satisfy the condition that the number of SRS resources selected in the base TO is the same as the number of SRS resources selected in other TOs. Through this operation, the selection of SRS resources for multiple TOs can be jointly indicated in a single SRI field, thus having the advantage of reducing the bit field size of the SRI field.

[0324] - When SRS for CB and SRS for NCB are mixed

[0325] When a UL transmission mode called “m-trpPUSCH” (or “hybrid”) (e.g., “txConfig”) is configured, or when M-TRP PUSCH scheduling is performed based on a hybrid SRS resource set / SRS resource configuration for CB and NCB, the following operations between the base station and the terminal are possible.

[0326] Based on methods 1 and 2, the base station can allocate only one SRS resource from the SRS resource set used for CB to the terminal. Here, the SRI field of the DCI used for M-TRP (or hybrid) PUSCH scheduling can be mapped to the SRS resource in the SRS resource set used for NCB, and the TPMI field of the corresponding DCI can be defined for CB. In other words, the SRI field indicated by the SRI for NCB and the TPMI field indicated by the precoder for CB can coexist in the DCI. Through this operation, the terminal can indicate the precoder ( / Tx (analog) beam) for CB / NCB respectively via the DCI, which will be applied to each PUSCH TO.

[0327] v) A method for configuring / indicating multiple MCS for multiple PUSCH TOs

[0328] For M-TRP scheduling DCI, the MCS field can be variable based on the number of PUSCH TOs. However, this has the drawback of arbitrarily increasing DCI overhead. Therefore, the MCS for a specific base PUSCH TO can be dynamically indicated through the MCS field of the existing DCI. The MCS offset value relative to the PUSCH TO MCS value, which can become the corresponding standard, can be configured via higher-layer signaling such as RRC / MAC-CE. Therefore, other TO MCSs besides the base PUSCH TO can be configured / indicated to the terminal as the base MCS + offset value. Each MCS value can be used for data transmission toward each TRP and is characterized by being mapped to a different PUSCH TO.

[0329] Alternatively, similar to the way two MCSs are indicated by codewords when indicating the MCS of a base station in existing LTE systems, the base station can simply indicate the same number of MCSs as the number of PUSCH TOs per TRP.

[0330] For each embodiment, it is evident that each different method can be applied / utilized independently for operation between the base station and the terminal, and furthermore, can be applied / utilized in combination of one or more specific embodiments and specific methods.

[0331] Figure 9 This is a diagram illustrating the signaling process between a network and a terminal in a method for sending and receiving PUSCH according to an embodiment of the present disclosure.

[0332] Figure 9 This refers to the signaling between the network (e.g., TRP 1 / TRP 2) and the UE in cases where the methods proposed in this disclosure (e.g., proposals 1 / 2 / 3 / 4, etc.) can be applied (i.e., M-TRP, or multiple cells, where all TRPs can be replaced by cells in the following text). Here, UE / network is merely an example and can be replaced by alternatives such as... Figure 12 and Figure 13 (The various devices described herein shall be used). Figure 9 This is merely for the convenience of description and does not limit the scope of the invention.

[0333] refer to Figure 9 For ease of description, signaling between two TRPs and the UE is considered; however, it is self-evident that the corresponding signaling methods can be extended and applied to signaling between multiple TRPs and multiple UEs. In the following description, the network can be a base station comprising multiple TRPs or a cell comprising multiple TRPs. In the example, ideal / non-ideal backhaul can be configured between TRP 1 and TRP 2 in the network configuration. Furthermore, the following description is based on multiple TRPs, but it can be similarly extended and applied to transmissions through multiple panels. Additionally, in this disclosure, the operation of the terminal receiving signals from TRP1 / TRP2 can be interpreted / described as the operation of the terminal receiving signals from the network (through / utilizing TRP1 / 2) (or may be an operation), and the operation of the terminal sending signals to TRP1 / TRP2 can be interpreted / described as the operation of the terminal sending signals to the network (through / utilizing TRP1 / TRP2) (or may be an operation), or it can be interpreted / described conversely.

[0334] The UE can receive SRS-related configuration information S901 from the network via / using TRP1 and / or TRP2.

[0335] Here, SRS-related configuration information can be sent to higher layers (e.g., RRC or MAC CE). Alternatively, when SRS-related configuration information is predefined or pre-configured, the corresponding steps can be omitted.

[0336] According to method 1, the SRS-related configuration information may include information about multiple SRS resource sets corresponding to each TRP. Here, the multiple SRS resource sets may i) include only SRS resource sets for codebooks, or ii) include only SRS resource sets for non-codebooks, or iii) include one or more SRS resource sets for codebooks and one or more SRS resource sets for non-codebooks.

[0337] Additionally, according to method 2, the SRS-related configuration information may include information about multiple SRS resources corresponding to each TRP (e.g., in a set of SRS resources). Here, the multiple SRS resources may i) include only SRS resources for the codebook, or ii) include only SRS resources for non-codebooks, or iii) include one or more SRS resources for the codebook and one or more SRS resources for non-codebooks.

[0338] Additionally, according to Embodiment 1, the SRS-related configuration information may include the receiving cell ID (or TRP ID) for the SRS resource set. Furthermore, it may include the receiving cell ID (or TRP ID) for the SRS resources.

[0339] Additionally, according to Embodiment 4, the SRS-related configuration information may include parameter configurations (TA, Tx beam, PC parameters, precoder, MCS, etc.) related to the transmission of multiple PUSCH TOs.

[0340] Although Figure 9 Although not shown in the diagram, the terminal can send SRS to different TRPs according to the SRS resource set based on the configuration information received in S901, and in addition, it can send SRS to different TRPs according to the SRS resource.

[0341] The UE can receive configuration information S902 related to PUSCH transmission from the network via / using TRP1 and / or TRP2.

[0342] Here, configuration information related to PUSCH transport can be sent to a higher layer (e.g., RRC or MAC CE). Alternatively, when the configuration information related to PUSCH transport is predefined or preconfigured, the corresponding steps can be omitted.

[0343] According to Embodiment 2, since the M-TRP PUSCH configuration (e.g., "m-trpPUSCH" or "hybrid") is defined as one of the UL transmission modes, the configuration information related to PUSCH transmission can include the M-TRP PUSCH configuration. The M-TRP PUSCH configuration (e.g., "m-trpPUSCH" or "hybrid") can refer to a transmission mode that performs transmission based on multiple SRS resource sets or multiple SRS resources.

[0344] Additionally, according to Embodiment 4, the configuration information related to PUSCH transmission may include parameter configurations (TA, Tx beam, PC parameters, precoder, MCS, etc.) related to the transmission of multiple PUSCH TOs.

[0345] The terminal can receive DCI S903 for PUSCH scheduling from the network via / using TRP 1 (and / or TRP 2).

[0346] Here, the DCI used for PUSCH scheduling may include scheduling information for PUSCH transmissions in N (N is a natural number) TOs used for M-TRP.

[0347] Additionally, the DCI used for PUSCH scheduling may include a single SRI field. Alternatively, multiple SRI fields may exist in the corresponding DCI, but the specific code point of the corresponding SRI field to be disabled / turned off can be indicated by any of them.

[0348] Here, according to Embodiment 2, the DCI used for PUSCH scheduling can be sent in the CORESET and / or search space set when the PUSCH is configured to be sent based on multiple SRS resource sets (or multiple SRS resources) (i.e., configured for M-TRP PUSCH transmission). Alternatively, the DCI used for PUSCH scheduling can be sent based on the RNTI and / or DCI format configured / defined for the PUSCH to be sent based on multiple SRS resource sets (or multiple SRS resources) (i.e., configured / defined for PUSCH transmission).

[0349] Here, according to embodiment 3, the DCI for PUSCH scheduling may include scheduling information (e.g., repeated transmission of PUSCH or partitioned transmission of PUSCH) about the transmission of multiple PUSCHs toward a single TRP or multiple TRPs in N (N is a natural number) TOs of PUSCH.

[0350] Additionally, according to Embodiment 4, the DCI used for PUSCH scheduling may include precoder information (e.g., TPMI, SRI fields) and / or MCS indication information regarding the transmission of multiple PUSCHs toward a single TRP or multiple TRPs in N (N is a natural number) TOs. Furthermore, the configuration on the code points of the SRI field can be defined differently depending on whether the transmission mode of transmitting PUSCHs based on multiple SRS resource sets (i.e., M-TRPPUSCH transmission mode) is enabled.

[0351] The terminal can send DCI-based PUSCH to a single TRP or multiple TRPs (i.e., TRP 1 and 2) S904, S905.

[0352] Here, PUSCH can be sent over N (N is a natural number) TOs (transmission times). As mentioned above, PUSCH can be sent alternately (i.e., cyclically, sequentially) to each TRP according to each TO. Alternatively, multiple adjacent TOs can be grouped, and PUSCH can be sent alternately (i.e., cyclically, sequentially) to each TRP according to each TO group.

[0353] Here, according to an embodiment, in each TO (or each TO group), PUSCH can be transmitted based on SRS resources in an SRS resource set identified by one of a plurality of SRI fields associated with each TO (or each TO group). Specifically, power control parameters for PUSCH transmission for each TO (or each TO group) and / or reference signals referenced for PUSCH transmission can be determined based on the configuration of the SRS resource set associated with each TO (or each TO group).

[0354] Furthermore, according to the embodiments, the power control parameters for PUSCH transmission for each TO (or each TO group) and / or the reference signals referenced for PUSCH transmission can be indicated by the SRI field associated with each TO (or each TO group).

[0355] Furthermore, according to embodiments, the precoder for PUSCH transmission for each TO (or each TO group) can be determined based on the TPMI field in the DCI or the SRI field associated with each TO (or each TO group).

[0356] Alternatively, PUSCH for each TO can be sent based on SRS resources in an SRS resource set identified by an enabled SRI field among multiple SRI fields associated with each TO.

[0357] In relation to Figure 9 Although not specifically described in the description, the descriptions of Examples 1, 2, 3, and 4 can also be applied. Figure 9 The operation.

[0358] As described above, the network / UE signaling and operations (e.g., Examples 1 / 2 / 3 / 4) Figure 9 (etc.) can be generated by a device (e.g., Figure 12 and Figure 13 This will be implemented as described below. For example, the network (e.g., TRP1 / TRP2) may correspond to the first wireless device and the UE may correspond to the second wireless device, and in some cases, the reverse may also be considered.

[0359] For example, the network / UE signaling and operations described above (e.g., Examples 1 / 2 / 3 / 4, ... Figure 9(etc.) can be made by Figure 12 and Figure 13 One or more processors (102, 202) in the system process the data. Furthermore, the aforementioned network / UE signaling and operations (e.g., embodiments 1 / 2 / 3 / 4) are also processed. Figure 9 (etc.) can be used for operation Figure 12 and Figure 13 At least one processor (e.g., 102, 202) stores commands / programs (e.g., instructions, executable code) in memory (e.g., ...). Figure 12 and Figure 13 One or more memories (104, 204)).

[0360] Figure 10 This is a diagram illustrating the operation of a terminal for sending a PUSCH method according to an embodiment of the present disclosure.

[0361] Figure 10 The illustrations show the operation of the terminal based on Examples 1 to 4. Figure 10 The examples provided are for illustrative purposes only and do not limit the scope of this disclosure. Figure 10 Some steps illustrated in the diagram may be omitted depending on the situation and / or configuration. Furthermore, the terminal is merely... Figure 10 One example, and can be derived from the following Figure 12 and Figure 13 The device illustrated in the diagram is used to achieve this. For example, Figure 12 and Figure 13 The processor (102 / 202) in the system can be controlled to send and receive channels / signals / data / information, etc., by using transceivers (106 / 206), and can be controlled to store channels / signals / data / information, etc., that will be sent or received in memory (104 / 204).

[0362] in addition, Figure 10 The operation can be performed by Figure 12 and Figure 13 One or more processors (102, 202) process it. Additionally, Figure 10 The operation can be used for operation Figure 12 and Figure 13 At least one processor (e.g., 102, 202) stores commands / programs (e.g., instructions, executable code) in memory (e.g., ...). Figure 12 and Figure 13 In one or more memories (104, 204).

[0363] The terminal receives SRS-related configuration information (first configuration information) from the base station S1001.

[0364] Here, SRS-related configuration information can be sent to higher layers (e.g., RRC or MAC CE). Additionally, when the SRS-related configuration information is predefined or pre-configured, the corresponding steps can be omitted.

[0365] According to Method 1, the SRS-related configuration information may include information about multiple SRS resource sets corresponding to each TRP. Here, the multiple SRS resource sets may i) include only SRS resource sets for codebooks, or ii) include only SRS resource sets for non-codebooks, or iii) include one or more SRS resource sets for codebooks and one or more SRS resource sets for non-codebooks.

[0366] Additionally, according to method 2, the SRS-related configuration information may include information about multiple SRS resources corresponding to each TRP (e.g., in a set of SRS resources). Here, the multiple SRS resources may i) include only SRS resources for the codebook, or ii) include only SRS resources for non-codebooks, or iii) include one or more SRS resources for the codebook and one or more SRS resources for non-codebooks.

[0367] Additionally, according to Embodiment 1, the SRS-related configuration information may include the receiving cell ID (or TRP ID) for the SRS resource set. Alternatively, it may include the receiving cell ID (or TRP ID) for the SRS resource.

[0368] Additionally, according to Embodiment 4, the SRS-related configuration information may include parameter configurations (TA, Tx beam, PC parameters, precoder, MCS, etc.) related to the transmission of multiple PUSCH TOs.

[0369] exist Figure 10 Although not shown in the diagram, the terminal can send SRS to different TRPs according to the SRS resource set based on the configuration information received in S1001, and in addition, it can send SRS to different TRPs according to the SRS resource.

[0370] The terminal can receive configuration information (second configuration information) S1002 related to PUSCH transmission from the base station.

[0371] Here, configuration information related to PUSCH transport can be sent to a higher layer (e.g., RRC or MAC CE). Alternatively, when the configuration information related to PUSCH transport is predefined or preconfigured, the corresponding steps can be omitted.

[0372] According to Embodiment 2, since the M-TRP PUSCH configuration (e.g., "m-trpPUSCH" or "hybrid") is defined as one of the UL transmission modes, the configuration information related to PUSCH transmission may include the M-TRP PUSCH configuration. The M-TRP PUSCH configuration (e.g., "m-trpPUSCH" or "hybrid") may refer to a transmission mode that performs transmission based on multiple SRS resource sets or multiple SRS resources.

[0373] Additionally, according to Embodiment 4, the configuration information related to PUSCH transmission may include parameter configurations (TA, Tx beam, PC parameters, precoder, MCS, etc.) related to the transmission of multiple PUSCH TOs.

[0374] The terminal receives DCI for PUSCH scheduling from base station S1003.

[0375] Here, the DCI used for PUSCH scheduling may include scheduling information for PUSCH transmissions at N (N is a natural number) TOs for M-TRP.

[0376] Additionally, the DCI used for PUSCH scheduling may include a single SRI field. Alternatively, multiple SRI fields may exist in the corresponding DCI, but the specific code point of the corresponding SRI field to be disabled / turned off can be indicated by any of them.

[0377] Here, according to Embodiment 2, the DCI for PUSCH scheduling can be sent within the CORESET and / or search space set where the PUSCH is configured to be sent based on multiple SRS resource sets (or multiple SRS resources) (i.e., for M-TRP PUSCH transmission configuration). Alternatively, the DCI for PUSCH scheduling can be sent based on the RNTI and / or DCI format where the PUSCH is configured / defined as being based on multiple SRS resource sets (or multiple SRS resources) (i.e., for M-TRP PUSCH transmission configuration / definition).

[0378] Here, according to embodiment 3, the DCI for PUSCH scheduling may include scheduling information (e.g., repeated transmission of PUSCH or partitioned transmission of PUSCH) about the transmission of multiple PUSCHs toward a single TRP or multiple TRPs at N (N is a natural number) TOs of PUSCH.

[0379] Furthermore, according to Embodiment 4, the DCI used for PUSCH scheduling may include precoder information (e.g., TPMI, SRI fields) and / or MCS indication information regarding the transmission of multiple PUSCHs toward a single TRP or multiple TRPs at N (N is a natural number) TOs. Additionally, the configuration on the code points of the SRI field can be defined differently depending on whether a transmission mode based on multiple SRS resource sets for transmitting PUSCHs (i.e., M-TRPPUSCH transmission mode) is enabled.

[0380] The terminal sends the PUSCH to the base station S1004.

[0381] Here, PUSCH can be sent at N (N is a natural number) TOs (transmission points). As mentioned above, PUSCH can be sent alternately (i.e., cyclically, sequentially) to each TRP according to each TO. Alternatively, multiple adjacent TOs can be grouped, and PUSCH can be sent alternately (i.e., cyclically, sequentially) to each TRP according to each TO group.

[0382] Here, according to an embodiment, for each TO (or each TO group), PUSCH can be transmitted based on SRS resources in an SRS resource set identified by one of a plurality of SRI fields associated with each TO (or each TO group). Specifically, power control parameters for PUSCH transmission for each TO (or each TO group) and / or reference signals referenced for PUSCH transmission can be determined based on the configuration of the SRS resource set associated with each TO (or each TO group).

[0383] Additionally, according to an embodiment, the power control parameters for PUSCH transmission for each TO (or each TO group) and / or the reference signal referenced for PUSCH transmission can be indicated by the SRI field associated with each TO (or each TO group).

[0384] Additionally, according to an embodiment, the precoder for PUSCH transmission for each TO (or each TO group) can be determined based on the TPMI field in the DCI or the SRI field associated with each TO (or each TO group).

[0385] In addition, PUSCH for each TO can be sent based on SRS resources in an SRS resource set identified by an enabled SRI field among multiple SRI fields associated with each TO.

[0386] In relation to Figure 10 Although not specifically described in the description, the descriptions in Examples 1, 2, 3, and 4 can be applied. Figure 10 The operation.

[0387] Figure 11 This is a diagram illustrating the operation of a base station for transmitting a PUSCH method according to an embodiment of the present disclosure.

[0388] Figure 11 This is a diagram illustrating the operation of a base station based on embodiments 1 to 4. Figure 11 The examples are for illustrative purposes only and do not limit the scope of this disclosure. Figure 11 Some steps illustrated in the diagram may be omitted depending on the situation and / or configuration. Furthermore, the base station is merely... Figure 11 One example, and can be derived from the following Figure 12 This is achieved using the device illustrated in the diagram. For example, Figure 12 The processor 102 / 202 can be controlled to send and receive channels / signals / data / information, etc. by using transceiver 106 / 206, and can be controlled to store the channels / signals / data / information, etc. to be sent or received in memory 104 / 204.

[0389] in addition, Figure 11 The operation can be performed by Figure 12 One or more processors 102 and 202 process it. Additionally, Figure 11 The operation can be used for operation Figure 12 At least one processor (e.g., 102, 202) has its commands / programs (e.g., instructions, executable code) stored in memory (e.g., ...). Figure 12 In one or more memories (104 and 204).

[0390] The base station sends the SRS-related configuration information (first configuration information) to the terminal S1101.

[0391] Here, SRS-related configuration information can be sent to higher layers (e.g., RRC or MAC CE). Additionally, when the SRS-related configuration information is predefined or pre-configured, the corresponding steps can be omitted.

[0392] According to method 1, the SRS-related configuration information may include information about multiple SRS resource sets corresponding to each TRP. Here, the multiple SRS resource sets may i) include only SRS resource sets for codebooks, or ii) include only SRS resource sets for non-codebooks, or iii) include one or more SRS resource sets for codebooks and one or more SRS resource sets for non-codebooks.

[0393] Additionally, according to method 2, the SRS-related configuration information may include information about multiple SRS resources (e.g., in a set of SRS resources) corresponding to each TRP. Here, the multiple SRS resources may i) include only SRS resources for the codebook, or ii) include only SRS resources for non-codebooks, or iii) include one or more SRS resources for the codebook and one or more SRS resources for non-codebooks.

[0394] Additionally, according to Embodiment 1, the SRS-related configuration information may include the receiving cell ID (or TRP ID) for the SRS resource set. Alternatively, it may include the receiving cell ID (or TRP ID) for the SRS resource.

[0395] Additionally, according to Embodiment 4, the SRS-related configuration information may include parameter configurations (TA, Tx beam, PC parameters, precoder, MCS, etc.) related to the transmission of multiple PUSCH TOs.

[0396] exist Figure 11 Although not shown, the base station can receive SRS or SRS resources from the SRS resource set from the terminal.

[0397] The base station can send configuration information (second configuration information) related to PUSCH transmission to terminal S1102.

[0398] Here, configuration information related to PUSCH transport can be sent to a higher layer (e.g., RRC or MAC CE). Alternatively, when the configuration information related to PUSCH transport is predefined or preconfigured, the corresponding steps can be omitted.

[0399] According to Embodiment 2, since the M-TRP PUSCH configuration (e.g., "m-trpPUSCH" or "hybrid") is defined as one of the UL transmission modes, the configuration information related to PUSCH transmission may include the M-TRP PUSCH configuration. The M-TRP PUSCH configuration (e.g., "m-trpPUSCH" or "hybrid") may refer to a transmission mode that performs transmission based on multiple SRS resource sets or multiple SRS resources.

[0400] Additionally, according to Embodiment 4, the configuration information related to PUSCH transmission may include parameter configurations (TA, Tx beam, PC parameters, precoder, MCS, etc.) related to the transmission of multiple PUSCH TOs.

[0401] The base station sends the DCI used for PUSCH scheduling to the terminal S1103.

[0402] Here, the DCI used for PUSCH scheduling may include scheduling information for PUSCH transmissions at N (N is a natural number) TOs for M-TRP.

[0403] Additionally, the DCI used for PUSCH scheduling may include a single SRI field. Alternatively, multiple SRI fields may exist in the corresponding DCI, but the specific code point of the corresponding SRI field to be disabled / turned off can be indicated by any of them.

[0404] Here, according to Embodiment 2, the DCI for PUSCH scheduling can be sent within a CORESET and / or search space set where the PUSCH is configured to be sent based on multiple SRS resource sets (or multiple SRS resources) (i.e., configured for M-TRP PUSCH transmission). Alternatively, the DCI for PUSCH scheduling can be sent based on the RNTI and / or DCI format configured / defined for the PUSCH to be sent based on multiple SRS resource sets (or multiple SRS resources) (i.e., configured / defined for M-TRP PUSCH transmission).

[0405] Here, according to embodiment 3, the DCI for PUSCH scheduling may include scheduling information (e.g., repeated transmission of PUSCH or partitioned transmission of PUSCH) about the transmission of multiple PUSCHs toward a single TRP or multiple TRPs at N (N is a natural number) TOs of PUSCH.

[0406] Furthermore, according to Embodiment 4, the DCI used for PUSCH scheduling may include precoder information (e.g., TPMI, SRI fields) and / or MCS indication information regarding the transmission of multiple PUSCHs toward a single TRP or multiple TRPs at N (N is a natural number) TOs. Additionally, the configuration on the code points of the SRI field can be defined differently depending on whether a transmission mode based on multiple SRS resource sets for transmitting PUSCHs (i.e., M-TRPPUSCH transmission mode) is enabled.

[0407] The base station receives PUSCH S1104 from the terminal.

[0408] Here, PUSCH can be transmitted at N (N is a natural number) TOs (transmission points). As described above, PUSCH can be transmitted alternately (i.e., cyclically, sequentially) to each TRP according to each TO. Here, when the base station is a single TRP, the base station can receive PUSCH in the TO corresponding to itself. Alternatively, multiple adjacent TOs can be grouped, and PUSCH can be transmitted alternately (i.e., cyclically, sequentially) to each TRP according to each TO group. Here, when the base station is a single TRP, the base station can receive PUSCH in the TO group corresponding to itself.

[0409] Here, according to an embodiment, for each TO (or each TO group), PUSCH can be transmitted based on SRS resources in an SRS resource set identified by one of a plurality of SRI fields associated with each TO (or each TO group). Specifically, power control parameters for PUSCH transmission for each TO (or each TO group) and / or reference signals referenced for PUSCH transmission can be determined based on the configuration of the SRS resource set associated with each TO (or each TO group).

[0410] Furthermore, according to the embodiments, the power control parameters for PUSCH transmission for each TO (or each TO group) and / or the reference signals referenced for PUSCH transmission can be indicated by the SRI field associated with each TO (or each TO group).

[0411] Furthermore, according to embodiments, the precoder for PUSCH transmission for each TO (or each TO group) can be determined based on the TPMI field in the DCI or the SRI field associated with each TO (or each TO group).

[0412] In addition, PUSCH for each TO can be sent based on SRS resources in an SRS resource set identified by an enabled SRI field among multiple SRI fields associated with each TO.

[0413] In relation to Figure 11 Although not specifically described in the description, the descriptions in Examples 1, 2, 3, and 4 can be applied. Figure 11 The operation.

[0414] The general-purpose devices disclosed herein can be used.

[0415] Figure 12 This is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure.

[0416] refer to Figure 12 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).

[0417] 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 processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor 102 may transmit a wireless signal including the first information / signal via the transceiver 106 after generating first information / signal by processing information in the memory 104. Furthermore, the processor 102 may receive a wireless signal including a second information / signal via the transceiver 106, and then store information obtained through signal processing of the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information relating to the operation of the processor 102. For example, the memory 104 may store software code including commands for performing all or part of the processes controlled by the processor 102 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. 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.

[0418] 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 processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure. For example, the processor 202 may generate third information / signals by processing information in the memory 204, and then transmit a wireless signal including the third information / signals via the transceiver 206. Additionally, the processor 202 may receive wireless signals including fourth information / signals via the transceiver 206, and then store information obtained through signal processing of the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including commands for executing all or part of the processes controlled by the processor 202 or for executing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed 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.

[0419] The hardware components of wireless devices 100 and 200 will be described in more detail below. However, they are not limited to this; 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, proposals, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, processes, proposals, and / or methods disclosed in this disclosure to provide them to one or more transceivers 106 and 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, proposals, methods, and / or operation flowcharts disclosed in this disclosure.

[0420] 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. In examples, 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, proposals, methods, and / or operation flowcharts disclosed 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, proposals, methods, and / or operation flowcharts disclosed 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, proposals, methods, and / or operation flowcharts disclosed in this invention may be implemented by firmware or software in the form of code, commands, and / or command sets.

[0421] One or more memories 104, 204 may be connected to one or more processors 102, 202 and are capable of storing 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, digital 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.

[0422] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or operation flowcharts, etc., disclosed herein 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, proposals, methods, and / or operation flowcharts disclosed herein 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. Furthermore, 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. Furthermore, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein through one or more antennas 108, 208. In this invention, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may process the received wireless signals / channels, etc., by converting them from RF band signals to baseband signals using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, wireless signals / channels, etc., processed by using one or more processors 102, 202 from baseband signals to RF band signals. Therefore, the one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0423] Figure 13 The illustration shows a vehicle device according to an embodiment of the present disclosure.

[0424] refer to Figure 13 The vehicle 100 may include a communication unit 110, a control unit 120, a memory unit 130, an input and output unit 140a, and a positioning unit 140b.

[0425] The communication unit 110 can send and receive signals (e.g., data, control signals, etc.) with external devices or base stations of other vehicles. The control unit 120 can perform various operations by controlling the components of the vehicle 100. The control unit 120 can control the memory unit 130 and / or the communication unit 110, and can be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this disclosure. The memory unit 130 can store data / parameters / programs / codes / commands supporting various functions of the vehicle 100. The input and output unit 140a can output AR / VR objects based on the information in the memory unit 130. The input and output unit 140a may include a HUD. The positioning unit 140b can obtain the position information of the vehicle 100. The position information may include the absolute position information of the vehicle 100, the position information in the driving lane, acceleration information, position information relative to surrounding vehicles, etc. The positioning unit 140b may include GPS and various sensors.

[0426] In the example, the communication unit 110 of vehicle 100 can receive map information, traffic information, etc., from an external server and store them in the memory unit 130. The positioning unit 140b can obtain vehicle location information through GPS and various sensors and store it in the memory unit 130. The control unit 120 can generate virtual objects based on map information, traffic information, and vehicle location information, and the input and output unit 140a can indicate the generated virtual objects on the windows of vehicles 1410 and 1420. In addition, the control unit 120 can determine whether vehicle 100 is operating normally in the driving lane based on vehicle location information. When vehicle 100 is abnormally outside the driving lane, the control unit 120 can indicate a warning on the vehicle windows through the input and output unit 140a. In addition, the control unit 120 can send warning messages about abnormal driving to surrounding vehicles through the communication unit 110. Depending on the situation, the control unit 120 can send vehicle location information and information about driving / vehicle problems to relevant agencies through the communication unit 110.

[0427] 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 can be implemented without combination with other elements or features. Furthermore, embodiments of this disclosure may include combinations of certain elements and / or features. The order of operations described in the 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. It is clear that embodiments may include combinations of claims where there is no explicit dependency in the claims, or may be included as new claims by amendment after the application.

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

[0429] 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 store such software or commands and are executable in the 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 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. Alternatively, the non-volatile memory devices in the memory may 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 results from 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.

[0430] Here, 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. Alternatively, the wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may perform communication based on LTE-M technology. Here, in examples, 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 the following standards: 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, and is not limited to the aforementioned names. Alternatively, the wireless communication technology 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 it is not limited to the aforementioned names. In the example, ZigBee technology can generate a PAN (Personal Area Network) associated with small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0431] [Industrial Availability]

[0432] The method proposed in this invention is mainly described using 3GPP LTE / LTE-A and 5G systems as examples, but it can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method comprising: The terminal receives first configuration information related to a sounding reference signal (SRS) from a base station, wherein the first configuration information includes information for multiple SRS resource sets; The terminal receives downlink control information from the base station for scheduling the PUSCH (Physical Uplink Shared Channel); as well as The terminal sends the PUSCH to the base station based on the downlink control information. The downlink control information includes multiple SRS Resource Indicator (SRI) fields, and each of the multiple SRI fields is associated with one of the multiple SRS resource sets. Specifically, the PUSCH is repeatedly sent in N (N is an integer greater than 1) PUSCH repetitions. The N PUSCH repeats are grouped into PUSCH repeat groups, each consisting of consecutive PUSCH repeats. Specifically, based on sequence mapping, the plurality of SRS resource sets are respectively mapped to each of the PUSCH repeating groups, and Specifically, based on the sequential mapping between the plurality of SRS resource sets and the PUSCH repeating group, the plurality of SRI fields are applied to the PUSCH repeating group.

2. The method according to claim 1, further comprising: Receive second configuration information related to the PUSCH from the base station. The transmission mode for sending the PUSCH based on the multiple SRS resource sets is configured by the second configuration information.

3. The method according to claim 1, wherein, The PUSCH is configured to send the downlink control information based on the search space set and / or control resource set of the plurality of SRS resource sets.

4. The method according to claim 1, wherein, The PUSCH is configured to transmit the downlink control information based on the downlink control information format and / or RNTI (Radio Network Temporary Identifier) ​​of the plurality of SRS resource sets.

5. The method according to claim 1, wherein, The power control parameters for the transmission of the PUSCH and / or the reference signals referenced for the transmission of the PUSCH in the PUSCH repeating group are determined based on the sequential mapping between the plurality of SRS resource sets and the PUSCH repeating group.

6. The method according to claim 1, wherein, The power control parameters for the transmission of the PUSCH for each of the PUSCH repeat groups and / or the reference signals referenced for the transmission of the PUSCH are indicated by the SRI field associated with each of the PUSCH repeat groups.

7. The method according to claim 1, wherein, The precoder for transmission of the PUSCH for each of the PUSCH repeat groups is determined based on the SRI field associated with each of the PUSCH repeat groups or the Transmit Precoder Matrix Indicator (TPMI) field in the downlink control information.

8. The method according to claim 1, wherein, Configure the code point configuration for the SRI field according to the transmission mode of sending the PUSCH based on the multiple SRS resource sets.

9. The method according to claim 1, wherein, The plurality of SRS resource sets i) include only the SRS resource set used for codebook-based uplink transmission, or ii) include only the SRS resource set used for non-codebook-based uplink transmission.

10. A terminal, comprising: At least one transceiver, the at least one transceiver being used to transmit and receive wireless signals; as well as At least one processor, the at least one processor being used to control the at least one transceiver, Wherein, the at least one processor is configured to: Receive first configuration information related to a sounding reference signal (SRS) from a base station, wherein the first configuration information includes information for a plurality of SRS resource sets; Receive downlink control information from the base station for scheduling the PUSCH (Physical Uplink Shared Channel); and The PUSCH is sent to the base station based on the downlink control information. The downlink control information includes multiple SRS Resource Indicator (SRI) fields, and each of the multiple SRI fields is associated with one of the multiple SRS resource sets. Specifically, the PUSCH is repeatedly sent in N (N is an integer greater than 1) PUSCH repetitions. The N PUSCH repeats are grouped into PUSCH repeat groups, each consisting of consecutive PUSCH repeats. Specifically, based on sequence mapping, the plurality of SRS resource sets are respectively mapped to each of the PUSCH repeating groups, and Specifically, based on the sequential mapping between the plurality of SRS resource sets and the PUSCH repeating group, the plurality of SRI fields are applied to the PUSCH repeating group.

11. A method comprising: The base station sends first configuration information related to a sounding reference signal (SRS) to the terminal, wherein the first configuration information includes information for multiple SRS resource sets; The base station sends downlink control information to the terminal for scheduling the PUSCH (Physical Uplink Shared Channel); as well as The base station receives the PUSCH from the terminal. The downlink control information includes multiple SRS Resource Indicator (SRI) fields, and each of the multiple SRI fields is associated with one of the multiple SRS resource sets. Specifically, the PUSCH is received repeatedly in N (N is an integer greater than 1) PUSCH repetitions. The N PUSCH repeats are grouped into PUSCH repeat groups, each consisting of consecutive PUSCH repeats. Specifically, based on sequence mapping, the plurality of SRS resource sets are respectively mapped to each of the PUSCH repeating groups, and Specifically, based on the sequential mapping between the plurality of SRS resource sets and the PUSCH repeating group, the plurality of SRI fields are applied to the PUSCH repeating group.

12. A base station, comprising: At least one transceiver, the at least one transceiver being used to transmit and receive wireless signals; as well as At least one processor, the at least one processor being used to control the at least one transceiver, Wherein, the at least one processor is configured to: Sending first configuration information related to a sounding reference signal (SRS) to the terminal, wherein the first configuration information includes information for multiple SRS resource sets; Send downlink control information to the terminal for scheduling the PUSCH (Physical Uplink Shared Channel); and Receive the PUSCH from the terminal. The downlink control information includes multiple SRS Resource Indicator (SRI) fields, and each of the multiple SRI fields is associated with one of the multiple SRS resource sets. Specifically, the PUSCH is received repeatedly in N (N is an integer greater than 1) PUSCH repetitions. The N PUSCH repeats are grouped into PUSCH repeat groups, each consisting of consecutive PUSCH repeats. Specifically, based on sequence mapping, the plurality of SRS resource sets are respectively mapped to each of the PUSCH repeating groups, and Specifically, based on the sequential mapping between the plurality of SRS resource sets and the PUSCH repeating group, the plurality of SRI fields are applied to the PUSCH repeating group.

Images