Documente Academic
Documente Profesional
Documente Cultură
Summary
High level Description Network Diagrams Protocol Stack Main Procedures Messages Flow Diagrams Typical Problems Hands On Acronyms and References
Network Diagrams
PABX
A-bis INAP ISDN
IN
MAP ISUP
BSC
Gb
MSC
MAP
GMSC
MAP ISUP
Um Iu-CS Gs
SMSC
EIR
Gf Gd Gr
RNC
Iur Iub Node B Iub Uu Node B
HLR
Gc
AUC
RNC
Iu-PS
Gi
GRX
Protocol Stack
Radio Network Layer
Control Plane RANAP User Plane Iu UP Protocol Layer
GTP-U UDP
IP
ATM
Data Link
ATM
Data Link
Physical Layer
Physical Layer
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)
Attach
The GPRS attach procedure is used for two purposes Normal GPRS attach, performed by the MS to IMSI attach for GPRS services only. Combined GPRS attach procedure, used to attach the IMSI for GPRS and non-GPRS services. The MS initiates the GPRS attach procedure by sending an ATTACH REQUEST message to the network. The attach type information element shall indicate "GPRS attach". If the GPRS attach request is accepted by the network, an ATTACH ACCEPT message is sent to the MS. If the attach request cannot be accepted by the network, an ATTACH REJECT message is transferred to the MS. This message will include a cause value indicating the reason for reject Attach procedure can used to reallocate P-TMSI/TMSI. In such cases MS will send ATTACH COMPLETE message after receiving ATTACH ACCEPT message
ATTACH ACCEPT
ATTACH COMPLETE
or
ATTACH REQUEST
ATTACH REJECT
SGSN
HLR
OLD SGSN
Attach Request send by MS Attach is accepted by the network after successful update GPRS Location procedure
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)
SGSN
HLR
Scenario: GPRS Attach Attach type information element in Attach Request message indicates "GPRS attach"
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. The detach type information element may indicate "GPRS detach with switching off", "GPRS detach without switching off", "IMSI detach", "GPRS/IMSI detach with switching off" or "GPRS/IMSI detach without switching off". In case the network initiates the GPRS detach procedure it sends a DETACH REQUEST message to the MS. The DETACH REQUEST message shall include a detach type IE. The detach type IE indicates "re-attach not required" or "re-attach required"
Network
SGSN
GGSN
UE sends Detach Request message to SGSN. Detach type IE indicates GPRS detach without switching off
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)
CR Routing Area Update Request CC DT1 - Common ID DTI - Security Mode Command DTI - Security Mode Complete
UpdateGPRSLocation procedure is failed because of System Failure UpdateGPRSLocation procedures failed with error System Failure
Routing Area Update is Rejected by the network with the cause value #17 Network Failure
Network
Network initiated PDP context activation
Network
SGSN
GGSN
Iu Connection Release
DTI Iu-Release Complete RLC RLSD
SGSN
GGSN
Iu Connection Release
Secondary PDP context activation also can be initiated by the network by sending REQUEST SECONDARY PDP CONTEXT ACTIVATION message to the MS
MS
Network
ACTIVATE SECONDARY PDP CONTEXT ACCEPT or ACTIVATE SECONDARY PDP CONTEXT REJECT
SGSN
GGSN
CC
DTI Security Mode Command DTI - Security Mode Complete DTI Common ID DTI Activate Second PDP Context Req GTP Create PDP context 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
In case the network initiates the PDP context modification procedure, the network sends the MODIFY PDP CONTEXT REQUEST message to the MS
Network
SGSN
GGSN
DTI Common ID
DTI Modify PDP Context Request
Once the PDP context is modified Modify PDP Context Accept message is send to the UE
SGSN
GGSN
DTI Common ID
DTI Modify PDP Context Request GTP Update PDP Context Request GTP Update PDP Context Response DTI - Modify PDP Context Reject DTI Iu-Release Command DTI Iu-Release Complete RLC
Update PDP Context procedure is executed in the Gn interface. 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
In order to deactivate a PDP context, the MS sends a DEACTIVATE PDP CONTEXT REQUEST message to the network.
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, the network sends a DEACTIVATE PDP CONTEXT REQUEST message to the MS.
The message contains the cause which is typically #8: operator Determined Barring, #36: regular deactivation, #38: network failure, or # 39: reactivation requested The MS shall, upon receipt of this message, reply with a DEACTIVATE PDP CONTEXT ACCEPT message
Anritsu Confidential Information
Network
SGSN
GGSN
Service Request
This procedure is used for The initiation of CM layer service (e.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. The service type IE shall indicate either "data", "signalling or "paging response
If the Service request cannot be accepted, the network returns a SERVICE REJECT message to the mobile station with appropriate cause
SGSN
GGSN
Scenario 1: Service Request for Signalling purpose There is no RAB Assignment in this scenario
SGSN
GGSN
RAB Assignment procedure is involved in this scenario IU Connection is released based when RRC connection is released in UTRAN
RLSD
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
SRNS Relocation
Macro Diversity
Macro diversity, refers to the condition that several radio links are active at the same time. These radio links may be towards different Node-Bs which are controlled by different RNCs
RNC Roles
Serving RNC
RNC which serves an UE and provides connection to core network
Drift RNC
RNC which provides UE radio resources, but doesn't manage UEs 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
2. Relocation Required 3. Forward Relocation Request 4. Relocation Request Establishment of Radio Access Bearers 4. Relocation Request Acknowledge 5. Forward Relocation Response 6. Relocation Command 7. Forwarding of data 8. Relocation Commit 9. Relocation Detect
Note: Forwarding of data is through Iu interface RRC Message, Physical Channel Reconfiguration is send by RNC Mobile responds with Physical Channel Reconfiguration complete when UE has reconfigured itself
12. Forward Relocation Complete Acknowledge 13. Update PDP Context Request 13. Update PDP Context Response
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
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,
Typical Problems
Attach Reject
Code 7: GPRS services not allowed Code 14: GPRS services not allowed in this PLMN Code 17: Network Failure
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
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
Hands On(1/2)
Filter Setup
Results in Overvie w
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
Hands On(2/2)
Results
Right click on the message in Sequence Diagram to obtain this view
Setup
Q&A
References
RANAP 3GPP TS: 25.413: http://www.3gpp.org/ftp/Specs/archive/25_series/25.413/25413-880.zip MAP 3GPP TS 29.002 : http://www.3gpp.org/ftp/Specs/archive/29_series/29.002/29002-7f0.zip SM, GMM: 3GPP TS 24.008 http://www.3gpp.org/ftp/Specs/archive/24_series/24.008/24008-7f0.zip HANDOVER: 3GPP TS 23.009 http://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-711.zip GPRS Service Description: 3GPP TS 23.060 http://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-7b0.zip
Thank you!