ZTE LTE FDD Connection Management Feature Guide

ZTE LTE FDD Connection
Management Feature Guide

LR14
ZTE LTE FDD Connection Management Feature

Guide
Version
V1.0
Date
2013-7-14
Author
Fu Ang
Wu Hao
Reviewer
Zhang Fan
Notes
The first edition
1.
Modify the document structure, and

the old third chapter is divided into
two parts ( Technical description and
V 2.0
2014-06-27
Fu Ang
Zhang Fan
Technical Details).
2.
Add the sixth chapter.
3.
Add the EIA3 and EEA3 security
algorithms description.
Add Chapter 4.3.5 Context Fetch
V3.0
2014-11-24
Fu Ang
Zhang Fan
Change the word template

Enrich Chapter 1.4
2015 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed
or used without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is
subjected to change without notice.
ZTE LTE FDD Connection Management Feature Guide
TABLE OF CONTENTS
1
1.1
1.2
1.3
1.4
Introduction ....................................................................................................... 1
Scope .................................................................................................................. 1
Target Group ....................................................................................................... 1
Feature Attribute .................................................................................................. 1
Correlation with Other Features ........................................................................... 2
2
2.1
Terminology....................................................................................................... 3
Definitions ............................................................................................................ 3
3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
Technical Description ....................................................................................... 4

Feature Description ............................................................................................. 4
Protocol Stacks .................................................................................................... 7
C-Plane Connections ........................................................................................... 8
U-Plane Connection ............................................................................................. 9
Connection Release ...........................................................................................10
4
4.1
4.1.1
4.2
4.2.1
4.2.2
4.3
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.4
4.5
4.5.1
4.5.2
4.5.3
4.6
4.7
4.7.1
4.7.2
4.7.3
4.7.4
4.8
4.8.1
4.8.2
Technical Details ..............................................................................................10

System Information Broadcasting .......................................................................10
System Information Architecture .........................................................................10
Paging ................................................................................................................14
Paging Initiated by the MME ...............................................................................15
Paging Initiated by the eNodeB...........................................................................16
RRC Connection Management ...........................................................................16
RRC Connection Establishment..........................................................................16
RRC Connection Reconfiguration .......................................................................18
RRC Connection Reestablishment......................................................................22
RRC Connection Release ...................................................................................23
Context Fetch .....................................................................................................24
NAS Signaling Transmission...............................................................................27
UE Context Management ....................................................................................28
Initial UE Context Setup ......................................................................................28
UE Context Release ...........................................................................................29
UE Context Modification .....................................................................................32
UE Capability Enquiry .........................................................................................33
E-RAB Management ...........................................................................................33
E-RAB Setup ......................................................................................................34
E-RAB Modification .............................................................................................36
E-RAB Release...................................................................................................37
Radio Bearer Combination ..................................................................................38
AS Security Management ...................................................................................39
Integrity Protection ..............................................................................................39
Ciphering ............................................................................................................40
ZTE Confidential Proprietary
2015 ZTE CORPORATION. All rights reserved.
4.9
4.9.1
4.9.2
4.9.3
4.9.4
4.9.5
4.9.6
4.10
4.10.1
4.10.2
4.10.3
4.10.4
4.10.5
4.10.6
S1 Interface Management ...................................................................................41

Error Indication ...................................................................................................42
Reset ..................................................................................................................43
S1 Establishment ................................................................................................43
Configuration Update ..........................................................................................44
Overload Indication .............................................................................................44
S1 Flex ...............................................................................................................45
X2 Interface Management ...................................................................................47
Load Indication ...................................................................................................48
Error Indication ...................................................................................................49
X2 Setup .............................................................................................................49
Reset ..................................................................................................................49
eNodeB Configuration Update ............................................................................50
Resource Status Report......................................................................................50
5
5.1
5.2
5.3
5.3.1
5.3.2
5.3.3
5.3.4
5.3.5
5.3.6
5.3.7
5.3.8
5.3.9
5.3.10
Key Parameters and Configuration .................................................................51

Parameter List ....................................................................................................51
Parameter configuration Rule .............................................................................52
Parameter Configuration Procedure....................................................................60
System Information Broadcast Parameters .........................................................60
Paging Parameters .............................................................................................64
ERAB Parameters ..............................................................................................64
Encryption Parameters .......................................................................................65
S1 Parameters ....................................................................................................66
S1-Flex Parameters ............................................................................................67
X2 Parameters ....................................................................................................67
The Other Related Parameters Configuration .....................................................68
Deactivate feature...............................................................................................69
Data Save and Synchronization ..........................................................................70
6
6.1
6.1.1
6.1.2
6.1.3
6.2
6.2.1
6.2.2
6.2.3
6.3
6.3.1
6.3.2
6.3.3
6.4
6.4.1
Feature Validation ............................................................................................70

System Information Broadcasting Test ...............................................................70
Topology .............................................................................................................70
Test Specification ...............................................................................................71
Test Result .........................................................................................................72
Paging Test ........................................................................................................74
Topology .............................................................................................................74
Test Result .........................................................................................................76
E-RAB Test.........................................................................................................76
Topology .............................................................................................................76
Test Result .........................................................................................................79
AS Security Management Test ...........................................................................81
Topology .............................................................................................................81
4
6.4.2
6.4.3
6.5
6.5.1
6.5.2
6.5.3
6.6
6.6.1
6.6.2
6.6.3

Test Result .........................................................................................................83
S1 Interface Test ................................................................................................89
Topology .............................................................................................................89
Test Result .........................................................................................................91
X2 Interface Test..............................................................................................101
Topology ...........................................................................................................101
Test Specification .............................................................................................102
Test Result .......................................................................................................103
7
7.1
7.2
7.3
Related Counters, KPI and Alarms ...............................................................109

Related Counters ..............................................................................................109
Related KPI ......................................................................................................117
Related Alarms .................................................................................................118
Impact on Network .........................................................................................118
Abbreviations .................................................................................................118
10
10.1
10.1.1
10.1.2
10.1.3
10.1.4
10.1.5
10.1.6
10.1.7
10.1.8
10.1.9
Appendix .........................................................................................................118
Cell Definitions of System Information Broadcast..............................................118
MasterInformationBlock ....................................................................................118
SystemInformationBlockType1 .........................................................................119
FIGURES
Figure 3-1 Sequence Diagram of the eNodeB Connection Management ................ 5
Figure 3-2 Control-Plane (C-Plane) Protocol Stacks on the Uu and S1 Interfaces .. 7
Figure 3-3 User-Plane (U-Plane) Protocol Stacks on the Uu and S1 Interfaces ...... 8
Figure 3-4 Control-Plane Protocol Stack on the X2 Interface .................................. 8
Figure 3-5 User-Plane Protocol Stack on the X2 Interface ...................................... 8
Figure 4-1 System Information Architecture .......................................................... 11
Figure 4-2 Sequence Diagram of UE Receiving System Information Broadcast ... 11
Figure 4-3 System Information Update ................................................................. 14
Figure 4-4 Paging ................................................................................................. 15
Figure 4-5 RRC Connection Establishment Procedure ......................................... 17
Figure 4-6 RRC Connection Reconfiguration Triggered by a Radio Resource
Request................................................................................................................... 19
Figure 4-7 RRC Connection Reconfiguration Including Mobility Control Information
................................................................................................................................ 21
Figure 4-8 RRC Connection Reestablishment Procedure ..................................... 22
Figure 4-9 RRC Connection Release .................................................................... 24
Figure 4-10 Initial UE Context Setup ..................................................................... 28
Figure 4-11 eNodeB Triggered UE Context Release ............................................ 30
Figure 4-12 MME Triggered UE Context Release ................................................. 31
Figure 4-13 UE Context Modification Procedure ................................................... 32
Figure 4-14 E-RAB With QCI Diagram .................................................................. 34
Figure 4-15 E-RAB Setup Procedure .................................................................... 35
Figure 4-16 E-RAB Modification Procedure .......................................................... 36
Figure 4-17 eNodeB Triggered E-RAB Release.................................................... 37
Figure 4-18 MME Triggered E-RAB Release ........................................................ 38
Figure 4-19 S1 Interface ....................................................................................... 42
Figure 4-20 S1-Flex .............................................................................................. 46
Figure 4-21 S1-Flex Example ............................................................................... 47
Figure 4-22 X2 Interface ....................................................................................... 48
Figure 5-1
SI Scheduling Information Configuration-1 ......................................... 60
Figure 5-2 SI Scheduling Information Configuration-2........................................... 61

Figure 5-3
EUTRAN Inter-Frequency Configuration .......................................... 62
Figure 5-4 UTRAN Frequency Configuration ........................................................ 62

Figure 5-5 GERAN Frequency Configuration ........................................................ 63
Figure 5-6
CDMA Frequency Configuration ........................................................ 63
Figure 5-7 Paging Related Parameter Configuration............................................. 64

Figure 5-8
Bearer Parameter Configuration ........................................................ 65
Figure 5-9 Encryption Parameter Configuration .................................................... 65

Figure 5-10 S1 SCTP Configuration ..................................................................... 66
Figure 5-11 S1AP Configuration ........................................................................... 66
Figure 5-12 Setting MME Load Balancing Switch ................................................. 67
Figure 5-13
X2 SCTP Configuration .................................................................... 68
Figure 5-14 X2AP Configuration ........................................................................... 68

Figure 5-15 UE Supported RAT Configuration ...................................................... 69
Figure 6-1 Topology for One Single eNodeB ........................................................ 71
Figure 6-2 MIB ...................................................................................................... 73
Figure 6-3 SIB1 .................................................................................................... 73
Figure 6-4 SIB2 .................................................................................................... 73
Figure 6-5 SIB3 .................................................................................................... 74
Figure 6-6 UE received Paging message .............................................................. 76
Figure 6-7 E-RAB Setup Process ......................................................................... 80
Figure 6-8 E-RAB Modify Process ........................................................................ 80
Figure 6-9 E-RAB Release Process ...................................................................... 80
Figure 6-10 The Integrity Protection Algorithm is EIA0 .......................................... 84
Figure 6-13 The Encryption Algorithm is EIA0 ...................................................... 87
Figure 6-16 Error Indication Message ................................................................... 92
Figure 6-17 S1 Setup Request message .............................................................. 92
Figure 6-18 S1 Setup Response message ........................................................... 93
Figure 6-19 Reset message.................................................................................. 94

Figure 6-20 Reset Acknowledge message ............................................................ 95
Figure 6-21 eNodeB Configuration Update message ............................................ 96
Figure 6-22 eNodeB Configuration Update Acknowledge message ...................... 97
Figure 6-23 MME Configuration Update message ................................................ 98
Figure 6-24 MME Configuration Update Acknowledge message .......................... 99
Figure 6-25 Overload Start message .................................................................. 100
Figure 6-26 Overload Stop message .................................................................. 101
Figure 6-27 X2 Interface Test Topology .............................................................. 102
Figure 6-28 X2 Setup Request Message ............................................................ 104
Figure 6-29 X2 Setup Response Message ......................................................... 104
Figure 6-30 Reset Request Message ................................................................. 105
Figure 6-31 Reset Response Message ............................................................... 105
Figure 6-32 Load Indication Information.............................................................. 106
Figure 6-33 X2AP: eNB Configuration Update Message ..................................... 107
Figure 6-34 X2AP: eNB Configuration Update Acknowledge Message ............... 107
Figure 6-35 Resource Status Request Message ................................................... 108
Figure 6-36 Resource Status Response Message .............................................. 108
Figure 6-37 Resource Status Reporting Message............................................... 109
TABLES
Table 1-1 Correlation with Other Features .............................................................. 2
Table 4-1 System Information Content Architecture .............................................. 12
Table 4-2 LTE Integrity Algorithms........................................................................ 40
Table 4-3 LTE Ciphering Algorithms ..................................................................... 41
Table 5-1 Parameters List..................................................................................... 51
Table 5-2 Configuration rule of parameters ........................................................... 52
Table 6-1 Test Equipment..................................................................................... 71
Table 6-2 System Information Broadcasting Test ................................................. 71
Table 6-3 Paging Test .......................................................................................... 74

Table 6-4 E-RAB Test........................................................................................... 76
Table 6-5 AS Security Management Test ............................................................. 81
Table 6-6 S1 Interface Test .................................................................................. 89
Table 6-7 X2 Interface Test Requirements ......................................................... 102
Table 6-8 X2 Interface Test ................................................................................ 102
Table 7-1 Related Counters ................................................................................ 109
Table 7-2
Related KPI ....................................................................................... 117
Introduction
1.1
Scope
This document describes the FDD connection management feature or technology
applied to the eNodeB in an LTE network, including the basic principle, algorithm flows,
performance gains, application scenarios, background key parameters and configuration
guide, related counters, KPI statistics, and alarms.
The design of the eNodeB (radio access network device) follows the basic principle of
logical separation of the signaling and data transport. In the detail implementation, it is
divided into two logical functional frameworks, control plane and user plane. For the
corresponding function protocol frameworks, refer to Chapter 3, Technical Description. In
this document, the eNodeB connection management function includes the connection
management on the control plane and the user plane, for example, radio resource
connection management, S1 interface connection management, and X2 interface
connection management. The RRC protocol layer, S1 application protocol, and X2
application protocol are involved.
1.2
Target Group
This document is intended for:
1.3
Personnel who need to understand FDD Connection Management function
Personnel who work with ZTE products
Feature Attribute
For FDD single-mode eNodeB V3.20.50.20 series:

OMMB version: V12.13.58
ZTE Confidential & Proprietary
EMS version: V12.13.58
For GUL multi-mode eNodeB V4.13.15 series:

OMMB version: V12.13.52
EMS version: V12.13.51
Note:
FDD single-mode V3.20.50.20 corresponds to GUL multi-mode V4.13.15, and LTE
technology description and operation requirements in the corresponding versions are the
same.
Involved NEs:
UE
eNodeB
MME
S-GW
BSC/RNC
SGSN
-
P-GW
-
HSS
-
Note:
*-: Not involved
*: involved
1.4
Correlation with Other Features

Table 1-1
Correlation with Other Features
Feature
Feature Name
ID
Required
Mutually
Affected
Feature
Exclusive
Feature
Feature
ZLF31-06-001
System Information
None
None
None
Broadcasting
ZLF31-06-002
Paging
None
None
None
ZLF31-06-003
RRC Connection
None
None
None
None
None
None
Management
ZLF31-06-004
NAS Signaling
Transfer
Feature
Feature Name
ID
Required
Mutually
Affected
Feature
Exclusive
Feature
Feature
ZLF31-06-005
UE Context
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
ZLF31-06-003
None
None
None
None
Management
ZLF31-06-006
UE Capability
Enquiry
ZLF31-06-007
Radio Access
Bearer Management
ZLF31-06-008
S1 Interface
Management
ZLF31-06-009
X2 Interface
Management
ZLF31-06-011
Context Fetch
RRC
Connection
Management
ZLF31-06-013
MFBI
Terminology
2.1
Definitions
None
E-RAB:
An E-RAB uniquely identifies an S1 bearer and the corresponding Data Radio
Bearer. When an E-RAB is set up, there is a one-to-one mapping relationship
between this E-RAB and an EPS bearer of the Non Access Stratum (NAS).
RRC:
Radio Resource Control protocol, including broadcast of system information, RRC
connection control, measurement control, and mobility procedure functions.
SRB:
A Signaling Radio Bearer (SRB) is a radio bearer that carries RRC or NAS protocol
messages. More specifically, three SRBs are defined: SRB0, SRB1, and SRB2.
Where, SRB0 is used for transmitting signaling messages over the CCCH logical
channel, SRB1 is used for transmitting RRC messages and NAS messages (before
the establishment of SRB2) over the DCCH logical channel, and SRB2 is used for
transmitting NAS messages.
Default Bearer:
To reduce the service setup delay and realize "always online" for users, as a part of
the flow in which a UE is connected to the network, the core network by default
allocates an IP address to the UE and establishes at least one E-RAB as the default
bearer. The default bearer is always in established status throughout the PDN
connection procedure.
Technical Description
3.1
Feature Description
This document describes the common LTE service process to cover the main application
scenarios of each function.
Figure 3-1
Sequence Diagram of the eNodeB Connection Management
UE
eNodeB1
MME
eNodeB2
System Information Broadcasting

Paging
RRC Connection Establishment

NAS Message Transfer (Including Authentication)
Initial Context Setup (Default EPS Bearer Context Establishment)
E-RAB Setup
Active Phase
E-RAB Release
X2 Handover
S1 Context Release (UE Context Release)
1.
A UE selects and resides in an LTE cell. The UE receives the system information
broadcast of the serving cell, and monitors paging messages.
By receiving the broadcast of system information provided by the serving cell, the
UE obtains mandatory information for establishing a connection to the network,
including radio parameter information, NAS information (such as the tracking
area code of the serving cell), and the cell reselection measurement control
information. For details, refer to section 4.1.
The UE monitors paging messages to detect system information changes for
receiving new broadcast information, or detect a called notification for initiating a
network connection. For details, refer to section 4.2.
2.
If the UE requires to use some services (for example, browsing the web), the UE
initiates an RRC connection procedure to be connected to the core network and
obtain the data service. For details, refer to section 4.3.
3.
The UE is in RRC_Connected state when the RRC connection has been

established. An NAS connection is established between the UE and the MME for
message interaction. For details, refer to section 4.4. A normal connection between
the eNodeB and the MME over the S1 interface is the basis for the UE to access the
network and obtain services. For the connection management function of the S1
interface, refer to section 4.9.
4.
The MME initiates an initial context setup procedure and a default bearer setup
procedure simultaneously. For details, refer to sections 4.5, 4.6, and 4.8.
5.
If the UE initiates a special service request (for example, video telephone) that the
default bearer cannot meet, the MME triggers a dedicated bearer setup procedure.
For details, refer to section 4.7.
6.
The phase in which the UE continues using network services is called active phase.
7.
The UE terminates the service, and the network initiates a bearer release procedure.
Only the unwanted dedicated bearer is released in this procedure. The default
bearer is still reserved. For details, refer to section 4.7.
8.
Persistent location movement of the UE triggers a handover procedure based on

the X2 interface. The UE is handed over to a cell of an adjacent eNodeB. The
connection between two adjacent eNodeBs over the X2 interface is the basis of the
information interaction between them, for example, X2 handover support, load
balance, and inter-cell interference suppression/coordination. For the X2 interface

connection management function, refer to section 4.10.
9.
If the UE has no service request (for example, the user inactivity timer expires), the
network initiates a UE context release procedure to save network resources. The
UE enters the RRC_IDLE state. For details, refer to section 4.5.
3.1.1
Protocol Stacks
This section describes the protocol stacks involved in the connection management
function.
The following figure shows the protocol stacks of the control plane between the UE and
the MME. For the Uu interface, the RRC, PDCP, RLC, MAC, and PHY protocols form the
access stratum, while the NAS protocol belongs to the non-access stratum. Where, in the
access stratum, the RRC protocol establishes radio bearers and configures all
RRC-controlled lower-layers between the eNodeB and the UE. Reliable transmission of
the signaling messages between the eNodeB and the MME is implemented based on the
SCTP protocol.
Figure 3-2
Control-Plane (C-Plane) Protocol Stacks on the Uu and S1 Interfaces
UE
eNodeB
MME
NAS
NAS
RRC
RRC
S1-AP
S1-AP
PDCP
RLC
MAC
RLC
PDCP
RLC
MAC
RLC
SCTP
IP
SCTP
IP
MAC
PHY
L2
PHY
PHY
L1
MAC
PHY
PHY
Uu Signalling
(SRB)
Uu
L2
PHY
S1 Signalling
L1
S1-MME
The IP packet of the UE is encapsulated in the specified protocol of the EPC, and is
transmitted between the S-GW and the eNodeB by using the GTP tunnel protocol. The
following figure shows the user-plane protocol stacks.
Figure 3-3
User-Plane (U-Plane) Protocol Stacks on the Uu and S1 Interfaces
UE
eNodeB
S-GW
IP App.
PDCP
RLC
MAC
RLC
MAC
PHY
Uu User Data
(DRB)
PHY
PDCP
RLC
MAC
RLC
GTPU
UDP/IP
MAC
PHY
L2
PHY
PHY
L1
GTPU
UDP/IP
L2
PHY
S1 User Data
L1
S1-U
Uu
The X2 interface between two eNodeBs is also divided into the control plane and the
user plane, support signaling interaction and data interaction respectively.
Figure 3-4
Control-Plane Protocol Stack on the X2 Interface
eNodeB1
eNodeB2
X2-AP
X2-AP
SCTP
IP
SCTP
IP
L2
PHY
L2
PHY
L1
X2 Signalling
L1
X2
Figure 3-5
User-Plane Protocol Stack on the X2 Interface
eNodeB1
eNodeB2
GTPU
UDP/IP
GTPU
UDP/IP
L2
PHY
L2
PHY
L1
X2 User Data
L1
X2
3.1.2
C-Plane Connections
A signaling connection may be triggered by a UE or a network (eNodeB or EPC).
If the signaling connection is triggered by the UE, the UE requests to establish an RRC
connection to the eNodeB. Once the RRC connection is established, the eNodeB selects
a suitable MME and sends the NAS message that the UE needs to send to the core
network to the MME.
The S1 Application Protocol (S1AP) defines the functional procedure between the
eNodeB and the EPC. The functions include the E-RAB management function (E-RAB
establishment, modification, and release), UE context management function (initial UE
context establishment, UE context modification and release), paging function, NAS
signaling transfer function (the eNodeB transparently transfers NAS messages between
the UE and the EPC), mobility function (intra-LTE S1 handover and inter-RAT mobility),
and S1 interface management function.
The X2 Application Protocol (X2AP) defines the functional procedure between eNodeBs.
The functions include the mobility management function (intra-LTE X2 handover) and X2
interface management function.
If the signaling connection is triggered by the network, the eNodeB sends a paging
message to the UE. After that, the connection procedure is the same as the procedure
triggered by the UE.
3.1.3
U-Plane Connection
After a new RRC connection is established, the MME selects an S-GW based on the
S-GW function, and initiates the default bearer establishment procedure. During the
procedure, the eNodeB starts security protection for user data on the Uu interface.
The default bearer exists throughout the lifecycle of the connection between the UE and
the PDN, making users feels that they are always online. Other bearers established
between the UE and the PDN are called dedicated bearers.
The initial QoS parameter values of the default bearer are assigned by the network,
based on subscription data.
Dedicated bearers may be GBR or Non-GBR bearers,
while the default bearer must be a Non-GBR bearer.

A downlink data stream and an uplink data stream may be established on the X2
interface for each E-RAB of the UE for user data forwarding during a handover
procedure.
3.1.4
Connection Release
The connection release may be triggered by an eNodeB or an MME. The connection
release includes UE-dedicated logical connection release on the S1/X2 interface,
related-resource release in the eNodeB, and RRC connection release.
Technical Details
4.1
System Information Broadcasting

The eNodeB is responsible for creating and broadcasting system information to UEs in a
cell that are in RRC_IDLE or RRC_CONNECTED. The UEs can get the basic cell
properties (bandwidth, PCI, and access barring), radio resource common configuration,
NAS information (Tracking Area Code of the cell), and cell reselection information by
receiving system information. System information is broadcasted periodically. When a
parameter in the system information is changed, all UEs in the cell are notified by a
paging message.
4.1.1
System Information Architecture

System information is divided into the Master Information Block (MIB) and a number of
System Information Blocks (SIBs). Each SIB contains one type of information.
The MIB includes a limited number of most essential and most frequently transmitted
parameters that are needed to acquire other information from the cell. The MIB is
transmitted on BCH. The MIB uses a fixed schedule with a periodicity of 40 ms and
repetitions made on each radio frame within 40ms.
SIBs other than SystemInformationBlockType1 are carried in System Information (SI)
messages and mapping of SIBs to SI messages is flexibly configurable by eNodeB
policies. The following figure shows the system information architecture.
10
Figure 4-1
System Information Architecture

Master
Information
Block
System
Information
Block 1
System
Information
Block 2
System
Information
Block 3
...
System
Information
Block N
SIB1 consists of the basic cell properties (such as PCI and supported operator list) and
SI message scheduling information. First, the UE receives the SIB1 message. After the
SI message scheduling information is acquired, the UE receives all the SI messages in
sequence, and acquires all SIB information from the SI messages. The SIB1 message
and all SI messages are transmitted on DL-SCH. The SIB1 uses a schedule with a
periodicity of 80 ms and repetitions made on every two radio frames within 80ms. The
transmission periodicity of SI messages is flexibly configured on the OMMB. The
following figure shows how the UE receives system information broadcast.
Figure 4-2
Sequence Diagram of UE Receiving System Information Broadcast
eNodeB
UE
MME
System Information
Broadcast
Scheduler
Master Information Block, BCH

System Information Block Type 1, DL-SCH
Get Scheduling
Information of SI
System Information, DL-SCH
UE
eNodeB
MME
11
SIB2 consists of the common radio configuration in a cell. The UE must acquire SIB2
before initiating an access to the cell. SIB3 through SIB8 consist of cell reselection
configurations. SIB10 through SIB11 consist of Earthquake and Tsunami Warning
System (ETWS) information. SIB12 consists of Commercial Mobile Alert Service (CMAS)
information.
ZTE eNodeB supports MIB, SIB1SIB8, and SIB10SIB12.
Table 4-1
System Information Content Architecture
Contents
MIB
SIB1
System Information Block Type N

2
Downlink
Bandwidth
PHICH
Configuration
System Frame
Number
Cell Access
Parameters
SIB Scheduling
Information
10
11
12
13
Common
Radio
Configuration
Information
Common Cell
Reselection
Information
Intra-frequency
Neighboring
Cell
Information
Inter-frequency
Cell
Reselection
Parameters
12
Contents
MIB
SIB1
System Information Block Type N

2
10
11
12
13
Inter-frequency
Neighboring
Cell
Information
Cell
Reselection
Information
(UTRA)
Cell
Reselection
Information
(GERAN)
Cell
Reselection
Information
(CDMA2000)
Name of Home
eNodeB
ETWS primary
notification
ETWS
secondary
notification
CMAS
notification
MBMS
configuration
13
Figure 4-3
System Information Update
Change notification
Updated information
BCCH modification period (n)
BCCH modification period (n+1)
If the SI message is modified, the eNodeB updates IE systemInfoValueTag in SIB1

accordingly for instructing the UE whether the SI message is changed. The eNodeB may
not update IE systemInfoValueTag in SIB1 upon change of some system information,
including ETWS, CMAS, and regularly changing information (for example, CDMA 2000
system time in SIB8).
The UE verifies whether the received system information remains valid by either
checking IE systemInfoValueTag in SIB1 after the modification period boundary, or
monitoring paging messages. The system information stored by the UE is valid only in a
maximum of three hours since the information is received. After the validity period
expires, the UE receives the broadcasted system information again even if it does not
receive the system information update notification.
4.2
Paging
A paging procedure may be initiated by an MME or an eNodeB. The MME uses this
function to page a UE in RRC_IDLE. As a response, the UE may initiate RRC connection
establishment, for example, to receive an incoming call. The eNodeB notifies the UEs in
RRC_IDLE orRRC_CONNECTED about system information update by sending a paging
message.
14
Figure 4-4
Paging
eNode
B
UE
eNodeB
initiated
MME
System Information
Changed and/or
ETWS Notification
Needed
Paging, PCCH
System Information Broadcasting Procedure
S1-AP: Paging
MME initiated
Determine cells in
which Paging
message should be
sent
Paging, PCCH
RRC Connection Establishment Procedure
UE
4.2.1
eNode
B
MME
Paging Initiated by the MME

The paging procedure initiated by the MME is described as follows:
The MME sends a paging message to the eNodeB to page the UE in one or multiple
Tracking Areas (TAs). The paging message contains the paging ID, paging DRX, and TA
list.
The eNodeB generates a paging message on the Uu interface based on the received
paging message from the MME.
The eNodeB sends the paging message at the UEs paging occasion in the cells in the
TA list specified by the MME.
15
4.2.2
Paging Initiated by the eNodeB

The paging procedure initiated by the eNodeB is described as follows:
If system information is modified (for example, maintenance personnel modifies
parameters on the OMC), the eNodeB generates a paging message on the Uu interface
and sets IE systemInfoModification and IE etws-Indication based on modified system
information.
The eNodeB sends the paging message based on the system information update period.
4.3
RRC Connection Management
4.3.1
RRC Connection Establishment

The RRC connection is the dedicated connection on the layer 3 protocol between the UE
and eNodeB. The purpose of this function is to establish an RRC connection between the
UE and eNodeB. The RRC connection consists of SRB1 establishment and initial NAS
information transfer.
If the eNodeB fails to establish an RRC connection, for example, because of resource
limit, it sends an RRC CONNECTION REJECT message to the UE. The UE starts the
T302 timer based on the IE waitTime value in the message, and sends a RRC
connection request again after the timer expires.
16
Figure 4-5
RRC Connection Establishment Procedure
eNode
B
UE
MME
Random Access Procedure
RRC_IDLE
RRC Connection Request, SRB0,

CCCH
Admission Control
RRC Connection Setup, SRB0,
CCCH
RRC Connection Setup Complete,SRB1,
DCCH
RRC_CONNECTE
D
UE
Initial UE Message
eNode
B
MME
The RRC connection establishment procedure is described as follows:

1.
The UE in RRC_IDLE sends an RRC CONNECTION REQUEST message,

including the UE ID and RRC connection establishment cause. If the UE has
already registered in the TA of the current cell, the UE ID is set to S-TMSI.
40
Otherwise, the UE ID is set to a random value in the range 02 -1.

2.
The RRC CONNECTIO REQUEST message using the CCCH logical channel is
sent in transparent mode over SRB0.
3.
Upon receiving the RRC CONNECTION REQUEST message, the eNodeB

allocates radio resources for the UE by using Radio Admission Control (RAC). For
details about RAC, refer to [5].
4.
The eNodeB allocates a Cell Radio Network Temporary Identity (C-RNTI) to the UE
to uniquely identify the UE in the cell. The eNodeB establishes the RRC context for
the UE internally.
5.
After RAC is successful, the eNodeB sends an RRC CONNECTION SETUP

message to the UE, including the dedicated radio resource configuration.
17
6.
Upon receiving the RRC CONNECTION SETUP message, the UE establishes

SRB1 based on the dedicated radio resource configuration in the message. The
RRC state transits to RRC_CONNECTED.
7.
The UE sends an RRC CONNECTION SETUP COMPLETE message using the

DCCH logical channel on SRB1 to the eNodeB. The UE sets the selected PLMN in
the message, namely, the IE selectedPLMN-Identity. Because SRB2 used to carry
NAS information is not established, the UE sends NAS information to the MME
through an RRC CONNECTION SETUP COMPLETE message.
8.
Upon receiving an RRC CONNECTION SETUP COMPLETE message, the eNodeB

selects a suitable MME based on the selected PLMN, and sends an INITIAL UE
MESSAGE to the MME. The message contains the NAS information that is
extracted from the RRC CONNECTION SETUP COMPLETE message by the
eNodeB.
4.3.2
RRC Connection Reconfiguration

The RRC connection reconfiguration procedure is used to modify an established RRC
connection, for example, to establish, modify, or release radio bearers, to establish,
modify, or release measurement s, and perform handover. The eNodeB can also transfer
NAS information to the UE by using this procedure.
4.3.2.1
RRC Connection Reconfiguration Not Including Mobility Control

Information
The eNodeB initiates this procedure in the following scenarios:
to establish, modify, or release radio bearers,
to establish, modify, or release measurement configuration.
The triggering conditions are listed as follows:

1.
Upon receiving an INITIAL CONTEXT SETUP REQUEST message from the MME,
the eNodeB establishes a radio bearer.
18
2.
Upon receiving an E-RAB SETUP REQUEST message from the MME, the eNodeB
establishes a radio bearer.
3.
Upon receiving an E-RAB MODIFY REQUEST message from the MME, the
eNodeB modifies the corresponding radio bearer.
4.
Upon receiving an E-RAB RELEASE COMMAND message from the MME, the
eNodeB releases the corresponding radio bearer.
Figure 4-6
RRC Connection Reconfiguration Triggered by a Radio Resource Request
eNode
B
UE
RRC_CONNECTE
D
MME
S1 signaling message REQUEST
Admission
Control
Initial UE Context Setup

Req,
E-RAB Setup Req,
E-RAB Modify Req,
E-RAB Release Cmd

SRB1, DCCH
Complete, SRB1, DCCH
S1 signaling message RESPONSE
UE
eNode
B
MME
The RRC connection reconfiguration procedure triggered by radio resource request is

described as follows:
1.
The following messages will trigger a radio resource request: the MME sends an
INITIAL CONTEXT SETUP REQUEST message, E-RAB SETUP REQUEST
message, E-RAB MODIFY REQUEST message, or E-RAB RELEASE COMMAND
message.
2.
Upon receiving a message from the MME, the eNodeB performs the E-RAB
configuration request. For example, upon receiving an E-RAB SETUP REQUEST
message, the eNodeB establishes the DRB and allocates the radio resource.
19
3.
The eNodeB sends an RRC CONNECTION RECONFIGURATION message to the

UE, indicating the UE to perform the radio resource configuration. The eNodeB
extracts NAS information from the message sent from the MME, and sends NAS
information in an RRC CONNECTION RECONFIGURATION message to the UE.
4.
The RRC CONNECTION RECONFIGURATION message may carry the

measurement configuration, indicating the UE to establish, modify, or release the
measurement
configuration,
including
intra-frequency
measurement,
inter-frequency measurement, and measurement GAP.

5.
Upon receiving the RRC CONNECTION RECONFIGURATION message, the UE

performs the radio resource configuration and measurement configuration, and
sends an RRC CONNECTION RECONFIGURATION COMPLETE message to the
eNodeB.
6.
Upon receiving the RRC CONNECTION RECONFIGURATION COMPLETE

message, the eNodeB confirms that the reconfiguration is successful, and sends a
response to the MME, for example, E-RAB SETUP RESPONSE message.
4.3.2.2
RRC Connection Reconfiguration Including Mobility Control Information

The network controlled mobility procedure (handover) can trigger RRC connection
reconfiguration including mobility control information.
20
Figure 4-7
RRC Connection Reconfiguration Including Mobility Control Information
Source eNB /
IRAT RAN
UE
Target
eNodeB
Handover Preparation Procedure
RRC Connection Reconfiguration, SRB1,

DCCH
Mobility Control Information
Synchronize to target eNodeB and access target cell via RACH
RRC Connection Reconfiguration Complete, SRB1, DCCH
Release the UEassociated

resources
UE
Source eNB /
IRAT RAN
Target
eNodeB
The RRC connection reconfiguration procedure with mobility control information is

1.
For intra-LTE or inter-RAT handover, the target eNodeB performs the RAC
procedure to allocate resources in the handover preparation phase. The target
eNodeB sends an RRC CONNECTION RECONFIGURATION message including
mobility control information to the source eNodeB by a handover preparation
response message.
2.
The source eNodeB sends an RRC CONNECTION RECONFIGURATION message

to the UE.
3.
Upon receiving the RRC CONNECTION RECONFIGURATION message, the UE

performs handover, disconnects from the source cell, and synchronizes and
accesses the target cell.
4.
The UE sends an RRC CONNECTION RECONFIGURATION COMPLETE

message to the target cell. The handover procedure ends.
21
4.3.3
RRC Connection Reestablishment

The UE initiates an RRC connection reestablishment procedure in the following
scenarios:
1.
The lower layer on the Uu interface of the UE detects a radio link failure.
2.
The intra-LTE handover fails.
3.
The inter-RAT handover fails.
4.
The UE PDCP protocol layer detects integrity check failure.
5.
The RRC connection reconfiguration fails.
Figure 4-8
RRC Connection Reestablishment Procedure
eNode
B
UE
MME
UE in Connected Mode
RRC Connection Reestablishment Request
SRB0, CCCH
Radio Resource
Reconfiguration
RRC Connection Reestablishment
SRB0, CCCH
Radio
Resource
Reconfiguration
RRC Connection Reestablishment Complete
SRB1, DCCH
UE
eNode
B
MME
The RRC connection reestablishment procedure is described as follows:

1.
The UE sends an RRC CONNECTION REESTABLISHMENT REQUEST message

to the eNodeB. The message contains the reestablishment UE-ID and the
reestablishment cause (such as handoverFailure, reconfigurationFailure, and
otherFailure).
22
2.
The RRC CONNECTION REESTABLISHMENT REQUEST message is sent on

SRB0, which is a UL CCCH message.
3.
Upon receiving the RRC CONNECTION REESTABLISHMENT REQUEST

message, the eNodeB suspends the SRB2 and all DRBs of this UE, reestablishes
SRB1, and reactivates the UE'S AS security context (the AS security algorithm of
the UE cannot be modified).
4.
The eNodeB sends an RRC CONNNECTION REESTABLISHMENT message on

SRB0 to the UE. The message is a DL CCCH message.
5.
Upon receiving the RRC CONNNECTION REESTABLISHMENT message, the UE

completes SRB1 reestablishment and AS security reestablishment.
6.
The UE sends an RRC CONNNECTION REESTABLISHMENT COMPLETE

message to the eNodeB. The RRC connection reestablishment procedure ends.
4.3.4
RRC Connection Release

The RRC connection release procedure is used to release the RRC resources of the UE
and the eNodeB, including radio bearers and radio resources.
The RRC connection release procedure is triggered when the eNodeB receives a UE
CONTEXT RELEASE COMMAND message from the MME.
23
Figure 4-9
eNode
B
UE
MME
S1-AP: UE Context Release Command

SRB1, DCCH
Release radio
resources
Enter RRC_IDLE
Release UEassociated radio

resources
S1-AP: UE Context Release Response
UE
eNode
B
MME
The RRC connection release procedure triggered by the MME is described as follows:
1.
The MME sends a UE CONTEXT RELEASE COMMAND message to the eNodeB,

informing the UE to release the dedicated S1 connection and radio resource.
2.
The eNodeB sends an RRC CONNECTION RELEASE message to the UE,
3.
The eNodeB releases the resources of the UE, including the S1 connection and
radio resources.
4.
Upon receiving an RRC CONNECTION RELEASE message, the UE releases the

radio resources and transits to RRC_IDLE.
4.3.5
Context Fetch
In accordance with 3GPP TS 36.331, only the eNodeB that has a valid UE context can
perform the RRC connection re-establishment procedure. The context fetch function is
based on the ZTE private X2 interface interaction and processing procedures. When the
eNodeB device receives an RRC CONNECTION REESTABLISHMENT REQUEST
message from a UE but there is no valid UE context, the eNodeB can obtain the UE's
context through the X2 interface, and complete the RRC connection re-establishment
procedure. This function can increase the success ratio of RRC connection
24
re-establishment, and decrease the dropped-call rate and increase the handover
success rate.
Figure 4-1
ContextFetch Sequence Diagram
UE
eNodeB-A
eNodeB-B
MME
SGW
1.RRC Connection Reestablishment Request

eNodeB-A has no valid UE
context. In fact, eNodeB-B
served the UE before RRC
re-establishment
2.X2AP: RLF Indication
(include ZTE specific IE:
inter-eNB reestablishment ind)
3.X2AP: Handover Request
(include valid UE Context)
4.RRC Connection Reestablishment
5.RRC Connection Reestablishment Complete
6.RRC Connection Reconfiguration
7.X2AP: Handover Request Acknowledge
8.X2AP: SN Status Transfer

Data Forwording
9.RRC Connection Reconfiguration Complete
Packet Data
Packet Data
10.S1AP: Path Switch Request
Switch DL path
End marker
Packet data
End marker
11.S1AP: Path Switch Request Acknowledge
12.X2AP: UE Context Release
UE
eNodeB-A
eNodeB-B
MME
SGW
The RRC connection re-establishment procedure based on the context fetch function is
1.
Before the RRC connection re-establishment procedure occurs, the serving

eNodeB of the UE is eNodeB-B. The UE initiates the RRC connection
re-establishment procedure for some reason (refer to the triggering cause described
in Section 4.3.3 RRC Connection Reestablishment. The UE selects a cell on
eNodeB-A through the cell selection procedure, and sends an RRC CONNECTION
REESTABLISHMENT REQUEST message.
2.
Because there is no information about the UE on eNodeB-A, eNodeB-A cannot find
25
the corresponding UE instance in accordance with the ue-Identity IE contained in

the RRC CONNECTION REESTABLISHMENT REQUEST message, which means
that there is no valid UE context. If the InterEnbReestabSwch parameter is set to
open on the OMMB, eNodeB-A performs the following Context Fetch procedure:
The physCellId parameter in the ue-Identity IE indicates the physical cell ID of the
serving cell of the UE before RRC connection re-establishment. eNodeB-A
searches for a neighbor eNodeB that probably has the valid context of the UE
(which means that the neighbor eNodeB has a cell with the physical cell ID being
physCellId). eNodeB-B is the neighbor eNodeB meeting the above condition.
If eNodeB-A and eNodeB-B meet the following conditions, eNodeB-A sends an RLF
INDICATION message to eNodeB-B:
The X2 connection is established.
They belong to the same MME.
The message contains the private Inter-eNB reestablishment Ind IE of ZTE.

3.
If the InterEnbReestabSwch parameter is set to open on the OMMB, eNodeB-B

performs the following Context Fetch procedure:
In accordance with the Failure cell PCI IE and C-RNTI IE contained in the RLF
INDICATION message, eNodeB-B searches for the corresponding UE instance. If
the message contains the Inter-eNB reestablishment Ind IE, eNodeB-B sends a
HANDOVER REQUEST message to eNodeB-A to deliver the valid UE context to
eNodeB-A.
4.
After obtaining the valid UE context from the received HANDOVER REQUEST
message, eNodeB-A starts the RRC connection re-establishment procedure, and
sends an RRC CONNECTION REESTABLISHMENT message to the UE.
5.
After completing access stratum security activation and SRB1 re-establishment, the
UE sends an RRC CONNECTION REESTABLISHMENT COMPLETE message to
eNodeB-A.
6.
eNodeB-A sends an RRC CONNECTION RECONFIGURATION message to the

UE to trigger the UE to re-establish SRB2 and DRB.
7.
26
eNodeB-A sends a HANDOVER REQUEST ACKNOWLEDGE message to
eNodeB-B.
8.
eNodeB-B sends an SN STATUS TRANSFER message to eNodeB-A.
9.
The UE sends an RRC CONNECTION RECONFIGURATION COMPLETE

message to eNodeB-A. eNodeB-A starts transmitting data to the UE.
10. eNodeB-A sends a PATH SWITCH REQUEST message to the MME to inform the
core network to switch over the UE service path to eNodeB-A. The SGW switches
the downlink path of all the services of the UE from eNodeB-B to eNodeB-A, and
then sends End marker to eNodeB-B to terminate data forwarding from eNodeB-B
to eNodeB-A.
11. The MME sends a PATH SWITCH REQUEST ACKNOWLEDGE message to
eNodeB-A.
12. eNodeB-A sends a UE CONTEXT RELEASE message to inform eNodeB-B to
release the context of the UE.
4.4
NAS Signaling Transmission

The NAS signaling transmission function is used for NAS message interaction between
the UE and the MME. These NAS messages are transparent for the eNodeB.
On the Uu interface, the NAS message can be carried on dedicated SRB2 as well as be
carried on RRC message on SRB1. When the NAS signaling is carried on SRB2, the
related Uu interface messages include the UL INFORMATION TRANSFER message
and the DL INFORMATION TRANSFER message. The RRC messages on SRB1 that
can carry the NAS signaling include the RRC CONNECTION SETUP COMPLETE
message and the RRC CONNECTION RECONFIGURATION message.
On the S1 interface, the S1AP messages used to transmit the NAS signaling include the
INITIAL UE MESSAGE, DOWNLINK NAS TRANSPORT message, and UPLINK NAS
TRANSPORT message.
For the eNodeB, the NAS messages between the UE and the MME are transparent DT
messages. When sending the first UL DT message (INITIAL UE MESSAGE) to the MME,
the eNodeB establishes a dedicated logical connection between the MME and the UE.
The NAS messages can be transmitted on this connection.
27
4.5
UE Context Management
4.5.1

This procedure is used to set up the initial UE context, including the E-RAB context,
security context, UE radio capability information, and UE security capability information.
The initial UE context setup procedure is triggered by the MME.
Figure 4-10
UE
eNodeB
MME
UE Capability Enquiry
Procedure
S1-AP: INITIAL CONTEXT SETUP
REQUEST
RRC Security Procedure
Admission Control
(SRB2 and default bearer)
eNodeB protocol layer configuration
(including UE-associated S1 default
bearer data tunnel configuration)
Procedure
S1-AP: INTIAL CONTEXT SETUP
RESPONSE
UE
eNodeB
MME
The initial UE context setup procedure is described as follows:

1.
If the NAS message of the UE is used for the Attach Request, the eNodeB initiates
the UE radio capability enquiry procedure after sending an INITIAL UE MESSAGE.
For details about UE radio capability enquiry, refer to section 4.6 UE Capability
Enquiry.
2.
Upon receiving the INITIAL UE MESSAGE, the MME initiates the NAS
authentication procedure and selects a suitable S-GW for the UE. The MME sends
28
an INITIAL CONTEXT SETUP REQUEST message to the eNodeB, including the

NAS signaling that needs to be sent to the UE.
3.
The eNodeB initiates the AS security procedure. For details, refer to section 4.8 AS
Security Management.
4.
Based on the INITIAL CONTEXT SUTUP REQUEST message, the eNodeB

completes RAC and radio resource allocation, including SRB2 and the default
bearer.
5.
After completing RAC and radio resource allocation, the eNodeB configures the Uu
interface and S1 interface protocols.
6.
The eNodeB sends an RRC CONNECTION RECONFIGURATION message to the

UE.
7.
After receiving the RRC CONNECTION RECONFIGURATION message, the

eNodeB sends an INITIAL CONTEXT SETUP RESPONSE message to the MME.
The message contains the successful E-RAB establishment list and possible failed
E-RAB establishment list.
4.5.2
UE Context Release
4.5.2.1
eNodeB-Triggered UE Context Release

The purpose of this procedure is to enable the eNodeB to request the UE context release
due to an E-UTRAN generated reason.
29
Figure 4-11
eNodeB Triggered UE Context Release
UE
eNodeB
MME
The eNodeB decide to request UEassociated S1-connection release
S1-AP: UE CONTEXT RELEASE

REQUEST
UE Context Release (MME Triggered)
UE
eNodeB
MME
The eNdoeB triggered UE context release procedure is described as follows:

1.
The eNodeB determines to initiate the UE context release procedure, for example,
triggered by user inactivity. The user inactivity detection function detects inactive
UEs in a period of time, and triggers the eNodeB to initiate a UE context release to
recycle the radio resources of the access network. The related OMC parameters
include switchForUserInactivity and tUserInac. If switchForUserInactivity is set to
open, and there is no users traffic data, the eNodeB triggers the UE context
release procedure.
2.
The eNodeB sends a UE CONTEXT RELEASE REQUEST message to the MME,

including an appropriate release cause. The eNodeB starts a timer. If the eNodeB
receives a UE CONTEXT RELEASE COMMAND message from the MME, it stops
the timer. If the timer expires, the eNodeB initiates UE context release locally.
3.
Upon receiving the eNodeBs request, the MME initiates the UE context release
procedure. For details, refer to section 4.5.2.2 MME-Triggered.
4.5.2.2
MME-Triggered UE Context Release

The purpose of this procedure is to enable the MME to trigger UE context release. The
procedure may be triggered after the MME receives the eNodeBs request, or be
triggered by the MME itself.
30
The MME is responsible for checking whether multiple UE-associated logical

S1-connections toward the same UE. When the MME detects two UE-associated logical
S1-connections toward the same UE after the UE has initiated the establishment of a
new UE-associated logical S1-connection, the MME releases the old UE-associated
logical S1-connection.
Figure 4-12
UE
MME Triggered UE Context Release
eNodeB
MME
ALT
REQUEST
COMMAND
RRC CONNECTION RELEASE PROCEDURE
The eNodeB release UE-associated

local resource

COMPLETE
UE
eNodeB
MME
The MME triggered UE context release procedure is described as follows:

1.
The MME triggers the UE context release procedure by itself or after receiving a
release request from the eNodeB.
2.
The MME sends a UE CONTEXT RELEASE COMMAND message to the eNodeB.
3.
The eNodeB initiates the RRC connection release procedure.
4.
The eNodeB releases the UE-related local resources.
5.
The eNodeB sends a UE CONTEXT RELEASE COMPLETE message to the MME.
31
4.5.3
UE Context Modification
This procedure is used to modify the established UE context partly, such as CS Fallback
process of connection state.
Figure 4-13
UE Context Modification Procedure
UE
eNodeB
MME
S1-AP: UE CONTEXT
MODIFICATION REQUEST
eNodeB store modified parameters and

reconfigure relative protocol layer

Procedure
S1-AP: UE CONTEXT
MODIFICATION RESPONSE
UE
eNodeB
MME
The UE context modification procedure is described as follows:

1.
The MME sends a UE CONTEXT MODIFICATION REQUEST message to the

eNodeB. The message includes:
i.
the Security Key IE;
ii.
the UE Aggregate Maximum Bit Rate IE;
iii.
the CS Fallback Indicator IE.
In addition, the message includes the NAS signaling that the MME needs to
transmit to the UE.
2.
Based on the UE CONTEXT MODIFICATION REQUEST message, the eNodeB

reconfigures the Uu interface related protocols.
3.
The eNodeB initiates the RRC connection reconfiguration procedure. For details,
refer to section 4.3.2 RRC Connection Reconfiguration.
32
4.
The eNodeB sends a UE CONTEXT MODIFICATION RESPONSE message to the

MME. The UE context modification procedure ends.
4.6
UE Capability Enquiry
This procedure is used to transfer UE radio access capability information from UE to the
network. This procedure is described as follows:
1.
If the eNodeB identifies that the NAS access type of the UE is Attach, it sends a UE
CAPABILITY ENQURY message to the UE during the Initial UE Context Setup
procedure, requiring the UE to report its radio capability.
2.
The UE sends a UE CAPABILITY RESPONSE message to the eNodeB.
3.
The eNodeB sends a UE CAPABILITY INFO INDICATION message to the MME,

and transfers the UE capability to the core network.
According to 3GPP TS23.401, in the Attach procedure, the MME will not send the UE
radio capability to the eNodeB, namely, the INITIAL CONTEXT SETUP REQUEST
message does not include the UE radio capability. Therefore, after the eNodeB detects
that the INITIAL CONTEXT SETUP REQUEST message received from the MME does
not contain UE capability information, the eNodeB initiates a UE capability enquiry
procedure on the Un interface.
To decrease the delay of the Attach procedure, the UE capability enquiry occasion
triggered by the ZTE eNodeB is optimized. That is to say, if the eNodeB ensures that the
UE access type is Attach, it initiates the UE capability enquiry procedure, instead of
waiting for the INITIAL CONTEXT SETUP REQUEST message from the MME.
4.7
E-RAB Management
Once a UE context is established, the E-RAB function is used to establish, modify, and
release E-UTRAN resources for user data transport. The MME initiates the E-UTRAN
33
resource establishment, modification, and release, and provides the related QoS
information to the eNodeB. .
For an LTE network, 3GPPdefines the core network as a single packet-switched network.
The bearer type can be identified by QoS class identifier (QCI1QCI9).
Figure 4-14
E-RAB With QCI Diagram
VoIP with
QCI1+5 or 1
Streaming
service with
QCI7~9
Video with
QCI2+5 or 2
Streaming
service with
QCI6
SRB
Best effort with

QCI8~9
Best effort with

QCI6
1.
One non-GBR streaming service of QCI7, QCI8, or QCI9.
2.
One non-GBR best effort service of QCI8 or QCI9.
3.
One non-GBR streaming service of QCI16.
4.
One non-GBR best effort service of QCI6.
5.
One GBR VoIP call of QCI1 + QCI5 or only QCI1. QCI5 is only used for IMS
signaling.
6.
One GBR video call of QCI2 + QCI5 or only QCI2. QCI5 is only used for IMS
signaling.
4.7.1
E-RAB Setup
This procedure is used to allocate resources on the Uu interface and S1 interface for one
or multiple E-RABs and to establish the corresponding Data Radio Bearer (DBR) to a
specific UE. In general, the EPC initiates the procedure.
34
Figure 4-15
E-RAB Setup Procedure
UE
eNodeB
MME
S1-AP: E-RAB Setup

Request
Admission
Control
(including UE-associated S1 data
tunnel configuration)
Procedure
S1-AP: E-RAB Setup
Response
UE
eNodeB
MME
The E-RAB setup procedure is described as follows:

1.
The MME sends an E-RAB SETUP REQUEST message to the eNodeB. The
message contains the E-RAB list to be established. In the message, the MME
specifies the E-RAB ID, QoS parameters (QCI, ARP, GBR, and MBR), and
UE-AMBR (used to limit the total uplink and downlink rate of all Non-GBR services
of the UE).
2.
Upon receiving the E-RAB SETUP REQUEST message, the eNodeB performs
resource admission and allocation based on the QoS requirements of the services
to be established.
3.
Based on the resource admission result, the eNodeB completes the protocol
configuration on the local Uu interface and S1 interface.
4.
The eNodeB initiates the RRC connection reconfiguration procedure.
5.
After the RRC connection reconfiguration procedure ends, the eNodeB sends an
E-RAB SETUP RESPONSE message to the MME, informing the MME of the
E-RAB establishment result. If the E-RAB establishment fails, the eNodeB fills in the
failed E-RAB establishment list in the message.
35
4.7.2
E-RAB Modification
This procedure is used to modify the one or multiple already established E-RABs, and is
triggered by the MME.
Figure 4-16
UE
E-RAB Modification Procedure
eNodeB
MME
S1-AP: E-RAB Modify

Request
Admission
Control

Procedure
S1-AP: E-RAB Modify
Response
UE
eNodeB
MME
The E-RAB modification procedure is described as follows:

1.
The MME sends an E-RAB MODIFY REQUEST message to the eNodeB.
2.
The eNodeB performs RAC based on the specified QoS in the E-RAB MODIFY
REQUEST message.
3.
For each E-RAB to be modified, the MME provides the QoS parameters to the
eNodeB, including QCI, ARP, and optional GBR QoS information. The eNodeB
configures the local protocols based on the RAC result.
4.
The eNodeB initiates the RRC connection reconfiguration procedure.
5.
After the RRC connection reconfiguration procedure ends, the eNodeB sends an
E-RAB MODIFY RESPONSE message to the MME, informing the MME of the
36
E-RAB modification result. If the E-RAB modification fails, the eNodeB fills in the
failed E-RAB modification list in the message and specifies the reason.
4.7.3
E-RAB Release
4.7.3.1
eNodeB Triggered E-RAB Release

This procedure enables the eNodeB to release one or multiple E-RABs for a specified
UE.
The eNodeB sends an E-RAB RELEASE INDICATION message to the MME. The
message contains the E-RAB list released at the eNodeB.
After receiving the E-RAB RELEASE INDICATION message, the MME completes the
E-RAB resource release on the core network side.
Figure 4-17
UE
eNodeB Triggered E-RAB Release
MME
eNodeB

Procedure
S1-AP: E-RAB RELEASE

INDICATION
UE
4.7.3.2
eNodeB
MME
MME Triggered E-RAB Release

This procedure enables the MME to release one or multiple E-RABs for a specified UE.
37
Figure 4-18
UE
MME Triggered E-RAB Release
MME
eNodeB

COMMAND
Release corresponding
local resources

Procedure
RESPONSE
UE
eNodeB
MME
The MME triggered E-RAB release procedure is described as follows:

1.
The MME sends an E-RAB RELEASE COMMAND message to the eNodeB. The
message contains the E-RAB release list.
2.
After receiving the E-RAB RELEASE COMMAND message, the eNodeB releases
the related resources locally.
3.
The eNodeB initiates the RRC connection reconfiguration procedure, informing the
UE to release the related resources.
4.
After the RRC connection reconfiguration is completed, the eNodeB sends an

E-RAB RELEASE RESPONSE message to the MME. If the E-RAB release fails,
the eNodeB fills in the failed E-RAB release list in the message.
4.7.4
Radio Bearer Combination

Different types of traffic bearers can be established for specified users. For example, a
user can simultaneously hold a video conference and process e-mails. The possible
traffic bearer combinations are listed as follows:
38
1.
SRB1 and SRB2 + one GBR VoIP + two non-GBR best effort services
2.
SRB1 and SRB2 + one GBR Video + two non-GBR best effort services
3.
SRB1 and SRB2 + three non-GBR best effort services
4.8
AS Security Management
4.8.1
Integrity Protection
This function supports signaling integrity protection on the Uu interface, preventing
deceptive attacks from a UE or third-party network devices.
Integrity protection is applicable to the NAS signaling and RRC signaling instead of the
service data of users. The integrity protection function is implemented on the PDCP
protocol layer.
In the initial context setup procedure, AS security is activated before establishment of
SRB2 and all DRBs. This procedure is described as follows:
1.
The eNodeB acquires KeNB and UE security capability from the INITIAL
CONTEXT SETUP REQUEST message sent by the MME. The eNodeB
generates the KRRCint (for the integrity protection of RRC signaling), KRRCenc (for the
ciphering of RRC signaling), and KUPenc (for the ciphering of user data) based on
KeNB. The eNodeB determines the negotiated AS security algorithms (integrity

and ciphering algorithms) based on UE security capability and locally configured
eNodeB AS security capability, and configures the algorithms to the UE by

sending a SECURITY MODE COMMAND message.
2.
The UE activates AS security, including integrity protection, based on the

received SECURITY MODE COMMAND message. The UE sends a SECURITY
MODE COMPLETE message to the eNodeB.
Integrity protection is applicable to all the RRC messages sent/received from/by the
eNodeB, including the SECURITY MODE COMPLETE message.
The integrity algorithm can be updated upon handover. The integrity keys can be
updated through the handover procedure, intra-cell handover procedure, and RRC
connection reestablishment procedure.
39
The following table lists the AS integrity algorithms supported by the LTE system. The
eNodeB integrity algorithm capability can be set by the integProtAlg parameter on the
OMC.
Table 4-2
LTE Integrity Algorithms
EPS RRC integrity algorithms
Four types of EPS RRC integrity algorithms are

defined:
- EIA0: Null integrity protection algorithm
- 128-EIA1: SNOW 3G
- 128-EIA2: AES
- 128-EIA3: ZUC based algorithm
4.8.2
Ciphering
This function supports ciphering for signaling and data on the Uu interface to ensure
communication reliability between the UE and the eNodeB, and between the UE and the
EPC.
The AS ciphering activation procedure is described as follows:
1.
The eNodeB acquires KeNB and UE security capability from the INITIAL
CONTEXT SETUP REQUEST message sent by the MME. The eNodeB
generates the KRRCint (for the integrity protection of RRC signaling), KRRCenc (for the
ciphering of RRC signaling), and KUPenc (for the ciphering of RRC signaling) based
on KeNB. The eNodeB determine the negotiated AS security algorithms
(integrity and ciphering algorithms) based on UE security capability and locally

configured eNodeB AS security capability, and configures the algorithms to the
UE by sending a SECURITY MODE COMMAND message.
2.
The UE activates AS security, including ciphering protection, based on the

received SECURITY MODE COMMAND message. The UE sends a SECURITY
MODE COMPLETE message to the eNodeB.
Ciphering is applicable to all the RRC messages sent/received from/by the eNodeB, but
the SECURITY MODE COMPLETE message itself is not ciphered.
40
The ciphering algorithm can be updated upon handover. The ciphering keys can be
updated through the handover procedure, intra-cell handover procedure, and RRC
connection reestablishment procedure.
The AS ciphering algorithms supported by the LTE system are listed in the following
table. The eNodeB ciphering algorithm capability can be set by the encryptionAlg
parameter on the OMC.
Table 4-3
LTE Ciphering Algorithms

Four types of EPS RRC ciphering algorithms
are defined.
- EEA0: Null ciphering algorithm
EPS RRC ciphering algorithms
- 128-EEA1: SNOW 3G based algorithm

- 128-EEA2: AES based algorithm
- 128-EEA3: ZUC based algorithm
Four types of EPS UP ciphering algorithms are
defined.
- EEA0: Null ciphering algorithm
EPS UP ciphering algorithms
- 128-EEA1: SNOW 3G based algorithm

- 128-EEA2: AES based algorithm
- 128-EEA3: ZUC based algorithm
4.9
S1 Interface Management
The S1 interface is an application interface between the eNodeB and the EPC.
41
Figure 4-19
S1 Interface
EUTRAN
S1-C
EPC
MME
MME
eNode
B
S-GW
eNode
B
S-GW
S1-U
The S1 interface includes S1 C-Plane and S1 U-Plane. The S1 U-Plane (S1-U) is defined
as the interface between the eNodeB and the S-GW, and the S1 C-Plane (S1-C) is
defined as the interface between the eNodeB and the MME.
The S1 interface management contains the following procedures:
1.
Error Indication
2.
Reset
3.
S1 Setup
4.
eNodeB/MME Configuration Update
5.
Overload
The above procedures are triggered under specific network conditions. For the test
purpose, Error Indication and Overload are difficult to be triggered.
4.9.1
Error Indication
This function is used to indicate logical errors without proper error response messages
between the eNodeB and MME. Both the MME and the eNodeB can trigger this
procedure. The corresponding message is ERROR INDICATION.
42
4.9.2
Reset
Both the MME and the eNodeB can trigger this procedure to reset the S1 connection.
This function does not affect the configuration data interacted by application layers
during S1 establishment.
If the procedure is triggered by the eNodeB, the eNodeB sends a RESET message to the
MME. After receiving the RESET message, the MME releases the corresponding
resources and answers the eNodeB with a RESET ACKNOWLEDGE message.
If the procedure is triggered by the MME, the MME sends a RESET message to the
eNodeB. After receiving the RESET message, the eNodeB releases the corresponding
resources, including the resources on the Uu interface, and answers the MME with a
RESET ACKNOWLEDGE message.
4.9.3
S1 Establishment
This procedure is used to establish an S1AP connection and switch necessary data
required by the application layer between the eNodeB and the MME.
This procedure is the initial procedure of S1AP, which reinitializes the E-UTRAN S1AP
UE related context (if exists) and clears all the related S1 signaling connections. The
result of this procedure is similar to that of Reset. Meanwhile, the MME related load state
information stored in the eNodeB is cleared. This procedure is described as follows:
The eNodeB sends an S1 SETUP REQUEST message to the MME to initiate the S1
establishment procedure.
If the S1 establishment is successful, the MME returns an S1 SETUP RESPONSE
message to the eNodeB. Otherwise, the MME returns an S1 SETUP FAILURE message
to the eNodeB. Once the S1 establishment is successful, the S1 interface can operate
properly.
43
4.9.4
Configuration Update
This procedure is used to update the application layer configuration between the eNodeB
and the MME. This procedure does not affect the existing UE contexts. Both the eNodeB
and the MME can trigger this procedure.
The eNodeB configuration update procedure is used to provide the updated eNodeB
configuration to the MME. The eNodeB sends an ENODEB CONFIGURATION UPDATE
message to the MME. The message contains the updated configuration. If the MME
successfully receives the related updated configuration, it returns an ENODEB
CONFIGURATION UPDATE ACKNOWLEDGE message to the eNodeB. For example,
the TA and default paging DRX can be updated through this procedure.
The MME configuration update procedure is used to provide the updated MME
configuration to the eNodeB. The eNodeB sends an ENODEB CONFIGURATION
UPDATE message to the MME. The message contains the updated configuration. If the
MME successfully receives the related updated configuration, it returns an ENODEB
CONFIGURATION UPDATE ACKNOWLEDGE message to the eNodeB. For example,
the serving GUMMEI and MME relative capability can be updated through this
procedure.
4.9.5
Overload Indication
This procedure is used for the MME to inform the eNodeB whether to reduce signaling
load to this MME, including the OVERLOAD START and OVERLOAD STOP messages.
If the eNodeB receives an OVERLOAD START message, the MME is considered to be
overload. The eNodeB takes actions based on the Overload Action IE in the message.
The Overload Action IE may be reject all RRC connection establishments for
non-emergency mobile originated data transfer , reject all RRC connection
establishments for signaling, or only permit RRC connection establishments for
emergency sessions and mobile terminated services If new users are going to connect
to the overload MME, the eNodeB must ensure that the users who meet the above
specified overload limit conditions can connect to this MME. If the UE is released to
reduce MME load, the eNodeB sends an RRC CONNECTION RELEASE message to
the UE with loadBalancingTAUrequired as the release cause.
44
If the eNodeB receives an OVERLOAD STOP message, the corresponding MME is not
considered to be overloaded. The eNodeB cancels signaling limit to this MME.
4.9.6
S1 Flex
S1-Flex means that one MME/S-GW can be connected to multiple eNodeBs, and one
eNodeB can be connected to multiple MME/S-GWs.
S1-Flex supports MME/S-GW redundancy and MME/S-GW load balancing.
Some UEs in an eNodeB are connected to one MME/S-GW, and some other UEs in this
eNodeB may be connected to another MME/S-GW. One UE can be connected to only
one MME/S-GW at the same time.
To support one eNodeB to be connected to multiple MME/S-GWs, the NAS Node
Selection Function (NNSF) on the eNodeB is used to determine the MME for specified
users. On the S1 interface, no procedure corresponds to NNSF. Through NNSF, the
eNodeB determines the MME association based on the UEs temporary ID (allocated by
the core network). In real cases, S-TMSI, GUMMEI, and selected PLMN can be used for
determining an MME association.
If the eNodeB cannot acquire the UEs S-TMSI and GUMMEI, it can select an MME
based on the selected PLMN and MME load. If the UE performs the Attach procedure,
and the eNodeB cannot select a proper MME for the UE, the eNodeB checks whether
there is an overloaded MME. For S1-Flex, if all the MMEs are overloaded, the MME
selection mechanism is the same as non-S1-Flex. The eNodeB refuses the access of the
corresponding new users according to the overload limit conditions specified by the MME,
which has no impact on the existing users.
45
Figure 4-20
S1-Flex
MME
S-GW
MME
S-GW
eNode-B
UE1
eNode-B
UE2
The S-TMSI is composed of an MMEC and an M-TMSI. The M-TMSI is allocated by the
MME. After acquiring the UEs S-TMSI, the eNodeB searches for the corresponding S1
association based on the S-TMSI. The GUMMEI is composed of an MMEC and an MME
Group ID. The UE may be set to the registeredMME IE in the RRC CONNECTION
COMPLETE message. After acquiring the GUMMEI, the eNodeB searches for the
corresponding S1 association based on the GUMMEI. The eNodeB can acquire the
MME Group ID from the S1 SETUP RESPONSE message and the MME
CONFIGURATION UPDATE message.
If the S-TMSI and the GUMMEI cannot be acquired, the eNodeB selects an MME based
on load conditions. In the S1 SETUP RESPONSE message, the MME provides its
relative capacity, which is called the weight factor ranging from 0 to 255. The higher the
weight factor, the more UE can be processed by the MME. If the weight factor is modified,
the MME informs the eNodeB by sending an MME CONFIGURATION UPDATE
message.
The MME relative capacity is pre-configured in accordance with the operators
requirements when the network is established, and cannot be updated with MME load
conditions. In general, the MME relative capacity is not frequently updated. However, the
MME relative capacity can be updated when a new MME is added or the MME is
maintained. For a newly added MME, the relative capacity at the initial phase can be set
high to rapidly increase its load.
The following example shows an S1-Flex example. MME1 and MME2 belong to MME
Group 1, and MME 3 belongs to MME Group 2. MME selection or load balancing can be
performed in MME Group 1. If a user performs handover from eNodeB1 to eNodeB2 or to
46
eNodeBn, the handover is not an inter-MME handover. When a user performs handover
from eNodeBn to eNodeBn+1, the handover is a inter-MME handover.
Figure 4-21
S1-Flex Example
S1 Interface
eNB1
MME1
MME Group 1
eNB2
...
MME2
eNBn
eNBn+1
MME3
MME Group 2
If the SCTP connection to an MME is broken, all the UE connected to the MME will be
released, and the MME is deleted from the MME selection list of the eNodeB.
4.10
X2 Interface Management
The X2 interface is the interface between eNodeBs. It is applied to the UEs in
RRC_CONNECTED state to perform the mobility procedure between eNodeBs.
47
Figure 4-22
X2 Interface
X2-C
eNodeB
eNodeB
X2-U
eNodeB
The X2 interface includes X2 C-Plane and X2 U-Plane. The X2 U-Plane offers

non-guaranteed delivery of user plane PDUs. The related management procedures
include:
1.
Load Indication
2.
Error Indication
3.
X2 Setup
4.
Reset
5.
eNodeB Configuration Update
6.
Resource Status Reporting
The above procedures are triggered under specific network conditions. For test purpose,
the Error Indication procedure is difficult to be triggered.
4.10.1
Load Indication
The load indication procedure is used to transfer load and interference co-ordination
information between eNodeBs controlling intra-frequency neighboring cells.
1.
The eNodeB sends a LOAD INFORMATION message to eNodeBs controlling

intra-frequency neighboring cells. In the message, UL Interference Overload
48
Indication IE and UL High Interference Indication IE are used for uplink interference
coordination, and Relative Narrowband Tx Power (RNTP) IE is used for downlink
interference coordination.
2.
According to the received message, the peer eNodeB adjusts the resource
allocation and scheduling on the Uu interface to suppress control interference.
4.10.2
Error Indication
This procedure enables the eNodeB to report the detected errors in a received message
if no proper failure response message.
4.10.3
X2 Setup
The X2 setup procedure is used to establish an X2AP connection and to exchange
application layer configuration data. This procedure erases any existing application layer
configuration data stored in the two eNodeBs and replaces it by the new received data.
This procedure also resets the X2 interface like a Reset procedure would do.
1.
The eNodeB sends an X2 SETUP REQUEST message to the peer eNodeB. The
message contains the serving cell list in the eNodeB and the supported GU Group
ID list.
2.
The peer eNodeB sends an X2 SETUP RESPONSE message to the eNodeB. The
message contains the serving cell list in the eNodeB and the supported GU Group
ID list.
4.10.4
Reset
This procedure is used to align the resources between eNodeBs. This procedure resets
the X2 interface, but does not affect the application layer configuration data exchanged
during the X2 setup procedure.
1.
eNodeB 1 sends a RESET REQUEST message to eNodeB2.
49
2.
eNodeB2 stops any other ongoing procedures on the X2 interface, and deletes the
all the context information related to eNodeB1. eNodeB2 returns a RESET
RESPONSE message to eNodeB1.
4.10.5
eNodeB Configuration Update

This procedure is used to update the X2 interface related application layer configuration
data.
1.
eNodeB1 sends an ENODEB CONFIGURATION UPDATE message to eNodeB2.
2.
eNodeB2 updates the served cell information about eNodeB1 and GU Group ID list.
eNodeB2 returns an ENODEB CONFIGURATION UPDATE ACKNOWLEDGE
message to eNodeB1.
4.10.6
Resource Status Report

This procedure is used by an eNodeB to determine whether to perform measurements
and to transfer resource status to another eNodeB.
1.
eNodeB1 sends a RESOURCE STATUS REQUEST message to eNodeB2.

eNodeB2 starts or stops the requested measurement according to the Registration
Request information in the message. There are three measurement types: PRB
Periodic, TNL Load Ind Periodic, and HW Load Ind Periodic. eNodeB2 returns a
RESOURCE STATUS RESPONSE message to eNodeB1.
2.
If eNodeB2 starts the measurement requested by eNodeB1, it transfers the

measurement result to eNodeB1 by sending a RESOURCE STATUS UPDATE
message.
50
Key Parameters and Configuration
5.1
Parameter List
Table 5-1
Parameters List
SN
Name
Figure
SI Identity
Figure 5-1,5-2
SI Periodicity
Figure 5-1,5-2
Flag for Whether SIB2 is in System Information
Figure 5-1,5-2
Figure 5-1,5-2
Figure 5-1,5-2
Figure 5-1,5-2
Figure 5-1,5-2
Figure 5-1,5-2
Figure 5-1,5-2
10
Figure 5-1,5-2
11
Figure 5-1,5-2
12
Figure 5-1,5-2
13
Figure 5-1,5-2
14
DRX cycle for paging
Figure 5-7
15
Paging Occasion Factor
Figure 5-7
16
Paging repeated times
Figure 5-7
17
BCCH modification period
Figure 5-7
18
Label number of service class
Figure 5-7
19
Service packet Qos delay parameter
Figure 5-7
20
Service packet Qos loss parameter
Figure 5-7
21
Service class name
Figure 5-7
51
5.2
22
Service priority
Figure 5-7
23
Service bearer type (GBR/Non-GBR)
Figure 5-7
24
RLC type
Figure 5-7
25
Service factor for a QCI
Figure 5-7
26
PDCP SN length
Figure 5-7
27
RLC sequence number type
Figure 5-7
28
Encryption algorithm
Figure 5-9
29
Integrity protection algorithm
Figure 5-9
30
MME load balancing algorithm switch
Figure 5-12
Parameter configuration Rule

Table 5-2
SN
Configuration rule of parameters

Name
Description
Value Range
Default Value
SI Identity,lots of sib
1
SI Identity
can be map to one
1-10
SI.
SI
Periodicity
SI Periodicity
(8[0],16[1],32[2],64[3],
128[4],256[5],512[6])
8[0]
rf
Flag for
3
Whether
Flag for whether
SIB2 is in
SIB2 is in system
System
information.
No[0],Yes[1]
Yes[1]
No[0],Yes[1]
No[0]
Information
Flag for
4
Whether
Flag for whether
SIB3 is in
SIB3 is in system
System
information.
Information
52
Flag for
5
Whether
Flag for whether
SIB4 is in
SIB4 is in system
System
information.
No[0],Yes[1]
No[0]
No[0],Yes[1]
No[0]
No[0],Yes[1]
No[0]
No[0],Yes[1]
No[0]
No[0],Yes[1]
No[0]
No[0],Yes[1]
No[0]
No[0],Yes[1]
No[0]
Information
Flag for
6
Whether
Flag for whether
SIB5 is in
SIB5 is in system
System
information.
Information
Flag for
7
Whether
Flag for whether
SIB6 is in
SIB6 is in system
System
information.
Information
Flag for
8
Whether
Flag for whether
SIB7 is in
SIB7 is in system
System
information.
Information
Flag for
9
Whether
Flag for whether
SIB8 is in
SIB8 is in system
System
information.
Information
Flag for
10
Whether
Flag for whether
SIB9 is in
SIB9 is in system
System
information.
Information
Flag for
11
Whether
Flag for whether
SIB10 is in
SIB10 is in system
System
information.
Information
53
Flag for
12
Whether
Flag for whether
SIB11 is in
SIB11 is in system
System
information.
No[0],Yes[1]
No[0]
No[0],Yes[1]
No[0]
Information
If choose TRUE
schedule
Flag for
Whether
13
SIB12 is in
System
Information
information for
SIB12 will be
included in system,
If choose FALSE
schedule
information for
SIB12 will not be
included in system.
When UE is in idle
and DRX is used ,
UE will monitor
14
DRX cycle
P-RNTI at paging
32[0],64[1],128[2],256[
for paging
occasion each DRX
3] unit Radio Frames
128[3]
cycle. The
parameter indicates
the DRX cycle.
nB is used as one of
Paging
15
Occasion
Factor(nB)
parameters to
derive the Paging
Frame and Paging
Occasion according
4T[0],2T[1],T[2],1/2T[3
],1/4T[4],1/8T[5],1/16T
T[2]
[6],1/32T[7]
to TS 36.304.
Paging
16
repeated
times
54
The parameter is
used to decide how
many times can be
0[0],1[1],2[2],4[3]
0[0]
repeated for paging.
The parameter is
used to determine
17
BCCH
BCCH modification
modification
period: BCCH
period
modification period
2[0],4[1],8[2],16[3]
4[1]
0-256
[0,65535] unit ms
100
= N * DRX cycle
length for paging.
The parameter is
QCI in SAE Bearer
18
Label
Info. eNodeB can
number of
find services QoS
service
parameters and
class
applications
parameters with
QCI.
The parameter is
packet delay
budget(PDB). The
19
Service
Packet Delay
packet qos
Budget (PDB)
delay
denotes the time
parameter
that a packet may

be delayed between
the UE and the PDN
GW.
55
The parameters is
packet loss rate.
The Packet Loss
Rate (PLR) defines
an upper bound for
the rate of SDUs
(e.g. IP packets)
20
Service
that have been
packet qos
processed by the
loss
sender of a link
parameter
layer protocol (e.g.
[0,1] step 10e-6
1-256
1-256
GBR[0],Non-GBR[1]
GBR[0],
1-2
RLC in E-UTRAN)
but that are not
successfully
delivered by the
corresponding
receiver to the upper
layer.
The parameter is
21
Service
name of service,
class name
corresponding to
QCI.
The parameter is
priority. Every QCI
(GBR and
22
Service
Non-GBR) is
priority
associated with a
Priority level. Priority
level 1 is the highest
Priority level.
Service
23
bearer
Service Bearer
type(GBR/N
type:GBR, Non GBR.
on-GBR)
RLC mode for
24
RLC type
application, includes
AM mode and UM
mode.
56
The service weight

25
Service
factor for a QCI that
factor for a
is used for priority
QCI
calculation when
1-255
64
7bit[0],12bit[1]
12bit[1]
5bit[0],10bit[1]
10bit[1]
QoS sorting.
The parameter
26
PDCP SN
defines the PDCP
length
PDU SN field size in

bits
27
RLC
The parameter
sequence
gives the UM SN
number type
field size in bits
57
The parameter
defines encryption
Algorithms for
PDCP, includes
EEA0,128-EEA1,12
8-EEA2,128-EEA1(
high
priority),128-EEA2(l
ow
priority),128-EEA2(h
igh
ow
priority),128-EEA3,1
28-EEA1(high
priority),
128-EEA2(medium
ow
igh priority),
128-EEA3(medium
28
Encryption
algorithm
ow
igh priority),
128-EEA1(medium
ow
igh
priority),128-EEA3(
medium
ow
igh
priority),128-EEA1(
medium
ow
igh priority),
enum(EEA0,128-EEA
1,128-EEA2,128-EEA
1(High priority) and
128-EEA2(Low
priority),128-EEA2(Hig
h priority) and
128-EEA1(Low
priority),128-EEA3,12
8-EEA1(High priority)
and
128-EEA2(Medium
priority) and
128-EEA3(Low
h priority) and
128-EEA3(Medium
priority) and
128-EEA2(Low
h priority) and
EEA0[0]
128-EEA1(Medium
priority) and
128-EEA3(Low
h priority) and
128-EEA3(Medium
priority) and
128-EEA1(Low
h priority) and
128-EEA1(Medium
priority) and
128-EEA2(Low
h priority) and
128-EEA2(Medium
priority) and
128-EEA1(Low
priority))
128-EEA2(medium
58
ow priority)
The parameter
defines integrity
protection
algorithms for
PDCP, includes
EIA0,128-EIA1,128EIA2,128-EIA1(high
priority),
128-EIA2(low
priority),128-EIA2(hi
gh
priority),128-EIA1(lo
w
priority),128-EIA3,1
28-EIA1(high
priority),
128-EIA2(medium
w
gh
priority),128-EIA3(m
Integrity
29
protection
algorithm
edium
w
gh
edium
w
gh
edium
w
gh
edium
w
gh priority),
128-EIA2(medium
w priority)
enum(EIA0,128-EIA1,
128-EIA2,128-EIA1(Hi
gh priority) and
128-EIA2(Low
priority),128-EIA2(Hig
h priority) and
128-EIA1(Low
priority),128-EIA3,128
-EIA1(High priority)
and
128-EIA2(Medium
priority) and
128-EIA3(Low
h priority) and
128-EIA3(Medium
priority) and
128-EIA2(Low
h priority) and
EIA0[0]
128-EIA1(Medium
priority) and
128-EIA3(Low
h priority) and
128-EIA3(Medium
priority) and
128-EIA1(Low
h priority) and
128-EIA1(Medium
priority) and
128-EIA2(Low
h priority) and
128-EIA2(Medium
priority) and
128-EIA1(Low
priority))
59
30
witch of MME Load

MME load
balancing
algorithm
switch
Balancing, which
can determine
whether the MME
Close[0],Open[1]
Open[1]
Load Balancing
function is
performed or not.
5.3
Parameter Configuration Procedure
5.3.1
System Information Broadcast Parameters

1.
Configure the correct cell. In the Configuration Management window on the EMS,
click Modify Area > Managed Element > Radio Parameter > LTE FDD >
E-UTRAN FDD Cell >Scheduling SI. By default, there are four SI records. The
default configurations of SI are SI1:{SIB2,SIB10} SI2:{SIB3,SIB4,SIB5}
SI3:{SIB6,SIB7,SIB8}and SI4:{SIB11}. Operator can modify SI records

according to requirements. Click each SI record, and check whether the flag for the
tested SIB is in system information, see Figure 5-1 and Figure 5-2. Synchronize the
data to eNodeBs.
Figure 5-1
60
SI Scheduling Information Configuration-1
Figure 5-2
2.
SI Scheduling Information Configuration-2
Click Modify Area > Managed Element > Radio Parameter > LTE FDD > Cell
Reselection Configuration > E-UTRAN Cell Reselection. Double-click the record
to add inter-frequency neighbor cells or frequencies for SIB5.
61
Figure 5-3
3.
EUTRAN Inter-Frequency Configuration
Reselection Configuration > UTRAN FDD Cell Reselection. Double-click the
record to add UTRAN frequencies for SIB6..
Figure 5-4
4.
UTRAN Frequency Configuration
Reselection Configuration > GERAN Cell Reselection. Double-click the record to
add GERAN related information for SIB7..
62
Figure 5-5
5.
GERAN Frequency Configuration
Reselection Configuration > CDMA2000 SIB8 Content. Double-click the record to
add CDMA related information for SIB8..
Figure 5-6
CDMA Frequency Configuration
63
5.3.2
Paging Parameters
1. In the Configuration Management window on the EMS, click Modify Area >
Managed Element > Radio Parameter > LTE FDD > E-UTRAN Service
Configuration > UE Paging. Some parameters related to Paging are displayed.
Click
Figure 5-7
5.3.3
to modify the related parameters..
Paging Related Parameter Configuration
ERAB Parameters
Managed Element > Radio Parameter > LTE FDD > QoS Configuration > QoS
Service Class. Some parameters related to QoS QCI 1-9 are displayed. Label
Number of Service Class 19 is for DRB, and 0 or 256 is for SRB.
64
Figure 5-8
5.3.4
Bearer Parameter Configuration
Encryption Parameters
1.
In the Configuration Management window on the EMS, click Modify Area >
Configuration > Security Management. Click
to modify the encryption and
decryption algorithm and integrity algorithm parameters. EEA1 is the SNOW

algorithm, EEA2 is the AES algorithm, and EEA3 is the AUC algorithm.
Figure 5-9
Encryption Parameter Configuration
65
5.3.5
S1 Parameters
Managed Element > Transmission Network > Signaling and Business > SCTP.
Click
Figure 5-10
to add S1 SCTP links..

S1 SCTP Configuration
After SCTP is established, the EMS will automatically add S1AP.
Figure 5-11
66
S1AP Configuration
5.3.6
S1-Flex Parameters
Configuration > Global Switch. Click
and set MME Load Balancing
Algorithm Switch to Open[1]..
Figure 5-12
5.3.7
Setting MME Load Balancing Switch
X2 Parameters
Managed Element > Transmission Network > Signaling and Business > SCTP.
Click
to add X2 SCTP links..
67
Figure 5-13
X2 SCTP Configuration
After SCTP is established, the EMS will automatically add X2AP..
Figure 5-14
5.3.8
X2AP Configuration
The Other Related Parameters Configuration

To test system information broadcast, the UE needs to support the related RAT. Set the
supported RAT by using the 00010 option of the NV parameter, see Figure 5-15. For
example, SIB6 contains UTRAN frequencies and UTRAN neighbor cells, so the UE
needs to support UTRAN.
68
Figure 5-15
5.3.9
UE Supported RAT Configuration
Deactivate feature
1.
Configuration > Security Management. Click
to modify the encryption and
decryption and integrity algorithms. Select the EEA0 and EIA0 algorithms to
deactivate the encryption and decryption functions.
69
2.
Configuration > Global Switch. Click
to modify the MME load balancing
switch on the S1 flex interface. Set Close[0] to deactivate the function.
5.3.10
Data Save and Synchronization

1.
After modified all the parameters, click
to save all the data.
2.
Select [Configuration Management->Data Synchronization] from the main menu

of the Configuration Management tab. The Data Synchronization dialog box opens.
First select NE, then select synchronization mode as Incremental synchronization,
then click Synchronize button.
Feature Validation
6.1
System Information Broadcasting Test
6.1.1
Topology
Topology is shown in Figure 6-1.
70
Figure 6-1
Topology for One Single eNodeB
eNB
IP bone
MME / S-GW
PGW
SGW / DHCP Relay
PDN Server
Test equipment is shown in Table 6-1.
Table 6-1
Test Equipment
SN
6.1.2
Test Equipment
Requirement
eNodeB
Number:1
UE
Number:1
MME
Number:1
PGW
Number:1
PDN server
Number:1
Test Specification
Table 6-2
System Information Broadcasting Test
Test Item
Test Purpose
System information broadcasting test

To verify the UE can acquire all of the MIB and SIBs transmitted
by the eNodeB.
1. EUTRAN works normally;
2. EPC works normally;
Preparations
3. Application server runs normally;

4. OMC works normally;
5. UE is prepared and works normally;
6. Test tools of eNodeB side and UE side are available;
Test Step
Expected Result
71
Test Item
Test Purpose

To verify the UE can acquire all of the MIB and SIBs transmitted
by the eNodeB.
Preparations

Test Step
Expected Result
Place UE to the coverage area of

test cell;
Open test tools to record UE log;
Power on UE and make sure that
the UE camps on the serving cell.
Check whether test log meet the
test requirement;
Save the log of UE side;
Test tool can trace and record the test

log of UE side
Cell ID of serving cell can be seen at
UE side;
MIB and SIB info can be seen in
System information message
Log is saved with the name of test
case;
1. System Information Broadcast process is listed as follow

UE
eNodeB
BCH:MIB
Anticipative
DL_SCH:SIB1
Result
DL_SCH:SI Messages
2. MIB information and SIB information can be received at UE

side;
6.1.3
Test Result
The UE can receive the MIB and SIB information correctly, see Figure 6-2~.
72
Figure 6-2
MIB
Figure 6-3
SIB1
Figure 6-4
SIB2
73
Figure 6-5
SIB3
6.2
Paging Test
6.2.1
Topology
Refer to section 6.1.1.
6.2.2
Test Specification
Table 6-3
Paging Test
Test Item
Test Purpose

To verify the UE can acquire paging message.
Preparations

Test Step
1
2
74
Expected Result

test cell;
Start test tool of eNodeB and UE
Test tools work normally.
Test Item
Test Purpose

To verify the UE can acquire paging message.
Preparations

Test Step
Expected Result
side to record the test log.

3
Power on UE and make sure that
Cell ID of serving cell can be seen at UE
the UE camps on the serving cell.
side;
Initiate Attach operation from UE

side.
Wait until the User inactivity timer
expires, and make sure that UE

enter idle mode.
UE access serving cell successfully;
RRC Connection Release Message can be

seen at UE side;
Initiate ping operation with
1 Ping operation is successful;
32Byte from PDN Server side to
2 Paging message is seen from UE
test UE;
side;
Stop ping operation.
Detach UE and save the log;
1.
Log is saved with the name of test case;
Paging process is listed as follow
UE
eNodeB
MME
Paging
Anticipative
RRC Connection Request
Result
RRC Connection Setup
RRC Connection Setup Complete
2. Paging process successful rate is 100%;
75
6.2.3
Test Result
Observe the UE log by CNT tool (or QXDM for Qualcomm UE). When UE received RRC
Connection Release message, the UE is in RRC idle state. Then initiate ping operation
with 32Byte from PDN Server side to test UE. The Paging message is received by UE,
see Figure 6-6.
Figure 6-6
UE received Paging message
6.3
E-RAB Test
6.3.1
Topology
6.3.2
Test Specification
Table 6-4
E-RAB Test
Test Item
Test Purpose

To verify that the UE can successfully establish, modify and
release an EPS bearer.
Preparations

Test Step
76
Expected Result

test cell;
Test Item
Test Purpose

Preparations

Test Step

Power on the UE and make sure
that the UE camps on the serving

cell.
Initiate and finish an attach

operation from the UE.
Establish 1 dedicated E-RAB
(GBR or NGBR) from MME.
Initiate and finish a ping operation
to application server from the UE

on this E-RAB.
Modify the QoS parameters of
the E-RAB from MME.

Release the dedicated E-RAB
from MME.
Expected Result
Test tools work normally;

UE side which is the same as the
serving cell.
The UE
attached.
has
been
successfully
E-RAB setup Request message can

be seen from UDT side.
The ping operation on the E-RABs is
successful
E-RAB Modify Request message can
be seen from UDT side.
E-RAB release Response message
can be seen from UDT side.
Record the signaling process of

UE operation upwards.
Anticipative
1.E-RAB setup process is list as follows:
Result
77
Test Item
Test Purpose

Preparations

Test Step
UE
Expected Result
eNodeB
MME
Serving
GW
PDN
GW
PCRF
PCRF Initiated IP-CAN Session Modification,begin

Create Bearer Request
Create Bearer Request
E-RAB Setup Request/Activate Dedicated EPS Bearer Context Request
RRC Connection Reconfiguration Complete
E-RAB Setup Response
Direct Transfer/Activate Dedicated EPS Bearer Context Accept
Uplink NAS Transport/Activate Dedicated EPS Bearer Context Accept
Create Bearer Response
Create Bearer Response
PCRF Initiated IP-CAN Session Modification,end
2. E-RAB modify process is list as follows:

UE
eNodeB
MME
Serving
GW
PDN
GW
PCRF
PCRF Initiated IP-CAN Session Modification,begin

Update Bearer Request
Update Bearer Request
E-RAB Modify Request/Modify EPS Bearer Context Request
RRC Connection Reconfiguration Complete
E-RAB Modify Response
Direct Transfer/Modify EPS Bearer Context Accept
Uplink NAS Transport/Modify EPS Bearer Context Accept
Update Bearer Response
Update Bearer Response
PCRF Initiated IP-CAN Session Modification,end
3.E-RAB release process is list as follows:
78
Test Item
Test Purpose

Preparations

Test Step
UE
Expected Result
eNodeB
MME
Serving
GW
PDN
GW
PCRF
HSS
IP-CAN Session Modification

Delete Bearer Request
Delete Bearer Request
E-RAB Release Command
Downlink NAS Transport/Deactivate EPS Bearer Context Request
Deactivate EPS Bearer Context Request
Radio Bearer Release Request
Radio Bearer Release Response
E-RAB Release Response
Direct Transfer/Deactivate EPS Bearer Context Accept
Uplink NAS Transport/Deactivate EPS Bearer Context Accept
Delete Bearer Response
Delete Bearer Response
IP-CAN Session Modification
6.3.3
Test Result
Test this item by Qualcomm UE and observe the log by QCAT tool. Select 0xB0C0
LTE RRC OTA Packet ,0xB0E2 LTE NAS ESM Plain OTA Incoming Message
and 0xB0E3
LTE NAS ESM Plain OTA Outgoing Message to see the EAB setup
process such as Figure 6-7.
79
Figure 6-7
E-RAB Setup Process
E-RAB modify process is seen in Figure 6-8.
Figure 6-8
E-RAB Modify Process
E-RAB release process is seen in Figure 6-9.
Figure 6-9
80
E-RAB Release Process
6.4
AS Security Management Test
6.4.1
Topology
6.4.2
Test Specification
Table 6-5
AS Security Management Test
Test Item
Test Purpose

To verify the function of integrity protection algorithms and
ciphering algorithms.
Preparations

Test Step
Configure the parameter Integrity

Protection Algorithm as EIA0.
position of serving cell.

that the UE camps on the serving

cell.
Initiate and finish an attach
operation from the UE.
The parameter configured successfully.
Place the UE to the centre
Power on the UE and make sure

4
Expected Result
Detach UE and Configure the

UE side which is the same as the
serving cell.
1) The UE has been successfully
attached.
2)
The
value
of
integrityProtAlgorithm IE in Security
Mode
Command
Message
is
reserved.
81
Test Item
Test Purpose

Preparations

Test Step
Expected Result
parameter Integrity Protection
attached.
Algorithm as 128-EIA1, then
2)
repeat steps 2 ~5.
IE in Security Mode Command
The value of integrityProtAlgorithm
Message is eia1.
Detach UE and Configure the
7
parameter Integrity Protection

Algorithm as 128-EIA2, then
repeat steps 2 ~5.

attached.
2)
The value of integrityProtAlgorithm
IE in Security Mode Command

Message is eia2.
Detach UE and configure the

attached.
parameter Encryption Algorithm
2)
as EEA0, then repeat steps 2 ~5.
in Security Mode Command Message is
The value of cipheringAlgorithm IE
eea0.
9

as 128-EEA1, then repeat steps
2 ~5.

as 128-EEA2, then repeat steps
2 ~5.
Anticipative
Result
82
2)

eea1.

10

attached.

attached.
2)

eea2.
1.
Signaling of Integrity Protection is listed as follow
Test Item
Test Purpose

Preparations

Test Step
UE
Expected Result
EUTRAN
SecurityModeCommand
SecurityModeComplete
6.4.3
Test Result
Test this item by using Qualcomm UE.
When Integrity Protection Algorithm is EIA0, the integrityProtAlgorithm IE is shown in
Figure 6-10
83
Figure 6-10
The Integrity Protection Algorithm is EIA0

Figure 6-11:
84
Figure 6-11

Figure 6-12.
85
Figure 6-12
When Encryption Algorithm is EIA0, the cipheringAlgorithm IE is shown in Figure 6-13.
86
Figure 6-13
The Encryption Algorithm is EIA0
87
Figure 6-14
88
Figure 6-15
6.5
S1 Interface Test
6.5.1
Topology
6.5.2
Test Specification
Table 6-6
S1 Interface Test
Test Item
Test Purpose
S1 interface test
To verify the function of S1 interface.
89

Preparations

6. Test tools of eNodeB side and Wireshark are available;
Test Step
Expected Result
Start test tool of eNodeB

1
and wirshark to record the
test log.
Trigger eNodeB send a
wrong message to MME,
2
such as a abstract syntax

error or transfer syntax
MME sends Error Indication message to

eNodeB after received the wrong message.
error.
Delete S1 link, then add
Message Flow:
S1 link to initiate the S1
eNodeB>MME
S1 Setup Request
setup procedure.
eNodeB<MME
S1 Setup Response
Reset eNodeB.
Message Flow:
eNodeB>MME
Reset
eNodeB<MME
Reset Acknowledge
Message Flow:
Modify the TA to initiate
5
eNodeB configuration
update procedure.
eNodeB>MME
eNB Configuration Update
eNodeB<MME
eNB Configuration Update
Acknowledge
Message Flow:
Modify MME Capacity to
eNodeB<MME
initiate MME configuration
Update
update procedure.
eNodeB>MME
MME Configuration
MME Configuration Update
Acknowledge
Message Flow:
Trigger Overload Start
7
message from MME to

eNodeB.
eNodeB<MME
Overload Start
eNodeB reduces the signaling load towards the

concerned MME.
90
Trigger Overload Stop
Message Flow:
message from MME to
eNodeB<MME
Overload Stop
S1 interface test
Test Item
Test Purpose
To verify the function of S1 interface.

Preparations

Test Step
eNodeB.
Expected Result
eNodeB ends overload status and resumed to
normal operation.
Anticipative
Result
6.5.3
All these message flows are collect.
Test Result
Observe the S1 message flows by using wireshark tool.
After MME received the wrong message from eNodeB, MME sends Error Indication
message to eNodeB, as shown in Figure 6-16.
91
Figure 6-16
Error Indication Message
S1 setup procedure is shown in Figure 6-17 and Figure 6-18.
Figure 6-17
92
S1 Setup Request message
Figure 6-18
S1 Setup Response message
eNodeB reset procedure is shown in Figure 6-19 and Figure 6-20.
93
Figure 6-19
94
Reset message
Figure 6-20
Reset Acknowledge message
eNodeB configuration update procedure is shown in Figure 6-21 and Figure 6-22.
95
Figure 6-21
96
eNodeB Configuration Update message
Figure 6-22
eNodeB Configuration Update Acknowledge message
MME configuration update procedure is shown in Figure 6-23 and Figure 6-24.
97
Figure 6-23
98
MME Configuration Update message
Figure 6-24
MME Configuration Update Acknowledge message
Overload procedure is shown in Figure 6-25 and Figure 6-26.
99
Figure 6-25
100
Overload Start message
Figure 6-26
Overload Stop message
6.6
X2 Interface Test
6.6.1
Topology
X2 interface test topology is shown in Figure 6-27.
101
Figure 6-27
X2 Interface Test Topology
IP bone
eNB1
MME / S-GW
PGW
SGW / DHCP Relay
eNB2
PDN Server
The test equipment requirement is listed in Table 6-7.
Table 6-7
X2 Interface Test Requirements

SN
6.6.2
Test Equipment
Requirement
eNodeB
Number:2
UE
Number:1
MME
Number:1
PGW
Number:1
PDN server
Number:1
Test Specification
Table 6-8
X2 Interface Test
Test Item
Test Purpose
X2 interface test
To verify the function of X2 interface.
Preparations

102
Test Step
Expected Result
Message Flow:
eNodeB1>eNodeB2
Modify the number of X2 SCTP

trigger X2 setup procedure.
X2 Setup
Request
eNodeB1<eNodeB2
X2 Setup
Response
Message Flow:
eNodeB1>eNodeB2
2
Reset eNodeB1 to trigger X2

SCTP reset procedure.
Reset
Request
eNodeB1<eNodeB2
Reset
Response
Configure Uplink ICIC Mode
3
Select Flag as Uplink Dynamic
Message Flow:
Frequency Domain ICIC to trigger
eNodeB1>eNodeB2
load information reporting
Information
Load
procedure.
Message Flow:
Block the cell of eNodeB1, then
4
unblock the cell to trigger the

eNodeB configuration update
eNodeB1>eNodeB2
Configuration Update
eNodeB1<eNodeB2
procedure.
eNB
eNB
Configuration Update Acknowledge

Configure the SON MLB policy
5
switch as open to trigger the

resource status procedure.
Anticipative
Result
6.6.3
eNodeB1>eNodeB2
Resource
Status Request
eNodeB1<eNodeB2
Resource
Status Response
All these message flows are collect.
Test Result
Observe the X2 message flows by using wireshark tool.
X2 setup procedure is shown in Figure 6-28 and Figure 6-29.
103
Figure 6-28
X2 Setup Request Message
Figure 6-29
X2 Setup Response Message
Reset procedure is shown in Figure 6-30 and Figure 6-31.
104
Figure 6-30
Reset Request Message
Figure 6-31
Reset Response Message
Load indication procedure is shown in Figure 6-32.
105
Figure 6-32
Load Indication Information
eNodeB configuration update procedure is shown in Figure 6-33 and Figure 6-34.
106
Figure 6-33
X2AP: eNB Configuration Update Message
Figure 6-34
X2AP: eNB Configuration Update Acknowledge Message
Resource status reporting procedure is shown in Figure 6-35, Figure 6-36 and Figure
6-37.
107
Figure 6-35 Resource Status Request Message
Figure 6-36
108
Resource Status Response Message
Figure 6-37
Resource Status Reporting Message
Related Counters, KPI and Alarms
7.1
Related Counters
Table 7-1
Related Counters
SN
1
Counter No.
C373200000
C373200001
C373200002
C373200003
C373200004
C373200005
Description
Number of Successful Mt-Access RRC
Establishment
Number of Mt-Access RRC Establishment
Failure due to Timeout
Failure due to ENODEB Admission Failure
Failure due to Other Reason
Number of Successful Mo-Signaling RRC
Establishment
Number of Mo-Signaling RRC Establishment
109
SN
7
10
11
12
13
14
Counter No.
C373200006
C373200007
C373200008
C373200009
C373200010
C373200011
C373200012
C373200013
15
Description
Number of Mo-Signalling RRC Establishment
Number of Mo-Signaling RRC Establishment
Number of Successful Mo-Data RRC
Establishment
Number of Mo-Data RRC Establishment
Number of Successful HighPriorityAccess
RRC Establishment
Number of HighPriorityAccess RRC
Establishment Failure due to Timeout
C373200014
Establishment Failure due to ENODEB

Admission Failure
16
17
18
19
20
21
22
23
110
C373200015
C373200016
C373200017
C373200018
C373200019
C373200020
C373200021
C373200022

Establishment Failure due to Other Reason
Number of Successful Emergency RRC
Establishment
Number of Emergency RRC Establishment
Number of RRC Connection Release due to
UserInactive Release
Number of RRC Connection Release by
MME due to UE Context Release
ENODEB due to Unavailable Resource
SN
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
Counter No.
C373200023
C373200024
C373210200
C373210201
C373210202
C373210203
C373210204
C373210205
C373210206
C373210207
C373210208
C373210209
C373210210
C373210211
C373210212
C373210213
C373210214
C373210215
Description
Number of RRC Connection Release due to
Cell Block or Reset
ENODEB due to Other Cause
Number of Initial QCI1 SAE Bearers
Successful Setup
Number of Initial QCI1 SAE Bearers Setup
Failures due to ENODEB Admission Failure
Failures due to Uu Interface Failure
Failures due to Security Failure
Failures due to Parameter Error
Failures due to Other Reason
Successful Setup
Successful Setup
111
SN
Counter No.
Description
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
112
C373210216
C373210217
C373210218
C373210219
C373210220
C373210221
C373210222
C373210223
C373210224
C373210225
C373210226
C373210227
C373210228
C373210229
C373210230
C373210231
C373210232

Successful Setup
Successful Setup
Successful Setup
SN
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
Counter No.
C373210233
C373210234
C373210235
C373210236
C373210237
C373210238
C373210239
C373210240
C373210241
C373210242
C373210243
C373210244
C373210245
C373210246
C373210247
C373210248
C373210249
C373210250
Description
Successful Setup
Successful Setup
Successful Setup
113
SN
Counter No.
Description
77
78
79
80
C373210251
C373210252
C373210253
C373210254
81

Number of Additional QCI1 SAE Bearers
Successful Setup
C373210255
Setup Failures due to ENODEB Admission

Failure
82
83
84
85
86
C373210256
C373210257
C373210258
C373210259
C373210260
87

Setup Failures due to Uu Interface Failure
Setup Failures due to Handover Trigger
Setup Failures due to Parameter Error
Setup Failures due to Other Reason
Successful Setup
C373210261

Failure
88
89
90
91
92
114
C373210262
C373210263
C373210264
C373210265
C373210266

Successful Setup
SN
Counter No.
93
Description
C373210267

Failure
94
95
96
97
98
C373210268
C373210269
C373210270
C373210271
C373210272
99

Successful Setup
C373210273

Failure
100
101
102
103
104
C373210274
C373210275
C373210276
C373210277
C373210278
105

Successful Setup
C373210279

Failure
106
107
108
C373210280
C373210281
C373210282

115
SN
109
110
Counter No.
C373210283
C373210284
111
Description
Successful Setup
C373210285

Failure
112
113
114
115
116
C373210286
C373210287
C373210288
C373210289
C373210290
117

Successful Setup
C373210291

Failure
118
119
120
121
122
C373210292
C373210293
C373210294
C373210295
C373210296
123

Successful Setup
C373210297

Failure
124
116
C373210298

SN
Counter No.
125
C373210299
126
C373210300
127
C373210301
128
C373210302
129
Description
Successful Setup
C373210303

Failure
130
C373210304
131
C373210305
132
C373210306
133
7.2
C373210307

Related KPI
Table 7-2
Related KPI
SN
KPI No.
Description
310500
RRC Establishment Success Rate
310501
E-RAB Setup Success Rate
310502
Initial E-RAB Accessibility
310503
Added E-RAB Accessibility
310504
E-RAB Drop Rate
310505
E-RAB Block Rate
310506
E-RAB Block Rate in Handover
311502
E-RAB Setup Success Rate in Cell,QCI=1
117
SN
7.3
KPI No.
Description
311503
10
311504
11
311505
12
311506
13
311507
14
311508
15
311509
16
311510
Related Alarms
None
Impact on Network
This feature is the basic function of L3 protocol (RRC, S1AP, X2AP) of eNodeB. It used
to supply the basic service of the signaling and user data transmission between UE and
eNodeB(RRC), eNodeB and eNodeB(X2AP), eNodeB and MME(S1AP) .
Abbreviations
For the acronyms and abbreviations, see LTE Glossary.
10
Appendix
10.1
Cell Definitions of System Information Broadcast
10.1.1
MasterInformationBlock
IE/Group Name
118
OMC Parameter
OMC Parameter Name
IE/Group Name
dl-Bandwidth
OMC Parameter
OMC Parameter Name
bandWidthDl(ExternalEUtranCellFDD)
Downlink system bandwidth
>phich-Duration
phichDuration
PHICH symbol length
>phich-Resource
ng
PHICH allocated group
phich-Config
calculation factor
10.1.2
SystemInformationBlockType1
IE/Group Name
OMC Parameter
OMC
Parameter
Name
cellAccessRelatedInfo
>plmn-IdentityList
>>plmn-Identity
>>>mcc
MCC
Broadcast
mobile country
code
>>>mnc
MNC
Broadcast
mobile network
code
>>cellReservedForOperatorUse
cellReservedForOptUse
Cell reserved for

operator
>trackingAreaCode
tac
Tracking area
code
>cellIdentity
eNBId
eNodeB ID
cellLocalId
Cell ID
Note: cellIdentity IE
consists of eNBId(high
20 bits) and
cellLocalId(low 8 bits)
>cellBarred
cellBarred
Cell barred
>intraFreqReselection
isIntraFreqReselection
Intra-Frequency
Cell Reselection
Indication
>csg-Indication
csgIndication
Enable access to
CSG cell
119
IE/Group Name
OMC Parameter
OMC
Parameter
Name
cellSelectionInfo
>q-RxLevMin
selQrxLevMin
Minimum
receiving RSRP
level during cell
selection
>q-RxLevMinOffset
qrxLevMinOfst
Minimum
receiving level
offset during cell
selection
p-Max
intraPmax
Maximum UE
transmission
power
freqBandIndicator
freqBandInd
Band indication
for frequency
schedulingInfoList
>si-Periodicity
periodicity
SI Periodicity
Sibn (n:{2,3,4,5,6,7})
Flag for Whether
>sib-MappingInfo
>>SIB-Type
SIBn is in
System
Information
nonCriticalExtension
>nonCriticalExtension
>>ims-EmergencySupport-r9
allowedAccessClasses
Emergency call
access indication
>>cellSelectionInfo-v920
>>>q-QualMin-r9
cellSelQqualMin
Minimum RSRQ
receiving level
during cell
selection
>>>q-QualMinOffset-r9
qQualminoffset
Minimum RSRQ
receiving level
offset during cell
selection
120
10.1.3
IE/Group Name
OMC Parameter
OMC Parameter
Name
ac-BarringInfo
>ac-BarringForEmergency
acBarringForEmergency
Urgent call access

parameters
>ac-BarringForMO-Signalling
>>ac-BarringFactor
acBarringFactor
Probability factor of
signaling access
>>ac-BarringTime
acBarringTime
Signaling access-deny
time
>>ac-BarringForSpecialAC
acBarringForSpecialAC
Access parameters of
signaling access level
>ac-BarringForMO-Data
>>ac-BarringFactor
acBarringFactorOrig
Probability factor of call

access
>>ac-BarringTime
acBarringTimeOrig
Call access-deny time
acBarringForSpecialACtOrig
Access parameters of
call access level
radioResourceConfigCommon
>rach-ConfigCommon
>>preambleInfo
>>>numberOfRA-Preambles
numberOfRAPreambles
Number of random
access preamble
signatures based on
contention conflict
>>>preamblesGroupAConfig
>>>>sizeOfRA-PreamblesGroupA
sizeOfRAPreamblesGroupA
Number of preamble
signatures in Group A
>>>>messageSizeGroupA
messageSizeGroupA
Message length of
random access
preamble group
>>>>
messagePowerOffsetGroupB
messagePowerOffsetGroupB
Transmission power
control margin of
Message 3 configured
by eNodeB
121
IE/Group Name
OMC Parameter
OMC Parameter
Name
>>powerRampingParameters
>>>powerRampingStep
powerRampingStep
PRACH power
ascending step
>>>preambleInitialReceivedTarge
preambleIniReceivedPower
tPower
PRACH initial
preamble transmission
power
>>ra-SupervisionInfo
>>>preambleTransMax
preambleTransMax
Maximum transmission
times of PRACH
preamble
>>>ra-ResponseWindowSize
raResponseWindowSize
Receiving search
window for random
access preamble
response
>>maxHARQ-Msg3Tx
maxHarqMsg3Tx
Maximum transmission
times of Message 3
>bcch-Config
>>modificationPeriodCoeff
modificationPeriodCoeff
BCCH modification
period
>pcch-Config
>>defaultPagingCycle
defaultPagingCycle
DRX cycle for paging
>>nB
nB
Paging Occasion
Factor
>prach-Config
>>rootSequenceIndex
rootSequenceIndex
Starting index of logical

root sequence to
generate 64 preamble
>>prach-ConfigInfo
>>>prach-ConfigIndex
prachConfigIndex
Transmission time
configuration of
random access
preamble
>>>highSpeedFlag
highSpeedFlag
Cell high-speed
attribute
122
IE/Group Name
OMC Parameter
OMC Parameter
Name
>>>zeroCorrelationZoneConfig
ncs
Cyclic shift parameters

based on logical root
sequence (Ncs)
>>>prach-FreqOffset
prachFreqOffset
Starting RB number of
random access
preamble
>pdsch-ConfigCommon
>>referenceSignalPower
cellReferenceSignalPower
Referenced signal
power of cell
>>p-b
pb
Signal power ratio
puschNsb
Number of sub-bands
>pusch-ConfigCommon
>>pusch-ConfigBasic
>>>n-SB
for PUSCH frequency

hopping
>>>hoppingMode
hoppingMode
PUSCH frequency
hopping mode
>>>pusch-HoppingOffset
puschhoppingOffset
PUSCH frequency
hopping offset
>>>enable64QAM
qam64DemSpIndUl
UL 64QAM
demodulation support
indicator
>pucch-ConfigCommon
>>deltaPUCCH-Shift
pucchDeltaShf
Cycle Shift Number for

PUCCH Format
1/1a/1b
>>nRB-CQI
pucchCqiRBNum
RB Number of PUCCH
Format 2/2a/2b
>>n1PUCCH-AN
pucchSemiAnNum
Number of Semi
pucchSrNum
Allocation Format 1
pucchAckRepNum
PUCCH;
Note: n1PUCCH-AN IE consists
the Number of SR
of pucchSemiAnNum
PUCCH;
, pucchSrNum, and
Number of Ack/Nack
Repetition PUCCH;
123
IE/Group Name
OMC Parameter
OMC Parameter
Name
pucchAckRepNum
>soundingRS-UL-ConfigComm
on
>>setup
srsEnable
Srs supported
>>>srs-BandwidthConfig
srsBWCfg
SRS Bandwidth
Configuration
>>>srs-MaxUpPts
SrsMaxUpPts
SrsMaxUpPts
poNominalPUSCH1
Cell nominal power
>uplinkPowerControlCommon
>>p0-NominalPUSCH
required for data

transmission in
PUSCH dynamic
scheduling
authorization mode
>>alpha
alpha(PowerControlUL)
Path loss
compensation factor
for PUSCH
transmission power
>>p0-NominalPUCCH
poNominalPUCCH
Related nominal power

used by PUCCH
physical channel
>>deltaFList-PUCCH
>>>deltaF-PUCCH-Format1
deltaFPucchFormat1
Physical channel
power compensation
for PUCCH Format 1
>>>deltaF-PUCCH-Format1b
deltaFPucchFormat1b
Physical channel
power compensation
for PUCCH Format 1b
>>>deltaF-PUCCH-Format2
deltaFPucchFormat2
Physical channel
power compensation
for PUCCH Format 2
>>>deltaF-PUCCH-Format2a
deltaFPucchFormat2a
Physical channel
power compensation
for PUCCH Format 2a
124
IE/Group Name
OMC Parameter
OMC Parameter
Name
>>>deltaF-PUCCH-Format2b
deltaFPucchFormat2b
Physical channel
power compensation
for PUCCH Format 2b
>>deltaPreambleMsg3
dtaPrmbMsg3
Power offset based on

PRACH message
>ul-CyclicPrefixLength
phyChCPSel
CP Selection for
Physical Channel for
Non-MBSFN
ue-TimersAndConstants
>t300
t300
Timer for UE to wait for

RRC connection
response (T300)
>t301
t301
Timer for UE to wait for

RRC re-connection
response (T301)
>t310
t310_Ue
Timer for UE to monitor

radio link failure
(T310_UE)
>n310
n310
Maximum number of
downlink
out-of-synchronization
indications (N310)
>t311
t311_Ue
Timer for UE to monitor

radio link failure to idle
(T311_UE)
>n311
n311
Maximum number of
downlink
synchronization
indications received by
UE (N311)
freqInfo
>ul-CarrierFreq
earfcnUl(EUtranCellFDD)
Uplink center carrier

frequency
>ul-Bandwidth
bandWidthUl(EUtranCellFDD)
Uplink system
bandwidth
125
IE/Group Name
OMC Parameter
OMC Parameter
Name
timeAlignmentTimerCommon
timeAlignTimer
Time alignment timer
voiceBarringFactor
Voice access-deny
lateNonCriticalExtension
>ssac-BarringForMMTEL-Voice
-r9
>>ac-BarringFactor
factor of multimedia
call
>>ac-BarringTime
voiceBarringTime
Voice access-deny
time of multimedia call
voiceBarForSpecAC
Voice access level of

multimedia call
>ssac-BarringForMMTEL-Video
-r9
>>ac-BarringFactor
videoBarringFactor
Video access-deny
factor of multimedia
call
>>ac-BarringTime
videoBarringTime
Video access-deny
time of multimedia call
videoBarForSpecAC
Video access level of

multimedia call
10.1.4
IE/Group Name
OMC Field Name
OMC Parameter
cellReselectionInfoCommon
>q-Hyst
qhyst
Reselection hysteresis of
serving cell
>speedStateReselectionPars
>>mobilityStateParameters
>>>t-Evaluation
tEvaluation
Time window length in

deciding
medium/high-speed
movement status
>>> t-HystNormal
tCrMaxHyst
Leaving duration of
medium/high-speed
126
IE/Group Name
OMC Field Name
OMC Parameter
movement status
>>> n-CellChangeMedium
nCellChangeMedium
Cell reselection times in

medium-speed movement
status
>>> n-CellChangeHigh
nCellChangeHigh
Cell reselection times in

high-speed movement
status
>>q-HystSF
>>>sf-Medium
qHystSFMedium
Additional hysteresis in
medium-speed movement
status
>>> sf-High
qHystSFHigh
Additional hysteresis in
high-speed movement
status
cellReselectionServingFreqInfo
>s-NonIntraSearch
sNintraSrchPre
Decision threshold of
same/lower priority RSRP
measurement
>threshServingLow
threshSvrLow
Lower threshold of serving

carrier
>cellReselectionPriority
cellReselectionPriority
Reselection priority of
intra-frequency cell
intraFreqCellReselectionInfo
>q-RxLevMin
intraQrxLevMin
Minimum receiving level of

intra-frequency cell
reselection
>p-Max
iIntraPmax
Maximum UE transmission
power of intra-frequency
reselection
>s-IntraSearch
sIntraSearch
RSRP decision threshold of

co-frequency measurement
>presenceAntennaPort1
intraPresenceAntPort1
Indicator for co-frequency

linked cell to use antenna
port 1
>t-ReselectionEUTRA
tReselectionIntraEUTRA
Reselection decision timer

duration of intra-frequency
127
IE/Group Name
OMC Field Name
OMC Parameter
cell
>t-ReselectionEUTRA-SF
>> sf-Medium
sfIntraMedium
Time scale factor for

co-frequency cell in
medium-speed status
>> sf-High
sfIntraHigh
Time scale factor for

co-frequency cell in
high-speed status
lateNonCriticalExtension
>s-IntraSearch-v920
>>s-IntraSearchP-r9
sIntraSearch
RSRP decision threshold of

co-frequency measurement
>>s-IntraSearchQ-r9
sIntraSrchQ
Intra-frequency decision
RSRQ threshold
>s-NonIntraSearch-v920
>>s-NonIntraSearchP-r9
snonintrasearch
same/lower priority RSRP
measurement
>>s-NonIntraSearchQ-r9
sNintraSrchQ
same/lower priority RSRQ
measurement
q-QualMin-r9
intraFreqQqualMin
Minimum value of
co-frequency RSRQ
threshServingLowQ-r9
threshSrvLowQ
RSRQ threshold (in dB) of

the serving cell when
reselecting towards a lower
priority RAT/ frequency
(Release 9)
10.1.5
IE/Group Name
OMC Field Name
OMC Parameter
intraFreqNeighCellList
>physCellId
pci
PCI
>q-OffsetCell
qofStCell
Cell Q-offset
intraFreqBlackCellList
128
10.1.6
IE/Group Name
OMC Field Name
OMC Parameter
interFreqCarrierFreqList
>dl-CarrierFreq
interCarriFreq(eutranRslPara)
Inter-frequency
> q-RxLevMin
interQrxLevMin
Minimum received RSRP

level during inter-frequency
reselection
> p-Max
interPmax
Maximum transmit power in

inter-frequency reselection
> t-ReselectionEUTRA
tReselectionInterEUTRA
The timer for cell reselection

in inter-frequency
> t-ReselectionEUTRA-SF
>>sf-Medium
sfInterMedium
Scaling factor for

inter-frequency reselection in
medium-speed
>>sf-High
sfInterHigh
Scaling factor for

inter-frequency reselection in
high-speed
> threshX-High
interThrdXHigh
RSRP threshold for

reselecting to inter-frequency
high priority cell
> threshX-Low
interThrdXLow
RSRP threshold for

reselecting to inter-frequency
low priority cell
> presenceAntennaPort1
interPresenceAntPort1
Switch for using antenna port

1 for inter-frequency cell
reselection
> cellReselectionPriority
interReselPrio
Inter-frequency cell
reselection priority
> q-OffsetFreq
qOffsetFreq
Inter-frequency offset
>>physCellId
pci
PCI
>>q-OffsetCell
qofStCell
Cell Q-offset
interFreqQqualMin
Minimum value of
> interFreqNeighCellList
> interFreqBlackCellList
> q-QualMin-r9
inter-frequency RSRQ
129
IE/Group Name
OMC Field Name
OMC Parameter
> threshX-Q-r9
>> threshX-HighQ-r9
interThreshXHighQ
RSRQ threshold for

reselecting higher priority
serving RAT cell
>> threshX-LowQ-r9
interThreshXLowQ
RSRQ threshold for

reselecting lower priority
serving RAT cell
10.1.7
IE/Group Name
OMC Field Name
OMC Parameter
carrierFreqListUTRA-FDD
>carrierFreq
utranCarriFreq
UTRAN FDD frequency
> cellReselectionPriority
utranReselPriority
UTRAN cell reselection

priority
> threshX-High
threshXHigh
Threshold for Reselecting to

High Priority UTRAN FDD
Cell
> threshX-Low
threshXLow
Threshold for reselecting to

low priority UTRAN FDD cell
> q-RxLevMin
qRxLevMin(utranRslPara)
Minimum required UTRAN

FDD cell RX level when cell
selection
> p-MaxUTRA
pMaxUTRA
Maximum allowed Tx power

of UE
> q-QualMin
qQualMin
Minimum quantity required

UTRAN FDD cell selection
> threshX-Q-r9
>> threshX-HighQ-r9
utranThreshXHighQFdd
RSRQ threshold for

reselecting higher priority
serving UTRAN cell
>> threshX-LowQ-r9
utranThreshXLowQFdd
RSRQ threshold for

reselecting lower priority
serving UTRAN cell
carrierFreqListUTRA-TDD
130
IE/Group Name
OMC Field Name
OMC Parameter
>carrierFreq
utranTDDCarriFreq
UTRAN TDD frequency
utranTDDReselPriority
UTRAN TDD cell reselection

priority
>threshX-High
threshXHighTDD
UTRAN TDD ThreshX_High
>threshX-Low
threshXLowTDD
UTRAN TDD ThreshX_Low
>q-RxLevMin
qRxLevMinTDD
UTRAN TDD qrxlevmin
>p-MaxUTRA
pMaxUtranTDD
Maximum TDD allowed Tx

power
t-ReselectionUTRA
reselUtran
The timer for cell reselection

in UTRAN FDD
t-ReselectionUTRA-SF
>sf-Medium
reselUtranSFM
Scale factor for UTRAN cell

reselection in medium-speed
>sf-High
reselUtranSFH
Scale factor for UTRAN cell

reselection in high-speed
10.1.8
IE/Group Name
t-ReselectionGERAN
OMC Field Name

tReselectionGERAN
OMC Parameter
Decision timer duration of
reselecting GERAN cell
t-ReselectionGERAN-SF
>sf-Medium
sfMediumGERAN
Time scale factor of

reselecting GERAN cell in
medium-speed status
>sf-High
sfHighGERAN
Time scale factor of

reselecting GERAN cell in
high-speed status
carrierFreqsInfoList
>carrierFreqs
>>startingARFCN
startARFCN(gsmRslPara)
the First ARFCN Value
>>bandIndicator
bandIndicator
Band Indicator
explicitARFCN
ARFCN detailed list
>>followingARFCNs(choice)
>>>explicitListOfARFCNs
131
IE/Group Name
OMC Field Name
OMC Parameter
>>> equallySpacedARFCNs
>>>>arfcn-Spacing
arfcnSpacing
Equally Spaced ARFCN

Value
>>>>numberOfFollowingARFCNs
followARFCNNum
the Number of the

Remaining Equally
Spaced ARFCN Values
commonInfo
geranReselectionPriority
Geran Cell Reselection

Priority
>q-RxLevMin
qRxLevMin(gsmRslPara)
Minimum Required
GERAN Cell RX Level
During Cell Selection
>threshX-High
geranThreshXHigh
Threshold for Reselecting

to High Priority GERAN
Cell
>threshX-Low
geranThreshXLow
Threshold for Reselecting

to Low Priority GERAN
Cell
10.1.9
IE/Group Name
OMC Parameter
OMC
Parameter
Name
searchWindowSize
searchWindowSize
Window size for

searching
neighbor pilot
parametersHRPD
> preRegistrationInfoHRPD
>> preRegistrationAllowed
isPreRegistAllowed
HRPD
Pre-registration
Indication
>> preRegistrationZoneId
preRegistrationZoneId
HRPD
pre-registration
area ID
>>secondaryPreRegistrationZoneIdList
132
IE/Group Name
OMC Parameter
OMC
Parameter
Name
>>> PreRegistrationZoneIdHRPD
secPreRegistrationZone
HRPD
Id
pre-registration
area secondary
ID
> cellReselectionParametersHRPD
>> bandClassList
>>> bandClass
hrpdBandClass
HRPD Band
Class
>>> cellReselectionPriority
hrpdReselPrio
HRPD Cell
Reselection
Priority
>>> threshX-High
hrpdThrdXHigh
Threshold for
Reselecting to
High Priority
HRPD Cell
>>> threshX-Low
hrpdThrdXLow
Threshold for
Reselecting to
Low Priority
HRPD Cell
>> neighCellList
>>> bandClass
BandClass
Frequency band
hrpdARNFCN
Carrier
>>> neighCellsPerFreqList
>>>> arfcn
frequency within
a CDMA2000
band
>>>>physCellIdList
>>>>> PhysCellIdCDMA2000
pNOffset
PN offset
>> t-ReselectionCDMA2000
reselHrpd
Decision timer
duration of
reselecting
CDMA HRPD
cell
>> t-ReselectionCDMA2000-SF
133
IE/Group Name
OMC Parameter
OMC
Parameter
Name
>>> sf-Medium
reselHrpdSFM
Time scale
factor of
reselecting
CDMA HRPD
cell in
medium-speed
status
>>> sf-High
reselHrpdSFH
Time scale
factor of
reselecting
CDMA HRPD
cell in
high-speed
status
parameters1XRTT
> csfb-RegistrationParam1XRTT
>> sid
oneXrttSID
1xRTT system
ID
>> nid
oneXrttNID
1xRTT network
ID
>> multipleSID
oneXrttMultSID
1xRTT
multi-SID
storage
supported
>> multipleNID
oneXrttMultNID
1xRTT
multi-NID
storage
supported
>> homeReg
oneXrttHomeReg
1xRTT local
registration
supported
>> foreignSIDReg
oneXrttForeSIDReg
1xRTT SID
roaming
registration
supported
134
IE/Group Name
OMC Parameter
OMC
Parameter
Name
>> foreignNIDReg
oneXrttForeNIDReg
1xRTT NID
roaming
registration
supported
>> parameterReg
oneXrttParaReg
1xRTT
parameter
change
registration
supported
>>powerUpReg
powerUpReg
1xRTT
power-on
registration
supported
>> registrationPeriod
oneXrttRegPeriod
1xRTT
registration
period
>> registrationZone
oneXrttRegZone
1xRTT
registration area
>> totalZone
oneXrttTotalZone
Number of
reserved 1xRTT
registration
areas
>> zoneTimer
oneXrttZoneTimer
1xRTT area
timer length
> cellReselectionParameters1XRTT
>> bandClassList
>>>bandClass
oneXrttBandClass
1XRTT Band
Class
>>> cellReselectionPriority
oneXrttReselPrio
1XRTT Cell
Reselection
Priority
>>> threshX-High
oneXrttThrdXHigh
Threshold for
Reselecting to
High Priority
1XRTT Cell
135
IE/Group Name
OMC Parameter
OMC
Parameter
Name
>>> threshX-Low
oneXrttThrdXLow
Threshold for
Reselecting to
Low Priority
1XRTT Cell
>> neighCellList
>>> bandClass
oneXrttBandClass
1XRTT Band
Class
>>> neighCellsPerFreqList
>>>> arfcn
oneXrttARFCN
Carrier
frequency within
a CDMA2000
band
>>>>physCellIdList
>> t-ReselectionCDMA2000
pNOffset
PN offset
tResel1Xrtt
Decision timer
duration of
reselecting
CDMA 1xRTT
cell
>> t-ReselectionCDMA2000-SF
>>> sf-Medium
tResel1XrttSFM
Time scale
factor of
reselecting
CDMA 1xRTT
cell in
medium-speed
status
>>> sf-High
tResel1XrttSFH
Time scale
factor of
reselecting
CDMA 1xRTT
cell in
high-speed
status
csfb-SupportForDualRxUEs-r9
136
csfbSuptDualRx
Switch for
IE/Group Name
OMC Parameter
OMC
Parameter
Name
CSFB
Supporting
DualRx UE
cellReselectionParametersHRPD-v920
> neighCellList-v920
>> neighCellsPerFreqList-v920
>>> NeighCellsPerBandclassCDMA2000-v920
>>>> physCellIdList-v920
pNOffset
PN offset
pNOffset
PN offset
oneXrttPowerDownRegI
CDMA2000
nd
power-off
cellReselectionParameters1XRTT-v920
> neighCellList-v920
>> neighCellsPerFreqList-v920
>>> NeighCellsPerBandclassCDMA2000-v920
>>>> physCellIdList-v920
csfb-RegistrationParam1XRTT-v920
> powerDownReg-r9
registration
supported
ac-BarringConfig1XRTT-r9
> ac-Barring0to9-r9
acBar0to9
AC-Barring 0-9
> ac-Barring10-r9
acBar10
AC-Barring 10
> ac-Barring11-r9
acBar11
AC-Barring 11
> ac-Barring12-r9
acBar12
AC-Barring 12
> ac-Barring13-r9
acBar13
AC-Barring 13
> ac-Barring14-r9
acBar14
AC-Barring 14
> ac-Barring15-r9
acBar15
AC-Barring 15
> ac-BarringMsg-r9
AC-barring
acBarMsg
factor for
message
137
IE/Group Name
OMC Parameter
OMC
Parameter
Name
transmission
> ac-BarringReg-r9
AC-barring
acBarReg
factor for
autonomous
registration
> ac-BarringEmg-r9
AC-barring
acBarEmg
factor for urgent

call/message
transmission
138

ZTE LTE FDD Connection Management Feature Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZTE LTE FDD Connection Management Feature Guide

Uploaded by

Copyright:

Available Formats

ZTE LTE FDD Connection

Management Feature Guide