Extended CP

Contents
4.1.4 Extended CP

eRAN
Extended CP Feature Parameter
Description
Issue 04
Date 2022-02-25
 HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2022. All rights reserved.

 No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and
recommendations in this document are provided "AS IS" without warranties, guarantees or representations of
any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website: https:/

Email: [email protected]

4.1.4 Contents
1 Change History
1.1 eRAN17.1 04 (2022-02-25)
1.2 eRAN17.1 03 (2021-06-26)
1.3 eRAN17.1 02 (2021-04-30)
1.4 eRAN17.1 01 (2021-03-05)
1.5 eRAN17.1 Draft A (2020-12-29)

2 About This Document

2.1 General Statements
2.2 Applicable RAT
2.3 Features in This Document

3 General Principles

4 Normal CP
4.1 Principles
4.2 Network Analysis
 4.2.1 Benefits
4.2.2 Impacts
4.3 Requirements
4.3.1 Licenses
4.3.2 Software
4.3.3 Hardware
4.3.4 Others
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation
4.4.1.2 Using MML Commands
4.4.1.3 Using the MAE-Deployment
4.4.2 Activation Verification
4.4.3 Network Monitoring

5 Extended CP
5.1 Principles
5.2 Network Analysis
5.2.1 Benefits
5.2.2 Impacts
5.3 Requirements
5.3.1 Licenses
5.3.2 Software
5.3.3 Hardware
5.3.4 Others
5.4 Operation and Maintenance
5.4.1 Data Configuration
5.4.1.1 Data Preparation
5.4.1.2 Using MML Commands
5.4.1.3 Using the MAE-Deployment (FDD)
5.4.1.4 Using the MAE-Deployment (TDD)
5.4.2 Activation Verification
5.4.3 Network Monitoring

6 Parameters

7 Counters

8 Glossary

9 Reference Documents
1 Change History

This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
• Technical changes
Changes in functions and their corresponding parameters
• Editorial changes
Improvements or revisions to the documentation
1.1 eRAN17.1 04 (2022-02-25)

This issue includes the following changes.

Technical Changes

None

Editorial Changes

Revised descriptions in this document.

1.2 eRAN17.1 03 (2021-06-26)

This issue includes the following changes.

Technical Changes

None

Editorial Changes

FDD: Renamed Static Shared Beam as Static Multiple Beam and Dynamic Dedicated Beam as
Dynamic Massive Beam. For details, see 5.3.2 Software.
1.3 eRAN17.1 02 (2021-04-30)

This issue includes the following changes.

Technical Changes

None

Editorial Changes
 Modified the impact relationship between normal CP/extended CP and Cells in a Multi-Carrier
Sector. For details, see 4.2.2 Impacts and 5.2.2 Impacts.
Added information about reference documents. For details, see 9 Reference Documents.
1.4 eRAN17.1 01 (2021-03-05)

This issue does not include any changes.

1.5 eRAN17.1 Draft A (2020-12-29)

This issue introduces the following changes to eRAN16.1 01 (2020-04-07).

Technical Changes

Change Description Parameter Change RAT Base Station Model

Added the mutually exclusive None FDD 3900 and 5900 series
relationship between base stations
extended CP and CRS
dynamic muting. For details,
see 5.3.2 Software.

Added the mutually exclusive None FDD 3900 and 5900 series
relationship between base stations
extended CP and RF channel
dynamic muting. For details,
see 5.3.2 Software.

Added the mutually exclusive None FDD 3900 and 5900 series
relationship between base stations
extended CP and dynamic
carrier shutdown. For details,
see 5.3.2 Software.

Added the mutually exclusive None FDD 3900 and 5900 series
relationship between base stations
extended CP and Dynamic
Dedicated Beam. For details,
see 5.3.2 Software.

Added the mutually exclusive None FDD 3900 and 5900 series
relationship between base stations
extended CP and Static
Shared Beam. For details,
see 5.3.2 Software.

Editorial Changes

None
2 About This Document

2.1 General Statements

Purpose

This document is intended to acquaint readers with:

• The technical principles of features and their related parameters
• The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
• Requirements of the operating environment that must be met before feature activation
• Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance

This document only provides guidance for feature activation. Feature deployment and feature gains
depend on the specifics of the network scenario where the feature is deployed. To achieve optimal
gains, contact Huawei professional service engineers.

Software Interfaces

Any parameters, alarms, counters, or managed objects (MOs) described in this document apply
only to the corresponding software release. For future software releases, refer to the
corresponding updated product documentation.
2.2 Applicable RAT

This document applies to FDD.

2.3 Features in This Document

This document describes the following FDD features.

Feature ID Feature Name Chapter/Section

LBFD-001004 CP length 4 Normal CP

LBFD-00100401 Normal CP 4 Normal CP

LOFD-001031 Extended CP 5 Extended CP

3 General Principles

Principles

A cyclic prefix (CP) is a copy of the end of an orthogonal frequency division multiplexing
(OFDM) symbol inserted at the beginning. Each CP serves as a guard interval between OFDM
symbols, as shown in Figure 3-1.
Figure 3-1 Structure of an OFDM symbol in the time domain

Radio signals are transmitted between an eNodeB and a UE through multiple propagation paths.
The maximum transmission delay difference between paths is the delay spread. In typical
eNodeB deployment scenarios (for example, urban areas), the delay spread is generally short.
However, in some areas with special channel environments (for example, valleys) or special
network topologies (for example, roads covered with several RRUs serving one cell), the delay
spread is long. In addition, the delay spread increases with the cell radius.
To mitigate intersymbol interference (ISI) and inter-carrier interference (ICI) caused by delay
spread in the OFDM system, the CP technique is introduced.
The symbol energy that can be captured by an OFDM receiver depends on the CP length:
• If the CP length is longer than the multipath delay spread of an OFDM symbol, the
OFDM receiver can capture all the energy of the symbol.
• If the CP length is shorter than the multipath delay spread of an OFDM symbol, the
OFDM receiver can capture only some energy of the symbol.
If the multipath components of an OFDM symbol whose multipath delay spread is longer than
the CP are incorrectly received as a subsequent OFDM symbol, interference is generated to the
actual subsequent OFDM symbol. This causes ISI. If the interfered OFDM symbol then
mistakenly captures some multipath components of adjacent symbols, the orthogonality between
subcarriers is lost after fast Fourier transformation (FFT). This causes ICI. To avoid ISI and ICI,
a sufficiently long CP is required. However, an unnecessarily long CP must be avoided because
it causes high system overhead and a loss of spectral efficiency.
To balance system performance, system overhead, and data transmission capability, normal CP
and extended CP were defined in section 5.6 "SC-FDMA baseband signal generation" and
section 6.12 "OFDM baseband signal generation" of 3GPP TS 36.211 V8.9.0 for non-RACH
channels to meet different multipath delay spread requirements.
Related Parameters

Normal CP and extended CP are specified by Cell.UlCyclicPrefix and Cell.DlCyclicPrefix.

4 Normal CP

4.1 Principles

Normal CP is a basic feature and is enabled by default. It applies to scenarios where the delay
spread is short.
Figure 4-1shows the structure of a timeslot in the normal CP case. The timeslot consists of seven
downlink OFDM symbols or uplink single-carrier frequency division multiple access (SC-
FDMA) symbols. The CP length of symbol 0 is approximately 5.2 µs, and the CP lengths of the
other six symbols are approximately 4.7 µs.
Figure 4-1 Structure of a timeslot in the normal CP case (with a subcarrier spacing of 15 kHz)

The system overhead for the normal CP case shown in Figure 4-1 is calculated using the following
formula:

4.2 Network Analysis

4.2.1 Benefits

The CP technique mitigates inter-symbol interference (ISI) and inter-carrier interference (ICI)
caused by multipath delay, ensuring network coverage in E-UTRAN cells.
4.2.2 Impacts

Network Impacts

None

Function Impacts

RAT Function Name Function Reference Description

Switch

FDD None None None None

4.3 Requirements

4.3.1 Licenses

There are no license requirements for basic functions.

4.3.2 Software

Before activating this function, ensure that its prerequisite functions have been activated and
mutually exclusive functions have been deactivated. For detailed operations, see the relevant
feature documents.

Prerequisite Functions

None

Mutually Exclusive Functions

None
4.3.3 Hardware

Base Station Models

No requirements

Boards

No requirements

RF Modules

No requirements

Cells

None
4.3.4 Others

None
4.4 Operation and Maintenance

4.4.1 Data Configuration

4.4.1.1 Data Preparation

describes the parameters used for function activation. This section does not describe
Table 4-1
parameters related to cell establishment.
At the moment when the CP modification takes effect in an activated cell, services carried by
UEs are interrupted in the cell. The duration for the UEs to reacquire synchronization with the
cell depends on the synchronization performance of the UEs.

Table 4-1 Parameters used for activation

Parameter Name Parameter ID Setting Notes

Uplink cyclic Cell.UlCyclicPrefix • Set the parameters to NORMAL_CP when

prefix length multipath delay spread is shorter than 4.7 μs.
• The settings of Cell.UlCyclicPrefix and
Downlink cyclic Cell.DlCyclicPrefix Cell.DlCyclicPrefix of a cell can be different or
prefix length not.
• The setting of Cell.UlCyclicPrefix or
Cell.DlCyclicPrefix of a cell must be the same
as that of the other cells established on the
same BBP.

4.4.1.2 Using MML Commands

//Activating normal CP
MOD CELL: LocalCellId=0, UlCyclicPrefix=NORMAL_CP, DlCyclicPrefix=NORMAL_CP;

4.4.1.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

4.4.2 Activation Verification

1. On the MAE, run the LST CELL command and check the values of Uplink cyclic
prefix length and Downlink cyclic prefix length.
• If the values are Normal, normal CP has been configured.
• If the values are Extended, extended CP has been configured.
2. On the MAE, start Uu interface tracing, deactivate the cell, and then reactivate it.
Wait until the cell is successfully activated, and then check the value of the
information element (IE) ul-CyclicPrefixLength in the first RRC_SYS_INFO
message (a SIB2 message) over the Uu interface.
• If its value is len1(0), normal CP is working in the uplink.
• If its value is len2(1), extended CP is working in the uplink.

CP configuration in the downlink is transparent to UEs. Therefore, there are no messages to check for
the downlink.
 4.4.3 Network Monitoring

None

5 Extended CP

5.1 Principles

Extended CP applies to scenarios where the delay spread is long. When multipath interference is
severe, system performance deteriorates significantly if the multipath delay spread is longer than
a normal CP. In an OFDM system, extended CP enhances multipath delay spread resistance in
large-cell-radius scenarios and multipath interference resistance. However, extended CP
increases the system overhead and consumes certain number of transport resources.
shows the structure of a timeslot in the extended CP case. The timeslot consists of six
Figure 5-1
downlink OFDM symbols or uplink SC-FDMA symbols. The CP length of each symbol is
approximately 16.7 μs.
Figure 5-1 Structure of a timeslot in the extended CP case (with a subcarrier spacing of 15 kHz)
 As shown in Figure 5-1, an extended CP is longer than a normal CP. The permissible multipath
delay at the receiving end increases with the CP length. The use of extended CP, however,
causes more system overhead than the use of normal CP. The system overhead for the extended
CP case is calculated using the following formula:

5.2 Network Analysis

5.2.1 Benefits

The CP technique mitigates ISI and ICI caused by multipath delay, ensuring network coverage in
E-UTRAN cells.
The deployment suggestions of extended CP are as follows:
• It is recommended that extended CP be activated to improve uplink and downlink
signal to interference plus noise ratios (SINRs) if the multipath delay spread exceeds
the normal CP length of 4.7 μs in the area (the time difference is greater than the
length of a normal CP, 4.7 μs), for example, where there are high buildings or
mountains in the distance that will reflect signals. This condition can be interpreted as
follows: There is at least 1.5 km difference between the line of sight (LOS) path of a
signal arriving at a UE and the reflected path of the same signal last arriving at the UE.
• It is difficult to obtain the actual multipath delay spread. To evaluate whether to use
extended CP, operators can estimate whether the multipath delay spread is longer than
the normal CP length based on the building distribution and landform.
• UEs may not support extended CP. Enabling this function may cause exceptions of
such UEs. It is not recommended that this function be enabled if there are such UEs on
the live network. The extended CP capability of UEs depends on UEs themselves.

This capability cannot be identified through UE capability information. If a UE can access a cell with
extended CP enabled and the UE data rate can reach its peak value, this indicates that the UE supports
extended CP.

5.2.2 Impacts

Network Impacts

The use of extended CP causes more system overhead than the use of normal CP and therefore
system capacity decreases.

Function Impacts
 RAT Function Function Switch Reference Description
Name

FDD Dynamic CellAlgoSwitch.EicicSwitch TDM eICIC (FDD) To use enhanced

TDM eICIC parameter with the value of inter-cell
DYNAMIC interference
coordination
(eICIC), operators
need to enable this
function in both
macro and micro
cells. Extended CP
is applicable only to
macro eNodeBs. If
extended CP is
enabled only in cells
served by macro
eNodeBs, optimal
performance of
eICIC cannot be
assured.

FDD UL 64QAM PUSCHCfg.Qam64Enabled Modulation Schemes In extended CP

parameter with the value of scenarios, UL
BOOLEAN_TRUE 64QAM does not
take effect.

FDD PAMC UlPAMCSwitch option of the Scheduling In extended CP

CellAlgoSwitch.UlSchExtSwitch scenarios, PAMC
parameter does not take effect.

5.3 Requirements

5.3.1 Licenses

RAT Feature ID Feature Name Model Sales Unit

FDD LOFD-001031 Extended CP LT1S000ECP00 per RRC

Connected User

5.3.2 Software

Before activating this function, ensure that its prerequisite functions have been activated and
mutually exclusive functions have been deactivated. For detailed operations, see the relevant
feature documents.

Prerequisite Functions

None
Mutually Exclusive Functions

RAT Function Function Switch Reference Description

Name

FDD Uplink joint UL_JOINT_INTRF_SUPPRESS_SW option of Interference None

interference the Detection and
Suppression
management UlInterfSuppressCfg.UlJointIntrfManagementSw
(FDD) parameter

FDD CPRI Cell.CPRICompression CPRI None

compression Compression

FDD SFN cell CellAlgoSwitch.SfnUlSchSwitch SFN The application

CellAlgoSwitch.SfnDlSchSwitch scenarios are
different. Extended
CP applies to the
extended coverage
scenario, while single
frequency network
(SFN) applies to
scenarios such as
indoor coverage,
indoor and outdoor
joint coverage,
densely populated
urban areas with short
inter-site distances,
and high-speed
railways.

FDD In-band relay InBandRelayDeNbSwitch and Relay None

InBandRelayReNbSwitch options of the
CellAlgoSwitch.RelaySwitch parameter

FDD Super SuperCombCellSwitch option of the Super None

combined CellAlgoSwitch.SfnAlgoSwitch parameter Combined Cell
(FDD)
cell

FDD DL CoMP FDDHomNetDlCompSwitch and DL CoMP Downlink (DL)

cell FDDHetNetDlCompSwitch options of the (FDD) coordinated multipoint
CellAlgoSwitch.DlCompSwitch parameter transmission/reception
(CoMP) does not
support extended cell
range scenarios
because DL CoMP
UEs must receive
data from different
cells. Extended CP is
usually deployed in
RAT Function Function Switch Reference Description
Name

extended cell range

scenarios. Therefore,
extended CP is not
supported when DL
CoMP is enabled.

FDD LTE in-band Prb.DeployMode NB-IoT In the current version,

deployment Enhancements both the NB-IoT cell
(FDD)
and the corresponding
LTE FDD cell do not
support extended CP
in LTE in-band
deployment.

FDD Massive Massive MIMO works in multiple scenarios. Its Massive MIMO None
MIMO function switch varies depending on scenarios. (FDD)
introduction For details, see Massive MIMO (FDD).

FDD Intelligent MM_INTELLIGENT_BEAM_SHAPING_SW Massive MIMO None

beam option of the SectorSplitGroup.SectorSplitSwitch (FDD)
shaping parameter

FDD WTTx MU- Tm9FourLayerPairSwitch option of the WTTx MU- None

MIMO CellAlgoExtSwitch.WttxMuMimoSwitch MIMO (FDD)
parameter

FDD Dynamic None Smart 8T8R When Dynamic

Massive (FDD) Massive Beam is
Beam used, set
Cell.UlCyclicPrefix and
Cell.DlCyclicPrefix to
NORMAL_CP.

FDD CRS CRS_DYNAMIC_MUTING_SW option of the Energy CRS dynamic muting

dynamic SymbolPwrSaving.SymbolShutdownEnhancedSw Conservation is not supported in
and Emission
muting parameter Reduction extended CP
scenarios.

FDD RF channel RF_CHN_DYN_MUTING_SW option of the Energy None

dynamic CellRfChnDynMuting.RfChnDynMutingAlgoSwitch Conservation
and Emission
muting parameter Reduction

FDD Dynamic CARRIER_DYN_SHUTDOWN_SW option of Energy Dynamic carrier

carrier the CellShutdown.CarrierShutdownEnhancedSw Conservation shutdown is not
and Emission
shutdown parameter Reduction supported in extended
CP scenarios.
 RAT Function Function Switch Reference Description
Name

FDD Static SectorSplitGroup.BeamTemplateId set to 0, Smart 8T8R When Static Multiple

Multiple SectorSplitGroup.BeamDeploymentMode set to (FDD) Beam is used, set
Beam MODE_3, and SectorSplitCell.CellBeamIndex Cell.UlCyclicPrefix and
set to 0 or 1 Cell.DlCyclicPrefix to
NORMAL_CP.

5.3.3 Hardware

Base Station Models

3900 and 5900 series base stations are compatible with this function.

Boards

In FDD, the following BBP models do not support extended CP:

• UBBPex2

RF Modules

In FDD: The AAU, pRRU, and book RRU do not support extended CP.

Cells

The cell bandwidth must be greater than 5 MHz.

5.3.4 Others

UEs must support extended CP.

5.4 Operation and Maintenance

5.4.1 Data Configuration

5.4.1.1 Data Preparation

describes the parameters used for function activation. This section does not describe
Table 5-1
parameters related to cell establishment.

At the moment when the CP modification takes effect in an activated cell, services carried by
UEs are interrupted in the cell. The duration for the UEs to reacquire synchronization with the
cell depends on the synchronization performance of the UEs.

Table 5-1 Parameters used for activation

 Parameter Name Parameter ID Setting Notes

Uplink cyclic Cell.UlCyclicPrefix • Set the parameters to EXTENDED_CP when

prefix length multipath delay spread is longer than 4.7 μs.
• The settings of Cell.UlCyclicPrefix and
Downlink cyclic Cell.DlCyclicPrefix Cell.DlCyclicPrefix of a cell can be different or
prefix length not.
• The setting of Cell.UlCyclicPrefix or
Cell.DlCyclicPrefix of a cell must be the same
as that of the other cells established on the
same BBP.

5.4.1.2 Using MML Commands

Activation Command Examples

//Activating extended CP
MOD CELL: LocalCellId=0, UlCyclicPrefix=EXTENDED_CP,
DlCyclicPrefix=EXTENDED_CP;

Deactivation Command Examples

//Deactivating extended CP
MOD CELL: LocalCellId=0, UlCyclicPrefix=NORMAL_CP, DlCyclicPrefix=NORMAL_CP;

5.4.1.3 Using the MAE-Deployment (FDD)

• Fast batch activation

This function can be batch activated using the Feature Operation and Maintenance
function of the MAE-Deployment. For detailed operations, see the following section
in the MAE-Deployment product documentation or online help: MAE-Deployment
Operation and Maintenance > MAE-Deployment Guidelines > Enhanced Feature
Management > Feature Operation and Maintenance.
• Single/Batch configuration
This function can be activated for a single base station or a batch of base stations on
the MAE-Deployment. For detailed operations, see Feature Configuration Using the MAE-
Deployment.

5.4.1.4 Using the MAE-Deployment (TDD)

For detailed operations, see Feature Configuration Using the MAE-Deployment.

5.4.2 Activation Verification

For details, see 4.4.2 Activation Verification.

5.4.3 Network Monitoring

None
6 Parameters

The following hyperlinked EXCEL files of parameter documents match the software version
with which this document is released.
• Node Parameter Reference: contains device and transport parameters.
• eNodeBFunction Parameter Reference:contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and
radio resource management.
• eNodeBFunction Used Reserved Parameter List: contains the reserved parameters that are in
use and those that have been disused.

You can find the EXCEL files of parameter reference and used reserved parameter list for the software version used
on the live network from the product documentation delivered with that version.

FAQ 1: How do I find the parameters related to a certain feature from parameter
reference?
1. Open the EXCEL file of parameter reference.
2. On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-
001016.
3. Click OK. All parameters related to the feature are displayed.
FAQ 2: How do I find the information about a certain reserved parameter from the used
reserved parameter list?
1. Open the EXCEL file of the used reserved parameter list.
2. On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version in
which it is activated for use.
7 Counters

The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
• Node Performance Counter Summary: contains device and transport counters.
• eNodeBFunction Performance Counter Summary:
contains all counters related to radio access
functions, including air interface management, access control, mobility control, and
radio resource management.

You can find the EXCEL files of performance counter reference for the software version used on the live network
from the product documentation delivered with that version.

FAQ: How do I find the counters related to a certain feature from performance counter
reference?
1. Open the EXCEL file of performance counter reference.
2. On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
3. Click OK. All counters related to the feature are displayed.

8 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

9 Reference Documents

1. 3GPP TS 36.211 V8.9.0, "SC-FDMA baseband signal generation"

2. 3GPP TS 36.211 V8.9.0, "OFDM baseband signal generation"
3. CPRI Compression

4. DL CoMP (FDD)

5. Massive MIMO (FDD)

6. WTTx MU-MIMO (FDD)

7. NB-IoT Enhancements (FDD)

8. Relay

9. SFN

10. Smart 8T8R (FDD)

11. Super Combined Cell (FDD)
12. Scheduling
13. Modulation Schemes
14. Interference Detection and Suppression
15. Energy Conservation and Emission Reduction
16. TDM eICIC (FDD)
17. Physical Channel Resource Management