Escolar Documentos
Profissional Documentos
Cultura Documentos
Date
2013-7-14
Author
Fu Ang
Wu Hao
Reviewer
Zhang Fan
Notes
The first edition
1.
V 2.0
2014-06-27
Fu Ang
Zhang Fan
Technical Details).
2.
3.
algorithms description.
Add Chapter 4.3.5 Context Fetch
V3.0
2014-11-24
Fu Ang
Zhang Fan
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
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
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
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
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
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
7
7.1
7.2
7.3
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
SystemInformationBlockType2 .........................................................................121
SystemInformationBlockType3 .........................................................................126
SystemInformationBlockType4 .........................................................................128
SystemInformationBlockType5 .........................................................................129
SystemInformationBlockType6 .........................................................................130
SystemInformationBlockType7 .........................................................................131
SystemInformationBlockType8 .........................................................................132
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
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
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
Feature Attribute
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
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
UE
eNodeB1
MME
eNodeB2
Active Phase
E-RAB Release
X2 Handover
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.
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.
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
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
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
eNodeB1
eNodeB2
X2-AP
X2-AP
SCTP
IP
SCTP
IP
L2
PHY
L2
PHY
L1
X2 Signalling
L1
X2
Figure 3-5
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.
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
4.1.1
10
Figure 4-1
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
eNodeB
UE
MME
System Information
Broadcast
Scheduler
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
Contents
MIB
SIB1
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
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
Change notification
Updated information
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
S1-AP: Paging
MME initiated
Determine cells in
which Paging
message should be
sent
Paging, PCCH
UE
4.2.1
eNode
B
MME
15
4.2.2
4.3
4.3.1
16
Figure 4-5
eNode
B
UE
MME
RRC_IDLE
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 CONNECTIO REQUEST message using the CCCH logical channel is
sent in transparent mode over SRB0.
3.
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.
17
6.
7.
8.
4.3.2
4.3.2.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
eNode
B
UE
RRC_CONNECTE
D
MME
Admission
Control
UE
eNode
B
MME
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.
4.
configuration,
including
intra-frequency
measurement,
6.
4.3.2.2
20
Figure 4-7
Source eNB /
IRAT RAN
UE
Target
eNodeB
UE
Source eNB /
IRAT RAN
Target
eNodeB
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.
3.
4.
21
4.3.3
The lower layer on the Uu interface of the UE detects a radio link failure.
2.
3.
4.
5.
Figure 4-8
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
22
2.
3.
4.
5.
6.
4.3.4
23
Figure 4-9
eNode
B
UE
MME
UE in Connected Mode
Release radio
resources
Enter RRC_IDLE
UE
eNode
B
MME
The RRC connection release procedure triggered by the MME is described as follows:
1.
2.
3.
The eNodeB releases the resources of the UE, including the S1 connection and
radio resources.
4.
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
UE
eNodeB-A
eNodeB-B
MME
SGW
Switch DL path
End marker
Packet data
End marker
11.S1AP: Path Switch Request Acknowledge
UE
eNodeB-A
eNodeB-B
MME
SGW
The RRC connection re-establishment procedure based on the context fetch function is
described as follows:
1.
2.
25
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.
7.
26
eNodeB-B.
8.
9.
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
27
4.5
UE Context Management
4.5.1
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)
RRC Connection Reconfiguration
Procedure
S1-AP: INTIAL CONTEXT SETUP
RESPONSE
UE
eNodeB
MME
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
The eNodeB initiates the AS security procedure. For details, refer to section 4.8 AS
Security Management.
4.
5.
After completing RAC and radio resource allocation, the eNodeB configures the Uu
interface and S1 interface protocols.
6.
7.
4.5.2
UE Context Release
4.5.2.1
29
Figure 4-11
UE
eNodeB
MME
UE in Connected Mode
UE
eNodeB
MME
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.
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
30
Figure 4-12
UE
eNodeB
MME
ALT
UE in Connected Mode
S1-AP: UE CONTEXT RELEASE
REQUEST
S1-AP: UE CONTEXT RELEASE
COMMAND
RRC CONNECTION RELEASE PROCEDURE
UE
eNodeB
MME
The MME triggers the UE context release procedure by itself or after receiving a
release request from the eNodeB.
2.
3.
4.
5.
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
eNodeB
MME
S1-AP: UE CONTEXT
MODIFICATION REQUEST
eNodeB
MME
ii.
iii.
In addition, the message includes the NAS signaling that the MME needs to
transmit to the UE.
2.
3.
The eNodeB initiates the RRC connection reconfiguration procedure. For details,
refer to section 4.3.2 RRC Connection Reconfiguration.
32
4.
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.
3.
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
VoIP with
QCI1+5 or 1
Streaming
service with
QCI7~9
Video with
QCI2+5 or 2
Streaming
service with
QCI6
SRB
1.
2.
3.
4.
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
UE
eNodeB
MME
eNodeB
MME
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.
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
eNodeB
MME
eNodeB
MME
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.
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
Figure 4-17
UE
MME
eNodeB
4.7.3.2
eNodeB
MME
37
Figure 4-18
UE
MME
eNodeB
eNodeB
MME
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.
4.7.4
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.
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
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
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
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
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.
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
Load Indication
2.
Error Indication
3.
X2 Setup
4.
Reset
5.
6.
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.
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.
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
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
2.
message.
50
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
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
Figure 5-7
15
Figure 5-7
16
Figure 5-7
17
Figure 5-7
18
Figure 5-7
19
Figure 5-7
20
Figure 5-7
21
Figure 5-7
51
5.2
22
Service priority
Figure 5-7
23
Figure 5-7
24
RLC type
Figure 5-7
25
Figure 5-7
26
PDCP SN length
Figure 5-7
27
Figure 5-7
28
Encryption algorithm
Figure 5-9
29
Figure 5-9
30
Figure 5-12
Description
Value Range
Default Value
SI Identity,lots of sib
1
SI Identity
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
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
SIB3 is in
SIB3 is in system
System
information.
Information
52
Flag for
5
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
SIB5 is in
SIB5 is in system
System
information.
Information
Flag for
7
Whether
SIB6 is in
SIB6 is in system
System
information.
Information
Flag for
8
Whether
SIB7 is in
SIB7 is in system
System
information.
Information
Flag for
9
Whether
SIB8 is in
SIB8 is in system
System
information.
Information
Flag for
10
Whether
SIB9 is in
SIB9 is in system
System
information.
Information
Flag for
11
Whether
SIB10 is in
SIB10 is in system
System
information.
Information
53
Flag for
12
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
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]
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
number of
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
parameter
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
packet qos
processed by the
loss
sender of a link
parameter
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
on-GBR)
RLC mode for
24
RLC type
application, includes
AM mode and UM
mode.
56
Service
factor for a
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
length
27
RLC
The parameter
sequence
gives the UM SN
number type
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
priority),128-EEA1(l
ow
priority),128-EEA3,1
28-EEA1(high
priority),
128-EEA2(medium
priority),128-EEA3(l
ow
priority),128-EEA1(h
igh priority),
128-EEA3(medium
28
Encryption
priority),128-EEA2(l
algorithm
ow
priority),128-EEA2(h
igh priority),
128-EEA1(medium
priority),128-EEA3(l
ow
priority),128-EEA2(h
igh
priority),128-EEA3(
medium
priority),128-EEA1(l
ow
priority),128-EEA3(h
igh
priority),128-EEA1(
medium
priority),128-EEA2(l
ow
priority),128-EEA3(h
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
priority),128-EEA1(Hig
h priority) and
128-EEA3(Medium
priority) and
128-EEA2(Low
priority),128-EEA2(Hig
h priority) and
EEA0[0]
128-EEA1(Medium
priority) and
128-EEA3(Low
priority),128-EEA2(Hig
h priority) and
128-EEA3(Medium
priority) and
128-EEA1(Low
priority),128-EEA3(Hig
h priority) and
128-EEA1(Medium
priority) and
128-EEA2(Low
priority),128-EEA3(Hig
h priority) and
128-EEA2(Medium
priority) and
128-EEA1(Low
priority))
128-EEA2(medium
58
priority),128-EEA1(l
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
priority),128-EIA3(lo
w
priority),128-EIA1(hi
gh
priority),128-EIA3(m
Integrity
29
protection
algorithm
edium
priority),128-EIA2(lo
w
priority),128-EIA2(hi
gh
priority),128-EIA1(m
edium
priority),128-EIA3(lo
w
priority),128-EIA2(hi
gh
priority),128-EIA3(m
edium
priority),128-EIA1(lo
w
priority),128-EIA3(hi
gh
priority),128-EIA1(m
edium
priority),128-EIA2(lo
w
priority),128-EIA3(hi
gh priority),
128-EIA2(medium
priority),128-EIA1(lo
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
priority),128-EIA1(Hig
h priority) and
128-EIA3(Medium
priority) and
128-EIA2(Low
priority),128-EIA2(Hig
h priority) and
EIA0[0]
128-EIA1(Medium
priority) and
128-EIA3(Low
priority),128-EIA2(Hig
h priority) and
128-EIA3(Medium
priority) and
128-EIA1(Low
priority),128-EIA3(Hig
h priority) and
128-EIA1(Medium
priority) and
128-EIA2(Low
priority),128-EIA3(Hig
h priority) and
128-EIA2(Medium
priority) and
128-EIA1(Low
priority))
59
30
Balancing, which
can determine
whether the MME
Close[0],Open[1]
Open[1]
Load Balancing
function is
performed or not.
5.3
5.3.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}
Figure 5-1
60
Figure 5-2
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.
Click Modify Area > Managed Element > Radio Parameter > LTE FDD > Cell
Reselection Configuration > UTRAN FDD Cell Reselection. Double-click the
record to add UTRAN frequencies for SIB6..
Figure 5-4
4.
Click Modify Area > Managed Element > Radio Parameter > LTE FDD > Cell
Reselection Configuration > GERAN Cell Reselection. Double-click the record to
add GERAN related information for SIB7..
62
Figure 5-5
5.
Click Modify Area > Managed Element > Radio Parameter > LTE FDD > Cell
Reselection Configuration > CDMA2000 SIB8 Content. Double-click the record to
add CDMA related information for SIB8..
Figure 5-6
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
ERAB Parameters
1. In the Configuration Management window on the EMS, click Modify Area >
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
Encryption Parameters
1.
In the Configuration Management window on the EMS, click Modify Area >
Managed Element > Radio Parameter > LTE FDD > E-UTRAN Service
Configuration > Security Management. Click
Figure 5-9
65
5.3.5
S1 Parameters
1. In the Configuration Management window on the EMS, click Modify Area >
Managed Element > Transmission Network > Signaling and Business > SCTP.
Click
Figure 5-10
Figure 5-11
66
S1AP Configuration
5.3.6
S1-Flex Parameters
1. In the Configuration Management window on the EMS, click Modify Area >
Managed Element > Radio Parameter > LTE FDD > E-UTRAN Service
Configuration > Global Switch. Click
Figure 5-12
5.3.7
X2 Parameters
1. In the Configuration Management window on the EMS, click Modify Area >
Managed Element > Transmission Network > Signaling and Business > SCTP.
Click
67
Figure 5-13
X2 SCTP Configuration
Figure 5-14
5.3.8
X2AP Configuration
68
Figure 5-15
5.3.9
Deactivate feature
1.
In the Configuration Management window on the EMS, click Modify Area >
Managed Element > Radio Parameter > LTE FDD > E-UTRAN Service
Configuration > Security Management. Click
decryption and integrity algorithms. Select the EEA0 and EIA0 algorithms to
deactivate the encryption and decryption functions.
69
2.
In the Configuration Management window on the EMS, click Modify Area >
Managed Element > Radio Parameter > LTE FDD > E-UTRAN Service
Configuration > Global Switch. Click
5.3.10
2.
Feature Validation
6.1
6.1.1
Topology
Topology is shown in Figure 6-1.
70
Figure 6-1
eNB
IP bone
MME / S-GW
PGW
PDN Server
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
Test Item
Test Purpose
Preparations
Expected Result
71
Test Item
Test Purpose
Preparations
Expected Result
eNodeB
BCH:MIB
Anticipative
DL_SCH:SIB1
Result
DL_SCH:SI Messages
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
Preparations
1
2
74
Expected Result
Test Item
Test Purpose
Preparations
Expected Result
side;
test UE;
side;
1.
UE
eNodeB
MME
Paging
Anticipative
Result
RRC Connection Setup
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
6.3
E-RAB Test
6.3.1
Topology
Refer to section 6.1.1.
6.3.2
Test Specification
Table 6-4
E-RAB Test
Test Item
Test Purpose
Preparations
76
Expected Result
Test Item
Test Purpose
Preparations
Expected Result
has
been
successfully
Anticipative
Result
77
Test Item
Test Purpose
Preparations
Expected Result
eNodeB
MME
Serving
GW
PDN
GW
PCRF
eNodeB
MME
Serving
GW
PDN
GW
PCRF
78
Test Item
Test Purpose
Preparations
Expected Result
eNodeB
MME
Serving
GW
PDN
GW
PCRF
HSS
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
79
Figure 6-7
Figure 6-8
Figure 6-9
80
6.4
6.4.1
Topology
Refer to section 6.1.1.
6.4.2
Test Specification
Table 6-5
Test Item
Test Purpose
Preparations
Expected Result
81
Test Item
Test Purpose
Preparations
Expected Result
attached.
2)
Message is eia1.
Detach UE and Configure the
7
2)
eea0.
Detach UE and configure the
9
Anticipative
Result
82
2)
1.
Test Item
Test Purpose
Preparations
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
84
Figure 6-11
85
Figure 6-12
86
Figure 6-13
87
Figure 6-14
88
Figure 6-15
6.5
S1 Interface Test
6.5.1
Topology
Refer to section 6.1.1.
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
Expected Result
test log.
Trigger eNodeB send a
wrong message to MME,
2
error.
Message Flow:
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
eNodeB<MME
Acknowledge
Message Flow:
eNodeB<MME
Update
update procedure.
eNodeB>MME
MME Configuration
Acknowledge
Message Flow:
Trigger Overload Start
7
eNodeB<MME
Overload Start
90
Message Flow:
eNodeB<MME
Overload Stop
S1 interface test
Test Item
Test Purpose
Preparations
eNodeB.
Expected Result
eNodeB ends overload status and resumed to
normal operation.
Anticipative
Result
6.5.3
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
Figure 6-17
92
Figure 6-18
93
Figure 6-19
94
Reset message
Figure 6-20
eNodeB configuration update procedure is shown in Figure 6-21 and Figure 6-22.
95
Figure 6-21
96
Figure 6-22
MME configuration update procedure is shown in Figure 6-23 and Figure 6-24.
97
Figure 6-23
98
Figure 6-24
99
Figure 6-25
100
Figure 6-26
6.6
X2 Interface Test
6.6.1
Topology
X2 interface test topology is shown in Figure 6-27.
101
Figure 6-27
IP bone
eNB1
MME / S-GW
PGW
eNB2
PDN Server
Table 6-7
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.
1. EUTRAN works normally;
2. EPC works normally;
Preparations
102
Test Step
Expected Result
Message Flow:
eNodeB1>eNodeB2
X2 Setup
Request
eNodeB1<eNodeB2
X2 Setup
Response
Message Flow:
eNodeB1>eNodeB2
2
Reset
Request
eNodeB1<eNodeB2
Reset
Response
Configure Uplink ICIC Mode
3
Message Flow:
eNodeB1>eNodeB2
Information
Load
procedure.
Message Flow:
Block the cell of eNodeB1, then
4
eNodeB1>eNodeB2
Configuration Update
eNodeB1<eNodeB2
procedure.
eNB
eNB
Anticipative
Result
6.6.3
eNodeB1>eNodeB2
Resource
Status Request
eNodeB1<eNodeB2
Resource
Status Response
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
Figure 6-29
104
Figure 6-30
Figure 6-31
105
Figure 6-32
eNodeB configuration update procedure is shown in Figure 6-33 and Figure 6-34.
106
Figure 6-33
Figure 6-34
Resource status reporting procedure is shown in Figure 6-35, Figure 6-36 and Figure
6-37.
107
Figure 6-36
108
Figure 6-37
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
Number of Mt-Access RRC Establishment
Failure due to ENODEB Admission Failure
Number of Mt-Access RRC Establishment
Failure due to Other Reason
Number of Successful Mo-Signaling RRC
Establishment
Number of Mo-Signaling RRC Establishment
Failure due to Timeout
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
Failure due to ENODEB Admission Failure
Number of Mo-Signaling RRC Establishment
Failure due to Other Reason
Number of Successful Mo-Data RRC
Establishment
Number of Mo-Data RRC Establishment
Failure due to Timeout
Number of Mo-Data RRC Establishment
Failure due to ENODEB Admission Failure
Number of Mo-Data RRC Establishment
Failure due to Other Reason
Number of Successful HighPriorityAccess
RRC Establishment
Number of HighPriorityAccess RRC
Establishment Failure due to Timeout
Number of HighPriorityAccess RRC
C373200014
16
17
18
19
20
21
22
23
110
C373200015
C373200016
C373200017
C373200018
C373200019
C373200020
C373200021
C373200022
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
Number of RRC Connection Release by
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
Number of Initial QCI1 SAE Bearers Setup
Failures due to Uu Interface Failure
Number of Initial QCI1 SAE Bearers Setup
Failures due to Security Failure
Number of Initial QCI1 SAE Bearers Setup
Failures due to Parameter Error
Number of Initial QCI1 SAE Bearers Setup
Failures due to Other Reason
Number of Initial QCI2 SAE Bearers
Successful Setup
Number of Initial QCI2 SAE Bearers Setup
Failures due to ENODEB Admission Failure
Number of Initial QCI2 SAE Bearers Setup
Failures due to Uu Interface Failure
Number of Initial QCI2 SAE Bearers Setup
Failures due to Security Failure
Number of Initial QCI2 SAE Bearers Setup
Failures due to Parameter Error
Number of Initial QCI2 SAE Bearers Setup
Failures due to Other Reason
Number of Initial QCI3 SAE Bearers
Successful Setup
Number of Initial QCI3 SAE Bearers Setup
Failures due to ENODEB Admission Failure
Number of Initial QCI3 SAE Bearers Setup
Failures due to Uu Interface Failure
Number of Initial QCI3 SAE Bearers Setup
111
SN
Counter No.
Description
Failures due to Security Failure
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
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
Number of Initial QCI6 SAE Bearers Setup
Failures due to Security Failure
Number of Initial QCI6 SAE Bearers Setup
Failures due to Parameter Error
Number of Initial QCI6 SAE Bearers Setup
Failures due to Other Reason
Number of Initial QCI7 SAE Bearers
Successful Setup
Number of Initial QCI7 SAE Bearers Setup
Failures due to ENODEB Admission Failure
Number of Initial QCI7 SAE Bearers Setup
Failures due to Uu Interface Failure
Number of Initial QCI7 SAE Bearers Setup
Failures due to Security Failure
Number of Initial QCI7 SAE Bearers Setup
Failures due to Parameter Error
Number of Initial QCI7 SAE Bearers Setup
Failures due to Other Reason
Number of Initial QCI8 SAE Bearers
Successful Setup
Number of Initial QCI8 SAE Bearers Setup
Failures due to ENODEB Admission Failure
Number of Initial QCI8 SAE Bearers Setup
Failures due to Uu Interface Failure
Number of Initial QCI8 SAE Bearers Setup
Failures due to Security Failure
Number of Initial QCI8 SAE Bearers Setup
Failures due to Parameter Error
Number of Initial QCI8 SAE Bearers Setup
Failures due to Other Reason
Number of Initial QCI9 SAE Bearers
Successful Setup
Number of Initial QCI9 SAE Bearers Setup
Failures due to ENODEB Admission Failure
Number of Initial QCI9 SAE Bearers Setup
113
SN
Counter No.
Description
Failures due to Uu Interface Failure
77
78
79
80
C373210251
C373210252
C373210253
C373210254
81
C373210255
82
83
84
85
86
C373210256
C373210257
C373210258
C373210259
C373210260
87
C373210261
88
89
90
91
92
114
C373210262
C373210263
C373210264
C373210265
C373210266
SN
Counter No.
93
Description
Number of Additional QCI3 SAE Bearers
C373210267
94
95
96
97
98
C373210268
C373210269
C373210270
C373210271
C373210272
99
C373210273
100
101
102
103
104
C373210274
C373210275
C373210276
C373210277
C373210278
105
C373210279
106
107
108
C373210280
C373210281
C373210282
115
SN
109
110
Counter No.
C373210283
C373210284
111
Description
Number of Additional QCI5 SAE Bearers
Setup Failures due to Other Reason
Number of Additional QCI6 SAE Bearers
Successful Setup
Number of Additional QCI6 SAE Bearers
C373210285
112
113
114
115
116
C373210286
C373210287
C373210288
C373210289
C373210290
117
C373210291
118
119
120
121
122
C373210292
C373210293
C373210294
C373210295
C373210296
123
C373210297
124
116
C373210298
SN
Counter No.
125
C373210299
126
C373210300
127
C373210301
128
C373210302
129
Description
Number of Additional QCI8 SAE Bearers
Setup Failures due to Handover Trigger
Number of Additional QCI8 SAE Bearers
Setup Failures due to Parameter Error
Number of Additional QCI8 SAE Bearers
Setup Failures due to Other Reason
Number of Additional QCI9 SAE Bearers
Successful Setup
Number of Additional QCI9 SAE Bearers
C373210303
130
C373210304
131
C373210305
132
C373210306
133
7.2
C373210307
Related KPI
Table 7-2
Related KPI
SN
KPI No.
Description
310500
310501
310502
310503
310504
310505
310506
311502
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
10.1.1
MasterInformationBlock
IE/Group Name
118
OMC Parameter
IE/Group Name
dl-Bandwidth
OMC Parameter
bandWidthDl(ExternalEUtranCellFDD)
>phich-Duration
phichDuration
>phich-Resource
ng
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
>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})
>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
SystemInformationBlockType2
IE/Group Name
OMC Parameter
OMC Parameter
Name
ac-BarringInfo
>ac-BarringForEmergency
acBarringForEmergency
>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
>>ac-BarringTime
acBarringTimeOrig
>>ac-BarringForSpecialAC
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
>>nB
nB
Paging Occasion
Factor
>prach-Config
>>rootSequenceIndex
rootSequenceIndex
>>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
>>>prach-FreqOffset
prachFreqOffset
Starting RB number of
random access
preamble
>pdsch-ConfigCommon
>>referenceSignalPower
cellReferenceSignalPower
Referenced signal
power of cell
>>p-b
pb
puschNsb
Number of sub-bands
>pusch-ConfigCommon
>>pusch-ConfigBasic
>>>n-SB
hoppingMode
PUSCH frequency
hopping mode
>>>pusch-HoppingOffset
puschhoppingOffset
PUSCH frequency
hopping offset
>>>enable64QAM
qam64DemSpIndUl
UL 64QAM
demodulation support
indicator
>pucch-ConfigCommon
>>deltaPUCCH-Shift
pucchDeltaShf
>>nRB-CQI
pucchCqiRBNum
RB Number of PUCCH
Format 2/2a/2b
>>n1PUCCH-AN
pucchSemiAnNum
Number of Semi
pucchSrNum
Allocation Format 1
pucchAckRepNum
PUCCH;
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
>uplinkPowerControlCommon
>>p0-NominalPUSCH
alpha(PowerControlUL)
Path loss
compensation factor
for PUSCH
transmission power
>>p0-NominalPUCCH
poNominalPUCCH
>>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
>ul-CyclicPrefixLength
phyChCPSel
CP Selection for
Physical Channel for
Non-MBSFN
ue-TimersAndConstants
>t300
t300
>t301
t301
>t310
t310_Ue
>n310
n310
Maximum number of
downlink
out-of-synchronization
indications (N310)
>t311
t311_Ue
>n311
n311
Maximum number of
downlink
synchronization
indications received by
UE (N311)
freqInfo
>ul-CarrierFreq
earfcnUl(EUtranCellFDD)
>ul-Bandwidth
bandWidthUl(EUtranCellFDD)
Uplink system
bandwidth
125
IE/Group Name
OMC Parameter
OMC Parameter
Name
timeAlignmentTimerCommon
timeAlignTimer
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
>>ac-BarringForSpecialAC
voiceBarForSpecAC
>ssac-BarringForMMTEL-Video
-r9
>>ac-BarringFactor
videoBarringFactor
Video access-deny
factor of multimedia
call
>>ac-BarringTime
videoBarringTime
Video access-deny
time of multimedia call
>>ac-BarringForSpecialAC
videoBarForSpecAC
10.1.4
SystemInformationBlockType3
IE/Group Name
OMC Parameter
cellReselectionInfoCommon
>q-Hyst
qhyst
Reselection hysteresis of
serving cell
>speedStateReselectionPars
>>mobilityStateParameters
>>>t-Evaluation
tEvaluation
>>> t-HystNormal
tCrMaxHyst
Leaving duration of
medium/high-speed
126
IE/Group Name
OMC Parameter
movement status
>>> n-CellChangeMedium
nCellChangeMedium
>>> n-CellChangeHigh
nCellChangeHigh
>>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
>cellReselectionPriority
cellReselectionPriority
Reselection priority of
intra-frequency cell
intraFreqCellReselectionInfo
>q-RxLevMin
intraQrxLevMin
>p-Max
iIntraPmax
Maximum UE transmission
power of intra-frequency
reselection
>s-IntraSearch
sIntraSearch
>presenceAntennaPort1
intraPresenceAntPort1
>t-ReselectionEUTRA
tReselectionIntraEUTRA
127
IE/Group Name
OMC Parameter
cell
>t-ReselectionEUTRA-SF
>> sf-Medium
sfIntraMedium
>> sf-High
sfIntraHigh
lateNonCriticalExtension
>s-IntraSearch-v920
>>s-IntraSearchP-r9
sIntraSearch
>>s-IntraSearchQ-r9
sIntraSrchQ
Intra-frequency decision
RSRQ threshold
>s-NonIntraSearch-v920
>>s-NonIntraSearchP-r9
snonintrasearch
Decision threshold of
same/lower priority RSRP
measurement
>>s-NonIntraSearchQ-r9
sNintraSrchQ
Decision threshold of
same/lower priority RSRQ
measurement
q-QualMin-r9
intraFreqQqualMin
Minimum value of
co-frequency RSRQ
threshServingLowQ-r9
threshSrvLowQ
10.1.5
SystemInformationBlockType4
IE/Group Name
OMC Parameter
intraFreqNeighCellList
>physCellId
pci
PCI
>q-OffsetCell
qofStCell
Cell Q-offset
intraFreqBlackCellList
128
10.1.6
SystemInformationBlockType5
IE/Group Name
OMC Parameter
interFreqCarrierFreqList
>dl-CarrierFreq
interCarriFreq(eutranRslPara)
Inter-frequency
> q-RxLevMin
interQrxLevMin
> p-Max
interPmax
> t-ReselectionEUTRA
tReselectionInterEUTRA
> t-ReselectionEUTRA-SF
>>sf-Medium
sfInterMedium
>>sf-High
sfInterHigh
> threshX-High
interThrdXHigh
> threshX-Low
interThrdXLow
> presenceAntennaPort1
interPresenceAntPort1
> 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 Parameter
> threshX-Q-r9
>> threshX-HighQ-r9
interThreshXHighQ
>> threshX-LowQ-r9
interThreshXLowQ
10.1.7
SystemInformationBlockType6
IE/Group Name
OMC Parameter
carrierFreqListUTRA-FDD
>carrierFreq
utranCarriFreq
> cellReselectionPriority
utranReselPriority
> threshX-High
threshXHigh
> threshX-Low
threshXLow
> q-RxLevMin
qRxLevMin(utranRslPara)
> p-MaxUTRA
pMaxUTRA
> q-QualMin
qQualMin
> threshX-Q-r9
>> threshX-HighQ-r9
utranThreshXHighQFdd
>> threshX-LowQ-r9
utranThreshXLowQFdd
carrierFreqListUTRA-TDD
130
IE/Group Name
OMC Parameter
>carrierFreq
utranTDDCarriFreq
>cellReselectionPriority
utranTDDReselPriority
>threshX-High
threshXHighTDD
>threshX-Low
threshXLowTDD
>q-RxLevMin
qRxLevMinTDD
>p-MaxUTRA
pMaxUtranTDD
t-ReselectionUTRA
reselUtran
t-ReselectionUTRA-SF
>sf-Medium
reselUtranSFM
>sf-High
reselUtranSFH
10.1.8
SystemInformationBlockType7
IE/Group Name
t-ReselectionGERAN
OMC Parameter
Decision timer duration of
reselecting GERAN cell
t-ReselectionGERAN-SF
>sf-Medium
sfMediumGERAN
>sf-High
sfHighGERAN
carrierFreqsInfoList
>carrierFreqs
>>startingARFCN
startARFCN(gsmRslPara)
>>bandIndicator
bandIndicator
Band Indicator
explicitARFCN
>>followingARFCNs(choice)
>>>explicitListOfARFCNs
131
IE/Group Name
OMC Parameter
>>> equallySpacedARFCNs
>>>>arfcn-Spacing
arfcnSpacing
>>>>numberOfFollowingARFCNs
followARFCNNum
commonInfo
>cellReselectionPriority
geranReselectionPriority
>q-RxLevMin
qRxLevMin(gsmRslPara)
Minimum Required
GERAN Cell RX Level
During Cell Selection
>threshX-High
geranThreshXHigh
>threshX-Low
geranThreshXLow
10.1.9
SystemInformationBlockType8
IE/Group Name
OMC Parameter
OMC
Parameter
Name
searchWindowSize
searchWindowSize
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
>>>>> PhysCellIdCDMA2000
>> 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
>>>>> PhysCellIdCDMA2000
pNOffset
PN offset
pNOffset
PN offset
oneXrttPowerDownRegI
CDMA2000
nd
power-off
cellReselectionParameters1XRTT-v920
> neighCellList-v920
>> neighCellsPerFreqList-v920
>>> NeighCellsPerBandclassCDMA2000-v920
>>>> physCellIdList-v920
>>>>> PhysCellIdCDMA2000
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
138