Professional Documents
Culture Documents
Nokia Voltetraining2017 Nampptx
Nokia Voltetraining2017 Nampptx
VoL
oLTE
TE Trai
aini
ning
ng
Detailed Analysis for Radio
13 March 2017
• VoL
VoLTE
TE Mobility
Mobi lity • VoLTE Call Flow Analysis
• VoL
VoLTE
TE layering
layer ing • Registration procedure
• SRVCC thresholds • Mobile originated VoLTE call
• Mobile terminated VoLTE call
• SRVCC to 3G
)
thus, the weight of setups
) 250 000 #
(
% 99.60
( s
t
attempted under poor radio
e
t p
a
R 99.50 m
200 000 e
conditions is increased
s t
t
s
e A
c
c 99.40 1
I
- If a handover becomes
u C
S 150 000 Q necessary during E-RAB Setup,
99.30 the eNB may interrupt the
100 000
ongoing E-RAB Setup procedure
99.20
as specified in 36.413 (chapter
50 000
99.10 8.2)
99.00 0
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
. 2
.
5 7 9 1 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2
2
. 2
. 2
. 3
. 0
. 0
. 0
. 0
. 1
. 1
. 1
. 1
. 1
. 2
. 2
. 2
. 2
. 2
. 3
. 0
. 0
. 0
. 0
. 1
. 1
. 1
. 1
. 1
. 2
. 2
.
8 8 8 8 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1
• 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 i nitiated
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 fail ed 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
PatchSwitchRequest
Create Bearer Response Cause: Temporarily Rejected due to Handover Procedure in
(failure) Progress
SIP: 503 Service Unavailable
SIP:INVITE
SIP: TRYING
R
PatchSwitchRequest e
Create Bearer Response Cause: Temporarily Rejected due to Handover Procedure in t
r
a
(failure) Progress n
Create Session Request (QCI5) s
m
Modify Bearer Request
i
s
s
Modify Bearer Response i
o
Create Session Response n
Patch Switch Request Ack
E-UTRAN E-RAB QCI1 with data in the queue drop ratio (LTE_5571f) =
100*sum( E RAB_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)
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
5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1 2 3 4 5 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1 2 3 4 5
1
- 1
- 1
- 1
- 1
- 2
- 2
- 2
- 2
- 2
- 2
- 2
- 2
- 2
- 2
- 3
- 3
- 0
- 0
- 0
- 0
- 0
- 1
- 1
- 1
- 1
- 1
- 2
- 2
- 2
- 2
- 2
- 2
- 2
- 2
- 2
- 2
- 3
- 3
- 0
- 0
- 0
- 0
- 0
-
5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 6 6 6 6 6 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 6 6 6 6 6
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
• SRVCC might fail due to size of "source to transparent c ontainer" 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 toUTRAN SRVCC Inter RAT HOUTRAN 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% issue in MSS not sending proper
600 users - 10 MHz 16 000
cause code for successful
80
14 000 SRVCC HO and thus, SRVCC
75 success counter is not correctly
) 12 000 )
#
( incremented.
%
( 70 s
t
s
s 10 000 p
e
c
c 65
u
m
e
t
• IMS network was not
S t
8 000 A
60
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
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
4
1
0
2
-115 dBm.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 7 9 1 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2
2 2 2 3 0 0 0 0 1 1 1 1 1 2 2 2 2 2 3 0 0 0 0 1 1 1 1 1 2 2
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 8 8 8 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1
• SRVCC causes always a short audio interruption (<300ms) and therefore, number of
SRVCC attempts should be reduced by lowering triggering threshold as much as possible
→ VoLTE service area is increased.
- SRVCC threshold and redirection thresholds should be enough far apart to avoid call drop during SRVCC.
• 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 i mprovement 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
LTEnetworkmay TD-LTEmaynot
nothavenothave beallowedtobe
Trafficsteeringis
contiguous usedforVoLTE
handledbyidleor
coverage serviceaccording
connectedmode
VoLTEisenabled togovernment
loadbalancing
acrossallthe regulationsin
features
carrierstoprovide somecountries
VoLTEtrafficmay
thebestpossible nothavea
service dedicatedlayer
accessibility
• 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 user s 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 inter-RAT cell releselection from WCDMA towards a higher If no suitable LTE cell found, then reselection to WCDMA will
priority LTE will be always triggered while a LTE neighboring cell happen when a neighbouring UMTS cell RSCP is better than
coverage is better than A djL Qr xlevmi nE UTR A + AdjL Thr es hig h. qRxLevMinUtr + UtraFrqThrL
The lower threshold can be applied in case of the strategy is The target UMTS cell must also have a CPICH Ec/Io >
capture more traffic to LTE. qQualMinUtra.
• 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)
<Change information classification in footer>
a2RedirectQci1 LNCEL A2 based redirect for VoLTE calls 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.
ServicebasedMobilityTrigger DedicatedMobilityThresholdsforSRVCC
Servicebasedmobilitythresholds SRVCCTriggerEnhancements
DedicatedVoLTEinter-frequencytarget SRVCCduetoAdmissionControlRejection
frequencylist RSRQbasedB2
QCI1EstablishmentTriggeredProtection VoLTEqualitytriggeredSRVCCtoGSM
Timer
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 ).
Note: If configured QCI1 specific T310 and N310 are equal to legacy values, eNB will not include rlf-TimersAndConstants IE.
Maximumnumberof
N311 LNCEL On-line 0:n1;1:n2;2:n3;3:n4;4:n5;5:n6;6:n8;7:n10 n1 n1 n1
in-syncindications
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
n6 ->n4 did not lead to further
furt her reduction, result:0.13%
result: 0.13%
VoLTE capable Rel. 9 UEs during test: >95% => Higher penetration would even improve result
69 © Nokia Solutions and Networks 2014
VoLTE Drop Call Optimization
Field Trial Results
Battery consumption:
E
G VoLTE users have a high battery 40 ms 1 ms
N
E consumption due to a long call session
L time compared to data users
L
A
H Voice application running in the handset
C
application processor requires a lot of
E
H power Sleep mode VoLTE packets
T
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
• The current analysis of DRX problems indicate that in case of poor RF the DRX causes
additional dropped calls:
- These
These dro
droppe
pped
d call
calls
s coul
could
d be
be cause
caused
d by
by additional delays caused by DRX
- Meas
Measur
urem
emen
entt de
dela
lay
ys for handovers
- Measur
Meas urem
emenentt in
inac
accu
cura
raci
cies
es of CQI (reported CQI in DRX active state might not correctly reflect the
RF quality due to the DRX sleep state)
- Due to th
thiis th
the
e 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
i mproved RF (improving absolute CQI value)
• If UE has QCI-1 DRB and DRX was previously disabled due to Poor RF RF,, and C-plane
receives new RL Status Indication for this UE indicating “ GoodChannelQuality
GoodChannelQuality”,
”, then C-
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:
2600 >80
• 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
0 6 2 8 0 6 2 8 0 6 2 8 0 6 2 8 0 7 4 1 4 1 8 1 8 5 2 5 2 9
0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 2 0 1 1 0 0 1 2 0 1 1
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 8 8 8 9 9 9 9 0 0 0 0 1 1 1 1 8 8 8 8 9 9 9 0 0 0 0 1 1 1
2 2 2 2 2 2 2 2 3 3 3 3 0 0 0 0 2 2 2 2 2 2 2 3 3 3 3 0 0 0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 4 4 4 4 4 4 4 4 4 4 4 5 5 5 5 4 4 4 4 4 4 4 4 4 4 4 5 5 5
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Intra ENB HO Prep att LTE_5123A Inter ENB HO Prep att LTE_5126A
• 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.
RSRP
RSRQ
RRC
Re-establishment
VoLTE Packet
WCDMA Voice 40
should be used 30
Lower
when train goes 20
drop rate
through a tunnel 10
. . . . . . . . . . . . . . . . . . . . . . . . .
: : : : : : : : : : : : : : : : : : : : : : : : :
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
LTE
WCDMA
xxx
SRVCC/HO command