Professional Documents
Culture Documents
Counter Description
for PKG 9.0.0 P1
This description provides call flows and detailed description for statistic items
collected in the LTE eNB system for analysis.
Radio Access Network
SNMTC-v3-0312
This manual should be read and used as a guideline for properly installing and/or operating the
product. Owing to product variations across the range, any illustrations and photographs used in
this manual may not be a wholly accurate depiction of the actual products you are using.
This manual may be changed for system improvement, standardization and other technical
reasons without prior notice.
Samsung Networks documentation is available at www.samsungdocs.com
Contents
Preface xix
Relevance ....................................................................................................................................... xix
Conventions in this Document ....................................................................................................... xix
New and Changed Information ....................................................................................................... xx
Revision History.............................................................................................................................. xxi
Organization of This Document ..................................................................................................... xxi
Related Documentation ................................................................................................................. xxi
Chapter 1 Introduction 1
Chapter 2 Counter Description 3
Appendix A Acronyms 4
Appendix B Call Flow 5
RRC ................................................................................................................................................... 5
RRC Connection Establishment .................................................................................................... 6
RRC Connection Reconfiguration ............................................................................................... 13
RRC Connection Re-establishment ............................................................................................. 14
RRC Connection Re-establishment Time .................................................................................... 28
RRC Connection Release ............................................................................................................ 28
RRC Connection Number ............................................................................................................ 42
RRC Connection Setup Time ....................................................................................................... 44
Call Drop .................................................................................................................................... 44
NB-IoT RRC Connection Establishment ...................................................................................... 48
NB-IoT RRC Connection Re-establishment Time ........................................................................ 55
NB-IoT RRC Connection Reconfiguration ................................................................................... 56
NB-IoT RRC Connection Re-establishment ................................................................................. 56
NB-IoT RRC Connection Release................................................................................................. 62
NB-IoT RRC Connection Number ................................................................................................ 70
NB-IoT RRC Connection Setup-NB Time ..................................................................................... 71
NB-IoT Call Drop ........................................................................................................................ 72
E-RAB .............................................................................................................................................. 76
E-RAB Setup ............................................................................................................................... 76
E-RAB Setup Add ........................................................................................................................ 82
E-RAB Setup Time ...................................................................................................................... 88
E-RAB Erase Request .................................................................................................................. 89
E-RAB Erase................................................................................................................................ 95
E-RAB Modify ............................................................................................................................. 95
E-RAB Release Request ............................................................................................................ 100
E-RAB Release .......................................................................................................................... 100
E-RAB Session Time per Cell ..................................................................................................... 103
E-RAB Session Time per QCI ..................................................................................................... 103
Active E-RAB Number............................................................................................................... 104
E-RAB QCI per-PLMN rejected.................................................................................................. 104
NB-IoT E-RAB Setup ................................................................................................................. 105
NB-IoT E-RAB Setup Add .......................................................................................................... 110
NB-IoT E-RAB Erase .................................................................................................................. 114
Contents
Contents
List of Figures
List of Figures
List of Figures
List of Figures
List of Figures
List of Figures
List of Figures
List of Figures
List of Figures
List of Figures
Figure 464. Collection Time for VoLTE S1 handover time ............................................................................... 249
Figure 465. Collection Time for Downlink VoLTE quality defect ..................................................................... 250
Figure 466. Collection Time for Uplink VoLTE quality defect .......................................................................... 250
Figure 467. Collection Time for VoLTE Recommended Bit Rate ..................................................................... 251
Figure 468. Collection Time for ULSpsConfigAtt and ULSpsConfigSucc .......................................................... 252
Figure 469. Collection Time for TTIBActAtt and TTIBActSucc ......................................................................... 252
Figure 470. Collection Time for TTIBDeactAtt and TTIBDeactSucc ................................................................. 253
Figure 471. Collection Time for GTP Forward Traffic (1) ................................................................................. 253
Figure 472. Collection Time for GTP Forward Traffic (2) ................................................................................. 253
Figure 473. Collection Time for GTP Forward Traffic (3) ................................................................................. 254
Figure 474. Collection Time for Discovery Related Counters .......................................................................... 255
Figure 475. Collection Time for S1APUEAmbrOverride .................................................................................. 256
Figure 476. Collection Time for S1APUEAmbrOverride in S1 Handover Case................................................. 256
Figure 477. Collection Time for X2APUEAmbrOverride in X2 Handover Case ................................................ 257
Figure 478. Collection Time for Measurement Report ................................................................................... 257
Figure 479. Collection Time for M2ConnEstabAtt (1) ..................................................................................... 258
Figure 480. Collection Time for M2ConnEstabAtt (2) ..................................................................................... 258
Figure 481. Collection Time for M2ConnEstabAtt (3) ..................................................................................... 259
Figure 482. Collection Time for M2ConnEstabAtt (4) ..................................................................................... 259
Figure 483. Collection Time for M2ConnEstabAtt (5) ..................................................................................... 259
Figure 484. Collection Time for M2ConnEstabAtt (6) ..................................................................................... 260
Figure 485. Collection Time for M2ConnEstabSucc (1) ................................................................................... 260
Figure 486. Collection Time for M2ConnEstabSucc (2) ................................................................................... 260
Figure 487. Collection Time for M2ConnEstabFail_M2apCuFail ..................................................................... 261
Figure 488. Collection Time for M2ConnEstabFail_M2apLinkFail (1) ............................................................. 261
Figure 489. Collection Time for M2ConnEstabFail_M2apLinkFail (2) ............................................................. 261
Figure 490. Collection Time for SessionStartAtt and SessionStartSucc .......................................................... 261
Figure 491. Collection Time for SessionStartFail_M2apCuFail........................................................................ 262
Figure 492. Collection Time for SessionStartFail_M2apLinkFail ..................................................................... 262
Figure 493. Collection Time for SessionStopAtt and SessionStopSucc ........................................................... 262
Figure 494. Collection Time for SessionStopFail_M2apLinkFail ...................................................................... 262
Figure 495. Collection Time for SessionUpdateAtt and SessionUpdateSucc .................................................. 263
Figure 496. Collection Time for SessionUpdateFail_M2AP_CU_FAIL ............................................................. 263
Figure 497. Collection Time for SessionUpdateFail_M2AP_LINK_FAIL ........................................................... 263
Figure 498. Collection Time for MBMSCountingAtt and MBMSCountingSucc ............................................... 264
Figure 499. Collection Time for MBMSCountingFail_M2AP_CU_FAIL ............................................................ 264
Figure 500. Collection Time for MBMSCountingFail_M2AP_LINK_FAIL ......................................................... 264
Figure 501. Collection Time for MBMSCountingResultsReport ...................................................................... 265
Figure 502. Collection Time for MBMSCountingResultsReportFail_M2AP_LINK_FAIL ................................... 265
Figure 503. Collection Time for eNB MBMS Counting Results ........................................................................ 266
Figure 504. Collection Time for eNB Sync ....................................................................................................... 266
Figure 505. Collection Time for ADR-related eNB Sync .................................................................................. 267
Figure 506. Collection Time for Cell Sync ........................................................................................................ 267
Figure 507. Collection Time for Carrier Aggregation capable UEs in Initial Attach case ................................. 268
Figure 508. Collection Time for Carrier Aggregation capable UEs in RRE case ............................................... 269
Figure 509. Collection Time for Carrier Aggregation capable UEs in S1 Handover case ................................. 270
Figure 510. Collection Time for Carrier Aggregation capable UEs in X2 Handover case................................. 271
Figure 511. Collection Time for UL SCell Addition for Initial Attach ............................................................... 272
Figure 512. Collection Time for UL SCell Addition for Intra eNB Handover .................................................... 272
Figure 513. Collection Time for UL SCell Addition for RRC Connection Reestablishment .............................. 273
Figure 514. Collection Time for UL SCell Carrier Change for event A1 ........................................................... 274
Figure 515. Collection Time for UL SCell Change for A6 event case ............................................................... 275
List of Figures
Figure 516. Collection Time for UL SCell Configuration Deconfiguration for A1 and A2 event ...................... 276
Figure 517. Collection Time for S1SIG (1)........................................................................................................ 277
Figure 518. Collection Time for S1SIG (2)........................................................................................................ 277
Figure 519. Collection Time for S1SIG (3)........................................................................................................ 277
Figure 520. Collection Time for S1ConnEstabFail_S1apSigTo ......................................................................... 278
Figure 521. Collection Time for NBIoT S1SIG (1) ............................................................................................. 278
Figure 522. Collection Time for NBIoT S1SIG (2) ............................................................................................. 278
Figure 523. Collection Time for NBIoT S1SIG (3) ............................................................................................. 279
Figure 524. Collection Time for NBIoT_S1ConnEstabFail_S1apLinkFail (1)..................................................... 279
Figure 525. Collection Time for NBIoT_S1ConnEstabFail_S1apLinkFail (2)..................................................... 279
Figure 526. Collection Time for NBIoT_S1ConnEstabFail_S1apSigTo ............................................................. 280
Figure 527. Collection Time for Paging ........................................................................................................... 280
Figure 528. Collection Time for NBIoT_AttPaging ........................................................................................... 280
Figure 529. Collection Time for eMTC_AttPaging ........................................................................................... 281
Figure 530. Collection Time for NBIoT_PdcpSduBitrateULAvg ....................................................................... 281
Figure 531. Collection Time for NBIoT_PdcpSduBitrateDLAvg ....................................................................... 281
Figure 532. Collection Time for PdcpSduDropRateDL ..................................................................................... 282
Figure 533. Collection Time for PdcpSduLossRateUL, PdcpSduLossUlNum .................................................... 282
Figure 534. Collection Time for NBIoT_PdcpSduDropRateDL ......................................................................... 283
Figure 535. Collection Time for NBIoT_PdcpSduLossRateUL, NBIoT_PdcpSduLossULNum............................ 283
Figure 536. Collection Time for eMTC_PdcpSduLossRateUL, eMTC_PdcpSduLossUlNum ............................. 283
Figure 537. Collection Time for Load .............................................................................................................. 284
Figure 538. Collection Time for Load Histogram ............................................................................................. 284
Figure 539. Denied Call by Overload Protection ............................................................................................. 285
Figure 540. Collection Time for UE Category (1) ............................................................................................. 286
Figure 541. Collection Time for UE Category (2) ............................................................................................. 286
Figure 542. Collection Time for UE Category (3) ............................................................................................. 287
Figure 543. Collection Time for UE Category (4) ............................................................................................. 287
Figure 544. Collection Time for CoverageHole ............................................................................................... 288
Figure 545. Collection Time for CoverageHoleN ............................................................................................. 288
Figure 546. Collection Time for TooEarlyHoFailure ........................................................................................ 289
Figure 547. Collection Time for TooEarlyHoRlfAfterHo .................................................................................. 289
Figure 548. Collection Time for TooLateHoRlfBeforeTriggering ..................................................................... 290
Figure 549. Collection Time for TooLateHoRlfAfterTriggering ........................................................................ 290
Figure 550. Collection Time for WrongCellRlfAfterTriggering ........................................................................ 291
Figure 551. Collection Time for WrongCellRlfAfterHo .................................................................................... 291
Figure 552. Collection Time for PingpongHandover ....................................................................................... 292
Figure 553. Collection Time for HwcReestablishRlfAfterHo............................................................................ 292
Figure 554. Collection Time for HwcReestablishRlfAfterTriggering ................................................................ 293
Figure 555. Collection Time for CoverageHoleAtSetup................................................................................... 293
Figure 556. Collection Time for CoverageHoleAtSetupN ................................................................................ 294
Figure 557. Collection Time for TooEarlyHoFailureAtSetup ........................................................................... 295
Figure 558. Collection Time for TooEarlyHORlfAfterHoAtSetup ..................................................................... 296
Figure 559. Collection Time for TooLateHoRlfBeforeTriggeringAtSetup ........................................................ 297
Figure 560. Collection Time for HoToWrongCellRlfAfterTriggeringAtSetup ................................................... 298
Figure 561. Collection Time for HOToWrongCellRlfAfterHOAtSetup ............................................................. 299
Figure 562. Collection Time for TooEarlyHoFailureVoice ............................................................................... 300
Figure 563. Collection Time for TooEarlyHoRlfAfterHoVoice ......................................................................... 300
Figure 564. Collection Time for TooLateHoRlfBeforeTriggeringVoice ............................................................ 301
Figure 565. Collection Time for TooLateHoRlfAfterTriggeringVoice ............................................................... 301
Figure 566. Collection Time for WrongCellRlfAfterTriggeringVoice................................................................ 302
Figure 567. Collection Time for WrongCellRlfAfterHoVoice ........................................................................... 302
List of Figures
List of Tables
Preface
This description provides call flows and detailed description for statistic items
collected in the LTE eNB system for analysis.
Relevance
This manual applies to the following products/software.
Name Type
PKG 9.0.0 P1 Software
Symbols
Symbol Description
Indicates a task.
Indicates a shortcut or an alternative method.
Provides additional information.
Menu Commands
menu | command
This indicates that you must select a command on a menu, where menu is the
name of the menu, and command is the name of the command on that menu.
Preface
Preface
Item Description
♦ DLScheDataTTIBin23
♦ DLScheDataTTIBin24
♦ DLScheDataTTIBin25
♦ DLScheDataTTIBin26
♦ DLScheDataTTIBin27
♦ DLScheDataTTIBin28
♦ DLScheDataTTIBin29
♦ DLScheDataTTIBin30
♦ DLScheDataTTIBin31
♦ DLScheDataTTIBin32
Deleted The following families have been deleted. (Family Display Name)
• SRS SINR Distribution
Updated • The LSM Output Format of the following type has been updated.
o Family Display Name: Massive MIMO Statistics for Downlink
Layer Usage
♦ TotLayerDLWithTM7MUPerTTIAvg
Revision History
The following table lists all versions of this document.
Document Version Publication Date Remarks
1.0 December 2019 First version
2.0 January 2020 Editorial changes done
3.0 July 2020 Counter Families are updated
4.0 August 2020 Counter Families are updated
Related Documentation
• LTE eNB Operation Manual
Chapter 1 Introduction
The Samsung LTE eNB counters report statistical performance measurements by
data samples and data points over time.
The following figure displays the counter structure.
The following table describes the items indicated in the figure above.
The following table outlines the fields used to describe each counter.
Chapter 1 Introduction
Field Description
Visible Shows whether the counter is displayed on the LSM
NE Type NE type
Counter Type The operation of each type
• CC (Cumulative Counter): The NE maintains a running count of the
event being counted. The counter is reset to a well-defined value
(usually 0) at the beginning of each granularity period.
• SI (Status Inspection): Network elements maintain internal counts for
resource management purposes. These counts are read at a
predetermined rate, which is usually based upon the expected rate of
change of the count value. Status inspection measurements can be
reset at the beginning of the granularity period and it can only have a
valid result at the end of the granularity period. Application updates
the based value, it calculates average value automatically. Average
means cumulated value divides with update count meaning.
• GAUGE (Gauge): Gauges represent dynamic variables that may
change in either direction. Gauges can be integer or real values. If a
gauge is required to produce low and high tide marks for a granularity
period (e.g. minimum and maximum call duration), then it is re-
initialized at the beginning of each granularity period.
• OW (Over-Write): Over-Write represents snapshot variables. Over-
Write would be the latest value at the end of the granularity period.
Period Counter gathering period.
Unit A unit of the counter.
• % (percentage)
• s (seconds)
• ms (milliseconds)
• count
• MB (Megabytes)
• Mbps (Megabits per second) and so on
Range Min./Max. A minimum and a maximum value of the counter range.
Hourly, Daily, Monthly Describes the hourly, daily, and monthly formula for the counter.
Calculation
Parameter non- Describes the calculation formula for the non-inputting parameter.
inputting Calculation
Formula
Collection Unit Describes the unit formula for the counter.
Formula
System Feature ID A system feature ID related to the counter.
Reference Call Flow Call flows related to the counter.
Refer to LTE eNB Operation Manual to retrieve statistics data using LSM GUI.
Chapter 2 Counter
Description
The LTE eNB counters with details are listed in the following attached Microsoft
Excel.
Appendix A Acronyms
CC Cumulative Counter
CLI Command Line Interface
GUI Graphic User Interface
LTE Long Term Evolution
NE Network Element
OW Over-Write
SI Status Inspection
RRC
The following figure depicts the statistical definition and message flow for each
stage of the Idle to Active (Service Request) procedure by the UE, which allows to
identify the overall handling of the RRC/E-RAB/S1 SIG statistics.
Step Description
1) The UE performs the Random Access procedure with the eNB.
2)-4) The UE transmits the NAS SERVICE REQUEST message to the MME. The
SERVICE REQUEST message is encapsulated in an RRC message
transmitted to the eNB.
5) The eNB includes the SERVICE REQUEST message in the INITIAL UE
message, which is an S1-AP Control message, and transmits it to the MME.
6) If there is no UE context for the UE in the network, the integrity is not protected
for the ATTACH REQUEST message, or the integrity check fails, an
authentication and an NAS security setup are always performed. The UE
performs the EPS AKA procedure (TS 33.401, 6.1.1) with the MME. The MME
sets up an NAS security association with the UE using the NAS SMC
procedure (TS 33.401, 7.2.4.4).
Step Description
7) The MME transmits the S1-AP Initial Context Setup Request message to the
eNB. This step activates both the radio bearer and S1 bearer for all active EPS
bearers.
8)-11) The eNB sets up the RRC radio bearers. The user plane security is set up at
this step. The uplink data from the UE can be sent to the S-GW by the S-GW.
The eNB transmits the uplink data to the S-GW, and then the S-GW transmits
it to the P-GW.
12) The eNB transmits the INITIAL CONTEXT SETUP RESPONSE message(S1-
AP) to the MME.
13)-14) For each PDN connection, the MME transmits the Modify Bearer Request
message to the S-GW. Now, the S-GW can transmit the downlink data to the
UE. The S-GW transmits the Modify Bearer Response message to the MME.
Call Drop
Figure 98. Collection Time for CallDrop_EccbDspAuditRlcMacCallRelease
For statistics on RRC connection establishment NB, Attempt, Success, Fail, and
Reject statistics are counted.
Attempt statistic is counted when the RRC Connection Request NB message is
received. Success statistic is counted when the messages up to RRC Connection
Setup Complete NB are successfully received.
When a timeout or internal failure occurs during the procedure from 1 to 2 in the
figure above, it is counted as Fail, returning the cause value. Reject statistic is
counted when the eNB determines that the call cannot be accepted after receiving
the RRC Connection Request NB message, and the applicable cause value is
recorded.
Figure 126. Collection Time for NBIoT RRC Connection Establishment (Reject)
The NBIoT RRC Connection setup time is taken from receiving the RRC
Connection Request NB message up to receiving the RRC Connection Setup
Complete NB message.
The eNB calculates and reports to the LSM the average and maximum values for
the collection period (in milliseconds).
E-RAB
E-RAB Setup
Figure 180. Collection Time for E-RAB Setup
The E-RAB setup time indicates the duration from receiving the Initial Context
Setup Request message up to transmitting the Initial Context Setup Response,
which is reported in milliseconds. The statistics block calculates the average and
maximum values of the setup time during the collection period.
The E-RAB setup time is a time taken from receiving the Initial Context Setup
Request message to transmitting the Initial Context Setup Response, and is
reported. The statistics block calculates its average and maximum values at every
collection interval.
The eNB E-RAB erase request refers to deleting the UE context. When the eNB
needs to release the UE context, it transmits the UE Context Release Request
message to the MME, and counts statistics.
E-RAB Erase
Figure 226. Collection Time for E-RAB Erase
E-RAB Modify
Figure 227. Collection Time for E-RAB Modify
E-RAB Release
Figure 239. Collection Time for E-RAB Release
HO EUTRAN
X2 Handover
Figure 309. X2 Based Handover Statistics processing
Step Description
1) The UE transmits the MeasurementReport message according to the system
information, standards and rules.
The source eNB determines whether to perform the UE handover based on
the MeasurementReport message and the radio resource management
information.
2) The source eNB sends the target eNB a HANDOVER REQUEST message
containing the information required for handover. The target eNB can perform
management control in accordance with the E-RAB QoS information received.
3)-4) The target eNB creates the RRCConnectionReconfiguration message which
contains the mobileControlInfo IE for preparing and executing the handover.
The target eNB transmits RRCConnectionReconfiguration to the source eNB,
which is encapsulated in the HANDOVER REQUEST ACKNOWLEDGE
message. The source eNB transmits the RRCConnectionReconfiguration
message and the necessary parameters to the UE to command it to perform
the handover.
5) To transmit the uplink PDCP SN receiver status and the downlink PDCP SN
transmitter status of the E-RABs of which the PDCP status should be
preserved, the source eNB transmits the SN STATUS TRANSFER message
to the target eNB.
6) After receiving the RRCConnectionReconfiguration message that
encapsulates the mobileControlInfo IE, the UE performs synchronization with
the target eNB and accesses the target cell through the Random Access
Step Description
Channel (RACH). The target eNB responds with UL allocation and a timing
advance value.
7) After having connected to the target cell successfully, the UE notifies the target
eNB that the Handover procedure has been completed using an
RRCConnection-ReconfigurationComplete message.
8) The target eNB, using the PATH SWITCH REQUEST message, notifies the
MME that the UE has changed the cell.
9)-10) The MME sends the Modify Bearer Request message to the S-GW. The S-GW
changes the downlink data path into the target eNB. The S-GW transmits at
least one ‘end marker’ to the source eNB through the previous path, and
releases the user plane resources for the source eNB.
The S-GW transmits a Modify Bearer Response message to the MME.
11) The MME transmits the PATH SWITCH REQUEST ACKNOWLEDGE
message to acknowledge the PATH SWITCH REQUEST message
12) The target eNB sends the UE CONTEXT RELEASE message to the source
eNB to notify the handover has succeeded and to make the source eNB
release its resources. If the source eNB receives the UE CONTEXT RELEASE
message, it releases the radio resources and the control plane resources
related to the UE context.
X2 In Handover
Figure 310. Collection Time for X2 In Handover
For Inter-X2 Handover In statistics, Attempt is counted when the target eNB
receives the X2 Handover Request message, and Prepare is counted after the target
eNB transmits the X2 Handover Request Acknowledge message.
The source eNB (target eNB in case of RLF Triggered Handover) transmits the
RRC Connection Reconfiguration message to the UE, and the target eNB receives
the RRC Connection Reconfiguration Complete message from the UE. Success is
counted when the handover is successfully completed and the X2 UE Context
Release message is transmitted to the source eNB.
When the procedure from ① to ② fails, it is counted as Prepare Fail, returning the
cause value.
X2 Out Handover
Figure 336. Collection Time for X2 Handover Out
For Inter-X2 Handover Out statistics, Attempt is counted when the X2 Handover
Request message can be transmitted to the target eNB after the Inter-X2 handover
decision following the Measurement Report message arrival or after receiving
RLF Indication due to RLF triggered Handover procedure.
Prepare is counted when the X2 Handover Request Acknowledge message is
received from the target eNB.
The source eNB (or target eNB in case of RLF Triggered Handover after receiving
RRC Connection Reestablishment Complete) transmits the RRC Connection
Reconfiguration message to the UE, and the target eNB receives the RRC
Connection Reconfiguration Complete message from the UE.
The target eNB transmits the X2 UE Context Release message to the source eNB
when the handover is successfully completed. At this point, the source eNB is
counted as Success. When the procedure from ① to ② fails, it is counted as
Prepare Fail, returning the cause value.
S1 Handover
Figure 352. S1 Handover Procedure
Step Description
1) The source eNB determines whether to perform S1-based handover into the
target eNB. The source eNB can make this decision when there is no X2
connection to the target or when an error is notified by the target eNB after an
X2-based handover has failed, or based on the information the source eNB
has obtained dynamically.
2) The source eNB transmits the HANDOVER REQUIRED message to the MME.
The source eNB notifies the target eNB which bearer is used for data
forwarding and whether the forwarding can be made directly from the source
eNB to the target eNB.
3)-4) The MME transmits the HANDOVER REQUEST message to the target eNB.
This message makes the target eNB create a UE context containing the
bearer-related information and the security context.
The target eNB transmits the HANDOVER REQUEST ACKNOWLEDGE
message to the MME.
5)-6) If indirect forwarding is used, the MME sends the Create Indirect Data
Forwarding Tunnel Request message to the S-GW. The S-GW replies the
Step Description
MME with the Create Indirect Data Forwarding Tunnel Response message.
7)-8) The MME sends the HANDOVER COMMAND message to the source eNB.
The source eNB creates the RRCConnectionReconfiguration message using
the Target to Source Transparent Container IE encapsulated in the
HANDOVER COMMAND message and then transmits it to the UE.
9)-10) To transmit the PDCP and HFN status of the E-RABs of which the PDCP
status must be preserved, the source eNB transmits the eNB/MME STATUS
TRANSFER message to the target eNB via the MME. The source eNB should
start forwarding the downlink data to the target eNB through the bearer which
was determined to be used for data forwarding. This can be either direct or
indirect forwarding.
11) The UE performs synchronization with the target eNB and connects to the
target cell via a RACH.
The target eNB responds with UL allocation and a timing advance value.
12) After having synchronized with the target cell, the UE notifies the target eNB
that the Handover procedure has been completed using the
RRCConnectionReconfigurationComplete message. The downlink packets
forwarded from the source eNB can be transmitted to the UE.
The uplink packets can also be transmitted from the UE to the S-GW through
the target eNB.
13) The target eNB sends the HANDOVER NOTIFY message to the MME. The
MME starts the timer which tells when the resources of the source eNB and
the temporary resources used by the S-GW for indirect forwarding can be
released.
14) The MME transmits the Modify Bearer Request message for each PDN
connection to the S-GW.
Downlink packets are transmitted from the S-GW to the target eNB
immediately.
15) The S-GW transmits a Modify Bearer Response message to the MME. As
soon as the target eNB changes the path to help packet reordering, the S-GW
transmits at least one ‘end marker’ packet to the source eNB through the
previous path.
16) If any of the conditions listed in section 5.3.3.0 of TS 23.401(6) are met, the
UE starts the Tracking Area Update procedure.
17)-18) When the timer started at step 13) expires, the MME sends the UE CONTEXT
RELEASE COMMAND message to the source eNB. The source eNB releases
the resources related to the UE and replies with the UE CONTEXT RELEASE
COMPLETE message.
19)-20) If indirect forwarding has been used, when the timer started at Step 13)
expires the MME transmits the Delete Indirect Data Forwarding Tunnel
Request message to the S-GW. This message gets the S-GW to release the
temporary resources allocated for indirect forwarding at Step 5).
The S-GW responds to the MME with the Delete Indirect Data Forwarding
Tunnel Response message.
S1 In Handover
Figure 353. Collection Time for S1 In Handover
S1 Out Handover
Figure 376. Collection Time for S1 Out Handover
For Inter-S1 Handover Out statistics, Attempt is counted when the S1 Handover
Required message can be transmitted to the MME after the inter S1 handover
decision following the Measurement Report message arrival.
Prepare is counted when the S1 Handover Command message is received from the
MME. The source eNB transmits the RRC Connection Reconfiguration message to
the UE, and the target eNB receives the RRC Connection Reconfiguration
Complete message from the UE.
The MME transmits the S1 UE Context Release Command message to the source
eNB when the handover is successfully completed in the target eNB. At this point,
the source eNB is counted as Success. When the procedure from ① to ② fails, it is
counted as Prepare Fail and returns the cause value, and when the procedure from
② to ③ fails, it is counted as Inter-S1 Out Fail and returns the cause value.
Intra-eNB Handover
Figure 392. Intra-eNB Handover Statistics processing
Step Description
1) Intra eNB handover is determined based on the measurement report.
2) New RLC, MAC and PHY configurations are set for the target cell.
3) When the resource setup is completed in the target cell, the RRC Connection
Reconfiguration message is transmitted to instruct the UE to perform handover.
4) The RRC Connection Reconfiguration Complete message is received to
complete the intra handover successfully.
Intra-eNB In Handover
Figure 412. Collection Time for Intra-eNB In Handover
Figure 443. Collection Time for Preemption Handover per E-RAB (Inter X2)
Figure 444. Collection Time for Preemption Handover per E-RAB (Inter S1)
Preemption Handover
Figure 445. Collection Time for Preemption Handover (Intra eNB)
Handover Time
Figure 448. Collection Time for Handover Time (Intra eNB)
Handover time statistics are based on the Target eNB. Intra handover time refers to
the time taken from transmitting the RRC Connection Reconfiguration message to
the UE until after receiving the RRC Connection Reconfiguration Complete
message. Inter-X2 handover time refers to the time taken from after transmission
of the X2 Handover Request Acknowledge message at the target eNB until
receiving the RRC Connection Reconfiguration Complete message from the UE.
Inter-S1 handover time refers to the time taken from after transmission of the S1
Handover Request Acknowledge message at the Target eNB until receiving the
RRC Connection Reconfiguration Complete message from the UE.
HO UTRAN
This section provides the statistics data for the handover between the LTE system
and UTRAN system for each cell. The following depicts the message flow for the
PS handover procedure from the E-UTRAN to the UTRAN.
Step Description
1) The source eNB determines the PS handover to the UTRAN. This decision is
made according to the measurement report received from the UE.
2) The source eNB transmits the HANDOVER REQUIRED message to the MME.
The source eNB then includes the source RNC to target RNC transparent
container IE information in the message for relaying the necessary information
to the target RNC.
3)-4) The source MME recognizes the handover from the target ID IE of the
HANDOVER REQUIRED message to the UTRAN and transmits the
FORWARD RELOCATION REQUEST message to the target SGSN. The
target SGSN determines whether to change the S-GW. If change is required, it
carries out the Create Session Request/Response procedure with a new S-
GW.
Step Description
5)-6) The target SGSN transmits the RELOCATION REQUEST message to the
target RNC to request resource allocation for the target RNC. The target RNC
performs CAC and resource allocation for each RAB for which handover is
requested, and transmits to the target SGSN the RELOCATION REQUEST
ACKNOWLEDGE message that encapsulates the result. The RELOCATION
REQUEST ACKNOWLEDGE message encapsulates the Target RNC to
Source RNC Transparent Container IE to be transmitted to the source eNB.
7)-9) To perform the forwarding tunnel setup, the target SGSN performs the Create
Indirect Data Forwarding Tunnel Request/Response procedure with target S-
GW and transmits the FORWARD RELOCATION RESPONSE message to the
source MME. To perform the forwarding tunnel setup, the source MME carries
out the Create Indirect Data Forwarding Tunnel Request/Response procedure
with the source S-GW.
10)-11) The source MME transmits the HANDOVER COMMAND message to the
source eNB to complete the handover preparation procedure to the target
UTRAN. The source eNB configures the MOBILITY FROM E-UTRAN
COMMAND containing the Target RNC to Source RNC Transparent Container
IE in the HANDOVER COMMAND message and transmits it to the UE to
request the PS handover to the UTRAN.
12) The UE performs synchronization with the target UTRAN and connects to the
target cell via the RACH.
After UE is successfully connected to the target cell, UE transmits the
HANDOVER TO UTRAN COMPLETE message to the target UTRAN to
complete the handover procedure.
13)-15) The target RNC transmits the RELOCATION COMPLETE message to the
target SGSN to notify that the handover procedure from the UE to the UTRAN
has been completed successfully.
The target SGSN transmits the FORWARD RELOCATION COMPLETE
NOTIFICATION message to the source MME. At this time, the source MME
operates the waiting timer for releasing the resource of the E-UTRAN and
transmits the FORWARD RELOCATION COMPLETE ACKNOWLEDGE
response message to the target SGSN. The target SGSN operates the waiting
timer for releasing the forwarding tunnel at the time when the source MME
receives the response message.
16)-18) The target SGSN transmits the Modify Bearer Request message for each PDN
connection to the target S-GW. Subsequent downlink packets are then
transmitted from the S-GW to the target RNC. The target S-GW performs the
Modify Bearer Request/Response procedure with the P-GW and transmits the
Modify Bearer Response message to the target SGSN.
19) When UE satisfies the conditions specified in section 5.5.2.1 of TS 23.401, the
Routing Area Update procedure starts.
20)-23) When the timer at Step 14) expires, the source MME requests the source eNB
and the source S-GW to release the resources. When the timer at Step 15)
expires, the target SGSN releases the resources release allocated for
forwarding tunnel with the target S-GW.
For the CSFB with Redirection UTRAN statistics, when the Initial Context Setup
Request or the UE Context Modification Request message received has the CSFB
Indicator IE, according to which CSFB is decided, it is counted as an Attempt.
When preparation is completed in the eNB, it is counted as a Prepare. A Success is
counted when the RRC Connection Release message is transmitted to the UE for
redirection.
HO GERAN
CSFB GERAN Redirection
Figure 453. Collection Time for CSFB GERAN Redirection
Packet Statistics
PDCP Packet
Figure 454. Collection Time for EnbQciULByte, PacketULCnt
VoLTE
VoLTE Handover
Figure 459. Collection Time for VoLTE Intra handover
Semi-Persistent Scheduling
Figure 468. Collection Time for ULSpsConfigAtt and ULSpsConfigSucc
TTI Bundling
Figure 469. Collection Time for TTIBActAtt and TTIBActSucc
GTP
GTP Forward Traffic
Figure 471. Collection Time for GTP Forward Traffic (1)
D2D Services
D2D Direct Discovery
Figure 474. Collection Time for Discovery Related Counters
Scheduler
Measurement Report
Figure 478. Collection Time for Measurement Report
eMBMS
MBMS eNB Signaling
Figure 479. Collection Time for M2ConnEstabAtt (1)
Carrier Aggregation
Carrier Aggregation capable UEs (PCell)
Figure 507. Collection Time for Carrier Aggregation capable UEs in Initial Attach case
Figure 508. Collection Time for Carrier Aggregation capable UEs in RRE case
Figure 509. Collection Time for Carrier Aggregation capable UEs in S1 Handover case
Figure 510. Collection Time for Carrier Aggregation capable UEs in X2 Handover case
Figure 512. Collection Time for UL SCell Addition for Intra eNB Handover
Figure 513. Collection Time for UL SCell Addition for RRC Connection Reestablishment
Figure 514. Collection Time for UL SCell Carrier Change for event A1
Figure 515. Collection Time for UL SCell Change for A6 event case
Figure 516. Collection Time for UL SCell Configuration Deconfiguration for A1 and A2 event
S1SIG
UE-associated logical S1 Connection Establishment
Figure 517. Collection Time for S1SIG (1)
Paging
Paging
Figure 527. Collection Time for Paging
NB-IoT Paging
Figure 528. Collection Time for NBIoT_AttPaging
SRB
NB-IoT Cell PDCP SDU Bit Rate
Figure 530. Collection Time for NBIoT_PdcpSduBitrateULAvg
DRB
Packet Drop Rate
Figure 532. Collection Time for PdcpSduDropRateDL
Load Balancing
Load
Figure 537. Collection Time for Load
Load Histogram
Figure 538. Collection Time for Load Histogram
Overload Protection
Denied Call by Overload Protection
Figure 539. Denied Call by Overload Protection
UE Category
UE Category
Figure 540. Collection Time for UE Category (1)
MRO
MRO RLF Classification
Figure 544. Collection Time for CoverageHole
OnDemand Handover
OnDemand Handover X2 In
Figure 571. Collection Time for X2 Hand-in Statistics by On-demand Handover
OnDemand Redirection
Figure 573. Collection Time for Redirection Statistics by On-demand Handover
Released UE by Timer
Figure 574. Collection Time for ReleaseCntByTimer
KPI
Accessibility
This KPI shows the probability for an end-user to be provided with an E-RAB at
request.
• Probability Success Rate for E-RABs Establishment
• Successful attempts compared with total number of attempts for the different
parts of the E-RAB establishment
Retainability
This section provides statistics on a measurement that shows how often an end-
user abnormally loses an E-RAB during the time the E-RAB is used. This statistics
item is collected for each cell.
Integrity
This section provides statistics on the data that shows how E-UTRAN impacts the
service quality provided to an end-user.
• Payload data volume on IP level per elapsed time unit on the Uu interface.
• E-UTRAN IP Throughput
• E-UTRAN IP Latency
Availability
This section provides statistics on the availability of an E-UTRAN cell.
• Percentage of time that the cell is considered available.
• The elapsed time from the cell down due to the fault until its recovery.
• E-UTRAN Cell Availability
Mobility
This section provides statistics on the data that shows how E-UTRAN Mobility
functionality is working.
• Success rate of E-UTRAN mobility
VoLTE Quality
This section provides statistics on the VoLTE Quality for QCI #1 Bearer.
• The number of VoLTE Drop rate
• The number of UL Quality Defect rate
• The number of DL Quality Defect rate
• The number of VoLTE HO Intra Success rate
• The number of VoLTE HO X2 Success rate
• The number of VoLTE HO S1 Success rate
UDC
The number of active E-RAB configured with UDC
Figure 575. Collection Time for UdcReset
Message
NB-IoT RRC Message
Figure 579. Collection Time for NBIoT_RrcConnectionReconfiguration
ANR
ECGI Report
Figure 586. Collection Time for ECGI Report