UMTS TROUBLESHOOTING

3G TELKOMSEL KALIMANTAN
19 March 2008

1) Drop due to missing Neighbor

Symptoms
TEMS log shows that signal is going down.
RSCP and Ec/No Mobile is weak
TEMS log and scanner information showing different SC.
After Cell Reselection Ec/No situation is ok.
See next pages for typical screen shot.

Reason & Solution

Add missing neighbor

Nokia Siemens Networks

Company Confidential

1) Drop due to missing Neighbor - TEMS

Symptoms
1 bad Ec/No
2 transition to
Idle Mode
3 weak RSCP
5 discrepancy
betw. Scan &
Ue
6 low SIR
7 high BLER
8 strong Ec/No
after Cell
Reselection
The call drops because the Ec/No is too weak, but after Cell Reselection, the Ec/No of a
different Pilot is very good drop like in GSM !
3

Nokia Siemens Networks

Company Confidential

2) Drop due to high RTWP

Symptoms

TEMS log shows that RF situation is good.

No Pilot Pollution
Low Ue Tx Power
Call is dropped because RNC request Iu release with
command IU release request Utran generated reason
RNC send an UE RRConnction release-unspecified
K15 Iub traces shows in Common Measurement a high value
(>70) for RTWP.
Reason & Solution

The high RTWP values represents a very high cell load for
the nodeB, thus the admission and congestion control are
not accepting call setup or call is very likely to be dropped
after HO.

Correction of Duamco Settings to right attenuation is

solves problem.
Company Confidential
Nokia Siemens Networks

2) Drop due to high RTWP (TEMS)

Symptoms
1 good Ec/No
2 good RSCP
3 no Pilot
Pollution
4 low Ue TxPower
5 good SIR
6 low BLER
7 dl RRC
Connection
Release
with Cause
unspecified

Nokia Siemens Networks

Company Confidential

2) Drop due to high RTWP (K15 Call

Trace )
Long Time
14:39:40,684,298
14:39:40,684,379
14:39:40,691,612
14:39:40,691,612
14:39:40,724,197
14:39:40,741,844
14:39:40,792,770
14:39:41,272,658
14:39:41,272,658
14:39:41,491,366
14:39:41,491,366
14:39:41,574,742
14:39:41,582,126
14:39:41,637,598
14:39:41,669,244
14:39:41,682,452
14:39:41,691,502
14:39:42,221,836
14:39:42,279,628
14:39:42,291,834

From
RNC
UMSC
Node-B #3 (DCH #1 UL)
Node-B #3 (DCH #1 UL)
UMSC
RNC
Node-B #3 (DCH #1 DL)
Node-B #3 (DCH #1 DL)
Node-B #3 (DCH #1 DL)
Node-B #3 (DCH #1 UL)
Node-B #3 (DCH #1 UL)
NBAP UL
NBAP UL
NBAP DL
NBAP UL
ALCAP DL
ALCAP UL
RNC
UMSC
RNC

2. MSG
SD
SD
FP DATA DCH
AM DATA DCH
SD
SD
FP DATA DCH
FP DATA DCH
UM DATA DCH
FP DATA DCH
UM DATA DCH
SD
SD
SD
SD
SD
SD
SD
SD
SD

14:39:44,950,269
14:39:44,950,269
14:39:44,964,028
14:39:44,971,650
14:39:44,993,878
14:39:44,993,878

C0 RACH UL
C0 RACH UL
NBAP UL
NBAP UL
C0 FACH1 DL
C0 FACH1 DL

FP DATA RACH
TM DATA RACH
SD
SD
FP DATA FACH
UM DATA FACH

3. MSG
RL
RL

4. MSG Procedure Code

6. MSG
DT1
id-Iu-ReleaseRequest
DT1
id-Iu-Release

uplinkDirectTransfer
RL
RL

IDRES
DT1
DT1

rrcConnectionRelease
rrcConnectionReleaseComplete
initiatingMessage
initiatingMessage
initiatingMessage
succesfulOutcome
REL
RLC
RL
DT1
RL
RLSD
RL
RLC

id-DirectTransfer
id-ErrorIndication

radioNetwork
release-due-to-utran-generated-reason
release-due-to-utran-generated-reason

RELCMP

cause = unspecified

id-commonMeasurement
id-commonMeasurement
id-radioLinkDeletion
id-radioLinkDeletion

id-Iu-Release

rrcConnectionRequest
initiatingMessage
initiatingMessage

id-commonMeasurement
id-commonMeasurement

rrcConnectionReject

cause = congestion

DUAMCO-setting: TMAgain FeederLoss DUAMCOattenuation = 0dB

Nokia Siemens Networks

Company Confidential

3) Call Rejection due to Congestion high

RTWP
Symptoms
TEMS log shows that RF situation is good.
No Pilot Pollution
Low Ue Tx Power
Call is Rejected with reason Congestion.
K15 Iub traces show in Common Measurement a high value
(>70 > -105dBm) for RTWP.
Reason & Solution

The high RTWP values represent a very high cell load for the
nodeB, thus the admission and congestion control are not
accepting HO or call setup. Even worse, the existing call(s)
will be terminated if set so in the RNC database
Correction of Duamco Settings to right attenuation.
Sometimes, there are other interference to 3G freq or freq
jamming
7

Nokia Siemens Networks

Company Confidential

3) Call Rejection due to Congestion

(TEMS)

Company
Confidential
After
the drop, a new call
attempt
is rejected
Page by RNC with Cause Congestion
8
Nokia Siemens Networks

3) Call rejection due to Congestion

(K15Trace )
Long Time
14:39:40,684,298
14:39:40,684,379
14:39:40,691,612
14:39:40,691,612
14:39:40,724,197
14:39:40,741,844
14:39:40,792,770
14:39:41,272,658
14:39:41,272,658
14:39:41,491,366
14:39:41,491,366
14:39:41,574,742
14:39:41,582,126
14:39:41,637,598
14:39:41,669,244
14:39:41,682,452
14:39:41,691,502
14:39:42,221,836
14:39:42,279,628
14:39:42,291,834

From
RNC
UMSC
Node-B #3 (DCH #1 UL)
Node-B #3 (DCH #1 UL)
UMSC
RNC
Node-B #3 (DCH #1 DL)
Node-B #3 (DCH #1 DL)
Node-B #3 (DCH #1 DL)
Node-B #3 (DCH #1 UL)
Node-B #3 (DCH #1 UL)
NBAP UL
NBAP UL
NBAP DL
NBAP UL
ALCAP DL
ALCAP UL
RNC
UMSC
RNC

2. MSG
SD
SD
FP DATA DCH
AM DATA DCH
SD
SD
FP DATA DCH
FP DATA DCH
UM DATA DCH
FP DATA DCH
UM DATA DCH
SD
SD
SD
SD
SD
SD
SD
SD
SD

14:39:44,950,269
14:39:44,950,269
14:39:44,964,028
14:39:44,971,650
14:39:44,993,878
14:39:44,993,878

C0 RACH UL
C0 RACH UL
NBAP UL
NBAP UL
C0 FACH1 DL
C0 FACH1 DL

FP DATA RACH
TM DATA RACH
SD
SD
FP DATA FACH
UM DATA FACH

3. MSG
RL
RL

4. MSG Procedure Code

6. MSG
DT1
id-Iu-ReleaseRequest
DT1
id-Iu-Release

uplinkDirectTransfer
RL
RL

IDRES
DT1
DT1

rrcConnectionRelease
rrcConnectionReleaseComplete
initiatingMessage
initiatingMessage
initiatingMessage
succesfulOutcome
REL
RLC
RL
DT1
RL
RLSD
RL
RLC

id-DirectTransfer
id-ErrorIndication

radioNetwork
release-due-to-utran-generated-reason
release-due-to-utran-generated-reason

RELCMP

cause = unspecified

id-commonMeasurement
id-commonMeasurement
id-radioLinkDeletion
id-radioLinkDeletion

id-Iu-Release

rrcConnectionRequest
initiatingMessage
initiatingMessage

id-commonMeasurement
id-commonMeasurement

rrcConnectionReject

cause = congestion

New call is rejected by the RNC with cause Congestion. This irrational behavior
of the RNC can be explained by the Congestion Control Algorithm which kicks in
when RTWP is high and that is the case if the TMAgain is not compensated by
the FeederLoss and Duamco.
Company Confidential
9

Nokia Siemens Networks

3) Call Rejection due to Congestion high

RTWP

Interference area

Good quality coverage but bad uplink interference that making call
rejection
10

Nokia Siemens Networks

Company Confidential

4) Interference / Pilot Pollution

Symptoms

TEMS log shows several strong server, but no dominant

server situation.
Frequent link additions and deletions.
See next page for typical sreen shot.

Reason & Solution

Changes in RF situation required to establish dominant

server.
Change of downtilts. Increase tilts of far sites
Change of azimuth.

11

Nokia Siemens Networks

Company Confidential

4) Interference / Pilot Pollution (TEMS)

Symptom
1 No
dominant
server
situation
causes
frequent SoftHO
2 more than
3 Pilots are
within a 6dB
RSCP-window
3 Ec/Io is of
average
quality
-10dB

12

Nokia Siemens Networks

Company Confidential

4) Interference / Pilot Pollution (Plot)

Some of recommedations
to reduce pilot pollution
- Change SCTV_BPPN_3
from 340 to 280
- BPPN Ctrum_2 from 160
to 195

13

Nokia Siemens Networks

Company Confidential

5) Intersystem Handover 3G-2G is not working

properly
Symptoms

No Handover from UTRAN to GSM command attempt

message when walking from 3g to 2g
High Drop rate on voice call
No ISHO Success Rate value
All related adjacents have been defined
Reason & Solution

Must be defined all information related with cell base

( egc id as number of cell target, bsic number
verficiation, LAC numbering and 2g freq )
Must be defined all information related with core ( 2g
MSC id on GT and MSRN number )

14

Nokia Siemens Networks

Company Confidential

Thank you..

15

Nokia Siemens Networks

Company Confidential

LONG CALL SETUP TIME

Symptom

Reason & Solution

HTML Document

No action from radio part

From Core side, there is changing to make response
RANAP RAB assignment and RANAP Initial Direct Transfer
faster

16

Nokia Siemens Networks

Company Confidential

LONG CALL SETUP TIME

17

Nokia Siemens Networks

Company Confidential

LONG CALL SETUP TIME

18

Nokia Siemens Networks

Company Confidential