Signaling Training Iu-PS

Anritsu Confidential Information

Summary
• • • • • • • • High level Description Network Diagrams Protocol Stack Main Procedures Messages Flow Diagrams Typical Problems Hands On Acronyms and References

Anritsu Confidential Information

High level Description
• Purpose of this presentation is provide an introduction to Iu-PS interface, Protocol Stack and the main procedures in this interface • The Iu interface is between the Core Network and UTRAN. The Iu interface towards the PS-domain of the core network is called Iu-PS • In another words Iu-PS is the interface between RNC and SGSN

Anritsu Confidential Information

Network Diagrams
PABX
A-bis INAP ISDN

IN
MAP ISUP

BSC
Gb

A

MSC
MAP

GMSC
MAP ISUP

Um Iu-CS Gs

R

SMSC
EIR
Gf Gd Gr

PSTN/ISDN PDN Internet/Intranet/ISP

RNC
Iur Iub Node B Iub Uu Node B

HLR
Gc

AUC

RNC

Iu-PS

SGSN GPRS Gn GGSN
Gp Private Backbone Gn

Gi

GRX

Anritsu Confidential Information

Protocol Stack
Radio Network Layer
Control Plane RANAP User Plane Iu UP Protocol Layer

Transport Network Layer

Transport Network User Plane
SCCP MTP3-B M3UA SCTP SSCF-NNI SSCOP AAL5 IP IP M3UA SCTP

Transport Network Control Plane

Transport Network User Plane

GTP-U UDP IP AAL5

GTP-U UDP

IP

ATM

Data Link

ATM

Data Link

Physical Layer

Physical Layer

Anritsu Confidential Information

modifying and releasing RABs • Radio Access Bearer (RAB) as a user plane connection provided by the UMTS Terrestrial Radio Access Network (UTRAN) between a User Equipment (UE) and the Core Network. This function enables to change the serving RNC functionality as well as the related Iu resources (RAB(s) and Signalling connection) from one RNC to another Anritsu Confidential Information . QoS.Radio Access Network Application Part • Major Functions of RANAP – Overall RAB management. • The general characteristics of a RAB (data rates. This function is responsible for setting up. etc) are normally set by the Core Network (CN) based on subscription and/or requirements of the media or set of medias using the RAB.RANAP . – Relocating serving RNC.

This function provides the CN for capability to page the UE – Transport of NAS information between UE and CN – Controlling the security mode in the UTRAN. This function makes the RNC aware of the UE's Common ID – Paging the user.Radio Access Network Application Part – Sending the UE Common ID (permanent NAS UE identity) to the RNC. – Location reporting.RANAP . the Location Reporting Control procedure is to allow the CN to request information on the location of a given UE Anritsu Confidential Information . and setting the operation mode for security functions. This function is used to send the security keys (ciphering and integrity protection) to the UTRAN.

Main Procedures List of main procedures: • Attach • Detach • Routing Area Update (RAU) • PDP Context Activation • Secondary PDP Context Activation • PDP Context Deactivation • PDP Context Modification • Service Request • Handovers – SRNS Relocation (With and without Iur interface) Anritsu Confidential Information .

Attach • The GPRS attach procedure is used for two purposes – Normal GPRS attach. an ATTACH ACCEPT message is sent to the MS. This message will include a cause value indicating the reason for reject Attach procedure can used to reallocate P-TMSI/TMSI. – If the GPRS attach request is accepted by the network. performed by the MS to IMSI attach for GPRS services only. In such cases MS will send ATTACH COMPLETE message after receiving ATTACH ACCEPT message • • Anritsu Confidential Information . used to attach the IMSI for GPRS and non-GPRS services. The attach type information element shall indicate "GPRS attach". – Combined GPRS attach procedure. The MS initiates the GPRS attach procedure by sending an ATTACH REQUEST message to the network. – If the attach request cannot be accepted by the network. an ATTACH REJECT message is transferred to the MS.

Attach (Successful) .Messages Flow MS ATTACH REQUEST Network ATTACH ACCEPT If P-TMSI and/or TMSI allocated ATTACH COMPLETE or ATTACH REQUEST ATTACH REJECT Anritsu Confidential Information .

Security Mode Command DTI .Messages Flow RNC CR – Attach Request CC DTI – GPRS Identity Request DTI .Security Mode Complete END – SendAuthenticationInfoRes Scenario: GPRS Attach Attach type information element in Attach Request message indicates "GPRS attach" SGSN HLR OLD SGSN Attach Request send by MS Attach is accepted by the network after successful „update GPRS Location‟ procedure UpdateGPRSLocation and InsertSubscriberData procedures DTI .SendAuthenticationInfoArg DTI – Authentication and Ciphering Req DTI .Common ID DTI .GPRS Identity Response BEGIN .Attach Complete DTI – Iu Release Command DTI – Iu Release Complete RLSD RLC Cancel Location procedure Attach Complete message is send by the UE if there is a PTMSI and/or a TMSI was included within the attach accept message (Implicit P-TMSI reallocation) RANAP Connection Release SCCP Connection Release Anritsu Confidential Information .Authentication and Ciphering Resp DTI .Attach (Successful) .Attach Accept DT1 .

„RoamingNotAllowed‟ Attach is Rejected by the network with the cause value „Roaming not allowed in this location area‟ UpdateGPRSLocation procedure failed DTI .Attach Reject DTI – Iu Release Command DTI – Iu Release Complete RLSD RLC Anritsu Confidential Information .Attach (Unsuccessful) .SendAuthenticationInfoArg DTI – Authentication and Ciphering Req DTI .Common ID DTI – GPRS Identity Request SGSN HLR Scenario: GPRS Attach Attach type information element in Attach Request message indicates "GPRS attach" Attach Request send by MS DTI .Authentication and Ciphering Resp DTI .Security Mode Command DTI .Security Mode Complete END – SendAuthenticationInfoRes UpdateGPRSLocation procedure fails with the cause value.Messages Flow RNC CR – Attach Request CC DT1 .GPRS Identity Response BEGIN .

The DETACH REQUEST message shall include a detach type IE. "GPRS/IMSI detach with switching off" or "GPRS/IMSI detach without switching off". "IMSI detach". – In case the network initiates the GPRS detach procedure it sends a DETACH REQUEST message to the MS. The detach type information element may indicate "GPRS detach with switching off". The detach type IE indicates "re-attach not required" or "re-attach required" Anritsu Confidential Information . "GPRS detach without switching off".Detach • The GPRS detach procedure is used – To detach the IMSI for GPRS services only – As a combined GPRS detach procedure used to detach the IMSI for GPRS and non-GPRS services or for non-GPRS services only – Detach procedure can be initiated by the MS or the Network – The GPRS detach procedure is initiated by the MS by sending a DETACH REQUEST message.

Detach – Message Flow MS DETACH REQUEST DETACH ACCEPT Network initiated Detach Network MS initiated Detach or at MS power switch off DETACH REQUEST MS DETACH REQUEST DETACH ACCEPT Network Anritsu Confidential Information .

Detach type IE indicates „GPRS detach without switching off „ All ongoing control plane procedures are aborted Anritsu Confidential Information .Detach (Successful) – Message Flow RNC CR – Detach Request CC DTI – Common ID DTI – Detach Accept DTI – Iu-Release Command DTI – Iu-Release Complete RLC RLSD SGSN sends Detach Accept message back to UE The SGSN sends Delete PDP Context Request messages for all active PDP contexts to the peer GGSNs SGSN GGSN UE sends Detach Request message to SGSN.

Routing Area Update (RAU) • This procedure is used for: – Normal routing area updating to update the registration of the actual routing area of an MS in the network – Combined routing area updating to update the registration of the actual routing and location area of an MS in the network – Periodic routing area updating. This procedure is used to notify periodically the availability of the mobile station to the network – IMSI attach for non-GPRS services when the MS is IMSI attached for GPRS services Anritsu Confidential Information .

RAU – Message Flow MS Network ROUTING AREA UPDATE REQUEST ROUTING AREA UPDATE ACCEPT ROUTING AREA UPDATE COMPLETE or ROUTING AREA UPDATE REQUEST ROUTING AREA UPDATE REJECT Anritsu Confidential Information .

Routing Area Update Complete DTI – Iu Release Command DTI – Iu Release Complete RLSD RLC Cancel Location procedure Routing Area Update is accepted by the network after successful „update GPRS Location‟ procedure Routing Area Update Complete message is send by the UE if there is a P-TMSI and/or a TMSI was included within the attach accept message (Implicit P-TMSI reallocation) Anritsu Confidential Information .Common ID DTI .Security Mode Command DTI . The update type IE indicates „RA updating‟ CR – Routing Area Update Request CC DT1 .RAU (Successful) – Message Flow RNC SGSN HLR OLD SGSN Routing Area Update Request send by UE.Security Mode Complete UpdateGPRSLocation and InsertSubscriberData procedures DTI – Routing Area Update Accept DTI .

RAU (Unsuccessful) .Security Mode Complete UpdateGPRSLocation procedure is failed because of System Failure UpdateGPRSLocation procedures failed with error „System Failure‟ DTI – Routing Area Update Reject DTI – Iu Release Command DTI – Iu Release Complete RLSD RLC Routing Area Update is Rejected by the network with the cause value „#17 Network Failure‟ Anritsu Confidential Information .Messages Flow RNC SGSN HLR Routing Area Update Request send by UE CR – Routing Area Update Request CC DT1 .Security Mode Command DTI .Common ID DTI .

the MS sends an ACTIVATE PDP CONTEXT REQUEST message to the network.PDP Context Activation • The purpose of this procedure is to establish a PDP context between the MS and the network for a specific QoS on a specific NSAPI. the network selects a radio priority level based on the QoS negotiated and may reply with an ACTIVATE PDP CONTEXT ACCEPT message Or. the network may reject the MS initiated PDP context activation by sending an ACTIVATE PDP CONTEXT REJECT message to the MS In case network request a PDP context activation. The message contains the selected NSAPI. PDP type. The PDP context activation may be initiated by the MS or the initiation may be requested by the network In order to request a PDP context activation. its sends a REQUEST PDP CONTEXT ACTIVATION message to the UE Anritsu Confidential Information • • • • . requested QoS Upon receipt of an ACTIVATE PDP CONTEXT REQUEST message.

PDP Context Activation – Message Flow MS initiated PDP context activation MS ACTIVATE PDP CONTEXT REQUEST ACTIVATE PDP CONTEXT ACCEPT or Network Network initiated PDP context activation ACTIVATE PDP CONTEXT REJECT MS REQUEST PDP CONTEXT ACTIVATION Network ACTIVATE PDP CONTEXT REQUEST ACTIVATE PDP CONTEXT ACCEPT or ACTIVATE PDP CONTEXT REJECT or REQUEST PDP CONTEXT ACTIVATION REJECT Anritsu Confidential Information .

Security Mode Complete DTI – Common ID DTI – Activate PDP Context Request GTP Create PDP Context Request DTI – RAB Assignment Request DTI – RAB Assignment Response DTI .PDP Context Activation (Successful) – Message Flow RNC CR – Service Request CC DTI – Security Mode Command DTI .Activate PDP Context Accept DTI – Iu-Release Request DTI – Iu-Release Command Cause = „#128 Request Accepted” SGSN GGSN Service Type = „Signalling‟ GTP Create PDP Context Response Iu Connection Release DTI – Iu-Release Complete RLC RLSD SCCP Connection Release Anritsu Confidential Information .

Activate PDP Context Reject DTI – Iu-Release Command DTI – Iu-Release Complete RLC RLSD Cause = „#29 User Authentication Failed‟ Cause = „#209 User Authentication Failed‟ SGSN GGSN Service Type = „Signalling‟ Iu Connection Release SCCP Connection Release Anritsu Confidential Information .PDP Context Activation (Unsuccessful) – Message Flow RNC CR – Service Request CC DTI – Security Mode Command DTI .Security Mode Complete DTI – Common ID DTI – Activate PDP Context Request GTP Create PDP Context Request GTP Create PDP Context Response DTI .

if the request can be accepted – Or. the MS shall send an ACTIVATE SECONDARY PDP CONTEXT REQUEST – The network will reply with ACTIVATE SECONDARY PDP CONTEXT ACCEPT message. the network may reject the MS initiated PDP context activation by sending an ACTIVATE SECONDARY PDP CONTEXT REJECT message to the MS • Secondary PDP context activation also can be initiated by the network by sending REQUEST SECONDARY PDP CONTEXT ACTIVATION message to the MS Anritsu Confidential Information .Secondary PDP Context Activation • • • This procedure is used to establish an additional PDP context between the MS and the network for a specific QoS profile It is invoked when one or more PDP contexts have already been established for the particular PDP address and APN In order to request a secondary PDP context activation.

Secondary PDP Context Activation .Message Flow MS Network MS initiated Secondary PDP context activation ACTIVATE SECONDARY PDP CONTEXT REQUEST Network initiated Secondary PDP context activation ACTIVATE SECONDARY PDP CONTEXT ACCEPT or ACTIVATE SECONDARY PDP CONTEXT REJECT MS Network REQUEST SECONDARY PDP CONTEXT ACTIVATION ACTIVATE SECONDARY PDP CONTEXT REQUEST ACTIVATE SECONDARY PDP CONTEXT ACCEPT or ACTIVATE SECONDARY PDP CONTEXT REJECT or REQUEST SECONDARY PDP CONTEXT ACTIVATION Anritsu Confidential Information .

Secondary PDP Context Activation – (Successful) Message Flow RNC CR – Service Request SGSN GGSN CC DTI – Security Mode Command DTI .Activate Second PDP Context Accpt DTI – Iu-Release Request DTI – Iu-Release Command DTI – Iu-Release Complete RLC RLSD GTP Create PDP context Response Cause = „#128 Request Accepted‟ Secondary PDP context activation is accepted by the network Anritsu Confidential Information .Security Mode Complete DTI – Common ID DTI – Activate Second PDP Context Req GTP Create PDP context Request Service Type = „Signalling‟ Secondary PDP context activation is initiated by the UE DTI – RAB Assignment Request DTI – RAB Assignment Response DTI .

Activate Second PDP Context Reject DTI – Iu-Release Request DTI – Iu-Release Command DTI – Iu-Release Complete RLC RLSD Secondary PDP context activation is Rejected by the network Anritsu Confidential Information .Secondary PDP Context Activation – (Unsuccessful) Message Flow RNC CR – Service Request SGSN GGSN CC DTI – Security Mode Command DTI .Security Mode Complete DTI – Common ID DTI – RAB Assignment Request DTI – RAB Assignment Response DTI – Activate Second PDP Context Req DTI – RAB Assignment Request RAB assignment is failed with cause value „Requested traffic class not available‟ Service Type = „Data‟ Secondary PDP context activation is initiated by the UE DTI – RAB Assignment Response DTI .

the network sends the MODIFY PDP CONTEXT REQUEST message to the MS Anritsu Confidential Information . or the TFT. the Radio priority level. the network may reply with the MODIFY PDP CONTEXT ACCEPT message in order to accept the context modification – Or. the MS sends the MODIFY PDP CONTEXT REQUEST message to the network. the network may reject the MS initiated PDP context modification request by sending a MODIFY PDP CONTEXT REJECT message to the MS • • In case the network initiates the PDP context modification procedure. The message may contain the requested new QoS and/or the TFT – Upon receipt of the MODIFY PDP CONTEXT REQUEST message. in order to change the QoS negotiated. negotiated during the PDP context activation procedure In order to initiate the procedure.PDP Context Modification • The PDP context modification procedure is invoked by the network or by the MS.

PDP Context Modification – Message Flow MS MODIFY PDP CONTEXT REQUEST Network MS initiated Modify PDP Context Network initiated Modify PDP Context MODIFY PDP CONTEXT ACCEPT or MODIFY PDP CONTEXT REJECT MS MODIFY PDP CONTEXT REQUEST Network MODIFY PDP CONTEXT ACCEPT Anritsu Confidential Information .

Security Mode Complete In order to Modify the PDP context.Modify PDP Context Accept DTI – Iu-Release Command DTI – Iu-Release Complete RLC RLSD Update PDP Context procedure is executed in the Gn interface Once the PDP context is modified „Modify PDP Context Accept‟ message is send to the UE Anritsu Confidential Information .PDP Context Modification (Successful) – Message Flow RNC CR – Service Request CC DTI – Security Mode Command DTI . „Modify PDP Context Request‟ by the UE to the SGSN This message may contain the new QOS parameters SGSN GGSN Service Type = „Signalling‟ DTI – Common ID DTI – Modify PDP Context Request GTP Update PDP Context Request GTP Update PDP Context Response DTI .

„Modify PDP Context Request‟ by the UE to the SGSN This message may contain the new QOS parameters SGSN GGSN Service Type = „Signalling‟ DTI – Common ID DTI – Modify PDP Context Request GTP Update PDP Context Request GTP Update PDP Context Response DTI .PDP Context Modification (Unsuccessful) – Message Flow RNC CR – Service Request CC DTI – Security Mode Command DTI .Modify PDP Context Reject DTI – Iu-Release Command DTI – Iu-Release Complete RLC Update PDP Context procedure is executed in the Gn interface.Security Mode Complete In order to Modify the PDP context. Update pdp context response contains the cause value „Service not supported' PDP context modification is rejected by the SGSN by sending „Modify PDP Context Reject‟ message to the UE This message has the cause value „Service option not supported‟ RLSD Anritsu Confidential Information .

upon receipt of this message. – The message contains the cause which is typically #26:insufficient resources. #36: regular deactivation or #37: QoS not accepted – The network shall reply with the DEACTIVATE PDP CONTEXT ACCEPT message • In case of network initiated PDP context deactivation. #36: regular deactivation. reply with a DEACTIVATE PDP CONTEXT ACCEPT message Anritsu Confidential Information .PDP Context Deactivation • The purpose of this procedure is to deactivate an existing PDP context between the MS and the network. the MS sends a DEACTIVATE PDP CONTEXT REQUEST message to the network. – The PDP context deactivation may be initiated by the MS or by the network • In order to deactivate a PDP context. or # 39: reactivation requested – The MS shall. the network sends a DEACTIVATE PDP CONTEXT REQUEST message to the MS. – The message contains the cause which is typically #8: operator Determined Barring. #38: network failure.

PDP Context Deactivation – Message Flow MS initiated PDP Context Deactivation MS DEACTIVATE PDP CONTEXT REQUEST Network initiated PDP Context Deactivation DEACTIVATE PDP CONTEXT ACCEPT Network MS DEACTIVATE PDP CONTEXT REQUEST Network DEACTIVATE PDP CONTEXT ACCEPT Anritsu Confidential Information .

Security Mode Complete DTI – Common ID DTI – Deactivate PDP Context Request GTP Delete PDP Context Request GTP Delete PDP Context Response DTI .Deactivate PDP Context Accept DTI – Iu-Release Command DTI – Iu-Release Complete RLC RLSD Cause = „#128 Request Accepted” SM Cause = „#24h Regular Deactivation‟ SGSN GGSN Service Type = „Signalling‟ Anritsu Confidential Information .PDP Context Deactivation (Successful) – Message Flow RNC CR – Service Request CC DTI – Security Mode Command DTI .

g. SM or SMS) procedure from the MS in IDLE mode – The network to transfer down link signalling – Uplink and downlink of user data • The MS initiates the Service request procedure by sending a SERVICE REQUEST message.Service Request • This procedure is used for – The initiation of CM layer service (e. the network returns a SERVICE REJECT message to the mobile station with appropriate cause Anritsu Confidential Information . "signalling“ or "paging response“ • If the Service request cannot be accepted. The service type IE shall indicate either "data".

Deactivate PDP Context Accept DTI – Iu-Release Command DTI – Iu-Release Complete RLC RLSD Cause = „#128 Request Accepted” Anritsu Confidential Information .Security Mode Complete DTI – Common ID DTI – Deactivate PDP Context Request GTP Delete PDP Context Request SM Cause = „#24h Regular Deactivation‟ SGSN GGSN Scenario 1: Service Request for Signalling purpose There is no RAB Assignment in this scenario Service Type = „Signalling‟ GTP Delete PDP Context Response DTI .Service Request (Successful) – Message Flow Service Type = Signalling RNC CR – Service Request CC DTI – Security Mode Command DTI .

Service Request (Successful) – Message Flow Service Type = Data RNC CR – Service Request CC DTI – Security Mode Command DTI .Security Mode Complete DTI – Common ID SGSN GGSN Scenario 2: Service Request for sending Data by the UE Service Type = „Data‟ DTI – RAB Assignment Request DTI .RAB Assignment Response DTI – Iu-Release Request DTI – Iu-Release Command DTI – Iu-Release Complete RLC RAB Assignment procedure is involved in this scenario IU Connection is released based when RRC connection is released in UTRAN RLSD Anritsu Confidential Information .

Service Request (Unsuccessful) – Message Flow RNC SGSN GGSN Service type = „Data‟ CR – Service Request CC DTI – Service Reject DTI – Iu-Release Command DTI – Iu-Release Complete RLC RLSD Service Request is rejected by the network because there is no Active PDP Context for this UE. Please note the service request type was „Data‟ Anritsu Confidential Information .

These radio links may be towards different Node-B‟s which are controlled by different RNC‟s • RNC Roles – Serving RNC • RNC which serves an UE and provides connection to core network – Drift RNC • RNC which provides UE radio resources.SRNS Relocation • Macro Diversity – Macro diversity. refers to the condition that several radio links are active at the same time. but doesn't manage UE‟s connection with core network • SRNS relocation – Procedure by which Drift RNC is made as the Serving RNC. when the UE is moved towards Drift RNC Anritsu Confidential Information .

Relocation Commit 9. Relocation Detect 10. Forward Relocation Response 6. Relocation Request Acknowledge 5. Forward Relocation Complete Acknowledge 14. Forward Relocation Complete 12. Forwarding of data 8.Forward Relocation With Iur (Successful) – Message MS Source RNC Decision to perform SRNS relocation Target RNC Old SGSN New SGSN GGSN 2. Update PDP Context Response 15. Update PDP Context Request 13. Relocation Required 3. Routing Area Update Anritsu Confidential Information . Forward Relocation Request 4. Relocation Request Establishment of Radio Access Bearers 4. RAN Mobility Information 10. Relocation Complete 12. Iu Release Complete 13. Iu Release Command 14. Relocation Command 7. RAN Mobility Information Confirm 11.

Forward Relocation Response 6. Forward SRNS Context 9. Forwarding of data 9. Forward Relocation Complete 14. Relocation Complete 12. Routing Area Update Anritsu Confidential Information . Iu Release Command 14. RRC message 7. RRC message 11. Forward Relocation Complete Acknowledge 13. Relocation Detect 8. Update PDP Context Request 13. Forward SRNS Context 9. Forward Relocation Request 4. Forward SRNS Context Acknowledge Note: Forwarding of data is through Iu interface RRC Message. Relocation Request Establishment of Radio Access Bearers 4.Forward Relocation Without Iur (Successful) – Message Flow MS Source RNC Target RNC Old SGSN New SGSN GGSN Decision to perform MS Involved SRNS Relocation 2. Relocation Command 8. Update PDP Context Response 15. Iu Release Complete 12. Relocation Request Acknowledge 5. Forward SRNS Context MS detected by target RNC 10. Physical Channel Reconfiguration is send by RNC Mobile responds with Physical Channel Reconfiguration complete when UE has reconfigured itself 9. Relocation Required 3.

Anritsu Confidential Information .Release-Command Iu.Release-Complete The call between the UE and the old RNS and between the old RNS and the MSC shall continue as if there had been no handover attempt MSC sends IU-Release-Command message with the cause "Relocation Cancelled " to the Target RNS.SRNS Relocation Failure UE RNS-A Iu-Relocation-Required Iu-Relocation-Request Iu-Relocation-Preparation Failure Iu-Relocation-Failure UE SGSN RNS-B Scenario: Handover Failure due to resource allocation failure in target RNS Target RNS sends a IU-RelocationFailure message to MSC with cause value “No Radio Resources Available in Target cell ” SGSN sends a IU-RelocationPreparation-Failure message to RNSA with cause value “No Radio Resources Available in Target cell” Iu.

Typical Problems • Attach Reject – Code 7: GPRS services not allowed – Code 14: GPRS services not allowed in this PLMN – Code 17: Network Failure • PDP Context Activation Failure – – – – Code 26: Insufficient resources Code 29: User Authentication failed Code 33: Requested service option not subscribed Code 38: Network failure Anritsu Confidential Information .

Typical Problems • RAB Assignment Failure – – – – – – – – – Code 15: Release due to UTRAN Generated Reason Code 18: Requested Traffic Class not Available Code 23: Invalid RAB Parameters Combination Code 46: Radio Connection With UE Lost Code 114: No Resource Available 9 MS identity cannot be derived by the network 10 Implicitly detached 17 Network failure 111 Protocol error-unspecified • Routing Area Update Failure Anritsu Confidential Information .

Hands On(1/2) • Tracing Attach Reject with ‘#11: Network failure’ cause in PAC – Select the appropriate IuPS linksets in PAC – Apply filter for in GMM layer with following criteria • Message Type = Attach Reject • GMM Cause = ‘#11: Network failure’ Anritsu Confidential Information .

Hands On(1/2) Filter Setup Results in Overvie w Results in Detailed View Anritsu Confidential Information .

Hands On(2/2) • Tracing Activate PDP context failure in CallTrace other than ‘#29: user authentication failed’ and ‘#33: Requested service option not subscribed’ – In Calltrace select IuPs-Dialogue – Select the appropriate Linksets and the Time interval – In Filter Condition Select ‟PdpActivationFailureCause‟ • From the selected drop down select ‘#29: user authentication failed’ and ‘#33: Requested service option not subscribed’ • Change the criteria from ‟equals‟ to ‟not equals‟ – Now hit the ‟Start Trace‟ button to see the results Anritsu Confidential Information .

Hands On(2/2) Results Right click on the message in Sequence Diagram to obtain this view Setup Anritsu Confidential Information .

Q&A Anritsu Confidential Information .

zip GPRS Service Description: 3GPP TS 23.org/ftp/Specs/archive/29_series/29.zip SM.3gpp.zip GTP PDP RANAP CC MAP SCCP CC CR DT1 RLC RLSD UDT BEGIN CONTINUE END SLR DLR IMSI IMEI MSISDN Anritsu Confidential Information .org/ftp/Specs/archive/24_series/24.008/24008-7f0.413: http://www.009 http://www.zip MAP 3GPP TS 29.org/ftp/Specs/archive/25_series/25.Acronyms and References DRNC HLR MSC RNC RNS SMSC SRNC SRNS UE UTRAN VLR Entities Drift Radio Network Controller Home Location Register Mobile Switching Center Radio Network Controller Radio Network Subsystem Short Message Service Center Serving Radio Network Controller Serving Radio Network Subsystem User Equipment UMTS Terrestrial Radio Access Network Visitor Location Register Protocols GPRS tunnelling protocol Packet Data Protocol Radio Access Network Application Part Call Control Mobile Applications Part Signalling Connection Control Part Messages SCCP .org/ftp/Specs/archive/23_series/23.3gpp.3gpp.060/23060-7b0.BEGIN Message Identifiers TCAP – CONTINUE Message TCAP – END Message Identifiers Source Local Reference Destination Local Reference International Mobile Subscriber Identity International Mobile Equipment Identity Mobile Subscriber ISDN Number References RANAP 3GPP TS: 25.002/29002-7f0.3gpp.Connection Confirm SCCP – Connection Request SCCP – Data Form 1 SCCP – Release Complete SCCP – Released SCCP .413/25413-880.Unit Data TCAP .008 http://www.060 http://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-711.002 : http://www. GMM: 3GPP TS 24.zip HANDOVER: 3GPP TS 23.

Thank you! Anritsu Confidential Information .

Sign up to vote on this title
UsefulNot useful