Call Drop Analysis

RA47057EN60GLA0 1
Call Drop Analysis

RA47057EN60GLA0 2
Call Drop Analysis

RA47057EN60GLA0 4
Call Drop Analysis

RA47057EN60GLA0 5
Call Drop Analysis

RA47057EN60GLA0 6
Call Drop Analysis

RA47057EN60GLA0 7
Call Drop Analysis

RA47057EN60GLA0 8
Call Drop Analysis

3GPP TS 32.451: Since the keep-alive possibilities of E-RABs, i.e. DRX

are available, it is probable that E-RABs are kept alive much longer
than they are used for transmitting data. With an extreme setting of this
keep-alive functionality it can lead to that basically all E-RAB releases
are doomed to be abnormal (the normal system releases do not exist if
keep-alive is set very long).
Hence the definition is to only count it as abnormal releases when there
was actually an impact on the end-user.
The preferred normalization of abnormal releases of the service shall be
time unit of transfer between abnormal releases, i.e. abnormal releases
per served session time.

RA47057EN60GLA0 9
Call Drop Analysis

RA47057EN60GLA0 10
Call Drop Analysis

RA47057EN60GLA0 11
Call Drop Analysis

RA47057EN60GLA0 12
Call Drop Analysis

RA47057EN60GLA0 13
Call Drop Analysis

RA47057EN60GLA0 14
Call Drop Analysis

RA47057EN60GLA0 15
Call Drop Analysis

RA47057EN60GLA0 16
Call Drop Analysis

RA47057EN60GLA0 17
Call Drop Analysis

RA47057EN60GLA0 18
Call Drop Analysis

Timer T301 supervises the RRC connection

reestablishment procedure
Start: Transmission of
RRCConnectionReestabilshmentRequest
Stop: Reception of
RRCConnectionReestablishment or
RRCConnectionReestablishmentReject message
as well as when the selected cell becomes
unsuitable
At expiry: Go to RRC_IDLE
Def. 200ms

RA47057EN60GLA0 19
Call Drop Analysis

Short-MAC-I calculated from:

cellIdentity Set to CellIdentity of the current cell
physCellId Set to the physical cell identity of the cell the UE was
connected to prior to the failure.
c-RNTI Set to C-RNTI that the UE had in the cell it was
connected to prior to the failure.

RA47057EN60GLA0 20
Call Drop Analysis

RA47057EN60GLA0 21
Call Drop Analysis

RA47057EN60GLA0 22
Call Drop Analysis

RA47057EN60GLA0 23
Call Drop Analysis

RA47057EN60GLA0 24
Call Drop Analysis

TAU = Tracking Area Update

RA47057EN60GLA0 25
Call Drop Analysis

Source: 3GPP TS 36.331, TS 36.300

Detection of physical layer problems in RRC_CONNECTED

The UE shall, upon receiving N310 consecutive "out-of-sync" indications from lower layers
while neither T300, T301, T304 nor T311 is running, start timer T310

Recovery of physical layer problems

Upon receiving N311 consecutive "in-sync" indications from lower layers while T310 is running,
the UE shall stop timer T310;
NOTE 1: In this case, the UE resumes the RRC connection without explicit Signaling, i.e. the
UE resumes the entire radio resource configuration.
NOTE 2: Periods in time where neither "in-sync" nor "out-of-sync" is reported by layer 1 do not
affect the evaluation of the number of consecutive "in-sync" or "out-of-sync" indications.

Radio link failure is triggered by

Upon T310 expiry
upon random access problem indication from MAC while neither T300, T301, T304 nor T311 is
running
upon indication from RLC that the maximum number of retransmissions has been reached

UE actions after RLF detection

If air interface security has not been activated, UE goes to RRC_IDLE and starts cell selection,
Tracking Area Update follows when suitable cell is found
If air interface security is activated, initiate the RRC connection re-establishment procedure
NOTE: in RL10/RL20 eNB does not support RRC connection re-establishment and eNB
always responds with a re-establishment reject message  Tracking Area Update follows

Timer T301 supervises the RRC connection reestablishment procedure

Start: Transmission of RRCConnectionReestabilshmentRequest
Stop: Reception of RRCConnectionReestablishment or
RRCConnectionReestablishmentReject message as well as when the selected cell becomes
unsuitable
At expiry: Go to RRC_IDLE
Def. 200ms

RA47057EN60GLA0 26
Call Drop Analysis

Source: 3GPP TS 36.331, TS 36.300

Detection of physical layer problems in RRC_CONNECTED

The UE shall, upon receiving N310 consecutive "out-of-sync" indications from lower layers
while neither T300, T301, T304 nor T311 is running, start timer T310

Recovery of physical layer problems

Upon receiving N311 consecutive "in-sync" indications from lower layers while T310 is running,
the UE shall stop timer T310;
NOTE 1: In this case, the UE resumes the RRC connection without explicit Signaling, i.e. the
UE resumes the entire radio resource configuration.
NOTE 2: Periods in time where neither "in-sync" nor "out-of-sync" is reported by layer 1 do not
affect the evaluation of the number of consecutive "in-sync" or "out-of-sync" indications.

Radio link failure is triggered by

Upon T310 expiry
upon random access problem indication from MAC while neither T300, T301, T304 nor T311 is
running
upon indication from RLC that the maximum number of retransmissions has been reached

UE actions after RLF detection

If air interface security has not been activated, UE goes to RRC_IDLE and starts cell selection,
Tracking Area Update follows when suitable cell is found
If air interface security is activated, initiate the RRC connection re-establishment procedure
NOTE: in RL10/RL20 eNB does not support RRC connection re-establishment and eNB
always responds with a re-establishment reject message  Tracking Area Update follows

RA47057EN60GLA0 27
Call Drop Analysis

•At least Qualcomm chip shows in-sync / out-sync BLER

•TS36.331: “Periods in time where neither "in-sync" nor "out-of-sync" is
reported by layer 1 do not affect the evaluation of the number of
consecutive "in-sync" or "out-of-sync" indications.”

RA47057EN60GLA0 28
Call Drop Analysis

Source: 3GPP TS 36.331, TS 36.300

Detection of physical layer problems in RRC_CONNECTED

The UE shall, upon receiving N310 consecutive "out-of-sync" indications from lower layers
while neither T300, T301, T304 nor T311 is running, start timer T310

Recovery of physical layer problems

Upon receiving N311 consecutive "in-sync" indications from lower layers while T310 is running,
the UE shall stop timer T310;
NOTE 1: In this case, the UE resumes the RRC connection without explicit Signaling, i.e. the
UE resumes the entire radio resource configuration.
NOTE 2: Periods in time where neither "in-sync" nor "out-of-sync" is reported by layer 1 do not
affect the evaluation of the number of consecutive "in-sync" or "out-of-sync" indications.

Radio link failure is triggered by

Upon T310 expiry
upon random access problem indication from MAC while neither T300, T301, T304 nor T311 is
running
upon indication from RLC that the maximum number of retransmissions has been reached

UE actions after RLF detection

If air interface security has not been activated, UE goes to RRC_IDLE and starts cell selection,
Tracking Area Update follows when suitable cell is found
If air interface security is activated, initiate the RRC connection re-establishment procedure
NOTE: in RL10/RL20 eNB does not support RRC connection re-establishment and eNB
always responds with a re-establishment reject message  Tracking Area Update follows

RA47057EN60GLA0 29
Call Drop Analysis

Source: RRC spec, 3GPP TS 36.331

When UE receives RRC Connection Reconfiguration with

mobilityControlInfo IE (i.e, ”handover command”), it starts timer T304
If PRACH procedure to the target cell does not succeed by the time
T304 expires, handover failure occurs  (If air interface security is
active) UE tries RRC Conn Re-establishment with re-establishment
cause ”handoverFailure”

RA47057EN60GLA0 30
Call Drop Analysis

RA47057EN60GLA0 31
Call Drop Analysis

RA47057EN60GLA0 32
Call Drop Analysis

RA47057EN60GLA0 33
Call Drop Analysis

RA47057EN60GLA0 34
Call Drop Analysis

RA47057EN60GLA0 35
Call Drop Analysis

Radio L1 SFS: “The periodic RI reports on PUCCH or PUSCH shall not be

taken into account for radio link failure detection.”

RA47057EN60GLA0 36
Call Drop Analysis

Source: RRM SFS 2041

RA47057EN60GLA0 37
Call Drop Analysis

RA47057EN60GLA0 38
Call Drop Analysis

Radio L1 SFS: Aperiodic reports on PUSCH come with a CRC, hence in this
case no special DTX detection has to be performed rather than just reporting
CRC ok or CRC failed

RA47057EN60GLA0 39
Call Drop Analysis

RA47057EN60GLA0 40
Call Drop Analysis

RA47057EN60GLA0 41
Call Drop Analysis

RA47057EN60GLA0 42
Call Drop Analysis

RA47057EN60GLA0 43
Call Drop Analysis

RA47057EN60GLA0 44
Call Drop Analysis

RA47057EN60GLA0 45
Call Drop Analysis

RA47057EN60GLA0 46
Call Drop Analysis

RAN2#65 decided that a UE processes UL grants only if TA timer is running,

i.e., UL grant when TAT is not running does not trigger a random access
procedure (see, e.g., R2-090967 CR0252)

eNB has inactivity timer parameter to get UE to IDLE

MME also has has a ”mobile reachable” timer, mme default = 58min, periodic
TA timer=54min default, implicit detach timer = 58min (default) (checked Dec
2010).

RA47057EN60GLA0 47
Call Drop Analysis

Random access procedure for UEs being UL Out-of-Sync (RL30)

If MAC has been triggered by higher layers (layer 3) to perform a random access procedure for a UE being UL Out-
of-Sync in order to gain timing alignment for this UE again (see TF_LTE_SFS_RL2_1236), MAC entity in eNB shall
select one of the free dedicated RA preambles that can be used for non-contention based RA (see
TF_LTE_SFS_RL2_1269) and signal the selected RA preamble to the UE in order to command a non-contention
base RA procedure to the UE . If there are no dedicated preambles available, then the eNB shall command a
contention based RA procedure for the UE instead.
The preamble Signaling shall be via PDCCH using DCI format 1A as specified in [3GPP-36.212], section 5.3.3.1.3.
The dedicated preamble can be reused as soon as MAC detects the success or failure of the RA procedure. The
RA procedure is considered to be successful if following the transmission of the Random Access Response
message containing the respective preamble within the Random Access Response Window, there was successful
transmission of data in DL (or UL). The RA procedure is considered to have failed if, following the assignment of the
dedicated preamble on PDCCH, MAC has to assume that the UE has exceeded the configured maximum number of
preamble transmissions while no transmission of the assigned dedicated preamble was detected by eNB. A timer
with configurable value (O&M parameter DedPreambleReuseTimer, see TF_LTE_SFS_RL2_1060) may be used as
worst case condition after which the failure of the RA procedure can be assumed by MAC.
Note that an optimized value of the timer setting for detection of an RA failure may be derived from settings for the
RA response window size, PRACH configuration, and maximum number of preamble transmissions.
Any necessary alignments with layer 3 requirements for RLD x releases are left to entity specification and
implementation.

Non-Contention Based RA Preamble Assignment (DL data arrival case), RL30

When there are DL data for an UE awaiting transmission and the eNB has detected that the UL synchronization
status of the UE is “Out-of-Sync”, the MAC entity in eNB shall select one of the free dedicated RA preambles that
can be used for non-contention based RA (see TF_LTE_SFS_RL2_1269). The selected RA preamble shall be
signaled to UE with PDCCH Signaling. If there are no dedicated preambles available, then the eNB shall command
a contention based RA procedure for the UE.
The preamble Signaling shall be via PDCCH using DCI format 1A as specified in [3GPP-36.212], section 5.3.3.1.3.
The dedicated preamble can be reused as soon as MAC detects the success or failure of the RA procedure. The
RA procedure is considered to be successful if following the transmission of the Random Access Response
message containing the respective preamble within the Random Access Response Window, there was successful
transmission of data in DL (or UL). The RA procedure is considered to have failed if, following the assignment of the
dedicated preamble on PDCCH, MAC has to assume that the UE has exceeded the configured maximum number of
preamble transmissions while no transmission of the assigned dedicated preamble was detected by eNB. A timer
with configurable value (O&M parameter DedPreambleReuseTimer, see TF_LTE_SFS_RL2_1060) may be used as
worst case condition after which the failure of the RA procedure can be assumed by MAC.
Note that an optimized value of the timer setting for detection of an RA failure may be derived from settings for the
RA response window size, PRACH configuration, and maximum number of preamble transmissions.

RA47057EN60GLA0 48
Call Drop Analysis

RA47057EN60GLA0 49
Call Drop Analysis

Procedure describes how an UE gets back into UL synchronization from a

state in which the time alignment has been lost
eNB detects that the time alignment of the UE is UL out-of-sync
(e.g. expiration of time alignment timer)
UE also detects out-of-sync (same trigger) and releases resources
on PUCCH for CQI reporting and scheduling request
If eNB detects DL data (either data traffic or RRC Signaling)
eNB sends a PDCCH order for RA procedure to UE (DCI 1A with specific codepoint;
preferably non-contention based RA depending on preamble availability)
UE starts a random access procedure
eNB recognizes when random access of the UE was successful and UE UL time
alignment is back “in-sync”
If UE detects UL data (either data traffic or RRC Signaling):
UE starts a random access procedure (contention-based)
eNB recognizes when random access of the UE was successful and UE UL time
alignment is back “in-sync”
eNB triggers the RRC procedure RRC Connection Reconfiguration
to configure (again) the PUCCH resources for CQI reporting and
scheduling request
Same resource used for simplification but could be optimized optionally
Note: the RRC message RRCConnectionReconfigurationComplete is
already sent using the configured PUCCH resources for scheduling
request.

RA47057EN60GLA0 50
Call Drop Analysis

Procedure describes how eNB detects that an UE has been lost

– triggered by downlink traffic
eNB detects that the time alignment of the UE is “out-of-
sync” (e.g. expiration of time alignment timer)
UE detects also that the time alignment is out-of-sync and
releases its PUCCH resources for CQI reporting and
scheduling request and/or UE detects a radio link failure
and moves to RRC_IDLE
If eNB detects DL data (either data traffic or RRC signaling)
eNB sends a PDCCH order DCI 1A to UE (may include several
re-tries)
UE will not recognize this PDCCH order because it has gone
to RRC_IDLE
eNB recognizes that the random access of the UE was not
successful (UE does not send any random access preamble)
and that the “in-sync” handling has failed
This event is handled as a new trigger for the radio link
failure procedure
eNB starts a supervision timer T-RLF and triggers UE
Context Release after timer expiration
Note: by using the supervision timer, UE is able to return to
cell via the RRC Connection Reestablishment

RA47057EN60GLA0 51
Call Drop Analysis

Procedure describes how eNB handles an UE whose time

alignment is out-of-sync and whose inactivity timer has expired
eNB detects that the time alignment of the UE is “out-of-
sync” (e.g. expiration of time alignment timer)
The inactivity timer for the UE expires. In the meantime,
UE may still be RRC_CONNECTED or may have gone to
RRC_IDLE silently
eNB checks the reachability of the UE by sending the
PDCCH order (DCI 1A)
If UE performs a random access
eNB recognizes that this is a normal “user inactivity” case
eNB sends the RRC message RRCConnectionReconfiguration to configure
PUCCH/SRS resources
eNB sends the message UE CONTEXT RELEASE REQUEST to MME with cause
“User Inactivity”
If MME starts the UE Context Release procedure
eNB sends the RRC message RRCConnectionRelease to UE and releases the
UE context.
If MME does not start the UE Context Release procedure
eNB keeps the current configuration.
Note: this may happen if new DL data arrive - either data traffic or S1AP
signaling
If eNB does not recognize any random access by the UE
eNB recognizes that this is a RLF trigger.
eNB starts immediately the UE Context Release procedure for RLF

RA47057EN60GLA0 52
Call Drop Analysis

RA47057EN60GLA0 53
Call Drop Analysis

RA47057EN60GLA0 54
Call Drop Analysis

RA47057EN60GLA0 55
Call Drop Analysis

RA47057EN60GLA0 56
Call Drop Analysis

PDCP status reporting should be activated for DL, to avoid TCP throughput notch during handover. Set
statusRepReq=3 in bearer PDCP profile.

RA47057EN60GLA0 57
Call Drop Analysis

PDCP status reporting should be activated for both UL and DL, to avoid TCP throughput notch during handover. Set
statusRepReq=3 in bearer PDCP profile.

RA47057EN60GLA0 58
Call Drop Analysis

RA47057EN60GLA0 59
Call Drop Analysis

RA47057EN60GLA0 60
Call Drop Analysis

RA47057EN60GLA0 61
Call Drop Analysis

RA47057EN60GLA0 62
Call Drop Analysis

RA47057EN60GLA0 63
Call Drop Analysis

RA47057EN60GLA0 64
Call Drop Analysis

RA47057EN60GLA0 65
Call Drop Analysis

RA47057EN60GLA0 66
Call Drop Analysis

RA47057EN60GLA0 67
Call Drop Analysis

RA47057EN60GLA0 68
Call Drop Analysis

RA47057EN60GLA0 69
Call Drop Analysis

RA47057EN60GLA0 70
Call Drop Analysis

RA47057EN60GLA0 71
Call Drop Analysis

RA47057EN60GLA0 72
Call Drop Analysis

RA47057EN60GLA0 73
Call Drop Analysis

RA47057EN60GLA0 74
Call Drop Analysis

RA47057EN60GLA0 75
Call Drop Analysis

THOoverall = T304 + T311 + T301 + THOoverallD

Where
T304 supervises the successful completion of a handover or cell
change given by t304IntraLte parameter, def 1000ms
T311 is the RRC re-establishment supervision timer in UE (the
maximum value 30000ms) def 3s
Timer T301 supervises the RRC connection reestablishment
procedure
Start: Transmission of
RRCConnectionReestabilshmentRequest
Stop: Reception of RRCConnectionReestablishment or
RRCConnectionReestablishmentReject message as well
as when the selected cell becomes unsuitable
At expiry: Go to RRC_IDLE
Def. 200ms
THOoverallD Covers the estimated time taken to send an
RRC:CONNECTION RECONFIGURATION message to the UE
Hard coded to 20ms

RA47057EN60GLA0 76
Call Drop Analysis

RA47057EN60GLA0 77
Call Drop Analysis

RA47057EN60GLA0 78
Call Drop Analysis

RA47057EN60GLA0 79
Call Drop Analysis

RA47057EN60GLA0 80
Call Drop Analysis

RA47057EN60GLA0 81
Call Drop Analysis

• Once the X2AP: HANDOVER REQUEST message has been sent to the
target eNB, guarding timer TX2RELOCprep is started to guard the handover
preparation phase

• Hard Coded to 500ms

RA47057EN60GLA0 82
Call Drop Analysis

RA47057EN60GLA0 83
Call Drop Analysis

Based on source cell parameter values:

TX2RELOCoverall = T304 + T311 + T301 + TX2RELOCoverallDelta

where:
· T304 is the maximum value of 2000ms (defined by 3GPP)
· T311 is the value set in the source eNB in [SYSINFO SFS.611]
· T301 is the value set in the source eNB in [SYSINFO SFS.611]
· TX2RELOCoverallDelta as defined by the vendor in MM.885 as the estimated time
taken to send the RRC: RRC CONNECTION RECONFIGURATION message to
the UE plus the time taken for the UE to generate and send an RRC message in
the target cell and for the target eNB to send an S1AP message to the MME
(i.e. start the Path Switch procedure)

TX2RELOCoverallDelta is <p name="tx2RelODelta">150</p> in the vendor file.

RA47057EN60GLA0 84
Call Drop Analysis

TX2RELOCexec = T304 + T311 + TX2RELOCexecDelta

 where:
• T304 supervises the successful completion of a handover or cell
change given by t304IntraLte parameter, def 1000ms (the value
set in the target eNB)
• T311 is the RRC re-establishment supervision timer in UE (the
maximum value 30000ms) def 3s
• TX2RELOCexecDelta is the estimated time taken from sending the
X2AP: HANDOVER REQUEST ACKNOWLEDGE message to the
UE starting timer T304, plus the time taken for the UE to generate
and send an RRC message in the target cell (hard coded 70ms)

RA47057EN60GLA0 85
Call Drop Analysis

Based on source cell parameter values:

TX2RELOCoverall = T304 + T311 + T301 + TX2RELOCoverallDelta

where:
· T304 is the maximum value of 2000ms (defined by 3GPP)
· T311 is the value set in the source eNB in [SYSINFO SFS.611]
· T301 is the value set in the source eNB in [SYSINFO SFS.611]
· TX2RELOCoverallDelta as defined by the vendor in MM.885 as the estimated time
taken to send the RRC: RRC CONNECTION RECONFIGURATION message to
the UE plus the time taken for the UE to generate and send an RRC message in
the target cell and for the target eNB to send an S1AP message to the MME
(i.e. start the Path Switch procedure)

TX2RELOCoverallDelta is <p name="tx2RelODelta">150</p> in the vendor file.

RA47057EN60GLA0 86
Call Drop Analysis

Based on source cell parameter values:

TX2RELOCoverall = T304 + T311 + T301 + TX2RELOCoverallDelta

where:
· T304 is the maximum value of 2000ms (defined by 3GPP)
· T311 is the value set in the source eNB in [SYSINFO SFS.611]
· T301 is the value set in the source eNB in [SYSINFO SFS.611]
· TX2RELOCoverallDelta as defined by the vendor in MM.885 as the estimated time
taken to send the RRC: RRC CONNECTION RECONFIGURATION message to
the UE plus the time taken for the UE to generate and send an RRC message in
the target cell and for the target eNB to send an S1AP message to the MME
(i.e. start the Path Switch procedure)

TX2RELOCoverallDelta is <p name="tx2RelODelta">150</p> in the vendor file.

RA47057EN60GLA0 87
Call Drop Analysis

RA47057EN60GLA0 88
Call Drop Analysis

RA47057EN60GLA0 89
Call Drop Analysis

RA47057EN60GLA0 90
Call Drop Analysis

RA47057EN60GLA0 91
Call Drop Analysis

LNCEL/tStoreUeCntxt, 100...20000 ms, step 100 ms, default 2000ms

RA47057EN60GLA0 92
Call Drop Analysis

LNCEL/tStoreUeCntxt, 100...20000 ms, step 100 ms, default 2000ms

RA47057EN60GLA0 93
Call Drop Analysis

RA47057EN60GLA0 94
Call Drop Analysis

LNCEL/tStoreUeCntxt, 100...20000 ms, step 100 ms, default 2000ms

RA47057EN60GLA0 95
Call Drop Analysis

RA47057EN60GLA0 96
Call Drop Analysis

RA47057EN60GLA0 97
Call Drop Analysis

RA47057EN60GLA0 98
Call Drop Analysis

RA47057EN60GLA0 99
Call Drop Analysis

RA47057EN60GLA0 100
Call Drop Analysis

RA47057EN60GLA0 101
Call Drop Analysis

RA47057EN60GLA0 102
Call Drop Analysis

RA47057EN60GLA0 103
Call Drop Analysis

RA47057EN60GLA0 104
Call Drop Analysis

RA47057EN60GLA0 105
Call Drop Analysis

RA47057EN60GLA0 106
Call Drop Analysis

RA47057EN60GLA0 107
Call Drop Analysis

RA47057EN60GLA0 108
Call Drop Analysis

RA47057EN60GLA0 109
Call Drop Analysis

RA47057EN60GLA0 110
Call Drop Analysis

RA47057EN60GLA0 111
Call Drop Analysis

RA47057EN60GLA0 112
Call Drop Analysis

RA47057EN60GLA0 113
Call Drop Analysis

RA47057EN60GLA0 114
Call Drop Analysis

RA47057EN60GLA0 115
Call Drop Analysis

RA47057EN60GLA0 116
Call Drop Analysis

RA47057EN60GLA0 117
Call Drop Analysis

RA47057EN60GLA0 118
Call Drop Analysis

RA47057EN60GLA0 119
Call Drop Analysis

RA47057EN60GLA0 120
Call Drop Analysis

RA47057EN60GLA0 121
Call Drop Analysis

RA47057EN60GLA0 122
Call Drop Analysis

RA47057EN60GLA0 123
Call Drop Analysis

RA47057EN60GLA0 124
Call Drop Analysis

RA47057EN60GLA0 125
Call Drop Analysis

RA47057EN60GLA0 126
Call Drop Analysis

RA47057EN60GLA0 127
Call Drop Analysis

RA47057EN60GLA0 128
Call Drop Analysis

RA47057EN60GLA0 129
Call Drop Analysis

RA47057EN60GLA0 130
Call Drop Analysis

RA47057EN60GLA0 131
Call Drop Analysis

RA47057EN60GLA0 132
Call Drop Analysis

RA47057EN60GLA0 133
Call Drop Analysis

RA47057EN60GLA0 134
Call Drop Analysis

RA47057EN60GLA0 135