L115401 Nine cells (One Frequency) support in three modems

LR13.3 ORF Workshop

Presenter: Priscille COCHOIS
October 9th, 2013
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
AGENDA

1 | FEATURE DESCRIPTION

2 | UPGRADE RULES

3 | FEATURE ACTIVATION STRATEGY

4 | PERFORMANCE EVALUATION

5 | CONCLUSION

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
1 | FEATURE DESCRIPTION

2 | UPGRADE RULES

3 | FEATURE ACTIVATION STRATEGY

4 | PERFORMANCE EVALUATION

5 | CONCLUSION

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Description - I ntroduction
This feature introduces the support of up to 9 Cells (same band, same
frequency, same bandwidth) on one eNb, with the usage of up to 3
modems.

This solution addresses hot spots, stadiums, … where huge capacity is

required to be deployed in a short time.

This solution :
 provides an increased capacity
 is cost effective
 is less time consuming
than the usual approach of adding new eNb.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Description – New topologies
New supported topologies :
• With 2 bCEMs (up to 6 cells), 1 eCCM (or 1 eCCM2) :
• 6 sectors – 1 site
• 6 sectors – 2 sites

• With 3 bCEMs (up to 9 cells), 1 eCCM2 :

• 9 sectors – 2 sites
• 9 sectors – 3 sites
• 9 sectors – 9 sites

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Description – I m pact on RF Algorithm s
Having more than 3 cells on one frequency requires adaptation in the
following RF algorithms:
• Automatic PCI allocation
• PRACH parameter (Prach-ConfigIndex) planning
• UL reference sequence index (RSI- RootSequenceIndex) planning
See more details in the next slides.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Description – I m pact on RF Algorithm s
Autom atic P CI allocation
• In pre-LR13.3, the “automatic PCI allocation” interference rule consists in checking that, for a
given frequency, two cells of an eNB use different PCI modulo 3 values.
• With more than 3 cells on one frequency, it is not suitable anymore.
• The feature L115340 “Support of Automatic PCI for 6 sectors Configuration” changes the rule
in order to support up to 9 cells on the same frequency: the interference rule consists now in
checking that, for a given frequency, two cells of a site [i.e with same cellSiteNumber],
identified as adjacent [adjacencies is determined based on cells azimuth values], use different
PCI modulo 3 values
• Example : 9 cells in a “9 sectors-two sites” configuration; PCI from 31 to 39 => [PCI Modulo 3]
= 0, 1, or 2.

cellSiteNumber = 1 cellSiteNumber = 2
With the pre LR13.3 implementation:
0 0 The algo would trigger an interference alarm and would not
1
be able to solve it
2 With the LR13.3 implementation:
2
2 1 With correct setting of cellSiteNumber and azimuth, the
algo manages to reach an allocation of PCI which does not
1 0
trigger interference alarm.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Description – I m pact on RF Algorithm s
P RACH-ConfigI ndex
• The Prach-ConfigIndex (sent by the eNb in the SIB2 and in the mobility control information) indicates the
RACH preamble timing to be used by the UEs in the Cell (3GPP 36.211).
• 3GPP requirements, in addition to our implementation (we have one single pRACH detector per modem)
impose that the cells handled by one Modem have distinct Prach-ConfigIndex.
• In legacy configurations, the Prach-ConfigIndex is based on the sector Number
• if LteCell.spare5 bit31 is 0, the LteCell sector Number is the one assigned at commissioning (in the
AntennaPort.sectorId).
• if LteCell.spare5 bit31 is 1, the LteCell sector Number is derived from the azimuth and beamwidth
configured in the AntennaPort.
• For the new configurations supported by L115401, the use of such sector Number is not suitable (e.g
several cells handled by one modem may have the same azimuth and beamwidth).
A new algorithm is implemented “modem_based”, as follows:
• There is one pool [1,2,3] of sectorNumber for each modem board.
• The sector number(1, 2 or 3) is allocated to one cell during cell setup and the sector number is freed when
cell is deleted. The smallest available number is allocated to new cell.
• A new parameter Enb::pRachIndexAlgorithm designates the algorithm to be used by the eNodeB at cell
setup (legacy_based or modem_based).

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Description – I m pact on RF Algorithm s
RootSequenceI ndex
• The RACH rootSequenceIndex is broadcasted in the SIB2 and is used by the UEs to generate their RACH
preambles sequences.
• rootSequenceIndex is based on parameter autoRSIConfigEnabled.
When set to false, rootSequenceIndex is derived from CellRachConf::rootSequenceIndex parameter
manually configured.
When set to true, rootSequenceIndex is derived automatically based on PCI and cell size:
RSI = C1 + mod(floor(PCI/3)×N, C2) [Before LR13.3]
RSI = C1 + mod(floor(PCI)×N, C2) [From LR13.3]
where: [C1, C1+C2] is the pool of RSI allowed to be used, N is related with Cell Size.
In order to avoid different cell using the same RSI, the RSI calculation now uses PCI instead of PCI/3.
This is to enhance RACH communication.
(The new formula is not used only for the new topologies with “up to nine cells (one frequency”). It applies by
default in LR13.3. for all configurations)
Note also that it is not mandatory to have autoRSIConfigEnabled = True for the new topologies with “up to
nine cells (one frequency”). We still can have rootSequenceIndex manually configured.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Description - License
This feature is under a license.
The parameter allowing the usage of this feature is :
Enb.ActivationService.isIncrementalSectorEnabled.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Interaction
• L115340 – Support of automatic PCI for 9 sectors configuration gives the
framework for automatic PCI configuration for topologies with up to 9
sectors. Parameter cellSiteNumber is introduced in the scope L115340.
L115401 depends on L115340 to solve PCI configuration issue for 9
sectors.
• ANR is impacted by the increased number of managed cells. Call Trace also
is adapted to be able to trace more than 6 cells per eNB.
• The configurations Dual Band/Carrier (FRS L115616/L115938), Tri Carrier
(FRS L115808), Carrier Aggregation (FRS 160847) are not compatible with
FRS115401 and must be disabled when isIncrementalSectorEnabled is
TRUE.
• 166802 – eNB SW Capacity LR13.3. The capacity of ‘up to Nine Cells (one
frequency)’ configurations are inline with 166802 capacity targets,
meaning: we are able to reach the peak number of users in any cell, up-to
the maximum capacity of the controller (eCCM/eCCM2).

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
1 | FEATURE DESCRIPTION

2 | UPGRADE RULES

3 | FEATURE ACTIVATION STRATEGY

4 | PERFORMANCE EVALUATION

5 | CONCLUSION

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Upgrade Rules

• To deactivate the feature, the parameter

Enb.ActivationService.isIncrementalSectorEnabled should be set to
“false”.
• To keep legacy algorithm for PrachIndex , the parameter
Enb.pRachIndexAlgorithm should be set to legacy_based or kept absent.

• Non-iso functionality after upgrade : Root Sequence Index calculation is

changed (if autoRSIConfigEnabled is True)

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
1 | FEATURE DESCRIPTION

2 | UPGRADE RULES

3 | FEATURE ACTIVATION STRATEGY

4 | PERFORMANCE EVALUATION

5 | CONCLUSION

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Activation Strategy
Pre-requisites for feature activation

1. Requirements on Core Network: none

2. Requirements on User Equipment: none
3. Requirements on EUTRAN HW:
It must be a d2UV5 rack with up to three bCEMs, every bCEM supporting up to 3
cells.
For 3 bCEMs configurations, eCCM2 controller is mandatory, else eCCM is
enough.
4. Requirements on other EUTRAN features to be de-activated:
Feature 115938: isDualCarrierEnabled must be FALSE
Feature 115808 : isTriCarrierEnabled must be FALSE
Feature 160846 and 160847 : isCarrierAggregationEnabled must be FALSE
Feature 110762 (PRB Capacity Limitation): isUnlimitedPRBLicenseAllowed must
be TRUE
5. Requirements on other EUTRAN features to be activated:
Feature 156783 : isAisgAllowed must be TRUE
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Activation Strategy
Pre-requisites for feature activation
6. EUTRAN configuration:
Properly configure the coordinates, which is used for PCI allocation (if automatic PCI allocation
is used):
• Latitude – given by LteCell.mainAntennaConfiguredPositionLatitude
• Longitude – given by LteCell.mainAntennaConfiguredPositionLongitude
• Altitude - given by LteCell.mainAntennaConfiguredPositionAltitude
• Radius – given by LteCell.cellRadius
• Site number – given by LteCell:cellSiteNumber – number from 1 to 9
• Azimuth – given by AntennaPort.azimuth
• Horizontal beam width – given by AntennaPort.horizontalBeamwidth
• Vertical beam width - given by AntennaPort.verticalBeamwidth

Properly configure ENBEquipment::maxTransportFiberDelayLengthCategory

• between 0 and 10Km : tenKm
• between 5 and 15Km : fifteenKm
In case of TRDUs usage, tenKm category must be used.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Activation Strategy
Feature activation

The feature is activated with:

• ActivationService.isI ncrem entalSectorEnabled = TR UE

This parameter activates or deactivates the capability to configure up to nine
cells same carrier and bandwidth when up to three different bCEM are used.
Parameter isI ncrem entalSectorEnabled
Object ENBEquipment / Enb / ActivationService
Range & Unit Enumerate
[False, True]
Class / Category Class B – customer settable
Value False (Default) / True to activate the feature

• Enb.pR achI ndex Algorithm = m odem _based

This parameter specifies the algorithm to be used by the eNodeB to determine
pRachConfigIndex value. If unset the value legacy_based will be used.
Parameter pR achI ndex Algorithm
Object ENBEquipment / Enb / ActivationService
Range & Unit Enumerate
[legacy_based, modem_based]]
Class / Category Class B – Cell / System-Restricted
Value Legacy_based (Default) / modem_based for configurations between
4 and 9 sectors same carrier on up to three modems.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
1 | FEATURE DESCRIPTION

2 | UPGRADE RULES

3 | FEATURE ACTIVATION STRATEGY

4 | PERFORMANCE EVALUATION

5 | CONCLUSION

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Performance Evaluation
Performance Monitoring

This feature does not introduce new counters.

The usual KPIs must be monitored to assess the performance of the new supported
configurations, to be monitored especially during ‘special events’ (situations where traffic
get huge and concentrated, like in a stadium, …), in order to assess the capacity benefit.
DOMAIN KPI Reference Longname
ACCESSIBILITY RRC Connection Failure Rate L12302_21_CI VS_RRC_cnx_fail_rate
RRC Connection Blocking Rate
UE Context Setup Failure Rate L12501_21_CI VS_UE_ctxt_setup_fail_rate
Total ERAB Setup Failure Rate L126a2_21_CI VS_ERABs_all_setup_fail_rate
RETAINABILITY RRC Connection Drop Rate
Context Drop Rate L125a2_31_CI VS_UE_ctxt_drop_rate
Total ERAB Drop Rate L12608_21_CI VS_ERABs_all_drop_rate
THROUGHPUT DL L1 Cell Tput L12030_30_CI VS_cell_thpt_DL_avg_PerCell
UL L1 Cell Tput L12031_30_CI VS_cell_thpt_UL_avg_PerCell
QUALITY Downlink Residual BLER L12707_30_CI VS_BLER_DL_all
Downlink Initial BLER L12708_30_CI VS_BLER_initial_DL_all
Uplink Residual BLER L12709_30_CI VS_BLER_UL_all
Uplink Initial BLER L12710_30_CI VS_BLER_initial_UL_all
MOBILITY all Intra LTE inter-cell Handover Success Rate L127b1_10_CI VS_HO_IrC_IaLTE_succ_src

TRAFFIC DL RLC Layer NonGBR L12105_2 VS_ERABs_NonGBR_RLC_PDU_UP_KiByte_DL

UL RLC Layer NonGBR L12106_2 VS_ERABs_NonGBR_RLC_PDU_UP_KiByte_UL

CAPACITY Average RRC Connected Users L13201_40_CI VS_UE_RRC_connected_avg_ForAllCells
Maximum RRC Connected Users L13201_Max_CI VS_UE_RRC_connected_max
L13201_Max_30_SI VS_UE_RRC_connected_Tmax
UL Noise Ue_with_0dB_Power_Headroom L13006_0 VS_PwHeadroom_normalized_UL_Lo
Avg_UL_Noise_per_PRB_GPxx L12027_xx_OD VS_noise_PRB_groupxx_UL_Lo_OD

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Performance Evaluation
E2E testing
Suggested non-regression E2E tests:
• Inter eNodeB mobility
• Intra-eNodeB mobility: H/O interruption time (C-plane & U-plane) and H/O
success rate must be inline with reference.
• DL and UL Throughput : performances must be inline with reference.
• Automatic PCI allocation and PCI conflict detection (in order to test the
interaction with L115340).

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
1 | FEATURE DESCRIPTION

2 | UPGRADE RULES

3 | FEATURE ACTIVATION STRATEGY

4 | PERFORMANCE EVALUATION

5 | CONCLUSION

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Conclusion
The feature introduces 6-sectors and 9 sectors topologies for which we
expect a capacity gain (compared to a 3 sectors topology), which is
particularly suitable for high traffic places like stadiums, hot-spots, …
It also allows to concentrate activities (maintenance, monitoring, …) on one
eNodeB instead of several ones (multi-site capabilities).

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION