New Iu Events Definition in UMTS

8/9/2019 New Iu Events Definition in UMTS

1/18

AnnexNew Iu Event Definition inUMTS

February 2005


2/18

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 writtenconsent of Actix Ltd.

All brand names and product names included in this book are trademarks, registered

trademarks, or trade names of their respective holders.


3/18

New Iu Event Definition in UMTS February 2005

Actix Confidential and Proprietary Page 1

Contents

1 INTRODUCTION................................................................................................... 2

1.1 DIAGRAMS ..................................................................................................... 2

2 CS EVENTS.......................................................................................................... 3

2.1

IU-CS TRANSPORT EVENT DIAGRAM............................................................... 3

2.2 IU-CS C ALL OUTGOING DIAGRAM ................................................................... 4

2.3 IU-CS C ALL INCOMING DIAGRAM .................................................................... 6

2.4 ATTRIBUTES FOR IU-CS C ALL H ANDLING ........................................................ 7

3 PS EVENTS ........................................................................................................ 11

3.1 IU-PS TRANSPORT EVENT DIAGRAM ............................................................. 11

3.2 IU-PS C ALL HANDLING DIAGRAM................................................................... 12

3.3 ATTRIBUTES FOR IU-PS C ALL H ANDLING....................................................... 14


4/18



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. Thereis 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 Diagram name Type of Analysis/Event

Call_State_01 CS call handling

RoutingArea_Update Routing Area UpdatesUMTS_Iu_Events.aev

Location_Update Location Updates

UMTS_Iu_Data_Events.aev UMTS_Data_Diagram Session management(PDP Contexts)

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

XML Filename Diagram name Type of Analysis/Event

UMTS_Iu_CS_Transport Iu-CS Transport Layersession tracking(SCCP/RANAP)

UMTS_Iu_CSCall_Outgoing Mobile Originated (MO)CS call handling

UMTS_Iu_CSCall_Incoming Mobile Terminated (MT)CS call handling

UMTS_Iu_CSCall_Handling.aev

Location_Update Location Area Updates

UMTS_Iu_PS_Transport Iu-PS Transport Layersession tracking

(SCCP/RANAP)

PS_Event_Layer Mobile Originated (MO)and Mobile Terminated(MT) PS call handling

UMTS_Iu_PSCall_Handling.aev

RoutingArea_Update Routing Area Updates


5/18


6/18



2.2 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 CCCause 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 anytimebetween SCCP:Connection Confirm and CC:Alerting


7/18



- Early Terminated Call Setup

An Early Terminated Call is a call that does not reach the Successful Setup state but atthe same time is not considered a Call Setup Failure, for example because the calledparty rejected the call. It is important to isolate these cases because they normally donot represent abnormal or failure scenarios in the network.

o Anytime between CC:Setup and CC:Alerting, release at NAS level with any of thefollowing 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 Setupprocedure is considered an Early Terminated Call Setup and not a Call setupFailure

- 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 beingpreceded by a release at NAS level. The only exception is when the Iu connectionis released due to successful completion of an outgoing SRNS Relocationprocedure (Iu Release with cause “”Successful Relocation”)


8/18



- 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 tosuccessful completion of an outgoing SRNS Relocation procedure (Iu Releasewith 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 previoussection).


9/18



Additional notes on MT calls:

RANAP Paging message is currently not tracked in the diagram. For this reason the type ofterminating call sometimes cannot be detected until the CC:Setup message. Also MT Callsthat fails at the very early stage (no Paging response) will not be detected. Tracking ofRANAP Paging messages will be introduced in the next release

2.4 Att ributes for Iu-CS Call Handling

At tr ibute Values Triggers

CS Mobile Originated Calls attributes

Iu_OutgoingCallOK 1 (Event)

Successful CS MOCall Setup.

See description ofKPIs in sec. 2.2

Iu_OutgoingCallSetupFail 1 (Event)

CS MO Call Setupfailure.


Iu_CallSetupStatusOrigination

0=Connection Refused by CN

1=Service Requested

2=Paging Replied

3=Authentication Pending

4=Authentication Completed

5=Authentication failed

6=Authentication Rejected byUE

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 TransportLevel

*=Other

It keeps track of theIu call sequencestate of a CS MOC.

The most importantstages are traced,via NAS messages.

CS Mobile Terminated Calls attributes

Iu_IncomingCallOK 1 (Event)

Successful CS MTCall Setup.



10/18




Iu_IncomingCallSetupFail 1 (Event)

CS MT Call Setupfailure.


Iu_CallSetupStatusTermination

0=Connection Refused by CN1=Service Requested

2=Paging Replied





7=T3260 Expired (No Auth.Response)

8=CC Setup sent9=Call setup successful(Alerting)

10=Call connected


20=Disconnected at NAS level

21=Disconnected at TransportLevel

*=Other

It keeps track of theIu call sequencestate of a CS MTC.

The most importantstages are traced,via NAS messages

Generic CS Calls attributes

Iu_CallCompleted 1 (Event)

Successful CS CallCompletion. Notethere is no distinctionbetween MOC andMTC.


Iu_CallDropped

1 (Event) CS Call dropped.Note there is nodistinction betweenMOC and MTC.

See description of

KPIs in sec. 2.2


11/18




Iu_CallSetupFailCause

0=Setting up SCCPconnection

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

13=RAB Release failed

20=Iu Release ongoing (CNtriggered)

21=Iu Released

22=SCCP ConnectionRefused

23=Iu Release ongoing (RNCtriggered)

100=Connection Refused byCN

101=Service Requested

102=Paging Replied


104=Authentication Completed105=Authentication failed

106=Authentication Rejectedby UE


108=CC Setup sent

109=Call setup successful(Alerting)

110=Call connected


120=Disconnected at NAS

When possible, itidentifies the eventthat caused the callsetup failure.Otherwise it showsthe last eventoccurred before thefailure.

SeeIu_OutgoingCallSetupFail andIu_IncomingCallSetupFail for triggers.

Iu_CallDropCause

Disconnected at NAS level,

Disconnected at TransportLevel

See Iu_CallDroppedfor triggers.


12/18




Iu_CS_Call_Type Not defined, Voice, Video

CM service Request(Emergency callonly), RANAP:RAB Ass.Request orCC:Setup.

Iu_CS_Transport_Status

-1=Default




3=Security Mode OK


5=RAB Setup ongoing

6=Setting up Iu AAL2

7=AAL2 set up OK

8=AAL2 setup failed

9=RAB Setup OK

10=RAB Setup Failed


12=RAB Release OK


20=Iu Release ongoing (CNtriggered)

21=Iu Released

22=SCCP Connection refused


It keeps track of theIu connectionsequence state.

The most importantstages are traced,via SCCP/RANAPmessages.

Iu_CallDuration msec.

Call duration iscalculated from theCC:Connect ACK tothe moment the callis completed ordropped.

NOTE: Callsreleased/droppedbetween Alerting and

Call setup have CallDuration = 0

Iu_TimeBetweenInitUEMsgAndCallStart

msec.

Call setup time.

It is calculated fromtheRANAP:InitialUEMsgto the CC:Alerting


13/18



3 PS Events

Events in the PS domain are referred to services like Web Browsing, File download, VideoStreaming, 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 applicationlayer (eg FTP, HTTP). From the radio technology point of view all these application servicesare considered “Packet Calls”.

There could be more than one definition of Packet Call over the Iu interface. For example aPacket Call can be considered equivalent to a PDP Session or to PS RAB Session; in thefollowing sections the definition of packet calls over the Iu interface adopted by Actix isdescribed.

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

• Routing Area Updates

In addition each SCCP Connection established over the Iu-PS interface is traced, togetherwith the RANAP messages eventually exchanged over the SCCP connection.

3.1 Iu-PS Transport Event Diagram


14/18



The scope of the Iu-PS transport diagram is to trace the main SCCP/RANAP procedure ofeach Iu-PS Signalling Connection.

Some of the information set in this diagram is used in the upper layers diagrams that handlePS calls and Mobility management procedures across the Iu-PS interface. The mostimportant 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 isongoing, even before the RAB setup phase, an attempt of establishing a PS call is detectedby 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 KPIsdescription.

- 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


15/18



o Service Reject

o Release of the underlying transport layer (SCCP / Iu-PS Connection) at anytimebetween 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 abovetrigger)

o Release of the underlying transport layer (SCCP / Iu-PS Connection) at anytimebetween RAB Assignment Request (Setup) and successful completion of the CallSetup (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 aPDP 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 “NormalRelease”

o RAB Assignment Request (Release) if the request was initiated by the RNC (viaprevious 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


16/18



3.3 Att ributes for Iu-PS Call Handling


PS Mobile Originated Calls attributes

Iu_OutgoingCallOK_PS 1 (Event)

Successful PS MOCall Setup.


Iu_OutgoingCallSetupFail_PS 1 (Event)

PS MO Call Setupfailure.


Iu_CallSetupStatusOrigination_PS

0=Connection Refused by CN

1=Service Requested

2=Paging Replied






8=PDP Act. Pending

9=PDP Act.Complete

10=PDP Act. Rejected

11=PS RAB Setup ongoing

12=RAB Setup completed

13=RAB setup failed

14=RAB Release Requestfrom RNC

15=RAB Release

16=RAB release Completed

17=RAB release Failed

18=Service rejected

*=Others

It keeps track of theIu call sequencestate of a PS MOC.

The most importantstages are traced,via NAS messagesand RANAP RABrelated messages.

PS Mobile Terminated Calls attributes

Iu_IncomingCallOK_PS 1 (Event)

Successful PS MTCall Setup



17/18




Iu_IncomingCallSetupFail_PS 1 (Event)

PS MT Call Setupfailure


Iu_CallSetupStatusTermination_PS

0=Connection Refused by CN1=Service Requested

2=Paging Replied






8=PDP Act. Pending9=PDP Act.Complete

10=PDP Act. Rejected

11=PS RAB Setup ongoing

12=RAB Setup completed

13=RAB setup failed

14=RAB Release Requestfrom RNC

15=RAB Release

16=RAB release Completed

17=RAB release Failed18=Service rejected

*=Others

It keeps track of theIu call sequencestate of a PS MTC.

The most importantstages are traced,via NAS messagesand RANAP RABrelated messages.

Generic PS Calls attributes

Iu_CallCompleted_PS 1 (Event)

Successful PS CallCompletion. Notethere is no distinctionbetween MOC andMTC.


Iu_CallDropped_PS

1 (Event) PS Call dropped.Note there is nodistinction betweenMOC and MTC.



18/18




Iu_PS_Transport_Status

-1=Default




3=Security Mode OK


5=RAB Setup ongoing

9=RAB Setup OK

10=RAB Setup Failed


12=RAB Release OK


20=Iu Release ongoing (CN

triggered)

21=Iu Released

22=SCCP Connection refused


It keeps track of theIu connectionsequence state.

The most important

stages are traced,via SCCP/RANAPmessages.

Documents

New Iu Events Definition in UMTS