UMTS Trouble Shooting

18. October 2003

1) Drop due to missing Neighbor

Symptoms

TEMS log shows that signal is going down. RSCP and Ec/No is weak, RSSI is high Mobile is changing to idle mode. 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

Page 2

1) 1 Drop due to missing Neighbor - TEMS

Symptoms 1 bad Ec/No

2 transition to Idle
Mode 3 weak RSCP 4 strong RSSI 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 !
Page 3

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 sendet an UE RRConnction release-unspecified K1297 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.
Page 4

2) 1 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
Note: there is a difference in time between TEMS Scanner and TEMS Ue

in measuring the Scrambling Codes of the Pilots

The Call drops because the RNC requests an Iu-Release due to UTRAN generated reasons
Page 5

2) 2 Drop due to high RTWP (K1297 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 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 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 C0 RACH UL C0 RACH UL NBAP UL NBAP UL C0 FACH1 DL C0 FACH1 DL 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 FP DATA RACH TM DATA RACH SD SD FP DATA FACH UM DATA FACH 3. MSG RL RL uplinkDirectTransfer RL RL 4. MSG Procedure Code 6. MSG DT1 id-Iu-ReleaseRequest DT1 id-Iu-Release IDRES DT1 DT1 radioNetwork release-due-to-utran-generated-reason release-due-to-utran-generated-reason

id-DirectTransfer id-ErrorIndication

RELCMP

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

cause = unspecified

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

id-Iu-Release

rrcConnectionRequest initiatingMessage initiatingMessage rrcConnectionReject

id-commonMeasurement id-commonMeasurement cause = congestion

DUAMCO-setting:

TMAgain FeederLoss DUAMCOattenuation = 0dB

Page 6

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. K1297 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.
Page 7

3) 1 Call Rejection due to Congestion (TEMS)

After the drop, a new call attempt is rejected byPage RNC 8 with Cause Congestion

3) 2 Call rejection due to Congestion (K1297 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 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 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 C0 RACH UL C0 RACH UL NBAP UL NBAP UL C0 FACH1 DL C0 FACH1 DL 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 FP DATA RACH TM DATA RACH SD SD FP DATA FACH UM DATA FACH 3. MSG RL RL uplinkDirectTransfer RL RL 4. MSG Procedure Code 6. MSG DT1 id-Iu-ReleaseRequest DT1 id-Iu-Release IDRES DT1 DT1 radioNetwork release-due-to-utran-generated-reason release-due-to-utran-generated-reason

id-DirectTransfer id-ErrorIndication

RELCMP

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

cause = unspecified

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

id-Iu-Release

rrcConnectionRequest initiatingMessage initiatingMessage rrcConnectionReject

id-commonMeasurement id-commonMeasurement 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.
Page 9

4) Drop due to Mobile

Symptoms

TEMS log shows that RF situation is good. No Pilot Pollution Low Ue Tx Power No RRC Release command received from UTRAN See next pages for typical screen shot Mobile is changing to idle mode without any motivation.

Reason & Solution

Must be a problem from mobile. (Qualcomm) Since Motorola Mobiles are available for TEMS, those Qualcomm problems shall not be considered any longer. (VDF Topphofen)

Page 10

4) 1 Drop due to Mobile TEMS trace

Symptoms 1 good or excellent RF

conditions
2 good SIR 3 low BLER 4 no Pilot Pollution 5 no dl RRC Connection Release 6 transition to Idle Mode

The call drops although the RF-conditions are perferct a second Ue in parallel does not drop!
Page 11

5) Missing Radio Bearer Setup

Symptoms

TEMS log shows that RF situation is good. No Pilot Pollution Ue Tx Power increased No RRC Connection Release command received. See next pages for typical screen shot Mobile is changing to idle mode without any motivation.

Reason & Solution

Possible reasons Downlink Layer 2 RLC errors or synchronisation problems on Layer 1 Other UTRAN error (e.g. ALCAP Problem between MSC & RNC). K1297 traces from Iub and Iu Interface necessary.
Page 12

5) Missing Radio Bearer Setup - Call Setup in TEMS

Symptoms 1 Ue in SHO 2 Good Ec/Io 3 medium RSCP

4 Good SIR
Before Failure: 5 High TxPower Normal Call Setup 7 low SIR 6 increased BLER

Transition to

Idle Mode
During Call Setup the Ue requests ActiveSet Update and goes into Soft-HO
Page 13

5) Missing Radio Bearer Setup L3 messages

Normal Call Setup Procedure

ActiveSet
Update during call Transition to Idle Mode After ActiveSet Update Complete no Measurement Control can be received from the UTRAN no Radio Bearer Setup setup

Page 14

5) Missing Radio Bearer Setup CalI Setup IMSI trace

Ty pe Ty pe ns m od it te eP d ow er q Sc Pri r a ma m ry bl in gC od e es sa ge Fr e ev en tI D In tra
[e1a[0]] [e1a[0]]

es sa ge

i re ct io

ot oc ol

-E rro

tra SI R

Ti m

AS

SI R

AS

Pr

16:00:39 16:00:39 16:00:39 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40 16:00:40

R R S S R S R S R S R R S R R S R S R S R R R S S R R S S

RRC DCCH RRC DCCH RANAP RNSAP RANAP RRC DCCH RNSAP ALCAP ALCAP RNSAP RNSAP RNSAP RNSAP RNSAP RRC DCCH RANAP RRC DCCH RANAP RANAP RRC DCCH RNSAP RANAP RANAP RRC DCCH RRC DCCH RRC DCCH RRC DCCH RRC DCCH ALCAP

MeasurementReport SecurityModeComplete SecurityModeComplete RadioLinkSetupRequestFDD DirectTransfer DownlinkDirectTransfer RadioLinkSetupResponseFDD ERQ - Establish Request ECF - Establish Confirm DedicatedMeasurementInitiationRequest RadioLinkRestoreIndication DedicatedMeasurementInitiationResponse DedicatedMeasurementInitiationRequest DedicatedMeasurementInitiationResponse UplinkDirectTransfer DirectTransfer UplinkDirectTransfer DirectTransfer DirectTransfer DownlinkDirectTransfer DedicatedMeasurementReport DirectTransfer RAB-AssignmentRequest DownlinkDirectTransfer ActiveSetUpdate MeasurementReport ActiveSetUpdateComplete MeasurementControl ERQ - Establish Request

[372, 291, 155, 162, 291]

[Identity Request] [Identity Request]

[Setup] [Setup] [Identity Response] [Identity Response] [Call Proceeding] [Call Proceeding] [55] [Facility] [Facility]

Ue requests ActiveSet Update and goes into Soft Handover mode

while Radio Bearer Assignment

[291] [372, 291, 162, 155, 291] [459, 299]

Page 15

5 Missing Radio Bearer Uplink Synchronisation error

Ty pe Ty pe tra ns C mit od te eP d ow er M es sa ge M es sa ge or ire ct io to co l -E rro Ne tw ot oc ol pr Ca u n r se k ra

Ti m e

AS

SI R

16:00:41 16:00:41 16:00:41 16:00:41 16:00:41 16:00:41 16:00:41 16:00:41 16:00:41 16:00:41 16:00:41 16:00:41 16:00:42 16:00:42 16:00:43 16:00:43 16:00:43 16:00:45 16:00:49 16:00:49 16:00:49 16:00:53 16:00:53 16:00:53 16:00:53 16:00:55 16:00:55 16:00:55 16:00:55 16:00:59 16:00:59 16:00:59 16:01:08 16:01:08

R S R S R S R S R S S S R R R R R R R R R R S S R R R S S R R R R S

ALCAP NBAP NBAP RNSAP RNSAP ALCAP ALCAP ALCAP ALCAP RNSAP NBAP RRC DCCH NBAP RNSAP RNSAP NBAP NBAP RNSAP NBAP NBAP NBAP NBAP RANAP RRC DCCH RANAP ALCAP ALCAP ALCAP ALCAP NBAP NBAP NBAP RANAP RANAP

ECF - Establish Confirm RadioLinkReconfigurationPrepareFDD RadioLinkReconfigurationReady RadioLinkReconfigurationPrepareFDD RadioLinkReconfigurationReadyFDD ERQ - Establish Request ECF - Establish Confirm ERQ - Establish Request ECF - Establish Confirm RadioLinkReconfigurationCommit RadioLinkReconfigurationCommit RadioBearerSetup DedicatedMeasurementReport DedicatedMeasurementReport DedicatedMeasurementReport DedicatedMeasurementReport DedicatedMeasurementReport RadioLinkFailureIndication DedicatedMeasurementReport DedicatedMeasurementReport DedicatedMeasurementReport RadioLinkFailureIndication RAB-AssignmentResponse RRCConnectionRelease Iu-ReleaseCommand REL - Release Request REL - Release Request RLC - Release Confirm RLC - Release Confirm DedicatedMeasurementReport DedicatedMeasurementReport DedicatedMeasurementReport Iu-ReleaseCommand ErrorIndication

Radio Bearer Setup is sent from RNC to NodeB but cannot be received by Ue

SI R

Pr o

AS

[75] [65] [34] [30] [30] [0] [0]

SIR error increases to maximum Layer 1 problem on Uplink

[synchronisation-failure[11]]

[96] [synchronisation-failure[10]] [radio-connection-with-UE-Lost[46]]

di o

MSC sends Iu-Release Comand

[0] [0] [96] [message-not-compatible-with-receiver-state[99]]

Page 16

5) Missing Radio Bearer Protocol Errors 1

16:01:08 16:01:08 16:01:09 16:01:09 16:01:09 16:01:13 16:01:19 16:01:19 16:01:19 16:01:23 16:01:23 16:01:29 16:01:29 16:01:29 16:01:33 16:01:38 16:01:38 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:39 16:01:40 16:01:40 16:01:40 16:01:40 16:01:40 16:01:40 16:01:40 16:01:40 16:01:41 R S R R R R R R R R S R R R R R S S S R S R S R R S R S R S R R R R R R S R S R S R S RANAP RANAP NBAP NBAP NBAP NBAP NBAP NBAP NBAP RANAP RANAP NBAP NBAP NBAP NBAP RANAP RANAP RRC DCCH NBAP NBAP NBAP NBAP NBAP NBAP RRC DCCH RANAP RRC DCCH RANAP RANAP RRC DCCH RANAP NBAP NBAP NBAP RRC DCCH RRC DCCH RRC DCCH RRC DCCH NBAP NBAP ALCAP ALCAP RANAP Iu-ReleaseCommand ErrorIndication DedicatedMeasurementReport DedicatedMeasurementReport [0] DedicatedMeasurementReport RadioLinkFailureIndication DedicatedMeasurementReport DedicatedMeasurementReport [0] DedicatedMeasurementReport Iu-ReleaseCommand ErrorIndication DedicatedMeasurementReport DedicatedMeasurementReport [0] DedicatedMeasurementReport RadioLinkFailureIndication Iu-ReleaseCommand ErrorIndication SecurityModeCommand DedicatedMeasurementInitiationRequest DedicatedMeasurementInitiationResponse DedicatedMeasurementInitiationRequest DedicatedMeasurementInitiationResponse DedicatedMeasurementInitiationRequest DedicatedMeasurementInitiationResponse SecurityModeComplete SecurityModeComplete InitialDirectTransfer [Location Updating Request] Iu-ReleaseRequest DirectTransfer [Routing area update accept] DownlinkDirectTransfer [Routing area update accept] Iu-ReleaseCommand DedicatedMeasurementReport DedicatedMeasurementReport [0] DedicatedMeasurementReport MeasurementReport UplinkDirectTransfer [Routing area update complete] RRCConnectionRelease RRCConnectionReleaseComplete RadioLinkDeletionRequest RadioLinkDeletionResponse REL - Release Request RLC - Release Confirm Iu-ReleaseComplete [message-not-compatible-with-receiver-state[99]] [0] [96] [synchronisation-failure[10]] [0] [96] [message-not-compatible-with-receiver-state[99]] [0] [96] [synchronisation-failure[10]] [message-not-compatible-with-receiver-state[99]]

[release-due-to-utran-generated-reason[15]]

[0] [96]

[norm

Page 17

5) Missing Radio Bearer Protocol Errors 2

Wed Sep 03 16:00:45 CEST Receive 2003 RNSAP Wed Sep 03 16:00:49 CEST Receive 2003 NBAP Wed Sep 03 16:00:49 CEST Receive 2003 NBAP Wed Sep 03 16:00:49 CEST Receive 2003 NBAP Wed Sep 03 16:00:53 CEST Receive 2003 NBAP Wed Sep 03 16:00:53 CEST Send2003 RANAP Wed Sep 03 16:00:53 CEST Send2003 RRC DCCH Wed Sep 03 16:00:53 CEST Receive 2003 RANAP Wed Sep 03 16:00:55 CEST Receive 2003 ALCAP Wed Sep 03 16:00:55 CEST Receive 2003 ALCAP Wed Sep 03 16:00:55 CEST Send2003 ALCAP Wed Sep 03 16:00:55 CEST Send2003 ALCAP Wed Sep 03 16:00:59 CEST Receive 2003 NBAP Wed Sep 03 16:00:59 CEST Receive 2003 NBAP Wed Sep 03 16:00:59 CEST Receive 2003 NBAP Wed Sep 03 16:01:08 CEST Receive 2003 RANAP Wed Sep 03 16:01:08 CEST Send2003 RANAP Wed Sep 03 16:01:09 CEST Receive 2003 NBAP Wed Sep 03 16:01:09 CEST Receive 2003 NBAP Wed Sep 03 16:01:09 CEST Receive 2003 NBAP Wed Sep 03 16:01:13 CEST Receive 2003 NBAP Wed Sep 03 16:01:19 CEST Receive 2003 NBAP Wed Sep 03 16:01:19 CEST Receive 2003 NBAP Wed Sep 03 16:01:19 CEST Receive 2003 NBAP Wed Sep 03 16:01:23 CEST Receive 2003 RANAP Wed Sep 03 16:01:23 CEST Send2003 RANAP Wed Sep 03 16:01:29 CEST Receive 2003 NBAP Wed Sep 03 16:01:29 CEST Receive 2003 NBAP Wed Sep 03 16:01:29 CEST Receive 2003 NBAP Wed Sep 03 16:01:33 CEST Receive 2003 NBAP Wed Sep 03 16:01:38 CEST Receive 2003 RANAP Wed Sep 03 16:01:38 CEST Send2003 RANAP Wed Sep 03 16:01:39 CEST Send2003 RRC DCCH RadioLinkFailureIndication DedicatedMeasurementReport DedicatedMeasurementReport DedicatedMeasurementReport RadioLinkFailureIndication RAB-AssignmentResponse RRCConnectionRelease Iu-ReleaseCommand REL - Release Request REL - Release Request RLC - Release Confirm RLC - Release Confirm DedicatedMeasurementReport DedicatedMeasurementReport DedicatedMeasurementReport Iu-ReleaseCommand ErrorIndication DedicatedMeasurementReport DedicatedMeasurementReport DedicatedMeasurementReport RadioLinkFailureIndication DedicatedMeasurementReport DedicatedMeasurementReport DedicatedMeasurementReport Iu-ReleaseCommand ErrorIndication DedicatedMeasurementReport DedicatedMeasurementReport DedicatedMeasurementReport RadioLinkFailureIndication Iu-ReleaseCommand ErrorIndication SecurityModeCommand
Page 18

[synchronisation-failure[11]]

[synchronisation-failure[10]] [radio-connection-with-UE-Lost[46]]

[message-not-compatible-with-receiver-state[99]]

[synchronisation-failure[10]]

[message-not-compatible-with-receiver-state[99]]

[synchronisation-failure[10]] [message-not-compatible-with-receiver-state[99]]

5) IMSI Trace RANAP Protocol Error continued

The Ue starts Call Setup and performs ActiveSet Update, however Measurement Control was not received by the Ue anymore although IMSI-trace shows that RNC sent Measurement

Control towards NodeB. This indicates already downlink sychronisation problem. Then Ue
awaits Radio Bearer Setup from RNC. The NodeB/Cell detects an Radio Link problem with the Ue during Call Setup. The Ue was at that time in Inter RNC softhandover. The first Radio Link Failure Indication was ignored by

the RNC as it came from the DRNC via RNSAP. Once the second cell, connected to the
SRNC, also reported an Radio Link Failure Indication, the RNC aborted the Radio Bearer Setup and sent RAB Assignment Response Radio Connection lost with Ue towards MSC. In parallel the RNC sends RRC Connection Release to the Ue The MSC answers with IuRelease Command message which seems to be wrong from the RNC protocol state as RNC

responses with Error Indication message not comaptible with receiver state.
The biggest issue is that the RNC is not able to clear the RRC Resources, so the NodeB/Cell continues to report Radio Link Failure Indication synchronisation failure. The MSC sends in regular intervals Iu-Release Command and the RNC rejects always with Error Indication. Note: Protocol Error continues for about 1 minute, during that time possible Call Setups will be rejected with Requested Service Option not supported
Page 19

6) 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 screen shot.

Reason & Solution

Changes in RF situation required to establish dominant server. Change of downtilts. Increase tilts of far sites Change of azimuth.

Page 20

6) Interference / Pilot Pollution (TEMS)

Symptom
1 No dominant server situation causes frequent Soft-HO 2 more than 3 Pilots are within a 6dB RSCPwindow

3 Ec/Io is of
average quality

-10dB

Strong Signal shooting up from Donnersberger Brcke which is a far site!

Page 21

6) Interference / Pilot Pollution (Plot)

Areas with more than 3 strong Pilots occur quite Frequently, because same Azimuths are used in neighbor sites

cells having the same azimuth cell-id Scr_Code MXU7774C 130 Hoehe_ 525m Hoehe 31.5m Azimuth 310
Page 22

Elek.Downtilt 3

7) Call Rejection due to loss of RRC Release Complete message Delayed Iu Release
Symptoms

After an RRC Connection Release (e.g. due to drop) it sometimes happens, that the RRC Connection Release Complete message is lost from the Ue.

In such cases the RNC is waiting a defined time period before it entirely

releases the resource on the Iu-interface.

This issue causes that the UMSC rejects a new call containing CM_SERV_REQ with cause Service Option not supportd

Reason & Solution

It is not possible to establish two CS calls at the same time. Resources need to be released before new connection can be established.

Decrease time the RNC waits until the resources are released. Ue may perform Cell Update after drop according to 3GPP 25.331

Page 23

7) Call Rejection due to loss of RRC Release Complete message (TEMS)

Symptoms 1 previous call drops

abnormally
2 Ue changes to Idle mode 3 New Call Setup

4 Good Ec/Io
5 Good RSCP

The previous Call dropped due to bad coverage and Ue changes to Idle Mode
Page 24

7) Call Rejection due to loss of RRC Release Complete message (Iu-trace K1297)
Iu-trace extract 1st call drops, 2nd call gets rejected right after CMSREQ
Long Time 14:39:03,642,122 14:39:03,652,085 14:39:04,041,923 14:39:04,102,237 14:39:04,401,936 14:39:04,522,265 14:39:04,542,627 14:39:04,543,694 14:39:04,561,923 14:39:06,791,932 14:39:07,527,879 14:39:07,557,739 14:39:07,921,920 14:39:25,661,855 14:39:25,776,495 14:39:32,826,903 14:39:32,872,642 14:39:32,886,910 14:39:32,586,963 14:39:32,708,121 From UMSC UMSC RNC UMSC RNC UMSC UMSC UMSC RNC RNC UMSC UMSC RNC RNC UMSC RNC UMSC RNC RNC UMSC 2. MSG SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD 3. MSG RL RL RL RL RL RL RL RL RL RL RL RL RL RL RL RL RL RL RL RL 4. MSG CC DT1 DT1 DT1 DT1 DT1 DT1 DT1 DT1 DT1 DT1 DT1 DT1 DT1 DT1 DT1 RLSD RLC CR CREF Procedure Code id-CommonID id-SecurityModeContr id-SecurityModeContr id-DirectTransfer id-DirectTransfer id-DirectTransfer id-DirectTransfer id-RAB-Assignment id-DirectTransfer id-RAB-Assignment id-DirectTransfer id-DirectTransfer id-DirectTransfer id-Iu-ReleaseRequest id-Iu-Release id-Iu-Release 5. MSG initiating.. initiating.. successful.. initiating.. initiating.. initiating.. initiating.. initiating.. initiating.. outcome initiating.. initiating.. initiating.. initiating.. initiating.. successful.. 6. MSG radioNetwork cause

IDREQ SETUP CPROC FACIL IDRES PROGRES CONNECT CONACK release-due-to-utran-generated-reason release-due-to-utran-generated-reason

id-InitialUE-Message id-DirectTransfer

initiating.. initiating..

CMSREQ CMSREJ Service Option not supported

The first call drops with release due to utran generated reason, but the Iu-Release is completed 7sec afterwards. In the meantime, the Ue tries to setup a new call which gets

rejected by MSC with cause Service Option not supportd assumption: 2 outgoing
CS calls are not supported for one Ue at the same time.
Page 25

7) Call Rejection due to loss of RRC Release Complete message (Iu + Iub trace K1297)
The Iu-resource gets released after about 7sec after the drop has been declared by RNC. It seems that a Radio Link timer runs in NodeB to monitor the Ues DCH. After the NodeB (cell) has reported an Radio Link Failure towards RNC, the Iu resource is released (IuRelease successful Outcome). Note: The Ue has not reported RRC Connection Complete

Long Time 14:39:25,661,855 14:39:25,776,495 14:39:26,435,778 14:39:26,435,778 14:39:30,608,053 14:39:30,618,806 14:39:31,068,692 14:39:32,826,903 14:39:32,872,642 14:39:32,886,910

From 2. MSG 3. MSG 4. MSG RNC SD RL DT1 UMSC SD RL DT1 Node-B #3 (DCH FP DATA #1 DL) DCH Node-B #3 (DCH UM DATA #1 DL) DCH rrcConnectionRelease NBAP UL SD initiatingMessage NBAP UL SD initiatingMessage NBAP UL SD initiatingMessage RNC SD RL DT1 UMSC SD RL RLSD RNC SD RL RLC

Procedure Code id-Iu-ReleaseRequest id-Iu-Release

5. MSG radioNetwork initiatingMess.. release-due-to-utran-generated-reaso initiatingMess.. release-due-to-utran-generated-reaso

id-commonMeasurement id-commonMeasurement id-radioLinkFailure synchronisation-failure id-Iu-Release successfulOutc..

Iu Released

Page 26

8) Unclear Server Footprint

Symptoms

Often, but not always, together with pilot polution. Tems log shows frequent active setupdates. Many 1a, 1b, 1c events This causes signaling load in network. Risk of link addition failure and drop is increased. Mobile is always in SHO and ocupies more resources than necessary.

Reason & Solution

Establish clear best server. Improve strong server and reduce not requested far server by changing azimuth and downtilts.

Page 27

8) Unclear Server Footprint (TEMS)

Page 28

8) Unclear Server Footprint (Plot before)

Page 29

8) Unclear Server Footprint (plot improved)

Page 30

9) Data Upload Problem

Upload of large e-mails or ftp files is not possible. Download is not infected. Very unclear picture Equipment settings Location Possible Reasons Max. MTU for one equipment in the connection could be to small or performs defragmentation. No all routers support 1500byte MTU. With BlakHoleDetection the MTU is reduced to 536Byte. Upload is possible. See special report.
Page 31

10) 3G to 2G HO - Ue lost after HCOM (K1297)

It can be seen that the HCOM is sent to the Ue, but after 15sec the UMSC sends a Iu-Release

because the InterRAT HO to GSM is not successful. If the InterRAT HO were successful a IuRelease with cause successful Relocation would be sent by UMSC. We know from the Ue that the call dropped in our trace. It is also obvious that the RNC waits more than 15sec and does not realize any problem during the handover. Here it is vital to check what is the setting for the timer T_RELOC_COMPLETE in RNC - if exist - as no handover failure with e.g.

contact with Ue lost is reported by RNC.

Page 32

10) 3G to 2G HO - Ue lost after HCOM

Open Question about 3G to 2G HO: 1. What is the timer setting in RNC for InterRAT HO to guard the handover in GSM it would be BSSMAP T8. In UMTS there must be a so called T_RELOC_COMPLETE timer to initiate a Iu-ReleaseRequest with cause e.g. contact with Ue lost 2. Possible protocol error. The RNC does not react upon the Release Command from UMSC by releasing the resources. On the contrary the UMSC repeats after 15sec the Iu-Release again. 3. The Node finally detects a Radio Link Failure cause synchronisation failure, but with about 30sec after the Handover Command sent on RLC/MAC. Here it is important to get the timer settings checked as we experience a big inbalance in detecting a drop between Ue and UTRAN, means the Ue goes back to Idle mode much quicker than the UTRAN detects it. This issue is also part of ticket: VTT00020680A

Page 33

10) 3G to 2G HO Relocation Timer overview

I n U M R 2 . 0 , t h e v a lu e o f b e lo w m e n t io n e d t im e r s c a n n o t b e c h a n g e d T h is is p o s s ib le o n ly f r o m U M R 3 . 0 o n w a r d s . P le a s e f in d in b r a c k e t s t h e a d ju s t a b le r a n g e s . 1 . T - R e lo c a t io n P r e p a r a t io n = 6 0 s * ( 1 - 1 8 0 ) 2 . T - R e lo c a t io n O v e r a ll = 6 0 s * ( 1 - 1 8 0 3 . T - R e lo c a t io n C a n c e l = 1 0 s * ( 1 - 6 0 ) T -R e lo c a tio n P R E P A R A T IO N : o n I u b e t w e e n U L - D T 1 ( R e lo c a t io n R e q u e s t ) a n d D L - D T 1 ( R e lo c a t io n C o m m a n d ) . T -R e lo c a tio n O V E R A L L : o n I u b e t w e e n D L - D T 1 ( R e lo c a t io n C o m m a n d = > R R C - H O - f r o m - U t r a n - c o m m a n d ) a n d D L I u - R e la s e c o m m a n d T -R e lo c a tio n C A N C E L : a f t e r R R C - H O - f r o m - U t r a n - c o m m a n d f a ilu r e , a n d b e t w e e n I u - U L ( R e lo c a t io n C a n c e l) a n d D L - D T 1 ( R e lo c a t io n A c k n o w le d g e . * U M R 2 .7 /2 .5

Page 34

10) 3G to 2G HO Relocation Flows [Normal]

Page 35

10) 3G to 2G HO Relocation Flows [Error case]

Page 36

10) 3G to 2G HO Relocation Flows [Error case]

Page 37

10) 3G to 2G HO Relocation Flows [Error case]

Page 38

10) 3G to 2G HO Relocation Flows [Error case]

Page 39

11) DL Radio Resources not available

Symptoms

Good RF condition EcNo and RSCP are good

RRC Connection Release with cause normal Event

In case of call-setup no Radio Bearer Setup message is seen RRC Connection Reject with cause unspecified is seen Problem may occur in high load situation e.g. when a PO call was running Problem may appear and disappear suddenly

Reason & Solution

Problem with Allocating the Spreading Factor in NodeB NodeB Reset fixes the problem temporarily

New software in NodeB is a permanent solution

Page 40

11) DL Radio Resources not available (K12 Iu trace)

After RAB-Assignment, Iu-ALCAP tries to establish the terrestrial connection between

MSC and RNC for the User Plane.

RNC responds with RAB-Assignment failure in the radio interface procedure because of NBAP Failure dl-radio-resources-not-available. The reason for this behavior is because the synchronised Radio Link Reconfiguration had an unsuccessful outcome.

Page 41

11) DL Radio Res. not available (K12 trace Iu+Iub)

unsuccessful outcome for synchronised Radio Link Reconfiguration Preparation

Page 42

11) DL Radio Resources not available (K1297 trace)

The RRC Connection Release has as a cause normal Event so a problem in UTRAN is not
visible for the Drive-test personnel when looking at TEMS

Page 43

11) DL Radio Resources not available (K1297 trace)

It can be seen that the failure dl-resources not available can also be the reason for

seeing RRC Connection Reject with cause unspecified

Page 44

12) Faulty RACH prevents Call Setup but SHO OK

Symptoms

Good RF condition EcNo and RSCP are good Ue (TEMS) shows sending of RRC Connection Request on RACH TrCH up to the max. number or retransmissions

Not any response from UTRAN e.g. RRC Connection Setup is missing
K1297 shows RACH decoding error or CRC checksum error SHOs into the affected cell and out of that cell work fine

Reason & Solution

Not available yet however the indications point to problem on CCCH

Page 45

12) Faulty RACH prevents Call Setup but SHO OK K1297 trace
Long Time 16:53:26,974,189 16:53:26,981,439 16:53:27,810,070 16:53:27,820,814 16:53:29,404,938 16:53:29,415,688 16:53:34,787,349 16:53:36,973,115 16:53:36,983,998 16:53:37,812,246 16:53:37,819,627 16:53:37,883,994 16:53:39,404,112 16:53:39,414,616 16:53:40,977,379 16:53:46,972,043 16:53:46,982,680 16:53:47,811,556 16:53:47,822,054 16:53:49,406,412 From NBAP UL NBAP UL NBAP UL NBAP UL NBAP UL NBAP UL C2 RACH UL NBAP UL NBAP UL NBAP UL NBAP UL C2 RACH UL NBAP UL NBAP UL C2 RACH UL NBAP UL NBAP UL NBAP UL NBAP UL NBAP UL 2. MSG SD SD SD SD SD SD FP DATA .. SD SD SD SD FP DATA .. SD SD FP DATA .. SD SD SD SD SD 3. MSG initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage Procedure Code id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement received total wide band power 70 70 18 70 18 70 18 70 18 70 18 70 18 70 18 70 transmitted carrier power 18

The C2 indicates the 3rd sector (C0 = 1st sector and C1=2nd sector) After the RACH has been relayed to the RNC there is no response from the RNC. Reason for that are decoding errors or wrong CRC-checksum inside the RACH.
Page 46

12) Iub shows RACH decoding errors or CRC checksum error K1297 trace

Page 47

12 Iub shows RACH decoding errors or CRC checksum error K1297 trace

Page 48

12) Iub Correct decoding RACH Example trace

Page 49

12) Drive-test log - RRC Connection Request w/o response from UTRAN
Symptoms 1 Good Ec/No 2 Good RSCP 3 Ue sends max.

number of RRC
Connection Requests without any Ack or Nack from

UTRAN
4 Ue back in Idle Mode 5 SHO into

faulty are ok

Page 50

12) Drive-test log SHO into faulty cell(s) are OK

The TEMS log

shows that
SHO into and out of the faulty cell are fine no

problem
visible

Page 51

12) Summary
The faulty cell(s) behave normal Pilot Channel can be decoded and soft-handover in and out of the faulty cell(s) are possible. Call-Setups in those faulty cells are prevented by decoding or CRC checksum error on the RACH-transport channel. As the K1297 trace monitors the Iub-interface, it cannot be determined if the error was introduced on the Air-interface or inside the NodeB. From the drive-test it looks similar like a sleeping cell, however soft-handover are working which prove that the RF-path and channels are okay. The cell is active on Uu but even after several RACHs still no response from UTRAN.

This error points to some hardware problem on the CCCH, as DCH channels work fine.

Page 52

13) No Call Setup possible but SHO OK

Symptoms

Good RF condition EcNo and RSCP are good Ue (TEMS) does not send any RRC Connection Request on RACH-TrCH Not any response from UTRAN e.g. RRC Connection Setup is missing

SHOs into the affected cell and out of that cell work fine
RNC database shows that neither Cell Barred nor Operator Barring is used, but SYSINFO Type 3 indicates Operator Barring (TEMS)

Reason & Solution

Cell Barred for Access Flag is set Cell Barred for Operator Use is set Perform an Audit on that NodeB to align RNC and NodeB database

Page 53

13) No Call Setup possible SysInfo 3 Operator Barring

Symptoms

1 Good Ec/No
2 Good RSCP 3 No RRC Connection

Request from
Ue

Cellname/SC and UARFCN are ok

System Info Type 3

Page 54

13) System Info Type 3 No Barring

Page 55

14) Ue bug too high RTWP

Symptoms

Good RF condition EcNo and RSCP are good Faulty Ue drops suddenly during or after Call-Setup for no obvious reason Other Ue(s) in parallel also drop for no obvious reason

TEMS RRC Connection Release cause unspecified

K1297 CommonMeasurement indicates very high RTWP (values >150 15dB)

Reason & Solution

Trace on Iub with K1297 and test all Ues for unusual high RTWP Throw away Ues causing high RTWP Issue seen so far on Siemens/Motorola Ue (U10 or U830)

Page 56

14) Faulty Ue causes high RTWP with drop of Ues

Long Time 13:32:03,300,666 13:32:11,963,035 13:32:11,974,026 13:32:12,859,539 13:32:12,870,040 13:32:13,292,675 13:32:13,300,059 13:32:22,862,047 13:32:22,869,181 13:32:23,291,660 13:32:31,964,773 13:32:31,972,148 13:32:32,684,387 13:32:32,764,374 13:32:32,860,915 13:32:32,871,659 13:32:32,959,332 3. MSG initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage RL RL initiatingMessage initiatingMessage RL RL 13:32:33,036,095 13:32:33,647,726 13:32:33,863,641 13:32:33,290,510 13:32:41,963,621 13:32:41,970,863 13:32:42,859,875 13:32:42,870,625 13:32:43,289,475 13:32:43,300,474 13:32:51,962,346 RRC Connection Release RRC Connection Release Complete initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage initiatingMessage DT1 id-Iu-Release 4. MSG Procedure Code id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-DirectTransfer id-DirectTransfer id-commonMeasurement id-commonMeasurement id-RAB-Assignment 6. MSG received-total-wide-band-power 70 70 70 70 70 149 SETUP IDRES 224 failure-in-the-radiointerface-procedure release-due-to-Utran generated reason unspecified radioNetwork releaseCause

DT1 DT1

DT1

id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement

Page 57

124 70 70 70 70

14) Faulty Ue causes high RTWP with drop of Ues

Long Time 13:32:43,300,474 13:32:51,962,346 13:32:51,973,337 13:32:52,862,349 13:32:58,303,387 13:32:59,383,284 13:33:01,961,562 13:32:02,099,883 RL RRC Connection Release initiatingMessage RRC Connection Release Complete initiatingMessage DT1 id-Iu-Release 3. MSG initiatingMessage initiatingMessage initiatingMessage initiatingMessage initialDirectTransfer uplinkDirectTransfer initiatingMessage 4. MSG Procedure Code id-commonMeasurement id-commonMeasurement id-commonMeasurement id-commonMeasurement 6. MSG received-total-wide-band-power 70 70 radioNetwork releaseCause

CMSREQ SETUP id-commonMeasurement 314 release-due-to-Utran generated reason unspecified id-commonMeasurement 249

13:33:02,767,047 13:33:02,861,322 13:33:02,983,573 13:33:03,290,895

id-commonMeasurement

124

It can be seen that as soon as the faulty Ue makes a phone call (SETUP message), the RTWP rises by more than 20dB. This leads to a drop and also other mobiles will drop in that Cell as well. The RRC release cause is unspecified Reason for high RTWP is the high output power of the Ue. Such an Ue will not power down as ordered by NodeB, therefore the high RTWP.
Page 58

15) TEMS bug no Measurement Reporting

Symptoms

Initial Measurement Control is sent ( for MOC: right after CM SERV REQ) Measurement Control contains Neighbor cells SC as specified in the Neighbor list After Connect Ack the Ue stops sending any measurement report towards RNC In most of the cases call drops if not aborted or Disconnected earlier

Reason & Solution

TEMS bug not yet confirmed by TEMS Support After Disconnect and new call Setup problem disappears Issue seen so far on Qualcom Ue in conjunction with TEMS only

Page 59

15) TEMS bug no Measurement Reporting

Symptoms
1 After Connect Ack no more messages from Ue are sent to

RNC
2 Ue measures neighbors but no measurement reports are sent to RNC 3 Ec/Io of Serving Cell drops, Neighbor Ec/Io are very good 4 Once a new call is set up, problem disappears

Page 60

16) No camping on cell but SHO into that cell is ok

Symptoms Problem seems only to affect the Siemens / Motorola Ue U10 / A830 model If the Measurement Control message contains one or more repeated Scrambling Code(s) (neighbor list in RNC-DB contains 2 times the same Scrambling Code) the Ue sends Measurement Control Failure Message with cause invalid configuration

The Ue cannot camp on such cell(s) - only via SHO a call can be made on that cell(s) The SysInfo Type 11 obtained in Idle Mode contains one or more repeated SCs

Reason & Solution

Delete double neighbor entries in RNC-DB

Page 61

16) 1 No camping on cell but SHO into that cell is ok

During a call, the Ue can perform SHO

with cell(s)
having an erronomeous Neighbor list same SC is defined twice as neighbor. The Meas Control Failure

is ignored by
RNC.

Page 62

16) 2 No camping on cell but SHO into that cell is ok

Textdokument
On the left there is an extract of a faulty neighbor-list. Two neighbors are defined twice with the same Scrambling

Code.
The complete Measurement Control Message can be found in the attached Textdokument.

Page 63

16) 3 No camping on cell but SHO into that cell is ok

The SysInfo 11
contains double SCs which cause the Ue to change PLMN

SysInfo 11

After having read SysInfo 11 the Ue changes the UARFCN ( try to

find another
PLMN). This is shown on the next slide.
Page 64

16) 4 No camping on cell but SHO into that cell is ok

After the Ue has received the SysInfo Type 11 with the doubling of Scrambling Codes, the Ue leaves the HPLMN Frequency and searches for different network(s). It

goes into
limited service state

Page 65

17) Blocked Call CM Service Reject with cause Network Failure

Symptoms Softhandover into the affected cell and out of the cell are ok Ec/Io and RSCP are good TEMS indicates Blocked Call Layer 3 messages shows CM Service Reject with cause Network Failure All Ues are affected

Reason & Solution

Cell(s) are not entered in (U)MSC database

Page 66

17) Blocked Call CM Service Reject (TEMS)

Symptoms
1 Good RF situation 2 all CM Serice Requests are rejected with cause Network failure

3 Soft-HO in and out

of affected cell(s) is/are OK

Page 67

17) Blocked Call RRC Connection Release unspecified

Symptoms 1 RNC aborts

the
connection with RRC Connection Release unspecified

Page 68