Introduction:

Besides, our daily remote OSS-O&M job the OSS permit us further
options to monitor, trace specific faults and maintenance under all
connected network elements (NE) such as RNC and BSC.
Broadly using all possibility features on OSS platform improve
addressing real-time faults allowing fast response in remote O&M
action. Additionally, supporting field intervenor able to be more
specific in finding root cause analysis (RCA) and improved taken
action during site intervention both in CM&PM activates.
2G PARTIAL SITE SOLUTION:
1.By Exporting OSS-BSS real-time alarm:<Batch file already prepared to
be shared upon your request>.
2G Sites shown on BSC with alarm slogan on its DUG/RRUS as BTS
INTERNAL AFFECTED or PERMANENT FUALT, are not operational. Remote OSS
BSS system troubleshooting clears such fault exist in all RBS.
Faults generally shown on BSC as BTS INTERNAL AFFECTED or PERMANENT
FUALT may raise in different causes under RBS. BSC generated fault
code should be mapped in finding where the specific RBS fault raised.
Generally, those DUG/RRUS raised faults can be managed remotely.
Currently, such faults exist almost in all SR BSC’s. Which, can be
managed remotely and planned for site intervention incase repeated
occurrence on same DUG/RRUS.
2.Following Daily 2G TCH Cell Availability Report:
Both 900 and 1800 technology 2G cells under same RBS 24Hrs performance
supposed to be approximately equal. Deviation shown in a/some cell
among others directly related with TRX, RRUS or DUG operational state.
Using Command RXCDP – Radio X-ceiver CONFIGRATION DATA print status of
TRX/TS slot operational status under a Managed Object (MO) with
specific DUG Transceiver Group (TG). TRX with UNUSED or BLOCKED
operation state lost its Configuration Data instead being keep CONFIG
state.
Resetting DUG with TRX CONFIGRATION DATA state UNUSED or BLOCKED
result TRX hold CONFIG operational state and able to carry traffic
then.
As far as we know resetting activities in some groups done regularly
and which is appreciated. But yet we don’t go further what the root
cause analysis (RCA) behind why those TRX lost its CONFIGRATION DATA.
If we follow-up regularly most of TRX need reset operation generate
from same Managed Object (MO). So, Gap be minimized if RCA well done
before re-setting.
In the meantime, Closer follow-up especially with those frequently
change in TRX Configuration Data after reset. Site with such
behavioral issue should be include under site intervention action plan
and be see together site technician.
3.2G Down while 3G Working:
In mixed mode, rural or road access site type, designed both 2G and 3G
under one RRUS 900 band only. In such case GPS Sync Out defined on 3G
DUW digital unit. In any ways, GPS Sync mis-configuration either one
of its sides results lost in synchronization between DUW to DUG
communication resulting RRUS out servicing.
Rarely exist but could have a probability to occur anytime whenever
DUW formatted due frequently script lost nature. During Cabinet.xml
script re-installation phase with “GPSOutenabled” parameter value
“FALSE”.
Easy to trace such fault on OSS level. Possibly done with remote
operation without any site intervention.
3G Partially Down.
DUW is very sensitive among other RBS digital units to environment and
climate system. Directly related with RBS FAN functionality. On top of
that, RBS 6301 pole mounted type cabinet very compacted and suffer
over-heating. consequently, DUW stop its operation to protect itself
before hardware failure occurred or burnout over heated.
Due such frequent DUW script losing nature, it’s mandatory to format
DUW and re-install all required scripts. Scripts required to be
installed after DUW formatting:
-Cabinet.xml
-OAM.xml
-Site Equipment.xml
-IUB.mo
Most 3G partial issues occurred during Site Equipment (SE).xml re-
installation phase after formatted DUW.
However, the Script generator physical data we used to generate SE.xml
not up to date since 2015. Hence, not inclusive the following
particular changes.
1.RNC Local Cell ID change after 3G expansion/layering.Mismatch in
Local Cell ID between RNC defined and generated SE.xml.
2.Frequency Band change made on 2100.
Our Script Generator, generate SE.xml, fq set values.
fqBandHighEdgeBranchA="21350" & fqBandLowEdgeBranchA="21150".
Updated fq parameter set values:
fqBandHighEdgeBranchA="21300" & fqBandLowEdgeBranchA="21100"

Still, 3G partial fault exist and being trace in the meantime

corrective action take placed in OSS remotely. Fortunately, DUW is IP
device and easy for remote O&M.
Recommended Permanent Solution: Updated Script Generator with up to
date physical data permanently end up such configuration mismatching.
Still these days we use script generator with version Ver-1.0. Must be
Re-vised.

NB: Excluding any Hardware Failure and Power Failure.