Method and apparatus for transmitting and receiving ptrs

Abstract

A method according to an embodiment of the present specification comprises the steps of: receiving an uplink configuration associated with a PTRS; receiving, from a base station, DCI for scheduling of a PUSCH; and transmitting the PTRS to the base station on the basis of symbols allocated to the PUSCH. The PTRS is mapped to resource elements in the symbols on the basis of two CDM groups associated with configuration type 1. The resource elements are associated with three PTRS ports. Among the resource elements, resource elements associated with two PTRS ports associated with a DMRS port in the same CDM group are based on i) different resource element offsets and / or ii) different resource blocks.

Description

Method and device for transmitting and receiving PTRS

[0001] This specification relates to a method and device for PTRS transmission and reception.

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, they have expanded beyond voice to include data services. Currently, explosive growth in traffic is leading to resource shortages and users are demanding faster services, necessitating a more advanced mobile communication system.

[0003] Next-generation mobile communication systems must support explosive data traffic growth, dramatically increasing data rates per user, a vastly increased number of connected devices, ultra-low end-to-end latency, and high energy efficiency. To achieve these goals, various technologies are being studied, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.

[0004] For 3-Tx uplink transmissions introduced in Rel-19, using three PTRS ports for phase noise estimation may be more performance-efficient, depending on the UE implementation (e.g., a UE equipped with three panels). In such cases, a method supporting three PTRS ports is required.

[0005] According to the existing method (e.g., PTRS mapping operation based on DMRS configuration type 1), two PTRS ports are mapped to different REs (with different subcarrier locations) based on two CDM groups. However, when three PTRS ports are mapped based on DMRS configuration type 1, a problem may arise where the REs to which the two PTRS ports are mapped overlap in the frequency domain. The problem is described in more detail below.

[0006] When two PTRS ports are associated with different DMRS ports within the same CDM group, the offset values ​​used to determine the subcarrier positions of the REs to which the PTRSs are mapped are different for each of the two PTRS ports. Therefore, different PTRS ports are mapped to different REs.

[0007] However, according to the existing method, the DMRS port with the lowest index within the CDM group is defined to be associated with the PTRS port. If three PTRS ports are mapped to an RE based on DMRS configuration type 1, two PTRS ports (e.g., PTRS port 0, PTRS port 2) can be defined / configured to be associated with the same DMRS port (lowest indexed DMRS port) within the same CDM group. In this case, the offset value applied to each of the two PTRS ports is also the same. In other words, the subcarriers of the REs to which the two PTRS ports are mapped are the same. As described above, two of the three PTRS ports can be mapped to the same RE(s) in the frequency domain.

[0008] The purpose of this specification is to propose a method for solving the problem that REs associated with different PTRS ports overlap in the frequency domain when supporting three PTRS ports.

[0009] The technical problems to be achieved in this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which this specification pertains from the description below.

[0010] A method according to one embodiment of the present disclosure includes the steps of receiving an uplink configuration related to a phase tracking reference signal (PTRS) from a base station, receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) from the base station, and transmitting the PTRS to the base station based on symbols allocated to the PUSCH.

[0011] The above PTRS is mapped to resource elements within the symbols based on two Code Division Multiplexing (CDM) groups associated with configuration type 1.

[0012] The above resource elements are associated with three PTRS ports.

[0013] Among the above resource elements, resource elements associated with two PTRS ports associated with a demodulation reference signal (DoModulation Reference Signal, DMRS) port within the same CDM group are characterized in that they are based on i) different resource element offsets and / or ii) different resource blocks.

[0014] The above different resource element offsets may include i) a first resource element offset and ii) a second resource element offset.

[0015] The first resource element offset may be a value determined based on a first offset among the offsets defined for the setting type 1. The first offset may be i) an offset set based on the setting information or ii) a first offset among the offsets.

[0016] The second resource element offset may be a value determined based on the second offset. The second offset may be one of the remaining offsets excluding the first offset among the offsets.

[0017] The second offset may be a subsequent offset from the first offset among the offsets.

[0018] The different resource blocks may include i) a first resource block and ii) a second resource block. The first resource block may be determined based on a frequency density associated with the PTRS. The second resource block may be a subsequent resource block to the first resource block.

[0019] The above different resource blocks may include resource blocks associated with each of the three PTRS ports.

[0020] The above different resource blocks may include i) a first resource block associated with a first PTRS port, ii) a second resource block associated with a second PTRS port, and iii) a third resource block associated with a third PTRS port.

[0021] The first resource block may be determined based on a frequency density associated with the PTRS. The second resource block may be a subsequent resource block to the first resource block. The third resource block may be a subsequent resource block to the second resource block.

[0022] A DMRS port associated with each PTRS port may be defined. The number of bits in the PTRS-DMRS association field in the DCI may be 0.

[0023] The above PUSCH may be associated with codebook based UL transmission based on three antenna ports.

[0024] A terminal according to another embodiment of the present disclosure includes one or more transceivers, one or more processors, and one or more memories connected to the one or more processors and storing instructions.

[0025] The above instructions are characterized in that they cause the terminal to perform all steps of any one of the above methods based on being executed by the one or more processors.

[0026] According to another embodiment of the present disclosure, a device comprises one or more memories and one or more processors functionally connected to the one or more memories. The one or more memories are characterized in that they store instructions that cause the device to perform all steps of any one of the above methods based on execution by the one or more processors.

[0027] A non-transitory computer-readable storage medium according to another embodiment of the present disclosure stores instructions, characterized in that the instructions, when executed by one or more processors, cause a terminal to perform all steps of any one of the above methods.

[0028] A method according to another embodiment of the present disclosure includes the steps of transmitting an uplink configuration related to a phase tracking reference signal (PTRS) to a terminal, transmitting downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) to the terminal, and receiving the PTRS from the terminal based on symbols allocated to the PUSCH.

[0029] The above PTRS is mapped to resource elements within the symbols based on two Code Division Multiplexing (CDM) groups associated with configuration type 1.

[0030] The above resource elements are associated with three PTRS ports.

[0031] Among the above resource elements, resource elements associated with two PTRS ports associated with a demodulation reference signal (DoModulation Reference Signal, DMRS) port within the same CDM group are characterized in that they are based on i) different resource element offsets and / or ii) different resource blocks.

[0032] A base station according to another embodiment of the present disclosure includes one or more transceivers, one or more processors, and one or more memories coupled to the one or more processors and storing instructions.

[0033] The above instructions are characterized in that they cause the base station to perform all steps of the method based on being executed by the one or more processors.

[0034] According to an embodiment of the present specification, when three PTRS ports are mapped to RE(s) based on configuration type 1, different PTRS ports can be prevented from being mapped to the same RE. In addition, since phase noise can be estimated for each of the three PTRS ports, the phase noise estimation performance required due to non-coherent UL transmission can be improved.

[0035] The effects that can be obtained from this specification are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the technical field to which this specification belongs from the description below.

[0036] Figure 1 is a diagram showing an example of uplink transmission and reception operation.

[0037] Figure 2 is a diagram showing the mapping of PTRS ports by DMRS type according to the existing method.

[0038] FIG. 3 is a diagram illustrating the mapping of PTRS ports according to an embodiment of the present specification.

[0039] Figure 4 illustrates an RB location to which a PTRS port is mapped according to the conventional method.

[0040] FIG. 5 is an example of an RB location for a PTRS port according to an embodiment of the present specification.

[0041] FIG. 6 is another example of RB locations for a PTRS port according to an embodiment of the present specification.

[0042] FIG. 7 is a flowchart illustrating a method according to one embodiment of the present specification.

[0043] FIG. 8 is a flowchart illustrating a method according to another embodiment of the present specification.

[0044] FIG. 9 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0045] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to illustrate exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be implemented. The following detailed description includes specific details to provide a thorough understanding of the present disclosure.

[0046] In some cases, to avoid ambiguity in the concepts of this specification, well-known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.

[0047] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal, and a receiver may be part of a base station. A base station may be expressed as a first communication device, and a terminal may be expressed as a second communication device. A base station (BS) may be replaced by terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI system, RSU (road side unit), vehicle, robot, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, the terminal may be fixed or mobile, and may be replaced with 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, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0048] DMRS (demodulation reference signal)

[0049] DMRS reception procedure

[0050] Let's look at DMRS-related operations for PDSCH reception.

[0051] When receiving a PDSCH scheduled by DCI format 1_0 or before any dedicated higher layer configuration of the dmrs-AdditionalPosition, maxLength and dmrs-Type parameters, the UE assumes that no PDSCH is present in any symbol carrying a DM-RS except for a PDSCH with an allocated duration of 2 symbols with PDSCH mapping type B, a single symbol front-loaded DM-RS with configuration type 1 is transmitted on DM-RS port 1000, and that none of the remaining orthogonal antenna ports are associated with a PDSCH transmission to another UE.

[0052] Additionally, for a PDSCH with mapping type A, the UE assumes that there are dmrs-AdditionalPosition='pos2' and up to two additional single-symbol DM-RSs in the slot according to the PDSCH duration indicated in the DCI. For a PDSCH with an allocated duration of 7 symbols for a normal CP or 6 symbols for an extended CP with mapping type B, when a front-loaded DM-RS symbol is in the 1st or 2nd symbol of the PDSCH allocated duration, respectively, the UE assumes that there is one additional single-symbol DM-RS in the 5th or 6th symbol. Otherwise, the UE assumes that no additional DM-RS symbol is present. And, for a PDSCH having an allocation duration of 4 symbols with mapping type B, the terminal assumes that no additional DM-RS exists, and for a PDSCH having an allocation duration of 2 symbols with mapping type B, the terminal assumes that no additional DM-RS exists, and the terminal assumes that the PDSCH exists within a symbol carrying a DM-RS.

[0053] When receiving a PDSCH scheduled by DCI format 1_1 by a PDCCH with a CRC scrambled by C-RNTI, MCS-C-RNTI or CS (configured scheduling)-RNTI,

[0054] - The terminal can be set to the upper layer parameter dmrs-Type, and the set DM-RS configuration type is used to receive PDSCH.

[0055] - The terminal can be configured with the maximum number of front-loaded DM-RS symbols for the PDSCH by the upper layer parameter maxLength given by DMRS-DownlinkConfig.

[0056] The number of DM-RS ports can be scheduled by the antenna port index of DCI format 1_1.

[0057] The DMRS configuration type is configured by the dmrs-Type parameter in the DMRS-DownlinkConfig IE in Table 1. DMRS configuration type 1 has higher RS ​​density in the frequency domain and supports up to 4 (8) ports for single (double)-symbol DMRS. In addition, DMRS configuration type 1 supports length 2 F-CDM and FDM for single-symbol DMRS, and length 2 F / T-CDM and FDM for double-symbol DMRS. DMRS configuration type 2 supports more DMRS antenna ports and supports up to 6 (12) ports for single (double)-symbol DMRS.

[0058] Table 1 below shows an example of a DMRS-DownlinkConfig IE used to configure downlink DMRS for PDSCH.

[0059]

[0060] In Table 1, the dmrs-AdditionalPosition parameter indicates the position of additional DM-RS in DL, and if the parameter is not present, the UE applies the value pos2. The dmrs-Type parameter indicates the selection of DMRS type to be used for DL, and if the parameter is not present, the UE uses DMRS type 1. The maxLength parameter indicates the maximum number of OFDM symbols for DL ​​front-loaded DMRS, and len1 corresponds to the value 1. The PhaseTrackingRS parameter configures DL PTRS, and if the parameter is not present or is canceled, the UE assumes that there is no DL PTRS.

[0061] For DM-RS setup type 1,

[0062] - If the terminal is scheduled with one code word and the antenna port mapping is assigned with indices of {2, 9, 10, 11, or 30}, or if the terminal is scheduled with two code words,

[0063] The terminal can assume that none of the remaining orthogonal antenna ports are associated with transmission of PDSCH to other terminals.

[0064] For DM-RS setup type 2,

[0065] - If the terminal is scheduled with one codeword and the antenna port mapping is assigned with indices of {2,10,23}, or if the terminal is scheduled with two codewords,

[0066] The terminal can assume that none of the remaining orthogonal antenna ports are associated with transmission of PDSCH to other terminals.

[0067] An example of the DL DMRS procedure is described below.

[0068] The base station transmits DMRS configuration information to the terminal.

[0069] The above DMRS configuration information may refer to DMRS-DownlinkConfig IE. The DMRS-DownlinkConfig IE may include a dmrs-Type parameter, a dmrs-AdditionalPosition parameter, a maxLength parameter, a phaseTrackingRS parameter, etc.

[0070] The above dmrs-Type parameter is a parameter for selecting the DMRS configuration type to be used for DL. In NR, DMRS can be divided into two configuration types: (1) DMRS configuration type 1 and (2) DMRS configuration type 2. DMRS configuration type 1 is a type with a higher RS ​​density in the frequency domain, and DMRS configuration type 2 is a type with more DMRS antenna ports.

[0071] The above dmrs-AdditionalPosition parameter is a parameter indicating the position of an additional DMRS in the DL. If the parameter does not exist, the terminal applies the value pos2. The first position of the front-loaded DMRS is determined according to the PDSCH mapping type (type A or type B), and an additional DMRS may be configured to support a high-speed terminal. The front-loaded DMRS occupies one or two consecutive OFDM symbols and is indicated by RRC signaling and DCI (downlink control information).

[0072] The above maxLength parameter is a parameter indicating the maximum number of OFDM symbols for DL ​​front-loaded DMRS. The above phaseTrackingRS parameter is a parameter that configures DL PTRS. If the parameter does not exist or is canceled, the terminal assumes that there is no DL PTRS.

[0073] The above base station generates a sequence used for DMRS.

[0074] The sequence for the above DMRS is generated according to the mathematical expression 1 below.

[0075]

[0076] The above pseudo-random sequence is defined in 3gpp TS 38.211 5.2.1, i.e. can be a length-31 Gold sequence using two m-sequences. The pseudo-random sequence generator is initialized by the following mathematical expression 2.

[0077]

[0078] Here, is the number of OFDM symbols in the slot, is the slot number within the frame.

[0079] and, is provided, and if the PDSCH is scheduled by a PDCCH using DCI format 1_1 with a CRC scrambled by C-RNTI, MCS-C-RNTI or CS-RNTI, it is given by the higher-layer parameters scramblingID0 and scramblingID1 in the DMRS-DownlinkConfig IE, respectively.

[0080] - is provided, if the PDSCH is scheduled by a PDCCH using DCI format 1_0 with a CRC scrambled by the C-RNTI, MCS-C-RNTI, or CS-RNTI, given by the higher-layer parameter scramblingID0 in the DMRS-DownlinkConfig IE.

[0081] - , otherwise, quantity When DCI format 1_1 is used, it is given by the DMRS sequence initialization field in the DCI associated with the PDSCH transmission.

[0082] The base station maps the generated sequence to a resource element. Here, the resource element may mean at least one of time, frequency, antenna port, or code.

[0083] The base station transmits the DMRS to the terminal on the resource element. The terminal receives the PDSCH using the received DMRS.

[0084] UE DMRS transmission procedure

[0085] Let's examine DMRS-related operations for PUSCH reception. As discussed, UL refers to signal transmission (or communication) from the terminal to the base station. UL DMRS-related operations are similar to the DL DMRS-related operations discussed above, and the names of the DL-related parameters can be replaced with those for UL.

[0086] That is, DMRS-DownlinkConfig IE can be replaced with DMRS-UplinkConfig IE, PDSCH mapping type can be replaced with PUSCH mapping type, and PDSCH can be replaced with PUSCH. In addition, in DL DMRS related operations, the base station can be replaced with the terminal, and the terminal can be replaced with the base station. Sequence generation for UL DMRS can be defined differently depending on whether transform precoding is enabled.

[0087] More specifically, DMRS uses a PN sequence when CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) is used (or when transform precoding is not enabled), and uses a ZC sequence with a length of 30 or more when DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) is used (when transform precoding is enabled).

[0088] Table 2 below shows an example of a DMRS-UplinkConfig IE used to configure uplink DMRS for PUSCH.

[0089]

[0090] In Table 2, the dmrs-AdditionalPosition parameter indicates the position of additional DM-RS in UL. If this parameter is not present, the UE applies the value pos2. The dmrs-Type parameter indicates the selection of DMRS type to be used for UL. If this parameter is not present, the UE uses DMRS type 1.

[0091] The maxLength parameter indicates the maximum number of OFDM symbols for UL front-loaded DMRS, and len1 corresponds to a value of 1. The PhaseTrackingRS parameter configures UL PTRS. The transformPrecodingDisabled parameter indicates DMRS-related parameters for Cyclic Prefix OFDM. The transformPrecodingEnabled parameter indicates DMRS-related parameters for DFT-s-OFDM (Transform Precoding).

[0092] Below, we will look at the UE DM-RS transmission procedure in more detail.

[0093] If the transmitted PUSCH is neither scheduled by DCI format 0_1 ​​with CRC scrambled by C-RNTI, CS-RNTI or MCS-C-RNTI nor corresponds to a configured grant, the UE uses a single symbol front-loaded DM-RS of configuration type 1 on DM-RS port 0, and the remaining REs not used for DM-RS in the symbols are not used for any PUSCH transmission except for a PUSCH with an allocated duration of 2 or fewer OFDM symbols with disabled transform precoding. Additional DM-RS may be transmitted depending on the scheduling type and PUSCH duration, taking into account whether frequency hopping is enabled.

[0094] When frequency hopping is disabled: The UE assumes that dmrs-AdditionalPosition is equal to 'pos2' and up to two additional DM-RS can be transmitted per PUSCH duration.

[0095] When frequency hopping is enabled: The UE assumes that dmrs-AdditionalPosition is equal to 'pos1' and at most one additional DM-RS can be transmitted per PUSCH duration.

[0096] When the transmitted PUSCH is scheduled by activation DCI format 0_0 with CRC scrambled by CS-RNTI, the UE uses a single symbol front-loaded DM-RS of a configuration type provided by a higher layer parameter dmrs-Type of configuredGrantConfig on DM-RS port 0, and the remaining REs that are not used for DM-RS in the symbols are not used for any PUSCH transmission except for a PUSCH with an allocated duration of two or fewer OFDM symbols with disabled transform precoding, and an additional DM-RS with dmrs-AdditionalPosition from configuredGrantConfig can be transmitted based on the scheduling type and the PUSCH duration, taking into account whether frequency hopping is enabled.

[0097] When the transmitted PUSCH corresponds to a scheduled or configured grant by DCI format 0_1 ​​with a CRC scrambled by C-RNTI, CS-RNTI or MCS-RNTI,

[0098] - The terminal can be configured with the upper layer parameter dmrs-Type in DMRS-UplinkConfig, and the configured DM-RS configuration type is used for PUSCH transmission.

[0099] - The terminal can set the maximum number of front-loaded DM-RS symbols for PUSCH by the upper layer parameter maxLength in DMRS-UplinkConfig.

[0100] When a terminal transmitting a PUSCH sets the upper layer parameter phaseTrackingRS in DMRS-UplinkConfig, the terminal can assume that the following settings do not occur simultaneously for the transmitted PUSCH.

[0101] - For DM-RS configuration type 1 and type 2, any DM-RS port among 4-7 or 6-11 is scheduled for each UE, and PT-RS is transmitted from the terminal.

[0102] For PUSCH scheduled by DCI format 0_1, by activated DCI format 0_1 ​​with CRC scrambled by CS-RNTI or by configured grant type 1 configuration, the UE assumes that the DM-RS CDM group is not used for data transmission.

[0103] PTRS (Phase Tracking Reference Signal)

[0104] In the 5G NR standard, a phase-tracking reference signal (PTRS) was introduced to compensate for impairments caused by phase noise in high-frequency bands. This is because phase noise causes common phase error (CPE) and inter-carrier interference (ICI) in the frequency domain.

[0105] Below, the operations related to DL PTRS and UL PTRS are described in detail.

[0106] DL PTRS related actions

[0107] Below, an example of the DL PTRS procedure is described in detail.

[0108] The base station transmits PTRS configuration information to the terminal. The PTRS configuration information may refer to the PTRS-DownlinkConfig IE. The PTRS-DownlinkConfig IE may include the frequencyDensity parameter, the timeDensity parameter, the epre-Ratio parameter, the resourceElementOffset parameter, and the like.

[0109] The above frequencyDensity parameter is a parameter indicating the presence and frequency density of DL PTRS as a function of the scheduled BW. The above timeDensity parameter is a parameter indicating the presence and time density of DL PTRS as a function of the modulation and coding scheme (MCS). The above epre-Ratio parameter is a parameter indicating the EPRE (Energy Per Resource Element) between PTRS and PDSCH.

[0110] The base station generates a sequence used for PTRS. The sequence for PTRS is generated using the DMRS sequence of the same subcarrier, as shown in Equation 3 below. Sequence generation for PTRS can be defined differently depending on whether transform precoding is enabled, and Equation 3 below shows an example when transform precoding is disabled.

[0111]

[0112] Here, is located and subcarriers is the DMRS given in .

[0113] That is, the sequence of PTRS uses the sequence of DMRS, but more specifically, the sequence of PTRS in subcarrier k is identical to the sequence of DMRS in subcarrier k.

[0114] The base station maps the generated sequence to a resource element. Here, the resource element may mean at least one of time, frequency, antenna port, or code.

[0115] The position of the PTRS in the time domain is mapped to a specific symbol interval starting from the start symbol of the PDSCH allocation. If a DMRS symbol exists, the mapping is performed from the symbol following the DMRS symbol. The specific symbol interval may be 1, 2, or 4 symbols.

[0116] And, with respect to resource element mapping of PTRS, the frequency location of PTRS is determined by the frequency location of the associated DMRS port and the upper layer parameter UL-PTRS-RE-offset. Here, UL-PTRS-RE-offset is included in the PTRS configuration and indicates the subcarrier offset for UL PTRS for CP-OFDM.

[0117] For DL, a PTRS port is associated with the DMRS port with the lowest index among the scheduled DMRS ports. For UL, the base station configures which DMRS port is associated with a PTRS port via UL DCI.

[0118] The base station transmits the PTRS to the terminal on the above resource element.

[0119] UL PTRS related actions

[0120] UL PTRS-related operations are similar to DL PTRS-related operations discussed above, and the names of the parameters related to DL PTRS can be replaced with the names of the parameters related to UL PTRS. That is, PTRS-DownlinkConfig IE can be replaced with PTRS-UplinkConfig IE, and in DL PTRS-related operations, the base station can be replaced with the terminal, and the terminal can be replaced with the base station. Similarly, sequence generation for PTRS can be defined differently depending on whether transform precoding is enabled.

[0121] Downlink transmission and reception operations

[0122] The base station schedules downlink transmissions, including frequency / time resources, transport layers, downlink precoders, and MCS. In particular, the base station can determine a beam for PDSCH transmission to a terminal through beam management operations.

[0123] And, the terminal receives downlink control information (DCI: Downlink Control Information) for downlink scheduling (i.e., including scheduling information of PDSCH) from the base station on the PDCCH. DCI format 1_0 or 1_1 can be used for downlink scheduling, and in particular, DCI format 1_1 includes the following information: DCI format identifier (Identifier for DCI formats), bandwidth part indicator, frequency domain resource assignment, time domain resource assignment, PRB bundling size indicator, rate matching indicator, ZP CSI-RS trigger, antenna port(s), transmission configuration indication (TCI: Transmission configuration indication), SRS request, DMRS (Demodulation Reference Signal) sequence initialization.

[0124] In particular, the number of DMRS ports can be scheduled according to each state / index indicated in the Antenna port(s) field, and also single-user (SU) / multi-user (MU) transmission scheduling is possible. Specifically, the order of DMRS ports corresponding to the number of CWs can be predefined according to dmrs-type and maxLength, and the number and / or order of DMRS ports can be indicated through the antenna port field of DCI.

[0125] Additionally, the TCI field consists of 3 bits, and dynamically indicates QCL for DMRS by indicating up to 8 TCI states depending on the TCI field value. Then, the terminal receives downlink data from the base station on the PDSCH. When the terminal detects a PDCCH including DCI format 1_0 or 1_1, it decodes the PDSCH according to the instructions of the corresponding DCI.

[0126] Here, when the terminal receives a PDSCH scheduled by DCI format 1_1, the terminal can set the DMRS configuration type by the upper layer parameter 'dmrs-Type', and the DMRS configuration type is used to receive the PDSCH. In addition, the terminal can set the maximum number of front-loaded DMRS symbols for the PDSCH by the upper layer parameter 'maxLength'.

[0127] For DMRS configuration type 1, if the terminal is scheduled with a single codeword and is assigned an antenna port mapped to an index of {2, 9, 10, 11, or 30}, or if the terminal is scheduled with two codewords, the terminal assumes that all remaining orthogonal antenna ports are not associated with PDSCH transmissions to another terminal. Alternatively, for DMRS configuration type 2, if the terminal is scheduled with a single codeword and is assigned an antenna port mapped to an index of {2, 10, or 23}, or if the terminal is scheduled with two codewords, the terminal assumes that all remaining orthogonal antenna ports are not associated with PDSCH transmissions to another terminal.

[0128] Uplink transmission and reception operation

[0129] Figure 1 is a diagram showing an example of uplink transmission and reception operation.

[0130] Referring to Figure 1, the base station schedules uplink transmissions, such as frequency / time resources, transmission layers, uplink precoder, and MCS (S110). In particular, the base station can determine a beam for PUSCH transmission by the terminal through beam management operations. Then, the terminal receives DCI for uplink scheduling (i.e., including PUSCH scheduling information) from the base station on the PDCCH (S120). DCI format 0_0 or 0_1 can be used for uplink scheduling, and in particular, DCI format 0_1 ​​includes the following information: DCI format identifier, UL / SUL (Supplementary uplink) indicator, UL / SUL indicator, bandwidth part indicator, frequency domain resource assignment, time domain resource assignment, frequency hopping flag, modulation and coding scheme (MCS), SRS resource indicator (SRI), precoding information and number of layers, antenna port(s), SRS request, DMRS sequence initialization, UL-SCH (Uplink Shared Channel) indicator.

[0131] In particular, SRS resources set within the SRS resource set associated with the upper layer parameter 'usage' can be indicated by the SRS resource indicator field. In addition, 'spatialRelationInfo' can be set for each SRS resource, and its value can be one of {CRI, SSB, SRI}.

[0132] Then, the terminal transmits uplink data to the base station on the PUSCH (S130). If the terminal detects a PDCCH containing DCI format 0_0 or 0_1, it transmits the corresponding PUSCH according to the instructions of the corresponding DCI. Two transmission methods are supported for PUSCH transmission: codebook-based transmission and non-codebook-based transmission.

[0133] For codebook-based transmission, when the upper layer parameter 'txConfig' is set to 'codebook', the terminal is configured for codebook-based transmission. On the other hand, when the upper layer parameter 'txConfig' is set to 'nonCodebook', the terminal is configured for non-codebook-based transmission. If the upper layer parameter 'txConfig' is not set, the terminal does not expect to be scheduled by DCI format 0_1. When PUSCH is scheduled by DCI format 0_0, PUSCH transmission is based on a single antenna port. For codebook-based transmission, PUSCH can be scheduled by DCI format 0_0, DCI format 0_1, or semi-statically. When this PUSCH is scheduled by DCI format 0_1, the UE determines a PUSCH transmission precoder based on the SRI, the Transmit Precoding Matrix Indicator (TPMI), and the transmission rank from the DCI, as given by the SRS resource indicator field and the Precoding information and number of layers field. The TPMI is used to indicate a precoder to be applied across antenna ports, and corresponds to the SRS resource selected by the SRI when multiple SRS resources are configured. Alternatively, when a single SRS resource is configured, the TPMI is used to indicate a precoder to be applied across antenna ports, and corresponds to the single SRS resource. The transmission precoder is selected from an uplink codebook having the same number of antenna ports as the upper layer parameter 'nrofSRS-Ports'. When the upper layer in which the UE is set to 'codebook' is configured with the parameter 'txConfig', the UE is configured with at least one SRS resource.The SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS resource precedes the PDCCH carrying the SRI (i.e., slot n).

[0134] For non-codebook based transmission, PUSCH can be scheduled in DCI format 0_0, DCI format 0_1, or semi-statically. When multiple SRS resources are configured, the UE can determine the PUSCH precoder and transmission rank based on the wideband SRI, which is given by the SRS resource indicator in the DCI or the higher layer parameter 'srs-ResourceIndicator'. The UE uses one or multiple SRS resources for SRS transmission, and the number of SRS resources can be configured for simultaneous transmission within the same RB based on the UE capability. Only one SRS port is configured for each SRS resource. Only one SRS resource can be configured with the higher layer parameter 'usage' set to 'nonCodebook'. The maximum number of SRS resources that can be configured for non-codebook based uplink transmission is 4. The SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS transmission precedes the PDCCH carrying the SRI (i.e., slot n).

[0135] Description of STxMP (Simultaneous Transmission across Multi-panels)

[0136] In R18, a method for a UE to simultaneously transmit multiple channels / RSs of the same type or multiple channels / RSs of different types is being discussed. In the case of existing UEs, the operation of transmitting multiple channels / RSs at a time is restricted (e.g., simultaneous transmission of multiple SRS resources of different SRS sets is possible for UL beam measurement, but simultaneous transmission of multiple PUSCHs is not possible). However, in the case of advanced UEs in the future, this restriction will be relaxed and multiple channels or RSs will be transmitted simultaneously using multiple transmission panels. Such UEs are called STxMP UEs. For example, two PUSCHs corresponding to two UL TBs are scheduled on the same RE, and Spatial relation RS 1 and PC parameter Set 1 (i.e., UL TCI state 1) and Spatial relation RS 2 and PC parameter Set 2 (i.e., UL TCI state 2) are set for PUSCH 1 and 2 transmission, respectively. The UE transmits PUSCH 1 using panel 1 corresponding to UL TCI state 1 and simultaneously transmits PUSCH 2 using panel 2 corresponding to UL TCI state 2.

[0137] When a base station schedules a PUSCH through DCI, it can indicate whether the PUSCH will be transmitted as STxMP, as a single panel, or as MTRP PUSCH repetitions. Of course, the UE must have STxMP capability, and the STxMP mode must be enabled in advance, such as through RRC signaling. To achieve this, the existing SRS resource set indication field can be redefined and used, or a new DCI field can be introduced.

[0138] Two methods are being considered for the R18 STxMP transmission technique: SFN and SDM.

[0139] The SFN method transmits the same channel from one panel to another. However, since the UL channels of each panel are different, each panel is transmitted using a different precoder, different transmission power, and different transmission beam (i.e., spatial relation RS indicated by the UL TCI).

[0140] The SDM method is a method that can be transmitted from rank 2 and above, and it is a method in which panel 1 transmits some of the multi-layers and panel 2 transmits the remaining layers. For example, in 2-layer transmission, panel 1 transmits the 1st layer and panel 2 transmits the 2nd layer. Even in this case, since the UL channels of each panel are different, different precoders, different transmission powers, and different transmission beams (i.e., spatial relation RS indicated by UL TCI) are transmitted for each panel.

[0141] Panel is not a term used in the standard, and other resources / terms corresponding to panel are used. For example, different panels may be mapped to different SRS resource sets or SRS resources. For example, the first panel may be mapped to SRS resource set 0, the second panel may be mapped to SRS resource set 1, and the SRS resources in SRS resource set 0 may refer to the transmit antenna ports of the first panel, and the SRS resources in SRS resource set 1 may refer to the transmit antenna ports of the second panel.

[0142] Description of the Unified TCI framework

[0143] In R17, both the UL TCI state and the DL TCI state can be indicated through DL DCI (e.g. DCI format 1-1 or 1-2), or only the UL TCI state can be indicated without indicating the DL TCI state. Accordingly, the methods used for configuring UL beam and power control (PC) in the existing R15 / R16 are replaced in R17 with the above UL TCI state indication method. More specifically, in R17, one UL TCI state can be indicated through the TCI field of the DL DCI, and the UL TCI state is applied to all PUSCHs and all PUCCHs after a certain time called the beam application time, and can be applied to some or all of the indicated SRS resource sets. In R18, a method in which multiple UL TCI states (and / or DL ​​TCI states) are indicated through the TCI field of the DL DCI is under discussion.

[0144] AIML related explanation

[0145] With the advancement of AI / ML (Artificial intelligence / machine learning) technology, the node(s) and terminal(s) that make up the wireless communication network are becoming more intelligent / advanced. In particular, due to the intelligence of the network / base station, it is expected that various network / base station decision parameter values ​​(e.g., transmission / reception power of each base station, transmission power of each terminal, precoder / beam of the base station / terminal, time / frequency resource allocation for each terminal, duplex method of each base station, etc.) can be quickly optimized and derived / applied according to various environmental parameters (e.g., distribution / location of base stations, distribution / location / material of buildings / furniture, etc., location / movement direction / speed of terminals, climate information, etc.).

[0146] The previously discussed features (DMRS, PTRS, UL transmission / reception operations, AI / ML, etc.) can be applied in combination with the methods proposed in this specification, which will be described later, or can be supplemented to clarify the technical characteristics of the methods proposed in this specification. The methods described below are distinguished for convenience of explanation, and it is obvious that some components of one method can be substituted for some components of another method, or they can be applied in combination with each other.

[0147] In this specification, 'port' and 'antenna port' may be interpreted as having the same meaning. For example, PTRS (DMRS) port means PTRS (DMRS) antenna port, and vice versa.

[0148] In this specification, 'DMRS (or PTRS)' may mean 'DM-RS (or PT-RS)' and vice versa.

[0149] NR MIMO Rel19 and later standards can support UL PUSCH transmissions with 3Tx. Existing standards support 1 / 2 / 4 / 8Tx uplink transmissions. To support the 3Tx uplink transmission introduced in Rel19, a method for configuring 3-port PTRS is required, as shown in the WID below.

[0150] “Specify non-coherent UL codebook to facilitate 3-antenna-port codebook-based transmissions, without enhancement on UL full power transmission and without enhancement on SRS resource

[0151] Note: UL full power transmission mode 1 and 2 are not supported.”

[0152] A method and device for a 3 port PTRS configuration to support 3 Tx UL are proposed as follows.

[0153] Technical issues to be resolved

[0154] In 3Tx uplink transmission (for codebook based UL), the following three levels of coherency can be considered, and the number of PTRS ports required can vary depending on the transmission mode.

[0155] Full coherency: When all three ports are capable of coherent transmission,

[0156] -> 1 port PTRS configuration

[0157] Partial coherency: When only two ports are capable of coherent transmission,

[0158] -> 1 or 2 port PTRS configuration

[0159] Non-coherency: If no port is capable of coherent transmission,

[0160] -> 1 or 2 port PTRS configuration. Furthermore, a 2-port PTRS may not be sufficient to estimate the three phase noises of a 3-Tx UL, requiring a 3-port PTRS configuration. For example, a 3-Tx UE may consist of three panels, making coherent transmission between panels difficult. In such cases, independent phase noise estimation for each panel / Tx / DMRS port may be more beneficial for performance (even considering the increased PTRS overhead).

[0161] When configuring 2-port PTRS, the PTRS RE positions are determined by DMRS CDM (Code Division Multiplexing) group according to the existing standard. Therefore, the SC (subcarrier) positions of the 2 PTRS ports will not automatically overlap. However, if 3 PTRS ports are configured and the number of DMRS CDM groups is 2 (e.g. DMRS type 1 & FD-OCC length 2 / 4), if the existing PTRS RE mapping method is used as is, the RE subcarrier positions may overlap.

[0162] Considering the above problems, a method for estimating three phase noises during non-coherency PUSCH transmission for a 3Tx terminal is required for a 3 port PTRS configuration.

[0163] Below, the existing operations related to PTRS are described in detail.

[0164] When the higher layer parameter phaseTrackingRS is set, PT-RS is set for the scheduled PUSCH according to the DCI format. When the higher layer parameter phaseTrackingRS is not set, the terminal does not transmit PT-RS.

[0165] DMRS type 1 has a total of 8 ports, from port 0 to 8, for 1 FL symbol. When the maximum number of PTRS ports is set to 1, PTRS-DMRS association can be performed based on a 2-bit table. This example can be applied when two codewords are scheduled for a terminal. Specifically, among the 1st to 8th scheduled DMRS ports, the PTRS port can be associated with one of the four DMRS ports belonging to the codeword having the Higher MCS. One of the four DMRS ports can be indicated based on the 2-bit PTRS-DMRS association field of the DCI for the codeword having the Higher MCS.

[0166] When the maximum number of PTRS ports is set to 2, PTRS-DMRS association can be performed based on a 4-bit table. For example, the value of the MSB 2 bit of the PTRS-DMRS association field indicates one of the 1st to 4th DMRS ports that share PTRS port 0. The value of the LSB 2 bit of the PTRS-DMRS association field indicates one of the 1st to 4th DMRS ports that share PTRS port 1.

[0167] For the NCB PUSCH case, the 1st to 4th DMRS ports sharing PTRS port 0 can be identified by the PTRS port index=0 set in the SRS resource indicated by the SRI. The 1st to 4th DMRS ports sharing PTRS port 1 can also be identified in the same manner.

[0168] In the case of 1 CW (one codeword) of the CB PUSCH case, DMRS ports corresponding to layers using PUSCH antenna ports 1000 and 1002 share PTRS 0, and DMRS ports corresponding to layers using PUSCH antenna ports 1001 and 1003 share PTRS 1. And in the case of 2 CW (two codewords), DMRS ports corresponding to layers using PUSCH antenna ports 1000, 1001, 1004, and 1005 share PTRS 0, and DMRS ports corresponding to layers using PUSCH antenna ports 1002, 1003, 1006, and 1007 share PTRS 1.

[0169] The behavior according to the existing standard is as follows:

[0170] For non-codebook based UL transmission, the actual number of UL PT-RS ports to be transmitted is determined based on the SRI in DCI format 0_1, 0_2 or 0_3 or the upper layer parameter sri-ResourceIndicator in rrc-ConfiguredUplinkGrant. When two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 and the upper layer parameter usage of SRS-ResourceSet is set to 'noncodebook', the actual number of UL PT-RS ports to be transmitted for each SRS resource set is determined based on the SRI corresponding to the associated SRS resource set or the upper layer parameter sri-ResourceIndicator or sri-ResourceIndicator2 corresponding to the associated SRS resource set in rrc-ConfiguredUplinkGrant. When the higher layer parameter phaseTrackingRS in DMRS-UplinkConfig is configured in the UE, the PT-RS port index for each configured SRS resource by the higher layer parameter ptrs-PortIndex configured by SRS-Config is configured in the UE. If the PT-RS port indices associated with different SRIs are the same, the corresponding UL DM-RS port is associated with one UL PT-RS port (For non-codebook based UL transmission, the actual number of UL PT-RS port(s) to transmit is determined based on SRI(s) in DCI format 0_1, 0_2 or 0_3 or higher layer parametersri-ResourceIndicatorinrrc-ConfiguredUplinkGrant.When two SRS resource sets are configured insrs-ResourceSetToAddModListorsrs-ResourceSetToAddModListDCI-0-2with higher layer parameterusageinSRS-ResourceSetset to 'noncodebook', the actual number of UL PT-RS port(s) to transmit corresponding to each SRS resource set is determined based on SRI(s) corresponding to the associated SRS resource set or higher layer parametersri-ResourceIndicator or sri-ResourceIndicator2corresponding to the associated SRS resource set inrrc-ConfiguredUplinkGrant. A UE is configured with the PT-RS port index for each configured SRS resource by the higher layer parameterptrs-PortIndexconfigured bySRS-Configif the UE is configured with the higher layer parameterphaseTrackingRS in DMRS-UplinkConfig. If the PT-RS port index associated with different SRIs are the same, the corresponding UL DM-RS ports are associated to the one UL PT-RS port).

[0171] When the higher layer parameter multipanelScheme is set to 'sdmscheme' and two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with higher layer parameter usage in SRS-ResourceSet to 'codebook' / 'nonCodebook' and higher layer parameter maxNrofPortsforSDMin in PTRS-UplinkConfig to n2, the actual number of UL PT-RS ports to transmit corresponding to the SRS resource set is 2. the actual number of UL PT-RS port(s) to transmit corresponding to SRS resource sets is2).

[0172] When the higher layer parameter multipanelScheme is set to 'SFNscheme' and two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with higher layer parameter usage in SRS-ResourceSet is set to 'codebook' / 'nonCodebook' and the higher layer parameter maxNrofPorts in PTRS-UplinkConfig is set to n2, the actual number of UL PT-RS ports to transmit corresponding to each SRS resource set is determined by the 1st TPMI codepoint field for 'codebook' or the 1st SRI(s) codepoint field for 'nonCodebook'. 'codebook' / 'nonCodebook' and the higher layer parametermaxNrofPortsinPTRS-UplinkConfigis set ton2, the actual number of UL PT-RS port(s) to transmit corresponding to each SRS resource set is determined based on 1st TPMI codepoint field for 'codebook' or 1 st SRI(s) codepoint field for 'nonCodebook').

[0173] For partial-coherent and non-coherent codebook-based UL transmission, the actual number of UL PT-RS port(s) is determined based on TPMI(s) and / or number of layers which are indicated by 'Precoding information and number of layers' field(s) in DCI format 0_1, 0_2 or 0_3 or configured by higher layer parameterprecodingAndNumberOfLayers.

[0174] - If the UE is configured with the higher layer parameter maxNrofPortsinPTRS-UplinkConfigset to 'n2', the actual UL PT-RS port(s) and the associated transmission layer(s) are derived from indicated TPMI(s) as:.

[0175] - PUSCH antenna ports 1000 and 1002 in indicated TPMI(s) share PT-RS port 0, and PUSCH antenna ports 1001 and 1003 in indicated TPMI(s) share PT-RS port 1.

[0176] - UL PT-RS port 0 is associated with UL layer 'x' among the layers transmitted to PUSCH antenna port 1000 and PUSCH antenna port 1002 in the indicated TPMI(s), and UL PT-RS port 1 is associated with UL layer 'y' among the layers transmitted to PUSCH antenna port 1001 and PUSCH antenna port 1003 in the indicated TPMI(s). where 'x' and / or 'y' are given by DCI parameter 'PTRS-DMRS association' as shown in DCI format 0_1, 0_2 and 0_3 described in Clause 7.3.1 of [5, TS38.212] (UL PT-RS port 0 is associated with the UL layer 'x' of layers which are transmitted with PUSCH antenna port 1000 and PUSCH antenna port 1002 in indicated TPMI(s), and UL PT-RS port 1 is associated with the UL layer 'y' of layers which are transmitted with PUSCH antenna port 1001 and PUSCH antenna port 1003 in indicated TPMI(s), where 'x' and / or 'y' are given by DCI parameter 'PTRS-DMRS association' as shown in DCI format 0_1, 0_2 and 0_3 described in Clause 7.3.1 of [5, TS38.212].).

[0177] If a UE is scheduled with two codewords,

[0178] - If the upper layer parameter maxNrofPorts of PTRS-UplinkConfig in the UE is set to 'n1', the PT-RS port is associated with one of the DM-RS ports indicated by the DCI field PTRS-DMRS Association for the codeword with the higher MCS. If the MCS indices of the two codewords are the same, the PT-RS antenna port is associated with codeword 0. When a codeword is scheduled to transmit PUSCH for retransmission, the MCS for determining PT-RS association to the codeword is obtained from the DCI for the same transport block in the initial transmission (- if the UE is configured with the higher layer parameter maxNrofPortsinPTRS-UplinkConfigset to 'n1', the PT-RS port is associated with the one of DM-RS ports indicated by the DCI field PTRS-DMRS associationfor the codeword with the higher MCS. If the MCS indices of the two codewords are the same, the PT-RS antenna port is associated with codeword 0. When a codeword is scheduled to transmit PUSCH for retransmission, the MCS for determining PT-RS association to the codeword is obtained from the DCI for the same transport block in the initial transmission).

[0179] - When the upper layer parameter maxNrofPorts of PTRS-UplinkConfig in the UE is set to 'n2', each PT-RS port is associated with one of the DM-RS ports indicated by the DCI field PTRS-DMRS Association. PUSCH antenna ports 1000, 1001, 1004 and 1005 share PT-RS port 0, and PUSCH antenna ports 1002, 1003, 1006 and 1007 share PT-RS port 1 (- if the UE is configured with the higher layer parameter maxNrofPortsinPTRS-UplinkConfigset to 'n2', each PT-RS port is associated with the one of DM-RS ports indicated by DCI field PTRS-DMRS association. PUSCH antenna ports 1000, 1001, 1004 and 1005 share PT-RS port 0, and PUSCH antenna ports 1002, 1003, 1006 and 1007 share PT-RS port 1).

[0180] The frequency density and time density of PTRS are set / determined based on higher layer parameters according to the variation of bandwidth and MCS (Modulation and Coding Scheme). However, if the timeDensity parameter is not set, L PT-RS Assuming = 1, if the frequencyDensity parameter is not set, K PT-RS = 2. And the timeDensity parameter and frequencyDensity parameter are set to threshold ptrs-MCSi, i=1,2,3 and N as shown in Table 3 and Table 4 below. RB,i , i=0,1.

[0181] The values ​​of the timeDensity parameter and frequencyDensity parameter are set based on the uplink configuration. Specifically, the timeDensity parameter and frequencyDensity parameter are set by the higher layer parameter PTRS-UplinkConfig. Here, L PT-RS and K PT-RS If one or both of them are set to "PT-RS is not present", the terminal is considered to have no PTRS present.

[0182] Here, PUSCH with 2 symbols or less is scheduled to be transmitted, and L PT-RS = If set to 2 or 4, the terminal does not transmit PTRS. And it is scheduled to transmit PUSCH with 4 symbols or less, and L PT-RS If = is set to 4, the terminal does not transmit PTRS. L PT-RS = 2 or 4 and if a PUSCH that does not fall under the above cases is scheduled, PTRS is L starting from the symbol immediately following DMRS. PT-RS It is transmitted for each symbol set to . If additional DMRS is transmitted in the middle, PTRS is transmitted again from the next symbol position of the additional symbol. PT-RS It is transmitted for each symbol set to .

[0183] Table 3 below shows the time density of PT-RS as a function of scheduled MCS.

[0184]

[0185] Table 4 below shows the frequency density of PT-RS as a function of scheduled bandwidth.

[0186]

[0187] The RE position of the PTRS within the PRB (e.g., frequency position of the RE to which the PTRS is mapped, subcarrier index) is determined according to the position of the associated DMRS port. For example, the RE position of the PTRS is determined to be the same as one of the RE positions of the associated DMRS port. A DMRS port is transmitted on multiple REs within a PRB, but a PTRS port is transmitted on only one RE within a PRB. According to the maxNrofPortsparameter indicated in PTRS-UplinkConfig, the position (subcarrier index) of one of the REs of the DMRS port associated with each PTRS port is offset ( according to Table 5 below). ) is applied. As described above, the frequency position (e.g., subcarrier index) of the RE for PTRS mapping is determined based on the RE position (subcarrier index) of the associated DMRS port and the offset. At this time, if the resourceElementOffset parameter in PTRS-UplinkConfig is not set, the column corresponding to 'offset00' in Table 5 is used as the offset. Hereinafter, PTRS mapping is described by DMRS configuration type with reference to FIG. 2.

[0188] Figure 2 is a diagram showing the mapping of PTRS ports by DMRS type according to the existing method.

[0189] Specifically, Fig. 2 shows the mapping of two PTRS ports according to DMRS type 1 / 2 (DMRS configuration type 1 / 2). Fig. 2 (a) shows the mapping of two PTRS ports based on DMRS type 1 (DMRS configuration type 1), and Fig. 2 (b) shows the mapping of two PTRS ports based on DMRS type 2 (DMRS configuration type 2).

[0190] Two PTRS ports (PTRS 0, PTRS 1) can be associated with DMRS ports belonging to different DMRS CDM groups (CDM 1, CDM 2). Referring to (a) of Fig. 2, each PTRS port (PTRS 0 or PTRS 1) can be mapped based on the location (subcarrier index 0 or 1) of the RE to which the DMRS port belonging to the different DMRS CDM group (CDM 1 or CDM 2) is mapped. Referring to (b) of Fig. 2, each PTRS port (PTRS 0 or PTRS 1) can be mapped based on the location (subcarrier index 0 or 2) of the RE to which the DMRS port belonging to the different DMRS CDM group (CDM 1 or CDM 2) is mapped.

[0191] For 1 codeword (CW) DMRS type 1 of CB PUSCH case, port 1000 of DMRS CDM group 1 corresponding to the layer using PUSCH antenna ports 1000 and 1002 shares PTRS port 0. Port 1001 of DMRS CDM group 2 corresponding to the layer using PUSCH antenna ports 1001 and 1003 shares PTRS port 1.

[0192] For 1 CW DMRS type 2 of CB PUSCH case, ports of DMRS CDM group 1 corresponding to layers using PUSCH antenna ports 1000 and 1001 share PTRS port 0, and ports of DMRS CDM group 2 corresponding to layers using PUSCH antenna ports 1002 and 1003 share PTRS port 1.

[0193]

[0194] In this specification, RE (Resource Element) location can be interpreted / replaced with frequency location, subcarrier, or subcarrier index, and RB (Resource Block) can be interpreted / replaced with PRB (Physical Resource Block).

[0195] Method 1

[0196] Below, we will look at how to determine / set the 3 port PTRS RE position.

[0197] When transmitting 3 layers and 3 port PTRS, each DMRS port is mapped / associated with each PTRS port. At this time, the PTRS RE location (e.g., RE frequency location, subcarrier index) is determined based on the RE location (e.g., RE frequency location, subcarrier index) of the associated DMRS port.

[0198] For DMRS type 2, three DMRS CDM groups are defined. Once three PTRS ports (e.g., PTRS ports 0-2) are configured, PTRS can be mapped to each DMRS port RE location as before. In this case, there is no problem of REs associated with different PTRS ports overlapping in the frequency domain.

[0199] For DMRS type 1, two CDM groups are defined. In this case, simply extending the existing PTRS mapping method allows two PTRS ports to be mapped to the same RE. Specifically, the frequency location (subcarrier index) of the RE associated with one PTRS port can be identical to the frequency location (subcarrier index) of the RE associated with another PTRS port. The issue of overlapping RE locations is described in more detail below.

[0200] Among three DMRS ports, two DMRS ports within the same CDM group are multiplexed based on a code (e.g., an orthogonal cover code), and thus the two DMRS ports can be mapped to the same RE location. For example, among three PTRS ports, two PTRS ports associated with the two DMRS ports within the same CDM group can be mapped to the same RE location (subcarrier index). For example, according to the existing method, each of the two PTRS ports is defined to be associated with the DMRS port with the lowest index (lowest indexed DM-RS port) among the DMRS ports of each of the two CDM groups. Among three PTRS ports, two PTRS ports associated with the same CDM group can be associated with the DMRS port with the lowest index (lowest indexed DMRS port) among the DMRS ports within the corresponding CDM group. In this case, the RE locations (subcarrier indexes) associated with each of the two PTRS ports are determined to have the same value. Specifically, the RE position (subcarrier index) is i) the RE position (subcarrier index) relative to the lowest indexed DMRS port and ii) the offset (e.g., in Table 5) relative to the lowest indexed DMRS port (e.g., DM-RS antenna port 0). ) is determined based on.

[0201] As above, in case of DMRS type 1, 1 st or 2 nd 3 in the same DMRS CDM group as the PTRS port rd When PTRS ports are configured simultaneously, REs may overlap.

[0202] To solve the problem of RE overlapping as described above, the following embodiments may be considered.

[0203] Two of the three PTRS ports (e.g. 1 st PTRS port, 2 nd PTRS port) is set to each CDM group as before. For example, 1 st PTRS port is 1 within the 1st CDM group st It is mapped based on the RE position (e.g. subcarrier index 0) of the DMRS port associated with the PTRS port. 2 nd PTRS port is 2 within the 2nd CDM group nd It is mapped based on the RE position of the DMRS port associated with the PTRS port (e.g. subcarrier index 1). The last PTRS port (e.g. 3 rd PTRS port) is mapped to the next RE location of the associated DMRS port. For example, 3 rd PTRS port is 3 within the 1st CDM group (or 2nd CDM group). rd It can be mapped based on the next RE position (e.g., subcarrier index 2 or 3) of the RE position (e.g., subcarrier index 0 or 1) of the DMRS port associated with the PTRS port. This embodiment is described with reference to FIG. 3.

[0204] FIG. 3 is a diagram illustrating the mapping of PTRS ports according to an embodiment of the present specification.

[0205] Referring to FIG. 3, PTRS port 0 & PTRS port 1 can be mapped based on the subcarrier index of the RE associated with the DMRS port in each CDM group according to the existing standard. Specifically, PTRS port 0 is mapped to REs based on the first subcarrier (e.g., subcarrier index 0), and PTRS port 1 is mapped to REs based on the second subcarrier (e.g., subcarrier index 1).

[0206] Referring to (a) and (b) of FIG. 3, the third PTRS port may be associated with a DMRS port within the first CDM group (CDM 1) or the second CDM group (CDM 2). The RE location to which the third PTRS port (e.g., PTRS port 2) is mapped may be determined so as not to overlap with the RE location to which another PTRS port (e.g., PTRS port 0 or PTRS port 1) associated with the same CDM group (e.g., CDM 1 or CDM 2) is mapped.

[0207] Referring to (a) of FIG. 3, the third PTRS port (e.g., PTRS port 2) may be mapped to a different RE location (e.g., subcarrier index 2, 4, 6, 8, or 10) than the RE location (e.g., subcarrier index 0) to which another PTRS port (e.g., PTRS port 0) is mapped based on the CDM group (CDM 1). In other words, among the RE locations (e.g., subcarrier index 0, 2, 4, 6, 8, or 10) based on the same CDM group (CDM 1), the third PTRS port (e.g., PTRS port 2) may be mapped to a second RE location (e.g., subcarrier index 2, 4, 6, 8, or 10) that is different from the first RE location (e.g., subcarrier index 0) to which another PTRS port (e.g., PTRS port 0) is mapped.

[0208] Referring to (b) of FIG. 3, the third PTRS port (e.g., PTRS port 2) may be mapped to a different RE location (e.g., subcarrier index 3, 5, 7, 9, or 11) than the RE location (e.g., subcarrier index 1) to which another PTRS port (e.g., PTRS port 1) is mapped based on the CDM group (CDM 2). In other words, among the RE locations (e.g., subcarrier index 1, 3, 5, 7, 9, or 11) based on the same CDM group (CDM 2), the third PTRS port (e.g., PTRS port 2) may be mapped to a second RE location (e.g., subcarrier index 3, 5, 7, 9, or 11) that is different from the first RE location (e.g., subcarrier index 1) to which another PTRS port (e.g., PTRS port 1) is mapped.

[0209] For example, the RE location (subcarrier index) associated with the third PTRS port can be determined based on an offset set based on a higher layer parameter (e.g., Table 5). As a specific example, the higher layer parameter resourceElementOffset in PTRS-UplinkConfig can be set to one of {offset01, offset10, offset11}. In this case, offset( ) is determined based on the above resourceElementOffset (e.g. offset01). Or, if the upper layer parameter resourceElementOffset in PTRS-UplinkConfig is not set, offset( ) is determined based on offset00.

[0210] Here, we will explain with an example where the upper layer parameter resourceElementOffset is set to offset01. Among the values ​​according to offset01 for another PTRS port (e.g. PTRS port 0) associated with the same CDM group, 2 is the first offset value ( ) can be applied. A second offset value different from the first offset value can be applied to the third PTRS port.

[0211] For example, the second offset value may be defined / determined as a different value from the first offset value.

[0212] For example, the second offset value may be determined based on a value different from offset01 (e.g., offset00, offset10, or offset11).

[0213] For example, the second offset value may be determined based on a table other than Table 5. 1 st &2nd Offst( related to PTRS port ) is determined based on offset01 and Table 5, 3 rd Offst( related to PTRS port ) can be determined based on offset01 and other tables in Table 5.

[0214] For example, 3 rd Information about offsets associated with PTRS ports (e.g. additional PTRS RE offset value for 3) rd The PT-RS port) can be set by the base station to the terminal. As a specific example, the upper layer parameter resourceElementOffset2 can be set. The upper layer parameter resourceElementOffset2 can be set to a value (e.g., offset11) different from the upper layer parameter resourceElementOffset (e.g., offset01). As a specific example, 3 rd Information indicating the offset (e.g. 0 to 11) for the PTRS port can be set.

[0215] Method 2-1

[0216] Below, we will look at how to determine / set the 3 port PTRS RB position.

[0217] According to the existing standard, all PTRS ports are located within the same RB. Specifically, all PTRS ports are mapped to REs within the same RB. The RB offset related to RB location can be set based on RRC signaling, as shown in Figure 4.

[0218] Figure 4 illustrates an RB location to which a PTRS port is mapped according to the conventional method.

[0219] Referring to Figure 4, the above-described Frequency density( ) based on which all PTRS ports are mapped together to the same RB.

[0220] In one embodiment, three PTRS ports can be mapped to RE(s) within an RB determined in the same manner as before and transmitted. In this case, Method 1 can be utilized to resolve the problem of overlapping RE locations.

[0221] In one embodiment, three PTRS ports can be mapped to RE(s) within different RBs and transmitted. For example, 3 rd RB position of PTRS port is 1 st & 2 nd The RB positions of PTRS ports can be determined differently. According to this embodiment, the following effects are achieved: Potential RE position collision problems and / or problems in which PTRS REs are too concentrated in a specific PRB, resulting in irregular rate-matching REs, can be prevented. This will be described below with reference to FIG. 5.

[0222] FIG. 5 is an example of an RB location for a PTRS port according to an embodiment of the present specification.

[0223] If =2, 1 st & 2 nd PTRS port (PTRS port #0, #1) is (2) is set / mapped to the first RB (e.g. RB#0, RB#2, RB#4, RB#6) determined based on, and 3 rd The PTRS port (PTRS port #2) can be set / mapped to and transmitted to the second RB (e.g., RB#1, RB#3, RB#5, RB#7) located next to the first RB.

[0224] If =4, 1 st & 2 nd PTRS port (PTRS port #0, #1) is (4) is set / mapped to the first RB (e.g. RB#0, RB#4, RB#8, RB#12) determined based on, and 3 rd The PTRS port (PTRS port #2) can be configured / mapped to the second RB (e.g., RB#1, RB#5, RB#9, RB#13) located after the first RB and transmitted. In this case, there is an advantage of distributing rate-matching.

[0225] Method 2-2

[0226] Below we will look at how to determine / set the 3 port PTRS RB position.

[0227] A method of setting the RB position / offset mapped to each PTRS port may be considered.

[0228] For example, 1 st PTRS port is a specific RB (as before) ) can be set / mapped based on the decision. 2 nd PTRS port is the above specific RB(1 st Next RB(2) of RB nd RB) can be set / mapped based on 3 rd PTRS port is 2 above nd It can be set / mapped based on the Next RB of the RB. This can resolve the problem of overlapping RE locations (subcarriers). This is explained below with reference to Figure 6.

[0229] FIG. 6 is another example of RB locations for a PTRS port according to an embodiment of the present specification.

[0230] Specifically, Fig. 6 =4 shows the RB location for each PTRS port.

[0231] Referring to Fig. 6, 1 st PTRS port (PTRS port #0) is It is set / mapped based on the first RB (e.g. RB#0, RB#4, RB#8, RB#12) determined based on . 2 nd PTRS port (PTRS port #1) can be mapped / configured based on the second RB (e.g., RB#1, RB#5, RB#9, RB#13) located after the first RB. 3 rd The PTRS port (PTRS port #2) can be mapped / configured based on the third RB (e.g., RB#2, RB#6, RB#10, RB#14) located after the second RB. This embodiment has the advantage of distributing rate-matching.

[0232] Method 3

[0233] Below, we will look at a method for setting up 2 port PTRS for 3Tx Non coherent codebook.

[0234] As with the existing 4Tx, phase noise estimation can be performed with only 2 PTRS ports in 3Tx Non-coherent codebook uplink transmission. In 3Tx Non-coherency transmission, the number of PTRS ports can be set to 2. In this case, PTRS-DMRS association can be indicated based on a 2-bit field. The 2-bit field can be interpreted based on a previously defined table. Specifically, the MSB of the 2-bit field indicates one of the 1st to 2nd DMRS ports that share PTRS port 0. The LSB of the 2-bit field indicates one of the 1st to 2nd DMRS ports that share PTRS port 1.

[0235] Regarding PTRS-DMRS association, a method to reduce DCI overhead (the number of bits in the DCI field for PTRS-DMRS association) may be considered. For example, in 3Tx Non-coherent codebook uplink transmission, PTRS port 0 is associated with the 1st DMRS port, and PTRS port 1 is associated with the 2nd DMRS port. nd A rule can be defined to associate with a DMRS port. In this case, no separate instruction / signaling is required for PTRS-DMRS association. Therefore, the number of bits in the DCI field for PTRS-DMRS association can be reduced from 2 bits to 0 bits.

[0236] By defining PTRS port 0 as always associated with the 1st DMRS port and PTRS port 1 as always associated with the 2nd DMRS port, two PTRS ports can be configured in one DMRS CDM group, or two PTRS ports can be configured in two DMRS CDM groups. This allows PTRS ports to be associated with DMRS ports with high RSRP, which can efficiently secure phase noise estimation and DMRS performance.

[0237] The above suggestions can be finally applied through a combination / combination.

[0238] In terms of implementation, the operations of the base station / terminal according to the embodiments described above (e.g., operations based on at least one of Method 1, Method 2-1, Method 2-2, and Method 3) can be processed by the device (e.g., 100, 200) of FIG. 9 described below.

[0239] In addition, the operations of the base station / terminal according to the above-described embodiment (e.g., operations based on at least one of method 1, method 2-1, method 2-2, and method 3) may be stored in a memory (e.g., 140, 240 of FIG. 9) in the form of commands / programs (e.g., instructions, executable codes) for driving at least one processor (e.g., 110, 210 of FIG. 9).

[0240] The embodiments described below are specifically described with reference to FIGS. 7 and 8 in terms of the operation of the terminal and base station. The methods described below are distinguished for convenience of explanation, and it is understood that some components of one method may be substituted for or combined with some components of another method.

[0241] FIG. 7 is a flowchart illustrating a method according to one embodiment of the present specification.

[0242] Referring to FIG. 7, a method according to one embodiment of the present specification includes an uplink configuration reception step (S710), a DCI reception step (S720), and a PTRS transmission step (S730).

[0243] In S710, the terminal receives uplink configuration related to a phase tracking reference signal (PTRS) from the base station. For example, the uplink configuration may be based on a higher layer parameter PTRS-UplinkConfig.

[0244] For example, the uplink configuration may include at least one of i) information related to frequency density (e.g., upper layer parameter frequencyDensity, see Table 4), ii) information related to time density (e.g., upper layer parameter timeDensity, see Table 3), iii) information related to resource element offset (e.g., upper layer parameter resourceElementOffset), and / or iv) information related to the maximum number of PTRS ports (e.g., upper layer parameter maxNrofPorts indicating the maximum number of PTRS ports).

[0245] In S720, the terminal receives downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) from the base station.

[0246] For example, the DCI may be based on DCI format 0 (e.g., DCI format 0_0, DCI format 0_1, DCI format 0_2, or DCI format 0_3).

[0247] For example, the DCI may include a PTRS-DMRS association field. Based on the PTRS-DMRS association field, an association between PTRS port(s) and DMRS port(s) may be indicated.

[0248] In S730, the terminal transmits the PTRS to the base station based on the symbols allocated to the PUSCH.

[0249] For example, the PTRS is transmitted only in resource blocks used for the PUSCH. Specifically, the PTRS is mapped to resource elements within symbols allocated for the PUSCH.

[0250] More specifically, the PTRS may be mapped to resource elements (REs) within the symbols based on i) two Code Division Multiplexing (CDM) groups associated with configuration type 1 (e.g., DMRS configuration type 1) or ii) three CDM groups associated with configuration type 2 (e.g., DMRS configuration type 2). The resource elements may be associated with three PTRS ports.

[0251] According to the existing method, when three PTRS ports are configured and the PTRSs are mapped based on Configuration Type 1, resource elements associated with two PTRS ports based on the same CDM group may overlap in the frequency domain. In other words, each resource element associated with two PTRS ports based on the same CDM group may be based on the same subcarrier index. Embodiments for resolving this problem are described in detail below.

[0252] In one embodiment, resource elements associated with two PTRS ports associated with a demodulation reference signal (DMRS) port within the same CDM group among the resource elements may be based on i) different resource element offsets and / or ii) different resource blocks. The present embodiment may be based on at least one of Method 1, Method 2-1, and / or Method 2-2.

[0253] In one embodiment, the different resource element offsets may include i) a first resource element offset and ii) a second resource element offset. The present embodiment may be based on Method 1.

[0254] For example, the first resource element offset may be a value determined based on a first offset among the offsets defined for the setting type 1 (e.g., offset00, offset01, offset10, offset11) (see Table 5). The first offset may be i) an offset set based on the setting information (e.g., offset01, offset10, or offset11) or ii) a first offset among the offsets (e.g., offset00).

[0255] As a specific example, the upper layer parameter resourceElementOffset may be set based on the above configuration information. The upper layer parameter resourceElementOffset may be set to offset01, offset10, or offset11. The first offset may be offset01, offset10, or offset11 based on the upper layer parameter resourceElementOffset.

[0256] As a specific example, the upper layer parameter resourceElementOffset may not be set based on the above configuration information. In this case, the first offset may be the first offset (e.g., offset00) among the offsets (e.g., offset00, offset01, offset10, offset11).

[0257] For example, the second resource element offset may be a value determined based on a second offset. The second offset may be one of the remaining offsets (e.g., offset00, offset10, offset11) excluding the first offset (e.g., offset01) among the offsets. As a specific example, the second offset may be a next offset (e.g., offset10) of the first offset (e.g., offset01) among the offsets. As a specific example, the second offset may be a previous offset (e.g., offset00) of the first offset (e.g., offset01) among the offsets. As a specific example, based on the first offset being an odd-numbered offset (e.g., offset00) among the offsets, the second offset may be a next odd-numbered offset (e.g., offset10). As a specific example, based on the first offset being an even-numbered offset (e.g., offset01) among the offsets, the second offset may be a next even-numbered offset (e.g., offset11).

[0258] In one embodiment, the different resource blocks may include i) a first resource block and ii) a second resource block. The first resource block may be determined based on a frequency density associated with the PTRS. The second resource block may be a next resource block of the first resource block. The present embodiment may be based on Method 2-1. FIG. 5 Referring to the case of =2, the first resource block has a frequency density (frequency density, ) may include RB#0, RB#2, RB#4, and RB#6 determined based on the first resource block. The second resource block may include RB#1, RB#3, RB#5, and RB#7, which are next resource blocks of the first resource block.

[0259] In one embodiment, the different resource blocks may include resource blocks associated with each of the three PTRS ports. This embodiment may be based on Method 2-2.

[0260] For example, the different resource blocks may include i) a first resource block associated with a first PTRS port, ii) a second resource block associated with a second PTRS port, and iii) a third resource block associated with a third PTRS port.

[0261] For example, the first resource block may be determined based on a frequency density associated with the PTRS. The second resource block may be a next resource block of the first resource block. The third resource block may be a next resource block of the second resource block. Referring to FIG. 6, the first resource block may be determined based on a frequency density (FDD). ) may include RB#0, RB#4, RB#8, RB#12 determined based on the first resource block. The second resource block may include RB#1, RB#5, RB#9, RB#13, which are next resource blocks of the first resource block. The third resource block may include RB#2, RB#6, RB#10, RB#14, which are next resource blocks of the second resource block.

[0262] In one embodiment, a DMRS port associated with each PTRS port may be defined. In this case, no separate signaling is required to indicate PTRS-DMRS association. Specifically, the number of bits of the PTRS-DMRS association field in the DCI may be 0. This embodiment may be based on Method 3. For example, a first PTRS port may be associated with a first DMRS port (e.g., the lowest indexed DMRS port in the first CDM group). A second PTRS port may be associated with a second DMRS port (e.g., the lowest indexed DMRS port in the second CDM group). A third PTRS port may be associated with either the first DMRS port or the second DMRS port.

[0263] In one embodiment, the PUSCH may be associated with a codebook based UL transmission based on three antenna ports.

[0264] The operations based on S710 to S730 described above can be implemented by the device of FIG. 9. For example, the terminal (200) can control one or more transceivers (230) and / or one or more memories (240) to perform the operations based on S710 to S730.

[0265] The embodiments described below are specifically described in terms of base station operation.

[0266] S810 to S830 described below correspond to S710 to S730 described in FIG. 7. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the base station operation described below may be replaced with the description / embodiment of FIG. 7 corresponding to the corresponding operation. For example, the description / embodiment of S710 to S730 of FIG. 7 may be additionally applied to the base station operation of S810 to S830 described below.

[0267] FIG. 8 is a flowchart illustrating a method according to another embodiment of the present specification.

[0268] Referring to FIG. 8, a method according to another embodiment of the present specification includes an uplink configuration transmission step (S810), a DCI transmission step (S820), and a PTRS reception step (S830).

[0269] In S810, the base station transmits uplink settings related to a phase tracking reference signal (PTRS) to the terminal.

[0270] In S820, the base station transmits downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) to the terminal.

[0271] In S820, the base station receives the PTRS based on the symbols allocated to the PUSCH from the terminal.

[0272] In one embodiment, the PTRS may be mapped to resource elements within the symbols based on two Code Division Multiplexing (CDM) groups associated with configuration type 1.

[0273] The above resource elements can be associated with three PTRS ports.

[0274] Among the above resource elements, the resource elements associated with two PTRS ports associated with a demodulation reference signal (DoModulation Reference Signal) port within the same CDM group may be based on i) different resource element offsets and / or ii) different resource blocks.

[0275] The operations based on S810 to S830 described above can be implemented by the device of FIG. 9. For example, the base station (100) can control one or more transceivers (130) and / or one or more memories (140) to perform the operations based on S810 to S830.

[0276] The operations / terms based on the embodiments described above have been described assuming a 5G system. However, this is for convenience of explanation and is not intended to limit the scope of application of the technical problems and problem-solving means to be solved by this specification to a specific system. That is, the technical problems / technical issues / problems mentioned in this specification may equally exist in other systems (e.g., 6G systems). It is self-evident that the embodiments of this specification can be expanded and applied to solve problems equally existing in the other systems. Therefore, for the expanded application of the embodiments of this specification to other systems, the terms defined / described based on the 5G system may be replaced / changed with terms defined in the other systems (or generalized terms not specific to one system). For example, PRACH, PUSCH, PUCCH, SRS, or PTRS (UL PTRS) may be replaced / changed with uplink signals (or uplink channels). For example, SSB, CSI-RS, PTRS (DL PTRS), PDSCH, and PDCCH can be replaced / changed into downlink signals (or downlink channels).

[0277] Hereinafter, a device to which an embodiment of the present specification can be applied (a device that implements a method / operation according to an embodiment of the present specification) is described with reference to FIG. 9.

[0278] FIG. 9 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0279] The first device (100) may include a processor (110), an antenna unit (120), a transceiver (130), and a memory (140).

[0280] The processor (110) performs baseband-related signal processing and may include a higher layer processing unit (111) and a physical layer processing unit (115). The higher layer processing unit (111) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (115) may process operations of a PHY layer. For example, when the first device (100) is a base station device in base station-terminal communication, the physical layer processing unit (115) may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, when the first device (100) is a first terminal device in terminal-to-terminal communication, the physical layer processing unit (115) may perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor (110) may also control the overall operation of the first device (100).

[0281] The antenna unit (120) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (130) may include an RF (Radio Frequency) transmitter and an RF receiver. The memory (140) may store information processed by the processor (110), and software, an operating system, applications, etc. related to the operation of the first device (100), and may also include components such as a buffer.

[0282] The processor (110) of the first device (100) may be configured to implement the operation of the base station in the base station-to-terminal communication (or the operation of the first terminal device in the terminal-to-terminal communication) in the embodiments described in the present disclosure.

[0283] The second device (200) may include a processor (210), an antenna unit (220), a transceiver (230), and a memory (240).

[0284] The processor (210) performs baseband-related signal processing and may include a higher layer processing unit (211) and a physical layer processing unit (215). The higher layer processing unit (211) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (215) may process operations of a PHY layer. For example, when the second device (200) is a terminal device in base station-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, when the second device (200) is a second terminal device in terminal-to-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor (210) may also control the overall operation of the second device (210).

[0285] The antenna unit (220) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (230) may include an RF transmitter and an RF receiver. The memory (240) may store information processed by the processor (210), software, an operating system, applications, etc. related to the operation of the second device (200), and may also include components such as a buffer.

[0286] The processor (210) of the second device (200) may be configured to implement operations of the terminal in base station-to-terminal communication (or operations of the second terminal device in terminal-to-terminal communication) in the embodiments described in the present disclosure.

[0287] In the operation of the first device (100) and the second device (200), the same explanations given for the base station and the terminal (or the first terminal and the second terminal in the terminal-to-terminal communication) in the examples of the present disclosure may be applied, and redundant explanations are omitted.

[0288] Here, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names.

[0289] Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names.

[0290] Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) that take low-power communication into account, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.

Claims

1. In the method, A step of receiving an uplink setting related to a phase tracking reference signal (PTRS) from a base station; A step of receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) from the base station; and A step of transmitting the PTRS based on symbols allocated to the PUSCH to the base station; The above PTRS is mapped to resource elements within the symbols based on two CDM (Code Division Multiplexing) groups associated with configuration type 1, The above resource elements are associated with three PTRS ports, A method characterized in that among the above resource elements, resource elements associated with two PTRS ports associated with a demodulation reference signal (DoModulation Reference Signal, DMRS) port within the same CDM group are based on i) different resource element offsets and / or ii) different resource blocks.

2. In paragraph 1, A method characterized in that the above different resource element offsets include i) a first resource element offset and ii) a second resource element offset.

3. In paragraph 2, The above first resource element offset is a value determined based on the first offset among the offsets defined for the above setting type 1, A method characterized in that the first offset is i) an offset set based on the setting information or ii) a first offset among the offsets.

4. In paragraph 3, The above second resource element offset is a value determined based on the second offset, A method characterized in that the second offset is one of the remaining offsets excluding the first offset among the offsets.

5. In paragraph 4, A method characterized in that the second offset is a next offset from the first offset among the offsets.

6. In paragraph 1, The above different resource blocks include i) a first resource block and ii) a second resource block, The first resource block is determined based on a frequency density associated with the PTRS, A method characterized in that the second resource block is a next resource block of the first resource block.

7. In paragraph 1, A method characterized in that the above different resource blocks include resource blocks associated with each of the three PTRS ports.

8. In paragraph 7, A method characterized in that the above different resource blocks include i) a first resource block associated with a first PTRS port, ii) a second resource block associated with a second PTRS port, and iii) a third resource block associated with a third PTRS port.

9. In paragraph 8, The first resource block is determined based on a frequency density associated with the PTRS, The second resource block is the next resource block of the first resource block, A method characterized in that the third resource block is a next resource block of the second resource block.

10. In paragraph 1, A DMRS port associated with each PTRS port is defined, A method characterized in that the number of bits of the PTRS-DMRS association field in the above DCI is 0.

11. In paragraph 1, A method characterized in that the above PUSCH is related to codebook based UL transmission based on three antenna ports.

12. At the terminal, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A terminal characterized in that the instructions, based on being executed by the one or more processors, cause the terminal to perform all steps of the method according to any one of claims 1 to 11.

13. In a device comprising one or more memories and one or more processors functionally connected to the one or more memories, A device characterized in that said one or more memories store instructions that cause said device to perform all steps of a method according to any one of claims 1 to 11, based on being executed by said one or more processors.

14. In a non-transitory computer-readable storage medium storing instructions, A non-transitory computer-readable storage medium characterized in that the instructions, based on being executed by one or more processors, cause a terminal to perform all steps of a method according to any one of claims 1 to 11.

15. In the method, A step of transmitting an uplink setting related to a phase tracking reference signal (PTRS) to a terminal; A step of transmitting downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) to the terminal; and A step of receiving the PTRS based on symbols allocated to the PUSCH from the terminal; including, The above PTRS is mapped to resource elements within the symbols based on two CDM (Code Division Multiplexing) groups associated with configuration type 1, The above resource elements are associated with three PTRS ports, A method characterized in that among the above resource elements, resource elements associated with two PTRS ports associated with a demodulation reference signal (DoModulation Reference Signal, DMRS) port within the same CDM group are based on i) different resource element offsets and / or ii) different resource blocks.

16. At the base station, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A base station characterized in that the instructions, based on being executed by the one or more processors, cause the base station to perform all steps of the method according to claim 15.

Images