Analyzer v5 LTE Training - Print

UMTS Events
Technical Reference
July 2008
www.actix.com
The content of this manual is provided for information only, is subject to change without
notice, and should not be construed as a commitment by Actix. Actix assumes no
responsibility or liability for any errors or inaccuracies that appear in this documentation.
Copyright © Actix 2008. All rights reserved. All trademarks are hereby acknowledged.
www.actix.com
Contents
1 INTRODUCTION .........................................................................................4
2 UMTS EVENTS .........................................................................................5

2.1 UMTS SCANNER EVENTS DETECTION AND INFORMATION ATTRIBUTES............................... 5
2.1.1 Threshold Options and Preferences ......................................................... 5
2.1.2 Coverage-related Events ....................................................................... 5
2.1.3 Other Information Attributes .................................................................. 5
2.2 UMTS UE EVENTS DETECTION AND INFORMATION ATTRIBUTES ...................................... 7
2.2.1 Threshold Options and Preferences ......................................................... 7
2.2.2 Coverage Related Events....................................................................... 8
2.2.3 System related Events .........................................................................11
2.2.4 CS domain-related events ....................................................................12
2.2.5 PS domain-related events.....................................................................18
2.2.6 RRC Connection Setup -related events ...................................................22
2.2.7 CS domain Mobility Management (MM) -related events .............................26
2.2.8 Handover-related events ......................................................................27
2.2.9 RAB-related events..............................................................................29
2.2.10 Other Information Attributes ...............................................................31
2.3 APPENDIX ...................................................................................................36
2.3.1 Appendix 1 RRC Flow diagram...............................................................36
www.actix.com
Actix Radioplan UMTS Events July 2008 Technical Reference Introduction 4
1 Introduction
Actix Analyzer allows engineers to examine drive test data and scanner data to fully
optimize a UMTS network. It lets engineers understand the causes and reasons for drop
calls and access failures.
Analyzer offers an unprecedented capability to execute a detailed examination of message
flows and automating statistical analyses of performance. Analyzer significantly accelerates
the rollout, troubleshooting and optimization of the UMTS network. Actix has embedded
intelligence in the software to allow the RF engineer to visualize specific events and
understand real problems occurring in the network.
Actix solutions embody our extensive experience as the market leader in optimization
solutions for CDMA, UMTS and GSM. All of the lessons learned and the techniques
developed over a 10-year period have been incorporated into these powerful, vendor-
independent solutions for UMTS infrastructure.
This document provides an overview of the key events, information attributes implemented
into the software. For additional information on Analyzer (and other Actix products),
including white papers and other literature, please refer to www.actix.com.
www.actix.com
Actix Analyzer UMTS Events Technical Reference July 2008 UMTS Events 5
2 UMTS Events
2.1 UMTS Scanner Events Detection and Information Attributes
2.1.1 Threshold Options and Preferences
Analyzer has thresholds and preference allowing engineers to define the levels of EcIo,
Timers, etc. necessary to peg events. The following thresholds and preferences are
available:
2.1.1.1 Scanner Threshold
• Uu_Scan_PilotPollutionThreshold (Used in Scanner Pilot Pollution – Section)

Recommended value is -15 dB and value should vary between -10 and -18 dB.
• Uu_Scan_TooManyServersThreshold (Used in Scanner Too Many Server event –

Section Recommended value is 5 dB and value should vary between 1 and 10 dB.
2.1.1.2 Scanner Preferences

The WCDMA options within the General Settings group in the Preferences dialog control the
simulated active set feature. See section 2.1.3.1.
2.1.2 Coverage-related Events
2.1.2.1 Pilot Pollution (Attribute Uu_Scan_PilotPollution)

Analyzer has event detection that allows engineers to visualize pilot pollution on a map
with drive-test scanner data. The Pilot Pollution event occurs when 4 or more pilots with
Ec/Io greater than Uu_PilotPollutionThreshold are can be seen.
2.1.2.2 Too many Servers (Attribute Uu_Scan_TooManyServer)

Because UMTS uses relative levels to evaluate additions/removals to the active set,
Analyzer has a different event that allows engineers to visualize pilot pollution relative to
the best server. The Too Many Servers event acts like the Pilot Pollution event except with
relative levels. The event occurs when 4 or more pilots with Ec/No within
“Uu_Scan_TooManyServersThreshold” dB of the best server
(CPICH_Scan_EcIo_SortedBy_EcIo[0]).
2.1.3 Other Information Attributes
2.1.3.1 Emulated Active Set Module (Attributes EventCellAddition,

EventCellRemoval, EcIo_in_ActiveSet, EcIo_in_MonitoredSet)
CPICH Pollution Analysis and Handoff Analysis are both based on a calculated Active Set,
which is determined by the Emulated Active Set module. The Emulated Active Set module
implements the 3GPP handoff algorithm and uses scanner Ec/Io measurements in
conjunction with user-specific 3GPP handoff thresholds to emulate the Active Set at each
point along a drive test. Shown below is a sample set of scanner data for three individual
SCs with color and vertical lines indicating transitions of pilots into and out of the Active
Set.
www.actix.com
Using Scanner Ec/Io measurements to implement 3GPP handoff algorithms for the Active Set
Shown below is the list of attributes available for modification by the user, as indicated in
the 3GPP specifications:
Setting 3GPP handoff algorithm attributes including Reporting Range: Hysteresis Event and Time to
Trigger Event
The parameters depicted in the picture are based on the WCDMA events defined in the
3GPP TR 25.922 V4.1.0 (2001-09) Radio Resource Management Strategies specification.
Max. Active Set Size (up to 8). Specify the maximum size of the Active Set (1-8).
Disable active set simulation. Select this check box to turn off the active set simulation
feature. This will usually give faster file loading times, and will mean that the lines to cells
feature in the map will be based on the measured SC (if it's available) rather than the
simulated active set. This option is off (deselected) by default.
www.actix.com
2.2 UMTS UE Events Detection and Information Attributes

Analyzer has embedded intelligence that helps the engineer to detect problems in the
UMTS network. The event detection capabilities of Analyzer allow engineers to quickly
visualize a series of problems.
2.2.1 Threshold Options and Preferences

Analyzer has thresholds allowing engineers to define the levels of RSCP, Ec/No, Time
Delay, etc. necessary to peg events. The following thresholds are available:
• Uu_EcNoInterferenceThreshold (Used in System Interference – Section 2.2.2.1).

Recommended value is -15 dB and recommended range is -10 and -18 dB.
• Uu_RSCP_InterferenceThreshold (Used in System Interference – Section 2.2.2.1).

Recommended value is -80 dBm and should lie between -60 and -90 dBm.
• Uu_Poor_EcNoThreshold (Used in Coverage Limited, Poor Downlink and Poor

Uplink Coverage – Sections 2.2.2.2, 2.2.2.3). Recommended value is -15 dB and
should lie between -10 and -18 dB.
• Uu_Poor_RSCP_Threshold (Used in Coverage Limited, Poor Downlink and Poor

Uplink Coverage – Section 2.2.2.2, 2.2.2.3). Recommended value is -95 dBm and
should lie between -85 and -105 dBm.
• Uu_HighUE_TxPower (Used in Poor Uplink Coverage – Section 2.2.2.2).

Recommended value is 15 dBm and should lie between 0 and 25 dBm.
• Uu_LowUE_TxPower (Used in Poor Downlink Coverage – Section 2.2.2.2).

Recommended value is -15 dBm and value should vary between 0 and -30 dBm.
• Uu_CoverageLimitedUE_TxPowerThreshold (Used in Coverage Limited – Section

2.2.2.4). Recommended value is 10 dBm and values should vary between 0 and 25
dBm.
• Uu_PilotPollutionThreshold (Used in Pilot Pollution – Section 2.2.2.5)

Recommended value is -15 dB and value should vary between -10 and -18 dB
• Uu_CallSetupFailure_Num_RRCConnReq (Used in Call Setup Failure event –

Section 2.2.4.1) Recommended value is 3 and value should vary between 1 and 5
• Uu_CallSetupFailure_TimeDelay (Used in Call Setup Failure event – Section

2.2.4.1) Recommended value is 2 and value should vary between 1 and 45
seconds
• Uu_TooManyServersThreshold (Used in Too Many Server event – Section 2.2.2.6)

Recommended value is 5 dB and value should vary between 1 and 10 dB
• Uu_t309_wait_timer (Used in CellChangeOrderfromUTRAN process) Recommended

value is 5000ms (5Sec) and value should vary between 5000 and 10000.
• Uu_ReEstablishment_wait_timer (Used in ReEstablishment process) Recommended

value is 0ms and value should vary between 0 and 15000 Note: Zero dis-enable
this feature.
• Uu_wait_timer_complete (Used in Change Reconfig process) Recommended value

is 8000ms (8Sec) and value should vary between 0 and 15000 Note: Zero dis-
enable this feature.
www.actix.com
2.2.2 Coverage Related Events
2.2.2.1 System Interference (Attribute Uu_SystemInterference)

The System Interference event occurs when the CPICH_EcNo_in_ActiveSet is less than
Uu_EcNoInterferenceThreshold (in dB) and the CPICH_RSCP_in_ActiveSet is greater than
Uu_RSCP_InterferenceThreshold (in dBm).
Example of system interference before a dropped call
2.2.2.2 Poor Uplink Coverage (Attribute Uu_PoorUL_Coverage)

The Poor Uplink Coverage event occurs when the CPICH_EcNo_in_ActiveSet is greater than
Uu_Poor_EcNoThreshold and the CPICH_RSCP_in_ActiveSet is greater than
Uu_Poor_RSCP_Threshold and UeTransmittedPower is greater than Uu_HighUE_TxPower
threshold.
Example of poor uplink coverage before a dropped call
2.2.2.3 Poor Downlink Coverage (Attribute Uu_PoorDL_Coverage)

The Poor Downlink Coverage event occurs when the CPICH_EcNo_in_ActiveSet is less than
Uu_Poor_EcNoThreshold and the CPICH_RSCP_in_ActiveSet is less than
www.actix.com
Uu_Poor_RSCP_Threshold and the UeTransmittedPower is less than Uu_LowUE_TxPower

threshold.
Example of poor downlink coverage before a dropped call
2.2.2.4 Coverage Limited (Attribute Uu_CoverageLimited)

The Coverage Limited event occurs when the CPICH_EcNo_in_ActiveSet is less than
Uu_Poor_EcNoThreshold and the CPICH_RSCP_in_ActiveSet is less than
Uu_Poor_RSCP_Threshold and the UeTransmittedPower is greater than
Uu_CoverageLimitedUE_TxPowerThreshold.
Example of coverage limited problem before a dropped call
2.2.2.5 Pilot Pollution (Attribute Uu_PilotPollution)

Analyzer’s event detection allows engineers to visualize pilot pollution on a map with drive
test data. The pilot pollution event occurs when 4 or more pilots with Ec/No greater than
Uu_PilotPollutionThreshold are in the active or monitored set.
www.actix.com
The engineer needs to look at each SC and try to find out what is the best way to optimize
the area. See the training document for a full detailed description on optimization
techniques.
Example of pilot pollution before a dropped call
2.2.2.6 Too Many Servers (Attribute Uu_TooManyServer)

Because UMTS uses relative levels to evaluate additions/removals to the active set,
Analyzer has a different event that allows the engineer to visualize pilot pollution relative
to the best server. The “Too Many Servers” event acts like the pilot pollution event except
with relative levels. The event occurs when 4 or more pilots with Ec/No within
“Uu_TooManyServersThreshold” dB of the best server (Uu_ActiveSet_EcNo_0) are in the
active or monitored set.
The engineer needs to look at each SC and try to find out what is the best way to optimize
the area. See the training document for a full detailed description on optimization
techniques.
www.actix.com
Example of too many servers around a dropped call
2.2.3 System related Events
2.2.3.1 Handover Problems (Attribute Uu_HandoverProblem)

Analyzer’s event detection allows engineers to visualize handover problems on a map with
drive test data. The handover problem event works as follows:
• Event detection looks for a dropped call or call setup failure
• It counts the number of times when the first best SC in the Monitored set is
stronger than the first best SC in the Active set, within an 8-second window
leading up to the drop.
• If that number is greater than the number of times the Active set is stronger than
the Monitored set, it sets a Handover problem (assuming we have no Active set
update messages)
Example of handover problems before a dropped call
www.actix.com
2.2.3.2 Missing Neighbours (Attribute Uu_MissingNeighbour)

Analyzer’s event detection allows engineers to visualize missing neighbour on a map with
drive test data. The missing neighbour event occurs when a particular SC is not in the
neighbour list and forces the call to drop. The following procedure is followed to trigger the
event.
When the drop call occurs, a specific function looks for the next origination and gets the
value of the new SC in the active set. If the new SC is different from the SCs in the active
set before the call dropped, the function looks for the last neighbour list before the call
dropped. If that same neighbour list does not contain the new SC, it is a possible missing
neighbour.
So, in other words:
If (SC in active set after drop call) <> (SCs in active set before drop call and Neighbour list
before drop call) then missing neighbour
Of course, in this case, the engineer needs to understand the coverage issues. If the new
SC is not meant to cover the specific area, optimization is probably the best solution and
the engineer should not add the specific neighbour.
Example of a missing neighbour before a dropped call
2.2.4 CS domain-related events
2.2.4.1 CS Call Setup (Attribute Uu_CallSetupStatusOrigination,

Uu_CallSetupStatusTermination)
Following 3GPP specifications (TS 25.331), during the RRC Connection phase, if expiry of
timer T300 (see threshold Uu_CallSetupFailure_TimeDelay) before RRC Connection Setup
and V300 (Number of RRC Connection Requests) is greater than N300
(Uu_RRC_CallSetupFailure_Num_RRCConnReq), refer to point 1 and 2. (Also see Appendix
section 3.1)
If V300 is less than or equal to N300, then reset timer T300 and V300 = V300 + 1.
Note: These thresholds are only used as a initial setting,

and are updated from the system information.
www.actix.com
If RRC Connection Setup or Setup Complete was received and the call fails to proceed after
that point, it would be considered as a call setup failure during the RRC Connection Setup.
Note: RRC Connection Setup & RRC Connection Reject

message must have the same UE Identity as the RRC
Connection Request.
If the call fails between the CM Service Request (or GPRS MM Service Request for PS Calls)
and the CC Setup (or the end of the Security Mode Command Complete for PS calls), it
would be considered as a call setup failure during security procedures.
www.actix.com
If the call fails between the CC Call Proceeding and the Radio Access Bearer Setup
Complete, it would be considered as a call setup failure during the RAB Setup procedure.
When any of the following messages is received, the call is considered as successful.
• CC Alert
• CC Connect
• CC Connect Acknowledge
Note: These attributes are also set during the initial stages
of a PS call
2.2.4.2 Outgoing Call OK (Attribute Uu_OutgoingCallOk)
• Uu_RRC_MsgType == RRC Connection Request*

▫ With Uu_RRC_RRCConnectionRequest_establishmentCause equals to:
• RRC_OriginatingConversationalCall
• RRC_ EmergencyCall
• Uu_RRC_MsgType == RRC Connection Setup
• Uu_RRC_MsgType == RRC Connection Setup Complete
• GSM_Um_Msg_Type == MM CM Service Request*
• GSM_Um_Msg_Type == MM Authentication Request (*)
• GSM_Um_Msg_Type == MM Authentication Response (*)
• Uu_RRC_MsgType == Security Mode Command (*)
*
At least one of those messages (RRC Connection Request, MM CM Service Request) needs to be
present to initiate the call setup.
www.actix.com
• Uu_RRC_MsgType == Security Mode Complete (*)
• GSM_Um_Msg_Type == CC Setup (*)
• GSM_Um_Msg_Type == CC Call Proceeding (*)
• Uu_RRC_MsgType == Radio Bearer Setup (*)
• Uu_RRC_MsgType == Radio Bearer Setup Complete (*)
• GSM_Um_Msg_Type == CC Alerting OR CC Connect OR CC Connect Acknowledge
Also Outgoing OK is flag with the following

• Uu_RRC_MsgType == RRC Connection Request
• GSM_Um_Msg_Type == CC Setup
2.2.4.3 Incoming Call OK (Attribute Uu_IncomingCallOk)
• Uu_RRC_MsgType == RRC Connection Request*

• RRC_TerminatingConversationalCall
• GSM_Um_Msg_Type == RR Paging response*
• GSM_Um_Msg_Type == MM Authentication Request (*)
• GSM_Um_Msg_Type == MM Authentication Response (*)
• Uu_RRC_MsgType == Security Mode Command (*)
• Uu_RRC_MsgType == Security Mode Complete (*)
• GSM_Um_Msg_Type == CC Setup (*)
• GSM_Um_Msg_Type == CC Call Proceeding (*)
• Uu_RRC_MsgType == Radio Bearer Setup (*)
• Uu_RRC_MsgType == Radio Bearer Setup Complete (*)
*
At least one of those messages (RRC Connection Request, RR Paging Response) needs to be
present to initiate the call setup.
www.actix.com
2.2.4.4 Outgoing Call Setup Fail (Attribute Uu_OutgoingCallSetupFail)

• RRC_ EmergencyCall
OR
• GSM_Um_Msg_Type == MM CM Service Request

Then any of the following options:
• Uu_RRC_MsgType == RRC Connection Reject

OR
• Timer Expiry based on 3GPP standards

OR
• Uu_RRC_MsgType == RRC Connection Release

OR

▫ With Uu_RRC_RRCConnectionRequest_establishmentCause not equal to
the starting establishmentCause.
OR
• Any BCCH messages or Release during the call setup
Note : The call flow diagram in the next section explains in

more detail the call setup failures and the different causes
associated with them.
www.actix.com
2.2.4.5 Incoming Call Setup Fail (Attribute Uu_IncomingCallSetupFail)

• TerminatingConversationalCall
OR
• GSM_Um_Msg_Type == RR Paging response


OR

OR

OR

the starting establishmentCause.
OR
• Any BCCH messages or Release during the call setup
2.2.4.6 Call Setup Fail Cause (Attribute Uu_CSCallSetupFailureCause)

This attribute indicates the method by which the Call Setup failure was detected
• UE drop to Idle, indicates that RRC layer was dropped
• UE Forced to Idle, indicates that RRC released the RRC layer
• NAS Release, the call was released by NAS layer

This attribute is only set if the is a RRC connected state, not during RRC Setup.
2.2.4.7 Drop call (Attribute Uu_CallDropped)

When in Call (Outgoing Call Ok or Incoming Call Ok), you get any of the following options:
• Any BCCH Message

OR

OR
• One of the following messages for CS Calls:

▫ (GSM_Um_Msg_Type == CC Disconnect) OR
▫ (GSM_Um_Msg_Type == CC Release Complete) OR
www.actix.com
▫ (GSM_Um_Msg_Type == CC Release)
▫ AND any of the above messages with NOT a normal cause for ending the
call (CauseCodeCC is greater than 31)
2.2.4.8 Dropped Call Cause (Attribute Uu_CSCallDroppedCause)

This attribute indicates the method by which the Dropped call was detected
• UE drop to Idle, indicates that RRC layer was drop
• UE Forced to Idle, indicates that RRC released the RRC layer
• NAS Release, the call was released by NAS layer
2.2.4.9 Call complete (Attribute Uu_CallCompleted)
• When in Call (Outgoing Call Ok or Incoming Call Ok), you get one of the following
messages:
▫ GSM_Um_Msg_Type == CC Disconnect (1) OR
▫ GSM_Um_Msg_Type == CC Release Complete OR
▫ GSM_Um_Msg_Type == CC Release
AND any of the above messages with a normal cause for ending the call (CauseCodeCC is
equal or less than 31)
2.2.5 PS domain-related events

Unlike in the CS domain, the definition of Call in the PS domain is subject to different
interpretations.
This paper explains the criteria used by Actix for the classification of a PS Call and the
definition of the related events.
It should be noted that besides PS Call related events and statistics Actix provides analysis
of other NAS specific procedures that are sometimes linked to the PS Call concept, like PDP
Context Activation/Deactivation.
The main criterion adopted by Actix for the definition of PS Call is:
There needs to be actual transfer of PS data
In fact in UMTS it is possible to establish a PDP Context without actually transfer any data
(this is typical of “Always-on” network). So the main trigger for the detection of PS Call is
the attempt to setup a PS Radio Bearer with rate greater than 0 kbps (some networks
allow to establish a dummy bearer of 0 kbps…).
However, because many operators tend to identify a PS Call with the setup of a PDP
context, whenever it is applicable. Session Management messages are used as trigger for
setting attributes like Successful/Failed PS Call Setup.
An Originating PS Call attempt is detected by one of the following triggers:
• RRC: RRC Connection Request with Establishment Cause equal to any of the
following:
▫ RRC_OriginatingStreamingCall
▫ RRC_OriginatingInteractiveCall
▫ RRC_OriginatingBackgroundCall
www.actix.com
▫ RRC_OriginatingSubscribedTrafficCall
• RRC: Radio Bearer Setup message with assignment of physical resources to that
PS Radio Bearer (PS Rate in DCH > 0 kbps) if PS call attempt not already detected*
• RRC: Radio Bearer Reconfiguration, with assignment of physical resources to that

PS Radio Bearer (PS Rate in DCH > 0 kbps) if PS call attempt not already detected*
• RRC: Transport Channel Reconfiguration, with assignment of physical resources to

the related PS Radio Bearer (PS Rate in DCH > 0 kbps) if PS call attempt not
already detected*
A Terminating PS Call attempt is detected with one of the following triggers:
• RRC: RRC Connection Request with Establishment Cause equal to any of the
following:
▫ RRC TerminatingStreamingCall
▫ RRC TerminatingInteractiveCall
▫ RRC TerminatingBackgroundCall
• GMM: Service Request with Service Type equal to “Paging Response”

It should be noted that in the likely case that more than one of the above events occur
during the setup sequence only the first event (in time) is valid for the detection of the PS
Call attempt. In other words, if a PS Call attempt has been already detected, subsequent
triggers do not detect the PS call again.
2.2.5.1 Outgoing Call OK PS (Attribute Uu_OutgoingCallOk_PS)

During the Originating PS Call Setup phase (i.e. an Originating PS Call Attempt has been
detected) each of the following events denotes a successful PS call setup:
• RRC: Radio Bearer Setup Complete if PS Rate in DCH > 0 kbps and a PDP Context
is already active for that Radio Bearer
• SM: Activation PDP Context Accept and the PS rate assigned during the RB Setup
procedure is greater than zero (NOTE: during the PDP Context activation a PS
Radio Bearer Setup procedure always occurs)
• RRC: Radio Bearer Reconfiguration Complete, with assignment of physical

resources to that PS Radio Bearer (PS Rate in DCH > 0 kbps) if not already in call
• RRC: Transport Channel Reconfiguration Complete, with assignment of physical

resources to the related PS Radio Bearer (PS Rate in DCH > 0 kbps) if not already
in call
2.2.5.2 Incoming Call OK PS (Attribute Uu_IncomingCallOk_PS)

During the Terminating PS Call Setup phase (i.e. a Terminating PS Call Attempt has been
detected) each of the following events denotes a successful PS call setup:
• RRC: Radio Bearer Setup Complete if PS Rate in DCH > 0 kbps and a PDP Context
is already active for that Radio Bearer
*
A typical case is where a RB is setup either in DCH without configuring physical resources
(Ch.Code) or in FACH
www.actix.com
• SM: Activation PDP Context Accept and the PS rate assigned during the RB Setup
procedure is greater than zero (NOTE: during the PDP Context activation a PS
Radio Bearer Setup procedure always occurs)
• RRC: Radio Bearer Reconfiguration Complete, with assignment of physical

resources to that PS Radio Bearer (PS Rate in DCH > 0 kbps) if not already in call
• RRC: Transport Channel Reconfiguration Complete, with assignment of physical

resources to the related PS Radio Bearer (PS Rate in DCH > 0 kbps) if not already
in call
2.2.5.3 Outgoing Call Setup Fail PS (Attribute Uu_OutgoingCallSetupFail_PS)

During the Originating PS Call Setup phase (i.e. an Originating PS Call Attempt has been
detected) and before reaching a PS Call successful Setup, each of the following events
denotes a PS call setup failure:
• RRC: RRC Connection Reject (e.g. Congestion)
• RRC Connection Setup fails due to timer expiry (T300 x N300)
• RRC: RRC Connection Release with cause other than “Normal Release”
• UE drops to idle*
• RRC: Radio Bearer Setup Failure
• SM: PDP Context Activation Reject (without RB Setup Failure)
• RRC: Radio Bearer Reconfiguration Failure
• RRC: Transport channel Reconfiguration Failure
2.2.5.4 Incoming Call Setup Fail PS (Attribute Uu_IncomingCallSetupFail_PS)

During the Terminating PS Call Setup phase (i.e. a Terminating PS Call Attempt has been
detected), and before reaching a PS Call successful Setup, each of the following events
denotes a PS call setup failure:
• RRC: RRC Connection Reject (e.g. Congestion)
• RRC Connection Setup fails due to timer expiry (T300 x N300)
• RRC: RRC Connection Release with cause other than “Normal Release”
• UE drops to idle*
• RRC: Radio Bearer Setup Failure
• SM: PDP Context Activation Reject (without RB Setup Failure)
• RRC: Radio Bearer Reconfiguration Failure
*
The algorithm use to detect a UE dropping to idle is based on one of the following events:
- SystemInfo messages from UE in Cell_DCH. The event is actually detected after an internal
configurable timer expires, in order to handle RRC re-establishment procedures
- RRC Connection Request from UE in Cell_FACH/Cell_PCH
www.actix.com
• RRC: Transport channel Reconfiguration Failure
2.2.5.5 Call complete PS (Attribute Uu_CallCompleted_PS)
• When in Call (Outgoing Call Ok PS or Incoming Call Ok PS), each of the following
events denotes a successfully completed PS call:
▫ Uu_RRC_MsgType == RRCConnectionRelease with cause “Normal Release”
or “User inactivity”
▫ Deactivation PDP Context Request with cause “Regular deactivation”
2.2.5.6 Dropped call PS (Attribute Uu_CallDropped_PS)
• When in Call (Outgoing Call Ok PS or Incoming Call Ok PS), each of the following
events denotes a PS Call drop:
▫ Uu_RRC_MsgType == RRCConnectionRelease with cause other than
“Normal Release” and “User inactivity”
▫ UE drops to idle and does not re-establish via RRC Connection re-
establishment procedure.
▫ Deactivation PDP Context Request with cause other than “Regular
deactivation”
2.2.5.7 Call setup time PS (Attribute Uu_TimeBetweenRRC_REQandCallStart)

The PS call setup time measures the time taken to setup the RRC Connection and the PS
radio bearer.
The starting point for the timer is the following event:
• Uu_RRC_MsgType == RRCConnectionRequest
▫ If the RRC Connection Request message is retransmitted, the starting point
for the Uu_TimeBetweenRRC_REQandCallStart remains the first RRC
Connection Request message
The ending point for the timer is the following event:
• Attribute Uu_IncomingCallOk_PS is set
• Attribute Uu_OutgoingCallOk_PS is set

▫ Please refer to the corresponding paragraphs for details about attributes
Uu_IncomingCallOk_PS and Uu_OutgoingCallOk_PS
2.2.5.8 PS Call known issues in the current release

This is a list of PS Calls known issues that will be fixed in the next release.
• As described in the PS Call Attempt definition, the RB Setup message detects an

Originating Call if physical resources are allocated for that PS Radio Bearer.
However in the case of Service Type “Data” a Call Id is always assigned even when
there are not physical resources assigned (i.e. PS Rate = 0 kbps); this results in
identifying possible PS Call Setup failures even when PS Rate = 0kbps.
• If during PDP Context Activation the logging tool skip the RB Setup message, the
message sequence stalls and restarts only when UE returns to idle, unless the
network sends a PDP context Reject.
www.actix.com
2.2.6 RRC Connection Setup -related events
2.2.6.1 RRC Connection ID (Attributes Uu_RRC_ID,

Uu_First_RRC_Request_N300, Uu_First_RRC_Request_T300,
Uu_RRC_Start_Time)
Uu_RRC_ID is a unique number asserted to a RRC connection. The Uu_RRC_ID is given a
number on the first RRC Connection Request this number is then maintained for the
duration of the connection.
Once the RRC is released or dropped the Uu_RRC_ID is set to zero on the next message.
Note: On the First RRC Request there are attributes

Uu_First_RRC_Request_N300,
Uu_First_RRC_Request_T300, Uu_RRC_Start_Time are set.
These give the N300 & T300 used for the RRC procedure
and the time of the first RRC.
www.actix.com
Uu RRC ID
RRC Counter is set to 1
Start Of 0 Uu_RRC_ID is set to 0
File
Uu_RRC_ID is set to RRC Counter

RRC Connection Request 1 RRC Counter is set to RRC Counter +1
Thus RRC Counter now 2
1
RRC Connection Setup
1
RRC Connection complete
1
RRC Connection Release
Uu_RRC_ID is set to 0
0
Uu_RRC_ID is set to RRC Counter

RRC Connection Request
2 RRC Counter is set to RRC Counter +1
Thus RRC Counter now 2
RRC Connection Request 2 If still within the N300 & T300 time frame
RRC LayerState (Attribute Uu_RRC_LayerState)

This attribute show the last state the device was in during the file. The attribute can be set
to one of the following based on the signaling received:
State Signaling
Idle UMTS System Information or RRC is released
RRC Request UL-CCCH RRCConnectionRequest
RRC Setup DL-CCCH RRCConnectionSetup
RRC Connected UL-DCCH RRCConnectionSetupComplete
Wait_for_ReEstablishment RRC Connection has dropped, and the event is wait
to see if the RRC reestablish
GSM_State GSM System Information or GSM Signalling
www.actix.com
Example:
2.2.6.2 RRC Connection Completed Outgoing Call (Attribute

Uu_OutgoingRRC_ConnectionOk)

▫ With Uu_RRC_RRCConnectionRequest_establishmentCause equals any of
the following:
• RRC_OriginatingStreamingCall
• RRC_OriginatingInteractiveCall
• RRC_OriginatingBackgroundCall
• RRC_OriginatingSubscribedTrafficCall
• RRC_emergencyCall
• RRC_interRAT_CellReselection
• RRC_interRAT_CellChangeOrder
• RRC_Registration
• RRC_detach
• RRC_OrignatingHighPrioritySignalling
• RRC_OrignatingLowPrioritySignalling
2.2.6.3 RRC Connection Completed Incoming Call (Attribute

Uu_IncomingRRC_ConnectionOk)
www.actix.com
▫ With Uu_RRC_RRCConnectionRequest_establishmentCause equals any of

the following:
• TerminatingConversationalCall
• TerminatingStreamingCall
• TerminatingInteractiveCall
• TerminatingBackgroundCall
• TerminatingHighPrioritySignalling
2.2.6.4 RRC Connection Reject (Attribute Uu_RRC_Reject)

▫ With Uu_RRC_RRCConnectionRequest_establishmentCause of any type
2.2.6.5 RRC Connection Abort (Attribute Uu_RRC_Abort)

▫ With Uu_RRC_RRCConnectionRequest_establishmentCause of any type

the starting establishmentCause
OR

OR

OR
• Where the UE identity is set to default value

▫ Uu_RRC_TMSI_and_LAI_GSM_MAP_tmsi[0],
Uu_RRC_P_TMSI_and_RAI_GSM_MAP_p_TMSI[0]
▫ Uu_RRC_IMSI
▫ Uu_RRC_IMEI_Digit
▫ Uu_RRC_ESN_DS_41
▫ Default is -1
www.actix.com
2.2.6.6 RRC ReEstablishment (Attribute Uu_RRC_ReEstablishment)

When a Radio Link is determined dropped (see above), you enter the state Wait for
ReEstablistment. A Reestablishment Attribute is set if you get one of the following within
the time period set by threshold Uu_ReEstablishment_wait_timer:
• Uu_RRC_MsgType == PhysicalChannelReconfigurationComplete
• Uu_RRC_MsgType == RadioBearerReconfigurationComplete
• Uu_RRC_MsgType == TransportChannelReconfigurationComplete
2.2.6.7 RRC State (Attribute Uu_RRC_MessageBased_state)

This attribute tracks the state of the RRC connection, to determine which mode it is in
based on signaling seen (such as DL-DCCH PhysicalChannReconfiguration). These states
are DCH, FACH, PCH.
RRC State Diagram
2.2.7 CS domain Mobility Management (MM) -related events
2.2.7.1 Location Update OK (Attribute Uu_LocationUpdateOK)
• GSM_Um_Msg_Type == MM Location Updating Request
• GSM_Um_Msg_Type == MM Location Updating Accept
2.2.7.2 Location Update Fail (Attribute Uu_LocationUpdateFail)
• GSM_Um_Msg_Type == MM Location Updating Reject

OR
www.actix.com
• Any BCCH messages during the Update Request process
2.2.8 Handover-related events
2.2.8.1 Handoff OK (Attribute Uu_HandoffOk)
• ActiveSetUpdate message (Uu_RRC_MsgType == ActiveSetUpdate)
• ActiveSetUpdateComplete message (Uu_RRC_MsgType ==

ActiveSetUpdateComplete)
Note : This attribute is only incremented if the RRC event

Diagram is in the RRC Connected State.
2.2.8.2 Handoff Failure (Attribute Uu_HandoffFail)
• ActiveSetUpdate message (Uu_RRC_MsgType == ActiveSetUpdate)
• ActiveSetUpdateFailure message (Uu_RRC_MsgType == ActiveSetUpdateFailure)

2.2.8.3 Handover to GSM event OK (Attribute Uu_Handover_toGSM)

HandoverfromUTRANcommand
• Uu_RRC_MsgType == HandoverfromUTRANcommand-GSM
And then
• GSM_Um_Msg_Type == RR Handover Complete

OR
• GSM_Um_Msg_Type == RR Measurement Report for 10 concessive message
CellChangeOrderfromUTRAN
• Uu_RRC_MsgType == CellChangeOrderfromUTRAN
And then
• GSM_Um_Msg_Type == RR Channel Request

OR
• GSM_Um_Msg_Type == RR Immediate Assignment

OR
• GSM_Um_Msg_Type == RR Immediate Assignment Extended
Note : One of the above must be received before the

expiry of the timer Uu_t309_wait_timer
www.actix.com
2.2.8.4 Handover to GSM event Failure (Attribute Uu_Handover_toGSM_Failure)

HandoverfromUTRANcommand
• Uu_RRC_MsgType == HandoverfromUTRANcommand-GSM
And then
• Uu_RRC_MsgType == HandoverFromUTRANFailure
OR
• Any GSM or UMTS BCCH messages.

OR
• GSM_Um_Msg_Type == RR Channel Request

OR
CellChangeOrderfromUTRAN
• Uu_RRC_MsgType == CellChangeOrderfromUTRAN
And then
• Uu_RRC_MsgType == CellChangeOrderFromUTRANFailure
OR
• Any UMTS BCCH messages.

OR
• Timer Expiry, which is configured by threshold Uu_T309_Wait_Timer

OR
2.2.8.5 Handover to UMTS event (Attribute Uu_Handover_toUTRAN)
• Handover to UMTS message

▫ Uu_RRC_MsgType == HandovertoUTRANcomplete
Note: that if a call is completed in GSM mode (after the

handover from UTRAN to GSM), the call event will appear
in the GSM section of the Workspace Explorer window.
2.2.8.6 IRAT Reselection (Attributes Uu_IRAT_Reselection3G2G,

Uu_IRAT_Reselection2G3G)
If a device is determined to be idle, and system information from the other technology is
seen, there will be an event to indicate there has been a technology change.
2.2.8.7 Cell Reselection (Attribute Uu_CellReselection)

If a device is determined to be in Cell Fach and there is a server cell change, then there
will be an event to indicate there has been a Cell reselection.
www.actix.com
2.2.8.8 UE Handoff State (Attribute Uu_UE_HandoffState)

The handoff state algorithm has the following components:
• The Active Set information from the Handset
• Using the geographic information in the log file and the SC, the network element
database is searched to identify the Sector and Cell IDs of the SC
• Handoff state is calculated by determining the configuration of the sectors in the

Active Set
2.2.9 RAB-related events
2.2.9.1 RadioBearerSetup OK (Attributes Uu_RadioBearerSetupOK,

Uu_PSRadioBearerSetupOK)
The domain Information Element determines which attribute is populated.
Uu_RadioBearerSetupOK is always populated and Uu_PS RadioBearerSetupOK is only
popluted if there is a PS domain content.
• RadioBearerSetup message (Uu_RRC_MsgType == RadioBearerSetup)
www.actix.com
Then
• RadioBearerSetupComplete message (Uu_RRC_MsgType ==

RadioBearerSetupComplete)
Also Uu_RadioBearerSetupOK if the following
• RadioBearerSetup message (Uu_RRC_MsgType == RadioBearerSetup)

Then
• UplinkDirectTransfer message (Uu_RRC_MsgType == UplinkDirectTransfer)

OR
• DownlinkDirectTransfer message (Uu_RRC_MsgType == DownlinkDirectTransfer)

2.2.9.2 RadioBearerSetup Failure (Attributes Uu_RadioBearerSetupfFail,

Uu_PSRadioBearerSetupfFail)
• RadioBearerSetup message (Uu_RRC_MsgType == ActiveSetUpdate)

Then
• RadioBearerSetupFailure message (Uu_RRC_MsgType == ActiveSetUpdateFailure)

OR
• RRC Layer has dropped.

2.2.9.3 RadioBearerRelease OK (Attributes Uu_RadioBearerReleaseOK,

Uu_PSRadioBearerReleaseOK)
• RadioBearerRelease message (Uu_RRC_MsgType == RadioBearerRelease)

Then
• RadioBearerReleaseComplete message (Uu_RRC_MsgType ==

RadioBearerReleaseComplete)

2.2.9.4 RadioBearerRelease Failure (Attributes Uu_RadioBearerReleaseFail,

Uu_PSRadioBearerReleaseFail)
• RadioBearerSetup message (Uu_RRC_MsgType == RadioBearerRelease)

Then
• RadioBearerSetupFailure message (Uu_RRC_MsgType ==

RadioBearerReleaseFailure)
OR
www.actix.com
• RRC Layer has dropped.

2.2.10 Other Information Attributes
2.2.10.1 ID and Call Type Attributes (Attributes Uu_Call_ID, Uu_Call_ID_PS,

Uu_RRC_Call_type, Uu_Call_type)
The table below shows how the ID and Type attributes are set:
RRC Request Cause Type Uu_RRC Uu_Call Uu_Call Uu_RRC Uu _Call

_ID _ID _ID_PS _Call_type _type
RRC_originatingconversationalCall Incr. Incr. CS CS

RRC_originatingStreamingCall Incr. Incr. PS PS
RRC_originatingInteractiveCall Incr. Incr. PS PS
RRC_originatingBackgroundcall Incr. Incr. PS PS
RRC_originatingSubscribedCall Incr. Other Other
terminatingConversationalCall Incr. Incr. CS CS
terminatingStreamingCall Incr. Incr. PS PS
terminatingInactiveCall Incr. Incr. PS PS
terminatingBackgroundCall Incr. Incr. PS PS
RRC_emergencyCall Incr. Incr. CS CS
RRC_interRAT_CellReselection Incr. IRAT Other
RRC_interRAT_CellChangeOrder Incr. IRAT Other
RRC_registration Incr. REG Other
RRC_detach Incr. DET Other
RRC_originatingHighPrioritySignalling Incr. CS/PS Other
RRC_originatingLowPrioritySignalling Incr. SMS Other
RRC_callRe_establishment Incr. Other Other
terminatingHighPrioritySignalling Incr. CS/PS Other
terminatingLowPrioritySignalling Incr. SMS Other
terminatingCauseUnknown Incr. Other Other
www.actix.com
2.2.10.2 CallState Attributes (Attributes Uu_CallState, Uu_CallState_PS)

These attributes show the last state the device was in during the file. The attribute can be
set to one of the following based on the signaling received:
State Signalling
Idle UMTS System Information or RRC is released
RRC Con Request UL-CCCH RRCConnectionRequest
RRC Con Setup DL-CCCH RRCConnectionSetup
RRC Setup Complete UL-DCCH RRCConnectionSetupComplete
Outgoing Call Setup MM CM Service Request
In Call CC Alerting or CC Connect or CC Connect Acknowledge
Security Mode Command DL-DCCH SecurityModeCommand
Security Complete UL-DCCH SecurityModeComplete
CC Setup CC Setup
Authentification Request MM Authentification Request
Authentification Response MM Authentification Response
CC Call Proceeding CC Call Proceeding
RAB Setup DL-DCCH RadioBearerSetup
RAB Complete UL-DCCH RadioBearerSetupComplete
Incoming Call Setup RR Paging Response
GSM Mode GSM System Information or GSM Signalling
Example:
www.actix.com
2.2.10.3 CS domain Call type (Attribute Uu_CS_Call_Type)

This attribute indicates the type of call, based on information in the CC Setup message:
Uu_RRC: UL_DCCH_Message
- . .integrityCheckInfo
- . . .messageAuthenticationCode: 10123811
- . . .rrc-MessageSequenceNumber: 1
- . .message:- uplinkDirectTransfer
- . . . .cn-DomainIdentity: 0 ( cs_domain)
- . . . .nas-Message
CC Setup
Bearer Capability- Radio Channel Requirement: 3,

Coding Standard: 0, Transfer Mode: 0,
Information Transfer Capability: 0 (Prefered Codec: 2)
Type of Number: unknown
Numbering Plan Id: ISDN/Telephony
Called Party #: 699
Thus if:
ITC=0 -> Voice Call,
ITC=1 -> Video Call,
ITC=2 (set in CM Service request) -> emergency call
2.2.10.4 PS Domain Reconfiguration OK (Attrbute Uu_PSReconfOK)
• Reconfiguration message (Uu_RRC_MsgType == RadioBearerReconfiguration or

TransportChannelReconfiguration or PhysicalChannelReconfiguration)
Then
• Reconfiguration Complete message (Uu_RRC_MsgType ==

RadioBearerReconfigurationComplete or TransportChannelReconfigurationComplete
or PhysicalChannelReconfigurationComplete)
2.2.10.5 PS Domain Reconfiguration Fail (Attrbute Uu_PSReconfFail)
• Reconfiguration message (Uu_RRC_MsgType == RadioBearerReconfiguration or

TransportChannelReconfiguration or PhysicalChannelReconfiguration)
Then
• Reconfiguration Complete message (Uu_RRC_MsgType ==

RadioBearerReconfigurationFailure or TransportChannelReconfiguration Failure or
PhysicalChannelReconfiguration Failure)
2.2.10.6 Technology Mode (Attribute Uu_Technology_Mode)

From signaling in the file, this attribute will be set to indicate if the device is in GSM or
UMTS mode.
2.2.10.7 ActiveSet information (Attributes UE_SCs_in_ActiveSetAtASU,

UE_HeldActiveSetSize_BtwASUs, UE_ActiveSetSizeAtASU)
These attribute are generate from the ActiveSet update signaling. Attribute
UE_SCs_in_ActiveSetAtASU is a text string of what is in the ActiveSet
www.actix.com
Example of the UE_SCs_in_ActiveSetAtASU
Attribute UE_HeldActiveSetSize_BtwASUs is the ActiveSet Size between the ActiveSet

updates, and UE_ActiveSetSizeAtASU is the ActiveSet Size at ActiveSet Update command.
2.2.10.8 PS Allocated Rate (Attributes Uu_PS_AllocatedRate, Uu_PS_RateDuration,

Uu_PSRate_DCH)
Attribute Uu_PS_AllocatedRate indicates the bit rate assigned by the network to a PS Radio
Bearer. The new value is set at the completion of the RRC procedure by which the network
assigns a new rate to the PS Radio Bearer. Supported values are
no phys.ch.
512 kbps
384 kbps
128 kbps
64 kbps
8 kbps (SF 64)
8 kbps (SF 128)
Attribute Uu_PS_RateDuration indicates the duration (in msec.) of the previous PS
Allocated rate. Like Uu_PS_AllocatedRate, it is set at the completion of the RRC procedure
by which the network assigns a new rate to the PS Radio Bearer.
www.actix.com
Attribute Uu_PSRate_DCH indicates the bit rate assigned by the network to a PS Radio
Bearer. Supported values are as above
It changes every time the network assigns a new rate to the user via RRC signaling (e.g.
Radio Bearer Setup). The new value is set at the start of the RRC procedure by which the
network assigns a new rate to the PS Radio Bearer.
2.2.10.9 UMTS Neighbour List (Attributes Uu_UE_NbrList, Uu_UE_NbrListCount)

These attributes are generated from Measurement Control signalling within file.
The Measurement Control messages are sent from the network to the UE during a RRC
connection. They can contain the list of the available neighbors (scrambling codes) that a
UE should consider in its measurement procedures. The first of these Measurement Control
messages is usually the setup Mode. The Concessive MC messages modify mode (i.e. they
change the list).
After the RRC connection procedure the algorithm, considers the first Measurement Control
message to be the Setup and builds up an internal array of Scrambling Code with their
corresponding index numbers (from attributes Uu_RRC_NewIntraFreqCell_intraFreqCellID
and Uu_RRC_PrimaryCPICH_Info_primaryScramblingCode). This information is then used
to populate attributes Uu_UE_NbrList and Uu_UE_NbrListCount (i.e. the number of SCs in
the array).
Concessive Measurement Control messages then modify this list, this continues until a new
RRC Setup procedure is detached at which point the array is reset.
Note: If there are any missing Measurement Control

messages, this NBR list will become out of sync with the
true NBR list being measured by the UE.
www.actix.com
Actix Analyzer UMTS Events Technical Reference July 2008 Appendix 36
3 Appendix
3.1 Appendix 1 RRC Flow diagram
www.actix.com
www.actix.com
www.actix.com

Analyzer v5 LTE Training - Print

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Analyzer v5 LTE Training - Print

Diunggah oleh

Hak Cipta:

Format Tersedia

UMTS Events

2 UMTS EVENTS .........................................................................................5

2.1.1.1 Scanner Threshold

• Uu_Scan_PilotPollutionThreshold (Used in Scanner Pilot Pollution – Section)

• Uu_Scan_TooManyServersThreshold (Used in Scanner Too Many Server event –

2.1.1.2 Scanner Preferences

2.1.2 Coverage-related Events

2.1.2.1 Pilot Pollution (Attribute Uu_Scan_PilotPollution)

2.1.2.2 Too many Servers (Attribute Uu_Scan_TooManyServer)

2.1.3 Other Information Attributes

2.1.3.1 Emulated Active Set Module (Attributes EventCellAddition,

2.2 UMTS UE Events Detection and Information Attributes

2.2.1 Threshold Options and Preferences

• Uu_EcNoInterferenceThreshold (Used in System Interference – Section 2.2.2.1).

• Uu_RSCP_InterferenceThreshold (Used in System Interference – Section 2.2.2.1).

• Uu_Poor_EcNoThreshold (Used in Coverage Limited, Poor Downlink and Poor

• Uu_Poor_RSCP_Threshold (Used in Coverage Limited, Poor Downlink and Poor

• Uu_HighUE_TxPower (Used in Poor Uplink Coverage – Section 2.2.2.2).

• Uu_LowUE_TxPower (Used in Poor Downlink Coverage – Section 2.2.2.2).

• Uu_CoverageLimitedUE_TxPowerThreshold (Used in Coverage Limited – Section

• Uu_PilotPollutionThreshold (Used in Pilot Pollution – Section 2.2.2.5)

• Uu_CallSetupFailure_Num_RRCConnReq (Used in Call Setup Failure event –

• Uu_CallSetupFailure_TimeDelay (Used in Call Setup Failure event – Section

• Uu_TooManyServersThreshold (Used in Too Many Server event – Section 2.2.2.6)

• Uu_t309_wait_timer (Used in CellChangeOrderfromUTRAN process) Recommended

• Uu_ReEstablishment_wait_timer (Used in ReEstablishment process) Recommended

• Uu_wait_timer_complete (Used in Change Reconfig process) Recommended value

2.2.2 Coverage Related Events

2.2.2.1 System Interference (Attribute Uu_SystemInterference)

Example of system interference before a dropped call

2.2.2.2 Poor Uplink Coverage (Attribute Uu_PoorUL_Coverage)

Example of poor uplink coverage before a dropped call

2.2.2.3 Poor Downlink Coverage (Attribute Uu_PoorDL_Coverage)

Uu_Poor_RSCP_Threshold and the UeTransmittedPower is less than Uu_LowUE_TxPower

Example of poor downlink coverage before a dropped call

2.2.2.4 Coverage Limited (Attribute Uu_CoverageLimited)

Example of coverage limited problem before a dropped call

2.2.2.5 Pilot Pollution (Attribute Uu_PilotPollution)

Example of pilot pollution before a dropped call

2.2.2.6 Too Many Servers (Attribute Uu_TooManyServer)

Example of too many servers around a dropped call

2.2.3 System related Events

2.2.3.1 Handover Problems (Attribute Uu_HandoverProblem)

• Event detection looks for a dropped call or call setup failure

Example of handover problems before a dropped call

2.2.3.2 Missing Neighbours (Attribute Uu_MissingNeighbour)

Example of a missing neighbour before a dropped call

2.2.4 CS domain-related events

2.2.4.1 CS Call Setup (Attribute Uu_CallSetupStatusOrigination,

Note: These thresholds are only used as a initial setting,

Note: RRC Connection Setup & RRC Connection Reject

2.2.4.2 Outgoing Call OK (Attribute Uu_OutgoingCallOk)

• Uu_RRC_MsgType == RRC Connection Request*

• Uu_RRC_MsgType == RRC Connection Setup

• Uu_RRC_MsgType == RRC Connection Setup Complete

• GSM_Um_Msg_Type == MM CM Service Request*

• GSM_Um_Msg_Type == MM Authentication Request (*)

• GSM_Um_Msg_Type == MM Authentication Response (*)

• Uu_RRC_MsgType == Security Mode Command (*)

• Uu_RRC_MsgType == Security Mode Complete (*)

• GSM_Um_Msg_Type == CC Setup (*)

• GSM_Um_Msg_Type == CC Call Proceeding (*)

• Uu_RRC_MsgType == Radio Bearer Setup (*)