CARRIER AGGREGATION

Implementation Simple Guidance

SW18 (FL18 | SRAN18 | TL18)

Confidential
CEM Insight / NPO Team - Dodi & Fani / April 2017
© Nokia 2017
Carrier Aggregation Configuration

CA feature Enable (True)

- actDLCAggr
- actInterEnbDLCAggr
- For master and Slave

Confidential
© Nokia 2017
Carrier Aggregation Configuration

Parameter object related (LNBTS) CAGENB

- actDLCAggr -> Create object CADPR
- actInterEnbDLCAggr -> check CAGENB ->
define eNb List Cluster

CADPR
CAGENB -> create -> eNB List CA Cluster

CAGENB -> create -> eNB List CA Cluster

- MRBTSID 278446 (Target MRBTSID)
- SRIO (0 – using airscale)
- SRIO (1 – using fsmf <-> fsmf)

Confidential
© Nokia 2017
Carrier Aggregation Configuration

Parameter object related (LNBTS) : L2300

- Define caClusterId (must same both MRBTSID
source/master <-> target/slave
- Define caClusterMemberId (Master
=1, target=2, … )
- caSchedFairFact = 1
- caClusterId must use unique ID

L1800
MRBTSID
caClusterMemberId
master : 1
caClusterMemberId
slave 1 = 2
caClusterMemberId
slave 2 = 3
L1800
L2300 MRBTSID
MRBTSID

Confidential
© Nokia 2017
Carrier Aggregation Configuration

Parameter object related (Lncel ) :

- Create CAPR From source (38750) ->
- Create CAREL with configuration Target (1875)
Beamforming in Scell (Blank) Due to CA Config 2CC 
EnB parent (enb for slave/target CA) FDD L1800 with TDD 2300
cell resource id (source <-> target same sector)
MaxNumOfSuppMIMOLayer

Please do the same for other sector

Cell resource from sector 1 -> target

sector 1 (LncelId 11)

MaxNumOfSuppMimoLayer 4-layer due to

target TDD 2300 already using MIMO 4x4

Confidential
© Nokia 2017
Carrier Aggregation Configuration

L2300 L1800
MRBTSID MRBTSID

CA PoolId :Same Sector Source <-> Target must using

same CaPoolId
Sector 1 L2300 & L1800 -> 11
Sector 2 L2300 & L1800 -> 21
Sector 3 L2300 & L1800 -> 31

Confidential
© Nokia 2017
Carrier Aggregation Configuration

Parameter related Carrier Aggregation must be configure :

dlCaCqiWindow = 50ms
dlCaMinPcellCqi = 0
dlCaMinPcellCqiQci1 = 0
ulCaMinPcellSinr = 0
ulCaMinPcellSinrQci1 = 0
ulCASinrWindow=50ms
scellFastSchedulingSelect = normal

Note : value parameter adjustable

Jika FSMF-AS TL2300, maka FSTSCH LTE-U di pdate spshaping nya jadi
3300

Additional Parameter for 3 CC :

maxNumCaConfUeDc = 50
maxNumCaConfUe3c = 50
sCellActivationMethod = nonGBRBufferBasedStepWise
nPucchF3Prbs = 2
maxNumScells = 2

Confidential
© Nokia 2017
Check CA

Go to PM/Performance Management in L1800

Wait for 15 minutes after activate done and No Alarm related CA
Check counter C8011C68 or SCELL_CONFIG_SUCC

Confidential
© Nokia 2017
Problem Found : 0 CA Attemp in Master site

Go to Slave site
Check Sync  btsSyncMode: phasesync
Check Clock  syncInpputtype: 1pps from sync
hub
If sync use phasesync need to create TOPP and
fill parameter:
maxBscTimeError = 50 (GNBCF)
maxBtsTimeError = 1500 (LNBTS)
maxBtsTimeError = 500

Confidential
© Nokia 2017
Problem Found : x2 link unavailable

 Check -> maxNumOfLnadjLimit

If config still 128 relation change to 256
LNADJ relation
 On LNADJ -> Delete all LNADJ
(before delete make sure ->
actUeBasedAnrInterFreqLte = 1 &
actUeBasedAnrIntraFreqLte = 1)
LNADJ will be automatic creation if
both parameter true (1).

maxNumOfLnadjLimit -> change to 200

(max config 256 relation)

Delete All LNADJ

Confidential
© Nokia 2017
Problem Found : Inter eNB CA Parameter(s) inconsistency between EnBs

 Make sure parameter related Carrier

Aggregation already proper
(caClusterId | caClusterMemberId |
caSchedFairFact | CaPoolId.. Etc)
 Change
manualFrameTimingAdjustment = 31
 to 0
 Change TotalDelayFromSHM from 31s
 to 47 ns
 Alarm Clear  CA Working Properly

Confidential
© Nokia 2017
Physical cable Connection Related Synchronization inter MRBTS

FSMF – FSMF Airscale – FSMF Airscale – Airscale

(max +/- 50 ns
phase error)
sync
sy /- 50 nor)
(m has
ax e e
p

n
+

c
rr

s
Confidential
© Nokia 2017
Sync Hub inter MRBTS

eNodeB (Sync Master) eNodeB (Sync Master)

SW – FL18A SW – SRAN18A
Example : MRBTS Master using GPS as clock Example : MRBTS Master using TOPF as clock
reference reference

Confidential
© Nokia 2017
Sync Hub inter MRBTS

eNodeB (Sync Slave) eNodeB (Sync Slave)

SW – FL18A SW – SRAN18A
Confidential
© Nokia 2017
Sync Hub inter MRBTS – Clearing Error

Modify Parameter for Slave MRBTS

for Clearing Error :
After Configure btsSyncMode to
PhaseSync will be occur some error
due to missing some parameter &
need modify for clearing.
PhaseSync -> need Object TOPP

Confidential
© Nokia 2017
Sync Hub inter MRBTS - Clearing Error

Modify Parameter for Slave MRBTS

for Clearing Error :
maxBscTimeError=50
GNBC -> maxBtsTimeError = 1500
LNBTS -> maxBtsTimeError = 500

Confidential
© Nokia 2017
Sync Hub inter MRBTS – Clearing Error

Modify Parameter for Slave MRBTS

for Clearing Error :
Add Object TOPP

eNodeB (Sync Slave)

Confidential
© Nokia 2017
 Check Status Synchronization

SW FL18 – Slave

SW SRAN18 – Slave (source from sync Hub

master)

From capture synchronization – both site

already using clock from master/source
MRBTS (synchronization OK).

Confidential
© Nokia 2017
Activation Summary Carrier Aggregation

InterEnb Carrier Aggregation Step :

1. Synchronize inter System Module/MRBTS -> if no synchronize CA InterEnb not working.
2. Modify Parameter Carrier Aggregation -> Make Sure no missing modify parameter both Target <->
Source (if there is missing parameter will be occurred Alarm related CA & CA not working)

Confidential
© Nokia 2017
Lesson Learn
1. Alarm inconsistent CA
Need check CAREL, CAGENB, caClusterid ( unique id), caClusterMemberId

Parameters below must be the same as the site pair in CA

actInterEnbDLCAggr , actDLCAggr , actFlexScellSelect , sCellDeactivationTimerEnb ,caSchedFairFact

LNCEL: caPoolId , cqiPerSbCycK , periodicCqiFeedbackType , riEnable , riPerM
cellResourceSharingMode , actSuperCell

2. No CA attempt and parameters CA in accordance with the guideline, need try Disable – Enable
actInterEnbDLCAggr.

3. Inter-Site CA Link Establishment Failure alarm usually occurs in Inter site using X2 connection.
the suspect in TDD site, the BTS not enabled automatically after recovery from X2 link failure. Update SW
in TDD site to TL18A 3.1 and do CA activation again.

4. Inter-Site CA X2 link unavailability alarm, do the deletion LNADJ on this BTS and pair. After LNADJ add
automatically check the status of LNADJ.

5. No CA alarm but CA not working, Check Sync setting, Check parameters in point 1 above, do reset site if
needed
Confidential
© Nokia 2017