Iu Events definition in UMTS-Unify3G v1_0.pdf

Annex Iu Event Definition in UMTS – Unify3G v1.0

November 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.

Iu Event Definition in UMTS – Unify3G v1.0 November 2005

Actix Confidential and Proprietary Page 1

Contents

1 INTRODUCTION......................................................................................................2 1.1 DIAGRAMS ........................................................................................................2

2 CS EVENTS.............................................................................................................4 2.1 IU-CS TRANSPORT EVENT DIAGRAM.................................................................4 2.2 IU-CS CALL OUTGOING DIAGRAM .....................................................................5 2.3 IU-CS CALL INCOMING DIAGRAM.......................................................................8 2.4 IU LOCATION UPDATE DIAGRAM........................................................................9 2.5 ATTRIBUTES FOR IU-CS..................................................................................10

3 PS EVENTS...........................................................................................................15 3.1 IU-PS TRANSPORT EVENT DIAGRAM...............................................................16 3.2 IU-PS CALL HANDLING DIAGRAM.....................................................................17 3.3 IU-PS MOBILITY MANAGEMENT DIAGRAM........................................................19 3.4 IU-PS SESSION MANAGEMENT........................................................................21 3.5 ATTRIBUTES FOR IU-PS ..................................................................................21



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 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

UMTS_Iu_CSCall_Handling.aev

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

UMTS_Iu_PSCall_Handling.aev

RoutingArea_Update Routing Area Updates

UMTS_Iu_Data_Events.aev UMTS_Data_Diagram PDP Context Handling



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 Layer session

tracking (SCCP/RANAP)

UMTS_Iu_CSCall_Outgoing Mobile Originated (MO) CS call handling UMTS_Iu_CSCall_Handling.aev

UMTS_Iu_CSCall_Incoming Mobile Terminated (MT) CS call handling

Iu_LocationUpdate.aev Iu_Location_Update Iu-CS Mobility Management (LAU, IMSI Attach, Detach)

UMTS_Iu_PS_Transport Iu-PS Transport Layer session tracking (SCCP/RANAP)

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

Iu_UMTS_GMM.aev RoutingArea_Update Iu-PS Mobility Management (RAU, PS Attach, PS Detach)

UMTS_Iu_Data_Events.aev UMTS_Data_Diagram PDP Context Handling



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 analyze these main procedures/services:

• MOC (Voice and video)

• MTC (Voice and video)

• Location Area Updates

• IMSI Attach/Detach

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 procedures 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.

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 SMSs are also tracked but no events are set apart from the CS Call Type, which assumes the “SMS” value.

Here below is shown the criteria used for the main Iu-CS Call KPIs:

- Call Setup Failure (Iu_OutgoingCallSetupFail)

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

NOTE: in case of release at NAS level without CC cause being indicated (the information is optional) the call setup is considered failed

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

- Early Terminated Call Setup (Iu_OutgoingEarlyTerminatedCall)

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 (Iu_OutgoingCallOK)

o CC:Alerting

o CC:Connect Ack in case CC:Alerting is not sent (eg. called UE is switched off and answering machine starts )

- Call Dropped (Iu_CallDropped)

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” and “Normal Unspecified”

NOTE: in case of release at NAS level without CC cause being indicated (the information is optional) the call is considered dropped

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”)

- Call Dropped beyond MSC (Iu_CallDroppedBeyondMSC)

This is a special case of call drop event that covers scenarios where the call is dropped due to problems on the other leg of the call.

The signaling for these calls does not show any failure, but only a call release initiated by the MSC at NAS level. The event therefore is useful to detect drop calls even in the case the signaling do not reveal any failure scenario in the monitored leg of the call. The reason for not including this scenario in the normal Call Dropped KPI is the event reflects only the user experience (the call drops for both users) but it does not represent an actual communication failure in the monitored leg of the call.

o After CC:Connect Ack message was sent:

Release at NAS level with cause “Normal Unspecified”

NOTE1: this event is peg only after reaching the Connect phase; if the MSC releases the call with cause “Normal Unspecified” between the Alerting and Connect phases the call is considered Completed, to cope with the case of T301 expiry. Next release will allow the user to specify the T301 value and event engine will be able to differentiate between a call dropped beyond MSC during Alerting and Connect phases and a call completion due to T301 expiry case.

NOTE2: as described in the previous KPI definitions, when MSC release the call with a “Normal Event” CC Cause Class before reaching the Alerting phase the event is stamped as Early Terminated Call Setup

- Call Completed (Iu_CallCompleted)

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 SMSs are also tracked but no events are set apart from the CS Call Type, which assumes the “SMS” value.

The criteria used for MT CS calls KPIs is the same as the one for MO CS calls (see previous section).

These are the attributes associated the main KPIs:

Call Setup Failure à Iu_IncomingCallSetupFail

Early Terminated Call Setup à Iu_IncomingEarlyTerminatedCall

Call Setup Successful à Iu_IncomingCallOK

Call Dropped à Iu_CallDropped

Call Completed à Iu_CallCompleted



2.4 Iu Location Update Diagram

The scope of the Iu Location Update diagram is to trace Mobility Management activity of users in the Iu-CS domain (MM).

Here below is shown the criteria used for the main Iu-CS Mobility Management KPIs:

- Location Update Failure / IMSI Attach Failure

(Iu_LocationUpdateFail, Iu_IMSIAttachFail)

The following scenarios trigger a LU Failure or a IMSI Attach failure depending on the value of Location Update Type field (Normal LU / Peiodic LU / IMSI Attach) - precondition is the detection of a previous Location Update Request message:


o MM:Location Update Reject

o Release of the underlying transport layer (SCCP / Iu -CS Connection) at anytime between SCCP:Connection Confirm and:

§ MM:Location Update Accept if this message does not include new TMSI

§ MM:TMSI Reallocation Complete if Location Update Accept message included new TMSI

NOTE: the diagram does not check any of the LU related timers (T3210..T3213, T3240, T3241 and T3250, T3255). Only at the release of Iu connection in the two clauses above listed will trigger the Location Update Failure event.

- Successful Location Update / Successful IMSI attach

(Iu_LocationUpdateOK, Iu_IMSIAttachOK)



The following scenarios trigger a successful LU or IMSI Attach depending on the value of Location Update Type field (Normal LU / Periodic LU / IMSI Attach) - precondition is the detection of a previous Location Update Request message:

o MM:Location Update Accept if this message does not include new TMSI

o MM:TMSI Reallocation Complete if Location Update Accept message included new TMSI

- Detach (Iu_CS_IMSIDetach)

o MM: Detach Indication

2.5 Attributes for Iu-CS

Attribute Values Triggers

Iu-CS Mobile Originated Calls attributes

Iu_OutgoingCallOK 1 (Event) Successful CS MO Call Setup

See description of KPIs in sec. 2.2

Iu_OutgoingCallSetupFail 1 (Event) CS MO Call Setup failure


Iu_OutgoingEarlyTerminatedCall

1 (Event) CS MO released during setup phase, not due to failures


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 by UE

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

It keeps track of the Iu call sequence state of a CS MOC.

The most important stages are traced, via NAS messages




Iu-CS Mobile Terminated Calls attributes

Iu_IncomingCallOK 1 (Event) Successful CS MT Call Setup


Iu_IncomingCallSetupFail 1 (Event) CS MT Call Setup failure


Iu_IncomingEarlyTerminatedCall 1 (Event)

CS MT released during setup phase, not due to failures


Iu_CallSetupStatusTermination

Same as Iu_CallSetupStatusOrigination

It keeps track of the Iu call sequence state of a CS MTC.

The most important stages are traced, via NAS messages

Generic Iu-CS Calls attributes

Iu_CallCompleted 1 (Event)

Successful CS Call Completion. Note there is no distinction between MOC and MTC.


Iu_CallDropped 1 (Event) CS Call dropped. Note there is no

distinction between MOC and MTC.


Iu_CallDroppedBeyondMSC

1 (Event) CS Call was dropped for reason beyond MSC, typically due to problems in the other leg of the call. Note there is no distinction between MOC and MTC.


Iu_OutCallSetupFailCause

0=Setting up SCCP connection

1=SCCP Connection set up 2=Security Mode ongoing

3=Security Mode OK

When possible, it identifies the event that caused the outgoing call setup failure. Otherwise it shows the last event occurred before the failure

See Iu_OutgoingCallSetupFail for triggers




Iu_InCallSetupFailCause

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 (CN triggered)

21=Iu Released

22=SCCP Connection Refused

23=Iu Release ongoing (RNC triggered)

100=Connection Refused by CN

101=Service Requested 102=Paging Replied

103=Authentication Pending

104=Authentication Completed 105=Authentication failed



108=CC Setup sent

109=Call setup successful (Alerting)

110=Call connected

115=CM Service Aborted

120=Disconnected at NAS

When possible, it identifies the event that caused the incoming call setup failure. Otherwise it shows the last event occurred before the failure

See Iu_IncomingCallSetupFail for triggers

Iu_CallDropCause Disconnected at NAS level,

Disconnected at Transport Level

See Iu_CallDropped for triggers

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




Iu_TimeBetweenInitUEMsgAndCallStart msec.

Call setup time.

It is calculated from the RANAP:InitialUEMsg to the CC:Alerting

Iu-CS Mobility Management attributes

Iu_LocationUpdateOK 1 (Event) Successful LAU


Iu_LocationUpdateFail 1 (Event) Unsuccessful LAU


Iu_IMSIAttachOK 1 (Event) Successful IMSI Attach


Iu_IMSIAttachFail 1 (Event) Unsuccessful IMSI Attach


Iu_CS_IMSIDetach 1 (Event) IMSI Detach


Iu_LocationUpdateDuration msec.

Duration of LU procedure.

It is set only for successful Location Updates:

TimeLU_Accept - TimeLU_Req Or

TimeTMSI_ReallComp - TimeLU_Req

depending on TMSI reallocation

Iu-CS generic attributes

Iu_CS_Outgoing_Call_Type Not defined, Voice, Video, Location Update, SMS, IMSI Attach, IMSI Detach

CM service Request (Emergency call only), SMS signaling, CC:Setup

Iu_CS_Incoming_Call_Type Not defined, Voice, Video, SMS

SMS signaling, CC:Setup




Iu_CS_Transport_Status

-1=Default


1=SCCP Connection set up

2=Security Mode ongoing 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

13=RAB Release failed

20=Iu Release ongoing (CN triggered)

21=Iu Released 22=SCCP Connection refused


It keeps track of the Iu connection sequence state.

The most important stages are traced, via SCCP/RANAP messages

Iu_Call_Id Long

Iu_Call_Id uniquely identifies an SCCP connection over the Iu interface (CS or PS) within a logfile. The attribute is relevant for signaling messages only.

Used to extract the signaling of a call over Iu

Iu_Call_Id_Inc_UserPlane Long

Iu_Call_Id_Inc_UserPlane uniquely identifies an SCCP connection and the associated User plane connections over the Iu interface (CS or PS) within a logfile.

Used to extract the signaling and User Plane of a call over Iu.

NOTE: User Plane over Iu-CS interface is not tracked




IubIu_Call_Id Long IubIu_Call_Id uniquely identifies a connection across Iub and Iu interfaces. The attribute is relevant for signaling messages only (NBAP, ALCAP, RRC, NAS, SCCP, RANAP)

NOTE: If the UE has SCCP connections on both Iu-CS and Iu-PS interfaces then two different IubIu_Call_Id will be allocated

Used to extract the signaling and User plane of a call over Iu and Iub

IubIu_Call_Id_Inc_UserPlane Long IubIu_Call_Id_Inc_UserPlane uniquely identifies a connection over Iu and Iub interface, including user plane data.

NOTE: If the UE has SCCP connections on both Iu-CS and Iu-PS interfaces then two different IubIu_Call_Id_Inc_UserPlane will be allocated

Used to extract the signaling and User plane of a call over Iu and Iub

NOTE: User Plane over Iu-CS interface is not tracked

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 (e.g. FTP, HTTP). From the radio technology point of view all these application services rely on underlying “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

• Routing Area Updates

• PS Attach/Detach



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

Iu-PS User plane is also tracked whenever the signalling for setting up the PDP Context is part of the tracked SCCP/RANAP connection. In always-on networks where the user can maintain the same PDP context for different calls, the Iu-PS User Plane may not be tracked as there is no need to establish the PDP every time a call is originated.

Support Iu-PS User Plane in always-on scenario will be available in a future release.

3.1 Iu-PS Transport Event Diagram

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 CS call handling, only one diagram traces 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 (Iu_OutgoingCallSetupFail_PS, Iu_IncomingCallSetupFail_PS)

For PS connections initiated with a Service Request with Service Type different from “Signaling”:


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 (Iu_OutgoingCallOK_PS, Iu_IncomingCallOK_PS)

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 (Iu_CallDropped_PS)

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 (Iu_CallCompleted_PS)

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



3.3 Iu-PS Mobility Management Diagram

The scope of the Iu-PS Mobility Management Diagram is to trace Mobility Management activity of users in the Iu-PS domain (GMM).

Here below is shown the criteria used for the main Iu-PS Mobility Management KPIs:

- PS Attach Failure (Iu_PS_Attach_Fail)

The following scenarios trigger PS Attach failure (precondition is the detection of a previous Attach Request message):


o GMM:Attach Reject

o Release of the underlying transport layer (SCCP / Iu -PS Connection) at anytime between SCCP:Connection Confirm and:

§ GMM:Attach Accept if this message does not include new P-TMSI

§ GMM:TMSI Reallocation Complete if Attach Accept message included new P-TMSI



o T3350 expiry

- Successful PS Attach (Iu_PS_Attach_OK)

The following scenarios trigger a successful PS Attach - precondition is the detection of a previous Attach Request message:

o GMM:Attach Accept if this message does not include new P-TMSI

o GMM:p-TMSI Reallocation Complete if Attach Accept message included new P-TMSI

- Routing Area Update Failure (Iu_PS_RAU_Fail)

The following scenarios trigger RAU failure (precondition is the detection of a previous RAU Request message):


o GMM:Routing Area Update Reject

o Release of the underlying transport layer (SCCP / Iu -PS Connection) at anytime between SCCP:Connection Confirm (or 1st RAU Request attempt if SCCP connection is already established) and:

§ GMM:RAU Accept if this message does not include new P-TMSI

§ GMM:P-TMSI Reallocation Complete if RAU Accept message included new P-TMSI

o T3350 expiry

- Successful Routing Area Update (Iu_PS_RAU_OK)

The following scenarios trigger a successful Routing Area Update - precondition is the detection of a previous RAU Request message:

o GMM:Routing Area Update Accept if this message does not include new P-TMSI

o GMM:P-TMSI Reallocation Complete if RAU Accept message included new P-TMSI

- PS Detach Failure (Iu_PS_Detach_Fail)

The following scenarios trigger a PS Detach failure - precondition is the detection of a previous GMM: Detach Request message:

o T3321 expiry

o Release of the underlying transport layer (SCCP / Iu -PS Connection) at anytime between SCCP:Connection Confirm (or 1st Detach Request attempt if SCCP connection is already established) and Detach Accept when the Detach is UE initiated

- Successful PS Detach (Iu_PS_Detach_OK)



The following scenarios trigger a successful PS Detach - precondition is the detection of a previous GMM: Request message:

o GMM:Detach Accept message in case of UE initiated Detach

o The GMM: Detach Request message itself in case of Network initiated Detach

3.4 Iu-PS Session Management

This version of Actix provides a simple implementation of Session Management over the Iu-PS interface, based on message detection.

The following basic events are provided:

- PDP Context Activation Failure (Iu_GPRS_PDPContextAct_Successful)

o SM:Activate PDP Context Reject

- Successful PDP Context Activation (Iu_GPRS_PDPContextAct_Reject)

o SM:Activate PDP Context Accept

- Successful PDP Context Deactivation (Iu_GPRS_PDPContextDeAct_Successful)

o SM:Deactivate PDP Context Accept

3.5 Attributes for Iu-PS


PS Mobile Originated Calls attributes

Iu_OutgoingCallOK_PS 1 (Event) Successful PS MO Call Setup


Iu_OutgoingCallSetupFail_PS 1 (Event) PS MO Call Setup failure





Iu_CallSetupStatusOrigination_PS

0=Connection Refused by CN

1=Service Requested

2=Paging Replied 3=Authentication Pending

4=Authentication Completed

5=Authentication failed



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 Request from RNC

15=RAB Release

16=RAB release Completed

17=RAB release Failed 18=Service rejected

*=Others

It keeps track of the Iu call sequence state of a PS MOC.

The most important stages are traced, via NAS messages and RANAP RAB related messages

PS Mobile Terminated Calls attributes

Iu_IncomingCallOK_PS 1 (Event) Successful PS MT Call Setup


Iu_IncomingCallSetupFail_PS 1 (Event) PS MT Call Setup failure


Iu_CallSetupStatusTermination_PS

Same as Iu_CallSetupStatusOrigination_PS

It keeps track of the Iu call sequence state of a PS MTC.

The most important stages are traced, via NAS messages and RANAP RAB related messages

Iu-PS Session Management (PDP) attributes Iu_GPRS_PDPContextAct_Successful 1 (Event)

Successful PDP Context Activation

SM: Activate PDP Context Accept

Iu_GPRS_PDPContextAct_Reject 1 (Event)

PDP Context Activation rejected

SM: Activate PDP Context Reject




Iu_GPRS_PDPContextDeAct_Successful 1 (Event)

Successful PDP Context Deactivation

SM: Deactivate PDP Context Accept

Iu_TimeBetweenPDP_ReqAndAct

msec. TimeAtcDPAcc - TimeActDPReq

Iu_TimeBetweenPDP_ReqAndDeActReq

msec. TimeDeaPDPReq - TimeActPDPReq

Iu_TimeBetweenPDP_DeactReqAndDeAct

msec. TimeDeaPDPAcc – TimeDeaPDPReq

Iu-PS Mobility Management attributes

Succ_1_Attempt .. Succ_5_Attempt

In case of a successful PS Attach, it indicates the number of Attach Request messages sent, within the same Iu-PS connection

Rejected GMM: Attach Reject Iu_PS_Attach

Aborted T3350 expiry

Iu_PS_Attach_OK 1 (Event) Successful PS Attach


Iu_PS_Attach_Fail 1 (Event) Unsuccessful PS Attach


Iu_PS_Attach_Duration msec.

Duration of PS Attach procedure.

It is set only for successful PS Attach:

TimeAtt_Accept – TimeAtt_Req

Or TimeAtt_Comp – TimeAttt_Req

depending on P-TMSI reallocation

Iu_PS_RAU Succ_1_Attempt .. Succ_5_Attempt

In case of a successful RAU, it indicates the number of RAU Request messages sent, within the same Iu-PS connection

Iu_PS_RAU_OK 1 (Event) Successful Routing Area Update


Iu_PS_RAU_Fail 1 (Event) Unsuccessful Routing Area Update


Iu_PS_RAU_Duration msec.

Duration of RAU procedure.

It is set only for successful RAU: TimeRAU_Accept – TimeRAU_Req

Or

TimeRAU_Comp – TimeRAU_Req depending on P-TMSI reallocation




Iu_PS_Detach Succ_1_Attempt .. Succ_5_Attempt

In case of a successful Detach, it indicates the number of Detach Indication messages sent, within the same Iu-PS connection. This is applicable only for UE initiated PS Detach

Iu_PS_Detach_OK 1 (Event) Successful PS Detach


Iu_PS_Detach_Fail 1 (Event) Unsuccessful PS Detach


Generic PS Calls attributes

Iu_CallCompleted_PS 1 (Event)

Successful PS Call Completion. Note there is no distinction between MOC and MTC.


Iu_CallDropped_PS 1 (Event)

PS Call dropped. Note there is no distinction between MOC and MTC.


Iu_PS_Transport_Status

-1=Default


1=SCCP Connection set up

2=Security Mode ongoing

3=Security Mode OK


5=RAB Setup ongoing

9=RAB Setup OK

10=RAB Setup Failed


12=RAB Release OK

13=RAB Release failed 20=Iu Release ongoing (CN triggered)

21=Iu Released

22=SCCP Connection refused


It keeps track of the Iu connection sequence state.

The most important stages are traced, via SCCP/RANAP messages

PS_Background

PS_Interactive

PS_Streaming PS_Conversational

RANAP: RAB Assignment Request (Setup)

Iu_PS_Call_Type

SMS SMS signaling




PS Registration (Attach/RAU) GMM:Attach Request

GMM:RAU Request

PS Detach GMM: Detach Indication

Iu Events definition in UMTS-Unify3G v1_0.pdf

Documents

Transcript of Iu Events definition in UMTS-Unify3G v1_0.pdf