120222 alarms part i v01

2 © Nokia Siemens Networks CommonAbis closing workshiop/ Martin Holecek / 22nd -24th February 2012Strictly confidential

22nd – 24th February 2012, Denpasar

Common Abis Closing Workshop

CARE services, Telkomsel network

3 © Nokia Siemens Networks CommonAbis closing workshiop/ Martin Holecek / 22nd -24th February 2012 Strictly confidential

OAM Alarm Handling

Part I• 3273 GPRS/EDGE TERRITORY FAILURE• 3265 UNEQUIPPED A INTERFACE CIRCUIT• 2725 ADJACENT CELL IDENTIFIER CONFIGURATION ERROR• 7741 MEAN HOLDING TIME ABOVE DEFINED THRESHOLD• 7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLD• 7712 WORKING SDCCH CHANNEL RATIO BELOW THRESHOLD• 7744 EXCESSIVE TCH INTERFERENCE


3273 GPRS/EDGE TERRITORY FAILURE

MeaningGPRS/EDGE territory size in the normal area of BTS is below the limit specified by the BTS specific radio network parameter 'default GPRS capacity (CDEF)' or the number of connected GPRS/EDGE channels (EGTCH) in the extended or super extended area of the BTS is smaller than the number of EGTCHs configured by operator. The BSC has not been able to add more radio channels to the territory within the informing delay of this alarm (180 seconds). The BSC's ability to transfer GPRS/EDGE traffic in the BTS has been reduced or totally prevented.

InstructionsIf the alarm indicates a lack of PCUPCM resources in the packet control unit (PCU), you should consider the following options:1. Reducing the default GPRS/EDGE / extended cell area GPRS/EDGE / super extended cell area GPRS/EDGE channels connected to PCU2. Reducing the amount of dynamic Abis pool (DAP) timeslots connected to the PCU3. Moving one cell/segment from the failed PCU to another PCU

CancellingDo not cancel the alarm. The system cancels the alarm automatically when the fault has been corrected.


3265 UNEQUIPPED A INTERFACE CIRCUIT

MeaningBSC does not recognize the Circuit Identification Code (CIC) of a message it has received, or the destination point acknowledges that it does not recognize the CIC of a message it has received from the BSC.

InstructionsIf several disturbances are generated check that the circuit in question has been created at both ends.

CancellingNo cancelling


2725 ADJACENT CELL IDENTIFIER CONFIGURATION ERRORMeaningAdjacent cell information has been defined incorrectly in the BSDATA (BSS Radio Network Configuration Database). Either the MSC or the source BSC can detect the error during an external handover. When the error has been detected, the handover attempt is interrupted.

InstructionsCheck the adjacent cell information of the BTS in supplementary information field 1 in the BSDATA. If the BSC has detected the error, supplementary information fields 3, 4 and 5 identify the cell that the MSC has defined as the target cell.

Check the adjacent cell definitions with the MML command:

ZEAO:BTS=<BTS identification>;

Use the BTS's adjacent cell definitions to check the adjacent cell identification information (LAC and CI) of either the adjacent cells in the target cell list or all adjacent cells in other BSSs.

CancellingCancel the alarm with an MML command after correcting the fault as presented in INSTRUCTIONS. See instructions on alarm administration.


7741 MEAN HOLDING TIME ABOVE DEFINED THRESHOLDMeaningThe mean holding time on the channel specified exceeds the operator-defined threshold during the measurement period. The alarm is used to supervise the functioning of the traffic and signaling channels. It reveals unreleased calls.

InformationParameters, with their default values, affecting the alarm:ZEEN:MAXHTT= maximum mean holding time for TCH (120 min)MAXHTS= maximum mean holding time for SDCCH (30 min)PRDMHT= length of TCH supervision measurement (240 min)PRDMHS= length of SDCCH supervision measurement (60 min)

CancellingIf the alarm does not require user actions, you can cancel it with the MML command EOR.

The system cancels the alarm when you lock and unlock the object in question, or, if the alarm requires no user actions, the system cancels the alarm at the end of the measurement period during which the channel that caused the alarm is allocated/ released normally.


7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLDMeaningMean holding time on a channel is below the operator-defined minimum during the measurement period. The alarm is used to supervise the functioning of traffic channels and to detect the possible faulty channels.

InstructionsCheck that the parameters affecting the alarm are reasonable. The MML command EEO outputs the radio network supervision parameter values and the EEN command modifies the parameter values.

Parameters, with their default values, affecting the alarm:ZEEN:MINHTT = minimum mean holding time for a TCH (10 s)PRDMHT = length of TCH supervision measurement (120 min)CS = channel seizure threshold value (10)

CancellingIf the alarm requires no user actions, you can cancel it with the MML command EOR.

The system cancels the alarm automatically in connection with the user's locking and unlocking commands, or, if the situation is solved without user actions, after the current measurement period.

All supplementary fields are set to zero irrespective of the alarms cancelled manually or by the system.


7712 WORKING SDCCH CHANNEL RATIO BELOW THRESHOLDMeaningThe radio network configuration and failure management has detected that the ratio between the number of SDCCH channels in the cell in normal working state (UNLOCKED-WORKING) and the number of traffic channels in the cell in normal working state (UNLOCKED-WORKING) is below the defined threshold.

Only one alarm per cell is possible. Object of the alarm is the BTS which has the BCCH timeslot.

InstructionsCheck why SDCCH channels in the cell in normal working state (UNLOCKED-WORKING) or traffic channels (full and half rate) in the cell in normal working state (UNLOCKED-WORKING) are out of use. If the reason is a faulty TRX, correct the fault. This increases the number of SDCCH channels in normal working state, and the alarm is removed automatically.

The BSC-specific threshold value of the alarm can be changed with the MMI command EEQ. The new threshold value takes effect as soon as the ratio ofthe channels changes, for example, when the administrative state of the TRX is changed, or when the TRX's operative state changes.

The following formula is used in calculating the ratio:( number of WO and BL-SHD SDCCH channels / number of WO and BL-SHD traffic channels ) * 100



7744 EXCESSIVE TCH INTERFERENCE

MeaningDuring the supervision period, the TCH time slot has suffered excessive interference in idle mode that is equal to or higher than the operator-defined alarm threshold percentage. That is, the interference in the time slot has lasted longer than is acceptable. The interference level classified as excessive is defined by the operator. The alarm is used to supervise the BTS traffic capacity.

InstructionsMeasure the interference level on the traffic channel in question.

Parameters, with their default values, affecting the alarm:ZEEN:HIFSHR= TCH interference level threshold value (50 )HIFLVL= excessive interference level threshold value (4)PRDHIF= TCH interference supervision measurement (120 min)



AgendaDay1 – 22nd February 2012

Day Category Description Time Presnter1 BSC overview Functional review of BSC

HSL check balance, configuration rulesSpecial Case – crosstalk on FBSC Jambi2

9:00 – 10:00 CARE(Narendra)

BSC overview PCU/NSEI dimensioning , configuration and limitsCDED, CDEF, CMAX3273 GPRS/EDGE territory failure

11:00-12:00 CARE(Narendra, Martin)

Lunch Break 12:00-13:00BTS special cases EDGE CU vs Non-EDGE CU, EDGE, GTRX, CS3&4,,

and known special cases:13:00-14:45 CARE

(Narendra)OAM Alarm handling I 3265 UNEQUIPPED A INTERFACE CIRCUIT

2725 ADJACENT CELL IDENTIFIER CONFIGURATION ERROR

14:45-15:45 CARE (Narendra/Angga)

Tea break 15:45-16:00

OAM Alarm handling I 7741, 7743, 7712, 7744 16:00-17:30 CARENarendra, Martin)


AgendaDay2 – 23th February 2012Day Category Description Time Presnter2 Recap &Test Day1 Review Day 1 content & Test Together 9:00-9:15 ALL

FMR commissioning 9:15-10:00 CARE (Narendra)

Operation &troubleshooting

Mixed CU configuration, preferred BCCH, TBF assignment vs MS class, HMC and SRA featuresZEQO conversion to XLS

10:00-11:00 CARE(Narendra, Martin)

OSS Scripts I Create BTS 11:00-12:00 OSS (Yuri)

Lunch Break 12:00-13:00

OSS Scripts II Delete/create LAPD, split multiplexing BTS+,Change BTS parameterModify EDAP, CDED, CDEF, CMAX, Enable/disable GPRS/EDGE/ GTRXRehoming BTS with CM editorDelete/Create ADJCConvert to/from XMLIncrease/ decrease LAPD size on FMR;

13:00-15:00 OSS (Yuri)

Tea Break 15:00-15:15

OAM Alarm handling II 7745, 7705, 7723, 7725, 7738, 7789, 7730Tracing TBF traffic on PCU

15:15 - 17:30 CARE(Narendra/ Angga)


AgendaDay3 – 24th February 2012Day Category Description Time Presnter3 Recap &Test Day2 Review Day 2 content & Test Together 9:00-9:15 ALL

Optimization BR to BS Parameter Mapping 09:30-11.15 NPO (Fani)Optimization BR to BS Parameter Mapping Q & A 11.45-12.00 NPO (Fani & Daru)

Lunch Break & Pray 12:00-13.45Optimization Layering strategy for Bali

Modernization13.45-15.30 NPO (Christian)

Tea Break 15:30-15.45Optimization Layering strategy for Bali

Modernization Q&A15.45-17.00 NPO (Christian &

Daru)Closing &feedback 17:00-17:30 All

120222 alarms part i v01

Documents