Seleksi Penerimaan Cpns Bekraf 2018 2 PDF

SFN Feature Parameter Description Page 1 of 43
eRAN TDD
eRAN TDD 13.0
SFN Feature Parameter Description
Issue 03
Date 2018-01-29
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2018. All rights reserved.

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

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Contents
1 About This Document
http://127.0.0.1:52199/hedex/pages/31189882/04/31189882/04/resources/hert/ref-ne/pdf/td... 10/3/2018
1.1 Scope
1.2 Intended Audience
1.3 Change History
1.4 Differences Between eNodeB Types
2 Overview
2.1 Introduction
2.2 Benefits
2.3 Architecture
3 Feature Principles
3.1 Joint-Scheduling-based SFN
3.2 Adaptive SFN/SDMA
3.2.1 Introduction
3.2.2 UE Attribute Decision
3.2.3 Adaptive Resource Scheduling
3.3 PDCCH Enhancement in Adaptive SFN/SDMA
3.3.1 PDCCH DCS in Adaptive SFN/SDMA
3.3.2 PDCCH SDMA in Adaptive SFN/SDMA
3.4 Coordination Between Adaptive SFN/SDMA and Multiple-Antenna Techniques
3.4.1 Inter-RRU CBF in Adaptive SFN/SDMA
3.4.2 MU-Beamforming in Adaptive SFN/SDMA
3.4.3 Adaptive SFN/SDMA+MU MIMO
4 Intra-BBP SFN Features
5 Inter-BBP SFN Features
6 Inter-BBU SFN Features
7 Application Restrictions
8 Related Features
8.1 TDLOFD-001075 SFN
8.2 TDLOFD-002008 Adaptive SFN/SDMA
8.3 TDLOFD-001098 Inter-BBP SFN
8.4 TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA
8.5 TDLOFD-001080 Inter-BBU SFN
8.6 TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA
8.7 TDLOFD-070227 PDCCH DCS in SFN
8.8 TDLOFD-081221 PDCCH SDMA in SFN
9 Network Impact
10 Engineering Guidelines
10.1 When to Use
10.2 Required Information
10.2.1 Traffic Requirements and Distribution of Interference Areas
10.2.2 Interference eNodeB and LBBP Configurations
10.3 Planning
10.4 Deployment of Intra- and Inter-BBP SFN Techniques
10.4.1 Requirements
10.4.2 Precautions
10.4.3 Hardware Adjustment
10.4.4 Data Preparation and Feature Activation
10.4.4.1 Data Preparation
10.4.4.2 Using the CME
10.4.4.3 Using MML Commands
10.4.5 Activation Observation
10.4.6 Deactivation
10.5 Deployment of Inter-BBU SFN Techniques
10.5.1 Requirements
10.5.2 Precautions

10.5.6 Deactivation
10.6 Performance Monitoring
10.7 Parameter Optimization
10.8 Possible Issues
11 Glossary
12 Reference Documents
1 About This Document
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:
• TDLOFD-001075 SFN
• TDLOFD-002008 Adaptive SFN/SDMA
• TDLOFD-001098 Inter-BBP SFN
• TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA
• TDLOFD-001080 Inter-BBU SFN
• TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA
• TDLOFD-070227 PDCCH DCS in SFN
• TDLOFD-081221 PDCCH SDMA in SFN
Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to the corresponding software release. For future software releases, refer to the
corresponding updated product documentation.
This document applies only to LTE TDD. Any "LTE" in this document refers to LTE TDD, and "eNodeB" refers to LTE TDD eNodeB.
In this document, eNodeBs only refers to DBS3900, DBS5900 and LampSite eNodeBs.
1.2 Intended Audience

This document is intended for personnel who:
• Need to understand the features described herein

• Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are two types of changes:
• Feature change
Changes in features and parameters of a specified version as well as the affected entities
• Editorial change
Changes in wording or addition of information and any related parameters affected by editorial changes. Editorial change does not specify the affected entities.
eRAN TDD 13.0 03 (2018-01-29)
This issue includes the following changes.
Change Type Change Description Parameter Change Affected Entity
Feature change None None N/A
Editorial change Revised the descriptions of mutually exclusive features in 8.1 TDLOFD- None N/A
001075 SFN.
eRAN TDD 13.0 02 (2017-12-25)
Feature change Added an option to specify whether to enable the optimization to resolve Added the SfnDlRblerOptSwitch • 3900 and 5900 series
consecutive downlink bit errors. For details, see 10.4.4.1 Data option to the base stations
Preparation. CellAlgoSwitch.SfnAlgoSwitch • DBS3900 LampSite
parameter. and DBS5900
LampSite
Editorial change Revised descriptions in this document. None N/A
eRAN TDD 13.0 01 (2017-09-05)
eRAN TDD 13.0 Draft B (2017-08-06)
eRAN TDD 13.0 Draft A (2017-06-30)
This issue introduces the following changes to Issue 03 (2017-06-29) of eRAN TDD 12.1.
Feature change None None • 3900 and 5900 series

base stations
• DBS3900 LampSite
and DBS5900
LampSite
1.4 Differences Between eNodeB Types

The features described in this document apply only to macro eNodeBs and LampSite eNodeBs.
LampSite eNodeBs support only the 2T2R mode, but do not support 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 serious problem on intra-frequency networks. This problem is even more serious at the cell edge where the signal to interference plus noise ratio (SINR)
is low. In densely populated urban areas where sites are densely deployed to ensure network coverage, interference between control channels of neighboring cells is severe,
reducing coverage of control channels. Inter-eNodeB interference also causes the performance of traffic channels to deteriorate. When interference is severe, high-order modulation
schemes cannot be used and LTE advantages are compromised.
Single frequency network (SFN) has been introduced to mitigate the interference. SFN allows two to seven RRUs to serve the same SFN cell, changing what had been 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
SFN provides the following benefits:
• The SINR of the entire network increases when SFN is deployed on a large scale, as the inter-RRU interference is converted into useful signals. For example:
◾ The average SINRs of the PDCCH and PDSCH increase by 2 dB to 3 dB when there are three RRUs serving the same SFN cell in a typical dense urban area.
◾ The average SINRs of the PDCCH and PDSCH increase by 5 dB to 6 dB when there are seven RRUs serving the same SFN cell in a typical dense urban
area.
• The coverage areas of cells are enlarged, the number of handovers decreases, the handover success rate increases, and the service drop rate decreases.
• Enabling the SFN feature, however, decreases the overall system capacity to some extent. In a typical dense urban area that is fully loaded, the average downlink
throughput of a single SFN cell served by three RF modules decreases to approximately 51% of that of three non-SFN cells served by three RF modules.
• To maintain system capacity, adaptive SFN/SDMA is adopted. In a typical dense urban area that is fully loaded, the average downlink throughput of a single SFN cell
served by three RF modules decreases to approximately 85% to 95% of that of three non-SFN cells served by three RF modules.
2.3 Architecture
SFN features are classified into two categories based on UE scheduling modes, as described in Table 2-1.
Table 2-1 SFN classification by scheduling mode
SFN Category Description Feature
SFN based on joint scheduling The eNodeB uses all RRUs to transmit data on downlink physical channels, and • TDLOFD-001075 SFN
uses some or all of the RRUs to receive data on uplink physical channels, • TDLOFD-001098 Inter-BBP SFN
regardless of whether a UE is located at the center of an RRU's coverage area or
the overlapping coverage area of RRUs. For details, see 3.1 Joint-Scheduling-
based SFN.
SFN based on adaptation The eNodeB adapts scheduling modes to UE attributes. The eNodeB uses only • TDLOFD-002008 Adaptive SFN/SDMA
between joint and independent the target RRU to process data for independent-scheduling UEs, and uses all of • TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA
scheduling the working RRUs to process data for joint-scheduling UEs. For details, see 3.2
Adaptive SFN/SDMA.
SFN features are classified into three categories based on the connections between the RRUs and BBPs, as described in Table 2-2.
Table 2-2 SFN classification by connections between RRUs and BBPs
Intra-BBP SFN features Intra-BBP SFN features enable RRUs • TDLOFD-001075 SFN
connected to the same BBP to serve the same • TDLOFD-002008 Adaptive SFN/SDMA
SFN cell. For details, see 4 Intra-BBP SFN
Features.
Inter-BBP SFN features Inter-BBP SFN features enable RRUs • TDLOFD-001098 Inter-BBP SFN
connected to different BBPs in the same BBU • TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA
to serve the same SFN cell. For details, see 5
Inter-BBP SFN Features.
Inter-BBU SFN features Inter-BBU SFN features enable RRUs • TDLOFD-001080 Inter-BBU SFN
connected to the BBPs in different BBUs to • TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA
serve the same SFN cell. For details, see 6
Inter-BBU SFN Features.
3 Feature Principles
3.1 Joint-Scheduling-based SFN

This section describes the principles of the following features:
Joint-scheduling-based SFN enables multiple RRUs to serve a single SFN cell. In this SFN cell, the RRUs use the same physical cell identifier (PCI). When joint-scheduling-based
SFN is enabled, multiple RRUs jointly transmit data in the downlink, and all RRUs, the target RRU, or the target RRU and coordinated RRUs receive data in the uplink. In this way,
signals from different cells that originally interfered with each other turn into multi-path signals from one cell. Joint-scheduling-based SFN decreases the number of neighboring cells,
mitigates co-channel interference between cells, and increases the SINR and improves user experience at the cell edge.
Figure 3-1 illustrates the difference between three common cells and a single combined SFN cell. In this example, the edges between cells 1, 2, and 3 become parts of the internal
coverage area of the SFN cell.
Figure 3-1 Comparison between common and SFN networking modes
In the downlink, the RRUs serving an SFN cell use the same time-frequency resources to transmit the same data. This eliminates the inter-RRU interference on the control channels
and the signal superimposition enhances signal quality.
In the uplink, all-RRU reception is used for the physical random access channel (PRACH) and sounding reference signals (SRSs). Either selective reception or joint reception is used
for the physical uplink shared channel (PUSCH). Only selective reception is used for the physical uplink control channel (PUCCH).
• All-RRU reception
All of the RRUs serving the SFN cell are used for data reception.
• Selective reception
Only the target RRU is used to receive PUSCH and PUCCH data. The eNodeB selects the RRU with the best measured channel quality as the target RRU.
TTI-level layer-2 (the MAC layer) selective reception was introduced starting in eRAN TDD 7.0. 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. The MAC layer selects and combines the correct demodulated data for reception. Layer-2
selective reception improves uplink coverage.
Layer-2 selective reception can only be used in SFN cells with a bandwidth of 10 or 20 MHz. This function is controlled by the SFNULL2SELECTIVERCVSWITCH option
of the CellAlgoSwitch.SfnAlgoSwitch parameter.
◾ When this option is selected, layer-2 selective reception is enabled and the eNodeB performs selective PUSCH data reception at the MAC layer in an SFN cell.
◾ When this option is deselected, layer-2 selective reception is disabled and the eNodeB receives PUSCH data only from the target RRU at the MAC layer in an
SFN cell.
• Joint reception
The eNodeB receives PUSCH data from both the target RRU and coordinated RRUs (other RRUs with sufficiently strong signals) and demodulates the data together.
Uplink joint reception is controlled by CellAlgoSwitch.SfnUplinkCompSwitch.
The eNodeB measures the strengths of SRSs reported by a UE and selects the RRUs whose measured SRS strength is less than that of the target RRU by a margin
within the range defined by the CellUlCompAlgo.SfnUlCompThd parameter as coordinated RRUs.
The eNodeB supports joint reception between RRUs with four or eight receivers. Either one or two RRUs can be selected as the coordinated RRUs for each UE.
The eNodeB may select an incorrect target RRU if uplink signals are measured inaccurately when a UE is moving in an SFN cell. To select target RRUs accurately, the
SfnTarRruSelEnhSwitch option has been added to the CellAlgoSwitch.SfnAlgoSwitch parameter.
◾ When this option is selected
RRUs calibrate received uplink signals based on the TA measurement results, ensuring that a more appropriate target RRU is selected. If the distance
between RRUs is short, the TA measurement results are more accurate. If the distance between RRUs is long, there is a higher possibility that the TA
measurement results are inaccurate.
◾ When this option is deselected
The eNodeB selects a target RRU based on the timing offset between received signals in the uplink. If the timing offset is small, the eNodeB can select a
correct target RRU. If the timing offset is large, the eNodeB may select an incorrect target RRU.
3.2 Adaptive SFN/SDMA

This section describes the principles of the following features:

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:
• Joint scheduling: Some or all of the RRUs in an SFN cell use the same time-frequency resources to transmit the same data to a UE and receive data from the same UE
for selective or joint demodulation and detection. This mode applies to UEs served by multiple RRUs.
• Independent scheduling: UEs served by different RRUs use the same time-frequency resources 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 used for an SFN cell, the RRUs serving the SFN cell use the same time-frequency resources to transmit or receive
different data.
3.2.2 UE Attribute Decision

This section describes the procedures for determining the working RRU list and the downlink and uplink attributes of a UE.
Downlink UE Attribute Decision
In the downlink, an eNodeB determines UE attributes by following the procedure shown in Figure 3-2.
Figure 3-2 Procedure for determining downlink UE attributes
The eNodeB determines downlink UE attributes as follows:
1. The eNodeB 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. The eNodeB arranges the RRUs in descending order of downlink equivalent RSRP values.
3. The eNodeB selects the RRU with the largest equivalent RSRP value as the target RRU of the UE.
4. The eNodeB creates a working RRU list based on the isolation degree.
a. The eNodeB sorts the RRUs into two groups, A and B. The RRU with the largest equivalent RSRP value is put into group A and the other RRUs into group
B. It then calculates the isolation degree between RRU groups A and B. The isolation degree equals the ratio of the total RSRP of RRU group A to the total
RSRP of RRU group B.
b. The eNodeB compares the isolation degree with a configured threshold. If the isolation degree is lower than the configured threshold, the eNodeB moves the
RRU with the largest equivalent RSRP in RRU group B to RRU group A and calculates the isolation degree again. The eNodeB repeats this process until the
isolation degree is greater than or equal to the specified threshold. When the isolation degree is greater than or equal to the specified threshold, the RRUs
contained in RRU group A form the working RRU list of the UE.
When adaptive SFN/SDMA is enabled, the SFN cell can use a fixed or adaptive isolation decision threshold. The adaptive threshold is adjusted based on
load status. The CellAlgoSwitch.SfnLoadBasedAdptSwitch parameter specifies whether a fixed or adaptive threshold is used in the SFN cell.
• When this parameter is set to OFF, the SFN cell uses a fixed isolation decision threshold.
• When this parameter is set to ON, the SFN cell uses an adaptive isolation decision threshold 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.
In eRAN8.1, load-based adaptive adjustment is optimized. The optimization is controlled by the SfnDl2LoadLevelAdptSwitch option of the
CellAlgoSwitch.SfnAlgoSwitch parameter. When the CellAlgoSwitch.SfnLoadBasedAdptSwitch parameter is set to ON:
• If the SfnDl2LoadLevelAdptSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter is deselected, load levels are not differentiated for
SFN cells in the downlink.
• If the SfnDl2LoadLevelAdptSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter is selected, 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 use a high decision threshold to make full use
of RRU resources, improving user experience. SFN cells in heavy load use 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. The eNodeB determines the UE attribute 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.
Uplink UE Attribute Decision
In the uplink, an eNodeB determines UE attributes by following the procedure shown in Figure 3-3.
Figure 3-3 Procedure for determining uplink UE attributes
The eNodeB determines uplink UE attributes as follows:
1. A measurement event triggers UE attribute determination. The eNodeB sorts the SINR and RSRP of signals from the UE to each RRU in descending order.
2. The eNodeB selects the RRU with the highest SINR as the target RRU.
3. The eNodeB calculates the uplink RSRP differences between other RRUs and the target RRU.
4. The eNodeB compares the RSRP difference between an RRU and the target RRU with the specified threshold. If the RSRP difference does not exceed the specified
threshold, the RRU belongs to the working RRU list of the UE.
When adaptive SFN/SDMA is enabled, the SFN cell can use a fixed or adaptive isolation decision threshold. The adaptive threshold is adjusted based on load status.
The CellAlgoSwitch.SfnLoadBasedAdptSwitch parameter specifies whether a fixed or adaptive threshold is used in the SFN cell.
• When this parameter is set to OFF, the SFN cell uses a fixed isolation decision threshold.
• When this parameter is set to ON, the SFN cell uses an adaptive isolation decision threshold. 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, the SFN cell uses a high isolation
decision threshold to make full use of RRU resources, improving user experience. When the network load is heavy, the SFN cell uses a low isolation decision
threshold to facilitate spatial multiplexing, improving spectral efficiency.
5. The eNodeB 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.
3.2.3 Adaptive Resource Scheduling

Based on the UE attribute, working RRU list, and target RRU of a UE, an eNodeB determines whether to perform joint or independent scheduling for the UE.
• Joint scheduling
Joint scheduling applies to UEs located in the areas served by multiple RRUs, such as UE 1 and UE 2 shown in Figure 3-4. In the downlink, some or all of the RRUs
transmit the same data to a UE by using the same time-frequency resources. This improves performance gains and prevents inter-RRU interference. In the uplink,
multiple RRUs use the same time-frequency resources to receive data for selective or joint demodulation and detection.
Figure 3-4 Joint scheduling
• Independent scheduling
In independent scheduling mode, only the target RRU of a UE allocates resources to the UE. Other RRUs in the SFN cell allocate those same time-frequency resources
to other UEs. Independently scheduled UEs use the same time-frequency resources as each other but transmit and receive different data. Independent scheduling is
appropriate for UEs located at the centers of the original common cells, such as UE 3, UE 4 and UE 5 shown in Figure 3-5. These UEs each use the same time-frequency
resources, but only receive data from or transmit data to their respective RRUs (RRU 1, RRU 2 and RRU 3). For example, in the downlink, UE 3 and UE 4 use the same
time-frequency resources to receive data from RRU 1 and RRU 2, respectively.
Figure 3-5 Independent scheduling
To enable adaptive SFN, the CellAlgoSwitch.SfnUlSchSwitch or CellAlgoSwitch.SfnDlSchSwitch parameter must be set to ADAPTIVE(Adaptive scheduling).
Downlink Adaptive Resource Scheduling
In the downlink, joint scheduling and independent scheduling are used adaptively, as shown in Figure 3-6.
Figure 3-6 Downlink adaptive resource scheduling
In Figure 3-6, the blocks in blue, red, and yellow represent different time-frequency resources. On the left, where joint scheduling is used, three RRUs allocate the same time-
frequency resources to the UE. On the right, where independent scheduling is used, only one RRU allocates time-frequency resources to a single UE and different RRUs allocate the
same time-frequency resources to different UEs.
In eRAN11.0, downlink adaptive resource scheduling is optimized. The optimization is controlled by the SfnDlSchAttriAdjsSwitch option of the CellAlgoSwitch.SfnAlgoSwitch
parameter. This option determines whether downlink scheduling attributes are adjusted. When the CellAlgoSwitch.SfnLoadBasedAdptSwitch parameter is set to ON and the
SfnDl2LoadLevelAdptSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter is selected, the SfnDlSchAttriAdjsSwitch option of the CellAlgoSwitch.SfnAlgoSwitch
parameter can be selected to enable the eNodeB to dynamically adjust scheduling attributes and resource allocation for UEs in an SFN cell at each TTI. The adjustment is based on
the cell load status and the distribution of UE attributes. This decreases scheduling delay for UEs.
Uplink Adaptive Resource Scheduling
In the uplink, joint scheduling and independent scheduling are used adaptively, as shown in Figure 3-7.
Figure 3-7 Uplink adaptive resource scheduling
In Figure 3-7, the blocks in blue, red, and yellow represent different time-frequency resources. On the left, where either selective or joint reception is used, the three RRUs allocate
the same time-frequency resources to a single UE. For selective reception, only one RRU receives data from the UE. With joint reception, multiple RRUs receive the same data from
the UE. On the right, where independent scheduling is enabled, the three UEs use the same time-frequency resources to transmit data, each to their respective 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.
3.3 PDCCH Enhancement in Adaptive SFN/SDMA
3.3.1 PDCCH DCS in Adaptive SFN/SDMA

This section describes the optional feature TDLOFD-070227 PDCCH DCS in SFN. DCS is short for dynamic cell selection.
In eRAN TDD 7.0, TDLOFD-070227 PDCCH DCS in SFN was introduced to mitigate interference on the PDCCH between SFN cells and to increase PDCCH SINR. This feature is
controlled by the SFNPDCCHDCSSWITCH option of the CellAlgoSwitch.SfnAlgoSwitch parameter.
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.
• PDCCH DCS in SFN not enabled

All the RRUs serving cell1 transmit PDCCH data to UE1 and all the RRUs serving cell2 transmit PDCCH data to UE2. Since UE1 is on the cell edges of both cells, it
receives PDCCH data from both cells and PDCCH data from cell2 causes interference to UE1.
• PDCCH DCS in SFN enabled
Only the working RRUs of the UE are allocated normal transmit power for PDCCH data. The other RRUs are not allocated transmit power. As 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. The eNodeB 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. The eNodeB sorts the RRUs in descending order of downlink equivalent RSRP values.
3. The eNodeB selects the RRU with the largest equivalent RSRP value as the target RRU of the UE.
4. The eNodeB creates a working RRU list based on the isolation degree.
a. The eNodeB sorts the RRUs into two groups, A and B. The RRU with the largest equivalent RSRP value is put into group A and the other RRUs into group
B. It then calculates the isolation degree between RRU groups A and B. The isolation degree equals the ratio of the total RSRP of RRU group A to the total
RSRP of RRU group B.
b. The eNodeB compares the isolation degree with a configured threshold. If the isolation degree is lower than the threshold specified by the
CellPdcchAlgo.SfnPdcchDcsThd parameter, the eNodeB moves the RRU with the largest equivalent RSRP in RRU group B to RRU group A, and
calculates the isolation degree again. The eNodeB repeats this process until the isolation degree is greater than or equal to the specified threshold. When
the isolation degree is greater than or equal to the specified threshold, the RRUs contained in RRU group A form the working RRU list of the UE.
If the CellPdcchAlgo.PDCCHAggLvlAdaptStrage parameter is set to STRATEGYBASEDONCOVERAGE, the eNodeB determines that all RRUs serving the SFN cell
are the working RRUs for PDCCH transmission for the following UEs: UEs providing HARQ feedback in multiplexing mode, UEs using PUCCH format 3, and UEs using
PUCCH format 1bcs. This ensures that PDCCH performance does not deteriorate for these UEs.
NOTE:
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.
3.3.2 PDCCH SDMA in Adaptive SFN/SDMA

This section describes the optional feature TDLOFD-081221 PDCCH SDMA in SFN.
In eRAN TDD 8.1, TDLOFD-081221 PDCCH SDMA in SFN was introduced to increase the PDCCH capacity of SFN cells. This feature is controlled by the
SFNPDCCHSDMASWITCH option of the CellAlgoSwitch.SfnAlgoSwitch parameter.
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 coverage area of RRU1 in cell1 and is far from other RRUs. UE2 is located in the coverage area of RRU2 in cell1 and is far
from other RRUs. UE3 is located in the coverage 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.
• PDCCH SDMA in SFN 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.
• PDCCH SDMA in SFN enabled
The eNodeB allocates PDCCH resources to a UE only at the working RRUs of the UE. PDCCH CCE resources of different RRUs in the SFN cell can be reused by UEs.
In the example illustrated in Figure 3-9, UE1 only receives the PDCCH signals transmitted by RRU1 in cell1 and UE2 only receives the PDCCH signals transmitted by
RRU2 in cell1. UE1 and UE2 can reuse the CCE resources of cell1. UE3 only receives the PDCCH signals transmitted by RRU4 in cell2 and UE4 only receives the
PDCCH signals transmitted by RRU5 and RRU6 in cell2. 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.
The creation of the working RRU list is a key part of the PDCCH SDMA in SFN feature. The process is the same as that used in the PDCCH DCS in SFN feature. For details, see
3.3.1 PDCCH DCS in Adaptive SFN/SDMA. The isolation decision threshold is specified by 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 the CellPdcchAlgo.PDCCHAggLvlAdaptStrage parameter is set to STRATEGYBASEDONCOVERAGE, the eNodeB determines that all RRUs serving the SFN cell
are the working RRUs for PDCCH transmission for the following UEs: UEs providing HARQ feedback in multiplexing mode, UEs using PUCCH format 3, and UEs using
PUCCH format 1bcs. This ensures that PDCCH performance does not deteriorate for these UEs.
3.4 Coordination Between Adaptive SFN/SDMA and Multiple-Antenna Techniques

To further increase cell throughput, adaptive SFN/SDMA can be used with coordinated beamforming (CBF), multi-user beamforming (MU-beamforming), and multi-user multiple-input
multiple-output (MU-MIMO).
3.4.1 Inter-RRU CBF in Adaptive SFN/SDMA

If inter-RRU CBF is enabled for an SFN cell, UEs with a low correlation under different RRUs are selected to pair through spatial multiplexing. Signals transmitted to the paired UEs
are weighted using CBF, mitigating inter-RRU interference on the UEs. Inter-RRU CBF in an SFN cell is controlled by the MuBfSwitch option of the
CellAlgoSwitch.MuBfAlgoSwitch parameter and the SfnCbfSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter.
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. It uses RRU 1 as its target RRU, but can also receive
strong signals from RRUs 0 and 2. UE 2 is covered only by RRU 2. Spatial multiplexing is used between UE 1 and UE 2. CBF directs strong signals to UE 2 and directs null signals
to UE 1 by adjusting weights. This mitigates the interference on UE 1 and generates only minimal signal loss for UE 2. As a result, the throughput of the SFN cell increases.
Figure 3-10 Inter-RRU CBF (1)
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 used between UE 1 and UE 2. CBF directs strong signals transmitted by RRU 2 to UE 2 and directs null signals to UE 1 by adjusting weights. In addition, CBF directs
strong signals transmitted by RRU 1 to UE 1 and directs null signals 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.
Figure 3-11 Inter-RRU CBF (2)
3.4.2 MU-Beamforming in Adaptive SFN/SDMA

MU-Beamforming is suitable for UEs with high channel correlations and considerable spatial diversities. In MU-Beamforming mode, multiple downlink data streams can be
transmitted using the same time and frequency resources, increasing cell throughput. When adaptive SFN/SDMA is enabled, independent UEs under each RRU can be paired for
MU-Beamforming. For details about the principles of MU-Beamforming, see Beamforming.
3.4.3 Adaptive SFN/SDMA+MU MIMO

In MU-MIMO mode, multiple UEs use the same time-frequency resources for data transmission in the uplink. MU-MIMO brings diversity and array gains as uplink receive diversity
does, and also brings multiplexing gains. System gains brought by MU-MIMO are subject to the SINRs of MIMO UEs and channel correlations between UEs. For details about the
principles of MU-MIMO, see MIMO.
When adaptive SFN/SDMA and MU-MIMO are used together, UE pairing policies differ between jointly scheduled UEs and independently scheduled UEs.
• A jointly scheduled UE (for example, UE A) can be paired with another jointly scheduled UE whose working RRUs are the same as UE A or are included in the working
RRU list of UE A, or with an independently scheduled UE whose working RRU is included in the working RRU list of UE A. To mitigate inter-stream interference between
paired UEs and enhance uplink system performance, the eNodeB preferentially selects a UE whose working RRU list does not include the target RRU of the UE involved
in first-layer pairing, for second-layer pairing. After UE pairing succeeds, the paired UEs receive data from their own target RRUs for demodulation.
• An independently scheduled UE must be paired with another independently scheduled UE served by the same target RRU.
4 Intra-BBP SFN Features

Intra-BBP SFN features consist of TDLOFD-001075 SFN and TDLOFD-002008 Adaptive SFN/SDMA. Intra-BBP SFN features enable the RRUs connected to the same LBBP to
serve an SFN cell, as shown in Figure 4-1.
Figure 4-1 Intra-BBP 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.
5 Inter-BBP SFN Features

In actual networking scenarios, to improve network coverage, multiple RRUs connected to different BBPs in the same BBU subrack are combined to serve one SFN cell. With
software configuration, inter-BBP SFN features allow RRUs connected to different BBPs 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-BBP SFN features include TDLOFD-001098 Inter-BBP SFN and TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA. Figure 5-1 shows an inter-BBP SFN cell.
Figure 5-1 Inter-BBP SFN cell
With inter-BBP SFN features, 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 PDCCH SINR and PDSCH SINR.
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.
6 Inter-BBU SFN Features

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. With proper software configuration, inter-BBU SFN techniques allow RRUs 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 for on-site O&M.
Inter-BBU SFN features include 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 a 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.
Figure 6-1 Inter-BBU SFN cell
With inter-BBU SFN features, up to 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 PDCCH SINR and PDSCH SINR.
NOTE:
BBU3910A does not support inter-BBU SFN.
Reliability
For inter-BBU SFN, the BBU that the SFN cell is set up on is known as the primary BBU or primary eNodeB. The other BBUs are known as auxiliary BBUs or auxiliary eNodeBs.
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 has been activated, details 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. Standby cells can be configured as either SFN cells or common
cells, but cannot be configured as inter-BBU SFN cells. After a standby cell is added, the RRUs connected to the secondary BBU start serving the standby cell for service
provisioning if any of the following faults persists for 4 minutes:
• Inter-BBU interconnection links are faulty.

• The clock accuracy error of the primary BBU is greater than 1.5 μs.
• The primary BBP is faulty.
• Transmission of the primary BBU is faulty.
• The main control board in the primary BBU is faulty.
• The SFN cell configured on the primary BBU has been deactivated.
• The clock precision deviation of a secondary BBU exceeds 1.5 μs.
• The data links between the primary BBU and the secondary BBU are not working properly.
After the fault is rectified, the standby cell is automatically deactivated and the SFN cell continues to provide services. If the data links between the primary BBU and the secondary
BBU are not working properly, run the RST SFNAUXRES command to restore services on the secondary cell.
NOTE:
• 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.
• 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.
• If the resources (including intra-BBP and inter-BBP routes) of a secondary BBU are abnormal, a standby cell cannot be set up on the secondary BBU.
• If the data links between the primary BBU and the secondary BBU are not working properly, the standby cell is activated only when the data links on all RRUs of the
secondary BBU are not working properly.
• A standby cell that has been successfully activated cannot be activated again within 10 minutes of an eNodeB upgrade or reset.
Introduction to the USU3900
The USU3900 allows baseband data to be transmitted between multiple BBUs so that different eNodeBs can share data. Table 6-1 describes the functions of the boards in the
USU3900.
Table 6-1 Board functions of the USU3900
Board Description Remarks
SMPT Implements O&M and resource management for other boards in the universal switching unit (USU). An SMPT must be configured in slot 6 or 7.
Slot 7 takes precedence over slot 6.
UCXU Transfers baseband data between USUs or between a USU and a BBU. A UCXU must be configured in one of the
following slots in descending order of priority:
Slot 3 > Slot 2 > Slot 1 > Slot 0
UCIU Transfers control and synchronization data between USUs or between a USU and a BBU. One UCIU must be configured in slot 5.
FAN Controls the fan speed, monitors the fan temperatures, reports the status of the fans, and dissipates heat The FAN is configured in slot 16.
from the USU.
UPEU Converts -48 V direct current (DC) into +12 V DC for a USU. If only one universal power and environment
interface unit (UPEU) is required, it must be
configured in slot 19.
For details about USU3900 hardware, see USU3900 Hardware Description.
Introduction to the USU3910
The USU3910 allows baseband data to be transmitted between multiple BBUs so that different eNodeBs can share data. The USU3910 can interconnect more BBUs than the
USU3900 can.
For details about USU3910 hardware, see USU3910 Hardware Description.
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 Multi-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 Multi-BBU Interconnection
Topology Scanning
In BBU interconnection scenarios, proper cabling between the USU and the BBUs, and between USUs, is critical. 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 scans the interconnection port topology of the USU, and the USU scans the interconnection port topology of each BBP. They then
check whether the obtained topology complies with interconnection rules. If there is any inconsistency, the BBU and the 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 the USU periodically scan the interconnection topologies and update topology data in real time. The DSP INTERCONTOPO
command can be executed to query the interconnection topologies on the eNodeBs and USUs. The command output contains the following information:
• Local Slot No.

• Local Port Type
• Local Port No.
• Peer ESN
• Peer Frame Type
• Peer Slot No.
• Peer Port Type
• Peer Port No.
• Local Sub Port No.
• Peer Level
• Peer Node ID
• Peer Sub Port No.
7 Application Restrictions
In inter-BBP and inter-BBU SFN scenarios, the primary baseband equipment needs to be bound to the SFN cell, the remaining primary BBP resources need to be queried, and the
primary BBP resources need to be queried and adjusted. This chapter describes the restrictions on these processes.
Binding with the Primary Baseband Equipment
When inter-BBP SFN is used, the primary baseband equipment is added differently in single- and multi-carrier scenarios.
• In single-carrier scenarios, the eNodeB automatically selects a BBP as the primary BBP in the cell activation process.
• In 10 MHz+20 MHz multi-carrier scenarios, the BBP in the sector equipment and the primary baseband equipment must be bound with the SFN cell by running the ADD
EUCELLSECTOREQM and ADD EUCELLPRIBBEQM commands, respectively. When the SFN cell is activated, the eNodeB automatically selects a BBP from the
primary BBP group as the primary BBP of the cell.
When the ADD EUCELLPRIBBEQM, MOD EUCELLPRIBBEQM, or MOD BASEBANDEQM command is executed and the primary baseband equipment differs from that to be
bound, the SFN cell will be reestablished. Exercise caution before running these commands.
NOTE:
• If the primary baseband equipment has been bound with an SFN cell, the primary BBP of the cell is selected from the bound primary baseband equipment. If the primary
baseband equipment is not bound with an SFN cell, only the BBP not bound with any SFN cell can be selected as the primary BBP of the SFN cell.
• If any of the cells configured on an eNodeB need to be bound with the primary baseband equipment, it is recommended that all the cells configured on the eNodeB be
bound with the primary baseband equipment. If the recommendation is not implemented, a large number of primary BBP resource fragments exist and some cells may not
be activated.
After the SFN cell is activated, information about the primary BBP can be queried by running the DSP CELL command.
Query of the Remaining Primary BBP Resources
Before expanding capacity, confirm that primary BBP resources are sufficient. If they are not, the expansion may fail. You can query information about the primary BBP resources by
running the DSP PRIBBPRESINFO command.
NOTE:
• Only the remaining primary BBP resources of 8T8R cells, 4T4R cells, 2T2R cells, SFN cells (a combination of 8T8R, 4T4R, 2T2R, 4T4R+8T8R, 4T4R+2T2R,
8T8R+2T2R, or 4T4R+8T8R+2T2R cells), and LampSite cells can be queried.
• The query results contain only the BBPs configured with at least one cell. For BBPs not configured with cells, capacity expansion must be performed based on BBP
processing capabilities.
Query and Adjustment of Primary BBP Resources
When an eNodeB allocates primary BBP resources, the allocation may fail. To minimize the number of SFN cells deactivated due to primary BBP resource allocation failures, primary
BBP resources need to be adjusted by running the DSP PRIBBPADJUST and STR PRIBBPADJUST commands after capacity expansion.
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.
Table 7-1 Restrictions on querying and adjusting primary BBP resources
Item Description
Application scenarios • Network capacity is expanded.

• Primary BBP resources fail to be allocated for the adjustment cell.
• Primary BBP resources of only 8T8R cells, 4T4R cells, 2T2R cells, SFN cells, and LampSite cells can be queried and adjusted.
• Primary BBP resources on the UBBPe board cannot be queried or adjusted.
Prerequisites • The CPU usage is lower than 50%. The query and adjustment will increase the CPU usage.
• Non-adjustment cells are all activated and all BBPs are available.
Requirements for the query and • Primary BBP resources can be adjusted only within the primary BBP group.
adjustment process • The DSP PRIBBPADJUST and STR PRIBBPADJUST commands cannot be run simultaneously. Otherwise, a message indicating
command execution failure is displayed.
• Configuration data cannot be added, modified, or deleted in the adjustment process. Otherwise, the STR PRIBBADUST command
execution process is aborted.
• 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

Prerequisite Features
None
Mutually Exclusive Features
Feature ID Feature Name Description
TDLBFD-00100301 5MHz Bandwidth The SFN feature does not work properly in macro cells with a bandwidth of 5
MHz.
TDLBFD-002010 Random Access Procedure

Two functions of this feature, contention-based access detection and non-
contention-based access optimization for UEs beyond the cell radius, are
incompatible with SFN.
TDLBFD-110103 Soft Split Resource Duplex None
TDLOFD-060201 Adaptive Inter-Cell Interference Coordination None
TDLOFD-001031 Extended CP None
TDLOFD-001039 RF Channel Intelligent Shutdown This feature and the SFN feature are mutually exclusive only on macro
eNodeBs.
TDLOFD-001007 High Speed Mobility If the BBP serving an SFN cell is LBBPc, the SFN cell does not support
TDLOFD-001007 High Speed Mobility.
TDLOFD-081217 Interference Detection and Suppression None
TDLOFD-111201 Remote Interference Adaptive Avoidance None
TDLOFD-120201 UL SU-MIMO None
TDLAOFD-080405 Out of Band Relay Introduction In this version, SFN does not work with the two features.
TDLAOFD-00100183 Relay Node Identification
TDLEOFD-121611 eMTC Introduction None
TDLEOFD-121601 Massive MIMO Introduction None
TDLOFD-130202 WTTx Turbo Beamforming (Trial) None
TDLOFD-121203 Inter-eNodeB Multi-Carrier Coordinated None

Scheduling
Impacted Features
Feature ID Feature/Function Name Description
TDLOFD-120202 Improved Uplink Coverage by Turbo Receiver This feature cannot be enabled when the ComCoverUlCompSwitch option of
the CellAlgoSwitch.SfnUplinkCompSwitch parameter is selected.
TDLOFD-001049 Single Streaming Beamforming If this feature is enabled and there are joint-scheduling UEs in an SFN cell, the
phases of the received signals at the UEs are random. This compromises the
gains brought by this feature, but system gains are still increased.
N/A DL CoMP When DL CoMP is enabled, SFN cells cannot be added to a DL CoMP cluster.
N/A Scheduling None

TDLOFD-001075 SFN None
TDLBFD-00202201 Downlink Static Inter-Cell Interference Coordination None
TDLBFD-00202202 Uplink Static Inter-Cell Interference Coordination None
Impacted Features
TDLBFD-00300201 DiffServ QoS Support In inter-BBP and inter-BBU adaptive SFN/SDMA scenarios, when the cell load is
relatively heavy, there will be a large number of independent- and joint-
TDLBFD-001015 Enhanced Scheduling scheduling UEs. If both GBR and non-GBR services are running and unevenly
distributed, the QoS of GBR services is affected by hybrid scheduling.
TDLOFD-001029 Enhanced Admission Control
TDLOFD-00102901 Radio/transport resource pre-emption
N/A Scheduling Since cell-specific reference signals (CRSs) are jointly transmitted by all RRUs
in an SFN cell, the subband channel quality indicated by the obtained subband
CQI deviates from that in the actual scheduling for some joint-scheduling UEs or
independent-scheduling UEs, which affects the frequency selective scheduling
feature.

None
Impacted Features
TDLBFD-00100701 uplink-downlink subframe configuration type1&2 Type 1 is not supported.

TDLOFD-002008 Adaptive SFN/SDMA None
TDLOFD-001098 Inter-BBP SFN None
None
Impacted Features
None

TDLOFD-001040 Low Power Consumption Mode None
TDLOFD-001042 Intelligent Power-Off of Carriers in the Same Coverage None
Impacted Features
TDLBFD-00300201 DiffServ QoS Support None
TDLBFD-001015 Enhanced Scheduling
TDLOFD-001029 Enhanced Admission Control
TDLOFD-00102901 Radio/transport resource pre-emption

TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA None
TDLOFD-001080 Inter-BBU SFN None
None
Impacted Features
None

TDLOFD-081221 PDCCH SDMA in SFN None
Impacted Features
None

TDLOFD-070227 PDCCH DCS in SFN (TDD) None
Impacted Features
None
9 Network Impact

System Capacity
• 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%.
• The average throughput for a single UE increases by about 53% in the downlink and by about 59% at the cell edge in the downlink when three RRUs serve an SFN cell in
a typical dense urban area and the load ratio is 100%.
• In typical indoor coverage scenarios, SFN networking increases the average cell throughput when compared with single-RRU or multi-RRU networking.
Network Performance
• The number of handovers decreases and the handover success rate increases, and therefore the service drop rate decreases.
• Large-scale SFN deployment improves the SINR of the entire network.
◾ The average PDCCH SINR and PDSCH SINR increase by 2 dB to 3 dB when three RRUs serve an SFN cell in a typical dense urban area.
◾ The average PDCCH SINR and PDSCH SINR increase by 5 dB to 6 dB when seven RRUs serve an SFN cell in a typical dense urban area.
◾ In typical indoor coverage scenarios, the average PDCCH SINR and PDSCH SINR increase obviously.

System Capacity
• The average cell throughput decreases to about 85% to 95% in the downlink when three RRUs serve an SFN cell in a typical dense urban area and the load ratio is
100%.
• The average throughput of a single UE at the cell edge increases by about 39% in the downlink when three RRUs serve an SFN cell in a typical dense urban area and the
load ratio is 100%.
Network Performance

System Capacity
Network Performance

System Capacity
load ratio is 100%.
Network Performance

System Capacity
Network Performance

System Capacity
load ratio is 100%.
Network Performance

System Capacity
When three RRUs serve an SFN cell in a typical dense urban area and the PDCCH load ratio is 100%, PDCCH DCS in SFN increases the user capacity of the PDCCH by about 9%.
The user capacity of the PDCCH refers to the average number of UEs that can be allocated CCE resources when UEs are evenly distributed.
Network Performance
PDCCH DCS in SFN increases the PDCCH SINR by about 0.5 dB when three RRUs serve an SFN cell in a typical dense urban area and the PDCCH load ratio is 100%.

System Capacity
When three RRUs serve an SFN cell in a typical dense urban area and the PDCCH load ratio is 100%, PDCCH SDMA in SFN increases the user capacity of the PDCCH by about
24%. The user capacity of the PDCCH refers to the average number of UEs that can be allocated CCE resources when UEs are evenly distributed.
Network Performance
No impact.
10 Engineering Guidelines
10.1 When to Use

SFN Techniques
Table 10-1 describes which SFN features are required for different kinds of SFN techniques.
Table 10-1 SFN techniques
SFN Technique SFN Feature
Intra-BBP SFN techniques • TDLOFD-001075 SFN

Inter-BBP SFN techniques • TDLOFD-001075 SFN

SFN Technique SFN Feature

Inter-BBU SFN techniques • TDLOFD-001075 SFN

• Adaptive SFN/SDMA is recommended when traffic in the SFN cell is heavy.

• Adaptive SFN/SDMA is not recommended for high-speed scenarios, where UE attributes change frequently.
• It is recommended that the PDCCH SDMA in SFN feature be activated when the PDCCH load is heavy, a large number of UEs are scheduled in each TTI, and the
Adaptive SFN/SDMA feature has been activated. If the PDCCH DCS in SFN feature has been activated, deactivate this feature before you activate the PDCCH SDMA in
SFN feature.
• It is recommended that the PDCCH DCS in SFN feature be activated when the PDCCH load is heavy, PDCCH interference between SFN cells is severe, and the
Adaptive SFN/SDMA feature has been activated. If the PDCCH SDMA in SFN feature has been activated, deactivate this feature before you activate the PDCCH DCS in
SFN feature.
Differences in System Configurations
Compared with non-SFN networking, intra- and inter-BBP SFN techniques have the following additional requirements:
• Multiple sectors and multiple pieces of sector equipment must be configured, because each RRU requires one sector and one piece of sector equipment.
• When an SFN cell is added by running the ADD CELL command, the cell.MultiRruCellFlag parameter must be set to BOOLEAN_TRUE(True) and the
cell.MultiRruCellMode parameter to SFN(SFN).
• The SFN cell must be associated with multiple pieces of sector equipment.
• After the SFN cell is configured, the following parameters must be set based on the network plan:
◾ SFN uplink scheduling switch (CELLALGOSWITCH.SfnUlSchSwitch)
◾ SFN downlink scheduling switch (CELLALGOSWITCH.SfnDlSchSwitch)
◾ SFN load-based adaptive algorithm switch (CELLALGOSWITCH.SFNLOADBASEDADPTSWITCH)
◾ SFN algorithm switch (CELLALGOSWITCH.SfnAlgoSwitch)
◾ SFN PDCCH DCS threshold (CellPdcchAlgo.SfnPdcchDcsThd)
◾ SFN PDCCH SDMA threshold (CellPdcchAlgo.SfnPdcchSdmaThd)
◾ Downlink load measurement period of SFN cell (CellDlschAlgo.SfnDlLoadPeriod)
◾ SFN downlink high load threshold (CellDlschAlgo.SfnDlHighLoadThd)
◾ SFN downlink low load threshold (CellDlschAlgo.SfnDlLowLoadThd)
◾ Isolation decision threshold offset of downlink heavy-load level (CellDlschAlgo.DlHighLoadSdmaThdOffset)
◾ Uplink load measurement period of SFN cell (CellUlschAlgo.SfnUlLoadPeriod)
◾ UL CoMP switch in SFN cell (CellAlgoSwitch.SfnUplinkCompSwitch)
◾ Switch for the number of combined antennas supporting uplink joint reception (CellAlgoSwitch.UlJRAntNumCombSw)
◾ UL CoMP admission threshold in SFN cell(CellUlCompAlgo.SfnUlCompThd)
◾ Algorithm switch based on BBU coordination (ENodeBAlgoSwitch.OverBBUsSwitch)
Compared with intra- and inter-BBP SFN techniques, inter-BBU SFN techniques have the following additional requirements:
• Interconnection parameters must be set for all the interconnected USUs and BBUs.
• SFN-related parameters must be set on the primary and auxiliary eNodeBs, as described in Table 10-2.
Table 10-2 SFN configurations on the primary and auxiliary eNodeBs
MO Configuration on the Primary eNodeB Configuration on the Auxiliary eNodeB
SECTOR Sectors and sector equipment must be configured for all the RRUs Sectors and sector equipment must be configured for
connected to the primary eNodeB. all the RRUs connected to the auxiliary eNodeB.
CELL When an SFN cell is added by running the ADD CELL command, It is recommended that a standby cell be added to the
the Cell.EuCellStandbyMode parameter must be set to ACTIVE auxiliary eNodeB by running the ADD CELL
(Active). The SFN cell must be manually activated on the primary command with the CELL.EuCellStandbyMode
eNodeB. parameter set to STANDBY(Standby). The standby
cell does not need to be manually activated.
EUCELLSECTOREQM The SFN cell must be associated with multiple pieces of sector If a standby cell is configured, the standby cell must
equipment configured on the primary eNodeB. be associated with multiple pieces of sector
equipment configured on the auxiliary eNodeB.
CELLOP Operator information must be configured. When a standby cell is configured, operator
information must be configured.
SFNCELLBIND The binding relationships between SFN cells and auxiliary eNodeBs N/A
must be configured.
CellAlgoSwitch The following parameters must be set based on the network plan: • When an SFN cell is functioning as a
• SFN uplink scheduling switch standby cell, it is recommended that the
(CELLALGOSWITCH.SfnUlSchSwitch) standby SFN cell have the same switch
settings as the SFN cell configured on the
• SFN downlink scheduling switch
primary eNodeB.
(CELLALGOSWITCH.SfnDlSchSwitch)
• Do not set these parameters when a
• SFN load-based adaptive algorithm switch
common cell is functioning as the standby
(CELLALGOSWITCH.SFNLOADBASEDADPTSWITCH)
cell.
MO Configuration on the Primary eNodeB Configuration on the Auxiliary eNodeB

• SFN algorithm switch
(CELLALGOSWITCH.SfnAlgoSwitch)
• UL CoMP switch in SFN cell
(CellAlgoSwitch.SfnUplinkCompSwitch)
• Switch for the number of combined antennas
supporting uplink joint reception
(CellAlgoSwitch.UlJRAntNumCombSw)
ENodeBAlgoSwitch If SFN uplink joint reception based on BBU coordination needs to be N/A
enabled, ENodeBAlgoSwitch.OverBBUsSwitch must be set.
CELLPDCCHALGO The CellPdcchAlgo.SfnPdcchDcsThd parameter must be set. • When an SFN cell is functioning as a
The CellPdcchAlgo.SfnPdcchSdmaThd parameter must be set. standby cell, the parameters
CellPdcchAlgo.SfnPdcchDcsThd and
CellPdcchAlgo.SfnPdcchSdmaThd
must be set to the same values for the
standby cell as it is set for the SFN cell
configured on the primary eNodeB.
• Do not set these parameters when a
cell.
CellDlschAlgo The following parameters must be set based on the network plan: N/A
• Downlink load measurement period
(CellDlschAlgo.SfnDlLoadPeriod)
• SFN downlink high load threshold
(CellDlschAlgo.SfnDlHighLoadThd)
• SFN downlink low load threshold
(CellDlschAlgo.SfnDlLowLoadThd)
• Isolation decision threshold offset of downlink heavy-load
level (CellDlschAlgo.DlHighLoadSdmaThdOffset)
CellUlschAlgo The following parameters must be set based on the network plan: N/A
Uplink load measurement period of SFN cell
(CellUlschAlgo.SfnUlLoadPeriod)
CellUlCompAlgo Configure the admission threshold of UL CoMP in SFN cells • When an SFN cell is functioning as a
(CellUlCompAlgo.SfnUlCompThd) as planned. standby cell, the
CellUlCompAlgo.SfnUlCompThd
parameter must be set to the same value
for the standby cell as it is set for the SFN
cell configured on the primary eNodeB.
• Do not set this parameter when a
cell.
SfnAuxResBind N/A The SFN cell configured on the primary eNodeB must
be associated with multiple pieces of sector
equipment configured on the auxiliary eNodeB.
10.2 Required Information
10.2.1 Traffic Requirements and Distribution of Interference Areas

• Collect the SINR distribution from the live network to determine whether to enable SFN.
• Collect traffic requirements to determine whether to enable adaptive SFN/SDMA.
10.2.2 Interference eNodeB and LBBP Configurations

• Collect information about the eNodeBs and BBPs that serve the cells in the interference area. If the cells subject to interference are served by the same BBP, the SFN or
adaptive SFN/SDMA feature is recommended. If these cells are served by different BBPs in the same BBU on an eNodeB, the inter-BBP SFN or inter-BBP adaptive
SFN/SDMA feature is recommended.
• Collect information such as space and power available at sites that need to deploy inter-BBU SFN or inter-BBU adaptive SFN/SDMA. Based on the collected information,
determine the number of BBUs that can be installed in the same equipment room, the configuration principles of the BBPs in these BBUs, and the number of RRUs to be
combined to form an SFN cell.
10.3 Planning
RF Planning
Deploying SFN in indoor and outdoor coverage scenarios requires a cell bandwidth of 10 or 20 MHz.
Network Planning
The network planning for the SFN networking mode is the same as that for the common networking mode.
Planning for the Primary eNodeB in Inter-BBU SFN Scenarios
To plan the primary eNodeB of an inter-BBU SFN cell, perform the following steps:
1. Count how many RRUs are serving each SFN cell, and sort them from those with the most RRUs to those with the least. Then identify the primary eNodeB of each SFN
cell on the list, starting with the one with the most RRUs and working towards the one with the least.
2. Select the eNodeB that provides the most RRUs serving an SFN cell as a candidate primary eNodeB of the SFN cell.
3. Check whether the eNodeB meets all the following conditions:
• The number of cells configured on the eNodeB has not reached the maximum allowed.
• The number of physical cells configured on the eNodeB has not reached the maximum allowed.
• The number of SFN cells each served by four or more RRUs on the eNodeB ≤ (Number of LBBPd boards + Number of UBBP boards x 2)
• Layer 2 resources meet the BBP specification requirements described in the following table.
Table 10-3 BBP specifications (Layer-2 logical cell configuration)
BBP Model Specifications
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 each served by one RRU
◾ One cell served by two RRUs + one cell served by one RRU
LBBPd When the cell bandwidth is 10 or 20 MHz:

◾ Three cells each served by one or two RRUs
◾ One cell served by four RRUs + one cell served by one or two RRUs
◾ One cell served by three RRUs + one cell served by one to three RRUs
◾ One cell served by five to seven RRUs
UBBPd4 and UMDUa1 When the cell bandwidth is 10 or 20 MHz:

◾ Three cells each served by one or two RRUs
◾ One cell served by four RRUs + one cell served by one or two RRUs
◾ One cell served by three RRUs + one cell served by one to three RRUs
◾ One cell served by five to seven RRUs
UBBPd6, UBBPd9, When the cell bandwidth is 10 or 20 MHz, any combination of cell configurations is supported if there are no more than 6 cells
UBBPe4, and UMDUa3 and no more than 9 RRUs.
UBBPei When the cell bandwidth is 10 or 20 MHz, any combination of cell configurations is supported if there are no more than 12 cells
and no more than 15 RRUs.
• The total number of out-of-eNodeB and into-eNodeB physical cells does not exceed 14 times the number of optical cables connecting the eNodeB and USUs.
NOTE:
◾ The number of optical cables connecting the eNodeB and USUs cannot exceed 4 or the total number of LBBPd and UBBP boards installed in slots
0, 1, 2, and 3 on the eNodeB, whichever is less.
◾ An into-eNodeB physical cell for an eNodeB (for example, eNodeB 0) is a physical cell that serves an SFN cell whose primary eNodeB is eNodeB
0 and resides on an eNodeB different from 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.
In Figure 10-1, there are two into-eNodeB physical cells and two out-of-eNodeB physical cells for eNodeB 0, and there are two into-eNodeB physical cells and
one out-of-eNodeB physical cell for eNodeB 1.
Figure 10-1 Inter-BBU SFN cell
If one or more eNodeBs meet all of the preceding conditions, go to 4. If no eNodeB meets all of the preceding conditions, go to 5.
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 is the total number of RRUs serving all of the SFN cells configured on the eNodeB, including RRUs connected to
different BBUs.
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 3 until the primary
eNodeB is selected.
6. Repeat 1 to 5 to select the primary eNodeBs for all the SFN cells.
Hardware Planning for Outdoor Coverage
2T2R, 4T4R, or 8T8R RRUs must be used in outdoor coverage scenarios.

Intra-BBP, inter-BBP, and inter-BBU SFN cells are supported in outdoor coverage scenarios. An SFN cell can be served by a maximum of seven RRUs.
BBP capabilities must be considered before deploying an intra-BBP, inter-BBP, or inter-BBU SFN cell. Table 10-4 and Table 10-5 describe BBP processing capabilities.
Table 10-4 BBP processing capabilities (L1 physical cell configuration, 4T4R/2T2R)
BBP Model Supported Sector Equipment Quantity (RRU, 10 MHz) Supported Sector Equipment Quantity (RRU, 20 MHz)
LBBPc 3 1
LBBPd 3 3
UBBPd4 and UMDUa1 3 3
UBBPd6, UBBPd9, UBBPe4, 6 6

and UMDUa3
UBBPei 12 12
Table 10-5 Baseband processing capabilities (L1 physical cell configuration, 8T8R)
BBP Model Supported Sector Equipment Quantity (RRU, 10 MHz) Supported Sector Equipment Quantity (RRU, 20 MHz)
LBBPc Unsupported Unsupported
LBBPd 2 1
UBBPd6 3 3
UBBPd9 and UBBPe4 3 3
UBBPei 6 6
The restrictions on hardware planning for outdoor coverage are as follows:
• Each BBU can house a maximum of six BBPs.

• When the cell bandwidth is 20 MHz for a cell established on an LBBPc, intra-BBP SFN techniques are not supported, because only one RRU can be connected to a
single LBBPc.
• 8T8R RRUs, 4T4R RRUs, and 2T2R RRUs cannot be connected to the same BBP. They must be connected to different BBPs.
• The LBBPc does not support configuration of 2T2R SFN cells.
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:
• In addition to the LBBPc, other BBP models must be configured in the BBU.
• 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.
• 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.
Hardware Planning for Indoor Coverage
2T2R pRRUs must be used for indoor coverage.

A maximum of eight pRRUs can serve a pRRU-aggregation cell.
In indoor coverage scenarios, an SFN cell can be served by:
• A maximum of seven pRRUs

• A maximum of seven pRRU-aggregation cells
• pRRUs + pRRU-aggregation cells: The total number of pRRUs and pRRU-aggregation cells must range from 2 to 7.
Table 10-6 lists the processing capabilities of BBPs.
Table 10-6 Processing capabilities of BBPs (L1 physical cell configuration, 2T2R)
BBP Model Supported Number of Sector Equipment Groups (pRRU)
LBBPc 3
LBBPd 3
UBBPd6 6
UBBPd9 and UBBPe4 6
NOTE:
• Each BBU can house a maximum of six BBPs.

• In indoor coverage scenarios, inter-BBU SFN is not supported.
10.4 Deployment of Intra- and Inter-BBP SFN Techniques

This section describes the procedures for deploying the following SFN features:

10.4.1 Requirements
Operating Environment
• In outdoor coverage scenarios, if the baseband processing board is LBBPc or LBBPd, the BBP.WM parameter must be set to TDD_ENHANCE.
When the BBP.WM parameter is set to TDD_ENHANCE for LBBPc, LBBPc+LBBPc convergence is not supported. In LBBPc+LBBPd convergence scenarios, the
convergence must be from LBBPc to LBBPd.
• In indoor coverage scenarios, if the baseband processing board is LBBPc or LBBPd, the BBP.WM parameter must be set to TDD.
• SFN and adaptive SFN/SDMA support subframe configurations 1 and 2 and special subframe configuration 7.
• Inter-BBP SFN and inter-BBP adaptive SFN/SDMA support only subframe configuration 2 and special subframe configuration 7.
• The Topo Type parameter in the RRUCHAIN MO must be set to CHAIN(CHAIN) or RING(RING).
NOTE:
LBBPc boards do not support CBF.
It is recommended that CBF be enabled when the UBBP serves as the primary BBP.
SFN supporting 2T2R cells does not support CBF.
Hardware
For details about hardware, see hardware planning in 10.3 Planning.
License
The operator must purchase and activate the license for the feature listed in the following table to activate intra-BBP SFN.
Feature ID Feature Name Model License Control Item NE Sales Unit
TDLOFD-001075 SFN LT1ST00SFN00 SFN (per Cell) (TDD) eNodeB Per Cell
The operator must purchase and activate the licenses for the features listed in the following table to activate intra-BBP adaptive SFN/SDMA.
TDLOFD-002008 Adaptive SFN/SDMA LT1SADASFN00 Adaptive SFN/SDMA (per Cell) (TDD) eNodeB Per Cell
The operator must purchase and activate the licenses for the features listed in the following table to activate inter-BBP SFN.
TDLOFD-001098 Inter-BBP SFN LT1SBBPSFN00 Inter-BBP SFN (TDD) eNodeB Per eNodeB
The operator must purchase and activate the licenses for the features listed in the following table to activate inter-BBP adaptive SFN/SDMA.
TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA LT1SBBPADA00 Inter-BBP Adaptive SFN/SDMA (TDD) eNodeB Per eNodeB
The operator must purchase and activate the licenses for the features listed in the following table to activate PDCCH DCS in SFN.
TDLOFD-070227 PDCCH DCS in SFN LT1SPDCSIS00 PDCCH DCS in SFN (TDD) eNodeB Per Cell
The operator must purchase and activate the licenses for the features listed in the following table to activate PDCCH SDMA in SFN.
TDLOFD-081221 PDCCH SDMA in SFN LT1SPSISFN00 PDCCH SDMA in SFN cells (each cell) eNodeB Per Cell
(TDD)
NOTE:
• When SFN and Adaptive SFN/SDMA are enabled, the numbers of feature license units and capacity license units required for an SFN cell are 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 served by three RRUs 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.
• 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
above.
• 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
• To ensure optimal resource usage, the activation of an SFN cell may deactivate and reactivate some cells served by the eNodeB.
• When an SFN cell is served by RRUs connected to both LBBPc and LBBPd or to both LBBPc and UBBP 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.
• BBPs can be combined in LBBPc-only, LBBPd-only, UBBP-only, LBBPc+LBBPd, or LBBPd+UBBP 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
BBP Combination Mode Before BBP Combination Mode After Switching Whether the SFN Cell Needs to Be Re-established
Switching
LBBPc only LBBPc only No
LBBPc only LBBPd only, UBBP only, or LBBPd+UBBP Yes (The cell is re-established immediately.)
LBBPc only LBBPc+LBBPd Yes (The cell is re-established immediately.)
LBBPd only, UBBP only, or LBBPc only Yes (The cell is re-established immediately.)
LBBPd+UBBP
LBBPd only, UBBP only, or LBBPd only, UBBP only, or LBBPd+UBBP No

LBBPd+UBBP
Switching
LBBPd only, UBBP only, or LBBPc+LBBPd Yes (The cell is re-established immediately.)
LBBPd+UBBP
LBBPc+LBBPd LBBPc only Yes (The cell is re-established in the wee hours when there are no users on
the network.)
LBBPc+LBBPd LBBPd only, UBBP only, or LBBPd+UBBP Yes (The cell is re-established in the wee hours when there are no users on
the network.)
LBBPc+LBBPd LBBPc+LBBPd No
• If the BBU configured with an SFN cell houses the LBBPc and LBBPd or UBBP, layer 1 must be bound to a BBP by running the ADD EUCELLSECTOREQM command
before the SFN cell is activated.
• A cell with a bandwidth of 20 MHz and a cell with a bandwidth of 10 MHz must be deployed on different BBPs when they are deployed in the same BBU. The deployment
requirements are as follows:
◾ The carrier with a bandwidth of 20 MHz is preferentially configured on the LBBPd or UBBP, and the carrier with a bandwidth of 10 MHz is preferentially
configured on the LBBPc.
◾ If the BBU configured with an SFN cell houses the LBBPc and LBBPd or UBBP, 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.
• The slots for installing the LBBPd and UBBP in descending order of priority are as follows: slot 3, slot 2, slot 0, slot 1, slot 4, and slot 5. The slots for installing the LBBPc
in descending order of priority are as follows: slot 5, slot 4, slot 1, slot 0, slot 2, and slot 3. The UBBP, LBBPd, and LBBPc must be installed in sequence when all of them
are required.
• 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.
• 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
possible between a BBP installed in slot 0 or 1 and another BBP installed in slot 4 or 5. This restriction applies only to BBU3900 and BBU5900.

None

Required Data
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.
Parameter Name Parameter ID Data Source Setting Notes
Sector ID SECTORID Network plan (negotiat)on not required) The sector number must be unique on the eNodeB.
Sector Name SECNAME Network plan (negotiation not required) None
Location Name LOCATIONNAME Equipment planning None
User Label USERLABEL Network plan (negotiation not required) Set this parameter based on customer requirements.
Antenna Number ANTNUM Network plan (negotiation not required) In outdoor coverage scenarios, set this parameter to 2,
4, or 8.
In indoor coverage scenarios, set this parameter to 2.
Cabinet No. of Antenna 1 ANT1CN Equipment planning Set this parameter to 0.
Subrack No. of Antenna 1 ANT1SRN Equipment planning Set this parameter to the subrack number of the RRU
connected to antenna 1.
Slot No. of Antenna 1 ANT1SRN Equipment planning Set this parameter to 0.
Channel No. of Antenna 1 ANT1N Equipment planning Set this parameter to R0A.
Slot No. of Antenna 2 ANT2SN Equipment planning Set this parameter to 0.
Channel No. of Antenna 2 ANT2N Equipment planning Set this parameter to R0B.
Channel No. of Antenna 3 ANT3N Equipment planning Set this parameter to R0C.
Channel No. of Antenna 4 ANT4N Equipment planning Set this parameter to R0D.
Slot No. of Antenna 5 ANT5SRN Equipment planning Set this parameter to 0.
Channel No. of Antenna 5 ANT5N Equipment planning Set this parameter to R0E.
Channel No. of Antenna 6 ANT6N Equipment planning Set this parameter to R0F.
Subrack No. of Antenna7 ANT7SRN Equipment planning Set this parameter to the subrack number of the RRU
Channel No. of Antenna7 ANT7N Equipment planning Set this parameter to R0G.
Channel No. of Antenna 8 ANT8N Equipment planning Set this parameter to R0H.
Create Default Sector sector.CREATESECTOREQM Network plan (negotiation not required) If the sector.CREATESECTOREQM parameter is set
Equipment to TRUE(TRUE), the default sector equipment is
added. The default sector equipment contains all
existing antennas specified in the ADD SECTOR
command. Each antenna can be used for transmitting
and receiving data. The transmit antennas work in
master mode.
If the sector.CREATESECTOREQM parameter is set
to FALSE(FALSE), run the ADD SECTOREQM
command to add sector equipment.
Default Sector Equipment ID sector.SECTOREQMID Network plan (negotiation not required) User-defined. This parameter is valid only when the
sector.CREATESECTOREQM parameter is set to
TRUE(TRUE).
The following table describes the parameters that must be set in the Cell MO to configure SFN cells.
Frequency band Cell.FreqBand Radio planning (internal planning) Set this parameter based on the network plan.
Uplink EARFCN indication Cell.UlEarfcnCfgInd Default/Recommended value Set this parameter to NOT_CFG(Not configure).
Downlink EARFCN Cell.DlEarfcn Radio planning (internal planning) Set this parameter based on the network plan.
Uplink bandwidth Cell.UlBandWidth Radio planning (internal planning) This parameter specifies the uplink cell bandwidth. Set
this parameter based on the network plan.
Downlink bandwidth Cell.DlBandWidth Radio planning (internal planning) This parameter specifies the downlink cell bandwidth.
Set this parameter based on the network plan.
Cell ID Cell.CellId Radio planning (internal planning) This parameter specifies the ID of an E-UTRAN cell.
Set this parameter based on the network plan.
Physical cell ID Cell.PhyCellId Radio planning (internal planning) This parameter specifies the PCI of a cell. Its value
ranges from 0 to 503. Set this parameter based on the
network plan.
Cell FDD TDD indication Cell.FddTddInd Radio planning (internal planning) Set this parameter to CELL_TDD(TDD).
Subframe assignment Cell.SubframeAssignment Radio planning (internal planning) This parameter specifies the uplink-downlink subframe
configuration of an E-UTRAN TDD cell. For details
about uplink-downlink subframe configurations, see
3GPP TS 36.211.
Special subframe patterns Cell.SpecialSubframePatterns Radio planning (internal planning) This parameter specifies the special subframe
configuration of an E-UTRAN TDD cell. For details
about special subframe configurations, see 3GPP TS
36.211.
Cell Standby Mode Cell.EuCellStandbyMode Radio planning (internal planning) This parameter specifies whether a cell works in active
or standby mode. For an inter-BBU SFN cell, set this
parameter to ACTIVE(Active) for the SFN cell
configured on the primary eNodeB and to STANDBY
(Standby) for the standby cell configured on a
secondary eNodeB. For a non-inter-BBU SFN cell, set
this parameter to ACTIVE(Active).
Root sequence index Cell.RootSequenceIdx Radio planning (internal planning) For details about setting restrictions, see the MO and
parameter references of eNodeBs.
Flag of Multi-RRU Cell Cell.MultiRruCellFlag Radio planning (internal planning) For SFN cells and pRRU aggregated cells, set this
parameter to BOOLEAN_TRUE(True). For common

cells, set this parameter to BOOLEAN_FALSE
(False).
Mode of Multi-RRU Cell Cell.MultiRruCellMode Radio planning (internal planning) For SFN cells, set this parameter to SFN(SFN). For
pRRU aggregated cells, set this parameter to
MPRU_AGGREGATION(MPRU_AGGREGATION).
For common cells, this parameter is invalid.
Physical Cell Number of SFN Cell.SectorEqmNum Radio planning (internal planning) This parameter specifies the total amount of sector
Cell equipment configured for an SFN cell.
Cell transmission and reception Cell.TxRxMode Radio planning (internal planning) In outdoor coverage scenarios, set this parameter as
mode follows:
• 4T4R: only for SFN cells combined by
4T4R or 4T4R+2T2R cells
8T8R, 8T8R+4T4R, 8T8R+2T2R, or
8T8R+4T4R+2T2R cells
2T2R cells
In indoor coverage scenarios, set this parameter to
2T2R.
The following table describes the parameters that must be set in the BASEBANDEQM MO to configure baseband equipment for SFN cells.
Baseband equipment must be added and the binding relationships between cells and BBPs must be configured when the SFN cell is set up in a LampSite scenario or is configured
with one 10 MHz carrier and one 20 MHz carrier.
Baseband Equipment ID BASEBANDEQM.BASEBANDEQMID Network plan (negotiation not required) Set this parameter based on the network plan.
Baseband Equipment Type BASEBANDEQM.BASEBANDEQMTYPE Network plan (negotiation not required) Set this parameter based on the network plan.
UMTS UL Demodulation Mode BASEBANDEQM.UMTSDEMMODE Network plan (negotiation not required) Set this parameter to NULL(NULL).
Cabinet No. of Process Unit x CNx Equipment planning Set this parameter to 0.
Subrack No. of Process Unit x SRNx Equipment planning Set this parameter to 0.
Slot No. of Process Unit x SNx Equipment planning Set this parameter to the number of the slot in which
the BBP is installed.
The following table describes the parameters that must be set in the EUCELLSECTOREQM MO to configure sector equipment for SFN cells.
Local cell ID EUCELLSECTOREQM.LocalCellId Radio planning (internal planning) The local cell ID must be unique on the eNodeB.
Sector equipment ID EUCELLSECTOREQM.SectorEqmId Radio planning (internal planning) Set this parameter to the sector equipment ID that
has been configured when a sector or a piece of
sector equipment is added.
The number of sectors must be consistent with
the amount of sector equipment for the SFN cell.
Reference signal power PDSCHCFG.ReferenceSignalPwr Default/Recommended value Set this parameter based on the network plan.
Baseband equipment ID EUCELLSECTOREQM.BaseBandEqmId Default/Recommended value Set this parameter based on the network plan.
Reference Signal Power EUCELLSECTOREQM.ReferenceSignalPwrMargin Default/Recommended value Set this parameter based on the network plan.
Margin
The following table describes the parameters that must be set in the EuCellPriBBEqm MO to configure the primary baseband equipment for SFN cells.
Local cell ID EUCELLPRIBBEQM.LocalCellId Radio planning (internal planning) The local cell ID must be unique on the eNodeB.
Primary Baseband Equipment EUCELLPRIBBEQM.PriBaseBandEqmId Radio planning (internal planning) If the primary baseband equipment is not configured
ID for a cell, the eNodeB selects baseband processing
units for the cell among all baseband processing units
that have not been bound to cells.
If this parameter is configured normally, the cell uses
the specified primary baseband equipment. In this
case, the cell can use only the baseband processing
units included in the primary baseband equipment.
Scenario-specific Data
• 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.
SFN UL Scheduling Switch CellAlgoSwitch.SfnUlSchSwitch Engineering design • If adaptive SFN/SDMA is required, set
this parameter to ADAPTIVE(adaptive
scheduling).
• If adaptive SFN/SDMA is not required,
set this parameter to JOINT(joint
scheduling).
SFN DL Scheduling Switch CellAlgoSwitch.SfnDlSchSwitch Engineering design

• If adaptive SFN/SDMA is required, set
this parameter to ADAPTIVE(adaptive
scheduling).
• If adaptive SFN/SDMA is not required,
set this parameter to JOINT(joint
scheduling).
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.
SFN Load-based Adaptive CellAlgoSwitch.SfnLoadBasedAdptSwitch Engineering design • When this parameter is set to OFF,
Switch the SFN cell uses a fixed isolation
decision threshold.
• When this parameter is set to ON,
the SFN cell uses an isolation
decision threshold that is adjusted
based on load status.
Load-based adaptive SFN/SDMA
can take effect only when both
CellAlgoSwitch.SfnUlSchSwitch
and
CellAlgoSwitch.SfnDlSchSwitch
are set to ADAPTIVE(Adaptive).
SFN Downlink Load Period CellDlschAlgo.SfnDlLoadPeriod Radio planning (internal planning) • This parameter specifies the
downlink load measurement period
of an SFN cell. The isolation
decision threshold is changed based
on the cell load in the measurement
period. If the cell load is heavy, the
isolation decision threshold is low
and UEs preferentially work in
independent-scheduling mode. If the
cell load is light, the isolation
decision threshold is high and UEs
preferentially work in joint-scheduling
mode.
• This parameter is valid when
CellAlgoSwitch.SfnDlSchSwitch is
set to ADAPTIVE and invalid when
CellAlgoSwitch.SfnDlSchSwitch is
set to JOINT.
SFN Uplink Load Period CellUlschAlgo.SfnUlLoadPeriod Radio planning (negotiation with the • This parameter specifies the uplink
peer) load measurement period of an SFN
cell. The isolation decision threshold
is changed based on the cell load in
the measurement period. If the cell
load is heavy, the isolation decision
threshold is low and UEs
preferentially work in independent-
scheduling mode. If the cell load is
light, the isolation decision threshold
is high and UEs preferentially work
in joint-scheduling mode.
• This parameter is valid when
CellAlgoSwitch.SfnUlSchSwitch is
set to ADAPTIVE and invalid when
CellAlgoSwitch.SfnUlSchSwitch is
set to JOINT. This parameter applies
only to LTE TDD networks.
• Downlink enhanced algorithm configuration of SFN cells

The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure the downlink two-load level adaption, load threshold, and isolation
decision threshold offset for SFN cells.
SFN Algorithm Switch CellAlgoSwitch.SfnAlgoSwitch Default/Recommended value Two-load level adaption is determined by
SfnDl2LoadLevelAdptSwitch of the
CellAlgoSwitch.SfnAlgoSwitch parameter.
• If SfnDl2LoadLevelAdptSwitch is
on, two load levels are applied.
• If SfnDl2LoadLevelAdptSwitch is
off, load levels are not differentiated.
In addition, SfnDl2LoadLevelAdptSwitch is
valid only when
CellAlgoSwitch.SfnLoadBasedAdptSwitch is
set to ON.
SFN Downlink High Load CellDlschAlgo.SfnDlHighLoadThd Default/Recommended value This parameter determines whether to trigger the
Threshold switchover from light load to heavy load. If this
parameter is set to a small value, the UE
throughput decreases when the cell load is light.
If this parameter is set to a large value, the UE
throughput decreases when the cell load is
heavy.
SFN Downlink Low Load CellDlschAlgo.SfnDlLowLoadThd Default/Recommended value This parameter determines whether to trigger the
Threshold switchover from heavy load to light load. If this

parameter is set to a small value, the UE
throughput decreases when the cell load is light.
If this parameter is set to a large value, the UE
throughput decreases when the cell load is
heavy.
Downlink High Load SDMA CellDlschAlgo.DlHighLoadSdmaThdOffset Default/Recommended value If this parameter is set to a small value, joint-
Threshold Offset scheduling UEs take a small proportion of all
UEs when the cell load is heavy. If this
parameter is set to a large value, joint-
scheduling UEs take a large proportion of all
UEs when the cell load is heavy.
(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.
SFN Algorithm Switch CellAlgoSwitch.SfnAlgoSwitch Default/Recommended value SFN downlink scheduling attribute adjustment is
determined by SfnDlSchAttriAdjsSwitch in the
SfnDlSchAttriAdjsSwitch is valid only when
SfnDl2LoadLevelAdptSwitch is set to ON.
(Optional) The following table describes the parameter that must be set in the CellAlgoSwitch MO to configure CBF for SFN cells.
SFN Algorithm Switch CellAlgoSwitch.SfnAlgoSwitch Default/Recommended value SFN CBF is determined by SfnCbfSwitch in the
SfnCbfSwitch is valid only when
SfnDl2LoadLevelAdptSwitch is set to ON.
It is recommended that the MuBfSwitch option of
the CellAlgoSwitch.MuBfAlgoSwitch parameter
be selected before the SfnCbfSwitch option is
selected.
(Optional) The following table describes the parameter that must be set in the CellAlgoSwitch MO to set the downlink RBLER optimization switch in an adaptive SFN cell
to enable the optimization to resolve consecutive downlink bit errors.
Parameter Name Parameter ID Setting Notes
SFN Algorithm Switch CellAlgoSwitch.SfnAlgoSwitch When the CellAlgoSwitch.SfnDlSchSwitch parameter is set to

ADAPTIVE(Adaptive scheduling), it is recommended that the
SfnDlRblerOptSwitch option of the CellAlgoSwitch.SfnAlgoSwitch
parameter be selected.
• Uplink enhanced algorithm configuration of SFN cells

(Optional) The following table describes the parameter that must be set in the CellAlgoSwitch MO to specify whether layer-2 selective reception is enabled in the uplink.
SFN Algorithm Switch CellAlgoSwitch.SfnAlgoSwitch Default/Recommended value Layer-2 selective reception applies only to 10 MHz
or 20 MHz SFN cells served by 4T4R RRUs. The
SfnUll2SelectiveRcvSwitch option of the
CellAlgoSwitch.SfnAlgoSwitch parameter
specifies whether layer-2 selective reception is
enabled.
• When this option is selected, layer-2
selective reception is enabled and the
working RRUs selectively receive
PUSCH data at the MAC layer.
• When this option is deselected, layer-2
selective reception is disabled and only
the target RRU receives PUSCH data at
the MAC layer.
(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 Threshold parameter. Uplink joint reception can be enabled only when the baseband boards of SFN cells are the LBBPd or
UBBP.
SFN Uplink Comp Switch CELLALGOSWITCH.SfnUplinkCompSwitch Network plan (negotiation not It is recommended that this parameter be set only
required) in the DBS3900 and DBS5900. Do not set this
parameter in LampSite eNodeBs.
Sfn UL CoMP Threshold CELLULCOMPALGO.SfnUlCompThd Radio planning (internal planning) Set this parameter when joint reception is
enabled in the uplink. On the macro eNodeB:
The SfnUlCompThd parameter is set to –8dB by
default.
UL JR Antenna Number CELLALGOSWITCH.UlJRAntNumCombSw Default/Recommended value This parameter specifies whether to enable UL
Combined Switch joint reception among cells each with a specific
number of RX antennas. UL joint reception
among cells each with four RX antennas is
supported by default. For a macro SFN cell, only
the following two options can be selected:
• Ul4R8RJRSwitch (uplink 4R and 8R
joint reception switch)

• Ul8R8RJRSwitch (uplink 8R and 8R
joint reception switch)
(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.
SFN Algorithm Switch CellAlgoSwitch.SfnAlgoSwitch Default/Recommended value It is recommended that the

SfnTarRruSelEnhSwitch option of this parameter
be selected to improve the accuracy of uplink target
RRU selection if the radius of a physical cell in an
SFN cell exceeds 500 meters.
• PDCCH enhanced algorithm configuration of SFN cells

(Optional) The following table describes the parameters that must be set in the MOs CellAlgoSwitch and CELLPDCCHALGO to specify whether to enable PDCCH DCS
in SFN and configure the SFN PDCCH DCS threshold for SFN cells.
SFN Algorithm Switch CellAlgoSwitch.SfnAlgoSwitch Default/Recommended value PDCCH DCS in SFN is controlled by the
SfnPdcchDcsSwitch option of the
PDCCH DCS in SFN takes effect only when the
CellAlgoSwitch.SfnDlSchSwitch parameter is set
to ADAPTIVE(Adaptive).
The SfnPdcchDcsSwitch and
SfnPdcchSdmaSwitch options cannot be both
selected.
SFN Pdcch DCS Threshold CELLPDCCHALGO.SfnPdcchDcsThd Engineering design This parameter specifies the isolation threshold for
deciding whether to enable PDCCH selective
transmission.
A large value of this parameter means high
PDCCH demodulation reliability but leads to severe
PDCCH interference between SFN cells. A small
value of this parameter means light interference
between SFN cells but leads to low PDCCH
demodulation reliability.
(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.
SFN Algorithm Switch CellAlgoSwitch.SfnAlgoSwitch Default/Recommended value PDCCH SDMA in SFN is controlled by the
SfnPdcchSdmaSwitch option of the
When this option is selected, SDMA can be used
for increasing the PDCCH capacity.
When this option is deselected, joint or selective
PDCCH transmission is used in the adaptive
SFN/SDMA feature.
PDCCH SDMA in SFN takes effect only when
CellAlgoSwitch.SfnDlSchSwitch is set to
ADAPTIVE. The SfnPdcchSdmaSwitch and
SfnPdcchDcsSwitch options cannot be both
selected.
SFN Algorithm Switch CellAlgoSwitch.SfnAlgoSwitch Default/Recommended value PUCCH dynamic ACK SDMA is controlled by the
SfnPucchAckSdmaSwitch option of the
If the switch is turned on, the PDCCH SDMA
efficiency is improved while the detection
performance of dynamic ACK messages may
deteriorate.
If the switch is turned off, the detection
performance of dynamic ACK messages may
improve while the PDCCH SDMA efficiency is low.
This switch is valid only when the
SfnPdcchSdmaSwitch option of the
CellAlgoSwitch.SfnAlgoSwitch parameter is
selected.
SFN PDCCH SDMA Threshold CELLPDCCHALGO.SfnPdcchSdmaThd Default/Recommended value This parameter indicates the isolation decision
threshold of PDCCH SDMA.
If this parameter is set to a large value, the
average PDCCH aggregation level and the
PDCCH spatial multiplexing ratio are low.
If this parameter is set to a small value, the
average PDCCH aggregation level and the
PDCCH spatial multiplexing ratio are high.
Set this parameter properly to balance the PDCCH
resource consumption and the multiplexing ratio
for the purpose of increasing the PDCCH capacity
of SFN cells.

For detailed operations, see CME-based Feature Configuration.
Single-carrier Scenario
This document provides configuration guidelines for newly deployed SFN cells. For details about how to combine common cells into SFN cells, see eRAN Reconfiguration Guide.
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.
1. Add sectors.
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.
Example (4T4R sectors):
ADD SECTOR: SECTORID=0, ANTNUM=4, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=60,
2. Add an SFN cell.
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 (4T4R SFN cell):
ADD CELL: LOCALCELLID=0, CELLNAME="TDD_SFN", FREQBAND=41, ULEARFCNCFGIND=NOT_CFG, DLEARFCN=40340, ULBANDWIDTH=CELL_BW_N100, DLBANDWIDTH=CELL_
3. Run the ADD CELLOP command to configure operator information.
Example:
ADD CELLOP: LocalCellId=0, TrackingAreaId=0;
4. Run the ADD BASEBANDEQM command to add baseband equipment.
Example:
ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=3;
5. Run the ADD EUCELLSECTOREQM command to add sector equipment.
The sector equipment ID must be consistent with that configured in 1 and the local cell ID must be consistent with that configured in 2. The sector served by one RRU
can be added to the SFN cell each time this MML command is executed. You can run this command multiple times to configure the RRUs for the SFN cell.
Example:
ADD EUCELLSECTOREQM: LOCALCELLID=0, SECTOREQMID=0, BASEBANDEQMID=0;
6. Run the MOD CELLALGOSWITCH command and set the CellAlgoSwitch.SfnUlSchSwitch and CellAlgoSwitch.SfnDlSchSwitch parameters based on network
requirements.
Example 1 (joint scheduling):
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNULSCHSWITCH=JOINT, SFNDLSCHSWITCH=JOINT;
Example 2 (adaptive scheduling):
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNULSCHSWITCH=ADAPTIVE, SFNDLSCHSWITCH=ADAPTIVE;
7. Run the MOD CELLALGOSWITCH command to enable or disable load-based adaptive isolation threshold adjustment in adaptive SFN/SDMA.
Example 1 (enabling load-based adaptive adjustment):
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNLOADBASEDADPTSWITCH=ON;
Example 2 (disabling load-based adaptive adjustment):
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNLOADBASEDADPTSWITCH=OFF;
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, SFN downlink scheduling attribute adjustment, or SFN CBF.
Example 1 (enabling PDCCH DCS in SFN and layer-2 selective reception):
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNALGOSWITCH=SfnPdcchDcsSwitch-1&SfnUll2SelectiveRcvSwitch-1;
Example 2 (disabling PDCCH DCS in SFN and layer-2 selective reception):
9. (Optional) Run the MOD CELLPDCCHALGO command to set the SFN PDCCH DCS threshold or the SFN PDCCH SDMA threshold.
Example (setting the SFN PDCCH DCS threshold to 20 dB):
MOD CELLPDCCHALGO: LOCALCELLID=0, SfnPdcchDcsThd=40;
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 (setting 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;
11. (Optional) Run the MOD CELLULSCHALGO command to configure the uplink load measurement period of an SFN cell.
Example (setting the uplink load measurement period to 1800 seconds):
MOD CELLULSCHALGO:LOCALCELLID=0, SfnUlLoadPeriod =1800;
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 (turning on the SFN UL CoMP switch and the switch for uplink joint reception between 8R cells):
MOD CELLALGOSWITCH: LocalCellId=0, SfnUplinkCompSwitch=IntraBaseBandSwitch-1, UlJRAntNumCombSw=Ul8R8RJRSwitch-1;
13. (Optional) Run the MOD CELLULCOMPALGO command to set the admission threshold of SFN UL CoMP.
Example (setting the SFN UL CoMP threshold to -5 dB):
MOD CELLULCOMPALGO: LocalCellId=0, SfnUlCompThd=-5;
14. Run the ACT CELL command to activate the SFN cell.
Example:
ACT CELL: LocalCellId=0;
Multi-carrier Scenario (20 MHz + 10 MHz)
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.
Figure 10-2 Example of 20 MHz+10 MHz SFN networking
1. Add sectors.
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.
ADD SECTOR:SECTORID=0,ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=60,ANT3SN=0,ANT
2. Add an SFN cell.
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.
ADD CELL:LOCALCELLID=0,CELLNAME="20M_SFN",FREQBAND=41,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=40340,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW_N100
ADD CELL:LOCALCELLID=1,CELLNAME="10M_SFN",FREQBAND=41,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=40196,ULBANDWIDTH=CELL_BW_N50,DLBANDWIDTH=CELL_BW_N50,C
Example:
Example:
ADD BASEBANDEQM: BASEBANDEQMID=4, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=2, SN2=3;
ADD BASEBANDEQM: BASEBANDEQMID=5, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=4, SN2=5;
Example:
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0,BASEBANDEQMID=0;
6. Run the ADD EUCELLPRIBBEQM command to add primary baseband equipment configuration to a cell.
Example:
ADD EUCELLPRIBBEQM:LOCALCELLID=0,PRIBASEBANDEQMID=4;
requirements.
Example 1 (enabling joint scheduling):
MOD CELLALGOSWITCH: LOCALCELLID=0,SFNULSCHSWITCH=JOINT,SFNDLSCHSWITCH=JOINT;
MOD CELLALGOSWITCH: LOCALCELLID=1,SFNULSCHSWITCH=JOINT,SFNDLSCHSWITCH=JOINT;
Example 2 (enabling adaptive scheduling):
MOD CELLALGOSWITCH:LOCALCELLID=0,SFNULSCHSWITCH=ADAPTIVE,SFNDLSCHSWITCH=ADAPTIVE;
MOD CELLALGOSWITCH:LOCALCELLID=1,SFNULSCHSWITCH=ADAPTIVE,SFNDLSCHSWITCH=ADAPTIVE;
MOD CELLALGOSWITCH:LOCALCELLID=0,SFNLOADBASEDADPTSWITCH=ON;
MOD CELLALGOSWITCH:LOCALCELLID=1,SFNLOADBASEDADPTSWITCH=ON;
MOD CELLALGOSWITCH:LOCALCELLID=0,SFNLOADBASEDADPTSWITCH=OFF;
MOD CELLALGOSWITCH:LOCALCELLID=1,SFNLOADBASEDADPTSWITCH=OFF;

MOD CELLALGOSWITCH:LOCALCELLID=0,SFNALGOSWITCH=SfnPdcchDcsSwitch-1&SfnUll2SelectiveRcvSwitch-1;
10. Run the MOD CELLPDCCHALGO command to set the SFN PDCCH DCS threshold or the SFN PDCCH SDMA threshold.
MOD CELLPDCCHALGO:LOCALCELLID=0,SfnPdcchDcsThd=40;
MOD CELLPDCCHALGO:LOCALCELLID=1,SfnPdcchDcsThd=40;
11. (Optiona,) Run the MOD CELLDLSCHALGO command to configure the downlink load measurement period, downlink heavy-load threshold, downlink light-load
MOD CELLULSCHALGO:LOCALCELLID=0, SfnUlLoadPeriod=1800;
MOD CELLULSCHALGO:LOCALCELLID=1, SfnUlLoadPeriod=1800;
number of antennas.
15. Run the ACT CELL command to activate the SFN cell.
Example:
ACT CELL:LocalCellId=0;
ACT CELL:LocalCellId=1;
NOTE:
For details about precautions for activating an SFN cell, see 10.4.2 Precautions.

Run the DSP CELL command to check cell status.
In the command output:
• If the value of the Cell instance state parameter is Normal, the cell has been activated.
• If the value of the Cell topology type parameter is SFN Type, the cell is an SFN cell.
• If the value of the Work Status parameter is Normal for all RRUs, all RRUs have been activated.
10.4.6 Deactivation


Run the DEA CELL command to deactivate the SFN cell.
Example:
DEA CELL: LocalCellId=0;
10.5 Deployment of Inter-BBU SFN Techniques

This section describes the procedures for deploying the following inter-BBU SFN features:

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
10.5.1 Requirements
Operating Environment
• In indoor coverage scenarios, inter-BBU SFN is not supported.

• In outdoor coverage scenarios, if the baseband processing board is LBBPc or LBBPd, the BBP.WM parameter must be set to TDD_ENHANCE.
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
convergence must be from LBBPc to LBBPd.
• Inter-BBU SFN and inter-BBU adaptive SFN/SDMA support only uplink-downlink subframe configuration 2 and special subframe configuration 7.
• 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 MOD ENODEBFRAMEOFFSET command.
• The Topo Type parameter in the RRUCHAIN MO must be set to CHAIN(CHAIN) or RING(RING).
• In inter-BBU SFN, the same software version such as V100R009C00SPC050 must be loaded for different BBUs connected to the same USU.
• In inter-BBU SFN, the USU software must match the BBU software. For details, see the relevant release notes.
• BBU3910A does not support inter-BBU SFN.
NOTE:
LBBPc boards do not support CBF.
It is recommended that CBF be enabled when the UBBP serves as the primary BBP.
Hardware
For details about hardware, see hardware planning in 10.3 Planning.
License
The operator must purchase and activate the licenses for the features listed in the following table to activate inter-BBU SFN.
TDLOFD-001080 Inter-BBU SFN LT1SBBUSFN00 Inter-BBU SFN (TDD) eNodeB Per eNodeB
The operator must purchase and activate the licenses for the features listed in the following table to activate inter-BBU adaptive SFN/SDMA.
TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA LT1SBBPADA00 Inter-BBP Adaptive SFN/SDMA (TDD) eNodeB Per eNodeB
TDLOFD-001082 Inter-BBU Adaptive SFN/SDMA LT1SBBUADA00 Inter-BBU Adaptive SFN/SDMA (TDD) eNodeB Per eNodeB
The operator must purchase and activate the license for the feature listed in the following table to activate PDCCH DCS in SFN.
TDLOFD-070227 PDCCH DCS in SFN LT1SPDCSIS00 PDCCH DCS in SFN (TDD) eNodeB Per Cell
The operator must purchase and activate the license for the feature listed in the following table to activate PDCCH SDMA in SFN.
TDLOFD-081221 PDCCH SDMA in SFN LT1SPSISFN00 PDCCH SDMA in SFN cells (each cell) eNodeB Per Cell
(TDD)
NOTE:
To know the precautions for using the licenses, see 10.4.1 Requirements.
10.5.2 Precautions
• The X2 interface is required only when there are cells configured on the eNodeB. If all the cells have been deleted on an eNodeB during network reconstruction or
optimization, remove the X2 interface.
• To ensure optimal resource usage, the activation of an SFN cell may deactivate and reactivate some cells served by the eNodeB.
• To deploy an SFN cell on BBUs interconnected through a USU3910, ensure that the primary PLMNs for the BBUs are the same. If the primary PLMNs are different, inter-
BBU links cannot be set up normally and the SFN cell cannot work properly.
• When an SFN cell is served by RRUs connected to both LBBPc and LBBPd or to both LBBPc and UBBP 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.
• BBPs can be combined in LBBPc-only, LBBPd-only, UBBP-only, LBBPc+LBBPd, or LBBPd+UBBP mode for an SFN cell. Table 10-8 describes BBP combination mode
switching and the impact of switching on an inter-BBU SFN cell.
Table 10-8 BBP combination mode switching and the impact of switching on an inter-BBU SFN cell
Switching
LBBPc only LBBPc only No
LBBPc only LBBPd only, UBBP only, or LBBPd+UBBP Yes (The cell is re-established immediately.)
LBBPc only LBBPc+LBBPd Yes (The cell is re-established immediately.)
LBBPd only, UBBP only, or LBBPc only Yes (The cell is re-established immediately.)
LBBPd+UBBP
LBBPd only, UBBP only, or LBBPd only, UBBP only, or LBBPd+UBBP No

LBBPd+UBBP
LBBPd only, UBBP only, or LBBPc+LBBPd Yes (The cell is re-established immediately.)
LBBPd+UBBP
LBBPc+LBBPd LBBPc only Yes (The cell is re-established in the wee hours when there are no users on
the network.)
LBBPc+LBBPd LBBPd only, UBBP only, or LBBPd+UBBP Yes (The cell is re-established in the wee hours when there are no users on
the network.)
Switching
LBBPc+LBBPd LBBPc+LBBPd No
• If the BBUs configured with an SFN cell have an LBBPc and an LBBPd or UBBP, layer 1 must be bound to a single BBP by running the ADD EUCELLSECTOREQM
command before the SFN cell is activated.
• A cell with a bandwidth of 20 MHz and a cell with a bandwidth of 10 MHz must be deployed on different BBPs when they are deployed in the same BBU. The deployment
requirements are as follows:
◾ The carrier with a bandwidth of 20 MHz is preferentially configured on the LBBPd or UBBP, and the carrier with a bandwidth of 10 MHz is preferentially
configured on the LBBPc.
◾ If the BBU configured with an SFN cell houses the LBBPc and LBBPd or UBBP, 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.
• The slots for installing the LBBPd and UBBP in descending order of priority are as follows: slot 3, slot 2, slot 0, slot 1, slot 4, and slot 5. The slots for installing the LBBPc
in descending order of priority are as follows: slot 5, slot 4, slot 1, slot 0, slot 2, and slot 3. The UBBP, LBBPd, and LBBPc must be installed in sequence when all of them
are required.
• 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.
• 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
possible between a BBP installed in slot 0 or 1 and another BBP installed in slot 4 or 5.

Adjusting BBPs in a BBU
Adjust BBPs in a BBU by referring to 10.3 Planning.
Installing the USU
For details about how to install a USU, see USU3900 Installation Guide or USU3910 Installation Guide.

USU Data Configuration
Finish configuring USUs by referring to USU3900 Initial Configuration Guide or USU3910 Initial Configuration Guide.
Data Configuration on the Primary eNodeB
The following table describes the parameters that must be set in the CASCADEPORT MO to configure interconnection ports.
Cabinet No. CASCADEPORT.CN Equipment planning Set this parameter to 0.
Subrack No. CASCADEPORT.SRN Equipment planning Set this parameter to 0.
Slot No. CASCADEPORT.SN Equipment planning Set this parameter to the number of the slot in which the
BBP is installed.
Port No. CASCADEPORT.PN Engineering design Set this parameter to 6 for the LBBPd and UBBP.
Set this parameter to 8 for the UMPT.
Switch CASCADEPORT.SW Engineering design Set this parameter to ON when the BBU is connected to
the USU.
The following table describes the parameter that must be set in the EQUIPMENT MO to configure the ID of open datalink interface (ODI).
Open DU Interface ID EQUIPMENT.ODIID Equipment planning The ODI IDs of interconnected BBUs and USUs must be
unique and cannot be set to 0.
The following table describes the parameters that must be set in the SFNCELLBIND MO to configure the binding relationship between an SFN cell and an auxiliary eNodeB.
Local cell ID SFNCELLBIND.LocalCellId Radio planning (internal planning) The local cell ID must be unique on the eNodeB.
Slave site eNodeB ID SFNCELLBIND.eNodebId Radio planning (internal planning) Set this parameter to the ID of the auxiliary eNodeB to be
bound.
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.
OverBBUsSwitch ENODEBALGOSWITCH.OverBBUsSwitch Engineering design Select the UlSfnJROverBBUsSwitch option of this

parameter.
For details about related parameters in 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.
Data Configuration on the Auxiliary eNodeB
The following table describes the parameters that must be set in the CASCADEPORT MO to configure interconnection ports.

Cabinet No. CASCADEPORT.CN Equipment planning Set this parameter to 0.
Subrack No. CASCADEPORT.SRN Equipment planning Set this parameter to 0.
Slot No. CASCADEPORT.SN Equipment planning Set this parameter to the number of the slot in which the
BBP is installed.
Port No. CASCADEPORT.PN Engineering design Set this parameter to 6 for the LBBPd and UBBP.
Set this parameter to 8 for the UMPT.
Switch CASCADEPORT.SW Engineering design Set this parameter to ON when the BBU is connected to
the USU.
The following table describes the parameter that must be set in the EQUIPMENT MO to configure the ID of open datalink interface (ODI).
Open DU Interface ID EQUIPMENT.ODIID Equipment planning The ODI IDs of interconnected BBUs and USUs must be
unique.
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 auxiliary eNodeBs.
Sector equipment ID SFNAUXRESBIND.SectorEqmId Radio planning (internal planning) Set this parameter to the ID of the sector equipment
configured on an auxiliary eNodeB.
Main eNodeB ID SFNAUXRESBIND.eNodebId Radio planning (internal planning) Set this parameter to the ID of the primary eNodeB.
Main eNodeB Local cell ID SFNAUXRESBIND.LocalCellId Radio planning (internal planning) Set this parameter to the ID of the local cell of the primary
eNodeB.
For details about related parameters in the MOs Sector, Cell, EUCELLSECTOREQM, BASEBANDEQM, EUCELLPRIBBEQM, CellAlgoSwitch, and CELLPDCCHALGO, see
section "Deployment of Intra- and Inter-BBP SFN Techniques".
NOTE:
When adding a standby cell to an auxiliary 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 is the primary BBU and BBU 1 is the secondary BBU. 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 auxiliary eNodeB ID is 101.
Figure 10-3 Example of inter-BBU SFN networking
Configurations for Interconnections Between BBUs and USUs
1. Run the SET EQUIPMENT command to set the ODI ID, and then run the RST BTSNODE command to reset the USU/BBU to make the ODI ID take effect.
Example 1 (configuring the ODI ID on the USU):
SET EQUIPMENT: ODIID=67;
RST BTSNODE:;
Example 2 (configuring the ODI ID on BBU 0):
SET EQUIPMENT:ODIID=100;
RST BTSNODE:;
Example 3 (configuring the ODI ID on BBU 1):
SET EQUIPMENT:ODIID=101;
RST BTSNODE:;
2. Run the SET CASCADEPORT command with the SW parameter set to ON(On) to configure interconnection ports.
Example 1 (configuring the interconnection port status of the UCXU and UCIU on the USU):
SET CASCADEPORT:CN=0,SRN=0,SN=2,PN=0,SW=ON;
Example 2 (configuring the interconnection port status of the BBP and UMPT on BBU 0):
Example 3 (configuring the interconnection port status of the BBP and UMPT on BBU 1):
Data Configuration on the Primary eNodeB
1. 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, enabling the eNodeB to create the default sector
equipment.
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.
ADD CELL:LOCALCELLID=0,CELLNAME="TDD_SFN",FREQBAND=41,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=40340,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW_N100
Example:
Example:
Examples:
6. (Optional) Perform this step only in the multi-carrier (10 MHz + 20 MHz) scenario. In the single-carrier scenario, perform 7.
Run the ADD EUCELLPRIBBEQM command to add primary baseband equipment configuration to a cell.
Example:
requirements.
Example 1 (enabling joint scheduling):
MOD CELLALGOSWITCH:LOCALCELLID=0,SFNULSCHSWITCH=JOINT,SFNDLSCHSWITCH=JOINT;
Example 2 (enabling adaptive scheduling):
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNULSCHSWITCH=ADAPTIVE, SFNDLSCHSWITCH=ADAPTIVE;
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNLOADBASEDADPTSWITCH=ON;
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNLOADBASEDADPTSWITCH=OFF;
10. (Optional) Run the MOD CELLPDCCHALGO command to set the SFN PDCCH DCS threshold or the SFN PDCCH SDMA threshold.
MOD CELLPDCCHALGO: LOCALCELLID=0,SfnPdcchDcsThd=40;
11. (Optional) Run the MOD CELLDLSCHALGO command to configure the downlink load measurement period, downlink heavy-load threshold, downlink light-load
MOD CELLDLSCHALGO:LOCALCELLID=0,SfnDlLoadPeriod=30,SfnDlHighLoadThd= 50,SfnDlLowLoadThd=20,DlHighLoadSdmaThdOffset=2;
MOD CELLULSCHALGO:LOCALCELLID=0,SfnUlLoadPeriod =1800;
number of antennas.
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;
16. Run the ADD ENODEBFUNCTION command to add the ID of the primary eNodeB.
Example:
ADD ENODEBFUNCTION: eNodeBFunctionName="LTE", ApplicationRef=1, eNodeBId=100;
17. On the primary eNodeB, run the ADD SFNCELLBIND command to add a binding relationship between the SFN cell and the auxiliary eNodeB.
Example:
ADD SFNCELLBIND: LOCALCELLID=0, ENODEBID=101;
18. Run the ACT CELL command on the primary eNodeB to activate an SFN cell.
Example:
ACT CELL: LocalCellId=0;
NOTE:
It is recommended that an SFN cell be activated after data configurations have been completed on auxiliary eNodeBs.
Data Configuration on Auxiliary eNodeBs
1. 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, enabling the eNodeB to create the default sector
equipment.
Example:
3. Run the ADD ENODEBFUNCTION command to add the ID of the auxiliary eNodeB.
Example:
ADD ENODEBFUNCTION: eNodeBFunctionName="LTE", ApplicationRef=1, eNodeBId=101;
4. Run the ADD SFNAUXRESBIND command to bind the sector equipment of an auxiliary 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;
5. (Optional) Configure standby cells on all the auxiliary eNodeBs.
a. Run the ADD CELL command to add a standby cell.

A 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 (4T4R SFN cell): 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,DLEARFCN=40340,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CEL
Example 2 (4T4R SFN cell): 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,DLEARFCN=40340,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CEL
b. Run the ADD EUCELLSECTOREQM command to add sector equipment.
Example (adding sector equipment for a standby cell that is also an SFN cell):
c. (Optional) Perform this step only in multi-carrier (10 MHz + 20 MHz) scenarios. In the single-carrier scenario, perform Step 4. Run the ADD
EUCELLPRIBBEQM command to add primary baseband equipment configuration to the cell.
Example:
ADD EUCELLPRIBBEQM: LOCALCELLID=0,PRIBASEBANDEQMID=0;
ADD EUCELLPRIBBEQM: LOCALCELLID=1,PRIBASEBANDEQMID=1;
d. Run the ADD CELLOP command to configure operator information.

Example:
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:
• SFN uplink scheduling switch (CELLALGOSWITCH.SfnUlSchSwitch)
• SFN downlink scheduling switch (CELLALGOSWITCH.SfnDlSchSwitch)
• SFN load-based adaptive algorithm switch (CELLALGOSWITCH.SFNLOADBASEDADPTSWITCH)
• SFN algorithm switch (CELLALGOSWITCH.SfnAlgoSwitch)
• SFN PDCCH DCS threshold (CellPdcchAlgo.SfnPdcchDcsThd)
• SFN PDCCH SDMA threshold (CellPdcchAlgo.SfnPdcchSdmaThd)
• Downlink load measurement period (CellDlschAlgo.SfnDlLoadPeriod)
• SFN downlink high load threshold (CellDlschAlgo.SfnDlHighLoadThd)
• SFN downlink low load threshold (CellDlschAlgo.SfnDlLowLoadThd)
• Isolation decision threshold offset of downlink heavy-load level (CellDlschAlgo.DlHighLoadSdmaThdOffset)
• Uplink load measurement period of SFN cell (CellUlschAlgo.SfnUlLoadPeriod)
• UL CoMP switch in SFN cell (CELLALGOSWITCH.SfnUplinkCompSwitch)
• Uplink joint reception switch of a specified number of antennas (CELLALGOSWITCH.UlJRAntNumCombSw)
• UL CoMP admission threshold in SFN cell (CELLULCOMPALGO.SfnUlCompThd)
• Algorithm switch based on BBU coordination (ENODEBALGOSWITCH.OverBBUsSwitch)

Run the DSP CELL command to check cell status.
In the command output:
• If the value of the Cell instance state parameter is Normal, the SFN cell has been activated.
• If the value of the Cell topo type parameter is SFN Type, the cell is an SFN cell.
• 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


Run the DEA CELL command to deactivate the SFN cell on the primary eNodeB.
Example:
DEA CELL: LocalCellId=0;
10.6 Performance Monitoring

Table 10-9 describes the SFN performance monitoring methods.
Table 10-9 Monitoring method
Monitoring Method SFN Feature
Starting SFN detection monitoring tasks • TDLOFD-001075 SFN

Starting multi-user BF and cell-level multi-user • TDLOFD-002008 Adaptive SFN/SDMA

BF monitoring tasks • TDLOFD-001081 Inter-BBP Adaptive SFN/SDMA
Measuring counters • TDLOFD-001075 SFN

CHR log analysis • TDLOFD-001075 SFN

Starting SFN Detection, Multi-User BF and Cell-level Multi-User BF Monitoring Tasks
On the U2000, start SFN detection, multi-user beamforming (MUBF) monitoring, and cell-level MUBF monitoring tasks to monitor the RRU utilization, link quality, and MUBF- and
CBF-capable UE pairing status when SFN is enabled.
1. Log in to the U2000 client.

2. Choose Monitor > Signaling Trace > Signaling Trace Management. (The following steps use only starting SFN detection as an example.)
3. In the navigation tree, choose LTE > User Performance Monitoring > SFN Detection Monitoring. The SFN Detection Monitoring dialog box is displayed.
4. Select an eNodeB, and click Next.
5. Set the SFN detection parameters, and click Finish. The SFN detection 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.
6. On the right of the Signaling Trace Management tab page, right-click the SFN detection monitoring task and choose Query Result to check the results of the items
described in Table 10-10.
Table 10-10 Monitoring result of SFN Detect
Monitoring Object Definition
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 ID This item indicates the ID of the uplink sector equipment.
Uplink Sector Equipment Group ID This item indicates the ID of an uplink sector equipment group.
UL RRU Slot No. This item indicates the attribute of an uplink RRU. Uplink RRUs can be classified into:
• Work RRU
• Target RRU
• Other RRU
• Work RRU (Joint Reception)
• 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 SINR This item indicates the SINR reported after layer 2 filtering.
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 Equipment ID This item indicates the ID of the downlink sector equipment.
Downlink Sector Equipment Group ID This item indicates the ID of a downlink sector equipment group.
DL RRU Slot No. This item indicates the attribute of a downlink RRU. Downlink RRUs can be classified into:
• Work RRU
• Target RRU
PDCCH RRU eNodeB ID This item indicates the eNodeB ID of the RRU used for PDCCH transmission.
PDCCH Sector Equipment ID This item indicates the cell sector equipment ID of the RRU used for PDCCH transmission.
PDCCH Sector Equipment Group ID This item indicates the cell sector equipment group ID of the RRU used for PDCCH transmission.
PDCCH RRU Slot No. This item indicates the attribute of an RRU used for PDCCH transmission. PDCCH RRUs can be classified into:
• Work RRU
• Target RRU
Table 10-11 and Table 10-12 describe the monitoring results of Multi-user BF (User) and Multi-user BF (Cell), respectively.
Table 10-11 Monitoring result of Multi-user BF (User)
Number of RBs allocated to successfully paired UEs for MUBF Indicates the number of RBs that are allocated to successfully paired UEs within a
period (one second).
Number of RBs allocated to successfully paired UEs for SFNCBF Indicates the number of RBs that are allocated to successfully paired UEs within a
period (one second).
Table 10-12 Monitoring result of Multi-user BF (User)
Number of RBs allocated to successfully paired UEs for MUBF Indicates the number of RBs that are allocated to successfully paired UEs for
MUBF.
Number of successfully paired UE pairs for MUBF Indicates the number of successfully paired UE pairs for MUBF.
Number of RBs allocated to paired UEs for MUBF Indicates the number of RBs that are allocated to paired UEs for MUBF.
Number of RBs allocated to successfully paired UEs for SFNCBF Indicates the number of RBs that are allocated to successfully paired UEs for
SFNCBF.
Number of successfully paired UE pairs for SFNCBF Indicates the number of successfully paired UE pairs for SFNCBF.
Number of RBs allocated to paired UEs for SFNCBF Indicates the number of RBs allocated to paired UEs for SFNCBF.
Measuring counters
The counters listed in the following table are used to indicate UE attribute changes and distributions of joint-scheduling UEs and independent-scheduling UEs when SFN and
adaptive SFN/SDMA are enabled.
Table 10-13 Performance measurement counters of SFN
Counter Name Description
L.SFN.User.DLI2J Number of times the downlink attribute of a UE changes from independent-scheduling to

joint-scheduling
L.SFN.User.DLJ2I Number of times the downlink attribute of a UE changes from joint-scheduling to

independent-scheduling
L.SFN.DLTRRU.Chg Number of times the target RRU of a UE changes in the downlink in an SFN cell
L.SFN.ULJSch.User.Avg Average number of joint-scheduling UEs in the uplink
L.SFN.ULJSch.RRU.Avg Average number of working RRUs per joint-scheduling UE in the uplink
L.SFN.User.ULI2J Number of times the uplink attribute of a UE changes from independent-scheduling to

joint-scheduling
L.SFN.User.ULJ2I Number of times the uplink attribute of a UE changes from joint-scheduling to

independent-scheduling
L.SFN.ULTRRU.Chg Number of times the uplink target RRU of a UE in an SFN cell changes
L.SFN.DLJSch.User.Avg Average number of joint-scheduling UEs in the downlink
L.SFN.DLJSch.RRU.Avg Average number of working RRUs per joint-scheduling UE in the downlink
L.Traffic.DL.SchTime.UE Total duration of downlink scheduling for all UEs with services in a cell
L.Traffic.UL.SchTime.UE Total duration of uplink scheduling for all UEs with services in a cell
L.SFN.PDCCH.RRU.Avg Average number of working RRUs for PDCCH transmission in an SFN cell
L.ULSFNJR.User.Avg Average number of UEs in an SFN cell with uplink joint reception enabled
L.ChMeas.PRB.UL.ULSFNJR.Used.Avg Average number of PRBs used by UEs in an SFN cell with uplink joint reception enabled
L.Thrp.bits.DL.BorderUE.JointTransmit Total downlink traffic volume of PDCP SDUs for joint-transmission CEUs in a cell
L.Thrp.bits.DL.LastTTI.BorderUE.JointTransmit Downlink traffic volume of PDCP SDUs sent in the last TTI before the buffer of the UE is
empty for joint-transmission CEUs in a cell
L.Thrp.Time.DL.RmvLastTTI.BorderUE.JointTransmit Duration of transmitting data for joint-transmission CEUs in a cell except the last TTI
before the downlink buffer is empty
L.Thrp.Time.DL.BorderUE.JointTransmit Total duration of sending PDCP SDUs to joint-transmission CEUs in a cell
L.Thrp.bits.UL.BorderUE.JointReception Total uplink traffic volume of PDCP PDUs for joint-reception CEUs in a cell
L.Thrp.bits.UL.SmallPkt.BorderUE.JointReception Traffic volume of PDCP PDUs scheduled for uplink small packets for joint-reception
CEUs in a cell
L.Thrp.Time.UL.RmvSmallPkt.BorderUE.JointReception Duration of transmitting uplink data except small packets for joint-reception CEUs in a
cell
L.Thrp.Time.UL.BorderUE.JointReception Total duration of receiving PDCP PDUs from joint-reception CEUs in a cell
L.ChMeas.PRB.PDSCH.Avg.BorderUE.JointTransmit Average number of PRBs used by the PDSCH for joint-transmission CEUs in a cell
L.ChMeas.PRB.PUSCH.Avg.BorderUE.JointReception Average number of PRBs used by the PUSCH for joint-reception CEUs in a cell
Table 10-14 Performance measurement counters based on sector equipment
L.CellSectorEQUIP.SFN.DLISch.User.Avg Average number of independently scheduled UEs in the downlink served by a set of sector
equipment in an SFN cell
L.CellSectorEQUIP.SFN.ULISch.User.Avg Average number of independently scheduled UEs in the uplink served by a set of sector
L.CellSectorEQUIP.SFN.DL.User.Avg Average number of UEs served by a set of sector equipment in an SFN cell during downlink
scheduling
L.CellSectorEQUIP.SFN.UL.User.Avg Average number of UEs served by a set of sector equipment in an SFN cell during uplink
scheduling
L.CellSectorEQUIP.SFN.Traffic.User.TM9.Avg Average number of UEs that apply TM9 under a sector equipment of an SFN cell
L.CellSectorEQUIP.SFN.DLISch.PRB.Avg Average number of PRBs occupied by independently scheduled UEs in the downlink served
by a set of sector equipment in an SFN cell
L.CellSectorEQUIP.SFN.ULISch.PRB.Avg Average number of PRBs occupied by independently scheduled UEs in the uplink served
by a set of sector equipment in an SFN cell
L.CellSectorEQUIP.SFN.DL.PRB.Used.Avg Average number of downlink PRBs for UEs served by a set of sector equipment in an SFN
cell
L.CellSectorEQUIP.SFN.UL.PRB.Used.Avg Average number of uplink PRBs for UEs served by a set of sector equipment in an SFN cell
L.CellSectorEQUIP.SFN.E-RAB.SuccEst Number of successful E-RAB setup times on a set of sector equipment in an SFN cell
L.CellSectorEQUIP.SFN.E-RAB.EstFail Number of E-RAB setup failures on a set of sector equipment in an SFN cell
L.CellSectorEQUIP.SFN.E-RAB.NormRel Number of normal E-RAB releases on a set of sector equipment in an SFN cell

L.CellSectorEQUIP.SFN.E-RAB.AbnormRel Number of abnormal E-RAB releases on a set of sector equipment in an SFN cell
L.CellSectorEQUIP.SFN.Traffic.DL.SCH.TB.bits Number of bits used for initial service transmissions on the downlink SCH on a set of sector
L.CellSectorEQUIP.SFN.Traffic.UL.SCH.TB.bits Number of bits used for initial service transmissions on the uplink SCH on a set of sector
L.CellSectorEQUIP.SFN.Traffic.DL.SchTime Duration of downlink service scheduling at the MAC layer of a set of sector equipment in an
SFN cell
L.CellSectorEQUIP.SFN.Traffic.UL.SchTime Duration of uplink service scheduling at the MAC layer of a set of sector equipment in an
SFN cell
L.CellSectorEQUIP.ULSFNJR.User.Avg Average number of UEs served by a set of sector equipment in an SFN cell with uplink joint
reception enabled
L.CellSectorEQUIP.ChMeas.PRB.UL.ULSFNJR.Used.Avg Average number of PRBs used by UEs served by a set of sector equipment in an SFN cell
with uplink joint reception enabled
L.CellSectorEQUIP.SFN.RRC.ConnReq.Att Number of RRC connection setup requests initiated by UEs served by a set of sector
L.CellSectorEQUIP.SFN.RRC.SetupFail Number of RRC connection setup failures on a set of sector equipment in an SFN cell
L.CellSectorEQUIP.SFN.RRC.ConnReq.Succ Number of successful RRC connection setup times on a set of sector equipment in an SFN
cell
Table 10-15 Performance measurement counters based on sector equipment groups
L.CellSectorEQUIPGroup.SFN.DLISch.User.Avg Average number of independently scheduled UEs in the downlink

served by a sector equipment group in an SFN cell
L.CellSectorEQUIPGroup.SFN.ULISch.User.Avg Average number of independently scheduled UEs in the uplink served

by a sector equipment group in an SFN cell
L.CellSectorEQUIPGroup.SFN.DL.User.Avg Average number of UEs served by a sector equipment group in an

SFN cell during downlink scheduling
L.CellSectorEQUIPGroup.SFN.UL.User.Avg Average number of UEs served by a sector equipment group in an

SFN cell during uplink scheduling
L.CellSectorEQUIPGroup.SFN.Traffic.User.TM9.Avg Average number of UEs that apply TM9 under a sector equipment
group of an SFN cell
L.CellSectorEQUIPGroup.SFN.DLISch.PRB.Avg Average number of PRBs occupied by independently scheduled UEs

in the downlink served by a sector equipment group in an SFN cell
L.CellSectorEQUIPGroup.SFN.ULISch.PRB.Avg Average number of PRBs occupied by independently scheduled UEs

in the uplink served by a sector equipment group in an SFN cell
L.CellSectorEQUIPGroup.SFN.DL.PRB.Used.Avg Average number of downlink PRBs for UEs served by a sector

equipment group in an SFN cell
L.CellSectorEQUIPGroup.SFN.UL.PRB.Used.Avg Average number of uplink PRBs for UEs served by a sector

L.CellSectorEQUIPGroup.SFN.E-RAB.SuccEst Number of successful E-RAB setup times in a sector equipment group

in an SFN cell
L.CellSectorEQUIPGroup.SFN.E-RAB.EstFail Number of E-RAB setup failures in a sector equipment group in an

SFN cell
L.CellSectorEQUIPGroup.SFN.E-RAB.NormRel Number of normal E-RAB releases in a sector equipment group in an

SFN cell
L.CellSectorEQUIPGroup.SFN.E-RAB.AbnormRel Number of abnormal E-RAB releases in a sector equipment group in

an SFN cell
L.CellSectorEQUIPGroup.SFN.Traffic.DL.SCH.TB.bits Number of bits used for initial service transmissions on the downlink
SCH in a sector equipment group in an SFN cell
L.CellSectorEQUIPGroup.SFN.Traffic.UL.SCH.TB.bits Number of bits used for initial service transmissions on the uplink SCH
in a sector equipment group in an SFN cell
L.CellSectorEQUIPGroup.SFN.Traffic.DL.SchduleTime Duration of downlink service scheduling at the MAC layer of a sector

L.CellSectorEQUIPGroup.SFN.Traffic.UL.SchduleTime Duration of uplink service scheduling at the MAC layer of a sector

L.CellSectorEQUIPGroup.SFN.RRC.ConnReq.Att Number of RRC connection setup requests initiated by UEs served by

a sector equipment group in an SFN cell
L.CellSectorEQUIPGroup.SFN.RRC.SetupFail Number of RRC connection setup failures in a sector equipment group

in an SFN cell
L.CellSectorEQUIPGroup.SFN.RRC.ConnReq.Succ Number of successful RRC connection setup times in a sector

CHR log analysis
The PERIOD_UE_MultiRRU_UL_RSRP_MR event is periodically logged. Table 10-16 describes the meaning of each field in the log.
Table 10-16 Meaning
Field Definition
Cnt Number of valid physical cells for UEs in the uplink.
MultiRRUInfolist eNodeBID ID of the eNodeB that provides the uplink physical cell
when an MR is reported.
LocalCellID ID of a local cell where the uplink physical cell is located

SectorEqmId ID of the cell sector equipment of the uplink physical cell

SectorEqmGroupId ID of the cell sector equipment group of the uplink physical

cell when an MR is reported.
ULSRSRsrp RSRP of uplink SRS.
10.7 Parameter Optimization

None
10.8 Possible Issues

SFN and Adaptive SFN/SDMA
If the BBP an SFN cell has been configured on is faulty, the SFN cell is automatically deactivated and ALM-29240 Cell Unavailable is reported. After the fault is rectified, the SFN cell
is automatically activated.
Inter-BBP SFN and Inter-BBP Adaptive SFN/SDMA
• The primary BBP on which an SFN cell has been configured is faulty.
If the primary BBP is faulty, the SFN cell is automatically deactivated and ALM-29240 Cell Unavailable is reported. The primary eNodeB then attempts to select another
one of its BBPs as the primary BBP. If the attempt succeeds, the SFN cell is reactivated. If the attempt fails, troubleshoot the primary BBP. After the fault is rectified, the
SFN cell is automatically activated.
• A secondary BBP on which an SFN cell has been configured is faulty.
If a secondary BBP is faulty, all the RRUs connected to this BBP are deactivated and ALM-29248 RF Out of Service is reported. After the fault in the secondary BBP is
rectified, these RRUs are automatically activated.
• Allocation of primary BBP resources fails.
If the primary BBP resources are sufficient and the allocation fails due to a large number of resource fragments, the SFN cell cannot be activated and ALM-29240 Cell
Unavailable is reported. In this case, run the DSP PRIBBPADJUST command to check whether BBP resources are sufficient and how to adjust BBP resources of other
cells to ensure that the primary BBP is successfully allocated to the SFN cell. Table 10-17 describes the displayed information and the corresponding handling methods.
Table 10-17 Query result and handling method
Displayed Information Handling Method
Bind the primary baseband equipment to Manually select the primary BBP based on the primary-BBP allocation information displayed in the DSP PRIBBPADJUST
cells based on the following scheme. command output.
Primary BBP allocation after running the Run the STR PRIBBPADJUST command to adjust the primary BBP resources allocated to other activated cells.
STR PRIBBPADJUST command.
The total BBP resources are insufficient. Adjust SFN networking based on BBP capabilities.
Inter-BBU SFN and Inter-BBU Adaptive SFN/SDMA
• If the primary or secondary BBP of an SFN cell is faulty or primary BBP resources fail to be allocated, handle the fault by referring to Inter-BBP SFN and Inter-BBP
Adaptive SFN/SDMA.
• The IDX1 or IDX2 link is disconnected.
If the IDX1 or IDX2 link is disconnected, the auxiliary eNodeB reports ALM-29248 RF Out of Service, and the primary eNodeB reports ALM-29243 Cell Capability
Degraded.
NOTE:
When the IDX1 or IDX2 link is disconnected, the auxiliary eNodeB cannot obtain the cell ID and name. Therefore, the values of the Cell Name and Cell ID parameters in
the alarm information are invalid.
• In BBU interconnection scenarios, a fault may occur the cable connection between a BBU and a USU or between USUs is incorrect:
◾ If the cable connection between a BBU and a USU is incorrect, 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 on the eNodeB and USU to query the interconnection topologies. Then, ask
field engineers to adjust the cable connections.
◾ If the cable connection between USUs is incorrect, the USUs report ALM-27110 Inter-Port Connection Error. Run the DSP INTERCONTOPO command on the
USUs to query the interconnection topology. Then, ask field engineers to adjust the cable connections.
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
12 Reference Documents
This chapter lists the reference documents related to SFN.
1. Base Station Initial Configuration Guide

2. USU3900 Hardware Description
3. USU3900 Installation Guide
4. USU3900 Initial Configuration Guide
5. USU3910 Hardware Description
6. USU3910 Installation Guide
7. USU3910 Initial Configuration Guide
8. eRAN Reconfiguration Guide

9. USU3900-based Multi-BBU Interconnection Feature Parameter Description
10. USU3910-based Multi-BBU Interconnection Feature Parameter Description
11. Beamforming Feature Parameter Description
12. MIMO Feature Parameter Description

Seleksi Penerimaan Cpns Bekraf 2018 2 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Seleksi Penerimaan Cpns Bekraf 2018 2 PDF

Uploaded by

Copyright:

Available Formats

SFN Feature Parameter Description Page 1 of 43

HUAWEI TECHNOLOGIES CO., LTD.

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

Huawei Technologies Co., Ltd.

10.5.5 Activation Observation

1 About This Document

1.2 Intended Audience

• Need to understand the features described herein

1.3 Change History

eRAN TDD 13.0 03 (2018-01-29)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected Entity

Feature change None None N/A

eRAN TDD 13.0 02 (2017-12-25)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected Entity

Editorial change Revised descriptions in this document. None N/A

eRAN TDD 13.0 01 (2017-09-05)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected Entity

Feature change None None N/A

Editorial change Revised descriptions in this document. None N/A

eRAN TDD 13.0 Draft B (2017-08-06)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected Entity

Feature change None None N/A

Editorial change Revised descriptions in this document. None N/A

eRAN TDD 13.0 Draft A (2017-06-30)

Change Type Change Description Parameter Change Affected Entity

Feature change None None • 3900 and 5900 series

Editorial change Revised descriptions in this document. None N/A

1.4 Differences Between eNodeB Types

SFN Category Description Feature

SFN Category Description Feature

SFN Category Description Feature

3.1 Joint-Scheduling-based SFN

3.2 Adaptive SFN/SDMA

• TDLOFD-002008 Adaptive SFN/SDMA

3.2.2 UE Attribute Decision

Downlink UE Attribute Decision

The eNodeB determines downlink UE attributes as follows:

Uplink UE Attribute Decision

Figure 3-3 Procedure for determining uplink UE attributes

The eNodeB determines uplink UE attributes as follows:

3.2.3 Adaptive Resource Scheduling

Figure 3-5 Independent scheduling

Downlink Adaptive Resource Scheduling

Uplink Adaptive Resource Scheduling

3.3 PDCCH Enhancement in Adaptive SFN/SDMA

3.3.1 PDCCH DCS in Adaptive SFN/SDMA

• PDCCH DCS in SFN not enabled

3.3.2 PDCCH SDMA in Adaptive SFN/SDMA

• PDCCH SDMA in SFN not enabled

3.4 Coordination Between Adaptive SFN/SDMA and Multiple-Antenna Techniques

3.4.1 Inter-RRU CBF in Adaptive SFN/SDMA

Figure 3-10 Inter-RRU CBF (1)

3.4.2 MU-Beamforming in Adaptive SFN/SDMA

3.4.3 Adaptive SFN/SDMA+MU MIMO

4 Intra-BBP SFN Features

5 Inter-BBP SFN Features

Figure 5-1 Inter-BBP SFN cell

6 Inter-BBU SFN Features

• Inter-BBU interconnection links are faulty.