115808 Tri-Carrier BBU

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

6 | APPENDIX A: CONFIGURATIONS

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

6 | APPENDIX A: CONFIGURATIONS

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Introduction
• This feature introduces the configurations with three carriers inside the same eNodeB, with
three modems.
• The cells using the same carrier will have also the same bandwidth.
• The three carriers could belong to two or three bands
• The following bands are supported (other bands, not used in France, also supported, are not shown here)

Band Name Frequencies UL Frequencies DL Bandwidth

3 1800MHz 1805 MHz – 1880 MHz 1710 MHz – 1785 MHz 75 MHz
7 2.6GHz 2620 MHz – 2690 MHz 2500 MHz – 2570 MHz 70 MHz
20 800MHz EDD 791 MHz – 821 MHz 832 MHz – 862 MHZ 30 MHz

• The following Band/Carrier arrangements are supported:

 Bi-band case: 6 sectors- 9 cells configuration
 Tri-band case: 9 sectors-9 cells configuration
Bi-Band config: 6 sectors-9 cells Tri-Band config: 9 sectors -9 cells

Band z 3 sectors – 3 cells

Band y 3 sectors – 6 cells
+
+ Band y 3 sectors – 3 cells
+
Band x 3 sectors – 3 cells
Band x 3 sectors – 3 cells

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Benefit
This features allows co-locating up to three carriers on different LTE bands
within a single eNodeB.
So by covering an area with up to 3 carriers, we have:
 more spectrum available
 better load balancing

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Description
General case for the Tri-Carrier configuration:
CCM
eCCM2
bCEM #1
Bandwidth #1
Carrier #1

Bandwidth #1
Carrier #1

Bandwidth #1 RRH
Carrier #1 Carrier #1

RRH
Carrier #3

bCEM #2 RRH
Bandwidth #2 Carrier #2
Carrier #2
RRH
Bandwidth #2 Carrier #1
Carrier #2 RRH
Carrier #1

RRH
Bandwidth #2
Carrier #3
Carrier #2
RRH
Carrier #2

RRH
Carrier #2
bCEM #3 RRH
Bandwidth #3 Carrier #3
Carrier #3

Bandwidth #3
Carrier #3

Bandwidth #3
Carrier #3

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Description
• In case of the loss of one bCEM (board removed or locked by the
operator), an automatic reconfiguration based on carrier priority (if any)
occurs such that the carrier with highest priority, if it was lost, is recovered
through a bCEM reset and restart. (Note: this does not address loss of
bCEM due to transient failure)
• The feature is under a license (parameter isTriCarrierEnabled)
• It is only supported on modem bCEM and controller eCCM2

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Interaction
For field deployment perspective, this feature 115808 has no dependency with other
features.
There are some interactions with other features:
• PRB licensing (feature 110762) must be disabled. The configurations with more
than one bCEM require unlimited PRB.
This implies to have isUnlimitedPRBLicenseAllowed = TRUE
• eMCTA (evolved Multi-Carrier Traffic Allocation).
The functions governing Mobility Management (trigger, filtering, target carrier
selection, etc.) support the tri-carrier configurations introduced by 115808.
This implies adequate creation and provisionning of objects related with
eMCTA for the new frequencies.
• X2 Dynamic Configuration and ANR are impacted by the increased number of
managed cells.
This implies adequate creation and provisionning of objects related with
ANR for the new frequencies.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Interaction
• Carrier Aggregation. The dependency with 115808 is that both features use as a
basis the support of 3 bCEM HW configuration. However CA and Tri-Freq features
have two different bCEM-to-sectors mapping approaches. With CA, one sector is
covered by one Modem board, that will cover all three carriers; with 115808, one
carrier is covered by one Modem board, that will cover all three sectors. Both
features are mutually exclusive.
Carriers to bCEM mapping for Carrier Aggregation configuration:
Carrier 1 Carrier 2 Carrier 3
Sector α Sector α Sector α bCEM1

Carrier 1 Carrier 2 Carrier 3

Sector β Sector β Sector β bCEM2

Carrier 1 Carrier 2 Carrier 3

Sector γ Sector γ Sector γ bCEM3

Carriers to bCEM mapping for Tri-Carrier configuration:

Carrier1 Carrier1 Carrier1
Sector α Sector ß Sector γ bCEM1

Carrier2 Carrier2 Carrier2

Sector α Sector ß Sector γ bCEM2

Carrier3 Carrier3 Carrier3

Sector α Sector ß Sector γ bCEM3

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Interaction
• ACC (Antenna Cross Connect) : The “Antenna Cross Connect” feature avoids losing one
sector in case of RRH failure: each RRH serves one TX/RX path for two sectors. In case of
RRH failure, the eNodeB defense will change the diversity path of a remaining RRH into main
path for the affected sector.
Antenna Cross Connect between RRH:

For 115808 Tri-Freq config, Antenna Cross Connect configurations are supported at carrier
level; this implies the possibility having mixed configurations at eNB level: one carrier could
be ACC, the others not ACC.
Note it is not possible to use the same RRH with two carriers and ACC in the same time.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Interaction
• 166802 – eNB SW Capacity LR13.3.
With 166802 (and OOT), eCCM2 supports 1800* connected users per eNodeB ; bCEM
supports 800 connected users per cell;
With Tri-Freq configuration we can have at maximum 9 cells on the eNodeB.
So bCEM capacity with Tri-Freq configuration is capped by eCCM2 capacity.
 800 connected users per cell if the sum on all cells remains below eCCM2 capacity
 200 (=1800/9) connected users per cell simultaneously;
*: will be 2400 at CL4

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

6 | APPENDIX A: CONFIGURATIONS

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

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

• To keep the feature deactivated:

Enb.ActivationService.isTriCarrierEnabled = FALSE
For all LTECell :
Enb.LteCell.dedicatedConfId = DedicatedConf/0
Enb.LteCell.enbRadioConfId = EnbRadioConf/0
Enb.LteCell.enbVoipConfId = EnbVoipConf/0
Enb.LteCell.FrequencyAndBandwidthFDD/multiCarrierPriority = 9

• This feature does not bring non-iso functionality after upgrade

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

6 | APPENDIX A: CONFIGURATIONS

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Activation Strategy
Possible Configurations

The following 3 configurations (Config1, Config2, Config3) are possible:

Band Name Configuration Config1 Config2 Config3 RF configuration

3 1800MHz Single – carrier 20 MHz 15 MHz 20 MHz MC TRDU and 2 Rx antenna, 1 CPRI link
7 2.6GHz Single - carrier 20 MHz 15 MHz 20 MHz RRH and 2 Rx antenna, 1 CPRI link
20 800MHz EDD Single - carrier 10 MHz 10 MHz TRDU and 2 Rx antenna, 1 CPRI link

Dual Band configuration

Hardware only two bCEMs requested

Rack: D2Uv5 (3JR37526AA)

Controller: eCCM2
Modem: bCEM P1.1
(3BK28961CA)
RUC: -48VDC – (3JR37517AE)
Antenna Configuration: 2T2R
CPRI/HSIQ rate: 3 (maximum 1
carrier 20MHz with 2Rx)

Note: the creation of a Tri-Freq Config (from mono-freq or from bi-freq) implies an
outage of the eNodeB.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
 Activation Strategy
Impact on RAN Model

Enb

[1..3] [1..3] [1..3]

EnbVoipConf
ActivationService LteCell DedicatedConf EnbRadioConf EnbVoipConf

isTriCarrierEnabled dedicatedConfId
enbRadioConfId
enbVoipConfId

FrequencyAndBandwidthFDD/TDD

multiCarrierPriority

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Activation Strategy
Pre-requisites for feature activation (1/4)
1. Requirements on Core Network: none
2. Requirements on User Equipment:
ue-Category - at least category 2 (and for the configurations with 4 Rx category 4).
SupportedBandListEUTR A (as defined in TS 25.101) must contain the support of the
bands.
3. Requirements on EUTRAN HW:
It must be a d2UV5 rack with three bCEMs and eCCM2 controller, every bCEM supporting
one carrier. This feature does not allow mapping cells with different carriers or bandwidths
on the same bCEM.
The CPRI/HSIQ rate for supporting all tri-freq configurations is 3 (even if some
configurations could be done at CPRI rate 5).
4. Requirements on other EUTRAN features to be activated/deactivated:
isUnlimitedPRBLicenseAllowed must be TRUE
isCarrierAggregationEnabled must be FALSE

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Activation Strategy
Pre-requisites for feature activations (2/4)
5. EUTRAN Configuration:
• ENBEquipm ent::m ax TransportFiberDelayLengthCategory .
Transport Fiber Delay Length Category must be the same for all RRH (tenKm or fifteenKm
or for all TRDUs (tenKm) -> tenKm (between 0 and 10Km) is to be used, imposed by the
presence of TRDUs.
• Create new instances for DedicatedConf, EnbRadioConf and EnbVoipConf Mos (only
if required to have different settings per Carrier)
• Make the LteCell M O reference the instances above appropriately (dedicatedConfI d,
enbR adioConfI d and enbVoipConfI d )
• Datafill the m ultiCarrierPriority in FrequencyAndBandw idthFDD/ TDD MO,
according to the wished strategy. Lowest possible priority is 9, highest is 0. All cells of the
same frequency must have the same priority.
• Datafill carefully:
CpriR adioEquipm ent::AntennaPort ,
LteCell::CellAntennaPort ,
LteCell::LteCellFDD
(see Appendix)
• Set isTriCarrierEnabled to TR UE

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Activation Strategy
Pre-requisites for feature activations (3/4)
• Impact for eMCTA configuration :
For each new frequency
• Mandatorily create one new instance
RrmServices.UeMeasurementConf.MeasObject.MeasObjectEUTRA (datafill dlEARFCN with the one
corresponding to the new frequency).
• Optionally create new instances for RrmServices.UeMeasurementConf.ReportConfigeUTRA (for intra
freq report config and for inter freq report config); this is optional in the sense they may also be
mutualized between all frequencies.
• Mandatorily create one new instance RrmServices.UeMeasurementConf.RrcMeasurementConf and
new instances RrmServices.UeMeasurementConf.MeasurementIdentityConf (that will point to the
relevant MeasObject of the new frequency).

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Activation Strategy
Pre-requisites for feature activations (4/4)
• Impact for eMCTA configuration (cont’d):
• Mandatorily add as many LteNeighboringFreqConf as new frequencies
• Configure the MobilityPriorityTable accordingly to the frequencies deployment strategy (priority of
freq based on services, based on QCI, ...).

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

6 | APPENDIX A: CONFIGURATIONS

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Performance Evaluation
Performance Monitoring
• PM Counters:
A new counter 13261 is added with 3 screenings:
• Screening-0 – 13261-1 – VS.NbRrcConnectedUsersPerCarrier.Carrier1 (with lowest dlEARFCN)
• Screening-1 – 13261-1 – VS.NbRrcConnectedUsersPerCarrier.Carrier2 (with next dlEARFCN > lowest dlEARFCN)
• Screening-3 – 13261-2 – VS.NbRrcConnectedUsersPerCarrier.Carrier3 (with next dlEARFCN > precedent dlEARFCN)

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Performance Evaluation
Performance Monitoring
Domain to assess:
• ANR
• Check the ANR for Inter Freq Neighbors

• eMCTA and Load Balancing

• Check the inter-frequency HO Success Rate : VS_HO_IrF_xxxx_rate
• Check the Inter-frequency Load Balancing behaviour

• Retainability
• ERAB Drop rate and UE Context Drop rate

• Capacity :
• counter #13261 on each frequency

• Throughput UL and DL :
• check that peak throughput per cell is maintained : VS_cell_thpt_ul_xxxx, VS_cell_thpt_dl_xxxx

• Note: having the tri-freq deployed in a dense urban area is required to assess the spectrum capacity
gain (offload of the two others frequencies).

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Performance Evaluation
Performance Monitoring
Monitor the following KPIs, on the whole eNodeB and on each Frequency separately, with a
focus on the new frequency 1800 MHz.

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

L12105_2 VS_ERABs_NonGBR_RLC_PDU_UP_KiByte_DL
TRAFFIC DL RLC Layer NonGBR
L12106_2 VS_ERABs_NonGBR_RLC_PDU_UP_KiByte_UL
UL RLC Layer NonGBR
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
Drive tests
• along a route made of contiguous tri-carrier sites
• along a route made of discontiguous tri-carrier sites
Perform
• UL traffic
• DL traffic
Measure :
• throughput performance,
• mobility intra-freq and inter-freq success rate,
• the cell selection and reselection in idle state.

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

6 | APPENDIX A: CONFIGURATIONS

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

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

This feature enables co-location of different carriers on the same LTE band
or on different LTE Band within a single eNB, when spectrum available in
one carrier is not sufficient.
A capacity gain is expected, considering the third frequency will allow to
offload the two other frequencies.

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

6 | APPENDIX A: CONFIGURATIONS

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

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

Cabling and datafilling CpriR adioEquipm ent::AntennaPort , LteCell::CellAntennaPort ,

LteCell::LteCellFDD :
Sector, Cell and Radio Equipment relations are reminded below.
Some rules must be followed in the definition of these objects like:
CellAntennaPort:rxPath .AND. CellAntennaPort::txPath = FALSE
CellAntennaPort:rxPath .OR. CellAntennaPort::txPath = TRUE
CellAntennaPort number of instances for one LteCell = LteCell:LteCellFDD:numberOfDLAntennas +
LteCell:LteCellFDD:numberOfULAntennas
LteCell:sectorNumber is deduced from LteCell:CellAntennaPort:antennaPortId:sectorId

ENBEquipment

eNB

LteCell
Sector CpriRadioEquipment
- uniqueName
- sectorNumber
- ...

LteCellFDD CellAntennaPort AntennaPort

CellAntennaPort AntennaPort
- numberOfDLAntennas CellAntennaPort
- antennaPortId AntennaPort
- antennaPortIndex
- antennaPortId - antennaPortIndex
- numberOfULAntennas - antennaPortId
- rxPath - antennaPortIndex
- sectorId
- rxPath - sectorId
- cellCapability2x2Mimo - rxPath
- txPath - sectorId
- assignedTransceiverPort
- txPath - assignedTransceiverPort
- cellCapability4x4Mimo - ...- txPath - assignedTransceiverPort
- rxUsed
- ... - rxUsed
- ... - ... - rxUsed
- txUsed
- txUsed
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. - -...-...txUsed
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
- ...
Configuration

CPRI connections should be executed as in picture bellow, antennas are 2T2R

bCEM HSIQ eCCM2 CPRI

RRH

TRDU

TRDU

bCEM
RRH

TRDU

TRDU

bCEM
RRH

TRDU

TRDU

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Configuration
Antenna Port mapping :
AntennaPort
Assigned CpriRadioEquipment
Sector Band
rdnId Transceiver txUsed rxUsed rdnId
Id
Port
1 1
True True 1 1 1
2 2
1 1
True True 2 2 1
2 2
1 1
True True 3 3 1
2 2
1 1
True True 4 4 2
2 2
1 1
True True 5 5 2
2 2
1 1
True True 6 6 2
2 2
1 1
True True 7 7 3
2 2
1 1
True True 8 8 3
2 2
1 1
True True 9 9 3
2 2

Cell Antenna Port setting.

rdnId Description txPath rxPath antennaPortId
Configure all Lte Cell the same way (pointing
LteCell 1
respectively on CpriRadioEquipment 1, 2, up to 9).
0 First Rx path False True CpriRadioEquipment_1/AntennaPort_1

1 First Tx path True False CpriRadioEquipment_1/AntennaPort_1

2 Second Rx path False True CpriRadioEquipment_1/AntennaPort_2

3 Second Tx path True False CpriRadioEquipment_1/AntennaPort_2

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION