Wrong SCF and Radio Module Detection

By: Panji Ryan W

A Dump could give us information how configuration file implemented on sites. We are able to
detect from all sites on air, which sites are having a radio module problem and wrong SCF implemented
on a sites. Base from my experience, many new sites using another SCF that shouldn’t be applied to that
site. This is not allowed because every sites and cells are having unique parameter configuration such as
physical cell id (PCI) and root sequence index (RSI).

Let’s have take a look how we can diagnose it from dump database.

1. Open last dump and copy LNCEL, LNCEL_PS, LNCEL_SIB to excel file

2. On sheet LNCEL just insert column D,E, F, and G to compare cell name between dump and
planning database. Column F and G is a comparison between enodeb name mrbtsid with cellname
dump. Snapshot below is an example wrong SCF implementation on site.

From above data, suspect site NBDG_0119 is using the same SCF with site NBDG_0123, to prove this
and make us confidence let’s check PCI and RSI configuration, also we can check TAC but sometimes TAC
information already match with the plan. I’m afraid if only TAC is correct because it could be there was
someone else make change request only for TAC parameter while it was a wrong SCF, or could be another
reason.
 3. Same RSI data , while in planning database is using 320,300,310

4. Same PCI data, while in planning database is using 111,112,113

5. Same condition with another site, SCF site NBDG_0104 is using SCF for NBDG_0373

6. Same PCI data

After we are collecting all sites that using another SCF, what should we do is resend SCF to
implementer to recommissioning those sites with new/update SCF. Hopefully recommissioning could be
done successfully otherwise will impact to quality and accessibility.
 Another problem related to radio module also can be detected in LNCEL by parameter riEnable
and in dlmimomode on LNCEL_PS.

riEnable should be 1 ,if it 0 means there is less module that should be installed or activated on
sites. To confirm this, check availability and if it already OA also can be checked from BTS Snapshot. In
FDD mode usually using minimum 2 FXCA (radio module) to have 2X4 MIMO configuration, and TDD mode
uses 3 FZNI. Also on parameter dlmimomode should be 30 (dynamic open loop MIMO 2X2), 40 (close loop
MIMO 2x2), or 41 (close loop MIMO 4x2) , if it 0 means only use single Tx and no MIMO activation.
Some notes to find few parameters related to this case :
phyCellId on A_LTE_LNCEL_PS

rootSeqIndex on A_LTE_LNCEL

TAC on A_LTE_LNCEL_SIB

administrativeState on A_LTE_LNCEL or in LNBTS with information from 0 until 5

0 = initializing

1 = commisioned

2 = not commisioned

3 = configured

4 = integrated to RAN

5 = ONAIR

Once we have found wrong SCF implementation, just resend SCF BTS only or update it to
implementer ex: NIC to be recommissioned. Also check Ip Mplane in dump whether already match with
MRBTS plan or not, can be found on A_LTE_IVIF (see picture below). While for less radio module
activation, escalate it as soon as possible to project team to fix the problem.
Ip Mplane can be found on column localIpAddress with QoS Enable = 0.

Other Info Join

http://t.me/npotelekom
http://bit.ly/belajarRF