Professional Documents
Culture Documents
VoLTE Training
Detailed Analysis for Radio
13 March 2017
09.06.2014
09.10.2014
09.20.2014
09.24.2014
10.04.2014
10.08.2014
10.12.2014
10.18.2014
10.22.2014
08.25.2014
08.29.2014
08.31.2014
09.02.2014
09.04.2014
09.08.2014
09.12.2014
09.14.2014
09.16.2014
09.18.2014
09.22.2014
09.26.2014
09.28.2014
09.30.2014
10.02.2014
10.06.2014
10.10.2014
10.14.2014
10.16.2014
10.20.2014
7 © Nokia Solutions and Networks 2014
VoLTE Call Setup Failure due to Handover in Progress
MME bearer request handling
• 3GPP 36.413 (chapter 8.2): If a handover becomes necessary during E-RAB Setup, the
eNB may interrupt the ongoing E-RAB Setup procedure and initiate the Handover
Preparation procedure as follows:
- The eNB shall send the E-RAB SETUP RESPONSE message in which the eNB shall indicate, if
necessary all the E-RABs fail with an appropriate cause value, e.g., ”S1 intra system Handover
triggered”, “S1 inter system Handover triggered” or “X2 Handover triggered”.
• Therefore, MME needs to resend the E-RAB Setup Request when it receives the Path
Switch Request after the failed E-RAB setup (applies for E-RAB release or modify
procedure as well) – feature implemented in Nokia MME (NS15 onwards).
- In case the SGW is changed due the HO then MME should send the Create Bearer Response
message to SGW indicating rejected E-RAB with cause 110 “Temporarily rejected due to
handover/TAU/RAU procedure in progress“.
• 3GPP TS 23.401: Upon reception of a rejection for an EPS bearer(s) PDN GW initiated
procedure with an indication that the request has been temporarily rejected due to
mobility procedure in progress, the PDN GW start a locally configured guard timer. The
PDN GW shall re-attempt, up to a pre-configured number of times, when either it
detects that the Tracking Area Update procedure is completed or has failed using
message reception or at expiry of the guard timer.
- PDN GW which initiated the bearer related request (e.g. Create / Update / Delete Bearer
request) is supposed to handle the rejection by re-sending the request after handover is
completed.
- Nokia PGW (NG3.2 onwards) has re-attempt mechanism, with the default value “handover-
rejection-guard-timer-reattempt-count” = 2, i.e. when PGW receives the rejection, it will re-initiate
rejected EPS bearer procedure to MME.
SIP:INVITE
SIP: TRYING
SIP:INVITE
SIP: TRYING
Retransmission
Create Bearer Response Cause: Temporarily Rejected due to Handover Procedure in
(failure) Progress
Create Session Request (QCI5)
Modify Bearer Request
E-UTRAN E-RAB QCI1 with data in the queue drop ratio (LTE_5571f) =
100*sum(ERAB_REL_ENB_ACT_QCI1)
sum(ERAB_REL_ENB_QCI1 + ERAB_REL_HO_PART_QCI1 + EPC_EPS_BEAR_REL_REQ_N_QCI1 +
EPC_EPS_BEAR_REL_REQ_D_QCI1 + EPC_EPS_BEAR_REL_REQ_R_QCI1 +
EPC_EPS_BEAR_REL_REQ_O_QCI1 + ERAB_REL_EPC_PATH_SWITCH_QCI1 - ERAB_REL_TEMP_QCI1 +
ERAB_REL_SUCC_HO_UTRAN_QCI1 + ERAB_REL_SUCC_HO_GERAN_QCI1)
%
0.50
- The difference is quite large between all
drops (during inactivity) and drops only in 0.40
case there is data in buffer as shown in 0.30
the graph on the right:
0.20
• 0.4%-0.8% for all drops
0.10
• 0.05%- 0.15% for only drops with data
0.00
in buffer
20 00:00
20 07:00
20 21:00
21 04:00
21 11:00
21 18:00
22 01:00
22 08:00
22 15:00
22 22:00
23 05:00
23 12:00
23 19:00
24 02:00
24 09:00
24 16:00
24 23:00
25 06:00
25 13:00
25 20:00
26 03:00
26 10:00
20 14:00
26 17:00
17 © Nokia Solutions and Networks 2014
VoLTE Drop Call Rate
GBR vs. non-GBR drop calls
GBR and non-GBR E-RAB Drop Rate (%) • QCI1 E-RAB drop rate is much
VoLTE Drops EPC initiated VoLTE Drops eNB initiated E-RAB Drop Rate, User Perspective (eNB pre-emptions excluded) VoLTE Drop Rate
worse compared to non-GBR
2.00 6 000
traffic.
1.80 720 users - 15 MHz
5 000
• VoLTE (QCI1) bearer drop rate
Admission Control Threshold – 75% 600 users - 10 MHz
1.60
has an increasing trend up to
1.40
4 000
1.6% with increased voice
traffic.
1.00 3 000
- The QCI1 session time (activity
time) is much longer compared
0.80 to the non-GBRQCI and
0.60
2 000 therefore, QCI1 is much more
sensitive to mobility related
0.40
1 000
performance challenges (too late
0.20
HO, too early HO, RRC re-
establishments)
0.00 0
09.14.2014
09.16.2014
09.18.2014
09.20.2014
09.22.2014
09.24.2014
10.20.2014
10.22.2014
08.25.2014
08.27.2014
08.29.2014
08.31.2014
09.02.2014
09.04.2014
09.06.2014
09.08.2014
09.10.2014
09.12.2014
09.26.2014
09.28.2014
09.30.2014
10.02.2014
10.04.2014
10.06.2014
10.08.2014
10.10.2014
10.12.2014
10.14.2014
10.16.2014
10.18.2014
18 © Nokia Solutions and Networks 2014
VoLTE KPI Benchmarking active drops per active minute QCI1
Active Drops per Session Time active drops per active minute non-GBR
Ratio
3
• The QCI1 performance in terms of drops 0.0015
per minute is much better compared to 2
the non-GBR, i.e. QCI1 performance 0.001
10.11.2014
10.12.2014
10.13.2014
10.14.2014
10.15.2014
10.16.2014
10.17.2014
10.18.2014
10.19.2014
10.20.2014
10.21.2014
10.22.2014
10.23.2014
10.24.2014
10.25.2014
19 © Nokia Solutions and Networks 2014
VoLTE Drop Call Rate
DCR vs. Release Causes
• After iPhone6/6Plus launched with
iPhone6 VoLTE VoLTE enabled, the VoLTE calls
launch
increased by 6 times.
• VoLTE drop rate KPI is stable with
~1.6% level with more call attempts.
• Howeve, abnormal VoLTE call release
distribution is as follows:
- ~80% calls are caused by EPC release due to
Radio cause
- ~10% calls are caused by ENB release due to
Radio cause
- ~10% calls are caused by ENB release due to
Other cause
• After increasing the t304InterRAT setting from 500ms (default) to 2000ms, the
SRVCC failure rate reduce ~13%, and QCI1 drop rate improvement can be
seen as well TS1RELOCoverall = TDRX + T304 + T311 + T301 + TS1RELOCoverallDelta
LTE_5562a Inter RAT HO Att, UTRAN, SRVCC LTE_5572a E-RAB QCI1 DR, RAN view
LTE_5563a Inter RAT HO FR, UTRAN, SRVCC 2.5
140 40
35 2
120
100 30
1.5
25
80
20
60 1
15
40 10 0.5
20 5
0 0 0
05-15
05-16
05-17
05-18
05-19
05-20
05-21
05-22
05-23
05-24
05-25
05-26
05-27
05-28
05-29
05-30
05-31
06-01
06-02
06-03
06-04
06-05
05-15
05-16
05-17
05-18
05-19
05-20
05-21
05-22
05-23
05-24
05-25
05-26
05-27
05-28
05-29
05-30
05-31
06-01
06-02
06-03
06-04
06-05
24 © Nokia Solutions and Networks 2014
SRVCC to WCDMA/GSM
iPhone6 issues with container size limitation
• SRVCC might fail due to size of "source to transparent container" is more that 255
bytes in S1AP: HandoverRequired message and thus, RNC does not decode WCDMA
BTS ID correctly and voice call is dropped.
- It could be caused by too big size of UE capability IE especially with Apple iPhones as it
supports lots of bands.
- As a workaround in some networks, SRVCC to WCDMA is set to both PS + CS in LNADJW
(SRVCC HO indication) because Relocation Request from PS CN has correct information even
though CS CN request is not valid.
- Another workaround could be the activation of LTE2324 Network requested UE capabilities
feature (FL15A) to limit UE capability information message size in case of CA is enabled in the
network.
- LTE2324 is based on 3GPP functionality and introduces filtering of supported CA band
combinations on UE side:
• upon eNB request, UE will report supported CA band combinations related only to bands used in Operator’s
network.
25 © Nokia Solutions and Networks 2014
SRVCC Benchmarking
SRVCC Success Rate
SRVCC Success (%)
• SRVCC performance for
Inter RAT HO Attempts to UTRAN SRVCC Inter RAT HO UTRAN with SRVCC Success Rate
VoLTE has declining trend with
95 20 000 increased attempts.
90 720 users - 15 MHz 18 000 - SRVCC is degraded due to an
85 Admission Control Threshold – 75% 600 users - 10 MHz
issue in MSS not sending proper
16 000
cause code for successful
80
14 000 SRVCC HO and thus, SRVCC
75 success counter is not correctly
12 000
Attempts (#)
incremented.
Success (%)
70
10 000
65 • IMS network was not
60
8 000
supporting aSRVCC
55
6 000
- Customized firmware was
50
4 000 created for the phones to do
45 2 000
CSFB instead of VoLTE
when the RSRP is less than
40 0
-115 dBm.
08.25.2014
08.27.2014
09.08.2014
09.10.2014
09.12.2014
09.24.2014
09.26.2014
10.08.2014
10.10.2014
08.29.2014
08.31.2014
09.02.2014
09.04.2014
09.06.2014
09.14.2014
09.16.2014
09.18.2014
09.20.2014
09.22.2014
09.28.2014
09.30.2014
10.02.2014
10.04.2014
10.06.2014
10.12.2014
10.14.2014
10.16.2014
10.18.2014
10.20.2014
10.22.2014
26 © Nokia Solutions and Networks 2014
SRVCC
Handover interruption time
• There is a short interruption period during SRVCC, i.e. user can notice ‘silent’ period.
• The interruption time of SRVCC should not be higher than 300ms as required in
TS 22.278 from EUTRAN to UTRAN.
• On the other hand, SRVCC should be triggered early enough to avoid degradation of voice
quality → VoLTE service area is reduced.
- SRVCC during the alerting stage without aSRVCC support (terminal/IMS) may cause the increased number of call
setup failures
KPI definitions
• Report Set RSLTE052 (accessible from JUMP) in Report Manager collects OSS KPIs and counters to
monitor the traffic load and VoLTE Service Quality.
• Performance monitoring for VoLTE by NetEng. Based on references from JUMP and RAN LTE KPIs
document is a collection of LTE KPIs and counters used when monitoring the VoLTE service.
KPI values
• The MBB and NPO KPI commitment targets guideline . Its contents are aligned with the more detailed
document KPI Targets document below. Note: Always download the latest one from the link above.
• MBB Performance Benchmarker
VoLTE KPI List for Acceptance
• A list covering all domains (not only radio) with OSS and drive test KPIs to be used as part of
customer discussions: VoLTE KPI List for Acceptance
Specified by ITU-T
recommendation P.800
• Non-perceptual methods (E-Model with R-Factor) are general physical or technical measures.
- Combines a number of values measuring the effect of various network impairments such as codec bitrate, jitter,
packet loss as well as mouth-to-ear delay which contributes to Conversational Quality.
• Used voice codec will have a big impact on the achieved MOS score
• Also the used voice samples (even languages) will have an effect on the MOS score.
- Results from different network cannot be compared unless the same sample used for all cases.
• Different handsets have different audio properties (frequency response, distortion, etc.)
- Changing the handset might give different results
- In the worst case handset audio module needs to be also calibrated and adjusted as there might
be differences in different units
• Drive test tool hardware (UEs, laptops, audio modules, power supplies, etc.) can have
effect on the MOS score if setup varies (cable routing)
• Other factors, e.g. there has been a case where a faulty switching power supply has
caused interference that has degraded the achieved MOS score
Voice codecs
300ms 2.9
500ms 2.86
1500ms 3.30
• The testing for the cell edge user showed significant MOS improvement when tDiscard
(for QCI1) was increased.
1. From the test resut, disable DRX can improve the RTP Jitter
2. increasing pdcp-SN-Size can further improve RTP jitter and MOS and RTP packet loss
RTP
Packet Loss
Date Test Case RSRP SINR MOS Jitter Duration Comments
Ratio
(ms)
20151215 Test case1 -83.166 15.129 0.58% 3.8 9.57 309.46 Disable QCI1 DRX
• However, VoLTE traffic steering with proper layering management could be beneficial in
order to improve network efficiency and end user experience for both VoLTE and data
services.
- Steering VoLTE traffic to dedicated layer free up control and data channel resources for non-VoLTE
users and thus, average throughput of data users might increase.
- Target VoLTE layer may have a better continuous coverage and therefore, VoLTE speech quality is
improved due to less frequent IFHO/SRVCC handovers, i.e. less voice interruptions during HO
measurement and execution phase.
• VoLTE calls can be steered to the preferred frequency layer using either service based
handover upon QCI1 bearer establishment or coverage/load based handovers.
- On the other hand, traffic steering is also increasing inter-frequency handovers in the network
which might lead drop calls unless mobility parameters are properly optimized.
interFrqThrH threshSrvLow
• The general strategy for VoLTE deployment is to initially enable voice service on all
carriers in the network in order to ensure maximum coverage and accessibility.
• Once VoLTE traffic is increasing the strategy should be reviewed and possible layering
options studied to gain understanding of the impact of network capacity and coverage on
both VoLTE and data services.
• VoLTE preferred frequencies can be chosen based on the following factors:
- Coverage: Contiguous coverage to avoid risk of dropped calls due to IFHO or SRVCC handovers.
Alternatively, low frequency band operation for higher cell range is beneficial to minimize the
number of handovers as well as to provide a good indoor coverage.
- Capacity: Frequency band with highest capacity (i.e. large bandwidth) can serve more VoLTE
users and on the other hand, data users might have improved throughputs on non-VoLTE layers
due to more scheduling occasions without VoLTE traffic.
Inter-RAT WCDMA
measurements will be
started at
threshold2Wcdma.
Threshold2a b2Threshold1Utra
• VoLTE users are recommended to start measuring WCDMA layer earlier than non-
VoLTE users (threshold2WcdmaQci1 > threshold2Wcdma)
• SRVCC to trigger 2-3dB earlier than PS handover to maintain voice service quality
perceived by end users (b2threshold1UtraQci1 > b2Threshold1Utra).
• If the measurements are started too late (low A2 threshold) and too large amount of 3G neighbors the
UE does not have enough time to send measurement reports (B2) hence the call drops.
• If A2 is set very close to B2 threshold this will reduce the time during which the measurement gaps
are scheduled to the mobile which may lead to non-optimal choice of target RAN cell if UE does not
have time to measure the best target cell (e.g. long neighboring list).
• However, if the SRVCC is triggered too early there might be too many SRVCC attempts and aSRVCC
attempts causing further challenges in case not supported by IMS.
51 © Nokia Solutions and Networks 2014
SRVCC Performance
Setting B2 threshold VoLTE call drop case by redirect (from field measurement)
LTE_771b Rel R, QCI1 ENB rel, RNL Redir LTE_5562a Inter RAT HO Att, UTRAN, SRVCC
LTE_5572b E-RAB QCI1 DR, RAN view LTE_5563a Inter RAT HO FR, UTRAN, SRVCC
Parameter Name MOC Full Name Current value (Internal) Proposed value (Internal)
a2RedirectQci1 LNCEL <Change
A2information classification
based redirect in footer>calls
for VoLTE enabled (1) disabled (0)
53 © Nokia Solutions and Networks 2014
SRVCC
RSRQ based SRVCC HO
• If SRVCC triggering threshold is set to very low value the user might experience bad RF
quality before RSRP threshold is reached.
• However, SRVCC trigger (B2) is typically based on RSRP and thus, SRVCC is not
triggered once RSRQ degrades.
• LTE2572 RSRQ based B2 feature is available from FL17 onwards.
DTX
DTX
DTX
DTX
DTX
CQI
CQI
CQI
CQI
CQI
DTX
DTX
DTX
DTX
DTX
CQI
CQI
CQI
CQI
CQI
time
LNCEL/cqiPerNp=10ms CQI_RLF ON
CQI_RLF
Example Vendor Parameter Values: OFF
nCqiDtx=4
nCqiRec=2
No Changes in VoLTE
Drop Ratio
• FL16 feature allows tuning RLF detection sensitivity at eNB in order to keep UEs longer
in RRC connection state.
• It applies to cases the eNB indicates RLF due to CQI DTX
- The tuning is possible by setting LNBTS:nCqiDtx and LNBTS:nCqiRec parameters
• LTE2206 does not change RLF detection functionality, sensitivity RLF indication is
issued
LTE1569 allows to configure QCI1 specific settings of N310 (LNCEL:n310qci1) and T310 (LNCEL:t310qci1) which are provided to the
UE during QCI1 bearer establishment by RRC Connection Reconfiguration message (overwriting SIB2 broadcasted values).
When UE is ending the VoLTE call, eNB sends RRC Connection Re-configuration message to release QCI1 DRB, this message
includes also RLF-TimersAndConstants-r9 IE with legacy values of T310 and N310 (LNCEL:t310 and LNCEL:n310).
Maximum number of
N311 LNCEL On-line 0:n1;1:n2;2:n3;3:n4;4:n5;5:n6;6:n8;7:n10 n1 n1 n1
in-sync indications
0:1000ms;1:3000ms;2:5000ms;3:10000ms;4:15000
T311 Timer T311 LNCEL On-line 3000ms 3000ms 3000ms
ms;5:20000ms;6:30000ms
0:100ms;1:200ms;2:300ms;3:400ms;4:600ms;5:100
t301 Timer T301 LNCEL On-line 400ms 400ms 400ms
0ms;6:1500ms;7:2000ms
• Set 1: initial ERAB drop rate for QCI1 with feature not activated: 0.14%
• Set 2: reduction of T310qci1 to 500ms improvement of ERAB DR QCI1 to 0.10%
• Set 3: reduction of N310qci1 from n6->n4 did not lead to further reduction, result: 0.13%
VoLTE capable Rel. 9 UEs during test: >95% => Higher penetration would even improve result
69 © Nokia Solutions and Networks 2014
Nokia Internal Use
VoLTE Drop Call Optimization
Field Trial Results
• Target is to start early re-establishment procedure by UE before call drop, but not to trigger too
early re-establishements and therefore, increase the risk to drop the call by a failed re-estabishment
procedure itself
• Set 1: Default parameters are T310=2000ms and N310=n10 -> Network was already adapted to
T310=1000ms, N310=n6 which leads to an improved ERAB DR.
• Set 2: QCI1 specific T310qci1 reduction leads to earlier triggering of re-establishment procedure
by UE and therewith to a further improvement of ERAB QCI1 DR from 0.14% -> 0.10%
• Set 3: Further parameter adaptions to trigger re-establishment procedure by UE even earlier lead
to an increase of DR compared to previous setting (Set 2) -> increased amount of re-
establishement procedures finally lead to an increased DR as re-establishement procedure might
fail as well
- It is recommended to activate feature LTE1617 RLF triggered handover to improve re-
establiment success in overall.
Battery consumption:
THE CHALLENGE
Handset power consumption is generally minimized by integrating a VoLTE client into the modem
processor (chipset)
DRX (Discontinuous Reception) functionality uses sleep mode in the handset between VoLTE
packet receptions – eVTT profile further enhances battery savings
Current (mA)
- Native VoLTE
154
- VoIP (Viber) 150 131
129 125 121
• Without VoLTE optimized DRX
100
- VoLTE consumes up to 88% higher power than
3G CS call
50
- Viber consumed up to two times more power
than 3G CS call 0
3G CS 3G CS noDRX DRX DRX DRX Viber
• With VoLTE optimized DRX AMR-NB AMR-WB 20ms 40ms 40ms
6ms 6ms 4ms
- VoLTE has similar power consumption as 3G CS OnDur OnDur OnDur
call
• The current analysis of DRX problems indicate that in case of poor RF the DRX causes
additional dropped calls:
- These dropped calls could be caused by additional delays caused by DRX
- Measurement delays for handovers
- Measurement inaccuracies of CQI (reported CQI in DRX active state might not correctly reflect the
RF quality due to the DRX sleep state)
- Due to this the LA might not work accurately and fast enough to be able to react on changing CQI in
poor RF and UE might never hear the HO command
• The DRX feature can be improved so that it could be turned off in poor RF (based on
CQI) and turned on in case of improved RF (improving absolute CQI value)
• If UE has QCI-1 DRB and DRX was previously disabled due to Poor RF, and C-plane
receives new RL Status Indication for this UE indicating “GoodChannelQuality”, then C-
plane sends RRC Reconfiguration message to UE to re-install the DRX profile (i.e. re-
enable DRX) provided that other DRX feature add conditions (feature flag, configuration,
etc.) are satisfied
• CQI threshold for deactivation and activation need to be set according to network
performance
CQI CQI
DRX OFF 7-9
DRX OFF 9-11 Average CQI is 11 or
higher in the cluster and
therefore, CQI thresholds
needs to be set higher
• UE should be considered as high speed UE in case Doppler shift at eNB is higher than 400Hz
• LTE48 Support of High Speed Users feature improves the eNB UL reception performance for the high
speed users but does not bring any gain for the low speed user (Doppler shift less than 400 Hz)
• Because of the frequency offset estimation and the signal correction, the computation complexity and
the processing latency are increased at eNB - Therefore the feature activation should be a subject for
consideration during the network planning by the customer
• Table below shows exemplary calculations for different frequency bands:
• LTE48 Support of High Speed Users feature can be activated by setting the parameter
prachHsFlag = ‘true’ (requires object locking)
- The range of allowed rootSeqIndex values becomes limited (restricted set) and the
number of PRACH sequences which can be generated from each root sequence is no
longer fixed -> RSI re-planning is required.
- hsScenario must be configured to ‘scenario1’ or ‘scenario 3’ dependently on the
deployment scenario - Scenario 1 (open space scenario) and scenario 3 (tunnel
scenario) defined by 3GPP
- ulCombinationMode must be set to ‘MRC’, i.e. LTE1402 Intra eNB UL CoMP cannot
be used.
Total Att LTE_753A CSSR LTE_5218C SR LTE_5220A Stp ATT LTE_5116A Data stp SR LTE_5003A
Data SR LTE_5117A
100.00 20,000
98.00 100.00 100,000
15,000
98.00 80,000
96.00
10,000 96.00 60,000
94.00
94.00 40,000
92.00 5,000
92.00 20,000
90.00 0 90.00 0
before after
04.28.00
04.28.06
04.28.12
04.28.18
04.29.00
04.29.06
04.29.12
04.29.18
04.30.00
04.30.06
04.30.12
04.30.18
05.01.00
05.01.06
05.01.12
05.01.18
04.30.01
04.30.08
04.30.15
04.28.00
04.28.07
04.28.14
04.28.21
04.29.04
04.29.11
04.29.18
04.30.22
05.01.05
05.01.12
05.01.19
Stp Att LTE_5118A eRAB Performance DR LTE_5025C
Stp SR LTE_5017A
8.00
Normal, NW view LTE_5024C 6.00
100.00 40,000 4.00
2.00
95.00 20,000 0.00
04.28.00
04.28.07
04.28.14
04.28.21
04.29.04
04.29.11
04.29.18
04.30.01
04.30.08
04.30.15
04.30.22
05.01.05
05.01.12
05.01.19
90.00 0
04.2…
04.2…
04.2…
04.2…
04.2…
04.2…
04.2…
04.3…
04.3…
04.3…
04.3…
05.0…
05.0…
05.0…
Intra ENB HO Prep att LTE_5123A Inter ENB HO Prep att LTE_5126A
04.30.08
04.30.15
04.30.22
05.01.05
05.01.12
05.01.19
04.28.00
04.28.06
04.28.12
04.28.18
04.29.00
04.29.06
04.29.12
04.29.18
04.30.00
04.30.06
04.30.12
04.30.18
05.01.00
05.01.06
05.01.12
05.01.18
83 © Nokia Solutions and Networks 2014
High Speed Train Optimization
LTE2445: Combined Supercell
• High speed users handovers occur very frequently causing a large amount of signaling.
Moreover, the train is running between cell centers and cell edges, which significantly
impacts data rates even causing service drops.
• LTE2445 Combined Supercell feature
reduces drastically the handover
frequency in high speed scenarios.
- The UE can move seamlessly between
subcells, without interruption by a RACH
procedure due to cell change as with
normal cells
- 6 RRH support allows for extended
supercell coverage
RSRP
RSRQ
RRC
Re-establishment
VoLTE Packet
85
Re-esta
© Nokia Solutions and Networks 2014
Re-esta Re-esta Re-esta
86
WCDMA Voice
should be used
when train goes
through a tunnel
0
10
30
50
60
20
40
2014.11.18:06.00
2014.11.18:13.00
2014.11.18:20.00
2014.11.19:09.00
High Speed Train Optimization
2014.11.19:16.00
2014.11.19:23.00
2014.11.20:12.00
2014.11.20:19.00
2014.11.26:08.00
2014.11.26:15.00
2014.11.26:22.00
2014.11.27:11.00
2014.11.27:18.00
2014.11.28:07.00
2014.11.28:14.00
2014.11.28:21.00
2014.11.29:10.00
2014.11.29:17.00
Drop Rate (ADR) [%]
2014.11.30:06.00
2014.11.30:13.00
2014.11.30:20.00
2014.12.01:09.00
2014.12.01:16.00
LTE
2014.12.01:23.00
WCDMA
2014.12.02:12.00
Lower
• LTE drop rate is around 38% but WCDMA’s drop rate is lower than LTE in tunnel sites.
drop rate
High Speed Train Optimization
Possible design concept
• To make UEs enter tunnels continuously without drop, our new design forces VoLTE UEs
to move to WCDMA by SRVCC in tunnel adjacent sites and tunnel sites.
LTE
WCDMA
AMR AMR
xxx
SRVCC/HO command