ZTE LTE FDD LR15 Basic Feature Description - 20161221

LTE FDD Basic Feature
Description
LR15
LTE FDD Basic Feature Description

Version Date Author Reviewer Notes
2016 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 Confidential & Proprietary 1

TABLE OF CONTENTS
1 System and Standards ...................................................................................... 7

1.1 3GPP Compliance ............................................................................................... 7
1.1.1 ZLF31-00-001 System Complying With 3GPP E-UTRAN R8 ............................... 7
1.1.2 ZLF31-00-002 System Complying With 3GPP E-UTRAN R9 ............................... 7
1.1.3 ZLF31-00-003 System Complying With 3GPP E-UTRAN R10 ............................. 8
1.1.4 ZLF31-00-004 E-UTRAN Interfaces ..................................................................... 9
1.1.5 ZLF31-00-005 Radio Channels (except EMBMS Channels) .............................. 14
1.1.6 ZLF31-00-006 Support UE Category 1~3........................................................... 16
1.1.7 ZLF31-00-015 System Improvements for 3GPP E-UTRAN R11 ........................ 17
1.2 UE Speed .......................................................................................................... 18
1.2.1 ZLF31-03-001 120KM/H .................................................................................... 18
1.3 Coverage ........................................................................................................... 18
1.3.1 ZLF31-04-001 Cell Radius: 15km ...................................................................... 18
2 Services and Radio Access Bearers .............................................................. 19

2.1.1 ZLF31-05-001 SRB1 and SRB2 for DCCH + 4 DRB Combination ..................... 19
2.1.2 ZLF31-05-008 Emergency Call .......................................................................... 20
3 Radio Network Functionality .......................................................................... 22

3.1 Connection Management ................................................................................... 22
3.1.1 ZLF31-06-001 System Information Broadcasting ............................................... 22
3.1.2 ZLF31-06-002 Paging ........................................................................................ 24
3.1.3 ZLF31-06-003 RRC Connection Management ................................................... 25
3.1.4 ZLF31-06-004 NAS Signaling Transfer .............................................................. 28
3.1.5 ZLF31-06-005 UE Context Management ........................................................... 29
3.1.6 ZLF31-06-006 UE Capability Enquiry ................................................................. 30
3.1.7 ZLF31-06-007 Radio Access Bearer Management ............................................ 31
3.1.8 ZLF31-06-008 S1 Interface Management .......................................................... 33
3.1.9 ZLF31-06-009 X2 Interface Management .......................................................... 35
3.1.10 ZLF31-06-010 S1-Flex ....................................................................................... 37
3.2 Mobility Management ......................................................................................... 39
3.2.1 ZLF31-07-001 Intra-LTE Cell Selection and Reselection.................................... 39
3.2.2 ZLF31-07-002 Intra-LTE Redirection.................................................................. 41
3.2.3 ZLF31-07-003 Intra-LTE Intra Frequency HO .................................................... 42
3.2.4 ZLF31-07-004 LTE->GERAN Cell Reselection .................................................. 43
3.2.5 ZLF31-07-005 LTE->GERAN Redirection .......................................................... 44
3.2.6 ZLF31-07-006 LTE->UTRAN Cell Reselection ................................................... 45
3.2.7 ZLF31-07-007 LTE->UTRAN Redirection .......................................................... 46
3.2.8 ZLF31-07-008 LTE->CDMA 1xRTT Cell Reselection ......................................... 47
2 ZTE Confidential & Proprietary

3.2.9 ZLF31-07-010 LTE->CDMA eHRPD Cell Reselection........................................ 47

3.2.10 ZLF31-07-011 LTE->CDMA eHRPD Redirection ............................................... 48
3.2.11 ZLF31-07-012 Intra-LTE Inter Frequency HO .................................................... 49
3.2.12 ZLF31-07-015 LTE->UTRAN PS Handover ....................................................... 51
3.2.13 ZLF31-07-016 UTRAN->LTE PS Handover ....................................................... 52
3.2.14 ZLF31-07-023 CSFB to UTRAN......................................................................... 53
3.3 Radio Resource Management............................................................................ 57
3.3.1 ZLF31-08-001 Radio Admission Control ............................................................ 57
3.3.2 ZLF31-08-004 Congestion Control ..................................................................... 58
3.3.3 ZLF31-08-005 Intra-LTE Load Balancing ........................................................... 59
3.3.4 ZLF31-08-008 LTE Load Control ....................................................................... 61
3.4 QoS Management .............................................................................................. 62
3.4.1 ZLF31-09-001 Standard QCI (19) .................................................................... 62
3.5 User Plane Processing....................................................................................... 63
3.5.1 ZLF31-10-001 MAC PDU and Functions ............................................................ 63
3.5.2 ZLF31-10-002 RLC PDU and Functions ............................................................ 64
3.5.3 ZLF31-10-003 PDCP PDU and Functions .......................................................... 65
3.5.4 ZLF31-10-004 Header Compression Profile 0x0000 .......................................... 66
3.5.5 ZLF31-10-005 Header Compression Profile 0x0001 .......................................... 67
3.6 Security Management ........................................................................................ 68
3.6.1 ZLF31-11-001 Integrity check (Reserved mode) ................................................ 68
3.6.2 ZLF31-11-002 Integrity check (128-EIA1) .......................................................... 69
3.6.4 ZLF31-11-004 Encryption/Decryption (EEA0) .................................................... 71
3.6.5 ZLF31-11-005 Encryption/Decryption (128-EEA1) ............................................. 72
3.7 Scheduling and Link Adaptation ......................................................................... 75
3.7.1 ZLF31-13-001 UL/DL HARQ .............................................................................. 75
3.7.2 ZLF31-13-002 Dynamic Scheduling ................................................................... 76
3.7.3 ZLF31-13-003 UL/DL Frequency Selective Scheduling ...................................... 77
3.7.4 ZLF31-13-009 QoS Scheduler ........................................................................... 78
3.7.5 ZLF31-13-011 Pseudo GBR for NGBR .............................................................. 79
3.7.6 ZLF31-13-012 Advanced AMC........................................................................... 80
3.7.7 ZLF31-13-013 PDCCH Link Adaptation ............................................................. 82
3.7.8 ZLF31-13-015 Enhanced Adaptive Intra-Mode MIMO Schemes ........................ 82
3.7.9 ZLF31-13-019 Static ICIC .................................................................................. 83
3.7.10 ZLF31-13-022 Advanced Operator Configurable QoS Scheduler ....................... 85
3.7.11 ZLF31-13-041 NI Based Interference Avoidance Scheduling ............................. 87
3.7.12 ZLF31-13-042 Small Packets Service Optimization ........................................... 87
3.7.13 ZLF31-13-043 TCP RTT Optimization................................................................ 88

3.8 Radio Part .......................................................................................................... 89

3.8.1 ZLF31-14-001 Basic Physical Layer Support ..................................................... 89
3.8.2 ZLF31-14-004 PRACH Format 0........................................................................ 90
3.8.3 ZLF31-14-008 UL QPSK/16QAM, DL QPSK/16QAM/64QAM ............................ 92
3.8.4 ZLF31-14-010 TX Diversity (2 Antennas) ........................................................... 93
3.8.5 ZLF31-14-011 Open Loop 2*2 Spatial Multiplexing (LD-CDD) ........................... 94
3.8.6 ZLF31-14-012 Closed Loop 2*2 Spatial Multiplexing .......................................... 95
3.8.7 ZLF31-14-013 Closed Loop 2*2 Spatial Multiplexing (Rank = 1) ........................ 96
3.8.8 ZLF31-14-021 Uplink 2-Ways MRC ................................................................... 97
3.8.9 ZLF31-14-022 Uplink 2-Ways IRC ..................................................................... 97
3.8.10 ZLF31-14-030 UL Open-Loop Power Control With FPC Supported ................... 98
4 Transport Network Functionality.................................................................. 100

4.1 Physical Interface............................................................................................. 100
4.1.1 ZLF32-00-001 FE/GE Interface ........................................................................ 100
4.2 Link Layer ........................................................................................................ 101
4.2.1 ZLF32-01-001 VLAN ........................................................................................ 101
4.2.2 ZLF32-01-002 VLAN Mapping ......................................................................... 103
4.3 Network Layer.................................................................................................. 104
4.3.1 ZLF32-02-001 DHCP ....................................................................................... 104
4.3.2 ZLF32-02-002 IPv4 Protocol Stack .................................................................. 105
4.3.3 ZLF32-02-005 IPv4 Address ............................................................................ 107
4.4 Traffic and QoS ................................................................................................ 108
4.4.1 ZLF32-03-001 Traffic Marking and Mapping .................................................... 108
4.4.2 ZLF32-03-005 Traffic Statistics ........................................................................ 112
4.5 Security............................................................................................................ 112
4.5.1 ZLF32-04-018 SFTP ........................................................................................ 112
4.5.2 ZLF32-04-019 SNMP ....................................................................................... 113
4.6 Synchronization ............................................................................................... 115
4.6.1 ZLF32-05-001 GPS Synchronization................................................................ 115
4.6.2 ZLF32-05-030 NTP Time Information............................................................... 116
5 SON Functionality ......................................................................................... 118

5.1 Self-Healing ..................................................................................................... 118
5.1.1 ZLF33-04-003 Software & Hardware Self-Healing ........................................... 118
5.1.2 ZLF33-04-004 Antenna Fault Diagnosis........................................................... 119
6 AAS ................................................................................................................ 120

6.1 ZLF36-00-001 Independent Uplink and Downlink Downtilts ............................. 120
7 Glossary ......................................................................................................... 121


FIGURES
Figure 3-1 Structure of System Information Blocks ............................................................23

Figure 3-2 S1-Flex .............................................................................................................38
Figure 3-3 CSFB architecture for UTRAN ..........................................................................55
Figure 3-4 Static Fractional FR ..........................................................................................85
Figure 3-5 Static Soft FR ...................................................................................................85
Figure 3-6 Random Access Preamble Format ...................................................................91
Figure 4-1 Basic Physical Interfaces ................................................................................101
Figure 4-2 VLAN Application for LTE ...............................................................................102
Figure 4-3 DHCP Application for an eNodeB ...................................................................105
Figure 4-4 LTE Transmission Protocol Stack ...................................................................106
Figure 4-5 Multi-IP-Address Configuration Scenario ........................................................108
Figure 4-6 LTE Traffic Model ...........................................................................................110
Figure 4-7 GPS Synchronization ......................................................................................116
TABLES
Table 1-1 Basic Logical Channels ......................................................................................15

Table 1-2 Transport Channels ...........................................................................................15
Table 1-3 Physical Channels .............................................................................................16
Table 2-1 Radio Bearer Combination (up to Four) .............................................................20
Table 3-1 Standard QCIs ...................................................................................................62
Table 3-2 Parameters of Different PRACH Formats ...........................................................91
Table 4-1 eNodeB Service Mapping Relationships ..........................................................110

1 System and Standards
1.1 3GPP Compliance
1.1.1 ZLF31-00-001 System Complying With 3GPP E-UTRAN R8
Dependency
Independent of peripheral NEs
Attribute
Basic function
Advantages
It supports the basic functions defined in 3GPP R8 FDD.
Description
3GPP R8 was launched in March 2009. As the first release for LTE, It completely defines
the basic functions of the LTE mobile communication system.
Introduced Version
LR13.2 and Before
Enhancement
LR14 supports 3GPP R10.
Dependency
Attribute

Basic function
Advantages
It supports the enhanced functions defined in 3GPP R9 FDD.
Description
3GPP R9, completed in March 2010, is an enhancement of 3GPP R8.
Introduced Version
LR13.2 and Before
Enhancement
LR14 supports 3GPP R10.
Dependency
Attribute
Basic function
Advantages
Description
3GPP R10, completed in Dec.2010, is a further enhancement of 3GPP R10.
Introduced Version
LR13.2 and Before
Enhancement

None
1.1.4 ZLF31-00-004 E-UTRAN Interfaces
Dependency
Attribute
Basic function
Advantages
It describes the connections between Network Elements (NEs) in E-UTRAN.
Description
ZTE eNodeB supports the following interfaces:
Interface between the eNodeB and the EPC
S1 is a logical interface between the eNodeB and the EPC. It can be divided into
the S1 user plane interface and the S1 control plane interface, both of which are
built in the IP layer in the transport network. The S1 user plane interface (S1-U) is
defined between the eNodeB and the S-GW. The S1 control plane interface
(S1-MME) is defined between the eNodeB and the MME.
S1 control plane:
E-RAB service management function
This function is used to set up, modify, and release System Architecture
Evolution (SAE) bearers triggered by the MME. The release of SAE bearers is
triggered by the eNodeB.
Initial context transfer function
This function is used to establish an S1 UE context in the eNodeB, establish

the default IP connectivity, establish one or more SAE bearers if requested by

the MME, and transfer Non-Access Stratum (NAS) signaling related

information to the eNodeB if needed.
Mobility functions for UEs in ECM-CONNECTED
Used to provide a change of eNodeBs within SAE/LTE (Handover

between the MME and the Serving SAE-GW) through the S1 interface.
Used to provide a change of RAN nodes between different RATs

(handover between the 3GPP and the RAT) through the S1 interface.
S1 paging function
This function provides the EPC with the capability to page a specific UE.
NAS signaling transport function between the UE and the MME:
Used to transfer NAS signaling related information and to establish the

S1 UE context in the eNodeB.
Used to transfer NAS signaling related information when the S1 UE

context in the eNodeB is already established.
S1 UE context release function
This function is used to manage the release of UE specific contexts in the

eNodeB and the MME.
Status Transfer
This function transfers PDCP SN Status information from the source eNodeB
to the target eNodeB in support of in-sequence delivery and duplication
avoidance for intra-LTE handovers.
S1 setup
Exchanging application level data is needed for the eNodeB and the MME to
interact on the S1 interface correctly. This procedure is used to erase any
existing application level configuration data in the two nodes and replaces it
with that received by any of the two nodes. This procedure also re-initializes

the E-UTRAN S1AP UE-related contexts (if any), and erases all related
signaling connections between the two nodes like a Reset procedure would
do.
Error indication
The purpose of the error indication procedure is to report detected logical

errors, if these errors cannot be reported through an appropriate failure
message. This procedure can be initiated by the MME or the eNodeB through
ERROR INDICATION messages.
Reset
The purpose of the reset procedure is to release all allocated resources on S1

and Uu to a UE upon receipt of a RESET message.
Configuration update
The purpose of the configuration update procedure is to update application

level configuration data needed for the eNodeB and the MME to interoperate
correctly on the S1 interface. This procedure does not affect the existing
UE-related contexts, if any.
UE capability info indication
The purpose of the UE capability info indication procedure is to enable the

eNodeB to provide the UE capability-related information and relevant
information updates. There is no need to inform the MME.
Location report
The MME requests the eNodeB to report where a UE is currently located by

sending a LOCATION REPORTING CONTROL message. On receipt of the
LOCATION REPORTING CONTROL message, the eNodeB performs the
requested location reporting control action for the UE.
S1 user plane:

S1 user plane mainly implements the GTP-U protocol that provides the packet
service for the user plane entities between the S-GW and the eNodeB, including:
Setup and release of GTP-U tunnels
UL/DL data unpacked, packed, and transmitted;
Path detection
Error indication
Interface between the eNodeBs.
X2 user plane and X2 control plane provide a logical interface between two
neighbour eNodeBs. This interface is built on the IP layer in the transport network.
1. X2 control plane:
Intra LTE mobility support for UE in ECM_CONNECTED
This function allows the eNodeB to move the responsibility of a certain UE to

another eNodeB. It includes context transfer from source eNodeB to target eNodeB,
control of user plane tunnels between source eNodeB and target eNodeB, and
Handover cancellation.
i. Load indication
i. The purpose of the load indication procedure is to transfer load and

interference co-ordination information between intra-frequency neighbor
eNodeBs. This procedure uses non-UE associated signaling.
An eNodeB initiates the procedure by sending a LOAD INFORMATION

message to an intra-frequency neighbor eNodeB.
ii. Error indication
The error indication procedure is initiated by an eNodeB to report detected

errors in one incoming message, if they cannot be reported by an appropriate
failure message.
iii. X2 setup

An eNodeB initiates the procedure by sending an X2 SETUP REQUEST

message to a candidate eNodeB. The candidate eNodeB replies with an X2
SETUP RESPONSE message. The initiating eNodeB transfers a list of served
cells to the candidate eNodeB. The candidate eNodeB replies with a list of its
served cells.
iv. Reset
The procedure is initiated with a RESET REQUEST message sent from

eNodeB1 to eNodeB2. Upon receipt of this message, eNodeB2 shall abort any
other ongoing procedures over the X2 interface between eNodeB1 and
eNodeB2. The eNodeB2 shall delete all the context information related to the
eNodeB1 including the X2AP ID for the contexts. After completion of release of
the resources, the eNodeB2 shall respond with a RESET RESPONSE
message.
v. eNodeB configuration update
An eNodeB initiates the procedure by sending an ENODE-B

CONFIGURATION UPDATE message to a peer eNodeB. Upon receipt of the
ENODE-B CONFIGURATION UPDATE message, the peer eNodeB updates
cell information accordingly and replies with an ENODE-B CONFIGURATION
UPDATE ACKNOWLEDGE message to inform the initiating eNodeB that the
requested update of application data was performed successfully. If the peer
eNodeB cannot accept the update, it shall respond with an ENODEB
CONFIGURATION UPDATE FAILURE message containing an appropriate
cause value.
2. X2 user plane:
X2 user plane implements the GTP-U protocol that provides the packet service
for user plane entity between eNodeBs, including:
Setup and release GTP-U tunnel
UL/DL data unpacked, packed and transmitted

Path detection
Error indication
Introduced Version
LR13.2 and Before
Enhancement
None
1.1.5 ZLF31-00-005 Radio Channels (except EMBMS Channels)
Dependency
Attribute
Basic function
Advantages
It describes the bearer capability for the LTE services.
Description
Logical channels, transport channels, and physical channels are defined in 3GPP
protocol. All channel types supported by ZTE eNodeB are described as follows:
Logical channels
Logical channels are Service Access Points (SAPs) between the MAC layer and the RLC
layer. The MAC layer provides data transfer services on logical channels. A set of logical
channel types is defined by different types of data transfer services. Each logical channel
type is defined by the type of information transferred.

Table 1-1 Basic Logical Channels
Abbreviation Name Description
BCCH Broadcast Control Carries cell broadcast information

Channel
PCCH Paging Control Carries paging information

Channel
CCCH Common Control Carries RRC signaling RB0

Channel
DCCH Dedicated Control Carries RRC signaling RB1 and RB2.

Channel
DTCH Dedicated Traffic Carries service RB.

Channel
Transport channels
Transport channels are SAPs between the MAC layer and Layer 1.
Table 1-2 Transport Channels
DL-SCH DL Shared Channel Carries user data and RRC signaling in the
LTE service.
BCH Broadcast Channel Carries cell broadcast information.
RACH Random Access Carries random access control information

Channel in uplink.
UL-SCH UL Shared Channel Carries user data and RRC signaling in the
LTE service.
PCH Paging Channel Carries paging information.
Physical channels
An uplink/downlink physical channel corresponds to a set of resource elements

carrying information originated from higher layers. The mapping between transport
channels and physical channels can be divided into uplink and downlink.

Table 1-3 Physical Channels
PBCH Physical Broadcast Carries the BCH transport channel.

Channel
PCFICH Physical Control Informs the UE of the number of OFDM

Format Indicator symbols used for the PDCCHs.
Channel
PDCCH Physical Downlink Informs the UE of resource allocation and

Control Channel Hybrid ARQ information related to
DL-SCH.
PHICH Physical Hybrid Carries Hybrid ARQ ACK/NACKs in

ARQ Indicator response to uplink transmissions.
Channel
PDSCH Physical Downlink Carries the DL-SCH transport channel.

Shared Channel
PUCCH Physical Uplink Carries uplink physical layer control

Control Channel signaling
PUSCH Physical Uplink Carries the UL-SCH transport channel

Shared Channel
PRACH Physical Random Carry the random access preamble.

Access Channel
Introduced Version
LR13.2 and Before
Enhancement
None
1.1.6 ZLF31-00-006 Support UE Category 1~3
Dependency
Attribute

Basic function
Advantages
It describes the UE category support capability in ZTEs eNodeB.
Description
ZTE eNodeB supports a peak downlink throughput of 100Mbps and a peak uplink
throughput of 50 Mbps for category-1, category-2, and category-3 (default) UEs.
Introduced Version
LR13.2 and Before
Enhancement
None
1.1.7 ZLF31-00-015 System Improvements for 3GPP E-UTRAN R11
Dependency
None
Attribute
Basic function
Advantages
Description
3GPP R11, functional freeze in March.2013, is a further enhancement of 3GPP R10.
Introduced Version
LR15

Enhancement
None
1.2 UE Speed
1.2.1 ZLF31-03-001 120KM/H
Dependency
None
Attribute
Basic function
Advantages
This feature supports high-speed UEs.
Description
ZTE eNodeB supports high-speed UE with the speed up to 120 km/h.
Introduced Version
LR13.2 and Before
Enhancement
None
1.3 Coverage
1.3.1 ZLF31-04-001 Cell Radius: 15km
Dependency

None
Attribute
Basic function
Advantages
This feature supports a maximum cell radius of 15 km in small cell scenarios for LTE
service coverage.
Description
Four PRACH preamble formats are defined in 3GPP TS36.211. For format 0, the
supported cell radius is up to 15 km, which is used in small cell scenarios for LTE service
coverage.
Introduced Version
LR13.2 and Before
Enhancement
None
2 Services and Radio Access Bearers
2.1.1 ZLF31-05-001 SRB1 and SRB2 for DCCH + 4 DRB Combination
Dependency
None
Attribute
Basic function
Advantages

This feature supports a maximum of four concurrent bearers per UE to improve user
experience.
Description
This feature supports a maximum of four concurrent bearers per UE. For the detailed
bearer combinations, refer to 3GPP TS 36.523-1.
Table 2-1 Radio Bearer Combination (up to Four)
Radio Bearer Combination

SRB1 and SRB2 for DCCH + 1xAM DRB
SRB1 and SRB2 for DCCH + 1xAM DRB + 1xUM DRB
Introduced Version
LR13.2 and Before
Enhancement
None
2.1.2 ZLF31-05-008 Emergency Call
Dependency
UE: supports the IMS emergency call function
CN: supports the IMS emergency call function
Attribute

Basic function
Advantages
This feature provides the emergency call service in the LTE network for crucial scenarios,
such as anti-terrorist missions, medical emergency assistance, fire fighting, and natural
disaster rescue.
Description
This feature is based on IMS entity deployment.
In SystemInformationBlockType1, the eNodeB indicates whether the local cell supports

emergency call services for UEs in limited service mode. A UE can obtain the capability
of supporting IMS emergency calls on the network through the system broadcast
messages. If the network supports the IMS emergency call service, the UE can inform
the network that it initiates an emergency call service by containing the emergency call
cause value during RRC connection setup procedure. The network processes this
service with high priority. The UE's IMS emergency call request is sent to the P-CSCF
functional entity in the IMS network through the eNodeB on the access network and the
EPC core network.
Introduced Version
LR13.2 and Before
Enhancement
None

3 Radio Network Functionality
3.1 Connection Management
3.1.1 ZLF31-06-001 System Information Broadcasting
Dependency
None
Attribute
Basic function
Advantages
This feature enables a UE to obtain the latest system information such as the network
identification, cell selection and reselection parameters, initial access parameters, and
neighbor cell parameters.
Description
The eNodeB is responsible for creating and broadcasting system information to UEs of a
cell that are in RRC_IDLE or RRC_CONNECTED mode. This feature enables the UEs to
obtain the latest system information such as the network identification, cell selection and
reselection parameters, initial access parameters, and neighbor cell parameters. When a
parameter related to the system information is changed, the eNodeB informs the UEs in
RRC_IDLE and the UEs in RRC_CONNECTED mode through a paging message.
System information is divided into the Master Information Block (MIB) and a number of
System Information Blocks (SIBs). The MIB provides UEs with several most essential
parameters that are needed for the UEs to acquire other information from the cell. Each
type of SIB contains a specific collection of information. SystemInformationBlockType1
(SIB1) contains the information for checking whether a UE is allowed to access a cell and
for defining the scheduling of other SIB information.

Figure 3-1 Structure of System Information Blocks
Master
Information
Block
System
Information
Block 1
System System System

Information Information ... Information
Block 2 Block 3 Block N
The MIB is repeatedly transmitted within a fixed scheduling period of 40ms. SIB1 is
transmitted repeatedly within a fixed scheduling period of 80ms. Other SIBs are
configured flexibly through SIB1. Each SIB can be contained only in one SI message.
Only the SIBs with the same scheduling period can be mapped in the same SI message,
In addition, SIB2 is mapped in the first SI message in the SI message list in the
corresponding scheduling information.
Each SIB in the system information supported by the eNodeB contains different kinds of
information:
SIB1 contains information for determining whether a UE is allowed to access a cell

and defines the scheduling of other system information blocks.
SIB2 contains information about public radio resource configurations in a cell.
SIB3 contains cell re-selection information that is irrelevant to cell re-selection

types.
SIB4 contains information about the intra-frequency neighbor cells relevant to cell
re-selection.
SIB5 contains information about the inter-frequency neighbor cells relevant to cell
re-selection.

SIB6 contains information about the UTRAN neighbor cells relevant to cell
re-selection.
SIB7 contains information about the GERAN neighbor cells relevant to cell
re-selection.
SIB8 contains information about the CDMA neighbor cells relevant to cell
re-selection.
Also, eNodeB support configuring and broadcasting Cell Barring information through
SIB1. At the same time, eNodeB support configuring and broadcasting Access Class
Barring (AC Barring) information through SIB2.
Introduced Version
LR13.2 and Before
Enhancement
In LR17 version, eNodeB support configuring and broadcasting Access Class Barring
Skipping (AC Barring Skip) for VoLTE service. When the network is in high load status,
eNodeB can broadcast AC Barring information. However, AC Barring will affect all type of
service since they do not distinguish the service type. In R12, AC Barring Skip
mechanism is supported to allow VoLTE service to skip AC Barring, thereby guarantee
VoLTE service experience.
3.1.2 ZLF31-06-002 Paging
Dependency
None
Attribute
Basic function
Advantages

This feature is used to page an UE in a cell or inform UEs of the change of the system
information.
Description
The network initiates a paging procedure to interact and communicate with a UE in

RRC_IDLE mode. Both the MME and eNodeB can initiate a paging procedure:
When the CN needs to send data (service or signaling) to a UE in RRC_IDLE mode,

the CN sends a paging message to the UE. After receiving this message, the UE
initiates an RRC connection establishment procedure to set up a link to the network
for data interaction.
When the system information is changed in eNodeB, the eNodeB sends paging
messages to inform the UEs in RRC_IDLE mode and the UEs in
RRC_CONNECTED mode of the change of the system information.
Introduced Version
LR13.2 and Before
Enhancement
None
3.1.3 ZLF31-06-003 RRC Connection Management
Dependency
None
Attribute
Basic function
Advantages
This feature manages the RRC connections between UEs and eNodeBs.
Description

RRC Connection Management is in charge of the RRC connections between UEs and
eNodeBs. RRC Connection Management includes RRC connection establishment, RRC
connection re-establishment, RRC connection reconfiguration, RRC connection release,
and RRC Connection rejection.
RRC connection establishment
The purpose of this procedure is to establish an RRC connection between a UE and

an eNodeB. RRC connection establishment involves Signaling Radio Bearer (SRB1)
establishment and transferring of initial NAS signaling message from the UE to the
eNodeB.
RRC connection re-establishment
The purpose of this procedure is to re-establish an RRC connection, which involves

the resumption of SRB1 operation and the re-activation of security. The connection
re-establishment will succeed only if the cell has a valid UE context. In the following
occasions, the UE initiates an RRC Connection Re-establishment procedure:
UE detecting a radio link failure
Intra-system handover failure
Inter-system handover failure
Integrity check failure
RRC connection reconfiguration failure
RRC connection reconfiguration
This procedure is performed to modify an RRC connection, for example, to

establish, modify, or release radio bearers, to perform handovers, and to configure
or modify measurements. As a part of the procedure, NAS dedicated information
may be transmitted from the network to the UE.
The eNodeB initiates the following RRC connection reconfiguration procedure to a

UE in RRC_CONNECTED mode:

The RRCConnectionReconfiguration message contains MobilityControlInfo

only when AS-layer security has been activated. In this case, SRB2 and at
least one DRB are established, and they will not be suspended.
The RRCConnectionReconfiguration message contains RB establishment

information (excluded SRB1, which has been established during the setup of
the RRC connection).
RRC connection release
This procedure is performed to release an RRC connection, including the release of

the established radio bearers and the release of all radio resources. After the RRC
connection is released there is no RRC connection between the UE and the
eNodeB anymore, and the UE enters RRC_IDLE mode. This procedure also may
be performed to re-direct the UE to the specified LTE frequency point or the cell of
other system frequency point.
The eNodeB initiates the RRC connection release procedure in the following
scenarios:
The eNodeB receives a UE Context Release Command from the MME.
The eNodeB initiates the RRC connection release procedure because a flow
failure occurs on the eNodeB.
RRC connection reject
This procedure is performed to reject an RRC Connection Request from a UE.
Introduced Version
LR13.2 and Before
Enhancement
None

3.1.4 ZLF31-06-004 NAS Signaling Transfer
Dependency
None
Attribute
Basic function
Advantages
This feature enables NAS signaling information interaction between UEs and the CN.
Description
The NAS signaling transfer function is used to transport NAS messages between a
specific UE and the MME on the S1 interface and the Uu interface. The NAS message
includes the service request, authentication, and Tracking Area (TA) update messages.
The RRC connection reconfiguration, RRC connection setup complete, DL information

transfer, and UL information transfer messages are used for containing NAS information
over the UU interface.
The Initial UE Message, Downlink NAS Transport, and Uplink NAS Transport messages
are used for containing NAS information over the S1 interface.
The NAS messages are not parsed by the eNodeB. The NAS Transport procedure may
use an existing UE-associated logical S1-connection. If no UE-associated logical
S1-connection exists, the establishment of the UE-associated logical S1-connection is
initiated (and may be established) as part of the procedure.
The eNodeB sends a NAS Non Delivery Indication message to the MME over the S1
interface in one of the following cases:
The eNodeB decides not to start the delivery of a NAS message that has been
received over an UE-associated logical S1-connection;
The eNodeB is unable to ensure that the NAS message has been received by the
UE.

Introduced Version
LR13.2 and Before
Enhancement
None
3.1.5 ZLF31-06-005 UE Context Management
Dependency
None
Attribute
Basic function
Advantages
This feature enables UE information management between the eNodeB and the EPC.
Description
The context management function includes the Initial Context Setup, UE Context
Release, and UE Context Modification procedures.
Initial UE Context Setup
This procedure is performed to establish the necessary overall initial UE Context

including E-RAB context, the Security Key, Handover Restriction List, UE Radio
Capability, and UE Security Capabilities. The procedure uses UE-associated
signaling. If no UE-associated logical S1-connection exists, the UE-associated
logical S1-connection shall be established on receipt of the INITIAL CONTEXT
SETUP REQUEST message.
UE Context Modification

This procedure is performed to partly modify the established UE Context, for

example, Security Key, SPID, AMBR, and CSFB indication. The procedure uses
UE-associated signaling.
UE Context Release
This procedure can be triggered by the eNodeB or the MME.
Initiated by the eNodeB
This procedure is performed to enable the eNodeB to request the MME to

release the UE-associated logical S1-connection due to eNodeB-generated
reasons (such as timer expiry). The procedure uses UE-associated signaling.
Initiated by the MME
This procedure is performed to enable the MME to order the release of the
UE-associated logical connection due to various reasons, for example,
completion of successful handover, or release of the old UE-associated logical
S1-connection when two UE-associated logical S1-connections to the same
UE is detected after the UE has initiated the establishment of a new
UE-associated logical S1-connection. The procedure uses UE-associated S1
connection.
Introduced Version
LR13.2 and Before
Enhancement
None
3.1.6 ZLF31-06-006 UE Capability Enquiry
Dependency
None
Attribute

Basic function
Advantages
This feature enables the UE to transfer its radio capability related information to the
network.
Description
This feature enables the radio access capability information of UE to be transferred from
the UE to the eNodeB.
During the Initial UE Context Setup procedure, when the MME has not stored the UE
radio access capability, the eNodeB sends a UE Capability Enquiry message to request
the UE to report its radio access capability information. On receipt of the radio access
capability information about the UE, the eNodeB sends this information in a UE
Capability Info Indication message to the MME.
If the UE has changed its radio access capability, the UE initiates the NAS procedure to
establish a new RRC connection to inform the network of the updated UE radio access
capability information.
Introduced Version
LR13.2 and Before
Enhancement
None
3.1.7 ZLF31-06-007 Radio Access Bearer Management
Dependency
None
Attribute
Basic function

Advantages
This feature manages E-UTRAN Radio Access Bearers (E-RABs).
Description
This feature manages E-RAB bearers. The E-RAB management procedures include:
E-RAB Setup
The purpose of the E-RAB Setup procedure is to assign resources on the Uu and
S1 interfaces for one or several E-RABs and to setup corresponding Data Radio
Bearers for a given UE. The procedure uses UE-associated signaling. The MME
initiates the procedure by sending an E-RAB SETUP REQUEST message to the
eNodeB.
E-RAB Modify
The purpose of the E-RAB Modify procedure is to enable parameter modification

(such as AMRB and ARP) of already established E-RABs for a given UE. The
procedure uses UE-associated signaling. The MME initiates the procedure by
sending an E-RAB MODIFY REQUEST message to the eNodeB.
E-RAB Release
The purpose of the E-RAB Release procedure is to enable the release of already
established E-RABs for a given UE. The procedure uses UE-associated signaling.
The MME initiates the procedure by sending an E-RAB RELEASE COMMAND
message to the eNodeB.
Introduced Version
LR13.2 and Before
Enhancement
None

3.1.8 ZLF31-06-008 S1 Interface Management
Dependency
None
Attribute
Basic function
Advantages
This feature manages the S1 interface between the eNodeB and the EPC.
Description
The S1 interface management procedures include:
Reset
The purpose of the Reset procedure is to initialize or re-initialize the eNodeB, or

part of eNodeB S1AP UE-related contexts. Both the eNodeB and the MME can
trigger this procedure:
If a failure occurs on the MME, the MME initiates the Reset procedure by
sending a RESET message to the eNodeB. On receipt of the RESET message
the eNodeB releases all allocated resources on S1 and UU related to the UE
associations indicated explicitly or implicitly in the RESET message and
removes the indicated UE contexts including S1AP ID.
If a failure occurs on the eNodeB, the eNodeB initiates the Reset procedure by
sending a RESET message to the MME. On receipt of the RESET message
the MME releases all allocated resources on S1 related to the UE associations
indicated explicitly or implicitly in the RESET message and removes the S1AP
ID for the indicated UE associations.
This procedure does not affect the application level configuration exchanged during
the S1 Setup procedure.
Error Indication

The Error Indication procedure is initiated by a receiving end in order to report

detected errors in one incoming message, if they cannot be reported by an
appropriate failure message. It can be initiated by the eNodeB or the MME. If the
error situation arises due to the reception of a message utilizing UE associated
signaling, then the Error Indication procedure uses UE associated signaling.
Otherwise, the procedure uses non-UE associated signaling.
S1 Setup
The purpose of the S1 Setup procedure is to exchange application level data

needed for the eNodeB and the MME for correctly interoperate on the S1 interface.
The procedure uses UE-associated signaling. The eNodeB initiates the procedure
by sending a S1 SETUP REQUEST message including the appropriate data to the
MME.
This procedure erases any existing application level configuration data in the
eNodeB and the MME and replaces it by the one received. This procedure also
re-initializes the eNodeB S1AP UE-related contexts (if any) and erases all related
signaling connections in the two nodes like a Reset procedure would do, and clears
MME overload state information at the eNodeB.
eNodeB/MME Configuration Update
The purpose of the eNodeB/MME Configuration Update procedure is to update

application level configuration needed for the eNodeB and the MME to interoperate
correctly on the S1 interface. This procedure does not affect any existing UE-related
contexts. The eNodeB initiates the procedure by sending an ENB
CONFIGURATION UPDATE message to the MME.
The purpose of the MME Configuration Update procedure is to update application

level configuration needed for the eNodeB and the MME to interoperate correctly on
the S1 interface. This procedure does not affect any existing UE-related contexts.
The MME initiates the procedure by sending an MME CONFIGURATION UPDATE
message to the eNodeB.
Overload

The purpose of the Overload procedure is to inform the eNodeB to reduce the
signaling load towards the concerned MME. The procedure uses non-UE
associated signaling, including the Overload Start and Overload Stop procedures.
On receipt of the OVERLOAD START message, the eNodeB shall assume the
MME from which it receives the message as being in overloaded state. In this case,
the eNodeB rejects the corresponding RRC Connection Requests in accordance
with the Overload Action setting contained in the OVERLOAD START message.
On receipt of the OVERLOAD STOP message, the eNodeB shall assume that the
overload situation on the MME from which it receives the message has ended and
shall resume normal operation towards this MME.
Introduced Version
LR13.2 and Before
Enhancement
None
3.1.9 ZLF31-06-009 X2 Interface Management
Dependency
Neighbor eNodeBs: supports the X2 interface management procedures
Attribute
Basic function
Advantages
This feature manages the X2 interface between eNodeBs.
Description
The X2 interface management functions include:
Load Indication

The purpose of the Load Indication procedure is to transfer load and interference
co-ordination information between eNodeBs controlling intra-frequency neighbor
cells. The procedure uses non UE-associated signaling. An eNodeB initiates the
procedure by sending a LOAD INFORMATION message to a peer eNodeB.
Error Indication
The Error Indication procedure is initiated by a receiving end in order to report

detected errors in one incoming message, if they cannot be reported by an
appropriate failure message. If the error situation arises due to reception of a
message utilizing UE associated signaling, then the Error Indication procedure uses
UE associated signaling. Otherwise, the procedure uses non-UE associated
signaling.
X2 Setup
The purpose of the X2 Setup procedure is to exchange application level

configuration data needed for two eNodeBs to interoperate correctly over the X2
interface. This procedure erases any existing application level configuration data in
the two eNodeBs and replaces it by the one received. This procedure also resets
the X2 interface like a Reset procedure would do. The procedure uses non
UE-associated signaling. An eNodeB initiates the procedure by sending the X2
SETUP REQUEST message to another eNodeB.
Reset
The purpose of the Reset procedure is to align the resources in eNodeB 1 and
eNodeB2 in the event of an abnormal failure. This procedure does not affect the
application level configuration data exchanged during the X2 Setup procedure. The
procedure uses non UE-associated signaling. The procedure is initiated with a
RESET REQUEST message sent from the serving eNodeB to neighboring eNodeB
(peer eNodeB).
eNodeB Configuration Update
The purpose of the eNodeB Configuration Update procedure is to update

application level configuration data needed for two eNodeBs to interoperate
correctly over the X2 interface. The procedure uses non UE-associated signaling.

The procedure is initiated with an ENB CONFIGURATION UPDATE message sent

from the serving eNodeB to neighboring eNodeB (peer eNodeB).
Resource Status Reporting
This procedure is initiated by an eNodeB to obtain the load measurement

information about other eNodeB. The procedure uses non UE-associated signaling,
including the Resource Status Reporting Initiation and Resource Status Reporting
procedures.
The Resource Status Reporting Initiation procedure is initiated with a RESOURCE

STATUS REQUEST message sent from serving eNodeB to neighboring eNodeB
(peer eNodeB). The Resource Status Reporting procedure is initiated by
neighboring eNodeB (peer eNodeB) to report the measurement results requested
by serving eNodeB.
Introduced Version
LR13.2 and Before
Enhancement
None
3.1.10 ZLF31-06-010 S1-Flex
Dependency
Feature list: ZLF31-06-008 S1 Interface Management
Attribute
Basic function
Advantages
This feature provides support for:
network redundancy

If an MME node is faulty in an MME/SGW pool, other nodes can share the load on
the faulty node, thus improving network redundancy.
signaling load balancing
An eNodeB selects an MME for a UE in accordance with the MME load situation to
implement MME load balancing and improve usage of system resources.
Description
The S1-Flex feature enables an eNodeB to establish associations with multiple MMEs in
different MME pools. One MME can also be connected to multiple eNodeBs. In the
many-to-many S1 interface relationships, an eNodeB selects an MME for a UE so that
the UE can be connected to the MME, which means the NAS Node Selection Function
(NNSF).
Figure 3-2 S1-Flex
MME S-GW MME S-GW
eNode-B eNode-B
UE1 UE2
The eNodeB selects an MME for a UE in accordance with some temporary identities that
the UE carries to the network access layer. For a UE that is attached initially, or does not
carry any temporary identity or MME information, or carries information about an MME
but the eNodeB cannot be connected to the MME, MME load balancing is required.
The eNodeB selects an MME to connect to the UE in accordance with the relative
capacity of each MME in the MME group for load balancing. Each MME sends an S1
Setup Response message to inform the eNodeB of its relative capacity. The MME sends

an MME Configuration Update message to inform the eNodeB of the change of the
relative capacity information.
Introduced Version
LR13.2 and Before
Enhancement
None
3.2 Mobility Management
3.2.1 ZLF31-07-001 Intra-LTE Cell Selection and Reselection
Dependency
None
Attribute
Basic function
Advantages
This feature is used to implement the mobility management for the UEs in idle mode in
the LTE system.
Description
There are two cell selection procedures:
Initiate cell selection
This procedure requires no prior knowledge of which RF (Radio Frequency)

channels are E-UTRAN carriers. The UE shall scan all RF channels in the
E-UTRAN bands according to its capabilities to find a suitable cell. On each carrier
frequency, the UE only searches for the strongest cell. Once a suitable cell is found,
this cell shall be selected.

Stored information cell selection
This procedure requires stored information of carrier frequencies and relevant

parameter information about other cells, from previously received measurement
control information elements or from previously detected cells. Once the UE has
found a suitable cell, the UE shall select it. If no suitable cell is found, the Initial Cell
Selection procedure shall be started.
The purposes of a UE camping on a cell in idle mode are as follows:
It enables the UE to receive system information from the cell.
When registered, the UE can initiate an RRC Connection Establishment request on

the control channel of the cell on which it is camped.
If the PLMN receives a call for the registered UE, it knows (in most cases) the set of
tracking areas in which the UE is camped. It can then send a paging message for
the UE on the control channels of all the cells in this set of tracking areas. The UE
will then receive the paging message and the UE can respond.
When a UE moves in idle mode, it can change the cell on which it is camped in
accordance with the cell reselection criteria. When the UE is camped on a cell, the UE
starts the cell reselection procedure. The UE determines whether to select a cell on a
frequency by evaluating the frequencies with different priorities in accordance with the
broadcasted system information or the dedicated reselection priority of each frequency.
There are three cell reselection policies:
Cell reselection between high-priority frequencies
Cell reselection between low-priority frequencies
Cell reselection within the same frequency or between frequencies with a equal
priority
In general, both cell selection and cell reselection can be divided into three phases:
measurement, selection or reselection evaluation, and cell camping. Measurement is the
prerequisite for cell selection and reselection, selection or reselection evaluation is the
core, and cell camping is the result of cell selection and reselection.

Also, the network support both RSRP and RSRQ based cell reselection. eNodeB informs
RSRP and RSRQ related reselection parameters to UE. Then UE perform cell
reselection evaluation according to RSRP and RSRQ measurement. This feature can be
used in the scenario of higher interference.
Introduced Version
LR13.2 and Before
Enhancement
None
3.2.2 ZLF31-07-002 Intra-LTE Redirection
Dependency
None
Attribute
Basic function
Advantages
This feature provides a flexible LTE mobility management policy. If a UE or network does
not support inter-frequency handover, or in some special application scenarios (such as
the cell being blocked), the redirection information is used to indicate the UE to select a
suitable cell on an LTE frequency.
Description
Based on the redirection policies, the eNodeB sends an RRC Connection Release
message to direct a UE in RRC_CONNECTED mode to another LTE frequency point.
The UE transitions from RRC_CONNECTED state to RRC_IDLE state, and initiates a
cell reselection procedure based on redirection frequency information indicated by the
network.

Redirection includes the coverage-based and blind redirection procedures. The

coverage-based redirection is applicable to the scenario where the UE or network does
not support handover. The blind redirection procedure is applicable to the scenario of a
cell being blocked.
Introduced Version
LR13.2 and Before
Enhancement
None
3.2.3 ZLF31-07-003 Intra-LTE Intra Frequency HO
Dependency
None
Attribute
Basic function
Advantages
This feature is used to hand over a UE to an intra-frequency cell based on the coverage
condition of LTE serving cells to ensure service continuity.
Description
To support UE mobility, handover is introduced to ensure that a UE in

RRC_CONNECTED state is served continuously when it moves between cells. Intra-LTE
intra-frequency handover refers to the handover of a UE in RRC-Connected state
between cells operating on the same frequency band of E-UTRAN.
Intra-frequency handover can be divided into three phases: handover measurement,

handover decision, and handover execution. Handover measurement is the prerequisite
for handover, handover decision is the core, and the handover execution is the

procedure realizing the handover. Intra frequency handover can be triggered based on
RSRP or RSRQ quantity. Intra frequency handovers are all based on measurements.
Intra-frequency handover includes S1 and X2 handover scenarios.
Introduced Version
LR13.2 and Before
Enhancement
None
3.2.4 ZLF31-07-004 LTE->GERAN Cell Reselection
Dependency
None
Attribute
Basic function
Advantages
This feature is used to implement the LTE-to-GERAN mobility management for the UEs
in idle mode.
Description
A UE performs evaluation on the GERAN frequency and cells in accordance with the
broadcasted system information, and then determines whether to reselect a cell on the
GERAN frequency.
The LTE-to-GERAN cell reselection parameters are set in

SystemInformationBlockType7, which contains information about GERAN frequencies
and GERAN neighbor cells.
Introduced Version

LR13.2 and Before
Enhancement
None
3.2.5 ZLF31-07-005 LTE->GERAN Redirection
Dependency
None
Attribute
Basic function
Advantages
This feature provides a flexible mobility management policy in a scenario consisting of

LTE and GERAN. If a UE or network does not support handover between the LTE
network and the GERAN network, or in some special application scenarios (such as the
cell being blocked), the redirection information is used to indicate the UE to select a
suitable cell on a GERAN frequency.
Description
With this feature, the eNodeB releases a UE from the LTE network, and then sends an
RRC Connection Release message in which the RedirectedCarrierInfo contains the
GERAN frequency information to inform the UE to redirect to the GERAN network. The
UE transitions to idle state, and selects a GERAN cell in accordance with the GERAN
frequency group information indicated by the LTE network.
The enhanced redirection mechanism is introduced in the R9 phase. The RAN

Information Management (RIM) function allows the transfer of SIB broadcast information
of neighbor GSM cells to eNodeBs. After the eNodeB triggers the release of a UE, the
eNodeB sends an RRC Connection Release message containing the SIB broadcast
information about neighbor GSM cells to the UE. The time for the UE to read the SIB
broadcast information is saved after reselecting a neighbor GSM cell, thus shortening the
time delay of the redirection procedure and reducing the service interruption time.

Introduced Version
LR13.2 and Before
Enhancement
None
3.2.6 ZLF31-07-006 LTE->UTRAN Cell Reselection
Dependency
None
Attribute
Basic function
Advantages
This feature is used to implement the LTE-to-UTRAN mobility management for the UEs
in idle mode.
Description
A UE performs evaluation on the UTRAN frequency and cells in accordance with the
UTRAN frequency.
The LTE-to-UTRAN cell reselection parameters are set in SystemInformationBlockType6,

which contains information about UTRAN frequencies and UTRAN neighbor cells.
Introduced Version
LR13.2 and Before
Enhancement
In LR15 version, eNodeB support LTE->UTRAN cell reselection with UMTS additional
channel configuration.

3.2.7 ZLF31-07-007 LTE->UTRAN Redirection
Dependency
None
Attribute
Basic function
Advantages

LTE and UTRAN. If a UE or network does not support handover between the LTE
network and the UTRAN network, or in some special application scenarios (such as the
cell being blocked), the redirection information is used to indicate the UE to select a
suitable cell on a UTRAN frequency.
Description
With this feature, the eNodeB releases a UE from the LTE network, and then sends an
RRC Connection Release message in which the RedirectedCarrierInfo contains the
UTRAN frequency information to inform the UE to redirect to the UTRAN network. The
UE transitions to idle state, and selects a UTRAN cell in accordance with the UTRAN
frequency information indicated by the LTE network.
The enhanced redirection mechanism is introduced in the R9 phase. The RIM function
allows the transfer of SIB broadcast information of neighbor UMTS cells to eNodeBs.
After the eNodeB triggers the release of a UE, the eNodeB sends an RRC Connection
Release message containing the SIB broadcast information about neighbor UMTS cells
to the UE. The time for the UE to read the SIB broadcast information is saved after
reselecting a neighbor UMTS cell, thus shortening the time delay of the redirection
procedure and reducing the service interruption time.
Introduced Version
LR13.2 and Before
Enhancement

In LR15 version, eNodeB support LTE->UTRAN redirection with UMTS additional

3.2.8 ZLF31-07-008 LTE->CDMA 1xRTT Cell Reselection
Dependency
UE: supports the LTE-to-1xRTT cell reselection function
Attribute
Basic function
Advantages
This feature is used to implement the LTE-to-1xRTT mobility management for the UEs in
idle mode.
Description
A UE performs evaluation on the 1xRTT frequency and cells in accordance with the
1xRTT frequency.
The E-UTRAN-to-1XRTT cell reselection parameters are set in

SystemInformationBlockType8, which contains information about 1XRTT frequencies
and 1XRTT neighbor cells.
Introduced Version
LR13.2 and Before
Enhancement
None
3.2.9 ZLF31-07-010 LTE->CDMA eHRPD Cell Reselection
Dependency

UE: supports the LTE-to-eHRPD cell reselection function
Attribute
Basic function
Advantages
This feature is used to implement the LTE-to-eHRPD mobility management for the UEs
in idle mode.
Description
A UE performs evaluation on the eHRPD frequency and cells in accordance with the
eHRPD frequency.
The LTE-to-eHRPD cell reselection parameters are set in SystemInformationBlockType8,

which contains information about eHRPD frequencies and eHRPD neighbor cells.
Introduced Version
LR13.2 and Before
Enhancement
None
3.2.10 ZLF31-07-011 LTE->CDMA eHRPD Redirection
Dependency
UE: supports the LTE-to-eHRPD redirection function
Attribute
Basic function
Advantages


LTE and eHRPD. If a UE or network does not support handover between the LTE system
and the eHRPD system, or in some special application scenarios (such as the cell being
blocked), the redirection information is used to indicate the UE to select a suitable cell on
an eHRPD frequency.
Description
This feature is also called non-optimization handover from LTE to eHPRD.
This feature is based on the S2a interface. The eNodeB is informed of a pre-registration
failure of a UE through the measurement report (preRegistrationStatusHRPD), or other
trigger cause (such as a measurement event). The eNodeB determines to initiate a
non-optimization handover procedure in accordance with the UE capability and network
capability, and sends an RRC Connection Release message with HRPD frequency
information to inform the UE to hand over the eHRPD network.
In accordance with whether the UE has been registered on the HRPD network,
non-optimization handover is divided into two cases: with an HRPD session and without
an HRPD session. If the UE has an HRPD session, the UE does not require UATI
allocation and session negotiation.
Introduced Version
LR13.2 and Before
Enhancement
None
3.2.11 ZLF31-07-012 Intra-LTE Inter Frequency HO
Dependency
None
Attribute
Basic function

Advantages
This feature ensures service continuality by handing over a UE to an inter-frequency

neighbor cell based on the coverage condition of the serving cell.
Description
Operators may configure intra-frequency and inter-frequency neighbor cells during

network deployment. Intra-LTE inter-frequency handover refers to hand over a UE in
RRC_CONNECTED mode from a cell at an E-UTRAN frequency to a cell at another
E-UTRAN frequency.
Each inter-frequency handover procedure consists of three parts: measurement,

handover decision, and handover execution. Measurement is the prerequisite for
handover, handover decision is the core, and the handover execution is the handover
implementation process. The prerequisite for a measurement-based inter-frequency
handover procedure is that the UE measures the RSPR or RSRQ to determine the
quality of the non-serving carrier frequency. After receiving the inter-frequency
measurement report from the UE, the eNodeB determines whether to perform an
inter-frequency handover. If the inter-frequency handover criteria are met, the eNodeB
hands over the UE to the target cell corresponding to the target frequency that is
indicated in the measurement report.
For the inter-frequency measurement performed by a UE in RRC_CONNECTED mode,

the measurement gap may be activated in accordance with the UE capability information.
If measurement gaps are required for UEs to perform inter-frequency measurement, the
measurement gap must be activated. Using measurement gaps means that some
sub-frames are not used for data transmission during signaling sending and receiving
procedures. Activation of measurement gaps has an impact on the system resource
consumption and UEs themselves. Therefore, inter-frequency measurement is enabled
normally when the radio quality of the current serving cell is poor.
Inter-frequency handover includes S1 and X2 handover scenarios.
Also, the network support both RSRP and RSRQ based inter-frequency handover
enhancement. eNodeB informs RSRP and RSRQ related measurement parameters to

UE. Then eNodeB trigger inter-frequency handover according to UE measurement report.

This feature can be used in the scenario of higher interference.
Introduced Version
LR13.2 and Before
Enhancement
None
3.2.12 ZLF31-07-015 LTE->UTRAN PS Handover
Dependency
UE: supports the LTE-to-UTRAN PS handover function
CN: supports the LTE-to-UTRAN PS handover function
UTRAN: supports the LTE-to-UTRAN PS handover function
Attribute
Basic function
Advantages

LTE and UTRAN. If the LTE network coverage is not available for a UE, a handover
command indicates to hand over the UE to a suitable cell at a UTRAN frequency to
ensure service continuity for the UE.
Description
The LTE configures a measurement reporting event B1/B2 for the cell measurement of
the UTRAN system. Before delivering the measurement reporting event B1 or B2, the
LTE network determines whether the UE supports the UTRAN measurement frequency
band, measurement, and event reporting capability. If the UE does not support
measurement reporting event B1/B2 of the UTRAN system, the LTE will not deliver the
event B1/B2 measurement to the UTRAN system.

The PS handover procedure from E-UTRAN to UTRAN is used for UEs in

RRC_CONNECTED mode, and can be divided into two phases: preparation phase and
execution phase. In the preparation phase, the eNodeB interacts with the target RNC
through the CN, and requests the target RNC to establish the UTRAN radio network
resources. After the target network resources are prepared, the eNodeB in the execution
phase sends an Mobility from E-UTRAN Command to the UE to inform the UE to hand
over to the target UTRAN network. After the handover is completed, the resources
related to the UE are released on the LTE network.
Introduced Version
LR13.2 and Before
Enhancement
In LR14 version, the network support both RSCP and Ec/Io based LTE->UTRAN PS
handover enhancement. eNodeB informs RSCP and Ec/Io related measurement
parameters to UE. Then eNodeB trigger LTE->UTRAN PS handover according to UE
measurement report. This feature can be used in the scenario of higher interference.
In LR15 version, eNodeB support LTE->UTRAN PS handover with UMTS additional

3.2.13 ZLF31-07-016 UTRAN->LTE PS Handover
Dependency
UE: supports the UTRAN-to-LTE PS handover function
CN: supports the UTRAN-to-LTE PS handover function
UTRAN: supports the UTRAN-to-LTE PS handover function
Attribute
Basic function
Advantages


LTE and UTRAN. If the UTRAN network coverage is not available for a UE, a handover
command indicates to hand over the UE to a suitable cell at an LTE frequency to ensure
service continuity for the UE.
Description
The UTRAN network initiates the corresponding LTE measurements for the PS handover
from UTRAN to LTE.
The PS handover procedure from UTRAN to LTE is used for UEs in RRC_CONNECTED
mode, and can be divided into two phases: preparation phase and execution phase. In
the preparation phase, the RNC interacts with the target eNodeB through the CN, and
requests the target eNodeB to establish the LTE radio network resources. After the target
network resources are prepared, the RNC in the execution phase sends an HO from
UTRAN Command to the UE to inform the UE to hand over to the target LTE network.
After the handover is completed, the resources related to the UE are released on the
UTRAN network.
Introduced Version
LR13.2 and Before
Enhancement
None
3.2.14 ZLF31-07-023 CSFB to UTRAN
Dependency
UE: supports the LTE-to-UTRAN CSFB function
CN: supports the LTE-to-UTRAN CSFB function
UTRAN: supports the LTE-to-UTRAN CSFB function
Attribute

Basic function
Advantages

LTE and UTRAN. If the LTE network does not support the VoIP voice service, this
feature falls back the UE to the CS domain in the UTRAN network to provide the voice
service to the UE.
Description
The CSFB procedure reuses the existing CS domain to provide voice services to the LTE
users in the LTE coverage that is overlapped by the UTRAN coverage.
The CSFB function from LTE to UTRAN has the following characteristics:
It can be used in a scenario where a UTRAN coverage area is overlapped by an

LTE coverage area.
The broadband data services are provided through the LTE network, while the voice
services are still provided by the traditional CS domain.
When a call needs to be handed over from the LTE network to the CS domain in the
UTRAN network, it takes a long time to establish the call.
The following figure shows the CSFB architecture for UTRAN CSFB. The signaling
messages related to the CSFB procedure are exchanged between the MME and the
MSC over the SGs interface.

Figure 3-3 CSFB architecture for UTRAN
MME
eNB
S1 SG
s MSC Server
LTE Network
S3
RAN
Iu/A
Gs
Iu/Gb
UTRAN/GERAN SGSN
Network
When an LTE UE requests to establish a voice service in the CS domain (MO call), or a
UE of another network calls the LTE user (MT call), the MME performs a network
handover to fall back the CS domain voice service request to the CS domain in the
UTRAN. The eNodeB triggers the corresponding mobility procedure in accordance with
the target cell capability, UE capability, and RRC connection state of the UE. For the
non-voice service that a UE already establishes, this service can handover to the UTRAN
through the PS handover procedure or suspend in LTE network according to the target
network capabilities and the PS HO capability of the UE. After the CS domain service is
completed, if the UE returns to the LTE network, the MME can restore the suspended
service of the UE if there is any suspended service in LTE.
TE to UTRAN CSFB include following features:
Measurement based LTE to UTRAN CSFB with redirection;
Blind based LTE to UTRAN CSFB with redirection;
Measurement based LTE to UTRAN CSFB enhancement with redirection + SI

inform;
Blind based LTE to UTRAN CSFB enhancement with redirection + SI inform;
Measurement based LTE to UTRAN CSFB enhancement with PS handover;
Blind based LTE to UTRAN CSFB enhancement with PS handover;

Emergency call with CSFB mechanism.
Introduced Version
LR13.2 and Before
Enhancement
In LR14 version, eNodeB support CSFB high priority feature. MME inform CSFB high
priority information to eNodeB in S1 interface. When receiving this inform, eNodeB
handle this user in priority and guarantee network resource of CSFB user.
In LR14 version, eNodeB support CSFB target frequency randomization. In UTRAN multi
same priority frequencies deployment, when eNodeB trigger blind based LTE to UTRAN
CSFB with redirection, eNodeB can random select CSFB target frequency for each
CSFB user to balance the load among multi UTRAN frequencies.
In LR15 version, eNodeB support CSFB enhancement with PS handover. When

triggering measurement based LTE to UTRAN CSFB with PS handover, eNodeB
perform CSFB target UTRAN cell selection according to measurement report and
UTRAN neighboring cell load information. This feature is used to avoid UE fallback to
higher load UTRAN neighboring cell and increase internal load balancing among UTRAN
multi frequency. This feature requires CN and UTRAN support RIM procedure.
In LR15 version, eNodeB support LTE->UTRAN CSFB with UMTS additional channel
configuration.
In LR16 version, eNodeB support UE position based CSFB enhancement. When

triggering LTE to UTRAN CSFB, eNodeB will distinguish CCU/CEU user position
information and configure CSFB user with different CSFB strategies. For example, CCU
user can use blind based CSFB strategy, CEU user can use measurement based CSFB
strategy, as so to make balance between CSFB successful rate and CSFB latency.

3.3 Radio Resource Management
3.3.1 ZLF31-08-001 Radio Admission Control
Dependency
None
Attribute
Basic function
Advantages
This feature performs admission control management on a new UE or service in

accordance with the requirements for requested resources and resource usage of the
cell when the UE implements RRC connection establishment, E-RAB bearer
establishment, or handover in the LTE network. This prevents the newly accessed UEs
or services from affecting the existing services or making the system overloaded, thus
ensuring system stability and UEs' QoS.
Description
The function of Radio Admission Control (RAC) is to admit or reject the new service
requests for new system resources. In order to do this, RAC takes into account the
overall resource situation in the system, the priority levels of the UEs and services, and
the provided QoS of in-process sessions and the QoS requirement of the new service
request. This prevents the newly accessed services from affecting the existing service
bearers or making the system overloaded, thus ensuring system stability and the QoS
requirements for services. The purpose of RAC is to accept more services as long as
radio resources available, thus ensuring high radio resource utilization, improving the
system capacity, and reducing the operation costs of operators.
A request for new cell resource is initiated in the following cases: RRC connection
establishment, E-RAB establishment, E-RAB modification, S1 handover, and X2
handover. After receiving an admission request, the eNodeB needs to consider the

resource usage and information of the system and cells. RAC is based on at least the
following resources or factors:
Rejection of new UEs based on probability
CPU usage of hardware resources
Number of users
Number of active bearers
Downlink PRB resources
Uplink PRB resources
Introduced Version
LR13.2 and Before
Enhancement
None
3.3.2 ZLF31-08-004 Congestion Control
Dependency
None
Attribute
Basic function
Advantages
This feature supports high-priority services preempting the resources from low-priority
GBR services if the system is congested and the services failed to be accepted due to
insufficient uplink or downlink PRB resources. Thereby, the access success rate of
high-priority services and the experience of high-priority users are improved.
Description

Congestion occurs when the idle system resources cannot meet the resource
requirements for admitting or modifying services. In this case, the congestion control
policy should be executed.
The congestion control is used to take a series of measures to relieve congestion and
reallocate radio resources of the system in accordance with the QoS attributes such as
the QCI, ARP, and service attributes. This feature improves the access success rate of
users, especially high-priority users and preferentially guarantees the access of new
high-priority users.
The system supports configurable GBR priority during the congestion control procedure,
thus preferentially guaranteeing the QoS of the real-time and high-priority services.
Introduced Version
LR13.2 and Before
Enhancement
In LR14 version, eNodeB support congestion control enhancement. In case system in

congestion status, when low priority UE access failure, eNodeB will redirect the UE to
other frequency or other network, to avoid low priority UE cannot initial service for a long
time in serving cell due to system congestion.
3.3.3 ZLF31-08-005 Intra-LTE Load Balancing
Dependency
Feature list: ZLF31-07-003 Intra-LTE Intra Frequency HO and ZLF31-07-012 Intra-LTE

Inter Frequency HO
Neighbor eNodeBs: supports exchanging load information over the X2 interface
Attribute
Basic function
Advantages

This feature is used to balance distribution of the traffic load over the serving cell and its
neighbor cells in the LTE network, especially consisting of multiple frequencies. The
purpose of this feature is to effectively use the resources of the LTE network, improve the
overall system capacity, and ensure system stability.
Description
Load balancing distributes traffic load as evenly as possible among the cells that are
geographically associated with each other, and prevents traffic load from being
centralized in a cell. This thus effectively increases the overall system performance and
improves system security, stability, and capacity to optimize the overall status of the
system.
The load balancing feature monitors the load of the local cell and its neighbor cells. If the
local cell is overloaded, a part of load is moved to the neighbor cells with low load. In this
way, load balancing is achieved among the cells in the area, and the system capacity is
increased.
Intra-LTE load balancing is applicable in a scenario consisting of multiple carrier

frequencies. If a cell on a frequency is overloaded, this feature enables to move a part of
load on the cell to the neighbor cells with lower load on other frequency.
Neighbor eNodeBs exchanges load information about neighbor cells with each other
over the X2 interface through the resource load management procedure. An eNodeB can
request another eNodeB to provide cells' information about the usage of the PRB,
hardware, transmission, and hybrid cell capacity, so that the eNodeB can select a target
cell with lower load during the load balancing procedure.
Introduced Version
LR13.2 and Before
Enhancement
In LR14 version, eNodeB support RRC user aware load balancing. In the LTE multi
frequency network, load balancing mechanism can be enabled according to RRC user

aware load evolution, to balancing load status among LTE multi frequencies, Meanwhile,
the network support combined load evolution to trigger load balancing. eNodeB will take
both RRC user and PRB usage factors into consideration during load evolution.
3.3.4 ZLF31-08-008 LTE Load Control
Dependency
None
Attribute
Basic function
Advantages
This feature enables the system to release low-priority GBR services to reduce the
system load quickly when the LTE network is overloaded and the system is on the brink
of instability. Thereby the system stability is ensured.
Description
The load control function can take various measures to quickly reduce each overloaded
cell, thus ensuring system stability.
For a cell, there are two load states: normal and overloaded. If the load level of a cell
exceeds the threshold for cell load control, it is determined that the cell is overloaded.
The cell starts load control. When the load level of the cell is lower than the recovery
threshold, it is determined that the cell becomes normal. Consequently, the cell stops
load control.
Introduced Version
LR13.2 and Before
Enhancement
In LR14 version, eNodeB supports QCI level load control strategy. When serving cell is
overload, the network distinguishes different service by QCI bearer and release

low-priority GBR services according to QCI strategy, thus avoiding the impact to
sensitive service, such as QCI=1 voice service.
3.4 QoS Management
3.4.1 ZLF31-09-001 Standard QCI (19)
Dependency
Feature list: ZLF31-06-007 Radio Access Bearer Management
Attribute
Basic function
Advantages
This feature is used in the LTE network to support bearers with QCI =1 through QCI=9
compliant with 3GPP standards.
Description
The eNodeB supports the following standard QCIs.
Table 3-1 Standard QCIs
QCI Remark
Priority Packet Packet Error Example Service

Delay Rate
Requirement
-2
1 (GBR) 2 100 ms 10 Session voice
-3
2 (GBR) 4 150 ms 10 Real-time video session
-3
3 (GBR) 3 50 ms 10 Real-time game
-6
4 (GBR) 5 300 ms 10 Non-session video (video
streams cached)
-6
5 (non-GBR) 1 100 ms 10 IMS signaling
-6
6 (non-GBR) 6 300 ms 10 Video stream caching

(TCP)
-3
7 (non-GBR) 7 100 ms 10 Voice, real-time video
stream, and interactive
game
-6
8 (non-GBR) 8 300 ms 10 Video stream caching
-6 (TCP)
9 (non-GBR) 9 300 ms 10
Introduced Version
LR13.2 and Before
Enhancement
None
3.5 User Plane Processing
3.5.1 ZLF31-10-001 MAC PDU and Functions
Dependency
None
Attribute
Basic function
Advantages
This feature supports the basic MAC layer functions in the LTE network.
Description
This feature supports the basic MAC layer functions defined in 3GPP TS 36.321,
including:
All MAC PDU formats defined in 3GPP
Mapping between logical channels and transport channels

Multiplexing of MAC SDUs from one or several downlink logical channels into
Transport Blocks (TBs)
Demultiplexing of MAC SDUs from TBs into one or several logical channels
Priority handling between UEs by means of scheduling
Priority handling between logical channels of one UE
Introduced Version
LR13.2 and Before
Enhancement
None
3.5.2 ZLF31-10-002 RLC PDU and Functions
Dependency
None
Attribute
Basic function
Advantages
This feature supports the basic RLC layer functions in the LTE network.
Description
This feature supports the basic RLC layer functions defined in 3GPP TS 36.322,
including:
RLC data transmission modes: Acknowledged data transfer Mode (AM),

Unacknowledged data transfer Mode (UM), and Transparent data transfer Mode
(TM)
Error correction through ARQ (only for AM data transfer)

AM entity reporting mechanism
Concatenation, segmentation, and reassembly of RLC SDUs (only for UM and AM

data transfer)
Reordering of RLC PDUs (only for UM and AM data transfer)
Duplicate detection (only for UM and AM data transfer)
Re-segmentation of RLC PDUs (only for AM data transfer)
RLC SDU discard (only for UM and AM data transfer)
RLC re-establishment
Protocol error detection (only for AM data transfer)
Introduced Version
LR13.2 and Before
Enhancement
None
3.5.3 ZLF31-10-003 PDCP PDU and Functions
Dependency
None
Attribute
Basic function
Advantages
This feature supports the basic PDCP layer functions in the LTE network.
Description

This feature supports the basic PDCP layer functions defined in 3GPP TS 36.323,
including:
Transfer of data between the NAS layer and the RLC layer, including Signaling
Radio Bearer (SRB) and Data Radio Bearer (DRB)
Maintenance of PDCP SNs
Delivery at re-establishment of lower layers
Timer based discard
Duplicate discarding
Introduced Version
LR13.2 and Before
Enhancement
None
3.5.4 ZLF31-10-004 Header Compression Profile 0x0000
Dependency
UE: supports header compression profile 0x0000
Attribute
Basic function
Advantages
This feature enables overhead reduction of packet header on radio interface.
Description
This feature enables header compression and decompression in accordance with ROHC
protocols.

The air interfaces used for radio transmission is limited and valuable. In some voice,
video, or multimedia applications, data payloads account for a very small part of the
entire IP packet. For VoIP, the payload of IP, RTP, and UDP is about 40 bytes or even
more, but the length of voice data is often 7 to 62 bytes, and usually 30 to 40 bytes. The
bandwidth utilization of air interfaces is very low. ROHC compresses unrecognized
packet headers of the VoIP service into only 1 to 2 bytes. The bandwidth utilization may
be greater than 90% in better cases.
Profile 0x0000 means uncompressing of unrecognized protocol packets.
Introduced Version
LR13.2 and Before
Enhancement
None
3.5.5 ZLF31-10-005 Header Compression Profile 0x0001
Dependency
Feature list: ZLF31-10-004 Header Compression Profile 0x0000
UE: supports header compression profile 0x0001
Attribute
Basic function
Advantages
In the LTE network, this feature uses an IP-based general compression technology for
radio transmission over air interfaces to improve the resource utilization of air interfaces.
For example, this feature can be applicable to the VoIP service.
Description
This feature enables header compression and decompression in accordance with ROHC
protocols.

The air interfaces used for radio transmission is limited and valuable. In some voice,
video, or multimedia applications, data overheads account for a very small part of the
entire IP packet. For VoIP, the overhead of IP, RTP, and UDP is about 40 bytes or even
more, but the length of voice data is often 7 to 62 bytes, and usually 30 to 40 bytes. The
bandwidth utilization of air interfaces is very low. ROHC compresses the packet headers
of the VoIP service into only 1 to 2 bytes. The bandwidth utilization may be greater than
90% in better cases.
Profile 0x0001 is for RTP/UDP/IP compression.
Introduced Version
LR13.2 and Before
Enhancement
None
3.6 Security Management
3.6.1 ZLF31-11-001 Integrity check (Reserved mode)
Dependency
None
Attribute
Basic function
Advantages
This feature enables integrity protection on the Uu interface to protect UEs and
network-side signaling from the fraudulent attacks made by other UEs or the network
equipment controlled by a third party.
Description

This feature verifies the integrity of the signaling messages transmitted between a UE
and an eNodeB.
The sender uses the integrity protection algorithm to calculate the parameters for
signaling integrity protection, attaches them behind data, and transmits them to the
recipient. The recipient uses the integrity protection algorithm to calculate these
parameters, and verifies that they are the same as the received parameters. Thereby,
the recipient determines signaling data integrity.
EIA0 corresponds to the null integrity protection algorithm.
Introduced Version
LR13.2 and Before
Enhancement
None
3.6.2 ZLF31-11-002 Integrity check (128-EIA1)
Dependency
None
Attribute
Basic function
Advantages
Description
and an eNodeB.

EIA1 is based on the SNOW 3G algorithm.
Introduced Version
LR13.2 and Before
Enhancement
None
Dependency
None
Attribute
Basic function
Advantages
Description
and an eNodeB.

EIA2 in based on the AES algorithm.
Introduced Version
LR13.2 and Before
Enhancement
None
3.6.4 ZLF31-11-004 Encryption/Decryption (EEA0)
Dependency
None
Attribute
Basic function
Advantages
This feature offers encryption protection for the signaling and data over the Uu interface.
It guarantees the security of UEs and network-side signaling and data, and ensures the
safe communication between UEs and the network.
Description
This feature offers the confidentiality protection for the signaling messaged and user data
transmitted between a UE and an eNodeB.
The sender generates a ciphering key by using the encryption algorithm, and uses this
key to encrypt data. After the encrypted data reaches the receiving end through a radio
link, the recipient decrypts the data by using the same ciphering key.
EEA0 is based on the null ciphering algorithm.

Introduced Version
LR13.2 and Before
Enhancement
None
3.6.5 ZLF31-11-005 Encryption/Decryption (128-EEA1)
Dependency
None
Attribute
Basic function
Advantages
Description
EEA1 is based on the SNOW 3G algorithm.
Introduced Version
LR13.2 and Before
Enhancement

None
Dependency
None
Attribute
Basic function
Advantages
This feature enables confidentiality protection for the data stream and signaling stream.
Description
EEA2 is based on the AES algorithm.
Introduced Version
LR13.2 and Before
Enhancement
None
Dependency
UE: supports EIA3 for integrity protection

Attribute
Basic function
Advantages
Description
and an eNodeB.
EIA3 is based on the ZUC algorithm.
Introduced Version
LR13.2 and Before
Enhancement
None
Dependency
UE: supports EEA3 for encryption protection
Attribute
Basic function

Advantages
Description
EEA3 is based on the ZUC algorithm.
Introduced Version
LR13.2 and Before
Enhancement
None
3.7 Scheduling and Link Adaptation
3.7.1 ZLF31-13-001 UL/DL HARQ
Dependency
None
Attribute
Basic function
Advantages

This feature supports the UL and DL HARQ functions defined in 3GPP to implement fast
retransmission and reduce BLER.
Description
This feature supports the following basic HARQ functions:
Asynchronous adaptive/non-adaptive HARQ in the downlink
Synchronous adaptive/non-adaptive HARQ in the uplink
Two HARQ retransmission modes: CC and IR
Configurable HARQ parameters for operators
Introduced Version
LR13.2 and Before
Enhancement
None
3.7.2 ZLF31-13-002 Dynamic Scheduling
Dependency
None
Attribute
Basic function
Advantages
This feature supports the uplink and downlink dynamic scheduling functions to implement
fast scheduling.
Description
This feature supports the following basic MAC scheduling functions:

Dynamic scheduling performed on each TTI
Multiple time domain priority scheduling policies, including Round Robin, Max C/I,
and Proportional Fair
Basic resource allocation in a frequency domain, which means that resources are
allocated in a frequency domain in the ascending order of UE sequence
Introduced Version
LR13.2 and Before
Enhancement
None
3.7.3 ZLF31-13-003 UL/DL Frequency Selective Scheduling
Dependency
System Bandwidth: Not Available for 1.4/3 MHz
Attribute
Basic function
Advantages
The feature enables cell throughput improvement and guarantees QoS requirements in
low speed environment.
Description
Because of the fast fading attributes of radio channels and the OFDM technology used in
LTE, the frequency selective scheduling allocates UE frequency-domain resources to the
PRBs with higher Signal Interference Noise Ratio (SINR). This improves the throughput
and frequency efficiency for UEs and cells.
The downlink frequency-selective scheduling selects PRBs based on the sub-band

CQI reports sent by UEs.

The uplink frequency-selective scheduling selects PRBs based on the SRS

signaling measurement reports sent by UEs.
The frequency-selective scheduling procedure is as follows:
Acquire the sub-band channel quality, and calculate the broadband channel quality.
Calculate the MCS, TBS, and the number of PRBs of a UE based on the broadband
channel quality and the QoS attributes of the UE.
Select the specific PRB location based on the sub-band channel quality.
Introduced Version
LR13.2 and Before
Enhancement
None
3.7.4 ZLF31-13-009 QoS Scheduler
Dependency
None
Attribute
Basic function
Advantages
This feature ensures the QoS attributes of services on the LTE network, such as AMBR,
GBR, and PDB for a specific service.
Description
The purpose of the QoS scheduler is to guarantee the QoS attributes of different services
in the LTE network.
The following QoS requirements are defined in 3GPP:

Service priority, such as QCI priority
GBR/MBR for GBR services
AMBR for NGBR services
Packet Error Rate (PER) and Packet Delay Budget (PDB) for the services
corresponding to each QCI
The eNodeB considers the above QoS requirements in the QoS scheduler, and
guarantees the QoS attributes of each service by priority queuing and QoS processing in
resource allocation.
Introduced Version
LR13.2 and Before
Enhancement
None
3.7.5 ZLF31-13-011 Pseudo GBR for NGBR
Dependency
None
Attribute
Basic function
Advantages
This feature ensures the minimum guaranteed bit rate for NGBR services to prevent
low-priority NGBR services from being starved.
Description
This feature ensures the minimum uplink and downlink guaranteed bit rate for NGBR
services to prevent low-priority NGBR services from being starved.

Operators can configure this minimum guaranteed bit rate.
Introduced Version
LR13.2 and Before
Enhancement
None
3.7.6 ZLF31-13-012 Advanced AMC
Dependency
None
Attribute
Basic function
Advantages
This feature improves the spectral efficiency and edge coverage quality for UEs in
different radio environments, which increases the spectral efficiency of the entire
network.
Description
The Adaptive Modulation and Coding (AMC) function grants each UE with proper air
interface resources (number of PRBs and MCS) at each TTI based on the radio channel
quality to maintain the target Block Error Ratio (BLER).
In the downlink, the AMC function obtains the downlink radio channel quality based on
the UE-reported CQI. In the uplink, the AMC function measures and calculates the uplink
radio channel quality based on the UE-reported SRS signals. Based on the uplink and
downlink radio channel quality, and UE buffered data status, and UE capabilities, the
AMC function of the eNodeB can determine the MCS and the number of PRBs to be
transmitted for the UE over the air interface at the scheduling time.
In general, ZTE eNodeB considers the following input for AMC:

Downlink CQI, and SINR measured based on uplink SRS signals
UE-reported BSR, and the UE's data that is cached on the eNodeB and waiting to
be transmitted
UE capabilities
BLER
ZTE eNodeB considers the following output for AMC:
Number of PRBs
MCS
Transmission power
In addition, ZTE eNodeB supports out-loop AMC to maintain a target BLER due to the
following reasons:
Deviation exists among the CQIs reported by different UE manufacturers.
The mapping between the radio channel quality and MCS based on the link level
simulation results must be revised in accordance with the actual channel
environment.
The out-loop AMC function calculates the revised value of MCS by considering the
ACK/NACK counters, uses this revised value to revise the MCS retrieved based on the
radio channel quality, and sends the revised MCS to the UE.
Introduced Version
LR13.2 and Before
Enhancement
None

3.7.7 ZLF31-13-013 PDCCH Link Adaptation
Dependency
None
Attribute
Basic function
Advantages
This feature increases the system capacity and improves PDCCH coverage.
Description
The PDCCH link adaptation function dynamically adjusts the PDCCH CCE aggregation
level and power setting of a UE based on the radio channel quality. This increases the
PDCCH capacity under the condition that the PDCCH coverage is guaranteed.
At the cell edge or in an area with poor radio channel quality, a large CCE aggregation
level is required, such as CCE4 and CCE8. At the same time, the RE power of PDCCH
should be increased. In an area with good radio channel quality, the aggregation level of
CCE2 is used and the RE power of PDCCH can be reduced appropriately.
Introduced Version
LR13.2 and Before
Enhancement
None
3.7.8 ZLF31-13-015 Enhanced Adaptive Intra-Mode MIMO Schemes
Dependency
None
Attribute

Basic function
Advantages
If two transmit antennas are deployed on an eNodeB, this feature improves the system
capacity and coverage by using adaptive intra-mode 22 MIMO schemes in the
downlink.
Description
ZTE eNodeB supports the following adaptive intra-mode 22 MIMO schemes in the
downlink:
Open-loop intra-mode adaption
If this option is selected, the transmission mode is switched adaptively between

transmit diversity and open-loop space division multiplexing in accordance with the
UE-reported RI and UE's radio channel quality.
Closed-loop intra-mode adaption
If this option is selected, the transmission mode is switched adaptively among

transmit diversity, closed-loop space division multiplexing, and closed-loop spatial
division multiplexing with a rank of 1 in accordance with the UE-reported RI and
UE's radio channel quality.
Introduced Version
LR13.2 and Before
Enhancement
None
3.7.9 ZLF31-13-019 Static ICIC
Dependency
System Bandwidth: Not Available for 1.4/3 MHz

Attribute
Basic function
Advantages
This feature coordinates and mitigates inter-cell interference through static Fractional
Frequency Reuse (FFR) or Soft Frequency Reuse (SFR).
Description
ZTE eNodeB supports the static Inter Cell Interference Coordination (ICIC) function.
There is no load information exchanged between eNodeBs during the configuration of
the static ICIC function.
The static ICIC function is described as follows:
UEs are divided into Cell Center Users (CCUs) and Cell Edge Users (CEUs) in
accordance with the RSRP measurement-based A3 event reports from UEs.
Based on the cell topology and the initial edge frequency division, the PRB
resources of a cell can be divided into cell-edge PRBs and cell-center PRBs. The
cell-edge PRBs of neighbor cells are mutually orthogonal.
The FR coefficient for CCUs is 1, and the FR coefficient for CEUs is 3.
Based on common uplink and downlink scheduling algorithms, the ICIC function enables
the scheduler to preferentially schedule CEUs on the cell-edge PRBs, and schedules
CCUs to the cell-center PRBs and cell-edge PRBs if still available.
Figure 3-4 shows the PRB allocation for static FFR. Take sector 1 as an example:
The entire frequency band is divided into four parts (configurable by operators).
The first part marked with OC can be available for only CEUs.
The second and third parts marked with forbidden, which are the edge frequency
band of other sectors, are not available for UEs in sector 1.
The last part marked with IC is available for CCUs in sector 1.

Figure 3-5 shows the PRB allocation for static SFR. Take sector 1 as an example:
The entire frequency band is divided into four parts (configurable by operators).
The second part marked with OC is available for only CEUs and CCUs if still
available.
The first, third, and fourth parts all marked with IC are available for CCUs in sector
1.
In the static ICIC algorithm, the number of divided band parts is configurable for
operators.
In addition, once ICIC is enabled, the downlink EPRE is increased for CEUs to increase
the cell edge throughput.
Figure 3-4 Static Fractional FR
P Sector 1 P Sector 2 P Sector 3

Forb Forb
Forb
Forb
Forb
Forb

OC idde idde

IC idde

OC idde

IC idde idde

OC IC
n n n n n n
F F F
Figure 3-5 Static Soft FR
Sector 1 Sector 2 Sector 3

P P P
OC OC OC
IC IC IC IC IC IC IC IC IC
F F F
Introduced Version
LR13.2 and Before
Enhancement
None
3.7.10 ZLF31-13-022 Advanced Operator Configurable QoS Scheduler
Dependency

None
Attribute
Basic function
Advantages
This feature supports absolute and relative QCI scheduling through the operator
configurable QoS scheduler to meet the different QoS requirements of different
operators.
Description
ZTE eNodeB supports the operator configurable QoS scheduler. Operators can
configure absolute and relative QCI priority scheduling. During the configuration of
absolute QCI priorities, services with different QCIs are distributed in different scheduling
queues. Absolute priority scheduling is implemented among QCI scheduling queues.
During the configuration of relative QCI priority scheduling, all the NGBR QCI services
can be configured in the same scheduling queue. Operators can control the scheduling
priority of each NGBR QCI service in a queue by configuring different AMBR, QCI, and
ARP scheduling factors. In addition, operators can configure the weight of each
scheduling factor in the final scheduling priority calculation.
To simplify the configuration complex of scheduling factors for the NGBR services, each
combination of QCI and ARP can be mapped to a single service priority scheduling factor.
The current software supports a maximum of 15 service priorities. Operators can
configure the combination of QCI and ARP corresponding to each service priority. When
service priorities are used to control QoS, independent QCI and ARP scheduling factors
must be disabled.
Operators can configure the QCI, ARP, and GBR scheduling factors for GBR services.
While guaranteeing the GBR rate, operators should fully consider the impact of different
QoS scheduling factors on service scheduling priorities.
Introduced Version
LR13.2 and Before

Enhancement
None
3.7.11 ZLF31-13-041 NI Based Interference Avoidance Scheduling
Dependency
Hardware devices: except BPL0
Attribute
Basic function
Advantages
This feature is used to improve system spectrum efficiency in some special scenarios
where there is high interference from other system on some PRB resources.
Description
In some special scenarios where there is high interference from other system on some
PRB resources, this feature avoids to allocate high NI PRB resources to user, based on
NI measurement, in order to improve system SE.
Introduced Version
LR15
Enhancement
None
3.7.12 ZLF31-13-042 Small Packets Service Optimization
Dependency
Hardware devices: except BPL0
Attribute

Basic function
Advantages
This feature is used to improve radio performance for small packets service, like IM
messages, etc.
Description
Small packets services for IM messages, like QQ, ICQ, WeChat, etc, occupy only small
number of RBs. Regarding to small RB service, this feature calculates MCS calculated
from selected best RB sub-set SINR, other than from wide-band SINR, in order to
improve small RB service user experience.
Introduced Version
LR15
Enhancement
None
3.7.13 ZLF31-13-043 TCP RTT Optimization
Dependency
Hardware devices: BPL1
Attribute
Basic function
Advantages
This feature is used to improve round trip time (RTT) for TCP service, in order to improve
TCP service user experience.
Description

For TCP service, the scheduler analyzes the DL TCP packet size and timing, and then
predicts the UL TCP ack packet size and timing; and then pre-allocate UL grant to UE, in
order to accelerate TCP RTT.
Introduced Version
LR15
Enhancement
None
3.8 Radio Part
3.8.1 ZLF31-14-001 Basic Physical Layer Support
Dependency
None
Attribute
Basic function
Advantages
This feature supports the basic physical layer functions defined in 3GPP.
Description
ZTE eNodeB supports the basic physical layer processing functions defined in 3GPP TS
36.211, TS 36.212, and TS 36.213.
ZTE eNodeB supports normal CP.
ZTE eNodeB supports basic physical channels processing functions, such as PCFICH,
PHICH, PDCCH, PDSCH, PRACH, PUCCH, and PUSCH.

ZTE eNodeB supports basic physical signal processing functions, such as cell specific
RS, UL DMRS, and Sounding RS.
ZTE eNodeB supports all the PDCCH formats and CCE aggregation levels defined in
3GPP.
ZTE eNodeB supports all the UCI formats defined in 3GPP.
ZTE eNodeB supports all the DCI formats except DCI 1B, DCI 1C, and DCI 1D.
ZTE eNodeB supports DL resource allocation types 0 and 2.
ZTE eNodeB supports all the PA and PB configurations defined in 3GPP TS 36.213 for
DL power allocation.
ZTE eNodeB supports all the MCSs and Transport Block Sizes (TBSs) on DL and UL
defined in 3GPP TS 36.213 for resource allocation.
Introduced Version
LR13.2 and Before
Enhancement
None
3.8.2 ZLF31-14-004 PRACH Format 0
Dependency
None
Attribute
Basic function
Advantages
This feature supports PRACH preamble format 0 defined in 3GPP specifications for
random access in a common urban area.

Description
A PRACH channel is used to generate a preamble for random access. According to

3GPP specifications, the random access preambles are generated one or several root
Zadoff-Chu sequences.
The typical application for PRACH preamble format 0 is as follows:
Within a normal subframe of 1ms, the preamble sequence of 800 s is used for
small-medium cells with their radiuses not greater than 14 km.
The following figure shows a typical random access preamble in the physical layer,
consisting of a Cyclic Prefix (CP) of length T CP and a preamble sequence part of length
TSEQ .
Figure 3-6 Random Access Preamble Format
CP Sequence
TCP TSEQ
The following table lists the CP length and preamble sequence length corresponding to
different PRACH preamble formats.
Table 3-2 Parameters of Different PRACH Formats
Preamble Format TCP TSEQ

0 3168*Ts 24576*Ts
1 21024*Ts 24576*Ts
2 6240*Ts 2*24576*Ts
3 21024*Ts 2*24576*Ts
Introduced Version
LR13.2 and Before
Enhancement
None

3.8.3 ZLF31-14-008 UL QPSK/16QAM, DL QPSK/16QAM/64QAM
Dependency
None
Attribute
Basic function
Advantages
This feature supports basic modulation schemes in uplink and downlink defined in 3GPP
specifications. Downlink high-order modulation schemes (such as DL 64QAM) can be
used under excellent channel conditions to increase the downlink throughput of a single
UE and a cell greatly.
Description
ZTE eNodeB supports basic modulation schemes defined in 3GPP specifications:
Downlink QPSK, 16QAM, and 64QAM
Uplink QPSK and 16QAM
QPSK allows a maximum of two information bits to be modulated to a symbol. 16QAM

allows a maximum of four information bits to be modulated to a symbol. However,
high-order 64QAM allows a maximum of six information bits to be modulated to a
symbol.
For a high-order 64QAM modulation scheme, there are 16 constellation points in a

quadrant. The EVM of the signal to be demodulated must be very small. Otherwise, the
signal will be demodulated to other signal. Therefore, 64QAM modulation scheme can be
used only under the excellent channel conditions. For a low-order QPSK modulation
scheme, there is only on constellation point in a quadrant. In this case, the requirements
for the EVM of the signal to be demodulated are reduced. Such modulation scheme is
suitable for a UE in a poor radio environment (such as the cell edge).
In addition, with the ZTE's Adaptive Modulation and Coding (AMC) function, the
modulation scheme adaption can be implemented in accordance with the channel

conditions, thus improving the radio transmission reliability and reducing the bit error
ratio.
Introduced Version
LR13.2 and Before
Enhancement
None
3.8.4 ZLF31-14-010 TX Diversity (2 Antennas)
Dependency
None
Attribute
Basic function
Advantages
If two downlink transmit antennas are deployed on an eNodeB, this feature is used to
improve cell-edge coverage through Tx diversity with two antennas.
Description
ZTE eNodeB supports using Tx diversity with two antennas to improve cell-edge
coverage in a low SNR or high-speed scenario. In addition, this transmit mode can
improve reliability of PBCH and control channels.
Tx diversity uses single-codeword and single-stream encoding mode for transmission.
Introduced Version
LR13.2 and Before
Enhancement
None

3.8.5 ZLF31-14-011 Open Loop 2*2 Spatial Multiplexing (LD-CDD)
Dependency
None
Attribute
Basic function
Advantages
If two antennas are deployed on an eNodeB in the downlink, this feature is used to
improve the single-UE and cell throughput by using open-loop spatial multiplexing in
downlink 22 MIMO.
Description
If RI=2 is reported by a UE with excellent SNR, ZTE eNodeB uses open-loop spatial
multiplexing to improve the peak value and average throughput of the UE and the cell.
In open-loop spatial multiplexing mode, a UE does not need to report its transmission
codebook. The correlation between two antenna channels is reduced manually through
large Cyclic Delay Diversity (CDD), which increases the spatial multiplexing efficiency
and UE throughput. Therefore, open-loop spatial multiplexing is suitable in a high-speed
coverage scenario.
Open-loop spatial multiplexing transmits two separately encoded streams (which means
two codewords) or one encoded stream (which means single codeword).
Introduced Version
LR13.2 and Before
Enhancement
None

3.8.6 ZLF31-14-012 Closed Loop 2*2 Spatial Multiplexing
Dependency
None
Attribute
Basic function
Advantages
improve the single-UE and cell throughput by using closed-loop spatial multiplexing in
downlink 22 MIMO.
Description
If a UE has an excellent SNR and the UE's radio conditions change slowly in a low-speed
or stationary scenario (such as in a room or hot zone area), ZTE eNodeB uses the
closed-loop spatial multiplexing technology to improve the peak value and average
throughput of the UE. After closed-loop spatial multiplexing is enabled for a UE, the UE
must feed back its PMI codebook indication. In accordance with the PMI reported from
the UE, the eNodeB selects an appropriate codebook for data transmission.
Because UEs need to feed back their PMI codebook, this feature is suitable only in a
low-speed scenario.
Closed-loop spatial multiplexing transmits two separately encoded streams (which

means two codewords) or one encoded stream (which means single codeword).
Introduced Version
LR13.2 and Before
Enhancement
None

3.8.7 ZLF31-14-013 Closed Loop 2*2 Spatial Multiplexing (Rank = 1)
Dependency
None
Attribute
Basic function
Advantages
improve cell-edge coverage for low-speed or stationary Cell Edge UEs (CEUs) by using
closed-loop spatial multiplexing (rank=1) in downlink 22 MIMO.
Description
If a UE has a poor SNR (at the cell edge) and the UE's radio conditions change slowly in
a low-speed or stationary scenario (such as in a room or hot zone area), ZTE eNodeB
uses the closed-loop spatial multiplexing (rank=1) technology to improve the peak value
and average throughput of the UE. After closed-loop spatial multiplexing (rank=1) is
enabled for a UE, the UE must feed back its PMI codebook indication. In accordance with
the PMI reported from the UE, the eNodeB selects an appropriate codebook for data
transmission.
Because UEs need to feed back their PMI codebook, this feature is suitable only in a
low-speed scenario.
Closed-loop spatial multiplexing (rank=1) transmits a single stream (which means single
codeword), which is also called codebook-based beamforming.
Introduced Version
LR13.2 and Before
Enhancement
None

3.8.8 ZLF31-14-021 Uplink 2-Ways MRC
Dependency
None
Attribute
Basic function
Advantages
If two receive antennas are deployed on an eNodeB and the cell interference is minor,
this feature is used to improve uplink coverage through a Maximum-Ratio Combining
(MRC) reception scheme.
Description
If two receive antennas are deployed on an eNodeB, the multi-antenna reception

diversity technologies can be used to improve uplink coverage.
There are two reception diversity technologies: MRC and Interference Rejection
Combining (IRC).
With MRC, two ways of received signals are combined proportionally based on SNR at
the symbol level. This feature is suitable in an AWGN-like environment with fewer UEs
and minor inter-cell interference.
Introduced Version
LR13.2 and Before
Enhancement
None
3.8.9 ZLF31-14-022 Uplink 2-Ways IRC
Dependency

None
Attribute
Basic function
Advantages
If two receive antennas are deployed on an eNodeB and the cell interference is high
(such as a commercial network with a great number of online UEs), this feature is used to
eliminate interference on UEs and improve uplink coverage through IRC reception
schemes.
Description
If two receive antennas are deployed on an eNodeB, the multi-antenna reception

diversity technologies can be used to improve uplink coverage.
There are two reception diversity technologies: MRC and IRC.
With IRC, two ways of received signals are combined proportionally based on
interference at the symbol level. This feature is suitable in an environment with many
UEs and high inter-cell interference.
Based on the link-level emulation effect, the link-level gains of IRC are increased by 2.5
dB in comparison with those of MRC.
Introduced Version
LR13.2 and Before
Enhancement
None
3.8.10 ZLF31-14-030 UL Open-Loop Power Control With FPC Supported
Dependency
None

Attribute
Basic function
Advantages
This feature is used to support the operator-configurable uplink open-loop power control
to reduce interference and increase uplink cell throughput in different scenarios.
Description
The purpose of PUSCH/SRS and PUCCH open-loop power control is to withstand

path-loss fluctuation, assist the AMC function, and reduce inter-cell interference.
ZTE eNodeB supports the following PUSCH/SRS and PUCCH open-loop power control
sub-functions:
PUSCH open-loop power control: In accordance with the network conditions, set an
PO_NOMINAL_ PUSCH
appropriate nominal PUSCH received power and fractional
path-loss compensation factor . UEs adjust their transmit power to partly

compensate for path loss in accordance with the eNodeB-delivered open-loop
power control parameters

PO_NOMINAL_ PUSCH
and .
PUCCH open-loop power control: In accordance with the network conditions, set an
appropriate nominal PUCCH received power PO_NOMINAL_ PUCCH and adjustment
factor F_PUCCH ( F ) for different PUCCH formats. UEs adjust their transmit power
to compensate for path loss in accordance with the eNodeB-delivered open-loop

power control parameters.
Operators can configure the above uplink open loop power control parameters.
Introduced Version
LR13.2 and Before
Enhancement

None
4 Transport Network Functionality
4.1 Physical Interface
4.1.1 ZLF32-00-001 FE/GE Interface
Dependency
Hardware device: CC board
Attribute
Basic function
Advantages
This feature provides Ethernet-based transport interfaces meeting basic bandwidth

requirements.
Description
The eNodeB supports auto-sensing 100/1000 Base-T FE/GE (RJ45) and GE

(optical/electrical) interfaces defined in IEEE 802.3 (2005).
The eNodeB supports 1000Base-LX/1000Base-BX/1000Base-SX (MM)

fiber/100Base-FX Ethernet interfaces.
The eNodeB supports standard SFP conversion modules.
The eNodeB uses a CC board to provide Ethernet interfaces, and one CC board
provides two FE/GE optical or electrical interfaces.

Figure 4-1 Basic Physical Interfaces
GE Interface for Debug
GE/FE Electrical/Optical
Interface for Transmission
Introduced Version
LR13.2 and Before
Enhancement
None
4.2 Link Layer
4.2.1 ZLF32-01-001 VLAN
Dependency
None
Attribute
Basic function
Advantages
This feature provides a standard VLAN function.
Description

Ethernet access is a widely-used technology in the LTE era for building a backhaul
network. The VLAN technology is used in Ethernet access networks to isolate traffic and
prevent broadcast storms.
The eNodeB supports 802.1Q-defined VLANs, and can send control-plane, user-plane,
and OMC traffic data through different VLANs. For example, S1-C, S1-U, X2, and OMC
traffic data can be configured so that it is sent in different VLANs. The eNodeB supports
a maximum of 30 VLANs, and the VLAN ID ranges from 1 to 4095.
In a multimode base station, VLANs can be used to isolate LTE traffic from traffic of other
system modes.
The switch connected to each eNodeB supports two-layer VLAN encapsulation for QinQ
implementation.
The following figure shows the multi-VLAN application.
Figure 4-2 VLAN Application for LTE
Switch at the
transport network may
add another layer
VLAN thus used as
QinQ scheme
SVLAN VLAN Payload

Qos policy divides
traffic into different GSM
priorities based on
X2 different VLANs
S1 OMC and marking LTE UMTS
IP1 IP2 IP3 IP

VLAN Payload
eNodeB eNodeB/NodeB
eNodeB will separate LTE traffic with

VLAN tag into different traffic
(S1/X2/OMC etc)
Introduced Version
LR13.2 and Before

Enhancement
None
4.2.2 ZLF32-01-002 VLAN Mapping
Dependency
Feature list: ZLF32-01-001 VLAN
Attribute
Basic function
Advantages
This feature maps service flows to different VLANs to implement different flow control
policies.
Description
LTE interfaces include the S1-MME, S1-U, X2, and OMC interfaces. The S1-MME
interface transfers Session Management (SM) and Mobility Management (MM)
messages (signaling-plane or control-plane messages), and the S1-U interface builds a
tunnel between the GW and the eNodeB to transfer user-plane data. The X2 interface
transfers control-plane and user-plane messages between eNodeBs, and the OMC
interface transfers network management messages. With VLAN mapping, control-plane,
user-plane, X2, and OMC data can be allocated to one or more different VLANs, and
data within each VLAN is isolated during transmission to enhance transmission security.
Introduced Version
LR13.2 and Before
Enhancement
None

4.3 Network Layer
4.3.1 ZLF32-02-001 DHCP
Dependency
None
Attribute
Basic function
Advantages
This feature uses DHCP to reduce the load of manually configuring IP addresses for the
eNodeB.
Description
DHCP is a protocol using UDP and relies upon the IP broadcast feature. For
interoperability with an L3 VPN, the DHCP relay function is required.
During automatic eNodeB configuration with DHCP, no configuration information on a

specific site is required from site engineers.
Through DHCP, the eNodeB can obtain the following information: eNB IP address and
subnet mask, default gateway IP address, security gateway IP address, OMC server
address and CA IP address.
The following figure shows the DHCP application for an eNodeB.

Figure 4-3 DHCP Application for an eNodeB
With DHCP handshake, eNodeB learn from DHCP optional message:

1, eNodeBs IP address and its subnet mask.
2, one or more IP addresses of def ault gateway. (DHCP Relay)
3, one or more IP address of security gateway. RADIUS
4, IP address of OMC server and CA IP address. MME
Broadcast domain Unicast domain
xGW
PAE Authentication
Authentication S1-MME
S1-U O MC
S1-MME traffic
S1-U traffic Remote X2
eNB OMC
Aut horise d X2 traffic
Port
OMC traffic S5/S8/S11
Security CA
DHCP Relay
Gateway
DHCP/D NS
Access Backhaul/Aggregation Core
Introduced Version
LR13.2 and Before
Enhancement
None
4.3.2 ZLF32-02-002 IPv4 Protocol Stack
Dependency
None
Attribute
Basic function
Advantages
This feature provides IPv4 and related protocols to meet IPv4 network requirements.
Description
IPv4 is a base protocol stack for eNodeB data transmission. The eNodeB supports IPv4
and related standards, which carry upper-layer application protocols, including

control-plane and user-plane protocol data, and network management protocol data. The
IPv4 protocol stack includes basic IP protocols such as ICMP and ARP.
During data transmission, the IP layer receives upper-layer protocol messages to be sent
(for example, UDP messages). There is MTU restriction on the data link layer, so if any
upper-layer message is too long, the IP layer segments the message. If the message
length is proper, the IP layer does not segment the message. Upper-layer protocol
messages or message segments are encapsulated into IP data grams in fixed format as
the payload, and transmitted over the bearer network. When receiving data, the IP-layer
receiving end consolidates the payload into upper-layer protocol messages based on IP
datagram headers.
Figure 4-4 LTE Transmission Protocol Stack
MME
UE eNB NAS
S1AP
NAS
APP SCTP
RRC RRC S1AP X2AP
IP
PDCP PDCP SCTP
RLC RLC IP
SGW
MAC MAC GTPU
GTPU
PHY PHY UDP
UDP
IP
Control plane traffic

User plane traffic
Introduced Version
LR13.2 and Before
Enhancement
None

4.3.3 ZLF32-02-005 IPv4 Address
Dependency
None
Attribute
Basic function
Advantages
This feature provides a means of IPv4 address configuration. The carrier can flexibly
choose how to configure IP addresses for an eNodeB based on traffic.
Description
An eNodeB can be configured with a single IP address, and all the logical interfaces such
as S1, X2, and OMC use the IP address for service data transmission, so that IP address
resources can be saved.
An eNodeB can also be configured with multiple IP addresses, and each IP address is
used for one logical connection. For example, different IP addresses can be configured
for S1-MME, S1_U, X2, OMC, and IEEE 1588v2 traffic.

Figure 4-5 Multi-IP-Address Configuration Scenario
e-NB
MME
Backhaul network S-GW
1588v2 server
IP address
A
e-NBIP address OMC

B
IP address
C
IP address
D
X2 traffic
S1 traffic
OMC traffic
1588v2 traffic
Introduced Version
LR13.2 and Before
Enhancement
None
4.4 Traffic and QoS
4.4.1 ZLF32-03-001 Traffic Marking and Mapping
Dependency
None
Attribute
Basic function

Advantages
This feature implements the QoS mechanism defined by the DiffServ model and
implements CoS marking for L2 traffic and DSCP marking for L3 traffic. This feature
supports mapping wireless QCIs into CoS and DSCP values and implements traffic
classification.
Description
The DiffServ model is used in an LTE network as a QoS mechanism, and classifies IP
traffic in a backhaul network into different classes (such as gold, silver, and copper
classes, or 8 classes defined in IEEE 802.1p), so that different forwarding and
processing mechanisms are used for different classes.
The eNodeB must be able to differentiate priority levels of uplink traffic, and mark the
traffic on the IP layer or Ethernet layer.
The service flow of each user between the UE and the core network has a bearer, and
each bearer is associated with QoS parameters such as QCI, GBR, MBR, AMBR, and
PBR. The eNodeB can adjust different scheduling parameters and the RRM algorithm to
ensure QoS requirements of different bearers.
Data is transparently transmitted on a wireless bearer in a backhaul network, so the

transport network does not need to learn about bearer information.

Figure 4-6 LTE Traffic Model
Application / Service Layer
UL Service Data Flows DL Service Data Flows
UL TFT DL TFT
UL TFT RBID DL TFT S5/S8a-TEID
RBID S1-TEID S1-TEID S5/S8a-TEID
UE eNodeB S1 Bearer Serving GW S5/S8 Bearer PDN GW

Radio Bearer
Based 802.1P Based IP DSCP

e-NB
xGW
e-NB
Bearer
The eNodeB can map bearers into backhaul DifferServ traffic, and the carrier can
configure the mapping relationships between 802.1p or DSCP values between bearers
and the backhaul network. In a backhaul network, packets with different 802.1p or DSCP
values can be processed with different priorities in a queue.
The eNodeB supports traffic marking through DSCP/802.1p. S1/X2/OMC traffic can be
allocated with different priority levels based on different rules, and traffic priorities can be
identified based on IP addresses or VLANs.
The following table shows the eNodeB service mapping relationships.
Table 4-1 eNodeB Service Mapping Relationships
No. Service Type Example DSCP Mapping 802.1p

Mapping
1 QCI 1 (GBR) Conversational Voice EF(46) 5

101110
2 QCI 2 (GBR) Conversational Video (Live CS4(32) 4

Streaming) 100000
3 QCI 3 (GBR) Real Time Gaming CS4(32) 4

100000
4 QCI 4 (GBR) Non-Conversational Video CS3(24) 3

(Buffered Streaming) 011000
5 QCI 5 (Non-GBR) IMS Signaling CS5(40) 5

101000
6 QCI 6 (Non-GBR) Video (Buffered Streaming) AF33(30) 3

TCP-based (for example, www, 011110
e-mail, chat, ftp, p2p file
sharing, or progressive video)
7 QCI 7 (Non-GBR) Voice, AF43(38) 4

Video (Live Streaming) 100110
Interactive Gaming
8 QCI 8 (Non-GBR) Video (Buffered Streaming) AF13(14) 1

TCP-based (for example, www, 001110
e-mail, chat, ftp, p2p file
9 QCI 9 (Non-GBR) DF(0) 000000 0
sharing, or progressive video)
10 SCTP EF(46) 5
101110
11 OMC EF(46) 5
101110
12 SYNC PTP1588 EF(46) 5

101110
13 Other DF(0) 000000 0
Introduced Version
LR13.2 and Before
Enhancement
None

4.4.2 ZLF32-03-005 Traffic Statistics
Dependency
None
Attribute
Basic function
Advantages
This feature collects statistics on the traffic that the eNodeB sends and receives.
Description
In an IP-based network, the LTE S1/X2 interface may have the problems of unstable
transmission rate and bandwidth fluctuation, so the carrier needs to detect the network
QoS conditions to ensure service quality. Traffic statistics provides the following
information: total throughput of input and outgoing, traffic of S1-MME, S1-U, OMC
information.
Introduced Version
LR13.2 and Before
Enhancement
None
4.5 Security
4.5.1 ZLF32-04-018 SFTP
Dependency
None
Attribute

Basic function
Advantages
This feature ensures file transfer security for an eNodeB.
Description
The Secure File Transfer Protocol (SFTP) provides a secure encryption method for
file transfer.
To meet eNodeB system security requirements, SFTP is used instead of FTP for
communication between the front end and the back end. This feature is used for data
transmission between the front end and the back end.
An eNodeB can provide the following functions based on SFTP:
1) Manages SSH network connections.
2) Supports encrypted file transfer where authentication can be implemented.
3) Provides the log function for easy rights management.
4) Provides serviceability tools for maintenance.
Introduced Version
LR13.2 and Before
Enhancement
None
4.5.2 ZLF32-04-019 SNMP
Dependency
None
Attribute
Basic function
Advantages

This feature provides a standard communication interface between an eNodeB and the
network management system.
Description
The OMC supports the following SNMP functions:
Basic operations of the SNMP protocol
SNMP Get request
SNMP Get-Next request
SNMP Set request
SNMP Response
SNMP safe mode
The OMC can interact with the NMS through the northbound SNMP interface.
Real-time alarm reports
The OMC can actively send alarms generated by NEs to the NMS.
Obtaining alarm IRP version information
The NMS can obtain alarm IPR version information through this interface.
Obtaining heartbeat IRP version information of alarms
The NMS can obtain heartbeat IPR version information of alarms through this interface.
Querying and setting the heartbeat period
The NMS can query and set the heartbeat period through this interface.
Querying the current alarms
Introduced Version
LR13.2 and Before
Enhancement
None

4.6 Synchronization
4.6.1 ZLF32-05-001 GPS Synchronization
Dependency
Hardware device: CC board
Attribute
Basic function
Advantages
This feature provides high-precision frequency and phase synchronization for an

eNodeB.
Description
For an LTE FDD network, frequency synchronization ensures that the frequency
difference for roaming services between eNodeBs is within a particular range, and the
difference from the reference source does not exceed +/- 0.05ppm.
For a traditional wireless network, frequency synchronization is implemented through a

TDMA transport network or the GPS. An LTE transport network is an IP-based network,
and Ethernet is a frequently-used technology. The eNodeB supports the following
synchronization techniques: Synchronous Ethernet, IEEE 1588v2, and GPS.
The eNodeB supports GPS clock input for synchronization. The GPS input interface is
located on a CC board, see the following figure. There are two types of input interfaces:
HDMI interfaces and feeder interfaces.

Figure 4-7 GPS Synchronization
HDMI clock interface Connect GPS antenna
Introduced Version
LR13.2 and Before
Enhancement
None
4.6.2 ZLF32-05-030 NTP Time Information
Dependency
None
Attribute
Basic function
Advantages

This feature uses the NTP protocol to synchronize the time of all NEs. The system
supports DST and multiple time zones, and can switch between DST mode and
multi-time-zone mode.
Description
The OMC supports NTP/SNTP, and uses a third-party server to provide the clock
source, ensuring time synchronization between the OMC and NEs.
For security purposes, the OMC uses the MD5 encryption algorithm defined in NTPv3.
Time synchronization is implemented as follows:
All the NEs in the network and the OMC use the same clock source server (GPS)
and use the NTP protocol. All the synchronization processes comply with RFC
2030.
The OMC configures the IP address and port of the clock source server through a
configuration file. Normally, the clock server is deployed on the OMC system side.
When the clock server is activated, it automatically implements time synchronization,
and the time on the OMC server is synchronized with the clock source server. When
an NE is connected to the OMC server, the OMC server sends its time information
to the NE for synchronization. The time synchronization interval can be set.
DST and multi-time-zone are supported as follows:
The OMC supports DST and multi-time-zone modes. A star network is established
between the OMC system and NEs for time synchronization. When the OMC server
is activated, the system synchronizes the time of all the NEs with the OMC server.
The system can switch between DST mode and multi-time-zone mode, ensuring
correct time in a multi-time-zone network.
Introduced Version
LR13.2 and Before
Enhancement
None

5 SON Functionality
5.1 Self-Healing
5.1.1 ZLF33-04-003 Software & Hardware Self-Healing
Dependency
None
Attribute
Basic function
Advantages
This feature is to clear software and hardware faults automatically to restore or isolate
faulty units and reduce the impact on the current network and UEs.
Description
The system detects and analyzes the software and hardware faults in accordance with
alarms, and triggers the appropriate recovery actions, including powering off faulty
boards, reloading software, resetting boards, handing over faulty units with backup units.
This feature can be applied in the following scenarios:
Version verification and fallback when a software version is be loaded
Identification and clearing of software and hardware faults during the eNodeB
operation
Automatic identification and isolation of software and hardware faults during

operation
Introduced Version
LR13.2 and Before

Enhancement
None
5.1.2 ZLF33-04-004 Antenna Fault Diagnosis
Dependency
None
Attribute
Basic function
Advantages
The feature supports the problem diagnosis and monitoring about antenna system, which
can improve the accuracy and efficiency of the fault locating, reduce the efforts to log in
to the site/tower, and use less equipment for measurement. The benefits of it are to
facilitate problem analysis and to decrease the OPEX.
Description
The problems about the antenna are complex, implicit, and serious for the affect of the
network performance. Therefore, it brings lots of difficulties for the daily maintenance.
The common problems are brought by the installation and ageing of the equipment.
For the ease of diagnosis, the faults can raise associated alarms automatically.
The alarms includes high threshold of RSSI (received signal strength indicator), low
threshold of RSSI, SWR (stand wave ratio).
Introduced Version
LR13.2 and Before
Enhancement
None

6 AAS
6.1 ZLF36-00-001 Independent Uplink and Downlink

Downtilts
Dependency
Software: none
Hardware: AAS devices with different frequency bands. This feature is not applicable to
macro eNodeBs.
Attribute
Basic function
Advantages
This feature increases the uplink and downlink system throughput. .
Description
Based on the system emulation result, LTE uplink transmission and downlink
transmission have different downtilt requirements for best coverage. For example, uplink
transmission requires an antenna downtilt of 6, and downlink transmission requires an
antenna downtilt of 7, which is different from the conventional deployment for uplink and
downlink transmission with the same downtilt. The AAS supports independent uplink and
downlink downtilts through multi-antenna amplitude and phase synthesis, so that the
uplink and downlink antennas operate at the best angle, thus increasing the system
capacity.
Introduced Version
LR13.2 and Before
Enhancement

None
7 Glossary
Abbreviations Full Attributes
1xRTT CDMA2000 1x Radio Transmission Technology
3GPP 3rd Generation Partnership Project
ABS Almost Blank Subframe
AIS Alarm Indication Signal
AM Acknowledged Mode
AMBR Aggregate Maximum Bit Rate
ANR Automatic neighbor Relation
ARP Allocation and Retention Priority

AS Access Stratum
AWGN Additive White Gaussian Noise
BCCH Broadcast Control Channel
BCH Broadcast Channel
BFD Bidirectional Forwarding Detection
BLER Block Error Rate
BSR Buffer Status Report

CA Carrier Aggregation
CC Chase-Combing
CCCH Common Control Channel
CCE Channel Control Element
CCO Cell Change Order

CCO Coverage and Capacity Optimization
CDT/MR Call Detail Trace / Measurement Report
CESoPSN Circuit Emulation Service over Packet Switched Network
CGI Cell Global Identifier
CLSM Close-Loop Spatial Multiplexing
CMC Connection Mobility Control
COC Cell Outage Compensation
CoMP Coordinated Multipoint Tx/Rx


COS Class of Service
CQI Channel Quality Indicator
CS Certification Server
CSFB CS Fallback
CTS Call Trace System

C-RNTI Cell Radio Networks Temporary Identifier
DCCH Dedicated Control Channel

DCI Downlink Control Information
DES Data Encryption Standard
DHCP Dynamic Host Configuration Protocol
DiffServ Differentiated Services
DL Downlink
DL-SCH DL Shared Channel
DRX Discontinuous Reception
DSCP Differentiated Services Code Point
DTCH Dedicated Traffic Channel
DTX Discontinuous Transmission
EMBMS Evolved Multimedia Broadcast and Multicast Service
eNodeB E-UTRAN NodeB

EAP Extensible Authentication Protocol
EAPOL EAP over LAN
ECN Explicit Congestion Notification
EPC Evolved Packet Core
EPS Evolved Packet System

ESP Encapsulating Security Payload
E-UTRAN Evolved UTRAN
ETWS Earthquake and Tsunami Warning System
EVC Ethernet Virtual Connection
FDD Frequency Division Duplex
FE Fast Ethernet
FFR Fractional Frequency Reuse


FTP File Transfer Protocol
GCI Global Cell ID
GE Gigabit Ethernet
GERAN GSM EDGE Radio Access Network
GNSS Global Navigation Satellite System

GSM Global System for Mobile communication
GBR Guaranteed Bit Rate

GPS Global Positioning System
GTP GPRS Tunneling Protocol
GUMMEI Globally Unique MME Identifier
HARQ Hybrid Automatic Repeat Request
HetNet Heterogeneous Network

HII High Interference Indicator
HSDPA High Speed Downlink Packet Access
HRPD CDMA2000 High Rate Packet Data
HTTP HyperText Transfer Protocol
ICIC Inter-Cell Interference Coordination
IEEE Institute of Electrical and Electronics Engineers
IKE Internet Key Exchange

IMS Inventory Management Server
IP Internet Protocol
IPsec Internet Protocol Security
IP-CAN IP Connectivity Access Network
IP-SM-GW IP-Short-Message-Gateway
IR Incremental-Redundancy
ITU International Telecommunication Union
LB Load Balancing
LDAP Lightweight Directory Access Protocol
LMT Local Maintenance Terminal
LTE Long Term Evolution
MAC Medium Access Control


MBMS Multimedia Broadcast Multicast Service
MBR Maximum Bit Rate
MCCH MBMS point-to-multipoint Control Channel
MCH Multicast Channel
MIB Master Information Block

MIMO Multiple Input Multiple Output
MLB Mobility Load Balancing

MME Mobility Management Entity
MPLS Multi-Protocol Label Switching
MTCH MBMS point-to-multipoint Traffic Channel
NACC Network Assisted Cell Change
NAS Non-Access Stratum

NCL Neighbor Cell List
NE Net Element
NRT Neighbor Relation Table
O&M Operation & Maintenance
OAM Operation Administration Maintenance
OFDM Orthogonal Frequency Division Multiplexing
OI Overload Indicator
OLSM Open-Loop Spatial Multiplexing
OMC Operation and Maintenance Center
PBCH Physical broadcast channel
PBR Prioritized Bit Rate
PCCH Paging Control Channel

PCH Paging Channel
PCFICH Physical control format indicator channel
PCI Physical Cell Identity
PDB Packet Delay Budget
PDCCH Physical downlink control channel
PDCP Packet Data Convergence Protocol
PDSCH Physical downlink shared channel


PE Provider Edge
PER Packet Error Rate
PHB Per-Hop Behavior
PKI Public Key Infrastructure
PHICH Physical Hybrid ARQ Indicator Channel

PLMN Public Land Mobile Network
PMCH Physical multicast channel

PQ Priority Queuing
PRACH Physical random access channel
PRB Physical Resource Block
PTP Precision Time Protocol
PUCCH Physical uplink control channel

PUSCH Physical uplink shared channel
PWE Pseudo Wire Emulate
QCI QoS Class Identifier
QoS Quality of Service
QPSK Quadrature Phase Shift Keying
RACH Random Access Channel
RADIUS Remote Authentication Dial In User Service

RAT Radio Access Technology
RBC Radio Bearer Control
RDI Remote Defect Indication
RF Radio Frequency
RLC Radio Link Control

RNTP Relative Narrowband Transmit Power
RO RACH Optimization
ROHC Robust Header Compression
RS Reference Signal
RSRP Reference Signal Received Power
RRC Radio Resource Control
RRM Radio Resource Management


RTP Real-time Transport Protocol
RV Redundancy Version
SAE System Architecture Evolution
SAP Service Access Point
SDH Synchronous Digital Hierarchy

SDR Software Defined Radio
SFR Soft Frequency Reuse

SHA Secure Hash Algorithm
S-GW Serving Gateway
SINR Signal Interference Noise Ratio
SIB System Information Block
SM Short Message
SON Self Organizing Network
SONET Synchronous Optical Network
SPS Semi-Persistent Scheduling
SRVCC Single Radio Voice Call Continuity
SU-MIMO Single-User Multi Input and Multi Output
SW Software
TA Tracking Area
TAU Tracking Area Update
TBS Transport Block Size
TCP Transport Control Protocol
TTI Transmission Time Interval
UDP User Datagram Protocol

UE User Equipment
UL Uplink
UL-SCH UL Shared Channel
UTRAN Universal Terrestrial Radio Access Network
VPN Virtual Private Network
VLAN Virtual Local Area Network
VoIP Voice over IP


WFQ Weighted Fair Queuing

ZTE LTE FDD LR15 Basic Feature Description - 20161221

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ZTE LTE FDD LR15 Basic Feature Description - 20161221

Hochgeladen von

Copyright:

Verfügbare Formate

LTE FDD Basic Feature

LTE FDD Basic Feature Description

2016 ZTE Corporation. All rights reserved.

ZTE Confidential & Proprietary 1

1 System and Standards ...................................................................................... 7

2 Services and Radio Access Bearers .............................................................. 19

3 Radio Network Functionality .......................................................................... 22

2 ZTE Confidential & Proprietary

3.2.9 ZLF31-07-010 LTE->CDMA eHRPD Cell Reselection........................................ 47

ZTE Confidential & Proprietary 3

3.8 Radio Part .......................................................................................................... 89

4 Transport Network Functionality.................................................................. 100

5 SON Functionality ......................................................................................... 118

6 AAS ................................................................................................................ 120

7 Glossary ......................................................................................................... 121

4 ZTE Confidential & Proprietary

ZTE Confidential & Proprietary 5

Figure 3-1 Structure of System Information Blocks ............................................................23

Table 1-1 Basic Logical Channels ......................................................................................15

6 ZTE Confidential & Proprietary

1 System and Standards

1.1 3GPP Compliance

1.1.1 ZLF31-00-001 System Complying With 3GPP E-UTRAN R8

Independent of peripheral NEs

It supports the basic functions defined in 3GPP R8 FDD.

LR13.2 and Before

LR14 supports 3GPP R10.

1.1.2 ZLF31-00-002 System Complying With 3GPP E-UTRAN R9

Independent of peripheral NEs

ZTE Confidential & Proprietary 7

It supports the enhanced functions defined in 3GPP R9 FDD.

3GPP R9, completed in March 2010, is an enhancement of 3GPP R8.

LR13.2 and Before

LR14 supports 3GPP R10.

1.1.3 ZLF31-00-003 System Complying With 3GPP E-UTRAN R10

Independent of peripheral NEs

It supports the enhanced functions defined in 3GPP R10 FDD.

3GPP R10, completed in Dec.2010, is a further enhancement of 3GPP R10.

LR13.2 and Before

8 ZTE Confidential & Proprietary

1.1.4 ZLF31-00-004 E-UTRAN Interfaces

Independent of peripheral NEs

It describes the connections between Network Elements (NEs) in E-UTRAN.

ZTE eNodeB supports the following interfaces:

Interface between the eNodeB and the EPC

E-RAB service management function

Initial context transfer function

This function is used to establish an S1 UE context in the eNodeB, establish

ZTE Confidential & Proprietary 9

the MME, and transfer Non-Access Stratum (NAS) signaling related

Mobility functions for UEs in ECM-CONNECTED

Used to provide a change of eNodeBs within SAE/LTE (Handover

Used to provide a change of RAN nodes between different RATs

NAS signaling transport function between the UE and the MME:

Used to transfer NAS signaling related information and to establish the

Used to transfer NAS signaling related information when the S1 UE

S1 UE context release function

This function is used to manage the release of UE specific contexts in the

10 ZTE Confidential & Proprietary

The purpose of the error indication procedure is to report detected logical

The purpose of the reset procedure is to release all allocated resources on S1

The purpose of the configuration update procedure is to update application

UE capability info indication