LTE Session Analysis
| Contents | 2
Contents
Summary of changes................................................................................................ 4
About.......................................................................................................................... 5
References.................................................................................................................. 6
Abreviations...............................................................................................................7
Analysis concept........................................................................................................8
Session details............................................................................................................9
Establishment Cause........................................................................................................................................... 11
C-RNTI................................................................................................................................................................12
eNB S1AP UE ID.............................................................................................................................................. 13
MME UE S1AP ID............................................................................................................................................ 14
TAC..................................................................................................................................................................... 14
EPS Session/Bearer Identifiers........................................................................................................................... 15
Session analysis....................................................................................................... 17
Basic LTE call.................................................................................................................................................... 28
Call reestablishment............................................................................................................................................45
Intra HO.............................................................................................................................................................. 54
X2 Inter eNB HO............................................................................................................................................... 60
S1 Handover....................................................................................................................................................... 65
I-RAT (Inter System Handover)........................................................................................................................ 70
CSFB - Circuit Switch Fallback........................................................................................................................ 73
Additional ERAB................................................................................................................................................77
Session location map...............................................................................................80
Measurement graph................................................................................................81
Message flow............................................................................................................82
Appendix A - In Cause.......................................................................................... 83
Appendix B - Out Cause........................................................................................84
| Contents | 3
Appendix C - S1AP Release Failure Cause......................................................... 86
Appendix D - S1 Establishment Failure Cause................................................... 90
Appendix E - S1 Release Cause............................................................................ 94
Appendix F - Fault phase...................................................................................... 98
Appendix G - RRC Establishment Cause............................................................ 99
Backup....................................................................................................................100
| Summary of changes | 4
Summary of changes
Table 1: Summary of changes
Author
Date
Version
Details
Lukasz Nowak
10.2.2014
0.1
Draft
Lukasz Nowak
26.2.2014
0.2
inter RAT measurement
removed from specification
(will be specified for next
release)
Lukasz Nowak
10.3.2014
0.3
Session flow information
updated, new case added
Lukasz Nowak
7.9.2015
0.7
All scenario reviewed,
more details added,
scenarion described msg
after msg
| About | 5
About
"LTE Session Analysis' specification includes basic information required by RETINA and NetAct TraceViewer
project to provide support for LTE session analysis.
Specification base on:
•
LTE 433/644 LTE Cell Trace
| References | 6
References
Table 2: References
Reference
Title
[1]
3GPP 36.331 Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC); Protocol specification v11.6.0
[2]
3GPP 36.413 Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1
Application Protocol (S1AP) v11.6.0
[3]
3GPP 36.423 Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2
Application Protocol (X2AP) v11.7.0
[4]
“LTE Signaling: Troubleshooting and Optimization” R. Kreher; K. Ganger
[5]
“Emil LTE Profile Manual” v2.0.9.9 A. Reijonen
[6]
LTE Emil-Traffica Interface Specification
[7]
“LTE Protocol Tracing Interface” G. Schoenwolf v 3.3
[8]
“Training – Layer 3 Data Collector” Sami Lehesaari
[9]
CASN Decoders
[10]
3GPP 36.355 v11.5.0 Evolved Universal Terrestrial Radio Access (E-UTRA); LTE
Positioning Protocol (LPP)
[11]
US_7741.11.13. As a NA I want to see graphical LTE Handover Analysis report
[12]
http://ltesignaling.blogspot.com/2011/10/rnti.html
[13]
http://www.netmanias.com/en/?m=view&id=techdocs&no=5905
[14]
"Handover between LTE and 3G Radio Access Technologies: Test measurement challenges
and field environment test planning" http://lib.tkk.fi/Dipl/2011/urn100472.pdf
[15]
3GPP TS 23.272 V11.8.0 Circuit Switched Fallback in Evolved Packet System
[16]
"Voice and SMS in LTE; White Paper" Rohde & Schwarz
[17]
http://tweet4tutorial.com/authentication-procedure-lte/
[18]
http://www.eventhelix.com/lte/security/lte-security-session-setup.pdf
[19]
24.301 NAS
[20]
http://www.eventhelix.com/lte/security/lte-security-presentation.pdf
[21]
http://howltestuffworks.blogspot.com/2011/10/rrc-connection-reestablishment-request.html
[22]
http://www.netmanias.com/en/post/techdocs/5907/identification-identifier-lte/lteidentification-iii-eps-session-bearer-identifiers
| Abreviations | 7
Abreviations
Table 3: Abbreviations
Abbreviation
Description
CRNTI
Common Radio Network Temporary ID
DRB
Data Radio Bearer
LCR
Local Cell Resource ID
MME
Mobility Management Entity
RAB
Radio Access Bearer
RRC
Radio Resource Control
RSRP
Radio Signal Reference Power
RSRQ
Radio Signal Reference Quality
SRB
Signalling Radio Bearer
TAC
Tracking Area Code
TAU
Traccking Area Update
TRSR
Trace Recording Session Reference number
| Analysis concept | 8
Analysis concept
RETINA for LTE will follow trace data analysis concept created in RETINA for UMTS. It means that following
section will be created:
•
•
•
•
•
session details - where the most important information about session itself will be presented
session flow information - where details regarding session status and phases are presented
UE session location map - where location for each measurement with identification from which cell measurements
comes will be presented
message flow information with message details
measurement graph - where RSRP and RSRQ will be presented (in future releases also inter RAT measurements)
Sections should synchronize to each other i.e. whenever RRCMeasurementReport is selected on 'Message Flow'
proper information must be selected on 'Measurement Graph'
Figure 1: General analysis concept in RATINA project
| Session details | 9
Session details
LTE "Session details" section consists of the most import information about session itself [1,2,3,5,7,17], i.e.:
•
Session ID
•
• TRSR assigned base on Start/StopTrace message
IMSI
•
•
sporadically available if NAS:ATTACH PROCEDURE is executed nas UE has been configured to
"AttachWith IMSI" [19]
• base on “LTE162 Cell Trace with IMSI” or when 'IMSI provider" will be connected
• NOTE: currently it’s being investigated possiibility to parse information from Traffica DB.
IMEI
•
• for future use, base on “LTE162 Cell Trace with IMSI”
• NOTE: currently it’s being investigated to parse information from Traffica DB.
Session Start Time
•
• time base on StartTrace where TRSR!=FFFF
Session Stop Time
•
• time base on StopTrace where TRSR!=FFFF
Session Duration
•
• StopTrace – StartTrace
CRNTI
•
•
Number available in trace messages according to [7]. From L3 flow is available on L2 and in
RRCConnectioReestablishmentRequest
• Prints CRTNI identifier the UE tries to use in RRCConnectionReestablismentRequest message. If eNB has
not yet release resource for the old CRNTI, the Re-establishment should be successful. Old CRNTI can be
used for mapping the original call the UE is trying to continue with Re-establishment procedure. If UE uses
wrong CRTNI or tries Re-establishment to a different cell compared to original cell, eNB always rejects the
RRCConnectionReestablishmentRequest [1], [5]
eNB UE S1AP ID
•
•
•
•
identifies uniquely user on eNB
together with MME UE S1AP ID it’s used in S1 link for unique user identification
parsed from trace messages according to [7] or from S1AP [2]: INITIAL CONTEXT SETUP REQUEST,
INITIAL CONTEXT SETUP RESPONSE, UE CONTEXT RELEASE REQUEST, HANDOVER
COMMAND, INITIAL UE MESSAGE, E-RAB SETUP REQUEST, E-RAB SETUP RESPONSE, E-RAB
MODIFY REQUEST, E-RAB MODIFY RESPONSE, E-RAB RELEASE COMMAND, E-RAB RELEASE
RESPONSE ...........[2]
MME UE S1AP ID
•
•
•
•
identifies uniquely user on MME
together with UE S1AP ID it’s used in S1 link for unique user identification
parsed from trace messages according to [7] or from S1AP [2]: parsed from S1AP: INITIAL CONTEXT
SETUP REQUEST, INITIAL CONTEXT SETUP RESPONSE, UE CONTEXT RELEASE REQUEST,
HANDOVER COMMAND, E-RAB SETUP REQUEST, E-RAB SETUP RESPONSE, E-RAB MODIFY
REQUEST, E-RAB MODIFY RESPONSE, E-RAB RELEASE COMMAND, E-RAB RELEASE
RESPONSE ...........[2]
MMEC
•
•
MME ID to which UE is connected
parsed from eRRC [1]: RRC CONNECTION REQUEST
| Session details | 10
•
• parsed from S1AP [2] : INITIAL CONTEXT SETUP REQUEST
eNB ID – Macro eNB ID
•
• parsed according to [7]
eNB Name
•
• read from topology when available
• MRBTS/LNBTS/name
CellID
•
• eUtraCellID - identifies cell uniquely within RAN
• Can be read from topology MRBTS/LNBTS/eUtraCellID
• 256*BTS_ID+LCR_ID [5]
PhyCellID
•
• Read from topology MRBTS/LNBTS/LNCEL/phycellid
LCR ID – Local Cell Resource ID – identifies cell uniquely within eNB
•
• Parsed according to [7]
TAC – Tracking Area Code
•
Parsed from S1AP TAI [2]: INITIAL UE MESSAGE, UPLINK NAS TRANSPORT
•
HO Cause
•
• base on X2AP [3]: HANDOVER REQUEST
• base on S1AP [2]: HANDOVER REQUIRED
Target eNB
•
• base on eRRC [1]: RRCConnectionReconfiguration
• base on X2AP [3]: HANDOVER REQUEST (from ecid)
• base on S1AP [2]: HANDOVER REQUIRED (macro eNB available)
Target cell
•
• base on eRRC [1]: RRCConnectionReconfiguration
• base on X2AP [3]: HANDOVER REQUEST (from ecid)
In cause - Prints reason how the UE has entered the cell [5]
•
• Appendix A
Out cause - Prints reason how the UE has exit the cell
•
• Appendix B
Failure cause
•
• reason why call has failed: Appendix A
Failure phase
•
• phase in which SRB or DRB has failed, for details refer to Appendix F
RRC Establishment Cause
•
base on RRCConnection Request and Reestablishment Appendix G - RRC Establishment Cause on page
99
RRC Release Cause [5]
•
• base on RRCConnectionRelease
S1 Establishment Cause
•
•
•
reason why S1 link was established. Information parsed from S1AP: INITIAL UE MESSAGE NAS Cointainer
part (NAS has to be decoded)
S1 Establishment Failure
| Session details | 11
•
•
reason why S1 link establishment failed. Information parsed from S1AP: INITIAL CONTEXT SETUP
FAILURE or PATH SWITH REQUEST FAILURE
S1 Release Cause
reason why S1 interface was released, for details refer to Appendix E, parsed from S1AP: UE CONTEXT
RELEASE COMMAND (MME initiated release), UE CONTEXT RELEASE COMMAND (eNB initiated
release)Appendix C
S1 Release Failure
•
•
•
•
Information parsed from S1AP: UE CONTEXT RELEASE COMMAND (MME initiated release), UE
CONTEXT RELEASE COMMAND (eNB initiated release), S1AP ERROR INDICATIONAppendix C,
X2 Establishment Cause
•
• reason why X2 link was established Information parsed from X2AP HANDOVER REQUEST
X2 Establishment Failure
•
• reason why X2 link establishment failed. Information parsed from X2AP HANDOVER CANCEL
X2 Release Cause
•
• reason why X2 link was released. Information parsed from X2AP UE CONTECT RELEASE REQUEST
X2 Release Failure
•
•
reason why failure on X2 link appeared. Information parsed from X2AP UE CONTECT RELEASE
REQUEST
S-RB Bearer Info
•
• Prints how many signalling radio bearers is currently been established for the call.
• S-RAB: 0 - RRC CONNECTION REQUEST
• S-RAB: 1 - RRC CONNECTION SETUP
• S-RAB: 2 - after RRC SECURITY MODE COMPLETE
D-RB Bearer Info
•
•
Prints how many data radio bearers is currently been allocated for the call. DRB is assosiated with S1AP
INITIAL CONTEXT SETUP or E-RAB SETUP REQUEST
VOLTE Bearer Info
•
•
Prints how many VoLTE (= QCI 1 voice service) DRBS have been allocated for the call with E-RAB SETUP
REQUEST
QCI
•
•
Quality Channel Indicator assigned to RABS. Read from S1AP INITIAL CONTEXT SETUP or E-RAB
SETUP REQUEST
# Link Reestablishment
•
number of link reestablishment, increased when RRC CONNECTION REESTABLISHMENT REQUEST
appears
Session is analysed message by message. After every message session information are updated accordingly
Establishment Cause
Establisment cause or reestablishment is filled in base on RRCConnectionRequest message or in case of connection
reestablishment base on RRCConnectionReestablishmentRequest. Reason can be read from IE:
•
•
establishmentCause
reestablishmentCause
For list of possible value refer to [1], [9] or Appendix A
Message example:
| Session details | 12
•
RRCConnectionRequest
UL-CCCH-Message : {
message c1 : rrcConnectionRequest : {
criticalExtensions rrcConnectionRequest-r8 : {
ue-Identity s-TMSI : {
mmec '10101010'B,
m-TMSI '10101010101010101010101010101010'B
},
establishmentCause highPriorityAccess,
spare '1'B
}
}
}
•
RRCCeonnectionReestablismentRequest
UL-CCCH-Message : {
message c1 : rrcConnectionReestablishmentRequest : {
criticalExtensions rrcConnectionReestablishmentRequest-r8 : {
ue-Identity {
c-RNTI '1010101010101010'B,
physCellId 0,
shortMAC-I '1010101010101010'B
},
reestablishmentCause reconfigurationFailure,
spare '10'B
}
}
}
C-RNTI
C-RNTI identifies the mobile within a cell. It can be [12]:
•
temp C-RNTI
•
• Allocated during the random access procedure
• May turn into a permanent C-RNTI after concatenation resolution
semi persistent C-RNTI
•
• used to schedule semi persistent resource via PDCCH
• SPS-CRNTI is used for scheduling persistent scheduling
permanent C-RNTI
•
•
C-RNTI value assigned after contention resolution after a random access
used for scheduling dynamic resources
It defines unambiguously which data sent in a DL direction within a particular LTE cell belongs to a particular
subscriber. For instance, all RRC messages belonging to a single connection between a UE and the network are
marked with the same C-RNTI value by the MAC entity that provided transport services to the RRC and NAS. Thus,
C-RNTI is an important parameter for call tracing.
| Session details | 13
Figure 2: C-RNTI
C-RNTI can be found in:
•
•
TraceObject.CorrelationInfo [7]
RRCReestablismentConnectionRequest
Table 4: Open Topic
Subject
Explanation
Does eNB treats reestablisment as
separate session
Do we need to combine reestablished
session base on same CRNTI
eNB S1AP UE ID
eNB S1AP UE ID identify uniquely UE withing a eNB. The ID us used over the S1-MME interface. eNB S1AP UE
ID is also used during X2 HO by marking 'old' and 'new' value.
Figure 3: LTE identification [13]
| Session details | 14
eNB S1AP UE ID can be found in:
•
•
•
•
TraceObject.Value - eNB UE S1AP ID [7]
S1APInitialUEMessage
S1APInitialContextResponse
other S1AP messages
Message example:
•
S1AP-PDU : initiatingMessage : {
procedureCode 12,
criticality ignore,
value InitialUEMessage : {
protocolIEs {
{
id 8,
criticality 0,
value ENB-UE-S1AP-ID : 0
},
{
...
MME UE S1AP ID
MME S1AP UE ID identify uniquely UE withing a MME. The ID us used over the S1-MME interface. The Id can be
parsed from L3 messages, e.g.:
•
•
S1APInitialContextSetupRequest
S1APInitialContextSetupResponse
Message example:
•
S1AP-PDU : initiatingMessage : {
procedureCode 9,
criticality reject,
value InitialContextSetupRequest : {
protocolIEs {
{
id 0,
criticality 0,
value MME-UE-S1AP-ID : 0
},
{
id 8,
criticality 0,
value ENB-UE-S1AP-ID : 0
},
...
TAC
TAC - tracking area code is a part of TAI - Tracking Area Identity (MCC+MNC+TAC). Typically all cells of eNB
would constitute a tracking area. The Id can be parsed from L3 messages, e.g.:
•
S1APInitialUEMessage
Meassge example:
•
S1AP-PDU : initiatingMessage : {
| Session details | 15
procedureCode 12,
criticality ignore,
value InitialUEMessage : {
protocolIEs {
{
id 8,
criticality 0,
value ENB-UE-S1AP-ID : 0
},
{
id 26,
criticality 0,
value NAS-PDU : ''H
},
{
id 67,
criticality 0,
value TAI : {
pLMNidentity '616263'H,
tAC '6162'H
}
},
...
EPS Session/Bearer Identifiers
Concept definition.
An EPS session is in charge of delivering and handling flows of the IP packets that are labeled with UE IP addresses
and travel between a UE and a PDN (UE – P-GW – PDN). On the other hand, an EPS bearer is a pipe through which
IP packets are delivered over the LTE network, i.e., between a UE and a P-GW (UE – eNB – S-GW - P-GW). A UE
can have multiple EPS bearers concurrently. So, different EPS bearers are identified by their EPS bearer ID, which is
allocated by an MME.
As seen in figure above, an EPS bearer actually is a concatenation of the following three bearers (DRB, S1 bearer and
S5 bearer):
•
•
[UE] - [eNB]: Data Radio Bearer (DRB) - EPS bearer established over LTE-Uu interface. User traffic (IP packet)
is delivered through a DRB. Different DRBs are identified by their DRB ID, which is allocated by an eNB.
[eNB] - [S-GW]: S1 bearer - EPS bearer established over S1-U interface. User traffic is delivered through a GTP
tunnel. Different S1 bearers are identified by their tunnel endpoint identifier (TEID), which is allocated by the
endpoints (eNB and S-GW) of the GTP tunnel.
| Session details | 16
•
[S-GW] - [P-GW]: S5 bearer - EPS bearer established over S5 interface. User traffic is delivered through a GTP
tunnel. Different S5 bearers are identified by their tunnel endpoint identifier (TEID), which is allocated by the
endpoints (S-GW and P-GW) of the GTP tunnel.
E-RAB is a bearer that has two endpoints of a UE and an S-GW, and consists of a DRB and an S1 bearer.
Technically, E-RAB is a concatenation of a DRB and an S1 bearer, and connects from a UE to an S-GW (UE – eNB
– S-GW). Different E-RABs are identified by their E-RAB ID, which is allocated by an MME. DRB IDs and E-RAB
IDs are mapped with EPS bearer IDs on 1:1 basis. [2,22].
| Session analysis | 17
Session analysis
Trace session analysis mostly base on [5],[8].
Reason is a combination of four fields in the report
•
•
•
•
In_Cause
Out_Cause
Failure_Cause
Failure_Phase
Table 5: Definitions of the contents of the messages
Fail Phase
Fail Message
Failure Cause
S1 Cause
RRC Setup
RRC
CONNECTION
REJECT
RRC Reject
-
No radio
resources
RRC
CONNECTION
SETUP
No UE Reply
-
RRC
CONNECTION
SETUP
COMPLETE
missing
S1AP INITIAL
UE MESSAGE
eNB Release
-
S1AP INITIAL
UE MESSAGE
missing from
S1; S1 interface
unavailable
S1AP INITIAL
CONTEXT
SETUP
REQUEST
No EPC
Messages
-
No answer from
MME to S1AP
INITIAL UE
MESSAGE
S1AP
DOWNLINK
NAS
TRANSPORT
No EPC
Messages
-
DOWNLINK
NAS
TRANSPORT
message missing
S1AP UE
CONTEXT
RELEASE
REQUEST
Radio Link
Failure
21: radioconnection-withue-lost
Radio connection
with the ue lost
before MME
sends INITIAL
CONTEXT
SETUP
REQUEST
S1AP UE
CONTEXT
RELEASE
COMMAND
EPC Release
See sheet
"S1 release
cause" e.g. 0:
Unspecified
MME does not
accept the request
made in the
NAS message
included in S1AP
INITIAL UE
MESSAGE.
RRC Access
X2 Cause
Description
| Session analysis | 18
Fail Phase
Fail Message
Re-est Setup
RRC
No UE Reply
CONNECTION
REESTABLISHMENT
COMPLETE
-
UE does not
send RRC
CONNECTION
REESTABLISHMENT
COMPLETE
message
RRC
Re-est Reject
CONNECTION
REESTABLISHMENT
REJECT
-
eNB rejects RRC
CONNECTION
REESTABLISHMENT
S1AP INITIAL
CONTEXT
SETUP
FAILURE
RAB Setup
Failure
See sheet
"S1 release
cause" e.g.
14: unknowneNodeB-ueS1-apid 15:
unknown-pairUe-S1-apid 27:
invalid QOS
combination
32: encryption
and or integrity
protection
algorithms not
supported 25:
radio resources
not available ??:
transportresourceunavailable 21:
radio-connectionwith-ue-lost
26: failure-inradio-interfaceprocedure
eNB releases
resources because
it has detected
an error See
sheet "S1 release
cause" for
UEContextReleaseCommand
message
failure cause
descriptions.
SRB or DRB
connection is
rejected because
eNB is lacking
resources and
failure is not
defined by any
other fail causes
See sheet "S1
release cause" for
UEContextReleaseCommand
message
failure cause
descriptions. eNB
releases resources
because of L1/L2
Radiolink Failure
is detected faster
than RRC guard
timer expires
No UE Reply
26: failure-inradio-interfaceprocedure
UE doest not
reply to RRC
SECURITY
MODE
COMMAND,
RRC UE
CAPABILITY
ENQUIRY
or RRC
RAB Setup
Failure Cause
S1 Cause
X2 Cause
Description
| Session analysis | 19
Fail Phase
Fail Message
Failure Cause
S1 Cause
X2 Cause
Description
CONNECTION
RECONFIGURATION
message during
guard time
interval
RAB Access
RAB Active
RRC
SECURITY
MODE
FAILURE
UE RRC Reject
32: encryption
and or integrity
protection
algorithms not
supported
RRC SECURITY
MODE
FAILURE is sent
by UE. Mismatch
in encryption/
integrity
protection
algorithms.
INITIAL
CONTEXT
SETUP
FAILURE
Radio Link
Failure
21: radioconnectionwith-ue-lost
26: failure-inradio-interfaceprocedure
eNB releases
resources
because of L1/L2
Radiolink Failure
eNB Release
See sheet
"S1 release
cause" e.g. 0:
Unspecified
eNB internal
failure causes
radio bearer
release.
Radio Link
Failure
21: radioconnectionwith-ue-lost
26: failure-inradio-interfaceprocedure
eNB releases
resources
because of L1/L2
Radiolink Failure
eNB Release
See sheet
"S1 release
cause" e.g. 0:
Unspecified
eNB internal
failure or RLC
failure causes
radio bearer
release.
EPC Release
See sheet
"S1 release
cause" e.g. 32:
nas: normalrelease 38: nas:
unspecified …
MME has noticed
UE has dropped
and appeared in a
new cell and eNB
has active RLF
or RLC error on.
Or MME has
call processing
problems
-
eNB notices the
re-establisment
and releases old
RRC connection
S1AP UE
CONTEXT
RELEASE
REQUEST
S1AP UE
CONTEXT
RELEASE
COMMAND
RRC
Re-establishment
CONNECTION
REESTABLISHMENT
REQUEST
| Session analysis | 20
Fail Phase
Fail Message
Source Intra HO
Setup
RRC
No eNB
CONNECTION resources
RECONFIGURATION
-
RRC
CONNECTION
RECONFIGURATION
message missing
(no action
to UE RRC
measurement
report by eNB).
This is not visible
as error in source
cell through cell
trace. This is
visible in Traffica
only if RB is
released due to
this in source
cell.
Source Intra HO
Access
S1AP UE
CONTEXT
RELEASE
REQUEST
Radio Link
Failure
21: radioconnectionwith-ue-lost
26: failure-inradio-interfaceprocedure
eNB releases
resources
because of L1/
L2 Radiolink
Failure.
eNB Release
See sheet
"S1 release
cause" e.g. 0:
Unspecified
eNB internal
failure or RLC
failure causes
radio bearer
release.
RRC
Re-establishment
CONNECTION
REESTABLISHMENT
REQUEST
-
UE didn't
receive RRC
CONNECTION
RECONFIGURATION
messages and
makes reestablishment.
eNB notices the
re-establisment
and releases old
RRC connection.
RRC
No UE Messages
CONNECTION
RECONFIGURATION
COMPLETE
-
RRC
CONNECTION
RECONFIGURATION
COMPLETE
message missing
RRC
Re-establishment
CONNECTION
REESTABLISHMENT
REQUEST
-
Handover failure
and UE makes reestablihement to
target cell.
Target Intra HO
Setup
Failure Cause
S1 Cause
X2 Cause
Description
| Session analysis | 21
Fail Phase
Fail Message
Failure Cause
S1 Cause
Target Intra HO
Access
S1AP UE
CONTEXT
RELEASE
REQUEST
Radio Link
Failure
21: radioconnectionwith-ue-lost
26: failure-inradio-interfaceprocedure
eNB releases
resources
because of L1/L2
Radiolink Failure
eNB Release
See sheet
"S1 release
cause" e.g. 0:
Unspecified
eNB internal
failure or RLC
failure causes
radio bearer
release.
RRC
No UE Reply
CONNECTION
RECONFIGURATION
COMPLETE
e.g. 26: failurein-radiointerfaceprocedure
RRC
CONNECTION
RECONFIGURATION
COMPLETE
message missing
RRC
Re-establishment
CONNECTION
REESTABLISHMENT
REQUEST
-
RRC
CONNECTION
RECONFIGURATION
procedure fails.
X2AP
X2 HO Rejected
HANDOVER
PREPARATION
FAILURE
-
Target eNB
doesn't have
resources or
has other call
processing
problems. If
the call ends
to failure, X2
HO Rejected as
error. If call ends
successfully (eg.
User inactivity
or successful
handover) the
X2 handover
preparation
failure will not be
visible.
X2AP
HANDOVER
CANCEL
X2 HO Failed
-
S1AP UE
CONTEXT
RELEASE
REQUEST
Radio Link
Failure
21: radioconnection-withue-lost
eNB releases
resources
because of L1/L2
Radiolink Failure
eNB Release
See sheet
"S1 release
eNB internal
failure or RLC
Source Inter X2
HO Setup
X2 Cause
9: TX2 Reloc
Overall Expiry
10: TRELOC
Preparation
Expiry
Description
X2AP
HANDOVER
REQUEST
ACKNOWLEDGE
message missing.
| Session analysis | 22
Fail Phase
Source Inter X2
HO Access
Target Inter X2
HO Setup
Fail Message
Failure Cause
S1 Cause
X2 Cause
Description
cause" e.g. 0:
Unspecified
failure causes
radio bearer
release.
Radio Link
Failure
21: radioconnectionwith-ue-lost
26: failure-inradio-interfaceprocedure
Source eNB
releases resources
because of L1/L2
Radiolink Failure
eNB Release
See sheet
"S1 release
cause" e.g. 0:
Unspecified
eNB internal
failure or RLC
failure causes
radio bearer
release.
9. TX2 Reloc
Overall Expiry
X2AP UE
CONTEXT
RELEASE
message missing.
tX2 relocation
timer expires.
RRC
Re-establishment
CONNECTION
REESTABLISHMENT
REQUEST
-
UE didn't
receive RRC
CONNECTION
RECONFIGURATION
messages and
makes reestablishment.
eNB notices the
re-establisment
and releases old
RRC connection.
RRC
No UE Messages
CONNECTION
RECONFIGURATION
COMPLETE
-
RRC
CONNECTION
RECONFIGURATION
COMPLETE
message missing
X2AP UE
CONTEXT
RELEASE
REQUEST
X2AP
X2 HO Reject
HANDOVER
PREPARATION
FAILURE
radioNetwork 5:
Unknown New
eNB UE X2AP
ID 6: Unknown
Old eNB UE
X2AP ID 7:
Unknown Pair
of UE X2AP ID
8: HO Target
not Allowed
11: Cell not
Available 12: No
Radio Resources
Available in
Failure in target
cell/eNB. X2
Handover request
is rejected via
HandoverPreparationFailure
message
| Session analysis | 23
Fail Phase
Fail Message
Failure Cause
S1 Cause
X2 Cause
Description
Target Cell
13: Invalid
MME Group ID
14: Unknown
MME Code 15:
Encryption And/
Or Integrity
Protection
Algorithms Not
Supported 16:
ReportCharacteristicsEmpty
17:
NoReportPeriodicity
18:
ExistingMeasurementID
19: Unknown
eNB
Measurement ID
20: Measurement
Temporarily not
Available 21:
Unspecified 25:
Value out of
allowed range 26:
Multiple E-RAB
ID instances
27: Switch Off
Ongoing 28: Not
supported QCI
value transport
256: Transport
Resource
Unavailable 517:
Unspecified
protocol 512:
Transfer Syntax
Error 513:
Abstract Syntax
Error (Reject)
514: Abstract
Syntax Error
(Ignore and
Notify) 516:
Semantic
Error 517:
Unspecified 518:
Abstract Syntax
Error (Falsely
Constructed
Message) misc
768: Control
Processing
Overload 769:
Hardware Failure
| Session analysis | 24
Fail Phase
Fail Message
Failure Cause
S1 Cause
X2 Cause
Description
770: O&M
Intervention 771:
Not enough User
Plane Processing
Resources 772:
Unspecified
Target Inter X2
HO Access
RRC
Re-establishment
CONNECTION
REESTABLISHMENT
REQUEST
-
Handover failure
and UE makes reestablihement to
target cell.
S1AP PATH
SWITCH
REQUEST
FAILURE
X2 HO Reject
All causes shown
on sheet "S1
establishment
failure cause" on
PathSwitchRequestFailure
message are
possible.
See sheet "S1
establishment
failure cause" for
PathSwitchRequestFailure
message.
S1AP PATH
SWITCH
REQUEST
No EPC
Messages
-
PATH SWITCH
REQUEST
ACKNOWLEDGE
message missing
21: radioconnectionwith-ue-lost
26: failure-inradio-interfaceprocedure
eNB releases
resources
because of L1/L2
Radiolink Failure
eNB release
See sheet
"S1 release
cause" e.g. 0:
Unspecified
eNB internal
failure or RLC
failure causes
radio bearer
release.
No UE Reply
e.g. 26: failurein-radiointerfaceprocedure
RRC
CONNECTION
RECONFIGURATION
COMPLETE
message missing
RRC
Re-establishment
CONNECTION
REESTABLISHMENT
REQUEST
-
RRC
CONNECTION
RECONFIGURATION
procedure fails.
S1AP
HANDOVER
COMMAND
-
HANDOVER
COMMAND
missing from
MME as a
reply to S1AP
RRC
Radio Link
CONNECTION Failure
RECONFIGURATION
COMPLETE
Source Inter S1
HO Setup
No EPC Reply
| Session analysis | 25
Fail Phase
Fail Message
Failure Cause
S1 Cause
X2 Cause
Description
HANDOVER
REQUIRED
Source Inter S1
HO Access
S1AP
S1 HO Reject
HANDOVER
PREPARATION
FAILURE
Causes shown
on sheet "S1 Rel.
Failure cause" on
HandoverFailure
message.
S1 Handover
request is
rejected via
HandoverFailure
message. This
is not visible as
error in source
cell through cell
trace. This is
visible in Traffica
only if RB is
released due to
this.
S1AP UE
CONTEXT
RELEASE
REQUEST
Radio Link
Failure
21: radioconnection-withue-lost
eNB releases
resources
because of L1/L2
Radiolink Failure
eNB Release
See sheet
"S1 release
cause" e.g. 0:
Unspecified
eNB internal
failure or RLC
failure causes
radio bearer
release.
eNB Release
8: ts1 reloc
overall expiry
UE CONTEXT
RELEASE
COMMAND
missing.
See sheet
"S1 release
cause" e.g. 0:
Unspecified
eNB internal
failure or RLC
failure causes
radio bearer
release.
21: radioconnection-withue-lost
eNB releases
resources
because of L1/L2
Radiolink Failure
-
UE didn't
receive RRC
CONNECTION
RECONFIGURATION
messages and
makes reestablishment.
eNB notices the
re-establisment
and releases old
RRC connection.
S1AP UE
CONTEXT
RELEASE
REQUEST
Radio Link
Failure
RRC
Re-establishment
CONNECTION
REESTABLISHMENT
REQUEST
| Session analysis | 26
Fail Phase
Fail Message
Failure Cause
S1 Cause
Target Inter S1
HO Setup
S1AP
HANDOVER
FAILURE
S1 HO Reject
Causes shown
on sheet "S1 Rel.
Failure cause" on
HandoverFailure
message.
S1 Handover
request is
rejected via
HandoverFailure
message
RRC
No UE Messages
CONNECTION
RECONFIGURATION
COMPLETE
-
RRC
CONNECTION
RECONFIGURATION
COMPLETE
message missing
S1AP MME
STATUS
TRANSFER
No EPC Reply
-
S1AP MME
STATUS
TRANSFER
message missing
S1AP UE
CONTEXT
RELEASE
REQUEST
EPC Release
-
MME releases
UE context
release (eg. Due
to problems
in MME)
before RRC
CONNECTION
RECONFIGURATION
COMPLETE is
received.
RRC
Re-establishment
CONNECTION
REESTABLISHMENT
REQUEST
-
Handover failure
and UE makes reestablihement to
target cell.
S1AP UE
CONTEXT
RELEASE
REQUEST
Radio Link
Failure
21: radioconnection-withue-lost
eNB releases
resources
because of L1/L2
Radiolink Failure
eNB Release
See sheet
"S1 release
cause" e.g. 0:
Unspecified
eNB internal
failure or RLC
failure causes
radio bearer
release.
RRC
No UE Reply
CONNECTION
RECONFIGURATION
COMPLETE
-
RRC
CONNECTION
RECONFIGURATION
COMPLETE
message missing
RRC
Re-establishment
CONNECTION
REESTABLISHMENT
REQUEST
-
RRC
CONNECTION
RECONFIGURATION
procedure fails.
Target Inter S1
HO Access
X2 Cause
Description
| Session analysis | 27
Fail Phase
Fail Message
Failure Cause
S1 Cause
Idle I-RAT HO
Setup
S1AP UE
CONTEXT
RELEASE
COMMAND
No EPC Reply
-
MME doesn't
reply to S1AP
CONTEXT
RELEASE
REQUEST
S1AP UE
CONTEXT
RELEASE
REQUEST
eNB Release
See sheet
"S1 release
cause" e.g. 0:
Unspecified
eNB internal
failure causes
radio bearer
release.
The final session results table should look like example below:
Table 6: Session analysis results - basic LTE call
Parameter
Value
Trace ID or TRSR
Session Start Time
Session Stop Time
Session duration
MMEC
8 bits
M-TMSI
32 bits
TAC
16 bits
MCC
12 bits
MNC
12 bits
eNB ID
20 bits
eNB Name
80 character
eUtraCellId
20 bits
PhysCellId
0...511
UE eNB S1AP ID
24 bits
MME Ue S1AP ID
32 bits
LCR ID
0..256
In Cause
int (enum)
Out Cause
int (enum)
Failure cause
int (enum)
Failure Phase
int (enum)
RRC Establishment Cause
int (enum)
RRC Release Cause
int (enum)
S1 Establishment Cause
int (enum)
X2 Cause
Description
| Session analysis | 28
Parameter
Value
S1 Establishment Failure
int (enum)
S1 Release Cause reason
int (enum)
S1 Release Failure
int (enum)
X2 Establishment Cause
int (enum)
X2 Establishment Failure
int (enum)
X2 Release Cause
int (enum)
X2 Release Failure
int (enum)
HO Cause
int (enum)
Target eNB
20 bits
Target ECI
28 bits
#S-RB Bearer
0...x (int)
#D-RB Bearer
0...x (int)
#E-RAB Bearer
0...x (int)
QCI
0..15
#Link reestablishment
0...x (int)
Table 7: Bearer information
ID
Start time
Stop time
QCI
5
INITIAL CONTEXT
SETUP REQUEST
UE CONTEXT RELEASE 8
REQUEST
INITIAL UE MESSAGE
-
-
------------------------------------------------------------------------
Basic LTE call
Basic LTE call - success scenario
-
-
| Session analysis | 29
In basic LTE call SRB and default DRAB (Data Radio Access Bearer ) are assigned. Call ends successfully. DRB is
assigned with S1AP INITIAL CONTEXT SETUP REQUEST. Information IF DRAB is requested to be established
can be found in 'value E-RABToBeSetupListCtxtSUReq'
S1AP-PDU : initiatingMessage : {
procedureCode 9,
criticality reject,
value InitialContextSetupRequest : {
protocolIEs {
........,
{
id 24,
criticality 0,
value E-RABToBeSetupListCtxtSUReq : {
{
id 52,
criticality 0,
value E-RABToBeSetupItemCtxtSUReq : {
e-RAB-ID 0,
e-RABlevelQoSParameters {
qCI 0,
allocationRetentionPriority {
priorityLevel 0,
pre-emptionCapability shall-not-trigger-pre-emption,
pre-emptionVulnerability not-pre-emptable
}
},
transportLayerAddress ''B,
gTP-TEID '61626364'H
}
}
}
},
.......
}
}
}
Let's see how the data is filled in step by step:
| Session analysis | 30
Table 8: Session analysis in details
Message
Parameter
START TRACE
Session start time
RRC CONNECTION REQUEST
In cause: 1-New SRB;
RRC Establishment Reason
RRC CONNECTION SETUP
S-RB: 1
RRC CONNECTION SETUP COMPLETE
S1AP INITIAL UE MESSAGE
S1 Establishment Cause
eNB UE S1AP ID
MMEC
TAI
S1AP INITIAL UE CONTEXT SETUP REQUEST
In cause: 2- New Call;
E-RAB:1 QCI: 8; Allocation Time
MME UE S1 AP ID
RRC SECURITY MODE COMMAND
RRC CONNECTION RECONFIGURATION
D-RB:1; S-RB:2
RRC SECURITY MODE COMPLETE
RRC CONNECTION RECONFIGURATION
COMPLETE
S1AP INITIAL CONTEXT SETUP RESPONSE
S1AP UE CONTEXT RELEASE REQUEST
S1 Release Cause
S1AP UE CONTEXT RELEASE COMMAND
RRC CONNECTION RELEASE
RRC Release Reason
S1AP UE CONTEXT RELEASE COMPLETE
D-RB:1; E-RAB:1 QCI: 8; Release time
Stop Trace
Session stop time
Out Cause: 2 - Call end
Table 9: Session analysis results - basic LTE call
Parameter
Value
In Cause
2 - New Call
Out Cause
2 - Call end
Failure cause
Failure Phase
1 - No Failure
S1 Establishment Cause
NAS S1AP INITIAL UE MESSAGE
S1 Establishment Failure
| Session analysis | 31
Parameter
Value
S1 Release Cause reason
S1 Release Failure
S1AP UE RELEASE CONTEXT REQUEST
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
2
#D-RB Bearer
1
#E-RAB Bearer
1
QCI
8
Table 10: Bearer information
ID
Start time
Stop time
QCI
5
INITIAL CONTEXT
SETUP REQUEST
UE CONTEXT RELEASE 8
REQUEST
INITIAL UE MESSAGE
----------------------------------------------------------------------------------------------------------------------------------Basic LTE call - failure during RRC establishment due to RRCConnectionReject
Figure 4: RRC Connection establishment failure [1]
Let's see how the data is filled in step by step:
Table 11: Session analysis in details
Message
Parameter
START TRACE
Session start time
RRC CONNECTION REQUEST
In cause: 1-New SRB;
RRC Establishment Reason
RRC CONNECTION REJECT
STOP TRACE
Session stop time
Out Cause: 1 - SRB Released
| Session analysis | 32
Message
Parameter
Failure cause: 20 - RRC Connection Reject
Failure Phase: RRC Setup
Table 12: Session analysis results - basic LTE call
Parameter
Value
In Cause
1 - New SRB
Out Cause
1- SRB released
Failure cause
20 - RRC Reject
Failure Phase
2 - RRC Setup
S1 Establishment Cause
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
#D-RB Bearer
#E-RAB Bearer
QCI
Table 13: Bearer information
ID
Start time
Stop time
QCI
----------------------------------------------------------------------------------------------------------------------------------Basic LTE call - failure during RRC establisment due to no response from UE
This scenario can happen if RRCConnectionSetupComplete was not send by UE. According to [1] and section "
11.2 Processing delay requirements for RRC procedures" UE must respond in time = 15ms. If UE doesn't send
RRCConnectionSetupComplete within 15ms+delta and/or additionally StopTime is not available such session can be
closed.
| Session analysis | 33
Figure 5: Basic LTE call - no response from UE [8]
According to [1], section 11.2 " Processing delay requirements for RRC procedures", UE has to answer N=15, where
N=1ms. If not do that, session ends. In this case, if StopTrace is missed, session ca be end by the Ratina system.
Let's see how the data is filled in step by step:
Table 14: Session analysis in details
Message
Parameter
START TRACE
Session start time
RRC CONNECTION REQUEST
In cause: 1-New SRB;
RRC Establishment Reason
RRC CONNECTION SETUP
SRB: 1
STOP TRACE
Session stop time
Out Cause: 1 - SRB Release
Failure cause: 17 - No UE Reply
Failure Phase: RRC Setup
Table 15: Session analysis results - basic LTE call
Parameter
Value
In Cause
1 - New SRB
Out Cause
1 - SRB Release
Failure Cause
17 - No UE Reply
Failure Phase
2 - RRC Setup
S1 Establishment Cause
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer Info
1
| Session analysis | 34
Parameter
Value
#D-RB Bearer Info
#E-RAB Bearer Info
QCI
Table 16: Bearer information
ID
Start time
Stop time
QCI
----------------------------------------------------------------------------------------------------------------------------------Basic LTE call - failure during authentication procedure or authentication reject
The MME sends an unciphered Authentication Request to the UE. The message contains the RAND and AUTN
numbers. Key selection identifier (KSI-ASME) is also included in the message. The UE reads the shared secret K
key from the USIM. The UE computes an authentication result (RES) from the key K and the received AUTN and
RAND values. The UE sends the RES value back to the MME. The MME compares the RES value received from the
UE with the XRES value specified by the HSS. Matching of the two values authenticates the UE. In this scenario, the
values match and the MME proceeds with NAS security procedure.
Procedure can fail either on UE or in Core network. If calculated by Ue keys do not match to those stored
in MME, CORE network sends NAS AUTH REJ to UE . Core network will release UE context by sending
S1APUEContextReleaseCommand with cause: nas authentication-failure [2,17] . In case of failure in
UE, NAS AuthenticationFailure is send to Core Network. Core newtork will release connection sending
S1APUEContextReleaseCommand cause: nas authentication-failure [2,17]
Figure 6: Basic LTE call - failure during authentication procedure
Let's see how the data is filled in step by step:
Table 17: Session analysis in details
Message
Parameter
START TRACE
Session start time
| Session analysis | 35
Message
Parameter
RRC CONNECTION REQUEST
In cause: 1-New SRB;
RRC Establishment Reason
RRC CONNECTION SETUP
S-RB: 1
RRC CONNECTION SETUP COMPLETE
S1AP INITIAL UE MESSAGE
S1 Establishment Cause
eNB UE S1AP ID
MMEC
TAI
S1AP DOWNLINK NAS TRANSPORT: AUTH REQ
RRC INFORMATION TRANSFER: AUTH REQ
RRC INFORMATION TRANSFER: AUTH RESP
S1AP DOWNLINK NAS TRANSPORT: AUTH RESP
S1AP UE CONTEXT RELEASE REQUEST
S1 Release Cause (authentication fail)
Out Cause: 2 - Call end
Failure cause: 12 - EPC Release
Failure phase: 5- RRC Access
S1AP UE CONTEXT RELEASE COMMAND
RRC CONNECTION RELEASE
RRC Release Reason
S1AP UE CONTEXT RELEASE COMPLETE
Stop Trace
Session stop time
Table 18: Session analysis results - basic LTE call
Parameter
Value
In Cause
2 - New Call
Out Cause
2 - Call end
Failure cause
12 - EPC Release
Failure Phase
5- RRC Access
S1 Establishment Cause
NAS S1AP INITIAL UE MESSAGE
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
S1AP UE RELEASE CONTEXT REQUEST
| Session analysis | 36
Parameter
Value
X2 Release Failure
#S-RB Bearer
1
#D-RB Bearer
#E-RAB Bearer
QCI
Table 19: Bearer information
ID
Start time
Stop time
QCI
----------------------------------------------------------------------------------------------------------------------------------Basic LTE call - failure during security mode procedure
RRCSecurityModeReject ussually indicates problems in the handset during activation and/or RRC/User Plane
integrity checking. [1, 18, 19]
According to 3GPP 36.331 [1]: - continue using the configuration used prior to the reception of the
SecurityModeCommand message, i.e. neither apply integrity protection nor ciphering. but: 36.413 If the supported
algorithms for integrity defined in the Integrity Protection Algorithms IE in the UE Security Capabilities IE, plus the
mandated support of the EIA0 algorithm in all UEs (TS 33.401 [15]), do not match any allowed algorithms defined
in the configured list of allowed integrity protection algorithms in the eNB (TS 33.401 [15]), the eNB shall reject the
procedure using the INITIAL CONTEXT SETUP FAILURE message.
Figure 7: Basic LTE call - security mode failure
Let's see how the data is filled in step by step:
Table 20: Session analysis in details
Message
Parameter
START TRACE
Session start time
| Session analysis | 37
Message
Parameter
RRC CONNECTION REQUEST
In cause: 1-New SRB;
RRC Establishment Reason
RRC CONNECTION SETUP
S-RB: 1
RRC CONNECTION SETUP COMPLETE
S1AP INITIAL UE MESSAGE
S1 Establishment Cause
eNB UE S1AP ID
MMEC
TAI
S1AP INITIAL UE CONTEXT SETUP REQUEST
In cause: 2- New Call;
E-RAB:1; QCI: 8; Allocation Time
MME UE S1 AP ID
RRC SECURITY MODE COMMAND
D-RB:1; S-RB:2
RRC CONNECTION RECONFIGURATION
RRC SECURITY MODE FAILURE
S1AP INITIAL CONTEXT SETUP FAILURE
S1 Establishment Failure (unspecified)
S1AP UE CONTEXT RELEASE COMMAND
Out Cause: 2 - Call end
Failure cause: 16 - RAB Setup Failure
Failure phase: 5- RAB Access
RRC CONNECTION RELEASE
RRC Release Reason
S1AP UE CONTEXT RELEASE COMPLETE
D-RB:1; QCI: 8; Release time
Stop Trace
Session stop time
Out Cause: 2 - Call end
Table 21: Session analysis results - basic LTE call
Parameter
Value
In Cause
2 - New Call
Out Cause
2 - Call end
Failure cause
16 - RAB Setup Failure
Failure Phase
4 - RAB Setup
S1 Establishment Cause
NAS S1AP INITIAL UE MESSAGE
S1 Establishment Failure
S1AP INITIAL CONTEXT SETUP FAILURE
S1 Release Cause reason
S1AP UE CONTEXT RELEASE COMMAND
S1 Release Failure
| Session analysis | 38
Parameter
Value
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
2
#D-RB Bearer
1
#E-RAB Bearer
1
QCI
8
Table 22: Bearer information
ID
Start time
Stop time
QCI
5
INITIAL CONTEXT
SETUP REQUEST
S1AP UE CONTEXT
RELEASE COMMAND
8
----------------------------------------------------------------------------------------------------------------------------------Basic LTE Call - RRC only case
Some procedures do not required to setup DRAB, whole session uses SRBs only. That is how e.g. periodical TAU
happens.
Let's see how the data is filled in step by step:
Table 23: Session analysis in details
Message
Parameter
START TRACE
Session start time
RRC CONNECTION REQUEST
In cause: 1-New SRB;
| Session analysis | 39
Message
Parameter
RRC Establishment Reason
RRC CONNECTION SETUP
S-RB: 1
RRC CONNECTION SETUP COMPLETE
S1AP INITIAL UE MESSAGE
S1 Establishment Cause
eNB UE S1AP ID
MMEC
TAI
S1AP DOWNLINK NAS TRANSPORT
RRC DL INFORMATION TRANSFER
RRC UL INFORMATION TRANSFER
S1AP UPLINK INFORMATION TRANSFER
S1AP UE CONTEXT RELEASE COMMAND
S1 Release Cause reason
RRC CONNECTION RELEASE
RRC Release Reason
S1AP UE CONTEXT RELEASE COMPLETE
STOP TRACE
Out Cause: 1 - SRB Released
Table 24: Session analysis results - basic LTE call
Parameter
Value
In Cause
1 - New SRB
Out Cause
1 - SRB Release
Failure cause
1 - No Failure
Failure Phase
S1 Establishment Cause
NAS S1AP INITIAL UE MESSAGE
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
#D-RB Bearer
#E-RAB Bearer
QCI
1
| Session analysis | 40
Table 25: Bearer information
ID
Start time
Stop time
QCI
---------------------------------------------------------------------------------------------------------------------------------------Call Drop in RAB Active state due to UE reply
At any time, after RAB has been established, connection can be reconfigured. According to [1] and section "
11.2 Processing delay requirements for RRC procedures" UE must respond in time = 15ms. If UE doesn't send
RRCConnectionReconfigurationComplete within 15ms+delta and/or additionally StopTime is not available such
session can be closed.
Note: this scenario describes normal session, without HO.
Figure 8: Call Drop in RAB Active state due to UE reply
Let's see how the data is filled in step by step:
Table 26: Session analysis in details
Message
Parameter
RRC CONNECTION RECONFIGURATION
S1AP UE CONTEXT RELEASE REQUEST
S1 Release Cause
Failure cause: 17 - No UE Reply
Failure Phase: 6 - RAB Active
S1AP UE CONTEXT RELEASE COMMAND
RRC CONNECTION RELEASE
RRC Release Reason
S1AP UE CONTEXT RELEASE COMPLETE
E-RAB:1; QCI: 8; Release time
| Session analysis | 41
Message
Parameter
Stop Trace
Session stop time
Out Cause: 2 - Call end
Table 27: Session analysis results - basic LTE call
Parameter
Value
In Cause
according to scenario
Out Cause
2 - Call end
Failure cause
17 - No UE Reply
Failure Phase
6 - RAB Active
S1 Establishment Cause
according to scenario
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
S1AP UE RELEASE CONTEXT REQUEST
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
2
#D-RB Bearer
1
#E-RAB Bearer
1
QCI
8
Table 28: Bearer information
ID
Start time
Stop time
QCI
5
INITIAL CONTEXT
SETUP REQUEST
UE CONTEXT RELEASE 8
REQUEST
----------------------------------------------------------------------------------------------------------------------------------------Call Drop in RRC Active State due to Link Failure
Session can be dropped due to the radio link failure. This can be noted either by receiving MAC RLF or S1AP UE
CONTEXT RELEASE REQUEST cause 'radio-connection-with-ue-lost'
Figure 9: Call Drop in RRC Active State due to Link Failure
| Session analysis | 42
Let's see how the data is filled in step by step:
Table 29: Session analysis in details
Message
Parameter
S1AP UE CONTEXT RELEASE REQUEST
S1 Release Cause cause 'radio-connection-with-ue-lost'
Failure cause: 11 - Radio Link Failure
Failure Phase: 17 - RRC Active
S1AP UE CONTEXT RELEASE COMMAND
RRC CONNECTION RELEASE
RRC Release Reason
S1AP UE CONTEXT RELEASE COMPLETE
Stop Trace
Session stop time
Out Cause: 2 - Call end
Table 30: Session analysis results - basic LTE call
Parameter
Value
In Cause
according to scenario
Out Cause
2 - Call end
Failure cause
11 - Radio Link Failure
Failure Phase
17 - RRC Active
S1 Establishment Cause
according to scenario
| Session analysis | 43
Parameter
Value
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
S1AP UE RELEASE CONTEXT REQUEST cause
'radio-connection-with-ue-lost'
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
2
#D-RB Bearer
according to scenario
#E-RAB Bearer
according to scenario
QCI
x
Table 31: Bearer information
ID
Start time
Stop time
QCI
according to scenario
---------------------------------------------------------------------------------------------------------------------------------------Call Drop in RAB Active State due to Link Failure
Figure 10: Call Dop in RAB Active State due to Link Failure
| Session analysis | 44
Let's see how the data is filled in step by step:
Table 32: Session analysis in details
Message
Parameter
S1AP UE CONTEXT RELEASE REQUEST
S1 Release Cause cause 'radio-connection-with-ue-lost/
failure-in-radio-interface''
Failure cause: 11 - Radio Link Failure
Failure Phase: 6 - RAB Active
S1AP UE CONTEXT RELEASE COMMAND
RRC CONNECTION RELEASE
RRC Release Reason
S1AP UE CONTEXT RELEASE COMPLETE
Stop Trace
Session stop time
Out Cause: 2 - Call end
Table 33: Session analysis results - basic LTE call
Parameter
Value
In Cause
according to scenario
Out Cause
2 - Call end
Failure cause
11 - Radio Link Failure
Failure Phase
6 - RAB Active
S1 Establishment Cause
according to scenario
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
S1AP UE RELEASE CONTEXT REQUEST cause
'radio-connection-with-ue-lost'
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RAB Bearer
2
#D-RAB Bearer
x
#E-RAB Bearer
x
QCI
x
| Session analysis | 45
Table 34: Bearer information
ID
Start time
Stop time
QCI
x
S1AP INITIAL UE
MESSAGE
S1AP UE RELEASE
CONTEXT REQUEST
x
S1AP INITIAL
CONTEXT SETUP
REQUEST
Call reestablishment
The purpose of RRC CONNECTION RE-ESTABLISHMENT procedure is to re-establish the RRC connection, which
involves the resumption of SRB1 operation and the re-activation of security (without changing algorithms). The UE
shall only initiate this procedure when AS security has been activated. The connection re-establishment succeeds
only if the concerned cell is prepared i.e. has a valid UE context. In case E-UTRAN accepts the re-establishment,
SRB1 operation resumes while the operation of other radio bearers remains suspended. If AS security has not been
activated, the UE doesn’t initiate this procedure, instead, it moves to RRC_IDLE directlyThe UE initiates the RRC
CONNECTION RE-ESTABLISHMENT procedure when one of the following conditions is met [1,21]:
•
•
•
•
•
Upon detecting radio link failure; or
Upon handover failure; or
Upon mobility from E-UTRA failure; or
Upon integrity check failure indication from lower layers; or
Upon an RRC CONNECTION RECONFIGURATION failure
Re-established session can be logged as:
•
•
same continued session - it this case session was re-established, but it continues to be reported with same TRSR
new session - new session reported in same or target eNB started with StartTrace
RRC Re-establishment call phase - intra eNB
Figure 11: RRC Re-establishment call phase - intra eNB [8]
In this scenario call continues in same eNB.
Let's see how the data is filled in step by step:
| Session analysis | 46
Table 35: Session analysis in details
Message
Parameter
START TRACE
Session start time
RRC CONNECTION REESTABLISHMENT
REQUEST
3 - Re-establishement
# Link Reestablishment
RRC CONNECTION REESTABLISHMENT
RRC CONNECTION REESTABLISHMENT
COMPLETE
RRC CONNECTION RECONFIGURATION
D-RB:x E-RAB-x; Allocation time
RRC CONNECTION RECONFIGURATION
COMPLETE
S1AP UE CONTEXT RELEASE REQUEST
S1 Release Cause
S1AP UE CONTEXT RELEASE COMMAND
RRC CONNECTION RELEASE
RRC Release Reason
S1AP UE CONTEXT RELEASE COMPLETE
D-RB:x; E-RAB-x; QCI: 8 (if available) ; Release time
Stop Trace
Session stop time
Out Cause: 2 - Call end
Table 36: Session analysis results - call re-establishment in same eNB
Parameter
Value
In Cause
according to the scenario
Out Cause
2 - Call end
Failure cause
Failure Phase
1 - No Failure
S1 Establishment Cause
according to the scenario
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
S1AP UE RELEASE CONTEXT REQUEST
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
2 (according to the scenario)
#D-RB Bearer
x (according to the scenario)
#E-RAB Bearer
x (according to the scenario)
| Session analysis | 47
Parameter
Value
QCI
x (according to the scenario)
# Link Reestablishment
1
Table 37: Bearer information
ID
Start time
Stop time
(according to the scenario)
RRC CONNECTION
RECONFIGURATION
UE CONTEXT RELEASE
REQUEST
QCI
----------------------------------------------------------------------------------------------------------------------------------RRC Re-establishment Reject in source cell
Figure 12: RRC Re-establishment Reject in source cell
Let's see how the data is filled in step by step:
Table 38: Session analysis in details
Message
Parameter
START TRACE
Session start time
....
RRC CONNECTION REESTABLISHMENT
REQUEST
# Link Reestablishment
RRC CONNECTION REESTABLISHMENT REJECT
Failure cause: 10 - Re-est reject
Failure phase: 16 - Re-est Setup
RRC CONNECTION RECONFIGURATION
RRC CONNECTION RECONFIGURATION
COMPLETE
S1AP UE CONTEXT RELEASE REQUEST
S1AP UE CONTEXT RELEASE COMMAND
S1 Release Cause
| Session analysis | 48
Message
Parameter
RRC CONNECTION RELEASE
RRC Release Reason
S1AP UE CONTEXT RELEASE COMPLETE
D-RB:x; E-RAB:x QCI: x ; Release time
Stop Trace
Session stop time
Out Cause: 2 - Call end
Table 39: Session analysis results - call re-establishment in same eNB failure
Parameter
Value
In Cause
according to the scenario
Out Cause
2 - Call end
Failure cause
10 - Re-est reject
Failure Phase
1 - No Failure
S1 Establishment Cause
according to the scenario
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
S1AP UE RELEASE CONTEXT REQUEST
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
2 (according to the scenario)
#D-RB Bearer
x (according to the scenario)
#E-RAB Bearer
x (according to the scenario)
QCI
8 (according to the scenario)
# Link Reestablishment
1
Table 40: Bearer information
ID
Start time
Stop time
(according to the scenario)
(according to the scenario)
UE CONTEXT RELEASE
REQUEST
QCI
----------------------------------------------------------------------------------------------------------------------------------RRC Re-establishment call phases within target cell - inter eNB
This scenario is only possible if target cell has already UE Context available. It's assumed that call has ended
sucessfully.
| Session analysis | 49
Figure 13: RRC Re-establishment call phases within target cell - inter eNB
Let's see how the data is filled in step by step:
Table 41: Session analysis in details
Message
Parameter
START TRACE
Session start time
RRC CONNECTION REESTABLISHMENT
REQUEST
3 - Re-establishement
# Link Reestablishment
RRC CONNECTION REESTABLISHMENT REJECT
RRC CONNECTION RECONFIGURATION
D-RB:x; E-RAB: x: establishment time
RRC CONNECTION RECONFIGURATION
COMPLETE
S1AP PATH SWITCH REQUEST
S1AP PATH SWITCH REQUEST ACKNOWLEDGE
X2AP UE CONTECT RELEASE
S1AP UE CONTEXT RELEASE REQUEST
S1 Release Cause
S1AP UE CONTEXT RELEASE COMMAND
RRC CONNECTION RELEASE
RRC Release Reason
S1AP UE CONTEXT RELEASE COMPLETE
D-RB:1; E-RAB:x QCI: 8 (if available) ; Release time
Stop Trace
Session stop time
Out Cause: 2 - Call end
Table 42: Session analysis results - call re-establishment in target eNB failure
Parameter
Value
In Cause
3 - Re-establishement
| Session analysis | 50
Parameter
Value
Out Cause
2 - Call end
Failure cause
Failure Phase
S1 Establishment Cause
according to the scenario
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
S1AP UE RELEASE CONTEXT REQUEST
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
2 (according to the scenario)
#D-RB Bearer
x (according to the scenario)
#E-RAB Bearer
x (according to the scenario)
QCI
x (according to the scenario)
# Link Reestablishment
1
Table 43: Bearer information
ID
Start time
Stop time
(according to the scenario)
RRC CONNECTION
RECONFIGURATION
UE CONTEXT RELEASE
REQUEST
QCI
----------------------------------------------------------------------------------------------------------------------------------RRC Re-establishment call phases within target cell - inter eNB, failure
As mentioned, re-establishment is possible only if eNB/MME has still UE context available. In this example, context
on MME was already release by source eNB
Figure 14: RRC Re-establishment call phases within target cell - inter eNB, failure
| Session analysis | 51
Let's see how the data is filled in step by step:
Table 44: Session analysis in details
Message
Parameter
START TRACE
Session start time
RRC CONNECTION REESTABLISHMENT
REQUEST
3 - Re-establishement
# Link Reestablishment
RRC CONNECTION REESTABLISHMENT
COMPLETE
RRC CONNECTION RECONFIGURATION
S-RB:2; D-RB=x;E-RAB=x Allocation time
RRC CONNECTION RECONFIGURATION
COMPLETE
S1AP PATH SWITCH REQUEST
S1AP ERROR INDICATION
Failure cause: 12 - EPC Release
Failure phase: 16 - Re-est setup (???) OR ERAB SETUP
X2AP UE CONTECT RELEASE
RRC CONNECTION RELEASE
RRC Release Reason
Stop Trace
Session stop time
Out Cause: 2 - Call end
| Session analysis | 52
Table 45: Session analysis results - call re-establishment in target eNB failure
Parameter
Value
In Cause
according to the scenario
Out Cause
2 - Call end
Failure cause
12 - EPC Release
Failure Phase
16 - Re-est setup (???) OR ERAB SETUP
S1 Establishment Cause
according to the scenario
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
S1AP ERROR INDICATION
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RAB Bearer
2 (according to the scenario)
#D-RAB Bearer
x (according to the scenario)
#E-RAB Bearer
x (according to the scenario)
QCI
x (according to the scenario)
# Link Reestablishment
Table 46: Bearer information
ID
Start time
Stop time
(according to the scenario)
(according to the scenario)
UE ERROR INDICATION
QCI
----------------------------------------------------------------------------------------------------------------------------------RRC Re-establishment call phases within target cell - inter eNB, failure
Figure 15: RRC Re-establishment call phases within target cell - inter eNB, failure
| Session analysis | 53
Table 47: Session analysis results - call re-establishment in target eNB failure
Parameter
Value
In Cause
3 - Re-establishement
Out Cause
2 - Call end
Failure cause
10 - Re-est Reject
Failure Phase
16 - Re-est Setup
S1 Establishment Cause
according to the scenario
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RAB Bearer
-
#D-RAB Bearer
-
#E-RAB Bearer
QCI
-
# Link Reestablishment
Table 48: Bearer information
ID
Start time
Stop time
QCI
| Session analysis | 54
Intra HO
Intra eNB HO is handled within same eNB. HO is triggered by RRC CONNECTION RECONFIGURATION
DL-DCCH-Message : {
message c1 : rrcConnectionReconfiguration : {
rrc-TransactionIdentifier 0,
criticalExtensions c1 : rrcConnectionReconfiguration-r8 : {
mobilityControlInfo {
targetPhysCellId 0,
t304 ms50,
newUE-Identity '1010101010101010'B,
....
}
Intra eNB HO flow and phases
Figure 16: Intra eNB HO phases
Intra eNB HO - source cell
Let's see how the data is filled in step by step:
Table 49: Session analysis in details - intra eNB HO - source cell
Message
Parameter
START TRACE
Session start time
..........
RRC CONNECTION RECONFIGURATION
STOP TRACE
Out Cause: 6 - Intra eNB HO
| Session analysis | 55
Table 50: Session analysis results - intra eNB HO - source cell
Parameter
Value
In Cause
2 - New Call
Out Cause
2 - Call end
Failure cause
Failure Phase
1 - No Failure
S1 Establishment Cause
NAS S1AP INITIAL UE MESSAGE
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
2
#D-RB Bearer
x (according to the scenario)
#E-RAB Bearer
x (according to the scenario)
QCI
x (according to the scenario)
Table 51: Bearer information
ID
Start time
Stop time
QCI
(according to the scenario)
(according to the scenario)
RRC
RECONFIGURATION
REQUEST
(according to the scenario)
Intra eNB HO - target cell
Let's see how the data is filled in step by step:
Table 52: Session analysis in details
Message
Parameter
START TRACE
Session start time
RRC CONNECTION RECONFIGURATION
COMPLETE
In Cause: 6 - Intra eNB HO
RRC CONNECTION RECONFIGURATION
REQUEST
RRC CONNECTION RECONFIGURATION
COMPLETE
S-RB=2;D-RB=x;E-RAB=x; Allocation time
....
| Session analysis | 56
Message
Parameter
STOP TRACE
Table 53: Session analysis results - intra eNB HO - target cell
Parameter
Value
In Cause
6 - Intra eNB HO
Out Cause
according to the scenario
Failure cause
Failure Phase
1 - No Failure
S1 Establishment Cause
S1 Establishment Failure
S1 Release Cause reason
according to the scenario
S1 Release Failure
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
2
#D-RB Bearer
x (according to the scenario)
#E-RAB Bearer
x (according to the scenario)
QCI
x (according to the scenario)
Table 54: Bearer information
ID
Start time
Stop time
QCI
x (according to the
scenario)
RRC CONNECTION
RECONFIGURATION
x (according to the
scenario)
x (according to the
scenario)
----------------------------------------------------------------------------------------------------------------------------------Intra eNB HO - source cell failure
| Session analysis | 57
Figure 17: Intra eNB HO - source cell failure
Let's see how the data is filled in step by step:
Table 55: Session analysis in details
Message
Parameter
START TRACE
Session start time
..........
RRC CONNECTION RECONFIGURATION
Out Cause: 6 - Intra eNB HO
S1AP UE CONTEXT RELEASE REQUEST
Failure cause: 17 - No UE Reply
Failure Phase: 8 - Source Intra HO Access
S1AP UE CONTEXT RELEASE COMMAND
S-RB:2; D-RB:x; E-RAB:x; Release time
RRC CONNECTION RELEASE REQUEST
S1AP UE CONTEXT RELEASE COMPLETE
STOP TRACE
Out Cause: 2 - Call ends
Table 56: Session analysis results - intra eNB HO - source cell failure
Parameter
Value
In Cause
according to the scenario
Out Cause
2- Call ends
Failure cause
17 - No UE Reply
Failure Phase
8 - Source Intra HO Access
S1 Establishment Cause
according to the scenario
S1 Establishment Failure
S1 Release Cause reason
according to the scenario
| Session analysis | 58
Parameter
Value
S1 Release Failure
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
2
#D-RB Bearer
x (according to the scenario)
#E-RAB Bearer
x (according to the scenario)
QCI
x (according to the scenario)
Table 57: Bearer information
ID
Start time
Stop time
x -according to the scenario x -according to the scenario S1AP UE CONTEXT
RELEASE COMPLETE
QCI
x -according to the scenario
----------------------------------------------------------------------------------------------------------------------------------Intra eNB HO - target cell failure
Figure 18: Intra eNB HO - target cell failure
Let's see how the data is filled in step by step:
Table 58: Session analysis in details
Message
Parameter
START TRACE
Session start time
| Session analysis | 59
Message
Parameter
RRC CONNECTION RECONFIGURATION
COMPLETE
In Cause: 6 - Intra eNB HO
RRC CONNECTION RECONFIGURATION
REQUEST
S-RB:2; D-RB:x; E-RAB:x; Allocation time
S1AP UE CONTEXT RELEASE REQUEST
Failure cause: 17 - No UE Reply
Failure Phase: 8 - Source Intra HO Access
S1AP UE CONTEXT RELEASE COMMAND
S-RB:2; D-RB:x; E-RAB:x; Release time
RRC CONNECTION RELEASE REQUEST
S1AP UE CONTEXT RELEASE COMPLETE
STOP TRACE
Out Cause: 2 - Call ends
Table 59: Session analysis results - intra eNB HO - target cell failure
Parameter
Value
In Cause
according to the scenario
Out Cause
2- Call ends
Failure cause
17 - No UE Reply
Failure Phase
12 - Target Intra HO Access
S1 Establishment Cause
S1 Establishment Failure
S1 Release Cause reason
S1AP UE CONTEXT RELEASE COMMAND
S1 Release Failure
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RB Bearer
2
#D-RB Bearer
x (according to the scenario)
#E-RAB Bearer
x (according to the scenario)
QCI
x (according to the scenario)
Table 60: Bearer information
ID
Start time
Stop time
x -according to the scenario x -according to the scenario S1AP UE CONTEXT
RELEASE COMPLETE
QCI
x -according to the scenario
| Session analysis | 60
X2 Inter eNB HO
Figure 19: Inter eNB handover phases from source eNB perspective [8]
Figure 20: Inter eNB handover phases from target eNB perspective
---------------------------------------------------------------------------------------------------------------------------------------------------------------Basic LTE X2 handover scenario.
| Session analysis | 61
Basic LTE X2 handover scenario - source cell
Let's see how the data is filled in step by step:
Table 61: Session analysis in details
Message
Parameter
START TRACE
Session start time
......
X2AP HANDOVER REQUEST
X2 Establsihment Cause
X2AP HANDOVER REQUEST ACKNOWLEDGE
RRC CONNECTION RECONFIGURATION
Out Cause: 5 - Inter eNB HO mobility info tag
X2AP SNSTATUS TRANSFER
X2AP UE CONTEXT RELEASE
X2 Release Cause
STOP TRACE
Table 62: Session analysis results -Basic LTE X2 handover scenario - target cell
Parameter
Value
In Cause
according to the scenario
Out Cause
5 - Inter eNB HO
Failure cause
| Session analysis | 62
Parameter
Value
Failure Phase
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2AP HANDOVER REQUEST
X2 Release Failure
Table 63: Bearer information
ID
Start time
Stop time
QCI
according to the scenario
X2AP HANDOVER
REQUEST or
RRCConnectionReconfiguration ???
Basic LTE X2 handover scenario - target cell
Let's see how the data is filled in step by step:
Table 64: Session analysis in details
Message
Parameter
START TRACE
Session start time
X2AP HANDOVER REQUEST
X2 Establishment Cause
In Cause:
X2AP HANDOVER REQUEST ACKNOWLEDGE
5 - Inter eNB HO
X2AP SNSTATUS TRANSFER
RRC CONNECTION RECONFIGURATION
COMPLETE
S-RB:2; D-RB:x; E-RAB:x ; Allocation time
S1AP PATH SWITCH REQUEST
RRC CONNECTION RECONFIGURATION
S1AP PATH SWITH REQUEST ACKNOWLEDGE
X2AP UE CONTEXT RELEASE
....
STOP TRACE
Table 65: Session analysis results - Basic LTE X2 handover scenario - target cell
Parameter
Value
In Cause
5 - Inter eNB HO
Out Cause
according to the scenario
Failure cause
| Session analysis | 63
Parameter
Value
Failure Phase
X2 Establishment Cause
X2AP HANDOVER REQUEST
X2 Establishment Failure
X2 Release Cause
X2AP UE CONTEXT RELEASE
X2 Release Failure
S1 Establishment Cause
S1AP PATH SWITCH REQUEST
S1 Release Cause
S1AP UE CONTEXT RELEASE
Table 66: Bearer information
ID
Start time
Stop time
QCI
x
according to the scenario
S1AP UE CONTEXT
RELEASE COMMAND
x
--------------------------------------------------------------------------------------------------------------------------------LTE Inter eNB HO scenario
Figure 21: Inter eNB handover failure on source cell
LTE Inter eNB HO scenario - source cell
Table 67: Session analysis results - source cell
Parameter
Value
In Cause
according to the scenario
Out Cause
2 - Call ends
Failure cause
13 - eNB release
Failure Phase
10 - Source Inter eNB HO access
X2 Establishment Cause
| Session analysis | 64
Parameter
Value
X2 Establishment Failure
X2 Release Cause
X2AP HANDOVER REQUEST
X2 Release Failure
X2AP HANDOVER CANCEL
S1 Release Cause
S1APUEContextReleaseRequest '
cause' (tx2relocoverall-expiry)
---------------------------------------------------------------------------------------------------------------------------------------------------------------LTE Inter eNB HO scenario - failure in target cell
Figure 22: Inter eNB handover failure in target cell
Table 68: Session analysis results - failure in target cell
Parameter
Value
In Cause
5 - Inter eNB HO
Out Cause
2 - Call ends
Failure cause
14 - No UE Message
Failure Phase
13 - Target Inter HO setup
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
---------------------------------------------------------------------------------------------------------------------------------------------------------------Inter eNB handover failure in target cell ( no UE response with RRCconnectionReconfiguration)
In another scenation UE doesn't respond with RRCConnectionReconfgurationComplete where it was requested to set
all SRB/DRB/Measurements
| Session analysis | 65
Figure 23: Inter eNB handover failure in target cell ( no UE response with
RRCconnectionReconfiguration)
Table 69: Session analysis results -failure in target cell ( no UE response with
RRCConnectionReconfiguration)
Parameter
Value
In Cause
5 - Inter eNB HO
Out Cause
2 - Call ends
Failure cause
17 - No UE Reply
Failure Phase
13 - Target Inter HO setup
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
S1 Handover
Basic S1 Inter eNB handover scenario
Figure 24: S1 Inter eNB handover
| Session analysis | 66
S1 Handover - phases for Home eNB
| Session analysis | 67
Figure 25: S1 handover - source eNB phases
S1 Handover - phases for Target eNB
Figure 26: S1 Handover - target eNB phases
------------------------------------------------------------------------------------------------------------------------------------------------S1 Handover scenario analysis
Home eNB
Table 70: Session analysis results - call re-establishment in target eNB failure
Parameter
Value
In Cause
according to the scenario
Out Cause
7 - S1 HO
Failure cause
Failure Phase
S1 Establishment Cause
according to the scenario
| Session analysis | 68
Parameter
Value
S1 Establishment Failure
S1 Release Cause reason
S1AP UE CONTEXT RELEASE REQUEST
S1 Release Failure
Table 71: Bearer information
ID
Start time
Stop time
QCI
S1AP UE CONTEXT
RELEASE REQUEST
Target eNB
Table 72: Session analysis results - call re-establishment in target eNB failure
Parameter
Value
In Cause
7 - S1 HO
Out Cause
according to the scenario
Failure cause
Failure Phase
S1 Establishment Cause
S1AP HANDOVER REQUIRED
S1 Establishment Failure
S1 Release Cause reason
according to the scenario
S1 Release Failure
Table 73: Bearer information
ID
Start time
Stop time
RRC CONNECTION
RECONFIGURATION
COMPLETE
according to the scenario
QCI
-----------------------------------------------------------------------------------------------------------------------S1 Handover failure on home eNB
S1AP Release command was not received from MME. Home eNB release UE context due timer tS1relocoverallexpiry
| Session analysis | 69
Figure 27: S1 handover failure on home eNB
LTE Inter eNB HO scenario source cell
Table 74: Session analysis results - call re-establishment in target eNB failure
Parameter
Value
In Cause
according to the scenario
Out Cause
2 - Call ends
Failure cause
13 - eNB Release
Failure Phase
19 - Source S1 HO Access
S1 Establishment Cause
S1AP HANDOVER REQUIRED
S1 Establishment Failure
S1AP UE CONTEXT RELEASE REQUEST
S1 Release Cause reason
S1 Release Failure
S1AP UE CONTEXT RELEASE REQUEST
Table 75: Bearer information
ID
Start time
Stop time
QCI
----------------------------------------------------------------------------------------------------------S1 Handover failure on target eNB
I this scenario UE didn't send to target eNB RRCConnectionReconfiguration complete after was triggered to do so by
S1APHandoverCommand send to home eNB. Radio bearers were not established in target eNB
| Session analysis | 70
Table 76: Session analysis results - call re-establishment in target eNB failure
Parameter
Value
In Cause
according to the scenario
Out Cause
2 - Call ends
Failure cause
14 - No UE message
Failure Phase
20 - Target S1 HO Setup
S1 Establishment Cause
S1AP HANDOVER REQUEST
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
Table 77: Bearer information
ID
Start time
Stop time
QCI
I-RAT (Inter System Handover)
I-RAT handover means inter system handover e.g. to UTRAN. It's can be triggered due to e.g. poor LTE signal. eNB
include IE (handover type) in S1APHandoverRequest what type of handover is required
| Session analysis | 71
Figure 28: E-UTRAN to UTRAN Inter RAT handover [14]
--------------------------------------------------------------------------------------------------------------I-RAT Redirection
UE is redirected to other system. Scenario assumes that UE context is released by eNB -in fact it most of the cases it
is released by MME via S1AUEContextReleaseCommand.
| Session analysis | 72
Figure 29: I-RAT redirection
Table 78: Session analysis results - call re-establishment in target eNB failure
Parameter
Value
In Cause
according to the scenario
Out Cause
9 - I-RAT Redirect
Failure cause
Failure phase
S1 Release cause
S1APUeContextReleaseCommand 'cause' (network/
interrat-redirection)
-----------------------------------------------------------------------------------------------------------------------------------------PS/CS I-RAT Handover
CS RAT handover is reported when S1APHandoverCommand - SRVCC HO Indication
| Session analysis | 73
Figure 30: IRAT Handover phases
Table 79: Session analysis results - call re-establishment in target eNB failure
Parameter
Value
In Cause
according to the scenario
Out Cause
8 - I-RAT HO
Failure cause
Failure phase
Table 80: Bearer information
ID
Start time
Stop time
according to the scenario
S1AP UE CONTEXT
RELEASE COMMAND
QCI
CSFB - Circuit Switch Fallback
CSFB is the mechanism to move a subscriber from LTE to a legacy technology to obtain circuit switched voice
service. This function is only available if LTE coverage is overlapped by GSM, UMTS, or CDMA2000® 1xRTT
coverage. [16]
| Session analysis | 74
------------------------------------------------------------------------------------------------------------------------------------CS Fallback - call starts from idle
Figure 32: CS Fallback call phases - call started from idle
Figure 31: CSFB flow [15]
Table 81: Link Release Cause
Link
S1
X2
Status
Release reason
S1APUeContextReleaseCommand 'cause' radioNetwork : cs -fallback-triggered
| Session analysis | 75
Table 82: Session analysis in details
Message
Parameter
START TRACE
Session start time
RRC CONNECTION REQUEST
In cause: 1-New SRB;
RRC Establishment Reason
RRC CONNECTION SETUP
S-RAB: 1
RRC CONNECTION SETUP COMPLETE
S1AP INITIAL UE MESSAGE
S1 Establishment Cause
eNB UE S1AP ID
MMEC
TAI
S1AP INITIAL UE CONTEXT SETUP REQUEST
2 - New Call ; value CSFallbackIndicator : cs-fallbackrequired
MME UE S1 AP ID
S1AP INITIAL CONTEXT SETUP RESPONSE
S1AP UE CONTEXT RELEASE REQUEST
S1 Release Cause value Cause : radioNetwork : csfallback-triggered
S1AP UE CONTEXT RELEASE COMMAND
RRC CONNECTION RELEASE
RRC Release Reason releaseCause other,
S1AP UE CONTEXT RELEASE COMPLETE
Stop Trace
Session stop time
Out Cause: 3 - CS Fallback
Table 83: Session analysis results - basic LTE call
Parameter
Value
In Cause
2 - New Call
Out Cause
3 - CS Fallback
Failure cause
Failure Phase
1 - No Failure
S1 Establishment Cause
NAS S1AP INITIAL UE MESSAGE
S1 Establishment Failure
S1 Release Cause reason
S1 Release Failure
X2 Establishment Cause
X2 Establishment Failure
radioNetwork : cs-fallback-triggered
| Session analysis | 76
Parameter
Value
X2 Release Cause
X2 Release Failure
#S-RAB Bearer
1
#D-RAB Bearer
0
#E-RAB Bearer
1
QCI
8
Table 84: Bearer information
ID
Start time
Stop time
QCI
5
INITIAL CONTEXT
SETUP REQUEST
UE CONTEXT RELEASE 8
REQUEST
INITIAL UE MESSAGE
--------------------------------------------------------------------------------------------------------------------------------------------------------CS Fallback - procedure start during RRC/RAB active state
Figure 33: CS Fallback - procedure start during RRC/RAB active state
Table 85: Session analysis results - basic LTE call
Parameter
Value
In Cause
2- New Call
Out Cause
3 - CS Fallback
Failure cause
Failure Phase
1 - No Failure
S1 Establishment Cause
NAS S1AP INITIAL UE MESSAGE
S1 Establishment Failure
| Session analysis | 77
Parameter
Value
S1 Release Cause reason
S1APUeContextReleaseCommandt radioNetwork : csfallback-triggered
S1 Release Failure
X2 Establishment Cause
X2 Establishment Failure
X2 Release Cause
X2 Release Failure
#S-RAB Bearer
1
#D-RAB Bearer
2
#E-RAB Bearer
1
QCI
8
Table 86: Bearer information
RB In Cause
RB Out Cause
acoording to the scenario
3 - CS Fallback
RB Failure Cause
RB Failure Phase
1 - No Failure
Table 87: Link Release Cause
Link
Status
S1
Release reason
S1APUeContextReleaseCommand 'cause' radioNetwork : cs-fallback-triggered
X2
Additional ERAB
The "Training – Layer 3 Data Collector" [8] defines few scenarios which are interesting from Traffica pov.
From NetAct TraceViewer or RETINA we are interested in a situation when call drop occur after ERAB setup/
modification/delete.
| Session analysis | 78
Figure 34: Additional ERAB Setup phases
Table 88: Session analysis results - call re-establishment in target eNB failure
Parameter
Value
#S-RAB Bearer
2
#D-RAB Bearer
1 default + # of added DRB
#E-RAB Bearer
if DRB with QCI 1 available
QCI
5,8
Table 89: Bearer information
ID
Start time
Stop time
QCI
5
S1AP INITIAL UE
MESSAGE
S1AP UE CONTEXT
RELEASE COMMAND
5
6
S1AP ERAB REQUEST
S1AP RELEASE
RESPONSE
8
Drop can be seen if UE doesn't respond to RRCConnectionReconfiguration. With RRC Connection Reconfiguration
DRB are activated on UE/eNB link.
Figure 35: Additional ERAB setup failure - no UE Reply
| Session analysis | 79
Table 90: Session analysis results - call re-establishment in target eNB failure
Parameter
Value
In Cause
Out Cause
2 - Call end
Failure cause
17 - No UE Reply
Failure Phase
25 - Additional ERAB Access
#S-RAB Bearer
2
#D-RAB Bearer
1 default + # of added DRB
#E-RAB Bearer
QCI
(according to the scenario)
# Link Reestablishment
Table 91: Bearer information
ID
Start time
Stop time
QCI
5
S1AP INITIAL UE
MESSAGE
S1AP UE CONTEXT
RELEASE COMMAND
5
6
S1AP ERAB REQUEST
S1AP RELEASE
RESPONSE
8
| Session location map | 80
Session location map
System needs to provide location information for LTE session whenever it's possible. Position is provided for each
RRC Measurement Report. In case of failure last available position should be used. Each position is marked on a map
with additional information regarding measurements. After selecting a measurement on a map component User see
which cell is a serving one and neighbour. Additionally other components i.e. 'message flow', 'measurement graph'
must be synchronised.
System should use currently existing position algorithm and also LTE1308/LTE1501 capabilities where it will be
possible to get GPS position via Cell Trace Interface.
Whenever GPS position is available in RRCMeasurementReport position should be taken from message [10]. - tbc
Figure 36: LTE Session location map support 1
Figure 37: LTE Session location map support 2
| Measurement graph | 81
Measurement graph
Report is build base on RRCMeasurementReport. For every messages, parameters RSRP, RSRQ or physicallCellId
must be extracted. Serving and neighbor cell can be recognized base on tags: measResultServCell or
measResultPCell, physCellId.
Currently, RETINA project focus only on INTRA FREQ measurements. In next step analysis capabilities must be
extended to support also INTER RAT measurements.
Message example:
UL-DCCH-Message : {
message c1 : measurementReport : {
criticalExtensions c1 : measurementReport-r8 : {
measResults {
measId 9,
measResultPCell {
rsrpResult 29,
rsrqResult 16
},
measResultNeighCells measResultListEUTRA : {
{
physCellId 45,
measResult {
rsrpResult 29,
rsrqResult 16
}
},
{
physCellId 133,
measResult {
rsrpResult 16,
rsrqResult 2
}
}
}
}
}
}
}
Measurements must be presented on the graph with clear indication which measurement comes from serving cell and
which one from neighbor. Detailed information must be presented in text form or in form of tooltip after 'mouse over'
a measurement. Selected information should be presented:
•
•
•
cell ID
eNB ID
RSRP or RSRQ
Graph is synchronised with 'message flow' and 'map session'.
Information about neighbor cell can be read base on following picture
Figure 38: Neighbor relation
| Message flow | 82
Message flow
It’s is required to provide detailed information about LTE session. All messages according to LTE644 must be
decoded. It’s also an added value to provide decoded NAS information.
Message flow should be presented in text for and also on diagram. Each message type must be distinguished by color.
Fields
•
•
•
•
•
•
•
No – message number
Time stamp – according to [7]
CRNTI - according to [7] or refer to CRNTI (already available in session)
eNBUE S1APID - according to [7] or refer to eNB UE S1AP ID (already available in session)
Message type - according to [7]
L3 Message - according to [7]
Link Direction - according to [7]
NAS – parsed NAS message
NOTE:
•
NAS meassge will not be decoded in first implementaion version
Figure 39: Diagram example
| Appendix A - In Cause | 83
Appendix A - In Cause
Table 92:
Value
Scenario
Explanation
1
New SRB
Only SRB is created
SRB is created during RRC Connection Establisment procedure.
2
New Call
DRB is created due to a new call (includes also creation of SRB)
3
Re-establishement
SRB and DRB resources are setup via re-establishement
DL-CCCH-Message : {
message c1 : rrcConnectionReestablishment : {
rrc-TransactionIdentifier 0,
criticalExtensions c1 :
rrcConnectionReestablishment-r8 : {
radioResourceConfigDedicated {
srb-ToAddModList {
{
srb-Identity 1
},
{
srb-Identity 2
}
},
drb-ToAddModList {
{
drb-Identity 10
}
}
},
nextHopChainingCount 0
}
}
}
4
empty
empty
5
Inter eNB HO
SRB and DRB resources are handed from another LTE eNB
6
Intra eNB HO
SRB and DRB resources are handed from inside eNB (another cell)
7
S1 HO
SRB and DRB resources are handed from another LTE eNB via MME
8
I-RAT HO
SRB and DRB resources are handed from another RAT technology
9
I-RAT Redirect
| Appendix B - Out Cause | 84
Appendix B - Out Cause
Table 93:
Value
Scenario
Explanation
1
SRB Released
Only SRB has been created and it is released without HO procedure
RRCConnectionReconfigurationMessage not available
2
Call Ends
SRB and DRB are released via UeContextReleaseCommand (call normally
terminated or failed)
SRB and DRB was configured correctly during a call using RRCEstablisment
procedure and RRCReconfigurationProcedure. Additionally
S1APInitialUUContectSetupResponse is available.
3
CS Fallback
SRB and DRB are redirected to another RAT technology CS service
4
empty
empty
5
Inter eNB HO
SRB and DRB resources are handed over to another LTE eNB
6
Intra eNB HO
SRB and DRB resources are handed over inside eNB
7
S1 HO
SRB and DRB resources are handed over to another LTE eNB via MME
8
I-RAT HO
SRB and DRB resources are handed over to another RAT technology
9
Idle I-RAT HO
SRB and DRB are redirected to another RAT technology PS service
10
Re-est Reject
eNB has rejected UE's Re-establishment request
RRCConnectionReestablishmentReject message
11
Radiolink Failure
eNB releases resources beacause of L1/L2 Radiolink Failure
MACRadioLinkFailure message appeared
12
EPC Release
MME releases resources because it has detected an error or UE has apperead in
another cell
S1APUEContextReleaseCommand
13
eNB Release
eNB releases resources because it has detected an error
S1APUEContextReleaseRequest
14
No UE Messages
SRB or DRB released because not a single L3 message is received from UE
15
No EPC Messages
SRB or DRB released because not a single L3 message is received from MME
16
RAB Setup Failure
E-RAB setup is rejected via InitialContextSetupFailure and failure is not
defined by any other fail causes
17
No UE Reply
UE is not replying to RandomAccess or RRC message from eNB to which is
expected a reply
This can happen when e.g. no reponse on RRCConnectionSetup or
RRCConnectionReconfigurationRequest is visible
| Appendix B - Out Cause | 85
Value
Scenario
Explanation
18
No EPC Reply
MME is not replying to RandomAccess or RRC message from eNB to which is
expected a reply
19
No eNB Resources
SRB or DRB connection is rejected because eNB is lacking resources and
failure is not defined by any other fail causes
20
RRC Reject
RRC connection is rejected via RrcConnectionReject message
21
X2 HO Reject
X2 Handover request is rejected via HandoverPreparationFailure message
22
S1 HO Reject
S1 Handover request is rejected via HandoverFailure message
| Appendix C - S1AP Release Failure Cause | 86
Appendix C - S1AP Release Failure Cause
Value
L3 message
Category
Cause
0
ErrorIndication
radioNetwork
unspecified
1
ErrorIndication
radioNetwork
tx2relocoverall-expiry
2
ErrorIndication
radioNetwork
successful-handover
3
ErrorIndication
radioNetwork
release-due-to-eutran-generated-reason
4
ErrorIndication
radioNetwork
handover-cancelled
5
ErrorIndication
radioNetwork
partial-handover
6
ErrorIndication
radioNetwork
ho-failure-in-target-EPC-eNB-or-target-system
7
ErrorIndication
radioNetwork
ho-target-not-allowed
8
ErrorIndication
radioNetwork
tS1relocoverall-expiry
9
ErrorIndication
radioNetwork
tS1relocprep-expiry
10
ErrorIndication
radioNetwork
cell-not-available
11
ErrorIndication
radioNetwork
unknown-targetID
12
ErrorIndication
radioNetwork
no-radio-resources-available-in-target-cell
13
ErrorIndication
radioNetwork
unknown-mme-ue-s1ap-id
14
ErrorIndication
radioNetwork
unknown-enb-ue-s1ap-id
15
ErrorIndication
radioNetwork
unknown-pair-ue-s1ap-id
16
ErrorIndication
radioNetwork
handover-desirable-for-radio-reason
17
ErrorIndication
radioNetwork
time-critical-handover
18
ErrorIndication
radioNetwork
resource-optimisation-handover
19
ErrorIndication
radioNetwork
reduce-load-in-serving-cell
20
ErrorIndication
radioNetwork
user-inactivity
21
ErrorIndication
radioNetwork
radio-connection-with-ue-lost
22
ErrorIndication
radioNetwork
load-balancing-tau-required
23
ErrorIndication
radioNetwork
cs-fallback-triggered
24
ErrorIndication
radioNetwork
ue-not-available-for-ps-service
25
ErrorIndication
radioNetwork
radio-resources-not-available
26
ErrorIndication
radioNetwork
failure-in-radio-interface-procedure
27
ErrorIndication
radioNetwork
invalid-qos-combination
28
ErrorIndication
radioNetwork
interrat-redirection
29
ErrorIndication
radioNetwork
interaction-with-other-procedure
30
ErrorIndication
radioNetwork
multiple-E-RAB-ID-instances
| Appendix C - S1AP Release Failure Cause | 87
31
ErrorIndication
radioNetwork
unknown-E-RAB-ID
32
ErrorIndication
radioNetwork
encryption-and-or-integrity-protectionalgorithms-not-supported
33
ErrorIndication
radioNetwork
redirection-towards-1xRTT
34
ErrorIndication
radioNetwork
s1-intra-system-handover-triggered
35
ErrorIndication
radioNetwork
s1-inter-system-handover-triggered
36
ErrorIndication
radioNetwork
x2-handover-triggered
37
ErrorIndication
radioNetwork
...
256
ErrorIndication
transport
transport-resource-unavailable
257
ErrorIndication
transport
unspecified
258
ErrorIndication
transport
...
512
ErrorIndication
nas
normal-release
513
ErrorIndication
nas
authentication-failure
514
ErrorIndication
nas
detach
515
ErrorIndication
nas
unspecified
516
ErrorIndication
nas
...
768
ErrorIndication
protocol
transfer-syntax-error
769
ErrorIndication
protocol
abstract-syntax-error-reject
770
ErrorIndication
protocol
abstract-syntax-error-ignore-and-notify
771
ErrorIndication
protocol
message-not-compatible-with-receiver-state
772
ErrorIndication
protocol
semantic-error
773
ErrorIndication
protocol
abstract-syntax-error-falsely-constructedmessage
774
ErrorIndication
protocol
unspecified
775
ErrorIndication
protocol
...
1024
ErrorIndication
misc
control-processing-overload
1025
ErrorIndication
misc
not-enough-user-plane-processing-resources
1026
ErrorIndication
misc
hardware-failure
1027
ErrorIndication
misc
om-intervention
1028
ErrorIndication
misc
unspecified
1029
ErrorIndication
misc
unknown-PLMN
1030
ErrorIndication
misc
...
4096
HandoverFailure
radioNetwork
unspecified
4097
HandoverFailure
radioNetwork
tx2relocoverall-expiry
4098
HandoverFailure
radioNetwork
successful-handover
4099
HandoverFailure
radioNetwork
release-due-to-eutran-generated-reason
| Appendix C - S1AP Release Failure Cause | 88
4100
HandoverFailure
radioNetwork
handover-cancelled
4101
HandoverFailure
radioNetwork
partial-handover
4102
HandoverFailure
radioNetwork
ho-failure-in-target-EPC-eNB-or-target-system
4103
HandoverFailure
radioNetwork
ho-target-not-allowed
4104
HandoverFailure
radioNetwork
tS1relocoverall-expiry
4105
HandoverFailure
radioNetwork
tS1relocprep-expiry
4106
HandoverFailure
radioNetwork
cell-not-available
4107
HandoverFailure
radioNetwork
unknown-targetID
4108
HandoverFailure
radioNetwork
no-radio-resources-available-in-target-cell
4109
HandoverFailure
radioNetwork
unknown-mme-ue-s1ap-id
4110
HandoverFailure
radioNetwork
unknown-enb-ue-s1ap-id
4111
HandoverFailure
radioNetwork
unknown-pair-ue-s1ap-id
4112
HandoverFailure
radioNetwork
handover-desirable-for-radio-reason
4113
HandoverFailure
radioNetwork
time-critical-handover
4114
HandoverFailure
radioNetwork
resource-optimisation-handover
4115
HandoverFailure
radioNetwork
reduce-load-in-serving-cell
4116
HandoverFailure
radioNetwork
user-inactivity
4117
HandoverFailure
radioNetwork
radio-connection-with-ue-lost
4118
HandoverFailure
radioNetwork
load-balancing-tau-required
4119
HandoverFailure
radioNetwork
cs-fallback-triggered
4120
HandoverFailure
radioNetwork
ue-not-available-for-ps-service
4121
HandoverFailure
radioNetwork
radio-resources-not-available
4122
HandoverFailure
radioNetwork
failure-in-radio-interface-procedure
4123
HandoverFailure
radioNetwork
invalid-qos-combination
4124
HandoverFailure
radioNetwork
interrat-redirection
4125
HandoverFailure
radioNetwork
interaction-with-other-procedure
4126
HandoverFailure
radioNetwork
multiple-E-RAB-ID-instances
4127
HandoverFailure
radioNetwork
unknown-E-RAB-ID
4128
HandoverFailure
radioNetwork
encryption-and-or-integrity-protectionalgorithms-not-supported
4129
HandoverFailure
radioNetwork
redirection-towards-1xRTT
4130
HandoverFailure
radioNetwork
s1-intra-system-handover-triggered
4131
HandoverFailure
radioNetwork
s1-inter-system-handover-triggered
4132
HandoverFailure
radioNetwork
x2-handover-triggered
4133
HandoverFailure
radioNetwork
...
4352
HandoverFailure
transport
transport-resource-unavailable
| Appendix C - S1AP Release Failure Cause | 89
4353
HandoverFailure
transport
unspecified
4354
HandoverFailure
transport
...
4608
HandoverFailure
nas
normal-release
4609
HandoverFailure
nas
authentication-failure
4610
HandoverFailure
nas
detach
4611
HandoverFailure
nas
unspecified
4612
HandoverFailure
nas
...
4864
HandoverFailure
protocol
transfer-syntax-error
4865
HandoverFailure
protocol
abstract-syntax-error-reject
4866
HandoverFailure
protocol
abstract-syntax-error-ignore-and-notify
4867
HandoverFailure
protocol
message-not-compatible-with-receiver-state
4868
HandoverFailure
protocol
semantic-error
4869
HandoverFailure
protocol
abstract-syntax-error-falsely-constructedmessage
4870
HandoverFailure
protocol
unspecified
4871
HandoverFailure
protocol
...
5120
HandoverFailure
misc
control-processing-overload
5121
HandoverFailure
misc
not-enough-user-plane-processing-resources
5122
HandoverFailure
misc
hardware-failure
5123
HandoverFailure
misc
om-intervention
5124
HandoverFailure
misc
unspecified
5125
HandoverFailure
misc
unknown-PLMN
5126
HandoverFailure
misc
...
| Appendix D - S1 Establishment Failure Cause | 90
Appendix D - S1 Establishment Failure Cause
Value
L3 message
Category
Cause
0
InitialContextSetupFailure
radioNetwork
unspecified
1
InitialContextSetupFailure
radioNetwork
tx2relocoverall-expiry
2
InitialContextSetupFailure
radioNetwork
successful-handover
3
InitialContextSetupFailure
radioNetwork
release-due-to-eutran-generated-reason
4
InitialContextSetupFailure
radioNetwork
handover-cancelled
5
InitialContextSetupFailure
radioNetwork
partial-handover
6
InitialContextSetupFailure
radioNetwork
ho-failure-in-target-EPC-eNB-or-target-system
7
InitialContextSetupFailure
radioNetwork
ho-target-not-allowed
8
InitialContextSetupFailure
radioNetwork
tS1relocoverall-expiry
9
InitialContextSetupFailure
radioNetwork
tS1relocprep-expiry
10
InitialContextSetupFailure
radioNetwork
cell-not-available
11
InitialContextSetupFailure
radioNetwork
unknown-targetID
12
InitialContextSetupFailure
radioNetwork
no-radio-resources-available-in-target-cell
13
InitialContextSetupFailure
radioNetwork
unknown-mme-ue-s1ap-id
14
InitialContextSetupFailure
radioNetwork
unknown-enb-ue-s1ap-id
15
InitialContextSetupFailure
radioNetwork
unknown-pair-ue-s1ap-id
16
InitialContextSetupFailure
radioNetwork
handover-desirable-for-radio-reason
17
InitialContextSetupFailure
radioNetwork
time-critical-handover
18
InitialContextSetupFailure
radioNetwork
resource-optimisation-handover
19
InitialContextSetupFailure
radioNetwork
reduce-load-in-serving-cell
20
InitialContextSetupFailure
radioNetwork
user-inactivity
21
InitialContextSetupFailure
radioNetwork
radio-connection-with-ue-lost
22
InitialContextSetupFailure
radioNetwork
load-balancing-tau-required
23
InitialContextSetupFailure
radioNetwork
cs-fallback-triggered
24
InitialContextSetupFailure
radioNetwork
ue-not-available-for-ps-service
25
InitialContextSetupFailure
radioNetwork
radio-resources-not-available
26
InitialContextSetupFailure
radioNetwork
failure-in-radio-interface-procedure
27
InitialContextSetupFailure
radioNetwork
invalid-qos-combination
28
InitialContextSetupFailure
radioNetwork
interrat-redirection
29
InitialContextSetupFailure
radioNetwork
interaction-with-other-procedure
30
InitialContextSetupFailure
radioNetwork
multiple-E-RAB-ID-instances
| Appendix D - S1 Establishment Failure Cause | 91
31
InitialContextSetupFailure
radioNetwork
unknown-E-RAB-ID
32
InitialContextSetupFailure
radioNetwork
encryption-and-or-integrity-protectionalgorithms-not-supported
33
InitialContextSetupFailure
radioNetwork
redirection-towards-1xRTT
34
InitialContextSetupFailure
radioNetwork
s1-intra-system-handover-triggered
35
InitialContextSetupFailure
radioNetwork
s1-inter-system-handover-triggered
36
InitialContextSetupFailure
radioNetwork
x2-handover-triggered
37
InitialContextSetupFailure
radioNetwork
...
256
InitialContextSetupFailure
transport
transport-resource-unavailable
257
InitialContextSetupFailure
transport
unspecified
258
InitialContextSetupFailure
transport
...
512
InitialContextSetupFailure
nas
normal-release
513
InitialContextSetupFailure
nas
authentication-failure
514
InitialContextSetupFailure
nas
detach
515
InitialContextSetupFailure
nas
unspecified
516
InitialContextSetupFailure
nas
...
768
InitialContextSetupFailure
protocol
transfer-syntax-error
769
InitialContextSetupFailure
protocol
abstract-syntax-error-reject
770
InitialContextSetupFailure
protocol
abstract-syntax-error-ignore-and-notify
771
InitialContextSetupFailure
protocol
message-not-compatible-with-receiver-state
772
InitialContextSetupFailure
protocol
semantic-error
773
InitialContextSetupFailure
protocol
abstract-syntax-error-falsely-constructedmessage
774
InitialContextSetupFailure
protocol
unspecified
775
InitialContextSetupFailure
protocol
...
1024
InitialContextSetupFailure
misc
control-processing-overload
1025
InitialContextSetupFailure
misc
not-enough-user-plane-processing-resources
1026
InitialContextSetupFailure
misc
hardware-failure
1027
InitialContextSetupFailure
misc
om-intervention
1028
InitialContextSetupFailure
misc
unspecified
1029
InitialContextSetupFailure
misc
unknown-PLMN
1030
InitialContextSetupFailure
misc
...
4096
PathSwitchRequestFailure
radioNetwork
unspecified
4097
PathSwitchRequestFailure
radioNetwork
tx2relocoverall-expiry
4098
PathSwitchRequestFailure
radioNetwork
successful-handover
4099
PathSwitchRequestFailure
radioNetwork
release-due-to-eutran-generated-reason
| Appendix D - S1 Establishment Failure Cause | 92
4100
PathSwitchRequestFailure
radioNetwork
handover-cancelled
4101
PathSwitchRequestFailure
radioNetwork
partial-handover
4102
PathSwitchRequestFailure
radioNetwork
ho-failure-in-target-EPC-eNB-or-target-system
4103
PathSwitchRequestFailure
radioNetwork
ho-target-not-allowed
4104
PathSwitchRequestFailure
radioNetwork
tS1relocoverall-expiry
4105
PathSwitchRequestFailure
radioNetwork
tS1relocprep-expiry
4106
PathSwitchRequestFailure
radioNetwork
cell-not-available
4107
PathSwitchRequestFailure
radioNetwork
unknown-targetID
4108
PathSwitchRequestFailure
radioNetwork
no-radio-resources-available-in-target-cell
4109
PathSwitchRequestFailure
radioNetwork
unknown-mme-ue-s1ap-id
4110
PathSwitchRequestFailure
radioNetwork
unknown-enb-ue-s1ap-id
4111
PathSwitchRequestFailure
radioNetwork
unknown-pair-ue-s1ap-id
4112
PathSwitchRequestFailure
radioNetwork
handover-desirable-for-radio-reason
4113
PathSwitchRequestFailure
radioNetwork
time-critical-handover
4114
PathSwitchRequestFailure
radioNetwork
resource-optimisation-handover
4115
PathSwitchRequestFailure
radioNetwork
reduce-load-in-serving-cell
4116
PathSwitchRequestFailure
radioNetwork
user-inactivity
4117
PathSwitchRequestFailure
radioNetwork
radio-connection-with-ue-lost
4118
PathSwitchRequestFailure
radioNetwork
load-balancing-tau-required
4119
PathSwitchRequestFailure
radioNetwork
cs-fallback-triggered
4120
PathSwitchRequestFailure
radioNetwork
ue-not-available-for-ps-service
4121
PathSwitchRequestFailure
radioNetwork
radio-resources-not-available
4122
PathSwitchRequestFailure
radioNetwork
failure-in-radio-interface-procedure
4123
PathSwitchRequestFailure
radioNetwork
invalid-qos-combination
4124
PathSwitchRequestFailure
radioNetwork
interrat-redirection
4125
PathSwitchRequestFailure
radioNetwork
interaction-with-other-procedure
4126
PathSwitchRequestFailure
radioNetwork
multiple-E-RAB-ID-instances
4127
PathSwitchRequestFailure
radioNetwork
unknown-E-RAB-ID
4128
PathSwitchRequestFailure
radioNetwork
encryption-and-or-integrity-protectionalgorithms-not-supported
4129
PathSwitchRequestFailure
radioNetwork
redirection-towards-1xRTT
4130
PathSwitchRequestFailure
radioNetwork
s1-intra-system-handover-triggered
4131
PathSwitchRequestFailure
radioNetwork
s1-inter-system-handover-triggered
4132
PathSwitchRequestFailure
radioNetwork
x2-handover-triggered
4133
PathSwitchRequestFailure
radioNetwork
...
4352
PathSwitchRequestFailure
transport
transport-resource-unavailable
| Appendix D - S1 Establishment Failure Cause | 93
.
4353
PathSwitchRequestFailure
transport
unspecified
4354
PathSwitchRequestFailure
transport
...
4608
PathSwitchRequestFailure
nas
normal-release
4609
PathSwitchRequestFailure
nas
authentication-failure
4610
PathSwitchRequestFailure
nas
detach
4611
PathSwitchRequestFailure
nas
unspecified
4612
PathSwitchRequestFailure
nas
...
4864
PathSwitchRequestFailure
protocol
transfer-syntax-error
4865
PathSwitchRequestFailure
protocol
abstract-syntax-error-reject
4866
PathSwitchRequestFailure
protocol
abstract-syntax-error-ignore-and-notify
4867
PathSwitchRequestFailure
protocol
message-not-compatible-with-receiver-state
4868
PathSwitchRequestFailure
protocol
semantic-error
4869
PathSwitchRequestFailure
protocol
abstract-syntax-error-falsely-constructedmessage
4870
PathSwitchRequestFailure
protocol
unspecified
4871
PathSwitchRequestFailure
protocol
...
5120
PathSwitchRequestFailure
misc
control-processing-overload
5121
PathSwitchRequestFailure
misc
not-enough-user-plane-processing-resources
5122
PathSwitchRequestFailure
misc
hardware-failure
5123
PathSwitchRequestFailure
misc
om-intervention
5124
PathSwitchRequestFailure
misc
unspecified
5125
PathSwitchRequestFailure
misc
unknown-PLMN
5126
PathSwitchRequestFailure
misc
...
| Appendix E - S1 Release Cause | 94
Appendix E - S1 Release Cause
Value
L3 message
Category
Cause
0
UEContextReleaseCommandradioNetwork
unspecified
1
UEContextReleaseCommandradioNetwork
tx2relocoverall-expiry
2
UEContextReleaseCommandradioNetwork
successful-handover
3
UEContextReleaseCommandradioNetwork
release-due-to-eutran-generated-reason
4
UEContextReleaseCommandradioNetwork
handover-cancelled
5
UEContextReleaseCommandradioNetwork
partial-handover
6
UEContextReleaseCommandradioNetwork
ho-failure-in-target-EPC-eNB-or-target-system
7
UEContextReleaseCommandradioNetwork
ho-target-not-allowed
8
UEContextReleaseCommandradioNetwork
tS1relocoverall-expiry
9
UEContextReleaseCommandradioNetwork
tS1relocprep-expiry
10
UEContextReleaseCommandradioNetwork
cell-not-available
11
UEContextReleaseCommandradioNetwork
unknown-targetID
12
UEContextReleaseCommandradioNetwork
no-radio-resources-available-in-target-cell
13
UEContextReleaseCommandradioNetwork
unknown-mme-ue-s1ap-id
14
UEContextReleaseCommandradioNetwork
unknown-enb-ue-s1ap-id
15
UEContextReleaseCommandradioNetwork
unknown-pair-ue-s1ap-id
16
UEContextReleaseCommandradioNetwork
handover-desirable-for-radio-reason
17
UEContextReleaseCommandradioNetwork
time-critical-handover
18
UEContextReleaseCommandradioNetwork
resource-optimisation-handover
19
UEContextReleaseCommandradioNetwork
reduce-load-in-serving-cell
20
UEContextReleaseCommandradioNetwork
user-inactivity
21
UEContextReleaseCommandradioNetwork
radio-connection-with-ue-lost
22
UEContextReleaseCommandradioNetwork
load-balancing-tau-required
23
UEContextReleaseCommandradioNetwork
cs-fallback-triggered
24
UEContextReleaseCommandradioNetwork
ue-not-available-for-ps-service
25
UEContextReleaseCommandradioNetwork
radio-resources-not-available
26
UEContextReleaseCommandradioNetwork
failure-in-radio-interface-procedure
27
UEContextReleaseCommandradioNetwork
invalid-qos-combination
28
UEContextReleaseCommandradioNetwork
interrat-redirection
29
UEContextReleaseCommandradioNetwork
interaction-with-other-procedure
30
UEContextReleaseCommandradioNetwork
multiple-E-RAB-ID-instances
| Appendix E - S1 Release Cause | 95
31
UEContextReleaseCommandradioNetwork
unknown-E-RAB-ID
32
UEContextReleaseCommandradioNetwork
encryption-and-or-integrity-protectionalgorithms-not-supported
33
UEContextReleaseCommandradioNetwork
redirection-towards-1xRTT
34
UEContextReleaseCommandradioNetwork
s1-intra-system-handover-triggered
35
UEContextReleaseCommandradioNetwork
s1-inter-system-handover-triggered
36
UEContextReleaseCommandradioNetwork
x2-handover-triggered
37
UEContextReleaseCommandradioNetwork
...
256
UEContextReleaseCommandtransport
transport-resource-unavailable
257
UEContextReleaseCommandtransport
unspecified
258
UEContextReleaseCommandtransport
...
512
UEContextReleaseCommandnas
normal-release
513
UEContextReleaseCommandnas
authentication-failure
514
UEContextReleaseCommandnas
detach
515
UEContextReleaseCommandnas
unspecified
516
UEContextReleaseCommandnas
...
768
UEContextReleaseCommandprotocol
transfer-syntax-error
769
UEContextReleaseCommandprotocol
abstract-syntax-error-reject
770
UEContextReleaseCommandprotocol
abstract-syntax-error-ignore-and-notify
771
UEContextReleaseCommandprotocol
message-not-compatible-with-receiver-state
772
UEContextReleaseCommandprotocol
semantic-error
773
UEContextReleaseCommandprotocol
abstract-syntax-error-falsely-constructedmessage
774
UEContextReleaseCommandprotocol
unspecified
775
UEContextReleaseCommandprotocol
...
1024
UEContextReleaseCommandmisc
control-processing-overload
1025
UEContextReleaseCommandmisc
not-enough-user-plane-processing-resources
1026
UEContextReleaseCommandmisc
hardware-failure
1027
UEContextReleaseCommandmisc
om-intervention
1028
UEContextReleaseCommandmisc
unspecified
1029
UEContextReleaseCommandmisc
unknown-PLMN
1030
UEContextReleaseCommandmisc
...
4096
UEContextReleaseRequest
radioNetwork
unspecified
4097
UEContextReleaseRequest
radioNetwork
tx2relocoverall-expiry
4098
UEContextReleaseRequest
radioNetwork
successful-handover
4099
UEContextReleaseRequest
radioNetwork
release-due-to-eutran-generated-reason
| Appendix E - S1 Release Cause | 96
4100
UEContextReleaseRequest
radioNetwork
handover-cancelled
4101
UEContextReleaseRequest
radioNetwork
partial-handover
4102
UEContextReleaseRequest
radioNetwork
ho-failure-in-target-EPC-eNB-or-target-system
4103
UEContextReleaseRequest
radioNetwork
ho-target-not-allowed
4104
UEContextReleaseRequest
radioNetwork
tS1relocoverall-expiry
4105
UEContextReleaseRequest
radioNetwork
tS1relocprep-expiry
4106
UEContextReleaseRequest
radioNetwork
cell-not-available
4107
UEContextReleaseRequest
radioNetwork
unknown-targetID
4108
UEContextReleaseRequest
radioNetwork
no-radio-resources-available-in-target-cell
4109
UEContextReleaseRequest
radioNetwork
unknown-mme-ue-s1ap-id
4110
UEContextReleaseRequest
radioNetwork
unknown-enb-ue-s1ap-id
4111
UEContextReleaseRequest
radioNetwork
unknown-pair-ue-s1ap-id
4112
UEContextReleaseRequest
radioNetwork
handover-desirable-for-radio-reason
4113
UEContextReleaseRequest
radioNetwork
time-critical-handover
4114
UEContextReleaseRequest
radioNetwork
resource-optimisation-handover
4115
UEContextReleaseRequest
radioNetwork
reduce-load-in-serving-cell
4116
UEContextReleaseRequest
radioNetwork
user-inactivity
4117
UEContextReleaseRequest
radioNetwork
radio-connection-with-ue-lost
4118
UEContextReleaseRequest
radioNetwork
load-balancing-tau-required
4119
UEContextReleaseRequest
radioNetwork
cs-fallback-triggered
4120
UEContextReleaseRequest
radioNetwork
ue-not-available-for-ps-service
4121
UEContextReleaseRequest
radioNetwork
radio-resources-not-available
4122
UEContextReleaseRequest
radioNetwork
failure-in-radio-interface-procedure
4123
UEContextReleaseRequest
radioNetwork
invalid-qos-combination
4124
UEContextReleaseRequest
radioNetwork
interrat-redirection
4125
UEContextReleaseRequest
radioNetwork
interaction-with-other-procedure
4126
UEContextReleaseRequest
radioNetwork
multiple-E-RAB-ID-instances
4127
UEContextReleaseRequest
radioNetwork
unknown-E-RAB-ID
4128
UEContextReleaseRequest
radioNetwork
encryption-and-or-integrity-protectionalgorithms-not-supported
4129
UEContextReleaseRequest
radioNetwork
redirection-towards-1xRTT
4130
UEContextReleaseRequest
radioNetwork
s1-intra-system-handover-triggered
4131
UEContextReleaseRequest
radioNetwork
s1-inter-system-handover-triggered
4132
UEContextReleaseRequest
radioNetwork
x2-handover-triggered
4133
UEContextReleaseRequest
radioNetwork
...
4352
UEContextReleaseRequest
transport
transport-resource-unavailable
| Appendix E - S1 Release Cause | 97
4353
UEContextReleaseRequest
transport
unspecified
4354
UEContextReleaseRequest
transport
...
4608
UEContextReleaseRequest
nas
normal-release
4609
UEContextReleaseRequest
nas
authentication-failure
4610
UEContextReleaseRequest
nas
detach
4611
UEContextReleaseRequest
nas
unspecified
4612
UEContextReleaseRequest
nas
...
4864
UEContextReleaseRequest
protocol
transfer-syntax-error
4865
UEContextReleaseRequest
protocol
abstract-syntax-error-reject
4866
UEContextReleaseRequest
protocol
abstract-syntax-error-ignore-and-notify
4867
UEContextReleaseRequest
protocol
message-not-compatible-with-receiver-state
4868
UEContextReleaseRequest
protocol
semantic-error
4869
UEContextReleaseRequest
protocol
abstract-syntax-error-falsely-constructedmessage
4870
UEContextReleaseRequest
protocol
unspecified
4871
UEContextReleaseRequest
protocol
...
5120
UEContextReleaseRequest
misc
control-processing-overload
5121
UEContextReleaseRequest
misc
not-enough-user-plane-processing-resources
5122
UEContextReleaseRequest
misc
hardware-failure
5123
UEContextReleaseRequest
misc
om-intervention
5124
UEContextReleaseRequest
misc
unspecified
5125
UEContextReleaseRequest
misc
unknown-PLMN
5126
UEContextReleaseRequest
misc
...
| Appendix F - Fault phase | 98
Appendix F - Fault phase
Value
Message content
1
No Failures
2
RRC Setup
3
RRC Access
4
RAB Setup
5
RAB Access
6
RAB Active
7
Source Intra HO Setup
8
Source Intra HO Access
9
Source Inter HO Setup
10
Source Inter HO Access
11
Target Intra HO Setup
12
Target Intra HO Access
13
Target Inter HO Setup
14
Target Inter HO Access
15
Target HO Setup
16
Re-Est Setup
17
RRC Active
18
Source S1 HO Setup
19
Source S1 HO Access
20
Target S1 HO Setup
21
Target S1 HO Access
22
I-RAT Redirect Setup
23
I-RAT Redirect Access
| Appendix G - RRC Establishment Cause | 99
Appendix G - RRC Establishment Cause
•
RRCConnectionRequest
Value
Cause
1
Emergency
2
HighPriorityAccess
3
mt-Access
4
mo-Signalling
5
mo-Data
6
spare3
7
spare2
8
spare1
•
RRCRe-establishmentRequest
9
reestablishmentCause otherFailure
10
reestablishmentCause handoverFailure
11
reestablishmentCause reconfigurationFailure
| Backup | 100
Backup
•
RRCConnectionRequest
Value
Cause
1
Emergency
2
HighPriorityAccess
3
mt-Access
4
mo-Signalling
5
mo-Data
6
spare3
7
spare2
8
spare1
•
RRCRe-establishmentRequest
9
reestablishmentCause otherFailure
10
reestablishmentCause handoverFailure
11
reestablishmentCause reconfigurationFailure