410-mmbs-operation-manual_v1.1.pdf

Ver.

2600-00CZU3GA4

1.1

410 MMBS

Operation Manual

COPYRIGHT

This manual is proprietary to SAMSUNG Electronics Co., Ltd. and is protected by copyright.

No information contained herein may be copied, translated, transcribed or duplicated for any commercial

purposes or disclosed to the third party in any form without the prior written consent of SAMSUNG Electronics

Co., Ltd.

TRADEMARKS

Product names mentioned in this manual may be trademarks and/or registered trademarks of their respective

companies.

©2011~2012 SAMSUNG Electronics Co., Ltd. All rights reserved.

This manual should be read and used as a guideline for properly installing and operating the product.

This manual may be changed for the system improvement, standardization and other technical reasons

without prior notice.

Updated manuals are available at:

https://systems.samsungwireless.com/

For questions on the manuals or their content, contact

[email protected]

https://systems.samsungwireless.com/

mailto:[email protected]

410 MMBS Operation Manual

© SAMSUNG Electronics Co., Ltd. I

INTRODUCTION

Purpose

The Long Term Evolution (LTE) EUTRAN Node B (eNB) Operation Manual describes the

procedure for controlling the eNB system to provide the operators with the system

operation information necessary to control and manage the system.

Document Content and Organization

This manual consists of 10 Chapters, 1 Annex, and a list of Abbreviations.

CHAPTER 1. Call Processing

Describes the various procedures performed to process calls in the LTE eNB system, call

processing-related parameters, call processing algorithms, etc.

CHAPTER 2. Configuration

Describes configuration management for the LTE eNB system.

CHAPTER 3. Loading

Describes the loading function of the LTE eNB system.

CHAPTER 4. Status

Describes the procedure for managing the status of the LTE eNB system.

CHAPTER 5. Diagnosis Functions

Describes the procedure for diagnosing the LTE eNB system.

CHAPTER 6. Grow and Degrow

Describes the procedures for growing and degrowing resources in the LTE eNB system.

CHAPTER 7. SON

Describes the Self Organizing Network (SON) function of the LTE eNB system.


© SAMSUNG Electronics Co., Ltd. II

CHAPTER 8. QoS Control

Describes the Quality of Service (QoS) function of the LTE eNB system.

CHAPTER 9. Fault

Describes the LTE eNB alarms and how to control them.

CHAPTER 10. Statistics

Describes the statistics items of the LTE eNB and the procedures for viewing and analyzing

statistics data.

ANNEX A. Open Source Announcement

Describes Open Source Announcement.

ABBREVIATIONS

This provides explanations of the abbreviations used throughout this manual.

Conventions

The following types of paragraphs contain special information that must be carefully read

and thoroughly understood. Such information may or may not be enclosed in a rectangular

box, separating it from the main text, but is always preceded by an icon and/or a bold title.

NOTE

Indicates additional information as a reference.

Console Screen Output

The lined box with „Courier New‟ font will be used to distinguish between the

main content and console output screen text.

„Bold Courier New‟ font will indicate the value entered by the operator on the

console screen.


© SAMSUNG Electronics Co., Ltd. III

Revision History

EDITION DATE OF ISSUE REMARKS

1.0 10. 2011. First Edition

1.1 02. 2012. Revised the following items.

- 1.6.1 LTE-HRPD Interoperation

- 8.4 CQI Control

- 8.6 Power Control

- Chapter 10. Statistics (modified the chapter overall)


© SAMSUNG Electronics Co., Ltd. IV

SAFETY CONCERNS

The purpose of the Safety Concerns section is to ensure the safety of users and prevent

property damage. Please read this document carefully for proper use.

Symbols

Caution

Indication of a general caution

Restriction

Indication for prohibiting an action for a product

Instruction

Indication for commanding a specifically required action


© SAMSUNG Electronics Co., Ltd. V

Caution

DU Reset

Resetting the DU restarts its CPU and other related units as well, by interrupting

the power supply to them.

Updating a Call Processing Block

Updating a specific block that performs call processing may prevent services from

being provided.

Updating a Block Related to Command Processing

Updating the loading block, or SNMP block, which are related to command

processing, may not provide the command execution results.

Upgrading CPLD Firmware

If the CPLD firmware has been upgraded, the master board may be reset

automatically and service may be stopped.

Updating firmware

Updating any incompatible/unverified firmware may lead to particular hardware

not function at all once it is reset. Further, power supply interruption during any

firmware update can damage the updating board(s) or device(s).

CAUTION


© SAMSUNG Electronics Co., Ltd. VI

TABLE OF CONTENTS

INTRODUCTION I

Purpose ....................................................................................................................................................... I

Document Content and Organization ........................................................................................................ I

Conventions ............................................................................................................................................... II

Console Screen Output ............................................................................................................................. II

Revision History ........................................................................................................................................ III

SAFETY CONCERNS IV

Symbols ................................................................................................................................................... IV

Caution ...................................................................................................................................................... V

CHAPTER 1. Call Processing 1-1

1.1 Call Processing S/W Block .................................................................................................... 1-1

1.2 Cell Setup ................................................................................................................................ 1-5

1.3 System Information Control .................................................................................................. 1-8

1.4 RRC ........................................................................................................................................ 1-12

1.4.1 Paging Control ....................................................................................................................... 1-12

1.4.2 RRC Connection establishment/release .............................................................................. 1-13

1.4.3 RRC Connection reconfiguration ......................................................................................... 1-23

1.4.4 Security .................................................................................................................................. 1-33

1.4.5 NAS message Transmission ................................................................................................ 1-35

1.4.6 Measurement Configuration and Reporting ........................................................................ 1-37

1.4.7 E-RAB Bearer Control ........................................................................................................... 1-41

1.4.8 RRC Connection Re-establishment ..................................................................................... 1-44

1.4.9 UE Inactivity Control .............................................................................................................. 1-47

1.4.10 RLF Control ........................................................................................................................... 1-48

1.5 Intra-LTE Handover .............................................................................................................. 1-49

1.5.1 Intra-eNB Handover .............................................................................................................. 1-49

1.5.2 Inter-eNB X2 Handover ........................................................................................................ 1-50

1.5.3 Inter-eNB S1 Handover ........................................................................................................ 1-52

1.6 Inter-RAT Mobility ................................................................................................................. 1-56


© SAMSUNG Electronics Co., Ltd. VII

1.6.1 LTE-HRPD Interoperation...................................................................................................... 1-56

1.6.2 LTE-1xRTT Interoperation CS Fallback ................................................................................ 1-62

1.7 CAC ....................................................................................................................................... 1-65

1.8 Overload Control ................................................................................................................. 1-71

1.8.1 eNB Overload Control ............................................................................................................ 1-71

1.8.2 MME Overload Control .......................................................................................................... 1-73

1.9 MME Selection Control ........................................................................................................ 1-78

1.10 Call Trace Control ................................................................................................................ 1-81

1.10.1 Management Based Trace .................................................................................................... 1-81

1.10.2 Signaling Based Trace ........................................................................................................... 1-86

1.10.3 Trace Data Information .......................................................................................................... 1-88

1.11 CSL ........................................................................................................................................ 1-93

1.11.1 CSL Data ................................................................................................................................. 1-93

1.12 S1 AP Related Control ......................................................................................................... 1-97

1.12.1 S1 Setup ................................................................................................................................. 1-97

1.12.2 S1 Reset ................................................................................................................................. 1-99

1.12.3 S1 eNB Configuration Update .............................................................................................1-102

1.13 X2 AP Related Control ....................................................................................................... 1-104

1.13.1 X2 AP Setup .........................................................................................................................1-104

1.13.2 X2 AP Reset .........................................................................................................................1-105

1.13.3 X2 AP eNB Configuration update ........................................................................................1-106

1.14 Preemption Control ........................................................................................................... 1-108

CHAPTER 2. Configuration 2-1

2.1 Resource Grow/Degrow ........................................................................................................ 2-1

2.2 Resource Service Control ..................................................................................................... 2-3

2.3 Parameter Control.................................................................................................................. 2-3

2.4 Retrieving Parameters ......................................................................................................... 2-21

CHAPTER 3. Loading 3-1

3.1 Reset ....................................................................................................................................... 3-2

3.1.1 Individual Hardware Unit Reset ............................................................................................... 3-2

3.1.2 All NE Reset ............................................................................................................................. 3-3

3.2 Software Management ........................................................................................................... 3-4

3.3 Firmware Management .......................................................................................................... 3-8

3.4 NTP Server Management ......................................................................................................3-11


© SAMSUNG Electronics Co., Ltd. VIII

3.5 Inventory Management ........................................................................................................ 3-12

CHAPTER 4. Status 4-1

4.1 Processor Status .................................................................................................................... 4-2

4.2 Processor Resource Status ................................................................................................... 4-2

4.3 Call Resource Status .............................................................................................................. 4-3

4.4 Device Status .......................................................................................................................... 4-4

4.4.1 GPSR Status Management .....................................................................................................4-4

4.4.2 RRH Status Management ........................................................................................................4-5

4.5 Link Status .............................................................................................................................. 4-7

4.6 S1/X2 Status ............................................................................................................................ 4-7

4.7 PRB Usage Status .................................................................................................................. 4-7

4.8 Inventory Information ............................................................................................................. 4-8

CHAPTER 5. Diagnosis Functions 5-1

5.1 External Ping Diagnosis ........................................................................................................ 5-4

5.1.1 External Ping Online Diagnosis ...............................................................................................5-5

5.2 Internal Ping Diagnosis .......................................................................................................... 5-6

5.2.1 Internal Ping Online Diagnosis ................................................................................................5-6

5.3 Transmission RF Power Diagnosis ....................................................................................... 5-8

5.3.1 Tx Power Online Test ...............................................................................................................5-9

5.4 VSWR Diagnosis................................................................................................................... 5-10

5.5 OCNS ..................................................................................................................................... 5-12

5.6 Model Diagnosis ................................................................................................................... 5-13

5.7 Trace Route Diagnosis ......................................................................................................... 5-14

5.8 Loopback Diagnosis ............................................................................................................ 5-15

5.9 Bit Error Rate Diagnosis ...................................................................................................... 5-16

5.10 Ethernet Loopback Function ............................................................................................... 5-17

5.11 RET Device Test .................................................................................................................... 5-18

5.12 Battery Test ........................................................................................................................... 5-19

5.12.1 Battery Test Online Diagnosis ............................................................................................... 5-19

5.13 Cell Traffic Trace ................................................................................................................... 5-21

5.14 EtherOAM .............................................................................................................................. 5-25


© SAMSUNG Electronics Co., Ltd. IX

CHAPTER 6. Grow and Degrow 6-1

6.1 eNB Grow/Degrow ................................................................................................................. 6-4

6.1.1 eNB Grow ................................................................................................................................. 6-4

6.1.2 eNB Degrow ............................................................................................................................. 6-6

6.2 CELL Grow/Degrow ............................................................................................................... 6-7

6.2.1 CELL Grow ............................................................................................................................... 6-7

6.2.2 CELL Degrow ........................................................................................................................... 6-8

6.3 RRH Grow/Degrow ................................................................................................................. 6-9

6.3.1 RRH Grow ................................................................................................................................ 6-9

6.3.2 RRH Degrow ............................................................................................................................ 6-9

CHAPTER 7. Self Organizing Network (SON) 7-1

7.1 SE ............................................................................................................................................ 7-3

7.2 ANR ......................................................................................................................................... 7-5

7.2.1 Initial NRT ................................................................................................................................. 7-5

7.2.2 ANR through UE Measurement .............................................................................................. 7-6

7.3 PCI ......................................................................................................................................... 7-10

7.4 RACH .....................................................................................................................................7-11

7.5 ES .......................................................................................................................................... 7-13

7.5.1 Schedule-based Energy Saving ............................................................................................ 7-14

7.5.2 Traffic-based Energy Saving ................................................................................................. 7-16

7.6 Self Optimization ................................................................................................................. 7-20

7.6.1 RRH Optic Delay Automatic Compensation ......................................................................... 7-20

CHAPTER 8. QoS Control 8-1

8.1 ARQ Control ........................................................................................................................... 8-1

8.2 HARQ Control ........................................................................................................................ 8-2

8.3 AMC Control ........................................................................................................................... 8-2

8.4 CQI Control ............................................................................................................................. 8-3

8.5 Scheduling Algorithm Control .............................................................................................. 8-4

8.6 Power Control ........................................................................................................................ 8-7

8.7 DRX ......................................................................................................................................... 8-9


© SAMSUNG Electronics Co., Ltd. X

CHAPTER 9. Fault 9-1

9.1 Alarm Overview ...................................................................................................................... 9-1

9.2 Alarm Output .......................................................................................................................... 9-3

9.3 Alarm Correlation ................................................................................................................... 9-4

9.4 Alarm Control ......................................................................................................................... 9-5

9.5 Alarm-Related Commands ..................................................................................................... 9-7

9.5.1 Retrieving Alarm Information ...................................................................................................9-7

9.5.2 Retrieving Alarm Status ............................................................................................................9-7

9.5.3 Retrieving Alarm History ..........................................................................................................9-8

9.5.4 Retrieving/Changing Alarm Inhibition ......................................................................................9-9

9.5.5 Retrieving/Changing Alarm Severity ..................................................................................... 9-11

9.5.6 Retrieving/Changing Alarm Threshold ................................................................................. 9-12

9.5.7 Retrieving/Changing UDA .................................................................................................... 9-13

CHAPTER 10. Statistics 10-1

10.1 Collecting Statistics and Creating Statistics Files ............................................................. 10-1

10.2 Setting and Viewing the Statistics Configuration .............................................................. 10-3

10.3 Statistics Items ................................................................................................................... 10-10

10.3.1 Resource Management ...................................................................................................... 10-21

10.3.2 Packet Statistics................................................................................................................... 10-23

10.3.3 RRC ..................................................................................................................................... 10-37

10.3.4 ERAB ................................................................................................................................... 10-55

10.3.5 Handover (HO) .................................................................................................................... 10-76

10.3.6 CSFB .................................................................................................................................. 10-105

10.3.7 CSL ..................................................................................................................................... 10-111

10.3.8 MRO_RLF ......................................................................................................................... 10-142

10.3.9 GTP .................................................................................................................................... 10-145

10.3.10 SRB .................................................................................................................................. 10-155

10.3.11 DRB .................................................................................................................................. 10-157

10.3.12 RRU ................................................................................................................................. 10-165

10.3.13 S1SIG .............................................................................................................................. 10-169

10.3.14 PAG .................................................................................................................................. 10-171

10.3.15 POWER ........................................................................................................................... 10-173

10.3.16 Random Access (RA) ..................................................................................................... 10-181

10.3.17 HARQ status .................................................................................................................... 10-183

10.3.18 AMC ................................................................................................................................. 10-190

10.3.19 KPI.................................................................................................................................... 10-213


© SAMSUNG Electronics Co., Ltd. XI

ANNEX A. Open Source Announcement A-1

ABBREVIATION I

A ~ D ......................................................................................................................................................... I

E ~ I ........................................................................................................................................................ II

L ~ P ....................................................................................................................................................... III

Q ~ P ....................................................................................................................................................... IV

LIST OF FIGURES

Figure 1.1 Control Plane Protocol Stack Architecture ............................................................. 1-2

Figure 1.2 User Plane Protocol Stack Architecture ................................................................. 1-2

Figure 1.3 LTE eNB Call Processing S/W Architecture .......................................................... 1-3

Figure 1.4 Cell Setup Request Procedure .............................................................................. 1-5

Figure 1.5 Paging Procedure................................................................................................ 1-12

Figure 1.6 Switching from Idle to Active Procedure .............................................................. 1-13

Figure 1.7 RRC Connection Release Procedure .................................................................. 1-15

Figure 1.8 Security Setup Procedure between eNB and UE ................................................ 1-33

Figure 1.9 Downlink NAS Transmission Procedure .............................................................. 1-35

Figure 1.10 Uplink NAS Transmission Procedure ................................................................ 1-35

Figure 1.11 E-RAB Setup Procedure .................................................................................... 1-41

Figure 1.12 E-RAB Release Procedure ................................................................................ 1-42

Figure 1.13 E-RAB Modification Procedure .......................................................................... 1-43

Figure 1.14 RRC Connection Reestablishment Procedure .................................................. 1-45

Figure 1.15 UE Inactivity Control Procedure ........................................................................ 1-47

Figure 1.16 Intra-eNB Handover Procedure ......................................................................... 1-49

Figure 1.17 Inter-eNB X2 Handover Procedure.................................................................... 1-50

Figure 1.18 Inter-eNB S1 Handover Procedure.................................................................... 1-53

Figure 1.19 LTE-HRPD Interoperation Procedure 1 ............................................................. 1-57



Figure 1.22 LTE-1xRTT Interoperated CS Fallback Procedure 1 ......................................... 1-62

Figure 1.23 LTE-1xRTT Interoperated CS Fallback Procedure 2 ......................................... 1-63

Figure 1.24 CAC Procedure ................................................................................................. 1-65

Figure 1.25 RRC Connection Establishment CAC Procedure .............................................. 1-66

Figure 1.26 E-RAB (DRB) Establishment CAC Procedure ................................................... 1-67

Figure 1.27 Intra-eNB HO CAC Procedure .......................................................................... 1-68


© SAMSUNG Electronics Co., Ltd. XII

Figure 1.28 Inter-eNB HO CAC Procedure ........................................................................... 1-69

Figure 1.29 eNB Overload Control Structure......................................................................... 1-72

Figure 1.30 MME Overload Control Message Procedure ..................................................... 1-74

Figure 1.31 Procedure After Receiving RRCConnectionRequest ......................................... 1-75

Figure 1.32 Procedure After Receiving RRCConnectionSetupComplete .............................. 1-76

Figure 1.33 MME Selection Control Procedure ..................................................................... 1-78

Figure 1.34 MME Selection Control Algorithm Execution Flow ............................................. 1-79

Figure 1.35 Management Based Trace Activation (New Calls) ............................................. 1-82

Figure 1.36 Management Based Trace Activation

(for a call for which call setup is proceeding) ..................................................... 1-83

Figure 1.37 Management Based Trace Deactivation ............................................................ 1-85

Figure 1.38 Signaling Based Trace Activation ....................................................................... 1-86

Figure 1.39 Signaling Based Trace Deactivation .................................................................. 1-87

Figure 1.40 CSL Data Flow ................................................................................................... 1-93

Figure 1.41 S1 Setup Procedure ........................................................................................... 1-97

Figure 1.42 S1 Setup Unsuccessful Operation (Timeout) ..................................................... 1-98

Figure 1.43 S1 Setup Failure Operation (Failure) ................................................................. 1-98

Figure 1.44 S1 Reset Reception Procedure.......................................................................... 1-99

Figure 1.45 MsgCeccbCellReleaseInd Reception Procedure ............................................. 1-100

Figure 1.46 ECCB Operation Procedure When Receiving the Reset Request Message .... 1-101

Figure 1.47 S1 NB eNB Configuration Update Procedure .................................................. 1-102

Figure 1.48 S1 eNB Configuration Update Timeout ............................................................ 1-102

Figure 1.49 S1 eNB Configuration Update Failure .............................................................. 1-103

Figure 1.50 X2 AP Setup Procedure 1 ................................................................................ 1-104

Figure 1.51 X2 AP Reset Procedure 2 ................................................................................ 1-104



Figure 1.54 X2 AP eNB Configuration Update Procedure 1 ................................................ 1-106

Figure 1.55 X2 AP eNB Configuration Update Procedure 2 ................................................ 1-106

Figure 1.56 Pre-emption Control Procedure ....................................................................... 1-109

Figure 2.1 Cell State Transition Diagram ................................................................................ 2-2

Figure 5.1 TM and Test Performing Blocks and Interfaces ...................................................... 5-1

Figure 5.2 BER measurement section .................................................................................. 5-16

Figure 5.3 Selecting the Call Trace Menu ............................................................................. 5-22

Figure 5.4 Registering Cell Traffic Trace ............................................................................... 5-22

Figure 5.5 Retrieving Cell Traffic Trace Result ...................................................................... 5-24

Figure 6.1 Grow/Degrow State Transition Diagram ................................................................. 6-3


© SAMSUNG Electronics Co., Ltd. XIII

Figure 7.1 SON Function in Action ......................................................................................... 7-1

Figure 7.2 eNB Self Establishment Process ........................................................................... 7-3

Figure 7.3 Base Station Grow Window (Initial NRT) ............................................................... 7-5

Figure 7.4 Event Window (Initial NRT) ................................................................................... 7-6

Figure 7.5 eNB Grow Window (Performing the PCI function) ............................................... 7-10

Figure 7.6 Event Window (Performing the PCI function) ...................................................... 7-10

Figure 7.7 eNB Grow Window (Performing the RACH function)............................................ 7-11

Figure 7.8 Event Window (Performing the RACH function) .................................................. 7-12

Figure 9.1 Alarm Detection and Reporting of the eNB System............................................... 9-1

Figure 9.2 Alarm Code ........................................................................................................... 9-2

Figure 9.3 LSM Alarm Output Window ................................................................................... 9-3

Figure 10.1 Collecting and Reporting Statistics (PM Data) ................................................... 10-1

Figure 10.2 RRC Connection Establishment (Success) collection time ............................. 10-39

Figure 10.3 RRC Connection Establishment (Reject) collection time ................................. 10-40

Figure 10.4 RRC Connection Reconfiguration collection time ............................................ 10-42

Figure 10.5 RRC Connection Re-establishment (Success) collection time ........................ 10-44

Figure 10.6 RRC Connection Re-establishment (Reject) collection time ........................... 10-45

Figure 10.7 RRC Connection Release collection time ........................................................ 10-47

Figure 10.8 RRC Connection Setup Time collection time ................................................... 10-50

Figure 10.9 RRC connection Reestablishment Time collection time .................................. 10-52

Figure 10.10 E-RAB Setup collection time ......................................................................... 10-57

Figure 10.11 Additional E-RAB Setup collection time ......................................................... 10-59

Figure 10.12 E-RAB Setup Time (initial E-RAB Setup) collection time ............................... 10-61

Figure 10.13 E-RAB Setup Time (additional E-RAB Setup) collection time ........................ 10-62

Figure 10.14 E-RAB Erase Request collection time ........................................................... 10-64

Figure 10.15 E-RAB Erase collection time ......................................................................... 10-66

Figure 10.16 E-RAB Modify collection time ........................................................................ 10-68

Figure 10.17 E-RAB Release Request collection time ....................................................... 10-70

Figure 10.18 E-RAB Release collection time...................................................................... 10-72

Figure 10.19 Intra eNB Handover collection time ............................................................... 10-78

Figure 10.20 X2 Handover Out collection time ................................................................... 10-81

Figure 10.21 X2 Handover In collection time ...................................................................... 10-84

Figure 10.22 S1 Handover Out collection time ................................................................... 10-87

Figure 10.23 S1 Handover In collection time ...................................................................... 10-90

Figure 10.24 Inter-RAT HRPD Handover (other than eNB) collection time ........................ 10-93

Figure 10.25 Inter-RAT UTRAN PS Handover OUT collection time ................................... 10-96

Figure 10.26 Inter-RAT UTRAN PS Handover IN collection time ....................................... 10-99

Figure 10.27 Handover Time (INTRA) collection time ...................................................... 10-102


© SAMSUNG Electronics Co., Ltd. XIV

Figure 10.28 Handover Time (INTER S1) collection time ................................................. 10-103

Figure 10.29 Handover Time (INTER X2) collection time ................................................. 10-104

Figure 10.30 CSFB PS Handover OUT collection time ..................................................... 10-107

Figure 10.31 CSFB Redirection OUT collection time ........................................................ 10-110

Figure 10.32 S1SIG collection time ................................................................................... 10-170

Figure 10.33 PAGING collection time ............................................................................... 10-172


© SAMSUNG Electronics Co., Ltd. 1-1

CHAPTER 1. Call Processing

1.1 Call Processing S/W Block

The LTE eNB system is located between the EPC and the UE. The LTE eNB software

consists of multiple function blocks or libraries that carry out call flow control in

accordance with the LTE Air standard, transmission and receipt of wireless signals,

modulation and demodulation of packet traffic, packet scheduling for efficient utilization of

wireless resources, Automatic Repeat Request (ARQ) processing, Hybrid ARQ (HARQ)

processing, packet header compression, wireless resources control, handover control, S1

interfacing, X2 interfacing, and security functions. The LTE eNB software is designed in a

way that these function blocks interwork with each other.



LTE eNB Protocol Stack Architecture

The LTE eNB radio protocol architecture consists of control plane (RRC) and user plane

(PDCP/RLC/MAC/PHY) protocols. The figures below show the protocol stack

architectures of the control plane and user plane. The interfaces between systems consist of

an S1 interface (between the eNB and EPC), X2 interface (between the eNB and another

eNB), and Uu interface (between the eNB and UE).

Figure 1.1 Control Plane Protocol Stack Architecture

Figure 1.2 User Plane Protocol Stack Architecture

PHY

MAC

RLC

PDCP

RRC

PMM

SM

UE

PHY

MAC

RLC

PDCP

RRC

eNB

Relay

L1

L2

SCTP

S1AP

IP

L1

IP

SCTP

S1AP

PMM

SM

EPC

L2

PHY

MAC

RLC

eNB

L1

L2

UDP

GTP-U

IP

L1

UDP

GTP-U

EPC

L2

PHY

MAC

RLC

PDCP

Other EPC

IP

UE

PDCP Relay

IP

IP



LTE eNB Call Processing S/W Architecture

The LTE eNB software consists of two subsystems, which are divided functionally based

on a layered protocol stack to support the LTE eNB‟s protocol stack architecture.

These two subsystems are the eNB Control Subsystem (ECS) that controls the control

plane, and the eNB Data Subsystem (EDS) that controls the user plane.

Each subsystem consists of software blocks that carry out the protocol functions of the LTE

eNB. Each software block has a modular structure for each function.

Figure 1.3 LTE eNB Call Processing S/W Architecture

EPC

Other eNB

ECMM

ESCM

ERCM

ERRM

ECCM

EHCM

SCTB

GTPB

PDCB

RLCB

MACB

PHY

UE

S1-C X2-C S1-U X2-U

LTE eNB

eNB Control

Subsystem (ECS)

ECMB

ECCB

eNB Data

Subsystem (EDS)

Uu

: Control (IPC) : Traffic : Socket Interface (UDP port)

S1-C: eNB EPC control plane/X2-C: eNB eNB control plane

S1-U: eNB EPC user plane/X2-U: eNB eNB user plane



Software Blocks and Their Functions

S/W Block Plane Function Description

eNB Common

Management Block

(ECMB)

control eNB Common Management Module (ECMM)

- Base station initialization and common channel setup

eNB System Information Control Module (ESCM)

- System information transmission for UE initialization

eNB Cell Resource Control Module (ERCM)

- Load control for controlling cell or system overload

eNB Call Control Block

(ECCB)

control eNB Radio Resource control Module (ERRM)

- Radio Resource Management

- Call Admission Control

eNB Call Control Module (ECCM)

- RRC/S1-AP ASN.1 interfacing

- Basic call connection control

- S1-AP Paging processing

- Complementary functions

- Call Summary LOG (CSL) processing

- Call Trace

- Statistics processing

eNB Handover call Control Module (EHCM)

- X2-AP ASN.1 interfacing

- Handover call control

Stream Control

Transmission protocol

Block (SCTB)

control - S1-C SCTP interfacing

- X2-C SCTP interfacing

- S1/X2 AP message transmission

GPRS Tunneling Protocol

Block (GTPB)

user General Packet Radio Service (GPRS) Tunneling Protocol

function for data access in the S1-U or X2-U interface

Packet Data

Convergence protocol

Block (PDCB)

user - Header compression/decompression for IP packet streams

- Ciphering, Integrity

- Downlink (DL)/Uplink (UL) data forwarding at handover

- PDCP sequence number maintenance

- Timer based PDCP SDU discard

Radio Link Control Block

(RLCB)

user - Radio link control and Automatic Repeat Request (ARQ)

- RLC SDU concatenation, segmentation and reassembly

- In sequence delivery

- RLC re-establishment

- RLC PDU re re-segmentation

- Paging

Medium Access Control

Block (MACB)

user - Mapping between the logical and transport channels

- HARQ

- Dynamic scheduling between UEs

- AMC

- ICIC

- DRX



5) msgCrlcCommonConfigCnf

OAM ECMB RLCB MACB

2) msgCmacPhyCommonConfigReq

3) msgCmacPhyCommonConfigCnf

4) msgCrlcCommonConfigReq

6) msgCmacSystemInfoSetupReq

8) msgCellSetupRsp

7) msgCmacSystemInfoSetupCnf

1) msgEcmbCellSetupReq

1.2 Cell Setup

Cell Setup refers to a series of procedures where the RRC layer and its lower layers set

both the cell setup parameters and the common transport channel setup parameters to the

same values in a particular cell to make it available.

Figure 1.4 Cell Setup Request Procedure

Refer to Command Description

Parameter description of command refer to „Input parameter description‟ of

„Command description‟.



RLC Layer-Related Cell Setup Commands

You can use RLC layer-related cell setup commands by selecting a target on the CLI of the

LTE System Manager (LSM) and a command in the „Command‟ tab, or by searching and

selecting a command in the „Search‟ tab.

The table below lists the commands used for RLC layer-related cell setup.

Commands Description

RTRV-BCCH-CONF Retrieves the configuration information for the Broadcast Control Channel

(BCCH) within the base station. It can retrieve/change the value that

controls the modification period of the system information.

CHG-BCCH-CONF

RTRV-PCCH-CONF Retrieves/Changes the configuration information for the Paging Control

Channel (PCCH) within the base station. The paging is used to initiate a

mobile terminating connection, to trigger the UE to re-acquire the system

information, or to send an Earthquake and Tsunami Warning System

(ETWS) indication to the UE.

CHG-PCCH-CONF

RTRV-CELL-IDLE Retrieves/changes the cell parameters being managed by the base station.

CHG-CELL-IDLE

MAC Layer-Related Cell Setup Commands

You can use RLC layer-related cell setup commands by selecting a target on the CLI of the

LSM and a command in the „Command‟ tab, or by searching and selecting a command in

the „Search‟ tab. The table below lists the commands used for MAC layer-related cell setup.


RTRV-DL-SCHED Retrieves/Changes the configuration information of the download

scheduling for the MAC layer within the base station.

It can retrieve/change the alpha, beta and gamma values used to set the

scheduler for the fairness, channel quality and priority.

CHG-DL-SCHED

RTRV-UL-SCHED Retrieves/Changes the configuration information of the uplink scheduling

for the MAC layer within the base station. It can retrieve/change the alpha,

beta and gamma values used to set the scheduler for the fairness, channel

quality and priority.

CHG-UL-SCHED

RTRV-CELL-IDLE Retrieves/changes the cell parameters being managed by the base station.

CHG-CELL-IDLE

RTRV-PHICH-IDLE Retrieves/Changes the configuration information for the Physical Hybrid

ARQ Indicator Channel (PHICH) within the base station.

It can retrieve/change the settings for the PHICH duration and resource.

CHG-PHICH-IDLE

RTRV-RACH-CONF Retrieves/Changes the configuration information for the Random Access

Channel (RACH) within the base station. It can retrieve/change the number

of backoff indicators and Msg3 HARQ transmissions, the number of non-

dedicated/dedicated preambles, the number of power ramping steps and

maximum transmissions, and the number of preamble groups A and B.

CHG-RACH-CONF



(Continued)


RTRV-RACH-IDLE Retrieves/Changes the configuration information for the Random Access

Channel (RACH) within the base station. It can retrieve/change the UE‟s

wait time for the RA response.

CHG-RACH-IDLE

RTRV-PRACH-CONF Retrieves/Changes the configuration information for the Physical Random

Access Channel (PRACH) within the base station. It can retrieve/change

the high speed flag, PRACH configuration index, root sequence index,

and zero correlation zone configuration.

CHG-PRACH-CONF

RTRV-PUSCH-CONF Retrieves/Changes the configuration information for the Physical Uplink

Shared Channel (PUSCH) within the base station. It can retrieve/change

the settings on whether the base station can receive 64 QAM and the

settings for hopping.

CHG-PUSCH-CONF

RTRV-PUSCH-IDLE Retrieves/Changes the configuration information for the Physical Uplink

Shared Channel (PUSCH) within the base station. It can retrieve/change

the n (1)_DMRS value used to determine the cyclic shift value of the

PUSCH reference signal.

CHG-PUSCH-IDLE

RTRV-SNDRS-CONF Retrieves/Changes the configuration information for the UL sounding

reference signal within the base station. It can retrieve/change

information on whether the ACK and NACK or the SR and SRS

simultaneous transmission is supported, whether the cell uses the SRS,

and the SRS MaxUpPts value.

CHG-SNDRS-CONF

RTRV-PWR-PARA Retrieves/Changes the configuration information for the Uplink Power

Control within the base station. It can retrieve/change the alpha value

used in the PUSCH power control, the settings related to the difference in

the transmission power for each PUCCH format, the p0_nominal_PUCCH

and p0_nominal_PUSCH value settings, and the UL IOT target value.

CHG-PWR-PARA

RTRV-SON-DLICIC Retrieves/changes the parameters related to the downlink ICIC used by

the base station. CHG-SON-DLICIC

RTRV-SON-ULICIC Retrieves/changes the parameters related to the uplink ICIC used by the

base station. CHG-SON-ULICIC

RTRV-CLOCK-CTRL Retrieves/changes the configuration parameters related to clockadvance/

retard settings of the base station modem/DSP. CHG-CLOCK-CTRL



1.3 System Information Control

System information refers to the Evolved UMTS Terrestrial Radio Access Network

(EUTRAN) system information for a cell for which cell setup has finished.

The system information includes timer values used by the UE, EUTRAN ID information,

cell selection and reselection information, cell‟s restrictions related to cell selection,

physical channel-related information, on/off status for each type of the system information

to be broadcasted, and interval.

Master Information Block (MIB) Broadcast

The master information is transmitted at the fixed intervals defined in the specification.

It includes the base station‟s downlink bandwidth, PHICH-related information, and system

frame number, etc.

For efficient operation of the MIB, the operator can view and change the MIB-related

parameters. The relevant search and change functions are provided as LSM commands.

System Information Block (SIB) Broadcast

The system information consists of SIB1 to SIB13. Each of these is transmitted at its own

set intervals, or the same interval.

The information for each system is as follows.

SIB1: Information on scheduling, cell selection, and PLMN list for other SIBs (2-13)

SIB2: Information on physical channel, and timer used by the UE

SIB3: Information on cell reselection into an intra frequency in the EUTRAN system

SIB4: Information on the list of neighbors which have an intra frequency

SIB5: Information on cell reselection to an inter frequency in the EUTRAN system

SIB6: Information on cell reselection into the UTRAN system

SIB7: Information on cell reselection to the GSM EDGE Radio Access Network

(GERAN) system

SIB8: Information on cell reselection into the CDMA system

SIB9: Home eNB-related information

SIB10: Earthquake and Tsunami Warning System (ETWS) primary warning message

SIB11: ETWS secondary warning message

SIB12: Commercial Mobile Alert System (CMAS) warning message

SIB13: Information on Multimedia Broadcast Multicast Service (MBMS)

For efficient operation of a cell, an operator can view and change individual system

information. The relevant view and change functions are provided as LSM commands.



SIB Modification

A change is made to the system information when a system information parameter value

changes, except for the warning message parameter values (SIB10, 11, and 12).

When the UE receives the changed system information through paging, or the

systemValueTag within SIB1, it applies the new system information at the next

modification period. The existing system information is maintained until the UE applies the

new system information.

For efficient operation of SIB modification, an operator can view and change the

modification period-related information. The relevant view and change functions are

provided as LSM commands.

System Information Control Commands

You can use system information setup commands by selecting a target on the CLI of the


the „Search‟ tab. The table below lists the commands used to control system information.


RTRV-SIB-INF Retrieves/changes the interval at which the base station transmits SIB and

SI window size. This command is used to control the SIB transmission

function.

CHG-SIB-INF

RTRV-SIB-IDLE Retrieves/changes the TM size at which the base station transmits SIB.

These commands are used to control the SIB transmission function. CHG-SIB-IDLE

RTRV-CELL-IDLE Retrieves/changes the cell parameters being managed by the base

station. CHG-CELL-IDLE

RTRV-PHICH-IDLE Retrieves/changes the parameters related to the PHICH, which is a

physical transport channel. CHG-PHICH-IDLE

RTRV-CELL-ACS Retrieves/changes the parameters related to cell access within the base

station. CHG-CELL-ACS

RTRV-CAS-IDLE Retrieves/changes the parameters related to the cell access when a cell in

the base station is in idle state. CHG-CAS-IDLE

RTRV-CELL-SEL Retrieves/changes the parameters related to cell selection within the base

station. CHG-CELL-SEL

RTRV-BAR-EMERG Retrieves/changes the parameters related to access barring for

emergency calls. CHG-BAR-EMERG

RTRV-BAR-SIG Retrieves/changes the parameters related to access barring for mobile

originating signal calls. CHG-BAR-SIG

RTRV-BAR-DATA Retrieves/changes the parameters related to access barring for mobile

originating calls. CHG-BAR-DATA

RTRV-TIME-INF Retrieves/changes the parameters related to the timers used by the UE.

CHG-TIME-INF



(Continued)


RTRV-TIME-ALIGN Retrieves/changes the time alignment-related parameters used by the

UE. CHG-TIME-ALIGN

RTRV-RACH-CONF Retrieves/changes the parameters related to the RACH, which is a

physical transport channel. CHG-RACH-CONF

RTRV-BCCH-CONF Retrieves/changes the parameters related to the BCCH, which is a

physical transport channel. CHG-BCCH-CONF

RTRV-PCCH-CONF Retrieves/changes the parameters related to the PCCH, which is a

physical transport channel. CHG-PCCH-CONF

RTRV-PRACH-CONF Retrieves/changes the parameters related to the PRACH, which is a

physical transport channel. CHG-PRACH-CONF

RTRV-PUSCH-CONF Retrieves/changes the parameters related to the PUCCH, which is a

physical transport channel. CHG-PUSCH-CONF

RTRV-SNDRS-CONF Retrieves/changes the parameters related to the sounding RS used by

the base station. CHG-SNDRS-CONF

RTRV-PWR-PARA Retrieves/changes the parameters related to uplink power control.

CHG-PWR-PARA

RTRV-EUTRA-FA Retrieves/changes the parameters related to the EUTRA frequency.

CHG-EUTRA-FA

RTRV-CELL-RSEL Retrieves/changes the parameters related to cell re-selection into an

ETURAN cell. CHG-CELL-RSEL

RTRV-MOBIL-STA Retrieves/changes the parameters used to determine the mobility state of

the UE. CHG-MOBIL-STA

RTRV-CSGPCI-IDLE Retrieves/changes the parameters related to a CSG cell.

CHG-CSGPCI-IDLE

RTRV-NBR-EUTRAN Retrieves/changes the information on the EUTRA cells, which are located

near the base station. CHG-NBR-EUTRAN

RTRV-CDMA-CNF Retrieves/changes the configuration parameters related to CDMA2000

within the base station. CHG-CDMA-CNF

RTRV-HRPD-PREG Retrieves/changes the parameters related to pre-registration into a

CDMA HRPD system. CHG-HRPD-PREG

RTRV-HRPD-OVL Retrieves/changes the parameters related to the CDMA HRPD cell which

is overlaid with the cell of the base station. CHG-HRPD-OVL

RTRV-C1XRTT-PREG Retrieves/changes the parameters related to pre-registration into a

CDMA 1XRTT system. CHG-C1XRTT-PREG

RTRV-HRPD-BCLS Retrieves/changes the parameters related to the bandclass information

for the CDMA HRPD systems around the base station. CHG-HRPD-BCLS



(Continued)


RTRV-C1XRTT-BCLS Retrieves/changes the parameters related to the bandclass information

for the CDMA 1XRTT systems around the base station. CHG-C1XRTT-BCLS

RTRV-C1XRTT-OVL Retrieves/changes the parameters related to the CDMA 1XRTT cell

which is overlaid with the cell of the base station. CHG-C1XRTT-OVL

RTRV-NBR-HRPD Retrieves/changes the information for the CDMA HRPD cells, which are

located around the base station. CHG-NBR-HRPD

RTRV-NBR-C1XRTT Retrieves/changes the information for the CDMA 1XRTT cells, which are

located around the base station. CHG-NBR-C1XRTT

RTRV-HRPD-FREQ Retrieves/changes the parameters related to the CDMA HRPD carrier

information. CHG-HRPD-FREQ

RTRV-C1XRTT-FREQ Retrieves/changes the parameters related to the CDMA 1XRTT carrier

information. CHG-C1XRTT-FREQ

RTRV-BLACK-LIST Retrieves/changes the EUTRAN blacklist cell parameters related to the

cell of the base station. CHG-BLACK-LIST



1.4 RRC

1.4.1 Paging Control

The paging procedure transmits paging information to the UE in the RRC_IDLE status, or

notifies the UE in the RRC_IDLE or RRC_CONNECTED status that the system information

has changed. This section describes the paging procedure when the UE is in idle mode.

The figure below shows the paging procedure when the UE is in idle mode.

Figure 1.5 Paging Procedure

1) The paging procedure begins when the Mobility Management Entity (MME) sends a

paging message to the SCTB of the eNB.

2) The SCTB of the eNB sends the msgSctpDatalnd message to the ECCB.

3) After receiving the paging message, the eNB ECCB includes the paging information

received from the S1AP in the msgCrlcPagingReq message as it relays the message.

At this time, the ECCB sends the paging message only to the cells which have an

identical value to the TAC value contained in the S1APPaging message.

If the S1APPaging message received by the ECCB contains a CSGIDList value, the

TAC and CSGIDList values contained in it are compared to those owned by cells, and

the paging message is sent to only those cells that have identical values. The ECCB

calculates paging occasion(s) and paging frame, includes them in the

msgCrlcPagingReq message and sends it to the RLC.

4) The RLC sends the paging message to the UE considering PF and PO.

Since the subsequent steps are identical to the „switching from idle to active‟ procedure, see

the corresponding procedure for reference.

The system may specify the following command when attempting paging.


CHG-PCCH-CONF Retrieves/Changes the configuration information for the PCCH within

the base station.

eNB

PHY/MAC/RL

C

PDCB ECCB

(RRC/S1AP/X2AP)

SCTB GTPB

3) msgCrlcPagingReq 4) Paging

UE EPC

MME/SGW

1) Paging 2) msgSctpDatalnd



1.4.2 RRC Connection establishment/release

The RRC connection establishment procedure is to configure an RRC connection between

the base station and the UE. The SRB1 is configured through this procedure.

In addition, the initial NAS dedicated information/message is sent from the UE to the eNB

through this procedure. For the message flow for this procedure, refer to the RRC

connection establishment section in the switching from idle to active procedure below.

Figure 1.6 Switching from Idle to Active Procedure

Serving eNB

Random Access Preamble

Rrc Connection Request

Rrc Connection Setup

SRB #0/RLC-TM/CCCH/UL-SCH

UE EPC

SRB #0/RLC-TM/ CCCH/DL-SCH

msgRlcCommonDatalnd

msgRlcCommonDataReq

msgCmacPhyConfigReq (SRB #1/Setup)

msgCrlcConfigReq (SRB #1)

msgCpdcpConfigReq (SRB #1)

msgCmacPhyConfigCnf

msgCrlcConfigCnf

msgCpdcpConfigCnf

msgCrlcDatalnd msgCpdcpDataTransferlnd Rrc Connection Setup Complete (+Service Request)

SRB #1/RLC-AM/ DCCH/UL-SCH

msgCsctpDataReq Initial UE Message (+Service Request)

msgCsctpDatalnd Initial Context Setup Request

msgCpdcpSecurityControl (SRB #1/Integrity)

msgCpdcpSecurityControlSuccess

SRB #1/RLC-

AM/DCCH/DL-SCH

Security Mode

Command

msgCrlcDataReq msgCpdcpDataTransferReq

msgCrlcDataCnf msgCpcpDataTransferCnf

msgCpdcpDataTransferlnd

msgPdcpSecurityControl (SRB #1/integrity and Ciphering)

msgPdcpSecurityControlSuccess

msgCrlcDatalnd

SRB #1/RLC-

AM/DCCH/UL-SCH

Security Mode

Complete

Rrc Connection Reconfiguration

SRB #1/RLC-AM/ DCCH/DL-SCH


msgCrlcDataCnf msgCpdcpDataTransferCnf

msgCmacPhyReconfigPrepare


msgCpdcpConfigReq (SRB #2, integrity and ciphering)

msgCrlcConfigReq (DRBs)

msgCpdcpConfigReq (DRBs, integrity and ciphering)

msgCgtpSetupReq (S1-U)

msgCrlcConfigCnf

msgCpdcpConfigCnf

msgCgtpSetupCnf (S1-U)

Rrc Connection Reconfiguration Complete


msgCrlcDatalnd msgCpdcpDataTransferlnd

msgCsctpDataReq

RRC_IDLE

RRC_CONNECTED

RRC Connection Establishment

Initial Security Activation

RRC Connection Reconfiguration

msgCrlcConfigCnf

msgCpdcpConfigCnf

msgCmacPhyReconfigReady

msgCmacPhyReconfigCommit (SRB #2, DRBs)

PHY/MAC RLCB SCTB GTPB PDCB ERMB ECCB MME SGW


Initial Context Setup Response



After the random access procedure is performed between the UE and eNB, the PHY layer

receives the RRC Connection Request message sent by the UE. The MAC layer sends the

C-RNTI value and RRC data to the RLC, which are determined during the random access

procedure.

The RLC layer sends the ECCB those values received from the MAC using the

msgRlcCommonDataInd message, which is the common interface message between the

RLC and ECCB.

The ECCB decodes the RRC message contained in the msgRlcCommonDataInd message

using ASN.1, and allocates the eNB‟s internal resources including call context to establish

the RRC connection. In addition, the ECCB saves the content contained in the RRC

message in the call context newly allocated. When receiving an RRC Connection Request

message, based on the information contained in it and the allocated resources, the ECCB

sets up both the UE and the protocol blocks within the base station simultaneously, to set

up the Signaling Radio Bearer No. 1 (hereafter, SRB #1).

The ECCB constructs and encodes the RRC Connection Setup message that will be sent to

the UE as the Information Element (hereafter, IE), containing only the SRB #1 information.

Then, the ECCB sends it to the RLC using the msgRlcCommonDataReq message.

The RLC sends this message to the MAC/PHY via the interface between the RLC and

MAC/PHY. The MAC/PHY protocol block sends the RRC Connection Setup message to

the UE using the SRB #0 which was set up during cell setup.

Simultaneously, to configure the RLC/MACPHY/PDCP within the base station (for setting

up the SRB #1), the ECCB also sends the msgCrlcConfigReq/msgCmacPhyConfigReq/

msgCpdcpConfigReq message to the blocks taking charge of the corresponding protocols.

When it receives the messages (msgCrlcConfigCnf/msgCpdcpConfigCnf/

msgCmacPhyConfigConf/RRC Connection Setup Complete) in response to all the

messages that were sent to set up the SRB #1 as above, the ECCB saves the information

contained in those confirmation or completion messages. The RRC Connection Setup

Complete message is sent to the newly set up SRB #1.



The RRC connection release procedure is used to release an established RRC connection.

The figure below shows its message flow.

Figure 1.7 RRC Connection Release Procedure

When RRC connection release is requested, the eNB sends the RRC Connection Release

message to the UE. Then, when the L2Ack message is received, the protocol blocks within

the base station are released.

Serving eNB

PHY/MAC RLCB SCTB GTPB PDCB ERMB ECCB

RRC Connection Release


UE

msgCmacPhyReleaseReq

msgCrlcPhyReleaseReq (SRB #1)

msgCpdcpReleaseReq (SRB #1)

msgCmacPhyReleaseCnf

msgCrlcReleaseCnf

msgCpdcpReleaseCnf

RRC_IDLE

RRC_IDLE

RRC Connection Release Procedure


msgCrlcDataCn

f

msgCpcpDataTransferCnf



PDCP Parameter Description

The PDCP information for the SRB is not sent to the UE. The related parameters are as follows:

Parameter Unit Range (H.C Value) Description Control Command

umSnSize enum len7 bits RLC UM Sequence Number Size -

RLC Parameter Description

Parameter Unit Range Description Control Command

rlcMode AM AM The only RLC mode of the SRB. -

timerPollRetransmit msec ms5, ms10, ms15, ms20, ms25, ms30, ms35,

ms40, ms45, ms50, ms55, ms60, ms65, ms70,

ms75, ms80, ms85, ms90, ms95, ms100, ms105,

ms110, ms115, ms120, ms125, ms130, ms135,

ms140, ms145, ms150, ms155, ms160, ms165,

ms170, ms175, ms180, ms185, ms190, ms195,

ms200, ms205, ms210, ms215, ms220, ms225,

ms230, ms235, ms240, ms245, ms250, ms300,

ms350, ms400, ms450, ms500

The timer used by the AM RLC

transmitting entity for poll

retransmission.

CHG-SRB-RLC

pollPDU PDU p4, p8, p16, p32, p64, p128, p256, pInfinity Used by the AM_RLC entity to trigger

poll for each pollPDU PDU.

pollByte kByte kB25, kB50, kB75, kB100, kB125, kB250, kB375,

kB500, kB750, kB1000, kB1250, kB1500, kB2000,

kB3000, kBinfinity

Used by the AM_RLC entity to trigger

poll for pollByte bytes.

maxRetransmissionThreshold count t1, t2, t3, t4, t6, t8, t16, t32 Used by the AM_RLC transmitting

entity to restrict the AMD PDU

retransmission count.



(Continued)


timerReordering msec ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40,

ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85,

ms90, ms95, ms100, ms110, ms120, ms130, ms140, ms150,

ms160, ms170, ms180, ms190, ms200

Used by the RLC receiving

entity to detect the loss of RLC

PDUs.

CHG-SRB-RLC

timerStatusProhibit - ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40,

ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85,

ms90, ms95, ms100, ms105, ms110, ms115, ms120, ms125,

ms130, ms135, ms140, ms145, ms150, ms155, ms160,

ms165, ms170, ms175, ms180, ms185, ms190, ms195,

ms200, ms205, ms210, ms215, ms220, ms225, ms230,

ms235, ms240, ms245, ms250, ms300, ms350, ms400,

ms450, ms500

The timer used by the RLC

receiving entity to prohibit

transmission of STATUS_PDU.



MAC Parameter Description


priority int 1~16 priority CHG-SRB-QCI

prioritisedBitRate kBps kBps0, kBps8, kBps16,

kBps32, kBps64, kBps128,

kBps256, infinity

Used for logical channel prioritization in the UE; the

minimum transmission rate that must be guaranteed for

each logical channel. The UE increases the bucket for

each logical channel in accordance with this parameter

value.

-

bucketSizeDuration msec ms50, ms100, ms150, ms300,

ms500, ms1000

Used for logical channel prioritization in the UE.

It determines the maximum bucket size for each logical

channel. Maximum bucket size = prioritizedBitRate *

bucketSizeDuration

-

logicalChannelGroup int 0~3 A information construction unit for the Buffer Status Report

(BSR). The UE adds the buffer sizes of the logical

channels which have the same logicalChannelGroupID to

write the BSR, and then sends it.

-

maxHARQ-Tx Number of

count

n1, n2, n3, n4, n5, n6, n7, n8,

n10, n12, n16, n20, n24, n28

Maximum HARQ retransmission count CHG-TRCH-INF

periodicBSR-Timer sub-frame sf5, sf10, sf16, sf20, sf32, sf40,

sf64, sf80, sf128, sf160, sf320,

sf640, sf1280, sf2560

Periodical buffer status report timer CHG-TRCH-BSR

retxBSR-Timer sub-frame sf320, sf640, sf1280, sf2560,

sf5120, sf10240

Retransmission BSR Timer

ttiBundling - BOOLEAN ttiBundling CHG-TRCH-INF



(Continued)


onDurationTimer sub-frame psf1, psf2, psf3, psf4, psf5,

psf6, psf8, psf10, psf20,


psf80, psf100, psf200

Timer for monitoring the PDCCH in the DRX mode CHG-DRX-INF

drx-InactivityTimer sub-frame psf1, psf2, psf3, psf4, psf5,




psf500, psf750, psf1280,

psf1920, psf2560, spare10

Timer denoting the DRX inactivity interval

drx-RetransmissionTimer sub-frame psf1, psf2, psf4, psf6, psf16,

psf24, psf33

DRX retransmission timer

longDRX-CycleStartOffset int 0..2559 longDRX-Cycle and drxStartOffset for running the

onDurationTimer

shortDRX-Cycle sub-frame sf2, sf5, sf8, sf10, sf16, sf20,

sf32, sf40, sf64, sf80, sf128,

sf160, sf256, sf320, sf512,

sf640

Short DRX cycle for running the onDurationTimer

drxShortCycleTimer int 1~16 Timer used to enter Long DRX mode CHG-DRX-INF

TimeAlignmentTimer sub-frame sf500, sf750, sf1280, sf1920,

sf2560, sf5120, sf10240,

infinity

Used by the UE to adjust the time over which it

determines whether uplink timing is correct.

CHG-TIME-ALIGN



(Continued)


periodicPHR-Timer sub-frame sf10, sf20, sf50, sf100, sf200,

sf500, sf1000, infinity

Periodic power head room timer CHG-TRCH-INF

prohibitPHR-Timer sub-frame sf0, sf10, sf20, sf50, sf100,

sf200, sf500, sf1000

Power Head Room prohibit Timer

dl-PathlossChange dB dB1, dB3, dB6, infinity Downlink Path Loss Change

semiPersistSchedIntervalUL sub-frame sf10, sf20, sf32, sf40, sf64,

sf80, sf128, sf160, sf320,

sf640

The interval at which the SPS UL has scheduled

resources.

CHG-DPHY-SPS

implicitReleaseAfter enum e2, e3, e4, e8 This parameter denotes how many times an empty

BSR is received before the SPS is released.

p0NominalPUSCHPersistent int -126~24 This parameter is an SPS Po parameter used for power

control.

CHG-DPHY-SPS

p0UEPUSCHPersistent int -8~7 This parameter is an SPS Po parameter used for power

control, which is determined for each UE.

semiPersistSchedIntervalDL sub-frame sf10, sf20, sf32, sf40, sf64,

sf80, sf128, sf160, sf320,

sf640

This parameter denotes the semi-persistent scheduling

interval for downlink. The unit is the number of sub-

frames: sf10 means 10 sub-frames; sf20 means

20 sub-frames, and so on. For the TDD, when using

this parameter value, it is rounded down to the largest

integer multiple of 10 sub-frames that is equal to, or

less than, this parameter value. For example, select

sf10 for 10 sub-frames, sf32 for 30 sub-frames, or

sf128 for 120 sub-frames (section 6.3.2 of TS 36.331).

numberOfConfSPSprocesses int 1~8 The number of HARQ processes set for semi-persistent

scheduling (section 5.10 of TS 36.321)



(Continued)


betaOffsetACKIndex uint 0~15 A value used when the ACK/NACK message is multiplexed

with the PUSCH.

CHG-DPHY-PUSCH

betaOffsetRIIndex uint 0~15 A value used when the RI message is multiplexed with the

PUSCH.

betaOffsetCQIIndex uint 0~15 A value used when the CQI message is multiplexed with the

PUSCH.

p0UePUSCH int -8~7 A non-persistent scheduling PO parameter used for PUSCH

power control, which is determined for each UE.

CHG-ULPWR-CTRL

deltaMCSenabled enum en0, en1 Whether to use a power offset for other MCSs.

accumulationEnabled BOOLEAN 0~1 Whether either Accumulation mode or Absolute mode is used

in the TPC. If it is TRUE, accumulation mode is used.

p0UePUCCH int -8~7 A PO parameter used for PUCCH power control, which is

determined for each UE.

pSRSoffset uint 0~15 The index indicating the power offset of the PUSCH and SRS.

filterCoefficient enum fc0, fc1, fc2, fc3, fc4, fc5,

fc6, fc7, fc8, fc9, fc11, fc13,

fc15, fc17, fc19

A filtering coefficient used for RSRP measurement.

The measurement is again used to calculate a path loss.

cqiReportModeAperiodic enum rm12, rm20, rm22, rm30,

rm31

A periodic CQI reporting mode (section 7.2.1 of TS 36.213):

Select rm12 for Mode 1-2, rm20 for Mode 2-0, or rm22 for

Mode 2-2 (section 6.3.2 of TS 36.331)

CHG-CQI-REP



(Continued)


nomPdschRsEpreOffset int -1~6 The shift offset used for calculating ρA which is the ratio of

PDSCH EPRE to cell-specific RS EPRE (section 7.2.3 of TS

36.213). The actual value used is the parameter value * 2

[dB] (section 6.3.2 of TS 36.331).

CHG-CQI-REP

wideSubbandSelect - Wide, short This parameter is used to select either wideband or sub

band CQI.

subbandCQI uint 1~4 This parameter denotes the transmission count of each sub

band CQI for one wideband CQI cycle.

simultaneousAckNackAndCQI BOOL BOOL This parameter denotes whether both ACK/NACK and CQI

messages can be sent simultaneously via PUCCH format

2a/2b. If it is TRUE, CQI can be transmitted simultaneously

with ACK/NACK.

1: TRUE, 2: FALSE

srsHoppingBandwidth enum hbw0, hbw1, hbw2,

hbw3

The bandwidth where the sounding RS is hopped. CHG-DPHY-ULSRS

duration uint 0~1 The transmission duration of the sounding RS.

If it is TRUE, transmission of the sounding RS continues until

it is disabled. If it is FALSE, the sounding RS is transmitted

just once.

dsrTransMax enum n4, n8, n16, n32, n64 The maximum count of the scheduling requests that can be

attempted until the PUSCH resource is allocated to the UE.

CHG-DPHY-SR



1.4.3 RRC Connection reconfiguration

The RRC connection reconfiguration procedure is the procedure where the Initial Context Setup message is received from the MME, and then the

SRB #2 and the default bearer are set up.

For the message flow for this procedure, refer to the RRC connection reconfiguration section in the switching from idle to active procedure below.

GTP Parameter Description


teId - Octet string (4) eNB GTP Tunnel Endpoint identifier -

destTeId - Octet string (4) eNB GTP Tunnel Endpoint identifier -

directionInd - 0x00: S1-U, 0x01: DL-Forward, 0x02: UL-Forward GTP Tunnel -

bearerQos - QoS Profile QoS characteristics of the bearer -

destAddr IP v4 Address unsigned int S-GW IP address -

pdcpAddr IP v4 Address unsigned int PDCP IP address -

PDCP Parameter Description

Parameter Unit Range (H.C value) Description Control Command

umSnSize enum len7 bits, len12 bits RLC UM

Sequence Number Size

CHG-PDCP-INF

fwdEndTimer msec 10~1000 Forwarding

End Timer

discardTimer msec 50, 100, 150, 300, 500, 750, 1500, infinity Discard Timer

rohcInfo.usedFlag boolean Boolean Whether the RB supports ROHC. CHG-ROHC-INF



(Continued)

Parameter Unit Range (H.C value) Description Control Command

rohcInfo.maxCid int 1~16383 maxContextSession CHG-ROHC-INF

rohcInfo.profiles boolean Boolean This parameter denotes whether each ROHC

profile is supported.

mode enum SECURITY_IDLE, INTEGRITY_ACTIVATED,

CIPHERING_ACTIVATED,

INTANDCHIPHER_ACTIVATED

Security mode to be set -

keyRrcInt uint8_t 16 arrays The key value used for integrity of the RRC

message.

-

keyRrcEnc uint8_t 16 arrays The key value used for ciphering of the RRC

message.

-

keyUpEnc uint8_t 16 arrays The key value used for ciphering of the user data. -

integrityAlgo - EIA1 (SNOW 3G), EIA2 (AES) Integrity algorithm CHG-SECU-INF

cipherAlgo - EEA0 (NULL), EEA1 (SNOW 3G), EEA2 (AES) Ciphering algorithm

gtpAddr IP v4 Address unsigned int GTP address -

rlcAddr IP v4 Address unsigned int RLC address -

rlcMode enum AM, UM RLC Mode -



To have different RLC parameters from each other, parameters of UE RLC and eNB RLC are separated.

UE RLC Parameter Description


ueTimerPollRetransmit msec ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40,

ms45, ms50, ms55, ms60, ms65, ms70, ms75,

ms80, ms85, ms90, ms95, ms100, ms105, ms110,

ms115, ms120, ms125, ms130, ms135, ms140,

ms145, ms150, ms155, ms160, ms165, ms170,

ms175, ms180, ms185, ms190, ms195, ms200,

ms205, ms210, ms215, ms220, ms225, ms230,

ms235, ms240, ms245, ms250, ms300, ms350,

ms400, ms450, ms500

The timer used by the AM RLC transmitting

entity for poll retransmission.

CHG-RLC-INF

uePollPDU PDU p4, p8, p16, p32, p64, p128, p256, pInfinity Used by the AM_RLC entity to trigger poll for

each pollPDU PDU.

uePollByte kByte kB25, kB50, kB75, kB100, kB125, kB250, kB375,

kB500, kB750, kB1000, kB1250, kB1500, kB2000,

kB3000, kBinfinity

Used by the AM_RLC entity to trigger poll for

each pollByte byte.

ueMaxRetxThreshold count t1, t2, t3, t4, t6, t8, t16, t32 Used by the AM_RLC transmitting entity to

restrict the AMD PDU retransmission count.

ueTimerReordering msec ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35,

ms40, ms45, ms50, ms55, ms60, ms65, ms70,

ms75, ms80, ms85, ms90, ms95, ms100, ms110,

ms120, ms130, ms140, ms150, ms160, ms170,

ms180, ms190, ms200

Used by the RLC receiving entity to detect

the loss of RLC PDUs.



(Continued)


ueTimerStatusProhibit - ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35,

ms40, ms45, ms50, ms55, ms60, ms65, ms70,

ms75, ms80, ms85, ms90, ms95, ms100, ms105,

ms110, ms115, ms120, ms125, ms130, ms135,

ms140, ms145, ms150, ms155, ms160, ms165,

ms170, ms175, ms180, ms185, ms190, ms195,

ms200, ms205, ms210, ms215, ms220, ms225,

ms230, ms235, ms240, ms245, ms250, ms300,

ms350, ms400, ms450, ms500

The timer used by the RLC receiving entity to

prohibit transmission of STATUS_PDU.

CHG-RLC-INF

eNB RLC Parameter Description


rlcMode enum AM, UM RLC Mode CHG-RLC-INF

timerPollRetransmit msec ms5, ms10, ms15, ms20, ms25, ms30, ms35,

ms40, ms45, ms50, ms55, ms60, ms65, ms70,

ms75, ms80, ms85, ms90, ms95, ms100, ms105,

ms110, ms115, ms120, ms125, ms130, ms135,

ms140, ms145, ms150, ms155, ms160, ms165,

ms170, ms175, ms180, ms185, ms190, ms195,

ms200, ms205, ms210, ms215, ms220, ms225,

ms230, ms235, ms240, ms245, ms250, ms300,

ms350, ms400, ms450, ms500

The timer used by the AM RLC transmitting

entity for poll retransmission.



(Continued)


pollPDU PDU p4, p8, p16, p32, p64, p128, p256, pInfinity Used by the AM_RLC entity to trigger poll

for each pollPDU PDU.

CHG-RLC-INF

pollByte kByte kB25, kB50, kB75, kB100, kB125, kB250, kB375,

kB500, kB750, kB1000, kB1250, kB1500,

kB2000, kB3000, kBinfinity

Used by the AM_RLC entity to trigger poll

for each pollByte byte.

maxRetransmissionThreshold count t1, t2, t3, t4, t6, t8, t16, t32 Used by the AM_RLC transmitting entity

to restrict the AMD PDU retransmission

count.

timerReordering msec ms0, ms5, ms10, ms15, ms20, ms25, ms30,

ms35, ms40, ms45, ms50, ms55, ms60, ms65,

ms70, ms75, ms80, ms85, ms90, ms95, ms100,

ms110, ms120, ms130, ms140, ms150, ms160,

ms170, ms180, ms190, ms200

Used by the RLC receiving entity to

detect the loss of RLC PDUs.

timerStatusProhibit - ms0, ms5, ms10, ms15, ms20, ms25, ms30,

ms35, ms40, ms45, ms50, ms55, ms60, ms65,

ms70, ms75, ms80, ms85, ms90, ms95, ms100,

ms105, ms110, ms115, ms120, ms125, ms130,

ms135, ms140, ms145, ms150, ms155, ms160,

ms165, ms170, ms175, ms180, ms185, ms190,

ms195, ms200, ms205, ms210, ms215, ms220,

ms225, ms230, ms235, ms240, ms245, ms250,

ms300, ms350, ms400, ms450, ms500

The timer used by the RLC receiving

entity to prohibit transmission of

STATUS_PDU.

snFieldLength enum Size5, size10 The field size of the UM Sequence

Number.



MAC Parameter Description


priority int 1~16 priority CHG-QCI-VAL

prioritisedBitRate kBps kBps0, kBps8, kBps16, kBps32,

kBps64, kBps128, kBps256, infinity

Used for logical channel prioritization in the

UE. It determines the minimum transmission

rate which must be guaranteed for each

logical channel.

The UE increases the bucket for each logical

channel in accordance with this parameter

value.

CHG-LOCH-INF

bucketSizeDuration msec ms50, ms100, ms150, ms300, ms500,

ms1000

Used for logical channel prioritization in the

UE. It determines the maximum bucket size

for each logical channel. Maximum bucket

size = prioritizedBitRate * bucketSizeDuration

logicalChannelGroup int 0~3 The information construction unit for the

Buffer Status Report (BSR).

The UE adds the buffer sizes of the logical

channels which have the same

logicalChannelGroupID to write the BSR, and

then sends it.

maxHARQ-Tx Number of

count

n1, n2, n3, n4, n5, n6, n7, n8, n10,

n12, n16, n20, n24, n28

Maximum HARQ retransmission count CHG-TRCH-INF

periodicBSR-Timer sub-frame sf5, sf10, sf16, sf20, sf32, sf40, sf64,

sf80, sf128, sf160, sf320, sf640,

sf1280, sf2560

Periodical buffer status report timer CHG-TRCH-BSR



(Continued)


retxBSR-Timer sub-frame sf320, sf640, sf1280, sf2560, sf5120,

sf10240

Retransmission BSR

Timer

CHG-TRCH-BSR

ttiBundling - BOOLEAN ttiBundling CHG-TRCH-INF

onDurationTimer sub-frame psf1, psf2, psf3, psf4, psf5, psf6, psf8,

psf10, psf20, psf30, psf40, psf50, psf60,

psf80, psf100, psf200

Timer for monitoring the PDCCH in the DRX

mode

CHG-DRX-INF

drx-InactivityTimer sub-frame psf1, psf2, psf3, psf4, psf5, psf6, psf8,

psf10, psf20, psf30, psf40, psf50, psf60,

psf80, psf100, psf200, psf300, psf500,

psf750, psf1280, psf1920, psf2560,

spare10

The timer representing the DRX inactivity

interval

drx-RetransmissionTimer sub-frame psf1, psf2, psf4, psf6, psf16, psf24,

psf33

DRX retransmission timer

longDRX-CycleStartOffset int 0..2559 longDRX-Cycle and drxStartOffset for

running the onDurationTimer

shortDRX-Cycle sub-frame sf2, sf5, sf8, sf10, sf16, sf20, sf32, sf40,

sf64, sf80, sf128, sf160, sf256, sf320,

sf512, sf640

Short DRX cycle for running the

onDurationTimer

drxShortCycleTimer int 1~16 Timer used to enter Long DRX mode CHG-DRX-INF

TimeAlignmentTimer sub-frame sf500, sf750, sf1280, sf1920, sf2560,

sf5120, sf10240, infinity

Used by the UE to adjust the time over which

it determines whether uplink timing is correct.

CHG-TIME-ALIGN

periodicPHR-Timer sub-frame sf10, sf20, sf50, sf100, sf200, sf500,

sf1000, infinity

Periodic power head room timer CHG-TRCH-INF



(Continued)


prohibitPHR-Timer sub-frame sf0, sf10, sf20, sf50, sf100,

sf200, sf500, sf1000

The timer prohibiting Power Head Room CHG-TRCH-INF

dl-PathlossChange dB dB1, dB3, dB6, infinity Downlink Path Loss Change

semiPersistSchedIntervalUL sub-frame sf10, sf20, sf32, sf40, sf64, sf80,

sf128, sf160, sf320, sf640

The interval with which the SPS UL has

scheduled resources.

CHG-DPHY-SPS

implicitReleaseAfter enum e2, e3, e4, e8 The number of times that an empty BSR is

received before the SPS is released.

p0NominalPUSCHPersistent int -126~24 An SPS Po parameter used for power control.

p0UEPUSCHPersistent int -8~7 An SPS Po parameter used for power control,

which is determined for each UE.

semiPersistSchedIntervalDL sub-frame sf10, sf20, sf32, sf40, sf64, sf80,

sf128, sf160, sf320, sf640

The semi-persistent scheduling interval for

downlink. The unit is the number of sub-

frames: sf10 means 10 sub-frames; sf20

means 20 sub-frames.

For the TDD, when using this parameter

value, it is rounded down to the largest

integer multiple of 10 sub-frames that is equal

to, or less than, this parameter value.

For example, 10 sub-frames are used for

sf10; 30 sub-frames for sf32; 120 sub-frames

for sf128. (section 6.3.2 of TS 36.331)

CHG-DPHY-SPS

numberOfConfSPSprocesses int 1~8 The number of HARQ processes set up for

semi-persistent scheduling (section 5.10 of

TS 36.321).



(Continued)


betaOffsetACKIndex uint 0~15 The value used when the ACK/NACK message is

multiplexed with the PUSCH.

CHG-DPHY-PUSCH

betaOffsetRIIndex uint 0~15 The value used when the RI message is multiplexed

with the PUSCH.

(betaOffsetCQIIndex uint 0~15 The value used when the CQI message is multiplexed

with the PUSCH.

CHG-DPHY-PUSCH

p0UePUSCH int -8~7 A non-persistent scheduling Po parameter used for

PUSCH power control, which is determined for each

UE.

CHG-ULPWR-CTRL

deltaMCSenabled enum en0, en1 Whether to use a power offset for other MCSs.

accumulationEnabled BOOLEAN 0~1 Whether either Accumulation mode or Absolute mode

is used in the TPC. If it is TRUE, accumulation mode is

used.

p0UePUCCH int -8~7 A Po parameter used for PUCCH power control, which

is determined for each UE.

pSRSoffset uint 0~15 The index denoting the power offset of the PUSCH and

SRS.

filterCoefficient enum fc0, fc1, fc2, fc3, fc4, fc5, fc6, fc7,

fc8, fc9, fc11, fc13, fc15, fc17, fc19

The filtering coefficient used for RSRP measurement.

The measurement is again used to calculate a path

loss.

cqiReportModeAperiodic enum rm12, rm20, rm22, rm30, rm31 Aperiodic CQI reporting mode (section 7.2.1 of TS

36.213): Select rm12 for Mode 1-2, rm20 for Mode 2-0,

or rm22 for Mode 2-2 (section 6.3.2 of TS 36.331)

CHG-CQI-REP



(Continued)


nomPdschRsEpreOffset int -1~6 The shift offset used for calculating ρA which is the ratio of

PDSCH EPRE to cell-specific RS EPRE (section 7.2.3 of TS

36.213). The actual value used is the parameter value * 2 [dB]

(section 6.3.2 of TS 36.331).

CHG-CQI-REP

wideSubbandSelect - Wide, short Selects either wideband or sub band CQI.

subbandCQI uint 1~4 The transmission count of each sub band CQI for one

wideband CQI cycle.

simultaneousAckNackAndCQI BOOL BOOL Whether both ACK/NACK and CQI messages can be sent

simultaneously via PUCCH format 2a/2b. If it is TRUE, CQI

can be transmitted simultaneously with ACK/NACK. 1: TRUE,

2: FALSE

CHG-CQI-REP

srsHoppingBandwidth enum hbw0, hbw1, hbw2, hbw3 Specifies the bandwidth where the sounding RS is hopped. CHG-DPHY-ULSRS

duration uint 0~1 Specifies the transmission duration of the sounding RS.

If it is TRUE, transmission of the sounding RS is continued

until it is disabled. If it is FALSE, the sounding RS is

transmitted just once.

CHG-DPHY-ULSRS

dsrTransMax enum n4, n8, n16, n32, n64 Specifies the maximum count of the scheduling requests that

can be attempted until the PUSCH resource is allocated to

the UE.

CHG-DPHY-SR



1.4.4 Security

Initial security activation

The following shows the security setup procedure between eNB and UE.

Figure 1.8 Security Setup Procedure between eNB and UE

The LTE MME must know the UE‟s capabilities before it can select a NAS protection

algorithm. Therefore, the initial NAS message contained in the RRC Connection Setup

Complete message includes all UEs Security capabilities, UE identifier (IMS or TMSI),

KSIASME, and NAS-MAC, etc.

When sending the initial UE message to the MME, the eNB includes the initial NAS

message contained the RRC Connection Setup Complete message into the initial UE

message and by-passes it.

The AKA procedure is the procedure where authentication and key agreement are

performed. The MME sends the UE the RAND (random challenge), AUTN (authentication

token), and KSIASME. Then, the UE calculates CK and IK based on them. In addition, it

can calculate KSIASME from CK and IK. If the verification for AUTN is successful, the

UE sends a response message to the MME.

RRC Connection Request

eNB

PHY/MAC/RLC SCTB GTPB PDCB ECCB

(RRC/S1AP/X2AP)

UE EPC

MME/SGW

Security Procedure

RRC Connection Setup

RRC Connection Setup Complete (+NAS)

SRB #0/RLC-TM/CCCH/UL_SCH

SRB #0/RLC-TM/CCCH/DL_SCH

SRB #1/RLC-AM/DCCH/UL_SCH Initial UE Message (+NAS)

DL Information Transfer

UL Information Transfer

Down Link NAS Transport

Up Link NAS Transport AKA Procedure

Initial Context Setup

Request msgCpdcpSecurityControl

msgCpdcpSecurityControlSuccess (SRB #1/Integrity Activation)

Security Mode Command

SRB #1/RLC-AM/DCCH/DL_SCH Security Mode Complete

SRB #1/RLC-AM/DCCH/UL_SCH msgCpdcpSecurityControl

(SRB #1/Cyphering Activation) msgCpdcpSecurityControlSuccess



The MME sends the UE security capabilities and the security key (KeNB) to the eNB using

Initial Context Setup Request. The UE security capabilities consist of a 32-bit string.

Its content is as follows.

UE Security Capa = Encryption Algorithm (16bits) + Integrity Algorithm

(16bits)

> Encryption Algorithms: Each position in the bitmap represents an

encryption algorithm:

"all bits equal to 0" - UE supports no other algorithm than EEA0

"first bit" - 128-EEA1, "second bit" - 128-EEA2, other bits reserved

for future use. Value ‘1’ indicates support and value '"0'" indicates

no support of the algorithm.

> Integrity Protection Algorithms: Each position in the bitmap

represents an encryption algorithm:

"all bits equal to 0" - UE supports no other algorithm than EEA0

"first bit" - 128-EEA1, "second bit" - 128-EEA2, other bits reserved

for future use. Value ‘1’ indicates support and value '"0'" indicates

no support of the algorithm.

The ECCB of the eNB selects an AS algorithm based on the Initial Context Setup Request

message. The integrity/ciphering algorithm preferred by the eNB is pre-determined by the

PLD. The ECCB of the eNB must select an algorithm that is common to the integrity/

ciphering algorithm, which is specified in the UE Security Capabilities IE transmitted in

the Initial Context Setup Request message. In addition, the ECCB of the eNB derives

Krrc_int, Krrc_enc, and Kup_enc from the received KeNB.

The ECCB of the eNB sends the determined algorithm, Krrc_int, Krrc_enc, and Kup_enc

to the PDCP using the msgCpdcpSecurityControl. Then, integrity will be applied to all

RRC messages sent subsequently.

When receiving the msgCpdcpSecurityControlSuccess message from the PDCP, the ECCB

sends the SecurityModeCommand message to the UE. At this time, the determined

algorithm is also sent. When receiving the Security Mode Complete message from the UE,

the ECCB sends the msgCpdcpSecurityControl message to the PDCP to apply the

ciphering algorithm to the SRB #1. Then, for each subsequent radio bearer, the ECCB

sends the msgCpdcpConfigReq message to the PDCP to apply the integrity/ciphering

algorithm.

Parameter Description

Parameter Unit Range (H.C Value) Description Control Command

integrityAlgo - EIA0 (NULL)

EIA1 (SNOW 3G),

EIA2 (AES)

Base station preferred

integrity Algorithm

CHG-SECU-INF

cipherAlgo - EEA0 (NULL),

EEA1 (SNOW 3G),

EEA2 (AES)

Base station preferred

ciphering Algorithm



1.4.5 NAS message Transmission

DL Information Transmission

Since a Downlink NAS Transport message belongs to the UE associated signaling, the

MME can send a Downlink NAS Transport message after receiving the Initial UE message

from the eNB. When the eNB sends the Initial UE message, the MME allocates

MME_UE_S1AP_ID and can then send a Downlink NAS Transport message.

When it receives a Downlink NAS Transport message, the eNB sends it to the UE

transparently via a radio interface. The Handover Restriction List IE, which denotes the

information for roaming areas and access restriction areas, can be contained in the

Downlink NAS message. The eNB must use this information when performing handover to

the target cell.

Figure 1.9 Downlink NAS Transmission Procedure

UL Information Transmission

When the eNB receives over the radio interface the NAS message to be sent to the MME,

the eNB adds the NAS message to the NAS PDU IE which is included in the uplink NAS

transport message and then sends the message. Whenever the eNB sends a message, it

includes the TAI and ECGI of the current cell in the message. The MME continuously

knows the current TAI and ECGI values owned by the UE, from the TAI and ECGI values

included in the message from the eNB. The NAS-PDU IE is a message which is not

interpreted within the eNB.

Figure 1.10 Uplink NAS Transmission Procedure

UE MME Source

eNB

Target

eNB

S1AP: Uplink NAS Transport

RRC UL Information Transfer

UE MME Source

eNB

Target

eNB

S1AP: Downlink NAS Transport

RRC DL Information Transfer



NAS Information concatenation

Besides transmitting the NAS message to the UE or MMS using the DL message, or UL

NAS message, the ECCB block can concatenate the NAS information to the RRC or S1AP

message and send it.

NAS information received using the S1AP message is concatenated to the RRC message

and is then sent when:

The NAS information contained in the E_RAB Setup Request message is included in

the RRC Connection Reconfiguration message and is then sent

The information contained in the E_RAB Modify Request message is included in the

RRC Connection Reconfiguration message and is then sent

The information contained in the E_RAB Release Command message as optional

information is included in the RRC Connection Reconfiguration message and is then

sent

The information contained in the Initial Context Setup Request message as optional

information is included in the RRC Connection Reconfiguration message and is then

sent

NAS information received using the RRC message is concatenated to the S1AP message

and is then sent when:

The NAS information contained in the RRC Connection Setup Complete message is

included in the Initial UE message and is then sent



1.4.6 Measurement Configuration and Reporting

The UE reports measured information to the eNB in accordance with the measurement

configuration provided by the eNB. The measurement configuration provided by the eNB

is applied to the UE in the RRC_CONNECTED status. That is, by using dedicated

signaling when the RRCConnectionReconfiguration message is used, the eNB sends the

measurement configuration information to the UE. The measurements the eNB can request

from the UE can be classified into five types, as listed in the table below.

Type Description

Intra-frequency

measurements

Performs measurement on the frequency which is identical to the

downlink carrier frequency of the serving cell.

Inter-frequency

measurements

Performs measurement on the frequency which is different to the

downlink carrier frequency of the serving cell.

Inter-RAT measurements

of UTRA frequencies

Performs measurement on the UTRA frequencies.


of GERAN frequencies

Performs measurement on the GERAN frequency.


of CDMA2000

HRPD/1xRTT frequencies

Performs measurement on the CDMA 2000 HRPD/1xRTT

frequencies.

The following parameters are included in the measurement configuration provided to the UE.


Measurement objects The object on which the UE must perform measurements.

The measurement object is a single E-UTRA carrier frequency for

intra-frequency and inter-frequency; a single UTRA carrier frequency

for inter-RAT UTRA; a set of GERAN carrier frequencies for inter-RAT

GERAN; and a set of single CDMA2000 (HRPD or 1xRTT) carrier

frequencies for inter-RAT CDMA2000.

Reporting configuration The reproting configuration list, each item of which consists of the

reporting criterion and the report format. The reporting criterion is the

reference information that the UE triggers to send a measurement

report. It is either a periodical event or a single event. The report format

includes the quantity information and the related information included

by the UE in a measurement report (e.g. number of cells to report).

Measurement identities The measurement identity list, each item of which is associated with

one measurement object and one reporting configuration.

Quantity configuration Quantity configuration includes the measurement quantities and

related filtering information for all event evaluation, each of which is

set by the RAT type.

Measurement gaps The period of time during which the UE performs measurements.

UL/DL data transmission is restricted during this period.



The table below lists the measurement event types that can be set currently in the eNB, and

provides descriptions of them.

Event Type Description

A1 Performs the Measurement Gap Deactivation.

A2 Performs the Measurement Gap Activation.

A3 Performs the Inter LTE Handover or the Automatic Neighbor Relation (ANR).

B2 Performs the Inter RAT Handover.

The following lists the commands for setting the measurement configuration information

and their parameters.


CHG-MEAS-INF

(PERCELL)

Changes the eNB‟s statistics collection status (STOP/START) and the

statistics collection status (ENABLE/DISABLE) for each family.

CHG-MSGAP-INF Changes the measurement gap in the cell set in the base station.

It receives the DB Index parameter value and modifies the gap pattern for

the DB‟s Inter FA, Inter RAT and ANR.

CHG-EUTRA-FA

(PERCELL)

Changes the parameter information required to process EUTRA FA

priority information. It receives the Cell Num and FA Index parameter

values and modifies the information of the EUTRA FA registered to the

cell within the base station.

CHG-EUTRA-A1CNF Changes the EUTRA A1 criteria. It receives the CELL_NUM and

PURPOSE parameter values to modify the information of the EUTRAN

A1 event report registered to the corresponding E-UTRAN served cell.

CHG-EUTRA-A2CNF

(PERCELL)

Changes the EUTRA A2 criteria. It receives the CELL_NUM and



CHG-EUTRA-A3CNF

(PERCELL)




CHG-EUTRA-A4CNF

(PERCELL)




CHG-EUTRA-A5CNF

(PERCELL)




CHG-EUTRA-PRD

(PERCELL)

Changes the EUTRA periodic criteria. It receives the CELL_NUM and


periodic report registered to the corresponding E-UTRAN served cell.

CHG-QUANT-EUTRA

(PERCELL)

Changes the quantity setting for the EUTRA measurement. It receives the

Cell Num value and modifies the measurement quantity for the EUTRAN

registered to the corresponding cell.



(Continued)


CHG-UTRA-FA

(PERCELL)

Changes the UTRA FA priority information. It receives the Cell Num and

FA Index values and modifies the information of the UTRAN FA

registered to the corresponding cell within the base station.

CHG-UTRA-B1CNF

(PERCELL)

Changes the UTRA B1 criteria. It receives the CELL_NUM and

PURPOSE parameter values to modify the information of the UTRAN B1

event report registered to the corresponding E-UTRAN served cell.

CHG-UTRA-B2CNF

(PERCELL)

Changes the UTRA B2 criteria. It receives the CELL_NUM and

PURPOSE parameter values to modify the information of the UTRAN B2

event report registered to the corresponding E-UTRAN served cell.

CHG-UTRA-PRD

(PERCELL)

Changes the UTRA periodic criteria. It receives the CELL_NUM and

PURPOSE parameter values to modify the information of the UTRAN

periodic report registered to the corresponding E-UTRAN served cell.

CHG-QUANT-UTRA

(PERCELL)

Changes the quantity setting for the UTRA FDD/TDD measurement. It

receives the Cell Num value and modifies the measurement quantity for

the UTRAN registered to the corresponding cell.

CHG-C1XRTT-FREQ

(PERCELL)

Changes the CDMA2000 1xRTT carrier information. It receives the Cell

Num and carrier index values and modifies the information of the 2000

1XRTT carrier registered to the corresponding cell within the base station.

CHG-C1XRTT-

B1CNF (PERCELL)

Changes the CDMA2000 1xRTT B1 criteria. It receives the CELL_NUM

and PURPOSE parameter values to modify the information of the CDMA

1xRTT B1 event report registered to the corresponding E-UTRAN served

cell.

CHG-C1XRTT-

B2CNF (PERCELL)

Changes the CDMA2000 1xRTT B2 criteria. It receives the CELL_NUM


1xRTT B2 event report registered to the corresponding E-UTRAN served

cell.

CHG-C1XRTT-PRD

(PERCELL)

Changes the CDMA2000 1xRTT periodic criteria. It receives the

CELL_NUM and PURPOSE parameter values to modify the information

of the CDMA HRPD periodic report registered to the corresponding E-

UTRAN served cell.

CHG-HRPD-FREQ

(PERCELL)

Changes the CDMA2000 HRPD carrier information. It receives the Cell

Num and carrier index values and modifies the information of the

CDMA2000 HRPD carrier registered to the cell within the base station.

CHG-HRPD-B1CNF

(PERCELL)

Changes the CDMA2000 HRPD B1 criteria. It receives the CELL_NUM


HRPD B1 event report registered to the corresponding E-UTRAN served

cell.

CHG-HRPD-B2CNF

(PERCELL)

Changes the CDMA2000 HRPD B2 criteria. It receives the CELL_NUM


HRPD B2 event report registered to the corresponding E-UTRAN served

cell.



(Continued)


CHG-HRPD-PRD

(PERCELL)

Changes the CDMA2000 HRPD periodic criteria. It receives the Cell Num

and Purpose values and modifies the corresponding periodic report's max

report cell and report interval information.

CHG-QUANT-CDMA

(PERCELL)

Changes the quantity setting for the CDMA2000 measurement. It receives

the Cell Num value and modifies the measurement quantity for the CDMA

registered to the corresponding cell.



1.4.7 E-RAB Bearer Control

E-RAB Setup

The E-RAB Setup function allocates one or more E-RAB resources on the S1 or Uu to the

UE, and sets up the E-RABs for the given UE. The detailed flow is provided below:

Figure 1.11 E-RAB Setup Procedure

The E-RAB setup procedure starts when the MME sends the E-RAB Setup Request

message to the eNB. When it receives the E-RAB Setup Request message, the ECCB of the

eNB allocates resources in accordance with the given E-RAB configuration, that is, the

E-RAB level QoS parameters (QCI, Allocation and Retention Priority, and GBR QoS

Information). The eNB saves the MAC/PHY information changed by the E-RAB setup

process and sends RRC Connection Reconfiguration to the UE.

When eNB receives from the UE the L2Ack message which confirms the RRC Connection

Reconfiguration message has been received, the Setup message is sent to the GTP, PDCP,

RLC, and MAC blocks within the base station, based on the configured resources.

When the RRC Connection Complete message is received from the UE and a response

message to the Setup message is received from all of those protocol blocks within the base

station, the information is saved, and the E-RAB Setup Response message is sent to the

EPC via the interface with the SCTP. Thus the E-RAB Setup procedure is completed.

Serving eNB

PHY/MA

C

RLCB SCTB GTPB


UE EPC

MME SGW

RRC_CONNETED



msgCsctpDatalnd ERAB Setup Request (+NAS PDU)



msgCrlcConfigReq x (DRBs)

msgCpdcpConfigReq x (DRBs)

msgCgtpSetupReq (S1-U) x (DRBs)

msgCgtpSetupCnf (S1-U) x (DRBs)

msgCmacPhyConfigCnf x n

msgCrlcConfigCnf x (DRBs)

msgCpdcpConfigCnf x (DRBs)

SRB #1/RLC-AM/ DCCH/UL-SCH Uplink Information Transfer (+NAS PDU)



msgCrlcDatalnd msgCpdcpDataTransfe

rlnd

msgCsctpDataReq

msgCsctpDataReq

ERAB Setup Response

Uplink NAS Transport (+NAS PDU)

RRC_CONNETED

msgCmacPhyReconfigCommit (DRBs)

PDCB ERMB ECCB


L2ack



E-RAB Release

The E-RAB Release function releases the E-RAB(s) previously set up for a specific UE.

The figure below shows the details of this function and its flow.

Figure 1.12 E-RAB Release Procedure

The E-RAB Release procedure starts when the MME sends the E-RAB Release Command

message to the eNB. When it receives the E-RAB Release Command message, the ECCB

of the eNB performs release of the requested E-RAB(s). The eNB saves the MAC/PHY

information changed by the E-RAB release process and sends RRC Connection

Reconfiguration to the UE.

When the eNB receives from the UE the L2Ack message which confirms that the RRC

Connection Reconfiguration message has been received, the release message for the E-RAB

is sent to the GTP/PDCP/RLC/MAC block within the base station.

When the eNB receives the RRC Connection Reconfiguration Complete message from the

UE and response messages for the release message from all relevant protocol blocks within

the base station, it saves the information and relays the E-RAB release response message to

the EPC over the SCTP interface to complete the E-RAB release process.

Serving eNB

PHY/MA

C

RLCB SCTB GTPB PDCB ERMB ECCB


UE EPC

MME SGW

RRC_CONNETED



msgCsctpDatalnd ERAB Release Command (+NAS PDU)


msgCmacPhyReconfigPerpare

msgCrlcReleaseReq x (DRBs)

msgCpdcpReleaseReq x (DRBs)

msgCgtpReleaseReq (S1-U) x (DRBs)

msgCgtpReleaseCnf (S1-U) x (DRBs)

msgCmacPhyReconfigReady

msgCrlcReleaseCnf x (DRBs)

msgCpdcpReleaseCnf x (DRBs)

SRB #1/RLC-AM/DCCH/UL-SCH

Uplink Information Transfer (+NAS PDU)




msgCsctppDataReq

msgCsctppDataReq

ERAB Release Response


RRC_CONNECTED

L2ac

k Rrc Connection Reconfiguration Complete




E-RAB Modification

The E-RAB modification function modifies the E-RAB(s) previously set up for a specific

UE. The figure below shows the details of this function and its flow.

Figure 1.13 E-RAB Modification Procedure

The E-RAB Modification procedure starts when the MME sends an E-RAB Modify

Request message to the eNB. When it receives the E-RAB Modify Request message, the

ECCB of the eNB allocates resources in accordance with the changed E-RAB

configuration, that is, the E-RAB level QoS parameters (QCI, Allocation and Retention

Priority, and GBR QoS Information). The eNB saves the MAC/PHY information changed

by the E-RAB modification process and sends RRC Connection Reconfiguration to the UE.

When eNB receives from the UE the L2Ack message which confirms the RRC Connection

Reconfiguration message has been received, the Modify message is sent to the PDCP, RLC,

MAC, and GTP blocks within the base station, based on the configured resources.

When the eNB receives the RRC Connection Reconfiguration Complete message from the

UE and response messages for the modify message from all relevant protocol blocks within

the base station, it saves the information and relays the E-RAB modify response message to

the EPC over the SCTP interface to complete the E-RAB modification process.

For related commands and parameters, see „RRC Connection Reconfiguration‟.

L2ac

k

Serving eNB

PHY/MA

C

RLCB SCTB GTPB PDCB ERMB ECCB


UE EPC

MME SGW

RRC_CONNETED



msgCsctpDatalnd ERAB Modify Request (+NAS PDU)


msgCrlcModifyReq x (DRBs)

msgCpdcpModifyReq x (DRBs)

msgCgtpModifyReq (S1-U) x (DRBs)

msgCgtpModifyCnf (S1-U) x (DRBs)

msgCmacPhyReconfigReady x (DRBs)

msgCrlcModifyCnf x (DRBs)

msgCpdcpModifyCnf x (DRBs)



Uplink Information Transfer (+NAS PDU)




msgCsctpDataReq

msgCsctpDataReq

ERAB Modify Response


RRC_CONNECTED





1.4.8 RRC Connection Re-establishment

The purpose of the RRC Connection Reestablishment procedure is to reestablish the

SRB #1 and reactivate security, without any changes in the algorithm. This procedure can

be performed if the eNB has a valid UE context when an RRC connection reestablishment

request is received from the UE. Therefore, the eNB can perform the RRC Connection

Reestablishment procedure when an RRC connection reestablishment request is received

where the new target is the serving cell, another cell that belongs to the serving cell‟s base

station, the source/target cell in the handover operation, or another cell that belongs to the

target base station in the handover operation.

The UE requests RRC connection reestablishment when any of the following occurs: radio

link failure, handover failure, integrity check failure, and RRC connection reconfiguration

failure.

When receiving an RRC connection reestablishment request from the UE, the base station

finishes the reestablishment procedure for the SRB #1 in accordance with the UE‟s context,

and then sends the RRC Connection Re-establishment message to the UE. When receiving

the RRC Connection Re-establishment Complete message from the UE, the base station

sets up the SRB #2 and DRB(s) in accordance with the existing configuration, and then

sends an RRC Connection Reconfiguration message to the UE. When the RRC Connection

Reconfiguration Complete message is received from the UE, the RRC Connection

Reestablishment procedure is completed.

As mentioned above, the RRC connection reestablishment procedure can be triggered by

various scenarios. The details of the procedure differ depending on the scenario, but the

basic concept is the same. Therefore, this document will describe the RRC Connection

Reestablishment procedure triggered when a radio link failure occurs with the UE in the

RRC connected status, and thus the UE sends an RRC Connection Re-establishment

Request messages to the cell (serving cell) from which it has received service.



Figure 1.14 RRC Connection Reestablishment Procedure

When the RRC Connection Re-establishment Request message is sent from the UE to the

serving cell, this means that the UE has already obtained a new C-RNTI through the

Random Access procedure. Therefore, to remove the MAC/PHY entity with the existing

C-RTNI, the UE sends the msgCmacPhyReleaseReq message to the base station.

When the ECCB receives the msgCmacPhyReleaseCnf message, it sends msgCpdcpControl

for re-establishing all PDCP RBs of the UE and sends msgCrlcControl for re-establishing

all RLC RBs. In addition, to set up the MAC/PHY entity with the new CRNTI, an

msgCmacPhyConfigReq message is sent. When all of the msgCpdcpControlSuccess,

msgCrlcControlSuccess, and msgCmacPhyConfigCnf messages are received for all RBs,

the base station sends an RRC Connection Re-establishment message to the UE.

Source eNB Target Cell Source Cell

PHY/MA

C

RLCB UE

RRC_CONNECTED

(Common Preamble) Random Access Preamble

PHY/MA

C

RLCB PDCB ECCB ECMB SCTB GTPB

Random Access Response

Rrc Connection Reestablishment Request


msgCrlcCommonDatalnd



msgCpdcpControl (Re-establish)

msgCrlcControl (Re-establish)

msgCmacPhyConfigCnf (Setup)

msgCpdcpControlSuccess

msgCrlcControlSuccess

msgCmacPhyConfigCnf

Rrc Connection Reestablishment

SRB #0/RLC-TM/CCCH/DL-SCH

msgCrlcCommonDataReq

msgCpdcpDataTransferlnd msgCrlcDatalnd Rrc Connection Reestablishment Complete

SRB #1/RLC-AM/CCCH/UL-SCH msgCpdcpControl (Resume-SRB #1)


msgCpdcpDataTransferReq msgCrlcpDataReq

msgCpdcpDataTransferCnf msgCrlcpDataCnf


SRB #1/RLC-AM/CCCH/DL-SCH


SRB #1/RLC-AM/CCCH/UL-SCH

msgCpdcpDataTransferlnd msgCrlcpDatalnd

PDCP Status Report in UL

PDCP Status Report in UL

msgCpdcpControl (Resume-SRB #2, DRB)


RRC_CONNECTED



When the source cell of the eNB receives the RRC connection re-establishment complete

message from the UE, the ECCB of the eNB sends the msgCpdcpControl message which

resumes the PCDP entity for SRB #1. When the ECCB receives msgCpdcpControlSuccess,

it sends the RRC connection reconfiguration message in order to setup the UE with the

configuration prior to the radio link failure.

When the source cell of the eNB receives the RRC connection reconfiguration complete

message from the UE, the ECCB of the eNB sends the msgCpdcpControl message which

resumes the PCDP entity for all RBs other than SRB #1.

When the ECCB receives msgCpdcpControlSuccess for all RBs other than SRB #1, the

RRC connection reconfiguration process is complete.

The related parameters are as follows:

Parameter Unit Range Description Control

Command

rlcControl enum RLC_NORMAL, RLC_RE_ESTABLISH,

RLC_SUSPEND, RLC_RESUME

RLC Control

Type

-

pdcpControl enum PDCP_NORMAL,

PDCP_HANDOVER_EXEC,

PDCP_HANDOVER_COMPLETE,

PDCP_REESTABLISH, PDCP_RESUME

PDCP Control

Type

-



1.4.9 UE Inactivity Control

If no traffic is received from a specific UE for a specific period of time, the UE Inactivity

Control function sends a UE Context Release Request message to the EPC to release that UE.

The Inactivity Call Release timer is passed to the MAC layer when the default bearer is set up.

Then, when the MAC layer detects user inactivity, it sends an msgCmacPhyUserInactivityInd

message to the ECCB, and then the ECCB performs the UE Context Release procedure.

The detailed flow is provided below:

Figure 1.15 UE Inactivity Control Procedure



Command

internaUserInactivity Sec 0~65535 This parameter is used when the MAC

detects user inactivity. If there is no user

traffic for the period of time specified by

this parameter, it is notified to the ECCB.

-

Serving eNB


msgCmaPhyUserInactivitylnd

UE EPC

MME SGW

RRC_IDLE


RRC_IDLE

msgCsctpDataReq UE Context Release Request

msgCsctpDatalnd RRC Connection Release msgCrlcDataReq msgCpdcpDataTransferReq



msgCrlcReleaseReq (SRB #1)


msgCrlcReleaseReq (SRB #2)


msgCrlcReleaseReq (x DRBs)

msgCpdcpReleaseReq (x DRBs)

msgCgtpReleaseReq (x DRBs)


msgCrlcReleaseCnf (SRB #1)

msgCpdcpReleaseCnf (SRB #1)

msgCrlcReleaseCnf (SRB #2)

msgCpdcpReleaseCnf (SRB #2)

msgCrlcReleaseCnf (x DRBs)

msgCpdcpReleaseCnf (x DRBs)

msgCgtpReleaseCnf (x DRBs)

msgCsctpDataReq UE Context Release Complete

UE Context Release Procedure

UE Context Release Command



1.4.10 RLF Control

If the MAC fails to detect the uplink signal of the UE in interoperation with the physical

layer, the RLF control function sends an msgCmacPhyOutOfSynchInd message to the

ECCB. When it receives the message, the ECCB attaches a timer to receive the Re-

establishmentRequest message from the UE, and waits for the Re-establishmentRequest

message from the UE.

When receiving the Re-establishmnetRequest message from the UE, the ECCB performs

the Re-establishment procedure. If a time-out occurs, it performs the call release procedure.

The call release procedure is identical to the „UE inactivity control‟ procedure.



Command

internaReestablsh

TimeToWait

msec 0~65535 The time to wait for the Re-establishment

Request message when an Out of Synch

message is received from the MAC

-



1.5 Intra-LTE Handover

1.5.1 Intra-eNB Handover

When the UE moves between cells belonging to the same eNB, the handover function is

carried out. The Intra-eNB handover is performed as follows: The PDCB becomes an

anchor through PDCP Re-establishment, the channel card is switched, and the RLC context

does not persist, but is reset through RLC Re-establishment. Therefore, for lossless data

transmission, the functions of PDCP SDU retransmission at the PDCP terminal, PDCP

status reporting, in-order delivery, and duplication elimination are carried out.

Figure 1.16 Intra-eNB Handover Procedure

1) The UE sends the MeasurementReport message according to the system information,

standards and rules. The source eNB determines whether to handover the UE based on

the MeasurementReport message and the radio resource management information.

At this time, when the determined target cell is located in the same eNB as the current

source cell, the intra-eNB handover procedure is performed.

2) The source eNB commands the UE to perform handover to the target cell by sending the

UE an RRCConnectionReconfiguration message containing the mobileControlInfo IE.

3) After receiving the RRCConnectionReconfiguration message containing the

mobileControlInfo IE, the UE performs synchronization with the target cell and

connects to the target cell via a Random Access Channel (RACH). The target cell

replies with an allocated UL and a timing advance value.

4) After having connected to the target cell successfully, the UE notifies the target cell

that the Handover procedure has been completed, using an ReconfigurationComplete

message.

For related commands and parameters, see „Inter-eNB X2 Handover‟

UE Source eNB

1) MeasurementReport

2) RRCConnectionReconfiguration

3) Synchronization/UL allocation and timing advance

{mobilityControlinfo}

4) RRCConnection ReconfigurationComplete



1.5.2 Inter-eNB X2 Handover

When the UE moves between cells belonging to different eNBs which belong to the same

MME group, the Handover function is carried out via the X2 interface.

When performing handover via the X2 interface, the target eNB determines whether to

perform uplink data forwarding. The source eNB performs uplink data forwarding only

when the target eNB admits it.

During handover, after configuring the SDU for the uplink PDU of the AM-Mode that is

not sent to the PDCB through RLC Re-establishment, the RLCB of the source eNB

performs the procedure for sending that SDU to the PDCB. When uplink data forwarding is

performed, after receiving the SDU from the RLCB, the PDCB configures the PDCP SN

status information including that SDU. When uplink data forwarding is not performed, the

PDCB configures the PDCP SN status information based on the uplink data currently

received.

Figure 1.17 Inter-eNB X2 Handover Procedure

UE Source eNB MME S-GW

EPC

1) MeasurementReport

Target eNB

Downlink/Uplink data Downlink/Uplink data

3) HANDOVER REQUEST ACKNOWLEDGE

5) SN STATUS TRANSFER

4) RRCConnection-

Reconfiguration

(mobilityControlinfo)

Data forwarding

6) Synchronization/UL allocation and timing advance

7) RRCConnectionReconfigurationComplete

Forwarded data

Uplink data

Forwarded data

Downlink data

Down/Uplink data Down/Uplink data

Uplink data

Downlink data

8) PATH SWITCH REQUEST 9) Modify Bearer Request

End marker

End marker

10) Modify Bearer Response 11) PATH SWITCH

REQUEST

ACKNOWLEDGE 12) UE CONTEXT RELEASE

2) HANDOVER REQUEST



1) The UE sends the MeasurementReport message according to the system information,

standards and rules. The source eNB determines whether to admit the UE 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 received E-RAB QoS information.

3) The target eNB prepares the handover and creates an RRCConnectionReconfiguration

message, containing the mobileControlInfo IE that tells the source eNB to perform the

handover. The target eNB includes the RRCConnectionReconfiguration message in the

HANDOVER REQUEST ACKNOWLEDGE message, and sends it to the source eNB.

4) The source eNB sends the UE an RRCConnectionReconfiguration message, containing

the needed parameter values to command it to perform the handover.

5) To send the uplink PDCP SN receiver status and the downlink PDCP SN transmitter

status of the E-RABs of which the PDCP status must be preserved, the source eNB

sends the SN STATUS TRANSFER message to the target eNB.

6) After receiving the RRCConnectionReconfiguration message containing the

mobileControlInfo IE, the UE performs synchronization with the target eNB and

accesses the target cell via the Random Access CHannel (RACH). The target eNB

replies with an allocated UL 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) 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 sends at least one „end marker‟

to the source eNB through the previous path, and releases the user plane resources for

the source eNB.

10) The S-GW sends a Modify Bearer Response message to the MME.

11) The MME sends 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.

When receiving the UE CONTEXT RELEASE messages, the source eNB released the

radio resource and the control plane resource related to the UE context.

The related commands and parameters are as follows.


CHG-NBR-ENB Changes the information of the neighbor eNB required for the operation

of the neighbor eNB. It receives the NBR_ENB_INDEX parameter value

to modify the neighbor eNB information.

CHG-NBR-EUTRA Changes the information of the E-UTRAN neighbor cell located near the

base station. It receives the CELL_NUM and RELATION_IDX parameter

values and modifies the E-UTRAN neighbor cell information.



1.5.3 Inter-eNB S1 Handover

When the UE moves between cells belonging to different eNBs, the Handover function is

carried out via the S1 interface. Generally, when two eNBs belong to the same MME group,

handover is performed via the X2 interface. When two eNBs belong to different MME

groups, handover is performed via the S1 interface. However, if they belong to the same

MME, but there is no X2 interface between the two eNBs, handover is performed via the

S1 interface. In addition, in the case of data forwarding, although handover is performed

via the S1 interface, if there is an X2 interface between the two eNBs, direct data

forwarding is performed via the X2-U. If there is no X2 interface between the two eNBs,

indirect data forwarding is performed via the S1-U.



Figure 1.18 Inter-eNB S1 Handover Procedure

UE Source eNB MME S-GW

EPC

Target eNB


3) HANDOVER REQUEST

5) Create Indirect Data

Forwarding Tunnel Request

8) RRCConnection-

Reconfiguration

(mobilityControlinfo)

1) Direct data forwarding

1) Decision to trigger a relocation via S1

2) HANDOVER REQUIRED

Indirect data forwarding

Downlink data

Downlink data

End marker

End marker

6) Create Indirect Data

Forwarding Tunnel Response 7) HANDOVER COMMAND

9) eNB STATUS TRANSFER

10) MME STATUS TRANSFER

2) Indirect data fowarding

11) Detach from old cell/Synchronize to new cell

12) RRCConnectionReconfigurationComplete

Forwarded data

Uplink data Uplink data

13) HANDOVER NOTIFY 14) Modify Bearer Request

15) Modify Bearer Response

Forwarded data

16) Tracking Area Update procedure

17) UE CONTEXT RELEASE COMMAND

18) UE CONTEXT RELEASE COMPLETE

19) Delete Indirect Data

Forwarding Tunnel Request

20) Delete Indirect Data

Forwarding Tunnel Response


4) HANDOVER REQUEST ACKNOWLEDGE



1) The source eNB determines whether to perform S1-based handover into the target eNB.

This decision can be made when there is no X2 connection to the target eNB, or when

the inter-eNB handover with the target eNB is set to run the S1 handover.

2) The source eNB sends the HANDOVER REQUIRED message to the MME.

The source eNB notifies the target eNB which bearer is used for data forwarding and

whether forwarding can be made directly from the source eNB to the target eNB.

3) The MME sends the HANDOVER REQUEST message to the target eNB.

This message makes the target eNB to create a UE context containing the bearer-

related information and the security context.

4) The target eNB sends the HANDOVER REQUEST ACKNOWLEDGE message to the

MME.

5) If indirect forwarding is used, the MME sends the Create Indirect Data Forwarding

Tunnel Request message to the S-GW.

6) The S-GW replies to the MME with the Create Indirect Data Forwarding Tunnel

Response message.

7) The MME sends the HANDOVER COMMAND message to the source eNB.

8) The source eNB creates the RRCConnectionReconfiguration message using the Target

to Source Transparent Container IE value contained in the HANDOVER COMMAND

message and then sends it to the UE.

9) To send the PDCP status, and the HFN status of the E-RABs of which the PDCP status

must be preserved, the source eNB sends the eNB/MME STATUS TRANSFER

message to the target eNB via the MME.

10) The source eNB must 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 replies with an allocated UL 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 cab be sent to the UE.

The uplink packets can be also sent from the UE to the S-GW via 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 will be released.

14) For each PDN connection, the MME sends the Modify Bearer Request message to the

S-GW. Downlink packets are sent from the S-GW to the target eNB immediately.

15) The S-GW sends a Modify Bearer Response message to the MME. As soon as the

target eNB changes the path to help packet reordering, the S-GW sends 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) When the timer started at step 13 expires, the MME sends the UE CONTEXT

RELEASE COMMAND message to the source eNB.



18) The source eNB releases the resources related to the UE and replies to the target eNB

with the UE CONTEXT RELEASE COMPLETE message.

19) If indirect forwarding has been used, when the timer started at step 13 expires the

MME sends 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.

20) The S-GW replies to the MME with the Delete Indirect Data Forwarding Tunnel

Response message.

For related commands and parameters, see „Inter-eNB X2 Handover‟.



1.6 Inter-RAT Mobility

1.6.1 LTE-HRPD Interoperation

Interoperation of the E-UTRAN and CDMA2000 HRPD consists of the transparent Pre-

registration procedure, and the Handover Signaling Transmission procedure between the

UE and the target access system. The purpose of these procedures is to minimize the total

service interruption time that occurs as the E-UTRAN to CDMA2000 HRPD handover is

performed. The network interoperation between systems is overlaid.

The E-UTRAN must broadcast to the SIB8 the information required for the UE to access

the target CDMA2000 HRPD. The UE performs pre-registration to the target CDMA2000

HRPD network, or performs cell reselection (Idle-mode Optimized Handover procedure),

referring to the preRegistrationInfoHRPD and cellReselectionParametersHRPD

information for the SIB8.

Also, when the UE in the Connected status performs handover to the target CDMA2000

HRPD, the E-UTRAN provides the E-UTRAN to CDMA2000 HRPD Handover function

via the S1 interface, and the Indirect Data Forwarding function via the S1-U.

S101 interface (between the EUTRAN and HRPD AN) is necessary to support the pre-

registration and HRPD handover function.

The optimized handover in the E-UTRAN to CDMA2000 HRPD Handover function

consists of two steps: first, when the UE performs pre-registration to the target CDMA2000

HRPD, and second, when handover is actually performed.

When the UE has succeeded in pre-registration, if the handover preparation fails when

performing the actual handover, the E-UTRAN sends the RRC Connection Release with

Redirection message to the UE. At this time, the UE reselects the target CDMA2000 HRPD

cell and performs the Idle-mode Optimized Handover procedure. Further, if the E-UTRAN

does not support the SIB8 required for interoperation with the CDMA2000 HRPD, when

the E-UTRAN receives from the UE the measurement report related to interoperation with

the CDMA2000 HRPD, the E-UTRAN supports a function that commands the UE to

perform non-optimized handover (sends the RRC Connection Release with Redirection

message).



Figure 1.19 LTE-HRPD Interoperation Procedure 1

1) The UE creates the UL HRPD message and sends the UL Information Transfer

message to the eNB.

2) When the eNB receives the UL Information Transfer message, it sends the Uplink S1

CDMA2000 Tunneling message to the MME.

3) The MME sends the Downlink S1 CDMA2000 Tunneling message to the eNB.

4) The eNB sends the DL Information Transfer message to the UE.

Source eNB LACA RANA RNSU

PHY/MAC RLCB SCTB GTPB PDCB ERMB E(H)CCB

UE EPC

MME S/GW

RRC_CONNECTED

HRPD Radio Session Establishment Signalling

1) UL Information Transfer

SRB#1/RLC-AM/DCCH/UL-SCH

4) DL Information Transfer

SRB#1/RLC-AM/DCCH/DL-SCH




msgCsctpDataReq 2) UL S1 cdma2000 Tunneling

msgCsctpDatalnd 3) DL S1 cdma2000 Tunneling

HRPD EAP-AKA Authentication

HRPD IP Session Establishment Siganalling

HRPD L2 Session Maintenance

CDMA2000 HRPD Pre-Registration Procedure



The following steps are identical to those above. The 4-step pre-registration is performed.

HRPD Radio Session Establishment Signalling

HRPD EAP-AKA Authentication

HRPD IP Session Establishment Signalling

HRPD L2 Session Maintenance


Source eNB

LACA RANA RNSU

PHY/MAC RLCB SCTB GTPB PDCB ERMB E(H)CC

B

UE EPC

MME S/GW

RRC_CONNECTED 1) Measurement Report

SRB#1 or 2/RLC-AM/DCCH/UL-SCH

6) Mobility From EUTRA Command

SRB#1 or 2/RLC-AM/DCCH/DL-SCH




7) msgCgtpSetupReq (S1-U/DL Forwarding)

8) msgCgtpSetupCnf (S1-U/DL Forwarding)

EUTRAN to HRPD Handover (Optimized Handover)-Preparation OK

Handover Decision

2) Handover From EUTRA Preparation Request msgCrlcDataReq msgCpdcpDataTransferReq

SRB#1 or 2/RLC-AM/DCCH/DL-SCH msgCrlcDataCnf msgCpdcpDataTransferCnf

3) UL Handover Preparation Transfer





9) msgCpdcpControl (Handover Execution)

10) msgCrlcControl (Re-establish)

11) msgCpdcpControlSuccess

12) msgCrlcControlSuccess

DL/UL Data Forwarding

msgCsctpDatalnd 13) UE Context Release Command

14) msgCpdcpBufferFlushReq

15) msgCpdcpBufferFlushCnf

16) msgCpdcpReleaseReq

17) msgCrlcReleaseReq

18) msgCcallReleaseReq

19) msgCgtpReleaseReq (S1-U)

20) msgCgtpReleaseReq (S1-U/DU Forwarding)

21) msgCpdcpReleaseCnf

23) msgCcallReleaseCnf

22) msgCrlcReleaseCnf

24) msgCgtpRelease (S1-U)

25) msgCgtpReleaseCnf (S1-U/DL Forawrding)

msgCsctpDataReq 26) UE Context Release Complete

RRC_IDLE

msgCmacPhyRTDInfoReq

msgCmacPhyRTDInfoCnf



1) If the Pre-registration procedure has been performed normally, and a HRPD

Dormant session has been set up, the UE sends the measurement report to the eNB

to perform the Handover procedure in accordance with the measurement

configuration configured during call setup.

2) When it receives the Measurement report from the UE, the eNB determines whether

to perform handover from the E-UTRAN to the HRPD through the handover

decision, and sends the Handover from E-UTRA Preparation Request message to

the UE.

3) When it receives the handover decision signal, the UE sends the UL Handover

Preparation Transfer message (HRPD message starting HO access) to the eNB.

4) When it receives the UL Handover Preparation Transfer message, the eNB sends the

MME the Uplink S1 CDMA2000 Tunneling message containing the HRPD

message starting HO access, SectorID, and CDMA2000 HO Required Indication

information as parameters.

5-6) After receiving the Downlink S1 CDMA2000 Tunneling message (HRPD message

with HO access information, S-GW address, S1-U uplink TEID(s), CDMA2000 HO

status) from the MME, when the preparation is completed, the eNB sends the UE

the Mobility from E-UTRA command message to command it to perform handover.

7-11) Having confirmed that the UE has received the Mobility from E-UTRA Command

message through the RLC ARQ function, the GTP tunnel is set up for downlink data

forwarding and uplink data forwarding. After the GTP tunnel has been set up, the

PDCP Control message is sent to command to perform uplink/downlink data

forwarding.

12) The ECCB notifies the RLCB that the handover has occurred, using the

msgCrlcControl (Re-establish) message. When it receives this message, the RLCB

configures the SDU for the uplink PDU of the AM-Mode that has not been sent to

the PDCB, and sends it to the PDCB. The ECCB notifies the PDCB that Inter RAT

handover has occurred, using the msgCpdcpControl (Handover Execute) message.

When it receives this message, the PDCP sends the ECCB the PDCP SN Status

information sent to, and received from, the UE using the msgCpdcpControlSuccess

message until the present time, and performs data forwarding for downlink and

uplink data to the HRPD (indirect forwarding to the MME).

13-15) When it receives the UE Context Release Command message from the MME

(which notifies that all handovers have been completed), the ECCB sends the

msgCpdcpBufferFlushReq message to the PDCB to flush the buffer, and tell the

PDCB to end data forwarding. When receiving this message, the PDCB sends the

end-marker to the HRPD AN after data forwarding for all downlink and uplink data

has been completed, and sends the msgCpdcpBufferFlushCnf message to the ECCB.

16-25) The ECCB sends the msgCpdcpReleaseReq, msgCgtpReleaseReq,

msgCrlcReleaseReq, and msgCmacPhyReleaseReq messages to request release of

all GTP, PDCP, RLC, MAC, and PHY resources from the eNB.

26) When it is confirmed through a Confirm message that all PDCP, RLC, MAC, and

PHY resources have been released, the ECCB sends the UE Context Release

Complete message to the MME and then deletes the UE Context for the UE and

releases the call.




1) If handover needs to be performed, the UE sends the measurement report to the eNB

to perform the Handover procedure in accordance with the measurement

configuration configured during call setup.

Pre-registration with the HRPD has not yet been performed for the UE (the SIB8

message broadcast earlier did not contain the ParametersHRPD information or the

UE did not contain information required for pre-registration).

2-4) If the SIB8 message does not contain the parametersHRPD information, when

receiving the measurement report from the UE,. the eNB performs handover to the

HRPD Access network through handover decision using the Non-optimized method.

First, the ECCB sends the RRC Connection Release message to the UE.

This message must contain the redirectedCarrierInfo (cdma2000-HRPD) information,

so that the UE can redirect it to the CDMA2000 network (i.e. RRC Connection

Release with Redirection). Further, the ECCB sends the UE Context Release Request

message to the MME. Then when the ECCB receives the UE Context Release

Command message as the reply to this message, the ECCB performs the Release

procedure for the internal resources of the eNB allocated previously.

5-8) The ECCB sends the msgCpdcpReleaseReq, msgCgtpReleaseReq,

msgCrlcReleaseReq, and msgCmacPhyReleaseReq messages to request release of all

GTP, PDCP, RLC, MAC, and PHY resources from the eNB.

9-13) When it has been confirmed through a Confirm message that all GTP, PDCP, RLC,

MAC, and PHY resources have been released, the ECCB sends the UE Context

Release Complete message to the MME, and then deletes the UE Context for the UE

and releases the call.

Source eNB

LACA RANA RNSU

PHY/MAC RLCB SCTB GTPB PDCB ERMB E(H)CC

B

UE EPC

MME S/GW

RRC_CONNECTED

1) Measurement Report

SRB#1 or 2/RLC-AM/DCCH/UL-SCH


5) msgCpdcpReleaseReq

8) msgCgtpReleaseReq (S1-U)

EUTRAN to HRPD Handover (Non-Optimized Handover)

Handover Decision 2) Rrc Connection Release

With redirection msgCrlcDataReq msgCpdcpDataTransferReq

SRB#1 or 2/RLC-AM/DCCH/DL-SCH msgCrlcDataCnf msgCpdcpDataTransferCnf

msgCsctpDataReq 3) UE Context Release Request

msgCsctpDatalnd 4) UE Context Release Command

9) msgCpdcpReleaseCnf

6) msgCrlcReleaseReq

11) msgCcallReleaseCnf

10) msgCrlcReleaseCnf

RRC_IDLE

7) msgCcallReleaseReq

12) msgCgtpReleaseCnf (S1-U)

msgCsctpDataReq 13) UE Context Release Complete





CHG-CDMA-CNF Changes the information for the CDMA2000 included in the SIB.

It modifies the CDMA EUTRA Synchronization, Search Window Size, and

CSFB Support Dual Rx UE information used to configure the CDMA2000

related System Information Block (SIB).

CHG-HRPD-BCLS Changes the information for the CDMA2000 HRPD bandclass within the

base station. The CDMA2000 HRPD can have 32 bandclasses; this

command modifies the priority and other information related to the

reselection to each bandclass.

CHG-HRPD-OVL Changes the information of the HRPD Cell overlaid to the corresponding cell

within the base station. A cell can have one HRPD cell; this command

modifies the corresponding cell‟s ID and sector ID information.

CHG-HRPD-PREG Changes the CDMA2000 HRPD pre-registration information. It receives the

CELL_NUM parameter value and modifies the corresponding CDAM2000

HRPD pre-registration information.

CHG-NBR-HRPD Changes the information of the CDMA2000 HRPD neighbor cell located

near the base station. It receives the CELL_NUM and RELATION_IDX

parameter values and modifies the CDMA2000 HRPD neighbor cell

information. This command can modify the status for the PLD‟s validity, the

color code, BSM ID, BSC ID, DPSS ID and sector ID for the corresponding

CDMA2000 HRPD neighbor cell‟s cell identity, and also the CDMA2000

HRPD neighbor cell‟s bandclass, ARFCN and PN offset (physical cell ID)

information.



1.6.2 LTE-1xRTT Interoperation CS Fallback

If the UE on the E-UTRAN network wants to use the CS-domain service, the CS fallback

function enables the existing 1xCS network to be used by interoperating it with the 1xRTT

CS network.

However, the CS fallback function is available only if the E-UTRAN coverage and the

1xRTT coverage are overlapped.

Figure 1.22 LTE-1xRTT Interoperated CS Fallback Procedure 1

1) The eNB must compile and send parameter1xRTT IE of the SIB 8 to support the

CSFB function. This parameter1xRTT IE consists of csfb-RegistrationParam1xRTT,

longCodeState1xRTT, and cellReselectionParameters1xRTT.

If the 1xCS CSFB UE is idle, the service request procedure is performed.

2) The eNB receives the CSFB Parameter Requests CDMA2000 message from the 1xCS

CSFB UE.

3) The eNB receives the CSFB Parameter Requests CDMA2000 message from the 1xCS

CSFB UE. At this time, the RAND and the MobilityParametersCDMA2000 IE are

configured in the message to be sent.

4) The eNB receives the UL Information Transfer message from the 1xCS CSFB UE.

5) The eNB sends the UL S1 cdma2000 Tunneling message to the MME, referring to the

received message. At this time, the CDMA2000 SectorID and the CDMA2000 1xRTT

RAND IE are configured in the message to be sent.

6) The eNB receives the DL S1 cdma2000 Tunneling message from the MME.

7) The eNB sends the DL Information Transfer message containing the CDMA2000-

PDU IE of the received message to the 1xCS CSFB UE.

eNB


1xCS CSFB

UE

EPC

MME S/GW

RRC_CONNECTED

2) CSFB Paramenters Request CDMA2000

SRB#1/RLC-AM/DCCH/DL-SCH


1xRTT CS Pre-Registration Procedure

3) CSFB Paramenters Response CDMA2000 msgCrlcDataReq msgCpdcpDataTransferReq

SRB#1/RLC-AM/DCCH/DL-SCH msgCrlcDataCnf msgCpdcpDataTransferCnf



1) Service Request procedure if the UE is idle state




7) DL Information Transfer msgCrlcDataReq msgCpdcpDataTransferReq




Figure 1.23 LTE-1xRTT Interoperated CS Fallback Procedure 2

1) The eNB receives the UL Information Transfer message (Extended Service Request

with CS Fallback Indicator) from the 1xCS CSFB UE.

2) The eNB sends the Uplink NAS Transport message to the MME, referring to the

received message.

3) The eNB receives the S1 UE Context Modification message from the MME.

At this time, if the CS Fallback Indicator IE is set to PRESENT, the eNB determines

that the fallback function has to be carried out, and then performs the procedure.

4) The eNB sends the RRC Connection Release message to the 1xCS CSFB UE.

At this time, the eNB configures the RedirectedCarrierInfo IE (bandclass, arfcn) into

the message for redirection, and sends it to the 1xCS CSFB UE.

5) The eNB sends the S1 UE Context Release Request message to the MME.

6) The eNB receives from the MME the S1 UE Context Release Command message as

the reply to the S1 UE Context Release Request message.

7) The eNB performs the procedure for releasing the internal resources, and sends the S1

UE Context Release Complete message to the MME.

eNB


1xCS CSFB

UE

EPC

MME S/GW

RRC_CONNECTED & Registered 1xRTT CS


(Extended Service Request)



CSFB Procedure to CDMA 1xRTT Network

4) RRC Connection Release msgCrlcDataReq msgCpdcpDataTransferReq


msgCsctpDataReq 2) Uplink NAS Transport

msgCsctpDatalnd 3) S1 UE Context Modification Request

7) S1 UE Context Release Complete

msgCrlcReleaseReq

msgCpdcpReleaseReq

msgCsctpDataReq

mscCgtpReleaseReq

msgCsctpDataReq 5) S1 UE Context Release Request

msgCsctpDatalnd 6) S1 UE Context Release Command


msgCrlcReleaseCnf

msgCpdcpReleaseCnf


mscCgtpReleaseCnf

RRC_IDLE

Internal Resource Release

Procedure



The related commands are as follows:


CHG-C1XRTT-BCLS Changes the CDMA2000 1xRTT bandclass information. It receives the

BC_INDEX parameter value and modifies the corresponding CDAM2000

1XRTT bandclass information.

CHG-C1XRTT-OVL Changes the CDMA2000 1XRTT overlay information within the base

station. It changes the parameter for the reselection to the CDMA2000

1XRTT cell in an environment with overlaid EUTRAN cell and

CDMA2000 1XRTT cell.

CHG-C1XRTT-PREG Changes the CDMA2000 1xRTT CSFB-pre-registration information within

the base station. It is used when a CS registration or pre-registration from

the EUTRA cell to the CDMA200 1XRTT is required.

CHG-NBR-C1XRTT Changes the information of the CDMA2000 1XRTT neighbor cell located

near the base station. It receives the CELL_NUM and RELATION_IDX

parameter values and modifies the CDMA2000 1XRTT neighbor cell

information. This command can modify the status for the PLD‟s validity,

the SID, NID and base ID for the corresponding CDMA2000 1XRTT

neighbor cell‟s cell identity, and also the CDMA2000 1XRTT neighbor

cell‟s bandclass, ARFCN and PN offset (physical cell ID) information.



1.7 CAC

Call Admission Control (CAC) calls new calls, EPS Radio Access Bearers (E-RABs),

handover calls, and re-establishment calls. Call admission or rejection is determined

according to eNB capacity based CAC and QoS based CAC.

Each of the call admission control functions supports operator control by commands over

the LSM. Emergency calls should never be rejected by call admission control and their call

flow is controlled in association with the preemption function.

Figure 1.24 CAC Procedure

RRC

establishment

E-RAB

establishment

eNB Capacity

based CAC

MaxUeENB count

MaxUeCELL count

MaxRbCELL count

BH link usage

QoS based

CAC

Admit or Reject

Air (PRB) link usage



RRC connection establishment CAC Procedure

Figure 1.25 RRC Connection Establishment CAC Procedure

1) In the RRC Connection Establishment procedure, the eNB Capacity based CAC is

controlled for each call. When the RRC Connection Request message is received from

the UE, the procedure is started.

2) The eNB capacity-based CAC procedure is performed.

If „Current # of UEs of the eNB < MaxUeENB‟ is satisfied, the call is admitted.

Otherwise, the call is rejected.

If „Current # of UEs of the cell < MaxUeCELL‟ is satisfied, the call is admitted.


3) If the call is admitted, the RRC Connection Setup message is sent to the UE to perform

the RRC Connection Establishment procedure. If the call is rejected and is an

emergency call, the call regarded as the longest of the active calls in the cell is released.

If the call is rejected and is a normal call, the RRC Connection Release message is

sent to the UE and the call is released.

4) The RRC connection setup complete message is received from the UE.

UE EPC

MME/SGW

1) RRC Connection Request

SRB#0/RLC-TM/CCCH/UL-SCH

msgRlcCommonDatalnd

PHY/MAC/

RLC PDCB

ECCB (RRC/S1AP/

X2AP) SCTB GTPB

3) RRC Connection Setup

SRB#0/RLC-TM/CCCH/DL-SCH

msgRlcCommonDataReq

2) eNB Capa based CAC

msgCrlcConfigReq (SRB#1)

msgCmacphyConfigReq (SRB#1)

msgCpdcpConfigReq (SRB#1)

msgCrlcConfigCnf

msgCpdcpConfigCnf

msgCmacphyConfigCnf

msgPdcpDataTransferln

d

msgSctpDataReq Initial UE Message

(Attach Requst or Service Request)

4) RRC Connection Setup Complete

(NAS msg)SRB#1/RLC-AM/DCCH/UL-SCH

msgRlcDatalnd



E-RAB (DRB) Establishment CAC Procedure

Figure 1.26 E-RAB (DRB) Establishment CAC Procedure

1) After the RRC Establishment procedure, the Initial Context Setup Request message or

the E-RAB Setup/Modify Request message is received from the MME to set up the

default radio bearer and the dedicated radio bearer (hereafter, DRB). Then the eNB

Capacity based CAC and the QoS based CAC are run sequentially to perform CAC for

the call.

2) The eNB Capacity-based CAC is performed per E-RAB.

If „Current # of bearers of the cell < MaxRbCELL‟ is satisfied, the call is admitted.


3) When the E-RAB has the GBR, the QoS based CAC is performed.

If „CurrentGbrPrbUsage + ExpectedPrbUsage < MaxGbrPrbUsage‟ is satisfied for

the current cell‟s PRB usage, the call is admitted. Otherwise, the call is rejected.

If „CurrentGbrBwUsage + ExpectedBw < MaxGbrBw‟ is satisfied for the backhaul

BW, the call is admitted. Otherwise, the call is rejected.

4) If the E-RAB is admitted, the RRC Connection Reconfiguration message is sent to the

UE to perform the E-RAB (DRB) Establishment procedure.

If the call is rejected, whether to admit each E-RAB (DRB) is determined in

interoperation with the preemption function to control the flow of the call.

(Note that partial success of each E-RAB is not considered.)

UE EPC

MME/SGW

msgCrlcConfigReq (DRB)

PHY/MAC/

RLC PDCB

ECCB (RRC/S1AP/

X2AP)

SCTB GTPB

msgCmacphyConfigReq (DRB)


msgRlcDataReq msgPdcpDataTransferReq

msgSctpDatalnd

msgCgtpSetupReq

msgCpdcpConfigReq

msgCrlcConfigCnf

1) E-RAB Setup Request (+NAS PDU)

4) RRC

Connection

Reconfiguration

(+NAS PDU)

SRB#1/RLC-AM/DCCH/

DL-SCH

msgCpdcpConfigCnf

3) QoS Based CAC

msgCgtpSetupCnf

msgCmacphyConfigCnf

msgRlcDatalnd msgPdcpDataTransferCnf

msgRlcDatalnd msgPdcpDataTransferlnd msgSctpDataReq E-RAB Setup

Response



Intra-eNB HO Call Admission Procedure

Figure 1.27 Intra-eNB HO CAC Procedure

1) When a cell change occurs in the same eNB, the intra-eNB handover CAC is

performed using the eNB Capacity Based CAC, and the QoS Based CAC.

2) The call-based eNB Capacity based CAC is performed.







the target cell‟s PRB usage, the call is admitted. Otherwise, the call is rejected.

4) If the call is admitted, the RRC Connection Reconfiguration message is sent to

perform the Intra-eNB handover procedure. If the call is rejected, whether to admit

each E-RAB is determined in interoperation with the preemption function to control

the flow of the call. (Note that partial success of each E-RAB is not considered.)

5) RRC connection reconfiguration complete is received from the UE.

UE ECCB

(RRC/S1AP/X2AP)

SCTB GTPB PDCB

MME/SGW

EPC Target

PHY/MAC/RLC

Source

PHY/MAC/RLC

Measurement Report

1) Handover Decision


3) QoS Based CAC

SRC #1/RLC-AM/DCCH/UL-SCH

msgCrlcConfigReq

msgCmacPhyConfigReq (Setup)

msgCrlcConfigCnf

4) Rrc Connection Reconfiguration

SRB #1/RLC-AM/DCCH/DL-SCH

5) Rrc Connection Reconfiguration Complete


msgCrlcDatalnd

msgCrlcConfigReq

msgCrlcdataCnf

msgCpdcpDataTransferReq

msgCpdcpDataTransferCnf

msgCpdcpData Transferlnd

msgCrlcDatalnd msgCpdcpData Transferlnd

msgCmacPhyConfigCnf



Inter-eNB HO Call Admission Procedure

Figure 1.28 Inter-eNB HO CAC Procedure

1) The Inter-eNB Handover CAC is started when the Handover Request message is

received. The eNB capacity based CAC, and the QoS based CAC, are performed

referring to the E-RAB Level QoS parameter value contained in the Handover Request

message.

2) The call-based eNB Capacity based CAC is performed.

If „Current # of UEs of the eNB < MaxUeENB‟ is satisfied, the call is admitted.






UE PDCB ECCB

(RRC/S1AP/X2AP)

GTPB PHY/MAC/RLC

eNB

Source

Measurement Report

Handover Decision


3) QoS Based CAC

msgCpdcpConfigReq (Setup/Handover)

msgCmacPhyConfigReq (Setup/Handover)

5) Rrc Connection Reconfiguration


(Dedicated Preamble)

6) Rrc Connection Reconfiguration Complete

msgCrlcDatalnd

msgCsctpDataReq

msgCrlcConfigCnf

msgCgtpSetupReq (S1-U)

msgCpdcpData Transferlnd

SCTB

1) Handover Request msgCsctpDatalnd

msgCrlcConfigReq

msgCrlcConfigCnf

msgCmacPhyConfigCnf

msgCgtpSetupReq (X2-U/DL Forwarding)

msgCgtpSetupReq (X2-U/UL Forwarding/Optional)

msgCgtpSetupCnf (S1-U)

msgCgtpSetupCnf (X2-U/DL Forwarding)

msgCgtpSetupCnf (X2-U/UL Forwarding/Optional)

4) Handover Request

Acknowledge


SN Status Transfer




If „CurrentGbrBwUsage + ExpectedBw < MaxGbrBw‟ is satisfied for the backhaul

BW, the call is admitted. Otherwise, the call is rejected.


the target cell‟s PRB usage, the call is admitted. Otherwise, the call is rejected.

4) If the call is admitted, the handover request acknowledge message is sent to the system

to perform the Inter-eNB handover procedure. If the call is rejected, whether to admit

each E-RAB is determined in interoperation with the preemption function to control

the flow of the call. (Note that partial success of each E-RAB is not considered.)

5) The RRC connection reconfiguration message is sent to the UE.

6) RRC connection reconfiguration complete is received from the UE.

CAC-Related Setup Commands

You can use CAC setup commands by selecting a target on the CLI of the LSM and a

command in the „Command‟ tab, or by searching and selecting a command in the „Search‟

tab.

The table below lists the commands used for CAC-related setup.


RTRV-CELL-CAC Retrieves/changes the CAC parameters based on the callCount and

drbCount in the cell. CHG-CELL-CAC

RTRV-ENB-CAC Retrieves/changes the CAC parameters based on the callCount in the eNB.

CHG-ENB-CAC

RTRV-QCAC-PARA Retrieves/changes the CAC parameters based on the QoS in the cell.

CHG-QCAC-PARA



1.8 Overload Control

1.8.1 eNB Overload Control

The eNB overload control function measures the load of the main processor of the eNB, or

the PRB load per cell. If this is determined as an overload, the eNB Overload Control function

sends the UE the access barring control parameter value mapped to the matching overload

level to block call connection attempts, and thus control the overload status of the eNB.

The overload level evaluation algorithm for the main processor of the eNB is as follows.

The load and level of the processor are measured in the OAM and notified to the Call

Processing block.

The CPU load ratio is evaluated as Critical, Major, Minor, and Normal level in reference to

their respective thresholds. When the CPU load level is changed, the system overload level

is determined depending on that change, i.e. the increase, decrease, and persistence of the

current CPU load ratio.

If the load increases, it is reflected to the system overload level immediately.

If the load increases, it is reflected to the system overload level immediately to notify a

rapid inflow of load and reflect the current situation to call control, including

restriction of new calls, as soon as possible.

If the load decreases, or when a low load persists for a specified period of time, it is

reflected to the system overload level.

If the load decreases, one level is decreased at a time. (To keep the system stable)

To operate the system more stably, when the load decreases, the load level is decreased

only if the low load has persisted for a specified period of time.

The PRB load of the cell is measured in the MAC layer and notified to the Call Processing

block periodically.

The table below lists the access barring control parameters mapped to each overload level.

Category Load Level

Critical Major Minor Normal

ac-BarringForEmergency Barred Not barred Not barred Not barred

ac-BarringForMO-

Signalling

ac-BarringFactor

(Access probability)

0% 90% 95% -

ac-BarringTime

(Time for which access

is restricted)

128s 32s 16s -

ac-BarringForMO-

Data

ac-BarringFactor

(Access probability)

0% 70% 80% -

ac-BarringTime

(Time for which access

is restricted)

128s 32s 16s -



eNB Overload Control Operation Procedure

1) The overload level is notified from the OAM or MAC.

2) The access barring control parameter is configured as the SIB depending on the

overload level.

3) The SIB is sent to the UE.

Figure 1.29 eNB Overload Control Structure

eNB Overload Control Setup Commands

You can use eNB overload control setup commands by selecting a target on the CLI of the


the „Search‟ tab. The table below lists the commands used for eNB overload control-related

setup.

Command Description

RTRV-BAR-EMERG Retrieves/changes the emergency barring parameter value for each

overload status in the cell. CHG-BAR-EMERG

RTRV-BAR-DATA Retrieves/changes the data barring parameter value for each overload

status in the cell. CHG-BAR-DATA

RTRV-BAR-SIG Retrieves/changes the signal barring parameter value for each overload

status in the cell. CHG-BAR-SIG

eNB

RRM Function of eNB Overload

eNB overload Control

Measurement Control

Main processor load

PRB load

SIB (Access Barring Control)

UE



1.8.2 MME Overload Control

The MME overload control function is carried out to reduce the signaling traffic of the

MME in the overload status. The MME Overload Control function of the eNB is performed

when the MME sends the „OVERLOAD START‟ message via the S1 interface.

When it receives the „OVERLOAD START‟ message, the eNB stores the information

contained in it to the mmeDBInfo. When a new call occurs, the eNB performs overload

control for the MME by admitting or rejecting signaling traffic in compliance with the

MME overload status information, and the overload action information stored in the

mmeDBInfo of the MME.



Figure 1.30 MME Overload Control Message Procedure

OVERLOAD START

(OverloadAction)

PHY/MAC SCTB GTPB RLCB PDCB ERMB E (H)CCB

EPC

MME Overload Control

UE Source eNB

MME S/GW

RRC_IDLE

MME Overload

msgCsctpDatalnd




(Ueid=randomValue,

S-TMSI/establishmentCause)



Rrc Connection Reject





Rrc Connection Reqeust

(Ueid=randomValue,

S-TMSI/establishmentCause) SRB #0/RLC-TM/CCCH/DL-SCH


msgCpdcpConfigReq (SRB #1)


msgCcallConfigReq (SRB #1/Setup)

msgCpdcpConfigCnf

msgCrlcConfigCnf

msgCcallConfigCnf




Rrc Connection Setup Complete

(selectedPLMN_Index)



MME Overload




MME Overload Event

RRC Connection Reject




Procedure after Receiving the RRCConnectionRequest Message

Figure 1.31 Procedure After Receiving RRCConnectionRequest

1) After the „RRCConnectionRequest‟ message is received from the UE, whether the

s-TMSI (in InitialUE-Identity) exists is determined. If the s-TMSI value exists, step 2

is performed. Otherwise, step 3 is performed.

2) If the s-TMSI exists, the MME can be ascertained. Hence, whether to perform

overload control for the MME is determined using the overloadStatus value in the

mmeDBinfo of the MME.

If the MME is not in the overload status, step 4 is performed.

If the MME is in the overload status, call admission is determined by comparing the

overloadAction value in mmeDBinfo with the EstablismentCause value

(in RRCConnectionRequest). If the call is admitted, step 4 is performed. Otherwise,

step 5 is performed.

3) If the s-TMSI does not exist, and the randomValue exists, the overloadStatus value is

checked from all mmeDBInfo.

If all MMEs are in the overload status, whether to admit the call is determined by

comparing the overloadAction value of each MME with the EstablishentCause

value of the UE. If the call is admitted, step 4 is performed. Otherwise, step 5 is

performed.

4) „Success‟ is returned for the MME overload control.

5) „Fail‟ is returned for the MME overload control.

Search to all an „overloadStatus‟ in

mmeDBinfo[All]

„overloadStatus‟ in mmeDBinfo

[s-TMSI]

„s-TMSI or random Value‟ in Initial

UE-Identity

„overloadStatus == ON‟

In mmeDBinfo[All]

Not Accept

overloadStatus == OFF

YES

NO

Accpt

Receive „RRCConnectionRequest‟

Reject (RRCConnectionReject

With waitTime)

random Value

s-TMSI

Compare to between

„overloadAction‟ in mmeDBinfo and

„EstablishmentCause‟ in RRCConnection

Request

overloadStatus == ON

Accept



Procedure after Receiving the RRCConnectionSetupComplete Message

Figure 1.32 Procedure After Receiving RRCConnectionSetupComplete

1) After receiving the „RRCConnectionSetupComplete‟ message from the UE, the eNB

determines whether the „RegisteredMME‟ value exists. If the RegisteredMME value

exists, step 2 is performed. Otherwise, the MME Load Balancing function is carried out.

2) If RegisteredMME exists, it is compared with the MMEC of the s-TMSI which is in

mmeDBinfo of the UE. If the MMEC is the same, step 3 is performed. Otherwise, the

MME load balancing function is carried out.

3) If RegisteredMME exists in the mmeDBinfo of the eNB, step 4 is performed.

Otherwise, the MME load balancing function is carried out.

4) If RegisteredMME exists, whether to perform overload control is determined from the

overloadStatus value in mmeDBinfo of the MME.

Receive „RRCConnectionSetup

Complete‟

Accept

Compare to between MMEC in RRCConnection

SetupCom Plete and MMEC in CallInfo (s-TMSI)

Present

Not present

Accept

MME selection & Load balancing start

Not same

No

Compare to between „overloadAction‟ in mmeDBinfo and

„EstablishmentCause‟ in callInfo

Is exist RegisteredMME Iin

mmeDBinfo[]

„overloadStatus‟ in mmeDBinfo

[RegisteredMME]

Not Accept

Reject (RRCConnectionRelease

With releaseCause)

Update „numAllocUE‟ in mmeDBinfo[selectedMME]

Same

Yes

overloadStatus == OFF


„RegisteredMME‟ in RRCConnectionSetup

Complete



5) If the MME is not in the overload status, step 6 is performed.

If the MME is in the overload status, whether to admit the call is determined by

comparing the overloadAction value in mmeDBinfo with the EstablishmentCause

value in the RRCConnectionRequest message. If the call is admitted, step 6 is

performed. Otherwise, step 7 is performed.

6) The eNB increases the numAllocUe value in the mmeDBInfo and returns „Success‟ for

the MME overload control.

7) The eNB returns „Fail‟ for the MME overload control.



1.9 MME Selection Control

The MME selection control function consists of the eNB allocating an MME to a new call,

considering the load balancing of each MME. The eNB allocating an MME is performed

after the RRCConnectionSetupComplete message is received for a new call.

The eNB selects one MME from the MME pool, considering the load balancing of each

MME, and allocates the selected one to the new call.

The reference for evaluating load balancing is RelativeMMECapacity of each MME.

RelativeMMECapacity is sent to the eNB using the S1 SETUP RESPONSE and MME

CONFIGURATION UPDATE messages. Figure 1.33 shows the MME selection control

procedure and Figure 1.34 shows the MME selection control algorithm flow.

1Figure 1.33 MME Selection Control Procedure

UE

Source eNB

PHY/MA

C

SCTB GTPB RLCB PDCB ERMB E

(H)CCB

EPC

MME S/GW

Load Based MME Selection

RRC_IDLE

S1 Setup Request

S1 Setup


(Ueid=randomValue or S-TMSI) SRB #0/RLC-TM/CCCH/UL-SCH

msgCpdcpConfigReq (SRB

#1)

msgCcallConfigReq (SRB #1/Setup)

msgCpdcpConfigCnf

msgCcallConfigCnf



msgCrlcDatalnd Rrc Connection Setup Complete

(selectedPLMN_Index) SRB #1/RLC-AM/DCCH/UL-SCH

msgCpdcpDatalndTransferInd

Load Based MME

Selection

Initial UE Message

msgCsctpDataReq

S1 Setup Response

servedPLMNs_id, servedMMEGroups_id, servedMMECs_id RelativedMMECapacity

msgCsctpDatalnd






msgCsctpDataReq

msgCrlcConfigCnf



Figure 1.34 MME Selection Control Algorithm Execution Flow

selectedMMEs_ available > 0

„overloadStatus‟ in mmeDBinfo [s-TMSImme]

Select available MME (using Compare to

between „overloadAction‟ in

mmeDBinfo and „EstablishentCause‟ in

callInfo) in mmeDVinfo

[selectedMMEs_plmn]

Is „sTmsiMneOverSt

at == 1‟ ??


overloadStatus

== OFF

YES

NO

NO

YES

NO

YES

NO

YES

Accept

Update „numAllocUE‟ in mmeDBinfo

[selectedMME]

Select same PLMN ID in mmeDBinfo [ALL]

Is exist s-TMSImme in

selectedMMEs_ available?

YES

NO

YES YES

NO

YES

NO

NO

YES

Calculate Load balancing order using

„mmeLbPortion, mmeLbAllocUE‟ in

mmeDBInfo [selectedMMEs_available]

Calculate load balancing order using

„mmeLBportion, mmeLBallocUE' in

mmeDBInfo [selectedMMEs_

overStat]

MME selection & Load Balancing Start

Accept

Is exist MMEC (s-TMSI)

in mmeDBinfo

Is exist s-TMSI in callInfo

Is exist RegisteredMME

?

Is same mmec between

RegisteredMME and s-TMSI

Accept

„overloadStatus == ON‟ In all the mmeDBinfo

[selectedMMEs_plmn]

Select „overloadStatus == OFF‟ In mmeDBinfo [selectedMMEs_plmn]

Is exist MMEC (s-TMSI) in

mmeDBinfo[]

Update „numAllocUE‟ in mmeDBinfo

[selectedMME] Reject

(RRCConnectionRelease with releaseCause)

Select MME (high value in load balancing order)

Update „numAllocUE‟ in mmeDBinfo [selectedMME]

Accept

Set to „sTMSImMEoCERsTAT

=1‟



1) When the Relative MME Capacity IE is received using the S1 SETUP RESPONSE

and MME CONFIGURATION UPDATE messages, it is saved in the mmeLBportion

(= RelativeMMECapacity) parameter in the mmeDBInfo.

2) When the MME selection & load balancing procedure starts, If RegisteredMME exists,

step 3 is performed. Otherwise, step 4 is performed.

3) If RegisteredMME is identical to the MMEC of the s-TMSI, the following step is

performed. Otherwise, step 4 is performed. It is checked whether the MMEC owned

by the s-TMSI exists in the mmeDBInfo. If it exists, step 6 below is performed.

Otherwise, step 5 below is performed.

4) If s-TMSI exists in callInfo, the following step is performed. Otherwise, step 5 is

performed. It is checked whether the MMEC owned by the s-TMSI exists in the

mmeDBInfo.

If the MMEC exists, the overloadStatus of the corresponding MME(s) is checked in

the mmeDBInfo. If „overloadStatus == ON‟, the local variable

„sTmsiMmeOverStat‟ is set to 1 and then step 5 is performed. Otherwise, step 6 is

performed.

If MMEC does not exist, step 5 is performed.

5) The MME that has the selected PLMN ID is selected from the mmeDBInfo.

If all MMEs selected in step 5 are in the overload status, the available MMEs are

selected by comparing the overloadAction value of each MME with the

EstablishmentCause value of the UE. If there is no MME that can be admitted, step

7 is performed.

If the local variable „sTmsiMmeOverStat‟ is set to 1 and if the MMECs with s-TMSI

exist among the MMEs selected in step 5, step 6 is performed. Otherwise, the MME

with the highest mmeCapacityFactor value is allocated and then step 6 is performed.

[mmeCapacityFactor = mmeLbPortion/(1 + mmeLbAllocUE)]

When the local variable „sTmsiMmeOverStat‟ is not set to 1, the MME with the

highest mmeCapacityFactor value is allocated and then step 6 is performed.

If all MMEs selected in step 5 are not in the overload status, the MME which has

the highest mmeCapacityFactor value and whose overloadStatus is set to OFF in

mmeDBInfo is allocated, and then step 6 is performed.

6) The mmeLBallocUe value of the selected MME is increased or decreased, and then

„MME Selection & Load Balancing Success‟ is returned.

7) „MME Selection & Load Balancing Fail‟ is returned.



1.10 Call Trace Control

The Call Trace function allows the operator to check the detailed information for one or

more UEs more easily. The main purpose of the call trace function is to analyze dropped

calls. However, it is also used to solve a functional problem with UE, analyze resource

usage of UE, and provide quality optimization. The call traced targets specified as standard

are the protocol signaling messages. The trace activation methods are „Management Based

Trace Activation‟ and „Signaling Based Trace Activation‟. When a notification telling the

ECCB to start a trace is received from the OAM Trace Management (TRM) block of the

eNB or the MME, the ECCB starts it immediately. The information for all calls that are

traced is finally collected in the Trace Collection Entity (TCE) via the TRM. Below are

described the Management Based Trace function and the Signaling Based Trace function.

1.10.1 Management Based Trace

The management based trace (cell traffic trace) function performs tracing on calls which

are connected to a specific cell. When the EMS performs this trace on a specified cell using

the ACT-TRC-JOB command, the trace control and configuration parameters are relayed

via the TRM to the ECCB, and the ECCB starts tracing all calls for the cell.

For terminating trace, when the EMS uses the DEACT_TRC_JOB command for the cell

currently being traced, the command is notified via the TRM to the ECCB and the ECCB

stops tracing immediately. If the EMS does not stop the trace, the trace for each call is

stopped when the call is exited normally.



Management Based Trace Activation

Figure 1.35 Management Based Trace Activation (New Calls)

EMS

eNB

TRM ECCB

MME

Start Trace Session

Trace Session Activation

1) msgCellTrafficTraceDeactTrmEccb

(Trace Reference, InterfaceToTrace, Trace depth, TCE address included)

Save Trace Session Information

in cellInfo


Allocate Trace Recording

Session Start Trace

2) msgCellTrafficTraceSuccessEccbTrm

Allocate MME_UE_S1AP_ID

4) Downlink NAS Transport or Initial Context Setup Request

5) S1AP Cell Traffic Trace

Intial Context Setup Response

Call Setup 3) msgCallTraceEccbTrm

msgCallTraceEccbTrm

msgCallTraceEccbTrm

msgCallTraceEccbTrm

UE

Management Based Trace Activation (New Call)



Figure 1.36 Management Based Trace Activation (for a call for which call setup is proceeding)

EMS

Management Based Trace Activation (Calls Undergoing Call Setup)

UE

eNB

TRM ECCB

MME

Start Trace Session


1) msgCellTrafficTraceActTrmEccb

Save Trace Session Information

in cellInfo

RRC Connection Setup Complete

Allocate Trace Recording

Session

Start Trace

3) msgCallTraceEccbTrm

2) msgCellTrafficTraceSuccessEccbTrm

Allocate MME_UE_S1AP_ID

4) Downlink NAS Transport or Initial Context Setup Request

5) S1AP Cell Traffic Trace

Intial Context Setup Response

RRC Connection Setup

Trace Session Activation

msgCallTraceEccbTrm

msgCallTraceEccbTrm

msgCallTraceEccbTrm



Management Based Trace Activation Procedure

1) The cell to be traced is specified from the EMS using the ACT_TRC_JOB command

and the trace control and configuration information is relayed to the TRM.

2) The ECCB receives the msgCellTrafficTraceTrmEccb message from the TRM.

This message includes the CellID, Trace Session Reference, InterfaceToTrace, Trace

Depth, and TCE Address information within itself.

3) The ECCB allocates a trace recording session reference to each call of the cell, and

starts the trace. Then, for each new call, the trace is started when the RRC Connection

Request message is received for it. For each existing call, the trace is started

immediately when the msgCellTrafficTraceActTrmEccb message is received from the

TRM.

4) When sending or receiving a protocol message, the ECCB checks the InterfaceToTrace

(Uu, X2, S1-MME) value, and if it is a corresponding interface message, it sends the

msgCallTraceEccbTrm message to the TRM.

5) When receiving the first message (Downlink NAS Transport or Initial Context Setup

Request message) from the MME during call setup, the ECCB sends the Cell Traffic

Trace message to the MME to notify that the call belongs to the trace targets.



Management Based Trace Deactivation

Figure 1.37 Management Based Trace Deactivation

If the call is exited normally, and thus the ECCB sends the RRC Connection Release

message to the UE, the trace for that call is ended.

Tracing cam be stopped for a cell currently being traced at the EMS by using the DEACT-

TRC-JOB command. When the ECCB receives the msgCellTrafficTraceDeactTrmEccb

message from the TRM, tracing for all calls for the cell is stopped.

X2 UE Context Release

UE EMS

TRM

TeNB

S1 UE Context Release Command

Trace Session Deactivation

Normal Exit for the Call

SeNB

TRM ECCB

Exit Trace Recording Session

Management Based Trace (Deactivation)


MME

TRM


S1 UE Context Release Complete


msgCellTrafficTraceDeactTrmEccb

Normal Exit for X2 Handover

Normal Exit for S1 Handover

Force Exit on EMS

ECCB

Exit Trace Recoding Session for All Calls from the Cell



1.10.2 Signaling Based Trace

Tracing a specific call is only possible using the Signaling Based Trace function.

If the Trace Activation IE is contained in the Initial Context Setup Request message, or

Trace Start message received from the MME, the ECCB starts a trace for the call.

When X2 or S1 handover is performed, if the Trace Activation IE is contained in the

Handover Request message received from the source eNB or the MME, the ECCB starts a

trace for the call.

Signaling Based Trace Activation

Figure 1.38 Signaling Based Trace Activation

UE

X2 Handover Request

Call Setup

SeNB

TRM ECCB

Start Trace


MME


Allocate Trace Recording Session

TeNB

ECCB TRM


msgCallTraceEccbTrm

msgCallTraceEccbTrm

(Trace Activation IE included)

Start Trace


msgCallTraceEccbTrm

msgCallTraceEccbTrm

1) Initial Context Setup Request or Trace Start


1) S1 Handover Required S1 Handover Request

RRC Connection Reconfiguration Complete

Handover



1) When the target eNB receives the Initial Context Setup Request message or Trace Start

message from the MME, or receives the Handover Request message during X2 or S1

handover, if the Trace Activation IE is contained the received message, the ECCB

starts a trace for the call immediately.

2) When sending or receiving a protocol message, the ECCB checks the InterfaceToTrace

(Uu, X2, S1-MME) value, and if it is a corresponding interface message, it sends the

msgCallTraceEccbTrm message to the TRM.

Signaling Based Trace Deactivation

Figure 1.39 Signaling Based Trace Deactivation

UE

X2 Handover Request

Call Setup

SeNB

TRM ECCB

Start Trace



Allocate Trace Recording Session

TeNB

ECCB TRM

Handover


msgCallTraceEccbTrm

msgCallTraceEccbTrm


Start Trace


msgCallTraceEccbTrm

msgCallTraceEccbTrm

1) Initial Context Setup Request or Trace Start

(Trace Activation IE inlcuded)

S1 Handover Request 1) S1 Handover Required


MME

TRM



If the call is exited normally, and thus the ECCB sends the RRC Connection Release

message to the UE, the trace for that call is ended.

When the MME wants to stop a trace which is running for a call, the ECCB receives the

Deactivate Trace message from the MME and stops the trace for that call.

1.10.3 Trace Data Information

Cell traffic trace can be triggered using the Call Management Trace Management menu

of the LSM. The trace data the ECCB sends to the OAM TRM block is different depending

on the InterfaceToTrace and Trace Depth values. InterfaceToTrace (Uu, X2AP, S1-MME)

determines the the protocol message to be sent and trace depth (minimum, medium,

maximum) determines whether the protocol message to be sent should include decoded

data or encoded data.

Data Traced According to Interface and Trace Depth is as follows.

Interface Format Trace Depth

Description Min Med Max

RRC (excluding measurement

report message)

Decoded M M O Message name

M M X eNB ID (Global eNB ID)

M M X The specific IE in the RRC

message

Encoded X X M The raw data of the RRC

message

S1 Decoded M M O Message name

M M X eNB ID (Global eNB ID),

MME ID (GUMMEID)

M M X The specific IE in the S1 message

ASN.1 X X M The raw data of the S1 message

X2 Decoded M M O Message name

M M X Source eNB ID (Global eNB ID),

Target eNB ID (Global eNB ID)

M M X The specific IE in the X2 message

ASN.1 X X M The raw data of the X2 message

RRC (Measurement Report

message)

Decoded X M X The Measurement Result IE in

the Measurement Report

message

ASN.1 X X M The raw data of the RRC

message



(Continued)

Interface Data Name Message Name Description

Trace

Depth

Min Med

RRC

(Uu)

Cs fallback

indicator

MOBILITY FROM

EUTRA COMMAND

Whether a fallback to the

CS network is possible

M M

CN domain PAGING Identifies whether the

domain is the CS network or

PS network.

M M

S-TMSI PAGING S-TMSI information of the

UE (MME code, M-TMSI)

M M

Reestablishmen

tCause

RRC CONNECTION

REESTABLISHMENT

REQUEST

Cause of UE‟s re-

establishment

M M

Wait time RRC CONNECTION

REJECT

The period of time for which

the system waits until the

UE attempts a call again

M M

Release Cause RRC CONNECTION

RELEASE

The reason for which the

UE‟s connection has been

released

M M

Redirection

Information

RRC CONNECTION

RELEASE

The carrier frequency of the

RAT used by the UE during

cell reselection

M M

Establishment

Cause

RRC CONNECTION

REQUEST

The reason for which the

UE‟s connection has been

established

M M

Selected PLMN-

Identity

RRC CONNECTION

SETUP COMPLETE

UE selected

PLMN ID

M M

RegisteredMME RRC CONNECTION

SETUP COMPLETE

Information of the MME with

which the UE is registered

M M

Rat-Type UE CAPABILITY

INFORMATION

The RAT information of the

capabilities given by the UE

M M

Measured

Results

MEASUREMENT

REPORT

The results measured by the

terminal

X M

CDMA2000-

Type

HANDOVER

FROMEUTRA

PREPARATION

REQUEST

UL HANDOVER

PREPARATION

TRANSFER

UL INFORMATION

TRANSFER

CDMA2000Type information

(1xRTT, HRPD)

M M

Target RAT

Type

MOBILITY FROM

EUTRA COMMAND

The RAT information for the

target

M M



(Continued)


Trace

depth

Min Med

S1 E-RAB ID All messages containing

the ID

E-RAB ID M M

E-RAB Level

QoS

Parameters

E-RAB SETUP

REQUEST

E-RAB MODIFY

REQUEST

INITIAL CONTEXT SETUP

REQUEST

QoS for the E-RAB M M

Cause INITIAL CONTEXT SETUP

FAILURE

UE CONTEXT RELEASE

REQUEST

UE CONTEXT RELEASE

COMMAND

UE CONTEXT

MODIFICATIONFAILURE

HANDOVER REQUIRED

HANDOVER

PREPARATION

FAILURE

HANDOVER REQUEST

HANDOVER FAILURE

HANDOVER CANCEL

PATH SWITCH REQUEST

FAILURE

NAS NON DELIVERY

INDICATION

Cause for failure

of the message

M M

Handover

Type

HANDOVER REQUIRED

HANDOVER COMMAND

HANDOVER REQUEST

Handover type (IntraLTE,

LTEtoUTRAN...)

M M

E-UTRAN

CGI

HANDOVER NOTIFY

PATH SWITCH REQUEST

INITIAL UE MESSAGE

UPLINK NAS

TRANSPORT

Cell global ID of the eNB

(PLMN ID + cell ID)

M M

TAI HANDOVER NOTIFY

PATH SWITCH REQUEST

UPLINK NAS

TRANSPORT

Tracking area ID of the

eNB (PLMN ID + TAC)

M M

Target ID HANDOVER REQUIRED ID of the target RAT

which is the handover

target

M M

CDMA2000

HO Status

DOWNLINK S1 CDMA2000

TUNNELING

Whether the HO to the

CDMA2000 is successful

M M



(Continued)


Trace

depth

Min Med

S1 CDMA2000

RAT

Type

DOWNLINK S1 CDMA2000

TUNNELING

UPLINK S1 CDMA2000

TUNNELING

RAT information of the

CDMA2000 (1xRTT,

HRPD)

M M

CDMA2000

Sector ID

UPLINK S1 CDMA2000

TUNNELING

Sector ID of the

CDMA2000

M M

CDMA2000

HO Required

Indication

UPLINK S1 CDMA2000

TUNNELING

Whether the UE has to

prepare handover to

the CDMA2000

M M

X2 E-RAB id All messages where it is

present

The ID of the E-RAB M M

E-RAB Level

QoS

HANDOVER REQUEST QoS for the E-RAB M M

Cause HANDOVER REQUEST

HANDOVER

PREPARATION

FAILURE

HANDOVER CANCEL

Cause information of

each message

M M

Target Cell ID HANDOVER REQUEST Handover target‟s cell

ID

M M

GUMMEI HANDOVER REQUEST Handover target‟s

GUMMEID

M M

UE History

Information

HANDOVER REQUEST History of the UE M M

Regardless of the InterfaceToTrace and Trace Depth values, the vendor-specific

information added to the message that is sent to the TRM. Besides them, the TRM General

Trace Data required to create XML data in the TRM is also added to the message that is

sent to the TRM.



Vendor-Specific Trace Data is as follows.

Data Name Description

callId The ID of the call

stateCmd The stateCmd information for the ECCB

state The internal state information for the ECCB

enbUeS1APId The ID of the UE allocated by the ECCB to send the S1AP message

mmeUeS1APId The ID of the UE allocated by the MME to send the S1AP message

servCellnum The No. of the cell to which the call belongs

mmeId The ID of the MME to which the call belongs (GUMMEI)

TRM General Trace Data is as follows.

Data Name Description

callStartTime The time (hour/minute/second) at which the call has been connected

traceID Trace ID

(Trace Session Reference, Trace Recording Session Reference)

tCEAddr The address of the trace collection entity

venderSepecific The information for determining whether the message is vendor-specific

or not

traceEnbId ID of the eNB that performs the trace

traceDepth Trace depth

Interface The interface and protocol information for the message

The following commands are related to trace activation and deactivation.


START-TRC Registers the signaling trace for all active calls in the designated cell.

Only one cell for each eNB can be specified. To run a trace in the cell

2 while the cell 1 is running a trace, you must first delete the trace from

the cell 1 then register a new trace in the cell 2. Once a trace is

registered, it cannot be modified. To modify, you must delete the existing

trace (STOP-TRC) and register a new one. This command can also be

executed in the following procedure:

1) Select Performance at the top of the main screen.

2) Select Call Trace.

3) Select the target eNB.

4) Select Register, then enter the parameters.

STOP-TRC Deletes each cell‟s registered trace. It stops the signaling trace data

collection for the active call in the designated cell. This command can

also be executed in the following procedure:

1) Select Performance at the top of the main screen.

2) Select Call Trace.


4) Select Delete.



1.11 CSL

The call summary log (CSL) data is collected by the ECCB, which is the call processing

block of the eNB, and reported to the TRM, which is the OAM block, at the end of the call.

When a given amount of CSL data is accumulated in the memory or when a given amount

of buffering time (RTRV-CSL-INFO) elapses, the TRM sends the data to the TrueCall

Server/LSM. When the LSM receives the corresponding data, it stores the raw data to the

/log/csl directory; the data can be displayed through the LSM‟s call history window.

Figure 1.40 CSL Data Flow

The CSL data includes various information for a call. It includes a total of 10 information

items: call information, common item information, connection information, release

information, handover information, throughput information, RF information, adjacency

information, UE history information, and call debugging information.

1.11.1 CSL Data

CAL Data Items is as follows.

CSL Data Item Data Name Description

Call Information cslEvent The information for the CSL event

- 0: RRC Release

- 1: Outgoing Handover

sTmsi The STMSI information for the call

This consists of the 1-byte mmeCode information and the

4-byte mTmsi value.

mmeUeS1APId The S1AP ID of the call allocated by the MME

enbUeS1APId The S1AP ID of the call allocated by the eNB

ECCB TRM msgCslDataNoti

EMS

EMS App.

eNB

M e m o r y



(Continued)


Common Item

Information

mmeId This global unique compatible MME ID consists of reserved

(1 byte) + PLMN ID (3 bytes) + MME group (2 bytes) +

MME code (1 byte).

tai The tracking area ID which consists of PLMN ID (3 bytes) +

TAC (1 byte)

enbId The eNBID to create the CSL consists of reserved (1 byte)

+ PLMN ID (3 bytes) + enbType (4 bytes) + eNBid (4 bytes).

enbType: 0 (Macro enb), 1 (Home enb)

enbName The eNB that created the CSL. Max 20 bytes

callReleaseCause The reason for call failure

Connection

Information

attemptYear The year/month/day on which the call is connected

attemptMon

attemptMday

attemptHour The time at which the call is connected

(hour/minute/second) attemptMin

attemptSec

attemptMillisec

setupHour The time at which the DRB was established

(hour/minute/second) setupMin

setupSec

setupMillisec

freqBandIndicator The bandclass when the target call is released

(e.g. 1.5 G or 800 M, etc.)

cgi The cell ID when the target call is connected

(CGI: Cell Global ID)

reserved (1 byte), PLMN ID (3 bytes) + Cell ID (28 bits)

pci The cell ID when the target call is connected

(PCI: Physical Cell ID)

mmeIpAddr The information for the upper equipment communicated

when the call is connected (ID and IP address, etc.) sGateIpAddr

TA The round-trip delay time (distance) between the UE and

eNB when the call is connected

cardId The resource information for the channel card accessed

when the target call is connected

transmitMode The transmission antenna mode when the call is connected

callType Identifies the type of the call, such as origination,

termination, or handover call.



(Continued)


Connection

Information

mmeIpAddr The information for MME‟s upper equipment communicated

when the call is connected (ID and IP address, etc.）

sGateIpAddr The information for S-GW communicated when the call is

connected (ID and IP address, etc.)

reserved reserved

reserved1 reserved

Release

Information

Release

Information

year The year/month/day on which the call is released

month

mday

hour The time at which the call is released (hour/minute/second)

min

sec

millisec

pci The cell ID when the target call is released

(PCI: Physical Cell ID)

cgi The cell ID when the target call is released


freqBandIndicator The bandclass when the target call is released

(e.g. 1.5G or 800 M, etc.)

cqi The CQI reported by the UE before the call is released

TA Round-trip delay time (distance) between the UE and eNB

when the call is released

cardId The card information for the node accessed when the

target call is released

pA The downlink power control parameter PA when the call is

released

transmitMode Transmission antenna mode when the call is released

mmeIpAddr The information for the upper equipment communicated

when the call is connected (ID and IP address, etc.) sGateIpAddr

reserved reserved

Handover

Information

enbId The eNBID of the target eNB when handover is performed.

This consists of PLMN ID (3 bytes) + enbType (4 bytes) +

eNBid (4 bytes).

enbType: 0 (Macro enb), 1 (Home enb)

enbIpAddr The IP address of the target eNB when handover is performed

cgi The cell ID of the target cell when handover is performed


PLMN ID (3 bytes) + Cell ID (28 bits).

pci The physical cell ID of the target cell when handover is

performed (PCI: Physical Cell ID)



(Continued)


Throughput

Information

rbId RB ID

epsbearerId E-RAB ID

txDataToSG The total bytes of data sent to the upper node during the

time between connection and release

qci QoS class identifier

rxDataFromSG The total bytes of data received from the upper node during

the time between connection and release

txDataToUE The total bytes of data sent to the UE during the time

between connection and release

reTxDataToUE The total bytes of data resent to the UE during the time

between connection and release

rxDataFromUE The total bytes of data received from the UE during the

time between connection and release

RF Information txPower The power sent from the eNB

ueTxPower The power sent from the UE

rsrp Reference signal received power

rsrq Reference signal received quality

Adjacency

Information

cgi The cell ID of the cell with the highest PSRP among the

adjacent cells reported by the UE (CGI: Cell Global ID)

PLMN ID (3 bytes) + Cell ID (28 bits)

pci The physical cell ID of the cell which has the highest RSRP

of the adjacent cells reported by the UE

rsrp RSRP of the adjacent cell ID #1

rsrq RSRQ of the adjacent cell ID #1

UE History

Information

cgi The cell global ID of the cell to which the UE belonged

PLMN ID (3 bytes) + Cell ID (28 bits)

cellSize The size of the cell to which the UE belonged

stayTime The time for which the UE belongs to the cell

Call Debugging

Information

stateCmd The state which changes according to the message

received externally

callState The ECCB state which changes according to the message

received internally and externally

msgId The ID of the message with which the call failure occurred

cslsequenceNum The sequence number of the CSL generated

callId Call ID

Imsi ID used to distinguish UE in CN

(IMSI: International Mobile Subscriber Identity)

C-RNTI ID used to distinguish UE in the cell



1.12 S1 AP Related Control

1.12.1 S1 Setup

The S1 Setup procedure is the first S1AP procedure after a TNL association has been made.

When this procedure is performed, the application level configuration data that has existed

between the eNB and MME are erased, and replaced with the newly received data.

The S1Setup message includes Supported TAs, CSGIdList, DRX, eNBName, etc.

The S1 Setup procedure ends after the eNB receives the S1SetupResponse message from

the MME and stores the information such as MME name, served GUMMEI and relative

MME capability to the internal database.

If the eNB receives the S1SetupFailure message, it waits for the Time to Wait value

contained in that failure message, and then attempts the S1Setup procedure again.

If the Time to Wait value is not included, it waits for the value of internalNoWaitRetry

Timer defined in the PLD and then runs the S1 Setup procedure again.

If the eNB fails to receive the S1SetupFailure or S1SetupResponse message and a timeout

occurs, the eNB attempts the S1Setup procedure again until S1 setup is made.

Figure 1.41 S1 Setup Procedure

S1SetupRequest (Timer Activated)

eNB MME

S1SetupResponse



Figure 1.42 S1 Setup Unsuccessful Operation (Timeout)

Figure 1.43 S1 Setup Failure Operation (Failure)

TimeOut

TimeOut


eNB MME

Cannot receive S1SetupResponse

Resend S1SetupRequest

Cannot receive S1SetupResponse


TimeToWait

TimeToWait


eNB MME

S1SetupFailure (TimeToWait)


S1SetupFailure (TimeToWait)




1.12.2 S1 Reset

The eNB has to perform the reset procedure in the following three cases:

When the Reset message is received from the MME

When the msgCeccbCellReleaseInd message is received from the ECMB block

When a specific block is down and the Reset Req message is received from the ECMB

When Receiving the Reset Message from the MME

Figure 1.44 S1 Reset Reception Procedure

1) When receiving the Reset message from the MME, the ECCB sends the Reset

Acknowledge message to the MME immediately.

2) The matched calls are searched and listed using the MME_UE_S1AP_ID, or ENB_

UE_S1AP_ID, contained in the Reset message.

3) The RRC Connection Release message is sent to all of the calls (UEs) listed.

4) The msgCmacPhyCallDeleteReq, msgCrlcCallDeleteReq, msgCpdcpCallDeleteReq

and msgCgtpCallDeleteReq messages are sent to the MACB, RLCB, PDCB, and

GTPB blocks to release the internal resources.

5) When the msgCmacPhyCallDeleteCnf, msgCrlcCallDeleteCnf,

msgCpdcpCallDeleteCnf, and msgCgtpCallDeleteCnf messages are received by the

MACB, RLCB, PDCB, and GTPB blocks, the Reset procedure is ended.

Reset

1) Reset Acknowledge

3) RRC Connection Release

msgCgtpCallDeleteReq

msgCgtpCallDeleteCnf

UE

eNB

PHY/MA

C

SCTB GTPB RLCB PDCB ECMB ECCB

EPC

MME S/GW

S1 Reset

2) Calls to be reset are

listed up

4) msgCmacPhyCallDeleteReq

msgCrlcCallDeleteReq

msgCpdcpCallDel

eteReq

5) msgCmacPhyCallDeleteCnf

msgCrlcCallDeleteCnf

msgCpdcpCallDeleteCnf



When Receiving the msgCeccbCellReleaseInd Message from the ECMB

Figure 1.45 MsgCeccbCellReleaseInd Reception Procedure

1) The ECCB receives the msgCeccbCellReleaselnd message from the ECMB.

2) The calls to be reset are determined within the ECCB and listed up.

3) The ECCB sends the reset message to the MME and receives the reset acknowledge

message.

4) The msgCpdcpCallDeleteReq and msgCgtpCallDeleteReq messages

are sent to the respective blocks for releasing internal resources.

5) When the msgCpdcpCallDeleteCnf and msgCgtpCallDeleteCnf messages are received

from the respective blocks, the reset procedure is complete.

Reset

1) Reset Acknowledge

3) RRC Connection Release

msgCgtpCallDeleteReq

msgCgtpCallDeleteCnf

UE

eNB

PHY/MA

C

SCTB GTPB RLCB PDCB ECMB ECCB

EPC

MME S/GW

S1 Reset

2) Calls to be reset are

listed up

4) msgCmacPhyCallDeleteReq

msgCrlcCallDeleteReq

msgCpdcpCallDeleteReq

5) msgCmacPhyCallDeleteCnf

msgCrlcCallDeleteCnf

msgCpdcpCallDeleteCnf



When Receiving the Reset Request Message from the ECMB

When loading is finished, the ECCB performs the Initialization procedure, and sends the

Alive Indication message to the ECMB block. When it receives the Reset Request message

from the ECMB, the ECCB performs the Initialization procedure for all resources, and

sends the Reset CNF message to the ECMB. The detailed ECCB operation is as follows.

Figure 1.46 ECCB Operation Procedure When Receiving the Reset Request Message

1) When the ECCB receives the Reset Request message, if ECCB ProcessID is received,

this message is notified after the ECCB block is restarted and alive indication is sent to

the ECMB. Therefore, after sending the Reset CNF message, the ECCB ignores this

message and ends the procedure.

2) When receiving the reset request message, if ECCB ProcessID is found, the reset CNF

message is send to the ECMB. Since the reset procedure for internal blocks is

performed by the ECMB, the ECCB performs the ECCB internal reset procedure for

call resource reconciliation between the MME and other eNBs.

3) Since no message will be sent to the internal blocks, the corresponding flags are set to

OFF and the corresponding calls are listed to perform the Reset procedure with the

MME, or the other eNB taking part in handover.

4) All calls listed are released using the S1 Reset message, or X2 Reset Request message,

and then the Common Reset procedure is performed.

5) Common reset is performed.

Receive

„Reset Request‟

Send „Reset CNF‟

to ECMB

ProcessID ==

ECCB

Message Ignore

END

Send Reset to

MME Send Reset

Request to TeNB

Flag off internal

blocks; list the

calls to be reset

Common Reset

Procedure

END

NO

YES



1.12.3 S1 eNB Configuration Update

When the eNB wants to update the application level data that has an effect to the UE-

related context, the eNB can send the eNB Configuration Update message to the MME

with which the eNB has an established S1 connection currently.

If the current TAC, CSGID, eNBName, or DefaultPagingDRX value set in the PLD is

changed during system operation, the eNB includes not only the changed parameter values

but also the unchanged parameter values in the eNB Configuration Update message, and

sends it to the MMEs. At this time, the eNB must send the message to all MMEs with S1

Setup established. When the eNB Configuration Update message is sent, a timer starts.

The eNB expects an eNB Configuration Update Acknowledge message to be received

before the timer expires. If the eNB configuration update acknowledge message is not

received before the timer expires, the eNB kills the timer, resends the eNB configuration

update message, and restarts the timer.

The eNB retransmits the eNB configuration update message when the eNB configuration

update failure message is received or the timer expires. This retransmission count can be

changed using the CHG-TIMER-INF command. The default is 3 times.

Figure 1.47 S1 NB eNB Configuration Update Procedure

Figure 1.48 S1 eNB Configuration Update Timeout

eNB Configuration Update (Timer Activated)

eNB MME

eNB Configuration Update Acknowledge

eNB MME

Resend eNB Configuration Update

Cannot receive eNB Configuration Update

Ack

Resend eNB Configuration Update

TimeOut

TimeOut

Cannot receive eNB Configuration Update Ack




Figure 1.49 S1 eNB Configuration Update Failure

The commands related to S1 AP Related Control are as follows.


CHG-MME-CONF Changes the MME related parameter information. It can change the

MME‟s Equip information, the active state information on whether to use

the S1, the MME IP and the secondary MME IP information.

CHG-CELL-IDLE Changes the EUTRAN cell information within the base station.

CHG-PCCH-CONF Changes the configuration information for the Paging Control Channel

(PCCH) within the base station. The paging is used to initiate a mobile

terminating connection, to trigger the UE to re-acquire the system

information, or to send an Earthquake and Tsunami Warning System


CHG-CAS-IDLE Changes the CSG cell ID value. It is broadcasted to the terminal through

the System Information Block (SIB) 1.

eNB MME

Resend eNB Configuration Update TimeToWait

Resend eNB Configuration Update TimeToWait

eNB Configuration Update Failure (TimeToWait)


eNB Configuration Update Failure (TimeToWait)



1.13 X2 AP Related Control

1.13.1 X2 AP Setup

This function is used when the X2 interface is set up between two eNBs for the first time.

The following figure shows the X2 AP setup procedure.

Figure 1.50 X2 AP Setup Procedure 1

1) eNB #1 sends its global eNB ID, served cell information, neighbor information, and

GU group ID list information to eNB #2 using the X2 Setup Request message.

2) eNB #2 receives the X2 Setup Request message and stores the information contained

in it in appropriate locations. Then eNB #2 sends its global eNB ID, served cell

information, neighbor information, and GU group ID list information to eNB #1 using

the X2 Setup Response message.

Figure 1.51 X2 AP Reset Procedure 2

1) eNB #1 receives the X2 setup failure message from eNB #2.

2) eNB #1 waits as long as Time To Wait as included in the X2 setup failure message and

then resends the X2 setup request message to eNB #2.

1) X2 Setup Request

eNB #1 eNB #2

2) X2 Setup Response

1) X2 Setup Request

eNB #1 eNB #2

2) X2 Setup Failure

X2 Setup Request

TimeToW

ait



1.13.2 X2 AP Reset

If an abnormal failure occurs with the X2 interface between two interacting eNBs, this

function reconciles the resources between the two eNBs.

The following figure shows the X2 AP reset procedure.


1) eNB #1 sends the X2 Reset Request message to eNB #2.

2) eNB #2 sends the X2 Reset Response message to eNB #1. If there are any procedures

which eNB #1 is carrying out via the X2 Interface, eNB #2 stops all of them and

performs the Call Release procedure for the call.


1) When receiving the msgCeccbCellReleaseInd message from the ECMB, the ECCB of

eNB #1 lists the reset target calls.

2) eNB #1 sends the X2 Reset Request message to every eNB #2 which owns a target call.

3) eNB #2 sends the X2 Reset Response message to eNB #1, and then performs the Call

Release procedure for the call.

1) X2 Reset Request

eNB #1 eNB #2

2) X2 Reset Response

2) X2 Reset Request

3) X2 Reset Response

eNB #2

ECMB

ECCB

eNB #1

ECMB

ECCB

1) msgCeccbCellReleaselnd



1.13.3 X2 AP eNB Configuration update

This function is used when application level data needs to be updated between two eNBs

interacting over the X2 interface. (Application level data includes served cell information,

neighbor information, GU group ID list, etc.)

If the eNB recognizes the PLD has been changed in the LSM, it checks whether the

changed PLD requires an update of the application level data. If necessary, it performs the

X2 AP eNB Configuration Update procedure.

The figure below shows the X2 AP eNB Configuration Update procedure.

Figure 1.54 X2 AP eNB Configuration Update Procedure 1

1) When eNB #1 recognizes the application level data has been changed and needs to be

updated, it sends the X2AP eNB Configuration Update Acknowledge message to eNB #2.

2) When it receives the X2AP eNB Configuration Update message, eNB #2 stores the

related information in the DB and then sends the X2AP eNB Configuration Update

Acknowledge message to eNB #1.

Figure 1.55 X2 AP eNB Configuration Update Procedure 2

1) eNB #1 receives the X2AP eNB configuration update failure message.

2) After waiting for Time to Wait included in the message received, it resends the X2AP

eNB configuration update message.

1) X2AP eNB Configuration Update

eNB #1 eNB #2

X2AP eNB Configuration Update

TimeToWait

2) X2AP eNB Configuration Update Failure

1) X2AP eNB Configuration Update

eNB #1 eNB #2

2) X2AP eNB Configuration Update Acknowledge



The commands related to X2 AP Related Control are as follows.



CHG-NBR-EUTRA Changes the information of the E-UTRAN neighbor cell located near the

base station. It receives the CELL_NUM and RELATION_IDX parameter

values and modifies the E-UTRAN neighbor cell information.



1.14 Preemption Control

The preemption function is performed when call admission fails during the E-RAB setup

procedure (QoS CAC fail, backhaul CAC fail). It is controlled according to the Allocation

and Retention Priority (ARP) parameters of the E-RAB Level QoS parameters.

The ARP parameters are sent to the eNB using the Initial Context Setup Request, E-RAB

Setup Request, E-RAB Modify Request, or Handover Request message and consist of

Priority Level, Pre-emption Capability, and Pre-emption Vulnerability.

The Priority Level parameter is set to up to 15 steps for the E-RAB. The Preemption

Capability parameter denotes the preemption capability of the E-RAB used to establish a

bearer. The Preemption Vulnerability parameter denotes the preemption capabilities of

other E-RABs.

1) The eNB receives the Initial Context Setup Request, E-RAB setup/Modify Request,

and Handover Request message messages.

2) If the call admission control result is „Failure‟, the Preemption function is carried out.

3) It is checked whether the Preemption Capability parameter of the ARP parameters of

the E-RAB is set to „may trigger preemption‟.

4) From the active E-RABs of the cell for which the E-RAB is to be set up, one E-RAB is

located where the Preemption Vulnerability parameter is set „preemptable‟ and the

Priority Level parameter value is lowest.

5) If two or more of the E-RABs have the same priority level, the one with the longest

E-RAB setup time (stay time) is selected and its resources are released.

6) The Setup/Modify procedure is performed for the E-RAB to be set up.



Figure 1.56 Pre-emption Control Procedure



Priority level 0~15

(0: error, 1: the highest priority, 15: no priority)

Preemption

Capability

Apply to the allocation of resources for an E-RAB

(Shall not trigger pre-emption, May trigger pre-emption)

Preemption

Vulnerability

Apply for the entire duration of the E-RAB

(Not preemptable, Preemptable)

Yes

Yes

Else

No

No

Preemption target

Preemption target selection

Preemption Control

Among the active calls of the

cell, search for ERAB with lower

priority level than of the ERAB

ARP and with preemption

vulnerability set to preemptable

Perform Bearer Setup

Send Failure/Response

Perform Bearer Release

The preemption target is the E-RAB

whose ARP has the lowest priority

level and the longest stay time.

Is the ERAB‟s Preemption Capability „may trigger

preemption‟?



CHAPTER 2. Configuration

The configuration information for the system is managed using Program Load Data (PLD).

PLD is the data defined to perform a specific function and is a group of tables which

consist of pairs of keys and values. All the PLD required for eNB system operation is

stored and managed in the shared memory of the target board and is shared by all software

entities.

The configuration-related commands allow the operator to add, delete, restrict, allow, or

retrieve cell configuration within the eNB. In addition, functions are provided for the

operator to retrieve or change the current operation parameter values required to perform

the inherent functions of the system and the current call processing parameter values for

call services.

The major configuration functions are as follows:

Resource Grow/Degrow Functions

Resource Service Control Functions

Parameter Control Functions

Parameter Display Functions

2.1 Resource Grow/Degrow

The operator can operate the system flexibly using the system grow and degrow functions.

The resource grow function is to add or delete a cell which is the component of the

resource managed by the CM block of the LTE eNB. Growing occurs when a cell is added

to the eNB; degrowing occurs when a cell is deleted from the eNB. The cell is the target

component for the resource addition and/or deletion.

Cell Grow/Degrow

During the cell grow, the Administrative State is set to Lock. The state of the cell is EQUIP,

but the service is not available. The service will become available after modifying the

additional required parameters, changing the Administrative State to UnLock, and then

setting up the cell.

A cell can be degrown after its administrative state is set to Lock.

Changing the Administrative State to Lock will immediately clear all calls currently in

service.



Changing the Administrative State to ShuttingDown will reject all new calls, wait until all

of the existing calls are disconnected, and then change the Administrative State to Lock.

State Description

Cell Grow A cell is grown when the Administrative State is set to Lock and the sector state is

set to EQUIP. The board that supports the cell is loaded, and the cell is ready to

provide the service. Since the RF output is turned off, it cannot provide service to

the EPC.

To provide service, the Administrative State should be changed to Unlock.

Cell Degrow To degrow a cell, the Administrative State should be changed to Lock or

ShuttingDown. When the Administrative State is changed to Lock, all call services

are stopped immediately so that the degrow can be performed. In the

ShuttingDown state, new services are not accepted; the state is changed to Lock

when all of the existing call services end to allow the cell degrow to be processed.

The following shows the cell state transition process.

Figure 2.1 Cell State Transition Diagram

N_EQUIP

act deact

EQUIP



2.2 Resource Service Control

If a system resource needs to be restricted from use because it has a problem or needs to be

removed, the resource service control functions are used. By using these functions, the

operator can make the system provide services more stably. In the ShuttingDown state, the

system waits until the calls allocated to specific resources are released, but prevents new

calls from being allocated to them. In Lock state, the calls allocated to the specific resource

are force terminated and allocation of new calls is restricted. In Lock state, the calls

allocated to the specific resource are force terminated and allocation of new calls is

restricted.

Controlling Cell Resource

Cell resource restriction and release is done using Lock/Unlock of the administrator.

2.3 Parameter Control

The parameter control functions allow the operator to change the current system control

parameter values and the current call processing parameter values used in the eNB system.

When changing the parameters, the CM block transmits the change notification message to

the LSM. The parameter-related modification commands used in the eNB system are

categorized as below according to their functions.

External Link Configuration Parameter

Manages the board external link information.

Command Description

CHG-ELINK-CONF Changes the configuration information of the external link required for

communications outside the system. It is used for growing or degrading

a port by specifying unit type, unit ID, and port ID and modifying the port

status.

As a measure to prevent communication disruption, the last link cannot

be degrown or locked.

General Management Function Parameter

Manages the general configuration information.

Command Description

CHG-NTP-CONF Changes the NTP server IP address.



RRH Equipment Parameter

Manages the RRH information within the eNB.

Command Description

CHG-RRH-CONF Changes the RRH grow/degrow and configuration information.

The operator can enter values for the CONNECT_BOARD_ID, CONNECT_

PORT_ID, and CASCADE_RRH_ID parameters for selecting an RRH to be

changed. After connecting the RRH to the DU, the operator can execute

the command to set the STATUS parameter to EQUIP so that the RRH is

grown and is ready to be controlled by the system. On the contrary, the

STATUS parameter can be set to N_EQUIP in order to degrow the RRH.

In order to manage the PSU connected to the RRH from the system, the

operator can execute the command to set the PSU_STATUS parameter to

EQUIP and grow the PSU.

On the contrary, PSU_STATUS can be set to N_EQUIP for degrowing the

PSU. The operator may specify an RRH name for USER_LABEL.

The operator can set latitude, longitude, or height. The operator can set

downlink antenna azimuth for DL_ANT_AZIMUTH. The operator can set Tx

and Rx attenuation values for each path for TX_ATTEN and RX_ATTEN.

The operator can set RRH Tx and Rx delay values for TX_DELAY and

RX_DELAY.

The operator can set VSWR alarm, OVER PWR alarm, and LOW PWR

alarm thresholds for VSWR_SHUT_ALARM_TH, OVER_PWR_ALARM_TH,

and LOW_PWR_ALARM_TH.

The operator can set FA information for each path by turning TX_PATH_A,

TX_PATH_B, TX_PATH_C, TX_PATH_D, RX_PATH_A, RX_PATH_B,

RX_PATH_C, and RX_PATH_D on/off.



eNB Function Parameter

Manages configuration information within the eNB.

Command Description

CHG-HO-OPT Changes the handover-related information. It can change the E-RAB

interaction method configured for the eNB, the neighbor cell list (NCL)

inclusion status, or the uplink data forwarding status at the target eNB.

CHG-TIMER-INF This command changes the timer values used by the ECCB within the base

station. It can change the timer value used for message transmission/

reception with the UE when a call is setup; the timer value used for message

transmission/reception with the MME; the timer value used for message

transmission/reception with the neighbor eNB; or the timer value used by

other ECCBs.

CHG-CSL-CTRL Changes the CSL control information within the base station.

It can change the criteria used by the base station for generating the CSL.

CHG-BAR-DATA Changes the access barring data parameter information according to the

CPU status within the base station. It changes the access barring data

parameter sent to the SIB 2 according to the CPU overload status.

When the UE issues service request, it controls cell access according to the

access barring data parameter value.

CHG-BAR-

EMERG

Changes the access barring emergency parameter information according to

the CPU status within the base station.

It changes the access barring emergency parameter sent to the SIB

2 according to the CPU overload status. When the UE issues emergency call

request, it controls cell access according to the access barring emergency

parameter value.

CHG-BAR-SIG Changes the access barring signaling parameter information according to the

CPU status within the base station.

It changes the access barring signaling parameter sent to the SIB 2 according

to the CPU overload status. When the UE issues attach, it controls cell

access according to the access barring signaling parameter value.

CHG-BLACK-LIST Changes the blacklist cell information for each cell within the base station.

It changes the blacklist information registered for the cell specified by Cell

Num according to the black List Idx value entered.

CRTE-BLACK-

LIST

Creates the blacklist cell information for each cell within the base station.

It displays the blacklist cell information for each cell within the base station

and the relevant information is relayed to the UE during the basic call procedure.

DLT-BLACK-LIST Deletes the blacklist cell information for each cell within the base station.

It deletes the information specified by the Cell Num and Black List Index

parameter values entered.

CHG-CELL-ACS Changes the cell access information within the base station.

It is broadcasted to the UE via SIB 1.

CHG-CELL-RSEL Changes the cell reselection information within the base station.




(Continued)

Command Description

CHG-CELL-SEL Changes the cell selection information within the base station.


CHG-CSGPCI-

IDLE

Changes the Closed Subscriber Group (CSG) related PCI of the cell.

If the cell‟s cell type is set to CSG, the PCI value or the PCI range of the CSG

is included in the SIB and sent.

Also, if the cell type is set to Macro, SIB inclusion is determined by usage.

CHG-SIB-INF Changes the interval for the SIB of the cell. SIBs 2 through 11 are sent as

system information (SI) messages, and the SIB v.s. SI message mapping

information for SIBs 2 through 11 is included in SchedulingInfoList of SIB 1.

Each SIB is included in one SI message, and the SIBs of the same interval

are mapped to the same SI message. There can also be multiple SI

messages sent at the same interval. SIB 2 is always mapped to the first SI

message on the SI message list of the scheduling info list.

CHG-MOBIL-STA Changes the mobility state. The CELL_NUM parameter input value is used to

change the mobility state. It changes Speed State ReSel Pars Usage, T

Evaluation, T Hyst Normal, N Cell Change Medium, or N CellChange High.

CHG-TIME-INF Changes the UE timer constant information within the base station.

It consists of the UE-Timers And Constants information broadcast to SIB2

and the UE-specific timer information.

The timer values broadcasted to SIB include t300, t301, t310, n310, and

n311 values, and the other values are UE-specific timer values included in

the RRC message.

CHG-CDMA-CNF Changes the CDMA2000 related information included in the SIB. It changes

CDMA EUTRA Synchronization, search Window Size, and CSFB Support

Dual Rx UE which are used for configuring CDMA2000 related SIB.

CHG-HRPD-BCLS Changes the CDMA2000 HRPD band class information within the base

station. CDMA 2000 HRPD can have up to 32 band classes; this command

changes priority and related information for reselecting each band class.

CHG-HRPD-OVL Changes the HRPD cell information overlaid for the specific cell within the

base station. Each cell can have 1 HRPD cell; the command modifies the ID

of the cell or the sector ID.

CHG-HRPD-

PREG

Changes the CDMA2000 HRPD pre-registration information. It uses the

CELL_NUM parameter input value to change the relevant CDAM2000 HRPD

pre-registration information.

CHG-C1XRTT-

BCLS

Changes the CDMA2000 1XRTT bandclass information.

It uses the BC_INDEX parameter input value to change the relevant

CDAM2000 1XRTT bandclass information.

CHG-C1XRTT-

OVL

Changes the CDMA2000 1XRTT overlay information within the base station.

This modifies the parameter required for reselection to a CDMA2000 1XRTT

cell in an environment where EUTRAN cells and CDMA2000 1XRTT cells

are overlaid together.



(Continued)

Command Description

CHG-C1XRTT-

MOBIL

Changes the CDMA2000 1XRTT mobility information. It uses the

CELL_NUM parameter input value to change the relevant CDMA2000

1XRTT mobility parameter information. It can change the values used in the

pre-registration process for CDMA2000 1XRTT interoperation.

CHG-C1XRTT-

ACBAR

Changes the AC barring information for CDMA 1xRTT.

The modified parameters are broadcast to SIB 8 via the EU.

CHG-GERAN-

RESEL

Changes the GERAN reselect information within the base station. It includes

the timer required for reselection to a GERAN cell, usage status of scaling

factor, and timer for each scaling factor. This command is included in the SIB

and sent to the UE.

CHG-SIB-IDLE Changes the max size of the packed SI which can be sent by the cell.

Change can be made only when the cell is in idle state.

CHG-CELL-CAC Changes the CAC parameter information for each active cell within the base

station. The CAC at the cell level can perform backhaul-based CAC, call

count-based CAC, DRB count-based CAC, or QoS-based CAC. It changes

the threshold for performing CAC at the cell level, CAC option and

preemption status.

CHG-ENB-CAC Changes the capacity based CAC parameter information for each active eNB

within the base station. The CAC performed at the base station level is call

count based CAC. It changes the threshold for performing CAC at the base

station level and the max call count information.

CHG-QCAC-PARA Changes the active quality of service (QoS) CAC parameter information

within the base station. QoS CAC is performed at the cell level, for QCI of

each GBR bearer. Retrieves the threshold for each QCI for performing QoS

CAC and modifies the threshold for determining the congestion status of

active cells.

CHG-BHBW-QCI Changes the parameter information required for backhaul CAC for each

active QoS Class Identifier (QCI) within the base station.

Backhaul-based CAC is performed on GBR bearers by QCI or service group.

This command changes the threshold for performing backhaul based CAC

by QCI.

CHG-BHBW-

SVCGR

Changes the parameter information for backhaul CAC by each active service

group within the base station. Backhaul-based CAC is performed on GBR

bearers by QCI or service group. Changes the threshold for performing

backhaul based CAC by service group.

CHG-SRB-QCI This command changes the signaling bearer identity (SRB ID) related

information. It changes resource type, which determines whether the SRB

type is Guaranteed Bit Rate (GBR) or Non-Guaranteed Bit Rate (NGBR),

priority, packet delay budget, and packet error loss rate of the SRB.

CHG-SRB-RLC Changes the parameter information required for RLC protocol operation.

It can change AMD PDU retransmission count, poll byte and poll PDU

settings for poll triggering, poll resend timer, loss detection timer setting, and

STATUS_PDU prohibit timer value for each SRB ID.



(Continued)

Command Description

CHG-QCIDSCP-

MAP

Changes the differentiated services code point (DSCP) mapping information

for each QCI.

CHG-DSCPCOS-

MAP

Changes the COS mapping information for each differentiated services code

point (DSCP). The COS values mapped to the DSCP values are marked with

VLAN TAG.

CHG-BHCGT-

PARA

Changes the backhaul congestion monitoring settings.

It changes the backhaul congestion monitoring usage status, the threshold

for determining backhaul congestion, rate adjustment value and monitoring

interval. A change made is applied to the backhaul port and queue as well.

CHG-BHCGT-

QUE

Changes the backhaul port and queue settings on which backhaul

congestion is monitored. Each backhaul port has up to 8 queues; each

queue status can be set to enable/disable.

CHG-QCI-VAL Changes the configuration parameter information for each QoS class

identifier (QCI) used by the Evolved Universal Terrestrial Radio Access

Network (EUTRAN) within the base station. It can change the status,

resource type, priority, Packet Delay Budget (PDB), Packet Error Loss Rate

(PLER), and backhaul service group parameter information for each QCI.

CHG-LOCH-INF Changes the parameter information required for logical channel operation.

It can change bucket the size duration, logical channel group ID, logical

channel priority, non-GBRPF weight, and prioritized bit rate for each QCI.

CHG-RLC-INF Changes the parameter information required for RLC protocol operation.

It can change the RLC mode, AMD PDU retransmission count at the base

station and at the UE, poll byte and poll PDU settings for poll triggering, poll

retransmission timer, loss detection timer setting, and STATUS_PDU prohibit

timer value for each QCI.

CHG-PDCP-INF Changes the PDCP information. Changes that can be made to PDCP

information include UM SN size, discard timer, and forward end timer for

each of the 256 QoS classes. Changes are applied to new calls and have no

effect on existing calls.

CHG-GTP-INF Changes the GTP information. It changes keep alive usage status, timeout

interval, and sequence number usage status of the GTP. If keep alive is

enabled, the GTP ECHO-REQ message sent to the S-GW at a specified

interval (T3_TIMER_LONG). If the GTP ECHO-RESP message is not

received from the S-GW before the next message transmission, the

message is resent by the number of times specified by N3_REQUEST at the

interval of T3_TIMER.

CHG-PCCH-

CONF

Changes the paging control channel (PCCH) configuration information within

the base station. Paging is performed when initiating a mobile terminating

connection, when triggering the UE to reload the system information, or

when sending Earthquake and Tsunami Warning System (ETWS) indication

to the UE.



(Continued)

Command Description

CHG-PDSCH-IDLE Changes the physical downlink shared channel (PDSCH) configuration

information within the base station.

It can change the power ratio of the resource element (RE) which transmits

the reference signal and the RE which transmits the data over the PDSCH.

CHG-PHICH-IDLE Changes the Physical Hybrid ARQ Indicator Channel (PHICH) configuration


It can change the information related to PHICH duration and resource.

CHG-PRACH-CONF Changes the Physical Random Access Channel (PRACH) configuration


It can change high speed flag, PRACH configuration index, root sequence

index, and zero correlation zone configuration information.

CHG-PUSCH-CONF Changes the Physical Uplink Shared Channel (PUSCH) configuration


It can change 64QAM reception availability status and hopping related

information of the base station.

CHG-RACH-CONF Changes the Random Access Channel (RACH) configuration information

within the base station.

It can change the backoff indicator, Msg3 HARQ send count, non-

dedicated/dedicated preamble count, power ramping step and max send

count, and preamble group A and B count information.

CHG-TIME-ALIGN Changes the time alignment configuration information of the UE.

Unless the time alignment timer value is infinity, the UE receives the timing

advance command within the timer value to determine that the uplink

timing is valid. Otherwise, the UE releases the PUCCH and SRS

resources.

CHG-SNDRS-CONF Changes the UL sounding reference signal configuration information within

the base station. It can change ACK/NACK, simultaneous transmission

support for SR and SRS, SRS usage status in the cell, and the SRS max

up PTS value.

CHG-PWR-PARA Changes the parameter information of uplink power control within the base

station. It can change the alpha value used in PUSCH power control,

settings related to difference in transmission power by PUCCH format,

p0_nominal_PUCCH and p0_nominal_PUSCH settings, and UL IOT target

value.

CHG-BCCH-CONF Changes the Broadcast Control Channel (BCCH) configuration information


It can change the modification Period Coeff value which determines the

modification interval of the system information.

CHG-PUSCH-IDLE Changes the Physical Uplink Shared Channel (PUSCH) configuration


It can change the n (1)_DMRS value used to determine the cyclic shift

value of the PUSCH reference signal.



(Continued)

Command Description

CHG-RACH-IDLE Changes the random access channel (RACH) configuration information


CHG-CLOCK-CTRL Changes the parameter information required for clock advance/retard

setting of the modem/DSP. The base station‟s DU signal send/receive

time changes according to the value entered for clock advance/retard.

If the clock advance/retard value increases when the RU settings remain

constant, the UE‟s UL timing advance value decreases.

CHG-CQI-REP Changes the parameter information required for CQI reporting operation.

It can set whether only wideband CQI is operated or wideband CQI and

subband CQI are operated simultaneously for each DL transmission

mode.

CHG-DPHY-PUSCH Changes the parameter information required for dedicated PUSCH

operation. When the UCI must be sent on the uplink in the same

subframe as the PUSCH, it can modify the beta Offset ACK, beta Offset

CQI, and beta Offset RI which determine how much resources should be

used by the UCI in the PUSCH.

CHG-DPHY-SPS Changes the parameter information required for dedicated Semi Persist

Scheduling (SPS) operation. It can change the UL power related settings

and two-interval SPS pattern usage status for SPS operation.

CHG-DPHY-SR Changes the parameter information required for dedicated Scheduling

Request (SR) operation. It can change the maximum scheduling request

send count for the UE.

CHG-ULPWR-CTRL Changes the parameter information required for dedicated uplink power

control operation. It can change the p0 value for PUSCH/PUCCH by UE,

usage status of accumulation mode of the TPC, power offset of the SRS

with the PUSCH, and the L3 filtering coefficient used by the UE for

pathloss calculation.

CHG-DPHY-ULSRS Changes the parameter information required for dedicated uplink

sounding RS operation. It can change hopping bandwidth of the SRS and

send duration of the SRS.

CHG-DRX-INF Changes the parameter information required for DRX operation.

It can change DRX usage status, long DRX cycle, short DRX usage status

and cycle information.

CHG-DL-SCHED Changes the downlink scheduling configuration information for the MAC

layer within the base station. It can change fairness, channel quality, and

priority-related scheduler settings (alpha, beta, and gamma).

CHG-UL-SCHED Changes the uplink scheduling configuration information for the MAC

layer within the base station. It can change fairness, channel quality, and


CHG-TRCH-BSR Changes the parameter information required for transport channel BSR

operation. It can change BSR-related timer values.



(Continued)

Command Description

CHG-TRCH-INF Changes the parameter information required for transport channel

operation. It can change the max UL HARQ retransmission count, TTI

bundling usage status and band, PHR send interval, and the pathloss

change value.

CHG-EUTRA-FA Changes the parameter information required for EUTRA FA priority

information operation. It uses the Cell Num and FA Index parameter

values to change the EUTRA FA information registered with a specific cell


CHG-MEAS-INF It changes the data and collection status (enable/disable) of the statistics

items defined in Measurement Job.

CHG-MSGAP-INF Changes the measurement gap information configured for each cell within

the base station. It uses the DB Index parameter input value to change

the gap pattern information for the DB‟s inter FA, inter RAT, and ANR.

CHG-UTRA-FA Changes the UTRA FA priority information. It uses the Cell Num and fa

Index parameter values to change the UTRAN FA information registered

with a specific cell within the base station.

CHG-C1XRTT-FREQ Changes the CDMA2000 1xRTT carrier information. It uses the Cell Num

and carrier Index parameter values to change the CDMA2000 1XRTT

carrier information registered with a specific cell within the base station.

CHG-HRPD-FREQ Changes the CDMA2000 HRPD carrier information. It uses the Cell Num

and carrier Index parameter values to change the CDMA2000 HRPD

carrier information registered with a specific cell within the base station.

CHG-EUTRA-A1CNF Changes the EUTRA A1 criteria information. It uses the CELL_NUM and

PURPOSE parameter values to change the EUTRAN A1 event report

registered with a specific E-UTRAN served cell.

CHG-EUTRA-A2CNF Changes the EUTRA A2 criteria information.

It uses the CELL_NUM and PURPOSE parameter values to change the

EUTRAN A2 event report registered with a specific E-UTRAN served cell.

CHG-EUTRA-A3CNF Changes the EUTRA A3 criteria information. It uses the CELL_NUM and



CHG-EUTRA-A4CNF Changes the EUTRA A4 criteria information.


EUTRAN A4 event report registered with a specific E-UTRAN served cell.

CHG-EUTRA-A5CNF Changes the EUTRA A5 criteria information.It uses the CELL_NUM and



CHG-EUTRA-PRD Changes the EUTRA periodic criteria information.


EUTRAN periodic report registered with a specific E-UTRAN served cell.



(Continued)

Command Description

CHG-UTRA-B1CNF Changes the UTRA B1 criteria information.


UTRAN B1 event report registered with a specific E-UTRAN served cell.

CHG-UTRA-B2CNF Changes the UTRA B2 criteria information.


UTRAN B2 event report registered with a specific E-UTRAN served cell.

CHG-UTRA-PRD Changes the UTRA periodic criteria information.


UTRAN periodic report registered with a specific E-UTRAN served cell.

CHG-C1XRTT-

B1CNF

Changes the CDMA2000 1xRTT B1 criteria information.


CDMA 1XRTT B1 event report registered with a specific E-UTRAN served

cell.

CHG-C1XRTT-

B2CNF

Changes the CDMA2000 1xRTT B2 criteria information.


CDMA 1XRTT B2 event report registered with a specific E-UTRAN served

cell.

CHG-C1XRTT-PRD Changes the CDMA2000 1xRTT periodic criteria information. It uses the

CELL_NUM and PURPOSE parameter values to change the CDMA

HRPD periodic report registered with a specific E-UTRAN served cell.

CHG-HRPD-B1CNF Changes the CDMA2000 HRPD B1 criteria information.


CDMA HRPD B1 event report registered with a specific E-UTRAN served

cell.

CHG-HRPD-B2CNF Changes the CDMA2000 HRPD B2 criteria information.


CDMA HRPD B2 event report registered with a specific E-UTRAN served

cell.

CHG-HRPD-PRD Changes the CDMA2000 HRPD B1 periodic criteria information. It uses the

Cell Num and purpose input parameter values to change max report cell

and report interval information of the specified periodic report.

CHG-QUANT-

EUTRA

Changes the quantity settings for EUTRA measurement.

It uses the Cell Num input parameter value to change the EUTRAN-

related measurement quantity information registered with a specific cell.

CHG-QUANT-UTRA Changes the quantity settings for UTRA FDD/TDD measurement. It uses

the Cell Num input parameter value to change the UTRAN-related

measurement quantity information registered with a specific cell.

CHG-QUANT-CDMA Changes the quantity settings for CDMA2000 measurement. It uses the

Cell Num input parameter value to change the CDMA-related

measurement quantity information registered with a specific cell.



(Continued)

Command Description

CHG-GERAN-

B1CNF

Changes the GERAN B1 event report information. It uses the CELL_NUM

and PURPOSE parameter values to change the GERAN B1 event report

information.

CRTE-GERAN-

B1CNF

Creates the GERAN B1 event report information. It uses the CELL_NUM

and PURPOSE parameter values to create the GERAN B1 event report

information. Any parameters not entered are set to the default values.

DLT-GERAN-B1CNF Deletes the GERAN B1 event report information. It uses the CELL_NUM

and PURPOSE parameter values to delete the GERAN B1 event report

information.

CHG-GERAN-

B2CNF



information.

CRTE-GERAN-

B2CNF

Creates the GERAN B2 event report information. It uses the CELL_NUM

and PURPOSE parameter values to create the GERAN B2 event report

information. Any parameters not entered are set to the default values.

DLT-GERAN-B2CNF Deletes the GERAN B2 event report information. It uses the CELL_NUM

and PURPOSE parameter values to delete the GERAN B2 event report

information.

CHG-GERAN-FA Changes the GERAN FA object information. It uses the CELL_NUM and

FA_INDEX parameter values to change the GERAN FA object

information.

CHG-GERAN-PRD Changes the GERAN periodic event report information.


GERAN periodic event report information.

CRTE-GERAN-PRD Creates the GERAN periodic event report information.

It uses the CELL_NUM and PURPOSE parameter values to create the


Any parameters not entered are set to the default values.

DLT-GERAN-PRD Deletes the GERAN periodic event report information.

It uses the CELL_NUM and PURPOSE parameter values to delete the


CHG-UTRA-RESEL Changes the UTRAN FA reselect information. It uses the CELL_NUM

parameter input value to change the UTRAN FA reselect information

registered with the E-UTRAN Served Cell.

CHG-EPRAT-REL Changes the relation with the specified inter RAT for each cell within the

base station. It uses the CELL_NUM parameter input value to change the

inter RAT relation information with the specified cell. It can change the

status which indicates validity of the current PLD, the associated RAT

type, and the relation IDX which assigns DB Index of the Inter RAT

Neighbor Cell.



(Continued)

Command Description

CRTE-EPRAT-REL Creates the relation with the specified inter RAT for each cell within the

base station. It uses the CELL_NUM parameter input value to create the

inter RAT relation information with the specified cell.

DLT-EPRAT-REL Deletes the relation with the specified inter RAT for each cell within the

base station. It uses the CELL_NUM parameter input value to delete the

inter RAT relation information with the specified cell.

CHG-GERAN-

B1CNF



information.

CHG-ROHC-INF Changes the parameter information of the RObust Header Compression

(ROHC) protocol. It specifies the ROHC operation status and support

profile types for each QoS class.

CHG-SECU-INF Changes the preferred integrity and ciphering algorithms for the base

station. It uses the DB Index parameter input value to change the

preferred integrity protection algorithm and ciphering algorithm.

CHG-NBR-GERAN Changes the GERAN neighboring cell information near the base station.

It uses the CELL_NUM and RELATION_IDX parameter values to change

the GERAN neighboring cell information.

CRTE-NBR-GERAN Creates the GERAN neighboring cell information near the base station.

It uses the CELL_NUM and RELATION_IDX parameter values to create

the GERAN neighboring cell information. Any parameters not entered are

set to the default values.

DLT-NBR-GERAN Deletes the GERAN neighboring cell information near the base station.

It uses the CELL_NUM and RELATION_IDX parameter values to delete


CHG-SCTP-PARA Changes the SCTP-related parameters.

CHG-NBR-ENB Changes the Neighbor eNB information required for Neighbor eNB

operation. It uses the NBR_ENB_INDEX parameter input value to change

the Neighbor eNB information.

CRTE-NBR-ENB Creates the Neighbor eNB information required for the neighbor eNB

operation. It uses the NBR_ENB_INDEX parameter input value to create

the neighbor eNB information. Any parameters not entered are set to the

default values.

DLT-NBR-ENB Deletes the neighbor eNB information near the base station required for

neighbor eNB operation. It uses the NBR_ENB_INDEX parameter input

value to delete the Neighbor eNB information.

CHG-NBR-EUTRAN Changes the E-UTRAN neighboring cell information near the base station.


the E-UTRAN neighboring cell information.



(Continued)

Command Description

CRTE-NBR-EUTRAN Creates the GERAN neighboring cell information near the base station.


the GERAN neighboring cell information. Any parameters not entered are


DLT-NBR-EUTRAN Deletes the GERAN neighboring cell information near the base station.



CHG-NBR-UTRAN Changes the UTRAN neighboring cell information near the base station.


the UTRAN neighboring cell information.

CRTE-NBR-UTRAN Creates the UTRAN neighboring cell information near the base station.


the UTRAN neighboring cell information. Any parameters not entered are


DLT- NBR-UTRAN Deletes the UTRAN neighboring cell information near the base station.


the UTRAN neighboring cell information.

CHG-NBR-C1XRTT Changes the CDMA2000 1XRTT neighboring cell information near the

base station. It uses the CELL_NUM and RELATION_IDX parameter

values to change the CDMA2000 1XRTT neighboring cell information.

The information modified includes the status indicating validity of the PLD,

and the SID, NID, and base ID which indicate the cell identity of the

specified CDMA2000 1XRTT neighbor cell. Band class, ARFCN, and PN

offset (physical Cell ID) of the CDMA2000 1XRTT neighbor cell can also

be changed.

CRTE-NBR-C1XRTT Creates the CDMA2000 1XRTT neighboring cell information near the


values to create the CDMA2000 1XRTT neighboring cell information.


DLT-NBR-C1XRTT Deletes the CDMA2000 1XRTT neighboring cell information near the base

station. It uses the CELL_NUM and RELATION_IDX parameter values to

delete the CDMA2000 1XRTT neighboring cell information.

CHG-NBR-HRPD Changes the CDMA2000 HRPD neighboring cell information near the


values to change the CDMA2000 HRPD neighboring cell information.

The information modified includes the status indicating validity of the PLD,

and the color code, BSM ID, BSC ID, DPSS ID, and sector ID which

indicate the cell identity of the specified CDMA2000 HRPD neighbor cell.

Band class, ARFCN, and PN offset (physical cell ID) of the CDMA2000

HRPD neighbor cell can also be modified.



(Continued)

Command Description

CRTE-NBR-HRPD Creates the CDMA2000 HRPD neighboring cell information near the base


create the CDMA2000 HRPD neighboring cell information.


DLT-NBR-HRPD Deletes the CDMA2000 HRPD neighboring cell information near the base


delete the CDMA2000 HRPD neighboring cell information.

CHG-MME-CONF Changes the MME-related parameter information.

It can change the equip information of the MME, the active state indicating

whether to use S1, the MME IP address, and the secondary MME IP

address.

CHG-ENB-INF Changes the basic information of the base station. Since the information

other than the backhaul capacity is entered when growing the base

station, it cannot be changed while the base station is running.

CHG-POS-CONF It changes the settings required to provide location services.


CHG-C1XRTT-PREG Changes the CDMA2000 1xRTT CSFB-Pre-Registration criteria

information within the base station. It is used when the EUTRA cell

requires CS registration or pre-registration towards CDMA2000 1XRTT.

CHG-CAS-IDLE Changes the CSG cell ID value. It is broadcasted to the UE via SIB 1.

CHG-HYBRIDPCI-

IDLE

Changes the hybrid cell related PCI of the cell.

If the cell type is set to hybrid cell, it modifies the PCI value or PCI range

of the hybrid cell.

CHG-OPENPCI-IDLE Changes the open cell related PCI of the cell.

If the cell type is set to open cell, it modifies the PCI value or PCI range of

the open cell.

CHG-PAT-MAP Changes the static port address translation (PAT) setting information.

It can change mapping information for the IP/UDP port of the monitoring

server which retrieves the information of the supplementary equipment

and the IP/UDP port of the supplementary equipment.

CHG-PAT-INF Changes the static port address translation (PAT) setting information.

It can change the IP/UDP port mapping information for the backhaul port

and the UDE port of the eNB.

CHG-SRS-IDLE Changes the parameters required for sounding reference signal resource

(SRS) allocation in the specified cell within the base station.

SRS resource allocation is performed for each UE.

For TDD, a different subframe location is used for each SRS allocation

type.

CHG-DPHY-RLF Changes the dedicated PHY RLF information.

It can change parameter information used for determining RLF.

CHG-MEAS-FUNC Changes the measurement information configured for each cell within the

base station. It uses the Cell Num parameter input value to change the

Meas Config information of the specified cell.



SON Function Parameter

These commands are used for controlling the Self Optimizing Network (SON) parameter

information.

Command Description

CHG-SON-DLICIC Changes the SON DL ICIC function.

CHG-SON-ULICIC Changes the SON UL ICIC function.

CHG-ES-COM Changes the ES mode common parameter information of the SON energy

saving function. The parameter of this command can be modified when the

energy saving function is set to Auto Apply by executing the CHG-SONFN-

CELL command. Traffic estimation for selecting ES mode involves the

following two methods. The first method is calculation with the average

value of the traffic load statistics for the specified time during the last 15 or

30 days as determined by the DATA_VALIDITY parameter. The second

method is calculation with weight-adjusted value of the MOVING_

AVERAGE_WEIGHT parameter value for the last 2, 3, 4, 5, or 10 hours as

determined by the MOVING_AVERAGE_VALIDITY parameter.

The maximum value of these two methods is selected for determining the

active ES mode. Energy saving guarantees operation performance by

monitoring the abnormal traffic state and the abnormal system state on an

hourly basis.

Abnormal traffic state means that the traffic exhibits sudden unusual

changes or that huge differences exist between the traffic estimation and the

actual traffic load measurement and therefore traffic estimation performance

is questioned (estimation hit ratio is lower than the CORRELATION_

COEFFICIENT_THRESHOLD parameter value).

In this case, energy saving is stopped and the system enters the ES normal

mode. Abnormal system state means that the system is in abnormal state

according to the eNB monitoring function. It is determined by the RE_TX_

THRESHOLD parameter and the BLER_THRESHOLD parameter.

In this case, energy saving is stopped immediately and the system enters

the ES normal mode.



(Continued)

Command Description

CHG-ES-SCHED Changes the schedule information of the SON energy saving function.

The parameter of this command is used to change the schedule information

of the pre-defined time based energy saving function which becomes active

when the energy saving function is set to Manual Apply using the CHG-

SONFN-CELL command. The system operator can use the LSM to

schedule the energy saving function of the eNB. The Energy Saving Manual

Apply function executes the PA bias voltage change command every hour

according to the set schedule.

The activation time, activation status, ES voltage mode, and the RB type to

restrict can be specified. Energy saving by schedule can be set on an hourly

basis; the schedule is checked hourly for determining the operation.

If ES_MODE_VOLTAGE_TYPE is the same for the previous hour and the

current hour, the operation for the previous hour remains for the current hour

as well. The ES_STATE parameter can be used for determining SUSPEND

or ACTIVE. Also, to stop the currently active ES mode, ES_STATE which is

ACTIVE for the current hour is modified to SUSPEND.

The ES_MODE_VOLTAGE_TYPE and ES_MODE_RB_TYPE parameters

determine the voltage mode which should be active and the RB type which

should be restricted for the specified hour. Therefore, these two parameters

should be paired properly in order to guarantee performance.

In other words, if ES_MODE_VOLTAGE_TYPE is ES Mode1_Voltage, ES_

MODE_RB_TYPE should also be set to ES Mode1_RB.



(Continued)

Command Description

CHG-SON-ANR Changes the parameter information of the SON ANR function.

This command can make modifications when the ANR function is set to

Manual Apply or Auto Apply by the CHG-SONFN-CELL command. By default,

the ANR function of the LTE-SON is supported by the User Equipment (UE) or

the LSM for obtaining the neighbor identity information including ECGI/TAC/

PLMN for automatic addition of an NR. The NR ranking function is performed

by considering the handover key performance index (KPI: HO attempt/failure

rate, etc.) for each neighboring cell obtained over the X2 interface. The ranking

is used as the reference for selecting an NR from the existing NRs to add to

the handover blacklist in order to add an NR for the new adjacent cell when

the system is running at the maximum NRT size. In other words, if a new NR is

added while the maximum NRT is full, the lowest ranking NR is added to the

blacklist. For determining the ranking, the DEFAULT_WEIGHT, HO_

ATTEMPT_WEIGHT, and HO_SUCCESS_WEIGHT parameter values can be

used for assigning weights to the new NR, HO attempt rate, and HO success

rate.

The HO blacklist function identifies invalid adjacent cells from the HO

performance viewpoint and adds them to the HO blacklist in order to prevent

unnecessary handover to invalid adjacent cells and ultimately to improve the

HO KPI. The criteria for inclusion in the HO blacklist are either that the NR

does not satisfy the HO KPI or that the HO attempt to wrong cells increases by

a certain rate. The first condition is set using the LOWER_HO_ATTEMPT_

RATE and LOWER_HO_ SUCCESS_TO_KPI parameters, while the second is

set using the UPPER_HO_TO_WRONG_RATE parameter. On the contrary, if

the HO attempt to the NR on the blacklist increases by a certain rate, it

escapes the blacklist. The escape condition is set using the UPPER_HO_TO_

BLACK_RATE parameter.

CHG-SON-MRO Changes the SON MRO control parameters.

CHG-SON-SO Changes the parameter information related to SON self optimization.

The parameters retrieved and their functions are as follows.

- RRH optic delay compensation: Measures an optic delay value per RRH

when the initial RRH setup and optic delay changes occur, and then

calculates the Tx/Rx time buffers modified by the expression. The time buffer

value obtained is sent to the respective RRH for RRH delay compensation.

The TX_TBMAX and RX_TBMAX values retrieved by this command are

required in the time buffer calculation process.

- Related command: The RRH optic delay compensation operation is

determined by the DELAY_COMPENSATION_

ENABLE parameter value of the CHG-SONFN-ENB command. If the value is

SON FuncOff, compensation is disabled. If the value is SON AutoApply,

compensation is enabled.

The TX_TBMAX and RX_TBMAX parameters can be retrieved using the

RTRV-SON-SO command.



(Continued)

Command Description

CHG-SONFN-CELL Changes the SON function cell control flag. This command is used for

setting the SON function controlled for each cell to three options of Function

Off, Manual Apply, and Auto Apply or to two options except for Manual

Apply. The SON ANR function automatically compiles the Neighbor Relation

Table (NRT) and detects any changes in the operation environment for

maintaining optimal NRT. In other words, the eNB uses the ANR function to

update the NRT by automatically detecting topological changes such as

addition and removal of neighbor eNBs and by adding or removing new

neighboring cells. The Energy Saving (ES) function reduces the operation

cost of the system by reducing the eNB‟s energy (power) consumption.

In other words, it flexibly adjusts the system capacity in response to the

actual traffic demand with the goal of reducing the energy consumption.

CHG-SONFN-ENB Changes the SON function eNB control flag. This command is used for

setting the SON function controlled for each eNB to three options of

Function Off, Manual Apply, and Auto Apply or to two options except for

Manual Apply. The SON PCID function automatically allocates PCI to the

cells belonging to the new eNB during the self-establishment procedure of

the newly added eNB and automatically detects PCI collision/confusion with

neighboring cells during system operation.

During the initial RRH installation or when the optic delay value is changed,

the SON delay compensation function is measured the optic delay value of

each RRH and calculates the modified Tx time buffer and Rx time buffer

values. The time buffer value obtained is sent to the respective RRH for

RRH delay compensation.

CHG-SON-BLBO Changes the parameter information required for Blaking Load Balancing

Optimization (BLBO). It changes the neighboring cell‟s load calculation

interval, BLBO state monitoring interval, the load value for starting BLBO,

the load value for stopping BLBO, the load value used as reference for

overload, and the margin value of the load calculation. This command is

significant if SONFN-CELL: lankingLoadBalancingEnable: = 1 (Automatic

Apply).

CHG-SON-RO Changes the parameter information required for RACH Optimization (RO).

It changes the period for collecting RACH data related statistics required for

RO operation, minimum and maximum values of the parameters modified

by RO, the parameters related to the number of dedicated preamble

optimization function, and the parameter information related to the RACH

Tx power optimization function and the PRACH configuration index

optimization function.

This command is significant if SONFN-CELL: rachOptEnable: = 1 (Manual

Apply) or 2 (Automatic Apply).



2.4 Retrieving Parameters

The parameter retrieval functions allow the operator to change the current system control

parameter values and the current call processing parameter values used in the system.

This function displays the values set in the PLD within the main processor of the current

eNB. The parameter retrieval commands used in the eNB are categorized as below

according to their functions.

Managed Element Parameter

Retrieves the basic NE system parameters.

Command Description

RTRV-SYS-CONF Retrieves the system configuration information. It includes the system ID,

status (EQUIP/N_EQUIP), administrative state (locked, shutting down,

unlocked), and the type of grown eNB. The operator can retrieve the

system version, the system location by latitude, longitude and altitude, and

the type of the board connected to the RU.

Physical Resource Holder Parameter

Retrieves the board unit information.

Command Description

RTRV-UNIT-CONF Retrieves the type, ID, mounting status in the PLD, board type, and

mounting location for each unit of the system.

External Link Configuration Parameter

Retrieves the board external link information.

Command Description

RTRV-ELINK-CONF Retrieves the external link settings. If PORT_ID is not specified, settings for

all external links are retrieved.

It can retrieve the link‟s EQUIP/LOCK state, MEDIA type, MTU, SPEED,

DUPLEX, and FLOW CONTROL settings.



General Management Function Parameter

Retrieves the general configuration information.

Command Description

RTRV-DB-VER Retrieves the version information of the PLD database in the system.

This includes the database schema version and the database data version.

It also shows the time of the last database update. The database schema

version is the same as the software version, and the database data version

increments by 1 each time the database is updated.

RTRV-NTP-CONF Retrieves the IP address of the NTP server.

RRH, Port Equipment Parameter

Retrieves the RRH, RU and port information within the eNB.

Command Description

RTRV-ECPPT-

CONF

Retrieves the port configuration information of the channel card (board) by

channel card and port. If a board ID or port ID is not entered, the

configuration information for all ports is retrieved.

If a board ID is entered but not a port ID, the configuration information for

all ports within the board ID entered is retrieved.

RTRV-RRH-CONF Retrieves the configuration information of RRH which is a remote RF unit.

This information can be retrieved by entering the board ID, port ID, or

cascade ID connected to the RRH according to the RRH ID scheme.

If a board ID is entered but not a port ID and a cascade ID, the

configuration information for all RRHs in the board ID is displayed.

If a board ID and a port ID are entered but not a cascade ID, the

configuration information for all RRHs in the board ID and port ID is

displayed. The operator can retrieve the RRH mounting status in the PLD,

the cells supported by the RRH, the RRH location, the maximum output

value and the alarm threshold value.

Cell Equipment Function Parameter

Retrieves the board cell information.

Command Description

RTRV-CELL-CONF Retrieves the configuration information of the cells provided by the system.

The operator can enter CELL_NUM to select a cell to be retrieved. If no cell

is selected, configuration information for all cells is displayed. The operator

can retrieve the cell‟s status, administrative state, sector information, FA

information, the channel card supporting the cell and the DSP information.



eNB Function Parameter

Retrieves configuration information within the eNB.

Command Description

RTRV-ENB-INF Retrieves the basic information of the base station (eNB).

It can retrieve whether the base station is a macro base station or a pico

base station, the base station‟s representative PLMN information, the eNB

ID information, the IP address and SCTP port information, and the

backhaul link‟s capacity information.

RTRV-HO-OPT Retrieves the handover-related information. It can retrieve the E-RAB

interaction method configured for the eNB, the neighbor cell list (NCL)

inclusion status, or the uplink data forwarding status at the target eNB.

RTRV-TIMER-INF Retrieves the timer values used by the ECCB within the base station.

It can retrieve the timer value used for message transmission/reception

with the UE when a call is setup; the timer value used for message

transmission/reception with the MME; the timer value used for message

transmission/ reception with the neighbor eNB; or the timer value used by

other ECCBs.

RTRV-CSL-CTRL Retrieves the Call Summary Log (CSL) function‟s control information within

the base station. The parameter defined in the PLD indicate the threshold

for CSL generation within the base station.

RTRV-CELL-IDLE Retrieves the EUTRAN cell information within the base station.

RTRV-BAR-DATA Retrieves the access barring data according to the CPU status within the

base station. It retrieves the access barring data parameter sent to the SIB

2 according to the CPU overload status. When the UE issues service

request, it controls cell access according to the access barring data

parameter value of SIB 2.

RTRV-BAR-EMERG Retrieves the access barring emergency parameter information according

to the CPU status within the base station. It retrieves access barring

emergency parameter information according to the CPU status within the

base station. When the UE issues emergency call request, it controls cell

access according to the access barring emergency parameter value.

RTRV-BAR-SIG Retrieves the access barring signaling parameter information according to

the CPU status within the base station. It retrieves the access barring

signaling parameter sent to the SIB 2 according to the CPU overload

status. When the UE issues attach, it controls cell access according to the

access barring signaling parameter value.

RTRV-BLACK-LIST Retrieves the blacklist cell information for each cell within the base station.

The blacklist cell information for each cell within the base station is sent to

the UE during the basic call procedure.

RTRV-CELL-RSEL Retrieves the cell reselection information within the base station.


RTRV-CELL-SEL Retrieves the cell selection information within the base station.




(Continued)

Command Description

RTRV-CSGPCI-

IDLE

Retrieves the Closed Subscriber Group (CSG) related PCI of the cell. If the

cell type is set to CSG, the PCI value or the PCI range of the CSG is

included in the SIB and sent.

Also, if the cell type is set to Macro, SIB inclusion is determined by usage.

RTRV-SIB-INF Retrieves the interval for the SIB of the cell. SIBs 2 through 11 are sent as

system information (SI) messages, and the SIB v.s. SI message mapping

information for SIBs 2 through 11 is included in SchedulingInfoList of SIB 1.

Each SIB is included in one SI message, and the SIBs of the same interval

are mapped to the same SI message. There can also be multiple SI

messages sent at the same interval. SIB 2 is always mapped to the first SI

message on the SI message list of the scheduling info list.

RTRV-MOBIL-STA Retrieves the mobility state. If a CELL_NUM parameter value is entered,

only the specified mobility state information is retrieved. If no CELL_NUM

parameter value is entered, all mobility state is retrieved.

RTRV-TIME-INF Retrieves the UE timer constant information within the base station. It

consists of the UE-Timers And Constants information broadcast to SIB2

and the UE-specific timer information.

The timer values broadcast to SIB include t300, t301, t310, n310, and n311

values, and the other values are UE-specific timer values which are

included in the RRC message.

RTRV-HRPD-BCLS Retrieves the CDMA2000 HRPD band class information within the base

station. CDMA 2000 HRPD can have up to 32 band classes; this command

retrieves priority and related information for reselecting each band class.

RTRV-HRPD-OVL Retrieves the overlaid HRPD cell information for the specified cell within

the base station. Each cell can have 1 HRPD cell; the command retrieves

the ID of the cell or the sector ID.

RTRV-HRPD-PREG Retrieves the CDMA2000 HRPD pre-registration information.

If a CELL_NUM parameter value is entered, only the specified CDMA2000

HRPD pre-registration information is retrieved.

If no CELL_NUM parameter value is entered, all registered CDMA2000

HRPD pre-registration information is retrieved.

RTRV-C1XRTT-

BCLS

Retrieves the CDMA2000 1XRTT bandclass information.

If a BC_INDEX parameter value is entered, only the specified CDMA2000

1XRTT bandclass information is retrieved.

If no BC_INDEX parameter value is entered, all CDMA2000 1XRTT

bandclass is retrieved.

RTRV-C1XRTT-OVL Retrieves the CDMA2000 1XRTT overlay information within the base

station. If a Cell Num parameter value is entered, only the information of

the CDMA2000 1XRTT cell overlaid with the specified cell is retrieved. If no

Cell Num parameter value is entered, all the information is retrieved.

RTRV-C1XRTT-

PREG

Retrieves the CDMA2000 1xRTT CSFB-Pre-Registration criteria

information within the base station. It is used when the EUTRA cell requires

CS registration or pre-registration towards CDMA2000 1XRTT.



(Continued)

Command Description

RTRV-CAS-IDLE Retrieves the CSG cell ID. The retrieved parameter is broadcasted to SIB 1

via the EU.

RTRV-GERAN-

RESEL

Retrieves the GERAN reselect information within the base station.

It retrieves the timer information required for reselection to a GERAN cell,

usage status of scaling factor, and timer for each scaling factor. This

command is included in the SIB and sent to the UE.

RTRV-SIB-IDLE Retrieves the max size of the packed SI which can be sent by the cell. The

transmission size of the SIB information is determined by considering the

downlink bandwidth, DCI formation type, SIB reception time on cell edge,

and payload size.

RTRV-CELL-CAC Retrieves the CAC parameter information for each active cell within the

base station. The CAC at the cell level can perform backhaul-based CAC,

call count-based CAC, DRB count-based CAC, or QoS-based CAC.

It retrieves the threshold for performing CAC at the cell level, CAC option

and preemption status.

RTRV-ENB-CAC Retrieves the capacity based CAC parameter information for each active

eNB within the base station. The CAC performed at the base station level is

call count based CAC. It retrieves the threshold for performing CAC at the

base station level and the max call count information.

RTRV-QCAC-PARA Retrieves the active quality of service (QoS) CAC parameter information

within the base station. QoS CAC is performed at the cell level, for QCI of

each GBR bearer. Retrieves the threshold for each QCI for performing QoS

CAC and retrieves the threshold for determining the congestion status of

active cells.

RTRV-BHBW-QCI Retrieves the parameter information required for backhaul CAC for each

active QoS class identifier (QCI) within the base station.

Backhaul based CAC is performed on GBR bearers by QCI or service

group. This command tetrieves the threshold for performing backhaul

based CAC by QCI.

RTRV-BHBW-

SVCGR

Retrieves the parameter information for backhaul CAC by each active

service group within the base station. Backhaul based CAC is performed

on GBR bearers by QCI or service group. This command retrieves the

threshold for performing backhaul based CAC by service group.

RTRV-SRB-QCI Retrieves the SRB information of the Signaling Bearer Identity (SRB ID).

It retrieves resource type, which determines whether the SRB type is

Guaranteed Bit Rate (GBR) or Non-Guaranteed Bit Rate (NGBR), priority,

packet delay budget, and packet error loss rate of the SRB.

RTRV-SRB-RLC Retrieves the parameter information required for RLC protocol operation.

It can retrieve AMD PDU retransmission count, poll byte and poll PDU

settings for poll triggering, poll resend timer, loss detection timer setting,

and STATUS_PDU prohibit timer value for each SRB ID.



(Continued)

Command Description

RTRV-QCIDSCP-

MAP

Retrieves the differentiated services code point (DSCP) mapping

information for each QCI.

RTRV-DSCPCOS-

MAP

Retrieves the COS mapping information for each differentiated services

code point (DSCP). The COS values mapped to the DSCP values are

marked with VLAN TAG.

RTRV-BHCGT-

PARA

Retrieves the backhaul congestion monitoring settings. Backhaul

congestion monitoring on a backhaul port of the eNB requires queue

length, rate adjustment information, and monitoring interval; these settings

are retrieved.

RTRV-BHCGT-QUE Retrieves the backhaul port and queue settings on which backhaul

congestion is monitored.

Each backhaul port has up to 8 queues; each queue status

(enable/disable) can be retrieved.

RTRV-QCI-VAL Retrieves the configuration parameter information for each QoS Class

Identifier (QCI) used by the Evolved Universal Terrestrial Radio Access

Network (EUTRAN) within the base station.

The QCI configuration parameters include Status, Resource Type, Priority,

Packet Delay Budget (PDB), and Packet Error Loss Rate (PLER) Backhaul

Service Group.

RTRV-LOCH-INF Retrieves the information required for logical channel operation.

RTRV-RLC-INF Retrieves the information required for RLC protocol operation.

It can retrieve the RLC mode, AMD PDU retransmission count at the base

station and at the UE, poll byte and poll PDU settings for poll triggering, poll

resend timer, loss detection timer setting, and STATUS_PDU prohibit timer

value for each QCI.

RTRV-PDCP-INF Retrieves the PDCP information. The PDCP information retrieved includes

UM SN size, discard timer, and forward end timer for each QoS class.

If no QoS class is specified, information for all 256 QoS classes is

retrieved.

RTRV-GTP-INF Retrieves the GTP information. The information retrieved includes keep

alive usage status, timeout interval, and sequence number usage status of

the GTP. If keep alive is enabled, the GTP ECHO-REQ message sent to

the S-GW at a specified interval (T3_TIMER_LONG). If the GTP ECHO-

RESP message is not received from the S-GW before the next message

transmission, the message is resent by the number of times specified by

N3_REQUEST at the interval of T3_TIMER.

RTRV-PCCH-CONF Retrieves the paging control channel (PCCH) configuration information

within the base station. Paging is performed when initiating a mobile

terminating connection, when triggering the UE to reload the system

information, or when sending Earthquake and Tsunami Warning System




(Continued)

Command Description

RTRV-PDSCH-IDLE Retrieves the physical downlink shared channel (PDSCH) configuration

information within the base station. It can set the power ratio of the

resource element (RE) which transmits the reference signal and the RE

which transmits the data over the PDSCH.

RTRV-PHICH-IDLE Retrieves the Physical Hybrid ARQ Indicator Channel (PHICH)

configuration information within the base station. It can retrieve the

information related to PHICH duration and resource.

RTRV-PUSCH-

CONF

Retrieves the Physical Uplink Shared Channel (PUSCH) configuration

information within the base station. It can retrieve 64QAM reception

availability status and hopping related information of the base station.

RTRV-RACH-CONF Retrieves the Random Access Channel (RACH) configuration information

within the base station. It can retrieve the backoff indicator, Msg3 HARQ

send count, non-dedicated/dedicated preamble count, power ramping step

and max send count, and preamble group A and B count information.

RTRV-TIME-ALIGN Retrieves the time alignment configuration information of the UE. Unless

the time alignment timer value is infinity, the UE receives the timing

advance command within the timer value to determine that the uplink

timing is valid. Otherwise, the UE releases the PUCCH and SRS

resources.

RTRV-SNDRS-

CONF

Retrieves the UL sounding reference signal configuration information within

the base station. It can retrieve ACK/NACK, simultaneous transmission

support for SR and SRS, SRS usage status in the cell, and the SRS

MaxUpPts value.

RTRV-PWR-PARA Retrieves the configuration information of uplink power control within the

base station. It can retrieve the alpha value used in PUSCH power control,

settings related to difference in transmission power by PUCCH format,

p0_nominal_PUCCH and p0_nominal_PUSCH settings, and UL IOT target

value.

RTRV-BCCH-CONF Retrieves the Broadcast Control Channel (BCCH) configuration information

within the base station. It can retrieves the value which determines the

modification interval of the system information.

RTRV-PUSCH-IDLE Retrieves the Physical Uplink Shared Channel (PUSCH) configuration

information within the base station. It can retrieve the n (1)_DMRS value

used to determine the cyclic shift value of the PUSCH reference signal.

RTRV-RACH-IDLE Retrieves the Random Access Channel (RACH) configuration information

within the base station. It can retrieve the time taken for the UE to wait for

the RA response.

RTRV-CLOCK-

CTRL

Retrieves the information required for clock advance/retard setting of the

modem/DSP. The base station‟s DU signal send/receive time changes

according to the value entered for clock advance/retard. If the clock

advance/retard value increases when the RU settings remain constant, the

UE‟s UL timing advance value decreases.



(Continued)

Command Description

RTRV-CQI-REP Retrieves the information required for CQI reporting operation.

It can retrieve whether only wideband CQI is operated or wideband CQI

and subband CQI are operated simultaneously for each DL transmission

mode.

RTRV-DPHY-

PUSCH

Retrieves the information required for dedicated PUSCH operation.

When the UCI must be sent on the uplink in the same subframe as the

PUSCH, it can retrieve the beta Offset ACK, beta Offset CQI, and beta

Offset RI which determine how much resources should be used by the UCI

in the PUSCH.

RTRV-DPHY-SPS Retrieves the information required for dedicated semiPersistScheduling

operation. It can retrieve the UL power related settings and two-interval

SPS pattern usage status for SPS operation.

RTRV-DPHY-SR Retrieves the information required for dedicated Scheduling Request

operation. It can retrieve the maximum scheduling request send count for

the UE.

RTRV-ULPWR-

CTRL

Retrieves the parameter information required for dedicated uplink power

control operation. It can retrieve the p0 value for PUSCH/PUCCH by UE,

usage status of accumulation mode of the TPC, power offset of the SRS

with the PUSCH, and the L3 filtering coefficient used by the UE for pathloss

calculation.

RTRV-DPHY-

ULSRS

Retrieves the parameter information required for dedicated uplink sounding

RS operation. It can retrieve hopping bandwidth of the SRS and send

duration of the SRS.

RTRV-DRX-INF Retrieves the information required for DRX operation.

It can retrieve DRX usage status, long DRX cycle, short DRX usage status

and cycle information.

RTRV-DL-SCHED Retrieves the downlink scheduling configuration information for the MAC

layer within the base station. It can retrieve fairness, channel quality, and


RTRV-UL-SCHED Retrieves the uplink scheduling configuration information for the MAC layer

within the base station. It can retrieve fairness, channel quality, and priority-

related scheduler settings (alpha, beta, and gamma).

RTRV-TRCH-BSR Retrieves the information required for transport channel operation.

It can retrieve BSR-related timer values.

RTRV-TRCH-INF Retrieves the information required for transport channel operation.

It can retrieve the max UL HARQ retransmission count, TTI bundling usage

status and band, PHR send interval, and the pathloss change value.

RTRV-EUTRA-FA Retrieves the parameter information required for EUTRA FA priority

information operation. If a Cell Num parameter value is entered, only the

EUTRA FA registered with a specific cell is retrieved. If no Cell Num

parameter value is entered, the EUTRA FA information of all cells is

retrieved.



(Continued)

Command Description

RTRV-MEAS Retrieves the statistics collection status (STOP/START) of the eNB and

statistics collection status for each family (enable, disable).

RTRV-MSGAP-INF Retrieves the measurement gap information configured for each cell within

the base station. It retrieves the measurement gap information required for

SON ANR, Inter FA, and Inter-RAT meausrement.

RTRV-UTRA-FA Retrieves the UTRA FA priority information. It can retrieve only the UTRAN

FA object registered with a specific E-UTRAN served cell. If no CELL_NUM

or FA_INDEX parameter value is entered, all UTRAN FA objects are

retrieved.

RTRV-HRPD-FREQ Retrieves the CDMA2000 HRPD carrier information.

It can retrieve only the CDMA HRPD frequency registered with a specific E-

UTRAN served cell. If no CELL_NUM or Carrier Index parameter value is

entered, all CDMA2000 HRPD carriers are retrieved.

RTRV-EUTRA-

A1CNF

Retrieves the EUTRA A1 criteria information. It uses the CELL_NUM and

PURPOSE parameter values to retrieve only the EUTRAN A1 event report

registered with a specific

E-UTRAN served cell. If no CELL_NUM or PURPOSE parameter value is

entered, all EUTRAN A1 event reports are retrieved.

RTRV-EUTRA-

A2CNF




If no CELL_NUM or PURPOSE parameter value is entered, all EUTRAN A2

event reports are retrieved.

RTRV-EUTRA-

A3CNF






RTRV-EUTRA-

A4CNF






RTRV-EUTRA-

A5CNF






RTRV-EUTRA-PRD Retrieves the EUTRA periodic criteria information. It uses the CELL_NUM

and PURPOSE parameter values to retrieve only the EUTRAN periodic

report registered with a specific E-UTRAN served cell. If no CELL_NUM or

PURPOSE parameter value is entered, all EUTRAN periodic reports are

retrieved.



(Continued)

Command Description

RTRV-UTRA-

B1CNF

Retrieves the UTRA B1 criteria information. It uses the CELL_NUM and

PURPOSE parameter values to retrieve only the UTRAN B1 event report


If no CELL_NUM or PURPOSE parameter value is entered, all UTRAN B1


RTRV-UTRA-

B2CNF

Retrieves the UTRA B2 criteria information. It uses the CELL_NUM and

PURPOSE parameter values to retrieve only the UTRAN B2 event report


If no CELL_NUM or PURPOSE parameter value is entered, all UTRAN B2


RTRV-UTRA-PRD Retrieves the UTRA periodic criteria information. It uses the CELL_NUM

and PURPOSE parameter values to retrieve only the UTRAN periodic


PURPOSE parameter value is entered, all UTRAN periodic reports are

retrieved.

RTRV-C1XRTT-

B1CNF

Retrieves the CDMA2000 1xRTT B1 criteria information.

It uses the CELL_NUM and PURPOSE parameter values to retrieve only

the CDMA 1XRTT B1 event report registered with a specific E-UTRAN

served cell. If no CELL_NUM or PURPOSE parameter value is entered, all

CDMA 1XRTT B1 event reports are retrieved.

RTRV-C1XRTT-

B2CNF

Retrieves the CDMA2000 1xRTT B2 criteria information.


the CDMA 1XRTT B2 event report registered with a specific E-UTRAN


CDMA 1XRTT B2 event reports are retrieved.

RTRV-C1XRTT-

PRD

Retrieves the CDMA2000 1xRTT Periodic criteria information. It uses the

CELL_NUM and PURPOSE parameter values to retrieve only the CDMA

1XRTT periodic report registered with a specific E-UTRAN served cell. If no

CELL_NUM or PURPOSE parameter value is entered, all CDMA 1XRTT

periodic report information is retrieved.

RTRV-HRPD-

B1CNF

Retrieves the CDMA2000 HRPD B1 criteria information.


the CDMA HRPD B1 event report registered with a specific E-UTRAN


CDMA HRPD B1 event reports are retrieved.

RTRV-HRPD-

B2CNF

Retrieves the CDMA2000 HRPD B2 criteria information.


the CDMA HRPD B2 event report registered with a specific E-UTRAN


CDMA HRPD B2 event reports are retrieved.



(Continued)

Command Description

RTRV-HRPD-PRD Retrieves the CDMA2000 HRPD periodic criteria information. It uses the

CELL_NUM and PURPOSE parameter values to retrieve only the CDMA

HRPD periodic report registered with a specific E-UTRAN served cell. If no

CELL_NUM or PURPOSE parameter value is entered, all CDMA HRPD

periodic report information is retrieved.

RTRV-QUANT-

EUTRA

Retrieves the quantity settings for EUTRA measurement.

When the base station sends the coefficient value used for EUTRA

measurement to the UE, the UE applies the coefficient value and performs

measurement on the EUTRA cell.

RTRV-QUANT-

UTRA

Retrieves the quantity settings for UTRA FDD/TDD measurement.

When the base station sends the coefficient value used for UTRA


measurement on the UTRA TDD or FDD cell.

RTRV-QUANT-

CDMA

Retrieves the quantity settings for CDMA2000 measurement.

When the base station sends the coefficient value used for CDMA 2000


measurement on the CDMA 2000 cell.

RTRV-GERAN-

B1CNF

Retrieves the GERAN B1 event report information. It uses the CELL_NUM

and PURPOSE parameter values to retrieve only the GERAN B1 event


PURPOSE parameter value is entered, all registered GERAN B1 event

reports are retrieved.

RTRV-GERAN-

B2CNF

Retrieves the GERAN B2 event report information. It uses the CELL_NUM

and PURPOSE parameter values to retrieve only the GERAN B2 event


PURPOSE parameter value is entered, all registered GERAN B2 event

reports are retrieved.

RTRV-GERAN-FA Retrieves the GERAN FA object information. It uses the CELL_NUM and

FA_INDEX parameter values to retrieve only the GERAN FA object

registered with a specific E-UTRAN served cell. If no CELL_NUM or

FA_INDEX parameter values are entered, all registered GERAN FA objects

are retrieved.

RTRV-GERAN-PRD Retrieves the GERAN periodic event report information.


the GERAN periodic event report registered with a specific E-UTRAN


registered GERAN Periodic event reports are retrieved.

RTRV-UTRA-

RESEL

Retrieves the UTRAN FA reselect information. It uses the CELL_NUM

parameter input value to retrieve only the UTRAN FA reselect registered

with a specific E-UTRAN served cell.

If no CELL_NUM parameter value is entered, all registered UTRAN FA

reselection information is retrieved.



(Continued)

Command Description

RTRV-EPRAT-REL Retrieves the relation with the specified inter RAT for each cell within the

base station. If a CELL_NUM parameter value is entered, only the Inter

RAT relation information with the specified cell is retrieved.

If no CELL_NUM parameter value is entered, the Inter RAT relation with all

registered cells is retrieved.

It can retrieve the status which indicates validity of the current PLD, the

related RAT type, and the relation IDX which assigns DB index of the Inter

RAT neighboring cell.

RTRV-ROHC-INF Retrieves the information for the RObust Header Compression (ROHC)

protocol. The information retrieved includes the ROHC operation status an

support profile types for each QoS class.

If no QoS class is specified, information for all 256 QoS classes is

retrieved.

RTRV-SECU-INF Retrieves the current integrity protection and ciphering algorithms for the

base station.

RTRV-NBR-GERAN Retrieves the GERAN neighboring cell information near the base station.

It uses the CELL_NUM and RELATION_IDX parameter values to retrieve

only the specified GERAN neighboring cell information. If no CELL_NUM or

RELATION_IDX parameter values are entered, all GERAN cell information

is retrieved.

RTRV-SCTP-PARA Displays the SCTP related parameters.

RTRV-NBR-ENB Changes the Neighbor eNB information required for Neighbor eNB

operation. It uses the NBR_ENB_INDEX parameter input value to change

the Neighbor eNB information.

RTRV-NBR-

EUTRAN

Retrieves the E-UTRAN neighboring cell information near the base station.


only the specified E-UTRAN neighboring cell information. If no CELL_NUM

or RELATION_

IDX parameter values are entered, all E-UTRAN neighboring cell

information is retrieved.

RTRV-NBR-UTRAN Retrieves the UTRAN neighboring cell information near the base station.


only the specified UTRAN neighboring cell information. If no CELL_NUM or

RELATION_IDX parameter values are entered, all UTRAN neighboring cell

information is retrieved.

RTRV-NBR-

C1XRTT

Retrieves the CDMA2000 1XRTT neighboring cell information near the

base station. It uses the CELL_NUM and RELATION_ IDX parameter

values to retrieve only the specified CDMA2000 1XRTT neighboring cell

information.

If no CELL_NUM or RELATION_IDX parameter values are entered, all

CDMA2000 1XRTT neighboring cell information is retrieved.



(Continued)

Command Description

RTRV-NBR-HRPD Retrieves the CDMA2000 HRPD neighboring cell information near the base


retrieve only the specified CDMA2000 HRPD neighboring cell information.

If no CELL_NUM or RELATION_IDX parameter values are entered, all

CDMA2000 HRPD neighboring cell information is retrieved.

RTRV-MME-CONF Retrieves the MME-related parameters. It can retrieve the equip

information of the MME, the active state indicating whether to use S1, the

MME IP address, and the secondary MME IP address.

RTRV-POS-CONF It retrieves the settings required to provide location services.

RTRV-CDMA-CNF Retrieves the CDMA2000 related information included in the SIB.

It can retrieve the information used for CDMA2000-related SIB

configuration.

RTRV-C1XRTT-

MOBIL

Retrieves the CDMA2000 1xRTT mobility parameter information. It uses the

CELL_NUM parameter input value to retrieve only the CDAM2000 1XRTT

mobility parameter registered with a specific E-UTRAN served cell.

If no CELL_NUM parameter value is entered, all CDMA2000 1XRTT

mobility parameters are retrieved. It can retrieve the values used in the pre-

registration process for CDMA2000 1XRTT interoperation.

RTRV-C1XRTT-

ACBAR

Retrieves the AC barring information for CDMA 1xRTT.

The retrieved parameters are broadcasted to SIB 8 via the EU.

RTRV-HYBRIDPCI-

IDLE

Retrieves the hybrid cell related PCI of the cell.

If the cell type is set to hybrid cell, it retrieves the PCI value or PCI range of

the hybrid cell.

RTRV-OPENPCI-

IDLE

Retrieves the open cell related PCI of the cell. If the cell type is set to open

cell, it retrieves the PCI value or PCI range of the open cell.

RTRV-PAT-MAP Retrieves the static Port Address Translation (PAT) mapping information.

It can retrieve mapping information for the IP/UDP port of the monitoring

server which retrieves the information of the supplementary equipment and

the IP/UDP port of the supplementary equipment.

RTRV-PAT-INF Retrieves the static Port Address Translation (PAT) setting information.

It can retrieve the IP/UDP port setting information for the backhaul port and

the UDE port of the eNB.

RTRV-PRACH-

CONF

Retrieves the Physical Random Access Channel (PRACH) configuration

information within the base station. It can retrieve high speed flag, PRACH

configuration index, root sequence index, and zero correlation zone

configuration information.

RTRV-SRS-IDLE Retrieves the parameters required to allocate Sounding Reference Signal

(SRS) resources in the specified cell within the base station. SRS resource

allocation is performed for each UE. For TDD, a different subframe location

is used for each SRS allocation type.

RTRV-DPHY-RLF Retrieves the dedicated PHY RLF information.

It can retrieve parameter information used for determining RLF.



(Continued)

Command Description

RTRV-MEAS-FUNC Retrieves the measurement information configured for each cell within the

base station. If a Cell Num parameter value is entered, only the

measurement related registered with a specific cell is retrieved. If no Cell

Num parameter value is entered, the measurement related information of

all cells is retrieved.

RTRV-C1XRTT-

FREQ

Retrieves the CDMA2000 1xRTT carrier information.

It can retrieve only the CDMA 1XRTT frequency registered with a specific

E-UTRAN served cell. If no CELL_NUM or Carrier Index parameter values

are entered, all CDMA2000 1XRTT Carrier information is retrieved.

RTRV-CELL-ACS Retrieves the cell access information within the base station.




SON Function Parameter

Retrieves the Self Optimizing Network (SON) parameter information.

Command Description

RTRV-SON-DLICIC Retrieves the SON DL ICIC function.

RTRV-SON-ULICIC Retrieves the parameter information related to the Uplink Inter-Cell

Interference Cancellation (UL ICIC) operation.

It is defined as one of the scheduler functions of the eNB system.

Unlike other SON functions, it is set by a separate flag and the Manual

Apply option is not available.

RTRV-ES-COM Retrieves the mode common parameter information of the SON energy

saving function. The parameter of this command retrieves the activating

conditions when the ES function is set to Auto Apply using the CHG-

SONFN-CELL command.

Traffic estimation for selecting ES mode involves the following two

methods. The first method is calculation with the average value of the traffic

load statistics for the specified time during the last 15 or 30 days as

determined by the DATA_VALIDITY parameter. The second method is

calculation with weight-adjusted value of the MOVING_

AVERAGE_WEIGHT parameter value for the last 2, 3, 4, 5, or 10 hours as


The maximum value of these two methods is selected for determining the

active ES mode. Energy saving guarantees operation performance by

monitoring the abnormal traffic state and the abnormal system state on an

hourly basis. Abnormal traffic state means that the traffic exhibits sudden

unusual changes or that huge differences exist between the traffic

estimation and the actual traffic load measurement and therefore traffic

estimation performance is questioned (estimation hit ratio is lower than the

CORRELATION_COEFFICIENT_THRESHOLD parameter value).

In this case, the energy saving function stops and the system returns to the

ES normal mode. Abnormal system state means that the system is in

abnormal state according to the eNB monitoring function.

It is determined by the RE_TX_THRESHOLD and BLER_THRESHOLD

parameters. In this case, the energy saving function stops immediately and

the system returns to the ES normal mode.



(Continued)

Command Description

RTRV-ES-TYPE Retrieves the mode type of the SON energy saving function. ES mode type

is applied when the energy saving function is set to Auto Apply using the

CHG-SONFN-CELL command.

In the LTE eNB system, the energy saving function is enabled when the

system traffic load estimated by traffic analysis satisfies the ES mode

entering condition. In other words, normal mode and three ES modes are

defined as follows:

- Normal Mode: The eNB is operating normally.

Normal mode is maintained if the estimated traffic load is greater than the

entering threshold of ES mode 1.

- ES mode #: PA bias of the eNB is adjusted for operation.

An appropriate PA bias change mode is enabled if the estimated hourly

traffic load is less than the entering threshold of ES Mode. The greater the

number of ES Mode, the more powerful energy saving function is enabled.

RTRV-ES-SCHED Retrieves the schedule of the SON energy saving function. The parameter

of this command is used to retrieve the schedule information of the pre-

defined time based energy saving function which becomes active when the

energy saving function is set to Manual Apply using the CHG-SONFN-CELL

command. The system operator can use the LSM to schedule the energy

saving function of the eNB.

The Energy Saving Manual Apply function executes the PA bias voltage

change command every hour according to the set schedule. The activation

time, activation status, ES voltage mode, and the RB type to restrict can be

specified. Energy saving by schedule can be set on an hourly basis; the

schedule is checked hourly for determining the operation.

If ES_MODE_VOLTAGE_TYPE is the same for the previous hour and the

current hour, the operation for the previous hour remains for the current hour

as well. The ES_STATE parameter can be used for determining SUSPEND

or ACTIVE. Also, to stop the currently active ES mode, ES_STATE which is

ACTIVE for the current hour is modified to SUSPEND.

The ES_MODE_VOLTAGE_TYPE and ES_MODE_RB_TYPE parameters

determine the voltage mode which should be active and the RB type which

should be restricted for the specified hour. Therefore, these two parameters

should be paired properly in order to guarantee performance.

In other words, if ES_MODE_VOLTAGE_TYPE is ES Mode1_Voltage, ES_

MODE_RB_TYPE should also be set to ES Mode1_RB.



(Continued)

Command Description

RTRV-SON-ANR Retrieves the parameter information of the SON ANR function.

The parameter of this command retrieves the activating conditions when the

ANR function is set to Manual Apply or Auto Apply using the CHG-SONFN-

CELL command. By default, the ANR function of the LTE SON is supported

by the User Equipment (UE) or the LSM for obtaining the neighbor identity

information including ECGI/TAC/PLMN for automatic addition of an NR.

The NR ranking function is performed by considering the handover key

performance index (KPI: HO attempt/failure rate, etc.) for each neighboring

cell obtained over the X2 interface. The ranking is used as the reference for

selecting an NR from the existing NRs to add to the handover blacklist in

order to add an NR for the new adjacent cell when the system is running at

the maximum NRT size. In other words, if a new NR is added while the

maximum NRT is full, the lowest ranking NR is added to the blacklist.

For determining the ranking, the DEFAULT_

WEIGHT, HO_ATTEMPT_WEIGHT, and HO_SUCCESS_

WEIGHT parameter values can be used for assigning weights to the new NR,

HO attempt rate, and HO success rate.

The HO blacklist function identifies invalid adjacent cells from the HO

performance viewpoint and adds them to the HO blacklist in order to prevent

unnecessary handover to invalid adjacent cells and ultimately to improve the

HO KPI.

The criteria for inclusion in the HO blacklist are either that the NR does not

satisfy the HO KPI or that the HO attempt to wrong cells increases by a

certain rate. The first condition is set using the

LOWER_HO_ATTEMPT_RATE and LOWER_ HO_SUCCESS_TO_KPI

parameter information, while the second is set using the

UPPER_HO_TO_WRONG_RATE parameter information. On the contrary, if

the HO attempt to the black cell on the blacklist increases by a certain rate, it

escapes the blacklist. The escape condition is set using the

UPPER_HO_TO_BLACK_RATE parameter.

RTRV-SON-MRO Retrieves the parameter information required for Mobility Robustness

Optimization (MRO). It retrieves the time taken to collect the handover data

statistics required for MRO, the KPI reference for triggering MRO, the

handover attempt reference for triggering MRO, the offset minimum/maximum

values which may be adjusted by MRO, the flag and related parameter values

for turning pingpong optimization on/off, and the flag and related parameter

values for turning TTT optimization on/off.

This command is significant if SONFN-CELL: mobilityRobustnessEnable: = 1

(Manual Apply) or 2 (Automatic Apply).



(Continued)

Command Description

RTRV-SON-SO Retrieves the parameter information related to SON self optimization. The

parameters retrieved and their functions are as follows.

- RRH Optic Delay Compensation

During the initial RRH installation or when the optic delay value is changed,

the SON delay compensation function is measures the optic delay value of

each RRH and calculates the modified Tx time buffer and Rx time buffer

values.

The time buffer value obtained is sent to the respective RRH for RRH delay

compensation. The TX_TBMAX and RX_TBMAX values retrieved by this

command are required in the time buffer calculation process.

- Related command: The RRH optic delay compensation operation is

determined by the DELAY_COMPENSATION_ ENABLE parameter value of

the CHG-SONFN-ENB command. If the parameter value is sonFuncOff,

compensation is disabled.

If the parameter value is sonAutoApply, compensation is enabled. The

TX_TBMAX and RX_TBMAX parameters can be changed using the CHG-

SON-SO command.

RTRV-SONFN-

CELL

Retrieves the SON function cell control flag.

This command retrieves the current mode of the SON function controlled for

each cell. Available modes include three modes of Function Off, Manual

Apply, and Auto Apply or two modes except for Manual Apply. The SON ANR

function automatically compiles the Neighbor Relation Table (NRT) and

detects any changes in the operation environment for maintaining optimal

NRT. In other words, the eNB uses the ANR function to update the NRT by

automatically detecting topological changes such as addition and removal of

neighbor eNBs and by adding or removing new neighboring cells. The Energy

Saving (ES) function reduces the operation cost of the system by reducing the

eNB‟s energy (power) consumption. In other words, it flexibly adjusts the

system capacity in response to the actual traffic demand with the goal of

reducing the energy consumption.

RTRV-SONFN-

ENB

Retrieves the SON function eNB control flag.

This command retrieves the current mode of the SON function controlled for

each eNB. Available modes include three modes of Function Off, Manual

Apply, and Auto Apply or two modes except for Manual Apply. The SON PCID

function automatically allocates PCI to the cells belonging to the new eNB

during the self-establishment procedure of the newly added eNB and

automatically detects PCI collision/confusion with neighboring cells during

system operation. During the initial RRH installation or when the optic delay

value is changed, the SON delay compensation function is measures the optic

delay value of each RRH and calculates the modified Tx time buffer and Rx

time buffer values. The time buffer value obtained is sent to the respective

RRH for RRH delay compensation.



(Continued)

Command Description

RTRV-SON-

BLBO

Retrieves the parameter information required for Blaking Load Balancing

Optimization (BLBO). It retrieves the neighbor cell‟s load calculation interval,

BLBO state monitoring interval, the load value for starting BLBO, the load

value for stopping BLBO, the load value used as reference for overload, and

the margin value of the load calculation. This command is significant if

SONFN-CELL: lankingLoadBalancingEnable:= 1 (Automatic Apply).

RTRV-SON-RO Retrieves the parameter information required for RACH Optimization (RO).

It retrieves the period for collecting RACH data related statistics required for

RO operation, minimum and maximum values of the parameters modified by

RO, the parameters related to the number of dedicated preamble optimization

function, and the parameter information related to the RACH Tx power

optimization function and the PRACH configuration index optimization

function. This command is significant if SONFN-CELL: rachOptEnable: = 1

(Manual Apply) or 2 (Automatic Apply).



CHAPTER 3. Loading

The loading block starts, resets, and shuts down the various processors and devices

installed in the NE, and manages the software and firmware so that the system can provide

services normally. System loading is a procedure that involves registration of NE with the

Registration Server (RS), package selection, package download and execution.

The environment variables and LSM settings that are important for loading are related to

system initialization settings.

The operator can initialize the system and manage the software by executing commands in

the LSM CLI. All commands are available from the Command Line Interface (CLI)

window of the LSM GUI.

The operator can also execute the same commands from the CLI provided by the target.

The operator can check the various loading events that occur in the Network Element (NE)

using the LSM Event Viewer, in text format in real time. Moreover, the messages printed

out in text format in the Event Viewer are saved as text files. The operator can therefore

also check past events at any time.

Loading

All loading commands are available under the „SWM‟ folder in the LSM CLI.

The same commands are also available in the target CLI. For more information

on how to execute commands and check events or past events in the LSM, see

the eNB EMS User Manual.



3.1 Reset

The reset function is used to restart a specific processor board or unit, or the entire system

in case of abnormal operation. The following functions are available in this category.

Individual hardware unit reset

All NE reset

Service Interruption

The service may stop while the reset function is performed.

3.1.1 Individual Hardware Unit Reset

Individual hardware unit reset command resets each unit of the system.

Below are listed the H/W units which become the reset targets.

UMP

ECP

RRH

DSP

GPS

S1SCTP

RET

EAIU

When the Individual H/W Unit Reset command is sent, each designated H/W Unit will be

reset. This function can be carried out only if the master board of the system can

communicate with each H/W unit normally, and the loading block operates properly in the

master board.

When a H/W unit reset fails, one of the following error messages is displayed.

Error message Description

INVALID_UNIT_TYPE A reset command cannot be executed for this type of hardware unit.

INVALID_UNIT_ID A reset command cannot be executed because the hardware unit

corresponding to the specified ID does not exist.

TARGET_NO_RESPONSE A reset command cannot be executed because the loading process

is not running normally.




Command Description

INIT-DSP Resets the DSP. The DSP reset is processed by blocking or supplying the

power to the DSP. One or several DSPs can be reset simultaneously.

INIT-GPS Resets the GPS. The GPS reset is performed by blocking or supplying the

power to the GPS.

INIT-PRC Resets the system‟s processor unit (ECP, UMP).

INIT-RRH Resets the eNB's RRH. The RRH reset is performed through the VSS reset

method. One or several RRHs can be reset simultaneously.

INIT-S1SCTP Resets the S1 connection. The connection between the MME and eNB is

established using the SCTP protocol, and the S1AP specification is

followed. This command resets the connection between the MME and eNB.

INIT-RET Resets the Remote Electrical Tilting (RET) equipment. Two RETs can be

connected to one RU/RRH; each RET can be operated independently.

INIT-EAIU Resets the EAIU equipment. The PSU reset is processed through the

messaging method.

3.1.2 All NE Reset

The operator can reset the entire system. When a system reset command is executed, it first

resets all RUs and then resets the DU.


Command Description

INIT-SYS Resets the system.



3.2 Software Management

The software management function informs the operator of operating status, and manages

abnormal operation of any software block, as well as updating them. An online package

upgrade function is also provided for upgrading the entire package.

Various software management functions are provided as follows.

Viewing Information for the Loading Target Software

Viewing Information for the Running Software

Software Update

Viewing Package Information

Performing Online Upgrades

Viewing Information for the Loading Target Software

The operator can view the information on the software blocks being managed by the

loading block on the the master/sub board. By viewing the software block information, the

operator can identify the software name, software version, and software build number, etc.


Command Description

RTRV-SW-INF Retrieves the software unit information. The software units downloaded in

the eNB include the unique version number attributed during the creation

of the software image by the image creation system.

The software version retrieve function retrieves and displays the unique

version number attributed to each software unit. This command checks

whether the appropriate software unit is running on the appropriate board.



Viewing Information for the Running Software

For software blocks being managed by the loading block on the master/sub board, the

operator can view the information on a software block running on the system. The operator

can view the start time, current operation status, and reset count for each software block.

SW_UNIT_STATUS_ACTIVATED indicates software blocks currently running and

SW_UNIT_STATUS_DEACTIVATED indicates software blocks which could not start.


RTRV-ACT-SW

Command Description

RTRV-ACT-SW Retrieves the information of currently activated software unit.

The software unit listed in the software list is divided into data property

unit and active property unit. The data property unit is stored in the disk

as a file and referenced by the active software unit; the active property

unit runs as a daemon in the eNB. This command allows to view the

status of the software unit running as a daemon.

Software Update

The operator can update the software blocks being managed by the loading block, with new

ones stored in the IS. Software update is performed in two steps. First, download the

software block file for update from the IS to the NE. Second, update the file of the NE.

If the block is running on the processor, it resets with the updated file.

SW Update Event Trap for the update of the software running on the board, and the SW

Deactivate Event Trap and SW Activate Event Trap for the software operation status, occur

sequentially in the LSM event window. Therefore, the operator can check whether the

software update is performed successfully.

Updating a Call Processing Block

Updating a specific block that performs call processing may prevent services from

being provided.

Updating a Block Related to Command Processing

Updating the loading block, or SNMP block, which are related to command

processing, may not provide the command execution results.

The operator can check the information on the software blocks being managed by the

loading block using the RTRV-SW-INF command (used to view the information on the

loading target software).




Command Description

DNLD-SW Downloads the corresponding software unit to the system. In the event a patch,

etc. is distributed for the software running in the system, this command is used to

download the software required to apply the corresponding patch to the system.

The software unit that can be downloaded in the eNB is listed in the software

list. The software unit not listed in the software list cannot be downloaded.

UDT-SW Updates the software unit in the eNB.

The DNLD-SW and DNLD-SW-BAT commands must be executed prior to

executing this command.

The type of the software unit to apply is the data file type and demon type.

- Data file: Applies to the file stored in the same storage as the configuration

file; applies after the eNB has restarted.

- Demon: Replaces the runnable software unit with a new software unit, then

restarts.

DNLD-SW-BAT Downloads the software listed in the batch file. In the event a patch, etc. is

distributed for the software unit running in the eNB, this command records the

software unit required to apply the corresponding patch to the batch file and

downloads the software unit listed in the batch file to the eNB‟s main board.

The software unit that can be downloaded in the eNB is listed in the software

list. The software unit not listed in the software list cannot be downloaded.

UDT-SW-BAT Updates the software unit in batch type. Once executed, the eNB downloads

the batch file designated in the parameter and starts the update of the software

unit listed in the corresponding file. The software unit that only runs on the

main board will be updated on the main board; the software unit that only runs

on the sub board will updated on the sub board. The software unit that runs on

both the main board and sub board will be updated simultaneously. The DNLD-

SW and DNLD-SW-BAT commands must be executed prior to executing this

command. Also, the designated software unit must be previously downloaded

to the eNB.

[Command Execution Procedure]

1) Place the latest software image, which will be used to update the existing image, in the

correct package directory of the IS.

2) Execute the DNLD-SW command to download the software image to the master board.

3) Execute the UDT-SW command to update the existing image with the downloaded

image. If the software block is running, reset it with the updated image.

4) Execute the RTRV-SW-INF command to check whether the software file has been

updated successfully.

5) The DNLD-SW-BAT command is used to create a list of the software programs to be

downloaded, and then download them using a single command. Its function is identical

to DNLD-SW except for downloading more than one software program at the same time.

6) The UDT-SW-BAT command is used to create a list of the software programs to be

applied, and then apply them using a single command. Its function is identical to UDT-

SW except for applying more than one software program at the same time.



Viewing Package Information

The operator can view the information for the software package running on the system.


Command Description

RTRV-PKG-VER Retrieves the package version.

A unique version is attributed to the software package corresponding to

its functions and features. This command checks the software package

running in the eNB. There are two types of version: package version and

release version. The package version is determined differently depending

on the main features provided by the eNB. If one or more features are

added or modified, a package update must be performed as they will

mostly become incompatible with the previous features.

The release version can be used as a complementary identifier if an

update occurs within the same package version.

Performing Online Upgrades

The online upgrade allows that while package version „N‟ is running, package version

„N + 1‟ is downloaded, and then version „N‟ is upgraded to version „N + 1‟. For example, if

the current package version is 2.0.3.1 (N), it can be upgraded to the package 2.0.3.2 (N + 1),

and so on.

If online upgrading is performed while the new package is downloaded and the system is

running services, the OS does not need to be restarted. Online upgrading allows the

package to be upgraded faster than system reset. Some services may be interrupted while

the package is being upgraded.

The online upgrade procedure is as follows:

1) The DNLD-PKG command is sent from the LSM.

2) The loading block downloads the new package from the LSM or IS.

3) The loading block upgrades the existing package with the new package.

4) The loading block reports the upgrade results to the LSM.

5) The UDT-PKG command is sent from the LSM.

6) The loading block resets each block using the software files of the upgraded package.

7) After resetting all blocks using the new package, the loading block reports the results

to the LSM.

The command execution process is as follows:

1) Prepare the package version „N+1‟ which will be used to upgrade the existing version.

2) Click CLI in the LSM.

3) In the Target tab, expand the tree folders and select the NE.

4) In the Command tab, expand the SWM tree folder and select the DNLD-PKG

command to configure the package version „N+1‟ data in the target NE.

5) Check the results of the upgrade.

6) Execute the UDT-PKG command to apply the package version „N+1‟ to the target NE.

7) Check the results of the application of the package.



3.3 Firmware Management

Using the firmware management functions, information about the current firmware fused in

the processor and hardware units as well as the CPLD information can be obtained, and the

firmware can be updated.

The following types of firmware can be updated.

BOOTER: This is boot loader image for processor board.

POST: Power On Self Test image for processor board.

KERNEL: Kernel image for processor board. It also has its redundant image available.

RFS_RAW: The raw root file system image for processor board.

RFS: Root file system image for processor board. It also has its redundant image

available.

IF-FPGA: Interface firmware image.

CPLD: Control CPLD and Clock CPLD images.

UCCM: Clock unit firmware image.

RRH: Firmwage image used for RRH.

ECM: Firmware image used in the environment monitoring unit.

FCM_D: Firmware image used in the FAN control unit.

EAIU: Firmware image used in the EAIU.

Various firmware management functions are available as follows:

Viewing Firmware Information

Updating Firmware

Updating Firmware

Updating any incompatible/unverified firmware may lead to particular hardware

not function at all once it is reset. Further, power supply interruption during any

firmware update can damage the updating board(s) or device(s).

Viewing Firmware Information

The operator can view the firmware information stored in, or running on, the processor

boards and device boards. By executing the command used to view the firmware

information, the firmware version, firmware image size, and firmware build time, etc. can

be checked for the Booter, Kernel, RFS, RFS_RAW, POST, IF-FPGA, MOD-FPGA, and

CPLD. However, the image size and the build time are not displayed for the firmware of

the CPLD and some device boards. If this command is used to view firmware information

after a processor board firmware update has been carried out, the information on the most

recently updated firmware is displayed. If this command is used to view the information on

running firmware, the information on the firmware which was loaded at boot time and is

running, is displayed. This will continue until a reboot is done.




Command Description

RTRV-GPS-INVT Retrieves the GPS unit‟s inventory information. The inventory is a unique

information contained in the Field Replaceable Unit (FRU), and includes

the information such as serial number, HW/FW version, unit type, unit ID,

family type and installation date. It can retrieve the inventory information

as proposed in TS32.692.

RTRV-PRC-INVT Retrieves the processor unit‟s inventory information.

RTRV-RRH-INVT Retrieves the RRH unit‟s inventory information.

RTRV-EAIU-INVT Retrieves the EAIU unit‟s inventory information.

RTRV-FCM-INVT Retrieves the FAN control unit‟s inventory information.

Updating Firmware

The operator specifies a specific area for a specific board and can upgrade the firmware.

By executing this command, the operator can upgrade the firmware for the CPLD and

device boards as well as the Booter, Kernel, RFS, and RFS RAW. The new firmware file

should be present in the firmware storage path in IS. The updated firmware is applied when

the board is reset.

The firmware update consists of two steps. First, download the firmware file for update

from IS to NE, and then apply the downloaded firmware file.

Upgrading CPLD Firmware

If the CPLD firmware has been upgraded, the master board may be reset

automatically and service may be stopped.

When the firmware update command is executed, since the firmware file download-related

the FW Update Event Trap and FW Activate Event Trap occur, the operator can view the

result of the update.

The operator can view the changed firmware information using the DIS-FW-INFO

command used to view the firmware information. If a firmware upgrade is performed to the

same version, the Firmware Info Event Trap does not occur.




Command Description

DNLD-FW Downloads the firmware to the eNB. The firmware that can be downloaded in

the eNB includes the Booter, Kernel, RFS, RFS_FAW, RU/RRH, IF-FPGA,

post, EPLD, GPS, etc.; diverse devices included in the eNB are also subject

to the firmware application.

UDT-FW Updates the firmware. It is used to update the downloaded firmware unit to

the actual flash memory or the corresponding device unit.

Once executed, a verification is performed to the designated firmware; then

an update is processed either in the flash memory or in the corresponding

equipment through the designated device unit and proprietary interface. Once

the update is completed, the target unit will be reset to run the updated

firmware.

UDT-RRH-FW Updates the RRH firmware. Once executed, a verification is performed to the

designated firmware; then an update is processed in the RRH through the

proprietary interface. Once the update is completed, the target unit must be

reset to run the updated firmware.

DNLD-FW-BAT Downloads the firmware listed in the batch file to the eNB‟s main board.

UDT-FW-BAT Updates the firmware in batch format. Once executed, the eNB downloads

the batch file designated in the parameter and starts the update of the

firmware listed in the corresponding file. The device equipments process the

update directly in the main board, and the firmwares that need to be updated

in the sub board process the update in the sub board, thus allowing the

updates to be processed in parallel. Once the update is completed, the target

unit must be reset to run the updated firmware.

The DNLD-FW and DNLD-FW-BAT commands must be executed prior to

executing this command. Also, the designated firmware must be previously

downloaded to the eNB.

The command execution process is as follows.

1) Place the firmware file for update into the appropriate firmware storage directory of IS.

2) Execute the DNLD-FW command to download the necessary firmware to the NE.

3) Check whether there is the FW Update Event Trap in the Event window.

4) Execute the UDT-FW command to apply the downloaded firmware.

5) Check whether there is the FW Activate Event Trap in the Event window.

6) Check whether the firmware is updated using commands, such as RTRV-GPS-INVT,

RTRV-PRC-INVT, RTRV-RRH-INVT, and RTRV-IIU-INVT.



3.4 NTP Server Management

The system performs time synchronization with reference to the time information of the

specified Network Time Protocol (NTP) server. Up to two NTP servers can be specified so

that the NE can perform time synchronization using both of them. The NE first performs

time synchronization using the server specified as NTP ID 0. If this fails, it attempts time

synchronization using the server specified as NTP ID 1.

If time synchronization for which the specified NTP server is used fails, the NTP update

error alarm occurs. In this case, the operator must check whether the NTP daemon is

operating normally on the server specified as the NTP server.

The following NTP server management functions are available to operator. Using these

functions the operator can view and change NTP server information.

Viewing NTP Server Information

Changing NTP Server Information

NTP Server Commands

The commands included in this range exist in the CM folder on the command tree

of the LSM CLI.

Viewing NTP Server Information

Using this function, the operator can view the NTP server information configured in the

system.

The information for both the specified NTP servers (NTP ID 0 and NTP ID 1) can be

checked.


Command Description

RTRV-NTP-CONF Retrieves the NTP server IP.

Changing NTP Server Information

Using this function, the operator can change the NTP server information for either or both

of the available NTP IDs.


Command Description

CHG-NTP-CONF Changes the NTP server IP.



3.5 Inventory Management

The inventory management functions manage the unique hardware information of the

system‟s hardware units. Each hardware unit provides the following unique hardware

information:

FAMILY_TYPE: Displays which family the corresponding hardware unit belongs to.

VERSION: Displays the version of the corresponding hardware unit.

SERIAL: Displays the serial number of the corresponding hardware unit.

VENDOR: Displays the manufacturer of the corresponding hardware unit.

MNF_DATE: Displays the manufacturing date of the corresponding hardware unit.

INSTALL_DATE: Displays the installation date of the corresponding hardware unit.

SERV_DATE: Displays the last serviced date of the corresponding hardware unit.

POSITION: Displays the installation location of the corresponding hardware unit.

Viewing the Inventory Information

The operator can view the unique hardware inventory information stored in each hardware

unit. The details of the hardware information can be viewed with the corresponding

retrieval commands.


Command Description

RTRV-GPS-INVT Retrieves the GPS unit‟s inventory information. The inventory is a unique

information contained in the Field Replaceable Unit (FRU), and includes

the information such as serial number, HW/FW version, unit type, unit ID,

family type and installation date. It can retrieve the inventory information

as proposed in TS32.692.

RTRV-PRC-INVT Retrieves the processor unit‟s inventory information.

RTRV-RRH-INVT Retrieves the RRH unit‟s inventory information.

RTRV-EAIU-INVT Retrieves the EAIU unit‟s inventory information.

RTRV-FCM-INVT Retrieves the FAN control unit‟s inventory information.



CHAPTER 4. Status

The status information of the LTE eNB system displays the current status of the system

(processor, device, link), the status of the processor‟s resource (CPU, memory, disk), and

the status of S1/X2. Generally, the status of the processor is determined with the hardware

alarm and the communication fail alarm. The status of the device and the link can be

viewed through the information transmitted from the corresponding device.

The RTRV-PRC-STS command displays the processor status by retrieving the status of the

processor (UMP, ECP) managed by the eNB. There is a command to display the status of

other devices (GPSR, RRH, rectifier) and link operation. The following types of status are

available:

Processor status

Processor‟s resource status

Call resource status

Device status

Link status

S1/X2 status

PRB usage status

Inventory information

The system state is categorized as follows:

ADMINISTRATIVE STATE

OPERATIONAL STATE

USAGE STATE

ADMINISTRATIVE STATE

The operator uses administrative state to set usage status of the system.

State Description

Locked The information set by the operator so that the resource is not used.

Shutting down The operator allows no further users, except for any using a resource, to

use the resource. It is the step before Locked is set.

Unlocked The information set by the operator so that the resource is used.



OPERATIONAL STATE

Operational state indicates whether the system is operational.

State Description

Enabled State indicating that the operation of a resource is available

Disabled State indicating that the operation of a resource is not available

USAGE STATE

Usage state indicates the system usage level.

State Description

Idle State indicating that a user is using the resource

Active State indicating that no user is using the resource

Busy State indicating that all of the maximum capacity of the resource is being

used and a new user can not be accepted

4.1 Processor Status

Displays the status of each processor in eNB. The Disabled status represents an abnormal

status of the processor or a communication fail alarm. The Enabled status represents the

board loading and operating normally or recovered communication.

Command Description

RTRV-PRC-STS Displays the status of the processor (unit).

- OPERATIONAL STATE

4.2 Processor Resource Status

Displays the status of the resource (CPU, memory, disk) of each processor in eNB.

The resource status will not be displayed if the processor‟s status is abnormal or if

communication is not possible.

Command Description

RTRV-CPU-UTIL Displays the CPU load.

RTRV-MEM-UTIL Displays the memory availability.

Displays TOT_SIZE, USED_SIZE and FREE_SIZE of the memory.

RTRV-DISK-UTIL Displays the disk availability.

Displays TOT_SIZE, USED_SIZE and FREE_SIZE of the disk.



4.3 Call Resource Status

The call service is controlled based on the status of the system and cell which logically

represent the call resource. In the cell, the maximum number of services is determined

depending on the system capacity, and the available resource is generated depending on the

cell status and interfaces with the UE.

Command Description

RTRV-SYS-STS Displays the status of the cell. The status of the cell is as follows:

- OPERATIONAL STATE

- USAGE STATE

The administrative state of the system that can be modified by the operator

can be viewed using RTRV-SYS-CONF.

RTRV-CELL-STS Displays the status of the cell. The status of the cell is as follows:

- OPERATIONAL STATE

- USAGE STATE

The administrative state of the cell that can be modified by the operator can

be retrieved using RTRV-CELL-CONF.



4.4 Device Status

The status of the device is managed by the main processor of the system. It manages the

status of the device (GPSR and RRH) managed by the system.

4.4.1 GPSR Status Management

The GPSR is a device which provides the system clock. You can view the current status of

the GPSR and various supplementary information by executing the RTRV-GPS-STS

command. The types of GPSR status available are as follows:

Status Description Output Condition

LOCKED Normal The locked normal status

UNLOCKED Abnormal The unlocked status

NOT HOLDOVER Not Holdover The non-holdover normal

status

HDOVER Holdover The holdover status

The RTRV-GPS-STS command displays the following information, as well as the latitude,

longitude, height, and TOD.

TFOM: Time Figure of Merit value

LOCK: The state of the front-panel GPSR Lock LED. [0 = LED is off (UNLOCK),

1 = LED is on (LOCK)]

ANT: GPSR antenna delay value in seconds

SATC: The number of satellites being tracked

SATN: a list of all satellites being tracked. Each satellite is identified by its pseudo

random noise code (PRN). [Range = 1 to 32 (PRN), 0 (no satellites being tracked)]

TINT (Time Interval): The difference or timing shift between the HP SmartClock 1 PPS

and ghe GPSR 1 PPS signals. Units are seconds.

FFOM (Frequency Figure of Merit): The Frequency Figure of Merit

Vender Name

Product Serial No

F/W Version, H/W revision No

Command Description

RTRV-GPS-STS Displays the status of the GPSR.

Displays the latitude, longitude, and supplementary information of the

GPSR.



4.4.2 RRH Status Management

You can view the current status of the RRH and various supplementary information by

executing the RTRV-RRH-STS command.

Command Description

RTRV-RRH-STS Displays the status and various supplementary information of the RRH.

The following information is displayed.

CONNECT_BOARD_ID: ID of the board connected to the RRH.

CONNECT_PORT_ID: ID of the port connected to the RRH.

CASCADE_RRH_ID: Cascade ID of the RRH.

PATH_ID: Path ID of the RRH.

OPERATIONAL_STATE: Operation state of the resource.

PATH_STATE: Operation state of the path.

FW_MODE: Current execution mode of the FW image (0: user mode, 1: factory mode).

NUM_OF_FA: Number of FAs.

MAP_OF_FA1: FA1‟s mapping number.



FA1_ON_OFF: FA1‟s On/Off.



FA1_CH_BANDWIDTH [MHz]: Channel bandwidth of FA1.



FA1_TX_EARFCN: FA1‟s outgoing E-UTRA Absolute Radio Frequency Channel

Number (EARFCN) value.





FA1_RX_EARFCN: FA1‟s incoming E-UTRA Absolute Radio Frequency Channel








OPTIC_DELAY [ns]: Optic delay value.

TX_DELAY [ns]: TX delay value.

RX_DELAY [ns]: RX delay value.

LOOPBACK: Loopback on/off.

TX_ON_OFF: TX‟s On/Off.

TX_CONTROL: TX enable/disable value for the path.

RX_ON_OFF: RX‟s On/Off.

TEMP [C]: Temperature value.

TX_RF_POWER [dBm]: Output RF power.

RETURN_LOSS [dB]: Return loss value.

FA1_RSSI_IQ_LEVEL: FA1 RSSI Digital IQ level value.



FA1_TSSI_IQ_LEVEL: FA1 TSSI Digital IQ level value.



FA1_TX_ATTEN [dB]: FA1 TX attenuation value.





4.5 Link Status

Status management of the link (port) connected to the DU is performed by the main

processor in the system. If a fault occurs, the function receives the information from the

FM block and applies the status.

Command Description

RTRV-ELINK-STS Displays the link‟s status.

- ADMINISTRATIVE_STATE

- OPERATIONAL_STATE

- AVAILABILITY_STATUS

RTRV-ETH-INTF Displays the ETHERNET INTERFACE information for the link.

- INTERFACE NAME

- IPV4 address

- IPV4 Prefix length

- Gateway address

4.6 S1/X2 Status

Manages the SCTP and interface status for S1 and X2 respectively in eNB.

Command Description

RTRV-S1-STS Displays S1‟s status.

- SCTP_STATE

- S1AP_STATE

RTRV-X2-STS Displays X2‟s status.

- SCTP_STATE

- X2AP_STATE

4.7 PRB Usage Status

Displays the usage status of the physical resource block (PRB) for each cell in the eNB.

Command Description

RTRV-PRB-USG Displays the PRB usage for each cell.

- Total PRB usage for downlink

- Total PRB usage for uplink

- QCI_0-15 PRB usage for downlink

- QCI_0-15 PRB usage for uplink



4.8 Inventory Information

Manages the inventory information for the DU, RU, and environment devices.

Command Description

RTRV-INVT-INF Displays the resouece‟s inventory information.

Provides the HARDWARE VERSION NUMBER, VENDOR NAME, SERIAL

NUMBER, manufacturing date, INSTALL DATE, and FIRMWARE

VERSION information that are the inventory information of a resource.



CHAPTER 5. Diagnosis Functions

Diagnosis is a function that allows the operator to view the status of the system, such as Tx

power, VSWR, model, OCNS, loopback and BER; to check whether the system is working

properly using the corresponding command.

The blocks and interfaces tested by the TM are illustrated below.

Figure 5.1 TM and Test Performing Blocks and Interfaces

: A message used by the TM for DSP settings including OCNS and MODEL.

It is received by the RLC block and relayed to the DSP. Then the DSP issues a

response message for the OCNS and MODEL setup message. It is relayed by the RLC

block to the TM.

: The interface between the TM belonging to the Master OAM and the STM

operating within the ECP.

Main Board

Sub Board

TM

FM

Sub OAM

FPGA

STM

RLC

DSP

RRHs RRHs RRHs

F/W



: This indicates the interface used for obtaining loopback, BER and other data from

the FPGA register or setting the FPGA.

: The Req message relayed to the RRH for diagnosis execution. It is received by the

firmware and it returns the RRH data.

: The interface used for setting alarm generation/clearance according to the online

diagnosis execution results.

The diagnosis functions are divided into the following two categories, according to how

they are performed:

On-demand test: Performs diagnosis when the operator executes the test command.

On-line test: Automatically performs diagnosis according to the interval pre-set by the

system.

On-demand test

The following commands are provided for on-demand tests:

Command Description

TEST-XXX TEST-XXX is the type of command that carries out a diagnosis function.

MON-TEST The command for viewing the status of the test that is being set currently.

TERM-TEST The command for exiting the currently running test.

Below is the procedure for carrying out the test.

1) In the CLI command window of the LSM, execute the TEST-XXX command to begin

the test.

2) After executing the TEST-XXX command, check that the test is performed in the

response window.

3) Check the test result in the Event window of the LSM CLI.

On-demand Test

Command Test Result

TEST-EPING

TEST-IPING

TEST-TXPWR

TEST-VSWR

TEST-MODEL

TEST-OCNS

TEST-TRC-ROUTE

TEST-LB

TEST-BER

TEST-ETHLB

TEST-ANT

TEST-BATT

S2600 NOTIFY TEST RESULT



On-line test

When performing an online test, the operator can set the test options, such as test

allow/inhibit, test period and test start/end time, according to his needs. The following

commands are provided:

Command Description

CHG-XXX-INF Adds/changes the test settings for each item (xxx). The registered test

items can be retrieved using RTRV-XXX-INF.

RTRV-XXX-INF Retrieves the test settings registered by CHG-XXX-INF.

CHG-TEST-LIST Changes the registered on-line test.

CRTE-TEST-LIST Adds the scheduler for performing the on-line tests. It can register up to

50 schedulers (OT_ID). The operator can execute the CHG-XXX-INF

command to register TEST_ID and TI_ID first and then execute the CHG-

TEST-LIST command to register the on-line tests.

DLT-TEST-LIST Deletes the online test registered by the CRTE-TEST-LIST command.

(Currently running on-line test items cannot be deleted. They can be

deleted only after the STATE is modified to STOP_ONLINE using the

CHG-TEST-LIST command.)

RTRV-XXX-RSLT Retrieves the test results.

RTRV-TEST-LIST Retrieves the on-line test result registered by the CHG-TEST-LIST

command.

CHG-BTEST-SCH Registers the scheduler for the on-line test of the battery test. It can set

the test start time and execution period.

The following items are provided for online tests:

Item Description

EPING The external ping test that is used to diagnose the network connections

between the system and an external host.

IPING The internal ping test that is used to diagnose the IPC paths between the

master processor and other processors.

TXPWR The Tx power test that is used to diagnose the RAS transmission power

level.



5.1 External Ping Diagnosis

The external ping test is used to diagnose the network connections between the system and

an external host. In the external ping test, an Internet Control Message Protocol (ICMP)

packet is created and a ping test is run with this to monitor the performance of an external

interface (Ethernet or Gigabit Ethernet). The frame delay, frame delay min, max, avg, and

the frame loss are then provided as the test results.

When the operator performs the external ping test on an external interface and if it is found

that there is no packet loss from the test results, he can determine that the external interface

is normal. With regard to the test results, „delay‟ means the round trip time (the period of

time from the sent time to the received time). The operator can check the min, max, avg

and variance for packet delay.


Command Description

TEST-EPING Tests the network connections between the system and an external host

as an external ping test.

The external ping test creates an Internet Control Message Protocol

(ICMP) packet and runs a ping test to monitor the performance of an

external interface (Ethernet or Gigabit Ethernet). The frame delay, frame

delay min, max, avg, and frame loss are then provided as the test result.

If there is no packet loss from the external ping test result, the operator

can determine that the external interface operates normally. In the test

result, „Delay‟ represents the round trip time (the period of time from the

sent time to the received time). The operator can check the min, max,

avg and variance for the packet delay.

Command Execution Procedure

1) Select the TEST-EPING command in the TM folder on the CLI window, enter the

destination IP and parameter values, and then click the Exec button to start the test.

2) Check whether the TEST-EPING command is executed in the response window.

3) If the response is OK in step 2, view the test result in the event window.



5.1.1 External Ping Online Diagnosis

The commands to perform the external ping online diagnosis are as follows:

Command Description

CHG-EPING-INF Specifies or modifies the test target and other options prior to executing the

external ping online test. You can add an online test for the added test

items (TI: up to 10 TIs can be added) using CHG-TEST-LIST to execute the

external ping online test.

RTRV-EPING-INF Retrieves the test target and other options registered for executing the

external ping online test.

RTRV-EPING-RSLT Retrieves the external ping on-line test results.

The test results are stored as RESULT_ID (30) for each TI_ID (10), thus up

to 300 test results can be stored in total. More recent the test, closer to zero

the RESULT_ID value will be. The value will increase over time.


1) Select the CHG-EPING-INF command in the TM folder in the CLI window.

2) Enter the parameters required for the execution and click the Exec button.

The test item specified in this step can be checked using the RTRV-EPING-INF

command.

3) Select the CHG-TEST-LIST command, then add the TEST_ID and TI_ID specified in

step 2) to start the online test.

4) Execute the RTRV-EPING-RSLT command to check the execution results.



5.2 Internal Ping Diagnosis

The internal ping test is used to diagnose the Inter Processor Communication (IPC) paths

between the UAMA processor and other processors. The internal ping test performs a ping

test to the CPU corresponding to BOARD_TYPE and BOARD_ID (destination) specified

by the operator in the eNB‟s master board (UAMA). The test is successful if it receives a

ping echo reply; the result is evaluated as normal.


Command Description

TEST-IPING Diagnoses the Inter Processor Communication (IPC) path between the

UAMA processor and other processors as an internal ping test.

The internal ping test performs a ping test to the CPU corresponding to

the BD_TYPE and BD_ID (destination) the operator specified in the

eNB‟s master board (UAMA), and displays the ping test result. The test is

successful if a ping echo reply is received; the result is then evaluated as

normal.


1) Select the TEST-IPING command in the TM folder on the CLI window, enter the type

and ID of the destination board, and click the Exec button to start the test.

2) Check whether the TEST-IPING command is executed in the response window.


5.2.1 Internal Ping Online Diagnosis

The commands to perform the internal ping online diagnosis are as follows:

Command Description

CHG-IPING-INF Specifies or modifies the test target and other options prior to executing

the internal ping online test. You can add an online test for the added test

items (TI: up to 10 TIs can be added) using CHG-TEST-LIST to execute

the internal ping online test.

RTRV-IPING-INF Retrieves the test target and other options registered for executing the

internal ping online test.

RTRV-IPING-RSLT Retrieves the internal ping on-line test results.

The test results are stored as RESULT_ID (30) for each TI_ID (10), thus

up to 300 test results can be stored in total. The RESULT_ID of the most

recent test result will have a number closest to 0, which will increase over

time.




1) Select the CHG-IPING-INF command in the TM folder in the CLI window.


The test item specified in this step can be checked using the RTRV-IPING-INF

command.



4) Execute the RTRV-IPING-RSLT command to check the execution results.



5.3 Transmission RF Power Diagnosis

The Tx RF power test is used to measure the eNB transmission power level.

In the Tx power test, the operator can diagnose the Tx path of the RU by measuring the Tx

RF output, the RSSI level, and attenuation of the PAU.

The related command is as follows.

Command Description

TEST-TXPWR Executes the ondemand test to the Tx power item.

The Tx power test is used to measure the transmission power of the

Power Amp. Unit (PAU). During the Tx power test, the operator can

diagnose the PAU‟s Tx route by measuring the TX RF power and RSSI.

The measurement is performed at the PAU output port, where the RF

power is checked. And the result is reported to the operator.

If this command is executed successfully, the ondemand test result can

be verified, from Event window of the LSM CLI, through the notification

(NOTIFY TEST RESULT).

The conditions for processing the diagnosis result as NOK are as follows:

- If the status of the cell that performed the diagnosis is „Lock‟, the Tx

output will be turned off, and the diagnosis result will be processed as

NOK.

- If any of the paths operating in the PAU is abnormal, the diagnosis

result will be processed as NOK. (The number of the operating paths

can be verified by the result notification‟s „PATH_CNT‟.)

- If the PAU appears grown in the configuration but is powered off and is

not in operation, the diagnosis result will be processed as NOK.

If the diagnosis result is NOK, the following details must be verified.

- Verify if the PAU is connected and is powered on.

- Verify if the status of the cell is „Unlock‟.

- Check the PAU‟s alarm status.

- Verify if the status of the PAU is Tx Enable, Tx On, Fa On.


1) Select the TEST-TXPWR command in the TM folder in the CLI window, enter the

number of the cell to diagnose, and click the Exec button to start the test.

2) Check whether the TEST-TXPWR command is executed in the response window.




5.3.1 Tx Power Online Test

The commands to perform the Tx Power online diagnosis are as follows:

Command Description

CHG-TXPWR-INF Specifies or modifies the test target and other options prior to executing the

Tx power online test.

You can add an online test for the added test items (TI: up to 10 TIs can be

added) using CHG-TEST-LIST to execute the internal ping online test.

RTRV-TXPWR-INF Retrieves the test target and other options registered for executing the Tx

power online test.

RTRV-TXPWR-

RSLT

Retrieves the Tx power on-line test results.

The test results are stored as RESULT_ID (30) for each TI_ID (10), thus up

to 300 test results can be stored in total. The RESULT_ID of the most

recent test result will have a number closest to 0, which will increase over

time.


1) Select the CHG-TXPWR-INF command in the TM folder in the CLI window.


The test item specified in this step can be checked using the RTRV-TXPWR-INF

command.



4) Execute the RTRV-TXPWR-RSLT command to check the execution results.



5.4 VSWR Diagnosis

The Voltage Standing Wave Ratio (VSWR) test is used to measure the return loss at the

eNB output terminal antenna. In the VSWR test, the operator can identify the interfacing

status of the antenna by measuring the return loss (convertible to VSWR) at the final output

terminal of the RU.

When the VSWR test is performed, the return loss is measured for each path of a subcell.

The return loss always has a negative (-) dB value, because the reflected power is less than

the input power.

However, since it is a ratio measurement, it is normal that the absolute value is represented.


Command Description

TEST-VSWR Executes the ondemand Test to the VSWR item.

The Voltage Standing Wave Ratio (VSWR) test is used to measure the

return loss at a Power Amp. Unit‟s (PAU) output terminal antenna.

In the VSWR test, the operator can identify the interfacing status of the

antenna by measuring the return loss (convertible to VSWR) at the final

output terminal of the PAU. When performing the VSWR diagnosis, the

system measures the return loss for each path of the corresponding PAU

and reports the diagnosis result to the operator. The return loss always

has a negative (-) dB value because the reflected power is less than the

input power. However, since it is a ratio measurement, it is normal that

the absolute value is represented. Since the VSWR test compares the Tx

RF power with the RF power reflected from the antenna, it can only be

measured if the TX RF power is above a given level.

If this command is executed successfully, the ondemand test result can

be verified, from Event window of the LSM CLI, through the notification

(NOTIFY TEST RESULT).

The conditions for processing the diagnosis result as NOK are as follows:

- If the status of the cell that performed the diagnosis is „Lock‟, the Tx

output will be turned off, and the diagnosis result will be processed as

NOK.

- If any of the paths operating in the PAU is abnormal, the diagnosis

result will be processed as NOK. (The number of the operating paths

can be verified by the result notification‟s „PATH_CNT‟.)

- If the PAU appears grown in the configuration but is powered off and is

not in operation, the diagnosis result will be processed as NOK.

If the diagnosis result is NOK, the following details must be verified.

- Verify if the PAU is connected and is powered on.

- Verify if the RF power output is normal. (Verify if the status of the cell is

„Unlock‟.)

- Verify if the antenna is properly connected.




1) Select the TEST-VSWR command in the TM folder in the CLI window, enter

BOARD_ID, PORT_ID, and CASCADE_ID of the RRH to test, and click the Exec

button to start the test.

2) Check whether the TEST-VSWR command is executed in the response window.




5.5 OCNS

Similar to establishing the cell plan for the eNB, when the downlink wireless environment

must be analyzed, the noise simulation function analyzes the wireless environment by

setting the type and part of the modulation of the Other Cell Noise Simulator (OCNS), and

then by setting a virtual call for each subcell through the settings above.

The following commands are used for enabling and disabling the OCNS.

Command Description

TEST-OCNS In the event an analysis of the forward link wireless environment is

required, such as for the cell planning of the base station, this command

sets up a virtual call and generates signals to enable network design of

the base station and analysis of forward link wireless environment

through the RF characteristics and forward link power measurements.

To set or clear the Orthogonal Channel Noise Simulator (OCNS), use the

following commands:

- TEST-OCNS: Sets the OCNS for a specific cell.

- MON-TEST: Retrieves the status of the test currently in process.

- TERM-TEST: Exits the test that is being performed.

MON-TEST Retrieves the test that is being performed in the eNB. The tests that can

be retrieved with this command are the commands related to the TM.

Note that the online diagnosis will not be included in the monitor test

since the registration status of the corresponding scheduler can be

retrieved with the RTRV-TEST-LIST command. Each diagnosis command

will be registered in the monitor test list at the time of its execution; the

command will be removed from the list at the time of its completion, when

the result notification message is transmitted. The removed command

cannot be retrieved by the monitor test command. If there is no diagnosis

command currently in process, „NO_DATA‟ will be displayed.

TERM-TEST Exits the test currently in process in the eNB.The tests that can be

terminated with this command are the commands related to the TM.

Note that the online diagnosis will not be included in the terminate test

since the corresponding scheduler can be terminated with the CHG-

TEST-LIST command. The MON-TEST command can be used to retrieve

the command currently in process and the invocation ID. The invocation

ID can be used to terminate a command currently in process.

(*Related command: MON-TEST)


1) Select the TEST-OCNS command in the TM folder in the CLI window, enter the cell

number to test and the parameters, and click the Exec button to start the test.

2) Check whether the TEST-OCNS command is executed in the response window.


4) To stop the command execution, select the TERM-TEST command and enter the

invocation ID to terminate the command.

CF) The status of the TEST-MODEL that is currently set can be retrieved by

executing the MON-TEST command.



5.6 Model Diagnosis

Performs the conformance test by artificially generating traffic and then measuring output

properties. The DU (DSP) specifies the property items defined in the standard (E-UTRA

test models) for RF property tests and then the RF outputs are tested on the DSP.

Performs the model test for the eNB.

The following commands are used to set and clear the model test.

Command Description

TEST-MODEL Generates a traffic in order to carry out the conformance test and

measures the output characteristics with a measuring instrument.

To perform the RF characteristics test in the DU (DSP), it sets the

characteristics criteria (E-UTRA test models) as defined in the standard

specification and verifies whether the DSP processes the RF output

normally. To set or clear the model test, use the following commands:

- TEST-MODEL: Sets the model test for a specific cell.

- MON-TEST: Retrieves the status of the test currently in process.

- TERM-TEST: Retrieves the test currently in process.

MON-TEST Retrieves the test that is being performed in the eNB. The tests that can

be retrieved with this command are the commands related to the TM.

Note that the online diagnosis will not be included in the monitor test

since the registration status of the corresponding scheduler can be

retrieved with the RTRV-TEST-LIST command. Each diagnosis command

will be registered in the monitor test list at the time of its execution; the

command will be removed from the list at the time of its completion, when

the result notification message is transmitted. The removed command

cannot be retrieved by the monitor test command. If there is no diagnosis

command currently in process, „NO_DATA‟ will be displayed.

TERM-TEST Exits the test currently in process in the eNB.The tests that can be

terminated with this command are the commands related to the TM.

Note that the online diagnosis will not be included in the terminate test

since the corresponding scheduler can be terminated with the CHG-

TEST-LIST command. The MON-TEST command can be used to retrieve

the command currently in process and the invocation ID. The invocation

ID can be used to terminate a command currently in process.

(*Related command: MON-TEST)


1) Select the TEST-MODEL command in the TM folder in the CLI window, enter the cell

number to test and the parameters, and click the Exec button to start the test.

2) Check whether the TEST-MODEL command is executed in the response window.


4) To stop the command execution, select the TERM-TEST command and enter the

invocation ID to terminate the command. The status of the TEST-MODEL that is

currently set can be retrieved by executing the MON-TEST command.



5.7 Trace Route Diagnosis

The trace route test is used to diagnose the network path between the system and an

external host.

When performing the trace route test, the operator can enter the destination IP address and

view the hop information between the NE and destination, the gateway and/or route

address for each hop and the delay time; can identify a problematic network in terms of the

external path.

There are several available options in the trace route test. The Differentiated Services Code

Point (DSCP) value or source IP address can be specified.

The test results are evaluated as normal only if all hops along the path to the destination are

normal.


Command Description

TEST-TRC-ROUTE Diagnoses the network path between the system and an external host as

a trace route test. When performing the trace route test, the operator can

enter the destination IP address and view the hop information between

the NE and destination, the gateway and/or route address for each hop

and the delay time to identify the network that has a problem with the

external path. Optionally, you can designate the destination IP version

and the Differentiated Services Code Point (DSCP) value for the trace

route test. The test result is evaluated as normal if all hops along the path

to the destination are normal. If the test result is NOK, it means that the

path to the target is disconnected.


1) Select the TEST-TRC-ROUTE command in the TM folder on the CLI window, enter

the destination IP and parameters, and then click the Exec button to start the test.

2) Check whether the TEST-TRC-ROUTE command is executed in the reply window.




5.8 Loopback Diagnosis

The loopback test is used to diagnose the communication path of the separate PPH

remotely.

When performing the loopback test, the operator can select the DU‟s MGT, the RU‟s (RF

Unit) MGT or the RU Mapper to verify whether the path has an error.

In order to execute the loopback test, ADMINISTRATIVE_STATE of the cell being tested

must be Lock. RTRV-CELL-CONF: Checks the cell state. If the state is Unlock, it changes

the state to Lock (Use Cell Management tab in the LSM).

Note that changing the cell state to Lock also turns RRH output off, terminating all running

services.

When the loopback test command is executed, the specified port on the ECP (channel card)

sends the IQ test pattern to the RRH and receives a response to test the path. Therefore, the

board type should be set to ECP.

Loopback test for cascade RRH paths can be performed by entering the cascade ID.

All RRHs belonging to the cascade connection area are configured for loopback and the IQ

test pattern is looped back at the specified RRH for diagnosis.


Command Description

TEST-LB Executes the ondemand test to the DU-RU loopback item. The DU-RU

loopback test verifies the optic link section by sending the packet from

the channel card‟s CPRI port toward the RU, receiving the response,

then comparing it with the packet sent. To execute the loopback

command, the target cell must be in „Lock‟ state. (The loopback

command cannot be processed while the cell is operating and providing

service.) You can retrieve the status of the cell in the Cell Management

window of the LSM. If the status of the cell is „Unlock‟, change it to „Lock‟

and continue the test.

If the TEST-LB command is executed successfully, the ondemand test

result can be verified, from Event window of the LSM CLI, through the

notification.


1) Select the TEST-LB command in the TM folder on the CLI window, enter the

parameters, and click the Exec button to start the test.

2) Check whether the TEST-LB command is executed in the reply window.




5.9 Bit Error Rate Diagnosis

The link Bit Error Rate (BER) test function tests physical quality of optic links. It returns

the BER value at every result reporting interval and, when the test is complete, it returns

the BER value of the link.

The DU periodically relays the BER measurement command and receives the response

message from the target for measuring and displaying BER values.

The BER measurement section is as follows:

Figure 5.2 BER measurement section

If ECP, RRH or IIU is selected for BOARD_TYPE, enter the board ID and optic port.

If RRH is selected for BOARD_TYPE, enter the board, port and cascade ID.

For ECP, only the UL BER is measured. For terminal RRH, only the DL BER is

measured.

The BER measurement result for each section is periodically relayed through the

notification message, and when the test ends, the final results are relayed through the

notification message.


Command Description

TEST-BER Executes the Bit Error Rate (BER) ondemand test on the DU-RU CPRI

section. The BER test verifies the error rate by calculating the Bit

Interleaved Parity (BIP) of the channel card‟s CPRI port. If this command

is executed successfully, the ondemand test result can be verified, from

Event window of the LSM CLI, through the notification. The test is

performed for „Interval‟ time period (minutes), „Iteration‟ times. The error

counts are accumulated until the test ends.


1) Select the TEST-BER command in the TM folder in the CLI window, enter the


2) Check whether the TEST-BER command is executed in the response window.


L9CA

#0

#1

#2

#5

RRH #2-2 RRH #2-0 RRH #2-1

Area0 Area1 Area2

(DL)

(UL)

Measurement Point2_Tx

Measurement Point2_Rx

(DL)

(UL)



(DL)

(UL)





5.10 Ethernet Loopback Function

The Ethernet loopback test performs the loopback test for the EFM function as defined in

the IEEE802.3ah standard. This function can be performed only if the test target NE

supports the EFM function.

When the operator executes the Ethernet loopback command, the discovery function is

performed to check that the EFM function is in active mode. If the discovery process fails

or if the EFM is in passive mode, NOK is returned for the command and the loopback test

is not performed.


Command Description

TEST-ETHLB Executes the loopback test on the EFM function as defined in the IEEE

802.3ah standard specification. The EFM verifies the path between the

systems directly connected to the eNB. In order to execute the Ethernet

loopback command, the discovery function must be carried out.

This command can only be triggered in the EFM active mode.

If the discovery function fails or the EFM is in passive mode, this command

is processed as NOK and the loopback test will not be performed.


1) Select the TEST-ETHLB command in the TM folder in the CLI window, enter the


2) Check whether the TEST-ETHLB command is executed in the response window.




5.11 RET Device Test Remote Electrical Tilting (RET) adjusts the interference with neighbor cells or coverage of

the current cell by adjusting down tilt of the MIMO antenna connected to the RRH.

CHG-RET-INF is used for remote and efficient adjustment of the antenna output beam.

Precise tilt adjustment is possible by using electrical means.

The TEST-ANT command is used for checking operation status of the RET.

Performs the calibration test on the RET device. ALD_ID and ANT_ID as well as

BOARD_ID, PORT_ID, and CASCADE_ID are entered to set a specific antenna.

When an antenna receives the calibrate ANT command, it tests automatically moving the

tilt and steer angles from minimum to maximum. At the start of the antenna test, the start

notification message is sent to the LSM and at the end, the test result notification message

is sent.


Command Description

TEST-ANT Executes the calibration test on the RET device. To specify a specific antenna,

the following mandatory parameters must be provided: BD_ID, PORT_ID,

CASCADE_ID, as well as ALD_ID and ANT_ID. The antenna that receives the

calibrate ANT command will perform the test by automatically varying its tilt and

steer angles from min to max.

A start notification message will be sent to the LSM when the antenna test starts,

and a test result notification message will be sent upon the completion of the test.

CHG-RET-INF Sets or changes the tilt and steer information of the RET device.

The RET is an antenna controlling device that interoperates with the RRH.

One RET can connect two Antenna Line Devices (ALD), and one ALD can

connect two antennas. In order to specify a specific RRH and ALD to control the

antenna, the BD_ID, PORT_ID, CASCADE_ID, ALD_ID and ANT_ID

information must be provided.

RTRV-RET-INF Retrieves the tilt and steer information of the RET device. The CHG-RET-INF

command outputs the registered RET Information. The RET is an antenna

controlling device that interoperates with the RRH. One RET can connect two

Antenna Line Devices (ALD), and one ALD can connect two antennas.

To specify a specific RRH to view the information of the antenna, the

BOARD_ID, PORT_ID and CASCADE_ID information must be provided.

The ALD_ID and ANT_ID fields are optional. If omitted, the information of every

ALD and antenna connected to the RRH will be can be retrieved.


1) Select the TEST-ANT command in the TM folder in the CLI window, enter the


2) Check whether the TEST-ANT command is executed in the response window.

3) If the response is OK in step 2, check the test result in the event window

(the START_NOTI message is displayed when the test starts and the RESULT_NOTI

message is displayed when the test ends).



5.12 Battery Test

The battery test provides the function to perform the battery discharge test through the

EAIU4-U. When the operator executes the command, the battery‟s test mode value will be

changed to „under test‟. It will revert to „normal‟ when the test is completed. The operator

can verify the current battery‟s test mode information with the RTRV-EAIU-STS command.

Only one instance of the battery test can be executed at a time. If a battery test is already

running, the battery test executed later will fail.

The related commands is as follow:

Command Description

TEST-BATT Executes the designated rectifier‟s battery test. Once the battery test starts,

the battery will perform the discharge test. When the battery test is

completed, the results, such as quality, etc. will be sent to the LSM.

The battery test can be terminated with the term test.

The TEST-BATT command is executed as the following procedure:

1) Select the TEST-BATT command in the TM folder on the CLI window, enter the


2) Check whether the TEST-BATT command was performed in the reply window.

3) If the response in step 2) is OK, retrieve the test result on the event window.

Refer to the command description for the details on the parameter.

5.12.1 Battery Test Online Diagnosis

In addition to the TEST-BATT command, the operator can also register the test schedule

with the CHG-BTEST-SCH command for a periodic execution of the battery test.

The commands to perform the battery test online diagnosis are as follows:

Command Description

CHG-BTEST-SCH Sets or changes the battery test schedule information. After the command is

executed, a test will be performed on the battery mounted in the DU of the

eNB system in accordance to the registered schedule.

The test will be initiated at each period (daily basis), at the designated time.

The battery quality value will be sent to the LSM upon the completion of

each test.

RTRV-BTEST-SCH Retrieves the battery test schedule registered with the CHG-BTEST-SCH

command.



The CHG-BTEST-SCH command is executed as the following procedure:

Select the CHG-BTEST-SCH command in the TM folder on the CLI window, enter the

parameters, and click the Exec button to register the battery test schedule.

Check whether the CHG-BTEST-SCH command was performed in the reply window.

If the schedule reaches the registered period, retrieve the test result on the event window.



5.13 Cell Traffic Trace

The cell traffic trace function provides the information for the flow and communication

status of all calls activated on the cell specified by the operator. This function not only

allows the system to operate smoothly since the operator can find out the flow of the

signaling data in the cell, but also provides the data necessary for analyzing dropped calls,

or for locating a problem in a malfunctioning UE. It can be enabled by cell. When enabling

the function, the following parameters should be set. (Note that MCC, MNC, Trace ID, and

TCE Address are automatically set when using the GUI.)

MCC

MNC

Trace ID

List of Interfaces

Trace Depth

Cell Number

TCE Address

Item Description

MCC Mobile Country Code

Three digit number. 0 to 9 or F can be entered.

MNC Mobile Network Code

Three digit number. 0 to 9 or F can be entered.

Trace ID Specifies a unique value in the same network.

- range: 0~16777215

List of Interfaces Multiple interface lists can be specified to collect trace data.

- Uu (MS-eNB)

- X2 (eNB-eNB)

- S1 (eNB-EPC)

If no interface list is specified, traces all interfaces.

Trace Depth Level for collecting trace data can be specified.

- Minimum

- Medium

- Maximum

- Minimum Without Vendor Specific Extension

- Medium Without Vendor Specific Extension

- Maximum Without Vendor Specific Extension

Cell Number Cell number of 0 to 5 allocated to each eNB

TCE Address Server address to which trace data will be transmitted lastly



The commands below are used for setting and releasing cell traffic trace.

Command Description

START-TRC Activates the cell traffic trace.

STOP-TRC Deactivates the cell traffic trace.

RTRV-TRC Retrieves the information of the activated cell traffic trace.

Cell Traffic Trace Activation

To check the result of cell traffic trace, you must start to trace through a command or GUI

in the LSM.

Below is the procedure for starting cell traffic trace using GUI.

1) Log in to the LSM.

2) Select Performance Call Trace from the menu.

Figure 5.3 Selecting the Call Trace Menu


4) Click Refresh to check that no cell traffic trace is currently registered and click Add to

register the cell traffic trace.

Figure 5.4 Registering Cell Traffic Trace



5) When the registration is complete, you can see that a trace list is created.

Since the information is stored in the database when cell traffic trace is activated, the cell

traffic trace remains even when the system resets.

Restriction When Setting Cell Traffic Trace

Only one cell traffic trace is activated in an eNB.

Retrieving Trace List

The trace list view function displays the cell traffic trace currently active in the eNB and

checks the parameters entered when activating the cell traffic trace.

Below is the procedure for viewing a trace list using GUI.

1) Log into the LSM and select Performance Management Call Trace.

2) Select an eNB in target.

3) You can check the currently activated trace list.

Cell Traffic Trace Deactivation

When the cell traffic trace function is deactivated, signaling data report for all calls within

the cell is stopped.

Below is the procedure for releasing the added cell traffic trace using the GUI.



3) Select the retrieved trace list and select Delete to delete it.

4) You can see that the trace list is deleted (deactivated).

Cell Traffic Trace Result Reporting

Provides information for the flow of all the calls, and the communication status in the cell

where the cell traffic trace is activated.

Below is the procedure to retrieve the result data for the added cell traffic trace.



3) Select the retrieved trace list and press the Start button. (Or, double-click the trace list.)

4) Access the call.

When the steps above are performed, you can check the result of the cell traffic trace in the

GUI, as shown in the figure below.



Figure 5.5 Retrieving Cell Traffic Trace Result

The following describes the screen elements present in the call traffic trace window.

: Allows storing or printing of the signaling trace data received. It also allows you to

delete the trace data in the current window. In this case, the trace data disappears only

from the window but the original data is saved. The Pause button is used for viewing

detailed values for each data set (see ).

: Illustrates the signaling trace data received.

: Displays the start time of the signaling trace data received.

: Displays the details of each trace data set received. You must stop the trace by

clicking the Pause button in before selecting the data to view it.



5.14 EtherOAM

The EtherOAM (EFM) determines the correctness of the path between the systems directly

connected to the eNB, as defined in the IEEE 802.3ah standard specification. The EFM

provides the Ethernet link monitoring, and performs the discovery, remote fault indication,

link monitoring and remote loopback functions through the Ethernet OAM Protocol Data

Unit (OAMPDU) for the maintenance of geographically remote Ethernet networks.

(Refer to the separate diagnosis command TEST-ETHLB for the remote loopback.)

The operator can retrieve or change the related parameters with the CHG-ETHOAM-

CONF/RTRV-ETHOAM-CONF commands.


Command Description

CHG-ETHOAM-CONF Processes the setting of the EFM function as defined in the IEEE

802.3ah standard specification.

RTRV-ETHOAM-CONF Retrieves the PLD ETHOAM setting. The operator can retrieve the

EFM related parameters previously modified with the CHG-ETHOAM-

CONF command.

The CHG-ETHOAM-CONF command is executed as the following procedure:

1) Select the CHG-ETHOAM-CONF command in the TM folder on the CLI window,

enter the parameters, and click the Exec button to start the test.

2) Check whether the CHG-ETHOAM-CONF command was performed in the reply

window.

3) If the response in step 2) is OK, run the RTRV-ETHOAM-CONF command to verify if

the modified values are successfully updated.



CHAPTER 6. Grow and Degrow

Grow and degrow functions allow growing or degrowing of eNBs and cells for increasing

the system capacity or optimizing the network efficiency by restructuring the system.

The LTE system provides the following grow/degrow functions.

Grow/Degrow Type is as follows.

Grow/Degrow Type Description

eNB grow/degrow eNBs add/detele

Cell grow/degrow Cell add/de; ete

RRH grow/degrow RRH add/delete

Grow/degrow is accompanied by the physical action of adding or removing a rack or

device. ENBs and RRHs are grown/degrown. When growing/degrowing cells, RRHs can

be added or removed depending on the configuration of the base station.

Grow/Degrow Features

The grow/degrow does not affect other systems that are operating. When growing and

degrowing, services to other system are not stopped.

For degrow, it is performed when the existing service is completed.

After growing eNB, the grown resource is loaded and initialized automatically.

When growing, the operator can change the system configuration in the status, so that

service is not performed.

To perform degrow, only the existing services persist and new service must not be

accepted. To do so, before degrowing and allowing the eNB or cell to degrow, select

the UI menu and change the Administrative State (Locked/Unlocked/Shutting Down)

to Shutting Down. Then, the eNB or cell in the Shutting Down status will be changed

to the Lock status automatically when the currently running services are exited.

The operator can then degrow the eNB.



Grow/Degrow Features

Existence of the eNB or cell is determined by the EQUIP or NOT EQUIP status value, and

the Administrative State is indicated as LOCKED, UNLOCKED, or SHUTTING DOWN.

The details are as follows:

LOCKED: This is an intermediate status that occurs when growing the system.

In this status, the system is equipped in the PLD in the software, but the direct call

service is not performed.Note that the loading, fault, and configuration management

functions operate normally in LOCKED state. In this state, the configuration and

operation data related to the system grow has been modified so that the data is used by

the block that requires it.

In this state, the operator can only delete eNB or cell and can change it to the

UNLOCK state so that service can be provided.

UNLOCKED: When system grow is complete, eNB or cell on the PLD is in EQUIP

state and call service is available.In UNLOCKED state, the commonly used wireless

environment related data has been updated in related systems as well.

SHUTTING DOWN: A transitional state in the system degrowth process. In this state,

the grown resources on the PLD continue to offer the call service of the previous

UNLOCKED state but does not offer any new call services. When the currently

running services are completed, this state is automatically switched to the LOCKED

state.

EQUIP/NOT EQUIP: The NOT EQUIP state of the processor or device indicates that

there is no operation data in the PLD in the software. If system grow is performed in

this state, the state of the processor or device is changed to the EQUIP state and the

operation data is created in the PLD in the software.

In EQUIP state, the operator can change the cell status to LOCKED, UNLOCKED, or

SHUTTING DOWN.



Figure 6.1 Grow/Degrow State Transition Diagram

UNLOCKED SHUTTING

DOWN

LOCKED

EQUIP

- LOCKED: Resource block state/call restricted

- UNLOCKED: Resource unblock state/call allowed

- SHUTTING DOWN: New calls restricted and existing calls

maintained Switch to LOCKED state when existing calls end

NOT_EQUIP



6.1 eNB Grow/Degrow

6.1.1 eNB Grow

The eNB growth can be performed in two ways as follows:

From the main window of the LSM, select Configuration -> Grow.

From the main window of the LSM, right-click on the tree viewer.

The following table shows the parameters entered by the operator to grow the eNB.

(M: Mandatory, O: Option, F: Fixed)

Input Parameter Mandatory/Optional/

Fixed Description

Group M Network group to which the grown eNB belongs

Type M eNB system type

Version M Software version for the grown eNB

System ID M ID of the eNB to be grown

System Name M Name of the eNB to be grown

Additional Info O Additional information on the operator‟s eNB

MME IP Info O MME IP version, IP address

Bandwidth M Bandwidth for the grown FA (carrier)

Cell Info M Cell configuration for the eNB to be grown

PCI auto allocation O PCI auto allocation option (SON option)

Initial neighbor auto

allocation

O Initial neighbor auto allocation option (SON option)

RACH Optimization O RACH optimization option (SON option)

CellNum F Cell number to be grown

PCID M Physical cell ID setting

- PCI auto allocation ON: Requires no operator

configuration

- PCI auto allocation OFF: Requires operator

configuration

DlAntCount O Tx antenna count

UlAntCount O Rx antenna count

TAC O Tracking area code

EAID O Emergency area ID

Latitude O Latitude information

Longitude O Longitude information



(Continued)


Fixed Description

RootSequence M Root sequence index

- RACH optimzation ON: Requires no operator

configuration

- RACH optimzation OFF: Requires operator

configuration

HighSpeedFlag O Unrestricted set (FALSE)/restricted set (TRUE)

option

ZeroCorrelZone O Zero correlation zone setting

eNB LOCKED

The eNB locked state is available from the Unlocked or Shutting Down state.


Fixed Description

ManagedElement

- administrativeState

M The grow/degrow state (administrative state) is

entered as Locked.

eNB UNLOCKED

The eNB Unlocked status can be switched from the Locked or Shutting Down state.


Fixed Description

ManagedElement



entered as Unlocked.

eNB SHUTTING DOWN

The eNB Shutting Down state can be switched from the Unlocked or Locked state.


Fixed Description

ManagedElement



entered as Shutting Down.



6.1.2 eNB Degrow

The eNB degrowth can be performed in two ways as follows:

From the main window of the LSM, right-click on the map viewer, then select NE

Degrow.

From the main window of the LSM, right-click on the tree viewer, then select NE

Degrow.

The eNB degrow can be changed only in the Locked status. The operation data of the PLD

is deleted.



6.2 CELL Grow/Degrow

6.2.1 CELL Grow

The cell growth can be performed as the following the procedure:

From the main window of the LSM, select Configuration Cell, select the cell to grow,

set the parameters, then click OK.


Fixed Description

Cell Info M Cell number to be grown

PCID M Physical cell ID setting

- PCI auto allocation ON: Requires no operator

configuration

- PCI auto allocation OFF: Requires operator

configuration

DlAntCount O Tx antenna count

UlAntCount O Rx antenna count

TAC O Tracking area code

EAID O Emergency area ID

Latitude O Latitude information

Longitude O Longitude information

RootSequence M The first logical root sequence index value used

when creating random preamble

(Allocates a different value from that of an

adjacent cell)

- RACH optimzation ON: Requires no operator

setting

- RACH optimzation OFF: Requires operator

setting

HighSpeedFlag O Unrestricted set (FALSE)/restricted set (TRUE)

option

ZeroCorrelZone O The zero correlation zone used when creating a

random preamble

Cell Locked

The Cell Locked state can be switched from the Unlocked or Shutting Down state.


Fixed Description

CellEquipmentConf



entered as Locked.



CELL UNLOCKED

The Cell Unlocked state can be switched from the Locked or Shutting Down state.


Fixed Description

CellEquipmentConf



entered as Unlocked.

CELL SHUTTING DOWN

The Cell Shutting Down state can be switched from the Unlocked or Locked state.


Fixed Description

CellEquipmentConf



entered as Shutting Down.

6.2.2 CELL Degrow

The cell degrowth can be performed using the following the procedure:

From the main window of the LSM, select Configuration Cell, select the cell to degrow,

then click OK.

The cell degrow can be switched only in the Locked state.



6.3 RRH Grow/Degrow

6.3.1 RRH Grow

The command for RRH growth is as follow:

Command Description

CHG-RRH-CONF Changes the RRH growth/degrowth and configuration information.

The operator can select the RRH to modify by providing the

CONNECT_BOARD_ID, CONNECT_PORT_ID and CASCADE_RRH_ID

parameters. After connecting the RRH to the DU, the operator can execute

the command to set the STATUS parameter to EQUIP and perform the

growth of the corresponding RRH to allow it to be controlled by the system.

Conversely, the operator can set the STATUS parameter to N_EQUIP to

degrow the corresponding RRH.

Up to 6 RRHs can be grown for each cascade connection.

Growing is possible by switching the CHG-RRH-CONF state to EQUIP.


Fixed Description

connectBoardId M Specifies the board ID connected to the RRH to be

grown.

connectPortId M Specifies the port ID within the board ID connected

to the RRH to be grown.

cascadeRrhId M Specifies the cascade ID of the RRH to be grown.

status M Specifies EQUIP/N_EQUIP for RRH grow/degrow.

Use EQUIP when growing.

6.3.2 RRH Degrow

The command for RRH degrowth is as follow:

Command Description

CHG-RRH-CONF Changes the RRH growth/degrowth and configuration information.

The operator can select the RRH to modify by providing the CONNECT_

BOARD_ID, CONNECT_PORT_ID and CASCADE_RRH_ID parameters.

After connecting the RRH to the DU, the operator can execute the command

to set the STATUS parameter to EQUIP and perform the growth of the

corresponding RRH to allow it to be controlled by the system. Conversely,

the operator can set the STATUS parameter to N_EQUIP to degrow the

corresponding RRH.



RRH degrowing is possible by changing the state of CHG-RRH-CONF to N_EQUIP.


Fixed Description

connectBoardId M Specifies the board ID connected to the RRH to be

degrown.

connectPortId M Specifies the port ID within the board ID connected

to the RRH to be degrown.

cascadeRrhId M Specifies the cascade ID of the RRH to be degrown.

status M Specifies EQUIP/N_EQUIP for RRH grow/degrow.

Use N_EQUIP when degrowing.



CHAPTER 7. Self Organizing Network

(SON)

The SON function allows automatic configuration, update, and optimization of the system

parameters during system operation. The operator can turn individual SON functions on/off

per cell or eNB.

Figure 7.1 SON Function in Action

eNB

UAMA (UMP)

L8HU (RRH)

SON

Notify Report

Measurement Configuration

Measurement

Report

LSM

UE

ES Mode Change



The LTE system provides the following individual SON functions.

Detailed Function

of the SON Description

SE Self Establishment

eNB is initialized automatically.

ANR Automatic Neighbor Relation

Each cell of eNB adds or deletes the neighbor list automatically.

PCI Physical Cell ID auto-configuration

Each cell of eNB sets the PCI through the LSM automatically.

RACH Random Access Channel optimization

Each cell of eNB sets the Root Sequence Index of the RACH parameter

through the LSM automatically.

ES Energy Savings

Each cell of eNB operates in Energy Saving mode according to the

specified schedule.

SO Self Optimization

The self optimization function includes automatic compensation for RRH

optic delay.

ICIC Inter-Cell Interference Coordination (TBD)

MRO Mobility Robustness Optimization (TBD)

MLBO Mobility Load Balancing Optimization (TBD)

CNC Coverage and Capacity optimization (TBD)

The following table shows the system commands to change and retrieve the On/Off control

of the SON functions.

Command Description System Type

CHG-SONFN-CELL Changes the SON function cell control flag. ALL

RTRV-SONFN-

CELL

Retrieves the SON function cell control flag. ALL

CHG-SONFN-ENB Changes the SON function eNB control flag. ALL

RTRV-SONFN-ENB Retrieves the SON function eNB control flag. ALL



7.1 SE

When installing the LTE system, the Self Establishment (SE) function allows the eNB to

perform initialization automatically to provide convenience for operation of the LTE

system. This function is turned on by default.

The SE function is performed through the following processes.

Figure 7.2 eNB Self Establishment Process

1) The eNB hardware installation is performed.

2) After power on, the eNB hardware test (Power On Self-Test) is performed.

3) When the hardware test is complete, the initial configuration parameter is entered by

the operator.

Initial input parameterA: eNB ID

4) The Self-Configuration policy is determined. The SC policy determines automatic

configuration or manual configuration of the SC.

SC Enable: Automatic configuration

SC Disable: Manual configuration

eNB DHCP Server

LSM eNBs EPC

1) Hardware Installation

2) Hardware Test (POST)

3) Initial Input Parameter

4) Self-Configuration Policy Decision (enable/disable)

5) eNB/LSM IP Address Acquisition

6) eNB Registration

7) Self-Configuration Policy/Software Profile Download

8) Software Version Check

9) Software Download and Installation

10) eNB Authentication

11) Configuration Data Download and Installation

12) SCTP S1 Setup

13) SCTP X2 Setup

14) Self-Test Report - POST Result - S1/X2 Setup State - Inventory Information - eNB State (Cell Operation State)

15) In Service

1. Boot Sequence

2. eNB/LSM IP Acquisition & eNB Configuration

3. Service Preparation

4. In Service



5) The eNB and LSM IP addresses are obtained.

If SC is enabled, the eNB obtains its IP address and the LSM IP address from the

DHCP server. The eNB and LSM IP addresses are obtained through the DHCP

service. The eNB IP address is given as the response to the request by the DHCP

service; the LSM IP address is given through the option field of the DHCP response

message.

If SC is disabled, the eNB and LSM IP addresses are manually entered.

6) The eNB performs the registration procedure to the LSM that manages the eNB itself.

This procedure is performed together when performing the cold start from the eNB in

step 10.

7) The eNB downloads the software list from the LSM.

8) The eNB checks the software version.

9) The eNB downloads the software from the LSM and installs it.

10) The LSM authenticates the eNB. After the eNB loads the software, the eNB sends the

cold start message to the LSM for the first time. This message contains the eNB ID,

eNB IP address, and software version information. When the eNB sends the eNB ID

managed by the LSM, the configuration data file information is provided to the eNB.

11) The eNB downloads the configuration data from the LSM and installs it.

12) The eNB performs the S1 setup with the MME.

13) The eNB performs the X2 setup with neighbor eNBs.

14) The eNB reports the Self-Test result to the LSM.

POST Result

S1/X2 Setup status

Inventory Information report

eNB status (Cell Operation State) report

15) The LSM checks the Self-Test result and determines whether to perform the In-service.



7.2 ANR

The Automatic Neighbor Relation (ANR) function ensures convenient operation of LTE

system by providing automatic addition/removal of neighboring cells for each cell of the

eNB during installation or operation.

7.2.1 Initial NRT

When installing the base station initially, the initial NRT function configures the initial

neighbor base station necessary for setting the PCID, referring to the latitude/longitude

information of the base station that the LSM manages.

To set On/Off for this function, change it on the son.pcid flag of the son.properties file in

the /home/lsm/aceman/data/properties/project directory in the LSM server. Setting On/Off

through the GUI will be provided in the future.

Below is the procedure for performing the Initial NRT.

1) Enter the location information of the base station in the RUConf latitude and longitude,

and perform grow in the Base Station Grow window.

Figure 7.3 Base Station Grow Window (Initial NRT)

2) After grow is performed, check the success of the Initial NRT through the Event

Window.



Figure 7.4 Event Window (Initial NRT)

7.2.2 ANR through UE Measurement

The automatic neighbor relation function through UE measurement is used for adding

neighbors via the LSM or the UE measurement in the following cases:

When operating the base station

When performing UE handover after initial base station installation

When the source cell lacks the target cell neighbor information

This function can be turned on/off using the CHG-SONFN-CELL command.

The CHG-SONFN-CELL command has the following ANR_ENABLE field parameter

values:

sonFuncOff: The ANR function is not performed.

sonManualApply: NR deletion (X2 based), handover blacklist addition according to

NR priority level and NRT recovery are performed automatically. Note that NR

deletion or blacklist addition requires user confirmation.

sonAutoApply: NR deletion (X2 based), handover blacklist addition according to NR

priority level and NRT recovery are performed automatically.

The system commands related to ANR of SON are as follows.


CHG-SON-ANR Changes the SON ANR parameters. ALL

RTRV-SON-ANR Retrieves the SON ANR parameters. ALL

CHG-NBR-EUTRAN Command

The operator can set whether a cell can be deleted by setting the

IS_REMOVE_ALLOWED parameter to True or False using the CHG-NBR-

EUTRAN command. Once this parameter is set to False, the cell cannot be

deleted, and even if the priority level is low, it will not be changed to HO blacklist.

Also, the operator can set the IS_HOALLOWED parameter to True or False to

have the cell included in the HO blacklist. Once this parameter is set to false, the

cell will be included in the HO blacklist.



Chaning the ANR Settings

The operator can change the ANR settings using the CHG-SON-ANR command.

This command changes the ANR settings which are applied when the ANR function is

Manual Apply or Auto Apply by executing the CHG-SONFN-CELL command.

By default, the ANR function of the LTE-SON is supported by the User Equipment (UE) or

the LSM for obtaining the neighbor identity information including ECGI/TAC/PLMN for

automatic addition of an NR. The NR ranking function is performed by considering the

handover key performance index (KPI: HO attempt/failure rate, etc.) for each neighboring

cell obtained over the X2 interface.

The ranking is used as the reference for selecting an NR from the existing NRs to add to

the handover blacklist in order to add an NR for the new adjacent cell when the system is

running at the maximum NRT size.

In other words, if a new NR is added while the maximum NRT is full, the lowest ranking

NR is added to the blacklist. For determining the ranking, the DEFAULT_WEIGHT,

HO_ATTEMPT_WEIGHT, and HO_SUCCESS_WEIGHT parameter values can be used

for assigning weights to the new NR, HO attempt rate, and HO success rate.

The HO blacklist function identifies invalid adjacent cells from the HO performance

viewpoint and adds them to the HO blacklist in order to prevent unnecessary handover to

invalid adjacent cells and ultimately to improve the HO KPI. The criteria for inclusion in

the HO blacklist are either that the NR does not satisfy the HO KPI or that the HO attempt

to wrong cells increases by a certain rate. The first condition is set using the LOWER_HO_

ATTEMPT_RATE and LOWER_HO_SUCCESS_TO_KPI parameters, while the second is

set using the UPPER_HO_TO_WRONG_RATE parameter.

On the contrary, if the HO attempt to the NR on the blacklist increases by a certain rate, it

escapes the blacklist. The escape condition is set using the UPPER_HO_TO_BLACK_

RATE parameter.



The following table shows input parameters for the CHG-SON-ANR command.

(M: Mandatory, O: Optional, F: Fixed)

Input

Parameter

Mandatory/

Optional/Fixed

(Default Value)

Range Description

MAX_NRTSIZE O (30) 1~256 The maximum size for a Neighbor Relation

Table (NRT) per cell. ANR manages the

ranking of NRs that are within this size.

If adding NRs exceeds the size, ANR

deletes the existing NRs with the lowest

rank to limit the number of NRs to

MAX_NRTSIZE.

DEFAULT_WEIGHT O (0.5) 0.0~1.0 The default weight to a new Neighbor

Relation (NR). Newly added neighboring

cells are at a disadvantage in terms of

handover attempt and success rates when

ranking occurs, and hence are given the

default weight specified in the input

parameter during the default period

(DEFAULT_PERIOD).

DEFAULT_PERIOD O (2) 1~30 The period of time (in days) when the

default priority is applied to the new

Neighbor Relation (NR). During this period,

the newly added NR is given the default

weight (DEFAULT_WEIGHT) and closed off

to the blacklist.

HO_ATTEMPT_

WEIGHT

O (1.0) 0.0~1.0 Weight given to a handover attempt rate

when calculating NR ranking. By default, the

handover success and failure rates of each

neighboring cell are considered and the

attempt rates are weighed when determining

the NR ranking.

HO_SUCCESS_

WEIGHT

O (1.0) 0.0~1.0 Weights given to a handover success rate

when calculating NR ranking. By default, the

handover success and failure rates of each

neighboring cell are considered and the

attempt rates are weighed when determining

the NR ranking.



(Continued)

Input

Parameter

Mandatory/

Optional/Fixed

(Default Value)

Range Description

LOWER_HO_

ATTEMPT_RATE

O (0.001) 0.0~1.0 The lowest attempt rate at which the

handover blacklist is applied. NRs that failed

to meet the handover KPI are included in

the handover blacklist to prevent handovers

to such neighboring cells. Cells whose

attempt rate is lower than the input

parameter value, and whose success rate is

lower than LOWER_HO_SUCCESS_TO_

KPI are managed using the handover blacklist.

LOWER_HO_

SUCCESS_TO_

KPI

O (0.5) 0.0~1.0 The lowest success rate at which the

handover blacklist is applied. NRs that failed

to meet the handover KPI are included in

the handover blacklist to prevent handovers

to such neighboring cells. Cells whose

success rate is lower than the handover KPI

multiplied by the input parameter value, and

whose attempt rate is lower than LOWER_

HO_ATTEMPT_RATE are managed using

the handover blacklist.

UPPER_HO_TO_

WRONG_RATE

O (0.9) 0.0~1.0 The upper limit of a handover attempt rate at

which handovers to wrong cells are

blacklisted. If handovers to wrong cells are

highly frequent (i.e. RLFs or reconnections

to other neighboring cells occur at a

frequency higher than the input parameter

value while handovers to the relevant

neighboring cells are in progress or before a

specified time lapses after the handovers

are complete), such handovers are added to

the handover blacklist.

UPPER_HO_TO_

BLACK_RATE

O (0.1) 0.0~1.0 The upper limit of a handover attempt rate at

which handovers to wrong cells are

removed from the blacklist.

During a handover from cell A to cell B, if a

„handover to wrong cell‟ event occurs and

reconnections to neighboring cells managed

by the blacklist occur at a frequency higher

than the input parameter value, the

corresponding NR is returned to NRT from

the blacklist.

Retrieving the ANR Settings

The operator can retrieve the ANR settings using the RTRV-SON-ANR command.

Details for output parameters are the same as described for CHG-SON-ANR.



7.3 PCI

When installing the LTE system, the Physical Cell ID auto-configuration (PCI) function

allows the eNB to set the PCI of each cell automatically, to provide convenience for

operation of the LTE system. When growing the base station, after configuring the initial

neighbor using the latitude and longitude information entered by the operator, it allocates

the PCID that the ambient base stations do not use. The procedure for performing the PCID

is the same as that for providing the Initial NRT. To set On/Off for this function, change it

on the son.pcid flag of the son.properties file in the /home/lsm/aceman/data/properties/

project directory in the LSM server. Setting On/Off through the GUI will be provided in the

future.

Below is the procedure for allocating the PCID automatically.



Figure 7.5 eNB Grow Window (Performing the PCI function)

2) After the grow is performed, check whether the PCID is allocated through the Event

window.

Figure 7.6 Event Window (Performing the PCI function)



7.4 RACH

When installing the eNB, the Random Access Channel (RACH) optimization function

automatically sets the root sequence index.

The root sequence index value is determined by the HighSpeedFlag and zeroCoorelation

values in the PRachConfLogic table of the eNB Cell Info window when expanding the

system. A value duplicated with the value which the adjacent eNBs uses cannot be

allocated. If the root sequence index available within the range is all occupied by adjacent

eNBs, values except for those used by the farthest eNB in terms of latitude and longitude

are allocated.

To set On/Off for this function, change it on the „son.rach flag‟ of the son.properties file in

the /home/lsm/aceman/data/properties/project directory in the LSM server. Setting On/Off

through GUI will be provided in the future.

Below is the procedure for allocating the RootSequenceIndex value automatically.



Figure 7.7 eNB Grow Window (Performing the RACH function)



2) After the grow is performed, check whether the RootSequenceIndex value is allocated

through the event window.

Figure 7.8 Event Window (Performing the RACH function)



7.5 ES

The Energy Saving (ES) function reduces the operation cost of the system by reducing the

eNB‟s energy (power) consumption. The function will reduce the power consumption by

modifying the PA bias voltage and the Resource Block (RB) according to the specified

requirements.

The following table shows ES-related system commands:


CHG-ES-COM Changes the common parameters used in ES mode. ALL

RTRV-ES-COM Retrieves the common parameters used in ES mode. ALL

RTRV-ES-TYPE Retrieves the ES mode type. ALL

CHG-ES-SCHED Changes the ES mode schedule.

The ES mode can be specified per cell or hour.

ALL

RTRV-ES-SCHED Retrieves the ES mode schedule. ALL

The ES function can either be executed by the predefined schedule (manual apply) or by

the traffic analysis (auto apply).

The operator can set the ES execution mode using the CHG-SONFN-CELL command.

The ENERGY_SAVINGS_ENABLE field of the CHG-SONFN-CELL command has the

following parameters:

sonFuncOff: The energy saving function is disabled except for during traffic analysis.

sonManualApply: The energy saving function is enabled according to the schedule set

by the operator.

sonAutoApply: Performs the energy saving function based on the information

obtained through traffic analysis.



7.5.1 Schedule-based Energy Saving

The schedule-based energy saving function runs in ES mode according to the schedule

specified by the operator. To enable this function, energy saving must be set to

„sonManualApply‟ using the CHG-SONFN-CELL command.

Setting Time Scheduled Energy Saving

The operator can set the schedule of the ES mode using the CHG-ES-SCHED command.

This command‟s parameter is used to change the schedule for the predefined time-based

energy saving performed when the energy saving function is set to „Manual Apply‟ using

the CHG-SONFN-CELL command.

The system operator can schedule the eNB‟s energy saving function through the LSM.

The Energy Saving Manual Apply function executes the PA bias voltage change command

every hour according to the set schedule. The activation time, activation status, ES voltage

mode, and the RB type to restrict can be specified. Energy saving by schedule can be set on

an hourly basis; the schedule is checked hourly for determining the operation.

If ES_MODE_VOLTAGE_TYPE is the same for the previous hour and the current hour,

the operation for the previous hour remains for the current hour as well. The ES_STATE

parameter can be used for determining SUSPEND or ACTIVE. Also, to stop the currently

active ES mode, ES_STATE which is ACTIVE for the current hour is modified to

SUSPEND.

The ES_MODE_VOLTAGE_TYPE and ES_MODE_RB_TYPE parameters determine the

voltage mode to use and the RB type to limit during the hour. To ensure the energy saving

performance, the two parameters must be paired correctly. In other words, if ES_MODE_

VOLTAGE_TYPE is ES Mode1_Voltage, ES_MODE_RB_TYPE should also be set to ES

Mode1_RB.

The following table shows input parameters for the CHG-ES-SCHED command. (M:

Mandatory, O: Optional, F: Fixed)

Input

Parameter

Mandatory/

Optional/Fixed

(Default Value)

Range Description

CELL_NUM M (N/A) 0~17 The cell number, for which the energy saving

function runs according to the schedule.

HOUR M (N/A) 0~23 The time period for which the energy saving

function runs according to the schedule.

ES_STATE O (esSuspend) esSuspend,

esActive

Determines the hourly energy saving

operation according to the schedule.

- esSuspend: Energy saving is suspended

during the hour.

- esActive: Energy saving is active during the

hour.



(Continued)

Input

Parameter

Mandatory/

Optional/Fixed

(Default Value)

Range Description

ES_MODE_

VOLTAGE_

TYPE

O (esNormal_Voltage) esNormal_Voltage,

esMode1_Voltage,

esMode2_Voltage,

esMode3_Voltage

The type of voltage in which the

hourly energy saving function runs

during the hour according to the

schedule.

Each has 30 V, 28 V, 26 V and

24 V as its value.

- esNormal_Voltage: Runs in

normal mode voltage (30 V).

- esMode1_Voltage: Runs in ES

mode 1 Voltage (28 V).

- esMode2_Voltage: ES Mode

2 Voltage (26 V).

- esMode3_Voltage: Runs in ES

mode 3 Voltage (24 V).

ES_MODE_

RB_TYPE

O (esNormal_RB) esNormal_RB,

esMode1_RB,

esMode2_RB,

esMode3_RB

The type of RB restricted by the

hourly energy saving function runs

during the hour according to the

schedule. Each parameter has a

different RB value depending on

the DSP bandwidth.

- esNormal_RB: Runs in normal

mode RB. 25 (BW 5 M), 50 (BW

10 M)

- esMode1_RB: Runs in ES mode

1 RB. 21 (BW 5 M), 44 (BW 10 M)


2 RB. 17 (BW 5 M), 38 (BW 10 M)


3 RB. 13 (BW 5 M), 26 (BW 10 M)

Retrieving the Time-Scheduled Energy Saving

The operator can retrieve the schedule of the energy saving function using RTRV-ES-

SCHED command.

Details for output parameters are the same as described for CHG-ES-SCHED.



7.5.2 Traffic-based Energy Saving

The traffic-based energy saving function runs in most appropriate ES mode according to

the traffic analysis. To enable this function, energy saving must be set to „sonAutoApply‟

using the CHG-SONFN-CELL command.

With this function, SON analyzes traffic statistics based on the conditions specified by the

operator at every interval. After checking that there is no error in the system and traffic, the

function will run in ES mode by modifying the PA bias voltage and Resource Block (RB).

Setting the Parameters of Traffic-based Energy Saving

The operator can set the parameters used for the traffic analysis using the CHG-ES-COM

command. The command changes the energy saving settings for when the function is set to

„Auto Apply‟ using the CHG-SONFN-CELL command.

Traffic estimation for selecting ES mode involves the following two methods.

The first method is calculation with the average value of the traffic load statistics for the

specified time during the last 15 or 30 days as determined by the DATA_VALIDITY

parameter. The second method is calculation with weight-adjusted value of the

MOVING_AVERAGE_WEIGHT parameter value for the last 2, 3, 4, 5, or 10 hours as


The ES mode is determined by selecting the maximum value from these two methods.

Energy saving guarantees operation performance by monitoring the abnormal traffic state

and the abnormal system state on an hourly basis. Abnormal traffic status indicates larger

traffic fluctuations than usual or significant differences between the traffic estimation and

the actual traffic load, which leads to poor traffic estimation performance (the estimation

success rate is lower than the CORRELATION_COEFFICIENT_THRESHOLD parameter

value) and causes the energy saving function to stop and return to ES normal mode.

Abnormal system status means the abnormal status monitored by the eNB and is

determined by the RE_TX_THRESHOLD and BLER_THRESHOLD parameters. It causes

the energy saving function to stop and return to ES normal mode.

The following table shows input parameters for the CHG-ES-COM command.


Input

Parameter

Mandatory/

Optional/Fixed

(Default Value)

Range Description

DATA_VALIDITY O (esDataValid_

30day)

esDataValid_

15day,

esDataValid_

30day

The number of days used in traffic

analysis for calculating an estimate to

determine the ES mode. Traffic estimation

includes calculating the average of the

specified hour‟s traffic load statistics over

the period (past 15 or 30 days)

determined by this parameter.



(Continued)

Input

Parameter

Mandatory/

Optional/Fixed

(Default Value)

Range Description

MOVING_

AVERAGE_

VALIDITY

O (esMovingAvg2) esMovingAvg2,

esMovingAvg3,

esMovingAvg4,

esMovingAvg5,

esMovingAvg10

The length of time (in days) for which

to apply a moving average for traffic

estimation. The MOVING_

AVERAGE_WEIGHT parameter

value is added as a weight to the

time (past 2, 3, 4, 5 or 10 hours)

determined by this parameter.

MOVING_

AVERAGE_

WEIGHT

O (50, 50, 0, 0, 0,

0, 0, 0, 0, 0)

NUMARRAY

(0~100)

Weight (in %) added to the length of

time, for which a moving average is

applied, for traffic estimation.

This parameter value serves as a

weight to the length of time

determined by MOVING_AVERAGE_

VALIDITY. The first weight of this

parameter indicates the most recent

time period.

If MOVING_AVERAGE_VALIDITY is

2 days and the parameter has

(50, 50, 0, 0, 0, 0, 0, 0, 0, 0), a 50%

weight is added to the past 2 hours.

CORRELATION_

COEFFICIENT_

THRESHOLD

O (0.8) 0.0~1.0 The minimum baseline to escapte

the ES mode due to a significant

difference between the traffic

estimation and the actual traffic load

measured, which can lead to poor

traffic estimation performance.

A hit rate measurement is used to

determine the performance of traffic

estimation. A hit is recorded per hour

when the ES mode selected by traffic

estimation matches the most

appropriate ES mode based on the

actual measurement. If the hit rate

over the past 24 hours is less than

this parameter value, the energy

saving mode stops and changes to

the normal mode.



(Continued)

Input

Parameter

Mandatory/

Optional/Fixed

(Default Value)

Range Description

RE_TX_

THRESHOLD

O (1) 0.0~1.0 The 4th ReTx threshold (in %) used to

determine system abnormality. The current

system condition needs to be checked prior

to the SON energy saving operation.

If the system is abnormal, the normal mode

is selected instead of the energy saving

mode, suspending the operation until the

system status is resolved. In DL-HARQ

Status, if the number of DL transmissions

exceeds the major alarm threshold, the

system is considered abnormal.

The parameter indicates the 4th

retransmission rate.

BLER_

THRESHOLD

O (10) 0.0~1.0 The 4th ReTx BLER threshold (in %) used

to determine system abnormality.

The current system condition needs to be

checked prior to the SON energy saving

operation. If the system is abnormal, the

normal mode is selected instead of the

energy saving mode, suspending the

operation until the system status is resolved.

In DL-HARQ Status, if the value for DL

Residual BLER exceeds the major alarm

threshold, the system is considered

abnormal. The parameter indicates the

BLER for the 4th retransmission.

Retrieving the Parameters of Traffic Based Energy Saving

The operator can retrieve the parameters used for the traffic analysis using the RTRV-

ESMODE-COMMON command. Details for output parameters are the same as described

for CHG-ES-COM.



Retrieving the Energy Saving Threshold Type

The operator can retrieve the threshold type to select the ES mode using the RTRV-ES-

TYPE command. Retrieves the mode type of the SON energy saving function.

ES mode type is applied when the energy saving function is set to Auto Apply using the

CHG-SONFN-CELL command. In the LTE eNB system, the energy saving function is

enabled when the system traffic load estimated by traffic analysis satisfies the ES mode

entering condition. In other words, normal mode and three ES modes are defined as

follows:

Normal Mode: The eNB is in normal operation. The normal mode is maintained when

the traffic load estimate is higher than the entering threshold of ES Mode1.

ES Mode #: The energy saving function runs by modifying the eNB‟s PA bias.

An appropriate PA bias change mode is enabled if the estimated hourly traffic load is

less than the entering threshold of ES Mode. The cells that perform the energy saving

function increase as the ES mode step increases.

The following table shows output parameters for the RTRV-ES-TYPE command.

(M: Mandatory, O: Optional, F: Fixed)

Output Parameter Range Description

ES_MODE_

INDEX

0~7 Index for the ES mode.

ES_MODE_TYPE esModeTypeNormal,

esModeTypeESMode1,

esModeTypeESMode2,

esModeTypeESMode3

ES mode to operate in when the traffic load

estimate is within the range between the entering

and leaving thresholds.

ES_MODE_

ENTERING_

THRESHOLD

0~100 Condition to change to an ES mode. When the

traffic load estimate is lower than the entering

threshold of each ES mode, it changes to the

respective ES mode.

ES_MODE_

LEAVING_

THRESHOLD

0~100 Condition to switch to a different ES mode.

When the traffic load estimate is higher than the

leaving threshold of each ES mode, the current

ES mode switches to another.



7.6 Self Optimization

The SON provides a self optimization function which includes automatic compensation for

RRH optic delay.

7.6.1 RRH Optic Delay Automatic Compensation

Each RRH provides the following commands to compensate the optic delay due to the

distance from the DU and the CPRI‟s hopping delay (transceiver board delay) occurring

within the intermediate RRHs along the path. During the initial RRH installation or when

the optic delay value is modified, the SON calculates the optic delay of each RRH to get

the Tx and Rx time buffers.

The calculated timer buffer is then sent to the corresponding RRH for RRH delay

compensation.

The operator can set how RRH optic delay is compensated using the CHG-SONFN-ENB

command. The DELAY_COMPENSATION_ENABLE field of the CHG-SONFN-ENB

command has the following parameters:

sonFuncOff: The SON delay compensation function is disabled.

sonAutoApply: The SON delay compensation function is enabled.

The following table shows the system commands related to the automatic compensation of

the SON‟s RRH optic delay:


CHG-SON-SO Changes the parameters of the SON optic delay automatic

compensation.

ALL

RTRV-SON-SO Retrieves the parameters of the SON optic delay

automatic compensation.

ALL

Setting the Tx/Rx Max. Time Buffers

The operator can set the Tx and Rx maximum time buffers using the CHG-SON-SO

command. RRH optic delay compensation related to this command measures an optic delay

value per RRH when the initial RRH setup and optic delay changes occur, and then

calculates the Tx/Rx time buffers modified by the expression. The time buffer value

obtained is sent to the respective RRH for RRH delay compensation. TX_TBMAX and

RX_TBMAX values that can be changed with this command are necessary to calculate the

time buffer.



The following table shows input parameters for the CHG-SON-SO command.


Input

Parameter

Mandatory/

Optional/Fixed

(Default Value)

Description

TX_TBMAX O (100485) The maximum value for the Tx time buffer; the maximum

delay that can occur from the DU to the RRH. TX_TBMAX

can be obtained in the following expression, where d_max

(km) is the maximum distance between the DU and RRH,

h_max (ns) is the maximum DL CPRI hopping delay,

N_max is the maximum number of RRHs to be cascaded,

and PD_max is the maximum Tx processing delay.

This expression is to determine the Tx maximum time

buffer and can change depending on various factors

when designing a network.

TX_TBMAX (ns) = 5000 * d_max + (N_max-1) * h_max +

PD_max

RX_TBMAX O (98505) The maximum value for the Rx time buffer; the maximum

delay that can occur from the DU to the RRH. TX_TBMAX

can be obtained in the following expression, where d_max

(km) is the maximum distance between the DU and RRH,

h_max (ns) is the maximum UL CPRI hopping delay,

N_max is the maximum number of RRHs to be cascaded,

and PD_max is the maximum Rx processing delay.

This expression is to determine the Rx maximum time

buffer and can change depending on various factors

when designing a network.

RX_TBMAX (ns) = 5000 * d_max + (N_max-1) * h_max +

PD_max

Retrieving the Tx/Rx Max Time Buffer

The operator can retrieve the Tx and Rx max time buffers using the RTRV-SON-SO

command. Details for output parameters are the same as described for CHG-SON-SO.



CHAPTER 8. QoS Control

8.1 ARQ Control

The Automatic Repeat Request (ARQ) function is a method to increase the reliability of

data transmission, through which the transmitter (hereafter Tx) retransmits data when the

receiver (hereafter Rx) requests retransmitting data.

The ARQ procedure is performed only in RLC Acknowledged Mode (AM). When the Tx

transmits data to the Rx and receives the ACK from the Rx, the Tx window is forwarded to

continue data transmission. The size of the LTE RLC Tx window is 1024, which means SN

0 to 1023.

If the Tx receives the NACK or no ACK/NACK, data transmission is performed with the

embedded timer. The purpose of the ARQ is to increase the reliability of data transmission

by allowing the Rx to receive data stably through the data retransmission process.

When the Rx receives data successfully, it sends the Tx the ACK information to notify to

the Tx that the data has been received successfully. Rx maintains the Rx window as the

current state, and transmits NACK to Tx when data received are „out-of-order‟ so that

unreceived data can be retransmitted within a specified time. The size of the LTE RLC Rx

window is 1024 (SN 0 to 1023) as the Tx window.



8.2 HARQ Control

HARQ reduces the impact of link quality (channel, interference) fluctuations and link

adaptation mismatches by performing the MAC-level retransmission of transport blocks

that are not transmitted properly. This operation combines data that are retransmitted

multiple times can also provide time diversity.

In the downlink, up to 8 HARQ processes with the asynchronous method can be assigned

to one UE. With the asynchronous HARQ, the UE uses the HARQ process identifier and

Redundancy Version (RV) that are sent along with the data to recognize which data will be

retransmitted at a certain time. The ACK/NACK for the DL HARQ is transmitted through

the PUCCH. The ACK/NACK for the PDSCH transmitted to the n-th sub-frame is received

through the PUCCH of the n + 4th sub-frame. When a NACK or none is detected as a

result of the error detection, DL HARQ retransmission occurs asynchronously, i.e. at a

certain point of time after a minimum delay or Round Trip Time (RTT).

In the uplink, the default operation is non-adaptive synchronous HARQ except for when

transmissions to the UE conflict in the same resources, adaptive HARQ is preferred.

With the non-adaptive synchronous method, the RB and MCS level used for retransmission

remain the same, so the control overhead decreases without having to transmit the UL grant

through the PDCCH. However, the same location of the assigned RB for retransmission

does not help resource efficiency.

8 UL HARQ processes are available. The eNB decodes the uplinked packets received and

saves the data in its memory for HARQ retransmission if the decoding fails.

8.3 AMC Control

To provide downlink channel information, the UE feeds the maximum modulation level

and the CQI for the coding rate back to the eNB through Adaptive Modulation and Coding

(AMC). The downlink scheduler considers the CQI received from the UE when allocating

resources and determines the number of the RBs per UE and the MCS to transmitted

through TBS. The selected MCS is transmitted to the UE through the PDCCH, and the UE

performs the decoding using the TBS information, i.e. the modulation level for each MCS

index value.

The uplink scheduler determines the modulation level and TBS to be transmitted depending

on the characteristic of the channel measured in the eNB and the number of RBs allocated

per UE. The MCS level is determined by comparing the measured SNR to the respective

MCS level thresholds and selecting the MCS whose threshold is below the SNR.

For the number of RBs, the RB allocation result is used.



8.4 CQI Control

The CQI/PMI/RI that the UE transmits to the eNB is classified into the two types: periodic

and aperiodic. With the periodic Channel Quality Indicator (CQI), the UE sends the

feedback regularly according to the parameters determined by the RRC layer.

Periodic reporting modes defined by the 3GPP standard are Mode 1-0, 1-1, 2-0, 2-1.

Each mode is applied according to whether the sub-band CQI and PMI feedback exist.

Aperiodic reporting modes distinguish the CQI feedback and PMI feedback; there are five

aperiodic reporting modes: Mode 1-2, 2-0, 2-2, 3-0, 3-1. The transmission information for

each report type above is fed back according to the respective period and offset determined

by the RRC layer.

The information required to operate the uplink scheduling includes the radio link status, the

scheduling request by the UE, and the buffer status. The 3GPP standard defines the

Sounding Reference Signal (SRS), Demodulation Reference Signal (DM RS) and Power

Headroom Report (PHR) to obtain the radio link status, and the Scheduling Request (SR)

and Buffer Status Report (BSR) to obtain the UE‟s scheduling request and buffer status.

The SRS is a reference signal transmitted to the uplink and exists in the subframe‟s last

symbol. Transmission occurs in a bandwidth set through the SRS and according to the

period and transmission offset. The DM RS is the reference signal transmitted in the

PUSCH area. The eNB receives the SRS and DM RS that each UE transmits, and uses

them for checking the uplink status or measuring the uplink timing. The PHR is a value

reported by the UE and represents the available power relative to the UE‟s maximum power.

The scheduler can use the PHR to estimate the UE‟s location indirectly.

The SR (Scheduling Request) is used to request the UL-SCH resource when there is new

data to be transmitted by the UE. When a dedicated SR is assigned, the SR is used through

thee PUCCH format 1, if not, it is used through the PRACH procedure. The Buffer Status

Report (BSR) is used to transmit the quantity of the data to be trasmitted by the UE to the

eNB. The reported buffer size includes the data in the buffer of the RLC and PDCP layer,

but it does not include the RLC header and MAC header.



8.5 Scheduling Algorithm Control

The UE-specific scheduling metric used for RB allocation consists of a PF metric and QoS

metric. The following shows the PF metric:

PF metric = (R)^ (beta)/ (Average_T_put)^ (alpha)

In the expression above, R represents the maximum data rate available for the channel

status. The channel status is calculated using the feedback information from the UE.

Average_T_put is the UE‟s average throughput, and alpha and beta are the fairness weight

and channel quality weight respectively which are parameters used to adjust the PF priority

policy. The default value for alpha and beta is 1. The following scheduling methods are

available:

Maximum C/I: Selects the UE with excellent channel characteristics. This is the best

method in terms of the system‟s spectral efficiency.

In the maximum C/I, resources are preferentially assigned to the UE where the channel

environment is good, which can lead to poor fairness between UEs. To configure the

maximum C/I, set the alpha to 0 and the beta to 1.

Proportional Fairness: A method to enhance the fairness between UEs and increase the

system capacity. It is better than the round robin for system capacity and than the

maximum C/I for fairness. The default value for alpha and beta is 1 respectively.

Alpha and beta can be set to a higher value to increase fairness (alpha) and cell

throughput (beta).

The other scheduling method is the round robin which is described below:

Round robin: A method to provide UEs with equal opportunities. It offers strong

performance in terms of fairness, but is not satisfactory for the system‟s spectral

efficiency as it gives the same resource allocation opportunity to all UEs with either a

good or bad channel environment.

The LTE standard defines a total of 9 QoS classes to ensure the QoS of various services.

Each QoS class is mapped to related requirements such as the data rate, packet delay and

error rate. Detailed characteristics are described in the table below:

QCI Resource

Type Priority

Packet

Delay

Budget

Packet

Error Loss

Rate

Example Services

1 GBR 2 100 ms 10-2 Conversational Voice

2 4 150 ms 10-3 Conversational Video

(Live Streaming)

3 3 50 ms 10-3 Real Time Gaming

4 5 300 ms 10-6 Non-Conversational Video

(Buffered Streaming)



(Continued)

QCI Resource

Type Priority

Packet Delay

Budget

Packet Error

Loss Rate Example Services

5 Non-GBR 1 100 ms 10-6 IMS Signalling

6 6 300 ms 10-6 Video (Buffered Streaming)

TCP-based (e.g. www, e-mail,

chat, ftp, p2p file sharing,

progressive video, etc.)

7 7 100 ms 10-3 Voice, Video (Live Streaming)

Interactive Gaming

8 8 300 ms 10-6 Video (Buffered Streaming)

TCP-based (e.g. www, e-mail,

chat, ftp, p2p file sharing,

progressive video, etc.)

9 9

Each QCI-related parameter in the table above has the following meaning:

The Resource Type indicates whether the service in question requires the minimum

data rate. The GBR type indicates a service with the minimum data rate requirement;

the non-GBR type indicates a service without such requirement.

Priority indicates the relative priority of service classes. The standard defines priority

with one of 1-9 values, 1 being the highest priority.

The Packet Delay Budget (PDB) indicates the delay requirement with which to

transmit each packet. 98% or more of the trasmitted packets must meet the delay

requirement. The standard defines the QCI-specific PDB, and the QoS scheduler uses

this value for scheduling.

The Packet Error Loss Rate indicates a ratio of errors occurring in the air link when

there is no congestion.

Samsung eNB supports additional QCIs that the service provider can customize as well as

QCI 1-9 defined in the 3GPP standard.

By default, the packet scheduler allocates resources to a service with a high priority to

satisfy the service QoS. Resources are allocated in the order of signaling data, VoIP data,

GBR and non-GBR which correspond to QCI 5, QCI 1, QCI 2-4 and QCI 7-9.

For GBR services, the priority above and PDB are reflected in the QoS metric to tightly

satisfy the QoS required by the standard. Then, the GBR service with a priority higher than

that of another GBR service is processed first at all times. If the priority is equal, the bigger

the packet delay and the smaller the PDB, the higher the QoS metric value.

In addition to the QCIs above, other QoS-related parameters supported by the LTE include

GBR, MBR and AMBR which are received from the PCRF for logical channel settings.

The GBR and MBR apply to GBR services, and represent the minimum and maximum data

rate requirements, respectively. The AMBR applies to non-GBR services, and restricts the

sum of all non-GBR services that can be supported for one UE.



The commands to retrieve/change the parameters related to the scheduling algorithm are as

follows:

Command Description

RTRV-DL-SCHED Retrieves the parameters related to the DL scheduling algorithm.

CHG-DL-SCHED Changes the parameters related to the DL scheduling algorithm.

RTRV-UL-SCHED Retrieves the parameters related to the UL scheduling algorithm.

CHG-UL-SCHED Changes the parameters related to the UL scheduling algorithm.



8.6 Power Control

The power transmitted to the LTE downlink is determined by the AP and BP values set in

the RRC layer. The eNB calculates the power which each Resource Element (RE) will use

in the downlink, using the AP which has one value per UE and the BP which has one

value per cell. Calculated values are A and B , ratios of the PDSCH EPRE (Energy per

Resource Element) power against the cell-specific RS EPRE in respective OFDM symbols

with and without RS (Reference Signal). The setting is UE-specific.

In the uplink, the UE measures the path loss for the serving cell to determine the power

according to the expression defined in the standard. Basically, open loop power control is

performed. The transmission power for each RB of the UE is determined by

)(O_PUSCH jP and )( j which is given from higher layers. )(O_PUSCH jP is a parameter

composed of the sum of a cell specific nominal component )( PUSCHO_NOMINAL_ jP provided

from higher layers for j=0 and 1 and a UE specific component )(O_UE_PUSCH jP provided

by higher layers for j =0 and 1. For PUSCH (re)transmissions corresponding to a semi-

persistent grant then j=0 , for PUSCH (re)transmissions corresponding to a dynamic

scheduled grant then j=1 and for PUSCH (re)transmissions corresponding to the random

access response grant then j=2. 0)2(O_UE_PUSCH P and

3_O_PREPUSCHO_NOMINAL_ )2( MsgPREAMBLEPP , where the parameter PREAMBLE_INITIAL_

RECEIVED_TARGET_POWER( O_PREP ) and 3_ MsgPREAMBLE are signalled from higher

layers.

For j =0 or 1, 1,9.0,8.0,7.0,6.0,5.0,4.0,0 is a 3-bit cell specific parameter provided

by higher layers. For j=2, .1)( j To measure the path loss, the UE uses the RS signal

power passed through the SIB and the serving cell RSRP measured by the UE.

To complement the UE‟s open loop power control, closed loop power control (for

correcting the path loss estimation error) and IoT control (for adjusting the neighboring cell

interference) are also supported.

The following describes the key characteristics of the power controls above:

Open loop power control: The default power control used in the uplink. It operates by

compensating the path loss measured through the downlink RS. The LTE standard

allows the full compensation of the path loss so that the Rx power can be a target

SINR. However, )( j is supported for partial compensation in consideration of

system efficiency. This parameter can have 8 values (0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1.0)

specified by the standard.

Closed loop power control: While the open loop power control adjusts the Tx power to

compensate the path loss, closed loop power control is also considered to compensate

the inaccuracy of path loss estimate. This is done using the TPC command passed to

the UE from the eNB.



IoT Control: Adjusts the interference between cells to a certain level using the

Interference Overload Indicator (IOI) shared via the X2 interface. It is controlled using

the TPC command in the same way as for the closed loop power control.

With this operation, adjusting the inter-cell interference can create an effect of

increasing the system capacity. The IOI is a result of measuring the size of interference

received in the serving cell and classifying it into high, medium or low for each RB.

It is passed to the neighboring cell via the X2 interface.

The commands to set the parameters related to the UL Power control are as follows:

Command Description

RTRV-ULPWR-CTRL Retrieves the UL power control related parameters.

CHG-ULPWR-CTRL Changes the UL power control related parameters.



8.7 DRX

The LTE provides the discontinuous reception (DRX) by which the UE can choose not to

monitor the incoming PDCCH in RRC CONNECTED status to reduce power consumption.

In DRX, an active time refers to a time when the UE monitors the PDCCH. When not in

active time, the UE cannot receive the PDCCH transmitted by the eNB.

Therefore, the eNB‟s packet scheduler performs the DL/UL scheduling to transmit the

PDCCH when the UE is in active time.

The UE performs the DRX-related operation in compliance with the DRX-related

parameters received from the eNB previously, except in the case that the DRX command

MAC CE is received from the eNB. The DRX operation uses DRX timers

(onDurationTimer, drx-InactivityTimer and drx-RetransmissionTimer) and parameters

(longDRX-Cycle, shortDRX-Cycle and drxStartOffset).

The commands to set the parameters related to the DRX are as follows:

Command Description

RTRV-DRX-INF Retrieves the DRX related parameters.

CHG-DRX-INF Changes the DRX related parameters.



CHAPTER 9. Fault

9.1 Alarm Overview

If a fault occurs, the eNB notifies it to the operator using an alarm, so a failover or restore

is performed as soon as possible. For some faults, after the eNB notifies the operator, the

system tries to restore them.

The following figure shows the eNB‟s alarm detection and reporting:

Figure 9.1 Alarm Detection and Reporting of the eNB System

The error processing block in the UMP collects alarms from the ECP, RRH, GPSR, and the

unit, and notifies the operator through the LSM if an alarm status changes.

The operator can retrieve the alarm generation/clear history in real time through the Event

Viewer of the LSM, and can retrieve the alarms being generated in the system in the CLI

window using the RTRV-ALM-LIST command. In addition, the operator can retrieve or

change the inhibition, severity and threshold settings for alarms as well as the User Defined

Alarm (UDA) settings.

UAMA (UMP)

RRH Alarm

GPSR/TOD Alarm

ECP Alarm

L8HU (RRH)

UCCM (GPSR)

L9CA (ECP)

Enclosure

eNB

Notify

Alarm

LSM

Rectifier/Environment

Alarm



Alarm Code

An alarm code is assigned to each alarm, which is composed of letters „A‟ and „R‟, and a

7-digit number „xxyyzzz‟ as shown below.

Figure 9.2 Alarm Code

„A‟: Abbreviation of „alarm‟

„R‟: Abbreviation of „RAN‟ (= eNB)

„xxyyzzz‟ (7-digit number): Unique to each alarm.

xx: NE type.

yy: Unit type.

zzz: Alarm type.

A xxyyzzz R

Abbreviation of the alarm

Abbreviation of the RAN (eNB)

Alarm number



9.2 Alarm Output

Types of Output Message

Alarm generation

Alarm clear

Format of Output Message

The figure below shows the alarm output window in the LSM.

Figure 9.3 LSM Alarm Output Window

The table below shows the output format of alarms.

Output Parameter Description

No Serial number

Severity Alarm severity (Critical, Major, Minor, Cleared)

Code Alarm code (A0000000R-A9999999R)

Group Alarm group (Equipment, Communication, QoS, and Environment)

Location /eNB Group/eNB ID/RACK[#]/SHEL[#]/SLOT[#]-Board[#]/Sub Location[#]

Probable Cause Alarm Type

Time yyyy-mm-dd HH:MM:SS

Colors for Alarm Severity

In the LSM Event Viewer, the following colors are used to indicate occurred and

cleared alarms and their, severity.

- Critical: Red

- Major: Orange

- Minor: Yellow

- Clear: Green



9.3 Alarm Correlation

Alarm correlation is used to filter unnecessary alarm notifications using the hierarchy of

the alarms defined in the system. There are some alarms that will be always followed by

their lower severity alarms when they occur. For those alarms which have a definite

hierarchy, alarm correlations are applied, and lower alarms are not notified to the LSM.

This is called „alarm filtering‟.

The purpose of alarm filtering is to allow the operator to have an intuitive understanding of

the alarm generation status and perform a failover or restore promptly, by reducing

unnecessary notification and notifying only the alarms on the real causes of a failure.

The following examples shows how alarm correlation is applied.

Correlation by Communication Fail

When the Communication Fail alarm is generated in the RRH, the alarms to be

collected from the boards cannot be detected. The Communication Fail alarm is

defined as the upper level alarm on all alarms of the board. All alarms occurred are

deactivated when the Communication Fail alarm is generated; after Communication

Fail is cleared, the alarms are collected then reflected.

Correlation of Alarms with Multiple Severity Levels

The overload alarm‟s hierarchy is defined in the order of Critical, Major, and Minor.

An alarm can only have one of those levels. A major alarm force-clears a minor alarm,

and a critical alarm force-clears the major alarms.



9.4 Alarm Control

Alarm Inhibition Control

Inhibition can be set for all alarms that occur in the system. The inhibition setting

determines whether to notify an alarm occurrence to the operator. The operator can set the

inhibition for alarms that do not require notifying.

When the inhibition setting is set to Inhibit for an alarm, although the alarm occurs, it is not

notified to the operator.

When the inhibition setting is set to Inhibit for an occurred alarm, the alarm is cleared and

it is notified to the operator. Then, although the alarm occurs repeatedly, the alarm is not

notified to the operator. The alarm is not notified to the operator, but it affects the system.

For example, if the VSWR Fail alarm which affects the cell status occurs at the RRH, if the

inhibition setting of the alarm is changed to Inhibit, the cell status is not recovered to the

normal status and only the alarm is cleared.

The system does not manage inhibited alarms. Therefore, inhibited alarms are not

displayed in the Event Viewer, and although the RTRV-ALM-LIST command is executed,

the alarms are not displayed.

Alarm Severity Control

Alarms that occur in the system are classified into three levels according to the severity,

and how seriously they affect the system function and services.

The alarm levels in this system are defined as follows:

Critical: Alarm which critically affects service. Immediate action is required for this

level of alarm.

Major: Alarm which affects service. Immediate action is required for this level of

alarm.

Minor: Although this level of alarm does not affect service, measures are required to

prevent a more serious fault, or to operate the system stably.

Alarm level control is applied only to alarms that are fixed to a specific level.

Therefore, since alarms that are determined depending on the threshold, like overload

alarms, cannot be fixed to a specific level, they are excluded when viewing or changing

alarm levels.

The operator can view or change the alarm levels only for those alarms whose level control

is available.

If an alarm level is changed in the case of an occurred alarm, the previous alarm level is

cleared and the new alarm level occurs.



Alarm Threshold Control

The operator can set the threshold for each level (Critical/Major/Minor) for some alarms.

When the value measured to determine whether to generate an alarm exceeds the set

threshold, the alarm of the level corresponding to the threshold occurs. The threshold

control target alarms are as follows:

Overload: Occurs when the load of the CPU exceeds the threshold.

Memory Full: Occurs when the usage of the memory exceeds the threshold.

Disk Full: Occurs when the usage of the disk exceeds the threshold.

Since the alarm is notified only as one level, if the measured value exceeds the threshold of

the critical level, only the critical alarm occurs in spite of the fact that the value exceeds the

thresholds of the major and minor levels. If the measured value is decreased to the value

between the thresholds of the critical and major levels, the critical alarm is cleared and the

major alarm occurs.

Moreover, in the status that an alarm for a specific level occurs, if the threshold of the level

is changed, since alarms are detected referring to the changed threshold again, the existing

alarm level is changed or cleared.

If the threshold is set to too a value, alarms for the threshold can occur frequently, therefore

the operator must set and manage a proper threshold, depending on the system status.

When setting the threshold, the value must be set to sequentially larger numbers in the

order Critical > Major > Minor.



9.5 Alarm-Related Commands

9.5.1 Retrieving Alarm Information

Views the occurrence location, type, severity, and threshold information for alarms

provided by this system.


Command Description

RTRV-ALM-INF Retrieves the list of the alarms available in the eNB. The following output

will be returned:

- UNIT_TYPE: Type of the unit where the alarm was generated.

- ALARM_GROUP: Alarm group.

- PROBABLE_CAUSE: Probable cause.

- ALARM_TYPE: Alarm type.

- ALARM_CODE: Unique code attributed to each alarm.

- SEVERITY: Alarm level.

- THRESHOLD_INFO: Threshold


1) Select the RTRV-ALM-INF command in the FM folder on the CLI window and click

the Execute button.

2) Check the execution result on the response window.

9.5.2 Retrieving Alarm Status

If a fault occurs in the system, or when checking the system status, as the operator views

the alarm status of the system, the required measures can be taken.

When viewing alarm status, the alarms that the inhibition settings are set to Inhibit cannot

be viewed. Therefore, if a system malfunction is suspected, but no alarm has occurred,

check the inhibition status of the alarms.

For the viewed alarms, refer to the maintenance manual.




Command Description

RTRV-ALM-LIST Retrieves the list of the alarms currently triggered in the eNB.

This command cannot retrieve The alarm that was cleared after it has

been triggered or inhibited by the operator. the following output will be

returned:


- UNIT_ID: Unit ID where the alarm was generated.

- RAISED_TIME: Time when the alarm was generated.







- LOCATION: location where the alarm was generated.

- SEQUENCE_ID: Sequence number of the alarm.


1) Select the RTRV-ALM-LIST command in the FM folder on the CLI window and click

the Execute button.


9.5.3 Retrieving Alarm History

Views the history of alarms that have occurred or are cleared in the system.


Command Description

RTRV-ALM-LOG Retrieves the eNB's alarm history. Up to 100 most recent alarm history

data can be retrieved. If an alarm was generated but not cleared, its

CLEARED_TIME will be displayed as '-' in the output result. the following

output will be returned:



- RAISED_TIME: Time when the alarm was generated.

- CLEARED_TIME: Time when the alarm was cleared.







- LOCATION: location where the alarm was generated.




1) Select the RTRV-ALM-LOG command in the FM folder on the CLI window and click

the Execute button.


9.5.4 Retrieving/Changing Alarm Inhibition

The following commands retrieve a list of inhibited alarms or change the alarms to the

inhibited state. There are two types of retrieval/change commands depending on whether

alarms are generated from the unit with a single ID (e.g. UMP) or the unit with multiple

IDs (e.g. RRH).

For the unit with a single ID, the CHG-ALM-INH and RTRV-ALM-INH commands

perform alarm inhibition change and retrieval respectively; for the unit with multiple IDs,

the CHG-RDALM-INH and RTRV-RDALM-INH commands perform alarm inhibition

change and retrieval respectively.


Command Description

RTRV-ALM-INH Retrieves a list of the inhibited alarms for the unit with a single ID, such

as UMP or ECP. The operator can use this command to retrieve a list of

the inhibited alarms, which are set to not be displayed on the operator

screen. If a fault occurs during the operation but the alarm is not

generated, the operator can use this command to check whether the

alarms are inhibited. The following output will be returned:





- INHIBIT_STATUS: Whether the alarm is inhibited or allowed

RTRV-RDALM-INH Retrieves a list of the inhibited alarms for the unit with multiple IDs, such

as RRH. The operator can use this command to retrieve a list of the

inhibited alarms, which are set to not be displayed on the operator

screen. If a fault occurs during the operation but the alarm is not

generated, the operator can use this command to check whether the

alarms are inhibited. The following output will be returned:


- CONNECT_BD_ID: ID of the board connected to the unit.

- CONNECT_PORT_ID: ID of the port connected to the unit.

- CASCADE_ID: Cascade ID of the unit.






(Continued)

Command Description

CHG-ALM-INH Changes the alarms to the inhibited state for the unit with a single ID,

such as UMP or ECP. The operator can use this command to change a

list of the alarms in the inhibited state. The list of alarms changed to the

inhibited state by the operator will not be displayed on the screen, and

will not be stored in the alarm history. The following inputs are required to

execute the command.





CHG-RDALM-INH Changes the alarms to the inhibited state for the unit with multiple IDs,

such as RRH. The operator can use this command to change a list of the

alarms in the inhibited state. The list of alarms changed to the inhibited

state by the operator will not be displayed on the screen, and will not be

stored in the alarm history. The following inputs are required to execute

the command.


- CONNECT_BD_ID: ID of the board connected to the unit.

- CONNECT_PORT_ID: ID of the port connected to the unit.

- CASCADE_ID: Cascade ID of the unit.



The command execution procedure is as follows:

[RTRV-ALM-INH]

1) Select the RTRV-ALM-INH command in the FM folder on the CLI window and click

the Execute button.


[CHG-ALM-INH]

1) Select the CHG-ALM-INH command in the FM folder on the CLI window, enter the

parameters, and click the Execute button.


3) When this command is executed for the occurred alarm, check whether the alarm is

cleared.

[RTRV-RDALM-INH]

1) Select the RTRV-RDALM-INH command in the FM folder on the CLI window, enter

the parameters, and click the Execute button.




[CHG-RDALM-INH]

1) Select the CHG-RDALM-INH command in the FM folder on the CLI window, enter

the parameters, and click the Execute button.


3) When this command is executed for the occurred alarm, check whether the alarm is

cleared.

9.5.5 Retrieving/Changing Alarm Severity

Retrieves or changes the alarm levels.

Execute the CHG-ALM-SEV command to change the levels to and from „Critical‟, „Major‟,

or „Minor‟. Execute the RTRV-ALM-SEV or RTRV-ALM-INF command to view the changes.


Command Description

RTRV-ALM-SEV Retrieves the severity of the eNB alarm. The following output will be

returned:





CHG-ALM-SEV Changes the severity of the eNB alarm. The operator can change the

severity of the alarm with this command. When the alarm is generated,

the alarm's severity level modified by the CHG-ALM-SEV command will

be displayed on the operator screen. The alarm's modified severity level

can be retrieved with the RTRV-ALM-SEV command. The following

inputs are required to execute the command.

- UNIT_TYPE: Type of the unit where the alarm is generated.




[RTRV-ALM-SEV]

1) Select the RTRV-ALM-SEV command in the FM folder on the CLI window and click

the Execute button.


[CHG-ALM-SEV]

1) Select the CHG-ALM-SEV command in the FM folder on the CLI window, enter the



3) When this command is executed for an occurred alarm, check whether the alarm of the

previous level has been cleared and the alarm of the changed level occurred.



9.5.6 Retrieving/Changing Alarm Threshold

Views or Changes the thresholds for the alarms that have thresholds set. The OVERLOAD,

DISK FULL, and MEMORY FULL are the alarms that have thresholds. Execute the CHG-

ALM-THR command to change the thresholds. Execute the RTRV-ALM-THR or RTRV-

ALM-INF command to view the alarm thresholds.


Command Description

RTRV-ALM-THR Retrieves the threshold of the eNB alarm. The command will output the

following information:




- THRESHOLD_CRITICAL: Critical threshold.

- THRESHOLD_MAJOR: Major threshold.

- THRESHOLD_MINOR: Minor threshold.

CHG-ALM-THR Changes the threshold of the eNB alarm. The operator can change the

threshold of the alarm with this command. If an alarm exceeds the

predefined threshold, the eNB displays the alarm with the level changed

accordingly on the operator screen. The modified alarm threshold can be

retrieved with the RTRV-ALM-THR command. The following inputs are

required to execute the command.



- THRESHOLD_CRITICAL: Critical threshold.

- THRESHOLD_MAJOR: Major threshold.

- THRESHOLD_MINOR: Minor threshold.


[RTRV-ALM-THR]

1) Select the RTRV-ALM-THR command in the FM folder on the CLI window and click

the Execute button.


[CHG-ALM-THR]

1) Select the CHG-ALM-THR command in the FM folder on the CLI window, enter the



3) When this command is executed for an occurred alarm, check whether the alarm level

is changed to the level that matches the new threshold entered or whether the alarm is

cleared.



9.5.7 Retrieving/Changing UDA

When an external device is installed, the operator can detect and manage faults that occur

in the external device by connecting the device to the UDA port of the system.

This function for retrieving/changing the UDA allows you to set or view the alarm name

and level for each UDA port.

To change the UDA, run the CHG-UDA-DATA command, and set the alarm name and

level of the UDA object, and change the status to EQUIP. If changing the alarm name for

the UDA port in the alarm occurrence status using the CHG-UDA-DATA command, the

alarm of the previous name is cleared and the alarm of the changed name occurs, and if

changing the alarm level, the alarm of the previous level is cleared and the alarm of the

changed level occurs.


Command Description

RTRV-UDA-DATA Retrieves the UDA data. The command will output the following information:

- PORT_ID: UDA port ID.

- STATUS: Whether the UDA port is in use.

- ALARM_NAME: User-defined alarm name.


CHG-UDA-DATA Sets the UDA data. The following inputs are required to execute the

command.

- PORT_ID: UDA port ID.

- STATUS: Whether the UDA port is in use.

- ALARM_NAME: User-defined alarm name.



[RTRV-UDA-DATA]

1) Select the RTRV-UDA-DATA command in the FM folder on the CLI window and

click the Execute button.


[CHG-UDA-DATA]

1) Select the CHG-UDA-DATA command in the FM folder on the CLI window, enter the



3) If an alarm is generated in the UDA port, check whether the alarm occurred is in

accordance with the entered alarm name and level.



CHAPTER 10. Statistics

The performance management collects and processes the performance data necessary for

system operation, and provides them to the operator.

The functions provided by the performance management are as follows.

Collecting statistical data and creating statistics files

Setting and viewing the statistics configuration

10.1 Collecting Statistics and Creating Statistics Files

The procedure for collecting and reporting statistical data (PM data) is as follows:

Figure 10.1 Collecting and Reporting Statistics (PM Data)

Each board saves events and statistical data that occurred during the system operation, and

transmits them to the UMP. The UMP records in the memory the data sent from the boards

and data generated internally, and creates a statistics file (.csv) every 5 minutes.

Statistics files are transmitted to the LSM using the FTP and are backed up in a specified

location.

The LSM views and processes the transmitted statistics file, and then stores it to the DB.

Then, upon operator request, the LSM provides the statistics data in an appropriate format.

UAMA (UMP) L9CA (ECP)

Modem

PM data PM data

PM

data

LSM



Validity and normality of the data saved in the statistics file can be checked as the

following:

ND: No Data

There is no data that the eNB reported to the LSM. „ND‟ output to the LSM.

PLD N_Equip

Abnormal communication between the eNB and LSM.

No statistics collected (for example, due to eNB or PM failures).

NG (-1): Not Good

„NG‟ output to the LSM.

Faults in the collected objects due to dismounts or abnormal communications.

allZero (0)

The eNB fills out a data flag with 0, and the entire index of the statistics item is

outputted as 0.

Data found (1)

The eNB fills out a data flag with 1, and fills a data field with actual data collected.

Statistics are collected as follows.

GAUGE: Gets the maximum, minimum and average values of the raw data collected

for 5 minutes.

Cumulative Counter (CC): Counts the event every time it occurs and calculates the

number of events occurred for 5 minutes.

Status Inspection (SI): Measures the data at the specified interval and calculates the

mean value of the data measured for 5 minutes.

Overwrite (OW): Overwrites a value every time an event occurs.



10.2 Setting and Viewing the Statistics Configuration

In configuration settings for performance management, you can retrieve information on

overall statistics data collection, resume or stop collecting overall statistics data, change the

data collection status, and retrieve or change information on the statistics file backup using

the CLI.

The following commands are used for viewing and setting the statistics data information.

Command Description

RTRV-MEAS Retrieves information on overall statistics data collection.

START-MEAS Resumes collecting overall statistics data.

STOP-MEAS Stops collecting overall statistics data.

CHG-MEAS-INF Changes the status of statistics data collection.

RTRV-MEAS-FILEDATA Retrieves information on the statistics file backup.

CHG-MEAS-FILEDATA Changes information on the statistics file backup.

RTRV-MEAS: Retrieve information on overall statistics data collection

This command retrieves the eNB‟s statistics collection status (stop/start) and the statistics

collection status (enable/disable) for each family.

When executed successfully

eNB_2580 2011-06-17 FRI 05:14:57

M0352 DISPLAY MEASUREMENT JOB INFORMATION: COMPLD

===========================================

FAMILY_ID FAMILY_STATUS

===========================================

STAT_RRC_ESTAB OPM_ENABLE

STAT_RRC_RECONFIG OPM_ENABLE

STAT_RRC_REESTAB OPM_ENABLE

STAT_RRC_RELEASE OPM_ENABLE

STAT_RRC_CONN OPM_ENABLE

STAT_RRC_TIME OPM_ENABLE

STAT_RRC_RESETUP_TIME OPM_ENABLE

STAT_ERAB_ESTAB OPM_ENABLE

STAT_ERAB_ESTAB_ADD OPM_ENABLE

STAT_ERAB_TIME OPM_ENABLE

STAT_ERAB_ERASE_ENB OPM_ENABLE

STAT_ERAB_ERASE OPM_ENABLE

STAT_ERAB_MOD OPM_ENABLE

STAT_ERAB_REL_ENB OPM_ENABLE

STAT_ERAB_REL OPM_ENABLE

STAT_ERAB_NUM OPM_ENABLE

STAT_HO_INTRA OPM_ENABLE



STAT_HO_X2_OUT OPM_ENABLE

STAT_HO_X2_IN OPM_ENABLE

STAT_HO_S1_OUT OPM_ENABLE

STAT_HO_S1_IN OPM_ENABLE

STAT_HO_INTER_RAT_HRPD OPM_ENABLE

STAT_HO_TIME OPM_ENABLE

STAT_CALL_DROP OPM_ENABLE

STAT_CSL OPM_ENABLE

STAT_MRO_RLF OPM_ENABLE

STAT_S1SIG OPM_ENABLE

STAT_PAGING OPM_ENABLE

STAT_TA OPM_ENABLE

STAT_CP_PACKET OPM_ENABLE

STAT_SRB OPM_ENABLE

STAT_ACTIVE_UE OPM_ENABLE

STAT_PDCP_DROP OPM_ENABLE

STAT_PDCP_LOSS OPM_ENABLE

STAT_IP_LATENCY OPM_ENABLE

STAT_PDCP_DELAY OPM_ENABLE

STAT_GTP_SN_QCI OPM_ENABLE

STAT_GTP_SN_ENB OPM_ENABLE

STAT_GTP_FW_ENB OPM_ENABLE

STAT_RESOURCE OPM_ENABLE

STAT_PACKET OPM_ENABLE

STAT_NET_HISTOGRAM OPM_ENABLE

STAT_QOS_INFO OPM_ENABLE

STAT_AIR_RLC_BYTES OPM_ENABLE

STAT_AIR_MAC_BYTES OPM_ENABLE

STAT_PRB_QCI OPM_ENABLE

STAT_PRB_TOTAL OPM_ENABLE

STAT_CELL_UNAVAILABLE OPM_ENABLE

STAT_POWER OPM_ENABLE

STAT_RNTP OPM_ENABLE

STAT_RA OPM_ENABLE

STAT_TRANSMISSION OPM_ENABLE

STAT_MIMO OPM_ENABLE

STAT_MCS OPM_ENABLE

STAT_DL_MCS OPM_ENABLE

STAT_DL_LAYER OPM_ENABLE

STAT_DL_CQI OPM_ENABLE

STAT_DL_PMI OPM_ENABLE

STAT_DL_RI OPM_ENABLE

STAT_DL_ACK_NACK_DTX_RATIO OPM_ENABLE

STAT_ANR OPM_ENABLE

STAT_IOT_9LEVEL OPM_ENABLE

STAT_PCI_300_REPORT OPM_ENABLE

STAT_PCI_504_REPORT OPM_ENABLE

STAT_ERAB_SESSION_UE OPM_ENABLE

STAT_ERAB_SESSION_QCI OPM_ENABLE

STAT_HO_INTER_RAT_UTRAN_OUT OPM_ENABLE

STAT_HO_INTER_RAT_UTRAN_IN OPM_ENABLE

STAT_CSFB_PSHO_UTRAN_OUT OPM_ENABLE

STAT_CSFB_REDIR_UTRAN_OUT OPM_ENABLE

STAT_IEEE1588_VISIBLE_MASTER OPM_ENABLE



STAT_MLBO OPM_ENABLE

STAT_ACCESSIBILITY OPM_ENABLE

STAT_INTEGRITY OPM_ENABLE

STAT_AVAILABILITY OPM_ENABLE

STAT_MOBILITY OPM_ENABLE

STAT_RF OPM_ENABLE

STAT_TX_DIGITALIQ OPM_ENABLE

STAT_IOT OPM_ENABLE

===========================================

GRANULARITY_PERIOD = MIN_15

REPORTING_PERIOD = MIN_15

STATUS = OPM_ACTIVE

RESULT = OK

;

When executed abnormally

eNB_2580 2011-06-17 FRI 06:18:49

M0352 DISPLAY MEASUREMENT JOB INFORMATION: DENY

RESULT = NOK

REASON = Parameter is Unknown (1th Parameter)

Output parameter

Output parameter Description

familyId The family name of eNB‟s statistics collection

familyStatus The collection status of each statistics family of the eNB. (enable/disable)

granularityPeriod The period for data collection period. The value can be set to 5 min, 15 min,

30 min, or 1 hour.

MIN_5 = 0,

MIN_15 = 1,

MIN_30 = 2,

MIN_60 = 3

reportingPeriod MIN_5 = 0,

MIN_15 = 1,

MIN_30 = 2,

MIN_60 = 3

status The status of the data collection task.

OPM_ACTIVE = 0,

OPM_SUSPEND = 1



START-MEAS: Resume Collecting Statistics

This command resumes the collection of the eNB's statistics, which was stopped.


eNB_2580 2011-06-17 FRI 05:22:19

M0350 RESUME MEASUREMENT JOB: COMPLD

RESULT = OK

;


eNB_2580 2011-06-17 FRI 05:21:56

M0350 RESUME MEASUREMENT JOB: DENY

RESULT = NOK

REASON = Intended operation result is already applied

;

STOP-MEAS: Stop Collecting Statistics

This command stops the eNB‟s statistics collection function.


eNB_2580 2011-06-17 FRI 06:03:47

M0351 SUSPEND MEASUREMENT JOB: COMPLD

RESULT = OK;

;


eNB_2580 2011-06-17 FRI 06:03:25

M0351 SUSPEND MEASUREMENT JOB: DENY

RESULT = NOK

REASON = Intended operation result is already applied;

;



CHG-MEAS-INF: Change Collection Status of Statistics

This command changes the collection status (enable, disable) of each statistics family of

the eNB.


eNB_133 2011-07-26 TUE 12:39:12

S0352 NOTIFY ATTRIBUTE CHANGE

OBJ_CLASS = PmMeasurementJobData

OBJ_INST = jobId=0,FamilyId=78

NOTI_ID = 98

EVENT_TIME = 2011-07-26T12:39:12Z

SYSTEM_DN = 20.1.1.133

NOTI_TYPE = notifyAttributeValueChange

STATION_ID = 0

FAMILY_ID = STAT_CSFB_REDIR_UTRAN_OUT

STATUS = OPM_DISABLE

;


eNB_133 2011-07-26 TUE 12:40:24

M0353 CHANGE MEASUREMENT JOB DATA: DENY

RESULT = NOK

REASON = Invalid Parameter Value (STATUS: ENUM

[OPM_ENABLE/OPM_DISABLE] )

;

Input Parameter

Input Parameter Range Description

FamilyId FAMILY_ID Measurement family ID

status OPM_ENABLE,

OPM_DISABLE

The collection status of the family data

- OPM_ENABLE: Collects the family data.

- OPM_DISABLE: Does not collect the family data.

Output parameter


FamilyId Measurement family ID

status The collection status of the family data

- OPM_ENABLE: Collects the family data.

- OPM_DISABLE: Does not collect the family data.



RTRV-MEAS-FILEDATA: Retrieve Statistics Backup Data

This command displays the PM file backup related data.


eNB_133 2011-07-26 TUE 12:42:55

M0356 RETRIEVE PM FILE DATA: COMPLD

DISK_USAGE_THR = 95

BACKUP_TIME_THR = 8

ALWAYS_FLASH_BACKUP_ENABLE = 0

RESULT = OK

;


eNB_133 2011-07-26 TUE 12:43:17

M0356 RETRIEVE PM FILE DATA: DENY

RESULT = NOK

REASON = Parameter is Unknown (1th Parameter)

;

Output parameter


DiskUsageThr The disk usage threshold After creating the statistics file, if the

current NE disk usage exceeds the threshold, it deletes the statistics

backup file.

BackupTimeThr Statistics file storage time

AlwaysFlashBackupEnable Regular backup of the statistics to the Flash memory (on/off flag)



CHG-MEAS-FILEDATA: Change Statistics Backup data

This command changes the PM file backup related data.


eNB_133 2011-07-26 TUE 12:44:05

M0357 CHANGE PM FILE DATA: COMPLD

DISK_USAGE_THR = 95

BACKUP_TIME_THR = 7

ALWAYS_FLASH_BACKUP_ENABLE = 0

RESULT = OK

;


eNB_133 2011-07-26 TUE 12:44:59

M0357 CHANGE PM FILE DATA: DENY

RESULT = NOK

REASON = Invalid Parameter Value (ALWAYS_FLASH_BACKUP_ENABLE: INT

(DEC) [0~1] )

;

Input Parameter

Input Parameter Range Description

DiskUsageThr 1~100 The disk usage threshold After creating the statistics

file, if the current NE disk usage exceeds the threshold,

it deletes the statistics backup file.

BackupTimeThr 1~8 Statistics file storage time

AlwaysFlashBackupEnable 0~1 Regular backup of the statistics to the Flash memory

(on/off flag)

Output parameter


DiskUsageThr The disk usage threshold After creating the statistics file, if the

current NE disk usage exceeds the threshold, it deletes the

statistics backup file.

BackupTimeThr Statistics file storage time

AlwaysFlashBackupEnable Regular backup of the statistics to the Flash memory (on/off flag)



10.3 Statistics Items

The statistics items for which the eNB collects statistics data, and their corresponding

names that are displayed in the Performance Manager of the LSM are given below.

Statistics Items

Category Statistics Item (Displayed in Performance Manager)

Resource Management RESOURCE

Packet Statistics Ethernet Interface

Histogram

QoS Information

Air Mac UL/DL bytes

Air RLC UL/DL bytes

S-GW UL/DL packets

RRC RRC connection establishments

RRC connection Reconfiguration

RRC connection re-establishments

RRC connection Release

RRC connection number

RRC connection setup time

RRC connection reestablishment time

Call Drop

ERAB E-RAB Setup

E-RAB Setup Add

E-RAB setup time

eNB E-RAB erase request

E-RAB erase

E-RAB modify

eNB E-RAB Release request

E-RAB release

E-RAB activity (UE)

E-RAB activity (QCI)

E-RAB simultaneous number

HO Intra eNB Handover

X2 Handover Out

X2 Handover In

S1 Handover Out

S1 Handover In

Inter-RAT HRPD Handover (Other than eNB)

Inter-RAT UTRAN PS Handover OUT



(Continued)

Category Statistics Item (Displayed in Performance Manager)

HO Inter-RAT UTRAN PS Handover IN

Handover Time (Average, Max)

CSFB CSFB PS Handover OUT

CSFB Redirection OUT

CSL Call Fail Report

MRO RLF MRO RLF Classification

GTP GTP Sequence Number by QCI

GTP Sequence Number by eNB

GTP Forward Traffic

SRB Cell PDCP SDU bit-rate

DRB Active UEs

Packet Delay

Packet Drop Rate

Packet loss rate

IP Latency measurements

RRU DL/UL PRB Usage

DL/UL Total PRB Usage

Cell Unavailable Time

S1SIG UE-associated logical S1-connection establishment

PAG Paging Performance

POWER Power

RNTP of own cell

RA Random Access Preambles

HARQ status DL/UL transmission

AMC MIMO

MCS

DL MCS

DL LAYER

DL CQI

DL PMI

DL RI

DL ACK/NACK/DTX Ratio

KPI Accessibility

Integrity

Availability

Mobility



Among the above statistics items, the RRC connection establishments, RRC connection re-

establishments, RRC connection Release, Call Drop, E-RAB Setup, E-RAB Setup Add,

E-RAB modify, E-RAB release, Intra eNB Handover, X2 Handover, S1 Handover, Inter-

RAT HRPD Handover, Inter-RAT UTRAN, CSFB PS Handover OUT and CSFB

Redirection OUT statistics commonly use Failure Cause as the statistics type.

Statistics Prefix

When using Failure Cause as the statistics type, the prefix is defined as follows:

Prefix Description

ConnEstabFail_ RRC_ESTAB Fail

ConnEstabReject_ RRC_ESTAB Reject

ConnReEstabFail_ RRC_REESTAB Fail

ConnReEstabReject_ RRC_REESTAB Reject

ConnRelease_ RRC_RELEASE

CallDrop_ CALL_DROP

EstabInitFailNbr_ ERAB_ESTAB Fail

EstabAddFailNbr_ ERAB_ESTAB_ADD Fail

ModQoSFailNbr_ ERAB_ESTAB_MOD Fail

RelFailNbr_ ERAB_REL Fail

IntraEnbPrepFail_ HO_INTRA Preparation Fail

IntraEnbFail_ HO_INTRA Execution Fail

InterX2OutPrepFail_ X2_OUT Preparation Fail

InterX2OutFail_ X2_OUT Execution Fail

InterX2InPrepFail_ X2_ IN Preparation Fail

InterX2InFail_ X2_IN Execution Fail

InterS1OutPrepFail_ S1_OUT Preparation Fail

InterS1OutFail_ S1_OUT Execution Fail

InterS1InPrepFail_ S1_IN Preparation Fail

InterS1InFail_ S1_IN Execution Fail

RatOutPrepFailHPRD_ Inter RAT Preparation Fail

RatOutFailHPRD_ Inter RAT Execution Fail



Statistics fail cause list

Refer to the table below for the fail cause that comes after the prefix.

No Statistics Fail Cause Description

0 S1AP_CauseRadioNetwork_

unspecified

A failure occurs in GW during the handover, or the handover

preparation fails if the MME cannot process the handover.

1 S1AP_ho_failure_in_target_

EPC_eNB_or_target_system

The handover preparation fails in the target EPC.

2 S1AP_ho_target_not_allowed The handover to the target cell is not allowed if the target

eNB is listed in the handover restriction list.

3 S1AP_tS1relocprep_expiry The timer expires while the source eNB sends the Handover

Required message and waits for the handover command.

4 S1AP_unknown_targetID The handover preparation fails because the MME does

not recognize the target ID received from the Source

eNB.

5 S1AP_no_radio_resources_

available_in_target_cell

A handover preparation failure is received from the MME.

6 S1AP_invalid_qos_

combination

An action fails due to the invalid QoS combination.

7 S1AP_authentication_failure The call is cancelled by the MME due to the terminal

authentication failure during the UE attach.

8 S1AP_CauseNas_unspecified The Context Release Command message is sent due to

an unspecified failure in the MME.

9 S1AP_csg_subscription_

expiry

The UE is not registered in the target cell‟s CSG, or its

registration has expired.

10 S1AP_CauseMisc_unspecified UE duplication occurs in the MME.

11 S1AP_Others Other causes defined in the S1AP specification occur.

12 X2AP_trelocprep_expiry A timeout occurs during the handover preparation in the

Source eNB while processing the X2 handover.

13 X2AP_no_radio_resources_


A handover preparation failure is received from the Target

eNB.

14 X2AP_CauseMisc_unspecified Default X2 cause in the eNB.

15 X2AP_Others Other causes defined in the X2AP specification occur.

16 ECC_TMOUT_

rrcConnectionSetup

The RRC Connection Setup Complete message is not

received after sending the RRC Connection Setup

message to the UE.

17 ECC_TMOUT_

rrcConnectionReconfig

The RRC Connection Reconfiguration Complete message

is not received after sending the RRC Connection

Reconfiguration message during the UE attach.



(Continued)


18 ECC_TMOUT_rrcConnection

ReEstablish

The RRC Connection Reestablishment Complete

message is not received after sending the RRC

Connection Reestablishment message to the UE.

19 ECC_TMOUT_

rrcSecurityModeCommand

The Security Mode Complete message is not received

after sending the Security Mode Command message to

the UE.

20 ECC_TMOUT_

rrcUeCapabilityEnquiry

The UE Capability Information message is not received

after sending the UE Capability Enquiry message to the

UE.

21 ECC_TMOUT_

rrcHandoverPreparation

The UL Handover Preparation Transfer message is not

received after sending the Handover From EUTRA

Preparation Request message.

22 ECC_TMOUT_intra_

HandoverCmdComplete

The target cell cannot receive the RRC Connection

Reconfiguration Complete message while processing the

intra-handover.

23 ECC_TMOUT_inter_

X2HandoverCmdComplete

The Target eNB cannot receive the RRC Connection


X2 handover.

24 ECC_TMOUT_inter_

S1HandoverCmdComplete

The Target eNB cannot receive the RRC Connection


S1 handover.

25 ECC_TMOUT_

s1InitialContextSetup

The call is cancelled because the Initial Context Setup

Request message is not received after sending the Initial

UE message to the MME.

26 ECC_TMOUT_s1PathSwitch The call is cancelled because the Path Switch Request

Acknowledge message is not received after the Target

eNB sends the Path Switch Request message while

processing the X2 handover.

27 ECC_TMOUT_

s1RelocOverall

The call is cancelled because a RelocOverall Timeout

occurred in the SeNB while processing the S1 handover.

28 ECC_TMOUT_

s1MMEStatusTransfer

The TeNB cannot receive the MME Status Transfer

message after the SeNB sends the eNB Status Transfer

message to the MME.

29 ECC_TMOUT_

x2RelocOverall

The call is cancelled because a RelocOverall Timeout

occurred in the SeNB while processing the X2 handover.

30 ECC_TMOUT_

x2SNStatusTransfer

The TeNB cannot receive the X2SNStatus Transfer

message sent from the SeNB.

31 ECC_TMOUT_

internalResourceSetup

The response message is not received after the

SetupReq message is sent for setting the resource for the

internal protocol blocks of the eNB.

32 ECC_TMOUT_

internalSecurityControl

The msgCpdcpSecurityControlSuccess message is not

received after the msgCpdcpSecurityControl message is

sent to the PDCB.



(Continued)


33 ECC_TMOUT_

internalForwardingPathSetup

The msgCgtpSetupCnf message is not received after the

msgCgtpSetupReq message is sent to the GTPB to set

the uplink and downlink path during the handover.

34 ECC_TMOUT_

internalReestablishControl

The msgCrlcControlSuccess or

msgCpdcpControlSuccess message are not received

after sending the msgCrlcControl or msgCpdcpControl

message to reestablish the RLC or PDCP during the

X2/S1 handover.

35 ECC_TMOUT_

internalBufferFlush

The msgCpdcpBufferFlushCnf message is not received

after the msgCpdcpBufferFlush message is sent to the

PDCB during handover.

36 ECC_TMOUT_

internalDataTransferStart

The msgCpdcpControlSuccess message is not received

after the msgCpdcpControl message is sent.

37 ECC_Others1 Other RRC related timeout occurs.

38 ECC_USER_INACTIVITY A User Inactivity notification is received from the MAC.

39 ECC_ARQ_MAX_RE_

TRANSMISSION

A Max Retransmission notification is received from the

RLC.

40 ECC_RADIO_LINK_

FAILURE

A Radio Link Fail (RLF) notification is received from the

MAC.

41 ECC_UE_CONTEXT_NOT_

FOUND

Although the UE requested the Reestablishment,

Reestablishment cannot be performed because could not

find the UE Context information in eNB.

42 ECC_SN_STATUS_NOT_

RECEIVED

The SN Status Transfer message is not received from the

source eNB during handover. Or the MME Status

Transfer message is not received from the MME.

43 ECC_REEST_FAIL_INVALID_

STATE

A RRC Connection Reestablishment Request message is

received during the UE attach.

44 ECC_CDMA_HANDOVER_

PREPARATION_FAILURE

Handover preparation to the CDMA system fails.

45 ECC_RCV_S1_

UECTXTRELEASECMD_

ABNORMAL_STATE

A UE Context Release Command message is received

from the base station when the UE Context Release

Command isn‟t expected to be issued.

46 ECC_RCV_RESET_

REQUEST_FROM_ECMB

The call is cancelled due to the reception of the Reset

Request message from the ECMB block.

47 ECC_RCV_S1_RESET_

FROM_MME

The call is cancelled due to the reception of the Reset

message from the MME.

48 ECC_RCV_X2_

RESETREQUEST

The call needs to be cancelled due to the reception of the

Reset Request message from other eNB.

49 ECC_S1_SCTP_OUT_OF_

SERVICE

The call needs to be cancelled because the status of S1

Association is Out of Service.



(Continued)


50 ECC_RCV_CELL_RELEASE_IND_

FROM_ECMB

The call needs to be cancelled due to the

reception of the Cell Release Ind message from

the ECMB block.

51 ECC_DSP_AUDIT_RLC_CALL_

RELEASE

The call is cancelled due to the resource

mismatch, because the ECCB and the MAC

have remaining calls but the RLC has no call

remaining.

52 ECC_DSP_AUDIT_MAC_CALL_

RELEASE

The call is cancelled due to the resource mismatch,

because the ECCB and the RLC have remaining

calls but the MAC has no call remaining.

53 ECC_DSP_AUDIT_RLC_MAC_CALL_

RELEASE

The call is cancelled due to the resource

mismatch, because the ECCB has remaining

calls but the RLC and the MAC have no call

remaining.

54 ECC_SEC_ALGORITHMS_

COMBINATION_INVALID

The Security Algorithm value within the Initial

Context Setup Request, S1 Handover Request,

X2 Handover Request or S1 UE Context

Modification message is received. If the integrity

algorithm supports Null Algorithm, the ciphering

algorithm must also receive the Null Algorithm

value. Otherwise, the call is cancelled.

55 ECC_X2_SCTP_OUT_OF_SERVICE The call needs to be cancelled because the

status of X2 Association is Out of Service.

56 ECC_RELEASE_DUE_TO_ENB_

GENERATED_REASON

The call is cancelled due to the internal cause of

the base station.

57 ECC_Others2 Other RRC related cause occurs.

58 RRM_CELL_BARRED If calls are generated by the cell being barred by

the operator, they are rejected by CAC.

59 RRM_MAX_CALL_COUNT_OVER If calls are generated for more than the number

of calls that can be accommodated, they are

rejected by CAC.

60 RRM_MAX_DRB_COUNT_OVER If calls are generated for more than the number

of DRB that can be accommodated by cell, they

are rejected by CAC.

61 RRM_QOSCAC_FAIL If calls with the QoS that cannot be

accommodated by cell, they are rejected by CAC.

62 RRM_BHCAC_FAIL The BH link usage by a specific QoS (GBR

Bearer) exceeds the threshold defined in the PLD.



(Continued)


63 RRM_CALLID_DB_FULL Call ID is all assigned thus cannot assign Call ID

further.

64 RRM_CALLID_DB_ABNORMAL Call ID cannot be assigned because the DB

managing the Call ID is not normal.

65 RRM_SRS_MUST_BE_ASSIGNED If a new call supports both SRS and DRX, the SRS

resources need to be assigned in advance to

assign the DRX resources but the DRX resources

cannot be assigned because the SRS resource is

not assigned.

66 RRM_CQIPMI_DB_ABNORMAL Because CQI/PMI internal DB is Abnormal,

CQI/PMI resource cannot be assigned to new

calls.

67 RRM_CQIPMI_DB_FULL CQI/PMI resources are all assigned and not

available any more.

68 RRM_SPS_DB_ABNORMAL During SPS resource assignment and cancellation,

the SPS resource search is not allowed to exceed

the Max value of the SPS resource DB.

69 RRM_SPS_DB_FULL SPS resources are all assigned thus the SPS

resource cannot be assigned any more.

70 RRM_SPS_ALREADY_ASSIGNED Assigning duplicate resources is not allowed since

the SPS resources are already assigned.

71 RRM_SPS_RNTI_FULL The RNTI used for SPS is all assigned and not

available anymore.

72 RRM_N1PUCCHAN_REP_DB_

ABNORMAL

n1PucchAnRep resources are all assigned and not

available anymore.

73 RRM_N1PUCCHAN_REP_

ALREADY_ASSIGNED

Since there are already assigned resources

regarding the N1PUCCHAN_REP on the call, it is

not assigned.

74 RRM_SR_DB_ABNORMAL During SR resource assignment and cancellation,

the SR resource search is not allowed to exceed

the Max value of the SR resource DB.

75 RRM_SR_DB_FULL SR resources are all assigned and not available

anymore.

76 RRM_SR_ALREADY_ASSIGNED Since there are already assigned resources

regarding the SR on the call, it is not assigned.

77 RRM_SRS_DB_ABNORMAL During SR resource assignment and cancellation,

a database search for the SRS resource exceeds

the range of resources secured.

78 RRM_SRS_DB_FULL SRS resources are all assigned.

79 RRM_SRS_ALREADY_ASSIGNED Since there are already assigned resources

regarding the SRS on the call, it is not assigned.



(Continued)


80 RRM_TPC_PUCCH_RNTI_

FULL

TPC PUCCH RNTI resources are all assigned and not

available anymore.

81 RRM_TPC_PUCCH_RNTI_

ALREADY_ASSIGNED

Assigning duplicate resources is not allowed since the

TPC PUCCH resources are already assigned.

82 RRM_SPS_MUST_BE_

ASSIGNED

To assign TPC PUSCH resources, the SPS resources

should be assigned but not assigned.

83 RRM_TPC_PUSCH_RNTI_

FULL

RNTIs used for the TPC PUSCH purpose are all assigned

and not available any more.

84 RRM_TPC_PUSCH_RNTI_

ALREADY_ASSIGNED

Assigning duplicate resources is not allowed since the

TPC PUSCH resources are already assigned.

85 RRM_ALL_MME_NOT_

SERVICE

The call is rejected because there is no MME currently in

connection.

86 RRM_MME_OVERLOAD When the MME is in Overload status, the calls cannot be

accommodated because overloadAction and

establishmetCause do not match.

87 RRM_NOT_EXIST_MME In MME Pool, a specific MME ID does not exist.

88 RRM_AVAILABLE_MME_

NOT_EXIST

The MME to accommodate new calls does not exist.

89 RRM_UE_STMSI_

DUPLICATE

The same UE transmits the RRC Connection Request with

the same S-TMSI value.

90 RRM_Others Other RRM related cause occurs.

91 GTP_Setup_Failure The GTP Setup fails after receiving the SetupReq

message from the ECCB.

92 GTP_Modify_Failure The GTP Modify fails after receiving the ModifyReq


93 GTP_Path_Failure After the SetupReq message is received from the ECCB, a

series of the GTP setup starts: create a GTP tunnel, set a

timer to the echo request message to be sent to the dstip

of the message, and respond to the ECCB if a response is

not received three times within the time limit.

94 GTP_GTP_Error_Ind The Error Indication message from the dst peer is

received. Then a response to cancel the call is sent to the

ECCB.

95 GTP_Others Other GTP related cause occurs.

96 PDCP_Invalid_Callid The call ID of the downloaded message from the ECCB is

above the value of the MAX_USER_ENB.

97 PDCP_Invalid_RBid A response is sent to notify that the message downloaded

from the ECCB is valid if the message is PDCP_DRB or

PDCP_SRB and the Rbid is below MAX_RB or MAX_SRB

respectively. Otherwise, an invalid message response is

sent.



(Continued)


98 PDCP_Invalid_NumRb The NumRb of the message downloaded from the ECCB

is above the value of CI_MAX_RB.

99 PDCP_Rohc_Setup_Failure The ROHC context setup procedure fails due to lack of

memory while receiving ConfigReq from the ECCB.

100 PDCP_Inactive_RBid The Inactive RB message is received while receiving the

msgCpdcpModifyReq from the ECCB.

101 PDCP_Others Other PDCP related cause occurs.

102 RLC_ECCB_INVALID_CEL

LNUM

The cell number of the message received from the ECCB

is greater than the maximum cell number defined.

103 RLC_ECCB_CELL_IS_

IDLE

The cell ID status of the message received from the ECCB

is IDLE, not ACTIVE.

104 RLC_ECCB_INVALID_

CALL_ID

The call ID of the message received from the ECCB is not

the value within the defined range.

105 RLC_ECCB_IVALID_NUM_

RB_UNMATCH

There is no mapping value for the RB value of the

message received from the ECCB.

106 RLC_ECCB_CALL_IS_

NOT_ACTIVE

The call ID status of the message received from the ECCB

is not ACTIVE.


CELLCALL_ID

The cell call ID of the message received from the ECCB is

not within the defined range.

108 RLC_ECCB_LACK_OF

NUMOFRB

New connections are not allowed due to insufficient RBs

that can be allocated to the message received from the

ECCB.

109 RLC_ECCB_DL_LACK_

OF_AMDWINDOW_POOL

New connections are not allowed due to insufficient AMD

window pools that can be allocated to the message

received from the ECCB.

110 RLC_ECCB_UL_NO_

MORE_WIN_TAG_POOL

There is not enough window tag pools that can be

allocated to the message received from the ECCB.

111 RLC_ECCB_INVALID_NU

M_CALL

The num call value of the message received from the

ECCB is not within the defined range.


CALLID_UNMATCH

The cell call ID and the CallID of the message received

from the ECCB do not match.

113 RLC_ECCB_NOT_

EQUIPPED_QCI

The QCI in the message received from the ECCB is not in

equipped status.

114 RLC_ECCB_UL_NO_

MORE_CALL_POLL

There is not enough call pools that can be allocated to the


115 RLC_ERROR_INVALID_

DATA_LEN

The error code is sent when the size of the message

received from the RLC is incorrect.

116 RLC_ERROR_NO_RSP_

FROM_DL

The error code is sent when the response message is not

received from the RLC downlink.



(Continued)



FROM_UL


received from the RLC uplink.


FROM_DLUL


received from the RLC downlink and uplink.

119 RLC_ERROR_RX_

BEFORE_RLC_READY

The error code is sent when a signaling message is

received before the RLC uplink is properly started.


RLC_TRANSACTION_ID

The error code is sent when the transaction ID exceeds

the specified range while the RLC processes the message

received from the ECCB and ECMB.


CONTEXT

The error code is sent when a reply for the signaling

message already processed by the RLC is received from

the RLC downlink.

122 RLC_ERROR_RLC_

CONTEXT_FULL

The error code is sent when the number of signaling

message received exceeds the RLC capacity.


CELLNUM

The error code is sent if the RLC cannot process the cell

num.

124 RLC_Others Other RLC related cause.

125 MAC_INVALID_CALL_

CELLID

The call cell ID of the message received from the ECCB is

not within the defined range.

126 MAC_INVALID_

PARAMETER

A parameter received is outside the allowed range.

127 MAC_INSUFFICIENT_

RESOURCE

The RB cannot be allocated due to the insufficient MACB

internal resource required to manage the RB.

128 MAC_NOT_ASSIGNED_

RB

A reconfig/delete request is received on the RB that is not

allocated.

129 MAC_NOT_ASSIGNED_

UE

A config/delete request is received on the UE that is not

allocated.

130 MAC_Others Other MAC related cause occurs.



10.3.1 Resource Management

It is the statistics of the CPU, memory and disk resources used by the internal applications.

The descriptions of each statistics are as follows:

CPU Usage: Collects and displays the CPU‟s average, maximum and minimum usage in %.

Memory Usage: Collects and displays the DRAM‟s average, maximum and minimum usage in %.

Disk Usage: Collects and displays the disk‟s average, maximum and minimum usage in %.

RESOURCE

It measures the usage of the system resource. It collects the average and maximum usage of the memory and CPU.

Measurement Interval

The PM measures the STAT_RESOURCE every 10 seconds. These samples measured every 10 seconds are used to calculate the following

statistics.

[Index]

Name Range Description

Shelf ID 0 Shelf ID. The eNB is configured in one shelf, thus the default value is 0.

Slot ID 0~3 The ID of the slot that the board is mounted. Maximum 4 slots per shelf.

Board Type 0~1 The type of the board mounted in the corresponding slot.

0: UAMA Board

1: L9CA Board



[Statistics Type]

No Item Unit Definition Collection

Method Count Collected When Type

Lower/Upper

Limit

1 MEMUsage_AVG % Average memory usage during

the measurement time.

GAUGE avg (MEMUsage) float 0.00~100.00

2 MEMUsage_MIN % Minimum memory usage during


GAUGE Minimum value of the memory usage

collected during the measurement time.

Formula: min (MEMUsage)

float 0.00~100.00

3 MEMUsage_MAX % Maximum memory usage during


GAUGE Maximum value of the memory usage

collected during the measurement time.

Formula: max (MEMUsage)

float 0.00~100.00

4 CPUUsage_AVG % Average usage of the CPU in

three seconds.

GAUGE avg (CPUUsage) float 0.00~100.00

5 CPUUsage_MIN % Minimum usage of the CPU in

three seconds.

GAUGE Minimum value of the CPU usage collected

during the measurement time.

Formula: min (CPUUsage)

float 0.00~100.00

6 CPUUsage_MAX % Maximum usage of the CPU in

three seconds.

GAUGE Maximum value of the CPU usage collected


Formula: max (CPUUsage)

float 0.00~100.00

7 DISKUsage_AVG % Average disk usage during the

measurement time.

GAUGE avg (DISKUsage) float 0.00~100.00

8 DISKUsage_MIN % Minimum disk usage during the

measurement time.

GAUGE Minimum value of the disk usage collected


Formula: min (DISKUsage)

float 0.00~100.00

9 DISKUsage_MAX % Maximum disk usage during the

measurement time.

GAUGE Maximum value of the disk usage collected


Formula: max (DISKUsage)

float 0.00~100.00



10.3.2 Packet Statistics

The Packet statistics is the statistics of the sent/received packets processed in the eNB.

The statistics provided are as follows. For the details on each item, refer to the explanation of the statistics of each item.

Ethernet Packet: PACKET, NET_HISTOGRAM, QOS_INFO

Wireless Packet (MAC): AIR_MAC_BYTES

Air RLC sent/received byte count: AIR_RLC_BYTES

Sent/Received packet count (PDCP): CP_PACKET

Ethernet Interface

It collects Ethernet packet statistics.


The PM measures STAT_PACKET every 10 seconds. These samples measured every 10 seconds are used to calculate the following statistics.

[Index]


PortNum 0~5 Port number

BH 0: 0

BH 1: 1

BH 2: 2

BH 3: 3

UDE 0: 4

UDE 1: 5



[Statistics Type]



Lower/Upper

Limit

1 RX_LinkUtilization % Average link utilization of the

packets received externally.

OW (tot (RX_GoodOctetSumBadOctet) * 8 * 10)/(cnt

(RX_GoodOctetSumBadOctet))/(IfSpeed)

int 0~100

2 RX_LinkUtilization_

MAX

% Maximum link utilization of the


OW (max (RX_GoodOctetSumBadOctet) * 8 * 10)/

(IfSpeed)

int 0~100

3 RX_ErrorRate % Rate of the error packets

received externally.

OW (RX_FifoOverrun + RX_Undersize +

RX_Fragment + RX_Oversize + RX_Jabber +

RX_ErrorFrame + RX_BadCRC + RX_Collision +

RX_LateCollision) * 100/(RX_UnicastPacket +

RX_BroadcastPacket + RX_MulticastPacket +

RX_FifoOverrun + RX_Undersize +

RX_Fragment + RX_Oversize + RX_Jabber +

RX_ErrorFrame + RX_BadCRC + RX_Collision +

RX_LateCollision)

int 0~100

4 RX_GoodOctet Mbyte

count

Total frame length of the

normal packets received

externally.

CC There are normal packets received in each port. int 0~2147483647

5 RX_UnicastPacket count Number of unicast packets


CC There are unicast type packets in the packets

received in each port.

int 0~2147483647

6 RX_BroadcastPacket count Number of broadcast packets


CC There are broadcast type packets in the packets


int 0~2147483647

7 RX_MulticastPacket count Number of multicast packets


CC There are Multicast type packets in the packets


int 0~2147483647



(Continued)



Lower/Upper

Limit

8 RX_FifoOverrun count Number of dropped packets

due to insufficient buffer

resource from the packets


CC There are drops due to Rx Fifo overrun in the

packets received in each port.

int 0~2147483647

9 RX_Undersize count Number of undersized

packets from the error


CC There are drops due to undersize in the packets


int 0~2147483647

10 RX_Fragment count Number of fragmented

packets from the error


CC There are drops due to fragment in the packets


int 0~2147483647

11 RX_Oversize count Number of oversized packets

from the error packets


CC There are drops due to oversize in the packets


int 0~2147483647

12 RX_Jabber count Number of jabbered packets



CC There are drops due to jabber error in the packets


int 0~2147483647

13 RX_ErrorFrame count Number of errors received

externally.

CC There are errors in the packets received in each

port.

int 0~2147483647

14 RX_BadCRC count Number of CRC error packets



CC There are CRC errors in the packets received in

each port.

int 0~2147483647

15 RX_Collision count Number of collisions from the


CC There are collisions in the packets received in

each port.

int 0~2147483647



(Continued)



Lower/Upper

Limit

16 RX_LateCollision count Number of late collisions from

the packets received

externally.

CC There are late collisions in the packets received in

each port.

int 0~2147483647

17 TX_LinkUtilization % Average link utilization of the

packets sent externally.

OW (tot (TX_GoodOctetSumBadOctet) * 8 * 10)/cnt

(TX_GoodOctetSumBadOctet)/(IfSpeed)

int 0~100

18 TX_LinkUtilization_

MAX

% Maximum link utilization of the


OW (max (TX_GoodOctetSumBadOctet) * 8 * 10)/

(IfSpeed)

int 0~100

19 TX_ErrorRate % Rate of the error packets sent

externally.

OW (TX_Underrun_BadCRC + TX_Deferred + TX_E_

Collisions) * 100/(TX_UnicastPacket +

TX_BroadcastPacket + TX_MulticastPacket +

TX_Underrun_BadCRC + TX_Deferred + TX_E_

Collisions)

int 0~100

20 TX_GoodOctet Mbyte

count

Total frame length of the

normal packets sent

externally.

CC There are normal packets sent from each port. int 0~2147483647

21 TX_UnicastPacket count Number of unicast packets

sent externally.

CC There are unicast type packets in the packets

sent from each port.

int 0~2147483647

22 TX_BroadcastPacke

t

count Number of broadcast packets

sent externally.

CC There are broadcast type packets in the packets


int 0~2147483647

23 TX_MulticastPacket count Number of multicast packets

sent externally.

CC There are multicast type packets in the packets


int 0~2147483647

24 TX_Underrun_

BadCRC

count Number of underrun or CRC

error packets from the


CC Tx Fifo underrun or CRC error occurs in the

packets sent from each port.

int 0~2147483647



(Continued)



Lower/Upper

Limit

25 TX_Deferred count Number of delayed

transmissions due to the busy

media when the port is

connected in half-duplex

mode.

CC Tx Defer occurs in the packets sent from each

port.

int 0~2147483647

26 TX_E_Collisions count Number of packets whose

transmission was cancelled

due to the excessive collision

when the port is connected in

half-duplex mode.

CC There are excessive collisions in the packets sent

from each port.

int 0~2147483647

Histogram

It groups and collects the Ethernet packets received from the backhaul or UDE port by size, for each port.


The PM measures the STAT_NET_HISTOGRAM every 10 seconds. These samples measured every 10 seconds are used to calculate the

following statistics.



[Index]



BH 0: 0

BH 1: 1

BH 2: 2

BH 3: 3

UDE 0: 4

UDE 1: 5

[Type of Statistics]



Lower/Upper

Limit

1 RX_Histogram_64 count Number of 64 byte packets

received

CC There are 64 byte packets in the packets


int 0~2147483647

2 RX_Histogram_127 count Number of 65-127 byte packets

received

CC There are ones of 65-127 bytes in the packets

received on each port.

int 0~2147483647

3 RX_Histogram_255 count Number of 128-255 byte

packets received

CC There are ones of 128-255 bytes in the

packets received on each port.

int 0~2147483647


packets received

CC There are ones of 256-511 bytes in the packets

received on each port.

int 0~2147483647


packets received

CC There are ones of 512-1023 bytes in the

packets received on each port.

int 0~2147483647

6 RX_Histogram_max count Number of over 1024 byte

packets received

CC There are ones of 1024 byte or larger packets in

the packets received on each port.

int 0~2147483647



QoS Information

When using the QoS function for each backhaul port, the system provides 8 queues for each port. The ports can be configured so that the

transmitted data are sorted by traffic type and mapped to each queue.

If there exists no default QoS setting for the backhaul port, only the default queue is used. The queue setting can be modified as illustrated in the

example below depending on the operating condition.

[Setting Example]

DSCP Value Queue # Traffic Type

24 (CS3) 0 Call Signaling (S1/X2)

24 (CS3) Management (SNMP Message)

48 (CS6) IP Control (DHCP)

26 (AF31) 1 OAM Traffic (FTP, Log)

.... .... ....

- 7 Default

The QOS_INFO provides the statistics on the number and bytes of the packets dropped in a given queue due to the congestion in the backhaul port.


The PM measures the QOS_INFO every 10 seconds. These samples measured every 10 seconds are used to calculate the following statistics.



[Index]



BH 0: 0

BH 1: 1

BH 2: 2

BH 3: 3

UDE 0: 4

UDE 1: 5

[Statistics Type]



Lower/Upper

Limit

1 Q0_TailDropOctet Kbytes Drop byte count on Queue 0 CC Count is collected on Queue 0 of each port. int 0~2147483647

2 Q0_TailDropPacket count Drop packet count on Queue 0 CC Count is collected on Queue 0 of each port. int 0~2147483647












(Continued)



Lower/Upper

Limit






Air Mac UL/DL bytes

It collects the statistics data for the cell throughput. Of the downlink/uplink transport blocks the eNB MAC allocated to the UE, the average of the

TB sizes of the packets successfully sent and received is collected.


The PM measures the AIR_MAC_BYTE every five seconds. These five-second samples are used to calculate the following statistics.

[Index]


cNum 0~5 Serving Cell Index



[Statistics Type]



Lower/Upper

Limit

1 AirMacByteUl Kbytes Sum of the size of the MAC PDU successfully

received via PUSCH during the statistics period

CC Air Mac UL/DL bytes statistics

are collected

int 0~2147483647

2 AirMacTtiUl TTI Sum of the section containing the MAC PDU

successfully received via PUSCH during the

statistics period


are collected

int 0~2147483647

3 AirMacUlThru bps Average size per second of the MAC PDU

successfully received via PUSCH

OW ((AirMacByteUl * 1000 * 8)/

(5120 * AirMacByteUlCnt)) *

1000

float 0~3.4 * 10^38

4 AirMacUlEfctivThru bps Average size of the MAC PDU of the section

successfully received via PUSCH during the

statistics period

OW ((AirMacByteUl * 1000 * 8)/

AirMacTtiUl) * 1000

float 0~3.4*10^38

5 AirMacByteDl Kbytes Sum of the size of the DCCT/DTCH MAC PDU

that received HARQ ACK among the MAC PDU

sent via PDSCH during the statistics period


are collected

int 0~2147483647

6 AirMacTtiDl TTI Sum of the section containing the MAC PDU

successfully transmitted via PDSCH during the

statistics period


are collected

int 0~2147483647

7 AirMacDlThru bps Average size per second of the DCCT/DTCH

MAC PDU that received HARQ ACK among the

MAC PDU sent via PDSCH during the statistics

period

OW (AirMacByteDl * 1000 * 8)/

(5120 * AirMacByteDlCnt)) *

1000

float 0~3.4 * 10^38

8 AirMacDlEfctivThru bps Average size of the MAC PDU of the section

successfully transmitted via PDSCH during the

statistics period

OW ((AirMacByteDl * 1000 * 8)/

AirMacTtiDl) * 1000

float 0~3.4 * 10^38



[Collection Time]

TTI (Transmission Time Interval: 1 ms)

Air RLC UL/DL bytes

Collects the downlink‟s transmitted byte and retransmitted byte count/throughput/IP throughput and the uplink‟s transmitted byte count/throughput

for the wireless section of the eNB.

Since the data are collected and summed for each cell and each QCI, they are collected after the cell setup has finished.


The PM measures the AIR_RLC_BYTE every five seconds. These samples measured every 5 seconds are used to calculate the following

statistics.

[Index]



QCI 0~15 QoS Class Identifier



[Statistics Type]



Lower/Upper

Limit

1 AirRlcByteUl byte

count

Air RLC uplink bytes

Number of bytes transmitted from the RLC as air

uplink. Collects the number of data bytes received

by the UE for each cell and QCI.

CC The RLC uplink is transmitted

to the PDCP.

int 0~2147483647

2 AirRlcByteDl byte

count

Air RLC downlink bytes

Number of bytes transmitted from the RLC as air

downlink. Collects the number of data bytes sent

to the UE for each cell and QCI.

CC The RLC downlink transmits

the RLC PDU to the MAC.

int 0~2147483647

3 AirRlcByteDlRe byte

count

Air RLC downlink ReTx bytes

Number of bytes retransmitted from the RLC as

air downlink. Collects the number of data bytes

sent to the UE for each cell and QCI.

CC The RLC downlink retransmits

the RLC PDU to the MAC.

int 0~2147483647

4 AirUlThru bps Air uplink throughput

Collects the data received from the UE as the air

uplink throughput for each cell and QCI.

SI avg (AirUlThru) float 0~3.4 * 10^38

5 AirDlThru bps Air downlink throughput

Collects the data sent to the UE as the air

downlink throughput for each cell and QCI.

SI avg (AirDlThru) float 0~3.4 * 10^38

6 IpThru bps IP throughput

Collects the IP throughput for each cell and QCI

using the method specified in 3GPP TS 32.450.

SI avg (IpThru) float 0~3.4 * 10^38



S-GW UL/DL packets

For each QCI, collects the statistics of the bytes, packet counts and throughputs of the user data transmitted between eNB and S-GW in accordance

to the 3GPP TS32.425 Performance Measurements specification. Each item is collected by the PDCP layer within the eNB.


The PM measures the CP_PACKET every two seconds. These samples measured every 2 seconds are used to calculate the following

statistics.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 ByteUleNBQCI byte

count

Total bytes of user data sent from

the eNB to the S-GW

CC This is the cumulated sum of the bytes sent

from the eNB, collected in PDCP SDU level

at the time of its transmission.

int 0~2147483647

2 ThruUleNBQCI kbps (Total bits of user data sent to S-

GW)/(Total time spent to send the

user data)

GAUGE This is calculated as the total bits sent from

the eNB for a given amount of time

(Measurement Period), in kbps unit.

The corresponding bits are collected in

PDCP SDU level.

Formula: avg (ThruUleNBQCI)

float 0~3.4 * 10^38



(Continued)



Lower/Upper

Limit

3 ThruUleNBQCIMax kbps The maximum value in 5 minutes

of (Total bits of user data sent to

S-GW)/(Total time spent to send

the user data)

GAUGE The maximum ThruUleNBQCI value

received.

float 0~3.4 * 10^38

4 PacketCntUl count Total number of packets sent from

the eNB to the S-GW

CC This is the cumulated statistics of the

number of packets sent from the eNB,

collected at the time of its transmission.

int 0~2147483647

5 ByteDleNBQCI byte

count

Total bytes of user data the eNB

received from the S-GW

CC This is the cumulated sum of the bytes

received by the eNB, collected in PDCP

SDU level at the time of its reception.

int 0~2147483647

6 ThruDleNBQCI kbps (Total bits of user data received

from S-GW)/(Total time spent to

receive the user data)

GAUGE This is calculated as the total bits received

by the eNB for a given amount of time


The corresponding bits are collected in

PDCP SDU level.

Formula: avg (ThruDleNBQCI)

float 0~3.4 * 10^38

7 ThruDleNBQCIMax kbps The maximum value in 5 minutes

of (Total bits of user data received

from S-GW)/(Total time spent to

receive the user data)

GAUGE The maximum ThruDleNBQCI value

received.

float 0~3.4 * 10^38

8 PacketCntDl count Total number of packets the eNB

received from the S-GW

CC This is the cumulated statistics of the

number of packets received by the eNB,

collected at the time of its reception.

int 0~2147483647



10.3.3 RRC

The RRC statistics consist of RRC connection establishment statistics, RRC connection reconfiguration statistics, RRC connection reestablishment

statistics, RRC termination call count statistics, RRC connection count statistics, RRC connection setup time statistics, RRC connection

reestablishment statistics and call drop statistics. For the details on each item, refer to the explanation of the statistics of each item below.

RRC Connection establishments

It collects the statistics data for RRC connection setup for each cell. The station receives the RRC connection request message from the terminal,

sends the RRC connection setup message to the terminal, then receives the RRC connection setup complete message from the terminal.

When this process is completed successfully, the RRC connection establishment attempt statistics and success statistics will be counted.

[Index]



EstabCause 0~4 RRC Connection Establishment Cause

0: emergency

1: highPriorityAccess

2: mt_Access

3: mo_Signalling

4: mo_Data



[Statistics Type]



Lower/Upper

Limit

1 ConnEstabAtt count The attempt count for RRC

ESTAB

CC The RRC connection request

message ( in the following

figure) is received.

int 0~2147483647

2 ConnEstabSucc count The success count for

RRC ESTAB

CC The RRC connection setup

complete message ( in the

following figure) is received.

int 0~2147483647

3~133 ConnEstabFail_S1AP_

CauseRadioNetwork_unspecified~

ConnEstabFail_MAC_Others

count RRC ESTAB failure count:

See „Statistics Fail Cause

List‟.

CC If a timeout or an internal error

occurs in step ~ in the

following figure, Fail is counted.

int 0~2147483647

134~

264

ConnEstabReject_S1AP_


ConnEstabReject_MAC_Others

count RRC ESTAB Reject count:


List‟.

CC It is determined that the station is

not possible to receive the

corresponding call after receiving

the RRC Connection Request

message in the following figure.

int 0~2147483647

../../../+이동통신%20매뉴얼/LTE/+미국(멕시코)/+Sprint향%20eNB/Users/Administrator/Desktop/서식/영문/l

../../../+이동통신%20매뉴얼/LTE/+미국(멕시코)/+Sprint향%20eNB/Users/Administrator/Desktop/서식/영문/l

../Local%20Settings/Users/Administrator/Desktop/서식/영문/l




[Collection Time]

Figure 10.2 RRC Connection Establishment (Success) collection time

The statistics will include the Attempt, Success, Fail and Reject statistics. The Attempt statistics will be counted upon the reception of the RRC

Connection Request message. The Success statistics will be counted upon successful reception of the RRC Connection Setup Complete message.

If a timeout or an internal error occurs in step - in the above figure, Fail is counted and the corresponding cause value is recorded.

For the Reject statistics, after receiving the RRC Connection Request message, it is determined if the station is in the condition to receive the

corresponding call. If it is not possible to receive the call, Reject is counted and the corresponding cause value is recorded.

eNB UE MME S/GW

RRC_IDLE

RRC_CONNECTED






Initial UE Message

1

2

Attempt

Success



Figure 10.3 RRC Connection Establishment (Reject) collection time

eNB UE

MME S/GW

RRC_IDLE

RRC_IDLE




Rrc Connection Reject

1

3

Attempt

RRC connection Reject Count



RRC Connection reconfiguration

The eNB collects the statistics data for the RRC connection reconfiguration for each cell. The failure statistics doesn‟t exist because during the

handover the RRC Connection Reconfiguration message goes down from the SeNB, but the RRC Connection Reconfiguration Complete message

is transmitted to the TeNB. In such situation, the Attempt and Success counts of the Reconfiguration statistics in the corresponding eNB may be

different from each other.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 ConnReconfigAtt count The attempt count for RRC

connection reconfiguration

CC The RRC Connection Reconfiguration

message ( in the figure below) is

transmitted.

int 0~2147483647

2 ConnReconfigSucc count The success count for RRC

connection reconfiguration

CC The RRC Connection Reconfiguration

Complete message ( in the figure below) is

received.

int 0~2147483647



[Collection Time]

Figure 10.4 RRC Connection Reconfiguration collection time

The statistics will count as Attempt if a Reconfiguration message is sent from the station to the terminal, and count as Success if a RRC Connection

Reconfiguration Complete message is received from the terminal. The failure statistics doesn‟t exist because during the handover the RRC

Connection Reconfiguration message goes down from the SeNB, but the RRC Connection Reconfiguration Complete message is transmitted to the

TeNB. In such situation, the Attempt and Success counts of the Reconfiguration statistics in the corresponding eNB may be different from each

other.

eNB UE MME S/GW

RRC_IDLE

RRC_CONNECTED



1

2

Attempt

Success



RRC Connection re-establishments

The eNB collects the statistics data for RRC connection reestablishment for each cell.

[Index]



ReEstabCause 0~3 RRC Connection Re-establishment Cause

0: reconfigurationFailure

1: handoverFailure

2: otherFailure

3: reserved

[Statistics Type]



Lower/Upper

Limit

1 ConnReEstabAtt count The attempt count for

RRC_REESTAB

CC RRC Connection Reestablishment

Request message ( in the figure

below) is received.

int 0~2147483647

2 ConnReEstabSucc count The success count for

RRC_REESTAB

CC RRC Connection Reestablishment

Complete message ( in the figure

below) is received.

int 0~2147483647

3~133 ConnReEstabFail_S1AP_

CauseRadioNetwork_

unspecified~ConnReEstabFail_

MAC_Others

count RRC_REESTAB failure

count: see „Statistics

Fail Cause List‟.

CC A timeout or an internal error occurs

in step ~ in the figure below.

int 0~2147483647




(Continued)



Lower/Upper

Limit

134~

264

ConnReEstabReject_S1AP_

CauseRadioNetwork_

unspecified~ConnReEstabReject_

MAC_Others

count RRC REESTAB Reject

count: see „Statistics

Fail Cause List‟.

CC It is determined that the station is not

possible to receive the

corresponding call after receiving the

RRC Connection Reestablishment

Request message in the following

figure.

int 0~2147483647

[Collection Time]

Figure 10.5 RRC Connection Re-establishment (Success) collection time

eNB UE MME S/GW

RRC_IDLE

RRC_CONNECTED



Rrc Connection Reestablishment Complete

1

2

Attempt

Success




The statistics will include the Attempt, Success, Fail and Reject statistics. The Attempt statistics will be counted upon the reception of the RRC

Connection Reestablishment Request message. The Success statistics will be counted upon successful reception of the RRC Connection

Reestablishment Complete message. A timeout or an internal error occurs in the steps in the following figure. For the Reject statistics, after

receiving the RRC Connection Reestablishment Request message, the eNB determines if the station is in the condition to receive the corresponding

call. If it is not possible to receive the call, it is counted as Reject and the corresponding cause value is recorded.

Figure 10.6 RRC Connection Re-establishment (Reject) collection time

eNB UE MME S/GW

RRC_IDLE

RRC_CONNECTED


Rrc Connection Reestablishment Reject

1

3

Attempt

Reject



RRC Connection release

The eNB collects the statistics data for RRC connection release for each cell.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 ConnRelease_NO_FAULT count The call ends successfully. CC The RRC is released. int 0~2147483647

2~132 ConnRelease_S1AP_


ConnRelease_MAC_Others

count RRC Connection Release

count: see „Statistics Fail Cause

List‟.

CC The RRC ( in the following

figure) is released.

int 0~2147483647





[Collection Time]

Figure 10.7 RRC Connection Release collection time

If the release of a call previously in RRC Connected status occurs, the number of RRC Connection Release message transmission to the terminal is

counted.

Call released by the MME

Call released by the eNB

eNB UE MME S/GW

RRC_IDLE

RRC_CONNECTED

Rrc Connection Release 1 Count



RRC Connection number

The eNB collects the statistics data for the average RRC connection count per unit time and the maximum RRC connection count for each cell.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 ConnNo count Average RRC connection per unit time GAUGE avg (ConnNo) float 0~3.4 * 10^38

2 ConnMax count Maximum RRC connection per unit time GAUGE max (ConnNo) float 0~3.4 * 10^38

3 ConnTot count Total RRC connection per unit time GAUGE tot (ConnNo) float 0~3.4 * 10^38

4 ReleaseCallHoldingTime sec Average release call holding time the

RRC connection was maintained, which

is calculated based on call release

SI sum

(ReleaseCallHoldingTimeTot)/

sum (ReleaseCallCnt)

float 0~3.4 * 10^38

5 ReleaseCallHoldingTimeTot sec Total RRC connection release call

holding time

SI tot (ReleaseCallHoldingTime) float 0~3.4 * 10^38

6 ReleaseCallCnt count Call Release Count SI cnt (HoldingTime) float 0~3.4 * 10^38



RRC Connection setup time

The eNB collects the statistics data for the average RRC connection setup time and the maximum RRC connection setup time for each cell.

[Index]




0: emergency


2: mt_Access

3: mo_Signalling

4: mo_Data

[Statistics Type]



Lower/Upper

Limit

1 ConnEstabTime msec Average RRC connection setup time GAUGE Avg (ConnEstabTime) float 0~3.4 * 10^38

2 ConnEstabTimeMax msec Maximum RRC connection setup time GAUGE max (ConnEstabTime) float 0~3.4 * 10^38

3 ConnEstabTimeTot msec Total RRC Connection setup time GAUGE Tot (ConnEstabTime) float 0~3.4 * 10^38



[Collection Time]

Figure 10.8 RRC Connection Setup Time collection time

The RRC connection setup time represents the time elapsed from the reception of the RRC Connection Request message until the reception of the

RRC Connection Setup Complete message. The station calculates the corresponding time in msec, collects the average and maximum values every

5 minutes, sends the results to the LSM, and displays on the LSM statistics window.

eNB UE MME S/GW

RRC_IDLE

RRC_CONNECTED




Initial UE Message

RRC Connection Setup time



RRC Connection reestablishment time

The eNB collects the statistics data for the average RRC Connection Setup time and the maximum RRC Connection Reestablishment Setup time

for each cell.

[Index]



ReEstabCause 0~3 RRC Connection Re-establishment Cause

0: reconfigurationFailure

1: handoverFailure

2: otherFailure

3: reserved

[Statistics Type]



Lower/Upper

Limit

1 ConnReEstabTime msec Average RRC connection

reestablishment setup time

GAUGE avg (ConnReEstabTime) float 0~3.4 * 10^38

2 ConnReEstabTimeMax msec Maximum RRC connection

reestablishment setup time

GAUGE max (ConnReEstabTime) float 0~3.4 * 10^38

3 ConnReEstabTimeTot msec Total RRC connection reestablishment

setup time

GAUGE tot (ConnReEstabTime) float 0~3.4 * 10^38



[Collection Time]

Figure 10.9 RRC connection Reestablishment Time collection time

The RRC connection reestablishment time represents the time elapsed from the reception of the RRC Connection Request message until the

reception of the RRC Connection Setup Complete message. The station calculates the corresponding time in msec, collects the average and

maximum values every 5 minutes, sends the results to the LSM, and displays on the LSM statistics window.

eNB UE MME S/GW

RRC_IDLE

RRC_CONNECTED



Rrc Connection Reestablishment Complete

RRC Connection

Reestablishment time



Call Drop

The eNB collects the call drop statistics. The call drop statistics is calculated by counting the disconnection of the calls, among those with the UE

Context, which are not caused by NO_FAULT. Not caused by NO_FAULT means that the call fail occurred due to NO_FAULT (0x0FFF),

C_S1AP_user_inactivity (0x114) or C_ECCB_USER_INACTIVITY (0x341) among the callFaultCause. For the callFaultCause other than the

3 causes above, the base station issues the call drop statistics.

[Index]




0: emergency


2: mt_Access

3: mo_Signalling

4: mo_Dat



[Statistics Type]



Lower/Upper

Limit

1 CallDrop_ECC_TMOUT_


count CALL_DROP count: See „Fail Cause

List‟.

CC The call is dropped. int 2147483648/0

2 CallDrop_ECC_TMOUT_

rrcConnectionReEstablish

count CALL_DROP count: See „Statistics

Fail Cause List‟.


3 CallDrop_ECC_ARQ_MAX_RE_

TRANSMISSION


Fail Cause List‟.


4 CallDrop_ECC_RADIO_LINK_

FAILURE


Fail Cause List‟.


5 CallDrop_ECC_RCV_CELL_

RELEASE_IND_FROM_ECMB


Fail Cause List‟.


6 CallDrop_ECC_DSP_AUDIT_

RLC_CALL_RELEASE


Fail Cause List‟.



MAC_CALL_RELEASE


Fail Cause List‟.



RLC_MAC_CALL_RELEASE


Fail Cause List‟.


9 CallDrop_ECC_RCV_RESET_

REQUEST_FROM_ECMB


Fail Cause List‟.


10 CallDrop_ECC_S1_SCTP_OUT_

OF_SERVICE


Fail Cause List‟.






















10.3.4 ERAB

The ERAB statistics consist of E-RAB setup count, additional E-RAB setup count, E-RAB setup time, E-RAB deletion request, E-RAB deletion,

E-RAB modification, E-RAB release request, E-RAB release, E-RAB activity (UE), E-RAB activity (QCI), E-RAB count statistics, etc.

For the details on each item, refer to the explanation of the statistics of each item below.

E-RAB Setup

The eNB collects the statistics data for initial E-RAB (default bearer) Setup for each cell.

[Index]




0: emergency


2: mt_Access

3: mo_Signalling

4: mo_Data




[Statistics Type]



Lower/Upper

Limit

1 EstabInitAttNbr count The number of attempts

for ERAB setup

CC The Initial Context Setup

Request message is received in

the initial call setup ( in the

following figure).

int 0~2147483647

2 EstabInitSuccNbr count The number of successes

for ERAB setup

CC The Initial Context Setup

Response message ( in the

following figure) is sent.

int 0~2147483647

3~133 EstabInitFailNbr_S1AP_


EstabInitFailNbr_MAC_Others

count The number of failures for

ERAB setup:


List‟.

CC A timeout or an internal error


following picture.

int 0~2147483647





[Collection Time]

Figure 10.10 E-RAB Setup collection time

If an Initial Context Setup Request message is received during the initial setup, it is counted as Attempt. The Initial Context Setup Response

message is sent, and it is counted as Success. If a timeout or an internal error occurs in the steps, it is counted as Fail and the corresponding cause

value is recorded.

eNB UE MME S/GW

RRC_CONNECTED

RRC_CONNECTED


Security Mode Complete




1 Attempt

2 Success

Authentication Procedure (NAS)

Initial Context Setup Request



E-RAB Setup Add

The eNB collects the statistics data for additional E-RAB (dedicated bearer) Setup for each cell.

[Index]




[Statistics Type]



Lower/Upper

Limit

1 EstabAddAttNbr count The number of attempts for

additional ERAB setup

CC The E-RAB Setup Request

message is received in the

E-RAB setup ( in the following

figure).

int 0~2147483647

2 EstabAddSuccNbr count The number of successes

for additional ERAB setup

CC The E-RAB Setup Response


figure) is sent.

int 0~2147483647

3~133 EstabAddFailNbr_S1AP_


EstabAddFailNbr_MAC_Others

count Additional ERAB Setup

failure count: See „Statistics

Fail Cause List‟.

CC A timeout or an internal error


following picture.

int 0~2147483647




[Collection Time]

Figure 10.11 Additional E-RAB Setup collection time

If an E-RAB Setup Request message is received during the E-RAB setup, it is counted as Attempt. The E-RAB Setup Response message is sent

and it is counted as Success. If a timeout or an internal error occurs in the steps, it is counted as Fail and the corresponding cause value is recorded.

eNB UE MME S/GW

RRC_CONNECTED

RRC_CONNECTED



E-RAB Setup Response

E-RAB Setup Request 1 Attempt

2 Success



E-RAB Setup time

The eNB collects the statistics data for the average E-RAB Setup time and the maximum E-RAB Setup time for each cell.

It is collected during the initial E-RAB Setup process and during the additional E-RAB Setup process.

[Index]




[Statistics Type]



Lower/Upper

Limit

1 EstabTime msec Average E-RAB setup time GAUGE sum (EstabTimeTot)/sum (EstabTimeCnt) int 0~2147483647

2 EstabTimeMax msec Maximum E-RAB setup time GAUGE max (EstabTime) int 0~2147483647

3 EstabTimeTot msec Total E-RAB setup time GAUGE Total EstabTime value is received. int 0~2147483647

4 EstabTimeCnt count E-RAB setup time collection

count

GAUGE The EstabTime count is received. int 0~2147483647



[Collection Time]

Figure 10.12 E-RAB Setup Time (initial E-RAB Setup) collection time

eNB UE MME S/GW

RRC_IDLE

RRC_CONNECTED

Security Mode Complete




E-RAB Setup time





Figure 10.13 E-RAB Setup Time (additional E-RAB Setup) collection time

The time elapsed from the reception of Initial Context Setup Request message to the transmission of Initial Context Setup Response message is

notified in msec.

Or, the time elapsed from the reception of ERAB Setup Request message to the transmission of ERAB Setup Response message is notified in msec.

The average and maximum value of the corresponding statistics is calculated in the statistics block every five minutes; the LSM displays the

corresponding result.

eNB UE MME S/GW

RRC_CONNECTED

RRC_CONNECTED



E-RAB Setup Response

E-RAB Setup time

E-RAB Setup Request



E-RAB Erase request

The eNB collects the statistics data for the E-RAB release requests made by the base station by sending the UE Context Release Request message

for each cell.

[Index]




[Statistics Type]



Lower/Upper

Limit

1 EraseAttbyEnb count The number of the E-RAB release requests

made by the base station using the UE

Context Release Request message

CC The Context Release Request


figure) is sent.

int 0~2147483647



[Collection Time]

Figure 10.14 E-RAB Erase Request collection time

The eNB E-RAB erase request is used to erase the UE context. If the station requires to release the UE context, it sends the UE Context Release

Request message to the MME and counts the corresponding statistics.

The events the station sends the UE Context Release Request message to the MME are as follows:

A RRC Connection Reconfiguration message is sent to the terminal, but no response is received.

A user inactivity occurs to the user with no DL/UL traffic from the MAC scheduler.

An ARQ retransmission error occurs to the RLC.

A Radio Link Failure occurs to the station.

eNB UE MME S/GW

RRC_CONNECTED

RRC_CONNECTED

1 Count UE Context Release Request


UE Context Release Complete




E-RAB Erase

The eNB collects the statistics data for the E-RAB release processed through the E-RAB Context Release Command message for each cell.

[Index]




[Statistics Type]



Lower/Upper

Limit

1 EraseAtt count The number of the E-RAB release

attempts using the UE Context

Release Command message.

CC The UE Context Release

Command message ( in the

following figure) is received.

int 0~2147483647

2 EraseSucc count The number of the E-RAB release

successes using the UE Context

Release command.

CC The UE Context Release

Complete message ( in the

following figure) is sent.

int 0~2147483647



[Collection Time]

Figure 10.15 E-RAB Erase collection time

In the E-RAB Erase statistics, it is counted as Attempt upon the reception of the UE Context Release Command message, and is counted as Success

after the UE Context Release Complete message is sent.

eNB UE MME S/GW

RRC_CONNECTED

RRC_CONNECTED

1 Attempt UE Context Release Command


Rrc Connection Release

2 Success



E-RAB Modify

The eNB collects the statistics data for E-RAB Modify for each cell.

[Index]




[Statistics Type]



Lower/Upper

Limit

1 ModQoSAttNbr count The number of attempts for

ERAB modification

CC The E-RAB Modify Request



int 0~2147483647

2 ModQoSSuccNbr count The number of successes

for ERAB modification

CC The Modify Response message

( in the following figure) is sent.

int 0~2147483647

3~133 ModQoSFailNbr_S1AP_


ModQoSFailNbr_MAC_Others

count The number of failures for

ERAB modification:


List‟.

CC The E-RAB Modify process in step

~ fails due to a timeout or an

internal error in the following

figure.

int 0~2147483647





[Collection Time]

Figure 10.16 E-RAB Modify collection time

In the corresponding statistics, it is counted as Attempt upon the reception of the E-RAB Modify Request message from the MME, and is counted

as Success after the E-RAB Modify Response message is sent. If the E-RAB Modify process fails due to a timeout or an internal error, it is counted

as Fail and the corresponding cause value is recorded.

eNB UE MME S/GW

RRC_CONNECTED

RRC_CONNECTED

1 Attempt E-RAB Modify Request

E-RAB Modify Response


2 Success




E-RAB Release request

The eNB collects the statistics data for the E-RAB release requests made by the base station using the E-RAB Release Indication message for each

cell.

[Index]




[Statistics Type]



Lower/Upper

Limit

1 RelAttbyEnbNbr count The number of the E-RAB release requests

made by the base station using the E-RAB

Release Indication message.

CC The E-RAB Release Indication


figure) is sent.

int 0~2147483647



[Collection Time]

Figure 10.17 E-RAB Release Request collection time

If the station requires to delete a bearer, it sends the E-RAB Release Indication message to the MME after deleting the corresponding bearer and

counts the corresponding statistics. This can occur if an ERAB is released preemptively or due to the reception of the GTP Error Indication

message.

eNB UE MME S/GW

RRC_CONNECTED

RRC_CONNECTED

1 Count E-RAB Release Indication

ERAB Release(eNB)



E-RAB Release

The eNB collects the statistics data for the E-RAB release processed through the E-RAB Release Command message for each cell.

[Index]




[Statistics Type]



Lower/Upper

Limit

1 RelAttNbr count The number of the ERAB release

attempts using the ERAB Release

command

CC The E-RAB Release Request



int 0~2147483647

2 RelSuccNbr count The number of the ERAB release

successes using the ERAB

Release command

CC The E-RAB Release Response


figure) is sent.

int 0~2147483647

3~133 RelFailNbr_S1AP_

CauseRadioNetwork_

unspecified~RelFailNbr_

MAC_Others

count Failure count for the ERAB that

must be released by the ERAB

Release Command message:

See „Statistics Fail Cause List‟.

CC The E-RAB Modify process in

step ~ in the following figure

fails due to a timeout or an

internal error.

int 0~2147483647




[Collection Time]

Figure 10.18 E-RAB Release collection time

In the corresponding statistics, it is counted as Attempt upon the reception of the E-RAB Release Request message from the MME, and is counted

as Success after the E-RAB Release Response message is sent. If the E-RAB Release process fails due to a timeout or an internal error, it is

counted as Fail and the corresponding cause value is recorded.

eNB UE MME S/GW

RRC_CONNECTED

RRC_CONNECTED

1 Attempt E-RAB Release Command

E-RAB Release Response


2 Success




E-RAB Activity (UE)

The eNB collects the statistics data for the in-session time of the UE. In-session is defined as valid if a data transmission took place during the last

100 msec; it collects the in-session time of the UE which had data transmissions with the PDSCH/PUSCH during the statistics period.


The PM measures the ERAB_SEESION_UE every five seconds. These five-second samples are used when calculating the next statistics.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 SessionTimeUE msec Average in-session time per UE SI avg (SessionTimeUE) float 0~3.4 * 10^38

2 SessionTimeUETot msec Total in-session time per UE SI tot (SessionTimeUE) float 0~3.4 * 10^38

[Collection Time]

TTI



E-RAB Activity (QCI)

The eNB collects the statistics data for the in-session time per QCI. In-session is defined as valid if a data transmission took place during the last

100 msec; it collects the in-session time of the Bearer which had data transmissions with the PDSCH/PUSCH during the statistics period for each

QCI.


The PM measures the ERAB_SEESION_UE every five seconds. These five-second samples are used to calculate the following statistics.

[Index]




[Statistics Type]



Lower/Upper

Limit

1 SessionTimeQCI msec Average in-session time per QCI SI avg (SessionTimeQCI) float 0~3.4 * 10^38

2 SessionTimeQCITot msec Total in-session time per QCI SI Tot (SessionTimeQCI) float 0~3.4 * 10^38

[Collection Time]

TTI



E-RAB simultaneous number

The eNB collects the statistics data for the average E-RAB count and the maximum E-RAB count per unit time for each cell.

[Index]




[Statistics Type]



Lower/Upper

Limit

1 UsageNbr count Average E-RAB count per unit time GAUGE avg (UsageNbr) float 0~3.4 * 10^38

2 UsageNbrMax count Maximum E-RAB count per unit time GAUGE max (UsageNbr) float 0~3.4 * 10^38



10.3.5 Handover (HO)

The Handover (HO) that collects the handover statistics data is divided into Intra LTE Handover and Inter RAT Handover. The Intra LTE Handover

is further divided into Intra eNB, Inter eNB S1 and Inter eNB X2 Handover. The Inter RAT Handover is further divided into Inter RAT HRPD,

Inter RAT UTRAN Handover, CSFB with PS Handover to UTRAN and CSFB with Redirection to UTRAN.

The Intra LTE Handover collects the statistics data through the source eNB and target eNB based on the source cell and target cell respectively.

The Inter RAT Handover collects the statistics data based on the eNB‟s served cell.

Intra eNB Handover

The eNB collects the statistics data for handover between cells within the base station for each cell.

[Index]


cNum 0~5 Source Cell Index

tcId 0~268435455 Target Cell Index.

Upper 20 bits: eNB number, lower 8 bits: cell number.

HOCause 0~1 Handover Cause

0: handover desirable for radio reasons

1: reserved



[Statistics Type]



Lower/Upper

Limit

1 IntraEnbAtt count The number of attempts for

intra-handover

CC The attempt ( in the following

figure) is performed (upon Intra

eNB Handover Decision).

int 0~2147483647

2 IntraEnbPrepSucc count The number of successes

for intra-handover

CC The preparation ( in the

following figure) is performed

(upon Target Cell Preparation).

int 0~2147483647

3 IntraEnbSucc count The number of successes

for intra-handover execution

CC The switch ( in the following

figure) is successful (upon

Internal Path Switch).

int 0~2147483647

4~134 IntraEnbPrepFail_S1AP_


IntraEnbPrepFail_MAC_Others

count Intra Handover Preparation


Fail Cause List‟.

CC The target cell preparation is

failed.

int 0~2147483647

135~

265

IntraEnbFail_S1AP_


IntraEnbFail_MAC_Others

count Intra Handover Execution


Fail Cause List‟.

CC The RRC Connection

Reconfiguration Complete

message is not received from

the terminal, and the Internal

Path Switch fails, etc.

int 0~2147483647





[Collection Time]

Figure 10.19 Intra eNB Handover collection time

After the reception of the Measurement Report message, if the message is evaluated as an Intra HO message by the HO Decision process, the

Attempt statistics will be counted. Once the inter-block handover process is ready and the RRC Connection Reconfiguration message is about to be

sent, the Prepare statistics will be counted. When the target cell successfully receives the RRC Connection Reconfiguration Complete message

from the terminal, the Success statistics will be counted. If the step ~ in the above process fails, it is counted as Prepare Fail and the

corresponding cause value is recorded. If the step ~ fails, it is counted as Intra Fail and the corresponding cause value is recorded.

eNB UE

UE moves to Intra eNB Cell



1 Attempt

2 Prepare

Measurement Report

3 Success

HO Decision

Target Cell

Preparation

Internal Path

Switch



X2 Handover Out

The eNB collects the statistics data for X2 handover between base stations for each cell in reference with the source eNB.

[Index]







1: reserved



[Statistics Type]



Lower/Upper

Limit

1 InterX2OutAtt count The number of X2 handover

attempts in SeNB


figure) is performed (upon Inter

eNB X2 Handover Decision).

int 0~2147483647

2 InterX2OutPrepSucc count The number of X2 handover

preparation successes in

SeNB



(reception of the X2 Handover

Request Ack message from the

target eNB).

int 0~2147483647

3 InterX2OutSucc count The number of X2 handover

successes in SeNB

CC The call release ( in the

following figure) is successful

(upon call release).

int 0~2147483647

4~134 InterX2OutPrepFail_S1AP_


InterX2OutPrepFail_MAC_Others

count SeNB‟s X2 Handover

Preparation failure count:


List‟.

CC The X2 Handover Request Ack

message from the target eNB is

not received.

int 0~2147483647

135~

265

InterX2OutFail_S1AP_

authentication_failure~

InterX2OutFail_MAC_Others

count SeNB‟s X2 Handover

Execution failure count:


List‟.

CC A failure case after preparation

( in the following figure) occurs

(All failure cases are collected).

(e.g. failure to setup the internal

resource, failure to receive the X2

UE Context Release Request

message, etc.)

int 0~2147483647







[Collection Time]

Figure 10.20 X2 Handover Out collection time

UE MME S/GW

Rrc Connection

Reconfiguration

1 Attempt

2 Prepare

Handover Request

Target eNB

Measurement Report

Source eNB

HO Decision

Handover Request

Acknowledge

SN Status Transfer

Path Switch Request

Path Switch Request

Acknowledge

Release Request

Call Release 3 Success

UE moves to Inter eNB Cell




After the reception of the Measurement Report message, if the message is evaluated as an Inter X2 HO message by the HO Decision process, the

Attempt statistics will be counted and the X2 Handover Request will be sent to the target eNB. When the X2 Handover Request Acknowledge

message is received from the target eNB, the Prepare statistics will be counted. The source eNB then sends the RRC Connection Reconfiguration

message to the terminal, and the target eNB receives the RRC Connection Reconfiguration Complete message from the terminal.

Once the handover is completed successfully, the target eNB sends the X2 UE Context Release message to the source eNB. The Source eNB then

processes the Success statistics count. If the step ~ in the above process fails, it is counted as Prepare Fail and the corresponding cause value is

recorded.

If the step ~ fails, it is counted as Inter X2 Fail and the corresponding cause value is recorded.

X2 Handover In

The eNB collects the statistics data for X2 handover between base stations for each cell in reference with the target eNB.

[Index]


cNum 0~5 Target Cell Index



1: reserved



[Statistics Type]



Lower/Upper

Limit

1 InterX2InAtt count The number of X2

handover attempts in

TeNB

CC The attempt ( in the following figure)

is performed (reception of the X2

Handover Request message from the

source eNB).

int 0~2147483647

2 InterX2InPrepSucc count The number of X2

handover preparation

successes in TeNB

CC The preparation ( in the following

figure) is performed (transmission of the

X2 Handover Request Ack message to

the source eNB).

int 0~2147483647

3 InterX2InSucc count The number of X2

handover execution

successes in TeNB

CC The handover notification ( in the


(transmission of the X2 UE Context

Release Request message to the source

eNB).

int 0~2147483647

4~134 InterX2InPrepFail_S1AP_

CauseRadioNetwork_

unspecified~InterX2InPrepFail_

MAC_Others

count TeNB‟s X2 Handover



List‟.

CC The setup the target eNB‟s internal

resource fails.

int 0~2147483647

135~

265

InterX2InFail_S1AP_

CauseRadioNetwork_

unspecified~InterX2InFail_

MAC_Others

count TeNB‟s X2 Handover



List‟.

CC A failure case after Prepare ( in the

following figure) occurs (All failure cases

are collected).

(e.g. failed to receive the RRC

Connection Reconfiguration Complete

message, failed to receive the SN Status

Transfer message, and failed to receive

the Path Switch Ack message, etc.)

int 0~2147483647







[Collection Time]

Figure 10.21 X2 Handover In collection time

UE MME S/GW

Rrc Connection

Reconfiguration

1 Attempt

2 Prepare

Handover Request

Target eNB

Measurement Report

Source eNB

HO Decision

Handover Request

Acknowledge

SN Status Transfer

Path Switch Request

Path Switch Request

Acknowledge

Release Request

Call Release

3 Success





The Attempt statistics will be counted upon the reception of the X2 Handover Request message by the target eNB; the Prepare statistics will be

counted after sending the X2 Handover Request Acknowledge message. After the RRC Connection Reconfiguration message is sent to the terminal

and the target eNB received the RRC Connection Reconfiguration Complete message from the terminal, upon successful completion of the

handover, the X2 UE Context Release message will be sent to the source eNB and the Success statistics will be counted. If the step ~ in the

above process fails, it is counted as Prepare Fail and the corresponding cause value is recorded. If the step ~ fails, it is counted as Inter X2 In

Fail and the corresponding cause value is recorded.

S1 Handover Out

The eNB collects the statistics data for S1 handover between base stations for each cell in reference with the source eNB.

[Index]







1: reserved



[Statistics Type]



Lower/Upper

Limit

1 InterS1OutAtt count The number of S1

handover attempts in

SeNB


figure) is performed (upon Inter eNB

S1 Handover Decision).

int 0~2147483647

2 InterS1OutPrepSucc count The number of S1


successes in SeNB


figure) is performed (reception of the

S1 Handover Command message).

int 0~2147483647

3 InterS1OutSucc count The number of S1

handover execution

successes in SeNB

CC The call release ( in the following

figure) is successful (upon call

release).

int 0~2147483647

4~134 InterS1OutPrepFail_S1AP_

CauseRadioNetwork_

unspecified~InterS1OutPrepFail_

MAC_Others

count SeNB‟s S1 Handover



List‟.

CC The S1 Handover Command

message from the MME is not

received.

int 0~2147483647

135~

265

InterS1OutFail_S1AP_

CauseRadioNetwork_

unspecified~InterS1OutFail_

MAC_Others

count SeNB‟s S1 Handover



List‟.


following figure) occurs (All failure

cases are collected).


resource, failure to receive the UE

Context Release Command

message, etc.)

int 0~2147483647







[Collection Time]

Figure 10.22 S1 Handover Out collection time

UE MME S/GW

Rrc Connection

Reconfiguration

1 Attempt

2 Prepare

Target eNB

Measurement Report

Source eNB

HO Decision

Handover Request

MME Status Transfer

Handover Notify


Call Release 3 Success



Handover Required

Handover Request

Acknowledge

Handover Command

eNB Status Transfer

Tracking Area Update Procedure (NAS)




After the reception of the Measurement Report message, if the message is evaluated as an Inter S1 HO message by the HO Decision process, the

Attempt statistics will be counted and the S1 Handover Required message will be sent to the MME. When the S1 Handover Command message is

received from the MME, the Prepare statistics will be counted.

The source eNB then sends the RRC Connection Reconfiguration message to the terminal, and the target eNB receives the RRC Connection

Reconfiguration Complete message from the terminal. Once the handover is completed successfully, the MME sends the S1 UE Context Release

Command message to the source eNB. The Source eNB then processes the Success statistics count. If the step ~ in the above process fails, it is

counted as Prepare Fail and the corresponding cause value is recorded. If the step ~ fails, it is counted as Inter S1 Out Fail and the

corresponding cause value is recorded.

S1 Handover In

The eNB collects the statistics data for S1 handover between base stations for each cell in reference with the target eNB.

[Index]





1: reserved



[Statistics Type]



Lower/Upper

Limit

1 InterS1InAtt count The number of attempts for

S1 handover in TeNB


figure) is performed (reception of the

S1 Handover Request message from

the MME).

int 0~2147483647

2 InterS1InPrepSucc count The number of successes

for S1 handover

preparation in TeNB


figure) is performed (transmission of

the S1 Handover Request Ack

message to the MME).

int 0~2147483647

3 InterS1InSucc count The number of successes

for S1 handover execution

in TeNB



(transmission of the S1 Handover

Notify message to the MME).

int 0~2147483647

4~134 InterS1InPrepFail_S1AP_

CauseRadioNetwork_

unspecified~InterS1InPrepFail_

MAC_Others

count TeNB‟s S1 Handover



List‟.

CC The setup of the target eNB‟s

internal resource fails.

int 0~2147483647

135~

265

InterS1InFail_S1AP_

CauseRadioNetwork_

unspecified~InterS1InFail_

MAC_Others

count TeNB‟s S1 Handover



List‟.


following figure) occurs (All failure

cases are collected).

(e.g. failure to receive the RRC

Connection Reconfiguration

Complete message, failure to receive

the MME Status Transfer message,

etc.)

int 0~2147483647







[Collection Time]

Figure 10.23 S1 Handover In collection time

UE MME S/GW

Rrc Connection

Reconfiguration

1 Attempt

Prepare

Target eNB

Measurement Report

Source eNB

HO Decision

Handover Request

MME Status Transfer

Handover Notify


Call Release

Success



Handover Required

Handover Request

Acknowledge

Handover Command

eNB Status Transfer

Tracking Area Update Procedure (NAS)


3

2



The Attempt statistics will be counted upon the reception of the S1 Handover Request message by the target eNB; the Prepare statistics will be

counted after sending the S1 Handover Request Acknowledge message. After the RRC Connection Reconfiguration message is sent to the terminal

and the target eNB received the RRC Connection Reconfiguration Complete message from the terminal, upon successful completion of the

handover, the S1 Handover Notify message will be sent to the MME and the Success statistics will be counted. If the step ~ in the above

process fails, it is counted as Prepare Fail and the corresponding cause value is recorded. If the step ~ fails, it is counted as Inter S1 In Fail and

the corresponding cause value is recorded.

Inter-RAT HRPD Handover (Other than eNB)

The eNB collects the statistics data for handover between the LTE system and eHRPD system for each cell.

[Index]





1: reserved



[Statistics Type]



Lower/Upper

Limit

1 RatOutAttHRPD count The number of attempts

for Inter-RAT HRPD

handover


figure) is performed (upon Inter RAT

CDMA HRPD Optimized Handover

Decision).

int 0~2147483647

2 RatOutPrepSuccHRPD count The number of successes

for Inter-RAT HRPD



figure) is performed (Transmission of

the data received from the MME to

the terminal via the Mobility From

Eutra Command message).

int 0~2147483647

3 RatOutSuccHRPD count The number of successes

for Inter-RAT HRPD

handover execution

CC The call release ( in the following

figure) is successful (upon call

release).

int 0~2147483647

4~134 RatOutPrepFailHRPD_S1AP_


RatOutPrepFailHRPD_MAC_

Others

count Inter RAT HRPD

Handover Preparation

failure count:


List‟.

CC A failure case occurs after Attempt

( in the following figure).

(e.g. failure to receive the UL

Handover Preparation Transfer

message, failure to receive the

Downlink S1 cdma2000 tunneling

message, etc.)

int 0~2147483647

135~

265

RatOutFailHRPD_S1AP_


RatOutFailHRPD_MAC_Others

count Inter RAT HRPD

Handover Execution

failure count:


List‟.

CC A failure case occurs after Prepare



resource, etc.)

int 0~2147483647







[Collection Time]

Figure 10.24 Inter-RAT HRPD Handover (other than eNB) collection time

UE MME S/GW

Handover From EUTRA

Preparation Request

Attempt

Prepare

Measurement Report

Source eNB

HO Decision


Call Release

Success

UE moves to CDMA HRPD

UL S1 cdma2000 Tunneling


1

2

3

UL Handover

Preparation Transfer

Mobility From

EUTRA Command

DL S1 cdma2000 Tunneling



After the reception of the Measurement Report message, if the message is evaluated as a HRPD Handover Execution message, the Attempt

statistics will be counted. When the Mobility EUTRA Command message is sent, the Prepare statistics will be counted. Upon successful

completion of the handover, the UE Context Release Command message will be received from the MME and the Success statistics will be counted.

If the step ~ in the above process fails, it is counted as Prepare Fail and the corresponding cause value is recorded. If the step ~ fails, it is

counted as Inter RAT HRPD Fail and the corresponding cause value is recorded.

Inter-RAT UTRAN PS Handover OUT

The eNB collects the statistics data for the handover between the LTE system and UTRAN system for each cell.

[Index]





1: reserved



[Statistics Type]



Lower/Upper

Limit

1 RatOutAttUTRAN count The number of attempts for LTE

to Inter RAT UTRAN handover



RAT UTRAN Handover

Decision).

int 0~2147483647

2 RatOutPrepSuccUTRAN count The number of successes for

LTE to Inter RAT UTRAN




(Transmission of the data

received from the MME to the

terminal via the Mobility From


int 0~2147483647

3 RatOutSuccUTRAN count LTE to Inter RAT UTRAN

Handover Preparation failure

count: The handover preparation

fails in the target EPC.




int 0~2147483647

4~134 RatOutPrepFailUTRAN_S1AP_

CauseRadioNetwork_

unspecified~

RatOutPrepFailUTRAN_MAC_

Others

count LTE to Inter RAT UTRAN


count: The handover preparation

fails due to the handover failure

in the GW or the MME cannot

perform the handover.



received.

int 0~2147483647

135~

265

RatOutFailUTRAN_S1AP_

CauseRadioNetwork_

unspecified~RatOutFailUTRAN_

MAC_Others

count LTE to Inter RAT UTRAN


count: The handover to the

target cell is not allowed if the

target eNB is in the HO

restriction list.

CC A failure case occurs after

Prepare ( in the following

figure).


resource, failure to receive the


message, etc.)

int 0~2147483647



[Collection Time]

Figure 10.25 Inter-RAT UTRAN PS Handover OUT collection time

After the reception of the Measurement Report message, if the message is evaluated as a UTRAN Handover Execution message, the Attempt

statistics will be counted and the S1 Handover Required message will be sent. When the Mobility Eutra Command message is sent, the Prepare

statistics will be counted. Upon successful completion of the handover, the UE Context Release Complete message will be sent from the MME and

the Success statistics will be counted. If the step ~ in the above process fails, it is counted as Prepare Fail and the corresponding cause value is

recorded. If the step ~ fails, it is counted as Inter RAT UTRAN HO Out Fail and the corresponding cause value is recorded.

UE MME

Attempt

Prepare

Measurement Report

Source eNB

HO Decistion


Call Release Success

Handover Required


1

2

3

Handover Command

Mobility From EUTRA Command



Inter-RAT UTRAN PS Handover IN

The eNB collects the statistics data for the handover between the LTE system and UTRAN system for each cell.

[Index]





1: reserved

[Statistics Type]



Lower/Upper

Limit

1 RatInAttUTRAN count The number of attempts

for Inter RAT UTRAN to

LTE handover


figure) is performed (reception of

the S1 Handover Request message

from the MME).

int 0~2147483647

2 RatInPrepSuccUTRAN count The number of successes


LTE handover preparation


figure) is performed (transmission

of the S1 Handover Request Ack

message to the MME).

int 0~2147483647

3 RatInSuccUTRAN count The number of successes


LTE handover execution



(transmission of the S1 Handover

Notify message to the MME).

int 0~2147483647



(Continued)



Lower/Upper

Limit

4~134 RatInPrepFailUTRAN_S1AP_


RatInPrepFailUTRAN_MAC_

Others

count Inter RAT UTRAN to LTE

Handover Preparation

failure count: See

„Statistics Fail Cause List‟.

CC A failure case occurs after Attempt



resource, etc.)

int 0~2147483647

135~

265

RatInFailUTRAN_S1AP_


RatInFailUTRAN_MAC_Others

count Inter RAT UTRAN to LTE

Handover Execution

failure count: See


CC A failure case after Prepare ( in

the following figure) occurs (All

failure cases are collected).

(e.g. failure to receive the RRC

Connection Reconfiguration

Complete message, failure to

receive the MME Status Transfer

message, etc.)

int 0~2147483647





[Collection Time]

Figure 10.26 Inter-RAT UTRAN PS Handover IN collection time

The Attempt statistics will be counted upon the reception of the S1 Handover Request message by the target eNB; the Prepare statistics will be

counted after sending the S1 Handover Request Acknowledge message. After the target eNB receives the RRC Connection Reconfiguration

Complete message from the terminal, upon successful completion of the handover, the S1 Handover Notify message will be sent to the MME, and

the Success statistics will be counted. If the step ~ in the above process fails, it is counted as Prepare Fail and the corresponding cause value is

recorded. If the step ~ fails, it is counted as Inter RAT UTRAN IN Fail and the corresponding cause value is recorded.

UE MME Target eNB

Handover Request

Handover Notify

Attempt 1

Prepare 2

Success 3

Handover Request Acknowledge


(Handover to E-UTRAN Complete)



Handover Time (Average, Max)

The eNB collects the statistics data for the average setup time and the maximum setup time of the handover interrupt time in the TeNB for each cell.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 IntraHOTime msec Average Intra HO Interrupt time GAUGE The time elapsed from the transmission of the

RRCConnectionReconfiguration message to

the UE until the reception of the

RRCConnectionReconfigurationComplete


Formula: avg (IntraHOTime)

float 0~3.4 * 10^38

2 IntraHOTimeMax msec Average maximum Intra HO

Interrupt time

GAUGE max (IntraHOTime) float 0~3.4 * 10^38

3 IntraHOTimeTot msec Total Intra HO Interrupt time GAUGE tot (IntraHOTime) float 0~3.4 * 10^38

4 S1HOTime msec Average S1 HO Interrupt time GAUGE The time elapsed from the transmission of the

S1 Handover Request Acknowledge message

to the MME until the reception of the



Formula: avg (S1HOTime)

float 0~3.4 * 10^38



(Continued)



Lower/Upper

Limit

5 S1HOTimeMax msec Average maximum S1 HO

Interrupt time

GAUGE max (S1HOTime) float 0~3.4 * 10^38

6 S1HOTimeTot msec Total S1 HO Interrupt time GAUGE tot (S1HOTime) float 0~3.4 * 10^38

7 X2HOTime msec Average X2 HO Interrupt time GAUGE The time elapsed from the transmission of the

X2 Handover Request Acknowledge message

to the Source eNB until the reception of the



Formula: avg (X2HOTime))

float 0~3.4 * 10^38

8 X2HOTimeMax msec Average maximum X2 HO

Interrupt time

GAUGE max (X2HOTime) float 0~3.4 * 10^38

9 X2HOTimeTot msec Total X2 HO Interrupt time GAUGE tot (X2HOTime) float 0~3.4 * 10^38



[Collection Time]

Figure 10.27 Handover Time (INTRA) collection time

eNB UE

UE moves to Intra eNB Cell



Measurement Report

HO Decision

Target Cell Preparation

Internal Path Switch

HO Time



Figure 10.28 Handover Time (INTER S1) collection time

UE MME S/GW

Rrc Connection

Reconfiguration

Handover Request

Target eNB

Measurement Report

Source eNB

HO Decision

Handover Request

Acknowledge

Handover Required



Handover Command

HO Time



Figure 10.29 Handover Time (INTER X2) collection time

The corresponding statistics are measured based on TeNB. The Intra Handover represents the time elapsed from the transmission of the RRC

Connection Reconfiguration message to the terminal until the reception of the RRC Connection Reconfiguration Complete message. The Inter X2

Handover represents the time elapsed from the transmission of the X2 Handover Request Acknowledge message from the target eNB until the

reception of the RRC Connection Reconfiguration Complete message by the terminal. The Inter X2 Handover represents the time elapsed from the

transmission of the S1 Handover Request Acknowledge message from the target eNB until the reception of the RRC Connection Reconfiguration

Complete message by the terminal.

UE MME S/GW

Rrc Connection

Reconfiguration

Handover Request

Target eNB

Measurement Report

Source eNB

HO Decision

Handover Request

Acknowledge



HO Time



10.3.6 CSFB

CSFB PS Handover OUT

The eNB collects the statistics data for the CSFB with PS Handover between the LTE system and UTRAN system for each cell.

[Index]



csfbInd 0~1 CSFB Indicator

0: Normal

1: High Priority

[Statistics Type]



Lower/Upper

Limit

1 CsfbPsHoAttUTRAN count The number of attempts for

CSFB with Inter RAT

UTRAN PS handover



RAT UTRAN Handover Decision).

int 0~2147483647

2 CsfbPsHoPrepSuccUTRAN count The number of successes

for CSFB with Inter RAT

UTRAN PS handover

preparation



(Transmission of the data

received from the MME to the

terminal via the Mobility From


int 0~2147483647



(Continued)



Lower/Upper

Limit

3 CsfbPsHoSuccUTRAN count The number of successes

for CSFB with Inter RAT

UTRAN PS handover

execution




int 0~2147483647

4~134 CsfbPsHoPrepFailUTRAN_

S1AP_CauseRadioNetwork_

unspecified~

CsfbPsHoPrepFailUTRAN_MAC_

Others

count CSFB with Inter RAT

UTRAN PS Handover



List‟.



received.

int 0~2147483647

135~

265

CsfbPsHoFailUTRAN_S1AP_


CsfbPsHoFailUTRAN_MAC_

Others

count CSFB with Inter RAT

UTRAN PS Handover

Execution failure count: See


CC A failure case after Prepare ( in

the following figure) occurs (All

failure cases are collected).


resource, failure to receive the UE

Context Release Command

message, etc.)

int 0~2147483647






[Collection Time]

Figure 10.30 CSFB PS Handover OUT collection time

After the reception of the Measurement Report message, if the message is evaluated as a HO UTRAN message by the HO Decision process, the

Attempt statistics will be counted and the S1 Handover Required message will be sent to the MME. When the S1 Handover Command message is

received from the MME, the Prepare statistics will be counted. The source eNB sends the Mobility From EUTRA Command message to the

terminal, and the MME sends the S1 UE Context Release Command message to the source eNB. The Source eNB then processes the Success

statistics count. If the step ~ in the above process fails, it is counted as Prepare Fail and the corresponding cause value is recorded. If the step

~ fails, it is counted as CSFB PS HO UTRAN Out and the corresponding cause value is recorded.

UE Source eNB MME

Solicit Measurement Report

Call Release

1 1 Attempt

1 3 Success

1 2 Prepare

Initial Context Setup Request (with CSFB Ind)

or UE Context Modification Request (with CSFB Ind)

Mobility From EUTRA Command

Handover Required

Handover Command





CSFB Redirection OUT

The eNB collects the statistics data for the CSFB with Redirection between the LTE system and UTRAN system for each cell.

[Index]



csfbInd 0~1 CSFB Indicator

0: Normal

1: High Priority

SIBOwn 0~1 Whether the UTRAN SI information is included

0: Not Included

1: Included

[Statistics Type]



Lower/Upper

Limit

1 CsfbRedirAttUTRAN count The number of attempts for

CSFB with Redirection to Inter

RAT UTRAN


figure) is performed (upon the

CSFB with Redirection

decision).

int 0~2147483647

2 CsfbRedirPrepSuccUTRAN count The number of successes for


RAT UTRAN Preparation



(upon the CSFB with

Redirection decision).

int 0~2147483647



(Continued)



Lower/Upper

Limit

3 CsfbRedirSuccUTRAN count The number of successes for


RAT UTRAN Execution

CC The message sending ( in the


(upon sending the RRC

Connection Release message to

the terminal).

int 0~2147483647

4~134 CsfbRedirPrepFailUTRAN_S1AP_


CsfbRedirPrepFailUTRAN_MAC_

Others

count CSFB with Redirection to Inter

RAT UTRAN Preparation


Fail Cause List‟.

CC Not applicable. int 0~2147483647

135~

265

CsfbRedirFailUTRAN_S1AP_


CsfbRedirFailUTRAN_MAC_

Others

count CSFB with Redirection to Inter

RAT UTRAN Execution failure

count: See „Statistics Fail

Cause List‟.

CC Not applicable. int 0~2147483647






[Collection Time]

Figure 10.31 CSFB Redirection OUT collection time

After the reception of CSFB Indicator IE within the Initial Context Setup Request message or the UE Context Modification Request message, if the

message is evaluated as CSFB, the Attempt statistics will be counted. When the station becomes ready, the Prepare statistics will be counted.

The Success statistics will be counted upon the transmission of the RRC Connection Release message to the terminal for redirection.

UE Source eNB MME

Call Release

1 1 Attempt

1 3 Success

1 2 Prepare

Initial Context Setup Request (with CSFB Ind)

or UE Context Modification Request (with CSFB Ind)

RRC connection Release (with Redirection Info)


or UE Context Modification Response

Redirection



10.3.7 CSL

The CSL, or the Call Summary Log, is counted upon call release. Based on the CSL‟s Call Release Cause and other diverse information, the

operator can analyze the cause of the call release and get the details of the corresponding call. For the details on each item, refer to the explanation

of the statistics of each item below.

Call Fail Report

The eNB collects the statistics for the CSL for each cell. The CSL statistics are collected when the call is released, and can help identify the actual

cause of the call release.

[Index]



[Statistics Type]


Method

Count Collected

When Type

Lower/Upper

Limit

1 c_NO_FAULT count The call ends successfully. CC - int 0~2147483647

2 c_S1AP_CauseRadioNetwork_

unspecified

count A failure occurs in GW during the handover, or

the handover preparation fails if the MME

cannot process the handover.

CC - int 0~2147483647

3 c_S1AP_tx2relocoverall_expiry count After receiving the Handover Request

Acknowledge message from the source eNB,

the timer ends while waiting for the UE Context

Release message from the target eNB.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

4 c_S1AP_successful_handover count The handover has completed successfully. CC - int 0~2147483647

5 c_S1AP_release_due_to_

eutran_generated_reason

count Released due to a cause from the E_UTRAN. CC - int 0~2147483647

6 c_S1AP_handover_cancelled count An action is taken due to the cancellation of the

handover.

CC - int 0~2147483647

7 c_S1AP_partial_handover count The E-RABs to Release List IE message is

included in the reception of the Handover

Command message, and it is determined that

the source eNB will not process the UE

handover to a specific target eNB.

CC - int 0~2147483647

8 c_S1AP_ho_failure_in_target_

EPC_eNB_or_target_system

count The handover preparation fails in the target

EPC.

CC - int 0~2147483647

9 c_S1AP_ho_target_not_

allowed

count The handover to the target cell is not allowed if

the target eNB is listed in the handover

restriction list.

CC - int 0~2147483647

10 c_S1AP_tS1relocoverall_expiry count After receiving the Handover Command

message from the source eNB, the timer ends

while waiting for the UE Context Release

Command message from the MME.

CC - int 0~2147483647

11 c_S1AP_tS1relocprep_expiry count The timer expires while the source eNB sends

the Handover Required message and waits for

the handover command.

CC - int 0~2147483647

12 c_S1AP_cell_not_available count The related cell is not available. CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

13 c_S1AP_unknown_targetID count The handover preparation fails because the

MME does not recognize the target ID received

from the SeNB.

CC - int 0~2147483647

14 c_S1AP_no_radio_resources_


count A handover preparation failure is received from

the MME.

CC - int 0~2147483647

15 c_S1AP_unknown_mme_ue_

s1ap_id

count The corresponding action fails when the MME

UE S1AP ID is unknown, or when a message

received from the eNB for the first time carries

an already identified MME UE S1AP ID.

CC - int 0~2147483647

16 c_S1AP_unknown_enb_ue_

s1ap_id

count The corresponding action fails when the ENB

UE S1AP ID is unknown, or when a message

received from the eNB for the first time carries

an already identified ENB UE S1AP ID.

CC - int 0~2147483647

17 c_S1AP_unknown_pair_ue_

s1ap_id

count The corresponding action fails when both items

of the UE S1AP ID pair are unknown or when

they are not defined in one context.

CC - int 0~2147483647

18 c_S1AP_handover_desirable_

for_radio_reason

count The reason of the handover request is wireless

related.

CC - int 0~2147483647

19 c_S1AP_time_critical_

handover

count Requests a handover because otherwise the

connection with the UE may be dropped.

CC - int 0~2147483647

20 c_S1AP_resource_

optimisation_handover

count Requests a handover to improve the load

balancing among the neighbor cells.

CC - int 0~2147483647

21 c_S1AP_reduce_load_in_

serving_cell

count Reduces the load of the serving cell. CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

22 c_S1AP_user_inactivity count All calls must be released due to the user

inactivity.

CC - int 0~2147483647

23 c_S1AP_radio_connection_

with_ue_lost

count The call must be released because the UE lost

the radio connection.

CC - int 0~2147483647

24 c_S1AP_load_balancing_tau_

required

count A TAU is requested for load balancing from the

MME.

CC - int 0~2147483647

25 c_S1AP_cs_fallback_triggered count A CS Fallback is triggered. CC - int 0~2147483647

26 c_S1AP_ue_not_available_

for_ps_service

count An action is taken because a Cell Change

Order is triggered.

CC - int 0~2147483647

27 c_S1AP_radio_resources_

not_available

count The requested radio resources are not

available.

CC - int 0~2147483647

28 c_S1AP_failure_in_radio_

interface_procedure

count The radio interface procedure fails. CC - int 0~2147483647

29 c_S1AP_invalid_qos_

combination

count The action fails due to the invalid QoS. CC - int 0~2147483647

30 c_S1AP_interrat_redirection count Release is requested due to the inter-RAT

redirection.

CC - int 0~2147483647

31 c_S1AP_interaction_with_

other_procedure

count Interrupts with other active procedures. CC - int 0~2147483647

32 c_S1AP_unknown_E_RAB_ID count Due to receiving incorrect E_RAB ID within

eNB, the procedure fails.

CC - int 0~2147483647

33 c_S1AP_multiple_E_RAB_ID_

instances

count Due to receiving duplicated E_RAB ID, the

procedure fails.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

34 c_S1AP_encryption_and_or_

integrity_protection_

algorithms_not_supported

count The eNB does not support the integrity and

encryption algorithms supported by the UE.

CC - int 0~2147483647

35 c_S1AP_s1_intra_system_

handover_triggered

count S1 Intra Handover is triggered. CC - int 0~2147483647

36 c_S1AP_s1_inter_system_

handover_triggered

count S1 Inter Handover is triggered. CC - int 0~2147483647

37 c_S1AP_x2_handover_

triggered

count X2 Handover is triggered. CC - int 0~2147483647

38 c_S1AP_redirection_towards_

1xRTT

count Occurs because a redirection to the 1xRTT

System is requested.

CC - int 0~2147483647

39 c_S1AP_not_supported_QCI_

value

count The E-RAB Setup fails because the requested

QCI is not supported.

CC - int 0~2147483647

40 c_S1AP_invalid_CSG_Id count The CSG ID provided to the target eNB is

invalid.

CC - int 0~2147483647

41 c_S1AP_transport_resource_

unavailable

count The transport resource is not available. CC - int 0~2147483647

42 c_S1AP_CauseTransport_

unspecified

count A failure occurs due to a reason related to the

transport layer other than the above error.

CC - int 0~2147483647

43 c_S1AP_normal_release count Released normally. CC - int 0~2147483647

44 c_S1AP_authentication_failure count The call is cancelled by the MME due to the

terminal authentication failure during the

attach.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

45 c_S1AP_detach count Detached. CC - int 0~2147483647

46 c_S1AP_CauseNas_

unspecified

count The Context Release Command message is

sent due to an unspecified failure in the MME.

CC - int 0~2147483647

47 c_S1AP_csg_subscription_

expiry

count The UE is not registered in the target cell‟s

CSG, or its registration has expired.

CC - int 0~2147483647

48 c_S1AP_transfer_syntax_error count The received message contains a transfer

syntax error.

CC - int 0~2147483647

49 c_S1AP_abstract_syntax_

error_reject

count The received message contains an abstract

syntax error and the related criticality reads

„reject‟.

CC - int 0~2147483647


error_ignore_and_notify



„ignore and notify‟.

CC - int 0~2147483647

51 c_S1AP_message_not_

compatible_with_receiver_state

count The received message does not correspond to

the reception state.

CC - int 0~2147483647

52 c_S1AP_semantic_error count The received message contains a semantic

error.

CC - int 0~2147483647


error_falsely_constructed_

message

count The order of the IE group or IE contained in the

received message is incorrect.

CC - int 0~2147483647

54 c_S1AP_CauseProtocol_

unspecified


protocol other than the above error.

CC - int 0~2147483647

55 c_S1AP_control_processing_

overload

count A control processing overload occurs. CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

56 c_S1AP_not_enough_user_

plane_processing_resources

count The resource related to the user plane is

insufficient.

CC - int 0~2147483647

57 c_S1AP_hardware_failure count An action is taken due to the hardware failure. CC - int 0~2147483647

58 c_S1AP_om_intervention count An action is taken due to the OAM intervention. CC - int 0~2147483647

59 c_S1AP_CauseMisc_

unspecified

count UE duplication occurs in the MME. CC - int 0~2147483647

60 c_S1AP_unknown_PLMN count The MME does not recognize the PLMN value

sent from the eNB.

CC - int 0~2147483647

61 c_X2AP_handover_desirable_

for_radio_reasons

count The reason of the handover request is wireless

related.

CC - int 0~2147483647

62 c_X2AP_time_critical_

handover

count Requests a handover because otherwise the

connection with the UE may be dropped.

CC - int 0~2147483647

63 c_X2AP_resource_

optimisation_handover

count Requests a handover to improve the load

balancing among the neighbor cells.

CC - int 0~2147483647

64 c_X2AP_reduce_load_in_

serving_cell

count Reduces the load of the serving cell. CC - int 0~2147483647

65 c_X2AP_partial_handover count The E-RABs to Release List IE message is

included in the reception of the Handover

Command message, and it is determined that

the source eNB will not process the UE

handover to a specific target eNB.

CC - int 0~2147483647

66 c_X2AP_unknown_new_eNB_

UE_X2AP_ID

count A failure related to the reception of unknown

new_eNB_UE_X2 ID occurs.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

67 c_X2AP_unknown_old_eNB_

UE_X2AP_ID


old_eNB_UE_X2 ID occurs.

CC - int 0~2147483647

68 c_X2AP_unknown_pair_of_

UE_X2AP_ID


New old_eNB_X2_ID, old_eNB_UE_X2 ID pair

occurs.

CC - int 0~2147483647

69 c_X2AP_ho_target_not_

allowed

count The handover to the target cell is not allowed

due to a UE problem.

CC - int 0~2147483647

70 c_X2AP_tx2relocoverall_expiry count Occurs due to the termination of the TX2

RelocOverall timer.

CC - int 0~2147483647

71 c_X2AP_trelocprep_expiry count A timeout occurs during the handover

preparation in the SeNB while processing the

X2 handover.

CC - int 0~2147483647

72 c_X2AP_cell_not_available count The handover for the problematic (suspicious)

UE to the designated target cell is not allowed.

CC - int 0~2147483647

73 c_X2AP_no_radio_resources_


count A handover preparation failure is received from

the TeNB.

CC - int 0~2147483647

74 c_X2AP_invalid_MME_GroupI

D

count The target eNB is not in the same pool area as

the source eNB.

CC - int 0~2147483647

75 c_X2AP_unknown_MME_Code count The target eNB is in the same pool area as the

source eNB, but does not recognize the MME

code.

CC - int 0~2147483647

76 c_X2AP_encryption_and_or_

integrity_protection_

algorithms_not_supported

count The target eNB does not support the integrity

and encryption algorithms supported by the

UE.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

77 c_X2AP_

reportCharacteristicsEmpty

count The characteristic report does not exist. CC - int 0~2147483647

78 c_X2AP_noReportPeriodicity count The periodicity is not defined. CC - int 0~2147483647

79 c_X2AP_existingMeasurementID count Some measurement IDs are not unknown. CC - int 0~2147483647

80 c_X2AP_unknown_eNB_

Measurement_ID

count The eNB cannot provide the requested

measurement object temporarily.

CC - int 0~2147483647

81 c_X2AP_measurement_

temporarily_not_available

count An action is taken due to an unknown reason in

the radio network.

CC - int 0~2147483647

82 c_X2AP_CauseRadioNetwork_

unspecified

count An action is taken due to an unknown reason in

the radio network.

CC - int 0~2147483647

83 c_X2AP_load_balancing count The mobility setting is modified for load

balancing.

CC - int 0~2147483647

84 c_X2AP_handover_optimisation count The mobility setting is modified for handover

optimization.

CC - int 0~2147483647

85 c_X2AP_value_out_of_

allowed_range

count The handover trigger parameter modification is

too higher or lower than the mobility parameter.

CC - int 0~2147483647

86 c_X2AP_multiple_E_RAB_ID_

instances

count The same E-RAB has multiple instances, thus

the corresponding action is taken.

CC - int 0~2147483647

87 c_X2AP_switch_off_ongoing count Searches for the next handover cell because a

switch-off occurred during the handover.

CC - int 0~2147483647

88 c_X2AP_transport_resource_

unavailable

count The transport resource is not available. CC - int 0~2147483647

89 c_X2AP_CauseTransport_

unspecified


transport layer other than the above error.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

90 c_X2AP_transfer_syntax_error count The received message contains a transfer

syntax error.

CC - int 0~2147483647

91 c_X2AP_abstract_syntax_

error_reject



„reject‟.

CC - int 0~2147483647


error_ignore_and_notify



„ignore and notify‟.

CC - int 0~2147483647

94 c_X2AP_semantic_error count The received message contains a semantic

error.

CC - int 0~2147483647

95 c_X2AP_CauseProtocol_

unspecified


protocol other than the above error.

CC - int 0~2147483647


error_falsely_constructed_

message

count The IE or IE group contained in the received

message are in wrong order, or have multiple

occurrences.

CC - int 0~2147483647

97 c_X2AP_control_processing_

overload

count The eNB control processing is overloaded. CC - int 0~2147483647

98 c_X2AP_hardware_failure count The eNB hardware fails. CC - int 0~2147483647

99 c_X2AP_om_intervention count An internal failure occurs in the base station

due to the abnormal OAM.

CC - int 0~2147483647

100 c_X2AP_not_enough_user_

plane_processing_resources

count A call is cancelled due to the insufficient user

plane resource.

CC - int 0~2147483647

101 c_X2AP_CauseMisc_

unspecified

count Default X2 cause in the eNB. CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

102 c_ECC_TMOUT_

rrcConnectionSetup

count The RRC Connection Setup Complete

message is not received after sending the RRC

Connection Setup message to the UE.

CC - int 0~2147483647

103 c_ECC_TMOUT_


count The RRC Connection Reconfiguration

Complete message is not received after

sending the RRC Connection Reconfiguration

message during the attach.

CC - int 0~2147483647

104 c_ECC_TMOUT_

rrcConnectionReEstablish

count The RRC Connection Reestablishment

Complete message is not received after

sending the RRC Connection Reestablishment

message to the UE.

CC - int 0~2147483647

105 c_ECC_TMOUT_

rrcSecurityModeCommand

count The Security Mode Complete message is not

received after sending the Security Mode

Command message to the UE.

CC - int 0~2147483647

106 c_ECC_TMOUT_

rrcUeCapabilityEnquiry

count The UE Capability Information message is not

received after sending the UE Capability

Enquiry message to the UE.

CC - int 0~2147483647

107 c_ECC_TMOUT_

rrcConnectionRelease

count The msgCpdcpDataTransferCnf message from

the PDCB is not received after sending the

RRC Connection Release message to the UE.

CC - int 0~2147483647

108 c_ECC_TMOUT_

rrcHandoverPreparation

count The UL Handover Preparation Transfer

message is not received after sending the

Handover From EUTRA Preparation Request

message.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

109 c_ECC_TMOUT_intra_

HandoverCmdComplete

count The target cell cannot receive the RRC

Connection Reconfiguration Complete

message while processing the intra-handover.

CC - int 0~2147483647

110 c_ECC_TMOUT_inter_

X2HandoverCmdComplete

count The TeNB cannot receive the RRC Connection

Reconfiguration Complete message while


CC - int 0~2147483647

111 c_ECC_TMOUT_inter_

S1HandoverCmdComplete

count The TeNB cannot receive the RRC Connection

Reconfiguration Complete message while

processing the S1 handover.

CC - int 0~2147483647

112 c_ECC_TMOUT_s1Setup count The S1 Setup Response message is not

received after sending the S1 Setup Request

message to the MME.

CC - int 0~2147483647

113 c_ECC_TMOUT_s1Update count The ENB Configuration Update Acknowledge

message is not received after sending the ENB

Configuration Update message to the MME.

CC - int 0~2147483647

114 c_ECC_TMOUT_

s1InitialContextSetup

count The call is cancelled because the Initial

Context Setup Request message is not

received after sending the Initial UE message

to the MME.

CC - int 0~2147483647

115 c_ECC_TMOUT_

s1ErabReleaseIndication

count After sending the Erab Release Indication

message to the MME, cannot receive the Erab

Release Command message

CC - int 0~2147483647

116 c_ECC_TMOUT_

s1UeContextRelease

count After sending the UE Context Release Request

message to the MME, cannot receive the UE

Context Release Command message

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

117 c_ECC_TMOUT_s1PathSwitch count The call is cancelled because the Path Switch

Request Acknowledge message is not received

after the TeNB sends the Path Switch Request

message while processing the X2 handover.

CC - int 0~2147483647

118 c_ECC_TMOUT_

s1HandoverPreparation

count After sending the Handover Required message

to the MME, cannot receive the Handover

Command message.

CC - int 0~2147483647

119 c_ECC_TMOUT_

s1RelocOverall

count The call is cancelled because a RelocOverall

Timeout occurred in the SeNB while processing

the S1 handover.

CC - int 0~2147483647

120 c_ECC_TMOUT_

s1HandoverCancel

count Currently unused. CC - int 0~2147483647

121 c_ECC_TMOUT_

s1MMEStatusTransfer

count The TeNB cannot receive the MME Status

Transfer message after the SeNB sends the

eNB Status Transfer message to the MME.

CC - int 0~2147483647

122 c_ECC_TMOUT_X2Setup count After sending the X2 Setup message, cannot

receive the X2Setup Response message.

CC - int 0~2147483647

123 c_ECC_TMOUT_X2Update count After sending the eNB Configuration Update

message, cannot receive the eNB

Configuration Update Acknowledge message.

CC - int 0~2147483647

124 c_ECC_TMOUT_

x2HandoverPreparation

count After sending the Handover Request to the

Target eNB, cannot receive the Handover

Request Acknowledge message.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

125 c_ECC_TMOUT_

x2RelocOverall

count The call is cancelled because a RelocOverall

Timeout occurred in the SeNB while


CC - int 0~2147483647

126 c_ECC_TMOUT_

x2SNStatusTransfer

count The TeNB cannot receive the X2SNStatus

Transfer message sent from the SeNB.

CC - int 0~2147483647

127 c_ECC_TMOUT_

internalResourceSetup

count The response message is not received after the

SetupReq message is sent for setting the

resource for the internal protocol blocks of the

eNB.

CC - int 0~2147483647

128 c_ECC_TMOUT_

internalResourceRelease

count The response message is not received after

sending the ReleaseReq message for setting

the resource for the internal protocol blocks of

the eNB.

CC - int 0~2147483647

129 c_ECC_TMOUT_

internalSecurityControl

count The msgCpdcpSecurityControlSuccess

message is not received after the

msgCpdcpSecurityControl message is sent to

the PDCB.

CC - int 0~2147483647

130 c_ECC_TMOUT_

internalRrcDataTransfer

count The msgCpdcpDataTransferCnf message from

the PDCB is not received during the intra-cell

handover, after sending the RRC Connection

Reconfiguration message to the UE.

CC - int 0~2147483647

131 c_ECC_TMOUT_

internalForwardingPathSetup

count The msgCgtpSetupCnf message is not

received after the msgCgtpSetupReq message

is sent to the GTPB to set the uplink and

downlink path during the handover.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

132 c_ECC_TMOUT_

internalReestablishControl

count The msgCrlcControlSuccess or

msgCpdcpControlSuccess message are not

received after sending the msgCrlcControl or

msgCpdcpControl message to reestablish the

RLC or PDCP during the X2/S1 handover.

CC - int 0~2147483647

133 c_ECC_TMOUT_

internalBufferFlush

count The msgCpdcpBufferFlushCnf message is not

received after the msgCpdcpBufferFlush

message is sent to the PDCB during handover.

CC - int 0~2147483647

134 c_ECC_TMOUT_

internalDataTransferStart

count The msgCpdcpControlSuccess message is not

received after the msgCpdcpControl message

is sent.

CC - int 0~2147483647

135 c_ECC_TMOUT_

internalDataForwardEndInd

count The msgCpdcpControlSuccess message is not

received after sending the msgCpdcpControl

message to the target side PDCB upon the

completion of the X2, S1 Handover to notify the

handover completion.

CC - int 0~2147483647

136 c_ECC_TMOUT_

InternalCmacPhyRestoreInd

count Currently unused. CC - int 0~2147483647

137 c_ECC_ARQ_NO_

ACKNOWLEDGE

count The messages sent to the DCCH cannot be

sent to the UE.

CC - int 0~2147483647

138 c_ECC_USER_INACTIVITY count A User Inactivity notification sent from the

MAC.

CC - int 0~2147483647

139 c_ECC_ARQ_MAX_RE_

TRANSMISSION

count A Max Retransmission notification sent from

the RLC.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

140 c_ECC_RADIO_LINK_

FAILURE

count A Radio Link Fail (RLF) notification sent from

the MAC.

CC - int 0~2147483647

141 c_ECC_UE_CONTEXT_NOT_

FOUND

count The reestablishment requested by the UE

cannot be performed because the UE Context

information could not be found in the eNB.

CC - int 0~2147483647

142 c_ECC_S1AP_SN_STATUS_

NOT_RECEIVED

count The SN Status Transfer message is not

received from the source eNB during handover.

Or, the MME Status Transfer message is

received from the MME.

CC - int 0~2147483647

143 c_ECC_REEST_FAIL_

INVALID_STATE

count A RRC Connection Reestablishment Request

message is received during the attach.

CC - int 0~2147483647

144 c_ECC_CDMA_HANDOVER_

PREPARATION_FAILURE

count Handover preparation to the CDMA system

fails.

CC - int 0~2147483647

145 c_ECC_RCV_S1_

UECTXTRELEASECMD_

ABNORMAL_STATE

count A UE Context Release Command message is

received from the base station when the UE

Context Release Command isn‟t expected to

be issued.

CC - int 0~2147483647

146 c_ECC_RCV_RESET_

REQUEST_FROM_ECMB

count The call is cancelled due to the reception of the

Reset Request message from the ECMB block.

CC - int 0~2147483647

147 c_ECC_RCV_S1_RESET_

FROM_MME

count The call is cancelled due to the reception of the

Reset message from the MME.

CC - int 0~2147483647

148 c_ECC_RCV_X2_

RESETREQUEST

count The call needs to be cancelled due to the

reception of the Reset Request message from

other eNB.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

149 c_ECC_S1_SCTP_OUT_OF_

SERVICE

count The call needs to be cancelled because the

status of S1 Association is Out of Service.

CC - int 0~2147483647

150 c_ECC_RCV_CELL_

RELEASE_IND_FROM_ECMB

count The call needs to be cancelled due to the

reception of the Cell Release Ind message

from the ECMB block.

CC - int 0~2147483647

151 c_ECC_DSP_AUDIT_RLC_

CALL_RELEASE

count The call is cancelled due to the resource

mismatch, because the ECCB and the MAC

have remaining calls but the RLC has no call

remaining.

CC - int 0~2147483647

152 c_ECC_DSP_AUDIT_MAC_

CALL_RELEASE


mismatch, because the ECCB and the RLC

have remaining calls but the MAC has no call

remaining.

CC - int 0~2147483647

153 c_ECC_DSP_AUDIT_RLC_

MAC_CALL_RELEASE


mismatch, because the ECCB has remaining

calls but the RLC and the MAC have no call

remaining.

CC - int 0~2147483647

154 c_ECC_SEC_ALGORITHMS_

COMBINATION_INVALID

count The Security Algorithm value within the Initial

Context Setup Request, S1 Handover

Request, X2 Handover Request or S1 UE

Context Modification message is received.

If the integrity algorithm supports Null

Algorithm, the ciphering algorithm must also

receive the Null Algorithm value. Otherwise,

the call is cancelled.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

155 c_ECC_X2_SCTP_OUT_OF_

SERVICE

count The call needs to be cancelled because the

status of X2 Association is Out of Service.

CC - int 0~2147483647

156 c_ECC_C_ECCB_RELEASE_

DUE_TO_ENB_GENERATED_

REASON

count The call is cancelled due to the internal cause

of the base station.

CC - int 0~2147483647

157 c_RRM_INIT_MODULE_FAIL count The DB initialization procedure managed by

the ERRM fails.

CC - int 0~2147483647

158 c_RRM_PLD_DATA_ERROR count The ERRM DB resources are not secured or

the resources cannot be assigned due to PLD

data error.

CC - int 0~2147483647

159 c_RRM_VALUE_INVALID count The formula was called with an invalid

parameter.

CC - int 0~2147483647

160 c_RRM_MSGID_INVALID count The MME Overload Control is disabled during

the procedure for messages other than RRC

Connection Request and RRC Connection

Setup Complete.

CC - int 0~2147483647

161 c_RRM_CELL_BARRED count If calls are generated by the cell being barred

by the operator, they are rejected by CAC.

CC - int 0~2147483647

162 c_RRM_MAX_CALL_COUNT_

OVER

count If calls are generated for more than the number

of calls that can be accommodated by the cell,

they are rejected by CAC.

CC - int 0~2147483647

163 c_RRM_MAX_DRB_COUNT_

OVER

count If calls are generated for more than the number

of DRB that can be accommodated by the cell,

they are rejected by CAC.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

164 c_RRM_QOSCAC_FAIL count If calls with the QoS that cannot be

accommodated by the cell are generated, they

are rejected by CAC.

CC - int 0~2147483647

165 c_RRM_PREEMPTION_FAIL count Preemption fails because the requested

ERAB‟s priority is under the priority of the

existing UE.

CC - int 0~2147483647

166 c_RRM_DRB_PREEMPTION_

POOL_ABNORMAL

count In Cell, the internal DB is abnormal for

Preemption.

CC - int 0~2147483647

167 c_RRM_RBID_FULL count When the DRB is generated exceeding the

MAX_DRB or MAX_LOGH per call, the DRB ID

and LOGH ID cannot be assigned.

CC - int 0~2147483647

168 c_RRM_BHCAC_FAIL count Occurs when the BH link usage by the specific

QoS (GBR Bearer) exceeds the threshold

defined in the PLD.

CC - int 0~2147483647

169 c_RRM_CALLID_DB_FULL count Call ID is all assigned thus cannot assign Call ID

further.

CC - int 0~2147483647

170 c_RRM_CALLID_DB_

ABNORMAL

count Call ID cannot be assigned because the DB

managing the Call ID is abnormal.

CC - int 0~2147483647

171 c_RRM_CALLID_NOT_

ASSIGNED

count The requested Call ID cannot be found when

requesting Call ID cancellation.

CC - int 0~2147483647

172 c_RRM_SRS_MUST_BE_

ASSIGNED

count If a new call supports both SRS and DRX, the

SRS resources need to assigned in advance to

assign the DRX resources but the DRX

resources cannot be assigned because the

SRS resource is not assigned.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

173 c_RRM_CQIPMI_PERIOD_

INVALID

count Because CQI/PMI period is Invalid, CQIPMI

internal DB cannot be initialized.

CC - int 0~2147483647

174 c_RRM_RI_MRI_INVALID count Because riConfigMri index is Invalid, CQIPMI

internal DB cannot be initialized.

CC - int 0~2147483647

175 c_RRM_CQIPMI_DB_

ABNORMAL

count Because CQI/PMI internal DB is abnormal,

cannot assign CQI/PMI resource to new calls.

CC - int 0~2147483647

176 c_RRM_CQIPMI_DB_FULL count CQI/PMI resources are all assigned and

cannot be assigned further.

CC - int 0~2147483647

177 c_RRM_CQIPMI_RESOURCE

_

NOT_ASSIGNED

count Cannot cancel the resource because there is

no resource assigned to the CQI/PMI DB.

CC - int 0~2147483647

178 c_RRM_CQIPMI_DB_

INSUFFICIENT

count Cannot initialize because the capacity of

CQI/PMI internal DB is too small.

CC - int 0~2147483647

179 c_RRM_SPS_DB_ABNORMAL count During SPS resource assignment and

cancellation, the SPS resource search is not

allowed to exceed the Max value of the SPS

resource DB.

CC - int 0~2147483647

180 c_RRM_SPS_DB_FULL count SPS resources are all assigned and cannot be

assigned further.

CC - int 0~2147483647

181 c_RRM_SPS_ALREADY_

ASSIGNED

count Assigning duplicate resources is not allowed

since the SPS resources are already assigned.

CC - int 0~2147483647

182 c_RRM_SPS_RNTI_FULL count Cannot assign further since the RNTI used for

SPS is all assigned.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

183 c_RRM_N1PUCCHAN_REP_

DB_ABNORMAL

count n1PucchAnRep resources are all assigned and

cannot be assigned further.

CC - int 0~2147483647

184 c_RRM_N1PUCCHAN_REP_

ALREADY_ASSIGNED

count Since there are already assigned resources

regarding the N1PUCCHAN_REP on the call, it

is not assigned.

CC - int 0~2147483647

185 c_RRM_MCCE_CONFIG_

INVALID

count Because the system resources are not

provided to MCCE configuration table, the

resource DB cannot be initialized.

CC - int 0~2147483647

186 c_RRM_N1PUCCH_DB_

INSUFFICIENT

count Cannot initialize because the capacity of

N1PUCCH internal resource DB is too small.

CC - int 0~2147483647

187 c_RRM_SR_DB_ABNORMAL count During SR resource assignment and

cancellation, the SR resource search is not

allowed to exceed the Max value of the SR

resource DB.

CC - int 0~2147483647

188 c_RRM_SR_DB_FULL count SR resources are all assigned and cannot be

assigned further.

CC - int 0~2147483647

189 c_RRM_SR_ALREADY_

ASSIGNED


regarding the SR on the call, it is not assigned.

CC - int 0~2147483647

190 c_RRM_SR_PERIOD_INVALID count Cannot initialize the resource DB because the

system‟s SR period and srConfgIndex Table

value do not match.

CC - int 0~2147483647

191 c_RRM_SRS_BW_

CONFIGURATION_INVALID

count SRS BW configuration value exceeds the Max

configuration index.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

192 c_RRM_SRS_CH_

BANDWIDTH_INVALID

count SRS Bandwidth does not exist in SRS

Bandwidth defined in Spec.

CC - int 0~2147483647

193 c_RRM_SRS_UE_PERIOD_

INVALID

count The UE Period value for the SRS resource

allocation and deallocation is invalid.

CC - int 0~2147483647

194 c_RRM_SRS_DB_ABNORMAL count The SRS resource DB search exceeds the

secured resource range in SRS resource

assignment and cancellation.

CC - int 0~2147483647

195 c_RRM_SRS_DB_FULL count SRS resources are all assigned. CC - int 0~2147483647

196 c_RRM_SRS_ALREADY_

ASSIGNED


regarding the SRS on the call, it is not

assigned.

CC - int 0~2147483647

197 c_RRM_TPC_PUCCH_RNTI_

DB_ABNORMAL

count During TPC PUCCH RNTI resource

assignment and cancellation, the TPC PUCCH

resource search is not allowed to exceed the

Max value of the TPC PUCCH resource DB.

CC - int 0~2147483647


FULL

count TPC PUCCH RNTI resources are all assigned

and not available anymore.

CC - int 0~2147483647


ALREADY_ASSIGNED


since the TPC PUCCH resources are already

assigned.

CC - int 0~2147483647


INDEX_INVALID

count When canceling the TPC PUSCH resources,

cannot cancel the resources because the TPC

PUCCH resource value of the call is invalid.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

201 c_RRM_SPS_MUST_BE_

ASSIGNED

count SPS resources which should be assigned prior

to the TPC PUSCH resource assignment are

not assigned.

CC - int 0~2147483647

202 c_RRM_TPC_PUSCH_RNTI_

FULL

count RNTIs used for the TPC PUSCH purpose are

all assigned and not available any more.

CC - int 0~2147483647


INDEX_INVALID

count When canceling the TPC PUSCH resources,

cannot cancel the resources because the TPC

PUSCH resource value of the call is invalid.

CC - int 0~2147483647


ALREADY_ASSIGNED


since the TPC PUSCH resources are already

assigned.

CC - int 0~2147483647


DB_ABNORMAL

count When canceling TPC PUSCH resources,

cannot cancel the resources because the

internal DB Index value is not correct.

CC - int 0~2147483647

206 c_RRM_ALL_MME_NOT_

SERVICE

count The call is rejected because there exists no

MME currently in connection.

CC - int 0~2147483647

207 c_RRM_MME_OVERLOAD count When the MME is in Overload status, the calls

cannot be accommodated because

overloadAction and establishmetCause do not

match.

CC - int 0~2147483647

208 c_RRM_NOT_EXIST_MME count In MME Pool, a specific MME ID does not

exist.

CC - int 0~2147483647

209 c_RRM_AVAILABLE_MME_

NOT_EXIST

count The MME to accommodate new calls does not

exist.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

210 c_RRM_UE_STMSI_

DUPLICATE

count The same UE transmits the RRC Connection

Request with the same S-TMSI value.

CC - int 0~2147483647

211 c_GTP_Setup_Failure count Response for the Gtp setup failure is

generated after receiving the SetupReq


CC - int 0~2147483647

212 c_GTP_Release_Failure count Response for Gtp release failure is generated

after receiving the ReleaseReq message from

the ECCB.

CC - int 0~2147483647

213 c_GTP_Modify_Failure count Response for the Gtp modify failure is

generated after receiving the ModifyReq


CC - int 0~2147483647

214 c_GTP_Reset_Failure count Response for Gtp reset failure is generated

after receiving the Reset message from the

ECMB.

CC - int 0~2147483647

215 c_GTP_Path_Failure count After the SetupReq message is received from

the ECCB, a series of the GTP setup starts:

create a GTP tunnel, set a timer to the echo

request message to be sent to the dstip of the

message, and respond to the ECCB if a

response is not received three times within the

time limit.

CC - int 0~2147483647

216 c_GTP_Not_Support_EH count A response is sent when the message received

from the dst peer during the tunnel setup has

an extension header not supportable by the

system.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

217 c_GTP_GTP_Error_Ind count A response is sent to cancel the call by

responding to the ECCB when receiving an

Error Indication message from the dst peer.

CC - int 0~2147483647

218 c_PDCP_Invalid_Callid count An invalid message response is sent when the

call ID of the message downloaded from the

ECCB is above MAX_USER_ENB.

CC - int 0~2147483647

219 c_PDCP_Invalid_RBid count A response is sent to notify that the message

downloaded from the ECCB is valid if the

message is PDCP_DRB or PDCP_SRB and

the Rbid is below MAX_RB or MAX_SRB

respectively. Otherwise, an invalid message

response is sent.

CC - int 0~2147483647

220 c_PDCP_Invalid_NumRb count The NumRb of the message downloaded

from the ECCB is above the value of

CI_MAX_RB.

CC - int 0~2147483647

221 c_PDCP_Invalid_RlcMode count The RLC Mode of the message downloaded

from the ECCB is inappropriate.

CC - int 0~2147483647

222 c_PDCP_Invalid_SetupType count The setupType of the message downloaded

form the ECCB is inappropriate.

CC - int 0~2147483647

223 c_PDCP_Invalid_CntlType count The CntlType of the message downloaded

from the ECCB is inappropriate.

CC - int 0~2147483647

224 c_PDCP_Invalid_PdcpSnType count The SNType of the message downloaded from

the ECCB is UM, but not 7-bit or 12-bit.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

225 c_PDCP_Invalid_LochType count The logical type of the message downloaded

from the ECCB is other than LOCH_DCCH or

LOCH_DTCH for SRB or DRB respectively.

CC - int 0~2147483647

226 c_PDCP_Rohc_Setup_Failure count The ROHC context setup procedure fails due

to lack of memory while receiving ConfigReq

from the ECCB.

CC - int 0~2147483647

227 c_PDCP_Inactive_RBid count The Inactive RB message is received while

receiving the msgCpdcpModifyReq from the

ECCB.

CC - int 0~2147483647

228 c_PDCP_SRB_Integrity_Failure count A SRB‟s integrity check failure notification is

issued from the PDCB.

CC - int 0~2147483647

229 c_RLC_ECCB_INVALID_

CELLNUM

count The cell number of the message received from

the ECCB is greater than the maximum cell

number defined.

CC - int 0~2147483647

230 c_RLC_ECCB_CELL_IS_IDLE count The status of the cell ID of the message

received from the ECCB is IDLE, not ACTIVE.

CC - int 0~2147483647


CALL_ID

count The call ID of the message received from the

ECCB is not within the defined range.

CC - int 0~2147483647

232 c_RLC_ECCB_NUMRB_ZERO count The number of RBs in the message received

from the ECCB is „0‟.

CC - int 0~2147483647

233 c_RLC_ECCB_NUMRB_

OVER_MAXRB

count The number of RBs in the message received

from the ECCB is greater than the maximum

value defined.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

234 c_RLC_ECCB_INVALID_T_

POLL

count The poll retransmit timer value of the message

received from the ECCB is greater than the

maximum value defined.

CC - int 0~2147483647


POLL_PDU

count The poll pdu value of the message received


value defined.

CC - int 0~2147483647


POLL_BYTE

count The poll byte value of the message received


value defined.

CC - int 0~2147483647

237 c_RLC_ECCB_INVALID_MAX_

RETX

count The max Retx value of the message received


value defined.

CC - int 0~2147483647

238 c_RLC_ECCB_INVALID_SN_

LENGTH

count The sn Length value of the message received


value defined.

CC - int 0~2147483647

239 c_RLC_ECCB_IVALID_NUM_

RB_UNMATCH

count There is no mapping value for the RB value of

the message received from the ECCB.

CC - int 0~2147483647

240 c_RLC_ECCB_CALL_IS_NOT_

ACTIVE

count The status of the call ID of the message

received from the ECCB is not ACTIVE.

CC - int 0~2147483647


CELLCALL_ID

count The „cell call ID‟ in the message received from

the ECCB is outside the defined range.

CC - int 0~2147483647


DELETE_FLAG

count The „delete flag‟ in the message received from


CC - int 0~2147483647


DELETE_NUMCALL

count The „delete numcall‟ in the message received

from the ECCB is outside the defined range.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit


T_REORDER

count The „T reorder‟ in the message received from


CC - int 0~2147483647


T_STATUS_PROHIBIT

count The „T status prohibit‟ in the message received


CC - int 0~2147483647


PCCH_CFG_T

count The „pcch cfg T‟ in the message received from


CC - int 0~2147483647


PCCH_CFG_MOD_PERIOD_

COEFF

count The „pcch cfg mode period coefficient‟ in the

message received from the ECCB is outside

the defined range.

CC - int 0~2147483647


PCCH_CFG_NB

count The „pcch cfg nB‟ in the message received


CC - int 0~2147483647

249 c_RLC_ECCB_LACK_OF_

NUMOFRB

count New connections are not allowed due to

insufficient RBs that can be allocated to the


CC - int 0~2147483647

250 c_RLC_ECCB_DL_LACK_OF_

AMDWINDOW_POOL

count New connections are not allowed due to

insufficient AMD window pools that can be

allocated to the message received from the

ECCB.

CC - int 0~2147483647

251 c_RLC_ECCB_INVALID_QCI_

VALUE

count The „qci‟ in the message received from the

ECCB is outside the defined range.

CC - int 0~2147483647

252 c_RLC_ECCB_INVALID_RLC_

MODE

count The „rlc mode‟ in the message received from


CC - int 0~2147483647

253 c_RLC_ECCB_UL_NO_

MORE_WIN_TAG_POOL

count There are not enough window tag pools that

can be allocated to the message received from

the ECCB.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit


LOCH_TYPE

count The „loch type‟ in the message received from


CC - int 0~2147483647


CONTROL_TYPE

count The „control type‟ in the message received


CC - int 0~2147483647

256 c_RLC_ECCB_INVALID_NUM_

CALL

count The „num Call‟ in the message received from


CC - int 0~2147483647


CALLID_UNMATCH

count The „cell Call Id‟ and „CallID‟ in the message

received from the ECCB do not match.

CC - int 0~2147483647


POLL_RETX

count The error code is sent when the

tPollRetransmit timer value within the Config

Request (i.e. the call setup message) that the

RLC received from the ECCB is incorrect.

CC - int 0~2147483647

259 c_RLC_ECCB_NOT_

EQUIPPED_QCI

count The „qci‟ in the message received from the

ECCB is not in „equip‟ status.

CC - int 0~2147483647

260 c_RLC_ECCB_UL_NO_

MORE_CALL_POLL

count There are not enough call pools that can be

allocated to the message received from the

ECCB.

CC - int 0~2147483647

261 c_RLC_ERROR_EMPTY_MSG count The error code is sent when the message

received from the RLC is NULL.

CC - int 0~2147483647

262 c_RLC_ERROR_UNKNOWN_

MSG_ID

count The error code is sent when the message

received from the RLC contains an unknown

message ID.

CC - int 0~2147483647

263 c_RLC_ERROR_INVALID_

DATA_LEN

count The error code is sent when the size of the

message received from the RLC is incorrect.

CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

264 c_RLC_ERROR_NO_RSP_

FROM_DL

count The error code is sent when the response

message is not received from the RLC

downlink.

CC - int 0~2147483647


FROM_UL


message is not received from the RLC uplink.

CC - int 0~2147483647


FROM_DLUL


message is not received from the RLC

downlink and uplink.

CC - int 0~2147483647

267 c_RLC_ERROR_RX_BEFORE

_

RLC_READY

count The error code is sent when a signaling

message is received before the RLC uplink is

properly started.

CC - int 0~2147483647

268 c_RLC_ERROR_INVALID_RLC

_

TRANSACTION_ID

count The error code is sent when the transaction ID

exceeds the specified range while the RLC

processes the message received from the

ECCB and ECMB.

CC - int 0~2147483647


CONTEXT

count The error code is sent when a reply for the

signaling message already processed by the

RLC is received from the RLC downlink.

CC - int 0~2147483647

270 c_RLC_ERROR_RLC_

CONTEXT_FULL

count The error code is sent when the number of

signaling message received exceeds the RLC

capacity.

CC - int 0~2147483647


CELLNUM

count The error code is sent if the RLC cannot

process the cell num.

CC - int 0~2147483647

272 c_MAC_INVALID_MSGID count An undefined Msg ID is received. CC - int 0~2147483647



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit

273 c_MAC_INVALID_SETUPTYPE count An undefined SetupType is received. CC - int 0~2147483647

274 c_MAC_INVALID_CALL_CELLID count The call cell ID of the message received from

the ECCB is not within the defined range.

CC - int 0~2147483647

275 c_MAC_INVALID_PARAMETER count The received parameter is outside the allowed

range.

CC - int 0~2147483647

276 c_MAC_INSUFFICIENT_

RESOURCE

count The RB cannot be allocated due to the

insufficient MACB internal resource required

to manage the RB.

CC - int 0~2147483647

277 c_MAC_NOT_ASSIGNED_RB count A reconfig/delete request for an unallocated

RB is received.

CC - int 0~2147483647

278 c_MAC_NOT_ASSIGNED_UE count A config/delete request for an unallocated UE

is received.

CC - int 0~2147483647

279 c_MAC_NOT_ASSIGN_SRB1 count The call setup message received does not

have the SRB1 setup.

CC - int 0~2147483647

280 c_MAC_INVALID_RB_CONFIG count The „RB num‟ in the logical channel config

exceeds the maximum value.

CC - int 0~2147483647

281 c_MAC_INVALID_CELL_ID count The cell corresponding to the message

received is idle.

CC - int 0~2147483647



10.3.8 MRO_RLF

The Mobility Robustness Optimization (MRO) statistics function collects the handover problems due to the Radio Link Failure (RLF) occurring

during or after the handover, organizes them by type, then applies the data to the MRO algorithm to optimize the handover parameter (e.g. Cell

Individual Offset) and improve the handover performance.

MRO RLF Classification

The causes of the handover related RLF recorded as MRO issue are: too-late handover, too-early handover, and handover to a wrong cell.

The causes of RLF not recorded as MRO issue are recorded as coverage hole.

MRO

The purpose of the Mobility Robustness Optimization (MRO) is to set the handover related parameters automatically during the system

operation to enhance the handover performance.

[Index]



Neighbor Cell 0~268435455 Neighbor Cell Index




[Statistics Type]



Lower/Upper

Limit

1 CoverageHole count The number of RLF/HO

failures due to the

coverage hole

CC The RRC re-establishment is performed to

the serving cell while the UE is not in

handover.

The coverage hole cannot be resolved with

the handover parameter, and requires the

coverage to be modified.

int 0~2147483647

2 CoverageHoleN count The number of RLF/HO

failures due to the

coverage hole toward

Cell N

CC The RRC re-establishment is performed to

a neighbor cell (N) other than the serving

cell while the UE is not in handover. Or the

coverage hole (neighbor) cannot be

resolved with the handover parameter, and

requires the coverage to be modified.

int 0~2147483647

3 TooEarlyHOFailure count The number of too-early

handovers after sending

the handover command

CC The UE received the HO Command

message from the serving cell and

performed the handover to the target cell,

but failed due to the T304 timer expiration,

then the re-establishment was performed

back to the serving cell.

int 0~2147483647

4 TooEarlyHORLFAfterHO count The number of too-early

handovers after

completing the handover

process

CC The UE completed the handover from the

serving cell to the target cell successfully,

then a RLF occurred and the re-

establishment was performed back to the

serving cell.

int 0~2147483647



(Continued)



Lower/Upper

Limit

5 TooLateHORLFBeforeTriggering count The number of RLFs

before triggering the

handover

CC A RLF occurred when the serving cell did

not receive the MR message including the

A3 event of the neighbor cell from the UE,

and the re-establishment to the neighbor

cell was performed.

int 0~2147483647

6 TooLateHORLFAfterTriggering count The number of RLFs

after sending the

handover command

CC The serving cell received the MR message

including the A3 event of the neighbor cell

from the UE, then a RLF occurred before

the UE initiated the handover and the re-

establishment to the corresponding

neighbor cell was performed.

int 0~2147483647

7 WrongCellRLFAfterTriggering count The number of

handovers to a wrong

cell before sending the

handover command

CC The serving cell received the MR message

including the A3 event of the neighbor cell

from the UE, then a RLF occurred before

the UE initiated the handover and the re-

establishment was performed to a cell

other than the target cell in which the A3

event was triggered.

int 0~2147483647

8 WrongCellRLFAfterHO count The number of

handovers to a wrong

cell after sending the

handover command.

CC The UE completed the handover from the

serving cell to the target cell successfully,

then a RLF occurred and the re-

establishment was performed to a cell

other than either the serving cell or the

target cell.

int 0~2147483647



10.3.9 GTP

The GPRS Tunneling Protocol Block (GTPB) provides the GPRS Tunneling Protocol function for the data connection in S1-U or X2-U, as well as

the functions to manage the GTP tunnel for the E-RAB and send/receive the user data. This function provides the statistics of the GTP layer packet

received from the S1-U (S-GW) in the DL to assist the operator to detect the backhaul state.

GTP Sequence Number by QCI

The eNB collects the statistics data of the lost downlink packets count and the Out of Sequence downlink packets count in the GTP layer for each

QCI.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 GtpSnPeakLossQci count Count of downlink GTP packets which have

been regarded to be lost until the statistics

collection time.

CC The packets are lost for a

given amount of time

(Measurement Period).

int 0~2147483647

2 GtpSnOosQci count Count of Out of Sequence downlink packets

for each QCI. That is, the accumulated count

of the packets whose GTP sequence numbers

were changed for each QCI.

CC The sequence numbers of

packets are reversed for a



int 0~2147483647



GTP Sequence Number by eNB

The eNB collects the statistics data for the count of lost downlink packets and the count of Out of Sequence downlink packets in the GTP layer for

the eNB.

[Index]

NONE.

[Statistics Type]



Lower/Upper

Limit

1 GtpSnPeakLossEnb count Count of downlink GTP packets assumed as

lost until the statistics collection time.

CC The packets are lost for a given

amount of time (Measurement

Period).

int 0~2147483647

2 GtpSnOosEnb count Count of Out of Sequence downlink packets

for each QCI. That is, the accumulated count

of the packets whose GTP sequence numbers

were changed.

CC The sequence numbers of

packets are reversed for a given

amount of time (Measurement

Period).

int 0~2147483647

3 GtpDlCntEnb count Count of downlink GTP packets received until

the statistics collection time.

CC The packets are received for a



int 0~2147483647

4 GtpSnLossEnbRate % Percentage of packets assumed as lost in the

total downlink GTP packets until the statistics

collection time.

* loss packet = GtpSnPeakLossEnb

* total packet = GtpDlCntEnb + (GtpDlCntEnb-

GtpSnOosEnb)

OW GtpSnPeakLossEnb/sum

(GtpDlCntEnb +

GtpSnPeakLossEnb-

GtpSnOosEnb) * 100

int 0~100



(Continued)



Lower/Upper

Limit

5 GtpSnOosEnbRate % Percentage of Out of Sequence packets in the

total downlink GTP packets until the statistics

collection time.

* Out of Sequence Packet = GtpSnOosEnb

* total packet = GtpDlCntEnb +

(GtpSnPeakLossEnb-GtpSnOosEnb)

OW GtpSnOosEnb/(GtpDlCntEnb +

GtpSnPeakLossEnb-

GtpSnOosEnb)* 100

int 0~100

GTP Forward Traffic

The GTP Forward Traffic, provided in statistics, is defined using the DL/UL Count/Byte/

Throughput for the forwarding traffic in the basic call, S1/X2 HO or Inter-RAT S1/X2 HO.


The PM measures the GTP Forward Traffic every 20 seconds. These samples measured every 20 seconds are used to calculate the following

statistics.

[Index]

NONE.



[Statistics Type]



Lower/Upper

Limit

1 CntGtpDlEnbS1Nor count Number of S1 downlink GTP packets

in basic call

CC There are S1 downlink GTP

packets in basic call.

int 0~2147483647

2 CntGtpUlEnbS1Nor count Number of S1 uplink GTP packets in

basic call

CC There are S1 uplink GTP

packets in basic call

int 0~2147483647

3 CntGtpDlEnbS1FW count Number of forwarding packets

received at S1 DL in S1 Handover

CC There are forwarding packets

received at S1 DL in S1

Handover

int 0~2147483647

4 CntGtpUlEnbS1FW count Number of packets forwarded to S1

UL in S1 Handover

CC There are packets forwarded

to S1 UL in S1 Handover

int 0~2147483647

5 CntGtpDlEnbX2FW count Number of forwarding packets

received at X2 DL in X2 Handover


received at X2 DL in X2

Handover

int 0~2147483647

6 CntGtpUlEnbX2FW count Number of packets forwarded to X2

UL in X2 Handover


to X2 UL in X2 Handover

int 0~2147483647

7 CntGtpDlEnbIRatUtraS1FW count Number of forwarding packets

received at S1 DL in Inter-RAT

(UTRAN) Handover


received at S1 DL in Inter-

RAT (UTRAN) Handover

int 0~2147483647

8 CntGtpUlEnbIRatUtraS1FW count Number of packets forwarded to S1

UL in Inter-RAT (UTRAN) Handover


to S1 UL in Inter-RAT

(UTRAN) Handover

int 0~2147483647

9 CntGtpDlEnbIRatUtraX2FW count Number of forwarding packets

received at X2 DL in Inter-RAT

(UTRAN) Handover


received at X2 DL in Inter-


int 0~2147483647



(Continued)



Lower/Upper

Limit

10 CntGtpUlEnbIRatUtraX2FW count Number of packets forwarded

to X2 UL in Inter-RAT (UTRAN)

Handover


to X2 UL in Inter-RAT

(UTRAN) Handover

int 0~2147483647

11 CntGtpDlEnbIRatGeranS1FW count Number of forwarding packets


(GERAN) Handover



RAT (GERAN) Handover

int 0~2147483647

12 CntGtpUlEnbIRatGeranS1FW count Number of packets forwarded

to S1 UL in Inter-RAT (GERAN)

Handover


to S1 DL in Inter-RAT

(GERAN) Handover

int 0~2147483647

13 CntGtpDlEnbIRatGeranX2FW count Number of forwarding packets


(GERAN) Handover




int 0~2147483647

14 CntGtpUlEnbIRatGeranX2FW count Number of packets forwarded

to X2 UL in Inter-RAT (GERAN)

Handover



(GERAN) Handover

int 0~2147483647

15 CntGtpDlEnbIRatCdma2000HrpdS1FW count Number of forwarding packets


(CDMA2000 HRPD) Handover



RAT (CDMA2000 HRPD)

Handover

int 0~2147483647

16 CntGtpUlEnbIRatCdma2000HrpdS1FW count Number of packets forwarded





(CDMA2000 HRPD)

Handover

int 0~2147483647



(Continued)



Lower/Upper

Limit

17 CntGtpDlEnbIRatCdma2000HrpdX2FW count Number of forwarding packets


RAT (CDMA2000 HRPD)

Handover

CC There are forwarding

packets received at X2 DL

in Inter-RAT (CDMA2000

HRPD) Handover

int 0~2147483647

18 CntGtpUlEnbIRatCdma2000HrpdX2FW count Number of packets forwarded


(CDMA2000 HRPD)

Handover

CC There are packets

forwarded to X2 UL in

Inter-RAT (CDMA2000

HRPD) Handover

int 0~2147483647

19 ByteGtpDlEnbS1Nor byte

count

Number of bytes of S1

downlink GTP packets in

basic call

CC There are S1 downlink

GTP packets in basic call

int 0~2147483647

20 ByteGtpUlEnbS1Nor byte

count

Number of bytes of S1 uplink

GTP packets in basic call

CC There are S1 uplink GTP


int 0~2147483647

21 ByteGtpDlEnbS1FW byte

count

Number of bytes of the

forwarding packets received

at S1 DL in S1 Handover


packets received at S1 DL

in S1 Handover

int 0~2147483647

22 ByteGtpUlEnbS1FW byte

count


packets forwarded to S1 UL

in S1 Handover

CC There are packets

forwarded to S1 UL in S1

Handover

int 0~2147483647

23 ByteGtpDlEnbX2FW byte

count


forwarding packets received

at X2 DL in X2 Handover


packets received at X2 DL

in X2 Handover

int 0~2147483647



(Continued)



Lower/Upper

Limit

24 ByteGtpUlEnbX2FW byte

count

Number of bytes of the packets

forwarded to X2 UL in X2

Handover



int 0~2147483647

25 ByteGtpDlEnbIRatUtraS1FW byte

count

Number of bytes of the forwarding

packets received at S1 DL in Inter-




(UTRAN) Handover

int 0~2147483647

26 ByteGtpUlEnbIRatUtraS1FW byte

count


forwarded to S1 UL in Inter-RAT

(UTRAN) Handover



(UTRAN) Handover

int 0~2147483647

27 ByteGtpDlEnbIRatUtraX2FW byte

count


packets received at X2 DL in Inter-




(UTRAN) Handover

int 0~2147483647

28 ByteGtpUlEnbIRatUtraX2FW byte

count


forwarded to X2 UL in Inter-RAT

(UTRAN) Handover



(UTRAN) Handover

int 0~2147483647

29 ByteGtpDlEnbIRatGeranS1FW byte

count






(GERAN) Handover

int 0~2147483647

30 ByteGtpUlEnbIRatGeranS1FW byte

count



(GERAN) Handover



(GERAN) Handover

int 0~2147483647

31 ByteGtpDlEnbIRatGeranX2FW byte

count






(GERAN) Handover

int 0~2147483647



(Continued)



Lower/Upper

Limit

32 ByteGtpUlEnbIRatGeranX2FW byte

count



(GERAN) Handover



(GERAN) Handover.

int 0~2147483647

33 ByteGtpDlEnbIRatCdma2000H

rpdS1FW

byte

count



RAT (CDMA2000 HRPD)

Handover




int 0~2147483647

34 ByteGtpUlEnbIRatCdma2000H

rpdS1FW

byte

count







int 0~2147483647

35 ByteGtpDlEnbIRatCdma2000H

rpdX2FW

byte

count



RAT (CDMA2000 HRPD)

Handover




int 0~2147483647

36 ByteGtpUlEnbIRatCdma2000H

rpdX2FW

byte

count







int 0~2147483647

37 ThruGtpDlEnbS1Nor kbps Throughput of S1 downlink GTP


SI There are S1 downlink GTP


float 0~3.4 * 10^38

38 ThruGtpUlEnbS1Nor kbps Throughput of S1 uplink GTP


SI There are S1 uplink GTP


float 0~3.4 * 10^38

39 ThruGtpDlEnbS1FW kbps Throughput of the forwarding

packets received at S1 DL in S1

Handover

SI There are forwarding packets

received at S1 DL in S1

Handover

float 0~3.4 * 10^38



(Continued)



Lower/Upper

Limit

40 ThruGtpUlEnbS1FW kbps Throughput of the forwarding

packets received at S1 UL in S1

Handover

SI There are packets forwarded

to S1 UL in S1 Handover

float 0~3.4*10^38

41 ThruGtpDlEnbX2FW kbps Throughput of the forwarding

packets received at X2 DL in X2

Handover


received at X2 DL in X2

Handover

float 0~3.4 * 10^38

42 ThruGtpUlEnbX2FW kbps Throughput of the forwarding

packets received at X2 UL in X2

Handover



float 0~3.4 * 10^38

43 ThruGtpDlEnbIRatUtraS1FW kbps Throughput of the forwarding





(UTRAN) Handover

float 0~3.4 * 10^38

44 ThruGtpUlEnbIRatUtraS1FW kbps Throughput of the packets


(UTRAN) Handover



(UTRAN) Handover

float 0~3.4 * 10^38

45 ThruGtpDlEnbIRatUtraX2FW kbps Throughput of the forwarding





(UTRAN) Handover

float 0~3.4 * 10^38

46 ThruGtpUlEnbIRatUtraX2FW kbps Throughput of the packets


(UTRAN) Handover



(UTRAN) Handover

float 0~3.4 * 10^38

47 ThruGtpDlEnbIRatGeranS1FW kbps Number of bytes of the forwarding





(GERAN) Handover

float 0~3.4 * 10^38



(Continued)



Lower/Upper

Limit

48 ThruGtpUlEnbIRatGeranS1FW kbps Throughput of the packets


(GERAN) Handover



(GERAN) Handover

float 0~3.4 * 10^38

49 ThruGtpDlEnbIRatGeranX2FW kbps Throughput of the forwarding





(GERAN) Handover

float 0~3.4 * 10^38

50 ThruGtpUlEnbIRatGeranX2FW kbps Throughput of the packets


(GERAN) Handover



(GERAN) Handover

float 0~3.4 * 10^38

51 ThruGtpDlEnbIRatCdma2000H

rpdS1FW

kbps Throughput of the forwarding


RAT (CDMA2000 HRPD)

Handover




float 0~3.4 * 10^38

52 ThruGtpUlEnbIRatCdma2000H

rpdS1FW

kbps Throughput of the packets






float 0~3.4 * 10^38

53 ThruGtpDlEnbIRatCdma2000H

rpdX2FW

kbps Throughput of the forwarding


RAT (CDMA2000 HRPD)

Handover




float 0~3.4 * 10^38

54 ThruGtpUlEnbIRatCdma2000H

rpdX2FW

kbps Throughput of the packets






float 0~3.4 * 10^38



10.3.10 SRB

The eNB provides the Control Plane PDCP SDU Bit-rate for each cell, divided into DL/UL.

Cell PDCP SDU bit-rate

The eNB calculates the average value of the Bit-rate for the Control Plane PDCP SDU at each given period, for each cell, divided into DL and UL,

in accordance with the 3GPP TS32.425 Performance Measurements standard specification.


The PM measures the SRB every two seconds. These samples measured every 2 seconds are used to calculate the following statistics.

[Index]





[Statistics Type]



Lower/Upper

Limit

1 PdcpSduBitrateDl kbps Average cell bit-rate of the

control plane downlink PDCP

SDUs

SI This is calculated as the total bits of Control Plane

PDCP SDU received by the eNB through S1 and

RRC SAP for a given amount of time


Formula: avg (PdcpSduBitrateDl)

float 0~3.4 * 10^38

2 PdcpSduBitrateUl kbps Average cell bit-rate of the

control plane uplink PDCP

SDUs

SI This is calculated as the total bits of Control Plane

PDCP SDU on UL for a given amount of time


Formula: avg (PdcpSduBitrateUl)

float 0~3.4 * 10^38



10.3.11 DRB

The eNB provides the number of Active UE, packet delay, packet drop rate, packet loss rate and IP latency of the DRB for each QCI.

Active UEs

The eNB collects the statistics data for the average number of UEs where the buffer data of the DRB is waiting.


The PM measures the ACTIVE_UE every five seconds. These samples measured every 5 seconds are used to calculate the following statistics.

[Index]






[Statistics Type]


Method

Count Collected

When Type

Lower/Upper

Limit

1 UEActiveDl count The number of UEs satisfying one or more of the following

conditions in a continuous 20 ms interval (sampling occasion)

is summed every 80 ms for each QCI.

- If there is a DRB which received a buffer occupancy request

from the RLC

- If there is a DRB which received an HARQ retransmission

request

When a collection interval ends, the summed number of UEs

is divided by the number of sampling occasions that occurred

to obtain the average.

SI avg (UEActiveDl) float 0~3.4 * 10^38

2 UEActiveDlTot count Total UEActiveDl SI tot (UEActiveDl) float 0~3.4 * 10^38

3 UEActiveUl count The number of UEs satisfying one or more of the following

conditions in a continuous 20 ms interval is summed every 80

ms for each QCI.

- If a DRB exists where the allocation requested Uplink Data

from the Buffer Status Report is on hold.

- If there is a DRB which received an HARQ retransmission

request

When a collection interval ends, the summed number of UEs

is divided by the number of sampling occasions that occurred

to obtain the average.

SI avg (UEActiveUl) float 0~3.4 * 10^38

4 UEActiveUlTot count Total UEActiveUl SI tot (UEActiveUl) float 0~3.4 * 10^38

[Collection Time]

sampling occasion



Packet Delay

Collects the statistics data for the DL PDCP SDU delay defined in the standard 3GPP TS 36.314 for each QCI.


The PM measures the PDCP_DELAY every two seconds. These samples measured every 2 seconds are used to calculate the following

statistics.

[Index]




[Statistics Type]


Method

Count Collected

When Type

Lower/Upper

Limit

1 PdcpSduDelay ms Average DL PDCP SDU delay DL PDCP SDU

delay on the downlink that occurred for 1 minute

SI avg (PdcpSduDelay) float 0~3.4 * 10^38

2 PdcpSduDelayTot ms Total PdcpSduDelay SI tot (PdcpSduDelay) float 0~3.4 * 10^38



Packet Drop Rate

For each eNB, provides the drop rate of the packet for User Plane Traffic which had packet drops on DL, in accordance with the 3GPP TS32.425

Performance Measurement standard specification. The corresponding statistics will be collected for each E-RAB QoS Level (QCI) level.

Such packet drops can occur due to the traffic congestion, and are calculated in ppm by multiplying 1E6 in accordance with the TS 36.314 Layer

2–Measurements standard specification.


The PM measures the PDCP_DROP every 60 seconds. These samples measured every 60 seconds are used to calculate the following

statistics.

[Index]





[Statistics Type]



Lower/Upper

Limit

1 PdcpSduDropRateDl ppm DL PDCP SDU packet drop

rate on the downlink that

occurred for one minute

SI This is the drop rate for the User Plane Traffic

(DTCH), the IP packets (PDCP SDU) dropped on

the DL for a given amount of time (Time Period),

calculated by multiplying 1E6. (Currently, the DL

packet drop occurs upon the control of the flow

with the lower layer, when the PDCP Layer

received the transmission cancel request from the

RLC and the DL packet arrived at the eNB PDCP

Layer is dropped.)

Formula: avg (PdcpSduDropRateDl)

float 0~3.4 * 10^38

2 PdcpPduDropRateDl ppm Average DL PDCP SDU

drop rate DL PDCP SDU

drop rate on the downlink

that occurred for one minute

SI avg (PdcpPduDropRateDl) float 0~100



Packet loss rate

In User Plane Traffic, For PDCP and SDU which receptions in UL were not successful, provides the loss rate for each eNB according to the 3GPP

TS32.425 Performance Measurement standard specification. The corresponding statistics will be collected for each E-RAB QoS Level (QCI).

The result is multiplied by 1E6 and calculated in ppm in accordance to the TS 36.314 Layer 2-Measurements standard specification.


The PM measures the PDCP_LOSS every 60 seconds. These samples measured every 60 seconds are used to calculate the following

statistics.

[Index]





[Statistics Type]



Lower/Upper

Limit

1 PdcpSduLossRateUl ppm UL PDCP SDU packet loss

rate on the uplink that

occurred for 1 minute

SI This is the loss rate for the User Plane Traffic (DTCH),

the IP packets (PDCP SDU) lost on the UL for a given

amount of time (Time Period), which drop rate is

calculated by multiplying 1E6.

(Currently, the UL packet loss is calculated from the

PDCP sequence number that was missed on the

UL.)

Formula: avg (PdcpSduLossRateUl)

float 0~3.4 * 10^38

2 PdcpSduAirIntf ppm Average DL PDCP SDU

loss rate DL PDCP SDU

packet loss rate on the

downlink that occurred for

1 minute

SI avg (PdcpSduAirIntf) float 0~100



IP Latency measurements

The eNB collects the statistics data for the DL IP latency defined in the standard 3GPP TS 32.450 for each QCI.


The PM measures the IP_LATENCY every two seconds. These samples measured every 2 seconds are used to calculate the following

statistics.

[Index]




[Statistics Type]



Lower/Upper

Limit

1 IpLateDl ms IP latency in DL, SAE bearer level

The IP latency on the downlink that

occurred for 1 minute.

SI avg (IpLateDl) float 0~3.4 * 10^38



10.3.12 RRU

The Radio Resource Utilization (RRU) statistics consists of the physical resource block usage statistics for each downlink/uplink QCI, the

downlink‟s/uplink‟s total physical resource block usage statistics, and the cell unavailable time statistics. For the details on each item, refer to the

explanation of the statistics of each item below.

DL/UL PRB Usage

The eNB collects the rate of PRB allocated to the DTCH among the total PRB on the DL/UL for each QCI.


The PM measures the PRB_QCI every five seconds. These five-second samples are used to calculate the following statistics.

[Index]




[Statistics Type]



Lower/Upper

Limit

1 PrbDl % The PRB usage used as the downlink DTCH traffic SI avg (PrbDl) float 0.00~100.00

2 PrbUl % The PRB usage used as the uplink DTCH traffic SI avg (PrbUl) float 0.00~100.00



[Collection Time]

TTI

DL/UL Total PRB Usage

The eNB collects the usage rate (percentage) of the PRB on the downlink PDSCH/PDCCH and the uplink PUSCH among the total PRB.


The PM measures the PRB_TOTALI every five seconds. These five-second samples are used to calculate the following statistics.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 TotPrbDl % The resource used for the PDSCH/PDCCH transmission

among the total downlink resource

GAUGE avg (TotPrbDl) float 0.00~100.00

2 TotGbrPrbDl % The resource used for the GBR traffic transmission


GAUGE sum{PrbDl (GBR QCI)} float 0.00~100.00

3 TotNGbrPrbDl % The resource used for the non-GBR traffic transmission


GAUGE sum{PrbDl (non-GBR QCI)} float 0.00~100.00



(Continued)



Lower/Upper

Limit

4 TotPrbUl % The resource used for the PUSCH transmission among

the total uplink resource

GAUGE avg (TotPrbDl) float 0.00~100.00

5 TotGbrPrbUl % The resource used for the GBR traffic transmission

among the total uplink resource

GAUGE sum{PrbUl (GBR QCI)} float 0.00~100.00

6 TotNGbrPrbUl % The resource used for the non-GBR traffic transmission

among the total uplink resource

GAUGE sum{PrbUl (non-GBR QCI)} float 0.00~100.00

[Collection Time]

TTI



Cell Unavailable Time

Collects the statistics data for the average locked time and disabled time per unit time for each cell.


The PM measures the CELL_UNAVAILABLE every five minutes.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 CellUnavailableTimeLock sec Measures the locked time

for a given amount of time.

CC Collects the time the administrator was

locked for each cell, from the time the lock

was engaged until it was released (unlocked),

in second.

float 0~900

2 CellUnavailableTimeDown sec Measures the disabled

time for a given amount of

time.

CC Collects the time the operational state was

disabled for each cell, from the time the state

was disabled until it was released (enabled), in

second.

float 0~900



10.3.13 S1SIG

The S1 SIG statistics will count as Attempt after sending the Initial UE message, then as Success upon receiving the Initial Context Setup Request

message. If a timeout or an internal error occurs in the steps, it is counted as Fail and the corresponding cause value is recorded.

UE-associated logical S1-connection establishment

The eNB collects the statistics data for S1 Logical Connection Setup for each cell.

[Index]




0: emergency


2: mt_Access

3: mo_Signalling

4: mo_Data

5: relocated



[Statistics Type]



Lower/Upper

Limit

1 S1ConnEstabAtt count The number of attempts for UE

logical S1 connection setup

CC The following occurs: int 0~2147483647

2 S1ConnEstabSucc count The number of successes for

UE logical S1 connection setup

CC The following occurs: int 0~2147483647

3~133 S1ConnEstabFail_S1AP_


S1ConnEstabFail_MAC_Others

count UE Logical S1 Connection

Setup failure count: See


CC The NAS process in the

following figure fails, or an

internal error occurs within

the station.

int 0~2147483647

[Collection Time]

Figure 10.32 S1SIG collection time

eNB UE MME S/GW

RRC_IDLE

RRC_CONNECTED

Initial UE Message


1 Attempt

2 Success




10.3.14 PAG

PAG is a statistics for paging. It collects the number of paging attempts in the RRC and the number of paging messages received in the RLC then

discarded due to the limit in the handling capacity.

The RLC can store up to 1024 paging messages per cell.

Paging Performance

The eNB collects the statistics data for paging. The eNB collects the statistics data for paging attempt, which is made by a paging request from the

MME, for each cell of the base station. Also, collects the number of the discarded paging messages that were not processed by the eNB for each

cell.

The paging for both of system information update and ETWA indication is not included. The eNB, which is an access network, does not collect the

statistics data for the paging responses which are made through NAS signaling.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 DiscardedNbr count Number of paging records

discarded at the eNodeB.

CC A paging message is received while the

RLC paging buffer is full.

int 0~2147483647

2 AttPaging count Number of paging

transmission attempts

CC Occurs as in the following figure . int 0~2147483647



[Collection Time]

Figure 10.33 PAGING collection time

eNB UE MME S/GW

RRC_IDLE

Paging

Paging Request

Paging 1 Attempt



10.3.15 POWER

The Power statistics consists of power statistics and RNTP statistics. For the details on each item, refer to the explanation of the statistics of each

item below.

Power

Collects the average interference over thermal noise for each PRB, the average thermal noise for each cell, the average RSSI for each cell, and the

average RSSI for each antenna.


The PM measures POWER every five seconds. These five-second samples are used to calculate the following statistics.

[Index]





[Statistics Type]



Lower/Upper

Limit

1 InterferencePower dBm Average interference over thermal

noise for each PRB

SI avg (InterferencePower) float -1000.00~

1000.00

2 ThermalNoisePower dBm Average Thermal Noise SI avg (ThermalNoisePower) float -1000.00~

1000.00

3 RssiOverPath dBm Average RSSI for each antenna SI avg (RssiOverPath) float -1000.00~

1000.00

4 RssiPath0 dBm Average RSSI of Antenna #0 SI avg (RssiPath0) float -1000.00~

1000.00

5 RssiPath1 dBm Average RSSI of Antenna #1 SI avg (RssiPath1) float -1000.00~

1000.00

[Collection Time]

TTI



RNTP of own cell

Collects the Relative Narrowband TX Power (RNTP) value for each PRB.


The PM measures RNTP every five seconds. These five-second samples are used to calculate the following statistics.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 RntpOwnCell_PRB0 indicator Rntp of the downlink PRB #0 CC The Rntp of the downlink PRB #0 is collected. float 0.00, 1.00











(Continued)



Lower/Upper

Limit
























(Continued)



Lower/Upper

Limit








[Collection Time]

TTI



10.3.16 Random Access (RA)

The RA statistics consists of Random Access Preamble statistics. For the details on each item, refer to the explanation of the statistics of each item

below.

Random Access Preambles

The eNB collects the high-speed monitoring results and the number of RACH preambles received.

For the High Speed Monitoring, the moving speed of the terminals within the cell is estimated and the terminals which speed is determined as high

is counted. Also, the eNB collects the number of detected Dedicated Preambles, Contention-based Group A Preambles, and Contention-based

Group B Preambles, then collects the average per second of the detected preambles.


The PM measures RA every five seconds. These five-second samples are used to calculate the following statistics.

[Index]





[Statistics Type]



Lower/Upper

Limit

1 HighSpeedMonitoring count The number of UEs which are

monitored for moving speed

CC UE is detected. int 0~2147483647

2 NoofHighSpeed count The number of high speed UEs

which are monitored

CC High speed UE is detected. int 0~2147483647

3 DedicatedPreambles count The number of detected dedicated

preambles

CC Dedicated preamble is

detected.

int 0~2147483647

4 DedicatedPreamblesAssignFail count The number of failures to get

dedicated preamble allocation after

requesting the dedicated preamble

from the RRC to the MAC

CC The dedicated preamble

allocation in the target

eNB‟s MAC function fails

during the handover.

int 0~2147483647

5 RandomlyselectedpreamblesLow count The number of the preambles

belonging to Group A among the

detected contention based

preambles

CC The preamble belonging to

Group A among the

contention based

preambles is detected.

int 0~2147483647

6 RandomlyselectedpreamblesHigh count The number of the preambles

belonging to Group B among the

detected contention based

preambles

CC The preamble belonging to

Group B among the

contention based

preambles is detected.

int 0~2147483647

7 RACHUsage count/

sec

Average number of detected

preambles

SI avg (RACHUsage) int 0~2147483647

[Collection Time]

Other items except for the Dedicated Preambles AssignFail are collected upon TTI.



10.3.17 HARQ status

The HARQ status statistics consists of downlink/uplink transmission statistics. For the details on each item, refer to the explanation of the statistics

of each item below.

DL/UL transmission

The eNB collects the number of transmissions/receptions and the Block Error Rate (BLER) information for each HARQ transmission for

PDSCH/PUSCH.


The PM measures TRANSMISSION every five seconds. These five-second samples are used to calculate the following statistics.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 DlResidualBLER_Retrans0 % PDSCH BLER for the initial HARQ

transmission

SI avg (DlResidualBLER_Retrans0) float 0.00~100.00

2 DlResidualBLER_Retrans1 % PDSCH BLER for the first HARQ

retransmission




(Continued)



Lower/Upper

Limit

3 DlResidualBLER_Retrans2 % PDSCH BLER for the second HARQ

retransmission


4 DlResidualBLER_Retrans3 % PDSCH BLER for the third HARQ

retransmission


5 UlResidualBLER_Retrans0 % PUSCH BLER for the initial HARQ

retransmission

SI avg (UlResidualBLER_Retrans0) float 0.00~100.00

6 UlResidualBLER_Retrans1 % PUSCH BLER for the first HARQ

retransmission


7 UlResidualBLER_Retrans2 % PUSCH BLER for the second HARQ

retransmission


8 UlResidualBLER_Retrans3 % PUSCH BLER for the third HARQ

retransmission


9 UlResidualBLER_Retrans4 % PUSCH BLER for the fourth HARQ

retransmission


10 UlResidualBLER_Retrans5 % PUSCH BLER for the fifth HARQ

retransmission


11 UlResidualBLER_Retrans6 % PUSCH BLER for the sixth HARQ

retransmission


12 UlResidualBLER_Retrans7 % PUSCH BLER for the seventh HARQ

retransmission


13 UlResidualBLER_Retrans8 % PUSCH BLER for the eighth HARQ

retransmission


14 UlResidualBLER_Retrans9 % PUSCH BLER for the ninth HARQ

retransmission




(Continued)



Lower/Upper

Limit

15 UlResidualBLER_Retrans10 % PUSCH BLER for the tenth HARQ

retransmission


16 UlResidualBLER_Retrans11 % PUSCH BLER for the eleventh HARQ

retransmission


17 UlResidualBLER_Retrans12 % PUSCH BLER for the twelfth HARQ

retransmission


18 UlResidualBLER_Retrans13 % PUSCH BLER for the thirteenth

HARQ retransmission


19 UlResidualBLER_Retrans14 % PUSCH BLER for the fourteenth

HARQ retransmission


20 UlResidualBLER_Retrans15 % PUSCH BLER for the fifteenth HARQ

retransmission


21 UlResidualBLER_Retrans16 % PUSCH BLER for the sixteenth HARQ

retransmission


22 UlResidualBLER_Retrans17 % PUSCH BLER for the seventeenth

HARQ retransmission


23 UlResidualBLER_Retrans18 % PUSCH BLER for the eighteenth

HARQ retransmission


24 UlResidualBLER_Retrans19 % PUSCH BLER for the nineteenth

HARQ retransmission


25 UlResidualBLER_Retrans20 % PUSCH BLER for the twentieth HARQ

retransmission


26 UlResidualBLER_Retrans21 % PUSCH BLER for the twenty first

HARQ retransmission




(Continued)



Lower/Upper

Limit

27 UlResidualBLER_Retrans22 % PUSCH BLER for the twenty second

HARQ retransmission


28 UlResidualBLER_Retrans23 % PUSCH BLER for the twenty third

HARQ retransmission


29 UlResidualBLER_Retrans24 % PUSCH BLER for the twenty fourth

HARQ retransmission


30 UlResidualBLER_Retrans25 % PUSCH BLER for the twenty fifth

HARQ retransmission


31 UlResidualBLER_Retrans26 % PUSCH BLER for the twenty sixth

HARQ retransmission


32 UlResidualBLER_Retrans27 % PUSCH BLER for the twenty seventh

HARQ retransmission


33 DlTransmission_Retrans0 count The count of the initial PDSCH

HARQ transmissions

CC The PDSCH HARQ is transmitted

for the first time.

int 0~2147483647

34 DlTransmission_Retrans1 count The count of the first PDSCH HARQ

retransmissions

CC The PDSCH HARQ is

retransmitted for the first time.

int 0~2147483647

35 DlTransmission_Retrans2 count The count of the second PDSCH

HARQ retransmissions


retransmitted for the second time.

int 0~2147483647

36 DlTransmission_Retrans3 count The count of the third PDSCH HARQ

retransmissions


retransmitted for the third time.

int 0~2147483647

37 UlTransmission_Retrans0 count The count of the initial PUSCH

HARQ transmissions

CC The PUSCH HARQ is transmitted

for the first time.

int 0~2147483647

38 UlTransmission_Retrans1 count The count of the first PUSCH HARQ

retransmissions

CC The PUSCH HARQ is

retransmitted for the first time.

int 0~2147483647



(Continued)



Lower/Upper

Limit

39 UlTransmission_Retrans2 count The count of the second PUSCH



retransmitted for the second time.

int 0~2147483647

40 UlTransmission_Retrans3 count The count of the third PUSCH HARQ

retransmissions


retransmitted for the third time.

int 0~2147483647

41 UlTransmission_Retrans4 count The count of the fourth PUSCH



retransmitted for the fourth time.

int 0~2147483647

42 UlTransmission_Retrans5 count The count of the fifth PUSCH HARQ

retransmissions


retransmitted for the fifth time.

int 0~2147483647

43 UlTransmission_Retrans6 count The count of the sixth PUSCH



retransmitted for the sixth time.

int 0~2147483647

44 UlTransmission_Retrans7 count The count of the seventh PUSCH



retransmitted for the seventh time.

int 0~2147483647

45 UlTransmission_Retrans8 count The count of the eighth PUSCH



retransmitted for the eighth time.

int 0~2147483647

46 UlTransmission_Retrans9 count The count of the ninth PUSCH



retransmitted for the ninth time.

int 0~2147483647

47 UlTransmission_Retrans10 count The count of the tenth PUSCH



retransmitted for the tenth time.

int 0~2147483647

48 UlTransmission_Retrans11 count The count of the eleventh PUSCH



retransmitted for the eleventh

time.

int 0~2147483647

49 UlTransmission_Retrans12 count The count of the twelfth PUSCH



retransmitted for the twelfth time.

int 0~2147483647



(Continued)



Lower/Upper

Limit

50 UlTransmission_Retrans13 count The count of the thirteenth PUSCH



retransmitted for the thirteenth

time.

int 0~2147483647

51 UlTransmission_Retrans14 count The count of the fourteenth PUSCH



retransmitted for the fourteenth

time.

int 0~2147483647

52 UlTransmission_Retrans15 count The count of the fifteenth PUSCH



retransmitted for the fifteenth

time.

int 0~2147483647

53 UlTransmission_Retrans16 count The count of the sixteenth PUSCH



retransmitted for the sixteenth

time.

int 0~2147483647

54 UlTransmission_Retrans17 count The count of the seventeenth

PUSCH HARQ retransmissions


retransmitted for the seventeenth

time.

int 0~2147483647

55 UlTransmission_Retrans18 count The count of the eighteenth PUSCH



retransmitted for the eighteenth

time.

int 0~2147483647

56 UlTransmission_Retrans19 count The count of the nineteenth PUSCH



retransmitted for the nineteenth

time.

int 0~2147483647

57 UlTransmission_Retrans20 count The count of the twentieth PUSCH



retransmitted for the twentieth

time.

int 0~2147483647



(Continued)



Lower/Upper

Limit

58 UlTransmission_Retrans21 count The count of the twenty first PUSCH



retransmitted for the twenty first

time.

int 0~2147483647

59 UlTransmission_Retrans22 count The count of the twenty second



retransmitted for the twenty

second time.

int 0~2147483647

60 UlTransmission_Retrans23 count The count of the twenty third PUSCH



retransmitted for the twenty third

time.

int 0~2147483647

61 UlTransmission_Retrans24 count The count of the twenty fourth



retransmitted for the twenty fourth

time.

int 0~2147483647

62 UlTransmission_Retrans25 count The count of the twenty fifth PUSCH



retransmitted for the twenty fifth

time.

int 0~2147483647

63 UlTransmission_Retrans26 count The count of the twenty sixth



retransmitted for the twenty sixth

time.

int 0~2147483647

64 UlTransmission_Retrans27 count The count of the twenty seventh



retransmitted for the twenty

seventh time.

int 0~2147483647

[Collection Time]

TTI



10.3.18 AMC

The AMC statistics consists of MIMO statistics, MCS statistics, downlink MCS statistics, downlink layer statistics, downlink CQI statistics,

downlink PMI statistics, downlink RI statistics and downlink ACK/NACK/DTX Ratio statistics. For the details on each item, refer to the

explanation of the statistics of each item below.

MIMO

Collects the Block Error Rate (BLER) information for each layer for PUSCH/PDSCH.


The PM measures MIMO every five seconds. These five-second samples are used to calculate the following statistics.

[Index]



Layer 1~4 Layer (MIMO Layer)

[Statistics Type]

No Item Unit Definition Collection Method Count Collected When Type Lower/Upper

Limit

1 PdschBLERperLayer % PDSCH BLER for each layer SI avg (PdschBLERperLayer) float 0.00~100.00

2 PuschBLERperLayer % PUSCH BLER for each layer SI avg (PuschBLERperLayer) float 0.00~100.00



[Collection Time]

TTI

MCS

The eNB collects the PUSCH‟s Block Error Rate (BLER), the number of allocated PRBs and the number of transmissions for each MCS.

For the PDSCH, it collects the Block Error Rate (BLER) and the number of allocated PRBs.


The PM measures MCS every five seconds. These five-second samples are used to calculate the following statistics.

[Index]



[Statistics Type]



Lower/Upper

Limit

1 PdschBLERperMCS0 % PDSCH BLER transmitted to MCS 0 SI avg (PdschBLERperMCS0) float 0.00~100.00








(Continued)



Lower/Upper

Limit

























(Continued)



Lower/Upper

Limit





33 PuschBLERperMCS0 % PUSCH BLER received at MCS 0 SI avg (PuschBLERperMCS0) float 0.00~100.00




















(Continued)



Lower/Upper

Limit















65 UlReceivedMCS0 count The number of times MCS 0 received PUSCH CC MCS 0 receives PUSCH. float 0~3.4 * 10^38










(Continued)



Lower/Upper

Limit

























(Continued)



Lower/Upper

Limit



97 DlSchedulerMCS0 count The total number of PRBs assigned to PDSCH

MCS 0

CC PRB is assigned to PDSCH

MCS 0.

int 0~2147483647


MCS 1


MCS 1.

int 0~2147483647


MCS 2


MCS 2.

int 0~2147483647


MCS 3


MCS 3.

int 0~2147483647


MCS 4


MCS 4.

int 0~2147483647


MCS 5


MCS 5.

int 0~2147483647


MCS 6


MCS 6.

int 0~2147483647


MCS 7


MCS 7.

int 0~2147483647


MCS 8


MCS 8.

int 0~2147483647


MCS 9


MCS 9.

int 0~2147483647


MCS 10


MCS 10.

int 0~2147483647



(Continued)



Lower/Upper

Limit


MCS 11


MCS 11.

int 0~2147483647


MCS 12


MCS 12.

int 0~2147483647


MCS 13


MCS 13.

int 0~2147483647


MCS 14


MCS 14.

int 0~2147483647


MCS 15


MCS 15.

int 0~2147483647


MCS 16


MCS 16.

int 0~2147483647


MCS 17


MCS 17.

int 0~2147483647


MCS 18


MCS 18.

int 0~2147483647


MCS 19


MCS 19.

int 0~2147483647


MCS 20


MCS 20.

int 0~2147483647


MCS 21


MCS 21.

int 0~2147483647


MCS 22


MCS 22.

int 0~2147483647



(Continued)



Lower/Upper

Limit

120 DlSchedulerMCS23 count The total number of PRBs assigned to

PDSCH MCS 23


MCS 23.

int 0~2147483647


PDSCH MCS 24


MCS 24.

int 0~2147483647


PDSCH MCS 25


MCS 25.

int 0~2147483647


PDSCH MCS 26


MCS 26.

int 0~2147483647


PDSCH MCS 27


MCS 27.

int 0~2147483647


PDSCH MCS 28


MCS 28.

int 0~2147483647


PDSCH MCS 29


MCS 29.

int 0~2147483647


PDSCH MCS 30


MCS 30.

int 0~2147483647


PDSCH MCS 31


MCS 31.

int 0~2147483647

129 UlSchedulerMCS0 count The total number of PRBs assigned to

PUSCH MCS 0

CC PRB is assigned to PUSCH

MCS 0.

int 0~2147483647


PUSCH MCS 1


MCS 1.

int 0~2147483647


PUSCH MCS 2


MCS 2.

int 0~2147483647



(Continued)



Lower/Upper

Limit


PUSCH MCS 3


MCS 3.

int 0~2147483647


PUSCH MCS 4


MCS 4.

int 0~2147483647


PUSCH MCS 5


MCS 5.

int 0~2147483647


PUSCH MCS 6


MCS 6.

int 0~2147483647


PUSCH MCS 7


MCS 7.

int 0~2147483647


PUSCH MCS 8


MCS 8.

int 0~2147483647


PUSCH MCS 9


MCS 9.

int 0~2147483647


PUSCH MCS 10


MCS 10.

int 0~2147483647


PUSCH MCS 11


MCS 11.

int 0~2147483647


PUSCH MCS 12


MCS 12.

int 0~2147483647


PUSCH MCS 13


MCS 13.

int 0~2147483647



(Continued)



Lower/Upper

Limit


PUSCH MCS 14


MCS 14.

int 0~2147483647


PUSCH MCS 15


MCS 15.

int 0~2147483647


PUSCH MCS 16


MCS 16.

int 0~2147483647


PUSCH MCS 17


MCS 17.

int 0~2147483647


PUSCH MCS 18


MCS 18.

int 0~2147483647


PUSCH MCS 19


MCS 19.

int 0~2147483647


PUSCH MCS 20


MCS 20.

int 0~2147483647


PUSCH MCS 21


MCS 21.

int 0~2147483647


PUSCH MCS 22


MCS 22.

int 0~2147483647


PUSCH MCS 23


MCS 23.

int 0~2147483647


PUSCH MCS 24


MCS 24.

int 0~2147483647


PUSCH MCS 25


MCS 25.

int 0~2147483647



(Continued)



Lower/Upper

Limit


PUSCH MCS 26

CC PRB is assigned to PUSCH MCS 26. int 0~2147483647


PUSCH MCS 27



PUSCH MCS 28



PUSCH MCS 29



PUSCH MCS 30



PUSCH MCS 31


[Collection Time]

TTI



DL MCS

The eNB collects the transmission counts per MCS/layer/Codeword for PDSCH.


The PM measures the DL_MCS every five seconds. These five-second samples are used to calculate the following statistics.

[Index]



Layer 1~4 Layer

Codeword 0~1 Codeword

[Statistics Type]


Method

Count Collected

When Type

Lower/Upper

Limit

1 DlTransmittedMCS0 count The number of times MCS 0 PDSCH is transmitted

per layer/codeword

CC MCS 0 PDSCH is

transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 1 PDSCH is

transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 2 PDSCH is

transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 3 PDSCH is

transmitted.

float 0~3.4 * 10^38



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit


per layer/codeword

CC MCS 4 PDSCH is

transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 5 PDSCH is

transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 6 PDSCH is

transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 7 PDSCH is

transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 8 PDSCH is

transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 9 PDSCH is

transmitted.

float 0~3.4 * 10^38

11 DlTransmittedMCS10 count The number of times MCS 10 PDSCH is

transmitted per layer/codeword

CC MCS 10 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 11 PDSCH

is transmitted.

float 0~3.4 * 10^38



CC MCS 12 PDSCH

is transmitted.

float 0~3.4 * 10^38



CC MCS 13 PDSCH

is transmitted.

float 0~3.4 * 10^38



CC MCS 14 PDSCH

is transmitted.

float 0~3.4 * 10^38



CC MCS 15 PDSCH

is transmitted.

float 0~3.4 * 10^38



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit


per layer/codeword

CC MCS 16 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 17 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 18 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 19 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 20 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 21 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 22 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 23 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 24 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 25 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 26 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 27 PDSCH

is transmitted.

float 0~3.4 * 10^38



(Continued)


Method

Count Collected

When Type

Lower/Upper

Limit


per layer/codeword

CC MCS 28 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 29 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 30 PDSCH

is transmitted.

float 0~3.4 * 10^38


per layer/codeword

CC MCS 31 PDSCH

is transmitted.

float 0~3.4 * 10^38

[Collection Time]

TTI



DL Layer

The eNB collects the transmission counts per layer for PDSCH.


The PM measures the DL_LAYER every five seconds. These five-second samples are used to calculate the following statistics.

[Index]



Layer 1~4 Layer

[Statistics Type]



Lower/Upper

Limit

1 DlTransmittedLayer count The number of times PDSCH is

transmitted for each layer

CC DL for each layer is

transmitted.

float 0~3.4 * 10^38

[Collection Time]

TTI



DL CQI

The eNB collects the CQI report information for each layer/codeword of the UE


The PM measures the DL_CQI every five seconds. These five-second samples are used to calculate the following statistics:

[Index]



Layer 1~4 Layer


[Statistics Type]



Lower/Upper

Limit

1 DlReceivedCQI0 count The number of times CQI 0 is

received for each layer/codeword

CC CQI0 is received for each layer/codeword. float 0~3.4 * 10^38



CC CQI 1 is received for each layer/codeword. float 0~3.4 * 10^38









(Continued)



Lower/Upper

Limit







































[Collection Time]

Upon CQI reception

DL PMI

The eNB collects the UE‟s PMI report information.


The PM measures the DL_PMI every five seconds. These five-second samples are used to calculate the following statistics:

[Index]





[Statistics Type]



Lower/Upper

Limit

1 DlReceivedPMI0 count The number of times PMI 0 is received CC PMI 0 is received. float 0~3.4 * 10^38
















[Collection Time]

Upon PMI reception



DL RI

Collects the UE‟s RI report information.


The PM measures the DL_RI every five seconds. These five-second samples are used to calculate the following statistics:

[Index]



[Statistics Type]



Lower/Upper

Limit

1 DlReceivedRI0 count reserved CC Not counted float 0~3.4 * 10^38

2 DlReceivedRI1 count The number of times RI 1 is received CC RI 1 is received. float 0~3.4 * 10^38




[Collection Time]

Upon RI reception



DL ACK/NACK/DTX Ratio

The eNB collects the UE‟s ACK/NACK/DTX ratio information.


The PM measures DL_ACK_NACK_DTX_RAT every five seconds. These five-second samples are used to calculate the following statistics:

[Index]



Layer 1~4 Layer


Status 0~2 0: ACK

1: NACK

2: DTX

[Statistics Type]



Lower/Upper

Limit

1 DlreceivedAckNackDtxRatio % ACK, NACK, DTX ratio SI avg (DlreceivedAckNackDtxRatio) float 0.00~100.00

[Collection Time]

Upon PUCCH/PUSCH ACK reception



10.3.19 KPI

The eNB calculates the KPI defined in 3GPP 32.450 and provides to the EMS.

Accessibility

A KPI that shows 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


The PM calculates the KPI every 5 minutes.

[Index]



100

QCI.tEstabInitSAEB.NbrAt

QCIt.ccEstabIniSAEB.NbrSu

EstabAttS1SIG.Conn

EstabSuccS1SIG.Conn

causenEstab.RRC.AttCon

causennEstab.RRC.SuccCo

1

QCI

cause

QCI

cause

BEstabSRInitialEPSA

100

QCItEstabAdd.SAEB.NbrAt

QCI.ccEstabAddSAEB.NbrSu

2

QCI

QCI

stabSRAddedEPSBEA



[Statistics Type]



Lower/Upper

Limit

1 ErabAccessibilityInit % Initial E-RAB establishment

success rate.

E-RAB Success/ERAB

Attempt

OW a = sum (STAT_RRC_ESTAB, ConnEstabSucc,

cNum, MAX_EstabCAUSE);

b = sum (STAT_RRC_ESTAB, ConnEstabAtt, cNum,

MAX_EstabCAUSE);

c = sum (STAT_S1SIG, S1ConnEstabSucc, cNum,

MAX_EstabCAUSE);

d = sum (STAT_S1SIG, S1ConnEstabAtt, cNum,

MAX_EstabCAUSE);

e = sum (STAT_ERAB_ESTAB, EstabInitSuccNbr,

cNum, MAX_EstabCAUSE, MAX_QCI-1);

f = sum (STAT_ERAB_ESTAB, EstabInitAttNbr,

cNum, MAX_EstabCAUSE, MAX_QCI-1);

ErabAccessibilityInit = ((a/b) * (c/d) * (e/f) * 100);

float 0.00~100.00

2 ErabAccessibilityAdd % Added E-RAB

establishment success rate.

Added E-RAN

Success/Added ERAB

Attempt

OW a = sum (STAT_ERAB_ESTAB_ADD,

EstabAddSuccNbr, cNum, MAX_QCI-1);

b = sum (STAT_ERAB_ESTAB_ADD,

EstabAddAttNbr, cNum, MAX_QCI-1);

ErabAccessibilityAdd = (a/b) * 100;

float 0.00~100.00

[Collection Time]

Every 5 minutes upon reporting the statistics



Integrity

A KPI 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



[Index]



Samples

Samples

DLtpT

DLtpV

ThroughputIP__

__

_

xQCIxQCI IPLatDlDRBLatDownlink .



[Statistics Type]



Lower/Upper

Limit

1 EutranIpThroughput % IP throughput for each cell

Total EutranIpThroughput for

each QCI

OW sum (STAT_AIR_RLC_BYTES, IpThru,

cNum, MAX_QCI-1)

float 0.00~100.00

2 EutranIpLatency % IP latency for each cell

Total EutranIpLatency for each

QCI

OW sum (STAT_IP_LATENCY, IpLateDl, cNum,

MAX_QCI-1)

float 0.00~100.00

[Collection Time]




Availability

A KPI that shows Availability of E-UTRAN Cell.

Percentage of time that the cell is considered available.

The cell availability provides the statistics of the elapsed time from the cell down due to the fault until its recovery.

E-UTRAN Cell Availability



[Index]



100_

]ime.[causeavailableTRRU.CellUn-t_periodmeasuremencause

periodtmeasuremenbilityCellAvaila



[Statistics Type]



Lower/Upper

Limit

1 EutranCellAvailability % Percentage of time that

the cell is considered

available

OW period = (PM collection time: 5 minutes) * 60; (e.g.

Period=300)

cellUnAvailTime = read (STAT_CELL_UNAVAILABLE,

CellUnavailableDown, cNum)

EutranCellAvailability = (period-cellUnAvailTime) *

100/period

float 0.00~100.00

[Collection Time]




Mobility

A KPI that shows how E-UTRAN Mobility functionality is working.

Success rate of E-UTRAN Mobility.

The handover is calculated for each case to produce the KPI.

Intra eNB Handover

X2 Handover Out

X2 Handover In

S1 Handover Out

S1 Handover In

Inter-RAT HPRD Handover

HO.PrepAtt.QCI is calculated by HO.PrepSucc.QCI + HO.PrepFail.QCI.



[Index]



%100.QCIHO.PrepAtt

c.QCIHO.PrepSuc

HO.ExeAtt

HO.ExeSucc

xQCI

xQCI

xQCIRateSuccessMobility



[Statistics Type]



Lower/Upper

Limit

1 EutranMobilityHOIntra % HOIntra Success

rate of E-UTRAN

Mobility

OW attVal = sum (STAT_HO_INTRA, IntraEnbAtt, cNum,

MAX_TCID, MAX_HOCAUSE);

succVal = sum (STAT_HO_INTRA, IntraEnbSucc, cNum,


prepSuccVal = sum (STAT_HO_INTRA,

IntraEnbPrepSucc, cNum, MAX_TCID,

MAX_HOCAUSE);

EutranMobilityHOIntra = (succVal/attVal) *

(prepSuccVal/attVal) * 100

float 0.00~100.00

2 EutranMobilityHOX2Out % HOX2Out

Success rate of

E-UTRAN

Mobility

OW attVal = sum (STAT_HO_X2_OUT, InterX2OutAtt, cNum,


succVal = sum (STAT_HO_X2_OUT, InterX2OutSucc,

cNum, MAX_TCID, MAX_HOCAUSE);

prepSuccVal = sum (STAT_HO_X2_OUT,

InterX2OutPrepSucc, cNum, MAX_TCID,

MAX_HOCAUSE);

EutranMobilityHOX2Out = (succVal/attVal) *


float 0.00~100.00

3 EutranMobilityHOX2In % HOX2In

Success rate of

E-UTRAN

Mobility

OW attVal = sum (STAT_HO_X2_IN, InterX2InAtt, cNum,

MAX_HOCAUSE);

succVal = sum (STAT_HO_X2_IN, InterX2InSucc, cNum,

MAX_HOCAUSE);

preSuccVal = sum (STAT_HO_X2_IN, InterX2InPrepSucc,

cNum, MAX_HOCAUSE);

EutranMobilityHOX2In = (succVal/attVal) *

(preSuccVal/attVal) * 100

float 0.00~100.00



(Continued)



Lower/Upper

Limit

4 EutranMobilityHOS1Out % HOIS1Out

Success rate of

E-UTRAN

Mobility

OW attVal = sum (STAT_HO_S1_OUT, InterS1OutAtt, cNum,


succVal = sum (STAT_HO_S1_OUT, InterS1OutSucc,

cNum, MAX_TCID, MAX_HOCAUSE);

prepSuccVal = sum (STAT_HO_S1_OUT,

InterS1OutPrepSucc, cNum, MAX_TCID,

MAX_HOCAUSE);

EutranMobilityHOS1Out = (succVal/attVal) *


float 0.00~100.00

5 EutranMobilityHOS1In % HOS1In

Success rate of

E-UTRAN

Mobility

OW attVal = sum (STAT_HO_S1_IN, InterS1InAtt, cNum,

MAX_HOCAUSE);

succVal = sum (STAT_HO_S1_IN, InterS1InSucc, cNum,

MAX_HOCAUSE);

preSuccVal = sum (STAT_HO_S1_IN, InterS1InPrepSucc,

cNum, MAX_HOCAUSE);

EutranMobilityHOS1In = (succVal/attVal) *


float 0.00~100.00

6 EutranMobilityHOInterRa

tHrpd

% HOInterRat

Success rate of

E-UTRAN

Mobility

OW attVal = sum (STAT_HO_INTER_RAT_HRPD,

RatOutAttHRPD, cNum, MAX_HOCAUSE);

succVal = sum (STAT_HO_INTER_RAT_HRPD,

RatOutSuccHRPD, cNum, MAX_HOCAUSE);

preSuccVal = sum (STAT_HO_INTER_RAT_HRPD,

RatOutPrepSuccHRPD, cNum,

MAX_HOCAUSE);

EutranMobilityHOS1In = (succVal/attVal) *


float 0.00~100.00



(Continued)



Lower/Upper

Limit

7 EutranMobilityHOInterRat

UtranOut

% HOInterRatUtran

Out rate of E-

UTRAN Mobility

OW attVal = sum (STAT_HO_INTER_RAT_UTRAN_OUT,

RatOutAttUTRAN, cNum, MAX_HOCAUSE);

succVal = sum (STAT_HO_INTER_RAT_UTRAN_OUT,

RatOutSuccUTRAN, cNum, MAX_HOCAUSE);

preSuccVal = sum (STAT_HO_INTER_RAT_UTRAN_

OUT, RatOutPrepSuccUTRAN, cNum,

MAX_HOCAUSE);

EutranMobilityHOInterRatUtranOut = (succVal/attVal) *


float 0.00~100.00

8 EutranMobilityHOInterRat

UtranIn

% HOInterRatUtran

In rate of E-

UTRAN Mobility

OW attVal = sum (STAT_HO_INTER_RAT_UTRAN_IN,

RatInAttUTRAN, cNum, MAX_HOCAUSE);

succVal = sum (STAT_HO_INTER_RAT_UTRAN_IN,

RatInSuccUTRAN, cNum, MAX_HOCAUSE);

preSuccVal = sum (STAT_HO_INTER_RAT_UTRAN_

IN, RatInPrepSuccUTRAN, cNum,

MAX_HOCAUSE);

EutranMobilityHOInterRatUtranIn = (succVal/attVal) *


float 0.00~100.00

[Collection Time]



© SAMSUNG Electronics Co., Ltd. A-1

ANNEX A. Open Source

Announcement

Some software components of this product incorporate source code covered under the

GNU General Public License (GPL), the GNU Lesser General Public License (LGPL) and

BSD License etc.

Acknowledgement:

The software included in this product contains copyrighted software that is licensed under

the GPL/LGPL. You may obtain the complete Corresponding Source code from us for a

period of three years after our last shipment of this product by sending email to:

[email protected]

If you want to obtain the complete Corresponding Source code in the physical medium

such as CD-ROM, the cost of physically performing source distribution may be charged.

This offer is valid to anyone in receipt of this information.

Below is the list of components covered under GNU General Public License, the GNU

Lesser General Public License and BSD License etc.

Opensource S/W License

Apache HTTP Server Apache License Version 2.0

OpenSSH BSD 2.0

NetBSD BSD 2.0

Net SNMP-net-snmp BSD 2.0

libssh2 BSD 2.0

Libedit BSD 2.0

Android-platform-external-gtest BSD 2.0

ISC DHCP DHCP License

Linux Kernel GPL 2.0

ftplib GPL 2.0

DHCP Forwarder GPL 2.0



(Continued)

Opensource S/W License

AVL GPL 2.0

ftplib LGPL 2.1

LIBSMI-Main Libsmi License

ppp-Pauls PPP Package License for PPP

libxml2 MIT License V2

libxslt MIT v2 with Ad Clause License

NTP-The Network Time Protocol NTP License

OpenSSL OpenSSL Combined License

zlib zlib/libpng License



Apache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

“License” shall mean the terms and conditions for use, reproduction, and distribution as

defined by Sections 1 through 9 of this document.

“Licensor” shall mean the copyright owner or entity authorized by the copyright owner that

is granting the License.

“Legal Entity” shall mean the union of the acting entity and all other entities that control,

are controlled by, or are under common control with that entity. For the purposes of this

definition, “control” means (i) the power, direct or indirect, to cause the direction or

management of such entity, whether by contract or

otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or

(iii) beneficial ownership of such entity. “You” (or “Your”) shall mean an individual or

Legal Entity exercising permissions granted by this License. “Source” form shall mean the

preferred form for making modifications, including but not limited to software source code,

documentation source, and configuration files.

“Object” form shall mean any form resulting from mechanical transformation or translation

of a Source form, including but not limited to compiled object code, generated

documentation, and conversions to other media types.

“Work” shall mean the work of authorship, whether in Source or Object form, made

available under the License, as indicated by a copyright notice that is included in or

attached to the work (an example is provided in the Appendix below).

“Derivative Works” shall mean any work, whether in Source or Object form, that is based

on (or derived from) the Work and for which the editorial revisions, annotations,

elaborations, or other modifications represent, as a whole, an original work of authorship.

For the purposes of this License, Derivative Works shall not include works that remain

separable from, or merely link (or bind by name) to the interfaces of, the Work and

Derivative Works thereof.

“Contribution” shall mean any work of authorship, including the original version of the

Work and any modifications or additions to that Work or Derivative Works thereof, that is

intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by

an individual or Legal Entity authorized to submit on behalf of the copyright owner.

For the purposes of this definition, “submitted” means any form of electronic, verbal, or

written communication sent to the Licensor or its representatives, including but not limited

to communication on electronic mailing lists, source code control systems, and issue

tracking systems that are managed by, or on behalf of, the Licensor for the purpose of

discussing and improving the Work, but excluding communication that is conspicuously

marked or otherwise designated in writing by the copyright owner as “Not a Contribution.”



“Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a

Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License.

Subject to the terms and conditions of this License, each Contributor hereby grants to You a

perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license

to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense,

and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License.

Subject to the terms and conditions of this License, each Contributor hereby grants to You a

perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated

in this section) patent license to make, have made, use, offer to sell, sell, import, and

otherwise transfer the Work, where such license applies only to those patent claims

licensable by such Contributor that are necessarily infringed by their Contribution(s) alone

or by combination of their Contribution(s) with the Work to which such Contribution(s)

was submitted. If You institute patent litigation against any entity (including a cross-claim

or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within

the Work constitutes direct or contributory patent infringement, then any patent licenses

granted to You under this License for that Work shall terminate as of the date such litigation

is filed.

4. Redistribution.

You may reproduce and distribute copies of the Work or Derivative Works thereof in any

medium, with or without modifications, and in Source or Object form, provided that You

meet the following conditions:

(a) You must give any other recipients of the Work or Derivative Works a copy of this

License; and

(b) You must cause any modified files to carry prominent notices stating that You changed

the files; and

(c) You must retain, in the Source form of any Derivative Works that You distribute, all

copyright, patent, trademark, and attribution notices from the Source form of the Work,

excluding those notices that do not pertain to any part of the Derivative Works; and



(d) If the Work includes a “NOTICE” text file as part of its distribution, then any

Derivative Works that You distribute must include a readable copy of the attribution

notices contained within such NOTICE file, excluding those notices that do not pertain

to any part of the Derivative Works, in at least one of the following places: within a

NOTICE text file distributed as part of the Derivative Works; within the Source form

or documentation, if provided along with the Derivative Works; or, within a display

generated by the Derivative Works, if and wherever such third-party notices normally

appear. The contents of the NOTICE file are for informational purposes only and do

not modify the License. You may add Your own attribution notices within Derivative

Works that You distribute, alongside or as an addendum to the NOTICE text from the

Work, provided that such additional attribution notices cannot be construed as

modifying the License.

You may add Your own copyright statement to Your modifications and provide additional

or different license terms and conditions use, reproduction, or distribution of Your

modifications, or any such Derivative Works as a whole, provided Your use, roduction, and

distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions.

Unless You explicitly state otherwise, Contribution intentionally submitted for inclusion in

the Work by You to the Licensor shall be under the terms and conditions of this License,

without any additional terms or conditions. Notwithstanding the above, nothing herein shall

supersede or modify the terms of any separate license agreement you may have executed

with Licensor regarding such Contributions.

6. Trademarks.

This License does not grant permission to use the trade names, trademarks, service marks,

or product names of the Licensor, except as required for reasonable and customary use in

describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty.

Unless required by applicable law or agreed to in writing, Licensor provides the Work (and

each Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT

WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including,

without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT,

MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely

responsible for determining the appropriateness of using or redistributing the Work and

assume any risks associated with Your exercise of permissions under this License.



8. Limitation of Liability.

In no event and under no legal theory, whether in tort (including negligence), contract, or

otherwise, unless required by applicable law (such as deliberate and grossly negligent acts)

or agreed to in writing, shall any Contributor be liable to You for damages, including any

direct, indirect, special, incidental, or consequential damages of any character arising as a

result of this License or out of the use or inability to use the Work (including but not

limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or

any and all other commercial damages or losses), even if such Contributor has been

advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability.

While redistributing the Work or Derivative Works thereof, You may choose to offer, and

charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations

and/or rights consistent with this License. However, in accepting such obligations, You

may act only on Your own behalf and on Your sole responsibility, not on behalf of any

other Contributor, and only if You agree to indemnify, defend, and hold each Contributor

harmless for any liability incurred by, or claims asserted against, such Contributor by

reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following boilerplate notice, with the

fields enclosed by brackets “[]” replaced with your own identifying information.

(Don‟t include the brackets!) The text should be enclosed in the appropriate comment

syntax for the file format. We also recommend that a file or class name and description of

purpose be included on the same “printed page” as the copyright notice for easier

identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file

except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License

is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY

KIND, either express or implied. See the License for the specific language governing

permissions and limitations under the License.



BSD 2.0 License

Copyright (C) <YEAR>, <OWNER>

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are

permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of

conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list of

conditions and the following disclaimer in the documentation and/or other materials

provided with the distribution.

Neither the name of the <ORGANIZATION> nor the names of its contributors may be

used to endorse or promote products derived from this software without specific prior

written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND

CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES,

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE

DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR

CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT

LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF

USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED

AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN

ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE

POSSIBILITY OF SUCH DAMAGE.

DHCP License

Copyright (C) 2004 by Internet Systems Consortium, Inc.(“ISC”)

Copyright (C) 1996-2003 by Internet Software Consortium

Permission to use, copy, modify, and distribute this software for any purpose with or

without fee is hereby granted, provided that the above copyright notice and this permission

notice appear in all copies.

THE SOFTWARE IS PROVIDED “AS IS” AND ISC DISCLAIMS ALL WARRANTIES

WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES

OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE

FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR

ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR

PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER

TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR

PERFORMANCE OF THIS SOFTWARE.



Internet Systems Consortium, Inc.

950 Charter Street

Redwood City, CA 94063

[email protected]

http://www.isc.org/

GNU GENERAL PUBLIC LICENSE

Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.

51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but

changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change

it. By contrast, the GNU General Public License is intended to guarantee your freedom to

share and change free software--to make sure the software is free for all its users.

This General Public License applies to most of the Free Software Foundation‟s software and to

any other program whose authors commit to using it. (Some other Free Software

Foundation software is covered by the GNU Library General Public License instead.) You

can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public

Licenses are designed to make sure that you have the freedom to distribute copies of free

software (and charge for this service if you wish), that you receive source code or can get it

if you want it, that you can change the software or use pieces of it in new free programs;

and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these

rights or to ask you to surrender the rights. These restrictions translate to certain

responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you

must give the recipients all the rights that you have. You must make sure that they, too,

receive or can get the source code. And you must show them these terms so they know their

rights.

We protect your rights with two steps:

(1) copyright the software, and (2) offer you this license which gives you legal permission

to copy, distribute and/or modify the software. Also, for each author‟s protection and ours,

we want to make certain that everyone understands that there is no warranty for this free

software.


http://www.isc.org/



If the software is modified by someone else and passed on, we want its recipients to know

that what they have is not the original, so that any problems introduced by others will not

reflect on the original authors‟ reputations.

Finally, any free program is threatened constantly by software patents.

We wish to avoid the danger that redistributors of a free program will individually obtain patent

licenses, in effect making the program proprietary. To prevent this, we have made it clear that

any patent must be licensed for everyone‟s free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND

MODIFICATION

0) This License applies to any program or other work which contains a notice placed by

the copyright holder saying it may be distributed under the terms of this General

Public License. The “Program”, below, refers to any such program or work, and a

“work based on the Program” means either the Program or any derivative work under

copyright law: that is to say, a work containing the Program or a portion of it, either

verbatim or with modifications and/or translated into another language.

(Hereinafter, translation is included without limitation in the term “modification”.)

Each licensee is addressed as “you”.

Activities other than copying, distribution and modification are not covered by this

License; they are outside its scope. The act of running the Program is not restricted, and the

output from the Program is covered only if its contents constitute a work based on the

Program (independent of having been made by running the Program). Whether that is

true depends on what the Program does.

1) You may copy and distribute verbatim copies of the Program‟s source code as you

receive it, in any medium, provided that you conspicuously and appropriately publish

on each copy an appropriate copyright notice and disclaimer of warranty; keep intact

all the notices that refer to this License and to the absence of any warranty; and give

any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your

option offer warranty protection in exchange for a fee.

2) You may modify your copy or copies of the Program or any portion of it, thus forming

a work based on the Program, and copy and distribute such modifications or work

under the terms of Section 1 above, provided that you also meet all of these

conditions:

a) You must cause the modified files to carry prominent notices stating that you

changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or in part

contains or is derived from the Program or any part thereof, to be licensed as a

whole at no charge to all third parties under the terms of this License.

c) If the modified program normally reads commands interactively when run, you

must cause it, when started running for such interactive use in the most ordinary way, to

print or display an announcement including an appropriate copyright notice and a

notice that there is no warranty (or else, saying that you provide a warranty) and

that users may redistribute the program under these conditions, and telling the user

how to view a copy of this License. (Exception: if the Program itself is interactive

but does not normally print such an announcement, your work based on the

Program is not required to print an announcement.)



These requirements apply to the modified work as a whole.

If identifiable sections of that work are not derived from the Program, and can be

reasonably considered independent and separate works in themselves, then this

License, and its terms, do not apply to those sections when you distribute them as

separate works. But when you distribute the same sections as part of a whole which is

a work based on the Program, the distribution of the whole must be on the terms of

this License, whose permissions for other licensees extend to the entire whole, and

thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work

written entirely by you; rather, the intent is to exercise the right to control the

distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the

Program (or with a work based on the Program) on a volume of a storage or

distribution medium does not bring the other work under the scope of this License.

3) You may copy and distribute the Program (or a work based on it, under Section 2) in

object code or executable form under the terms of Sections 1 and 2 above provided

that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code,

which must be distributed under the terms of Sections 1 and 2 above on a medium

customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third

party, for a charge no more than your cost of physically performing source

distribution, a complete machine-readable copy of the corresponding source code,

to be distributed under the terms of Sections 1 and 2 above on a medium

customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute

corresponding source code. (This alternative is allowed only for noncommercial

distribution and only if you received the program in object code or executable

form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making

modifications to it. For an executable work, complete source code means all the source

code for all modules it contains, plus any associated interface definition files, plus the

scripts used to control compilation and installation of the executable. However, as a

special exception, the source code distributed need not include anything that is

normally distributed (in either source or binary form) with the major components

(compiler, kernel, and so on) of the operating system on which the executable runs,

unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a

designated place, then offering equivalent access to copy the source code from the

same place counts as distribution of the source code, even though third parties are not

compelled to copy the source along with the object code.

4) You may not copy, modify, sublicense, or distribute the Program except as expressly

provided under this License. Any attempt otherwise to copy, modify, sublicense or

distribute the Program is void, and will automatically terminate your rights under this

License. However, parties who have received copies, or rights, from you under this

License will not have their licenses terminated so long as such parties remain in full

compliance.



5) You are not required to accept this License, since you have not signed it.

However, nothing else grants you permission to modify or distribute the Program or its

derivative works. These actions are prohibited by law if you do not accept this License.

Therefore, by modifying or distributing the Program (or any work based on the

Program), you indicate your acceptance of this License to do so, and all its terms and

conditions for copying, distributing or modifying the Program or works based on it.

6) Each time you redistribute the Program (or any work based on the Program), the

recipient automatically receives a license from the original licensor to copy, distribute

or modify the Program subject to these terms and conditions. You may not impose any

further restrictions on the recipients‟ exercise of the rights granted herein. You are not

responsible for enforcing compliance by third parties to this License.

7) If, as a consequence of a court judgment or allegation of patent infringement or for any

other reason (not limited to patent issues), conditions are imposed on you

(whether by court order, agreement or otherwise) that contradict the conditions of this

License, they do not excuse you from the conditions of this License.

If you cannot distribute so as to satisfy simultaneously your obligations under this

License and any other pertinent obligations, then as a consequence you may not

distribute the Program at all. For example, if a patent license would not permit royalty-

free redistribution of the Program by all those who receive copies directly or indirectly

through you, then the only way you could satisfy both it and this License would be to

refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular

circumstance, the balance of the section is intended to apply and the section as a whole

is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other

property right claims or to contest validity of any such claims; this section has the sole

purpose of protecting the integrity of the free software distribution system, which is

implemented by public license practices. Many people have made generous contributions to

the wide range of software distributed through that system in reliance on consistent

application of that system; it is up to the author/donor to decide if he or she is willing

to distribute software through any other system and a licensee cannot impose that

choice.

This section is intended to make thoroughly clear what is believed to be a consequence

of the rest of this License.

8) If the distribution and/or use of the Program is restricted in certain countries either by

patents or by copyrighted interfaces, the original copyright holder who places the

Program under this License may add an explicit geographical distribution limitation

excluding those countries, so that distribution is permitted only in or among countries

not thus excluded. In such case, this License incorporates the limitation as if written in

the body of this License.



9) The Free Software Foundation may publish revised and/or new versions of the General

Public License from time to time. Such new versions will be similar in spirit to the

present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a

version number of this License which applies to it and “any later version”, you have

the option of following the terms and conditions either of that version or of any later

version published by the Free Software Foundation.

If the Program does not specify a version number of this License, you may choose any

version ever published by the Free Software Foundation.

10) If you wish to incorporate parts of the Program into other free programs whose

distribution conditions are different, write to the author to ask for permission.

For software which is copyrighted by the Free Software Foundation, write to the Free

Software Foundation; we sometimes make exceptions for this. Our decision will be

guided by the two goals of preserving the free status of all derivatives of our free

software and of promoting the sharing and reuse of software generally.

NO WARRANTY

11) BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO

WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY

APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE

COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM

“AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR

IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES

OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE

PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE,

YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR

CORRECTION.

12) IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN

WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO

MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED

ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL,

SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF

THE USE OR INABILITY TO USE THE PROGRAM(INCLUDING BUT NOT

LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR

LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE

PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH

HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF

SUCH DAMAGES.




How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the

public, the best way to achieve this is to make it free software which everyone can

redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start

of each source file to most effectively convey the exclusion of warranty; and each file

should have at least the “copyright” line and a pointer to where the full notice is found.

<one line to give the program‟s name and a brief idea of what it does.>

Copyright (C) <year> <name of author>

This program is free software; you can redistribute it and/or modify it under the terms of the

GNU General Public License as published by the Free Software Foundation; either version 2 of

the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;

without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR

PURPOSE.

See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if

not, write to the Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-

1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in an

interactive mode:

Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with

ABSOLUTELY NO WARRANTY; for details type „show w‟.

This is free software, and you are welcome to redistribute it under certain conditions; type „show

c‟ for details.



GNU LESSER GENERAL PUBLIC LICENSE

Version 2.1, February 1999

Copyright (C) 1991, 1999 Free Software Foundation, Inc.

51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but

changing it is not allowed.

[This is the first released version of the Lesser GPL. It also counts as the successor of the

GNU Library Public License, version 2, hence the version number 2.1.]

Preamble

The licenses for most software are designed to take away your freedom to share and change

it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom

to share and change free software--to make sure the software is free for all its users.

This license, the Lesser General Public License, applies to some specially designated

software packages--typically libraries--of the Free Software Foundation and other authors

who decide to use it. You can use it too, but we suggest you first think carefully about

whether this license or the ordinary General Public License is the better strategy to use in

any particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use, not price.

Our General Public Licenses are designed to make sure that you have the freedom to

distribute copies of free software (and charge for this service if you wish); that you receive

source code or can get it if you want it; that you can change the software and use pieces of

it in new free programs; and that you are informed that you can do these things.

To protect your rights, we need to make restrictions that forbid distributors to deny you

these rights or to ask you to surrender these rights. These restrictions translate to certain

responsibilities for you if you distribute copies of the library or if you modify it.

For example, if you distribute copies of the library, whether gratis or for a fee, you must

give the recipients all the rights that we gave you. You must make sure that they, too,

receive or can get the source code.

If you link other code with the library, you must provide complete object files to the

recipients, so that they can relink them with the library after making changes to the library

and recompiling it. And you must show them these terms so they know their rights.

We protect your rights with a two-step method: (1) we copyright the library, and (2) we

offer you this license, which gives you legal permission to copy, distribute and/or modify

the library.

To protect each distributor, we want to make it very clear that there is no warranty for the

free library.

Also, if the library is modified by someone else and passed on, the recipients should know

that what they have is not the original version, so that the original author‟s reputation will

not be affected by problems that might be introduced by others.



Finally, software patents pose a constant threat to the existence of any free program. We

wish to make sure that a company cannot effectively restrict the users of a free program by

obtaining a restrictive license from a patent holder. Therefore, we insist that any patent

license obtained for a version of the library must be consistent with the full freedom of use

specified in this license.

Most GNU software, including some libraries, is covered by the ordinary GNU General

Public License.

This license, the GNU Lesser General Public License, applies to certain designated

libraries, and is quite different from the ordinary General Public License. We use this

license for certain libraries in order to permit linking those libraries into non-free programs.

When a program is linked with a library, whether statically or using a shared library, the

combination of the two is legally speaking a combined work, a derivative of the original

library. The ordinary General Public License therefore permits such linking only if the

entire combination fits its criteria of freedom. The Lesser General Public License permits

more lax criteria for linking other code with the library.

We call this license the “Lesser” General Public License because it does Less to protect the

user‟s freedom than the ordinary General Public License. It also provides other free software

developers Less of an advantage over competing non-free programs. These disadvantages are

the reason we use the ordinary General Public License for many libraries. However, the

Lesser license provides advantages in certain special circumstances.

For example, on rare occasions, there may be a special need to encourage the widest

possible use of a certain library, so that it becomes a de-facto standard. To achieve this,

non-free programs must be allowed to use the library. A more frequent case is that a free

library does the same job as widely used non-free libraries. In this case, there is little to

gain by limiting the free library to free software only, so we use the Lesser General Public

License.

In other cases, permission to use a particular library in non-free programs enables a greater

number of people to use a large body of free software. For example, permission to use the GNU

C Library in non-free programs enables many more people to use the whole GNU

operating system, as well as its variant, the GNU/Linux operating system.

Although the Lesser General Public License is Less protective of the users‟ freedom, it

does ensure that the user of a program that is linked with the Library has the freedom and

the wherewithal to run that program using a modified version of the Library.

The precise terms and conditions for copying, distribution and modification follow.

Pay close attention to the difference between a “work based on the library” and a “work

that uses the library”. The former contains code derived from the library, whereas the latter

must be combined with the library in order to run.



TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND

MODIFICATION

0) This License Agreement applies to any software library or other program which

contains a notice placed by the copyright holder or other authorized party saying it

may be distributed under the terms of this Lesser General Public License (also called “this

License”). Each licensee is addressed as “you”.

A “library” means a collection of software functions and/or data prepared so as to be

conveniently linked with application programs (which use some of those functions and data)

to form executables.

The “Library”, below, refers to any such software library or work which has been

distributed under these terms. A “work based on the Library” means either the Library

or any derivative work under copyright law: that is to say, a work containing the Library or a

portion of it, either verbatim or with modifications and/or translated straightforwardly into

another language. (Hereinafter, translation is included without limitation in the term

“modification”.)

“Source code” for a work means the preferred form of the work for making

modifications to it. For a library, complete source code means all the source code for

all modules it contains, plus any associated interface definition files, plus the scripts

used to control compilation and installation of the library.

Activities other than copying, distribution and modification are not covered by this

License; they are outside its scope. The act of running a program using the Library is

not restricted, and output from such a program is covered only if its contents constitute

a work based on the Library (independent of the use of the Library in a tool for writing

it). Whether that is true depends on what the Library does and what the program that

uses the Library does.

1) You may copy and distribute verbatim copies of the Library‟s complete source code as

you receive it, in any medium, provided that you conspicuously and appropriately

publish on each copy an appropriate copyright notice and disclaimer of warranty; keep

intact all the notices that refer to this License and to the absence of any warranty; and

distribute a copy of this License along with the Library.

You may charge a fee for the physical act of transferring a copy, and you may at your

option offer warranty protection in exchange for a fee.

2) You may modify your copy or copies of the Library or any portion of it, thus forming a work

based on the Library, and copy and distribute such modifications or work under the

terms of Section 1 above, provided that you also meet all of these conditions:

a) The modified work must itself be a software library.

b) You must cause the files modified to carry prominent notices stating that you

changed the files and the date of any change.

c) You must cause the whole of the work to be licensed at no charge to all third

parties under the terms of this License.



d) If a facility in the modified Library refers to a function or a table of data to be

supplied by an application program that uses the facility, other than as an

argument passed when the facility is invoked, then you must make a good faith

effort to ensure that, in the event an application does not supply such function or

table, the facility still operates, and performs whatever part of its purpose remains

meaningful. (For example, a function in a library to compute square roots has a

purpose that is entirely well-defined independent of the application.

Therefore, Subsection 2d requires that any application-supplied function or table

used by this function must be optional: if the application does not supply it, the

square root function must still compute square roots.) These requirements apply to the

modified work as a whole. If identifiable sections of that work are not derived

from the Library, and can be reasonably considered independent and separate

works in themselves, then this License, and its terms, do not apply to those

sections when you distribute them as separate works.

But when you distribute the same sections as part of a whole which is a work

based on the Library, the distribution of the whole must be on the terms of this

License, whose permissions for other licensees extend to the entire whole, and

thus to each and every part regardless of who wrote it. Thus, it is not the intent of this

section to claim rights or contest your rights to work written entirely by you;

rather, the intent is to exercise the right to control the distribution of derivative or

collective works based on the Library. In addition, mere aggregation of another

work not based on the Library with the Library (or with a work based on the

Library) on a volume of a storage or distribution medium does not bring the other

work under the scope of this License.

3) You may opt to apply the terms of the ordinary GNU General Public License instead

of this License to a given copy of the Library. To do this, you must alter all the notices

that refer to this License, so that they refer to the ordinary GNU General Public

License, version 2, instead of to this License. (If a newer version than version 2 of the

ordinary GNU General Public License has appeared, then you can specify that version

instead if you wish.) Do not make any other change in these notices. Once this change

is made in a given copy, it is irreversible for that copy, so the ordinary GNU General

Public License applies to all subsequent copies and derivative works made from that

copy.

This option is useful when you wish to copy part of the code of the Library into a

program that is not a library.

4) You may copy and distribute the Library (or a portion or derivative of it, under Section

2) in object code or executable form under the terms of Sections 1 and 2 above

provided that you accompany it with the complete corresponding machine-readable

source code, which must be distributed under the terms of Sections 1 and 2 above on a

medium customarily used for software interchange.

If distribution of object code is made by offering access to copy from a designated

place, then offering equivalent access to copy the source code from the same place

satisfies the requirement to distribute the source code, even though third parties are not

compelled to copy the source along with the object code.



5) A program that contains no derivative of any portion of the Library, but is designed to

work with the Library by being compiled or linked with it, is called a “work that uses

the Library”. Such a work, in isolation, is not a derivative work of the Library, and

therefore falls outside the scope of this License.

However, linking a “work that uses the Library” with the Library creates an executable

that is a derivative of the Library (because it contains portions of the Library), rather

than a “work that uses the library”.

The executable is therefore covered by this License. Section 6 states terms for

distribution of such executables.

When a “work that uses the Library” uses material from a header file that is part of the

Library, the object code for the work may be a derivative work of the Library even

though the source code is not. Whether this is true is especially significant if the work

can be linked without the Library, or if the work is itself a library.

The threshold for this to be true is not precisely defined by law.

If such an object file uses only numerical parameters, data structure layouts and

accessors, and small macros and small inline functions (ten lines or less in length),

then the use of the object file is unrestricted, regardless of whether it is legally a

derivative work. (Executables containing this object code plus portions of the Library will

still fall under Section 6.)

Otherwise, if the work is a derivative of the Library, you may distribute the object

code for the work under the terms of Section 6. Any executables containing that work

also fall under Section 6, whether or not they are linked directly with the Library itself.

6) As an exception to the Sections above, you may also combine or link a “work that uses

the Library” with the Library to produce a work containing portions of the Library, and

distribute that work under terms of your choice, provided that the terms permit modification

of the work for the customer‟s own use and reverse engineering for debugging such

modifications.

You must give prominent notice with each copy of the work that the Library is used in it and

that the Library and its use are covered by this License. You must supply a copy of this

License. If the work during execution displays copyright notices, you must include the

copyright notice for the Library among them, as well as a reference directing the user

to the copy of this License. Also, you must do one of these things:

a) Accompany the work with the complete corresponding machine-readable source code

for the Library including whatever changes were used in the work (which must be

distributed under Sections 1 and 2 above); and, if the work is an executable linked

with the Library, with the complete machine-readable “work that uses the Library”,

as object code and/or source code, so that the user can modify the Library and then

relink to produce a modified executable containing the modified Library.

(It is understood that the user who changes the contents of definitions files in the

Library will not necessarily be able to recompile the application to use the

modified definitions.)



b) Use a suitable shared library mechanism for linking with the Library. A suitable

mechanism is one that (1) uses at run time a copy of the library already present on the

user‟s computer system, rather than copying library functions into the executable,

and (2) will operate properly with a modified version of the library, if the user

installs one, as long as the modified version is interface-compatible with the

version that the work was made with.

c) Accompany the work with a written offer, valid for at least three years, to give the

same user the materials specified in Subsection 6a, above, for a charge no more

than the cost of performing this distribution.

d) If distribution of the work is made by offering access to copy from a designated

place, offer equivalent access to copy the above specified materials from the same

place.

e) Verify that the user has already received a copy of these materials or that you have

already sent this user a copy. For an executable, the required form of the “work

that uses the Library” must include any data and utility programs needed for

reproducing the executable from it. However, as a special exception, the materials

to be distributed need not include anything that is normally distributed

(in either source or binary form) with the major components (compiler, kernel,

and so on) of the operating system on which the executable runs, unless that

component itself accompanies the executable.

It may happen that this requirement contradicts the license restrictions of other

proprietary libraries that do not normally accompany the operating system.

Such a contradiction means you cannot use both them and the Library together in an

executable that you distribute.

7) You may place library facilities that are a work based on the Library side-by-side in a

single library together with other library facilities not covered by this License, and

distribute such a combined library, provided that the separate distribution of the work

based on the Library and of the other library facilities is otherwise permitted, and

provided that you do these two things:

a) Accompany the combined library with a copy of the same work based on the

Library, uncombined with any other library facilities. This must be distributed

under the terms of the Sections above.

b) Give prominent notice with the combined library of the fact that part of it is a

work based on the Library, and explaining where to find the accompanying

uncombined form of the same work.

8) You may not copy, modify, sublicense, link with, or distribute the Library except as

expressly provided under this License. Any attempt otherwise to copy, modify,

sublicense, link with, or distribute the Library is void, and will automatically terminate

your rights under this License. However, parties who have received copies, or rights,

from you under this License will not have their licenses terminated so long as such parties

remain in full compliance.

9) You are not required to accept this License, since you have not signed it.

However, nothing else grants you permission to modify or distribute the Library or its

derivative works. These actions are prohibited by law if you do not accept this License.

Therefore, by modifying or distributing the Library (or any work based on the Library),

you indicate your acceptance of this License to do so, and all its terms and conditions

for copying, distributing or modifying the Library or works based on it.



10) Each time you redistribute the Library (or any work based on the Library), the recipient

automatically receives a license from the original licensor to copy, distribute, link with

or modify the Library subject to these terms and conditions. You may not impose any

further restrictions on the recipients‟ exercise of the rights granted herein. You are not

responsible for enforcing compliance by third parties with this License.

11) If, as a consequence of a court judgment or allegation of patent infringement or for any

other reason (not limited to patent issues), conditions are imposed on you

(whether by court order, agreement or otherwise) that contradict the conditions of this

License, they do not excuse you from the conditions of this License. If you cannot

distribute so as to satisfy simultaneously your obligations under this License and any other

pertinent obligations, then as a consequence you may not distribute the Library at all.

For example, if a patent license would not permit royalty-free redistribution of the

Library by all those who receive copies directly or indirectly through you, then the only

way you could satisfy both it and this License would be to refrain entirely from

distribution of the Library. If any portion of this section is held invalid or

unenforceable under any particular circumstance, the balance of the section is intended

to apply, and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other

property right claims or to contest validity of any such claims; this section has the sole

purpose of protecting the integrity of the free software distribution system which is

implemented by public license practices. Many people have made generous contributions to

the wide range of software distributed through that system in reliance on consistent

application of that system; it is up to the author/donor to decide if he or she is willing to

distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence

of the rest of this License.

12) If the distribution and/or use of the Library is restricted in certain countries either by

patents or by copyrighted interfaces, the original copyright holder who places the

Library under this License may add an explicit geographical distribution limitation

excluding those countries, so that distribution is permitted only in or among countries

not thus excluded. In such case, this License incorporates the limitation as if written in

the body of this License.

13) The Free Software Foundation may publish revised and/or new versions of the Lesser

General Public License from time to time. Such new versions will be similar in spirit to

the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Library specifies a

version number of this License which applies to it and “any later version”, you have the

option of following the terms and conditions either of that version or of any later

version published by the Free Software Foundation. If the Library does not specify a

license version number, you may choose any version ever published by the Free

Software Foundation.



14) If you wish to incorporate parts of the Library into other free programs whose

distribution conditions are incompatible with these, write to the author to ask for

permission. For software which is copyrighted by the Free Software Foundation, write

to the Free Software Foundation; we sometimes make exceptions for this. Our decision

will be guided by the two goals of preserving the free status of all derivatives of our

free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

15) BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO

WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE

LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT

HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY “AS IS”

WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY

IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME

THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

16) IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN

WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO

MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED

ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL,

SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF

THE USE OR INABILITY TO USE THE LIBRARY(INCLUDING BUT NOT

LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR

LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE

LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH

HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF

SUCH DAMAGES.


How to Apply These Terms to Your New Libraries

If you develop a new library, and you want it to be of the greatest possible use to the public,

we recommend making it free software that everyone can redistribute and change.

You can do so by permitting redistribution under these terms (or, alternatively, under the

terms of the ordinary General Public License).

To apply these terms, attach the following notices to the library. It is safest to attach them

to the start of each source file to most effectively convey the exclusion of warranty; and

each file should have at least the “copyright” line and a pointer to where the full notice is

found.



one line to give the library‟s name and an idea of what it does.

Copyright (C) year name of author

This library is free software; you can redistribute it and/or modify it under the terms of the GNU

Lesser General Public License as published by the Free Software Foundation; either version

2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;

without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR

PURPOSE.

See the GNU Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with this

library; if not, write to the Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston,

MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your school, if any, to

sign a “copyright disclaimer” for the library, if necessary. Here is a sample; alter the names:

Yoyodyne, Inc. hereby disclaims all copyright interest in the library „Frob‟ (a library for tweaking

knobs) written by James Random Hacker.

Signature of Ty Coon, 1 April 1990 Ty Coon, President of Vice

That‟s all there is to it!

libsmi license

Copyright (C) 1999-2002 Frank Strauss, Technical University of Braunschweig.

This software is copyrighted by Frank Strauss, the Technical University of Braunschweig,

and other parties. The following terms apply to all files associated with the software unless

explicitly disclaimed in individual files.

The authors hereby grant permission to use, copy, modify, distribute, and license this

software and its documentation for any purpose, provided that existing copyright notices

are retained in all copies and that this notice is included verbatim in any distributions.

No written agreement, license, or royalty fee is required for any of the authorized uses.

Modifications to this software may be copyrighted by their authors and need not follow the

licensing terms described here, provided that the new terms are clearly indicated on the

first page of each file where they apply.



IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY

PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL

DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS

DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS

HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES

OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-

INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN “AS IS” BASIS, AND

THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE

MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

License for PPP

Copyright (C) 1995 Pedro Roque Marques. All rights reserved.



1. Redistributions of source code must retain the above copyright notice, this list of


2. Redistributions in binary form must reproduce the above copyright notice, this list of



3. The names of the authors of this software must not be used to endorse or promote

products derived from this software without prior written permission.

4. Redistributions of any form whatsoever must retain the following acknowledgment:

“This product includes software developed by Pedro Roque Marques

<[email protected]>“

THE AUTHORS OF THIS SOFTWARE DISCLAIM ALL WARRANTIES WITH

REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL THE AUTHORS BE

LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR

ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR

PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER

TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR

PERFORMANCE OF THIS SOFTWARE.



The MIT License

Copyright (C) <year> <copyright holders>

Permission is hereby granted, free of charge, to any person obtaining a copy of this

software and associated documentation files (the “Software”), to deal in the Software

without restriction, including without limitation the rights to use, copy, modify, merge,

publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to

whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or

substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,

EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES

OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT

HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,

WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING

FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR

OTHER DEALINGS IN THE SOFTWARE.

MIT v2 with Ad Clause License

Permission is hereby granted, free of charge, to any person obtaining a copy of this

software and associated documentation files (the “Software”), to deal in the Software

without restriction, including without limitation the rights to use, copy, modify, merge,

publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to

whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or

substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,

EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES

OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR

ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF

CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN

CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN

THE SOFTWARE.

Except as contained in this notice, the names of the authors or their institutions shall not be

used in advertising or otherwise to promote the sale, use or other dealings in this Software

without prior written authorization from the authors.



NTP License

This file is automatically generated from html/copyright.htm

Copyright Notice

[sheepb.jpg] “Clone me,” says Dolly sheepishly

_________________________________________________________________

The following copyright notice applies to all files collectively called the Network Time

Protocol Version 4 Distribution. Unless specifically declared otherwise in an individual file,

this notice applies as if the text was explicitly included in the file.

Copyright (C) David L. Mills 1992-2001

Permission to use, copy, modify, and distribute this software and its documentation for any

purpose and without fee is hereby granted, provided that the above copyright notice appears in

all copies and that both the copyright notice and this permission notice appear in

supporting documentation, and that the name University of Delaware not be used in

advertising or publicity pertaining to distribution of the software without specific, written prior

permission. The University of Delaware makes no representations about the suitability this

software for any purpose. It is provided “as is” without express or implied warranty.

The following individuals contributed in part to the Network Time Protocol Distribution

Version 4 and are acknowledged as authors of this work.

[1]Mark Andrews <[email protected]> Leitch atomic clock controller

[2]Bernd Altmeier <[email protected]> hopf Elektronik serial line and PCI-bus devices

[3]Viraj Bais <[email protected]> and [4]Clayton Kirkwood

<[email protected]> port to WindowsNT 3.5

[5]Michael Barone <michael,[email protected]> GPSVME fixes

[6]Karl Berry <[email protected]> syslog to file option

[7]Greg Brackley <[email protected]> Major rework of WINNT port.

Clean up recvbuf and iosignal code into separate modules.

[8]Marc Brett <[email protected]> Magnavox GPS clock driver

[9]Piete Brooks <[email protected]> MSF clock driver, Trimble PARSE support

[10]Reg Clemens <[email protected]> Oncore driver (Current maintainer)

[11]Steve Clift <[email protected]> OMEGA clock driver

[12]Casey Crellin <[email protected]> vxWorks (Tornado) port and help with target

configuration

[13]Sven Dietrich <[email protected]> Palisade reference clock driver, NT adj.

residuals, integrated Greg's Winnt port.

[14]John A. Dundas III <[email protected]> Apple A/UX port

[15]Torsten Duwe <[email protected]> Linux port

[16]Dennis Ferguson <[email protected]> foundation code for NTP Version 2 as

specified in RFC-1119



[17]Glenn Hollinger <[email protected]> GOES clock driver

[18]Mike Iglesias <[email protected]> DEC Alpha port

[19]Jim Jagielski <[email protected]> A/UX port

[20]Jeff Johnson <[email protected]> massive prototyping overhaul

[21]Hans Lambermont <[email protected]> or

[22]<[email protected]> ntpsweep

[23]Poul-Henning Kamp <[email protected]> Oncore driver(Original author)

[24]Frank Kardel [25]<[email protected]>

PARSE <GENERIC> driver(14 reference clocks), STREAMS modules for PARSE,

support scripts, syslog cleanup

[26]William L. Jones <[email protected]> RS/6000 AIX modifications,

HPUX modifications

[27]Dave Katz <[email protected]> RS/6000 AIX port

[28]Craig Leres <[email protected]> 4.4BSD port, ppsclock, Magnavox GPS clock driver

[29]George Lindholm <[email protected]> SunOS 5.1 port

[30]Louis A. Mamakos <[email protected]> MD5-based authentication

[31]Lars H. Mathiesen <[email protected]> adaptation of foundation code for Version 3 as

specified in RFC-1305

[32]David L. Mills <[email protected]> Version 4 foundation: clock discipline,

authentication, precision kernel; clock drivers: Spectracom, Austron, Arbiter, Heath,

ATOM, ACTS, KSI/Odetics; audio clock drivers: CHU, WWV/H, IRIG

[33]Wolfgang Moeller <[email protected]> VMS port

[34]Jeffrey Mogul <[email protected]> ntptrace utility

[35]Tom Moore <[email protected]> i386 svr4 port

[36]Kamal A Mostafa <[email protected]> SCO OpenServer port

[37]Derek Mulcahy <[email protected]> and [38]Damon Hart-Davis

<[email protected]> ARCRON MSF clock driver

[39]Rainer Pruy <[email protected]> monitoring/trap scripts,

statistics file handling

[40]Dirce Richards <[email protected]> Digital UNIX V4.0 port

[41]Wilfredo Sánchez <[email protected]> added support for NetInfo

[42]Nick Sayer <[email protected]> SunOS streams modules

[43]Jack Sasportas <[email protected]> Saved a Lot of space on the stuff in the

html/pic/ subdirectory

[44]Ray Schnitzler <[email protected]> Unixware1 port

[45]Michael Shields <[email protected]> USNO clock driver

[46]Jeff Steinman <[email protected]> Datum PTS clock driver

[47]Harlan Stenn <[email protected]> GNU automake/autoconfigure makeover, various

other bits(see the ChangeLog)

[48]Kenneth Stone <[email protected]> HP-UX port

[49]Ajit Thyagarajan <[email protected]>IP multicast/anycast support

[50]Tomoaki TSURUOKA <[email protected]>TRAK clock driver

[51]Paul A Vixie <[email protected]> TrueTime GPS driver, generic TrueTime clock driver



[52]Ulrich Windl <[email protected]> corrected and validated HTML

documents according to the HTML DTD

_________________________________________________________________

[53]gif

[54]David L. Mills <[email protected]>

References



















mailto:jagubox.gsfc.nasa.gov





http://www4.informatik.uni-erlangen.de/˜kardel
























mailto:pebbles.jpl.nasa.gov







file://localhost/backroom/ntp-stable/html/index.htm


LICENSE ISSUES

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL

License and the original SSLeay license apply to the toolkit. See below for the actual

license texts. Actually both licenses are BSD-style Open Source licenses. In case of any

license issues related to OpenSSL please contact [email protected].

OpenSSL License

Copyright (C) 1998-2004 The OpenSSL Project. All rights reserved.



1) Redistributions of source code must retain the above copyright notice, this list of


2) Redistributions in binary form must reproduce the above copyright notice, this list of



3) All advertising materials mentioning features or use of this software must display the

following acknowledgment:

“This product includes software developed by the OpenSSL Project for use in the

OpenSSL Toolkit. (http://www.openssl.org/)”

4) The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or

promote products derived from this software without prior written permission. For

written permission, please contact [email protected].

5) Products derived from this software may not be called “OpenSSL” nor may

“OpenSSL” appear in their names without prior written permission of the OpenSSL

Project.



6) Redistributions of any form whatsoever must retain the following acknowledgment:

“This product includes software developed by the OpenSSL Project for use in the

OpenSSL Toolkit (http://www.openssl.org/)”

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS” AND ANY

EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,

THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL

PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,

INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES

(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN

CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR

OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,

EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young

([email protected]). This product includes software written by Tim Hudson

([email protected]).

Original SSLeay License

Copyright (C) 1995-1998 Eric Young ([email protected])


This package is an SSL implementation written by Eric Young ([email protected]).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following

conditions are adheared to. The following conditions apply to all code found in this

distribution, be it the RC4, RSA, lhash, DES, etc. code; not just the SSL code.

The SSL documentation included with this distribution is covered by the same copyright

terms except that the holder is Tim Hudson ([email protected]). Copyright remains Eric

Young‟s, and as such any Copyright notices in the code are not to be removed. If this

package is used in a product, Eric Young should be given attribution as the author of the

parts of the library used.

This can be in the form of a textual message at program startup or in documentation

(online or textual) provided with the package.



1) Redistributions of source code must retain the copyright notice, this list of conditions

and the following disclaimer.

2) Redistributions in binary form must reproduce the above copyright notice, this list of





3) All advertising materials mentioning features or use of this software must display the

following acknowledgement:

“This product includes cryptographic software written by Eric Young

([email protected])”

The word „cryptographic‟ can be left out if the rouines from the library being used are

not cryptographic related:-).

4) If you include any Windows specific code (or a derivative thereof) from the apps

directory (application code) you must include an acknowledgement: “This product

includes software written by Tim Hudson ([email protected])”

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “AS IS” AND ANY EXPRESS OR

IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR

CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER

CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN

ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE

POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publically available version or derivative of this

code cannot be changed. i.e. this code cannot simply be copied and put under another

distribution license [including the GNU Public Licence.]

The zlib/libpng License

Copyright (C) 1995-1998 Jean-loup Gailly and Mark Adler

This software is provided „as-is‟, without any express or implied warranty. In no event will

the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial

applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you

wrote the original software. If you use this software in a product, an acknowledgment in the

product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented

as being the original software.

3. This notice may not be removed or altered from any source distribution.


© SAMSUNG Electronics Co., Ltd. I

ABBREVIATION

A AAA Authentication, Authorization and Accounting

ACL Access Control List

ADC Analog to Digital Converter

AKA Authentication and Key Agreement

ANR Automatic Neighbor Relation

ARQ Automatic Repeat Request

AWS Advanced Wireless Services

B BCCH Broadcast Control Channel

BSP Board Support Package

C CGF Charging Gateway Functionality

CLI Command Line Interface

CM Configuration Management

CMAS Commercial Mobile Alert System

CN Core Network

CPLD Complex Programmable Logic Device

CPRI Common Public Radio Interface

CPS Call Processing Software

CS Chipselect

D DAC Digital to Analog Converter

DD Device Driver

DHCP Dynamic Host Configuration Protocol

DNS Domain Name Service


© SAMSUNG Electronics Co., Ltd. II

E ECCB eNB Call Control Block

ECCM eNB Call Control Module

ECMB eNB Common Management Block

ECMM eNB Common Management Module

EHCM eNB Handover call Control Module

EIR Equipment Identity Register

EMS Element Management System

EMTS Element Maintenance Terminal Server

eNB EUTRAN NodeB

EPC Evolved Packet Core

EPS Evolved Packet System

ERCM eNB cell Resource Control Module

ERRM eNB Radio Resource control Module

ESCM eNB System information Control Module

ETWS Earthquake and Tsunami Warning System

EUTRA Evolved-Universal Terrestrial Radio Access

EUTRAN Evolved-Universal Terrestrial Radio Access Network

F FM Fault Management

FTP File Transfer Protocol

G GERAN GSM EDGE Radio Access Network

GPRS General Packet Radio Service

GTP GPRS Tunneling Protocol

GTPB GTP Block

GTP-U GPRS Tunneling Protocol-User

GW Gateway

H HA High Availability

HARQ Hybrid Automatic Repeat Request

HSS Home Subscriber Server

HTTP Hypertext Transfer Protocol

I IPC Inter Process Communication

IPRS IP Routing Subsystem

IPSec IP Security


© SAMSUNG Electronics Co., Ltd. III

L LAG Link Aggregation

LKC Linux Kernel Core

LOG Log Management

LSM LTE System Manager

LSS LTE SON server

LTE Long Term Evolution

M MAC Medium Access Control

MACB MAC Block

MBMS Multimedia Broadcast Multicast Service

MIB Management Information Base

MIF Management Interface

MIMO Multiple Input Multiple Output

MME Mobility Management Entity

MS Mobile Station

MW Middleware

N NAS Non Access Stratum

NP Network Processing

O OAM Operation and Maintenance

OCS Online Charging System

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OS Operating System

P PCCH Paging Control Channel

PCEF Policy and Charging Enforcement Function

PCRF Policy Charging & Rule Function

PDCB PDCP Block

PDCP Packet Data Convergence Protocol

PDN Packet Data Network

PDSCH Physical Downlink shared Channel

PDU Protocol Data Unit

PHICH Physical Hybrid ARQ indicator Channel

P-GW PDN GW

PM Performance Management

PMIP Proxy Mobile IP

PRACH Physical Random Access Channel

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel


© SAMSUNG Electronics Co., Ltd. IV

Q QAM Quadrature Amplitude Modulation

QoS Quality of Service

R RA Random Access

RACH Random Access Channel

RLC Radio Link Control

RLCB RLC Block

RRC Radio Resource Control

S SC-FDMA Single Carrier-Frequency Division Multiple Access

SCTP Stream Control Transmission Protocol

SDMA Spatial Domain Multiple Access

SDU Service Data Unit

SFN System Fame Number

SFTP Secure FTP

SGSN Serving GPRS Support Node

S-GW Serving GW

SIB System Information Block

SM Security Management

SNMP Simple Network Management Protocol

SOAP Simple Object Access Protocol

SSL Secure Socket Layer

SwM Software Management

T TL1 Transaction Language 1

TM Test Management

TRM Trace Management

U UCCM Universal Core Clock Module

UDA User-Defined Alarm

UDP User Datagram Protocol

UE User Equipment

UTRAN UMTS Terrestrial Radio Access Network

UDA User-Defined Alarm

V VLAN Virtual LAN

410 MMBS

Operation Manual

©2011~2012 Samsung Electronics Co., Ltd.


Information in this manual is proprietary to SAMSUNG

Electronics Co., Ltd.

No information contained here may be copied, translated,

transcribed or duplicated by any form without the prior written

consent of SAMSUNG.

Information in this manual is subject to change without notice.

410-mmbs-operation-manual_v1.1.pdf

Documents

lte enb system

lte enb alarms

system improvement

console screen

special information

additional information

loading function

main content