Method and apparatus for performing uplink transmission and reception in communication system

Abstract

A method and an apparatus for performing uplink transmission and reception in a communication system are disclosed. A method performed by a terminal in a wireless communication system according to an embodiment disclosed herein comprises the steps of: receiving information on a configuration of an SRS resource set; the method comprises the following steps: receiving DCI (Downlink Control Information), wherein the DCI comprises a first PRS-DMRS port association field and a second PRS-DMRS port association field; and transmitting the PTRS on the basis of at least one of the first PTRS-DMRS port association field and the second PTRS-DMRS port association field. Here, based on the configuration of three PTRS ports for the terminal, the first PTRS-DMRS port association field may indicate information on one DMRS port associated with one PTRS port, and the second PTRS-DMRS port association field may indicate information on two DMRS ports associated with two PTRS ports.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for performing uplink transmission and reception in a wireless communication system. Background Art

[0002] A mobile communication system has been developed to provide voice services while ensuring user mobility. However, the mobile communication system has been extended to data services as well as voice services, and currently, the explosive growth of services has led to resource shortages, and users have demanded faster services, thus requiring more advanced mobile communication systems.

[0003] The overall requirements of the next generation mobile communication system should be able to support the accommodation of explosive data services, a significant increase in the transmission rate per user, the accommodation of a significantly increased number of connected devices, very low end-to-end latency and high energy efficiency. To this end, a variety of technologies such as dual connectivity, massive multiple-input multiple-output (massive MIMO), in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and device networking have been studied. Summary of the invention

[0004] Technical issues

[0005] A technical object of the present disclosure is to provide a method and apparatus for performing uplink transmission and reception in a wireless communication system.

[0006] In addition, an additional technical object of the present disclosure is to provide a method and apparatus for configuring / indicating a Phase Tracking Reference Signal-Demodulation Reference Signal (PTRS-DMRS) port association regarding uplink transmission and reception in a wireless communication system.

[0007] The technical objectives to be achieved by the present disclosure are not limited to the above-mentioned technical objectives, and those skilled in the art can clearly understand other technical objectives not described herein through the following description.

[0008] Technical Solution

[0009] A method performed by a user equipment (UE) in a wireless communication system according to an aspect of the present disclosure may include the following steps: receiving information for configuration of a sounding reference signal (SRS) resource set; receiving downlink control information (DCI), the DCI including a first phase tracking reference signal demodulation reference signal (PTRS-DMRS) port association field and a second PTRS-DMRS port association field; and transmitting a PTRS based on at least one of the first PTRS-DMRS port association field or the second PTRS-DMRS port association field. In this article, based on the configuration of three PTRS ports for the UE, the first PTRS-DMRS port association field may indicate information for one DMRS port associated with one PTRS port, and the second PTRS-DMRS port association field indicates information for two DMRS ports associated with two PTRS ports. The field sizes for the first PTRS-DMRS port association field and the second PTRS-DMRS port association field may be determined based on the number of specific SRS resources belonging to the SRS resource set.

[0010] A method performed by a base station in a wireless communication system according to an additional aspect of the present disclosure may include the following steps: transmitting information for configuration of a sounding reference signal (SRS) resource set; transmitting downlink control information (DCI), the DCI including a first phase tracking reference signal demodulation reference signal (PTRS-DMRS) port association field and a second PTRS-DMRS port association field; and receiving a PTRS based on at least one of the first PTRS-DMRS port association field or the second PTRS-DMRS port association field. In this article, based on three PTRS ports being configured for a UE, the first PTRS-DMRS port association field may indicate information for one DMRS port associated with one PTRS port, and the second PTRS-DMRS port association field indicates information for two DMRS ports associated with two PTRS ports. The field sizes for the first PTRS-DMRS port association field and the second PTRS-DMRS port association field may be determined based on the number of specific SRS resources belonging to the SRS resource set.

[0011] Beneficial Effects

[0012] According to one embodiment of the present disclosure, a method and apparatus for performing uplink transmission and reception in a wireless communication system may be provided.

[0013] According to one embodiment of the present disclosure, a method and apparatus for configuring / indicating a Phase Tracking Reference Signal-Demodulation Reference Signal (PTRS-DMRS) port association regarding uplink transmission and reception in a wireless communication system may be provided.

[0014] According to one embodiment of the present disclosure, even when the number of PTRS ports that can be configured to a UE increases for performance improvement, PTRS-DMRS port association can be efficiently indicated by utilizing a specific number of indication fields.

[0015] Effects achievable by the present disclosure are not limited to the above-described effects, and other effects not described herein may be clearly understood by those skilled in the art through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0018] Figure 2 The frame structure in a wireless communication system to which the present disclosure can be applied is illustrated.

[0019] Figure 3 A resource grid in a wireless communication system to which the present disclosure can be applied is illustrated.

[0020] Figure 4 The physical resource blocks in a wireless communication system to which the present disclosure can be applied are illustrated.

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

[0022] Figure 6 Physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the physical channels are illustrated.

[0023] Figure 7 A multiple transmission and reception point (TRP) transmission scheme in a wireless communication system to which the present disclosure can be applied is illustrated.

[0024] Figure 8 is a diagram illustrating an operation of a user equipment for performing a method of PTRS transmission and reception according to an embodiment of the present disclosure.

[0025] Fig. 9 is a diagram illustrating an operation of a base station for performing a method of PTRS transmission and reception according to an embodiment of the present disclosure.

[0026] Fig.10 is a diagram illustrating a block diagram of a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0027] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed by the accompanying drawings is intended to describe exemplary embodiments of the present disclosure, rather than to represent the only embodiment in which the present disclosure can be implemented. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the relevant art know that the present disclosure can be implemented without these specific details.

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

[0029] In the present disclosure, when an element is referred to as being "connected", "combined" or "linked" to another element, it may include an indirect connection relationship between another element and a direct connection relationship. In addition, in the present disclosure, the term "comprising" or "having" specifies the presence of the mentioned features, steps, operations, components and / or elements, but does not exclude the presence or addition of one or more other features, stages, operations, components, elements and / or groups thereof.

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

[0031] The terms used in this disclosure are intended to describe specific embodiments, rather than to limit the claims. As used in the description of the embodiments and the appended claims, the singular form is intended to include the plural form, unless the context clearly indicates otherwise. The term "and / or" used in this disclosure may refer to one of the related enumerated items, or mean that it refers to and includes any and all possible combinations of two or more of them. In addition, unless otherwise stated, the " / " between words in the present invention has the same meaning as "and / or".

[0032] The present disclosure describes a wireless communication network or a wireless communication system, and operations performed in the wireless communication network may be performed in a process in which a device (e.g., a base station) controlling a corresponding wireless communication network controls the network and transmits or receives a signal, or may be performed in a process in which a terminal associated with the corresponding wireless network transmits or receives a signal between the network or the terminal.

[0033] In the present disclosure, sending or receiving a channel includes the meaning of sending or receiving information or signals through the corresponding channel. For example, sending a control channel means sending control information or control signals through the control channel. Similarly, sending a data channel means sending data information or data signals through the data channel.

[0034] In the following, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, the transmitter may be part of a base station, and the receiver may be part of a terminal. In the uplink, the transmitter may be part of a terminal, and the receiver may be part of a base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. The base station (BS) may be replaced by terms such as a fixed station, a node B, an eNB (evolved node B), a gNB (next generation node B), a BTS (base station transceiver system), an access point (AP), a network (5G network), an AI (artificial intelligence) system / module, an RSU (roadside unit), a robot, a drone (UAV: unmanned aerial vehicle), an AR (augmented reality) device, a VR (virtual reality) device, and the like. In addition, the terminal 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) device, M2M (machine to machine) device, D2D (device to device) device, vehicle, RSU (roadside unit), robot, AI (artificial intelligence) module, drone (UAV: unmanned aerial vehicle), AR (augmented reality) device, VR (virtual reality) device, etc.

[0035] The following description can be used for various radio access systems, such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented by UTRA (Universal Terrestrial Radio Access) or CDMA 2000. TDMA can be implemented by radio technologies such as GSM (Global System for Mobile Communications) / GPRS (General Packet Radio Service) / EDGE (Data Rate Enhanced GSM Evolution). OFDMA can be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802-20, E-UTRA (Evolved UTRA), etc. 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-Apro is an advanced version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE / LTE-A / LTE-Apro.

[0036] In order to make the description clearer, the description is based on the 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​the present disclosure is not limited to this. LTE means the technology after 3GPP TS (Technical Specification) 36.xxx version 8. Specifically, the LTE technology in or after 3GPP TS 36.xxx version is called LTE-A, and the LTE technology in or after 3GPP TS 36.xxx version 13 is called LTE-Apro. 3GPP NR means the technology in or after TS 38.xxx version. LTE / NR can be referred to as a 3GPP system. "xxx" means the detailed number of the standard document. LTE / NR can generally be referred to as a 3GPP system. For the background technology, terms, abbreviations, etc. used to describe the present disclosure, reference can be made to the matters described in the standard documents disclosed before the present disclosure. For example, reference can be made to the following documents.

[0037] For 3GPP LTE, reference may be made to TS 36.211 (Physical Channels and Modulation), TS 36.212 (Multiplexing and Channel Coding), TS 36.213 (Physical Layer Procedures), TS 36.300 (Overall Description), and TS 36.331 (Radio Resource Control).

[0038] For 3GPP NR, you can refer to TS 38.211 (Physical channels and modulation), TS 38.212 (Multiplexing and channel coding), TS 38.213 (Physical layer procedures for control), TS 38.214 (Physical layer procedures for data), TS 38.300 (NR and NG-RAN (Next Generation Radio Access Network) overall description), and TS 38.331 (Radio Resource Control Protocol Specification).

[0039] Abbreviations of terms that may be used in the present disclosure are defined as follows.

[0040] -BM: Beam Management

[0041] -CQI: Channel Quality Indicator

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

[0043] -CSI: Channel State Information

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

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

[0046] -DMRS: Demodulation Reference Signal

[0047] -FDM: Frequency Division Multiplexing

[0048] -FFT: Fast Fourier Transform

[0049] -IFDMA: Interleaved Frequency Division Multiple Access

[0050] -IFFT: Inverse Fast Fourier Transform

[0051] -L1-RSRP: Layer 1 reference signal received power

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

[0053] -MAC: Media Access Control

[0054] -NZP: Non-Zero Power

[0055] -OFDM: Orthogonal Frequency Division Multiplexing

[0056] –PDCCH: Physical Downlink Control Channel

[0057] -PDSCH: Physical Downlink Shared Channel

[0058] -PMI: Precoding matrix indicator

[0059] -RE: Resource Element

[0060] -RI: Rank indicator

[0061] -RRC: Radio Resource Control

[0062] -RSSI: Received Signal Strength Indicator

[0063] -Rx: Receive

[0064] -QCL: Quasi-Co-located

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

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

[0067] -TDM: Time Division Multiplexing

[0068] -TRP: Transmit and Receive Point

[0069] -TRS: Tracking Reference Signal

[0070] -Tx: Send

[0071] -UE: User Equipment

[0072] -ZP: Zero Power

[0073] Overall system

[0074] As more communication devices require higher capacity, there has been a demand for improved mobile broadband communications compared to existing radio access technologies (RATs). In addition, large-scale MTC (machine type communication) that provides various services anytime and anywhere by connecting multiple devices and things is also one of the main issues to be considered in the next generation of communications. In addition, the design of communication systems considering services / terminals that are sensitive to reliability and latency is also 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 technology is referred to as NR in this disclosure. NR is an expression representing an example of 5G RAT.

[0075] The new RAT system including NR uses an OFDM transmission method or a transmission method similar thereto. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system follows the parameters of the existing LTE / LTE-A as is, but may support a wider system bandwidth (e.g., 100 MHz). Alternatively, a cell may support multiple parameter sets. In other words, terminals operating according to different parameter sets may coexist in one cell.

[0076] A parameter set corresponds to one subcarrier spacing in the frequency domain. As the reference subcarrier spacing is scaled by an integer N, different parameter sets can be defined.

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

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

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

[0080] The NR system may support multiple parameter sets. Here, the parameter set may be defined by subcarrier spacing and cyclic prefix (CP) overhead. Here, multiple subcarrier spacings may be derived by scaling the basic (reference) subcarrier spacing by an integer N (or, μ). In addition, although it is assumed that very low subcarrier spacings are not used in very high carrier frequencies, the parameter set used may be selected independently of the frequency band. In addition, various frame structures according to multiple parameter sets may be supported in the NR system.

[0081] In the following, OFDM parameter sets and frame structures that can be considered in the NR system are described. Multiple OFDM parameter sets supported in the NR system can be defined as shown in Table 1 below.

[0082] [Table 1]

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

[0084] NR supports multiple parameter sets (or subcarrier spacing (SCS)) for supporting various 5G services. For example, when the SCS is 15kHz, the wide area of ​​the traditional cellular band is supported; and when the SCS is 30kHz / 60kHz, dense cities, lower latency and wider carrier bandwidth are supported; and when the SCS is 60kHz or higher, bandwidths exceeding 24.25GHz are supported to overcome phase noise. The NR band is defined as two types of frequency ranges (FR1, FR2). FR1 and FR2 can be configured as shown in Table 2 below. In addition, FR2 can mean millimeter wave (mmW).

[0085] [Table 2]

[0086]

[0087] Regarding the frame structure in the NR system, the sizes of various fields in the time domain are expressed as T c =1 / (Δf max ·N f ) is a multiple of the time unit. Here, Δf max 480·10 3 Hz, and N f is 4096. Downlink and uplink transmissions are configured (organized) to have duration T f =1 / Δf max N f / 100)T c =10ms radio frame. Here, the radio frame is configured with 10 subframes, each of which has T sf =(Δf max N f / 1000)·T c =1 ms duration. In this case, there may be one frame set for the uplink and one frame set for the downlink. Furthermore, the transmission in the i-th uplink frame from the terminal should start T earlier than the corresponding downlink frame in the corresponding terminal. TA =(N TA +N TA,offset )T c For subcarrier spacing configuration μ, the time slots are arranged in n subframes. s μ ∈{0,...,N slot subframe,μ -1} and in the radio frame the number is incremented by n s,f μ ∈{0,...,N slot frame,μ -1}. A time slot is configured with N symb slotconsecutive OFDM symbols, and N symb slot Determined according to CP. Time slot n in a subframe s μ The beginning of the OFDM symbol n in the same subframe s μ N symb slot All terminals may not perform transmission and reception at the same time, which means that all OFDM symbols of a downlink time slot or an uplink time slot may not be used. Table 3 shows the number of OFDM symbols per time slot in a normal CP (N symb slot ), the number of time slots per radio frame (N slot frame,μ ) and the number of time slots per subframe (N slot subframe,μ ), and Table 4 represents 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.

[0088] [Table 3]

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

[0090] [Table 4]

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

[0092] Figure 2 is an example of μ=2 (SCS is 60kHz), see Table 3, 1 subframe can include 4 time slots. Figure 2 1 subframe = {1, 2, 4} shown in is an example, and the number of time slots that can be included in 1 subframe is defined as in Table 3 or Table 4. In addition, a mini time slot may include 2, 4, or 7 symbols or more or less symbols. Regarding physical resources in the NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. may be considered. Hereinafter, the physical resources that may be considered in the NR system will be described in detail.

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

[0094] Figure 3A resource grid in a wireless communication system to which the present disclosure can be applied is illustrated.

[0095] Reference Figure 3 , which graphically depicts a resource grid configuration with N in the frequency domain RB μ N sc RB subcarriers, and one subframe is configured with 14·2 μ OFDM symbols, but not limited to this. In the NR system, the transmitted signal consists of 2 μ N symb (μ) OFDM symbols and N RB μ N sc RB Here, N RB μ ≤N RB max,μ . N RB max,μ represents the maximum transmission bandwidth, which may differ between uplink and downlink and between parameter sets. In this case, one resource grid can be configured for each μ and antenna port p. Each element of the resource grid 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 refers to the symbol position in the subframe. When referencing a resource element in a slot, an index pair (k, l) is used. Here, l = 0, ..., N symb μ -1. The resource element (k, l') for μ and antenna port p corresponds to the complex value a k,l' (p,μ) When there is no risk of aliasing or when no specific antenna port or parameter set is specified, the indices p and μ may be dropped and the complex value may be ak,l'(p) or ak,l'. In addition, a resource block (RB) is defined as N in the frequency domain. sc RB =12 consecutive subcarriers.

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

[0097] -OffsetToPointA for the primary cell (PCell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping with the SS / PBCH block, which is used by the terminal for initial cell selection. Assuming a subcarrier spacing of 15kHz is used for FR1 and a subcarrier spacing of 60kHz is used for FR2, it is expressed in resource blocks.

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

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

[0100] [Formula 1]

[0101]

[0102] In Equation 1, k is defined relative to point A, so that k=0 corresponds to a subcarrier centered at point A. Physical resource blocks are spaced from 0 to N in a bandwidth part (BWP). BWP,i size,μ -1 numbering and i is the number of BWP. Physical resource block n in BWPi PRB and public resource block n CRB The relationship between is given by the following formula 2.

[0103] [Formula 2]

[0104]

[0105] N BWP,i start,μ is the common resource block where the BWP starts relative to common resource block 0.

[0106] Figure 4 The physical resource blocks in the wireless communication system to which the present disclosure can be applied are illustrated. Figure 5 The time slot structure in a wireless communication system to which the present disclosure can be applied is illustrated.

[0107] Reference Figure 4 and Figure 5 , a time slot includes multiple symbols in the time domain. For example, for a normal CP, 1 time slot includes 7 symbols, but for an extended CP, 1 time slot includes 6 symbols

[0108] A carrier includes 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 part) is defined as multiple consecutive (physical) resource blocks in the frequency domain and may correspond to a parameter set (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication may be performed through an activated BWP, and only one BWP may be activated for a terminal. In a resource grid, each element is called a resource element (RE) and may map a complex symbol.

[0109] In the NR system, each component carrier (CC) can support up to 400MHz. If a terminal operating in such a wideband CC always operates to turn on the radio frequency (FR) chip for the entire CC, the terminal battery consumption may increase. Alternatively, when considering multiple application scenarios operating in a wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different parameter sets (e.g., subcarrier spacing, etc.) can be supported in each frequency band in the corresponding CC. Alternatively, each terminal may have different capabilities for the maximum bandwidth. Taking this into account, the base station can instruct the terminal to operate only in part of the bandwidth instead of the full bandwidth of the wideband CC, and for convenience, the corresponding partial bandwidth is defined as a bandwidth part (BWP). The BWP can be configured with continuous RBs on the frequency axis and can correspond to a parameter set (e.g., subcarrier spacing, CP length, slot / mini slot duration).

[0110] In addition, even in one CC configured to the 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 time slot, and the PDSCH indicated by the PDCCH can be scheduled in a larger BWP. Alternatively, when the UE is congested in a specific BWP, other BWPs can be configured for some terminals for load balancing. Alternatively, considering the frequency domain inter-cell interference elimination between adjacent cells, some full-bandwidth intermediate spectrums can be excluded, and BWPs on two edges can be configured in the same time slot. In other words, the base station can configure at least one DL / UL BWP to a terminal associated with a broadband CC. The base station can activate at least one DL / UL BWP in the configured DL / UL BWP at a specific time (via L1 signaling or MAC CE (control element) or RRC signaling, etc.). In addition, the base station can indicate switching to other configured DL / UL BWPs (via L1 signaling or MAC CE or RRC signaling, etc.). Alternatively, based on a timer, when the timer value expires, it can switch to a determined DL / UL BWP. Here, the activated DL / UL BWP is defined as the active DL / UL BWP. However, when the terminal performs the initial access procedure or sets up the RRC connection, the configuration on the DL / UL BWP may not be received, so the DL / UL BWP assumed by the terminal in these cases is defined as the initial active DL / UL BWP.

[0111] Figure 6 Physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the physical channels are illustrated.

[0112] In a wireless communication system, a terminal receives information from a base station through a downlink and transmits information to the base station through an uplink. The information sent and received by the base station and the terminal includes data and various control information, and there are various physical channels according to the type / purpose of the information they send and receive.

[0113] When the terminal is turned on or newly enters a cell, it performs an initial cell search including synchronization with a base station (S601). For the initial cell search, the terminal can synchronize with the base station by receiving a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station, and obtain information such as a cell identifier (ID). Then, the terminal can obtain broadcast information in the cell by receiving a physical broadcast channel (PBCH) from the base station. In addition, the terminal can check the downlink channel status by receiving a downlink reference signal (DLRS) in the initial cell search phase.

[0114] The terminal that has completed the initial cell search may obtain more detailed system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S602).

[0115] In addition, when the terminal accesses the base station for the first time or there are no radio resources for signal transmission, it can perform a random access (RACH) process (S603 to S606) on the base station. For the random access process, the terminal can send a specific sequence as a preamble code through a physical random access channel (PRACH) (S603 and S605), and can receive a response message to the preamble code through a PDCCH and a corresponding PDSCH (S604 and S606). The contention-based RACH can additionally perform a contention resolution process.

[0116] The terminal that subsequently performs the above process may perform 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 the format varies according to its purpose of use.

[0117] In addition, the control information sent by the terminal to the base station through the uplink or received by the terminal from the base station includes downlink / uplink ACK / NACK (acknowledgement / non-acknowledgement) signal, CQI (channel instruction indicator), PMI (precoding matrix indicator), RI (rank indicator), etc. For the 3GPP LTE system, the terminal can send the above-mentioned CQI / PMI / RI and other control information through PUSCH and / or PUCCH.

[0118] Table 5 shows an example of the DCI format in the NR system.

[0119] [Table 5]

[0120]

[0121] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information (e.g., UL / SUL (supplementary 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., process number, DAI (downlink assignment index), PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), power control information related to the scheduling of PUSCH (e.g., PUSCH power control, etc.), and control information included in each DCI format may be predefined. DCI format 0_0 is used to schedule PUSCH in one cell. Information included in DCI format 0_0 is CRC (Cyclic Redundancy Check) scrambled by C-RNTI (Cell Radio Network Temporary Identifier) ​​or CS-RNTI (Configured Scheduling RNTI) or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and transmitted.

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

[0123] DCI format 0_2 is used to schedule PUSCH in one cell. Information included in DCI format 0_2 is scrambled and transmitted by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0124] 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 (TBs) (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 ports, TCI (transmission configuration indicator), SRS (sounding reference signal) request, etc.), information related to PUCCH scheduling regarding PDSCH (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each DCI format may be predefined.

[0125] DCI format 1_0 is used to schedule a PDSCH in one DL cell. Information included in DCI format 1_0 is a CRC scrambled and transmitted by a C-RNTI or a CS-RNTI or an MCS-C-RNTI.

[0126] DCI format 1_1 is used to schedule PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled and transmitted by C-RNTI or CS-RNTI or MCS-C-RNTI.

[0127] DCI format 1_2 is used to schedule PDSCH in one cell. Information included in DCI format 1_2 is CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0128] Quasi-Co-location (QCL)

[0129] The antenna port is defined so that the channel that transmits the symbol in the antenna port can be inferred from the channel that transmits other symbols in the same antenna port. When the characteristics of the channel carrying the symbol in one antenna port can be inferred from the channel carrying the symbol in another antenna port, the two antenna ports are said to be in a QC / QCL (quasi co-location or quasi co-location) relationship.

[0130] Here, the channel characteristics include at least one of delay spread, Doppler spread, frequency / Doppler shift, average received power, receive timing / average delay, or spatial RX parameters. Here, the spatial Rx parameters mean spatial (Rx) channel characteristic parameters such as angle of arrival.

[0131] The terminal may be configured at a list of up to M TCI state configurations in the higher layer parameter PDSCH-Config to decode the PDSCH from the detected PDCCH with the desired DCI for the corresponding terminal and a given serving cell. M depends on the UE capabilities.

[0132] Each TCI state includes parameters for configuring a quasi co-location relationship between one or two ports of a DL reference signal and a DM-RS (Demodulation Reference Signal) of a PDSCH.

[0133] The quasi co-location relationship is configured by the higher layer parameter qcl-Type1 for the first DL RS and qcl-Type2 (if configured) for the second DL RS. For two DL RSs, the QCL type is different whether the reference is the same DL RS or different DL RSs.

[0134] The QCL type corresponding to each DL RS is given by a high-level parameter qcl-Type of QCL-Info and can take one of the following values.

[0135] - "QCL-TypeA": {Doppler shift, Doppler spread, average delay, delay spread}

[0136] - "QCL-TypeB": {Doppler shift, Doppler spread}

[0137] - "QCL-TypeC": {Doppler shift, average delay}

[0138] - "QCL-TypeD": {spatial Rx parameters}

[0139] For example, when the target antenna port is a specific NZP CSI-RS, it can indicate / configure the corresponding NZP CSI-RS antenna port to be quasi-co-located with a specific TRS with respect to QCL-Type A, and quasi-co-located with a specific SSB with respect to QCL-Type D. The terminal that receives such an indication / configuration can receive the corresponding NZP CSI-RS by using the Doppler and delay values ​​measured in the QCL-TypeA TRS, and apply the Rx beam used to receive the QCL-TypeD SSB to the reception of the corresponding NZP CSI-RS.

[0140] The UE may receive the activation command via MACCE signaling for mapping up to 8 TCI states to code points of the DCI field "Transmission Configuration Indication".

[0141] When a HARQ-ACK corresponding to a PDSCH carrying an activation command is sent in slot n, the HARQ-ACK can be transmitted by sending the HARQ-ACK signal from slot n+3N to the PDSCH carrying the activation command. slot subframe,μ +1 to apply the mapping indicated between the TCI state and the code point of the DCI field "Transmission Configuration Indication". After receiving the initial higher layer configuration for the TCI state before the UE receives the activation command, the UE can assume for QCL-TypeA and, if applicable, for QCL-TypeD that the DMRS ports of the PDSCH of the serving cell are quasi-co-located with the SS / PBCH blocks determined during the initial access procedure.

[0142] When a higher layer parameter (e.g., tci-PresentInDCI) indicating whether a TCI field is present in the DCI configured for the UE is set to be enabled for the CORESET that schedules the PDSCH, the UE may assume that the TCI field is present in the DCI format 1_1 of the PDCCH sent in the corresponding CORESET. When tci-PresentInDCI is not configured for the CORESET that schedules the PDSCH, or when the PDSCH is scheduled by DCI format 1_0 and the time offset between the reception of the corresponding PDSCH and the DL DCI is equal to or greater than a predetermined threshold (e.g., timeDurationForQCL), in order to determine the PDSCH antenna port QCL, the UE may assume that the TCI state or QCL assumption for the PDSCH is the same as the TCI state or QCL assumption applied to the CORESET for PDCCH transmission. Here, the predetermined threshold may be based on the reported UE capabilities.

[0143] When the parameter tci-PresentInDCI is set to enabled, the TCI field in the DCI in the scheduled CC (component carrier) can indicate the activated TCI state of the scheduled CC or DL ​​BWP. When PDSCH is scheduled by DCI format 1_1, the UE can use the TCI state to determine the PDSCH antenna port QCL based on the value of the "Transmission Configuration Indication" field of the detected PDCCH with DCI.

[0144] When the time offset between the reception of the corresponding PDSCH and DL DCI is equal to or greater than a predetermined threshold (e.g., timeDurationForQCL), the UE may assume that the DMRS port of the PDSCH of the serving cell is quasi-co-located with the RS in the TCI state of the QCL type parameter given by the indicated TCI state.

[0145] When a single slot PDSCH is configured for the UE, the indicated TCI state may be based on the activated TCI state of the slot with the scheduled PDSCH.

[0146] When multi-slot PDSCH is configured for a UE, the indicated TCI state may be based on the activated TCI state of the first slot with scheduled PDSCH, and the UE may expect the activated TCI state across slots with scheduled PDSCH to be the same.

[0147] When a CORESET associated with a search space set for cross-carrier scheduling is configured for the UE, the UE may expect the tci-PresentInDCI parameter to be set to be enabled for the corresponding CORESET. When one or more TCI states are configured for a serving cell scheduled by a search space set including QCL-TypeD, the UE may expect the time offset between the reception of the corresponding PDSCH and the PDCCH detected in the search space set to be equal to or greater than a predetermined threshold (e.g., timeDurationForQCL).

[0148] For the case where the parameter tci-PresentInDCI is set to enabled and tci-PresentInDCI is not configured in RRC connected mode, when the time offset between the reception of the corresponding PDSCH and DL DCI is less than a predetermined threshold (e.g., timeDurationForQCL), the UE may assume that the DMRS port of the PDSCH of the serving cell is quasi-co-located with the RS of the QCL parameter indicated by the PDCCH QCL of the CORESET associated with the monitored search space, where the monitored search space has the lowest CORESET ID in the latest time slot of one or more CORESETs in the activated BWP of the UE monitoring the serving cell.

[0149] In this case, when the QCL-TypeD of the PDSCH DMRS is different from the QCL-TypeD of the PDCCH DMRS and they overlap in at least one symbol, the UE can expect to prioritize the reception of the PDCCH associated with the corresponding CORESET. It can also be applied to intra-band CA (carrier aggregation) (when the PDSCH and CORESET exist in different CCs). When any configured TCI state does not include QCL-TypeD, different QCL assumptions can be obtained from the TCI state indicated for the scheduled PDSCH regardless of the time offset between the reception of the corresponding PDSCH and DL DCI.

[0150] For the periodic CSI-RS resources of the configured NZP-CSI-RS-ResourceSet including the higher layer parameter trs-Info, the UE may expect the TCI state to indicate one of the following QCL types.

[0151] - QCL-Type C with SS / PBCH blocks and, if applicable, QCL-Type D with the same SS / PBCH blocks, or

[0152] - QCL-TypeC with SS / PBCH blocks and, if applicable, QCL-TypeD with CSI-RS resources in NZP-CSI-RS-ResourceSet with configuration including repetition of higher layer parameters

[0153] For non-periodic CSI-RS resources of the configured NZP-CSI-RS-ResourceSet including the higher-level parameter trs-Info, the UE may expect the TCI state to indicate QCL-TypeA for the periodic CSI-RS resources of the NZP-CSI-RS-ResourceSet including the higher-level parameter trs-Info, and if applicable, QCL-TypeD for the same periodic CSI-RS resources.

[0154] *For CSI-RS resources of NZP-CSI-RS-ResourceSet configured without higher layer parameter trs-Info and without higher layer parameter repetition, the UE may expect the TCI state to indicate one of the following QCL types.

[0155] - QCL-TypeA for CSI-RS resources with a configured NZP-CSI-RS-ResourceSet including the higher layer parameter trs-Info, and, if applicable, QCL-TypeD for the same CSI-RS resources, or

[0156] - QCL-TypeA for CSI-RS resources with a configured NZP-CSI-RS-ResourceSet including the higher layer parameter trs-Info, and if applicable, QCL-TypeD for SS / PBCH blocks, or

[0157] - QCL-TypeA for CSI-RS resources in NZP-CSI-RS-ResourceSet with a configuration including the higher layer parameter trs-Info, and, if applicable, QCL-TypeD for CSI-RS resources in NZP-CSI-RS-ResourceSet with a configuration including the higher layer parameter repetition, or

[0158] When QCL-TypeD is not applicable, QCL-TypeB of CSI-RS resources of NZP-CSI-RS-ResourceSet with configuration including higher layer parameter trs-Info.

[0159] For CSI-RS resources of a configured NZP-CSI-RS-ResourceSet including repetition of higher layer parameters, the UE may expect the TCI state to indicate one of the following QCL types.

[0160] - QCL-TypeA for CSI-RS resources with a configured NZP-CSI-RS-ResourceSet including the higher layer parameter trs-Info, and if applicable, QCL-TypeD for the same CSI-RS resources, or

[0161] - QCL-TypeA for CSI-RS resources in NZP-CSI-RS-ResourceSet with a configuration including the higher layer parameter trs-Info, and, if applicable, QCL-TypeD for CSI-RS resources in NZP-CSI-RS-ResourceSet with a configuration including the higher layer parameter repetition, or

[0162] - QCL-Type C with SS / PBCH blocks and, if applicable, QCL-Type D with the same SS / PBCH blocks.

[0163] For DMRS of PDCCH, the UE may expect the TCI state to indicate one of the following QCL types.

[0164] - QCL-TypeA for CSI-RS resources with a configured NZP-CSI-RS-ResourceSet including the higher layer parameter trs-Info, and if applicable, QCL-TypeD for the same CSI-RS resources, or

[0165] - QCL-TypeA for CSI-RS resources in NZP-CSI-RS-ResourceSet with a configuration including the higher layer parameter trs-Info, and, if applicable, QCL-TypeD for CSI-RS resources in NZP-CSI-RS-ResourceSet with a configuration including the higher layer parameter repetition, or

[0166] - QCL-TypeA with CSI-RS resources of NZP-CSI-RS-ResourceSet configured without higher layer parameter trs-Info and without higher layer parameter repetition, and if applicable, QCL-TypeD with the same CSI-RS resources.

[0167] For DMRS of PDSCH, the UE may expect the TCI state to indicate one of the following QCL types.

[0168] - QCL-TypeA for CSI-RS resources with a configured NZP-CSI-RS-ResourceSet including the higher layer parameter trs-Info, and if applicable, QCL-TypeD for the same CSI-RS resources, or

[0169] - QCL-TypeA for CSI-RS resources in NZP-CSI-RS-ResourceSet with a configuration including the higher layer parameter trs-Info, and, if applicable, QCL-TypeD for CSI-RS resources in NZP-CSI-RS-ResourceSet with a configuration including the higher layer parameter repetition, or

[0170] - QCL-TypeA with CSI-RS resources of NZP-CSI-RS-ResourceSet configured without higher layer parameter trs-Info and without higher layer parameter repetition, and if applicable, QCL-TypeD with the same CSI-RS resources.

[0171] Multi-TRP (M-TRP) related operations

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

[0173] Reference Figure 7 (a) shows a case where layer groups transmitting the same codeword (CW) / transport block (TB) correspond to different TRPs. Here, the layer group may mean a predetermined set of layers including one or more layers. In this case, the advantage is that the amount of transmission resources increases due to the number of multiple layers, so robust channel coding with a low coding rate can be used for the TB, and in addition, since multiple TRPs have different channels, it can be expected to improve the reliability of the received signal based on diversity gain.

[0174] Reference Figure 7 (b) shows an example of sending 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 identical to each other. In other words, CW#1 and CW#2 mean that the same TB is transformed into different CWs by different TRPs through channel coding, etc. Therefore, an example of repeatedly sending the same TB can be considered. Figure 7 In the case of (b), Figure 7 Compared with (a), it may have the disadvantage of a higher code rate corresponding to the TB. However, it has the advantage that the code rate can be adjusted by indicating different RV (redundancy version) values ​​or the modulation order of each CW can be adjusted for the coded bits generated from the same TB according to the channel environment.

[0175] According to the above Figure 7 (a) and Figure 7 The method shown in (b) can improve the data reception probability of the terminal because the same TB is repeatedly sent through different layer groups and each layer group is sent by a different TRP / panel. It is called the M-TRP URLLC transmission method based on SDM (spatial division multiplexing). Layers belonging to different layer groups are sent through DMRS ports belonging to different DMRS CDM groups respectively.

[0176] In addition, the above content related to multiple TRPs is described based on the SDM (spatial division multiplexing) method using different layers, but it can be extended and applied to a frequency division multiplexing (FDM) method based on different frequency domain resources (e.g., RB / PRB (sets), etc.) and / or a time division multiplexing (TDM) method based on different time domain resources (e.g., time slots, symbols, sub-symbols, etc.).

[0177] Regarding methods for URLLC based on multiple TRPs scheduled by a single DCI, the following methods are discussed.

[0178] 1) Method 1 (SDM): Time and frequency resource allocation overlap and n (n<=Ns) TCI states in a single time slot

[0179] 1-a) Method 1a

[0180] - The same TB is transmitted in one layer or one layer set at each transmission time (opportunity), and each layer or each layer set is associated with one TCI and one DMRS port set.

[0181] - Use a single codeword with one RV in all spatial layers or all layer sets. With respect to the UE, different coded bits are mapped to different layers or layer sets by using the same mapping rule.

[0182] 1-b) Method 1b

[0183] - The same TB is transmitted in one layer or one layer set at each transmission time (opportunity), and each layer or each layer set is associated with one TCI and one DMRS port set.

[0184] - Use a single codeword with one RV in each spatial layer or each layer set. The RV corresponding to each spatial layer or each layer set can be the same or different.

[0185] 1-c) Method 1c

[0186] - At one transmission time (opportunity), the same TB having one DMRS port associated with multiple TCI state indexes is transmitted in one layer, or the same TB having multiple DMRS ports associated one-to-one with multiple TCI state indexes is transmitted in one layer.

[0187] In the case of the above-mentioned methods 1a and 1c, the same MCS is applied to all layers or all layer sets.

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

[0189] - Each non-overlapping frequency resource allocation is associated with one TCI state.

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

[0191] 2-a) Method 2a

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

[0193] 2-b) Method 2b

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

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

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

[0197] - Each transmission time (opportunity) of a TB has a time granularity of a mini-slot and has one TCI and one RV.

[0198] - A common MCS for all transmission times (opportunities) in a time slot is used with single or multiple DMRS ports.

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

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

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

[0202] - All transmission times (opportunities) across K time slots use a common MCS and single or multiple DMRS ports.

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

[0204] Downlink Multi-TRP (M-TRP) URLLC Transmission Operation

[0205] DL MTRP URLLC transmission method means that multiple TRPs send the same data / DCI by using different space (e.g., layer, port) / time / frequency resources. For example, TRP 1 sends specific data / DCI in resource 1, and TRP 2 sends specific data / DCI in resource 2 (i.e., the same data / DCI).

[0206] A UE configured with the DL MTRP-URLLC transmission method receives the same data / DCI by using different layer / time / frequency resources. Here, the UE can receive an indication of the QCL RS / type (i.e., DL TCI state) used to receive the corresponding data / DCI from the base station in the space / time / frequency resources.

[0207] For example, when receiving data / DCI in resource 1 and resource 2, the DL TCI state used in resource 1 and the DL TCI state used in resource 2 may be indicated. The UE may achieve high reliability because it receives data / DCI through resource 1 and resource 2. Such DL MTRP URLLC may be applied to PDSCH / PDCCH.

[0208] The UL MTRP-URLLC transmission method means that multiple TRPs receive the same data / UCI from any UE by using different space / time / frequency resources. For example, TRP 1 can receive the same data / DCI from the UE in resource 1, and TRP 2 can receive the same data / DCI from the UE in resource 2. And, TRP 1 and TRP 2 can share the data / UCI received from the UE through the backhaul link (connected between TRPs).

[0209] That is, a UE configured with the UL MTRP-URLLC transmission method can send the same data / UCI by using different space / time / frequency resources. Here, the UE can be instructed by the base station to use the Tx beam and Tx power (i.e., UL TCI state) to send the same data / UCI in the space / time / frequency resources. For example, when the same data / UCI is sent in resource 1 and resource 2, the UE can be instructed by the base station to use the UL TCI state used in resource 1 and the UL TCI state used in resource 2. This UL M-TRP URLLC can be applied to PUSCH / PUCCH.

[0210] In addition, when describing the present disclosure, when data / DCI / UCI is received / sent through specific space / time / frequency resources, using (or mapping) a specific TCI state (or TCI) may mean, for DL, using the QCL type and QCL RS indicated by the specific TCI state in the specific space / time / frequency resources to estimate the channel from the DMRS, and receiving / demodulating the data / DCI / UCI using the estimated channel.

[0211] In addition, when data / DCI / UCI is received / sent through specific space / time / frequency resources, using (or mapping) a specific TCI state (or TCI) may mean that, for UL, DMRS and data / UCI are transmitted / modulated using the Tx beam and / or Tx power indicated by the specific TCI state in the specific space / time / frequency resources.

[0212] And, the UL TCI state may include the Tx beam or Tx power information of the UE. In addition, the base station may configure the spatial relationship information, etc. for the UE through other parameters instead of the TCI state.

[0213] For example, the UL TCI state may be directly indicated to the UE through the UL grant DCI. Alternatively, the UL TCI state may mean the spatial relationship information of the SRS resource indicated by the SRS resource indicator (SRI) field of the UL grant DCI. Alternatively, the UL TCI state may mean the open-loop (OP) Tx power control parameter connected to the value indicated by the SRI field of the UL grant DCI.

[0214] Here, the OL Tx power control parameters may include, for example, j (α and index for OP parameters), Po (maximum 32 parameter values ​​set per cell), q_d (index of DL RS resources for PL (path loss) measurement (up to 4 measurements per cell)), or / and I (closed-loop power control process index (up to 2 processes per cell)).

[0215] As another embodiment of the present disclosure, the M-TRP eMBB transmission method refers to a method in which M-TRP uses different space / time / frequency resources to send different data / DCI. If the M-TRP eMBB transmission method is configured, it can be assumed that the UE receives multiple TCI states from the base station via DCI, and the data received using the QCL RS indicated by each of the multiple TCI states are different from each other.

[0216] In addition, since the RNTI for M-TRP URLLC and the M-TRP eMBB RNTI are used separately, the UE can determine whether a specific transmission / reception is M-TRP URLLC transmission / reception or M-TRP eMBB transmission / reception. For example, when the RNTI for URLLC is used and CRC masking is performed for DCI, the UE can determine the corresponding transmission as URLLC transmission. In addition, when the RNTI for eMBB is used and CRC masking is performed for DCI, the UE can determine the corresponding transmission as eMBB transmission. As another example, the base station can configure the M-TRP URLLC transmission / reception method or the M-TRP eMBB transmission / reception method to the UE through new signaling.

[0217] For the convenience of describing the present disclosure, it has been assumed that two TRPs cooperate with each other to perform transmission / reception operations, but the present disclosure is not limited to this. That is, the present disclosure can be extended and applied even in a multi-TRP environment of 3 or more, and can be extended and applied even in an environment where transmission / reception is performed in different panels or beams in the same TRP. The UE can identify different TRPs as different TCI states. The UE sending / receiving data / DCI / UCI using TCI state 1 means that it sends / receives data / DCI / UCI / from TRP 1 (or to TRP 1).

[0218] The present disclosure can be used when M-TRP transmits PDCCH in a collaborative manner (repeated transmission or division of the same PDCCH). In addition, the present disclosure can be used when M-TRP transmits PDSCH in a collaborative manner or receives PUSCH / PUCCH in a collaborative manner.

[0219] In addition, when describing the present disclosure, repeatedly sending the same PDCCH by multiple base stations (M-TRP) may mean sending the same DCI through multiple PDCCH candidates, and has the same meaning as repeatedly sending the same DCI by multiple base stations. Here, two DCIs with the same DCI format / size / payload may be regarded as the same DCI.

[0220] Alternatively, if the scheduling results are the same even if the payloads of the two DCIs are different, the two DCIs can be regarded as the same DCI. For example, the time domain resource allocation (TDRA) field of the DCI can relatively determine the time slot / symbol position of the data and the time slot / symbol position of A(ACK) / N(NACK) based on the reception time of the DCI.

[0221] In this case, when the DCI received at time n and the DCI received at time n+1 indicate the same scheduling result to the UE, the TDRA fields of the two DCIs are different, so the DCI payloads are different from each other. Therefore, even if the payloads of the two DCIs are different, if the scheduling results are the same, the two DCIs can be regarded as the same DCI. Here, the number of repetitions R can be directly indicated to the UE by the base station or mutually agreed.

[0222] Alternatively, even if the payloads of two DCIs are different and the scheduling results are not the same, the two DCIs may be regarded as the same DCI when the scheduling result of one DCI is a subset of the scheduling result of the other DCI.

[0223] For example, if the same data is TDMed and repeatedly transmitted N times, DCI 1 received before the first data indicates (or schedules) the repetition of the data N times, and DCI 2 received before the second data indicates the repetition (scheduling) of the data N-1 times. In this case, the scheduling result (or data) of DCI 2 becomes a subset of the scheduling result (or data) of DCI 1, and the two DCIs have scheduling results for the same data. Therefore, even in this case, the two DCIs can be regarded as the same DCI.

[0224] And, in describing the present disclosure, dividing and sending the same PDCCH by multiple base stations may mean sending one DCI through one PDCCH candidate, but TRP 1 sends some resources defined for the corresponding PDCCH candidate and TRP 2 sends the remaining resources.

[0225] For example, when TRP 1 and TRP 2 divide and transmit PDCCH candidates corresponding to aggregation level m1+m2, the PDCCH candidates may be divided into PDCCH candidate 1 corresponding to aggregation level m1 and PDCCH candidate 2 corresponding to aggregation level m2, TRP 1 may transmit PDCCH candidate 1, and TRP 2 may transmit PDCCH candidate 2. In this case, TRP 1 and TRP 2 may use different time / frequency resources to transmit PDCCH candidate 1 and PDCCH candidate 2. After receiving PDCCH candidate 1 and PDCCH candidate 2, the UE may generate a PDCCH candidate corresponding to aggregation level m1+m2 and attempt DCI decoding.

[0226] In this case, the method of dividing the same DCI into multiple PDCCH candidates and sending them can be implemented in the following two methods:

[0227] The first method is a method of encoding a DCI payload (e.g., control information + CRC) through a channel encoder (e.g., a polarization encoder) and dividing it into two TRPs and transmitting it. That is, the first method means a method of dividing the coded bits obtained according to the encoding result into two TRPs and transmitting them in the two TRPs. Here, the entire DCI payload may be encoded into the coded bits transmitted by each TRP, but is not limited thereto, and only some DCI payloads may be encoded.

[0228] The second method divides the DCI payload (e.g., control information + CRC) into two DCIs (DCI 1 and DCI 2) and encodes each of them through a channel encoder (e.g., a polarization encoder). Thereafter, each of the two TRPs can send coded bits corresponding to DCI 1 and coded bits corresponding to DCI 2 to the terminal.

[0229] That is, dividing / repeating the same PDCCH by multiple base stations (M-TRP) and sending it at multiple monitoring opportunities (MO) may mean: 1) for each base station (S-TRP), the coded bits encoding the entire DCI content of the corresponding PDCCH are repeatedly sent through each MO, 2) the coded bits encoding the entire DCI content of the corresponding PDCCH are divided into multiple parts, and each base station (S-TRP) sends different parts through each MO, or 3) the DCI content of the corresponding PDCCH is divided into multiple parts, and different parts are encoded (that is, separately encoded) for each base station (S-TRP) and sent through each MO.

[0230] The repetition / split transmission of the PDCCH may be understood as transmitting the PDCCH multiple times at multiple transmission opportunities (TOs).

[0231] Here, TO may mean a specific time and / or frequency resource unit in which the PDCCH is transmitted. For example, when the PDCCH is transmitted multiple times (to a specific RB) on slot 1, slot 2, slot 3, and slot 4, TO may mean each slot. As another example, if the PDCCH is transmitted multiple times (in a specific slot) on RB set 1, RB set 2, RB set 3, and RB set 4, TO may mean each RB set. As another example, if the PDCCH is transmitted multiple times at different times and frequencies, TO may mean each time / frequency resource. In addition, the TCI state for DMRS channel estimation may be set differently for each TO, and it may be assumed that the TOs in which the TCI state is set differently are sent through different TRPs / panels.

[0232] Repeated transmission or division of PDCCH by multiple base stations may mean that PDCCH is transmitted on multiple TOs, and the union of TCI states configured in the corresponding TOs is composed of two or more TCI states. For example, PDCCH transmitted in TO 1, TO 2, TO 3, TO 4 may mean that TCI state 1, TCI state 2, TCI state 3, TCI state 4 are configured in each of TO 1, TO 2, TO 3, TO 4, and TRP i transmits PDCCH in TO i collaboratively.

[0233] In describing the present disclosure, the UE repeatedly sending the same PUSCH to multiple base stations (ie, M-TRP) may mean that the UE sends the same data through multiple PUSCHs, and each PUSCH may be sent by optimizing the UL channels for different TRPs.

[0234] For example, the UE may repeatedly transmit the same data through PUSCH 1 and PUSCH 2. In this case, PUSCH 1 may be transmitted using UL TCI state 1 for TRP 1, and link adaptation such as precoder / MCS may also be scheduled to receive a channel optimized value for TRP 1 to transmit PUSCH. PUSCH 2 may be transmitted using UL TCI state 2 for TRP 2, and link adaptation such as precoder / MCS may also be scheduled for a channel optimized value for TRP 2 to transmit PUSCH. In this case, the repeatedly transmitted PUSCH 1 and PUSCH 2 may be transmitted as TDM, FDM, or SDM at different times.

[0235] In addition, when describing the present disclosure, the UE sending the same PUSCH to multiple base stations (i.e., M-TRP) by dividing the same PUSCH may mean sending one data through one PUSCH, but the resources allocated to the PUSCH are divided and optimized for UL channels of different TRPs for transmission.

[0236] For example, the UE may send the same data through a 10-symbol PUSCH. At this time, the first 5 symbols among the 10 symbols may be sent using UL TCI state 1 for TRP 1, and the UE may send a 5-symbol PUSCH (to TRP 1) by receiving a link adaptation such as a precoder / MCS and scheduling a channel optimized value for TRP 1. The remaining 5 symbols may be sent using UL TCI state 2 for TRP 2, and the UE may send the remaining 5-symbol PUSCH (about TRP 2) by receiving a link adaptation such as a precoder / MCS and scheduling a channel optimized value for TRP 2.

[0237] In the above example, a method has been described of dividing one PUSCH into time resources and performing TDM transmission for TRP 1 and TRP 2. However, the present disclosure is not limited thereto, and the UE may divide and transmit the same PUSCH to a plurality of base stations by using the FDM / SDM method.

[0238] The UE may repeatedly transmit the PUCCH to multiple base stations (similar to PUSCH transmission) or divide and transmit the same PUCCH.

[0239] Furthermore, when multiple TOs are indicated for the terminal in order to repeatedly transmit PDCCH / PDSCH / PUSCH / PUCCH or to divide and transmit PDCCH / PDSCH / PUSCH / PUCCH, for each TO, UL may be transmitted toward a specific TRP or DL ​​may be received from a specific TRP. At this time, the UL TO transmitted toward TRP 1 (or the TO of TRP 1) may mean a TO using the first value of two spatial relationships, two UL TCIs, two UL power control parameters, or two path loss (PL)-RSs indicated to the terminal. Furthermore, the UL TO transmitted toward TRP 2 (or the TO of TRP 2) may mean a TO using the second value of two spatial relationships, two UL TCIs, two UL power control parameters, or two PL-RSs indicated to the UE.

[0240] Similarly, in the case of DL transmission, the DL TO sent by TRP 1 (or the TO of TRP 1) may mean the TO using the first value of the two DL TCI states indicated to the terminal (for example, when two TCI states are set in the CORESET), and the DL TO sent by TRP 2 (or the TO of TRP 2) may mean the TO using the second value of the two DL TCI states indicated to the terminal (for example, two TCI states are set in the CORESET).

[0241] The present disclosure can be extended and applied to various channels such as PUSCH / PUCCH / PDSCH / PDCCH. In addition, the present disclosure can be extended and applied to both the case where channels are repeatedly transmitted and the case where channels are divided and transmitted in different space / time / frequency resources.

[0242] In addition, in terms of DCI transmission, the M-TRP transmission scheme can be designed as i) an M-TRP transmission scheme based on multiple DCI (M-DCI), in which each TRP sends different DCI, and ii) an M-TRP transmission scheme based on a single DCI (S-DCI), in which one TRP sends DCI. For example, in the case of S-DCI, since all scheduling information for data sent by the M-TRP needs to be transmitted through one DCI, it can be used in an ideal backhaul (ideal BH) environment where dynamic collaboration between two TRPs is possible.

[0243] Related to enhanced M-TRP sending and receiving

[0244] Regarding M-TRP transmission / reception in Rel-16 NR standardization, PDSCH transmission / reception according to the S-DCI-based M-TRP transmission scheme and the M-DCI-based M-TRP transmission scheme is supported.

[0245] First, the S-DCI-based M-TRP PDSCH transmission scheme will be described.

[0246] One of the SDM / FDM / TDM schemes can be used for S-DCI-based M-TRP PDSCH transmission. In the case of SDM, the base station sends one TB using multiple layers, but sends layers belonging to different DMRS CDM groups with different Tx beams (i.e., QCL RS or TCI states). Thus, compared with the existing S-TRP transmission scheme, the transmission capacity can be increased by increasing the number of layers. In addition, when one TB is sent using multiple layers, some layers are sent to TRP 1 and other layers are sent to TRP 2, thereby improving the channel reliability due to diversity gain.

[0247] In the case of FDM, Scheme 2a and Scheme 2b are supported. Here, Scheme 2a is a scheme for sending one TB using multiple RBs but sending RBs belonging to different RB groups using different Tx beams (i.e., QCL RS or TCI states). Scheme 2b is a scheme for sending the same TB using different RB groups but sending RBs belonging to different RB groups using different Tx beams (i.e., QCL RS or TCI states). In the case of TDM, Scheme 3 and Scheme 4 are supported. Here, Scheme 4 (i.e., inter-slot TDM) is a scheme for repeatedly sending the same TB in multiple slots but sending slots belonging to different slot groups using different Tx beams (i.e., QCL RS or TCI states). On the other hand, Scheme 3 (i.e., intra-slot TDM) is a scheme for repeatedly sending the same TB in multiple OFDM symbol groups but sending some OFDM symbol groups and the remaining OFDM symbol groups using different Tx beams (i.e., QCL RS or TCI states).

[0248] Next, the M-TRP PDSCH transmission scheme based on M-DCI will be described.

[0249] M-DCI-based MTRP PDSCH transmission is a scheme in which each TRP schedules and sends PDSCH through DCI. That is, TRP 1 sends PDSCH 1 through DCI 1, and TRP 2 sends PDSCH 2 through DCI 2. When PDSCH 1 and PDSCH 2 overlap on the same frequency and time resources, since two PDSCHs are received for the same RE, resource efficiency is improved and transmission capacity is increased. To this end, the concept of CORESET pool (meaning a group of multiple CORESETs) has been introduced. For example, TRP 1 sends PDCCH through CORESET belonging to CORESET pool 0, and also sends PDSCH scheduled by the corresponding PDCCH. TRP 2 sends PDCCH through CORESET belonging to CORESET pool 1, and also sends PDSCH scheduled by the corresponding PDCCH.

[0250] Even in the case of PUSCH, a specific TRP may schedule PUSCH transmissions to a UE through a CORESET belonging to each CORESET pool. For example, some PUCCH resources may be scheduled by TRP 1 and the remaining PUCCH resources may be scheduled by TRP 2. The UE may send independent PUSCH / PUCCH for each of TRP 1 and TRP 2.

[0251] In addition, the UE may identify a PUSCH (or PUCCH) scheduled by a DCI received based on a different CORESET (or a CORESET belonging to a different CORESET group) as a PUSCH (or PUCCH) sent to a different TRP or as a PUSCH (or PUCCH) of a different TRP. In addition, a scheme for UL transmissions (e.g., PUSCH / PUCCH) sent to different TRPs may be equally applied to UL transmissions sent to different panels belonging to the same TRP.

[0252] In addition, the CORESET group ID (or the CORESET pool index having the same meaning) described / mentioned in the present disclosure may mean the index / identification information (e.g., ID) used to distinguish the CORESET for each TRP / panel. In addition, the CORESET group may mean the group / union of CORESETs distinguished by the index / identification information (e.g., ID) / CORESET group ID used to distinguish the CORESET for each TRP / panel. As an example, the CORESET group ID may be specific index information defined in the CORESET configuration. That is, the CORESET group may be configured / indicated / defined by the index defined in the CORESET configuration for each CORESET. And / or, the CORESET group ID may mean the index / identification information / indicator for the classification / identification between the CORESETs configured to each TRP / panel / related to each TRP / panel.

[0253] The CORESET group ID described / mentioned in the present disclosure can be represented by replacing it with a specific index / specific identification information / specific indicator for classification / identification between CORESETs set / associated with each TRP / panel. The corresponding information can be configured / indicated by high-level signaling (e.g., RRC signaling, MAC-CE, etc.) and / or physical layer signaling (e.g., DCI). As an example, it can be configured / indicated to perform PDCCH detection for each TRP / panel in the corresponding CORESET group unit, and to perform UCI (e.g., CSI, HARQ-ACK / NACK, SR, etc.) for each TRP / panel in the corresponding CORESET group unit. And / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) can be configured / indicated to be managed / controlled separately. And / or, HARQ ACK / NACK (process / retransmission) for PDSCH / PUSCH scheduled for each TRP / panel in units of the corresponding CORESET group can be managed.

[0254] For example, a high-level parameter ControlResourceSet IE (information element) is used to configure a time / frequency control resource set (control resource set CORESET). The corresponding CORESET may be associated with the detection / reception of downlink control information. The ControlResourceSet IE may include a CORESET-related ID (e.g., controlResourceSetID) / CORESET pool index for the CORESET (e.g., CORESETPoolIndex) / time / frequency resource settings of the CORESET / TCI information associated with the CORESET. As an example, the index of the CORESET pool (e.g., CORESETPoolIndex) may be configured to 0 or 1. In the above description of the present disclosure, a CORESET group may correspond to a CORESET pool, and a CORESET group ID may correspond to a CORESET pool index (e.g., CORESETPoolIndex). The aforementioned ControlResourceSet (i.e., CORESET) may be configured through high-level signaling (e.g., RRC signaling).

[0255] In addition, regarding M-TRP transmission and reception in Rel-17 NR standardization, M-TRP PDCCH / PDSCH SFN transmission, M-TRP PUSCH repetition transmission based on S-DCI, and M-TRP PUCCH repetition transmission based on a single PUCCH resource are supported. In the transmission scheme, the same content (ie, DCI / UL TB / UCI, etc.) is repeatedly transmitted by improving the URLLC target to improve reliability. Here, M-TRP PDCCH repetition transmission is performed based on TDM or FDM, M-TRP PDCCH / PDSCH SFN transmission is performed in the same time / frequency / layer, and M-TRP PUSCH repetition transmission based on S-DCI is performed based on TDM, and M-TRP PUCCH repetition transmission based on a single PUCCH resource is performed based on TDM.

[0256] First, the S-DCI-based M-TRP PDCCH repetition transmission scheme will be described.

[0257] In the NR Rel-17 standardization, multiple CORESETs configured with different TCI states (i.e., different QCL RSs) for M-TRP PDCCH repetitive transmission are configured for the terminal, and multiple SS sets connected to the corresponding CORESETs are configured. The base station can indicate / configure that the SS set connected to one CORESET and the SS set connected to another CORESET are linked for repeated transmission to the terminal. Thus, the terminal can recognize that the PDCCH candidates of the corresponding SS set are repeatedly transmitted.

[0258] For example, two CORESETs (CORESET 0 and CORESET 1) may be configured to the terminal, CORESET 0 and CORESET 1 may be connected to SS set 0 and SS set 1, respectively, and SS set 0 and SS set 1 may be linked. The terminal may recognize that the same DCI is repeatedly transmitted in the PDCCH candidates of SS set 0 and the PDCCH candidates of SS set 1, and based on a specific rule, the terminal may recognize that a specific PDCCH candidate of SS set 0 and a specific PDCCH candidate of SS set 1 correspond to a pair configured to repeatedly transmit the same DCI. The two PDCCH candidates may be referred to as linked PDCCH candidates, and when the terminal correctly receives either of the two PDCCH candidates, the corresponding DCI may be successfully decoded. However, when receiving the PDCCH candidate of SS set 0, the terminal may use the QCL RS (i.e., DL beam) of the TCI state of CORESET 0 connected to SS set 0, and when receiving the PDCCH candidate of SS set 1, the terminal may use the QCL RS (i.e., DL beam) of the TCI state of CORESET 1 connected to SS set 1. Therefore, the terminal receives associated PDCCH candidates using different beams.

[0259] Next, the M-TRP PDCCH repetition transmission scheme based on M-DCI will be described.

[0260] As one of the M-TRP PDCCH repetition transmission types, multiple TRPs can repeatedly send the same DCI through the same time / frequency / DMRS port, and this transmission method can be called SFN PDCCH transmission. However, for SFN PDCCH transmission, the base station configures multiple TCI states in one CORESET instead of configuring multiple CORESETs in which different TCI states are configured. When the terminal receives a PDCCH candidate through an SS set connected to one CORESET, the terminal can perform channel estimation on the PDCCH DMRS and attempt to decode by using all of the multiple TCI states.

[0261] In addition, during the above-mentioned M-TRP PDSCH repeated transmission, the two TRPs repeatedly send the corresponding channels to different resources. However, when the resources used by the two TRPs are the same, that is, when the same channel is repeatedly sent through the same frequency / time / layer (i.e., DMRS port), the reliability of the corresponding channel can be improved. In this case, since the resources are not distinguished, the same repeatedly transmitted channel is received while being sent (i.e., in the air), so it can be identified as one channel (e.g., a composite channel) from the receiving side (e.g., a terminal). For SFN PDSCH transmission, two DL TCI states for PDSCH DMRS reception can be configured at the terminal.

[0262] Next, the S-DCI-based M-TRP PUSCH repetition transmission scheme will be described.

[0263] In the NR Rel-17 standardization, the base station configures two SRS sets to the terminal for S-DCI-based M-TRPPUSCH transmission, and each set is used to indicate the UL beam / QCL information for the UL Tx ports of TRP 1 and TRP 2. In addition, the base station can indicate the SRS resources for each SRS resource set by including two SRI fields in one DCI, and can indicate up to two PC parameter sets. For example, the first SRI field can indicate the SRS resources and PC parameter set defined in SRS resource set 0, and the second SRI field can indicate the SRS resources and PC parameter set defined in SRS resource set 1. The terminal can be indicated with the QCL information / UL beam, UL Tx port and PC parameter set for TRP 1 through the first SRI field, and thereby, the terminal performs PUSCH transmission in the TO corresponding to SRS resource set 0. Similarly, the terminal can be indicated the QCL information / UL beam, UL Tx port and PC parameter set for TRP 2 through the second SRI field, and thereby, the terminal performs PUSCH transmission in TO corresponding to SRS resource set 1.

[0264] Next, the M-TRP PUCCH repetition transmission scheme based on a single PUCCH resource will be described.

[0265] In the NR Rel-17 standardization, the base station can activate / configure two spatial relationship information about a single PUCCH resource to the terminal for M-TRP PUCCH transmission based on a single PUCCH resource (if FR1, two PC parameter sets are enabled / configured). When UL UCI is sent through the corresponding PUCCH resource, each spatial relationship information is used to indicate the spatial relationship information for TRP 1 and TRP 2 to the terminal respectively. For example, through the value indicated in the first spatial relationship information, the terminal is indicated to the Tx beam / PC parameters toward TRP 1, and the terminal uses the corresponding information to perform PUCCH transmission in the TO corresponding to TRP 1. Similarly, through the value indicated in the second spatial relationship information, the terminal is indicated to the Tx beam / PC parameters toward TRP 2, and the terminal uses the corresponding information to perform PUCCH transmission in the TO corresponding to TRP 2.

[0266] In addition, for the repeated transmission of M-TRP PUCCH, the configuration scheme is improved so that two spatial relationship information can be configured in the PUCCH resources. That is, when power control (PC) parameters such as PLRS, α, P0 and closed-loop index are set in each spatial relationship information, the spatial relationship RS can be configured. Therefore, the PC information and spatial relationship RS information corresponding to the two TRPs can be configured by two spatial relationship information. Thus, the terminal uses the first spatial relationship information to send UCI (i.e., CSI, ACK / NACK, SR, etc.) PUCCH in the first TO, and uses the second spatial relationship information to send the same UCI PUCCH in the second TO. In the present disclosure, a PUCCH resource configured with two spatial relationship information is referred to as an M-TRP PUCCH resource, and a PUCCH resource configured with one spatial relationship information is referred to as an S-TRP PUCCH resource.

[0267] In addition, in the NR wireless communication system, multi-TB PUSCH / PDSCH scheduling based on S-DCI can be considered. For example, in the ultra-high frequency band (e.g., more than 5.26 GHz, FR2 band) of the NR wireless communication system (e.g., NR system based on Rel-17), a scheme in which one DCI simultaneously schedules multiple PUSCH / PDSCHs can be supported.

[0268] As a specific example, multiple time resources (e.g., TDRA, transmission opportunity (TO)) can be indicated at one time by the time resource allocation field (e.g., TDRA field) of the DCI that schedules the PUSCH. In this case, different TBs for each TO can be sent through the PUSCH. The values ​​of the frequency resource allocation field (e.g., FDRA field), the modulation and coding scheme (MCS) field, the transmitted precoding matrix indicator (TPMI) field, and / or the SRS resource indicator (SRI) field of the DCI can be commonly applied to multiple scheduled TBs. In addition, the new data indicator (NDI) and the redundancy version (RV) for each TB can be indicated separately by the corresponding DCI, and a value for the number of HARQs can be indicated, but it can be increased sequentially in TO order based on the initial TO.

[0269] In addition, with respect to the NR wireless communication system, a method in which a terminal simultaneously transmits a plurality of channels / RS of the same type or a method in which a plurality of channels / RS of different types are simultaneously transmitted may be considered.

[0270] In the case of existing terminals, the operation of sending multiple channels / RS at a time is restricted. For example, a terminal can simultaneously send multiple SRS resources of different SRS resource sets for UL beam management, but multiple PUSCHs may not be sent at the same time. Different from this, in the future, enhanced terminals may be considered to relax the above restrictions and use multiple transmission panels to send multiple channels / RS simultaneously. Such a terminal may be referred to as a simultaneous transmission across multiple panels (STx MP) terminal.

[0271] For example, a method of scheduling two PUSCHs (i.e., a first PUSCH and a second PUSCH) corresponding to two UL TBs to the same resource element (RE) and configuring a first spatial information RS and a first power control (PC) parameter set for the first PUSCH and a second spatial information RS and a second PC parameter set for the second PUSCH may be applied. That is, a first UL TCI state may be configured for the first PUSCH, and a second UL TCI state may be configured for the second PUSCH. In this case, the terminal may send the first PUSCH using a first Tx spatial filter (e.g., a first panel) corresponding to the first UL TCI state, and may send the second PUSCH using a second Tx spatial filter (e.g., a second panel) corresponding to the second UL TCI state.

[0272] In this regard, when the base station schedules PUSCH through DCI, the base station can indicate to the terminal which of the STxMP scheme, the single-panel-based scheme, or the M-TRP-based PUSCH repetition transmission scheme is applied as the corresponding PUSCH transmission scheme. Here, the STxMP scheme is available when the terminal supports the STxMP capability, and the STxMP mode needs to be enabled for the terminal in advance through RRC signaling, etc. To this end, the existing SRS resource set indication field can be redefined, or a new DCI field can be introduced.

[0273] In addition, in the NR wireless communication system, the UL TCI state as well as the DL TCI state may be indicated by DL DCI (e.g., DCI format 1_1 / 1_2, etc.), and only the UL TCI state may be indicated without indicating the DL TCI state. Thus, the scheme for configuring UL spatial information (e.g., UL beam) and power control (PC) in the existing NR wireless communication system (e.g., the NR system in Rel-15 / 16) may be replaced / extended to be applied as a method for indicating the UL TCI state.

[0274] As a specific example, a UL TCI state can be indicated by the TCI field of the DL DCI, and the corresponding UL TCI state can be applied to all PUSCH / PUCCH after a specific time (e.g., beam application time). In addition, the corresponding UL TCI state can be applied to some or all of the SRS resource sets.

[0275] In this regard, a method of indicating multiple UL TCI states (and / or D1TCI states) through the TCI field of the DL DCI may also be considered.

[0276] PTRS-DMRS port association indication method for UL transmission in 8Tx-UE

[0277] The present disclosure proposes a method for indicating PTRS-DMRS port association for UL transmission in 8Tx-UE.

[0278] Here, the 8Tx terminal may mean a UE that can support 8 ports / layers for UL transmission.

[0279] In this regard, for SRS configuration for UL transmission in 8Tx-UE (e.g., codebook (CB) / non-codebook (NCB) based UL transmission, etc.), the UE can be configured with a single SRS resource set, or can be configured with up to two SRS resource sets.

[0280] For example, if the UE is defined as being configured with a single SRS resource set, the SRS resource set may be configured with up to eight single-port SRS resources. In this case, the UE may be configured with up to eight PUSCH layers or DMRS ports through one SRS resource set (e.g., SRS resource set 0), and may perform UL transmission based thereon.

[0281] As another example, if the UE is defined as being configured with up to two SRS resource sets, each SRS resource set may be configured with up to four single-port SRS resources. In this case, the UE may be configured with up to four PUSCH layers or DMRS ports through one SRS resource set (e.g., SRS resource set 0), and may be configured with up to four PUSCH layers or DMRS ports through another SRS resource set (e.g., SRS resource set 1). That is, the UE may perform UL transmission based on up to eight configured PUSCH layers or DMRS ports.

[0282] Below, the present disclosure illustrates a method for indicating PTRS-DMRS port association in consideration of the above-mentioned 8Tx-UE through a specific example.

[0283] The method according to an embodiment of the present disclosure is described as an indication method for 8Tx-UE, but is not limited thereto, and may be extended and applied to UE capable of supporting more ports / layers for UL transmission.

[0284] Implementation Method 1

[0285] The present embodiment relates to a method of indicating PTRS-DMRS port association when the number of PTRS ports of a terminal is set to 1.

[0286] When the number of PTRS ports is set to 1, the UE may receive information on which SRS resource among N SRS resources indicated by the SRI field is associated with the PTRS port through the PTRS-DMRS port association field.

[0287] In this regard, the SRI field and the PTRS-DMRS port association field may be included in a DCI (eg, DCI format 0_1, DCI format 0_2, etc.) that schedules PUSCH transmission.

[0288] For example, the SRI field may indicate to the UE the N1 SRS resources in SRS resource set 0 and the N2 SRS resources in SRS resource set 1. In this regard, if the UE is indicated as SRS resources in only a single SRS resource set, the N2 value may be 0. In this case, the PTRS-DMRS Port Association field may indicate to the UE which SRS resource among the N1+N2 SRS resources corresponding to the combined set is associated with the PTRS port.

[0289] At this time, since N SRS resources (e.g., N1+N2 SRS resources) are mapped one-to-one to N DMRS ports (e.g., N1+N2 DMRS ports), the indication can have the same meaning as indicating which DMRS port among the N DMRS ports is associated with the PTRS port.

[0290] The number of PTRS ports being set to 1 may mean that the maximum number of PTRS ports (e.g., a high-level parameter maxNrofPorts) is set to 1 (e.g., n1). Alternatively, even if the maximum number of PTRS ports is 2 (e.g., n2) or greater, the indicated N SRS resources (e.g., N1+N2 SRS resources) may be configured to all share the same PTRS port index through RRC configuration. In this case, since the number of PTRS ports actually transmitted is 1, it may be considered that the number of PTRS ports is set to 1.

[0291] When the PTRS-DMRS port association field in the DCI is set to k bits, n bits may be used to indicate to the UE which DMRS port among the aforementioned N DMRS ports (eg, N1+N2 DMRS ports) is associated with the PTRS port.

[0292] On the other hand, if the PTRS-DMRS port association field in the DCI is divided into a k1-bit first field and a k2-bit second field, one or more of the following example methods may be considered.

[0293] For example, which DMRS port among N DMRS ports (eg, N1+N2 DMRS ports) is associated with the PTRS port may be indicated to the UE by using k1+k2 bits, which are the sum of two fields (ie, the first field and the second field).

[0294] For another example, the DMRS ports that can be indicated by each field can be distinguished, and the PTRS-DMRS port association information can be indicated based on this. As a specific example, the first field can be defined to indicate by selecting one of {None, Port #0, Port #1}, and the second field can be defined to indicate by selecting one of {None, Port #2, Port #3}. If the number of PTRS ports is 1, one of the two fields needs to indicate None.

[0295] Implementation Method 2

[0296] The present embodiment relates to a method of indicating PTRS-DMRS port association when the number of PTRS ports of a UE is set to 2.

[0297] When the number of PTRS ports is set to 2, the UE can distinguish between n1 SRS resources configured as shared PTRS port index = 0 (hereinafter, PTRS port 0) and n2 SRS resources configured as shared PTRS port index = 1 (hereinafter, PTRS port 1) through RRC configuration among the N SRS resources indicated by the SRI field. The UE can receive information about which SRS resource among the n1 SRS resources sharing PTRS port 0 is associated with PTRS port 0 and which SRS resource among the n2 SRS resources sharing PTRS port 1 is associated with PTRS port 1 through the PTRS-DMRS port association field.

[0298] In this regard, the SRI field and the PTRS-DMRS port association field may be included in a DCI (eg, DCI format 0_1, DCI format 0_2, etc.) that schedules PUSCH transmission.

[0299] For example, the SRI field in the DCI may be used to indicate to the UE that N1 SRS resources in SRS resource set 0 and N2 SRS resources in SRS resource set 1 are received. In this regard, if the UE is instructed to receive only SRS resources in a single SRS resource set, the value of N2 may be 0. In this regard, the sum of N1 and N2 may be equal to the sum of n1 and n2, and as a special case, the N1 SRS resources may be equal to the n1 SRS resources, and the N2 SRS resources may be equal to the n2 SRS resources.

[0300] At this time, N SRS resources (e.g., N1+N2 SRS resources) can be mapped one-to-one with N DMRS ports (e.g., N1+N2 DMRS ports). Therefore, the information about which SRS resource is associated with PTRS port 0 and which SRS resource is associated with PTRS port 1 can have the same meaning as the information about which DMRS port is associated with PTRS port 0 and which DMRS port is associated with PTRS port 1.

[0301] The number of PTRS ports being set to 2 may mean that the maximum number of PTRS ports (e.g., a high-level parameter maxNrofPorts) is set to a value greater than or equal to 2 (e.g., n2), and N (e.g., N1+N2) SRS resources share a total of 2 PTRS port indexes through RRC configuration. For example, n1 SRS resources may be configured by RRC to share port 0, and n2 SRS resources may be configured by RRC to share port 1.

[0302] When the PTRS-DMRS port association field in the DCI is set to k bits (where k=k1+k2), the most significant bit (MSB) k1 bit may be used to indicate to the UE the DMRS port associated with PTRS port 0 among the n1 DMRS ports corresponding to the n1 SRS resources. In addition, the least significant bit (LSB) or the remaining k2 bits may be used to indicate to the UE the DMRS port associated with PTRS port 1 among the n2 DMRS ports corresponding to the n2 SRS resources. For example, k1 and k2 may be respectively agreed / defined to be equal to a value of k / 2.

[0303] On the other hand, it can be considered that the PTRS-DMRS port association field in the DCI is divided into a k1-bit first field and a k2-bit second field. In this case, the DMRS port associated with PTRS port 0 among the n1 DMRS ports corresponding to the n1 SRS resources can be indicated to the UE through the first field. Similarly, the DMRS port associated with PTRS port 1 among the n2 DMRS ports corresponding to the n2 SRS resources can be indicated to the UE through the second field.

[0304] In this regard, it may be desirable to configure k1 and k2 corresponding to each field size based on a worst-case scenario.

[0305] For example, for SRS resources belonging to an SRS resource set configured for a UE (e.g., SRS resource set 0, SRS resource set 1), the number of SRS resources configured to share PTRS port 0 through RRC signaling / configuration is referred to as L1, and the number of SRS resources configured to share PTRS port 1 is referred to as L2. In this case, k1 may be determined / defined as ceil(log2(L1)), and k2 may be determined / defined as ceil(log2(L2)). Here, ceil() may mean a ceil function.

[0306] For another example, if the maximum number of UL PUSCH layers that a UE can transmit is referred to as L, the values ​​of k1 and k2 may be equivalently determined / defined as ceil(log2(L)). Here, ceil() may mean a ceil function.

[0307] Additionally or alternatively, when N1 SRS resources are the same as n1 SRS resources, and when N2 SRS resources are the same as n2 SRS resources, k1 bit and k2 bit may be defined to indicate DMRS ports mapped to SRS resources within SRS resource set 0 and SRS resource set 1, respectively.

[0308] In a conventional wireless communication system (e.g., 3GPP NR Rel-17), a PTRS field is set for each SRS resource set, but if m PTRS ports are set, m DMRS ports can be indicated in each field. In contrast, in the case of the method proposed in the present disclosure, one DMRS port can be indicated by each field.

[0309] For example, if only one PTRS port is configured, only the first field may be used to indicate the DMRS port mapped to the SRS resource within the default SRS resource set (e.g., SRS resource set 0). Alternatively, only the second field may be used to indicate the DMRS port mapped to the SRS resource within the default SRS resource set (e.g., SRS resource set 1).

[0310] Implementation 3

[0311] The present embodiment relates to a method of indicating PTRS-DMRS port association when the number of PTRS ports of a UE is set to 3.

[0312] When the number of PTRS ports is set to 3, the UE can distinguish, through the SRI field, among the indicated N SRS resources, n1 SRS resources configured as shared PTRS port index = 0 (hereinafter, PTRS port 0) through RRC configuration, n2 SRS resources configured as shared PTRS port index = 1 (hereinafter, PTRS port 1), and n3 SRS resources configured as shared PTRS port index = 2 (hereinafter, PTRS port 2). The UE can receive information about which SRS resource among the n1 SRS resources for sharing PTRS port 0 is associated with PTRS port 0, information about which SRS resource among the n2 SRS resources for sharing PTRS port 1 is associated with PTRS port 1, and information about which SRS resource among the n3 SRS resources for sharing PTRS port 2 is associated with PTRS port 2 through the PTRS-DMRS port association field.

[0313] In this regard, the SRI field and the PTRS-DMRS port association field may be included in a DCI (eg, DCI format 0_1, DCI format 0_2, etc.) that schedules PUSCH transmission.

[0314] For example, the SRI field in the DCI may indicate to the UE N1 SRS resources in SRS resource set 0 and N2 SRS resources in SRS resource set 1. In this regard, if only SRS resources in a single SRS resource set are indicated to the UE, the value of N2 may be 0. In this regard, the sum of N1 and N2 may be equal to the sum of n1, n2, and n3.

[0315] At this time, N SRS resources (e.g., N1+N2 SRS resources) can be mapped one-to-one with N DMRS ports (e.g., N1+N2 DMRS ports). Therefore, which SRS resource can have the same meaning as the information for which PTRS port (e.g., PTRS port 0 / PTRS port 1 / PTRS port 2).

[0316] The number of PTRS ports being set to 3 may mean that the maximum number of PTRS ports (e.g., a high-level parameter maxNrofPorts) is set to a value greater than or equal to 3 (e.g., n3), and N (e.g., N1+N2) SRS resources share a total of 3 PTRS port indexes through RRC configuration. For example, n1 SRS resources may be configured by RRC to share port 0, n2 SRS resources may share port 1, and n3 SRS resources may share port 2.

[0317] When the PTRS-DMRS Port Association field in the DCI is set to k bits (where k=k1+k2+k3), the MSB k1 bit may be used to indicate to the UE the DMRS port associated with PTRS port 0. Additionally, the subsequent k2 bit may be used to indicate to the UE the DMRS port associated with PTRS port 1. Additionally, the subsequent k3 bit may be used to indicate to the UE the DMRS port associated with PTRS port 2. For example, k1, k2, and k3 may be respectively agreed / defined to be equal to a value of k / 3.

[0318] On the other hand, it can be considered that the PTRS-DMRS port association field in the DCI is divided into a k1-bit first field and a k2-bit second field.

[0319] In this case, the DMRS port associated with PTRS port 0 (among n1 DMRS ports corresponding to n1 SRS resources) can be indicated to the UE through the first field. In addition, the DMRS port associated with PTRS port 1 (among n2 DMRS ports corresponding to n2 SRS resources) can be indicated to the UE through some bits of the second field, and the DMRS port associated with PTRS port 2 (among n3 DMRS ports corresponding to n3 SRS resources) can be indicated to the UE through the remaining bits of the second field.

[0320] Alternatively, the DMRS ports associated with PTRS port 0 and PTRS port 1, respectively, may be indicated to the UE through some bits and remaining bits of the first field, and the DMRS port associated with PTRS port 1 may be indicated to the UE through the second field.

[0321] Alternatively, it may be considered to expand the number of PTRS-DMRS port association fields to be configured / defined to a number greater than 2 (e.g., 3). In this case, the first field may be defined to indicate a DMRS port association associated with PTRS port 0, the second field may be defined to indicate a DMRS port association associated with PTRS port 1, and the third field may be defined to indicate a DMRS port association associated with PTRS port 2.

[0322] In this regard, it may be desirable to configure k1, k2, and k3 based on a worst-case scenario. Here, k1, k2, and k3 may correspond to field sizes, respectively, or some combination thereof may correspond to one field.

[0323] For example, for SRS resources belonging to an SRS resource set (e.g., a single SRS resource set, multiple SRS resource sets, etc.) for PUSCH transmission to a UE, the number of SRS resources configured to share PTRS port 0 through RRC signaling / configuration is referred to as L1, the number of SRS resources configured to share PTRS port 1 is referred to as L2, and the number of SRS resources configured to share PTRS port 2 is referred to as L3. In this case, k1 may be determined / defined as ceil(log2(L1)), k2 may be determined / defined as ceil(log2(L2)), and k3 may be determined / defined as ceil(log2(L3)). Here, ceil() may mean a ceil function.

[0324] For another example, if the maximum number of UL PUSCH layers that the UE can transmit is referred to as L, the values ​​of k1, k2, and k3 may be identically determined / defined as ceil(log2(L)). Here, ceil() may mean a ceil function.

[0325] Additionally or alternatively, considering the case where the PTRS-DMRS port association field consists of two fields (i.e., the first field and the second field as described above), the size of the first field (e.g., k1) can be determined / defined as ceil(log2(L1)), and the size of the second field (e.g., k2) can be determined / defined as ceil(log2(L2))+ceil(log2(L3)).

[0326] In this case, the first field may indicate the association between PTRS port 0 and DMRS port. In addition, in the second field, the ceil(log2(L2)) bit may indicate the association between PTRS port 1 and DMRS port, and the ceil(log2(L3)) bit may indicate the association between PTRS port 2 and DMRS port.

[0327] Additionally or alternatively, considering the case where the PTRS-DMRS port association field consists of two fields (i.e., the first field and the second field as described above), the size of the first field (e.g., k1) can be determined / defined as ceil(log2(L1)), and the size of the second field (e.g., k2) can be determined / defined as ceil(log2(L2*L3)).

[0328] In this case, the first field may indicate the association between PTRS port 0 and the DMRS port. In addition, the second field may jointly indicate the association between PTRS port 1 and PTRS port 2 and the DMRS port. That is, the indication of the second field may be based on the joint encoding / decoding related to the DMRS port indication associated with PTRS port 1 and the DMRS port indication associated with PTRS port 2.

[0329] Implementation 4

[0330] The present embodiment relates to a method of indicating PTRS-DMRS port association when the number of PTRS ports of a terminal is set to 4.

[0331] When the number of PTRS ports is set to 4, the UE can distinguish among the N SRS resources indicated by the SRI field n1 SRS resources configured as shared PTRS port index = 0 (hereinafter, PTRS port 0), n2 SRS resources configured as shared PTRS port index = 1 (hereinafter, PTRS port 1), n3 SRS resources configured as shared PTRS port index = 2 (hereinafter, PTRS port 2), and n4 SRS resources configured as shared PTRS port index = 3 (hereinafter, PTRS port 3). The UE can be instructed through the PTRS-DMRS port association field to receive information on which of the n1 SRS resources for shared PTRS port 0 is associated with PTRS port 0, information on which of the n2 SRS resources for shared PTRS port 1 is associated with PTRS port 1, information on which of the n3 SRS resources for shared PTRS port 2 is associated with PTRS port 2, and information on which of the n4 SRS resources for shared PTRS port 3 is associated with PTRS port 3.

[0332] In this regard, the SRI field and the PTRS-DMRS port association field may be included in a DCI (eg, DCI format 0_1, DCI format 0_2, etc.) that schedules PUSCH transmission.

[0333] For example, the SRI field in the DCI may indicate to the UE N1 SRS resources in SRS resource set 0 and N2 SRS resources in SRS resource set 1. In this regard, if only SRS resources in a single SRS resource set are indicated to the UE, the value of N2 may be 0. In this regard, the sum of N1 and N2 may be equal to the sum of n1, n2, n3, and n4.

[0334] At this time, N SRS resources (e.g., N1+N2 SRS resources) can be mapped one-to-one with N DMRS ports (e.g., N1+N2 DMRS ports). Therefore, which SRS resource can have the same meaning as the information for which PTRS port (e.g., PTRS port 0 / PTRS port 1 / PTRS port 2).

[0335] The number of PTRS ports being set to 4 may mean that the maximum number of PTRS ports (e.g., a high-level parameter maxNrofPorts) is set to a value greater than or equal to 4 (e.g., n4), and N (e.g., N1+N2) SRS resources share a total of 4 PTRS port indexes through RRC configuration. For example, n1 SRS resources may be configured by RRC to share port 0, n2 SRS resources may be configured by RRC to share port 1, n3 SRS resources may be configured by RRC to share port 2, and n4 SRS resources may be configured by RRC to share port 3.

[0336] When the PTRS-DMRS Port Association field in the DCI is set to k bits (where k=k1+k2+k3+k4), the MSB k1 bit may be used to indicate to the UE the DMRS port associated with PTRS port 0. Additionally, the subsequent k2 bit may be used to indicate to the UE the DMRS port associated with PTRS port 1. Additionally, the subsequent k3 bit may be used to indicate to the UE the DMRS port associated with PTRS port 2. Additionally, the subsequent k4 bit may be used to indicate to the UE the DMRS port associated with PTRS port 3. For example, k1, k2, k3, and k4 may be respectively agreed / specified to be equal to the value k / 4.

[0337] On the other hand, it can be considered that the PTRS-DMRS port association field in the DCI is divided into a k1-bit first field and a k2-bit second field.

[0338] In this case, the DMRS port associated with PTRS port 0 (among n1 DMRS ports corresponding to n1 SRS resources) may be indicated to the UE through some bits of the first field, and the DMRS port associated with PTRS port 1 (among n2 DMRS ports corresponding to n2 SRS resources) may be indicated to the UE through the remaining bits of the first field. In addition, the DMRS port associated with PTRS port 2 (among n3 DMRS ports corresponding to n3 SRS resources) may be indicated to the UE through some bits of the second field, and the DMRS port associated with PTRS port 3 (among n4 DMRS ports corresponding to n4 SRS resources) may be indicated to the UE through the remaining bits of the second field.

[0339] Alternatively, it may be considered to expand the number of PTRS-DMRS port association fields to be configured / defined to a number greater than 2 (e.g., 4). In this case, the first field may be defined to indicate a DMRS port association associated with PTRS port 0, the second field may be defined to indicate a DMRS port association associated with PTRS port 1, the third field may be defined to indicate a DMRS port association associated with PTRS port 2, and the fourth field may be defined to indicate a DMRS port association associated with PTRS port 3.

[0340] In this regard, it may be desirable to configure k1, k2, k3, and k4 based on the worst case. Here, k1, k2, k3, and k4 may correspond to field sizes, respectively, or some combination thereof may correspond to one field.

[0341] For example, for SRS resources belonging to an SRS resource set (e.g., a single SRS resource set, multiple SRS resource sets, etc.) configured for PUSCH transmission to a terminal, the number of SRS resources configured to share PTRS port 0 through RRC signaling / configuration is referred to as L1, the number of SRS resources configured to share PTRS port 1 is referred to as L2, the number of SRS resources configured to share PTRS port 2 is referred to as L3, and the number of SRS resources configured to share PTRS port 3 is referred to as L4. In this case, k1 may be determined / defined as ceil(log2(L1)), k2 may be determined / defined as ceil(log2(L2)), k3 may be determined / defined as ceil(log2(L3)), and k4 may be determined / defined as ceil(log2(L4)). Here, ceil() may mean a ceil function.

[0342] For another example, if the maximum number of UL PUSCH layers that the UE can transmit is specified as L, the values ​​of k1, k2, k3, and k4 may be identically determined / defined as ceil(log2(L)). Here, ceil() may mean a ceil function.

[0343] Additionally or alternatively, considering the case where the PTRS-DMRS port association field consists of two fields (i.e., the first field and the second field as described above), the size of the first field (e.g., k1) can be determined / defined as ceil(log2(L1))+ceil(log2(L2)), and the size of the second field (e.g., k2) can be determined / defined as ceil(log2(L3))+ceil(log2(L4)).

[0344] In this case, in the first field, the ceil(log2(L1)) bit may indicate the association between the PTRS port 0 and the DMRS port, and the ceil(log2(L2)) bit may indicate the association between the PTRS port 1 and the DMRS port. In addition, in the second field, the ceil(log2(L3)) bit may indicate the association between the PTRS port 2 and the DMRS port, and the ceil(log2(L4)) bit may indicate the association between the PTRS port 3 and the DMRS port.

[0345] Additionally or alternatively, considering the case where the PTRS-DMRS port association field consists of two fields (i.e., the first field and the second field as described above), the size of the first field (e.g., k1) can be determined / defined as ceil(log2(L1*L2)), and the size of the second field (e.g., k2) can be determined / defined as ceil(log2(L3*L4)).

[0346] In this case, the first field may jointly indicate the association between PTRS port 0 and PTRS port 1 and the DMRS port. That is, the indication of the first field may be based on the joint encoding / decoding related to the DMRS port indication associated with PTRS port 0 and the DMRS port indication associated with PTRS port 1. In addition, the second field may jointly indicate the association between PTRS port 2 and PTRS port 3 and the DMRS port. That is, the indication of the second field may be based on the joint encoding / decoding related to the DMRS port indication associated with PTRS port 2 and the DMRS port indication associated with PTRS port 3.

[0347] The embodiments in the present disclosure described above may be applied individually or based on combination / combination between some embodiments.

[0348] In addition, regardless of whether the method according to the embodiment of the present disclosure is applicable, the information / factors / parameters used in the method can be indicated to the UE by the base station through specific signaling (for example, DCI, MAC-CE, RRC configuration / signal, etc.), or reported by the UE to the base station.

[0349] Figure 8 is a diagram illustrating an operation of a UE for performing a method of PTRS transmission and reception according to one embodiment of the present disclosure.

[0350] Figure 8 The operation of the UE based on the previously proposed method (for example, any one or a combination of Embodiments 1 to 4 and their detailed embodiments) is illustrated. Figure 8The examples are for ease of description and do not limit the scope of the present disclosure. Depending on the environment and / or configuration, the Figure 8 In addition, Figure 8 The UE in is only an example and may be implemented as follows Fig.10 For example, Fig.10 The processor 102 / 202 can control the use of the transceiver 106 / 206 to send and receive channels / signals / data / information (e.g., RRC signaling, MAC CE, DCI for UL / DL scheduling, SRS, PDCCH, PDSCH, PUSCH, PUCCH, etc.), and can control the storage of channels / signals / data / information to be sent or received in the memory 104 / 204.

[0351] also, Figure 8 The operation can be done by Fig.10 One or more processors (102, 202) in the process, and Figure 8 The operation can be used to drive Fig.10 Instructions / programs (e.g., instructions, executable code) of at least one processor (102, 202) are stored in a memory (e.g., Fig.10 in one or more memories (104, 204)).

[0352] At step S810 , the UE may receive information regarding configuration of an SRS resource set.

[0353] For example, the corresponding SRS resource set may correspond to an SRS resource set configured for codebook-based PUSCH transmission or non-codebook-based PUSCH transmission.

[0354] The corresponding SRS resource set may be configured to include one or more SRS resources, and each SRS resource may be configured to share a PTRS port.

[0355] At step S820 , the UE may receive DCI including a first PTRS-DMRS port association field and a second PTRS-DMRS port association field.

[0356] In this regard, when three PTRS ports are set for the UE, the first PTRS-DMRS port association field may indicate information for one DMRS port associated with one PTRS port, and the second PTRS-DMRS port association field may indicate information for two DMRS ports associated with two PTRS ports.

[0357] At this time, the field size for the first PTRS-DMRS port association field and the second PTRS-DMRS port association field can be determined based on the number of specific SRS resources belonging to the SRS resources configured for the UE (ie, the SRS resource set in step S810).

[0358] For example, the number of bits of the first PTRS-DMRS port association field may be determined based on the number of SRS resources configured to share one PTRS port among the SRS resources belonging to the SRS resource set configured for the UE. Specifically, the number of bits of the first PTRS-DMRS port association field may be determined as ceil(log2(L1)). Here, ceil() represents a ceil function, and L1 represents the number of SRS resources configured to share one PTRS port.

[0359] For example, the number of bits in the second PTRS-DMRS port association field may be determined based on the number of SRS resources configured to share two PTRS ports among SRS resources belonging to an SRS resource set configured for the UE.

[0360] For example, when the second PTRS-DMRS port association field consists of a first part and a second part, the number of bits of the first part can be determined based on the number of SRS resources configured to share the first PTRS port among the two PTRS ports, and the number of bits of the second part can be determined based on the number of SRS resources configured to share the second PTRS port among the two PTRS ports. Specifically, the number of bits of the first part can be determined by ceil(log2(L2)), and the number of bits of the second part can be determined by ceil(log2(L3)). Here, ceil() represents the ceil function, L2 represents the number of SRS resources configured to share the first PTRS port, and L3 represents the number of SRS resources configured to share the second PTRS port.

[0361] As another example, when two DMRS ports associated with two PTRS ports are jointly indicated, the number of bits of the second PTRS-DMRS port association field may be determined as ceil(log2(L2*L3)). Here, ceil() represents a ceil function, L2 represents the number of SRS resources configured to share a first PTRS port among the two PTRS ports, and L3 represents the number of SRS resources configured to share a second PTRS port among the two PTRS ports.

[0362] In addition, when four PTRS ports are set for the UE, the first PTRS-DMRS port association field and the second PTRS-DMRS port association field may each indicate information for two DMRS ports associated with the two PTRS ports.

[0363] For example, the number of bits of the first PTRS-DMRS port association field may be determined based on the number of SRS resources configured to share the first PTRS port and the number of SRS resources configured to share the second PTRS port among the SRS resources belonging to the SRS resource set configured for the UE. The number of bits of the second PTRS-DMRS port association field may be determined based on the number of SRS resources configured to share the third PTRS port and the number of SRS resources configured to share the fourth PTRS port among the SRS resources belonging to the SRS resource set configured for the UE.

[0364] As a specific example, when the first PTRS-DMRS port association field and the second PTRS-DMRS port association field each consist of two parts, the number of bits of the first PTRS-DMRS port association field can be determined as the sum of the number of bits according to the number of SRS resources configured to share the first PTRS port and the number of bits according to the number of SRS resources configured to share the second PTRS port. The number of bits of the second PTRS-DMRS port association field can be determined as the sum of the number of bits according to the number of SRS resources configured to share the third PTRS port and the number of bits according to the number of SRS resources configured to share the fourth PTRS port.

[0365] As a specific example, if the DMRS port associated with the first PTRS port and the DMRS port associated with the second PTRS port are jointly indicated, the number of bits of the first PTRS-DMRS port association field can be determined as ceil(log2(L1*L2)). In addition, if the DMRS port associated with the third PTRS port and the DMRS port associated with the fourth PTRS port are jointly indicated, the number of bits of the second PTRS-DMRS port association field can be determined as ceil(log2(L3*L4)). Here, ceil() represents the ceil function, L1 represents the number of SRS resources configured to share the first PTRS port, L2 represents the number of SRS resources configured to share the second PTRS port, L3 represents the number of SRS resources configured to share the third PTRS port, and L4 represents the number of SRS resources configured to share the fourth PTRS port.

[0366] In step S830, the UE may send a PTRS based on at least one of the first PTRS-DMRS port association field or the second PTRS-DMRS port association field.

[0367] The present invention can be implemented based on the description in the above embodiments (for example, embodiment 1, embodiment 2, embodiment 3, embodiment 4 and their detailed embodiments) in the present invention. Figure 8 Operation of the UE and / or information about configuration / indication.

[0368] Fig. 9 is a diagram illustrating an operation of a base station for performing PTRS transmission and reception according to one embodiment of the present disclosure.

[0369] Fig. 9 The operation of the base station based on the previously proposed method (for example, any one or a combination of Embodiments 1 to 4 and their detailed embodiments) is illustrated. Fig. 9 The examples are for ease of description and do not limit the scope of the present disclosure. Depending on the environment and / or configuration, the Fig. 9 In addition, Fig. 9 The base station in is only an example and can be implemented as follows Fig.10 For example, Fig.10 The processor 102 / 202 can control the use of the transceiver 106 / 206 to send and receive channels / signals / data / information (e.g., RRC signaling, MAC CE, DCI for UL / DL scheduling, SRS, PDCCH, PDSCH, PUSCH, PUCCH, etc.), and can control the storage of channels / signals / data / information to be sent or received in the memory 104 / 204.

[0370] also, Fig. 9 The operation can be done by Fig.10 One or more processors (102, 202) in the process, and Fig. 9 The operation can be used to drive Fig.10 Instructions / programs (e.g., instructions, executable code) of at least one processor (102, 202) are stored in a memory (e.g., Fig.10 in one or more memories (104, 204)).

[0371] In step S910, the base station may send information regarding configuration of an SRS resource set.

[0372] For example, the corresponding SRS resource set may correspond to an SRS resource set configured for codebook-based PUSCH transmission or non-codebook-based PUSCH transmission.

[0373] The corresponding SRS resource set may be configured to include one or more SRS resources, and each SRS resource may be configured to share a PTRS port.

[0374] In step S920 , the base station may transmit a DCI including a first PTRS-DMRS port association field and a second PTRS-DMRS port association field.

[0375] In this regard, when three PTRS ports are configured for the UE, the first PTRS-DMRS port association field may indicate information for one DMRS port associated with one PTRS port, and the second PTRS-DMRS port association field may indicate information for two DMRS ports associated with two PTRS ports.

[0376] At this time, the field size for the first PTRS-DMRS port association field and the second PTRS-DMRS port association field can be determined based on the number of specific SRS resources belonging to the SRS resources configured for the UE (ie, the SRS resource set in step S810).

[0377] In step S930, the base station may receive a PTRS based on at least one of the first PTRS-DMRS port association field or the second PTRS-DMRS port association field.

[0378] Details about the size, configuration, etc. of the first PTRS-DMRS port association field and the second PTRS-DMRS port association field are as follows: Figure 8 are similar to those described in Fig. 9 Its detailed description is omitted.

[0379] The present invention can be implemented based on the description in the above embodiments (for example, embodiment 1, embodiment 2, embodiment 3, embodiment 4 and their detailed embodiments) in the present invention. Fig. 9 The operation of the base station and / or information about the configuration / instructions.

[0380] General devices to which the present disclosure can be applied

[0381] Fig.10 A block diagram of a wireless communication device according to an embodiment of the present disclosure is illustrated.

[0382] Reference Fig.10 , the first wireless device 100 and the second wireless device 200 can send and receive wireless signals through various radio access technologies (e.g., LTE, NR).

[0383] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may further 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 description, function, process, suggestion, method and / or operation flow chart disclosed in the present disclosure. For example, the processor 102 may send a wireless signal including the first information / signal through the transceiver 106 after generating the first information / signal by processing the information in the memory 104. In addition, the processor 102 may receive a wireless signal including the second information / signal through the transceiver 106, and then store the information obtained by the 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 related to the operation of the processor 102. For example, the memory 104 may store software codes including commands for executing all or part of the processing controlled by the processor 102 or for executing the description, function, process, suggestion, method and / or operation flow chart disclosed in the present disclosure. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver 106 may be connected to the processor 102 and may send and / or receive wireless signals through one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used in conjunction with an RF (radio frequency) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0384] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may further 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 description, function, process, suggestion, method and / or operation flowchart disclosed in the present disclosure. For example, the processor 202 may generate third information / signal by processing the information in the memory 204, and then transmit the wireless signal including the third information / signal through the transceiver 206. In addition, the processor 202 may receive the wireless signal including the fourth information / signal through the transceiver 206, and then store the information obtained by the signal processing of the fourth information / signal 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 codes including commands for executing all or part of the processing controlled by the processor 202 or for executing the description, function, process, suggestion, method and / or operation flowchart disclosed in the present disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver 206 may be connected to the processor 202 and may send and / or receive wireless signals through one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used in conjunction with an RF unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0385] In the following, the hardware elements of the wireless device 100, 200 will be described in more detail. Without limitation thereto, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 may generate one or more PDUs (protocol data units) and / or one or more SDUs (service data units) according to the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in the present disclosure. One or more processors 102, 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, suggestions, and / or methods disclosed in the present disclosure to provide it to one or more transceivers 106, 206. One or more processors 102, 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106, 206 according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow charts disclosed in the present disclosure, and obtain the PDU, SDU, message, control information, data, or information.

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

[0387] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, signals, messages, information, programs, codes, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located inside and / or outside one or more processors 102, 202. In addition, 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.

[0388] One or more transceivers 106, 206 may send user data, control information, wireless signals / channels, etc. mentioned in the method and / or operation flow chart of the present disclosure to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc. mentioned in the description, function, process, suggestion, method and / or operation flow chart disclosed in the present disclosure from one or more other devices. For example, one or more transceivers 106, 206 may be connected to one or more processors 102, 202 and may send and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to send user data, control information or wireless signals to one or more other devices. In addition, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information or wireless signals from one or more other devices. In addition, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 may be configured to send and receive user data, control information, wireless signals / channels, etc. mentioned in the description, functions, processes, suggestions, methods, and / or operation flow charts, etc. disclosed in the present disclosure through one or more antennas 108, 208. In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received wireless signals / channels, etc. from RF band signals into baseband signals to process received user data, control information, wireless signals / channels, etc. by using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, wireless signals / channels, etc. processed by using one or more processors 102, 202 from baseband signals into RF band signals. Thus, one or more of the transceivers 106 , 206 may include (analog) oscillators and / or filters.

[0389] The above-mentioned embodiments are to combine the elements and features of the present disclosure in a predetermined form. Unless otherwise explicitly mentioned, each element or feature should be considered as optional. Each element or feature can be implemented in a form that is not combined with other elements or features. In addition, the embodiments of the present disclosure may include combined partial elements and / or features. The order of the operations described in the embodiments of the present disclosure may be changed. Some elements or features of an embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. Obviously, the embodiments may include claims that do not have a clear reference relationship in the combined claims, or may be included as new claims by modification after application.

[0390] It is clear to those skilled in the relevant art that the present disclosure can be implemented in other specific forms within the scope of the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted restrictively in every aspect, but should be considered as illustrative. The scope of the present disclosure should be determined by the reasonable interpretation of the attached claims, and all changes within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0391] The scope of the present disclosure includes software or machine executable commands (e.g., operating systems, applications, firmware, programs, etc.) that perform operations in a device or computer according to the methods of various embodiments, and non-transitory computer-readable media that enable software or commands, etc. to be stored and executable in a device or computer. Commands that can be used to program a processing system that performs the features described in the present disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in the present disclosure can be implemented by using a computer program product that includes such a storage medium. The storage medium may include a high-speed random access memory, such as DRAM, SRAM, DDRRAM, or other random access solid-state storage devices, but is not limited thereto, and it may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory optionally includes one or more storage devices located away from the processor. The memory, or alternatively, the non-volatile memory device in the memory includes a non-transitory computer-readable storage medium. The features described in this disclosure may be stored in any machine-readable medium to control the hardware of a processing system, and may be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using the results from the 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.

[0392] Here, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may include narrowband Internet of Things for low-power communication, as well as LTE, NR and 6G. Here, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, which may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2 and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may perform communication based on LTE-M technology. Here, for example, LTE-M technology may be an example of LPWAN technology and may be referred to as various names such as eMTC (enhanced machine type communication). For example, LTE-M technology may be implemented in at least any one of various standards, including 1) LTE CAT 0; 2) LTE Cat M1; 3) LTE Cat M2; 4) LTE non-BL (non-bandwidth limited); 5) LTE-MTC; 6) LTE machine type communication; and / or 7) LTE M, etc., and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100, 200 of the present disclosure may include at least any one of ZigBee, Bluetooth, and a low power wide area network (LPWAN) considering low power communication, and is not limited to the above names. For example, ZigBee technology can generate a PAN (Personal Area Network) related to small / low power digital communication based on various standards (e.g., IEEE 802.15.4, etc.), and can be called various names.

[0393] Industrial Applicability

[0394] The method proposed in the present disclosure is mainly described based on examples applied to 3GPP LTE / LTE-A and 5G systems, but can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method performed by a user equipment UE in a wireless communication system, the method comprising the following steps: Receiving information on configuration of a sounding reference signal (SRS) resource set; receiving downlink control information DCI, wherein the DCI includes a first phase tracking reference signal demodulation reference signal PTRS-DMRS port association field and a second PTRS-DMRS port association field; and sending a PTRS based on at least one of the first PTRS-DMRS port association field or the second PTRS-DMRS port association field, Wherein, based on that three PTRS ports are configured for the UE, the first PTRS-DMRS port association field indicates information for one DMRS port associated with one PTRS port, and the second PTRS-DMRS port association field indicates information for two DMRS ports associated with two PTRS ports, and The field sizes of the first PTRS-DMRS port association field and the second PTRS-DMRS port association field are determined based on the number of specific SRS resources belonging to the SRS resource set.

2. The method according to claim 1, in, The number of bits of the first PTRS-DMRS port association field is determined based on the number of SRS resources configured to share the one PTRS port among the SRS resources belonging to the SRS resource set.

3. The method according to claim 2, in, The number of bits of the first PTRS-DMRS port association field is determined by ceil(log2(L1)), Herein, ceil() represents a ceil function, and L1 represents the number of SRS resources configured to share the one PTRS port.

4. The method according to claim 1, in, The number of bits of the second PTRS-DMRS port association field is determined based on the number of SRS resources configured to share the two PTRS ports among the SRS resources belonging to the SRS resource set.

5. The method according to claim 4, in, Based on the second PTRS-DMRS port association field including a first part and a second part, the number of bits of the first part is determined based on the number of SRS resources configured to share the first PTRS port among the two PTRS ports, and the number of bits of the second part is determined based on the number of SRS resources configured to share the second PTRS port among the two PTRS ports.

6. The method according to claim 5, in, The number of bits of the first portion is determined by ceil(log2(L2)), and the number of bits of the second portion is determined by ceil(log2(L3)), Among them, ceil() represents the ceil function, L2 represents the number of SRS resources configured to share the first PTRS port, and L3 represents the number of SRS resources configured to share the second PTRS port.

7. The method according to claim 4, in, Based on the two DMRS ports associated with the two PTRS ports being jointly indicated, the number of bits of the second PTRS-DMRS port association field is determined to be ceil(log2(L2*L3)), Among them, ceil() represents the ceil function, L2 represents the number of SRS resources configured to share the first PTRS port among the two PTRS ports, and L3 represents the number of SRS resources configured to share the second PTRS port among the two PTRS ports.

8. The method according to claim 1, in, Based on that four PTRS ports are configured for the UE, the first PTRS-DMRS port association field and the second PTRS-DMRS port association field each indicate information for two DMRS ports associated with two PTRS ports.

9. The method according to claim 8, in, The number of bits of the first PTRS-DMRS port association field is determined based on the number of SRS resources configured to share the first PTRS port and the number of SRS resources configured to share the second PTRS port among the SRS resources belonging to the SRS resource set, and The number of bits of the second PTRS-DMRS port association field is determined based on the number of SRS resources configured to share the third PTRS port and the number of SRS resources configured to share the fourth PTRS port among the SRS resources belonging to the SRS resource set.

10. The method according to claim 9, in, Based on that each of the first PTRS-DMRS port association field and the second PTRS-DMRS port association field includes two parts, The number of bits of the first PTRS-DMRS port association field is determined as a sum of the number of bits according to the number of SRS resources configured to share the first PTRS port and the number of bits according to the number of SRS resources configured to share the second PTRS port, and The number of bits of the second PTRS-DMRS port association field is determined as a sum of a number of bits according to a number of SRS resources configured to share the third PTRS port and a number of bits according to a number of SRS resources configured to share the fourth PTRS port.

11. The method according to claim 9, in, Based on the DMRS port associated with the first PTRS port and the DMRS port associated with the second PTRS port being jointly indicated, the number of bits of the first PTRS-DMRS port association field is determined to be ceil(log2(L1*L2)), and wherein, based on the DMRS port associated with the third PTRS port and the DMRS port associated with the fourth PTRS port being jointly indicated, the number of bits of the second PTRS-DMRS port association field is determined to be ceil(log2(L3*L4)), Among them, ceil() represents the ceil function, L1 represents the number of SRS resources configured to share the first PTRS port, L2 represents the number of SRS resources configured to share the second PTRS port, L3 represents the number of SRS resources configured to share the third PTRS port, and L4 represents the number of SRS resources configured to share the fourth PTRS port.

12. A user equipment UE in a wireless communication system, the UE comprising: at least one transceiver; as well as at least one processor coupled to the at least one transceiver, Wherein, the at least one processor is configured to: Receiving information on configuration of a sounding reference signal (SRS) resource set; receiving downlink control information DCI, wherein the DCI includes a first phase tracking reference signal demodulation reference signal PTRS-DMRS port association field and a second PTRS-DMRS port association field; and sending a PTRS based on at least one of the first PTRS-DMRS port association field or the second PTRS-DMRS port association field, Wherein, based on that three PTRS ports are configured for the UE, the first PTRS-DMRS port association field indicates information for one DMRS port associated with one PTRS port, and the second PTRS-DMRS port association field indicates information for two DMRS ports associated with two PTRS ports, and The field sizes of the first PTRS-DMRS port association field and the second PTRS-DMRS port association field are determined based on the number of specific SRS resources belonging to the SRS resource set.

13. A method performed by a base station in a wireless communication system, the method comprising the following steps: Sending information on configuration of a sounding reference signal SRS resource set; Sending downlink control information DCI, wherein the DCI includes a first phase tracking reference signal demodulation reference signal PTRS-DMRS port association field and a second PTRS-DMRS port association field; and receiving a PTRS based on at least one of the first PTRS-DMRS port association field or the second PTRS-DMRS port association field, Wherein, based on three PTRS ports being configured for the UE, the first PTRS-DMRS port association field indicates information for one DMRS port associated with one PTRS port, and the second PTRS-DMRS port association field indicates information for two DMRS ports associated with two PTRS ports, and The field sizes of the first PTRS-DMRS port association field and the second PTRS-DMRS port association field are determined based on the number of specific SRS resources belonging to the SRS resource set.

14. A base station in a wireless communication system, the base station comprising: at least one transceiver; as well as at least one processor coupled to the at least one transceiver, Wherein, the at least one processor is configured to: Sending information on configuration of a sounding reference signal SRS resource set; Sending downlink control information DCI, wherein the DCI includes a first phase tracking reference signal demodulation reference signal PTRS-DMRS port association field and a second PTRS-DMRS port association field; and receiving a PTRS based on at least one of the first PTRS-DMRS port association field or the second PTRS-DMRS port association field, Wherein, based on three PTRS ports being configured for the UE, the first PTRS-DMRS port association field indicates information for one DMRS port associated with one PTRS port, and the second PTRS-DMRS port association field indicates information for two DMRS ports associated with two PTRS ports, and The field sizes of the first PTRS-DMRS port association field and the second PTRS-DMRS port association field are determined based on the number of specific SRS resources belonging to the SRS resource set.

15. A processing device, the processing device being configured to control a user equipment in a wireless communication system, the processing device comprising: one or more processors; as well as One or more computer memories operatively connected to the one or more processors and storing instructions for performing the method according to any one of claims 1 to 11 upon execution by the one or more processors.

16. At least one non-transitory computer-readable medium storing one or more instructions, in, The one or more instructions are executed by one or more processors to control a device in a wireless communication system to perform the method according to any one of claims 1 to 11.

Images