CSPC
Contents
4.3.2 CSPC
eRAN
CSPC Feature Parameter Description
Issue
05
Date
2023-03-25
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2023. 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:
support@huawei.com
4.3.2 Contents
1 Change History
1.1 eRAN17.1 05 (2023-03-25)
1.2 eRAN17.1 04 (2022-05-07)
1.3 eRAN17.1 03 (2021-06-26)
1.4 eRAN17.1 02 (2021-04-30)
1.5 eRAN17.1 01 (2021-03-05)
1.6 eRAN17.1 Draft B (2021-01-31)
1.7 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 Overview
3.1 Background
3.2 Introduction
3.3 Architecture
4 CSPC
4.1 Principles
4.1.1 Clustering for CSPC
4.1.2 CSPC Procedure
4.1.3 Scheduling for CSPC
4.1.4 RSRP Measurement for CSPC
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 Networking
4.3.5 Others
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation (FDD)
4.4.1.2 Using MML Commands (FDD)
4.4.1.3 Using the MAE-Deployment (FDD)
4.4.2 Activation Verification (FDD)
4.4.3 Network Monitoring (FDD)
4.4.4 Possible Issues
5 eCSPC (FDD)
5.1 Principles
5.1.1 eCSPC Procedure
5.1.2 Scheduling for eCSPC
5.1.3 RSRP Measurement for eCSPC
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 Networking
5.3.5 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
5.4.2 Activation Verification
5.4.3 Network Monitoring
5.4.4 Possible Issues
6 Intra-eNodeB CSPC (FDD)
6.1 Principles
6.1.1 Intra-eNodeB CSPC Procedure
6.1.2 Scheduling for Intra-eNodeB CSPC
6.1.3 RSRP Measurement for Intra-eNodeB CSPC
6.2 Network Analysis
6.2.1 Benefits
6.2.2 Impacts
6.3 Requirements
6.3.1 Licenses
6.3.2 Software
6.3.3 Hardware
6.3.4 Networking
6.3.5 Others
6.4 Operation and Maintenance
6.4.1 Data Configuration
6.4.1.1 Data Preparation
6.4.1.2 Using MML Commands
6.4.1.3 Using the MAE-Deployment
6.4.2 Activation Verification
6.4.3 Network Monitoring
7 Parameters
8 Counters
9 Glossary
10 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 05 (2023-03-25)
This issue includes the following changes.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
1.2 eRAN17.1 04 (2022-05-07)
This issue includes the following changes.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
1.3 eRAN17.1 03 (2021-06-26)
This issue includes the following changes.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
Renamed Static Shared Beam as Static Multiple Beam and Dynamic Dedicated Beam as
Dynamic Massive Beam. For details, see:

4.3.2 Software

5.3.2 Software

6.2.2 Impacts

6.3.2 Software
1.4 eRAN17.1 02 (2021-04-30)
This issue includes the following changes.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
1.5 eRAN17.1 01 (2021-03-05)
This issue includes the following changes.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
1.6 eRAN17.1 Draft B (2021-01-31)
This issue includes the following changes.
Technical Changes
None
Editorial Changes

Changed the reference document for centralized power sharing, which is mutually
exclusive with CSPC and eCSPC, from Dynamic Power Sharing Between LTE Carriers to
Smart 8T8R (FDD). For details, see 4.3.2 Software and 5.3.2 Software.

Revised descriptions in this document.
1.7 eRAN17.1 Draft A (2020-12-29)
This issue introduces the following changes to eRAN16.1 02 (2020-05-21).
Technical Changes
Change Description
Parameter Change
RAT
Deleted ALM-27107
Interconnected Optical
Module Receive Failure
and replaced it with ALM27109 Inter-Port Failure as
of this version. For details,
None
FDD
Base Station Model


3900 and 5900
series base
stations
DBS3900
LampSite and
DBS5900
Change Description
Parameter Change
RAT
Base Station Model
see 4.4.4 Possible Issues.
Deleted ALM-27108
Interconnected Optical
Module Transmit Failure
and replaced it with ALM27105 Interconnected
Optical Module Fault as of
this version. For details,
see 4.4.4 Possible Issues.
LampSite
None
FDD


Deleted as of this version
None
ALM-26312 Inter-BBU
Optical Module Receive
Failure and ALM-26313
Inter-BBU Optical Module
Transmit Failure, which are
no longer provided in 4.4.4
Possible Issues.
FDD
Added incompatibility of
None
CSPC with RF channel
dynamic muting. For
details, see Mutually Exclusive
Functions in 4.3.2 Software.
FDD
Added incompatibility of
None
CSPC with centralized
power sharing and Hybrid
DSS Based on Asymmetric
Bandwidth. For details, see
Mutually Exclusive Functions in
4.3.2 Software.
FDD
Added incompatibility of
eCSPC with centralized
power sharing and RF
channel dynamic muting.
For details, see Mutually
Exclusive Functions in 5.3.2
Software.
None
FDD
Added incompatibility of
intra-eNodeB CSPC with
RF channel dynamic
muting. For details, see
None








FDD


3900 and 5900
series base
stations
DBS3900
LampSite and
DBS5900
LampSite
3900 and 5900
series base
stations
DBS3900
LampSite and
DBS5900
LampSite
3900 and 5900
series base
stations
DBS3900
LampSite and
DBS5900
LampSite
3900 and 5900
series base
stations
DBS3900
LampSite and
DBS5900
LampSite
3900 and 5900
series base
stations
DBS3900
LampSite and
DBS5900
LampSite
3900 and 5900
series base
stations
DBS3900
Change Description
Mutually Exclusive Functions
6.3.2 Software.
Parameter Change
RAT
Base Station Model
in
Canceled the compatibility
with the BTS3911E as of
this version.
LampSite and
DBS5900
LampSite
None
FDD
BTS3911E
Editorial Changes
Revised descriptions in this document.
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.
Functions mentioned in this document work properly only when enabled in the specified applicable
scenarios (such as RAT and networking). If a function not mentioned in this document is enabled or a
function is enabled in a scenario not specified as applicable, exceptions or other impacts may occur.
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
LOFD-070208
Coordinated
Scheduling based
Power Control
4 CSPC
3
5 eCSPC (FDD)
Overview
For FDD, the Coordinated Scheduling based Power Control feature includes the following
functions:

Coordinated scheduling-based power control (CSPC) in networks deployed using a
centralized Cloud BB architecture (referred to as CSPC in this document)

CSPC in IP RANs (referred to as eCSPC in this document)
In this document, micro cells are those with low transmit power and small coverage radius. They can be served by
low-power RF modules of macro eNodeBs.


Among 1T1R cells, micro cells are those with total RRU transmit power not greater than 5 W.
Among 2T2R and 4T4R cells, micro cells are those with total RRU transmit power not greater than 10
W.
3.1 Background
In an LTE network, physical resource block (PRB) usage increases with traffic volume. UEs
experience severe interference in densely populated urban areas where intra-frequency cells are
deployed with an average inter-site distance (ISD) of less than 500 m, as shown in Figure 3-1 and
Figure 3-2.
Figure 3-1 Macro-macro intra-frequency network (FDD)
Figure 3-2 HetNet
Downlink transmit power can be coordinated between cells to increase the signal to interference
plus noise ratio (SINR) for cell edge UEs. The modulation and coding scheme (MCS) for
downlink data transmission can be adjusted based on interference from neighboring cells,
improving network performance.
Cell edge UEs are defined in either of the following two ways:
 By geographical location: Cell edge UEs are UEs that are located at the geographical edge of a cell.
 By throughput: Cell edge UEs are the 5% of all UEs in the cell with the lowest throughput.
The scope of cell edge UEs defined by throughput varies significantly with different traffic models. You are advised
to use the geographical location to determine whether a UE is a cell edge UE.
Inter-cell power coordination can be performed in the frequency and time domains.

In the frequency domain, adaptive inter-cell interference coordination (ICIC) works.
For details, see Adaptive ICIC.

In the time domain, the feature described in this document works.
3.2 Introduction
The Coordinated Scheduling based Power Control feature coordinates transmit power
configurations between cells in the time domain. Figure 3-3 shows an example of the coordination
between two neighboring cells. In each cell, the transmit power of individual resource elements
(REs) carrying data on the physical downlink shared channel (PDSCH) is adjusted in each
transmission time interval (TTI). This allows them to meet their respective scheduling
requirements.
Figure 3-3 Example of time-domain transmit power coordination
For FDD, CSPC supports full- and zero-power transmission in macro and micro cells.
In full-power transmission mode, no restriction is imposed on data service scheduling. In zero-power transmission
mode, data services are not scheduled in zero-power subframes.
For FDD:
Coordinated Scheduling based Power Control includes the CSPC and eCSPC functions. These
functions are used in the scenarios listed in Table 3-1.
Table 3-1 Deployment requirements and application scenarios of Coordinated Scheduling based Power
Control
Function
Deployment Requirement
Application Scenario
CSPC
Universal switching units (USUs)
An operator requires fast interference
and centralized control nodes must coordination.
be deployed.
eCSPC
USUs and centralized control
nodes are not required.
An operator allows interference
coordination at longer time intervals.
Intra-eNodeB CSPC is used in the scenario listed in Table 3-2.
Table 3-2 Deployment requirements and application scenarios of intra-eNodeB CSPC
Function
Deployment Requirement
Application Scenario
Intra-eNodeB
CSPC
USUs and centralized control
nodes are not required.
An operator requires interference
coordination between intra-frequency
cells served by the same baseband
processing unit (BBP) in an eNodeB.
These functions can be deployed individually or in combinations. Note that:

CSPC and eCSPC cannot be deployed simultaneously.

When intra-eNodeB CSPC is deployed with CSPC or eCSPC, the intra-eNodeB CSPC
procedure takes place to optimize the MCSs for UEs that experience interference
primarily from intra-eNodeB intra-frequency cells.
3.3 Architecture
CSPC
The CSPC function is implemented on the MAE-Access, USUs, eNodeBs, centralized control
nodes, and UEs. It requires time synchronization with accuracy of ±1.5 μs across the network.
For FDD, this function works in a macro network (comprised of macro cells only), in a HetNet
(comprised of both macro and micro cells), or in a LampSite network (comprised of LampSite
eNodeBs only). Figure 3-4, Figure 3-5, and Figure 3-6 show the network architectures for CSPC.
Figure 3-4 Network architecture for CSPC (macro network)
Figure 3-5 Network architecture for CSPC (HetNet)
The micro cell is served by a distant low-power remote radio unit (RRU), rather than by a micro eNodeB.
Figure 3-6 Network architecture for CSPC (LampSite network)
The following describes the functions of each entity involved in CSPC:

UE
A UE measures the channel state information (CSI) about its serving cell and reports
the results to the serving eNodeB. In addition, the UE receives downlink scheduling
information from the eNodeB.


eNodeB

Measures and maintains the uplink reference signal received power (RSRP)
for serving and neighboring cells of each served UE.

Provides information such as the RSRP measurement, MCS, and scheduled
data rate for each served UE to the centralized control node. The eNodeB
updates the downlink power for each served cell and neighboring cells
based on configurations received from the centralized control node.
Centralized control node
A centralized control node is deployed in a baseband processing unit (BBP) in the
baseband unit (BBU) of an eNodeB. Cells are not established on this BBP.
Centralized control nodes can be classified into centralized clustering nodes and
centralized scheduling nodes based on logical functions.

A centralized clustering node divides cells into clusters and maps each
cluster to only one centralized scheduling node. For details about clustering,
see 4.1.1 Clustering for CSPC.

A centralized scheduling node collects information about UEs in the cells in
a cluster, performs centralized scheduling, generates the suggested
downlink power configurations for all the cells, and delivers the results to
the eNodeBs. It is not recommended that multiple centralized scheduling
nodes be deployed on the same BBU.
For more details about centralized clustering nodes and centralized scheduling nodes,
see Cloud BB Overview.
On a Cloud BB network, the CSPC function can be deployed for cells of the same
duplex mode.

For cells in the same duplex mode on a Cloud BB network, one centralized
control node can work as both a centralized clustering node and a
centralized scheduling node. Other centralized control nodes can work only
as centralized scheduling nodes. Figure 3-7 shows CSPC deployment for cells
in the same duplex mode on a Cloud BB network.
A centralized clustering node supports a maximum of 12 centralized
scheduling nodes and a centralized scheduling node supports a maximum of
180 cells. As a result, all cells in a Cloud BB network can use CSPC at the
same time. For details about hardware planning for centralized scheduling
nodes, see 4.3.3 Hardware.
Figure 3-7 CSPC deployment for cells in the same duplex mode on a Cloud BB network

USU
One or more USUs connect multiple BBUs to form a Cloud BB network. The CSPC
function can be used only in a Cloud BB network.
For details about Cloud BB networking, see Cloud BB Overview, USU3900-based Multi-BBU
Interconnection, and USU3910-based Multi-BBU Interconnection.

MAE-Access
On the MAE-Access, users can query cell power configurations and observe
performance counters to review the improvements brought by this function. For
details, see 4.4.3 Network Monitoring (FDD).
eCSPC (FDD)
The eCSPC function does not require time synchronization across the entire network and can be
directly deployed on a network. Figure 3-8 shows the network architecture for eCSPC. It works in
a macro network or a HetNet.
Figure 3-8 Network architecture for eCSPC
The following describes the functions of entities and interfaces involved in eCSPC:

UE
A UE measures the CSI about its serving cell and reports the results to the serving
eNodeB. In addition, the UE receives downlink scheduling information from the
eNodeB.


eNodeB

Measures and maintains the downlink event A3 RSRP for serving and
neighboring cells of each served UE.

Calculates optimum downlink transmit power for serving and neighboring
cells and updates cell power configurations.
eX2
The eX2 interface is a logical interface between eNodeBs for service coordination. For
details, see eX2 Self-Management.

MAE-Access
On the MAE-Access, users can query cell power configurations and observe
performance counters to review the improvements brought by this function. For
details, see 5.4.3 Network Monitoring.
Intra-eNodeB CSPC (FDD)
Intra-eNodeB CSPC reduces interference only between intra-frequency cells served by an
eNodeB. It can be directly deployed in an eNodeB and does not have requirements for network
architecture.
4
CSPC
4.1 Principles
4.1.1 Clustering for CSPC
Definition of a Cluster
A cluster is a contiguous area covered by cells that support CSPC, as shown in Figure 4-1. Clusters
are introduced to deal with limited baseband processing capabilities and scheduling delays.
Figure 4-1 Definition of a cluster
Cluster-Level CSPC Triggering (FDD)
CSPC brings high gains in networks with medium or high loads. Cell loads in the CSPC
coverage area are monitored in real time to evaluate triggering of CSPC at the cluster level.
Figure 4-2
illustrates when a cluster enters or exits CSPC.
Figure 4-2 Evaluation of entry into or exit from CSPC for a cluster

eNodeBs calculate the maximum downlink PRB usage of cells every 5 minutes within
each period of 15 minutes. If the maximum downlink PRB usage of any cell in a
cluster exceeds the CspcAlgoPara.CspcEnableDlPrbRatioThd parameter value three
times within a period, the cluster enters the CSPC state for inter-cell power
coordination.

The cluster exits CSPC only when the maximum downlink PRB usage of each cell in
the cluster becomes less than the result of the CspcAlgoPara.CspcEnableDlPrbRatioThd
parameter value minus 10% three times. This prevents ping-pong CSPC entry and
exit.
Clustering Principles
Cells that meet all the following requirements can be grouped in a cluster:

The geographical coverage of the cells is continuous.

The average inter-RRU distance is less than 500 m in densely populated urban areas.

The cells operate on the same frequency, have identical bandwidths, and use the same
duplex mode.

There are hotspot cells whose busy-hour downlink PRB usage is greater than 40%.
The gains brought by CSPC depend on the number of cells in a cluster. If a cluster consists of
more cells, the scheduling delay is longer; if a cluster consists of fewer cells, a larger percentage
of these cells experience interference from outside the cluster.
The total delay in calculation for centralized scheduling should be as short as possible so that the
power configurations can meet inter-cell interference and data transmission requirements for the
coverage area. In FDD, a cluster consists of a maximum of 72 cells.
The following are suggestions for clustering:

Deploy hotspot cells, whose busy-hour downlink PRB usage is greater than 40%, in
the center of a cluster.

Deploy lightly-loaded cells at the edges of the cluster.

Make the shape of the cluster close to a circle, in order to maximize feature gains.
Power is not coordinated between cells in different CSPC clusters.
4.1.2 CSPC Procedure
Figure 4-3
illustrates the sequence of transmissions involved in CSPC.
Figure 4-3 CSPC-related transmission sequence
UE information reporting and power configuration delivery occur in sequence. The total delay is
determined by the transmission and processing delay. The transmission delay is within 1 ms in
Cloud BB scenarios. The processing delay is determined by the number of cells to be processed.
The interval at which an eNodeB reports UE information is the same as the period within which
the centralized scheduling node performs centralized scheduling and also the same as the interval
at which the eNodeB receives and applies power configurations. The reporting interval,
scheduling period, and delivery interval are denoted by T1, T3, and T2, respectively.
Figure 4-4
outlines the CSPC procedure.
Figure 4-4 CSPC procedure
1. All UEs in the CSPC coverage area measure the CSI in their respective serving cells
and report the measurement results to the eNodeBs.
2. The eNodeBs send measurement reports to the centralized scheduling node. The
reports contain information such as the RSRP measurements, MCSs, RB usage in
each cell, and scheduled data rates for UEs.
3. The centralized scheduling node periodically collects UE information from the
eNodeBs and performs centralized scheduling. During this scheduling, the
centralized scheduling node considers the MCSs for UEs under cell power
configurations and generates downlink power configurations that are optimal for
overall scheduling performance. The centralized scheduling node then sends the
power configurations to the eNodeBs.
The centralized control node periodically generates the following information for
each cell involved in centralized scheduling:

Power configuration for the downlink time-frequency resources in the cell
within a power configuration period

Set of neighboring cells that cause interference to the local cell, as well as
the power configurations for the downlink time-frequency resources in the
neighboring cells within the same power configuration period
The power configurations for all the cells involved in centralized scheduling in one
period take effect at the same time. The time is specified by the centralized
scheduling node.
4. Based on the downlink scheduling algorithm, each eNodeB changes the downlink
power of each served cell and neighboring cell to the power values received from the
centralized scheduling node.
4.1.3 Scheduling for CSPC
CSPC-capable cells periodically report information about upcoming UE scheduling to
centralized scheduling nodes, which specify the reporting time. If there are no UEs to be
scheduled in a cell, the cell does not report UE scheduling information.
Each cell periodically receives, and saves, TTI-specific power configurations for the local cell
and interfering neighboring cells from the centralized scheduling node. In each TTI, the
scheduler of each cell sets downlink transmit power to the received power value. The power
configurations take effect for initial transmission of user data but not for common and dedicated
control information transmissions or user data retransmission.
In each TTI, the scheduler of each cell updates the MCS for each UE that experiences
interference. The update is based on the CSI values, RSRP values, and hybrid automatic repeat
request (HARQ) feedback from UEs, in addition to the active power configurations for the
current cell and interfering neighboring cells. The MCS update improves channel quality.
For details about downlink scheduling, see Scheduling.
4.1.4 RSRP Measurement for CSPC
CSPC adjusts the MCSs for UEs at the cell edge by adjusting cell transmit power in each TTI.
The MCS for a cell edge UE experiencing interference in the downlink is closely related to the
transmit power of the neighboring cell and the distance from the UE to the neighboring cell.

If the transmit power from the neighboring cell remains unchanged, the MCS index
has a negative correlation with the measured RSRP of signals from the neighboring
cell. Higher RSRP indicates greater interference from the neighboring cell.

If the measured RSRP of signals from the neighboring cell remains unchanged, the
MCS index has a negative correlation with the transmit power for traffic channels in
the neighboring cell. Lower transmit power from the neighboring cell results in less
interference to the UE in its serving cell.
CSPC determines in real time an MCS suitable for interference coordination by evaluating the
RSRP measurement and the transmit power of the neighboring cell.
In FDD, only uplink RSRP measurement can be used for cell edge UEs. Figure 4-5 and Figure 4-6
illustrate RSRP measurements on a macro or LampSite network and on a HetNet, respectively.
Uplink RSRP measurement takes effect when the CspcAlgoPara.CspcRsrpMeasMode parameter is
set to RSRP_UL. Currently, this type of measurement is based on sounding reference signals
(SRSs).
Figure 4-5 RSRP measurement (macro or LampSite network)
RSRP measurement on a LampSite network is the same as that on a macro network.
Figure 4-6 RSRP measurement (HetNet)
Uplink RSRP Measurement (FDD)
The serving cell and neighboring cells all receive uplink signals from the cell edge UE. The
serving cell informs each neighboring cell of which time-frequency resources are used for the
uplink transmission. Each neighboring cell then measures the RSRP on the specified resources
and sends the measurement result to the serving cell.
Figure 4-7
shows the uplink RSRP measurement process.
Figure 4-7 Uplink RSRP measurement
On a HetNet, the downlink cell-specific reference signal (CRS) transmit power differs a lot
between macro and micro cells. To use uplink RSRP measurement results to evaluate the relative
downlink interference from a neighboring cell, the serving cell deducts the downlink CRS
transmit power difference between the serving and neighboring cells from the uplink RSRP
measurement value sent by the neighboring cell.
4.2 Network Analysis
4.2.1 Benefits
CSPC efficiently reduces inter-cell interference and offers the following benefits:

Increases downlink user-perceived data rates in hotspot cells on a load-imbalanced
network.

Increases User Downlink Average Throughput of cell edge UEs across the network.
For FDD:
CSPC is recommended when all the following conditions are met:

The average inter-RRU distance between eNodeBs is less than 500 m in densely
populated urban areas. Alternatively, the cells cover large-sized indoor enclosed
buildings, such as stadiums and railway stations.

There are hotspot cells whose busy-hour Downlink Resource Block Utilizing Rate is greater
than 40%.

Most UEs in the network move at speeds less than 10 km/h.

The number of RRC_CONNECTED UEs served by each BBP deployed with cells is
less than 850.

Average CPU Load

The downlink cell bandwidth is greater than or equal to 10 MHz.
of each BBP deployed with cells is less than 75%.
CSPC affects throughput, depending on the following factors:

Inter-cell interference
The shorter the inter-RRU distance, the larger the gains brought by CSPC. An interRRU distance of less than 500 m is recommended for CSPC coverage areas.

Network load distribution
On live networks, cell load is represented by Downlink Resource Block Utilizing Rate in
individual cells. The more imbalanced the load between cells is, the more gains CSPC
brings. Therefore, it is recommended that CSPC be deployed in areas that include
hotspot cells.
Hotspot cells are cells with busy-hour Downlink Resource Block Utilizing Rate of greater than 40%.

Overall network load
Overall network load is represented by the average Downlink Resource Block Utilizing Rate
of all cells in the network.


If the interference level at the time of scheduling differs from the
interference level at the time of channel quality measurement, CSPC can
select a more accurate MCS than an MCS selected without CSPC.
Therefore, CSPC increases spectral efficiency. The increase first rises and
then gradually drops.

If the network load is high, for example the average Downlink Resource Block
Utilizing Rate is greater than 40%, power coordination takes effect as the
probability of scheduling collision between the serving cell and interfering
neighboring cells increases. During power coordination, CSPC adjusts the
percentage of cells in which power is shut down to achieve a tradeoff
between the gains in User Downlink Average Throughput and gains in average
downlink edge-user throughput.
Inter-cluster interference
Power is not coordinated between cells in different CSPC clusters.

The larger the number of cells in a cluster, the smaller the percentage of
cluster edge cells and the higher the gains.

The gains are higher if the interference is more concentrated. For example,
the gains in a cluster covering a circular area are higher than the gains in a
cluster covering a belt-shaped area when the two clusters consist of the
same number of cells.

For a cluster edge cell, the less severe the interference from inter-cluster
neighboring cells is, the higher the gains are.

Shape of the feature coverage area
The larger the feature coverage area is and the more regular the network topology in
the area is, the higher the feature gains are. Therefore, CSPC is recommended for
contiguous coverage areas.

UE movement speed
CSPC requires uplink RSRP measurements. It is recommended for networks where
most UEs move at speeds less than 10 km/h. If most UEs move at higher speeds,
eNodeBs cannot track fast interference changes.
4.2.2 Impacts
Network Impacts
For FDD:
On a heavily loaded network in a densely populated urban area, CSPC increases the downlink
user-perceived data rate without affecting the downlink traffic volume of the entire network.
CSPC can be used when the busy-hour average Downlink Resource Block Utilizing Rate in the CSPC
coverage area exceeds 30%, the inter-RRU distance between eNodeBs is less than 500 m, and no
obvious inter-system interference is present. CSPC has the following impact on network
performance:

User Downlink Average Throughput

To identify cell edge UEs, CSPC requires uplink SRS transmission. The resource
consumption by uplink SRSs affects uplink performance.
increases by 5% to 15%, and the average downlink
edge-user throughput increases by 5% to 30%.
Function Impacts
RA
T
Function
Name
FD
D
Function Switch
Referenc
e
Description
VoIP semi- For the uplink: the
persistent SpsSchSwitch option of the
scheduling CellAlgoSwitch.UlSchSwitch
parameter
For the downlink: the
SpsSchSwitch option of the
CellAlgoSwitch.DlSchSwitch
parameter
VoLTE
CSPC does not take effect for
UEs that are scheduled in a semipersistent manner.
FD
D
Carrier
None
aggregatio
n
Carrier
Aggregatio
n
For FDD, CSPC affects the gains
of carrier aggregation (CA) UEs in
specific scenarios.a
FD
Intra-
UlJointReceptionPhaseIISwit UL CoMP
Intra-eNodeB inter-BBP UL CoMP
RA
T
Function
Name
Function Switch
D
eNodeB
inter-BBP
UL CoMP
ch option of the
CellAlgoSwitch.UplinkCompSwi
tch parameter
FD
D
SFN cell
Cell.MultiRruCellMode
FD
D
Adaptive
SFN/SDM
A
CellAlgoSwitch.SfnDlSchSwitch SFN
Load is measured on a per logical
cell basis.
FD
D
InterNone
eNodeB
SFN based
on eNodeB
coordinatio
n
SFN
When a CSPC cluster includes an
inter-eNodeB SFN cell, the
CspcAlgoPara.CspcPowerConfigD
elay parameter must be set to a
value that is 1 ms longer than the
value for non-SFN cells.
FD
D
eMTC
introductio
n
eMTC
CSPC does not take effect for
UEs capable of enhanced
Machine Type Communication
(eMTC).
FD
D
LTE inNone
band
deploymen
t
NB-IoT
Basics
(FDD)
(Impact on LTE FDD) NB-IoT
causes interference to LTE FDD
SRSs and therefore affects RSRP
measurement.
FD
D
DL CoMP
with TM10
DL CoMP
(FDD)
DL CoMP with TM10 and CSPC
(controlled by
CellCspcPara.CellCspcSwitch) can
be both enabled, but CSPC takes
precedence. If CSPC has taken
effect in a cell, DL CoMP UEs are
not scheduled in coordinating
cells.
EMTC_SWITCH option of the
CellEmtcAlgo.EmtcAlgoSwitch
parameter
HomNet: the
FDDHomNetDlCompSwitch
option of the
CellAlgoSwitch.DlCompSwitch
parameter
HetNet: the
FDDHetNetDlCompSwitch
option of the
CellAlgoSwitch.DlCompSwitch
Referenc
e
Description
and CSPC share intra-eNodeB
inter-BBP bandwidth. If this
bandwidth is limited, the firstcome first-served rule applies.
Any function that fails to be
allocated resources cannot take
effect.
SFN
CSPC can be activated in single
frequency network (SFN) cells
whose
CellRacThd.CellCapacityMode
parameter is set to
NORMALCAPACITY, but not in
SFN cells with this parameter set
to LARGECAPACITY.
RA
T
Function
Name
Function Switch
Referenc
e
Description
DL CoMP
(FDD)
DL CoMP with TM9 and CSPC
(controlled by
CellCspcPara.CellCspcSwitch) can
be both enabled, but CSPC takes
precedence. If CSPC has taken
effect in a cell, DL CoMP UEs are
not scheduled in coordinating
cells.
parameter
FD
D
DL CoMP
with TM9
Tm9JtSwitch option of the
CellAlgoSwitch.DlCompSwitch
parameter
a: CSPC affects the gains of CA UEs in specific scenarios.

Serving- and neighboring-cell RSRP measurements for CSPC are based on SRSs
transmitted by UEs to eNodeBs. If a cell in the CSPC coverage area is configured as a
secondary cell (SCell) for a CA UE but is not configured to work in an uplink band,
SRS configurations do not apply to the UE. As a result, CSPC does not take effect on
the UE.

Centralized control nodes for CSPC help increase the average throughput of cells on
the affected frequency and the cell edge UE throughput in the network. However, it
may have a negative impact on high-throughput UEs that experience interference in
hotspot neighboring cells. If the Round Robin (RR) scheduling policy is used with
CA, the data rate of a CA UE (a variable used to calculate scheduling priority) is
defined as the total data rate of the UE on all the aggregated carriers. It is typically
higher than the data rate of a non-CA UE. As a result, CA UEs encounter a lower
probability of being scheduled and a lower data rate in CSPC scenarios.
4.3 Requirements
4.3.1 Licenses
FDD:
RAT
Feature ID
Feature Name
Model
Sales Unit
FDD
LOFD070208
Coordinated Scheduling
based Power Control
LT1SCSBPCC00 per Cell
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
RAT
Function Name
Function Switch
Reference
FDD
CQI adjustment CqiAdjAlgoSwitch option of the Scheduling
CellAlgoSwitch.CqiAdjAlgoSwitch
parameter
FDD
Synchronization None
with GPS
Synchronization
FDD
IEEE1588 V2
None
clock
synchronization
Synchronization
Description
Channel quality
indicator (CQI)
adjustment enables
the initial block error
rate (IBLER) of UEs to
approach the optimal
target value after
CSPC is activated.
CSPC requires time
synchronization
across the network.
Mutually Exclusive Functions
RAT Function
Name
Function Switch
Reference
Description
FD
D
ACT AICIC executed on the eCoordinator
Adaptive
inter-cell
interference
coordinatio
n
Adaptive ICIC
Adaptive ICIC
is based on
eCoordinators
, whereas
CSPC is
based on
Cloud BB.
They are
suitable for
different
scenarios and
therefore
cannot be
used together.
FD
D
High speed Cell.HighSpeedFlag
mobility
High Speed
Mobility
In high-speed
mobility
scenarios, cell
load changes
so rapidly that
downlink
power
adjustment
cannot
promptly
RAT Function
Name
Function Switch
Reference
Description
follow the load
changes.
FD
D
Dynamic
Power
Sharing
Between
LTE
Carriers
LTE_DYN_POWER_SHARING_SW option
of the
CellDynPowerSharing.DynamicPowerSharingS
witch parameter
Dynamic Power
Sharing
Between LTE
Carriers
CSPC cannot
be activated
together with
this function.
FD
D
Extreme
power
sharing
LTE_EXTREME_POWER_SHARING_SW
option of the
CellDynPowerSharing.DynamicPowerSharingS
witch parameter
Dynamic Power
Sharing
Between LTE
Carriers
CSPC cannot
be activated
together with
this function.
FD
D
Smart 8T8R
Centralized LTE_CENTRAL_POWER_SHARING_SW
(FDD)
power
option of the
CellDynPowerSharing.DynamicPowerSharingS
sharing
witch parameter
CSPC cannot
be activated
together with
this function.
FD
D
Virtual
4T4R
Virtual4T4RSwitch option of the
CellAlgoSwitch.EmimoSwitch parameter
Virtual 4T4R
(FDD)
CSPC cannot
be activated
together with
this function.
FD
D
Energy
saving
based on
proactive
scheduling
SymbolPwrSaving.TrigBndlSchDlAvgPrbThld
Energy
Conservation
and Emission
Reduction
CSPC and
bundled
scheduling
cannot both
take effect.
FD
D
RF channel RF_CHN_DYN_MUTING_SW option of the
CellRfChnDynMuting.RfChnDynMutingAlgoSwi
dynamic
muting
tch parameter
Energy
Conservation
and Emission
Reduction
None
FD
D
Ultra high
speed
mobility
High Speed
Mobility
In high-speed
mobility
scenarios, cell
load changes
so rapidly that
downlink
power
adjustment
cannot
promptly
follow the load
changes.
Cell.HighSpeedFlag
RAT Function
Name
Function Switch
Reference
Description
FD
D
Adaptive
power
allocation
for celledge UEs
AdptCellEdgePwrAllocSw option of the
CellAlgoSwitch.CellDlCoverEnhanceSwitch
parameter
Scheduling
CSPC does
not work with
adaptive
power
allocation for
cell edge
UEs.
FD
D
Cell radius Cell.CellRadius
greater
than 15 km
Extended Cell
Range
FD
D
Cell radius
greater
than 100
km
Cell.CellRadius
Extended Cell
Range
CSPC
requires that
the radius of
each cell
involved
should not
exceed 15
km. If the
radius
exceeds 15
km, CSPC
does not take
effect.
FD
D
CellAlgoSwitch.EicicSwitch being set to
Dynamic
TDM eICIC DYNAMIC
FD
D
Super
combined
cell
FD
D
DdCellGroup.DdBandwidth
Flexible
bandwidth
based on
overlapping
carriers
SuperCombCellSwitch option of the
CellAlgoSwitch.SfnAlgoSwitch parameter
TDM eICIC
(FDD)
CSPC and
this eICIC
function are
suitable for
different
scenarios and
therefore
cannot be
activated
together.
Super Combined
Cell (FDD)
CSPC cannot
be activated
together with
this function.
Flexible
Bandwidth
based on
Overlap Carriers
(FDD)
If a Double
Deck cell
group uses a
non-standard
bandwidth of
5.7, 7.3, 7.6,
8.6, or 8.9
MHz, CSPC
cannot be
RAT Function
Name
Function Switch
Reference
Description
activated in
either of the
cells in the
group.
If a Double
Deck cell
group uses a
non-standard
bandwidth of
4, 12.2, or
17.1 MHz,
CSPC cannot
be activated
in the cell with
a standard
bandwidth of
3 MHz in the
group.
If a Double
Deck cell
group uses a
non-standard
bandwidth of
27.6 or 28.5
MHz, CSPC
cannot be
activated in
the cell with a
standard
bandwidth of
10 MHz in the
group.
FD
D
CDMA and
LTE Zero
Bufferzone
(LTE FDD)
AvoidCDMAInterfSwitch option of the
CellAlgoSwitch.AvoidInterfSwitch parameter
CDMA and LTE
Zero Bufferzone
CSPC cannot
be activated
together with
this function.
FD
D
GSM and
LTE Zero
Bufferzone
GLZeroBufferZoneSwitch option of the
CellAlgoSwitch.DynSpectrumShareSwitch
parameter
GSM and LTE
Zero Bufferzone
CSPC cannot
be activated
together with
this function.
FD
D
Static
Multiple
Beam
None
Massive MIMO
(FDD)
CSPC cannot
be activated
together with
RAT Function
Name
Function Switch
Reference
Description
this function.
FD
D
Dynamic
Massive
Beam
None
Massive MIMO
(FDD)
CSPC cannot
be activated
together with
this function.
FD
D
Intelligent
beam
shaping
MM_INTELLIGENT_BEAM_SHAPING_SW
option of the
SectorSplitGroup.SectorSplitSwitch
parameter
Massive MIMO
(FDD)
CSPC cannot
be activated
together with
this function.
FD
D
LTE FDD
and NR
uplink
spectrum
sharing
SpectrumCloud.SpectrumCloudSwitch
parameter with the value of
LTE_NR_UPLINK_SPECTRUM_SHR
LTE FDD and
NR Uplink
Spectrum
Sharing
CSPC cannot
be activated
together with
this function.
FD
D
LTE FDD
and NR
Flash
Dynamic
Spectrum
Sharing
SpectrumCloud.SpectrumCloudSwitch
parameter with the value of
LTE_NR_SPECTRUM_SHR
LTE FDD and
NR Spectrum
Sharing
CSPC cannot
be activated
together with
this function.
FD
D
Hybrid DSS
Based on
Asymmetric
Bandwidth
SpectrumCloud.SpectrumCloudSwitch
parameter with the value of
LTE_NR_SPECTRUM_SHR, and
LNR_SPECTRUM_SHR_ASYM_SW option
of the
SpectrumCloud.SpectrumCloudEnhSwitch
parameter selected
LTE FDD and
NR Spectrum
Sharing
CSPC cannot
be activated
together with
this function.
FD
D
Superior
uplink
coverage
CellAlgoExtSwitch.UlCoverageEnhancementSw Superior Uplink
CSPC cannot
be activated
together with
this function.
FD
D
Data
learningbased
downlink
intelligent
AMC
DL_INTEL_AMC_SELECTION_SW option of eMIMO (FDD)
the CellIntelAmcConfig.IntelligentAmcSwitch
parameter
CSPC cannot
be activated
together with
this function.
4.3.3 Hardware
Coverage (FDD)
Base Station Models
For FDD, the following base stations are compatible with this function:

3900 and 5900 series base stations

DBS3900 LampSite and DBS5900 LampSite

USU3900

USU3910
Boards
The BBPs listed in Table 4-1 are compatible with CSPC.
Table 4-1 BBPs compatible with CSPC
BBP for Deploying the Centralized Control Node
in an eNodeB
BBP Not for Deploying the Centralized Control
Node in an eNodeB
FDD: UBBPd6/UBBPei/UBBPe6/UBBPg3
FDD: LBBPd/UBBPd/UBBPe/UBBPei/UBBPg

A UMPT must be configured as the main control board for each BBU involved in
CSPC.

If the cells in the CSPC coverage area are configured in BBU3900s or BBU5900s, a
UBBPd, LBBPd, or UBBPe must be installed in slot 2 or 3 of each BBU. This
constraint does not apply to cells configured in BBU3910s.

BBPs used to carry centralized control nodes but not cells must be installed in the
BBUs interconnected through USUs. Only one BBP in an eNodeB is used to carry a
centralized control node. For the BBP that can be used to deploy the centralized
control node and the BBPs not for deploying the centralized control node in an
eNodeB, see the preceding table.

If CSPC is to be deployed for cells in a single duplex mode on a Cloud BB
network, only one centralized clustering node and one or more centralized
scheduling nodes can be deployed on the network.

The centralized clustering node allows all cells served by the
BBUs interconnected through one or two levels of USUs to
participate in CSPC.

In FDD, a cluster consists of a maximum of 72 cells.

The centralized clustering node supports a maximum of 12
centralized scheduling nodes.

Each centralized scheduling node supports a maximum of 180
cells.

If the number of cells for which CSPC is to be
deployed does not exceed 180, only one centralized
control node is required. This node is configured to
work as both a centralized clustering node and a
centralized scheduling node.


If the number of cells for which CSPC is to be
deployed exceeds 180, two or more centralized control
nodes must be deployed. The required number of
centralized control nodes is obtained by rounding up
the result of the number of cells divided by 180.
Among the centralized control nodes, one is
configured to work as both a centralized clustering
node and a centralized scheduling node. The others are
configured to work as centralized scheduling nodes.
If CSPC is to be deployed for both FDD and TDD cells in a Cloud BB
network, the FDD and TDD cells must be configured in different BBUs.
Two centralized clustering nodes, one for FDD cells and the other for TDD
cells, need to be deployed. Each of the nodes supports a maximum of 12
centralized scheduling nodes. Cells in a duplex mode in a CSPC coverage
area can be managed only by centralized control nodes in that duplex mode.
RF Modules
No requirements
4.3.4 Networking

The network must be deployed using the Cloud BB architecture.
For details about the networking, cable connections, and clock synchronization for
USU3900-based Cloud BB architecture, see USU3900-based Multi-BBU Interconnection.
For details about the networking, cable connections, and clock synchronization for
USU3910-based Cloud BB architecture, see USU3910-based Multi-BBU Interconnection. eX2
interfaces must be configured between interconnected BBUs. For details about the
configuration, see eX2 Self-Management.
IP Performance Monitor (PM) sessions of forward activation type are recommended
for delay detection. Avoid configuring an IP PM session of bidirectional activation
type at either end of an eX2 interface. That is because eNodeBs will automatically
create IP PM sessions to detect link status. If an IP PM session of bidirectional
activation type is added, it may conflict with an automatically created session. If this is
the case, the eX2 interface will fail to work properly.

For FDD, in a CSPC coverage area, all the cells must operate on the same frequency,
have the same bandwidth, use the same duplex mode, and primarily provide outdoor
coverage or indoor coverage in large-sized enclosed buildings (such as stadiums and
railway stations).

External synchronization sources must be configured for BBUs. For details, see
Synchronization.
4.3.5 Others
The following information must be collected before CSPC can be deployed:


Engineering parameters of cells

Whether the eNodeBs are outdoor base stations that cover densely
populated urban areas

Whether the average inter-RRU distance between eNodeBs is less than 500
m in densely populated urban areas

Frequency, duplex mode, and bandwidth configurations of cells
Values of counters indicating the LTE network load status and interference level

Counters indicating the network load status are listed in Table 4-2 and Table 43.
Table 4-2 Number of UEs in a cell
Counter ID
Counter Name
1526727378
L.Traffic.User.Avg
1526727379
L.Traffic.User.Max
1526728969
L.Traffic.ActiveUser.DL.Avg
1526728970
L.Traffic.ActiveUser.DL.Max
1526728975
L.Traffic.ActiveUser.Avg
1526728976
L.Traffic.ActiveUser.Max
Table 4-3 Average number of consumed PRBs

Counter ID
Counter Name
1526726740
L.ChMeas.PRB.DL.Used.Avg
1526728433
L.ChMeas.PRB.DL.Avail
1526741763
L.ChMeas.PRB.PUSCH.Avg.BorderUE
1526741767
L.ChMeas.PRB.PDSCH.Avg.BorderUE
Counters indicating the network interference level are listed in Table 4-4,
Table 4-5, Table 4-6, Table 4-7, and Table 4-8.
Before deploying CSPC, run the following command:
MOD CELLCOUNTERPARAGROUP: LocalCellId=0,
CellCounterAlgoSwitch=BasedA3EdgeUserSwitch-1,
EdgeUserA3Offset=-20;
The reason for running this command is as follows: Among the following counters, the
counters related to cell edge UEs are available only when the BasedA3EdgeUserSwitch
option of the CellCounterParaGroup.CellCounterAlgoSwitch parameter is selected. The
offset for event A3 used to identify cell edge UEs is specified by the
CellCounterParaGroup.EdgeUserA3Offset parameter.
Table 4-4 Number of cell edge UEs in a cell
Counter ID
Counter Name
1526741888
L.Traffic.User.BorderUE.Avg
1526741889
L.Traffic.User.BorderUE.Max
Table 4-5 Number of times MCS index n (n = 0 to 31) is selected for PUSCH and
PDSCH scheduling in a cell
Counter ID
Counter Name
1526727412 to
1526727443
L.ChMeas.PUSCH.MCS.0
to L.ChMeas.PUSCH.MCS.31
1526727444 to
1526727475
L.ChMeas.PDSCH.MCS.0
to L.ChMeas.PDSCH.MCS.31
Table 4-6 Number of times the reported wideband CQI is n (n = 0 to 15) in a cell
Counter ID
Counter Name
1526727396 to
1526727411
L.ChMeas.CQI.DL.0
1526737710
L.ChMeas.CQI.DL.BorderUE.Total
1526737711
L.ChMeas.CQI.DL.BorderUE.Num
to L.ChMeas.CQI.DL.15
Table 4-7 Average downlink user data rate in a cell
Counter ID
Counter Name
1526728261
L.Thrp.bits.DL
1526729005
L.Thrp.bits.DL.LastTTI
1526729015
L.Thrp.Time.DL.RmvLastTTI
Average downlink user data rate in a cell = (L.Thrp.bits.DL –
L.Thrp.bits.DL.LastTTI)/(L.Thrp.Time.DL.RmvLastTTI x 1000)
Table 4-8 Downlink data rate of cell edge UEs in a cell
Counter ID
Counter Name
1526737755
L.Thrp.bits.DL.BorderUE
1526737758
L.Thrp.bits.DL.LastTTI.BorderUE
1526737759
L.Thrp.Time.DL.RmvLastTTI.BorderUE
Downlink data rate of cell edge UEs in a cell = (L.Thrp.bits.DL.BorderUE –
L.Thrp.bits.DL.LastTTI.BorderUE)/(L.Thrp.Time.DL.RmvLastTTI.BorderUE x 1000)
4.4 Operation and Maintenance
The CSPC deployment process is as follows:
1. Determine the area in which CSPC is to be deployed.
2. Configure the MAE-Access, USUs, and eNodeBs.
3. Configure data such as the IP addresses, IP routes, and operator information of the
network elements.
4. Configure time synchronization data in the Cloud BB network.
5. Configure the cells and clusters to be involved in CSPC on the eNodeB side.
6. Turn on CSPC switches on the eNodeB side.
For FDD, take the following precautions when deploying CSPC:

All cells in a CSPC coverage area must have the same CSPC configurations.

When deploying CSPC, operators must observe the synchronization status of cells.

When configuring neighboring cells for SRS measurement:


In manual configuration mode, a cell that has the same result of physical
cell identifier (PCI) modulo 30 as the local cell cannot be configured as a
neighboring cell for the local cell. If the local cell and a neighboring cell
have the same result of PCI modulo 30, SRS transmission uses the same
cell-level root sequence in the two cells, making it difficult to differentiate
between signals of UEs on the same time-frequency resources.

In automatic configuration mode, the eNodeB hourly updates the set of
neighboring cells for SRS measurement based on event A3 reports.

Automatic configuration is recommended on live networks. Manual
configuration is recommended for tests or for immediate use of CSPC when
the number of UEs is small and event A3 reports are scarce.
CSPC is based on uplink RSRP measurement. This function requires that the
downlink cell bandwidth be greater than or equal to 10 MHz and that the cell-specific
parameters related to uplink SRS be reconfigured on each eNodeB.
Cell-specific SRS reconfiguration causes cells to be reestablished and therefore should be performed
when traffic is light, for example, in the early morning.

Public land mobile network (PLMN) information must be configured for the eNodeBs
that serve the cells in the CSPC coverage area and for the eNodeBs equipped with the
BBPs where centralized control nodes are deployed. If the PLMN information is not
configured, routes cannot be set up.
4.4.1 Data Configuration
4.4.1.1 Data Preparation (FDD)
The CspcAlgoPara MO consists of CSPC algorithm parameters. The following table describes
the key parameters.
Parameter
Name
Parameter ID
Setting Notes
CSPC
Algorithm
Switch
CspcAlgoPara.CspcAlgoSwitch
Set this parameter as required.
CSPC Power CspcAlgoPara.CspcPowerConfigDelay
Config Delay
If the CSPC cluster includes an intereNodeB SFN cell, set this parameter to
3. In all other scenarios, set this
parameter to 2.
CSPC RSRP CspcAlgoPara.CspcRsrpMeasMode
Measurement
Mode
This parameter specifies the RSRP
measurement type for CSPC. Set this
parameter to RSRP_UL.
CspcAlgoPara.CspcScheduleUeSpec
CSPC
Schedule UE
Specification
The default value is recommended.
CspcAlgoPara.CspcClusterMode
CSPC
Cluster Mode
Currently, only static clustering is
supported.
CSPC
Enable
Downlink
PRB Ratio
Threshold
CspcAlgoPara.CspcEnableDlPrbRatioThd The value 40 is recommended when
the average inter-RRU distance
between eNodeBs is short and
interference is strong, for example, in
densely populated urban areas with a
200 m average inter-RRU distance
between eNodeBs or in stadiums.
The value 70 is recommended when
the average inter-RRU distance
between eNodeBs is long and
Parameter
Name
Parameter ID
Setting Notes
interference is light, for example, in
common urban areas with a 500 m
average inter-RRU distance between
eNodeBs.
CSPC
Capacity
Factor
CspcAlgoPara.CspcCapacityFactor
The value 5 is recommended.
The CellCspcPara MO consists of cell-specific CSPC parameters. The following table describes
the key parameters.
Parameter
Name
Parameter ID
CSPC UE
SRS Config
Report
Period
CellCspcPara.CspcUeSrsCfgRptPeriod This parameter specifies the interval at
which the local cell reports its UE-specific
SRS configurations to the centralized
control node.
The value 1 is recommended.
CellCspcPara.CspcRapidRptSwitch
CSPC UE
SRS Config
Rapid Report
Switch
Setting Notes
This parameter specifies whether to report
the updated UE-specific SRS
configurations immediately after the
configurations are changed.
If this parameter is set to ON, the updated
configurations are reported immediately to
the centralized control node. If this
parameter is set to OFF, the updated
configurations are not reported
immediately.
The value OFF is recommended.
Cell CSPC
Switch
CellCspcPara.CellCspcSwitch
The value ON is recommended.
CSPC CQI
Filter
Coefficient
CellCspcPara.CspcCqiFilterCoeff
For FDD, the value 0 is recommended.
Uplink RSRP CellCspcPara.UlRsrpRptPeriod
Measurement
Report
Period
The value 1 is recommended.
The NCellSrsMeasPara MO consists of SRS measurement parameters for neighboring cells.
The following table describes the key parameters.
Parameter
Name
Parameter ID
Setting Notes
NCellSrsMeasPara.NCellSrsMeasA3Offset
SRS or
DMRS Auto
Neighbour
Cell
Measurement
A3 Offset
The value -20 is recommended.
NCellSrsMeasPara.SrsAutoNCellMeasSwitch
SRS Auto
Neighbour
Cell
Measurement
Switch
For tests or to use CSPC
immediately (for example, in
stadiums), set this parameter to
OFF if the number of UEs is small
and event A3 reports are scarce.
For live networks, the value ON is
recommended.
The CellSrsAdaptiveCfg MO consists of cell-level parameters related to SRS period adaption.
The following table describes the key parameters.
Parameter
Name
Parameter ID
Setting Notes
SRS Period
Adaptive
Switch
CellSrsAdaptiveCfg.SrsPeriodAdaptive Set this parameter to OFF if
CspcAlgoPara.CspcAlgoSwitch is set to
ON.
User SRS
Period
CellSrsAdaptiveCfg.UserSrsPeriod
For non-SFN cells, set this parameter to
ms40.
For SFN cells, set this parameter to ms40
if CellRacThd.CellCapacityMode is set to
NORMALCAPACITY.
The SRSCfg MO consists of cell-level SRS-related parameters. The following table describes
the key parameters.
Parameter Name
Parameter ID
Setting Notes
SRS
Configuration
Indicator
SRSCfg.SrsCfgInd
Set this parameter to BOOLEAN_TRUE if
CspcAlgoPara.CspcAlgoSwitch is set to ON.
FDD SRS
SRSCfg.FddSrsCfgMode
Set this parameter to DEFAULTMODE if
Parameter Name
Parameter ID
CspcAlgoPara.CspcAlgoSwitch is set to ON.
Configuration
Mode
SRS subframe
configuration
Setting Notes
SRSCfg.SrsSubframeCfg
If CspcAlgoPara.CspcAlgoSwitch is set to ON,
set this subframe configuration parameter as
follows:
 If the result of the PCI modulo 3 is 0,
set this parameter to SC3.
 If the result of the PCI modulo 3 is 1,
set this parameter to SC4.
 If the result of the PCI modulo 3 is 2,
set this parameter to SC5.
The CoProcRes MO consists of parameters related to coordinated processing resources.
Parameter Name
Parameter ID
Setting Notes
Baseband
Equipment ID
CoProcRes.BaseBandEqmId
Set this parameter based on the network
plan.
Work Mode
CoProcRes.WorkMode
Select the COORDINATING_PROCESSING
and CLUSTER_MANAGEMENT options of
this parameter.
Coordinate
Process
Resource ID
CoProcRes.CoProcResId
Set this parameter based on the network
plan.
Bundling
Cluster Type
CoProcRes.BundlingClusterType The default value is recommended.
If the COORDINATING_PROCESSING option of the CoProcRes.WorkMode parameter is selected for a BBP
that does not support coordinated processing, ALM-26245 Configuration Data Inconsistency will be reported. In this
case, the BBP supports only universal baseband processing so that cell services are not affected.
The Cluster MO consists of parameters related to clusters. The following table describes the key
parameters.
Parameter Name
Parameter ID
Setting Notes
Cluster ID
Cluster.ClusterId
Set this parameter based on the network plan.
Parameter Name
Parameter ID
Setting Notes
Cluster Type
Cluster.ClusterType
The default value is recommended.
The ClusterCell MO consists of parameters related to cells in clusters. The following table
describes the key parameters.
Parameter Name
Parameter ID
Setting Notes
Cluster ID
ClusterCell.ClusterId
Set this parameter based on the network plan.
Mobile country
code
ClusterCell.Mcc
Set this parameter based on the network plan.
Mobile network
code
ClusterCell.Mnc
Set this parameter based on the network plan.
eNodeB ID
ClusterCell.eNodeBId
Set this parameter based on the network plan.
Cell ID
ClusterCell.CellId
Set this parameter based on the network plan.
4.4.1.2 Using MML Commands (FDD)
Activation Command Examples
Before using MML commands, refer to 4.2.2 Impacts and 4.3.2 Software and complete the parameter
configurations for related functions based on the impact, dependency, and mutually exclusive
relationships between the functions, as well as the actual network scenario.
The following steps assume that the number of cells in which the CSPC function is to be
deployed does not exceed 180 and only one centralized scheduling node is required. To activate
the CSPC function, perform the following steps on the eNodeB side:
1. Run the ADD BRD command to add a BBP for centralized scheduling to the
specified BBU.
2. Run the ADD BASEBANDEQM command to add a set of baseband equipment that
includes the BBP.
3. Run the ADD COPROCRES command to deploy centralized scheduling on the set
of baseband equipment.
The execution of this command interrupts services carried by the boards in the set of
baseband equipment and causes cells on the boards to be reestablished.
4. Run the ADD CLUSTER command to add a cluster on the BBP.
5. Run the ADD CLUSTERCELL command to add cells to the cluster on the BBP.
It is recommended that intra-frequency cells providing continuous coverage be added to the same
cluster.
6. (Required only for manual neighboring cell configuration) Run the ADD
CSPCCELLSRSMEASNCELL command to add neighboring cells, which will
perform SRS measurements, for each cell in the cluster on the BBP.
For each cell in the cluster, select 10 neighboring cells with the shortest inter-RRU distances to the
cell. A cell cannot be configured as a neighboring cell of itself. If you can obtain information about
measurement reports, you are advised to select the 10 neighboring cells with a measurement result –10
dB greater than the local cell and most frequently reported in A3 reports over a period of time.
You are advised not to add neighboring cells for a cell at the cluster edge if the coverage of the cell
overlaps that of cells outside the cluster. If neighboring cells are added for such a cell, the CSPC
function may produce negative gains due to incorrect interference estimation.
7. (Required for automatic neighboring cell configuration) Run the MOD
NCELLSRSMEASPARA command to enable cell-specific automatic SRS
measurement in neighboring cells.
8. Run the MOD SRSCFG and MOD CELLSRSADAPTIVECFG commands to
specify the fixed cell- and UE-specific SRS configurations.
9. Run the MOD CELLCSPCPARA command to set cell-specific CSPC parameters.
In this step, set the cell-level CSPC switch on.
10. Run the MOD CSPCALGOPARA command to set CSPC algorithm parameters on
the BBP. In this step, set the overall CSPC algorithm switch on and specify a
clustering mode.
After CSPC is enabled, modifications of clusters and cells in clusters will take effect
within 5 minutes.
This example assumes that the number of cells for which the function is to be deployed is not
greater than 180.
//Adding a BBP for centralized scheduling to the specified BBU
ADD BRD: CN=0, SRN=0, SN=0, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-1&LTE_TDD-0;
//Adding a set of baseband equipment that includes the BBP
ADD BASEBANDEQM: BASEBANDEQMID=23, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL,
CN1=0, SRN1=0, SN1=0;
//Deploying centralized scheduling on the set of baseband equipment
ADD COPROCRES: CoProcResId=0, BaseBandEqmId=23,
WorkMode=BASEBAND_PROCESSING-0&COORDINATING_PROCESSING-1&CLUSTER_MANAGEMENT1;
//Adding a cluster on the centralized control node
ADD CLUSTER: ClusterId=0;
//Adding a cell to the cluster on the centralized control node
ADD CLUSTERCELL: ClusterId=0, Mcc="460", Mnc="01", eNodeBId=32, CellId=1;
//(Required for manual neighboring cell configuration) Adding a neighboring
cell, which will perform SRS measurements, for the cell in the cluster on
the centralized control node
ADD CSPCCELLSRSMEASNCELL: Mcc="460", Mnc="01", eNodeBId=32, CellId=1,
NCellMcc="460", NCellMnc="01", NCellENodeBId=32, NCellId=2;
//(Required for automatic neighboring cell configuration) Enabling cellspecific automatic SRS measurements in neighboring cells
MOD NCELLSRSMEASPARA: LocalCellId=0, SrsAutoNCellMeasSwitch=ON;
//Specifying the fixed cell- and UE-specific SRS configurations
MOD SRSCFG: LocalCellId=0, SrsSubframeCfg=SC3, SrsCfgInd=BOOLEAN_TRUE,
FddSrsCfgMode=DEFAULTMODE;
MOD CELLSRSADAPTIVECFG: LocalCellId=0, SrsPeriodAdaptive=OFF,
UserSrsPeriod=ms40;
//Turning on the cell-level CSPC switch
MOD CELLCSPCPARA: LocalCellId=0, CellCspcSwitch=ON;
//Turning on the overall CSPC switch and specifying the clustering mode on
the centralized control node
MOD CSPCALGOPARA: CspcAlgoSwitch=ON, CspcClusterMode=STATIC_CONFIG;
Optimization Command Examples
In each TTI, the scheduler of each cell updates the MCS for each UE that experiences
interference. This update is based on the CSI values, RSRP values, and HARQ feedback from
UEs, in addition to the active power configurations for the current cell and interfering
neighboring cells.
Before determining the MCS for a UE that experiences severe interference, the scheduler
estimates the SINR for the UE based on the neighboring-cell power configurations delivered
from the centralized scheduling node.
If the power configurations indicate zero transmit power from a neighboring cell, there is a high
probability that the scheduler selects an MCS with a large index for initial transmission to the
UE. However, the power configurations do not apply to retransmissions of common control
information, UE-specific control information, or UE-specific data. It is possible that the UE is
scheduled in its serving cell when the neighboring cell is transmitting information or data. As a
result, there is a low probability that the SINR of the UE is so low that all permissible
retransmissions fail. Residual block error rate (RBLER) increases as a result.
In most cases, CSPC ensures that the RBLER is lower than 1‰. The RBLER is calculated as
follows:
To meet a stricter RBLER requirement, select the DlRetxTbsIndexAdjOptSwitch option of the
CellAlgoSwitch.CqiAdjAlgoSwitch parameter.
Deactivation Command Examples
The following provides only deactivation command examples. You can determine whether to
restore the settings of other parameters based on actual network conditions.
//Setting the cell-level CSPC switch off
MOD CELLCSPCPARA:LocalCellId=0,CellCspcSwitch=OFF;
//Setting the overall CSPC switch off
MOD CSPCALGOPARA:CspcAlgoSwitch=OFF;
4.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 MAEDeployment.
4.4.2 Activation Verification (FDD)
1. Run the eNodeB command DSP CELLCSPCSTATUS. View the value of Cell
CSPC Status in the command output.
Expected result: The value is On.
2. Log in to the MAE-Access. Choose Monitor > Signaling Trace > Signaling Trace
Management. In the navigation tree of the displayed window, choose Trace Type >
LTE > User Performance Monitoring, and double-click Quality of Channel
Monitoring. In the displayed dialog box, select the target cells and create a task that
monitors the uplink RSRP of serving and neighboring cells.
Expected result: The serving and neighboring cells all report uplink SRS RSRP.
When creating a monitoring task, you must specify a random value or an S-TMSI, as shown in Figure
4-8. To query the random value allocated for UE access or the S-TMSI, run the DSP
ALLUEBASICINFO command for eNodeBs.
Figure 4-8 Creating a channel quality monitoring task
3. On the MAE-Access, choose Monitor > Signaling Trace > Signaling Trace
Management. In the navigation tree of the displayed window, choose Trace Type >
LTE > Cell Performance Monitoring, and double-click Usage of RB Monitoring.
In the displayed dialog box, select the target cells and create a task that monitors
resource block (RB) usage.
Expected result: Downlink Power off RB Num has a valid value.
4.4.3 Network Monitoring (FDD)
Use one of the following methods to observe the gains brought by CSPC:

Observe the counters listed in the following table before and after activating this
function. The changes in the counter values reflect function performance.
Table 4-9 Counters related to average downlink user-perceived data rates
Counter ID
Counter Name
1526728261
L.Thrp.bits.DL
1526729005
L.Thrp.bits.DL.LastTTI
1526729015
L.Thrp.Time.DL.RmvLastTTI
1526728997
L.Thrp.Time.Cell.DL.HighPrecision
1526728262
L.Thrp.Time.DL
1526728599 to
1526728630
L.ChMeas.PRB.DL.RANK1.MCS.0
to L.ChMeas.PRB.DL.RANK1.MCS.31
1526728631 to
1526728662
L.ChMeas.PRB.DL.RANK2.MCS.0
to L.ChMeas.PRB.DL.RANK2.MCS.31
1526727444 to
1526727475
L.ChMeas.PDSCH.MCS.0
1526727396 to
1526727411
L.ChMeas.CQI.DL.0
to L.ChMeas.CQI.DL.15
1526730141 to
1526730142
L.ChMeas.RI.Rank1
to L.ChMeas.RI.Rank2
to L.ChMeas.PDSCH.MCS.31

Counter ID
Counter Name
1526732737 to
1526732738
L.ChMeas.RI.Rank3
to L.ChMeas.RI.Rank4
Observe the counters listed in Table 4-10 to monitor the number of UEs for which
CSPC has taken effect.
In the counters, geometry factor is the result of the RSRP value of the local cell
divided by the sum of all RSRP values of the neighboring cells. A value greater than
or equal to 6 dB is a high geometry factor, and a value less than 6 dB is a low
geometry factor. After CSPC takes effect, a larger number of UEs with a low
geometry factor indicates a higher level of interference from neighboring cells to the
local cell and indicates higher CSPC gains.
Table 4-10 Average numbers of UEs with different levels of geometry factors in the local cell

Counter ID
Counter Name
1526739801
L.Traffic.HighGeometry.User.Avg
1526739802
L.Traffic.LowGeometry.User.Avg
Log in to the MAE-Access, and choose Monitor > Signaling Trace > Signaling
Trace Management. In the navigation tree of the displayed window, choose Trace
Type > LTE > Cell Performance Monitoring, and double-click CSPC (Cell)
Monitoring. In the displayed dialog box, select the target cells and create a task to
monitor the numbers of UEs experiencing different levels of interference from the
neighboring cells.
4.4.4 Possible Issues
CSPC does not introduce any new alarms.
If any of the following alarms is reported after CSPC is activated, handle the alarm according to
the alarm reference. If the alarm persists, deactivate CSPC for the cells served by the faulty
BBU.
Table 4-11 eNodeB alarms related to multi-BBU interconnection in the Cloud BB architecture
Alarm ID
Alarm Name
26116
Inter-NE Address Conflict
26310
Inter-BBU Optical Module Fault
26311
Inter-BBU Optical Module Not in Position
26314
Inter-BBU Port Failure
26315
Inter-BBU Port Connection Error
Table 4-12 USU alarms related to multi-BBU interconnection
Alarm ID
Alarm Name
26116
Inter-NE Address Conflict
27105
Interconnected Optical Module Fault
27106
Interconnected Optical Module Not Installed
27109
Inter-Port Failure
27110
Inter-Port Connection Error
If either of the following alarms is reported after CSPC is activated, handle the alarm according
to the alarm reference. In addition, check whether the BBPs where the centralized control nodes
are configured support centralized control for CSPC. If they do not, replace them with BBPs that
support centralized control for CSPC.
Table 4-13 eNodeB alarms related to BBPs
Alarm ID
Alarm Name
26245
Configuration Data Inconsistency
26203
Board Software Program Error
5
eCSPC (FDD)
5.1 Principles
5.1.1 eCSPC Procedure
Downlink power coordination takes effect on a cell and its neighboring cells that cause strong
interference to the cell. In eCSPC, eNodeBs make calculations for downlink power coordination
and exchange information over eX2 interfaces. eCSPC is controlled by the
CellCspcPara.CelleCspcSwitch parameter.
Figure 5-1
outlines the eCSPC procedure.
Figure 5-1 eCSPC procedure
1. Each eNodeB selects cells to form a cell set for interference coordination.
The cell set consists of 11 cells, including the local cell and 10 neighboring cells that
cause the strongest interference to the local cell. Each eNodeB selects the
neighboring cells from those that meet event A3 or A6 reporting conditions within a
set time period.
In non-CA scenarios, the selection is based on event A3. In CA scenarios, the
selection for the primary cell (PCell) is based on event A3 and the selection for
SCells is based on event A6.
2. Each eNodeB calculates the power adjustment requirement for each neighboring cell
of the local cell.
The calculation is based on the SINR values of UEs in the local cell, downlink
transmit power of the local cell, and RSRP for each neighboring cell. In the
calculation, the eNodeBs also consider rate fairness among UEs across the network.
The required power decrease for a neighboring cell positively correlates with the
level of interference from this neighboring cell.
3. The eNodeBs exchange power adjustment requirements.
The requirements are exchanged over eX2 interfaces.
4. The eNodeBs update downlink transmit power configurations.
An eNodeB calculates the latest downlink transmit power for a local cell based on
the received power adjustment requirements, active transmit power configuration for
this cell, and power requirement of this cell. The eNodeB takes the latest downlink
transmit power when the local cell load is higher than or equal to the value of the
CellCspcPara.eCspcPCAdjUeNumTh parameter. The cell load is represented by the
average number of activated UEs (that is, RRC_CONNECTED UEs for which
downlink data is buffered on the eNodeB side) in the downlink.
5. The eNodeBs update PA settings for UEs.
The eNodeBs check cell power changes every second and send RRC Connection
Reconfiguration messages to UEs to inform them of updated cell power
configurations.
If the latest downlink transmit power in a cell changes, the updated power takes
effect for UEs that will access the cell after the change and for UEs that are
downloading large volumes of data.
5.1.2 Scheduling for eCSPC
After eCSPC is enabled, each eNodeB collects information about interference from the
neighboring cells causing strong interference. The eNodeBs calculate the optimum transmit
power for each cell and adjust the downlink transmit power based on the
CellCspcPara.eCspcPCAdjRange parameter value.
The CellCspcPara.eCspcPCAdjRange parameter specifies the cell power adjustment range for
eCSPC. At most two values can be selected for this parameter. The values must be less than the
value of the CellDlpcPdschPa.PaPcOff parameter.
The following are examples of how the settings of the CellCspcPara.eCspcPCAdjRange
parameter take effect when the CellDlpcPdschPa.PaPcOff parameter is set to DB_3_P_A:

If the DB_6_P_A and DB_4DOT77_P_A options of the
CellCspcPara.eCspcPCAdjRange parameter are selected, the eNodeB uses the
following values for power adjustments: –6 dB, –4.77 dB, and –3 dB.

If the DB_6_P_A option of the CellCspcPara.eCspcPCAdjRange parameter is selected,
the eNodeB uses the following values for power adjustments: –6 dB and –3 dB.
5.1.3 RSRP Measurement for eCSPC
eCSPC supports only downlink RSRP measurement, which does not involve uplink SRS or
require time synchronization across the entire network. For details about downlink RSRP
measurement, see 4.1.4 RSRP Measurement for CSPC.
In eCSPC, the CellCspcPara.eCspcA3Offset parameter specifies the offset for event A3. A large
value of this parameter results in a low probability of UEs reporting event A3 and therefore a
small number of UEs considered as cell edge UEs. A small value of this parameter results in a
large number of cell edge UEs. The default value for this parameter is recommended, due to the
limited accuracy of RSRP measurement by UEs.
5.2 Network Analysis
5.2.1 Benefits
eCSPC efficiently reduces inter-cell interference and offers the following benefits:

Increases downlink user-perceived data rates in hotspot cells on a load-imbalanced
network.

Increases User Downlink Average Throughput of cell edge UEs across the network.
eCSPC is recommended when all the following conditions are met:

The average inter-RRU distance between eNodeBs is less than 500 m in densely
populated urban areas.

The average Downlink Resource Block Utilizing Rate is greater than 30% across the
network, the average number of active UEs in hotspot cells is greater than 3, and cells
are imbalanced in their loads.

The movement speeds of UEs on the live network are lower than 10 km/h.

Average CPU Load
of each BBP deployed with cells is less than 75%.
eCSPC affects throughput, depending on the following factors:

Inter-cell interference
The shorter the average inter-RRU distance between eNodeBs, the larger the gains
brought by eCSPC. An average inter-RRU distance of less than 500 m between
eNodeBs is recommended for eCSPC coverage areas.

Network load distribution
On live networks, cell load is represented by Downlink Resource Block Utilizing Rate in
individual cells. The more imbalanced the load between cells is, the more gains
eCSPC brings. Therefore, it is recommended that eCSPC be deployed in areas that
include hotspot cells.
Hotspot cells are cells with busy-hour Downlink Resource Block Utilizing Rate of greater than 40%.

Shape of the feature coverage area
The larger the feature coverage area is and the more regular the network topology in
the area is, the higher the feature gains are. Therefore, eCSPC is recommended for
contiguous coverage areas.

UE movement speed
eCSPC requires downlink RSRP measurements. It is recommended for networks
where most UEs move at speeds less than 10 km/h. If most UEs move at higher
speeds, eNodeBs cannot track fast interference changes.
5.2.2 Impacts
Network Impacts
In relaxed backhaul scenarios, when eCSPC and other features involving the coordination of
multiple eNodeBs (such as UL CoMP; see Cloud BB Overview) are enabled together, these features
share transmission bandwidths. If the transmission bandwidths are insufficient, the delays
increase and the gains of these features are affected.
On a heavily loaded network in a densely populated urban area, eCSPC increases the downlink
user-perceived data rate without affecting the downlink traffic volume of the entire network.
eCSPC can be used when the average Downlink Resource Block Utilizing Rate in the eCSPC coverage
area exceeds 30%, the average number of active UEs in hotspot cells is greater than 3, the interRRU distance between eNodeBs is less than 500 m, and no obvious inter-system interference is
present. eCSPC has the following impact on network performance:

When the average Downlink Resource Block Utilizing Rate in the eCSPC coverage area is
around 30%, the average downlink edge-user throughput increases by up to 10% and
User Downlink Average Throughput increases by up to 5% in hotspot cells.

When the average Downlink Resource Block Utilizing Rate in the eCSPC coverage area is
around 50%, the average downlink edge-user throughput increases by 5% to 20% and
User Downlink Average Throughput increases by 5% to 10% in hotspot cells.

In the eCSPC coverage area, the overall average cell throughput slightly decreases due
to the decrease in throughput of lightly loaded cells. However, the total downlink
traffic volume does not decrease, because the lightly loaded cells have sufficient radio
resources and can use more frequency-domain resources to compensate for the
increase in the transmission time.

To identify cell edge UEs, eCSPC requires UEs to measure the RSRP of neighboring
cells and report the measurement results to eNodeBs in event A3 or A6. The reporting
consumes uplink radio resources, affecting uplink performance. The eNodeBs deliver
transmit power configurations to the UEs through RRC Connection Reconfiguration
messages. Therefore, the amount of signaling load increases over the radio interface.
When CA is used, the increase in cell edge UE throughput depends on the coverage overlap between the PCell and
SCells. If the PCell and SCells cover the same area, CA does not affect the increase in cell edge UE throughput. If
the PCell and SCells do not completely overlap, the increase in cell edge UE throughput is determined by cell edge
UE throughput in the PCell rather than that in the SCells.
Function Impacts
Function Name
Function Switch
Reference
Description
Carrier
aggregation
None
Carrier
Aggregation
eCSPC mitigates interference
between intra-frequency cells
to increase the average UE
data rates and cell edge UE
data rates across the eCSPC
coverage area. eCSPC may
produce negative gains for CA
UEs causing strong
interference to other UEs. If
basic scheduling is used with
CA, the data rate of a CA UE
is defined as the total data
Function Name
Function Switch
Reference
Description
rate of the UE on all the
aggregated carriers. As a
result, CA UEs in eCSPCdisabled cells encounter lower
data rates than CA UEs in
eCSPC-enabled cells.
5.3 Requirements
5.3.1 Licenses
RAT
Feature ID
Feature Name
Model
Sales Unit
FDD
LOFD070208
Coordinated Scheduling
based Power Control
LT1SCSBPCC00 per Cell
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
Function
Name
Function Switch
Reference
CQI
adjustment
CqiAdjAlgoSwitch option of the Scheduling
CellAlgoSwitch.CqiAdjAlgoSwitch
parameter
Description
CQI adjustment enables the
IBLER of UEs to approach the
optimal target value after
eCSPC is activated.
Mutually Exclusive Functions
Function
Name
Reference
Description
High speed Cell.HighSpeedFlag
mobility
High Speed
Mobility
Cell.HighSpeedFlag
High Speed
Mobility
In high-speed
mobility scenarios,
cell load changes
so rapidly that
downlink power
adjustment cannot
promptly follow the
Ultra high
speed
mobility
Function Switch
Function
Name
Function Switch
Reference
Description
load changes.
Scheduling
eCSPC does not
work with adaptive
power allocation
for cell edge UEs.
Cell radius Cell.CellRadius
greater
than 15 km
Extended
Cell Range
Cell radius Cell.CellRadius
greater
than 100
km
Extended
Cell Range
eCSPC requires
that the radius of
each cell involved
should not exceed
15 km. If the radius
exceeds 15 km,
eCSPC does not
take effect.
CellAlgoSwitch.EicicSwitch being set to
Dynamic
TDM eICIC DYNAMIC
TDM eICIC
(FDD)
eCSPC and this
eICIC function are
suitable for
different scenarios
and therefore
cannot be
activated together.
Super
Combined
Cell (FDD)
eCSPC cannot be
activated together
with this function.
CDMA and AvoidCDMAInterfSwitch option of the
LTE Zero CellAlgoSwitch.AvoidInterfSwitch parameter
Bufferzone
(LTE FDD)
CDMA and
LTE Zero
Bufferzone
eCSPC cannot be
activated together
with this function.
GSM and GLZeroBufferZoneSwitch option of the
LTE Zero CellAlgoSwitch.DynSpectrumShareSwitch
Bufferzone parameter
GSM and
LTE Zero
Bufferzone
eCSPC cannot be
activated together
with this function.
Dynamic
Power
Sharing
Between
LTE Carriers
eCSPC cannot be
activated together
with this function.
Adaptive
power
allocation
for celledge UEs
Super
combined
cell
AdptCellEdgePwrAllocSw option of the
CellAlgoSwitch.CellDlCoverEnhanceSwitch
parameter
SuperCombCellSwitch option of the
CellAlgoSwitch.SfnAlgoSwitch parameter
Dynamic
Power
Sharing
Between
LTE
Carriers
LTE_DYN_POWER_SHARING_SW option of the
CellDynPowerSharing.DynamicPowerSharingSwitch
parameter
Extreme
power
LTE_EXTREME_POWER_SHARING_SW option Dynamic
Power
of the
Sharing
CellDynPowerSharing.DynamicPowerSharingSwitch
eCSPC cannot be
activated together
Function
Name
Function Switch
Reference
Description
sharing
parameter
Between
LTE Carriers
with this function.
Centralized LTE_CENTRAL_POWER_SHARING_SW option Smart 8T8R eCSPC cannot be
(FDD)
power
of the
activated together
CellDynPowerSharing.DynamicPowerSharingSwitch
sharing
with this function.
parameter
Static
Multiple
Beam
None
Massive
MIMO (FDD)
eCSPC cannot be
activated together
with this function.
Dynamic
Massive
Beam
None
Massive
MIMO (FDD)
eCSPC cannot be
activated together
with this function.
Intelligent
beam
shaping
MM_INTELLIGENT_BEAM_SHAPING_SW
option of the SectorSplitGroup.SectorSplitSwitch
parameter
Massive
MIMO (FDD)
eCSPC cannot be
activated together
with this function.
DL CoMP
with TM10
HomNet: the FDDHomNetDlCompSwitch option
of the CellAlgoSwitch.DlCompSwitch parameter
HetNet: the FDDHetNetDlCompSwitch option of
the CellAlgoSwitch.DlCompSwitch parameter
DL CoMP
(FDD)
DL CoMP
with TM9
Tm9JtSwitch option of the
CellAlgoSwitch.DlCompSwitch parameter
DL CoMP
(FDD)
eCSPC adjusts
power of different
cells to reduce
interference and is
suitable for heavyload scenarios.
The gain source
and application
scenarios of
eCSPC are
different from those
of joint
transmission.
RF
channel
dynamic
muting
RF_CHN_DYN_MUTING_SW option of the
CellRfChnDynMuting.RfChnDynMutingAlgoSwitch
parameter
Energy
Conservation
and
Emission
Reduction
5.3.3 Hardware
Base Station Models
The following base stations are compatible with this function:

3900 and 5900 series base stations

DBS3900 LampSite and DBS5900 LampSite
None
Boards


The following types of BBPs are compatible with eCSPC:

LBBPd

UBBPd

UBBPe

UBBPei

UBBPg
BBU3910C/BBU5900A is also compatible with eCSPC.
RF Modules
No requirements
5.3.4 Networking

In an eCSPC coverage area, all the cells must operate on the same frequency, have the
same bandwidth, use the same duplex mode, and primarily provide outdoor coverage.

IP Performance Monitor (PM) sessions of forward activation type are recommended
for delay detection. Avoid configuring an IP PM session of bidirectional activation
type at either end of an eX2 interface. That is because, when eCSPC is deployed,
eNodeBs will automatically create IP PM sessions to detect link status. If an IP PM
session of bidirectional activation type is added, it may conflict with an automatically
created session. If this is the case, the eX2 interface will fail to work properly.

Inter-BBU cells need to be planned to ensure inter-BBU route connectivity. eX2
interfaces between BBUs are required. For details, see eX2 Self-Management.

In an IP RAN, the one-way delay must be less than 8 ms.
5.3.5 Others
No requirements
5.4 Operation and Maintenance
Take the following precautions when deploying eCSPC:

PLMN information must be configured for the eNodeBs that serve the cells in the
eCSPC coverage area. If the PLMN information is not configured, routes cannot be set
up.

The CellCspcPara.eCspcPCAdjRange parameter must be set with the
CellDlpcPdschPa.PaPcOff parameter setting considered. Otherwise, eCSPC cannot be
enabled. A maximum of two values can be selected for the
CellCspcPara.eCspcPCAdjRange parameter. The values must be less than the value of
the CellDlpcPdschPa.PaPcOff parameter. The value range used for power adjustment
is dependent on the parameter settings:

If only one value is selected for the CellCspcPara.eCspcPCAdjRange
parameter, the eNodeB uses either this value or the value of the
CellDlpcPdschPa.PaPcOff parameter.

If two values are selected for the CellCspcPara.eCspcPCAdjRange
parameter, the eNodeB uses any of the two values and the value of the
CellDlpcPdschPa.PaPcOff parameter.
5.4.1 Data Configuration
5.4.1.1 Data Preparation
The CellCspcPara MO consists of cell-specific eCSPC parameters. The following table
describes the key parameters.
Parameter
Name
Parameter ID
Setting Notes
Cell eCSPC
Switch
CellCspcPara.CelleCspcSwitch
Set this parameter based on the network
plan.
eCSPC A3
Offset
CellCspcPara.eCspcA3Offset
Set this parameter based on the network
plan.
eCSPC
Power
Control
Adjustment
Range
CellCspcPara.eCspcPCAdjRange
Set this parameter based on the network
plan.
eCSPC PC
Adjustment
UE Number
Threshold
CellCspcPara.eCspcPCAdjUeNumTh Set this parameter based on the network
plan.
5.4.1.2 Using MML Commands
Activation Command Examples
Before using MML commands, refer to 5.2.2 Impacts and 5.3.2 Software and complete the parameter
configurations for related functions based on the impact, dependency, and mutually exclusive
relationships between the functions, as well as the actual network scenario.
Run the MOD CELLCSPCPARA command with the eCSPC A3 Offset and eCSPC Power
Control Adjustment Range parameters set to proper values and the Cell eCSPC Switch
parameter set to ON(On).
Five minutes after being enabled, eCSPC starts to coordinate inter-cell power for a cell and
neighboring cells that cause strong interference to this cell.

If the CellDlpcPdschPa.PaPcOff parameter is set to DB_3_P_A(-3 dB):
MOD CELLCSPCPARA: LocalCellId=0, eCspcA3Offset=-12,
CelleCspcSwitch=ON, eCspcPCAdjRange=DB_6_P_A-1&DB_4DOT77_P_A-1;

If the CellDlpcPdschPa.PaPcOff parameter is set to DB0_P_A(0 dB):
MOD CELLCSPCPARA: LocalCellId=0, eCspcA3Offset=-12,
CelleCspcSwitch=ON, eCspcPCAdjRange=DB_3_P_A-1&DB_1DOT77_P_A-1;
Optimization Command Examples
The CellCspcPara.eCspcPCAdjRange parameter helps determine the power adjustment range. The
values of this parameter must be less than the value of the CellDlpcPdschPa.PaPcOff parameter.
If the range includes three values, eCSPC achieves a finer power adjustment but consumes more
RRC signaling resources. If the range includes two values, eCSPC achieves a less fine power
adjustment but consumes fewer RRC signaling resources.
The CellCspcPara.eCspcPCAdjRange parameter specifies the smallest value in the power
adjustment range. The smaller the value, the higher the gains in hotspot cells and the greater the
loss in non-hotspot cells. An extremely small value may have a negative impact on the coverage
of non-hotspot cells.
The CellCspcPara.eCspcPCAdjUeNumTh parameter specifies the minimum required cell load for
power coordination by eCSPC to take effect.

In medium or high load scenarios with load imbalance, a smaller parameter value
results in a higher proportion of cells for which power coordination by eCSPC takes
effect. A higher proportion indicates higher gains. A larger parameter value leads to
lower gains.

In light load scenarios, a smaller parameter value results in a higher probability of cell
performance loss. A larger parameter value leads to a lower probability.
Deactivation Command Examples
The following provides only deactivation command examples. You can determine whether to
restore the settings of other parameters based on actual network conditions.
//Setting the cell-level eCSPC switch off
MOD CELLCSPCPARA: LocalCellId=0, CelleCspcSwitch=OFF;
5.4.1.3 Using the MAE-Deployment

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 MAEDeployment.
5.4.2 Activation Verification
To verify that eCSPC has been activated, perform the following steps:
1. Run the DSP CELLECSPCSTATUS command on the eNodeBs to query
information about the cooperating neighboring cells in eCSPC.
If information about cooperating neighboring cells is displayed, eCSPC has taken
effect. If no information about cooperating neighboring cells is displayed, eCSPC has
not taken effect.
2. On the MAE-Access, choose Monitor > Signaling Trace > Signaling Trace
Management. In the navigation tree of the displayed window, choose Trace Type >
LTE > Cell Performance Monitoring, and double-click CSPC (Cell) Monitoring.
Create a cell-level eCSPC monitoring task. If the result indicates a non-zero value of
User Num of UE PDSCH PA Consistent with Cell PDSCH PA as shown in Figure
5-2, eCSPC has taken effect on UEs. If the result indicates that the value of Downlink
PDSCH PA(0.01dB) is different from the baseline PA value, eCSPC has taken effect
in the cell.
Figure 5-2 Performance monitoring
3. On the MAE-Access, choose Monitor > Signaling Trace > Signaling Trace
Management. In the navigation tree of the displayed window, choose Trace Type >
LTE > Application Layer, and double-click Uu Interface Trace. Create a Uu
interface tracing task. If an RRC message as shown in Figure 5-3 is traced, PA has been
changed for the relevant UE.
Figure 5-3 Signaling message indicating a PA change
5.4.3 Network Monitoring
Use one of the following methods to observe the gains brought by eCSPC:

Observe the counters listed in Table 5-1 before and after activating this function. The
changes in the counter values reflect function performance.
Table 5-1 Counters related to average downlink user-perceived data rates
Counter ID
Counter Name
1526728261
L.Thrp.bits.DL
1526729005
L.Thrp.bits.DL.LastTTI
1526729015
L.Thrp.Time.DL.RmvLastTTI
1526728997
L.Thrp.Time.Cell.DL.HighPrecision
1526728262
L.Thrp.Time.DL
1526728599 to
1526728630
L.ChMeas.PRB.DL.RANK1.MCS.0
to L.ChMeas.PRB.DL.RANK1.MCS.31
1526728631 to
1526728662
L.ChMeas.PRB.DL.RANK2.MCS.0
to L.ChMeas.PRB.DL.RANK2.MCS.31
1526727444 to
1526727475
L.ChMeas.PDSCH.MCS.0
1526727396 to
1526727411
L.ChMeas.CQI.DL.0
to L.ChMeas.CQI.DL.15
1526730141 to
1526730142
L.ChMeas.RI.Rank1
to L.ChMeas.RI.Rank2
1526732737 to
L.ChMeas.RI.Rank3
to L.ChMeas.RI.Rank4
to L.ChMeas.PDSCH.MCS.31
Counter ID
Counter Name
1526732738

At least seven days before activating this function, ensure that the
BasedA3EdgeUserSwitch option of the
CellCounterParaGroup.CellCounterAlgoSwitch parameter has been selected and the
CellCounterParaGroup.EdgeUserA3Offset parameter has been set to -20. Observe the
counters listed in Table 5-2.
The CellCspcPara.eCspcA3Offset parameter specifies the A3 offset for eCSPC and the
CellCounterParaGroup.EdgeUserA3Offset parameter is used for counter measurement. The two
parameters do not affect each other, and it is recommended that the
CellCounterParaGroup.EdgeUserA3Offset parameter be set to a value equal to or slightly less than
the value of the CellCspcPara.eCspcA3Offset parameter.
Table 5-2 Counters related to downlink user-perceived data rates of cell edge UEs
Counter ID
Counter Name
1526729056 to
1526729065
L.Thrp.DL.BitRate.Samp.Index0
1526737755
L.Thrp.bits.DL.BorderUE
1526737758
L.Thrp.bits.DL.LastTTI.BorderUE
1526737759
L.Thrp.Time.DL.RmvLastTTI.BorderUE
1526741760
L.Thrp.Time.DL.BorderUE
1526737710
L.ChMeas.CQI.DL.BorderUE.Total
1526737711
L.ChMeas.CQI.DL.BorderUE.Num
1526741767
L.ChMeas.PRB.PDSCH.Avg.BorderUE
1526741888
L.Traffic.User.BorderUE.Avg
1526741889
L.Traffic.User.BorderUE.Max
1526741890
L.Traffic.User.IntraBoard.BorderUE.Avg
1526741891
L.Traffic.User.IntraBBUInterBoard.BorderUE.Avg
1526741892
L.Traffic.User.InterBBU.BorderUE.Avg
1526741768
L.Traffic.DL.SCH.TB.BorderUE
to L.Thrp.DL.BitRate.Samp.Index9

Counter ID
Counter Name
1526741770
L.Traffic.DL.SCH.ErrTB.Rbler.BorderUE
1526741769
L.Traffic.DL.SCH.ErrTB.Ibler.BorderUE
Observe the counters listed in Table 5-3 to monitor the percentage of UEs for which
eCSPC has taken effect.
Table 5-3 Counters related to cell algorithms and measurements
Counter ID
Counter Name
1526741772 to
1526741779
L.Traffic.PdschPA.Samp.Index0
to L.Traffic.PdschPA.Samp.Index7
5.4.4 Possible Issues
Run the DSP CELLECSPCSTATUS command on the eNodeB to query information about the
cooperating neighboring cells in eCSPC. The eX2 interface is faulty if either of the following
information is displayed in the command output:

The value of eCspc Data Link Status is UNAVAILABLE.

The value of eCspc Coordinate Cell Ex2 Link Delay Status is Yes.
For details about how to rectify the fault, see eX2 Self-Management.
6
Intra-eNodeB CSPC (FDD)
6.1 Principles
6.1.1 Intra-eNodeB CSPC Procedure
This function is controlled by the CellCspcPara.IntraEnbCspcSw parameter and must be
implemented between cells served by the same BBP.
Intra-eNodeB CSPC takes effect for UEs mainly under interference from intra-eNodeB intrafrequency neighboring cells. It reduces interference between the serving cell and the two intraeNodeB intra-frequency neighboring cells that cause the strongest interference to the serving
cell.
Figure 6-1
outlines the intra-eNodeB CSPC procedure.
Figure 6-1 Intra-eNodeB CSPC procedure
1. For each served cell, the eNodeB selects cells to form a cell set for interference
coordination.
The cell set consists of three intra-eNodeB intra-frequency cells, including the local
cell and the two neighboring cells that cause the strongest interference to the local
cell. The eNodeB selects the neighboring cells from those that meet event A3 or A6
reporting conditions within a set time period.
In non-CA scenarios, the selection is based on event A3. In CA scenarios, the
selection for the PCell is based on event A3 and the selection for SCells is based on
event A6.
2. The eNodeB determines the interference levels in the local cell and the neighboring
cells forming the cell set.
The eNodeB calculates the loads of these cells and exchanges the load information
and RSRP between the neighboring cells in the cell set.
3. The eNodeB reduces interference between the cells.
The eNodeB corrects the MCSs for downlink data transmission based on the UEreported channel quality indicators (CQIs), load status of the cells in the cell set, and
relative interference level. The correction increases downlink spectral efficiency.
The intra-eNodeB CSPC function takes effect when the serving cell meets the following
conditions:

The CQI reporting interval is greater than or equal to 40 ms.

The interference from intra-eNodeB intra-frequency neighboring cells is at least 6 dB
higher than that from inter-eNodeB neighboring cells.
6.1.2 Scheduling for Intra-eNodeB CSPC
Based on real-time information about the interference from the cells in the cell set, a UE
determines the difference between the interference status at the downlink scheduling time and
the interference status at the latest CSI reporting time. The UE adjusts the CSI accordingly.
Based on the adjusted CSI, the eNodeB selects an MCS that is more suitable for downlink data
transmission, improving the downlink spectral efficiency and data rates.
6.1.3 RSRP Measurement for Intra-eNodeB CSPC
RSRP measurement for intra-eNodeB CSPC is as follows:

If both intra-eNodeB CSPC and CSPC are enabled, intra-eNodeB CSPC uses uplink
RSRP measurement. For details, see 4.1.4 RSRP Measurement for CSPC.

If both intra-eNodeB CSPC and eCSPC are enabled, intra-eNodeB CSPC uses
downlink RSRP measurement. For details, see 5.1.3 RSRP Measurement for eCSPC.

If only intra-eNodeB CSPC is enabled, it uses downlink RSRP measurement. For nonCA scenarios, see 5.1.3 RSRP Measurement for eCSPC. For CA scenarios, two additional
parameters need to be set. Specifically, set the
NCellDlRsrpMeasPara.DlRsrpAutoNCellMeasSwitch parameter ON, and set the
NCellDlRsrpMeasPara.DlRsrpNCellMeasA6Offset parameter to its recommended value.
6.2 Network Analysis
6.2.1 Benefits
Intra-eNodeB CSPC efficiently reduces inter-cell interference and offers the following benefits:

Increases downlink user-perceived data rates in hotspot cells on a load-imbalanced
network.

Increases User Downlink Average Throughput of cell edge UEs across the network.
Intra-eNodeB CSPC is recommended when all the following conditions are met:

The average Downlink Resource Block Utilizing Rate is greater than 30% across the
network.

The movement speeds of UEs on the live network are lower than 10 km/h.

The number of sectors configured on a single eNodeB is not less than three.

Average CPU Load
of each BBP deployed with cells is less than 75%.
Intra-eNodeB CSPC affects throughput, depending on the following factors:

Inter-cell interference
It is recommended that intra-eNodeB CSPC be deployed in eNodeBs that each serve at
least three sectors.


If eNodeBs each serve more than three sectors, for example, in 2T6S or
4T6S multi-sector scenarios and in massive MIMO Static Multiple Beam
scenarios, User Downlink Average Throughput increases by about 1% to 5%.

If eNodeBs each serve three sectors, User Downlink Average Throughput
increases by 0% to 2%.
Network load distribution
On live networks, cell load is represented by Downlink Resource Block Utilizing Rate in
individual cells. The more imbalanced the load between cells is, the more gains intraeNodeB CSPC brings. Therefore, it is recommended that intra-eNodeB CSPC be
deployed in areas that include hotspot cells.
Hotspot cells are cells with busy-hour Downlink Resource Block Utilizing Rate of greater than 40%.

Overall network load
Overall network load is represented by the average downlink PRB usage of all cells in
the network.
If the interference level at the time of scheduling differs from the interference level at
the time of channel quality measurement, intra-eNodeB CSPC can select a more
accurate MCS than an MCS selected without intra-eNodeB CSPC. Therefore, intraeNodeB CSPC increases spectral efficiency. The increase first rises and then gradually
drops.

UE movement speed
Intra-eNodeB CSPC requires downlink or uplink RSRP measurements. It is
recommended for networks where most UEs move at speeds less than 10 km/h. If
most UEs move at higher speeds, eNodeBs cannot track fast interference changes.
6.2.2 Impacts
Network Impacts
On a heavily loaded network in a densely populated urban area, intra-eNodeB CSPC increases
the downlink user-perceived data rate without affecting the downlink traffic volume of the entire
network.
The reporting of event A3 or A6 for triggering intra-eNodeB CSPC consumes control channel
elements (CCEs) on the physical downlink control channel (PDCCH) and uplink PRBs,
adversely affecting uplink performance. The amount of the impact increases with the number of
UEs and the traffic volume of uplink services.
Function Impacts
Function
Name
Function Switch
Referenc Description
e
Adaptive
SFN/SDM
A
CellAlgoSwitch.SfnUlSchSwitch or
CellAlgoSwitch.SfnDlSchSwitch being set
to ADAPTIVE
SFN
The
CellAlgoSwitch.SfnDlSchSwit
ch parameter cannot be set to
ADAPTIVE. If it is so, the
intra-eNodeB CSPC function
Function
Name
Function Switch
Referenc Description
e
does not take effect.
Massive
MIMO
(FDD)
Static
Multiple
Beam
None
If two beams are generated
after a split, Static Multiple
Beam is compatible with
intra-eNodeB CSPC only
when intelligent beam
scheduling is enabled.
Intelligent
beam
shaping
MM_INTELLIGENT_BEAM_SHAPING_S Massive
MIMO
W option of the
(FDD)
SectorSplitGroup.SectorSplitSwitch
parameter
High
speed
mobility
Cell.HighSpeedFlag
High
Speed
Mobility
Intra-eNodeB CSPC is not
recommended in high-speed
mobility scenarios, where the
rapid changes in network
interference characteristics
affect the accuracy of
downlink interference
coordination.
Ultra high
speed
mobility
Cell.HighSpeedFlag
High
Speed
Mobility
Intra-eNodeB CSPC is not
recommended in high-speed
mobility scenarios, where the
rapid changes in network
interference characteristics
affect the accuracy of
downlink interference
coordination.
Cell radius Cell.CellRadius
greater
than 15
km
Extended
Cell
Range
Intra-eNodeB CSPC is
suitable for densely
populated urban areas. It is
not recommended for cells
with a radius greater than 15
km.
Cell radius Cell.CellRadius
greater
than 100
km
Extended
Cell
Range
Intra-eNodeB CSPC is
suitable for densely
populated urban areas. It is
not recommended for cells
with a radius greater than
100 km.
Intelligent beam shaping is
not compatible with intraeNodeB CSPC when two
beams are generated after a
split.
Function
Name
Function Switch
Referenc Description
e
Data
learningbased
downlink
intelligent
AMC
DL_INTEL_AMC_SELECTION_SW
option of the
CellIntelAmcConfig.IntelligentAmcSwitch
parameter
eMIMO
(FDD)
If data learning-based
downlink intelligent AMC is
enabled and then intraeNodeB CSPC is enabled,
the MCS correction function
and further the gains of intraeNodeB CSPC will be
affected.
6.3 Requirements
6.3.1 Licenses
RAT
Feature ID
Feature Name
Model
Sales Unit
FDD
LOFD070208
Coordinated Scheduling
based Power Control
LT1SCSBPCC00 per Cell
6.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
Function
Name
Function Switch
Reference
CQI
adjustment
CqiAdjAlgoSwitch option of the Scheduling
CellAlgoSwitch.CqiAdjAlgoSwitch
parameter
Description
CQI adjustment enables the
IBLER of UEs to approach the
optimal target value after intraeNodeB CSPC is activated.
Mutually Exclusive Functions
Function
Name
Function Switch
CellAlgoSwitch.EicicSwitch being set to
Dynamic
TDM eICIC DYNAMIC
Reference
Description
TDM eICIC
(FDD)
Intra-eNodeB
CSPC and this
eICIC function are
Function
Name
Function Switch
Reference
Description
suitable for
different scenarios
and therefore
cannot be
activated together.
Super
combined
cell
SuperCombCellSwitch option of the
CellAlgoSwitch.SfnAlgoSwitch parameter
DdCellGroup.DdBandwidth
Flexible
bandwidth
based on
overlapping
carriers
Super
Combined
Cell (FDD)
Flexible
Bandwidth
based on
Overlap
Carriers
(FDD)
Intra-eNodeB
CSPC cannot be
activated together
with this function.


If a
Double
Deck
cell
group
uses a
nonstandard
bandwid
th of 5.7,
7.3, 7.6,
8.6, or
8.9
MHz,
intraeNodeB
CSPC
cannot
be
activate
d in
either of
the cells
in the
group.
If a
Double
Deck
cell
group
uses a
nonstandard
bandwid
th of 4,
12.2, or
Function
Name
Function Switch
Reference
Description

CDMA and AvoidCDMAInterfSwitch option of the
CDMA and
17.1
MHz,
intraeNodeB
CSPC
cannot
be
activate
d in the
cell with
a
standard
bandwid
th of 3
MHz in
the
group.
If a
Double
Deck
cell
group
uses a
nonstandard
bandwid
th of
27.6 or
28.5
MHz,
intraeNodeB
CSPC
cannot
be
activate
d in the
cell with
a
standard
bandwid
th of 10
MHz in
the
group.
Intra-eNodeB
Function
Name
Function Switch
CellAlgoSwitch.AvoidInterfSwitch parameter
LTE Zero
Bufferzone
(LTE FDD)
Reference
Description
LTE Zero
Bufferzone
CSPC cannot be
activated together
with this function.
Intra-eNodeB
CSPC cannot be
activated together
with these
functions.
GSM and
LTE
dynamic
power
sharing
(LTE)
CellAlgoSwitch.GLPwrShare
GSM and
LTE
Dynamic
Power
Sharing
UMTS and
LTE
Dynamic
Power
Sharing
(LTE FDD)
UMTS_LTE_DYN_POWER_SHARING_SW
option of the
CellDynPowerSharing.DynamicPowerSharingSwitch
parameter
UMTS and
LTE
Dynamic
Power
Sharing
GLDynSpectrumShareSwitch option of the
GSM and
CellAlgoSwitch.DynSpectrumShareSwitch
LTE FDD
Dynamic
parameter
Spectrum
Sharing
(LTE FDD)
GSM and
LTE FDD
Dynamic
Spectrum
Sharing
GLZeroBufferZoneSwitch option of the
GSM and
CellAlgoSwitch.DynSpectrumShareSwitch
LTE Zero
Bufferzone parameter
GSM and
LTE Zero
Bufferzone
Intra-eNodeB
CSPC cannot be
activated together
with this function.
Dynamic
Massive
Beam
Massive
MIMO (FDD)
Intra-eNodeB
CSPC cannot be
activated together
with this function.
Energy
Conservation
and
Emission
Reduction
None
None
RF channel RF_CHN_DYN_MUTING_SW option of the
CellRfChnDynMuting.RfChnDynMutingAlgoSwitch
dynamic
muting
parameter
6.3.3 Hardware
Base Station Models
The following base stations are compatible with this function:

3900 and 5900 series base stations

DBS3900 LampSite and DBS5900 LampSite

The following types of BBPs are compatible with intra-eNodeB CSPC:
Boards


LBBPd

UBBPd

UBBPe

UBBPei

UBBPg
BBU3910C/BBU5900A is also compatible with intra-eNodeB CSPC.
RF Modules
No requirements
6.3.4 Networking
In an intra-eNodeB CSPC coverage area, all the cells must operate on the same frequency, have
the same bandwidth, work in the same duplex mode, and primarily provide outdoor coverage.
6.3.5 Others
No requirements
6.4 Operation and Maintenance
6.4.1 Data Configuration
6.4.1.1 Data Preparation
The CellCspcPara MO consists of cell-specific intra-eNodeB CSPC parameters. The following
table describes the key parameters.
Parameter Name Parameter ID
Setting Notes
Intra Enodeb
Cspc Switch
CellCspcPara.IntraEnbCspcSw Set this parameter based on the network plan.
eCSPC A3
Offset
CellCspcPara.eCspcA3Offset
Set this parameter based on the network plan.
The NCellDlRsrpMeasPara MO consists of cell-level parameters related to downlink RSRP
measurements on neighboring cells. The following table describes the key parameters.
Parameter
Name
Parameter ID
Setting Notes
Parameter
Name
Parameter ID
Setting Notes
NCellDlRsrpMeasPara.DlRsrpAutoNCellMeasSwitch This parameter is required in
DL RSRP
Auto NCell
intra-BBU CA scenarios. The
value ON is recommended.
Measurement
Switch
NCellDlRsrpMeasPara.DlRsrpNCellMeasA6Offset
DL RSRP
NCell
Measurement
A6 Offset
This parameter is required in
intra-BBU CA scenarios. Set
this parameter to its
recommended value.
6.4.1.2 Using MML Commands
Activation Command Examples
Before using MML commands, refer to 6.2.2 Impacts and 6.3.2 Software and complete the parameter
configurations for related functions based on the impact, dependency, and mutually exclusive
relationships between the functions, as well as the actual network scenario.



Do not set the CellDlschAlgo.MbsfnSfCfg parameter.
Intra-eNodeB CSPC does not take effect in any of the following scenarios:
 The DetectRank2AdjSwitch option of the
CellDlschAlgo.DlRankDetectSwitch parameter is selected.
 The UsUeGuaranteeSwitch option of the CellUSParaCfg.UsAlgoSwitch
parameter is selected.
 The CellAlgoSwitch.SfnDlSchSwitch parameter is set to ADAPTIVE.
Five minutes after being enabled, intra-eNodeB CSPC takes effect in the serving cell
and the neighboring cells that cause the strongest interference to the serving cell.
During intra-eNodeB CSPC, the eNodeB adjusts downlink MCSs for UEs.
//Configuring MBSFN subframes and the policy of increasing the number of RBs
to lower the MCS index
MOD CELLDLSCHALGO: LocalCellId=0,
RBPriMcsSelectStrategy=MULTIUSR_LOWMCSLIMIT_STRATEGY, MbsfnSfCfg=SubFrame00&SubFrame1-0&SubFrame2-0&SubFrame3-0&SubFrame4-0&SubFrame5-0&SubFrame60&SubFrame7-0&SubFrame8-0&SubFrame9-0;
//Setting the A3 offset and setting the intra-eNodeB CSPC switch on
MOD CELLCSPCPARA: LocalCellId=0, eCspcA3Offset=-12, IntraEnbCspcSw=ON;
//Turning on the switch for downlink RSRP measurements on neighboring cells
and setting the A6 offset for the measurements in intra-BBU CA scenarios
MOD NCELLDLRSRPMEASPARA: LocalCellId=0, DlRsrpAutoNCellMeasSwitch=ON,
DlRsrpNCellMeasA6Offset=-12;
Optimization Command Examples
N/A
Deactivation Command Examples
The following provides only deactivation command examples. You can determine whether to
restore the settings of other parameters based on actual network conditions.
//Setting the intra-eNodeB CSPC switch off
MOD CELLCSPCPARA:LocalCellId=0, IntraEnbCspcSw=OFF;
6.4.1.3 Using the MAE-Deployment

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 MAEDeployment.
6.4.2 Activation Verification
Run the DSP CELLINTRAENBCSPCSTATUS command on the eNodeB to query information
about the cooperating neighboring cells in intra-eNodeB CSPC.
If information about cooperating neighboring cells is displayed, intra-eNodeB CSPC has taken
effect. If no information about cooperating neighboring cells is displayed, intra-eNodeB CSPC
has not taken effect.
6.4.3 Network Monitoring
Use one of the following methods to observe the gains brought by intra-eNodeB CSPC:

Observe the counters listed in Table 6-1 before and after activating this function. The
changes in the counter values reflect function performance.
Table 6-1 Counters related to average downlink user-perceived data rates
Counter ID
Counter Name
1526728261
L.Thrp.bits.DL
1526729005
L.Thrp.bits.DL.LastTTI
1526729015
L.Thrp.Time.DL.RmvLastTTI
1526728997
L.Thrp.Time.Cell.DL.HighPrecision

Counter ID
Counter Name
1526728262
L.Thrp.Time.DL
1526728599 to
1526728630
L.ChMeas.PRB.DL.RANK1.MCS.0
to L.ChMeas.PRB.DL.RANK1.MCS.31
1526728631 to
1526728662
L.ChMeas.PRB.DL.RANK2.MCS.0
to L.ChMeas.PRB.DL.RANK2.MCS.31
1526727444 to
1526727475
L.ChMeas.PDSCH.MCS.0
1526727396 to
1526727411
L.ChMeas.CQI.DL.0
to L.ChMeas.CQI.DL.15
1526730141 to
1526730142
L.ChMeas.RI.Rank1
to L.ChMeas.RI.Rank2
1526732737 to
1526732738
L.ChMeas.RI.Rank3
to L.ChMeas.RI.Rank4
to L.ChMeas.PDSCH.MCS.31
At least seven days before activating this function, ensure that the
BasedA3EdgeUserSwitch option of the
CellCounterParaGroup.CellCounterAlgoSwitch parameter has been selected and the
CellCounterParaGroup.EdgeUserA3Offset parameter has been set to -20. Observe the
counters listed in Table 6-2.
The CellCspcPara.eCspcA3Offset parameter specifies the A3 offset for intra-eNodeB CSPC and the
CellCounterParaGroup.EdgeUserA3Offset parameter is used for counter measurement. The two
parameters do not affect each other, and it is recommended that the
CellCounterParaGroup.EdgeUserA3Offset parameter be set to a value equal to or slightly less than
the value of the CellCspcPara.eCspcA3Offset parameter.
Table 6-2 Counters related to downlink user-perceived data rates of cell edge UEs
Counter ID
Counter Name
1526729056 to
1526729065
L.Thrp.DL.BitRate.Samp.Index0
1526737755
L.Thrp.bits.DL.BorderUE
1526737759
L.Thrp.Time.DL.RmvLastTTI.BorderUE
1526741760
L.Thrp.Time.DL.BorderUE
1526737710
L.ChMeas.CQI.DL.BorderUE.Total
to L.Thrp.DL.BitRate.Samp.Index9

Counter ID
Counter Name
1526737711
L.ChMeas.CQI.DL.BorderUE.Num
1526741767
L.ChMeas.PRB.PDSCH.Avg.BorderUE
1526741888
L.Traffic.User.BorderUE.Avg
1526741889
L.Traffic.User.BorderUE.Max
1526741890
L.Traffic.User.IntraBoard.BorderUE.Avg
1526741891
L.Traffic.User.IntraBBUInterBoard.BorderUE.Avg
1526741892
L.Traffic.User.InterBBU.BorderUE.Avg
1526741768
L.Traffic.DL.SCH.TB.BorderUE
1526741770
L.Traffic.DL.SCH.ErrTB.Rbler.BorderUE
1526741769
L.Traffic.DL.SCH.ErrTB.Ibler.BorderUE
Observe the counters listed in Table 6-3 to monitor the percentage of UEs for which
intra-eNodeB CSPC has taken effect.
Table 6-3 Counters related to cell performance measurements
7
Counter ID
Counter Name
1526742073
L.ChMeas.PRB.DL.IntraEnbCspc.Used.Avg
Parameters
The following hyperlinked EXCEL files of parameter documents match the software version
with which this document is released.

Node Parameter Reference:

eNodeBFunction Parameter Reference:

eNodeBFunction Used Reserved Parameter List:
contains device and transport parameters.
contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and
radio resource management.
use and those that have been disused.
contains the reserved parameters that are in
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 TDLOFD001016.
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.
8
Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.

Node Performance Counter Summary:

eNodeBFunction Performance Counter Summary:
contains device and transport counters.
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.
9
Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
10
Reference Documents
1. 3GPP TS 36.331,"Radio Resource Control (RRC);Protocol specification"
2.
Synchronization
3.
Scheduling
4.
eX2 Self-Management
5.
USU3900-based Multi-BBU Interconnection
6.
USU3910-based Multi-BBU Interconnection
7.
Cloud BB Overview
8.
Adaptive ICIC
9.
VoLTE
10. Carrier Aggregation
11. SFN
12. eMTC
13. RAN Sharing
14. Dynamic Power Sharing Between LTE Carriers
15. High Speed Mobility
16. Extended Cell Range
17. TDM eICIC (FDD)
18. Super Combined Cell (FDD)
19. Flexible Bandwidth based on Overlap Carriers (FDD)
20. GSM and LTE Zero Bufferzone
21. CDMA and LTE Zero Bufferzone
22. DL CoMP (FDD)
23. eMIMO (FDD)
24. GSM and LTE FDD Dynamic Spectrum Sharing
25. GSM and LTE Dynamic Power Sharing
26. Massive MIMO (FDD)
27. UL CoMP
28. UMTS and LTE Dynamic Power Sharing
29. Virtual 4T4R (FDD)
30. NB-IoT Basics (FDD)
31. Superior Uplink Coverage (FDD)
32. LTE FDD and NR Spectrum Sharing
33. LTE FDD and NR Uplink Spectrum Sharing
34. Smart 8T8R (FDD)
35. Energy Conservation and Emission Reduction