NETWORK ENGINEERING

LTE3443
VoLTE quality triggered SRVCC to GSM
SR001658 LTE 18 new feature implementation for SRAN
Network Engineering Information
• Doc ID: 5ac5dfeede26750012b75e6c
• Version 2.1
• Marek Brylka
• Status: Approved
• 05-04-2018

Please, always check the latest version of NEI slides.

1 © Nokia 2018
Disclaimer

• Please note that the NEI materials are for internal use only. If they shall be used as a
source for the customer presentation, it is mandatory to align the contents with the
Product Management and/or local sales teams at first!
• The results of simulations shown in this presentation are examples only. They
demonstrate trends (not absolute values) expected after feature activation. The
presented simulations should be analyzed with respect to the assumptions taken.
They may differ from results achievable in real networks.
• This NEI slide deck reflects the state of the feature/solution as it is at the moment of
the NEI slide deck release and is being updated up to C5 (release available) milestone.

2 © Nokia 2018 Nokia Internal Use

Revision history and metadata

Document ID: 5ac5dfeede26750012b75e6c

Document location: https://webnei.emea.nsn-net.net/#/webnei/5ac5dfeede26750012b75e6c/1
Organization: MN CS Network Engineering

Version Description of Changes Date Doc Owner Doc Status Reviewed by Approver Approval Date

0.1 Draft for review 10-01-2017 Marek Brylka DRAFT Katarzyna

Rybianska, Thomas
Stark, Lv Dz, Piotr
Lechowicz

0.2 After internal and external 17-01-2017 Marek Brylka

review ready for approval;
comments included

1.0 Version for training 17-01-2017 Marek Brylka CONDITIONALLY Jacek Kotwinski Jacek Kotwinski * 18-01-2017
APPROVED

2.0 Update of the materials by 11-01-2018 Marek Brylka APPROVED Jacek Kotwinski Jacek Kotwinski 11-01-2018
information provided in
FL18/TL18; counters and KPIs

2.1 SRAN feature name added 05-04-2018 Marek Brylka

* approved as preliminary version for first NEI training focused on Chinese market / TL16A MP, material update planned in FL18/TL18 timeframe)

3 © Nokia 2018 Nokia Internal Use

Open Issues

Item Description Comments

4 © Nokia 2018 Nokia Internal Use

LTE3443 VoLTE quality triggered SRVCC to GSM*
Table of contents

Introduction Technical Inter – Benefits and Configuration

Details dependencies Gains Management
Motivation and Feature Detailed Functionality Simulation, Lab and Parameters and
Interdependencies with
Overview Description Field Findings Parameterization
other features and
functions Scenarios
1

Deployment Performance
Aspects Aspects
Activation, Counters and KPIs,
Configuration Examples, Feature Impact Analysis
Fault Mgmt, Trial Area and Verification

*No difference in implementation for SRAN18 (status for 05.04.2018)

Please track upcoming related release notes to get familiarized with the latest solutions
5 © Nokia 2018 Nokia Internal Use
LTE3443 VoLTE quality triggered SRVCC to GSM

Introduction

Table of contents

6 © Nokia 2018
Introduction
LTE3443 VoLTE quality triggered SRVCC to GSM

Before After

• From LTE network perspective, SRVCC to • Degradation of voice quality, detected by

GSM is possible if RSRP or RSRQ of serving serving eNB, due to:
cell is poor • gaps in DL PDCP packets
• gaps in UL PDCP packets
• poor UL residual BLER
is a new trigger for SRVCC to GSM

• In this case the decision for triggering of • In this case the decision for triggering of
SRVCC is based on event B2 measurements SRVCC is based on event B1 measurements
reported by the UE reported by the UE

7 © Nokia 2018
Nokia Internal Use
LTE3443 VoLTE quality triggered SRVCC to GSM

Section Name
Technical Details

Table of contents

8 © Nokia 2018
Technical Details Sales information
Dependency Table BSW/ASW ASW

Release information
Release/version RL release eNodeB NetAct
FDD LTE FDD-LTE 18 FL18 NetAct 18.2
TDD LTE TDD-LTE 18 TL18 NetAct 18.2
Flexi Zone Micro (FZM/FZP) FDD-LTE 18 FLF18 NetAct 18.2
Flexi Zone Controller (FZC) N/A N/A NetAct 18.2
Single RAN SRAN18A SBTS18A TBD

Release information – general

HW & IOT HW requirements MME SAE GW UE Specified by 3GPP
FSMF/FZM/ 3GPP R8 UE
- - - -
AirScale SM capabilities

9 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• SRVCC is a procedure which assures voice service continuity in CS domain of 2G/3G RATs in case VoLTE call can
not be maintained in LTE PS domain any more
• SRVCC is only possible if supported both by the network and by the UE terminal capabilities (Feature Group
Indications)

• If FGI9 and FGI23 are set to 1, the UE supports SRVCC to GERAN based on event B2 measurements;
• If additionally FGI15 is to 1, SRVCC to GERAN is also possible based on event B1 measurements
Index of Definition Notes
indicator
9 - EUTRA RRC_CONNECTED to GERAN GSM Dedicated handover - related to SR-VCC
- can only be set to 1 if the UE has set bit
number 23 to 1
15 - Measurement reporting event: Event B1 – Neighbour > - can only be set to 1 if the UE has set at least
threshold for GERAN, 1xRTT or HRPD, if the UE has set bit one of the bit number 22, 23, 24, 26 or 39 to 1.
number 23, 24 or 26 to 1, respectively

23 - GERAN measurements, reporting and measurement

reporting event B2 in E-UTRA connected mode

10 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Till FL18/TL18, in Nokia portfolio SRVCC to GSM RSRP/RSRQ RSSI

is supported/enhanced by set of features:
Event B2 conditions for
- LTE873 SRVCC to GSM SRVCC to GSM met

- LTE2572 RSRQ based B2 b2Threshold1GERAN

b2Threshold1GERANQci1 b2Threshold2RssiGERAN
- LTE64 VoLTE dedicated thresholds b2Threshold1RsrqGERAN b2Threshold2RssiGERANQci1
b2Threshold1RsrqGERANQci1
- LTE3127 SRVCC to GSM measurement
optimization hysB2ThresholdGERAN
hysB2ThresholdRsrqGERAN
• activation of GERAN measurements for SRVCC, disables all
other LTE inter-freq/inter-RAT measurements, active so far

- LTE3290 SRVCC trigger enhancements

b2TimeToTriggerGERANMeas
• SRVCC is avoided in alerting phase of VoLTE call setup b2TimeToTriggerRsrqGERANMeas

• Poor RSRP or RSRQ on LTE side and sufficient

RSSI on GERAN side, defined by 3GPP as event
Trigger point for SRVCC to GSM
B2 conditions and reported by the UE, is a
trigger for SRVCC to GSM procedure

11 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• With LTE3443, activated by LNBTS:actVoLteQualSRVCCtoGsm = true, Call flow degradation

the trigger for SRVCC, from serving eNB point of view, may be lack of for voice packets in DL or UL
correctly transmitted/received packets for voice (QCI1) detected by eNB PDCP or
for voice packets in UL packets
- in DL/UL, detected by PDCP layer (PDCP PDU gaps)
detected by eNB MAC
- in UL, detected by MAC layer (high UL residual BLER)

• If the serving eNB detects above mentioned voice service quality Activation of event B1
degradation, event B1 measurements are activated for VoLTE user conditions for mobility to GERAN
- such mechanism is possible even if RSRP/RSRQ of serving LTE cell is
satisfying; event B1 measurement are activated because it is enough
to check whether the target GERAN cell has sufficient RSSI level to
maintain the voice call in CS domain UE sends Measurement Report
with event B1 and eNB triggers
SRVCC towards GSM procedure
• Only if event B1 conditions are reported by the UE, the eNB triggers
SRVCC to GSM procedure

12 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Event B1 conditions which comes with LTE3443, reuse parameters (threshold for RSSI, hysteresis, TimeToTrigger,
report interval) applicable for event B2 and introduced by LTE873, LTE64
• reportConfig for event B1 introduced by LTE3443
ReportConfigInterRAT
VoLTE quality triggered
SRVCC
Parameter name set value length basic type
> triggerType = event Sequence
> > eventId =eventB1 Sequence
> > > b1-Threshold single ThresholdGERAN
MMI parameter
LNHOG:b2Threshold2RssiGERAN/
> > > > ThresholdGERAN LNHOG:b2Threshold2RssiGERANQci1 single INTEGER(0..63)
MMI parameter
> > hysteresis LNHOG:hysB2ThresholdGERAN single INTEGER(0..30)
ENUMERATED{ms0,ms40,ms64,ms80,ms100,ms12
MMI parameter (restricted up to ms256) 8,ms160,ms256,ms320,ms480,ms512,ms640,ms1
> > timeToTrigger LNHOG:b2TimeToTriggerGERANMeas single 024,ms1280,ms2560,ms5120}
> maxReportCells = maxCellReport single INTEGER(1..maxCellReport)
ENUMERATED{ms120,ms240,ms480,ms640,ms102
MMI parameter 4,ms2048,ms5120,ms10240,min1,min6,min12,mi
> reportInterval LNHOG:reportIntervalGERAN single n30,min60,spare3,spare2,spare1}

> reportAmount infinity single ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}
13 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM VQ-TrON – Voice Quality Trigger ON
VQP_DL_ON – Voice Quality Problem ON for DL
VQP_UL_ON – Voice Quality Problem ON for UL

• Decision to activate event B1 measurements for SRVCC to GSM

C-plane conditions Trigger Combination

• QCI1 Bearer established VQ-TrON
Function
• UE capabilities supporting SRVCC to GSM (Voice Quality
If for a given VoLTE
Trigger ON)
• EPC supporting SRVCC UE, supporting reported by
• no sidelink* session active for the UE SRVCC to GSM, there Trigger
• etc. is at least one Voice Combination
Quality Problem Function results
(VQP) type detected, in event B1
then event B1 measurements
PDCP PDU UL/DL gap detection VQP ON Flow Control VQP ON
measurements may (SRVCC to GSM)
be activated activation for
the UE
VQP_DL_ON or
VQP_BLER ON VQP_UL_ON or
MAC UL residual BLER conditions (based on
LTE2493) VQP_BLER_ON

*sidelink refers to functionality introduced by LTE2612 ProSe Direct Communications for Public Safety

14 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Decision to activate event B1 measurements for SRVCC to GSM -> PDCP trigger

C-plane conditions Trigger Combination

• QCI1 Bearer established VQ-TrON
Function
• UE capabilities supporting SRVCC to GSM (Voice Quality
If for a given VoLTE
Trigger ON)
• EPC supporting SRVCC UE, supporting reported by
• no sidelink* session active for the UE SRVCC to GSM, there Trigger
• etc. is at least one Voice Combination
Quality Problem Function results
(VQP) type detected, in event B1
then event B1 measurements
PDCP PDU UL/DL gap detection VQP ON Flow Control VQP ON
measurements may (SRVCC to GSM)
be activated activation for
the UE
VQP_DL_ON or
VQP_BLER ON VQP_UL_ON or
MAC UL residual BLER conditions (based on
LTE2493) VQP_BLER_ON

*sidelink refers to functionality introduced by LTE2612 ProSe Direct Communications for Public Safety

15 © Nokia 2018
Nokia Internal Use
 PDCP DL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• PDCP PDU gap detection for DL packets in eNB - PDCP SDU

VQP ON
eNB UE

- Every PDCP PDU in DL forwarded towards RLC

layer has its timestamp assigned by PDCP layer
- Timestamp is added to PDCP PDU when header
with SN is added to the PDCP SDU

Timestamp added

PDCP PDU
16 © Nokia 2018
Nokia Internal Use
 PDCP DL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• PDCP PDU gap detection for DL packets in eNB -

VQP ON

PDCP SDU

PDCP SDU

PDCP SDU

PDCP SDU

PDCP SDU

PDCP SDU

PDCP SDU

PDCP SDU

PDCP SDU

PDCP SDU

PDCP SDU
- IP packets for voice, which come to PDCP layer …
as PDCP SDUs, are generated with periodicity
T [ms]
of 20ms 20ms 20ms … …

- As result it is expected that in general the

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU
timestamp for each consecutive PDCP PDU will
differ by about 20ms (as indicated on previous …
slide timestamp is added to PDCP PDU) T [ms]
…

Timestamp X - 40ms
Timestamp X - 60ms

Timestamp X - 20ms

Timestamp X
17 © Nokia 2018
Nokia Internal Use
 PDCP DL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• PDCP PDU gap detection for DL packets in eNB -

VQP ON PDCP PDU discarded from the PDCP
buffer before sending to the RLC
- PDCP PDUs before sending to RLC layer are layer or lost due to no HARQ ACK
stored in the buffer, however it is required that
the eNB discards packets which get stuck in
the buffer for too long

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU
- eNB removes the voice packets from the DL
PDCP buffer after time which is impacted by …

parameter LNBTS:pdcpProf101:tDiscard … T [ms]

- eNB removes the packets from the buffer also

Timestamp X - 40ms
Timestamp X - 60ms

Timestamp X - 20ms
if maximum number of HARQ retransmissions
in DL is reached but no HARQ ACK is received by Not poor RSRP or RSRQ of serving
cell but lack of correctly

Timestamp X
the eNB
transmitted packets which degrade
- All this leads to voice packet gap in DL, so in voice call quality perceived by end
transmission from eNB towards the UE user is a trigger to leave LTE side via
SRVCC

18 © Nokia 2018
Nokia Internal Use
 PDCP DL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• PDCP PDU gap detection for DL packets in eNB -

VQP ON PDCP PDUs PDCP PDUs
sent sent
- With LTE3443 the eNB controls the timestamp successfully successfully
delta between each two consecutively
successfully transmitted PDCP PDUs for a given
VoLTE call

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU
…
- If timestamp delta is higher than T [ms]
VOLTEQUALPR:badQualityDLGapThres then
the VQP ON (Voice Quality Problem ON)

Timestamp Z
Timestamp X
Timestamp Y
message is sent to the Flow Control functional
block

Timestamp Y - Timestamp X < VOLTEQUALPR:badQualityDLGapThres -> no Voice Quality Problem detected Flow
control
Timestamp Z - Timestamp Y > VOLTEQUALPR:badQualityDLGapThres -> Voice Quality Problem detected VQP ON
message

19 © Nokia 2018
Nokia Internal Use
 PDCP DL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• PDCP PDU gap detection for DL packets in eNB -

VQP ON PDCP PDUs PDCP PDUs
sent to the sent to the
- It could be that some of the PDCP PDUs are RLC layer RLC layer
discarded by the eNB or lost from the
transmitting buffer but the timestamp delta
between consecutively correctly transmitted

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU
PDCP PDUs is still lower than period defined by
VOLTEQUALPR:badQualityDLGapThres …

- In this case no VQP problem is detected and no T [ms]

VQP ON message is sent to the Flow Control

Timestamp Y
Timestamp X
box

Timestamp Y - Timestamp X < VOLTEQUALPR:badQualityDLGapThres

-> no Voice Quality Problem detected even if some packets in between are discarded

20 © Nokia 2018
Nokia Internal Use
 PDCP DL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM
VQP ON VQP OFF
• Recovery from VQP ON to VQP OFF for DL voice
packets PDCP PDUs
sent to the
- VQP OFF message is sent to the Flow Control RLC layer
functional block, if serving eNB detects that all
PDCP PDUs transmitted to the RLC layer within
time window defined by

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU
PDCP PDU
VOLTEQUALPR:goodQualityGapThres have
consecutive SNs (Sequence Numbers) …

T [ms]

Timestamp Y
Timestamp X

PDCP SDU
Timestamp Y - Timestamp X > VOLTEQUALPR:goodQualityGapThres
Flow
-> if all PDCP PDUs with timestamps between Timestamp X and Timestamp Y have control

SN
consecutive SNs in their PDCP PDU headers eNB takes the decision no Voice Quality VQP OFF

HEADER
Problem occurs any more so the VQP OFF is sent towards Flow Control block message

21 © Nokia 2018
Nokia Internal Use
 PDCP UL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• PDCP PDU gap detection for UL packets in eNB - PDCP SDU

VQP ON
- For UL direction, for each PDCP PDU coming UE eNB

from RLC layer, eNB assigns timestamp

- Similarly to DL case, for good transmission
conditions it is expected that the UL PDCP
PDUs will arrive at the eNB with periodicity of
about 20ms

Timestamp added

PDCP PDU
22 © Nokia 2018
Nokia Internal Use
 PDCP UL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• PDCP PDU gap detection for UL packets in eNB -

VQP ON
- It could be that packets on UE side are
discarded from PDCP buffer according to 3GPP
standardized mechanism (3GPP 36.323, 5.4)
- In Nokia product, PDCP discard on UE side for
voice packets is controlled by already
mentioned LNBTS:pdcpProf101:tDiscard
parameter
- The value of LNBTS:pdcpProf101:tDiscard is
provided to the UE with the help of
RRC:RRCConnectioneReconfiguration
message at establishment of QCI1 DRB

23 © Nokia 2018
Nokia Internal Use
 PDCP UL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• PDCP PDU gap detection for UL packets in eNB - VQP

ON UL PDCP PDUs missing on
eNB due to discarding on
- If packets will be discarded on UE side due to UE side or no HARQ ACK
discardTimer expiry, then at serving eNB this will be
reflected by some gap in incoming UL voice PDCP
PDUs stream

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU
- The packets are also removed from UE PDCP buffer
if maximum number of HARQ retransmission is …

reached but no HARQ ACK is received by the UE T [ms]

- When eNB PDCP detects the gap in received SNs

Timestamp X - 40ms
Timestamp X - 20ms
Timestamp X

Timestamp Y
(Sequence Numbers) of PDPC PDUs and the delta
between timestamps for successfully received
PDCP PDUs is higher than
VOLTEQUALPR:badQualityULGapThres the VQP
ON (Voice Quality Problem ON) message is sent to Flow
the Flow Control functional box control
VQP ON
Timestamp Y - Timestamp X > VOLTEQUALPR:badQualityULGapThres -> Voice Quality Problem detected message

24 © Nokia 2018
Nokia Internal Use
 PDCP UL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM
VQP ON VQP OFF
• Recovery from VQP ON to VQP OFF for UL voice
packets PDCP PDUs
received from
- VQP OFF message is sent to Flow Control the RLC layer
functional block if serving eNB detects that all
PDCP PDUs received from RLC layer within time
window defined by

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU

PDCP PDU
PDCP PDU
VOLTEQUALPR:goodQualityGapThres have
consecutive SNs (Sequence Numbers) …

T [ms]

Timestamp Y
Timestamp X

PDCP SDU
Timestamp Y - Timestamp X > VOLTEQUALPR:goodQualityGapThres
Flow
-> if all PDCP PDUs with timestamps between Timestamp X and Timestamp Y have control

SN
consecutive SNs in their PDCP PDU headers eNB takes the decision no Voice Quality VQP OFF

HEADER
Problem occurs any more so the VQP OFF is sent towards Flow Control message

25 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Monitoring split for DL and UL packets

- The operator may decide whether the packet gaps detected by PDCP layer of serving eNB shall be monitored for
UL or for DL or for both directions
- This concept is realized just by configuring or not of mentioned parameters badQualityDLGapThres,
badQualityULGapThres from the MOC VOLTEQUALPR which are of type optional

26 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Avoiding of C-Plane overload due to VQP status change

- The change of VQP (Voice Quality Problem) from OFF to ON, and vice versa, for both DL and UL shall lead to
activation/deactivation of event B1 measurements for the UE
- Frequent changes of VQP status per UE, for many VoLTE users served by the same LTE cell may significantly
impact C-Plane processing
- To minimize C-Plane overload, the trigger condition indications coming from many users are queued in Flow
Control functional block and sent to the Trigger Combination Function in a predefined rate

The change of VQP status is

Flow control
sent for max 5 VoLTE UEs Trigger Combination Function
with periodicity of 100ms
Collects the list of VQP ON/OFF is an eNB block which commands to
per each VoLTE UE activate/deactivate event B1 for
SRVCC to GERAN for e given UE,
based on received VQP status

27 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Avoiding of C-Plane overload due to VQP status change

Flow Control sends towards PDCP

Trigger Combination Function VQP ON VQP OFF VQP ON VQP OFF VQP ON VQP OFF
VQP reports
- with periodicity of 100ms Added Removed Added Added Removed Added
Flow to the from the to the to the from the to the
- one report covers status for Control list list list list list list
max 5 UEs

Initial conditions: 100ms 100ms 100ms 100ms Reporting occasions

1. EPS Bearer with QCI1 between FC and TCF

established Trigger Notification Notification

2. VQP OFF Combination sent to the sent to the
TCF
3. no event B1 for SRVCC to Function TCF

GSM activated
4. Example for VQP states Event B1 Event B1
activation deactivation
detected for only one UE
28 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Decision to activate event B1 measurements for SRVCC to GSM

C-plane conditions Trigger Combination

• QCI1 Bearer established VQ-TrON
Function
• UE capabilities supporting SRVCC to GSM (Voice Quality
If for a given VoLTE
Trigger ON)
• EPC supporting SRVCC UE, supporting reported by
• no sidelink* session active for the UE SRVCC to GSM, there Trigger
• etc. is at least one Voice Combination
Quality Problem Function results
(VQP) type detected, in event B1
then event B1 measurements
PDCP PDU UL/DL gap detection VQP ON Flow Control VQP ON
measurements may (SRVCC to GSM)
be activated activation for
the UE
VQP_DL_ON or
VQP_BLER ON VQP_UL_ON or
MAC UL residual BLER conditions (based on
LTE2493) VQP_BLER_ON

*sidelink refers to functionality introduced by LTE2612 ProSe Direct Communications for Public Safety

29 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Decision to activate event B1 measurements for SRVCC to GSM -> MAC trigger

C-plane conditions Trigger Combination

• QCI1 Bearer established VQ-TrON
Function
• UE capabilities supporting SRVCC to GSM (Voice Quality
If for a given VoLTE
Trigger ON)
• EPC supporting SRVCC UE, supporting reported by
• no sidelink* session active for the UE SRVCC to GSM, there Trigger
• etc. is at least one Voice Combination
Quality Problem Function results
(VQP) type detected, in event B1
then event B1 measurements
PDCP PDU UL/DL gap detection VQP ON Flow Control VQP ON
measurements may (SRVCC to GSM)
be activated activation for
the UE
VQP_DL_ON or
VQP_BLER ON VQP_UL_ON or
MAC UL residual BLER conditions (based on
LTE2493) VQP_BLER_ON

*sidelink refers to functionality introduced by LTE2612 ProSe Direct Communications for Public Safety

30 © Nokia 2018
Nokia Internal Use
 MAC UL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• UL residual BLER
- LTE2493 Enhanced VoLTE Performance Monitoring introduced among others measurements of VoLTE uplink
final residual BLER as a metric of voice quality.

- ulQci1ResBler = 100 * M8026C269 / M8026C270

where:
• M8026C270 provides the total number of initial HARQ transmissions for the QCI1 (VoLTE) bearer in the uplink
• M8026C269 provides the number of failed TB transmissions after the maximum number of HARQ
retransmission count for the QCI1 (VoLTE) bearer in the uplink

• LTE3443 re-uses the LTE2493 input data, in order to determine the final residual UL BLER (ulQci1ResBler ) and take
the decision whether this BLER indicates good or bad Voice Quality
- Residual UL BLER as defined by LTE2493 is evaluated with periodicity of 10240ms
- For LTE3443 Residual UL BLER value is evaluated with a periodicity of 500ms.

31 © Nokia 2018
Nokia Internal Use
 MAC UL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• High UL residual BLER detection ulQci1ResBler [%]

- If ulQci1ResBler, measured for VoLTE user
is higher than
VOLTEQUALPR:badQualityRBlerThres and
these conditions are valid for
VOLTEQUALPR:rBlerCondTimeToTrigger VOLTEQUALPR:badQualityRBlerThres
then such UE is added to the list of VoLTE
VOLTEQUALPR:goodQualityRBlerThres
users for which MAC layer sends
VQP_BLER ON to the Trigger Combination
Function 500 1000 1500 2000 2500 3000
T [ms]

VOLTEQUALPR: rBlerCondTimeToTrigger = 1s (as an example)

UE is a candidate for reporting VQP_BLER ON

Note: parameter range for
VOLTEQUALPR:rBlerCondTimeToTrigger to Trigger Combination Function
is 0…3s, step 0.5s

32 © Nokia 2018
Nokia Internal Use
 MAC UL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Low UL residual BLER detection ulQci1ResBler [%]

- If ulQci1ResBler, measured for VoLTE user
is lower than
VOLTEQUALPR:goodQualityRBlerThres
and these conditions are valid for
VOLTEQUALPR:rBlerCondTimeToTrigger VOLTEQUALPR:badQualityRBlerThres
then such UE is added to the list of VoLTE
VOLTEQUALPR:goodQualityRBlerThres
users for which MAC layer sends
VQP_BLER OFF to the Trigger
Combination Function 500 1000 1500 2000 2500 3000
T [ms]

VOLTEQUALPR: rBlerCondTimeToTrigger = 1s (as an example)

UE is a candidate for reporting VQP_BLER OFF

Note: parameter range for
VOLTEQUALPR:rBlerCondTimeToTrigger to Trigger Combination Function
is 0…3s, step 0.5s

33 © Nokia 2018
Nokia Internal Use
 MAC UL
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• UL residual BLER reporting to the

Trigger Combination Function
- Every MAC VQP status change for
MAC UE1 UE2 UE3
VoLTE user, places such UE on the
list which is inspected by the eNB
VQP_BLER ON
- MAC layer reports the detected VQP_BLER OFF
changes to Trigger Combination VQP_BLER OFF

Function with the periodicity of 100ms 100ms 100ms T [ms]

100ms
Trigger
- Per one report the status of only Combination
one VoLTE user may be sent Function

MAC sends towards Trigger Event B1 Event B1 Event B1

activation deactivation deactivation
Combination Function VQP reports possible possible possible
- with periodicity of 100ms
- one report covers status for 1 UE

34 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Decision to activate event B1 measurements for SRVCC to GSM

C-plane conditions Trigger Combination

• QCI1 Bearer established VQ-TrON
Function
• UE capabilities supporting SRVCC to GSM (Voice Quality
If for a given VoLTE
Trigger ON)
• EPC supporting SRVCC UE, supporting reported by
• no sidelink* active for the UE SRVCC to GSM, there Trigger
• etc. is at least one Voice Combination
Quality Problem Function results
(VQP) type detected, in event B1
then event B1 measurements
PDCP PDU UL/DL gap detection VQP ON Flow Control VQP ON
measurements may (SRVCC to GSM)
be activated activation for
the UE
VQP_DL_ON or
VQP_BLER ON VQP_UL_ON or
MAC UL residual BLER conditions (based on
LTE2493) VQP_BLER_ON

*sidelink refers to functionality introduced by LTE2612 ProSe Direct Communications for Public Safety

35 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Decision to deactivate event B1 measurements for SRVCC to GSM

C-plane conditions Trigger Combination

• QCI1 Bearer released VQ-TrOFF
Function
• Sidelink* activated for VoLTE user (Voice Quality
If Voice Quality
Trigger OFF)
• etc. Problem (VQP) reported by
disappears or VoLTE Trigger
call is disconnected Combination
existing event B1 Function results
measurements are in event B1
deactivated; measurements
PDCP PDU UL/DL gap detection Flow Control VQP_DL_OFF and (SRVCC to GSM)
VQP OFF VQP OFF VQP_UL_OFF and deactivation for
VQP_BLER_OFF the UE
or
MAC UL residual BLER conditions (based on QCI1 released or
2493) VQP_BLER OFF sidelink activated

*sidelink refers to functionality introduced by LTE2612 ProSe Direct Communications for Public Safety

36 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Remarks for event B1 based measurement activation

- If no GSM cell is allowed for SRVCC (LNRELG:srvccAllowed = forbidden), no measurement
reconfiguration will be done when the trigger happens
- If EPC does not support SRVCC, no measurement reconfiguration will be done when the trigger
happens
- If UE does not support B1 measurement or SRVCC to GSM (to support SRVCC with B1, FGI9, 15, 23
have to be set to true), no measurement reconfiguration will be done when the trigger happens

37 © Nokia 2018
Nokia Internal Use
Technical Details
LTE3443 VoLTE quality triggered SRVCC to GSM

• Actions after event B1 activation

- Activation of event B1 based on VQP triggers coming from PDCP or MAC does not assure that SRVCC
to GSM will be triggered
- The UE has to find GSM cell with sufficient RSSI as indicated by event B1 conditions
- eNB triggers SRVCC to GSM only after receiving RRC:MeasurementReport with event B1
- Further steps in SRVCC procedure are the same as defined for LTE873 SRVCC to GSM

38 © Nokia 2018
Nokia Internal Use
LTE3443 VoLTE quality triggered SRVCC to GSM

Interdependencies

Table of contents

39 © Nokia 2018
Interdependencies

LTE873 SRVCC to GSM

prerequisites LTE873 is a precondition for LTE3443; the same GERAN targets and radio conditions
applicable for target GERAN cells are used by LTE873 and LTE3443; the only
difference is that for LTE3443 no radio conditions for serving cell (RSRP/RSRQ) are
checked;
LTE873 relies on event B2 based measurements, while for LTE3443 event B1 is used;
however from target GERAN cell point of view, exactly the same radio conditions are
used for both mentioned events B2 and B1
 More details available on WebNEI: LTE873

LTE2493 Enhanced VoLTE Performance Monitoring

UL VoLTE residual BLER measurements as such are introduced by LTE2493; in this
context LTE2493 is prerequisite for UL residual BLER SRVCC trigger introduced by
LTE3443
 More details available on WebNEI: LTE2493

40 © Nokia 2018
Nokia Internal Use
Interdependencies

LTE64 Service based handover thresholds

extensions If VoLTE dedicated thresholds for event B2 based SRVCC towards GSM are configured,
the LTE3443 uses this VoLTE dedicated threshold applicable for event B1 based
SRVCC to GSM
 More details available on WebNEI: LTE64

LTE3290 SRVCC trigger enhancement

Event B1 Measurement Report for SRVCC to GSM trigger due to LTE3443 is ignored if
delay timer introduced by LTE3290 is running
 More details available on WebNEI: LTE3290

LTE907 TTI bundling

If LTE907 is enabled, final residual BLER triggers SRVCC according to LTE3443
functionality if UE is in TTIB mode; PDCP voice gaps, trigger SRVCC according to
LTE3443 independently of the TTIB mode
 More details available on WebNEI: LTE907

41 © Nokia 2018
Nokia Internal Use
Interdependencies

LTE3127 SRVCC to GSM measurement optimization

extensions In case of GERAN measurement activation for VoLTE users, LTE3127 eliminates all
other already active inter-frequency LTE and Inter-RAT measurements; the same rule
apply also for case, GERAN measurements are activated by LTE3443
 More details available on WebNEI: LTE3127

LTE1127 Service based mobility trigger

LTE3443 SRVCC trigger does not stop LTE1127 triggered A4 measurements
 More details available on WebNEI: LTE1127

LTE570 Periodic UE measurements

LTE3443 SRVCC trigger does not stop the (LTE570) periodical intra frequency
measurements
 More details available on WebNEI: LTE570

42 © Nokia 2018
Nokia Internal Use
Interdependencies

LTE3120 VoLTE quality triggered SRVCC to WCDMA

extensions If LTE3120 and LTE3443 are enabled in the same cell, B1 measurements for GSM and
WCDMA are configured in parallel; the report that is received first from eNodeB
determines which RAT is used for SRVCC (this feature is FL19/TL19 candidate)

43 © Nokia 2018
Nokia Internal Use
Interdependencies

LTE2612 ProSe Direct Communications for Public Safety

limitations If the UE is configured for sidelink communication, VQ triggered SRVCC to GSM is not
used
 More details available on WebNEI: LTE2612

LTE1170 Inter eNode B IF Load Balancing

LTE1841 Inter-Frequency Load Equalization
LTE3443 SRVCC trigger stop running LB A4 measurements
 More details available on WebNEI: LTE1170
 More details available on WebNEI: LTE1841

LTE1357 LTE-UTRAN load balancing

LTE3443 SRVCC trigger stop running LB B1 measurements
 More details available on WebNEI: LTE1357

LTE2051 Measurement based Idle Mode Load Balancing

LTE3443 SRVCC trigger stop running IMLB A4 measurements
 More details available on WebNEI: LTE2051
44 © Nokia 2018
Nokia Internal Use
LTE3443 VoLTE quality triggered SRVCC to GSM

Benefits and Gains

Table of contents

45 © Nokia 2018
Benefits and Gains
LTE3443 VoLTE quality triggered SRVCC to GSM

• LTE 3443 seem to bring benefits especially in areas VoLTE users with low voice quality due
highly loaded by VoLTE traffic and overlapped by GSM missing packets may be steered towards
layer
GSM via SRVCC procedure
• Feature reduces the number of calls for which low
voice quality is perceived by end users
- this is possible by moving VoLTE users towards CS
domain of GSM via SRVCC procedure LTE
• LTE3443 may be treated also as supporting feature
for GBR congestion resolution
- so far existing mechanism introduced by feature SRVCC to GSM
bundle LTE496/LTE497/LTE534 would finally lead to
disconnections of GBR bearers
- now VoLTE calls, which are of GBR traffic, may be
GSM
moved toward GSM before they are disconnected by
congestion handling mechanism

46 © Nokia 2018
Nokia Internal Use
LTE3443 VoLTE quality triggered SRVCC to GSM

Configuration
Management
Table of contents

47 © Nokia 2018
Configuration Management
Definition of terms and rules for parameter classification*
The ‘Basic Parameters’ category contains The ‘Advanced Parameters’ category contains
primary parameters which should be considered the parameters for network optimisation and
during cell deployment and must be adjusted to fine tuning:
a particular scenario:
• Decent network performance should be achieved without tuning
• Network Element (NE) identifiers these parameters
• Planning parameters, e.g. neighbour definitions, frequency, • Universal defaults ensuring decent network performance need
scrambling codes, PCI, RA preambles to be defined for all parameters of this category. If this is not
• Parameters that are the outcome from dimensioning, i.e. basic possible for a given parameter it must be put to the ‘Basic
parameters defining amount of resources Parameters’ category
• Basic parameters activating basic functionalities, e.g. power • Parameters requiring detailed system knowledge and broad
control, admission control, handovers experience unless rules for the ‘Basic Parameters’ category are
• Parameters defining operators’ strategy, e.g. traffic steering, violated
thresholds for power control, handovers, cell reselections, basic • All parameters (even without defaults, e.g. optional structures)
parameters defining feature behaviour related to advanced and very complex features

The ‘Obsolete parameters’ category is intended for parameters that are candidates to be removed
from the product in a future release: * - purpose: Categories of parameters have been defined to simplify network
parametrization. Parameterization effort shall be focused mainly on Basic
• Parameters always used with default value
• Parameters that are not used by operators ones. Categorization is reflected in a ‘view’ definition in NetAct CM Editor.
• Parameters that are not relevant anymore
48 © Nokia 2018
Nokia Internal Use
 • Under LNBTS up to 96 independent VoLTE Quality
Configuration Management Profiles VOLTEQUALPR may be defined

LTE3443 VoLTE quality triggered SRVCC to GSM • A given cell is using VoLTE Quality Profile indicated
by parameter LNCEL:assignedVoLteQualProfId
LNBTS which is a pointer to VOLTEQUALPR:voLteQualPrId
actSrvccToGsm = true
actVoLteQualSRVCCtoGsm = true
…

LNCEL-1 LNCEL-2 LNCEL-96

assignedVoLteQualProfId = X assignedVoLteQualProfId = Y … assignedVoLteQualProfId = …
… … …

VOLTEQUALPR-1 VOLTEQUALPR-2 VOLTEQUALPR-96

voLteQualPrId = Y voLteQualPrId = … voLteQualPrId = X
badQualityRBlerThres badQualityRBlerThres badQualityRBlerThres
goodQualityRBlerThres
rBlerCondTimeToTrigger
goodQualityRBlerThres
rBlerCondTimeToTrigger
… goodQualityRBlerThres
rBlerCondTimeToTrigger
badQualityDLGapThres badQualityDLGapThres badQualityDLGapThres
badQualityULGapThres badQualityULGapThres badQualityULGapThres
goodQualityGapThres goodQualityGapThres goodQualityGapThres

49 © Nokia 2018
Configuration Management
New parameters

Abbreviated name Full name PKDB link

LNBTS:actVoLteQualSRVCCtoGsm Activate VoLTE quality triggered SRVCC to GSM

LNCEL:assignedVoLteQualProfile Assigned VoLTE quality profile

VOLTEQUALPR:voLteQualPrId VoLTE quality profile identifier

50 © Nokia 2018
Nokia Internal Use
Configuration Management
New parameters

Abbreviated name Full name PKDB link

VOLTEQUALPR: badQualityRBlerThres Bad quality residual BLER threshold

VOLTEQUALPR: goodQualityRBlerThres Good quality residual BLER threshold

VOLTEQUALPR: rBlerCondTimeToTrigger Residual BLER condition time to trigger

VOLTEQUALPR: badQualityDLGapThres Bad quality DL voice gap threshold

VOLTEQUALPR: badQualityULGapThres Bad quality UL voice gap threshold

VOLTEQUALPR: goodQualityGapThres Good quality UL DL voice gap threshold

PMCCP:maxVBreakDistThresh Max voice break distribution threshold

51 © Nokia 2018
Nokia Internal Use
LTE3443 VoLTE quality triggered SRVCC to GSM

Deployment
Aspects
Network graphic boxes Network element boxes
Table of contents

52 © Nokia 2018
Nokia Internal Use
Deployment Aspects
LTE3443 VoLTE quality triggered SRVCC to GSM

• High number of VoLTE users is established in the cell

• The users are moving towards cell edge, however no low RSRP or RSRQ is reached to activate event B2 based
measurement for SRVCC to GSM (acc. to to LTE873)
• The more UEs moving towards cell edge, the more physical radio resources are needed to keep requested GBR
requirements for VoLTE traffic
• If GBR congestion is detected some of the VoLTE bearers may be deprioritized – this means some of them will be
scheduled less frequent as required what can degrade the voice call quality directly perceived by the end user
• If congestion is not resolved within 300ms, the eNB may decide to release some of existing voice connections

• With LTE3443, event B1 for SRVCC to GSM may be activated at congestion detection
state and lead to congestion resolution by moving the VoLTE UEs to GSM, reducing at
the same time number of possible VoLTE call disconnections

53 © Nokia 2018
Nokia Internal Use
LTE3443 VoLTE quality triggered SRVCC to GSM

Performance
Aspects
Table of contents

54 © Nokia 2018
Performance Aspects
LTE3443 VoLTE quality triggered SRVCC to GSM

• Monitoring of PDCP packet loss for DL/UL (1/3)

- Despite of detection of Voice Quality Problem (VQP) based on the missing packets in DL
(VOLTEQUALPR:badQualityDLGapThres) and UL (VOLTEQUALPR:badQualityULGapThres), the eNB is
able to collect the distribution of the PDCP packets gaps in DL and UL as such

- For this purposes 11 bins for DL and 11 bins for UL reflected by new counters were created
• 11 bins for DL reflected by new counters
DL_VB_PERIOD_BIN1 (M8067C0)...DL_VB_PERIOD_BIN11 (M8067C10)
• 11 bins for UL reflected by new counters
UL_VB_PERIOD_BIN1 (M8067C11)...UL_VB_PERIOD_BIN11 (M8067C21)

55 © Nokia 2018
Nokia Internal Use
Performance Aspects
LTE3443 VoLTE quality triggered SRVCC to GSM

• Monitoring of PDCP packet loss for DL/UL (2/3)

- Gap span for each bin in DL/UL is evaluated based on new parameter PMCCP:maxVBreakDistThresh
with possible values 1...10 s, step 1 s according to following formula
• Gap span for BINX, where X = 1…10
(X -1 )*(PMCCP:maxVBreakDistThresh/10) < Gap Span <= X*(PMCCP:maxVBreakDistThresh/10)
• Gap span for BINX, where X = 11
(X -1)*(PMCCP:maxVBreakDistThresh/10) < Gap Span

- As an example for PMCCP:maxVBreakDistThresh = 2s (default value) the detected Voice Breaks will fall
into bins and increment appropriated counters according to the ranges as below

BIN1 BIN2 BIN3 BIN4 BIN5 BIN6 BIN7 BIN8 BIN9 BIN10 BIN11
(0,0.2] (0.2,0.4] (0.4,0.6] (0.6,0.8] (0.8,1.0] (1.0,1.2] (1.2,1.4] (1.4,1.6] (1.6,1.8] (1.8,2.0] >2.0

56 © Nokia 2018
Nokia Internal Use
Performance Aspects
LTE3443 VoLTE quality triggered SRVCC to GSM

• Monitoring of PDCP packet loss for DL/UL (3/3)

- Having information collected by bins, an Operator is able to create PDCP Voice Breaks histograms for DL/UL, giving
the view whether PDCP Voice Break problem is significant or not
- It is expected that the Voice Breaks will be dominant in the first bins and the trend shall be decreasing for next
bins, but the most valuable information is numerousness collected in bins for a given collection period
- This way the Operator is able to compare its service requirements against the
network conditions and take a decision whether activation of PDCP gap triggered
numerousness
SRVCC to GSM is reasonable or not
- Histograms may also be helpful for tuning parameters which control VQP_ON
triggered by PDCP packet gaps

BIN11
BIN10
BIN5
bins

BIN1
BIN2
BIN3
BIN4

BIN6
BIN7
BIN8
BIN9
57 © Nokia 2018
Nokia Internal Use
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

ISYS_HO_GERAN_SRVCC_PREP_VQ This measurement provides the number of Inter-System Handover
(M8016C61) preparations to
the GERAN with VoLTE-Quality-triggered SRVCC.
#LTE Inter System Handover
Trigger event: Transmission of an S1AP:HANDOVER REQUIRED message to
the source MME for an Inter-System
Handover to the GERAN with VoLTE Quality Triggered SRVCC.

Use case: Preparation Phase Success Ratio for VoLTE-Quality-triggered

SRVCC to GERAN
ISYS_HO_GERAN_SRVCC_ATT_VQ
Proposed KPI#1 (new) =
ISYS_HO_GERAN_SRVCC_PREP_VQ

58 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

ISYS_HO_GERAN_SRVCC_ATT_VQ This measurement provides the number of Inter-System Handover attempts
(M8016C62) to GERAN
with VoLTE-Quality-triggered SRVCC (Single Radio Voice Call Continuity,
#LTE Inter System Handover 3GPP TS 23.216).

Trigger event: Reception of an S1AP:HANDOVER COMMAND message

(source eNB <- MME; 3GPP TS 36.413) in case this message is received in
response to the preparation for an Inter-System Handover to GERAN with
VoLTE-Quality-triggered SRVCC (Single Radio Voice Call Continuity,
3GPP TS 23.216).

Use case: Preparation Phase Success Ratio for VoLTE-Quality-triggered

SRVCC to GERAN
ISYS_HO_GERAN_SRVCC_ATT_VQ
Proposed KPI#1 (new) =
ISYS_HO_GERAN_SRVCC_PREP_VQ

59 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

ISYS_HO_GERAN_SRVCC_SUCC_VQ This measurement provides the number of successful Inter-System
(M8016C63) Handover completions
to GERAN with VoLTE-Quality-triggered SRVCC (Single Radio Voice Call
#LTE Inter System Handover Continuity, 3GPP TS 23.216).

Trigger event: Reception of an S1AP:UE CONTEXT RELEASE COMMAND

message (source eNB <- MME; 3GPP TS 36.413) with Cause value "Radio
Network Layer (Successful Handover)" in case this message is received for an
Inter-System Handover to GERAN with VoLTE-Quality-triggered SRVCC
(Single Radio Voice Call Continuity, 3GPP TS 23.216).

Use case: Execution Phase Success Ratio for VoLTE-Quality-triggered SRVCC

to GERAN
ISYS_HO_GERAN_SRVCC_SUCC_VQ
Proposed KPI#2 (new) =
ISYS_HO_GERAN_SRVCC_ATT_VQ

60 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

ISYS_HO_GER_SRVCC_P_FAIL_TI_VQ This measurement provides the number of failed Inter-System Handover
(M8016C64) preparations
to the GERAN with VoLTE-Quality-triggered SRVCC due to the expiration of
#LTE Inter System Handover the guarding timer.

Trigger event: This counter is updated when Inter-System Handover

preparation to GERAN with VoLTE-Quality-triggered SRVCC fails due to
expiration of the guarding timer TS1RELOCprep_InterRAT. This
counter is updated for the source cell of the handover.

Use case: Preparation Phase Failure Ratio for VoLTE-Quality-triggered

SRVCC to GERAN due to guarding time expiry

ISYS_HO_GER_SRVCC_P_FAIL_TI_VQ
Proposed KPI#3 (new) =
ISYS_HO_GERAN_SRVCC_PREP_VQ

61 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

ISYS_HO_GER_SRVCC_P_FAIL_AC_VQ This measurement provides the number of failed Inter-System Handover
(M8016C65) preparations
to the GERAN with VoLTE-Quality-triggered SRVCC due to admission control
#LTE Inter System Handover of the target cell.
Trigger event: This counter is updated when an S1AP:HANDOVER
PREPARATION FAILURE message is received from the MME with cause "No
radio resources available in target cell" for an Inter-System Handover to the
GERAN with VoLTE-Quality-triggered SRVCC. This counter
is updated for the source cell of the handover.

Use case: Preparation Phase Failure Ratio for VoLTE-Quality-triggered

SRVCC to GERAN due to admission control rejection

ISYS_HO_GER_SRVCC_P_FAIL_AC_VQ
Proposed KPI#4 (new) =
ISYS_HO_GERAN_SRVCC_PREP_VQ

62 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

ISYS_HO_GER_SRVCC_P_FAIL_OT_VQ The number of failed Inter-System Handover preparations to the GERAN
(M8016C66) with VoLTE-Quality-triggered SRVCC due to other reasons (target cell).

#LTE Inter System Handover Trigger event: This counter is updated when an S1AP:HANDOVER
PREPARATION FAILURE message is received from the MME with a cause other
than "No radio resources available in target cell" for an Inter-System
Handover to the GERAN with VoLTE-Quality-triggered SRVCC.

Use case: Preparation Phase Failure Ratio for VoLTE-Quality-triggered

SRVCC to GERAN due other reasons

ISYS_HO_GER_SRVCC_P_FAIL_OT_VQ
Proposed KPI#5 (new) =
ISYS_HO_GERAN_SRVCC_PREP_VQ

63 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

ISYS_HO_GER_SRVCC_FAIL_TIM_VQ The number of VoLTE-Quality-triggered SRVCC HO execution failures due
(M8016C67) to expiry of the guarding timer.

#LTE Inter System Handover Trigger event: This counter is updated following the expiry of the guarding
timer TS1RELOCoverall in case that this timer was started because of an
Inter-System Handover to GERAN with VoLTE-Quality-triggered SRVCC.

Use case: Execution Phase Failure Ratio for VoLTE-Quality-triggered SRVCC

to GERAN due to TS1RELOCoverall guarding time expiry

ISYS_HO_GER_SRVCC_FAIL_TIM_VQ
Proposed KPI#6 (new) =
ISYS_HO_GERAN_SRVCC_ATT_VQ

64 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

DL_VB_PERIOD_BIN1 This counter provides sum of events when UEs are having packet loss for period
(M8067C0) matching the range of bin 1.
The range is dependent on the value of the PMCCP:maxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 1 is as follows:
Histogram 0 < UE in Voice Break Period for DL <= 0,1 * PMCCP:maxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin1. Packet loss period is detected as difference in the time between the last
successful PDCP SDU sent and the first new successful PDCP SDU sent after the
period of discarded SDUs (or the lower layer indicated as not possible to
proceed).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

65 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

DL_VB_PERIOD_BIN2 This counter provides sum of events when UEs are having packet loss for period
(M8067C1) matching the range of bin 2.
The range is dependent on the value of the PMCCP:maxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 2 is as follows:
Histogram 0,1 * PMCCP:maxVBreakDistThresh < UE in Voice Break Period for DL <= 0,2 *
PMCCP:maxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin2. Packet loss period is detected as difference in the time between the last
successful PDCP SDU sent and the first new successful PDCP SDU sent after the
period of discarded SDUs (or the lower layer indicated as not possible to
proceed).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

66 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

DL_VB_PERIOD_BIN3 This counter provides sum of events when UEs are having packet loss for period
(M8067C2) matching the range of bin 3.
The range is dependent on the value of the PMCCP:maxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 3 is as follows:
Histogram 0,2 * PMCCP:maxVBreakDistThresh < UE in Voice Break Period for DL <= 0,3 *
PMCCP:maxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin3. Packet loss period is detected as difference in the time between the last
successful PDCP SDU sent and the first new successful PDCP SDU sent after the
period of discarded SDUs (or the lower layer indicated as not possible to
proceed).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

67 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

DL_VB_PERIOD_BIN4 This counter provides sum of events when UEs are having packet loss for period
(M8067C3) matching the range of bin 4.
The range is dependent on the value of the PMCCP:maxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 4 is as follows:
Histogram 0,3 * PMCCP:maxVBreakDistThresh < UE in Voice Break Period for DL <= 0,4 *
PMCCP:maxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin4. Packet loss period is detected as difference in the time between the last
successful PDCP SDU sent and the first new successful PDCP SDU sent after the
period of discarded SDUs (or the lower layer indicated as not possible to
proceed).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

68 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

DL_VB_PERIOD_BIN5 This counter provides sum of events when UEs are having packet loss for period
(M8067C4) matching the range of bin 5.
The range is dependent on the value of the PMCCP:maxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 5 is as follows:
Histogram 0,4 * PMCCP:maxVBreakDistThresh < UE in Voice Break Period for DL <= 0,5 *
PMCCP:maxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin5. Packet loss period is detected as difference in the time between the last
successful PDCP SDU sent and the first new successful PDCP SDU sent after the
period of discarded SDUs (or the lower layer indicated as not possible to
proceed).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

69 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

DL_VB_PERIOD_BIN6 This counter provides sum of events when UEs are having packet loss for period
(M8067C5) matching the range of bin 6.
The range is dependent on the value of the PMCCP:maxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 6 is as follows:
Histogram 0,5 * PMCCP:maxVBreakDistThresh < UE in Voice Break Period for DL <= 0,6 *
PMCCP:maxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin6. Packet loss period is detected as difference in the time between the last
successful PDCP SDU sent and the first new successful PDCP SDU sent after the
period of discarded SDUs (or the lower layer indicated as not possible to
proceed).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

70 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

DL_VB_PERIOD_BIN7 This counter provides sum of events when UEs are having packet loss for period
(M8067C6) matching the range of bin 7.
The range is dependent on the value of the PMCCP:maxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 7 is as follows:
Histogram 0,6 * PMCCP:maxVBreakDistThresh < UE in Voice Break Period for DL <= 0,7 *
PMCCP:maxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin7. Packet loss period is detected as difference in the time between the last
successful PDCP SDU sent and the first new successful PDCP SDU sent after the
period of discarded SDUs (or the lower layer indicated as not possible to
proceed).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

71 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

DL_VB_PERIOD_BIN8 This counter provides sum of events when UEs are having packet loss for period
(M8067C7) matching the range of bin 8.
The range is dependent on the value of the PMCCP:maxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 8 is as follows:
Histogram 0,7 * PMCCP:maxVBreakDistThresh < UE in Voice Break Period for DL <= 0,8 *
PMCCP:maxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin8. Packet loss period is detected as difference in the time between the last
successful PDCP SDU sent and the first new successful PDCP SDU sent after the
period of discarded SDUs (or the lower layer indicated as not possible to
proceed).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

72 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

DL_VB_PERIOD_BIN9 This counter provides sum of events when UEs are having packet loss for period
(M8067C8) matching the range of bin 9.
The range is dependent on the value of the PMCCP:maxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 9 is as follows:
Histogram 0,8 * PMCCP:maxVBreakDistThresh < UE in Voice Break Period for DL <= 0,9 *
PMCCP:maxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin9. Packet loss period is detected as difference in the time between the last
successful PDCP SDU sent and the first new successful PDCP SDU sent after the
period of discarded SDUs (or the lower layer indicated as not possible to
proceed).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

73 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

DL_VB_PERIOD_BIN10 This counter provides sum of events when UEs are having packet loss for period
(M8067C9) matching the range of bin 10.
The range is dependent on the value of the PMCCP:maxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 10 is as follows:
Histogram 0,9 * PMCCP:maxVBreakDistThresh < UE in Voice Break Period for DL <= 1 *
PMCCP:maxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin10. Packet loss period is detected as difference in the time between the last
successful PDCP SDU sent and the first new successful PDCP SDU sent after the
period of discarded SDUs (or the lower layer indicated as not possible to
proceed).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

74 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

DL_VB_PERIOD_BIN11 This counter provides sum of events when UEs are having packet loss for period
(M8067C10) which exceeds the range of the parameter PMCCP:MaxVBreakDistThresh
commissioned by the customer. The range of bin 11 is as follows:
#LTE VoLTE Voice Break Period PMCCP:maxVBreakDistThresh < UE in Voice Break Period for DL
Histogram
Trigger event: This counter is updated if packet loss period exceed the maximum
value defined by Customer. Maximum value is defined by
PMCCP:MaxVBreakDistThresh parameter. Packet loss period is detected as
difference in the time between the last successful PDCP SDU sent and the first
new successful PDCP SDU sent after the period of discarded SDUs (or the lower
layer indicated as not possible to proceed).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

75 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

UL_VB_PERIOD_BIN1 This counter provides sum of events when UEs are having packet loss for period
(M8067C11) matching the range of bin 1.
The range is dependent on the value of the PMCCP:MaxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 1 is as follows:
Histogram 0 <= UE in Voice Break Period for UL <= 0,1 * PMCCP:MaxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin1. Packet loss period is detected as difference in the time between the last
successfully decoded PDCP SDU and the first new successfully decoded PDCP
SDU after period of lost SDUs (SN are missing).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

76 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

UL_VB_PERIOD_BIN2 This counter provides sum of events when UEs are having packet loss for period
(M8067C12) matching the range of bin 2.
The range is dependent on the value of the PMCCP:MaxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 2 is as follows:
Histogram 0,1 * PMCCP:MaxVBreakDistThresh < UE in Voice Break Period for UL <= 0,2 *
PMCCP:MaxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin2. Packet loss period is detected as difference in the time between the last
successfully decoded PDCP SDU and the first new successfully decoded PDCP
SDU after period of lost SDUs (SN are missing).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

77 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

UL_VB_PERIOD_BIN3 This counter provides sum of events when UEs are having packet loss for period
(M8067C13) matching the range of bin 3.
The range is dependent on the value of the PMCCP:MaxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 3 is as follows:
Histogram 0,2 * PMCCP:MaxVBreakDistThresh < UE in Voice Break Period for UL <= 0,3 *
PMCCP:MaxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin3. Packet loss period is detected as difference in the time between the last
successfully decoded PDCP SDU and the first new successfully decoded PDCP
SDU after period of lost SDUs (SN are missing).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

78 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

UL_VB_PERIOD_BIN4 This counter provides sum of events when UEs are having packet loss for period
(M8067C14) matching the range of bin 4.
The range is dependent on the value of the PMCCP:MaxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 4 is as follows:
Histogram 0,3 * PMCCP:MaxVBreakDistThresh < UE in Voice Break Period for UL <= 0,4 *
PMCCP:MaxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin4. Packet loss period is detected as difference in the time between the last
successfully decoded PDCP SDU and the first new successfully decoded PDCP
SDU after period of lost SDUs (SN are missing).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

79 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

UL_VB_PERIOD_BIN5 This counter provides sum of events when UEs are having packet loss for period
(M8067C15) matching the range of bin 5.
The range is dependent on the value of the PMCCP:MaxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 5 is as follows:
Histogram 0,4 * PMCCP:MaxVBreakDistThresh < UE in Voice Break Period for UL <= 0,5 *
PMCCP:MaxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin5. Packet loss period is detected as difference in the time between the last
successfully decoded PDCP SDU and the first new successfully decoded PDCP
SDU after period of lost SDUs (SN are missing).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

80 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

UL_VB_PERIOD_BIN6 This counter provides sum of events when UEs are having packet loss for period
(M8067C16) matching the range of bin 6.
The range is dependent on the value of the PMCCP:MaxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 6 is as follows:
Histogram 0,5 * PMCCP:MaxVBreakDistThresh < UE in Voice Break Period for UL <= 0,6 *
PMCCP:MaxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin6. Packet loss period is detected as difference in the time between the last
successfully decoded PDCP SDU and the first new successfully decoded PDCP
SDU after period of lost SDUs (SN are missing).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

81 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

UL_VB_PERIOD_BIN7 This counter provides sum of events when UEs are having packet loss for period
(M8067C17) matching the range of bin 7.
The range is dependent on the value of the PMCCP:MaxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 7 is as follows:
Histogram 0,6 * PMCCP:MaxVBreakDistThresh < UE in Voice Break Period for UL <= 0,7 *
PMCCP:MaxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin7. Packet loss period is detected as difference in the time between the last
successfully decoded PDCP SDU and the first new successfully decoded PDCP
SDU after period of lost SDUs (SN are missing).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

82 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

UL_VB_PERIOD_BIN8 This counter provides sum of events when UEs are having packet loss for period
(M8067C18) matching the range of bin 8.
The range is dependent on the value of the PMCCP:MaxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 8 is as follows:
Histogram 0,7 * PMCCP:MaxVBreakDistThresh < UE in Voice Break Period for UL <= 0,8 *
PMCCP:MaxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin8. Packet loss period is detected as difference in the time between the last
successfully decoded PDCP SDU and the first new successfully decoded PDCP
SDU after period of lost SDUs (SN are missing).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

83 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

UL_VB_PERIOD_BIN9 This counter provides sum of events when UEs are having packet loss for period
(M8067C19) matching the range of bin 9.
The range is dependent on the value of the PMCCP:MaxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 9 is as follows:
Histogram 0,8 * PMCCP:MaxVBreakDistThresh < UE in Voice Break Period for UL <= 0,9 *
PMCCP:MaxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin9. Packet loss period is detected as difference in the time between the last
successfully decoded PDCP SDU and the first new successfully decoded PDCP
SDU after period of lost SDUs (SN are missing).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

84 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

UL_VB_PERIOD_BIN10 This counter provides sum of events when UEs are having packet loss for period
(M8067C20) matching the range of bin 10.
The range is dependent on the value of the PMCCP:MaxVBreakDistThresh
#LTE VoLTE Voice Break Period parameter. The range of bin 10 is as follows:
Histogram 0,9 * PMCCP:MaxVBreakDistThresh < UE in Voice Break Period for UL <= 1 *
PMCCP:MaxVBreakDistThresh

Trigger event: This counter is updated if packet loss period is within the range of
bin10. Packet loss period is detected as difference in the time between the last
successfully decoded PDCP SDU and the first new successfully decoded PDCP
SDU after period of lost SDUs (SN are missing).
Note: This counter is related to monitoring VoLTE-quality-triggered SRVCC to
GSM/WCDMA.

85 © Nokia 2018
Performance Aspects
New counters
Feature LTE3443 introduced 29 new counters

Counter name Description

UL_VB_PERIOD_BIN11 This counter provides sum of events when UEs are having packet loss for period
(M8067C21) which exceeds the range of the parameter PMCCP:MaxVBreakDistThresh
commissioned by the customer. The range of bin 11 is as follows:
#LTE VoLTE Voice Break Period PMCCP:maxVBreakDistThresh < UE in Voice Break Period for UL
Histogram
Trigger event: This counter is updated if packet loss period exceed the maximum
value defined by Customer. Maximum value is defined in
PMCCP:MaxVBreakDistThresh parameter. Packet loss period is detected as
difference in the time between the last successfully decoded PDCP SDU and the
first new successfully decoded PDCP SDU after the period of lost SDUs (SN are
missing).
Note: The counter is related to monitoring VoLTE quality triggered SRVCC to
GSM/WCDMA.

86 © Nokia 2018
Performance Aspects
Feature impact

Feature impact How to measure?

It is expected that existing KPIs which control PDCP SDU Loss KPIs:
Ratio for DL and UL and PDCP SDU Discard Ratio for DL will
improve. - E-UTRAN PDCP SDU Loss Ratio in the UL, QCI1 (LTE_5311b)
This is because with LTE3443 UEs, which contribute to high - E-UTRAN PDCP SDU Loss Ratio in the DL, QCI1 (LTE_5305c)
Loss Ratio or Discard Ratio may be now moved from LTE to - E-UTRAN PDCP SDU Discard Ratio in DL, QCI1 (LTE_5256c)
GSM via SRVCC procedure.
As result such unwanted UEs state is shortened on LTE side

It is recommended to verify histograms of UL residual BLER Counters:

introduced by LTE2493.
- UL_QCI1_RES_BLER_BIN1 (M8054C11)
It is expected that the bins defined for high BLER (above
VOLTEQUALPR:badQualityRBlerThres) will be updated less …
frequently, due to fact SRVCC to GSM may be triggered by high - UL_CI1_RES_BLER_BIN11 (M8054C21)
UL residual BLER

87 © Nokia 2018
Nokia Internal Use
Performance Aspects
Feature impact

Feature impact How to measure?

It is recommended to verify histograms of DL/UL PDCP Voice Counters:
Break - DL_VB_PERIOD_BIN1 (M8067C0)
It is expected that the Voice Breaks will be dominant in the first …
bins and the trend shall be decreasing for next bins, but the - DL_VB_PERIOD_BIN11 (M8067C10)
most valuable information is numerousness collected in bins for
a given collection period - UL_VB_PERIOD_BIN1 (M8067C11)
Based on this the Operator is able to compare its service …
requirements against the network conditions and take a - UL_VB_PERIOD_BIN11 (M8067C21)
decision whether activation of PDCP gap triggered SRVCC to
GSM is reasonable or not

As LTE3443 introduces additional trigger for SRVCC to GSM it is KPIs:

expected that the number of SRVCC to GSM preparations and
SRVCC attempts will increase - Inter RAT HO Preparation Attempts to GERAN with SRVCC
(LTE_6107a)
- E-UTRAN Inter RAT HO Attempts to GERAN SRVCC
(LTE_5565a)

88 © Nokia 2018
Nokia Internal Use
89 © Nokia 2018