New Iu Events Definition in UMTS

Annex
New Iu Event Definition in

UMTS
February 2005
Confidential and Proprietary

Copyright 1998-2005 Actix Ltd. All Rights Reserved.
No part of this publication may be copied, photocopied, reproduced, transmitted, transcribed,
or reduced to any electronic medium or machine-readable form without the prior written
consent of Actix Ltd.
All brand names and product names included in this book are trademarks, registered
trademarks, or trade names of their respective holders.
New Iu Event Definition in UMTS
February 2005
Contents
1
INTRODUCTION................................................................................................... 2
1.1 DIAGRAMS ..................................................................................................... 2
CS EVENTS .......................................................................................................... 3
2.1 IU-CS TRANSPORT EVENT DIAGRAM ............................................................... 3
2.2 IU-CS CALL OUTGOING DIAGRAM ................................................................... 4
2.3 IU-CS CALL INCOMING DIAGRAM .................................................................... 6
2.4 ATTRIBUTES FOR IU-CS CALL HANDLING ........................................................ 7
PS EVENTS ........................................................................................................ 11
3.1 IU-PS TRANSPORT EVENT DIAGRAM ............................................................. 11
3.2 IU-PS CALL HANDLING DIAGRAM ................................................................... 12
3.3 ATTRIBUTES FOR IU-PS CALL HANDLING ....................................................... 14
Actix Confidential and Proprietary
Page 1
February 2005
1 Introduction
Most of the Event Diagrams based on Iu Interface signalling have been redesigned.
The following analyses were modified:
-
CS Call Handling
PS Call Handling
CS/PS Mobility Management and Session Management events did not change.
The scope of this document is to describe only the changes in the Iu event detection. There
is no description of the events that are handled in unchanged diagrams
1.1
Diagrams
Previously the event diagrams were arranged in the following way:
XML Filename
UMTS_Iu_Events.aev
UMTS_Iu_Data_Events.aev
Diagram name
Type of Analysis/Event
Call_State_01
CS call handling
RoutingArea_Update
Routing Area Updates
Location_Update
Location Updates
UMTS_Data_Diagram
Session management
(PDP Contexts)
This is the new structure (new/modified diagrams in bold):
XML Filename
UMTS_Iu_CSCall_Handling.aev
UMTS_Iu_PSCall_Handling.aev
Diagram name
Type of Analysis/Event
UMTS_Iu_CS_Transport
Iu-CS Transport Layer

session tracking
(SCCP/RANAP)
UMTS_Iu_CSCall_Outgoing
Mobile Originated (MO)

CS call handling
UMTS_Iu_CSCall_Incoming
Mobile Terminated (MT)

CS call handling
Location_Update
Location Area Updates
UMTS_Iu_PS_Transport
Iu-PS Transport Layer

session tracking
(SCCP/RANAP)
PS_Event_Layer
Mobile Originated (MO)

and Mobile Terminated
(MT) PS call handling
RoutingArea_Update
Page 2
February 2005
2 CS Events
Events in the CS domain are referred to services like AMR Voice Call, UDI Video Call, SMS
and Mobility Management procedures (IMSI Attach, Location Area Update, IMSI Detach).
Current Iu diagrams handle these main procedures/services:
MOC (Voice and video)
MTC (Voice and video)
Location Area Updates
In addition each SCCP Connection established over the Iu-CS interface is traced, together
with the RANAP messages eventually exchanged over the SCCP connection.
2.1
Iu-CS Transport Event Diagram
The scope of the Iu-CS transport diagram is to trace the main SCCP/RANAP procedure of
each Iu-CS Signalling Connection.
Some of the information set in this diagram is used in the upper layers diagrams that handle
CS calls and Mobility management procedures across the Iu-CS interface. The most
important of this information is the status of the Iu-connection itself (up, down, establishing,
releasing, etc.). The upper layer diagrams in fact rely on the presence of the underlying Iu
Connection.
Page 3
2.2
February 2005
Iu-CS Call Outgoing Diagram
The scope of the Iu-CS Call Outgoing diagram is to trace MO CS Calls, both AMR voice
(12.2 kbps) and UDI Video (64 kbps). Originated SMS is not tracked.
Here below is shown the criteria used for the main CS Call KPIs:
Call Setup Failure

o The SCCP Connection is refused by the MSC
o CM Service Abort
o Anytime before CC:Alerting, release at NAS level with any of the following CC
Cause classes:
Resource Unavailable
Invalid Message
Protocol Error
o Normal Release at NAS level due to previous RAB Setup Failure

o Release of the underlying transport layer (SCCP / Iu-CS Connection) at anytime
between SCCP:Connection Confirm and CC:Alerting
Page 4
February 2005
Early Terminated Call Setup

An Early Terminated Call is a call that does not reach the Successful Setup state but at
the same time is not considered a Call Setup Failure, for example because the called
party rejected the call. It is important to isolate these cases because they normally do
not represent abnormal or failure scenarios in the network.
o Anytime between CC:Setup and CC:Alerting, release at NAS level with any of the
following CC Cause classes:
Normal Event
Service Option not Available
Service Option not Implemented
Typical examples of release cause that falls in these criteria are:

- User busy
- Call rejected
- Unassigned number
Also a NAS release with cause Normal Call Clearing during a RAB Setup
procedure is considered an Early Terminated Call Setup and not a Call setup
Failure
Call Setup Successful

o CC:Alerting
o CC:Connect Ack in case CC:Alerting is not sent (eg. called UE is switched off)
Call Dropped
A call drop event can be set only if the call reached the Successful Call setup state.
o If CC:Connect Ack message is not sent yet:
Release at NAS level with any of the following CC Cause classes:
Resource Unavailable
Invalid Message
Protocol Error
o If CC:Connect Ack message was sent:

Release at NAS level with any cause other than Normal Call clearing
o Release of the underlying transport layer (SCCP / Iu-CS Connection) not being
preceded by a release at NAS level. The only exception is when the Iu connection
is released due to successful completion of an outgoing SRNS Relocation
procedure (Iu Release with cause Successful Relocation)
Page 5

-
February 2005
Call Completed
o If CC:Connect Ack message is not sent yet:
Release at NAS level with any of the following CC Cause classes:
Normal Event
Service option not Available
Service option not Implemented
o If CC:Connect Ack message was sent:

Release at NAS level with Normal Call clearing
o Release of the underlying transport layer (SCCP / Iu-CS Connection) due to
successful completion of an outgoing SRNS Relocation procedure (Iu Release
with cause Successful Relocation)
2.3
Iu-CS Call Incoming Diagram
The scope of the Iu-CS Call Outgoing diagram is to trace MT CS Calls, both AMR voice
(12.2 kbps) and UDI Video (64 kbps). Terminated SMS is not tracked.
The criteria used for MT CS calls KPIs is the same as the one for MO CS calls (see previous
section).
Page 6
February 2005
Additional notes on MT calls:

RANAP Paging message is currently not tracked in the diagram. For this reason the type of
terminating call sometimes cannot be detected until the CC:Setup message. Also MT Calls
that fails at the very early stage (no Paging response) will not be detected. Tracking of
RANAP Paging messages will be introduced in the next release
2.4
Attributes for Iu-CS Call Handling
Attribute
Values
Triggers
CS Mobile Originated Calls attributes
Iu_OutgoingCallOK
1 (Event)
Iu_OutgoingCallSetupFail
1 (Event)
0=Connection Refused by CN
1=Service Requested
2=Paging Replied
3=Authentication Pending
4=Authentication Completed
Successful CS MO
Call Setup.
See description of
KPIs in sec. 2.2
CS MO Call Setup
failure.
See description of
KPIs in sec. 2.2
It keeps track of the
Iu call sequence
state of a CS MOC.
The most important
stages are traced,
via NAS messages.
5=Authentication failed
6=Authentication Rejected by
UE
Iu_CallSetupStatusOrigination
7=T3260 Expired (No Auth.

Response)
8=CC Setup sent
9=Call setup successful
(Alerting)
10=Call connected
15=CM Service Aborted
20=Disconnected at NAS level
21=Disconnected at Transport
Level
*=Other
CS Mobile Terminated Calls attributes
Iu_IncomingCallOK
1 (Event)
Successful CS MT
Call Setup.
See description of
KPIs in sec. 2.2
Page 7
February 2005
Attribute
Values
Iu_IncomingCallSetupFail
1 (Event)
1=Service Requested
2=Paging Replied
Triggers
CS MT Call Setup
failure.
See description of
KPIs in sec. 2.2
Iu call sequence
state of a CS MTC.
The most important
stages are traced,
via NAS messages
UE
Response)
Iu_CallSetupStatusTermination
8=CC Setup sent

(Alerting)
10=Call connected
20=Disconnected at NAS level
21=Disconnected at Transport
Level
*=Other
Generic CS Calls attributes
Iu_CallCompleted
1 (Event)
Successful CS Call
Completion. Note
there is no distinction
between MOC and
MTC.
See description of
KPIs in sec. 2.2
1 (Event)
Iu_CallDropped
CS Call dropped.
Note there is no
distinction between
MOC and MTC.
See description of
KPIs in sec. 2.2
Page 8
Attribute
February 2005
Values
Triggers
0=Setting up SCCP
connection
When possible, it
identifies the event
that caused the call
setup failure.
Otherwise it shows
the last event
occurred before the
failure.
1=SCCP Connection set up

2=Security Mode ongoing
3=Security Mode OK
4=Security mode Failed
5=RAB Setup ongoing
9=RAB Setup OK
10=RAB Setup Failed
11=RAB Release ongoing
12=RAB Release OK
See
Iu_OutgoingCallSetu
pFail and
Iu_IncomingCallSetu
pFail for triggers.
13=RAB Release failed

20=Iu Release ongoing (CN
triggered)
21=Iu Released
22=SCCP Connection
Refused
Iu_CallSetupFailCause
23=Iu Release ongoing (RNC

triggered)
100=Connection Refused by
CN
101=Service Requested
102=Paging Replied
106=Authentication Rejected
by UE
Response)
108=CC Setup sent
(Alerting)
110=Call connected
120=Disconnected at NAS
Disconnected at NAS level,
Iu_CallDropCause
Disconnected at Transport
Level
See Iu_CallDropped
for triggers.
Page 9
Attribute
Iu_CS_Call_Type
February 2005
Values
Triggers
Not defined, Voice, Video
CM service Request
(Emergency call
only), RANAP:RAB
Ass.Request or
CC:Setup.
-1=Default
0=Setting up SCCP
connection
3=Security Mode OK

Iu connection
sequence state.
The most important
stages are traced,
via SCCP/RANAP
messages.

5=RAB Setup ongoing
6=Setting up Iu AAL2
7=AAL2 set up OK
Iu_CS_Transport_Status
8=AAL2 setup failed

9=RAB Setup OK
10=RAB Setup Failed
12=RAB Release OK
triggered)
21=Iu Released
22=SCCP Connection refused
triggered)
Iu_CallDuration
msec.
Call duration is
calculated from the
CC:Connect ACK to
the moment the call
is completed or
dropped.
NOTE: Calls
released/dropped
between Alerting and
Call setup have Call
Duration = 0
Call setup time.
Iu_TimeBetweenInitUEMsgAndCa
llStart
msec.
It is calculated from
the
RANAP:InitialUEMsg
to the CC:Alerting
Page 10
February 2005
3 PS Events
Events in the PS domain are referred to services like Web Browsing, File download, Video
Streaming, MMS, Session Management procedures (PDP Context Activation/Deactivation)
and Mobility Management procedures (PS Attach, Routing Area Update, PS Detach).
It should be noted that the Iu-PS event diagrams do not handle events in the application
layer (eg FTP, HTTP). From the radio technology point of view all these application services
are considered Packet Calls.
There could be more than one definition of Packet Call over the Iu interface. For example a
Packet Call can be considered equivalent to a PDP Session or to PS RAB Session; in the
following sections the definition of packet calls over the Iu interface adopted by Actix is
described.
Current Iu diagrams handle these main procedures/services:
PS MOC (Packet Switch Mobile Originated Call)
PS MTC (Packet Switch Mobile Terminated Call)
PDP Context Activation/Deactivation
In addition each SCCP Connection established over the Iu-PS interface is traced, together
with the RANAP messages eventually exchanged over the SCCP connection.
3.1
Iu-PS Transport Event Diagram
Page 11
February 2005
The scope of the Iu-PS transport diagram is to trace the main SCCP/RANAP procedure of
each Iu-PS Signalling Connection.
Some of the information set in this diagram is used in the upper layers diagrams that handle
PS calls and Mobility management procedures across the Iu-PS interface. The most
important of this information is the status of the Iu-connection itself (up, down, establishing,
releasing, etc.). The upper layer diagrams in fact rely on the presence of the underlying Iu
Connection.
3.2
Iu-PS Call handling Diagram
Unlike for CS call handling, there is only one diagram that trace PS Calls.
Definition of PS call over the Iu-PS Interface:
A PS call is equivalent to a RAB instance.
However a PS call does not necessarily starts at the RAB Setup RANAP procedure.
Whenever it is possible to derive from the signalling that an attempt to establish a PS call is
ongoing, even before the RAB setup phase, an attempt of establishing a PS call is detected
by the diagram. For example a Service Request message with service type Data implies
that a RAB needs to be established to transfer data for the new service requested.
Details on the triggers for PS Calls related events are provided below in the KPIs
description.
Call Setup Failure

For PS connections initiated with a Service Request with Service Type different from
Signalling:
o The SCCP Connection is refused by the MSC
Page 12
February 2005
o Service Reject
o Release of the underlying transport layer (SCCP / Iu-PS Connection) at anytime
between SCCP:Connection Confirm and RAB Assignment Request (Setup)
For any PS connection:
o RAB Assignment Response (Failure to Setup)
o Activation PDP Context Reject (if not due to RAB Setup failure see above
trigger)
o Release of the underlying transport layer (SCCP / Iu-PS Connection) at anytime
between RAB Assignment Request (Setup) and successful completion of the Call
Setup (RAB Assignment Response or Activation PDP Context Accept)
Call Setup Successful

o Activation PDP Context Accept
o RAB Assignment Response (Setup) if the RAB Setup procedure is not part of a
PDP Context Activation (i.e. the PDP Context is already established)
Call Dropped
A call drop event can be set only if the call reached the Successful Call setup state.
o RAB Assignment Request (Release) with a release cause different from Normal
Release
o RAB Assignment Request (Release) if the request was initiated by the RNC (via
previous RAB Release Request)
o In case of PS RABs still set up, release of the underlying transport layer (SCCP /
Iu-PS Connection) with cause different from:
Successful Relocation
User Inactivity
NAS Normal release
Call Completed
o RAB Assignment Response (Released) with a release cause Normal Release
o In case of PS RAB(s) still set up, release of the underlying transport layer (SCCP /
Iu-PS Connection) with any of the following causes:
Successful Relocation
User Inactivity
NAS Normal release
Page 13
3.3
February 2005
Attributes for Iu-PS Call Handling
Attribute
Values
Triggers
PS Mobile Originated Calls attributes
Iu_OutgoingCallOK_PS
1 (Event)
Iu_OutgoingCallSetupFail_PS
1 (Event)
1=Service Requested
2=Paging Replied
UE
Successful PS MO
Call Setup.
See description of
KPIs in sec. 3.2
PS MO Call Setup
failure.
See description of
KPIs in sec. 3.2
Iu call sequence
state of a PS MOC.
The most important
stages are traced,
via NAS messages
and RANAP RAB
related messages.

Response)
8=PDP Act. Pending
Iu_CallSetupStatusOrigination_PS
9=PDP Act.Complete
10=PDP Act. Rejected
11=PS RAB Setup ongoing
12=RAB Setup completed
13=RAB setup failed
14=RAB Release Request
from RNC
15=RAB Release
16=RAB release Completed
17=RAB release Failed
18=Service rejected
*=Others
PS Mobile Terminated Calls attributes
Iu_IncomingCallOK_PS
1 (Event)
Successful PS MT
Call Setup
See description of
KPIs in sec. 3.2
Page 14
February 2005
Attribute
Values
Iu_IncomingCallSetupFail_PS
1 (Event)
1=Service Requested
2=Paging Replied
UE
Triggers
PS MT Call Setup
failure
See description of
KPIs in sec. 3.2
Iu call sequence
state of a PS MTC.
The most important
stages are traced,
via NAS messages
and RANAP RAB
related messages.

Response)
8=PDP Act. Pending
Iu_CallSetupStatusTermination_P
S
9=PDP Act.Complete
10=PDP Act. Rejected
11=PS RAB Setup ongoing
12=RAB Setup completed
13=RAB setup failed
14=RAB Release Request
from RNC
15=RAB Release
16=RAB release Completed
17=RAB release Failed
18=Service rejected
*=Others
Generic PS Calls attributes
Iu_CallCompleted_PS
1 (Event)
Successful PS Call
Completion. Note
there is no distinction
between MOC and
MTC.
See description of
KPIs in sec. 3.2
1 (Event)
Iu_CallDropped_PS
PS Call dropped.
Note there is no
distinction between
MOC and MTC.
See description of
KPIs in sec. 3.2
Page 15
Attribute
February 2005
Values
Triggers
-1=Default

Iu connection
sequence state.
0=Setting up SCCP
connection
3=Security Mode OK
The most important

stages are traced,
via SCCP/RANAP
messages.

5=RAB Setup ongoing
9=RAB Setup OK
Iu_PS_Transport_Status
10=RAB Setup Failed

12=RAB Release OK
triggered)
21=Iu Released
22=SCCP Connection refused
triggered)
Page 16

New Iu Events Definition in UMTS

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

New Iu Events Definition in UMTS

Enviado por

Direitos autorais:

Formatos disponíveis

Annex

New Iu Event Definition in

Confidential and Proprietary

New Iu Event Definition in UMTS

Actix Confidential and Proprietary

New Iu Event Definition in UMTS

Previously the event diagrams were arranged in the following way:

Routing Area Updates

This is the new structure (new/modified diagrams in bold):

Actix Confidential and Proprietary

Iu-CS Transport Layer

Mobile Originated (MO)

Mobile Terminated (MT)

Location Area Updates

Iu-PS Transport Layer

Mobile Originated (MO)

Routing Area Updates

New Iu Event Definition in UMTS

Iu-CS Transport Event Diagram

Actix Confidential and Proprietary

New Iu Event Definition in UMTS

Iu-CS Call Outgoing Diagram

Call Setup Failure

o Normal Release at NAS level due to previous RAB Setup Failure

Actix Confidential and Proprietary

New Iu Event Definition in UMTS

Early Terminated Call Setup

Service Option not Available

Service Option not Implemented

Typical examples of release cause that falls in these criteria are:

Call Setup Successful

o If CC:Connect Ack message was sent:

Actix Confidential and Proprietary

New Iu Event Definition in UMTS

Service option not Available

Service option not Implemented

o If CC:Connect Ack message was sent:

Iu-CS Call Incoming Diagram

Actix Confidential and Proprietary

New Iu Event Definition in UMTS

Additional notes on MT calls:

Attributes for Iu-CS Call Handling

CS Mobile Originated Calls attributes

7=T3260 Expired (No Auth.

CS Mobile Terminated Calls attributes

Actix Confidential and Proprietary

New Iu Event Definition in UMTS

8=CC Setup sent

Actix Confidential and Proprietary

New Iu Event Definition in UMTS

1=SCCP Connection set up

13=RAB Release failed

23=Iu Release ongoing (RNC

Actix Confidential and Proprietary

New Iu Event Definition in UMTS

Not defined, Voice, Video

It keeps track of the

4=Security mode Failed

8=AAL2 setup failed

Actix Confidential and Proprietary

New Iu Event Definition in UMTS

PS MOC (Packet Switch Mobile Originated Call)

PS MTC (Packet Switch Mobile Terminated Call)

PDP Context Activation/Deactivation