Professional Documents
Culture Documents
11
70%
1.25
The document provides different networking strategies for these scenarios. In addition, it
provides KPIs of in-service sites mapping the two scenarios as a reference
For frequencies that allow camping, ensure the continuous coverage to reduce the risk of
call drops caused by inter-frequency band handovers in the circuit switched (CS) domain.
The soft handover success rate is higher than the inter-frequency band hard handover
success rate.
Considering the network evolution trend and networking possibilities, the R99+HSPA
hybrid networking strategy is recommended. If only R99 services are carried over
frequencies, HSPA services fall back to R99 service, causing code resource congestion.
Therefore, it is not recommended that only R99 services be carried over frequencies.
If the barred camping strategy is used, packet switching (PS) call drop rate increases
when the signaling storm solution is deployed. Therefore, the barred camping strategy is
not recommended
Inter-frequency band blind handover neighboring cell: Only the inter-frequency band
blind handover can be performed between the source and target cells. The coveragebased inter-frequency band handover and inter-frequency band reselection are not
supported. In addition, the source and target cells have the same coverage but different
frequencies.
Coverage-based inter-frequency band handover neighboring cell: Only the coveragebased inter-frequency band handover can be performed between the source and target
cells. The inter-frequency band reselection and inter-frequency band blind handover are
not supported.
Inter-frequency band neighboring cells that have the same coverage can be configured
as inter-frequency band reselection or inter-frequency band blind handover neighboring
cells. Inter-frequency band neighboring cells that have different coverage can be
configured as coverage-based inter-frequency band handover neighboring cells.
For different frequencies used in the same sectors, the following configuration is
recommended:
After the HSPA+ features are introduced, the network first selects candidate cells with
the highest HSPA+ capabilities based on the highest capability of UEs. Currently, the
capacity loss caused by sharing of carriers between MIMO and HSPA can be controlled
within 10%. After the MIMO+H co-frequency problem is solved, MIMO and 64QAM can
be regarded as an enhanced high speed downlink packet access (HSDPA) technology.
For details about the MIMO+HSPA hybrid networking scenario, see the networking
solutions of other common scenarios. If independent carriers are required for deployment
of MIMO and 64QAM, the networking requirement can be addressed by incorporating
the HSPA+ capability mapping between candidate cells and UEs and the service priority.
For details, see the following descriptions.
ADD UCELLALGOSWITCH:NBMULCACALGOSELSWITCH
ADD UNODEBALGOPARA:HsupaCeConsumeSelection=GBR;
ADD UCELLALGOSWITCH:NBMCacAlgoSwitch=CRD_ADCTRL-1
Null
ADD UCELLALGOSWITCH:NBMCacAlgoSwitch=HSDPA_UU_ADCTRL1&HSUPA_UU_ADCTRL-1
ADD UCELLALGOSWITCH:NBMCacAlgoSwitch=HSDPA_GBP_MEAS1&HSDPA_PBR_MEAS-1&HSUPA_PBR_MEAS1&HSUPA_EDCH_RSEPS_MEAS-1
Confidential
Information of Huawei. No Spreading Without
SET UCORRMALGOSWITCH:DrSwitch=DR_RAB_SING_DRD_SWITCH-1
Permission
SET UCORRMALGOSWITCH:DrSwitch=DR_RAB_COMB_DRD_SWITCH-0
SET UDRD:ServiceDiffDrdSwitch=OFF,
SET UDRD:ConnectFailRrcRedirSwitch=Allowed_To_Inter_RAT;
SET UDRD:LdbDRDSwitchDCH=OFF,
LdbDRDSwitchHSDPA=ON, LdbDRDchoice=UserNumber,
ADD UCELLCAC:MAXHSDPAUSERNUM=64
Triggered by CE resources
SET ULDCALGOPARA:LdcSwitch=NODEB_CREDIT_LDR_SWITCH1&LCG_CREDIT_LDR_SWITCH-1&LC_CREDIT_LDR_SWITCH-1;
LDR action
ADD UCELLALGOSWITCH:NBMLdcAlgoSwitch=UL_UU_LDR-1&DL_UU_LDR1&CELL_CODE_LDR-1&CELL_CREDIT_LDR1,NbmLdcUeSelSwitch=NBM_LDC_MATCH_UE_ONLY;
ADD UCELLLDR:LdrCodeUsedSpaceThd=13
SET UUSERPRIORITY:PriorityReference=ARP,CarrierTypePriorInd=DCH
Configure neighboring cells using the same carrier as intra-frequency band neighboring
cells.
ADD UINTRAFREQNCELL
Configure the concentric F2 cells with different frequencies as the inter-frequency band
blind handover cells of F1 cells.
ADD U2GNCELL
Handover based on load: LDR is used to balance the load between two carriers
Whether the camping strategy takes effect: The number of RRC connection requests
sent on F2 should be much smaller than that on F1.
VS.RRC.AttConnEstab.Cell
Balance of the number of HSPA subscribers on two carriers: The HSPA subscriber load
balancing algorithm is used. Theoretically, the difference in the number of HSPA
subscribers on two carriers cannot exceed 4, that is, MAXHSDPAUSERNUM x
LdbDRDOffsetHSDPA = 64 x 0.05 = 3.2.
Success rate of RB setup for Outgoing Inter-Frequency Directed Retry: used to analyze
the DRD success rate.
VS.HSDPA.UE.Mean.Cell
VS.DRD.RBSetup.SuccOut/VS.DRD.RBSetup.AttOut x 100%
VS.HHO.AttInterCell.LB/VS.HHO.SuccInterCell.LB x 100%
Answer:
Access Strategy (CAC, RRC redirection),LDR Strategy and DC Strategy are same with
scenario 1
UEs camp on F1 or F2 at random. The reselection offsets of F1 and F2 are not set, or
set to the same value. The following is a configuration example:
Configure neighboring cells using the same carrier as intra-frequency band neighboring cells.
ADD UINTRAFREQNCELL
Configure the concentric F2 cells with different frequencies as the inter-frequency band blind
handover cells of F1 cells.
Configure the concentric F1 cells with different frequencies as the inter-frequency band blind
handover cells of F2 cells.
ADD U2GNCELL
Camping Strategy, LDR Strategy , Mobility Strategy and DC Strategy are same between
Voice Performance First and System Capacity First in scenario 1
Camping Strategy, LDR Strategy , Mobility Strategy and DC Strategy are same between
Voice Performance First and System Capacity First in scenario 1
Whether the preferred camping strategy takes effect: The number of RRC connection
requests sent on F2 should be much smaller than that on F1 or be equal to zero.
VS.RRC.AttConnEstab.Cell
Difference in the number of HSPA subscribers on two carriers after the service steering
strategy is deployed: The number of HSPA subscribers on F1 is much smaller than that
on F2 or is equal to zero. The number of HSPA subscribers on F1 is not equal to zero
only when the number of subscribers on F2 reaches MAXHSDPAUSERNUM, or LDR is
triggered, or the number of combined service requests is large, or rollback upon a DRD
failure is initiated.
VS.HSDPA.UE.Mean.Cell
Success rate of RB setup for Outgoing Inter-Frequency Directed Retry: used to analyze
the DRD success rate.
VS.DRD.RBSetup.SuccOut/VS.DRD.RBSetup.AttOut x 100%
VS.HHO.AttInterCell.LB/VS.HHO.SuccInterCell.LB x 100%
Answer:
If UEs camp on F1, F2, F3/F4 at random, services initiated on the coverage
border of F3/F4 may be hard handed over to F1 or F2 and call drops may occur.
Therefore, random camping on 3 or 4 carriers is not recommended in this
scenario.
In the 3-carrier scenario, only a pair of DC cells can exist. If DC must be deployed on the
entire network, it is recommended that F1 and F2 be configured as a pair of DC cells
(ensure that a spacing of 5 MHz must be reserved between F1 and F2). If DC is enabled
only for hotspot cells, it is recommended that F2 and F3 be configured as a pair of DC
cells (ensure that a spacing of 5 MHz must be reserved between F2 and F3).
Whether the camping strategy takes effect: The number of RRC connection requests
sent on F1 should be basically the same as that on F2. The number of RRC connection
requests sent on F3 or F4 should be much smaller than that on F1 or F2, or be equal to
zero.
VS.RRC.AttConnEstab.Cell
Balance of the number of HSPA subscribers on four carriers: The HSPA subscriber load
balancing algorithm is used. Theoretically, the difference in the number of HSPA
subscribers on any two of the four carriers cannot exceed 4, that is,
MAXHSDPAUSERNUM x LdbDRDOffsetHSDPA = 64 x 0.05 = 3.2.
VS.HSDPA.UE.Mean.Cell
Inter-frequency band hard handover success rate: The coverage-based handover from
F3 or F4 to F1 or F2 exists. Therefore, the inter-frequency band hard handover success
rate is much lower than the intra-frequency band hard handover success rate.
Success rate of RB setup for Outgoing Inter-Frequency Directed Retry: used to analyze
the DRD success rate.
VS.DRD.RBSetup.SuccOut/VS.DRD.RBSetup.AttOut x 100%
VS.HHO.AttInterCell.LB/VS.HHO.SuccInterCell.LB x 100%
Random camping of UEs can basically ensure load balancing of HSPA services
between carriers during access of HSPA subscribers. Therefore, load balancing of
HSPA services is not needed, which decreases the number of DRDs and increases the
RAB setup success rate of HSPA services. In special conditions, if load balancing of
HSPA services is enabled, the load balancing effect is only little better than that in the
case that load balancing is disabled. Currently, random camping is enabled but load
balancing of HSPA services is disabled on a network in Canada.
In the 3-carrier scenario, only a pair of DC cells can exist. If DC must be deployed on the
entire network, it is recommended that F1 and F2 be configured as a pair of DC cells
(ensure that a spacing of 5 MHz must be reserved between F1 and F2). If DC is enabled
only for hotspot cells, it is recommended that F2 and F3 be configured as a pair of DC
cells (ensure that a spacing of 5 MHz must be reserved between F2 and F3).
Whether the camping strategy takes effect: The number of RRC connection requests
sent on F1 should be basically the same as that on F2. The number of RRC connection
requests sent on F3 or F4 should be much smaller than that on F1 or F2, or be equal to
zero.
VS.RRC.AttConnEstab.Cell
Balance of the number of HSPA subscribers on four carriers: The HSPA subscriber load
balancing algorithm is used. Theoretically, the difference in the number of HSPA
subscribers on any two of the four carriers cannot exceed 4, that is,
MAXHSDPAUSERNUM x LdbDRDOffsetHSDPA = 64 x 0.05 = 3.2.
VS.HSDPA.UE.Mean.Cell
Inter-frequency band hard handover success rate: The coverage-based handover from
F3 or F4 to F1 or F2 exists. Therefore, the inter-frequency band hard handover success
rate is much lower than the intra-frequency band hard handover success rate.
Success rate of RB setup for Outgoing Inter-Frequency Directed Retry: used to analyze
the DRD success rate.
VS.DRD.RBSetup.SuccOut/VS.DRD.RBSetup.AttOut x 100%
VS.HHO.AttInterCell.LB/VS.HHO.SuccInterCell.LB x 100%
Whether the camping strategy takes effect: The number of RRC connection requests
sent on F1 should be basically the same as that on F2. The number of RRC connection
requests sent on F3 or F4 should be much smaller than that on F1 or F2, or be equal to
zero.
VS.RRC.AttConnEstab.Cell
Balance of the number of HSPA subscribers on four carriers: The HSPA subscriber load
balancing algorithm is used. Theoretically, the difference in the number of HSPA
subscribers on any two of the four carriers cannot exceed 4, that is,
MAXHSDPAUSERNUM x LdbDRDOffsetHSDPA = 64 x 0.05 = 3.2.
VS.HSDPA.UE.Mean.Cell
Inter-frequency band hard handover success rate: The coverage-based handover from
F3 or F4 to F1 or F2 exists. Therefore, the inter-frequency band hard handover success
rate is much lower than the intra-frequency band hard handover success rate.
Success rate of RB setup for Outgoing Inter-Frequency Directed Retry: used to analyze
the DRD success rate.
VS.DRD.RBSetup.SuccOut/VS.DRD.RBSetup.AttOut x 100%
VS.HHO.AttInterCell.LB/VS.HHO.SuccInterCell.LB x 100%
Answer:
If UEs camp on F1, F2, F3/F4 at random, services initiated on the coverage
border of F3/F4 may be hard handed over to F1 or F2 and call drops may occur.
Therefore, random camping on 3 or 4 carriers is not recommended in this
scenario.
In the 3-carrier scenario, only a pair of DC cells can exist. If DC must be deployed on the
entire network, it is recommended that F1 and F2 be configured as a pair of DC cells
(ensure that a spacing of 5 MHz must be reserved between F1 and F2). If DC is enabled
only for hotspot cells, it is recommended that F2 and F3 be configured as a pair of DC
cells (ensure that a spacing of 5 MHz must be reserved between F2 and F3).
Whether the camping strategy takes effect: The number of RRC connection requests
sent on F1 should be basically the same as that on F2. The number of RRC connection
requests sent on F3 or F4 should be much smaller than that on F1 or F2, or be equal to
zero.
VS.RRC.AttConnEstab.Cell
Balance of the number of HSPA subscribers on four carriers: The HSPA subscriber load
balancing algorithm is used. Theoretically, the difference in the number of HSPA
subscribers on any two of the four carriers cannot exceed 4, that is,
MAXHSDPAUSERNUM x LdbDRDOffsetHSDPA = 64 x 0.05 = 3.2.
VS.HSDPA.UE.Mean.Cell
Inter-frequency band hard handover success rate: The coverage-based handover from
F3 or F4 to F1 or F2 exists. Therefore, the inter-frequency band hard handover success
rate is much lower than the intra-frequency band hard handover success rate.
Success rate of RB setup for Outgoing Inter-Frequency Directed Retry: used to analyze
the DRD success rate.
VS.DRD.RBSetup.SuccOut/VS.DRD.RBSetup.AttOut x 100%
VS.HHO.AttInterCell.LB/VS.HHO.SuccInterCell.LB x 100%
Random camping of UEs can basically ensure load balancing of HSPA services
between carriers during access of HSPA subscribers. Therefore, load balancing of
HSPA services is not needed, which decreases the number of DRDs and increases the
RAB setup success rate of HSPA services. In special conditions, if load balancing of
HSPA services is enabled, the load balancing effect is only little better than that in the
case that load balancing is disabled. Currently, random camping is enabled but load
balancing of HSPA services is disabled on a network in Canada.
Whether the camping strategy takes effect: The number of RRC connection requests
sent on F1 should be basically the same as that on F2. The number of RRC connection
requests sent on F3 or F4 should be much smaller than that on F1 or F2, or be equal to
zero.
VS.RRC.AttConnEstab.Cell
Balance of the number of HSPA subscribers on four carriers: The HSPA subscriber load
balancing algorithm is used. Theoretically, the difference in the number of HSPA
subscribers on any two of the four carriers cannot exceed 4, that is,
MAXHSDPAUSERNUM x LdbDRDOffsetHSDPA = 64 x 0.05 = 3.2.
VS.HSDPA.UE.Mean.Cell
Inter-frequency band hard handover success rate: The coverage-based handover from
F3 or F4 to F1 or F2 exists. Therefore, the inter-frequency band hard handover success
rate is much lower than the intra-frequency band hard handover success rate.
Success rate of RB setup for Outgoing Inter-Frequency Directed Retry: used to analyze
the DRD success rate.
VS.DRD.RBSetup.SuccOut/VS.DRD.RBSetup.AttOut x 100%
VS.HHO.AttInterCell.LB/VS.HHO.SuccInterCell.LB x 100%
Whether the camping strategy takes effect: The number of RRC connection requests
sent on F1 should be basically the same as that on F2. The number of RRC connection
requests sent on F3 or F4 should be much smaller than that on F1 or F2, or be equal to
zero.
VS.RRC.AttConnEstab.Cell
Balance of the number of HSPA subscribers on four carriers: The HSPA subscriber load
balancing algorithm is used. Theoretically, the difference in the number of HSPA
subscribers on any two of the four carriers cannot exceed 4, that is,
MAXHSDPAUSERNUM x LdbDRDOffsetHSDPA = 64 x 0.05 = 3.2.
VS.HSDPA.UE.Mean.Cell
Inter-frequency band hard handover success rate: The coverage-based handover from
F3 or F4 to F1 or F2 exists. Therefore, the inter-frequency band hard handover success
rate is much lower than the intra-frequency band hard handover success rate.
Success rate of RB setup for Outgoing Inter-Frequency Directed Retry: used to analyze
the DRD success rate.
VS.DRD.RBSetup.SuccOut/VS.DRD.RBSetup.AttOut x 100%
VS.HHO.AttInterCell.LB/VS.HHO.SuccInterCell.LB x 100%
In the general strategy of this scenario, U900s are not used for improvement of weak
To deploy the DC strategy, two carriers must be in the same band and the spacing
between two carriers must be 5 MHz. Therefore, in this scenario, only F1 and F2 can be
configured as a pair of DC cells. If the spacing between F1 and F2 exceeds 5 MHz, the
DC strategy cannot be deployed.
Configure neighboring cells using the same carrier as intra-frequency band neighboring
cells.
ADD UINTRAFREQNCELL
Configure the concentric F3 and F4 cells with different frequencies as the unidirectional
inter-frequency band blind handover cells of F1 and F2 cells.
Configure the concentric F1 and F2 cells with different frequencies as the inter-frequency
band blind handover cells of each other.
Configure the concentric F3 and F4 cells with different frequencies as the inter-frequency
band blind handover cells of each other.
Configure 2G inter-RAT neighboring cells for F1, F2, F3, and F4 cells.
ADD U2GNCELL
Whether the random camping strategy takes effect: The number of RRC connection
requests sent on F2 should be basically the same as that on F1. If F4 is used to cover
coverage holes, some UEs may camp on F4. Therefore, some RRC requests may exist
on F4, but the number of RCCs on F3 or F4 should be much smaller than that on F1 or
F2 or be equal to zero.
Balance of the number of HSPA subscribers on four carriers: The HSPA subscriber load
balancing algorithm is used. Theoretically, the difference in the number of HSPA
subscribers on any two of the four carriers cannot exceed 4, that is,
MAXHSDPAUSERNUM x LdbDRDOffsetHSDPA = 64 x 0.05 = 3.2.
Success rate of RB setup for Outgoing Inter-Frequency Directed Retry: used to analyze
the DRD success rate.
VS.HSDPA.UE.Mean.Cell
Inter-frequency band hard handover success rate: The coverage-based handover from
F3 or F4 to F1 or F2 exists. Therefore, the inter-frequency band hard handover success
rate is much lower than the intra-frequency band hard handover success rate.
VS.RRC.AttConnEstab.Cell
VS.DRD.RBSetup.SuccOut/VS.DRD.RBSetup.AttOut x 100%
VS.HHO.AttInterCell.LB/VS.HHO.SuccInterCell.LB x 100%
ADD UCELLACCESSSTRICT:
IDLECELLBARRED=NOT_BARRED,CONNCELLBARRED=NOT_BARRED
The coverage of U900 is better than that of U2100. Some sites need to use U900s for
improvement of weak coverage, that is, use U900s to handle services in areas that are
not covered by U2100s. In this scenario, a lot of hard handovers occur during voice
services and call drop rate is high. Therefore, it is recommended that the optimization
solution be used when U900 F3 and F4 are also used for continuous coverage.
In the general strategy of this scenario, U900s are not used for improvement of weak
coverage.
To deploy the DC strategy, two carriers must be in the same band and the spacing
between two carriers must be 5 MHz. Therefore, in this scenario, only F1 and F2 can be
configured as a pair of DC cells. If the spacing between F1 and F2 exceeds 5 MHz, the
DC strategy cannot be deployed.
When configuring the cell selection or reselection data, set the inter-frequency band reselection
thresholds of F2, F3, and F4 to large values so that inter-frequency band reselection can be easily
triggered. The following is a configuration example:
Set the offset so that UEs preferentially camp on F1. The following is a configuration example:
Configure neighboring cells using the same carrier as intra-frequency band neighboring
cells.
ADD UINTRAFREQNCELL
Configure the concentric F3 and F4 cells with different frequencies as the unidirectional
inter-frequency band blind handover cells of F1 and F2 cells.
Configure the concentric F1 and F2 cells with different frequencies as the inter-frequency
band blind handover cells of each other.
Configure the concentric F3 and F4 cells with different frequencies as the inter-frequency
band blind handover cells of each other.
Configure 2G inter-RAT neighboring cells for F1, F2, F3, and F4 cells.
ADD U2GNCELL
Whether the random camping strategy takes effect: The number of RRC connection
requests sent on F2 should be basically the same as that on F1. If F4 is used to cover
coverage holes, some UEs may camp on F4. Therefore, some RRC requests may exist
on F4, but the number of RCCs on F3 or F4 should be much smaller than that on F1 or
F2 or be equal to zero.
Balance of the number of HSPA subscribers on four carriers: The HSPA subscriber load
balancing algorithm is used. Theoretically, the difference in the number of HSPA
subscribers on any two of the four carriers cannot exceed 4, that is,
MAXHSDPAUSERNUM x LdbDRDOffsetHSDPA = 64 x 0.05 = 3.2.
Success rate of RB setup for Outgoing Inter-Frequency Directed Retry: used to analyze
the DRD success rate.
VS.HSDPA.UE.Mean.Cell
Inter-frequency band hard handover success rate: The coverage-based handover from
F3 or F4 to F1 or F2 exists. Therefore, the inter-frequency band hard handover success
rate is much lower than the intra-frequency band hard handover success rate.
VS.RRC.AttConnEstab.Cell
VS.DRD.RBSetup.SuccOut/VS.DRD.RBSetup.AttOut x 100%
VS.HHO.AttInterCell.LB/VS.HHO.SuccInterCell.LB x 100%
The strategy application flow shows how an appropriate networking strategy is selected.
It helps you complete the strategy configuration.
As each RRU supports one band, to expand the capacity of an RRU, add the RRU and
antenna feeder system for the other band. Boards and resource groups in the baseband
are configured based on the number of cells.
In the preceding application scenario, one sector deploys two inter-connected RRUs.
Check whether the RRU power supports the new carrier. If not, add RRU for the new
carrier. Boards and resource groups in the baseband are configured based on the
number of cells.
Node B
RNC
Prepare at least one DPUe board for each subrack to support the rate of 42
Mbit/s.
For the BTS3812E, configure all the boards in one resource group, set the local cells of
f1 and f2 in enhanced boards.
For the DBS3900, run RESALLOCRULE: RULE=CAPAFIRST to set the b and d boards
work in load balance mode.