PT-RS Resource Management

Product Version: NR22.2

ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P. R. China
Postcode:518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION

Copyright ©2020 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties.
Any reproduction or distribution of this document or any portion of this document, in any
form by any means, without the prior written consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by contractual confidentiality
obligations.

All company, brand and product names are trade or service marks, or registered trade or
service marks, of ZTE CORPORATION or of their respective owners.

This document is provided“as is”, and all express, implied, or statutory warranties,
representations or conditions are disclaimed, including without limitation any implied
warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE
CORPORATION and its licensors shall not be liable for damages resulting from the use of or
reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights
or applications covering the subject matter of this document. Except as expressly provided
in any written license between ZTE CORPORATION and its licensee, the user of this
document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product
without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire

related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Serial Number:2023-03-05
 PT-RS Resource Management

PT-RS Resource Management

1 About This Document

1.1 Personal Data Security Statement

Some of the features listed in this document need users’ personal data during provisioning, including the SUPI, IMSI, IMEI, MSISDN, and UEIP.
These features are used for the purpose of implementing the service procedures or location procedures specified by 3GPP, optimizing service
experience of users, and facilitating system maintenance. When activating these features, you shall comply with local laws and regulations on
personal data protection and privacy protection.For any inquiries on the legality of activating these features, please consult your legal
department.

1.2 Changes

This section describes the changes between different versions of the product, including two types of changes:
Technical changes: technical changes and parameter changes between different versions.
Description changes: description and structure changes between different versions, including content optimization and supplementation.

Change Type Change Date Description Parameter Change

Technical changes 2023-01-30 Compared with the previous NR22.1 version, there is no change. None

Description changes 2023-01-30 Compared with the previous NR22.1 version, there is no change. None

2 Document Description

2.1 Covered Features

The following table lists the features covered in this document.

Table 1 Covered Feature List

No. NR22.2 Feature ID NR22.2 Feature Name NR21.2Feature ID and Feature Name Scenario Refer to

1 ZNR-RB-0060 Schedule ZNR03-08-240 PTRS SA&NSA 4 PTRS

2.2 Correlation with Other Features

Table 2 Correlation with Other Features

Feature ID Feature Name Required Feature Mutually Exclusive Feature Impacted Feature

ZNR-RB-0060 Schedule None None None

2.3 Terms and Definitions

For the related terms and definitions, refer to the following table.

Table 3 Terms and Definitions

Term Full Name Definition

PTRS Phase Tracking Reference Signal A physical signal used for phase noise estimation and PDSCH demodulation.

2.4 Feature Difference Descriptions

2.4.1 Difference Between FR1 FDD and FR1 TDD

3 - 18
 PT-RS Resource Management

Table 4 Difference Between FR1 FDD and FR1 TDD

Feature Difference Description Refer to

PTRS Only FR2 supports. 4 PTRS

2.4.2 Difference Between NSA and SA Networks

Table 5 Difference Between NSA and SA Networks

Feature Difference Description Refer to

PTRS No difference between NSA and SA. 4 PTRS

2.4.3 Difference Between FR1 and FR2

Here in this document, FR1 refers to 410MHz~7125MHz, FR2 refers to 24250MHz~52600MHz. For detailed definition of FR1 and FR2, refer to 5.1
General in 3GPP TS 38.104 V15.5.0.

Table 6 Difference Between FR1 and FR2

Feature Difference Description Refer to

PTRS Only FR2 supports. 4 PTRS

3 Overview
Phase noise refers to the random change in the phase of system output signals caused by RF components under the action of various noises.
Phase noise may deteriorate the SNR or error vector amplitude of the receiving end, resulting in a large number of bit errors. This restricts the
use of high-order modulation, and seriously affects system capacity. Relatively speaking, phase noise has little impact on low frequency bands.
Under high frequency bands (millimeter wave), the impact of phase noise is greatly increased due to the large increase in the number of times
that the frequency is multiplied by the reference clock source and the process level and power consumption of components. To cope with the
phase noise in the high frequency band, in addition to increasing the subcarrier spacing and improving the component quality, the 5G new air
interface introduces uplink/downlink PTRS signal.

4 PTRS

4.1 Principle

4.1.1 DL PTRS

In the downlink transmission scheme of NR FR2, PTRS is a part of the data to be transmitted and an unique feature for FR2. PTRS uses the same
transmission coding scheme as the transmitted data, so it can also be used as a part of demodulation reference signal, which is commonly
used in high-order MCS(Modulation and Coding Scheme) transmission. PTRS is often used for:

■ Phase noise estimation

■ Channel estimation

■ Frequency and time bias estimation

PTRS uses QPSK independent from data modulation. In FR2, the 256QAM for PDSCH is disabled by default，PTRS reference signal would be
enabled when MCS is larger than 10. If the 256QAM for PDSCH is enabled, PTRS reference signal would be enabled when MCS is larger than 5.
PTRS is transmitted along with PDSCH. The port number of PTRS has no concern with that of PDSCH. PTRS appears in the port with smaller
port number.
The sequence of PTRS is the same as DMRS's, but the frequency and time domain density of PTRS is much smaller than DMRS(Demodulation
Reference Singal). In time domain, PTRS appears every 1,2,4 symbols, and in frequency domain, PTRS appears every 2,4 RBs.
The PTRS configuration notifies the UE via PTRS-DownLinkConfig. In Section 7.4.1.2 of the 5GNR protocol 38.211, PTRS can be configured with

4 - 18
 PT-RS Resource Management

different time and frequency domain densities to achieve the proportion of multiple reference signals to service channels and match the
transmission at various MCS levels.
DL-PTRS has the following description dimensions:

■ Time domain density(PTRSDl.timeDensity，PTRSDl.timeDensityFor256QAM): available chooses 1,2,4. It means a symbol with PTRS

appears every 1,2,4 symbols.

■ Frequency domain density(PTRSDl.frequencyDensity): available chooses 2,4. It means a RB(Resource Block) with PTRS appears every

2,4RBs.
■ Power boosting level: available chooses 0, 3, 4.7, 6, 7, 7.78dB. It means the transmitting RE(Resource Element) power of PTRS is larger

than PDSCH transmitting RE power. Only 0, 3dB is supported now. Referring to the table below.

Table 7 PTRS EPRE to PDSCH EPRE per layer per RE

epre-Ratio The number of PDSCH layers

1 2 3 4 5 6

0 0 3 4.77 6 7 7.78

1 0 0 0 0 0 0

2 reserved

3 reserved

The following figures illustrate the cases of PTRS time domain density is 1,2,4 respectively.

Figure 1 PTRS Time domain density =1

Figure 2 PTRS Time domain density =2

Figure 3 PTRS Time domain density =4

The following figure Figure 4 shows the cases of PTRS frequency domain density is 2, 4 and with the cases of DMRS port number is 1, 2.
Particularly, PTRS only appears on the lower port when DMRS is 2 ports, and the counterpart RE of the other port is supposed to transmit
nothing.

Figure 4 PTRS transmit with various frequency domain density and various DMRS port number

5 - 18
 PT-RS Resource Management

The k in formula is the ReOfst of PTRS which stands for the offset of PTRS RE referring to RE0 in a certain RB. k depends on DMRS port number
and PTRS frequency density. The relationship between DMRS port index to k is shown in the following table in protocol. See protocol section
7.4.1.2 of 38.211 for details.

Table 8 PTRS Re Offset Parameter Lookup

DM-RS DM-RS Configuration type 1 DM-RS Configuration type 2

antenna port
resourceElementOffset resourceElementOffset

00 01 10 11 00 01 10 11

1000 0 2 6 8 0 1 6 7

1001 2 4 8 10 1 6 7 0

1002 1 3 7 9 2 3 8 9

1003 3 5 9 11 3 8 9 2

1004 - - - - 4 5 10 11

1005 - - - - 5 10 11 4

The RbOfst is the RB offset number referring to RB0 in BWP of PTRS, the formula is shown below, see protocol section 7.4.1.2 of 38.211 for
more details.
Figure 5 shows the cases for frequency domain density is 2, 4, RbOfst is 1, 3.

Figure 5 PTRS RB offset

4.1.2 UL PTRS

From the perspective of timing interval, as shown in Figure 6, Figure 7, and Figure 8, respectively show three PTRS time domain densities 1, 2
and 4. From the perspective of frequency domain spacing, PTRSs in the uplink and downlink are exactly the same. Refer to Figure 4 in the
downlink section.

Figure 6 Uplink PTRS Time domain density =1

6 - 18
 PT-RS Resource Management

Figure 7 Uplink PTRS Time domain density =2

Figure 8 Uplink PTRS Time domain density =4

Thus, the distribution of physical resources of uplink PTRS is basically the same as that of downlink PTRS. The difference is that SC-FDMA
should be considered in uplink. When OFDM is used, the traversal condition is shown in [table Conditions of uplink CP-OFDM PTRS traversal].
When SC-FDMA is adopted, the traversal condition is shown in [table Conditions for UL SC-FDMA PTRS traversal].

Table 9 Conditions of uplink CP-OFDM PTRS traversal

PTRS TimeSpace PTRS FreqSpace PTRS ReOffset Port index PTRS PortNum PtrsLayerIndx

1/2/4 2/4 0~3 0~3 0~2 0/1（When portnum is 1 or 2）

Table 10 Conditions for UL SC-FDMA PTRS traversal

PTRS X PTRS K

2/4/8 2/4（When X is 8, it can only be 4.）

4.2 Network Analysis

Note:
The feature activation effect depends on the network environment. Therefore, this document only guides the feature provisioning. For network
gains pertinent contents, refer to ZTE for support.

4.2.1 Benefit Analysis

For higher-order MCS, the receiving end is more affected by frequency deviation. The receiving performance and downlink traffic of UE can be
improved if downlink PTRS is configured, and the eNodeB demodulation performance and uplink traffic can be improved if uplink PTRS is
configured.

4.2.2 Impact Analysis

PTRSs occupy the RE transmitted on service channels, and a small amount of resource overhead is introduced.

4.3 Application Scenarios

No special requirements.

4.4 Provisioning Guidance

7 - 18
 PT-RS Resource Management

4.4.1 PTRS Provisioning Guidance

4.4.1.1 Prerequisites

Table 11 Hardware Requirement

Device Description Remark

5GC/EPC 5GC None

BBU V9200 None

AAU/RRU/Qcell No spectial requirement on RRU None

Table 12 Other Requirement

Other Requirement Description

CN None

Carrier frequency bands, frequencies, and bandwidths None

UE None

Transmission bandwidth None

FTP server None

4.4.1.2 Restrictions

None.

4.4.1.3 Feature Activation

4.4.1.3.1 Feature Activation Process

Table 13 PTRS Physical Resource Configuration Steps And Parameters

No STEPS Related Parameters Process Verification

1 1、Configuring downlink PTRS parameters on the UME PTRSDl.frequencyDensity none

2 PTRSDl.timeDensity

3 PTRSDl.epreRatio

4 PTRSDl.reOffset

5 1、Configuring upink PTRS parameters on the UME PTRSUl.frequencyDensityCpofdm none

6 PTRSUl.timeDensityCpofdm

7 PTRSUl.maxNrofPorts

8 PTRSUl.reOffset

9 PTRSUl.ptrsPower

10 PTRSUl.sampleDensity

11 PTRSUl.timeDensityDft

4.4.1.3.2 Related Parameters and Figures

8 - 18
 PT-RS Resource Management

Path on the UME for setting PTRS physical resources:

/ManagedElement/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPDL/PDSCHConfig/PTRSDl
/ManagedElement/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUSCHConfig/PTRSUl

Table 14 PTRS Physical Resource Management Feature Activation

No. Paramete Parameter Configurat Parameter Path

r ID Name ion Examp
le

1 PTRSDl.fr PTRS 4;4 Managed

equency frequency- Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPDL/PDSCH
Density domain configuration/PTRSDl
density

9 - 18
 PT-RS Resource Management

2 PTRSDl.ti PTRS 11;11;11 Managed

meDensit time- Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPDL/PDSCH
y domain configuration/PTRSDl
density

10 - 18
 PT-RS Resource Management

3 PTRSDl.e PTRS 1 Managed

preRatio EPRE Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPDL/PDSCH
offset configuration/PTRSDl
relative to
PDSCH
EPRE

4 PTRSDl.r subcarrier offset00 Managed

eOffset offset Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPDL/PDSCH
configuration/PTRSDl

11 - 18
 PT-RS Resource Management

5 PTRSUl.fr PTRS 4;4 Managed

equency frequency Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/ConfiguredGrant
DensityC density for config parameter for VoNR/CgDMRSConfiguration/PTRSUl; Managed
pofdm
CP-OFDM Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUSCH channel
configuration/PTRSUl

12 - 18
 PT-RS Resource Management

6 PTRSUl.ti PTRS time 0;0;0 Managed

meDensit density for Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/ConfiguredGrant
yCpofdm CP-OFDM config parameter for VoNR/CgDMRSConfiguration/PTRSUl; Managed
Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUSCH channel
configuration/PTRSUl

13 - 18
 PT-RS Resource Management

7 PTRSUl. Maximum n1 Managed

maxNrof number of Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/ConfiguredGrant
Ports ports config parameter for VoNR/CgDMRSConfiguration/PTRSUl; Managed
Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUSCH channel
configuration/PTRSUl

8 PTRSUl.r Subcarrier offset00 Managed

eOffset offset Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/ConfiguredGrant
config parameter for VoNR/CgDMRSConfiguration/PTRSUl; Managed
Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUSCH channel
configuration/PTRSUl

14 - 18
 PT-RS Resource Management

9 PTRSUl.p UL PTRS p00 Managed

trsPower power Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/ConfiguredGrant
boost config parameter for VoNR/CgDMRSConfiguration/PTRSUl; Managed
Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUSCH channel
configuration/PTRSUl

15 - 18
 PT-RS Resource Management

10 PTRSUl.s Sample 1;1;1;1;276 Managed

ampleDe density Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/ConfiguredGrant
nsity config parameter for VoNR/CgDMRSConfiguration/PTRSUl; Managed
Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUSCH channel
configuration/PTRSUl

11 PTRSUl.ti Time d1 Managed

meDensit density of Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/ConfiguredGrant
yDft PTRS for config parameter for VoNR/CgDMRSConfiguration/PTRSUl; Managed
DFT Element/NRRadioInfrastructure/NRPhysicalCellDU/PhyResourceConfigforBWPUL/PUSCH channel
configuration/PTRSUl

The location of PTRS parameters on the UME is as follows:

Figure 9 PTRS Parameter Configuration 1

Figure 10 PTRS Parameter Configuration 2

16 - 18
 PT-RS Resource Management

4.4.1.4 Feature Deactivation

If the number of MCSs and RBs in current scheduling does not exceed the threshold, PTRS is not used.

4.4.1.5 Test Method

Table 15 PTRS Test Method

Test Item PTRS

Sub-item N/A

Prerequisites Refer to 4.4.1.3.2 Related Parameters and Figures.

Test Steps ① Verify that the test cell operates properly and the UE can access the cell successfully;
② Check the UE signaling, PTRS is not used.

Expected Result Refer to 4.4.1.6.1 PDSCH PTRS Provisioning Observation.

4.4.1.6 Provisioning Observation

4.4.1.6.1 PDSCH PTRS Provisioning Observation

The cell operates properly and the UE can access the network.
The PTRS configuration is delivered to the UE through the RRC reconfiguration message. The location of the Qualcomm terminal log is as
follows: QXDM > Filtered View > RRCConnectionReconfiguration, keyword: phaseTrackingRS setup

Figure 11 FR2 Downlink PTRS Provisioning Observation

4.4.1.6.2 PUSCH PTRS Provisioning Observation

The cell operates properly and the UE can access the network.

17 - 18
 PT-RS Resource Management

The PTRS configuration is delivered to the UE through the RRC reconfiguration message. The location of the Qualcomm terminal log is as
follows: QXDM > Filtered View > RRCConnectionReconfiguration, keyword: phaseTrackingRS setup

Figure 12 FR2 Uplink PTRS Provisioning Observation

5 Related Counters, KPIs, and Alarms

5.1 Related Counters

This feature has no related counter.

5.2 Related KPIs

This feature has no related KPI.

5.3 Related Alarms

This feature has no related alarm.

6 Abbreviations
For the acronyms, refer to the abbreviations.

7 References
1. 3GPP TS 38.211, “NR; Physical channels and modulation”
2. 3GPP TS 38.212, “NR; Multiplexing and channel coding”
3. 3GPP TS 38.213, “NR; Physical layer procedures for control”
4. 3GPP TS 38.331, “NR; Radio Resource Control (RRC); Protocol specification”
5. 3GPP TS 38.214, “NR; Physical layer procedures for data

18 - 18