Professional Documents
Culture Documents
Additional Radio Events For The PS Domain in UMTS
Additional Radio Events For The PS Domain in UMTS
July 2004
Contents
1
INTRODUCTION................................................................................................... 2
Page 1
July 2004
1 Introduction
Three new event diagrams will handle the PS NAS signalling and associated procedures for
UMTS. The events apply to radio interface logs only (e.g. drive test logs).
PMM
GMM
SM
There are three new corresponding event diagrams (.aev), format groups (.xml), and
attributes (.xml) files.
There are also changes to some of the already existing files, mainly due to the fact that
some old attributes in the UMTS.xxx are now moved to the above new files, with the
intention of including the PS properties (attributes, format groups) in the specific PS files
rather than keep them in the more general UMTS files.
Description of events, attributes and values are specified in the relevant sections below.
Note on diagrams:
red dotted lines between states represent transition that have been added to cope
with corrupted log files that occasionally skip messages.
Note on timers:
Page 2
July 2004
2.1
The PPM event diagram traces the PS signalling connections, from the setup to the release
phases.
A PS signalling connection is a logical signalling resource between terminal and SGSN. It
relies on the presence of both radio (RAN UE) and Iu-PS interface (RAN SGSN)
logical/physical resources:
UE
RNC
SGS
PS Signalling Connection
RRC Connection
Iu-PS Connection
Page 3
July 2004
Every NAS procedure (e.g. PS Attach or PDP context Activation) between UE and SGSN
can take place only if the PS Signalling connection is already established between the two
nodes.
2.2
As shown in the diagram above, in order to establish a PS Signalling connection, a RRC and
Iu-PS connections need to be present for the UE.
While on the radio side the RRC Connection is shared between CS and PS Signalling
connections, on the Iu interface side the Iu resources are logically separated.
The PS signalling connection establishment is always initiated by the UE via:
RRC: Initial Direct Transfer with PS domain indication
UE
RNC
SGS
RRC Connection
Page 4
2.3
July 2004
The PS Signalling Connection is normally released via a RRC Connection release procedure
or a PS Signalling connection release procedure. The latter occurs usually when a CS
connection is also present and can be triggered by both UE and RAN/SGSN
1) RRC connection Release procedure
RRC: RRC Connection Release
UE
RNC
SGS
PS Signalling Connection
RNC
SGS
PS Signalling Connection
Page 5
UE
July 2004
RNC
SGS
PS Signalling Connection
2.4
Attribute
Values
Triggers
After Initial direct Transfer (PS):
Successful
Uu_PS_SigConn_Setup
Failed
Successful
Uu_PS_SigConn_Release
RB Release Complete
Failed
Abnormal
release
RB Release Failure
After Initial direct Transfer (PS) or Sig.
Conn. is set up or RB Release:
RRC:RRC Conn. Req.
Time elapsed between the successful
setup and the successful/abnormal
release of the PS Signalling Connection
Page 6
July 2004
3.1
GMM procedures
Most of the GMM procedures are common to UMTS and GPRS. In this initial version of
GMM event diagram only the UMTS events are detected. The following GMM procedures
are analyzed:
PS Attach
PS Detach
PS Attach
A PS Attach is always initiated by the UE via:
Attach Request
The message is included either in RRC:Initial Direct transfer or in RRC:Uplink Direct
Transfer messages.
Page 7
July 2004
RNC
SGS
RRC Connection
UE is GMM-deregistered
Attach complete1
Iu procedures
UE is GMM-registered
Successful PS Attach
Note that in case of missing reply to Attach Request, the UE should re-send the message,
up to a total of 4 re-transmissions. The same mechanism is used by the SGSN to supervise
the reply (when expected) to Attach Accept.
The PS Attach procedure can fail for several reasons, the most common of which are
detected by the GMM Event diagram and listed below (see the table of attributes for more
details):
PS Detach
A UE can be PS detached explicitly (the procedure can be initiated by either the UE or the
SGN) or implicitly (normally by the SGSN only)
The GMM Event diagram can only detect an explicit PS Detach procedure; regardless of the
initiating node, the explicit PS Detach is triggered by:
Detach request
The message is included either in RRC:Initial Direct Transfer or in RRC:Uplink Direct
Transfer messages if UE initiated, in a RRC:Downlink Direct Transfer if SGSN initiated.
Page 8
UE
July 2004
RNC
SGS
RRC Connection
UE is GMM-registered
Detach Accept1
Iu procedures
UE is GMM-deregistered
Successful PS Detach
The failure scenarios covered by the Event Diagram occur only in case of UE initiated
Detach without power-off:
The network release the underlying RRC connection instead of accepting the Detach
request
RNC
SGSN
RRC Connection
RAU request (n)
RAU Accept (m)
RAU complete1
Iu procedures
Page 9
July 2004
Except for Network Failure reasons, when a RAU fails the UE is still considered PS
Attached. The diagram is a simplified interpretation of the 3GPP specs (24.008), where more
specific failure scenarios are specified. However, all of the most common scenarios are
covered.
3.2
Attribute
Values
Succ_1_Attempt
..
Succ_5_Attempt
Triggers
Attach Accept if this message includes
P-TMSI
Attach Complete if preceding Attach
Accept do not include P-TMSI
The attempts refer to the number of
Attach Request messages sent
After Attach request:
Rejected
Attach Reject
Uu_PS_Attach
Aborted
Succ_1_Attempt
..
Succ_5_Attempt
Uu_PS_Detach
Aborted
Page 10
Attribute
Values
Succ_1_Attempt
..
Succ_5_Attempt
July 2004
Triggers
RAU Accept if this message includes PTMSI
RAU Complete if preceding RAU Accept
do not include P-TMSI
The attempts refer to the number of RAU
Request messages sent
After RAU request:
Uu_PS_RAU
Rejected
RAU Reject
After RAU request:
Aborted
Uu_PS_Attach_Duration
Value in msec.
Page 11
July 2004
4 Session Management (SM) UMTS only with inter-system handover to/from GPRS
Page 12
July 2004
Page 13
4.1
July 2004
SM procedures
As in GMM most of the SM procedures are common to UMTS and GPRS. This initial version
of SM event diagram is focused on UMTS events; in most of the inter-system (3G 2.5G)
handover scenarios also some GPRS events are considered. However the Event diagram
set only UMTS attributes.
The following procedures are analyzed:
Limitations:
Although the Event Diagram can trace the number of PDP Contexts simultaneously
active for the UE, there is no differentiation between primary and secondary contexts
(PDP differentiation based on TI will be added in the next releases.
UE
RNC
SGSN
RRC Connection
Request PDP context Activation1
Activate PDP Context Request
Iu procedures
Page 14
UE
July 2004
RNC
SGSN
RRC Connection
Iu procedures
Both SGSN and UE initiated PDP Context Activation procedures provide a mechanism for
re-transmitting a message when an expected reply is not received.
These are the failure scenarios covered:
UE
RNC
SGSN
RRC Connection
Deactivate PDP Context Request
Iu procedures
Deactivate PDP Context Accept
Page 15
July 2004
The only failure scenario detected for the PDP context Deactivation procedure is a missing
reply to the Deactivation Request:
4.2
The first event usually detected by the SM Event Diagram is a PDP context Activation
with UE in UMTS coverage. However, the diagram also recognizes:
1. A PDP context deactivation (from UMTS).
This may occur if the logs start with the UE already having an active PDP context.
2. An inter-RAT Cell Change Order from UTRAN, which causes a UMTS GPRS
transition for a UEs in Cell_DCH or Cell_FACH state.
3. A GPRS UMTS transition. In this case, it is always assumed that only one PDP
Context is active at the time the transition occurs. Moreover the GPRS SM/GMM
activity eventually occurring before the transition is not taken into account.
Just like during UMTS coverage the number of PDP Contexts active in GPRS is tracked,
although such information is not displayed until the UE returns to UMTS coverage.
Throughout the GPRS session only a in GPRS flag will appear. No attributes are
displayed for SM events occurring in GPRS.
However, once the UE is in GPRS mode, the following GPRS NAS procedures are
detected:
1. PDP context Activation/Deactivation
2. PS Detach
3. PS Attach
The detection of the above procedures in GPRS is fundamental in order to keep track of
the correct number of PDP Contexts active when the UE returns eventually to 3G.
The SM diagram takes into account the following inter-system handover and cell reselection procedures:
-
Page 16
4.3
July 2004
Attributes for SM
Attribute
Uu_PS_PDPAct_From_UE
Values
Triggers
Succ_1_A
ttempt
..
Succ_5_A
ttempt
Rejected_
by_NW
Aborted
Succ_1_A
ttempt
..
Succ_5_A
ttempt
Rejected_
by_NW
Uu_PS_PDPAct_From_NW
Rejected_
by_UE
Aborted
Page 17
Attribute
Values
July 2004
Triggers
After Deactivate PDP Context
Request from UE:
Succ_1_A
ttempt
..
Uu_PS_PDPDeact_From_UE
Succ_5_A
ttempt
Aborted
Succ_1
_Attempt
..
Uu_PS_PDPDeact_From_NW
Succ_5
_Attempt
Aborted
Uu_PDP_State
PDP Act
Request
PDP
Deact
Request
in GPRS
Page 18
Attribute
Values
July 2004
Triggers
Beginning of the file
Last PDP deactivated
No PDP
1 PDP
..
3 PDPs
PDP_Session_ID
0..n
Uu_TimeBetweenPDP_ReqAndAct
Value in
msec.
Uu_TimeBetweenPDP_ReqAndDeactReq
Value in
msec.
Uu_TimeBetweenPDP_ActAndDeact
Value in
msec.
Uu_TimeBetweenPDP_DeactReqAndDeact
Value in
msec.
Page 19