Beruflich Dokumente
Kultur Dokumente
Issue 02
Date 2016-04-20
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.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview......................................................................................................................................... 4
2.1 Introduction.................................................................................................................................................................... 4
2.2 Benefits........................................................................................................................................................................... 4
2.3 Architecture.................................................................................................................................................................... 5
3 Feature Principles.......................................................................................................................... 7
3.1 Joint-Scheduling-based SFN.......................................................................................................................................... 7
3.2 Adaptive SFN/SDMA.....................................................................................................................................................9
3.2.1 Introduction................................................................................................................................................................. 9
3.2.2 UE Attribute Determination...................................................................................................................................... 10
3.2.3 Adaptive Resource Scheduling..................................................................................................................................13
3.3 PDCCH Enhancement in Adaptive SFN/SDMA......................................................................................................... 15
3.3.1 PDCCH DCS in Adaptive SFN/SDMA.................................................................................................................... 15
3.3.2 PDCCH SDMA in Adaptive SFN/SDMA.................................................................................................................17
3.4 Coordination Between Adaptive SFN/SDMA and Multiple-Antenna Techniques......................................................19
3.4.1 Inter-RRU CBF in Adaptive SFN/SDMA.................................................................................................................19
3.4.2 MU-Beamforming in Adaptive SFN/SDMA............................................................................................................ 21
3.4.3 Adaptive SFN/SDMA+MU MIMO...........................................................................................................................21
9 Network Impact........................................................................................................................... 45
9.1 TDLOFD-001075 SFN.................................................................................................................................................45
9.2 TDLOFD-002008 Adaptive SFN/SDMA.................................................................................................................... 45
9.3 TDLOFD-001098 Inter-BBP SFN............................................................................................................................... 46
9.4 TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA................................................................................................... 46
9.5 TDLOFD-001080 Inter-BBU SFN...............................................................................................................................47
9.6 TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA.................................................................................................. 47
9.7 TDLOFD-070227 PDCCH DCS in SFN......................................................................................................................48
9.8 TDLOFD-081221 PDCCH SDMA in SFN..................................................................................................................48
10 Engineering Guidelines........................................................................................................... 49
10.1 When to Use SFN....................................................................................................................................................... 49
10.2 Required Information................................................................................................................................................. 54
10.2.1 Traffic Requirements and Distribution of Interference Areas................................................................................. 54
10.2.2 Interference eNodeB and LBBP Configurations..................................................................................................... 54
10.3 Planning...................................................................................................................................................................... 55
10.4 Deployment of Intra- and Inter-BBP SFN Techniques...............................................................................................59
10.4.1 Requirements........................................................................................................................................................... 59
10.4.2 Precautions...............................................................................................................................................................62
10.4.3 Hardware Adjustment..............................................................................................................................................64
10.4.4 Data Preparation and Feature Activation.................................................................................................................64
10.4.4.1 Data Preparation................................................................................................................................................... 64
10.4.4.2 Using the CME..................................................................................................................................................... 82
10.4.4.3 Using MML Commands....................................................................................................................................... 82
10.4.5 Activation Observation............................................................................................................................................88
10.4.6 Deactivation.............................................................................................................................................................88
10.4.6.1 Using the CME..................................................................................................................................................... 88
10.4.6.2 Using MML Commands....................................................................................................................................... 88
10.5 Deployment of Inter-BBU SFN Techniques...............................................................................................................88
10.5.1 Requirements........................................................................................................................................................... 89
10.5.2 Precautions...............................................................................................................................................................91
10.5.3 Hardware Adjustment..............................................................................................................................................93
10.5.4 Data Preparation and Feature Activation.................................................................................................................93
10.5.4.1 Data Preparation................................................................................................................................................... 93
10.5.4.2 Using the CME..................................................................................................................................................... 96
10.5.4.3 Using MML Commands....................................................................................................................................... 96
10.5.5 Activation Observation..........................................................................................................................................103
10.5.6 Deactivation...........................................................................................................................................................103
11 Parameters................................................................................................................................. 115
12 Counters.................................................................................................................................... 154
13 Glossary..................................................................................................................................... 174
14 Reference Documents............................................................................................................. 175
1.1 Scope
This document describes the single frequency network (SFN) feature, including its technical
principles, related features, network impact, and engineering guidelines.
This document covers the following features:
l TDLOFD-001075 SFN
l TDLOFD-002008 Adaptive SFN/SDMA
l TDLOFD-001098 Inter-BBP SFN
l TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA
l TDLOFD-001080 Inter-BBU SFN
l TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA
l TDLOFD-070227 PDCCH DCS in SFN
l TDLOFD-081221 PDCCH SDMA in SFN
Any managed objects (MOs), parameters, alarms, or counters described in this document
correspond to the software release delivered with this document. Any future updates will be
described in the product documentation delivered with future software releases.
This document applies only to LTE TDD. Any "LTE" in this document refers to LTE TDD,
and "eNodeB" refers to DBS3900 and LampSite eNodeB.
LampSite eNodeBs support only the 2T2R mode, but do not support adaptive SFN/SDMA
and multiple-antenna techniques described in 3.4 Coordination Between Adaptive SFN/
SDMA and Multiple-Antenna Techniques.
2 Overview
2.1 Introduction
Co-channel interference is a critical problem on intra-frequency networks. This problem is
more critical at the cell edge where the signal to interference plus noise ratio (SINR) is low
for some users. In dense urban areas where sites are densely deployed to ensure network
coverage, interference is severe on control channels between cells, reducing coverage of
control channels. Inter-eNodeB interference also deteriorates the performance of traffic
channels. When interference is severe, high-order modulation schemes cannot be used and
LTE advantages are compromised.
To mitigate the previous interference, Single Frequency Network (SFN) is introduced. SFN
allows two to seven RRUs to serve an SFN cell, changing the original cell edges into the SFN
cell center. For details about how to deploy multiple RRUs to serve one SFN cell, see 10.3
Planning.
2.2 Benefits
The SFN feature converts inter-RRU interference into desired signals. Large-scale SFN
deployment improves the SINR of the entire network. For example:
l The average SINRs on the PDCCH and PDSCH increase by 2 dB to 3 dB when three
RRUs serve an SFN cell in a typical dense urban area.
l The average SINRs on the PDCCH and PDSCH increase by 5 dB to 6 dB when three
RRUs serve an SFN cell in a typical dense urban area.
The SFN feature also increases the cell coverage area and handover success rate, and reduces
the number of handovers and service drop rate.
Enabling the SFN feature, however, decreases the overall system capacity to some extent.
Compared with the throughput of three single-RRU cells in a common network, the average
cell throughput decreases to about 51% in the downlink when three RRUs serve an SFN cell
in a typical dense urban area and the load ratio is 100%.
To maintain system capacity, adaptive SFN/SDMA is adopted. The average cell throughput
decreases to about 85% in the downlink when three RRUs serve an SFN cell in a typical
dense urban area and the load ratio is 100%.
2.3 Architecture
Based on scheduling modes, SFN features are classified into two types, as described in Table
2-1.
Based on connections between RRUs and BBPs, SFN features are classified into three types,
as described in Table 2-2.
3 Feature Principles
Figure 3-1 Comparison between the common networking mode and the SFN networking
mode
In the downlink, the RRUs serving an SFN cell use the same time-frequency resource to
transmit the same data on downlink physical channels. Compared with the common
networking mode, the SFN networking mode prevents interference on control channels
between RRUs and enhances the signal quality by combining received signals.
In the uplink, all RRUs serving the SFN cell receive data transmitted on the physical random
access channel (PRACH) and also sounding reference signals (SRSs). Selective reception or
joint reception is adopted for receiving data transmitted on the physical uplink shared channel
(PUSCH). However, only selective reception is adopted for receiving data transmitted on the
physical uplink control channel (PUCCH).
l For physical random access channel (PRACH) data and sounding reference signals
(SRSs), all the RRUs serving the SFN cell are used for data reception.
l For physical uplink shared channel (PUSCH) and physical uplink control channel
(PUCCH) data, only the target RRU is used for data reception. The target RRU is
determined by the eNodeB based on the measured channel quality of the UE.
In eRAN TDD 7.0, the TTI-level layer-2 selective reception function is introduced. With
this function, multiple working RRUs of a UE demodulate PUSCH data for the UE and
then report the demodulation results to the MAC layer. Based on the demodulation
results, the MAC layer combines the correctly demodulated PUSCH data. Layer-2
selective reception improves uplink coverage.
Layer-2 selective reception applies only to 10 MHz or 20 MHz SFN cells served by
4T4R/8T8R RRUs. The SFNULL2SELECTIVERCVSWITCH option in the
CellAlgoSwitch.SfnAlgoSwitch parameter specifies whether layer-2 selective reception
is enabled.
When SFNULL2SELECTIVERCVSWITCH is set to ON, layer-2 selective
reception is enabled and the working RRUs selectively receive PUSCH data at the
MAC layer.
3.2.1 Introduction
Adaptive SFN/SDMA enables the RRUs serving an SFN cell to determine scheduling modes
based on UE attributes. It helps to increase the spectral efficiency while maintaining system
capacity. Adaptive SFN/SDMA supports the following scheduling modes:
l Joint scheduling: Some or all RRUs in an SFN cell use the same time-frequency resource
to transmit the same data to a UE and receive data for selective or joint demodulation
and detection. This mode applies to UEs served by multiple RRUs.
l Independent scheduling: UEs served by different RRUs use the same time-frequency
resource to transmit and receive their own data. This mode applies to UEs served by only
one RRU.
NOTE
When space division multiple access (SDMA) is adopted in an SFN cell, the RRUs serving the
SFN cell use the same time-frequency resource to transmit or receive different data.
from RRU group B to RRU group A and calculates the isolation again. The eNodeB
repeats the moving and calculation until the isolation is greater than the specified
threshold. When the isolation is greater than the specified threshold, the RRUs
contained in RRU group A form the working RRU list of the UE.
NOTE
When adaptive SFN/SDMA is enabled, the SFN cell can use a fixed isolation decision threshold or
an isolation decision threshold that is adjusted based on load status. The
CellAlgoSwitch.SfnLoadBasedAdptSwitch parameter specifies which threshold is used in an SFN
cell.
l When this parameter is set to OFF, the SFN cell adopts a fixed isolation decision threshold.
l When this parameter is set to ON, the SFN cell adopts an isolation decision threshold that is
adjusted based on load status. The eNodeB periodically measures and updates the load status
of a cell. The period is specified by the CELLDLSCHALGO.SfnDlLoadPeriod parameter.
When the network load is light, SFN cells adopt a high isolation decision threshold to make
full use of RRU resources, improving user experience. When the network load is heavy, SFN
cells adopt a low isolation decision threshold to facilitate spatial multiplexing, improving
spectral efficiency.
In eRAN8.1, load-based adaptive adjustment is determined by the SFN downlink two-load-level
adaption switch SfnDl2LoadLevelAdptSwitch in the CellAlgoSwitch.SfnAlgoSwitch parameter.
When the SFN load-based adaption switch (CellAlgoSwitch.SfnLoadBasedAdptSwitch) is on:
l If SfnDl2LoadLevelAdptSwitch in the CellAlgoSwitch.SfnAlgoSwitch parameter is set to
OFF, load levels are not differentiated for SFN cells in the downlink.
l If SfnDl2LoadLevelAdptSwitch in the CellAlgoSwitch.SfnAlgoSwitch parameter is set to
ON, two load levels are adaptively adjusted for SFN cells in the downlink. Two load levels are
light load and heavy load. SFN cells in light load adopt a high decision threshold to make full
use of RRU resources, improving user experience. SFN cells in heavy load adopt a low
decision threshold to facilitate spatial multiplexing, increasing spectral efficiency. The
threshold for switching from light load to heavy load is specified by the
CELLDLSCHALGO.SfnDlHighLoadThd parameter. The threshold for switching from
heavy load to light load is specified by the CELLDLSCHALGO.SfnDlLowLoadThd
parameter.
5. Determines UE attributes based on the number of RRUs in the working RRU list of the
UE.
If the working RRU list contains only one RRU, the UE is an independent-
scheduling UE.
If the working RRU list contains multiple RRUs, the UE is a joint-scheduling UE.
When adaptive SFN/SDMA is enabled, the SFN cell can use a fixed isolation decision threshold or
an isolation decision threshold that is adjusted based on load status. The
CellAlgoSwitch.SfnLoadBasedAdptSwitch parameter specifies which threshold is used in an SFN
cell.
l When this parameter is set to OFF, the SFN cell adopts a fixed isolation decision threshold.
l When this parameter is set to ON, the SFN cell adopts an isolation decision threshold that is
adjusted based on load status. The eNodeB periodically measures and updates the load status
of a cell. The period can be set in the CELLULSCHALGO.SfnUlLoadPeriod parameter.
When the network load is light, SFN cells adopt a high isolation decision threshold to make
full use of RRU resources, improving user experience. When the network load is heavy, SFN
cells adopt a low isolation decision threshold to facilitate spatial multiplexing, improving
spectral efficiency.
5. Determines UE attributes based on the number of RRUs contained in the working RRU
list of the UE.
If the working RRU list contains only one RRU, the UE is an independent-
scheduling UE.
If the working RRU list contains multiple RRUs, the UE is a joint-scheduling UE.
l Independent scheduling
In independent scheduling mode, only the target RRU of a UE allocates resources to the
UE, and other RRUs in the SFN cell allocate the same time-frequency resource to other
UEs. Independent-scheduling UEs use the same time-frequency resource to transmit and
receive their own data. Independent scheduling applies to UEs located at the centers of
the original common cells, such as UE 3, UE 4 and UE 5 shown in Figure 3-5. UE 3, UE
4 and UE 5 use the same time-frequency resource to receive the data sent by RRU 1,
RRU 2 and RRU 3, respectively. In the uplink, UE 3 and UE 4 use the same time-
frequency resource to receive data from RRU 1 and RRU 2, respectively.
In Figure 3-6, the blocks in blue, red, and yellow represent different time-frequency
resources. In the left part where joint transmission is used, three RRUs allocate the same time-
frequency resources to a UE. In the right part where independent scheduling is used, only one
RRU allocates time-frequency resources to a UE and different RRUs allocate the same time-
frequency resource to different UEs.
NOTE
In eRAN11.0, downlink adaptive resource scheduling is optimized so that SFN downlink scheduling
attributes are determined by SfnDlSchAttriAdjsSwitch in the CellAlgoSwitch.SfnAlgoSwitch
parameter. If SfnDlSchAttriAdjsSwitch in the CellAlgoSwitch.SfnAlgoSwitch parameter is set to ON
when CellAlgoSwitch.SfnLoadBasedAdptSwitch is turned on and SfnDl2LoadLevelAdptSwitch in the
CellAlgoSwitch.SfnAlgoSwitch parameter is turned on, the eNodeB dynamically adjusts scheduling
attributes and resource allocation for UEs in an SFN cell at each TTI based on the cell load status and
the distribution of UE attributes, decreasing scheduling delay for UEs.
In Figure 3-7, the blocks in blue, red, and yellow represent different time-frequency
resources. In the left part where selective reception is used, three RRUs allocate the same
time-frequency resource to a UE and the UE receives data only from one RRU or jointly
receives data from multiple RRUs. In the right part where independent scheduling is enabled,
three UEs use the same time-frequency resource to transmit data to their target RRUs.
eRAN7.0 introduces layer-2 selective reception in addition to uplink selective reception. For
details about layer-2 selective reception, see 3.1 Joint-Scheduling-based SFN.
eRAN8.1 introduces uplink joint reception in addition to uplink selective reception and
layer-2 selective reception. For details about uplink joint reception, see 3.1 Joint-Scheduling-
based SFN.
Figure 3-8 Comparison between the networking with PDCCH DCS in SFN disabled and that
with PDCCH DCS in SFN enabled
In the network shown in Figure 3-8, UE1 is located at the edges of cells 1 and 2, and UE2 is
located in cell2 and is far away from cell1.
l When PDCCH DCS in SFN is not enabled, all the RRUs serving cell1 transmit PDCCH
data to UE1 and all the RRUs serving cell2 transmit PDCCH data to UE2. In this
situation, UE1 receives PDCCH data from both cells 1 and 2 and PDCCH data received
from cell2 causes interference to UE1.
l When PDCCH DCS in SFN is enabled, all the working RRUs of a UE are allocated
normal transmit power to transmit PDCCH data and the other RRUs are not allocated
transmit power. In the network shown in Figure 3-8, UE1 receives PDCCH data only
from RRU3 and UE2 only from RRUs 4 and 6, thereby mitigating PDCCH interference
caused by cell2 to UE1.
NOTE
When PDCCH DCS in SFN is enabled, RRUs use different CCE resources to transmit PDCCH data to
different UEs.
The procedure for determining the working RRU list in PDCCH DCS in SFN mode is similar
to that used in adaptive SFN/SDMA mode. In the procedure, the eNodeB determines the
working RRU list as follows:
1. Calculates the equivalent RSRP values of the signals that each RRU sends to the UE
based on the RSRP values of the signals that the UE sends to the RRUs in the SFN cell.
2. Arranges the RRUs in descending order of downlink equivalent RSRP values.
3. Selects the RRU with the largest equivalent RSRP value as the target RRU of the UE.
4. Determines the working RRU list based on the isolation.
a. Arranges the RRUs with the largest equivalent RSRP value into RRU group A and
the other RRUs into RRU group B, and then calculates the isolation between RRU
groups A and B. The isolation equals the ratio of the total RSRP of RRU group A to
the total RSRP of RRU group B.
b. Moves the RRU with the second largest equivalent RSRP value from RRU group B
to RRU group A and calculates the isolation again if the isolation is less than the
isolation threshold specified by the CellPdcchAlgo.SfnPdcchDcsThd parameter. In
this way, the eNodeB calculates the isolation until it exceeds the isolation threshold.
When the isolation exceeds the isolation threshold, the RRUs contained in RRU
group A form the working RRU list of the UE.
NOTE
l The working RRU list can be determined only when adaptive SFN/SDMA is enabled. Therefore,
PDCCH DCS in SFN depends on adaptive SFN/SDMA but does not work together with PDCCH
SDMA in SFN.
l If PDCCHAggLvlAdaptStrage is set to STRATEGYBASEDONCOVERAGE, the eNodeB
determines that the working RRUs on PDCCH demodulation for UEs providing HARQ feedback in
multiplexing mode, UEs of PUCCH format 3, and UEs of PUCCH format 1bcs are all RRUs serving
the SFN cell. This ensures that the PDCCH demodulation performance of UEs does not deteriorate.
Figure 3-9 Comparison between the networking with PDCCH SDMA in SFN disabled and
that with PDCCH SDMA in SFN enabled
In the network shown in Figure 3-9, UE1 is located in the cover area of RRU1 in cell1 and is
far from other RRUs. UE2 is located in the cover area of RRU2 in cell1 and is far from other
RRUs. UE3 is located in the cover area of RRU4 in cell2 and is far from other RRUs. UE4 is
located in the edge area covered by both RRU5 and RRU6 in cell2.
l When PDCCH SDMA in SFN is not enabled, all the RRUs serving cell1 transmit
PDCCH data to UE1 and UE2 and all the RRUs serving cell2 transmit PDCCH data to
UE3 and UE4.
l When PDCCH SDMA in SFN is enabled, the eNodeB allocates PDCCH resources and
transmits PDCCH signals to a UE in the SFN cell only on the working RRUs of the UE.
PDCCH CCE resources of different RRUs in the SFN cell can be reused by UEs. As
shown in Figure 3-9, UE1 receives only the PDCCH signals transmitted by RRU1 in
cell1 and UE2 receives only the PDCCH signals transmitted by RRU2 in cell1. UE1 and
UE2 can reuse the CCE resources of cell1. UE3 receives only the PDCCH signals
transmitted by RRU4 in cell2 and UE4 receives only the PDCCH signals transmitted by
RRU5 and RRU6 in cell1. UE3 and UE4 can reuse the CCE resources of cell2.
NOTE
When PDCCH SDMA in SFN is enabled, RRUs reuse CCE resources to transmit PDCCH data to
different UEs.
As the key of the PDCCH SDMA in SFN feature, the procedure for determining the working
RRU list is similar with that for determining the working RRU list in PDCCH DCS in
Adaptive SFN/SDMA. For details, see 3.3.1 PDCCH DCS in Adaptive SFN/SDMA. The
isolation judgment threshold is specified in the CellPdcchAlgo.SfnPdcchSdmaThd
parameter.
NOTE
The working RRU list can be determined only when adaptive SFN/SDMA is enabled. Therefore,
PDCCH SDMA in SFN depends on adaptive SFN/SDMA but does not work together with PDCCH
DCS in SFN.
If PDCCHAggLvlAdaptStrage is set to STRATEGYBASEDONCOVERAGE, the eNodeB
determines that the working RRUs on PDCCH demodulation for UEs providing HARQ feedback in
multiplexing mode, UEs of PUCCH format 3, and UEs of PUCCH format 1bcs are all RRUs serving the
SFN cell. This ensures that the PDCCH demodulation performance of UEs does not deteriorate.
Figure 3-10 shows an SFN cell served by RRUs 0, 1, and 2. UE 1 resides in the overlapping
coverage area of the three RRUs. By taking RRU 1 as its target RRU, UE 1 can also receive
strong signals from RRUs 0 and 2 simultaneously. UE 2 resides in the coverage area of RRU
2. Spatial multiplexing is performed between UE 1 and UE 2. In addition, CBF directs strong
signals to UE 2 and directs nulls to UE 1 by adjusting weights. This mitigates the interference
on UE 1 and generates only little signal loss for UE 2. As a result, the throughput of the SFN
cell increases.
As shown in Figure 3-11, UE 1 resides in the overlapping coverage area of RRUs 0, 1, and 2
while UE 2 resides in the overlapping coverage area of RRUs 1 and 2. Spatial multiplexing is
performed between UE 1 and UE 2. CBF directs strong signals transmitted by RRU 2 to UE 2
and directs nulls to UE 1 by adjusting weights. In addition, CBF directs strong signals
transmitted by RRU 1 to UE 1 and directs nulls to UE 2 by adjusting weights. These measures
mitigate the mutual signal interference between UE 1 and UE 2 and increase the throughput of
the SFN cell.
The maximum number of RRUs serving an intra-BBP SFN cell depends on the BBP
processing capabilities. For details, see 10.3 Planning.
With inter-BBP SFN techniques, a maximum of seven RRUs connected to different LBBPs in
a BBU can be combined to serve an SFN cell. Compared with an SFN cell served by three
RRUs, the SFN cell served by seven RRUs increases the average SINR on the PDCCH and
PDSCH.
For an inter-BBP SFN cell, the primary BBP processes both Layer-2 and Layer-1 data and the
secondary BBPs process only Layer-1 data. Layer-1 data of each RRU is processed on the
connected BBP, which can be the primary or secondary BBP. Layer-2 data of all RRUs are
processed only on the primary BBP.
When an inter-BBP SFN cell is activated, the eNodeB automatically selects a BBP as the
primary BBP of the inter-BBP SFN cell. After the SFN cell is activated, information about the
primary BBP can be queried by running the DSP CELL command.
Application Scenarios
When multiple BBUs are deployed in the same equipment room, the RRUs connected to
different BBUs may be required to serve an SFN cell during network reconstruction and
capacity expansion. When BBUs are interconnected using a universal switching unit (USU),
and with the proper software configuration, inter-BBU SFN techniques allow RRUs, that are
connected to different BBUs, to serve a single SFN cell. This minimizes the changes in
physical connections between RRUs and BBUs during SFN network reconstruction, reducing
the need of on-site O&M.
Inter-BBU SFN techniques cover TDLOFD-001080 Inter-BBU SFN and TDLOFD-001082
Inter-BBU Adaptive SFN/SDMA. Inter-BBU SFN is based on inter-BBU interconnection.
Different BBUs are interconnected using USU3900 or USU3910 so that RRUs that are
connected to different BBUs can be combined to serve an SFN cell. Figure 6-1 shows an
inter-BBU SFN cell when BBUs are interconnected using a USU3900.
With inter-BBU SFN techniques, a maximum of seven RRUs connected to BBPs in different
BBUs can serve an SFN cell. Compared with an SFN cell served by three RRUs, the SFN cell
served by seven RRUs increases the average SINR on the PDCCH and PDSCH.
NOTE
Reliability
For inter-BBU SFN, the BBU on which the SFN cell is set up is known as the primary BBU
and the other BBUs are known as secondary BBUs.
NOTE
When an SFN cell is set up by running the ADD CELL command on the primary eNodeB, the
Cell.EuCellStandbyMode parameter must be set to ACTIVE(Active). In addition, engineers must run
the ADD SFNCELLBIND command on the primary eNodeB to specify auxiliary eNodeBs for the SFN
cell.
The primary BBU houses the primary BBP of the SFN cell. After an inter-BBU SFN cell is
activated, the information about the primary BBP can be queried by running the DSP CELL
command on the primary BBU.
To enable the RRUs connected to secondary BBUs to serve an SFN cell, the SFN cell and the
sector equipment of the secondary BBUs must be associated by running the ADD
SFNAUXRESBIND command on each secondary BBU.
To prevent service interruptions caused by the unavailability of all RRUs and improve service
reliability in an inter-BBU SFN cell, a standby cell can be added by running the ADD CELL
command with the Cell.EuCellStandbyMode parameter set to STANDBY(Standby) on a
secondary BBU. A standby cell can be configured as either an SFN cell or a common cell. It
cannot be configured as an inter-BBU SFN cell. After a standby cell is added, the RRUs
connected to the secondary BBU start to serve the standby cell for service provisioning when
any of the following faults persists for 10 minutes:
After the fault is rectified, the standby cell is automatically deactivated and the SFN cell
continues to provide services.
NOTE
l When the inter-BBU interconnection links on the control plane are functional, the operating
frequency of the standby cell must be the same as that of the SFN cell configured on the primary
BBU. Otherwise, the standby cell cannot be activated.
l When the primary BBP is faulty, the primary BBU attempts to select a new primary BBP. If the
primary BBU successfully selects a new primary BBP, the SFN cell continues providing services. If
the primary BBU fails to select a new primary BBP, the SFN cell is deactivated and the standby cell
starts to provide services.
SMPT Provides O&M and resource management for other The following slots
boards in a universal switching unit (USU). for configuring an
SMPT are arranged in
descending order of
priority: Slot 7 > Slot
6
UCXU Transfers baseband data between USUs or between a The following slots
USU and a BBU. for configuring a
UCXU are arranged
in descending order
of priority: Slot 3 >
Slot 2 > Slot 1 > Slot
0
UCIU Transfers control and synchronization data between One UCIU must be
USUs or between a USU and a BBU. configured in slot 5.
FAN Controls the fan speed, monitors the fan The FAN is
temperatures, reports the status of the fans, and configured in slot 16.
dissipates heat from the USU.
UPEU Converts -48 V direct current (DC) into +12 V DC If only one universal
for a USU. power and
environment interface
unit (UPEU) is
required, it must be
configured in slot 19.
BBU Interconnection
BBU interconnection is required for TDLOFD-001080 Inter-BBU SFN and TDLOFD-001082
Inter-BBU Adaptive SFN/SDMA. BBUs are interconnected using the USU3900 or USU3910.
For details about the application scenarios of BBU interconnection and the physical
connections between BBUs and USU3900s, see USU3900-based BBU Interconnection
Feature Parameter Description.
For details about the application scenarios of BBU interconnection and the physical
connections between BBUs and USU3910s, see USU3910-based BBU Interconnection
Feature Parameter Description.
Topology Scanning
In BBU interconnection scenarios, interconnection cables must be properly connected
between USUs and BBUs and between USUs. If they are connected incorrectly, inter-BBU
SFN performance is compromised. The topology scanning function enables users to remotely
check cable connections in BBU interconnection scenarios and therefore facilitates fault
identification and improves O&M efficiency.
After the BBU and USU are powered on, the BBU and USU scan the interconnection port
topology of the USU and each BBP, respectively. Then, they check whether the obtained
topology complies with interconnection rules. In case of inconsistency, the BBU and USU
report ALM-26315 Inter-BBU Port Connection Error and ALM-27110 Inter-Port Connection
Error, respectively.
When topology scanning is triggered, the eNodeB and USU periodically scan the
interconnection topologies and update the topology information in real time. The DSP
INTERCONTOPO command can be executed to query the interconnection topologies on
eNodeBs and USUs. The command output contains the following information:
7 Application Restrictions
This chapter provides application restrictions of inter-BBP and inter-BBU SFN imposed in the
following scenarios: The primary baseband equipment is bound. The remaining primary BBP
resources are queried. Primary BBP adjustments are queried and primary BBP resources are
adjusted.
After the SFN cell is activated, information about the primary BBP can be queried by running
the DSP CELL command.
NOTE
l The remaining primary BBP resources can be queried only for 8T8R cells, 4T4R cells, SFN cells,
and LampSite cells. The SFN cells can be 8T8R, 4T4R, or 4T4R+8T8R.
l The query results contain only the BBPs configured with at least one cell. Capacity expansion must
be performed based on BBP processing capabilities.
NOTE
When primary BBP resources fail to be allocated for multiple cells or non-adjustment cells are faulty,
deactivate the non-adjustment cells and then adjust and activate adjustment cells until all cells are
adjusted.
Item Description
Prerequisites l The CPU usage is lower than 50%. The query and adjustment will
increase the CPU usage.
l Non-adjustment cells are all activated and all BBPs are available.
Requirements l Primary BBP resources can be adjusted only within the primary BBP
for the query group.
and adjustment l The DSP PRIBBPADJUST and STR PRIBBADUST commands
process cannot be run simultaneously. Otherwise, a message indicating a
failure to run the MML command is displayed.
l Configuration data cannot be added, modified, or deleted in the
adjustment process. Otherwise, the STR PRIBBADUST command
execution process is aborted.
l If the eNodeB fails to obtain a resource allocation solution within 30
minutes after the STR PRIBBADUST command is run, the search
times out. In this case, adjust SFN networking based on BBP
capabilities.
NOTE
During the adjustment, the algorithm for adjusting primary BBP resources is used.
If the resource allocation solution recommended by the algorithm for adjusting
primary BBP resources does not meet the rules used by the algorithm for pre-
allocating primary BBP resources, the number of inter-BBP cells increases, leading
to a high inter-BBP bandwidth usage.
8 Related Features
Impacted Features
Feature ID Feature/Function Description
Name
Impacted Features
Feature ID Feature/Function Description
Name
Impacted Features
Feature ID Feature/Function Description
Name
Impacted Features
Feature ID Feature/Function Description
Name
Impacted Features
Feature ID Feature/Function Description
Name
Impacted Features
Feature ID Feature/Function Description
Name
Impacted Features
Feature ID Feature/Function Description
Name
Impacted Features
Feature ID Feature/Function Description
Name
9 Network Impact
Network Performance
l The number of handovers decreases and the handover success rate increases, and
therefore the service drop rate decreases.
l Large-scale SFN deployment improves the SINR of the entire network.
The average SINRs on the PDCCH and PDSCH increase by 2 dB to 3 dB when
three RRUs serve an SFN cell in a typical dense urban area.
The average SINRs on the PDCCH and PDSCH increase by 5 dB to 6 dB when
three RRUs serve an SFN cell in a typical dense urban area.
In typical indoor coverage scenarios, the average SINRs on the PDCCH and
PDSCH increase obviously.
l In typical indoor coverage scenarios, SFN networking increases the average cell
throughput when compared with single-RRU or multi-RRU networking.
Network Performance
l The number of handovers decreases and the handover success rate increases, and
therefore the service drop rate decreases.
l Large-scale SFN deployment improves the SINR of the entire network.
The average SINRs on the PDCCH and PDSCH increase by 2 dB to 3 dB when
three RRUs serve an SFN cell in a typical dense urban area.
The average SINRs on the PDCCH and PDSCH increase by 5 dB to 6 dB when
three RRUs serve an SFN cell in a typical dense urban area.
In typical indoor coverage scenarios, the average SINRs on the PDCCH and
PDSCH increase obviously.
Network Performance
l The number of handovers decreases and the handover success rate increases, and
therefore the service drop rate decreases.
l Large-scale SFN deployment improves the SINR of the entire network.
The average SINRs on the PDCCH and PDSCH increase by 2 dB to 3 dB when
three RRUs serve an SFN cell in a typical dense urban area.
The average SINRs on the PDCCH and PDSCH increase by 5 dB to 6 dB when
three RRUs serve an SFN cell in a typical dense urban area.
In typical indoor coverage scenarios, the average SINRs on the PDCCH and
PDSCH increase obviously.
l In typical indoor coverage scenarios, SFN networking increases the average cell
throughput when compared with single-RRU or multi-RRU networking.
Network Performance
l The number of handovers decreases and the handover success rate increases, and
therefore the service drop rate decreases.
l Large-scale SFN deployment improves the SINR of the entire network.
The average SINRs on the PDCCH and PDSCH increase by 2 dB to 3 dB when
three RRUs serve an SFN cell in a typical dense urban area.
The average SINRs on the PDCCH and PDSCH increase by 5 dB to 6 dB when
three RRUs serve an SFN cell in a typical dense urban area.
In typical indoor coverage scenarios, the average SINRs on the PDCCH and
PDSCH increase obviously.
Network Performance
l The number of handovers decreases and the handover success rate increases, and
therefore the service drop rate decreases.
l Large-scale SFN deployment improves the SINR of the entire network.
The average SINRs on the PDCCH and PDSCH increase by 2 dB to 3 dB when
three RRUs serve an SFN cell in a typical dense urban area.
The average SINRs on the PDCCH and PDSCH increase by 5 dB to 6 dB when
three RRUs serve an SFN cell in a typical dense urban area.
In typical indoor coverage scenarios, the average SINRs on the PDCCH and
PDSCH increase obviously.
l In typical indoor coverage scenarios, SFN networking increases the average cell
throughput when compared with single-RRU or multi-RRU networking.
Network Performance
l The number of handovers decreases and the handover success rate increases, and
therefore the service drop rate decreases.
l Large-scale SFN deployment improves the SINR of the entire network.
The average SINRs on the PDCCH and PDSCH increase by 2 dB to 3 dB when
three RRUs serve an SFN cell in a typical dense urban area.
The average SINRs on the PDCCH and PDSCH increase by 5 dB to 6 dB when
three RRUs serve an SFN cell in a typical dense urban area.
In typical indoor coverage scenarios, the average SINRs on the PDCCH and
PDSCH increase obviously.
Network Performance
PDCCH DCS in SFN increases the SINR by 0.5 dB when three RRUs serve an SFN cell in a
typical dense urban area and the PDCCH load ratio is 100%.
Network Performance
No impact.
10 Engineering Guidelines
NOTE
l Interconnection parameters must be set for all the interconnected USUs and BBUs.
l SFN-related parameters must be set on the primary and secondary eNodeBs, as described
in Table 10-2.
10.3 Planning
RF Planning
l In outdoor coverage scenarios, the cell bandwidth must be 10 MHz or 20 MHz.
l In indoor coverage scenarios, the cell bandwidth must be 20 MHz.
l SFN is not supported when the cell bandwidth is 5 or 15 MHz.
Network Planning
The network planning for the SFN networking mode is the same as that for the common
networking mode.
Step 1 Count the RRUs serving each SFN cell, sort SFN cells in descending order by the number of
their serving RRUs, and then determine the primary eNodeB of each SFN cell starting from
the SFN cell served by the maximum number of RRUs.
Step 2 Select the eNodeB that provides the maximum number of RRUs serving an SFN cell as a
candidate primary eNodeB of the SFN cell.
Step 3 Check whether the eNodeB meets all the following conditions:
l The number of cells configured on the eNodeB has not reached the upper limit.
l The number of physical cells configured on the eNodeB has not reached the upper limit.
l Number of SFN cells with each served by four or more RRUs (Number of LBBPd
boards + Number of UBBP boards x 2)
l Layer 2 resources meet the BBP specifications provided in the following table.
LBBPc When the cell bandwidth is 20 MHz: One cell served by one to three
RRUs
When the cell bandwidth is 10 MHz:
One cell served by two or three RRUs
Three cells with each served by one RRU
One cell served by two RRUs + one cell served by one RRU
UBBPd6/ When the cell bandwidth is 10 MHz or 20 MHz, the total number of
UBBPd9/ cells is less than 6, and the total number of RRUs is less than 9, any
UMDUa3 combination of cell configurations is supported.
l The total number of out-of-eNodeB and into-eNodeB physical cells is less than or equal
to 14 times the number of optical fibers between the eNodeB and USUs.
NOTE
The number of optical fibers between the eNodeB and USUs must be equal to or less than the
smaller value between 4 and the number of LBBPd and UBBP boards installed in slots 0, 1, 2,
and 3 on the eNodeB.
An into-eNodeB physical cell for an eNodeB (for example, eNodeB 0) is a physical cell that
resides on an eNodeB different from eNodeB 0 and serves an SFN cell whose primary eNodeB
is eNodeB 0.
An out-of-eNodeB physical cell for an eNodeB (for example, eNodeB 0) is a physical cell that
resides on eNodeB 0 and serves an SFN cell whose primary eNodeB is not eNodeB 0.
"Physical cell" mentioned in this section corresponds to one carrier of each RRU.
The LBBPc board does not support the configuration of 8T8R L2 logical cells.
As shown in Figure 10-1, eNodeB 0 is configured with two into-eNodeB physical cells
and two out-of-eNodeB physical cells, and eNodeB 1 is configured with two into-
eNodeB physical cells and one out-of-eNodeB physical cell.
If one or more eNodeBs meet all of the preceding conditions, go to Step 4. If no eNodeB
meets all of the preceding conditions, go to Step 5.
Step 4 Select an eNodeB as the primary eNodeB of an SFN cell. If only one eNodeB meets all of the
preceding conditions, the eNodeB functions as the primary eNodeB of the SFN cell. If
multiple eNodeBs meet all of the preceding conditions, the eNodeB that provides the
minimum number of RRUs processed by Layer 2 is preferentially selected as the primary
eNodeB of the SFN cell.
NOTE
The total number of RRUs processed by Layer 2 equals the total number of RRUs serving any of the
SFN cells configured on the eNodeB, including RRUs connected to different BBUs.
Step 5 Select the eNodeB providing the second largest number of RRUs serving an SFN cell as the
candidate primary eNodeB of the SFN cell and repeat Step 3 until the primary eNodeB is
selected.
Step 6 Repeat Step 1 to Step 5 to select the primary eNodeBs for all the SFN cells.
----End
LBBPc 3 1
LBBPd 3 3
UBBPd4/ 3 3
UMDUa1
UBBPd6/ 6 6
UBBPd9/
UMDUa3
LBBPd 2 1
UBBPd9 3 3
NOTE
When four or more RRUs are used to serve an inter-BBP or inter-BBU SFN cell, one LBBPd
or UBBPd must be installed.
Inter-BBU SFN techniques also have the following requirements:
l In addition to the LBBPc, other BBP models must be configured in the BBU.
l When USU3900s are used for BBU interconnection, one USU is required if five or fewer
BBUs are interconnected. If 6 to 25 BBUs are interconnected, two levels of USUs are
required. One first-level USU can connect a maximum of five BBUs. Multiple first-level
USUs (not more than five USUs) are interconnected to one second-level USU.
l When USU3910s are used for BBU interconnection, one USU is required if five or fewer
BBUs are interconnected. If 6 to 60 BBUs are interconnected, two levels of USUs are
required. One first-level USU can connect a maximum of five BBUs. Multiple first-level
USUs (not more than 12 USUs) are interconnected to one or two second-level USUs.
NOTE
For details about the board configuration principles of USUs and BBUs, see USU3900 Hardware
Description, USU3910 Hardware Description, USU3900-based Multi-BBU Interconnection Feature
Parameter Description, and USU3910-based Multi-BBU Interconnection Feature Parameter Description.
NOTE
10.4.1 Requirements
Operating Environment
l In outdoor coverage scenarios, the BBP.WM parameter must be set to
TDD_ENHANCE(Support TDD BF) when the baseband processing board is LBBPc
or LBBPd.
When the BBP.WM parameter is set to TDD_ENHANCE for LBBPc, LBBPc+LBBPc
convergence is not supported. In the LBBPc+LBBPd convergence scenario, the
converged board must be LBBPd instead of LBBPc.
l In indoor coverage scenarios, the BBP.WM parameter must be set to TDD when the
baseband processing board is LBBPc or LBBPd.
l SFN and adaptive SFN/SDMA support subframe configurations 1 and 2 and special
subframe configuration 7.
l Inter-BBP SFN and inter-BBP adaptive SFN/SDMA support only subframe
configuration 2 and special subframe configuration 7.
Hardware
For details about hardware, see hardware planning in 10.3 Planning.
License
The operator has purchased and activated the license for the feature listed in the following
table to activate intra-BBP SFN.
The operator has purchased and activated the licenses for the features listed in the following
table to activate intra-BBP adaptive SFN/SDMA.
The operator has purchased and activated the licenses for the features listed in the following
table to activate inter-BBP SFN.
The operator has purchased and activated the licenses for the features listed in the following
table to activate inter-BBP adaptive SFN/SDMA.
The operator has purchased and activated the licenses for the features listed in the following
table to activate PDCCH DCS in SFN.
The operator has purchased and activated the licenses for the features listed in the following
table to activate PDCCH SDMA in SFN.
NOTE
l When SFN and Adaptive SFN/SDMA are enabled, the number of feature licenses and capacity
licenses required for an SFN cell is calculated based on the number of RRUs serving the SFN cell.
For example, if an SFN or adaptive SFN/SDMA cell comprises three physical cells and DL 2x2
MIMO is enabled, three license units are required for each of the following license control items:
Number of cells, SFN, Adaptive SFN/SDMA, and DL 2x2 MIMO.
l If any of the following features is enabled, the feature license units must be purchased for both
primary and secondary BBUs: Inter-BBP SFN, Inter-BBU SFN, Inter-BBP Adaptive SFN/SDMA,
and Inter-BBU Adaptive SFN/SDMA. The number of license units purchased for any BBU is
determined in the same manner as that described in the previous point.
l When inter-BBU SFN or inter-BBU Adaptive SFN/SDMA is enabled, ALM-26819 Data
Configuration Exceeding Licensed Limit is reported only for the primary BBU if the licenses on
both primary and secondary BBUs are insufficient. If the licenses of the primary BBU meet service
requirements but those of the secondary BBU do not, this alarm is reported on the secondary BBU.
10.4.2 Precautions
l The activation of an SFN cell may deactivate and activate some activated cells served by
the eNodeB, which ensures optimal resource usage.
l When an SFN cell is served by RRUs connected to both LBBPc and LBBPd or to both
LBBPc and UBBPd and the PUCCHCFG.DeltaShift parameter is set to
DS1_DELTA_SHIFT(ds1), the parameter value will be automatically changed to
DS2_DELTA_SHIFT(ds2) after the SFN cell is activated.
l BBPs can be combined in LBBPc-only, LBBPd-only, UBBPd-only, LBBPc+LBBPd, or
LBBPd+UBBPd mode for an SFN cell. Table 10-6 describes BBP combination mode
switching and the impact of switching on an inter-BBP SFN cell.
Table 10-6 BBP combination mode switching and the impact of switching on an inter-
BBU SFN cell
LBBPc+LBBPd LBBPc+LBBPd No
l If the BBU configured with an SFN cell houses the LBBPc and LBBPd or UBBPd, layer
1 must be bound to a BBP by running the ADD EUCELLSECTOREQM command
before the SFN cell is activated.
l When two cells with the bandwidths of 10 and 20 MHz are configured on the same
BBU, they must be configured on different BBPs. In addition, the following
requirements must be met:
The carrier with the bandwidth of 20 MHz is preferentially configured on the
LBBPd or UBBPd, and the carrier with the bandwidth of 10 MHz is preferentially
configured on the LBBPc.
For the common cell, BBPs must be grouped based on cell bandwidths and then be
added to baseband equipment. The cells with different bandwidths must be
configured with different baseband equipment.
For the SFN cell, if the BBU configured with the SFN cell houses the LBBPc and
LBBPd or UBBPd, layer 1 must be bound to a single BBP and layer 2 must be
bound to baseband equipment based on cell bandwidths.
If the BBU does not house any LBBPc, layer 1 and layer 2 need to be bound to
baseband equipment based on cell bandwidths.
l The slots for installing the LBBPd and UBBPd are arranged in the descending order of
priority as follows: Slot 3 > Slot 2 > Slot 0 > Slot 1 > Slot 4 > Slot 5. The slots for
installing the LBBPc are arranged in the descending order of priority as follows: Slot 5 >
Slot 4 > Slot 1 > Slot 0 > Slot 2 > Slot 3. The UBBPd, LBBPd, and LBBPc must be
installed in sequence when all of them are required.
l In 20 MHz+10 MHz multi-carrier scenarios, the RRU must be connected to the BBP
configured with the 20 MHz carrier and then to the BBP configured with the 10 MHz
carrier through the backplane.
l The LBBPc configured with the 10 MHz carrier must be used with a BBP configured
with the 20 MHz carrier to perform CPRI aggregation. CPRI aggregation is not available
between a BBP installed in slot 0 or 1 and another BBP installed in slot 4 or 5. This
restriction applies only to the BBU3900.
Required Data
NOTE
Configure two to seven pieces of sector equipment and sectors for an SFN cell based on site
requirements. The number of sectors must be consistent with the amount of sector equipment for the
SFN cell.
The following table describes the parameters that must be set in the SECTOR MO to
configure sectors for SFN cells.
The following table describes the parameters that must be set in the Cell MO to configure
SFN cells.
Flag of Multi- Cell.MultiRr Radio planning (internal For SFN cells and
RRU Cell uCellFlag planning) pRRU aggregated
cells, set this parameter
to
BOOLEAN_TRUE(T
rue). For common
cells, set this parameter
to
BOOLEAN_FALSE(
False).
Mode of Cell.MultiRr Radio planning (internal For SFN cells, set this
Multi-RRU uCellMode planning) parameter to
Cell SFN(SFN). For pRRU
aggregated cells, set
this parameter to
MPRU_AGGREGAT
ION(MPRU_AGGRE
GATION). For
common cells, this
parameter is invalid.
The following table describes the parameters that must be set in the BASEBANDEQM MO
to configure baseband equipment for SFN cells.
NOTE
Baseband equipment must be added and the binding relationships between cells and BBUs must be
configured when the SFN cell is set up in LampSite scenarios or is configured with one 10 MHz carrier
and one 20 MHz carrier.
The following table describes the parameters that must be set in the
EUCELLSECTOREQM MO to configure sector equipment for SFN cells.
The following table describes the parameters that must be set in the EuCellPriBBEqm MO to
configure the primary baseband equipment for SFN cells.
Scenario-specific Data
l Basic algorithm configuration of SFN cells
The following table describes the parameters that must be set in the CellAlgoSwitch MO
to configure uplink and downlink scheduling modes for SFN cells.
Parameter Parameter ID Data Setting Notes
Name Source
The following table describes the parameters that must be set in the MOs
CellAlgoSwitch, CellDlschAlgo, and CellUlschAlgo to configure the SFN load-based
adaptive switch and the uplink and downlink load measurement periods for SFN cells.
Parameter Parame Data Source Setting Notes
Name ter ID
(Optional) The following table describes the parameter that must be set in the
CellAlgoSwitch MO to configure the SFN downlink scheduling attribute adjustment for
SFN cells.
(Optional) The following table describes the parameter that must be set in the
CellAlgoSwitch MO to configure CBF for SFN cells.
Parameter Parameter ID Data Setting Notes
Name Source
(Optional) The following table describes the parameters that must be set in the MOs
CellAlgoSwitch and CELLULCOMPALGO to specify whether to enable uplink joint
reception and configure the SFN UL CoMP admission threshold for SFN cells. Uplink
joint reception can be enabled only when the baseband boards of SFN cells are the
LBBPd or UBBPd.
Parameter Parameter Data Source Setting Notes
Name ID
(Optional) The following table describes the parameters that must be set in the MOs
CellAlgoSwitch and CELLPDCCHALGO to specify whether to enable PDCCH
SDMA in SFN and the PUCCH dynamic ACK SDMA function and configure the SFN
PDCCH SDMA threshold for SFN cells.
Parameter Parameter ID Data Setting Notes
Name Source
(Optional) The following table describes the parameters that must be set in the
CellAlgoSwitch MO to configure the enhanced SFN uplink target RRU selection switch.
Parameter Parameter ID Data Source Setting Notes
Name
Single-carrier Scenario
NOTE
l This document provides configuration guidelines for newly deployed SFN cells. For details about
how to combine common cells into SFN cells, see eRAN(TDD) Reconfiguration Guide.
l The following description uses an SFN cell served by three RRUs as an example. The parameter
settings in the following commands are used for reference only. Set the parameters based on network
requirements.
Run the ADD SECTOR command to add sectors. In the command, specify the number of
antennas in a sector and each antenna's RRU cabinet number, subrack number, slot number,
and port number. In addition, set the Create Default Sector Equipment parameter to
TRUE(TRUE), enabling the eNodeB to create the default sector equipment.
Run the ADD CELL command to add an SFN cell. In this step, set the
Cell.MultiRruCellFlag parameter to BOOLEAN_TRUE(True), the
Cell.MultiRruCellMode parameter to SFN(SFN), and the SectorEqmNum parameter to the
actual number of RRUs to be combined. Set the other parameters by referring to the
parameter settings of common cells.
Example:
Step 7 Run the MOD CELLALGOSWITCH command to enable or disable load-based adaptive
SFN/SDMA.
Example 1: Run the following command to enable load-based adaptive SFN/SDMA:
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNLOADBASEDADPTSWITCH=ON;
Step 8 (Optional) Run the MOD CELLALGOSWITCH command to configure PDCCH DCS in
SFN, PDCCH SDMA, PUCCH dynamic ACK SDMA, uplink layer-2 selective reception,
SFN downlink two-load-level adaption, or SFN downlink scheduling attribute adjustment, or
SFN CBF.
Example 1: Run the following command to enable PDCCH DCS in SFN and layer-2 selective
reception:
MOD CELLALGOSWITCH: LOCALCELLID=0,
SFNALGOSWITCH=SfnPdcchDcsSwitch-1&SfnUll2SelectiveRcvSwitch-1;
Example 2: Run the following command to disable PDCCH DCS in SFN and layer-2
selective reception:
MOD CELLALGOSWITCH: LOCALCELLID=0,
SFNALGOSWITCH=SfnPdcchDcsSwitch-0&SfnUll2SelectiveRcvSwitch-0;
Step 9 (Optional) Run the MOD CELLPDCCHALGO command to set the SFN PDCCH DCS
threshold or the SFN PDCCH SDMA threshold.
Example: Run the following command to set the SFN PDCCH DCS threshold to 20 dB:
MOD CELLPDCCHALGO: LOCALCELLID=0, SfnPdcchDcsThd=40;
Step 10 (Optional) Run the MOD CELLDLSCHALGO command to configure the downlink load
measurement period, downlink heavy-load threshold, downlink light-load threshold, and
isolation decision threshold offset of downlink heavy-load level for an SFN cell.
Example: Set the downlink load measurement period to 30 seconds, downlink heavy-load
threshold to 50%, downlink light-load threshold to 20%, and isolation decision threshold
offset of downlink heavy-load level to 2 dB.
MOD CELLDLSCHALGO:LOCALCELLID=0, SfnDlLoadPeriod=30, SfnDlHighLoadThd=50,
SfnDlLowLoadThd=20, DlHighLoadSdmaThdOffset=2;
Step 11 (Optional) Run the MOD CELLULSCHALGO command to configure the uplink load
measurement period of an SFN cell.
Example: Set the uplink load measurement period to 1800 seconds.
MOD CELLULSCHALGO:LOCALCELLID=0, SfnUlLoadPeriod =1800;
Step 12 (Optional) Run the MOD CELLALGOSWITCH command to configure the uplink joint
reception switch in SFN cell or the switch for uplink joint reception of a specific number of
antennas.
Example: Run the following command to turn on the SFN UL CoMP switch and the switch
for uplink 8R supporting joint reception.
MOD CELLALGOSWITCH: LocalCellId=0, SfnUplinkCompSwitch=IntraBaseBandSwitch-1,
UlJRAntNumCombSw=Ul8R8RJRSwitch-1;
Step 13 (Optional) Run the MOD CELLULCOMPALGO command to set the admission threshold
of SFN UL CoMP.
Example:
MOD CELLULCOMPALGO: LocalCellId=0, SfnUlCompThd=-5;
NOTE
For details about precautions for activating an SFN cell, see 10.4.2 Precautions.
----End
Run the ADD SECTOR command with the antenna quantities, and the cabinet numbers,
subrack numbers, slot numbers, and port numbers of RRUs connected to antenna ports
specified. The SECTOR.CREATESECTOREQM parameter must be set to TRUE(TRUE).
Run the ADD CELL command to add an SFN cell. In this step, set the
Cell.MultiRruCellFlag parameter to BOOLEAN_TRUE(True), the
Cell.MultiRruCellMode parameter to SFN(SFN), and the SectorEqmNum parameter to the
actual number of RRUs to be combined. Set the other parameters by referring to the
parameter settings of common cells.
YMODE=ACTIVE,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCF
GIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_TRUE,MULTIRRUCELLMO
DE=SFN,SECTOREQMNUM=3,TXRXMODE=4T4R;
ADD
CELL:LOCALCELLID=1,CELLNAME="10M_SFN",FREQBAND=41,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=
40196,ULBANDWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,CELLID=101,PHYCELLID=101,FDD
TDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEPATTERNS=SSP7,EUCELLSTANDBYM
ODE=ACTIVE,ROOTSEQUENCEIDX=1,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGI
ND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_TRUE,MULTIRRUCELLMODE
=SFN,SECTOREQMNUM=3,TXRXMODE=4T4R;
Step 6 Run the ADD EUCELLPRIBBEQM command to add primary baseband equipment
configuration to a cell.
Example:
ADD EUCELLPRIBBEQM:LOCALCELLID=0,PRIBASEBANDEQMID=4;
ADD EUCELLPRIBBEQM:LOCALCELLID=1,PRIBASEBANDEQMID=5;
Step 8 Run the MOD CELLALGOSWITCH command to enable or disable load-based adaptive
SFN/SDMA.
Example 1: Run the following command to enable load-based adaptive SFN/SDMA:
MOD CELLALGOSWITCH:LOCALCELLID=0,SFNLOADBASEDADPTSWITCH=ON;
MOD CELLALGOSWITCH:LOCALCELLID=1,SFNLOADBASEDADPTSWITCH=ON;
Step 9 (Optional) Run the MOD CELLALGOSWITCH command to configure PDCCH DCS in
SFN, PDCCH SDMA, PUCCH dynamic ACK SDMA, uplink layer-2 selective reception,
SFN downlink two-load-level adaption, or SFN downlink scheduling attribute adjustment, or
SFN CBF.
Example 1: Run the following command to enable PDCCH DCS in SFN and layer-2 selective
reception:
MOD
CELLALGOSWITCH:LOCALCELLID=0,SFNALGOSWITCH=SfnPdcchDcsSwitch-1&SfnUll2SelectiveRcv
Switch-1;
MOD
CELLALGOSWITCH:LOCALCELLID=1,SFNALGOSWITCH=SfnPdcchDcsSwitch-1&SfnUll2SelectiveRcv
Switch-1;
Example 2: Run the following command to disable PDCCH DCS in SFN and layer-2
selective reception:
MOD
CELLALGOSWITCH:LOCALCELLID=0,SFNALGOSWITCH=SfnPdcchDcsSwitch-0&SfnUll2SelectiveRcv
Switch-0;
MOD
CELLALGOSWITCH:LOCALCELLID=1,SFNALGOSWITCH=SfnPdcchDcsSwitch-0&SfnUll2SelectiveRcv
Switch-0;
Step 10 Run the MOD CELLPDCCHALGO command to set the SFN PDCCH DCS threshold or the
SFN PDCCH SDMA threshold.
Example: Run the following command to set the SFN PDCCH DCS threshold to 20 dB:
MOD CELLPDCCHALGO:LOCALCELLID=0,SfnPdcchDcsThd=40;
MOD CELLPDCCHALGO:LOCALCELLID=1,SfnPdcchDcsThd=40;
Step 11 (Optional) Run the MOD CELLDLSCHALGO command to configure the downlink load
measurement period, downlink heavy-load threshold, downlink light-load threshold, and
isolation decision threshold offset of downlink heavy-load level for an SFN cell.
Example: Set the downlink load measurement period to 30 seconds, downlink heavy-load
threshold to 50%, downlink light-load threshold to 20%, and isolation decision threshold
offset of downlink heavy-load level to 2 dB.
MOD CELLDLSCHALGO:LOCALCELLID=0, SfnDlLoadPeriod=30, SfnDlHighLoadThd=50,
SfnDlLowLoadThd=20, DlHighLoadSdmaThdOffset=2;
MOD CELLDLSCHALGO:LOCALCELLID=1, SfnDlLoadPeriod=30, SfnDlHighLoadThd=50,
SfnDlLowLoadThd=20, DlHighLoadSdmaThdOffset=2;
Step 12 (Optional) Run the MOD CELLULSCHALGO command to configure the uplink load
measurement period of an SFN cell.
Step 13 (Optional) Run the MOD CELLALGOSWITCH command to configure the uplink joint
reception switch in SFN cell or the switch for uplink joint reception of a specific number of
antennas.
Example: Run the following command to turn on the SFN UL CoMP switch and the switch
for uplink 8R supporting joint reception.
MOD CELLALGOSWITCH: LocalCellId=0, SfnUplinkCompSwitch=IntraBaseBandSwitch-1,
UlJRAntNumCombSw=Ul8R8RJRSwitch-1;
MOD CELLALGOSWITCH: LocalCellId=1, SfnUplinkCompSwitch=IntraBaseBandSwitch-1,
UlJRAntNumCombSw=Ul8R8RJRSwtich-1;
Step 14 (Optional) Run the MOD CELLULCOMPALGO command to set the admission threshold
of SFN UL CoMP.
Example:
MOD CELLULCOMPALGO: LocalCellId=0, SfnUlCompThd=-5;
MOD CELLULCOMPALGO: LocalCellId=1, SfnUlCompThd=-5;
NOTE
For details about precautions for activating an SFN cell, see 10.4.2 Precautions.
----End
l If the value of Cell instance state is Normal, the cell has been activated.
l If the value of Cell topology type is SFN Type, the cell is an SFN cell.
l If the working status of all RRUs is Normal, all RRUs have been activated.
10.4.6 Deactivation
The following sections use USU3900s as an example to describe how to interconnect BBUs. For details,
see USU3900 Installation Guide, USU3900 Initial Configuration Guide, and USU3900-based Multi-
BBU Interconnection Feature Parameter Description.
For details about how to interconnect BBUs using USU3910s, see USU3910 Installation Guide,
USU3910 Initial Configuration Guide, and USU3910-based Multi-BBU Interconnection Feature
Parameter Description.
10.5.1 Requirements
Operating Environment
l In indoor coverage scenarios, inter-BBU SFN is not supported.
l In outdoor coverage scenarios, the BBP.WM parameter must be set to
TDD_ENHANCE when the baseband processing board is LBBPc or LBBPd.
When the BBP.WM parameter is set to TDD_ENHANCE for LBBPc, LBBPc+LBBPc
convergence is not supported. In the LBBPc+LBBPd convergence scenario, the
converged board must be LBBPd instead of LBBPc.
l Inter-BBU SFN and inter-BBU adaptive SFN/SDMA support only uplink-downlink
subframe configuration 2 and special subframe configuration 7.
l Inter-BBU SFN and inter-BBU adaptive SFN/SDMA require that the TDD Frame
Offset parameter be set to the same value for primary and secondary eNodeBs by
running the MML command MOD ENODEBFRAMEOFFSET.
l The Topo Type parameter in the RRUCHAIN MO must be set to CHAIN(CHAIN).
Hardware
For details about hardware, see hardware planning in 10.3 Planning.
License
The operator has purchased and activated the licenses for the features listed in the following
table to activate inter-BBU SFN.
The operator has purchased and activated the licenses for the features listed in the following
table to activate inter-BBU adaptive SFN/SDMA.
The operator has purchased and activated the license for the feature listed in the following
table to activate PDCCH DCS in SFN.
The operator has purchased and activated the license for the feature listed in the following
table to activate PDCCH SDMA in SFN.
NOTE
To know the precautions for using the licenses, see 10.4.1 Requirements.
10.5.2 Precautions
l The X2 interface is required only when at least one cell is configured on an eNodeB. If
all the cells are deleted on an eNodeB during network reconstruction or optimization,
remove the X2 interface.
l The activation of an SFN cell may deactivate and activate some activated cells served by
the eNodeB, which ensures optimal resource usage.
l When an SFN cell is served by RRUs connected to both LBBPc and LBBPd or to both
LBBPc and UBBPd and the PUCCHCFG.DeltaShift parameter is set to
DS1_DELTA_SHIFT(ds1), the parameter value will be automatically changed to
DS2_DELTA_SHIFT(ds2) after the SFN cell is activated.
l BBPs can be combined in LBBPc-only, LBBPd-only, UBBPd-only, LBBPc+LBBPd, or
LBBPd+UBBPd mode for an SFN cell. Table 10-7 describes BBP combination mode
switching and the impact of switching on an inter-BBP SFN cell.
Table 10-7 BBP combination mode switching and the impact of switching on an inter-
BBU SFN cell
LBBPc+LBBPd LBBPc+LBBPd No
l If the BBU configured with an SFN cell houses the LBBPc and LBBPd or UBBPd, layer
1 must be bound to a BBP by running the ADD EUCELLSECTOREQM command
before the SFN cell is activated.
l When two cells with the bandwidths of 10 and 20 MHz are configured on the same
BBU, they must be configured on different BBPs. In addition, the following
requirements must be met:
The carrier with the bandwidth of 20 MHz is preferentially configured on the
LBBPd or UBBPd, and the carrier with the bandwidth of 10 MHz is preferentially
configured on the LBBPc.
For the common cell, BBPs must be grouped based on cell bandwidths and then be
added to baseband equipment. The cells with different bandwidths must be
configured with different baseband equipment.
For the SFN cell, if the BBU configured with the SFN cell houses the LBBPc and
LBBPd or UBBPd, layer 1 must be bound to a single BBP and layer 2 must be
bound to baseband equipment based on cell bandwidths.
If the BBU does not house any LBBPc, layer 1 and layer 2 need to be bound to
baseband equipment based on cell bandwidths.
l The slots for installing the LBBPd and UBBPd are arranged in the descending order of
priority as follows: Slot 3 > Slot 2 > Slot 0 > Slot 1 > Slot 4 > Slot 5. The slots for
installing the LBBPc are arranged in the descending order of priority as follows: Slot 5 >
Slot 4 > Slot 1 > Slot 0 > Slot 2 > Slot 3. The UBBPd, LBBPd, and LBBPc must be
installed in sequence when all of them are required. This requirement does not apply to
the UBBPd, LBBPd, or LBBPc that has been installed.
l In 20 MHz+10 MHz multi-carrier scenarios, the RRU must be connected to the BBP
configured with the 20 MHz carrier and then to the BBP configured with the 10 MHz
carrier through the backplane.
l The LBBPc configured with the 10 MHz carrier must be used with a BBP configured
with the 20 MHz carrier to perform CPRI aggregation. CPRI aggregation is not available
between a BBP installed in slot 0 or 1 and another BBP installed in slot 4 or 5.
The following table describes the parameter that must be set in the EQUIPMENT MO to
configure the ID of open datalink interface (ODI).
The following table describes the parameters that must be set in the SFNCELLBIND MO to
configure the binding relationship with auxiliary eNodeBs on the primary eNodeB.
The following table describes the parameters that must be set in the
ENODEBALGOSWITCH MO to configure SFN uplink joint reception based on
coordinated BBU on the primary eNodeB.
For details about the parameter settings of the MOs Sector, Cell, EUCELLSECTOREQM,
BASEBANDEQM, EUCELLPRIBBEQM, CELLPDCCHALGO, and CellAlgoSwitch,
see 10.4.4.1 Data Preparation in 10.4 Deployment of Intra- and Inter-BBP SFN
Techniques.
The following table describes the parameter that must be set in the EQUIPMENT MO to
configure the ID of open datalink interface (ODI).
The following table describes the parameters that must be set in the SFNAUXRESBIND MO
to configure the binding relationships between an SFN cell configured on the primary
eNodeB and the sector equipment configured on secondary eNodeBs.
For details about the parameter settings of the MOs Sector, Cell, EUCELLSECTOREQM,
BASEBANDEQM, EUCELLPRIBBEQM, CELLPDCCHALGO, and CellAlgoSwitch,
see 10.4.4.1 Data Preparation in 10.4 Deployment of Intra- and Inter-BBP SFN
Techniques.
NOTE
When a standby cell is to be added to a secondary eNodeB by running the ADD CELL command, the
cell.EuCellStandbyMode parameter must be set to STANDBY(Standby).
Networking Example
In the networking architecture shown in Figure 10-3: BBU 0 and BBU 1 are primary and
secondary BBUs, respectively. The four RRUs connected to BBU 0 and the two RRUs
connected to BBU 1 serve an SFN cell. The primary eNodeB ID is 100 and the secondary
eNodeB ID is 101.
Step 2 Run the SET CASCADEPORT command with the SW parameter set to ON(On) to
configure interconnection ports.
Example 1: To configure the interconnection port status of the UCXU and UCIU on the USU,
run the following commands:
SET CASCADEPORT:CN=0,SRN=0,SN=2,PN=0,SW=ON;
SET CASCADEPORT:CN=0,SRN=0,SN=3,PN=0,SW=ON;
SET CASCADEPORT:CN=0,SRN=0,SN=3,PN=1,SW=ON;
SET CASCADEPORT:CN=0,SRN=0,SN=5,PN=0,SW=ON;
SET CASCADEPORT:CN=0,SRN=0,SN=5,PN=1,SW=ON;
Example 2: To configure the interconnection port status of the BBP and UMPT on BBU 0,
run the following commands:
SET CASCADEPORT:CN=0,SRN=0,SN=2,PN=6,SW=ON;
SET CASCADEPORT:CN=0,SRN=0,SN=3,PN=6,SW=ON;
SET CASCADEPORT:CN=0,SRN=0,SN=7,PN=8,SW=ON;
Example 3: To configure the interconnection port status of the BBP and UMPT on BBU 1,
run the following commands:
SET CASCADEPORT:CN=0,SRN=0,SN=3,PN=6,SW=ON;
SET CASCADEPORT:CN=0,SRN=0,SN=7,PN=8,SW=ON;
----End
Step 2 Run the ADD CELL command to add an SFN cell. In this step, set Cell.MultiRruCellFlag to
BOOLEAN_TRUE(True), Cell.MultiRruCellMode to SFN(SFN),
Cell.EuCellStandbyMode to ACTIVE(Active), and SectorEqmNum to the number of RRUs
that serve an SFN cell. Set the other parameters by referring to the parameter settings of
common cells.
Step 6 (Optional) Perform this step only in the multi-carrier (10M+20M) scenario. In the single-
carrier scenario, perform Step 7.
Run the ADD EUCELLPRIBBEQM command to add primary baseband equipment
configuration to a cell.
Example:
ADD EUCELLPRIBBEQM:LOCALCELLID=0,PRIBASEBANDEQMID=0;
ADD EUCELLPRIBBEQM:LOCALCELLID=1,PRIBASEBANDEQMID=1;
Step 8 Run the MOD CELLALGOSWITCH command to enable or disable load-based adaptive
SFN/SDMA.
Example 1: Run the following command to enable load-based adaptive SFN/SDMA:
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNLOADBASEDADPTSWITCH=ON;
Step 9 (Optional) Run the MOD CELLALGOSWITCH command to configure PDCCH DCS in
SFN, PDCCH SDMA, PUCCH dynamic ACK SDMA, uplink layer-2 selective reception,
SFN downlink two-load-level adaption, or SFN downlink scheduling attribute adjustment, or
SFN CBF.
Example 1: Run the following command to enable PDCCH DCS in SFN and layer-2 selective
reception:
MOD CELLALGOSWITCH: LOCALCELLID=0,
SFNALGOSWITCH=SfnPdcchDcsSwitch-1&SfnUll2SelectiveRcvSwitch-1;
Example 2: Run the following command to disable PDCCH DCS in SFN and layer-2
selective reception:
MOD CELLALGOSWITCH: LOCALCELLID=0,
SFNALGOSWITCH=SfnPdcchDcsSwitch-0&SfnUll2SelectiveRcvSwitch-0;
Step 10 (Optional) Run the MOD CELLPDCCHALGO command to set the SFN PDCCH DCS
threshold or the SFN PDCCH SDMA threshold.
Example: Run the following command to set the SFN PDCCH DCS threshold to 20 dB:
MOD CELLPDCCHALGO: LOCALCELLID=0,SfnPdcchDcsThd=40;
Step 11 (Optional) Run the MOD CELLDLSCHALGO command to configure the downlink load
measurement period, downlink heavy-load threshold, downlink light-load threshold, and
isolation decision threshold offset of downlink heavy-load level for an SFN cell.
Example: Set the downlink load measurement period to 30 seconds, downlink heavy-load
threshold to 50%, downlink light-load threshold to 20%, and isolation decision threshold
offset of downlink heavy-load level to 2 dB.
MOD CELLDLSCHALGO:LOCALCELLID=0,SfnDlLoadPeriod=30,SfnDlHighLoadThd=
50,SfnDlLowLoadThd=20,DlHighLoadSdmaThdOffset=2;
Step 12 (Optional) Run the MOD CELLULSCHALGO command to configure the uplink load
measurement period of an SFN cell.
Example: Set the uplink load measurement period to 1800 seconds.
MOD CELLULSCHALGO:LOCALCELLID=0,SfnUlLoadPeriod =1800;
Step 13 (Optional) Run the MOD CELLALGOSWITCH command to configure the uplink joint
reception switch in SFN cell or the switch for uplink joint reception of a specific number of
antennas.
Example: Run the following command to turn on the SFN UL CoMP switch and the switch
for uplink 8R supporting joint reception.
MOD CELLALGOSWITCH: LocalCellId=0, SfnUplinkCompSwitch=IntraBaseBandSwitch-1,
UlJRAntNumCombSw=Ul8R8RJRSwitch-1;
Step 14 (Optional) Run the MOD CELLULCOMPALGO command to set the admission threshold
of SFN UL CoMP.
Example: Set the admission threshold of SFN UL CoMP to -5 dB.
MOD CELLULCOMPALGO: LocalCellId=0, SfnUlCompThd=-5;
Step 15 (Optional) Run the MOD ENODEBALGOSWITCH command to configure the SFN uplink
joint reception switch based on BBU coordination.
Example:
MOD ENODEBALGOSWITCH: OverBBUsSwitch=UlSfnJROverBBUsSwitch -1;
Step 16 Run the ADD ENODEBFUNCTION command to add the ID of the secondary eNodeB.
Example:
ADD ENODEBFUNCTION: eNodeBFunctionName="LTE", ApplicationRef=1, eNodeBId=101;
Step 17 On the primary eNodeB, run the ADD SFNCELLBIND command to bind the SFN cell to a
secondary eNodeB.
Example (taking 4T4R sectors for example):
Step 18 Run the ACT CELL command on the primary eNodeB to activate an SFN cell.
Example (taking 4T4R sectors for example):
ACT CELL: LocalCellId=0;
NOTE
It is recommended that an SFN cell be activated after data configurations have been completed on
secondary eNodeBs.
----End
Step 3 Run the ADD ENODEBFUNCTION command to add the ID of the primary eNodeB.
Example:
ADD ENODEBFUNCTION: eNodeBFunctionName="LTE", ApplicationRef=1, eNodeBId=100;
Step 4 Run the ADD SFNAUXRESBIND command to bind the sector equipment of a secondary
eNodeB to the SFN cell.
Example:
ADD SFNAUXRESBIND:SECTOREQMID=0,ENODEBID=100,LOCALCELLID=0,BASEBANDEQMID=0;
ADD SFNAUXRESBIND:SECTOREQMID=1,ENODEBID=100,LOCALCELLID=0,BASEBANDEQMID=0;
Step 5 (Optional) Configure standby cells for all the secondary eNodeBs.
1. Run the ADD CELL command to add a standby cell.
The standby cell can be an SFN cell or a common cell. When the standby cell is an SFN
cell, configure the standby cell based on the parameter settings of the SFN cell
configured on the primary eNodeB.
Example 1 (taking 4T4R SFN cell for example): When an SFN cell serves as the standby
cell, run the ADD CELL command. In this step, set the Cell.EuCellStandbyMode
parameter to STANDBY(Standby), the SECTOREQMNUM parameter to the number
of RRUs serving the SFN cell, and the other parameters based on the parameter settings
of the SFN cell on the primary eNodeB.
ADD
CELL:LOCALCELLID=0,CELLNAME="TDD_SFN",FREQBAND=41,ULEARFCNCFGIND=NOT_CFG,DLEAR
FCN=40340,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW_N100,CELLID=100,PHYCELL
ID=100,FDDTDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEPATTERNS=SSP7,
EUCELLSTANDBYMODE=STANDBY,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,
EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEA
N_TRUE,MULTIRRUCELLMODE=SFN,SECTOREQMNUM=2,TXRXMODE=4T4R;
Example 2 (taking 4T4R SFN cell for example): When a common cell serves as the
standby cell, run the ADD CELL command. In this step, set Cell.MultiRruCellFlag to
BOOLEAN_FALSE(False), Cell.EuCellStandbyMode to STANDBY(Standby), and
the other parameters based on the parameter settings of the SFN cell on the primary
eNodeB.
ADD
CELL:LOCALCELLID=0,CELLNAME="TDD_SFN",FREQBAND=41,ULEARFCNCFGIND=NOT_CFG,DLEAR
FCN=40340,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW_N100,CELLID=100,PHYCELL
ID=100,FDDTDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEPATTERNS=SSP7,
EUCELLSTANDBYMODE=STANDBY,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,
EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEA
N_FALSE,TXRXMODE=4T4R;
3. (Optional) Perform this step only in the multi-carrier (10M+20M) scenario. In the single-
carrier scenario, perform Step 4. Run the ADD EUCELLPRIBBEQM command to add
primary baseband equipment configuration to a cell.
Example:
ADD EUCELLPRIBBEQM: LOCALCELLID=0,PRIBASEBANDEQMID=0;
ADD EUCELLPRIBBEQM: LOCALCELLID=1,PRIBASEBANDEQMID=1;
NOTE
If the standby cell is a common cell, the configuration is complete. If the standby cell is an SFN cell, set
the following parameters based on their settings on the primary eNodeB:
l SFN uplink scheduling switch (CELLALGOSWITCH.SfnUlSchSwitch)
l SFN downlink scheduling switch (CELLALGOSWITCH.SfnDlSchSwitch)
l SFN load-based adaptive algorithm switch
(CELLALGOSWITCH.SFNLOADBASEDADPTSWITCH)
l SFN algorithm switch (CELLALGOSWITCH.SfnAlgoSwitch)
l SFN PDCCH DCS threshold (CellPdcchAlgo.SfnPdcchDcsThd)
l SFN PDCCH SDMA threshold (CellPdcchAlgo.SfnPdcchSdmaThd)
l Downlink load measurement period (CellDlschAlgo.SfnDlLoadPeriod)
l SFN downlink high load threshold (CellDlschAlgo.SfnDlHighLoadThd)
l SFN downlink low load threshold (CellDlschAlgo.SfnDlLowLoadThd)
l Isolation decision threshold offset of downlink heavy-load level
(CellDlschAlgo.DlHighLoadSdmaThdOffset)
l Uplink load measurement period of SFN cell (CellUlschAlgo.SfnUlLoadPeriod)
l UL CoMP switch in SFN cell (CELLALGOSWITCH.SfnUplinkCompSwitch)
l Uplink joint reception switch of a specified number of
antennas(CELLALGOSWITCH.UlJRAntNumCombSw)
l UL CoMP admission threshold in SFN cell (CELLULCOMPALGO.SfnUlCompThd)
l Algorithm switch based on BBU coordination (ENODEBALGOSWITCH.OverBBUsSwitch)
----End
l If the value of the Cell instance state parameter is Normal, the SFN cell has been
activated.
l If the value of the Cell topo type parameter is SFN Type, the cell is an SFN cell.
l If the value of the Work Status parameter is Normal for all RRUs, all RRUs in the SFN
cell have been activated.
10.5.6 Deactivation
Example:
DEA CELL: LocalCellId=0;
Step 2 Choose Monitor > Signaling Trace > Signaling Trace Management. (The following steps
use only starting SFN detection as an example.)
Step 3 In the navigation tree, choose LTE > User Performance Monitoring > SFN Detection
Monitoring. In the SFN Detection Monitoring dialog box.
Step 5 Set the SFN detection parameters, and click Finish. The SFN monitoring task starts.
NOTE
In the Test Items area, the options PDCCH RRU Detect, UL RRU Detect, and DL RRU Detect are
available. You can select one or more among these monitoring items to monitor the related SFN
performance.
Step 6 On the right of the Signaling Trace Management tab page, select the SFN monitoring task
and right-click Query Result to check the results of the items described in Table 10-9.
Cell Global Identification This item indicates the global identification of a cell.
UL User Mode In the uplink, UEs can be classified into jointly scheduled UEs
and independently scheduled UEs.
DL User Mode In the downlink, UEs can be classified into jointly scheduled
UEs and independently scheduled UEs.
Physical Cell ID This item indicates the physical cell ID of an SFN cell.
UL RRU eNodeB ID This item indicates the eNodeB ID of the RRU used for uplink
transmission.
Uplink Sector Equipment This item indicates the ID of the uplink sector equipment.
ID
Uplink Sector Equipment This item indicates the ID of an uplink sector equipment
Group ID group.
UL RRU Slot No. This item indicates the attribute of an uplink RRU. Uplink
RRUs can be classified into:
l Work RRU
l Target RRU
l Other RRU
l Work RRU (Joint Reception)
l Target RRU (Joint Reception)
Uplink SRS RSRP This item indicates the uplink RSRP of SRSs measured by all
the RRUs serving the SFN cell.
Uplink SRS&DMRS This item indicates the SINR measured by layer 2 filtering.
SINR
Uplink DMRS SINR This item indicates the DMRS SINR and RSRP measured by
all the RRUs serving the SFN cell.
DL RRU eNodeB ID This item indicates the eNodeB ID of the RRU used for
downlink transmission.
Downlink Sector This item indicates the ID of the downlink sector equipment.
Equipment ID
DL RRU Slot No. This item indicates the attribute of a downlink RRU.
Downlink RRUs can be classified into:
l Work RRU
l Target RRU
PDCCH RRU eNodeB ID This item indicates the eNodeB ID of the RRU used for
PDCCH transmission.
PDCCH Sector This item indicates the ID of the PDCCH sector equipment.
Equipment ID
PDCCH RRU Slot No. This item indicates the attribute of a PDCCH RRU. PDCCH
RRUs can be classified into:
l Work RRU
l Target RRU
Table 10-10 and Table 10-11 show the monitoring results of Multi-user BF (User) and Multi-
user BF (Cell), respectively.
Number of RBs allocated to successfully Indicates the number of RBs that are
paired UEs for MUBF allocated to successfully paired UEs within
a period (one second).
Number of RBs allocated to successfully Indicates the number of RBs that are
paired UEs for SFNCBF allocated to successfully paired UEs within
a period (one second).
Number of RBs allocated to successfully Indicates the number of RBs that are
paired UEs for MUBF allocated to successfully paired UEs for
MUBF.
Number of successfully paired UE pairs for Indicates the number of successfully paired
MUBF UE pairs for MUBF.
Number of RBs allocated to paired UEs for Indicates the number of RBs that are
MUBF allocated to paired UEs for MUBF.
Number of RBs allocated to successfully Indicates the number of RBs that are
paired UEs for SFNCBF allocated to successfully paired UEs for
SFNCBF.
Number of successfully paired UE pairs for Indicates the number of successfully paired
SFNCBF UE pairs for SFNCBF.
Number of RBs allocated to paired UEs for Indicates the number of RBs allocated to
SFNCBF paired UEs for SFNCBF.
----End
Measuring counters
The counters listed in the following table are used to indicate UE attributes and distributions
of joint-scheduling UEs and independent-scheduling UEs when SFN and adaptive SFN/
SDMA are enabled.
10.8 Troubleshooting
SFN and Adaptive SFN/SDMA
If the BBP on which an SFN cell has been configured fails, the SFN cell is automatically
deactivated and ALM-29240 Cell Unavailable is reported. After the fault is rectified, the SFN
cell is automatically activated.
For details about alarm handling, see eNodeB Alarm Reference.
Bind the primary Manually select the primary BBP based on the primary-BBP
baseband equipment allocation information displayed in the DSP PRIBBPADJUST
to cells based on the command output.
following scheme.
Therefore, the values of the Cell Name and Cell ID parameters in the alarm information are
invalid.
l In BBU interconnection scenarios, a fault may occur between a BBU and a USU or
between USUs:
When a fault occurs between a BBU and a USU, the BBU and USU report
ALM-26315 Inter-BBU Port Connection Error and ALM-27109 Inter-Port
Connection Error, respectively. Run the DSP INTERCONTOPO command to
query the interconnection topologies on the eNodeB and USU.
If the interconnection cables are connected incorrectly, instruct field engineers to
adjust cable connections. When a fault occurs between USUs, the USU reports
ALM-27110 Inter-Port Connection Error. Run the DSP INTERCONTOPO
command to query the interconnection topology on the USU. If the interconnection
cables are connected incorrectly, instruct field engineers to adjust cable
connections.
11 Parameters
SfnDlSchAttriAdjsSwitch:Off, SfnCbfSwitch:Off,
SfnVoLteDlJSchSwitch:Off, SfnTarRruSelEnhS-
witch:Off, SfnTarRruAdjSelSwitch:Off
Unit: None
Actual Value Range: IntraBaseBandSwitch,
InterBaseBandSwitch, ComCoverUlCompSwitch,
SfnUplinkComp3CellSwitch
Default Value: IntraBaseBandSwitch:Off,
InterBaseBandSwitch:Off, ComCoverUlCompS-
witch:Off, SfnUplinkComp3CellSwitch:Off
CellUlC SfnUlCo MOD LOFD-0 SFN Meaning: Indicates the admission threshold for UL
ompAlg mpThd CELLU 03029 / Adaptiv CoMP UEs in an SFN cell.
o LCOMP TDLOF e SFN/ GUI Value Range: -15~15
ALGO D-00107 SDMA
5 Unit: dB
LST
CELLU LOFD-0 Actual Value Range: -15~15
LCOMP 70205 / Default Value: -8
ALGO TDLOF
D-00200
8
CellAlg SfnLoad MOD TDLOF Adaptiv Meaning: Indicates whether to enable load-based
oSwitch BasedA CELLA D-00200 e SFN/ adaptive adjustment in the adaptive SFN/SDMA
dptSwitc LGOSW 8 SDMA feature. If this switch is turned on, load-based
h ITCH adaptive adjustment is enabled, which increases the
LST proportion of joint-scheduling UEs and improves user
CELLA experience when the network load is light, and
LGOSW increases the proportion of independent-scheduling
ITCH UEs and ensures the spectral efficiency when the
network load is heavy. If this switch is turned off,
load-based adaptive adjustment in the adaptive SFN/
SDMA feature cannot be enabled. This switch applies
only to LTE TDD cells.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CellDlsc SfnDlHi MOD TDLOF Adaptiv Meaning: Indicates the PRB usage threshold used to
hAlgo ghLoad CELLD D-00200 e SFN/ determine the change from low load to high load in
Thd LSCHA 8/ SDMA the downlink.
LGO LOFD-0 GUI Value Range: 0~100
DSP 70205
Unit: %
CELLC
OVENH Actual Value Range: 0~100
STUS Default Value: 45
LST
CELLD
LSCHA
LGO
CellDlsc SfnDlLo MOD TDLOF Adaptiv Meaning: Indicates the PRB usage threshold used to
hAlgo wLoadT CELLD D-00200 e SFN/ determine the change from high load to low load in
hd LSCHA 8/ SDMA the downlink.
LGO LOFD-0 GUI Value Range: 0~100
DSP 70205
Unit: %
CELLC
OVENH Actual Value Range: 0~100
STUS Default Value: 30
LST
CELLD
LSCHA
LGO
CellPdc SfnPdcc MOD TDLOF Adaptiv Meaning: Indicates the threshold of isolation for
chAlgo hDcsTh CELLP D-00200 e SFN/ determining whether to enable PDCCH selective
d DCCHA 8 SDMA transmission in adaptive SFN/SDMA scenarios. For a
LGO UE, if the ratio between the RSRP of strong signals
LST and that of weak signals from multiple RRUs in an
CELLP SFN cell is greater than or equal to the value of this
DCCHA parameter, the power of weak signals is not
LGO transmitted. This parameter applies only to LTE TDD
cells.
GUI Value Range: 1~100
Unit: 0.5dB
Actual Value Range: 1~50
Default Value: 40
CellPdc SfnPdcc MOD TDLOF Adaptiv Meaning: Indicates the threshold of isolation for
chAlgo hSdmaT CELLP D-00200 e SFN/ determining whether to enable PDCCH SDMA in
hd DCCHA 8 SDMA adaptive SFN/SDMA scenarios. For a UE, if the ratio
LGO between the RSRP of RRUs with strong signals and
LST that of RRUs with weak signals in an SFN cell is
CELLP equal to or greater than the value of this parameter, the
DCCHA UE only use resources of RRUs with strong signals
LGO while RRUs with weak signals can be reused by other
UEs.
GUI Value Range: 0~100
Unit: 0.5dB
Actual Value Range: 0~50
Default Value: 24
Cell EuCellS ADD LBFD-0 Broadca Meaning: Indicates the active or standby mode of the
tandby CELL 02009 / st of cell. A cell is in active mode by default. If this
Mode MOD TDLBF system parameter is set to STANDBY, an inter-BBU SFN
CELL D-00200 informat auxiliary cell can roll back to the standby mode to
9 ion provide services if inter-BBU faults occur. Only
LST common cells, SFN cells or MPRU_AGGREGATION
CELL cells support the standby mode.
GUI Value Range: ACTIVE(Active),
STANDBY(Standby)
Unit: None
Actual Value Range: ACTIVE, STANDBY
Default Value: ACTIVE(Active)
Cell MultiRr ADD LOFD-0 SFN Meaning: Indicates whether to enable or disable the
uCellFla CELL 03029 / Adaptiv multi-RRU cell feature.
g MOD TDLOF e SFN/ GUI Value Range: BOOLEAN_FALSE(False),
CELL D-00107 SDMA BOOLEAN_TRUE(True)
5
LST Inter- Unit: None
CELL TDLOF BBP
D-00200 Actual Value Range: BOOLEAN_FALSE,
SFN BOOLEAN_TRUE
8
Inter- Default Value: BOOLEAN_FALSE(False)
TDLOF BBU
D-00109 SFN
8
Inter-
TDLOF BBP
D-00108 Adaptiv
0 e SFN/
TDLOF SDMA
D-00108 Inter-
1 BBU
TDLOF Adaptiv
D-00108 e SFN/
2 SDMA
Cell MultiRr ADD LOFD-0 SFN Meaning: Indicates the type of the multi-RRU cell.
uCellMo CELL 03029 / Adaptiv GUI Value Range: SFN(SFN),
de MOD TDLOF e SFN/ CELL_COMBINATION(Cell Combination),
CELL D-00107 SDMA TWO_RRU_COMBINATION(TWO RRU
5 Combination), DIGITAL_COMBINATION(Cell
LST Inter-
CELL LOFD-0 BBP Digital Combination),
70205 / SFN MPRU_AGGREGATION(MPRU_AGGREGATION)
TDLOF Unit: None
D-00200 Inter-
8 BBU Actual Value Range: SFN, CELL_COMBINATION,
SFN TWO_RRU_COMBINATION,
TDLOF DIGITAL_COMBINATION,
D-00109 Inter-
BBP MPRU_AGGREGATION
8
Adaptiv Default Value: SFN(SFN)
TDLOF e SFN/
D-00108 SDMA
0
Inter-
TDLOF BBU
D-00108 Adaptiv
1 e SFN/
TDLOF SDMA
D-00108
2
CellAlg SfnUlSc MOD None None Meaning: Indicates the SFN uplink scheduling mode.
oSwitch hSwitch CELLA The uplink scheduling modes include the joint
LGOSW scheduling mode, and the auto-selection mode
ITCH between joint scheduling and independent scheduling.
LST GUI Value Range: ADAPTIVE(Adaptive scheduling),
CELLA JOINT(Joint scheduling)
LGOSW Unit: None
ITCH
Actual Value Range: ADAPTIVE, JOINT
Default Value: JOINT(Joint scheduling)
CellAlg SfnDlSc MOD None None Meaning: Indicates the SFN downlink scheduling
oSwitch hSwitch CELLA mode. The downlink scheduling modes include the
LGOSW joint scheduling mode, and the auto-selection mode
ITCH between joint scheduling and independent scheduling.
LST GUI Value Range: ADAPTIVE(Adaptive scheduling),
CELLA JOINT(Joint scheduling)
LGOSW Unit: None
ITCH
Actual Value Range: ADAPTIVE, JOINT
Default Value: JOINT(Joint scheduling)
CellDlsc DlHigh MOD TDLOF Adaptiv Meaning: Indicates the offset to the high load
hAlgo LoadSd CELLD D-00200 e SFN/ threshold in the downlink of an adaptive SFN cell.
maThdO LSCHA 8/ SDMA GUI Value Range: -25~25
ffset LGO LOFD-0
70205 Unit: dB
DSP
CELLC Actual Value Range: -25~25
OVENH Default Value: 0
STUS
LST
CELLD
LSCHA
LGO
CellAlg UlJRAnt MOD LOFD-0 Intra- Meaning: Indicates whether to enable UL joint
oSwitch NumCo CELLA 01066 / eNodeB reception among cells each with the specific number
mbSw LGOSW TDLOF UL of RX antennas. Ul1R1RJRSwitch: Indicates whether
ITCH D-00106 CoMP to enable UL joint reception among cells each with
LST 6 Intra- one RX antenna. If this option is selected, UL joint
CELLA LOFD-0 eNodeB reception is enabled among such cells. You are
LGOSW 70222 UL advised to select this option when the serving cell and
ITCH CoMP coordinating cells are not connected based on relaxed
LOFD-0 backhaul. If this option is deselected, UL joint
70223 / Phase II
reception among such cells is disabled. This option
TDLOF UL applies only to LTE FDD. Ul1R2RJRSwitch:
D-08120 CoMP Indicates whether to enable UL joint reception among
7 based on cells each with one RX antenna and cells each with
LOFD-0 Coordin two RX antennas. If this option is selected, UL joint
03029 ated reception among such cells is enabled. You are
BBU advised to select this option when the serving cell and
LOFD-0
70205 SFN coordinating cells are not connected based on relaxed
Adaptiv backhaul. If this option is deselected, UL joint
e SFN/ reception among such cells is disabled. This option
SDMA applies only to LTE FDD. Ul2R8RJRSwitch:
Indicates whether to enable UL joint reception among
cells each with two RX antennas and cells each with
eight RX antennas. If this option is selected, UL joint
reception among such cells is enabled. If this option is
deselected, UL joint reception among such cells is
disabled. This option applies only to LTE TDD cells
in cell combination scenarios. Ul4R8RJRSwitch:
Indicates whether to enable UL joint reception among
cells each with four RX antennas and cells each with
eight RX antennas. If this option is selected, UL joint
reception among such cells is enabled. If this option is
deselected, UL joint reception among such cells is
disabled. This option applies only to LTE TDD.
Ul8R8RJRSwitch: Indicates whether to enable UL
joint reception among cells each with eight RX
antennas. If this option is selected, UL joint reception
among such cells is enabled. If this option is
deselected, UL joint reception among such cells is
disabled. This option applies only to LTE TDD. When
UL CoMP is enabled or switches related to joint
reception in SFN cells are turned on, UL joint
reception among cells each with two RX antennas and
UL joint reception among cells each with four RX
antennas are enabled by default. Ul1R4RJRSwitch:
Indicates whether to enable UL joint reception among
cells each with one RX antenna and cells each with
four RX antennas. If this option is selected, UL joint
reception among such cells is enabled. You are
Intra-
band
Carrier
Aggrega
tion for
Downlin
k 2CC
in
30MHz
Inter-
BBU
UL
CoMP
Inter-
eNodeB
VoLTE
CoMP
BBP WM ADD None None Meaning: Indicates the working mode of the baseband
BRD processing board. There are seven working modes:
MOD FDD, TDD, HYBRID, TDD_ENHANCE,
BBP TDD_8T8R, TDD_TL and FDD_ATG. The
Frequency Division Duplex (FDD) mode carries the
LST traditional voice and data services. TDD is short for
BBP Time Division Duplex. The HYBRID mode is a
combination of FDD and IMB modes. In Integrated
Mobile Broadcasting (IMB) mode, the baseband
processing board carries the mobile TV services. The
value TDD_ENHANCE indicates the TDD mode
integrated with the BeamForming (BF) function. The
BF function provides the data transmission service in
transmission modes 7 and 8 defined in protocols. For
details, see 3GPP TS 36.213. In TDD_8T8R mode,
the baseband processing board supports TD-LTE
single-mode 8T8R. In addition, the baseband
processing board supports the BF function and CPRI
specifications are applied between the BBU and RRU.
In TDD_TL mode, the baseband processing board
supports the TD-LTE&TDS-CDMA dual mode and
the TD-LTE single mode. In addition, the baseband
processing board supports 8T8R BF and 2T2R
Multiple-Input Multiple-Output (MIMO) and CMCC
TD-LTE IR specifications are applied between the
BBU and RRU. In FDD_ATG mode, the baseband
processing board supports communication between
Air and Ground. The FDD_ATG mode applies only to
communication between air and ground.
GUI Value Range: FDD(Frequency Division Duplex),
TDD(Time Division Duplex), HYBRID(HYBRID),
TDD_ENHANCE(Support TDD BF),
TDD_8T8R(Support CPRI ports), TDD_TL(Support
CMCC TDS and TDL dual modes),
FDD_ATG(Support air-ground communication)
Unit: None
Actual Value Range: FDD, TDD, HYBRID,
TDD_ENHANCE, TDD_8T8R, TDD_TL, FDD_ATG
Default Value: FDD(Frequency Division Duplex)
PUCCH DeltaShi MOD LBFD-0 Physical Meaning: Indicates the interval between cyclic shifts
Cfg ft PUCCH 02003 / Channel used for the PUCCH. The interval between cyclic
CFG TDLBF Manage shifts used for the PUCCH can be acquired based on
LST D-00200 ment the average delay spread in the cell, where the average
PUCCH 3 delay spread is acquired based on the networking
CFG environment. The parameter value
DS1_DELTA_SHIFT is not supported by the LBBPc.
If a cell is established on an LBBPc but this parameter
is set to DS1_DELTA_SHIFT, the value of this
parameter is automatically changed to
DS2_DELTA_SHIFT when this parameter takes
effect. For details, see 3GPP TS 36.211.
GUI Value Range: DS1_DELTA_SHIFT(ds1),
DS2_DELTA_SHIFT(ds2),
DS3_DELTA_SHIFT(ds3)
Unit: None
Actual Value Range: DS1_DELTA_SHIFT,
DS2_DELTA_SHIFT, DS3_DELTA_SHIFT
Default Value: DS1_DELTA_SHIFT(ds1)
Cell FreqBan ADD LBFD-0 Cell Meaning: Indicates the frequency band in which a cell
d CELL 0201803 Selectio operates. For details about this parameter, see 3GPP
ADD / n and TS 36.104. For details about the usage of 252 to 255,
CELLB TDLBF Re- see the following LTE-U forum document: eNodeB
AND D-00201 selection Minimum Requirements for LTE-U SDL V1.0.
803 Broadca GUI Value Range: 1~256
LST
CELLB LBFD-0 st of Unit: None
AND 02009 / system
TDLBF informat Actual Value Range: 1~256
MOD D-00200 ion Default Value: None
CELL 9 Multi-
RMV LBFD-0 Band
CELLB 70103 / Compati
AND TDLBF bility
LST D-00201 Enhance
CELL 806 ment /
LAOFD
-111301:
LAA(Li
censed
Assisted
Access )
for DL 2
Carrier /
LAOFD
-111304:
LAA
FCS
(Freque
ncy
Channel
Selectio
n) /
LAOFD
-111305:
LAA
Cell
On/Off
Cell UlEarfc ADD LBFD-0 Cell Meaning: Indicates whether to configure the uplink
nCfgInd CELL 0201803 Selectio EARFCN of the cell.
MOD / n and GUI Value Range: NOT_CFG(Not configure),
CELL TDLBF Re- CFG(Configure)
D-00201 selection
LST 803 Unit: None
CELL Broadca
LBFD-0 st of Actual Value Range: NOT_CFG, CFG
02009 / system Default Value: NOT_CFG(Not configure)
TDLBF informat
D-00200 ion
9
Cell DlEarfc ADD LBFD-0 Broadca Meaning: Indicates the DL EARFCN of the cell. For
n CELL 02009 / st of details about this parameter, see 3GPP TS 36.104. For
MOD TDLBF system the detailed usage of 255144 to 262143, see the
CELL D-00200 informat following LTE-U forum document: eNodeB Minimum
9 ion Requirements for LTE-U SDL V1.0.
LST
CELL LBFD-0 Coverag GUI Value Range:
0201801 e Based 0~65535,66436~67335,255144~256143,260894~2621
/ Intra- 43
TDLBF frequenc Unit: None
D-00201 y
801 Actual Value Range:
Handov 0~65535,66436~67335,255144~256143,260894~2621
LBFD-0 er 43
0201803 Cell
/ Default Value: None
Selectio
TDLBF n and
D-00201 Re-
803 selection
/ /
LAOFD LAOFD
-111305 -111301:
LAA(Li
censed
Cell UlBand ADD LOFD-0 Compac Meaning: Indicates the UL bandwidth of the cell,
Width CELL 01051 t which is based on the number of resource blocks
MOD LBFD-0 Bandwi (RBs). The value CELL_BW_N25 indicates a cell
CELL 02009 / dth bandwidth of 25 RBs. The value CELL_BW_N50
TDLBF Broadca indicates a cell bandwidth of 50 RBs. The mapping
LST between the parameter value and the actual cell
CELL D-00200 st of
9 system bandwidth (that is, the number of RBs) can be
informat deduced similarly. For details, see 3GPP TS 36.104.
TDLBF
D-00100 ion GUI Value Range: CELL_BW_N6(1.4M),
3 Scalable CELL_BW_N15(3M), CELL_BW_N25(5M),
Bandwi CELL_BW_N50(10M), CELL_BW_N75(15M),
dth CELL_BW_N100(20M)
Unit: None
Actual Value Range: CELL_BW_N6,
CELL_BW_N15, CELL_BW_N25, CELL_BW_N50,
CELL_BW_N75, CELL_BW_N100
Default Value: None
Cell DlBand ADD LOFD-0 Compac Meaning: Indicates the DL bandwidth of the cell,
Width CELL 01051 t which is based on the number of resource blocks
MOD LBFD-0 Bandwi (RBs). The value CELL_BW_N25 indicates a cell
CELL 02009 / dth bandwidth of 25 RBs. The value CELL_BW_N50
TDLBF Broadca indicates a cell bandwidth of 50 RBs. The mapping
DSP between the parameter value and the actual cell
DDCEL D-00200 st of
9 system bandwidth (that is, the number of RBs) can be
LGROU deduced similarly. For details, see 3GPP TS 36.104.
P TDLBF informat
D-00100 ion GUI Value Range: CELL_BW_N6(1.4M),
LST CELL_BW_N15(3M), CELL_BW_N25(5M),
CELL 3 Scalable
Bandwi CELL_BW_N50(10M), CELL_BW_N75(15M),
dth CELL_BW_N100(20M)
Unit: None
Actual Value Range: CELL_BW_N6,
CELL_BW_N15, CELL_BW_N25, CELL_BW_N50,
CELL_BW_N75, CELL_BW_N100
Default Value: None
Cell CellId ADD LBFD-0 Broadca Meaning: Indicates the ID of the E-UTRAN cell. The
CELL 02009 / st of combination of this parameter and the eNodeB ID
MOD TDLBF system forms the E-UTRAN cell identity. The combination of
CELL D-00200 informat the E-UTRAN cell identity and the PLMN identity
9 ion forms the ECGI. For details, see 3GPP TS 36.413.
DSP
CELLC GUI Value Range: 0~255
AMCST Unit: None
ATUS Actual Value Range: 0~255
LST Default Value: None
CELL
Cell PhyCellI ADD LOFD-0 Compac Meaning: Indicates the physical cell ID. For details,
d CELL 01051 t see 3GPP TS 36.331.
MOD LBFD-0 Bandwi GUI Value Range: 0~503
CELL 02009 / dth
Unit: None
LST TDLBF Broadca
D-00200 st of Actual Value Range: 0~503
CELL
9 system Default Value: None
informat
ion
Cell FddTddI ADD LBFD-0 Broadca Meaning: Indicates the duplex mode of the cell.
nd CELL 02009 st of CELL_FDD indicates the FDD mode, and
MOD TDLBF system CELL_TDD indicates the TDD mode.
CELL D-00100 informat GUI Value Range: CELL_FDD(FDD),
7 ion CELL_TDD(TDD)
LST
CELL TDLBF Basic Unit: None
D-00100 uplink-
downlin Actual Value Range: CELL_FDD, CELL_TDD
701
k Default Value: None
TDLBF subfram
D-00100 e
702 configur
TDLOF ation
D-00102 uplink-
6 downlin
TDLOF k
D-00102 subfram
601 e
TDLOF configur
D-00102 ation
602 type1&2
TDLOF uplink-
D-00102 downlin
603 k special
subfram
e
configur
ation
type 7
Optional
uplink-
downlin
k
subfram
e
configur
ation
uplink-
downlin
k
subfram
e
configur
ation
type 0
uplink-
downlin
k special
subfram
e
configur
ation
type 4
uplink-
downlin
k special
subfram
e
configur
ation
type 5
Cell Subfram ADD LBFD-0 Broadca Meaning: Indicates the ratio of UL subframes to DL
eAssign CELL 02009 st of subframes in a TDD cell. For details, see 3GPP TS
ment MOD TDLBF system 36.211.
CELL D-00100 informat GUI Value Range: SA0(SA0), SA1(SA1), SA2(SA2),
7 ion SA3(SA3), SA4(SA4), SA5(SA5), SA6(SA6)
LST
CELL TDLBF Basic Unit: None
D-00100 uplink-
downlin Actual Value Range: SA0, SA1, SA2, SA3, SA4,
701 SA5, SA6
k
TDLBF subfram Default Value: SA0(SA0)
D-00100 e
702 configur
TDLOF ation
D-00102 uplink-
6 downlin
TDLOF k
D-00102 subfram
601 e
TDLOF configur
D-00102 ation
602 type1&2
TDLOF uplink-
D-00102 downlin
603 k special
subfram
e
configur
ation
type 7
Optional
uplink-
downlin
k
subfram
e
configur
ation
uplink-
downlin
k
subfram
e
configur
ation
type 0
uplink-
downlin
k special
subfram
e
configur
ation
type 4
uplink-
downlin
k special
subfram
e
configur
ation
type 5
Cell SpecialS ADD LBFD-0 Broadca Meaning: Indicates the ratio of special UL subframes
ubframe CELL 02009 st of to special DL subframes in a TDD cell. For details,
Patterns MOD TDLBF system see 3GPP TS 36.211.
CELL D-00100 informat GUI Value Range: SSP0(SSP0), SSP1(SSP1),
7 ion SSP2(SSP2), SSP3(SSP3), SSP4(SSP4), SSP5(SSP5),
LST
CELL TDLBF Basic SSP6(SSP6), SSP7(SSP7), SSP8(SSP8), SSP9(SSP9)
D-00100 uplink- Unit: None
701 downlin
k Actual Value Range: SSP0, SSP1, SSP2, SSP3, SSP4,
TDLBF subfram SSP5, SSP6, SSP7, SSP8, SSP9
D-00100 e Default Value: SSP0(SSP0)
702 configur
TDLOF ation
D-00102 uplink-
6 downlin
TDLOF k
D-00102 subfram
601 e
TDLOF configur
D-00102 ation
602 type1&2
TDLOF uplink-
D-00102 downlin
603 k special
subfram
e
configur
ation
type 7
Optional
uplink-
downlin
k
subfram
e
configur
ation
uplink-
downlin
k
subfram
e
configur
ation
type 0
uplink-
downlin
k special
subfram
e
configur
ation
type 4
uplink-
downlin
k special
subfram
e
configur
ation
type 5
Cell RootSeq ADD LBFD-0 Random Meaning: Indicates the first logical root sequence,
uenceId CELL 02010 / Access which is used to generate the preamble sequence.
x MOD TDLBF Procedu Each logical root sequence corresponds to a physical
CELL D-00201 re root sequence. For the mapping between logical root
0 sequences and physical root sequences, see 3GPP TS
LST 36.211.
CELL
GUI Value Range: 0~837
Unit: None
Actual Value Range: 0~837
Default Value: None
Cell SectorE ADD None None Meaning: Indicates the number of physical cells
qmNum CELL consisting an SFN cell. In macro eNodeBs, this
MOD parameter value equals the number of sector
CELL equipment sets serving an SFN cell. In LampSite
eNodeB, this parameter value equals the number of
LST sector equipment groups serving an SFN cell. In
CELL macro and LampSite eNodeBs, the parameter value
equals the sum of the sector equipment sets and sector
equipment groups serving an SFN cell.
GUI Value Range: 2~7
Unit: None
Actual Value Range: 2~7
Default Value: 3
Cell TxRxM ADD None None Meaning: Indicates the transmission and reception
ode CELL mode of the cell.
MOD GUI Value Range: 1T1R, 1T2R, 2T2R, 2T4R, 4T4R,
CELL 8T8R, 2T8R, 4T8R
LST Unit: None
CELL Actual Value Range: 1T1R, 1T2R, 2T2R, 2T4R,
4T4R, 8T8R, 2T8R, 4T8R
Default Value: None
BASEB BASEB ADD None None Meaning: Indicates the number of the baseband
ANDEQ ANDEQ BASEB equipment.
M MID ANDEQ GUI Value Range: 0~23
M
Unit: None
LST
BASEB Actual Value Range: 0~23
ANDEQ Default Value: None
M
MOD
BASEB
ANDEQ
M
RMV
BASEB
ANDEQ
M
BASEB BASEB ADD None None Meaning: Indicates the type of baseband equipment.
ANDEQ ANDEQ BASEB GUI Value Range: UL(UL), DL(DL),
M MTYPE ANDEQ ULDL(Combined UL and DL)
M
Unit: None
LST
BASEB Actual Value Range: UL, DL, ULDL
ANDEQ Default Value: None
M
MOD
BASEB
ANDEQ
M
RMV
BASEB
ANDEQ
M
BASEB UMTSD ADD None None Meaning: Indicates the demodulation mode of uplink
ANDEQ EMMO BASEB baseband equipment for UMTS mode. When uplink
M DE ANDEQ (or uplink and downlink) baseband equipment is
M added, its demodulation mode must be specified.
LST Different demodulation modes can be specified for
BASEB different sets of uplink (or uplink and downlink)
ANDEQ baseband equipment. This parameter is not used for
M GSM mode, and therefore it is recommended that this
parameter be set to NULL for GSM mode. This
parameter cannot be set to NULL for UMTS mode.
This parameter is not used for LTE mode, and
therefore it is recommended that this parameter be set
to NULL for LTE mode.
GUI Value Range: NULL(NULL), DEM_4_CHAN(4-
Channels Demodulation Mode),
DEM_ECON_4_CHAN(Economical 4-Channels
Demodulation Mode), DEM_2_CHAN(2-Channels
Demodulation Mode)
Unit: None
Actual Value Range: NULL, DEM_4_CHAN,
DEM_ECON_4_CHAN, DEM_2_CHAN
Default Value: None
eUCellS LocalCe ADD None None Meaning: Indicates the local cell identity. It uniquely
ectorEq llId EUCEL identifies a cell within an eNodeB.
m LSECT GUI Value Range: 0~255
OREQ
M Unit: None
eUCellS SectorE ADD None None Meaning: Indicates the ID of the sector device that
ectorEq qmId EUCEL serves the cell,it uniquely identifies a sector device
m LSECT within an eNodeB.
OREQ GUI Value Range: 0~65535
M
Unit: None
DSP
EURTW Actual Value Range: 0~65535
P Default Value: None
LST
EUCEL
LSECT
OREQ
M
MOD
EUCEL
LSECT
OREQ
M
RMV
EUCEL
LSECT
OREQ
M
RST
EUCEL
LRES
DSP
INREC
PDSCH Referen MOD LBFD-0 Dynami Meaning: Indicates the cell reference signal power of
Cfg ceSignal PDSCH 02016 / c each physical antenna. However, the cell reference
Pwr CFG TDLBF Downlin signal power delivered in SIB2 is that of each logical
LST D-00201 k Power antenna.
PDSCH 6 Allocati GUI Value Range: -600~500
CFG LBFD-0 on
Unit: 0.1dBm
02009 / Broadca
TDLBF st of Actual Value Range: -60~50
D-00200 system Default Value: 182
9 informat
ion
EuCellP LocalCe ADD None None Meaning: Indicates the local cell identity. It uniquely
riBBEq llId EUCEL identifies a cell within an eNodeB.
m LPRIBB GUI Value Range: 0~255
EQM
Unit: None
LST
EUCEL Actual Value Range: 0~255
LPRIBB Default Value: None
EQM
MOD
EUCEL
LPRIBB
EQM
RMV
EUCEL
LPRIBB
EQM
CASCA CN DSP None None Meaning: Indicates the cabinet number of the board
DEPOR BBPLN where the interconnection port is located.
T KSTAT GUI Value Range: 0~7
DSP Unit: None
PORTM
ODE Actual Value Range: 0~7
CASCA SRN DSP None None Meaning: Indicates the subrack number of the board
DEPOR BBPLN where the interconnection port is located.
T KSTAT GUI Value Range: 0~1
DSP Unit: None
PORTM
ODE Actual Value Range: 0~1
CASCA SN DSP None None Meaning: Indicates the slot number of the board
DEPOR BBPLN where the interconnection port is located.
T KSTAT GUI Value Range: 0~7
DSP Unit: None
PORTM
ODE Actual Value Range: 0~7
CASCA PN DSP None None Meaning: Indicates the number of the port that carries
DEPOR BBPLN the interconnection link.
T KSTAT GUI Value Range: 0~6,8
DSP Unit: None
PORTM
ODE Actual Value Range: 0~6,8
CASCA SW SET None None Meaning: Indicates the enabled/disabled state of the
DEPOR CASCA port. Alarms can be detected and reported through the
T DEPOR port only when the state of the port is ON.
T GUI Value Range: OFF(Off), ON(On)
LST Unit: None
CASCA
DEPOR Actual Value Range: OFF, ON
T Default Value: OFF(Off)
EQUIP ODIID SET None None Meaning: Indicates the ID of the open DU interface
MENT EQUIP (ODI). If this parameter is set to 0, no ID is configured
MENT for the ODI and this base station cannot communicate
LST with other base stations. This parameter applies only
EQUIP to Cloud BB scenarios. In non-Cloud BB scenarios,
MENT the parameter should be set to 0.
GUI Value Range: 0~254
Unit: None
Actual Value Range: 0~254
Default Value: 0
SfnCell LocalCe ADD None None Meaning: Indicates the local ID of the cell. It uniquely
Bind llId SFNCE identifies a cell within a eNodeB.
LLBIN GUI Value Range: 0~255
D
Unit: None
LST
SFNCE Actual Value Range: 0~255
LLBIN Default Value: None
D
RMV
SFNCE
LLBIN
D
SfnCell eNodeB ADD None None Meaning: Indicates the ID of the auxiliary eNodeB.
Bind Id SFNCE GUI Value Range: 0~1048575
LLBIN
D Unit: None
SfnAux SectorE ADD TDLOF Inter- Meaning: Indicates the ID of the sector device. It
ResBind qmId SFNAU D-00108 BBU uniquely identifies a piece of sector equipment within
XRESBI 0 SFN an eNodeB.
ND TDLOF Inter- GUI Value Range: 0~65535
LST D-00108 BBU Unit: None
SFNAU 2 Adaptiv
XRESBI e SFN/ Actual Value Range: 0~65535
ND SDMA Default Value: None
MOD
SFNAU
XRESBI
ND
RMV
SFNAU
XRESBI
ND
SfnAux eNodeB ADD None None Meaning: Indicates the ID of the main eNodeB.
ResBind Id SFNAU GUI Value Range: 0~1048575
XRESBI
ND Unit: None
SfnAux LocalCe ADD None None Meaning: Indicates the local cell ID of a cell of the
ResBind llId SFNAU primary eNodeB. It uniquely identifies a cell within
XRESBI the primary eNodeB.
ND GUI Value Range: 0~255
MOD Unit: None
SFNAU
XRESBI Actual Value Range: 0~255
ND Default Value: None
RMV
SFNAU
XRESBI
ND
LST
SFNAU
XRESBI
ND
12 Counters
13 Glossary
14 Reference Documents