Professional Documents
Culture Documents
Tems - UMTS - Dropped & Blocked Call Specifications!!!!
Tems - UMTS - Dropped & Blocked Call Specifications!!!!
1
2
2.1
2.2
2.3
2.4
2.5
2.6
3
3.1
3.2
3.3
3.3.1
3.3.2
3.4
3.4.1
3.4.2
3.4.3
3.5
3.5.1
3.5.2
3.5.3
Introduction.........................................................................................2
Dropped Calls Classification...............................................................3
Missing Neighbours............................................................................3
Poor Coverage...................................................................................4
Bad Radio Environment......................................................................5
Congestion.........................................................................................6
Not Radio............................................................................................7
Equipment Fault.................................................................................8
Blocked Calls Classification................................................................9
Missing Neighbour............................................................................10
Poor RF (Bad Coverage and Radio Environment)............................11
Equipment Fault (UE).......................................................................12
Security and Authentication Mode Failure.........................................12
UE Freeze........................................................................................13
Not Radio..........................................................................................14
Disconnect on RAB Setup................................................................14
Resources Unavailable (Congestion)...............................................15
UE Sensitivity Fault...........................................................................16
Abnormal blocked calls.....................................................................17
Unclassified - Unanswered RRC requests........................................17
Faulty Block Recording - Barred Network.........................................18
Call Initialisation during L.U. signalling..............................................19
Introduction
This document describes some of the typical dropped/blocked call
classifications encountered during several RAN Tuning Projects for WCDMA
networks. The purpose of the document is for RAN Consultants to understand
some of the problems to make the UE analysis and classification easier. The
analysis has been based on limited data (for example no UETR data or data
based on similar tool, no usage of RBS and RNC tracers) and for this result
there could be a deviation in the results. Some of these classifications are
only a guideline and should be viewed merely as documenting the typical
problem until the correct reason behind the dropped call is established.
All these dropped/blocked calls categories are adapted to the radio
environment evaluation thresholds set up for the MTN 3G RAN Tuning project
in the post-processing tool TEMS Deskcat 5.6.
In the table below are listed the main causes that must be considered during
the analysis, with the explanation for each cause.
CLASSIFICATION CRITERIA
Poor Coverage
The Drop occurs in regions where conditions CPICH RSCP and/or CPICH Ec/No are measured in
critical values not suitable for a proper connection.
Every drop that occurs when Best Server is Missing (Mostly in good CPICH RSCP conditions). The
UE active set update cannot follow the quick coverage changes. In this case Pilot Pollution
situations are included as well (3 cells in AS and more than 1 strong SCs is interfering the
connection within a range of 5 dB - Ec/No basis evaluation).
Congestion
Every drop that occurs when there are no more available radio resources for the connection. The
network sends an RRC Connection Release when the RBS reaches the maximum available Power
in DL.
Not Radio
Every drop that occurs when the radio conditions are good, the logging equipment is working
properly and the RRC connection release cause (marked usually as "Unspecified") could be
attributed to a RBS/Network fault, (including UL UE power going to maximum even if the CPICH
RSCP is measured at good values, crossed feeders causing false missing neighbours, crossed ULDL feeders, wrong parameter settings that can affect accessibility/SHOs in the cell).
Equipment Fault
Every drop that occurs when TEMS Investigation/UE are Blocking or Freezing and/or SW is
crashing, so that it's not possible to maintain the connection.
Missing Neighbours
Every drop that occurs when there are poor RSCP and/or Ec/No levels/quality on the Best
Server/AS, with the contemporary possibility for the UE to perform a SHO on a better cell that is not
declared as a Neighbour for the AS cells themselves.
2.1
Missing Neighbours
Every drop that occurs when there are poor RSCP and/or Ec/No levels/quality
on the Best Server/AS, with the contemporary possibility for the UE to perform
a SHO on a better cell that is not declared as a Neighbour for the AS cells
themselves. An example of dropped call for missing neighbour problem is
shown in figure below.
Problem Description: The Active Set best server is cell 61888 (SC = 205).
During the call sector 62096 (SC = 293) becomes the strongest sector but is
not added to the active set, as the two cells are not defined neighbours. This
can be seen in the Serving/Active Set window in TEMS. The cell 62096 act as
an increasing interferer until eventually the call is released. The release cause
is classified as unspecified.
2.2
Poor Coverage
The Drop occurs in regions where conditions CPICH RSCP and/or CPICH
Ec/No are measured in critical values not suitable for a proper connection. In
the table below an example is shown.
2.3
Problem Description: The Active Set best servers are cells with SCs 49 and
303, and all MN (SCs 304, 179 and 180) are close to them on a RSCP basis
(from 70dBm to 79 dBm). During the call UE is performing a continuous
number of SHOs, affecting both the service continuity and the quality of the
connection (low values of Ec/No on each cell). So, the Radio Environment is
not suitable for a good connection and therefore the dropped call occurs.
Sometimes the TEMS Inv. doesnt show the event on the chart, like in this
case, so its advisable to check the Events and Layer 3 messages: In the L3
table the RRC Connection Release DL corresponds (into the Event table) to
an RRC Connection Abnormal Release with the specification Unspecified.
2.4
Congestion
Every drop that occurs when there are no more available radio resources for
the connection. The network sends an RRC Connection Release when the
RBS reaches the maximum available Power in DL. In the corresponding DL
Layer 3 message RRC Connection Release when the drop happens, the
release cause is clearly marked as Congestion. An example is shown in
figure below.
Problem Description: In this case the radio environment doesnt show any
critical issue: the AS is full, and there is a Best Server cell (SC 352) with two
more cells that are carrying the service. Also the MN set is good, and the
Layer 3 messages sequence is regular.
The radio resource unavailability pops up suddenly after a certain number of
fast SHOs, and an RRC Connection Release message from the network
comes to interrupt the call. In the TEMS L3 messages window details the
release cause is clearly marked as Congestion.
2.5
Not Radio
Every drop that occurs when the radio conditions are good, the logging
equipment is working properly and the RRC connection release cause
(marked usually as "Unspecified") could be attributed to a RBS/Network fault,
(including UL UE power going to maximum even if the CPICH RSCP is
measured at good values, crossed feeders causing false missing neighbours,
crossed UL-DL feeders, wrong parameter settings that can affect
accessibility/SHOs in the cell).
This case also includes the UE Sensitivity drop, as shown in figure below.
2.6
Equipment Fault
Every drop that occurs when TEMS Investigation/UE are Blocking or Freezing
and/or SW is crashing, so that it's not possible to maintain the connection.
An example of UE freezing dropped call is shown in figure below.
3.1
Missing Neighbour
3.2
3.3
3.3.1
Problem Description: In this case there is a problem with the security and
Authentication procedure, which causes the connection to be dropped and
result in a blocked call. As can be seen in figure above the radio environment
at the time of the blocked call is good i.e. Best server RSCP=-71dBm and
Ec/No=-2dB.
The call is released normally during call set up and 6 seconds after the
network sends the security command. There is a timer for the correct
response to this security command, which is set to 6 seconds. This indicates
a problem in the security and authentication response by the UE.
3.3.2
UE Freeze
3.4
Not Radio
3.4.1
3.4.2
3.4.3
UE Sensitivity Fault
3.5
3.5.1
Problem description: In this example an RRC request is sent but the network
never responds with an RRC connection setup message. It is not clear
whether or not the network receives the RRC request. The radio environment
in the downlink as seen by TEMS is good i.e. good RSPC, low CPICH Ec/No.
3.5.2
3.5.3