CSPC (eRAN12.1 03)

eRAN
CSPC Feature Parameter

Description
Issue 03
Date 2017-08-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2017. 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: http://www.huawei.com
Email: support@huawei.com
Issue 03 (2017-08-30) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
eRAN
CSPC Feature Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Differences Between eNodeB Types.............................................................................................................................. 4
2 Overview......................................................................................................................................... 5
2.1 Background.....................................................................................................................................................................5
2.2 Introduction.................................................................................................................................................................... 6
2.3 Benefits........................................................................................................................................................................... 7
2.4 Architecture.................................................................................................................................................................... 7
3 CSPC.............................................................................................................................................. 11
3.1 Clustering for CSPC..................................................................................................................................................... 11
3.2 CSPC Procedure........................................................................................................................................................... 13
3.3 Scheduling for CSPC....................................................................................................................................................14
3.4 RSRP Measurement for CSPC..................................................................................................................................... 14
4 eCSPC............................................................................................................................................ 17
4.1 eCSPC Procedure......................................................................................................................................................... 17
4.2 Scheduling for eCSPC.................................................................................................................................................. 18
4.3 RSRP Measurement for eCSPC................................................................................................................................... 19
5 Intra-eNodeB CSPC.....................................................................................................................20
5.1 Intra-eNodeB CSPC Procedure.................................................................................................................................... 20
5.2 Scheduling for Intra-eNodeB CSPC.............................................................................................................................21
5.3 RSRP Measurement for Intra-eNodeB CSPC.............................................................................................................. 21
6 Related Features...........................................................................................................................22
7 Network Impact........................................................................................................................... 26
7.1 System Capacity........................................................................................................................................................... 26
7.2 Network Performance...................................................................................................................................................26
8 Engineering Guidelines for CSPC........................................................................................... 29

8.1 When to Use................................................................................................................................................................. 29
8.2 Required Information................................................................................................................................................... 29
Issue 03 (2017-08-30) Huawei Proprietary and Confidential ii

eRAN
8.3 Planning........................................................................................................................................................................ 33
8.4 Deployment.................................................................................................................................................................. 34
8.4.1 Process....................................................................................................................................................................... 34
8.4.2 Requirements............................................................................................................................................................. 34
8.4.3 Precautions.................................................................................................................................................................35
8.4.4 Data Preparation and Feature Activation...................................................................................................................35
8.4.4.1 Data Preparation..................................................................................................................................................... 35
8.4.4.2 Activation............................................................................................................................................................... 39
8.4.5 Activation Observation..............................................................................................................................................41
8.4.6 Deactivation...............................................................................................................................................................42
8.5 Performance Monitoring...............................................................................................................................................42
8.6 Parameter Optimization................................................................................................................................................ 44
8.7 Possible Issues.............................................................................................................................................................. 45
9 Engineering Guidelines for eCSPC......................................................................................... 46

9.1 When to Use................................................................................................................................................................. 46
9.2 Required Information................................................................................................................................................... 46
9.3 Planning........................................................................................................................................................................ 49
9.4 Deployment.................................................................................................................................................................. 50
9.4.1 Requirements............................................................................................................................................................. 50
9.4.2 Precautions.................................................................................................................................................................50
9.4.3 Data Preparation and Feature Activation...................................................................................................................51
9.4.3.1 Data Preparation..................................................................................................................................................... 51
9.4.3.2 Activation............................................................................................................................................................... 51
9.4.4 Activation Observation..............................................................................................................................................52
9.4.5 Deactivation...............................................................................................................................................................53
9.5 Performance Monitoring...............................................................................................................................................54
9.6 Parameter Optimization................................................................................................................................................ 57
9.7 Possible Issues.............................................................................................................................................................. 57
10 Engineering Guidelines for Intra-eNodeB CSPC............................................................... 58

10.1 When to Use............................................................................................................................................................... 58
10.2 Required Information................................................................................................................................................. 58
10.3 Planning...................................................................................................................................................................... 61
10.4 Deployment................................................................................................................................................................ 62
10.4.1 Requirements........................................................................................................................................................... 62
10.4.2 Data Preparation and Feature Activation.................................................................................................................62
10.4.2.1 Data Preparation................................................................................................................................................... 62
10.4.2.2 Activation............................................................................................................................................................. 63
10.4.3 Activation Observation............................................................................................................................................63
10.4.4 Deactivation.............................................................................................................................................................64
10.5 Performance Monitoring.............................................................................................................................................64
10.6 Parameter Optimization.............................................................................................................................................. 67
10.7 Possible Issues............................................................................................................................................................ 67
Issue 03 (2017-08-30) Huawei Proprietary and Confidential iii

eRAN
11 Parameters................................................................................................................................... 68
12 Counters...................................................................................................................................... 97
13 Glossary..................................................................................................................................... 108
14 Reference Documents............................................................................................................. 109
Issue 03 (2017-08-30) Huawei Proprietary and Confidential iv

eRAN
CSPC Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes LOFD-070208 Coordinated Scheduling based Power Control,
including its technical principles, related features, network impact, and engineering
guidelines.
The Coordinated Scheduling based Power Control feature includes the following functions:
l CSPC in networks deployed using a centralized Cloud BB architecture (referred to as
CSPC in this document)
l CSPC in IP RANs (referred to as eCSPC in this document)
l Intra-eNodeB CSPC
In this document, a micro cell is served by a micro eNodeB or by a distant low-power remote
radio unit (RRU), such as an RRU3220E, in a macro eNodeB. Micro cells are used for filling
coverage holes or offloading traffic in the coverage areas of macro cells.
Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to
the corresponding software release. For future software releases, refer to the corresponding
updated product documentation.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
Issue 03 (2017-08-30) Huawei Proprietary and Confidential 1

eRAN
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
eRAN12.1 03 (2017-08-30)
This issue includes the following changes.
Change Change Description Parameter Affected Entity

Type Change
Feature None None N/A

change
Editorial Added the conditions for the None N/A

change intra-eNodeB CSPC function to
take effect. For details, see 5.1
Intra-eNodeB CSPC
Procedure.
Revised descriptions in this None N/A

document.
eRAN12.1 02 (2017-04-26)

Type Change

change
Editorial Revised 8.1 When to Use and None N/A

change 8.4.4.1 Data Preparation.
Added the mutual exclusivity None N/A

between CSPC and adaptive
power allocation for cell edge
UEs. For details, see 6 Related
Features.
eRAN12.1 01 (2017-03-08)

eRAN

Type Change

change
Editorial Revised descriptions in this None N/A

change document.
eRAN12.1 Draft A (2016-12-30)

Draft A (2016-12-30) of eRAN12.1 introduces the following changes to Issue 03
(2016-06-30) of eRAN11.1.
Change Change Description Parameter Change Affected

Type Entity
Feature l Added the impact of eMTC None Macro, micro,

change on the Coordinated and LampSite
Scheduling based Power eNodeBs
Control feature. For details,
see Impacted Features.
l Added support for eCSPC
through the X2 interface. For
details, see 2.4 Architecture.
l Added the board UBBPei and
updated the descriptions of:
Hardware Planning in
8.3 Planning
Hardware in 8.4.2
Requirements
Hardware in 9.4.1
Requirements
Hardware in 10.4.1
Requirements
Editorial None None N/A

change

eRAN
1.4 Differences Between eNodeB Types

Feature Support by Macro, Micro, and LampSite eNodeBs
Feature ID Feature Supported by Supported by Supported by
Name Macro Micro LampSite
eNodeBs eNodeBs eNodeBs
LOFD-07020 Coordinated Yes Yes Yes

8 Scheduling
based Power
Control
"Micro eNodeBs" refers to the following models:

l BTS3911E
l BTS3912E
Function Implementation in Macro, Micro, and LampSite eNodeBs

Function Supported by Supported by Supported by
Macro eNodeBs Micro eNodeBs LampSite
eNodeBs
CSPC Yes No Yes
eCSPC Yes Yes Yes
Intra-eNodeB CSPC Yes Yes Yes

eRAN
CSPC Feature Parameter Description 2 Overview
2 Overview
2.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
2-1.
Figure 2-1 Intra-frequency cells in a densely populated urban area
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.
NOTE
Cell edge UEs are defined in either of the following two ways:
l By geographical location: Cell edge UEs are UEs that are located at the geographical edge of a
cell. You are advised to use the geographical location to determine whether a UE is a cell edge UE.
l 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.
Inter-cell power coordination can be performed in the frequency and time domains.

eRAN
l In the frequency domain, adaptive inter-cell interference coordination (ICIC) works. For
details, see Adaptive ICIC Feature Parameter Description.
l In the time domain, the feature described in this document works.
2.2 Introduction
The Coordinated Scheduling based Power Control feature coordinates transmit power
configurations between cells in the time domain. Figure 2-2 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 2-2 Example of time-domain transmit power coordination
NOTE
Currently, the CSPC function supports only full- and zero-power transmission. 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.
Coordinated Scheduling based Power Control includes the CSPC, eCSPC, and intra-eNodeB
CSPC functions. These functions are used in the scenarios listed in Table 2-1.
Table 2-1 Deployment requirements and application scenarios

Function Deployment Requirements Application Scenarios
CSPC Universal switching units An operator requires fast interference

(USUs) and centralized control coordination.
nodes must be deployed.
eCSPC USUs and centralized control An operator allows interference

nodes are not required. coordination at longer time intervals.
Intra-eNodeB USUs and centralized control An operator requires interference

CSPC nodes are not required. coordination between intra-eNodeB
intra-frequency cells.
These functions can be deployed individually or in combinations. Note that:

l CSPC and eCSPC cannot be deployed simultaneously.
l 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.

eRAN
2.3 Benefits
Coordinated Scheduling based Power Control effectively reduces inter-cell interference and
offers the following benefits:
l Increases downlink user-perceived data rates in hotspot cells on a load-unbalanced
network.
l Increases the user-perceived throughput of cell edge UEs across the network.
l Reduces handover failures and service drops caused by downlink interference.
2.4 Architecture
CSPC
The CSPC function is implemented on the U2000, USUs, eNodeBs, centralized control nodes,
and UEs. It requires time synchronization with an accuracy of 1.5 s across the network.
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 2-3, Figure 2-4, and Figure 2-5 show the network architectures for
CSPC.
Figure 2-3 Network architecture for CSPC (macro network)

eRAN
Figure 2-4 Network architecture for CSPC (HetNet)
NOTE
The micro cell is served by a distant low-power RRU, rather than by a micro eNodeB.
Figure 2-5 Network architecture for CSPC (LampSite network)
The following describes the functions of each entity involved in CSPC:

l 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.
l 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.
l 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.

eRAN
A centralized clustering node implements cell clustering and maps a cluster to only
one specified centralized scheduling node. For details about clustering, see 3.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. Centralized
scheduling nodes are evenly distributed on a Cloud BB network.
For more details about centralized clustering nodes and centralized scheduling nodes, see
Cloud BB Overview Feature Parameter Description.
On a Cloud BB network, the CSPC function can be deployed for cells of the same
duplex mode or different duplex modes.
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 2-6 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 Hardware Planning
in 8.3 Planning.
Figure 2-6 CSPC deployment for cells in the same duplex mode on a Cloud BB
network
If CSPC is deployed for FDD cells and TDD cells served by separate BBUs in a
Cloud BB network, two centralized clustering nodes must be deployed with one
used for FDD cells and the other for TDD cells. Each of the centralized clustering
nodes supports a maximum of 12 centralized scheduling nodes.
l 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.
In a Cloud BB network, if FDD cells and TDD cells are served by separate BBUs, CSPC
can be deployed for both FDD and TDD cells. The technical principles and deployment
method are the same as those for CSPC deployment in cells in the same duplex mode.
For details, see this document and CSPC Feature Parameter Description in eRAN TDD
Feature Documentation.

eRAN
For details about Cloud BB networking, see Cloud BB Overview Feature Parameter
Description and USU3910-based Multi-BBU Interconnection Feature Parameter
Description.
l U2000
On the U2000, users can query cell power configurations and observe performance
counters to review the improvements brought by CSPC. For details, see 8.5
Performance Monitoring.
eCSPC
The eCSPC function does not require time synchronization across the entire network and can
be directly deployed on a network. Figure 2-7 shows the network architecture for eCSPC. It
works in a macro network or a HetNet.
Figure 2-7 Network architecture for eCSPC
The following describes the functions of entities and interfaces involved in eCSPC:
l 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.
l 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.
l eX2
The eX2 interface is a logical interface between eNodeBs for service coordination. For
details, see eX2 Self-Management Feature Parameter Description.
l U2000
On the U2000, users can query cell power configurations and observe performance
counters to review the improvements brought by eCSPC. For details, see 9.5
Performance Monitoring.
Intra-eNodeB CSPC
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.

eRAN
CSPC Feature Parameter Description 3 CSPC
3 CSPC
3.1 Clustering for CSPC

Definition of a Cluster
A cluster is a contiguous area covered by cells that support CSPC, as shown in Figure 3-1.
Clusters are introduced to deal with limited baseband processing capabilities and scheduling
delays.
Figure 3-1 Definition of a cluster
Cluster-Level CSPC Triggering

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 3-2 illustrates when a cluster enters or exits CSPC.

eRAN
Figure 3-2 Evaluation of entry into or exit from CSPC for a cluster
l 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.
l 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:
l The geographical coverage of the cells is continuous.
l The average inter-RRU distance is less than 500 m in densely populated urban areas.
l The cells operate on the same frequency, have identical bandwidths, and use the same
duplex mode.
l 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. It is recommended that a cluster include 72 cells at most.
The following are suggestions for clustering:
l Deploy hotspot cells, whose busy-hour downlink PRB usage is greater than 40%, in the
center of a cluster.
l Deploy lightly-loaded cells at the edges of the cluster.
l Make the shape of the cluster close to a circle, in order to maximize feature gains.
NOTE
Power is not coordinated between cells in different CSPC clusters.

eRAN
3.2 CSPC Procedure

Figure 3-3 illustrates the sequence of transmissions involved in CSPC.
Figure 3-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 3-4 outlines the CSPC procedure.
Figure 3-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.

eRAN
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.
3.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 MAC 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 Feature Parameter Description.
3.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.
l 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.

eRAN
l 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.
RSRP measurement for cell edge UEs is classified into uplink RSRP measurement and
downlink RSRP measurement. Figure 3-5 and Figure 3-6 illustrate RSRP measurements on a
macro or LampSite network and on a HetNet, respectively.
Currently, the CSPC function supports only uplink RSRP measurement, which is now based
on sounding reference signal (SRS). Specify this type of measurement by setting
CspcAlgoPara.CspcRsrpMeasMode to RSRP_UL.
Figure 3-5 RSRP measurement (macro or LampSite network)
NOTE
RSRP measurement on a LampSite network is the same as that on a macro network.
Figure 3-6 RSRP measurement (HetNet)
l Uplink RSRP measurement

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 3-7 shows the uplink RSRP measurement process.

eRAN
Figure 3-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.
l Downlink RSRP measurement
A cell edge UE receives wanted signals from its serving cell and also interfering signals
from neighboring cells. (The signals are all reference signals.) If the signal quality of a
neighboring cell is offset better than that of the serving cell, event A3 is triggered. Then,
the UE reports the RSRP values of the serving cell and neighboring cells to the serving
eNodeB. For details about event A3, see section 5.5.4.4 "Event A3 (Neighbour becomes
offset better than PCell)" in 3GPP TS 36.331 V10.4.0. The CellMcPara.A3Offset
parameter specifies the offset for event A3.
NOTE
Automatic neighboring cell configuration for SRS measurement used by the CSPC function is
dependent on downlink RSRP measurement, by which neighboring cells are detected.

eRAN
CSPC Feature Parameter Description 4 eCSPC
4 eCSPC
4.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.
Figure 4-1 outlines the eCSPC procedure.
Figure 4-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-carrier aggregation (CA) scenarios, the selection is based on event A3. In CA
scenarios, the selection for the primary serving cell (PCell) is based on event A3 and the
selection for secondary serving cells (SCells) is based on event A6.

eRAN
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.
4.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(-3 dB):
l If the DB_6_P_A(-6 dB) and DB_4DOT77_P_A(-4.77 dB) 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.
l If the DB_6_P_A(-6 dB) option of the CELLCSPCPARA.eCSPCPCAdjRange
parameter is selected, the eNodeB uses the following values for power adjustments: 6
dB and 3 dB.

eRAN
4.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 3.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.

eRAN
CSPC Feature Parameter Description 5 Intra-eNodeB CSPC
5 Intra-eNodeB CSPC
5.1 Intra-eNodeB CSPC Procedure

Intra-eNodeB CSPC takes effect for UEs mainly under interference from intra-eNodeB intra-
frequency neighboring cells. It reduces interference between the serving cell and the two
intra-eNodeB intra-frequency neighboring cells that cause strongest interference to the
serving cell.
Figure 5-1 outlines the intra-eNodeB CSPC procedure.
Figure 5-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.

eRAN
CSPC Feature Parameter Description 5 Intra-eNodeB CSPC
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 UE-
reported 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:
l The CQI reporting interval is greater than or equal to 40 ms.
l The interference from intra-eNodeB intra-frequency neighboring cells is at least 6 dB
higher than that from inter-eNodeB neighboring cells.
The intra-eNodeB CSPC function produces stable gains when the previous conditions are
fulfilled.
5.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 last 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.
5.3 RSRP Measurement for Intra-eNodeB CSPC

RSRP measurement for intra-eNodeB CSPC is the same as that for CSPC. For details, see 3.4
RSRP Measurement for CSPC.
l If the CSPC function is enabled together with intra-eNodeB CSPC, intra-eNodeB CSPC
uses uplink RSRP measurement.
l If the eCSPC function is enabled together with intra-eNodeB CSPC, intra-eNodeB CSPC
uses downlink RSRP measurement.
l If the CSPC and eCSPC functions are disabled, intra-eNodeB CSPC uses downlink
RSRP measurement.

eRAN
CSPC Feature Parameter Description 6 Related Features
6 Related Features
Prerequisite Features
Feature ID Feature Name Description
LBFD-001015 Enhanced Scheduling Based on enhanced scheduling,

Coordinated Scheduling based Power
Control provides optimum downlink
transmit power configurations for cells
across the network.
LBFD-00101501 CQI Adjustment CQI adjustment enables the initial block

error rate (IBLER) of UEs to approach
the optimal target value after
Control is enabled.
LBFD-00300503 Synchronization with CSPC requires time synchronization

GPS across the network.
LOFD-00301302 IEEE1588 V2 Clock

Synchronization
Mutually Exclusive Features

LBFD-002025 Basic Scheduling Basic scheduling does not ensure

scheduling fairness among UEs.
Control requires enhanced scheduling.
LBFD-070106 PDSCH Efficiency CSPC and eCSPC do not work with

Improvement adaptive power allocation for cell edge
UEs.
LOFD-001007 High Speed Mobility In high-speed mobility scenarios, cell

load changes so rapidly that centralized

eRAN
LOFD-001008 Ultra High Speed control nodes and eNodeBs cannot

Mobility respond promptly during downlink
power adjustment.
LOFD-001009 Extended Cell The Coordinated Scheduling based

Access Radius Power Control feature requires that the
radius of each cell involved should not
LOFD-081223 Extended Cell exceed 15 km.
Access Radius
Beyond 100km
LOFD-060201 Adaptive Inter-Cell Adaptive ICIC is based on

Interference eCoordinators, whereas CSPC is based
Coordination on Cloud BB. They apply to different
scenarios and therefore cannot be used
together.
LAOFD-081233 Dynamic TDM Coordinated Scheduling based Power

eICIC Control and the eICIC feature produce
gains in different scenarios, and
therefore cannot be both enabled.
LOFD-081221 Super Combined This feature and Coordinated

Cell Scheduling based Power Control cannot
be both enabled.
LEOFD-111302 Flexible Bandwidth l If a Double Deck cell group uses a

based on Overlap non-standard bandwidth of 5.7, 7.3,
Carriers 7.6, 8.6, or 8.9 MHz, the CSPC and
intra-eNodeB CSPC functions
cannot be activated in either of the
cells in the group.
l If a Double Deck cell group uses a
non-standard bandwidth of 4, 12.2,
or 17.1 MHz, the CSPC and intra-
eNodeB CSPC functions cannot be
activated in the cell with a standard
bandwidth of 3 MHz in the group.
l If a Double Deck cell group uses a
non-standard bandwidth of 27.6 or
28.5 MHz, the CSPC and intra-
eNodeB CSPC functions cannot be
activated in the cell with a standard
bandwidth of 10 MHz in the group.
LOFD-111205 CDMA and LTE This feature and Coordinated

Zero Bufferzone Scheduling based Power Control cannot
(LTE FDD) be both enabled.
MRFD-231806 GSM and LTE Intra-eNodeB CSPC does not work with
Dynamic Power these two features.
Sharing (LTE)

eRAN
MRFD-090202 GSM and LTE FDD

Dynamic Spectrum
Sharing (LTE FDD)
MRFD-111401 GSM and LTE Zero This feature and Coordinated

Bufferzone Scheduling based Power Control cannot
be both enabled.
Impacted Features
LOFD-001016 VoIP Semi-persistent CSPC does not apply to UEs that are
Scheduling scheduled in a semi-persistent manner.
LAOFD-001001 LTE-A Introduction Serving- and neighboring-cell RSRP

measurements for CSPC are based on
SRS, which is transmitted by UEs to
eNodeBs. If a cell in the CSPC coverage
area is configured as a secondary
serving 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
in most cases. However, it may have a
negative impact on UEs that achieve
high throughput and experience
interference in hotspot neighboring
cells. If basic scheduling 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. Therefore,
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.
eCSPC mitigates interference between
intra-frequency cells to increase the
overall average UE throughput and cell
edge UE throughput in the eCSPC
coverage area. eCSPC may produce
negative gains for CA UEs causing

eRAN
LAOFD-001002 Carrier Aggregation strong interference to other UEs. If basic

for Downlink 2CC in scheduling is used with CA, the data
40MHz rate of a CA UE is defined as the total
data rate of the UE on all the aggregated
carriers. As a result, CA UEs in cells
with eCSPC disabled encounter a lower
data rate than CA UEs in cells with
eCSPC enabled.
LOFD-003029 SFN CSPC applies to SFN cells for which the

FddResMode.SfnCapabilityMode
parameter is set to
NORMAL(NORMAL), but not to SFN
cells for which the
FddResMode.SfnCapabilityMode
parameter is set to
LARGECAPABILITY(LARGECAP
ABILITY).
LOFD-070205 Adaptive SFN/ If the CellAlgoSwitch.SfnDlSchSwitch

SDMA parameter is set to
ADAPTIVE(Adaptive scheduling), the
intra-eNodeB CSPC function will not
take effect. Therefore, this parameter
cannot be set to this value.
LOFD-081208 Inter-eNodeB SFN When a CSPC cluster includes an inter-

Based on eNodeB SFN cell, the
Coordinated eNodeB CspcAlgoPara.CspcPowerConfigDelay
parameter must be set to a value that is 1
ms longer than the value for non-SFN
cells.
MLOFD-121280 eMTC Introduction The Coordinated Scheduling based

Power Control feature does not take
effect for UEs capable of enhanced
Machine Type Communication (eMTC).

eRAN
CSPC Feature Parameter Description 7 Network Impact
7 Network Impact
7.1 System Capacity

On a heavily loaded network in a densely populated urban area, Coordinated Scheduling
based Power Control increases the user-perceived downlink data rate without affecting the
downlink traffic volume of the entire network.
7.2 Network Performance

The impact of Coordinated Scheduling based Power Control on throughput is dependent on
the following factors:
l Inter-cell interference
The shorter the inter-RRU distance, the larger the gains brought by CSPC and
eCSPC. An inter-RRU distance of less than 500 m is recommended for CSPC and
eCSPC coverage areas.
Intra-eNodeB CSPC mitigates interference between three intra-eNodeB intra-
frequency neighboring cells at most. Therefore, it is recommended that intra-
eNodeB CSPC be deployed in eNodeBs that each serve three cells.
l Network load distribution
On live networks, cell load is represented by the downlink PRB usage in individual cells.
The more unbalanced the load between cells is, the more gains Coordinated Scheduling
based Power Control brings. Therefore, it is recommended that this feature be deployed
in areas that include hotspot cells.
NOTE
Hotspot cells are cells with busy-hour downlink PRB usage of greater than 40%.
l 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, 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.

eRAN
If the network load is high, for example the average PRB usage 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 average UE throughput and gains in cell
edge UE throughput.
l Inter-cluster interference
NOTE
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 both 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.
l 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.
l UE movement speed
Coordinated Scheduling based Power Control requires downlink or uplink RSRP
measurements. This feature 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.
CSPC
CSPC can be used when the average PRB usage 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:
l The average UE throughput increases by 5% to 15%, and the cell edge UE throughput
increases by 5% to 30%.
l To identify cell edge UEs, CSPC requires uplink SRS transmission. The resource
consumption by uplink SRS affects uplink performance.
eCSPC
eCSPC can be used when the average PRB usage in the eCSPC coverage area exceeds 30%,
the average number of active UEs in hotspot cells is greater than 3, the inter-RRU distance
between eNodeBs is less than 500 m, and no obvious inter-system interference is present.
eCSPC has the following impact on network performance:
l When the average PRB usage in the eCSPC coverage area is around 30%, the cell edge
UE throughput increases by up to 10% and the average UE throughput increases by up to
5% in hotspot cells.
l When the average PRB usage in the eCSPC coverage area is around 50%, the cell edge
UE throughput increases by 5% to 20% and the average UE throughput increases by 5%
to 10% in hotspot cells.
l In the eCSPC coverage area, the average cell throughput slightly decreases due to the
decrease in throughput of lightly loaded cells. However, the total downlink traffic

eRAN
volume does not decrease because the lightly loaded cells have sufficient radio resources
and use more frequency-domain resources to transmit the same amount of data without
increasing the transmission time.
l 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.
NOTE
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.
Intra-eNodeB CSPC
Intra-eNodeB CSPC can be used when the average PRB usage exceeds 30% in the intra-
eNodeB CSPC coverage area and no obvious inter-system interference is present. Intra-
eNodeB CSPC has the following impact on network performance:
l When the average PRB usage in the intra-eNodeB CSPC coverage area is around 30%,
the average UE throughput increases by 0% to 5%.
l 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.

eRAN
CSPC Feature Parameter Description 8 Engineering Guidelines for CSPC
8 Engineering Guidelines for CSPC
8.1 When to Use

Use CSPC for cells that meet all the following conditions:
l 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.
l There are hotspot cells whose busy-hour downlink PRB usage is greater than 40%.
l Most UEs in the network move at speeds less than 10 km/h.
l The number of RRC_CONNECTED UEs served by each BBP deployed with cells is less
than 850.
l The CPU usage of each BBP deployed with cells is less than 85%.
l The downlink cell bandwidth is greater than or equal to 10 MHz.
8.2 Required Information

Before deploying CSPC, collect the following information:
l 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 and bandwidth configurations of cells
l Values of counters indicating the LTE network load status and interference level
Counters indicating the network load status are listed in Table 8-1 and Table 8-2.

eRAN
Table 8-1 Number of UEs in a cell
Counter ID Counter Name Description
1526727378 L.Traffic.User.Avg Average number of UEs

in a cell
1526727379 L.Traffic.User.Max Maximum number of

UEs in a cell
1526728969 L.Traffic.ActiveUser.DL.Avg Average number of

activated UEs in the
downlink
1526728970 L.Traffic.ActiveUser.DL.Max Maximum number of

downlink
1526728975 L.Traffic.ActiveUser.Avg Average number of

activated UEs
1526728976 L.Traffic.ActiveUser.Max Maximum number of

activated UEs
Table 8-2 Average number of consumed PRBs
1526726740 L.ChMeas.PRB.DL.Used.Avg Average number of used

downlink PRBs
1526728433 L.ChMeas.PRB.DL.Avail Number of available

downlink PRBs
1526741763 L.ChMeas.PRB.PUSCH.Avg.Bord Average number of

erUE PUSCH PRBs used by
cell edge UEs in a cell
1526741767 L.ChMeas.PRB.PDSCH.Avg.Bord Average number of

erUE PDSCH PRBs used by
Counters indicating the network interference level are listed in Table 8-3, Table
8-4, Table 8-5, Table 8-6, and Table 8-7.
NOTE
Before deploying CSPC, run the following command:

MOD CELLCOUNTERPARAGROUP:LocalCellId=0,
CellCounterAlgoSwitch=BasedA3EdgeUserSwitch-1, EdgeUserA3Offset=-6;
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.

eRAN
Table 8-3 Number of cell edge UEs in a cell

1526741888 L.Traffic.User.BorderUE.Avg Average number of cell

edge UEs in a cell
1526741889 L.Traffic.User.BorderUE.Max Maximum number of

Table 8-4 Number of times MCS index n (n = 0 to 31) is selected for PUSCH and
PDSCH scheduling in a cell
1526727412 L.ChMeas.PUSCH.MCS.0 to Number of times MCS

to L.ChMeas.PUSCH.MCS.31 index n is selected for
1526727443 PUSCH scheduling
1526727444 L.ChMeas.PDSCH.MCS.0 to Number of times MCS

to L.ChMeas.PDSCH.MCS.31 index n is selected for
1526727475 PDSCH scheduling
Table 8-5 Number of times the reported wideband CQI is n (n = 0 to 15) in a cell
1526727396 L.ChMeas.CQI.DL.0 to Number of wideband

to L.ChMeas.CQI.DL.15 CQI reports with the
1526727411 value n
1526737710 L.ChMeas.CQI.DL.BorderUE.Tot Accumulated value of

al wideband CQIs reported
by cell edge UEs
1526737711 L.ChMeas.CQI.DL.BorderUE.Nu Number of times

m wideband CQIs are
reported by cell edge
UEs
Table 8-6 Average downlink user data rate in a cell

1526728261 L.Thrp.bits.DL Total downlink traffic

volume for PDCP SDUs
in a cell

eRAN
1526728997 L.Thrp.Time.Cell.DL.HighPrecisio Total duration of

n downlink data
transmission in a cell
(with the precision of 1
ms)
1526728262 L.Thrp.Time.DL Total transmit duration

of downlink PDCP
SDUs in a cell
1526729005 L.Thrp.bits.DL.LastTTI Downlink PDCP traffic

volume sent in the last
TTI before the buffer is
empty
1526729015 L.Thrp.Time.DL.RmvLastTTI Data transmission

duration except the last
TTI before the downlink
buffer is empty
Table 8-7 Downlink data rates of cell edge UEs in a cell

1526737755 L.Thrp.bits.DL.BorderUE Downlink PDCP-layer

traffic volume sent for
CEUs in a cell
1526741760 L.Thrp.Time.DL.BorderUE Total duration of sending

data to cell edge UEs in
the downlink at the
PDCP layer in a cell
1526737758 L.Thrp.bits.DL.LastTTI.BorderU Downlink PDCP-layer

E traffic volume sent in the
last TTI for CEUs before
the buffer is empty in a
cell
1526737759 L.Thrp.Time.DL.RmvLastTTI.Bo Data transmission

rderUE duration for CEUs
except the last TTI
before the downlink
buffer is empty

eRAN
8.3 Planning
RF Planning
N/A
Network Planning
l The network must be deployed using the Cloud BB architecture.
For details about the networking, cable connections, and clock synchronization for
USU3910-based Cloud BB architecture, see USU3910-based Multi-BBU Interconnection
Feature Parameter Description. eX2 interfaces must be configured between
interconnected BBUs. For details about the configuration, see eX2 Self-Management
Feature Parameter Description.
l 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).
Hardware Planning
Hardware planning for CSPC is as follows:
l UBBPd6 or UBBPei boards must be installed in the BBUs interconnected through
USUs, and the boards must be used only to carry centralized control nodes. For details
about the networking, see Figure 2-6. The other BBPs must be LBBPd, UBBPd,
UBBPe, or UBBPei. Only one BBP in an eNodeB is used to carry a centralized control
node.
In a Cloud BB network, only one centralized clustering node and one or more
centralized scheduling nodes can be deployed for FDD cells.
n The centralized clustering node allows all cells served by the BBUs
interconnected through one or two levels of USUs to participate in CSPC.
n Each cluster includes a maximum of 72 cells.
n The centralized clustering node supports a maximum of 12 centralized
scheduling nodes.
n 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

eRAN
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.
l External synchronization sources must be configured for BBUs. For details, see
Synchronization Feature Parameter Description.
8.4 Deployment
8.4.1 Process
The CSPC deployment process is as follows:
1. Determine the area in which CSPC is to be deployed.

2. Configure the U2000, 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.
8.4.2 Requirements
Other Features
The prerequisite features described in 6 Related Features must be enabled.
Hardware
l A UMPT must be configured as the main control board for each BBU.
l If the cells in the CSPC coverage area are configured in BBU3900s, an LBBPd, UBBPd,
or UBBPe must be installed in slot 2 or 3 of each BBU. This constraint does not apply to
cells configured in BBU3910s.
l CSPC requires the following types of BBPs.
BBPs for Deploying Centralized Other BBPs
Control Nodes
UBBPd6 LBBPd
UBBPei UBBPd
UBBPe
UBBPei
License
Operators must purchase and activate the following license.

eRAN
Feature ID Feature Model License Control NE Sales

Name Item Unit
LOFD-070 Coordinated LT1SCSBP Coordinated eNodeB per cell

208 Scheduling CC00 Scheduling based
based Power Power Control (FDD)
Control
8.4.3 Precautions
Take the following precautions for using CSPC:
l All cells in a CSPC coverage area must have the same CSPC configurations.
l Monitor the synchronization status of cells and the status of transmission links when
deploying CSPC. If any faults occur, follow the instructions described in 8.7 Possible
Issues to handle them.
l Take the following precautions 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, causing the failure to differentiate between signals of UEs using 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.
l The CSPC function 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.
NOTE
Cell-specific SRS reconfiguration causes cells to be reestablished and therefore should be

performed when traffic is light, for example, in the early morning.
l 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.
8.4.4 Data Preparation and Feature Activation
8.4.4.1 Data Preparation

The CspcAlgoPara MO consists of CSPC algorithm parameters. The following table
describes the key parameters.

eRAN
Parameter Parameter ID Setting Notes

Name
CSPC Algorithm CspcAlgoPara.C N/A

Switch spcAlgoSwitch
CSPC Power CspcAlgoPara.C If the CSPC cluster includes an inter-eNodeB SFN

Config Delay spcPowerConfig cell, set this parameter to 3. In all other scenarios,
Delay set this parameter to 2.
CSPC Compute CspcAlgoPara.C The default value is recommended.

Switch spcComputeSwitc
h
CSPC RSRP CspcAlgoPara.C The default value is recommended.

Measurement spcRsrpMeasMo
Mode de
CSPC Schedule CspcAlgoPara.C The default value is recommended.

UE Specification spcScheduleUeS
pec
CSPC Cluster CspcAlgoPara.C Currently, only static clustering is supported.

Mode spcClusterMode
CSPC Enable CspcAlgoPara.C The value 40 is recommended when the inter-site

Downlink PRB spcEnableDlPrb distance is short and interference is strong, for
Ratio Threshold RatioThd example, in densely populated urban areas with a
200 m inter-site distance or in stadiums.
The value 70 is recommended when the inter-site
distance is long and interference is light, for
example, in common urban areas with a 500 m
inter-site distance.
CSPC Capacity CspcAlgoPara.C The value 30 is recommended when

Factor spcCapacityFact CspcRapidRptSwitch is set to ON(On). The
or value 1 is recommended when
CspcRapidRptSwitch is set to OFF(Off).
The CellCspcPara MO consists of cell-specific CSPC parameters. The following table


Name
CSPC UE SRS CellCspcPara.Cs The default value is recommended.

Config Report pcUeSrsCfgRptPe
Period riod
CSPC UE SRS CellCspcPara.Cs The default value is recommended.

Config Rapid pcRapidRptSwitc
Report Switch h

eRAN

Name
Cell CSPC CellCspcPara.Cel The value ON(On) is recommended.

Switch lCspcSwitch
CSPC CQI Filter CellCspcPara.Cs The value 0 is recommended.

Coefficient pcCqiFilterCoeff
Uplink RSRP CellCspcPara.Ul The default value is recommended.

Measurement RsrpRptPeriod
Report Period
The NCellSrsMeasPara MO consists of SRS measurement parameters for neighboring cells.

The following table describes the key parameters.

Name
SRS or DMRS NCellSrsMeasP The default value is recommended.

Auto Neighbour ara.NCellSrsMe
Cell asA3Offset
Measurement
A3 Offset
SRS Auto NCellSrsMeasP For tests or to use CSPC immediately, set this
Neighbour Cell ara.SrsAutoNCe parameter to OFF if the number of UEs is small
Measurement llMeasSwitch and event A3 reports are scarce. For live networks,
Switch 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.

Name
SRS Period CellSrsAdaptive Set this parameter to OFF(Off) if

Adaptive Switch Cfg.SrsPeriodAda CspcAlgoPara.CspcAlgoSwitch is set to
ptive ON(On).
User SRS Period CellSrsAdaptive For non-SFN cells, set this parameter to
Cfg.UserSrsPerio ms40(40ms).
d For SFN cells, set this parameter to ms40(40ms)
if FddResMode.SfnCapabilityMode is set to
NORMAL(NORMAL).
The SRSCfg MO consists of cell-level SRS-related parameters. The following table describes
the key parameters.

eRAN

Name
SRS SRSCfg.SrsCfgIn Set this parameter to BOOLEAN_TRUE(True)

Configuration d if CspcAlgoPara.CspcAlgoSwitch is set to
Indicator ON(On).
FDD SRS SRSCfg.FddSrsC Set this parameter to DEFAULTMODE(Default

Configuration fgMode Mode) if CspcAlgoPara.CspcAlgoSwitch is set
Mode to ON(On).
SRS subframe SRSCfg.SrsSubfr If CspcAlgoPara.CspcAlgoSwitch is set to

configuration ameCfg ON(On), set this subframe configuration
parameter as follows:
l If the result of the physical cell identifier
(PCI) modulo 3 is 0, set this parameter to
SC3(3).
l If the result of PCI modulo 3 is 1, set this
parameter to SC4(4).
l If the result of PCI modulo 3 is 2, set this
parameter to SC5(5).
The EUCOSCHCFG MO consists of parameters related to the configuration of coordinated

scheduling in E-UTRAN cells in Cloud BB scenarios. The following table describes the key
parameters.

Name
Cluster Partition EUCOSCHCFG N/A

Node Base Band .PrtNodeBaseBa
Equipment Id ndEqmId
Scheduling EUCOSCHCFG N/A

Node Base Band .SchNodeBaseBa
Equipment Id ndEqmId
Coordinated EUCOSCHCFG N/A

Scheduling .WorkMode
Work Mode
The Cluster MO consists of parameters related to clusters. The following table describes the
key parameters.

Name
Cluster ID Cluster.ClusterI N/A

d

eRAN

Name
Cluster Type Cluster.ClusterT The default value is recommended.

ype
The ClusterCell MO consists of parameters related to cells in clusters. The following table

Name
Cluster ID ClusterCell.Clus N/A

terId
Mobile country ClusterCell.Mcc N/A

code
Mobile network ClusterCell.Mnc N/A

code
eNodeB ID ClusterCell.eNo N/A

deBId
Cell ID ClusterCell.CellI N/A

d
8.4.4.2 Activation
Using the CME

l Fast batch activation
This feature can be batch activated using the Feature Operation and Maintenance
function of the CME. For detailed operations, see the following section in the CME
product documentation or online help: CME Management > CME Guidelines >
Enhanced Feature Management > Feature Operation and Maintenance.
l Single/batch configuration
This feature can be activated for a single eNodeB or a batch of eNodeBs on the CME.
For detailed operations, see CME-based Feature Configuration.
Using MML Commands

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:
Step 1 Run the ADD BRD command to add a BBP for centralized scheduling to the specified BBU.
Step 2 Run the ADD BASEBANDEQM command to add a set of baseband equipment that includes
the BBP.

eRAN
Step 3 Run the MOD EUCOSCHCFG command to deploy centralized scheduling on the set of
baseband equipment.
NOTICE
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.
Step 4 Run the ADD CLUSTER command to add a cluster on the BBP.
Step 5 Run the ADD CLUSTERCELL command to add cells to the cluster on the BBP.
NOTE
It is recommended that intra-frequency cells providing continuous coverage be added to the same
cluster.
Step 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.
NOTE
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.
Step 7 (Required for automatic neighboring cell configuration) Run the MOD
NCELLSRSMEASPARA command to enable cell-specific automatic SRS measurement in
neighboring cells.
Step 8 Run the MOD SRSCFG and MOD CELLSRSADAPTIVECFG commands to specify the
fixed cell- and UE-specific SRS configurations.
Step 9 Run the MOD CELLCSPCPARA command to set cell-specific CSPC parameters. In this
step, set the cell-level CSPC switch on.
Step 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.
NOTICE
After CSPC is enabled, modifications of clusters and cells in clusters will take effect within 5
minutes.
----End

eRAN
MML Command Examples

This example assumes that the number of cells for which CSPC is to be deployed is not
greater than 180.
//Adding a BBP for centralized scheduling to the specified BBU
ADD BRD: 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
MOD EUCOSCHCFG: PRTNODEBASEBANDEQMID=23, SCHNODEBASEBANDEQMID=23,
WORKMODE=COORDINATED_SCHEDULING_ONLY;
//Adding a cluster on the BBP
ADD CLUSTER: CLUSTERID=0;
//Adding a cell to the cluster on the BBP
ADD CLUSTERCELL: CLUSTERID=0, MCC="460", MNC="01", ENODEBID=32, CELLID=1;
//(Optional; required for manual neighboring cell configuration) Adding a
neighboring cell, which will perform SRS measurements, for the cell in the
cluster on the BBP
ADD CSPCCELLSRSMEASNCELL: MCC="460", MNC="01", ENODEBID=32, CELLID=1,
NCELLMCC="460", NCELLMNC="01", NCELLENODEBID=32, NCELLID=2;
//(Optional; required for automatic neighboring cell configuration) Enabling cell-
specific 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;
//Setting the cell-level CSPC switch on
MOD CELLCSPCPARA: LOCALCELLID=0, CELLCSPCSWITCH=ON;
//Setting the overall CSPC algorithm switch on and specifying the clustering mode
on the BBP
MOD CSPCALGOPARA: CSPCALGOSWITCH=ON, CSPCCLUSTERMODE=STATIC_CONFIG;
8.4.5 Activation Observation

The activation observation procedure is as follows:
Step 1 Run the eNodeB command DSP CELLCSPCSTATUS. View the value of Cell CSPC Status
in the command output.
Expected result: The value is On.
Step 2 Log in to the U2000 client. Choose Monitor > Signaling Trace > Signaling Trace
Management. In the displayed window, choose Trace Type > LTE > User Performance
Monitoring > Quality of Channel Monitoring in the navigation tree. In the displayed dialog
box, select the target eNodeBs 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.
NOTE
When creating a monitoring task, you must specify a random value or an S-TMSI, as shown in Figure
8-1. To query the random value allocated for UE access or the STMSI, run the DSP
ALLUEBASICINFO command for eNodeBs.

eRAN
Figure 8-1 Creating a channel quality monitoring task
Step 3 On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management.
In the displayed window, choose Trace Type > LTE > Cell Performance Monitoring >
Usage of RB Monitoring in the navigation tree. In the displayed dialog box, select the target
eNodeBs and create a task that monitors resource block (RB) usage.
Expected result: Downlink Power off RB Num has a valid value.
----End
8.4.6 Deactivation
Using the CME
Using MML Commands

l Setting the cell-level CSPC switch off
Run the eNodeB command MOD CELLCSPCPARA with the Cell CSPC Switch
parameter set to OFF(Off).
l Setting the overall CSPC switch off
Run the eNodeB command MOD CSPCALGOPARA with the CSPC Algorithm
Switch parameter set to OFF(Off).

//Setting the cell-level CSPC switch off
MOD CELLCSPCPARA: LOCALCELLID=0,CELLCSPCSWITCH=OFF;
//Setting the overall CSPC switch off
MOD CSPCALGOPARA: CSPCALGOSWITCH=OFF;
8.5 Performance Monitoring

Use one of the following methods to observe the gains brought by CSPC:
l Observe the counters listed in the following table before and after activating CSPC. The
changes in the counter values reflect CSPC performance.

eRAN
Table 8-8 Counters related to average user-perceived downlink rates


volume for PDCP SDUs in
a cell

volume sent in the last TTI
before the buffer is empty
1526729015 L.Thrp.Time.DL.RmvLa Data transmission duration

stTTI except the last TTI before
the downlink buffer is
empty
1526728997 L.Thrp.Time.Cell.DL.Hi Total duration of downlink

ghPrecision data transmission in a cell
ms)
1526728262 L.Thrp.Time.DL Total transmit duration of

downlink PDCP SDUs in a
cell
1526728599 to L.ChMeas.PRB.DL.RAN Number of PRBs on the

1526728630 K1.MCS.0 to PDSCH in rank 1 mode
L.ChMeas.PRB.DL.RAN using MCS index n (n = 0
K1.MCS.31 to 31) for scheduling in a
cell

cell
1526727444 to L.ChMeas.PDSCH.MCS. Number of times MCS

1526727475 0 to index n (n = 0 to 31) is
L.ChMeas.PDSCH.MCS. selected for scheduling on
31 the PDSCH
1526727396 to L.ChMeas.CQI.DL.0 to Number of times the

1526727411 L.ChMeas.CQI.DL.15 reported wideband CQI is
n (n = 0 to 15)
1526730141 to L.ChMeas.RI.Rank1 to Number of times rank n is

1526730142 L.ChMeas.RI.Rank2 reported by UEs (n = 1 or
2)

4)

eRAN
l Observe the counters listed in Table 8-9 to monitor the number of UEs for which CSPC
has taken effect.
In the counters, geometry 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 8-9 Average numbers of UEs with different levels of geometry factors in the local
cell
1526739801 L.Traffic.HighGeometry. Average number of UEs

User.Avg with a high geometry
factor in the local cell
1526739802 L.Traffic.LowGeometry. Average number of UEs

User.Avg with a low geometry factor
in the local cell
l Log in to the U2000 client, and choose Monitor > Signaling Trace > Signaling Trace
Management. In the displayed window, choose Trace Type > LTE > Cell Performance
Monitoring > CSPC (Cell) Monitoring in the navigation tree. 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.
8.6 Parameter Optimization

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.

eRAN
8.7 Possible Issues

CSPC does not introduce any new alarms.
If any of the alarms listed in this section 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 8-10 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
26312 Inter-BBU Optical Module Receive Failure
26313 Inter-BBU Optical Module Transmit Failure
26314 Inter-BBU Port Failure
26315 Inter-BBU Port Connection Error
Table 8-11 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
27107 Interconnected Optical Module Receive Failure
27108 Interconnected Optical Module Transmit Failure
27109 Inter-Port Failure
27110 Inter-Port Connection Error

eRAN
CSPC Feature Parameter Description 9 Engineering Guidelines for eCSPC
9 Engineering Guidelines for eCSPC
9.1 When to Use

Use eCSPC for cells that meet all the following conditions:
l The average inter-RRU distance is less than 500 m in densely populated urban areas.
l The average downlink PRB usage is greater than 30% across the network, the average
number of active UEs in hotspot cells is greater than 3, and cells are unbalanced in their
load.
l The movement speeds of UEs on the live network are lower than 10 km/h.

Before deploying eCSPC, collect the following information:

Whether the eNodeBs are outdoor base stations that cover densely populated urban
areas
Whether the average inter-RRU distance is less than 500 m in densely populated
urban areas
Table 9-1 Number of UEs in a cell

in a cell

UEs in a cell

eRAN

downlink

downlink

activated UEs

activated UEs
Table 9-2 Average number of PRBs used in the downlink


downlink PRBs

downlink PRBs

NOTE
Before deploying eCSPC, run the following command:

When CA is used, counters related to the number of cell edge UEs count the number of UEs
that have reported event A3 only in their PCells because a CA UE is treated as an entity in
the PDCP layer or above only in its PCell. Therefore, if the PCell coverage and SCell
coverage do not completely overlap, the gains for UEs at the SCell edges out of the PCell
coverage cannot be measured by counters, though there are positive gains.

eRAN

edge UEs in a cell

Table 9-4 Number of times MCS index n (n = 0 to 31) is selected for PDSCH
scheduling in a cell


1526727411 value n

by cell edge UEs

m wideband CQIs are
UEs

in a cell

n downlink data
ms)

eRAN

of downlink PDCP
SDUs in a cell

empty

buffer is empty


CEUs in a cell

the downlink at the

cell

except the last TTI
before the downlink
buffer is empty
9.3 Planning
RF Planning
N/A
Network Planning
l 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.

eRAN
l In an IP RAN, the one-way delay must be less than 8 ms.
Hardware Planning
N/A
9.4 Deployment
9.4.1 Requirements
Other Features
Hardware
eCSPC requires the following types of BBPs:
l LBBPd
l UBBPd
l UBBPe
l UBBPei
License

Name Item Unit

Control
9.4.2 Precautions
Take the following precautions before deploying eCSPC:
l 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.
l 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:

eRAN
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.

The CellCspcPara MO consists of cell-specific eCSPC parameters. The following table

Name
Cell eCSPC CELLCSPCPAR N/A

Switch A.CelleCspcSwitc
h
eCSPC A3 Offset CellCspcPara.eC N/A

spcA3Offset
eCSPC Power CellCspcPara.eC N/A

Control spcPCAdjRange
Adjustment
Range
eCSPC PC CellCspcPara.eC N/A

Adjustment UE spcPCAdjUeNum
Number Th
Threshold
9.4.3.2 Activation
Using the CME


eRAN
Using MML Commands

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).
NOTICE
Five minutes after being enabled, eCSPC starts to coordinate inter-cell power for a cell and
neighboring cells that cause strong interference to the cell.

l 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;
l 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;

To verify that eCSPC has been activated, perform the following steps:
Step 1 Run the DSP CELLECSPCSTATUS command on the eNodeB 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.
Step 2 On the U2000 client, choose Monitor > Signaling Trace and double-click Signaling Trace
Management. In the navigation tree of the displayed window, choose 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 9-1, 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.

eRAN
Figure 9-1 Performance monitoring
Step 3 On the U2000 client, choose Monitor > Signaling Trace and double-click Signaling Trace
Management. In the navigation tree of the displayed window, choose LTE > Application
Layer and double-click Uu Interface Trace. Create a Uu interface tracing task. If the RRC
message shown in Figure 9-2 is traced, PA has been changed for the relevant UE.
Figure 9-2 Signaling message indicating a PA change
----End
9.4.5 Deactivation
Using the CME

eRAN
Using MML Commands

Run the eNodeB command MOD CELLCSPCPARA with the Cell eCSPC Switch

//Setting the cell-level eCSPC switch off
MOD CELLCSPCPARA: LOCALCELLID=0, CELLECSPCSWITCH=OFF;

Use one of the following methods to observe the gains brought by eCSPC:
l Observe the counters listed in Table 9-8 before and after activating eCSPC. The changes
in the counter values reflect eCSPC performance.

a cell


empty

ms)

cell

cell

cell

eRAN

1526727475 0 to index n (n = 0 to 31) is
31 the PDSCH

n (n = 0 to 15)

2)

4)
l At least seven days before activating eCSPC, run the MOD

CELLCOUNTERPARAGROUP command with the BasedA3EdgeUserSwitch option
of the Cell Counter Algorithm Switch parameter selected and with the Edge User
Distinguish A3 Offset parameter set to -6, and observe the counters listed in Table 9-9.
Table 9-9 Counters related to user-perceived downlink rates of cell edge UEs
1526729056 to L.Thrp.DL.BitRate.Sam Number of downlink

1526729065 p.Index0 to throughput samples within
L.Thrp.DL.BitRate.Sam the range of index n (n = 0
p.Index9 to 9)
1526737755 L.Thrp.bits.DL.BorderU Downlink PDCP-layer

E traffic volume sent for
CEUs in a cell
1526737758 L.Thrp.bits.DL.LastTTI. Downlink PDCP-layer

BorderUE traffic volume sent in the
cell

stTTI.BorderUE for CEUs except the last
buffer is empty
1526741760 L.Thrp.Time.DL.Border Total duration of sending

UE data to cell edge UEs in
the downlink at the PDCP
layer in a cell

eRAN
1526737710 L.ChMeas.CQI.DL.Bord Accumulated value of

erUE.Total wideband CQIs reported
by cell edge UEs
1526737711 L.ChMeas.CQI.DL.Bord Number of times

erUE.Num wideband CQIs are
reported by cell edge UEs
1526741767 L.ChMeas.PRB.PDSCH. Average number of

Avg.BorderUE PDSCH PRBs used by cell
edge UEs in a cell
1526741888 L.Traffic.User.BorderUE Average number of cell

.Avg edge UEs in a cell
1526741889 L.Traffic.User.BorderUE Maximum number of cell

.Max edge UEs in a cell
1526741890 L.Traffic.User.IntraBoar Average number of intra-

d.BorderUE.Avg BBP CEUs in a cell
1526741891 L.Traffic.User.IntraBBU Average number of intra-

InterBoard.BorderUE.A BBU inter-BBP CEUs in a
vg cell
1526741892 L.Traffic.User.InterBBU. Average number of inter-

BorderUE.Avg BBU CEUs in a cell
1526741768 L.Traffic.DL.SCH.TB.Bo Number of TBs initially

rderUE transmitted to cell edge
UEs on the downlink SCH
1526741770 L.Traffic.DL.SCH.ErrT Number of downlink

B.Rbler.BorderUE erroneous TBs after the
maximum number of
retransmissions to cell
edge UEs is reached

B.Ibler.BorderUE erroneous TBs after initial
transmission to cell edge
UEs
l Observe the counters listed in Table 9-10 to monitor the percentage of UEs for which
eCSPC has taken effect.

eRAN
Table 9-10 Counters related to cell algorithms and measurements

1526741772 to L.Traffic.PdschPA.Samp. Number of samples with

1526741779 Index0 to the downlink PDSCH PA
L.Traffic.PdschPA.Samp. equal to index n (n = 0 to
Index7 7)

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 lowest 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.
l 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.
l 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.
9.7 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:
l The value of eCspc Data Link Status is UNAVAILABLE.
l The value of eCspc Coordinate Cell Ex2 Link Delay Status is Yes.
For details about how to rectify the fault, see eX2 Self-Management Feature Parameter
Description.

eRAN
CSPC Feature Parameter Description 10 Engineering Guidelines for Intra-eNodeB CSPC
10 Engineering Guidelines for Intra-

eNodeB CSPC
10.1 When to Use

Use intra-eNodeB CSPC when the following conditions are met:
l The average downlink PRB usage is greater than 30% across the network.
l The movement speeds of UEs on the live network are lower than 10 km/h.
l Three sectors are deployed on each eNodeB.

Before deploying intra-eNodeB CSPC, collect the following information:

Networking information, for example, whether at least two intra-frequency cells are
established on a BBP and whether intra-eNodeB intra-frequency cells have
overlapping coverage
Table 10-1 Number of downlink UEs in a cell

in a cell

UEs in a cell

eRAN

downlink

downlink

activated UEs

activated UEs
Table 10-2 Average number of PRBs used in the downlink


downlink PRBs

downlink PRBs

NOTE
Before deploying intra-eNodeB CSPC, run the following command:



edge UEs in a cell


eRAN
Table 10-4 Number of times MCS index n (n = 0 to 31) is selected for PDSCH
scheduling in a cell


1526727411 value n

by cell edge UEs

m wideband CQIs are
UEs


in a cell

n downlink data
ms)

of downlink PDCP
SDUs in a cell

empty

eRAN

buffer is empty

CEUs in a cell

the downlink at the

cell

except the last TTI
before the downlink
buffer is empty
10.3 Planning
RF Planning
N/A
Network Planning
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.
Hardware Planning
N/A

eRAN
10.4 Deployment
10.4.1 Requirements
Other Features
Hardware
Intra-eNodeB CSPC requires the following types of BBPs:
l LBBPd
l UBBPd
l UBBPe
l UBBPei
License

Name Item Unit

Control

The CellCspcPara MO consists of cell-specific intra-eNodeB CSPC parameters. The
following table describes the key parameters.

Name
Intra Enodeb CELLCSPCPAR N/A

Cspc Switch A.IntraEnbCspcS
w
eCSPC A3 Offset CellCspcPara.eC N/A

spcA3Offset

eRAN
10.4.2.2 Activation
Using the CME

Using MML Commands
NOTICE
l Do not set the CellDlschAlgo.MbsfnSfCfg parameter.
l Do not select the DetectRank2AdjSwitch option of the
CellDlschAlgo.DlRankDetectSwitch parameter, and do not set the
CellAlgoSwitch.SfnDlSchSwitch parameter to ADAPTIVE(Adaptive scheduling).
Otherwise, intra-eNodeB CSPC becomes ineffective.
Run the MOD CELLCSPCPARA command with the eCSPC A3 Offset parameter set to a
proper value and the Intra Enodeb Cspc Switch parameter set to ON(On).
NOTICE
Five minutes after intra-eNodeB CSPC is activated, it 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=SubFrame0-0&SubFrame1-0&SubFrame2-0&SubFrame3-0&SubFrame4-0&SubFrame5-0
&SubFrame6-0&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;

Run the DSP CELLINTRAENBCSPCSTATUS command on the eNodeB to query
information about the cooperating neighboring cells in intra-eNodeB CSPC.

eRAN
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.
10.4.4 Deactivation
Using the CME

Using MML Commands

Run the eNodeB command MOD CELLCSPCPARA with the Intra Enodeb Cspc Switch

//Setting the intra-eNodeB CSPC switch off
MOD CELLCSPCPARA: LOCALCELLID=0, IntraEnbCspcSw=OFF;

Use one of the following methods to observe the gains brought by intra-eNodeB CSPC:
l Observe the counters listed in Table 10-8 before and after activating intra-eNodeB
CSPC. The changes in the counter values reflect intra-eNodeB CSPC performance.

a cell


empty

ms)

cell

eRAN

cell

cell

1526727475 0 to index n (n = 0 to 31) is
31 the PDSCH

n (n = 0 to 15)

2)

4)
l At least seven days before activating this feature, run the MOD
CELLCOUNTERPARAGROUP command with the BasedA3EdgeUserSwitch option
of the Cell Counter Algorithm Switch parameter selected and with the Edge User
Distinguish A3 Offset parameter set to -6, and observe the counters listed in Table 10-9.
Table 10-9 Counters related to user-perceived downlink rates of cell edge UEs
1526729056 to L.Thrp.DL.BitRate.Sam Number of downlink

1526729065 p.Index0 to throughput samples within
L.Thrp.DL.BitRate.Sam the range of index n (n = 0
p.Index9 to 9)
1526737755 L.Thrp.bits.DL.BorderU Downlink PDCP-layer

E traffic volume sent for
CEUs in a cell

stTTI.BorderUE for CEUs except the last
buffer is empty

eRAN
1526741760 L.Thrp.Time.DL.Border Total duration of sending

UE data to cell edge UEs in
the downlink at the PDCP
layer in a cell
1526737710 L.ChMeas.CQI.DL.Bord Accumulated value of

erUE.Total wideband CQIs reported
by cell edge UEs
1526737711 L.ChMeas.CQI.DL.Bord Number of times

erUE.Num wideband CQIs are
reported by cell edge UEs
1526741767 L.ChMeas.PRB.PDSCH. Average number of

Avg.BorderUE PDSCH PRBs used by cell
edge UEs in a cell
1526741888 L.Traffic.User.BorderUE Average number of cell

.Avg edge UEs in a cell
1526741889 L.Traffic.User.BorderUE Maximum number of cell

.Max edge UEs in a cell
1526741890 L.Traffic.User.IntraBoar Average number of intra-

d.BorderUE.Avg BBP CEUs in a cell
1526741891 L.Traffic.User.IntraBBU Average number of intra-

InterBoard.BorderUE.A BBU inter-BBP CEUs in a
vg cell
1526741892 L.Traffic.User.InterBBU. Average number of inter-

BorderUE.Avg BBU CEUs in a cell
1526741768 L.Traffic.DL.SCH.TB.Bo Number of TBs initially

rderUE transmitted to cell edge
UEs on the downlink SCH

B.Rbler.BorderUE erroneous TBs after the
maximum number of
retransmissions to cell
edge UEs is reached

B.Ibler.BorderUE erroneous TBs after initial
transmission to cell edge
UEs
l Observe the counters listed in Table 10-10 to monitor the percentage of UEs for which
intra-eNodeB CSPC has taken effect.

eRAN
Table 10-10 Counters related to cell performance measurements

1526742073 L.ChMeas.PRB.DL.Intra Average number of PRBs

EnbCspc.Used.Avg used by UEs on which
downlink intra-eNodeB
CSPC takes effect in a cell

None
10.7 Possible Issues

N/A

eRAN
CSPC Feature Parameter Description 11 Parameters
11 Parameters
Table 11-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
CspcAlg CspcEna MOD LOFD-0 Coordin Meaning: Indicates the physical resource block (PRB)
oPara bleDlPr CSPCA 70208 ated usage threshold for enabling coordinated scheduling-
bRatioT LGOPA Scheduli based power control (CSPC). CSPC is enabled when
hd RA ng based the highest PRB usage among all cells in a CSPC
LST Power cluster is greater than this parameter value. To prevent
CSPCA Control( CSPC from being enabled and disabled frequently in
LGOPA Cloud the cluster, the PRB usage threshold for disabling
RA BB) CSPC is lower than this parameter value. This
parameter applies only to LTE FDD.
GUI Value Range: 0~100
Unit: %
Actual Value Range: 0~100
Default Value: 70
CspcAlg CspcRsr MOD LOFD-0 Coordin Meaning: Indicates the RSRP measurement mode
oPara pMeasM CSPCA 70208 ated used for CSPC. The uplink RSRP is measured based
ode LGOPA TDLOF Scheduli on the uplink SRS. This parameter applies only to
RA D-08020 ng based LTE FDD.
LST 3 Power GUI Value Range: RSRP_UL(Uplink RSRP)
CSPCA Control(
Cloud Unit: None
LGOPA
RA BB); Actual Value Range: RSRP_UL
Coordin Default Value: RSRP_UL(Uplink RSRP)
ated
Scheduli
ng based
Power
Control

eRAN

nd
CellMcP A3Offse MOD TDLBF Downlin Meaning: Indicates the offset for event A3. This offset
ara t CELLM D-00202 k Static is the difference between the signal quality of a
CPARA 201 Inter- neighboring cell and that of the serving cell. A larger
LST TDLBF Cell value indicates a higher requirement on neighboring
CELLM D-00202 Interfere cell quality for reporting event A3. This parameter
CPARA 202 nce applies only to LTE FDD and LTE TDD.
Coordin GUI Value Range: -30~30
LOFD-0 ation
60201 Unit: 0.5dB
Uplink
Static Actual Value Range: -15~15
Inter- Default Value: -13
Cell
Interfere
nce
Coordin
ation
Adaptiv
e Inter-
Cell
Interfere
nce
Coordin
ation
CellCsp eCspcP MOD LOFD-0 Coordin Meaning: Indicates the threshold of the number of
cPara CAdjUe CELLC 70208 ated UEs for power coordination. The eNodeB samples the
NumTh SPCPA Scheduli number of activated UEs in the downlink in the cell
RA ng based and calculates the average number of activated UEs.
LST Power Power coordination takes effect only if the average
CELLC Control( number of activated UEs is greater than or equal to
SPCPA Cloud this threshold. This parameter applies only to LTE
RA BB) TDD.
Unit: None
Actual Value Range: 0~10, step:0.1
Default Value: 0

eRAN

nd
CellCsp eCspcP MOD LOFD-0 Coordin Meaning: Indicates the cell power adjustment range
cPara CAdjRa CELLC 70208 ated for eCSPC. This parameter must be set to a PDSCH
nge SPCPA Scheduli PA value less than the value of the PaPcOff parameter.
RA ng based At most two values can be selected for the
LST Power eCspcPCAdjRange parameter. If one value is selected
CELLC Control for the eCspcPCAdjRange parameter, the PA can be
SPCPA changed only to this value. If two values are selected
RA for this parameter, the PA can be changed to two
values. This parameter applies only to LTE FDD.
GUI Value Range: DB_6_P_A(-6 dB),
DB_4DOT77_P_A(-4.77 dB), DB_3_P_A(-3 dB),
DB_1DOT77_P_A(-1.77 dB), DB0_P_A(0 dB),
DB1_P_A(1 dB), DB2_P_A(2 dB), DB3_P_A(3 dB)
Unit: None
Actual Value Range: DB_6_P_A, DB_4DOT77_P_A,
DB_3_P_A, DB_1DOT77_P_A, DB0_P_A,
DB1_P_A, DB2_P_A, DB3_P_A
Default Value: DB_6_P_A:Off,
DB_4DOT77_P_A:Off, DB_3_P_A:Off,
DB_1DOT77_P_A:Off, DB0_P_A:Off,
DB1_P_A:Off, DB2_P_A:Off, DB3_P_A:Off
CellDlp PaPcOff MOD LBFD-0 Dynami Meaning: Indicates the PA to be used when PA
cPdschP CELLD 02016 / c adjustment for PDSCH power control is disabled, DL
a LPCPD TDLBF Downlin ICIC is disabled, and the even power distribution is
SCHPA D-00201 k Power used for the PDSCH. This parameter applies only to
LST 6 Allocati LTE FDD and LTE TDD.
CELLD LOFD-0 on GUI Value Range: DB_6_P_A(-6 dB),
LPCPD 70208 Coordin DB_4DOT77_P_A(-4.77 dB), DB_3_P_A(-3 dB),
SCHPA ated DB_1DOT77_P_A(-1.77 dB), DB0_P_A(0 dB),
Scheduli DB1_P_A(1 dB), DB2_P_A(2 dB), DB3_P_A(3 dB)
ng based Unit: dB
Power
Control Actual Value Range: DB_6_P_A, DB_4DOT77_P_A,
DB_3_P_A, DB_1DOT77_P_A, DB0_P_A,
DB1_P_A, DB2_P_A, DB3_P_A
Default Value: DB_3_P_A(-3 dB)

eRAN

nd
CellCsp eCspcA MOD LOFD-0 Coordin Meaning: Indicates the A3 offset for eCSPC. If the
cPara 3Offset CELLC 70208 ated parameter value is increased, the probability of UEs
SPCPA Scheduli reporting event A3 is reduced. A larger value of this
RA ng based parameter indicates a smaller number of cell edge
LST Power users, and a smaller value of this parameter indicates a
CELLC Control larger number of cell edge users. For details, see
SPCPA 3GPP TS 36.331. This parameter applies only to LTE
RA FDD.
GUI Value Range: -30~30
Unit: 0.5dB
Actual Value Range: -15~15
Default Value: -12
FddRes SfnCapa MOD None None Meaning:

Mode bilityMo FDDRE Indicates the operating mode of single frequency
de SMODE network (SFN) cells. This eNodeB-level parameter
LST applies to LTE FDD eNodeBs equipped with LBBPd,
FDDRE UBBPd, or UBBPe boards.
SMODE
If this parameter is set to NORMAL, an SFN cell with
a bandwidth of 10 MHz or more supports a maximum
of 400 UEs, and an SFN cell with a bandwidth of 5
MHz supports a maximum of 200 UEs.
If this parameter is set to LARGECAPABILITY, an
SFN cell with a bandwidth of 10 MHz or more
supports a maximum of 1200 UEs, and an SFN cell
with a bandwidth of 5 MHz supports a maximum of
600 UEs.
This parameter applies only to LTE FDD.
GUI Value Range: NORMAL(NORMAL),
LARGECAPABILITY(LARGECAPABILITY)
Unit: None
Actual Value Range: NORMAL,
LARGECAPABILITY
Default Value: NORMAL(NORMAL)

eRAN

nd
CellAlg SfnDlSc MOD LOFD-0 SFN Meaning: Indicates the SFN downlink scheduling
oSwitch hSwitch CELLA 03029 / Adaptiv mode. The downlink scheduling modes include the
LGOSW TDLOF e SFN/ joint scheduling mode, and the auto-selection mode
ITCH D-00107 SDMA between joint scheduling and independent scheduling.
LST 5/ This parameter applies only to LTE FDD and LTE
MLOFD Inter- TDD.
CELLA BBU
LGOSW -121204 GUI Value Range: ADAPTIVE(Adaptive scheduling),
SFN
ITCH LOFD-0 JOINT(Joint scheduling)
70205 / Inter-
BBU Unit: None
TDLOF
D-00200 Adaptiv Actual Value Range: ADAPTIVE, JOINT
8 e SFN/ Default Value: JOINT(Joint scheduling)
SDMA
TDLOF
D-00108
0
TDLOF
D-00108
2
CspcAlg CspcPo MOD LOFD-0 Coordin Meaning: Indicates the interval between the time an
oPara werConf CSPCA 70208 ated eNodeB reports measurement information to the
igDelay LGOPA TDLOF Scheduli centralized control node and the time the power
RA D-08020 ng based configuration delivered by the centralized control
LST 3 Power node takes effect on the eNodeB. This parameter
CSPCA Control( applies only to LTE FDD and LTE TDD.
LGOPA Cloud GUI Value Range: 2~10
RA BB);
Unit: ms
Coordin
ated Actual Value Range: 2~10
Scheduli Default Value: 7
ng based
Power
Control

eRAN

nd
CellCou CellCou MOD LEOFD- Virtual Meaning: Indicates whether to enable cell-level
nterPara nterAlgo CELLC 111305 / 4T4R algorithms related to performance counters. This
Group Switch OUNTE LEOFD- Adaptiv parameter includes the following options:
RPARA 111305 e Inter- BasedA3EdgeUserSwitch: Indicates whether to enable
GROUP LOFD-0 Cell A3-based cell edge user (CEU) identification. If this
LST 60201 Interfere option is selected, the eNodeB starts to identify CEUs
CELLC nce based on A3-related measurement reports and collects
LOFD-0 related performance counters based on the identified
OUNTE 70208 Coordin
RPARA ation CEUs. This option applies only to LTE FDD and LTE
GROUP TDD.
Coordin
ated GUI Value Range:
Scheduli BasedA3EdgeUserSwitch(BasedA3EdgeUserSwitch)
ng based Unit: None
Power Actual Value Range: BasedA3EdgeUserSwitch
Control
Default Value: BasedA3EdgeUserSwitch:Off
CellCou EdgeUs MOD LEOFD- Virtual Meaning: Indicates the offset for cell edge user (CEU)
nterPara erA3Off CELLC 111305 4T4R identification event A3. This offset is the difference
Group set OUNTE LOFD-0 Adaptiv between the signal quality of a neighboring cell and
RPARA 60201 e Inter- that of the serving cell. A larger value of this
GROUP Cell parameter results that better signal quality of the
LOFD-0 neighboring cell is required for the reporting of CEU
LST 70208 Interfere
CELLC nce identification event A3 and the eNodeB has a lower
OUNTE Coordin probability of identifying a UE as a CEU. A smaller
RPARA ation value of this parameter results in a higher probability
GROUP that a UE is identified as a CEU. This parameter
Coordin applies only to LTE FDD and LTE TDD.
ated
Scheduli GUI Value Range: -30~30
ng based Unit: 0.5dB
Power Actual Value Range: -15~15
Control
Default Value: -13
CspcAlg CspcAlg MOD LOFD-0 Coordin Meaning: Indicates whether to enable CSPC for cells
oPara oSwitch CSPCA 70208 ated under the centralized control node in Cloud BB
LGOPA TDLOF Scheduli scenarios. This parameter applies only to LTE FDD.
RA D-08020 ng based GUI Value Range: OFF(Off), ON(On)
LST 3 Power
Control( Unit: None
CSPCA
LGOPA Cloud Actual Value Range: OFF, ON
RA BB); Default Value: OFF(Off)
Coordin
ated
Scheduli
ng based
Power
Control

eRAN

nd
CspcAlg CspcCo MOD LOFD-0 Coordin Meaning: Indicates whether the centralized control
oPara mputeS CSPCA 70208 ated node performs power calculation for power
witch LGOPA TDLOF Scheduli optimization. If this parameter is set to ON, the
RA D-08020 ng based centralized control node performs power calculation
LST 3 Power based on measurement information received from
CSPCA Control( eNodeBs. If this parameter is set to OFF, the
LGOPA Cloud centralized control node does not perform power
RA BB); calculation after receiving measurement information
Coordin from eNodeBs. This parameter applies only to LTE
ated FDD and LTE TDD.
Scheduli GUI Value Range: OFF(Off), ON(On)
ng based Unit: None
Power
Control Actual Value Range: OFF, ON
Default Value: ON(On)
CspcAlg CspcSch MOD LOFD-0 Coordin Meaning: Indicates the maximum number of UEs that
oPara eduleUe CSPCA 70208 ated can be selected for CSPC. This parameter applies only
Spec LGOPA TDLOF Scheduli to LTE FDD and LTE TDD.
RA D-08020 ng based GUI Value Range: 1~25
LST 3 Power
Control( Unit: None
CSPCA
LGOPA Cloud Actual Value Range: 1~25
RA BB); Default Value: 1
Coordin
ated
Scheduli
ng based
Power
Control

eRAN

nd
CspcAlg CspcClu MOD LOFD-0 Coordin Meaning: Indicates the mode of grouping cells into
oPara sterMod CSPCA 70208 ated clusters for CSPC. If this parameter is set to
e LGOPA TDLOF Scheduli STATIC_CONFIG, cells must be manually grouped
RA D-08020 ng based into clusters for CSPC based on site scenarios. If this
LST 3 Power parameter is set to
CSPCA Control( DYNAMIC_PARTITION_CONFIG, the centralized
LGOPA Cloud control node periodically groups cells into clusters for
RA BB); CSPC based on site scenarios. The
Coordin DYNAMIC_PARTITION_CONFIG value does not
ated take effect currently. This parameter applies only to
Scheduli LTE FDD and LTE TDD.
ng based GUI Value Range: STATIC_CONFIG(Static Config),
Power DYNAMIC_PARTITION_CONFIG(Dynamic
Control Partition Config)
Unit: None
Actual Value Range: STATIC_CONFIG,
DYNAMIC_PARTITION_CONFIG
Default Value: STATIC_CONFIG(Static Config)
CspcAlg CspcCa MOD LOFD-0 Coordin Meaning: Indicates the acceptable capacity loss
oPara pacityFa CSPCA 70208 ated percentage for a network with CSPC enabled. This
ctor LGOPA Scheduli parameter affects the gain for cell edge UEs. Set this
RA ng based parameter in heavily-loaded networks to adjust cell
LST Power downlink throughput and the downlink throughput
CSPCA Control( gain of cell edge UEs. If this parameter is set to 100,
LGOPA Cloud network capacity loss is not considered, and the
RA BB) downlink throughput gain of cell edge UEs reaches
the maximum. If this parameter is set to 0, the
capacity of heavily-loaded networks is preferentially
maintained. However, the downlink throughput gain
of cell edge UEs decreases. This parameter applies
only to LTE FDD.
Unit: %
Actual Value Range: 0~100
Default Value: 100
CellCsp CspcUe MOD LOFD-0 Coordin Meaning: Indicates the interval at which the local cell
cPara SrsCfgR CELLC 70208 ated reports its UE-specific SRS configurations to the
ptPeriod SPCPA Scheduli centralized control node. This parameter applies only
RA ng based to LTE FDD.
LST Power GUI Value Range: 1~60
CELLC Control(
Cloud Unit: s
SPCPA
RA BB) Actual Value Range: 1~60
Default Value: 1

eRAN

nd
CellCsp CspcRa MOD LOFD-0 Coordin Meaning: Indicates whether to report the changed
cPara pidRptS CELLC 70208 ated sounding reference signal (SRS) configurations of
witch SPCPA Scheduli UEs with CSPC applied in the serving cell to the
RA ng based centralized control node immediately after the
LST Power configurations are changed. This parameter applies
CELLC Control( only to LTE FDD.
SPCPA Cloud GUI Value Range: OFF(Off), ON(On)
RA BB)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CellCsp CellCsp MOD LOFD-0 Coordin Meaning: Indicates whether to enable CSPC in the
cPara cSwitch CELLC 70208 ated cell. This parameter applies only to LTE FDD and
SPCPA TDLOF Scheduli LTE TDD.
RA D-08020 ng based GUI Value Range: OFF(Off), ON(On)
LST 3 Power
Control( Unit: None
CELLC
SPCPA Cloud Actual Value Range: OFF, ON
RA BB) Default Value: OFF(Off)
Coordin
ated
Scheduli
ng based
Power
Control

eRAN

nd
CellCsp CspcCqi MOD LOFD-0 Coordin Meaning: Indicates the filtering coefficient for channel
cPara FilterCo CELLC 70208 ated quality indicators (CQIs) in CSPC-based power
eff SPCPA TDLOF Scheduli optimization. This filtering makes the reported CQIs
RA D-08020 ng based more stable. This parameter applies only to LTE FDD
LST 3 Power and LTE TDD.
CELLC Control( GUI Value Range: 0~100
TDLAO Cloud
SPCPA FD-081 Unit: None
RA BB)
411 Actual Value Range: 0~1, step:0.01
Coordin
TDLAO ated Default Value: 0
FD-110 Scheduli
408 ng based
Power
Control
Inter-
eNodeB
DL
CoMP
Based
on
Relaxed
Backhau
l
Inter-
eNodeB
DL
CoMP
Based
on
Coordin
ated
BBU
CellCsp UlRsrpR MOD LOFD-0 Coordin Meaning: Indicates the interval at which neighboring
cPara ptPeriod CELLC 70208 ated cells report their uplink reference signal received
SPCPA Scheduli power (RSRP) measurement results to the local cell.
RA ng based This parameter applies only to LTE FDD.
LST Power GUI Value Range: 1~50
CELLC Control(
Cloud Unit: 100ms
SPCPA
RA BB) Actual Value Range: 100~5000
Default Value: 10

eRAN

nd
NCellSr NCellSr MOD LOFD-0 Coordin Meaning: Indicates the offset for events related to the
sMeasPa sMeasA NCELL 70208 ated SRS automatic neighboring cell measurement or
ra 3Offset SRSME LOFD-1 Scheduli DMRS neighboring cell measurement. This offset is
ASPAR 10203 ng based the difference between the signal quality of a
A Power neighboring cell and that of the serving cell. A larger
LOFD-0 Control value of this parameter requires better signal quality
LST 01066 /
NCELL (Cloud of a neighboring cell for sending measurement reports
TDLOF BB) of the SRS automatic neighboring cell measurement
SRSME D-00106
ASPAR Coordin or DMRS neighboring cell measurement. SRS
6 automatic neighboring cell measurement applies to
A ated
LOFD-0 Scheduli LTE FDD and LTE TDD. DMRS neighboring cell
70222 ng based measurement applies only to LTE FDD.
LOFD-0 Power GUI Value Range: -30~30
70223 Control Unit: 0.5dB
(Relaxe
d Actual Value Range: -15~15
Backhau Default Value: -20
l)
Intra-
eNodeB
UL
CoMP
Intra-
eNodeB
UL
CoMP
Phase II
UL
CoMP
based on
Coordin
ated
eNodeB

eRAN

nd
NCellSr SrsAuto MOD LOFD-0 Coordin Meaning: Indicates whether a cell supports SRS
sMeasPa NCellM NCELL 70208 ated automatic neighboring cell measurements. If this
ra easSwitc SRSME LOFD-1 Scheduli parameter is set to ON(On), the
h ASPAR 10203 ng based UlHetnetCompOnUlRsrpSw and
A Power UlHetnetCompManualNcellCfgSw options of the
LOFD-0 Control UplinkCompSwitch parameter do not take effect. This
LST 01066 /
NCELL (Cloud parameter applies only to LTE FDD and LTE TDD.
TDLOF BB)
SRSME D-00106 GUI Value Range: OFF(Off), ON(On)
ASPAR 6 Coordin Unit: None
A ated
LOFD-0 Scheduli Actual Value Range: OFF, ON
70222 ng based Default Value: OFF(Off)
LOFD-0 Power
70223 Control
TDLOF (Relaxe
D-11120 d
8 Backhau
l)
Intra-
eNodeB
UL
CoMP
Intra-
eNodeB
UL
CoMP
Phase II
UL
CoMP
based on
Coordin
ated
eNodeB
Uplink
Interfere
nce
Coordin
ation

eRAN

nd
CellSrs SrsPerio MOD LBFD-0 Physical Meaning: Indicates whether to enable SRS reporting
Adaptiv dAdapti CELLS 02003 / Channel period adaptation. If this parameter is set to ON(On),
eCfg ve RSADA TDLBF Manage the SRS reporting period adaptively changes based on
PTIVEC D-00200 ment the SRS algorithm. If this parameter is set to
FG 3 OFF(Off), the SRS reporting period is specified by the
LST UserSrsPeriod parameter. This parameter applies only
CELLS to LTE FDD and LTE TDD.
RSADA GUI Value Range: OFF(Off), ON(On)
PTIVEC Unit: None
FG
Actual Value Range: OFF, ON
Default Value: ON(On)
CellSrs UserSrs MOD LBFD-0 Physical Meaning: Indicates the fixed SRS reporting period.
Adaptiv Period CELLS 02003 / Channel This parameter takes effect only when the
eCfg RSADA TDLBF Manage SrsPeriodAdaptive parameter is set to OFF(Off). This
PTIVEC D-00200 ment parameter applies only to LTE FDD and LTE TDD.
FG 3 GUI Value Range: ms5(5ms), ms10(10ms),
LST ms20(20ms), ms40(40ms), ms80(80ms),
CELLS ms160(160ms), ms320(320ms)
RSADA Unit: ms
PTIVEC
FG Actual Value Range: ms5, ms10, ms20, ms40, ms80,
ms160, ms320
Default Value: ms40(40ms)

eRAN

nd
SRSCfg SrsCfgI MOD LBFD-0 Physical Meaning: Indicates whether to configure sounding
nd SRSCF 02003 / Channel reference signal (SRS) resources for UEs in a cell.
G TDLBF Manage The value BOOLEAN_TRUE indicates that SRS
LST D-00200 ment resources are available in the cell and can be
SRSCF 3 DL 4- configured for UEs in the cell. The value
G TDLAO Layer BOOLEAN_FALSE indicates that no SRS resource is
FD-081 MIMO available in the cell, and therefore no UE in the cell is
409 Based configured with SRS resources. This parameter does
on TM9 not take effect on: (1) FDD cell that is established on
TDLEO an LBBPc and uses four or more RX antennas. (2)
FD-121 DL FDD cell that is established on an LBBPc and uses
615 Flexible extended cyclic prefix (CP) in the uplink. (3) TDD
TDLOF 3D- cell established on an LBBPc. If this parameter does
D-00104 Beamfor not take effect on a cell but SRS resources are
9 ming available in the cell, SRS resources can be configured
Single for UEs in the cell. This parameter applies only to
Streami LTE FDD and LTE TDD.
ng GUI Value Range: BOOLEAN_FALSE(False),
Beamfor BOOLEAN_TRUE(True)
ming
Unit: None
Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
Default Value: BOOLEAN_TRUE(True)

eRAN

nd
SRSCfg FddSrsC MOD LBFD-0 Physical Meaning: Indicates the allocation mode of sounding
fgMode SRSCF 02003 Channel reference signal (SRS) resources in LTE FDD. This
G LEOFD- Manage parameter must be set when the SrsCfgInd parameter
LST 111305 ment is set to BOOLEAN_TRUE(True). If the
SRSCF Virtual FddSrsCfgMode parameter is set to
G 4T4R DEFAULTMODE(Default Mode), SRS resource
allocation is activated by default after a cell is
established, and SRS resources are allocated to UEs
that access the cell. If this parameter is set to
ADAPTIVEMODE(Adaptive Mode), SRS resource
allocation can be adaptively activated or deactivated
based on the cell load. After this parameter is set to
ADAPTIVEMODE(Adaptive Mode), settings of
parameters SrsAlgoSwitch, SrsSubframeCfg, and
UserSrsPeriod do not take effect. The parameter value
ADAPTIVEMODE(Adaptive Mode) is recommended
in heavy-traffic scenarios where there is a large
number of UEs in the cell. The parameter value
ADAPTIVEMODE(Adaptive Mode) does not apply
to cells established on an LBBPc. This parameter
applies only to LTE FDD.
GUI Value Range: DEFAULTMODE(Default Mode),
ADAPTIVEMODE(Adaptive Mode)
Unit: None
Actual Value Range: DEFAULTMODE,
ADAPTIVEMODE
Default Value: ADAPTIVEMODE(Adaptive Mode)

eRAN

nd
SRSCfg SrsSubfr MOD LBFD-0 Physical Meaning: Indicates the index of the SRS subframe
ameCfg SRSCF 02003 / Channel configuration for the cell. The value SCn, where n is
G TDLBF Manage variable, represents configuration n. For example, the
LST D-00200 ment value SC0 indicates subframe configuration 0, and the
SRSCF 3 value SC1 indicates subframe configuration 1. If the
G cell operates in FDD mode, the value SC15 is
reserved. If the cell operates in TDD mode, the values
SC14 and SC15 are reserved. The reserved values
cannot be used. For the relationship between the
subframe configuration index and the cell-specific
subframe cycle/offset, see 3GPP TS 36.211. In FDD
mode, this parameter is permanently valid. In TDD
mode, this parameter is valid only if TddSrsCfgMode
is set to EXPERIENCE_FIRST. This parameter
applies only to LTE FDD and LTE TDD.
GUI Value Range: SC0(0), SC1(1), SC2(2), SC3(3),
SC4(4), SC5(5), SC6(6), SC7(7), SC8(8), SC9(9),
SC10(10), SC11(11), SC12(12), SC13(13), SC14(14)
Unit: None
Actual Value Range: SC0, SC1, SC2, SC3, SC4, SC5,
SC6, SC7, SC8, SC9, SC10, SC11, SC12, SC13,
SC14
Default Value: SC3(3)
EuCoSc PrtNode MOD TDLAO Inter- Meaning: Indicates the ID of the baseband equipment
hCfg BaseBan EUCOS FD-110 eNodeB used by the centralized clustering node. If this
dEqmId CHCFG 408 DL parameter is set to 255, the baseband equipment used
LST CoMP by the centralized clustering node is not specified.
EUCOS Based This parameter applies only to LTE FDD and LTE
CHCFG on TDD.
Coordin GUI Value Range: 0~23,255
ated
BBU Unit: None
Actual Value Range: 0~23,255
Default Value: 255
EuCoSc SchNod MOD TDLAO Inter- Meaning: Indicates the ID of the baseband equipment
hCfg eBaseBa EUCOS FD-081 eNodeB used by the centralized scheduling node. If this value
ndEqmI CHCFG 411 DL is set to 255, the baseband equipment used by the
d LST CoMP centralized scheduling node is not specified. This
EUCOS Based parameter applies only to LTE FDD and LTE TDD.
CHCFG on GUI Value Range: 0~23,255
Relaxed
Backhau Unit: None
l Actual Value Range: 0~23,255
Default Value: 255

eRAN

nd
EuCoSc WorkM MOD TDLAO Inter- Meaning:

hCfg ode EUCOS FD-081 eNodeB Indicates the coordinated scheduling working mode of
CHCFG 411 DL baseband equipment.
LST CoMP
EUCOS Based COORDINATED_SCHEDULING_ONLY: Indicates
CHCFG on that the baseband equipment provides only the
Relaxed coordinated scheduling function.
Backhau
l COORDINATED_SCHEDULING_MIXING:
Indicates that the baseband equipment provides
common baseband processing and coordinated
scheduling functions. This parameter applies only to
LTE FDD and LTE TDD.
GUI Value Range:
COORDINATED_SCHEDULING_ONLY(COORDI
NATED_SCHEDULING_ONLY),
COORDINATED_SCHEDULING_MIXING(COOR
DINATED_SCHEDULING_MIXING)
Unit: None
Actual Value Range:
COORDINATED_SCHEDULING_ONLY,
COORDINATED_SCHEDULING_MIXING
Default Value:
COORDINATED_SCHEDULING_ONLY(COORDI
NATED_SCHEDULING_ONLY)
Cluster ClusterI ADD LOFD-0 Coordin Meaning: Indicates the ID of a cluster in Cloud BB
d CLUST 70208 ated scenarios. When static clusters are configured, the
ER TDLOF Scheduli value of this parameter ranges from 0 to 999. This
LST D-08020 ng based parameter applies only to LTE FDD and LTE TDD.
CLUST 3 Power GUI Value Range: 0~65535
ER Control(
Cloud Unit: None
RMV BB) Actual Value Range: 0~65535
CLUST
ER Coordin Default Value: None
ated
Scheduli
ng based
Power
Control

eRAN

nd
Cluster ClusterT ADD TDLAO Intra- Meaning: Indicates the feature type of a cluster, which
ype CLUST FD-001 eNodeB can be CSPC, DL CoMP, CAMC, or UL ICS. This
ER 00103 DL parameter applies only to LTE TDD when it is set to
DSP LOFD-0 CoMP DLCOMP(DLCOMP), CAMC(CAMC), or
CLUST 70208 in DCS ULICS(ULICS).
ERCEL Mode GUI Value Range: CSPC(CSPC),
TDLOF
L D-08020 Coordin DLCOMP(DLCOMP), CAMC(CAMC),
LST 3 ated ULICS(ULICS)
CLUST Scheduli Unit: None
TDLOF ng based
ER D-09020 Actual Value Range: CSPC, DLCOMP, CAMC,
Power
6/ Control ULICS
TDLOF (Cloud Default Value: CSPC(CSPC)
D-11020 BB)
6
Coordin
ated
Scheduli
ng based
Power
Control
Inter-
eNodeB
Uplink
Coordin
ated
Uplink
Scheduli
ng

eRAN

nd
ClusterC ClusterI ADD LOFD-0 Coordin Meaning: Indicates the ID of a cluster in Cloud BB
ell d CLUST 70208 ated scenarios. When static clusters are configured, the
ERCEL TDLOF Scheduli value of this parameter ranges from 0 to 999. This
L D-08020 ng based parameter applies only to LTE FDD and LTE TDD.
DSP 3 Power GUI Value Range: 0~65535
CLUST Control(
Cloud Unit: None
ERCEL
L BB) Actual Value Range: 0~65535
LST Coordin Default Value: None

CLUST ated
ERCEL Scheduli
L ng based
Power
RMV Control
CLUST
ERCEL
L
DSP
CELLC
AMCST
ATUS
ClusterC Mcc ADD LOFD-0 Coordin Meaning: Indicates the mobile country code (MCC) of
ell CLUST 70208 ated the cluster cell. A public land mobile network
ERCEL TDLOF Scheduli (PLMN) ID is comprised of an MCC and a mobile
L D-08020 ng based network code (MNC). The MCC consists of three
LST 3 Power digits. The MNC consists of two to three digits. For
CLUST Control( example, if the MCC is 123 and the MNC is 45, the
ERCEL Cloud PLMN ID is 12345. This parameter applies only to
L BB) LTE FDD and LTE TDD.
RMV Coordin GUI Value Range: 3 characters
CLUST ated Unit: None
ERCEL Scheduli
ng based Actual Value Range: 000~999
L
Power Default Value: None
DSP Control
CELLC
AMCST
ATUS
DSP
CLUST
ERCEL
L

eRAN

nd
ClusterC Mnc ADD LOFD-0 Coordin Meaning: Indicates the mobile network code (MNC)
ell CLUST 70208 ated of the cluster cell. A public land mobile network
ERCEL TDLOF Scheduli (PLMN) ID is comprised of a mobile country code
L D-08020 ng based (MCC) and an MNC. The MCC consists of three
LST 3 Power digits. The MNC consists of two to three digits. For
CLUST Control( example, if the MCC is 123 and the MNC is 45, the
ERCEL Cloud PLMN ID is 12345. This parameter applies only to
L BB); LTE FDD and LTE TDD.
RMV Coordin GUI Value Range: 2~3 characters
CLUST ated Unit: None
ERCEL Scheduli
ng based Actual Value Range: 00~99,000~999
L
Power Default Value: None
DSP Control
CELLC
AMCST
ATUS
DSP
CLUST
ERCEL
L
ClusterC eNodeB ADD LOFD-0 Coordin Meaning: Indicates the eNodeB identity of the cluster
ell Id CLUST 70208 ated cell. It uniquely identifies an eNodeB within a PLMN.
ERCEL TDLOF Scheduli The 28-bit E-UTRAN cell identity is comprised of the
L D-08020 ng based cell identity and the eNodeB identity (represented by
LST 3 Power the most significant 20 bits). The cell global identity
CLUST Control( (CGI) of an E-UTRAN cell is comprised of the E-
ERCEL Cloud UTRAN cell identity and the PLMN ID. For details
L BB) about this parameter, see 3GPP TS 36.413. This
Coordin parameter applies only to LTE FDD and LTE TDD.
RMV
CLUST ated GUI Value Range: 0~1048575
ERCEL Scheduli Unit: None
L ng based
Power Actual Value Range: 0~1048575
DSP Control Default Value: None
CELLC
AMCST
ATUS
DSP
CLUST
ERCEL
L

eRAN

nd
ClusterC CellId ADD LOFD-0 Coordin Meaning: Indicates the ID of a cell in a cluster. It
ell CLUST 70208 ated uniquely identifies a cell within an eNodeB. The 28-
ERCEL TDLOF Scheduli bit E-UTRAN cell identity is comprised of the cell
L D-08020 ng based identity (represented by the least significant eight bits)
LST 3 Power and the eNodeB identity. The cell global identity
CLUST Control( (CGI) of an E-UTRAN cell is comprised of the E-
ERCEL Cloud UTRAN cell identity and the PLMN ID. For details
L BB) about this parameter, see 3GPP TS 36.413. This
Coordin parameter applies only to LTE FDD and LTE TDD.
RMV
CLUST ated GUI Value Range: 0~255
ERCEL Scheduli Unit: None
L ng based
Power Actual Value Range: 0~255
DSP Control Default Value: None
CLUST
ERCEL
L

eRAN

nd
CellAlg CqiAdj MOD LBFD-0 CQI Meaning:

oSwitch AlgoSwi CELLA 0101501 Adjustm CqiAdjAlgoSwitch: Indicates whether to allow the
tch LGOSW / ent eNodeB to adjust the UE-reported CQI based on the
ITCH TDLBF Dynami initial block error rate (IBLER). If this option is
LST D-00101 c selected, the CQI adjustment algorithm is enabled. In
CELLA 501 Scheduli this case, the eNodeB adjusts the UE-reported CQI
LGOSW LBFD-0 ng based on the IBLER. If this option is deselected, the
ITCH 0101502 DL CQI adjustment algorithm is disabled. In this case, the
/ Asynchr eNodeB does not adjust the UE-reported CQI based
TDLBF onous on the IBLER. This option applies only to LTE FDD
D-00101 HARQ and LTE TDD.
502
Optimiz StepVarySwitch: Indicates whether to enable variable-
LBFD-0 ed CFI- step-based adjustment. If this option is selected,
02005 / Calculat variable-step-based adjustment is enabled to
TDLBF ion- accelerate the convergence of IBLER. In this case,
D-00200 based rapid adjustment at large steps is applied if there is a
5 MCS large difference between the measured IBLER and
TDLOF Index target IBLER; fine-tuning at small steps is applied if
D-08123 Selectio the measured IBLER is close to the target IBLER. If
1 n this option is deselected, the adjustment is performed
at a fixed step. This option applies only to LTE FDD
and LTE TDD.
DlVarIBLERtargetSwitch: Indicates whether to enable
downlink target IBLER adaptation. If this option is
selected, the downlink target IBLER is adaptively
adjusted based on the TBS to improve spectral
efficiency. If this option is deselected, the target
IBLER is determined based on the setting of the
DlEnVarIblerTargetSwitch option of this parameter.
This option applies only to LTE FDD and LTE TDD.
TddBundlingCqiAdjOptSwitch: Indicates whether to
enable optimized CQI adjustment algorithm in ACK
bundling mode. If this option is selected, the
optimized CQI adjustment algorithm is enabled. If this
option is deselected, the optimized CQI adjustment
algorithm is disabled. This option applies only to LTE
TDD.
TddMultiplexingCqiAdjOptSwitch: Indicates whether
to enable optimized CQI adjustment in ACK
multiplexing mode. If this option is selected,
optimized CQI adjustment is enabled. If this option is
deselected, optimized CQI adjustment is disabled.
This option applies only to LTE TDD.
AdaptiveStepVarySwitch: Indicates whether to enable
adaptive step change in CQI adjustment. This option

eRAN

nd
applies only to LTE FDD and LTE TDD. If this option

is selected, the CQI adjustment is performed at a large
step when significant changes in the signal quality are
detected, accelerating the IBLER convergence. If this
option is deselected, the CQI adjustment is performed
at a fixed step.
DlCqiAdjDeltaOptSwitch: Indicates whether to
optimize CQI adjustment amount calculation. If this
option is deselected, the CQI adjustment amount is
calculated using the following formula: CQI
adjustment amount = (Number of ACKs for initial
transmissions x CQI adjustment amount per ACK +
Number of NACKs for initial transmissions x CQI
adjustment amount per NACK)/(Number of NACKs
for initial transmissions + Number of ACKs for initial
transmissions). If this option is selected, the CQI
adjustment amount is calculated using the following
formula: CQI adjustment amount = Number of ACKs
for initial transmissions x CQI adjustment amount per
ACK + Number of NACKs for initial transmissions x
CQI adjustment amount per NACK. This option
applies only to LTE FDD and LTE TDD.
DlEnVarIblerTargetSwitch: Indicates whether to
enable enhanced downlink target IBLER adaptation. If
this option is selected, the downlink target IBLER is
adaptively adjusted based on CQI fluctuation and
TBS. If this option is deselected, the downlink target
IBLER policy is controlled by the
DlVarIBLERtargetSwitch option of this parameter.
This option applies only to LTE FDD and LTE TDD.
DlRetxTbsIndexAdjOptSwitch: Indicates whether to
optimize transport block size (TBS) index adjustment
in retransmissions. If this option is selected, TBS
index adjustment in retransmissions is optimized. The
TBS index is lowered for the scheduling of the last
two retransmissions, and the TBS index is determined
based on the CQI adjustment result for the scheduling
of other retransmissions. If this option is deselected,
TBS index adjustment in retransmissions is not
optimized. The TBS index is determined based on the
CQI adjustment result for the scheduling of all
retransmissions. This option applies only to LTE FDD
and LTE TDD.
CfiConvertOptSwitch: Indicates whether to optimize
CFI conversion. If this option is selected, new CFI
calculation tables for normal and special subframes

eRAN

nd
are used to ensure more accurate MCS selection in

normal and special subframes and facilitate IBLER
convergence to the target value. If this option is
deselected, the original CFI calculation tables for
normal and special subframes are used. This option
applies only to LTE TDD.
BundlingOptThdSwitch: Indicates whether to adjust
the MCS index threshold for enabling the optimized
CQI adjustment algorithm in TDD bundling mode. If
this option is selected, the lower MCS index threshold
for enabling the optimized CQI adjustment algorithm
in TDD bundling mode is changed from MCS index 6
to MCS index 0. If this option is deselected, the lower
MCS index threshold for enabling the optimized CQI
adjustment algorithm in TDD bundling mode is MCS
index 6. This option applies only to LTE TDD.
DlSpsMcsIncreaseSwitch: Indicates whether to enable
MCS index increase for semi-persistent scheduling
(SPS). If this option is selected, MCS index increase is
enabled for SPS, reducing the number of RBs for SPS
and improving cell performance when RB resources
are limited. However, the VoLTE MOS value may
decrease. If this option is deselected, MCS index
increase is disabled for SPS, increasing the VoLTE
MOS value. However, more RBs may be consumed
for SPS. This option applies only to LTE FDD and
LTE TDD.
CqiAdjTimeEffSwitch: Indicates whether to enable
validity evaluation and adjustment for CQI
adjustment, and whether to trigger large-step-based
CQI adjustment when a long time has elapsed before a
UE begins to perform services based on the setting of
the AdaptiveStepVarySwitch option of this parameter.
If this option is selected, the eNodeB evaluates the
validity of all CQI adjustment values in a unified
manner and adjusts these adjustment values based on
the evaluation results. If this option and the
AdaptiveStepVarySwitch option are selected, large-
step-based CQI adjustment is triggered when a long
time has elapsed before a UE begins to perform
services. If this option is deselected, the eNodeB does
not evaluate the validity of CQI adjustment values or
adjust these values in a unified manner, and large-
step-based CQI adjustment is not triggered when a
long time has elapsed before a UE begins to perform
services. This option applies only to LTE TDD.

eRAN

nd
RptCqiFltInitSwitch: Indicates whether to adjust the

initial filtered value of the reported CQI. If this option
is selected, the initial filtered value of the reported
CQI is determined based on the CQI value reported by
the UE, and the filtering coefficient for the reported
CQI in the first several reporting periods is adjusted.
If this option is deselected, the initial filtered value of
CQIs reported by all UEs is fixed to 4. This option
UeSigInitCqiModSwitch: Indicates the time when the
reported initial CQI takes effect. If this option is
selected, the reported initial CQI takes effect when the
ACK to Msg4 HARQ retransmission is received or
when Msg5 is received. If this option is deselected,
the reported CQI immediately takes effect. This option
CqiFastCompstSwitch: Indicates whether the eNodeB
performs fast CQI compensation for the following
UEs: UEs handed over to cells whose values of PCI
modulo 3 conflict with source cells' values of PCI
modulo 3, beamforming UEs in 8T8R cells, and UEs
reporting aperiodic CQIs during network access under
a high CAPS condition. If this option is selected, the
eNodeB identifies these UEs and quickly compensates
for their CQIs. If this option is deselected, the eNodeB
does not identify these UEs for CQI compensation.
This option applies only to LTE TDD.
CfiConvertWiDrsSwitch: Indicates whether to
consider the DMRS overhead when converting the
control format indicator (CFI) for beamforming UEs.
If this option is selected, the eNodeB considers the
DMRS overhead when converting the CFI of
beamforming UEs. If this option is deselected, the
eNodeB does not consider the DMRS overhead when
converting the CFI of beamforming UEs in open-loop
TM7, TM8, or TM9 mode. This option applies only to
LTE FDD and LTE TDD.
IblerCqiOffsetSwitch: Indicates whether to perform
CQI compensation based on the target IBLER. The
eNodeB performs CQI compensation based on the
target IBLER only if this option is selected. This
option applies only to LTE TDD.
CqiFltOptSwitch: Indicates whether to optimize CQI
filtering. If this option is selected, the eNodeB
determines whether to discard a UE-reported CQI
based on this reported CQI and the previous HARQ

eRAN

nd
retransmission IBLER, does not filter CQIs again in

case of TM change, and triggers both large step
increase and large step decrease during step
adaptation. If this option is deselected, the eNodeB
directly uses UE-reported CQIs, filters CQIs again in
case of TM change, and triggers only large step
increase during step adaptation. This option applies
only to LTE TDD.
PreciseMcsAdaptSwitch: Indicates whether to enable
precise MCS adaptation. If this option is selected, the
eNodeB selects the TBS with a higher index for the
first downlink HARQ retransmission. In addition,
when the initial CQI adjustment amount is relatively
conservative, the eNodeB increases and compensates
for the CQI adjustment amount. If this option is
deselected, the eNodeB does not perform the
preceding operations. This option applies only to LTE
FDD.
PilotOffCqiAdjOptSwitch: Indicates CQI adaptation
optimization for CRS transmission disabling. If this
option is selected, for UEs regarded as large-packet
UEs when the BreathingPilotSwitch or
EmimoCpsSwitch option is selected, the CQI
adjustment is performed at a large step in case of
significant signal quality changes. If this option is
deselected, the CQI adjustment is performed at a fixed
step for the preceding UEs. This option applies only to
LTE FDD.
GUI Value Range:
CqiAdjAlgoSwitch(CqiAdjAlgoSwitch),
StepVarySwitch(StepVarySwitch),
DlVarIBLERtargetSwitch(DlVarIBLERtargetSwitch),
TddBundlingCqiAdjOptSwitch(TddBundlingCqiAd-
jOptSwitch), TddMultiplexingCqiAdjOptS-
witch(TddMultiplexingCqiAdjOptSwitch),
AdaptiveStepVarySwitch(AdaptiveStepVarySwitch),
DlCqiAdjDeltaOptSwitch(DlCqiAdjDeltaOptSwitch),
DlEnVarIblerTargetSwitch(DlEnVarIblerTargetS-
witch), DlRetxTbsIndexAdjOptS-
witch(DlRetxTbsIndexAdjOptSwitch),
CfiConvertOptSwitch(CfiConvertOptSwitch),
BundlingOptThdSwitch(BundlingOptThdSwitch),
DlSpsMcsIncreaseSwitch(DlSpsMcsIncreaseSwitch),
CqiAdjTimeEffSwitch(CqiAdjTimeEffSwitch),
RptCqiFltInitSwitch(RptCqiFltInitSwitch),
UeSigInitCqiModSwitch(UeSigInitCqiModSwitch),
CqiFastCompstSwitch(CqiFastCompstSwitch),

eRAN

nd
CfiConvertWiDrsSwitch(CfiConvertWiDrsSwitch),
IblerCqiOffsetSwitch(IblerCqiOffsetSwitch),
CqiFltOptSwitch(CqiFltOptSwitch),
PreciseMcsAdaptSwitch(PreciseMcsAdaptSwitch),
PilotOffCqiAdjOptSwitch(PilotOffCqiAdjOptSwitch)
Unit: None
Actual Value Range: CqiAdjAlgoSwitch,
StepVarySwitch, DlVarIBLERtargetSwitch,
TddBundlingCqiAdjOptSwitch, TddMultiplexingC-
qiAdjOptSwitch, AdaptiveStepVarySwitch,
DlCqiAdjDeltaOptSwitch, DlEnVarIblerTargetSwitch,
DlRetxTbsIndexAdjOptSwitch,
CfiConvertOptSwitch, BundlingOptThdSwitch,
DlSpsMcsIncreaseSwitch, CqiAdjTimeEffSwitch,
RptCqiFltInitSwitch, UeSigInitCqiModSwitch,
CqiFastCompstSwitch, CfiConvertWiDrsSwitch,
IblerCqiOffsetSwitch, CqiFltOptSwitch,
PreciseMcsAdaptSwitch, PilotOffCqiAdjOptSwitch
Default Value: CqiAdjAlgoSwitch:On,
StepVarySwitch:Off, DlVarIBLERtargetSwitch:Off,
TddBundlingCqiAdjOptSwitch:Off,
TddMultiplexingCqiAdjOptSwitch:Off,
AdaptiveStepVarySwitch:Off, DlCqiAdjDeltaOptS-
witch:Off, DlEnVarIblerTargetSwitch:Off,
DlRetxTbsIndexAdjOptSwitch:On,
CfiConvertOptSwitch:Off,
BundlingOptThdSwitch:Off, DlSpsMcsIncreaseS-
witch:Off, CqiAdjTimeEffSwitch:Off,
RptCqiFltInitSwitch:Off, UeSigInitCqiMod-
Switch:Off, CqiFastCompstSwitch:Off,
CfiConvertWiDrsSwitch:Off, IblerCqiOffsetS-
witch:Off, CqiFltOptSwitch:Off, PreciseMcsAdaptS-
witch:Off, PilotOffCqiAdjOptSwitch:Off
CellCsp CelleCs MOD LOFD-0 Coordin Meaning: Indicates whether to enable cell-level
cPara pcSwitc CELLC 70208 ated enhanced CSPC (eCSPC). eCSPC is enabled only
h SPCPA Scheduli when this parameter is set to ON(On). This parameter
RA ng based applies only to LTE FDD.
LST Power GUI Value Range: OFF(Off), ON(On)
CELLC Control
Unit: None
SPCPA
RA Actual Value Range: OFF, ON

eRAN

nd
CellCsp IntraEnb MOD LOFD-0 Coordin Meaning: Indicates whether to enable intra-eNodeB
cPara CspcSw CELLC 70208 ated CSPC. Intra-eNodeB CSPC is enabled only when this
SPCPA Scheduli parameter is set to ON(On). This parameter applies
RA ng based only to LTE FDD.
LST Power GUI Value Range: OFF(Off), ON(On)
CELLC Control(
Cloud Unit: None
SPCPA
RA BB) Actual Value Range: OFF, ON
CellDlsc MbsfnSf MOD LAOFD DL 2*2 Meaning: Indicates whether to configure Multimedia
hAlgo Cfg CELLD -080210 MIMO Broadcast multicast service Single Frequency
LSCHA LAOFD based on Network (MBSFN) subframes. The ten options of this
LGO -080205 TM9 parameter map to the ten MBSFN subframes. If an
LST DL 4*2 option is selected, the corresponding subframe is
CELLD MIMO configured. If an option is not selected, the
LSCHA based on corresponding subframe is not configured. PDSCH
LGO TM9 services with enhanced MIMO applied can be
scheduled on configured MBSFN subframes. This
parameter applies only to LTE FDD and LTE TDD.
GUI Value Range: SubFrame0(SubFrame0),
SubFrame1(SubFrame1), SubFrame2(SubFrame2),
SubFrame9(SubFrame9)
Unit: None
Actual Value Range: SubFrame0, SubFrame1,
SubFrame2, SubFrame3, SubFrame4, SubFrame5,
SubFrame6, SubFrame7, SubFrame8, SubFrame9
Default Value: SubFrame0:Off, SubFrame1:Off,
SubFrame2:Off, SubFrame3:Off, SubFrame4:Off,
SubFrame5:Off, SubFrame6:Off, SubFrame7:Off,
SubFrame8:Off, SubFrame9:Off

eRAN

nd
CellDlsc DlRank MOD LOFD-0 DL 2X2 Meaning:

hAlgo DetectS CELLD 01001 / MIMO Indicates whether to perform rank detection.
witch LSCHA TDLOF DL 4x4
LGO D-00100 MIMO DetectRank2AdjSwitch: If this option is deselected,
LST 1 Based the eNodeB does not perform rank 2 detection for UEs
CELLD LOFD-0 on TM3 reporting rank 1. In this case, the eNodeB performs
LSCHA 01060 / and single-codeword scheduling. If this option is selected:
LGO TDLOF TM4 (1) The eNodeB performs rank 2 detection upon
D-00106 reception of rank 1 reported by any UEs if the UE
Dual whitelist has not been configured. (2) The eNodeB
0 streamin performs rank 2 detection only upon reception of rank
TDLOF g 1 reported by whitelisted UEs if configured. The
D-00106 Beamfor StartRankDetectEffThd parameter in the
1 ming CellDlschAlgo MO, the StartRankDetectCntThd
parameter in the CellDlschAlgo MO, the
RankDetectSuccessCntThd parameter in the
CellDlschAlgo MO, and the
RankReverseDetectCntThd parameter in the
CellDlschAlgo MO take effect only when the
DetectRank2AdjSwitch option is selected.
DetectRank1AdjSwitch: If this option is deselected,
the eNodeB does not perform rank 1 detection for UEs
reporting rank 2. In this case, the eNodeB performs
dual-codeword scheduling. If this option is selected,
the eNodeB performs rank 1 detection for UEs
reporting rank 2. This option applies only to LTE
TDD. The setting of this option does not take effect
for LTE FDD but takes effect for LTE TDD.
BfDetectRank1AdjSwitch: If this option is deselected,
the eNodeB switches between the single-stream
beamforming and dual-stream beamforming modes
based on the spectral efficiency. If this option is
selected, the eNodeB attempts to switch to the single-
stream beamforming mode when it is in dual-stream
beamforming mode. This option applies only to LTE
TDD.
GUI Value Range:
DetectRank2AdjSwitch(DetectRank2AdjSwitch),
DetectRank1AdjSwitch(DetectRank1AdjSwitch),
BfDetectRank1AdjSwitch(BfDetectRank1AdjSwitch)
Unit: None
Actual Value Range: DetectRank2AdjSwitch,
DetectRank1AdjSwitch, BfDetectRank1AdjSwitch
Default Value: DetectRank2AdjSwitch:Off,
DetectRank1AdjSwitch:Off,
BfDetectRank1AdjSwitch:Off

eRAN
CSPC Feature Parameter Description 12 Counters
12 Counters
Table 12-1 Counters

Counter ID Counter Name Counter Feature ID Feature Name
Description
1526726740 L.ChMeas.PRB.DL Average number of Multi-mode: None Basic Scheduling

.Used.Avg used PDSCH PRBs GSM: None Basic Scheduling
UMTS: None Adaptive SFN/
LTE: SDMA
LBFD-002025 Virtual 4T4R
TDLBFD-002025
LOFD-070205
LEOFD-111305
1526727378 L.Traffic.User.Avg Average number of Multi-mode: None RRC Connection

users in a cell GSM: None Management
UMTS: None RRC Connection
Management
LTE:
LBFD-002007
TDLBFD-002007
1526727379 L.Traffic.User.Max Maximum number Multi-mode: None RRC Connection

of users in a cell GSM: None Management
Management
LTE:
LBFD-002007
TDLBFD-002007

eRAN

Description
1526727396 L.ChMeas.CQI.DL. Number of Multi-mode: None Dynamic Downlink

0 wideband CQI GSM: None Power Allocation
reports with the Dynamic
value of 0 UMTS: None
Scheduling
LTE:
LBFD-002016 Dynamic Downlink
Power Allocation
LBFD-00101502
TDLBFD-002016
1526727411 L.ChMeas.CQI.DL. Number of Multi-mode: None Dynamic Downlink

15 wideband CQI GSM: None Power Allocation
reports with the Dynamic
value of 15 UMTS: None
Scheduling
LTE:
LBFD-002016 Dynamic Downlink
Power Allocation
LBFD-00101502
TDLBFD-002016
1526727412 L.ChMeas.PUSCH. Number of times Multi-mode: None Basic Scheduling

MCS.0 MCS index 0 is GSM: None Modulation: DL/UL
scheduled on the QPSK, DL/UL
PUSCH UMTS: None
16QAM, DL
LTE: 64QAM
LBFD-002025
Basic Scheduling
LBFD-001005
Modulation: DL/UL
TDLBFD-002025 QPSK, DL/UL
TDLBFD-001005 16QAM, DL
64QAM
1526727443 L.ChMeas.PUSCH. Number of times Multi-mode: None Basic Scheduling

MCS.31 MCS index 31 is GSM: None Basic Scheduling
scheduled on the
PUSCH UMTS: None Modulation: DL/UL
QPSK, DL/UL
LTE:
16QAM, DL
LBFD-002025
64QAM
TDLBFD-002025 Modulation: DL/UL
LBFD-001005 QPSK, DL/UL
16QAM, DL
TDLBFD-001005
64QAM
LOFD-001006
UL 64QAM
TDLOFD-001006 UL 64QAM

eRAN

Description
1526727444 L.ChMeas.PDSCH. Number of times Multi-mode: None Basic Scheduling

PDSCH UMTS: None
16QAM, DL
LTE: 64QAM
LBFD-002025
Basic Scheduling
LBFD-001005
Modulation: DL/UL
64QAM
1526727475 L.ChMeas.PDSCH. Number of times Multi-mode: None Basic Scheduling

PDSCH UMTS: None
16QAM, DL
LTE: 64QAM
LBFD-002025
Basic Scheduling
LBFD-001005
Modulation: DL/UL
64QAM
1526728261 L.Thrp.bits.DL Total downlink Multi-mode: None Radio Bearer

traffic volume for GSM: None Management
PDCP SDUs in a Radio Bearer
cell UMTS: None
Management
LTE:
LBFD-002008 Basic Scheduling
TDLBFD-002008 Basic Scheduling
LBFD-002025
TDLBFD-002025
1526728262 L.Thrp.Time.DL Total transmit Multi-mode: None Radio Bearer

duration of GSM: None Management
downlink PDCP Radio Bearer
SDUs in a cell UMTS: None
Management
LTE:
LBFD-002025
TDLBFD-002025

eRAN

Description
1526728433 L.ChMeas.PRB.DL Number of Multi-mode: GSM and LTE FDD

.Avail available downlink MRFD-090202 Dynamic Spectrum
PRBs GSM: None Sharing(LTE FDD)
UMTS: None LTE-A Introduction

LTE: Carrier Aggregation
LAOFD-001001 for Downlink 2CC
LAOFD-001002 in 40MHz
LOFD-070205 Adaptive SFN/

SDMA
TDLOFD-001075
SFN
LEOFD-111305
Virtual 4T4R
1526728599 L.ChMeas.PRB.DL Number of PRBs on Multi-mode: None Modulation: DL/UL

.RANK1.MCS.0 the PDSCH in rank GSM: None QPSK, DL/UL
1 mode using MCS 16QAM, DL
index 0 for UMTS: None 64QAM
scheduling in a cell LTE: DL 2x2 MIMO
LBFD-001005
DL 4x2 MIMO
LOFD-001001 DL 4x4 MIMO
LOFD-001003 Modulation: DL/UL
LOFD-001060 QPSK, DL/UL
16QAM, DL
TDLBFD-001005
64QAM
TDLOFD-001001 DL 2x2 MIMO

LBFD-001005
DL 4x2 MIMO
16QAM, DL
TDLBFD-001005
64QAM

eRAN

Description

LBFD-001005
DL 4x2 MIMO
16QAM, DL
TDLBFD-001005
64QAM

LBFD-001005
DL 4x2 MIMO
16QAM, DL
TDLBFD-001005
64QAM
1526728969 L.Traffic.ActiveUse Average number of Multi-mode: None RRC Connection

r.DL.Avg activated UEs in GSM: None Management
downlink RRC Connection
UMTS: None
Management
LTE:
LBFD-002007
TDLBFD-002007
1526728970 L.Traffic.ActiveUse Maximum number Multi-mode: None RRC Connection

r.DL.Max of activated UEs in GSM: None Management
downlink RRC Connection
UMTS: None
Management
LTE:
LBFD-002007
TDLBFD-002007

eRAN

Description
1526728975 L.Traffic.ActiveUse Average number of Multi-mode: None RRC Connection

r.Avg activated UEs GSM: None Management
Management
LTE:
LBFD-002007
TDLBFD-002007
1526728976 L.Traffic.ActiveUse Maximum number Multi-mode: None RRC Connection

r.Max of activated UEs GSM: None Management
Management
LTE:
LBFD-002007
TDLBFD-002007
1526728997 L.Thrp.Time.Cell.D Total duration of Multi-mode: None Radio Bearer

L.HighPrecision downlink data GSM: None Management
transmission in a Radio Bearer
cell (with the UMTS: None
Management
precision of 1 ms) LTE:
LBFD-002025
TDLBFD-002025
1526729005 L.Thrp.bits.DL.Last Downlink traffic Multi-mode: None Radio Bearer

TTI volume sent in the GSM: None Management
last TTI for PDCP Radio Bearer
SDUs before the UMTS: None
Management
buffer is empty LTE:
LBFD-002025
TDLBFD-002025
1526729015 L.Thrp.Time.DL.R Data transmit Multi-mode: None Radio Bearer

mvLastTTI duration except the GSM: None Management
last TTI before the Radio Bearer
downlink buffer is UMTS: None
Management
empty LTE:
LBFD-002025
TDLBFD-002025

eRAN

Description
1526729056 L.Thrp.DL.BitRate. Number of samples Multi-mode: None Radio Bearer

Samp.Index0 with the downlink GSM: None Management
throughput ranging Radio Bearer
within index 0 UMTS: None
Management
LTE:
LBFD-002025
TDLBFD-002025
1526729065 L.Thrp.DL.BitRate. Number of samples Multi-mode: None Radio Bearer

Samp.Index9 with the downlink GSM: None Management
throughput ranging Radio Bearer
within index 9 UMTS: None
Management
LTE:
LBFD-002025
TDLBFD-002025
1526730141 L.ChMeas.RI.Rank Number of times Multi-mode: None Basic Scheduling

1 rank 1 is reported GSM: None DL 2x2 MIMO
UMTS: None DL 4x2 MIMO
LTE: Basic Scheduling
LBFD-002025 DL 2x2 MIMO
LOFD-001001
LOFD-001003
TDLBFD-002025
TDLOFD-001001
1526730142 L.ChMeas.RI.Rank Number of times a Multi-mode: None Basic Scheduling

2 UE reports rank 2 GSM: None DL 2x2 MIMO
UMTS: None DL 4x2 MIMO
LTE: Basic Scheduling
LBFD-002025 DL 2x2 MIMO
LOFD-001001
LOFD-001003
TDLBFD-002025
TDLOFD-001001

eRAN

Description

UMTS: None Basic Scheduling
LTE:
LBFD-002025
LOFD-001060
TDLBFD-002025

UMTS: None Basic Scheduling
LTE:
LBFD-002025
LOFD-001060
TDLBFD-002025
1526737710 L.ChMeas.CQI.DL. Accumulated value Multi-mode: None Basic Scheduling

BorderUE.Total of wideband CQIs GSM: None Basic Scheduling
reported by CEUs
UMTS: None
LTE:
LBFD-002025
TDLBFD-002025
1526737711 L.ChMeas.CQI.DL. Number of times Multi-mode: None Basic Scheduling

BorderUE.Num wideband CQIs are GSM: None Basic Scheduling
reported by CEUs
UMTS: None
LTE:
LBFD-002025
TDLBFD-002025
1526737755 L.Thrp.bits.DL.Bor Downlink PDCP- Multi-mode: None Basic Scheduling

derUE layer traffic volume GSM: None Basic Scheduling
sent for CEUs in a
cell UMTS: None
LTE:
LBFD-002025
TDLBFD-002025
1526737758 L.Thrp.bits.DL.Last Downlink PDCP- Multi-mode: None Basic Scheduling

TTI.BorderUE layer traffic volume GSM: None Basic Scheduling
sent in the last TTI
for CEUs before the UMTS: None
buffer is empty in a LTE:
cell LBFD-002025
TDLBFD-002025

eRAN

Description
1526737759 L.Thrp.Time.DL.R Data transmission Multi-mode: None Basic Scheduling

mvLastTTI.Border duration for CEUs GSM: None Basic Scheduling
UE except the last TTI
before the downlink UMTS: None
buffer is empty LTE:
LBFD-002025
TDLBFD-002025
1526739801 L.Traffic.HighGeo Number of UEs Multi-mode: None Coordinated

metry.User.Avg with high geometry GSM: None Scheduling based
factor Power Control
UMTS: None
LTE:
LOFD-070208
1526739802 L.Traffic.LowGeom Number of UEs Multi-mode: None Coordinated

etry.User.Avg with low geometry GSM: None Scheduling based
factors Power Control
UMTS: None
LTE:
LOFD-070208
1526741760 L.Thrp.Time.DL.Bo Total duration of Multi-mode: None Basic Scheduling

rderUE sending data to cell GSM: None Basic Scheduling
edge UEs in the
downlink at the UMTS: None
PDCP layer in a LTE:
cell LBFD-002025
TDLBFD-002025
1526741763 L.ChMeas.PRB.PU Average number of Multi-mode: None Basic Scheduling

SCH.Avg.BorderU PUSCH PRBs GSM: None Basic Scheduling
E occupied by CEUs
in a cell UMTS: None
LTE:
LBFD-002025
TDLBFD-002025
1526741767 L.ChMeas.PRB.PD Average number of Multi-mode: None Basic Scheduling

SCH.Avg.BorderU PDSCH PRBs GSM: None Basic Scheduling
E occupied by CEUs
in a cell UMTS: None
LTE:
LBFD-002025
TDLBFD-002025

eRAN

Description
1526741768 L.Traffic.DL.SCH. Number of TBs Multi-mode: None Transport Channel

TB.BorderUE initially transmitted GSM: None Management
to cell edge UEs on Transport Channel
the downlink SCH UMTS: None
Management
LTE:
LBFD-002002
TDLBFD-002002
1526741769 L.Traffic.DL.SCH. Number of Multi-mode: None Transport Channel

ErrTB.Ibler.Border downlink erroneous GSM: None Management
UE TBs after initial Transport Channel
transmission to cell UMTS: None
Management
edge Ues LTE:
LBFD-002002
TDLBFD-002002
1526741770 L.Traffic.DL.SCH. Number of Multi-mode: None Transport Channel

ErrTB.Rbler.Border downlink erroneous GSM: None Management
UE TBs after the Transport Channel
maximum number UMTS: None
Management
of retransmissions LTE:
to cell edge UEs is LBFD-002002
reached TDLBFD-002002
1526741772 L.Traffic.PdschPA. Number of samples Multi-mode: None Adaptive Inter-Cell

Samp.Index0 with the downlink GSM: None Interference
PDSCH PA equal to Coordination
index 0 UMTS: None
Coordinated
LTE: Scheduling based
LOFD-060201 Power Control
LOFD-070208
1526741779 L.Traffic.PdschPA. Number of samples Multi-mode: None Adaptive Inter-Cell

Samp.Index7 with the downlink GSM: None Interference
PDSCH PA equal to Coordination
index 7 UMTS: None
Coordinated
LTE: Scheduling based
LOFD-060201 Power Control
LOFD-070208
1526741888 L.Traffic.User.Bord Average number of Multi-mode: None Basic Scheduling

erUE.Avg CEUs in a cell GSM: None Basic Scheduling
UMTS: None
LTE:
LBFD-002025
TDLBFD-002025

eRAN

Description
1526741889 L.Traffic.User.Bord Maximum number Multi-mode: None Basic Scheduling

erUE.Max of CEUs in a cell GSM: None Basic Scheduling
UMTS: None
LTE:
LBFD-002025
TDLBFD-002025
1526741890 L.Traffic.User.Intra Average number of Multi-mode: None Basic Scheduling

Board.BorderUE.A intra-BBP CEUs in GSM: None Basic Scheduling
vg a cell
UMTS: None
LTE:
LBFD-002025
TDLBFD-002025
1526741891 L.Traffic.User.Intra Average number of Multi-mode: None Basic Scheduling

BBUInterBoard.Bor intra-BBU inter- GSM: None Basic Scheduling
derUE.Avg BBP CEUs in a cell
UMTS: None
LTE:
LBFD-002025
TDLBFD-002025
1526741892 L.Traffic.User.Inter Average number of Multi-mode: None Basic Scheduling

BBU.BorderUE.Av inter-BBU CEUs in GSM: None Basic Scheduling
g a cell
UMTS: None
LTE:
LBFD-002025
TDLBFD-002025
1526742073 L.ChMeas.PRB.DL Average number of Multi-mode: None Coordinated

.IntraEnbCspc.Used PRBs used by UEs GSM: None Scheduling based
.Avg on which downlink Power Control
intra-eNodeB CSPC UMTS: None
takes effect in a cell LTE:
LOFD-070208

eRAN
CSPC Feature Parameter Description 13 Glossary
13 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
CSPC Feature Parameter Description 14 Reference Documents
14 Reference Documents
1. 3GPP TS 36.331: "Radio Resource Control (RRC); Protocol specification"

2. Synchronization Feature Parameter Description
3. Scheduling Feature Parameter Description
4. eX2 Self-Management Feature Parameter Description
5. USU3910-based Multi-BBU Interconnection Feature Parameter Description
6. Cloud BB Overview Feature Parameter Description


CSPC (eRAN12.1 03)

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

CSPC (eRAN12.1 03)

Diunggah oleh

Hak Cipta:

Format Tersedia

eRAN

CSPC Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2017-08-30) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

8 Engineering Guidelines for CSPC........................................................................................... 29

Issue 03 (2017-08-30) Huawei Proprietary and Confidential ii

9 Engineering Guidelines for eCSPC......................................................................................... 46

10 Engineering Guidelines for Intra-eNodeB CSPC............................................................... 58

Issue 03 (2017-08-30) Huawei Proprietary and Confidential iii

Issue 03 (2017-08-30) Huawei Proprietary and Confidential iv

1 About This Document

1.2 Intended Audience

1.3 Change History

Issue 03 (2017-08-30) Huawei Proprietary and Confidential 1

Change Change Description Parameter Affected Entity

Feature None None N/A

Editorial Added the conditions for the None N/A

Revised descriptions in this None N/A

Change Change Description Parameter Affected Entity

Feature None None N/A

Editorial Revised 8.1 When to Use and None N/A

Added the mutual exclusivity None N/A

Issue 03 (2017-08-30) Huawei Proprietary and Confidential 2

Change Change Description Parameter Affected Entity

Feature None None N/A

Editorial Revised descriptions in this None N/A

eRAN12.1 Draft A (2016-12-30)

Change Change Description Parameter Change Affected

Feature l Added the impact of eMTC None Macro, micro,

Editorial None None N/A

Issue 03 (2017-08-30) Huawei Proprietary and Confidential 3

1.4 Differences Between eNodeB Types

LOFD-07020 Coordinated Yes Yes Yes

"Micro eNodeBs" refers to the following models:

Function Implementation in Macro, Micro, and LampSite eNodeBs

CSPC Yes No Yes

eCSPC Yes Yes Yes

Intra-eNodeB CSPC Yes Yes Yes

Issue 03 (2017-08-30) Huawei Proprietary and Confidential 4

Figure 2-1 Intra-frequency cells in a densely populated urban area

Issue 03 (2017-08-30) Huawei Proprietary and Confidential 5

Figure 2-2 Example of time-domain transmit power coordination

Table 2-1 Deployment requirements and application scenarios

CSPC Universal switching units An operator requires fast interference

eCSPC USUs and centralized control An operator allows interference

Intra-eNodeB USUs and centralized control An operator requires interference

These functions can be deployed individually or in combinations. Note that:

Issue 03 (2017-08-30) Huawei Proprietary and Confidential 6

Figure 2-3 Network architecture for CSPC (macro network)

Issue 03 (2017-08-30) Huawei Proprietary and Confidential 7

Figure 2-4 Network architecture for CSPC (HetNet)

Figure 2-5 Network architecture for CSPC (LampSite network)

The following describes the functions of each entity involved in CSPC:

Issue 03 (2017-08-30) Huawei Proprietary and Confidential 8

Issue 03 (2017-08-30) Huawei Proprietary and Confidential 9

Figure 2-7 Network architecture for eCSPC

Issue 03 (2017-08-30) Huawei Proprietary and Confidential 10

3.1 Clustering for CSPC

Figure 3-1 Definition of a cluster

Cluster-Level CSPC Triggering