Professional Documents
Culture Documents
1 LTE FDD
4T6S Solution
Security Level:
Purpose
This document provides simplified guidelines for frontline engineers to deploy the 4T6S solution. It describes
the solution principles, module and antenna specifications, hardware planning roadmap, GUL multi-mode
splitting solution, application scenarios, as well as gain evaluation methods and expectations. For details, see
LTE FDD 4T6S Solution User Guide. Software-defined antennas (SDAs) and 8T8R RRUs are introduced in
eRAN16.1.
Change History
Version Date Prepared By Reviewed By Change Description
4T4R
4T4R
1.8 GHz 4T4R 1.8 GHz 4T4R Frequency Band 1710–2600 MHz
33° 33°
4T
R
4T 4
4R
beam beam
2.1 GHz 4T4R 2.1 GHz 4T4R 8-port 4T4R multi-beam Gain 18.0–19.4 dBi
antenna
Electrical 2° to 12°, left and right beams
8-port 4T4R multi- AMB4519R6v06 Downtilt are adjusted separately
beam antenna
Dual-beam antenna
1 x AMB4519R6v06
4T4R
4T4R
Frequency Band 1710–2600 MHz, 800–900 MHz
1.8 GHz 4T4R 33° 33° 1.8 GHz 4T4R Gain 17.5 dBi/15.3 dBi
4T
R
4T 4
4R
2.1 GHz 4T4R
beam beam
2.1 GHz 4T4R 12-port SDA t Electrical 2° to 12°, left and right beams
s ubjec Downtilt are adjusted separately
e
700/900 MHz 2T2R 12-port SDA t i o n s ar ion.
Support 1.8–2.6 p e c ifica nformat Available Time 2020Q1
Power 8 x 40 W
Broadband 8T8R module
RRU5862
Sector A IBW 40 MHz + 40 MHz
@ 1.8 GHz+2.1 GHz
Sector B
@ 1.8 GHz+2.1 GHz Dimensions 24L
Support 4T4R RRU
CPRI combination RRU5862 Weight 25 kg
BBU
Each module supports
(39XX / 59XX) Available Time 2020Q2
8T8R @ 1.8 GHz+2.1 GHz
f1 No power sharing
Before After
Pmax Pmax
Benefit for
P0/1 P0/1 P2/3 inter-carrier + inter-
P2/3 sector scenarios
Provide benefit for 100% UEs
QPSK UE QAM UE
S2
2L+4T6S AMB4519R13v06 27013405 2 x 690–960 MHz 1.7–2.6 GHz 12 499 x 206@2 m Available
2L+4T6S AMB4519R9v06 27013238 2 x 690–960 MHz 1.7–2.6 GHz 12 499 x 206@2.6 m 2019Q2
2L+2H+4T6S AMB4519R18v06 27013558 2 x 690–960/2 x 1695–2690 MHz 1.7–2.6 GHz 16 499 x 206@2 m 2019Q4
2 x 690–960 MHz
2L+4T6S SDA TBD TBD
4 x 1695–2690 MHz
1.7–2.6 GHz 12 499 x 206@2 m 2020Q1
*The antenna size is not finalized. It is for reference only and is not committed.
**The Available state of antennas is defined as TR5.
Note: The antenna specifications will be updated from time to time. The preceding information is for reference
only. For details about the antenna product specifications, visit
http://3ms.huawei.com/mm/docMaintain/mmMaintain.do?method=showMMDetail&f_id=Ann190430360216756 .
Considering both capacity gains and costs, it is recommended Considering that the module is mainly used for LTE network capacity expansion,
that 8T8R+digital-analog hybrid antennas be used for evolution in it is recommended that a large number of channels be reserved for LTE.
2T3S scenarios. The gains of single SDA ports differ. The GSM coverage shrinks by about 2 dB
with the same power configuration. The impact needs to be aligned with that of
the site.
Evolution
Evolution target In non-recommended scenarios, review the configuration based on the site
scenario
8T8R Capacity+evolution 8T8R+ configuration.
target 2T3S digital-analog hybrid
Modernization antenna
scenario replacement Power allocation suggestions for 8 x 40 W channels
4T4R RRU
Capacity+evolution
combination+
4T3S •
Existing 4T usage
digital-analog hybrid Total GSM power consumption ≤ 40 W
antenna
• Total UMTS power consumption ≤ 40 W
Small gains
• The remaining 8 x 30 W power is configured
provided by 4T6S
Massive MIMO
2T6S based on the 1 W/M PSD for LTE, which
upgrading
GSM UMTS LTE
can incorporate the 30 MHz spectrum.
L.ChMeas.PRB.DL.Used.Avg
120000000000
80
100000000000
80000000000 60
60000000000 40
40000000000
20
20000000000
0 0
0 52 104156208260312364416468520572637741
Cell 2
L.ChMeas.PRB.DL.Used.Avg (None) L.Thrp.bits.DL (bit)
L.Traffic.User.Avg
3. UEs are evenly distributed under the left and right beams. The 4. The included angle between sectors is at least 90° before sector splitting.
proportion of UEs under the left beam is between 30% and 70%.
Cell 1
< 90°
≥ 90°
DL tRAFFIC
8
User THP
150
6
100
4
2 50
0 0
0 200000 400000 600000 800000 1000000 1200000 0 200 400 600 800 1000 1200 1400
DL PRB
DL Traffic
4T6S Solution
Baseline
Increase in User-Perceived Rates Increase in Spectral Efficiency
(Throughput vs Traffic) (Traffic vs PRB Ratio)
When SDAs are used, power sharing improves network experience and capacity. The expected gains are the
same as the single-channel power of common antennas. However, it is not recommended that SDAs be directly
compared with common split antennas.
4T4R 4T4R 4T4R 4T4R 4T4R 4T4R 4T4R 4T4R 4T4R 4T4R
33° 33° 33° 33° 33° 33° 33° 33°
beam beam beam beam 33° 33° beam beam beam beam
beam beam
AMB4520R6v06 AMB4520R6v06 AMB4520R6v06 AMB4520R6v06
AMB4520R6v06
RPCU
UBBPd6 6 6
UBBPd (UBBPd1 to
UBBPd (UBBPd1 to UBBPd (UBBPd1 to
UBBPd6/UBBPd9)
BBU and BBP selection principles UBBPd6/UBBPd9) UBBPd6/UBBPd9)
UBBPe (UBBPe1 to
1. BBU5900 is recommended for new sites. UBBPe (UBBPe1 to UBBPe (UBBPe1 to
UBBPe4/UBBPe5/UBBPe6)
UBBPe4/UBBPe5/UBBPe6) UBBPe4/UBBPe5/UBBPe6)
2. If BBU3900 is used at an existing site, it is recommended BBP WBBP (WBBPa/WBBPb1 to
UBBPei/UBBPem/UBBPf1/
UBBPei/UBBPem/UBBPf1/
that BBU3900 be replaced with BBU3910 or BBU5900. UBBPex2
WBBPb4/WBBPd1 to UBBPex2
LBBP (LBBPd1 to LBBPd5)
3. The UBBPe board supporting six cells is preferred. Intra- WBBPd3/WBBPf1 to WBBPf4) UBBPfw1
(customized)
LBBP (LBBPc/LBBPd1 to LBBP (LBBPc/LBBPd1 to
frequency cells are deployed on the same board. Boards WBBP (WBBPf1 to WBBPf4)
LBBPd5) LBBPd5) (customized)
supporting only three cells are not recommended. (customized)
4. When SDAs are used, the BBP must be UBBPe or UBBPg. The boards in blue are supported by the corresponding BBUs only.
The boards in red are not supported according to specifications but supported according to capabilities. They are available for customization.
R R R
Voltage boosting R R R R R R
R R R DCDU12B R R R
power distribution box n R R R R R R
R R R U but io
riU U DCDU12B
U U e r dis t d. U U U U U U
U w e
8 62 poODMlement
RRU5 be supp ODM
T8 R t o
8 is
The olution ODM
s
Material: Material:
Material:
One voltage boosting power distribution box One DCDU
One power input per RRU One ODM per RRU One DCDU
Two power inputs per RRU One power input per RRU
3-sector 2T2R/4T4R 6-sector 4T4R Select the six- Alternative solution: Use the six-sector solution if the
LTE Priority 3 sector solution. features are mutually exclusive and cannot be disabled.
6-sector 2T2R 6-sector 4T4R
Three sectors (cell combination)
Three sectors UMTS cell combination and UL CloudAIR are mutually • UMTS multi-sector solution selection process
UMTS exclusive. In this scenario, six sectors are used.
UL Six sectors Six sectors
2100 Select the cell
Start Is the baseline Y Is UL CloudAIR N combination
3-sector 2T2R/4T4R 6-sector 4T4R three-sector?
LTE configured? solution.
6-sector 2T2R 6-sector 4T4R Priority 1
FDD N Y
LTE 3-sector 2T2R/4T4R 6-sector 4T4R
2600 It is recommended that
Select the six- UL CloudAIR be
TDD sector solution.
LTE 3-sector 2T2R/4T4R 6-sector 4T4R disabled.
2600
Priority 2
Supported as of
With CoBCCH Separate-MPT or Co-MPT 2T4R cell Supported as of SRAN13.1 (2018-11)
SRAN13.1 (2018-11)
The cell combination feature is mutually exclusive with
Without Combined Supported as of
Separate-MPT or Co-MPT Supported in SRAN11.1 some GSM features. For details, contact GSM engineer
4 x 2T2R RRU CoBCCH cell SRAN13.1 (2018-11)
Xu Faguo (employee ID: 00275657).
(combined)
You are advised to disable the CoBCCH feature or
With CoBCCH Separate-MPT or Co-MPT Not supported
replace the RRU with a 4T4R RRU.
UL2100
LTE Configuration Scenario
UMTS Configuration UMTS Setting
UL without CloudAIR UL with CloudAIR
LTE Configuration RRU Scenario Notes
UL2100
LTE Configuration Scenario
UMTS UMTS
Configuration Setting UL without CloudAIR UL with CloudAIR Remarks
LTE Scenario Notes
RRU
Configuration
RRU1_A RRU1_A
RRU1_A RRU1_A
SECTOR1 SECTOR1
+ - + -+ - + - + -+
- CAL CAL
+ - + -
RPCU
CAL B D F H
A C D B A C D B A C E G
RRU1 RRU2 RRU
B Combiner 4 4 6 y1 -
Sector 2
A Combiner 3 2
C Combiner 3 5
RRU5502 2.6G 4T4R RRU 2.6G 4T4R RRU RRU3281
RRU5502 D Combiner 4 2
B Combiner 4 5
Note: All radio parameters except device parameters must inherit the original cell configurations. Do not use a new site deployment template. Otherwise,
gains cannot be obtained or KPIs may fluctuate due to parameter inconsistency between two cells. You are advised to use the MAE to prepare site
deployment scripts. For details, visit http://3ms.huawei.com/hi/group/9261/thread_7655427.html?mapId=9434835&for_statistic_from=all_group_forum&l=en .
ADD EUCELLSECTOREQM: LOCALCELLID=x2, SECTOREQMID=x2; //Enabling TX channel calibration for combined RRUs
ACT CELL: LocalCellId=x2; ADD EUCELLSECTOREQM: LocalCellId=x2, SECTOREQMID=x2;
MOD RRUJOINTCALPARACFG: LocalCellId=x2, TxChnCalSwitch=ON, TxChnCalTime=03&00&00,
TxChnCalPeriod=48;
ACT CELL: LocalCellId=x2;
//Turning on the extreme power sharing switch MOD CELLDYNPOWERSHARING: LocalCellId=x1, DynamicPowerSharingSwitch=LTE_EXTREME_POWER_SHARING_SW-1;
MOD CELLDYNPOWERSHARING: LocalCellId=x2, DynamicPowerSharingSwitch=LTE_EXTREME_POWER_SHARING_SW-1;
//Activating the cells
ACT CELL: LocalCellId=x1;
ACT CELL: LocalCellId=x2;
• Activation verification: Based on the uplink RSSI and RRU/RFU output power, check whether the uplink 4R/8R
and downlink 4T/8T have taken effect. If they have not taken effect, check the engineering connections and
parameter configurations onsite in a timely manner. When SDAs are used, the cell is configured as 8T8R with eight channels.
• Alarm check and cell status check: If no new alarm is generated after splitting, the cell status is normal. Otherwise, rectify the fault
based on the corresponding prompt.
• Site verification:
Check whether basic services of each site are normal.
Check whether the antenna feeder is reversely connected. (Check whether the PCI distribution is consistent with that of engineering
parameters based on DT data.)
Check whether cable connections are correct.
• General principles: Verify the solution by cluster, without differentiating frequency bands.
The expected gains cannot be ensured for each split due to many factors, such as scenario satisfaction, UE distribution, traffic
model, user behavior, holidays, and counter fluctuations. Therefore, acceptance by cluster is preferred.
If the 4T6S solution is deployed on a multi-band network, the acceptance should be performed on all frequency bands at a time.
• Acceptance criteria:
Capacity: Virtual clusters are used for acceptance. These clusters only consist of split sectors, which may not be geographically
contiguous. Generally, cluster planning is performed based on delivery time and geographical areas. It is recommended that at least
20 sectors be involved and scatter charts be used for evaluation.
Drive test: The methods are the same as those for verifying new sites. After 4T6S deployment, the average RSRP should be
equivalent to that for 2T3S/4T3S, and the average SINR is expected to be slightly lower than that for 2T3S/4T3S.
KPI: After 4T6S deployment, basic KPIs (such as the RRC connection setup success rate, E-RAB setup success rate, service drop
rate, and handover success rate) remain stable during peak hours and slightly decrease during off-peak hours. Some counters, such
as the CQI, MCS index, and rank 2 proportion, decrease slightly.
Note: If non-Huawei multi-beam antennas are used, performance expectations will change, depending on antenna performance. No
acceptance commitment is made.
Main lobe
Main lobe Main lobe
• Gains brought by capacity solutions are mainly indicated
by peak-hour KPIs. However, peak-hour data rates during
DTs fluctuate greatly with traffic, so coverage (rather than
rates) is usually evaluated during DTs.
• The parameters of the • Adjust the azimuths • RF optimization: Adjust • Adjust the MLB policy • If the number of CEUs
new split cells must be and downtilts based on the azimuths towards to achieve load increases significantly,
consistent with those the check results and the split cell with heavy balancing between increase the downtilts
of the original cells. inherit the original traffic to balance UEs frequency bands. by 1° or 2°.
• If performance settings. in the left and right
parameters can be • Adjust feeder cells.
further optimized and connections or CRS
the customer agrees, port mapping based on
further optimize the the check results.
parameters.
Before Before downtilt After downtilt Before Before downtilt After downtilt Before Before downtilt After downtilt
construction adjustment adjustment construction adjustment adjustment construction adjustment adjustment
Select this option. (If the frequency reselection priority is high and low, and the
CellAlgoSwitch.MlbA InterFreqLoadEvalPrd Set this parameter to 10.
InterFreqMlbSwitch lowest priority has only one frequency, MLB can be disabled for the frequency with
lgoSwitch
the lowest priority.)
CellCapacityScaleFactor The default value 10 is recommended.
If the operator has requirements for PRB balance, it is recommended that this It is recommended that this parameter be set
CellMLB MlbTriggerMode parameter be set to PRB_OR_UE_NUMBER. Otherwise, set this parameter to FreqSelectStrategy
to FAIRSTRATEGY.
UE_NUMBER_ONLY.
LoadBalanceNCellScope Set this parameter to ADAPTIVE.
CellMLB InterFreqUeTrsfType Select both SynchronizedUE and IdleUE options.
CellMLB UeNumDiffOffsetTransCa Set this parameter to 100.
CellAlgoSwitch.Enha DediPrioManageOnLowL
It is recommended that this option be selected.
MLB algorithm ncedMlbAlgoSwitch oadSw It is recommended that this parameter be set
selection MlbHoCellSelectStrategy
CellAlgoSwitch.Enha SpectralEffBasedLoadEv to ONLY_STRONGEST_CELL.
It is recommended that this option be selected.
ncedMlbAlgoSwitch alSw SnrBasedUeSelectionMode The default value Random is recommended.
It is recommended that this option be selected in normal cases. When CA is
enabled on the live network and the traffic volume per UE served by SCCs is less MlbInterFreqEffiRatio The default value 100 is recommended.
CellAlgoSwitch.Enha
CaUserLoadTransferSw than 30% of that served by the PCC, it is recommended that this option be Algorithm
ncedMlbAlgoSwitch
selected. When this option is selected, the UeNumDiffOffsetTransCa parameter parameter EutranInterNFreq
value must be changed to 100. setting Set this parameter to ALLOWED in common
notes MlbTargetInd
CellAlgoSwitch.Enha ActiveUeBasedLoadEval scenarios.
It is recommended that this option be deselected.
ncedMlbAlgoSwitch Sw
CellReselPriorityCfgInd Set this parameter to CFG.
If there is no 5 MHz cell whose frequency can be treated as a target for MLB, set
this parameter to 15, 30, or 40 for 10 MHz, 15 MHz, or 20 MHz cells, respectively. Set this parameter to YES for inter-frequency
InterFreqIdleMlbUeNumT EutranInterFreqNCell OverlapInd
If there is 5 MHz cell whose frequency can be treated as a target for MLB, set this co-coverage cells.
hd
parameter to 10, 25, 40, or 55 for 5 MHz, 10 MHz, 15 MHz, or 20 MHz cells,
respectively. Set this parameter to -103 in the unit of dBm
InterFreqHoGroup InterFreqLoadBasedHoA4ThdRSRP
(default value).
If there is no 5 MHz cell whose frequency can be treated as a target for MLB, set
this parameter to 30, 40, or 50 for 10 MHz, 15 MHz, or 20 MHz cells, respectively. RrcConnStateTimer T320ForLoadBalance Set this parameter to min10 (default value).
CellMLB InterFreqMlbUeNumThd If there is 5 MHz cell whose frequency can be treated as a target for MLB, set this
parameter to 15, 30, 50, or 65 for 5 MHz, 10 MHz, 15 MHz, or 20 MHz cells, CellAlgoSwitch.FreqP It is recommended that this option be
LoadTriggerFreqPriHoSwitch
respectively. riorityHoSwitch deselected.
It is recommended that this parameter be set to 40 in the unit of %. The default CellMlbHo.MlbMatch It is recommended that this option be
InterFreqMlbThd HoAdmitSwitch
Algorithm value is 60. OtherFeatureMode deselected.
parameter MlbUeNumOffset Set this parameter to 5. Set the SnrBasedUeSelectionMode
setting notes Inter-frequency non-co-site scenarios
LoadOffset Set this parameter to 8 in the unit of %. parameter to Worst.
IdleMlbUeNumDiffThd Set this parameter to 15 in the unit of %. Disable inter-frequency MLB and enable load
High-speed scenarios
pre-balancing in fixed proportions.
UeNumDiffThd Set this parameter to 15 in the unit of %.
LoadDiffThd Set this parameter to 15 in the unit of %. Networks with different frequencies are
provided by different vendors, or the X2
LoadTransferFactor Set this parameter to 0 (default value). Special Enable blind MLB but disable inter-frequency
interface is not configured between
MlbIdleUeNumAdjFactor Set this parameter to 0 (default value). scenarios MLB.
Huawei base stations and inter-base-
If the MlbTriggerMode parameter is set to PRB_OR_UE_NUMBER, it is station MLB is required.
recommended that this parameter be set to 2 in the unit of %. If the Deselect the PrbUsage option of the
MlbUeSelectPrbThd SFN scenarios
MlbTriggerMode parameter is set to UE_NUMBER_ONLY, it is recommended MultiRruMode parameter.
that this parameter be set to 50. Set the InterFreqMLBRanShareMode
MOCN scenarios
MlbMaxUeNum Set this parameter to 20. (The default value is 5.) parameter.
Thank you.
organization for a fully connected,
intelligent world.